Rogelio J. Baucells

I agree with returning an object. The implementation I am working on returns an object with the three fields. For now we can provide some formatting to the object been...

I can confirm the error is still present in apoc-4.2.0.4. This bug prevents the use of `custom.xxx()` functions and procedures. Once the database is restarted and the error happens there...

Any updated on this issue, I just upgraded to Neo4J 4.3 using APOC 4.3.0.0 and the bug is still present. This bug prevents the use of `custom.xxx()` functions and procedures!

Yes, I am facing another problem. A new database with your steps (@vga91) work fine, but I am pretty sure my problem was triggered by the database restart. I had...

Sorry, but I gave up, no longer using custom functions/procedures. A simple test that I cannot make it work: ```cypher CALL apoc.custom.declareFunction('test2(subject::NODE) :: BOOLEAN', 'RETURN true', true, 'dummy function'); ```...

> there's work in-progress which could unblock this: [open-telemetry/opentelemetry-java#5918](https://github.com/open-telemetry/opentelemetry-java/pull/5918) Is there anything else preventing the PR from being merged? The above mentioned change was already merged...

> @rjbaucells can you integrate that change into your PR? I looked at the details of PR [5918](https://github.com/open-telemetry/opentelemetry-java/pull/5918) and it provides a way to supress instrumentation of internal calls in...

The Context value in the above mentioned PR is `suppress_internal_exporter_instrumentation`. Looking at the name it is very specific to "exporters". I did not find the place the agent is reading...

I have the PR already updated, waiting for SDK 1.41.0 to push it.

Hello, What is the status of this PR? Thanks