Skip to content

[doc] Update README - #170

Merged
0oshowero0 merged 1 commit into
Ascend:mainfrom
0oshowero0:update_doc
Sep 8, 2026
Merged

0oshowero0 merged 1 commit into
Ascend:mainfrom
0oshowero0:update_doc

Conversation

@0oshowero0

Copy link
Copy Markdown
Collaborator

As title

Signed-off-by: 0oshowero0 <o0shower0o@outlook.com>
Copilot AI lite review requested due to automatic review settings September 8, 2026 05:08
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-08T05:10:36.831675Z 2bad65e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@ascend-robot

Copy link
Copy Markdown

CLA Signature Pass

0oshowero0, thanks for your pull request. All authors of the commits have signed the CLA. 👍

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is a straightforward README update with consistent formatting and no code/behavioral impact.

Pull request overview

Updates the project README’s “🔄 Updates” section to reflect an additional real-world adoption of TransferQueue, keeping the repository’s status/current usage information up to date.

Changes:

  • Add a new “September 8, 2026” update noting adoption in Meshy and describing TransferQueue’s role in that system.
File summaries
File Description
README.md Adds a new entry in the Updates section announcing adoption in Meshy.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@0oshowero0
0oshowero0 merged commit d45bfe8 into Ascend:main Sep 8, 2026
7 checks passed
Ginray added a commit to Ginray/TransferQueue that referenced this pull request Oct 9, 2026
Sync 11 main PRs (Ascend#162, Ascend#167, Ascend#168, Ascend#170-Ascend#172, Ascend#174, Ascend#175, Ascend#177-Ascend#179)
into the payload-transfer branch. Main's PR history is preserved; the
payload transfer abstraction stays on top.

Conflict resolutions:
- SimpleStorageUnit: keep main's config-dict constructor, hybrid
  memory/SSD storage, proxy identity filter, arrival counters, accept
  probe, and checkpoint delegation; the worker dispatches PUT/GET
  families to the configured PayloadTransfer as before.
- AsyncSimpleStorageManager: keep main's socket pools, retry with
  diagnosis, and heavy-request logging; per-unit put/get delegate to
  the configured PayloadTransfer.
- Bootstrap: keep main's config-dict actor construction plus payload
  transfer validation and NIXL endpoint collection.

Semantic adaptations (not textual conflicts):
- Add PayloadTransferTimeout (base.py) carrying wire_bytes; both
  backends raise it on an unanswered control message, and the manager
  translates it to StorageUnitTimeout so Ascend#171 retry/diagnosis covers
  the ZMQ and NIXL-UCX paths uniformly.
- PayloadTransfer.put returns payload bytes moved, so Ascend#171's manager
  side heavy-put logging keeps true wire sizes per backend.

Verified: python -m compileall -q transfer_queue tutorial tests clean;
ruff check clean; pytest 622 passed, 8 skipped, 8 errors (the 8 errors
are the pre-existing optional-Yuanrong-backend baseline).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants