Pyinstaller error 'Failed to determine version' - python-3.x

from the error 'Unhandled exception in script' I can see that it somehow doesn't recognise module Mindee
in my code it's imported as
'from mindee import Client, documents'
I tried --hidden import, but nothing seems to work it's always the same error
importing only mindee doesn't work too

Something similar happened to me. It seems to look for a version file inside path/main/version folder that doesn't exists (and it doesn't creates either)

Related

Issues with importing a library in nim test file

I'm having some issues including a library in a nim test file.
My code in my test file looks like this.
import unittest
import testToolpkg/Login
import dotenv
load()
test "valid login cookies":
var cookies = loginCookies(os.get("EMAIL"), os.get("PASSWORD"), os.get("URL"))
check cookies.len != 0
However when I run nimble test I get this error Error: cannot open file: dotenv. This seems to be an issue with any external library I try to use in a test.
The dotenv library works fine outside of the tests folder. I'm not sure if I'm missing some kind of option to get this to work? I am running this on windows as well.
After adding the lib to my .nimble file
requires "dotenv >= 2.0.0"
The issue was resolved!

Can't import openzeppelin node_modules: File import callback not supported

Whenever I try to compile my solidity contract, the error ParserError: Source \"#OpenZeppelin/contracts/math/SafeMath.sol\" not found: File import callback not supported gets thrown.
pragma solidity ^0.7.0;
import "#OpenZeppelin/contracts/token/ERC20/ERC20.sol";
import "#OpenZeppelin/contracts/math/SafeMath.sol";
Any ideas what could be causing this?
Make sure you opened VS Code in the root directory of the project.
In my case, this is how my VS Code directory looked like when I get that same error.
projects
|___MyContract
|__contracts
|__Contract.sol
Reopening VS Code in the MyContract directory fixes it.
MyContract
|__contracts
|__Contract.sol
I have the same problem right now. I'm using truffle+node and I fixed it modifying the import path to a relative path, for example,
pragma solidity ^0.7.0;
import "../node_modules/OpenZeppelin/contracts/token/ERC20/ERC20.sol";
import "../node_modules/OpenZeppelin/contracts/math/SafeMath.sol";
I'm not 100% sure why this happen but I hope I helped you.
After installing OpenZeppelin close your IDE and re-open it.
For some environments, SafeMath has a different path
import "#openzeppelin/contracts/utils/math/SafeMath.sol";
Make sure you installed openzeppelin
npm install --save #openzeppelin/contracts#v3.0.0
actualy the problem is solidity compiler is stupid and doesn't automatically follow path, you have to specify all allowed path manually (https://docs.soliditylang.org/en/latest/using-the-compiler.html), every each one of them and completely to the file(cannot give juste the higher level folder) use npx hardat compile if you can it's better
what worked for me;
(I am using Windows10 and visual studio code)
-click on the extensions icon
-search for the solidity extension
-select the uninstall button and click on the drop down arrow
-select install another version
-select version 0.0.135
-After the installation, click on "Reload required"
This worked for me -
Change the settings in Solidity extension in VSCode.
The default settings include:
"solidity.packageDefaultDependenciesContractsDirectory": "contracts"
Users need to change the setting from contracts to an empty string.
"solidity.packageDefaultDependenciesContractsDirectory": ""
Source - https://github.com/juanfranblanco/vscode-solidity/issues/178
Try this:
import "{Project Name}/node_modules/#openzeppelin/contracts/token/ERC20/ERC20.sol";

Failed to compile ./src/components/Chat/Chat.js Module not found: Can't resolve './components' in

Failed to compile
./src/components/Chat/Chat.js
Module not found: Can't resolve './components' in 'C:\Users\VISHAL\Desktop\Chat-app\lets_meet\client\src\components\Chat'
I am copy this project from github but it is showing error..... i didn't copy whole project just copy some of the pages...
the link of the github from where i copied the code is
can anyone help me?
Chat.js is trying to import component.js from the Chat folder which doesn't exists. Navigate to the correct path where the component.js file located.
Actually it is giving this type of error because i forgot to make a file inside message folder message.js ,Now it's working fine .I think if there is any missing file then it will give error like that .... Sorry for made a common mistake.

unable to resolve external module typescript

I'm trying to build a project, but I keep getting compiler errors which say
Unable to resolve external module and Module cannot be aliased to a non-module type.
I have header file which contains all the typing reference path, but even when I try to reference the path in the same file, it still doesn't resolve the problem.
I ran into this error when I shouldn't have due to a bug with TypeScript 1.0.0, but was able to resolve it by upgrading to 1.0.1. Try doing that. If you still get the error, it's probably a bug in your code.

Jelly module throwing internal server error

The Jelly module throws a 500 internal error. I have no idea why it does this and how to solve this.
When I remove jelly module folder from the server or simply rename any of the Jelly module files, the error disappears (Kohana throws an error because Jelly Class is not found which is normal).
I don't understand why Jelly would throw an internal error, it just does not make any sense!
(The error does not come from the folders and files permissions. I made sure that they're all 755 and 644).
(Everything works fine locally - WAMP server)
Thank you.
Check you're on the latest version of Jelly.
Check all your files for syntax errors. If you don't get an error page returned from Kohana it's probably because you've crashed php in some way.
Sorry if this doesn't help, please post more code/debug info.
Thank your for your answers. The problem was solved somehow. I have no idea what happened.
It seemed to work when I removed send_headers() in the bootstrap but it really annoyed me because I needed it.
Then I replaced Request::instance($_SERVER['PATH_INFO']) by Request::instance() in the echo in the bootstrap and it worked...
More info about the error logs there: http://forum.kohanaframework.org/comments.php?DiscussionID=6322&page=1

Resources