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

Revert "refactor: don't expose Deno[Deno.internal].core namespace" #18881

Merged
merged 3 commits into from
Apr 27, 2023

Conversation

bartlomieju
Copy link
Member

Also conditionally disabled one test if there's not enough space on device.

Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

// NOTE(bartlomieju): writing a 0.5Gb file might be too much for CI,
// so skip running if writing fails.
return;
}
Copy link
Member

@dsherret dsherret Apr 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this should be a separate PR in case we revert the revert? (Not a big deal)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather get it in here, instead of waiting for another PR to pass CI

Deno.writeFileSync(filePath, bytes);
try {
Deno.writeFileSync(filePath, bytes);
} catch (e) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have a way to check the specific error instead of returning on all errors?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's OS specific so I'm not sure what will the error be on other OSes.

@bartlomieju bartlomieju merged commit 683dbd7 into denoland:main Apr 27, 2023
10 checks passed
@bartlomieju bartlomieju deleted the revert_core branch April 27, 2023 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants