-
-
Notifications
You must be signed in to change notification settings - Fork 354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to close page or browser properly? #1095
Comments
I think there was an error in closing the browser. So if I change it to another URL, it causes a stuck I use thunder client, WSL I'm processing data on Google Form to get title, description, number of pages, and number of questions. But for now I am focusing on this stuck problem |
Please fix the format of your markdown: 6 MD032/blanks-around-lists Lists should be surrounded by blank lines [Context: "1) I run my program code for t..."]
13 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```go"]
34 MD031/blanks-around-fences Fenced code blocks should be surrounded by blank lines [Context: "```go"] generated by check-issue |
Update: I tried using Windows, there was no stuck problem. However, when using Linux a stuck occurs |
This is my Dockerfile # Build stage
FROM golang:1.21.11-alpine3.19 AS builder
WORKDIR /app
COPY . .
RUN go build -o main main.go
RUN apk add curl
# Run stage
FROM alpine:3.14
RUN apk add --no-cache chromium
WORKDIR /app
COPY --from=builder /app/main .
COPY --from=builder /app/migrate.linux-amd64 ./migrate
COPY app.env .
COPY start.sh .
COPY wait-for.sh .
COPY db/migration ./migration
EXPOSE 8080
CMD [ "/app/main" ]
ENTRYPOINT [ "/app/start.sh" ] |
Rod is not tested on Alpine. The CI of rod uses ubuntu. Better to use |
Doesn't look like a rod issue. |
Rod Version: v0.116.1
I have a problem about how to close page or browser, i think.
So this is the scenario:
Am I wrong about how to close the page and browser after the first running program is run?
This is my code:
service.go
util.go
The text was updated successfully, but these errors were encountered: