Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deployKeys.find is not a function when loading project #1674

Open
linusha opened this issue Aug 27, 2024 · 1 comment
Open

deployKeys.find is not a function when loading project #1674

linusha opened this issue Aug 27, 2024 · 1 comment
Assignees
Labels
🐞 bug Something isn't working

Comments

@linusha
Copy link
Contributor

linusha commented Aug 27, 2024

After updating Chrome (to Version 128.0.6613.85 (Official Build) (64-bit)), after five minutes the project https://github.com/engageLively/galyleo-dashboard still hasn't loaded. I clicked through the required-project-update dialog box before itr hanged. I am seeing this error in the console:

404 ()Understand this error
landing-page.cp-f59ae217.js:10768 Uncaught (in promise) TypeError: deployKeys.find is not a function
    at _callee7$ (landing-page.cp-f59ae217.js:10768:50)
    at tryCatch (deps.js:722:40)
    at Generator.invoke [as _invoke] (deps.js:950:22)
    at Generator.next (deps.js:777:21)
    at asyncGeneratorStep (__rootModule___commonjs-entry-35de395a.js:48:30)
    at _next (__rootModule___commonjs-entry-35de395a.js:70:15)

Originally posted by @rickmcgeer in #1673 (comment)

@linusha linusha self-assigned this Aug 27, 2024
@linusha linusha added the 🐞 bug Something isn't working label Aug 27, 2024
@LivelyKernel LivelyKernel deleted a comment Aug 27, 2024
@linusha
Copy link
Contributor Author

linusha commented Aug 27, 2024

@rickmcgeer could you do me a favor and check out this branch https://github.com/LivelyKernel/lively.next/tree/fix/unfound-deploy-keys inside of your lively next repository, start the server once more (no build required) and load the project again? Afterwards, please report if this fixes your problem.

I have a hard time reproducing your exact scenario, as the code takes ownership of the repository into account. I hope this fixes things? If so, I'll merge it asap.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant