feat(graph): add PJRTPlan execution wrapper with KV cache state management #75
Annotations
7 errors and 1 warning
|
Vet (excluding purego GPU bindings)
Process completed with exit code 1.
|
|
Vet (excluding purego GPU bindings):
internal/pjrt/serialize.go#L49
possible misuse of unsafe.Pointer
|
|
Vet (excluding purego GPU bindings):
internal/pjrt/pjrt.go#L303
possible misuse of unsafe.Pointer
|
|
Vet (excluding purego GPU bindings):
internal/pjrt/pjrt.go#L159
possible misuse of unsafe.Pointer
|
|
Vet (excluding purego GPU bindings):
internal/pjrt/client.go#L183
possible misuse of unsafe.Pointer
|
|
Vet (excluding purego GPU bindings):
internal/pjrt/buffer.go#L410
possible misuse of unsafe.Pointer
|
|
Vet (excluding purego GPU bindings)
not enough arguments in call to GemvQ5_0F32
|
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-go@v5. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
Loading