stackblitz / webcontainer-core

Dev environments. In your web app.
https://webcontainers.io
MIT License
3.7k stars 139 forks source link

Cloning large repositories fails #1168

Closed james-pre closed 2 months ago

james-pre commented 10 months ago

Describe the bug

When cloning very large git repositories from GitHub, StackBlitz fails to clone it after some time.

Link to the blitz that caused the error

https://stackblitz.com/~/github.com/BabylonJS/babylon.js

Steps to reproduce

  1. Open the blitz
  2. "Cloning BabylonJS/babylon.js on branch master"
  3. "Could not clone BabylonJS/babylon.js. Please check that this repository exists and try again."

Expected behavior

It should clone the repository, but fails to do so. I presume this is because the repository in questions is over 5GB is size for a full clone.

Parity with Local

Screenshots

image

Platform

Version = 1.72.0
Hash = 27729c2178447b5efac2fb0da8e0c65b16a43747
WebContainer = 33975f1d

Browser name  = Chrome
Full version  = 115.0.0.0
Major version = 115
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36
performance.memory = {
  "totalJSHeapSize": 67637472,
  "usedJSHeapSize": 64924804,
  "jsHeapSizeLimit": 2066219008
}

Additional context

I can clone other repositories fine, but not BabylonJS or my fork of it (dr-vortex/babylon.js).

Nemikolh commented 10 months ago

Hi @dr-vortex! :wave: Thanks for opening this issue!

I've created an internal ticket and we'll keep you posted :+1:

james-pre commented 2 months ago

@Nemikolh Any updates on this?

Nemikolh commented 2 months ago

Hey @dr-vortex! We've recently made some changes to our infra that made the cloning possible. It's a bit slow the first time but subsequent page loads are much faster and the initial error is gone:

project-load

There's still more work to do to have this fully working. If you can try it out right now and let us know what issues your run into, please add comments to this issue!