Upload was not successful, rerunning about solana-candy-factory

[advanztek]

@advanztek how did you fix this?

Hi @dant89, it seems like your NFTs names or description are too long. So go to cache and change to false the ones that have a long name or have an issue. After that run the metaplex upload command again.

[advanztek]

This is the other error from gitbash

at WrappedLayout.encode (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\borsh\src\index.ts:96:24)
saving config line 1990-1999 failed RangeError: encoding overruns Buffer
at Blob.encode (C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:2325:13)
at Structure.encode (C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:1263:26)
at WrappedLayout.encode (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\borsh\src\index.ts:96:24)
at WrappedLayout.encode (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\borsh\src\index.ts:96:24)
at Structure.encode (C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:1263:26)
at C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:1113:25
at Array.reduce ()
at Sequence.encode (C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:1112:22)
at Structure.encode (C:\Users\user\metaplex\js\packages\cli\node_modules\buffer-layout\lib\Layout.js:1263:26)
at WrappedLayout.encode (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\borsh\src\index.ts:96:24)
upload was not successful, rerunning

[kevinfaveri]

You should just re-run the upload until it is successful = true

[advanztek]

Okay thanks, I'll keep on trying it.

[advanztek]

It's still showing false after retrying for about an hour. Is this a normal thing, so that I can keep trying?

Thank you for your response in advance.

[advanztek]

Hi @kevinfaveri, still having the same issue. Please is this a normal thing when deploying to the mainnet? Or there is something causing this?

Coz everything has been uploaded to arewave already all I need is the successful = true.

Please 🙏 your response really means a lot. About 7 SOL gone already.

[advanztek]

Hi @kevinfaveri, still waiting for your response please. Am really frustrated right now. I've been trying this more than 5 hours and it still keeps saying "upload was not successful, rerunning".

[kevinfaveri]

Are your NFT "name" keys long? I'm not sure what is happening honestly, I would need more logs to think about something, but as far as I know, it should be working as expected. Anyway, this seems like an issue you could open on the Metaplex github repo as an issue too

[advanztek]

They're have a max of 32 CHARS, can I reupload it without paying another SOL again?

How can I send you the cache?

[advanztek]

mainnet-beta-temp.zip

[advanztek]

Hi @kevinfaveri I reuploaded everything for the second time.

Then running this command
ts-node ~/metaplex/js/packages/cli/src/candy-machine-cli.ts create_candy_machine --env mainnet-beta --keypair ~/.config/solana/candyfactory-mainnet.json --price 0.49 > ./logs/main/candy-machine-log.txt

I got the error below. Please any form of help will be appreciated.

Transaction simulation failed: Error processing Instruction 0: custom program error: 0x139
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ invoke [1]
Program 11111111111111111111111111111111 invoke [2]
Program 11111111111111111111111111111111 success
Program log: Custom program error: 0x139
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ consumed 21820 of 200000 compute units
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ failed: custom program error: 0x139
(node:17216) UnhandledPromiseRejectionWarning: Error:
at Function.parse (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\anchor\src\error.ts:30:14)
at Object.rpc [as initializeCandyMachine] (C:\Users\user\metaplex\js\packages\cli\node_modules@project-serum\anchor\src\program\namespace\rpc.ts:23:42)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use node --trace-warnings ... to show where the warning was created)
(node:17216) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:17216) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

[dant89]

@advanztek how did you fix this?