Typescript error on Generate Site

Describe the bug
I tried to run upptime with almost default setup but it fails generating the site.
Logs
https://www.toptal.com/developers/hastebin/xoduyuweti.typescript

Same here: https://github.com/Cyb3r-Jak3/uptime-stats/runs/6583704392?check_suite_focus=true

Same here

Me too on the official upptime/upptime repo: https://github.com/upptime/upptime/runs/6585123364?check_suite_focus=true

"yet another same here" https://github.com/gbifatlas/status/runs/6587519856?check_suite_focus=true#step:3:96

Wow i thought it was my dumb mistake
Is that something with the upptime itself or rather github?
@AnandChowdhary

same issue

ditto: https://github.com/rouilj/RoundupAssets/actions/runs/2388379300

Me, too… 🤷🏻♂

Please stop, this is unnecessary. Just click thumbs up and subscribe, then go.

Posting to update regarding the latest release.
Unfortunately the latest (1.12.5) release also has the issue.
@upptime-bot
Error: exec:
/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:42530
        ts.Debug.assert(typeof typeReferenceDirectiveName === "string", "Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.");
                 ^
Error: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.
    at Object.resolveTypeReferenceDirective (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:42530:18)
    at /home/runner/work/Status/Status/site/node_modules/ts-node/src/index.ts:623:55
    at Array.map (<anonymous>)
    at Object.resolveTypeReferenceDirectives (/home/runner/work/Status/Status/site/node_modules/ts-node/src/index.ts:622:33)
    at actualResolveTypeReferenceDirectiveNamesWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:116611:163)
    at resolveTypeReferenceDirectiveNamesWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:116911:26)
    at processTypeReferenceDirectives (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:118393:31)
    at findSourceFileWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:1182[78](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:79):21)
    at findSourceFile (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:11[81](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:82)33:26)
    at processImportedModules (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:118539:25)

        ts.Debug.assert(typeof typeReferenceDirectiveName === "string", "Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.");
                 ^
Error: Debug Failure. False expression: Non-string value passed to `ts.resolveTypeReferenceDirective`, likely by a wrapping package working with an outdated `resolveTypeReferenceDirectives` signature. This is probably not a problem in TS itself.
    at Object.resolveTypeReferenceDirective (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:42530:18)
    at /home/runner/work/Status/Status/site/node_modules/ts-node/src/index.ts:623:55
    at Array.map (<anonymous>)
    at Object.resolveTypeReferenceDirectives (/home/runner/work/Status/Status/site/node_modules/ts-node/src/index.ts:622:33)
    at actualResolveTypeReferenceDirectiveNamesWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:116611:163)
    at resolveTypeReferenceDirectiveNamesWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:116911:26)
    at processTypeReferenceDirectives (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:118393:31)
    at findSourceFileWorker (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:11[82](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:83)78:21)
    at findSourceFile (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:118133:26)
    at processImportedModules (/home/runner/work/Status/Status/site/node_modules/typescript/lib/typescript.js:11[85](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:86)39:25)

    at Object.error (/home/runner/work/_actions/upptime/uptime-monitor/v1.27.0/node_modules/shelljs/src/common.js:110:1)
    at execSync (/home/runner/work/_actions/upptime/uptime-monitor/v1.27.0/dist/index.js:1511[91](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:92):12)
    at Object._exec (/home/runner/work/_actions/upptime/uptime-monitor/v1.27.0/dist/index.js:1512[94](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:95):12)
    at Object.exec (/home/runner/work/_actions/upptime/uptime-monitor/v1.27.0/node_modules/shelljs/src/common.js:335:1)
    at Object.generateSite (/home/runner/work/_actions/upptime/uptime-monitor/v1.27.0/dist/site.js:40:1)
    at processTicksAndRejections (internal/process/task_queues.js:[97](https://github.com/modem7/Status/runs/6609669083?check_suite_focus=true#step:3:98):5)

This is fixed now in https://github.com/upptime/status-page/releases/tag/v1.12.6. You don't to update anything, it should just work if you manually run "Static Site CI", or it'll auto-run tomorrow and it should all be green again.
I'll keep this issue open until one of you confirms that it's working for you.
Cheers!

This is fixed now in https://github.com/upptime/status-page/releases/tag/v1.12.6. You don't to update anything, it should just work if you manually run "Static Site CI", or it'll auto-run tomorrow and it should all be green again.
I'll keep this issue open until one of you confirms that it's working for you.
Cheers!

Confirmed working.
Thank you for your efforts!

Can confirm, closing.


Add/update some UI elements

I assigned this issue to @JackD83, but anyone can self-assign this if they want to do some of this.

[ ] ALVR launcher: this is used to check if SteamVR and the VC++ redistributable package are installed correctly, before launching SteamVR. The functionality is already implemented, it's just missing proper formatting and styling. For now this is implemented as a single html page (index.html). It's hard to use local resources such as fonts/icons/js/css because the html page is loaded at compile time as a string (with include_str!()) and there is no web server (for the launcher). An option is string templating on the Rust side (with the format!() macro) to include resources directly inside the html head or body.
[ ] Hardware checks during the setup wizard: /graphics-devices returns a list of gpus info (name + support). Only the first GPU in the list matters (that have adapter index 0) but the UI could show all of them. If /audio-devices returns no devices, then set gameAudio/enabled to false.
[ ]  Client entries: the management of client entries is entirely offloaded to the server, log id #{ "id"="sessionUpdated", "data"={ "webClientId"=null, "updateType"="clientList" }}# commands will be used to signal the changes to the web client. UI-wise, the client entries should not show the IP address anymore (since now the clients are identified by a hostname), instead a "Manage IPs" button should be added for each entry. The "Manage IPs" should show a dialog box that displays the hostname, the last used local address and the list of manually added remote IPs (with a "Add remote IP" button at the bottom). /clients/trust should be used to trust a client by using ["hostname", null] as the body, or to add a remote IP (with ["hostname", "ip"]). /clients/remove should be used to remove a remote IP (with ["hostname", "ip"]) or to completely remove a client (with ["hostname", null]). As you can see there is no way of adding a remote IP if the client didn't connect the the server locally at least once. This is a required step to exchange the client certificate (the server cannot trust random client certificates from the internet).

@JackD83 These things are not urgent since there are still a lot of other things to do until the v13 release. Some things are still TBD, so please ask for clarifications and give me suggestions. Anyway thank you as always for your contributions!

Closed in favor of #372.

Closed in favor of #372.


Creating temporary object with space in class name (unsigned int) within REQUIRE() parsing error

I don't know if this is an easy, hard, or impossible fix.  There's an easy workaround, but I tend to make a bug report whenever I run into something.  This is of course a reduced test case, otherwise pointless.  i takes the place of a function being tested.
#define CATCH_CONFIG_MAIN
#include <catch.hpp>
TEST_CASE("") {
   unsigned int i = 0;
   REQUIRE(unsigned int { 0 } == i);
}

Gives
In file included from catchUnsigned.cpp:2:0:
catchUnsigned.cpp: In function ‘void ____C_A_T_C_H____T_E_S_T____13()’:
catchUnsigned.cpp:22:12: error: expected primary-expression before ‘unsigned’
    REQUIRE(unsigned int { 0 } == i);
            ^
catchUnsigned.cpp:22:12: error: expected ‘)’ before ‘unsigned’
catchUnsigned.cpp:22:12: error: expected primary-expression before ‘unsigned’
    REQUIRE(unsigned int { 0 } == i);
                ^
catchUnsigned.cpp:22:12: error: expected ‘)’ before ‘unsigned’
catchUnsigned.cpp:22:4: error: expected ‘;’ before ‘)’ token
    REQUIRE(unsigned int { 0 } == i);
    ^
catchUnsigned.cpp:22:4: error: expected primary-expression before ‘)’ token

The same happens for signed int.  I'm thinking the space in the variable type is what's causing it.  Using int or a fixed-width uint32_t works fine.
Easiest workaround to stick with unsigned int is:
#define CATCH_CONFIG_MAIN
#include <catch.hpp>
using uint = unsigned int;
TEST_CASE("") {
   uint i = 0;
   REQUIRE(uint { 0 } == i);
}

Could of course define the expected value, then compare against it instead of a temporary, also.

This is not an issue with catch. unsigned int { 0 } is not legal C++. Wrap the multi-word type in parentheses: (unsigned int) { 0 }.

Huh.  You're right, sorry about that!
int {0} is legal c++11, but unsigned int {0} even in an if statement without involving catch at all gives the same type of error.  Weird!


Network problem when using a second eth interface that have a bloc IP on it. (config included)

Hello,
One problem is that containers can't reach each other, when I ping from one to the other via the public ip redirected to them, it doesn't pass (see iptables problem below).
The other problem is that every time I docker stop on a container, before I start it again I have to restart the whole docker (the daemon), if not, there is the port already binded error. Even if I lsof, I don't see it bind, but docker think it is...
Also if I want to access the container from outside, I have to delete nat rule within DOCKER statement in iptables -L -t nat.
I have a bloc IP from OVH bind on eth1 of my server. It has been a few weeks I run with that, I guess now I have to share it here so we can find how to solve the problem and stop the workarounds. I only have one container that use the address on eth0, all the others is using an IP of the bloc on eth1.
Kernel:
Linux 3.14-0.bpo.1-amd64 #1 SMP Debian 3.14.12-1~bpo70+1 (2014-07-13) x86_64 GNU/Linux

Docker:
Client version: 1.1.2
Client API version: 1.13
Go version (client): go1.2.1
Git commit (client): d84a070
Server version: 1.1.2
Server API version: 1.13
Go version (server): go1.2.1
Git commit (server): d84a070

Here is my /etc/network/interfaces :
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
        address <IP_ADDRESS>
        netmask <IP_ADDRESS>
        network <IP_ADDRESS>
        broadcast <IP_ADDRESS>
        gateway <IP_ADDRESS>

iface eth0 inet6 static
        address 2001:41D0:8:65ec::
        netmask 64
        post-up /sbin/ip -f inet6 route add 2001:41D0:8:65ff:ff:ff:ff:ff dev eth0
        post-up /sbin/ip -f inet6 route add default via 2001:41D0:8:65ff:ff:ff:ff:ff
        pre-down /sbin/ip -f inet6 route del default via 2001:41D0:8:65ff:ff:ff:ff:ff
        pre-down /sbin/ip -f inet6 route del 2001:41D0:8:65ff:ff:ff:ff:ff dev eth0

auto eth1
iface eth1 inet static
     address <IP_ADDRESS>
     netmask <IP_ADDRESS>
     post-up /sbin/ip route add default via <IP_ADDRESS> dev eth1 table 125
     post-up /sbin/ip rule add from <IP_ADDRESS>/27 table 125
     pre-down /sbin/ip rule del from <IP_ADDRESS>/27 table 125
     pre-down /sbin/ip route del default via <IP_ADDRESS> dev eth1 table 125
     post-up /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-down /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-up /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-down /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-up /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-down /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-up /sbin/ip addr add <IP_ADDRESS>/27 dev eth1
     post-down /sbin/ip addr add <IP_ADDRESS>/27 dev eth1

Here is the ip addr:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet <IP_ADDRESS>/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:25:90:dd:32:0c brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2001:41d0:8:65ec::/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::225:80ff:fedd:320c/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
    link/ether 00:25:90:dd:32:0d brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/27 scope global eth1
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/27 scope global secondary eth1
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/27 scope global secondary eth1
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/27 scope global secondary eth1
       valid_lft forever preferred_lft forever
    inet <IP_ADDRESS>/27 brd <IP_ADDRESS> scope global secondary eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::225:80ff:fedd:320d/64 scope link
       valid_lft forever preferred_lft forever
267: veth49fb: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether 52:3a:a2:ce:19:06 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::503a:a2ff:fece:1906/64 scope link
       valid_lft forever preferred_lft forever
277: veth9707: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether 4e:19:2f:c7:26:db brd ff:ff:ff:ff:ff:ff
    inet6 fe80::4c19:2fff:fec7:26db/64 scope link
       valid_lft forever preferred_lft forever
53: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 56:84:7a:fe:97:99 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/16 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::5484:7aff:fefe:9799/64 scope link
       valid_lft forever preferred_lft forever
329: veth66fa: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether d2:06:6c:c8:de:09 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::d006:6cff:fec8:de09/64 scope link
       valid_lft forever preferred_lft forever
185: veth652d: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether 8a:f9:3a:e4:27:2e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::88f9:3aff:fee4:272e/64 scope link
       valid_lft forever preferred_lft forever
191: veth3dbb: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether f6:d2:d5:91:b2:d0 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::f4d2:d5ff:fe91:b2d0/64 scope link
       valid_lft forever preferred_lft forever
193: vethe287: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether fe:42:2b:b5:eb:25 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::fc42:2bff:feb5:eb25/64 scope link
       valid_lft forever preferred_lft forever
207: veth9f71: <BROADCAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master docker0 state UP qlen 1000
    link/ether de:d5:4b:b9:0a:f1 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::dcd5:4bff:feb9:af1/64 scope link
       valid_lft forever preferred_lft forever

iptables -L -t nat :
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination
DOCKER     all  --  anywhere             anywhere             ADDRTYPE match dst-type LOCAL

Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
DOCKER     all  --  anywhere            !loopback/8           ADDRTYPE match dst-type LOCAL

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE  all  --  <IP_ADDRESS>/16       !<IP_ADDRESS>/16

Chain DOCKER (2 references)
target     prot opt source               destination
DNAT       tcp  --  anywhere             alpha.xoib.com    tcp dpt:63389 to:<IP_ADDRESS>:389

I kept the last one because it is on the adress of eth0, the others for eth1 I had to delete them for the container to be reachable from outside
I changed all the dns name and adresses to keep the server private.
Thanks,

closing as duplicate of https://github.com/docker/docker/issues/2801, it is really a effect caused by that issue


TrackingEventProcessor-Thread dies during init

We're observing missing TrackingEventProcessors when our database doesn't get ready quick enough. Looking at the stack-traces everything points to the inner TrackingEventProcessor$WorkerLauncher that's used to init segments and distribute them to single TrackingSegmentWorker:
If this call fails with an execption:
https://github.com/AxonFramework/AxonFramework/blob/90ac654f0dbf2b4ed6d1a82c5c28ec27c11996e3/core/src/main/java/org/axonframework/eventhandling/TrackingEventProcessor.java#L546
the WorkerLauncher-Thread crashes as it seems there is no recovery/retry-mechanism. Especially during re-deployments this is pretty brittle and it should be more resilient to failures.

Pushed a test to reproduce and some draft which fixes this case.

I thought it's reasonable to span the try/catch until segments are completely initialized.


Documentation links with a trailing slash seem to be broken

Any link in the documentation with a trailing slash currently seems to be broken and redirects to the main site, e.g. links on
https://docs-beta.opensearch.org/security-plugin/configuration/index
https://docs-beta.opensearch.org/opensearch/install/docker-security/ redirects to https://docs-beta.opensearch.org/
vs.
https://docs-beta.opensearch.org/opensearch/install/docker-security which works.
I'm able to reproduce this both on Chrome and Firefox.

It seems that local Jekyll builds and GitHub Pages aren't aligned on behavior here, since these links continued (and continue) to work fine locally for me. I believe I have things working on the actual site now. Let me know if you're still encountering issues.


Test coverage: Finalize

[x] Write unit tests pre refactoring (3 story points)
[ ] Refactor tests after refactoring and include any new functions (3 story points)


--match  causes "--dirty is incompatible with commit-ishes"

This seems to only affect me on Windows.  Versioneer v.0.16.
At https://github.com/warner/python-versioneer/blob/master/src/git/from_vcs.py#L32 - the addition of the --match argument with the tag prefix causes versioneer to fail completely and return the version as 0+unknown.  Removing these two arguments makes things work again.
Does this warrant some platform special casing?  I'm happy to put a PR forward, but I don't have a feeling for the best way to address this issue.

Seconded.

Huh. what version of git are you using? I'd expect --match success or failure to depend upon git, more than on the platform.
Maybe we could change it to watch for a return value that indicates a --match -less git (or OS) and fall back to some other flavor of the command. Or run two separate git commands (one with --match, one without) and merge their results.

Apologies, I will be unable to contribute to this issue, I filed this when I was at a different job. I recall it happening moderately frequently, as we used Versioneer in our package management system, but I'm not currently in an environment that uses Versioneer in our package management system so I'll be unable to perform any further testing.

No worries.. thanks for confirming it happens in more than one place!

I can confirm this. git 2.14.0, not that it matters.
I'm getting a message fatal: --dirty is incompatible with commit-ishes when running python setup.py bdist_wheel.  It only occurs with an empty tag_prefix.
It looks like the * is being globbed on windows, which results in multiple arguments following --match. For example, subprocess.Popen(['echo', '*']) will result in one argument on unix systems, but many arguments on windows.
I'll try to dig into this more tonight.

I too am seeing this issue with versioneer v0.18, but only when using my anaconda distribution of python through cygwin. If I use python 3.6 or 2.7 through cygwin, python setup.py version yields the correct version tag. With the anaconda distribution [python 3.5.4], I get the --dirty is incompatible with commit-ishes error. I'm using git 2.14.1 as well

I'm curious if this is resolved by #229.

Hi, after some analysis of versioneer.py I came up with a fix in my PR #262. Could you try this out please?


JAVA-3145: Implement some notion of retry logic around call to metadata service for Astra clients

I implemented the retry mechanism in two ways. Apart from the current one, the following also works:
  @NonNull
  protected BufferedReader fetchProxyMetadata(
      @NonNull URL metadataServiceUrl, @NonNull SSLContext sslContext) throws IOException {
    HttpsURLConnection connection = null;
    int attempt = 0;
    while(attempt < METADATA_RETRY_MAX_ATTEMPTS){
      try {
        connection = (HttpsURLConnection) metadataServiceUrl.openConnection();
        connection.setSSLSocketFactory(sslContext.getSocketFactory());
        connection.setRequestMethod("GET");
        connection.setRequestProperty("host", "localhost");
        return new BufferedReader(
                new InputStreamReader(connection.getInputStream(), StandardCharsets.UTF_8));
      } catch (ConnectException e) {
        throw new IllegalStateException(
                "Unable to connect to cloud metadata service. Please make sure your cluster is not parked or terminated",
                e);
      } catch (UnknownHostException e) {
        throw new IllegalStateException(
                "Unable to resolve host for cloud metadata service. Please make sure your cluster is not terminated",
                e);
      } catch (IOException e) {
        attempt++;
        // if this is the last try, throw
        // else if status code not 200, retry; otherwise, throw
        if (attempt != METADATA_RETRY_MAX_ATTEMPTS && connection != null && connection.getResponseCode() != 200) {
          try {
            Thread.sleep(METADATA_RETRY_INITIAL_DELAY_MS);
          } catch (InterruptedException interruptedException) {
            Thread.currentThread().interrupt();
            throw new IOException("Interrupted while waiting to retry metadata fetch", interruptedException);
          }
        } else {
          throw e;
        }
      }
    }
    throw new DriverTimeoutException("Unable to fetch metadata from cloud metadata service"); // dead code
  }

We could discuss those design decisions in our next meeting :)

Regarding your alternate proposed implementation above @SiyaoIsHiding; I think we probably should prefer the version actually contained in this PR.  We know some non-200 response codes can trigger an IOException but I don't think we have that guaranteed across the board.  The code in your existing impl explicitly checks the response code for everybody rather than relying on an IOException to hit that logic; I'm guessing that prolly what we want to go with.


Add toHaveBeenLastCalledWith / migrate lastCalledWith to jest-matcher…

…s package

Current coverage is 91.17% (diff: 100%)

Merging #1526 into master will increase coverage by 0.16%

@@             master      #1526   diff @@
==========================================
  Files            28         28
  Lines          1102       1122    +20
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           1003       1023    +20
  Misses           99         99
  Partials          0          0

Powered by Codecov. Last update 83c2541...b022094


Add multicluster deployment documentation to Istio

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
Assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sebastienvas note clicking the link to the OWNERS file results in a 404.

/assign linsun

@sdake that s because the file does not exist. @geeknoid  What should be the initial file ?

For now, please list me and Lin as approvers.

@sebastienvas right - ok makes sense :)  I guess in the bot convergence across repos, this OWNERS file was missed.
Cheers
-steve

Added the OWNERS file

/assign @geeknoid

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
Assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign linsun

rebased to pull in spell checking and automated linting. (plus branch was in merge conflict anyway).

@linsun @geeknoid PTAL especially the dictionary expansion.

apologies on the force push - git head in detached state.

Do you have a staging site I can look at for the final rendered form?
On Thu, Apr 5, 2018 at 6:08 PM Steven Dake<EMAIL_ADDRESS>wrote:

apologies on the force push - git head in detached state.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio.github.io/pull/1139#issuecomment-379120487,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVucHWDWNCYWvVTp7U0vHoDtXNqJJCkUks5tlsAkgaJpZM4TD9t7
.

I render locally on my lab gear, but will spin up a GCP instance to render the docs.  Will need about 20 mins or so - and its dinner time, so t-2 hrs?

@geeknoid give this a go: http://<IP_ADDRESS>:4000/docs/setup/kubernetes/

minor comments, otherwise looks good
/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, linsun
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid,linsun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

@linsun thanks for picking up those problems.  There should be more clarity now.

@sebastienvas You had mentioned on the ML that tide is being used for this repo.  I see that is the case after I just pushed an update.  One thing that is odd is the PR had  lgtm/approve/cla/passing checks/no merge conflicts flags for 16 hours, yet did not automatically merge.  In this ok, thats fine - as I needed to push 1 more update to fix reviewer comments.  Are manual merges currently required for this repo?  Looking over the closed PRs, it looks as though individual devs have been approving pulls (rather than a bot).
Is this inconsistent from istio/istio (which automatically merges), just a misunderstanding about how the automatic merging bot should work for this repo, a bug, or some other condition?
Cheers
-steve

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, linsun
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid,linsun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid, linsun
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid,linsun]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hklai The PR looks good for merge yet tide hasn't merged it.  Can you take a look?
Cheers
-steve

@sebastienvas
The PR is in the MERGE state (https://prow.istio.io/tide.html) but is not merged. I don't seem to see why, do you?

@costinm thanks for the great comments.  I will address existing issues today in a new PR.  An ILB makes good sense for Pilot/Mixer.  I'll submit a PR that makes that happen.  I am aware the Pod IPs change too often - and think it is a big limitation of the current implementation.  Thanks for making the ILB suggestion.
RE forward looking comments I am doing my best to make this documentation match the reality of the implementation, not what it should be or we wish it to be.  I have a separate PR in the works to be ready to go with the secrets changes in @sbezverk 'z work once his work merges.
Cheers
-steve


os/mac/keg: Frameworks -> MUST_BE_WRITABLE_DIRS

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

I added HOMEBREW_PREFIX/"Frameworks" to the KEG_LINK_DIRECTORIES and MUST_EXIST_DIRECTORIES variables in extend/os/mac/keg.rb in #6620, which I thought was enough, but I just ran into an issue in which brew test-bot.rb:1185-1201 deletes HOMEBREW_PREFIX/"Frameworks" folder, which causes the brew doctor part of the test-bot to complain that the Frameworks folder is missing (example jenkins failure). This chunk of test-bot code is using the MUST_BE_WRITABLE_DIRECTORIES variable, which is defined in keg.rb, so I've extended that variable with HOMEBREW_PREFIX/"Frameworks" for os/mac, and I included MUST_EXIST_SUBDIRECTORIES for completeness.
It's a little weird because I observed it in a failure with one of my jenkins builds on a 10.13 machine, but I wasn't able to reproduce it on a different 10.14 machine. I didn't dig further than that.
An alternative to this PR is to not remove the Frameworks folder in test-bot (such as https://github.com/scpeters/homebrew-test-bot/commit/a9b66521a6287b67bc1109a94afa5f272b676700, which I used as a temporary workaround to fix the previously mentioned jenkins build). I can submit a pull request for that change instead if requested.

Makes sense, thanks again @scpeters!


Add missing or move incorrect semicolons

Missing or incorrect semicolon placement in function definitions was leading to multiple signatures in the documentation

Tagging @daniel-thom in case this broke any tests


Completion target shown in italics when "editor.suggest.insertMode": "replace"

Can this be turned off? Or changed to be a selection-type highlight rather italics?
Also this behavior seems to happen even if the extension doesn't support replace.

I don't see this same behavior with json (which works) but with typescript I see it and the replace doesn't work (#91105)

Yeah, there is setting for this "editor.suggest.insertHighlight": true. I am open for suggestions but the idea is that the italics part shows unexpected insert behaviour. E.g you have configured replace behaviour but this insertion only support insert (and the other way around).

So the italics is kind of an error case? Is it worth trying to show that? Because I'm not sure anyone will figure out the meaning without being told.

Not really an error case but a kind of "you will likely be surprised". Tho, given that we now have the  (optional) suggest widget status bar we could remove this again. The status bar should be telling if something can be inserted or replaced only

Decided to remove this - users that need more guidance should use the editor.suggest.statusBar.visible setting

@jrieken but how I can be sure what part will be replaced?
TS usually completes name, however other plugins might also go for next punctuation characters or more.
Instruction to use Shift in status bar suggest that it can be used, but doesn't help to determine what actually will be replaced.


WSL 2: VSCode keeps crashing with error "WebSocket close with status code 1006"

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.94.2 & 1.95..0 Insiders
OS Version: Windows 11 23H2 22631.4317
WSL Version: <IP_ADDRESS>
Kernel Version: <IP_ADDRESS>-2
Windows Version from WSL: 10.0.22631.4317

Steps to Reproduce:

Connect to WSL in VSCode
After a few minutes, the connection hangs
When force-reloading the window, I get the following:

This happens since at least late 2023 (see #201612). I've tried on VSCode Insiders and the problem still happens. Now the problem also happens with SSH.
I've tried uninstalling and reinstalling WSL completely (not just the distribution) but that didn't solve the problem.
EDIT: I also tried enabling the virtio9p=false option as indicated in another issue, without success.
Here are the logs I forgot to attach earlier:
Output of WSL: Show log
[2024-10-14 09:30:57.060] Extension version: 0.88.4
[2024-10-14 09:30:57.060] L10N bundle: none
[2024-10-14 09:30:57.083] authorityHierarchy: wsl+Ubuntu
[2024-10-14 09:30:57.083] WSL extension activating for a local WSL instance
[2024-10-14 09:30:57.094] Resolving wsl+Ubuntu, resolveAttempt: 1
[2024-10-14 09:30:57.095] NodeExecServer run: C:\Windows\System32\wsl.exe --status
[2024-10-14 09:30:57.123] WSL feature installed: true (wsl --status)
[2024-10-14 09:30:57.123] NodeExecServer run: C:\Windows\System32\wsl.exe --list --verbose
[2024-10-14 09:30:57.149] 1 distros found
[2024-10-14 09:30:57.150] Starting VS Code Server inside WSL (wsl2)
[2024-10-14 09:30:57.150] Windows build: 22631. Multi distro support: available. WSL path support: enabled
[2024-10-14 09:30:57.150] Scriptless setup: false
[2024-10-14 09:30:57.158] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e sh -c [ -f '/tmp/vscode-distro-env.ASbwos' ] && cat '/tmp/vscode-distro-env.ASbwos' || echo ''
[2024-10-14 09:30:57.212] WSL daemon log file:
[2024-10-14 09:30:57.213] Connecting to daemon started by other WSL window... <IP_ADDRESS>-microsoft-standard-WSL2 Ubuntu
[2024-10-14 09:30:57.213] WSL resolver response: <IP_ADDRESS>:52540
[2024-10-14 09:30:57.213] To debug connection issues, open a local browser on http://<IP_ADDRESS>:52540/version
[2024-10-14 09:30:57.217] Using shell environment from invoking shell: /tmp/vscode-distro-env.ASbwos
[2024-10-14 09:30:57.224] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.281] Resolving wsl+Ubuntu, resolveAttempt: 2
[2024-10-14 09:30:57.281] Returning resolved promise.
[2024-10-14 09:30:57.297] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.381] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.438] Resolving wsl+Ubuntu, resolveAttempt: 3
[2024-10-14 09:30:57.438] Returning resolved promise.
[2024-10-14 09:30:57.451] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.531] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.589] Resolving wsl+Ubuntu, resolveAttempt: 4
[2024-10-14 09:30:57.589] Returning resolved promise.
[2024-10-14 09:30:57.612] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.680] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.738] Resolving wsl+Ubuntu, resolveAttempt: 5
[2024-10-14 09:30:57.738] Returning resolved promise.
[2024-10-14 09:30:57.763] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.846] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });
[2024-10-14 09:30:57.916] Download in background is enabled
[2024-10-14 09:30:57.932] NodeExecServer run: C:\Windows\System32\wsl.exe -d Ubuntu -e /home/clement/.vscode-server/bin/384ff7382de624fb94dbaf6da11977bba1ecd427/node -e const net = require('net'); process.stdin.pause(); const client = net.createConnection({ host: '<IP_ADDRESS>', port: 43115 }, () => { client.pipe(process.stdout); process.stdin.pipe(client); }); client.on('close', function (hadError) { console.error(hadError ? 'Remote close with error' : 'Remote close'); process.exit(hadError ? 1 : 0); }); client.on('error', function (err) { process.stderr.write(err && (err.stack || err.message) || String(err)); });

Output of Developer: Shows logs... > Extension Host
2024-10-14 11:30:56.989 [info] Extension host with pid 6020 started
2024-10-14 11:30:56.989 [info] Skipping acquiring lock for c:\Users\cleme\AppData\Roaming\Code\User\workspaceStorage\3986382221569136d353bb5f868c969b.
2024-10-14 11:30:56.989 [info] $getCanonicalURI invoked for authority (wsl)
2024-10-14 11:30:56.993 [info] ExtensionService#_doActivateExtension ms-vscode-remote.remote-wsl, startup: false, activationEvent: 'onResolveRemoteAuthority:wsl'
2024-10-14 11:30:57.096 [info] [resolveAuthority(wsl,1)][0ms] activating remote resolvers wsl+Ubuntu
2024-10-14 11:30:57.096 [info] [resolveAuthority(wsl,1)][0ms] activating resolver for wsl+Ubuntu...
2024-10-14 11:30:57.096 [info] [resolveAuthority(wsl,1)][0ms] invoking final resolve()...
2024-10-14 11:30:57.221 [info] [resolveAuthority(wsl,1)][124ms] setting tunnel factory...
2024-10-14 11:30:57.221 [info] [resolveAuthority(wsl,1)][124ms] returned <IP_ADDRESS>:52540
2024-10-14 11:30:57.283 [info] [resolveAuthority(wsl,2)][0ms] activating remote resolvers wsl+Ubuntu
2024-10-14 11:30:57.283 [info] [resolveAuthority(wsl,2)][0ms] activating resolver for wsl+Ubuntu...
2024-10-14 11:30:57.284 [info] [resolveAuthority(wsl,2)][0ms] invoking final resolve()...
2024-10-14 11:30:57.284 [info] [resolveAuthority(wsl,2)][0ms] setting tunnel factory...
2024-10-14 11:30:57.284 [info] [resolveAuthority(wsl,2)][0ms] returned <IP_ADDRESS>:52540
2024-10-14 11:30:57.441 [info] [resolveAuthority(wsl,3)][0ms] activating remote resolvers wsl+Ubuntu
2024-10-14 11:30:57.441 [info] [resolveAuthority(wsl,3)][0ms] activating resolver for wsl+Ubuntu...
2024-10-14 11:30:57.441 [info] [resolveAuthority(wsl,3)][0ms] invoking final resolve()...
2024-10-14 11:30:57.441 [info] [resolveAuthority(wsl,3)][0ms] setting tunnel factory...
2024-10-14 11:30:57.441 [info] [resolveAuthority(wsl,3)][0ms] returned <IP_ADDRESS>:52540
2024-10-14 11:30:57.591 [info] [resolveAuthority(wsl,4)][0ms] activating remote resolvers wsl+Ubuntu
2024-10-14 11:30:57.591 [info] [resolveAuthority(wsl,4)][0ms] activating resolver for wsl+Ubuntu...
2024-10-14 11:30:57.591 [info] [resolveAuthority(wsl,4)][0ms] invoking final resolve()...
2024-10-14 11:30:57.591 [info] [resolveAuthority(wsl,4)][0ms] setting tunnel factory...
2024-10-14 11:30:57.592 [info] [resolveAuthority(wsl,4)][0ms] returned <IP_ADDRESS>:52540
2024-10-14 11:30:57.740 [info] [resolveAuthority(wsl,5)][0ms] activating remote resolvers wsl+Ubuntu
2024-10-14 11:30:57.740 [info] [resolveAuthority(wsl,5)][0ms] activating resolver for wsl+Ubuntu...
2024-10-14 11:30:57.740 [info] [resolveAuthority(wsl,5)][0ms] invoking final resolve()...
2024-10-14 11:30:57.740 [info] [resolveAuthority(wsl,5)][1ms] setting tunnel factory...
2024-10-14 11:30:57.740 [info] [resolveAuthority(wsl,5)][1ms] returned <IP_ADDRESS>:52540
2024-10-14 11:30:57.934 [info] Eager extensions activated
2024-10-14 11:30:58.017 [info] ExtensionService#_doActivateExtension PKief.material-icon-theme, startup: false, activationEvent: 'onStartupFinished'
2024-10-14 11:30:58.027 [info] ExtensionService#_doActivateExtension usernamehw.errorlens, startup: false, activationEvent: 'onStartupFinished'
2024-10-14 11:30:58.032 [info] ExtensionService#_doActivateExtension zhuangtongfa.material-theme, startup: false, activationEvent: 'onStartupFinished'

I tried to use Tailscale's SSH to see if it worked better, and got a different kind of bug. Here is the SSH log from VSCode:
[14:04:20.417] Log Level: 2
[14:04:20.429] VS Code version: 1.94.2
[14:04:20.429] Remote-SSH version<EMAIL_ADDRESS>[14:04:20.429] win32 x64
[14:04:20.432] SSH Resolver called for "ssh-remote+bulldozer-wsl", attempt 1
[14:04:20.433] "remote.SSH.useLocalServer": false
[14:04:20.433] "remote.SSH.useExecServer": true
[14:04:20.433] "remote.SSH.showLoginTerminal": false
[14:04:20.433] "remote.SSH.remotePlatform": {"localhost":"linux","rpi4-nas":"linux","<IP_ADDRESS>":"linux","bulldozer-wsl":"linux"}
[14:04:20.433] "remote.SSH.path": undefined
[14:04:20.433] "remote.SSH.configFile": undefined
[14:04:20.433] "remote.SSH.useFlock": true
[14:04:20.433] "remote.SSH.lockfilesInTmp": false
[14:04:20.433] "remote.SSH.localServerDownload": auto
[14:04:20.433] "remote.SSH.remoteServerListenOnSocket": false
[14:04:20.433] "remote.SSH.showLoginTerminal": false
[14:04:20.433] "remote.SSH.defaultExtensions": []
[14:04:20.433] "remote.SSH.loglevel": 2
[14:04:20.434] "remote.SSH.enableDynamicForwarding": true
[14:04:20.434] "remote.SSH.enableRemoteCommand": false
[14:04:20.434] "remote.SSH.serverPickPortsFromRange": {}
[14:04:20.434] "remote.SSH.serverInstallPath": {}
[14:04:20.434] "remote.SSH.permitPtyAllocation": false
[14:04:20.434] "remote.SSH.preferredLocalPortRange: undefined
[14:04:20.434] "remote.SSH.useCurlAndWgetConfigurationFiles: false
[14:04:20.439] SSH Resolver called for host: bulldozer-wsl
[14:04:20.439] Setting up SSH remote "bulldozer-wsl"
[14:04:20.444] Using commit id "384ff7382de624fb94dbaf6da11977bba1ecd427" and quality "stable" for server
[14:04:20.447] Script variables:
 {
  "InstallExitCode.24": "AlreadyInProgress",
  "InstallExitCode.25": "ServerDownloadFailed",
  "InstallExitCode.26": "NoDownloaderAvailable",
  "InstallExitCode.27": "UnsupportedArch",
  "InstallExitCode.28": "StatusCheckFailed",
  "InstallExitCode.29": "NeedInsidersArch",
  "InstallExitCode.30": "NoDownloaderAvailableForStatusCheck",
  "InstallExitCode.31": "ServerTransferFailed",
  "InstallExitCode.32": "ServerFailedToStart",
  "InstallExitCode.33": "NeedInsidersWindows",
  "InstallExitCode.34": "CreateInstallDirFailed",
  "InstallExitCode.35": "UnsupportedPlatform",
  "InstallExitCode.36": "ServerTerminatedCVE20201416",
  "InstallExitCode.37": "UnpackFailed",
  "InstallExitCode.38": "ChangeDirFailed",
  "InstallExitCode.AlreadyInProgress": "24",
  "InstallExitCode.ServerDownloadFailed": "25",
  "InstallExitCode.NoDownloaderAvailable": "26",
  "InstallExitCode.NoDownloaderAvailableForStatusCheck": "30",
  "InstallExitCode.UnsupportedArch": "27",
  "InstallExitCode.StatusCheckFailed": "28",
  "InstallExitCode.NeedInsidersArch": "29",
  "InstallExitCode.ServerTransferFailed": "31",
  "InstallExitCode.ServerFailedToStart": "32",
  "InstallExitCode.NeedInsidersWindows": "33",
  "InstallExitCode.CreateInstallDirFailed": "34",
  "InstallExitCode.UnsupportedPlatform": "35",
  "InstallExitCode.ServerTerminatedCVE20201416": "36",
  "InstallExitCode.UnpackFailed": "37",
  "InstallExitCode.ChangeDirFailed": "38",
  "InstallUnpackCode.Success": "success",
  "InstallUnpackCode.Error": "error",
  "InstallUnpackCode.MissingFiles": "missingFiles",
  "uuid": "badb94640956",
  "startMarker": "badb94640956: running",
  "commitId": "384ff7382de624fb94dbaf6da11977bba1ecd427",
  "quality": "stable",
  "token": "1a1a1111-1aa1-1a1a-aa1a-111111a1a11a",
  "vscodeAgentFolder": "$HOME/.vscode-server",
  "allowClientDownload": "1",
  "forceClientDownload": "0",
  "cliNameInArchive": "code",
  "ignoreWgetConfigFlag": " --no-config ",
  "ignoreCurlConfigFlag": " --disable ",
  "wgetTriesSegment": "--tries=1",
  "listenArgs": "--on-host=<IP_ADDRESS> --on-port",
  "getDownloadServerStartTrigger": "badb94640956:trigger_server_download",
  "getDownloadServerEndTrigger": "badb94640956:trigger_server_download_end",
  "getProgressDownloading": "badb94640956%%1%%",
  "getProgressInstalling": "badb94640956%%2%%"
}
[14:04:20.449] Install and start server if needed
[14:04:20.450] Checking ssh with "C:\Windows\System32\OpenSSH\ssh.exe -V"
[14:04:20.468] > OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2

[14:04:20.470] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53670 "bulldozer-wsl" sh
[14:04:20.471] Generated SSH command: 'type "C:\Users\cleme\AppData\Local\Temp\vscode-linux-multi-line-command-bulldozer-wsl-588604053.sh" | "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53670 "bulldozer-wsl" sh'
[14:04:20.472] Using connect timeout of 17 seconds
[14:04:20.472] Terminal shell path: C:\Windows\System32\cmd.exe
[14:04:20.886] > badb94640956: running
> Script executing under PID: 11723
> Found existing installation at /home/clement/.vscode-server...
> Starting VS Code CLI...
> printenv:
>     USER=clement
>     SSH_CLIENT=<IP_ADDRESS> 53671 22
>     SHLVL=0
>     HOME=/home/clement
>     _=/usr/bin/sh
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>     SHELL=/bin/bash
>     PWD=/home/clement
>     SSH_CONNECTION=<IP_ADDRESS> 53671 <IP_ADDRESS> 22
> Removing old logfile at /home/clement/.vscode-server/.cli.384ff7382de624fb94dbaf6da11977bba1ecd427.log
> Spawned remote CLI: 11741
> Waiting for server log...
> ]0;C:\Windows\System32\cmd.exe
[14:04:20.886] Got some output, clearing connection timeout
[14:04:20.916] > Waiting for server log...
[14:04:20.930] > badb94640956: start
> listeningOn==<IP_ADDRESS>:45327==
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/tmp==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> serverStartTime==67==
> execServerToken==1a1a1111-1aa1-1a1a-aa1a-111111a1a11a==
> platformDownloadPath==cli-alpine-x64==
> badb94640956: end
[14:04:20.930] Received install output:
listeningOn==<IP_ADDRESS>:45327==
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/tmp==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==67==
execServerToken==1a1a1111-1aa1-1a1a-aa1a-111111a1a11a==
platformDownloadPath==cli-alpine-x64==

[14:04:20.931] Remote server is listening on port 45327
[14:04:20.931] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":45327},"osReleaseId":"ubuntu","arch":"x86_64","tmpDir":"/tmp","platform":"linux","execServerToken":"1a1a1111-1aa1-1a1a-aa1a-111111a1a11a"},"serverStartTime":67,"installUnpackCode":""}
[14:04:20.933] Starting forwarding server. local port 53672 -> socksPort 53670 -> remotePort 45327
[14:04:20.933] Forwarding server listening on port 53672
[14:04:20.933] Waiting for ssh tunnel to be ready
[14:04:20.934] [Forwarding server port 53672] Got connection 0
[14:04:20.935] Tunneled port 45327 to local port 53672
[14:04:20.935] Resolved "ssh-remote+bulldozer-wsl" to "port 53672"
[14:04:20.940] Initizing new exec server for ssh-remote+bulldozer-wsl
[14:04:20.940] Resolving exec server at port 53672
[14:04:20.941] [Forwarding server port 53672] Got connection 1
[14:04:20.947] >
[14:04:20.964] Exec server for ssh-remote+bulldozer-wsl created and cached
[14:04:20.967] ------

[14:04:20.975] [server] Checking /home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/log.txt and /home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/pid.txt for a running server...
[14:04:21.024] [server] Installing and setting up Visual Studio Code Server...
[14:04:21.025] [server] Server setup complete
[14:04:21.025] [server] Starting server...
[14:04:21.025] [server] Starting server with command... Command { std: "/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/bin/code-server" "--connection-token=remotessh" "--accept-server-license-terms" "--start-server" "--enable-remote-auto-shutdown" "--socket-path=/tmp/code-f9d9ef5d-1985-4523-a99c-8b68dd13f936", kill_on_drop: false }
[14:04:21.121] [server] *
[14:04:21.121] [server] * Visual Studio Code Server
[14:04:21.121] [server] *
[14:04:21.121] [server] * By using the software, you agree to
[14:04:21.121] [server] * the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
[14:04:21.121] [server] * the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
[14:04:21.123] [server] Server bound to /tmp/code-f9d9ef5d-1985-4523-a99c-8b68dd13f936
[14:04:21.123] [server] Extension host agent listening on /tmp/code-f9d9ef5d-1985-4523-a99c-8b68dd13f936
[14:04:21.123] [server] parsed location: "/tmp/code-f9d9ef5d-1985-4523-a99c-8b68dd13f936"
[14:04:21.123] [server]
[14:04:21.123] [server] Server started
[14:04:21.175] [server] [14:04:21]
[14:04:21.218] [server]
[14:04:21.218] [server]
[14:04:21.218] [server]
[14:04:21.222] [server] [14:04:21] Extension host agent started.
[14:04:21.255] [server] [14:04:21] [<unknown>][646633b3][ExtensionHostConnection] New connection established.
[14:04:21.301] [server] [14:04:21] [<unknown>][bb8f06fb][ManagementConnection] New connection established.
[14:04:30.876] [server] [14:04:29] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.876] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.876] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.876] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.876] [server] [14:04:29] resolving shell environment failed Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.876] [server] [14:04:29] ptyHost was unable to resolve shell environment Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.876] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.876] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.876] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.876] [server] [14:04:29] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.876] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.876] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.876] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.876] [server] [14:04:29] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.876] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.876] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.877] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.877] [server] [14:04:29] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.877] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.877] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.877] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.877] [server] [14:04:29] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.877] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.877] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.877] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.877] [server] [14:04:29] ptyHost was unable to resolve shell environment Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:04:30.877] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:04:30.877] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:04:30.877] [server]     at process.processTimers (node:internal/timers:519:7)
[14:04:30.877] [server] [14:04:29] [<unknown>][646633b3][ExtensionHostConnection] <11844> Launched Extension Host Process.
[14:07:20.722] [server] [14:07:20] ptyHost was unable to resolve shell environment Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:07:20.722] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:07:20.722] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:07:20.722] [server]     at process.processTimers (node:internal/timers:519:7)
[14:07:20.806] [server] [14:07:20] ExtensionHostConnection#buildUserEnvironment resolving shell environment failed Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration and restart.
[14:07:20.852] [server]     at Timeout.<anonymous> (file:///home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/out/vs/server/node/server.main.js:48:731)
[14:07:20.852] [server]     at listOnTimeout (node:internal/timers:581:17)
[14:07:20.852] [server]     at process.processTimers (node:internal/timers:519:7)
[14:07:44.632] [server]
[14:07:44.633] [server] <--- Last few GCs --->
[14:07:44.633] [server]
[14:07:44.633] [server] [11796:0x75c1f20]   214522 ms: Mark-Compact 4051.2 (4139.2) -> 4040.3 (4141.7) MB, 648.61 / 0.00 ms  (average mu = 0.658, current mu = 0.181) task; scavenge might not succeed
[14:07:44.633] [server]
[14:07:44.637] [server]  1: 0xb82d33 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.637] [server]  2: 0xef0c50 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.637] [server]  3: 0xef0f37 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.638] [server]  4: 0x1102ad5  [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.638] [server]  5: 0x111a958 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.638] [server]  6: 0x117352c v8::internal::MinorGCJob::Task::RunInternal() [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.639] [server]  7: 0xd392c6  [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.639] [server]  8: 0xd3c86f node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.639] [server]  9: 0x18b2093  [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.639] [server] 10: 0x18c6b0b  [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.640] [server] 11: 0x18b2db7 uv_run [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.640] [server] 12: 0xbc9be6 node::SpinEventLoopInternal(node::Environment*) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.640] [server] 13: 0xd0d604  [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.641] [server] 14: 0xd0e09d node::NodeMainInstance::Run() [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.641] [server] 15: 0xc7216f node::Start(int, char**) [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:07:44.641] [server] 16: 0x7f11501a51ca  [/lib/x86_64-linux-gnu/libc.so.6]
[14:07:44.641] [server] 17: 0x7f11501a528b __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
[14:07:44.641] [server] 18: 0xbc6b6e _start [/home/clement/.vscode-server/cli/servers/Stable-384ff7382de624fb94dbaf6da11977bba1ecd427/server/node]
[14:08:07.441] ------

[14:08:07.441] SSH Resolver called for "ssh-remote+bulldozer-wsl", attempt 2, (Reconnection)
[14:08:07.442] SSH Resolver called for host: bulldozer-wsl
[14:08:07.442] Setting up SSH remote "bulldozer-wsl"
[14:08:07.443] Using commit id "384ff7382de624fb94dbaf6da11977bba1ecd427" and quality "stable" for server
[14:08:07.444] Script variables:
 {
  "InstallExitCode.24": "AlreadyInProgress",
  "InstallExitCode.25": "ServerDownloadFailed",
  "InstallExitCode.26": "NoDownloaderAvailable",
  "InstallExitCode.27": "UnsupportedArch",
  "InstallExitCode.28": "StatusCheckFailed",
  "InstallExitCode.29": "NeedInsidersArch",
  "InstallExitCode.30": "NoDownloaderAvailableForStatusCheck",
  "InstallExitCode.31": "ServerTransferFailed",
  "InstallExitCode.32": "ServerFailedToStart",
  "InstallExitCode.33": "NeedInsidersWindows",
  "InstallExitCode.34": "CreateInstallDirFailed",
  "InstallExitCode.35": "UnsupportedPlatform",
  "InstallExitCode.36": "ServerTerminatedCVE20201416",
  "InstallExitCode.37": "UnpackFailed",
  "InstallExitCode.38": "ChangeDirFailed",
  "InstallExitCode.AlreadyInProgress": "24",
  "InstallExitCode.ServerDownloadFailed": "25",
  "InstallExitCode.NoDownloaderAvailable": "26",
  "InstallExitCode.NoDownloaderAvailableForStatusCheck": "30",
  "InstallExitCode.UnsupportedArch": "27",
  "InstallExitCode.StatusCheckFailed": "28",
  "InstallExitCode.NeedInsidersArch": "29",
  "InstallExitCode.ServerTransferFailed": "31",
  "InstallExitCode.ServerFailedToStart": "32",
  "InstallExitCode.NeedInsidersWindows": "33",
  "InstallExitCode.CreateInstallDirFailed": "34",
  "InstallExitCode.UnsupportedPlatform": "35",
  "InstallExitCode.ServerTerminatedCVE20201416": "36",
  "InstallExitCode.UnpackFailed": "37",
  "InstallExitCode.ChangeDirFailed": "38",
  "InstallUnpackCode.Success": "success",
  "InstallUnpackCode.Error": "error",
  "InstallUnpackCode.MissingFiles": "missingFiles",
  "uuid": "0becc5d355f8",
  "startMarker": "0becc5d355f8: running",
  "commitId": "384ff7382de624fb94dbaf6da11977bba1ecd427",
  "quality": "stable",
  "token": "11a11111-1aa1-11a1-1aa1-1aa11a1aaaa1",
  "vscodeAgentFolder": "$HOME/.vscode-server",
  "allowClientDownload": "1",
  "forceClientDownload": "0",
  "cliNameInArchive": "code",
  "ignoreWgetConfigFlag": " --no-config ",
  "ignoreCurlConfigFlag": " --disable ",
  "wgetTriesSegment": "--tries=1",
  "listenArgs": "--on-host=<IP_ADDRESS> --on-port",
  "getDownloadServerStartTrigger": "0becc5d355f8:trigger_server_download",
  "getDownloadServerEndTrigger": "0becc5d355f8:trigger_server_download_end",
  "getProgressDownloading": "0becc5d355f8%%1%%",
  "getProgressInstalling": "0becc5d355f8%%2%%"
}
[14:08:07.445] Install and start server if needed
[14:08:07.447] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53773 "bulldozer-wsl" sh
[14:08:07.447] Generated SSH command: 'type "C:\Users\cleme\AppData\Local\Temp\vscode-linux-multi-line-command-bulldozer-wsl-353602787.sh" | "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53773 "bulldozer-wsl" sh'
[14:08:07.448] Using connect timeout of 17 seconds
[14:08:07.448] Terminal shell path: C:\Windows\System32\cmd.exe
[14:08:07.682] > 0becc5d355f8: running
> Script executing under PID: 12576
> Found existing installation at /home/clement/.vscode-server...
> Starting VS Code CLI...
> printenv:
>     USER=clement
>     SSH_CLIENT=<IP_ADDRESS> 53774 22
>     SHLVL=0
>     HOME=/home/clement
>     _=/usr/bin/sh
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>     SHELL=/bin/bash
>     PWD=/home/clement
>     SSH_CONNECTION=<IP_ADDRESS> 53774 <IP_ADDRESS> 22
> Removing old logfile at /home/clement/.vscode-server/.cli.384ff7382de624fb94dbaf6da11977bba1ecd427.log
> Spawned remote CLI: 12594
> Waiting for server log...
> ]0;C:\Windows\System32\cmd.exe
[14:08:07.683] Got some output, clearing connection timeout
[14:08:07.696] > 0becc5d355f8: start
> listeningOn==<IP_ADDRESS>:40689==
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/tmp==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> serverStartTime==36==
> execServerToken==11a11111-1aa1-11a1-1aa1-1aa11a1aaaa1==
> platformDownloadPath==cli-alpine-x64==
> 0becc5d355f8: end
[14:08:07.696] Received install output:
listeningOn==<IP_ADDRESS>:40689==
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/tmp==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==36==
execServerToken==11a11111-1aa1-11a1-1aa1-1aa11a1aaaa1==
platformDownloadPath==cli-alpine-x64==

[14:08:07.696] Remote server is listening on port 40689
[14:08:07.696] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":40689},"osReleaseId":"ubuntu","arch":"x86_64","tmpDir":"/tmp","platform":"linux","execServerToken":"11a11111-1aa1-11a1-1aa1-1aa11a1aaaa1"},"serverStartTime":36,"installUnpackCode":""}
[14:08:07.698] Starting forwarding server. local port 53775 -> socksPort 53773 -> remotePort 40689
[14:08:07.698] Forwarding server listening on port 53775
[14:08:07.698] Waiting for ssh tunnel to be ready
[14:08:07.699] [Forwarding server port 53775] Got connection 0
[14:08:07.699] Tunneled port 40689 to local port 53775
[14:08:07.699] Resolved "ssh-remote+bulldozer-wsl" to "port 53775"
[14:08:07.701] Verified and reusing cached exec server for ssh-remote+bulldozer-wsl
[14:08:07.703] ------

[14:08:07.722] >
[14:08:08.514] [server] Aborted (core dumped)
[14:08:08.514] [server] Aborted (core dumped)
[14:08:42.743] ------

[14:08:42.743] SSH Resolver called for "ssh-remote+bulldozer-wsl", attempt 3, (Reconnection)
[14:08:42.744] SSH Resolver called for host: bulldozer-wsl
[14:08:42.744] Setting up SSH remote "bulldozer-wsl"
[14:08:42.746] Using commit id "384ff7382de624fb94dbaf6da11977bba1ecd427" and quality "stable" for server
[14:08:42.747] Script variables:
 {
  "InstallExitCode.24": "AlreadyInProgress",
  "InstallExitCode.25": "ServerDownloadFailed",
  "InstallExitCode.26": "NoDownloaderAvailable",
  "InstallExitCode.27": "UnsupportedArch",
  "InstallExitCode.28": "StatusCheckFailed",
  "InstallExitCode.29": "NeedInsidersArch",
  "InstallExitCode.30": "NoDownloaderAvailableForStatusCheck",
  "InstallExitCode.31": "ServerTransferFailed",
  "InstallExitCode.32": "ServerFailedToStart",
  "InstallExitCode.33": "NeedInsidersWindows",
  "InstallExitCode.34": "CreateInstallDirFailed",
  "InstallExitCode.35": "UnsupportedPlatform",
  "InstallExitCode.36": "ServerTerminatedCVE20201416",
  "InstallExitCode.37": "UnpackFailed",
  "InstallExitCode.38": "ChangeDirFailed",
  "InstallExitCode.AlreadyInProgress": "24",
  "InstallExitCode.ServerDownloadFailed": "25",
  "InstallExitCode.NoDownloaderAvailable": "26",
  "InstallExitCode.NoDownloaderAvailableForStatusCheck": "30",
  "InstallExitCode.UnsupportedArch": "27",
  "InstallExitCode.StatusCheckFailed": "28",
  "InstallExitCode.NeedInsidersArch": "29",
  "InstallExitCode.ServerTransferFailed": "31",
  "InstallExitCode.ServerFailedToStart": "32",
  "InstallExitCode.NeedInsidersWindows": "33",
  "InstallExitCode.CreateInstallDirFailed": "34",
  "InstallExitCode.UnsupportedPlatform": "35",
  "InstallExitCode.ServerTerminatedCVE20201416": "36",
  "InstallExitCode.UnpackFailed": "37",
  "InstallExitCode.ChangeDirFailed": "38",
  "InstallUnpackCode.Success": "success",
  "InstallUnpackCode.Error": "error",
  "InstallUnpackCode.MissingFiles": "missingFiles",
  "uuid": "796022f41fcb",
  "startMarker": "796022f41fcb: running",
  "commitId": "384ff7382de624fb94dbaf6da11977bba1ecd427",
  "quality": "stable",
  "token": "1111111a-11aa-1111-a1aa-111aaaa11a11",
  "vscodeAgentFolder": "$HOME/.vscode-server",
  "allowClientDownload": "1",
  "forceClientDownload": "0",
  "cliNameInArchive": "code",
  "ignoreWgetConfigFlag": " --no-config ",
  "ignoreCurlConfigFlag": " --disable ",
  "wgetTriesSegment": "--tries=1",
  "listenArgs": "--on-host=<IP_ADDRESS> --on-port",
  "getDownloadServerStartTrigger": "796022f41fcb:trigger_server_download",
  "getDownloadServerEndTrigger": "796022f41fcb:trigger_server_download_end",
  "getProgressDownloading": "796022f41fcb%%1%%",
  "getProgressInstalling": "796022f41fcb%%2%%"
}
[14:08:42.748] Install and start server if needed
[14:08:42.750] Running script with connection command: "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53797 "bulldozer-wsl" sh
[14:08:42.750] Generated SSH command: 'type "C:\Users\cleme\AppData\Local\Temp\vscode-linux-multi-line-command-bulldozer-wsl-260473757.sh" | "C:\Windows\System32\OpenSSH\ssh.exe" -T -D 53797 "bulldozer-wsl" sh'
[14:08:42.750] Using connect timeout of 17 seconds
[14:08:42.751] Terminal shell path: C:\Windows\System32\cmd.exe
[14:08:42.982] > 796022f41fcb: running
> Script executing under PID: 12785
> Found existing installation at /home/clement/.vscode-server...
> Starting VS Code CLI...
> printenv:
>     USER=clement
>     SSH_CLIENT=<IP_ADDRESS> 53798 22
>     SHLVL=0
>     HOME=/home/clement
>     _=/usr/bin/sh
>     PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>     SHELL=/bin/bash
>     PWD=/home/clement
>     SSH_CONNECTION=<IP_ADDRESS> 53798 <IP_ADDRESS> 22
> Removing old logfile at /home/clement/.vscode-server/.cli.384ff7382de624fb94dbaf6da11977bba1ecd427.log
> Spawned remote CLI: 12803
> Waiting for server log...
> ]0;C:\Windows\System32\cmd.exe
[14:08:42.983] Got some output, clearing connection timeout
[14:08:43.004] > 796022f41fcb: start
> listeningOn==<IP_ADDRESS>:43375==
> osReleaseId==ubuntu==
> arch==x86_64==
> vscodeArch==x64==
> bitness==64==
> tmpDir==/tmp==
> platform==linux==
> unpackResult====
> didLocalDownload==0==
> downloadTime====
> installTime====
> serverStartTime==34==
> execServerToken==1111111a-11aa-1111-a1aa-111aaaa11a11==
> platformDownloadPath==cli-alpine-x64==
> 796022f41fcb: end
[14:08:43.004] Received install output:
listeningOn==<IP_ADDRESS>:43375==
osReleaseId==ubuntu==
arch==x86_64==
vscodeArch==x64==
bitness==64==
tmpDir==/tmp==
platform==linux==
unpackResult====
didLocalDownload==0==
downloadTime====
installTime====
serverStartTime==34==
execServerToken==1111111a-11aa-1111-a1aa-111aaaa11a11==
platformDownloadPath==cli-alpine-x64==

[14:08:43.005] Remote server is listening on port 43375
[14:08:43.005] Parsed server configuration: {"serverConfiguration":{"remoteListeningOn":{"port":43375},"osReleaseId":"ubuntu","arch":"x86_64","tmpDir":"/tmp","platform":"linux","execServerToken":"1111111a-11aa-1111-a1aa-111aaaa11a11"},"serverStartTime":34,"installUnpackCode":""}
[14:08:43.006] Starting forwarding server. local port 53799 -> socksPort 53797 -> remotePort 43375
[14:08:43.006] Forwarding server listening on port 53799
[14:08:43.007] Waiting for ssh tunnel to be ready
[14:08:43.007] [Forwarding server port 53799] Got connection 0
[14:08:43.008] Tunneled port 43375 to local port 53799
[14:08:43.008] Resolved "ssh-remote+bulldozer-wsl" to "port 53799"
[14:08:43.009] Verified and reusing cached exec server for ssh-remote+bulldozer-wsl
[14:08:43.011] ------

[14:08:43.011] >

The (core dumped) part seems to indicate this is a native program's crash.

I tried a lot of things in the past few days ; notably installing and running code-server manually. I exclusively used the WebUI for my projects, for a few minutes. I had no extension installed and no specific configuration, I had removed $HOME/.vscode-server before installing it.
But it also crashed after a few minutes, and I saw in my terminal that the problem was caused by a heap memory issue. Some Node.js process ran out of memory and thus crashed.

Ok so I've finally found the beginning of an answer. After finding out the server produced log files under ~/.vscode-server/data/logs/<timestamp>/exthost1/remoteexthost.log, I found out that it contained the following error message:
Error: Unable to resolve your shell environment in a reasonable time. Please review your shell configuration.

After looking for a while, I read my /.bashrc and remembered it contained the following statements:
# ~/.bashrc: executed by bash(1) for non-login shells.
# see /usr/share/doc/bash/examples/startup-files (in the package bash-doc)
# for examples

# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

<command to run an interactive, blocking shell>
exit

# ...suite of the bashrc

Basically, I have a custom-made shell that I automatically run on opening bash (yes it's a very specific case). This works perfectly fine usually as in case of non-interactive session, this comman isn't triggered. So SSH commands for instance work fine, unlike if I set this specific shell as my login shell.
But, with VSCode It seems like the server is actually trying for some reason to create an interactive shell session, which means my custom shell is run, and times out because the server can't do what it wants to do.
Removing this call removes the problem entirely and VSCode works perfectly fine.
I was intrigued by the fact VSCode waited a long time (about 5 seconds) before activating extensions, and extensions took a long time to activate. I think the server is trying to do its stuff in the shell, and if can't it times out and switches to another method which in turn ends up crashing, maybe for a memory-related reason.
All is well that ends well!

Thanks for figuring this out, @ClementNerma !


Issue with "az aks get-credentials" command

When I try to use "az aks get-credentials" command I get the following error:
$ az aks get-credentials --resource-group "$RESOURCE_GROUP" --name "$AKS_CLUSTER_NAME" --admin
The HTTP method 'POST' is not supported.
It worked OK few days ago.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d75c3a8d-1187-bea1-a7d4-7ebba71c1790
Version Independent ID: 75b0c352-762e-16ae-5cc6-d807ffc1dc3f
Content: az aks
Content Source: latest/docs-ref-autogen/aks.yml
Service: container-service
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

I can not reproduce this on az cli 2.0.44, acs 2.3.0
What version are you running?

azure-cli (2.0.55)
acr (2.1.12)
acs (2.3.14)
advisor (2.0.0)
ams (0.3.2)
appservice (0.2.11)
backup (1.2.1)
batch (3.4.1)
batchai (0.4.6)
billing (0.2.0)
botservice (0.1.4)
cdn (0.2.0)
cloud (2.1.0)
cognitiveservices (0.2.4)
command-modules-nspkg (2.0.2)
configure (2.0.20)
consumption (0.4.2)
container (0.3.11)
core (2.0.55)
cosmosdb (0.2.7)
dla (0.2.3)
dls (0.1.7)
dms (0.1.1)
eventgrid (0.2.0)
eventhubs (0.3.2)
extension (0.2.3)
feedback (2.1.4)
find (0.2.13)
hdinsight (0.2.0)
interactive (0.4.1)
iot (0.3.4)
iotcentral (0.1.5)
keyvault (2.2.9)
lab (0.1.5)
maps (0.3.3)
monitor (0.2.8)
network (2.3.0)
nspkg (3.0.3)
policyinsights (0.1.0)
profile (2.1.2)
rdbms (0.3.5)
redis (0.3.2)
relay (0.1.2)
reservations (0.4.1)
resource (2.1.8)
role (2.3.0)
search (0.1.1)
security (0.1.0)
servicebus (0.3.2)
servicefabric (0.1.11)
signalr (1.0.0)
sql (2.1.7)
storage (2.3.0)
telemetry (1.0.0)
vm (2.2.12)
Same issue

I am also unable to reproduce this on latest build 2.0.77. I am going to close this given the age of the issue, but @akoval-jsp please give it a retry and if it still occurs comment and I can re-open.


Update Banner

See https://trello.com/c/P5xQ8cLZ/1190-update-banner-to-highlight-states-with-rising-case-numbers

Add 4 more states that have increasing hospitalizations on the recommendation of Igor.
Add text into the banner highlighting that cases are also rising.

I decided to keep the states to highlight in the explore hospitalization hard-coded because I want a manual curation step. Same with keeping the flat or rising vague to two-thirds.
We will have to update this, but I'm not worried because this is high visibility for the team at the moment.


Inline/full-function completions?

Hi, I'm wondering how we might go about getting multi-line, full-function completions from tabnine into emacs: https://www.tabnine.com/blog/introducing-inline-code-completions/
I've searched around and found no mention of it, and I suppose company might have a one-line limitation to its functionality though I don't know.
I've only just started using tabnine this month and decided to keep on with it for now, but would like to get more out of it of course.
Cheers for the elisp!

Would love a response on this as well. The copilot.el supports it so I don't see why it wouldn't be possible. If we could get this then I would give up copilot immediately.

try this:  @trevor-vincent @spacebat
https://github.com/shuxiao9058/tabnine


The O365 Connector does not include auditlogs from Teams & Skype for Business

All documentation indicates that you are able to select whatever O365 activity you want to send to Sentinel, but in my environment and all demo's I have seen I can only select Exchange & SharePoint and no data from Teams etc.
Can anyone please confirm if only Exchange & SharePoint are supported?
If thats the case, does anyone know when all O365 audit logs, in particular Teams, will be available?

Hi @JeroenMvS
Thats correct.  today we only get Ex+SP via the office connector.  We are working on native connectors for other services like teams.
In the short term, we have solutions you can use
https://github.com/Azure/Azure-Sentinel/tree/master/Playbooks/Get-O365Data - Logic App Playbook to get O365 Data.
https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/O365 Data - Azure Function to get O365 Data

Thanks for the quick and useful reply!


depthai: 2.15.5-1 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository depthai to 2.15.5-1:

upstream repository: https://github.com/luxonis/depthai-core.git
release repository: https://github.com/luxonis/depthai-core-release.git
distro file: galactic/distribution.yaml
bloom version: 0.11.1
previous version for package: 2.15.4-2

depthai
* EEPROM FIX
* Json fix (#478 <https://github.com/luxonis/depthai-core/issues/478>)
  * Fixed nlohmann json < v3.9.0 compat and toolchain generation
  * turn off clang format
  Co-authored-by: Martin Peterlin<EMAIL_ADDRESS>  Co-authored-by: TheMarpe<EMAIL_ADDRESS>* Empty-Commit
* Update package.xml
* Contributors: Sachin, Sachin Guruswamy

Holding for Galactic Sync


Add access to the token endpoint

If the fan or bridge has the power reset, the token is accessible for
10 minutes before the endpoint is locked. We can allow home assistant
to setup the device without the user having to use the app to find
the token by resetting the power to it.

Thanks Eugene.  Would you mind bumping the pypi as well?

Just released!
On Mon, Feb 22, 2021 at 9:04 AM J. Nick Koston<EMAIL_ADDRESS>wrote:

Thanks Eugene. Would you mind bumping the pypi as well?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/prystupa/bond-api/pull/7#issuecomment-783398400, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAG7RZQMJ2TXTCCZEONPXLDTAJQAFANCNFSM4X6LLEDQ
.

--
Thanks,
Eugene

Thanks!


Improve the [ambience] mod

We need to try to improve (or check if no improved made) the ambience mod with this tweaked mod :
Description
Ambiance Redo 0.5 released with code changes, smaller sound files thanks to Kilbith and some timing changes...
Link
https://github.com/tenplus1/ambience

@ObaniGemini @crabman77 @LeMagnesium @gravgun
Nobody interrested about this check/possible improved of the [ambience] mod ?

I will update it before the end of the day. It should just take a bit of time because we manipulated a lot of thigns in that mod.

Yes, i understand that point, take your time :)

@LeMagnesium Need to talk with you on IRC, please come :D

Ok, I will be clear.
This was re-written. So either I destroy everything and we use the new version with little addons like soundset, either we keep our old heavy version, which is the only way of maintaining such mechanisms as the music player. I cannot "improve" that mod, I can update it, or leave it as it's now. Period.
Maybe @tenplus1 would be helpful to say something if he has time to waste to read our old version's code but I doubt about that.

The goal is to use the new code wich is improved and Tidied.
So we nned to destroy everything and re-write/re-add all of our sounds into the mod ! (its a hug work... But it will be very interrest for server performances/ressources consumption)

We finally take the Tenplus1 version of this mod, it's lighter, we just need to re-add one music !
@ObaniGemini can you choose a music to add ?

One music ? 0.o
Hem... Let me think about it

Up

Up, need a name...

Ambivalent.ogg (Yes I know it's the first music of the mod)

You might want to get players to vote about that, but we don't have enough time for this. Ambivalent will be good then.

Ok, now assigned to @crabman77
The idea(from @crabman77) is to create a mod with just this music and a loop for playing it.
It's better because we don't touch the [ambience] mod is this case.

No, 20 30 minutes is a good time. And has most of the music of the mod are quite repetitive and calm, they fit easily has ambience musics.

Has been done some weeks ago


Determine unique values from data, not pandas.cat

Closes #235.
When using the meta-data of the pandas categorical dtype to determine
all unique values, it might create an encoding for values not present in
the data. Ignoring the meta-data and using the seen unique values
instead ensures proper behavior when a new value occurs in the test
data. It will be handled through the handle_unknown strategy
accordingly.

This PR is opened prematurely, sorry for that. I still need to add test the fix and add a unit test.
Unfortunately I encountered issues running the unit tests locally.
I tried to, but got this error while running tests (on Py3.6.10, with pandas 1.0.1 and 0.25.3):
Traceback (most recent call last):
  File "~\continuum\anaconda3\envs\ce\lib\multiprocessing\process.py", line 258, in _bootstrap
    self.run()
  File "~\continuum\anaconda3\envs\ce\lib\multiprocessing\process.py", line 93, in run
    self._target(*self._args, **self._kwargs)
  File "~\repositories\forks\categorical-encoding\category_encoders\hashing.py", line 203, in require_data
    data_part = self.hashing_trick(X_in=data_part, hashing_method=self.hash_method, N=self.n_components, cols=self.cols)
  File "~\repositories\forks\categorical-encoding\category_encoders\hashing.py", line 391, in hashing_trick
    X_cat.columns = new_cols
  File "~\continuum\anaconda3\envs\ce\lib\site-packages\pandas\core\generic.py", line 5287, in __setattr__
    return object.__setattr__(self, name, value)
  File "pandas\_libs\properties.pyx", line 67, in pandas._libs.properties.AxisProperty.__set__
  File "~\continuum\anaconda3\envs\ce\lib\site-packages\pandas\core\generic.py", line 661, in _set_axis
    self._data.set_axis(axis, labels)
  File "~\continuum\anaconda3\envs\ce\lib\site-packages\pandas\core\internals\managers.py", line 178, in set_axis
    f"Length mismatch: Expected axis has {old_len} elements, new "
ValueError: Length mismatch: Expected axis has 1 elements, new values have 8 elements

I am not sure if I am testing with wrong versions here, is there documentation on the developer requirements?
I installed:
nose
coverage
unittest2

The following old unit test fails:
    def test_pandas_categorical(self):
        X = pd.DataFrame({
            'Str': ['a', 'c', 'c', 'd'],
            'Categorical': pd.Categorical(list('bbea'), categories=['e', 'a', 'b'], ordered=True)
        })

        enc = encoders.OrdinalEncoder()
        out = enc.fit_transform(X)

        th.verify_numeric(out)
        self.assertEqual(3, out['Categorical'][0])
        self.assertEqual(3, out['Categorical'][1])
        self.assertEqual(1, out['Categorical'][2])
        self.assertEqual(2, out['Categorical'][3])

It is expecting the mapping to be based on the categorical meta-data.
Following the changes, the output actually follows the mapping b->1, e->2, a->3.
I can update the unit test accordingly. But really the exact mapping is not specified.
Should I rewrite the test instead to test that in the transformed categorical column:

the first two elements are mapped to the same number, and
the third and fourth element are both different from any other element in the output?

If the categorical attribute was defined with ordered=False, your proposed test would be right. But if someone bothered to define the order of the categorical values, I think we should honor it.
Can't we get a list which:

honors the ordering in .cat.categories.tolist()
and contains only values in .unique().tolist()

?

Yes we can. Follow up question then, when we see an ordered categorical variable defined with categories (in order) ['a' , 'b', 'c'], and as training data for the OrdinalEncoder only ['a', 'c']is passed. What mapping do we expect?  a=0, c=2 or a=0, c=1?

I would opt for a=0, c=1. Reasoning: If a user wants a=0, c=2, it is easy to do it without any library.

Done! Let me know if you see room for improvement.

Thank you, @PGijsbers. I have updated requirements.txt to make it easier for others to run the tests.


Build validation step for config files

Add RawConfigValidator which runs validation on the raw config files. This lays a foundation that makes it easy to add validation to the config files for jambo builds. Current validation includes checking that global_config.json exists, that "default" and "localeConfig" keys are present if local_config.json is present, and a check that there exists a localeConfig for every locale referenced by the page config file names. I also moved some utils to configutils.js and added enums to constants.js
TODO: Add jsdocs and unit tests
J=SLAP-590
TEST=manual, auto
Confirmed existing unit tests pass. Also manually modified a jambo site to observe the validation correctly pass or fail.

What do you all think of this validation architecture? Should I pull the RawConfigValidator out of SitesGenerator.generate() and put it in it in a SitesGenerator validation function which must pass before generate() will execute?

Tom brought up some old validation code which used a validation factory. Would that pattern be useful here?


Tests cases for wrong paths in schema parser

This code has been removed from the project. Now the schema parser job is done by Troy.


Remove unused maximum_passkeys_per_user; not the gem's concern

The :maximum_passkeys_per_user attribute is legacy code from the early experiments in the gem (see: https://github.com/ruby-passkeys/devise-passkeys/blob/main/lib/devise/passkeys/passkey_issuer.rb#L38).
And validations/limits on the number of passkeys that can be created should be handled by the app itself. This keeps the gem focused, reduces our maintenance overhead, and gives implementors control over the exact behavior

@tcannonfodder I can take this issue when I return home.

Created a pull request for this issue: https://github.com/ruby-passkeys/devise-passkeys/pull/41


[ko] Ready training section for vanilla Docsy

en PR https://github.com/kubernetes/website/pull/45870/files

/approve


Add mai/matic deprecation proposal.

The avalanche portion still fails testing with the CALLER_NOT_RISK_OR_POOL_ADMIN error, presumably because the executor should be the guardian on avalanche? Let us know what the right fix here would be in the new system.

please merge main, do forge install and re-run tests for avalanche

add snapshot links

Rebased on main, updated config and added the snapshot url, and regenerated. This fixed the issue with avalanche but now the optimism payload fails during the default test when trying to run the e2eTest at the end of the proposal. Appears to be error 59 or PRICE_ORACLE_SENTINEL_CHECK_FAILED - not sure exactly what's going on here, could use your help understanding what to do next.

Rebased on main, updated config and added the snapshot url, and regenerated. This fixed the issue with avalanche but now the optimism payload fails during the default test when trying to run the e2eTest at the end of the proposal. Appears to be error 59 or PRICE_ORACLE_SENTINEL_CHECK_FAILED - not sure exactly what's going on here, could use your help understanding what to do next.

Hey try updating the fork block to 111887045, it seems the network may have been down for the selected block.

Updated blocks and re-ran tests, that worked thanks!

Added deployed addresses for all chains.
To confirm, with gov 2.5 and beyond avalanche payloads are now executed by normal governance and not by a steward?

Updated blocks and included requested parameter changes, as detailed in the updated proposal description.

I tried to merge main and update for changes to the generator, but I got some errors when trying to regenerate with this config, is there a summary of changes to the config that I should apply here?

The payloads will also need to be re-deployed after further review

Added newly redeployed payload addresses

To limit governance fatigue and maximize the voting period during the weekday, we will push this AIP on chain on Monday Nov 20.


Persistence Layer - Common Data Service

Are Microsoft looking to add a Persistence Layer  for the  Common Data Service? If not yet could we get it added to the roadmap?
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/data-platform-intro

Thanks for the suggestion, @johngrace. Do you have particular scenarios in mind for this, or thoughts on how you would like to see the FHIR resources persisted to CDS? As normalized CDS entities?

As normalized CDS entities, as then you get all the benefits of the Power Platform.
Even if you just provided a working code example of here is an entity in CDS with 10 fields and show how the Persistence layer mapping details work, that would be a great help.

We're talking with the CDS team about this.

labeling won't fix for now.


artifacts: read predefined items

Hi @kazzmir
I wondered how itemdata.lbx is structured and fell somehow down a rabbit hole. Except the very last byte of each item (seems to be some sort of flag), I think if got everything with the help of the wiki 1, 2, 3.
I'm not sure how to proceed at this point:

The existing Artifact is missing some fields: Abilities, Mana Cost, Slot, Requirements. I've put it an own struct Item for now.
Where to put the function that reads the predefined items. I've put it in artifacts/items.go for now.
At which point to read the existing items.
How to integrate the spells.

This is very good thanks! I added you as a collaborator to the repo so now you can create a branch directly of my repo. Could you recreate this PR as a branch off my repo? That way it will be easier for us both to modify it.

https://github.com/kazzmir/master-of-magic/pull/160


📝 Add GitHub autogenerated release notes to releasing

Better to properly document this.
Also fixing the formatting for the pyproject.toml version change.

please also fix the typo in the subtitle Publishing to pipy to PyPI @hillairet

please also fix the typo in the subtitle Publishing to pipy to PyPI @hillairet

I fixed it


ARROW-6862: [Developer] Check pull request title

It checks pull request title periodically.
If a checked pull request doesn't start with ARROW-XXX, github-actions bot comments how to contribute.
See .github/workflows/pull_request/title_check.md for comment content.

Demo: https://github.com/kou/arrow/pull/6

What do you think about permitting PRs with [MINOR] or similar to not have a JIRA? It's not that much of a nuisance to have the bot commenting on minor PRs, though

(very cool by the way)

I think that indicating "no JIRA pull request" by title is fragile. We need to add a rule to our how to contribute guideline. We may forget the new rule.
In this change, the check doesn't comment a pull request that already has any comments:
https://github.com/apache/arrow/pull/5628/files#diff-3cbfc93b2e63cf9e17728203104d36a0R53
It means that we can prevent "open an issue on JIRA" comment by just commenting "This is a trivial fix." by ourselves like https://github.com/apache/arrow/pull/5604#pullrequestreview-298543538 .
I think that this is simpler and easy to understand the situation of the pull request.
What do you think about this approach?

I think that Travis CI failure is unrelated.

No more comments?
I'll merge this tomorrow.

I'll merge this.

Thanks @kou


Autorest Regen Preview to 3.0.0-alpha.20230714.6 by Josh Love from refs/pull/3553/head

Triggered from https://github.com/Azure/autorest.csharp/pull/3553

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.DataFactory


Jeep Uconnect Portal

Hello, would it be possible to add a Jeep version? It uses same Uconnect stuff just via the uconnect Jeep portal.
Would be great if i can modify the code to login to the jeep portal :-)
With kind Regads
Michael

Need credentials for add this
contact me in the iobroker forum https://forum.iobroker.net/user/tombox

I add blindly the jeep support in the github version but not tested with a vehicle

@TA2k Just to tell you that it works: I own 2 Jepp (Compass PHEV 2021 and Renegade PHEV 2022) and both of them fully work in iobroker. So I think, you could close this issue.