Skip to content

Conversation

@felixwalberg
Copy link
Contributor

After attempting to save the files that had been changed so that I could show Will the diff, all the changes vanished on running a commit.

What worked: completely deleting the repository and cloning again. Now I am able to run my scenes without UID not found errors.

What is still happening: These files (in the diff of this PR) are still appearing as changed and untracked. I added all of them to be tracked by git and committed them. There were no files that I made any modifications to during my work. My local main was up to date with endless/threadbare.git.

As of now, this doesn't seem to be hindering my ability to make more progress on the VRmont SQ, but of course, once I go to make my next PR, these changes might still be present.

@felixwalberg felixwalberg requested a review from a team as a code owner January 15, 2026 19:50

importer="game.threadbare.credits"
type="Resource"
importer="csv_translation"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, this is interesting and disappointing. I introduced a new import plugin to parse the CSV in a different way to the default.

@wjt
Copy link
Member

wjt commented Jan 15, 2026

After attempting to save the files that had been changed so that I could show Will the diff, all the changes vanished on running a commit.

If I understand correctly what happened: you committed the changes (screenshot on #1829) so by definition re-saving the project changed nothing. You could have used git show or a similar command to inspect the comimt.

@felixwalberg
Copy link
Contributor Author

After attempting to save the files that had been changed so that I could show Will the diff, all the changes vanished on running a commit.

If I understand correctly what happened: you committed the changes (screenshot on #1829) so by definition re-saving the project changed nothing. You could have used git show or a similar command to inspect the comimt.

That makes sense. Once I committed, my git status was up to date with the remote branch, and I was unaware that there were other ways to find commits if they didn't show up as "ahead" of the remote branch there.

@wjt
Copy link
Member

wjt commented Jan 15, 2026

That makes sense. Once I committed, my git status was up to date with the remote branch, and I was unaware that there were other ways to find commits if they didn't show up as "ahead" of the remote branch there.

You can compare your current branch to another one with a command like git diff main...my-lovely-branch. You can use git diff main...HEAD to compare main to the checked-out commit. Also you may find a Git GUI useful to explore the commit graph.

I'll close this PR and track the problem with the CSV import plugin in #1832. Thanks for reporting this!

@wjt wjt closed this Jan 15, 2026
@wjt wjt deleted the resources-added-troubleshooting branch January 15, 2026 20:23
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

Successfully merging this pull request may close these issues.

3 participants