Previous season 5 |
Current season: 6 |
Next season 7 |
|---|
This is an oveview of the sixth season (31 days, day 158-189) of using this tool (until the Personal Access Token expires)
This season starts with 2022, Thursday, December 1st. It is expected to last until 2022, Saturday, December 31st.
For this season, I have chosen a custom range, instead of a 30 day range. From now on, I plan to have the access token expire on the first day of each month.
A large segment (well over half) of this season contains no data, as the workflow was not operating correctly this month.
Click/tap here to expand/collapse the Season 6 notes section
Click/tap here to expand/collapse the 2022 December section
Click/tap here to expand/collapse the entry for 2022, Thursday, December 1st
2022, Thursday, December 1st
The process ran (somewhat) successfully today, finishing in 2 hours, 46 minutes, and 17 seconds. There were no aiohttp errors today. Despite the process running so much longer today, only 1000 repositories were scanned today. My recent uptick in Java usage is now showing up in the language statistics.
I put the workflow runs into 26 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2300+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2300+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2300+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2300+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2300+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2300+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2300+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2300+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2300+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2300+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2300+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2300+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2300+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2300+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2300+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2300+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2300+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2300+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2300+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2300+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2300+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2300+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2300+ repositories scanned/indexed - Category 25:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 12 day. I was hoping for a better start to the month, but at least the month didn't start with failure.
Click/tap here to expand/collapse the entry for 2022, Friday, December 2nd
2022, Friday, December 2nd
The process ran successfully today, finishing in 4 hours, 3 minutes, and 58 seconds. There were no aiohttp errors today. All repositories were scanned today.
I put the workflow runs into 26 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2300+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2300+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2300+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2300+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2300+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2300+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2300+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2300+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2300+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2300+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2300+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2300+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2300+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2300+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2300+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2300+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2300+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2300+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2300+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2300+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2300+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2300+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2300+ repositories scanned/indexed - Category 25:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 25 day.
Click/tap here to expand/collapse the entry for 2022, Saturday, December 3rd
2022, Saturday December 3rd
The process ran unsuccessfully today, failing in 1 minute and 5 seconds. There were some aiohttp errors today. There was an uncommon AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common. No repositories were scanned today.
I put the workflow runs into 26 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2300+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2300+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2300+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2300+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2300+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2300+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2300+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2300+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2300+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2300+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2300+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2300+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2300+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2300+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2300+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2300+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2300+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2300+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2300+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2300+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2300+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2300+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2300+ repositories scanned/indexed - Category 25:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Sunday, December 4th
2022, Sunday, December 4th
The process ran unsuccessfully again today, failing in 2 minute and 4 seconds. There were some aiohttp errors today. There was an uncommon AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common. No repositories were scanned today. I currently assume it failed because I was working while the process was starting.
I put the workflow runs into 26 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2300+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2300+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2300+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2300+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2300+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2300+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2300+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2300+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2300+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2300+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2300+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2300+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2300+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2300+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2300+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2300+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2300+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2300+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2300+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2300+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2300+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2300+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2300+ repositories scanned/indexed - Category 25:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Monday, December 5th
2022, Monday, December 5th
The process ran unsuccessfully yet again today (3rd consecutive day of failure) failing in 1 minute and 50 seconds. There were some aiohttp errors today. There was also a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common. No repositories were scanned today. I previously assumed that it failed because I was working while it was starting. That wasn't the case today. I am glad it at least failed when my last workflow run gave full results. I feel it has done something similar to this in the past, and has bounced back. However, if there isn't a successful run by 2022, Friday, December 9th, I will contact the author of the workflow.
I put the workflow runs into 26 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2300+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2300+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2300+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2300+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2300+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2300+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2300+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2300+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2300+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2300+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2300+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2300+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2300+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2300+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2300+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2300+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2300+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2300+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2300+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2300+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2300+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2300+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2300+ repositories scanned/indexed - Category 25:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Tuesday, December 6th
2022, Tuesday, December 6th
The process ran unsuccessfully yet again today (4th consecutive day of failure) but it put up a good fight, failing in 2 hours, 3 minutes, and 40 seconds. There were thousands of aiohttp errors today. I knew something was really off when there were nearly 2000 errors within the first 20 minutes. There was also a AttributeError: 'NoneType' object has no attribute 'get' error today as a cherry on top. This error is starting to become common. Additionally, the workflow had to back itself up before finishing, as something went really wrong at the end. No repositories were scanned today. I feel it has done something similar to this in the past, and has bounced back. However, if there isn't a successful run by 2022, Friday, December 9th, I will contact the author of the workflow.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Wednesday, December 7th
2022, Wednesday, December 7th
The process ran (somewhat) successfully today, ending a 4 day failure streak. It finished with partial results in 1 hour 32 minutes and 31 seconds. There were no aiohttp errors today. Only 900 repositories were scanned today, still better than failure.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 11 day.
Click/tap here to expand/collapse the entry for 2022, Thursday, December 8th
2022, Thursday, December 8th
The process ran unsuccessfully today, failing within 1 minute and 23 seconds. There was also a AttributeError: 'NoneType' object has no attribute 'get' error today as a cherry on top. This error is starting to become common. No repositories were scanned today. Hopefully it can work tomorrow, this month hasn't been going too well for this project.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Friday, December 9th
2022, Friday, December 9th
The process ran (somewhat) successfully today. It finished with partial results in 1 hour 50 minutes and 12 seconds. There were no aiohttp errors today. Only 1000 repositories were scanned today, still better than failure.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 12 day.
Click/tap here to expand/collapse the entry for 2022, Saturday, December 10th
2022, Saturday, December 10th
The process ran unsuccessfully today, failing within 2 minutes and 3 seconds. There was also a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. No repositories were scanned today. Hopefully it can work tomorrow, this month really hasn't been going too well for this project.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Sunday, December 11th
2022, Sunday, December 11th
The process ran unsuccessfully today, failing within 1 minute and 3 seconds. There was also a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. No repositories were scanned today. Hopefully it can work tomorrow, this month really hasn't been going too well for this project. I am starting to think this workflow wasn't designed for someone with so many repositories
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Monday, December 12th
2022, Monday, December 12th
The process ran successfully today, finishing within 4 hours, 20 minutes, and 44 seconds. Despite some aiohttp errors, the workflow succeeded today. All repositories were scanned today. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 26 day.
Click/tap here to expand/collapse the entry for 2022, Tuesday, December 13th
2022, Tuesday, December 13th
The process ran unsuccessfully today, failing within 1 minute and 13 seconds. There was not a AttributeError: 'NoneType' object has no attribute 'get' error today. !--> Instead, there was a size changed during iteration error, which is the most common error I receive when the workflow runs unsuccessfully, despite me not being active on GitHub for an hour before and after it started. !--> No repositories were scanned today. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Wednesday, December 14th
2022, Wednesday, December 14th
The process ran unsuccessfully again today, failing within 0 minutes and 54 seconds. There was a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. No repositories were scanned today. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Thursday, December 15th
2022, Thursday, December 15th
The process ran unsuccessfully again today for a 3rd consecutive day, failing within 1 minute and 6 seconds. There was a there was a size changed during iteration error today, which is the most common error I receive when the workflow runs unsuccessfully. The failure may have been my fault this time, as I was slightly busy at the time that the workflow started. !--> No repositories were scanned today. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well.
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Friday, December 16th
2022, Friday, December 16th
The process ran (somewhat) successfully today, breaking a 3 day failure streak. The process finished within 2 hours, 40 minutes and 26 seconds. Only 1000 repositories were scanned today. Assembly has surpassed Java for the top 10 slots on off days, due to usage in recent Android x64 development. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 12 day.
Click/tap here to expand/collapse the entry for 2022, Saturday, December 17th
2022, Saturday, December 17th
The process ran unsuccessfully today, faling within 0 hours, 0 minutes and 54 seconds. there was a size changed during iteration error today, which is the most common error I receive when the workflow runs unsuccessfully. The failure may have been my fault this time, as I was activly checking to see if the workload had started, and accidentally made a push about 3 seconds after it started, which may have caused the failure. There were no aiohttp errors today. No repositories were scanned today. For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Sunday, December 18th
2022, Sunday, December 18th
The process ran (somewhat) successfully today, breaking a 1 day failure streak. The process finished within 1 hour, 51 minutes and 17 seconds. There were no aiohttp errors today. Only 900 repositories were scanned today. Assembly has surpassed Java for the top 10 slots on off days, due to usage in recent Android x64 development. Today for some reason, all 3 of the recent languages that have been increasing in use (Java, Assembly, and JSON) all appeared on the list. SVG usage has been stressing me out for a while, and I don't know how to fix it. There is a chance it may overtake both HTML and Python on both on and off days by late 2023 or 2024.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 11 day.
Click/tap here to expand/collapse the entry for 2022, Monday, December 19th
2022, Monday, December 19th
The process ran (somewhat) successfully today, getting a 2 consecutive day streak going for the first time in weeks, but also being a massive disappointment at the same time. The process finished within 5 hours, 28 minutes and 29 seconds. Even with all that time, it didn't even scan half of my repositories. There were some aiohttp errors today. Only 1000 repositories were scanned today. I am frustrated by the poor results over nearly 5 and a half hours, but am still glad it at least succeeded. Assembly has recently surpassed Java for the top 10 slots on off days, due to usage in recent Android x64 development. Today for some reason, all 3 of the recent languages that have been increasing in use (Java, Assembly, and JSON) all appeared on the list. SVG usage has been stressing me out for a while, and I don't know how to fix it. There is a chance it may overtake both HTML and Python on both on and off days by late 2023 or 2024.
I really felt like it was going to be a full success today, given how long it took, but no. This workflow seems completely unpredictable now.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 12 day.
Click/tap here to expand/collapse the entry for 2022, Tuesday, December 20th
2022, Tuesday, December 20th
The process ran (somewhat) successfully today, entering a 3 day success streak. The process finished within 1 hour, 31 minutes and 0 seconds. There were no aiohttp errors today. Only 900 repositories were scanned today. Assembly has surpassed Java for the top 10 slots on off days, due to usage in recent Android x64 development. Today for some reason, all 3 of the recent languages that have been increasing in use (Java, Assembly, and JSON) all appeared on the list, additionally, Ruby also appeared on the list. SVG usage has been stressing me out for a while, and I don't know how to fix it. There is a chance it may overtake both HTML and Python on both on and off days by late 2023 or 2024.
Today gave poor results, but unlike yesterday, it didn't waste excessive time or get my hopes up.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 11 day.
Click/tap here to expand/collapse the entry for 2022, Wednesday, December 21st
2022, Wednesday, December 21st
The process ran unsuccessfully today, breaking a 3 day success streak. The process failed within 0 hours, 1 minutes and 14 seconds. There was a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. There were no aiohttp errors today. No repositories were scanned today.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Thursday, December 22nd
2022, Thursday, December 22nd
The process ran unsuccessfully again today, going into day 2 of a failure streak. The process failed within 0 hours, 1 minutes and 55 seconds. There was a AttributeError: 'NoneType' object has no attribute 'get' error today. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. Additionally, there were some aiohttp errors today. No repositories were scanned today.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Friday, December 23rd
2022, Friday, December 23rd
The process ran unsuccessfully again today, going into day 3 of a failure streak. The process failed within 4 hours, 43 minutes and 44 seconds. The workflow spit out thousands of aiohttp errors. I knew early on that it may have not succeeded, but I decided to let it keep going to see if it would, as I can’t be sure due to what has been going on lately. After 4 hours, 43 minutes, and 44 seconds, it failed, with over 16000 errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become common and may surpass the Size changed during iteration error in terms of occurrence. No repositories were scanned today.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Saturday, December 24th
2022, Saturday, December 24th
The process ran unsuccessfully yet again today, going into day 4 of a failure streak. The process failed within 0 hours, 0 minutes and 58 seconds. There were some aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence. No repositories were scanned today.
If the workload doesn't have a successful run by 2022, December 27th, I will contact @jstrieb but I am considering contacting him anyways (regardless if it succeeds by then) due to how the workload has been handling this month.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Sunday, December 25th
2022, Sunday, December 25th
The process ran unsuccessfully yet again today, going into day 5 of a failure streak. The process failed within 0 hours, 1 minutes and 14 seconds. There were some aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
Additionally, there was an error while handling the error, which was new. During handling of the above exception, another exception occurred: followed by another AttributeError: 'NoneType' object has no attribute 'get' error, and several aiohttp failed for GraphQL query errors, before it finally ended with Error: Process completed with exit code 1.
If the workload doesn't have a successful run by 2022, December 27th, I will contact @jstrieb but I am considering contacting him anyways (regardless if it succeeds by then) due to how the workload has been handling this month.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Monday, December 26th
2022, Monday, December 26th
The process ran unsuccessfully yet again today, going into day 6 of a failure streak. The process failed within 0 hours, 0 minutes and 53 seconds. There were some aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
Additionally, there was an error while handling the error, which was new. During handling of the above exception, another exception occurred: followed by another AttributeError: 'NoneType' object has no attribute 'get' error, and several aiohttp failed for GraphQL query errors, before it finally ended with Error: Process completed with exit code 1.
If the workload doesn't have a successful run by 2022, December 27th, I will contact @jstrieb but I am considering contacting him anyways (regardless if it succeeds by then) due to how the workload has been handling this month.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Tuesday, December 27th
2022, Tuesday, December 27th
The process ran unsuccessfully yet again today, going into day 7 of a failure streak. The process failed within 0 hours, 58 minutes and 58 seconds. It tried to run today, but there were too many aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
I plan to contact @jstrieb some time in 2023, January. The workflow has never done so poorly before.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Wednesday, December 28th
2022, Wednesday, December 28th
The process ran unsuccessfully yet again today, going into day 8 of a failure streak. The process failed within 2 hours, 56 minutes and 43 seconds. It tried to run today, but there were too many (near or more than 10000) aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
I plan to contact @jstrieb some time in 2023, January. The workflow has never done so poorly before.
I was additionally upset today, as for most of the day, my other GitHub stats were having problems, and I didn't have the time or resources to set up a Vercel instance to get them to work. Luckily, they self-recovered. This workflow hasn't.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Thursday, December 29th
2022, Thursday, December 29th
The process ran unsuccessfully yet again today, going into day 9 of a failure streak. The process failed within 0 hours, 0 minutes and 56 seconds. It tried to run today, but there were a couple aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
Additionally, there was an error while handling the error, which was new. During handling of the above exception, another exception occurred: followed by another AttributeError: 'NoneType' object has no attribute 'get' error, and several aiohttp failed for GraphQL query errors, before it finally ended with Error: Process completed with exit code 1.
I plan to contact @jstrieb some time in 2023, January. The workflow has never done so poorly before.
I have a feeling that this is going to last the rest of the month. There are still 2 days left, hopefully it can have 1 final success.
I didn't update my stats repository for 4 days. Today is the first time in 4 days that I updated it. I also learned today that the workflow in the post Run actions checkout phase has always been normal, at least for errored days.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Friday, December 30th
2022, Friday, December 30th
The process ran unsuccessfully yet again today, going into day 10 of a failure streak. The process failed within 0 hours, 1 minute and 21 seconds. There were a couple aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
Additionally, there was an error while handling the error; During handling of the above exception, another exception occurred: , followed by another error; AttributeError: 'NoneType' object has no attribute 'get' error, and several aiohttp failed for GraphQL query errors, before it finally ended with Error: Process completed with exit code 1.
I plan to contact @jstrieb some time in 2023, January. The workflow has never done so poorly before.
I have a feeling that this is going to last the rest of the month. There is still 1 day left, hopefully it can have 1 final success.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
Click/tap here to expand/collapse the entry for 2022, Saturday, December 31st
2022, Saturday, December 31st
The process ran unsuccessfully yet again today, going into day 11 of a failure streak, and ending the year with a failrue. The process failed within 0 hours, 1 minute and 0 seconds. There were a couple aiohttp errors, followed by a AttributeError: 'NoneType' object has no attribute 'get' error. This error is starting to become very common and may surpass the Size changed during iteration error in terms of occurrence.
I plan to contact @jstrieb some time in 2023, January. The workflow has never done so poorly before.
The year ended with a failure. I am hoping it improves next year. I still intend to renew the access token tomorrow.
For the meantime, when the workflow has a 100% success, it will be counted as equivalent to 2 days of partial success. This month really has not been going well. The failure rate is still well over 50%
I put the workflow runs into 27 categories:
[Click/tap here to expand/collapse the category listing]
- Category 0:
Complete failure- The process did not run - Category 1:
R0- Partial, extremely poor success, with 0 repositories scanned/indexed, but the workflow still ran and didn't throw an error - Category 2:
R99- Partial, extremely poor success, with 1-99 out of 2400+ repositories scanned/indexed - Category 3:
R100- Partial, extremely poor success, with 100-199 out of 2400+ repositories scanned/indexed - Category 4:
R200- Partial, extremely poor success, with 200-299 out of 2400+ repositories scanned/indexed - Category 5:
R300- Partial, extremely poor success, with 300-399 out of 2400+ repositories scanned/indexed - Category 6:
R400- Partial, very poor success, with 400-499 out of 2400+ repositories scanned/indexed - Category 7:
R500- Partial, very poor success, with 500-599 out of 2400+ repositories scanned/indexed - Category 8:
R600- Partial, very poor success, with 600-699 out of 2400+ repositories scanned/indexed - Category 9:
R700- Partial, very poor success, with 700-799 out of 2400+ repositories scanned/indexed - Category 10:
R800- Partial, poor success, with 800-899 out of 2400+ repositories scanned/indexed - Category 11:
R900- Partial poor success, with 900-999 or less out of 2400+ repositories scanned/indexed - Category 12:
R1000- Partial success, with 1000-1099 out of 2400+ repositories scanned/indexed - Category 13:
R1100- Partial success, with 1100-1199 out of 2400+ repositories scanned/indexed - Category 14:
R1200- Partial success, with 1200-1299 out of 2400+ repositories scanned/indexed - Category 15:
R1300- Partial success, with 1300-1399 out of 2400+ repositories scanned/indexed - Category 16:
R1400- Partial success, with 1400-1499 out of 2400+ repositories scanned/indexed - Category 17:
R1500- Partial success, with 1500-1599 out of 2400+ repositories scanned/indexed - Category 18:
R1600- Moderate success, with 1600-1699 out of 2400+ repositories scanned/indexed - Category 19:
R1700- Moderate success, with 1700-1799 out of 2400+ repositories scanned/indexed - Category 20:
R1800- Moderate success, with 1800-1899 out of 2400+ repositories scanned/indexed - Category 21:
R1900- Moderate success, with 1900-1999 out of 2400+ repositories scanned/indexed - Category 22:
R2000- Moderate success, with 2000-2099 out of 2400+ repositories scanned/indexed - Category 23:
R2100- Major success, with 2100-2199 out of 2400+ repositories scanned/indexed - Category 24:
R2200- Major success, with 2200-2299 out of 2400+ repositories scanned/indexed - Category 25:
R2300- Major success, with 2300-2399 out of 2400+ repositories scanned/indexed - Category 26:
Complete success- The process ran and gave accurate results with all repositories scanned
Today was a category 0 day.
I made the observation that when successfully ran, only 10 languages are listed, but when it doesn't run successfully, only 15 languages are listed. This has been proven untrue with the 2022 September 30th workflow run
I have noted that a good way to see if it ran correctly or not is to check the overview image card. If it says No name instead of my original GitHub username (Sean P. Myrick V19.1.7.2) (not my handle, seanpm2001) then it ran incorrectly. Otherwise, it worked correctly. For personal usage, I can tell it ran worse when the counted repositories is 800 instead of 900 or 1000 additionally, if my GitHub username doesn't come up, the card puts 0 for the total commit count. This has been proven untrue with the 2022 September 30th workflow run
These errors have been present on all runs since 2022, October 13th
Additionally, these errors were present:
build
Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: actions/checkout, actions/setup-python, actions/cache, actions/checkout
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
The `save-state` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
build
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
I am adding these verbatim. The same errors seem to have been duplicates.
Click/tap here to expand the season 6 overview & language counts table
| Type rate | Count |
|---|---|
| Success rate (days) | 9 |
| Full success (days) | 2 |
| Partial success (days) | 7 |
| Failure rate (days) | 22 |
| Full success % | 06.89% |
| Partial success % | 29.03% |
| Overall success % | 22.58% |
| Success % Margin of error | 00.01% |
| Overall failure % | 70.96% |
Previous season 5 |
Current season: 6 |
Next season 7 |
|---|
The access token for this project was simply named ACCESS_TOKEN I don't have its URL on me, but I do have the configuration info for when I create a new one tomorrow (since the current one expires on 2022, Tuesday, July 12th)
You can use this as a reference for setting up the project.
The access token for this project was renewed on 2022 July 12th before 2:35 pm PST.
The access token for this project was renewed on 2022, August 26th
The access token for this project was renewed on 2022, September 25th
The access token for this project was renewed on 2022, October 25th. For this season, I am changing things up for the range. I have chosen a custom range, instead of a 30 day range. From now on, I plan to have the access token expire on the first day of each month.
The access token for this project was renewed on 2022, December 1st. I am continuing on with the plan of having the token expire on the first day of each month, so that it is also renewed on the first day of each month.
Click/tap here to expand/collapse the file info section
File type: Markdown document (*.md *.mkd *.mdown *.markdown)
File version: 22 (2022, Saturday, December 31st at 7:57 pm PST)
Line count (including blank lines and compiler line): 2,175
Article language: English (USA) / Markdown (CommonMark) / HTML5 (5.3)
You may need special rendering support for the <details> tag in use in this document.
Click/tap here to expand/collapse the changelog for this project
Version 1 (2022, Thursday, December 1st at 9:14 pm PST)
This version was made by: @seanpm2001
Changes:
- Started the file
- Added the title section
- Added the main table
- Separated the access token section
-
- Added the master access token section
-
- Added the season 1 access token section
-
- Added the season 2 access token section
-
- Added the season 3 access token section
-
- Added the season 4 access token section
-
- Added the season 5 access token section
-
- Added the season 6 access token section
- Remodeled the file for season 6
- Added the file info section
- Added the changelog
- No other changes in version 1
Version 2 (2022, Friday, December 2nd at 10:04 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Friday, December 2nd
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 2
Version 3 (2022, Monday, December 5th at 5:54 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Saturday, December 3rd
- Added an entry for 2022, Sunday, December 4th
- Added an entry for 2022, Monday, December 5th
- Unsuccessfully attemped to correct the access token image link for season 6
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 3
Version 4 (2022, Tuesday, December 6th at 9:10 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Monday, December 6th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 4
Version 5 (2022, Thursday, December 8th at 6:31 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Tuesday, December 7th
- Added an entry for 2022, Wednesday, December 8th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 5
Version 6 (2022, Friday, December 9th at 8:50 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Friday, December 9th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 6
Version 7 (2022, Saturday, December 10th at 7:53 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Saturday, December 10th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 7
Version 8 (2022, Monday, December 12th at 11:47 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Sunday, December 11th
- Added an entry for 2022, Monday, December 12th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 8
Version 9 (2022, Tuesday, December 13th at 8:45 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Tuesday, December 13th
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 9
Version 10 (2022, Wednesday, December 14th at 7:13 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Wednesday, December 14th
- Added a failure/success rate table for the month
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 10
Version 11 (2022, Thursday, December 15th at 6:24 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Thursday, December 15th
- Updated the failure/success rate table for the month
-
- Current fail rate: 66.67%
-
- Current success rate: 33.33%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 11
Version 12 (2022, Friday, December 16th at 10:14 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Friday, December 16th
- Updated the failure/success rate table for the month
-
- Current fail rate: 62.50%
-
- Current success rate: 37.50%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 12
Version 13 (2022, Saturday, December 17th at 6:19 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Saturday, December 17th
- Updated the failure/success rate table for the month
-
- Current fail rate: 64.70%
-
- Current success rate: 35.30%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 13
Version 14 (2022, Sunday, December 18th at 8:03 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Sunday, December 18th
- Updated the failure/success rate table for the month
-
- Current fail rate: 61.11%
-
- Current success rate: 38.89%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 14
Version 15 (2022, Monday, December 19th at 11:14 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Monday, December 19th
- Updated the failure/success rate table for the month
-
- Current fail rate: 57.89%
-
- Current success rate: 42.11%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 15
Version 16 (2022, Tuesday, December 20th at 7:29 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Tuesday, December 20th
- Made corrections to yesterdays entry (2022, Sunday, December 19th)
- Updated the failure/success rate table for the month
-
- Current fail rate: 55.00%
-
- Current success rate: 45.00%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 16
Version 17 (2022, Wednesday, December 21st at 5:40 pm PST)
This version was made by: @seanpm2001
Changes:
- Added some miscellaneous notes for project development for tomorrow
- Added an entry for 2022, Wednesday, December 21st
- Updated the failure/success rate table for the month
-
- Current fail rate: 57.14%
-
- Current success rate: 42.86%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 17
Version 18 (2022, Thursday, December 22nd at 8:08 pm PST)
This version was made by: @seanpm2001
Changes:
- Removed some miscellaneous notes for project development from yesterday, as they are unnecessary for this file, and they have now been completed
- Added an entry for 2022, Thursday, December 22nd
- Updated the failure/success rate table for the month
-
- Current fail rate: 59.09%
-
- Current success rate: 40.91%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 18
Version 19 (2022, Saturday, December 24th at 6:20 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Friday, December 23rd
- Added an entry for 2022, Saturday, December 24th
- Updated the failure/success rate table for the month
-
- Current fail rate: 62.50%
-
- Current success rate: 37.50%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 19
Version 20 (2022, Sunday, December 25th at 7:22 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Sunday, December 25th
- Updated the failure/success rate table for the month
-
- Current failure rate: 64.00%
-
- Current success rate: 36.00%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 20
Version 21 (2022, Thursday, December 29th at 6:54 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Monday, December 26th
- Added an entry for 2022, Tuesday, December 27th
- Added an entry for 2022, Wednesday, December 28th
- Added an entry for 2022, Thursday, December 29th
- Updated the failure/success rate table for the month
-
- Current failure rate: 68.07%
-
- Current success rate: 31.03%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 21
Version 22 (2022, Saturday, December 31st at 7:57 pm PST)
This version was made by: @seanpm2001
Changes:
- Added an entry for 2022, Friday, December 30th
- Added an entry for 2022, Saturday, December 31st
- Updated the failure/success rate table for the month
-
- Final failure rate: 70.97%
-
- Final success rate: 29.03%
- Updated the main table
- Updated the file info section
- Updated the file history section
- No other changes in version 22

