-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Enable dash-site to check for running Firebase emulator #10564
Labels
e1-hours
Effort: < 8 hrs
infra.structure
Relates to the tools that create docs.flutter.dev
p1-high
Major but not urgent concern: Resolve in months. Update each month.
Comments
atsansone
added
infra.structure
Relates to the tools that create docs.flutter.dev
p1-high
Major but not urgent concern: Resolve in months. Update each month.
e1-hours
Effort: < 8 hrs
st.triage.ltw
labels
May 10, 2024
@parlough, can this be closed? |
I am also experiencing this issue. Here is a log:
|
Quick fix for anyone stuck (Mac):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
e1-hours
Effort: < 8 hrs
infra.structure
Relates to the tools that create docs.flutter.dev
p1-high
Major but not urgent concern: Resolve in months. Update each month.
When I run the link checker a second time, the following error appears:
The Firebase emulator was still running because nothing told it to terminate. This, though, prevents the link checker from running.
Can the script either check for a running FIrebase emulator or terminate once a link check run completes?
The text was updated successfully, but these errors were encountered: