cowch/lst_v3
1
0
Fork 0
Code Issues 20 Pull Requests Actions Packages Projects Releases 10 Wiki Activity

[BUG - Server] inv history crashing on restart #27

New Issue
Closed
opened 2026-06-01 06:55:28 -05:00 by cowch · 1 comment
cowch commented 2026-06-01 06:55:28 -05:00
Owner
Copy Link

Summary

Briefly explain the issue.

when the app restarted it will crash and send an email.

Steps To Reproduce

  1. Go to ...
  2. Click ...
  3. Scan ...
  4. Error occurs ...

Expected Behavior

What should have happened? just pass as it should already have the data for the day

Actual Behavior

What actually happened instead? the app will crash and send over an eamil with the below logs saying " values() must be called with at least one value"

Severity

  • Low
  • Medium
  • High
  • Critical

Environment

Example:

  • Production
Error: values() must be called with at least one value
    at PgInsertBuilder.values (file:///D:/LST_V3/node_modules/drizzle-orm/pg-core/query-builders/insert.js:32:13)
    at historicalInvImport (file:///D:/LST_V3/dist/logistics/logistics.historicalInv.js:92:102)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
# Summary Briefly explain the issue. when the app restarted it will crash and send an email. --- # Steps To Reproduce 1. Go to ... 2. Click ... 3. Scan ... 4. Error occurs ... --- # Expected Behavior What should have happened? just pass as it should already have the data for the day --- # Actual Behavior What actually happened instead? the app will crash and send over an eamil with the below logs saying " values() must be called with at least one value" --- # Severity - [ ] Low - [ ] Medium - [x] High - [ ] Critical --- # Environment Example: - Production --- ```txt Error: values() must be called with at least one value at PgInsertBuilder.values (file:///D:/LST_V3/node_modules/drizzle-orm/pg-core/query-builders/insert.js:32:13) at historicalInvImport (file:///D:/LST_V3/dist/logistics/logistics.historicalInv.js:92:102) at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
cowch added the serverbug labels 2026-06-01 06:55:28 -05:00
cowch commented 2026-06-01 16:58:21 -05:00
Author
Owner
Copy Link

corrections were made to what was considered activations.... 108 was actually the ai bot not waste

corrections were made to what was considered activations.... 108 was actually the ai bot not waste
cowch closed this issue 2026-06-01 16:58:21 -05:00
Sign in to join this conversation.
main
Branches Tags
Labels
Clear labels
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 feature
New feature
frontend
help wanted
Need some help
 invalid
Something is wrong
 mobile
question
More information is needed
 server
wontfix
This won't be fixed
No Label bug server
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cowch
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: cowch/lst_v3#27
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?