Decide: what the two halves of the HTTP transport showed when run together
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- backend-api-design, documentation
Research direction
Read TRN-14 and ADRs 0011, 0014, 0017, 0027, and 0028, along with issue #132 and the records for HTTP-40 and HTTP-31. Compare the seven listed observations with D2 and step 5's last task (#12, task 8). Done means one short record is proposed and accepted that states each narrowing; the issue says this does not block #128 or #129.
Written by the indexing model from the issue text.
Description
The HTTP connector (#128) and the provider endpoints (#129) were run against each other on one tree before either merged. Calls, replies, each error kind, tokens, the principal, deadlines, the idempotency key and a burst of 20 concurrent calls agreed under WSGI and ASGI. What is left is in the records, which each half follows faithfully:
- A request that passed the caller's check can still come back
invalid_argument. TRN-14 and ADR 0017 Decision 9 step 2 say a caller that checks its own requests never receives that kind for one. Over HTTP the provider's host can still answer it: a body over its size limit (ADR 0011 row 12, HTTP-40), or plain HTTP where it requires HTTPS (row 5). In-process neither applies, so the same call succeeds there. To weigh: narrow the promise to requests that fail the caller's own check, or give both modes one limit (ADR 0011 open question 5). - A token's lifetime is shared by clock difference and waiting time. A provider accepts a token until
exp + 60on its own clock, so a call with no deadline that waits more than about 120 seconds before authentication isunauthenticated. To weigh: state it in ADR 0027 Decision 4, or choose a longer lifetime within spec 03's cap. - Framing. ADR 0011 Decision 4 lists the headers the host sets and says it sets no other; the endpoint also states
Content-Lengthon every response with a body, which connection reuse depends on. - A repeated
Content-Lengthunder ASGI. ADR 0011 says the server joins repeated fields; uvicorn merges equal values and refuses differing ones itself. - HEAD on the well-known paths. Django's WSGI servers drop
Content-Length: 0from a HEAD answer; ADR 0011's sentence follows whatever HTTP-31 says once #129 lands. - The reply body has no bound on the caller's side (ADR 0028 open question 1). To weigh: a bound, and the kind when it is passed.
- What a refusal may print. ADR 0014's table prints a refused key and a refused
BACKENDvalue, and a remote provider's url is never printed; #132 found a database password inneolith.E005. To weigh: one rule for every settings refusal.
How: one short record, proposed and accepted with step 5's last task (#12, task 8), stating each narrowing under D2. Nothing here blocks #128 or #129.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 5h 30m
- Merged PRs (30d)
- 85
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stack314/django-neolith
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#142 · 1 comment ·
Maintainers usually reply within 1 day
-
help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#141 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
stack314/django-neolith#140 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
stack314/django-neolith#126 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
stack314/django-neolith#119 · 2 comments ·
Maintainers usually reply within 1 day
All issues in stack314/django-neolith
Similar issues
-
automated endpoint-dead needs-curation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
almanac-data/climate-almanac#138 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
OceanDataTools/openrvdas#760 ·
Maintainers usually reply within 1 day
-
level/subtask type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
wazuh/wazuh-virtual-machines#1091 ·
Maintainers usually reply within 1 day
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·