-
Notifications
You must be signed in to change notification settings - Fork 0
[fix(ytdlp)] Stabilize progress streaming and temp file handling #13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
1ee3a23
b3e8245
5bdb6f9
d97e47c
cedfeaf
e0eebe3
593b2e4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,10 +1,10 @@ | ||
| ## Description | ||
|
|
||
| <!--- Describe your changes in short detail --> | ||
| ## Types of changes | ||
|
|
||
| <!-- '- [ ] file name(clickable): change made --> | ||
| - [ ] | ||
|
|
||
| ## Checklist | ||
|
|
||
| - [ ] Updated ChangeLog | ||
| - [ ] | ||
| - [ ] All tests passed. |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -46,3 +46,4 @@ nadunssh | |
| id_rsa | ||
| id_ed25519 | ||
| /postman/collections/*/.resources/definition.yaml | ||
| .agents | ||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| # Nadzu Backend - Engineering Standards & Policies | ||
|
|
||
| This document serves as the foundational mandate for all engineering work on this codebase. It applies to both human developers and AI agents. Strict adherence is required to maintain the "Anti-Corruption Layer" and high-performance nature of the system. | ||
| This document serves as the foundational mandate for all engineering work on naduns codebase. It applies to both human developers and AI agents. Strict adherence is required to maintain the security and high-performance nature of the system. | ||
|
|
||
| ## 1. Architectural Integrity | ||
|
|
||
|
|
@@ -61,9 +61,10 @@ This document serves as the foundational mandate for all engineering work on thi | |
| * **Clippy**: Must be zero-warning. | ||
| * **Rustfmt**: Must be applied to every file. | ||
| * **Makefile**: Use `make c` for a full validation suite before concluding any task. | ||
| * Use -j (nproc) for parallel builds and tests to speed up the shell commands. | ||
|
|
||
| ### Documentation | ||
| * All public-facing methods and services must have `///` (Rustdoc) comments explaining intent and behavior. | ||
| * All public-facing methods and services must have `///` (Rustdoc) comments explaining intent and behavior.do not over document, make guesses about the unseen code. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Clarify the documentation guideline. The current wording "do not over document, make guesses about the unseen code" is grammatically awkward and potentially contradictory—documentation guidelines typically discourage guessing. Consider rephrasing for clarity. 📝 Suggested fix-* All public-facing methods and services must have `///` (Rustdoc) comments explaining intent and behavior.do not over document, make guesses about the unseen code.
+* All public-facing methods and services must have `///` (Rustdoc) comments explaining intent and behavior. Avoid over-documentation; do not make assumptions about unseen code.🤖 Prompt for AI Agents |
||
| * Complex logic (like the Midnight Snap caching strategy) must be documented inline. | ||
|
|
||
| --- | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.