[Bug?] Casting to a width stored in a struct

I have no idea if this is valid SystemVerilog, but Questasim and Quartus accept it and we use it all over our code.
typedef struct {
    int WIDTH;
} width_t;

module Foo ();
    localparam width_t w = width_t'{32};
    wire [31:0] t = (w.WIDTH'(0));
endmodule

[SNT:PA0207] foo_struct_width.sv:7:28: Syntax error: no viable alternative at input 'module Foo ();\n    localparam width_t w = width_t'{32};\n    wire [31:0] t = (w.WIDTH'',
    wire [31:0] t = (w.WIDTH'(0));
                            ^-- ./slpp_all/work/_6142509188972423790/foo_struct_width.sv:7:28:.

In order to get Surelog to parse it, I have to surround w.WIDTH with parens. Seems like a precedence issue in your grammar.

It's legal, the grammar had that particular rule commented out for runtime issues, I'll reactive it. UHDM compilation still need to get update to support hier_path object as a cast typespec.

#2933 fixes the grammar part, UHDM still has to be updated.

Fixed by #2940

This worked on our large internal codebase. I think our code now parses, but now hellosureworld is segfaulting after a CP0335 message. The COMP phase is after the parse phase, yes?

Nope. Nevermind


MarketData Websocket not getting updated

I tried running
r_ws = gemini.MarketDataWS('BTCUSD', sandbox=True)
but found that subsequently the class object is not getting updated (i.e. the dictionaries are always empty). Interestingly, using websocket-client WebSocketApp function directly does correctly trigger the on_message regularly. Does anyone have similar experience?

I figured that I have to do the start() method.


Parallel queries from two components

Is it a bug or a feature?
In one component
const { status, isFetching } = useQuery('gallery',[variables], fetchGallery, { onSuccess: () => {...} })

In another component
  const { data: rows = [], ...rest } = useQuery('gallery', undefined, { manual: true })

The result: both queries return loading status, do retries and eventually error.
If I remove the second one, first one is loading as it should be.
I try to use here the cache from one component in another

This is intentional. My suggestion:

Extract your gallery query into a custom hook that can accept optional config. This way its reusable, and you'll never find yourself without the query function for that query.
Extract your function to a different file that you can import where you use this query
Use queryCache.getQueryData to synchronously access the query's data, which doesn't require a fetcher function to be passed at all.


PARTIAL_SYNC.md needs updating for EOS Nation snapshots instructions

https://github.com/dfuse-io/dfuse-eosio/blob/develop/PARTIAL_SYNC.md
snapshots are now in zstd format (was previously bzip2)

There is also an apt package for zstd.

Thanks added!


Java indexer: create MarkedSources utility class [phab:D1765]

Created by schroederc at 2017-07-07 18:28:44:
This is the first step towards decoupling the MarkedSource logic from VName/EntrySet logic.

fromberger accepted this revision at 2017-07-07 18:57:13

schroederc closed via commit 7ca58225741f1aa91f2b20ec9a0564319083b83a at 2017-07-07 19:13:11


Fix Elixir v1.4 warnings

Coverage remained the same at 98.667% when pulling ea83b4454db141f8048a055d3463209c2ff13a05 on tmjoen:tm-fix-elixir14-warnings into 76e48e6cc0ff99a9fc90ded614561b60a867eecb on c-rack:master.

Thanks a lot and sorry about the late merge!


Databricks Azure Synapse connector fails to capture exception in preActions/PostActions

We are trying to make use of the preActions and postActions options of Databricks Azure Synapse connector which fails to catch exception.

Screenshot for reference -

Please review and let me know if -
1. we are missing any option
2. or this is a known issue with a workaround
3. or this is a product bug
5. or there is a no workaround
[Enter feedback here]

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

ID: c5a38f10-28c6-dede-67a6-444c83ecee9e
Version Independent ID: 67dd3e6c-189e-1e6c-5e1a-b733f1dfef38
Content: Azure Synapse Analytics - Azure Databricks
Content Source: databricks/data/data-sources/azure/synapse-analytics.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

Thanks for leveraging Azure docs feedback channel to raise this question. This channel is reserved for ‘Azure docs’ feedback- for sharing doc feedback and suggesting content improvements. We didn't determine any changes for this documentation upon reviewing this feedback.
If your issue is specific to a use case, we request you to please reach out in forums like Microsoft Q&A or Stackoverflow. We have our engineers and other community members who will be happy to assist. Forums have a better suited audience for such queries. Once your issue is posted in forum, please do share the forum thread link here for tracking.
If you have a document which you are following and if you think it needs an update, please let us know about that here.
Thank you

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply and reopen the issue. We will gladly continue the discussion.
Please do share the forum link once the issue is posted. Thank you


Create inventory-notifier

A plugin that displays an icon overlay showing the number of free spaces available in your inventory and that will also send a notification when the inventory is full.

This plugin is very similar to https://runelite.net/plugin-hub/show/inventory-count


Dependency resolution fails after clean

If a run poac clean followed by poac <build | run> and I have (conan*) dependencies the build fails to reconnect/link to the existing downloaded dependencies until the poac.toml has been updated, built and modified back to the state when it was cleaned. I assume this is due to Poac only doing a full build if the poac.toml is modified but considering a clean build. The error is bubbled up from the compiler due to missing headers and Poac.
*Only tested with packages from conan registry not Poac's.

$ git clone https://github.com/wx257osn2/poac-conan-demo
$ cd poac-conan-demo
$ ls
poac.toml  src
$ poac build
$ poac clean
$ ls
poac.lock  poac,toml  src
$ poac build
   Compiling 1/1: poac-demo v0.1.0 ("/path/to/poac-conan-demo")
FAILED: /path/to/poac-conan-demo/poac-out/debug/poac-demo
g++ -std=c++20 src/main.cpp -o /path/to/poac-conan-demo/poac-out/debug/poac-demo
src/main.cpp:2:10: fatal error: leveldb/db.h: No such file or directory
    2 | #include <leveldb/db.h>
      |          ^~~~~~~~~~~~~~
compilation terminated.
Error: failed to build package `poac-demo`

Caused by:
    internal build system has been stopped with an error:
subcommand failed

Closing as the Conan support was tentatively removed.


Finalize the behavior of the 'lengthof' operator for value-type JSON

Currently lengthof operator for value-typed JSON (e.g: json j = 5;) gives -1.
Need to finalize what the correct behavior is

Json.length() method is removed with JBallerina 1.0.0. Either user have to convert a JSON value to map or json[] inorder to get the length.


when a table is long set fpr_kable param scroll = gitbook_on

Gramaphone fish tables are an example

Closing in favor of fpr issue #30


certs not getting renewed

Describe the bug:
Hello.
I noticed every time  certmanager pod is restarted, a lot of messages are displayed, which is not clear for me if there's in fact an issue. I'm running it on EKS 1.19 + certmanager 1.5.0 ( though this has been happening in previous versions ).
I0812 10:47:09.194912       1 start.go:75] cert-manager "msg"="starting controller"  "git-commit"="0c93a2b2b9e735153615aabfbb61d71144c2d2f8" "version"="v1.5.0"
W0812 10:47:09.195440       1 client_config.go:615] Neither --kubeconfig nor --master was specified.  Using the inClusterConfig.  This might not work.
I0812 10:47:09.197165       1 controller.go:268] cert-manager/controller/build-context "msg"="configured acme dns01 nameservers" "nameservers"=["<IP_ADDRESS>:53"]
I0812 10:47:09.198081       1 controller.go:85] cert-manager/controller "msg"="enabled controllers: [certificaterequests-approver certificaterequests-issuer-acme certificaterequests-issuer-ca certificaterequests-issuer-selfsigned certificaterequests-issuer-vault certificaterequests-issuer-venafi certificates-issuing certificates-key-manager certificates-metrics certificates-readiness certificates-request-manager certificates-revision-manager certificates-trigger challenges clusterissuers ingress-shim issuers orders]"
I0812 10:47:09.198796       1 controller.go:115] cert-manager/controller "msg"="starting leader election"
I0812 10:47:09.199719       1 leaderelection.go:243] attempting to acquire leader lease runtime/cert-manager-controller...
 Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt" "resource_namespace"="" "resource_version"="v1"
I0812 10:47:19.395298       1 setup.go:219] cert-manager/controller/clusterissuers "msg"="ACME server URL host and ACME private key registration host differ. Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
E0812 10:47:19.397514       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-idp.staging.mydomain.net-2099224861-1196080546"
E0812 10:47:19.495749       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-sim.staging.mydomain.net-1311908321-3872851150"
E0812 10:47:19.496295       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-ip-network.staging.mydomain.net-328321089-3060104841"
E0812 10:47:19.498015       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-stream-vbzgj-2409796431"
E0812 10:47:19.500924       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-account.go.staging.mydomain.net-sb4zk-3688802901"
E0812 10:47:19.595367       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-accountstaging.extremeconnect.me-2bp7z-1624007278"
E0812 10:47:19.595626       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-agreements.staging.mydomain.net-2669863-4087702731"
E0812 10:47:19.597090       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-observability.staging.mydomain.net-1432193325-853042156"
E0812 10:47:19.597778       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-websheets-demo.staging.mydomain.net-kh6w8-1911680294"
E0812 10:47:19.598820       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="observability/cert-stream-86hld-853042156"
E0812 10:47:19.599494       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-data-stack.staging.mydomain.net-8hvxq-2409796431"
E0812 10:47:19.707687       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-billing.staging.mydomain.net-702293397-2481318050"
E0812 10:47:19.795064       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-rsp-platform.staging.mydomain.net-70599831-291985742"
E0812 10:47:20.109159       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-strimzi-data-stack.staging.mydomain.net-xfnsg-2409796431"
E0812 10:47:20.110108       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-crm.staging.mydomain.net-329897409-2861563615"
E0812 10:47:20.111058       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-msc-dissertations.staging.mydomain.net-htdt4-371370178"
E0812 10:47:19.798962       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-accountstaging.extremeconnect.me-cm89x-1624007278"
E0812 10:47:20.295052       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-stream-lv8cp-2409796431"
E0812 10:47:19.994948       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-acs-network.staging.mydomain.net-58qkz-2965047923"
E0812 10:47:20.495009       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-runtime.staging.mydomain.net-969809985-1956196063"
E0812 10:47:20.499413       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-ordering.staging.mydomain.net-1295641273-1498736715"
E0812 10:47:20.594191       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-continuous-integration.staging.mydomain.net-326-2550545983"
E0812 10:47:20.595059       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-go-staging.mydomain.net-gltvl-1545252937"
E0812 10:47:20.595875       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-hr.staging.mydomain.net-982257025-3331042549"
E0812 10:47:20.597589       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-voice.staging.mydomain.net-3132620241-1700705636"
E0812 10:47:20.694214       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-test-for-finance.staging.mydomain.net-41711-4156406073"
E0812 10:47:20.695658       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-test-demo.websheets.staging.mydomain.net-3257378810"
E0812 10:47:20.017282       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-packet.staging.mydomain.net-2283909335-1649831580"
E0812 10:47:20.695914       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-test.google.entitlements.staging.io3.co-3981238007"
E0812 10:47:20.697280       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-manager-dnstoremove.hello-world.staging.truphon-1948827277"
E0812 10:47:20.697577       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-test.huawei.entitlements.staging.io3.co-2991422606"
E0812 10:47:21.008178       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-infrastructure-security.staging.mydomain.net-24-2629602955"
E0812 10:47:21.095289       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-ui-stack.staging.mydomain.net-p45zf-1335709154"
E0812 10:47:20.016576       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="observability/cert-stream-dtwkp-853042156"
E0812 10:47:20.897924       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-subscriber.staging.mydomain.net-2909077-3227228278"
E0812 10:47:21.096413       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-compute.staging.mydomain.net-851316101-50647104"
I0812 10:47:22.234143       1 setup.go:309] cert-manager/controller/clusterissuers "msg"="verified existing registration with ACME server" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
I0812 10:47:22.432210       1 setup.go:309] cert-manager/controller/clusterissuers "msg"="verified existing registration with ACME server" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt" "resource_namespace"="" "resource_version"="v1"
I0812 10:47:23.595911       1 setup.go:219] cert-manager/controller/clusterissuers "msg"="ACME server URL host and ACME private key registration host differ. Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
I0812 10:47:23.998360       1 setup.go:219] cert-manager/controller/clusterissuers "msg"="ACME server URL host and ACME private key registration host differ. Re-checking ACME account registration" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt" "resource_namespace"="" "resource_version"="v1"
E0812 10:47:24.399758       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-idp.staging.mydomain.net-2099224861-1196080546"
E0812 10:47:24.498661       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-ip-network.staging.mydomain.net-328321089-3060104841"
E0812 10:47:24.498660       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-sim.staging.mydomain.net-1311908321-3872851150"
E0812 10:47:24.593702       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-stream-vbzgj-2409796431"
E0812 10:47:24.595604       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-account.go.staging.mydomain.net-sb4zk-3688802901"
E0812 10:47:24.597541       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-accountstaging.extremeconnect.me-2bp7z-1624007278"
E0812 10:47:24.599168       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-agreements.staging.mydomain.net-2669863-4087702731"
E0812 10:47:24.694165       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-observability.staging.mydomain.net-1432193325-853042156"
E0812 10:47:24.695567       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-websheets-demo.staging.mydomain.net-kh6w8-1911680294"
E0812 10:47:24.696929       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="observability/cert-stream-86hld-853042156"
E0812 10:47:24.698225       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-data-stack.staging.mydomain.net-8hvxq-2409796431"
E0812 10:47:24.794742       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-billing.staging.mydomain.net-702293397-2481318050"
E0812 10:47:25.202115       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-rsp-platform.staging.mydomain.net-70599831-291985742"
E0812 10:47:25.209107       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-msc-dissertations.staging.mydomain.net-htdt4-371370178"
E0812 10:47:25.294312       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-accountstaging.extremeconnect.me-cm89x-1624007278"
E0812 10:47:25.295555       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-crm.staging.mydomain.net-329897409-2861563615"
I0812 10:47:25.297772       1 setup.go:309] cert-manager/controller/clusterissuers "msg"="verified existing registration with ACME server" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt-staging" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt-staging" "resource_namespace"="" "resource_version"="v1"
E0812 10:47:25.298375       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-stream-lv8cp-2409796431"
E0812 10:47:25.298726       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="data-stack/cert-strimzi-data-stack.staging.mydomain.net-xfnsg-2409796431"
E0812 10:47:25.495099       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-acs-network.staging.mydomain.net-58qkz-2965047923"
E0812 10:47:25.595325       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-runtime.staging.mydomain.net-969809985-1956196063"
E0812 10:47:25.599902       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-ordering.staging.mydomain.net-1295641273-1498736715"
E0812 10:47:25.603764       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-continuous-integration.staging.mydomain.net-326-2550545983"
E0812 10:47:25.606868       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-hr.staging.mydomain.net-982257025-3331042549"
E0812 10:47:25.693988       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-go-staging.mydomain.net-gltvl-1545252937"
E0812 10:47:25.696711       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-voice.staging.mydomain.net-3132620241-1700705636"
E0812 10:47:25.699076       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-test-demo.websheets.staging.mydomain.net-3257378810"
I0812 10:47:25.696949       1 setup.go:309] cert-manager/controller/clusterissuers "msg"="verified existing registration with ACME server" "related_resource_kind"="Secret" "related_resource_name"="letsencrypt" "related_resource_namespace"="runtime" "resource_kind"="ClusterIssuer" "resource_name"="letsencrypt" "resource_namespace"="" "resource_version"="v1"
E0812 10:47:25.697449       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-test-for-finance.staging.mydomain.net-41711-4156406073"
E0812 10:47:25.698964       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/cert-network-packet.staging.mydomain.net-2283909335-1649831580"
E0812 10:47:25.806920       1 controller.go:163] cert-manager/controller/orders "msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available" "key"="istio-system/ingress-cert-test.google.entitlements.staging.io3.co-3981238007"
I0812 10:47:28.194601       1 trace.go:205] Trace[1578350570]: "Reflector ListAndWatch" name:external/io_k8s_client_go/tools/cache/reflector.go:167 (12-Aug-2021 10:47:11.194) (total time: 16999ms):
Trace[1578350570]: ---"Objects listed" 16906ms (10:47:28.101)
Trace[1578350570]: [16.999779737s] [16.999779737s] END

Expected behaviour:

As we can see, in fact there are some different error messages which might be related between them such as
- ""msg"="re-queuing item due to error processing" "error"="ACME client for issuer not initialised/available""
- ""error"="ACME client for issuer not initialised/available"
- "error"="certificaterequest.cert-manager.io "cert-ip-network.staging.mydomain.net-328321089" not found"
This last one is particularly strange because that particular CertificateRequest does exist when checking via kubectl get cr -A
I believe these errors should not appear everytime certmanager is booting.
Steps to reproduce the bug:
kubectl delete pod <certmanager_pod> and check the logs for the new certmanager pod is enough to trigger these messages
Anything else we need to know?:
Yesterday I found out that certs are not being renewed after reach renewal time. However, I could not find any errors, infos, etc , it looks like it even didnt try to renew. Editing the Certificate with some random stuff (ie new label ) was sufficient to force the renew and in that time, cert was renewed sucessfully. Not sure if this behaviour is related with boot messages described above.
Environment details::

Kubernetes version: 1.19
Cloud-provider/provisioner: EKS
cert-manager version:  1.5.0 ( though this has been happening at least since 1.4.0 )
Install method: static manifests

Having the same issue after upgrade from 1.1.0 to 1.2.0.

Not sure if this behaviour is related with boot messages described above.

The 'owner not found' messages should not be related and don't suggest an issue, we've hopefully improved that part in #4369 . They appear because cache is out of sync briefly just after the pod restarts.
Certs not getting renewed is an issue- this is currently being discussed on Slack.
@mfmbarros would you agree to change the issue header to something like 'certs not getting renewed after upgrade to v1.5' or similar?

@irbekrm sure. I thought errors displayed on boot were somehow related with the issue itself, which is: certs are not being renewed.
Giving more insight: In last month I updated certmanager from 0.10 to 1.50 with the following order: 0.10.1 > 0.13.1 > 0.16.1 > 1.2.0 > 1.4.0 > 1.5.0 . Can't exactly tell when cert renewals became broken, but at 0.16.1 I'm almost sure it's working and at least in 1.4.0 this issue was already presented (might be ocurring already in 1.2.0, not really sure).
Apart from those error messages on boot, I see no errors, no logs, no activity, when certificate's RenewalTime is reached.
Few days ago I set log level to "v=4" and when a certificate reached renewalTime I could see in certmanager logs this:
I0819 04:39:59.004266       1 controller.go:153] cert-manager/controller/certificates-trigger "msg"="syncing item" "key"="istio-system/ingress-cert-account-staging.mydomain.com"
I0819 04:39:59.004429       1 gatherer.go:312] cert-manager/controller/certificates-trigger "msg"="Found no CertificateRequest resources owned by this Certificate for the next revision" "key"="istio-system/ingress-cert-account-staging.mydomain.com" "revision"=1
I0819 04:39:59.005179       1 controller.go:169] cert-manager/controller/certificates-trigger "msg"="finished processing work item" "key"="istio-system/ingress-cert-account-staging.mydomain.com"

And nothing more happened, the renewal didn't run. However, if I manually restart certmanager pod, the new pod will automatically renew sucessfully that certificate so right now, my workaround is restarting certmanager pod whenever certificate's expiration date is below 30d.
As far I can observe, any Certmanager resources living on my EKS Cluster should be using "cert-manager.io/v1" api version, though most of them were initially created on cluster with "certmanager.k8s.io/v1alpha2". Old crds were cleaned up

I believe this issue is caused by the slight difference of renewal time as it appears on .status.renewalTime on Certificate and our calculated value- in the first case it appears like this is rounded to a second.
Looking at the Certificate configs posted on Slack about this issue, I see that the certs have the ~1 second diff between the notAfter and notBefore value:
  Not After:               2021-09-18T04:39:59Z
  Not Before:              2021-06-20T04:40:00Z
  Renewal Time:            2021-08-19T04:39:59Z

The renewal time on the cert is calculated by this function and the value returned from the function should be something like 2021-08-19T04:39:59.333333334Z, but on the cert's status it is truncated to the nearest second.
This becomes a problem because, we use the renewal time from certificate's status when determining when the cert should be popped from the queue (here), but then we again use our function to determine whether the cert has to be renewed now (here. This means that in cases like above we end up popping the cert out of the queue slightly earlier than the calculated renewal time, so it doesn't get renewed. It also doesn't get re-queued again because the requeuing uses the renewal time on the cert and only re-queues if the renewal time is 'now' -which it is according to the truncated time.
The solution probably will be to simply truncate the time in the function that calculates renewal time.

We've now released patches with a fix that will hopefully solve this issue:

https://github.com/jetstack/cert-manager/releases/tag/v1.5.3
https://github.com/jetstack/cert-manager/releases/tag/v1.4.4

Any feedback would be very welcome!
Thanks a lot @mfmbarros for providing all the logs and debugging info!

Thanks! I've just upgraded it to 1.5.3, so far so good. One of my certs should reach Renewal Time tomorrow evening, I'll let you know how did it go.


macOS RDP -> W7 LDAP?

Is there a way to connect from
macOS Windows RDP to Win7 Ult machine with the pgina.fork <IP_ADDRESS> installed on it?
LDAP server is running on macOS Server 10.12.
I always get
Anmeldung fehlschlagen: Der Benutzer besitzt nicht den benötigten Anmeldetyp aus diesem Computer.
Google Translate:
Logon Failure: The user does not have the required logon type from that computer.

Logs are stored at %ProgramFiles%\pGina.fork\log
The eventlog will help  you too.
Its possible to rdp into a pgina machine


upgrade .Net version to 6.0

Replaces #509
Target 5.0 with 6.0 sdk

Target 6.0 with 6.0 sdk

There were some people in some regions where VS2022 doesn't run well on older hardware and want to still use VS2019 instead. However this isn't possible with the release version of the 6.0 SDK. However you can use the preview 4 build of the SDK with VS2019 as a stop gap solution. I don't know How long that would work if some new features are being used.

Idk how long that test is broken. That one should be fixed in a follow up PR.


feat: format path-uri at Page and Redirects

Question: Shouldn't we make it a bit clearer that this means "path already present on the site", and not a random path?
Not sure if we're locking anything here

Question: Shouldn't we make it a bit clearer that this means "path already present on the site", and not a random path?

I didn't get it what you mean, can you rephrase? As far as I understood what you said, the admin that handles this format path-uri


Spurious "This branch has conflicts that must be resolved" warning

Extension version: 0.12.0
VSCode Version: 1.39.2
OS: Debian 4.19.37

Steps to Reproduce:

Clone the wpt repo and find https://github.com/web-platform-tests/wpt/pull/19754 in the list of pull requests in VS Code. For me it's under "Created By Me" but for others it may be hard to find.
2.At the bottom of the "Description" view, "This branch has conflicts that must be resolved" will be shown. But there are no conflicts to resolve.

Screenshot:

If it'll help to debug this issue, at the time I was looking the refs/pull/19754/merge ref of the repo was pointing at https://github.com/web-platform-tests/wpt/commit/4c234adbd7ffa423a23deafecd9c1a9a832f24ce. The first parent of that merge is https://github.com/web-platform-tests/wpt/commit/b482734e5092c5f5a6aadc66aa1c599742f2dc67 (the master branch) and the second is https://github.com/web-platform-tests/wpt/commit/3cb58e960af6312e9792ec4bbd0e73bfdada1805 (head of the PR branch). No conflict.

Thanks for reporting this @foolip! Looks like we are missing a "pending" state for this message - should display that the mergability is still being calculated in that case

Aha, that would explain it. I had just created the PR then.


C++ SDK for Azure Service Bus

Query/Question
Hello, is there an SDK available for C++ to query Azure Service Bus? I couldn't find anything on this except a feature request. If there's a branch where development has started, I'd be happy to contribute. Can someone point me in the right direction?
Why is this not a Bug or a feature Request?
Couldn't find anything related to this other than feature request...
Setup (please complete the following information if applicable):

OS: Ubuntu 22
IDE : IntelliJ
Latest

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ + ] Query Added
[ + ] Setup information Added

Hi @0xar1, thanks for the feature request. We don't currently have Azure Service Bus support in C++.
Can you please help us understand your application and usage scenarios that requires an SDK for it? What are you trying to build and do? We are looking for customer requests like yours to help motivate and drive the effort, so providing some context would be quite helpful.
cc @ronniegeraghty, @RickWinter

Closing as a duplicate of #3981

Hi @0xar1, thanks for the feature request. We don't currently have Azure Service Bus support in C++. Can you please help us understand your application and usage scenarios that requires an SDK for it? What are you trying to build and do? We are looking for customer requests like yours to help motivate and drive the effort, so providing some context would be quite helpful.
cc @ronniegeraghty, @RickWinter

Use mysql to query from service bus.


VS2022 Debugger Does Not Enumerate ctypes Arrays

Describe the bug
The debugger in Visual Studio 2022 does not treat ctypes arrays as containers, and hovering over them or looking at them in the variables window does not show length or allow the items to be enumerated like a list or dict. This is a new problem in VS2022, and did not occur in VS2017 or VS2019, which is why I've only recently started using VS2022 and this problem is making it very unpleasant as I use ctypes extensively in my work.
Ordinarily I would post in a forum to ask if there is some setting that's set incorrectly (the settings are default for Python), but as there's no forum here I'm making a bug report.
Steps to Reproduce
For me this occurs any and all times I use ctypes arrays in any context, so I don't really have any specific instructions to reproduce. The only thing worth noting is that this occurs regardless of whether "Enable debugging of the Python standard library" is enabled (I mostly work with it enabled). Maybe read a random binary file into a bytearray and do something like
x = (ctypes.c_uint8 * len(file_bytes)).from_buffer(file_bytes)
Then hover over x (or look at it in the variables window). It will only show "special variables" and "protected variables".
Expected behavior
In past VS versions the debugger would display as if it was a list, showing the length and list of all elements.
Configuration information
VS Version: Community 2022 (64-bit) 17.3.0
PTVS version: 17.0.22179.3
Python version: 3.9.7 64-bit (x64)
Debugger Type: I don't think this is relevant for VS2022?

I wasn't even able to get past the import ctypes statement in VS.
Here's the code I ran:
import ctypes

prime_numbers = [2, 3, 5, 7]
byte_array = bytearray(prime_numbers)
x = (ctypes.c_uint8 * len(byte_array)).from_buffer(byte_array)

print(x)

Here's vscode running this just fine:

But when I try the same code in VS, I get an exception from the debugger process:

Traceback (most recent call last):
  File "C:\Users\advolker\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\advolker\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy\__main__.py", line 37, in <module>
    from debugpy.server import cli
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy/..\debugpy\server\__init__.py", line 7, in <module>
    import debugpy._vendored.force_pydevd  # noqa
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy/..\debugpy\_vendored\force_pydevd.py", line 36, in <module>
    preimport('pydevd', [
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy/..\debugpy\_vendored\__init__.py", line 126, in preimport
    import_module(name)
  File "C:\Users\advolker\AppData\Local\Programs\Python\Python39\lib\importlib\__init__.py", line 127, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy\_vendored\pydevd\pydevd.py", line 45, in <module>
    from _pydevd_bundle import pydevd_utils
  File "c:\users\advolker\appdata\local\microsoft\visualstudio\17.0_f467929dexp\extensions\microsoft corporation\python\17.0.0\debugpy\_vendored\pydevd\_pydevd_bundle\pydevd_utils.py", line 9, in <module>
    import ctypes
  File "C:\Users\advolker\source\repos\ctypes\ctypes\ctypes.py", line 6, in <module>
    x = (ctypes.c_uint8 * len(byte_array)).from_buffer(byte_array)
AttributeError: partially initialized module 'ctypes' has no attribute 'c_uint8' (most likely due to a circular import)
Press any key to continue . . .

And if I try to remove the import statement, I get an error that ctypes is not defined.

@int19h Are you able to look into this whenever you can? I'm not really sure what's going on here.

Very strange that you can't import ctypes in VS. At least it looks like you're able to reproduce it on VSCode. In VS length is hidden away under "protected variables" (as with all variables that start with _), but your image doesn't show enumeration of entries.

@AdamYoblick The error is because your sample is named ctypes.py, so when you import ctypes it imports itself.
Aside from that I'm pretty sure the behavior is identical between VS and VSCode - we don't do anything special in debugpy that'd make a difference.
ctypes arrays have len() and are iterable though, so not showing items is a bug for sure.

@AdamYoblick Adam Yoblick FTE The error is because your sample is named ctypes.py, so when you import ctypes it imports itself.

aaaand I feel like a fool 😆
@TheRealQuantam I see what you're saying about the variable data being presented in a slightly different way.
Here's VSCode:

And here's VS:

This has to do with Visual Studio variable presentation options found in Tools -> Options -> Python -> Debugging.
If you don't want protected variables to be shown in a group, select Inline for that option, then restart debugging:

Then the view will look like VSCode:

Please let me know if this fixes your issue and I can close this out :)

@int19h I was under the impression that VSCode used group for everything, but it sounds like it uses inline for some things. I'd like to change the default behavior of VS to match VSCode. Can you please point me to variable presentation options passed to debugpy from VSCode if the user doesn't change anything?

VSCode doesn't actually wire it up in any special way - whatever is in launch.json is flown through as is, and if it's not there, debugpy defaults are used, which are to group everything except for "protected":
https://github.com/microsoft/debugpy/blob/db43846a8d053199c27eda599c28f95c504dd7e6/src/debugpy/_vendored/pydevd/_pydevd_bundle/pydevd_api.py#L72-L74
Note though that showing _length_ as an attribute directly under the variable is separate from showing the actual items and length for a collection. If you expand prime_numbers in the repro, you'll see all the items, and length represented as a synthetic member len(). This is what the ctypes array should be doing as well.

Ok so I'll create a new issue to have protected variables be presented as Inline, to match the vs code defaults. And I'll move this issue to debugpy per Pavel's instructions.


Remove _anzaTokenAddress from LoanNotary.sol method inputs

Need to remove _anzaTokenAddress input argument from _getBorrower and _getSigner() methods. It is not a fullproof verification.

Implemented the following immutable variables:

DebtNotary: address private immutable __debtNotary_anzaTokenAddress
RefinanceNotary: address private immutable __refinanceNotary_anzaTokenAddress
SponsorshipNotary: address private immutable __sponsorshipNotary_anzaTokenAddress

AnzaToken address variable was not needed for LoanNotary.


Add openApp to CardAction for Teams Compose Extension

This changes adds a new type "openApp" to CardAction for compose extension. It's also an already supported type in SMBA.

@maoyu-dev,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


Only load and parse pollfile if it has changed since last loading

Scope and purpose
Fixes #282.
Add a description of what this PR does and why it is needed. If a linked ticket(s) fully
cover it, you can omit this.
Contributor Checklist
Every pull request should have this checklist filled out, no matter how small it is.
More information about contributing to Zino can be found in the
README.

[X] Added a changelog fragment for towncrier
[X] Added/amended tests for new/changed code
[X] Added/changed documentation
[X] Linted/formatted the code with black, ruff and isort, easiest by using pre-commit
[X] The first line of the commit message continues the sentence "If applied, this commit will ...", starts with a capital letter, does not end with punctuation and is 50 characters or less long. See https://cbea.ms/git-commit/
[ ] If applicable: Created new issues if this PR does not fix the issue completely/there is further work to be done

I have rebased this instead of adding more commit because I have rethought how to access the saved attribute of when the poll file was last modified.


Build fails: Linker error Runtime-lib mismatch

I created the Solution files using the included python scripts for VisualStudio2019. When building with VS, Hazelnut and Sandbox are failing because of linker errors. I did not modify the runtime library to use, everything is at default, no change on my side.
Every project inside the solution uses MultithreadDebugDLL runtime libs. So what (I assume external) component is causing this?
Linker output (only a few selected, there are hundred of repetaed errors):
yaml-cpp.lib(stream.obj) : error LNK2038: mismatch detected for 'RuntimeLibrary': value 'MTd_StaticDebug' doesn't match value 'MDd_DynamicDebug' in ExampleLayer.obj

msvcprtd.lib(MSVCP140D.dll) : error LNK2005: "public: __cdecl std::_Locinfo::_Locinfo(char const *)" (??0_Locinfo@std@@QEAA@PEBD@Z) already defined in yaml-cpp.lib(stream.obj)

libcpmtd.lib(locale.obj) : error LNK2005: "public: char const * __cdecl std::_Locinfo::_Getfalse(void)const " (?_Getfalse@_Locinfo@std@@QEBAPEBDXZ) already defined in msvcprtd.lib(MSVCP140D.dll)

In the yaml premake file change static runtime to "off", this is the same issue as #457

Closing as duplicate of #457

Thanks.
Will this be fixed in an upcoming release?

Thanks.
Will this be fixed in an upcoming release?

It depends when Cherno merges https://github.com/TheCherno/yaml-cpp/pull/1 as mentioned in #457.

And sorry for duplicate, but "Errors on Running" is just a really bad title when it comes to searching for this error beforehand...

I've changed the title of #457.


rancher quick start vagrant cluster lunch kubectl not working as expected.

rancher quick start vagrant cluster lunch kubectl not working as expected, its keep trying to connect to shell for a long time. but the cluster is up and running fine.

As this is not really a docs issue, can you file it here: https://github.com/rancher/rancher/issues/new
Please include more info on what OS you are running Vagrant, what browser you are using, what is the actual network response from the API when you open developer tools?


Always show controlbars in fullscreen mode.

Hi,
I wonder if there is a function that could make the control always showing in fullscreen mode.
note: i've added this code before just to achieve fadeIn timing. Considering if this could be an issue.
$(".mejs-inner").mouseenter(function() {
$(".mejs-controls").fadeIn(300).delay(2000).fadeOut(300);
});
thanks.

@elruinnou Have you tried alwaysShowControls options from the newest version? Is this still an issue?

@elruinnou Closing old issues. If you'd like to reopen this, let us know. Thanks!


Javascript error in sphinx-book-theme.js

Describe the bug
Index page emits this js error:
sphinx-book-theme.js:15 Uncaught TypeError: Cannot read property 'offsetTop' of undefined
    at HTMLDocument.scrollToActive (VM375 sphinx-book-theme.js:15)

To Reproduce

Go to https://sphinx-book-theme.readthedocs.io/en/latest/index.html
Open js console
See error

Expected behavior
No error. :stuck_out_tongue:

Which browser and OS are you on?

And what is the documentation that this occurs on? Seems to me that the code isn't robust to empty pages / pages not in the toctree. :)

I observe the error on both latest chrome and firefox, the page is linked in the issue description (it occurs in your docs), and I agree with your assessment.

the page is linked in the issue description

Huh. Not sure how I missed that! Whoops! 😅

Fixed in https://github.com/executablebooks/sphinx-book-theme/commit/4a94b9272b5010b70683b92bdd597ecaa52651da


Upgrade dev experience.

Update many things:

Webpack build + server
Cleaning stuff
Add github templates and docs
Remove Bower
Update npm usage (only upload needed files) and clean useless scripts
ES-6 Modules

@ollwenjones since you are the biggest contributor (congrats!) do you mind having a quick look at this if you have the time for it, please?

sorry @yoannmoinet ... I changed jobs in November, and in the transition totally missed this. Seems like a great set of improvements, though.


Positional Encodings

Hi,
If I am reading your code correctly, you are not using any positional encodings - is that right? Any reasons for it?
Thank you! :)

Hi,
Thank you for your your question!
That is correct - we aren't using any positional encodings. There wasn't a strong reason for not using positional encodings, just the fact that we had a few convolutional layers before the transformer encoder layer.
Best,
Eeshit


Sync of blockchain was fast but sync of lightning-wallet is taking days (2)

Hello,
I think I have a better idea what was wrong.
In the previous version of this issue I was informed that I have to manually unlock the lnd-wallet.
So far so good. Except, that I did not set up lnd at all. I specifically set up raspiblitz to use cln.
So the lnd-wallet should not be a problem or even be mentioned.
That does sound inconsistent to me. Maybe there is something here to check after all.
And btw: after unlocking lnd the cln-wallet did sync in a reasonable time, even if this does not make sense.
But after then next reboot it started all over at 94%.
This happended with fresh sd-cards on at least two different nodes with different ssd and different sd-cards and different rpi-boards.

I do not know. I flashed an sd-card, booted and followed the instructions.
Therefore what ever is in clconf is default.

what is in your clconf?
I flashed the sd-card, booted and followed the menu.
Therefore whatever is in clconf is the default and was not changed by me.
Any errors I mention appear after the initial setup, purely by the menu and before I have any opportunity to change anything at all.
I can post clconf , once you specifically tell me which file or program you mean.

Is rescan present ?
Don't know what that is. I flashed the sd-card, booted and followed the setup-menu. Rescan is not mentioned anywhere.
I can see if rescan is present, once you specifically tell me where to look.

I f you are restoring an old node the the config options are preserved. If you are storing from file or seed the rescan option is added to the CLN config file. You can find it with using the alias:
clconf
or in the SYSTEM menu.

Seems resolved => closing


How to set field to null during upsert?

func (User) Fields() []ent.Field {
	return []ent.Field{
		field.String("name").
			Unique(),
		field.Int("age").
			Optional(),
		field.Time("created_at").
			Default(time.Now),
	}
}

err := client.User.
	Create().
	SetName("a8m").
	SetAge(30).
	Exec(ctx)

err = client.User.
	Create().
	SetName("a8m").
	// SetAgeNull() // not exists
	OnConflict().
	UpdateNewValues().
	Exec(ctx)

I would like to set the age field to null during upsert.

Hey @e48 and thanks for opening this issue. It looks like we don't have an example for this use case on our website.
You can clear optional fields on conflict as follows:
client.User.Create().
	SetName("a8m").
	SetAge(30).
	OnConflict().
	Update(func(u *ent.UserUpsert) {
		u.ClearAge()
	}).
	ExecX(ctx)

Please, feel free to contribute documentation improvement for the upsert section. Closing 🙏

Thank you for the answer. But what I'm actually would like to do is bulk upsert with null values. Like:
up := []*ent.UserCreate{
	client.User.Create().SetName("john").SetAge(30).SetPetNull(),
	client.User.Create().SetName("tom").SetAgeNull().SetPet(dog),
	...
}
ent.User.CreateBulk(up...).OnConflict().UpdateNewValues().Exec(ctx)

If you don't call SetName it will be null in the.

Optional fields don't have NULL-setters (Clear<Field>) on create. For example, if the age field is optional, and the SetAge setter is not called, then the age field is set to NULL implicitly (the SetAgeNull method does not exist).
Does it answer your question? Also, what database do you use?

I use sqlite. When I run the code from first comment, age is not set to null.

Hey @e48, age is NULL after the second command, because when you use the UpdateNewValues modifier, ent updates the database values with the ones that were provided to the creator. If you want to clear the age field (set it to NULL), use the example in my first comment:
client.User.Create().
	SetName("a8m").
	SetAge(30).
	SetAddress("TLV").
	OnConflict().
	// Use the new values, but also clear the `age` field.
	UpdateNewValues().
	Update(func(u *ent.UserUpsert) {
		u.ClearAge()
	}).
	ExecX(ctx)

The above commands generates the following SQL statement:
INSERT INTO `users` (`age`, `name`, ...) VALUES (?, ?, ...) ON CONFLICT DO UPDATE SET `age` = NULL, `address` = `excluded`.`address`, `name` = `excluded`.`name`, ... RETURNING `id`

The same behavior applies also to the CreateBulk option.

That works for single record, but is there any way to do bulk upsert UserUpsertOne?

This is what queries ent actually generates:
client.User.Create().
		SetName("a8m").
		SetAge(30).
		ExecX(ctx)

	client.User.Create().
		SetName("a8m").
		OnConflict().
		UpdateNewValues().
		ExecX(ctx)
		// age is still 30
		// ent: INSERT INTO `users` (`name`, `created_at`) VALUES (?, ?) ON CONFLICT
		// DO UPDATE SET `name` = `excluded`.`name`, `created_at` = `excluded`.`created_at` RETURNING `id` args=...

	client.User.CreateBulk(
		client.User.Create().
			SetName("a8m"),
	).
		OnConflict().
		UpdateNewValues().
		ExecX(ctx)
		// age is still 30
		// ent: INSERT INTO `users` (`created_at`, `name`) VALUES (?, ?) ON CONFLICT
		// DO UPDATE SET `created_at` = `excluded`.`created_at`, `name` = `excluded`.`name` RETURNING `id` args=...

So ent does not set null fields implicitly.

End up implemented Clean* method(edges, optional fields) for creator myown. If anyone interested c426683139d292f26fdff371e81bf085a15148a4

So ent does not set null fields implicitly.

Optional fields are set to NULL implicitly by the database, and therefore, ent does not add them to the INSERT statement as it's redundant and will make the statement longer. Like I mentioned above, if you're interested in clearing optional fields in case of conflict, call Clear<Field> explicitly either on the builder itself or with a custom function.
client.User.Create().
	// ...
	OnConflict().
	// Custom update function.
	Update(func(u *ent.UserUpsert) {
		u.ClearAge()
	}).
	// Or on the builder.
	ClearAge().
	ExecX(ctx)

End up implemented Clear* method(edges, optional fields) for creator myown. If anyone interested c426683139d292f26fdff371e81bf085a15148a4

I don't have access to it. Please paste here a link.


temp bypass gpu test

@cyberzhg
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.

Workaround Fixes https://github.com/tensorflow/addons/issues/1942


Add a new screen and functionality for auto saves.

Add:

A screen specially for loading auto saved games based
A way to navigate through this screen and the load one
An option in the engine to define the time interval between auto saves

Functionality added in #7847165, still unclear if a new screen is necessary or if having it next to the normal load slots is best.

The addition of a new button could have some problems with the responsiveness on very small devices,  having the slots together is fine for now.


epic: design Advanced Cairo chapter structure

Resolves #578
@enitrat  This is a first draft, i took all opened issues related to Advanced Cairo features.
I didn't think a lot about it for now,  tell me if you imagine a better organization than simply including different features one after the other

This change is

I'm not a fan of having WIP chapters - maybe just comment them out of the summary


Create wh40k-10e-light.catpkg.yml

Fingers crossed I did this the right way!

If possible, could someone let me know whether i've done this right?

Please see https://github.com/BSData/catalogue-development/issues/86 for details of how to self-host your content.


If null passed as a value into controled SelectElement, application fails with Uncaught TypeError: Cannot read properties of null (reading 'id')

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
In https://github.com/dohomi/react-hook-form-mui/blob/master/packages/rhf-mui/src/SelectElement.tsx on 62 string there is a condition  if (typeof value === 'object') and I think this is the reason of the failure, because if value will be null, condition
typeof null === 'object' will be true.
Expected behavior 🤔
PAssed null as value to controlled SelectElement doesn't cause a failure
Steps to reproduce 🕹
Steps:

@AlexandrKostrov you are not supposed to add any value into the SelectElement. Because react-hook-form is been used you would use the the FormProvider or FormContainer to preset any values. Do you have any code example?

fixed in v6


RunTime Error when running inference

Hello, shaoshuai !
I have trained the model follow your steps, but when I ran the following codes, errors occured:
python eval_rcnn.py --cfg_file cfgs/default.yaml --ckpt ../output/rpn/default/ckpt/checkpoint_epoch_200.pth --batch_size 4 --eval_mode rcnn
And the error is :
RuntimeError: Error(s) in loading state_dict for PointRCNN:
Missing key(s) in state_dict: "rcnn_net.SA_modules.0.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.0.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.0.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer2.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer2.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer2.conv.bias", "rcnn_net.xyz_up_layer.layer0.conv.weight", "rcnn_net.xyz_up_layer.layer0.conv.bias", "rcnn_net.xyz_up_layer.layer1.conv.weight", "rcnn_net.xyz_up_layer.layer1.conv.bias", "rcnn_net.merge_down_layer.layer0.conv.weight", "rcnn_net.merge_down_layer.layer0.conv.bias", "rcnn_net.cls_layer.0.conv.weight", "rcnn_net.cls_layer.0.conv.bias", "rcnn_net.cls_layer.2.conv.weight", "rcnn_net.cls_layer.2.conv.bias", "rcnn_net.cls_layer.3.conv.weight", "rcnn_net.cls_layer.3.conv.bias", "rcnn_net.reg_layer.0.conv.weight", "rcnn_net.reg_layer.0.conv.bias", "rcnn_net.reg_layer.2.conv.weight", "rcnn_net.reg_layer.2.conv.bias", "rcnn_net.reg_layer.3.conv.weight", "rcnn_net.reg_layer.3.conv.bias".

Hello, shaoshuai !
I have trained the model follow your steps, but when I ran the following codes, errors occured:
python eval_rcnn.py --cfg_file cfgs/default.yaml --ckpt ../output/rpn/default/ckpt/checkpoint_epoch_200.pth --batch_size 4 --eval_mode rcnn
And the error is :
RuntimeError: Error(s) in loading state_dict for PointRCNN:
Missing key(s) in state_dict: "rcnn_net.SA_modules.0.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.0.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.0.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.0.mlps.0.layer2.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.1.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.1.mlps.0.layer2.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer0.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer0.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer1.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer1.conv.bias", "rcnn_net.SA_modules.2.mlps.0.layer2.conv.weight", "rcnn_net.SA_modules.2.mlps.0.layer2.conv.bias", "rcnn_net.xyz_up_layer.layer0.conv.weight", "rcnn_net.xyz_up_layer.layer0.conv.bias", "rcnn_net.xyz_up_layer.layer1.conv.weight", "rcnn_net.xyz_up_layer.layer1.conv.bias", "rcnn_net.merge_down_layer.layer0.conv.weight", "rcnn_net.merge_down_layer.layer0.conv.bias", "rcnn_net.cls_layer.0.conv.weight", "rcnn_net.cls_layer.0.conv.bias", "rcnn_net.cls_layer.2.conv.weight", "rcnn_net.cls_layer.2.conv.bias", "rcnn_net.cls_layer.3.conv.weight", "rcnn_net.cls_layer.3.conv.bias", "rcnn_net.reg_layer.0.conv.weight", "rcnn_net.reg_layer.0.conv.bias", "rcnn_net.reg_layer.2.conv.weight", "rcnn_net.reg_layer.2.conv.bias", "rcnn_net.reg_layer.3.conv.weight", "rcnn_net.reg_layer.3.conv.bias".

You're trying to evaluate an rpn module on rcnn eval mode. You have to use --eval_mode rpn in your command.

@bmankirLinker , thank you for your reply. But when I use .pth in rcnn , the error still occured. In the last step, I trained 30 epochs as the author listed. When I use the 30th .pth, the error will happened, but when I use others , it will be ok, but the result is not good .

@bmankirLinker , thank you for your reply. But when I use .pth in rcnn , the error still occured. In the last step, I trained 30 epochs as the author listed. When I use the 30th .pth, the error will happened, but when I use others , it will be ok, but the result is not good .

So when you run --eval-all option, it works fine till 30th epoch then get an error?
Never run into such thing, can you share your training commands and if any changes in your local repo?

I had same problem. If you are training with --train_mode rcnn_offline, try using --eval_mode rcnn_offline. For me that solved the issue.

I had same problem. If you are training with --train_mode rcnn_offline, try using --eval_mode rcnn_offline. For me that solved the issue.

Did you solve the problem? I met the same error, but I don't know how to deal it....

I had same problem. If you are training with --train_mode rcnn_offline, try using --eval_mode rcnn_offline. For me that solved the issue.

Did you solve the problem? I met the same error, but I don't know how to deal it....

I had this issue when training/evaluating on offline GT. I solved it by setting --eval_mode flag to rcnn_offline as shown below (just an example):
python eval_rcnn.py --data_path ../data/ --cfg_file cfgs/data.yaml --ckpt ../output/rcnn/data/ckpt/checkpoint_epoch_50.pth --batch_size 1 --eval_mode rcnn_offline --rcnn_eval_roi_dir ../output/rpn/data/eval/epoch_200/val/detections/data --rcnn_eval_feature_dir ../output/rpn/data/eval/epoch_200/val/features


set incoming packet limit per player

packet count
incoming packet size
decompressed packet size (potential attack vector)

not prio imo; velocity should handle this


Issue 14135 - std.uuid.randomUUID breaks @safety

Issue 14135 - std.uuid.randomUUID breaks @safety
https://issues.dlang.org/show_bug.cgi?id=14135
Do note I am committing this completely blind, and do not even know if it compiles. It should. The unit-tests should also pass, but if not, the unittests are arguably wrong.
Also, this should be a faster implementation, as it prefers reinterpret to primitive than assign, over re-interpret to array, then do slice copies.

And that should do it. I'll squash tomorrow. Anything else?

@JakobOvrum : Did you delete your comment? the randGen being safe must be new in master, because in 2.067, it's not safe. Thanks for bringing it up, fixed now.

OK. Done and rebased.

Pingitty boop.

LGTM

Auto-merge toggled on


Scripts in HTML Starter Template linked wrong

The links in the starter template were linked wrong, jquery.min.js doesn't exist in the CSS only download, but jquery.js does, same with the what-input script, it does not have a min version in the CSS download, only a version without min. The file foundation.min.js exists but it is in the vendor folder, not directly in the js folder. After fixing these three links in the starter template, everything I try is now working as expected.
Without these linked properly you cannot totally use Foundation.
The starter template should link everything correctly so everything works as shown in the tutorials. I actually was looking at other frameworks because I couldn't get all that I wanted to run working, and the wrong linking was why. I went back to my old Foundation code and everything is working perfectly. This template may just be old code from a previous version of Foundation when the file structure was different.
This fix will help new people to this framework learn and stay with Foundation.

Good call and thanks for the PR! Merged!

Thanks for the quick review and all you do!

But there should be both production(minified) and development version in the css only download i guess ??

The js/vendor folder in the CSS only version has:
foundation.js
foundation.min.js
jquery.js
what-input.js


Image optimization on data-srcset

Hi,
I am trying to efficiently lazyload background images from a data-srcset like this:
data-srcset="https://cdn.com/image/path/601x300/image.jpg 601w,https://cdn.com/image/path/747x373/image.jpg 747w ... "

and would like to convert these to .jpg files to .webp using pagespeed. I am aware that this issue has had some progress on /incubator-pagespeed-mod/pull/1899 - is there any chance of updates to this repo to reflect said progress for the nginx build.
Thanks!

Nginx still don´t have the latest version. <IP_ADDRESS>, avalaible for mod_pagespeed.
In this version a basic support for data-srcset is enabled with the PR #1899.
The version <IP_ADDRESS> is public 2 days ago, so I think in no much more time the nginx version can land.
Maybe @oschaaf can say a stimated ETA for this.

I want to stress that  <IP_ADDRESS>(incubating) is not released yet, though hopefully very soon! It is still being voted on

Alright, great. Thanks very much for the update!


Ensure compatibility with Sync Gateway 2.x

A Sync Gateway 2.0 beta is available (release notes). Verify that synctos' generated sync functions are compatible with it. Notably SG 2.0 has upgraded to a newer version of the Otto JavaScript engine that claims to be compatible with ECMAScript 5, except for some noted RegExp incompatibilities.
Furthermore, since ES5 (and by extension this newer version of otto) does include JSON.stringify, the templates/sync-function/json-stringify-module.js module should only be used as a fallback for older versions of Sync Gateway. For example, in templates/sync-function/template.js:
var jsonStringify = (JSON && JSON.stringify) ? JSON.stringify : importSyncFunctionFragment('json-stringify-module.js');

Note that the version of Underscore.js (1.4.4) has not changed in the newer version of otto.

I have performed a number of tests on the Sync Gateway 2.0 beta with sync functions generated by synctos, and it appears to be fully compatible. Pull request #262 includes minor improvements to enhance support for SG 2.0, but everything appears to be 👍 .

Addressed by #262


Support ionic 5

can i use this component for ionic 5?

Yes. It is working on ionic 5.

Yes. It is working on ionic 5.

<ion-rating [rate]="rate"
readonly="false"
size="default"
(rateChange)="onRateChange($event)">

when I clicked on star, event is not working in ionic 5 capacitor
please help me

Can you provide a StackBlitz demo of the issue?

its not working anymore on ionic 5 :(

its not working anymore on ionic 5 :(

How are you using it? it is working on ionic 5  i used it. Import it in your page you are using.  e.g: yourPage.module.ts

@all let me explain you guys, i added it on app and page module as usually and when i put it on template it works, i mean it renders on screens, but how @GaneshMalode1789 says, rateChange event doesn't work, i tried to use it with reactform but i does not update value neither.

check this: https://github.com/RodainaMohamed/ionic-rating/issues/9#issuecomment-558979477

@ALL let me explain you guys, i added it on app and page module as usually and when i put it on template it works, i mean it renders on screens, but how @GaneshMalode1789 says, rateChange event doesn't work, i tried to use it with reactform but i does not update value neither.

Check This: https://github.com/RodainaMohamed/ionic-rating/issues/9#issuecomment-558979477

@Saqib92  Thank you, its works!


Random errors leading to core dumped

Host: Ubuntu 18.04, x86_64
Edge TPU runtime: Installed libedgetpu1-std from repo deb https://packages.cloud.google.com/apt coral-edgetpu-stable main, version 12-1
Demo: checked out master at 9a7b16c
After running install_requirements.sh script, I run python3 pose_camera.py and
get different errors. I've even tried different USB ports:
Loading model:  models/posenet_mobilenet_v1_075_481_641_quant_decoder_edgetpu.tflite
Segmentation fault (core dumped)

Loading model:  models/posenet_mobilenet_v1_075_481_641_quant_decoder_edgetpu.tflite
terminating with uncaught exception of type std::logic_error: basic_string::_M_construct null not valid
Aborted (core dumped)

I've not seen any pattern on how they appear, but error is throw at https://github.com/google-coral/project-posenet/blob/9a7b16c77230cab8ab4fc72d34371ed14fca7d76/pose_camera.py#L97 and https://github.com/google-coral/project-posenet/blob/9a7b16c77230cab8ab4fc72d34371ed14fca7d76/pose_engine.py#L85
Any ideas what could be wrong ?
FYI, I've tflite_runtime 2.0.0 installed and I'm able to run my tflite models converted to edgetpu models on the same host, therefore, I'm discarding installation issues (lib location, permissions)

Are you still having this issue with the latest versions ?

Closing this due to lack of activity. Feel free to reopen if the issue still persists.


Leaderboards

Tracking who's won the most and lost the most might be fun, even if it requires a DB of some sort. Thoughts?

It's already backed by a database, every race and bet is recorded 🙂 so this is totally possible. What's more difficult is how you display this data: if it's in Slack then we need another slash command or an option to display a leaderboard. If it's on the web then we probably need authentication rather than letting usernames etc be publicly visible.

I already started work on an admin panel for checking on how many Slack instances and channels the race has been triggered in, but haven't got very far.

Was more just thinking a /leaderboard Slash command or something, a web-based board is way too much of a infosec nightmare.

I wonder whether it'd be better not to register more slash commands. Was wondering whether to add some parsing to the /race command so something like:
/race [options]              -> run a race
/race leaderboard [options]  -> view a leaderboard

@rowanmanning Makes sense to me 👍

This has been added now, there are two new options.
Get a leaderboard for the current channel
/race leaderboard

Get a global leaderboard for the whole Slack Workspace
/race leaderboard global


Fix faulty key types

Some keys were misspelled leading to the default keyword-type of "keyword" being used. The good news is that the new validation flags this as an error. the bad news is that from what I recall, we will need to reindex the types because they are changing from "keyword" to "integer"

Closing in favor of the new indexer structure


Attributes are still visible on storefront filter despite that are marked as hidden

What I'm trying to achieve
I would like to have attributes for internal usage, don't want to show them to user or don't want to make them visible in filters
Steps to reproduce the problem

Set attributes to be hidden/not visible to user
Check in storefront

Screenshots

System information
Operating system: all
Browser: all

I confirm there is some problem with this - when I enable 'Visible on Product Page in Storefront' it becomes available on product page which is expected, but it also becomes visible in the faceted filtering. I'll keep debugging it to check if it's backend or frontend issue.

OK so this is how it works:

Visible on Product Page in Storefront (visibleInStorefront in API) behaves as a master switch to determine whether an attribute is visible publicly. If enabled, storefront would render the attribute both in the faceted filtering and on product page
Use in Faceted Navigation (filterableInStorefront in API) is supposed to determine whether an attribute is visible in faceted filtering. Storefront's query currently fetches all public attributes without checking this value. To fix it quickly, we should change the storefront's query to get attributes to have filter: {filterableInStorefront: true}.

But the second problem is that filterableInStorefront requires visibleInStorefront set to True, otherwise an attribute won't be visible in the storefront at all.
We can fix the storefront's query but we still have a UX problem in the dashboard. Visible on Product Page in Storefront should either become a master switch called "Public/Internal attribute" and we should have another field to configure whether you want to display an attribute on the product page.


fix: update contracts to forc to v0.13.0

Add also shortcut commands on the root path to build and deploy contracts.

Contract changes look good!


Broken render on Macbook M1 Pro

https://github.com/Spiri0/Threejs-WebGPU-IFFT-Ocean-V2/assets/97088/bc3e5a55-3821-4ae6-b036-87ef1720876a
Chrome 124.0.6367.156

That looks pretty ugly. Is there an error message in the console?
Unfortunately I don't have a Macbook. I have to think about whether I know anyone who has one

That looks pretty ugly. Is there an error message in the console?

Hmm, there is!

The warning with the “normal” not found on geometry is harmless. This is because I save the creation of the normal attribute in the worker for the geometry, since the normal vectors come from the IFFT derivations. I'll still create normals even if they won't be used anyway. Then the warning is gone.
The one with the timeout I have never seen.
Can you please make a test in main in the RAF function:
//setTimeout(() => {
this.RAF();
//}, 1);
because the timeout is not neccessay. I've already taken that out of mine. This has become an unnecessary relic.

@sunag Any ideas?

@sunag Any ideas?

No yet... M2 and Windows it work done.

It also works without any problems on my desktop with Ubuntu with r161 to r164. I have to go to work now. I'll try to update to r164 this evening. This probably won't solve the problem, but it still makes sense. Then I can also use "await renderer.init();"

I have now updated to r164. And I also made sure that the warning about the missing normal vectors no longer appears by now creating normal vectors for the buffer geometries. In addition, the app is now initialized robustly.
Unfortunately I can only test this on the devices I have. This is my windows laptop and my ubuntu desktop. It runs well on both.
What about your Macs?

Turns out this is a bug in MacOS that has already been fixed in 14.5 👌


Timeouts not showing the reason

The reason is not shown when you receive a timeout message.
The fix is the following last line beginning with reason: in the following code:
  case 'timeout':
    this.emit('timeout', {
      target: message.data.message.data.args[0],
      target_user_id: message.data.message.data.target_user_id,
      created_by: message.data.message.data.created_by,
      created_by_user_id: message.data.message.data.created_by_user_id,
      duration: message.data.message.data.args[1],
      reason: message.data.message.data.args[2] || null,

Would you mind to add that? :) Thanks!

Sure will add that in and try to get it out later today after some testing.

i can push it if you want that, i've tested it already on my twitchbot, works like a charm.

Just published<EMAIL_ADDRESS>Bumped a minor because I added a bunch of previously unsupported chat actions as well as added the reason for timeouts!


Surface Pro 8 support

Hi!
Please add support for Microsoft Surface Pro 8 with SKU Surface_Pro_8_for_Business_1983 and Surface_Pro_8_for_Business_with_LTE_Advanced_1982
Thx.

please do :D

@BlueSoD
My workaround:
Download MSProducts.xml
Add the following model to MSProduct.xml:
<Model SystemSKU="Surface_Pro_8_for_Business_1983" ProductName="SurfacePro8" DisplayName="Surface Pro 8" SupportedBuilds="2009"></Model>
Save MSproduct.xml to an temporary folder.
Edit the file "C:\Program Files\MSEndpointMgr\Driver Automation Tool\Settings\OEMLinks.xml" and change the path for Manufacturer Microsoft to your msproduct.xml in your temporary folder.

The entries for Surface Pro 8 exists in the official MSProducts.xml but the display names have typos ("Sufrace")
<Model SystemSKU="Surface_Pro_8_for_Business_1983" ProductName="SurfacePro8" DisplayName="Sufrace Pro 8" SupportedBuilds="1809,1903,1909,2004,2009"></Model>
<Model SystemSKU="Surface_Pro_X_1876" ProductName="SurfaceProX" DisplayName="Sufrace Pro X with SQ1" SupportedBuilds="1809,1903,1909,2004,2009"></Model>
<Model SystemSKU="Surface_Pro_X_H_1876" ProductName="SurfaceProX" DisplayName="Sufrace Pro X with SQ2" SupportedBuilds="1809,1903,1909,2004,2009"></Model>


NIFI-3869 Add HTTP/2 support to ListenHTTP and HandleHttpRequest

Summary
NIFI-3869 Adds configurable support the HTTP/2 protocol in the ListenHTTP and HandleHttpRequest Processors.
The implementation includes a new nifi-jetty-configuration module under nifi-commons containing a reusable ServerConnectorFactory and standard implementation. The configuration module includes a custom Application Layer Protocol Negotiation (ALPN) Processor that supports Java 8 Update 251 and later, which aligns with the current minimum required Java version for NiFi. The Jetty http2-server and jetty-alpn-server libraries are now included in the nifi-jetty-bundle along with all other required Jetty libraries.
Both ListenHTTP and HandleHttpRequest include a new HTTP Protocols property that depends on the SSL Context Service property. Enabling HTTP/2 requires enabling TLS, and both components default to HTTP/1.1 for both standard and TLS configurations in order to avoid unexpected changes when upgrading. The HTTP/2 protocol supports negotiating support based on client requests using ALPN, but maintaining HTTP/1.1 as the default property setting allows administrators to enable HTTP/2 support if desired. The HTTP Protocols property supports the following configuration options:

http/1.1
h2 http/1.1
h2

The property values correspond to the values defined in RFC 7540 Section 3.1 and also align with the approach used for configuring HTTP Protocols in Apache HTTP Server. The value of h2 http/1.1 enables the server and client to negotiate the supported version, while selecting h2 or http/1.1 requires the client to support the selected version.
Tracking
Please complete the following tracking steps prior to pull request creation.
Issue Tracking

[X] Apache NiFi Jira issue created

Pull Request Tracking

[X] Pull Request title starts with Apache NiFi Jira issue number, such as NIFI-00000
[X] Pull Request commit message starts with Apache NiFi Jira issue number, as such NIFI-00000

Pull Request Formatting

[X] Pull Request based on current revision of the main branch
[X] Pull Request refers to a feature branch with one commit containing changes

Verification
Please indicate the verification steps performed prior to pull request creation.
Build

[X] Build completed using mvn clean install -P contrib-check

[X] JDK 8
[X] JDK 11
[X] JDK 17

Licensing

[ ] New dependencies are compatible with the Apache License 2.0 according to the License Policy
[ ] New dependencies are documented in applicable LICENSE and NOTICE files

Documentation

[X] Documentation formatting appears as expected in rendered files

Will review

I tested this using openssl s_client -alpn h2 -connect <IP_ADDRESS>:8101 -status and openssl s_client -alpn http/1.1 -connect <IP_ADDRESS>:8101 -status commands on both ListenHTTP and HandleHttpRequest and:

I was able to negotiate both ALPN protocols for when (h2 || http/1.1) was used
I was able to negotiate ALPN h2 for when (h2) was used
I was not able to negotiate ALPN for http/1.1 when http/1.1 was used

I'm not sure why the last case wasn't working.. probably not a big issue.

I tested this using openssl s_client -alpn h2 -connect <IP_ADDRESS>:8101 -status and openssl s_client -alpn http/1.1 -connect <IP_ADDRESS>:8101 -status commands on both ListenHTTP and HandleHttpRequest and:
* I was able to negotiate both ALPN protocols for when (h2 || http/1.1) was used

* I was able to negotiate ALPN h2 for when (h2) was used

* I was not able to negotiate ALPN for http/1.1 when http/1.1 was used

I'm not sure why the last case wasn't working.. probably not a big issue.

Thanks for the feedback and testing @thenatog! For the last case, the StandardServerConnectorFactory does not add the ALPN Connector when h2 is not selected. In other words, http/1.1 indicates that ALPN will not be used, and the components will use standard TLS and HTTP/1.1 connectors.

Roger that, +1 from me will merge


Tensor Processing Primitives: A Programming Abstraction for Efficiency and Portability in Deep Learning Workloads

Hello, can TPP be used as the backend of tensorflow?

No, if you refer to an already implemented integration with TensorFlow. Yes, if you want to implement such an integration.

Thank you for your participation and asking a question. Feel free to reopen this issue if you have more questions about the paper.


Correct number of role assignments per subscription

The documentation here states that Azure RBAC has a role assignment limit of 2000.
https://learn.microsoft.com/en-us/azure/storage/blobs/data-lake-storage-access-control#what-are-the-limits-for-azure-role-assignments-and-acl-entries
However, in this documentation it's mentioned that there is a role assignment limit of 4000.
https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-steps#step-5-assign-role

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

ID: a3aa443a-b30f-2914-5cb8-b032be075c07
Version Independent ID: ece80543-b5c2-7415-776c-06cdf55d2006
Content: Access control lists in Azure Data Lake Storage Gen2
Content Source: articles/storage/blobs/data-lake-storage-access-control.md
Service: storage
Sub-service: data-lake-storage-gen2
GitHub Login: @jimmart-dev
Microsoft Alias: jammart

Thanks for reporting @jomarvel - 4000 is the correct number. I've updated the access control model article and that change should be live by 3 PM.  Thanks again!
#please-close

@normesta
Thanks for your inputs


refactor logging system: collect logs in one socket

This PR refactors the logging system. Creates the logserver who centralizes the log processing allowing two different log modes:

singlefile: in this mode, all logs (syslog, pantavisor logs, containers logs, lxc console, etc) are centralized in one file called pv.log that file is located in the folder of the current revision, inside of the logs/ directory
filetree: this is the traditional log organization

Both modes are not exclusives and can be set at the same time.
Important: currently only is possible to send logs to the cloud if the filetree option is not set.
To set the different log modes, a new configuration option called log.server.outputs was added to the pantavisor.config file, the different modes can be set using a comma as a separator. For example:
log.server.outputs=singlefile,filetree

All current log options are working and the only issues/missing features are:

Currently the logs from the ph_logger fork are not sent to the log
The logs from logs/current/<container>/lxc/lxc.log aren't capture in singlefile mode

Check the clang errors in the build check, maybe happening because CI uses clang-format-11 and other versions might fail.
About log.stdout, have you checked if you cannot change it because it is in /proc/cmdline or overridden in any other place?
Also, please redact the whole PR message so everything is up to date and remove the things that are no longer valid.

To land this I would like to know that the default b ehaviour (old way of logging) is well tested; the new way can be buggy etc.:

by default old log behavior is preserved on new installs and on upgrades from existing
default configuration with local XP has been tested with local experience including no reboot updates etc.
default configuration with local XP has been tested with many containers in parallel running and logging (like 10)
can we also do a test container that puts some stress testing on this, like logging through socket in parallel and under load?
default behafviour with remote XP has been validated to upload logs to the cloud etc.


Godot  4.1.1

Create BeehaveTree
Cannot get class ''.
editor/editor_data.cpp:581 - Parameter "p_object" is null.
editor/scene_tree_dock.cpp:2275 - Condition "!child" is true.

Does this happen after restarting Godot a couple of times? Currently, Godot has a set of issues where it tries to load classes before having finished its loading/initialization step. So this is nothing we can do about but that is an issue with Godot itself.

I've been able to fix this when restarting Godot 4.1.1 after enabling the Beehave plugin.
Would it be possible perhaps to give a hint in that error message?
"Please restart Godot to finish Beehave setup" or something. If that's not possible, we should pin the fix somewhere or add it to the docs.

@rakista112 we may be able to improve the messaging on failed start up for sure, good idea.


fix: create Ajv instance lazily, that should fix request/request#2572

@ahmadnassri previously validator was used lazily, only when har-validator is used in request. Now it is used when har-validator is required. This issue would exist with all compiling (=fast) validators, not just with Ajv.
Once this PR is merged and published to npm the issue in the title will be resolved.

We can go further by pre-compiling schemas into modules with ajv-cli so that Function constructor is not used at the run time, like I did in table package. This would allow using har-validator in environments that have CSP enabled with unsafe-eval restriction. But I suggest publishing this fix first.

👍

@ahmadnassri thank you! please publish before all the Atom plugins that use request blow up :)

it's released as 4.2.1

sorry, missed it. I forgot that it releases automatically.


How do I set number of threads in candle ?

As in set_num_threads equivalent.

Depends on the backend, if you don't use mkl, then RAYON_NUM_THREADS if you use mkl then OMP_NUM_THREADS.

Thanks !
On Sun, Aug 27, 2023 at 9:03 PM Laurent Mazare @.***>
wrote:

Depends on the backend, if you don't use mkl, then RAYON_NUM_THREADS if
you use mkl then OMP_NUM_THREADS.
—
Reply to this email directly, view it on GitHub
https://github.com/huggingface/candle/issues/626#issuecomment-1694697165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAXGU4DDKQKZHVOD5EOPVALXXNSDFANCNFSM6AAAAAA4AMIJUQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Get public keys connect time out

I verify ID tokens using the Firebase Admin SDK, but get public keys connect time out
public GooglePublicKeysManager refresh() throws GeneralSecurityException, IOException {
...
HttpResponse certsResponse = this.transport.createRequestFactory().buildGetRequest(new GenericUrl(this.publicCertsEncodedUrl)).execute();
...
}

Most likely due to a network issue at your end, or a temporary issue with Google public key server. Please get back to us if the problem can be reproduced reliably.


Replace zedpac C

The only reason we use CGO_ENABLED=1 is because of zedpac. That, in itself, is just a single function that makes other calls. We should replace this with native go code when possible.

Actually no -- its not a single function -- it is an entire implementation of the duktape JavaScript engine that we're embedding -- replacing it will be pretty difficult.
Btw, @deitch we should probably start opening up issue up in EVE repo since this one won't transition to LF Edge.

we should probably start opening up issue up in EVE repo since this one won't transition to LF Edge.

Good point. I am going to move this one over there and close it here.


Update README.md

Changed a word in README file which looks little better for the sentence.

As an English speaker I think greatly sounds better. Truly is very formal.

Yes I agree with you on this point, but I created this PR under the thought of making it more formal.
Lemme know if it's worth merging this, or should I close this PR.

Any contributions you make are **truly appreciated**.
it looks good but can bbe better if we use this in my opinion
Any useful contributions you make are **truly appreciated**.

Any contributions you make are **truly appreciated**.
it looks good but can bbe better if we use this in my opinion
Any useful contributions you make are **truly appreciated**.

Hey @jaynarayan-vaishnav , that was smooth !😆
I will keep that in mind !
Thanks for the review !

Any contributions you make are **truly appreciated**. it looks good but can bbe better if we use this in my opinion Any useful contributions you make are **truly appreciated**.

Buddy keep it simple. We are here to decide whether the contribution is useful to the project or not.
But what I think is that adding like "Any useful contribution" will step the first-time contributor a step backward.

@kumarsonsoff3  Thanks for your input on this 🙂  it was just an opinion to make the guidelines more clear


Background Bug

Reference Issues/PRs
#60
What does this implement/fix? Explain your changes.

save_image and nft_storage methods background bug fixed
README.md updated

Any other comments?

@sadrasabouri Please review this PR 💯


Service Request by Monika Salvage for Milestones Data coherence sorting

[ ] Qualtrics Service Request Form was received from User
[ ] e-mail acknowledging that User's Qualtrics Service Request Form was sent
[ ] Problem NOT RESOLVED
[ ] Problem PARTIALLY RESOLVED
[ ] Problem FULLY RESOLVED and Issue is Closed
[ ] Qualtrics Post-Service Request Survey was sent to User

Use comments feature (below) to document:

A clear and concise description of the solution.

A clear and concise description of any alternative solutions or features you've considered.

Any additional context, such as screenshots about the problem.

Hi Jeff,
Monika raised the issue of her data being "disorganized under mIlestones in specification".
I know you worked on this before. Please can you help the counties in general writing a code so that these Milestones are all sorted by intended start date.
Thanks
Donrie

Yes, Jeff fixed this in Monitoring Milestones, but maybe in Specification.
Jeff, please add your sort feature to Specification, too.

Can you tell me the county/IPA/Strategy for this?
In the code, Milestones in Specification is already sorted by IntendedStart date.
Perhaps I'm missing something.

The county in question was Cayuga County

Hi Jeff:
Cayuga. Looks like Milestone Monitoring is fine. Maybe an issue in Specification.
DL

I found it. This should be all set now.

Thanks! Great.