Tag Archives:  

Connected Redis Execute command Error: (error) MISCONF Redis is configured to save RDB snapshots,

Error reporting when connecting to redis

(error) MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error.

The solution is as follows:

Connect redis and run the config set stop writes on bgsave error no command

Close the configuration item stop writes on bgsave error to solve the problem.

[Solved] React Issue: Selected Style Not Working

Source code:

<NavLink to="/home1" activeClassName="selected"> Home Page 1</NavLink>
        <NavLink activeStyle={{
            fontWeight: 'bold',
            color: 'red'}}
          to="/home2"> Home Page 2
        </NavLink>

report errors:

index.js:1 Warning: React does not recognize the `activeClassName` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `activeclassname` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

First check your version:

All versions above V6 will report this error. Just change back to V5. At the same time, if you use <Routes> Please delete this V6 attribute

[Solved] VScode error: vetur can’t find ‘tsconfig. JSON’ or ‘jsconfig. JSON’. Solution to red wave error “vetur. Ignoreprojectwarning”: true, 

    // VSCode Error: Vetur can't find 'tsconfig.json' or 'jsconfig.json' solution, Red wave error solution
    "vetur.ignoreProjectWarning": true,
    "eslint.enable": false,
    "vetur.validation.template": false,
    "files.associations": {
        "*.vue": "html"
    }

When using FORTRAN under vs, there is a fatal error lnk1561: the entry point must be defined, which is the solution to this problem   

After chopping hands, the fraud call came before the express delivery was received. How to improve the privacy and security of e-commerce>>>

After IVF is installed, a new project is created, but it can’t run

The error is as follows

solution:

Click configuration manager

Click new on the platform, select new platform, copy settings from here, and select Win32

Set the active solution platform to x64

It can run normally

Note: if you don’t select it, copy the settings from here and select Win32. The following error will be reported. You only need to delete the new one and reset it

   Error occurred when executing the make command G + +: command not found

Geeks, please accept the hero post of 2021 Microsoft x Intel hacking contest>>>

Error occurred when executing the make command G + +: command not found

October 24, 2016 12:31:29

Number of readings: 4366

Problems encountered by friends when installing node

Error report screenshot:

in fact, it’s very simple, just need to install
Yum – y install GCC automake Autoconf libtool make
and Yum install GCC gcc-c +

Setting up CocoaPods master repo [How to Fix Stuck Issue]

Setting up cocoapods master repo stuck

1. That’s because of the mirror image of Taobao（ https://ruby.taobao.org/ ）It’s no longer available. So now we use the latest supported Ruby image（ https://gems.ruby-china.org/ )

Command line required:

$gem sources -r https://rubygems.org/ (remove the old version of the image. If you don’t know what image is currently used on your computer, you can use $gem sources – L to view it)
$gem sources – A https://gems.ruby-china.org/ (add available images)
$gem sources – L

2. When pod setup enters the setting up cocoapods master repo, it means that it is downloading. At this time, you can open a new terminal window, enter the command line “Cd ~ /. Cocoapods /”, jump to the cocoapods folder, and execute “Du – sh *” to check the size of the folder being downloaded

3. When it appears as follows

[!] An error occurred while performing `git pull` on repo `master`.

[!]/usr/bin/git pull –ff-only

This error should mean that there is something wrong with this node. Then try to delete the node of cocoapods and add another node. Maybe it’s OK

Reason: the branch of cocoapods does not support the latest Xcode version

Solution: delete the master branch and create a new one

sudo rm -fr ~/.cocoapods/repos/master

Then: pod setup