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

Upload results in a flood of tiny changesets #1579

Closed
TO-92 opened this issue Sep 24, 2019 · 10 comments
Closed

Upload results in a flood of tiny changesets #1579

TO-92 opened this issue Sep 24, 2019 · 10 comments
Assignees
Labels

Comments

@TO-92
Copy link

TO-92 commented Sep 24, 2019

Some days ago I took a field trip with StreetComplete (latest version, 14.0). Auto-Sync was off, and when I got home to my WLAN I started a manual upload.

To my surprise I found that it had created almost 100 individual changesets, each with just one single edit, like 42× "Add path surfaces", 26× "Add whether way is lit", etc.

See https://www.openstreetmap.org/user/BC168/history between 2019-09-22T18:42:01Z and 2019-09-22T18:46:02Z

I seem to recall that StreetComplete used to "bundle" edits, creating only one changeset per quest containing all the changes of that type. So this does not look like it is intended behaviour, does it?

@TO-92 TO-92 added the bug label Sep 24, 2019
@westnordost westnordost self-assigned this Sep 25, 2019
@westnordost
Copy link
Member

Yes, it should bundle it. This is a critical bug, I will investigate.

@westnordost
Copy link
Member

westnordost commented Sep 25, 2019

Hmm, I can not reproduce it. See https://www.openstreetmap.org/changeset/74897075

I tried both Auto-Sync on and Auto-Sync off. So it does not always happen. One example changeset of yours is https://www.openstreetmap.org/changeset/74779079
Interesting here is that the changeset was closed one second after it was opened. This will be the reason why a new changeset was created. The app tried to upload the change into the existing changeset but got rejected cause it was already closed.

So the question is, why is it closed? The app should only close changesets after there has been no activity for 20min.

@westnordost
Copy link
Member

Got it. The bug was that the app was closing the changeset created for each change immediately before uploading the next change if the last quest was answered more than 20 minutes ago.

@peternewman
Copy link
Collaborator

peternewman commented Sep 25, 2019

Got it. The bug was that the app was closing the changeset created for each change immediately before uploading the next change if the last quest was answered more than 20 minutes ago.

Hi @westnordost ,

Your comment here and the commit comment seem to disagree to me. I assume you mean the issue is if 20 minutes have elapsed between answering the quest and uploading the data?

I don't think that's true of some of mine either:
https://www.openstreetmap.org/user/Peter%20Newman/history

@westnordost
Copy link
Member

I assume you mean the issue is if 20 minutes have elapsed between answering the quest and uploading the data?

Yes

I don't think that's true of some of mine either:
https://www.openstreetmap.org/user/Peter%20Newman/history

Why? One cannot see from the public history how much time elapsed between answering the question and uploading the answer. One can only see when it was uploaded, not when it was answered.

@peternewman
Copy link
Collaborator

Why? One cannot see from the public history how much time elapsed between answering the question and uploading the answer. One can only see when it was uploaded, not when it was answered.

Sorry, I probably wasn't very clear, I know because of where I was walking that within 20 minutes of completing a number of those quests I was within WiFi range and still had the app running, or does it also need to be the foreground app to upload?

@westnordost
Copy link
Member

It needs to be in the foreground, yes

@peternewman
Copy link
Collaborator

Hi @westnordost ,

I've updated to 14.1 and it still seems to be happening for me.

@peternewman
Copy link
Collaborator

I've updated to 14.1 and it still seems to be happening for me.

Ignore me, I've just realised the edits are now grouped by quest, which I assume was the intended behaviour.

@matkoniecz
Copy link
Member

Yes, this kind of splitting is intended!

Thanks for checking.

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

No branches or pull requests

4 participants