codesandbox / codesandbox-ci-ui Goto Github PK

This is probably not the best repo to report this, but couldn't find a better place.

It seems that if we quickly push (force-push?) to a single PR then multiple comments from CodeSandbox might appear.

I've encountered this several times, most recently here:
statelyai/xstate#888 (comment)
statelyai/xstate#888 (comment)

Hi, I hope I'm in the right repo here - this seems to be the most "CSB CI"-themed Repo.

We would love it if there were a way of configuring the text of the CodeSandbox-CI bot comment.

Especially the ability to have the package install instructions right in the comment would be incredibly valuable, as at the moment, we often have to add screenshots in hand-written comments to explain to contributors how to install the CI build.

Hello, I couldn't find the dedicated codesandbox-ci repo, so please feel free to transfer this issue if I've just missed it 😅

Our complete list of sandboxes in react-spring is about 20. But only 10 seem to be built from the configuration, as seen in a recent PR but sometimes when there are more sandboxes in the issue or PR they are still built as can be seen in this PR.

Maybe i've done something wrong? Or maybe there's a maximum and it needs documenting? I did put this in the Discord, but received no reply.

I assume that the output packages of CodeSandbox CI expire after some time. However, there is no mention of when in https://codesandbox.io/docs/ci. It would be great to have an order of magnitude. This was raised during an internal discussion with @mnajdova.

Hi again, I still hope I'm in the correct repo :)

We'd like to exclude renovate/* branches from the CSB CI, as those renovate-PRs already add a lot of noise, and the checks from CSB add additional noise on top of that. Could you maybe add a configuration option for that?

Installing a GitHub App is very difficult on a organization repository due to lack of permission. 😅

Not sure if this is appropriate here.

yarn v2 no longer installs packages from arbitrary urls.

Right now

diff --git a/package.json b/package.json
index 2f92273..b2e2b2a 100644
--- a/package.json
+++ b/package.json
@@ -3,6 +3,7 @@
   "version": "0.1.0",
   "private": true,
   "dependencies": {
+    "@material-ui/core": "https://pkg.csb.dev/mui-org/material-ui/commit/e9a9cdb2/@material-ui/core",
     "@testing-library/jest-dom": "^5.11.4",
     "@testing-library/react": "^11.1.0",
     "@testing-library/user-event": "^12.1.10",

fails with

$ yarn
➤ YN0000: ┌ Resolution step
➤ YN0001: │ Error: @material-ui/core@https://pkg.csb.dev/mui-org/material-ui/commit/e9a9cdb2/@material-ui/core isn't supported by any available resolver
    at i.getResolverByDescriptor (/home/eps1lon/Development/throwaway/cra4-mui5-react17/.yarn/releases/yarn-2.3.3.cjs:2:314629)

I asked in their discord and they confirmed that tarballs need the .tgz extension. I tried if this url already existed but got a 404: https://pkg.csb.dev/mui-org/material-ui/commit/e9a9cdb2/@material-ui/core.tgz

Alternatives:

1. download as .tgz and install does not work since the codesandbox replaced dependency ranges with https://csb.*
2. write custom yarn resolver

We're trying to use CS:CI for a React component for the first time and running into an interesting error that maybe y'all can help with.

Here's the base sandbox which is working fine:
https://codesandbox.io/s/npm-embeddable-explorer-zotwkv

Here's a PR which uses that sandbox in its sandbox config:
apollographql/embeddable-explorer#31

The packages in that build can be installed and work in an npm project. However, the actual sandbox fork says the module is missing. When I look into the sources, I don't see @apollo/explorer anywhere in the node_modules like I'd expect. Here's a screenshot of what I'm looking at:

In the original sandbox, the @apollo/explorer module does show up in the node_modules.

Hopefully that's helpful, let me know if you need any more info from us.

Github is currently having issues: https://www.githubstatus.com/incidents/2y6v4ltq26g7

However, this has made my build fail https://ci.codesandbox.io/status/Sage/carbon/pr/2764/builds/21874

yarn run v1.21.1
$ node dist/index.js
+ git clone https://github.com/Sage/carbon.git .
Cloning into '.'...
+ git fetch --force origin pull/2764/head:remotes/origin/pull/2764
fatal: unable to access 'https://github.com/Sage/carbon.git/': The requested URL returned error: 504
{ Error: Process rejected with status code 128
    at ChildProcess.<anonymous> (/app/dist/utils/exec.js:18:27)
    at ChildProcess.emit (events.js:198:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12) code: 128 }
error Command failed with exit code 128.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

There is no way to re-trigger this build, it would be great to be able to do this from the UI.

I'm happy to help with this if there is a way for me to contribute?

In particular, I need an API to restart the build.

https://ci.codesandbox.io/status/un-ts/domiso/pr/37/builds/449609

I haven to change to use yarn v1 for CodeSanbox CI

https://ci.codesandbox.io/status/un-ts/domiso/pr/37/builds/449610

I would like to raise a potential race condition or a rate-limiting issue with CI as well as a frustration point.

On mui-org, we frequently experience failing builds with the following: EACCES: permission denied, for instance: https://ci.codesandbox.io/status/mui-org/material-ui-x/pr/890/builds/95536. This seems to be correlated to an increase a build per minute. This happens for us systematically when dependabot opens a bunch of pull requests. The problem is made worse by #11.

Seems like codesandbox is still on 10.23 (EOL end of this month).

I'm trying to do a gradual migration to 12.x and it won't even install even though I have a dedicated install command that runs yarn install --ignore-engines.

This indicates that you don't use the yarn version we checked into our repository (yarn install:codesandbox is working locally with node 10.23).

Failure: https://ci.codesandbox.io/status/mui-org/material-ui/pr/25306/builds/108812
Changes: mui/material-ui#25306

See build: https://ci.codesandbox.io/status/apollographql/apollo-server/pr/5999/builds/206909

We have a pretty large list of packages, and only one that needs to be excluded (it's private / unpublished). I tried to use the glob pattern packages/!(apollo-server-integration-testsuite) to ignore it, but it interprets the string literally and results in the error:
Error: Can't find package.json at /tmp/16f8ef8e/packages/!(apollo-server-integration-testsuite)/package.json

The docs/example does say globs are supported:

// Globs are supported.
"packages": ["packages/react", "packages/react-dom"],

In https://github.com/mui/mui-x there's a dependency in package.json which is a git repo. In turns out that if a git repo has its history rewritten, e.g. by deleting a commit, Yarn will try to do a merge commit if it already has the repo cached and CodeSandbox CI will fail because it doesn't have the user and email to write the commit. Cleaning the cache before yarn install solves the problem locally but is there a way to do this inside CodeSandbox CI?

I have this build that I have used successfully - all of the packages were available and installable. However, this one became unavailable suddenly - it's returning "Not Found" error.