Position tracking thrown out of order
For some reason, the following tweets were just spit out by track positions:
Logs
2021-03-18 00:00:23.213 WET
update
edjiisd4rasd
Tweeting about *ReactiveX/RxJava* surpassing *google/guava* (209/280 characters).
Info
2021-03-18 00:00:23.304 WET
update
edjiisd4rasd
Tweeting about *scikit-learn/scikit-learn* surpassing *cdr/code-server* (242/280 characters).
Info
2021-03-18 00:00:23.308 WET
update
edjiisd4rasd
Tweeting about *ReactTraining/react-router* surpassing *prettier/prettier* (245/280 characters).
Info
2021-03-18 00:00:23.308 WET
update
edjiisd4rasd
Tweeting about *jekyll/jekyll* surpassing *serverless/serverless* (210/280 characters).
Info
2021-03-18 00:00:23.312 WET
update
edjiisd4rasd
Tweeting about *moment/moment* surpassing *neovim/neovim* (204/280 characters).
Info
2021-03-18 00:00:23.314 WET
update
edjiisd4rasd
Tweeting about *necolas/normalize.css* surpassing *soimort/you-get* (237/280 characters).
Info
2021-03-18 00:00:23.400 WET
update
edjiisd4rasd
Tweeting about *huggingface/transformers* surpassing *tesseract-ocr/tesseract* (262/280 characters).
Info
2021-03-18 00:00:23.403 WET
update
edjiisd4rasd
Tweeting about *apache/echarts* surpassing *meteor/meteor* (215/280 characters).
Info
2021-03-18 00:00:23.404 WET
update
edjiisd4rasd
Tweeting about *fatedier/frp* surpassing *grafana/grafana* (204/280 characters).
Info
2021-03-18 00:00:23.407 WET
update
edjiisd4rasd
Tweeting about *ionic-team/ionic-framework* surpassing *yarnpkg/yarn* (273/280 characters).
Info
2021-03-18 00:00:23.410 WET
update
edjiisd4rasd
Tweeting about *meteor/meteor* surpassing *ageitgey/face_recognition* (232/280 characters).
Info
2021-03-18 00:00:23.503 WET
update
edjiisd4rasd
Tweeting about *cdr/code-server* surpassing *Dogfalo/materialize* (238/280 characters).
Info
2021-03-18 00:00:23.508 WET
update
edjiisd4rasd
Tweeting about *neovim/neovim* surpassing *juliangarnier/anime* (224/280 characters).
Info
2021-03-18 00:00:23.598 WET
update
edjiisd4rasd
Tweeting about *google/guava* surpassing *ColorlibHQ/AdminLTE* (228/280 characters).
Info
2021-03-18 00:00:23.601 WET
update
edjiisd4rasd
Tweeting about *grafana/grafana* surpassing *nwjs/nw.js* (211/280 characters).
Info
2021-03-18 00:00:23.602 WET
update
edjiisd4rasd
Tweeting about *prettier/prettier* surpassing *ziishaned/learn-regex* (240/280 characters).
Info
2021-03-18 00:00:23.605 WET
update
edjiisd4rasd
Tweeting about *spring-projects/spring-framework* surpassing *babel/babel* (260/280 characters).
Info
2021-03-18 00:00:23.607 WET
update
edjiisd4rasd
Tweeting about *yarnpkg/yarn* surpassing *parcel-bundler/parcel* (221/280 characters).
Info
2021-03-18 00:00:23.609 WET
update
edjiisd4rasd
Tweeting about *square/okhttp* surpassing *square/retrofit* (209/280 characters).
Info
2021-03-18 00:00:23.610 WET
update
edjiisd4rasd
Tweeting about *home-assistant/core* surpassing *tailwindlabs/tailwindcss* (263/280 characters).
Info
2021-03-18 00:00:23.699 WET
update
edjiisd4rasd
Tweeting about *serverless/serverless* surpassing *ziishaned/learn-regex* (236/280 characters).
Info
2021-03-18 00:00:23.704 WET
update
edjiisd4rasd
Tweeting about *soimort/you-get* surpassing *ziishaned/learn-regex* (226/280 characters).
It looks like almost all repos reported changing positions at once (during one update call) and I have no idea why. It might be related to #55.
It also makes absolutely no sense in terms of the absolute positions:
- RxJava is at position 82 and guava is at 95.
This means that this is for sure a bug in the logic that I need to fix asap.
Okay, so the source of the incident is pretty clear:
For some reason, the position jumped to 70 for one fetch. This bug has to be resolved.
I checked the order in the database now and it looks all good (the positions match the order by stars).
Need a way to enforce correct array order better probably. Trusting the GitHub API might not be the move. I want to say yes, but I am not yet sure what caused the bug.
This is still occuring, probably on about a weekly basis.
#331 resolves the symptoms of it for the most part, but the issue still exists. Renaming to generalize the issue.
Reducing priority due to the fix of symptoms in #331.
Cannot reproduce at this time.