Closed hassnian closed 3 months ago
I've fixed that deploys should work against other branches, so prury can test tho
Name | Link |
---|---|
Latest commit | 681e53aed4c8c4d1cdc111897fd95b18171cef11 |
Latest deploy log | https://app.netlify.com/sites/koda-canary/deploys/65f2e13afa46af00083e8290 |
Deploy Preview | https://deploy-preview-9711--koda-canary.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Netlify can't build tho
1:18:40 PM: [error] Nuxt Build Error: [vite:load-fallback] Could not load /opt/build/repo/composables/drop/massmint/useDropMassmintState (imported by components/collection/drop/modal/PaidMint.vue?vue&type=script&setup=true&lang.ts): ENOENT: no such file or directory, open "/opt/build/repo/composables/drop/massmint/useDropMassmintState" 1:18:40 PM: βELIFECYCLEβ Command failed with exit code 1. (https://ntl.fyi/exit-code-1)
Netlify can't build tho
1:18:40 PM: [error] Nuxt Build Error: [vite:load-fallback] Could not load /opt/build/repo/composables/drop/massmint/useDropMassmintState (imported by components/collection/drop/modal/PaidMint.vue?vue&type=script&setup=true&lang.ts): ENOENT: no such file or directory, open "/opt/build/repo/composables/drop/massmint/useDropMassmintState" 1:18:40 PM: βELIFECYCLEβ Command failed with exit code 1. (https://ntl.fyi/exit-code-1)
deployed https://deploy-preview-9711--koda-canary.netlify.app/
yup testing
seems list maybe it's not done yet as I see it's draft PR
mints took >1 minute to render when I visited, but probably not scope of this pr
minted 3
the same happened (in the mass list there were no items)
after coming back to the drop page
Minor Allowlist bug I have eligible on left, button on right not eligible
okay, trying to battle test it before it goes out, sweet work @hassnian !
Probably add sharing on Farcaster but probably coming once merged I guess as it's on main
already
Got hung up on slow rendering arts (as I expected), minor for now https://deploy-preview-9711--koda-canary.netlify.app/ahp/drops/sailwings
Can be done follow up
that preheating error that we were talking about is happening when you cancel the massminting and try again hassnian, i see now
also if i cancel the massmint dialog and try to massmint again the button will not work, but probably a problem coming from refactor, will check
but probably a problem coming from refactor, will check
thought that refactor should actually solve this?
waiting for:
fix(PaidGenerative.vue): empty listing cart
numbering is missing but I guess it's because of something else?
waiting for:
mints took >1 minute to render when I visited
yup, but probably outside scope of this one
fix(PaidGenerative.vue): empty listing cart
numbering is missing but I guess it's because of something else? ![image](https://private-user-images.githubusercontent.com/
yup, its something else
but probably a problem coming from refactor, will check
thought that refactor should actually solve this?
i'm still checking for bugs on the open PR from daiagi, button state got refactored recently there
@kodadot/internal-dev
https://fxart-beta.kodadot.workers.dev/drops/meadow
returning minted
0
{
"id": "genmeadow",
"chain": "ahk",
"collection": "379",
"disabled": 0,
"image": "ipfs://bafkreic7ii2fvo3fhe557pyozhzitkfnhgmxovaebnf3shqmjiva42erb4",
"name": "MEADOW",
"banner": "ipfs://bafkreic7ii2fvo3fhe557pyozhzitkfnhgmxovaebnf3shqmjiva42erb4",
"alias": "meadow",
"content": "ipfs://bafybeicdv7iu5racra3vsvg2k2uvp2jxvb534h67f6lqdwidhmvzg2tjou",
"type": "paid",
"max": null,
"minted": 0,
"meta": "20000000000",
"price": "5000000000",
"holder_of": null,
"location": null,
"start_at": null
}
Hey @kodadot/internal-dev, is there any critical review from you? Otherwise, I want to have it in tomorrow's release as it was tested with a few people. It looks solid to me.
We can always do post-refactor, yet we want it out, which I believe helps us on the revenue side.
Then drops-refactor
can be merged to main
fxart-beta.kodadot.workers.dev/drops/meadow
returning
minted
0
related https://github.com/kodadot/private-workers/issues/80
you can use this instead at the moment (afaik until now we still use this) fxart-beta.kodadot.workers.dev/drops/meadow/status
Hey @kodadot/internal-dev, is there any critical review from you?
For now, I'm still unwell today, unable to review, I believe in @prury ππ» Same for this PR https://github.com/kodadot/nft-gallery/pull/9709
I will check tomorrow after it merged ππ»ππ»ππ»
I'm still unwell today
oh, get well!
@hassnian let's fix merge conflicts, hopefully nothing much critical, I'm happy to test it afterwards
Once this PR is merged, let's make PR to merge drops-refactor
to main
noticed that time estimation on listing its not correct, but can be fixed later it resets after some time, like it was estimating the time for each of nfts to be listed
mobile needs some small work:
not being able to type in the amount is on purpose?
i would not merge this PR until the following is solved: π«
mobile needs some small work:
we can stack the two if it does not fit
@hassnian forgot to push maybe?
i don't see your latest changes
@hassnian forgot to push maybe?
i don't see your latest changes
was planning re-request a review once I was done with all the comments
was planning re-request a review once I was done with all the comments
you're right. apologies
Gonna test, if it would be okayish, we are merging and then to the main branch, so @prury have like last 2-3 hours for final checks if something is missing
works! found something minor, but I guess 409 should not be issue in this case? I've clicked once and then clicked elsewhere so probably that's why.
|
@hassnian let us know when you are good to go, I see you are adjusting something
@hassnian let us know when you are good to go, I see you are adjusting something
will do
Mobile does job well too
all @daiagi comments have been solved, should be ok now , checking @prury comments
How come conflicts surfaced? There was none last 30 minutes. Coming from?
How come conflicts surfaced? There was none last 30 minutes. Coming from?
yes, because i pulled main into drops-refactor
@yangwao revert?
merge this into drop-reafctor
and then reconcile with main?
it's gonna be a bomb shell
it's gonna be a bomb shell
I don't think so as if you pulled main
-> drops-refactor
, this PR shows conflicts between drops-refactor
<-> drops-refactor-mass-mint
, hope I'm not wrong.
Even I'm aware of
@hassnian still up? very last one batch of merge conflicts. Then I will fly over to test it to make sure it's working.
@hassnian still up? very last one batch of merge conflicts. Then I will fly over to test it to make sure it's working.
checking
@hassnian look like some code never got pushed
i got some comments you say fixed but doesn't appear fixed to me
i got some comments you say fixed but doesn't appear fixed to me
if it's not critical can we resolve in follow up, when this would be merged against main
π
so far mass mint has worked in primary case for me and others. There was some edge cases I've seen
if it's not critical can we resolve in follow up, when this would be merged against main π
your wish is my command
your wish is my command
@yangwao i didn't get the dune reference / joke
guess i need to watch Dune2
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
No data about Coverage
No data about Duplication
PR Type
Context
Needs QA check
@kodadot/qa-guild please review
amount of nfts that you can mint depends on:
when minting one nft , ensure it's not generating a new one , ie it's using the same
Needs Design check
Did your issue had any of the "$" label on it?
Screenshot πΈ