Category Archives: Error

[Solved] Module build failed: from ./node_modules/mini-css-extract-plugin/dist/loader.js

When building the project today, the following error is reported:

I always thought it was a problem with the node-sass and sass loader versions, and it was not possible to reinstall these two plug-ins;

Later, it was found that the version of the element was updated today, and node-sass was changed to dart sass, resulting in some syntax errors in CSS, such as/deep/can’t be used, so it has to be replaced with:: v-deep;

Problem-solving:

1. The version number of element UI can be fixed to 2.15.6 or other versions below 2.15.7;

2.node-sass change into Dart sass, but some CSS syntax in it should be modified, which is troublesome.

The first method is recommended

Flutter ListView Error: RenderBox was not laid out: RenderViewport#680c1 NEEDS-LAYOUT NEEDS-PAINT

RenderBox was not laid out: RenderViewport#680c1 NEEDS-LAYOUT NEEDS-PAINT

When using listview.builder() layout, this error may be reported if it is nested in row or column. The reason is that the size is not specified for the listview, so a sizedbox or container should be set outside the listview, and then a height should be specified. Or if you want to adapt the height, set a flexible or expanded.

return Scaffold(
      body: SafeArea(
        left: false,
        right: false,
        child: Container(
          padding: EdgeInsets.fromLTRB(0, 12, 0, 36),
          child: Column(children: [
	  ......
	  other components
	  ......
	    Expanded(
                child: Container(
              child: ListView(
                  children: []
                    ..add(row('Anywhere'))
                    ..add(or())
                    ..add(row('Country'))
                    ..add(row('State'))),
            )),
	  ......
	  other components
	  ......
	  ]))));

If the screen is still blank, try setting shrinkwrap to true and physics to neverscrollablescrollphysics()

ProXmoX VE Update apt-get update Error [How to Solve]

Use the default apt update source of proxmox ve. After clicking “Refresh” on the web update management panel, an error will be displayed. At this time, because the default update source is the subscription of proxmox ve Enterprise Edition, if we do not purchase the subscription, we will prompt the signature error, which makes the apt update fail. The solution is very simple. Just replace the software source. Proxmox officially provides sources corresponding to different versions, which can be selected according to your own situation.

The principle of the three solutions found online is to replace the software source. The three methods are:

Method 1:

vim /etc/apt/sources.list.d/pve-enterprise.list

Note out:

# deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

then:

echo "deb http://download.proxmox.com/debian/pve stretch pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list

Method 2:

Edit sources.list and enter the following command:

nano /etc/apt/sources.list

Add at the bottom after opening:

deb http://download.proxmox.com/debian buster pve-no-subscription

Then press Ctrl + O to save and Ctrl + X to exit.

Edit pve-enterprise.list and enter the following command:

nano /etc/apt/sources.list.d/pve-enterprise.list

Comment out   deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise

Then save and exit.

Method 3:

Back up the original sources.list

cp /etc/apt/sources.list /etc/apt/sources.list.bak

Replace the contents of sources.list with the following official non feeds

deb http://ftp.debian.org/debian buster main contrib
deb http://ftp.debian.org/debian buster-updates main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve buster pve-no-subscription

# security updates
deb http://security.debian.org buster/updates main contrib

Comment out the original URL in /etc/apt/sources.list.d/pve-enterprise.list

# deb https://enterprise.proxmox.com/debian/pve buster pve-enterpris

Then execute the following command to upgrade normally.

apt update && apt dist-upgrade

After the upgrade, reboot and restart the physical server, execute pveversion – V to check the latest software version.

[Solved] Angular creates component error: More than one module matches. Use skip-import option to skip importing the component into the closest module. 

ng g c new-component-name

Your global Angular CLI version (12.2.9) is greater than your local version (9.1.7). The local Angular CLI version is used.

To disable this warning use “ng config -g cli.warnings.versionMismatch false”.

More than one module matches. Use skip-import option to skip importing the component into the closest module.

Solution:

ng g c new-component-name --module app

Your global Angular CLI version (12.2.9) is greater than your local version (9.1.7). The local Angular CLI version is used.
To disable this warning use “ng config -g cli.warnings.versionMismatch false”.More than one module matches. Use skip-import option to skip importing the component into the closest module.

Spring Error: ‘artifactId‘ with value ‘xxxx‘ does not match a valid id pattern.

Error: ‘artifactid’ with value ‘XXXX’ does not match a valid ID pattern.

Notes:

Error reason: POM file is in GAV format, UN-English characters or spaces are not allowed. Just use underscores, numbers and letters to change the artifactid attribute value to the required form .1 <artifactId> 2020_11_15

Container Cannot Find bean, Field usersMapper in com.imooc.impl.UserServiceImpl required a bean of type ‘com.imooc.mapper.UsersMapper’ that could not be found.

Startup report: no relevant entity class error found

Description:

Field usersMapper in com.imooc.impl.UserServiceImpl required a bean of type 'com.imooc.mapper.UsersMapper' that could not be found.

The injection point has the following annotations:
	- @org.springframework.beans.factory.annotation.Autowired(required=true)


Action:

Consider defining a bean of type 'com.imooc.mapper.UsersMapper' in your configuration.

The reason is that the package range of the startup class scanning needs to be annotated with the package path corresponding to the error reporting class

import tk.mybatis.spring.annotation.MapperScan;

@SpringBootApplication
@MapperScan("com.imooc.mapper")
public class Application {
    public static void main(String[] args) {
        SpringApplication.run(Application.class,args);
    }
}

SSL certificate problem in Git: unable to get local issuer certificate error

This is because when you access git remote warehouse through HTTPS, GIT will report an error if the SSL certificate on the server is not authenticated by a third-party authority. The reason is that unknown unsigned certificates mean that there may be a great risk. The solution is to turn off SSL verify in Git with the following command

This command affects the current user of the system

git config –global http.sslverify false

If you want to set all users globally, you can change it to this:

git config –system http.sslverify false

If you only want to set for the current warehouse, you can execute it under the warehouse directory to be modified

git config http.sslverify false

Modified git configuration C: \ program files \ git \ etc:

 

 

Turn: https://www.cnblogs.com/jaxu/p/12027839.html

 

SLF4J: Detected both log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on the class path

If the log jar packages referenced by Maven dependent components conflict, an error will be reported:

“SLF4J: Detected both log4j-over-slf4j.jar AND bound slf4j-log4j12.jar on the class path”

 

resolvent:

In specific dependencies & lt; dependency>& lt;/ dependency> Add the following contents:

<exclusions>
    <exclusion>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-log4j12</artifactId>
    </exclusion>
</exclusions>

If you still report an error, you can replace it with the following:

<exclusions>
    <exclusion>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-log4j12</artifactId>
    </exclusion>
    <exclusion>
        <groupId>log4j</groupId>
        <artifactId>log4j</artifactId>
    </exclusion>
</exclusions>

*After adding content, refresh maven, otherwise the running program will still report an error!

 

There are many ways to operate in the idea interface:

a. Click reload all Maven projects on the Maven interface

b. Right click the item name  -& gt; Maven -> Reload project

c. Right click the pom.xml file  -& gt; Maven -> Reload project

d. Right click – & gt; in the pom.xml editing interface; Maven -> Reload project