nginx 1.9.5 crashes with brotli enabled, when being curl'ed

Hi,
not sure, if this an upstream google/brotli issue, but since I'm using cloudflare's bundle I'll put it here first, maybe you guys have an idea what's going on:
I packaged nginx 1.9.5 for debian, with ngx_brotli_module-master.

nginx.conf

brotli on;
brotli_comp_level 6;
brotli_min_length 1000;

nginx sits behind nghttpx, a tls offloader and http2 proxy, communicating over http/1.1/no-tls with the nginx backend.
When opening a page with multiple png images (rand() generated) with chrome or firefox, everything's fine, using gzip though.
Opening the same page with curl, both HTTP/1.1 and HTTP2, nginx crashes immediately.

curl:

curl 7.45.0 (x86_64-pc-linux-gnu) libcurl/7.45.0 GnuTLS/3.3.18 zlib/1.2.8 libidn/1.32 libssh2/1.5.0 nghttp2/1.3.4 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets

gdb ./nginx /tmp/core:

Reading symbols from ./nginx...done.

warning: exec file is newer than core file.
[New LWP 16376]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `nginx: worker pr'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f9e2c55d8c0 in ngx_http_brotli_header_filter (r=0x7f9e2cb60820)
    at /home/daniel/code/nginx/nginx-1.9.5/debian/modules/ngx_brotli_module-master/ngx_http_brotli_filter_module.c:171
171         if (!ngx_strstrn(ae->value.data, "br", 1)) {
(gdb) bt full
#0  0x00007f9e2c55d8c0 in ngx_http_brotli_header_filter (r=0x7f9e2cb60820)
    at /home/daniel/code/nginx/nginx-1.9.5/debian/modules/ngx_brotli_module-master/ngx_http_brotli_filter_module.c:171
        h = 0x7f9e2cb60d88
        ae = 0x0
        ctx = 0x7f9e2cb60820
        conf = 0x7f9e2cb7e338
#1  0x00007f9e2c51cf32 in ngx_http_headers_filter (r=0x7f9e2cb60820) at src/http/modules/ngx_http_headers_filter_module.c:208
        value = {len = 134,
          data = 0x7f9e2cb7aefb "pin-sha256=\"sggymnso4MC+EGK/CjpEYzpHqNYgFoT+3AxbPG/06LM=\"; pin-sha256=\"qWRoFIB2OK8l7M4/nAKetrygsdoqgA5MgQpGKeKgVi0=\"; max-age=15768000"}
        i = 1
        safe_status = 1
        h = 0x7f9e2cb7afb0
        conf = 0x7f9e2cb7e378
#2  0x00007f9e2c51e11d in ngx_http_not_modified_header_filter (r=0x7f9e2cb60820) at src/http/modules/ngx_http_not_modified_filter_module.c:61
No locals.
#3  0x00007f9e2c4e0b3b in ngx_http_send_header (r=0x7f9e2cb60820) at src/http/ngx_http_core_module.c:1947
No locals.
#4  0x00007f9e2c50e6e4 in ngx_http_upstream_send_response (r=0x7f9e2cb60820, u=0x7f9e2cb65ce8) at src/http/ngx_http_upstream.c:2653
        tcp_nodelay = 32670
        n =<PHONE_NUMBER>41344
        rc =<PHONE_NUMBER>30168
        p = 0xc28
        c = 0x7f9e2cc300a0
        clcf = 0x7f9e2cbca4a8
#5  0x00007f9e2c50d53e in ngx_http_upstream_process_header (r=0x7f9e2cb60820, u=0x7f9e2cb65ce8) at src/http/ngx_http_upstream.c:2165
        n = 3112
        rc = 0
        c = 0x7f9e2cbca4a8
#6  0x00007f9e2c50b7fd in ngx_http_upstream_handler (ev=0x7f9e2cc00260) at src/http/ngx_http_upstream.c:1095
        c = 0x7f9e2cbca3d0
        r = 0x7f9e2cb60820
        u = 0x7f9e2cb65ce8
#7  0x00007f9e2c4c6d4a in ngx_event_process_posted (cycle=0x7f9e2cb46a20, posted=0x7f9e2c8517f0 <ngx_posted_events>) at src/event/ngx_event_posted.c:33
        q = 0x7f9e2cc002b0
        ev = 0x7f9e2cc00260
#8  0x00007f9e2c4c410d in ngx_process_events_and_timers (cycle=0x7f9e2cb46a20) at src/event/ngx_event.c:259
        flags = 3
        timer = 14400000
        delta = 1
#9  0x00007f9e2c4d32ac in ngx_worker_process_cycle (cycle=0x7f9e2cb46a20, data=0x1) at src/os/unix/ngx_process_cycle.c:753
        worker = 1
#10 0x00007f9e2c4cf231 in ngx_spawn_process (cycle=0x7f9e2cb46a20, proc=0x7f9e2c4d3192 <ngx_worker_process_cycle>, data=0x1,
    name=0x7f9e2c590403 "worker process", respawn=-3) at src/os/unix/ngx_process.c:198
        on = 1
        pid = 0
        s = 1
#11 0x00007f9e2c4d1dea in ngx_start_worker_processes (cycle=0x7f9e2cb46a20, n=2, type=-3) at src/os/unix/ngx_process_cycle.c:358
        i = 1
        ch = {command = 1, pid = 16375, slot = 0, fd = 3}
#12 0x00007f9e2c4d1337 in ngx_master_process_cycle (cycle=0x7f9e2cb46a20) at src/os/unix/ngx_process_cycle.c:130
        title = 0x7f9e2cbbfc8c "master process /usr/sbin/nginx"
        p = 0x7f9e2cbbfcaa ""
        size = 31
        i = 1
        n = 0
        sigio = 0
        set = {__val = {0 <repeats 16 times>}}
        itv = {it_interval = {tv_sec = 0, tv_usec = 0}, it_value = {tv_sec = 0, tv_usec = 0}}
        live = 0
        delay = 0
        ls = 0x0
        ccf = 0x7f9e2cb47b20
#13 0x00007f9e2c4947a5 in main (argc=1, argv=0x7ffec3c42b38) at src/core/nginx.c:415
        b = 0x7f9e00000001
        log = 0x7f9e2c84c7e0 <ngx_log>
        i = 47
        cycle = 0x7f9e2cb46a20
        init_cycle = {conf_ctx = 0x0, pool = 0x7f9e2cb46530, log = 0x7f9e2c84c7e0 <ngx_log>, new_log = {log_level = 0, file = 0x0, connection = 0,
            disk_full_time = 0, handler = 0x0, data = 0x0, writer = 0x0, wdata = 0x0, action = 0x0, next = 0x0}, log_use_stderr = 0, files = 0x0,
          free_connections = 0x0, free_connection_n = 0, reusable_connections_queue = {prev = 0x0, next = 0x0}, listening = {elts = 0x0, nelts = 0,
            size = 0, nalloc = 0, pool = 0x0}, paths = {elts = 0x0, nelts = 0, size = 0, nalloc = 0, pool = 0x0}, config_dump = {elts = 0x0, nelts = 0,
            size = 0, nalloc = 0, pool = 0x0}, open_files = {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0},
          shared_memory = {last = 0x0, part = {elts = 0x0, nelts = 0, next = 0x0}, size = 0, nalloc = 0, pool = 0x0}, connection_n = 0, files_n = 0,
          connections = 0x0, read_events = 0x0, write_events = 0x0, old_cycle = 0x0, conf_file = {len = 21, data = 0x7f9e2c58c25e "/etc/nginx/nginx.conf"},
          conf_param = {len = 0, data = 0x0}, conf_prefix = {len = 11, data = 0x7f9e2c58c25e "/etc/nginx/nginx.conf"}, prefix = {len = 17,
            data = 0x7f9e2c58c24c "/usr/share/nginx/"}, lock_file = {len = 0, data = 0x0}, hostname = {len = 0, data = 0x0}}
        cd = 0x7f9e2c46ded0
        ccf = 0x7f9e2cb47b20

What is the Accept-Encoding field you supply with curl?

Hi,
full output of curl -v, using HTTP/1.1:
*   Trying <IP_ADDRESS>...
* Connected to remote.host (<IP_ADDRESS>) port 443 (#0)
* found 180 certificates in /etc/ssl/certs/ca-certificates.crt
* found 724 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* SSL connection using TLS1.2 / ECDHE_RSA_AES_256_GCM_SHA384
*        server certificate verification OK
*        server certificate status verification SKIPPED
*        common name: remote.host (matched)
*        server certificate expiration date OK
*        server certificate activation date OK
*        certificate public key: RSA
*        certificate version: #3
*        [...]
*        compression: NULL
* ALPN, server accepted to use http/1.1
> GET /http2/ HTTP/1.1
> Host: remote.host
> User-Agent: curl/7.45.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Wed, 21 Oct 2015 13:53:38 GMT
< Content-Type: text/html; charset=utf-8
< Transfer-Encoding: chunked
< Vary: Accept-Encoding
< Vary: Accept-Encoding
< Public-Key-Pins: pin-sha256="sggymnso4MC+EGK/CjpEYzpHqNYgFoT+3AxbPG/06LM="; pin-sha256="qWRoFIB2OK8l7M4/nAKetrygsdoqgA5MgQpGKeKgVi0="; max-age=15768000
< Server: nghttpx nghttp2/1.3.4
< Via: 1.1 nghttpx
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
< X-XSS-Protection: 1; mode=block
< Strict-Transport-Security: max-age=31536000; preload
< Front-End-Https: on
< X-UA-Compatible: IE=Edge,chrome=1

Looking at the gdb output, #1, could this be an issue when using quotes in the http headers? (pin-sha256="")? Not sure why brotli would care for this, but not sure why this would be in the core either if it's not related?

I pushed a possible fix, can you check and tell me if it worked?

confirmed, no crash with both h1 and h2, thanks!

Thank you


Unable to install Eufy Security Addon

I can get as far as adding a repository, but unable to install.
21-09-18 22:40:33 INFO (SyncWorker_1) [supervisor.docker.interface] Downloading docker image bropat/eufy-security-ws with tag 0.4.3.
21-09-18 22:40:35 ERROR (SyncWorker_1) [supervisor.docker.interface] Can't install bropat/eufy-security-ws:0.4.3: 404 Client Error for http+docker://localhost/v1.41/images/create?tag=0.4.3&fromImage=bropat%2Feufy-security-ws: Not Found ("manifest for bropat/eufy-security-ws:0.4.3 not found: manifest unknown: manifest unknown")

This was an issue of my error, this version is not ready to install.
Please refresh your repositories and install old version 0.3.3

Feel free to resolve

Appreciate it, this version is able to be installed but I then run into an issue (that I don't think is your side).
2021-09-20 02:44:14.416  INFO Eufy Security server listening on port 3000  2021-09-20 02:44:16.846  ERROR Station T8510Q10202709C2 - Response code not ok  {   code: 20028,   msg: 'Failed to request.' } buffer.js:330   throw new ERR_INVALID_ARG_TYPE(   ^ TypeError [ERR_INVALID_ARG_TYPE] [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received undefined     at Function.from (buffer.js:330:9)     at stringWithLength (/usr/src/app/node_modules/eufy-security-client/build/p2p/utils.js:23:35)     at p2pDidToBuffer (/usr/src/app/node_modules/eufy-security-client/build/p2p/utils.js:32:18)     at Object.buildLookupWithKeyPayload (/usr/src/app/node_modules/eufy-security-client/build/p2p/utils.js:36:26)     at P2PClientProtocol.lookupByAddress (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:182:33)     at /usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:166:51     at Array.map (<anonymous>)     at P2PClientProtocol.lookup (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:166:29)     at Socket.<anonymous> (/usr/src/app/node_modules/eufy-security-client/build/p2p/session.js:241:26)     at Socket.onListening (dgram.js:246:7) {   code: 'ERR_INVALID_ARG_TYPE' }

i see the errors from at on but how this is happened? What is impact?

I’m also having issues getting this to work. Installed all the components and the getting and error with the integration. Below the LOG:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 293, in async_setup
result = await component.async_setup_entry(hass, self)  # type: ignore
File "/config/custom_components/eufy_security/init.py", line 44, in async_setup_entry
await coordinator.initialize_ws()
File "/config/custom_components/eufy_security/coordinator.py", line 94, in initialize_ws
raise Exception("Start Listening was not completed in timely manner")
Exception: Start Listening was not completed in timely manner

Please share your logs from eufy ws add on. Home assistant is not able to reach your docker over host:port combination

Please share your logs from eufy ws add on. Home assistant is not able to reach your docker over host:port combination

Here you go:
2021-09-20 06:57:13.635  INFO Eufy Security server listening on port 3000
2021-09-20 06:57:14.863  INFO No stations found.
2021-09-20 06:57:15.355  INFO No devices found.
2021-09-20 06:57:16.236  INFO Push notification connection successfully established
2021-09-20 06:57:21.344  INFO Push notification connection successfully established
2021-09-20 07:07:16.218  INFO No stations found.
2021-09-20 07:07:16.547  INFO No devices found.

There are no devices associated with this account, try to login with mobile app or restart your add on. You should share your devices with this account you are using in home assistant

There are no devices associated with this account, try to login with mobile app or restart your add on. You should share your devices with this account you are using in home assistant

Restarted the add on, still no luck. I have shared the device with the new account (granted admin access, not just view only) and can see the camera from this account (in the Eufy App). For some reason, it still shows as "no devices found". Any ideas?

can you double check your country in add on config? If not, please email me
credentials, I can test if you want.
On Mon, 20 Sept 2021 at 10:50, cjeri @.***> wrote:

There are no devices associated with this account, try to login with
mobile app or restart your add on. You should share your devices with this
account you are using in home assistant
Restarted the add on, still no luck. I have shared the device with the new
account (granted admin access, not just view only) and can see the camera
from this account (in the Eufy App). For some reason, it still shows as "no
devices found". Any ideas?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/eufy_security/issues/55#issuecomment-922739695,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUSN7REVG2WBVRVGOJ7T4DUC3YWLANCNFSM5EJ6DCRA
.

can you double check your country in add on config? If not, please email me credentials, I can test if you want.
…
On Mon, 20 Sept 2021 at 10:50, cjeri @.***> wrote: There are no devices associated with this account, try to login with mobile app or restart your add on. You should share your devices with this account you are using in home assistant Restarted the add on, still no luck. I have shared the device with the new account (granted admin access, not just view only) and can see the camera from this account (in the Eufy App). For some reason, it still shows as "no devices found". Any ideas? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#55 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACUSN7REVG2WBVRVGOJ7T4DUC3YWLANCNFSM5EJ6DCRA .

Country code was enabled correctly. I have managed to get it working :) Removed the permissions and re-shared the device as "view only" instead of "admin". It worked!
Thanks for your help.

let me update README with this information, admin permission is a must
then.
On Mon, 20 Sept 2021 at 11:31, cjeri @.***> wrote:

can you double check your country in add on config? If not, please email
me credentials, I can test if you want.
… <#m_9007909433985482102_>
On Mon, 20 Sept 2021 at 10:50, cjeri @.***> wrote: There are no devices
associated with this account, try to login with mobile app or restart your
add on. You should share your devices with this account you are using in
home assistant Restarted the add on, still no luck. I have shared the
device with the new account (granted admin access, not just view only) and
can see the camera from this account (in the Eufy App). For some reason, it
still shows as "no devices found". Any ideas? — You are receiving this
because you modified the open/close state. Reply to this email directly,
view it on GitHub <#55 (comment)
https://github.com/fuatakgun/eufy_security/issues/55#issuecomment-922739695>,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUSN7REVG2WBVRVGOJ7T4DUC3YWLANCNFSM5EJ6DCRA
.
Country code was enabled correctly. I have managed to get it working :)
Removed the permissions and re-shared the device as "view only" instead of
"admin". It worked!
Thanks for your help.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/fuatakgun/eufy_security/issues/55#issuecomment-922766668,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUSN7SRYKTZAZN2EBV36ITUC35OLANCNFSM5EJ6DCRA
.


Update Mesos docs/scripts/configs for new Sock Shop setup

blocked by https://github.com/microservices-demo/microservices-demo/issues/304


Hyprlock problem when turning on monitor

Regression?
No
Hyprlock Info and Version
Version: 0.4.1-1
 Hyprlock config
background {
    monitor =
    path = $HOME/Immagini/Arch-wallpapers/geology.png
}

input-field {
    monitor =
    size = 200, 50
    outline_thickness = 3
    dots_size = 0.33 # Scale of input-field height, 0.2 - 0.8
    dots_spacing = 0.15 # Scale of dots' absolute size, 0.0 - 1.0
    dots_center = true
    dots_rounding = -1 # -1 default circle, -2 follow input-field rounding
    outer_color = rgb(151515)
    inner_color = rgb(FFFFFF)
    font_color = rgb(10, 10, 10)
    fade_on_empty = true
    fade_timeout = 1000 # Milliseconds before fade_on_empty is triggered.
    placeholder_text = Input Password... # Text rendered in the input box when it's empty.
    hide_input = false
    rounding = -1 # -1 means complete rounding (circle/oval)
    check_color = rgb(204, 136, 34)
    fail_color = rgb(204, 34, 34) # if authentication failed, changes outer_color and fail message color
    fail_text = $FAIL ($ATTEMPTS) # can be set to empty
    fail_transition = 300 # transition time in ms between normal outer_color and fail_color
    capslock_color = -1
    numlock_color = -1
    bothlock_color = -1 # when both locks are active. -1 means don't change outer color (same for above)
    invert_numlock = false # change color if numlock is off
    swap_font_color = false # see below
    position = 0, -20
    halign = center
    valign = center
}

label {
    monitor =
    #clock
    text = cmd[update:1000] echo "$TIME"
    color = rgba(200, 200, 200, 1.0)
    font_size = 55
    font_family = Fira Semibold
    position = -100, 70
    halign = right
    valign = bottom
    shadow_passes = 5
    shadow_size = 10
}

label {
    monitor =
    text = $USER
    color = rgba(200, 200, 200, 1.0)
    font_size = 20
    font_family = Fira Semibold
    position = -100, 160
    halign = right
    valign = bottom
    shadow_passes = 5
    shadow_size = 10
}

image {
    monitor =
    path = $HOME/Immagini/Arch-wallpapers/4k-Arch-Dark-Background.png
    size = 280 # lesser side if not 1:1 ratio
    rounding = -1 # negative values mean circle
    border_size = 4
    border_color = rgb(221, 221, 221)
    rotate = 0 # degrees, counter-clockwise
    reload_time = -1 # seconds between reloading, 0 to reload with SIGUSR2
#    reload_cmd =  # command to get new path. if empty, old path will be used. don't run "follow" commands like tail -F
    position = 0, 200
    halign = center
    valign = center
}

Compositor Info and Version
 System/Version info
Hyprland, built from branch  at commit 9a09eac79b85c846e3a865a9078a3f8ff65a9259  (props: bump version to 0.42.0).
Date: Wed Aug 7 19:17:10 2024
Tag: v0.42.0, commits: 5069

flags: (if any)

System Information:
System name: Linux
Node name: arch
Release: 6.10.6-arch1-1
Version: #1 SMP PREEMPT_DYNAMIC Mon, 19 Aug 2024 17:02:39 +0000

GPU information:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1) (prog-if 00 [VGA controller])
NVRM version: NVIDIA UNIX x86_64 Kernel Module  555.58.02  Tue Jun 25 01:39:15 UTC 2024

os-release: NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://gitlab.archlinux.org/groups/archlinux/-/issues"
PRIVACY_POLICY_URL="https://terms.archlinux.org/docs/privacy-policy/"
LOGO=archlinux-logo

plugins:
  hyprkool by thrombe ver 0.7.1

Description
I'm on Arch using the Hyprlock screen lock. I have two problems with it: sometimes, when I unlock the screen, only the mouse movement works, and so I have to force shutdown because even the keyboard shortcuts don't work. It happened a couple of times, maybe when I start moving the mouse as soon as Hyprlock fades out instead of waiting 2/3 seconds, but I'm not sure.
The main problem is that, when I activate Hyprlock and I turn off the monitor, as soon as I turn it back on I see a full red screen, with only the mouse visible. I tried to add allow_session_lock_restore = true to misc in hyprland.conf, but it didn't solve it.
How to reproduce
Just install Hyprlock, activate it and turn off the monitor. Turn it on and the RSOD appears.
Crash reports, logs, images, videos
No response

I imagine is the same problem:
Used to be rare, but recently hyprlock is semi-freezing my workspaces after I type my password and press enter. The windows lose interactivity that can only be recovered by going to a TTY (ctrl+alt+f4) and back to the session (ctrl+alt+f2). Some things work, like the hover over waybar workspaces list, tooltips (some times), but can't click anything.
I'm on a RTX 2060 mobile with drivers 560.35.03 set to discreet GPU mode.

It seems that also, pontetially, can expose your password. Like it looks it did with mine with the Discord window that was open alone in a workspace.

sometimes, when I unlock the screen, only the mouse movement works, and so I have to force shutdown because even the keyboard shortcuts don't work. It happened a couple of times, maybe when I start moving the mouse as soon as Hyprlock fades out instead of waiting 2/3 seconds, but I'm not sure.

Dupe of #459

The main problem is that, when I activate Hyprlock and I turn off the monitor, as soon as I turn it back on I see a full red screen, with only the mouse visible. I tried to add allow_session_lock_restore = true to misc in hyprland.conf, but it didn't solve it.

Dupe of #434


fix clippy warnings in the workspace

Fixes for warnings discovered by clippy: cargo clippy -- -D warnings
Needed for  #76

Thanks for fixing these! Looks good!


images field coming as None (ArrayField)

After you fixed the accept for the ArrayField, the error you described here is occurring. It's like the images field is coming as None. And returns this error:
'NoneType' object has no attribute 'name'
I tested the lib in the previous version (django-image-uploader-widget==1.0.0) and it worked.

I checked further and discovered that the error occurs due to the lack of enctype="multipart/form-data" in the .
It would be good to include this guidance in the documentation :)

I checked further and discovered that the error occurs due to the lack of enctype="multipart/form-data" in the <form>
It would be good to include this guidance in the documentation :)
<form method="post" enctype="multipart/form-data">

This behaviour is descibed in django documentation.


ipfs: allow configuring ipfs daemon address

Fixes #1781
Depends on https://github.com/containerd/stargz-snapshotter/pull/1050
This commit adds --ipfs-address flag to nerdctl pull, nerdctl run, nerdctl compose.
This allows nerdctl to use an arbitrary IPFS API address instead of the local daemon, as proposed in #1781 .

Needs rebase


ApiGateway S3 Proxy

Hi,
I have created an api gateway as proxy to s3 to allow my client to upload items and download  items directly as specified here.
This is all specified in cloud formation resources as the serverless framework or plugins dont currently support this. Unfortunately at present it means this part of my architecture cannot be run and tested locally.
Is it feasible to add functionality to serverless-s3-local that would be able to route the resource based routes to local s3 somehow?
Below is my resource spec
Resources:
  s3ItemResource:
    DependsOn:
      - ApiGatewayRestApi
      - ApiGatewayResourceS3Proxy
    Type: AWS::ApiGateway::Resource
    Properties:
      ParentId:
        Ref: ApiGatewayResourceS3Proxy
      PathPart: "{key}"
      RestApiId:
        Ref: ApiGatewayRestApi
  s3ProxyOptionsMethod:
    Type: "AWS::ApiGateway::Method"
    Properties:
      ResourceId:
        Ref: s3ItemResource
      RestApiId:
        Ref: ApiGatewayRestApi # Reference API from serverless.yml using Serverless naming convention https://serverless.com/framework/docs/providers/aws/guide/resources/
      AuthorizationType: NONE
      HttpMethod: OPTIONS
      Integration:
        Type: MOCK
        IntegrationResponses:
          - ResponseParameters:
              method.response.header.Access-Control-Allow-Headers: "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'"
              method.response.header.Access-Control-Allow-Methods: "'GET,OPTIONS'"
              method.response.header.Access-Control-Allow-Origin: "'*'" # TODO : Can we restrict this further
            ResponseTemplates:
              application/json: ''
            StatusCode: '200'
        PassthroughBehavior: NEVER
        RequestTemplates:
          application/json: '{"statusCode": 200}'
      MethodResponses:
        - ResponseModels:
            application/json: Empty
          ResponseParameters:
            method.response.header.Access-Control-Allow-Headers: true
            method.response.header.Access-Control-Allow-Methods: true
            method.response.header.Access-Control-Allow-Origin: true
          StatusCode: '200'
  s3ProxyGetMethod:
    Type: "AWS::ApiGateway::Method"
    DependsOn: CustomAuthorizerApiGatewayAuthorizer # Reference function Custom Authorizer from serverless.yml using Serverless naming convention https://serverless.com/framework/docs/providers/aws/guide/resources/
    Properties:
      ApiKeyRequired: false
      AuthorizationType: CUSTOM
      AuthorizerId:
        Ref: CustomAuthorizerApiGatewayAuthorizer # Reference function Custom Authorizer from serverless.yml using Serverless naming convention https://serverless.com/framework/docs/providers/aws/guide/resources/
      HttpMethod: GET
      Integration:
        Credentials: !GetAtt ArtefactRole.Arn
        IntegrationHttpMethod: GET
        IntegrationResponses:
            - StatusCode: 200
              ResponseParameters:
                method.response.header.Content-Type: integration.response.header.Content-Type
                method.response.header.Content-Disposition: integration.response.header.Content-Disposition
                method.response.header.Access-Control-Allow-Headers: "'Content-Type,X-Amz-Date,Authorization,X-Api-Key,X-Amz-Security-Token'"
                method.response.header.Access-Control-Allow-Methods: "'GET,OPTIONS'"
                method.response.header.Access-Control-Allow-Origin: "'*'" # TODO : Can we restrict this further
            - StatusCode: 400
              SelectionPattern: "400"
              ResponseParameters:
                method.response.header.Content-Type: integration.response.header.Content-Type
                method.response.header.Content-Disposition: integration.response.header.Content-Disposition
            - StatusCode: 404
              SelectionPattern: "404"
              ResponseParameters:
                method.response.header.Content-Type: integration.response.header.Content-Type
                method.response.header.Content-Disposition: integration.response.header.Content-Disposition
            - StatusCode: 500
              SelectionPattern: '5\d{2}'
              ResponseParameters:
                method.response.header.Content-Type: integration.response.header.Content-Type
                method.response.header.Content-Disposition: integration.response.header.Content-Disposition
        PassthroughBehavior: WHEN_NO_MATCH
        RequestParameters:
          integration.request.header.Accept: method.request.header.Accept
          integration.request.path.key: method.request.path.key
        Type: AWS
        Uri: arn:aws:apigateway:${self:provider.region}:s3:path/${self:custom.bucketName}/{key}
      MethodResponses:
        - StatusCode: 200
          ResponseParameters:
            method.response.header.Content-Type: integration.response.header.Content-Type
            method.response.header.Content-Disposition: integration.response.header.Content-Disposition
            method.response.header.Access-Control-Allow-Headers: true
            method.response.header.Access-Control-Allow-Methods: true
            method.response.header.Access-Control-Allow-Origin: true
        - StatusCode: 400
          ResponseParameters:
            method.response.header.Content-Type: integration.response.header.Content-Type
            method.response.header.Content-Disposition: integration.response.header.Content-Disposition
        - StatusCode: 404
          ResponseParameters:
            method.response.header.Content-Type: integration.response.header.Content-Type
            method.response.header.Content-Disposition: integration.response.header.Content-Disposition
        - StatusCode: 500
          ResponseParameters:
            method.response.header.Content-Type: integration.response.header.Content-Type
            method.response.header.Content-Disposition: integration.response.header.Content-Disposition
      RequestParameters:
        method.request.header.Accept: false
        method.request.path.key: false
      ResourceId:
        Ref: s3ItemResource
      RestApiId:
        Ref: ApiGatewayRestApi # Reference API from serverless.yml using Serverless naming convention https://serverless.com/framework/docs/providers/aws/guide/resources/
  s3Deployment: # Need to redeploy after creating the resource otherwise the thing foesnt exist (may need to change the name of this deployment on each run using build epoch)
    Type: AWS::ApiGateway::Deployment
    DependsOn:
      - ApiGatewayDeployment${sls:instanceId}
      - s3ProxyGetMethod
    Properties:
      Description: Deploy with S3 Getter
      RestApiId:
        Ref: ApiGatewayRestApi
      StageName: ${self:custom.stage}

@ed-sparkes
Thanks for your comment. I think this is a feature of ApiGateway.


Update operation context for aggregation node

Description

Add batch run id for aggregate node, to guarantee don't touch collection table.
Add attribute to mark is aggregation or not. For aggregate node, we don't write LineSummary.
Delete _exec_aggregation_with_bulk_results method, used by nowhere.
Use exec_aggregation instead of _exec_aggregation for better code structure.

All Promptflow Contribution checklist:

[X] The pull request does not introduce [breaking changes].
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[X] I have read the contribution guidelines.
[ ] Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: suggested workflow.

General Guidelines and Best Practices

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

Description

Add batch run id for aggregate node, to guarantee don't touch collection table.
Add attribute to mark is aggregation or not. For aggregate node, we don't write LineSummary.
Delete _exec_aggregation_with_bulk_results method, used by nowhere.
Use exec_aggregation instead of _exec_aggregation for better code structure.

All Promptflow Contribution checklist:

[x]  The pull request does not introduce [breaking changes].
[ ]  CHANGELOG is updated for new features, bug fixes or other significant changes.
[x]  I have read the contribution guidelines.
[ ]  Create an issue and link to the pull request to get dedicated review from promptflow team. Learn more: suggested workflow.

General Guidelines and Best Practices

[x]  Title of the pull request is clear and informative.
[x]  There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x]  Pull request includes test coverage for the included changes.

Could you share more context of this PR. Why do we have to make this PR? What problem does it solve?


[python] DPI feature/arg in plot_importance

Demo:
https://gist.github.com/jkotra/65f5d97907fc5af38acb604035660136

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: jkotra sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@jkotra Thanks a lot for your contribution!
LGTM!
Is it useful to have this argument for other plotting functions? WDYT?

Yes, it is.
Added DPI option to plot_metric and  plot_tree.
I was not able to test how plot_split_value_histogram works, i get the following error:
AttributeError: 'Booster' object has no attribute 'get_split_value_histogram'

even unittest fails:
======================================================================
ERROR: test_plot_split_value_histogram (test_plotting.TestBasic)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/th4n0s/Documents/git/LightGBM/tests/python_package_test/test_plotting.py", line 66, in test_plot_split_value_histogram
    ax0 = lgb.plot_split_value_histogram(gbm0, 27)
AttributeError: module 'lightgbm' has no attribute 'plot_split_value_histogram'

----------------------------------------------------------------------

new(better) demo to show DPI effects:
https://gist.github.com/jkotra/ca4dee988e34666eca2c005a0e0b3403


Ya'll can use regular expressions to exclude stuff now.

Example
_config.yml:
exclude: /do_not_want/
Given:
do_not_want.html
do_not_want.jpg
When
I run jekyll
Then
do_not_want.jpg is not in the site
do_not_want.html is not in the site

Curious if you have feedback on this request. Would be highly valuable.

connected #109


Fail to pod update 'Tor'

If someone meet the same issue like this? The pod update always fail to install tor.

Are you doing this from within China? torproject.org is probably blocked there. Use a tunnel! Like Tor. :-) If you cannot get ahold of Tor Browser or a pure Tor binary, try to find a copy of Orbot, Siphon or stuff like ShadowSocks, VMess some VPN or other tunnelling software, which gets you through the "Great Firewall".

Are you doing this from within China? torproject.org is probably blocked there. Use a tunnel! Like Tor. :-) If you cannot get ahold of Tor Browser or a pure Tor binary, try to find a copy of Orbot, Siphon or stuff like ShadowSocks, VMess some VPN or other tunnelling software, which gets you through the "Great Firewall".

Thanks for your reply @tladesignz! I already connect to a tunnel and I can visit Google and Youtube in my location, that's why I'am here to post a issue.

Thanks for your reply @tladesignz! I already connect to a tunnel and I can visit Google and Youtube in my location, that's why I'am here to post a issue.

I see. Well, obviously something's blocking/redirecting you. Either at the exit or you have a bug in your network configuration. E.g. DNS still resolving internally and sending you somewhere else?
Anyway, I can assure you, this address is reachable from liberal countries.

Closing due to inactivity.


SR-4079: Make Enum CaseStmt introduce new type refinement context

TypeRefinementContext which restrict access to declarations based on availability attributes wasn't introduced for a switch case body with partially available enum element. So this pull request attempts to fix this. The main challenge was to get an original declaration of enum element used in switch, because type refinement context building happens before type resolution of case labels. My solution is to postpone building refinement context for CaseStmt until case labels fully type checked.

Resolves SR-4079.

Updated tests to incorporate changes

@CodaFi Hi! I would be grateful if you take a look

One other thing you could try is introducing a “lazy refinement context” that expands on demand, then assert that you’ve resolved the patterns.  But this is all getting kind of convoluted now...

One other thing you could try is introducing a “lazy refinement context” that expands on demand, then assert that you’ve resolved the patterns. But this is all getting kind of convoluted now...

I thought about making request for building refinement context, but at the moment I don't think I'm familiar with codebase enough to refactor refinement context building

@CodaFi So how do we proceed further?

I'm not comfortable taking this until we make pattern resolution more functional to accommodate out-of-band requests.  Unfortunately, the alternative is going to require a holistic fix like the laziness above, or integrating this with AST scopes.  Both of those are currently a bit pie-in-the-sky.
If you'd like to attack the pattern resolution problem first, we can discuss that in another SR or on the forums.  For now, we can close this or park it.  Your choice.

I don't know how we can adapt pattern resolution to solve this problem without introducing laziness to type refinement context building. Here we are interested in pattern_enum_element, the resolution of which requires subject type of switch stmt, therefore we need a help from type refinement context, which we can't build lazily for now. So I think we need to make type refinement context building lazy.

Can one of the admins verify this patch?

Please update the base branch to main by Oct 5th otherwise the pull request will be closed automatically.

How to change the base branch: (Link)
More detail about the branch update: (Link)


[ Feature ] Enter on keyboard inserts a new line

Current behavior is for the prompt to be submitted when I hit enter on my phone keyboard. I would like to have an option (or make it default) for the keyboard to enter a new line instead. This will help with sending code snippets in the prompt as you may normally do with chat GPT in the browser.

interesting that does not happen on my Android phone when I use the Android app. Which phone, model & operating system do you use? Maybe try another keyboard for your phone which does not hit "enter".
"Enter" is needed for PC as it makes typing and sending faster and shift+enter will be newline, but as said on my phone it does not send it directly via the Android keyboard.

will close this ticket now as there was no response so far, so I guess the issue is solved. If it still happens please let us know

Sorry, I had forgotten I added this report (and hoped my behavior was the common behavior).
I tried the latest version of Gboard (<IP_ADDRESS>4733254-release-arm64-v8a) and my phone's built-in Samsung Keyboard (<IP_ADDRESS>) and both submit when I hit the enter key.
Phone model: Galaxy S10e
Phone model number: SM-G970U
Android ver: 12


Corrections

I noticed that your draft for version 2 of derivative contains some imperfections.
Indeed the new feature style-inf-denom is not compatible with compact.
Therefore, I suggest some corrections to fix this compatibility.
To do so, I detect in __deriv_dv_preparation if you should use _denom or nothing for the command __deriv_insert_inf (which is used inside l__deriv_#2_style_var#4_tl) and I pass it down.

Version 1.3 has been released to CTAN today with the Compact feature.


Reasoning for selector duplications and usage.

I see a lot of duplication in the reducers like getEntities and then getBookEntities in the index reducer.
I'm curious what the main reasoning behind this is.
Also selectors like getSelected and getAll are only used in tests at the moment. Is there a plan to implement this in the future somewhere.

To be able to use the getEntities selector, it needs to be wrapped with a new selector getBookEntities. Check out the comments inside the code.

Every reducer module exports selector functions, however child reducers have no knowledge of the overall state tree. To make them useable, we need to make new selectors that wrap them.

The createSelector function from the reselect library creates very efficient selectors that are memoized and only recompute when arguments change. The created selectors can also be composed together to select different pieces of state.

getSelected is being used in the selected-book-page.ts file and the getAll selector was most likely used early on before it was refactored. So as far as using it in the future, I can't say at the moment, but it can probably be removed.


Quick Chat

I have the NullContinuanceToken error in Among Us So i tried the Option "All chat", but nothing change. What do i have to do?

Honestly, the new update seemed to have account issue and this is probably related to that, I'd just say wait it out and I'll reply to this again if I work it out.

Same problem

Still unaware of what causes this. Going to close the issue as it doesn't appear to be related to AUE.


'str' does not support the buffer interface

warning: Skipping personal/800a627bf4.ics: 'str' does not support the buffer interface
warning: This event will not be available in khal.
Unknown exception happened.
Traceback (most recent call last):
  File "/nix/store/2g8bi8cnmryx63dsrwnrrgjwhm4dvg1l-python3.4-khal-0.4.0/lib/python3.4/site-packages/khal/khalendar/khalendar.py", line 175, in _update_vevent
    self._dbtool.update(event.raw, href=href, etag=etag)
  File "/nix/store/2g8bi8cnmryx63dsrwnrrgjwhm4dvg1l-python3.4-khal-0.4.0/lib/python3.4/site-packages/khal/khalendar/backend.py", line 253, in update
    self._update_impl(vevent, href, etag)
  File "/nix/store/2g8bi8cnmryx63dsrwnrrgjwhm4dvg1l-python3.4-khal-0.4.0/lib/python3.4/site-packages/khal/khalendar/backend.py", line 280, in _update_impl
    dtstartend = aux.expand(vevent, self.locale['default_timezone'], href)
  File "/nix/store/2g8bi8cnmryx63dsrwnrrgjwhm4dvg1l-python3.4-khal-0.4.0/lib/python3.4/site-packages/khal/khalendar/aux.py", line 62, in expand
    rrule = dateutil.rrule.rrulestr(rrulestr, dtstart=vevent['DTSTART'].dt)
  File "/nix/store/kp28654ln61c2yvvppklb1sxv2dpplvb-python3.4-dateutil-2.2/lib/python3.4/site-packages/dateutil/rrule.py", line 1108, in __call__
    return self._parse_rfc(s, **kwargs)
  File "/nix/store/kp28654ln61c2yvvppklb1sxv2dpplvb-python3.4-dateutil-2.2/lib/python3.4/site-packages/dateutil/rrule.py", line 1025, in _parse_rfc
    (s.find(':') == -1 or s.startswith('RRULE:'))):
TypeError: 'str' does not support the buffer interface
warning: Skipping<EMAIL_ADDRESS>'str' does not support the buffer interface
warning: This event will not be available in khal.

I used vdirsyncer to sync with my owncloud. When calling khal a lot of these messages are printed and the displayed calendar remains empty.
I'm on khal version 0.4.0.
If you want to debug this further, I could create an owncloud account on my page for you, if you don't have a own owncloud!
Edit: Ah, btw... I'm on nixos... that's why the pathes in the traceback might look weird to you!

0.4.0 does not work with python3. Support was added after that release, and you'll need to use the latest version from git.


fixed jshint detected errors

I fixed some jshint detected error for improve it :+1:

Thanks, but it seems you also removed the type declaration that was recently added. Could you rebase?
Also, i'm not sure if we should remove the fallthrough. I believe was added for clarity..

Hi,
Yes right, i removed because i was missed type defined already. I mean here https://github.com/kvz/phpjs/blob/master/functions/var/serialize.js#L70-L71 i  was missed this comma. :smiley: i fixed it and improve for jshint.
About undefined also meaning default why we need it ?
case 'undefined':
defaut:

this is same thing, no different.
defaut:

Ops, maybe you mean this ?
case 'undefined':
  // Fall-through
  break; // i can add this and commit again?
defaut:

Oh ok, i will not touch Fall-through :smile:

Thanks!


Update hdf5, netcdf-c, netcdf-fortran etc (wait for netcdf-c-4.9.1?)

Please describe the package or library you would like to add to spack-stack.
hdf5 1.14.0 was released, we should test this version and switch if we can. See also https://github.com/NOAA-EMC/hpc-stack/issues/513.
For netCDF: netcdf-c is now at 4.9.0 (4.9.1 will be release shortly, should we wait for this one?), netcdf-fortran at 4.6.0, netcdf-cxx4 is at 4.3.1 (but I think we don't want to use netcdf-cxx4 anyway).
What applications will be using this package or library?
All
Is there already a package or library in spack-stack that provides this, or related, functionality?
Earlier versions are used everywhere.
Additional context
n/a
Will This Package be Needed in a NOAA Operational Application?
Those libraries have all been approved on WCOSS2.

Update: netcdf-c 4.9.1 currently doesn't compile with hdf5 1.14.0, but netcdf-c 4.9.0 does. This is the problem: https://github.com/Unidata/netcdf-c/issues/2614
Let's hold off on updating to 4.9.1 until the netcdf-c developers fixed this.

I don't think you should hold off.
The problem is with byterange code, and we never use it. In fact, we need to build with --disable-byterange anyway, so that disables the code with the bug.
Meanwhile 4.9.1 contains some important fixes for the new quantize and zstd compression features, which the UFS teams wants to try out, and which will also benefit anyone at NCAR who's trying to use these new compression features.

@AlexanderRichert-NOAA See here. I don't agree, we probably want to build with byterange as soon as the fix has been released (4.9.2) on all platforms EXCEPT the FISMA high systems where we turn it off, together with other things.

What failed? Did it crash? Or produce different results?

On Feb 13, 2023, at 7:15 AM, Hang-Lei-NOAA @.***> wrote:
Our tests based on the netcdf/4.9.1 with two options:
--disable-byterange
--disable-libxml2
The UFS failed.
On Mon, Feb 13, 2023 at 9:10 AM Dom Heinzeller @.***>
wrote:

@AlexanderRichert-NOAA https://github.com/AlexanderRichert-NOAA See
here. I don't agree, we probably want to build with byterange as soon as
the fix has been released (4.9.2) on all platforms EXCEPT the FISMA high
systems where we turn it off, together with other things.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428002636,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFH5EFCGFRHYF57H3GDWXI6FPANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428011236, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB5C2RO5H5X4X4BABBKSF5LWXI6Y5ANCNFSM6AAAAAAUD6O44I.
You are receiving this because you were assigned.

UFS model crashed with segmentation error  when using netcdf.
On Mon, Feb 13, 2023 at 9:55 AM Dom Heinzeller @.***>
wrote:

What failed? Did it crash? Or produce different results?

On Feb 13, 2023, at 7:15 AM, Hang-Lei-NOAA @.***> wrote:
Our tests based on the netcdf/4.9.1 with two options:
--disable-byterange
--disable-libxml2
The UFS failed.
On Mon, Feb 13, 2023 at 9:10 AM Dom Heinzeller @.***>
wrote:

@AlexanderRichert-NOAA https://github.com/AlexanderRichert-NOAA See
here. I don't agree, we probably want to build with byterange as soon
as
the fix has been released (4.9.2) on all platforms EXCEPT the FISMA
high
systems where we turn it off, together with other things.
—
Reply to this email directly, view it on GitHub
<
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428002636
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AKWSMFH5EFCGFRHYF57H3GDWXI6FPANCNFSM6AAAAAAUD6O44I

.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub <
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428011236>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/AB5C2RO5H5X4X4BABBKSF5LWXI6Y5ANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.

—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428075233,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFBT3YPLYOJNQZ7KBCTWXJDO3ANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.Message ID:
@.***>

Can we have more detail about the failure posted here?

@Edward Hartnett - NOAA Affiliate @.***> the failure
docs was kept on cactus. It has been switched to operation. I will redo a
test on Acorn for that.
On Mon, Feb 13, 2023 at 10:22 AM Dom Heinzeller @.***>
wrote:

In the meanwhile, I am going to revert netcdf-c back to 4.9.0 in the first
unified-dev PR (#455 https://github.com/NOAA-EMC/spack-stack/issues/455)
or I will never be able to complete that step.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428130195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFFR3BLMQTSW25BZFADWXJGT3ANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.Message ID:
@.***>

Failure provided by Pan Li on Acorn when using hdf 1.14.0 and netcdf 4.9.1:
@.***:~> vi
/lfs/h1/emc/ptmp/li.pan/FV3_RT/rt_192415/cpld_control_p8/err
fv3.exe<PHONE_NUMBER>42FCFB  MAIN__                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so<PHONE_NUMBER>2852BD  _libc_start_main     Unknown  Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       0000154AF9E6E2BD  _libc_start_main     Unknown  Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
xe<PHONE_NUMBER>DEE04A  ESMCI_FTableCallE         824
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       00001507FBB082BD  _libc_start_main     Unknown  Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       000014D0BAB752BD  __libc_start_main     Unknown  Unknown
On Mon, Feb 13, 2023 at 10:41 AM Hang Lei - NOAA Affiliate <
@.***> wrote:

@Edward Hartnett - NOAA Affiliate @.***> the failure
docs was kept on cactus. It has been switched to operation. I will redo a
test on Acorn for that.
On Mon, Feb 13, 2023 at 10:22 AM Dom Heinzeller @.***>
wrote:

In the meanwhile, I am going to revert netcdf-c back to 4.9.0 in the
first unified-dev PR (#455
https://github.com/NOAA-EMC/spack-stack/issues/455) or I will never be
able to complete that step.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428130195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFFR3BLMQTSW25BZFADWXJGT3ANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.Message ID:
@.***>

Update from cactus:
/lfs/h2/emc/ptmp/li.pan/FV3_RT/rt_219124
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line        Source
fv3.exe<PHONE_NUMBER>EF5BEA  Unknown               Unknown  Unknown
libpthread-2.31.s<PHONE_NUMBER>F148C0  Unknown               Unknown  Unknown
libnetcdff.so.7.1<PHONE_NUMBER>AA3C5F  netcdf_mp_nf90_in     Unknown  Unknown
fv3.exe<PHONE_NUMBER>9926D4  netcdf_io_mod_mp_        1511
netcdf_io.F90
fv3.exe<PHONE_NUMBER>990A84  netcdf_io_mod_mp_          85
netcdf_read_data.inc
fv3.exe<PHONE_NUMBER>9ABFAC  netcdf_io_mod_mp_          44
compressed_read.inc
fv3.exe<PHONE_NUMBER>A02F71  grid2_mod_mp_open         195
grid2.F90
fv3.exe<PHONE_NUMBER>A04276  grid2_mod_mp_open         253
grid2.F90
fv3.exe<PHONE_NUMBER>A0442D  grid2_mod_mp_grid         144
grid2.F90
fv3.exe<PHONE_NUMBER>933C83  fms_mod_mp_fms_in         428  fms.F90
fv3.exe<PHONE_NUMBER>313BD4  mom_cap_mod_mp_in         465
mom_cap.F90
fv3.exe<PHONE_NUMBER>DEA414  _ZN5ESMCI6FTable1        2167
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>DEE04A  ESMCI_FTableCallE         824
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>3D2F9B  _ZN5ESMCI3VMK5ent        1124
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>45DC7F  nuopc_driver_mp_l        2713
NUOPC_Driver.F90
fv3.exe<PHONE_NUMBER>484C2A  nuopc_driver_mp_i        1313
NUOPC_Driver.F90
fv3.exe<PHONE_NUMBER>48E0F3  nuopc_driver_mp_i         476
NUOPC_Driver.F90
fv3.exe<PHONE_NUMBER>DEA414  ZN5ESMCI6FTable1        2167
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>DEE04A  ESMCI_FTableCallE         824
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so<PHONE_NUMBER>9252BD  __libc_start_main     Unknown  Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
On Mon, Feb 13, 2023 at 11:25 AM Hang Lei - NOAA Affiliate <
@.***> wrote:

Failure provided by Pan Li on Acorn when using hdf 1.14.0 and netcdf 4.9.1:
@.***:~> vi
/lfs/h1/emc/ptmp/li.pan/FV3_RT/rt_192415/cpld_control_p8/err
fv3.exe<PHONE_NUMBER>42FCFB  MAIN__                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so<PHONE_NUMBER>2852BD  _libc_start_main     Unknown
Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       0000154AF9E6E2BD  _libc_start_main     Unknown
Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
xe<PHONE_NUMBER>DEE04A  ESMCI_FTableCallE         824
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       00001507FBB082BD  _libc_start_main     Unknown
Unknown
fv3.exe<PHONE_NUMBER>42EBAA  Unknown               Unknown  Unknown
C
fv3.exe<PHONE_NUMBER>3D2DAF  ZN5ESMCI3VMK5ent        2320
ESMCI_VMKernel.C
fv3.exe<PHONE_NUMBER>3BC859  ZN5ESMCI2VM5ente        1216
ESMCI_VM.C
fv3.exe<PHONE_NUMBER>DEB857  c_esmc_ftablecall         981
ESMCI_FTable.C
fv3.exe<PHONE_NUMBER>9D2700  esmf_compmod_mp_e        1223
ESMF_Comp.F90
fv3.exe<PHONE_NUMBER>7D3A96  esmf_gridcompmod        1412
ESMF_GridComp.F90
fv3.exe<PHONE_NUMBER>42FCFB  MAIN                    381  UFS.F90
fv3.exe<PHONE_NUMBER>42EC92  Unknown               Unknown  Unknown
libc-2.31.so       000014D0BAB752BD  __libc_start_main     Unknown
Unknown
On Mon, Feb 13, 2023 at 10:41 AM Hang Lei - NOAA Affiliate <
@.***> wrote:

@Edward Hartnett - NOAA Affiliate @.***> the failure
docs was kept on cactus. It has been switched to operation. I will redo a
test on Acorn for that.
On Mon, Feb 13, 2023 at 10:22 AM Dom Heinzeller @.***>
wrote:

In the meanwhile, I am going to revert netcdf-c back to 4.9.0 in the
first unified-dev PR (#455
https://github.com/NOAA-EMC/spack-stack/issues/455) or I will never
be able to complete that step.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-EMC/spack-stack/issues/453#issuecomment-1428130195,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWSMFFR3BLMQTSW25BZFADWXJGT3ANCNFSM6AAAAAAUD6O44I
.
You are receiving this because you were assigned.Message ID:
@.***>

Hello @Hang-Lei-NOAA !
I think you meant @edwardhartnett but thanks for making me aware of all the cool stuff NOAA is up to on GitHub! I was involved with getting the Canadian feds into using GitHub so am happy to see more like it.

This update was completed in #454


-k parameter not working on Ubuntu

When I use the command rdb -c json -k 'cluster_*' redis.rdb
I always get following error :
Traceback (most recent call last):
  File "/usr/local/bin/rdb", line 9, in <module>
    load_entry_point('rdbtools==0.1.10', 'console_scripts', 'rdb')()
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/cli/rdb.py", line 86, in main
    parser.parse(dump_file)
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 326, in parse
    self.parse_fd(open(filename, "rb"))
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 381, in parse_fd
    self.skip_object(f, data_type)
  File "/usr/local/lib/python2.7/dist-packages/rdbtools/parser.py", line 550, in skip_object
    skip_string(f)
NameError: global name 'skip_string' is not defined

If the -k parameter is removed it gives me all keys which is not what I want.
<EMAIL_ADDRESS>python -V
Python 2.7.6
<EMAIL_ADDRESS>pip install rdbtools
Requirement already satisfied (use --upgrade to upgrade): rdbtools in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied (use --upgrade to upgrade): redis in /usr/local/lib/python2.7/dist-packages (from rdbtools)
Cleaning up...

@VikramMoule Please try using the master code, it should have a fix to this as to #96 .
@oranagra is there an expected release to include this?

@amotzg Thanks. It works as expected with the master code.

i don't think we have any other release coming soon, so the question is if this fix alone justifies a release.

Is there some way to daylight this in lieu of a release? The only way I found this was by searching in the closed issues of this repo after a google search turned up a result that indicated that it might have been an issue (not a result that pointed to the issue--the page of the result didn't actually have the actual content, it was just one of those "github issue mirroring" sites so I got the clue to search here from that). Not exactly a straight line.

FYI @VikramMoule @aawilson the fix was released as version 0.1.11. sorry for the delay.


Update log4j to 2.17 to address CVE-2021-45105

Log4j version update because of CVE-2021-45105 vulnerability.
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-45105

Hi, I have signed the CLA. Would it be possible for a re-scan?

Done. Thanks


Assume the local HEAD is the PR's head commit

Resolves #266
Not really sure we need a changelog entry for that ¯_(ツ)_/¯

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

  Generated by :no_entry_sign: danger

I think it's worth a CHANGELOG because it's a pretty big change in behavior, maybe something like
- Relies on the current git HEAD, instead of pulling a merge branch from GitHub - justMaku ?

Right! Updated :)

aye


Fix layout for anchor links

In order to display the page correctly, when visiting an anchor link, negative margin including a positiv padding must be added to the stylesheet for the link_owner class in order to skip the header of the page.
Example:
margin-top: -80px;
padding-top: 90px;

This example will add a distance delta of 10px above the heading element. This will have an impact on the distance of the heading element to the header element when visiting the page using an anchor link as well as distances between headings and other siblings.
You will be able to actually see the heading this way. Currently it is behind the header of the page.
Example link: https://themes.gohugo.io//theme/compose/docs/getting-started/shortcodes/#column

@mk0, thanks for contributing, I will have a look at this and #14


@import handling should use the loader defined in the webpack config

I am currently developing a sass loader which uses the original ruby sass compiler. When the css-loader processes the output and handles @import directives currently calls the sass loader again (which fails, since ruby sass can't seem to handle normal css files properly).
I think it would be better to call the loader defined in the webpack config for that file pattern instead.

@ddelbondio is your ruby-sass loader working and do you plan to release it?

@geddski yes it is working. I cleaned it up a bit and published it at https://github.com/ddelbondio/ruby-sass-loader / https://www.npmjs.com/package/ruby-sass-loader
Let me know if you have any issues with it


Fix regressions in FormReader / FileBufferingReadStream.

#605 @davidfowl @muratg @benaadams @BrennanConroy
The recent perf changes caused two regressions in the FileBufferingReadStream used by form reader. The one reported in #605 is that most of the data buffered in memory gets discarded when transitioning to the file buffer. This happened because Write was accidentally given the wrong length when I cleaned up some of @benaadams's code.
The other regression was that the constructor only rented buffers if the in-memory threshold was less than 1mb, but Read always assumed it was using rented buffers. This would have caused ArgumentNullExceptions trying to use an uninitialized buffer. The fix is to rent a buffer when needed and do a manual CopyTo loop.
Compare with https://github.com/aspnet/HttpAbstractions/commit/bd60507dcd317f2c1f42da37afd9dbc928f50928#diff-6bee66e850efacd8fe96daae334fa1c5R192

Looks reasonable :shipit:


Presentations of BHNT#79?

BHNT#80 will start soon, but the BHNT#79 hacks aren't yet on the website.
I remember that those were collected in the pad at: https://pad.systemli.org/p/bhnt079
However, that one has been emptied in the meantime.

Does anyone else have a backup/copy of this?
Alternatively, what about the list of hacks from the voting?

started a PR here: #302


Replace cl.hpp with cl2.hpp

[x] Add OpenCL-CLHPP repository as external project and use cl2.hpp header instead of current cl.hpp header.
[x] Provide a cmake build option USE_SYSTEM_CL2HPP to use headers installed on the system. By default this value shall be OFF which results in download and generation of the headers from OpenCL-CLHPP repository.

This change is

I have built the changes on the following compiler configuration
jesse:build arrayfire$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/c++ --version
Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.5.0
Thread model: posix
jesse:build arrayfire$ /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc --version
Apple LLVM version 6.1.0 (clang-602.0.49) (based on LLVM 3.6.0svn)
Target: x86_64-apple-darwin14.5.0
Thread model: posix

ProductName:	Mac OS X
ProductVersion:	10.10.5

and the changes built successfully.

@kknox looks like travis is still on Mavericks which seems to be the cause of the failure.
We can hook up clSparse into arrayfire's jenkins for now if you are interested.

This PR is still missing option to use cl2.hpp present on the system. Once this is done, this can remove the need for #138 and resolve #162

I have added option to use cl2.hpp present on the system.

Reviewed 18 of 24 files at r1, 7 of 7 files at r2.
Review status: all files reviewed at latest revision, 4 unresolved discussions, some commit checks failed.

.gitignore, line 34 [r2] (raw file):

# temp build file locations
build/

This is mostly a pet peeve of mine, but I do not like any generated files to be mixed in with the source, even if it's whitelisted in the .gitignore.  I feel these are the types of exceptions that belong in a fork, not in upstream.  I can't find below where you generate code in 'builld/', so this may be moot.  Can you revert this change?

samples/sample-axpy.cpp, line 28 [r2] (raw file):

#define CL_HPP_MINIMUM_OPENCL_VERSION BUILD_CLVERSION
#define CL_HPP_TARGET_OPENCL_VERSION BUILD_CLVERSION
#include <CL/cl2.hpp>

I really like that the system specific pre-processor guards can be eliminated here.  Thanks for this simplification!

src/clsparseTimer/CMakeLists.txt, line 65 [r2] (raw file):

if(${UNIX})
    ADD_DEFINITIONS(-fvisibility=hidden)
endif(${UNIX})

Why is this necessary?  I would prefer to use the standard add_compiler_export_flags?   I see above in a comment that you say it's deprecated?  Can you provide material that I can read?

src/library/CMakeLists.txt, line 254 [r2] (raw file):

if(${UNIX})
    ADD_DEFINITIONS(-fvisibility=hidden)
endif(${UNIX})

Why is this necessary?  I would prefer to use the standard add_compiler_export_flags?

Comments from Reviewable

According to this travis page, we can opt-in to a more recent version of mac osx.  Can you update the .travis.yml file on your next commit to include osx_image: xcode8

This is mostly a pet peeve of mine, but I do not like any generated files to be mixed in with the source, even if it's whitelisted in the .gitignore. I feel these are the types of exceptions that belong in a fork, not in upstream. I can't find below where you generate code in 'builld/', so this may be moot. Can you revert this change?

build is not autogenerated, but it is an ever present directory sitting at the top of the repo where we build the project. This is the canonical way to build a cmake project in Linux.

Why is this necessary? I would prefer to use the standard add_compiler_export_flags? I see above in a comment that you say it's deprecated? Can you provide material that I can read?

@kknox On latest versions of CMake, you get the following warning when you use that function:

The add_compiler_export_flags function is obsolete.  Use the
CXX_VISIBILITY_PRESET and VISIBILITY_INLINES_HIDDEN target properties
instead.

Now I am not sure when these options were added, but v3.0.2 seems to definitely have those options. If you are willing to change the minimum CMake requirement to 3.0, this can be fixed in the proper manner.

You can see that the documentation mention that function is obsolete at the end of this page:
https://cmake.org/cmake/help/v3.0/module/GenerateExportHeader.html

This is the canonical way to build a cmake project in Linux.

I'm not advocating that you change your build layout, and I don't feel like you are doing anything wrong, but it's a specific requirement of your build environment and doesn't need to live upstream.  I advocate its up to the user to decide where to compile, and this change encourages otherwise.

... this can be fixed in the proper manner.  You can see that the documentation mention that function is obsolete at the end of this page.

Thank you for the heads up.  I like your suggestion with regard to target properties, so could you refactor the code into:
set_target_properties(target PROPERTIES CXX_VISIBILITY_PRESET hidden)
set_target_properties(target PROPERTIES VISIBILITY_INLINES_HIDDEN ON )

My understanding is that this will do the right things on windows, and should also work for cmake 2.8.12.   I think we would be good all around.

@kknox All platform builds pass now.

@9prady9 can you rebase the PR to have fewer commits ?

This may not matter if @kknox wants to squash the commits while merging.

This looks great now; if you want to rebase, go ahead.  If you are find with a merge/squash, i'll do that at the end of my business day.
Thank you for your contribution

Reviewed 4 of 4 files at r3.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable

@kknox pradeep is working on Indian time. I think it's fine if you merge + squash it :)


feat(ingestion): Mode retry wait logic to avoid hitting Mode API rate limit

Implement exponential backoff retry logic when accessing Mode API to avoid HTTP error 429: "Too many API request".
See Datahub Mode connector Config Details on how to customize these settings.
Checklist

[X] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[X] Docs related to the changes have been added/updated (if applicable)

Hey, do you know if we need to do any further optimizations here? We are getting this error repeatedly for updating around 10k datasets every 15 minutes for a 3 node t3.small.search OpenSearch cluster
Our version already have this fix, still not helping


weird background issue with ayu dark

As you can see from the two images, there is a different background color on the right of the editor and at the bottom under the last line of code. I have tried to reproduce this issue but failed doing so as it only happens with the dark version of this theme, mirage does not have this issue but I would like to switch to the dark one.
VSCode 1.31.1

I got same issue with Mirage :( But Dark version work as well

This was an issue with vscode itself and has since been fixed as noted in the issue mentioning this one


Warranty

Good Morning.
Has anyone tried on a laptop and sent it to the warranty?
What was the answer?
tks

In most cases they will repair it. It looks like a motherboard shorted out. Just don't mention that it was the result of usb kill or it is considered negligent/abuse/accidental damage.

Yea they will change the system board, if wait for a few weeks and do it again, then on the 3rd time your items is regarded as a 'lemon' as will need to be replaced by a brand new similar model or get your full money back.
I have done this for TVs, Mobiles, Laptops, computers, etc


[WIP] Support constant spread-list-member within the keys of a table

Purpose
As mentioned in the spec, structural constructors are allowed as long as their subexpressions are also constant. However, as mentioned in https://github.com/ballerina-platform/ballerina-lang/issues/41979, an invalid diagnostic is produced when a spread-list-member is within such constructors.
Related to: https://github.com/ballerina-platform/ballerina-lang/pull/41992
Fixes https://github.com/ballerina-platform/ballerina-lang/issues/41979
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[x] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Need to revisit the design again. Till then we will be closing this PR.


CAD improvements and heatset guide

CAD Improvements:

Fix collisions for S2
Fix lid (connection, spacing, collisions)
Include bracket development file
Strengthen brace and increase functionality

#127


Printable concepts to simplify SFINAE

:notebook_with_decorative_cover: Description

Problem:

There are several variable templates with cumbersome metaprogramming
in defining them.
There is some verbose SFINAE for constraining various function
templates around the ideas of being printable.

Solution:

Add various concepts like printable and apply them to simplify the
metaprogramming and SFINAE.

:memo: Checklist

[X] All user-facing changes have changelog entries.
[X] The changes are reflected on docs.tenzir.com/vast, if necessary.
[X] The PR description contains instructions for the reviewer, if necessary.

:dart: Review Instructions

File-by-file. The first commit is just a rename of printer to  printer_base.

ping @mavam @tobim -- pipeline is passing

Strange compilation error. It works with GCC11, but both GCC10 and clang fail. The curious part is that the fallback formatter that uses the stringification inspector hits the one for printable further down, which should not be the case. I wonder how your changes could have triggered this?

Strange compilation error. It works with GCC11, but both GCC10 and clang fail. The curious part is that the fallback formatter that uses the stringification inspector hits the one for printable further down, which should not be the case. I wonder how your changes could have triggered this?

I'm not sure yet...I don't fully understand the issue. With https://github.com/tenzir/vast/pull/1818/commits/88aaa58814aec7ed554fe46e7e8671c20af32c1d, it was passing fine on Clang and we were just ignoring the warning on GCC. I think it's a GCC bug in eagerly evaluating the body of a concept of the is_printable concept or something.

With that being said, would you be opposed to disabling the warning for now on GCC? All tests passed still...I plan on trying to simplify the logger_formatters.hpp to simplify the metaprogramming which may fix this bug.

i would like to verify that the formatting is still correct for the that path. Can you check that the output of this added line is unchanged:
diff --git a/libvast/src/system/accountant.cpp b/libvast/src/system/accountant.cpp
index 53d138086..da1538b84 100644
--- a/libvast/src/system/accountant.cpp
+++ b/libvast/src/system/accountant.cpp
@@ -292,6 +292,7 @@ accountant(accountant_actor::stateful_pointer<accountant_state> self,
   self->delayed_send(self, overview_delay, atom::telemetry_v);
   return {
     [self](atom::announce, const std::string& name) {
+      VAST_INFO("{} got announce from {}", self, self->current_sender()->address());
       auto& st = *self->state;
       st.actor_map[self->current_sender()->id()] = name;
       self->monitor(self->current_sender());

VAST_INFO("{} got announce from {}", self, self->current_sender()->address());

Sure. Can you elaborate a bit more on how to verify that the output of your added line is unchanged? Is there a test I can run, or something else?

VAST_INFO("{} got announce from {}", self, self->current_sender()->address());

Sure. Can you elaborate a bit more on how to verify that the output of your added line is unchanged? Is there a test I can run, or something else?

Running vast --enable-metrics start should do the trick.

VAST_INFO("{} got announce from {}", self, self->current_sender()->address());

Sure. Can you elaborate a bit more on how to verify that the output of your added line is unchanged? Is there a test I can run, or something else?

Running vast --enable-metrics start should do the trick.

Here is the output which looks the same.  On top of tree with your added log line, using llvm 12.0.1, the output is:
./vast --enable-metrics start
[09:27:31.669] loaded configuration file: "/Users/joe/dev_local/vast/build/etc/vast/vast.yaml"
[09:27:32.176] accountant got announce from 10@7817E89FEDA8EF0185063BBD8B5EF70D97BBE700#6723
[09:27:32.177] accountant got announce from 11@7817E89FEDA8EF0185063BBD8B5EF70D97BBE700#6723
[09:27:32.178] accountant got announce from 14@7817E89FEDA8EF0185063BBD8B5EF70D97BBE700#6723
[09:27:32.178] importer adds accountant source
[09:27:32.181] VAST node is listening on localhost:42000

On my branch when using the dev Docker file with gcc10, the output is similar:
[13:33:18.291] loaded configuration file: "/opt/tenzir/vast/etc/vast/vast.yaml"
[13:33:18.328] accountant got announce from 10@C0388D7211856698956FF8542CE446EBABE7A100#1
[13:33:18.329] accountant got announce from 11@C0388D7211856698956FF8542CE446EBABE7A100#1
[13:33:18.330] accountant got announce from 24@C0388D7211856698956FF8542CE446EBABE7A100#1
[13:33:18.331] importer adds accountant source
[13:33:18.336] VAST node is listening on localhost:42000

Given this, I think we're fine just disabling the warning for GCC for now and moving on. What do you think? Does this look right to you?

Maybe there is a fix for the fallback formatters so that the warning can be enabled again?
I think in the long run we should turn all the alternatives in vast::data into strong typedefs and implement fmt formatters for them to avoid these issues.


RxTx delay on echo (?)

Hi there,
I'm implementing an iot project and I'm facing something that to me seems a little strange, I'm using RxTx protocol with netty and an arduino, and implementing and echo server-client data takes to long to get received by netty on the channelRead0 method.
I know it is slow because I tried the same in python with pySerial and got around 23 messages per second, but in java with netty I can only get 10 to 12 at max.
Doesn't anyone have any idea of what might be going on?

do you call Channel.write*(...) from outside the EventLoop ?

In a nutshell this is what I have:
private ChannelFuture startConnectionRxTx(RxtxDeviceAddress rxtxDeviceAddress) {
        Bootstrap bootstrap = new Bootstrap();
        String INITIAL_MESSAGE = "0204000006\n";
        bootstrap
                .group(new OioEventLoopGroup())
                .channel(RxtxChannel.class)
                .handler(new ChannelInitializer<RxtxChannel>() {
                    @Override
                    protected void initChannel(RxtxChannel ch) throws Exception {
                        ch.config()
                                .setBaudrate(115200)
                                .setParitybit(RxtxChannelConfig.Paritybit.NONE)
                                .setStopbits(RxtxChannelConfig.Stopbits.STOPBITS_1)
                                .setDatabits(RxtxChannelConfig.Databits.DATABITS_8)
                                .setWaitTimeMillis(0)
                                .setReadTimeout(1);

                        ch.pipeline()
                                .addLast(
                                        new LineBasedFrameDecoder(32768),
                                        new StringEncoder(),
                                        new StringDecoder(),
                                        new SimpleChannelInboundHandler<String>(){
                                            @Override
                                            public void channelActive(ChannelHandlerContext ctx) {
                                                ctx.writeAndFlush(INITIAL_MESSAGE);
                                            }

                                            @Override
                                            protected void channelRead0(ChannelHandlerContext ctx, String msg) throws Exception {
                                                ctx.writeAndFlush(msg);
                                            }
                                        }
                                );
                    }
                });
        ChannelFuture channelFuture = bootstrap.connect(rxtxDeviceAddress);
        channelFuture.syncUninterruptibly();
        return channelFuture;
    }


Blood Boil on Death Runes

Blood Boiling on Blood runes is not a good idea since it orphans your frost runes as unholy. Therefore we want to track how many times a Blood Boil was done on blood runes.
It's probably worth creating some class that easily tracks what runes were used for an ability (if it already doesn't exist).
This same functionality would be useful for the Festering Strike issue.

On second thought, I feel like this is less useful, using them on death runes is probably better but I don't think this is worth considering at this time


Add logging configuration options and other misc logging improvements

gin access logs now use logrus, and generally don't output non-JSON in prod environments
Fixes #40
Sample output for env = prod
{
  "file": "/Users/fherzfeld/src/github.com/TBD54566975/did-dht-method/impl/cmd/main.go:43",
  "func": "main.main",
  "level": "info",
  "msg": "starting up",
  "time": "2024-01-23T13:15:41-08:00"
}
{
  "file": "/Users/finn/src/github.com/TBD54566975/did-dht-method/impl/cmd/main.go:58",
  "func": "main.run",
  "level": "info",
  "msg": "loading config from file",
  "path": "config/config.toml",
  "time": "2024-01-23T13:15:41-08:00"
}
{
  "environment": "prod",
  "file": "/Users/finn/src/github.com/TBD54566975/did-dht-method/impl/pkg/server/server.go:84",
  "func": "github.com/TBD54566975/did-dht-method/pkg/server.setupHandler",
  "level": "info",
  "msg": "configuring server for environment",
  "time": "2024-01-23T13:15:41-08:00"
}
{
  "file": "/Users/finn/src/github.com/TBD54566975/did-dht-method/impl/cmd/main.go:87",
  "func": "main.run.func2",
  "level": "info",
  "listen_address": "<IP_ADDRESS>:8305",
  "msg": "starting listener",
  "time": "2024-01-23T13:15:41-08:00"
}
{
  "clientIP": "::1",
  "dataLength": 16,
  "file": "/Users/finn/go/pkg/mod/github.com/toorop/gin-logrus@v0.0.0-20210225092905-2c785434f26f/logger.go:80",
  "func": "github.com/toorop/gin-logrus.Logger.func1",
  "hostname": "finn-mac.local",
  "latency": 1,
  "level": "info",
  "method": "GET",
  "msg": "::1 - finn-mac.local [23/Jan/2024:13:15:44 -0800] \"GET /health\" 200 16 \"\" \"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36\" (1ms)",
  "path": "/health",
  "referer": "",
  "statusCode": 200,
  "time": "2024-01-23T13:15:44-08:00",
  "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
}
{
  "file": "/Users/finn/src/github.com/TBD54566975/did-dht-method/impl/cmd/main.go:95",
  "func": "main.run",
  "level": "info",
  "msg": "shutdown signal received",
  "signal": "interrupt",
  "time": "2024-01-23T13:15:46-08:00"
}

This logs to stdout regardless of config and to a as well file if configured. Heavily based off the ssi-service logging. IMO logging to a file isn't a thing that we should have until we have a concrete reason to have it.


Add UBLOX_EVK_ODIN_W2 override for int. SD-card

Enable the internal SD-card reader in UBLOX_EVK_ODIN_W2. This will
disable the CI-shield SD-card reader if you have, if you prefer using it
you have to remove this target override section.
Please note that there seem to be some reliability problems with the
internal SD-card slot, in my case the mbed OS CI-shield works better.

I would hold off with merging until a "GO" from Cloud Client team.

I think this one now getting ready to be merged in. Remaining issue with the WiFi will be fixed by UBLOX team within a fortnight I believe. https://github.com/ARMmbed/mbed-os/issues/4257


XML format change to include property

I am thinking we should have the schema properties part of the schema. Currently they are listed in the epilogue section of the XML file:

    !# end hed

    This is the new format for the mediawiki schema. The schema attributes are designed to be checked in software rather than hard-coded. The schema attributes, themselves have properties. These are:

    * boolProperty - indicates that that attribute represents something that is either true or false and does not have a value. Attributes without this value are assumed to have string values.
    * unitClassProperty - indicates that this attribute is designed to be applied to unit classes.
    * unitModifierProperty - indicates that this attribute is designed to be applied to unit classes.
    * unitProperty - indicates that this a applies to units within a unit class.

I think that it would be better to put them in the schema as:

<propertyDefinitions>
    <propertyDefinition>
        <name>boolProperty</name>
        <description>Indicates that that attribute represents something that is either true or false and does not have a value. Attributes without this value are assumed to have string values.</description>
    </propertyDefinition>
</propertyDefinitions>

The reason that I am thinking of this is that then everything is in the XML and can be specified using an XSD.   I think it will mainly affect the python schema stuff, but probably the JavaScript and Matlab readers will have to be adjusted.
If there are no objections, I would like to go ahead with this before we release HED-3G, but I would like to hear comments from @IanCa  @happy5214 @dungscout96 about potential implications.

They'll still need to be hardcoded to do anything, and the readers will need to go properties -> attributes -> tags/units/modifiers.
I don't think these are major problems, just the main implications I know of.

@VisLab and I discussed this a couple of weeks ago. I was against including these as schema elements because I feel the properties are aspects of the specification, not of the individual schemas. Unless we're creating new schema-specific properties, I feel there's nothing to be gained by including them in the schemas in a structured form.

I have been working on an XSD to be used to specify the structure of and to validate XML HED schema.  This specification is needed to nail down the structure of the schema, particularly as we move forward with library schema.  I was hoping to include an XSD as part of the initial release of HED8.0.0.
The hedxsd-test directory of the hed-specification repository has a draft of the XSD and the proposed structure for the XML. At the end of the XSD is the specification of the HED structure in terms of the previously-defined complex types.
I am thinking that we should actually require all of the sections (even when they are empty). I have included the property specification as part of this as well. The reason that I now think it should be in is that the schema validators should eventually check that there aren't any random properties associated with the schema attribute section.   Most of this is relevant only to schema validation and not to HED validators.  Hence, if the JavaScript and Python HED validators won't have any issue with ignoring it, there shouldn't be a problem.
Could @IanCa and @happy5214 and @dungscout96 verify that the property section can be easily ignored when reading the HED schema for processing?  I would appreciate it if you could also look over the proposed XSD and see if you spot any issues.  I have validated using several online validators, but they all require me to explicitly load the XSD.
@sappelhoff: any comments you have on this would be appreciated too.

Also, does anyone see any problems if we end up putting the XSD file in the hedxml directory?

These changes have been incorporated into HED8.0.0-beta.3


fix(Route Cache): Filters set cookie header from page cache

Fix for https://github.com/dulnan/nuxt-multi-cache/issues/30

Thank you very much for the fix! I see the problem of generally caching the set-cookie header, though I'm wondering if there might be cases where this might actually be desired, since it doesn't always have to be a cookie that relates to authentication.  Just thinking of somebody using the useCookie() composable and wondering why after the second request the response is served from cache without a Set-Cookie header.
Maybe a better approach would be to offer a way to enable/disable this behaviour, maybe even decide via a method that can be provided whether and what to store in cache?
In any case, I'm going to merge this now since it also contains tests and make this behaviour at least configurable, maybe even try to implement something like a onBeforeRouteCacheWrite server option.


outgoing-webhooks validation

IAC-224 CXO: Validation Webhooks for CRDs

@OrNovo Please consider adding testcases to e2e/outbound_webhook_test.go, or in a new file, to validate the new functionality.

@OrNovo Please consider adding testcases to e2e/outbound_webhook_test.go, or in a new file, to validate the new functionality (even in a follow-up).

I  resolved the issued you mentioned. The e2e-tests will be added on a different PR.


⚠ Bofrost.lu has degraded performance

In 84773e3, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1298 ms

Resolved: Bofrost.lu performance has improved in a10858a after 20 minutes.


Can`t edit profile in the game

After I use the tool,i`t worked,but  I cannot edit the profile in the game. Once I do this, the game will not respond
My ETS2 vision is 1.45,and the tool vision is <IP_ADDRESS>

Always update to latest version.
Do not edit autosaves.
You can Restore from Backup (button next to save selection)


visdiff: Don't comment if no visual changes found

:mag_right: :mute:
:eyeglasses: @keybase/react-hackers

:+1:

:mag_right: These commits introduced some visual changes:

Changed: Request_Invite-Name (before) (after)


Add code to push to artifactory

We're in the process of moving all of our Avvo Ruby gems over to an Artifactory installation at IB. The first part of this process is making it so that new gem versions will get pushed to packagecloud as well as to artifactory. This pull request will add the necessary changes for this. Please let me know if I can explain in more detail about the larger project or if there are questions about the changes in this pull request.

FYI, I'm not really maintaining this project anymore. You might want to fork the project to the Avvo organization and use that fork or I can transfer the project to the Avvo organization.


[GenericResources] Update API version lookup to be case-insensitive

Why
While using the GenericResources API collection, the SDK caches the available API versions for the resource type by invoking the   equivalent of GET /providers/Microsoft.
The API version lookup for a specific resource type is case sensitive, which is throwing an exception if there is a case mismatch between user input and the dictionary contents.
Issue - #27819
Sample PR - #27944
What

Resources API Version dictionary has been modified to become case insensitive.

API change check
API changes are not detected in this pull request.

PR is merged, thanks for your contribution! @abhiroop-goyal


New version: Fly-io.flyctl version 0.3.42

Pull request has been created with komac v2.6.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

No errors to post.

(Automated response - build 899.)


Spade multi-game support

Support loading multiple games to Sprig. We'd use the last half of Sprig's flash (the first half is used for something... I'm not sure), breaking it up into 8 100kb slots.
This would break games that are <100kb, but there's potential for having the ability to have a game span multiple slots.
Users would be able to select one of ~8 games in a list from the Sprig console's boot screen. When uploading a game, the Sprig web client would specify the name of the game. This will fail if there are no available slots on the device, and games can be deleted on the Sprig console.
Functionality in Spade to change and delete slots will be wrapped in an interface to support future use of the SD card to store games and assets.

@leomcelroy could I have your thoughts?

I'm fine with this feature but would not consider it high priority. I think you should always be able to upload from the browser. It sounds like that would neccesitate adding the ability to delete a slot from the console. Also what happens if you have a large game. Is the mqx game size now limited?


HDDS-11318. Add versionsBackup to the gitignore file

What changes were proposed in this pull request?
When executing mvn versions:set, all versionsBackup files are shown, which should be hidden. The purpose of this PR is to solve this.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11318
How was this patch tested?
After adding this pr, the versionsBackup file will not be displayed again when executing mvn versions:set again.
mvn versions:set -DnewVersion=1.5.1
`
Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git restore ..." to discard changes in working directory)
modified:   hadoop-hdds/annotations/pom.xml
modified:   hadoop-hdds/client/pom.xml
modified:   hadoop-hdds/common/pom.xml
modified:   hadoop-hdds/config/pom.xml
modified:   hadoop-hdds/container-service/pom.xml
modified:   hadoop-hdds/crypto-api/pom.xml
modified:   hadoop-hdds/crypto-default/pom.xml
modified:   hadoop-hdds/docs/pom.xml
modified:   hadoop-hdds/erasurecode/pom.xml
modified:   hadoop-hdds/framework/pom.xml
modified:   hadoop-hdds/hadoop-dependency-client/pom.xml
modified:   hadoop-hdds/hadoop-dependency-server/pom.xml
modified:   hadoop-hdds/hadoop-dependency-test/pom.xml
modified:   hadoop-hdds/interface-admin/pom.xml
modified:   hadoop-hdds/interface-client/pom.xml
modified:   hadoop-hdds/interface-server/pom.xml
modified:   hadoop-hdds/managed-rocksdb/pom.xml
modified:   hadoop-hdds/pom.xml
modified:   hadoop-hdds/rocks-native/pom.xml
modified:   hadoop-hdds/rocksdb-checkpoint-differ/pom.xml
modified:   hadoop-hdds/server-scm/pom.xml
modified:   hadoop-hdds/test-utils/pom.xml
modified:   hadoop-hdds/tools/pom.xml
modified:   hadoop-ozone/client/pom.xml
modified:   hadoop-ozone/common/pom.xml
modified:   hadoop-ozone/csi/pom.xml
modified:   hadoop-ozone/datanode/pom.xml
modified:   hadoop-ozone/dist/pom.xml
modified:   hadoop-ozone/fault-injection-test/mini-chaos-tests/pom.xml
modified:   hadoop-ozone/fault-injection-test/network-tests/pom.xml
modified:   hadoop-ozone/fault-injection-test/pom.xml
modified:   hadoop-ozone/httpfsgateway/pom.xml
modified:   hadoop-ozone/insight/pom.xml
modified:   hadoop-ozone/integration-test/pom.xml
modified:   hadoop-ozone/interface-client/pom.xml
modified:   hadoop-ozone/interface-storage/pom.xml
modified:   hadoop-ozone/ozone-manager/pom.xml
modified:   hadoop-ozone/ozonefs-common/pom.xml
modified:   hadoop-ozone/ozonefs-hadoop2/pom.xml
modified:   hadoop-ozone/ozonefs-hadoop3-client/pom.xml
modified:   hadoop-ozone/ozonefs-hadoop3/pom.xml
modified:   hadoop-ozone/ozonefs-shaded/pom.xml
modified:   hadoop-ozone/ozonefs/pom.xml
modified:   hadoop-ozone/pom.xml
modified:   hadoop-ozone/recon-codegen/pom.xml
modified:   hadoop-ozone/recon/pom.xml
modified:   hadoop-ozone/s3-secret-store/pom.xml
modified:   hadoop-ozone/s3gateway/pom.xml
modified:   hadoop-ozone/tools/pom.xml
modified:   pom.xml
no changes added to commit (use "git add" and/or "git commit -a")
`

One can avoid generating backup files by setting generateBackupPoms to false.
mvn versions:set -DnewVersion=1.5.0 -DgenerateBackupPoms=false

Currently versionsBackup files can be removed simply by git clean -fd.  After this change they will be ignored by Git, so git clean -fd will not remove them.

Thanks @adoroszlai .
It looks like this issue doesn't need to be fixed, I will close this PR.


Static headers with aurelia-table?

Hey,
We are trying to make a table with static headers with your aurelia-table, and were wondering if there was a built in way to add the static headers. I don't think the documentation mentioned it, but I figure I'd ask anyway.
We initially tried doing this by separating headers and data into 2 different tables, and then using $displayData to relate the two (so the top table sorts, and the bottom table displays.) This works, except the column widths are different for header and data tables, so the headers don't align up with the data. We don't want to hard code the widths each time because there are too many tables to apply it too. We were relying on the browser to auto fit everything.
Is there a way using aurelia-table to have static headers, or could there be something in the future?
This may be a stretch, but if there IS something for static headers, is there something for static columns too? So someone could horizontally scroll and have a couple fixed columns on the left?
Any help would be appreciated! Thanks!

Unfortunately no, there is no official way to support static headers or columns, one of the goals I have with Aurelia Table is to keep it very simple and leverage HTML tables the most possible.
I will take some time though to look into it, but I cannot promise anything, sorry

Alright that's fine. Your aurelia table sorter is still making our lives much easier, so we're going to continue using it.
Thanks for the quick response!

I would love if even an unofficial way/description of doing this found its way into Aurelia Table. Im in the process of writing a quite advanced application with potentially very large tables, and this is the most critical piece that is missing (and my css-knowledge is bleh...). Im reluctant to start using ag-Grid since I would be losing most of the awesome databinding that aurelia provides. So static/floating headers - yay! Floating column(s) - yay yay!!
Anyhow, keep up the good work.


Another suggestion: All URLs should be relative

Hey Andrii (@pasichDev),
I've noticed that in both your initial code and this new version that you always have a config variable with the site and port.
This should either be inferred from the $_SERVER array, or never be mentioned anywhere by always using relative paths.
This allows for very easy deployments without having to have another variable to configure.
We have config vars for the stuff we can't get from $_SERVER and/or $_ENV, like database credentials and such.
The rest must be collected from the environment that the app is residing, not ask the person that deploys to have another variable to mess up :smiley:
Humans tend to make mistakes. Collecting data from the environment is safer that having a human guess what it is.
Cheers,
Gus

Hello @gcarreno , you are right, it was implemented illogically!

Hi @gcarreno , I already fixed it, you can close the issue!

Hey Andrii (@pasichDev),

you are right, it was implemented illogically!

Not completely illogical, no. A lot of the frameworks have some kind of variable with the same info.
The difference is that they try and get it from the running environment and avoid being a fixed constant :smiley:

I already fixed it, you can close the issue!

That is awesome, I'll do that :smiley:
Cheers,
Gus