Skip to content
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

Uknown file fileid.db gets created each time jupyverse starts in a folder #300

Closed
oscar6echo opened this issue May 13, 2023 · 5 comments · Fixed by #304
Closed

Uknown file fileid.db gets created each time jupyverse starts in a folder #300

oscar6echo opened this issue May 13, 2023 · 5 comments · Fixed by #304
Labels
bug Something isn't working

Comments

@oscar6echo
Copy link

Description

Uknown file fileid.db gets created each time jupyverse starts in a folder.
Is it important ? Can a user delete it ? Probably it should not be there ? or at least visible ?
Probably not serious, but worrying.

image

Reproduce

Open jupyverse in any folder in any mode.

@oscar6echo oscar6echo added the bug Something isn't working label May 13, 2023
@welcome
Copy link

welcome bot commented May 13, 2023

Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗

If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
welcome
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋

Welcome to the Jupyter community! 🎉

@davidbrochart
Copy link
Collaborator

It's the path to the database used by the file ID manager (see here), which is responsible for tracking files and giving them a global ID.
I agree that it should at least start with a . to be hidden. It is fine to delete it, because it is created at startup.

@oscar6echo
Copy link
Author

Ok, if it could be put out of the user's way e.g. ~/local/share/jupyter next to its cousins file_id_manager.db, jupyverse_users.db, etc then it may stop confusing the user, unless there is a good reason to have it in the opened folder ?

Alternatively I tested with name .fileid.db and indeed it does not show up in jupyter lab; good enough.

@davidbrochart
Copy link
Collaborator

I'm not sure it can live in a Jupyter directory, because between two server sessions the file system could be completely different (say the local file system and a file system on the cloud, for instance), and it wouldn't make sense to mix the information from both file systems.

@oscar6echo
Copy link
Author

Ok, I have inspected the .fileid.db with an sqlite browser and now have better idea what all this is about.
Indeed by definition this is relevant to the current directory.

So yes the conclusion seems to be that renaming it to .fileid.db would solve the user unease with this UFO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants