Age | Commit message (Collapse) | Author |
|
Having `|| true` means that the job always executes with a success code,
even when it really fails. Credit to Bartek for spotting this possible
mistake.
Towards #22257
|
|
Our `itest` macros will occasionally run away and fail ~2 hours later.
This aborts all testcases after 2 minutes.
|
|
Bumped versions for 1.41.0
Co-authored-by: bartlomieju <bartlomieju@users.noreply.github.com>
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
|
|
Currently useful for `deno test` and internal tests, but could
potentially be exposed at a later time as a `Deno` API.
|
|
|
|
`deno compile` was ignoring configuration file and thus not applying
`compilerOptions` to influence the way files were emitted.
|
|
Updates dependent crates which includes an investigation fix by @irbull
in Deno's LSP when linting code. Huge thanks to Ian for tracking down
this issue.
Also includes Divy's deno_graph executor change, which reduces memory
usage when loading jsr specifiers and makes them faster.
Co-authored-by: irbull <irbull@users.noreply.github.com>
Co-authored-by: littledivy <littledivy@users.noreply.github.com>
|
|
When using a prefix or suffix containing an invalid filename character,
it's not entirely clear where the errors come from. We make these errors
more consistent across platforms.
In addition, all permission prompts for tempfile and tempdir were
printing the same API name.
We also take the opportunity to make the tempfile random space larger by
2x (using a base32-encoded u64 rather than a hex-encoded u32).
|
|
|
|
|
|
Co-authored-by: Divy Srivastava <dj.srivastava23@gmail.com>
|
|
|
|
Supersedes #22501 and also fixes that issue.
|
|
|
|
denort are release binaries for `deno compile`. Stripping debuginfo and
symbols lets us ship a smaller binary. The same source can be run under
`deno` CLI to get the proper Rust backtrace.
stripped denort is 55MB on macOS.
|
|
Closes #22473
|
|
|
|
(#22507)
…rios (#21910)"
This reverts commit bd1358efab8ba7339a8e70034315fa7da840292e.
This change caused https://github.com/denoland/deno/issues/22496 and
https://github.com/denoland/deno/issues/22445
|
|
Closes #18665
Closes #20213
|
|
|
|
I think it was occassionally reading the diagnostics from the previous
cache command rather than the config update.
Closes #22481
|
|
|
|
|
|
Fixes https://github.com/denoland/deno/issues/22299
|
|
|
|
|
|
1. Renames zap/fast-check to instead be a `no-slow-types` lint rule.
1. This lint rule is automatically run when doing `deno lint` for
packages (deno.json files with a name, version, and exports field)
1. This lint rules still occurs on publish. It can be skipped by running
with `--no-slow-types`
|
|
As discussed with @mmastrac.
---------
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
Renames `op_fs_fstat_{sync/async}` to `op_fs_file_stat_{async/sync}` in
preparation of the upcoming removal of `Deno.fstat()` in v2.
|
|
|
|
As part of ongoing efforts to remove `rid` properties from the public
API. Note: this property is undocumented.
|
|
If we strip out unprintable chars, we don't see the full filename being
requested by permission prompts. Instead, we highlight and escape them
to make them visible.
|
|
Towards #22197
|
|
fix parseArgs() not working due to missing import of node:process
this commit fixes issue #22363
|
|
Closes #22229.
---------
Signed-off-by: Asher Gomez <ashersaupingomez@gmail.com>
|
|
As part of ongoing works to make `rid` private.
---------
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
This change deprecates
`Deno.CreateHttpClientOptions.{certChain,privateKey}` in favour of
`Deno.CreateHttpClientOptions.{cert,key}`.
Closes #22278
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
Migrations:
- Use the new SnapshotSerializer for TSC/compiler snapshots
|
|
`ModuleLoader` was doing too much duplicate work.
|
|
The format of the sanitizers will change a little bit:
- If multiple async ops leak and traces are on, we repeat the async op
header once per stack trace.
- All leaks are aggregated under a "Leaks detected:" banner as the new
timers are eventually going to be added, and these are neither ops nor
resources.
- `1 async op` is now `An async op`
- If ops and resources leak, we show both (rather than op leaks masking
resources)
Follow-on to https://github.com/denoland/deno/pull/22226
|
|
Moving tests around so that we can make #22413 smaller
|
|
Signed-off-by: Igor Zinkovsky <igor@deno.com>
|
|
Splitting the sleep and interval ops allows us to detect an interval
timer. We also remove the use of the `op_async_void_deferred` call.
A future PR will be able to split the op sanitizer messages for timers
and intervals.
|
|
deno fmt sometimes had stuff like:
```
NODE: Evaluation
```
...in the output.
|
|
As discussed with @mmastrac. I'll move `tools/wpt` to `tests/wpt` in a
follow-up PR.
---------
Co-authored-by: Matt Mastracci <matthew@mastracci.com>
|
|
This changes the lockfile to not store JSR specifiers in the "remote"
section. Instead a single JSR integrity is stored per package in the
lockfile, which is a hash of the version's `x.x.x_meta.json` file, which
contains hashes for every file in the package. The hashes in this file
are then compared against when loading.
Additionally, when using `{ "vendor": true }` in a deno.json, the files
can be modified without causing lockfile errors—the checksum is only
checked when copying into the vendor folder and not afterwards
(eventually we should add this behaviour for non-jsr specifiers as
well). As part of this change, the `vendor` folder creation is not
always automatic in the LSP and running an explicit cache command is
necessary. The code required to track checksums in the LSP would have
been too complex for this PR, so that all goes through deno_graph now.
The vendoring is still automatic when running from the CLI.
|
|
Signed-off-by: Divy Srivastava <dj.srivastava23@gmail.com>
|
|
This is the release commit being forwarded back to main for 1.40.5
Co-authored-by: Divy Srivastava <dj.srivastava23@gmail.com>
|
|
Closes https://github.com/denoland/deno/issues/22315
```
~> DENO_FUTURE=1 target/debug/deno
> globalThis.window
undefined
```
|
|
|