🔴 Meticulous spotted visual differences in 7 of 1367 screens tested: view and approve differences detected.

Meticulous evaluated ~10 hours of user flows against your PR.

_{Last updated for commit d68fd0d. This comment will update as new commits are pushed.}

Codecov Report

All modified and coverable lines are covered by tests ✅

❌ Unsupported file format

Upload processing failed due to unsupported file format. Please review the parser error message:

Error parsing JUnit XML in /home/runner/work/datahub/datahub/metadata-io/build/test-results/test/TEST-com.linkedin.metadata.graph.search.elasticsearch.SearchGraphServiceElasticSearchTest.xml at 117:1057

Caused by:
    RuntimeError: Error converting computed name to ValidatedString
    
    Caused by:
        string is too long

For more help, visit our troubleshooting guide.

📢 Thoughts on this report? Let us know!

Bundle Report

Changes will increase total bundle size by 1.73kB (0.01%) ⬆️. This is within the configured threshold ✅

Affected Assets, Files, and Routes:

Hello @david-leifker we have found a problem trying to configure OAUTH on kafka on the frontend project , we have this error on logs:

As you can see despite we have previously configured correctly the oauth bearer token endpoint , this configuration is not properly applied , it appears as null:

Our configuration is:

springKafkaConfigurationOverrides:
security.protocol: SASL_SSL
sasl.mechanism: OAUTHBEARER
sasl.login.callback.handler.class: org.apache.kafka.common.security.oauthbearer.OAuthBearerLoginCallbackHandler
sasl.oauthbearer.token.endpoint.url: https://login.microsoftonline.com/xxxxxx/oauth2/v2.0/token
sasl.oauthbearer.method: oidc

We think maybe it is necessary to set the assignment of this property on these files:

• datahub-frontend/app/client/KafkaTrackingProducer.java
  

• datahub-frontend/conf/application.conf
  

@RafaelFranciscoLuqueCerezo - Good call out here! Most of our application stack is using Spring and benefits from the Spring kafka plugin. The frontend component is however not using Spring and appears to be manually configured. Let me look over the configuration there and potentially I can refactor the code to use the Spring properties even though it is not a Spring application. We can then replace all this manual work to configure the frontend Kafka producer.