webcrateapp / webcrate Goto Github PK

🏷️ WebCrate Version

v1.5.5

⚙️ Environment

Firefox, Chrome

🐞 Describe the bug

Using a Deta Space app, a public crate is not reachable on its public URL.

📚 To Reproduce

I'm using this app on deta.space. After creating a crate and adding a link to it, I clicked "Make public" and tried browsing to the link that was generated. This has (so far) returned two different error messages. This is one:

Error Type:

Runtime.ExitError
Error Message:

RequestId: df914776-af77-4b6e-b114-c315a4f838f6 Error: Runtime exited with error: exit status 1
Logs:

time="2023-08-30T20:04:14Z" level=info msg="serving logs listener on sandbox.localdomain:1234" agent=logsApiAgent
TELEMETRY	Name: telemetry-extension	State: Already subscribed	Types: [Function]
Listening on port 8080

I have also seen another error, which seems like a config issue:

Error Type:
&alloc::boxed::Box

Error Message:
error sending request for url (http://127.0.0.1:8080/crate/public/<crate-id>): connection closed before message completed

Logs:
<empty>

💡 Expected behavior

Some sort of app view that allowed me to see the links in the crate.

📋 Additional context

No response

More info: #71

🐞 Describe the bug

I just installed WebCrate. I tried adding a link to one of my empty Crates. It doesn't work :(

📚 To Reproduce

Click add link, enter a URL, click add link to confirm

💡 Expected behavior

The link should be added to my crate

🖼️ Screenshots

⚙️ Environment

• OS: macOS 10.15.7
• Browser version: Firefox 91
• WebCrate version (can be found under ?): v.0.1.0

📋 Additional context
n/a

🏷️ WebCrate Version

v1.4.2

⚙️ Environment

Chrome, Safari

🐞 Describe the bug

In a link detail 'box', selecting Move Link opens the window as expected, however clicking on the dropdown menu under the "Select a crate to move the link" button performs a quick animation, then returns to the main crate page without allowing for a selection to be made.

As far as i recall, this worked prior to the update applied today.

📚 To Reproduce

• click a link to expand link details
• click the disclosure icon (...) for more options
• select Move Link
• click the selection icon in the resulting window to pick a new destination crate.
• enjoy the animation
• view the crate contents

💡 Expected behavior

a list of available crates should appear, from which a selection can be made.

📋 Additional context

No response

🏷️ WebCrate Version

v1.2.0

⚙️ Environment

Firefox

🐞 Describe the bug

I have about 25 crates in WebCrate. On the sidebar, I can only see 20 of them. I can still search for the other missing ones, but I'm not seeing a way to display them. Unsure if this limit is intentional or not.

📚 To Reproduce

1. Add >20 crates
2. Count number of crates in sidebar
3. Hopefully find discrepancy

💡 Expected behavior

All crates would be included in sidebar.

📋 Additional context

No response

Summary: Can't run new-space branch (63cf695) locally (with Node 20.4.0, NPM 9.8.0). (But, it seems to run well on Deta.Space.)

🐞 Describe the bug

Hi Maximilian or friend,

Thank you for Deta & WebCrate. Looking forward to using them & contributing.

Environment: Current Manjaro (stable Arch, x64) Linux (current stable kernel 6.3.5-2), Node 20.4.0, NPM 9.8.0 (installed via nvm). (All the below is running not as root/via sudo, but as an ordinary user.)

FIRST: (but potentially unrelated): Instead of space dev I've tried npm run build. That complained about needing rimraf. So I've installed it with npm install rimraf.
FYI: That reports: 78 vulnerabilities (51 moderate, 25 high, 2 critical).

SECOND:

space --version
space version 0.3.13
space dev

Checking for running micros...

 Starting 1 micro servers...

Micro app (primary)
L url: http://localhost:4200/

[app] 
[app] > [email protected] start
[app] > NODE_ENV=production node build/index.js
[app] 
[app] 
[app] node:internal/modules/cjs/loader:1051
[app]   throw err;
[app]   ^
[app] 
[app] Error: Cannot find module '/share/pkehl/GIT/webcrate/build/index.js'
[app]     at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)
[app]     at Module._load (node:internal/modules/cjs/loader:901:27)
[app]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
[app]     at node:internal/main/run_main_module:23:47 {
[app]   code: 'MODULE_NOT_FOUND',
[app]   requireStack: []
[app] }
[app] 
[app] Node.js v20.4.0
[app] 
Command `/home/pkehl/.nvm/versions/node/v20.4.0/bin/npm run start` exited.
Error: Get "http://localhost:4201/__space/actions": dial tcp [::1]:4201: connect: connection refused

THIRD: on Deta.Space:

space new
...
space push
...
Checking for running micros...

 Starting 1 micro servers...

Micro app (primary)
L url: http://localhost:4200/

[app] 
[app] > [email protected] start
[app] > NODE_ENV=production node build/index.js
[app] 
[app] 
[app] node:internal/modules/cjs/loader:1051
[app]   throw err;
[app]   ^
[app] 
[app] Error: Cannot find module '/share/pkehl/GIT/webcrate/build/index.js'
[app]     at Module._resolveFilename (node:internal/modules/cjs/loader:1048:15)
[app]     at Module._load (node:internal/modules/cjs/loader:901:27)
[app]     at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:83:12)
[app]     at node:internal/main/run_main_module:23:47 {
[app]   code: 'MODULE_NOT_FOUND',
[app]   requireStack: []
[app] }
[app] 
[app] Node.js v20.4.0
[app] 
Command `/home/pkehl/.nvm/versions/node/v20.4.0/bin/npm run start` exited.
Error: Get "http://localhost:4201/__space/actions": dial tcp [::1]:4201: connect: connection refused
...

# BUT, SURPRISINGLY:
2023/07/06 15:16:21 All micros built successfully
...
2023/07/06 15:16:44 starting installation...
...
2023/07/06 15:17:24 completed...
                                                                  
✓ Successfully pushed your code and updated your Builder instance!
# That seems to run well (so far).

Please, shed some light. Node/NPM is outside of my expertise, but wherever I can, I'll contribute, I'll update docs...

Thank you in advance for any tips on developing locally.

🏷️ WebCrate Version

v1.5.2

⚙️ Environment

Chrome

🐞 Describe the bug

Due to the new deta space change, new webcrate app instances could not be accessed in the old way alias.username.deta.app., and old apps are unable to be accessed in the same way by February 13th:

Under the old system, a Space app was available under alias.username.deta.app. This means if you share a link to your Space app, it will expose your Deta username. For some users this may be ok, but we want the default on Space to be as secure and private as possible. We also had to generate one SSL certificate per user, and we’ve been having reliability issues on this front.

Going forward, to fix these issues, all Space apps have new a domain in the following format: alias-random.deta.app. Each app gets its own random suffix, which will make it much harder to guess an app’s domain. We are also moved from double subdomains to single subdomains. This makes issuing SSL certificates easier and further improves security, as all a user’s apps get their own site.

I spent a full afternoon to find out why the website could not be accessed in the old way lol, deta docs are always splattered around

📚 To Reproduce

Opening a new app, we would get a domain like this: webcrate-1-b8374455.deta.app

💡 Expected behavior

Docs needed to be updated (and maybe we should find a way to work around this problem, as the new domain is toooooo hard to remember)

📋 Additional context

No response

🏷️ WebCrate Version

v1.5.2

⚙️ Environment

Other (please specify below)

🐞 Describe the bug

📚 To Reproduce

Install current app

💡 Expected behavior

no double install of default folders

📋 Additional context

No response

https://addons.mozilla.org/en-US/firefox/addon/webcrate/

Please let me know if I'm missing something, thanks!

Discussed in https://github.com/WebCrateApp/webcrate/discussions/37

Originally created by @dzakki in #37

🏷️ WebCrate Version

v1.3.0

⚙️ Environment

Other (please specify below)

🐞 Describe the bug

Links to open feature request or ask community are broken so I use the classic bug report.

Hi,

Is there any plan to self-host the app without the need of deta base or any others third parties?

Thanks,

📚 To Reproduce

None

💡 Expected behavior

None

📋 Additional context

No response

🏷️ WebCrate Version

v?

⚙️ Environment

Chrome

🐞 Describe the bug

image of a link is broken

📚 To Reproduce

I add a link via extension
in this case webcrate.app itself
when we click to preview this link

💡 Expected behavior

image is not shown

📋 Additional context

No response

🏷️ WebCrate Version

v1.4.3

⚙️ Environment

Firefox

🐞 Describe the bug

When I click on install on the install button, it generates an error

Error: Cert not issued yet, please try again after a few minutes. If the error
persists, please login again and contact us.

Either it's the platform or there's an issue with the installation of the app on the platform, any guidance would be appreciated.

📚 To Reproduce

Just sign up on deta, and login.
After login, install WebCrate.

💡 Expected behavior

Should install.

📋 Additional context

🏷️ WebCrate Version

v1.0.2

⚙️ Environment

Mobile

🐞 Describe the bug

When I try adding a link it just says Error: Network Error instead of adding the link

📚 To Reproduce

Install the PWA version on Android and try adding a link

💡 Expected behavior

Should just add a link to the webcrate

📋 Additional context

No response

🏷️ WebCrate Version

v1.4.0

⚙️ Environment

Chrome, Other (please specify below)

🐞 Describe the bug

I use WebCrate on Chrome and Brave.
Trying to share what is supposed to be a public link (https://webcrate.nikahmad.deta.app/link/public/j6oIXfg4tJqjOXTG)

📚 To Reproduce

Create a link in a Crate and then enable sharing.
Open other browser or a new private tab, then open the shared link.

💡 Expected behavior

That link can be open on any browser.

📋 Additional context

It should work like sharing this crate: https://webcrate.nikahmad.deta.app/crate/public/vs8m95QyZesqRZjW

🏷️ WebCrate Version

v1.5.2

⚙️ Environment

Other (please specify below)

🐞 Describe the bug

The rust folder is missing

📚 To Reproduce

install the app and add two folders

💡 Expected behavior

rust folder should also be available

📋 Additional context

No response

🏷️ WebCrate Version

v.0.11.0

⚙️ Environment

Chrome

🐞 Describe the bug

When opening webcrate via deta.space, directly through an URL or via the browser extension, I am redirected from webcrate to deta.space in an endless loop.

📚 To Reproduce

Opening the webcrate website.

💡 Expected behavior

Launching into my application

📋 Additional context

No response