Retry GitHub stats queries #52
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
❌ Deploy Preview for nf-core-stats failed. Why did it fail? →
|
|
@mashehu is this ready for review? |
… documentation - Introduced a new SQL query to track pipeline development periods in `pipeline_timeline.sql`. - Added a new timeline page in `timeline.md` to visualize pipeline development cycles. - Updated `index.md` to link to the new timeline documentation. - Marked an extraneous dependency in `package-lock.json`. - Created a new configuration file for MCP servers in `mcp.json`.
- Changed SQL queries to create a stacked bar chart for pipeline lifecycle, showing development and released time. - Updated the data structure for the timeline visualization to reflect the new lifecycle data. - Added a new SQL query for a comprehensive lifecycle summary of each pipeline. - Enhanced the development vs released time analysis with additional statistics.
…e visualization - Updated section titles and descriptions for clarity on pipeline lifecycle. - Simplified SQL queries for lifecycle summary and adjusted data structure for better visualization. - Enhanced DataTable to include detailed columns for development and release durations with appropriate bar colors.
- Adjusted SQL queries to improve the calculation of development and release durations. - Modified the timeline documentation to reflect changes in the SQL structure and data retrieval. - Changed the date filtering in the SQL query to start from 2017 for a broader data range.
…ocus on first release dates - Revised documentation to clarify that the timeline now tracks time to **first release** instead of last release. - Adjusted SQL queries to calculate development durations based on **first release** dates. - Enhanced insights section to reflect the importance of first release analysis in understanding pipeline development.
…guration - Removed redundant section header for Pipeline Lifecycle Summary. - Added title to DataTable for clarity. - Adjusted DataTable to display 20 rows for improved data visibility.
… scheme - Updated color descriptions for timeline bar charts to improve clarity. - Adjusted bar colors in DataTable to align with nf-core branding for better visualization of development and release durations.
…tion - Added grouping by year in SQL query to improve data organization. - Updated DataTable title for clarity and adjusted grouping settings for better visualization. - Enhanced column titles with icons for improved user experience.
- Updated date formatting in DataTable for consistency and clarity. - Enhanced SQL query to include median, min, and max development days for released pipelines. - Added new sections for development time trends and comparative analysis to provide deeper insights into pipeline performance.
- Added date formatting for x-axis in DataTable to ensure consistency across visualizations. - Enhanced column definition for 'Year' to include formatting for improved clarity.
- Modified SQL query to cast start_year as an integer and added a new column for truncated year date. - Enhanced clarity in data representation for better trend analysis.
…se timing - Revised terminology in the documentation to specify "days until first release" instead of "average development times." - Updated DataTable column titles to reflect the new focus on release timing, enhancing clarity in data representation.
For the life of me, I cannot find where this is added.
|
okay, looks like we are now making too many api calls for one token... |
https://dlthub.com/docs/general-usage/http/requests#retry-rules |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.