Implement checking of stop bits and channel counter

In my application I need to handle DMX input using sources that may send less than 512 channels. The issue is that I don't know how many channels are sent, a user can connect any source, so I need to dynamically support any number of channels (24-512) and accurately detect how many channels were sent.
I have been able to implement checking of the stop bits in PIO, which could be used to detect the end of a frame. But I'm struggling with how to communicate the number of received channels back to the C code. I've toyed with raising a IRQ at the end of the frame (which essentially is when the stop bits are missing = invalid). But I can't figure out how to capture that in the C code and use that as a channel counter, and somehow sync that with the DMA transfer.
I've also thought about using a 16-bit buffer for the DMX transfer, and set the high byte to indicate when the stop bits are wrong, so I could then count the number of channels in the C code. But not only would it be a waste of memory, it would also be a fairly breaking change to this library that I would like to avoid.
Would it be possible to have a counter in PIO and then push that at an invalid stop bit somehow? Is there another way? I'm fairly new to PIO so I may be missing something obvious.

Hmmmm interesting ideas!
I have not worked on this library in a little while so I have to admit that I'm a bit rusty on the whole PIO shctick. I can at least throw out some ideas!
What might be possible is to modify the PIO assembly so that it reads the number of channels received into a scratch register as the data is received by the PIO. Hopefully it is possible to read the scratch registers from software (?)
Another way might be, as you suggest, to trigger a IRQ when the PIO detects the end of a frame. After a IRQ, a call to dma_channel_abort could stop the DMA transfer of the data before the completion of the full 512 channels have been recieved. Perhaps it is possible to read the number of bytes transferred by the DMA instance somehow?
What are your thoughts?

Working on my forked version of this code (in pure Python), one major challenge I still have to resolve is how to handle "short" DMX frames containing less than 512 channels. The DMX standard (ANSI E1.11-2008 R2018) only allows you to identify the start of the next frame, not the end of the current one. The idle time (Mark Before Break) can be anything from zero up to one full second, and the receiver must be capable of handling "a signal with a refresh rate of 0.8Hz to approximately 836Hz". My current solution is to raise an IRQ as soon as the BREAK (or a malformed value) is detected, i.e. after a constant low for more than 9 bit periods, or 36us) - but this is remarkably close to the start of the next frame which could occur only 56us later, thus presenting a potential race condition.
The other issue I'm still struggling with is handling non-zero START codes, which is essential if working with RDM-enabled devices.

@jostlowe Yeah the issue I'm having is how to communicate the channel count over (and INCing a register isn't that straightforward in PIO, but it can be done). I could PUSH it into the fifo, but that means the DMA transfer will be short, so I don't think that will work. I could push 512 bytes, plus the counter, but that's also annoying. I've read that it's possible to read the number of transfers in DMA, so it may be possible to do that, but I'm a little rusty on how to catch that IRQ and I can't find an example that does something similar.
@MikeEllis-personal I was going to use the lack of start+stop bits as an indicator that it's the end of the frame. I realize there's an maximum gap between channel bytes, but I've yet to see a source that has more than negligible gap, so it's a trade-off I'm ok with doing. I have several sources that send less than 512 channels, so that's a more important issue to resolve. It sounds like you're doing the same thing. Do you still use PIO, but with the "program" in Python, or are you saying you "bitbang" in Python as well? FWIW I don't see how a non-zero START would cause issues, it's just the first byte, right? But I haven't attempted to work with RDM devices.

@HakanL
One trick I've only just spotted re-reading the standard as a result of your query is that for START=0 frames, once one frame has been received, ALL subsequent (compliant) START=0 frames MUST be the same length - thus knowing how long the frame is makes it MUCH easier to generate the "end of frame" IRQ more easily. It also makes proper handling of non-zero START frames even more critical, notwithstanding that the bytes which follow the non-zero START are NOT dimmer values - they can be ASCII text messages, used to configure the DMX receivers in other devices, to poll the DMX chain for capabilities and a whole host of other functions.
I'm using a modified version of @jostlowe 's PIO code for the core the DMX receive and transmit, with DMA transfers to/from the main Python code and an IRQ at the end of frame - and it is Python's slowness at responding to that IRQ that causes the race condition currently with short frames. It is hosted on GitHub (https://github.com/MikeEllis-personal/DMXfire) - feel free to look. I expect that following this conversation, I might pick up the project again and implement the START=0 checks and improve the short-frame handling.

Hmm, interesting, but how would one know when the source changes? For example I have an ArtNet-DMX device that can send X channels per frame. I can send ArtNet packets of various length to it, and it will output that many channels per frame, but I believe it just changes on the fly, to my knowledge there's no "down period" to reset the frame length (but I haven't verified). I think it's "safer" to assume that any frame can be of any length, but assume that the gap between bytes is minimal and constant. At least that's what I'm planning to go with :) And use the lack of a valid byte to indicate the end of a frame.

I hooked it up, it seems that it's just changing the frame length on the fly. Granted I didn't hook up a scope, but looking at DMXcat I can see the number of slots changing almost immediately when I vary the number of channels sent over ArtNet. The "speed" settings on some devices/consoles are typically indicating the update/refresh rate (up to 44 Hz). I have an Enttec clone and these are the settings:

Source: https://dmxking.com/downloads/ultraDMX Micro User Manual (EN).pdf
It does note that in "maximum compatibility mode" that it adds a 44uS interslot delay. I have yet to hear of anybody actually using this (I've sold these devices since 2015 in the US/CA). It was primarily added for non-compliant cheapo light fixtures, but I believe those are probably long gone by now. Definitely a valid concern though, but I still think that even if there is an interslot delay, it would be constant in the frame.
Your point about non-zero START frames is definitely valid, and I think if for no other reason than that, that it would be best to support variable frame length in each frame, using some learned frame length in PIO seems a little too complicated (and we're still limited to 32 instructions, I'm at 17 now with stop bit detection).
FWIW I'm not trying to argue, just trying to come up with a solid solution (I'm selling the hardware where my code will run) :)

Please see also https://github.com/jostlowe/Pico-DMX/issues/21#issuecomment-1462486196:
I've used rp2040's "alarm timer" to detect whenever the line is low for at least 88µs (= BREAK) to detect the end of a frame. It's quite reliable but due to the high number of IRQs, the CPU load is a bit high. However, the "end of frame, prepare for next frame" doesn't work as I would expect it. Yet.
We could also use a second PIO SM to detect "the condition" (= line has been low for 88µs) but that would require two SMs (out of 8) for each universe.
Best option would be to have a "LOW for 88µs"-detection in the same state machine as the DMX input code. But I didn't manage that since it would increase the number of instructions and we might need a higher clock rate so we can run "more code" and still don't miss a single bit. I will have a look at your PIO code to see if we can combine that.
Maybe we don't need the DMA's "byte/frame" counter at all and can just rely on the BREAK detection?

@kripton The issue I see with BREAK detection is that in the scenario of <512 channels then we'll miss the last frame sent (unless you have yet another alarm timer to catch when you don't get the next BREAK. Or did I misunderstand how your timers work? I have a discussion on the RPi Forum as well, and at the moment I'm leaning towards trying to abort the DMA transfer when the start/stop bits don't show up (i.e. about one byte after the last byte). I'm not sure this will work, and I haven't figured out how to signal an interrupt in PIO and catch it in the c-code to abort the DMA (and then figure out the transfer count).

@HakanL I get it absolutely, and not seeing you as "arguing" at all - these discussions are where the great ideas come from.
You might like to look at my Python code to see how to do the IRQ from PIO - it's actually very simple. My revised code also includes "IRQ-on-BREAK" detection - but (as I discovered) waiting for the BREAK means the IRQ can be raised too close to the start of frame for the Pico to process it and configure the DMA correctly before the data starts flowing again, resulting in at best the loss of a frame and at worst reception of a corrupted frame.  Writing the code in C rather than Python might be enough to resolve this though.
Most senders I've seen use the BREAK as "start of frame" (and the standard is written with that implication) rather than "end of frame", hence the longest and most variable idle time is the MBB (Mark Before Break) which is allowed to be anything from 0us (i.e. no gap at all between the last STOP bit and the start of the BREAK) all that way up to one full second - around 200us seems to be common. The MAB (Mark After Break) is generally pretty stable and close to the minimum allowed (12us Tx, 8us Rx), as is the BREAK itself (92us min Tx, 88us min Rx).
I'm not sure that "missing the last frame" is a real concern - frames must occur at least once per second, and the transmitter is not allowed to assume that the receiver receives every single one (e.g. due to interference), so the "last frame" really is an edge case for a system which is already broken to all practical intents and purposes. A potentially bigger concern is that if the transmitter is sending the DMX at the slowest rate permitted (1/sec), waiting for the BREAK will introduce almost 1 second of potentially avoidable latency.

@MikeEllis-personal : I'll have a look at your PIO code later, I'm interested about the condition you trigger the IRQ on. Missing a frame is not ideal but tolerable in "only NULL Start code" frames. Losing one frame is really bad when doing RDM though

What might be possible is to modify the PIO assembly so that it reads the number of channels received into a scratch register as the data is received by the PIO. Hopefully it is possible to read the scratch registers from software (?)

As far as I can see from the PIO register map in the RP2040's data sheet, reading (or writing) the scratch registers from the CPU is not possible.
Obscure ways one can transfer additional data:

Push more "bits per DMX channel" to the FIFO, using the upper/unused bits for "status" (as proposed by @HakanL)
When the PIO SM is "paused", one can make it execute a simple program that loads the sratch register and push it to the FIFO. Before re-setting the SM, that is
There is a register DBG_PADOUT for each PIO. It's 32 bit wide (of course) and probably only some GPIOs are driven at a time from one state machine. One could probably set some unused bits from the PIO SM and read that info from the CPU. Crude, Hacky and possibly hard to do with the limited number of instructions

@HakanL Just out of curiosity: What in your application is it that needs to know the exact length of the DMX frame? ☺

@jostlowe I'm building a DMX "re-mapper", that can change DMX channels on the fly so you can for example drive LED RGB fixtures (that may need some channels fixed at 255 to turn on, etc) with simple fader consoles. One use case is for installations where it's hard to change the programming (it was created during installation and then left as-is) but the fixtures have to be moved/replaced. Think theme parks where the programming was created externally when an attraction was built.
So I need to output the same stream that I'm receiving (and making changes on the fly), if I receive 24 channels in then I need to output 24 channels. It could be possible to always output 512 channels, but the issue is that some devices with <512 channels run at higher refresh rate, I need the output to mirror the input as much as possible.

Thanks for all your input. I was able to get this to work now. I ran into one major issue where I needed to do a WAIT, but with a timeout, which obviously doesn't exist in PIO. I had to do a loop while checking for a LOW input, and to get the timing precision I opted to increase the processing speed to 2 MHz (and just adjusting the delays to fit the DMX-512 spec). Since these are breaking changes I'm not sure if it's appropriate to incorporate them here as a PR, I've forked a version and made it available here: https://github.com/DMXCore/Pico-DMX
It now handles varying size packets and I've tried with my fastest sources, my Enttec-clone set to slowest speed, and it handles 1 through 512 channels without issues. The simple console that outputs data at 200+ Hz (24 channels) works great too.
In summary I ended up using the lack of the start/end bits with a 100 uS timeout as an indicator for the end of the packet.

And for clarity, what I ended up using to communicate the number of channels is by reading the DMA transfer count. Because of how DMX works, there is a very defined quiet period, so the DMA is just stalled at that point, which makes it reliable to read the transfer count at that time. Initially I had code that used a counter in the PIO and then pushed that to the FIFO after raising an IRQ. I then compared that to the DMA transfer count, and it was always identical, so then it was cleaner to just use the transfer count.
This could probably be a steppingstone to implement RDM, but at the moment I don't have a need (or time) to implement RDM.
Shameless plug, this is the product I'm building: https://dmxprosales.com/products/dmx-core-pico2

@HakanL thank you


Translations Batch: 2024-02-01

Request and update CiviForm translations using Transifex.
Check weekly if there are new strings needing translations on transifex.
The last string we requested translation for #6252 was: content.adminFooterPrompt for Are you an administrator?, sort by Source String Updated Ascending
Follow the instructions at go/civiform-translations to

[x] Request a new batch of translations
[x] Create a ticket for the next batch of translations, and assign to the next Google.org Works SWE (when translations are sent out)
[ ] Upload translations into Transifex

I noticed that none of the translations added in #6532 have context strings so we'll need to add them too

I noticed that none of the translations added in #6532 have context strings so we'll need to add them too

Yeah I noticed that too - was going to put a topic in the eng weekly reminding people about that and I'll also make sure its in the docs.

Submitted translations for review related to https://github.com/civiform/civiform/issues/5535 and https://github.com/civiform/civiform/issues/6450

Estimated Completion Date: 02/19/2024

https://github.com/civiform/civiform/pull/6686


duplicate uploads

Not much of a bug rather a small detail which could be looked into. I just noticed that, when a file is open in more than a view in Atom (i.e. splitted right), the remote-sync uploads for each view on Save command.
Is it just me or has anyone else noticed this?

@nxet do you still have this issue?

There has been no response to this ticket as such it will now be closed.
If the issue still exists please reply and we will look into it.


improve Umbra shortest path queries

The queries have been improved to avoid block nested loop joins where
possible. Additionally, the initial paths from the initials nodes are
computed before the iteration.

Thanks!


[Code Examples] SimpleFacebookAuthBot doesn't work in Telegram?

App ID: 62516114-227c-436c-8e55-e7dcf50e7474
SDK Platform: .NET
SDK Version: 3.11.0
Active Channels: Skype, Telegram
Deployment Environment: AWS

Reproduction Steps

add bot to contacts
try login

workaround posted https://github.com/Microsoft/BotBuilder/issues/2347#issuecomment-305999604


gateway No resources found , gateway.networking  works

Bug Description
[root]$ kubectl get gateway
No resources found in default namespace.
[root ~]$
[root ~]$ kubectl get gateway.networking
NAME            AGE
linux-gateway   10s
Version
$ istioctl version
client version: 1.12.0
control plane version: 1.12.0
data plane version: 1.12.0 (2 proxies)
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.0", GitCommit:"c2b5237ccd9c0f1d600d3072634ca66cefdf272f", GitTreeState:"clean", BuildDate:"2021-08-04T18:03:20Z", GoVersion:"go1.16.6", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.9", GitCommit:"a5e4de7e277a707bd28d448bd75de58b4f1cdc22", GitTreeState:"clean", BuildDate:"2021-11-16T01:09:55Z", GoVersion:"go1.15.14", Compiler:"gc", Platform:"linux/amd64"}
WARNING: version difference between client (1.22) and server (1.20) exceeds the supported minor version skew of +/-1

Additional Information
install
istioctl install --set profile=default -y

AND
$ istioctl manifest generate -f istio.yaml |  istioctl verify-install -f -
✔ CustomResourceDefinition: authorizationpolicies.security.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: destinationrules.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: envoyfilters.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: gateways.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: istiooperators.install.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: peerauthentications.security.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: requestauthentications.security.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: serviceentries.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: sidecars.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: telemetries.telemetry.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: virtualservices.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: wasmplugins.extensions.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: workloadentries.networking.istio.io.istio-system checked successfully
✔ CustomResourceDefinition: workloadgroups.networking.istio.io.istio-system checked successfully
✔ ServiceAccount: istio-ingressgateway-service-account.istio-system checked successfully
✔ ServiceAccount: istio-reader-service-account.istio-system checked successfully
✔ ServiceAccount: istiod.istio-system checked successfully
✔ ServiceAccount: istiod-service-account.istio-system checked successfully
✔ ClusterRole: istio-reader-clusterrole-istio-system.istio-system checked successfully
✔ ClusterRole: istio-reader-istio-system.istio-system checked successfully
✔ ClusterRole: istiod-clusterrole-istio-system.istio-system checked successfully
✔ ClusterRole: istiod-gateway-controller-istio-system.istio-system checked successfully
✔ ClusterRole: istiod-istio-system.istio-system checked successfully
✔ ClusterRoleBinding: istio-reader-clusterrole-istio-system.istio-system checked successfully
✔ ClusterRoleBinding: istio-reader-istio-system.istio-system checked successfully
✔ ClusterRoleBinding: istiod-clusterrole-istio-system.istio-system checked successfully
✔ ClusterRoleBinding: istiod-gateway-controller-istio-system.istio-system checked successfully
✔ ClusterRoleBinding: istiod-istio-system.istio-system checked successfully
✔ ValidatingWebhookConfiguration: istio-validator-istio-system.istio-system checked successfully
✔ EnvoyFilter: stats-filter-1.10.istio-system checked successfully
✔ EnvoyFilter: stats-filter-1.11.istio-system checked successfully
✔ EnvoyFilter: stats-filter-1.12.istio-system checked successfully
✔ EnvoyFilter: tcp-stats-filter-1.10.istio-system checked successfully
✔ EnvoyFilter: tcp-stats-filter-1.11.istio-system checked successfully
✔ EnvoyFilter: tcp-stats-filter-1.12.istio-system checked successfully
✔ ConfigMap: istio.istio-system checked successfully
✔ ConfigMap: istio-sidecar-injector.istio-system checked successfully
✔ MutatingWebhookConfiguration: istio-sidecar-injector.istio-system checked successfully
✔ Deployment: istio-ingressgateway.istio-system checked successfully
✔ Deployment: istiod.istio-system checked successfully
✔ PodDisruptionBudget: istio-ingressgateway.istio-system checked successfully
✔ PodDisruptionBudget: istiod.istio-system checked successfully
✔ Role: istio-ingressgateway-sds.istio-system checked successfully
✔ Role: istiod.istio-system checked successfully
✔ Role: istiod-istio-system.istio-system checked successfully
✔ RoleBinding: istio-ingressgateway-sds.istio-system checked successfully
✔ RoleBinding: istiod.istio-system checked successfully
✔ RoleBinding: istiod-istio-system.istio-system checked successfully
✔ HorizontalPodAutoscaler: istio-ingressgateway.istio-system checked successfully
✔ HorizontalPodAutoscaler: istiod.istio-system checked successfully
✔ Service: istio-ingressgateway.istio-system checked successfully
✔ Service: istiod.istio-system checked successfully
Checked 14 custom resource definitions
Checked 2 Istio Deployments
✔ Istio is installed and verified successfully

$ kubectl get all -n istio-system
NAME                                        READY   STATUS    RESTARTS   AGE
pod/istio-ingressgateway-76fbf7f599-bztjb   1/1     Running   0          17m
pod/istiod-6b4fcd8b8f-zqn9f                 1/1     Running   0          17m
pod/jaeger-7665fdb96f-df876                 1/1     Running   0          45m
pod/kiali-689668dbdd-schbs                  1/1     Running   0          45m

NAME                           TYPE           CLUSTER-IP        EXTERNAL-IP     PORT(S)                                      AGE
service/istio-ingressgateway   LoadBalancer   <IP_ADDRESS>    20.17.xxx.xxx   15021:32641/TCP,80:32037/TCP,443:30282/TCP   17m
service/istiod                 ClusterIP      <IP_ADDRESS>    <none>          15010/TCP,15012/TCP,443/TCP,15014/TCP        17m
service/jaeger-collector       ClusterIP      <IP_ADDRESS>    <none>          14268/TCP,14250/TCP,9411/TCP                 45m
service/kiali                  NodePort       <IP_ADDRESS>    <none>          20001:32222/TCP,9090:30018/TCP               45m
service/tracing                NodePort       <IP_ADDRESS>   <none>          80:32286/TCP,16685:31864/TCP                 45m
service/zipkin                 ClusterIP      <IP_ADDRESS>   <none>          9411/TCP                                     45m

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/istio-ingressgateway   1/1     1            1           17m
deployment.apps/istiod                 1/1     1            1           17m
deployment.apps/jaeger                 1/1     1            1           45m
deployment.apps/kiali                  1/1     1            1           45m

NAME                                              DESIRED   CURRENT   READY   AGE
replicaset.apps/istio-ingressgateway-76fbf7f599   1         1         1       17m
replicaset.apps/istiod-6b4fcd8b8f                 1         1         1       17m
replicaset.apps/jaeger-7665fdb96f                 1         1         1       45m
replicaset.apps/kiali-689668dbdd                  1         1         1       45m

NAME                                                       REFERENCE                         TARGETS   MINPODS   MAXPODS   REPLICAS   AGE
horizontalpodautoscaler.autoscaling/istio-ingressgateway   Deployment/istio-ingressgateway   5%/80%    1         5         1          17m
horizontalpodautoscaler.autoscaling/istiod                 Deployment/istiod                 0%/80%    1         5         1          17m

Likely it is because you have k8s gateway crd installed before istio gateway API, and kubectl get gateway will list k8s gateway instead of istio gateway.

Likely it is because you have k8s gateway crd installed before istio gateway API, and kubectl get gateway will list k8s gateway instead of istio gateway.

installed after
$ kubectl get crd|grep gateways
gateways.gateway.kubesphere.io                      2021-12-14T04:06:45Z
gateways.networking.istio.io                        2021-12-14T03:57:04Z

$ kubectl delete customresourcedefinition.apiextensions.k8s.io/gateways.gateway.kubesphere.io
customresourcedefinition.apiextensions.k8s.io "gateways.gateway.kubesphere.io" deleted
$ kubectl get gateway
Error from server (NotFound): Unable to list "gateway.kubesphere.io/v1alpha1, Resource=gateways": the server could not find the requested resource (get gateways.gateway.kubesphere.io)

Probably need to wait a bit before getting gateway? Anyway it is not an istio issue..

Probably need to wait a bit before getting gateway? Anyway it is not an istio issue..

resolved thx


Top Nav height increases when I scroll down

Issue: The top nav height increases when I scroll down. This behaviour does not occur on the marketing site.
Fix: Height of the top nav should not change
I have a reference video which was too big to upload here. Will post into Slack

Related to #9434

Related to #9434

sent a fix to make sidebar and top navs all go mobile at the same time.

sent a fix to make sidebar and top navs all go mobile at the same time.


Falco segmentation fault double free or corruption (!prev)

Describe the bug
Falco process crashes with segmentation fault and emits these messages:
* Setting up /usr/src links from host
* Running falco-driver-loader with: driver=bpf, compile=yes, download=yes
* Mounting debugfs
* Found kernel config at /proc/config.gz
* COS detected (build 12371.175.0), using cos kernel headers
* Downloading https://storage.googleapis.com/cos-tools/12371.175.0/kernel-headers.tgz
* Extracting kernel sources
* Configuring kernel
* Trying to compile the eBPF probe (falco_cos_4.19.102+_1.o)
* Skipping download, eBPF probe is already present in /root/.falco/falco_cos_4.19.102+_1.o
* eBPF probe located in /root/.falco/falco_cos_4.19.102+_1.o
* Success: eBPF probe symlinked to /root/.falco/falco-bpf.o
Thu May 21 05:20:04 2020: Falco initialized with configuration file /etc/falco/falco.yaml
Thu May 21 05:20:04 2020: Configured rules filenames:
Thu May 21 05:20:04 2020:    /etc/falco/falco_rules.yaml
Thu May 21 05:20:04 2020:    /etc/falco/falco_rules.local.yaml
Thu May 21 05:20:04 2020: Loading rules from file /etc/falco/falco_rules.yaml:
Thu May 21 05:20:05 2020: Loading rules from file /etc/falco/falco_rules.local.yaml:
double free or corruption (!prev)

Frequently it does not emit any message and silently crashes at the same position (seemingly, no syscall events are emitted to the log, as well)
Here is the current count of restarts from my staging environment.
NAME          READY   STATUS    RESTARTS   AGE
falco-5jxkz   2/2     Running   3          5h31m
falco-6kqn7   2/2     Running   7          5h35m
falco-6w2wh   2/2     Running   5          5h33m
falco-9ngz6   2/2     Running   7          5h33m
falco-d7t89   2/2     Running   7          5h34m
falco-dvzdm   2/2     Running   3          5h35m
falco-g8bwf   2/2     Running   8          5h33m
falco-jjvwn   2/2     Running   4          5h31m
falco-jxnzf   2/2     Running   3          5h30m
falco-n9njg   2/2     Running   7          5h32m
falco-plk84   2/2     Running   7          5h33m
falco-pv9wz   2/2     Running   0          5h32m
falco-pzhb6   2/2     Running   3          5h31m
falco-v5lhj   2/2     Running   3          5h30m
falco-xvlx8   2/2     Running   4          5h34m
falco-z4dqd   2/2     Running   8          5h35m
falco-zzmql   2/2     Running   1          5h34m

How to reproduce it
I don't really have minimal/precise steps. The staging environment we are testing on is of considerable scale - we are working through figuring out compute allocation as well as dealing with syscall drops. The configuration is mostly default beyond enabling the gRPC server. I have not yet experimented with disabling rules entirely but am considering it until we can be sure the segmentation faults and syscall drops can be mitigated.
Complete (redacted) manifest here: https://gist.github.com/fujin/384b41af022cef939479cbb3ec0c88d6
I found a one-liner in another issue that prints the last logged line from the previously exited container, thus:
for pod in `kubectl get pods --no-headers -l app=falco -o custom-columns=":metadata.name"`; do echo -n "$pod exited with: "; kubectl logs $pod -c falco --previous | tail -n 1; done

Expected behaviour
The code, configuration, or environmental condition causing segmentation fault should be isolated and repaired.
Screenshots

Environment
< Falco version:
Falco version: 0.23.0
Driver version: 96bd9bc560f67742738eb7255aeb4d03046b8045

System info:

{
  "machine": "x86_64",
  "nodename": "gke-gke-stage-general-02-b1d1b568-176z",
  "release": "4.19.102+",
  "sysname": "Linux",
  "version": "#1 SMP Tue Feb 11 05:33:03 PST 2020"
}

Cloud provider or hardware configuration: GKE
OS: Container-Optimized OS build 12371.175.0w/ kernel

Kernel: 4.19.102+

Installation method: Kubernetes, manifests attached in reproduction section.

Additional context

Nodes: 7x n2-standard-32 pools, 1x n2-standard-8
Cluster: 32 nodes total, 952vCPU/3808GB RAM.
Pods: 453~ total.
Other: gRPC server enabled, a modified Falco Exporter is subscribing to events.

Same environment as #1231

@fujin: There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hey @fujin
Is this issue still present in Falco 0.25.0?

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


Null Reference Exception preventing use

I've gotten this a number of times over the past couple of days; the first few times, restarting Procurement let it work, but not since this afternoon.
[07-09-2015 16:23] Error downloading stash for Warbands, exception details: System.NullReferenceException: Object reference not set to an instance of an object.
at POEApi.Model.POEModel.GetStash(String league, String accountName)
[07-09-2015 16:23] System.Exception: Downloading stash for Warbands, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues
at POEApi.Model.POEModel.GetStash(String league, String accountName)
at Procurement.ViewModel.LoginWindowViewModel.LoadStashItems(Character character)
at Procurement.ViewModel.LoginWindowViewModel.d__6.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
at Procurement.ViewModel.LoginWindowViewModel.<>c__DisplayClass2.b__1()
at System.Threading.Tasks.Task.Execute()

Did you change any settings or anything, or did Procurement just suddenly start Procuring this error?


Save table prediction in cells format

This pull request allows to return predictions in raw cell representation from table transformer. It will be later used in unstructured repository to save prediction in a cells format for simpler metrics calculation

For the unit tests:

The 'cells' type was previously tested in this function https://github.com/Unstructured-IO/unstructured-inference/pull/335/files#diff-56b4d700e2ed72befcaf37f68f915270aacece7bfdba7ce12906bf8d6efcf485R926
I have added unit test for raising error when the type is wrong

Bumping version:

Last released version is 0.7.25, the change-log was edited for 0.7.26. Is there any script to bump version you referring to? How can I bump version?

Not passing test_ingest:

@badGarnet could you guide me how to debug this problem? I looked into logs and I do not see any stacktrace and errors

the version bump is just edit both the CHANGLOG.md and unstructured_inference/__version__.py to match. We could add a ci lint check to ensure those two are consistent.
The ingest test failing can be ignored for now (it is not required anyway); we should take a look and maybe remove this step as it has been out of date for a while.


not in a resolved environment on Windows

Hi !
Maybe I'm missing something, but after installing rez and do a quick rez-bind --quickstart, when I set an environment with rez-env, python for example, aliases work great but it's seems like no environment is keeped.
C:\Users\Sam>rez env python
resolved by Sam@MSI, on Sun Aug 13 16:17:11 2017, using Rez v2.13.1

requested packages:
python
~platform==windows       (implicit)
~arch==AMD64             (implicit)
~os==windows-10.0.14393  (implicit)

resolved packages:
arch-AMD64             C:\Users\Sam\packages\arch\AMD64                                                       (local)
os-windows-10.0.14393  C:\Users\Sam\packages\os\windows-10.0.14393                                            (local)
platform-windows       C:\Users\Sam\packages\platform\windows                                                 (local)
python-2.7.13          C:\Users\Sam\packages\python\2.7.13\platform-windows\arch-AMD64\os-windows-10.0.14393  (local)

C:\Users\Sam>rez context
not in a resolved environment context.

C:\Users\Sam>python
'python' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.

So, dependency packages don't work as well, when I call one that need other packages, previous env are not keeped ..
Sorry maybe it's look like a noob issue ?
Thanks,
Nicolas

Ok, because I use rez in Linux normally, I was a bit confused by that, but it seems to work great with -c CMD as in #375 . Some fixes added : #377 .

Ok yeah looks as though #377 adds the necessary fixes for this, although I
think as well that we should drop sh/pbs completely, they're just fancy
subproc handlers and it doesn't seem worth the trouble they're causing on
Windows.
Should be able to start addressing these issues in the coming weeks, away
on vacation atm.
Cheers
A
On Wed, Aug 16, 2017 at 4:16 AM, Nicolas Castelli<EMAIL_ADDRESS>wrote:

Ok, because I use rez in Linux normally, I was a bit confused by that, but
it seems to work great with -c CMD as in #375
https://github.com/nerdvegas/rez/issues/375 . Some fixes added : #377
https://github.com/nerdvegas/rez/pull/377 .
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nerdvegas/rez/issues/452#issuecomment-322545908, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABjqSuGC0HRFHUN3m-dHWAOAFxVu_T6Fks5sYeCBgaJpZM4O1tA3
.

I did some work on that already for our pre-production deployment branch. The main open question is about the classmethod for export(). On vacation too though, so greetings from Malta and have a good one Alan :)

I should have been clearer. By "work on that" i meant dropping sh.

For reference i created a separate issue for dropping sh as i ran into things i am not sure i understand heh #459

Just confirmed that the example @NicolasCastelli gave has been fixed with #377 and the issue is solved when using version 2.18.0.
I think we can close this issue.

Fixed by https://github.com/AcademySoftwareFoundation/rez/pull/377


Crash when connecting relay to a normal connection

http://pastebin.com/Ra26gYVw

And this, folks, is why you should always test your mods outside of the dev environment before releasing. Will push out a hotfix for it now.


Roll up coverageThresholds set in project configs

🚀 Feature Proposal
Roll up the coverageThresholds config blocks from projects to work like you had added the projects to the coverageThresholds paths.
Motivation
Allowing users to configure their project thresholds individually and rolling up is a lot like what is already in place for configuring thresholds, only it would be more convenient with how projects are used.
Example
jest.config.js
module.exports = {
  collectCoverage: true,
  collectCoverageFrom: ['**/src/**/*.js'],
  coverageThreshold: {
    global: {
      statements: 78,
      branches: 65,
      functions: 70,
      lines: 70,
    },
  },
  projects: ['packages/*/jest.config.js'],
  watchPlugins: [
    'jest-watch-typeahead/filename',
    'jest-watch-typeahead/testname',
  ],
};

packages/a/jest.config.js
const { resolve } = require('path');
const base = require('@cnc/config/jest/jest.config');

const rootDir = resolve(__dirname);

module.exports = {
  collectCoverageFrom: ['**/src/**/*.js'],
  transform: {
    '^.+\\.jsx?$': resolve(__dirname, 'babel-transform.js'),
    '.*': '@brimstone/jest-static-assets-mocker',
  },
  snapshotSerializers: ['@wldcordeiro-stuffz/snapshot-diff-serializer'],
  testURL: 'http://localhost',
  watchPlugins: [
    'jest-watch-typeahead/filename',
    'jest-watch-typeahead/testname',
  ],
  rootDir,
  displayName: 'breadcrumb tests',
  setupTestFrameworkScriptFile: './test-setup.js',
  coverageThreshold: {
    global: {
      statements: 100,
      branches: 100,
      functions: 100,
      lines: 100,
    },
  },
};

packages/b/jest.config.js
const { resolve } = require('path');
const base = require('@cnc/config/jest/jest.config');

const rootDir = resolve(__dirname);

module.exports = {
  collectCoverageFrom: ['**/src/**/*.js'],
  transform: {
    '^.+\\.jsx?$': resolve(__dirname, 'babel-transform.js'),
    '.*': '@brimstone/jest-static-assets-mocker',
  },
  snapshotSerializers: ['@wldcordeiro-stuffz/snapshot-diff-serializer'],
  testURL: 'http://localhost',
  watchPlugins: [
    'jest-watch-typeahead/filename',
    'jest-watch-typeahead/testname',
  ],
  rootDir,
  displayName: 'breadcrumb tests',
  setupTestFrameworkScriptFile: './test-setup.js',
  coverageThreshold: {
    global: {
      statements: 100,
      branches: 100,
      functions: 100,
      lines: 100,
    },
  },
};

Pitch
You can already go into your root configuration and define thresholds on a per path/file basis, this would be similar only it would allow for each package in a monorepo to define a threshold close to itself.

@rickhanlonii @SimenB anyone? This seems like something that should work with the projects feature. 🤔

@rickhanlonii I would be, I think I'd need some help though as I haven't done any coding in the Jest codebase before.
General questions:

Do I need to get the CLA signed?
What packages would I work on this change in?
Are there any PRs I could use as a "template" for how to best contribute?

I want to get off on the right foot here and make things as easy for maintainer to review once I have a PR ready.


GOMAXPROCS setting in config file not respected

I am using version 1.3.5, branch HEAD, commit 9d9001036d3585cf21925c13a57881bc6c8dcc7e
Steps to reproduce :-

Add the following line to config file :-
GOMAXPROCS = 8
Start influxd with the above config file
Observe the following line in the output :-
Go version go1.8.3, GOMAXPROCS set to 24

Expected behaviour :- GOMAXPROCS set to 8
Actual behaviour :- GOMAXPROCS set to 24
It works as expected if I use an environment variable however.

This is a Go environment variable, not an InfluxDB specific setting.  There is no config file option to set this.

That's not what this says :-
https://docs.influxdata.com/influxdb/v1.4/administration/config/#global-options

The list of environment variables is listed in the documentation at :-
https://docs.influxdata.com/influxdb/v1.4/administration/config/#environment-variables

The documentation isn't clear and is incorrect.  It is not settable via the config.  You can only set it via the environment variable.
Only the options listed in the config (influxd config) are settable via environment variables and they are prefixed with INFLUXDB_.
I have opened a docs issue https://github.com/influxdata/docs.influxdata.com/issues/1357 highlighting this issue in the docs.

I see you created a similar issue in https://github.com/influxdata/docs.influxdata.com/issues/1356.  I'll close the one I just created.


Refactor Stage 2: HandlerContext, Document Control, Internal Messaging

Expanded refactor after #282
Moves document lifecycle management into extension.
Abstracted most extension document interaction into context - storage interaction remains to be refactored.
Deletes the stdRouter, in favor of document-specific handlers more closely associated with the functionality.

Is there generally any downsides to using a Context mechanism for managing and sharing state across multiple levels of the component tree? More specifically, what's happening internally (simply messaging passing?) that enables the custodyClient to be callable by the viewClient in a context setting?

Is there generally any downsides to using a Context mechanism for managing and sharing state across multiple levels of the component tree? More specifically, what's happening internally (simply messaging passing?) that enables the custodyClient to be callable by the viewClient in a context setting?

context should be used to abstract interfaces of the extension that the implementation needs to access. context should not be used to share state directly, because context objects are not reused - they are created new for every activation of a handler. but, context may be used to inject state known to the adapter or router at request time, or to provide a queryable interface to state.
context is provided by a function parameter to the adapter. our context creation function is in service-worker.ts
https://github.com/penumbra-zone/web/blob/34cd33bfc1a2112e4c21240f576fa33da1f8165b/apps/extension/src/service-worker.ts#L114-L129
it's used in adapter.ts to inject state. the adapter knows nothing of our extension architecture, it's a generic 'chrome runtime to connectrpc' adapter, and we're configuring it with our function def in service-worker. there are comments in adapter.ts that may be informative.
https://github.com/penumbra-zone/web/blob/34cd33bfc1a2112e4c21240f576fa33da1f8165b/packages/transport/src/chrome-runtime/adapter.ts

it's also worth understanding that contextValues is not the only thing contained within HandlerContext
https://github.com/connectrpc/connect-es/blob/cc6662442d2502f04dceb155d85c4b0208017840/packages/connect/src/implementation.ts#L69
it provides features for interacting with / gaining information about the request itself, and respecting things like timeouts and aborts, which are managed by the adapter


Restore DefaultTestOptions port to 4222

This is used by RunDefaultServer() and some external projects tests
may rely on the fact that this runs on the default port.
Our tests that want to use ephemeral ports to avoid port conflicts
should be updated to not use these default options and/or RunDefaultServer().

Coverage decreased (-0.2%) to 92.113% when pulling 72bbd2b98211d1c799737f8d9e3a8a02b8902d0c on restore_default_test_options_port into fa662bbfdb5e671a26412b335f86d18c46049281 on master.


Adds camel-jolokia-starter

@mcarlett Do you mind adding the starter's name to the list of starters in product/src/main/resources/required-productized-camel-artifacts.txt?

thanks @cunningt for the reminder, I will close this and I will open another one once the upstream PR will be merged

this pr is replaced by #437


[vcpkg baseline] Update discordcoreapi, jsonifier version

Fixed CI pipeline issue:
F:\vcpkg\buildtrees\discordcoreapi\src\8b54cf9-9e5ee11bfa\Source\FoundationEntities.cpp(42): error C2593: 'operator =' is ambiguous
F:\vcpkg\buildtrees\discordcoreapi\src\8b54cf9-9e5ee11bfa\Include\discordcoreapi/Etf.hpp(438): note: could be 'DiscordCoreInternal::EtfSerializer &DiscordCoreInternal::EtfSerializer::=<uint64_t>(_T0) noexcept'
        with
        [
            _T0=uint64_t
        ]

Related Upstream issue: #32, #2

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Thank you!


[Dupe] Item duping when trying to remove an IC2C machine from someone else's claim

Dupes the blocks + the inventory of the block when you're trying to remove an IC2C machine with a wrench on a claim where you are not trusted.
https://www.youtube.com/watch?v=OJp10YnPQMg
Video for demonstration.

Same issue with Thermal expansion : https://www.youtube.com/watch?v=psftoxD1lfM

I found that "interact-block-secondary" was set to "true" thats why it happened.


[MPG] add more doc and modify update function

This pull request resolves #450.
The pull request is ready to be merged.
The details of the pull request:

modify update function to abstract method.
add more doc to nas.md

Coverage increased (+0.06%) to 93.645% when pulling 44ad71813d1d7d8bcf1fa3b4ad0058a409199d90 on chengchengeasy:refactor into f455e22c140775975f5061354dc78cdf6b52dc26 on jhfjhfj1:master.


Error logging in (ERROR: Navigated to password page for the  2nd time. Exiting...)

I set up the add-on yesterday and was able to successfully retrieve my data usage and migrate it into HA that morning. However, after that first time, it now consistently gives the "ERROR:  Navigated to password page for the  2nd time. Exiting..." error. This continues 2-3 times before eventually hanging with high CPU/RAM usage. I have already attempted reinstalling the add-on (choosing to wipe data) as well as resetting my configs and reentering all info. I have also confirmed I am able to login with the credentials used in the config via my browser, and I do not have 2FA enabled. Attached are the debug logs. Thanks for this app, it is MUCH appreciated, wish Xfinity made it easier to track usage.
logs.pdf

To add, not sure if my password should be in plain text in the logs (assume it should for XFINITY_PASSWORD) and if so, it appears that the add-on is ignoring my actual password in my config and replacing it with a string of random characters.

I had luck with the new version for a few hours and it started failing again. Same problem.

Let know if v<IP_ADDRESS> helps.  Xfinity's bot detection is causing a lot of headaches.

Let know if v<IP_ADDRESS> helps. Xfinity's bot detection is causing a lot of headaches.

Yup, hat worked! Thank you for your work on this, much appreciated!


How to install

Thanks for this beautiful player
It's a great job you did.
Unfortunately
I do not know how to install on the hosting of my site.. cpanel shared hosting ..
How do I generate a link like this.  https://appsdev.cyou/player/v1/current/player.min.js
It is hosted on my website hosting.
I don't know what it is and how npm works
Can I upload the entire video player file to my site
But how do I create a javascript link to the video player.
I don't know the correct way
I searched for several months but did not know how it works.
thank you so much for your help i really appreciate it .

to build this project and get the player.min.js, follow this:
first you need to install the latest version of nodejs
the easy way to install is to download it from the nodejs official website

https://nodejs.org/es/

download the "LTS" version
the other way is to use a manager that allows you to install multiple nodejs versions

https://github.com/nvm-sh/nvm

once installed, check in your console, if the installation was successful,
using node -v and npm -v

then you clone the project, there are several ways, from the web by .zip or by git

https://git-scm.com/

then open a new console and go to the project location
and from there run npm install
then if the packages are installed correctly, run npm run build-dev
if everything went well, in the dist location,
you will see several html files and player.min.js

now, if you want to use this player.min.js in only one web page,
just run npm run build
copy dist content to your website,
you will have to copy the files everywhere you want to use the player

if you only want to be on a single site and be used by several web pages,
run npm run build-cdn
this will generate several files in dist-cdn

copy the entire v1 folder to your main web page
and now you can use it wherever you want
by default is assigned the path https://appsdev.cyou/player,
so just swap it for yours, https://{YOUR_DOMAIN}/player
in the desploy.json file
run again npm run build-cdn
in the hosting, create the player folder
and copy the whole v1 folder (including the same folder) to your hosting
and your script would look like this
<script src="https://{YOUR_DOMAIN}/player/v1/current/player.min.js"></script>

any other questions, let me know

Excuse me for being a beginner
So this question came to my mind
Why should the script be configured with nodejs
Why not upload script files directly to the site?
I don't understand why exactly this way.
The important ...
It seems that the program does not work on Windows 7.
So I downloaded an older version of the program. v14.0.0 (node-v14.0.0-x64.msi

Do I need to download the latest version of nodejs?

nodejs is used to facilitate several jobs when building the final player.min.js file,
such as joining all the separate modules you see in src, translating the code to one that all browsers can understand.
you entered the nodejs interface, exit by typing .exit
and in the windows console, execute all the commands mentioned above.
the version you use also works.

i beg your pardon .I want you to explain in more detail.
windows console its cmd.exe .. right ?
download this to my computer
https://github.com/Joel2B/Custom-Video-Player/archive/refs/heads/master.zip
whats mean  project location..
something like this
K:\folder\Custom-Video-Player-master.zip npm install
What exactly do I type in cmd?
I'm stuck on the first step

right, with cmd.exe
download and extract the master.zip file with WinRAR,
or any other program that allows you to decompress rar files.
Copy the folder location and in your cmd,

type cd \d  and then paste the location, will look like this
cd \d K:\folder\Custom-Video-Player-master
press enter, and then type npm install

don't worry, if still is not clear, keep writing to me

I finally did it .
I uploaded these files from K:\Custom-Video-Player\dist-cdn\v1\current
to my site .

Do I have to upload the other files that appeared in the dist file to my site?
I mean these files

I only uploaded these 3 files to my site .

Now the video player is working .
I'm just wondering what is the difference between the player.min.js script file produced by nodejs .
And your https://appsdev.cyou/player/v1/current/player.min.js script file that I can downloaded and upload to my site.
Especially I just changed this "cdn": "https://appsdev.cyou/player" in deploy.json .
thank you so much

If you download the player.min.js from appsdev.cyou, and upload it to your website,
will point all resources as images to the appsdev.cyou domain.
then to avoid that you change the domain, as you said, in deploy.json,
and now that nodejs player.min.js will point to the domain you specified,
and you can upload it to a primary website, and use it on any website.
the advantage of building your own build, is that you will not depend on appsdev.cyou,
in case that stops working, you will have the player.min.js on your web page,
the disadvantage is that when i make changes to the source code,
you will have to do git pull, npm run build-cdn, upload it back to your site
to apply the latest changes to all your websites.


Fix COGS script to not call API redundantly

(You might need to request another review as the branch protection rule requires 2 on this repo now.)


Feature#2601 Check RoutingResult.

Fixes https://github.com/apache/incubator-shardingsphere/issues/2601.
Changes proposed in this pull request:

add checker in ParsingSQLRouter for check RoutingResult.
add ParsingSQLRoutingResultChecker to check RoutingResult with ShardingRule.RoutingUnits.
add, modify some UTs.

Reflect is only in AbstractSpringJUnitTest.java for unit test to reload MetaData after create table.

We can discuss which sql should be check. In my view, we can divide the check into two parts, dataSource check and table check. In this PR table check for DML, and dataSource check for no master-slaver.

It's right to check all the DMLs. You can take a performance test for comparision.

Pull Request Test Coverage Report for Build 325

43 of 95 (45.26%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 63.846%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/sharding-core-api/src/main/java/org/apache/shardingsphere/api/config/sharding/strategy/InlineShardingStrategyConfiguration.java
0
1
0.0%

sharding-core/sharding-core-route/src/main/java/org/apache/shardingsphere/core/route/router/sharding/ParsingSQLRoutingResultChecker.java
38
89
42.7%

Totals

Change from base Build 349:
-0.1%

Covered Lines:
9319

Relevant Lines:
14596

💛  - Coveralls

I run jmeter with SELECT * FROM t_order WHERE order_id = 3 (2 threads, 100 loop counts) and find there was not performance impact basically. Because there is no String + String operation when check pass, and JVM will optimize String + String operation.

I run jmeter with SELECT * FROM t_order WHERE order_id = 3 (2 threads, 100 loop counts) and find there was not performance impact basically. Because there is no String + String operation when check pass, and JVM will optimize String + String operation.

OK.
Please resolve the coverage decreasing.


Inconsistent Tip Position During Transfer

Expected Behavior

When a single transfer command is broken down into multiple sub-transfers, each sub-transfer should use the same tip height.

Observed Behavior

Only the first sub-transfer uses height specified in protocol; following transfers use default height.

Steps to Recreate
Note did not recreate this on a robot; steps per Kinnari's bug report and Seth's code review.

Create a protocol with a single transfer from one well to another, a transfer volume greater than the maximum pipette capacity, and a initial tip height higher than the default (1mm) height.
Observe that pipette moves to specified initial tip height for initial transfer, and then to default 1mm tip height for subsequent transfers.

This is a known issue - or really, known not to be a feature - in protocol API v1. In protocol API V2, it works: you can specify locations (the output of Well.top() or other location accessors) in your source and destination lists and they'll be respected even if the transfer plan has to split them up:
This is the internals of a transfer. The transfer plan is the sequence that the robot will execute. Note that the positions it uses correspond with the .top(z=5) I specified in the source and destination lists:
>>> from opentrons.protocol_api import transfers
>>> from opentrons import simulate
>>> ctx = simulate.get_protocol_api('2.0')
>>> tr = ctx.load_labware('opentrons_96_tiprack_300ul', '1')
>>> plate = ctx.load_labware('corning_96_wellplate_360ul_flat', '2')
>>> instr = ctx.load_instrument('p300_single', 'right', tip_racks=[tr])
>>> tp = transfers.TransferPlan(600, plate['A1'].top(z=5), plate['A2'].top(z=4), instr, 300)
>>> itp = iter(tp)
>>> next(itp)
{'method': 'pick_up_tip', 'args': [], 'kwargs': {}}
>>> next(itp)
{'method': 'aspirate', 'args': [300, Location(point=Point(x=162.88, y=106.24, z=67.22), labware=A1 of Corning 96 Well Plate 360 µL Flat on 2), 1.0], 'kwargs': {}}
>>> plate['A1'].top(z=5)
Location(point=Point(x=162.88, y=106.24, z=67.22), labware=A1 of Corning 96 Well Plate 360 µL Flat on 2)
>>> next(itp)
{'method': 'dispense', 'args': [300, Location(point=Point(x=171.88, y=106.24, z=66.22), labware=A2 of Corning 96 Well Plate 360 µL Flat on 2), 1.0], 'kwargs': {}}
>>> next(itp)
{'method': 'aspirate', 'args': [300, Location(point=Point(x=162.88, y=106.24, z=67.22), labware=A1 of Corning 96 Well Plate 360 µL Flat on 2), 1.0], 'kwargs': {}}
>>> next(itp)
{'method': 'dispense', 'args': [300, Location(point=Point(x=171.88, y=106.24, z=66.22), labware=A2 of Corning 96 Well Plate 360 µL Flat on 2), 1.0], 'kwargs': {}}
>>> next(itp)
{'method': 'drop_tip', 'args': [], 'kwargs': {}}


Condition: Dx of In Utero Exposure to DES

Mick entered a comment in the DER that the only DE being used in the CDS is code. How can that be? Aren't we displaying a date next to the entry on the dashboard? Will you be including the constrained verificationStatus' that we agreed on on 5/10?

Sorry, I should have been clearer by that comment. code is the only element that is needed by the actual logic for a DES Exposure Condition, since the logic only needs a simple yes/no to "Were you exposed to DES?". But you're correct, when we display this in the dashboard, we display all of the same elements as we do for other Conditions:

code
clinicalStatus
onset[x]
recordedDate

Would you like me to add the constraints for verificationStatus to the DES Exposure queries? Should these be applied to all conditions, or just this one and the Cervical Vaginal Lesions Condition mentioned in https://github.com/ccsm-cds-tools/ccsm-cds-with-tests/issues/18?

I added constraints for verificationStatus to the DES Exposure queries, since we agreed in Issue #11 to add this constraint to all conditions.
Between the addition of the verificationStatus constraint and the clarification of the data elements used in the dashboard in my original comment, I believe all concerns about this issue were addressed. I will close this out, but feel free to re-open if there are further issues.


Add Branch Search Functionality

I would like to suggest a feature to search through the list of branches when creating a pull request from the extension.
Currently, the list of branches is not searchable, making it slightly difficult to quickly find and select the desired branch, especially when working with a large number of branches. A search feature would allow users to easily filter the list of branches based on specific keywords or phrases, making it more efficient and user-friendly.
This feature would be a nice addition to the extension as it would make the pull request process smoother and less time-consuming, particularly for those who work with a large number of branches.

@galezra you can start typing when the branch dropdown is open to navigate quickly to a branch.

When one types a few characters in the list, the context of the search is disjointed, so a branch-specific search box would be useful, like this:

This has moved into a quick pick, making it much more searchable.

Awesome! 🚀


python: can't open file './main.py': [Errno 2] No such file or directory

I am new with Docker, and I am trying to run a minimalist python example.
Here is the Docker file:
FROM python:3.5
CMD ["python", "./main.py"]

The build is fine:
Sending build context to Docker daemon 3.072 kB
Step 1 : FROM python:3.5
 ---> 1d0326469b55
Step 2 : CMD python ./main.py
 ---> Using cache
 ---> a0f7fad9414e
Successfully built a0f7fad9414e

However when I try to run:
python: can't open file './main.py': [Errno 2] No such file or directory

The doc says that it copies the directory content to /usr/src/app, but didn't see anything there.
Any ideas?

The docs specifically mention using one of the onbuild images.  Its steps automatically COPY in your directory and install dependencies so that your code is available in the resulting image and container.  It is the same as running this in your Dockerfile.
FROM python:3.5

RUN mkdir -p /usr/src/app
WORKDIR /usr/src/app

COPY requirements.txt /usr/src/app/
RUN pip install --no-cache-dir -r requirements.txt

COPY . /usr/src/app
CMD ["python", "./main.py"]

Closing old issue.

python3: can't open file 'kickthemout.p': [Errno 2] No such file or directory
please help?

edefef

I have the same issue：
python: can't open file './main.py': [Errno 2] No such file or directory
why?

Wrong interpreter, it could be that you're project interpreter is inside a vritualenv or docker, that's what worked for me :)

python2: can't open file 'admin_panel_finder': [Errno 2] No such file or directory faceing this problem or can anyone gide me how to find any website login link for sql injection please


Separate endpoint for subscriptions

I can't see this anywhere in the examples. Is it possible to have a separate subscriptions endpoint alongside the usually graphql one?
With my current setup below, I'm not sure it's possible to add subscriptions to my normal graphql endpoint
// GraphQL struct handles GraphQL API request over HTTP.
type GraphQL struct {
	handler          *relay.Handler
}

// NewGraphQL creates a new GraphQL handler.
func NewGraphQL(s *graphql.Schema, ll loader.Map, c *config.Config) *GraphQL {
	return &GraphQL{
		handler: &relay.Handler{
			Schema: s,
		},
	}
}

Within my main.go
s = graphql.MustParseSchema(schema.String(), r)

h := handler.NewGraphQL(s)

router.Handle("/graphql", logging.LoggingHandler(h))

Thanks

You don't need a separate endpoint to handle subscriptions. Your code will already handle subscriptions just fine.

https://github.com/graph-gophers/graphql-transport-ws


⚠ Bofrost.at has degraded performance

In cd6a1e7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2491 ms

Resolved: Bofrost.at performance has improved in a730400.


CAMEL-9449 - Allow to specify custom exit code when camel exits due t…

…o expired Duration

Thanks code is merged. Do you mind closing this PR


Added check connectivity api to network watcher swagger

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[ ] The title of the PR is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[ ] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[ ] If applicable, the PR references the bug/issue that it fixes.
[ ] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[ ] I have read the contribution guidelines.
[ ] My spec meets the review criteria:

[ ] The spec conforms to the Swagger 2.0 specification.
[ ] The spec follows the guidelines described in the Swagger checklist document.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@irrogozh is this "check connectivity" method available on 2016-09-01 and 2016-12-01? If so, it's important for the CLI to update them as well (profile support).
@johanste @derekbekoe for comments

lmazuel, it will only be available for latest version

 https://github.com/Azure/azure-sdk-for-ruby/pull/770

 https://github.com/Azure/azure-sdk-for-python/pull/1129

No modification for NodeJS


[Card] Additional sizes and names

What package is this for?

[x] React
[ ] Angular

Summary
PAL card guidance
In the PAL, the card component has 5 card sizes and a different naming structure than what is in React. This was due to the card existing in code before with no documentation on the site, and then the dashboard guild working on cards later on.
I've updated the guidance to align on the sizes available in React, but this issue is to also include 2 additional card sizes, and to update the naming convention we have for the card widths and heights.
After talking to @davidicus about it, we won't be replacing the existing names for those using it, but adding additional names to the card sizes.

Card widths:

Extra small: 4 columns
Small: 6 columns (new size)
Medium: 8 columns
Large: 12 columns (new size)
Extra large: 16 columns

Card heights:

Short: 144 px
Regular: 304 px
Tall: 464 px (new size)
Extra tall: 624 px

Based on what I see in the [storybook], the 1:1 mapping for these new names would be:

Existing name
New name

SMALL
Extra small, Short

SMALLWIDE
Medium, Short

SMALLFULL
Extra large, Short

MEDIUMTHIN
Extra small, Regular

MEDIUM
Medium, Regular

MEDIUMWIDE
Extra large, Regular

LARGETHIN
Extra small, Extra tall

LARGE
Medium, Extra tall

LARGEWIDE
Extra large, Extra tall

Would it make sense to separate out the width and height sizes for more flexibility?

@davidicus @dianatran18 "we won't be replacing the existing names for those using it, but adding additional names to the card sizes."   I guess that would be because chaning the names would break a lot of contracts downstream. Would this mean that we expose duplicative size options, though? It seems like we are only adding more potentialy for confusion, since none of these names are ever referenced in the designs handed over to development anyway (that I know of)

Blocks https://jsw.ibm.com/browse/GRAPHITE-48767

@JordanWSmith15 @jessieyan yes. We can't remove the old names but we will take them out of the documentation which should be done along with this work. Instead just referencing the new "official" names.

@dianatran18 Hi Diana, would you please offer more information on the size dimensions?
For example, in the existing design we have 6 breakpoints for size SMALL.
SMALL: {
max: { w: 4, h: 1 },
xl: { w: 4, h: 1 },
lg: { w: 4, h: 1 },
md: { w: 2, h: 1 },
sm: { w: 2, h: 1 },
xs: { w: 4, h: 1 },
},
for breakpoint max, we have width: 4 columns and height: 1 row.
Do you have anything similar for the new names? Thank you!

@dianatran18 Please help us with the breakpoint mapping. Also the image above does not take into account for 2 column cards. @JordanWSmith15 Correct me if I am  wrong, but this was an issue for Health the last time we updated our grid sizes and we had to revert some changes.

@davidicus @jessieyan we should only be adding new sizes, not altering existing ones, so I don't expect that we'd effect any app teams downstream

@jessieyan we will have to talk about the best way to support these new sizes without breaking existing dashboards. The small, for instance, is calling for 6 columns but, as you pointed out in your comment above, we have historically had 4 columns wide for Small cards.

@JordanWSmith15  We can add the names, but from the image above in the issue description it shows a new mapping to the amount of grid rows. We can add the new names and then change new sizes in major release. Or we can provide a modified name to support the official grid size until next major.

I don't like changing the names of the existing sizes much myself, as that definitely would effect downstream consumers. I am only interested in making the new sizes  available, particularly the 12 column width ones.

The confusing part is that "small" in the existing card naming convention is referring to the height of the card. In the new naming convention, "small" is referring to the width.

Small, medium, large, etc. makes more sense as a width than it does a height. That follows what other components use, like modals. The current naming wasn't consistent either. For example, the "SMALLWIDE" is 8 columns, but "MEDIUMWIDE" and "LARGEWIDE" are 16 columns. Short, regular, tall, etc. makes a lot more sense as heights.
To account for the 2 column card size, it would be something more like this... I know teams have been using it already, but I still wouldn't surface that card size, because it can barely fit any content, and is not scalable. I just put "mini" for now, but I'll confirm with Robin on what we could call it.

Trying to shoehorn additional card sizes in an existing naming convention that is already confusing isn't a good solution. Is there any way we could create a fresh set of cards with the new naming convention and new card sizes in the major release, that are customizable so teams can put anything they want in them? I thought the cards now are not as flexible as we'd like anyways, so it seems like a good opportunity to correct the cards and build them to be more flexible.

@dianatran18 Agree that we need to update this, but the there is a blocking dependency side and a technical debt side to this story that will need to be split out. Let me explain a bit:
For the blocking dependency, we have designers using the 12 column width sizes in designs despite the fact that they are not available in code (our typical issue), and that is causing application development teams to be dependent on us to deliver that 12 column width size. The app developers don't have a strong preference what the sizes are called... they will figure out the names. They really just need that size available to build the app to spec.
On the technical debt side, we need to update ALL of the card size names. This will be a bit of work on the PAL side, but the main issue is that it exposes our consumers to a considerable amount of risk. If we make this change, and those teams update PAL, their application will break completely because their code is targeting the existing sizes. There is no way for us to update their code automatically to reference the new sizes. Someone from each app team will need to manually go through and change "Medium" to "Medium-Regular", etc.  We could post a warning in the PAL React slack channel to give them a heads up, but that's the best we could do, and it would likely go unnoticed by a lot of impacted parties.  Even worse, the effort for a team like Tririga to upgrade their code, snapshots and automation might take a day or it might be huge... we can't tell how much pain we're inflicting, because we don't know how their code is structured.
So, we need to split out these two items into different deliveries.

Need to discuss with @davidicus how to get the new sized (E.g. Large 12 columns cards) as well as other combinations implemented and if we should add width prop and height prop to fulfill the width/height combinations.
@dianatran18 We still need  information on the dimensions of breakpoints for each card size.

Hi @dianatran18, can we get your input for the breakpoints that Jessie is asking for?

Let me know if this works for the 12 column size only.
@davidicus feel free to suggest a better name if these don't work.
SMALLTHICK: {
max: { w: 12, h: 1 },
xl: { w: 12, h: 1 },
lg: { w: 12, h: 1 },
md: { w: 8, h: 1 },
sm: { w: 8, h: 1 },
xs: { w: 4, h: 1 },
},
MEDIUMTHICK: {
max: { w: 12, h: 2 },
xl: { w: 12, h: 2 },
lg: { w: 12, h: 2 },
md: { w: 8, h: 2 },
sm: { w: 8, h: 2 },
xs: { w: 4, h: 2 },
},
LARGETHICK: {
max: { w: 12, h: 4 },
xl: { w: 12, h: 4 },
lg: { w: 12, h: 4 },
md: { w: 8, h: 4 },
sm: { w: 8, h: 4 },
xs: { w: 4, h: 4 },
},

Hi Diana,
Thanks for the feedback. For all the new sizes showed up in the picture, do we need breakpoints for each one of them? Or could we have breakpoints just for the specific width(4, 6, 8, 12, 16) and height(1, 2, 3, 4) rather than size names.
Does SMALLTHICK, MEDIUMTHICK, LARGETHICK mean SMALLWIDE, MEDIUMWIDE and LARGEWIDE in the picture?

The boxes highlighted in purple are the new 12 column sizes with the 3 heights. Those are the ones I listed out in the breakpoints above, and should be able to fit the needs @JordanWSmith15's team has.

As for the larger changes (adding additional sizes, updating the naming convention to the new structure), I think we'll need to break out that work separately. It will be super confusing to try and solve for both at once. @davidicus and I talked about potentially having a Card V2 with all of the updated names and sizes, and to control the width and the height separately, vs needing to control the widths and heights together with the current naming structure.


linear 1.20

linear-1.20.1 depended on by:

GPipe-2.0.1 (>=1.18 && < 1.20). Tobias Bexelius<EMAIL_ADDRESS>@tobbebex.
active-<IP_ADDRESS> (>=1.14 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
diagrams-contrib-<IP_ADDRESS> (>=1.11.3 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
diagrams-core-<IP_ADDRESS> (>=1.11.3 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
diagrams-haddock-<IP_ADDRESS> (>=1.10 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
diagrams-lib-<IP_ADDRESS> (>=1.11.3 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
force-layout-<IP_ADDRESS> (>=1.10 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
sdl2-2.0.0 (>=<IP_ADDRESS> && < 1.20). Gabríel Arthúr Pétursson<EMAIL_ADDRESS>@haskell-game
smoothie-<IP_ADDRESS> (>=1.16 && < 1.20). Dimitri Sabadie<EMAIL_ADDRESS>@phaazon

doctest-0.10.1 depended on by:

linear-1.20.1 (>=0.8 && < 0.10). Edward Kmett<EMAIL_ADDRESS>@ekmett

reflection-2.1 depended on by:

lens-4.12.3 (>=2 && < 2.1). Edward Kmett<EMAIL_ADDRESS>@ekmett

On my way writting the patch! :)

Done for smoothie.

Upper bounds needing to be relaxed:
doctest-0.10.1 depended on by:

linear-1.20.1 (>=0.8 && < 0.10). Edward Kmett<EMAIL_ADDRESS>@ekmett

linear-1.20.1 depended on by:

diagrams-haddock-<IP_ADDRESS> (>=1.10 && < 1.20). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth
sdl2-2.0.0 (>=<IP_ADDRESS> && < 1.20). Gabríel Arthúr Pétursson<EMAIL_ADDRESS>@haskell-game

Lower bounds needing to be relaxed, or wait until the upper bounds are fixed:
reflection-2.1 depended on by:

lens-4.12.3 (>=2 && < 2.1). Edward Kmett<EMAIL_ADDRESS>@ekmett
linear-<IP_ADDRESS> depended on by:
diagrams-lib-<IP_ADDRESS> (>=1.20.1 && < 1.21). Brent Yorgey<EMAIL_ADDRESS>@bergey @byorgey @fryguybob @jeffreyrosenbluth

The lower bound bump for diagrams-lib was quite deliberate, we would prefer to just wait for the upper bounds to catch up.  I have been slowly working my way through upper bound updates for diagrams packages, I should get to diagrams-haddock tomorrow.

Uploaded diagrams-haddock.

It seems that the following are all that remain

[ ] Release a new version of linear to hackage that works with doctest-0.10.* (already on github)
[ ] Release a new version of sdl2 to hackage that works with linear-1.20.* (already on github)
[ ] Upgrade a few other packages to work with lens-4.13.* (#831)

Things are starting to pile up on this, so I intend to remove sdl2 from the Nov 1 nightly and see if the rest works out.

Can I personally be notified about sdl2? I've released a new version now, but I don't get @haskell-game notifications.

What is missing to get linear-1.20 into stackage?

@ocharles you sure can! https://github.com/fpco/stackage/commit/a29841b105428321dc18f19b90d2457cf7337431
Thanks for that release. @phaazon it looks like nothing is missing now. I'll lift the constraints related to this issue; anticipate linear-1.20 in the next nightly build.


docs: Edits SR rules commands

Closes #
Verification Steps

Do x
Do y

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation change
[ ] Other (please specify)

Checklist

[ ] Documentation added for the feature
[ ] CI and all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

@rkpattnaik780 Thanks so much for your prompt and helpful review and approval :)
@smccarthy-ie Another one that is ready for you to peer review, thanks :)

Thanks @bredamc Looks great! Left a few comments for minor polishing :)


add proxy property

Add opportunity for running tests in browser with proxy.

Coverage decreased (-0.4%) to 76.759% when pulling 7aeab46a1dc0d1d5a680dc4e42dba35b33231b55 on middaymi:addProxyProperty into 6e40f30473624d08cfe1c55658a71b9db564ce12 on alfa-laboratory:master.


Add support for Scala 2.12

This updates some libraries for 2.12 support. One code change re: ListT which doesn't have withFilter. I didn't bump the version number.

Thanks!


[TEST] use arr branch of ctest

This PR test whether the arr branch of ctest breaks anything. It requires being a bit more explicit about how arrays are passed in C FFI.

@gnzlbg: no appropriate reviewer found, use r? to override


Fix "AVCaptureDeviceTypeExternal is deprecated for Continuity Cameras"

Fixes #859

Hello. CI failed

Hello. CI failed

Hello!
Thank you for taking a look.
It looks like CI is failing because of the old macOS 12 runner.
Github now has macOS 13 & macOS 14 runners, which should work with the new SDK - at least XCode 15 (according to https://developer.apple.com/support/xcode/)
https://github.com/actions/runner-images/blob/main/images/macos/macos-13-Readme.md
https://github.com/actions/runner-images/blob/main/images/macos/macos-14-Readme.md

We need to support old systems

We need to support old systems, and homebrew enforces it

Ok, in that case, since XCode 15 can't be installed on macOS 12, this PR will have to be postponed, or I can close it if you want.

You have to implement a fallback.


Highlight.js should be a dep

Using angular-highlightjs crashes without, so the package.json should list it as a dep.

Yeah, and I might also add angular as a dependency as well.

https://github.com/pc035860/angular-highlightjs/releases/tag/v0.6.0
New release with new npm dependencies published.
Closing the issue.


Update linux-support-ebpf.md

Updating troubleshooting section for eBPF on how to identify if eBPF is causing perf issues and then mitigate it accordingly

Closing this PR. Changes have been merged in https://github.com/MicrosoftDocs/microsoft-365-docs-pr/pull/23966.


fix/design-changes-to-footer

Description

matches https://www.notion.so/oaknationalacademy/Footer-Mobile-Footer-010ae9ef0d8f4a49bc04d0fa238bd348

It looks like every link is an external link now

:tada: This PR is included in version 1.14.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


updates misc visual styles for compliance tag dropdown. fixes z-index stacking issue that caused avatar metadata below to appear above field tag dropdown. fixes issue with containingPersonalData flag being null when user does not interact with toggle

Coverage remained the same at 27.636% when pulling 3b5d3ef3aa0ddf0bfcb6edc975c043a838957cc9 on theseyi:cosmetic-updates into 04a17f851f2be2794421d51b5e63012d878c5f7c on linkedin:master.

Codecov Report

Merging #1220 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #1220   +/-   ##
======================================
  Coverage    8.24%   8.24%
======================================
  Files          60      60
  Lines        2280    2280
  Branches      483     483
======================================
  Hits          188     188
  Misses       2092    2092

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04a17f8...3b5d3ef. Read the comment docs.


Setup Greenkeeper

It would be super nice to have Greenkeeper keeping things up to date here :)

Or renovate bot https://github.com/fhinkel/teeny-request/pull/30


Can't run Flutter web

Hi!
I am using 1.10.14. Somehow my Flutter App won't even build for Chrome. Building for MacOs works just fine.
Getting following error in AppLinksPluginWeb:
../../../../../.pub-cache/hosted/pub.dev/app_links-3.4.3/lib/src/app_links_web.dart:11:24: Error: Undefined name 'window'.
final _initialLink = window.location.href;
Is this my error or simply broken?
Cheers,
Linus
EDIT: Maybe a bug for the app_links team?

Have you edited that file? It should be available by the dart:html import in that file. But yeah that's more an issue from that package.

What flutter/dart version are you using? Please post the output of flutter doctor -v

Vincent was correct - idk how I deleted the line since Android Studio still asked me if I want to edit the file.
But it works now. Thank you! :)


Please put URL in Readme or code comment

I downloaded this a year or so ago and used it.  Some time later I wanted to look for an update, but the GitHub URL is nowhere I can find in the files themselves.  There are several ASP/JSON libraries online.  Please put the https://github.com/rcdmk/aspJSON URL in the comments at the head of jsonObject.class.asp , and/or the readme

Hi. Good idea.
I'll add this in the next releases.


Add ability to download unified diff

We already generate a unified diff for display with diff2html, so let's find a way to let users download the diff if they wanted to do something fancy like apply a patch file with git apply!

I haven't really found a clear use case for this, but am open to a PR if someone would like to contribute the functionality.


Adds stackoverflow and google links on debug mode

Links which point to StackOverflow search page or Google search page only when in debug mode.
Adds missing dependency from CONTRIBUTING.rst document.

Thanks for the patch, but I don't think this belongs in the debugger.


Run url-fetch perf tests against a fresh database each time

The subsequent runs of url-fetch on jenkins are way faster, and this
appears to be because commiting is much faster on subsequent runs. The
perf tests now use a new database each time.

jenkins: perf this

Current coverage is 87.50% (diff: 100%)

Diff Coverage
File Path

•••••••••• 100%
go/perf/suite/suite.go

No coverage report found for master at 4fd84d5.

Powered by Codecov. Last update 4fd84d5...476cec8

PTAL


Added PillarsJS microtaller

Added PillarsJS microtaller to the event description.

Allready updated. Thanks for your help @wchiquito
PS.: I've updated the workshop and saw your PR, see you the 14th of january


[chip-test] chip_plic_fatal_alert

Test point name
chip_plic_fatal_alert
Host side component
SystemVerilog
OpenTitanTool infrastructure implemented
None
Contact person
No response
Checklist
Please fill out this checklist as items are completed. Link to PRs and issues as appropriate.

[ ] Check if existing test covers most or all of this testpoint (if so, either extend said test to cover all points, or skip the next 3 checkboxes)
[ ] Device-side (C) component developed
[ ] Bazel build rules developed
[ ] Host-side component developed
[ ] HJSON test plan updated with test name (so it shows up in the dashboard)
[ ] Test added to dvsim nightly regression (and passing at time of checking)

Note that this test ("Verify that the fatal alert is fired from PLIC due to bus integrity violation.") seems to overlap with chip_sw_plic_alerts ("Verify alerts from PLIC due to both, TL intg and reg WE onehot check faults."), which is tracked in https://github.com/lowRISC/opentitan/issues/16835. In particular, alerts due to reg WE onehot check faults seem to be verified already since https://github.com/lowRISC/opentitan/pull/16845. This leaves verifying TL integrity errors, which this test is about.

Note that this test ("Verify that the fatal alert is fired from PLIC due to bus integrity violation.") seems to overlap with chip_sw_plic_alerts ("Verify alerts from PLIC due to both, TL intg and reg WE onehot check faults."), which is tracked in #16835. In particular, alerts due to reg WE onehot check faults seem to be verified already since #16845. This leaves verifying TL integrity errors, which this test is about.

@cindychip: I think the chip_sw_plic_alerts testpoint could be implemented by this test plus chip_sw_all_escalation_resets. WDYT?

Thanks @andreaskurt, I agree this should be part of the escalation resets, or at least can share the same test infra.

@msfschaffner to cross-reference test cases.

@cindychip can you close this once you added the SVA?

thanks Michael, closing it.


Update scalatest to 3.2.9

Updates org.scalatest:scalatest from 3.2.7 to 3.2.9.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

labels: library-update, semver-patch

Codecov Report

Merging #507 (e02d4cb) into main (65f9a5e) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #507   +/-   ##
=======================================
  Coverage   95.90%   95.90%
=======================================
  Files          15       15
  Lines         757      757
  Branches       44       44
=======================================
  Hits          726      726
  Misses         31       31

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65f9a5e...e02d4cb. Read the comment docs.


Added .css extension to compiled responsive CSS files

Not sure if this was an oversight in the Makefile or if it's intentional but the 2 compiled responsive CSS files don't have a ".css" extension.

Duplicate! Someone else beat me to it


Can't export data after patch

After patch dbtools-common.jar with SQLcl 23.4.0 cant export data query in sqlDeveloper <IP_ADDRESS>5

Yes, the export produces empty files with the patched db-common.jar. Thanks for letting us know.
Today the SQLDev team presented this roadmap for Oracle SQL Developer Extension for VSCode:

Custom Format Settings are not mentioned.
SQL Developer "Classic" will be end of life in 2026. However, SQL Developer "Classic" is de facto EOL, even if we can expect a bug-fix update here and there.
In other words, we have to stop using the custom format settings in SQL Developer "Classic" and wait until the Oracle SQL Developer Extension for VS Code supports custom format settings in a compatible way.

It seems like formatting might be just around the corner. But the "Advanced" section might take some time and especially input.


PAge break at a section

Hi there, I am facing an issue with the format. My section is doing a page break when the content becomes more than the space available on the page. Can't figure out where this happens in the preamble. Could you please help?

Thank you for your feedback! Are you using the latest version of the template? I've made several recent changes to improve the compatibility of the template with other packages (e.g., biblatex). If you can share your code (or an example), I can help take a look.

Yes, sorry for the mistake. Was using the previous version. Now its working fine. Thanks

Glad it works now =)


Remove Accept-Encoding header

We are using Heroku and we had similar issue mentioned here: https://github.com/waterlink/rack-reverse-proxy/issues/12.
The problem was that compression was applied twice: first time on proxied response and second time on original response. So I see two possible solutions: either decompress proxied response or do not send "Accept-Encoding" to proxy server. I used second solution, what do you think?

You probably want to add :preserve_encoding to @global_options to provide an explicit default value (true or false, what it should be, WDYT?).
Additionally, could you please rebase against upstream master and add this option to the README?
Looks like the build errored randomly on Rubinius (sometimes it does segfaults, don't know why TBH).

I have restarted the job for Rubinius, should work.

Hmm, no it does not look like it is random, rubinius seems broken to me.

Heh, even though it segfaulted on gem --version, travis still proceeded and test suite succeeded. That is weird.

LGTM
@maxilev Thanks!

@maxilev I have released 0.11.0 with your changes.

Nice :+1:


Next 15 support<EMAIL_ADDRESS>

This bumps swc_core to 0.106.3.
This is tested with Next 15.0.0

Hello, may I ask if this can be merged? Thank you very much.

Not sure why the "test publish" action is failing, as building does seem to work locally

Waiting for upgrade Next15 😄

Could not find this version (and previous as well) in the compatibility site, created the issue https://github.com/swc-project/website/issues/273

Yeah, I noticed the compatibility site not updating after a certain canary version.
I ended up manually checking the package.json for Next.

I reverted rust toolchain, have no idea why it was bumped. It seems it builds with existing version without issue.

swc_core at some point bumped the rust toolchain, so i did as well.
This according to the https://github.com/lingui/swc-plugin/blob/main/CONTRIBUTING.md#rust-version documentation

SWC uses nightlies internally, but it does seem that 2024-07-21 and 1.80 is pretty much the same release
https://github.com/swc-project/swc/pull/9319

Available in 4.1.0.


PhoneCallOriginDataRequestTriggerDetails what is the trigger for this?

I understand how PhoneCallOriginDataRequestTriggerDetails id used in the background but I cannot figure out what the trigger is for this class. I tried PhoneCallOriginDataRequestTrigger but that does not work.
Any help is greatly appreciated.....

new PhoneTrigger(PhoneTriggerType.CallOriginDataRequested) is the trigger.

oldnewthing - Thank you. I am amazed by your detailed knowledge of these APIs.

ITNOA
Hi, what is meaning of CallOriginDataRequest and when it trigger?

See the CallerID sample.


Hot Reload

How to enable hot reload for this app?
I can't find a proper way to enable hot reload for it according to Avalonia document.

Avalonia has no hot reload feature.
However there are two experimental open source projects that try to do it :
https://github.com/AvaloniaUI/Live.Avalonia
https://github.com/Kir-Antipov/HotAvalonia
Avalonia team is thinking about developing this feature for a "pro" paid subscription (https://github.com/AvaloniaUI/Avalonia/discussions/14097)


Change Zendesk4ProcessExecution.DownloadParams visibility to public

Fixes #387.

Coverage remained the same at 82.601% when pulling a50ebea1a6d7f283e67d2868da75d1cecdefddc6 on peter-plochan:ppl-downloadparams into d485c49aaa9f8339324f900876d515d522e4929f on martiner:master.


14 addresses found first in Issue 265

@tschubotz  There are 14 safe wallets found in issue https://github.com/safe-global/safe-user-allocation-reports/issues/265 before https://github.com/safe-global/safe-user-allocation-reports/issues/294. The author of the issue https://github.com/safe-global/safe-user-allocation-reports/issues/294 also agrees with me . Could you please check the edit histories to confirm it?
0xe6e94ba16E7c752424Cff7aFA0c87602Be3e3Eec
0x705cCA342b7a36C46442C06E7117D33Be661d711
0xD66292d9EE2ddF4772dc94Fe3d2791c38ED7605F
0xF41E53A089854F71eEEA2934967C759658d8560A
0x35345E852C4b70883cB0710945Bf63BC32c01369
0x5cF25A39b7015a1F49208E88e7c45a0ad5921861
0x5Dfa97d1d1746E19Bc5FbB28213C23EB33da498e
0x72002988E532ea1cAB05Dc2AF0F730860e8Aa5C2
0xAc2caB720ce08becCb69FfE5ec9d5aAC3CDc7f3C
0x93Bb9aa2F46f3775d0ff0a916fFac650C574B96b
0xcf0574082B0E548eA57dBD4785863094f856dA2c
0xDe77b3DAA28714E8a21Ad1AE68d93BF65D7E4d34
0x8d1534aAbe5296EbBab5158d4CdfAD6723E6Ec0A
0x4429fb5D1282170c3C644bd4244700F272a71Fc5

Thanks, fixed.


Bug: Need translation values not visible after upgrade

Hi,
First, I would like to thank you for providing this project, it has been very helpful for us to keep track of the translations to the various languages. I do have a small issue I just ran into and would appreciate any help that you can provide.
I am attempting to upgrade the mojito installation from v0.83 to v0.105 and have a problem that after the upgrade all repositories are listed as Done.
Before the upgrade "Need Translation" column in the Repositories overview listed how many translations are still needed for a repository (for example, one repository listed "139 ( 561 words )"). After the upgrade, the values are not listed and all the repositories are marked as "Done".
If I navigate to a repository and change a translation (for example, if I add a space to an existing translation or if I enter a new translation) then the value for the "Need translation" reappears for that repository (and is correct).
The problem is that I do not wish to do any updates on the translations. I am only maintaining the installation and not actually working on the translations themselves, so I would prefer to not do any modifications to the data.
Thank you in advance for your time and any assistance you can provide.
Prerok

Hello Prerok,
Thank you for using Mojito. The problem you saw may be from the changes in
how we keep track of repository stats.
Jean - is there an option to force repository stats to be re-computed?
Jee
On Fri, Jun 19, 2020 at 5:54 AM digi-prerok<EMAIL_ADDRESS>wrote:

Hi,
First, I would like to thank you for providing this project, it has been
very helpful for us to keep track of the translations to the various
languages. I do have a small issue I just ran into and would appreciate any
help that you can provide.
I am attempting to upgrade the mojito installation from v0.83 to v0.105
and have a problem that after the upgrade all repositories are listed as
Done.
Before the upgrade "Need Translation" column in the Repositories overview
listed how many translations are still needed for a repository (for
example, one repository listed "139 ( 561 words )"). After the upgrade, the
values are not listed and all the repositories are marked as "Done".
If I navigate to a repository and change a translation (for example, if I
add a space to an existing translation or if I enter a new translation)
then the value for the "Need translation" reappears for that repository
(and is correct).
The problem is that I do not wish to do any updates on the translations. I
am only maintaining the installation and not actually working on the
translations themselves, so I would prefer to not do any modifications to
the data.
Thank you in advance for your time and any assistance you can provide.
Prerok
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/box/mojito/issues/594, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEEYVBA7MYQ6RYPSLESEULTRXNNYPANCNFSM4OCWOOJQ
.

@jeeyi we don't have a command to re-trigger statistique computation manually.
@digi-prerok the next time you push content to the repositories it should also recompute them. I don't know if you do that on a regular basis?
How many repositories do you have?

Jean, Prerok had mentioned that he has not had new strings for a while and does not want to change the translations. Would it still cause a recomputation if he pushes the same source file as before? (ie. there will be no changes, but a push nonetheless causing a recomputation?)

re-pushing the same file won't re-trigger computation.
Actually we have a way, through config + deployment to enable periodic computation of stats using the l10n.repository-statistics.scheduler.cron property

Thanks, @aurambaj , works like a charm!
After enabling the recomputation of statistics they reappeared once the cron job activated. Thank you all, @aurambaj , @ehoogerbeets and @jeeyi for your fast response and help!
Wish you all the best in the future.


Error while playing GTNH version 2.3.3 with this mod

Here is the crash report, thanks
crash-2022-12-01_23.27.38-client.txt

Incidentally, I'm just an ordinary mc player, so I have no clue about the cause of the problem, I'm sorry, but I'm willing to provide you with more information, thank you.

Incidentally, I found that I had downloaded version 0.1.8 from the release page, but it was recognized as version 0.1.4 in mmc

I'm not sure, because I chose to download the latest GTNH version 2.3.3, but the NEI it provides is exactly version 2.3.7, am I misunderstanding something

Maybe you can lower the version of nei utilities, I'm not sure, I can only make sure that 0.1.8 supports 2.3.14 and later versions.

Maybe you can lower the version of nei utilities, I'm not sure, I can only make sure that 0.1.8 supports 2.3.14 and later versions.

I encountered the same problem. I used GTNH stable Edition, <IP_ADDRESS>.
The nei version is 2.3.7-GTNH, with frequent crash.

Now I use 0.1.7 and it works well

Now I use 0.1.7 and it works well

感谢，我去下载一下。


fix swiftlint warnings

use swift constructor
use struct extension properties
do NOT repeat let statement in conditional binding
separate methods, to avoid Cyclomatic Complexity warning

@fumitoito thanks!