Version: MacOS 12.3.1 Monterey
Error message:
crun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
It is generally caused by system update. Enter the following command in the terminal and agree to install after a dialog box pops up.
xcode-select --installAfter installation, reopen the terminal and input the command to operate normally.
JSP Project request.getParameter Error
When running JSP project in IDEA, request.getParameter report error:
Solution:
Add Tomcat dependency package
Step 1
Step 2 (click the dependency plus sign)
Step 3
Step 4
be accomplished
ERROR: ./depthai_sdk is not a valid editable requirement.
Error Messages:
ERROR: ./depthai_sdk is not a valid editable requirement. It should eit her be a path to a local project or a VCS URL (beginning with bzr+http, bzr+http?:, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git +https, git+ssh, git+git, git+filr, hg+file, hg+http, hg+https, hg+«sh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).
Solution:
Go to the depthai directory, then execute python3 -m pip install -r . /requirements.txt
Please be sure to execute the relevant commands in the depthai folder, otherwise you will get errors such as file not found, not editable, etc.
[system] [error] Attempted to start Color camera – NOT detected
Error message:
OAK-1 run script depthai_movenet_main/examples/yoga_pose_recognition/demo.py error: [system] [error] Attempted to start Color camera – NOT detected!
Solution:
please check whether the camera inside the oak is connected to the motherboard normally and whether the camera is loose. Try upgrading depthai
Vite Bulk Import import.meta.glob Error: ERR_ABORTED 403 (Forbidden)
You need to set Vite server.fs.strict to false
Vite restricts access to files outside the workspace root path.
import { defineConfig } from 'vite'
export default defineConfig({
base: './', //PATH
plugins: [
createVuePlugin()
],
server: {
port: 8002, // Set the service startup port number
open: true, // Set whether to open the browser automatically when the service is started
fs: {
strict: false
}
}
})
Error: AttributeError: ‘depthai.node.ObjectTracker‘ object has no attribute ‘setTrackerIdAssigmentPolicy‘
Error Messages:
gen2 blur faces error: AttributeError: ‘depthai.node.ObjectTracker’ object has no attribute ‘setTrackerIdAssigmentPolicy’
Solution:
This is the old version of api, new version: objectTracker.setTrackerIdAssignmentPolicy(dai.TrackerIdAssignmentPolicy.SMALLEST_ID)
eggjs error: Warning: Current Server Discovery and Monitoring engine is deprecated, and will be rem…
Errors are reported as follows:
Warning: Current Server Discovery and Monitoring engine is deprecated, and will be removed in a future version. To use the new Server Discover and Monitoring engine, pass option { useUnifiedTopology: true } to the MongoClient constructor
Cause of error reporting:
Mongoose the old parser is going to be discarded and the new parser should be used
Solution:
Add a configuration in the directory config/config.default.js:
config.mongoose = {
url: 'mongodb://127.0.0.1:27017/userLog',
options: {
useUnifiedTopology:true
},
};Run c++ file with vscode error: fatal error: opencv2\core.hpp:No such file or diretory
The main error is that the corresponding header file cannot be found in the header file directory!
C header file directory %MINGW_PATH%/include under the header file, which has strcpy and other c function declaration.
C++ header file directory %MINGW_PATH%/lib/gcc/mingw32/4.4.0/include/c++ under the header file, which has the declaration of std::string class.
//home directory
MINGW_PATH=D:/MinGW
//C header file directory
C_INCLUDE_PATH=%MINGW_PATH%/include;%MINGW_PATH%/lib/gcc/mingw32/3.4.5/include
//C++ header file directory
CPLUS_INCLUDE_PATH=%MINGW_PATH%/include/c++/3.4.5;%MINGW_PATH%/include/c++/3.4.5/mingw32;%MINGW_PATH%/include/c++/3.4.5/backward;% C_INCLUDE_PATH%
//In QTSDK with MinGW the C++ header files are in the lib folder
CPLUS_INCLUDE_PATH=%MINGW_PATH%/lib/gcc/mingw32/4.4.0/include/c++;%C_INCLUDE_PATH%
//library directory
LIBRARY_PATH=%MINGW_PATH%/lib;%MINGW_PATH%/lib/gcc/mingw32/3.4.5
//executable program directory
PATH=%MINGW_PATH%/bin;%MINGW_PATH%/libexec/gcc/mingw32/3.4.5
AgilePLM error
Problem phenomenon
Agile version: 9.3.2
When searching for a material in full-text search, the error is report: ora-00904: “A”.”ITEM_NUMBER”:invalid identifier
However, no error will be reported when using advanced search to specify material search. Restart the database, restart the application and rebuild the index can not be solved.
Cause analysis
In the troubleshooting process, advanced search was used to search all objects one by one. Finally, it was found that the separate search price times was wrong. Later, the administrator remembered that he had changed a price standard in the morning and used the material code as the price standard. The problem may be caused by this operation.
Problem-solving
If the standard is changed, the material code cannot be used as the price standard. Then restart the agile application server. To solve the problem.
target_link_libraries error:
When compiling a project with cmake, the following appears:
NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
Cmake:
target_link_libraries(target target1 target2)
In this way, Target1 and target2 libraries need to be used when linking target. However, if Target1 also uses target2, you need to add additional:
target_link_libraries(target1 target2)
Otherwise, when the link generates Target1, you can’t find anything in target2. If target uses Target1 link again, it will definitely report an error.
cmake编译opencv开源项目报错问题
Recently, cmake encountered the following problems when compiling a C + + open source project configured with OpenCV environment:
CMake Warning at D:/opencv4/OpenCVConfig.cmake:176 (message):
Found OpenCV Windows Pack but it has no binaries compatible with your
configuration.
You should manually point CMake variable OpenCV_DIR to your build of OpenCV
library.
Call Stack (most recent call first):
CMakeLists.txt:13 (find_package)
CMake Error at CMakeLists.txt:13 (find_package):
Found package configuration file:
D:/opencv4/OpenCVConfig.cmake
but it set OpenCV_FOUND to FALSE so package "OpenCV" is considered to be
NOT FOUND.
So I checked all the methods online, which are basically divided into two categories: one is to modify cmakeLis.txt document. The other is to change the OpenCV version or vs version. But They are not working for me. Finally, I accidentally found that x64 was not selected in configure, and x86 was selected by default. After x64 was selected, the compilation was successful.
https://blog.csdn.net/weixin_61023120/article/details/124738628
In the past, the project could be built on Jenkins normally. Today, it is suddenly found that the construction is wrong. The problems are as follows:
Could not determine the dependencies of task ':lint'.
> Could not resolve all artifacts for configuration ':releaseUnitTestCompileClasspath'.
> Could not resolve junit:junit:4.+.
Required by:
project :
> Failed to list versions for junit:junit.
> Unable to load Maven meta-data from http://jcenter.bintray.com/junit/junit/maven-metadata.xml.
> Could not get resource 'http://jcenter.bintray.com/junit/junit/maven-metadata.xml'.
> Could not GET 'https://jcenter.bintray.com/junit/junit/maven-metadata.xml'.
> org.apache.http.client.ClientProtocolException (no error message)
> Skipped due to earlier error
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.Gradle plug-in version 4.1.2, gradle version 6.5
The solution to this problem is as follows:
1. Find the build.gralle file of moudle.
Modify testImplementation 'junit:junit:4.+' to testImplementation 'junit:junit:4.12'
2. Find the following places in the gradle compilation file used by Jenkins server and modify it to the following information
allprojects {
repositories {
jcenter { url "http://jcenter.bintray.com/"}
google()
maven { url 'http://repo1.maven.org/maven2' }
}
}Then use Jenkins to build again, and the APK can be built normally.