This repository has been archived by the owner on Jun 20, 2023. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 71
git-referenced library causes endless rebuild loop #356
Labels
Comments
It also seems to re-generate |
Removing the git-referenced library seems to fix it, e.g. lib_deps =
https://github.com/SodaqMoja/SodaqOne-UniversalTracker-v2.git Changing it to a short notation with fixed sha doesn't seem to make a difference: lib_deps =
SodaqMoja/SodaqOne-UniversalTracker-v2#4b6b52fee10c7f4d31016acb6c34b188cd3a0d71 even on command line it seems to re-download/clone the repository every single build run. |
joscha
changed the title
Rebuild spawns an endless stream of Python processes
Rebuild with git-referenced library spawns an endless stream of Python processes
Apr 11, 2017
joscha
changed the title
Rebuild with git-referenced library spawns an endless stream of Python processes
git-referenced library causes endless rebuild loop
Apr 11, 2017
Using a version number, e.g.: |
Should be fixed in the latest PIO Core. Could you reproduce it again? |
Please install the latest PIO IDE 2.0 Beta 3. Should be fixed |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2.0.0-beta.2
3.4.0a4
When rebuilding a project after updating to
2.0.0-beta.2
from1.7
, the rebuild window spins up an endless number of times, each time setting off an additional Python process that downloads theatmelsam
framework.Came across it due to trying out the fix for: platformio/platform-atmelsam#10
can only get out with:
killall python2.7
andkillall Atom
ini looks like:
The text was updated successfully, but these errors were encountered: