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

Missing information in error message #121

Open
paulmillar opened this issue Nov 1, 2023 · 3 comments
Open

Missing information in error message #121

paulmillar opened this issue Nov 1, 2023 · 3 comments

Comments

@paulmillar
Copy link
Contributor

We have an issue from a dCache admin, that the error message indicating that an LSC file is missing doesn't provide enough information to know which LSC file is expected.

The error message comes from CaNL, so updating CaNL to provide additional information in the error message would seem a natural way to resolve the dCache issue.

@golbi
Copy link
Member

golbi commented Nov 2, 2023

OK, Can you please be bit more specific, about the situation in which canl is not providing this information? I.e. how it is used (API calls) and what is missing in error precisely?

@paulmillar
Copy link
Contributor Author

Hi @golbi , Thanks for the quick reply.

Did you see the additional information that @onnozweers posted in the above mentioned dCache issue?

Is this sufficient information to understand the problem?

@golbi
Copy link
Member

golbi commented Nov 24, 2023

Hi @paulmillar
I was sure I've answered, but it somehow didn't happen. Sorry about that.

So, no it is not very helpful :-) I'd need to get the following pieces of information:

  1. how (precisely - no time to dig in source code of an integration) canl is configured
  2. what is a call to canl lib method, and with what input
  3. what error is generated by canl and what would be expected.

In here... I don't think that canl supports lsc files, so likely there is some integration asking canl to do something basing on the messed up lsc file. It is very hard to decipher what is going on in that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants