Open augi opened 3 months ago
Work around: Write a log message before the PubSub client is created. Looks like there is a race or chicken-egg at the startup.
I have been able to reproduce this and found a similar workaround that just by instantiating a logger using SLF4J, this error is not thrown. Example:
private static final Logger logger = LoggerFactory.getLogger(PublisherExample.class);
I'm not of the exact cause of the issue right now, but it seems to lie in a layer below the Pub/Sub client library. Some initial thoughts are that there is some dependency conflict, but I've been unable to find definitive evidence or a fix for that yet. WE will continue investigating, but currently using a workaround is the best option for this issue.
Environment details
1.127.2
, andv0.131.3-alpha
Steps to reproduce
Use both dependencies in one project.
Code example
Stack trace
External references such as API reference guides
Any additional information below
I checked that both dependencies use the same version of gRPC. There is no issue if we replace the GCP logging with plain stdout logging.