Fix error on parse emits if connection is already closed, fixes #132

@bwoebi @trowski Please review, no idea what I'm doing.

There should be no further update to bodyPromisor after failure. The code causing it being updated/resolved should be fixed.

I believe this would be as simple as adding if ($client->isDead) { return; } to onParsedEntityPart().

I've realized @kelunik solution is the correct one, but not applied to everything; there's an edge case where bodyPromisors being closed in onReadable() may also trigger it (in combination with the size upgrade mechanism).
@trowski That'd work just for CLOSED_RD mode and also on EntityResult. And will have unexpected effects if data is closed, but already completely transmitted, but still in buffer of parser due to size limits and these then being raised.


CasADi performance bottlenecks overview

Issue to add any minimum working examples related to improving the casadi solver

For very simple models, it takes much longer to evaluate the outputs than it does to solve the model
import pybamm
import numpy as np

class Decay(pybamm.BaseModel):
    def __init__(self):
        super().__init__()
        x = pybamm.Variable("x")
        self.rhs = {x: -x}
        self.initial_conditions = {x: 1}
        self.variables = {"x": x}

model = Decay()
solver = pybamm.CasadiSolver()
t_data = np.linspace(0, 10, 1000)
# profile this line:
solution = solver.solve(model, t_data)["x"]
# currently about 10% solver / 90% evaluate

SPMe with differential surface form and power mode fails to converge
import pybamm

pybamm.set_logging_level("INFO")
model = pybamm.lithium_ion.SPMe(
    {"surface form": "differential", "operating mode": "power"}
)
parameter_values = pybamm.ParameterValues("Chen2020")
parameter_values.update({"Power function [W]": 4}, check_already_exists=False)
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve([0, 3600])

https://github.com/pybamm-team/PyBaMM/issues/2173 (it now fails instead of hanging indefinitely)

An example that takes a long time because it struggles near an event (sharp voltage drop-off)
import pybamm

pybamm.set_logging_level("INFO")

model = pybamm.lithium_ion.DFN()
parameter_values = pybamm.ParameterValues("Chen2020")
parameter_values["Positive electrode active material volume fraction"] = 0.1
sim = pybamm.Simulation(model, parameter_values=parameter_values)
sim.solve([0, 3600])
sim.plot(["Voltage [V]"])

Linking #1996 , we probably don't want to use vertcat at all, instead store the ys separately

Linking #1482 which only seems to happen with the casadi solver

https://github.com/pybamm-team/PyBaMM/discussions/3943

#3960


Reliably slo report crashes when manifest is run from the server

Describe the bug
I have a manifest that was created by reliably slo init, and if I run reliably slo report using that manifest when it is stored on the Reliably SAAS it crashed with the error:
⡿ panic: interface conversion: interface {} is map[string]interface {}, not manifest.LatencyCriteria
The manifest concerned is:
services:
- name: Service GTF
  service-levels:
  - name: 95% of requests successful over last 1 hour
    type: availability
    slo: 95
    sli:
    - id: arn:aws:apigateway:eu-west-3:912823331559:/apis/3ix4qm7v4d
      provider: aws
    - id: arn:aws:apigateway:eu-west-3:912823331559:/apis/3ix4qm7v4d
      provider: aws
    window: PT1H
  - name: 98% of requests faster than 350ms over last 1 day
    type: latency
    criteria:
      threshold: 350ms
    slo: 98
    sli:
    - id: arn:aws:apigateway:eu-west-3:912823331559:/apis/3ix4qm7v4d
      provider: aws
    window: PT24H

If you run with this manifest locally you do not get the same error.
To Reproduce
Create a manifest with a reliably slo init add an availability so and a latency slo as shown in the manifest above. Run the slo report ensuring you use the version on the server.
Expected behavior
A manifest that is generated from an slo init should be able to produce a report
Additional context
If you run aa local copy of the manifest it seems to run ok

@daidokoro is investigating

The bug is caused by different unmarshalling methods being used for Manifest files vs those pulled from the API.
The API uses the json.Unmarsal and the file Load uses yaml.Unmarhal
Due to subtle differences in how these packages work, when unmarshalling the LatencyCriteria property of the manifest we get:
json.Unmarshal: when pulling from the API
interface {}(map[string]interface {}) [
        "threshold": "350ms",
]

yaml.Unmarshal: when reading a local file
interface {}(github.com/reliablyhq/cli/core/manifest.LatencyCriteria) {
        Threshold: github.com/reliablyhq/cli/core.Duration {Duration: 350000000},}

As the report generator expects the later, whenever we generate report while pulling from the API with a LatencyCriteria defined, we get a panic:
goroutine 1 [running]:
github.com/reliablyhq/cli/core/report.FromManifest(0xc00000e390, 0xc000146840, 0x0, 0x0)
        /Users/daidokoro/Projects/reliably/cli/core/report/generate.go:86 +0x1185
github.com/reliablyhq/cli/cmd/reliably/slo/report.reportRun(0xc000010320, 0x0, 0x0)
        /Users/daidokoro/Projects/reliably/cli/cmd/reliably/slo/report/cmd.go:90 +0x145
github.com/reliablyhq/cli/cmd/reliably/slo/report.NewCommand.func2(0xc0001d6580, 0xc0000389e0, 0x0, 0x1, 0x0, 0x0)
        /Users/daidokoro/Projects/reliably/cli/cmd/reliably/slo/report/cmd.go:59 +0x2a
github.com/spf13/cobra.(*Command).execute(0xc0001d6580, 0xc0000389d0, 0x1, 0x1, 0xc0001d6580, 0xc0000389d0)
        /Users/daidokoro/Go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:850 +0x472
github.com/spf13/cobra.(*Command).ExecuteC(0xc000161340, 0x5, 0x0, 0x0)
        /Users/daidokoro/Go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:958 +0x375
github.com/spf13/cobra.(*Command).Execute(...)
        /Users/daidokoro/Go/pkg/mod/github.com/spf13/cobra@v1.1.1/command.go:895
github.com/reliablyhq/cli/cmd/reliably.Execute()
        /Users/daidokoro/Projects/reliably/cli/cmd/reliably/root.go:124 +0xe5
main.main()
        /Users/daidokoro/Projects/reliably/cli/main.go:21 +0x25

Further checks indicate that the above was due to there only being a Custom Unmarshaller for YAML defined in core/manifest/types.go and not JSON.


the rostopic  "aligned_depth" not accurate as topic depth/image_raw

I use sr300 and need to aligned the depth to color, the accuracy of topic aligned_depth_to_color which realsense2_camer provide is much lower than the topic depth/image_raw,anybody know how to fix this?
thanks

Is there an easy way to aligned depth/image_raw to color/image_raw?

Hello @GITSHOHOKU
Perhaps this issue is same as the one the PR #367 is fixing.
The PR is not accepted yet currently, so you can do the same modification to see if it helps you.
Thanks : )


Fix win32 stopping projects and "crash" status

fixes https://github.com/flowforge/flowforge/issues/530
While setting up the FF developer environment and testing on windows box, issues around project status when stopping / starting projects were discovered.
This PR fixes these issues...

Project cannot be stopped
Project status "crashed"
Launching node instead of the batch file (so the correct PID is obtained)

@hardillb please note, this has been tested on Windows only.


Miscellaneous minor improvements

Please have a look at the individual commit messages for the details.

Merging despite the unrelated failure which hopefully get fixed by https://github.com/oss-review-toolkit/ort/pull/4526.


[ISSUE #901]🔥Implement Produer send single message other methods🚀

Which Issue(s) This PR Fixes(Closes)

Fixes #901
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit(AI) will review your code first🔥


Unable to run rules-configmap-reloader in docker 18.9.2  to 10Mi limit

What did you do?
Upgraded  dokcer version 18.9.2
What did you expect to see?
Pods continue running
What did you see instead? Under which circumstances?
Message:      OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:390: setting cgroup config for procHooks process caused \\\"failed to write 10485760 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/burstable/pod39529789-35a2-11e9-98c7-005056bd98cb/564ac56ec41f355be129131d9c0599b3de38d76068688abb9538c8456e5bc7cb/memory.limit_in_bytes: device or resource busy\\\"\"": unknown

Environment

Prometheus Operator version:
0.29

Kubernetes version information:
v12.5

hi
I look  https://github.com/coreos/prometheus-operator/releases/tag/v0.29.0
I konw docker 18.9.2 unknown 10Mi  memory.limit   I konw memory.limit  change 100Mi is OK
I update 0.29 ,but statefulset.apps.alertmanager-main statefulset.apps.prometheus-k8s is no good.
I  don't find statefulset.prometheus-k8s and statefulset.alertmanager-main memory.limit,
How to change the configuration. i don't find configuration.....
thanks.

    State:          Waiting
      Message:      OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:390: setting cgroup config for procHooks process caused \\\"failed to write 10485760 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/burstable/pod39529789-35a2-11e9-98c7-005056bd98cb/9856bf0c86a0b07d86ad768429fa2a571a9eaf930b06a48f826870addd50c886/memory.limit_in_bytes: device or resource busy\\\"\"": unknown
    Ready:          False
    Restart Count:  23
    Limits:
      cpu:     50m
      memory:  10Mi
    Requests:
      cpu:        50m
      memory:     10Mi

@gouki777 This issue looks to be the same as yours: https://github.com/coreos/prometheus-operator/issues/2409

i change alertmanager-main 100Mi,but no good. alertmanager-main auto change 10Mi....

kubectl edit statefulset.apps -n monitoring alertmanager-main
        image: quay.io/coreos/configmap-reload:v0.0.1
        imagePullPolicy: IfNotPresent
        name: config-reloader
        resources:
          limits:
            cpu: 50m
            memory: 10Mi

Does the Prometheus Operator log anything? It sounds to me like something is going wrong with rolling out the updated StatefulSets.

my git clone https://github.com/coreos/prometheus-operator.git (0.29) and docker version 18.9.2
alertmanager-main-0 and  prometheus-k8s-0  wrong.
failed to write 10485760 to memory.limit_in_bytes: write...

# pwd
/root/prometheus-operator/contrib/kube-prometheus/manifests
# kubeclet apply -f .
.......
# kubectl get po -n monitoring
NAME                                   READY   STATUS              RESTARTS   AGE
alertmanager-main-0                    0/2     ContainerCreating   0          45s
prometheus-adapter-b7d894c9c-s5kts     1/1     Running             0          46s
prometheus-k8s-0                       2/3     CrashLoopBackOff    3          44s
prometheus-k8s-1                       2/3     CrashLoopBackOff    3          44s
prometheus-operator-566b5d5c85-jfsv8   1/1     Running             0          62s

# kubectl describe po -n monitoring prometheus-k8s-0
Name:                      prometheus-k8s-0
Namespace:                 monitoring
    State:          Terminated
      Reason:       Error
      Exit Code:    2
      Started:      Thu, 21 Feb 2019 22:21:11 +0800
      Finished:     Thu, 21 Feb 2019 22:26:09 +0800
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     50m
      memory:  50Mi
    Requests:
      cpu:     50m
      memory:  50Mi
    Environment:
      POD_NAME:  prometheus-k8s-0 (v1:metadata.name)
    Mounts:
      /etc/prometheus/config from config (rw)
      /etc/prometheus/config_out from config-out (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from prometheus-k8s-token-plk9g (ro)
  rules-configmap-reloader:
    Container ID:  docker://8068194a57bbfb23865739edef952a057b43e3f9308f41b8e816fec7d9d2b6e1
    Image:         quay.io/coreos/configmap-reload:v0.0.1
    Image ID:      docker-pullable://quay.io/coreos/configmap-reload@sha256:e2fd60ff0ae4500a75b80ebaa30e0e7deba9ad107833e8ca53f0047c42c5a057
    Port:
    Host Port:
    Args:
      --webhook-url=http://localhost:9090/-/reload
      --volume-dir=/etc/prometheus/rules/prometheus-k8s-rulefiles-0
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       ContainerCannotRun
      Message:      OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:390: setting cgroup config for procHooks process caused \\\"failed to write 10485760 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/burstable/podeef0512c-35e3-11e9-98c7-005056bd98cb/8068194a57bbfb23865739edef952a057b43e3f9308f41b8e816fec7d9d2b6e1/memory.limit_in_bytes: device or resource busy\\\"\"": unknown
      Exit Code:    128
      Started:      Thu, 21 Feb 2019 22:24:02 +0800
      Finished:     Thu, 21 Feb 2019 22:24:02 +0800
    Ready:          False
    Restart Count:  5
    Limits:
      cpu:     25m
      memory:  10Mi
    Requests:
      cpu:        25m
      memory:     10Mi
    Environment:
    Mounts:
      /etc/prometheus/rules/prometheus-k8s-rulefiles-0 from prometheus-k8s-rulefiles-0 (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from prometheus-k8s-token-plk9g (ro)
Events:
  Type     Reason     Age                    From                      Message
  ----     ------     ----                   ----                      -------
  Normal   Scheduled  5m2s                   default-scheduler         Successfully assigned monitoring/prometheus-k8s-0 to k8s-n2-107v8-yz
  Normal   Pulled     5m1s                   kubelet, k8s-n2-107v8-yz  Container image "quay.io/coreos/prometheus-config-reloader:v0.28.0" already present on machine
  Normal   Created    5m1s                   kubelet, k8s-n2-107v8-yz  Created container
  Normal   Pulled     5m (x2 over 5m1s)      kubelet, k8s-n2-107v8-yz  Container image "quay.io/prometheus/prometheus:v2.5.0" already present on machine
  Normal   Created    5m (x2 over 5m1s)      kubelet, k8s-n2-107v8-yz  Created container
  Normal   Started    5m                     kubelet, k8s-n2-107v8-yz  Started container
  Normal   Started    4m59s (x2 over 5m1s)   kubelet, k8s-n2-107v8-yz  Started container
  Warning  BackOff    4m35s (x4 over 4m58s)  kubelet, k8s-n2-107v8-yz  Back-off restarting failed container
  Normal   Pulled     4m21s (x4 over 5m)     kubelet, k8s-n2-107v8-yz  Container image "quay.io/coreos/configmap-reload:v0.0.1" already present on machine
  Normal   Created    4m21s (x4 over 5m)     kubelet, k8s-n2-107v8-yz  Created container
  Warning  Failed     4m21s (x4 over 5m)     kubelet, k8s-n2-107v8-yz  Error: failed to start container "rules-configmap-reloader": Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:390: setting cgroup config for procHooks process caused \\\"failed to write 10485760 to memory.limit_in_bytes: write /sys/fs/cgroup/memory/kubepods/burstable/podeef0512c-35e3-11e9-98c7-005056bd98cb/rules-configmap-reloader/memory.limit_in_bytes: device or resource busy\\\"\"": unknown

kube-prometheus is completely unversioned and the v0.29.0 tag only relates to the prometheus operator. You will need to use current master of this repo for v0.29.0 of the prometheus operator to be in kube-prometheus. We intend to move kube-prometheus to a separate repository to avoid confusion like this.

thanks. I konw.
I change kube-prometheus 0prometheus-operator-deployment.yaml . -> v0.28.0  to v0.29.0
pods continue running
      containers:
      - args:
        - --kubelet-service=kube-system/kubelet
        - --logtostderr=true
        - --config-reloader-image=quay.io/coreos/configmap-reload:v0.0.1
        - --prometheus-config-reloader=quay.io/coreos/prometheus-config-reloader:v0.28.0
        image: quay.io/coreos/prometheus-operator:v0.28.0


added message for no search results

Description
When search does not match any groomers there will be a message displayed to announce no results found
Type

[ ] This is a bugfix.
[ ] This is a new feature.
[ ] This is part of a feature.

Organization

[ ] Have you linked this pull request to a Trello card?
[ ] Have you named the branch in the format of feature/describe_feature_or_change OR bug/describe_bug_this_is_fixing

Review

[ ] Is this a work in progress?
[ ] Is this ready to be reviewed?
[ ] Have you added two reviewers to this pull request?

 give a useful message to user if no search results


Responsive header

What problem does this feature solve?
Having a header with the same behaviour of sider with some size breakpoint like the sider...
What does the proposed API look like?
Not responsive !

https://ng.ant.design/docs/faq/zh
#有些特性为什么不会被支持
ng-zorro-antd 是 Angular 版本 Ant Design 的实现，这意味着只有 Ant Design 支持的交互、功能 才会被 ng-zorro-antd 实现。

No english ?

we only support the features designed by ant design


Read audio file tags

Can get title, album, album art, etc. To improve audio preview

https://ordinalsbitcoin.com/inscription/42c2aeb3bb16845fde392d8ec5b976af880e8636dfc356cd8f9b12d90233c3e3i0
Here's an example I uploaded a few days ago, if you download this file and preview it on Mac, or iTunes etc. you should see the embedded album art and artist field etc.


Lime-133, Issue 169: Collateral can be deposited in a finished pool

Description
Stacked pull request on #203
The depositCollateral function doesn't check the status of the pool so collateral can be deposited in a finished loan. This can happen by mistake and all funds will be lost.
https://github.com/code-423n4/2021-12-sublime/blob/9df1b7c4247f8631647c7627a8da9bdc16db8b11/contracts/Pool/Pool.sol#L207
Integrations Checklist

[ ]  Have any function signatures changed? If yes, outline below.
[ ]  Have any features changed or been added? If yes, outline below.
[ ]  Have any events changed or been added? If yes, outline below.
[ ]  Has all documentation been updated?

Changelog

Checking loan status before depositing collateral(Issue 169: Collateral can be deposited in a finished pool
Ref: https://github.com/code-423n4/2021-12-sublime-findings/issues/169)

Event Signature Changes
Function Signature Changes
Features
Events

Codecov Report

Merging #204 (20d2bea) into lime-81 (f34145d) will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##           lime-81     #204      +/-   ##
===========================================
- Coverage    15.95%   15.94%   -0.01%
===========================================
  Files           16       16
  Lines         1736     1737       +1
  Branches       320      321       +1
===========================================
  Hits           277      277
- Misses        1459     1460       +1

Impacted Files
Coverage Δ

contracts/Pool/Pool.sol
0.00% <0.00%> (ø)

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 f34145d...20d2bea. Read the comment docs.


[PMD+PDS] Create a Helm Chart

Today, Kubernetes is one of the core technologies allowing DevOps team to deploy scalable solutions to a cluster of nodes in the cloud.
Many free and open source software (FOSS) security tools are designed as command line (CLI) tools, that is totally fine. However, to make them cluster ready SecHub developed the Product Delegation Server (PDS). PDS can turn any CLI tool into a cluster ready tool.
By creating a Helm Chart for the PMD+PDS solution it is possible to allow anyone to easily run the PMD+PDS in a Kubernetes cluster. By using SecHub and the PMD+PDS Helm Chart in combination, one can run many scans in parallel.
Creating a Helm Chart is not difficult. Helm Charts are a number of configuration files bundled together in a folder. The templates in a Helm folder are nothing more than normal Kubernetes files. The only difference is, that it is possible to use Go-Templating inside of them, which makes them very flexible and powerful.
In addition, Helm requires some additional Metadata files.
To get started have a look at our Helm Chart for GoSec+PDS: https://github.com/mercedes-benz/sechub/tree/develop/sechub-pds-solutions/gosec/helm/pds-gosec. This chart can be used as blueprint, by simply copying it and adjusting the parameters to PMD+PDS.
To get a better understanding of Helm Charts and how to develop them have a look at the many resources Helm already provides:

Quickstart Guide
Chart Template Guide
How-to Guides

Keep in mind this step can be difficult, as running a Kubernetes cluster locally is quite resource intensive. There are several projects trying to reduce the effort:

K3S
kind

The previous steps so far:

Create a single PMD+PDS instance #1353
Create mocks PMD+PDS #1358
Multiple PMD+PDS instances #1359

This is a sub issue of #764

@Jeeppler
please review my PR.

@Jeeppler any problems with my PR ?

@zigfridus sorry, for not getting this done faster. I will try to get this PR done as quick as possible. I reviewed it and it looks fine. Additionally, I want to try if it works in a K8s cluster. Give me a little bit of time.


[Bug] Keep screen on does not work for android

Godot version:
3.0.2 (stable from AUR)
OS/device including version:
Arch linux and android 7.1 cancro (and some other devices)
Issue description:
Even though I checked in settings "Display -> Window -> Keep screen on" and selected the permission "wake lock", the app does not make use of the android permission "keep awake". So the device fells a sleep.
Steps to reproduce:

Create an empty project
Create node, save it and select as main node.
Check "Display -> Window -> Keep screen on"
Create Export scheme for Android with permission "wake lock" checked

Minimal reproduction project:
See: https://github.com/braniii/Keep_screen_on
And thanks for this great engine!

I believe this setting is for Godot editor itself, not the exported app.

@Zireael07
Oh, but then it is confusing that it is part of the "project settings" and not of the "editor settings". Can you tell me how to make use of the android permission "wake lock". Do I need to call a function?

Did this get resolved? I'm struggling to keep the screen on in my exported app having used the settings I had thought were correct.

Nope. It will be fixed with 3.1. If it's urgent you need to use 2.*

No worries, thanks for your help!

This seems to be working on master, is there any chance to get the fix cherry picked on 3.0?

The fix is #20192, it's marked for cherry-picking. I'll add it for 3.0.7.


Make tests independent from (often changing) data

https://github.com/YoungVision-eV/website/pull/52#issuecomment-1946339365

In general we should think of a testing strategy so we don't depend on things:

editable/changing data (dates, pictures, events, ...)
current date

Also very relevant with #38 as we expect our posts to change every few days. I think I'll use the mask option to hide them for now. But this means we won't be able to verify the images are actually shown :(

See these Vercel environment variables: https://vercel.com/docs/projects/environment-variables/system-environment-variables
Perhaps using VERCEL_ENV === preview could work for the github actions.

We'll probably need something like this to test that calendar and other time sensitive data
https://github.com/vesln/timekeeper

Also of interest for playwright: https://github.com/microsoft/playwright/issues/6347#issuecomment-1085850728

[ ] events
[ ] instagram posts
[ ] testamonials

[x]  events

[ ]  instagram posts

[ ]  testamonials

Is that all. We have donations.ts and exercises.ts, but these are not really often changing data, are they?

I think you're right. If we see that we edit those we can change it then.

@Han2-Ro I've had to revert your PR #80 because it caused the main branch to fail. See #89
We probably shouldn't run the tests against the vercel built version anymore and build the website in Github actions for the tests.
Remove the PLAYWRIGHT_TEST_BASE_URL variable and run the workflow on: [pull_request, merge_queue]
https://github.com/YoungVision-eV/website/blob/b3e36d2d8a504c80e902c2274322d94028d30087/.github/workflows/playwright.yml#L29

One drawback I've just noticed: We can't test if our links in production are valid anymore :(
Perhaps in the future we should run some basic tests against production deployments as well?
There is also the possibility of replacing the changing elements with stylepath for example.


Last stable release (0.14.3) fails to build kernel module with Linux 6.8.

Last stable release (0.14.3) fails to build kernel module with Linux 6.8.
error: implicit declaration of function ‘strlcpy’
Possibly fixed with https://github.com/falcosecurity/libs/commit/350208fac72a72d5e95dca0363ec52b018d40d84 and https://github.com/falcosecurity/libs/commit/18c33257e962dc17e189735756a4d95358226e91
Unfortunately it's not trivial to cherry-pick the fixes (there are 187 commits since last release) so I wonder when the next stable release is planned?
Or maybe someone can provide a list of commits that can be backported?
Also, CheckSymbolExists in libscap.cmake falsely detects existence of STRL* in string.h which are disable by a macro __USE_MISC for Linux systems.
include(CheckSymbolExists)
check_symbol_exists(strlcpy "string.h" HAVE_STRLCPY)
check_symbol_exists(strlcat "string.h" HAVE_STRLCAT)

Background:
Ubuntu 24.04 is almost in Beta and they already moved to Linux 6.8.
Ubuntu and and Debian still use 0.14.1 and need to be "persuaded" to update to next release but 0.14.3 is still not enough for newer Kernels.
Below is the build log:
DKMS make.log for scap-0.14.3 for kernel 6.8.0-11-generic (x86_64)
Fri Mar  8 12:45:16 PM MST 2024
make: Entering directory '/usr/src/linux-headers-6.8.0-11-generic'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-13ubuntu1) 13.2.0
  You are using:           gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0
  CC [M]  /var/lib/dkms/scap/0.14.3/build/main.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/dynamic_params_table.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/fillers_table.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/flags_table.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/ppm_events.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/ppm_fillers.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/event_table.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/syscall_table64.o
  CC [M]  /var/lib/dkms/scap/0.14.3/build/ppm_cputime.o
/var/lib/dkms/scap/0.14.3/build/ppm_cputime.c:353:10: warning: no previous prototype for ‘nsec_to_clock_t’ [-Wmissing-prototypes]
  353 | uint64_t nsec_to_clock_t(uint64_t x)
      |          ^~~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/scap/0.14.3/build/ppm_tp.o
/var/lib/dkms/scap/0.14.3/build/main.c:2838:5: warning: no previous prototype for ‘scap_init’ [-Wmissing-prototypes]
 2838 | int scap_init(void)
      |     ^~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/main.c:3001:6: warning: no previous prototype for ‘scap_exit’ [-Wmissing-prototypes]
 3001 | void scap_exit(void)
      |      ^~~~~~~~~
  CC [M]  /var/lib/dkms/scap/0.14.3/build/syscall_ia32_64_map.o
/var/lib/dkms/scap/0.14.3/build/ppm_events.c: In function ‘val_to_ring’:
/var/lib/dkms/scap/0.14.3/build/ppm_events.c:652:36: error: implicit declaration of function ‘strlcpy’; did you mean ‘strscpy’? [-Werror=implicit-function-declaration]
  652 |                         len = (int)strlcpy(args->buffer + args->arg_data_offset,
      |                                    ^~~~~~~
      |                                    strscpy
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:509:14: warning: no previous prototype for ‘ppm_get_mm_exe_file’ [-Wmissing-prototypes]
  509 | struct file *ppm_get_mm_exe_file(struct mm_struct *mm)
      |              ^~~~~~~~~~~~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:550:15: warning: no previous prototype for ‘ppm_get_mm_counter’ [-Wmissing-prototypes]
  550 | unsigned long ppm_get_mm_counter(struct mm_struct *mm, int member)
      |               ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:728:5: warning: no previous prototype for ‘accumulate_argv_or_env’ [-Wmissing-prototypes]
  728 | int accumulate_argv_or_env(const char __user * __user *argv,
      |     ^~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:874:6: warning: no previous prototype for ‘ppm_is_upper_layer’ [-Wmissing-prototypes]
  874 | bool ppm_is_upper_layer(struct file *exe_file){
      |      ^~~~~~~~~~~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:2261:5: warning: no previous prototype for ‘f_sys_send_e_common’ [-Wmissing-prototypes]
 2261 | int f_sys_send_e_common(struct event_filler_arguments *args, int *fd)
      |     ^~~~~~~~~~~~~~~~~~~
/var/lib/dkms/scap/0.14.3/build/ppm_fillers.c:2397:5: warning: no previous prototype for ‘f_sys_recv_x_common’ [-Wmissing-prototypes]
 2397 | int f_sys_recv_x_common(struct event_filler_arguments *args, int64_t *retval)
      |     ^~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:243: /var/lib/dkms/scap/0.14.3/build/ppm_events.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [/usr/src/linux-headers-6.8.0-11-generic/Makefile:1926: /var/lib/dkms/scap/0.14.3/build] Error 2
make: *** [Makefile:240: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.8.0-11-generic'

Please check out our build badges in https://github.com/falcosecurity/libs -> 6.8-rc7 is currently red. We usually wait until a kernel officially gets out of rc to avoid a feature being reverted again, which has happened in the past. CC @FedeDP.

Hi! Kernel 6.8 is already fixed since a couple of weeks! CI check is red because we have a different bug(related to driverkit) in libs master that I fixed this morning, tomorrow will be green!
About the next release, it is scheduled somewhere during the next week!

Ubuntu 24.04 is almost in Beta and they already moved to Linux 6.8.
Ubuntu and and Debian still use 0.14.1 and need to be "persuaded" to update to next release but 0.14.3 is still not enough for newer Kernels.

Uh didn't notice this part.
While we plan to tag libs 0.15.0 and drivers during this week (or by the end of the next one), we won't release a new Falco until the end of May.

/milestone next-driver

Drivers 7.1.0+driver are now tagged. We can consider this issue as solved.
/close

@FedeDP: Closing this issue.

In response to this:

Drivers 7.1.0+driver are now tagged. We can consider this issue as solved.
/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.


Revise errorhandlers

The errorhandlers are called after the coroutine returns, this means that they will not have a stacktrace, which makes it very cumbersome to track down errors in handlers/coroutines.
Revising them by wrapping the handler function in an xpcall which attaches the stacktrace to the error before reporting.

It's also possible to call debug.traceback on failed coroutine directly, the trace will start at error.

yes, that is probably a better solution, less overhead. thx for bringing it to my attention!

Hey, I was looking for a way to get better crash reporting (stack traces) with copas and stumbled upon this thread. Is this going to be ever resolved? Any workaround you can suggest in the mean time?

@pranas There is copas.setErrorHandler function that sets error handler to be called after anerror in current thread. Default handler prints the error, associated socket and coroutine. You can set it to also print traceback, like this (do this in every callback thread):
copas.setErrorHandler(function(msg, co, skt)
   print(msg, co, skt)
   print(debug.traceback(co))
end)

Currently it's not possible to rethrow the error as errors inside error handler are ignored.

@mpeterv awesome, thanks! 👍

@mpeterv having stack traces are great! However we see that error message sometimes comes in as nil. We checked and the same issue applies when you use default error handler. Are you aware of this problem? Any workaround for it?

We tested stack traces by triggering crash with undefinedFunction() and error message was nil.

Can't reproduce using this test case:
local copas = require "copas"

copas.addthread(function()
   copas.setErrorHandler(function(msg, co)
      print(msg)
      print(debug.traceback(co))
   end)

   undefinedFunction()
end)

Output:
testerror.lua:9: attempt to call global 'undefinedFunction' (a nil value)
stack traceback:
	testerror.lua:9: in function <testerror.lua:3>
	(tail call): ?

Ok, maybe an error on my side, can't reproduce it.


PINCache version need to update to latest version in pods

I am using both PINCache and PINRemoteImage which is causing iOS compilation issue with PINRemoteImage as pods is still referring to older version of PINCache.
Please update this to latest version.
Need to update
'PINCache', '=3.0.1-beta.8'
to
'PINCache', '=3.0.1'

Any plan to release it?


V1.0.0

Codecov Report

Merging #14 into master will increase coverage by 1.94%.
The diff coverage is 88.88%.

@@            Coverage Diff             @@
##           master      #14      +/-   ##
==========================================
+ Coverage      80%   81.94%   +1.94%
==========================================
  Files           8        9       +1
  Lines          65       72       +7
==========================================
+ Hits           52       59       +7
  Misses         13       13

Impacted Files
Coverage Δ

collection/sort.go
0% <0%> (ø)
:arrow_up:

collection/uniq.go
100% <100%> (ø)
:arrow_up:

collection/collection.go
100% <100%> (ø)
:arrow_up:

collection/array.go
100% <100%> (ø)
:arrow_up:

collection/each.go
100% <100%> (ø)

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 f001b66...9e8899e. Read the comment docs.


Map: The menu drawer handle is too tall

Make more like bing or google
Google:

But what if we want to put two buttons in the handle?
< for close menu item
<< for hide the whole darn thing
?


Proposed fixes to DHAP <=> sn-glycerol-3-phosphate reactions

I recently came across five reactions that are involved in the conversion of DHAP to sn-glycerol-3-phosphate in glycolysis that I've included below:

Reaction ID
Reaction String
GPR

MAR01169
FAD [m] + sn-glycerol-3-phosphate [c] ⇒ DHAP [c] + FADH2 [m]
GPD2

MAR00483
sn-glycerol-3-phosphate [c] + ubiquinone [m] ⇒ DHAP [c] + ubiquinol [m]
GPD2

MAR00482
FAD [c] + sn-glycerol-3-phosphate [c] ⇒ DHAP [c] + FADH2 [c]
GPD2

MAR00479
DHAP [c] + H+ [c] + NADH [c] ⇒ NAD+ [c] + sn-glycerol-3-phosphate [c]
GPD1L, GPD1

MAR00478
DHAP [c] + H+ [c] + NADPH [c] ⇒ NADP+ [c] + sn-glycerol-3-phosphate [c]
GPD1

The Uniprot page for GPD2 supports the reaction MAR00483, but contradicts MAR00482 and MAR01169. Similarly, the Uniprot pages for GPD1 and GPD1L  support MAR00479 but don't include MAR00478. Additionally, I wasn't able to find any papers that mentioned NADPH/NADP+ in this reaction in humans.
As a result, I think it would be appropriate to remove reactions MAR00482, MAR00478, and MAR01169

Good catch!
I am ok with removing MAR00478 and MAR00482.
I am not sure about this. I am not familiar with this protein, just from Uniprot annotation, it appears to have FAD binding region.

Cofactor
Protein has 1 cofactor binding site:
FAD (UniProtKB | Rhea| CHEBI:57692 )

@haowang-bioinfo what is your idea about this?

@jreimertz thanks for the checking

I am ok with removing MAR00478 and MAR00482. Removing MAR00482 since the protein is a mitochondria protein.

agree

The FAD-containing reaction (MAR01169) could be seen as part of a 2-step reaction with:
MAR06911: FADH2 [m] + ubiquinone [m] ⇔ FAD [m] + ubiquinol [m]
whereby the FAD cofactor acts as an intermediate electron carrier.
MAR00482, the FAD reaction taking place in the cytosol, is a bit weirder because there is no equivalent to MAR06911 in the cytosol, so it would instead be a 3-step reaction including MAR06911 above and:
MAR06513: FAD [m] + FADH2 [c] ⇔ FAD [c] + FADH2 [m]
So I agree with @feiranl to remove MAR00482 since it takes place in the cytosol and would have a strange mechanism, but I would not necessarily remove MAR01169.

MAR00482, the FAD reaction taking place in the cytosol, is a bit weirder because there is no equivalent to MAR06911 in the cytosol, so it would instead be a 3-step reaction including MAR06911 above and:
MAR06513: FAD [m] + FADH2 [c] ⇔ FAD [c] + FADH2 [m]
So I agree with @feiranl to remove MAR00482 since it takes place in the cytosol and would have a strange mechanism, but I would not necessarily remove MAR01169.

yes, MAR00482 should be removed for sure, as well as MAR00478 (use NADPH)

The FAD-containing reaction (MAR01169) could be seen as part of a 2-step reaction with:
MAR06911: FADH2 [m] + ubiquinone [m] ⇔ FAD [m] + ubiquinol [m]
whereby the FAD cofactor acts as an intermediate electron carrier.

this MAR06911 is very much relevant, and probably better pair with MAR00449: FAD [m] + sn-glycerol-3-phosphate [m] ⇒ DHAP [m] + FADH2 [m] than MAR01169: FAD [m] + sn-glycerol-3-phosphate [c] ⇒ DHAP [c] + FADH2 [m]. And both MAR00449 and MAR01169 have GPR GPD2, and the latter should be removed.

So a question about compartments: does the [m] compartment include both the intermembrane space and the mitochondrial matrix? Because the reactions catalyzed by GPD1 and GPD2 both specifically involve DHAP and glycerol-3-phosphate in the intermembrane space, not the mitochondrial matrix. And I've come across a lot of papers like this that characterize the metabolite pools of the cytosol and intermembrane space to be largely equivalent and both clearly distinct from the metabolic composition of the mitochondrial matrix:

The OMM often is considered a relatively non-specific ‘sieve’ that is permeable for most molecules up to 5 kDa. However, recent findings indicate a higher degree of selectivity and regulation and potentially also the existence of additional OMM transporters (Kruger et al., 2017). In comparison, the IMM is impermeable and metabolites require dedicated transporters – many of which are coupled to the anti/symport of other metabolites or to the mitochondrial membrane potential. As there are not IMM transporters for all metabolites, some metabolites have to be converted to other metabolites for which transporters exist. For example, the malate–aspartate shuttle serves to export oxaloacetate from the matrix to the cytosol or to transfer NADH from the cytosol to the matrix. As there is no IMM transporter for oxaloacetate, it has to be converted to aspartate, which can be transported out of the matrix in an antiport with glutamate. In the cytosol/IMS [the aspartate aminotransferase GOT2 is found in the IMS proteome (Hung et al., 2014)], aspartate is converted back to oxaloacetate, which is reduced by NADH, yielding malate, which is transported into the matrix in an antiport with 2-oxoglutarate.
Also it sort of seems like the [i] compartment is intended to represent the intermembrane space? Even though it's nominally named "inner_mitochondria", the electron transport chain reactions (MAR06914, MAR06918, MAR06921) move H+ from [m] to [i], and ATP synthase (MAR06916) returns them from [i] back to [m].
All that is to say: should the reaction that GPD2 catalyzes involve DHAP [i] and sn-glycerol-phosphate [i] instead of the [c] or [m] versions of those metabolites? If we think [c] includes the intermembrane space, then we should keep MAR00483 and remove MAR00449, but if we think [m] includes the intermembrane space (which I think is inaccurate), then we should keep MAR00483 and remove MAR00449.

The FAD-containing reaction (MAR01169) could be seen as part of a 2-step reaction with:
MAR06911: FADH2 [m] + ubiquinone [m] ⇔ FAD [m] + ubiquinol [m]
whereby the FAD cofactor acts as an intermediate electron carrier.

If we're keeping MAR01169 because GPD2 uses electrons from DHAP to reduce (tightly-bound) FAD, which it then also uses to reduce ubiquinone, then we should probably add it to the GPR of MAR06911, which currently contains the subunits of the electron transfer flavoprotein heterodimer (ETFA and ETFB) and ETFDH, which oxidizes the FAD bound to ETFA/B and reduces ubiquinone, and one of the subunits of the succinate dehydrogenase complex (SDHC). Since those enzymes are all part of distinct complexes, it seems like there's precedent for adding in another clearly distinct enzyme that catalyzes this reaction.

Here's a list of all similar pairs of reactions I could find (I'm reasonably confident this is all of them) with one FAD-dependent version and one ubiquinone-dependent version:

MAR02035 (ubiquinone) and MAR03121 (FAD)
MAR03211 (ubiquinone) and MAR03212 (FAD)
MAR03751 (ubiquinone) and MAR03752 (FAD)
MAR03783 (ubiquinone) and MAR03784 (FAD)
MAR04242 (ubiquinone) and MAR04243 (FAD)
MAR03769 (ubiquinone) and MAR03770 (FAD)
MAR03838 (ubiquinone) and MAR08611 (FAD)
MAR04652 (ubiquinone) and MAR08743 (FAD)
MAR02366 (ubiquinone) and MAR03163 (FAD)
MAR02367 (ubiquinone) and MAR03135 (FAD)
MAR02639 (ubiquinone) and MAR03149 (FAD)
MAR02370 (ubiquinone) and MAR03128 (FAD)
MAR02372 (ubiquinone) and MAR03156 (FAD)
MAR02373 (ubiquinone) and MAR03142 (FAD)

Also it feels relevant to note that several of the ubiquinone-dependent reactions in this list have inaccurate GPRs; they have ACOX1 and ACOX3 in them, which are peroxisomal proteins according to Uniprot and also several papers I found; their FAD-dependent duplicates have the correct GPRs
According to this paper the following enzymes interact with ETFA/B:

ACADVL
ACADL
ACADM
ACADS
ACADSB
ACAD9
ACAD10
ACAD11
GCDH
IBDH
IVD
SARDH
DMGDH
D2HGDH
Most of these are in Human-GEM and are collectively associated with hundreds of reactions, nearly all of which use FAD and not ubiquinone (the exceptions are above), so whatever we decide here should apply to all of these reactions as well.

There's also MAR00562, which turns FADH2 and Electron Flavoprotein Oxidized into FAD and Electron Flavoprotein Reduced, and MAR00563, which turns Electron Flavoprotein Reduced and ubiquinone into Electron Flavoprotein Oxidized and ubiquinol, which seem redundant with MAR06911 (I think MAR00562 and MAR00563 should be dropped cuz ETFA and ETFB and ETFDH are all already in the GPR of MAR06911), but hypothetically another option here would be to have all of the reactions associated with proteins that are known to interact with ETFA/B as the intermediate between FAD and ubiquinone reduced Electron Flavoprotein Oxdized instead of FAD.
There's also MAR04575: (S)-dihydroorotate + ubiquinol <-> orotate + ubiquinone, catalyzed by DHODH. DHODH is also a flavoenzyme but is one of the few human flavoenzymes that uses FMN instead of FAD as its intermediate electron acceptor. DHODH is capable of reducing ubiquinone, so we could keep it as-is, but if we want it to be consistent with all these other reactions, we would have to create a mitochondrial FMN metabolite (currently only exists in cytosol and extracellular compartments) and a new reduced FMN metabolite (which doesn't exist), and a new reaction catalyzed by DHODH that reduces ubiquinone with reduced FMN.

So a question about compartments: does the [m] compartment include both the intermembrane space and the mitochondrial matrix? Because the reactions catalyzed by GPD1 and GPD2 both specifically involve DHAP and glycerol-3-phosphate in the intermembrane space, not the mitochondrial matrix.

yes, GPD2 is localized in the intermembrane space, instead of the mitochondrial matrix

Also it sort of seems like the [i] compartment is intended to represent the intermembrane space? Even though it's nominally named "inner_mitochondria", the electron transport chain reactions (MAR06914, MAR06918, MAR06921) move H+ from [m] to [i], and ATP synthase (MAR06916) returns them from [i] back to [m]. Also there are apparently a ton of reactions that do cotransport of a cytosolic metabolite into or out of the mitochondria accompanied by H+ [i], so, despite the name, it seems like [i] is functionally a representation of the intermembrane space, but that [c] is also sort of treated as equivalent to/containing the intermembrane space?

yes, the [i] compartment is meant to represent the intermembrane space

Here's a list of all similar pairs of reactions I could find (I'm reasonably confident this is all of them) with one FAD-dependent version and one ubiquinone-dependent version:

Very good - might be better move this to a separate issue?

If we're keeping MAR01169 because GPD2 uses electrons from DHAP to reduce (tightly-bound) FAD, which it then also uses to reduce ubiquinone, then we should probably add it to the GPR of MAR06911, which currently contains the subunits of the electron transfer flavoprotein heterodimer (ETFA and ETFB) and ETFDH, which oxidizes the FADH2 bound to ETFA/B and reduces ubiquinone, and one of the subunits of the succinate dehydrogenase complex (SDHC). Since those enzymes are all part of distinct complexes, it seems like there's precedent for adding in another clearly distinct enzyme that catalyzes this reaction.

if provided with supporting evidence, GPD2 can be added to the GPR of MAR01169 (or MAR00449)

Regarding the [i] compartment:
As @haowang-bioinfo mentioned above, it represents the mitochondrial intermembrane space. While it is true that there are many more enzymes/reactions/metabolites that should actually be in the [i] compartment rather than [m], this is generally not done to avoid an unnecessarily large model.
The [i] compartment was primarily implemented as a tool to allow the simulation of energy exchange related to membrane concentration gradients (e.g., proton motive force), rather than to represent the actual contents of the intermembrane space in reality (described in detail in the supporting text of the Human1 publication). The [i] compartment is used to tightly control the transport of protons and other metabolites whose movement across the membrane is coupled to some energy-consuming or producing reaction; e.g., ATP synthase. Without the isolation of the [i] compartment, it becomes very difficult to prevent energy leakage because there are so many reactions that can produce/consume protons in a way that allow the model to "cheat" and create energy using combinations of such reactions.
So in general, the [m] compartment is used to hold all the reactions, metabolites, and enzymes that are present in the mitochondrial matrix or the intermembrane space, except for those that use or affect the membrane gradient in some way. Otherwise, the model would become much larger since many metabolites/reactions would need to be duplicated in the [i] compartment, and would make it more difficult to debug energy leakage issues related to that compartment.

A little bit summary of above discussions to make sure that I understand correctly.

we are all good about removing MAR00478 and MAR00482
keep reactions in [m]; since [i] is isolated for energy gradient
still wait for discussions for ubiquinone and FAD in #607 , then we can decide to remove MAR00483 or MAR01169

In #607 and #613, we decided to remove MAR00483, since GDP2 uses an FAD cofactor as an intermediate electron carrier between sn-glycerol-3-phosphate and ubiquinone, and MAR06911 already represents the reduction of ubiquinone with FADH2, which resolved the only remaining open question about the proposed changes in this issue, so all that's left is:

Remove MAR00478 because there's no evidence that GPD1 or GPD1L can use NADP(H) in addition to NAD(H)
Remove MAR00482 because GPD2 is definitely localized to the inner mitochondrial membrane, so it should use FAD(H2) [m] and not [c]
are we good to go with opening a PR to make those changes?

fixed in #710, feel free to reopen


New version: VolkerFischer.Jamulus version 3.11.0

Checklist for Pull Requests

[ ] Have you signed the Contributor License Agreement?
[ ] Is there a linked Issue?

Manifests

[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Installation failed with exit code -1978335187
2024-09-21 03:15:14.402 [FAIL] Installer failed security check. Url: https://github.com/jamulussoftware/jamulus/releases/download/r3_11_0/jamulus_3.11.0_win.exe Result: 0x80004005

Automated error analysis suggests -1978335187 may mean Installer failed security check. Another script should retry this every 18 hours.
Automated error analysis suggests 80004005 may mean Resource missing
(Automated response - build 896.)

@wingetbot run


[Windows] Desktop shortcut icon is not hidpi

Describe the bug
Looks like modern applications have bigger and cleaner icons (see icons on the left vs icons on the right)

Not windows specific, but I agree that F3D icon should be modernized.

Tested but I do not replicate the initial issue anyway.
1.3.1:

master:


Fix unpublish function to close all open connections and allow republish

After calling unpublish the HTTP server will be stopped but all clients stay connected which you can see if you call netstat. Any data which will be sent from those connected clients will still be processed even though the bridge should not be published anymore at this point. The process must be killed to close those open connections.
This makes it impossible to unpublish and republish a bridge. Furthermore the publish method cannot be called again because the ProtocolInformation service will be added again. The application needs to be restarted in order to be able to publish the bridge again.
Those issues lead to the issue described under https://github.com/NRCHKB/node-red-contrib-homekit-bridged/issues/12 where it is not possible to redeploy a bridge node in Node-RED by calling unpublish and creating a new bridge instance.

Well, that’s hot.

🙏 Thanks for fixing this


Docker Distribution isn't supported as a Ansible Service Broker registry

Feature:
The number and types of Ansible Service Broker Registrys that are supported are very limited. Our company would like to use Jfrog's Artifactory, but at a minimum, I would hope that a regular v2 distrubution end point would be supported. Would be great if you added v2 distrubution as supported registry fro Ansible Service Broker
What happened:
Tried using ansible service broker registry, was dissapointed when I could not
What you expected to happen:
I expected it to support docker distribution/registries, like pulp, or docker distribution, or jfrog aritfactory.
How to reproduce it:
Try and use any regular v2 docker distribution endpoint, it isnt currently supported.

Fixed by a bunch of PRs to bundle-lib
https://github.com/automationbroker/bundle-lib/pulls?q=is%3Apr+apiv2+is%3Aclosed

Yall are the best, thank you for working on this.


error: docker-compose up

Getting the following error, when running the...
Command
docker-compose up
Error:
16:21:27 ✘ pk:(master)~/Documents/code/graphprotocol/graph-node/docker$ docker-compose up
Starting docker_postgres_1 ...
Starting docker_postgres_1 ... error

ERROR: for docker_postgres_1  Cannot start service postgres: driver failed programming external connectivity on endpoint docker_postgres_1 (189ccdcca9625969a8de728a3e831919d29dd8240268e3cbb66599174ab4dc64): Error starting userland proxy: listen tcp <IP_ADDRESS>:5432: bind: address already in use

ERROR: for postgres  Cannot start service postgres: driver failed programming external connectivity on endpoint docker_postgres_1 (189ccdcca9625969a8de728a3e831919d29dd8240268e3cbb66599174ab4dc64): Error starting userland proxy: listen tcp <IP_ADDRESS>:5432: bind: address already in use
ERROR: Encountered errors while bringing up the project.

...please HELP!

Do you have postgres (or any other docker container running docker))  running locally on your machine? If so, you need to wind it down to allow docker to use that port.

Hey @pkrasam 👋 !
Have you resolved this issue with your local deployment?
I agree that it appears you already had a postgres instance (or something else) running on port 5432.


[DO NOT MERGE] Switch email list adapter to just use "create"

https://trello.com/c/dgdLhy2H/777-update-transition-to-brexit-in-email-notifications-for-transition-taxon
Depends on: https://github.com/alphagov/email-alert-api/pull/1569
Previously calling "find_or_create_subscriber_list" would result in
up to 2 API calls. Since we've changed the "create" endpoint to also
return an existing list 1, we can simplify the adapter to just use
that, with the added benefit of keeping titles/URLs in-sync.

@sihugh I've added another commit to this, to remove a couple of test helpers. This more clearly makes this a breaking change, so I've specified as much in the CHANGELOG.
Would you like to take another look?

@sihugh I've added another commit to this, to remove a couple of test helpers. This more clearly makes this a breaking change, so I've specified as much in the CHANGELOG.
Would you like to take another look?


accordion app bug: navigates to home page with strange url when editing or opening

I'm running a local Oqtane site in debug (localhost:44357/).
When editing (or sometimes even just clicking on a 2nd accordion app on a new test page), it seems to treat it as a hyperlink with names like localhost:44357/#a-2985 which takes me away from the page with the accordion on and to the site's home page.

This appears to be related to an issue with the Razor navigation system; it "intercepts" certain actions.
Could you specify Oqtane version and rendering / interactivity modes?

Thanks - I believe I have the latest version of Oqtane (6.0.0) , with render set to Interactive (because I am using the StudioElf.Theme.JetPack.Theme, StudioElf.Theme.JetPack.Client.Oqtane theme).  But I didn't reinstall the accordion app, instead I just replaced the two files as per https://github.com/2sic/app-accordion/issues/24#issuecomment-2530986411.

@ropalko maybe we should just change the accordion to not change the URL on Oqtane (I think something like $2sxc.env.platform() https://docs.2sxc.org/api/js/SxcGlobalEnvironment.html#Api_Js_SxcJs_SxcGlobalEnvironment.
This would reduce it's functionality, but at least not break links for now.
What do you think @ropalko ?

I think its a good idea, i will change this.

Hello @patrickjlee
I have updated the code. Please apply the following changes:
These are located under /bs5/dist
scripts.min.js
scripts.min.js.map
This ist located under /bs5
Assets.cshtml
In this file you can also simply add the line: @Kit.Page.Activate("2sxc.JsCore")

Many thanks @ropalko! That does seem to have fixed the issue :)


Discuss swaggerMetadata namespacing its processed request parameters

Typical Node.js development uses req.params to get access to request parameters.  With swaggerMetadata, we intentionally namespaced them in req.swagger.params.  Let's run this by the community to see what their thoughts on doing this are.

I know this is coming in late, but I thought I would offer a bit more feedback:

Swagger-tools utilizes tools to set req.query and req.body, but it avoids req.params? Seems like it's breaking the pattern...
Node Express prevents modifying the req.params with middleware, so the suggestion by BigstickCarpet to add middleware would not work.
I think a simple solution would be to modify swagger-router.js to add:

var swaggerParamsToParams = function(req){
  _.forEach(req.swagger.params, function(param, key){
    if (param.schema.in === 'path')
      req.params[key] = param.value;
  })
}

just before calling the handler. That wouldn't break any middleware, but it would also allow the use of the more common req.params variable

swagger-tools does nothing of the sort regarding req.body or req.query.  The server middleware is responsible for these things.  And while swagger-tools provides default middleware for you so things just work, it's up to you to own this if need be.  req.swagger is the only object swagger-tools creates/manipulates

swagger-tools does not alter req.params

I don't know that we have a problem here so the solution doesn't make much sense to me


Added build preLaunchTask for debug configuration

@Deilan,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot


Lunar Icon Outlines are off-model

They're dark blue, when they ought to be cyan - see this screenshot for comparison.

Also there's now a mod by Kevin that lets you generate outlines in-game, if that's easier than the method you used for the other items. https://thunderstore.io/package/KevinfromHPCustomerService/PickupIconRenderer/

Thanks, I never noticed that! Fixed in the upcoming update.


Multi audio streams not migrating correctly

Whenever I use a video Asset with multi audio streams (e.g. english + french). The output will be in CMAF (as expected) and have the same amount of audio streams but then english + english.

Hi @mouab215,
Is it possible for you to provide input assets for us investigate?  If not, is it possible to provide the ism/ismc files?
Thanks.

hi @pohhsu, Yes, here it is. Let me know if it works:
https://we.tl/t-4NFzYdYOqa

Looks like we are hitting a bug with shaka packager, where even though in the command line we specify the two audio streams as eng & fre, the generated mpd/m3u8 only has language as eng.

Create a pull request #231 for this issue. While waiting for the fix, the customer can make the change locally and test.  It is a one line change in Manifest.cs  (or you can use the duggaraju/mulit_audio) branch.

Hey @duggaraju , I've tried it with the latest commit, however i still end up with 2 english audio tracks while the initial asset contains both english and french


added logo to front page

This is relating to issue #4

Hi there! I'd like to merge this, but I don't have permission from the organization to add the logo. Is there another image you would like to choose that is free to use? I like to use https://unsplash.com/ and https://pixabay.com/illustrations/ to find royalty-and-trademark-free images.

Sure, I'm switching out the image now.

Hi Jen, looks like it's ready to merge. Let me know any issue.


The icon for switching between list and grid views on the timetable screen differs from the Figma design

actual
expected

The icon has already been switched to the correct one, so I will close this.


Skip python.exe with uv install python --default

I love the uv python install --default feature (https://github.com/astral-sh/uv/pull/8650), but it creates a python.exe executable in addition to a python3.exe executable. Unfortunately, we still need python.exe to resolve to a Python 2.7 interpreter for the time being. Would you be willing to add a uv.toml setting or an alternative --default-py3only arg or something that limits the feature to only managing python3.exe. Similar issue on Linux, but I'm specifically looking at the Windows behavior.

Oof. Hm.. I guess a uv.toml setting is less controversial to me (it seems niche for the CLI), but we don't have Python install settings there yet.
Would an environment variable be sufficient?

Unfortunately, we still need python.exe to resolve to a Python 2.7 interpreter for the time being.

Would it be feasible to specify the full path to your 2.7 interpreter? Or adjust the PATH in that context?
Thanks for reporting!

Would an environment variable be sufficient?

Yeah, that could work. We could set that globally in our uv installation script (not that different from setting it in the uv.toml). We're already setting the default index url and python-install-mirror in the uv.toml.

Would it be feasible to specify the full path to your 2.7 interpreter? Or adjust the PATH in that context?

Not easily. We need to support a mixed environment where legacy scripts expect python to be Python 2.7. I really want ~/.local/bin to be first in the PATH since that's where all the uv goodies live, but a python.exe there will shadow others later in the PATH. Putting Python 2.7 before ~/.local/bin on the PATH could work, but introduces other complexities with managing PATH order.
Also feel free to decide that uv isn't going to go out of its way to support coexistence with Python 2. That'll make me sad because --default is exactly the feature I want to use to manage Python 3 versions going forward, but I can create my own python3.exe symlink that points to the desired uv trampoline executable instead or come up with other workarounds 😊.

Another question, is there a way you're invoking python.exe for Python 2 that would inform us that we should pass that invocation through to another executable?
I think some flag here is reasonable, just need to figure out how to express it.

Python 2 is typically invoked via the shebang in the the Python script (e.g. #!/usr/bin/env python) in a Git Bash (aka msys bash) shell on Windows. We do it this way so it works the same on Linux and macOS. There are some shell scripts that explicitly call Python 2 scripts directly, like python myscript.py. Both cases assume that python is on the PATH and resolves to Python 2.


XLA BF16 enablement of Gemm and Conv

@stevenireeves the changes do not enable any tests, how did we test this change?

@deven-amd before this PR BF16 was changed into FP32 on ROCm. BF16 is covered in  https://github.com/ROCmSoftwarePlatform/tensorflow-upstream/blob/develop-upstream/tensorflow/compiler/xla/tests/convolution_test.cc#L1568-L1589


[nRF54l] drivers/flash/Kconfig.nrf_rram: bufferd write by default

Enable buffered write for nRF54l RRAM flash driver by default. CONFIG_NRF_RRAM_WRITE_BUFFER_SIZE=1 means that write will be buffered by 16 B buffer (native RRAM write-bock-size).
This allows optimal life-endurance of RRAM memory.
For reference" DTS declares 16 write-block-size alredy.

Why not go with 16 byte buffer directly?

Why not go with 16 byte buffer directly?

This enable 16 B buffer using HW capability given. RRAMC unit is equipped with 32 of 128-bit buffers for incoming data. So it is possible to use only multipliers of 16 B buffer size: 0 - no use, 1 -> 16 B, 2 -> 32 B, 3 -> 48 b and so one

@carlescufi We are using RRAM very suboptimal. Buffering should be used - It ensures maximum lifetime endurance of RRAM on RRAMC built-in behavior level.


Radar Chart?

I couldn't see any example of a Radar Chart. Does react-vis support it?

Not at the time, but a PR would be appreciated! 😃

I've been thinking Radar charts would be part of a larger story around r-theta plots (#209), which would enable us to do a whole variety of additional polar coordinate based charts!

At last radar charts are part of the library! Woot! They'll be up int he next release


Add Parcel Bundler doc

Hello,
Not sure if it helps but proposed.
Tested and used with V5 alpha.
Thanks,
Eric
Preview: https://deploy-preview-30909--twbs-bootstrap.netlify.app/docs/5.0/getting-started/parcel/

That being said, I'm not sure if this gives any value? I mean, it's the same procedure as webpack.

Hello,

That being said, I'm not sure if this gives any value? I mean, it's the same procedure as webpack.
Not at all.

Simply use this 'import 'bootstrap' don't work. I also needed to add as bootstrap` to avoid building errors and have bootstrap js available (I don't remember the case).
You should check with :
if (typeof bootstrap !== 'undefined' || bootstrap !== null) {
    console.log("Popover version : " + bootstrap.Popover.VERSION);
} else {
    console.log("index.js : Bootstrap undefined");
}

Thanks,
Eric

@mdo WDYT?

I'm not a big fan of doing a separate page for all the bundlers 🤔

I don't mind having separate pages for key tools and more from the ecosystem. If anything it boosts our visibility and usability across multiple communities and gives folks a solid starting point inside our own docs.

Pushed a bunch of updates to simplify and standardize:

Removed some headings, sentence cased some other headings
Removed the CSS snippets and defer folks to the extensive customize section w/ details on Sass
Combined and clarified JS import options
Buttoned up some copy

@mdo my only problem is listing this and parcel in Getting Started. We should probably add a parent submenu later.
Branch rebased.

Yeah good point. And while we’re thinking about it, what else could we do for guides like this? Are there more languages and tools?

@mdo not sure but maybe we should land this after the Windows issue is sorted out, and we add a new parent page later.

@eldk care to take care of the rm issue?

Hello @XhmikosR ,
I have no windows device, so I can't test it.
I think this should be used :
"prebuld": "rmdir /Q /S \"build\""
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/rmdir
https://stackoverflow.com/questions/50696920/configuring-package-json-on-windows
Maybe should someone test it to confirm it's OK ?
Thanks,
Eric

@eldk now the docs will only work on Windows 😛 Maybe just go with npx rimraf build?

But I think with the npx solution we can make this cross-platform.

That's ok for me.

@XhmikosR Do we need this in the beta, or can it wait until v5 stable or v5.1.0?

It can wait, but it's ready I think. We could probably create a new subgroup named Bundlers and move Webpack and Parcel and whatever new shows up in the future, or leave it as is for now.


HS-754108 - Remove i wording

Do not advertise an unsupported feature.
Helpscout

@wrandall22 looks like amplify is complaining in this app too, similar or different issue from mpdx_web?

Different, from provisioning step:
Build failed to complete successfully. Reason: [BUILD_CONTAINER_UNABLE_TO_PULL_IMAGE: Unable to pull customer's container image. CannotPullContainerError: Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit]

Haha, got past that error then ran into the same one you hit in mpdx.

https://github.com/CruGlobal/cru-terraform/blob/master/applications/campus-contacts/web/amplify.tf#L8-L9

https://github.com/CruGlobal/cru-terraform/blob/master/applications/campus-contacts/web/amplify.tf#L8-L9

Yep, same values we have for mpdx. Wondering if we should have a team/shared account so we don't run into this again

This pull request is automatically being deployed by Amplify Hosting (learn more).Access this pull request here: https://pr-852.d23um2gb8xlk6n.amplifyapp.com

@wrandall22 that's a good sign!

This seems to be working in stage. I'll plan to deploy tomorrow morning.


ROWY-954: Quick-Fix - GitHub Sign-in Issue in Roadmap App

This PR fixes the bug, as seen in this GitHub Discussion: https://github.com/rowyio/rowy/discussions/1122. The Roadmap app currently gives a runtime error when logged in via GitHub.
Fix: Set the displayName variable to have optional value.

@BeeBombshell The error that user faced is seems like related to server model than client. I'm going to reproduce the error first, then I'll leave further information here.


Using a react-media component as child to Slider

I'm trying to use a <Media/> component from react-media (https://www.npmjs.com/package/react-media) to render an extra component at the end of the slider based on whether the query matches or not.
When the query matches, the component is rendered correctly. However, when the query doesn't match, the component isn't rendered but an empty slide is still rendered. I'm guessing this is because react-slick still sees the Media component and believes a component is being rendered, but in actual fact it's just a higher order component that renders the children that are passed to it.
I've replicated this issue here: https://codesandbox.io/s/0662x6kyl
Any ideas how to get round this?

Our current work around is to use two different <Media> components with complementary queries, and render different <Slider>s in each one, see: https://codesandbox.io/s/v0w7673lq3
Not an ideal solution, so still open to ideas around this


Removed SolFile class in favor of a new FileManager class

The code contained hardcoded filepaths in many classes that had to read from or write to files.
The SolFiles class also required a boolean flag for each file access, so the user had to know whether or not the file was located in the readonly file directory or the writable file directory.
The FileManager solves both these issues. It internally contains (the most common) directory paths
and can provide users with the correct filehandle for these directories, without having to provide any additional arguments.
This PR also changes the terms for "readonly" and "writable" files to "static" and "dynamic" files.

Excellent cleanup, thanks!


⚠ Jenkins Plugins Artifactory has degraded performance

In 13a282d, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 2407 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 7ee9464 after 17 minutes.


restic prune/check should report defective snapshots on error

Output of restic version
restic 0.3.2 (v0.3.2-18-g4a6086a)
compiled with go1.7.4 on linux/amd64

Expected behavior
[Feature Suggestion]
A CLI switch --skip-defective-packs should allow prune to operate even if some packs/blocks as long as it can safely operate on the remaining data. A single corrupt packfile should in this case output an error and return a non-0 exitcode, but not stop prune from operating. Corrupt trees should be prunable with --remove-corrupt-trees.
restic check should output a list of snapshots which are affected by corrupt files in the repository.
Example output:
found corrupt snapshots:
* 5f943409 -> packfile 2239aa29 corrupt: header larger than file
* 5f943409 -> packfile ceef3392 corrupt: checksum mismatch
* 1220aa31 -> packfile ceef3392 corrupt: checksum mismatch

For an overview, it might also be helpful to include hostname/timestamp into this output.
Actual behavior
restic prune crashes/terminates with an header larger than file error
restic check will simply state that there are errors without specifying further information.
Steps to reproduce the behavior

Create Repository with Snapshots
Modify/Corrupt Packfile so that it outputs header larger than file

(Sadly the error cleared on my side by now and I was unable to manually induce it again)

Hey, thanks for reporting this issue! I think we need to make check/prune more robust.


Paste (CTRL+V) without formatting short key (e.g. CTRL+SHIFT+V)

Description of the new feature / enhancement
One feature I'm missing in PowerToys is the option to past (CTRL+V) without formatting.
Personally I find it very enoying that Windows per default pastes with formating, because when copying from one app to the other the formating is always different.
Is some application (like chrome) you can past without format by pressing CTRL+SHIFT+V.
In other applications (e.g. office) you have to use a special menu to choose different pasting options (special past-> merge, text only, ...)
Wouldn't it be great that PowerToys could harmonize the different solutions?
Scenario when this would be used?

Option to set 'Always without formatting'. Meaning, everything on the clipboard is kept without formating.
Shortkey definition to past without formatting, for example: CTRL+SHIFT+V
In addtion maybe a past option to merge the formatting with the destination. For example, your typing a heading in Word, and you want to past a phrase or sentence. Then it would be great that it uses the current selected formatting in Word instead of without formatting, or with the formatting from the source.

Supporting information
In general, this would improve my productivity or reduce frustrations during the day.

I like this idea! I currently use PureText to do this (http://stevemiller.net/PureText/). But I am on a mission to reduce the number of little utilities I have installed and if this was added to PowerToys, I would remove PureText.

Duplicate of #1684

Issue is a duplicate
Thank you for your issue! We've linked your report against another issue to centralize the thread.
Thanks for helping us to make PowerToys a better piece of software..


canceling a bogus linking

I made a typo in one of the account when creating the linkage.  The good news is I noticed it quickly since the next page show the full name from the erroneous account.  But this makes me think that an easy way to cancel a linkage in progress would be nice.  Or maybe just mention of when the request will time out.

I was thinking about deleting pending verification after 3 days if unsuccessful. What do you think about that?


Pjl customtabs

Creates an embedded chrome custom tab when clicking a link inside a chat room. Need to customize the chrome custom tab according to the options documented here: https://developer.chrome.com/multidevice/android/customtabs.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 3 committers have signed the CLA.:white_check_mark: bizzbyster:x: ear-dev:x: Peter LepeskaPeter Lepeska seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Add Azure App Configuration Extension

[ ] Requires Quarkus with SmallRye Config 2.13.0

@radcortez you've set the Quarkus version to <quarkus.version>999-SNAPSHOT</quarkus.version>. Is that because you are waiting for SmallRye Config 2.13.0 ?

@radcortez you've set the Quarkus version to <quarkus.version>999-SNAPSHOT</quarkus.version>. Is that because you are waiting for SmallRye Config 2.13.0 ?

Yes, the update will come in the next Quarkus version. Once is out, I'll update the PR.

BTW the reason is that the latest SR Config, added the ability to provide a ConfigMapping in the ConfigSourceFactory: https://github.com/smallrye/smallrye-config/pull/827

Quarkus 2.15.0.CR1 is available on Central since a couple of hours. It seems to have SmallRye Config 2.13.0 already: https://repo1.maven.org/maven2/io/quarkus/quarkus-bom/2.15.0.CR1/quarkus-bom-2.15.0.CR1.pom

I confirm that mvn clean integration-test -Dnative passes with <quarkus.version>2.15.0.CR1</quarkus.version>

@radcortez wouldn't it be better to name this extension microprofile-config (jakartaee-config maybe in the future) ? I know that naming things is hard, but I can already see a microprofile-health and a microprofile-rest-client extensions coming.

I wanted to match the name of the Azure service we are integrating with. I think it may be easier for users to find it.
Also, the config extension is tied to Quarkus. Yes, it does use some MicroProfile Config APIs, but it would not work standalone. Calling it microprofile-config may give the wrong impression that it will work with any MP environment, but it won't with the current implementation.
If Jakarta Config becomes a thing, it would just be an implementation detail in the extension. The user will not care which one is using.
Anyway, I'm happy to rename it if you think it makes more sense :)

@all-contributors please add @radcortez for code.

@all-contributors please add @ppalaga for review


Make program?

Hello, can´t you make program like there is for PermissionsEx? I mean https://www.spigotmc.org/resources/pexbuilder-gui.42248/
What is there good?
Available permissions - you can select and them and transfer them to active permissions.
It looks very cool, beacuse you don´t need find permissions for specific plugin.
Or you can add that to your web interface.

LuckPerms has a graphical editor:


fix: Clone options object before mutating it

This fixes a weird stateful bug where a single comment-based JSX pragma declaration can change the pragma used for all subsequent transforms.
The issue is caused by the options object being mutated by the transform() function. In particular, it is done when a @jsx directive comment is found in a file. If you then re-use the same options object instance for your next transform call (which coincidentally is what is done by buble-loader), you will be potentially passing through an incorrect JSX pragma.
Example
const transform = require('buble')

const options = {}

transform(`
/* @jsx h */
const { h } = require('preact')
const foo =
Bar

`, options)

/* output:
const { h } = require('preact')
const foo = h('div', {}, 'Bar')
*/

// At this point, options has been mutatated by calling `transform`, it now looks like this: { jsx: 'h' }

transform(`
const React = require('preact')
const foo =
Bar

`, options)

/* output:
const React = require('preact')
const foo = h('div', {}, 'Bar')
*/

The solution I have implemented here is to shallow-clone the options object before mutating it.

I have no idea why tests are failing in node 8, it works absolutely fine locally


Create Post “installation”

Automatically generated by Netlify CMS

👷 Deploy Preview for hotplate-docs processing.

Name
Link

🔨 Latest commit
b579e50d0f5129fa3da5c0bfcc548aafb15ffb01

🔍 Latest deploy log
https://app.netlify.com/sites/hotplate-docs/deploys/62bcde1bfa95840008c49f98


Handle errors returned by cmark_resume_with_options()

Here's the follow-up to https://github.com/Byron/pulldown-cmark-to-cmark/issues/91!

Oh, I see now that the version bump was already done in #242 by @kdarkhan. I'll keep my first commit here (for now) since I find the workaround slightly cleaner than what the merged PR does — then I can rebase either way, depending on what you prefer.

Oh, I see now that the version bump was already done in #242 by @kdarkhan. I'll keep my first commit here (for now) since I find the workaround slightly cleaner than what the merged PR does — then I can rebase either way, depending on what you prefer.

Thanks for handling this, @cip999! Please rebase this on top of latest changes. Would be good if @mgeisler could take a look as well since he has some context on this issue.

Oh, I see now that the version bump was already done in #242 by @kdarkhan. I'll keep my first commit here (for now) since I find the workaround slightly cleaner than what the merged PR does — then I can rebase either way, depending on what you prefer.

Thanks for handling this, @cip999! Please rebase this on top of latest changes. Would be good if @mgeisler could take a look as well since he has some context on this issue.

Thanks for reviewing! Yes that's a good idea, and it can wait, there's no rush to merge this PR right now. :slightly_smiling_face:

Codecov Report
Attention: Patch coverage is 77.34375% with 29 lines in your changes missing coverage. Please review.

Project coverage is 84.78%. Comparing base (a3bb63f) to head (9a72a91).

Files with missing lines
Patch %
Lines

i18n-helpers/src/lib.rs
65.30%
3 Missing and 14 partials :warning:

i18n-helpers/src/gettext.rs
91.66%
4 Missing and 1 partial :warning:

i18n-helpers/src/normalize.rs
57.14%
1 Missing and 2 partials :warning:

i18n-helpers/src/xgettext.rs
72.72%
0 Missing and 3 partials :warning:

i18n-helpers/src/preprocessors/gettext.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #244      +/-   ##
==========================================
- Coverage   84.87%   84.78%   -0.09%
==========================================
  Files          15       15
  Lines        3366     3379      +13
  Branches     3366     3379      +13
==========================================
+ Hits         2857     2865       +8
+ Misses        422      413       -9
- Partials       87      101      +14

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


JAVA-2216 - add partialFilterExpression to indexRequest in async MongoCollectionImpl

Thanks @ekandlen for the ticket and the patch


Create feature_cached.rb

This is a cached version of feature_dism. Dism is ran once and a copy is stored in memory and reused for the life time of chef-client. As such it is an order of magnitude quick when checking multiple features
The cache is cleared if pages are installed or removed via this same provisioner.
For now to use set node.default['windows']['feature_provider'] = 'cached'.
Perhaps once it's proven it can be added to feature.rb as a normal option.
I've tested this with the provided test kitchen resources as well as with our own cookbooks.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
GitHub Users Who Are Not Authorized To Contribute
The following GitHub users do not appear to have signed a CLA:

@mattchurchy

Please sign the CLA here.

This is a great idea and I'd be inclined to say go ahead and just add to the dism feature. The unfortunate thing is that if you mix feature providers in a single run, the cache could be invalid. Its certainly possible to mix providers but unlikely unless you have multiple community cookbooks wrapping windows_feature and using different providers.

Same as https://github.com/chef-cookbooks/windows/pull/339. Just trying to the CLA signing recognised. Also just saw @mwrock comments so will give that some thought.

@mattchurchy Regarding the CLA - is the email on your commit (your gmail address) associated with your github user account?  And that github user account associated with your Chef supermarket account?
As to the technical aspect, I like Matt's thinking and making sure that the cache is only hit for like providers.

Whoa CCLA should be sorted now! I'll have to switch to my other git-hub account though.
Sorry but I'm not following how you want to proceed....
You want me to modify Feature_Dism and not worry about other providers?
I could introduce a new attribute as a fail-safe to allow caching to be disabled?
Regardless of whether multiple providers is handled, there will remain the possibility of software installing windows features in the background. This feels like a niche scenario to me though, and a user could just converge again. So having an attribute feels like a reasonable compromise to me for users to need to handle that scenario.


make abstraction strip worn flag

This is just a bit of a thing: abstract didn't strip the worn flag so if you abstracted something worn, it remained notionally worn.

Should this not also be done for BANISH?

Makes sense; I didn't think of it. I'll submit a patch to my patch.

I got Banish and its little dog Purloin, too.
Stripping worn. ecdysiasm. I should've named the branch ecdysiasm.


roll ios-deploy to HEAD

Upstream commit https://github.com/ios-control/ios-deploy/commit/4405d291e2be6dfcf608da06a52ef969c06f8682

On this version I'm seeing [....] Disconnected <> from WIFI. logging:
$ flutter run -d 00008027-001925360106802E
...
An Observatory debugger and profiler on iPad is available at:
http://<IP_ADDRESS>:63652/o1xKe9CMH88=/
Activating Dart DevTools...                                      1,305ms
The Flutter DevTools debugger and profiler on iPad is available at:
http://<IP_ADDRESS>:9100?uri=http://<IP_ADDRESS>:63652/o1xKe9CMH88=/
[VERBOSE-2:profiler_metrics_ios.mm(203)] Error retrieving thread information: (os/kern) invalid argument
[....] Disconnected d83d5bc53967baa0ee18626ba87b6254b2ab5418 from WIFI.
[....] Disconnected d83d5bc53967baa0ee18626ba87b6254b2ab5418 from WIFI.

d83d5bc53967baa0ee18626ba87b6254b2ab5418 isn't even the device I'm flutter runing to, it's another iPhone I have.
https://github.com/ios-control/ios-deploy/pull/442 (and then https://github.com/ios-control/ios-deploy/pull/490)
When I unlock this other device I see the logging from https://github.com/ios-control/ios-deploy/pull/502
Skipping d83d5bc53967baa0ee18626ba87b6254b2ab5418 (N71mAP, iPhone 6s, iphoneos, arm64, 13.7, ) a.k.a. 'iPhone 6s'.

I think we'll need to suppress the [....] ios-deploy prefixed logging since it's confusing.

ios-deploy has a -output <file> and --error_output <file> option, which I think may only include the lldb output we want and not the ios-deploy debugging lines? Would have to check though.  So we could output those to a file, or somehow direct those to stdout and throw the actual process stdout on the ground (except maybe when flutter logging is verbose?)

Note to self: i opened the following upstream PRs to make these log messages verbose-only:

Make "Disconnected..." message verbose-only ios-control/ios-deploy#532
Make "Skipping..." log messages verbose only ios-control/ios-deploy#531

These PRs were merged upstream, and I rolled the commits to our mirror, however, we are blocked on building the newest version by https://github.com/flutter/flutter/issues/90403

@jmagman rolled to my changes marking the logs in question verbose, could you take another look?


Save processed Dataset

Proposed changes
Implementing save and load for datasets with pickle.
Closes #96.
Checklist
Put an x in the boxes that apply.

[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation

I think it's fair to assume that our main branch is in sync with the mlx main branch - we'll wait for mlx 0.6 before making the new release though

0.6 is out anyway 😉

Amazing!