Please refer to the latest official documents;
Modify the solution configuration file;
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"dev": " webpack serve --open",
"build": "webpack"
},
Welcome to add~
When creating a project, vuecli4 always fails to report an error. Command failed: NPM install — loglevel error
installing the Taobao image is also an error.
the way to find it on the Internet
NPM install chromedriver — chromedriver_ cdnurl= http://cdn.npm.taobao.org/dist/chromedriver
After completing the operation, re create the project Vue create****
My installed version is as follows:
node – V
v14.16.1
npm -v
6.14.2
vue -V
@vue/cli 4.5.12
npm install chromedriver –chromedriver_ cdnurl= http://cdn.npm.taobao.org/dist/chromedriver
vue create
So it worked
There is no space after the comma, as shown in the figure:
Today’s unhappiness is that reload (sys) can’t be used
prompt NameError: name ‘reload’ is not defined
import sys
reload(sys)
sys.setdefaultencoding("utf-8")
This one instead
import importlib
importlib.reload(sys)
Today, when I imported the face recognition model built by keras into the Django framework to run, the system reported oseeeor, and the display file does not exist, but I can run it normally when I run the model alone. Finally, we get the following two solutions.
Solution
Method 1
This method is a problem encountered by others when I was looking for a solution, although it did not solve my problem:)
it may be that the environment of the framework was destroyed after the model was imported, and the file path was changed, which can be solved by re installing py
pip3 uninstall h5py
pip3 installl h5py
Method 2: path problem
It seems that this solution has not been mentioned, but it has solved my problem
although the relative path can be used to run the model alone, it should be changed to absolute path under Django. As for why, I’m not sure.
Specifically, for example, y. astype (int). Astype (float)
If we find the error can’t open when we install Oracle Software display:127.0.0.1 :0.0 ， probably Display can’t find the graphic link library corresponding to 127.0.0.1, so you need to use export display =: 0.0 to make the system automatically find the matching graphic link library,
And modify the overall settings in/home/Oracle /. Bash_ The display parameter in the profile file is =: 0.0.
export DISPLAY= localhost:10.0
Use the xclock command to test the result, if it still reports an error.
Maybe it’s the root environment when the GUI logs in, and then you convert it to an Oracle environment, such as su – oracle ， This may also lead to this error. Error: Can’t open display:127.0..0.1 :0.0
Suppose that the Linux account for installing Oracle Software is Oracle, Then we need to log in to the GUI directly as an Oracle user instead of switching to Oracle after logging in as root, We can set the VNC corresponding to the Oracle user (to install the user environment settings of Oracle) ， Then login VNC as Oracle user to install.
If there is a libxp type error, it may be that the RPM package of libxp is not installed.
Nextjs program released, reported a pile of errors
18 verbose node v14.11.0
19 verbose npm v6.14.8
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] build: `next build`
22 error Exit status 1
23 error Failed at the [email protected] build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]Maybe due to the version update,
the solution is to install it again. It is recommended to empty all the previous ones
rm -rf node_modules
rm package-lock.json
npm cache clear --force
npm install
Problem phenomenon: continuous clicking causes the fusing of hystrix
The solution on the Internet is to adjust the maxqueuesize property. After the modification, the following error still appears. Why does the maxqueuesize property not work?Later, by checking the official documents, we found that hystrix also has a queuesizerejectionthreshold property, which controls the maximum threshold of the queue. By default, hystrix only has five, Therefore, even if we set the maxqueuesize value to be larger, it will not work. Both properties must be configured at the same time
could not be queued for execution and no fallback availableSolution
hystrix:
threadpool:
default:
coreSize: 200 #Maximum number of threads for concurrent execution, default 10
maxQueueSize: 1000 #Max queue size of BlockingQueue, default -1
queueSizeRejectionThreshold: 800 #Even if maxQueueSize is not reached, the request will be rejected after reaching the value of queueSizeRejectionThreshold：
Aspecj cannot intercept method annotations on an interface
Aspecj can’t intercept the method annotation on the interface, it can only act on the method of the implementation class. At this time, it needs to use methodinterceptor to implement.
@Target(ElementType.METHOD)
@Retention(RetentionPolicy.RUNTIME)
@Documented
@Inherited
public @interface AopTest {
}
Interface
public interface TestAOPI {
@AopTest
public String test();
}
Implementation class 1
@Service
public class TestAOPService implements TestAOPI{
@Override
public String test() {
return "service";
}
}
Implementation class 2
@Service
public class TestAOPService2 implements TestAOPI{
@AopTest
@Override
public String test() {
return "service";
}
}
Aspecj (partially valid)
If and only if the @ aoptest annotation is added to the method of the implementation class, it will take effect (implementation class 2), but implementation class 1 will not
@Aspect
@Configuration
public class AopTestAspect {
/**
* Identifies the method annotated with OperationLog
*/
@Pointcut("@annotation(com.example.demo1.config.AopTest)")
public void methodHasAopTestAnnotation() {
}
@Around("methodHasAopTestAnnotation()")
public Object doAround(ProceedingJoinPoint joinPoint) throws Throwable {
System.out.println("aop!!!");
return joinPoint.proceed();
}
}
Solution
It needs to be changed to the following way by manual
@Configuration
public class AopTestConfiguration {
@Bean
public Advisor methodPointcutAdvisor() {
AopTestMethodPointcutAdvisor advisor = new AopTestMethodPointcutAdvisor();
advisor.setAdvice(new AopTestInterceptor());
return advisor;
}
class AopTestInterceptor implements MethodInterceptor {
@Override
public Object invoke(MethodInvocation invocation) throws Throwable {
String name = invocation.getMethod().getName();
System.out.println("==============" + name + " before ================");
Object result = invocation.proceed();
System.out.println("==============" + name + " after ================");
return result;
}
}
public class AopTestMethodPointcutAdvisor extends StaticMethodMatcherPointcutAdvisor {
@Override
public boolean matches(Method method, Class<?> targetClass) {
// Implementing a class method with a target annotation on it
if(method.isAnnotationPresent(AopTest.class)){
return true;
}
// The method has a corresponding interface method and the interface method is annotated
Class<?>[] interfaces = method.getDeclaringClass().getInterfaces();
for (int i = 0; i < interfaces.length; i++) {
Method[] methods = interfaces[i].getMethods();
for (int j = 0; j < methods.length; j++) {
if(methods[j].getName().equals(method.getName())){
return methods[j].isAnnotationPresent(AopTest.class);
}
}
}
return false;
}
}
}
After Nacos started, the client worker log was printed all the time
Phenomenon
Print the clientworker log all the time
2020-08-24 00:57:30.977 INFO [12932] --- [.cn_8848-public] c.a.n.client.config.impl.ClientWorker : [fixed-nacos.itlym.cn_8848-public] [data-received] dataId=common.yml, group=DEFAULT_GROUP, tenant=public, md5=8c191cace81179b01fb745b5d027c1c8, content=xxx
2020-08-24 00:57:30.989 INFO [12932] --- [.cn_8848-public] c.a.n.client.config.impl.ClientWorker : [fixed-nacos.itlym.cn_8848-public] [data-received] dataId=sms-center.yml, group=DEFAULT_GROUP, tenant=public, md5=f12bc945ba0c1d39f3dea2e0977db712, content=xxx
...
Cause analysis
Root cause
Having seen the source code of Nacos before, Nacos will check whether the configuration items are consistent with the server configuration items every 10ms. If not, it will pull the latest configuration from the server therefore, if the MD5 algorithms of Nacos client and Nacos server are different, it will lead to misjudgment, thus constantly refreshing and printing the client worker logs.
Direct cause
My Nacos server is 1.3, and the client uses spring cloud Alibaba. Version . Click to find that the Nacos client version is 1.2
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-alibaba-dependencies</artifactId>
<version>2.2.1.RELEASE</version>
<type>pom</type>
<scope>import</scope>
</dependency>
Here, the
spring-cloud-alibaba-dependencies‘s official website and warehouse have not been updated for a long time, which is easy to make complaints about users and waste a lot of investigation time.
Other possible reasons
The public is set in the namespace. See the Nacos GitHub
At this time, the best way to solve this problem is not to set the namespace. Otherwise, when Nacos releases a new version, it may be 1.4
Solution
Method 1:
Change the version of client and Nacos server to the same, as follows
client:
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-alibaba-dependencies</artifactId>
<version>${spring-cloud-alibaba.version}</version>
<type>pom</type>
<scope>import</scope>
<exclusions>
<exclusion>
<artifactId>com.alibaba.nacos</artifactId>
<groupId>nacos-client</groupId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.alibaba.nacos</groupId>
<artifactId>nacos-client</artifactId>
<version>1.3.2</version>
</dependency>
Method 2:
Because spring cloud Alibaba dependencies leaves the gap of properties specified version (default < nacos.client.version> 1.2.1)
so you only need to add
<properties>
<nacos.client.version>1.2.1</nacos.client.version>
</properties>
Note: if spring cloud starter Nacos config is introduced, it can’t be avoided by this scheme, because ‘spring cloud Alibaba dependencies’ has hard coding problems. When importing, you should actively specify the version.
<dependency>
<groupId>com.alibaba.cloud</groupId>
<artifactId>spring-cloud-starter-alibaba-nacos-config</artifactId>
<version>1.3.0</version>
</dependency>
Method 3 (middleware upgrade scheme suitable for existing system):
Download the Nacos client Version 1.2.1 code, modify its md5util package path to a new one, and then re publish it to the local or private warehouse.
Context has been closed already solution
Error code
With such a piece of code, the context has been closed already error may occur during running, and once it occurs, it will make an error every time it runs in the future.
@Component
public class SpringContextUtil implements ApplicationContextAware {
private static ApplicationContext context = null;
@Override
public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
ApplicationContextExt.context = applicationContext;
}
/**
* This static method allows you to retrieve the desired bean from the Spring context.
*/
public static <T> T getBean(Class<T> cls) {
if (context == null)
throw new IllegalStateException("no application context aviliable.");
try {
return (T) context.getBean(cls); // Wrong!
} catch (BeansException e) {
throw new RuntimeException(e);
}
return (T) null;
}
}
Cause analysis
However, when spring cloud context. Jar is included in the classpath, because the contextrefresher class will close the old context when the context is refreshed, so that the context in the static class has been closed, so this error will occur.
Trigger exploration
Find out the direct reason. Find out that a jar that you depend on listens to a notification from MQ. When you hear the message to be refreshed, you will refresh the context, which leads to this phenomenon.