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

Version Control: Commit Changes dialog populates with other windows contents #1686

Closed
th3coop opened this issue Jun 8, 2016 · 3 comments
Closed
Assignees
Milestone

Comments

@th3coop
Copy link
Member

th3coop commented Jun 8, 2016

Short Summary

I have two Komodo Windows open
I have the Commit Changes tab in the Version Control widget open in both
While I'm working eventually the OTHER window (ie. not the one I'm working in) will populate Commit Changes with my working windows file state information.

In my case I was working on Edit in one window and IDE in the other. I ended up making a commit on IDE from the Edit project and didn't notice because i was editing the same file in each project. I don't know how to reproduce this EXACTLY but if you work with the setup described above you should eventually hit the issue.

I've attached a screenshot to try and show what this looks like. Yes the root directories in Places for each window were in the correct repo:
capture

@Naatan
Copy link
Member

Naatan commented Jun 9, 2016

Can you consistently reproduce this? The context of this screenshot could easily just be correlation, not causation.

@th3coop
Copy link
Member Author

th3coop commented Jun 9, 2016

The context of this screenshot could easily just be correlation, not causation.

The screenshot is just pointing out the resulting bug and what it looks like. I don't know what is causing it.

Yes this is consistently reproducible following the steps I outlined above. I'll try to clarify:

  1. Start Komodo and open a Project that has git, wait until it shows it's status in the Commit Changes
  2. open another Komodo window that has a git repo. Wait until it updates it's own status in the Commit Changes tab.
  3. Watch the first windows Commit Changes tab. It should eventually update with the second windows state.

@Naatan
Copy link
Member

Naatan commented Jun 10, 2016

Alright, thanks @cgchoffman.

@Naatan Naatan added this to the 10.0.1 milestone Jun 10, 2016
@Naatan Naatan self-assigned this Jun 10, 2016
@Naatan Naatan closed this as completed in 5fee5de Jun 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants