[BUG] Unable to access Node IP addresses over HTTPS on VM router in Harvester cluster v1.1.1

Describe the bug

In the Harvester cluster whose management network has a VLAN ID, the VM will be unable to access the host port or node port with the host IP where the VM is running.
The customer is experiencing issues accessing Node addresses over HTTPS on a VM acting as a router on a harvester cluster. The customer has tried troubleshooting steps, such as checking MTUs and firewall rules but has not resolved the issue. The customer also mentioned that the issue only started in v1.1.1. The customer needs to resolve the issue as soon as possible.
This issue only happens when the VM is running on the node.
Example:
VM1 is running inside Node1. The VM1 can ping and ssh the Node1 but cannot https to the node address. The VM1 can access the other nodes without issues through ping, ssh, and https.
If the customer moves VM1 to Node2, The VM1 can ping and ssh the Node2 but cannot https to the node address.
To Reproduce
Steps to reproduce the behavior:

Create a cluster with the management network on VLAN 1001.
Add a VM network with VLAN 1001 to communicate from the VMs to the node.
Attempt to access HTTPS on port 443 on the hosts or the VIP address using the VM as a router.

Expected behavior

The customer cannot access HTTPS on the Node address when a VM runs inside the node. To the other nodes, the HTTPS communication works fine.
Support bundle

Environment

Harvester ISO version:  Harvester 1.1.1
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): Baremetal with Dell PowerEdge R630

Additional context
Add any other context about the problem here.

Workaround: Execute the following command in harvester nodes.
sysctl -w net.bridge.bridge-nf-call-iptables=0

After restarting nodes, the command should be executed again.

@yaocw2020 why do we have to disable bridge-nf-call-iptables? isn't this a security risk?

might be related to https://rancher-users.slack.com/archives/C01GKHKAG0K/p1692691256324529

I'm not able to sufficiently reproduce this in our lab and was wondering if any members of the community would be willing to collect some diagnostic info to help me troubleshoot the root cause to help develop a fix.
On the Harvester node that the VM tries to reach over HTTPS, disable the workaround by restoring the bridge-nf-call-iptables sysctl to 1:
# sysctl -w net.bridge.bridge-nf-call-iptables=1

Then, add tracing rules (replace $NODE_VIP with the node's VIP or HTTPS endpoint the issue reproduces with, and you can replace --dport 6443 with whatever port number the VM is trying to reach; also replace $VM_IP with the VM's IP address)
# iptables -t raw -A PREROUTING -p tcp --destination $NODE_VIP --dport 6443 -j TRACE
# iptables -t raw -A OUTPUT -p tcp --destination $NODE_VIP --dport 6443 -j TRACE
# iptables -t raw -A PREROUTING -p tcp --destination $VM_IP -j TRACE
# iptables -t raw -A OUTPUT -p tcp --destination $VM_IP -j TRACE

Now, inside their VM that is trying to reach the node it is on over HTTPS, try to reach it (again, replace NODE_VIP and 6443 accordingly):
$ curl --insecure https://$node_vip:6443/

Back to the Harvester node, there should now be iptables tracelogs in the kernel logs:
# dmesg -T > kernel.log
# iptables-save > iptables.txt

:exclamation:
Please attach the kernel.log and iptables.txt output for review. Alternatively, send them to<EMAIL_ADDRESS>and reference this GitHub issue.

To reverse the modifications to the Harvester node and restore the workaround (replace $NODE_VIP and 6443 as well as VM_IP with their respective values):
# iptables -t raw -D PREROUTING -p tcp --destination $NODE_VIP --dport 6443 -j TRACE
# iptables -t raw -D OUTPUT -p tcp --destination $NODE_VIP --dport 6443 -j TRACE
# iptables -t raw -D PREROUTING -p tcp --destination $VM_IP -j TRACE
# iptables -t raw -D OUTPUT -p tcp --destination $VM_IP -j TRACE
# sysctl -w net.bridge.bridge-nf-call-iptables=0

after some experiments on customer's testbed, the cause is pretty much the same as issue#4359 https://github.com/harvester/harvester/issues/4359.
The tcpdump from the downstream nodes for curl -k to VIP. The http(s) packet fail to be forwarded from the mgmt-br to the pod with the http service.
05:14:32.556491 vethf219c7e5 P   ifindex 60 3e:75:17:d4:db:ab ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.45190 > <IP_ADDRESS>.80: Flags [S], seq<PHONE_NUMBER>, win 64240, options [mss 1460,sackOK,TS val 294234997 ecr 0,nop,wscale 7], length 0
05:14:32.556506 mgmt-br In  ifindex 4 3e:75:81:00:03:e8 ethertype IPv4 (0x0800), length 84: IP13 (invalid)

After correctly untag the packet, the packet flow seems to be correct. The packet from <IP_ADDRESS> to VIP will be SNAT/DNAT to <IP_ADDRESS> and <IP_ADDRESS>. The ACK to the http also correctly convert back to <IP_ADDRESS> to <IP_ADDRESS>.
05:56:53.746783 vethf219c7e5 P   ifindex 60 3e:75:17:d4:db:ab ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.60844 > <IP_ADDRESS>.80: Flags [S], seq 800135625, win 64240, options [mss 1460,sackOK,TS val 353479517 ecr 0,nop,wscale 7], length 0
05:56:53.746803 mgmt-br In  ifindex 4 3e:75:17:d4:db:ab ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.60844 > <IP_ADDRESS>.80: Flags [S], seq 800135625, win 64240, options [mss 1460,sackOK,TS val 353479517 ecr 0,nop,wscale 7], length 0
05:56:53.746820 flannel.1 Out ifindex 11 a2:6d:c3:4c:09:20 ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.37035 > <IP_ADDRESS>.80: Flags [S], seq 800135625, win 64240, options [mss 1460,sackOK,TS val 353479517 ecr 0,nop,wscale 7], length 0
05:56:53.747092 flannel.1 In  ifindex 11 46:99:9e:8a:4c:ba ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.80 > <IP_ADDRESS>.37035: Flags [S.], seq 671964721, ack 800135626, win 64308, options [mss 1410,sackOK,TS val 331341449 ecr 353479517,nop,wscale 7], length 0
05:56:53.747109 mgmt-br Out ifindex 4 10:70:fd:86:eb:f2 ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.80 > <IP_ADDRESS>.60844: Flags [S.], seq 671964721, ack 800135626, win 64308, options [mss 1410,sackOK,TS val 331341449 ecr 353479517,nop,wscale 7], length 0
05:56:53.747113 mgmt-bo Out ifindex 5 10:70:fd:86:eb:f2 ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.80 > <IP_ADDRESS>.60844: Flags [S.], seq 671964721, ack 800135626, win 64308, options [mss 1410,sackOK,TS val 331341449 ecr 353479517,nop,wscale 7], length 0
05:56:53.747117 enp1s0f0np0 Out ifindex 2 10:70:fd:86:eb:f2 ethertype IPv4 (0x0800), length 80: <IP_ADDRESS>.80 > <IP_ADDRESS>.60844: Flags [S.], seq 671964721, ack 800135626, win 64308, options [mss 1410,sackOK,TS val 331341449 ecr 353479517,nop,wscale 7], length 0

However, the downstream node doesn't seem to receive the ACK packet. I believe the ACK packet should go to the dhcpd VM (router) first, then sent back to the downstream VM. Since there's no tcpdump on the VM. I need to find out where the packet goes.

Do the ping traffic flow for comparison
10:42:50.291340 vethcc2eab56 P   ifindex 69 3e:75:17:d4:db:ab ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 10, seq 1, length 64
10:42:50.291398 vethaa4698be Out ifindex 50 3e:75:17:d4:db:ab ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 10, seq 1, length 64
10:42:50.291402 mgmt-br P   ifindex 4 3e:75:81:00:03:e8 ethertype IPv4 (0x0800), length 108: IP13 (invalid)
10:42:50.291684 calia0c43ffb637 In  ifindex 49 2a:dd:db:e6:60:37 ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo request, id 10, seq 1, length 64
10:42:50.291729 calia0c43ffb637 Out ifindex 49 ee:ee:ee:ee:ee:ee ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 10, seq 1, length 64
10:42:50.291888 vethaa4698be P   ifindex 50 da:46:88:c9:66:f6 ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 10, seq 1, length 64
10:42:50.291906 vethcc2eab56 Out ifindex 69 da:46:88:c9:66:f6 ethertype IPv4 (0x0800), length 104: <IP_ADDRESS> > <IP_ADDRESS>: ICMP echo reply, id 10, seq 1, length 64

The src ip address of ping will be converted from <IP_ADDRESS> to <IP_ADDRESS>. And the ping reply will goes back to <IP_ADDRESS> which is then forwarded to vethaa4698be, the interface that router node is bound to. The router then forward it back to the downstream VM.
Unlike the http(s) traffic, the src ip address remains the same <IP_ADDRESS> and of course the default route is taken to route the packet via mgmt-br and mgmt-br. The router VM has no chance receive the packet.
Will need to check which iptables rule is applied for ICMP to convert the src IP address as the next step.

I can simply reproduce with 2 VMs, 1 VM as a router and the other VM route vi the 1nd VM.
disable net.bridge.bridge-nf-call-iptables can workaround the issue.
The packet should flow between veth interfaces which belongs to the router VM, but it goes to the outbond uplink interface of the Host.
There's should be some iptables rule which is not applied correctly.

Need the https://github.com/harvester/network-controller-harvester/pull/83 to be approved. We may need to evaluate the risk first.

I have written a document before to explain the case. Please refer to Harvester-SNAT-problem.md. @mingshuoqiu @iosifnicolae2 @connorkuehl

The solution in https://github.com/harvester/network-controller-harvester/pull/119
doesn't fix the issue and introduce another https://github.com/harvester/harvester/issues/6747. Need to fix it for the issue.

As per discussed, we have the following test plan
Environment:

Multiple nodes Harvester cluster (not mandatory to have vlan on management network)

Test scenarios:

Create virtual machine vm1 on node1 with management network, try to access port 443 and 80 on node1 from vm1
vm1 should still can access port 443 and 80 on other nodes
Migrate vm1 to node2, try to access 443 and 80 on node2 from vm1
After migration vm1 can still access port on other nodes
Reboot the current node where vm1 located on it, check can access specific port on node1 after reboot.
Upgrade from v1.3.2 to v1.4-head, and check test scenarios 1 - 4

Verifying on v1.4-d57f2aec-head (24/11/25)
Result
$\color{green}{\textsf{PASS}}$ Access node2 port 443 and 80 from vm1, where vm1 originally located on node2 $~~$

Originally located in node2

Can access port 443 and 80 on node2
opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{green}{\textsf{PASS}}$ Access node1 port 443 and 80 from vm1, where vm1 originally located on node2 $~~$

Can access port 443 and 80 on node1opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{green}{\textsf{PASS}}$ Migrate vm1 to node1, and access node1 port 443 and 80 $~~$

Migrate from node2 to node1

Can access port 443 and 80 on node1
opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{green}{\textsf{PASS}}$ Migrate vm1 to node1, and access node2 port 443 and 80 $~~$

Can access port 443 and 80 on node2
opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{green}{\textsf{PASS}}$ After rebooting node machine, can access current node's port 443 and 80 $~~$

Currently vm1 located on node2

After migrated, vm would move to node1

Can access port 443 and 80 on node1 from vm1
opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{green}{\textsf{PASS}}$ After rebooting node machine, can access other node's port 443 and 80 $~~$

Can access port 443 and 80 on node2 from vm1
opensuse@vm1:~> curl <IP_ADDRESS>:443

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

opensuse@vm1:~> curl <IP_ADDRESS>:80
<a href="https://<IP_ADDRESS>/">Found.

$\color{blue}{\textsf{Ongoing}}$ After upgrade to v1.4-head, can access the current node's port 443 and 80 $~~$

Test Information

Test Environment: Two nodes bare-metal machines
VLAN id: 2021
Harvester version: v1.4-d57f2aec-head (24/11/25)

Verify Steps
Access node port 443 and 80 from vm on the same node

Prepare two nodes Harvester which management interface set to VLAN ID

Created two nodes Harvester

Create vm1 on management interface

Check which node the vm located on (e.g node2)

ssh to vm1

Access node 2 port 443 and 80 with curl command

$ curl node-ip:443
$ curl node-ip:80

Access node 1 port 443 and 80 with curl command
Check can get response from port 443 and 80

After migrate vm, access node port 443 and 80 from vm on the same node

Prepare two nodes Harvester which management interface set to VLAN ID

Created two nodes Harvester

Create vm1 on management interface

Check which node the vm located on (e.g node2)

Migrate vm1 to node1

ssh to vm1

Access node 1 port 443 and 80 with curl command

$ curl node-ip:443
$ curl node-ip:80

Access node 2 port 443 and 80 with curl command
Check can get response from port 443 and 80

The net.bridge.bridge-nf-call-iptables will be toggled back to 1 after restart rke2. Need to monitor and toggle it back

The net.bridge.bridge-nf-call-iptables will be toggled back to 1 after restart rke2. Need to monitor and toggle it back

Failed - Migrate vm1 to node1, can't access node1 port 443 and 80
Failed - After rebooting node machine, can't access current node's port 443 and 80
@mingshuoqiu there are two failed cases here. The second is related to node reboot. How about the first failed case?

@mingshuoqiu Is the failed case also caused by rke2 restart?

(Failed) Migrate vm1 to node1, can't access node1 port 443 and 80

Just confirmed that the VM migration (caused by reboot and manual operation) is caused by the RKE2 restart

Close this issue since we can track the rke2 restart behavior in issue #7041


add nodeSelector to run on a selection of nodes

We need to run this only on a few nodes or a group of nodes and not every node.
Add a nodeSelector to the values flie and in the node manifest.

E2E tests are failing due to credentials not found. Can someone please fix it?


add Strings/anagram_checker.py

code is already there.

true that.
it's the copied code from geeksforgeeks though.
On Sat, Sep 26, 2020 at 7:32 AM AKSHITA GUPTA<EMAIL_ADDRESS>wrote:

code is already there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/akshitagit/Python/pull/70#issuecomment-699348690, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADJN2D5ES2GVGC4S5PZG6CLSHVRV3ANCNFSM4R2UAW4A
.


Smart Dominant Speakers Function

What
Adds a function smartDominantSpeakers to react-components package that will return dominant speakers gracefully ordered.
This function can be consumed inside VideoGallery or similar components to get order remoteParticipants on the basis of their dominance.
Works for both audio only and video participants.
Why
Too many re-renders if we use the standard dominant speaker events without gracefully handling them.
How Tested

Process & policy checklist

[ ] I have updated the project documentation to reflect my changes if necessary.
[ ] I have read the CONTRIBUTING documentation.

Is this a breaking change?

[ ] This change causes current functionality to break.

I'm being more than usual pedantic about code minutiae because this is an involved algorithm. Readability is very important.

Appreciate it. I will be gone for a month so its more important that others find it easier to work with.


HJSON support with built in json language server

https://code.visualstudio.com/docs/languages/json
The json smart features currently support JSON with Comments and JSON only. It seems like it would be easy to add HJSON support, the main difference is # is permitted as a comment character. Unlike JSON with Comments, it's a standard with a published spec.
There is an hjson extension available but it doesn't support json schemas in the way the built in json language server does, therefore no hovers, autocomplete etc. It's just syntax highlighting
Are you accepting PRs for this change?

Sorry, I'm not in favor of adding additional JSON flavors to the JSON language server. This should be added by separate extensions. This is the best way to share the work (especially the long-term maintenance) and keep the JSON extension lean.  Also, it's hard to decide which flavors to support, and which not. Excuse my ignorance, but this is the first time I've heard of HJSON.
The good news is that it's not that hard to write a language support. The JSON language server internally uses the vscode-json-languageservice node module that contains most of the smarts (schema driven code assist, validation..) and supports plugin in a different parser.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


still same bug with version detection

i don't know what you have fixed in the ticket you closed.
still wrong vulnerabilities are listed for wrong version numbers.
[INF] Trying to detect Joomla on target...
[INF] Joomla detected sucessfully!
[INF] Trying to get Joomla version on target...
[INF] Joomla version is: 2.5.28
[INF] Searching for Joomla vulnerabilites for this version
[INF] Joomla! 3.4.4 < 3.6.4 - Account Creation / Privilege Escalation -> WRONG
[INF] Joomla! 3.7 - SQL Injection  -> WRONG
[INF] Joomla! 3.9.0 < 3.9.7 - CSV Injection -> WRONG
[INF] Joomla! 3.9.13 - 'Host' Header Injection  -> WRONG
[INF] Joomla! < 3.6.4 - Admin Takeover  -> WRONG
[INF] Joomla! 1.5 < 3.4.5 - Object Injection Remote Command Execution -> RIGHT
[INF] Joomla! 1.5 < 3.4.6 - Object Injection 'x-forwarded-for' Header Remote -> RIGHT
Code Execution
[INF] Joomla! 3.2.x < 3.4.4 - SQL Injection -> WRONG
[INF] Joomla! 3.4.6 - 'configuration.php' Remote Code Execution -> WRONG
[INF] Joomla! 3.2.1 - SQL Injection -> WRONG
[INF] Joomla! 3.0.2 - 'highlight.php' PHP Object Injection -> WRONG
[INF] Joomla! 3.0.3 - 'remember.php' PHP Object Injection -> WRONG

RegEx for Version Parsing 1-3 dots.
^(\d+.)?(\d+.)?(*|\d+)$

Hello @d4op!
First of all, sorry for closing your issue without any reason etc...
I think I've fixed the Joomla version problems, if you can test on your target again and verify will be helpful.
Best regards,
knightmare

yeah its fixed.
maybe you can print out exploit links for the vulns found using a additional parameter.


✖ listen EACCES: permission denied <IP_ADDRESS>:1337

Hi i have a problem with the INITIALIZATION.
i did all the previouse steps but it show me this message :✖ listen EACCES: permission denied <IP_ADDRESS>:1337
can you help me to fix that please ?

Hi @lightvortex01 :wave:,
Thanks for opening this issue. Can you please try to change the PORT to another one via the .env file and retry?

ok thx it work perfectly!


Rustup installs 64bit compiler on a 32bit Docker instance

This is what is in my dockerfile:
 RUN curl https://sh.rustup.rs -o rustup.sh && sh rustup.sh --default-toolchain nightly -y && rustup default nightly

Here are some details from the docker instance
root@cc25a7d3570a:~/test32# uname -a
 Linux cc25a7d3570a 4.4.0-97-generic #120-Ubuntu SMP Tue Sep 19 17:28:18 UTC 2017 i686 i686 i686 GNU/Linux
root@cc25a7d3570a:~/test32# rustc --version
rustc 1.23.0-nightly (2be4cc040 2017-11-01)
root@cc25a7d3570a:~/test32# rustup show
Default host: x86_64-unknown-linux-gnu

installed toolchains
--------------------

nightly-i686-unknown-linux-gnu (default)
nightly-x86_64-unknown-linux-gnu

active toolchain
----------------

nightly-i686-unknown-linux-gnu (default)
rustc 1.23.0-nightly (2be4cc040 2017-11-01)

I hand installed the i686 compiler by running rustup install nightly-i686-unknown-linux-gnu.
You can find the Dockerfile here

The 32 bit Dockerfile can be seen here: https://github.com/Wilfred/remacs/blob/master/docker/ubuntu/32bit/Dockerfile
If I set the default-host explicitly with --default-host i686-unknown-linux-gnu then the right thing happens. If I leave it up to rustup-init determining the host I get a mixed i686 and x86_64 Rust install which refuses to run (as you might expect).

I believe this has come up again, and we ought to see if we can fix it.  cf. #2111

I have investigated and I believe that this should be working with current rustup.  Could you please double-check @shaleh and let me know.  If it's not working, can you please add -x to the sh cmdline (i.e. sh -x rustup.sh ...) and paste from where it looks at /proc/self/exe to where it starts downloading the installer please?

It is my strong belief that this is no longer a problem on x86, and with the patch for #2111 it'll be fixed for aarch64/armv7 too.  If it is still an issue, please reopen with details as above.


Changed deployed URL

https://cloud-assessment.prathmadev.workers.dev/ .. this is the url in which I have deployed my site

i also want to do this assessment how can i do it
i have install npm and node.js with wrangal can you tell me after full procedure what to do each and every step

Ya sure , if you have installed wrangler with npm and node js .. on your
local machine create one template folder using wrangler router template..
once created .. you can change in index.js file to make the changes..
whenever you want to check if the api is working you can run wrangler dev
.. it will run the local dev server.. when your project is ready you can
config and then publish it.
For coding guidelines, i followed the documentation of cloudflare..
https://developers.cloudflare.com/workers/
All the best!
On Wed, Oct 21, 2020 at 5:02 AM Shivam7-1<EMAIL_ADDRESS>wrote:

i also want to do this assessment how can i do it
i have install npm and node.js with wrangal can you tell me after full
procedure what to do each and every step
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare-hiring/cloudflare-2020-general-engineering-assignment/pull/21#issuecomment-713422657,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2E2FR3S57T3HTDPBQ4X5TSL2PTZANCNFSM4SZBHHEQ
.


Err installing Kale on Kubeflow on MicroK8s

Steps to bug:

Install kubeflow-lite on MicroK8s
Start a Jupyter notebook server on Kubeflow dashboard
Connecting to notebook server
Open a new terminal on that server
Type first step to install kale - pip install kubeflow-kale

ERR below:

Retested this on a fresh Ubuntu server instance on AWS, same outcome.

We now have instructions on how to use Kale here


feat/test-multiple-versions

Need to work out why it fails on Mac

There is still come context leaking between tests. This is because every test uses the same crashes directory test-app Crashes.


Add size increase for heightened Righteous Might spell effect

Fixes #10651

We are currently in a data entry freeze for CRB/APG data, due to the remaster. This will have to wait until we see if the spell is changed in the remaster.


Modify lambda packaging for requests layer creation

This is a companion ticket for vanotify-infra 480, which will create a lambda layer for the "requests" Python package.

[x] Modify lambda-functions.yml so it doesn't package requests for affected lambdas:

...notification-api$ grep -l requests lambda_functions/*/requirements-lambda.txt
lambda_functions/two_way_sms/requirements-lambda.txt
lambda_functions/vetext_incoming_forwarder_lambda/requirements-lambda.txt

Contrary to the verbiage of the infra ticket, do not remove requirements-lambda.txt files, which are still desirable for documentation.

I have made my first round of changes for this. I am waiting for infra dev to become available for me to deploy and test.

Work is complete (assuming no PR change requests).  This will be merged after 12/21 due to the upcoming release.

Hey team! Please add your planning poker estimate with Zenhub @cris-oddball @EvanParish @jakehova @k-macmillan @kalbfled @ldraney @trevor2718


Crash on start up 1.19 forge 41.1.0

It just wont start in my modpack, heres the logs but it always says couldnt load some random fish, https://mclo.gs/CrpDyQn

Maybe it’s not caused by this mod but by fish_of_thieves?

btw fish of thieves was a problem but curses still wont run on my modpack, heres the logs https://mclo.gs/jKHVXfn

im testing rn but i think thats for 1.19.1+ not 1.19

yep, javafml needs to be 41? https://mclo.gs/9s0FxFi

Yes, the latest version is for 1.19.1+ because it was at the time when 1.19.1 was already out, so nobody needs previous versions.
I think that issue is resolved now. Because I’m not "backporting" it. You could try to edit the mods.toml file in the jar, maybe it works.


Plugin breaks non-JS/TS code

I'd love to use this to bundle resources that may include Deno code and non-JS code (like CSS/SCSS files).
But adding the plugin to my ESBuild configuration breaks if there are files that aren't TypeScript/JavaScript.
IMO, if this plugin doesn't know how to handle these files, it should just skip them and allow other plugins (or esbuild itself) to handle them.
Reproduction
I've got a minimal reproduction here:
https://github.com/NfNitLoop/deno-loader-bug
With a config like this:
import * as esbuild from<EMAIL_ADDRESS>import { denoPlugins } from "jsr<EMAIL_ADDRESS>
const result = await esbuild.build({
  plugins: [
    // ...denoPlugins()
  ],
  entryPoints: [
    "src/mod.ts",
    "src/style.css",
  ],
  outdir: "dist",
  bundle: true,
  format: "esm",
});
esbuild.stop();

This works, but if you uncomment the denoPlugins() line you get errors:

✘ [ERROR] Expected a JavaScript or TypeScript module, but identified a Unknown module. Importing these types of modules is currently not supported.
Specifier: file:///Users/codyc/code/bugs/deno-loader-bug/src/style.css [plugin deno-loader]

FWIW, I previously rolled my own code that was similar to esbuild-deno-loader, but decided to adopt esbuild-deno-loader to support JSR imports.  My loader explicitly only applied to particular kinds of imports (back then, http[s] imports), so it didn't run into this issue. So I expect filtering to just js/ts/jsx/tsx imports here might be a quick fix?

The code sited below seems to be the cause of the issue. It assumes that all files can be handled by loadEsm, even files that are not imported. For example, if you add a css file entrypoint to the list with the postcss plugin before or after the deno plugin, it will fail because the deno plugins onLoad function will be called even for css files.
The TODO below should be removed and the onLoad filter should limit it to only being called for files deno would handle, like ts, tsx, js, jsx, and wasm.
https://github.com/lucacasonato/esbuild_deno_loader/blob/main/src/plugin_deno_loader.ts#L360
function onLoad(
  args: esbuild.OnLoadArgs,
): Promise<esbuild.OnLoadResult | null> | undefined {
  if (args.namespace === "file" && isInNodeModules(args.path)) {
    // inside node_modules, just let esbuild do it's thing
    return undefined;
  }
  const specifier = esbuildResolutionToURL(args);
  return loaderImpl.loadEsm(specifier);
}
// TODO(lucacasonato): once https://github.com/evanw/esbuild/pull/2968 is fixed, remove the catch all "file" handler
build.onLoad({ filter: /.*/, namespace: "file" }, onLoad);

Another option is changing the onLoad filter to exclude css. That way the default css loader from esbuild or other plugins after it will be used instead. To work around this issue, I plan on just creating an esbuild plugin that will call the default css loader for css files and put it and any css related esbuild plugins before the deno plugin.

I was wrong in my last comment about a potential way to workaround the issue. Adding a plugin before it with an onLoad callback won't prevent it from also calling the onLoad callback in the next plugin. The only way to prevent it from getting handled by the next plugin is to mark it as external in an onResolve callback. But esbuild doesn't allow you to set entrypoints as being external, so that won't work either.
I'm going to fork this PR and update it to have more restrictive file type filters for it's onLoad callback that I previously mentioned so that it isn't catching other files that you wouldn't want the deno plugin to handle like css and image files. I'll create a PR to try to upstream it into luca's esbuild_deno_loader but might also publish my fork so that I can use it immediately. I'll add an update here on how to use it for anyone else that encounters this issue. Then I'll yank my fork from jsr once the issue is resolved in this repository.

I have an idea on how to work around this. Let me try it.

I have an idea on how to work around this. Let me try it.

Okay, I'll wait for you to try first. I was just going to try myself this weekend but I can wait.

If the next release is made today or tomorrow, I'll test it out to verify it is working right, allowing me to build css entrypoints using the postcss esbuild plugin I've been working on.

I can still reproduce this against [https://jsr.io/<EMAIL_ADDRESS>But it looks like that's because #142 isn't included in that release.

This is still broken in v0.11.0, though with a slightly different error message.
Task build deno run -A example.ts
✘ [ERROR] [unreachable] Not an ESM module. [plugin deno-loader]

error: Uncaught (in promise) Error: Build failed with 1 error:
error: [unreachable] Not an ESM module.
    at failureErrorWithLog (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:1651:15)
    at file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:1059:25
    at runOnEndCallbacks (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:1486:45)
    at buildResponseToResult (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:1057:7)
    at file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:1086:16
    at responseCallbacks.<computed> (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:704:9)
    at handleIncomingPacket (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:764:9)
    at Readable.readFromStdout (file:///Users/codyc/Library/Caches/deno/npm/registry.npmjs.org/esbuild/0.20.2/lib/main.js:680:7)
    at Readable.emit (ext:deno_node/_events.mjs:393:28)
    at addChunk (ext:deno_node/_stream.mjs:2438:16)

Removing denoModules() from the esbuild configuration allows esbuild's default behavior (which just passes those files through unmodified.)

Should I open a new issue? I can't re-open this one.

I opened a new one:  https://github.com/lucacasonato/esbuild_deno_loader/issues/159
I'm about to put up a PR for resolving it. Hopefully I can get it approved/merged.

Here is a link to my PR that I believe will actually resolve this issue.
https://github.com/lucacasonato/esbuild_deno_loader/pull/160


Action "Generate method" adds using System

Let's say I have the following code while there is no method OnEvent is present.
Class.Event += OnEvent
Upon invoking the action "Generate method Class.OnEvent" I'm given
using System;
.
.
.
private void OnEvent() {
    throw new NotImplementedException();
}

What I expect is
private void OnEvent() {
    throw new System.NotImplementedException();
}

This action should not add using System

This would be a feature request for Roslyn. If this is still a problems, please open a new issue at https://github.com/dotnet/roslyn/issues


possibility to changee email backend

Djoser settings should include an option to modify the email backend used for sending emails.
For the moment, it uses an in-house solution: utils.UserEmailFactoryBase
but the ideal situation would be to be able to override this.

I'm open to correction, but as far as I'm aware that's not the email backend. It's just a factory for creating the actual emails themselves. They'll still be sent with whatever email backend you've specified in the Django settings.

You're right, it is in fact, just a factory.
In that case, why ont just use the django default email templates?
I mean, django already has activation, password_reset, etc,  email templates.
Is this not possible?

I haven't come across anything like this in the Django codebase but maybe you're right.

I'm not sure I follow, is it not possible to use these?
https://github.com/django/django/tree/master/django/contrib/admin/templates/registration

Oh those are the templates, not the email objects. The factory just controls which templates to use and what variables to make available to them.

Hello! Actually Djoser does not influence your chosen email backend. We're using a factory to simplify storing email templates in separate template files to improve code readability and to decouple the view layer from controller layer (as in MVC). Also it's totally fine to override the mentioned utils.UserEmailFactoryBase with e.g.:
class UserProfileEmailFactory(UserEmailFactoryBase):
    subject_template_name = 'user_profile_subject.txt'
    html_body_template_name = 'user_profile_body.txt'

Also if you'd like to actually change the email backend as in issue title you can for example use
https://github.com/anymail/django-anymail to accomplish that.
I'm going to close the issue as the problem seems to be solved, however feel free to reply if you need to discuss this further.


Don't panic on memory commit failure.

https://github.com/tetratelabs/wazero/pull/2315

For clarity, the idea here is that since https://github.com/tetratelabs/wazero/pull/2315 if the allocator returns nil, the Wasm module is informed that growing memory failed.
Then for a C module, sbrk fails, malloc returns NULL, and if we compile with SQLITE_DEFAULT_MEMSTATUS then sqlite3_malloc tries to free some memory (caches, etc) before trying a second time.


exceptions.AttributeError: 'FerryServerProtocol' object has no attribute 'autoPingPendingCall'

hi
while running portia 15.09 version using docker in centos i received error as
      File "/usr/local/lib/python2.7/dist-packages/autobahn/websocket/protocol.py", line 1209, in _connectionLost
        if self.autoPingPendingCall:
    exceptions.AttributeError: 'FerryServerProtocol' object has no attribute 'autoPingPendingCall'

can you please help me to resolve this

Can you try rebuilding your docker image. It seems like you have a version mismatch

hi
i configured the new version of portia using docker, running fine but some time it closed automate and shows error as
File "/app/slyd/slyd/splash/ferry.py", line 165, in sendMessage
self.protocol.sendMessage(metadata(self.protocol))
File "/app/slyd/slyd/splash/commands.py", line 83, in metadata
socket.tab.loaded = True
AttributeError: 'NoneType' object has no attribute 'loaded'
Aborted (core dumped)


fixed compiler warning: dead initialization (the values are never read)

In order to not get compiler warnings about 'unused return values'
a void cast is used, which also makes it clear the the returned values
are ignored on purpose

Which compilers have you tested this with?
Admittedly I don't know a lot about all the compilers out there, but a quick Google search tells me this will reintroduce the original warning I sort to avoid on GCC >= 4.6.

I use gcc (GCC) 5.3.0 and I do not see the original warning.
I also tested it with clang 3.7.1 and also did not see the warning.
This project will not compile with GCC == 4.6 because of the -std=gnu++11 option.

Alright, I'll take you word :smile:


format "media-range" is used in the schema without a specification

format: media-range appears in the JSON Schema for v3.1 (it appears to have been introduced in this version), but it is not mentioned in the spec anywhere, especially in https://spec.openapis.org/oas/v3.1.0#data-types. This should either be added to the spec as an extension to the "format" keyword, or the schema should change to using a "pattern" instead.

cc @jdesrosiers you added this in commit b5bf761d9b4e -- perhaps you have more information?

"media-range" is a custom format attribute as defined here, https://json-schema.org/draft/2020-12/json-schema-validation.html#rfc.section.7.2.3. It's not really intended to be validated but it optionally could be. It's based on the "media-range" ABNF production in RFC-7231, https://datatracker.ietf.org/doc/html/rfc7231#appendix-D.
We talked about it and decided we didn't want to include some ginormous nasty regex and we didn't want a simple regex that could give a false sense of security, so we came up with this as an alternative. A standard validator will ignore it, but if you have a validator that understands the custom format attribute, you can get assertion behavior.
Specifying the format attribute in OAS wouldn't help because the dialect of the schema is draft 2020-12. The format attribute would only apply to the OAS JSON Schema dialect. I agree that there should be something in the schema that gives a hint about what "media-range" means. Maybe a $comment or a description.

This format has since been added to the formats registry.


TFT

Using a TFT display have the option to select your bid?
Use the Meadow board from WildernessLabs?

https://github.com/CurtisIreland/electronics/blob/master/Ard-TFTButtons/TFT-RGB-LED/TFT-RGB-LED.ino

https://github.com/adafruit/TFTLCD-Library/blob/master/examples/tftpaint/tftpaint.ino

https://github.com/raysan5/raygui

https://learn.inventr.io/courses/adventure-kit-2-day-0/


0 start position for Doughnut

As it stands right now if I create a new Doughnut chart, my first value position begins at the center top of the graph and then loads up clockwise. Is there anywhere to change the degree starting position? Right now it begins at 0, but what if i wanted to start at 270 so i could have a value of 50% fill the top half of the chart rather than the right side of the chart

@drnen101 maybe you could change line 174 on Chart.Doughnut.js to include some starting property?
Not in a position where I can do this now but I'll swing back around this weekend and send you a sample that should work.

1) Add default property
		//Number - The angle to start the first segment stroke
		rotation: 0,

2) Modified the if statement that calculates the startAngle, also had to move this up a few lines
				if (index === 0){
					segment.startAngle = (this.options.rotation-90) * Math.PI / 180;
				}

View Gist
View CodePen

A PR into the 2.0-dev branch would be great for this.  Also a max-circumference was mentioned in another issue as well, essentially creating a gauge chart.

Thanks for looking into it for me Mark - i tried your implementation but other parts are breaking now. They are actually breaking in your codepen as well unfortunately- notice that most of the hover interactions on the chart are now broken. I'm looking at it in firefox right now and only Grey and Dark grey sections have functioning hover states. Let me know if you have any idea why-- thanks again!

Thanks for pointing that out!
I'll be working some more on Sunday on a site that I need this to work for, so I'll update you again tomorrow.

@markadrake I made couple of commits to the v2.0-dev branch to fix the angles. It seems to work. Maybe you can use some of that to your advantage.

I tried to update this over the weekend but got lost in the InRange function. If I apply any initial rotation (other than the Math.PI * -0.5 default) then the mouse positions (for 1PI - 1.5PI) seems to be ignored when the slice crosses the quadrant.
The changes aren't really significant:
Chart.Core.js
Added the following definition to the defaults, inserted as line 105:
            rotation: Math.PI * -0.5,

Chart.Doughnut.js
Updated spots where startAngle was defined, lines 96 and 161:
slice._model.startAngle = this.options.rotation;

Doughnut.html
Just added rotation to the options:
        options: {
            responsive: true,
            rotation: Math.PI * -0.75
        }

Done in v2

Another approach to set the startAngle for the doughnut chart is to create multiple canvas and create dougnut chart over each by adding the css "transform: rotate" to each as per the desired startAngle. Just make sure all the canvas are positioned properly to make the doughnut to appear as a single chart. Hope this solves the issue.


Finished taskbar!!!

(Let me just... clear out these conflicts ;))

Well, I will have to reopen it took look at a list of confilicts


[issue]  C++ runtime support multimodal model llava-one-vision

How to support the new model in cpp runtime ? Is there any reference document ? For example, the multimodal model llava-one-vision
Following TRTLLM doc, some issue as following:
Hardware: A100
1.
MODEL_PATH=/data/MLLM/llava-interleave-qwen-7b-hf
MODEL_NAME=$(basename $MODEL_PATH)
python3 tensorrt_llm/examples/llama/convert_checkpoint.py \
    --model_dir $MODEL_PATH \
    --output_dir output/${MODEL_NAME}/fp16/1-gpu \
    --dtype float16

    llama = LLaMAForCausalLM.from_hugging_face(
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/llama/model.py", line 354, in from_hugging_face
    loader = ModelWeightsLoader(hf_model_dir, custom_dict)
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/model_weights_loader.py", line 65, in __init__
    self.preload()
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/model_weights_loader.py", line 154, in preload
    self.shards = [
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/models/model_weights_loader.py", line 155, in <listcomp>
    safe_open(f, framework="pt", device="cpu") for f in shard_files
safetensors_rust.SafetensorError: Error while deserializing header: HeaderTooLarge

python tensorrt_llm/examples/multimodal/build_visual_engine.py --model_path ${MODEL_PATH} --model_type llava
[TensorRT-LLM] TensorRT-LLM version: 0.14.0.dev2024091700
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Loading checkpoint shards:   0%|                                                                                | 0/4 [00:00<?, ?it/s]
Traceback (most recent call last):
  File "/data/MLLM/tensorrtllm_backend/tensorrt_llm/examples/multimodal/build_visual_engine.py", line 12, in <module>
    builder.build()
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/tools/multimodal_builder.py", line 82, in build
    build_llava_engine(args)
  File "/usr/local/lib/python3.10/dist-packages/tensorrt_llm/tools/multimodal_builder.py", line 328, in build_llava_engine
    model = LlavaForConditionalGeneration.from_pretrained(
  File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 3838, in from_pretrained
    ) = cls._load_pretrained_model(
  File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 4278, in _load_pretrained_model
    state_dict = load_state_dict(shard_file, is_quantized=is_quantized)
  File "/usr/local/lib/python3.10/dist-packages/transformers/modeling_utils.py", line 516, in load_state_dict
    with safe_open(checkpoint_file, framework="pt") as f:
safetensors_rust.SafetensorError: Error while deserializing header: HeaderTooLarge

How to support the new model in cpp runtime ? Is there any reference document ? For example, the multimodal model.

Multimodal cpp runtime is still WIP and it is supported in python runtime only.
For the llava issues, I cannot reproduce these errors. It works fine for the latest TensorRT-LLM. Please refer to the installation doc to install TensorRT-LLM first. My reproduce step:
cd examples/multimodal/
git clone https://huggingface.co/llava-hf/llava-interleave-qwen-7b-hf
python3 ../llama/convert_checkpoint.py \
    --model_dir ./llava-interleave-qwen-7b-hf \
    --output_dir tmp/trt_models/llava-interleave-qwen-7b-hf/fp16/1-gpu \
    --dtype float16
python3 build_visual_engine.py --model_path ./llava-interleave-qwen-7b-hf --model_type llava

BTW, now TensorRT-LLM cannot support Qwen variant of LLaVA. @symphonylyh please correct me if I am wrong.

Still WIP. As for the timeline, @symphonylyh could you help answer this question?


Review and add new linters to improve the code quality of telemetry manager.

Configuration for Go code linting
Changes proposed in this pull request:

Configuration for existing linters
Added 12 new linters
Refactoring for the codebase to eliminate linting errors
Makefile target for automatic code fixing

Related issue(s)
https://github.com/kyma-project/telemetry-manager/issues/86

 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.Oleksandr Meteiko seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Replaced by https://github.com/kyma-project/telemetry-manager/pull/112


Old docs

Where can I find the old documentation for the 3.X branch?
Thanks!

Keep in mind that old versions are not supported http://eonasdan.github.io/bootstrap-datetimepicker/version3/


Update SCSS syntax extension

Rebuilds the SCSS syntax from the source repo (https://github.com/atom/language-sass).
The latest version of the syntax includes a separate file for SassDoc comment blocks, so
I've modified the scripts and grammars in package.json to account for that.
Closes #49071

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

@stormwarning Awesome, thanks a lot for the PR!


OSD-22395: Passing the KMS key defined for the cluster (if any) to osd-network-verifier

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.59%. Comparing base (79cec55) to head (4771f5c).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #266      +/-   ##
==========================================
+ Coverage   38.29%   39.59%   +1.29%
==========================================
  Files          16       16
  Lines        1465     1470       +5
==========================================
+ Hits          561      582      +21
+ Misses        866      849      -17
- Partials       38       39       +1

Files
Coverage Δ

pkg/networkverifier/networkverifier.go
48.23% <100.00%> (+23.23%)
:arrow_up:


Is NextJS in router or app mode?

Hi,
Is NextJS in router or app mode?

It uses App Router. does that answer your question?


Removes line that was causing message passing to fail

Just like it says on the tin.
https://bugzilla.redhat.com/show_bug.cgi?id=1393501

@mkanoor Please review

@tinaafitz @mkanoor Please review

@d-m-u Looks good.

https://github.com/ManageIQ/manageiq-ui-classic/pull/742


UnitOfWork - java.lang.IllegalStateException: Existing session transaction state (false) does not match requested (true)

After upgrading the dropwizard to 2.0.25, I am started getting this exception in the methods having @unitOfwork annotations ,
Can you help me out to rectify these errors ? why I am getting these errors now ?
Caused by: java.lang.IllegalStateException: Existing session transaction state (false) does not match requested (true) at io.dropwizard.hibernate.UnitOfWorkAspect.validateSession(UnitOfWorkAspect.java:178) at io.dropwizard.hibernate.UnitOfWorkAspect.beforeStart(UnitOfWorkAspect.java:85)

@rbobbaa This exception can only occur, when the SessionFactory for the HibernateBundle referenced by the @UnitOfWork.value() has already been bound to Hibernate's ManagedSessionContext and when the getCurrentSession() method of this SessionFactory returns an existing Session whose Transaction is not active. This means an other Session is managed by Hibernate and the transaction hasn't started yet or is already committed or aborted.
If you don't manually bind to Hibernate's ManagedSessionContext, I think there's a race condition in your application. Do you manually register a UnitOfWorkApplicationListener or do you use the UnitOfWorkAwareProxyFactory?

I only add the anotation of unitOfWork on methods, One thing I noticed is there are multiple UnitOfWork anotations present in my code like calling method is also having unitofWork annotation , is this the issue ?

for some of them I am not having this nested condition and still getting errors.

Could you provide a test for this? I think this is really hard to debug and would appreciate an example to reproduce this.

@rbobbaa Any update on this?

Closing this due to inactivity of the author.


Store more metadata about registered types

This might be useful when we're using reflection more extensively, particularly with scenes.

Closing in favor of #4042.


Support LayoutSpec Buildable

Inspired by SwiftUI body property

Can access updated constraintedSize property
Don't needs override layoutSpecThatFits: method

Example

import AsyncDisplayKit
import TextureSwiftSupport

class CardNode: ASDisplayNode, LayoutSpecBuildable {

  // MARK: - UI Components

  let thumnailImageNode: ASNetworkImageNode = ...
  let titleNode: ASTextNode = ...
  let contentNode: ASTextNode = ...
  let userNode: UserProfileNode = ...
  let curationBadgeNode: CurationBadgeNode = ...

  override init() {
    super.init()
    self.automaticallyManagesLayoutSpecBuilder()
  }

  // MARK: - LayoutSpec

  var layoutSpec: ASLayoutSpec {
    LayoutSpec {
      VStackLayout {
        mediaAreaLayoutSpec
        VSpacerLayout(minLength: 2.0)
        titleNode.flexShrink(1.0)
        VSpacerLayout(minLength: 4.0)
        contentNode.flexShrink(1.0)
        VSpacerLayout(minLength: 4.0)
        userNode
      }
    }
  }

  var mediaAreaLayoutSpec: ASLayoutSpec {
    LayoutSpec {
      AspectRatioLayout(ratio: 1.0) {
        thumnailImageNode
      }.overlay(
        RelativeLayout(
          horizontalPosition: .end,
          verticalPosition: .start
        ) {
          curationBadgeNode
        }
      )
    }
  }
}

@GeekTree0101
Thank you!
It looks pretty good. And I have a question, can we discuss it?
I think It would be better to create it as a class instead of LayoutSpecBuildable.
Because we can remove several methods and properties for subclasses if it's class.
with @available(*, unavailable).
I cared about the developer can declare layoutSpecThatFits and layoutSpec.
and I'm not sure there are no issues constraint-size becoming to stored-property.
If we change to class, we need to create around 3 types of base-classes.

For DisplayNode
For CellNode
For ControlNode

What do you think?
Thanks!

Thnk review comment!
IMO, Making 3 types of base-classes is looks like a reinvented-wheels, but it's more explicit than LayoutSpecBuildable. I just worry about maintenance about base-classes
Antd, stored-property (constraintedSize) is always updated after setNeedsLayout :]
Thnk

I think it's not so big deal with creating several base classes.
With this, the developer would become writing more safely and clearly.
And, I'm understanding you want to create a more simple base class which to be closed with SwiftUI.View than ASDisplayNode.
Actually that is already done with ASDisplayNode. I think there are not so many differences.
But I think it might be better to add it to the library with the way I showed.
I have no good idea of name for those classes.

Oh, I missed the advantages of using protocol.
With using protocol, we can enforce the developer to implement the method that needed.
It's aslo really advantages.

I think so too. both have advantages and disadvantages.
Also I believe that if more texture community people are interested in this repository, it will go to more better practical direction.


UIImage+Webp Decoding will crash with Memory leak

New Issue Checklist

[ ] I have read and understood the CONTRIBUTING guide
[ ] I have read the Documentation
[ ] I have searched for a similar issue in the project and found none

Issue Info

Info
Value

Platform Name
e.g. ios / tvos

Platform Version
e.g. 8.0

SDWebImage Version
e.g. 3.7.6

Integration Method
e.g. carthage / cocoapods / manually

Xcode Version
e.g. Xcode 7.3

Repro rate
e.g. all the time (100%) / sometimes x% / only once

Repro with our demo prj
e.g. does it happen with our demo project?

Demo project link
e.g. link to a demo project that highlights the issue

Issue Description and Steps
Please fill in the detailed description of the issue (full output of any stack trace, compiler error, ...) and the steps to reproduce the issue.
When decode much webp images at the same time will crash.
This is my solution(add an autoreleasepool):
do {         @autoreleasepool {            UIImage *image;            if (iter.blend_method == WEBP_MUX_BLEND) {                 image = [self sd_blendWebpImageWithOriginImage:[images lastObject] iterator:iter];             } else {                 image = [self sd_rawWepImageWithData:iter.fragment];             }             if (!image) {                 continue;             }             [images addObject:image];             duration += iter.duration / 1000.0f;         }     } while (WebPDemuxNextFrame(&iter));

Fix in #1985

OK, I will try.

4.1.1 is now released.


Improve patient information capture

Describe the bug
Add capability to find and convert the following patient information

NOTE:  the following were moved to #111

Patient.communication.language, Patient.communication.preferred / PID-15

NOTE:  the following were moved to #110

Patient.telecom / PID-13 (home), PID-14 (work)

NOTE:  the following were moved to #108

Patient.name.use / PID-5.7
Patient.name.given / PID-5.3 (middle name)

NOTE: the following were moved to #103

Patient.maritalStatus / PID-16

NOTE: the following were moved to #100

Patient.address / PID-11
Patient.address.district / PID-12. (Also known as Country code)

NOTE: the following were moved to #97

Patient.multipleBirthBoolean / PID-24
Patient.multipleBirthInteger / PID-25
Patient.deceasedDateTime / PID-29
Patient.deceasedBoolean / PID-30

To Reproduce
Create a sample HL7V2.6 patient PID segment with aforementioned patient information.
Expected behavior
Patient information should be detected and added to corresponding fields in HL7 FHIR resources.
Examples:
Patient Address:  This should handle a complete Extended Address XAD content  (should allow for multiple)
{
  "resourceType": "Patient",
  "id": "address",
  "address": [
    {
      "use": "home",
      "type": "both",
      "text": "534 Erewhon St PeasantVille, Rainbow, Vic  3999",
      "line": [
        "534 Erewhon St"
      ],
      "city": "PleasantVille",
      "district": "Rainbow",    <<< comes from PID.12
      "state": "Vic",
      "postalCode": "3999",
      "period": {
        "start": "1974-12-25"
      }
    }
  ],

District / Country code
From HL7V2.6, it is four characters of local definition.
Inserted into .address as shown above
Telcom (both home and work):  follow the Extended Telephone Communication XTN format  (should allow for multiple)
  "telecom": [
    {
      "system": "home",
      "value": "(03) 5555 6473",
      "use": "work",
      "rank": 1
    },
    {
      "system": "phone",
      "value": "(03) 5555 6473",
      "use": "work",
      "rank":2
    }
    }
  ],

Communication language:  recommended based on ISO table 639. However ISO 639 has additional versions.  This is a CWE encoding.
  "communication": [
    {
      "language": {
        "coding": [
          {
            "system": "urn:ietf:bcp:47",  << May not be this system.
            "code": "nl",
            "display": "Dutch"
          }
        ],
        "text": "Nederlands"
      },
      "preferred": true
    }
  ],

Screenshots
N/A
Desktop (please complete the following information):

OS:  Mac OS
Version Big Sur

Additional context
Add any other context about the problem here.

Each of the original enhancements in this issue have been moved to separate issues.   (See notes above).   Closing this issue because no work is left in it.  Future improvements will be in smaller more granular issues.


Questing

Written within the ai system -- meaning core RM does not have quest points. Central engine will have 'quests' concerning items, potions, and skills. In effect the first 'quest' comes with the mud school.


Add docs about v3 auth API and usage

[x] Import a digested version of the design doc: https://goo.gl/fwBxz6
[x] Release note and usage guide of CN based auth (after finishing the PR): https://github.com/coreos/etcd/pull/6881
[x] Release note and description about token types (after finishing the PR of jwt token): https://github.com/coreos/etcd/pull/6082

@mitake Thanks! We finish all of them. So closing.


🐛 Bug Report: 401s when making requests to GitHub with Multiple GitHub Integrations

📜 Description
I have two GitHub integrations setup to query two different Organizations that our company runs.
integrations:
  github:
    - host: github.com
      apps:
        - $include: github-app-ORG-ONE-credentials.yaml
        - $include: github-app-ORG-TWO-credentials.yaml

When Backstage makes calls to the repos that are in the ORG-ONE Organization, calls succeed as expected. However, when it attempts to make calls to any repos that are contained in the ORG-TWO Organization, calls fail with a 401/Unauthorized. If remove the first organization credentials from the list above, calls succeed.
I was able to track down the potential issue (I believe there was a similar issue noted as an issue on here, but cannot find it at the moment) to an issue in @backstage/integration where it it will look at the two credentials that are setup, and the first one that is not null is what will be used, regardless if an accessToken is null within it. This may not be the real fix to be honest, but does alleviate the symptom and fixes my issue.
Here is the whole of the fix that I created as a local patch:
az0916 $ cat<EMAIL_ADDRESS>diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index a85e29a..9227328 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -1354,7 +1354,7 @@ class GithubAppCredentialsMux {
         )
       )
     );
-    const result = results.find((resultItem) => resultItem.credentials);
+    const result = results.find((resultItem) => resultItem.credentials.accessToken);
     if (result) {
       return result.credentials.accessToken;
     }

Here, resultItem.credentials does not check if the credential actually has a valid accessToken within it, and upon checking to see if accessToken is truthy it'll allow calls to each organization to complete as expected (get a 200 response and get the needed repository data into Backstage). The check above should probably check to make sure resultItem.credentials is truthy and then check to see if accessToken is there to ensure we don't run into any sort of nil/undefined issues.
👍 Expected behavior
Backstage should be able to use the appropriate token between the two configured integrations for the organization when making calls to the GitHub API.
👎 Actual Behavior with Screenshots
When running with both integrations, I see these errors in the logs for ORG-TWO.

👟 Reproduction steps

Setup two separate GitHub organizations as integrations.
Setup at least a single catalog provider that will try to read from each Organization that is configured in step one. The repos that will be scanned by these integrations should either be 'internal' or 'private'.
See that the first Organization's repos are pulled in.
See the second Organizations's repos are not pulled in and the error above is observed in the logs.

📃 Provide the context for the Bug.
We are unable to pull the repositories and catalogs within them for ORG-TWO.
🖥 Your Environment
OS:   Darwin 21.6.0 - darwin/x64
node: v16.17.0
yarn: 1.22.19
cli:  0.22.1 (installed)
backstage:  1.10.1
Dependencies:
@backstage/app-defaults                          1.1.0
@backstage/backend-app-api                       0.3.1
@backstage/backend-common                        0.18.1
@backstage/backend-plugin-api                    0.3.1
@backstage/backend-tasks                         0.4.2
@backstage/catalog-client                        1.3.0
@backstage/catalog-model                         1.1.5
@backstage/cli-common                            0.1.11
@backstage/cli                                   0.22.1
@backstage/config-loader                         1.1.8
@backstage/config                                1.0.6
@backstage/core-app-api                          1.4.0
@backstage/core-components                       0.12.3
@backstage/core-plugin-api                       1.3.0
@backstage/errors                                1.1.4
@backstage/integration-aws-node                  0.1.1
@backstage/integration-react                     1.1.9
@backstage/integration                           1.4.2
@backstage/plugin-api-docs                       0.8.14
@backstage/plugin-app-backend                    0.3.41
@backstage/plugin-auth-backend                   0.17.4
@backstage/plugin-auth-node                      0.2.10
@backstage/plugin-catalog-backend-module-github  0.2.4
@backstage/plugin-catalog-backend                1.7.1
@backstage/plugin-catalog-common                 1.0.10
@backstage/plugin-catalog-graph                  0.2.26
@backstage/plugin-catalog-import                 0.9.4
@backstage/plugin-catalog-node                   1.3.2
@backstage/plugin-catalog-react                  1.2.4
@backstage/plugin-catalog                        1.7.2
@backstage/plugin-events-node                    0.2.2
@backstage/plugin-github-actions                 0.5.14
@backstage/plugin-org                            0.6.4
@backstage/plugin-permission-backend             0.5.16
@backstage/plugin-permission-common              0.7.3
@backstage/plugin-permission-node                0.7.4
@backstage/plugin-permission-react               0.4.9
@backstage/plugin-proxy-backend                  0.2.35
@backstage/plugin-scaffolder-backend             1.10.1
@backstage/plugin-scaffolder-common              1.2.4
@backstage/plugin-scaffolder-react               1.0.1
@backstage/plugin-scaffolder                     1.10.1
@backstage/plugin-search-backend-module-pg       0.5.2
@backstage/plugin-search-backend-node            1.1.2
@backstage/plugin-search-backend                 1.2.2
@backstage/plugin-search-common                  1.2.1
@backstage/plugin-search-react                   1.4.0
@backstage/plugin-search                         1.0.7
@backstage/plugin-tech-radar                     0.6.0
@backstage/plugin-techdocs-backend               1.5.2
@backstage/plugin-techdocs-module-addons-contrib 1.0.9
@backstage/plugin-techdocs-node                  1.4.5
@backstage/plugin-techdocs-react                 1.1.2
@backstage/plugin-techdocs                       1.4.3
@backstage/plugin-user-settings                  0.6.2
@backstage/release-manifests                     0.0.8
@backstage/test-utils                            1.2.4
@backstage/theme                                 0.2.16
@backstage/types                                 1.0.2
@backstage/version-bridge                        1.0.3
✨  Done in 2.60s.
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

Are you using the allowedInstallationOwners configuration? I think the logic might be a bit off there currently, where specifying that option with multiple providers will break the lookup. I think there's a risk you proposed fix will break the fallback to access public repos, but as long as we make sure the support that I think something like your fix is the way to go 👍

@Rugvip - we are indeed using allowedInstallationOwners.
I'll have to dig a bit, but I'm curious about the risk to breaking public repo access. I'm pretty naive to the other inner workings around this particular function, but it seems like since we are returning result.credentials.accessToken a few lines down from the check, that we'd want said accessToken to not be null/undefined.
I'll see what I can do about grabbing the latest from this repo, making the small tweak (including the check on .credentials first, and cross my fingers no tests break (and try to add one as well 😄).

Following up on this - looks like this may have been fixed in this commit: https://github.com/backstage/backstage/commit/5d12393bc9a04c57e277cc7c05892a7ec0601057


Docker for Windows mssql-server-linux:latest fails to run due to memory limit

I may be doing this wrong...
Docker: 18.04.0-ce-win62 (17151)
image: microsoft/mssql-server-linux:latest
I'm just trying to run the following:
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=supersecret" -p 1417:1433 --name sql17 --platform linux -d microsoft/mssql-server-linux:latest

I can see the container in VS Code created and started, but then immediately stops. I check the logs:
docker logs sql17 --tail 50 -f
sqlservr: This program requires a machine with at least 2000 megabytes of memory.

So I saw mention in another issue about -e "MSSQL_MEMORY_LIMIT_MB=3072"  so I tried that but still gets the same error.
Am I doing something wrong?

if you are literally using supersecret as your password it isnt meeting complexity requirements.  You can run it without -d to see the output and see if there is anything useful there.

I'm pulling down the Ubunut:latest image to just see if I can get it to run. It may be just an issue with trying to run Linux over Windows mode...

Ah ha!  You are hitting this issue where Linux Containers on Windows (LCOW) is limited to max 2GB of memory.
https://github.com/Microsoft/opengcs/issues/145

I've read that there are options to reduce the memory usage of SQL Server.  Is there a way to set those via the docker env file?

You can control the amount of memory that SQL Server uses by passing the MSSQL_MEMORY_LIMIT_MB environment variable.  SQL Server on Linux does need a minimum of 2GB of memory though for now.

Looks like the option to configure the VM memory is back in the more recent versions of Docker for Windows.  Can you please try changing this from the default 2 GB to 4 GB or something and try running SQL Server on Linux again?  Should work now.

I'm running into the same extremely annoying issue.

Tried to run without success this container on Windows 10 in experimental mode (where you can run Linux and windows containers side by side). In this mode you lose ability to control how mush resources you can assign to Linux container. Even if previously in Linux mode you set  higher memory limit it does not matter. Also if you try manually to assign more memory to MobyLinuxVM in Hyper-V manager, it does not help.
If you have an idea, please share. I would like to run SQL in Linux container side by side with Windows-Core running Powershell (to configure SQL).

Hello,
I am facing the same issue using the latest docker version( 18.09.0-ce-beta1), i can;t start sqlsrv linux contaner:  "sqlservr: This program requires a machine with at least 2000 megabytes of memory."
I don't what to to fix it!.Can you help me out with this one,please?
Thank you!

The 2GB minimum does not seem sensible to me.
Does really empty sqlsrv needs that much memory just to start? I understand there may be some (potentially big) performance degradation for bigger tables and bigger indices, but it does not seem sensible to beef up the machine just to create a table with 20 rows for Travis build. Production (!) and fast enough MySQL/MariaDB for small web can run on 512M DigitalOcean droplet along with httpd and standard Debian.

@tomasfejfar There's a bit more to it than just simply running SQL Server.  Keep in mind that SQL Server on Linux runs inside of a platform abstraction layer (PAL).  More detailed reading.  The additional memory required to run the PAL itself is a big part of the overall memory demands of running SQL Server in as small of a footprint as possible.  On a production system with 1 TB of RAM available the extra 512MB-1 GB to run the PAL is negligible, but when you are trying to run some CI tests on as small of a footprint as possible, it's completely understandable to want to minimize the memory consumption.  We're working on reducing the memory footprint, but it will take some time.  Hope that provides a bit more context.

That's much more context, thanks. And the link provided me with much deeper understanding. My understanding was pretty much limited to "it's probably just C, so not much different from other RDBMS".

Any Status update on this?

Bumping this to see if anyone has looked into it or if there is a roadmap to support this eventually again.

We don't have anything to share at the moment. We are actively investigating how we can support this in production. Once we have support for the same, we will make a formal announcement and also update this thread.

I have the following environment withing my windows 10:
**Client:
Version:       18.03.0-ce
API version:   1.37
Go version:    go1.9.4
Git commit:    0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch:       windows/amd64
Experimental:  false
Orchestrator:  swarm
Server: Docker Engine - Community
Engine:
Version:      18.09.1
API version:  1.39 (minimum version 1.12)
Go version:   go1.10.6
Git commit:   4c52b90
Built:        Wed Jan  9 19:41:57 2019
OS/Arch:      linux/amd64
Experimental: false**
Before running the following command:
docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=password' -e 'MSSQL_MEMORY_LIMIT_MB = 4000m' -p 1401:1433 microsoft/mssql-server-linux
I have set the limit on virtualbox for base memory to 2048 mb and it works properly

Not using vbox, using hyper-v default docker machine and will not be able
to setup or push for vbox every where
On Mon, Feb 11, 2019 at 2:02 PM Fatlonder<EMAIL_ADDRESS>wrote:

I have the following environment withing my windows 10:
**Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24302
Built: Fri Mar 23 08:31:36 2018
OS/Arch: windows/amd64
Experimental: false
Orchestrator: swarm
Server: Docker Engine - Community
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.12)
Go version: go1.10.6
Git commit: 4c52b90
Built: Wed Jan 9 19:41:57 2019
OS/Arch: linux/amd64
Experimental: false**
Before running the following command:
docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=password' -e
'MSSQL_MEMORY_LIMIT_MB = 4000m' -p 1401:1433 microsoft/mssql-server-linux
I have set the limit on virtualbox for base memory to 2048 mb and it works
properly
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/mssql-docker/issues/293#issuecomment-462451734,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACgvXOQntV2dSj_ocMPh-XcXVOTSVWk3ks5vMb5CgaJpZM4TeDRZ
.

Not using vbox, using hyper-v default docker machine and will not be able to setup or push for vbox every where
…
On Mon, Feb 11, 2019 at 2:02 PM Fatlonder @.***> wrote: I have the following environment withing my windows 10: Client: Version: 18.03.0-ce API version: 1.37 Go version: go1.9.4 Git commit: 0520e24302 Built: Fri Mar 23 08:31:36 2018 OS/Arch: windows/amd64 Experimental: false Orchestrator: swarm Server: Docker Engine - Community Engine: Version: 18.09.1 API version: 1.39 (minimum version 1.12) Go version: go1.10.6 Git commit: 4c52b90 Built: Wed Jan 9 19:41:57 2019 OS/Arch: linux/amd64 Experimental: false Before running the following command: docker run -e 'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=password' -e 'MSSQL_MEMORY_LIMIT_MB = 4000m' -p 1401:1433 microsoft/mssql-server-linux I have set the limit on virtualbox for base memory to 2048 mb and it works properly — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#293 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/ACgvXOQntV2dSj_ocMPh-XcXVOTSVWk3ks5vMb5CgaJpZM4TeDRZ .

Can't you change the memory limit on hyper-v as well? I guess there should be an option

You have to change them using docker flags with Linux containers but when
you are using mixed mode containers
I.e. windows containers along side Linux containers
Docker throws an error saying that memory resource allocation is not
supported
On Fri, Feb 15, 2019 at 4:27 PM Fatlonder<EMAIL_ADDRESS>wrote:

Not using vbox, using hyper-v default docker machine and will not be able
to setup or push for vbox every where
… <#m_-636101805999469629_>
On Mon, Feb 11, 2019 at 2:02 PM Fatlonder @.***> wrote: I have the
following environment withing my windows 10: Client: Version: 18.03.0-ce
API version: 1.37 Go version: go1.9.4 Git commit: 0520e24302 Built: Fri Mar
23 08:31:36 2018 OS/Arch: windows/amd64 Experimental: false Orchestrator:
swarm Server: Docker Engine - Community Engine: Version: 18.09.1 API
version: 1.39 (minimum version 1.12) Go version: go1.10.6 Git commit:
4c52b90 Built: Wed Jan 9 19:41:57 2019 OS/Arch: linux/amd64 Experimental:
false Before running the following command: docker run -e
'ACCEPT_EULA=Y' -e 'MSSQL_SA_PASSWORD=password' -e 'MSSQL_MEMORY_LIMIT_MB =
4000m' -p 1401:1433 microsoft/mssql-server-linux I have set the limit on
virtualbox for base memory to 2048 mb and it works properly — You are
receiving this because you commented. Reply to this email directly, view it
on GitHub <#293 (comment)
https://github.com/Microsoft/mssql-docker/issues/293#issuecomment-462451734>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACgvXOQntV2dSj_ocMPh-XcXVOTSVWk3ks5vMb5CgaJpZM4TeDRZ
.
Can't you change the memory limit on hyper-v as well? I guess there should
be an option
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/mssql-docker/issues/293#issuecomment-464206740,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACgvXHB9OKTivoryK7NMrFc3obfqIhKgks5vNyZTgaJpZM4TeDRZ
.

Hi,
Any updates on this issue with Windows mixed containers?

+1 on not working in mixed mode Windows containers, no (apparent) way of increasing the Docker VM memory

Got tired of waiting and refocused effort in getting kubernetes cluster in
azure working :/
On Fri, Mar 22, 2019 at 12:41 AM Simon<EMAIL_ADDRESS>wrote:

+1 on not working in mixed mode Windows containers, no (apparent) way of
increasing the Docker VM memory
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/mssql-docker/issues/293#issuecomment-475491989,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACgvXKsR8B8bhUR0JsXq5ZnxbbaaMDzJks5vZF7-gaJpZM4TeDRZ
.

@wsmelton
I made a docker image that works around this memory (limitation) policy:
https://github.com/justin2004/mssql_server_tiny

ı waste lots of time about this issue and ı couldnt find any solution. maybe @justin2004 ' image can solve this problem .. Does anyone try this ?

I had the same issue. Here is what I did to solve it:

In the Windows Docker app right click and switch to Linux container

Open Settings and select Advanced (make it 3g)

then just run in bash or powershell:
docker run --name demoSQLServer
-p 1431:1433
-e "ACCEPT_EULA=Y"
-e "SA_PASSWORD=1qaz.@WSX"
-d microsoft/mssql-server-linux:latest

@justin2004 I just came back to see if there was any status changes on this since my post last year and I see your branch as a viable Option. Again a lot of people do not realize that the issue is when they are trying to run mixed containers (linux containers running in windows mode with LCOW).
Anyways, Justin I am going to pull your branch and see if I can implement your solution as one viable way to get it running in a container in linux running in mixed mode for windows

FWIW, the --memory option now works in my environment:
docker run --memory=2G -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=P@ssword12345' -p 1433:1433 mcr.microsoft.com/mssql/server
My environment:
PS C:\> [System.Environment]::OSVersion
Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0

PS C:\> docker version                                                                                Client: Docker Engine - Enterprise
 Version:           19.03.0
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        7c57940
 Built:             Wed Jun 12 09:43:47 2019
 OS/Arch:           windows/amd64
 Experimental:      true

Server: Docker Engine - Enterprise
 Engine:
  Version:          19.03.0
  API version:      1.40 (minimum version 1.24)
  Go version:       go1.12.5
  Git commit:       7c57940
  Built:            Wed Jun 12 09:57:40 2019
  OS/Arch:          windows/amd64
  Experimental:     true
PS C:\>

@jsandquist where did you get 19.03.0? Is it Edge channel?

@ggirard07 Not Edge channel - but a recent Enterprise Edition download from https://hub.docker.com/editions/community/docker-desktop-ent
I have not yet looked at the Community Edition.

The current implementation does not allow mcr.microsoft.com/mssql/server to start on Azure machine that actually had 2 GiB RAM (sizes A1v1, B1ms, F1s, etc.) because the machine reports just 1949872k total memory.
The 2 GiB DigitalOcean VM reports 2041328k total memory, and the container starts with no issues.
It looks like by "2000 megabytes" Microsoft actually means 200,000,000 bytes, and if kernel happens to take more than 140 MB RAM (like it now does on Azure VMs) - SQL Server will not start.

@skand888
I've started sqlserver on a machine with just 512 MB of RAM using:
https://github.com/justin2004/mssql_server_tiny

@skand888
I've started sqlserver on a machine with just 512 MB of RAM using:
https://github.com/justin2004/mssql_server_tiny

Yes, I've seen your solution above, but I am somewhat worried for possible consequences because it will allow it to start on a machine with any amount of RAM and behaviour might be unpredictable. But if no other solution is found - we will probably use a modification of your solutions.
BTW, I noticed that you use 1024l * 1024l * 1024l * 2l, while 1000l * 1000l * 1000l * 2l should probably be enough.

@skand888

behaviour might be unpredictable.

we already know what would happen if physical RAM was low enough -- i'm sure you'd see lots of page faulting and kswapd would be busy, and things would take longer and maybe even timeout by wallclock time, same as any other application. but that is the price we pay with diminishing physical RAM.

BTW, I noticed that you use 1024l * 1024l * 1024l * 2l, while 1000l * 1000l * 1000l * 2l should probably be enough.

probably. if you test it i'll accept your pull request.

@justin2004
We decided to go with your elegant solution with a couple of small updates. I've created pull request.
Thank you for the solution!

Any Status update on this?

Is this yet more evidence that Microsoft care only about the development experience of Windows users? Sadly a predictable part of working within this sphere.

@LukeCarrier I don't think that's fair. MS is doing a lot for Linux development. I can imagine that porting database engine that used many low level Windows functions to work with the Linux kernel reliably is no small feat.

When you spend every minute of your work day wrestling elements of the
Microsoft ecosystem into playing nicely with the wider world your ability
to empathise with the teams shipping releases with major regressions day
after day wanes somewhat.
Everything very much Windows-first. If Microsoft don't care about the
experience for those of us outside of that niche, they should do one of two
things:

Open source the stack and let us fix these problems by ourselves; or
Just leave. We have alternatives, and simply not having the inferior
product on the table for middle management and executives to choose would
enable us to get on with building our platforms.

Just look at how little regard there is for customers of this platform in
this very GitHub repo. A similar disinterest and, at times, outright
hostility, meets customers trying to get feedback into product groups via
Azure too.
I'm sorry, but I don't buy that Microsoft is open enough to support these
platforms.
On Tue, 18 Feb 2020, 19:58 Tomáš Fejfar<EMAIL_ADDRESS>wrote:

@LukeCarrier https://github.com/LukeCarrier I don't think that's fair.
MS is doing a lot for Linux development. I can imagine that porting
database engine that used many low level Windows functions to work with the
Linux kernel reliably is no small feat.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/mssql-docker/issues/293?email_source=notifications&email_token=AAERYF5UEUTKQUS43JQU7BDRDQ4X5A5CNFSM4E3YGRM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMEF3VY#issuecomment-587750871,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAERYF472KWM5LJIEUHLSNLRDQ4X5ANCNFSM4E3YGRMQ
.

So, we let this issue just fade into the nether without any solution or is it just me? 🤔
I am experiencing the same problem with latest WSL2 and Docker in mixed mode (Windows Containers with experimental setting). I tried setting the memory into .wslconfig file, but I still get that error.
I guess it is a dead-end 🤷♂

@totollygeek
there is a workaround here:
https://github.com/justin2004/mssql_server_tiny
it works in linux distros.
maybe it will work in WSL?

@justin2004
Well, I manage to workaround it, using deprecated functionality as the deploy tags in docker-compose.yaml and give 3GB of memory to the container. It works then, but it is kinda ugly I guess.

I was with the same problem.
To fix it, execute:
docker-machine stop
docker-machine ls (get name)
docker-machine inspect <NAME>

take a look StorePath
Go to StorePath and open config.json
alter attribute "Memory"
save
docker-machine start
if necessary, reboot your system
then
execute the pull container again =)

Here is my solution.
I was getting this logs from container named sql1.
This container is running as user mssql.
To learn more visit https://go.microsoft.com/fwlink/?linkid=2099216.
sqlservr: This program requires a machine with at least 2000 megabytes of memory.
/opt/mssql/bin/sqlservr: This program requires a machine with at least 2000 megabytes of memory.

After searching a lil bit. I changed my virtual machine's ram from virtual box gui. It was 1024mb. I changed it to 4096mb.
Now it works

With WSL2 modify .wslconfig file in your user folder and reboot
[wsl2]
memory=4GB   # Limits VM memory in WSL 2 up to  4 GB
processors=2 # Makes the WSL 2 VM use two virtual processors

With WSL2 modify .wslconfig file in your user folder and reboot
[wsl2]
memory=4GB # Limits VM memory in WSL 2 up to 4 GB
processors=2 # Makes the WSL 2 VM use two virtual processors

@dotupNET
This does not solve the problem for me, and I'm not sure how this is supposed to help? as far as I understand it, it puts an upper limit on memory usage for WSL. We would need a way to specify minimum memory allocation to WSL to solve the issue.
the strange thing for me is:
if I run docker in linux container mode, the sql container runs just fine, but if I'm in windows mode and launch it with "--platform=linux" I run into the memory issue...

if you are literally using supersecret as your password it isnt meeting complexity requirements. You can run it without -d to see the output and see if there is anything useful there.

He gave you a problem why you are giving him hard time about his password that's outrages

@totollygeek
there is a workaround here: https://github.com/justin2004/mssql_server_tiny
it works in linux distros. maybe it will work in WSL?

outdated but do we have any other solution :)


Deleting actors causes crashing

Whenever you try to delete many actors eventually it crashes and using that level I can't delete any more actors without it crashing.
To Reproduce
Steps to reproduce the behavior:

Delete many actors in a row
Eventually it will just crash and not let u delete any more

Expected behavior
For it too not crash.
Operating System:
Win11 x64
Additional context
None.

fixed with 5659cd4


Problem with freeing-up memory of matrix

When performing a cholesky decomposition of a large matrix, freeing-up the memory of the resulting matrix leads to an "invalid pointer"-error (see below). When the example code is in a function, then the same error occurs at the end of the function also without the del-statement. The error only occurs for large covariance matrices. The size, where the error starts to occur, is depending on the type of computer node used. The error below occurs on piz daint at CSCS when using a covariance matrix larger than ca. 70000x70000. On other systems, the same code causes a Segmentation fault instead of this "invalid pointer"-error.
Reproducing code example:

import numpy as np
from scipy.sparse import csr_matrix
from scipy.linalg import cholesky

covariancematrix = csr_matrix( np.identity(70000) )
C = cholesky(covariancematrix.toarray(), lower=True)
del C

Error message:

*** Error in `python3': free(): invalid pointer: 0x00002ab7b049c010 ***

Scipy/Numpy/Python version information:

Python  3.8.5
numpy  1.21.1
scipy  1.7.1

It seems like a problem with too much memory being requested. This is probably leading to bad allocation, resulting in invalid pointer error or segmentation fault on python side. IMHO, adding a better error message in the underlying C-code (if any) should resolve the issue.

Let's close this under an assumption that the origin is the same as in gh-20229. Feel free to reopen if the problem surfaces again.


Instantiate Struct from object

I'm trying to instantiate a complex Struct in the JS side with lots of attributes. Is there an easy way instantiate it? maybe something like this?
#[wasm_bindgen]
pub struct BigUserStruct {
    username: String,
    email: String,
    // ...
}

And at the JS side do something like this:
const user = new BigUserStruct({username: "Sam1", email<EMAIL_ADDRESS>/* ... */ })

To support this you'd probably want to do something like:
#[wasm_bindgen]
impl BigUserStruct {
    #[wasm_bindgen(constructor)]
    pub fn new(obj: &js_sys::Object) -> BigUserStruct {
        // ...
    }
}

and then accessing the fields of obj can be done with Reflect::get perhaps?

@alexcrichton Although that works, I think he was just asking for a more convenient way to create the Rust struct on the JS side.
If wasm-bindgen auto-generated a fromObject method, he could do this in JS:
BigUserStruct.fromObject({username: "Sam1", email<EMAIL_ADDRESS>/* ... */ });

The fromObject method would take the object, access its properties in JS, and then somehow translate those values into a Rust struct:
class BigUserStruct {
    static fromObject(obj) {
        let username = obj.username;
        let email = obj.email;
        return new BigUserStruct(wasm_bindgen_magic_goes_here(username, email));
    }

    ...
}

Yes, exactly what @Pauan said

Ok thakns for the clarification @DanielRamosAcosta, if this is a feature request though I'd be more inclined to do this via a Rust macro rather than a builtin "magical method". You could also use serde here I believe!

I'm closing this, as it's 3 years old now.


Can mixin windows handle RadioButtonGroups?

The code below works fine using mixin.FCMCustomWindow() (and various finale.FCWindows) but fails with FCMCustomLuaWindow and FCXCustomLuaWindow. In both latter cases clicking any radio button gives the message:
ERROR: FCMCustomLuaWindow:134
Control with ID #10001 not found in ‘Handle Command’ (code=The lua function invocation raised an error)
(RGP 0.67 with TrustedMode disabled - latest mixin files from src)
local mixin = require("library.mixin")
--local dlg = mixin.FCMCustomLuaWindow()
local dlg = mixin.FCMCustomWindow()
local b_group = dlg:CreateRadioButtonGroup(0, 0, 4)
local bttn = {}

for i = 1, 4 do
    bttn[i] = b_group:GetItemAt(i - 1)
    local str = finale.FCString()
    str.LuaString = "I am button " .. i
    bttn[i]:SetText(str)
end
b_group:SetSelectedItem(2)
dlg:CreateOkButton()
dlg:ExecuteModal(nil)

CC @ThistleSifter

No I haven't added that yet, I'm a bit behind on some of those. Do you need it for a script?

Not yet - just experimenting. So no hurry from my side.


Dead link is not really dead

Your lib marks this link as dead https://vimeo.com/78912852 but it's not, as you can see by clicking it.

Can we re-open this issue?  Some vimeo links still are marked dead, when they are not.
- Linting
✖ Linting
  README.md:212:3
  ✖  212:3  Link to https://vimeo.com/20241649 is dead  remark-lint:no-dead-urls
  ✖  213:3  Link to https://vimeo.com/9790850 is dead   remark-lint:no-dead-urls
  2 errors

@dialex I don't see your link validation lib.  Can you post / package it?

See https://github.com/transitive-bullshit/check-links/issues/4. check-links is the lower-level link-checking library this plugin uses. I'm sure they'd appreciate a PR, if @dialex or anybody else has ways to fix some false positives.

My bad, it was in a branch. It's merged now, this is the file. I asked a friend, it took him a couple of hours, and it works (so far no false positives) 👍

I'm having the same issue here: https://travis-ci.org/fregante/Awesome-WebExtensions/jobs/563973345#L208
It says https://bfred.it is not working (both on Travis and my computer) but the URL loads fine

@fregante please post an issue on the underlying project, mentioned above.


Fixed the last 6 warnings, enabled "Treat warnings as errors"

Fixed incompatible code property of ISpdyError with the base class NSError: replaced the getter declaration by a property one, using NS_ENUM to make ISpdyErrorCode compatible with NSInteger (the type of NSError's code property), and updated a format string due to this change (common.m:185)
Fixed _closeSocket declaration and implementation differing in return type
Fixed an integer precision warning (ispdy.m:1047)
Fixed the null argument passed to non-null parameter warning in loop.m, added for this a dummy timer method and passing that to the timer
Fixed retain cycle warning by using weak reference to self in request.m
Updated the project file and the podspec to enable the "Treat warnings as errors" build setting

@indutny, @georgekola please take a look at this PR, I recommend we fix all warnings and enable the "treat warnings as error" build setting


cmake generate vs program have no souce code olny cmake rules ?

cmake generate vs program have no souce code olny cmake rules ?
how to generate vs program with souce code ?

This all looks good. You opened the top-level build, which uses rules to download and build all dependencies (VTK, ITK, DCMTK, ...). You first need to build this solution.
Then, after build is completed, if you want to see source code in the solution then open the corresponding solution file within ...-build subfolder.

you mean first build  all_build project   then  i can see the source code in  build dir ,  I want to debug it  with vs, how can i do?   thank you

To debug, open the corresponding solution file within ...-build subfolder.

thank you very much


GenericDatum: Using long to represent string length in BinaryDecoder.

Currently BinaryEncoder uses long (int64) and BinaryDecoder uses int (int32). Avro spec asks us to use long.

This is fixed by:
Pull: https://github.com/stealthly/go-avro/pull/37
Commit: https://github.com/arunmk/go-avro/commit/44744fb68a84ce7c308cde333c51ee2cc7bc6374


Add "Nebula" to the nasa page

at various logical locations... https://openlifesci.org/nasa/

It has begun! 🚀

Closed with PR #763. Thanks, Yo!


assign glyph-names

1. Why is this change necessary?
It makes it easier to change the font or creating another one (f.e. with icomoon) using shopware's glyph-names - without changing all the names in template.
2. What does this change do, exactly?
adding glyph-names to svg
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

see #1540


Setup stylelint and configured it to use wagtail-styleint-config

I have tried to set up stylelint and it seems to work now by using npm run lint:css. Addresses #170.

Sure

This should do the trick. Have a look

Something went wrong.
0s
Run npm run lint:css

><EMAIL_ADDRESS>lint:css
> stylelint **/*.scss

sh: 1: stylelint: not found
Error: Process completed with exit code 127.

Not sure but maybe it's running too early or something.
Also - are you able to rebase on master - it's saying there are merge conflicts

Yes. I have resolved merge conflicts in previous commits.

Yes. I have resolved merge conflicts in previous commits.

It's still saying cannot rebase due to conflicts for me.


Do users never leave?

So if we assign a CAL to a user, and it cannot be “revoked”, what happens when they leave the company?

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

ID: 3d69b9ea-9672-c267-03e4-a34bf105d31b
Version Independent ID: bddcfc0f-77d6-ff1c-9af3-c5b3ad11ba63
Content: License your RDS deployment with client access licenses (CALs)
Content Source: WindowsServerDocs/remote/remote-desktop-services/rds-client-access-license.md
Product: windows-server
Technology: remote-desktop-services
GitHub Login: @lizap
Microsoft Alias: elizapo

You've probably worked this out by now, but a user CAL is allocated to a user on login, and expires 1 month after allocation. Expired licenses are placed back into the CAL pool and allocated to the next user that needs one.

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


Shimmer effect grows wider when its height is big

I'm not sure what is wrong exactly but I have some weird behavior when I try to use the library with a complex and full-screen layout.
We are actually using the library for another screen where we only have small list item. That works fine.
Here is how it looks like. The shimmer is wider on the bottom.

@tasomaniac This is not an issue and the height has nothing to do with it. The problem (or I would not say it is a problem) is that your are using different background colors for the views in the animation. The color of the shimmer line has a zero alpha value at the left and right side and 1 alpha value at the middle. This means if you have a lighter color than the shimmer line, the line will look wider since the edges will be visible even when they only have 0.1 alpha. On the other hand, when you use darker colors the situation is quite the opposite. The edges of the shimmer line will be visible if they have higher alpha value  so only the part near to the vertical center of the line will be visible.
So by using the same background your issue will be fixed.
I suggest reading the article listed in the README section, it will help a lot! :)

We saw the article and wanted to switch from the other library.
In our case, it is actually not possible to change the colors. We may change the colors of call and email buttons but the image below the buttons even has a lot of transparency.
So you're saying that this is the limitation of the library and it is not possible to do shimmer on an arbitrary image? So it needs to have a single color for the library to work?

So basically yes, using one color is the easiest way but for different backgrounds it looks slightly different. What you can do is to play with the background alpha, so when you decrease the alpha of the top view, the line will be wider, but the line below the buttons will not change.
As for images, it can run on any image.


LCAM-1271-adding null check

What
Link to story
Describe what you did and why.
Checklist
Before you ask people to review this PR:

[ ] Tests should be passing: ./gradlew test
[ ] Github should not be reporting conflicts; you should have recently run git rebase main.
[ ] Avoid mixing whitespace changes with code changes in the same commit. These make diffs harder to read and conflicts more likely.
[ ] You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
[ ] You should have checked that the commit messages say why the change was made.

Unfortunately, this doesn't quite tackle the problem we're seeing.
Here is an example snippet of a request from MAAT:
"contribution": {
      "timestamp": null,
      "selected": false,
      "id": null,
      "monthlyContribs": null,
      "upfrontContribs": null,
      "effectiveDate": {
        "value": null
      },
      "calcDate": {
        "value": null
      },
      "capped": null,
      "upliftApplied": false,
      "basedOn": {
        "value": ""
      }
    }

The validation you've added accounts for blank strings, but not when null is passed as the value.