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

All .py files duplicated as .ipynb #167

Closed
lukaszmentel opened this issue Jul 26, 2023 · 4 comments
Closed

All .py files duplicated as .ipynb #167

lukaszmentel opened this issue Jul 26, 2023 · 4 comments

Comments

@lukaszmentel
Copy link

Hey, first of all thanks for a great tool!

I managed to configure the extension and get access to remote repo. I pulled all the files (not sure what is the difference between pull in the repo section and download in the workspace section, but it's safe to assume I did both at some point.

I made changes locally to some files and since there is no push I used upload from the workspace section. Now comes the unexpected and unwanted situation that all my .py files in the (even the ones I didn't touch got converted to .ipynb and pushed to remote repo.

Here's what I'm wondering:

  1. how to reverse this situation while keeping the changes I made locally - obviously I don't want to convert all the files. Both the extension and databricks have pretty basic (insufficiently minimal) git/github interface so it's hard to figure out what a good move here.
  2. Can I configure the extension to not convert any of the existing files and keep them as they are?

Thanks!

@KateGrim
Copy link

This also happens to any repo files you edit using wsfs:/. I've set "databricks.connection.default.exportFormats": {"Python": ".py"} but it doesn't seem to make any difference. This makes working from repos (most of what I do) totally impossible.

This does not seem to happen to python notebooks inside of a databricks workspace that are not connected to a repo.

@gbrueckl
Copy link
Collaborator

I will have a look at this once I am back at work next week.
It seems like the root cause is how notebooks and python files are treated
I will report back here once I had a closer look

@gbrueckl
Copy link
Collaborator

just found some time to have a look at this and I think I fixed the issue with v2.2.3 which is also live now in the VSCode Gallery

please give it another try and report back, thanks!

@gbrueckl
Copy link
Collaborator

closing as fixed and no further feedback provided

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants