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

version 6.2 to version 6.3 banner Message missing parameter #10863

Open
BenediktMeierUIT opened this issue Sep 19, 2024 · 3 comments
Open

version 6.2 to version 6.3 banner Message missing parameter #10863

BenediktMeierUIT opened this issue Sep 19, 2024 · 3 comments
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Type: Bug a defect

Comments

@BenediktMeierUIT
Copy link
Contributor

What steps does it take to reproduce the issue?
From version 6.2 to version 6.3, likely due to this change #10565 the "displayValue" is no longer returned.

Version 6.3:
Screenshot from 2024-09-19 14-30-46

Version 6.2:
Screenshot from 2024-09-19 13-54-01

@BenediktMeierUIT BenediktMeierUIT added the Type: Bug a defect label Sep 19, 2024
@BenediktMeierUIT BenediktMeierUIT closed this as not planned Won't fix, can't repro, duplicate, stale Sep 19, 2024
@BenediktMeierUIT
Copy link
Contributor Author

BenediktMeierUIT commented Sep 19, 2024

I am so confused right now. On one system with a different database, it is not displayed, and in another, everything works wonderfully.
Sorry for the confusion. I will only create a ticket if I get the same error on different databases.

@pdurbin
Copy link
Member

pdurbin commented Sep 19, 2024

No worries. Please keep us posted!

@BenediktMeierUIT
Copy link
Contributor Author

I found the error. I'm not quite sure yet how it should be done best. However, I think something should be set in the Dockerfile (

ENV MP_CONFIG_PROFILE=ct
). I've tried several things. But I'm not done testing and verifying the perfect solution yet.

The problem lies in the terminal LANG setting. If you have "C.UTF-8" when starting the Docker, then the error occurs. Whether you then execute something in the Docker container with "docker exec -u root -e LANG='C.UTF-8' -it dataverse /bin/bash" or without LANG. Up to the current state, it is important how the Docker was started. It also doesn't matter whether LANG is set in the docker-compose file or not.

I wanted to see what effects it has if LANG is set in the Dockerfile. Or has anyone of you ever had this problem?

@pdurbin pdurbin added the Component: Containers Anything related to cloudy Dataverse, shipped in containers. label Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Containers Anything related to cloudy Dataverse, shipped in containers. Type: Bug a defect
Projects
None yet
Development

No branches or pull requests

2 participants