Skip to content
triage_issues

[QST] How to get candidate features after using pre-trained embedding tables? #393

Sign in to view logs

[QST] How to get candidate features after using pre-trained embedding tables?

[QST] How to get candidate features after using pre-trained embedding tables? #393

Triggered via issue May 7, 2024 12:02
@hkristof03hkristof03
opened #1239 eb1e541
Status Success
Total duration 25s
Artifacts –

triage.yml

on: issues
triage_issue  /  triage_issue
14s
triage_issue / triage_issue
Fit to window
Zoom out
Zoom in

Annotations

1 error and 3 warnings
triage_issue / triage_issue
Process completed with exit code 1.
triage_issue / triage_issue
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
triage_issue / triage_issue
The following actions uses node12 which is deprecated and will be forced to run on node16: tibdex/github-app-token@36464acb844fc53b9b8b2401da68844f6b05ebb0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
triage_issue / triage_issue
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/