When the following error occurs in the console，it means that the plug-in is installed incorrectly
Can’t resolve ‘ansi-html-community’
Cannot find module ‘is-docker
Don’t use npm install
npm i vuex-persistedstate
But the environment you use is yarn, so you need to use yarn to install the plugin
yarn add vuex-persistedstateThen the problem can be solved smoothly
Solution：
sys_include=(/usr/include,/usr/lib/gcc-lib/i486-suse-linux/2.95.3/include,/usr/lib/gcc-lib/i386-redhat-linux/2.96 /include)
Solution：
$cd /home
$chmod –R 744 oracle
Problem symptoms:
“ORA-01034: ORACLE not available
ORA-27121: unable to determine size of shared memory segment
SVR4 Error: 13: Permission denied”
Solution:
Log in as the oracle user, execute the following command
$cd $ORACLE_HOME/bin
$ls -altr oracle #Modify if it is not the following permissions after viewing
$ chmod 6751 oracle
Solution：
Start oracle service and monitor.
Solution：
Check whether the language configurations such as nls under the .bash_profile file are the same as the oracle user’s .bash_profile.
Solution：
Check whether the configuration and order related to tuxedo under the .bash_profile file are correct (Compare with the actual path).
Solution：
Maybe the license of tuxedo is incorrect. Check whether the lic.txt under /home/tuxedo/Tuxedo 8.1/bealic has been overwritten, or check whether the TYPE= SDK in lic is correct, and the value of type is SDK.
Solution：
View the machine name in the ubbwinnt file, modify and recompile.
Solution：
Tmshutdown -y stop all services, and recompile.
Solution：
Ipcrm, ipcs or restart the computer.
Solution：
Solution：
Check whether the executable file generated when the source file is compiled is missing in the bin folder. Also if the tuxconfig file is missing, it will also prompt a “GMDTUX_CAT:1360” error.
Solution：
Solution：
Check if the tuxedo patch has been installed, Check if the tuxedo runner path has been added to the path of the system environment variable. You can add the corresponding files that are prompted to be missing to “C:\WINDOWS\system32”.
Solution：
Check if the path in the .bash_profile file is the configured fbase path. Whether the fbase installation package upload is useful requires binary upload.
Solution：
Check if the fbase path is correctly configured in the .bash_profile file.
Solution：
json is not compiled successfully, Enter the json path to check whether the .lib folder is generated.
Solution：
Add F:\hs\fbase20\Fbase_win32\lib to the environment variable system variable path value; add F:\hs\fbase20\Fbase_win32\lib to the user variable lib value.
After successfully building Linux, installing the required dependency libraries, and installing WPS and WRF. Run an instance simulation.
./ungrib.exe reports an error that libpng16.so.16 cannot be found.
The error is as follows：
./ungrib.exe: error while loading shared libraries: libpng16.so. 16: cannot open shared object file: No such file or directory
sudo vim /etc/ld.so.conf
Add statement: /home/tian/Software/libpng-intel/lib
sudo ldconfig
Go to ./ungrib.exe to run successfully
The reason for this exception found on the Internet is basically that the kotlin version does not conform to the cause, Maybe the kotlin version will also cause this error.
But my error is not due to the kotlin version problem, but due to the conflict of the component cache version pulled down by the pub command, as shown below:
fluwx-3.9.1 and 3.9.2, delete and yml file Inconsistent versions resolve this exception.
Component name: There may be two reasons for the exception of compileDebugKotlin:
1. The kotlin version often said on the Internet does not conform to
2. There are different versions of the components in the pub cache and they conflict
Determine whether the obj object contains the children attribute, but the following error occurs
Do not access Object.prototype method ‘hasOwnProperty’ from target object.
Cannot directly access methods on Object prototype
Reason：
It is not safe to call hasOwnProperty directly on the result object，If the obj object itself has the hasOwnProperty property，there will be some unexpected problems when calling it. If someone with intentions takes advantage of ，set the property in obj to malicious code， will cause some security issues.
Workaround：
Use call to change the call point
const hasChild = Object.prototype.hasOwnProperty.call(obj, 'children');CARLA reports error rpc server
Trying to do some research on autopilot with carla,When running the example，error:
RuntimeError: trying to create rpc server for traffic manager; but the system failed to create because of bind error.
Possible reasons for this issue: The last time the PythonAPI was run was not properly terminated,causing some resources or ports Occupied.
Solution：
1）Restart carla;
2）If the error is still reported after restarting carla, Then restart the computer.
When installing Nignx
Installing the GCC compiler
yum install -y gcc
Report an error as below:
Error: Package: glibc-headers-2.17-317.el7.x86_64 (base)
Requires: glibc = 2.17-317.el7
Installed: glibc-2.17-322.el7_9.i686 (@c6-update)
glibc = 2.17-322.el7_9
Available: glibc-2.17-317.el7.i686 (base)
glibc = 2.17-317.el7
Error: Package: glibc-devel-2.17-317.el7.x86_64 (base)
Requires: glibc = 2.17-317.el7
Installed: glibc-2.17-322.el7_9.i686 (@c6-update)
glibc = 2.17-322.el7_9
Available: glibc-2.17-317.el7.i686 (base)
glibc = 2.17-317.el7
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Show one installed version higher than the required version
Resolved by downgrading.
yum downgrade glibc glibc-devel glibc-common glibc-headers
Installation success!
Installed:
gcc.x86_64 0:4.8.5-44.el7
Dependency Installed:
cpp.x86_64 0:4.8.5-44.el7 glibc-devel.x86_64 0:2.17-317.el7 glibc-headers.x86_64 0:2.17-317.el7 kernel-headers.x86_64 0:3.10.0-1160.el7 libmpc.x86_64 0:1.0.1-3.el7
mpfr.x86_64 0:3.1.1-4.el7
Complete!
keystone install error: Failed to parse /etc/keystone/keystone.conf: at /etc/keystone/keystone.conf:687, No ‘:’ or ‘=’ found in assignment: ‘connection’
Reason: The connection is not = or colon
Modified
Note the keyistone format
wangeditor5 Import and Run Error: You may need an appropriate loader to handle this file type (es6 compatibility issues)
Recently upgraded the rich text wangeditor used, I upgraded to the latest version of wangeditor5
Introduced wangeditor5 into the vue project, Starting the project has been reporting errors
You may need an appropriate loader to handle this file type
At first, I tried many methods but failed to solve it, Later I noticed an error reported in the console， Guess it may be related to the writing method of (…) in es6, So I will make a specific query later I took a look at the issue of compatibility with es6, I learned that webpack can only process a part of ES6 syntax, some more advanced ES6 syntax cannot be processed，Need to do compatibility processing.
1. Install the babel-polyfill es6-promise package
npm i babel-polyfill es6-promise --save
2. Add the following codes to main.js:
import 'babel-polyfill' //Note: This import should be before import Vue from 'vue'
import Vue from 'vue'
import Es6Promise from 'es6-promise'
Es6Promise.polyfill()
3. Add the following codes to webpack.base.conf.js:
module.exports = {
...
entry: {
app: ["babel-polyfill", "./src/main .js"]
},
...
}
Because wangeditor5 is a third-party dependency, in node_modules, and babel-polyfill does not detect es6, in node_modules, we need to add it manually.
Note：If you do not configure es6 compatibility for third-party dependencies，You can ignore the fourth step，You can run the startup project after the third step directly
4. In the webpack.base.conf.js file, modify the configuration of babel-loader, add a configuration item: resolve(‘node_modules/@wangeditor’ )(It needs to be modified according to the third-party dependencies actually introduced)
{
test: /\.js$/,
loader: 'babel-loader' ,
include: [resolve('src'), resolve( 'test'), resolve('node_modules/@wangeditor' ), resolve('node_modules/webpack-dev-server/client')]
},
Finally restart the project to be successful!
Developing a microservice project, requires the service registration and configuration center. The development and application of Nacos technology. The native OS is Windows11, Nacos version is 2.1.1 installed on Drive D.
Nacos start：
Double-click startup.cmd in the bin directory and it will flash back, that is, the startup failed;
Use the command to start: startup.cmd -m standalone, An error message appears
D:\Program Files (x86)\nacos-server-2.1.1\nacos\bin>startup.cmd -m standalone
"nacos is starting with standalone"
There should be no \nacos-server-2.1.1\nacos"\logs\java_heapdump.hprof -XX:-UseLargePages" at this point.
The first solution: unzip Nacos to a directory does not contain non-English and numbers, Command line started successfully
Second solution: Open startup with editor, Comment out the content shown below：
rem if %MODE% == "cluster" (
rem echo "nacos is starting with cluster"
rem if %EMBEDDED_STORAGE% == "embedded" (
rem set "NACOS_OPTS=-DembeddedStorage=true"
rem )
rem set "NACOS_JVM_OPTS=-server -Xms2g -Xmx2g -Xmn1g -XX:MetaspaceSize=128m -XX:MaxMetaspaceSize=320m -XX:-OmitStackTraceInFastThrow -XX:+HeapDumpOnOutOfMemoryError -XX: HeapDumpPath=%BASE_DIR%\logs\java_heapdump.hprof -XX:-UseLargePages"
rem )Not sure if this solution will cause other problems, but it starts fine
onnx error:
import onnx
Traceback (most recent call last):
File "torch2onnx.py", line 3, in
import onnx
File "/home/dy/anaconda3/envs/torch/lib/python3.6/site-packages/onnx/__init__.py", line 5, in
from .onnx_cpp2py_export import ONNX_ML
ImportError: /home/dy/anaconda3/envs/torch/lib/python3.6/site-packages/onnx/onnx_cpp2py_export.cpython-36m-x86_64-linux-gnu.so: undefined symbol: _ZN6google8protobuf7Message17CopyWithSizeCheckEPS1_RKS1_Solution:
git clone https://github.com/onnx/onnx.git
cd onnx
git submodule update –init –recursive
# Optional: prefer lite proto
export CMAKE_ARGS=”-DONNX_USE_PROTOBUF_SHARED_LIBS=ON”
export CMAKE_ARGS=-DONNX_USE_LITE_PROTO=ON
pip install -e .