IOS upgrade to xcode13 simulator running error

Xcode13 running simulator reports an error and the real machine is normal

building for iOS Simulator, but linking in object file built for iOS, xxxx for architecture arm64

Solution here is only a real and effective solution of my own

build settings -> Validate workspace (set to yes)

Set validate workspace to yes, and then run the simulator. The simulator really runs

FAILED: esp-idf/mbedtls/x509_ crt_ Solutions to bundle error reporting and information sources

When compiling a project with esp-idf, the following errors are encountered:

FAILED: esp-idf/mbedtls/x509_crt_bundle
cmd.exe /C "cd /D C:\Users\yahsa\Desktop\NTU\FYP\ESP_Workspace\blink\build\esp-idf\mbedtls && C:\Users\yahsa\esp.espressif\python_env\idf4.3_py3.8_env\Scripts\python.exe C:/Users/yahsa/esp/esp-idf/components/mbedtls/esp_crt_bundle/ --input C:/Users/yahsa/esp/esp-idf/components/mbedtls/esp_crt_bundle/cacrt_all.pem -q" Invalid certificate in C:/Users/yahsa/esp/esp-idf/components/mbedtls/esp_crt_bundle/cacrt_all.pem
Invalid certificate
ninja: build stopped: subcommand failed.

This problem is because cacrt_ A certificate in the all.pem file recently expired (September 30), resulting in the failure of compiling the project.

The solution is to enter this command build before compiling the project, enter the menuconfig for project configuration, enter the certificate bundle setting according to the following path, and cancel the enable trusted root certificate bundle option, that is, the trusted root certificate bundle will not be enabled in this project.

(Top) > Component config > mbedTLS > Certificate Bundle-> Enable trusted root certificate bundle

Using esp-idf plug-in in vscode is the same method. Open the project and click the gear at the bottom left ⚙ Icon for engineering configuration.

Solution information source – GitHub link

Error in installing demjson in Python 3

The following error occurs when Python 3 installs demjson 2.2.4

error in demjson setup command: use_2to3 is invalid

Since demjson 2.2.4 is compatible with python2 and python3, some code needs to be converted when the installation environment is python3

Setuptools no longer supports 2to3 builds from version 58.0.0, so demjson 2.2.4 is no longer available after installation,

It can be solved by demoting the version of setuptools

pip install --upgrade setuptools==57.5.0

Solve the problem of JS using JSX syntax to report errors in vite react project


During the vite test of stock items, it is found that many stock (old) items directly write JSX syntax in JS, and a lot of problems will be thrown when vite is used to start failed to parse source .

It’s not too much trouble to run a script to modify the file type in batch. This is a solution.

In order to get to the bottom of the matter and access vite for the lowest cost of stock projects, try to avoid modifying the business code. We have to find another way to solve it.

The screenshot of error reporting is as follows

Recurrence problem

Initialize demo project

# npm 6.x
npm init [email protected] my-react-app --template react-ts

# npm 7+, extra double-dash is needed:
npm init [email protected] my-react-app -- --template react-ts

# yarn
yarn create vite my-react-app --template react-ts

The contents are as follows

├── index.html
├── package.json
├── src
|  ├── App.css
|  ├── App.tsx
|  ├── favicon.svg
|  ├── index.css
|  ├── logo.svg
|  ├── main.tsx
|  └── vite-env.d.ts
├── tsconfig.json
└── vite.config.ts


npm run dev

The page is normal. Next, modify app. TSX to app. JS

You will get the above error report


    Vite will do the dependent pre build at startup

    pre built , runtime only performs syntax conversion between JSX and TSX by default. Will not do JSX syntax conversion for JS.


    Modify the configuration that depends on the pre build

    Use the Babel plug-in @ Babel/plugin transform react JSX , and let vite convert JS files at runtime

Add a little configuration to the configuration file as described in the document

export default defineConfig({
  optimizeDeps: {
    entries: [],

By reading the documentation of @ vite/plugin react , we found that it supports incoming Babel plug-ins

npm i @babel/plugin-transform-react-jsx

Add plug-in

import { defineConfig } from 'vite'
import react from '@vitejs/plugin-react'

export default defineConfig({
  plugins: [react({
      babel: {
        plugins: ['@babel/plugin-transform-react-jsx'],

Start the verification again and an error is found

The reason is that react is not introduced into app.js. Let’s introduce it

import React,{ useState } from 'react'

be accomplished


Two treatment schemes

    File suffix JS = & gt; jsx

    Modify the dependency pre build configuration and add Babel plug-in @ Babel/plugin transform react JSX

The second method will affect the startup speed of the project to a certain extent. Readers can pick the scheme according to the actual project situation


Welcome to share/exchange some problems and lessons learned when accessing vite in the development process in the comment area

Source address

[azure application service] the application deployed under the app service reports an error out of memory

Problem description

After the app is deployed to the app service, an out of memory error is encountered.


Error message: GetData   Error:, Exception of type ‘System.OutOfMemoryException’ was thrown.,

at System.IO.MemoryStream.set_ Capacity(Int32 value)

at System.IO.MemoryStream.EnsureCapacity(Int32 value)

at System.IO.MemoryStream.Write(Byte[] buffer, Int32 offset, Int32 count)

at OfficeOpenXml.Packaging.ZipPackage..ctor(Stream stream)

at OfficeOpenXml.ExcelPackage.ConstructNewFile(String password)

at OfficeOpenXml.ExcelPackage..ctor(FileInfo newFile)

at MyLife.Utility.ExcelHelper.LoadDataTableFromFile(String fileName)

at MyLife.Serivces.GetData()


2021-09-12 05:19:57.0362 | Error | HCPService-StartPreprocessing-Exception of type ‘System.OutOfMemoryException’ was thrown.-

2021-09-12 05:19:57.0756 | Error | An unhandled exception has occurred while executing the request. System.OutOfMemoryException: Exception of type ‘System.OutOfMemoryException’ was thrown.

Problem solving

In the case of oom error at the beginning of deployment, it means that the memroy of the current pricing layer is not enough to meet the operation of the application. However, the memory of different pricing layers of APP service is different. The lowest free layer has 1g ram and the highest can reach 14g.

  (Source : )  


If the memory limitation of the pricing layer is excluded, another important factor is the platform setting of APP service.

App service supports 32-bit and 64 bit platform systems. Therefore, if the default setting is 32-bit operating system, it only supports 4G memory at most. In order to make the application use the maximum memory and not waste the ram resources of APP service, when facing the problem of oom, modify the 64 bit platform bit of APP service at the first time. If oom still occurs, you can consider upgrading the pricing layer of APP service.




When hive processes data, it cannot run directly and reports an error: execution error, return code 2 from

terms of settlement:



Error reason:

The memory space of the namenode is not enough, and the remaining memory space of the JVM is not enough, which is caused by the operation of a new job


Reference link:


Error: vs2015 does not set the object reference to the instance of the object

Problem Description:

Operating environment:

  > win10

  > vs2015 update3

  > qt 5.9.1

An error occurs when opening the. Pro project of QT using vs2015  

Vs2015 does not set an object reference to an instance of an object

Problem analysis:

The environment variable of vs2015 should be modified

Problem solving:

Restore/reset vs2015 environment


1. Use the developer command line of vs2015 to enter:   devenv.exe  /Resetsettings (the problem is not solved)

2. Uninstall QT plug-in, delete vs configuration folder, and reinstall QT plug-in. (problem solving)

2-1. Uninstall QT plug-in









2-2. Delete

      -> C: \ users \ username \ appdata \ local \ Microsoft \ VisualStudio\

All folders under path

2-3. Reinstall QT vsaddin plug-in



Error: No valid exports main found for ‘/Users/work/company_fc/a/node_modules/colorette'”

Error: No valid exports main found for ‘/Users/work/company_ fc/a/node_ modules/colorette

Prompt problem encountered while installing dependency



Cause analysis:

The node version may be incorrect

The default version of the current node is 13.3.0. Switch to version 12.14.1 and start normally.


Generally, for old projects, it is necessary to switch to the lower version of node

However, if you don’t want to uninstall the original high version and want to use the low version, NVM is required at this time

reference resources: 44954172/article/details/104260612

If NVM is installed, simply

 nvm use 12.14.1


Error attempting to get column ‘xxx’ from result set. Cause: java.sql.sqlexception: unable to convert to internal representation. Error resolution during Oracle database query

Overall error log details:

Org.springframework.jdbc.uncategorized sqlexception: error attempting to get column ‘xxx’ from result set. Cause: java.sql.sqlexception: unable to convert to internal representation
; uncategorized SQLException; SQL state [99999]; error code [17059]; Cannot convert to internal representation; Nested exception is java.sql.sqlexception: cannot convert to internal representation

There are many errors that can lead to this problem. Let me say that I made the error because I used the in the Lombok plug-in  @ Builder   This annotation

The first solution is to kill this annotation. When assigning an object, you can directly xxx.setxxx;

The second solution is to add these two annotations @ allargsconstructor on Lombok    @ NoArgsConstructor   Add a construction method that does not participate in all parameters,

Simply put, @ builder is added to mybatis to query without parameters   This annotation results in the absence of a parameterless structure, resulting in an error.


Summary, problems

Solution 1: directly kill the @ builder annotation on the entity class

Solution 2: add @ allargsconstructor @ noargsconstructor to the entity class   annotation