"JoinEP: Failed to load program for host endpoint" error when starting cilium-agent

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Cilium agents running on some nodes in the cluster do not start properly and display error messages (below).
root@rs-dal-km1-staging:~# cilium status
    /¯¯\
 /¯¯\__/¯¯\    Cilium:         2 errors
 \__/¯¯\__/    Operator:       OK
 /¯¯\__/¯¯\    Hubble:         disabled
 \__/¯¯\__/    ClusterMesh:    disabled
    \__/

DaemonSet         cilium             Desired: 3, Ready: 3/3, Available: 3/3
Deployment        cilium-operator    Desired: 1, Ready: 1/1, Available: 1/1
Containers:       cilium             Running: 3
                  cilium-operator    Running: 1
Cluster Pods:     0/1 managed by Cilium
Image versions    cilium             quay.io/cilium/cilium:v1.12.2@sha256:986f8b04cfdb35cf714701e58e35da0ee63da2b8a048ab596ccb49de58d5ba36: 3
                  cilium-operator    quay.io/cilium/operator-generic:v1.12.2@sha256:00508f78dae5412161fa40ee30069c2802aef20f7bdd20e91423103ba8c0df6e: 1
Errors:           cilium             cilium-nww6k    controller endpoint-3020-regeneration-recovery is failing since 3m16s (111x): regeneration recovery failed
                  cilium             cilium-b2xfx    controller endpoint-4082-regeneration-recovery is failing since 1m6s (112x): regeneration recovery failed

The cilium-agent pods are in Running status, but keep printing the error messages shown below repeatedly
root@rs-dal-km1-staging:~#  kubectl -n kube-system get pods -o wide
NAME                               READY   STATUS    RESTARTS       AGE     IP              NODE                        NOMINATED NODE   READINESS GATES
cilium-b2xfx                       1/1     Running   0              3h39m   x.x.x.x   kubenode5   <none>           <none>
cilium-nww6k                       1/1     Running   0              3h39m   x.x.x.x   kubenode1  <none>           <none>
cilium-operator-74448469b9-9sq89   1/1     Running   2 (2d4h ago)   12d     x.x.x.x   kubenode1  <none>           <none>
cilium-pfl2p                       1/1     Running   0              12d     x.x.x.x   kubenode6  <none>           <none>
<none>

I have included the error message being displayed, in the section below. This is from cilium-b2xfx. The message keeps repeating. I have attached the full log file with this ticket.
Cilium Version
$ cilium version
cilium-cli: v0.12.4 compiled with go1.19.1 on linux/amd64
cilium image (default): v1.12.2
cilium image (stable): v1.12.3
cilium image (running): v1.12.2

Kernel Version
# uname -a
Linux rs-dal-km1-staging 4.19.0-6-amd64 #1 SMP Debian 4.19.67-2+deb10u2 (2019-11-11) x86_64 GNU/Linux

Kubernetes Version
# kubectl version
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.8", GitCommit:"a12b886b1da059e0190c54d09c5eab5219dd7acf", GitTreeState:"clean", BuildDate:"2022-06-16T05:57:43Z", GoVersion:"go1.17.11", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.8", GitCommit:"a12b886b1da059e0190c54d09c5eab5219dd7acf", GitTreeState:"clean", BuildDate:"2022-06-16T05:51:36Z", GoVersion:"go1.17.11", Compiler:"gc", Platform:"linux/amd64"}

Sysdump
cilium-sysdump-20221117-130912.zip
Relevant log output
level=warning msg="JoinEP: Failed to load program for host endpoint (from-netdev)" containerID= datapathPolicyRevision=0 desiredPolicyRevision=8 endpointID=4082 error="Failed to replace Qdisc for eno1: netlink: Replacing qdisc for eno1 failed: invalid argument" file-path=4082_next/bpf_host.o identity=1 ipv4= ipv6= k8sPodName=/ subsys=datapath-loader veth=eno1

level=error msg="Error while rewriting endpoint BPF program" containerID= datapathPolicyRevision=0 desiredPolicyRevision=8 endpointID=4082 error="Failed to replace Qdisc for eno1: netlink: Replacing qdisc for eno1 failed: invalid argument" identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint

level=warning msg="generating BPF for endpoint failed, keeping stale directory." containerID= datapathPolicyRevision=0 desiredPolicyRevision=8 endpointID=4082 file-path=4082_next_fail identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint

level=warning msg="Regeneration of endpoint failed" bpfCompilation=8.121081665s bpfLoadProg=7.129776105s bpfWaitForELF=8.12168829s bpfWriteELF=2.064211ms containerID= datapathPolicyRevision=0 desiredPolicyRevision=8 endpointID=4082 error="Failed to replace Qdisc for eno1: netlink: Replacing qdisc for eno1 failed: invalid argument" identity=1 ipv4= ipv6= k8sPodName=/ mapSync="5.181µs" policyCalculation="67.333µs" prepareBuild=33.633652ms proxyConfiguration="18.589µs" proxyPolicyCalculation="6.299µs" proxyWaitForAck=0s reason="syncing state to host" subsys=endpoint total=15.291350907s waitingForCTClean="1.138µs" waitingForLock="22.182µs"

level=error msg="endpoint regeneration failed" containerID= datapathPolicyRevision=14 desiredPolicyRevision=8 endpointID=4082 error="Failed to replace Qdisc for eno1: netlink: Replacing qdisc for eno1 failed: invalid argument" identity=1 ipv4= ipv6= k8sPodName=/ subsys=endpoint

level=warning msg="Failed while regenerating endpoint" endpointID=4082 subsys=endpoint

level=info msg="Finished regenerating restored endpoints" regenerated=0 subsys=daemon total=

Anything else?
Please find the full log file from cilium-agent pod cilium-b2xfx attached.
cilium-agent-b2xfx.txt
The kernel config from kubenode5  as mentioned in the requirements document,  is below.
# grep -f config  /boot/config-4.19.0-20-amd64
CONFIG_CGROUPS=y
CONFIG_CGROUP_BPF=y
CONFIG_BPF=y
CONFIG_BPF_SYSCALL=y
CONFIG_NET_SCH_INGRESS=m
CONFIG_NET_CLS_BPF=m
CONFIG_NET_CLS_ACT=y
CONFIG_BPF_JIT=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_USER_API_HASH=m

I had looked at other similar issues while filing this issue. Issue https://github.com/cilium/cilium/issues/14753 seemed close, but the error was different.
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I found the root cause for this.
It turned out that kube-proxy-replacement was set to strict in my cluster. The feature required a greater kernel version than the one running on my kubenodes (4.19.0-20).
I set kubeProxyReplacement=disabled and the errors displayed by the cilium-agent on startup went away.


Server Action in a loop can't pass data

Is your feature request related to a problem? Please describe.
When you do a loop
{response.data
  .map((booking) => (
    <button onClick={(e) => doSomething(e, booking.id)}>lala</button>
))}

booking.id will throw an error because it does not exist on the client and the server bookind.id will be undefined.
The very unique way to solve this is injecting a data attr and use dataset to retreive the data on the server.
{response.data
  .map((booking) => (
    <button data-lala={booking.id} onClick={doSomething}>lala</button>
))}

// then e.currentTarget.dataset.lala will have the info

This is working and is a valid approach, but maybe we could document this or give a better way to handle this situation.

@AlbertSabate is already documented https://brisa.build/building-your-application/data-management/server-actions#using-data-attributes

btw; improve any kind of documentation is always very welcome as a contribution

Ohh nice, I saw the commit https://github.com/brisa-build/brisa/commit/b66b39ba9d4f16b98fd17d3fa8177d21f3eab18b
@aralroca so fast adding docs haha
Let's keep it open for now, maybe someone can improve the examples? If there is no volunteers I'll get more examples there :)
Thank you!!

I am closing the issue since it has been documented. Any PR improving documentation is welcome but you don't need to have an open issue for it.


For Media SDK 19.4.0, actual bitrate is a little higher than target bitrate when la

I tested Media SDK 19.4.0 recently and find that the actual bitrate is a little higher than target bitrate. Media SDK 16.9(2018 R2) is OK.
command:
ffmpeg -init_hw_device "qsv=hw" -filter_hw_device hw -f rawvideo -s 1920x1080 -pix_fmt yuv420p -r 30 -i chiji_Ad24DdIRwHI_60s.264.yuv -vf hwupload -c:v h264_qsv -preset:v veryslow -b:v 5000k -maxrate:v 6000.0k -bufsize:v 5000k -look_ahead 1 -look_ahead_depth 30 -no-scenecut 1 -g 90 -bf 3 -an -f h264 -y chiji_Ad24DdIRwHI_60s.h264
which print:
`[AVHWDeviceContext @ 0x23f8d00] Unknown driver "Intel iHD driver - 19.4.0", assuming standard behaviour.
[h264_qsv @ 0x23fbce0] Using the VBR with lookahead (LA) ratecontrol method
[h264_qsv @ 0x23fbce0] MFMode:2
[AVHWDeviceContext @ 0x25784e0] Unknown driver "Intel iHD driver - 19.4.0", assuming standard behaviour.

Hi @YaboWei ,
Can you please prepare a reproducer with sample_encode?

@dmitryermilov Sorry for my late reply.
sudo ./MediaStack/opt/intel/mediasdk/share/mfx/samples/_bin/sample_encode h264 -i ~/chiji_Ad24DdIRwHI_60s.yuv -o a.264 -w 1920 -h 1080 -r 30 -g 90 -la -lad 30 -b 5000 -u veryslow
outputs:
`libva info: VA-API version 1.6.0
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
Encoding Sample Version 19.4.0
Input file format	YUV420
Output video		AVC
Source picture:
Resolution	1920x1088
Crop X,Y,W,H	0,0,1920,1080
Destination picture:
Resolution	1920x1088
Crop X,Y,W,H	0,0,1920,1080
Frame rate	30.00
Bit rate(Kbps)	5000
Gop size	90
Ref dist	30
Ref number	0
Idr Interval	0
Target usage	quality
Memory type	system
Media SDK impl		hw
Media SDK version	1.31
Processing started
Frame number: 1801
Encoding fps: 182
Processing finished
$ ll a.264
-rw-rw-r-- 1 web_server web_server 39493591 Apr 13 22:49 a.264
`
calculate bitrate in kbps:
39493591*8 / (1801/30.0) / 1000 = 5262.8

Hi @YaboWei ,
Can you please prepare a reproducer with sample_encode?

@dmitryermilov Sorry for my late reply.
sudo ./MediaStack/opt/intel/mediasdk/share/mfx/samples/_bin/sample_encode h264 -i ~/chiji_Ad24DdIRwHI_60s.yuv -o a.264 -w 1920 -h 1080 -r 30 -g 90 -la -lad 30 -b 5000 -u veryslow
outputs:
`libva info: VA-API version 1.6.0
libva info: Trying to open /opt/intel/mediasdk/lib64/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_6
libva info: va_openDriver() returns 0
Encoding Sample Version 19.4.0
Input file format YUV420
Output video AVC
Source picture:
Resolution 1920x1088
Crop X,Y,W,H 0,0,1920,1080
Destination picture:
Resolution 1920x1088
Crop X,Y,W,H 0,0,1920,1080
Frame rate 30.00
Bit rate(Kbps) 5000
Gop size 90
Ref dist 30
Ref number 0
Idr Interval 0
Target usage quality
Memory type system
Media SDK impl hw
Media SDK version 1.31
Processing started
Frame number: 1801
Encoding fps: 182
Processing finished
$ ll a.264
-rw-rw-r-- 1 web_server web_server 39493591 Apr 13 22:49 a.264
`
calculate bitrate in kbps:
39493591*8 / (1801/30.0) / 1000 = 5262.8

@dmitryermilov please check my sample_encode result, thanks!

Hi, @YaboWei
In your line for sample_encode -r should be replaced with -f, as -r is for GOP distance and -f for frame rate.
I investigated your issue. In all cases where bitrate is higher with lookahead option it is no more than 10%. According to developer encoding algorithms checks that bitrate is no more than 10% higher than requested.

Hi, @YaboWei
In your line for sample_encode -r should be replaced with -f, as -r is for GOP distance and -f for frame rate.
I investigated your issue. In all cases where bitrate is higher with lookahead option it is no more than 10%. According to developer encoding algorithms checks that bitrate is no more than 10% higher than requested.

Hi, @filippenkos
I tried command:
/opt/intel/mediasdk/share/mfx/samples/_bin/sample_encode h264 -i chiji_Ad24DdIRwHI_60s.yuv -o a.264 -w 1920 -h 1080 -f 30 -g 90 -b 5000 -la -lad 30 -u veryslow
and the bitrate is 39584622*8 / (1801/30.0) / 1000 = 5275

Hi @YaboWei
As I mentioned encoding algorithms checks that bitrate is no more than 10% higher than requested.  In your case bitrate is higher than requested by 5,5%. So this result is not an issue.


Outdated

This guide is outdated with regards to current Azure portal

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

ID: dd3afb20-4404-d9df-79e6-dde3c6ac6759
Version Independent ID: 0eac06e5-8280-4009-f06d-3feff1049e45
Content: Enable Remote Desktop Connection for a Role in Azure Cloud Services
Content Source: articles/cloud-services/cloud-services-role-enable-remote-desktop-new-portal.md
Service: cloud-services
GitHub Login: @mmccrory
Microsoft Alias: mmccrory

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Screenshot needs to be updated.
Assigning back to @mmccrory.

#reassign: @MicahMcKittrick-MSFT

We are currently cleaning up old issues and closing out items that are greater than 90 days old. If an issue is still present, please open a new feedback item on the document so we can prioritize correctly.
#please-close


[5-02] As the system, I want to automatically generate and send invoices once a membership is approved

As the system, I want to automatically generate and send invoices once a membership is approved
Estimation: 6 hours

[ ]     The document that is generated is public. Meaning anyone with the link can access the invoice . Better to make it private and only accessible to user, exec and coordinator roles.
[ ]     If you lose the email there is no way easy way to access the invoice. Be good to have a link to it somewhere. Maybe an invoice section for the signup application.
[ ]     The details on the invoice are from the home tab. Probably best to use the work details tab. We could have another ticket for the applicant to choose which details to be used for invoice (home or work)
[ ]     The dollar sign after the number looks a bit weird. Maybe have the $ then the number in the invoice
[ ] Update invoice to look similar to current Xero invoice


Can't bind to 'columns' since it isn't a known property of 'dx-data-grid'.

When I add a devextreme widget I got the follow errors:

VM23187:27 Unhandled Promise rejection: Template parse errors:
Can't bind to 'columns' since it isn't a known property of 'dx-data-grid'.

If 'dx-data-grid' is an Angular component and it has 'columns' input, then verify that it is part of this module.
If 'dx-data-grid' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.
("

<dx-data-grid
[ERROR ->][columns]='[
"FullName"
]'
"): EmployeesList@16:4
Can't bind to 'dataSource' since it isn't a known property of 'dx-data-grid'.

If 'dx-data-grid' is an Angular component and it has 'dataSource' input, then verify that it is part of this module.
If 'dx-data-grid' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.......`

I got this error with all widget, I try to add a button but it doesn't work.

`Can't bind to 'text' since it isn't a known property of 'dx-button'.

If 'dx-button' is an Angular component and it has 'text' input, then verify that it is part of this module.
If 'dx-button' is a Web Component then add "CUSTOM_ELEMENTS_SCHEMA" to the<EMAIL_ADDRESS>of this component to suppress this message.

I using webpack and Angular 2.2.3.
How can I fix this?

Hello @Freez
I suppose that you need to add a DevExtremeModule to imports of your root module. To find the real cause of this error, please provide an example, what demonstrate this behavior. You can use our plunker template for this.


Loading local images provides high performance memory cache support, while loading network images provides memory and local secondary cache support, such as image loading provides properties MemoryCache: true, localCaahe: true, Instead of using third-party libraries.

Loading local images provides high performance memory cache support, while loading network images provides memory and local secondary cache support, such as image loading provides properties
MemoryCache: true, localCaahe: true,
Instead of using third-party libraries.

Hi @gionchat
can you describe the issue or the proposal more in details?
thank you

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so its always better to open new issues and reference related issues.


Map: My location button takes me to my location twice when I press it twice

Description of issue
On Android:

Go to parade map and click on location button.
Before it takes you your location, click it again.
Wait until it takes you to your location and move away.
It will now take you to your location again.

Possibile cause:
Every click on the "my location" button seems to trigger a call to the location service. On Android it can take a few seconds to receive the location. Once it gets it, it moves the map. In between you can still move the map to anywhere you want, though.
Expected behaviour

It should only ask the location service once. When I click the button again and it didn't receive something from the last call, don't call again.
If the users moves the map while we retrieve the location, we should not go to the users location anymore??

OS / Browser / Device model
Most visible on Android.
Screenshots
If it's a visual bug, please provide screenshots or screen captures.

I will be looking into this along with #503 and #502.


Unit Test templates for .NET Core not referencing latest stable version of MSTest

Description
Unit test templates for .NET Core 2.0 do not use MSTest.Adapter and MSTest.TestFramework 1.1.18 (latest stable) and uses 1.1.17 instead. This is inconsistent with what is used with test templates for .NET, which correctly uses 1.1.18. Also we know that when latest stable is not present, features that are built on top of this (e.g LUT) could run into issues depending on the bug fixes that went into 1.1.18
Steps to reproduce
Install VS 2017 version 15.3 and .NET Core 2.0 SDK.
File->New->Test and pick a .NET Core Unit Test template
Expected behavior
Should reference MSTest.TestFramework & MSTest.TestAdapter version 1.1.18 (latest stable) and manage NuGet packages UI should not show updates available immediately after File->New
Actual behavior
Shows references to MSTest.TestFramework MSTest.TestAdapter version 1.1.17 and manage NuGet packages UI shows updates available for version 1.1.18

https://github.com/dotnet/templating/pull/1155

Also we know that when latest stable is not present, features that are built on top of this (e.g LUT) could run into issues depending on the bug fixes that went into 1.1.18

@morrisjoe : Can you please help us with such a scenario? This is not expected to break. Customers running LUT on earlier stable VS builds would run into issues then and that is a concern.

@morrisjoe: gently pinging back.

This is fixed since VS 15.4.


Detect Bluetooth support

https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetooth_API
Object.keys(Object.getOwnPropertyDescriptors(window)).filter(key => /Bluetooth/.test(key))
/*
0: "Bluetooth"
1: "BluetoothCharacteristicProperties"
2: "BluetoothDevice"
3: "BluetoothRemoteGATTCharacteristic"
4: "BluetoothRemoteGATTDescriptor"
5: "BluetoothRemoteGATTServer"
6: "BluetoothRemoteGATTService"
7: "BluetoothUUID"
*/
'bluetooth' in navigator

There's the following check which requires no permission (works on HTTPS only):
await navigator.bluetooth.getAvailability()


fix(ui): reintroduce portal-based Modal stories

Summary
reintroduce portal-based Modal stories
Changes Made

reintroduce portal-based Modal stories

Related Issues

Issue 1: [https://github.com/cloudoperators/juno/issues/520]

Testing Instructions

npm i
npm run storybook

Checklist

[ ] I have performed a self-review of my code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have made corresponding changes to the documentation (if applicable).
[ ] My changes generate no new warnings or errors.

@barsukov, @guoda-puidokaite, @andypf Would you be able to review this PR?


Fixes inconsistencies in names

This commit addresses an issue where one of the strings starting with "endif" was inconsistent, with only one of them starting with an uppercase letter. To maintain code consistency, it was changed to lowercase.

See my comment on your first PR, this is not where these changes are made, see here


[WSL2] F5 VPN breaks network connectivity

Version
Microsoft Windows [Version 10.0.19044.1288]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
5.10.16
Distro Version
Ubuntu-22.04
Other Software
F5 Edge VPN Client
Repro Steps

Logon to f5 VPN
Start the WSL
Do a curl to curl www.google.com

As per f5 knowledge article, we have to launch the WSL2 once we are on VPN, but it does not work.  FYI: I do not have admin rights on the windows 10.
Expected Behavior
network connectivity should work from WSL 2
Actual Behavior
network connectivity is not working from WSL 2
Diagnostic Logs
No response

I have also tried these steps, but it's not resolving the issue.

I tried wsl-vpnkit and it worked

Same issue using the Azure VPN client where the remote VNET has conflicting IP routes with the WSL2 ethernet

Same here


Fixes issue #627

Actually, problem was  that the output class file was created in  destination address within a python
sub-folder.
It was due to the initial value of namespace  i.e  python . Which further joins the python sub-folder in
dirname address  .

ping @eliasdorneles

I just restarted the build as it was stuck on the smoke test job – it's now completed, but with a bunch of errors.

I'm closing this since it doesn't really fix the issue, feel free to reopen if you decide to work on it again. Thanks!


Num observations react hook

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding. Failure to do so may result in the rejection of the pull request.
Do not change the following line aside from replacing YOUR-ISSUE-HERE with the issue this PR fixes
fixes #413
Please provide enough information so that others can review your pull request:
Created a custom hook allowing numObservations to be accessed from other components without using higher-order components.
Explain the details for making this change. What existing problem does the pull request solve?
numObservations before was only accessible to the DiagnosticContainer component.
Test plan (required)
Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes UI.

Final Checklist

[X] Have you bumped the version in package.json?

Second decimal for major change, third decimal for minor change. This can go past 10 i.e. 1.0.9 !=> 1.1.0, 1.0.9 => 1.0.10
Read here for more info

[ ] Have you added any new tests necessary?
[X ] Is your PR rebased off the most current master?
[X] Have you squashed all commits, or if you will merge will you squash all commits?
[X] Did you use yarn, not npm?
[ ] Did you use Material-UI wherever possible?
[ ] Did you format according to Prettier?
[X] Did you run all of your most recent changes locally to make sure everything is working?

I made a mistake when I was trying to combine commits sorry there shouldn't have been that many file changes.


Remove conditional accesses on unity objects

looks good. did you test it?

closing this for now.
please reopen after testing.


GLIBC version requerd

I update the tool to the latest version and i have this issues,
katana: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.32' not found (required by katana) katana: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34' not found (required by katana)

For solution please refer to https://github.com/projectdiscovery/katana/issues/678. Closing this.


segfault on compile_pymc_model

compiled_model = nutpie.compile_pymc_model(pymc_model)

crashes the kernel

Oh well, that's almost supposed to happen...
Can you share the model?
Strangely enough this is even before any of the rust code is involved, so this might be a numba or aesara issue.
There should also be a conda package pretty soon: https://github.com/conda-forge/staged-recipes/pull/19354
Maybe that is worth trying as well.

---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
Input In [3], in <cell line: 1>()
----> 1 import nutpie.lib; nutpie.lib.PySamplerArgs()

ModuleNotFoundError: No module named 'nutpie.lib'

@twiecki The PR in the conda feedstock that enables the osx amd64 builds is merged, so the new packages should be available pretty soon. Could you try to install those then and see if you still see the segfault?

I don't get a segfault anymore:

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
File <timed exec>:2, in <module>

File ~/miniforge3/envs/pymc4/lib/python3.10/site-packages/nutpie/compile_pymc.py:38, in compile_pymc_model(model, **kwargs)
     36 def compile_pymc_model(model, **kwargs):
     37     """Compile necessary functions for sampling a pymc model."""
---> 38     n_dim, logp_func, expanding_function, shape_info = _make_functions(model)
     39     logp_func = numba.njit(**kwargs)(logp_func)
     40     logp_numba_raw, c_sig = _make_c_logp_func(n_dim, logp_func)

File ~/miniforge3/envs/pymc4/lib/python3.10/site-packages/nutpie/compile_pymc.py:125, in _make_functions(model)
    120 # We should avoid compiling the function, and optimize only
    121 func = aesara.function(
    122     (joined,), (logp, grad), givens=symbolic_sliced, mode=aesara.compile.NUMBA
    123 )
--> 125 logp_func = func.vm.jit_fn.py_func
    127 # Make function that computes remaining variables for the trace
    128 trace_vars = {
    129     name: var
    130     for (name, var) in model.named_vars.items()
    131     if var not in model.observed_RVs + model.potentials
    132 }

AttributeError: 'Function' object has no attribute 'vm'

I guess I'm missing a lower version requirement for aesara in the package...
About the segfault:
I can see two ways to debug this further:

Get a coredump to see in what function the segfault occurs.
Run the code section by section, or run equivalent code to figure out where it happens.

So something like this:
Does it happen with all models?
with pm.Model() as pymc_model:
    pm.Normal("a")

compiled = nutpie.compile_pymc_model(model)

Or compile the logp function in numba mode:
with pm.Model() as model:
    pm.Normal("a")

# With a model where compilation segfaults
logp = model.logp()
point = model.initial_point()
func = aesara.function(model.value_vars, logp, mode="NUMBA")
func(**point)
func_grad = aesara.function(model.value_vars, [logp] + at.grad(logp, model.value_vars), mode="NUMBA")
func_grad(**point)

# For the model with one var:
numba_func = func.vm.jit_fn

@numba.cfunc(numba.types.float64(numba.types.float64))
def logp_cfunc(a):
    out = numba_func(a)[0]
    return out

Does numba work in general?
@numba.njit()
def foo(x):
    return np.exp(x)

foo(0.1)

@numba.cfunc(numba.types.float64(numba.types.float64))
def bar(x):
    return foo(x)

The first one segfaults, the other ones are fine.

Does nutpie.compile_pymc._make_functions(simple_model) segfault?

No.

So unless I misunderstand something, one of those lines has to segfault, which?
n_dim, logp_func, expanding_function, shape_info = nutpie.compile_pymc._make_functions(model)
logp_func = numba.njit(**kwargs)(logp_func)
logp_numba_raw, c_sig = nutpie.compile_pymc._make_c_logp_func(n_dim, logp_func)
logp_numba = numba.cfunc(c_sig, **kwargs)(logp_numba_raw)

logp_numba = numba.cfunc(c_sig)(logp_numba_raw)

This one.

Ok, next one (sorry for the piece by piece info, but I don't have a lot of other ideas than going through it step by step)
import pymc as pm
import numba
import aesara.tensor as at

with pm.Model() as model:
    var = pm.Normal("a")

joined = at.dvector("__joined_variables")

value_vars = [model.rvs_to_values[var]]

logp = model.logp()
grads = at.grad(logp, value_vars)
grad = at.concatenate([grad.ravel() for grad in grads])

num_free_vars = 1

func = aesara.function(
    (joined,), (logp, grad), givens=[(value_vars[0], joined[:].reshape(()))], mode=aesara.compile.NUMBA
)

logp_func = func.vm.jit_fn.py_func

logp_func_numba = numba.njit()(logp_func)

N = 1

c_sig = numba.types.int64(
    numba.types.uint64,
    numba.types.CPointer(numba.types.double),
    numba.types.CPointer(numba.types.double),
    numba.types.CPointer(numba.types.double),
    numba.types.voidptr,
)

def logp_numba(dim, x_, out_, logp_, user_data_):
    try:
        x = numba.carray(x_, (N,))
        out = numba.carray(out_, (N,))
        logp = numba.carray(logp_, ())

        logp_val, grad = logp_func_numba(x)
        logp[()] = logp_val
        out[...] = grad

        if not np.all(np.isfinite(out)):
            return 2
        if not np.isfinite(logp_val):
            return 3
        if np.any(out == 0):
            return 4
    except Exception:
        return 1
    return 0

numba.cfunc(c_sig)(logp_numba)

I'd expect this to segfault on the last line, based on what we figured out so far...

I'd expect this to segfault on the last line, based on what we figured out so far...

Correct.

Ok, so we got rid of all the nutpie code, just pymc, aesara and numba left ;-)
Let's get rid of pymc and simplify the final function a bit:
import aesara.tensor as at
import numba

var = at.dscalar("a")
logp = -var ** 2

joined = at.dvector("__joined_variables")

grads = at.grad(logp, [var])
grad = at.concatenate([grad.ravel() for grad in grads])

func = aesara.function(
    (joined,), (logp, grad), givens=[(var, joined[:].reshape(()))], mode=aesara.compile.NUMBA
)

logp_func = func.vm.jit_fn.py_func

logp_func_numba = numba.njit()(logp_func)

N = 1

c_sig = numba.types.int64(
    numba.types.uint64,
    numba.types.CPointer(numba.types.double),
    numba.types.CPointer(numba.types.double),
    numba.types.CPointer(numba.types.double),
    numba.types.voidptr,
)

def logp_numba(dim, x_, out_, logp_, user_data_):
    x = numba.carray(x_, (N,))
    out = numba.carray(out_, (N,))
    logp = numba.carray(logp_, ())

    logp_val, grad = logp_func_numba(x)
    logp[()] = logp_val
    out[...] = grad
    return 0

numba.cfunc(c_sig)(logp_numba)

Still a segfault?

Opened an issue here: https://github.com/aesara-devs/aesara/issues/1023

Closing as fixed with a workaround in aesara


typora: 0.9.73 -> 0.9.89

Motivation for this change
The package is currently broken due to the 404-ed URL.
This PR bumps the version and fixes the build.
Fixes #91838, fixes #89482 and fixes #76249.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)

558.5MiB (~220MiB from itself)

[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Is this an issue on stable? That means we'd need to backport. I'm assuming it is since the url 404d.

@worldofpeace Yes, it's also broken on stable channels.
I should backport it to release-20.03, right?


docker-collectd-plugin

We have noticed the following error logged in /var/log/syslog.
collectd[11566]: Failed to open types database `/usr/share/collectd/docker-collectd-plugin/dockerplugin.db': No such file or directory

This error appears on instances that have collectd  and
Docker installed. This is visible on instances that belong to docker_management.

The initial change was introduced by https://github.com/alphagov/govuk-puppet/commit/ae7468e0a0d5caad56363e316eb6bb972b923e7b#diff-8f1f4c9a523ffbaf50a9977a99bfe92d

pip doesn't install docker-collectd-plugin. Hence, we have taken the
content from https://github.com/lebauce/docker-collectd-plugin.

This issue was noticed when a new graphite instance was created in the
integration environment and null data was recorded.

Pair: @kevindew @suthagarht

Instead of copying the docker-collectd-plugin into govuk-puppet which we now have to maintain and keep up to date, could we not just clone the repo into /usr/share/collectd/docker-collectd-plugin? We could pin to a specific commit to make sure it doesn't break underneath us?

Hi @thomasleese ,
Thank you. That sounds great. I will try this.
Thank You
SK


timestamp_field error with unix type.

ERROR:root:Error running query: TransportError(400, u'search_phase_execution_exception', u'failed to parse date
 field [1.496638310584814E9] with format [epoch_second]')

How can i solve it?

I think this is an Elasticsearch issue: https://github.com/elastic/elasticsearch/issues/21489
See discussion from https://github.com/Yelp/elastalert/issues/996
I'm not actually sure how to solve it

Closing as duplicate of #996


Make NF4Tensor constructible from different dtypes

Summary
This doesnt work today because transpose is doing some dtype shennagins

Failures
========================================================================================================= short test summary info =========================================================================================================
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_output_dtype_match[dtype0] - RuntimeError: "copy_" not implemented for 'Bits2x4'
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_backward_dtype_match[dtype0] - RuntimeError: "copy_" not implemented for 'Bits2x4'
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_nf4_bnb_linear[dtype0] - RuntimeError: copy_() does not support casting bits types to different bits types. Source dtype is BFloat16target dtype is Bits2x4
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_to_bfloat16 - AssertionError: assert <class 'torchao.dtypes.nf4tensor.NF4Tensor'> == <class 'torch.Tensor'>
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear[dtype0] - RuntimeError: copy_() does not support casting bits types to different bits types. Source dtype is BFloat16target dtype is Bits2x4
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear[dtype1] - RuntimeError: copy_() does not support casting bits types to different bits types. Source dtype is BFloat16target dtype is Bits2x4
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear[dtype2] - RuntimeError: copy_() does not support casting bits types to different bits types. Source dtype is BFloat16target dtype is Bits2x4
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear_compile[dtype0] - torch._dynamo.exc.TorchRuntimeError: Failed running call_function <built-in function linear>(*(FakeTensor(..., device='cuda:0', size=(2, 32, 32), dtype=torch.bfloat16), Quantized Data: FakeTensor(..., device='cuda:0', size=(512,),...
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear_compile[dtype1] - torch._dynamo.exc.TorchRuntimeError: Failed running call_function <built-in function linear>(*(FakeTensor(..., device='cuda:0', size=(2, 32, 32), dtype=torch.float16), Quantized Data: FakeTensor(..., device='cuda:0', size=(512,), ...
FAILED test/dtypes/test_nf4.py::TestNF4Linear::test_smoketest_linear_compile[dtype2] - torch._dynamo.exc.TorchRuntimeError: Failed running call_function <built-in function linear>(*(FakeTensor(..., device='cuda:0', size=(2, 32, 32)), Quantized Data: FakeTensor(..., device='cuda:0', size=(512,), dtype=torch.uint8)
================================================================================================ 10 failed, 22 passed, 3 warnings in 9.22s ================================================================================================

Thanks for sending this!


Allow specifying configurations for each logger

Dropwizard doesn't have the ability to specify configurations for individual loggers yet. With this patch user can do something like this:
logging:
  level: INFO
  loggers:
    wego.curiosity:
      level: DEBUG
      appenders:
        - type: console
          target: stdout
          logFormat: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{16} - %msg%n"
          ...
  appenders:
    - type: file
     ...
    - type: console
      target: stdout
      logFormat: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{16} - %msg%n"
    - type: loggly
    ...

+1

do you think specifying debug level per appender per logger would be useful? I think it might be a bit overkill....

I would just like to have the logger reference appenders by name, as they could if logback were configured via xml or groovy. Really, I would just like the yml configuration to have feature parity with the xml configuration.

+1
Being able to configure different loggers to log to different files is really important for many applications.

alright so this looks okay? How do I proceed? Thanks.

Sorry for the delay. I will take look at this today.

Thanks for taking your time to implement this feature. Some observations, before we can proceed further:

Please, follow Dropwizard Contributing Guide in your contribution.
Rebase your change against master branch. It's not mergeable now.
Don't change spaces to tabs in the whole file. Dealing with different indentations across the project is a nightmare. Make your change focused.
Add some tests to verify that your change works and doesn't break anything. As far as I can tell, the proposed implementation is not comptatibe with the current logger configuration format:

logging:
  level: INFO
  loggers:
    "com.example.app": DEBUG

@arteam thanks for you input. I'm gonna update my code :+1:

@arteam added tests and changed code styling

@wakandan You probably misunderstaned me.
People who use the current format
logging:
  level: INFO
  loggers:
    "com.example.app": DEBUG

should not update their configuration to
logging:
  level: INFO
  loggers:
    "com.example.app":
        level: DEBUG

I don't think we could change the format of the field loggers at all, unless we must to.
I would more think about adding other field like advancedLoggers, that would override loggers, if it's present.

@arteam aaaahhhh. I understood now, never thought of that. Okay I will update my code :+1:

@arteam I modified the code as you requested. "advancedLoggers" key can be read from the configuration file and it will override settings from "loggers" key. Please review. Thanks :+1:

advancedLoggers feels like a bit of a wart on the side of the configuration.
What if we extended the appenders, instead? Provide them with a "loggers" list property consisting of the loggers that should write to that appender. Default the list of loggers to all loggers. That would be backwards compatible and provide the intended functionality.
logging:
  level: INFO
  loggers:
    wego.curiosity: DEBUG
  appenders:
    - type: file
      loggers: [wego.curiosity]
     ...
    - type: console
      target: stdout
      logFormat: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{16} - %msg%n"

I'm happier with Ryan's approach, tbh.
On Wed, Jun 24, 2015 at 11:57 AM Ryan Kennedy<EMAIL_ADDRESS>wrote:

advancedLoggers feels like a bit of a wart on the side of the
configuration.
What if we extended the appenders, instead? Provide them with a "loggers"
list property consisting of the loggers that should write to that appender.
Default the list of loggers to all loggers. That would be backwards
compatible and provide the intended functionality.
logging:
level: INFO
loggers:
wego.curiosity: DEBUG
appenders:
- type: file
loggers: [wego.curiosity]
...
- type: console
target: stdout
logFormat: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{16} - %msg%n"
—
Reply to this email directly or view it on GitHub
https://github.com/dropwizard/dropwizard/pull/1092#issuecomment-114924378
.

Probably is not good enough, if we, for example, want to log wego.curiosity to a separate file.
Moreover, it seems wrong to me that appenders know about loggers. I always thought about them as entities that control where and how to log, but not what to log.

Why isn't it good enough to log wego.curiosity to a separate file? Create an appender for that file and add wego.curiosity to the loggers list for it. If the concern is that it would still be logging to the other appenders, we could have includedLoggers (defaulted to all loggers) and excludedLoggers (defaulted to no loggers) for each appender.
To play the other side of the coin, what if you want to log wego.curiosity and yougo.curiosity to the same file? Will you spec the appender twice (once for each logger)?
As for appenders knowing about loggers, I'm only talking about the relationship between loggers and appenders is configured. How the loggers get hooked up to appenders under the hood is (in my mind) separate from how the relationship gets configured in the YAML file.

I have an idea to make the configuration more dynamic, so we can permit objects with different types for keys. For example:
level: INFO
loggers:
  "com.example.app": DEBUG
  "wego.curiosity":
      level: DEBUG
      appenders:
        - type: console
          target: stdout
          logFormat: "%d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{16} - %msg%n"

To map this to Java we need to change the type of the loggers field to ImmutableMap<String, JsonNode>. And then make a type check in runtime something like that:
for (Map.Entry<String, JsonNode> entry : loggers.entrySet()) {
    Logger logger = loggerContext.getLogger(entry.getKey());

    JsonNode jsonNode = entry.getValue();
    if (jsonNode.isTextual()) {
        // Just a level as a string
        Level level = Level.valueOf(jsonNode.asText());
        logger.setLevel(level);
    } else if (jsonNode.isObject()) {
        // Level and appender
        LoggerConfiguration configuration;
        try {
            configuration = Jackson.newObjectMapper().treeToValue(jsonNode, LoggerConfiguration.class);
        } catch (JsonProcessingException e) {
            throw new IllegalArgumentException("Wrong format of logger '" + entry.getKey() + "'", e);
        }
        logger.setLevel(configuration.getLevel());
        for (AppenderFactory appender : configuration.getAppenders()) {
            logger.addAppender(appender.build(loggerContext, name, null));
        }
    } else {
        throw new IllegalArgumentException("Unsupported format of logger '" + entry.getKey() + "'");
    }
}

Thoughts?

I like Ryan's idea. I also like @arteam's idea, though I don't think it makes sense to define appenders inline with the logger like that. I'd rather just let the appender have a name and let the 'advanced' logger configuration syntax reference the appender by name (much the same as a conventional logback.xml would do).

I still think putting appenders in the loggers will lead to appenders being spec'd repeatedly and in multiple locations. I think either have the loggers refer to the appenders by name (something we don't have today…an appender name) that they want to be a part of or have appenders refer to the loggers they'll handle output for. Appenders are already an object, so the code change is minimal. Loggers would require either breaking compatibility (switch from level to an object); adding a new loggers property (the advancedLoggers suggestion), which I think looks wart-ish; or make loggers polymorphic, which I think impacts readability of the code (I refer to configuration classes often when I'm trying to figure out how to configure a thing…JsonNode isn't self-documenting).
My preference is to add the loggers list to the appenders because it requires the smallest change to the code/configuration format and because it avoids duplicating appender configuration and avoids having appenders configured in multiple locations.

Would it be so terrible to change the configuration syntax?
Failing that, if the appenders reference loggers (which is reversed from logback configuration files), how would additivity be configured?

In case the default cumulative behavior turns out to be unsuitable for your needs, you can override it by setting the additivity flag to false. Thus, a branch in your logger tree may direct output to a set of appenders different from those of the rest of the tree.
http://logback.qos.ch/manual/configuration.html

For example, some loggers should log to all appenders, while other loggers should log to only one appender.

Something else to consider is that one could roll their own logger factory which reads from a provided logback.xml. This way we keep the current logging configuration simple and in yaml, which probably satisfies most users. If you really want complex configuration, then you have a way. My 2cs.

@carlo-rtr 's idea is actually not bad. I was thinking about doing the same thing since we have some logback configuration file. One thing the old-fashioned xml logback might be good for is that they can do scanning for changes in the xml file (during runtime, and reload config), which is very very handy for debugging in production.
@ryankennedy 's approach seems nice for both readability & backward compatibility. Should we proceed with that?

Sorry, but I have a firm opinion that we should not configure loggers in appenders.
Despite that it's easy to implement, such configuration is not conventional and not obvious for users. The polymorphic solution seems to me as the lesser of two evils.
@dropwizard/committers, what is your opinion on this?

I think I like Carlo's idea of the logback.xml/groovy configuration. The YAML configuration should satisfy 95% of all use cases. In 5% of the use cases there should be an alternative mechansim to achieving the desired result (logback.xml). Dropwizard can't and shouldn't support all logging fantasies in the YAML. For instance, logback supports automatically scanning the file for changes and applying them. In my opinion, if someone wanted this in Dropwizard, they should be expected to into the logback.xml to configure it.
Since creating an uber jar messes with the class path, one can use logback.xml by invoking:
java -Dlogback.configurationFile=logback.xml -jar <jarfile> server config.yaml

However, one can't currently use this approach as all the configured appenders in logback.xml are killed on bootup by the following code:
final Logger root = LoggingUtil.getLoggerContext().getLogger(org.slf4j.Logger.ROOT_LOGGER_NAME);
root.detachAndStopAllAppenders();

I can't say why this is done (it's been this way for more than a couple of years). But I feel like maybe the optimal solution would be for logback.xml and the yaml to complement each other.
The next question, if this pull request should be in the 95% use case, from a user standpoint, I like Artem's solution of ImmutableMap<String, JsonNode> for the different type of keys. From a user point of view, everything is localized in the configuration.

@nickbabcock The code you are referring to is in BootstrapLogging.bootstrap, which is called in the default constructor of Application. If someone rolls their own logger factory, then they just need to override the default constructor for the subclass of Application, and not call bootstrap.

...so is there a consensus approach for this? I'm still interested in pushing for this feature if possible

@wakandan, sorry for sitting on this so long.
I think we should proceed with the approach proposed in 115012595. It's less controversial than 114924378 and shouldn't be very hard to implement.

alright @arteam I will check that. Thanks for your comments :+1:

@arteam updated

Thanks for your work on this, @wakandan!
Applied the patch to master with some improvements.

thanks! :+1:


GNU Nano fails to install

Describe the bug
Nano Installs an additional APT package which do not exist. This package 'auto' is not in PKGBUILD oddly also.
To Reproduce
Steps to reproduce the behavior:

Install Pacstall
Install Nano by: pacstall -I nano
Notice that installation fails because of trying to install package auto which does not exist.

Expected behavior
Nano fails to install because of nonexistent package.
Screenshots

Desktop (please complete the following information):

OS: Ubuntu
Version: 20.04.3 LTS

I can't reproduce this on my Pop!_OS machine, it only asks to install groff & texinfo here.

@Henryws, can you test this in a docker container of Ubuntu 20.04 LTS.

Tried this on Debian Sid in a VM and it to had this issue:

Can you view the pacscript during install?

Here's what nano's PKGBUILD looks like from vim tiny:

And as you can see auto is not in the depends either oddly.

I'm unable to produce this. Hmm

It's this substititution's fault

Why is this an issue on @cat-master21's machine but no one elses?

automake is not installed but make is

Welp, schedule it for 2.0.0

There is an easy fix tho

This behavior will not be present in v2.0

Yes, manually installing Automake fixed this issue fortunately for me.


Introduce Error::is_header_section_too_large (fixes #2462)

We rename Parse::TooLarge into Parse::HeaderSectionTooLarge while at it.

Superseded by #2504.


Fix dependabot alerts

This PR fixes https://github.com/microsoft/azuredatastudio/security/dependabot/671 and https://github.com/microsoft/azuredatastudio/security/dependabot/670

Looks like there was a breaking change in the version bump, causing the compilation failure. I think this package is just used for adding the port request labels, so it should be ok to comment out the places with errors if the fix isn't very obvious, then fix those in a separate PR to unblock the builds sooner.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 41.76%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
30828

Relevant Lines:
69082

💛  - Coveralls

@kisantia, @Charles-Gagnon, @alanrenmsft The PR looks good to go now from my end. Can you take a pass on this, so that the builds can go through? Thanks!


OnClick / Style ... Forced erroring

The following code:
    templ OnClick(onclick string, icon string, title string, name string) {
	<button class="button2" type="button" onclick={ onclick } title={ title }>

Errors: "cannot use onclick (variable of type string) as templ.ComponentScript value in variable declaration"

Let me be clear on this: There is no possible injection or other attack vector, this is pure esthetic sub template function, that we recently introduced to unify some of our html code.
Style has the same issue...
Errors:  "invalid style attribute: style attributes cannot be a templ expression"

The fact that basic functionality is being blocked, is (long time) peeing off our developers. We had the same issue with style needed convoluted ways around it and wasting hours of time.
Using  templ.ComponentScrip does not work for use as we do not run any javascript from our html snippets (direct parse and not eval injections). These things need to be optional, not forced! If we want to use onclick directly with a string provided function definition, that is our choice. If we want a custom style, without falling back to classes, that is our choice.
The documentation is starting to get loaded with entire pages of "no, you can not do that, but here is a alternative forced way to get the same thing".  For all the nice things of Templ, we are starting to look at other templating engines again, simply because of these "features".
To quote one of our devs: "its a freaking template engine, not my mother" ...

I think you may have written this while being frustrated, since it's not particularly constructive. If you have a team of developers using templ, perhaps you could have put together a more detailed proposal of how to improve script and CSS handling?
Go's built-in html/template forces you to use the type template.JS to identify safe JavaScript strings. If you use a standard string for a JS attribute, you don't get a compile error, you get a silent failure at runtime. Copy the output of this program into a HTML file, and you'll see what I'm talking about: https://go.dev/play/p/G_ts4C2g7nl
One of the goals of templ is to bring errors up early. Compile time errors are better than runtime errors, and are a lot better than silently not doing what you might reasonably expect.
Putting that aside, I think that what you're asking for is a way to bypass the XSS protection for script and style attributes, in much the same way as there's a SafeURL type that lets developers bypass URL sanitization for URLs in templ.
So, something like this would work:
templ Button(onclick templ.JS, style templ.Style, title string, text string) {
  <button class="button" type="button" onclick={ onclick } style={ style } title={ title }>{ text }</button>
}

For scripts, the generator would need to be updated so that the generated code supports the use of both templ.ComponentScript and templ.JS, and a new templ.JS string type added.
For style attributes, a similar update could be done to generate custom code that expects a templ.Style type, or else, it sanitizes the CSS.
I think this is very do-able.

Let me put it in simple terms...
Right now, your making another class to fix a issue what needs to be a very basic compile time flag.
templ generate --nostylecheck --nojschecks ...
The manual right now is already loaded with too much custom behavior in dealing with CSS/...  what is linked a lot to to bypass checks.
I understand that you prefer to have a strict amount of checking, but we have been writing way more methods to bypass Templ restrictions then we like. O, and that compile change a while back where you altered all the generated variable names was SO MUCH FUN, as it broke a lot of code that relied on injection to do bypasses.
When we see more and more features like proxy, live compiling etc... Great but again your add features that are done easily by existing tooling, where there are 100's of live compile / file watch programs. So instead of just adding a section to the manual, your doing the typical recreate existing features.
 You can imagine the fun when your handling 1000's of images.
Why did this exist even? Because the author kept adding features to his client, that he considered useful like json decoding directly as a output and that created issues as he coded it in such a way, that he was unable to simply export the body reader.
We ended up forking it and stripping out all that json, and other unneeded code, returned it to a bare client, and directly feed into io.copy, and the difference in performance (and memory utilization) was amazing. If we needed json? Wel, just take the reader and directly feed it into our json module. Less was better! But now the developer was on the hook for maintaining the whole json part, and so much other features. Instead of focusing on the core ... And we need to deal with a fork, so if a change happens to the base functionality, well, now we are forced to check again and again. Everybody loses in the end.
Right now, Templ is starting to tinker on this line, of trying to add more and more features that do not belong into it, or that are designed around a specific philosophy. Great to see JS, or CSS templ included but you know what is even better? Just a basic JS or CSS file in your html header, that only needs to be rendered one time. I know, old fashion design. Bonus, it has no issues unlike templ generated css/js because those CSS/JS never get evaluated if we send html snippets from server to client (for darn good reasons of security!).
So excuse my ranting. But i deal with the team members when they get into roadblocks (as it was my choice originally to use templ). Right now, we moving away from templ and are in the process of writing our own template generator, that is heavily inspired by templ but that just does the basics. And if we need more, like live reloading, ... Trust me when i say this: KISS ... stick to it, make some of those feature external or simply document them as such but we are seeing Templ go in a direction for a while, that is going to put so much stress on you as a developer to keep maintain it, and then like so many project it gets abandoned when you burn out.
Anyway, i am closing this issue... We are already moving to our own solution. I thanks you for reading this rant and i hope a bit of self reflection is in order. And my advice: Do not add every feature that people want / ask / cry about, do not make a project around your own development platform, ... Your just going to frustrate more people over time. Been way too darn long in this business to know how most projects end up, especially with one or small teams.
Good luck to you sir...

I am also running into this issue... I am using daisyui with a modal and need to simply write the following string
modal-%s.showModal()", entity.ID but I cannot do this
cannot use fmt.Sprintf("modal-%s.showModal()", entity.ID) (value of type string) as templ.ComponentScript value in variable declaration
So I tried this
<button class="btn btn-ghost btn-xs" onclick={templ.ComponentScript{Function: fmt.Sprintf("modal-%s.showModal()",entity.ID)}}>Open</button>
but then my onclick function is just empty, nothing is show in the element view
I am really confused as I simply want to write a string with a variable name that I control. What is the right way to do this? There is no documentation on ComponentScript at all.


Fallback for 500-page

If the whole page crashes with a 500-error, we need a static file fallback, because the controller may not actually be hit.

Oops, wrong repo


Add roles and groups to entities extracted by duckling

Description of Problem:
Entity roles and groups are currently only support by CRFEntityExtractor and DIETClassifier, e.g. components that extract custom entities. It might be helpful to add support for SpacyEntityExtractor and DucklingHTTPExtractor as well. If you are building a larger bot, you might have lots of different entities that are "number".
Example:
I need a table for 4 with one seat for a toddler

Overview of the Solution:
We don't have a clear solution in mind. One idea was to split off the role classification part from e.g. the CRFEntityExtractor and then wrapping that around the duckling extractor.
However, the more challenging part is the annotation of the training data. For SpacyEntityExtractor and DucklingHTTPExtractor you don't need to annotate anything right now. But if you want to learn specific roles for e.g. a "number", we need some kind of training data.
One idea was to just annotate tokens in the training data with roles. For example:
The car has [4]{"role": "wheel-count"} wheels and [2]{"role": "door-count"} doors

Hi this exactly the issue I'm trying to solve right now. Can i use CRFEntityExtractor to extract "related" numbers based on "entity groups" by having training data as follows?

can I have [2]{"entity": "itemQty", "group": "1"} [beer]{"entity": "itemName", "group": "1"}  [1]{"entity": "itemQty", "group": "2"} [water]{"entity": "itemName", "group": "2"} and [4]{"entity": "itemQty", "group": "3"} [mojito]{"entity": "itemName", "group": "3"}

And what happens if the user uses cardinals instead of numbers? usually this is done by DucklingHTTPExtractor, which does not read "groups" or "roles"

Any updates on this?
Makes sense to annotate tokens in the training data with roles:
The car has [4]{"role": "wheel-count"} wheels and [2]{"role": "door-count"} doors

It should be easier to add this support after resolving this issue


DM updates - default to not displaying dm groups

See https://github.com/xmtp/libxmtp/issues/1074
As a pre-requisite for dual sending 1 to 1 messages, we will be creating DM groups that we do not want to show up for users until we switch to V3 only clients. This PR filters DM groups from list and stream conversations functions that are used in bindings and downstream SDKs

Maybe you covered this somewhere but is there a way to override the filter out functionality? So for these pure V3 clients that they can still get conversations?

@nplasterer For streams to include Dm groups, we just need to pass in true to stream_conversations_with_callback here:
https://github.com/xmtp/libxmtp/blob/5d58c4c731b5e52ba14f48ac7be0eec8c19b6f1b/bindings_ffi/src/mls.rs#L864
For list to include Dm groups, we need to pass in true for include_dm_groups in  FindGroupParams struct here:
https://github.com/xmtp/libxmtp/blob/eb506f4e982cf3d07c42c51b049511e9911869cf/bindings_ffi/src/mls.rs#L839


Matched bets not in order stream

order_filter = streaming_order_filter(include_overall_position=True)
I only have unmatched bets in the order stream. Is that intended and I have to build a cache and assume that if a bet is no longer in the stream it was matched or am I missing something?
Thanks for any hint.

This is a limitation of streaming for orders.
(Feel free to join the slack group where you will get a response much quicker from the community)

Thanks for adding me to the Slack.
In case someone stumbles upon this - the matched orders are coming through the order stream if they were placed after the stream started.


Expose the API used for the interactive playground to extensions

I am looking for a way to recreate this in vscode:
https://www.youtube.com/watch?v=4jXGKmBrD5g (Opening a selection/file/function/symbol into a grouped view so you can work on multiple layers of your call path in one tab)
So far, I have investigated the use of FileSystemProvider; kinda like this: https://github.com/microsoft/vscode-extension-samples/tree/main/fsprovider-sample
I have also investigated using jupyter notebooks, but again the API does not seem to be flexible enough.
The interactive playground feature of the app seems to be able to provide something roughly like this with some changes.

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

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

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


Write a Haskell program to convert days to seconds

Description
Write a Haskell program to convert days to seconds
1 day = 24 hours = 1440 minutes = 86400 seconds
Input  : 5
Output : 432000

How to contribute

Save the solution in convert_days_to_seconds.hs file
Add convert_days_to_seconds.hs file in convert-days-to-seconds folder

!assign


Chart is Cropped in Firefox

I'm using Chromium 44.0.24 and Firefox 40.0.3 in Linux Mint 17.2.
On Chromium, chart is displayed correctly like this :

But in Firefox, label and bottom of the chart is cropped :

My HTML is like this :

Daily Sales

 Income

 Capital

 Profit

Javascript :
var labels = ['1', '2', '3', '4', '5', '6', '7', '8', '9', '10', '11', '12', '13', '14', '15', '16', '17', '18', '19', '20', '21', '22', '23', '24', '25', '26', '27', '28', '29', '30', '31'];
var income = [25742, 24176, 15258, 14044, 14762, 17520, 12539, 22712, 20319, 12063, 14068, 8246, 20541, 12735, 18280, 17423, 12071, 10496, 6912, 9391, 12283, 13820, 22869, 7937, 14173, 9738, 10082, 14873, 12841, 6768];
var capital = [16254.715, 15412.763, 9741.414, 8824.078, 9276.232, 11042.787, 8119.397, 14116.888, 12862.216, 7572.455, 9141.24, 5367.299, 12826.632, 8099.858, 11561.422, 11191.344, 7692.961, 6644.227, 4389.582, 6015.917, 7923.305, 8856.643, 14588.642, 5051.441, 9071.414, 6344.426, 6471.769, 9363.205, 8143.329, 4093.242];
var profit = [9486.785, 8762.737, 5516.586, 5219.422, 5485.268, 6476.713, 4419.603, 8594.612, 7456.284, 4490.045, 4926.76, 2878.201, 7713.868, 4634.642, 6718.078, 6231.656, 4378.039, 3851.273, 2522.418, 3374.583, 4359.195, 4963.357, 8279.858, 2885.059, 5101.586, 3393.574, 3609.731, 5509.795, 4697.671, 2674.758];

var series = [{
    className: 'ct-income',
    name: 'income',
    data: income
}, {
    className: 'ct-capital',
    name: 'capital',
    data: capital
}, {
    className: 'ct-profit',
    name: 'profit',
    data: profit
}];

var options = {
    height: 500,
    fullWidth: true,
    lineSmooth: false,
    showArea: false,
    showLine: true,
    showPoint: true,
    axisX: {
        labelOffset: {
            x: -3
        }
    },
    axisY: {
        offset: 0,
        showLabel: false
    },
    chartPadding: {
        top: 8,
        left: 24,
        right: 24,
        bottom: 0
    }
};

new Chartist.Line('#ct-chart', {
    labels: labels,
    series: series,
}, options);

And last, my CSS :
* {
    margin: 0px;
    padding: 0px;

    -webkit-box-sizing: border-box;
    -moz-box-sizing: border-box;
    box-sizing: border-box;

    color: #212121;
    font-family:'Roboto', 'sans-serif';
}

 .min-height-100 {
    min-height: 100px;
}

 body, html {
    background-color: #eee;
}

.content {
    padding: 8px;
    max-width: 1028px;
    margin: auto;
    overflow: auto;
}

.box {
    margin: 8px;
    border: 1.5px solid #ddd;
    background-color: #FFF;
    box-shadow: 0px 2px 10px 0px rgba(167, 167, 167, 0.35);
}

 .box-header {
    width: 100%;
    display: table;
}

.box-header .header {
    padding: 16px;
    font-size: 1.1em;
    font-weight: 600;
    display: table-cell;
}

.box-footer {
    padding: 16px;
    display: block;
    font-size: 0.8em;
    font-weight: 500;
    text-align: center;
    border-top: 1.5px solid #ddd;
}

 .chart {
    padding: 16px;
    border-top: 1.5px solid #ddd;
}

.box-legend p {
    display: inline-block;
}

.box-legend p:not(:last-child) {
    margin-right: 24px;
}

.box-legend .fa {
    margin-right: 8px;
}

 #ct-chart .ct-line {
    stroke-width: 3px;
    stroke-linecap: round;
}

#ct-chart .ct-point {
    opacity: 0.5;
    cursor: pointer;
    stroke-width: 12px;

    transition: all 500ms ease;
    -webkit-transition: all 500ms ease;
    -moz-transition: all 500ms ease;
    -o-transition: all 500ms ease;
}

#ct-chart .ct-point:hover {
    opacity: 1;
    stroke-width: 24px;
}

#legend-income, #ct-chart .ct-income .ct-line, #ct-chart .ct-income .ct-point {
    color: #673AB7;
    stroke: #673AB7;
}

#legend-capital, #ct-chart .ct-capital .ct-line, #ct-chart .ct-capital .ct-point {
    color: #2196F3;
    stroke: #2196F3;
}

#legend-profit, #ct-chart .ct-profit .ct-line, #ct-chart .ct-profit .ct-point {
    color: #E91E63;
    stroke: #E91E63;
}

You can see the sample in this fiddle.

I have the exact same issue.  The last time the graph work for Firefox was the 0.7.4 release.  But the scale wasn't good either.

I've got it now. I don't know why, but it seems the problem is happened because the padding in div that used as chart container. So, to fix it, I remove the padding in my .chart class :
 .chart {
/*  padding: 16px;                  remove this*/
    border-top: 1.5px solid #ddd;
}

Now it displayed correctly in Firefox and Chromium :

You can see it in this fiddle.

The CSS fix doesn't work for me as I have no padding or a .chart css class.
What I did do was as the following config option to the chart:
low: -150
And this result in the following, however, the X axis labels still do not show,  Any ideas?

@RadhiFadlillah The chart container uses padding to create an intrinsic container. Therefore, you should not apply padding to the container directly. If you need padding you'll need to use an other wrapper around the container.
@treadmillian , I'll investigate this ASAP.

@gionkunz Here's 0.7.4 working, however, the option to show on integers for the Y Axis doesn't work.
onlyInteger: true

@treadmillian can you reproduce the issue on jsbin? Because looking at the examples here http://gionkunz.github.io/chartist-js/examples.html I can't seem to find an issue like this using FF 39.

It's probably related to some styles you're using that are no problem for 0.7.4 but are for 0.9

On a lot closer inspection for some reason I had this:

When it should have been this:

Checking it more, but can't believe that's what it has ended-up as being the problem.... Sorry!

I have a similar problem, except that the "x" axis is compressed in Firefox. It shows the line type graphic as a vertical line. All labels look good.

I just added
.ct-chart-line{
		overflow:visible !important;
}

in the page and problem fixed for me.

Closing this issue for now

I want to reopen this issue, because it is still present. When the chart is set in a grid container the @coolbit solution is the only thing that helps to show the entire chart. This is not enough though. The width of chart on the right is wrong (look at the superimposed grid, it should leave empty the middle column.

Upon resizing the window, the chart reduces in size, fitting in the asigned grid position

The chart on the right has the same settings, but it does not get clipped, like the one on the left.
Do note that the amount of clipping seems to coincide with the offset: 120 applied on the axisY which is the same in both cases .

Having the same problem with Firefox, however this bug occurs only when I use labelInterpolationFnc.


Replace greedy versions approach

Hello. Recently I got unexpected test failures in CircleCI which were not happening on my machine. This was caused by the reason that babel-jest was silently updated because I followed approach in README and set version of it to *. To avoid such non-positive situations in the future I suggest to show good approach in README for users to set stable library which is latest now, this will help to avoid applying of breaking changes unexpectedly.
What do you think?

Closing this. We'll import babel-jest into the jest repo.


Meteor.userId can only be invoked in method calls.

Why can I not use Meteor.userId in collection.js ?
Error Message
W20151019-12:35:48.616(-4)? (STDERR) Error: Meteor.userId can only be invoked in method calls. Use this.userId in publish functions.
W20151019-12:35:48.618(-4)? (STDERR)     at AccountsServer.userId (accounts_server.js:80:13)
W20151019-12:35:48.618(-4)? (STDERR)     at Object.Meteor.userId (accounts_common.js:222:19)
W20151019-12:35:48.618(-4)? (STDERR)     at [object Object].UploadFS.store.Local.onRead (packages/me_mypack/collections.js:22:1)
W20151019-12:35:48.618(-4)? (STDERR)     at Object.path [as handle] (packages/jalik_ufs/ufs-server.js:156:1)
W20151019-12:35:48.618(-4)? (STDERR)     at next (/Users/me/.meteor/packages/webapp/.1.2.2.v8ezdl++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:190:15)
W20151019-12:35:48.619(-4)? (STDERR)     at Function.app.handle (/Users/me/.meteor/packages/webapp/.1.2.2.v8ezdl++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:198:3)
W20151019-12:35:48.619(-4)? (STDERR)     at Object.fn [as handle] (/Users/me/.meteor/packages/webapp/.1.2.2.v8ezdl++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:74:14)
W20151019-12:35:48.619(-4)? (STDERR)     at next (/Users/me/.meteor/packages/webapp/.1.2.2.v8ezdl++os+web.browser+web.cordova/npm/node_modules/connect/lib/proto.js:190:15)
W20151019-12:35:48.619(-4)? (STDERR)     at Object.WebAppInternals.staticFilesMiddleware (packages/webapp/packages/webapp.js:370:1)
W20151019-12:35:48.619(-4)? (STDERR)     at packages/webapp/packages/webapp.js:633:1
My package.js includes this line:
api.add_files("collections.js");
collections.js (available on client & server)
/////////////////////////////////////
// Define server & client collections.
/////////////////////////////////////

//mypack_std_out = new Mongo.Collection("mypack_std_out");
//mypack_std_err = new Mongo.Collection("mypack_std_err");
mypack_log = new Mongo.Collection("mypack_log");
mypack_jobs = new Mongo.Collection("mypack_jobs");
mypack_uploads = new Mongo.Collection("mypack_uploads");

// Uploaded files are stored here.
mypack_uploads_store = new UploadFS.store.Local({
	collection: mypack_uploads,
	name: 'mypack_uploads',
	path: '~/mypack_uploads',

	// Called before reading file to check if we can return it.
	onRead: function (fileId, request, response) {
		var doc = mypack_uploads.findOne(fileId);
		if (doc) {
			// User must own file to download it.
			if (doc.userId !== Meteor.userId()) {
				throw new Meteor.Error(403, 'this file is private');
			}
		} else {
			throw new Meteor.Error(404, 'file not found');
		}
	},

	// Called when file has been uploaded.
	onFinishUpload: function (file) {
		console.log(file.name + ' has been uploaded');
	}
});

Sorry, it seems the correct way to get the logged in user ID is with request.userId.


feat: Disable / Enable actions

Description
closes #2286
todos:

[x] icons for toolbar buttons - Disable / Enable (@DesignPolice )
[x] selection states be reflected on Disable/Enable buttons (@yeze322 )
[x] do we need 'Disable' / 'Enable' options inside the '...' flyout menu?

Task Item

Screenshots

No action selected

Both 'Disable' and 'Enable' clickable

Only 'Disable' clickable

Only 'Enable' clickable

'Disable' Effects

@DesignPolice Hey Marc, you were assigned because we need your input on icons.
Could you help to figure out what's the proper icons for the 'Disable' and 'Enable' button?
Can I find one in the Office Fabric Icon lib?

My 2 cents:
Tool bar:

disable & enable button state should be more user friendly (eg. after one node disabled, select this node , the disable button should not be clickable)

Overall UX experience:

if nodes disabled in visual canvas, could we reflect the state in property panel as well ? sometimes I did not notice such node is disabled but I am still editing.
After disable action, the node will be in gray but not easy to tell it is disable gray or none-user interaction node gray (eg. set property)  as it is in gray as well. could we let user be more aware of these changes ? @sangwoohaan

schema driven or runtime driven for nested actions

add node into disabled if/else branch, this node will be in gray but the schema file does not add disable . so just want to confirm this is runtime driven for nested actions

Coverage decreased (-0.07%) to 48.022% when pulling 6d5decf5e2178e56a8e3e04379115cb5fdc7a420 on visual/disabled into c68a1880f4e80c30383eb5d1716d6d077f870e56 on master.

@yeze322 what is the status of this PR? I saw you had some questions out to the design team as well as some UX feedback? Has everything been addressed? If not, can you mark this PR as draft until it is ready again?

@a-b-r-o-w-n yeah, waiting for two design feedbacks:

Icons
Toolbar button UX (in our scrum the decision is to hide all unavailable buttons)

@yeze322 Can you address the conflict?
Also, it wasn't clear to me if this is ready for review based on yesterday's standup? Are we still waiting on something from design?

Addressed here and discussed in several standups.
https://www.figma.com/file/LlTlh5vXwq91zjGnFtrUUR6l/Composer-main-design-spec-UI-library?node-id=2968%3A27508
For more questions, feel free to reach out to me.
The design impacts toolbars across the app.

@a-b-r-o-w-n just adapted to new design, now it's done.


Taskbar - Limit to current workspace

Hello,
A feature request that would be very nice to have is to limit taskbar to show apps running only in the current workspace.
Thanks!

You're probably looking for the all-outputs option https://github.com/Alexays/Waybar/wiki/Module:-Taskbar

No not really, all_outputs = false would show ALL applications currently running on workspaces on the current monitor. I would like to limit the task bar to applications running on the current workspace.

duplicate of #1997


[kfr] Update to 4.2.1

Describe the pull request

What does your PR fix?
Fixes #19954

Which triplets are supported/not supported? Have you updated the CI baseline?
<all / linux, windows, ...>, <Yes/No>

Does your PR follow the maintainer guide?
Your answer

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
<Yes / I am still working on this PR>

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Have you tested the features in this PR? @myd7349

Have you tested the features in this PR? @myd7349

Hi! @NancyLi1013 Yes. I have tested this PR locally. This PR doesn't introduce new features and the old ones currently only works with Clang AFAIK.

LGTM now, thanks for your updates @myd7349.


PollParticipantPromise and PollCompletion in core/lib/promise/party.h  compile error: control reaches end of non-void function [-Werror=return-type]

What version of gRPC and what language are you using?
gRPC version: 1.62.0
C++
What operating system (Linux, Windows,...) and version?
ubuntu 22.04
What runtime / compiler are you using (e.g. python version or version of gcc)
GCC 11.4.0
What did you do?
compile gRPC with -Werror=return-type
What did you expect to see?
add return value at default branch in PollParticipantPromise and PollCompletion
What did you see instead?
In file included from /path/grpc_1.62.0/src/core/lib/transport/call_spine.h:26,
from /path/grpc_1.62.0/src/core/lib/transport/call_spine.cc:17:
/path/grpc_1.62.0/src/core/lib/promise/party.h: In member function ‘bool grpc_core::Party::PromiseParticipantImpl::PollParticipantPromise() [with SuppliedFactory = grpc_core::ForwardCall(grpc_core::CallHandler, grpc_core::CallInitiator, grpc_core::ClientMetadataHandle)::<lambda()> mutable::<lambda(grpc_core::MessageHandle)> mutable::<lambda()>]’:
/path/grpc_1.62.0/src/core/lib/promise/party.h:567:5: error: control reaches end of non-void function [-Werror=return-type]
567 |     }
|     ^
/path/grpc_1.62.0/src/core/lib/promise/party.h: In member function ‘grpc_core::Poll<typename grpc_core::promise_detail::OncePromiseFactory<void, F>::Promise::Result> grpc_core::Party::PromiseParticipantImpl::PollCompletion() [with SuppliedFactory = grpc_core::ForwardCall(grpc_core::CallHandler, grpc_core::CallInitiator, grpc_core::ClientMetadataHandle)::<lambda()> mutable::<lambda(grpc_core::MessageHandle)> mutable::<lambda()>]’:
/path/grpc_1.62.0/src/core/lib/promise/party.h:579:5: error: control reaches end of non-void function [-Werror=return-type]
579 |     }
|     ^
Anything else we should know about your project / environment?
N/A

The same here under Gentoo (Pentoo):
 * QA Notice: Package triggers severe warnings which indicate that it
 *            may exhibit random runtime failures.
 * ./src/core/lib/promise/party.h:567:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:579:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:567:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:579:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:567:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:579:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:567:5: warning: control reaches end of non-void function [-Wreturn-type]
 * ./src/core/lib/promise/party.h:579:5: warning: control reaches end of non-void function [-Wreturn-type]

@ctiller ping

The same here under ALT

./src/core/lib/promise/party.h:567:5: error: control reaches end of non-void function [-Werror=return-type]
  567 |     }
      |     ^
./src/core/lib/promise/party.h:579:5: error: control reaches end of non-void function [-Werror=return-type]
  579 |     }
      |     ^
./src/core/lib/promise/party.h:567:5: error: control reaches end of non-void function [-Werror=return-type]
  567 |     }
      |     ^
./src/core/lib/promise/party.h:579:5: error: control reaches end of non-void function [-Werror=return-type]
  579 |     }
      |     ^


cmake build error while building rippled on ubuntu 18.04

/rippled/build$ cmake ..
-- Found Git: /usr/bin/git (found version "2.23.0")
-- The C compiler identification is GNU 7.4.0
-- The CXX compiler identification is GNU 7.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Using 2 cores for ExternalProject builds.
-- Build type not specified - defaulting to Release
-- rippled version: 1.3.1
-- NIH-EP cache path: /home/blocmatrix/rippled/.nih_c/unix_makefiles/GNU_7.4.0/Release
-- docker NOT found -- won't be able to build containers for packaging
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
-- Check if compiler accepts -pthread
-- Check if compiler accepts -pthread - yes
-- Found Threads: TRUE
-- BOOST_ROOT: /home/my_user/boost_1_71_0
-- BOOST_LIBRARYDIR:
CMake Error at Builds/CMake/FindBoost.cmake:2153 (message):
Unable to find the requested Boost libraries.
Unable to find the Boost header files.  Please set BOOST_ROOT to the root
directory containing Boost or BOOST_INCLUDEDIR to the directory containing
Boost's headers.
Call Stack (most recent call first):
CMakeLists.txt:717 (find_package)
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.a (found suitable version "1.1.1", minimum required is "1.0.2")
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.11")
CMake Error at CMakeLists.txt:1114 (get_target_property):
get_target_property() called with non-existent target "Boost::date_time".
-- Pausing to download NuDB...
-- Found Protobuf: /usr/lib/x86_64-linux-gnu/libprotobuf.a;-pthread (found version "3.0.0")
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- doxygen executable not found -- skipping docs target
-- Configuring incomplete, errors occurred!
See also "/home/blocmatrix/rippled/build/CMakeFiles/CMakeOutput.log".
See also "/home/blocmatrix/rippled/build/CMakeFiles/CMakeError.log".

I'm following the steps from https://xrpl.org/build-run-rippled-ubuntu.html

got resolved

how?


June 11th 2024 MicroProfile Live Hangout video for Youtube

Here is the link to the video for upload to YouTube. Please update the Meeting Minutes with a link to the recording.
Thanks!

https://youtu.be/_GT-yXaH7gY Updated


[Azure Monitor OpenTelemetry] Handle Parsing Nested Objects in Integration Tests

Packages impacted by this PR
@azure/monitor-opentelemetry
Issues associated with this PR
#29046
Describe the problem that is addressed by this PR
Integration tests are failing because while the expected properties are all met in the actual properties object, there is additional information provided that does not exactly match the staticly set values in the expected object.
Checklists

[x] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

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


New deployment type: PSGalleryScript

PSGalleryModule is up and running, would be handy to have a PSGalleryScript to go along with it, for example:
Deploy SomeScript {
    By PSGalleryScript {
        FromSource SomeScript.ps1
        To 'PSGallery' #Optional, default to gallery
        WithOptions @{
            ApiKey = '<my_api_key>'
            Guid = '' # Ideally we avoid a new GUID for every deployment... require here or maybe look up in the gallery, generate if not found?
            # Other params, see New-ScriptFileInfo for examples
        }
    }
}

Do you want to generate the "new-scriptfileinfo" block yourself or have people do that before uploading a script to PSGallery?
Test-ScriptFileInfo and if not generate it?

New-ScriptFileInfo and Update-ScriptFileInfo still seem a little dodgy :S so might wanna wait with this module a couple of updates ;)
New-ScriptFileInfo adds all the fields to the scriptfile not just the one you supplied.
Update-ScriptFileInfo does not except any of those fields to be $null even tho they are not mandatory. (does not help if you remove them form the fileinfo block.)

The variable cannot be validated because the value  is not a valid value for the CompanyName variable.
The variable cannot be validated because the value  is not a valid value for the Copyright variable.
The variable cannot be validated because the value $null is not a valid value for the RequiredModules variable.
The variable cannot be validated because the value $null is not a valid value for the ExternalModuleDependencies variable.
The variable cannot be validated because the value $null is not a valid value for the RequiredScripts variable.
The variable cannot be validated because the value $null is not a valid value for the ExternalScriptDependencies variable.
The variable cannot be validated because the value $null is not a valid value for the Tags variable.
The variable cannot be validated because the value $null is not a valid value for the ProjectUri variable.
The variable cannot be validated because the value $null is not a valid value for the LicenseUri variable.
The variable cannot be validated because the value $null is not a valid value for the IconUri variable.
You cannot call a method on a null-valued expression.

Yep, those functions definitely have a ways to go.  Guessing we'll need two paths:

Test-ScriptFileInfo on source passes: Use regex or another tool to update existing manifest (until Update-ScriptFileInfo works)
Test-ScriptFileInfo on source fails: Generate header based on WithOptions data.

Personally, I'll always use the latter.  Planning to deploy a subset of functions from this misc repo, will let PSDeploy handle the headers, leave the source clean.
Cheers!

I am planning the latter as well, still in doubt to create folders per script and add a script.test.ps1 and script.psdeploy.ps1 but that's a different matter.
Yeah will need to implement both option for now till MS get's this fixed. Will see what I can do ;)

Added a PSGalleryScript type marked as experimental.  Definitely needs more work.  Not even accounting for Test-ScriptFileInfo yet, at this point assuming all input files are devoid of script info data.

https://github.com/OneGet/oneget/issues/185


Fix counting of escape sequences when splitting TXT strings

endingToTxtSlice, used by TXT, SPF and a few other types, parses a string such as "hello world" from an RR's content in a zone file. These strings are limited to 255 characters, and endingToTxtSlice automatically splits them if they're longer than that. However, it didn't count the length correctly: escape sequences such as \\ or \123 were counted as multiple characters (2 and 4 respectively in these examples), but they should only count as one character because they represent a single byte in wire format (which is where this 255 character limit comes from). This commit fixes that.

A more detailed explanation of the problem: https://github.com/miekg/dns/issues/1384#issuecomment-1946017184

Apologies, found a bug! Fix and more tests coming today.

I think this is OK (my gawd... txt records)... I see a escapedStringOffset without looking too closely, don't we already have a bunch of those type of functions? Is a new one really needed or can something older be re-used?

Thanks for looking! I had indeed found one, escapedNameLen, but, while it's similar, it's also different enough to make it difficult to reuse for our purposes. Looking at callers of isDDD again now, I also don't see anything else that could easily be reused.

FYI: we've been running this in production for 3+ weeks with no issues

Seems to have triggered https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=68124 cc @miekg

hmm, thanks.
After some clicking this is the testcase:
 hinFo ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ\
 ~~~

Yikes, thanks @catenacyber. I don't have access to the report but I'll try to figure out what's happening here.

@miekg I'm using slightly modified versions of Fuzz and FuzzNewRR (surely the latter is the problematic one), but I'm not able to replicate the issue. I've tried some variations of the test case, such as removing the spaces at the start of each of the two lines, removing the six spaces at the end of the first line, in case those were added by mistake, but no luck. I also tried the second line with and without a trailing \n. Parsing fails if I remove the initial spaces, but I imagine the report isn't about a simple error (fuzz function returning code 0) but about a panic.
I think I need some help here. If the test case is available as a binary file that'd be great. Confirmation that it is indeed FuzzNewRR that's failing would be helpful too.

Here is the base64-encoded file
IGhpbkZvIP//////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////XA==

FuzzNewRR is the target

panic: runtime error: slice bounds out of range [:256] with length 255
--
  |
  | goroutine 17 [running, locked to thread]:
  | github.com/miekg/dns.endingToTxtSlice(0x0?, {0x755ec9, 0x10})
  | github.com/miekg/dns/scan_rr.go:60 +0xc78
  | github.com/miekg/dns.(*HINFO).parse(0x10c0000dc000, 0x10c00007c6c0?, {0x0?, 0x0?})
  | github.com/miekg/dns/scan_rr.go:201 +0x4b
  | github.com/miekg/dns.(*ZoneParser).Next(0x10c0000d2090)
  | github.com/miekg/dns/scan.go:672 +0x29b7
  | github.com/miekg/dns.ReadRR({0x810638?, 0x10c0000ce000?}, {0x0?, 0x797180?})
  | github.com/miekg/dns/scan.go:128 +0xa6
  | github.com/miekg/dns.NewRR({0x10c0000c8000, 0x106})
  | github.com/miekg/dns/scan.go:113 +0x13f
  | github.com/miekg/dns.FuzzNewRR({0x612000000940?, 0x0?, 0x5cc301?})
  | github.com/miekg/dns/fuzz.go:29 +0xdb
  | main.LLVMFuzzerTestOneInput(...)
  | ./main.1703470873.go:21

Thanks a ton! The problem seems to be within escapedStringOffset, in particular the return i + 1 within if offset >= byteOffset. The function is getting confused by the trailing slash and returning an OOB offset, which should never be allowed to happen.
It should be easy enough to fix by adding a bounds check there but I'll see if I can come up with something better that's easier to follow.

Haven't tested it, but I think escapedNameLen might suffer from a similar issue where an invalid message could be produced if the last character is a backslash. That one is probably less serious because I doubt it would panic and, regardless, a backslash shouldn't be able to get there in the first place unless someone is modifying the structs directly. Perhaps another argument for not trying to preserve zone file syntax such as escape sequences in parsed data structures though?

Here's my proposed fix: #1557

Looks ok. Not near a computer for a couple of days..
Are you willing to accept an invite to become maintainer and able to merge?
/Miek
On Fri, 19 Apr 2024, 15:10 Janik Rabe, @.***> wrote:

Here's my proposed fix: #1557 https://github.com/miekg/dns/pull/1557
—
Reply to this email directly, view it on GitHub
https://github.com/miekg/dns/pull/1540#issuecomment-2066546102, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWIW3LQBKBHHSO4XBE2MLY6EJTZAVCNFSM6AAAAABEBXPUECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWGU2DMMJQGI
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thank you Miek! It would be an honor!

Ack. Ack
On mobile, but will push buttons next week.
Thanks all, appreciate all the help
On Fri, 26 Apr 2024, 09:24 Janik Rabe, @.***> wrote:

Thank you Miek! It would be an honor!
—
Reply to this email directly, view it on GitHub
https://github.com/miekg/dns/pull/1540#issuecomment-2078889710, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWIW34NQOYKLH2CHF6J33Y7IFKXAVCNFSM6AAAAABEBXPUECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYHA4DSNZRGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

invite finally sent


No JavaScript from generated from npm init

When I'm trying to use npm init @open-wc for the first time to start a new Application, there are no .js files being generated. (See screenshot below)
Am I missing something really obvious, or is this just not working as intended?

Node Version: v12.14.1
NPM Version: v6.13.4

This is not correct, thanks for reporting it


using Aggregation without window

I want to use aggregate node without  time window. for example i have a message like  :
{
    "eventName": "sale",
    "id": "1",
    "order": "1000",
    "product": "shoe"
}

I want to aggregate events  with the same id (grouped by id) until sum of their order is less than 20000.
when their sum passes 20000  new event should trigger.
actually here window is sum of 'order' property and id. when ever the sum of order passes 20000 new event trigger and new window begin for next events.

Hi, @jafarrasooli!
Currently there are two types of windows available as you have seen. They are mainly used to limit the quantity of items that operations like sum, avg, var, should be working with. That being said, the way that you are willing to do is not possible, at least right now. However, what you can do is create a new node in your flow at the output of the aggregate node, like the function node, with two outputs, one output in case the new event generated is bellow 20000 and the other if the otherwise. If the first case happens, you'll probably need only to do a few tweaks on the event generated in case it does not have the source's fields/properties like eventType (pay attention that you are probably using an outdated version, so the eventType in your case is the same as eventName), hence it can be refeed back to the aggregate node much like any other event that is entering the node. In the aggregate node, you can keep your current setting, either using time window or count window (though time I think would be more suitable) and still grouping all events by id

thanks @CeZL. that is a good solution to the  problem. I think I should think more CEP way.


Remove style

We need functionality to remove a style from the styles page.

This functionality is in. Open any style, then click on the settings tab. There should be a remove style (trash can icon) button at the bottom of the page.

Ok


Create new RMAN Sprints -11316

Add here your WMS ID
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

Please complete the Oracle Contributor Agreement. We cannot approve your PR before that is done.

Hi ,
I have already signed the agreement.
Thanks
Satish
On Fri, Jun 2, 2023 at 10:01 AM William Masdon @.***>
wrote:

Please complete the Oracle Contributor Agreement. We cannot approve your
PR before that is done.
—
Reply to this email directly, view it on GitHub
https://github.com/oracle-livelabs/partner-solutions/pull/49#issuecomment-1574047210,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO7RKYMYHABLY72OH3PFDFTXJIL7FANCNFSM6AAAAAAYXOTCSQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @satish-oracleace,
The check is still failing on the PR. Are you sure your Oracle account is affiliated with the email committing this PR?

Best,
Kaylien

Yes, I use the same email for Oracle account as well.
Can we have a Zoom call to go over and  try to fix the issue?
Thanks
Satish
On Mon, Jun 5, 2023 at 3:07 PM Kaylien Phan @.***>
wrote:

Hi @satish-oracleace https://github.com/satish-oracleace,
The check is still failing on the PR. Are you sure your Oracle account is
affiliated with the email committing this PR?
[image: image]
https://user-images.githubusercontent.com/20189073/243487119-352143ba-417d-41a3-8641-67b338a01151.png
Best,
Kaylien
—
Reply to this email directly, view it on GitHub
https://github.com/oracle-livelabs/partner-solutions/pull/49#issuecomment-1577544350,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO7RKYJRLVQELOTRCEY3XA3XJZKBFANCNFSM6AAAAAAYXOTCSQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks Kaylien
Once you publish pls let me know
Thanks
Satish
On Thu, Jun 8, 2023 at 9:46 AM Kaylien Phan @.***>
wrote:

Merged #49 https://github.com/oracle-livelabs/partner-solutions/pull/49
into main.
—
Reply to this email directly, view it on GitHub
https://github.com/oracle-livelabs/partner-solutions/pull/49#event-9474925143,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AO7RKYOIM46MPYPELRFKI6DXKH6UTANCNFSM6AAAAAAYXOTCSQ
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


Addon can't be downloaded from the asset store. Error 404

When trying to download the plugin from the asset store getting the error Failed: 404
Godot 4.3 .NET

Aha that makes total ssense. Thanks!