-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: AttributeError: 'PosixPath' object has no attribute 'split' / ImportError: attempted relative import beyond top-level package #1391
Comments
Same. Watchtower pulled latest last night and suddenly this container keeps dying with that error when it has been running for months with no issues with prior builds. I'm guessing now I'll have to go in and adjust some configuration to accommodate some change that was made for the sake of change. Many such cases! |
I assume ya'll were running on We just pushed a big pre-release last night, and not just for the sake of change, it's a big new security update with the latest Django 4.2 version that we've been working towards upgrading to for years. It'll make a lot of longstanding issues go away, and we'll be able to finally use some of the newer Django Admin UI features that people have been requesting for a long time. This latest The fix for this particular issue should be up within the next few hours, but beware there will likely be other issues in this |
@pirate Thanks for the update. I am willingly using the dev build to test it while in use. I take daily backups so that is fine. I was just reporting the issue. |
I tried downgrading to stable as suggested and am still running into the issue. (I should note that some self-hosted application repositories are shipping with the dev version, which might be why this is coming up.) EDIT: I ultimately fixed it by removing the |
Hello, Facing the same issue here, maybe the docker-compose example should be updated to use main insead: Line 16 in 1d49bee
I didn't even know I was using an unstable version (though I should have checked ^^) |
I mentioned this elsewhere, but it's this commit that needs to be brought into the dev branch to fix the relative import problem. |
Ah whoops that was caused by a bad merge into I will also have this fix and a fix for the |
Hi
The Docker dev build is throwing an error which prevents it from starting the container. That is why I can't run the archivebox info command.
The version
image: archivebox/archivebox
runs fine.Then I go ahead and define Chrome user dir however now it throws another type of error.
- CHROME_USER_DATA_DIR=/data/chrome
The text was updated successfully, but these errors were encountered: