Skip to content
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

BUG: JS failing to detect "preferred" docs version #1416

Closed
wants to merge 2 commits into from

Conversation

drammock
Copy link
Collaborator

@drammock drammock commented Aug 18, 2023

our dev docs have a JS console error about not detecting any "preferred" version of the docs. This PR will try to fix it, but first need to do a bit of debugging. It's severe in that it results in none of the "on page load" JS getting executed (e.g., making our searchbar not work)

@drammock drammock changed the title debugging BUG: JS failing to detect "preferred" docs version Aug 21, 2023
@drammock drammock added kind: bug Something isn't working impact: block-release Should block a release from happening. Only use if this is a critical problem we don't want to ship labels Aug 21, 2023
@12rambau
Copy link
Collaborator

I checked this PR build and of course everything works just as expected. Note that I also experience the issue ou see in latest.

@12rambau 12rambau removed the impact: block-release Should block a release from happening. Only use if this is a critical problem we don't want to ship label Aug 23, 2023
@12rambau
Copy link
Collaborator

I've removed the block release as it's not failing all the JS anymore.

@drammock
Copy link
Collaborator Author

I checked this PR build and of course everything works just as expected. Note that I also experience the issue ou see in latest.

yeah it's frustrating that it works fine on PR build but not on main.

@drammock drammock closed this Oct 17, 2023
@drammock drammock deleted the fix-json branch October 17, 2023 21:10
@drammock
Copy link
Collaborator Author

fixed / superseded by #1512

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants