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

graphql-ui issue show  on each line and near the cursor #23914

Closed
MartinSem opened this issue Feb 23, 2022 · 5 comments · Fixed by #24025
Closed

graphql-ui issue show  on each line and near the cursor #23914

MartinSem opened this issue Feb 23, 2022 · 5 comments · Fixed by #24025

Comments

@MartinSem
Copy link

Describe the issue
After the upgrade to Quarkus 2.7.0 and maven 3.8.3, graphql-ui show a  on each line and near the cursor.
It happens only on window local environment, there is no issue when we deploy it into a kubernetes container.

image

Environment info
$ mvn -v Apache Maven 3.8.3 (ff8e977a158738155dc465c6a97ffaf31982d739) Java version: 11.0.7, vendor: Oracle Corporation, runtime: *** Default locale: en_US, platform encoding: Cp1252 OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Is there anyway to handle this?

@quarkus-bot
Copy link

quarkus-bot bot commented Feb 23, 2022

/cc @geoand, @iocanel, @jmartisk, @phillip-kruger

@phillip-kruger
Copy link
Member

I think it's due to platform encoding: Cp1252. I'll see if I can fix that, but if you can change to UTF8 that might solve it

@phillip-kruger phillip-kruger self-assigned this Feb 23, 2022
@jmartisk
Copy link
Contributor

I'm trying to reproduce this on my Windows machine that also uses CP1252, but I'm not successful.
I tried compiling and running the application there,
I also tried compiling and running it on the linux/UTF8 machine but accessing it from the Windows machine,
but no luck. We might need some more info, like your pom.xml, or built jar files,....

@gsmet
Copy link
Member

gsmet commented Feb 28, 2022

@MartinSem care to share some information?

@phillip-kruger @jmartisk I wonder if it could be that we are not sending proper encoding headers anymore for these resources. That could explain that you have different behaviors depending on the default encoding of the browser.

@gsmet
Copy link
Member

gsmet commented Mar 1, 2022

Probably fixed by #24025 .

@gsmet gsmet added this to the 2.7.3.Final milestone Mar 1, 2022
@gsmet gsmet closed this as completed Mar 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants