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

fix: [jsx] remote jsx/tsx files were compiled as js/ts #3125

Merged
merged 8 commits into from
Oct 16, 2019

Conversation

keroxp
Copy link
Contributor

@keroxp keroxp commented Oct 14, 2019

  • At resolving remote files, extension are ignored and .jsx | .tsx files were compiled as .js and .ts, resulting throw compilation error.
  • To resolve correctly, remote files should be checked by content-type and extension together.

@keroxp
Copy link
Contributor Author

keroxp commented Oct 14, 2019

Why benchmark? @ry Would you re-run actions?

@bartlomieju
Copy link
Member

@keroxp to rerun benchmarks just push empty commit:

git commit --allow-empty -m "reset CI"

cli/tests/048_remote_jsx.ts Outdated Show resolved Hide resolved
Some("application/x-typescript")
),
msg::MediaType::JSX
);
Copy link
Member

Choose a reason for hiding this comment

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

👍

- Adding jsx imports to 019_media_types.ts crashes 019 and 022
- There may be other bugs
@keroxp
Copy link
Contributor Author

keroxp commented Oct 15, 2019

@ry I can't know how integration tests are failing on ubuntu. There are no hints on CI console, just exiting with code 1. Those tests have passed on my macOS machine. Could someone check it on linux?

@keroxp
Copy link
Contributor Author

keroxp commented Oct 15, 2019

Additionally, cargo test fails on master branch on my macOS (10.15)

test wasm ... ok
test fmt_test ... FAILED
test js_unit_tests ... FAILED

failures:

---- fmt_test stdout ----
tools/http_server.py starting...
tools/http_server.py ready
target_dir /Users/keroxp/src/deno/target/debug
target_dir /Users/keroxp/src/deno/target/debug
thread 'fmt_test' panicked at 'tools/fmt_test.py executed with failing error code
fmt (__main__.TestFmt) ... ERROR

======================================================================
ERROR: fmt (__main__.TestFmt)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "tools/fmt_test.py", line 31, in test_fmt
    quiet=True)
  File "/Users/keroxp/src/deno/tools/util.py", line 99, in run_output
    sys.exit(retcode)
SystemExit: -4

----------------------------------------------------------------------
Ran 1 test in 24.631s

FAILED (errors=1)
', cli/tests/util/mod.rs:34:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

---- js_unit_tests stdout ----
thread 'js_unit_tests' panicked at 'called `Result::unwrap()` on an `Err` value: "PoisonError { inner: .. }"', src/libcore/result.rs:999:5


failures:
    fmt_test
    js_unit_tests

test result: FAILED. 92 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out

@bartlomieju
Copy link
Member

@keroxp it's caused by #3122 there's already PR going to fix it

@ry
Copy link
Member

ry commented Oct 15, 2019

@keroxp I've merged the v8 upgrade which should alleviate the failure you were experiencing. I think there is still an issue in this patch though...

Copy link
Member

@ry ry left a comment

Choose a reason for hiding this comment

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

LGTM - thanks for the good tests!

@ry ry merged commit c1b302d into denoland:master Oct 16, 2019
mmastrac added a commit that referenced this pull request Jul 31, 2023
Includes a lightly-modified version of hyper-util's `TokioIo` utility. 

Hyper changes:

v1.0.0-rc.4 (2023-07-10)
Bug Fixes

    http1:
http1 server graceful shutdown fix (#3261)
([f4b51300](hyperium/hyper@f4b5130))
send error on Incoming body when connection errors (#3256)
([52f19259](hyperium/hyper@52f1925),
closes hyperium/hyper#3253)
properly end chunked bodies when it was known to be empty (#3254)
([fec64cf0](hyperium/hyper@fec64cf),
closes hyperium/hyper#3252)

Features

client: Make clients able to use non-Send executor (#3184)
([d977f209](hyperium/hyper@d977f20),
closes hyperium/hyper#3017)
    rt:
replace IO traits with hyper::rt ones (#3230)
([f9f65b7a](hyperium/hyper@f9f65b7),
closes hyperium/hyper#3110)
add downcast on Sleep trait (#3125)
([d92d3917](hyperium/hyper@d92d391),
closes hyperium/hyper#3027)
service: change Service::call to take &self (#3223)
([d894439e](hyperium/hyper@d894439),
closes hyperium/hyper#3040)

Breaking Changes

Any IO transport type provided must not implement hyper::rt::{Read,
Write} instead of tokio::io traits. You can grab a helper type from
hyper-util to wrap Tokio types, or implement the traits yourself, if
it's a custom type.
([f9f65b7a](hyperium/hyper@f9f65b7))
client::conn::http2 types now use another generic for an Executor. Code
that names Connection needs to include the additional generic parameter.
([d977f209](hyperium/hyper@d977f20))
The Service::call function no longer takes a mutable reference to self.
The FnMut trait bound on the service::util::service_fn function and the
trait bound on the impl for the ServiceFn struct were changed from FnMut
to Fn.
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.

3 participants