When installing graphviz using homebrew, the following errors are reported:
There are two main solutions found on the Internet:
1.brew install cmake
2. Reinstall homebrew
These two solutions did not solve my problem, so I tried to update home brew (brew update) to perfectly solve the above problems.
S32ds uses JLINK debugging to report an error: error in services launch sequence
1、 Solution
2、 Scenario:
Create a new example project and connect JLINK to SWD. Select XXX_ debug_ flash_ JLINK option for debugging. The error interface pops up, as shown in the figure below
3、 Solving process
Use JLINK to connect MCU. Segger’s SWD is connected to the MCU, the red light flashes, and the interface prompts that the connection is successful. Click the debugging button of s32ds, and the JLINK light does not flash. It is suspected that the correlation between s32ds and segger is abnormal, so the path is found and the solution is obtained
If the figure reports an error
solution:
Step 1: set
Step 2: search vetur.validation.template and uncheck
Refer to vrep/vreppython.pdf at main · Hu Xiao max/vrep · GitHub
Because this vrep.py comes with you after installation
Pypi can’t install vrep, so copy it yourself
The reason is that the wrong statement
is added to the modelsim.ini file
There are a lot of mce log we can check from the mcelog file. Indeed, this is a HW issue and some part is defective one, almost is memory. But a lot of vender don’t want to replace it for this is a correctable error. And we can also check this error at ilom (different vendor have different name but almost of them is built by polit 3,4 arch) as bellow.
2021-11-14/20:09:00 ereport.cpu.intel.quickpath.mem_ce@/SYS/MB/P1/D3
count = 0x1
system_component_firmware_versions = (ILOM)5.0.1.28 r140973,(BIOS)38340900
2021-11-14/20:17:57 ereport.cpu.intel.quickpath.mem_ce@/SYS/MB/P1/D3
count = 0x1
system_component_firmware_versions = (ILOM)5.0.1.28 r140973,(BIOS)38340900
—
If you want to disable them for some monitor policy pls check as bellow
Solution:
Machine Check Exception
mce=off
Disable machine check
mce=no_cmci
Disable CMCI(Corrected Machine Check Interrupt) that
Intel processor supports. Usually this disablement is
not recommended, but it might be handy if your hardware
is misbehaving.
Note that you’ll get more problems without CMCI than with
due to the shared banks, i.e. you might get duplicated
error logs.
mce=dont_log_ce
Don’t make logs for corrected errors. All events reported
as corrected are silently cleared by OS.
This option will be useful if you have no interest in any
of corrected errors.
mce=ignore_ce
Disable features for corrected errors, e.g. polling timer
and CMCI. All events reported as corrected are not cleared
by OS and remained in its error banks.
Usually this disablement is not recommended, however if
there is an agent checking/clearing corrected errors
(e.g. BIOS or hardware monitoring applications), conflicting
with OS’s error handling, and you cannot deactivate the agent,
then this option will be a help.
mce=bootlog
Enable logging of machine checks left over from booting.
Disabled by default on AMD because some BIOS leave bogus ones.
If your BIOS doesn’t do that it’s a good idea to enable though
to make sure you log even machine check events that result
in a reboot. On Intel systems it is enabled by default.
mce=nobootlog
Disable boot machine check logging.
mce=tolerancelevel[,monarchtimeout] (number,number)
tolerance levels:
0: always panic on uncorrected errors, log corrected errors
1: panic or SIGBUS on uncorrected errors, log corrected errors
2: SIGBUS or log uncorrected errors, log corrected errors
3: never panic or SIGBUS, log all errors (for testing only)
Default is 1
Can be also set using sysfs which is preferable.
monarchtimeout:
Sets the time in us to wait for other CPUs on machine checks. 0
to disable.
The mcelog is loging to message by default but you want to check this HW issue separately, audit the /etc/mcelog/mcelog.conf as bellow.
Before:
/usr/sbin/mcelog –ignorenodev –syslog –foreground
After：
/usr/sbin/mcelog –ignorenodev –syslog –foreground –logfile=/var/log/mcelog
Now restart the service
#service mcelog restart
You can find the /var/log/mcelog as expected.
Environmental Science:
spring cloud + Mybatis-plus + postgresql
Scenario:
Prompt during table insertion
org.postgresql.util.PSQLException: ERROR: syntax error at or near “current_date”
Causes:
current_ Date() is the method of SQL, current_ Date is the method name
resolvent:
current_ Change date to create_ Date (optional here, not the method name)
Analysis process:
The Error statement in XML file and navigator displays current_ Date is green (keyword color)
Error while loading shared libraries: libmysql.So.16
my personal test is available. Here we only introduce the current environment with libmysqlclient.So.*
Step 1: ldconfig – V | grep MySQL
The red box indicates my Linux environment
Ln – S/usr/lib64/MySQL/libmysqlclient.So.18.0.0/lib/libmysql.So.16
the problem is solved here
The object of set is irreversible
I am adding an error in the path of the form, and then checking URLs
it is found that when the app configures URLs, the [] of URL patterns is written as {}
URL patterns should be a list[].
Then there’s no problem~
Another version problem… I ran into it all. The version of
torchvision is too low, io.read_ Image does not support grayscale images. You can only read three channel color images…
segmentation = mask_to_rle(torchvision.io.read_image(os.path.join(self.root, m['mask']))[0] == 255)
current version
torchvision==0.8.2
Upgraded version
torchvision==0.9.0
Problem solved, yep! Of course, it is possible to solve the problem without upgrading torchvision. You can first convert the gray image into a three channel image, and you can try
(it’s also a reminder. Pay attention to the matching of torch versions)
2021.11.18
When idea starts a new project, a pop-up prompt error is encountered
Error running ‘xxx Application’:Command line is too lang. Shorten command line for Application or aalso for Spring Boot default configuration
Error reason: the springboot project startup command is too long
Solution:
The first method (protest is effective)
Step 1: find the idea/workspace.xml file in the project, and then find <component name="PropertiesComponent"> </component > tag, as shown below
step2：Add a line to the component tag < property name="dynamic.classpath" value="true"/>, as shown below
Restart the project.
Error reporting prompt of Android Studio: error while launching activity
Solution:
Directly follow the following figure:
in this way, you can re-run the project