#Errors when compiling source with blueprint addition

1 messages · Page 1 of 1 (latest)

dusky ice
#

Hope I am just an idiot and missed something, will post the errors

formal nova
#

sounds to me like a yarn error

#

didn't read the log yet though haha

#

yep nailed it

dusky ice
#

yeah, it was when running yarn

formal nova
#

You'll have to run the yarn command so it initializes some dependencies.

dusky ice
#

Anything other than yarn? I do remember running yarn already as is mentioned in the install guide

root@web:/var/www/pterodactyl# yarn
00h00m00s 0/0: : ERROR: There are no scenarios; must have at least one.
root@web:/var/www/pterodactyl#
formal nova
#

Oh wait do you have cmdtest installed?

#

apt remove cmdtest

dusky ice
#

yeah after it errored, I did apt install the dependencies on the list, one of them did decide to install cmdtest when not specified

#

Oh I see, so I apt installed yarn which overwrote the one by npm seems like?

formal nova
#

Perchance. Try logging out and back in to your shell, might make yarn appear again

dusky ice
#

yarn is back by re-running npm i -g yarn, I did it before you sent the message

root@web:/var/www/pterodactyl# yarn
yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
success Already up-to-date.
Done in 0.94s.
formal nova
#

Alrighty, could you try to rm -r node_modules and run that yarn command again? Just to make sure it does it correctly.

dusky ice
#

Alright, thank you for the help so far

formal nova
#

no problem

#

once that command finishes feel free to run blueprint -rerun-install

dusky ice
#

Doing that now

#

Same errors

#

hmm

formal nova
#

weird

#

could you try to do blueprint -upgrade?

#

i'll take a closer look at your logs in the meantime

dusky ice
#

Same errors, good it is consistent at least

formal nova
#

lmfaoo

#

did any pterodactyl mods previously?

dusky ice
#

I am fairly certain I did not, I will check my local copy vs the panel source code

formal nova
#

You could rm the resources folder and go through the manual update steps which should fix the errors.

#

Then after that, run yarn and then run blueprint -upgrade again to repair blueprint

dusky ice
#

Alright, will try

#

hmm, alright, that worked

#

Is there a way to remove blueprint so I can retry the install from the guide to see if/where the issue still exists

formal nova
dusky ice
#

I think I know what differed, I did unzip the beta zip in /var/www/pterodactyl and replaced the files and not sure if blueprint upgrade does the same

formal nova
#

Blueprint upgrade does the same

dusky ice
#

hmmm...

formal nova
#

I think it was just some weird issue with one specific file, might have to do with panel updates or something.

dusky ice
#

I do know the script has a commit hash while I downloaded from latest release

#

not sure if the latest release and commit hash match though

formal nova
#

at the moment yes,
usually no

#

when i commit a new change it shouldn't match

dusky ice
#

Yep, I see, the hash does match the tag's hash

formal nova
#

until i submit a new release

dusky ice
#

does blueprint download the .zip or the source .zip

formal nova
#

blueprint -upgrade release .zip
blueprint -upgrade remote git clone

dusky ice
#

huh, then yeah, don't know the difference, maybe my install wasn't clean? I know I checked the version to ensure it was latest before installing blueprint, very weird

formal nova
#

probably, yeah

#

at least it works now

dusky ice
#

yeah, now I can start working on some extensions

formal nova
#

alrighty

#

visit /admin/extensions/blueprint to enable developer mode

dusky ice
#

done