Category Archives: Error

[Solved] nvrtc: error: failed to load builtins for compute_70

mxnet.base.MXNetError: Traceback (most recent call last):
File “src/operator/fusion/fused_op.cu”, line 647
MXNetError: Check failed: compileResult == NVRTC_SUCCESS (7 vs. 0) : NVRTC Compilation failed. Please set environment variable MXNET_USE_FUSION to 0.
nvrtc: error: failed to load builtins for compute_70.
Solution:
export MXNET_USE_FUSION=0

Error-Do not use “//@ts-ignore“ because it alters compilation errors [How to Solve]

When writing code using ts, in some cases, such as third-party library objects, we want to add some attributes and confirm that it is OK, but an error will be reported during TS check, resulting in failure to compile and run normally:

By adding//@TS-ignore, we tell ts that the statement does not check the type problem. At this time, it can be compiled normally. However, the comment//@TS-ignore is marked in red, which is very uncomfortable:

We can eliminate this prompt by modifying the .Eslintrc.JS file:

module.exports = {
	...
	rules: {
		...
		"@typescript-eslint/ban-ts-comment": "off",
	}
}

Clear yum Cache Error: rpmdb: Thread/process 24307/140520328255392 failed: Thread died in Befkeley DB library

Error prompt after executing the command:

[root@redhat]# yum clean all
rpmdb: Thread/process 24307/140520328255392 failed: Thread died in Befkeley DB library
error: db3 error (-30974) from dbenv-›failchk: DB_RUNRECOVERY: Fatal error, run database
recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open Packages database in /var/lib/rpm
CRITICAL: yum.main:

Error: rpmdb open failed

#Rpmdb: thread/process 24307/140520328255392 failed: thread died in befkeley DB Library
# error: db3 error (- 30974) from dbenv – › failchk: DB_ Runrecovery: fatal error, running database recovery
# error: unable to open package index using db3 – (- 30974)
# error: unable to open packages database in/var/lib/rpm
# key: yum.main:
#
# error: rpmdb open failed

In this case, the RPM database is damaged, which makes the yum and RPM related commands unusable. The above also prompts/var/lib/rpm, which is the path where the temporary files of the RPM database are located.

Solution:

Rebuild RPM database

#Go to the path where rpmdb is located
cd /var/lib/rpm/
#List related files to find __db.*
ls
#Delete or move the rpmdb file, I created a new directory and moved the file
mkdir old
mv _db.* old/
#Rebuild the rpm database after completion
rpm --rebuilddb

After the reconstruction is completed, execute Yum clean all again to solve the problem

[Solved] java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.internal.ws.api.BindingID

Error Messages:

16:47:56.249 [http-nio-8099-exec-9] ERROR invoking [Service:sys.login:public abstract java.lang.String com.icitic.sys.api.login.LoginService.jumpUrl(java.lang.String,ja
va.lang.String)] failed c.i.c.s.internal.ServiceRegistry
java.lang.NoClassDefFoundError: Could not initialize class com.sun.xml.internal.ws.api.BindingID
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseBinding(RuntimeWSDLParser.java:445) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parseWSDL(RuntimeWSDLParser.java:342) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:157) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:120) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:258) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:221) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.client.WSServiceDelegate.<init>(WSServiceDelegate.java:169) ~[na:1.7.0_79]
at com.sun.xml.internal.ws.spi.ProviderImpl.createServiceDelegate(ProviderImpl.java:101) ~[na:1.7.0_79]
at javax.xml.ws.Service.<init>(Service.java:77) ~[na:1.7.0_79]

 

Solution:

the solution is to get rid of saaj-impl-1.3.2.jar and saaj-api-1.3.jar libraries from OUR_SERVICE_APP and’force’ it to use rt.jar / JDK implementations instead.

The solution is to remove the saaj-impl-1.3.2.jar and saaj-api-1.3.jar libraries from our _service_application and “force” it to use rt.jar/JDK.

However, since these two jar packages are provided by other third-party applications, they cannot be deleted. It is recommended to develop by writing a custom ClassLoader, and load it into the specified JAR first through the custom ClassLoader, and delegate the rest to the parent class loader to load.

[Solved] jmeter Start Error: Uncaught exception in thread Thread[AWT-EventQueue-0,6,main]

new downloaded jmeter, starting reward:

First, you can see ERROR o.a.j.JMeter: Uncaught exception in thread Thread

2021-10-13 20:27:42,010 INFO o.j.r.PluginManager: Plugins Status: [jpgc-plugins-manager=1.6, jmeter-core=5.4.1, jmeter-ftp=5.4.1, jmeter-http=5.4.1, jmeter-jdbc=5.4.1, jmeter-jms=5.4.1, jmeter-junit=5.4.1, jmeter-java=5.4.1, jmeter-ldap=5.4.1, jmeter-ldap=5.4.1, jmeter-ldap=5.4.1 eter-mail=5.4.1, jmeter-mongodb=5.4.1, jmeter-native=5.4.1, jmeter-tcp=5.4.1, jmeter-components=5.4.1]
2021-10-13 20:27:54,241 INFO o.a.j.s.FileServer: Default base=’/Users/kidd’
2021-10-13 20:27:54,243 INFO o.a.j.a.Load: Loading file: /Users/kidd/jmetertesting_file/View Results Tree.jmx
2021-10-13 20:27:54,244 INFO o.a.j.s.FileServer: Set new base=’/Users/kidd/jmeteretereter testing_file’
2021-10-13 20:27:54,383 INFO o.a.j.s.SaveService: Testplan (JMX) version: 2.2. Testlog (JTL) version: 2.2
2021-10-13 20:27:54,391 INFO o.a.j.s.SaveService: Using SaveService properties version 5.0
2021-10-13 20:27:54,392 INFO o.a.j.s.SaveService: Using SaveService properties file encoding UTF-8
2021-10-13 20:27:54,394 INFO o.a.j.s.SaveService: Loading file: /Users/kidd/jmetertesting_file/View Results Tree.jmx

*

Resistance: reconstruction, issue is completely resolved.

*

*

How to Solve gltf format error after Draco compression

The error message of Google Chrome is as follows:
Uncaught SyntaxError: Unexpected token'<‘

When loading the draco algorithm, the file path was also quoted according to the online method, and the result was an error. I used Parcel to package and build.
dracoLoader.setDecoderPath(” /three/examples/js/libs/draco/gltf/ “);

The solution is to put the files in this directory in static files. Static file directory: /static/gltf

The 3D model is a model built using 3dmax and exported to fbx format files. Use FBX2glTF to convert to gltf

npm install -g FBX2glTF

Then enter node_global\node_modules\fbx2gltf\bin\Windows_NT directory
> .\FBX2glTF.exe -i .\lou.FBX -b -d

 

Click to view code

 

Perfect solution, no error is reported, remember to add a slash before and after gltf, if you do not add it, you will still report an error

[Solved] Swagger Error: Failed to start bean ‘documentationPluginsBootstrapper’

Error cause: it may be caused by version mismatch. My spring boot is 2.6.0, but the spring cloud version needs to be compared in this way and cannot be degraded, so it is configured in this way

POM dependency

 <parent>
	 <groupId>org.springframework.boot</groupId>
	 <artifactId>spring-boot-starter-parent</artifactId>
	 <version>2.6.0</version>
	 <relativePath/> <!-- lookup parent from repository -->
</parent>
<dependencies>
	<dependency>
		<groupId>io.springfox</groupId>
		<artifactId>springfox-swagger2</artifactId>
		<version>2.9.2</version>
	</dependency>
	<dependency>
		<groupId>io.springfox</groupId>
		<artifactId>springfox-swagger-ui</artifactId>
		<version>2.9.2</version>
	</dependency>
	<dependency>
		<groupId>com.google.guava</groupId>
		<artifactId>guava</artifactId>
		<version>25.1-jre</version>
	</dependency>
</dependencies>

Startup class:

@SpringBootApplication
@EnableDiscoveryClient
@EnableWebMvc // Comment out
public class UploadServiceApplication {

    public static void main(String[] args) {
        SpringApplication.run(UploadServiceApplication.class, args);
    }

}

This configuration may cause the UI page of swagger to fail to open, so the following configuration is required:

import org.springframework.context.annotation.Configuration;
import org.springframework.util.ResourceUtils;
import org.springframework.web.servlet.config.annotation.ResourceHandlerRegistry;
import org.springframework.web.servlet.config.annotation.WebMvcConfigurerAdapter;

@Configuration
public class WebMvcConfigurer extends WebMvcConfigurerAdapter {

    /**
     * Accessing static resources
     */
    @Override
    public void addResourceHandlers(ResourceHandlerRegistry registry) {
        /**
         * SpringBoot autoconfiguration itself does not map the /swagger-ui.html
         * This path is mapped to the corresponding directory META-INF/resources/
         * Use WebMvcConfigurerAdapter to publish the static files of swagger;
         */
        registry.addResourceHandler("swagger-ui.html")
                .addResourceLocations("classpath:/META-INF/resources/");

        registry.addResourceHandler("/webjars/**")
                .addResourceLocations("classpath:/META-INF/resources/webjars/");
        //Map all /static/** accesses to the classpath:/static/ directory
        registry.addResourceHandler("/static/**").addResourceLocations(ResourceUtils.CLASSPATH_URL_PREFIX +"/static/");
        super.addResourceHandlers(registry);
    }
}

[Solved] HBuilderX Run uniapp Error: SassError: Invalid CSS after “}”: expected selector, was “,”

After the hbuilderx editor is updated to the latest version, sass reports an error. If you switch to the previous version, there will be no error

Error message:

Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Invalid CSS after " }": expected selector, was ","

Problems and solutions:

There is a problem with CSS writing. There may be a deviation between the prompted position and the actual position

The verification of the new version of hbuilderx editor is more strict. Just remove the comma at the corresponding position

[Solved] The activity must be exported or contain an intent-filter

The following error occurred while testing an activity:

(1) This is generally because this activity is not launcher activity, nor is it set to Android: exported = "true"

*The activity as the startup page in Android must be set to intent filter or exported in mainfest

Solution: you can set Android: exported = "true" on the activity configuration in androidmanifest.xml, or set intent filter

As follows:

        <!--    activity Set exported as true    -->
        <activity android:name=".activity.POStockInActivity" android:exported="true"/>

        <!--    activity set intent-filter    -->
        <activity android:name=".activity.LoginActivity" >
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>

(2) In another case, after modifying launcher activity, run it directly with the shortcut key Shift + F10, which will continue to run with the previous activity

Solution: do not use shortcut keys to start. Right-click the newly set activity and click ‘run xxxactivity’ to run it

*The following figure shows how to modify the launcher activity. You can see that after modifying the launcher activity, you will be warned. You need to set this activity to exported or set intent filter:

The back-end receives the field validation errors passed by the front-end: invalid validation tag on field ‘username’

background

Received username, string length greater than or equal to 2 bits, incorrect use

Username string ` validate:"required,min=2," `

The console prompts that the validation label on the error information field “username” is invalid

After finding the validate document, the correct import method is used. After using the string format restrictions such as min, the require is no longer used

	Username string ` validate:"min=0,max=5" `  //use requier instead of min