#Flixpatrol error: failed to parse

1 messages · Page 1 of 1 (latest)

west hull
#

Using nightly build because I saw on the github that it was suppose to fix the flixpatrol error: failed to parse issue, but, unfortunately, still running into the same issue.

modern compassBOT
#

Welcome!

It looks like you have not yet completed #938455615741775902, this will allow us to help you quicker.

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type !close at any time to close this post.

modern compassBOT
west hull
#

Here is my log:

plush shoal
#

Finally someone else with the same error as me.

west hull
#

I had it working no problem a few weeks ago and then all of a sudden it rejects it. I was changing the link every couple of days to the most current date, but that didn't seem to be causing an issue... at least for a while

plush shoal
#

All was good for me as well and then it just stopped

#

Hopefully you will have more luck

west hull
#

I'm already at a standstill so doubt I'll have more luck

#

Afaik flixpatrol doesn't use restricted api or tokens. Was thinking maybe I was missing something in my config

steady spindle
#

except you are still on 1.18 per this log

#

@west hull you need to update to nighly, and the current nightly at that

west hull
#

Thought I did that. Do I need to set up a new docker container?

steady spindle
#

no...

#

you need to make sure your build is nightly and then you need to pull the most recent commit

mint jasper
west hull
#

Got it. Will try it again. Thanks!

#

Well that fixed it. Up and running again. Just set up my docker improperly the first time. Will that fix for flixpatrol be applied to the upcoming stable release as well?

steady spindle
#

It will eventually be pushed to the master branch