-
Notifications
You must be signed in to change notification settings - Fork 11
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
Duplicate uploads of Salmon Run jobs previously uploaded by s3s #45
Labels
bug
Something isn't working
Comments
It was a bug in s3s, and I am happy to add workaround to avoid duplicate export |
Merged
spacemeowx2
added a commit
that referenced
this issue
Nov 30, 2022
Duplicate uploads and missing the weapon list should be fixed. Please delete the old battles using |
spacemeowx2
added a commit
that referenced
this issue
Nov 30, 2022
spacemeowx2
added a commit
that referenced
this issue
Nov 30, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I've been running s3s for the past few weeks, and wanted to give s3si.ts a go for its rank tracking. After starting the docker container, I noticed it started trying to upload 50 salmon run jobs, and after stopping it and checking one, I had noticed that it was uploading duplicates of jobs s3s had uploaded.
This can be observed on my stat.ink profile here
Interestingly, those uploaded by s3si.ts also seem to be missing the rank before (showing ? -> whatever rank whereas s3s shows the data, possibly related to the below error?), and are missing the weapon list on the Salmon Log page, but not in the full details page.
At some point, I also started getting spam of the following error:
I am unsure if this happens with normal games too as I quickly killed s3si.ts after noticing this
To Reproduce
Steps to reproduce the behavior:
Expected behavior
s3si.ts should skip jobs uploaded by s3s.
Screenshots or Links
If applicable, add screenshots or links to stat.ink to help explain your problem.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: