Rancher UI does not set X-Api-CSRF if using Apache as SSL-Proxy

Rancher versions:
rancher/server: 1.6.0
rancher/agent: 1.2.2
Infrastructure Stack versions:
healthcheck: 0.3.1
ipsec: net 0.11.2
network-services: metadata 0.9.1, network-manager: 0.7.0
scheduler: 0.7.5
kubernetes (if applicable): n/a
Docker version: (docker version,docker info preferred)
Containers: 13
Running: 10
Paused: 0
Stopped: 3
Images: 30
Server Version: 17.05.0-ce
Storage Driver: overlay
Backing Filesystem: extfs
Supports d_type: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
seccomp
Profile: default
Kernel Version: 3.10.0-514.16.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
OSType: linux
Architecture: x86_64
CPUs: 20
Total Memory: 125.8GiB
Name: de-cg1-docker03.1worldsync.de
ID: XTA3:KPC2:45EA:A7NV:HUMH:XQIM:W43C:N2YW:AXR6:SYK7:Y7AT:3SL2
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
<IP_ADDRESS>/8
Live Restore Enabled: false
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
3.10.0-514.16.1.el7.x86_64
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Bare-metal
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single Node Rancher with internal DB using Active Directory for authentication
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Set up Apache with HTTPS using the Virtual Host configuration as mentioned here:
https://docs.rancher.com/rancher/v1.6/en/installing-rancher/installing-server/basic-ssl-config/#example-apache-configuration
Activate Active Directory Authentication configured.
Try to login with any valid user via the HTTPS proxy.
Results:
If trying to login through SSL Proxy a "CSRF header and cookie do not match" is logged and reported in the Login Match.
Using the direct way to log in (via HTTP, no Proxy) it works as expected.
Using a HTTP Trace Tool in the Browser comparing the successful and the failed request, one can see the X-Api-CSRF Header is missing in the Requests using the Apache SSL Proxy:
Successful Request (partly)
POST http://:8099/v2-beta/token
Origin: http://:8099
x-api-action-links: actionLinks
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36
content-type: application/json
x-api-no-challenge: true
accept: application/json
x-api-csrf: 3209AD4010
Referer: http://:8099/login
Accept-Encoding: gzip, deflate
Accept-Language: de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4,nb;q=0.2
Cookie: PL=rancher; CSRF=3209AD4010
Failed Request (partly)
https:///v2-beta/token
POST https:///v2-beta/token
x-api-no-challenge: true
accept: application/json
Origin: https://
x-api-action-links: actionLinks
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36
content-type: application/json
Referer: https:///login
Accept-Encoding: gzip, deflate, br
Accept-Language: de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4,nb;q=0.2
Cookie: PL=rancher; CSRF=91B3593D26
The only log message I get is:
[i.g.i.g.r.handler.CSRFCookieHandler ] Request's CSRF header did not match cookie
(from cattle-debug.log)
I'm pretty much out of ideas what to do here...

This seems hard to believe, the UI has absolutely no logic around it (https://github.com/vincent99/ui/blob/1.6-dev/app/mixins/store-tweaks.js#L16-L19) and there are lots of people using Apache.  Do you have other config that is changing the cookies to httponly or something?  That's all I can think of that would explain there being a cookie in the request but the UI doesn't see it and therefore doesn't set the header.

This was indeed the problem, this is a central Apache for a lot of services and deep down in its configuration there was a:
Header edit Set-Cookie ^(.*)$ $1;HttpOnly;Secure
The admin removed the "HttpOnly" and now it is properly working. Thanks a lot for the hint! I didn't see the HttpOnly while debugging the first time.


Allow sorting decklists by Set

Give the option to sort decklists by set, so that we can easily see which card is from which set for people who store their collection in sets.
Netrunnerdb allows this already.

Yes, I asked about this a while ago as well.
https://github.com/Alsciende/thronesdb/issues/96

old ticket, this got fixed with the dec. 18 release.


蓝牙MESH 广播包内容编辑 (IDFGH-10147)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
求助：蓝牙mesh 广播包 的内容可以像 普通蓝牙广播包 里的内容一样根据格式自定义吗？

You can use the following API to send regular advertising when using mesh.
esp_err_t esp_ble_mesh_start_ble_advertising(const esp_ble_mesh_ble_adv_param_t *param,
                                             const esp_ble_mesh_ble_adv_data_t *data);


feat✨: add clear button for every input box

Close #12

It's easy to add a clear button to a <input>  by set it as <input type="search">. But there is no easy and consistent way  ( consistent with the <input type="search"> implementation ) to add a clear button to <textarea>.
And I tried to find some web components that does just this, but failed.
So here is my crappy solution to make a consistent clear button across <input> and <textarea>.


REQUEST: Complete LiveView Form implementation example

Hi @bluzky!
Would it be possible for you to add a complete LiveView form example with different types of inputs (input, textarea, select, checkbox) using the Salad UI components? It would be really helpful for more novice Elixir programmers to get a more complete example of how to implement forms using your components.

@jasur-boswell sure, I'll add another example on the storybook. I'll ping you when it's done

@jasur-boswell  here is a demo form.
https://github.com/bluzky/salad_storybook/blob/main/storybook/examples/form_demo.story.exs
If you have any question, feel free to ask me


[Bug] RuntimeError: Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu

Hi,
It happens in band_pass_filter.py
bandwidth_dist is allocated on the CPU (ln 101-103) while center_dist (ln96-98) is allocated on the GPU.
I think that it can be solved by using the device info of selected_samples for bandwidth_dist .

Ok, yeah, that should be fixed. I'll see if I can patch it real quick

https://github.com/asteroid-team/torch-audiomentations/pull/138


Angrylion RDP N64 and general libretro builds

I got to about where you are building mupen64 for web. Another project you might be interested in is https://github.com/nbarkhina/N64Wasm/ they took the old parallel libretro code and used SDL openGL baked into emsdk.
My question is if it is possible to basically go back in time just forget about Glide and use CPU cycles to get something working for N64? It looks like in the most current versions everything is tied to threading and as far as I can tell with all the building I have done enabling PTHREAD in retroarch and using workers is a big overhaul to the codebase to enable shared memory arrays.
I got the interface to load using proxy-to-worker, but any core launching from there will just crash.
I have not had any luck getting the parallel core building and working with angrylion RDP on my own, just wondering if it is something you have looked into? I am mostly interested to see if it produces something playable with a modern CPU despite the lack of threading.
Also unrelated to this issue, it looks like to get mobile compatibility the missing piece is overlay support in:
https://github.com/libretro/RetroArch/blob/master/input/drivers/rwebinput_input.c
It needs touch mapped like they do for mouse:
https://emscripten.org/docs/api_reference/html5.h.html#touch
https://github.com/libretro/RetroArch/blob/master/input/drivers/rwebinput_input.c#L261-L279
Then referenced properly in input_overlay.
Alternatively elements can be rendered in the page separate from the canvas.
Basically I have gotten as far as I believe I am technically capable of porting cores over for self hosted web and seeing if you may have anymore insight on continuing to fork off some of these cores to something usable for web.

Sorry it took me so long to get to this issue.

My question is if it is possible to basically go back in time just forget about Glide and use CPU cycles to get something working for N64?

Possibly, but I really wouldn't want to (try to) do this.
Workers are a new concept to me, they seem like they would be useful, I can look into them.
As @ethanaobrien suggested in #6, I am going to try using the GLupeN64 core. It is a little out of date, but I should be able to update it as needed.

As for touch support, thanks for the information, I will play around with it and see how it works. However, I'm a little afraid that the RetroArch touch controls are too lacking, and the screen may be shrunk by the aspect ratio, but that can be fixed (see #7). I was considering making custom controllers in the DOM that would trigger keyboard events to simulate inputs.

I will start work on these as soon as 6.4 is released, which is soon, I promise. I want to start focusing more on getting more cores supported now.

Here is reference code for the cores I built.
https://github.com/linuxserver/libretro-cores
Released as tarball here:
https://github.com/linuxserver/libretrojs
Outside of the data directory change for the wasm file location they should be plug and play.
Source snapshot:
https://github.com/thelamer/retrostash
They have the missing assets stanzas removed. I built using emsdk 1.39.5.
Been working lately to get safari 15 support for iPhones/iPads without luck, the code runs, but nothing renders to canvas.

This is as far as I could get with Glupen:
https://ipfs.infura.io/ipfs/QmfWEGQFoBxi4YQ49KCimTAK9jpgdUf1HvxgoqxjXVXMtf?filename=glupen64.zip
It builds and loads, but complains about the functions defined in glsm.c and crashes:

Source: (built with emsdk 1.39.7 for fiber support)
https://github.com/thelamer/GLupeN64

So I did not get anywhere with Glupen, but did find a change that actually modified the output and got a bit further.
I was interested if it made a difference in your mupen64 core and surprisingly it did.
If you change ctx=canvas.getContext("webgl" to ctx=canvas.getContext("webgl2" in the mupen64plus_next_libretro.js file a bunch of the texture errors dissapear. IE:
Without:

With webgl2:

Not really an encompassing fix for anything, but maybe could lead to something.

I tried it out, it fixes a few errors, but not all.
I think that switching to GLES3 is a wise idea, that's what m4xw was testing. Once this next update is finished, I'll see what I can do.

@BinBashBanana I agree
Another example:
webgl

webgl 2

This is when only changing that one line of code

So I guess goal achieved, I went back in time and got an angrylion emscripten build. Forked here:
https://github.com/thelamer/parallel-n64/tree/angrylion
Honestly it is not far off on modern systems especially an Xbox Series console despite only having one core to work with and using old code. I have not had any luck forcing Angrylion into a 320x240 low res mode though and I feel like that may be the only path to this being playable.
PreBuilts here:
https://ipfs.infura.io/ipfs/QmczcVnKehE4xfsZJ2KcGH1Q9Jz7Nq4rGa8u5p9e35ecvS?filename=parallel_n64.zip

I got threading to work with the latest emsdk (3.1.0), this allows building against head of https://github.com/libretro/parallel-n64:
https://user-images.githubusercontent.com/1852688/147839990-2b1d8cb3-8fc5-4d17-8f6d-7971159d213c.mp4
It is pretty basic changes to the make section of the core: (also change -Ofast to -O3 and disable -fcommon)
# emscripten
else ifeq ($(platform), emscripten)
   TARGET := $(TARGET_NAME)_libretro_$(platform).bc
   GLES = 0
   HAVE_OPENGL = 0
   WITH_DYNAREC :=
   HAVE_PARALLEL = 0
   CPUFLAGS += -DNOSSE -DEMSCRIPTEN -DNO_ASM -DNO_LIBCO -s USE_ZLIB=1 -s PRECISE_F32=1
   WITH_DYNAREC =
   CC = emcc
   CXX = em++
   HAVE_NEON = 0
   PLATFORM_EXT := unix
   STATIC_LINKING = 1
   SOURCES_C += $(CORE_DIR)/src/r4300/empty_dynarec.c
   HAVE_THR_AL = 1
   CFLAGS += -pthread
   LDFLAGS += -pthread
   CXXFLAGS += -pthread

Then for Retroarch itself: (Makefile.emscripten)
MEMORY ?= 536870912
CFLAGS += -pthread
CXXFLAGS += -pthread
LIBS    := -s USE_ZLIB=1
LDFLAGS := -L. --no-heap-copy -s $(LIBS) -s TOTAL_MEMORY=$(MEMORY) -s NO_EXIT_RUNTIME=0 -s FULL_ES2=1 -s "EXTRA_EXPORTED_RUNTIME_METHODS=['callMain']" \
           -s EXPORTED_FUNCTIONS="['_main', '_malloc', '_cmd_savefiles', '_cmd_save_state', '_cmd_load_state', '_cmd_take_screenshot']" \
           --js-library emscripten/library_rwebaudio.js \
           --js-library emscripten/library_rwebcam.js \
           --js-library emscripten/library_errno_codes.js \
           -pthread -s PTHREAD_POOL_SIZE=4

This will also produce a parallel_n64_libretro.worker.js that needs to be copied over to your project.
For this to work in chrome you also need to serve the content from a webserver with Cross-Origin-Embedder-Policy and Cross-Origin-Opener-Policy set. IE to achieve this with an express server:
app.use(function(req, res, next) {
  res.header("Cross-Origin-Embedder-Policy", "require-corp");
  res.header("Cross-Origin-Opener-Policy", "same-origin");
  next();
});

Or from an Nginx webserver:
        add_header 'Cross-Origin-Embedder-Policy' 'require-corp';
        add_header 'Cross-Origin-Opener-Policy' 'same-origin';

I have kind of a shitty PC (i7-4790) I would expect better on more modern chips.
One thing really stands out playing with thread count, I do not think the current bottleneck is in going past 4-8 threads for angrylion. I can get more CPU usage by going to 16 32 etc, but it actually hurts performance and it looks like the limit is on the main thread (possibly). I suspect cxd4 rsp, but do not have the knowledge to really dig in past this. In general it is not there yet and not "playable", I wonder if any other tweaks could be applied to get it on par with the desktop version.
Pre-Built bins:
https://ipfs.infura.io/ipfs/QmcHKT7PM2tFTyqkaZUsUJ8ATHgojLRL1zav5ibvAmB2wk?filename=multi-angry.zip

Bumped down to 320x240 for the resolution, this is really close to being playable.
https://user-images.githubusercontent.com/1852688/147858795-4fdc885d-3fa6-497b-8225-28e629f38d00.mp4
https://ipfs.infura.io/ipfs/QmaaHjhVCikFKh2TQ5M8cQP1WGhUsXd2jTCjT9qz79F56n?filename=angry-320.zip

Bumped down to 320x240 for the resolution, this is really close to being playable.
https://user-images.githubusercontent.com/1852688/147858795-4fdc885d-3fa6-497b-8225-28e629f38d00.mp4
https://ipfs.infura.io/ipfs/QmaaHjhVCikFKh2TQ5M8cQP1WGhUsXd2jTCjT9qz79F56n?filename=angry-320.zip

Awesome! Sorry I haven't been keeping up with this issue. I'll try implementing ToadKing's emscripten libco fix, just to see if that works better than PTHREAD. (it probably doesn't)

Awesome! Sorry I haven't been keeping up with this issue. I'll try implementing ToadKing's emscripten libco fix, just to see if that works better than PTHREAD. (it probably doesn't)

Threads opens up a bunch of options here, check out ds emulation:
https://user-images.githubusercontent.com/1852688/147860005-425405aa-3c2b-422a-aec6-1125705e6aea.mp4
https://ipfs.infura.io/ipfs/QmPCcMAR3bSyWzGBgZCJKHo78eXpMh9PFqwteC1vrUBB36?filename=melon.zip
I would bet this makes stuff like Saturn playable as well, though I can't figure out the proper symbol declaration in yabause/src/thr-rthreads.c for slock and sthread stuff when building with HAVE_PTHREADS

Threads opens up a bunch of options here, check out ds emulation:
https://user-images.githubusercontent.com/1852688/147860005-425405aa-3c2b-422a-aec6-1125705e6aea.mp4
https://ipfs.infura.io/ipfs/QmPCcMAR3bSyWzGBgZCJKHo78eXpMh9PFqwteC1vrUBB36?filename=melon.zip
I would bet this makes stuff like Saturn playable as well, though I can't figure out the proper symbol declaration in yabause/src/thr-rthreads.c for slock and sthread stuff when building with HAVE_PTHREADS

As suspected Saturn runs really good with threading: (full speed on an Xbox)
https://user-images.githubusercontent.com/1852688/148463500-e2321890-1b7a-4640-988d-c3628d458f77.mp4

Hi @thelamer, sorry for the long period of inactivity, I have been working hard on v6.5 and it is finally released! It addresses several things in this issue:

All of the WebGL draw errors were caused by emscripten issue 4214. Implementing one of the patches fixes the problem completely.
Mupen64Plus-Next has been updated to the latest version from GitHub, and is now using GLideN64 GLES3 (WebGL 2). A different bug is still here: see #4.
ParaLLEl N64 has been added with GLide64 and glN64 (both GLES2 renderers on WebGL 2, as using WebGL 2 seems to fix a minor color depth problem.) Libco/fiber has been added back as well.
melonDS and Yabause have both been added without threads since github.io cannot host with special headers.
Beetle PSX HW has been added, I worked on GLES 3.0 support for the HW renderer (see pull #856).

Additionally, these 5 cores have been built with autovectorization which can improve performance slightly (these flags added to the compile flags: -msimd128 -ftree-vectorize)
Threaded Angrylion is not out of the question, I'd like to get this working on the Mupen64Plus-Next core as well. Another thing - what was your solution to getting Yabause to build with threads? I couldn't figure it out.
At some point in the future I also want to port melonDS's OpenGL renderer to GLES 3.0, as well as getting YabaSanshiro (outdated saturn core with GLES 3.0 rendering) or Kronos (more updated saturn core that either requires GLES 3.0 or 3.1, I'm not sure) to run on a single thread.
Threaded OpenGL rendering may also be possible at least for Mupen64Plus-Next, m4xw said that he had had threaded GLideN64 working at some point but not anymore. He also said that he found an old mailing list saying that offscreen framebuffers only worked on emscripten's SDL backend (not on EGL) but it could be outdated.
Speaking of this, it seems I'm restricted to emscripten 2.0.15 as any higher than that prevents any core from loading. I haven't actually tested this recently because it is a pain to test, and I may have already fixed it.
I have also transitioned to a much better system for core patches, see Building from source. I tried my best to be a thorough as possible when making this, so let me know if you run into any problems.
Here's some screenshots of Mupen64Plus-Next:

Show

Holy cow @BinBashBanana this is amazing you are a genius. Correct me if I'm wrong here, but this should add capabilities to anything that doesn't leverage simd right? Shouldn't stuff like duckstation and PS2 be plausible now?

Probably. I don't expect particularly good performance at all, but I can try also using SIMD in cores that use SIMD instructions (emscripten support). I tried compiling GLideN64's NEON stuff in Mupen64Plus-Next, but there were some unimplemented symbols so I gave up. Citra, Dolphin, PCSX2, PPSSPP, and Flycast are the cores that I haven't built yet for this reason. (A few of them also use CMake which could also be annoying.)


Patch emojis & new properties

Description
My primary motivation was to fix bugs (e.g: toList not called on map, cannot react with custom emojis...).
After that, I saw there wasn't a lot of properties for emojis, like; theirs names was always nyxx, the cdnUrl was always returning static pngs even for animated emojis, and so on. So I basically fixed bugs and added new methods/properties described below.
Type of change

Added example for emojis

[x] Bug fix (non-breaking change which fixes an issue)
- Defaut value of http for CachePolicyLocation is true instead of false (according to the doc)
- encodeForAPI in IBaseGuildEmoji works properly now

[x] New feature (non-breaking change which adds functionality)
- Added fetchCreator method to emoji
- Added resolve method on IResolvableGuildPartialEmoji to return a IGuildEmoji

[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- cdnUrl is no more a property

Checklist:

[x] Ran dart analyze or make analyze and fixed all issues
[x] Ran dart format --set-exit-if-changed -l 160 ./lib or make format and fixed all issues
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked my changes haven't lowered code coverage

Looks good. Gonna merge today in the afternoon. Thanks for contributing :)


JBPM-5097 - Kie Server - jBPM UI - process image markers not visible …

…for some nodes
@mrietveld could you please take a look?

+1 When the jenkins tests complete.
@mswiderski Nice tests!


Content change due to tabs in modal cause top of modal to be cut off

I'm using vertically centered modals (via css below) to display content. They work fine, except for when I have tabbed content that overflows the page (see image). I've looked up a bunch of different fixes and I haven't found anything to work.
.modal .modal-dialog {     z-index: 10051;     position: absolute;     top: 50%;     left: 50%;     transform: translate(-50%, -50%) !important;  }
https://gyazo.com/91961650bfdd0b90b20bbc789acbcb9a

Hi, could you please provide a test case as per our contributing guidelines? You can fork this JSFiddle.


Test failure with Skylake CPU, potentially related to avx512 instructions

I have a test failure (dblas3) on the current develop branch. Here is the test output, DBLAT3.SUMM.
I build OpenBLAS with cmake, setting CMAKE_BUILD_TYPE=Release and running ctest. The machine has Intel Xeon Silver 4116 CPUs and is running Ubuntu 18.04 with GCC 7.5.0.
This test passes if I set NO_AVX512=1

Please share OpenBLAS version and the last number from CPU trade name (it is all in /proc/cpuinfo)
Worth trying git checkout (the "Download ZIP" button on top right in github project page)

I checked out the develop branch SHA = 253670383f15cd4d25c6be6b210dfa48a6dcc883
Here's the info from /proc/cpuinfo for processor 0 ( 48 total)
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 85
model name	: Intel(R) Xeon(R) Silver 4116 CPU @ 2.10GHz
stepping	: 4
microcode	: 0x2006b06
cpu MHz		: 2100.000
cache size	: 16896 KB
physical id	: 0
siblings	: 24
core id		: 0
cpu cores	: 12
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 22
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti intel_ppin ssbd mba ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm mpx rdt_a avx512f avx512dq rdseed adx smap clflushopt clwb intel_pt avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts pku ospke md_clear flush_l1d
bugs		: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs taa itlb_multihit
bogomips	: 4200.00
clflush size	: 64
cache_alignment	: 64
address sizes	: 46 bits physical, 48 bits virtual
power management:

What about building with GNU make (whether this error still occur)?

There is something strange - I did not see failures in my local builds and the latest CI jobs do not show a problem, but looking back I see occasional test failures (in the Azure job that uses Intel SDE) after commits that did not touch any x86_64 code at all. Could be there is something using uninitialized memory that just happens to be zeroed most of the time :(

btw that CI job uses plain make for the build (and gcc 7.5 on ubuntu 18)

Failure of dblas3 test is reproducible on my i7-9800x when building with cmake using gcc-7 and gfortran-7 (ubuntu-16.04), willl look into it deeply this weekend.

@wjc404  first to check should be AVX512 xsave block early in boot log....

It seems that something is wrong with cmake variables. Possibly the cmake variable DYNAMIC_ARCH is set to ON prior to the parsing of kernel/CMakeLists.txt however the C macro DYNAMIC_ARCH is not defined when reading param.h.

Update: this change can solve the problem

Thanks. That would certainly explain why my recent workaround - to fall back to the earlier 4x8 kernel in DYNAMIC_ARCH builds - did not work with CMAKE. Unfortunately it still seems likely that there is something amiss in the 16x2 kernel. (Unless @quantumsteve built with -DDYNAMIC_ARCH as well)

@martin-frbg I did not build with -DDYNAMIC_ARCH.

Playing with SDE, it seems it could be the dgemm_tcopy_16_skylakex.c that is problematic, not the 16x2 DGEMM/DTRMM kernel itself. Unfortunately I am currently away from my SkylakeX and it appears to have lost its wireless connection to the office router.
If you are willing to experiment, you can try changing the DGEMMITCOPY line in kernel/x86_64/KERNEL.SKYLAKEX to point to "../generic/gemm_tcopy_16.c" rather than "dgemm_tcopy_16_skylakex.c" and do a complete rebuild

Believed to have been fixed by the 0.3.21 rewrite of the compiler capability test and subsequent logic in the getarch tool, plus the removal of my somewhat misguided workarounds for the originally observed symptoms - 0.3.19 from just around the time of the report would have been broken in this regard.


Error: https://registry.yarnpkg.com/@bfc%2Feslint-plugin-bfcomposer: Not found

Hi there,
do you know how to solve this?
My Steps:

Download Composer as .zip from Resp
unpack
Open in VS
run yarn install
error

Thanks for your help!
Yarn version:
1.22.10
Node version:
14.15.4
Platform:
win32 x64
Trace:
Error: https://registry.yarnpkg.com/@bfc%2Feslint-plugin-bfcomposer: Not found
at Request.params.callback [as _callback] (C:\Users)
at Request.self.callback (C:\Users)
at Request.emit (events.js:315:20)
at Request. (C:\Users)
at Request.emit (events.js:315:20)
at IncomingMessage. (C:\Users)
at Object.onceWrapper (events.js:421:28)
at IncomingMessage.emit (events.js:327:22)
at endReadableNT (internal/streams/readable.js:1327:12)
at processTicksAndRejections (internal/process/task_queues.js:80:21)

@Heinzfb - On windows if you download as zip, sometimes the zip is marked as blocked.  Could you verify that you have unblocked the zip file before unzipping.  You can bring up properties and see if there is a checkbox for unblocking.

@Heinzfb - On windows if you download as zip, sometimes the zip is marked as blocked.  Could you verify that you have unblocked the zip file before unzipping.  You can bring up properties and see if there is a checkbox for unblocking.

Hey there,
thanks for the quick answer. I do not have the win10 Pro version. - gpedit.msc - is not intalled by default. So I can't check by bringing this property up. But no Problem, I will get it via clone.  :)

Hey there,
thanks for the quick answer. I do not have the win10 Pro version. - gpedit.msc - is not intalled by default. So I can't check by bringing this property up. But no Problem, I will get it via clone.  :)


🐞 dagger call Secret reveals plaintext

What is the issue?
I have a function that returns Secret[] and when I call it from the CLI it prints all the secret material to the terminal.
dagger call secrets

- _type: Secret
  name: cloudflare.apiToken
  plaintext: XXX
- _type: Secret
  name: restate.host
  plaintext: XXX
- _type: Secret
  name: restate.apiToken
  plaintext: XXX
- _type: Secret
  name: restate.identityToken
  plaintext: XXX
- _type: Secret
  name: restate.adminApiToken
  plaintext: XXX
- _type: Secret
  name: turso.platform.apiToken
  plaintext: XXX
- _type: Secret
  name: turso.groups.platform.apiToken
  plaintext: XXX

Dagger version
v0.13.0
Steps to reproduce
No response
Log output
No response

Mm, we need a way of marking these fields that they shouldn't be printed out.
I think we should have a dagql.Sensitive or similar for items in our server - then we can put this into the typedefs api, and fields that have this should be hidden on the CLI.
This is probably better than a generic "don't show", since Sensitive is more specific for this case, and it would be nice if we could show plaintext: ***.
cc @helderco does that make sense to you? Am happy to work on this for the release.

Or, I wonder if we should just hook up the SecretCensor to the output here :thinking: that would also be cool.

Hey, I made a quickfix in:

https://github.com/dagger/dagger/pull/8468

[...] it would be nice if we could show plaintext: ***.
cc @helderco does that make sense to you?

I don't see the point since it's not useful information.

I think Helder's fix makes the most sense, it's just not something that should be printed automatically by object field auto-selection.
I would say there are probably use cases for a user very explicitly asking for the plaintext of a secret, but that should only be when they explicitly select the plaintext field in their dagger call, never automatic. So whatever we do we probably want to preserve that as a feature (I believe Helder's PR does preserve that).


Test fedora minimal embedded container in downstream

This pull request includes another embedded container in edge-commit and edge-installer blueprints, just like container-embedding.sh upstream test case.
Playbook tasks have been included to check the fedora minimal container image is embedded, and the image is not being pulled again (task fails if podman try to pull latest tag).

/test-rhel-9-2

/test-rhel-8-8

/test-rhel-8-8

We need to wait for osbuild-composer package version in RHEL-8.8 to be delivered before merging this PR.

/test-rhel-9-2


xmlstarlet breaks server.xml

if I use proxy variables, the server.xml will be broken and Confluence fails with
10-Jul-2017 18:15:20.715 WARNING [main] org.apache.catalina.startup.Catalina.load Catalina.start using conf/server.xml: Error at (14, 19) : addChild:  Child name '/confluence' is not unique
If I edit server.xml manually, everything is fine..!?

server.xml will look like this (only proxyName added):

<Server
port="8000"
shutdown="SHUTDOWN"
debug="0"

<Service
  name="Tomcat-Standalone"
>
    <Connector
    port="8090"
    connectionTimeout="20000"
    redirectPort="8443"
    maxThreads="48"
    minSpareThreads="10"
    enableLookups="false"
    acceptCount="10"
    debug="0"
    URIEncoding="UTF-8"
    protocol="org.apache.coyote.http11.Http11NioProtocol"
    proxyName="host.mydomain.com"
/>

    <Engine
    name="Standalone"
    defaultHost="localhost"
    debug="0"
  >

ok. it replaces also the context path for synchrony.
The file doesn't look so strange if you don't use -S or -P

Can you please give a concrete example of your envs or even better the whole docker command?

CONFLUENCE_CONTEXT_PATH=/confluence
CONFLUENCE_PROXY_SCHEME=http
CONFLUENCE_PROXY_PORT=80
CONFLUENCE_PROXY_NAME=host.mydomain.com
I set the envs manually and executed xmlstarlet with the same behaviour as docker run or docker-compose. part of docker-compose:
confluence:
restart: always
image: blacklabelops/confluence:6.2.3
build:
context: ./confluence
args:
- CONFLUENCE_VERSION=6.2.3
container_name: confluence
hostname: confluence
dns: <IP_ADDRESS>
networks:
- backend
ports:
- '8090:8090'
- '8091:8091'
volumes:
- confluence:/var/atlassian/confluence
environment:
TZ: "Europe/Berlin"
CONFLUENCE_CONTEXT_PATH: "/confluence"
ONFLUENCE_PROXY_NAME: "host.mydomain.com"
CONFLUENCE_PROXY_PORT: "80"
ONFLUENCE_PROXY_SCHEME: "http"

Hello @blacklabelops, could you please fix the xmlstarlet behavior, please? There are two context paths and both will be set to i.e. /confluence, but the second context path for synchrony shouldn't be changed. Otherwise, Confluence doesn't start.
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false" startStopThreads="4">
   <Context path="/confluence" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">
   <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties -->
      <Manager pathname="" />
      <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />
   </Context>

   <Context path="${confluence.context.path}/synchrony-proxy" docBase="../synchrony-proxy" debug="0" reloadable="false" useHttpOnly="true">
      <Valve className="org.apache.catalina.valves.StuckThreadDetectionValve" threshold="60" />
   </Context>
</Host>

Of course.

Fixed. Feel free to test.

It works. Thank you very much!


[FR] OCR

Describe your request
For many scanned PDF documents, batch OCR may not provide accurate recognition for document layout. As a result, I have to use rectangular selection combined with OCR.
Could you please add a command line option to export the selected links as images to a specified path, making it convenient to use the OCR functionality of other software?
If the plugin could directly support OCR integration, it would be even better.
Thank you for your hard work on this project!

Could you please add a command line option to export the selected links as images to a specified path, making it convenient to use the OCR functionality of other software?

I guess it's the same request as #65.
You can already specify the path from the Obsidian core's "default location for new attachments" setting, but I agree it will be nice to have more options than that.

If the plugin could directly support OCR integration, it would be even better.

Do you have any recommendations for OCR libraries?

@iris2jane By the way, what OCR tool do you use? I've just tried OCRmyPDF and it's impressive!

I wrote a simple plugin for calling OCRmyPDF from within Obsidian: https://github.com/RyotaUshio/obsidian-pdf-ocr

顺便问一下，你用什么OCR工具？我刚刚尝试了OCRmyPDF，它令人印象深刻！

I use Umi-OCR, which is an open-source software with active updates.

我写了一个简单的插件，用于从黑曜石中调用 OCRmyPDF：https://github.com/RyotaUshio/obsidian-pdf-ocr

Thanks for your prompt and helpful responses!

Not os, but PDF24 has been working great for me. It's free.


Fix merge transcripts

fixes #82

I won't take this PR for two reasons:

L750-59 of EditTrack was meant to remove duplicates, among other things. That it doesn't, means the bug is in L750-59.
The bug is not only about duplicating subfeatures if the same transcript is passed for merge. It can manifest itself in several ways as noted here https://github.com/yeban/afra/issues/82#issuecomment-68584897. This PR is ineffective against them.


[ClusterLoader2] change slice related Go template functions

Required to add access-tokens test to branch 1.17
Related to https://github.com/kubernetes/kubernetes/issues/83375

/lgtm
/approve
/ok-to-test

Are those functions already on the master branch and this is a cherry-pick?

Those functions already on the master branch, this is a cherry-pick and squash of two commits.


Errors: test_gpu doesn't work

Hi all
I have these errors when I try to run 'test_gpu':
Running GPU tests
terminate called after throwing an instance of 'std::runtime_error'
what():  Error: compute_ctc_loss in small_test, stat = execution failed
Aborted (core dumped)
Note that: I can run 'test_cpu' without any problems (Running CPU tests, Tests pass)
I was wondering I might miss some libraries or anything else.
Every kind of suggestion would be appreciated!
Thank you so much.

What kind of GPU do you have?

I have GeForce GTX 580.

The GTX 580 has compute capability 2.0, but warp-ctc requires compute capability of 3.0 or higher. That's why this error occurs. We don't have plans at the moment to support compute capability 2.0 - it would require some work in the GPU kernels. It's definitely possible, though - feel free to send a pull request.


Inconsistent behavior when using List.last as setter

When run on dartpad.dev:
  List<bool> a = [true, true];
  print(a.last); //=> "true"
  a.last = false;
  print(a.last); //=> this still prints "true"

  List<int> b = [1, 2];
  print(b.last); //=> "2"
  b.last = 3;
  print(b.last); //=> "3"
}

Also, when using development build in flutter, this inconsistency was not shown and both updates were successful. However, in production build, this problem start to appear.

Same issue seems to be the case when doing it with .first:
void main() {
  List<bool> a = [true, true];

  print(a.first); //=> "true"
  a.first = false;

  print(a.first); //=> this still prints "true"
  print(a); // [false, true]
  print(a[0]); // true
}

Tested with DartPad on Master with Firefox.

Reproduces readily.
Consistent for any read that is statically detectable as being on the same list with the same index, even in a nother function, as long as it's only called with the same list as argument (probably because it's inlined).
Works for print(a[a.length - 1]) as well, while print(a); shows the false value.
Over-optimistic value caching.

Looked into this and found its caused by a bug in Dart2js's global inference algorithm. We assume that when we see the first/last selectors that they can't modify the "type" of the List. This isn't true for dynamic Lists (where any modification will pass the implicit covariance check) and it isn't true for Lists where Dart2js is representing the values in the list as part of the type (as is the case in the above example where we have true as part of the type of the literal list). We got lucky with a later conservative check in our SSA process that meant this bug only shows up for bool lists. But technically the bug applies to many other types as well.

A fix to Dart2js's type inference has been landed in the SDK.
The criteria to trigger this bug is fairly specific but if you're encountering this issue on a version of the SDK without the fix and need a workaround: The simplest solution is to replace a.first = someBool with a[0] = someBool and a.last = someBool with a[a.length - 1] = someBool. This should properly update the type of the list.


🐛 [firebase_crashlytics] - Flutter/Android Obfuscated Trace

Hello.
I have an App made in Flutter for Android published. It uses Crashlytics so we can detect errors.
The problem is that we obfuscate the code, both in dart as indicated in this link https://flutter.dev/docs/deployment/obfuscate as well as by R8 (by default in flutter, configured with a Proguard file).
The problem is that being obfuscated, when I get the reports to Crashlytics, they arrive with the StackTrace obfuscated and I can not know how to see it without obfuscating. Attached is an image of how it appears.

I have asked for Firebase support and they have told me the following:

Upon checking your screenshot, the way how the stack traces appear non-readable is indeed strange. Currently, as much as we would like to debug this from our side, Flutter is considered one of the external frameworks that's not yet covered by Firebase support. Even though Flutter basically still belongs to Google and we recommend this library for developers looking to bind Firebase to their suitable frameworks, it is not yet considered an official Firebase SDK. Issues that occur while integrating it are being handled by the Flutter team as they have the resources to further check why crashes coming from your app appear that way.
With this, you may try to bring up this issue in the official GitHub tracker for FlutterFire here (handled by Flutter team) so that this issue can be deeply examined. And if you wish to try our official Android SDK during part of the testing, you may also try to run our quickstart app for Crashlytics which has the latest Firebase Crashlytics SDK version and see if it reproduces the same issue (if it's reproducible using the official Android SDK, we can try to troubleshoot it here as well).

Would anyone know how to read the obfuscated trace?

Hi @adriancsbna
Could you please provide your flutter doctor -v and flutter pub deps -- --style=compact?
Thank you

Hi @adriancsbna
This is a duplicate of #2644, and this issue is solved by #4407. It is recently merged. You have to wait a few days for this fix to published in pub.dev. If you want to use it now, you can override your Crashlytics dependency with:
firebase_crashlytics:
  git:
    url: https://github.com/FirebaseExtended/flutterfire.git
    path: packages/firebase_crashlytics/firebase_crashlytics

Deobfuscation can be done like this.

Hi @untp
I have done the test and it works correctly.
I have also been able to defuse correctly.
Thank you very much
Best regards


fix: use non-deprecated delete flag with node drain

Problem
kubectl drain calls a deprecated flag, --delete-local-data, per https://github.com/kubernetes/kubernetes/pull/95076.
Solution
Use the designated replacement.
Result
No warning errors about the --delete-local-data flag deprecation on node drain.

This might not exist on older versions of kubectl. This should be changed depending on the version.

Ok. What changes are you specifically looking for?

@laebshade Yes they are not supported but we download an appropriate kubectl version based on the kube version of a cluster.
So I would get the active entity in that menu, look at the kube version metadata and switch which arg is used based on that.

Thanks for clarifying.
I’m unable to prioritize your requested changes.
Do you wish to close this PR, pick up ownership, or hand off your requested
changes to some one else specifically?
On Mon, Nov 22, 2021 at 9:38 AM Sebastian Malton @.***>
wrote:

@laebshade https://github.com/laebshade Yes they are not supported but
we download an appropriate kubectl version based on the kube version of a
cluster.
So I would get the active entity in that menu, look at the kube version
metadata and switch which arg is used based on that.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lensapp/lens/pull/4400#issuecomment-975595024, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAKQ4KOSOJ5QVZ2OVHK7X3UNJIXBANCNFSM5IPWRQ2Q
.

If you are unable to spend the time now, could you open an issue describing this issue before you close the PR. That way we can track it for planning.

No thank you
On Mon, Nov 22, 2021 at 2:01 PM Sebastian Malton @.***>
wrote:

If you are unable to spend the time now, could you open an issue
describing this issue before you close the PR. That way we can track it for
planning.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lensapp/lens/pull/4400#issuecomment-975828152, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAKQ4M3S527DZAHWHFONXLUNKHQVANCNFSM5IPWRQ2Q
.


A lot of npm vulnerabilities

Description
on a new create-sails project, running npm install produces 34 vulnerabilities.
...
Current behavior
...
Expected behavior
...

Replace space in square bracket with x e.g [x]

[ x] I have checked and this issue does not exist

Hey which of the templates are you using? Vue or React?

vue template

Got it @Maxed0utt I will check it out. Are you currently shipping this?

Got it @Maxed0utt I will check it out. Are you currently shipping this?

Thanks! Not yet, I'm currently shipping SailsJS with web app template, and another project just SailsJS backend. Was just checking out the boring stack for a future project as it seems like it's a better version of the web app template which I'm a huge fan of.


How do I stop Sol from disappearing in a test environment?

This is what I see when I spin up a local server (see screenshare). The app loads up and is shown but when I click away from it,it disappears.
Is there a way to make the app always show on a local server so I can make edits in real time?
https://user-images.githubusercontent.com/72312238/229111720-193f0cfb-8412-4b8b-8d3d-b902ea6b43fc.mp4
Thanks,
Josh

You have to modify the code in AppDelegate.m so that it doesn't hide the window when it looses focus, but it will break a bunch of other stuff

Thanks Oscar!


docs: update documentation

#13

:tada: This PR is included in version 1.0.0-beta.13 :tada:
The release is available on:

npm package (@develop dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add variable expansion support in shortcode params

See 3) in https://github.com/twbs/bootstrap/issues/24475#issuecomment-441211586
Not sure how this would look like, but something ala Bash's variable expansion, eg.
{{< relref "${.Site.Params.version}/features" >}}

Can’t this already be solved by a simple wrapper shortcode?

Yes. But it is a fairly common problem, and you it would potentially create lots of "wrapper variants" and make the content "unportable".
I don't think I'm solving this unless I can find a simple and fast way to do it -- but there are obvious and useful use cases for this.

This is still a valid request.

Big time want for us!


Add more types & clarify docs

Add a few missing type hints.
Clarify and simplify the setup tutorials.

Thanks!


[WIP] generic retry logic applies to nodes, network policies and network policy dynamic handlers

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

709 of 1441 (49.2%)  changed or added relevant lines in 7 files are covered.
70 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.3%) to 50.386%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

go-controller/pkg/ovn/namespace.go
1
7
14.29%

go-controller/pkg/factory/factory.go
23
105
21.9%

go-controller/pkg/ovn/policy.go
128
219
58.45%

go-controller/pkg/ovn/master.go
50
154
32.47%

go-controller/pkg/ovn/ovn.go
120
285
42.11%

go-controller/pkg/ovn/obj_retry.go
377
661
57.03%

Files with Coverage Reduction
New Missed Lines
%

go-controller/pkg/ovn/egressfirewall_dns.go
1
82.31%

go-controller/pkg/node/node_ip_handler_linux.go
3
50.33%

go-controller/pkg/ovn/master.go
14
34.96%

go-controller/pkg/ovn/policy.go
14
69.95%

go-controller/pkg/ovn/ovn.go
38
51.97%

Totals

Change from base Build<PHONE_NUMBER>:
-0.3%

Covered Lines:
14289

Relevant Lines:
28359

💛  - Coveralls

/retest

/retest-failed


SMP-1362 Add monitoring for databases, harness services in helm-charts

Already merged with release 0.6.0


I think the yaml attributes may be missing something

Describe the issue
I am not able to get this to work, but I did also notice there is no "topic" field specified in the document.  I am adding the topic, but I am getting this error:
error creating pubsub client: pubsub(publisher): google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information"
At first, I thought it should have been project_id and not projectId because Secrets Manager for GCP uses project_id. Suggestion is to make it consistent. I am using the same service account and credentials to connect. Is there possibly something wrong with the connector to GCP Cloud Pub Sub or am I missing something?
URL of the docs
https://docs.dapr.io/reference/components-reference/supported-pubsub/setup-gcp-pubsub/
Expected content
I believe topic is an attribute based on other sources I am seeing. And for consistency sake, accepting project_id to be similar with how other GCP configuration is done makes sense.
Additional context
As noted above,  even adding topic to the settings does not help.  Below is the error I am seeing.. And I am using the same service account used for Secrets Manager that is working seems to have this auth issue.
error creating pubsub client: pubsub(publisher): google: could not find default credentials. See https://cloud.google.com/docs/authentication/external/set-up-adc for more information"
Thank you so much!
Chris

@christcottrell - Apologies to getting to this issue late. Dapr Yaml files keep to a consistent naming convention across all of them, hence projectId and not project_id. Did you get this to work, or have you got more detailed information on the error that you are seeing?

@christcottrell Any feedback or update here?


Mark up IT ISO documents

To find examples of source code etc, and how it is rendered. @ronaldtse, any drafts or completed standards I should look at?

There are plenty in public indeed!
The ISO maintains the following PAS list: http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
The following documents are useful in their properties:

ISO/IEC 27000: InfoSec terms - very long terms of reference
ISO/IEC 29100: PII - privacy principles
ISO/IEC 40314: MathML - code, tables, math
ISO/IEC 21778:2017: JSON - a minimal standard example

ISO/IEC 21778:2017 |
-- | --
ISO/IEC 21778:2017 |
-- | --

"ISO/IEC 40314: MathML" has a lot of source code in there. However this document has a very non-standard textual formatting. It actually looks like it's been typeset in LaTeX. Hence the importance of a standardized document model.

@opoudjis Let's markup the JSON document, simple, easy and free.

This will speed up once we have reverse_asciidoctor implemented.

Or unless, this is purely for demonstration purposes. That could be nice and useful.

... We already have the Rice document for demonstration purposes. I think we can let this go, so long as you keep finding new documents to encode...


CI: Hashpin sensitive actions and install dependabot

Closes #225
I've configured dependabot to work the same way as you requested in https://github.com/microsoft/TypeScript/pull/56211

Based on #227, this was missing some pipelines, it seems; oops.

Hi @jakebailey, not sure I understood what you meant on your last comment, can you clarify what was missing?

See https://github.com/microsoft/tslib/commit/095b6a0104d551f550a11385907cfa26b595ba35, this PR forgot CI.yml.

Oh I see.
I left the CI.yml unpinned because it didn't access to any secrets or write permissions, so having it unpinned shouldn't bring any real security threat, and the flexibility of unpinned dependencies can be useful sometimes. But having all actions hash-pinned is not a problem at all 😄.


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3

Why?

Because it's not used and has never been used. It's completely pointless to include.

We don't directly publish to bower, so one could argue that the entire bower.json file is irrelevant. There's nothing special about the version property. Not sure this merits a change to master either.

To each their own. I strongly disagree with that view, but whatever

Ah, I just noticed the link in your description. Regardless, all pull requests must be against develop? As mentioned in the contributing doc. I'll remove this property in the next release though.

This is literally going to every single person who has this in their bower.json. I'm not bothering with reading each contrib doc. I do apologize for not following it, but too many to do.

I understand. Thanks for the heads up though, and like I said, I'll remove this in the near future.

Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property


Add info back into configuration

Change Overview
Add non-mandatory Azure information back into config structure
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[x] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Test Plan

[ ] :muscle: Manual
[x] :zap: Unit test
[ ] :green_heart: E2E

Are the downstream callers being changed to use the config values from the map?

Are the downstream callers being changed to use the config values from the map?

@pavannd1  Downstream callers will store these information alongside with clientID, tenantID, clientSecret and other config information. At the moment, it it intended for information surfacing, i.e. showing end-user the complete suite of config being used for Azure Client. No data management functional changes.


Update --tasks list option in interface documentation

Added information about the --tasks list option to the interface documentation.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


feat(rust): implement channel tunneling, update ockamd to use it

All of this is rolled into #620, so I'm closing this PR in favor of that.


Fix TagGroup label alignment

Uses span instead of label since we aren't labelling a form element
Uses gap so that the tags line up with the label

✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Test TagGroup label is span, and left-most tags align vertically with the label above.
🧢 Your Project:

lgtm, we should probably run chromatic just to be sure though

We haven't added chromatic stories for TagGroup yet fyi

Oh ok


Huge HTML hangs whole server

Example: https://www.win.tue.nl/~aeb/natlang/ie/tochB.html
This page is really big, so okay, txtdot proxy can't parse it in reasonable time. But it hangs the whole server, and after client gets timeout error, txtdot still does not accept any requests, what makes DoS attacks as simple as possible: attacker needs only one request.
Using NodeJS profiler, I found out that JSDOM takes almost all the time.
What we can do:

Set a timeout for server response, so Fastify won't wait page processing to complete; connectionTimeout seems to be the solution, but I'm not sure.
Switch to other HTML processing library which provides DOM API (sorted by last commit date: linkedom, happy-dom, cheerio).
Rewrite Readability so it won't need DOM API; and/or rewrite it in Rust.

actually there is a problem with this function

We should probably get rid of dom and do it on the regex. I removed the code where the links change and the server responds and doesn't hang.


HHH-18949 fix underscores within uppercase names

[Please describe here what your change is about]

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

https://hibernate.atlassian.net/browse/HHH-18949

This needs to be back-ported to 6.6.

This needs to be back-ported to 6.6.

See https://github.com/hibernate/hibernate-orm/pull/9440


Support for Matter 1.4 Water Heater

Proposed change

Adding support for Matter 1.4 Water Heater :
Testing

Matter EFR32 Water Heater Example
Markdown instructions: WaterHeater_websocket_testing.md

Clusters

0x0094: WaterHeaterManagement
0x009E: Mode_WaterHeater

ID (Decimal)
ID (hex)
Name

144
0x0090
Electrical Power Measurement

145
0x0091
Electrical Energy Measurement

148
0x0094
Water Heater Management

152
0x0098
Device Energy Management

156
0x009C
Power Topology

158
0x009E
Water Heater Mode

159
0x009F
Device Energy Management Mode

513
0x0201
Thermostat

Type of change

[ ] Dependency upgrade
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New integration (thank you!)
[X] New feature (which adds functionality to an existing integration)
[ ] Deprecation (breaking change to happen in the future)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information
WaterHeaterManagement Cluster on Endpoint 2
WaterHeaterMode Cluster on Endpoint 2

3 modes: [{"0":"Off","1":0,"2":[{"1":16384}]},{"0":"Manual","1":1,"2":[{"1":16385}]},{"0":"Timed","1":2,"2":[{"1":16386}]}]

Link to documentation pull request:

Checklist

[ ] The code change is tested and works locally.
[ ] Local tests pass. Your PR cannot be merged unless tests pass
[ ] There is no commented out code in this PR.
[ ] I have followed the development checklist
[ ] I have followed the perfect PR recommendations
[ ] The code has been formatted using Ruff (ruff format homeassistant tests)
[x] Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] The manifest file has all fields filled out correctly.
Updated and included derived files by running: python3 -m script.hassfest.
[ ] New or updated dependencies have been added to requirements_all.txt.
Updated by running python3 -m script.gen_requirements_all.
[ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.

To help with the load of incoming pull requests:

[ ] I have reviewed two other open pull requests in this repository.

Adding Markdown instructions: WaterHeater_websocket_testing.md

Water Heater is now also supported by Espressif's SDK for Matter:
https://github.com/espressif/esp-matter/blob/main/SUPPORTED_DEVICE_TYPES.md?plain=1#L85


fix: image orientation on android

Motivation
Fix camera image's orientation issue on android #1701
Inspired by stack overflow
Test Plan
Use launchCamera to take photo, the assets returned should display correctly on Image Component.
Tested on Pixel 4a (android 12).

Any updates on getting this merged, currently running into the issue at #1701 as well.

why dont just returned the orientation value in the payload? I don’t think this will be approved.

@Johan-dutoit  any update on this PR?

Bump

This would resolve my issue #1900. I was going to make the same changes.

When this PR will commit approve?

I don't feel comfortable adding this code to rotate the image.  As Axeljeremy7 suggested, it might be better to include the orientation of the image.
Happy to be convinced otherwise.

Yeah, we either need to provide a rotate method via the library or as options on the input. As a default I don't think this is safe.


Proposal: Show appropriate error when app with native extensions are built with unsupported builder

Problem:  For most apps, npm-install runs fine on the base builder. But when the app requires compilation of native extensions using node-gyp, the buildpack requires the full builder because node-gyp requires python and the module may require other shared objects.
Reproducing the issue

Remove the builder line in integration.json

Run this test

You can see it fails the build step with:

[builder] Paketo NPM Install Buildpack 1.2.3
[builder]   Resolving installation process
[builder]     Process inputs:
[builder]       node_modules      -> "Found"
[builder]       npm-cache         -> "Not found"
[builder]       package-lock.json -> "Found"
[builder]
[builder]     Selected NPM build process: 'npm rebuild'
[builder]
[builder]   Executing build process
[builder]     Running 'npm run-script preinstall --if-present'
[builder]     Running 'npm rebuild --nodedir=/layers/paketo-buildpacks_node-engine/node'
[builder]<EMAIL_ADDRESS>/workspace
[builder]     +--<EMAIL_ADDRESS>[builder] npm rebuild failed: exit status 1
[builder]     | +--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>deduped
[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | `--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | | `--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | | `--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>deduped
[builder]     |   | `--<EMAIL_ADDRESS>[builder]     |   |   +--<EMAIL_ADDRESS>[builder]     |   |   | +--<EMAIL_ADDRESS>deduped
[builder]     |   |   | `--<EMAIL_ADDRESS>[builder]     |   |   `--<EMAIL_ADDRESS>[builder]     |   |     +--<EMAIL_ADDRESS>[builder]     |   |     `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | | +--<EMAIL_ADDRESS>[builder]     |   | | | `--<EMAIL_ADDRESS>deduped
[builder]     |   | | `--<EMAIL_ADDRESS>[builder]     |   | |   `--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>[builder]     |   |   +--<EMAIL_ADDRESS>[builder]     |   |   | +--<EMAIL_ADDRESS>[builder]     |   |   | +--<EMAIL_ADDRESS>[builder]     |   |   | | `--<EMAIL_ADDRESS>[builder]     |   |   | |   `--<EMAIL_ADDRESS>[builder]     |   |   | +--<EMAIL_ADDRESS>[builder]     |   |   | +--<EMAIL_ADDRESS>deduped
[builder]     |   |   | `--<EMAIL_ADDRESS>[builder]     |   |   |   `--<EMAIL_ADDRESS>[builder]     |   |   +--<EMAIL_ADDRESS>deduped
[builder]     |   |   `--<EMAIL_ADDRESS>[builder]     |   |     +--<EMAIL_ADDRESS>deduped
[builder]     |   |     +--<EMAIL_ADDRESS>deduped
[builder]     |   |     `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>[builder]     |   | | `--<EMAIL_ADDRESS>[builder]     |   | |   `--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>[builder]     |   |   `--<EMAIL_ADDRESS>[builder]     |   `--<EMAIL_ADDRESS>[builder]     +--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | |   +--<EMAIL_ADDRESS>[builder]     | |   `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | |   `--<EMAIL_ADDRESS>[builder]     | | |     +--<EMAIL_ADDRESS>[builder]     | | |     `--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | |   `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | +--<EMAIL_ADDRESS>[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | |   +--<EMAIL_ADDRESS>[builder]     | | |   +--<EMAIL_ADDRESS>deduped
[builder]     | | |   +--<EMAIL_ADDRESS>[builder]     | | |   +--<EMAIL_ADDRESS>[builder]     | | |   +--<EMAIL_ADDRESS>deduped
[builder]     | | |   +--<EMAIL_ADDRESS>[builder]     | | |   | `--<EMAIL_ADDRESS>deduped
[builder]     | | |   `--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | | +--<EMAIL_ADDRESS>[builder]     | | | +--<EMAIL_ADDRESS>deduped
[builder]     | | | +--<EMAIL_ADDRESS>[builder]     | | | +--<EMAIL_ADDRESS>deduped
[builder]     | | | +--<EMAIL_ADDRESS>deduped
[builder]     | | | +--<EMAIL_ADDRESS>[builder]     | | | | +--<EMAIL_ADDRESS>[builder]     | | | | +--<EMAIL_ADDRESS>[builder]     | | | | | `--<EMAIL_ADDRESS>[builder]     | | | | `--<EMAIL_ADDRESS>deduped
[builder]     | | | +--<EMAIL_ADDRESS>deduped
[builder]     | | | `--<EMAIL_ADDRESS>[builder]     | | |   `--<EMAIL_ADDRESS>deduped
[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | +--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | | `--<EMAIL_ADDRESS>[builder]     | |   +--<EMAIL_ADDRESS>[builder]     | |   +--<EMAIL_ADDRESS>[builder]     | |   | +--<EMAIL_ADDRESS>deduped
[builder]     | |   | `--<EMAIL_ADDRESS>[builder]     | |   +--<EMAIL_ADDRESS>[builder]     | |   +--<EMAIL_ADDRESS>deduped
[builder]     | |   +--<EMAIL_ADDRESS>[builder]     | |   | `--<EMAIL_ADDRESS>deduped
[builder]     | |   `--<EMAIL_ADDRESS>[builder]     | +--<EMAIL_ADDRESS>[builder]     | `--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | +--<EMAIL_ADDRESS>deduped
[builder]     |   | `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   | `--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>deduped
[builder]     |   +--<EMAIL_ADDRESS>[builder]     |   `--<EMAIL_ADDRESS>[builder]     `--<EMAIL_ADDRESS>[builder]       +--<EMAIL_ADDRESS>[builder]       +--<EMAIL_ADDRESS>[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | +--<EMAIL_ADDRESS>deduped
[builder]       | `--<EMAIL_ADDRESS>deduped
[builder]       `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         | `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>deduped
[builder]         | `--<EMAIL_ADDRESS>deduped
[builder]         +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>[builder]         | | +--<EMAIL_ADDRESS>[builder]         | | +--<EMAIL_ADDRESS>[builder]         | | +--<EMAIL_ADDRESS>[builder]         | | `--<EMAIL_ADDRESS>[builder]         | |   `--<EMAIL_ADDRESS>[builder]         | `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>[builder]         | | +--<EMAIL_ADDRESS>deduped
[builder]         | | +--<EMAIL_ADDRESS>[builder]         | | +--<EMAIL_ADDRESS>[builder]         | | `--<EMAIL_ADDRESS>[builder]         | |   +--<EMAIL_ADDRESS>deduped
[builder]         | |   +--<EMAIL_ADDRESS>deduped
[builder]         | |   `--<EMAIL_ADDRESS>deduped
[builder]         | `--<EMAIL_ADDRESS>[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   | `--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   | `--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   | `--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   | +--<EMAIL_ADDRESS>deduped
[builder]         |   | `--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   | `--<EMAIL_ADDRESS>deduped
[builder]         |   +--<EMAIL_ADDRESS>[builder]         |   +--<EMAIL_ADDRESS>deduped
[builder]         |   `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         | `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>deduped
[builder]         +--<EMAIL_ADDRESS>[builder]         | +--<EMAIL_ADDRESS>[builder]         | `--<EMAIL_ADDRESS>[builder]         +--<EMAIL_ADDRESS>[builder]         | `--<EMAIL_ADDRESS>deduped
[builder]         `--<EMAIL_ADDRESS>[builder]
[builder]
[builder]     ><EMAIL_ADDRESS>install /workspace/node_modules/sqlite3
[builder]     > node-pre-gyp install --fallback-to-build
[builder]
[builder]     gyp ERR! find Python
[builder]     gyp ERR! find Python Python is not set from command line or npm configuration
[builder]     gyp ERR! find Python Python is not set from environment variable PYTHON
[builder]     gyp ERR! find Python checking if "python" can be used
[builder]     gyp ERR! find Python - "python" is not in PATH or produced an error
[builder]     gyp ERR! find Python checking if "python2" can be used
[builder]     gyp ERR! find Python - "python2" is not in PATH or produced an error
[builder]     gyp ERR! find Python checking if "python3" can be used
[builder]     gyp ERR! find Python - "python3" is not in PATH or produced an error
[builder]     gyp ERR! find Python
[builder]     gyp ERR! find Python **********************************************************
[builder]     gyp ERR! find Python You need to install the latest version of Python.
[builder]     gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
[builder]     gyp ERR! find Python you can try one of the following options:
[builder]     gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
[builder]     gyp ERR! find Python   (accepted by both node-gyp and npm)
[builder]     gyp ERR! find Python - Set the environment variable PYTHON
[builder]     gyp ERR! find Python - Set the npm configuration variable python:
[builder]     gyp ERR! find Python   npm config set python "/path/to/pythonexecutable"
[builder]     gyp ERR! find Python For more information consult the documentation at:
[builder]     gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
[builder]     gyp ERR! find Python **********************************************************
[builder]     gyp ERR! find Python
[builder]     gyp ERR! configure error
[builder]     gyp ERR! stack Error: Could not find any Python installation to use
[builder]     gyp ERR! stack     at PythonFinder.fail (/layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:307:47)
[builder]     gyp ERR! stack     at PythonFinder.runChecks (/layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:136:21)
[builder]     gyp ERR! stack     at PythonFinder.<anonymous> (/layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:179:16)
[builder]     gyp ERR! stack     at PythonFinder.execFileCallback (/layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:271:16)
[builder]     gyp ERR! stack     at exithandler (child_process.js:301:5)
[builder]     gyp ERR! stack     at ChildProcess.errorhandler (child_process.js:313:5)
[builder]     gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
[builder]     gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:246:12)
[builder]     gyp ERR! stack     at onErrorNT (internal/child_process.js:415:16)
[builder]     gyp ERR! stack     at process._tickCallback (internal/process/next_tick.js:63:19)
[builder]     gyp ERR! System Linux 4.19.76-linuxkit
[builder]     gyp ERR! command "/layers/paketo-buildpacks_node-engine/node/bin/node" "/layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "--fallback-to-build" "--module=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node" "--module_name=node_sqlite3" "--module_path=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64" "--napi_version=6" "--node_abi_napi=napi" "--napi_build_version=0" "--node_napi_label=node-v64" "--nodedir=/layers/paketo-buildpacks_node-engine/node"
[builder]     gyp ERR! cwd /layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3
[builder]     gyp ERR! node -v v10.22.0
[builder]     gyp ERR! node-gyp -v v5.1.0
[builder]     gyp ERR! not ok
[builder]     node-pre-gyp ERR! build error
[builder]     node-pre-gyp ERR! stack Error: Failed to execute '/layers/paketo-buildpacks_node-engine/node/bin/node /layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64 --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64 --nodedir=/layers/paketo-buildpacks_node-engine/node' (1)
[builder]     node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/node_modules/node-pre-gyp/lib/util/compile.js:83:29)
[builder]     node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
[builder]     node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
[builder]     node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
[builder]     node-pre-gyp ERR! System Linux 4.19.76-linuxkit
[builder]     node-pre-gyp ERR! command "/layers/paketo-buildpacks_node-engine/node/bin/node" "/workspace/node_modules/sqlite3/node_modules/.bin/node-pre-gyp" "install" "--fallback-to-build"
[builder]     node-pre-gyp ERR! cwd /layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3
[builder]     node-pre-gyp ERR! node -v v10.22.0
[builder]     node-pre-gyp ERR! node-pre-gyp -v v0.11.0
[builder]     node-pre-gyp ERR! not ok
[builder]     Failed to execute '/layers/paketo-buildpacks_node-engine/node/bin/node /layers/paketo-buildpacks_node-engine/node/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js configure --fallback-to-build --module=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64/node_sqlite3.node --module_name=node_sqlite3 --module_path=/layers/paketo-buildpacks_npm-install/modules/node_modules/sqlite3/lib/binding/node-v64-linux-x64 --napi_version=6 --node_abi_napi=napi --napi_build_version=0 --node_napi_label=node-v64 --nodedir=/layers/paketo-buildpacks_node-engine/node' (1)
[builder]     npm ERR! code ELIFECYCLE
[builder]     npm ERR! errno 1
[builder]     npm ERR<EMAIL_ADDRESS>install: `node-pre-gyp install --fallback-to-build`
[builder]     npm ERR! Exit status 1
[builder]     npm ERR!
[builder]     npm ERR! Failed at the<EMAIL_ADDRESS>install script.
[builder]     npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[builder]
[builder]     npm ERR! A complete log of this run can be found in:
[builder]     npm ERR!     /home/cnb/.npm/_logs/2020-09-25T15_10_10_126Z-debug.log
[builder]
[builder]
[builder] ERROR: failed to build: exit status 1
ERROR: failed to build: executing lifecycle. This may be the result of using an untrusted builder: failed with status code: 145

Proposed implementation

During build phase,  see if the vendored/downloaded node_modules contain native extensions.
This could be checked by detecting the presence of the binding.gyp file at the root of every module.
E.g. https://github.com/paketo-buildpacks/npm-install/blob/v0.2.0/integration/testdata/vendored/node_modules/sqlite3/binding.gyp

If it contains native extensions, check for the build image supports compiling native extensions
Maybe check for some heuristics like python

If the app contains native extensions and is using a build image that can't support compiling it, fail build with appropriate error message logged.

This would be great. Even better if the error message can tell users to try again with the Full stack.

After further discussion with paketo core team, it's best if we do not check for builder support in the build phase. We could simply elaborate the build failure log msg with a few common reasons for build failure instead.