[vilenarios]

getResponseErrorFromDioRespose threw when Dio had already decoded a JSON error body into a Map. The throw was an Error, not an Exception, so the chunk retry added in 4.0.1 did not run, and the upload stopped after its first chunk attempt.

Changes

• getResponseErrorFromDioRespose reads the error from a Map, List, String or empty body, and no longer throws.
• uploadTransaction counts a header the network already has as posted, and sends the chunks:
  • 208 "Transaction already processed.", as before
  • 400 "Transaction is already in the mempool." (pending for more than 10 minutes)
  • 400 "Transaction is already on the weave." (mined, while its anchor is still recent)
• New uploadTransactionChunks posts a transaction's chunks without posting its header. It covers transactions too old for a re-posted header to be recognised. This is an addition; existing functions are unchanged.
• The first chunk is sent on its own, and the rest fan out (up to 128) once it is accepted. Until the header reaches the nodes every chunk is rejected and retried, and the gateway forwards each attempt to several peers. Retrying every chunk at once multiplied that traffic for nothing.
• Version 4.1.0, because of the new API.

Testing

• test/chunk_upload_retry_test.dart covers:
  • each error body shape
  • a chunk retried after a 400 JSON response
  • a chunks-only upload, which posts no header
  • the header responses for pending, mined and refused transactions
  • a 3-chunk upload whose first chunk is rejected twice, which must send nothing else until that chunk is accepted
• The parser, retry, "already on the weave" and fan-out tests fail against the code before their fixes.
• The rest of the suite is unchanged. Two transactions_test.dart cases fail on master too, because they need arweave.net.

Follow-ups, not in this PR

• An AR.IO gateway's chunk response has no per-peer error strings, so _fatalChunkUploadErrors never matches through a gateway. A truly fatal chunk is retried for about 10 minutes before failing. That is slow, but it is not data loss.
• lib/src/models/transaction_uploader.dart (the http-package path) is unchanged.

After merge, tag v4.1.0 so ardrive-web can pin it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XxK9v6SqyxtV5g4yaXSkB1

Summary by CodeRabbit

• New Features
  • Added support for uploading transaction chunks without submitting the transaction header.
• Bug Fixes
  • Header uploads now succeed when the transaction is already in the mempool or on the weave.
  • Improved error-message handling across response formats, including plain text, JSON, and empty responses.
  • Updated chunk uploads to begin sequentially, then continue with up to 128 concurrent uploads, replacing each completed upload as it finishes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 346d7550-d773-4750-b81c-c035af6c4d2e

📥 Commits

Reviewing files that changed from the base of the PR and between e399497 and 1573dae.

📒 Files selected for processing: 3

• lib/src/streams/transaction_uploader.dart
• pubspec.yaml
• test/chunk_upload_retry_test.dart

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

The Dio response-error utility now handles response bodies by runtime type. Transaction uploads accept specified already-processed header responses, use revised chunk scheduling, and support chunk-only uploads. Tests cover response decoding and upload behavior. The package version changes to 4.1.0.

Changes: Dio response decoding

Layer / File(s)	Summary
Response body handling lib/src/utils.dart, test/chunk_upload_retry_test.dart	The utility extracts string errors and nested string data, preserves unparseable strings, JSON-encodes other non-null values, and returns an empty string for null. Tests cover decoded and string-encoded JSON, legacy nested errors, gateway results, plain text, and empty bodies.

Transaction chunk uploads

Layer / File(s)	Summary
Header handling and chunk-only uploads lib/src/streams/transaction_uploader.dart, test/chunk_upload_retry_test.dart, pubspec.yaml	HTTP 400 header responses containing “already in the mempool” or “already on the weave” are accepted. uploadTransactionChunks uploads chunks without posting the header. Tests cover accepted and unrelated rejected header responses, and chunk-only uploads. The package version changes to 4.1.0.
Chunk scheduling and retry lib/src/streams/transaction_uploader.dart, test/chunk_upload_retry_test.dart	The uploader sends the first chunk alone, then starts up to 128 uploads and starts one replacement upload for each later completion. Tests cover retrying rejected chunks and upload progress.

Priority: ➖ Normal

Estimated code review effort: 3 (Moderate) | ~20 minutes

Change: Bug fix

Suggested reviewers: thiagocarvalhodev

Merge Risk: ⚪ Minimal · up to 1573d

The inspected upload and retry paths show no outstanding issue requiring a fix before merge.

Pre-merge checks: 5

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title accurately identifies the primary change: fixing chunk-upload retries when Dio returns an error response with a JSON body. It does not mention the additional chunk-only upload and already-ac…

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)

Full details: Title check

Explanation

The title accurately identifies the primary change: fixing chunk-upload retries when Dio returns an error response with a JSON body. It does not mention the additional chunk-only upload and already-accepted-header behavior, but the title need not cover every change.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}