• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

kobotoolbox / kpi / 43074472147
65%
master: 76%

Build:
Build:
LAST BUILD BRANCH: dev-3367-remove-celery-beat-from-trash-bin
DEFAULT BRANCH: master
Ran 11 Nov 2026 06:11PM UTC
Jobs 10
Files 890
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Nov 2026 06:05PM UTC coverage: 85.934% (+0.005%) from 85.929%
43074472147

push

github

web-flow
fix(frontend): smarter asset resolving DEV-3076 (#7686)

### đŸ“Ŗ Summary

Project settings no longer flip back to outdated values when a save and
a project reload happen at the same time (an edge case scenario).

### 💭 Notes

Two requests for the same project can be in the air at once — a save
(`PATCH`) and a reload/fetch (`GET`) — and they can come back in either
order. `PermProtectedRoute` stored whichever landed last, so the slower,
older response could undo a save that was already on screen.

Changes here:

- `jsapp/js/assetUtils.ts` — new `getNewerAsset()`
- `jsapp/js/router/permProtectedRoute.tsx` — uses the new function
- `jsapp/js/assetUtils.tests.js` — four cases: older loses, newer wins,
timestamp tie, nothing to compare

Left alone on purpose: `assetStore` and the `assetCache` in `actions.js`
are last-writer-wins in exactly the same way. Many more consumers there,
so it requires some more thought put there.

### 👀 Preview steps

This is actually hard to test as it fixes an edge case scenario that was
found by robot. I have added some utility tests to ensure things work.
Please read the code carefully and then for the sake of ensuring things
still work do these steps:

1. â„šī¸ have an account and a deployed project with a few submissions
2. Project → Settings: change the project name and description, save —
the new values show straight away and survive navigating away and back
3. Project → Data → Table: hide a column and change the sort, then leave
the section and return — both stick
4. Project → Data → Map: change a map style, leave and come back — still
there
5. Project → Settings → Sharing: add a collaborator, then reopen the
project — the share is listed and the project still opens normally for
you
6. đŸŸĸ no section bounces back to a previous value, and nothing lands you
on an "Access denied" screen

10900 of 13720 branches covered (79.45%)

34115 of 39699 relevant lines covered (85.93%)

5.82 hits per line

Jobs
ID Job ID Ran Files Coverage
1 43074472147.1 11 Nov 2026 06:11PM UTC 885
54.38
2 43074472147.2 11 Nov 2026 06:11PM UTC 887
55.71
3 43074472147.3 11 Nov 2026 06:11PM UTC 887
51.36
4 43074472147.4 11 Nov 2026 06:11PM UTC 885
49.99
5 43074472147.5 11 Nov 2026 06:12PM UTC 885
57.39
6 43074472147.6 11 Nov 2026 06:13PM UTC 885
59.41
7 43074472147.7 11 Nov 2026 06:13PM UTC 887
58.98
8 43074472147.8 11 Nov 2026 06:14PM UTC 888
66.39
9 43074472147.9 11 Nov 2026 06:15PM UTC 887
60.59
10 43074472147.10 11 Nov 2026 06:16PM UTC 890
68.91
Source Files on build 43074472147
  • Tree
  • List 890
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • 393e55a3 on github
  • Prev Build on main (#43002679339)
  • Next Build on main (#43100829811)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc