active 2024-10-14 → 2025-03-15 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 153 days from 2024-10-14 to 2025-03-15. Pushes: 513 total, peak 66 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 11 total, peak 11 in a day. Comments: 3 total, peak 3 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| Manoj-Kumar-Selvaraj | 516 | 513 | 0 | 3 |
| maheshritgithub | 11 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#9Manoj-Kumar-Selvaraj2024-11-02 11:15Wrap the database query in a try-except block to handle any unexpected database issues gracefully.
- Issue comment#7Manoj-Kumar-Selvaraj2024-11-02 11:14It is better to save in utc format. So it will be easier to show the local time while retreveing from the database.
- Issue comment#6Manoj-Kumar-Selvaraj2024-11-02 11:10This check is good, but the logic could be improved by explicitly logging why a duplication might happen
- Issue#11maheshritgithub2024-11-02 11:07Declare the varaibles by the way to identify what is the purpose of it
- Issue#10maheshritgithub2024-11-02 11:01It’s good practice to add a message or status field, like "message": "Barcodes retrieved successfully"
- Issue#9maheshritgithub2024-11-02 11:00Wrap the database query in a try-except block to handle any unexpected database issues gracefully.
- Issue#8maheshritgithub2024-11-02 10:57Please keep in tn seprate file as helper method to avoid code duplication
- Issue#7maheshritgithub2024-11-02 10:56It is better to save in utc format. So it will be easier to show the local time while retreveing from the database.
- Issue#6maheshritgithub2024-11-02 10:55This check is good, but the logic could be improved by explicitly logging why a duplication might happen
- Issue#5maheshritgithub2024-11-02 10:51You calculate the checksum for each barcode separately in a loop. Consider extracting the checksum calculation logic to a helper method, which could improve readability and allow you to reuse it if needed.
- Issue#4maheshritgithub2024-11-02 10:49please use djangos logging statements like logger.debug(f"Barcode without checksum: {barcode_without_checksum} (Length: {len(barcode_without_checksum)})")
- Issue#3maheshritgithub2024-11-02 10:48The user variable here is outside of any method, which would result in an AttributeError since request is undefined at this scope. The user variable should be accessed within each request handler method (like get or post) to avoid such errors.
- Issue#2maheshritgithub2024-11-02 10:42If new_barcode returns an empty list (due to an error with length or checksum), you should handle this case to notify the client of the error
- Issue#1maheshritgithub2024-11-02 10:30Please remove the unnecessary files
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.