- 03 6月, 2019 1 次提交
-
-
由 Gurwinder S 提交于
-
- 01 6月, 2019 3 次提交
-
-
由 Kitson Kelly 提交于
-
由 Yoshiya Hinosawa 提交于
-
由 Kurt Mackey 提交于
-
- 31 5月, 2019 4 次提交
-
-
由 Andy Hayden 提交于
Move every test to a method on DenoTestCase. test.py is a single TestSuite of every TestCase. Add a Spawn context manager for http_server, this is explicitly used where it's needed. Each python test file can now be run independently without needing to manually run http_server. Add --help and consistent flags using argparse for each python test, including --failfast. Use ColorTextTestRunner so that '... ok' is green.
-
由 Bert Belder 提交于
-
由 Christian Moritz 提交于
-
由 Christian Moritz 提交于
-
- 30 5月, 2019 2 次提交
- 29 5月, 2019 3 次提交
-
-
由 Ryan Dahl 提交于
* Compiler no longer has its own Tokio runtime. Compiler handles one message and then exits. * Uses the simpler ts.CompilerHost interface instead of ts.LanguageServiceHost. * avoids recompiling the same module by introducing a hacky but simple `hashset<string>` that stores the module names that have been already compiled. * Removes the CompilerConfig op. * Removes a lot of the mocking stuff in compiler.ts like `this._ts`. It is not useful as we don't even have tests. * Turns off checkJs because it causes fmt_test to die with OOM.
-
由 Ryan Dahl 提交于
This is to ensure a more fair test. Also we were already downloading from the internet since we changed the URL to use std@v0.5.0. This change exposes an OOM bug, which is then fixed in the upcoming compiler refactor by changing checkJs compiler option to false.
-
由 Ryan Dahl 提交于
op_fetch_module_meta_data is an op that is used by the TypeScript compiler. TypeScript requires this op to be sync. However the implementation of the op does things on the event loop (like fetching HTTP resources). In certain situations this can lead to deadlocks. The runtime's thread pool can be filled with ops waiting on the result of op_fetch_module_meta_data. The runtime has a maximum number of threads it can use (the number of logical CPUs on the system). This patch changes tokio_util::block_on to launch a new Tokio runtime for evaluating the future, thus bipassing the max-thread problem. This is only an issue in op_fetch_module_meta_data. Other synchronous ops are truly synchornous, not interacting with the event loop. TODO comments are added to direct future development.
-
- 28 5月, 2019 1 次提交
-
-
由 Ryan Dahl 提交于
-
- 27 5月, 2019 2 次提交
-
-
由 Bartek Iwańczuk 提交于
-
由 Adam Conrad 提交于
-
- 26 5月, 2019 1 次提交
-
-
由 Bartek Iwańczuk 提交于
-
- 25 5月, 2019 1 次提交
-
-
由 Andy Hayden 提交于
-
- 24 5月, 2019 6 次提交
- 23 5月, 2019 2 次提交
-
-
由 champ 提交于
-
由 Bert Belder 提交于
This reverts commit 72197878.
-
- 22 5月, 2019 1 次提交
-
-
由 Bartek Iwańczuk 提交于
-
- 21 5月, 2019 4 次提交
- 18 5月, 2019 3 次提交
-
-
由 Bartek Iwańczuk 提交于
-
由 chiefbiiko 提交于
-
由 Bartek Iwańczuk 提交于
-
- 17 5月, 2019 6 次提交
-
-
由 Stephan Renatus 提交于
Signed-off-by: NStephan Renatus <srenatus@chef.io>
-
由 JaePil Jung 提交于
-
由 Bert Belder 提交于
-
由 Bert Belder 提交于
-
由 Bert Belder 提交于
-
由 Bert Belder 提交于
-