CFP: External L4LB DSR support

Hello,
We have troubles using Cilium with external L4LB. Our internal network is IPv6 single stack and only edge fabric can handle incoming IPv4 traffic. Before traffic reaches K8S nodes it gets balanced by external LB which works similar to Cilium standalone L4LB - original packet gets encapsulated in another IP packet and delivered to node, then DSR is expected from destination web server.
Using Cilium 1.15 or 1.16-rc this IPIP traffic gets dropped in eBPF layer as unknown protocol.
Observed traffic flow:
Client_IPv4 -> VIP_IPv4 hits one of the LB servers
LB Server, having configured VIP_IPv4 -> UPSTREAM_IPv6 encapsulates original IPv4 packet in IPv6 sends it to K8S node.
LBServer_IPv6 -> UPSTREAM_IPv6 with inner Client_IPv4 -> VIP_IPv4
Traffic reaches K8S node because UPSTREAM_IPv6 configured as LoadBalancer service IP (with ETP: Local if that matters) and announced through BGP by Cilium
Cilium looks at outer IPv6 packet and finds corresponding service, but then packet gets dropped in lb6_extract_tuple at https://github.com/cilium/cilium/blob/main/bpf/lib/lb.h#L568
There is multiple related ongoing work, but I'm struggling to find solution for different stack (outer IPv6 + inner IPv4) problem.
First of all, there is merged PR https://github.com/cilium/cilium/pull/31213 by @borkmann that enables creating IPIP interfaces in the host network namespace, but there are no attached eBPF programs to these interfaces.
Then this https://github.com/cilium/cilium/pull/30547 https://github.com/cilium/cilium/pull/31163 two PRs exists but closed for some reason. I've made one more rework of these changes on top of fresh main here and indeed this works flawlessly, even without IPIP tunnels and resolves external DSR problem almost completely. One case that is still failing is different stack inner packets (outer IPv6 + inner IPv4 or outer IPv4 + inner IPv6), which is main blocker for me.
Then there is discussion here https://github.com/cilium/cilium/issues/32473 which also mentions external LB with IPIP packets, but observed packet drops in different eBPF program.
And lastly there is this rather new issue https://github.com/cilium/cilium/issues/33020 that seems like almost complete duplicate of this issue, but it's proposed PR https://github.com/cilium/cilium/pull/33026 handles only IPv4 traffic. As I understood comment from @gentoo-root here the proposed solution was to attach one more eBPF program to IPIP devices created by https://github.com/cilium/cilium/pull/31213 and route to services from there using shared map that gets filled by host interface program.
Thanks.

After discussing with External LB team, we decided to try to rewrite original IPv4 packet to IPv6 using RFC6052.
So instead of "outer IPv6 + inner IPv4" Cilium will receive "outer IPv6 + inner IPv6 (rewritten by LB)", thus, if we succeed, https://github.com/cilium/cilium/pull/31163 will work out of the box.

@borkmann @gentoo-root Any help here would be welcome.
It would be great to have this feature merged before 1.16 release. I can open PR from https://github.com/YakhontovYaroslav/cilium/tree/feature/external-dsr if code authorship is not an issue or try to rebase pr/ipip6 branch.
Thanks.


Spanner: Jetty ALPN/NPN has not been properly configured if spark dependencies are added

My requirement was to write a Spark DataFrame to the Spanner Table, when I tried to run application it end up with "Jetty ALPN/NPN has not been properly configured" even I run spanner application without spark code it was giving this error.
When I run the same application by removing spark dependencies it ran! so, I am on conclusion that, Spanner application is not running with spark dependencies.
here is the spark and Spanner dependencies by putting together it is failing:
compile group: 'com.google.cloud', name: 'google-cloud', version: '0.20.0-alpha'
compile group: 'com.google.cloud', name: 'google-cloud-spanner', version: '0.20.0-beta'
compile group: 'org.apache.hadoop', name: 'hadoop-mapreduce-client-core', version: '2.7.2'
compile (group: 'org.apache.spark', name: 'spark-core_2.11', version: '2.0.2'){
       exclude group: 'org.apache.hadoop', module:'hadoop-mapreduce-client-core'
   }
compile group: 'org.apache.spark', name: 'spark-sql_2.11', version: '2.0.2'
compile group: 'org.apache.hadoop', name: 'hadoop-aws', version: '2.7.2'

Hi @vaiju12p! I was able to reproduce the problem using a very simple Spanner application and the dependencies you listed. I found that including the following exclusion in my build.gradle file resolved the issue:
configurations {
    compile.exclude module: 'netty-all'
}

Let me know if this fixes the problem for you. If it is not an option for you to exclude this dependency, then you may want to investigate the compatibility of different versions of netty that are being used by Spark and by the io.grpc:grpc-netty package. You can use gradle dependencies to view the dependencies that are being used.
Hopefully that helps!

great!! It is working thanks you very much @michaelbausor .


building with Carthage

I am trying to use carthage to get this into a project.  It fails to build with the following:
=== BUILD TARGET BRNImagePickerSheet OF PROJECT BRNImagePickerSheet WITH CONFIGURATION Release ===

Check dependencies
Code Sign error: No code signing identities found: No valid signing identities (i.e. certificate and private key pair) matching the team ID “XXXXXXXXXX” were found.
CodeSign error: code signing is required for product type 'Framework' in SDK 'iOS 8.2'

I just started giving carthage a go so it could be something I am doing wrong.  Any thoughts?

I just tried it. It works fine for me. This issue might help you out a little.


[BUG] Missing textures

Description:
I am playing on a mostly vanilla singleplayer from CurseForge. IR is the (almost) only mod to add blocks. Most of the textures for machines are missing making it extremely hard to figure out things. I have tried to reinstall IR and from a new world but it made no difference. Are these missing texture because any specific reason or any specific incompatibility with any mod in particular? any way to fix it?
Steps to Reproduce:

Just play

Technical Information:

Minecraft: 1.18
Fabric API: 0.12.12
Industrial Revolution: 1.13.2 beta
Modpack: It's Performance+ (so Vanilla) but I added other mods (63 total). Included are some performance mods like Sodium and its brothers (Starlight instead of Phosporous), Entity culling, FerriteCore, Fast Furnace, Enhanced Block Entities, Discerning Furnaces, Krypton.

A full list of mods and their versions is this.

You have Sodium installed I presume.
You either need to uninstall Sodium OR install Indium with Sodium as well

Ok perfect. I checked if there were any dependencies to install but i must have missed Indium. Thanks


Add option to run with coverage

This is a feature request not an issue
Currently I can (and do) manually add the --coverage flag to the jest runner's runOptions. The only downside is generating coverage makes the tests run quite a bit longer than usual. I usually add the --coverage option to see initial coverage, then return to settings and remove it, add some more tests and then re-add it again to check my coverage. This makes the whole process faster since my tests run faster in that period where I have coverage disabled.
It would be great to have an additional run option "Run with coverage" inline in the code then I can just click that when I want coverage and the normal run/debug when I don't

It's a good idea, no doubt. Wanna try a POC?

getting the extra option to render: https://github.com/firsttris/vscode-jest-runner/blob/master/src/JestRunnerCodeLensProvider.ts
command registration: https://github.com/firsttris/vscode-jest-runner/blob/aec44ff5bb6d3f816663d91e838e0e9e4ecf36c9/src/extension.ts#L15-L20

Hey @cdaringe sure that would be awesome I'll try to get it going and make a PR
Thanks

merged


Bug or missing docs for data isolation mode

Describe the bug
When i try to access vizier directly via px proxy and  https://<IP_ADDRESS>:31068/  getting 404
I dig into the envoy routes and try other ones :
https://<IP_ADDRESS>:31068/pl.vizier.services.query_broker
https://<IP_ADDRESS>:31068/pl.api
Both of them giving Must have bearer auth
To Reproduce
Steps to reproduce the behavior:

run px proxy
go to the https://<IP_ADDRESS>:31068/ or other uri
See error

Expected behavior
There are definitely should be  a way to view your metrics without https://work.withpixie.ai/live or if not it should be documented, now its not clear how isolated mode is working.
Logs
`[2021-01-16 08:34:39.781][1][info][main] [source/server/server.cc:249] initializing epoch 0 (hot restart version=11.104)
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:251] statically linked extensions:
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:253]   access_loggers: envoy.file_access_log,envoy.http_grpc_access_log,envoy.tcp_grpc_access_log
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:256]   filters.http: envoy.buffer,envoy.cors,envoy.csrf,envoy.ext_authz,envoy.fault,envoy.filters.http.adaptive_concurrency,envoy.filters.http.dynamic_forward_proxy,envoy.filters.http.grpc_http1_reverse_bridge,envoy.filters.http.grpc_stats,envoy.filters.http.header_to_metadata,envoy.filters.http.jwt_authn,envoy.filters.http.original_src,envoy.filters.http.rbac,envoy.filters.http.tap,envoy.grpc_http1_bridge,envoy.grpc_json_transcoder,envoy.grpc_web,envoy.gzip,envoy.health_check,envoy.http_dynamo_filter,envoy.ip_tagging,envoy.lua,envoy.rate_limit,envoy.router,envoy.squash
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:259]   filters.listener: envoy.listener.http_inspector,envoy.listener.original_dst,envoy.listener.original_src,envoy.listener.proxy_protocol,envoy.listener.tls_inspector
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:262]   filters.network: envoy.client_ssl_auth,envoy.echo,envoy.ext_authz,envoy.filters.network.dubbo_proxy,envoy.filters.network.mysql_proxy,envoy.filters.network.rbac,envoy.filters.network.sni_cluster,envoy.filters.network.thrift_proxy,envoy.filters.network.zookeeper_proxy,envoy.http_connection_manager,envoy.mongo_proxy,envoy.ratelimit,envoy.redis_proxy,envoy.tcp_proxy
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:264]   stat_sinks: envoy.dog_statsd,envoy.metrics_service,envoy.stat_sinks.hystrix,envoy.statsd
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:266]   tracers: envoy.dynamic.ot,envoy.lightstep,envoy.tracers.datadog,envoy.tracers.opencensus,envoy.tracers.xray,envoy.zipkin
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:269]   transport_sockets.downstream: envoy.transport_sockets.alts,envoy.transport_sockets.raw_buffer,envoy.transport_sockets.tap,envoy.transport_sockets.tls,raw_buffer,tls
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:272]   transport_sockets.upstream: envoy.transport_sockets.alts,envoy.transport_sockets.raw_buffer,envoy.transport_sockets.tap,envoy.transport_sockets.tls,raw_buffer,tls
[2021-01-16 08:34:39.782][1][info][main] [source/server/server.cc:278] buffer implementation: new
[2021-01-16 08:34:39.784][1][warning][misc] [source/common/protobuf/utility.cc:282] Using deprecated option 'envoy.api.v2.listener.FilterChain.tls_context' from file listener.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2021-01-16 08:34:39.784][1][warning][misc] [source/common/protobuf/utility.cc:282] Using deprecated option 'envoy.api.v2.listener.Filter.config' from file listener.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2021-01-16 08:34:39.784][1][warning][misc] [source/common/protobuf/utility.cc:282] Using deprecated option 'envoy.api.v2.Cluster.tls_context' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2021-01-16 08:34:39.784][1][warning][misc] [source/common/protobuf/utility.cc:282] Using deprecated option 'envoy.api.v2.Cluster.tls_context' from file cds.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2021-01-16 08:34:39.785][1][warning][main] [source/server/server.cc:350] No admin address given, so no admin HTTP server started.
[2021-01-16 08:34:39.785][1][info][main] [source/server/server.cc:458] runtime: layers:

name: base
static_layer:
{}
name: admin
admin_layer:
{}
[2021-01-16 08:34:39.785][1][info][config] [source/server/configuration_impl.cc:62] loading 0 static secret(s)
[2021-01-16 08:34:39.785][1][info][config] [source/server/configuration_impl.cc:68] loading 2 cluster(s)
[2021-01-16 08:34:39.789][1][info][config] [source/server/configuration_impl.cc:72] loading 1 listener(s)
[2021-01-16 08:34:39.792][1][warning][misc] [source/common/protobuf/utility.cc:282] Using deprecated option 'envoy.config.filter.accesslog.v2.AccessLog.config' from file accesslog.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/intro/deprecated for details.
[2021-01-16 08:34:39.792][1][info][config] [source/server/configuration_impl.cc:97] loading tracing configuration
[2021-01-16 08:34:39.792][1][info][config] [source/server/configuration_impl.cc:117] loading stats sink configuration
[2021-01-16 08:34:39.792][1][info][main] [source/server/server.cc:549] starting main dispatch loop
[2021-01-16 08:34:39.794][1][info][upstream] [source/common/upstream/cluster_manager_impl.cc:161] cm init: all clusters initialized
[2021-01-16 08:34:39.794][1][info][main] [source/server/server.cc:528] all clusters initialized. initializing init manager
[2021-01-16 08:34:39.794][1][info][config] [source/server/listener_manager_impl.cc:578] all dependencies initialized. starting workers
[2021-01-16T08:39:01.549Z] "GET /healthz HTTP/1.1" 200 - 0 35 11 10 "-" "Go-http-client/1.1" "030c4549-24ad-44ad-a68f-402caf5f3d37" "<IP_ADDRESS>:31068" "<IP_ADDRESS>:50300"
[2021-01-16T08:39:04.296Z] "GET /healthz HTTP/1.1" 200 - 0 35 0 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "18c73c02-ddf4-40b2-b79d-dafc657c66dc" "<IP_ADDRESS>:31068" "<IP_ADDRESS>:50300"
[2021-01-16T08:39:06.926Z] "GET /healthz HTTP/1.1" 200 - 0 35 0 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "e2305cf9-28ad-4642-b56c-792f4a920367" "<IP_ADDRESS>:31068" "<IP_ADDRESS>:50300"
[2021-01-16T08:39:07.376Z] "GET / HTTP/1.1" 404 NR 0 0 0 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "81346da7-00c6-469f-87ef-dfdda9fbba0c" "<IP_ADDRESS>:31068" "-"
[2021-01-16T08:39:10.654Z] "GET / HTTP/1.1" 404 NR 0 0 0 - "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "2ca4edd5-6cb3-4d31-ac85-dad292c15097" "<IP_ADDRESS>:31068" "-"
[2021-01-16T08:39:10.867Z] "GET /pl.vizier.services.query_broker HTTP/1.1" 401 - 0 22 480 479 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "9f18d78c-5a56-45f2-80d7-5f130dfec456" "<IP_ADDRESS>:31068" "<IP_ADDRESS>:50300"
[2021-01-16T08:39:11.655Z] "GET /pl.api/ HTTP/1.1" 401 - 0 22 463 462 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.0.2 Safari/605.1.15" "dc692909-69e7-4dcb-9f02-4ed135983e1d" "<IP_ADDRESS>:31068" "<IP_ADDRESS>:50300"`

App information (please complete the following information):

Pixie version 0.5.19
K8s cluster version  v1.15.12-eks-31566f

Additional context
With the --passthrough=true everything is working just fine
Also i note that vizier proxy pod is recreating for some reasons, it is not failing(restarting) but recreating every 5 minutes or so.

Hi @Ultrafenrir , thanks for trying out Pixie!
The px proxy command is actually outdated, since we've added authentication in our system (which is why you're seeing the "Must have bearer auth" errors).
You should use the UI (https://work.withpixie.ai/live) or CLI to safely access the data in data isolation mode.
Other users have had confusion about how the data is isolated if you are accessing it through the Pixie-hosted UI, so I wanted to give a brief explanation:

In regular passthrough mode, when you execute a script in our UI, the request is made to Pixie's backend. Pixie's backend is then responsible for forwarding this request to your cluster, then proxying the results back in its response to the UI.
In data isolation mode, when you execute a script in our UI, the request is made directly to the proxy pod running in your cluster instead of to Pixie's backend. Since you are accessing the UI through your browser, which is running on a computer on your network, and the request is made directly to the cluster running on your network, none of the data ever leaves the network. This is why you must be directly on your network, or logged onto VPN, to actually access the data.

If you wanted to access the data through your own self-hosted Pixie UI, that'll be coming soon as we work on open-sourcing our product. So stay tuned!
As for the proxy pod recreating, we haven't seen that case before. Would it be possible to paste the output of kubectl describe for that pod?

Hi @Ultrafenrir , thanks for trying out Pixie!
The px proxy command is actually outdated, since we've added authentication in our system (which is why you're seeing the "Must have bearer auth" errors).
You should use the UI (https://work.withpixie.ai/live) or CLI to safely access the data in data isolation mode.
Other users have had confusion about how the data is isolated if you are accessing it through the Pixie-hosted UI, so I wanted to give a brief explanation:

In regular passthrough mode, when you execute a script in our UI, the request is made to Pixie's backend. Pixie's backend is then responsible for forwarding this request to your cluster, then proxying the results back in its response to the UI.
In data isolation mode, when you execute a script in our UI, the request is made directly to the proxy pod running in your cluster instead of to Pixie's backend. Since you are accessing the UI through your browser, which is running on a computer on your network, and the request is made directly to the cluster running on your network, none of the data ever leaves the network. This is why you must be directly on your network, or logged onto VPN, to actually access the data.

If you wanted to access the data through your own self-hosted Pixie UI, that'll be coming soon as we work on open-sourcing our product. So stay tuned!
As for the proxy pod recreating, we haven't seen that case before. Would it be possible to paste the output of kubectl describe for that pod?


Add stealthybox to Maintainers

Membership from https://github.com/fluxcd/community/issues/234
@kingdonb @stefanprodan @mewzherder @matheuscscp @scottrigby

These folks are all still doing Flux advocacy work on behalf of Flux AFAIK (administrivia: I see at least one spelling mistake/ typo that we should fix on this page, and some affiliations may need updating)
We should revisit the access list further down the page though, as there are a few places where only one person is mentioned as has access according to the listing. Do any core maintainers have access to LinkedIn, Twitter, etc? I know we do not usually list core maintainers on lower level listings, but they should be granted access. Since we have had some team changes, it would be good to make sure each resource has at least two people identified that can manage it.
Also, it may make sense to finally promote some of our long-standing contributors to maintainer in the Community repo
@mewzherder @staceypotter @priyanka-ravi @scottrigby PTAL 🪴 😶🌫


Angular auto import Module or another standalone Component in template like WebStorm

We try to keep VS Code lean and we think the functionality you're asking for is great for a VS Code extension. Maybe you can already find one that suits you in the VS Code Marketplace. Just in case, in a few simple steps you can get started writing your own extension. See also our issue reporting guidelines.
Happy Coding!


Unable to generate Barcode

Unable to generate barcode while converting to html. Any light on how to achieve this is appreciated. Thanks

+1


generating projects with lccgen

I'm trying to use licgen to create a new project , but I'm not sure how to use it
If I'm first trying that:
lccgen project init -n POM
nothing is happening (no text , even with verbose option)
Do I have to provide a rsa private key (link to .rsa files ? or the keys content in the command line ?)
lccgen project init --primary-key pom_private_key.rsa --public-key pom_public_key.rsa --project-name POM
return nothing :-/

I have this problem too, can anyone answer?

same here ! Project is still live ?

Hi,
I am not sure about the latest version but here are my notes when I
evaluated open-license-manager. I don't guarantee that it will work for you
because I did not follow recent developments and I don't know the internal
details of open-license-manager.
The documentation of open-license-manager
https://open-license-manager.github.io/licensecc/usage/issue-licenses.html
suggests to have the executable lcc in your path and organize the project
as follows:
projects└── DEFAULT       #(your project name)    ├── include    │
└── licensecc    │       └── DEFAULT    │           ├──
licensecc_properties.h    │           └── public_key.h    ├── licenses
│   └── test.lic    └── private_key.rsa
Here, DEFAULT is the project name and would be replaced by MYPROJECT, for
example.
The idea is that each project has its settings and licenses. In addition to
DEFAULT (which is used for internal tests of open-license-manager), a new
project can be added by reconfiguring cmake with the following additional
variable -DLCC_PROJECT_NAME=xxx.
When I did so for  MYPROJECT , I ended up with the following directory
structure:
.├── DEFAULT│   ├── include│   │   └── licensecc│   │       └──
DEFAULT│   │           ├── licensecc_properties.h│   │           └──
public_key.h│   └── private_key.rsa└── MYPROJECT    ├── include    │
└── licensecc    │       └── MYPROJECT    │           ├──
licensecc_properties.h    │           └── public_key.h    └──
private_key.rsa
Also, lccgen can be used to generate the project (in fact this is how the
cmake configuration does it). When I tested this, the same directory
structure was generated, but for some reason the file licensecc_properties.h
is not created.
<#create-the-secret-key>
From the above structure we see that the build process generated both the
public and the private key, by using openssl.
For a start, it can be sufficient to remove the public and private key when
rebuilding the project, and this will regenerate both keys.
After compiling the library (cmake --build . --target install --config
Release), the structure of the install directory is as follows:
.├── bin│   ├── lccgen│   └── MYPROJECT│       └── lccinspector├──
include│   └── licensecc│       ├── datatypes.h│       ├──
licensecc.h│       └── MYPROJECT│           ├──
licensecc_properties.h│           └── public_key.h└── lib    ├── cmake
│   ├── lccgen    │   │   ├── lccgen-config.cmake    │   │   ├──
license_generator.cmake    │   │   └── license_generator-release.cmake
│   └── licensecc    │       ├── licensecc-config.cmake    │
└── licensecc-config-version.cmake    └── licensecc        └──
MYPROJECT            ├── cmake            │   ├── licensecc.cmake
│   └── licensecc-release.cmake            └──
liblicensecc_static.a
There is a global lccgen executable, which is common for all projects, and
then a lccinspector specific for each project. I suppose that this is
because the hardware identifier strategy is specific for each project, and
other variables as well.
Also, the include directory from each project's directory is copied as to
the installation include directory, and a static library is generated for
each project. Finally, some .cmake files are added for each project,
probably to facilitate integration if you know how to use it.
Best regards,
Evan Monroig
Le jeu. 13 oct. 2022 à 23:48, Sid-Ahmed @.***> a écrit :

same here ! Project is still live ?
—
Reply to this email directly, view it on GitHub
https://github.com/open-license-manager/licensecc/issues/139#issuecomment-1278212640,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRMGXNOWFRXQ7KI3PDSIRDWDB7R3ANCNFSM6AAAAAAQD3O4FI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

This video might help https://youtu.be/BHb-p-4aaZE?si=_UehJQVSmzQA6fwl


How can I find the Camera Matrix from D435i without Opencv

Required Info

Camera Model
D435i

Firmware Version
<IP_ADDRESS>

Operating System & Version
Win 10 64bits

Platform
PC

SDK Version
2.18.1

Language
Visual Studio 2017(15.9.7) / C++

Issue Description
I wanna find the fx, fy to create the Camera Matrix, but I didn't find any d435i spec. talk about that. Is there any resolution for this issue or readme or any similar problems others faced that can help with get going?

Hi @cookiedog
Check out API-How-To#get-video-stream-intrinsics

Hi @cookiedog
Check out API-How-To#get-video-stream-intrinsics

Thanks for your resolution!

I have one more question, as the camera have various resolution preset, are intrinsic parameters available for each resolution ?

@cichard ,  that's correct - the intrinsic is uniquely calculated per-sensor/per-resolution

If any one interested, intrinsics can be retrieved using rs-enumerate-devices -c.

If any one interested, intrinsics can be retrieved using rs-enumerate-devices -c.
But still have a question on parameters that it sends back. Because when I use Intel.RealSenseCustomRW -rthey are different ...


Draw Quads

Oh this pull request has way to many commits

And I dont know why if file changed I have the files for the orthographic camera as well, I'll try to fix that

Oh this pull request has way to many commits

I think this is due because you don't create branch when developing new feature


ipc: static_vrings: Support DT-defined buffer size

Recently OpenAMP introduced the possibility to set the sizes for TX and
RX buffers per created instance. Expose this also to Zephyr users by
using a DT property "buffer-size".
Signed-off-by: Carlo Caione<EMAIL_ADDRESS>

@mbolivar-nordic let me change that to zephyr,buffer-size, no harm in that.

@arnopo @hubertmis @KAGA164 @kapi-no
Pushing this again with a fix. The problem with the previous submission was that also the remote side must be avare of the buffer size because this value is used to compute SHMEM addresses and other values needed for the communication, see:
https://github.com/zephyrproject-rtos/zephyr/blob/bc1b800a85cf8c42717cfa7f5ed04525d9af8f63/subsys/ipc/ipc_service/backends/ipc_rpmsg_static_vrings.c#L225-L245
The problem was spotted because when using a buffer size > RPMSG_BUFFER_SIZE the communication was failing. This new revision is working correctly for buffer sizes <=> RPMSG_BUFFER_SIZE..
Ready again for review.


Added profile editing feature

Users can now edit their name, email id and phone number.

Merging LGTM!


Docs should mention running "npm install"?

You seem to be making everything perfectly simple, including explaining how to install webpack and the development server globally. But "npm run build" doesn't work unless I do "npm install" first. Seems like it would be simpler and easier to understand for newbies if the docs mentioned the need to do "npm install".

@garyrob I would gladly take a pull request if you can help update the pull request on which steps that you were struggling :)

https://github.com/alicoding/react-webpack-babel/commit/4822efe669552e08de030f2da9bc3e399856990a


User Documentation is missing

When User tries to check user guide a 404 is returned.
http://gpc.github.com/grails-rendering/

Correct link is http://gpc.github.io/rendering/

great thank you

@c0mput3rxz, updated URL is now merged in.


Log files are not closed properly

Hello, Alex!
I found that log files are not closed when they should be. I have a restriction of 1000 open file handles and athena_meta inevitably crushes with error "Too many files are opened".
This sloppy quickfix worked for me (but I'm sure there is a better solution):
In log.py:
  def open_log(self):
    if self.log_file is None:
      self.log_file = open(self.log_path, "w")

to
  def open_log(self):
    pass

and
in  def log(self, message):
    self.log_file.write(message_str)
    self.log_file.flush()

to
   with open(self.log_path, "r+") as log.file:
       log_file.write(message_str)
       log_file.flush()

Hi,
Thank you for the suggestion.  Can I ask how many processes you specified?  An alternative solution would be to set the maximum to below your max file handle limit so that this should never be reached at once.  I’m a bit hesitant to accept your suggested changes because although this can alleviate failure from the restriction, it isn’t failsafe if all 1000 processes write at once.  Let me give it a bit more thought, but I’m happy you’ve found a temporary fix.
Also, not sure what version of Athena you are using, but we did some significant updates that are available on the main branch.  These updates introduced a dependence on a new fork of IDBA, referenced in the updated README, and fixed several bugs to significantly increase performance.  We found whole organisms that were unassembled with the previous version are now put together in <10 large contigs.  I hope you find it useful!  Sorry that there is not yet a tag released for these major revisions; this will come soon when we finalize fixes/updates.
Best!
alex
On Oct 25, 2017, at 11:51 AM, 1dayac <notifications<EMAIL_ADDRESS>wrote:
Hello, Alex!
I found that log files are not closed when they should be. I have a restriction of 1000 open file handles and athena_meta inevitably crushes with error "Too many files are opened".
This quickfix worked for me (but I'm there is a better solution):
In log.py:
def open_log(self):
if self.log_file is None:
self.log_file = open(self.log_path, "w")
to
def open_log(self):
pass
and
in def log(self, message):
self.log_file.write(message_str)
self.log_file.flush()
to
with open(self.log_path, "r+") as log.file:
self.log_file.write(message_str)
self.log_file.flush()
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/abishara/athena_meta/issues/7, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACzgIedwa5Eefc_keqmIve0iTUKadhotks5sv4MZgaJpZM4QGe5n.

Thank you for your answer!
I observed this behaviour as with 1 and with 16 processes - so it is not because I used more processes than the number of possible opened file handles.
I'm using the latest version of Misha Kolmogorov's fork that uses ABruijn instead of Canu for OLC assembly.

Oh hmm, that is definitely a bug then and not desired.  Let me look a bit more into that when I get the chance to see if I can properly address it.  Thanks for pointing this out.
Great, that should contain most of the significant updates.  I will create a tag when we have a proper release version.
Thanks!
alex
On Oct 25, 2017, at 1:13 PM, 1dayac <notifications<EMAIL_ADDRESS>wrote:
Thank you for your answer!
I observed this behaviour as with 1 and with 16 processes - so it is not because I used more processes than the number of possible opened file handles.
I'm using the latest version of Misha Kolmogorov's fork that uses ABruijn instead of Canu for OLC assembly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/abishara/athena_meta/issues/7#issuecomment-339456674, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACzgId_qXjwIrBpEQFs9M3pjYbXVx-Z2ks5sv5aGgaJpZM4QGe5n.

Fixed this in commit ac00c74cf8d1b916c7b, sorry for the delay


TF Rule: S3 bucket policy should not have a wildcard action

Add a new Terraform rule:
An S3 bucket policy should not use a wildcard action.

This rule is covered in cli/assets/terraform.yml and cli/assets/terraform12.yml with rule S3_BUCKET_POLICY_WILDCARD_ACTION


Site-specific search doesn't work; attempts to open as a link instead and fails

When searching for site:producthunt.com change password using the search/URL box at the top, the process fails with a Unable to open this type of link.
Visiting DuckDuckGo.com and typing the same works though.
It's just that searching on the URL box fails.

See also #347

Oh, I completely missed that. I see an open PR against this issue. @subsymbolic, could you advise on which issue could be closed at this stage? 🤔

Thanks @arunsathiya and @GuiltyDolphin. I'll close this one as a duplicate as it came after https://github.com/duckduckgo/Android/issues/347.


some weird letters in generated docs in firefox

When generating docs from specs in UTF-8, it seems like the encoding information probably gets lost because some weird letters will show up in firefox, only tested in firefox 53 on mac.
Firefox opens the docs in "western", when manually changing this in firefox to "unicode", it will show the correct letters.
Then found here: http://stackoverflow.com/questions/29578122/why-there-is-no-utf-8-encoding-in-firefox
to add:
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
to a generated spec html file also will cause firefox to show all letters correct.
Don't know if this is just the way firefox works (see comment in above link "Firefox defaults to latin1") or if it's an option to anyhow read the spec encoding and generate such a meta tag, too.

Closing this as an old issue. This may be fixed in the newer releases.
Will reopen if it still needs fixing.


[Question] Add trial

Is there a way to add a trial, for example when using GPTuner, with para1=10, param2=70 and objective_value=0?

You can click "customized trial" button on web UI to manually add a trial.
However GPTuner will not receive metrics from manually added trials. This is a limitation of the tuner implementation.

How about for the advisor?
advisor:
  builtinAdvisorName: BOHB
  classArgs:
    optimize_mode: maximize
    min_budget: 1
    max_budget: 27
    eta: 3


Application Configuration: Attenuation Duration Enhancements

We need two additional configuration variables for the attenuation duration, namely defaultBucketOffset and riskScoreNormalizationDivisor.
The target config should look like this:
default-bucket-offset: 0 # discussed as W4
risk-score-normalization-divisor: 25 # discussed as W5
thresholds:
  lower: 50
  upper: 70
weights:
  low: 1.0
  mid: 0.5
  high: 0.0

Value range for bucket offset: 0 or 1 (int)
risk score normalization divisor: 1...1000 (int)

@michael-burwig

Proposed .proto file:
syntax = "proto3";
package app.coronawarn.server.common.protocols.internal;
option java_package = "app.coronawarn.server.common.protocols.internal";
option java_multiple_files = true;

message AttenuationDuration {
  Thresholds thresholds = 1;
  Weights weights = 2;
  int32 defaultBucketOffset = 3;
  int32 riskScoreNormalizationDivisor = 4;
}

message Thresholds {
  int32 lower = 1;
  int32 upper = 2;
}

message Weights {
  double low = 1;
  double mid = 2;
  double high = 3;
}


build: enable vendoring dependencies

Setup the support for building SPM with vendored dependencies.  This is preparatory work to enable the build of the LSP which is not possible to build with SPM on Windows and thus prevented from being able to be built and debugged outside of the toolchain build.

This is using a personal branch for swift-certificates as this is waiting on https://github.com/apple/swift-certificates/pull/158 (CC: @yim-lee)

@swift-ci please test

@swift-ci please test


not able to understand api_client.py file please help me understand please

Issues and Contributing

Expected Behavior

Actual Behavior

Possible Solution

Steps to Reproduce (for bugs)

Python code that reproduces the issue:
print("this is only an example Python code block")

Your Environment

Library version or repository branch:
Python version:
Operating System and version:
InsightVM/Nexpose product version:

Other relevant information

@ujjawalmaheshwari Have you attempted any of the samples that have been provided here: https://github.com/rapid7/vm-console-client-python/blob/master/samples/list_assets.py. This should give a decent starting point

sir are you free please sir
i need just one google meet i will be highly grateful if this meet happens please sir

Sir I know  am asking for a lot but please sir help me with this .

Is it possible Sir? Please just few minutes time would be more then enough I am not able to understand why sanitize_for_serialization and deserialize and few other functions are used please sir help me get the concept. Thanking you for the same

@zyoutz-r7 sir please tell me why rapid7vmconsole.Configuration(name='Rapid7') Rapid7 is used please sir


Ship dipstick metrics to grafana cloud

Towards: https://github.com/giantswarm/giantswarm/issues/29351
This PR sends aggregated metrics from dipstick to grafana cloud.
Checklist

[x] Update CHANGELOG.md
[ ] Add Unit tests
[ ] Follow Alert structure
[ ] Consider creating a dashboard (guidelines) (if it does not exist already) to help oncallers monitor the status of the issue.
[ ] Request review from oncall area, as well as team (e.g: oncall-kaas-cloud GitHub group).

Tested on gauss


Range: when resetting the form value, the values of begin and end are not reseted.

When in single selection mode, if we reset the form value driving the selected date, then the value of selectedValue is correctly reseted in the SatCalendarBody component.
But in range mode, this is not the case: the values of begin and end in SatCalendarBody remain unchanged.
I think this is a bug.

How do you reset value?

I tried with both ngModel and formControl (respectively resetting the form by setting the model to null and with form.reset()) and I have the same problem.
But indeed, I made more tests and the problem happens only when I reset the form immediately after the dateChange event.
Wrapping the reset in a setTimeout(() => {...}, 0) solves the problem.
Moreover, this only happens when the closeAfterSelection option is false.
So perhaps it could be solved with a markForCheck somewhere but I don't know where.

Here is a sample to reproduce the bug:
import { Component } from '@angular/core';
import {FormBuilder, FormGroup} from "@angular/forms";

@Component({
  selector: 'app-root',
  template: `
      <form [formGroup]="form">
          <mat-form-field>
              <input matInput
                     placeholder="Choose a date"
                     [satDatepicker]="picker"
                     (dateChange)="dateChange($event)"
                     formControlName="date">
              <sat-datepicker #picker [rangeMode]="true"
                              [closeAfterSelection]="false">
              </sat-datepicker>
              <sat-datepicker-toggle matSuffix [for]="picker"></sat-datepicker-toggle>
          </mat-form-field>
      </form>
`,
  styleUrls: ['./app.component.scss']
})
export class AppComponent {
    form: FormGroup;
    constructor(fb: FormBuilder) {
        this.form = fb.group({
            date: [{ begin: new Date(2018, 7, 5), end: new Date(2018, 7, 25) }]
        });
    }

    dateChange(event) {
        // Do some stuff
        this.form.reset();
    }

}

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.
Don't work this!

I tried in this mode but don't work same:
@ViewChild(SatCalendar, {static: true}) calendar: SatCalendar<Date>     this.calendar.beginDateSelected = false;     this.calendar.beginDate = null;     this.calendar.maxDate = null;     this.calendar.selected = null;     this.calendar.startAt = null; ;
So it's a BUG of library and must to be fix or insert new solution

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.
Don't work this!

I tried in this mode but don't work same:
@ViewChild(SatCalendar, {static: true}) calendar: SatCalendar<Date> this.calendar.beginDateSelected = false; this.calendar.beginDate = null; this.calendar.maxDate = null; this.calendar.selected = null; this.calendar.startAt = null; ;
So it's a BUG of library and must to be fix or insert new solution

You have to pass the values(beginDate and endDate) like below in sat-calender element
<sat-calendar
[beginDate]="calendar.beginDate"
[endDate] = "calendar.maxDate">

The my setup is:
The unser click one day and the week is selected (from Mondato to Sunday). When click other day of week this reset week and re-click day for select week.
The bug is when the user (after clicked the day and selected week) re-click the same day or day in week selected the saturn fire (beginDateSelectedChange) and this work badly.
Example StackBlitz
So i would reset range or send to set null beginDate

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.
Don't work this!

I tried in this mode but don't work same:
@ViewChild(SatCalendar, {static: true}) calendar: SatCalendar<Date> this.calendar.beginDateSelected = false; this.calendar.beginDate = null; this.calendar.maxDate = null; this.calendar.selected = null; this.calendar.startAt = null; ;
So it's a BUG of library and must to be fix or insert new solution

You have to pass the values(beginDate and endDate) like below in sat-calender element
<sat-calendar
[beginDate]="calendar.beginDate"
[endDate] = "calendar.maxDate">

The my setup is:
The user click one day and the week is selected (from Monday to Sunday). When click other day of week this reset week and re-click day for select week.
The bug is when the user (after clicked the day and selected week) re-click the same day or day in week selected, the saturn fire (beginDateSelectedChange) and this work badly.
Example StackBlitz
So i would reset range of days or send to set beginDate = null

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.
Don't work this!

I tried in this mode but don't work same:
@ViewChild(SatCalendar, {static: true}) calendar: SatCalendar<Date> this.calendar.beginDateSelected = false; this.calendar.beginDate = null; this.calendar.maxDate = null; this.calendar.selected = null; this.calendar.startAt = null; ;
So it's a BUG of library and must to be fix or insert new solution

You have to pass the values(beginDate and endDate) like below in sat-calender element
<sat-calendar
[beginDate]="calendar.beginDate"
[endDate] = "calendar.maxDate">

The my setup is:
The user click one day and the week is selected (from Monday to Sunday). When click other day of week this reset week and re-click day for select week.
The bug is when the user (after clicked the day and selected week) re-click the same day or day in week selected, the saturn fire (beginDateSelectedChange) and this work badly.
Example StackBlitz
So i would reset range of days or send to set beginDate = null
NOTE: i don't konow because stackblitz don't work with momentjs. So you must try in local for try work example

Any solution boys??

Hope, maybe it will help you, To reset i have tried like this, passing | assigning the [beginDate] and [endDate] value as null on sat-calendar.
Don't work this!

I tried in this mode but don't work same:
@ViewChild(SatCalendar, {static: true}) calendar: SatCalendar<Date> this.calendar.beginDateSelected = false; this.calendar.beginDate = null; this.calendar.maxDate = null; this.calendar.selected = null; this.calendar.startAt = null; ;
So it's a BUG of library and must to be fix or insert new solution

You have to pass the values(beginDate and endDate) like below in sat-calender element
<sat-calendar
[beginDate]="calendar.beginDate"
[endDate] = "calendar.maxDate">

The my setup is:
The user click one day and the week is selected (from Monday to Sunday). When click other day of week this reset week and re-click day for select week.
The bug is when the user (after clicked the day and selected week) re-click the same day or day in week selected, the saturn fire (beginDateSelectedChange) and this work badly.
Example StackBlitz
So i would reset range of days or send to set beginDate = null
NOTE: i don't konow because stackblitz don't work with momentjs. So you must try in local for try work example

EMPORANY SOLUTION:
I Added SCSS/CSS attributes on root style (style.scss)
`.mat-calendar-body-selected {
pointer-events: none;
cursor: default;
text-decoration: none;
color: black;
}
.mat-calendar-body-begin-range:not(.mat-calendar-body-end-range) {
pointer-events: none;
cursor: default;
text-decoration: none;
color: black;
}
.mat-calendar-body-end-range:not(.mat-calendar-body-begin-range) {
pointer-events: none;
cursor: default;
text-decoration: none;
color: black;
}
.mat-calendar-cell-semi-selected {
pointer-events: none;
cursor: default;
text-decoration: none;
color: black;
}`


Remove crate restrictions on Postgres Types

Why do these need to be public only to the crate?
These are extremely valuable properties to have access to, and is restricting the use cases of this library.
My use case is a cross platform database viewer, with a shared library written in rust. It is powered by react native, so I want to pass all of the raw bytes from Postgres up to the JS layer, where I turn it into JS Types, or make it manipulatable with a UI Component.
An example of my use case implemented with this change:
  async fn query(
    &self,
    id: &u32,
    sql: &str,
  ) -> Result<DatabaseQueryResult, DatabaseError> {
    let instances = _INSTANCES.lock().await;
    if !instances.contains_key(&id) {
      return Result::Err(Box::new(NoConnectionError { id: id.clone() }));
    }
    let connection = &instances[id];
    drop(&instances);

    let query = sqlx::query(sql);
    let result = query.fetch_all(connection).await;
    if result.is_err() {
      return Result::Err(Box::new(result.err().unwrap()));
    }

    let mut columns: Vec<DatabaseColumnInfo> = Vec::new();
    let mut rows: Vec<Vec<Option<Vec<u8>>>> = Vec::new();

    let result_data = result.unwrap();
    if result_data.len() > 0 {
      let column_info = result_data[0].columns();

      for column in column_info {
        let type_info = column.type_info();

        columns.push(DatabaseColumnInfo {
          name: column.name().to_string(),
          data_type: type_info.oid().to_string(),
        });
      }

      for row in &result_data {
        let mut data: Vec<Option<Vec<u8>>> = Vec::new();
        for ordinal in 0..column_info.len() {
          let value_ref = row.try_get_raw(ordinal).unwrap();

          let mut value: Option<Vec<u8>> = None;
          if value_ref.value.is_some() {
            let value_bytes = value_ref.value.unwrap();
            value = Some(value_bytes.to_vec());
          }
          data.push(value);
        }
        rows.push(data);
      }
    }

    let payload = DatabaseQueryResult { columns, rows };
    return Result::Ok(payload);
  }

In API design you typically want to expose the smallest API surface possible.
The issue with making everything public is it significantly restricts our ability to make internal refactors. Making all this stuff public means making stability guarantees about APIs that we haven't put a whole lot of thought into because we only use them internally right now.
It sounds like your use-case may be better served with an ability to serialize the PgRow to JSON: https://github.com/launchbadge/sqlx/issues/182

Yeah, discussed this with @mehcode and we're not comfortable stabilizing this great of an API surface at this time. We're interested in supporting serialization for Rows which is being discussed in #182 as I linked previously.

@abonander @mehcode Cool, I will check out the new row info changes.
Do you think we could open a new change to make as_bytes public for the database value? I think it is valuable to be able to get the raw values so we can do our own parsing of the values.


Fail to build with target no-modules with --dev flag

🐛 Bug description
wasm-pack build --target no-modules --dev  doesn't work.
wasm-pack build --target no-modules  works.
wasm-pack build --dev works.
It's worked with wasm-pack build --target no-modules until today, but suddenly it doesn't work.
console log
    Finished dev [optimized + debuginfo] target(s) in 0.06s // << Cargo check or build done i guess?
[WARN]: :-) origin crate has no README
[INFO]: Installing wasm-bindgen...
error: cannot import from modules (`env`) with `--no-modules` // << ?????
Error: Running the wasm-bindgen CLI
Caused by: failed to execute `wasm-bindgen`: exited with exit status: 1
  full command: "/home/namse/.cache/.wasm-pack/wasm-bindgen-e63eccbd87203048/wasm-bindgen" "/home/namse/rust/luda-editor/luda-editor-client/target/wasm32-unknown-unknown/debug/luda_editor_client.wasm" "--out-dir" "/home/namse/rust/luda-editor/luda-editor-client/pkg" "--typescript" "--target" "no-modules" "--debug"

🤔 Expected Behavior
wasm-pack build --target no-modules --dev  should work as before.
👟 Steps to reproduce
just run wasm-pack build --target no-modules --dev
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.2
rustc version: rustc 1.56.1 (59eed8a2a 2021-11-01)

It's not reproduced in new project so I think it's the problem with my project. let me see.


[Discussion] Next.js application pattern

Hello and greetings from Sonos!
First off, I just wanted to say thank you for supplying an amazing repo of patterns.  This has inspired us to start tackling one of our more challenging deployments and hopefully convert it to something anyone can use.
I wanted to chat about application frameworks like Next.JS.  These frameworks provide end-to-end application development experience that makes it very appealing to development teams.  The only issue is that they want you to spend money on their hosting platform versus providing any guidance on how to host yourself.
https://nextjs.org/docs/deployment
Their basic solution for you is to spin up an EC2 and run the start script.  I'm sure we could also explore using ECR/ECS with containers but where's the fun in that.  We want a serverless solution!
The Serverless community has built a somewhat working solution here https://serverless-nextjs.com/ but its definitely lacking Next.JS features and I'm not 💯  sure about their approach.  CloudFront + Lambda@edge used for APIs, etc.
The Terraform community has built another solution here https://registry.terraform.io/modules/dealmore/next-js/aws/latest and is also lacking some core NextJS features and appears to still be in active development.  I do like their approach to the serverless architecture here.  It just feels better and isn't forced like the Serverless approach is.
I was hoping this community could band together and vet each solution to come up with a proper pattern for these types of application frameworks 🤞
Cheers,
Andrew

This could be an option - https://github.com/dabit3/next.js-cdk-amplify-workshop

This could be an option - https://github.com/dabit3/next.js-cdk-amplify-workshop

Aye, I've looked into these sort of patterns in the past and I want to like Amplify.  It still doesn't support backend routes from NextJS (think SSR routes, or dynamic routes).  It still relies on Serverless to deploy the entire NextJS app out to Cloudfront. https://github.com/dabit3/next.js-cdk-amplify-workshop#deployment-with-serverless-framework.
I'll start creating some diagrams next week to start the conversation.  I think we can combine a few of the patterns laid out here into a best practice NextJS pattern.

Yes, I agree that the full SSR deployment on AWS is complicated, that is, not only on AWS, but the SSR architecture is a complicated thing.
Months ago I did a lab and deployed a small SSR solution (NuxtJS) using Lambda @ Edge + Cloudfront and it works well.
Count on me to discuss this and try to create a pattern for it using the CDK.


Allow optionally including the port number on images and playlists.

Is your feature request related to a problem? Please describe.
Running threadfin behind a reverse proxy makes it difficult when the guide adds the port number and protocol into both the m3u file and the xml file.  Plex when you have tls "required" will force upgrade any http connection to https.  So while threadfin is listening on port 34400, and is running on http://localhost:34400/, plex is forcing to "https" which is not in use.  The reverse proxy is configured for the domain on 443, and does the tls termination, and then passes the traffic to 34400.
Describe the solution you'd like
Allow setting the threadfin destination and a toggle on weather or not to include the port in the playlist / image links.
Describe alternatives you've considered
Allow a post processing script that allows running sed commands.  This would be beneficial if I wanted to change channel names to use part of the description.  For example, NFL Football is the title for any nfl game, and I may want to inject the team name into the title of the show instead.
Additional context
none

Have you tried setting these options in threadfin settings?

This is working perfectly for me. My m3u and xml have no port in them.
The stream url in the m3u is then:
https://threadfin.internal.mydomain.xyz/stream/f58280c7
The reverse proxy then just directs the request to threadfins port 34400

Threadfin is essentially a proxy as well. The URL threadfin uses to connect to your provider is the one in the m3u from your provider. If its http then Threadfin will use http. Plex connecting to Threadfin via https though should satisfy its need for ssl.

FWIW: I agree that it doesn't make sense that the "ForceHTTPS" bool would cause TF to override whatever prototocl is specified in the Playlist m3u, but it does look it's intentionally coded this way.
IMO, it'd make sense to remove this section: https://github.com/Threadfin/Threadfin/blob/ecc998444875e4f36efc2e6b715a77823f30e99c/src/webserver.go#L132C1-L142C1

It makes perfect sense as HTTPS has to be port 443. Apps like Plex and Jellyfin typically only work over 443 for HTTPS

WIW: I agree that it doesn't make sense that the "ForceHTTPS" bool would cause TF to override whatever prototocl is specified in the Playlist m3u, but it does look it's intentionally coded this way.

Sure, https and port 443 make perfect sense, but not in all cases rewriting the m3u urls is wanted. Maybe an additional option "Force https for images only" would be an option?

Yet the links in "Server Information" still contain the port
http://threadfin.domain.com:34400/m3u/threadfin.m3u

as long as you have force https not activated, the port will not be rewritten

It makes perfect sense as HTTPS has to be port 443. Apps like Plex and Jellyfin typically only work over 443 for HTTPS

Sure, https and port 443 make perfect sense, but not in all cases rewriting the m3u urls is wanted. Maybe an additional option "Force https for images only" would be an option?

In the case of HTTPS and SSL Certificates, if 1 URL is HTTPS they ALL have to be. That is how it works. You CANNOT and SHOULD NOT mix HTTP with HTTPS


implement more SIMD intrinsics

Requires https://github.com/rust-lang/rust/pull/94681
With this, the cast, i32_ops, and f32_ops test suites of portable-simd pass. :)
Cc https://github.com/rust-lang/miri/issues/1912

@bors r+

:pushpin: Commit b87a9c90e1ca983eb81778d79b23db8c52eace54 has been approved by RalfJung

:hourglass: Testing commit b87a9c90e1ca983eb81778d79b23db8c52eace54 with merge 64b086a8e26cbf7daddcf4581e6351a55718a913...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 64b086a8e26cbf7daddcf4581e6351a55718a913 to master...


Nutrition Facts Page: view jumps to empty Serving size field when clicking unit buttons

What
On the Nutrition Facts edit page, the view jumps to the empty Serving size field when clicking unit buttons on the right side of page.
Steps to reproduce the behavior

Go to Nutrition Facts page for a product
If the Serving size field is empty, proceed to step 3. If not, clear the Serving size field
Choose a nutrient and change its value
Click the unit button for that nutrient
See view jump to Serving size field

Expected behavior
Expect view to remain unchanged when clicking button
Smartphone model

Device: Pixel 6a
OS: Android 13
App Version: 4.1.0+848

@zanovis Today I was not able to reproduce this issue, on an iOS emulator.
Do you still have this issue, e.g. with 4.3.0? Could be android-related.

Yes, I observed this on 4.3.0 yesterday on Android 13

@zanovis I've just tried again and still could not reproduce the issue on my ios emulator.
That said, I've fixed slightly related lines in #3716, which may fix that issue too.

@zanovis I've managed to reproduce it on my android smartphone.
About to PR a fix...


X-B3-TraceId different from x-cloud-trace-context

Hi All,
I ran into an issue with Tracing.
We have a legacy service which is using spring cloud gcp version 1.1.3.RELEASE and spring boot 2.2.9.RELEASE. When this service calls another service within GCP, I am seeing two headers in the request in the receiving service, one is X-B3-TraceId (value: a2e133bea066bd99b312d26ab2c8daeb) and the other is x-cloud-trace-context(value: 3a123f008baede015d011883f0c1f1c7/12431584679717275694). I don't know if anyone can tell us how these two different values are generated. I tried the same case with our new service using GCP version 1.2.5.RELEASE and spring boot 2.3.2.RELEASE, and these two headers are with the same value.
In addition, I am also seeing another header X-B3-SpanId (value: 99aaa0c8fca9eb90). When X-B3-SpanId is not provided or with invalid value, even if x-cloud-trace-context is different from X-B3-TraceId, the nginx log can be aggregated with application log because these two are all using x-cloud-trace-context as traceId. However, when X-B3-SpanId is provided with valid value and when X-B3-TraceId is different from x-cloud-trace-context, the nginx log will use x-cloud-trace-context and application log will use X-B3-TraceId, which makes logs unable to be grouped. I don't know if this is designed or a bug?
I really have no idea to fix this issue. In the legacy service, I even tried upgrade spring cloud gcp and spring to new version, I am still seeing different values for X-B3-TraceId and x-cloud-trace-context. I guess these may also be some issue beyond spring boot & GCP.
Please kindly offer your help. Thank you.

First off, both 1.1.x, which is ancient, and 1.2.x version of Spring Cloud GCP are no longer supported. You should upgrade to version 2.x.
Nonetheless, just to give you an idea of what might be going on...
The x-cloud-trace-context header is something that is populated by GCP. All of the X-B3... headers are used by Brave/Spring.
At some point, we added a customization to Brave that ensured that if x-cloud-trace-context was present, it would be transated to X-B3.... In the absence of the adapter, even when an x-cloud-trace-context is present, Brave won't see it, and will generate a new trace id in X-B3-TraceId. That's probably what is happening in the legacy service. Version 1.2.5 definitely has the adapter that coordinates both headers to avoid generating new trace IDs when one is already present.

@meltsufin, This helps a lot. Thank you.


Add workflow to check compatibility

All the issues linked here confirmed that all plugins have passing gradle assemble and mavenlocal() as their first repository in build.gradle are closed now: https://github.com/opensearch-project/opensearch-devops/issues/114
Description
This change adds a workflow to check the compatibility with all the plugins in opensearch-project. It adds a comment if any component is incompatible. Example: https://github.com/gaiksaya/OpenSearch/pull/7#issuecomment-1623129382
Related Issues
https://github.com/opensearch-project/opensearch-devops/issues/114
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Hi @nknize This PR is ready for review. Please let me know if it needs any changes. Thanks!

I looked at https://github.com/gaiksaya/OpenSearch/pull/7#issuecomment-1623129382 and it outputs this.
> Task :test:external-modules:test-delayed-aggs:publishNebulaPublicationToMavenLocal
> Task :test:external-modules:test-delayed-aggs:publishToMavenLocal
> Task :checkCompatibility
Compatible components: [https://github.com/opensearch-project/common-utils]

It tells me what's "incompatible" (I suppose it means it didn't build), but doesn't really give me anything actionable like a log, or a reason. What is one supposed to do when they see an error from this check?

I looked at gaiksaya#7 (comment) and it outputs this.
> Task :test:external-modules:test-delayed-aggs:publishNebulaPublicationToMavenLocal
> Task :test:external-modules:test-delayed-aggs:publishToMavenLocal
> Task :checkCompatibility
Compatible components: [https://github.com/opensearch-project/common-utils]

It tells me what's "incompatible" (I suppose it means it didn't build), but doesn't really give me anything actionable like a log, or a reason. What is one supposed to do when they see an error from this check?

The log or reason can be viewed on the workflow itself: https://github.com/gaiksaya/OpenSearch/actions/runs/5472486309/job/14817298994
Regarding action item, that is next in queue to create GitHub issues in respective component repo once the concerned PR is merged.

@dblock @gaiksaya Whats the next steps to get this PR merged?

Moving forward with this PR.
Will monitor if this change is working as intended. If it is, the next step as stated above will be creating GH issues in all incompatible components repositories when the pull request breaking things is merged in this repository.
Thanks!


new website design

moved current design to folder old
added new design

to do:

merge changelog xml code from old design

Thank you!
I don't want to merge this request to master since it breaks existing links, at least to a changelog. Will do this via file copying...

I agree that we don't need additional andstatus folder.
Stylesheet should be external, one for all pages (like it was earlier).

You stated reasonable issues. I fixed them in a new commit, see pull request.

Hi @vinzv , I pulled your changes into another branch, where we can complete new design. Please see https://github.com/andstatus/andstatus/tree/web-design-243


Question about iperf

Hi,
I was trying to run iPerf between 2 different ground stations with Starlink constellation of 100 satellites and 36 ground stations. The two ground stations are node 101 and node 104. I found that, even though, node 101 can perform iPerf as a client to 104 (as a server), it does not work the other way around. They can ping each other, and their routing tables are the same and are shown as follows:
node 101:
<IP_ADDRESS>/24  proto bird  metric 32
        nexthop via <IP_ADDRESS>  dev B101-eth32 weight 1
        nexthop via <IP_ADDRESS>  dev B101-eth88 weight 1

node 104:
<IP_ADDRESS>/24  proto bird  metric 32
        nexthop via <IP_ADDRESS>  dev B104-eth32 weight 1
        nexthop via <IP_ADDRESS>  dev B104-eth88 weight 1

I also used traceroute to understand the routing hops for both directions. The packets from 101 can reach node 104 through 1 satellite hop, but packets from 104 cannot reach 101. The results from traceroute are shown as follows:
101 to 104:
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 30 hops max, 60 byte packets
 1  ovs_container_32.GSL_32-101 (<IP_ADDRESS>)  35.379 ms  35.363 ms  35.370 ms
 2  <IP_ADDRESS> (<IP_ADDRESS>)  70.115 ms  70.126 ms  70.131 ms

104 to 101:
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 30 hops max, 60 byte packets
 1  * * *
 2  * * *
 3  * * *
 4  * * *
 5  * * *

Does anyone know what might go wrong in my setup?
Thank you.

It seems that you use the main branch of StarryNet. Depending on the OS release and Docker version, Docker may apply some filter rules to packets with specific address, port or other conditions. I guess that's why iperf packets are intercepted.
We recommend that you use the dev branch of StarryNet，which deprecates Docker for its high memory consumption and long start-up time. For your problem, it doesn't apply filter rules anymore so the iperf packets can reach the other end. This branch is experimental and we will continue to improve it.
If you are interested in the filter rules mentioned above,  you can check the nftable or iptable rules for verification. Use Linux command nft or iptables to check those rules related to Docker.


Re: Automatic baseline calibration

How do I switch ABC off? @mikan

@Akshul-pirhoalpha Is it the ASC (automatic self calibration)? The ASC isn't been ported yet, but is in the original code:
https://github.com/adafruit/Adafruit_CircuitPython_SCD4X/blob/main/adafruit_scd4x.py#L174-L187


[CS] Send logs to Loggly (if available)

Move to Log4j2 (for proprty substitution in configuration)
Configure Log4j2 with a syslog appender
Link a "loggly" container as "syslog" in @.service.template (this will set the required environment variables used in the configuration)

Pivotal story: 102023108

Just curious: Why not logback? I was under the impression that "just use logback" was the advice du jour for JVM logging.

@cap10morgan We were already using Log4j. And the Log4j2 about page throws some shade at Logback: "Log4j 2... provides many of the improvements available in Logback while fixing some inherent problems in Logback's architecture"
In either case, they are both widely used and this was an upgrade, not a lateral move.

Gotcha, makes sense. The logging library wars will rage on it seems.

Shiny! So clean. LGTM.


Microsoft Graph v1.0: teams channel get

The teams channel get command uses the beta endpoint to filter groups as shown below.
The resourceProvisioningOptions filter is not supported in the v1.0 endpoint, but the displayName filter is, therefore we should consider using the v1.0 endpoint instead and use JavaScript to filter the response by resourceProvisioningOptions.
https://github.com/pnp/cli-microsoft365/blob/266fd8d68e2a71a9c3d8d58d5c133916193f99b9/src/m365/teams/commands/channel/channel-get.ts#L46-L52

@pnp/cli-for-microsoft-365-maintainers any thoughts?

This approach has also been used in several other commands, listed below

team list
team channel list
team conversationmember add
team conversationmember list

I've also found in the documentation that in certain circumstances there are Teams that may not have the resourceProvisioningOptions property set.
Get a list of groups: https://docs.microsoft.com/en-us/graph/teams-list-all-teams?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#get-a-list-of-groups

I've also found in the documentation that in certain circumstances there are Teams that may not have the resourceProvisioningOptions property set.
Get a list of groups: https://docs.microsoft.com/en-us/graph/teams-list-all-teams?context=graph%2Fapi%2F1.0&view=graph-rest-1.0#get-a-list-of-groups

Hi,
unfortunately there is not a more efficient way to retrieve Teams than by using this technique. The Teams SDK uses the same technique to return Teams.
The resourceProvisioningOptions issue should not happen very often these times. Nevertheless, we should at least document this.
Last but not least, I would not move to the v1.0 endpoint yet. Filtering client side will be a pain for customers having a big amount of Groups.
Cheers

If there is a v1.0 of the endpoint available, we should consider using it instead of a beta that could change any moment without any upfront notice and break us. Yes, the v1.0 is less efficient than the beta, but if for some reason the beta stops working altogether, we'd have a bigger problem. One thing that we should consider is to submit a feature request for the Teams team to introduce support for resourceProvisioningOptions in the v1.0 API.

If there is a v1.0 of the endpoint available, we should consider using it instead of a beta that could change any moment without any upfront notice and break us. Yes, the v1.0 is less efficient than the beta, but if for some reason the beta stops working altogether, we'd have a bigger problem. One thing that we should consider is to submit a feature request for the Teams team to introduce support for resourceProvisioningOptions in the v1.0 API.

With this reasoning we should never use a beta endpoint in our CLI. Fine with that decision. Do we all agree with that?

I think we should look to use v1.0 endpoints as a default wherever possible, this ensures that we are using stable endpoints that are supported in production scenarios.
We should only look to use beta endpoints when there is no other option and we document it as such, an example would be todo commands.
The resourceProvisioningOptions filter is used in conjunction with the displayName filter in the examples I have given, so whilst there is a client side overhead I don't see that this would cause a huge a issue as the bulk of the filtering is performed on the displayName.
I am happy to speak to the Graph Team about seeing if resourceProvisioningOptions can be promoted to v1.0 as @waldekmastykarz has suggested.

With this reasoning we should never use a beta endpoint in our CLI. Fine with that decision. Do we all agree with that?

Agreed with @garrytrinder reasoning. If there is no other way out, we can use beta, with a proper remark in our docs, that the command might change. When there is a v1.0 API available, we should update the command to use to ensure that our users can rely on CLI.

With this reasoning we should never use a beta endpoint in our CLI. Fine with that decision. Do we all agree with that?

Agreed with @garrytrinder reasoning. If there is no other way out, we can use beta, with a proper remark in our docs, that the command might change. When there is a v1.0 API available, we should update the command to use to ensure that our users can rely on CLI.

When there is a v1.0 API available, no beta features should be considered at all then for that specific endpoint. Do you both agree?

When there is a v1.0 API available, no beta features should be considered at all then for that specific endpoint. Do you both agree?

So this is tricky, because how changes on Microsoft Graph are implemented. Say Microsoft works on a new API that's available only in beta. In that case, we'd use the beta endpoint in the CLI. When the functionality arrives to v1.0, we'd switch to v1.0. But then, when Microsoft starts working on new functionality, that would be available only in beta, we could consider using that functionality and jump back to the beta endpoint. I think it all depends on the functionality and demand for a particular feature from the community. Not sure if we can cover it with a blanket statement like never/always.

But then, when Microsoft starts working on new functionality, that would be available only in beta, we could consider using that functionality and jump back to the beta endpoint. I think it all depends on the functionality and demand for a particular feature from the community. Not sure if we can cover it with a blanket statement like never/always.

This is what I mean. Its either black or white here. Otherwise it is blurry and would also not count in this issue

I don't think we can have a never/always answer for this question as there will always be exceptions.

I see two possible activities here

Leave the implementation as is using the beta endpoint, in this case I think we should include a comment in the code base so that we document our decision to use the beta endpoint, or
Implement the v1.0 endpoint in the request, keeping the displayName filter but removing the resourceProvisioningOptions filter, filter the request response using JavaScript to remove any groups that are not Teams

I personally would prefer to implement option two.

I see two possible activities here

Leave the implementation as is using the beta endpoint, in this case I think we should include a comment in the code base so that we document our decision to use the beta endpoint, or
Implement the v1.0 endpoint in the request, keeping the displayName filter but removing the resourceProvisioningOptions filter, filter the request response using JavaScript to remove any groups that are not Teams

I personally would prefer to implement option two.

Based on the discussion we only have option 2 left.

+1 for option 2

Spec updated, thank you for your input @plamber and @waldekmastykarz 👍🏻

Hi @garrytrinder, May I take this up!

@ktskumar awesome! Appreciate the help!


Todo list

Creating  a todo list using react

Thank you for your response sure
On Sun, 1 Oct 2023, 18:09 Kritika Gupta, @.***> wrote:

Assigned #4 https://github.com/Kritika30032002/ReactCreations/issues/4
to @Swastik200 https://github.com/Swastik200.
—
Reply to this email directly, view it on GitHub
https://github.com/Kritika30032002/ReactCreations/issues/4#event-10519540678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXNS7FQNWZR7XNY6RFJODV3X5FQB5ANCNFSM6AAAAAA5OJJHBY
.
You are receiving this because you were assigned.Message ID:
@.***
com>

Plz check and confirm
On Sun, 1 Oct 2023, 22:07 SWASTIK MISHRA, @.***>
wrote:

Thank you for your response sure
On Sun, 1 Oct 2023, 18:09 Kritika Gupta, @.***> wrote:

Assigned #4 https://github.com/Kritika30032002/ReactCreations/issues/4
to @Swastik200 https://github.com/Swastik200.
—
Reply to this email directly, view it on GitHub
https://github.com/Kritika30032002/ReactCreations/issues/4#event-10519540678,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXNS7FQNWZR7XNY6RFJODV3X5FQB5ANCNFSM6AAAAAA5OJJHBY
.
You are receiving this because you were assigned.Message ID:
@.***
com>

Can u please me this??

?

I will add todo list project can you please assign me this @Kritika30032002

?

PLEASE ASSIGN ME i WILL BE CREATING A TO-DO LIST


The python version 3.6.9 is not supported anymore.

Kindly elaborate.

Not planning to provide such maintenance support for this repo.


[Live-Site] Created panel component

Issue
Closes #462
What is the change?
I have added the panel component for live site.
Is Development Tested?

[x] Yes
[ ] No

Before / After Change Screenshots

Desktop Full Image

Individual Component Image

Mobile Image

Note :
What to delete and what not to

Keep the headings and answer the questions.
Delete the examples
Delete the description below headings What is the change? & Before/After Screenshots

@satyam73 Adding few comments regarding the UI

Why making these right aligned, why not center aligned. I think it will look much better if it's center aligned

Can we please use same family of icons here like having same stroke width ? Use fortawesome/fontawesome which is already included in the codebase (package.json) https://fontawesome.com/icons/screen-users?f=classic&s=solid
Have some padding in icons so that icon and icon background look visually good
In mobile/tablet view, use small font and icons sizes, take reference from the navbar elements and place the values relatively.

The rest things I can do but I wasn't able to find the relatable icons in fontawesome that's why used this.

Hey @rohan09-raj here's the updated screenshots of the same.

Updated Image (Desktop)

Updated Image (Individual Component)

Updated Image (Mobile )


Wrong links in task output

We are using this task 'trstringer/manual-approval' for manual approval process in enterprise server.
in output can see different urls, mixed formats, either pointing to github.com or to local endpoint, but not clickable because it drives you to api link..
This issue is to address those links formats and make them clickable.
Thx.

In issue description also wrong links, should point to local Github Enterprise Server

The issue should have been fixed with https://github.com/trstringer/manual-approval/pull/125 and https://github.com/trstringer/manual-approval/pull/112.
@trstringer we need a release to see the changes on trstringer/manual-approval@v1
@DenisBalan alternatively you may point your action to main branch (trstringer/manual-approval@main) until a release is published.

@trstringer Could we release a new version with the fix?

@trstringer please progress this
also linked to #128

@trstringer 🙏🏾

Yeah I'm also seeing the same issue with the wrong link being provided.
The "api" prefix should be removed from the URL link.

Would love to see this fix released as well!

@yuqu I don't believe those commits fix the issue. If I pin the sha containing those commits, I still get see the api.github.com url in the issue body.
For reference, the (sanitized) workflow step configuration:
# jobs.*.steps:
    - name: Manual Gate
      if: ${{ env.deploy_environment == 'QA' }}
      timeout-minutes: 15
      # pin: two url bugfixes not yet included in a release (as of 1.9.1)
      uses: trstringer/manual-approval@d2e412d84000579996fd00d7834a817f92af19d3 # or 51b76c4576aad25fefe130f04f4cc4de75814e94, same result
      with:
        secret: ${{ steps.team-approval-auth.outputs.token }}
        approvers: qa-approvers
        minimum-approvals: 1
        issue-title: "Deploying to ${{ env.deploy_environment }}"
        issue-body: >
          Please approve or deny the deployment to
          ${{ env.github_environment }}
          from ${{ github.ref_type }} ${{ github.ref_name }}
        exclude-workflow-initiator-as-approver: true
        additional-approved-words: ''
        additional-denied-words: ''

And the created Issue:
Title:

Manual approval required for workflow run<PHONE_NUMBER>1: Deploying to QA

Body:

Please approve or deny the deployment to QA from branch fix/manual-approval-link
Workflow is pending manual review.
URL: https://api.github.com/ORG/REPO/actions/runs/12345678901
Required approvers: [usera userb userc]
Respond "approved", "approve", "lgtm", "yes" to continue workflow or "denied", "deny", "no" to cancel."

Hello, do you have an update when the new release will be out?


bug: walletClient compatible with ethers ContractFactory?

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.0.5
Current Behavior
I'm attempting to create a contract using ethers.js and wagmi but getting a ts trying to pass the walletclient (signer) into ContractFactory:

If ignore the ts error with below i get other errors cause it doesnt thing its a signer
_async_to_generator.mjs:6 Uncaught (in promise) Error: invalid signer (argument="signer", value={"chain":{"id":11155111,"network":"sepolia","name":"Sepolia","nativeCurrency":{"name":"Sepolia Ether","symbol":"SEP","decimals":18},"rpcUrls":{"alchemy":{"http":["https://eth-sepolia.g.alchemy.com/v2"],"webSocket":["wss://eth-sepolia.g.alchemy.com/v2"]},"infura":{"http":["https://sepolia.infura.io/v3"],"webSocket":["wss://sepolia.infura.io/ws/v3"]},"default":{"http":["https://rpc.sepolia.org"]},"public":{"http":["https://rpc.sepolia.org"]}},"blockExplorers":{"etherscan":{"name":"Etherscan","url":"https://sepolia.etherscan.io"},"default":{"name":"Etherscan","url":"https://sepolia.etherscan.io"}},"contracts":{"multicall3":{"address":"0xca11bde05977b3631167028862be2a173976ca11","blockCreated":6507670}},"testnet":true},"key":"wallet","name":"Wallet Client","pollingInterval":4000,"transport":{"key":"custom","name":"Custom Provider","retryCount":0,"retryDelay":150,"type":"custom"},"type":"walletClient","uid":"7222dc8b4a4","account":{"address":"0x66c2801e144A0BA4d7F6aFF62f535F312aaF609a","type":"json-rpc"}}, code=INVALID_ARGUMENT, version=contracts/5.7.0)
    at Logger.makeError (index.js:224:1)
    at Logger.throwError (index.js:233:1)
    at Logger.throwArgumentError (index.js:236:1)
    at new ContractFactory (index.js:928:1)
    at eval (DeployContract.tsx:42:17)
    at step (tslib.es6.js:147:1)

versions:
npm ls ethers
├──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      ├─┬<EMAIL_ADDRESS>      │ └─┬<EMAIL_ADDRESS>      │   └──<EMAIL_ADDRESS>deduped
      └─┬<EMAIL_ADDRESS>        └──<EMAIL_ADDRESS>deduped

Expected Behavior
im expecting the signer to work as the migration guide here says thats what it is
Steps To Reproduce
run code as shown above and below:
   const { data: walletClient } = useWalletClient();

  const handleSubmit = async (evt: FormEvent<HTMLFormElement>) => {
    evt.preventDefault();
    const NFT = new ContractFactory(
      NFTContract.abi,
      NFTContract.bytecode,
      walletClient as any
    );
    console.log(NFT);
    const nft = await NFT.deploy(
      'MyNFT',
      'MNFT'
    )
    await nft.deployed();
    console.log(nft);
  };

Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

I am also having this exact issue


Linked Properties not visible in the EdgeDB UI Data Explorer

EdgeDB Version: CLI 2.0.4+a7fc49b
OS Version: macOS 12.0.1 (21A559)

Steps to Reproduce:

Add a linked property to your schema. Run your migration and then refresh the EdgeDB UI.
See that the linked properties are not shown anywhere.
Notice how you can still query for them in the REPL.

Schema:
  type Roster {
    required link team -> Team;
    required link player -> Player {
      property position -> FieldPosition;
      property number -> str;
    };
    required link season -> Season;
    required property isActive -> bool {
      default := true;
    };

    constraint exclusive on ((.team, .player, .season));
  }

EdgeDB UI:

REPL:

https://github.com/edgedb/edgedb-ui/issues/11


Ability the user's to register their FIDO devices during the authentication

During MFA with FIDO, It is nice to have an option for the end-users to register their FIDO devices during the authentication.
This is already available in the Email OTP and the SMS OTP. The user is able to fill in their email address or the mobile number during the authentication.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


engine(module_resolver): Fix build for no_std

Initialize a dummy module resolver instead of None, as in Engine::new_raw()
Related change: https://github.com/jonathandturner/rhai/commit/dc4e52e7954db4f52da0cbb917806961003c9eb6#diff-ff278ec599adfd033d35a083ebe8948db8bf177c9817dee8ddc4f3a9e3f5728eR767

Ouch!  I better change my CI example of no_std to catch this.


Fix RePaint: use ground-truth in the last in-painting step

Dear @lucidrains,
I have found an imperfection of the RePaint method. In the last in-painting step (when t=1 and we denoise the image to get the restored x_{t=0}) the ground-truth image is not used in the area were the mask is positive. This leads to more blurry images as @nilsleh mentioned in another issue.
By using the ground-truth image (provided as input alongside the mask) in the last step, we make sure that we use the real image where we are not meant to reconstruct any missing part, and we only perform the RePaint algorithm in the missing section marked with the mask.
Let me know if any questions 👍

lgtm!


mod breaks lobby by changing the host's game version?

Not sure if this is an issue with this mod or its dependencies. With this enabled, you're unable to join the host's lobby because of a disparity in versions, where the joiner's is 40 and the host's is ~16470.
Our versions are the same; we verified the game files; we ensured that we had the same mods, to no avail. Still, sorry if it's actually just an issue with the dependencies.

Hey @Luminouscales. Are you still having this issue? I saw this myself a couple of times but restarting the game always fixed it for me

Yeah, still the same issue, I'm afraid.

Hi! this issue is still happening, we got it yesterday and today and was a a bit of work to figured out which mode was giving the failure and turn out was this one :'(

I have the same issue, I couldn't figure out which mod was the culprit, glad you made this issue thread!


Streamline AppId and DaprId

Describe the proposal
Inside the runtime, the cli, the docs and in pictures the terms "App ID, "Dapr App ID" and "Dapr ID" are used interchangeable and it seems, that "Dapr ID" was the old naming, "App ID" the new naming.
E.g. dapr.exe with app-id and daprd.exe with dapr-id
It would be beneficial for maintainers, users/developers and new people coming to this project for using only "App ID" with an optional "Dapr" before in all situations to make clear it refers to the same thing.

@pruthvidhodda can you please file the pr on cli repo ?

Done.


fix build with appveyor warning

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


Type checking in float/int distribution bin configs is broken

Submitted by both @bobular and @dpbisme.
The distribution endpoint on dev (dfalke-b) and qa is giving a 400 response with what seems to be a reasonable request:
Error: 400 Bad Request
{"status":"bad-request","message":"Variable OBI_0001169 of type INTEGER: displayRangeMin must be an integer value."}
POST data to https://localhost:3000/eda-subsetting-service/studies/SCORESL01-1/entities/EUPATH_0000096/variables/OBI_0001169/distribution:
{"valueSpec":"count","filters":[],"binSpec":{"displayRangeMin":0,"displayRangeMax":80,"binWidth":3}}

Fixed with upgrade to lib-eda-subsetting v1.2.1


magic.connect.showWallet().then() never fires

✅ Prerequisites

[x] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
[x] Are you running the latest SDK version?
[c] Are you reporting to the correct repository (magic-sdk)?

🐛 Description
I'm trying to listen to event when wallet dialog is open with magic.connect.showWallet().then(...) but this never fires. The promise only settles to error after the opened dialog is closed.
🧩 Steps to Reproduce

Connect a wallet
call magic.connect.showWallet().then(() =>{})
then callback never fires

🤔 Expected behavior
Calllback should e fired when dialog is opened.
😮 Actual behavior
Callback never fires, promise is throwing after the dialog is closed.
💻 Code Sample
https://codesandbox.io/s/magic-connect-demo-forked-w508kc?file=/src/App.tsx
🌎 Environment

Software
Version(s)

magic-sdk
10

Browser
Chrome

Hi @SpadarShut , thank you for reporting this issue. We are currently working on this issue and will follow up when it is resolved.

the only time I see it fired is when I logout ! close the dialog would go to catch(err =>{})

@garyng2000
We've pushed an update to magic-sdk via v14.0.0 that resolves this.
You can see how to handle the user disconnecting from the login modal in our docs.
https://magic.link/docs/connect/wallet-api-reference/javascript-client-sdk#showui()


cleanup(userspace/libsinsp): small cleanups in user_group_manager API.

What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area libsinsp
Does this PR require a change in the driver versions?
NOPE

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@deepskyblue86 this should supersede #751 ; care to take a look?

@deepskyblue86: changing LGTM is restricted to collaborators

In response to this:

LGTM, just a nit

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: deepskyblue86, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.10.0

LGTM label has been added.  Git tree hash: 555a302246e657fa87d0377a757c1dc8b47fb3d3

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

New changes are detected. LGTM label has been removed.

LGTM label has been added.  Git tree hash: d206574dae99b03db49a4cf829443fdebbbc51bb

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, gnosek
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP,gnosek]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Module Core User Management Roles and Permissions

is there a module package for user roles and permissions management,

You don't have to create them, but it is easy to do it
you can use any of these 2 packages
composer require spatie/laravel-permission
work with laravel's authentication packages or you can make your own
o
composer require cartalyst/sentinel requires login and register if you don't know how it works you can guide you from asgard
https://github.com/AsgardCms/Platform/tree/master/Modules/User, keep in mind that you can use it as a reference, don't copy and paste (not recommended).
Good luck in your project


Set tabline color for modified file

Hi @itchyny,
Thanks so much for this awesome plugin. I have been considering shifting from airline to lightline because this is so lightweight and fast. There is one feature that I think is lacking from lightline and I was wondering if it possible to add it (in my .vimrc or in the plugin itself). How would I set the color of the tabline to something else if the file is modified (and not saved yet)? Any hints would be appreciated.
Thanks

This is not basically supported feature but there's a hint in :h lightline-problem-12.

Thanks for the quick reply. I did take a look at the problem and although it's not obvious to me how I will go about doing that, I will give it a try. Thanks :)

You can change the modified color of some components in statusline, but you cannot change the colors in tabline. This is a limitation of this plugin and will not be changed.


argocd-secret is not updated with an oidc.dex.clientSecret token

Describe the bug
After upgrading to OpenShift GitOps Operator 1.8.1, and even after downgrading to 1.7.1 DEX / Login with Openshift gave an error and login was not possible.
The reason is that the operator(?) had changed the argocd-cm configmap to reference the oidc.dex.clientSecret secret key in the argocd-secret Secret, but the key is not present.
To Reproduce
Steps to reproduce the behavior:

Operator installed in the OpenShift operator dashboard
Existing argocd instance not able to login

Expected behavior
Able to login
Screenshots
argocd-dex-server-5fd5544b95-rqdr6 dex time="2023-03-24T14:04:57Z" level=warning msg="config referenced '$oidc.dex.clientSecret', but key does not exist in secret"                      argocd-dex-server-5fd5544b95-rqdr6 dex time="2023-03-24T14:04:57Z" level=info msg="dex config unmodified"

Additional context
Argocd instances are created in separate namespaces, pr team, and setup with NamespaceConfig
apiVersion: redhatcop.redhat.io/v1alpha1
kind: NamespaceConfig
metadata:
  name: argocd
spec:
  labelSelector:
    matchLabels:
      custom.label.com/argocd-enabled: "true"
  templates:
  - excludedPaths:
    - .spec.rbac.policy
    - .spec.replicas
    - .metadata
    - .status
    objectTemplate: |
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      metadata:
        name: argocd
        namespace: {{ .Name }}
        labels:
          app.kubernetes.io/managed-by: namespace-configuration-operator
      spec:
        rbac:
          defaultPolicy: ''
          policy: |
            # the env-admins have access to support teams
            g, env-admins, role:admin
            g, deployer, role:admin
            # add your teams below here
          scopes: '[groups]'
        redis: {}
        repo: {}
        server:
          route:
            enabled: true
            tls:
              termination: reencrypt
        sso:
          dex:
            openShiftOAuth: true
        statusBadgeEnabled: true
        initialRepositories: |
          - type: helm
            name: ourrepo
            url: https://ourrepo.com/repository/helm/

** Workaround **
We can work around the issue by adding the secret manually.
oc get secret argocd-secret -o yaml  # See that `oidc.dex.clientSecret` is missing
NAMESPACE=yournamespace-argocd
secret=$(oc get -n $NAMESPACE sa argocd-argocd-dex-server -o json | jq -r '.secrets' | grep token | sed 's/    "name": "//g' | sed 's/"//g')
echo $secret
expectedClientSecret=$(oc get secret $secret -n $NAMESPACE -o json | jq -r '.data.token')
echo $expectedClientSecret
oc patch secret argocd-secret  --patch="{\"data\": { \"oidc.dex.clientSecret\": \"${expectedClientSecret}\" }}"

oc patch secret argocd-secret  --patch="{"data": { "oidc.dex.clientSecret": "${expectedClientSecret}" }}" This line should have namespace . This should be like this:-
oc patch secret argocd-secret  --patch="{"data": { "oidc.dex.clientSecret": "${expectedClientSecret}" }}"  -n $NAMESPACE

This was solved by adding provider: dex to sso
spec:
  sso:
    provider: dex
    dex:
      openShiftOAuth: true


create db

Why create_db.sh is not added in the Dockerfile?

I removed create_db.sh from the repo. It is created at the very beginning stage of the repo, and is not needed anymore.