Skip to content
Issue labeler (policy)

The creation of a Realm instance consistently fails. As a result, the only workaround is to delete the existing data and initialize an empty Realm instance each time. #193

Sign in to view logs

The creation of a Realm instance consistently fails. As a result, the only workaround is to delete the existing data and initialize an empty Realm instance each time.

The creation of a Realm instance consistently fails. As a result, the only workaround is to delete the existing data and initialize an empty Realm instance each time. #193

Triggered via issue September 17, 2024 05:06
@yashaswinidcyashaswinidc
opened #3674 e24061b
Status Success
Total duration 18s
Artifacts –

issue-labeler.yml

on: issues
Matrix: label-issues-policy
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
label-issues-policy (feature.yml)
The following actions use a deprecated Node.js version and will be forced to run on node20: stefanbuck/github-issue-parser@c1a559d78bfb8dd05216dab9ffd2b91082ff5324, redhat-plumbers-in-action/advanced-issue-labeler@6ee6fddfd744ee26b977e6a0436916f256896971. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
label-issues-policy (bug.yml)
The following actions use a deprecated Node.js version and will be forced to run on node20: stefanbuck/github-issue-parser@c1a559d78bfb8dd05216dab9ffd2b91082ff5324, redhat-plumbers-in-action/advanced-issue-labeler@6ee6fddfd744ee26b977e6a0436916f256896971. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/