queued 2026-09-24 18:57:49 · started 18:57:50 · finished 18:57:53 · duration 3s · target v2.0.0 · chromium · trigger: cli-adopted · batch: DEMO-013
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.62s | goto http://127.0.0.1:8000/demo/freight/login/ | 133 ms |
| +0.75s | fill #username | 68 ms |
| +0.82s | fill #password | 25 ms |
| +0.85s | click #login-btn | 128 ms |
| +0.98s | wait_for_selector #signed-in-user | 159 ms |
| +1.13s | ⏱ search shipments | 348 ms |
| +1.14s | goto http://127.0.0.1:8000/demo/freight/ops/shipments/ | 80 ms |
| +1.22s | fill #shipment-search | 62 ms |
| +1.28s | select_option #status-filter | 22 ms |
| +1.30s | click #apply-filters | 146 ms |
| +1.44s | wait_for_selector #result-count | 38 ms |
| +1.49s | inner_text #result-count | 6 ms |
| +1.50s | click #shipments-table th a[data-sort=eta] | 92 ms |
| +1.50s | ⏱ sort by ETA | 140 ms |
| +1.59s | wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta] | 48 ms |
| +1.64s | ⏱ open AF-100001 | 147 ms |
| +1.64s | click #shipments-table a:text-is('AF-100001') | 96 ms |
| +1.74s | wait_for_selector #ship-status | 51 ms |
| +1.90s | ⏱ save a note | 140 ms |
| +1.91s | fill #note-text | 23 ms |
| +1.93s | click #note-save | 66 ms |
| +1.99s | wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]) | 51 ms |
| +2.18s | 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-185750-r297/ |
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.62s] starting DEMO-013
[timing] goto http://127.0.0.1:8000/demo/freight/login/: 133ms
[timing] fill #username: 68ms
[timing] fill #password: 25ms
[timing] click #login-btn: 128ms
[timing] wait_for_selector #signed-in-user: 159ms
[test] [ 1.14s] signed in as tester
[timing] goto http://127.0.0.1:8000/demo/freight/ops/shipments/: 80ms
[timing] fill #shipment-search: 62ms
[timing] select_option #status-filter: 22ms
[timing] click #apply-filters: 146ms
[timing] wait_for_selector #result-count: 38ms
[timing] search shipments: 348ms
[timing] inner_text #result-count: 6ms
[test] [ 1.50s] Showing 1–2 of 2 shipments
[timing] click #shipments-table th a[data-sort=eta]: 92ms
[timing] wait_for_selector #shipments-table th[aria-sort] a[data-sort=eta]: 49ms
[timing] sort by ETA: 140ms
[timing] click #shipments-table a:text-is('AF-100001'): 96ms
[timing] wait_for_selector #ship-status: 51ms
[timing] open AF-100001: 147ms
[test] [ 1.90s] screenshot: 01-shipment.png
[timing] fill #note-text: 23ms
[timing] click #note-save: 66ms
[timing] wait_for_selector #notes-list .note-text:has-text('promised by Friday'), #note-error:not([hidden]): 51ms
[timing] save a note: 140ms
[test] [ 2.18s] screenshot: 02-note-failed.png
[timing] inner_text #note-error: 19ms
[test] [ 2.20s] 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.