Status Update
Comments
va...@chromium.org <va...@chromium.org> #2
Fixed by
va...@chromium.org <va...@chromium.org> #3
va...@chromium.org <va...@chromium.org> #4
7.1.1 only included 2 critical Studio fixes in order to release very quickly with minimum testing, so the fix will be included in 7.1.2. Apologies for the inconvenience.
va...@chromium.org <va...@chromium.org> #5
Thanks for the update. Will be waiting for 7.1.2.
va...@chromium.org <va...@chromium.org> #6
Thanks for the info. Where can I find the release notes for 7.1.1? Can't see anything here
va...@chromium.org <va...@chromium.org> #7
va...@chromium.org <va...@chromium.org> #8
steamkar id 573918761
va...@chromium.org <va...@chromium.org> #9
support topup
va...@chromium.org <va...@chromium.org> #10
va...@chromium.org <va...@chromium.org> #11
va...@chromium.org <va...@chromium.org> #12
va...@chromium.org <va...@chromium.org> #13
va...@chromium.org <va...@chromium.org> #14
va...@chromium.org <va...@chromium.org> #15
lx...@google.com <lx...@google.com> #16
va...@chromium.org <va...@chromium.org> #17
va...@google.com <va...@google.com> #18
va...@chromium.org <va...@chromium.org> #19
va...@chromium.org <va...@chromium.org> #20
va...@chromium.org <va...@chromium.org> #21
lx...@google.com <lx...@google.com> #22
lx...@google.com <lx...@google.com> #23
lx...@google.com <lx...@google.com> #24
va...@chromium.org <va...@chromium.org> #25
bu...@essential-inputs.iam.gserviceaccount.com <bu...@essential-inputs.iam.gserviceaccount.com> #26
bu...@essential-inputs.iam.gserviceaccount.com <bu...@essential-inputs.iam.gserviceaccount.com> #27
bu...@essential-inputs.iam.gserviceaccount.com <bu...@essential-inputs.iam.gserviceaccount.com> #28
bu...@essential-inputs.iam.gserviceaccount.com <bu...@essential-inputs.iam.gserviceaccount.com> #29
bu...@essential-inputs.iam.gserviceaccount.com <bu...@essential-inputs.iam.gserviceaccount.com> #30
je...@google.com <je...@google.com> #31
da...@chromium.org <da...@chromium.org> #32
listen [127.0.0.1]:49363: Address in use
channel_setup_fwd_listener_tcpip: cannot listen to port: 49363
Fixing this required enabling/disabling the extension in chrome://extensions. Is there a known issue for this?
va...@google.com <va...@google.com> #33
is...@google.com <is...@google.com> #34
[Monorail blocked-on:
[Monorail blocking:
[Monorail components added to Component Tags custom field.]
wi...@google.com <wi...@google.com> #35
Loading wasm program... «««This is in alpha -- see https://crbug.com/1312115 for KIs»»» done.
Is the "alpha" label still correct? Since we're being opted-in for our daily use, I suspect this warning is out-of-date and should be beta at a minimum?
va...@google.com <va...@google.com> #36
bumping to beta at this point is reasonable, thanks
ap...@google.com <ap...@google.com> #37
Branch: main
commit c22251c9108118e3dbf7435e814882921649f78e
Author: Mike Frysinger <vapier@chromium.org>
Date: Wed Mar 27 10:54:37 2024
wassh: update "alpha" status to "beta"
Bug:
Change-Id: I6fe7c80a7e4ec53a70fa8a128efe1ac98ba76932
Reviewed-on:
Tested-by: kokoro <noreply+kokoro@google.com>
Reviewed-by: Joel Hockey <joelhockey@chromium.org>
M nassh/js/nassh_plugin_wasm.js
st...@google.com <st...@google.com> #38
When the connection is lost (e.g. on closing chromebook) with original client you can hit a key to cause reconnect; but the wasm version does not seem to respond in the same way, meaning you have to manually close the window and open a new one.
ja...@gmail.com <ja...@gmail.com> #39
de...@google.com <de...@google.com> #40
ssh: connect to host xxxxx : Host is unreachable
Loading wasm program... «««This is in beta -- see
ek...@google.com <ek...@google.com> #41
Re:
mi...@google.com <mi...@google.com> #42
I can still not mount an SFTP drive and going via x20 is a pain
ja...@gmail.com <ja...@gmail.com> #43
See attached screenshot.
va...@google.com <va...@google.com> #44
this bug is intended for tracking issues filed independently, it isn't for people to post their specific issues. if something isn't working for you, please file a unique bug with details in it.
an...@google.com <an...@google.com> #45
The SSH tunneling also stops working when this screen hangs. I use this a lot so this is a really big issue for me. As a workaround, I open another terminal and use SSH tunneling again and then quit by typing exit
. This closes the connection correctly and connecting again causes the tunneling to work again.
va...@google.com <va...@google.com> #46
again, this issue is not for reporting new things. it is a tracker bug only. please file dedicated issues as we aren't going to triage anything here.
lu...@gmail.com <lu...@gmail.com> #47
la...@google.com <la...@google.com> #48
Filed
cr...@google.com <cr...@google.com> #49
va...@google.com <va...@google.com> #50
if you have a question, please use the mailing lists. if you have an issue to report, please file a new bug.
cr...@google.com <cr...@google.com> #51
Thanks! I have opened:
Description
for a quick summary of all KI issues, click the "View details" link on the LHS under the "BlockedOn" section.