github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #4562] [Bug]: JSON Parsing Error with edge-alpine #8880

New Issue
Closed
opened 2026-04-10 19:10:28 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2026-04-10 19:10:28 -05:00
Owner
Copy Link

Originally created by @chrismilson on GitHub (Mar 7, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4562

Originally assigned to: @lelemm on GitHub.

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am using the digest sha256:e01806d1bcb53f1b2c0a5252b96a00c0d46a5acf60bddc9d88a166c6aa4cbd96 that was released 7 minutes ago.

I deploy in Kubernetes and I have a configmap, that mounts a file into /config/config.json, and I set the ACTUAL_CONFIG_PATH environment variable to /config/config.json.

The content of the json file is:

{"openId":{"authMethod":"oauth2","client_id":"actualbudget","client_secret":"","issuer":"https://login.example.com/context/path","server_hostname":"https://actual.example.com"}}

I get the following error when the pod starts:

undefined:1
https://login.example.com/context/path
^

SyntaxError: Unexpected token h in JSON at position 0
    at JSON.parse (<anonymous>)
    at coerce (/app/node_modules/convict/src/main.js:415:29)
    at /app/node_modules/convict/src/main.js:359:15
    at Array.forEach (<anonymous>)
    at overlay (/app/node_modules/convict/src/main.js:356:21)
    at /app/node_modules/convict/src/main.js:364:7
    at Array.forEach (<anonymous>)
    at overlay (/app/node_modules/convict/src/main.js:356:21)
    at /app/node_modules/convict/src/main.js:602:11
    at Array.forEach (<anonymous>)

Node.js v18.20.1

And then the pod exits.

How can we reproduce the issue?

Create a file config.json locally with the content above.

podman run -v .:/config -e ACTUAL_CONFIG_PATH=/config/config.json ghcr.io/actualbudget/actual@sha256:e01806d1bcb53f1b2c0a5252b96a00c0d46a5acf60bddc9d88a166c6aa4cbd96

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Safari, Firefox

Operating System

Linux

Originally created by @chrismilson on GitHub (Mar 7, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4562 Originally assigned to: @lelemm on GitHub. ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I am using the digest sha256:e01806d1bcb53f1b2c0a5252b96a00c0d46a5acf60bddc9d88a166c6aa4cbd96 that was released 7 minutes ago. I deploy in Kubernetes and I have a configmap, that mounts a file into /config/config.json, and I set the ACTUAL_CONFIG_PATH environment variable to /config/config.json. The content of the json file is: ```json {"openId":{"authMethod":"oauth2","client_id":"actualbudget","client_secret":"","issuer":"https://login.example.com/context/path","server_hostname":"https://actual.example.com"}} ``` I get the following error when the pod starts: ``` undefined:1 https://login.example.com/context/path ^ SyntaxError: Unexpected token h in JSON at position 0 at JSON.parse (<anonymous>) at coerce (/app/node_modules/convict/src/main.js:415:29) at /app/node_modules/convict/src/main.js:359:15 at Array.forEach (<anonymous>) at overlay (/app/node_modules/convict/src/main.js:356:21) at /app/node_modules/convict/src/main.js:364:7 at Array.forEach (<anonymous>) at overlay (/app/node_modules/convict/src/main.js:356:21) at /app/node_modules/convict/src/main.js:602:11 at Array.forEach (<anonymous>) Node.js v18.20.1 ``` And then the pod exits. ### How can we reproduce the issue? Create a file config.json locally with the content above. ```sh podman run -v .:/config -e ACTUAL_CONFIG_PATH=/config/config.json ghcr.io/actualbudget/actual@sha256:e01806d1bcb53f1b2c0a5252b96a00c0d46a5acf60bddc9d88a166c6aa4cbd96 ``` ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Safari, Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-04-10 19:10:28 -05:00
GiteaMirror commented 2026-04-10 19:10:29 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Mar 7, 2025):

try this:

{"openId":{"authMethod":"oauth2","client_id":"actualbudget","client_secret":"","discoveryURL":"https://login.example.com/context/path","server_hostname":"https://actual.example.com"}}

I changed issuer to discoveryURL

<!-- gh-comment-id:2705305606 --> @lelemm commented on GitHub (Mar 7, 2025): try this: ```json {"openId":{"authMethod":"oauth2","client_id":"actualbudget","client_secret":"","discoveryURL":"https://login.example.com/context/path","server_hostname":"https://actual.example.com"}} ``` I changed `issuer` to `discoveryURL`
GiteaMirror commented 2026-04-10 19:10:30 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

I get a different error:

/app/node_modules/convict/src/main.js:679
          throw new Error(output)
                ^

Error: configuration param 'openId.discoveryUrl' not declared in the schema
    at Object.validate (/app/node_modules/convict/src/main.js:679:17)
    at file:///app/src/load-config.js:285:14
    at ModuleJob.run (node:internal/modules/esm/module_job:195:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:337:24)
    at async loadESM (node:internal/process/esm_loader:34:7)
    at async handleMainPromise (node:internal/modules/run_main:106:12)

Node.js v18.20.1
<!-- gh-comment-id:2705309764 --> @chrismilson commented on GitHub (Mar 7, 2025): I get a different error: ``` /app/node_modules/convict/src/main.js:679 throw new Error(output) ^ Error: configuration param 'openId.discoveryUrl' not declared in the schema at Object.validate (/app/node_modules/convict/src/main.js:679:17) at file:///app/src/load-config.js:285:14 at ModuleJob.run (node:internal/modules/esm/module_job:195:25) at async ModuleLoader.import (node:internal/modules/esm/loader:337:24) at async loadESM (node:internal/process/esm_loader:34:7) at async handleMainPromise (node:internal/modules/run_main:106:12) Node.js v18.20.1 ```
GiteaMirror commented 2026-04-10 19:10:30 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Mar 7, 2025):

this is case sensitive. URL in the end

<!-- gh-comment-id:2705310844 --> @lelemm commented on GitHub (Mar 7, 2025): this is case sensitive. URL in the end
GiteaMirror commented 2026-04-10 19:10:31 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

Oh dear, pardon me. Let me try with the correct case

<!-- gh-comment-id:2705311345 --> @chrismilson commented on GitHub (Mar 7, 2025): Oh dear, pardon me. Let me try with the correct case
GiteaMirror commented 2026-04-10 19:10:31 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

Yep looking good after setting "discoveryURL".

<!-- gh-comment-id:2705311933 --> @chrismilson commented on GitHub (Mar 7, 2025): Yep looking good after setting "discoveryURL".
GiteaMirror commented 2026-04-10 19:10:31 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Mar 7, 2025):

Any other issues let us know. closing the issue

<!-- gh-comment-id:2705313618 --> @lelemm commented on GitHub (Mar 7, 2025): Any other issues let us know. closing the issue
GiteaMirror commented 2026-04-10 19:10:32 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

Thanks @lelemm - will this be a standard schema change coming in a future version?

<!-- gh-comment-id:2705313889 --> @chrismilson commented on GitHub (Mar 7, 2025): Thanks @lelemm - will this be a standard schema change coming in a future version?
GiteaMirror commented 2026-04-10 19:10:32 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

I see context in #4530 Thank you~

<!-- gh-comment-id:2705316424 --> @chrismilson commented on GitHub (Mar 7, 2025): I see context in #4530 Thank you~
GiteaMirror commented 2026-04-10 19:10:33 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Mar 7, 2025):

yes, we overhauled the config loader to use a schema checker, this made me have to create a new var

<!-- gh-comment-id:2705317191 --> @lelemm commented on GitHub (Mar 7, 2025): yes, we overhauled the config loader to use a schema checker, this made me have to create a new var
GiteaMirror commented 2026-04-10 19:10:33 -05:00
Author
Owner
Copy Link

@chrismilson commented on GitHub (Mar 7, 2025):

I see the message from coderabbitai:

it now handles backward compatibility by mapping discoveryURL to issuer when present.

Does this mean I shouldn't have seen this error?

<!-- gh-comment-id:2705319458 --> @chrismilson commented on GitHub (Mar 7, 2025): I see the message from coderabbitai: > it now handles backward compatibility by mapping discoveryURL to issuer when present. Does this mean I shouldn't have seen this error?
GiteaMirror commented 2026-04-10 19:10:34 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Mar 7, 2025):

I see the message from coderabbitai:

it now handles backward compatibility by mapping discoveryURL to issuer when present.

Does this mean I shouldn't have seen this error?

you should since you have values in the config.json. this is for the saved values in the database

<!-- gh-comment-id:2705321275 --> @lelemm commented on GitHub (Mar 7, 2025): > I see the message from coderabbitai: > > > it now handles backward compatibility by mapping discoveryURL to issuer when present. > > Does this mean I shouldn't have seen this error? you should since you have values in the config.json. this is for the saved values in the database
GiteaMirror commented 2026-04-10 19:10:34 -05:00
Author
Owner
Copy Link

@yieldhog commented on GitHub (Apr 6, 2025):

Documentation needs to be updated https://actualbudget.org/docs/experimental/oauth-auth#config-using-configuration-file

<!-- gh-comment-id:2781668104 --> @yieldhog commented on GitHub (Apr 6, 2025): Documentation needs to be updated https://actualbudget.org/docs/experimental/oauth-auth#config-using-configuration-file
GiteaMirror commented 2026-04-10 19:10:34 -05:00
Author
Owner
Copy Link

@lelemm commented on GitHub (Apr 7, 2025):

Documentation needs to be updated https://actualbudget.org/docs/experimental/oauth-auth#config-using-configuration-file

True, ty

<!-- gh-comment-id:2783895165 --> @lelemm commented on GitHub (Apr 7, 2025): > Documentation needs to be updated https://actualbudget.org/docs/experimental/oauth-auth#config-using-configuration-file True, ty
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#8880
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?