Skip to content

add tests for deck-layers fourwings heatmap layer#4151

Merged
j8seangel merged 2 commits into
developfrom
deck-layers/test
Jul 14, 2026
Merged

add tests for deck-layers fourwings heatmap layer#4151
j8seangel merged 2 commits into
developfrom
deck-layers/test

Conversation

@j8seangel

@j8seangel j8seangel commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@j8seangel j8seangel requested a review from fernand0q July 6, 2026 14:26
@github-actions

github-actions Bot commented Jul 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Test Results

✅ deck-layers:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/deck-layers
 ✓  deck-layers  src/layers/fourwings/heatmap/FourwingsHeatmapLayer.spec.ts (12 tests) 88ms
 ✓  deck-layers  src/layers/fourwings/heatmap/fourwings-heatmap.utils.spec.ts (33 tests) 100ms
stderr | src/layers/fourwings/heatmap/FourwingsHeatmapTileLayer.spec.ts
luma.gl: This version of luma.gl has already been initialized
stderr | src/layers/fourwings/FourwingsLayer.spec.ts
luma.gl: This version of luma.gl has already been initialized
Compiling TypeScript files for project "deck-layers"...
 ✓  deck-layers  src/layers/fourwings/heatmap/FourwingsHeatmapStaticLayer.spec.ts (8 tests) 22ms
 ✓  deck-layers  src/layers/fourwings/heatmap/FourwingsHeatmapTileLayer.spec.ts (19 tests) 102ms
 ✓  deck-layers  src/layers/fourwings/FourwingsLayer.spec.ts (4 tests) 104ms
 Test Files  5 passed (5)
      Tests  76 passed (76)
   Start at  17:53:10
   Duration  9.45s (transform 9.79s, setup 0ms, import 22.78s, tests 416ms, environment 1ms)
Done compiling TypeScript files for project "deck-layers".
✅ dataviews-client:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/dataviews-client
 ✓  dataviews-client  src/url-workspace/url-workspace.spec.ts (40 tests) 65ms
 Test Files  1 passed (1)
      Tests  40 passed (40)
   Start at  17:53:05
   Duration  2.33s (transform 232ms, setup 0ms, import 620ms, tests 65ms, environment 1.33s)
Compiling TypeScript files for project "dataviews-client"...
Done compiling TypeScript files for project "dataviews-client".
✅ deck-layer-composer:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/deck-layer-composer
stderr | src/resolvers/resolvers.spec.ts > resolvers > dataviewToDeckLayer > Fourwings layers > should create FourwingsClustersLayer for FourwingsTileCluster type
No datasetId found for dataview {
  id: 'test-dataview',
  category: 'activity',
  config: { type: 'FOURWINGS_TILE_CLUSTER' },
  datasetsConfig: [],
  datasets: []
}
stderr | src/resolvers/resolvers.spec.ts > resolvers > dataviewToDeckLayer > Context layers > should create PolygonsLayer for Polygons type
No url found for polygon resolver {
  id: 'test-dataview',
  category: 'context',
  config: { type: 'POLYGONS' },
  datasetsConfig: [],
  datasets: []
}
 ✓  deck-layer-composer  src/resolvers/resolvers.spec.ts (20 tests) 46ms
 ✓  deck-layer-composer  src/hooks/deck-layers-composer.hooks.spec.ts (22 tests | 2 skipped) 633ms
 Test Files  2 passed (2)
      Tests  40 passed | 2 skipped (42)
   Start at  17:53:26
   Duration  7.01s (transform 3.72s, setup 0ms, import 9.42s, tests 679ms, environment 2.83s)
❌ fishing-map:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/apps/fishing-map
◇ injected env (0) from apps/fishing-map/.env // tip: ⌘ enable debugging { debug: true }
========================================
Authentication Setup Started (chromium)
========================================
Email configured: Yes
Password configured: Yes (hidden)
🔐 Setting up authenticated browser state...
Launching Playwright browser...
Starting auth proxy server...
Navigating to proxy login URL: http://localhost:3000/login
   [BROWSER CONSOLE] error: Connecting to 'https://ad.doubleclick.net/ccm/s/collect?auid=1207976632.1784051579&gtm=45Xe67d0v810016194za200zd810016194xea' violates the following Content Security Policy directive: "connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com https://*.g.doubleclick.net https://*.google.com https://*.google.es https://challenges.cloudflare.com". The action has been blocked.
   [BROWSER CONSOLE] error: Fetch API cannot load https://ad.doubleclick.net/ccm/s/collect?auid=1207976632.1784051579&gtm=45Xe67d0v810016194za200zd810016194xea. Refused to connect because it violates the document's Content Security Policy.
   [BROWSER CONSOLE] error: Executing inline script violates the following Content Security Policy directive 'script-src 'nonce-49285855ba3743d41a5d62682ac296c1' 'self' https://*.googletagmanager.com https://*.google-analytics.com https://challenges.cloudflare.com 'unsafe-eval''. Either the 'unsafe-inline' keyword, a hash ('sha256-aBVupgi3uDqPBRiVgRTJfWuvbuLQZdE/xsdxrWsl9UY='), or a nonce ('nonce-...') is required to enable inline execution. The action has been blocked.
Navigated to auth page: https://gateway.api.dev.globalfishingwatch.org/v3/auth?client=gfw&locale=en&callback=http%3A%2F%2Flocalhost%3A3000%2Fauth%2Fcallback
Filling in email...
Filling in password...
Clicking login button...
Waiting for redirect to proxy callback with access token...
Access token captured from callback URL: Yes (length: 30)
Exchanging access token for API tokens with GFWAPI...
Token retrieved: Yes (length: 818)
Refresh token retrieved: Yes (length: 92)
✅ Authentication tokens saved to /home/runner/work/frontend/frontend/apps/fishing-map/test/.auth/tokens.json
Auth proxy server stopped
Browser closed
========================================
Authentication Setup Completed Successfully
========================================
========================================
Authentication Setup Started (global-setup)
========================================
✅ Valid tokens found, skipping auth setup
5:53:01 PM [vite] (client) Re-optimizing dependencies because vite config has changed
5:53:02 PM [vite] (client) [optimizer] scanning dependencies...
5:53:04 PM [vite] (client) [optimizer] bundling dependencies...
stderr | test/integration/Reports.spec.tsx > Reports > should navigate to a report from eez
luma.gl: WebGL debug mode activated. Performance reduced.
stderr | test/integration/Reports.spec.tsx > Reports > should navigate to a report from eez
luma.gl: Binding pathStyleUniforms not set: Not found in shader layout.
stderr | test/integration/Reports.spec.tsx > Reports > should navigate to a report from eez
{
  "message": "signal is aborted without reason",
  "metadata": {},
  "status": 20,
}
stderr | test/integration/Reports.spec.tsx > Reports > should navigate to a report from eez
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout 4845.707999999999ms exceeded.
Call log:
  - taking element screenshot
  - waiting for fonts to load...
  - fonts loaded
  - attempting scroll into view action
    - waiting for element to be stable
]
stderr | test/integration/Reports.spec.tsx > Reports > should display the date chosen in the timebar with the imprecision tolerance in the report description
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Reports > should display the date chosen in the timebar with the imprecision tolerance in the report description
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Reports > should display the date chosen in the timebar with the imprecision tolerance in the report description
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Reports > should display the date chosen in the timebar with the imprecision tolerance in the report description
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Reports > should update report data when filter changes
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Reports > should update report data when filter changes
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Reports > should update report data when filter changes
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Reports > should update report data when filter changes
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Global reports > should open global report when clicking on highlighted workspace in reports category
React-Modal: "parentSelector" prop did not returned any DOM element. Make sure that the parent element is unmounted to avoid any memory leaks.
stderr | test/integration/Reports.spec.tsx > Global reports > should open global report when clicking on highlighted workspace in reports category
DataviewInstance id: viirs doesn't have a valid dataview (undefined)
stderr | test/integration/Reports.spec.tsx > Global reports > should have activity, events and detections tabs
DataviewInstance id: viirs doesn't have a valid dataview (undefined)
stderr | test/integration/Reports.spec.tsx > Global reports > should display the same number in the graph as in the timeseries
DataviewInstance id: viirs doesn't have a valid dataview (undefined)
stderr | test/integration/Reports.spec.tsx > Global reports > should change dataviews when changing tabs
DataviewInstance id: viirs doesn't have a valid dataview (undefined)
stderr | test/integration/Reports.spec.tsx > Global reports > should show detections in detections tab
DataviewInstance id: viirs doesn't have a valid dataview (undefined)
stderr | test/integration/Reports.spec.tsx > Private user reports > should show correct access message for private reports
{
  "message": "Not authorized by permissions",
  "metadata": {},
  "refreshError": true,
  "status": 401,
}
stderr | test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/12/13]
stderr | test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...-layers/5/13/13]
stderr | test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().locator('body')
]
 ❯  fishing-map-chromium  test/integration/Reports.spec.tsx (18 tests | 8 failed) 517745ms
     × should navigate to a report from eez 57494ms
     ✓ should display the date chosen in the timebar with the imprecision tolerance in the report description  23750ms
     ✓ should show same report data at different zoom levels  15499ms
     ✓ should update report data when timebar changes  27693ms
     ✓ should update report data when filter changes  28318ms
     ✓ should show no data message when no data  14063ms
     × should add new subcategory option when new layer is added from layer library 31085ms
     ✓ should open global report when clicking on highlighted workspace in reports category  12055ms
     ✓ should have activity, events and detections tabs  1024ms
     × should display the same number in the graph as in the timeseries 30274ms
     ✓ should change dataviews when changing tabs  13090ms
     × should show detections in detections tab 34955ms
     ✓ should show correct access message for private reports  1430ms
     × should show user reports when user is logged in 61558ms
     × should correctly display others points reports data 61080ms
     ✓ should show second selector when choose data comparison mode  19586ms
     × should show both dataviews in map when compared data is selected 31628ms
     × should show both dataviews in graph when compared data is selected 52559ms
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should open vessel popup on vessel click and show tile related info
luma.gl: WebGL debug mode activated. Performance reduced.
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should open vessel popup on vessel click and show tile related info
luma.gl: Binding pathStyleUniforms not set: Not found in shader layout.
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should open vessel popup on vessel click and show tile related info
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout -410.04000000003725ms exceeded.
Call log:
  - taking element screenshot
]
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should be able to close an opened popup
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout -383.4660000000149ms exceeded.
Call log:
  - taking element screenshot
]
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should be able to navigate to vessel viewer inside the vessel popup
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout -391.9449999999488ms exceeded.
Call log:
  - taking element screenshot
]
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should display the vessel track on the timebar
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout 5000ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().locator('body')
    - locator resolved to visible <body data-testid="__vitest_0__">…</body>
]
stderr | test/integration/Vessels.spec.tsx > Vessel map popup > should be able to interact with vessels after filtering by flag
[vitest] Failed to take a screenshot [TimeoutError: locator.screenshot: Timeout -132.9299999999348ms exceeded.
Call log:
  - taking element screenshot
]
 ❯  fishing-map-chromium  test/integration/Vessels.spec.tsx (9 tests | 6 failed) 263385ms
     × should open vessel popup on vessel click and show tile related info 37253ms
     × should be able to close an opened popup 37015ms
     × should be able to navigate to vessel viewer inside the vessel popup 38238ms
     × should display the vessel track on the timebar 37849ms
     × should be able to see vessel info on hover and pin a vessel to the map to see it on the sidebar 16365ms
     ✓ should show vessel info on vessel hover  25171ms
     ✓ should show vessel name, flag and date on vessel name hover on sidebar  20653ms
     ✓ should be able to filter vessels by flag  13681ms
     × should be able to interact with vessels after filtering by flag 37016ms
 ↓  fishing-map-chromium  test/integration/UserDatasets.spec.tsx (7 tests | 7 skipped)
stderr | test/integration/Datasets.spec.tsx > Datasets > should add reference data layer
luma.gl: WebGL debug mode activated. Performance reduced.
stderr | test/integration/Datasets.spec.tsx > Datasets > should add reference data layer
luma.gl: Binding pathStyleUniforms not set: Not found in shader layout.
 ✓  fishing-map-chromium  test/integration/Datasets.spec.tsx (5 tests) 56716ms
     ✓ should add reference data layer  15138ms
     ✓ should add environment data layer  9435ms
     ✓ should add events data layer  7832ms
     ✓ should add activity data layer  10082ms
     ✓ should preserve other layers when removing layer  14099ms
stderr | test/integration/Map.spec.tsx > Map > should pass zoom, latitude and longitude changes of query params to map state
luma.gl: WebGL debug mode activated. Performance reduced.
 ❯  fishing-map-chromium  test/integration/Map.spec.tsx (8 tests | 2 failed) 81652ms
     ✓ should render a map element and it should be loaded and with the default state  2193ms
     ✓ should pass zoom, latitude and longitude changes of query params to map state  11993ms
     ✓ should preserve map state when adding a new layer  8656ms
     ✓ should preserve map state when removing a layer  4002ms
     ✓ should update layers when interacting with the map  6409ms
     × should reflect period changes on the state and map 6936ms
     ✓ should preserve map state when changing period  9313ms
     × should be able to set map visualization to positions and see the corresponding layers on the map 32000ms
stderr | test/integration/VesselViewer.spec.tsx > Vessel viewer > should renders tabs and vessel basic info
luma.gl: WebGL debug mode activated. Performance reduced.
 ❯  fishing-map-chromium  test/integration/VesselViewer.spec.tsx (7 tests | 6 failed) 192491ms
     × should renders tabs and vessel basic info 30100ms
     ✓ should change tab when clicking on a tab  11553ms
     × should render summary tab by type 30129ms
     × should render summary tab by timeline 30134ms
     × should render areas tab and its tabs 30131ms
     × should render related vessels tab 30132ms
     × should render insights tab 30131ms
 ❯  fishing-map-chromium  test/integration/Polygon.spec.tsx (3 tests | 1 failed | 2 skipped) 131ms
     × should be able to navigate to the polygon editor
     ↓ should load the polygon in the map
     ↓ should be able to draw a new polygon, see it in the map and delete it
stderr | test/integration/Timebar.spec.tsx > App Timebar Integration > the map should be interactive after timebar interaction
luma.gl: WebGL debug mode activated. Performance reduced.
stderr | test/integration/Timebar.spec.tsx > App Timebar Integration > the map should be interactive after timebar interaction
luma.gl: Binding pathStyleUniforms not set: Not found in shader layout.
 ✓  fishing-map-chromium  test/integration/Timebar.spec.tsx (3 tests) 36848ms
     ✓ the map should be interactive after timebar interaction  15516ms
     ✓ events should be visible on timebar  6367ms
     ✓ detections should be visible on timebar  14699ms
stderr | test/integration/Sidebar.spec.tsx > Sidebar tools > should change language from selector
React-Modal: "parentSelector" prop did not returned any DOM element. Make sure that the parent element is unmounted to avoid any memory leaks.
stderr | test/integration/Sidebar.spec.tsx > Sidebar tools > should show help hints and allow dismissing one
luma.gl: WebGL debug mode activated. Performance reduced.
 ✓  fishing-map-chromium  test/integration/Sidebar.spec.tsx (5 tests) 13526ms
     ✓ should open feedback modal  2714ms
     ✓ should change language from selector  779ms
     ✓ should toggle sidebar  3996ms
     ✓ should show help hints and allow dismissing one  1599ms
     ✓ should restore help hints when requested  4102ms
 ✓  fishing-map-chromium  test/utils/store/testing-store-middleware.spec.ts (7 tests) 372ms
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: context-layer-high-seas doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: global-sea-surface-temperature doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: global-water-salinity doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: global-chlorophyl doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: encounter-events doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: sar-match doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: viirs-match doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: sar-match doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
DataviewInstance id: viirs-match doesn't have a valid dataview (undefined)
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
deck: initialization of ContextLayer({id: 'basemap'}): deck.gl: assertion failed. [Error: deck.gl: assertion failed.]
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
deck: initialization of PMTilesLayer({id: 'basemap-bathimetry'}): deck.gl: assertion failed. [Error: deck.gl: assertion failed.]
stderr | test/integration/MarineManager.spec.tsx > Marine Manager > should show workspace layers matching the workspace configuration
deck: initialization of PMTilesLayer({id: 'basemap-landmass'}): deck.gl: assertion failed. [Error: deck.gl: assertion failed.]
 ❯  fishing-map-chromium  test/integration/MarineManager.spec.tsx (2 tests | 1 failed) 7258ms
     × should be able to navigate to marine manager workspace through sidebar 3262ms
     ✓ should show workspace layers matching the workspace configuration  3688ms
stderr | unknown test
[Error: Failed to fetch resource (404) : https://gateway.api.dev.globalfi...t-layers/5/0/17]
 ❯  fishing-map-chromium  test/integration/VesselSearch.spec.tsx (3 tests | 3 failed) 68757ms
     × can search for a vessel and see it on the map 30093ms
     × preserves vessel search value when navigating away and back 7999ms
     × reacts to clearing the search input 30517ms
 ✓  fishing-map-chromium  test/integration/VesselsVMSBrazil.spec.tsx (2 tests) 13544ms
     ✓ should render public VMS Brazil identity fields  10185ms
     ✓ should render private-only VMS Brazil identity fields  3226ms
stderr | unknown test
luma.gl: WebGL debug mode activated. Performance reduced.
 ✓  fishing-map-chromium  features/dataviews/dataviews.utils.spec.ts (4 tests) 1330ms
stderr | test/integration/PrivateWorkspace.spec.tsx > PrivateWorkspace > should not be able to navigate to the private workspace if not authenticated
{
  "message": "Not authorized by permissions",
  "metadata": {},
  "refreshError": true,
  "status": 401,
}
 ✓  fishing-map-chromium  test/integration/PrivateWorkspace.spec.tsx (4 tests) 7387ms
     ✓ should not be able to navigate to the private workspace if not authenticated  1598ms
     ✓ should be able to navigate to the private workspace if authenticated  1811ms
     ✓ should be able to navigate to a password-protected workspace if correct password is used  1878ms
     ✓ should not be able to navigate to a password-protected workspace if incorrect password is used  1963ms
stderr | test/integration/App.spec.tsx > Fishing Map App > should preserve map previous state on layer toggle
luma.gl: WebGL debug mode activated. Performance reduced.
 ✓  fishing-map-chromium  test/integration/App.spec.tsx (2 tests) 8091ms
     ✓ should reflect store changes on layer toggle  2160ms
     ✓ should preserve map previous state on layer toggle  5793ms
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should render Timebar component with heatmap visualization by default
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
stderr | features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
Warning: useRouter must be used inside a <RouterProvider> component!
 ❯  fishing-map-chromium  features/timebar/Timebar.spec.tsx (2 tests | 1 failed) 443ms
     ✓ should render Timebar component with heatmap visualization by default 86ms
     × should call onTimebarChange with new time interval on yearly data button click 290ms
stderr | test/integration/User.spec.tsx > User expiration > should show expired session warning toast
luma.gl: WebGL debug mode activated. Performance reduced.
 ❯  fishing-map-chromium  test/integration/User.spec.tsx (1 test | 1 failed) 30703ms
     × should show expired session warning toast 30520ms
stderr | features/workspace/user/UserSection/UserSection.test.tsx > UserSection > should have a login link if the user is a guest
Deprecated datasets:
stdout | features/workspace/user/UserSection/UserSection.test.tsx > UserSection > should have a login link if the user is a guest
{
  "public-global-encounters-events:v4.0": "public-global-encounters-events:v5.0",
  "public-global-fishing-effort:v4.0": "public-global-fishing-effort:v5.0",
  "public-global-fishing-events:v4.0": "public-global-fishing-events:v5.0",
  "public-global-loitering-events:v4.0": "public-global-loitering-events:v5.0",
  "public-global-port-visits-events:v4.0": "public-global-port-visits-events:v5.0",
  "public-global-presence:v4.0": "public-global-presence:v5.0",
  "public-global-vessel-identity:v4.0": "public-global-vessel-identity:v5.0",
}
 ✓  fishing-map-chromium  features/workspace/user/UserSection/UserSection.test.tsx (1 test) 5035ms
     ✓ should have a login link if the user is a guest  4968ms
⎯⎯⎯⎯⎯⎯ Failed Tests 29 ⎯⎯⎯⎯⎯⎯⎯
 FAIL   fishing-map-chromium  features/timebar/Timebar.spec.tsx > Timebar > should call onTimebarChange with new time interval on yearly data button click
AssertionError: expected "vi.fn()" to be called with arguments: [ '2012-01-01T00:00:00.000Z', …(1) ]
Received:
  1st vi.fn() call:
  [
    "2012-01-01T00:00:00.000Z",
    "2026-12-31T23:59:59.999Z",
+   "YEAR_INTERVAL_BUTTON",
  ]

Number of calls: 1

Failure screenshot:
  - apps/fishing-map/features/timebar/__screenshots__/Timebar.spec.tsx/Timebar-should-call-onTimebarChange-with-new-time-interval-on-yearly-data-button-click-1.png
 ❯ features/timebar/Timebar.spec.tsx:54:31
     52|
     53|     // Now you can assert on the spy
     54|     expect(onTimebarChangeSpy).toHaveBeenCalledWith(
       |                               ^
     55|       '2012-01-01T00:00:00.000Z',
     56|       '2026-12-31T23:59:59.999Z'
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/29]⎯
 FAIL   fishing-map-chromium  test/integration/Map.spec.tsx > Map > should reflect period changes on the state and map
AssertionError: expected { …(2) } to match object { …(2) }
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Map.spec.tsx/Map-should-reflect-period-changes-on-the-state-and-map-1.png
- Expected
+ Received
  {
-   "end": "2026-12-31T23:59:59.999Z",
+   "end": "2027-01-01T00:00:00.000Z",
    "start": "2012-01-01T00:00:00.000Z",
  }
 ❯ test/integration/Map.spec.tsx:156:22
    154|     const deckLayersState = jotaiStore.get(deckLayersStateAtom)
    155|
    156|     expect(timerange).toMatchObject({
       |                      ^
    157|       start: '2012-01-01T00:00:00.000Z',
    158|       end: '2026-12-31T23:59:59.999Z',
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/29]⎯
 FAIL   fishing-map-chromium  test/integration/Map.spec.tsx > Map > should be able to set map visualization to positions and see the corresponding layers on the map
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Map.spec.tsx/Map-should-be-able-to-set-map-visualization-to-positions-and-see-the-corresponding-layers-on-the-map-1.png
 ❯ test/integration/Map.spec.tsx:188:2
    186|   })
    187|
    188|   it('should be able to set map visualization to positions and see the…
       |  ^
    189|     const store = makeStore(defaultState)
    190|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/29]⎯
 FAIL   fishing-map-chromium  test/integration/MarineManager.spec.tsx > Marine Manager > should be able to navigate to marine manager workspace through sidebar
AssertionError: expected undefined to match object { type: 'WORKSPACE', …(3) }
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/MarineManager.spec.tsx/Marine-Manager-should-be-able-to-navigate-to-marine-manager-workspace-through-sidebar-1.png
- Expected:
{
  "meta": {
    "location": {
      "current": {
        "pathname": "/marine-manager/fiji-public",
        "payload": {
          "category": "marine-manager",
          "workspaceId": "fiji-public",
        },
      },
      "kind": StringMatching /redirect|push/,
      "prev": Any<Object>,
    },
  },
  "payload": {
    "category": "marine-manager",
    "workspaceId": "fiji-public",
  },
  "replaceQuery": true,
  "type": "WORKSPACE",
}
+ Received:
undefined
 ❯ test/integration/MarineManager.spec.tsx:27:19
     25|     const action = testingMiddleware.getLastActionByType('WORKSPACE')
     26|
     27|     expect(action).toMatchObject({
       |                   ^
     28|       type: 'WORKSPACE',
     29|       payload: {
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/29]⎯
 FAIL   fishing-map-chromium  test/integration/Polygon.spec.tsx > Polygon > should be able to navigate to the polygon editor
Error: [Vitest] Unexpected .only modifier. Remove it or pass --allowOnly argument to bypass this error
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Reports > should navigate to a report from eez
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Reports.spec.tsx:130:2
    128|   })
    129|
    130|   it('should navigate to a report from eez', async () => {
       |  ^
    131|     const store = makeStore(defaultState)
    132|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Reports > should add new subcategory option when new layer is added from layer library
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Reports-should-add-new-subcategory-option-when-new-layer-is-added-from-layer-library-1.png
 ❯ test/integration/Reports.spec.tsx:289:2
    287|   })
    288|
    289|   it('should add new subcategory option when new layer is added from l…
       |  ^
    290|     const store = makeStore(defaultState)
    291|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[7/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Global reports > should display the same number in the graph as in the timeseries
VitestBrowserElementError: Cannot find element with locator: page.getByTestId('evolution-timeseries-chart')
<body
  class=""
>
  
  

  <span
    aria-hidden="true"
    id="recharts_measurement_span"
    style="position: absolute; top: -20000px; left: 0px; padding: 0px; margin: 0px; border-width: medium; border-style: none; border-color: currentcolor; border-image: initial; white-space: pre; font-size: 12px; letter-spacing: normal;"
  >
    20
  </span>
  <div
    id="__root__"
  >
    <a
      class="print-only"
      href="https://globalfishingwatch.org"
    >
      <svg
        aria-label="Global Fishing Watch "
        class="_container_13m0y_1"
        height="60"
        viewBox="20 0 220 60"
        width="200"
        xmlns="http://www.w3.org/2000/svg"
      >
        <g
          aria-hidden="true"
          fill="none"
          fill-rule="evenodd"
          focusable="false"
        >
          <path
            d="M23.1 27.83c-.08.16-2.25 4.5.57 8.76.83 1.25 1.76 2.24 4.1 3.8 3.38 2.26 7.42 6.16 8.4 8.45.1.21.36.59-.06.83-.73.41-1.75.31-2.16.25l-.12-.02c-4.75-.88-14.5-5-13.8-13.8.18-2.21.98-4.87 3.07-8.27zm9.92-8.64c.7-.08 2.98-.15 3.08.08.07.17-.83.5-.87.52-5.22 1.98-6.97 3.16-7.22 3.3-3.3 2.01-4.71 4.35-4.82 4.57 1.48-3.1 5.2-7.93 9.83-8.47z"
            fill="#8ABBC7"
          />
          <path
            d="M40.45 19.2l.64 1.16a17.1 17.1 0 011.52 3.94c.27 1.1.39 2.23.31 3.37a9.39 9.39 0 01-1.72 4.84 12.9 12.9 0 01-3.29 3.2 20.3 20.3 0 01-7.02 3.08c-.4.09-.8.16-1.2.19a3.39 3.39 0 01-1.3-.17c-.43-.17-.5-.43-.28-.83a13.43 13.43 0 012.53-3.4 35.39 35.39 0 015.48-4.56c.76-.53 1.5-1.06 2.15-1.7a8.5 8.5 0 002.55-4.63 8.37 8.37 0 00-.24-3.89l-.18-.59.05-.02zm.64 16.43c.5.03.64.28.4.72-.35.64-.9 1.04-1.6 1.21-.68.16-1.35.13-2.02-.02-.42-.09-.83-.23-1.24-.35l-.11-.06.12-.08c1.02-.53 2.07-.97 3.19-1.26.4-.1.83-.18 1.26-.16zM30.73 10.07c.92.2 1.75.61 2.54 1.11.87.56 1.65 1.21 2.4 1.92a29.78 29.78 0 014.2 5.18l.01.07-.18-.16a14.79 14.79 0 00-3.6-2.45c-1.01-.5-2.06-.9-3.11-1.3-.58-.23-1.16-.44-1.7-.75a1.82 1.82 0 01-.75-.76c-.15-.32-.07-.6.23-.78l.35-.18c-.28-.14-.53-.24-.75-.38-.2-.13-.38-.29-.55-.45a.77.77 0 01-.21-.64c.02-.24.13-.38.35-.46.26-.08.52-.03.77.03z"
            fill="#E84427"
          />
          <text
            class="_mainBrand_13m0y_5 _default_13m0y_10"
            x="52"
            y="37"
          >
            Global Fishing Watch
          </text>
        </g>
      </svg>
    </a>
    <div
      class="_appLayout_d89r9_1"
    >
      <div
        class="_appLayoutContent_d89r9_8"
        id="app-layout-content"
      >
        <div
          class="_container_1gfa5_1 _isOpen_1gfa5_19 _splitContainer_d89r9_66"
        >
          <aside
            class="_aside_1gfa5_8 _aside_d89r9_77"
            style="width: 50%;"
          >
            <div
              aria-label="Resize sidebar"
              class="_resizer_1gfa5_32 print-hidden"
              role="button"
              tabindex="0"
            />
            <div
              class="_container_10gdv_1"
            >
              <div … />
              <ul … />
            </div>
          </aside>
          <main
            class="_main_1gfa5_23 _main_d89r9_16"
            data-testid="app-main"
            id="app-main"
            style="left: 50%;"
          >
            <div
              class="_mapContainer_d89r9_22 _withTimebar_d89r9_33"
            >
              <div … />
            </div>
            <div
              class="_timebarWrapper_1pma8_1"
              data-testid="timebar-wrapper"
              role="toolbar"
            >
              <div … />
              <div … />
            </div>
            <footer
              class="print-hidden _footer_1k9s3_1"
            >
              <div … />
              <span … />
            </footer>
          </main>
        </div>
        <section
          aria-atomic="false"
          aria-label="Notifications Alt+T"
          aria-live="polite"
          aria-relevant="additions text"
          class="Toastify"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
      </div>
      <div
        class="_panel_15iap_1 _hidden_15iap_12"
        style="width: 540px; --panel-width: 540px;"
      >
        <div
          class="_panelResizer_15iap_29"
          role="button"
          tabindex="0"
        />
      </div>
    </div>
  </div>
  <div
    class="ReactModalPortal"
  />
</body>...
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Global-reports-should-display-the-same-number-in-the-graph-as-in-the-timeseries-1.png
 ❯ test/integration/Reports.spec.tsx:379:68
    377|     expect(statsData).toBeDefined()
    378|     const latestStatsData = (await waitForStatsQueryLoaded(store))?.da…
    379|     await expect.element(getByTestId('evolution-timeseries-chart')).to…
       |                                                                    ^
    380|     const timeseries = latestStatsData?.[0]?.timeseries
    381|     if (!timeseries?.length) {
Caused by: Error: Matcher did not succeed in time.
 ❯ test/integration/Reports.spec.tsx:379:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[8/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Global reports > should show detections in detections tab
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Global-reports-should-show-detections-in-detections-tab-1.png
 ❯ test/integration/Reports.spec.tsx:445:2
    443|   })
    444|
    445|   it('should show detections in detections tab', async () => {
       |  ^
    446|     const store = makeStore(defaultState)
    447|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[9/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Private user reports > should show user reports when user is logged in
AssertionError: expected 'idle' to be 'finished' // Object.is equality
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Private-user-reports-should-show-user-reports-when-user-is-logged-in-1.png
Expected: "finished"
Received: "idle"
 ❯ waitForUserReportsReady test/integration/Reports.spec.tsx:59:5
     57|   await expect
     58|     .poll(() => store.getState().reports.status, { timeout })
     59|     .toBe(AsyncReducerStatus.Finished)
       |     ^
     60| }
     61|
 ❯ test/integration/Reports.spec.tsx:491:10
Caused by: Error: Matcher did not succeed in time.
 ❯ waitForUserReportsReady test/integration/Reports.spec.tsx:57:2
 ❯ test/integration/Reports.spec.tsx:491:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[10/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Private user reports > should correctly display others points reports data
AssertionError: expected 'idle' to be 'finished' // Object.is equality
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Private-user-reports-should-correctly-display-others-points-reports-data-1.png
Expected: "finished"
Received: "idle"
 ❯ waitForUserReportsReady test/integration/Reports.spec.tsx:59:5
     57|   await expect
     58|     .poll(() => store.getState().reports.status, { timeout })
     59|     .toBe(AsyncReducerStatus.Finished)
       |     ^
     60| }
     61|
 ❯ test/integration/Reports.spec.tsx:516:10
Caused by: Error: Matcher did not succeed in time.
 ❯ waitForUserReportsReady test/integration/Reports.spec.tsx:57:2
 ❯ test/integration/Reports.spec.tsx:516:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[11/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in map when compared data is selected
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Reports.spec.tsx/Data-Comparison-should-show-both-dataviews-in-map-when-compared-data-is-selected-1.png
 ❯ test/integration/Reports.spec.tsx:563:2
    561|   })
    562|
    563|   it('should show both dataviews in map when compared data is selected…
       |  ^
    564|     const store = makeStore(defaultState)
    565|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[12/29]⎯
 FAIL   fishing-map-chromium  test/integration/Reports.spec.tsx > Data Comparison > should show both dataviews in graph when compared data is selected
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Reports.spec.tsx:590:2
    588|   })
    589|
    590|   it('should show both dataviews in graph when compared data is select…
       |  ^
    591|     const store = makeStore(defaultState)
    592|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[13/29]⎯
 FAIL   fishing-map-chromium  test/integration/User.spec.tsx > User expiration > should show expired session warning toast
VitestBrowserElementError: Cannot find element with locator: page.getByText(/Your session has expired/i)
<body>
  
  

  <div
    id="__root__"
  >
    <a
      class="print-only"
      href="https://globalfishingwatch.org"
    >
      <svg
        aria-label="Global Fishing Watch "
        class="_container_13m0y_1"
        height="60"
        viewBox="20 0 220 60"
        width="200"
        xmlns="http://www.w3.org/2000/svg"
      >
        <g
          aria-hidden="true"
          fill="none"
          fill-rule="evenodd"
          focusable="false"
        >
          <path
            d="M23.1 27.83c-.08.16-2.25 4.5.57 8.76.83 1.25 1.76 2.24 4.1 3.8 3.38 2.26 7.42 6.16 8.4 8.45.1.21.36.59-.06.83-.73.41-1.75.31-2.16.25l-.12-.02c-4.75-.88-14.5-5-13.8-13.8.18-2.21.98-4.87 3.07-8.27zm9.92-8.64c.7-.08 2.98-.15 3.08.08.07.17-.83.5-.87.52-5.22 1.98-6.97 3.16-7.22 3.3-3.3 2.01-4.71 4.35-4.82 4.57 1.48-3.1 5.2-7.93 9.83-8.47z"
            fill="#8ABBC7"
          />
          <path
            d="M40.45 19.2l.64 1.16a17.1 17.1 0 011.52 3.94c.27 1.1.39 2.23.31 3.37a9.39 9.39 0 01-1.72 4.84 12.9 12.9 0 01-3.29 3.2 20.3 20.3 0 01-7.02 3.08c-.4.09-.8.16-1.2.19a3.39 3.39 0 01-1.3-.17c-.43-.17-.5-.43-.28-.83a13.43 13.43 0 012.53-3.4 35.39 35.39 0 015.48-4.56c.76-.53 1.5-1.06 2.15-1.7a8.5 8.5 0 002.55-4.63 8.37 8.37 0 00-.24-3.89l-.18-.59.05-.02zm.64 16.43c.5.03.64.28.4.72-.35.64-.9 1.04-1.6 1.21-.68.16-1.35.13-2.02-.02-.42-.09-.83-.23-1.24-.35l-.11-.06.12-.08c1.02-.53 2.07-.97 3.19-1.26.4-.1.83-.18 1.26-.16zM30.73 10.07c.92.2 1.75.61 2.54 1.11.87.56 1.65 1.21 2.4 1.92a29.78 29.78 0 014.2 5.18l.01.07-.18-.16a14.79 14.79 0 00-3.6-2.45c-1.01-.5-2.06-.9-3.11-1.3-.58-.23-1.16-.44-1.7-.75a1.82 1.82 0 01-.75-.76c-.15-.32-.07-.6.23-.78l.35-.18c-.28-.14-.53-.24-.75-.38-.2-.13-.38-.29-.55-.45a.77.77 0 01-.21-.64c.02-.24.13-.38.35-.46.26-.08.52-.03.77.03z"
            fill="#E84427"
          />
          <text
            class="_mainBrand_13m0y_5 _default_13m0y_10"
            x="52"
            y="37"
          >
            Global Fishing Watch
          </text>
        </g>
      </svg>
    </a>
    <div
      class="_appLayout_d89r9_1"
    >
      <div
        class="_appLayoutContent_d89r9_8"
        id="app-layout-content"
      >
        <div
          class="_container_1gfa5_1 _isOpen_1gfa5_19 _splitContainer_d89r9_66"
        >
          <aside
            class="_aside_1gfa5_8 _aside_d89r9_77"
            style="width: 40rem;"
          >
            <button
              aria-label="Toggle sidebar"
              class="print-hidden _toggleBtn_1gfa5_48"
            >
              <svg … />
            </button>
            <div
              class="_container_10gdv_1"
            >
              <div … />
              <ul … />
            </div>
          </aside>
          <main
            class="_main_1gfa5_23 _main_d89r9_16"
            data-testid="app-main"
            id="app-main"
            style="left: 40rem;"
          >
            <div
              class="_mapContainer_d89r9_22 _withTimebar_d89r9_33"
            >
              <div … />
            </div>
            <div
              class="_timebarWrapper_1pma8_1"
              data-testid="timebar-wrapper"
              role="toolbar"
            >
              <div … />
              <div … />
            </div>
            <footer
              class="print-hidden _footer_1k9s3_1"
            >
              <div … />
              <span … />
            </footer>
          </main>
        </div>
        <section
          aria-atomic="false"
          aria-label="Notifications Alt+T"
          aria-live="polite"
          aria-relevant="additions text"
          class="Toastify"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
      </div>
      <div
        class="_panel_15iap_1 _hidden_15iap_12"
        style="width: 540px; --panel-width: 540px;"
      >
        <div
          class="_panelResizer_15iap_29"
          role="button"
          tabindex="0"
        />
      </div>
    </div>
  </div>
  <div
    class="ReactModalPortal"
  />
</body>...
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/User.spec.tsx/User-expiration-should-show-expired-session-warning-toast-1.png
 ❯ test/integration/User.spec.tsx:19:65
     17|     const { getByText, getByTestId } = await render({ store })
     18|
     19|     await expect.element(getByText(/Your session has expired/i)).toBeV…
       |                                                                 ^
     20|     await expect.element(getByTestId('login-link').first()).toBeVisibl…
     21|   })
Caused by: Error: Matcher did not succeed in time.
 ❯ test/integration/User.spec.tsx:19:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[14/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselSearch.spec.tsx > Vessel search > can search for a vessel and see it on the map
TimeoutError: locator.click: Timeout 27367ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByTestId('link-vessel-profile')

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselSearch.spec.tsx/Vessel-search-can-search-for-a-vessel-and-see-it-on-the-map-1.png
 ❯ test/integration/VesselSearch.spec.tsx:28:20
     26|
     27|     await userEvent.type(getByTestId('search-vessels-basic-input'), 'G…
     28|     await userEvent.click(getByTestId('link-vessel-profile'))
       |                    ^
     29|
     30|     await waitForVesselTrackReady(jotaiStore, getByTestId)
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[15/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselSearch.spec.tsx > Vessel search > preserves vessel search value when navigating away and back
AssertionError: expected undefined to be 'Gabu Reefer' // Object.is equality
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselSearch.spec.tsx/Vessel-search-preserves-vessel-search-value-when-navigating-away-and-back-1.png
- Expected:
"Gabu Reefer"
+ Received:
undefined
 ❯ test/integration/VesselSearch.spec.tsx:53:7
     51|     await expect
     52|       .poll(() => store.getState().location.query.query, { timeout: 50…
     53|       .toBe('Gabu Reefer')
       |       ^
     54|     await router.navigate({
     55|       to: ROUTE_PATHS.WORKSPACE,
Caused by: Error: Matcher did not succeed in time.
 ❯ test/integration/VesselSearch.spec.tsx:51:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[16/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselSearch.spec.tsx > Vessel search > reacts to clearing the search input
VitestBrowserElementError: Cannot find element with locator: page.getByTestId('link-vessel-profile')
<body>
  
  

  <div
    id="__root__"
  >
    <a
      class="print-only"
      href="https://globalfishingwatch.org"
    >
      <svg
        aria-label="Global Fishing Watch "
        class="_container_13m0y_1"
        height="60"
        viewBox="20 0 220 60"
        width="200"
        xmlns="http://www.w3.org/2000/svg"
      >
        <g
          aria-hidden="true"
          fill="none"
          fill-rule="evenodd"
          focusable="false"
        >
          <path
            d="M23.1 27.83c-.08.16-2.25 4.5.57 8.76.83 1.25 1.76 2.24 4.1 3.8 3.38 2.26 7.42 6.16 8.4 8.45.1.21.36.59-.06.83-.73.41-1.75.31-2.16.25l-.12-.02c-4.75-.88-14.5-5-13.8-13.8.18-2.21.98-4.87 3.07-8.27zm9.92-8.64c.7-.08 2.98-.15 3.08.08.07.17-.83.5-.87.52-5.22 1.98-6.97 3.16-7.22 3.3-3.3 2.01-4.71 4.35-4.82 4.57 1.48-3.1 5.2-7.93 9.83-8.47z"
            fill="#8ABBC7"
          />
          <path
            d="M40.45 19.2l.64 1.16a17.1 17.1 0 011.52 3.94c.27 1.1.39 2.23.31 3.37a9.39 9.39 0 01-1.72 4.84 12.9 12.9 0 01-3.29 3.2 20.3 20.3 0 01-7.02 3.08c-.4.09-.8.16-1.2.19a3.39 3.39 0 01-1.3-.17c-.43-.17-.5-.43-.28-.83a13.43 13.43 0 012.53-3.4 35.39 35.39 0 015.48-4.56c.76-.53 1.5-1.06 2.15-1.7a8.5 8.5 0 002.55-4.63 8.37 8.37 0 00-.24-3.89l-.18-.59.05-.02zm.64 16.43c.5.03.64.28.4.72-.35.64-.9 1.04-1.6 1.21-.68.16-1.35.13-2.02-.02-.42-.09-.83-.23-1.24-.35l-.11-.06.12-.08c1.02-.53 2.07-.97 3.19-1.26.4-.1.83-.18 1.26-.16zM30.73 10.07c.92.2 1.75.61 2.54 1.11.87.56 1.65 1.21 2.4 1.92a29.78 29.78 0 014.2 5.18l.01.07-.18-.16a14.79 14.79 0 00-3.6-2.45c-1.01-.5-2.06-.9-3.11-1.3-.58-.23-1.16-.44-1.7-.75a1.82 1.82 0 01-.75-.76c-.15-.32-.07-.6.23-.78l.35-.18c-.28-.14-.53-.24-.75-.38-.2-.13-.38-.29-.55-.45a.77.77 0 01-.21-.64c.02-.24.13-.38.35-.46.26-.08.52-.03.77.03z"
            fill="#E84427"
          />
          <text
            class="_mainBrand_13m0y_5 _default_13m0y_10"
            x="52"
            y="37"
          >
            Global Fishing Watch
          </text>
        </g>
      </svg>
    </a>
    <div
      class="_appLayout_d89r9_1"
    >
      <div
        class="_appLayoutContent_d89r9_8"
        id="app-layout-content"
      >
        <div
          class="_container_1gfa5_1 _isOpen_1gfa5_19 _splitContainer_d89r9_66"
        >
          <aside
            class="_aside_1gfa5_8 _aside_d89r9_77"
            style="width: 100%;"
          >
            <div
              class="_container_10gdv_1"
            >
              <div … />
              <ul … />
            </div>
          </aside>
          <main
            class="_main_1gfa5_23 _main_d89r9_16"
            data-testid="app-main"
            id="app-main"
            style="left: 100%;"
          >
            <div
              class="_mapContainer_d89r9_22"
            >
              <div … />
            </div>
            <footer
              class="print-hidden _footer_1k9s3_1"
            >
              <div … />
              <span … />
            </footer>
          </main>
        </div>
        <section
          aria-atomic="false"
          aria-label="Notifications Alt+T"
          aria-live="polite"
          aria-relevant="additions text"
          class="Toastify"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
        <div
          class="ReactModalPortal"
        />
      </div>
      <div
        class="_panel_15iap_1 _hidden_15iap_12"
        style="width: 540px; --panel-width: 540px;"
      >
        <div
          class="_panelResizer_15iap_29"
          role="button"
          tabindex="0"
        />
      </div>
    </div>
  </div>
  <div
    class="ReactModalPortal"
  />
</body>...
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselSearch.spec.tsx/Vessel-search-reacts-to-clearing-the-search-input-1.png
 ❯ test/integration/VesselSearch.spec.tsx:81:61
     79|     await userEvent.type(searchVesselInput, 'Gabu Reefer')
     80|
     81|     await expect.element(getByTestId('link-vessel-profile')).toBeVisib…
       |                                                             ^
     82|
     83|     await userEvent.clear(searchVesselInput)
Caused by: Error: Matcher did not succeed in time.
 ❯ test/integration/VesselSearch.spec.tsx:81:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[17/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should renders tabs and vessel basic info
Error: expect(element).toHaveTextContent()
Expected element to have text content:
  Gabu Reefer
Received:
  GabureeferCheck the vessel profile here
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-renders-tabs-and-vessel-basic-info-1.png
 ❯ test/integration/VesselViewer.spec.tsx:17:56
     15|     await router.navigate(navigateToVesselViewer())
     16|
     17|     await expect.element(getByTestId('vv-vessel-name')).toHaveTextCont…
       |                                                        ^
     18|     await expect.element(getByText('Registry', { exact: true })).toBeV…
     19|     await expect.element(getByText('AIS', { exact: true })).toBeVisibl…
Caused by: Error: Matcher did not succeed in time.
 ❯ test/integration/VesselViewer.spec.tsx:17:4
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[18/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should render summary tab by type
TimeoutError: locator.click: Timeout 26965ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByTestId('vv-summary-tab')

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-render-summary-tab-by-type-1.png
 ❯ test/integration/VesselViewer.spec.tsx:88:20
     86|
     87|     await GFWAPITest.waitForRequest('/events')
     88|     await userEvent.click(getByTestId('vv-summary-tab'))
       |                    ^
     89|     await expect.element(getByTestId('vv-list-port_visit')).toBeVisibl…
     90|   })
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[19/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should render summary tab by timeline
TimeoutError: locator.click: Timeout 29176ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByRole('button').filter({ hasText: 'Timeline by voyages' })

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-render-summary-tab-by-timeline-1.png
 ❯ test/integration/VesselViewer.spec.tsx:100:20
     98|
     99|     await GFWAPITest.waitForRequest('/events')
    100|     await userEvent.click(getByRole('button').filter({ hasText: 'Timel…
       |                    ^
    101|     await expect.element(getByText(/\d+ Events? between .+ and .+/).fi…
    102|   })
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[20/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should render areas tab and its tabs
TimeoutError: locator.click: Timeout 29195ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByTestId('vv-areas-tab')

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-render-areas-tab-and-its-tabs-1.png
 ❯ test/integration/VesselViewer.spec.tsx:109:20
    107|     const { getByTestId, router } = await render({ store, authenticate…
    108|     await router.navigate(navigateToVesselViewer())
    109|     await userEvent.click(getByTestId('vv-areas-tab'))
       |                    ^
    110|
    111|     await expect.element(getByTestId('vv-area-eez')).toBeVisible()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[21/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should render related vessels tab
TimeoutError: locator.click: Timeout 29078ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByTestId('vv-related-tab')

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-render-related-vessels-tab-1.png
 ❯ test/integration/VesselViewer.spec.tsx:125:20
    123|     })
    124|     await router.navigate(navigateToVesselViewer())
    125|     await userEvent.click(getByTestId('vv-related-tab'))
       |                    ^
    126|
    127|     await expect
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[22/29]⎯
 FAIL   fishing-map-chromium  test/integration/VesselViewer.spec.tsx > Vessel viewer > should render insights tab
TimeoutError: locator.click: Timeout 29073ms exceeded.
Call log:
  - waiting for locator('[data-vitest="true"]').contentFrame().getByTestId('__vitest_0__').getByTestId('vv-insights-tab')

Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/VesselViewer.spec.tsx/Vessel-viewer-should-render-insights-tab-1.png
 ❯ test/integration/VesselViewer.spec.tsx:140:20
    138|     const { getByTestId, getByText, router } = await render({ store, a…
    139|     await router.navigate(navigateToVesselViewer())
    140|     await userEvent.click(getByTestId('vv-insights-tab'))
       |                    ^
    141|
    142|     await expect
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[23/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should open vessel popup on vessel click and show tile related info
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Vessels.spec.tsx:18:2
     16|   })
     17|
     18|   it('should open vessel popup on vessel click and show tile related i…
       |  ^
     19|     const store = makeStore(defaultState, [])
     20|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[24/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should be able to close an opened popup
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Vessels.spec.tsx:55:2
     53|   })
     54|
     55|   it('should be able to close an opened popup', async () => {
       |  ^
     56|     const store = makeStore(defaultState, [])
     57|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[25/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should be able to navigate to vessel viewer inside the vessel popup
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Vessels.spec.tsx:88:2
     86|   })
     87|
     88|   it('should be able to navigate to vessel viewer inside the vessel po…
       |  ^
     89|     const store = makeStore(defaultState, [])
     90|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[26/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should display the vessel track on the timebar
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Vessels.spec.tsx:120:2
    118|   })
    119|
    120|   it('should display the vessel track on the timebar', async () => {
       |  ^
    121|     const GFWAPITest = new GFWAPITestUtils()
    122|     const store = makeStore(defaultState, [])
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[27/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should be able to see vessel info on hover and pin a vessel to the map to see it on the sidebar
AssertionError: expected undefined to strictly equal { dataviewInstances: [ …(4) ], …(5) }
Failure screenshot:
  - apps/fishing-map/test/integration/__screenshots__/Vessels.spec.tsx/Vessel-map-popup-should-be-able-to-see-vessel-info-on-hover-and-pin-a-vessel-to-the-map-to-see-it-on-the-sidebar-1.png
- Expected:
{
  "bivariateDataviews": null,
  "dataviewInstances": [
    {
      "config": {
        "color": "#F95E5E",
        "colorCyclingType": undefined,
        "events": [
          "public-global-fishing-events:v4.0",
          "public-global-port-visits-events:v4.0",
          "public-global-encounters-events:v4.0",
          "public-global-loitering-events:v4.0",
          "public-global-gaps-events:v4.0",
        ],
        "info": "public-global-vessel-identity:v4.0",
        "relatedVesselIds": [
          "19630081d-d249-9b1d-2b6d-46113987f976",
          "9126f54fd-d5b3-2c09-0552-abcceccd10ff",
        ],
        "track": "public-global-all-tracks:v4.0",
      },
      "dataviewId": "fishing-map-vessel-track-v-4",
      "deleted": false,
      "id": "vessel-9375434a0-0b91-7247-5a95-57a10d2b08df:v4.0",
    },
    {
      "config": {
        "visible": true,
      },
      "id": "presence",
    },
    {
      "config": {
        "visible": false,
      },
      "id": "vms",
    },
    {
      "config": {
        "visible": false,
      },
      "id": "ais",
    },
  ],
  "latitude": 19,
  "longitude": 26,
  "timebarVisualisation": "vessel",
  "zoom": 1.49,
}
+ Received:
undefined
 ❯ test/integration/Vessels.spec.tsx:180:29
    178|     const pinAction = actions.findLast((action) => action.type === 'HO…
    179|
    180|     expect(pinAction?.query).toStrictEqual({
       |                             ^
    181|       dataviewInstances: [
    182|         {
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[28/29]⎯
 FAIL   fishing-map-chromium  test/integration/Vessels.spec.tsx > Vessel map popup > should be able to interact with vessels after filtering by flag
Error: Test timed out in 30000ms.
If this is a long-running test, pass a timeout value as the last argument or configure it globally with "testTimeout".
 ❯ test/integration/Vessels.spec.tsx:326:2
    324|   })
    325|
    326|   it('should be able to interact with vessels after filtering by flag'…
       |  ^
    327|     const store = makeStore(defaultState, [])
    328|     const jotaiStore = createJotaiStore()
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[29/29]⎯
 Test Files  9 failed | 9 passed | 1 skipped (19)
      Tests  29 failed | 55 passed | 9 skipped (93)
   Start at  17:52:57
   Duration  1467.51s (transform 0ms, setup 1.45s, import 68.66s, tests 1305.41s, environment 0ms)
✅ timebar:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/timebar
 ❯  timebar  src/timebar.spec.tsx (0 test)
 ❯  timebar  src/timebar-range.spec.tsx (0 test)
 ❯  timebar  src/timeline/timeline-drag.utils.spec.ts (0 test)
 ❯  timebar  src/components/playback.spec.tsx (0 test)
 ❯  timebar  src/timeline/timeline.interaction.spec.tsx (0 test)
 ❯  timebar  src/components/timerange-selector.spec.tsx (0 test)
 ✓  timebar  src/charts/charts-store.atom.spec.tsx (2 tests) 57ms
 ❯  timebar  src/charts/charts.hooks.spec.tsx (0 test)
⎯⎯⎯⎯⎯⎯ Failed Suites 7 ⎯⎯⎯⎯⎯⎯⎯
 FAIL   timebar  src/timebar-range.spec.tsx [ src/timebar-range.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/data-transforms" from "libs/timebar/src/timebar-range.ts". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/timebar-range.ts:3:27
  1  |  import { useCallback, useEffect, useRef, useState } from "react";
  2  |  import { getUTCDate } from "@globalfishingwatch/data-transforms";
     |                              ^
  3  |  // Echo lag is at most a couple of commits behind the rAF loop, so a short window is
  4  |  // plenty; the buffer is cleared whenever an external change is adopted.
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/7]⎯
 FAIL   timebar  src/timebar.spec.tsx [ src/timebar.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/deck-loaders" from "libs/timebar/src/timebar.spec.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/timebar.spec.tsx:4:0
  23 |  }, this) }));
  24 |  const __vi_import_0__ = await import("@testing-library/react");
  25 |  const __vi_import_1__ = await import("@globalfishingwatch/deck-loaders");
     |                                       ^
  26 |  const __vi_import_2__ = await import("./timeline/timeline-context");
  27 |  const __vi_import_3__ = await import("./charts");
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/7]⎯
 FAIL   timebar  src/charts/charts.hooks.spec.tsx [ src/charts/charts.hooks.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/data-transforms" from "libs/timebar/src/charts/charts.hooks.ts". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/charts/charts.hooks.ts:5:27
  2  |  import { scaleTime } from "d3-scale";
  3  |  import { EventTypes } from "@globalfishingwatch/api-types";
  4  |  import { getUTCDate } from "@globalfishingwatch/data-transforms";
     |                              ^
  5  |  import { useTimelineContext } from "../timeline/timeline-context";
  6  |  export const filterData = (data, start, end) => {
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/7]⎯
 FAIL   timebar  src/components/playback.spec.tsx [ src/components/playback.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/deck-loaders" from "libs/timebar/src/components/playback.spec.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/components/playback.spec.tsx:4:0
  23 |  }, this) }));
  24 |  const __vi_import_0__ = await import("@testing-library/react");
  25 |  const __vi_import_1__ = await import("@globalfishingwatch/deck-loaders");
     |                                       ^
  26 |  const __vi_import_2__ = await import("../constants");
  27 |  const __vi_import_3__ = await import("../timebar");
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/7]⎯
 FAIL   timebar  src/components/timerange-selector.spec.tsx [ src/components/timerange-selector.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/deck-loaders" from "libs/timebar/src/components/timerange-selector.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/components/timerange-selector.tsx:12:7
  2  |  import classNames from "classnames";
  3  |  import { DateTime } from "luxon";
  4  |  import { FOURWINGS_INTERVALS_ORDER, getFourwingsInterval, LIMITS_BY_INTERVAL } from "@globalfishingwatch/deck-loaders";
     |                                                                                       ^
  5  |  import { Select } from "@globalfishingwatch/ui-components/select";
  6  |  import { Tooltip } from "@globalfishingwatch/ui-components/tooltip";
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/7]⎯
 FAIL   timebar  src/timeline/timeline-drag.utils.spec.ts [ src/timeline/timeline-drag.utils.spec.ts ]
Error: Failed to resolve import "@globalfishingwatch/deck-loaders" from "libs/timebar/src/timeline/timeline-drag.utils.ts". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/timeline/timeline-drag.utils.ts:6:64
  1  |  import { DateTime } from "luxon";
  2  |  import { FOURWINGS_INTERVALS_ORDER, getFourwingsInterval } from "@globalfishingwatch/deck-loaders";
     |                                                                   ^
  3  |  import { EVENT_SOURCE } from "../constants";
  4  |  import { stickToClosestUnit } from "../utils";
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/7]⎯
 FAIL   timebar  src/timeline/timeline.interaction.spec.tsx [ src/timeline/timeline.interaction.spec.tsx ]
Error: Failed to resolve import "@globalfishingwatch/data-transforms" from "libs/timebar/src/charts/highlighter.tsx". Does the file exist?
  Plugin: vite:import-analysis
  File: /home/runner/work/frontend/frontend/libs/timebar/src/charts/highlighter.tsx:7:27
  4  |  import { useAtomValue } from "jotai";
  5  |  import { DateTime } from "luxon";
  6  |  import { getUTCDate } from "@globalfishingwatch/data-transforms";
     |                              ^
  7  |  import { Icon } from "@globalfishingwatch/ui-components/icon";
  8  |  import { IconButton } from "@globalfishingwatch/ui-components/icon-button";
 ❯ TransformPluginContext._formatLog ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30602:39
 ❯ TransformPluginContext.error ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30599:14
 ❯ normalizeUrl ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27842:18
 ❯ ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27905:30
 ❯ TransformPluginContext.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:27873:4
 ❯ EnvironmentPluginContainer.transform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:30387:14
 ❯ loadAndTransform ../../node_modules/.pnpm/vite@8.0.16_@types+node@25.9.1_@vitejs+devtools@0.3.1_esbuild@0.28.1_jiti@2.7.0_less@4._a7c07b7e3edb290c34748eebaad75d68/node_modules/vite/dist/node/chunks/node.js:24646:26
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[7/7]⎯
 Test Files  7 failed | 1 passed (8)
      Tests  2 passed (2)
   Start at  17:52:43
   Duration  9.29s (transform 403ms, setup 0ms, import 316ms, tests 57ms, environment 17.78s)
✅ api-client:test 
Done compiling TypeScript files for project "api-client".
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/api-client
stderr | src/api-client.spec.ts > api-client > GFW_API_CLASS > fetch > should continue fetch after login rejects when logging is in progress
GFWAPI: _login — Invalid access token { status: 401, message: 'Invalid', messages: undefined }
 ✓  api-client  src/utils/search.spec.ts (14 tests) 13ms
stdout | src/api-client.spec.ts > api-client > GFW_API_CLASS > logout > should log warn when logout API fails
GFWAPI: GFW API Client initialized with the following config {
  debug: true,
  baseUrl: 'https://api.example.com',
  storageKeys: {
    token: 'GFW_API_USER_TOKEN',
    refreshToken: 'GFW_API_USER_REFRESH_TOKEN'
  },
  token: '',
  refreshToken: ''
}
GFWAPI: logout start {
  hasAccessToken: true,
  hasLocalRefreshToken: true,
  hasRefreshStrategy: false,
  hasSessionInvalidateStrategy: false,
  status: 'idle',
  loginInProgress: false,
  refreshInProgress: false
}
GFWAPI: logout — revoking session on gateway
GFWAPI: Fetching URL: /v3/auth/logout
stdout | src/api-client.spec.ts > api-client > GFW_API_CLASS > logout > should log warn when logout API fails
GFWAPI: invalidateClientSession — clearing local session
GFWAPI: updated token with 
GFWAPI: updated refreshToken with 
GFWAPI: logout finished
 ✓  api-client  src/api-client.spec.ts (84 tests) 391ms
 Test Files  2 passed (2)
      Tests  98 passed (98)
   Start at  17:52:54
   Duration  3.15s (transform 776ms, setup 0ms, import 874ms, tests 404ms, environment 4.11s)
✅ deck-loaders:test 
 RUN  v4.1.8 /home/runner/work/frontend/frontend/libs/deck-loaders
 ✓  deck-loaders  src/user/lib/parse-user-tracks.spec.ts (10 tests) 55ms
 ✓  deck-loaders  src/fourwings/helpers/time.spec.ts (17 tests) 59ms
 ✓  deck-loaders  src/fourwings/lib/parse-fourwings-clusters.spec.ts (7 tests) 30ms
 ✓  deck-loaders  src/user/lib/utils.spec.ts (6 tests) 24ms
 ✓  deck-loaders  src/fourwings/helpers/fourwings-graph-aggregation.spec.ts (5 tests) 10ms
src/vessels/lib/vessel-track-proto.gen.js 713ms
 ✓  deck-loaders  src/user/lib/features.utils.spec.ts (11 tests) 19ms
src/vessels/lib/vessel-track-proto.gen.d.ts 197ms
 ✓  deck-loaders  src/fourwings/lib/parse-fourwings.spec.ts (5 tests) 26ms
 ✓  deck-loaders  src/vessels/lib/parse-events.spec.ts (6 tests) 61ms
 ✓  deck-loaders  src/fourwings/lib/parse-fourwings-vectors.spec.ts (4 tests) 26ms
 ✓  deck-loaders  src/fourwings/helpers/byte-length.spec.ts (3 tests) 10ms
 ✓  deck-loaders  src/fourwings/helpers/timestamps.spec.ts (6 tests) 17ms
 ✓  deck-loaders  src/vessels/lib/parse-tracks.spec.ts (7 tests) 19ms
 Test Files  12 passed (12)
      Tests  87 passed (87)
   Start at  17:52:39
   Duration  2.83s (transform 840ms, setup 0ms, import 2.76s, tests 355ms, environment 2ms)
Compiling TypeScript files for project "deck-loaders"...
Done compiling TypeScript files for project "deck-loaders".

Summary: 6 passed, 1 failed

@j8seangel j8seangel merged commit bbf641c into develop Jul 14, 2026
2 checks passed
@j8seangel j8seangel deleted the deck-layers/test branch July 14, 2026 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@fernand0q fernand0q Awaiting requested review from fernand0q

Assignees

No one assigned

Labels

deck-layers deck-loaders

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@j8seangel