Improve Runtime Error log

[tzzed]

Is your feature request related to a problem / use case? Please describe.
When orion return Runtime Error (unknown attribute value type in DB: ) we don't know the attribute name

Describe the solution you'd like
Something like this.
Runtime Error (unknown attribute value type in DB: type on attribute "name")

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Describe why you need this feature
This simplify the debug.

Additional information
Add any other information, diagrams or screenshots about the feature request here.

Do you have the intention to implement the solution

• Yes, but I will need help.

[fgalan]

Thanks for the feedback! I agree that adding the attribute name would make the log trace more useful.

As far as I have checked, that log trace is used in three places:

I would say that in them all the attribute name is accessible at caP->name, so the issue could be easy to implement. @tzzed maybe you could do the PR implementing it, please? Thanks!

[tzzed]

I have seen, but I need to compile orion on mac M2 if it is possible or should compile on linux for more simplicity?

[fgalan]

mac M2 is not a supported platform. Maybe it works, but we haven't tested it.

Maybe you could create a Linux-based virtual machine in your mac M2 system using some virtualization tool (VirtualBox, etc.)?

[mapedraza]

@tzzed Have a look to https://github.com/abiosoft/colima project. It allows to run containers virtualising the platform.

[tzzed]

@fgalan should the PR only set the attrobute on LM_E(("Runtime Error (unknown attribute value type in DB: %d)" or all logs that contains LM_E(("Runtime Error (unknown attribute value type %d)" to have harmonized logs?

[fgalan]

@fgalan should the PR only set the attrobute on LM_E(("Runtime Error (unknown attribute value type in DB: %d)" or all logs that contains LM_E(("Runtime Error (unknown attribute value type %d)" to have harmonized logs?

I see a PR has been raised for this issue. Let's continue discussion there.

[fgalan]

Fixed by PR #4393

@tzzed should this issue be closed or is there anything else pending, please?

[tzzed]

It can be closed. Thank you