queued 2026-09-24 18:55:40 · started 18:56:47 · finished 18:56:50 · duration 3s · target v2.0.0 · chromium · trigger: cli-adopted · batch: 8 tests (terminal)
What went wrong
AssertionError: saving a note failed: 'The notes service is busy -- try again'
Technical details (full error)
AssertionError: saving a note failed: 'The notes service is busy -- try again'
Traceback (most recent call last):
File "/opt/pw-testhub/app/core/harness/run_test.py", line 737, in main
module.run(TimedPage(page, ctx), ctx)
File "/opt/pw-testhub/data/tests/DEMO-013__freight_shipments_and_notes.py", line 49, in run
raise AssertionError(f"saving a note failed: {page.inner_text('#note-error')!r}")
AssertionError: saving a note failed: 'The notes service is busy -- try again'
the page at the moment it failed
Activity replay 4 frames, captured only while the page was actually changing — idle waits are skipped automatically
+0.00s
Step timings follows the replay — click a step to see it there
| at | step | took |
|---|---|---|
| +0.60s | goto http://127.0.0.1:8000/demo/freight/login/ | 155 ms |
| +0.76s | fill #username | 112 ms |
| +0.88s | fill #password | 43 ms |
| +0.91s | click #login-btn | 178 ms |
| +1.09s | wait_for_selector #signed-in-user | 148 ms |
| +1.24s | ⏱ search shipments | 368 ms |
| +1.25s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/ | 84 ms |
| +1.33s | fill #shipment-search | 63 ms |
| +1.39s | select_option #status-filter | 67 ms |
| +1.45s | click #apply-filters | 107 ms |
| +1.56s | wait_for_selector #result-count | 46 ms |
| +1.62s | inner_text #result-count | 11 ms |
| +1.62s | click #shipments-table th a[data-sort=eta] | 125 ms |
| +1.63s | ⏱ sort by ETA | 186 ms |
| +1.76s | wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] | 61 ms |
| +1.81s | ⏱ open AF-100001 | 208 ms |
| +1.81s | click #shipments-table a:text-is('AF-100001') | 106 ms |
| +1.92s | wait_for_selector #ship-status | 102 ms |
| +2.18s | fill #note-text | 18 ms |
| +2.18s | ⏱ save a note | 148 ms |
| +2.20s | click #note-save | 63 ms |
| +2.26s | wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) | 66 ms |
| +2.45s | inner_text #note-error | 19 ms |
Times are when each step began, on the replay's clock. Add your own phases with
with ctx.timed("label"):.
Screenshots
Artifacts
| Run log | run.log |
| Playwright trace | trace.zip
open with: playwright show-trace trace.zip |
| Result JSON | result.json |
| Folder | results/DEMO-013/20260924-185647-r290/ |
Full log
Read from the S3 bucket (the last 20 KB; the whole file is the Run log link above).
[harness] test=DEMO-013 browser=chromium headed=False timeout=120s
[harness] target: http://127.0.0.1:8000/demo/
[test] [ 0.61s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 155ms
[timing] fill #username: 112ms
[timing] fill #password: 43ms
[timing] click #login-btn: 179ms
[timing] wait_for_selector #signed-in-user: 148ms
[test] [ 1.24s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 84ms
[timing] fill #shipment-search: 63ms
[timing] select_option #status-filter: 67ms
[timing] click #apply-filters: 107ms
[timing] wait_for_selector #result-count: 46ms
[timing] search shipments: 368ms
[timing] inner_text #result-count: 11ms
[test] [ 1.63s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 125ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 61ms
[timing] sort by ETA: 186ms
[timing] click #shipments-table a:text-is('AF-100001'): 106ms
[timing] wait_for_selector #ship-status: 102ms
[timing] open AF-100001: 208ms
[test] [ 2.18s] screenshot: 01-shipment.png
[timing] fill #note-text: 19ms
[timing] click #note-save: 63ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 66ms
[timing] save a note: 147ms
[test] [ 2.45s] screenshot: 02-note-failed.png
[timing] inner_text #note-error: 19ms
[test] [ 2.47s] FAILED: saving a note failed: 'The notes service is busy -- try again'
[harness] security: 0 high, 1 medium, 1 low
[harness] saved failure.png
[harness] saved trace.zip
[harness] saved video.webm
[harness] result: failed
Security observations what the browser noticed while this ran — not a penetration test
| Severity | Finding | What to do |
|---|---|---|
| medium | The application is served over plain HTTP http://127.0.0.1:8000/demo/ is not HTTPS, so anything typed into it travels the network in the clear and can be modified in transit. |
On an isolated lab network this may be a deliberate choice -- if so, note it and move on. Anywhere else, terminate TLS in front of the application. |
| low | Response advertises software version (server) server: pw-testhub -- this tells an attacker exactly what to look up known vulnerabilities for. |
Suppress or blank the server header at the proxy. |
| info | Cookie 'csrftoken' is readable by JavaScript (expected) This looks like a CSRF token, which the page's own JavaScript has to read in order to send it back. HttpOnly would break that. Nothing to do -- listed so you know it was checked and not missed. |
No action. Do check that SESSION cookies are HttpOnly. |
All of these appear together on the Security page.