Skip to content
Check Changelog

RNET-1161: Implement support for using a log level for a specific log category #1924

Sign in to view logs

RNET-1161: Implement support for using a log level for a specific log category

RNET-1161: Implement support for using a log level for a specific log category #1924

Triggered via pull request July 2, 2024 13:18
@elle-jelle-j
synchronize #3634
lj/logger
Status Success
Total duration 14s
Artifacts –

check-changelog.yml

on: pull_request
changelog
3s
changelog
Fit to window
Zoom out
Zoom in

Annotations

1 error and 9 warnings
Realm.Fody.Tests.dll.Analytics.Tests.ValidateFeatureUsage. ► Analytics.Tests ► ValidateFeatureUsage("IAsymmetricObject","I_ASYMMETRIC_OBJECT"): TestResults.xml#L0
Failed test found in: TestResults.xml Error: at MongoDB.Bson.BsonDocument.get_Item(String name)
Realm/Realm/Handles/SharedRealmHandle.cs#L67
TODO entry doesn't have a link to Github issue or Jira ticket lj): Update arg order to be the same across the SDK.
Realm/Realm/Logging/LogCategory.cs#L118
TODO entry doesn't have a link to Github issue or Jira ticket lj): Prefer `SDK` or `Sdk` for c#?
Realm/Realm/Logging/Logger.cs#L77
TODO entry doesn't have a link to Github issue or Jira ticket lj): Deprecate
Realm/Realm/Logging/Logger.cs#L96
TODO entry doesn't have a link to Github issue or Jira ticket lj): Deprecate
Realm/Realm/Logging/Logger.cs#L195
TODO entry doesn't have a link to Github issue or Jira ticket lj): Currently using `!` since calls always go thru `Log()`; however, we
wrappers/src/shared_realm_cs.cpp#L51
TODO entry doesn't have a link to Github issue or Jira ticket lj): Update arg order to be the same across the SDK.
wrappers/src/shared_realm_cs.cpp#L301
TODO entry doesn't have a link to Github issue or Jira ticket lj): Usage in Core:
wrappers/src/shared_realm_cs.cpp#L305
TODO entry doesn't have a link to Github issue or Jira ticket lj): But this seems to work as well:
changelog
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: dangoslen/changelog-enforcer@c0b9fd225180a405c5f21f7a74b99e2eccc3e951. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.