WhereIsAI/github-issue-similarity huggingface dataset:
Issue 1:
ISSUE TYPE

Bug Report

COMPONENT NAME

uri

ANSIBLE VERSION

ansible 2.3.0.0
config file = /ansible/ansible.cfg
configured module search path = Default w/o overrides
python version = 2.7.5 (default, Aug 2 2016, 04:20:16) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)]

CONFIGURATION

N/A

OS / ENVIRONMENT

N/A

SUMMARY

Ansible 2.3 just landed in RHEL7, so I just spent the last couple hours chasing down an obscure bug in our infrastructure. Ultimately, I have isolated this issue to the change in #20427. On it's face, this is a good idea, but the no_log attribute effects everything returned by the module, including the content. It just happened to be that the password appeared in one of our files, so it was replaced with stars and broke the file.

STEPS TO REPRODUCE

- uri:
url: '{{ someFileThatContainsPasswordToDownload }}'
user: '{{ user }}'
password: '{{ password }}'
return_content: yes
register: result

EXPECTED RESULTS

The value of result.content should match the original file on the server.

ACTUAL RESULTS

All appearances of {{ password }} in {{ someFileThatContainsPasswordToDownload }} are replaced with *, corrupting the value of result.content.

Issue 2:
ISSUE TYPE

Bug Report

COMPONENT NAME

core

ANSIBLE VERSION

ansible 2.4.0

config file = /home/conductor/playbooks/ansible.cfg

configured module search path = Default w/o overrides

python version = 2.7.12 (default, Jul 1 2016, 15:12:24) [GCC 5.4.0 20160609]

CONFIGURATION

Not relevant

OS / ENVIRONMENT

Ubuntu 16.04 / Python 2.7

SUMMARY

Ansible display "when statements should not include jinja2 templating" warning while I'm not using jinja2 templating in the when statement.

The problem come from the face the variable passed in the when statement references an other variable:

in defaults/main.yml

my_role_var: "{{ my_host_var }}"

in tasks/main.yml

- copy: …
when: my_role_var

[WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ my_host_var }}

test.zip

STEPS TO REPRODUCE

Uncompress the attached project.

Update hosts file and playbook to specify a reachable host.

run it using "ansible-playbook -i hosts playbook.yml"

EXPECTED RESULTS

No warning, or an explanation about what to do about it.

ACTUAL RESULTS

ansible-playbook -i hosts playbook.yml

PLAY [*]

TASK [Gathering Facts]

ok: [test]

TASK [simple : debug]

[WARNING]: when statements should not include jinja2 templating delimiters such as {{ }} or {% %}. Found: {{ hello }}

ok: [test] => {

"changed": false,

"msg": "Hello"

}

PLAY RECAP

test : ok=2 changed=0 unreachable=0 failed=0
Issue 1:
Obviously I could export the app to an executable every time I make a change, then use Windows settings to force that executable to use the GPU I want to be used, but that would be extremely tedious. Is there some way through Electron I can force my dedicated GPU to be used rather than the CPU integrated graphics?

Issue 2:
Electron version: 1.7.3

Operating system: macOS 10.12.5

Problem

My app uses the discrete GPU constantly which has a negative impact on battery life (sindresorhus/caprine#238). I would like to be able to force my app to only use the integrated GPU if available. Chrome has a flag for this: --force_discrete_gpu=0. This is different from the app.disableHardwareAcceleration() method as I don't want to disable hardware acceleration, just use the more power efficient GPU.

Solution

Support it with app.commandLine.appendSwitch() or as a separate method app.forceIntegratedGPU().
Issue 1:
tsc --allowJs moment-with-locales.min.js

on min/moment-with-locales.min.js

from https://github.com/moment/moment/archive/2.11.1.zip

gives

node_modules/typescript/lib/tsc.js:32405

if (moduleName.indexOf("!") != -1) {

^

TypeError: Cannot read property 'indexOf' of undefined

at classicNameResolver (node_modules/typescript/lib/tsc.js:32405:23)

at resolveModuleName (node_modules/typescript/lib/tsc.js:32308:28)

at resolveModuleNamesWorker (node_modules/typescript/lib/tsc.js:32573:40)

at processImportedModules (node_modules/typescript/lib/tsc.js:33156:35)

at findSourceFile (node_modules/typescript/lib/tsc.js:33132:17)

at processSourceFile node_modules/typescript/lib/tsc.js:33059:27)

at processRootFile (node_modules/typescript/lib/tsc.js:32982:13)

at node_modules/typescript/lib/tsc.js:32594:60

at Object.forEach (node_modules/typescript/lib/tsc.js:98:30)

at Object.createProgram (node_modules/typescript/lib/tsc.js:32594:16)

Issue 2:
If you include the file http://momentjs.com/downloads/moment.js in a tsc --allowJs compilation, a TypeError is thrown:

TypeError: Cannot call method 'indexOf' of undefined
at classicNameResolver (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32405:24)
at resolveModuleName (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32308:28)
at resolveModuleNamesWorker (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32573:40)
at processImportedModules (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:33156:35)
at findSourceFile (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:33132:17)
at processSourceFile (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:33059:27)
at processRootFile (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32982:13)
at /home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32594:60
at Object.forEach (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:98:30)
at Object.createProgram (/home/jeffrey/TypeScript-1.8.0-beta/lib/tsc.js:32594:16)

This is caused by the following JS source line:

require('./locale/' + name);

The function isRequireCall in utilities.ts returns true on this expression, but there are two places that assume that if isRequireCall returns true, then the argument must be a string literal.
Issue 1:
The following code compiles with no warning or error:

enum x {}

enum y { x }

fn main() {}

However if the positions of the enums are reversed then the compile fails with a (I think bogus) error message:

enum y { x }

enum x {}

fn main() {}

The error message is:

test.rs:5:0: 5:9 error: Duplicate definition of value x
test.rs:5 enum x {}
^~~~~~~~~
test.rs:3:9: 3:10 note: First definition of value x here:
test.rs:3 enum y { x }
^
error: aborting due to previous error

Issue 2:
Affects all attempts to build the compiler from revision 98d4d49 (with snapshot 9e4e524) forward. Last "good" release was 87dce0c.

Build output:

CFG_LLVM_LINKAGE_FILE=/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/rt/llvmdeps.rs LD_LIBRARY_PATH=/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/stage1/lib:$LD_LIBRARY_PATH x86_64-unknown-freebsd/stage1/bin/rustc --cfg stage1 -O --cfg rtopt --cfg debug -C prefer-dynamic --target=x86_64-unknown-freebsd -D warnings -L "x86_64-unknown-freebsd/rt" -L "/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/llvm/Release+Asserts/lib" -L "" --out-dir x86_64-unknown-freebsd/stage1/lib/rustlib/x86_64-unknown-freebsd/lib -C extra-filename=-4e7c5e5c /home/aidan/rust/rust2/rust/src/libcore/lib.rs
/home/aidan/rust/rust2/rust/mk/target.mk:165: recipe for target 'x86_64-unknown-freebsd/stage1/lib/rustlib/x86_64-unknown-freebsd/lib/stamp.core' failed
gmake: *** [x86_64-unknown-freebsd/stage1/lib/rustlib/x86_64-unknown-freebsd/lib/stamp.core] Segmentation fault: 11

When compiling with this command line:

RUST_LOG=debug CFG_LLVM_LINKAGE_FILE=/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/rt/llvmdeps.rs LD_LIBRARY_PATH=/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/stage1/lib:$LD_LIBRARY_PATH x86_64-unknown-freebsd/stage1/bin/rustc --cfg stage1 -O --cfg rtopt --cfg debug -C prefer-dynamic --target=x86_64-unknown-freebsd -D warnings -L "x86_64-unknown-freebsd/rt" -L "/usr/home/aidan/rust/rust2/rust/x86_64-unknown-freebsd/llvm/Release+Asserts/lib" -L "" --out-dir x86_64-unknown-freebsd/stage1/lib/rustlib/x86_64-unknown-freebsd/lib -C extra-filename=-4e7c5e5c -Z time-passes /home/aidan/rust/rust2/rust/src/libcore/lib.rs

Yields this debug log tail

Ran configure as:

./configure --disable-jemalloc --prefix=/pkg/rust2 --local-rust-root=/pkg/rust2 --libdir=/pkg/rust2/lib --enable-debug

uname -a output (not that it should matter much):

FreeBSD freebsd 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r+2315ea3: Fri Dec 20 12:48:50 PST 2013 root@build.ixsystems.com:/tank/home/jkh/checkout/freenas/os-base/amd64/tank/home/jkh/checkout/freenas/FreeBSD/src/sys/FREENAS.amd64 amd64

(Note that I've updated the base FreeBSD installation to run w/ clang instead of gcc.)

Builds and runs fine when jemalloc is enabled, but if we assume the system allocator works, it would mean there's a bug somewhere in rustc's (or llvm's) code generation: some investigation showed the segfault occurred due to memory corruption in the AST. I suspect this problem will be reproducable with FreeBSD 10.
Issue 1:
VSCode Version:1.0

OS Version:

Steps to Reproduce:

中文版安装

所有命令都变中文了。 不能使用英文命令。除非切换成英文版本。

希望能中英文命令都兼容

Issue 2:
VSCode Version:

バージョン 0.10.12-insider

コミット ef2a1fc

日付 2016-03-21T11:33:38.240Z

シェル 0.35.6

レンダラー 45.0.2454.85

ノード 4.1.1

Even Japanese people, typing Japanese words are very painful and time-consuming because of IME composition problems.

We expects that the commands are all in English.

For example, if I want to execute git pull, I will type "git pull"; not "git プル".

Hope you can understand our situation.
Issue 1:
Environment

Windows build number: Windows 10.0.18363.476.
PowerToys version: 0.14.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

File-Open

Open Notepad.exe (or another application that uses a File-Open dialog).

Use Shift+Drag to move Notepad.exe into a zone.

Select File > Open.

File-Save

Open Notepad.exe.

Use Shift+Drag to move Notepad.exe into a zone.

Select File > Save As....

Expected behavior

File-Open

Notepad's File-Open dialog should be the same size as the previous time it was opened.

File-Save

Notepad's File-Save dialog should be rendered correctly (so that the filenames are visible).

Actual behavior

File-Open

Notepad's File-Open dialog is the same size as the Notepad window and its display seems to have been prevented from rendering.

File-Save

Notepad's File-Save dialog's display seems to have been prevented from rendering.

Screenshots

File-Open

File-Save

Issue 2:
📝 Provide a description of the new feature

Integration for Darkmode based on sunrise/sunset times from your geo/localization.

Like the Windows-Auto-Night-Mode app:

https://github.com/Armin2208/Windows-Auto-Night-Mode

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Issue 1:
It appears that our event stream is putting pressure on etcd and leading to crashes. Investigate event + etcd memory performance

Issue 2:
Is this a request for help? (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): sha1sum

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Kubernetes version (use kubectl version): 1.5

What happened: Using the manual upgrade procedures to debug #37257 and found that upgrade.sh crashed.

What you expected to happen: The shell script to not crash.

How to reproduce it (as minimally and precisely as possible): Follow manual upgrade procedures on a system that doesn't have sha1sum in the path (e.g. Mac).
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Drawer should be "at the same elevation as the content or background.". Only a temporary drawer should, as discribed, "opens temporarily above all other content until a section is selected.".

Current Behavior

The Drawer blocks all other content regardless of varient property.

Steps to Reproduce (for bugs)

Code Sandbox

Create a React.JS app.

Import Drawer from material-ui/Drawer.

Add it to a component and set the varient to either persistent or permenant.

Load the page.

Context

I'm trying to make sure that this drawer stays open to be used as general navigation in a project. The example on the website for material-ui with react has a lot of code to figure out, I'm trying to slim it down to the bare necceseties (which I think is this?).

Your Environment

Tech
Version

Material-UI
1.0.0-beta.31

React
16.0.36

browser
Chromium 64.0.3282.119

Issue 2:
For example, using Chrome/Safari, open the demo page of any component like "AppBar" or "Menu", click on any button or any menu item, the ripple effect will appear twice.

Tested on Chrome/Safari, IOS 9.1, iPhone 6.
Issue 1:
Bug report

Bug summary

Pressing "enter" or "numpad enter" within a TextBox has no effect when using the WxAgg backend

Code for reproduction

# Based on https://matplotlib.org/3.1.1/gallery/widgets/textbox.html

import numpy as np
import matplotlib.pyplot as plt
from matplotlib.widgets import TextBox
import matplotlib as mpl

#mpl.use('TkAgg') # Enter and numpad enter work fine
#mpl.use('Qt5Agg') # Enter and numpad enter work fine
mpl.use('WxAgg') # Neither enter nor numpad enter work

fig, ax = plt.subplots()
plt.subplots_adjust(bottom=0.2)
t = np.arange(-2.0, 2.0, 0.001)
s = t ** 2
initial_text = "t ** 2"
l, = plt.plot(t, s, lw=2)

def submit(text):
print(text)
plt.draw()

axbox = plt.axes([0.1, 0.05, 0.8, 0.075])
text_box = TextBox(axbox, 'Evaluate', initial=initial_text)
text_box.on_submit(submit)

plt.show()

Actual outcome

With the TkAgg and Qt5Agg backends, pressing "enter" or "numpad enter" within a TextBox work as expected (you see the printed value of the box text in the console).

With the WxAgg backend you can enter/delete characters but the enter keys have no effect.

Expected outcome

The enter keys should work equally well in all of these backends.

Note: Clicking into and then out of the TextBox still works regardless of the backend chosen

Matplotlib version

Operating system: Windows 10

Matplotlib version: 3.1.1

Matplotlib backend (print(matplotlib.get_backend())): See above - problem is with WxAgg

Python version: 3.7.4

Jupyter version (if applicable): n/a

Other libraries: WxPython 4.0.6

Installed via pip.

Issue 2:
Bug summary

On Windows, with the wx backend, arrow keys are not reported

Code for reproduction

Use the keypress example and insert:

from matplotlib import use
use('wx')

Actual outcome

On Windows, when pressing arrow keys, no keys are printed to the console.

On macOS it works as expected.

Matplotlib version

Matplotlib 2.0.0, Python 2.7, Windows 10

Anaconda
Issue 1:
class B { }
class C extends B { }
console.log(B.isPrototypeOf(C))

Expected: true

Actual: false

Issue 2:
The following code:

var i = 0, j = 0;

class Base {
get instanceAccessor() { return ++i; }
static get staticAccessor() { return ++j; }
toString = () => 'instance: ' + this.instanceAccessor + ' static: ' + Base.staticAccessor;
}

class Derived extends Base {
toString = () => 'instance: ' + this.instanceAccessor + ' static: ' + Derived.staticAccessor;
}

console.log('Base:\n%s\n%s\n%s', new Base(), new Base(), new Base());
console.log('Derived:\n%s\n%s\n%s', new Derived(), new Derived(), new Derived());

generates the following output (with the v1.3 compiler):

Base:
instance: 1 static: 2
instance: 2 static: 3
instance: 3 static: 4
Derived:
instance: 4 static: 1
instance: 5 static: 1
instance: 6 static: 1

Clearly Derived.staticAccessor is no longer an accessor, but a 'snapshot' of the value of Base.staticAccessor when the Derived constructor function called __extends.

Just wondering if this is the expected/correct behaviour?

PS. I haven't run into this problem 'in the wild' as I rarely use classes or accessors, but merely came across a rant/blog post about another compile-to-JS language doing something similar, and was curious how TypeScript handled it.
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version:2.6.2

Operating System version: mac 10.13.6

Java version: 1.8

Steps to reproduce this issue

in this example https://github.com/dubbo/dubbo-samples/tree/master/dubbo-samples-docker

docker run -t --net=host dubbo-sample-docker:latest

server not start

[DUBBO] Could not get local host ip address, will use 127.0.0.1 instead., dubbo version: 2.6.2, current host: 127.0.0.1

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

support docker host network

Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!
ERROR 1 --- [ main] com.alibaba.dubbo.common.utils.NetUtils : [DUBBO] Could not get local host ip address, will use 127.0.0.1 instead., dubbo version: 2.6.2, current host: 127.0.0.1

Issue 2:
目前我有一个疑惑，dubbo的服务消费者跟提供者都用容器去包装，然后发布在容器云里面。一般来说不应该去修改容器镜像内的东西，但是服务的发现会用网卡ip信息去实现。网上有说要改host文件或者该dubbo的配置文件，但都不太现实，如果是基于弹性伸缩的情况下，每次都得去改配置，而且注册的都是用宿主机的ip，很显然是不正确的。有没有办法通过DNS做域名映射实现服务注册以及服务消费呢？或者dubbo团队能否提供一些镜像案例给我们参考参考。
Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Shall we remove react & react-dom from peerDependencies? Since using preact (without react) is already an option.

Current Behavior

will warning about:

npm WARN next@3.0.1-beta.18 requires a peer of react@^15.5.4 but none was installed.
npm WARN next@3.0.1-beta.18 requires a peer of react-dom@^15.5.4 but none was installed.

Steps to Reproduce

npm install next@beta preact preact-compat

Issue 2:
I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

Throwing undefined in the renderToHTML shouldn't halt the request.

Current Behavior

Throwing undefined halt the request.

Steps to Reproduce (for bugs)

Throw undefined in a .getInitialProps() method.

Context

To be more specific an error is raised from this line:

https://github.com/zeit/next.js/blob/2ec397b3564d5dbca933e8def9cd0801ebd3a2b5/server/index.js#L321

unhandledRejection reason TypeError: Cannot read property 'code' of undefined

at Server._callee18$ (/app/node_modules/next/dist/server/index.js:943:37)

Yes, throwing undefined is supported by JavaScript. It was a mistake on my end. I don't throw undefined on purpose 😁 .

Your Environment

Tech
Version

next
v4.0.2

node
v8.5.0

OS
Linux

browser
Chrome
Issue 1:
[x ] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

I basically expect to be able to have a "placeholder" in the input if the value is empty. I've accomplished this by setting the floatingLabelText dynamically. I also want the input to honor the width of said placeholder.

Current Behavior

The input doesn't honor the width of the label for the floating text because it's set to position:absolute.

Steps to Reproduce (for bugs)

https://codesandbox.io/s/q8n5k5r319

Context

How does one accomplish this w/ MUI? I don't see how this is possible? Am I going about this the wrong way?

Your Environment

Tech
Version

Material-UI
0.20.0

React
16.0.0

browser
Chrome

etc

Issue 2:
In my code I added

import {DatePicker} from 'material-ui';

Then i've got error

ReferenceError: document is not defined

at [object Object].componentWillMount (~/node_modules/material-ui/lib/overlay.js:64:34)

I also change my import to

const DatePicker = require('material-ui/lib/date-picker/date-picker');

Still no luck
Issue 1:
Use case - Routing settings are made to not use a machine , but later we need to use that machine.

We should be able to delete settings related to routing.

Issue 2:
If you enable a setting on a index you cannot remove it.

For example if you want to disable shard relocation in cluster and enable it for one index you use:

curl -XPUT http://localhost:9200/articles/_settings -d '{"index.routing.allocation.disable_allocation": false}'
curl -XPUT http://localhost:9200/_cluster/settings -d '{"transient":{"cluster.routing.allocation.disable_allocation": true}}'

Then if you want to use the cluster setting on the index there is no way to delete the defined value and you need to manually maintain it.

A good enhancement will be to have the ability to use:

curl -XDELETE http://localhost:9200/articles/_settings -d '{"index.routing.allocation.disable_allocation"}'

or

curl -XPUT http://localhost:9200/articles/_settings -d '{"index.routing.allocation.disable_allocation":default}'
Issue 1:
Reproducing code example:

import numpy as np

a = np.array([-9.93686340e+02, -9.85949280e+02, -9.67635925e+02, -9.39872864e+02,
-8.98984009e+02, -8.41368530e+02, -7.81853699e+02, -6.92064392e+02,
-6.12045349e+02, -5.30710449e+02, -4.54482269e+02, -3.71461731e+02,
-3.14179626e+02, -2.76059692e+02, -2.41759018e+02, -2.20870255e+02,
-1.92301758e+02, -1.66814026e+02, -1.44157349e+02, -1.30507690e+02,
-1.12051003e+02, -9.58245697e+01, -8.61438751e+01, -7.31186905e+01,
-6.15607414e+01, -4.49081726e+01, -3.38174362e+01, -2.26543159e+01,
-1.42377014e+01, -8.23967838e+00, -4.27592516e+00, -1.91338563e+00,
-6.95205748e-01, -1.86089307e-01, -0.00000000e+00,
-9.93686328e+02, -7.39944519e+02])

print(np.argsort(a))

Error message:

[ 0 35 1 2 3 4 5 6 36 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
22 23 24 25 26 27 28 29 30 31 32 33 34]

The result should be:

[ 0 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
22 24 25 26 27 28 29 30 31 32 1 23]

Note that a[:-2] is ascending (print(np.argsort(a[:-2]))):

[ 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
24 25 26 27 28 29 30 31 32 33 34]

The last two elements cause the bug above.

NumPy/Python version information:

1.19.1 3.8.5 | packaged by conda-forge | (default, Jul 24 2020, 01:25:15)
[GCC 7.5.0]

Issue 2:
Proposed new feature or change:

Requirement

Today, show_config generated via meson does not include compiler flags

Changes

Find a way to parse the compiler flags provided either via env vars like CFLAGS or via config_settings and include in show_config

Note: Additionally this needs to be ported to SciPy
Issue 1:
source is as simple this

import { serve } from 'https://deno.land/std@0.51.0/http/server.ts'
const s = serve({ port: 8000 })
console.log('servce on http://localhost:8000')
for await (const req of s) {
req.respond({ body: "hhhhhh" })
}

after with @deno bundle --unstable .\main.ts main.js

try to run with @deno run --unstable --allow-net main.js

get this error

error: Uncaught SyntaxError: Unexpected reserved word
for await (const req of s) {

Issue 2:
Steps to reproduce

Create server.js with the following content:

import { serve } from "https://deno.land/std@v0.35.0/http/server.ts";
const s = serve({ port: 8000 });
console.log("http://localhost:8000/");
for await (const req of s) {
req.respond({ body: "Hello World\n" });
}

Run deno bundle server.js out.js

Run deno out.js

Expected result

The code runs

Actual result

error: Uncaught SyntaxError: Unexpected reserved word
► file:///path/to/out.js:113:17

113 for await (const req of s) {
~~~~~

Notes

Adding await console.log("test"); or any other await statement is detected by the bundler and allows the for-await block to work properly. (See #4206)

deno 0.35.0
v8 8.1.310
typescript 3.8.2