Reverting changes (in dev container) broken

Bug Reports
1

Since 45.9 reverting changes in composer does revert changes, but running a build with yarn builds with last known state instead of with actual reverted state. Is it just me? win10

2

Could you share some screenshots of what you’re seeing? Would be helpful to see:

  • your composer history/checkpoints
  • the state of your files after reverting
  • the build output showing the wrong state

This will help us figure out if it’s a dev container specific issue or something else

3

Its a Problem with the restore mechanism. Atm on 0.45.15 (user setup, what ever this means)

Images wont help, but here they are

image
image1586×862 96.4 KB

image
image1581×832 92.8 KB

agent does changes. I build with yarn. (Code has 1184 lines)
I do not like the changes. I revert back with restore button, accept with blue button (Code has 1185 lines again). Do another build
yarn says compared for emit, so nothin changed compared to file before

As soon as i click out of the chat window the old chat gets normal again and the code changes back to the last edit as if i never reverted (1184 Lines again).

This behaviour started with 0.45.4? i guess

4

persists in 0.46.7
Restore Checkpoint
Leave chat Input Box
Changes are restored

5

I’ve been having an issue where whenever I revert, multiple files that were edited in the process are then messed up with improper indentation (python) which have to fix to get back to normal. This has been a big pain in the ■■■■ that just started happening this week. I never noticed it before.

I thought it was because I moved my files to my GitHub repo folder and it was pulling it or something but I just checked my most recent projects that had it happen and they are not attached to a Repo or anything else.

6

@TSTP-Enterprises This does not really seem realted.

Anyway, the mentioned bug is kinda fixed.

There is still a bug with reverting changes.

  1. Stopping/aborting a change removes the restore button, in combination with:

  2. There is no checkpoint made AFTER a change. Just after another user promt.

… leads to lost changes since there is no restore button in the a new window when you abbort a change and no restore in the last finished window, just a restore LAST checkpoint which in addition deletes the last change of the last (successful) window because you can’t restore to the last finished change.

I have to manually restore every file from history.

This also happens when the ai aborts. Reverting changes removes previous difs. With 0.64 the feature is absolutely not reliable

7

I also get the indentation issue - I’m no sure but it seems possibly related to claude-3.7-sonnet. When the agent tries to fix the indent errors (which it doesn’t sem to spot unless secifically told) it often says

I apologize for the difficulties with the edit tool. It seems we’re having trouble making the changes. Let me try one final approach by creating a new temporary file with the correct indentation and then replacing the old one

8

I am having this issue all the time. Large file, changes mess up Python indenting, then you revert to before the changes, and indenting still messed up. In some cases I have to revert 2 or 3 or 4 sets of changes back before it actually reverts. Then have to do all of them again.