starred/arr-scripts
1
0
Fork 0
mirror of https://github.com/RandomNinjaAtk/arr-scripts.git synced 2026-03-02 22:57:35 -05:00
Code Issues 55 Projects Packages Wiki Activity

[BUG] - Lidarr - parse error: Invalid numeric literal at line 2, column 0 #29

New issue
Closed
opened 2026-02-20 00:13:47 -05:00 by deekerman · 9 comments
deekerman commented 2026-02-20 00:13:47 -05:00
Owner
Copy link

Originally created by @Eric-sson on GitHub (Jul 29, 2023).

Application
Lidarr

Script
BeetsPostProcessor.bash
MetadataPostProcess.bash

Script Version
latest

Describe the bug
I am seeing the following error when running both scripts:

parse error: Invalid numeric literal at line 2, column 0

To Reproduce
Steps to reproduce the behavior:

  1. Go to 'Artist'
  2. Click on 'Preview Rename - Rename and Preview Retag - Retag'
  3. Scroll down to 'System - Events'
  4. See error

Expected behavior
Not sure if the error has any impact.

Originally created by @Eric-sson on GitHub (Jul 29, 2023). **Application** Lidarr **Script** BeetsPostProcessor.bash MetadataPostProcess.bash **Script Version** latest **Describe the bug** I am seeing the following error when running both scripts: parse error: Invalid numeric literal at line 2, column 0 **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Artist' 2. Click on 'Preview Rename - Rename and Preview Retag - Retag' 3. Scroll down to 'System - Events' 4. See error **Expected behavior** Not sure if the error has any impact.
deekerman 2026-02-20 00:13:47 -05:00
deekerman commented 2026-02-20 00:13:48 -05:00
Author
Owner
Copy link

@Eric-sson commented on GitHub (Jul 29, 2023):

BeetsPostProcessor.txt

@Eric-sson commented on GitHub (Jul 29, 2023): [BeetsPostProcessor.txt](https://github.com/RandomNinjaAtk/arr-scripts/files/12207294/BeetsPostProcessor.txt)
deekerman commented 2026-02-20 00:13:48 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Jul 29, 2023):

So a bug fix that was just pushed may help. But it looks like you didn't follow the installation instructions because your missing required packages.

One thing to note, I'm currently not using those scripts because I've found they cause issues with Lidarr. You should also only have it trigger on import and upgrade, not retag.

Follow the installation instructions and the most recent changes should fix some of the errors your seeing. Keep in mind, it's untested...

@RandomNinjaAtk commented on GitHub (Jul 29, 2023): So a bug fix that was just pushed may help. But it looks like you didn't follow the installation instructions because your missing required packages. One thing to note, I'm currently not using those scripts because I've found they cause issues with Lidarr. You should also only have it trigger on import and upgrade, not retag. Follow the installation instructions and the most recent changes should fix some of the errors your seeing. Keep in mind, it's untested...
deekerman commented 2026-02-20 00:13:49 -05:00
Author
Owner
Copy link

@Eric-sson commented on GitHub (Jul 30, 2023):

Which packages am I missing?

I was hoping that the both scripts would also work for existing files therefore I ticked retag as well. But I guess this will only work for newly downloaded files?

@Eric-sson commented on GitHub (Jul 30, 2023): Which packages am I missing? I was hoping that the both scripts would also work for existing files therefore I ticked retag as well. But I guess this will only work for newly downloaded files?
deekerman commented 2026-02-20 00:13:49 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Jul 30, 2023):

Didn’t look like beets was installed, so you didn’t follow the setup instructions correctly

@RandomNinjaAtk commented on GitHub (Jul 30, 2023): Didn’t look like beets was installed, so you didn’t follow the setup instructions correctly
deekerman commented 2026-02-20 00:13:49 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Jul 30, 2023):

This may have been fixed with that last change, but I have not tested it. Both scripts are deprecated because they can tend to cause more issues with Lidarr than is desirable and I personally don't recommend you use them.

For discussions around the uses/challenges these scripts tried to solve, see these discussions: https://github.com/RandomNinjaAtk/arr-scripts/discussions/47

The scripts will remain in this repo, but no support will be provided going forward.

@RandomNinjaAtk commented on GitHub (Jul 30, 2023): This may have been fixed with that last change, but I have not tested it. Both scripts are deprecated because they can tend to cause more issues with Lidarr than is desirable and I personally don't recommend you use them. For discussions around the uses/challenges these scripts tried to solve, see these discussions: https://github.com/RandomNinjaAtk/arr-scripts/discussions/47 The scripts will remain in this repo, but no support will be provided going forward.
deekerman commented 2026-02-20 00:13:49 -05:00
Author
Owner
Copy link

@wieluk commented on GitHub (Aug 1, 2023):

Lidarr is still trying to start /config/extended/scripts/MetadataPostProcess.bash

2023-08-01 09:12:43.2|Error|EventAggregator|NotificationService failed while processing [TrackFileRetaggedEvent]

[v1.2.6.3313] System.ComponentModel.Win32Exception (2): An error occurred trying to start process '/config/extended/scripts/MetadataPostProcess.bash' with working directory '/app/lidarr/bin'. No such file or directory
   at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec)
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at NzbDrone.Common.Processes.ProcessProvider.Start(String path, String args, StringDictionary environmentVariables, Action`1 onOutputDataReceived, Action`1 onErrorDataReceived) in ./Lidarr.Common/Processes/ProcessProvider.cs:line 189
   at NzbDrone.Common.Processes.ProcessProvider.StartAndCapture(String path, String args, StringDictionary environmentVariables) in ./Lidarr.Common/Processes/ProcessProvider.cs:line 229
   at NzbDrone.Core.Notifications.CustomScript.CustomScript.ExecuteScript(StringDictionary environmentVariables) in ./Lidarr.Core/Notifications/CustomScript/CustomScript.cs:line 308
   at NzbDrone.Core.Notifications.CustomScript.CustomScript.OnTrackRetag(TrackRetagMessage message) in ./Lidarr.Core/Notifications/CustomScript/CustomScript.cs:line 141
   at NzbDrone.Core.Notifications.NotificationService.Handle(TrackFileRetaggedEvent message) in ./Lidarr.Core/Notifications/NotificationService.cs:line 354
   at NzbDrone.Core.Messaging.Events.EventAggregator.PublishEvent[TEvent](TEvent event)

Why is this happening?

@wieluk commented on GitHub (Aug 1, 2023): Lidarr is still trying to start /config/extended/scripts/MetadataPostProcess.bash ``` 2023-08-01 09:12:43.2|Error|EventAggregator|NotificationService failed while processing [TrackFileRetaggedEvent] [v1.2.6.3313] System.ComponentModel.Win32Exception (2): An error occurred trying to start process '/config/extended/scripts/MetadataPostProcess.bash' with working directory '/app/lidarr/bin'. No such file or directory at System.Diagnostics.Process.ForkAndExecProcess(ProcessStartInfo startInfo, String resolvedFilename, String[] argv, String[] envp, String cwd, Boolean setCredentials, UInt32 userId, UInt32 groupId, UInt32[] groups, Int32& stdinFd, Int32& stdoutFd, Int32& stderrFd, Boolean usesTerminal, Boolean throwOnNoExec) at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo) at NzbDrone.Common.Processes.ProcessProvider.Start(String path, String args, StringDictionary environmentVariables, Action`1 onOutputDataReceived, Action`1 onErrorDataReceived) in ./Lidarr.Common/Processes/ProcessProvider.cs:line 189 at NzbDrone.Common.Processes.ProcessProvider.StartAndCapture(String path, String args, StringDictionary environmentVariables) in ./Lidarr.Common/Processes/ProcessProvider.cs:line 229 at NzbDrone.Core.Notifications.CustomScript.CustomScript.ExecuteScript(StringDictionary environmentVariables) in ./Lidarr.Core/Notifications/CustomScript/CustomScript.cs:line 308 at NzbDrone.Core.Notifications.CustomScript.CustomScript.OnTrackRetag(TrackRetagMessage message) in ./Lidarr.Core/Notifications/CustomScript/CustomScript.cs:line 141 at NzbDrone.Core.Notifications.NotificationService.Handle(TrackFileRetaggedEvent message) in ./Lidarr.Core/Notifications/NotificationService.cs:line 354 at NzbDrone.Core.Messaging.Events.EventAggregator.PublishEvent[TEvent](TEvent event) ``` Why is this happening?
deekerman commented 2026-02-20 00:13:50 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Aug 1, 2023):

@wieluk You’re on your own, read the previous comment for details

@RandomNinjaAtk commented on GitHub (Aug 1, 2023): @wieluk You’re on your own, read the previous comment for details
deekerman commented 2026-02-20 00:13:50 -05:00
Author
Owner
Copy link

@wieluk commented on GitHub (Aug 1, 2023):

Oh I see where it came from. The autoconfig added the metadata post process connection thanks anyway.

@wieluk commented on GitHub (Aug 1, 2023): Oh I see where it came from. The autoconfig added the metadata post process connection thanks anyway.
deekerman commented 2026-02-20 00:13:50 -05:00
Author
Owner
Copy link

@RandomNinjaAtk commented on GitHub (Aug 1, 2023):

@wieluk Yeah, that is true, when these scripts first came out it added them… However, AutoConfig no longer does that, but there isn’t an easy way to reverse the configuration for existing setups if they were already added. So if you remove them, they shouldn’t be re-added as long as your on the latest scripts updates…

@RandomNinjaAtk commented on GitHub (Aug 1, 2023): @wieluk Yeah, that is true, when these scripts first came out it added them… However, AutoConfig no longer does that, but there isn’t an easy way to reverse the configuration for existing setups if they were already added. So if you remove them, they shouldn’t be re-added as long as your on the latest scripts updates…
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
Needs Triage

   
Not Reproducible

   
Upstream Issue

   
User Error

   
bug

   
documentation

   
enhancement

   
good first issue

   
help wanted

   
invalid

   
lidarr

   
lidarr

   
question

   
radarr

   
readarr

   
sabnzbd

   
sonarr

   
synology (host)

   
unraid (host)

   
waiting for logs

   
wontfix
No labels
Needs Triage
Not Reproducible
Upstream Issue
User Error
bug
documentation
enhancement
good first issue
help wanted
invalid
lidarr
lidarr
question
radarr
readarr
sabnzbd
sonarr
synology (host)
unraid (host)
waiting for logs
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/arr-scripts#29
No description provided.