Category Archives: How to Fix

Failed to upload report – An error has occurred. Please contact your administrator 

ERROR: Error during SonarScanner execution
ERROR: Failed to upload report - An error has occurred. Please contact your administrator
ERROR: 
ERROR: Re-run SonarScanner using the -X switch to enable full debug logging.
[Pipeline] }

View service details

Enter the corresponding sonar installation directory and look at the log below log

web.log   The following error is reported, MySQL

Setting and modifying the maximum MySQL receive

vim /etc/my.cnf

Add a row

max_ allowed_ packet = 2102410240

Restart service

systemctl restart mysqld

If an error is still reported during the execution of sonar, restart sonar,

Failed to load plugin jsdoc: Cannot find module ‘eslint-plugin-jsdoc‘

In the egg project, NPM is installed for the first time   The following errors are reported when the package is:

Oops! Something went wrong! :(

ESLint: 5.16.0.
ESLint couldn't find the plugin "eslint-plugin-jsdoc". This can happen for a couple different reasons:

1. If ESLint is installed globally, then make sure eslint-plugin-jsdoc is also installed globally. A globally-installed ESLint cannot find a locally-installed plugin.

2. If ESLint is installed locally, then it's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

     npm i eslint-plugin-jsdoc@latest --save-dev

Path to ESLint package: /Users/***/node_modules/eslint

If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team.

The eslint does not work normally, and when the file does not comply with the eslint rules, an error is reported in the console log as follows:

Failed to load plugin jsdoc: Cannot find module 'eslint-plugin-jsdoc'....

reason:

When NPM v8.0 installed the project dependency, it did not correctly install the project dependency (eslint config egg) dependency (eslint plugin JSDoc)

solve:

After upgrading NPM to v8.1.2, delete the node in the project_ Modules and package-lock.json, and then reinstall

rm -rf node_modules
rm package-lock.json
npm i

Supplement:

If you have the same error, you can search globally   Eslint plugin JSDoc to locate dependencies with NPM command

➜  *** git:(master) ✗ npm ls eslint-plugin-jsdoc
***@1.0.0 /Users/***
└─┬ [email protected]
  └── [email protected]

Then determine whether to install or upgrade NPM manually or for other reasons.

Error reported when Windows builds docker image: failed to create LLB definition: 403 Forbidden

preface

Use the docker build command to build a mirror: “failed to solve with frontend dockerfile. V0: failed to create LLB definition: unexpected status code [manifests 18.04]: 403 Forbidden”. The specific screenshot of the error is as follows:

resolvent

It happens during the build process. It is an error in the buildkit, considering that the buildkit is still unstable. If you use the docker desktop on MAC/windows, you may also have to disable it in the “docker engine” JSON configuration
docker desktop – & gt; Settings – & gt; Docker engine – & gt; “Features”: {buildkit: true} will “features”: {buildkit: false}

Note that this is not a fix, it is a solution until someone in the docker team implements the correct fix. Please try again when the buildkit is more stable

Reference articles

github issues

Failed to connect to appears after burp suite agent is set

http://www.gstatic.com/generate_ two hundred and four

Burpsuite and browser settings are set normally, but an unknown port appears when capturing packets, and the domain name is unknown.

The reason is whether the upstream system agent is set in the user options of burpsuite, which is generally used for linkage scanning with awvs and Xray. If it is not closed here, it will be impossible to capture packets next time.

 ———

Simple problems are not simple when they are not encountered. Record, share and solve problems.

 

Chunkloaderror caused by deleteoriginalassets: loading chunk * failed error

If you don’t say much, report the error directly:

this error report looks too familiar. After searching online, the general solution is:

1. Record an error in Vue history mode chunkloaderror: loading chunk XX failed net:: err_ Abort 404 (not found) solution

2. Error: loading chunk * failed, Vue router lazy loading error report solution

Follow the example. History, publicpath, onerror, and even the online server. Whatever solution you have, I can’t solve it. There’s no sign that it can be solved. I’m still a local project, and removing lazy loading can’t solve this problem. Why are such errors prompted?

In the end, experienced colleagues have to find the cause of the problem: delete original assets. Finally, just comment it out.

In vue.config.js, it is used to optimize the front-end performance: front-end performance optimization – using gzip compression.

Failed to read artifact descriptor for xxx:jar Missing

Background

I’ve been looking at HBase recently, introducing

        <dependency>
            <groupId>org.apache.hbase</groupId>
            <artifactId>hbase-client</artifactId>
            <version>2.1.3</version>
        </dependency>

Abnormal

Exception thrown: failed to read artifact descriptor for XXX: jar missing

Solution

Delete the org.apache.hbase related files under the local repository to solve the problem

reference resources

https://blog.csdn.net/weixin_ 42204641/article/details/80768905

Front end Vue project operation error module build failed

Scenario Description: when a Vue project of someone else is running on vscode, the download dependency process is normal, and the run dev reports an error. The information is as follows
in many cases, this error is because the node version required for project operation is inconsistent with your local node version. Just switch back to the normal version

Solve host key verification failed [valid]

Host key verification failed

When I wanted to connect to my server on the Mac, I found that there was a problem with my key, so Baidu took a look and made a record.

The first terminal is the picture of the problem, and the second terminal is a code to solve the problem

SSH keygen - R IP address you want to access
SSH keygen - R 192.168.1.5

Reference blog

Springboot startup error failed to configure a datasource 

***************************
APPLICATION FAILED TO START
***************************

Description:

Failed to configure a DataSource: 'url' attribute is not specified and no embedded datasource could be configured.

Reason: Failed to determine a suitable driver class


Action:

Consider the following:
	If you want an embedded database (H2, HSQL or Derby), please put it on the classpath.
	If you have database settings to be loaded from a particular profile you may need to activate it (no profiles are currently active).


Process finished with exit code 1

This error is always reported when springboot starts
my solution:
1. Check whether the Resources folder is configured. Mine was gray before, and it is equipped with


2. Use Maven clean

and start successfully.