nlnwa / veidemann-browser-controller

veidemann-browser-controller

Test

go test ./...

Run integration test

The integration test is useful to validate compatibility between the browserless container image and the chromedp library.

Using docker

go test --tags=integration -run TestSession_Fetch ./server

Using podman

Note that you have to manually clean up containers after every run with using podman as container provider because the container reaper (ryuk) is disabled.

# Setup podman socket
systemctl --user start podman

# Run integration test
DOCKER_HOST="unix:///run/user/$UID/podman/podman.sock" go test -run TestSession_Fetch --tags=integration ./server -provider=podman

veidemann-browser-controller's Issues

Use scopecheck service for normalizing URIs

We need to use the same normalizing function across every service in the platform.

Handle ABORTED status similar to NOT FOUND

veidemann-browser-controller/controller/browsercontroller.go

Line 102 in 639aa4e

case codes.NotFound:

The ABORTED status indicates concurrency issues on the frontier that is transitory. It should not stop the browser-controller