Resolvers for Let's Encrypt DNS-01 challenge are not used

Welcome!

[X] Yes, I've searched similar issues on GitHub and didn't find any.
[X] Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What did you do?
I'm trying to configure Traefik with Let's Encrypt using DNS-01 challenge and the pdns provider.
I already accomplished this scenario using cert-manager instead of Traefik and it works fine, but I had to add extra configuration because I'm using a split-horizon DNS setup.
My assumption is that the resolvers config for Traefik should accomplish the same behavior.
What did you see instead?
You can see in the attached logs that the resolvers config has been detected :
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Checking DNS record propagation using [<IP_ADDRESS>:53 <IP_ADDRESS>:53]"

But on the last line that those resolvers are not used, and instead the resolvers defined in /etc/resolv.conf are used :
time="2023-10-25T05:11:41Z" level=error msg="Unable to obtain ACME certificate for domains \"test.example.com\": unable to generate a certificate for the domains [test.example.com]: error: one or more domains had a problem:\n[test.example.com] propagation: time limit exceeded: last error: read udp <IP_ADDRESS>:47017-><IP_ADDRESS>:53: i/o timeout\n" routerName=test@docker rule="Host(`test.example.com`)" providerName=myresolver.acme ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory"

What version of Traefik are you using?
Version:      2.10.5
Codename:     saintmarcelin
Go version:   go1.21.3
Built:        2023-10-11T13:54:02Z
OS/Arch:      linux/amd64

What is your environment & configuration?
docker.compose.yml
version: "3.8"

networks:
  traefik_public:
    external: true

services:
  server:
    command: "--configFile=/configs/traefik_static_config.toml"
    container_name: traefik
    environment:
      PDNS_API_KEY: "${PDNS_API_KEY}"
      PDNS_API_URL: "${PDNS_API_URL}"
    image: traefik:2.10.5
    networks:
      - traefik_public
    ports:
      - target: 80
        published: 80
        protocol: tcp
        mode: host
      - target: 443
        published: 443
        protocol: tcp
        mode: host
    restart: always
    volumes:
      - "server_certs:/certs"
      - "server_config:/configs"
      - "/var/run/docker.sock:/var/run/docker.sock:ro"

volumes:
  server_certs:
    driver_opts:
      device: "${VOLUMES_BASE_PATH}/traefik/server/certs"
      o: bind
      type: none

  server_config:
    driver_opts:
      device: "${VOLUMES_BASE_PATH}/traefik/server/configs"
      o: bind
      type: none

traefik_static_config.toml
[accessLog]

[api]
  dashboard = true

[certificatesResolvers.myresolver.acme]
  caServer = "https://acme-staging-v02.api.letsencrypt.org/directory"
  email =<EMAIL_ADDRESS>  storage = "/certs/acme.json"

  [certificatesResolvers.myresolver.acme.dnsChallenge]
    provider = "pdns"
    resolvers = ["<IP_ADDRESS>:53", "<IP_ADDRESS>:53"]

[entryPoints]
  [entryPoints.web]
    address = ":80"

  [entryPoints.web.http]
    [entryPoints.web.http.redirections]
      [entryPoints.web.http.redirections.entryPoint]
        to = "websecure"
        scheme = "https"

  [entryPoints.websecure]
    address = ":443"

[log]
  level = "DEBUG"

[metrics]
  [metrics.prometheus]

[ping]

[providers]
  [providers.docker]
    exposedByDefault = false

  [providers.file]
    filename = "/configs/traefik_dynamic_config.toml"

 traefik_dynamic_config.toml
[tls.options]
  [tls.options.default]
    sniStrict = true

  [tls.options.intermediate]
  cipherSuites = [
      "TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
      "TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
      "TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305",
      "TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305"
    ]
    minVersion = "VersionTLS12"
    sniStrict = true

  [tls.options.modern]
    minVersion = "VersionTLS13"
    sniStrict = true

If applicable, please paste the log output in DEBUG level
time="2023-10-25T05:09:37Z" level=info msg="Configuration loaded from file: /configs/traefik_static_config.toml"
time="2023-10-25T05:09:37Z" level=info msg="Traefik version 2.10.5 built on 2023-10-11T13:54:02Z"
time="2023-10-25T05:09:37Z" level=debug msg="Static configuration loaded {...}"
time="2023-10-25T05:09:37Z" level=info msg="\nStats collection is disabled.\nHelp us improve Traefik by turning this feature on :)\nMore details on: https://doc.traefik.io/traefik/contributing/data-collection/\n"
time="2023-10-25T05:09:37Z" level=debug msg="Configured Prometheus metrics" metricsProviderName=prometheus
time="2023-10-25T05:09:37Z" level=info msg="Starting provider aggregator aggregator.ProviderAggregator"
time="2023-10-25T05:09:37Z" level=debug msg="Starting TCP Server" entryPointName=websecure
time="2023-10-25T05:09:37Z" level=debug msg="Starting TCP Server" entryPointName=traefik
time="2023-10-25T05:09:37Z" level=debug msg="Starting TCP Server" entryPointName=web
time="2023-10-25T05:09:37Z" level=info msg="Starting provider *file.Provider"
time="2023-10-25T05:09:37Z" level=debug msg="*file.Provider provider configuration: {\"watch\":true,\"filename\":\"/configs/traefik_dynamic_config.toml\"}"
time="2023-10-25T05:09:37Z" level=info msg="Starting provider *traefik.Provider"
time="2023-10-25T05:09:37Z" level=debug msg="*traefik.Provider provider configuration: {}"
time="2023-10-25T05:09:37Z" level=info msg="Starting provider *docker.Provider"
time="2023-10-25T05:09:37Z" level=debug msg="*docker.Provider provider configuration: {\"watch\":true,\"endpoint\":\"unix:///var/run/docker.sock\",\"defaultRule\":\"Host(`{{ normalize .Name }}`)\",\"swarmModeRefreshSeconds\":\"15s\"}"
time="2023-10-25T05:09:37Z" level=info msg="Starting provider *acme.Provider"
time="2023-10-25T05:09:37Z" level=debug msg="*acme.Provider provider configuration: {...}"
time="2023-10-25T05:09:37Z" level=debug msg="Attempt to renew certificates \"720h0m0s\" before expiry and check every \"24h0m0s\"" ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory" providerName=myresolver.acme
time="2023-10-25T05:09:37Z" level=info msg="Testing certificate renew..."  providerName=myresolver.acme ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory" routerName=nexttest@docker rule="Host(`test.example.com`)"
time="2023-10-25T05:09:37Z" level=debug msg="Domains [\"test.example.com\"] need ACME certificates generation for domains \"test.example.com\"." ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory" routerName=nexttest@docker rule="Host(`test.example.com`)" providerName=myresolver.acme
time="2023-10-25T05:09:37Z" level=debug msg="Loading ACME certificates [test.example.com]..." providerName=myresolver.acme ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory" routerName=nexttest@docker rule="Host(`test.example.com`)"
time="2023-10-25T05:09:37Z" level=debug msg="Building ACME client..." providerName=myresolver.acme
time="2023-10-25T05:09:37Z" level=debug msg="https://acme-staging-v02.api.letsencrypt.org/directory" providerName=myresolver.acme
time="2023-10-25T05:09:37Z" level=debug msg="Using DNS Challenge provider: pdns" providerName=myresolver.acme
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Obtaining bundled SAN certificate"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] AuthURL: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/9058374894"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Could not find solver for: tls-alpn-01"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Could not find solver for: http-01"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: use dns-01 solver"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Preparing to solve DNS-01"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Trying to solve DNS-01"
time="2023-10-25T05:09:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Checking DNS record propagation using [<IP_ADDRESS>:53 <IP_ADDRESS>:53]"
time="2023-10-25T05:09:40Z" level=debug msg="legolog: [INFO] Wait for propagation [timeout: 2m0s, interval: 2s]"
time="2023-10-25T05:09:50Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:10:02Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:10:14Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:10:26Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:10:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:10:50Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:11:02Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:11:14Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:11:26Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:11:38Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Waiting for DNS record propagation."
time="2023-10-25T05:11:40Z" level=debug msg="legolog: [INFO] [test.example.com] acme: Cleaning DNS-01 challenge"
time="2023-10-25T05:11:41Z" level=debug msg="legolog: [INFO] Deactivating auth: https://acme-staging-v02.api.letsencrypt.org/acme/authz-v3/9058374894"
time="2023-10-25T05:11:41Z" level=error msg="Unable to obtain ACME certificate for domains \"test.example.com\": unable to generate a certificate for the domains [test.example.com]: error: one or more domains had a problem:\n[test.example.com] propagation: time limit exceeded: last error: read udp <IP_ADDRESS>:47017-><IP_ADDRESS>:53: i/o timeout\n" routerName=nexttest@docker rule="Host(`test.example.com`)" providerName=myresolver.acme ACME CA="https://acme-staging-v02.api.letsencrypt.org/directory"

Hello @nmengin
Hmm actually I think it's more a bug report than a question, that's why I posted here.
Anyway, I've just created a post on the community forum : https://community.traefik.io/t/resolvers-for-lets-encrypt-dns-01-challenge-are-not-used/20279.


Rename restart runtime to reconnect

(print screen got from Jose's today stream)
Jose was streaming and got this two label differences for the same action (reconnect the runtime). And he asked to make a PR to fix this. :)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


subjective: Con type alias seems to only be used in one place, and seems to make readability worse

consider removing it?

removed, eventually I'll probably just make a bunch of functions newStrengthReduceW*


Patch for issue #43

Please see issue: Directories containing a large number of files never complete #43
This patch creates a new Python Queue to track jobs that are currently in progress in the scandirwalk_worker threads.

merged pr into master, thank you for this patch.


Synchronizing SoftDiceLoss across GPUs

Write a detailed description of your PR here.
Please follow the guidelines for PRs contained here. Checklist:

[ ] Ensure that your PR is small, and implements one change.
[ ] Add unit tests for all functions that you introduced or modified.
[ ] Run PyCharm's code cleanup tools on your Python files.
[ ] Link the correct GitHub issue for tracking.
[ ] Update the Changelog file: Describe your change in terms of
Added/Changed/Removed/... in the "Upcoming" section.
[ ] When merging your PR, replace the default merge message with a description of your PR,
and if needed a motivation why that change was required.

Hello @ant0nsc! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file InnerEye/ML/models/losses/cross_entropy.py:

Line 11:80: E501 line too long (89 > 79 characters)
Line 103:80: E501 line too long (109 > 79 characters)
Line 107:80: E501 line too long (114 > 79 characters)

In the file InnerEye/ML/models/losses/soft_dice.py:

Line 10:80: E501 line too long (89 > 79 characters)
Line 16:80: E501 line too long (119 > 79 characters)
Line 17:80: E501 line too long (115 > 79 characters)
Line 20:80: E501 line too long (110 > 79 characters)
Line 31:80: E501 line too long (104 > 79 characters)
Line 32:80: E501 line too long (99 > 79 characters)
Line 35:80: E501 line too long (90 > 79 characters)
Line 37:80: E501 line too long (101 > 79 characters)
Line 40:80: E501 line too long (115 > 79 characters)
Line 42:80: E501 line too long (109 > 79 characters)
Line 98:80: E501 line too long (91 > 79 characters)
Line 104:80: E501 line too long (115 > 79 characters)
Line 112:80: E501 line too long (119 > 79 characters)

In the file InnerEye/ML/utils/image_util.py:

Line 605:80: E501 line too long (111 > 79 characters)
Line 609:80: E501 line too long (103 > 79 characters)
Line 612:80: E501 line too long (106 > 79 characters)
Line 620:80: E501 line too long (93 > 79 characters)
Line 622:80: E501 line too long (101 > 79 characters)
Line 623:80: E501 line too long (107 > 79 characters)
Line 626:80: E501 line too long (112 > 79 characters)
Line 627:80: E501 line too long (93 > 79 characters)

In the file Tests/ML/models/losses/test_dice_loss.py:

Line 92:80: E501 line too long (82 > 79 characters)
Line 96:80: E501 line too long (81 > 79 characters)
Line 103:80: E501 line too long (113 > 79 characters)
Line 110:80: E501 line too long (82 > 79 characters)
Line 116:80: E501 line too long (81 > 79 characters)
Line 130:80: E501 line too long (83 > 79 characters)
Line 134:80: E501 line too long (81 > 79 characters)


html - page too tall

Even though the browser window is tall enough to show the full page (including the footer), the footer bar is never fully visible:

Here is a snapshot of published content:
oxygen.zip
We require modifications to the oxygen-webhelp\template\f13ldman.css file to fix the above layout issue.

Hi @IanMayo , I think remove line 47 will fix this issue

result:

Yes, that looks perfect!

Fixed in https://github.com/DeepBlueCLtd/LegacyMan/commit/8188354f596ccbc66837318a5b0eed93bca3bb42


GA - Submitting proposal - validation submitted data vs provided URL is not working

To reproduce:

Start adding new proposal eg Info.
Fill all required info
Continue to last step with download of Info.json file
Provide input Paste the URL here: - tye valid url to not existing file and confirm - verification starts, no error is shown, wallet is called

Compare with recording.
https://github.com/IntersectMBO/govtool/assets/82152577/ad848c57-fa3b-40fc-9ea7-5d1e4b55578b

Hello @pmbinapps ,
Spot on! Not only is there a missing provided URL and submitted data validation check during GA proposal submission, but there's also the same issue for dRep registration and editing registered dReps.
For reference reports:

GA proposal submission : report
DRep registration : report
Edit registered dRep: report

OK for GA
https://jam.dev/c/631abc60-ccfa-4cf2-9160-3238c2cb3427
OK for DRep
https://jam.dev/c/80c2b85c-71b2-4a31-8a3d-e1d7641c7914

Can't test, as get same error as #1027

This has worked for me now on staging. Closing


hono/aws-lambda + @hono/graphql-server GET not working!

What version of Hono are you using?
4.3.7
What runtime/platform is your app running on?
Lambda
What steps can reproduce the bug?
Any idea why the GET method doesn't work?
import rootResolver from "./resolvers/resolvers"
import { GraphQLFileLoader } from "@graphql-tools/graphql-file-loader"
import { loadSchemaSync } from "@graphql-tools/load"
import { addResolversToSchema } from "@graphql-tools/schema"
import { graphqlServer } from "@hono/graphql-server"
import { serve } from "@hono/node-server"
import { Hono } from "hono"
import { handle } from "hono/aws-lambda"
import { compress } from "hono/compress"
import { cors } from "hono/cors"
import { logger } from "hono/logger"
import { prettyJSON } from "hono/pretty-json"
import path from "path"

const app = new Hono()

app.use(logger())
app.use(cors())
app.use(compress())
app.use(prettyJSON())

const schemaPath = path.join(__dirname, "schemas/schema.graphql")

const schema = loadSchemaSync(schemaPath, {
  loaders: [new GraphQLFileLoader()],
})

const schemaWithResolvers = addResolversToSchema({
  schema,
  resolvers: rootResolver,
})

app.use(
  "/graphql",
  graphqlServer({
    schema: schemaWithResolvers,
  }),
)

if (process.env.AWS_LAMBDA_FUNCTION_NAME) {
  console.log("Running in AWS Lambda environment.")
  exports.handler = handle(app)
} else {
  console.log("Server is running on http://localhost:3000")
  serve(app)
}

What is the expected behavior?

What do you see instead?

Additional information
No response

I have noticed (and fixed) this issue a while back when updating my fork to align with hono's current update, you could patch the package for a workaround in the time being.
Advertising alert - or you could use my fork: hono-adapter-aws-lambda, it also comes with a triggerProcessor handle AWS trigger events like S3, EventBridge.
I'll proceed to create a PR for official Hono now.

Hi @mthmcalixto, coming back to this issue, graphql is using HTTP method and should be supported by the official adapter.
For your case, it is actually because you were including a JSON body with a GET method, which is not supported by the Web Standard Request, you should put it as query parameter for GET requests.
And in your test output on AWS Lambda, I guess you were testing with a simple payload like this?:
{ "hello": true },
This is an invalid request and will throw at isProxyEventALB function.
You could check the AWS doc to see the valid payload for testing.

@NamesMT  Yes, it seems that I passed an empty graphql body and this caused an internal error.

Body empty:

That's weird, is "GraphQL query" in the Body a string that you put in or is it a placeholder by the API Client?,
From my testing, when the body is NOT EMPTY for GET requests, Lambda will returns a 502, and the localhost will return a 400 with empty error, that is correct,
But if you are sure your body is empty then do the following debug steps:

Check your CloudWatch log to see what Error has been thrown
Use another API client

If after that it still happens, could you setup a repo so that I can clone and test?
For my freshly set up repo, the GraphQL works fine with an empty body, and will works when I pass it as a query parameter for GET request, example:

Or you know what? You could just screw, never use GET requests and use only POST requests, GraphQL also recommend POST requests for easier sending of the query payload.

For my adapter fork,
Currently, it allows unknown events to be processed by v1Processor instead of throwing at isALBEvent check and it adds a triggerProcessor to support custom invokations following the format: { "eventSource":  "string" } and AWS event sources like S3, EventBridge,...

@NamesMT try to put the query empty and do a GET.

Hi @mthmcalixto, this is my response if I put the query empty and do a GET (Lambda):

The response is a proper 400 with message, not a 502

Hi @mthmcalixto, this is my response if I put the query empty and do a GET (Lambda):
The response is a proper 400 with message, not a 502

Try https://httpie.io/docs/desktop

@mthmcalixto
It will return 400 with message if the body is selected as None,
If the body is selected as GraphQL, even with nothing inputted, httpie will still include the JSON body of: {"query": ""}, so this issue is basically user error / HTTP client error.

You could have checked it the whole time in the Request tab 🤦🏽

 You could have checked it the whole time in the tab 🤦🏽Request

but it shouldn't return a 502 error, but a 400 error

Hi,
The problem here is by web standards, HTTP GET requests cannot contains a Body, and HTTPie will includes a body of {"query": ""} even when you have inputted nothing with GraphQL mode selected, so the request is invalid and therefor will cause error on Lambda while parsing the request.

Hi, The problem here is by web standards, HTTP GET requests cannot contains a Body, and HTTPie will includes a body of {"query": ""} even when you have inputted nothing with GraphQL mode selected, so the request is invalid and therefor will cause error on Lambda while parsing the request.

That's exactly the error I'm saying, it should return 400, not a 502.
The error is not handled.

Having similar issue.
On another note, in just using the Hello World example for AWS lambda in https://hono.dev/getting-started/aws-lambda, this problem can be also replicated. Reverted as of the moment as this issue isn't present at least on v4.2.9 with a couple of drawbacks like this issue was fixed on v4.4.1.

Hi @zerijodmanguardia,
Would greatly appreciate it if you could have the time to create an issue detailing your issue:D

A TL;DR FYI on the original issue for later comers, the issue was caused by user error, not Hono, more specifically, the HTTP client he is using: "HTTPie" will includes a JSON body with GET request, even when nothing is inputted, this will throw an error on AWS Lambda because it is not allowed according to web standards.


sysfs: drops os.File special casing for fs.FS to pass wasi-testsuite

This adds a wazero adapter which passes wasi-testsuite 100pct on darwin, linux and windows. While the main change was adding inodes to the wasi fd_readdir dirents, there was a lot of incidental work needed.
Most of the work was troubleshooting in nature, around windows specifically, but also wrapping of files. This backfills a lot of tests and reworked how wrapping works, particularly around windows.
To accommodate this, we drop os.File special casing except for sysfs.DirFS.
Why don't we attempt to pass wasi-testsuite on user-defined fs.FS?
While most cases work fine on an os.File based implementation, we won't promise wasi-testsuite compatibility on user defined wrappers of os.DirFS. The only option for real systems is to use our sysfs.FS.
There are a lot of areas where windows behaves differently, despite the os.File abstraction. This goes well beyond file locking concerns (e.g. EBUSY errors on open files). For example, errors like ACCESS_DENIED aren't properly mapped to EPERM. There are trickier parts too. FileInfo.Sys() doesn't return enough information to build inodes needed for WASI. To rebuild them requires the full path to the underlying file, not just its directory name, and there's no way for us to get that information. At one point we tried, but in practice things became tangled and functionality such as read-only wrappers became untenable. Finally, there are version-specific behaviors which are difficult to maintain even in our own code. For example, go 1.20 opens files in a different way than versions before it.

will start on windows as soon as I see if the testsuite agrees with me on linux and darwin ;)

ok I've organized pretty much what works and doesn't work. I'll work on the windows side when my laptop stops windows update ;)

I'll raise an issue post merge about that composite fs doesn't return inodes properly. this really can't happen until we have our own file type as trying now is really messy

huge milestone! (last piece?)

So, yeah it is a great milestone to be maybe the only runtime that passes wasi-testsuite on all platforms (not sure if others do, as they aren't testing windows).
This is the last for this release candidate. There are a couple corner cases we haven't finished for GOOS=js which once complete reveals the entire feature surface needed to make our file type. These will continue after the cut and maybe our internal structure can be stable by 1.0.


MINOR: preparing for bug fix release

You don't need to do this. The release script should create the tag with the right versions.

@ijuma @dguy I think the changes in pom.xml needs to be done manually, since they are recently added post <IP_ADDRESS> release for the streams quickstart archetype project.


Token problem

What am I doing wrong?
I have a token, it's the same token I'm using with https://github.com/joeyespo/grip
Cool.
So I just store the token in the password field for the api.github.com block in the .netrc? The login field wouldn't be needed at this point, but I've tried it with or without. I haven't debugged, so all I know is:
Got 404, update your token to with the gist scope (verbatim)
I like that your plugin is light as heck on the vim side especially. I think a few things should happen:

That error message is confusing, but it makes me wonder if it's not reading my token at all.

Heck with the required description, let's make that your preferred default, but also able to be turned off (can you not POST an empty description?  Oh and my .netrc permissisions are 600.

 The "typo" in the error message made my brain stop trying and understand it meant to give the token create gist permissions.
:cool:

😛 🦆


Fix panic on update cluster queue status if cluster queue not found on queue manager.

What type of PR is this?
/kind bug

What this PR does / why we need it:
Fix panic on update cluster queue status if cluster queue not found on queue manager.
Which issue(s) this PR fixes:

Fixes #2459
Special notes for your reviewer:
Does this PR introduce a user-facing change?

Fix panic on update cluster queue status if cluster queue not found on queue manager.

/test all

So it looks like the error occurred when a ClusterQueue was deleted while a reconciler was still running on it, right?
In that case, a restart of Kueue would fix the issue.
/release-note-edit
Fix panic that could occur when a ClusterQueue is deleted while Kueue was updating the ClusterQueue status.

/lgtm
/approve

/cherry-pick release-0.7


Remove performance improvement for hasTask/getTasks

Those changes seemed to have caused up-to-date assemble on largeJavaMultiProject (parallel false) to fail.
I don't quite understand why the problem is fixed when removing the optimisation, but it works anyway...

Successful performance test coordinator build: https://builds.gradle.org/viewLog.html?buildId=12858687&buildTypeId=Gradle_Check_PerformanceTestCoordinator

Abandoned.


rows grabbed from db as a parameter

limit # of rows grabbed from db

limit # of rows grabbed from db


About page should focus more on OpenTelemetry, less on observability

Need to reword the about page so that it:

Focuses more on the project rather than the scope / industry
Better reflects the beta status
Move "Get Involved" content to this page

I'll work on this next week


Example of adding more hybrid algorithms to generate.yaml

is there any change to make this combination through the template generator

Yes, this should work -- but please note that this would be a hybrid, not a composite (edit/add: Please check the README at the link above to see the differences). If you're really after a Composite, I'd suggest touching base with @feventura who contributed that code).

Originally posted by @baentsch in https://github.com/open-quantum-safe/oqs-provider/issues/426#issuecomment-2161108300
Hello @baentsch  When I try to add for example rsa4096_dilithium3 or rsa3072_dilithium3 or pss4096_dilithium3 to generate.yaml, and I create a key/certificate the generated classic key is always rsa2048, while for p521_dilithium3 or p256_dilithium3 it always generates p384 for classic part.
Is there anything besides this or the approach itself is not good and simply can't add those combinations ?
Br
Maro

Please post your changes to generate.yml, what exactly you then executed (generate/build/execute), what you expected and what actually happened (as well as the platform used, of course).

Thanks


Fixing channels amount bug where we weren't able to close chan with e…

…scrow, removing some logging

Coverage decreased (-0.2%) to 90.363% when pulling b5c55a9ca732a8eed4f7dd1a23f9b8dd8a08331c on Christewart:fix_channels_amount_bug into 54a9525c3bc601ee327bb2681836cd2d2210ab55 on bitcoin-s:master.


feat(frontend): spider授权白名单

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


docs: mention docker.io and new kubectl versions

Closes #14

@prometherion is this ok to merge?

@ptx96 may I ask you to revamp this, as well as update the compatibility matrix with v1.28 support thanks to #24?


ENH: least_squares: should not re-instanciate csr_matrix if already provided by user (performance gain)

Current status (scipy 1.4.1)

When using scipy.optimize.least_squares(), the user can, if he/she knows its form, provide the jacobian as a callable to accelerate convergence and avoid discretization errors.
This option is very valuable since it can make a significant difference, especially for problems with large datasets and many variables (i.e.: large jacobian matrices)
Currently, scipy.optimize.least_squares() first checks whther jac is callable, and if so tests whether it is sparse, because when the user provides a sparse jacobian it should be faster use at every iteration.
If sparse, a wrapper is implemented to make sure the jac is a csr_matrix format
This wrapper is called for every iteration, hence possibly hundreds or thousands of times, and every time it converts jac to csr_matrix
This conversion takes a bit of time (not much I agree), but it does not take advantage of the fact the user may already provide jac as a csr_matrix, in which case this conversion is not necessary and time can be saved at every iteration.

I would suggest

The docstring should explain that, even when it is a callable, jac can (and probably should) be provided as a sparse csr_matrix by the user (indeed, I though sparsity was only relevant for discrete evaluations of jac, i.e.: '2-points' or '3-points', I only realized that a sparse callable would be used too by looking at source code).
To preserve the generality of the scipy.sparse.csr_matrix() instanciation and still save time when jac is already a csr_matrix, we could:

test if csr_matrix and implement wrapper only if not
or use the method .tocsr() which does the same except that, by default, if the matrix is already csr it returns a reference to itself, which is much faster than forcing instanciation of a new csr
or make sure csr_matrix instanciation returns a reference to the passed array if it is already a csr_matrix (i.e.: equivalent to using tocsr() method)

A solution is proposed in PR #12250
Performance gain evaluation
In [1]: import scipy.sparse as scpsparse

In [2]: a = scpsparse.csr_matrix(np.random.random((100,1000)))

In [3]: %timeit b = scpsparse.csr_matrix(a)
19.1 µs ± 158 ns per loop (mean ± std. dev. of 7 runs, 100000 loops each)

In [4]: %timeit b = a.tocsr()
106 ns ± 0.644 ns per loop (mean ± std. dev. of 7 runs, 10000000 loops each)

In [5]: 19e3/106
Out[5]:<PHONE_NUMBER>1886792

That's two orders of magnitude faster, and the gain occurs at every iteration of least_squares().
Indeed, tocsr() returns a reference to the already existing instance by default:
In [13]: a.tocsr??
Signature: a.tocsr(copy=False)
Docstring:
Convert this matrix to Compressed Sparse Row format.

With copy=False, the data/indices may be shared between this matrix and
the resultant csr_matrix.
Source:
    def tocsr(self, copy=False):
        if copy:
            return self.copy()
        else:
            return self

Fixed by gh-12250.


Add docs-rs extension

Description

Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi!
Thanks for your contribution! My name is Milena and I'm reviewing your extension today.
I just installed it here and it works. However, it made me think: what would be the difference between this extension and a Quicklink with a query parameter? I don't see it adding much value as is.
Cheers,

@mil3na you have a point, I didn't think of the quicklinks to begin with. Also, after putting this together quickly I discovered there's a crates.io extension which also has an action to open the latest documentation. So I will close this.


Cannot use request with an argument with its name

./zig-cache/zig-wayland/virtual_keyboard_unstable_v1_client.zig:7:61: error: redefinition of 'key'
pub fn key(virtual_keyboard_v1: *VirtualKeyboardV1,time:u32,key:u32,state:u32) void {const proxy = @ptrCast(*client.wl.Proxy,virtual_keyboard_v1);var args = [_]common.Argument{.{ .u = time},.{ .u = key},.{ .u = state},};
                                                            ^
./zig-cache/zig-wayland/virtual_keyboard_unstable_v1_client.zig:7:5: note: previous definition is here
pub fn key(virtual_keyboard_v1: *VirtualKeyboardV1,time:u32,key:u32,state:u32) void {const proxy = @ptrCast(*client.wl.Proxy,virtual_keyboard_v1);var args = [_]common.Argument{.{ .u = time},.{ .u = key},.{ .u = state},};
    ^
./zig-cache/zig-wayland/virtual_keyboard_unstable_v1_client.zig:7:199: note: referenced here
pub fn key(virtual_keyboard_v1: *VirtualKeyboardV1,time:u32,key:u32,state:u32) void {const proxy = @ptrCast(*client.wl.Proxy,virtual_keyboard_v1);var args = [_]common.Argument{.{ .u = time},.{ .u = key},.{ .u = state},};

Hmm, I suppose we should probably just prefix all argument names with an underscore. This is rather unfortunate though :/

Yeah I don't see a better way to deal with this<PHONE_NUMBER>8a4c618683a536489e3f69fc035038


Please support ksh

mksh, ksh93 and pdksh are classic POSIX shells and widely used, probably more widely than the zsh. Please add support for ksh flavors.

I just wanted to start small :). added zsh because it's my main shell.
I'll try to add support for the other shells in the next weeks.
Also, If you're familiar with these shells, I would appreciate contributions :)

fish too!

No one uses fish!

Would definitely love fish support. It's heavily used by my company and other developers I know.


Added cardinal properties to L.LatLngBounds

According to the Leaflet API and documentation, there were 4 missing property methods from the Leaflet.d.ts file for the L.LatLngBounds class, which have been added.
getNorth(): number
getSouth(): number
getWest(): number
getEast(): number
http://leafletjs.com/reference.html#latlngbounds

@jplante thanks mate!


Nan::TryCatch instantiated but not used

Both callback_helpers.cc and field_accessors.cc define a Nan::TryCatch but doesn't reference it at all afterwards.
On the other hand, the instantiated instance in nodegit_wrapper.cc is used and checked.
Nan::TryCatch tryCatch;
instance = new cppClass();
// handle the case where the default constructor is not supported
if(tryCatch.HasCaught()) {
  delete instance;
  tryCatch.ReThrow();
  return;
}

Is something missing here?

That's definitely an oversight. I'm not sure what the original intention with a thrown error is though. I feel like handling the error in C++ is going to be tricky so our best bet right now is to remove the unused Nan::TryCatch and then add it in again later when we have a good strategy for what to do with it.


"All" endpoint with query params to include or exclude fields

is_foil
MTGJSON set name
prices

Solved with /cards/search endpoing.


Restore does not work with 0.8.0-beta.3 + ember-cli-simple-auth-token

Hello,
Posting this here since this may be related to the latest updates to the simple-auth package...
I'm trying to determine what has changed that breaks the restore functionality in the latest ember-cli-simple-auth-token
Ive gone through the changelog and notice the breaking change relating to the secure keyword in the stored session data but not sure if that's related.
Just wondering if you have any ideas? Again the restore functionality worked in the 0.6.0 tag of the token package and so the breaking change may or may not be related to change in simple auth since the latest tag 0.7.1 requires using 0.8.0-beta.2+
Any help appreciated!

The changes with the shouldn're require changes in the authenticators. You might want to ask for help in the https://github.com/jpadilla/ember-cli-simple-auth-token repo.

@marcoow that's what I thought, I did submit an issue there but as one of the contributors I thought I'd also run it by you since you wrote the simple auth package and maybe Im missing something..
Did you get a chance to glance at that restore method?
Also, why isn't the jwt package listed anywhere on the simple auth side?

https://github.com/jpadilla/ember-cli-simple-auth-token isn't part of Ember Simple Auth, it's an authenticator/authorizer package that you can use with ESA. I'm not sure how that's implemented internally.

right I know that, just wondering why it isn't also listed as it makes use of ESA and is similar to e.g. esa oauth/esa devise etc..
anyways no worries ill keep looking into this thanks


Data viewer cuts off bottom ~4 rows

If the terminal panel is up, sometimes you can't see all the rows in the data viewer or the horizontal scrollbar until you close the panel.

Can scroll to see the whole table.
Validated


Onboard CI pipeline to this repo

Description

pre-commit should contains aspects like json validation, detect secrets.
end to end test should deploy the full stack

New or affected modules

By submitting this issue, you agree to follow our Code of Conduct

Now added


Markers Icon is not accurate

as our icon is circle, and default behaviour of maps marker's icon is on top of coordinate point, this  causes misinterpreted data and unsynchronized behaviour with pulse animation
figuring out how to put the exact center of icon on the coordinate point will fix this issue

I will tackle this one @fajarnuha


Parse typescript components

It would be wonderful if Sveld could generate proper typescript declarations for typescript components (ie: lang="ts), rather than only JS-annotated types.

Could you clarify what you mean?
The use case for this library is to make plain Svelte components compatible with users who do use lang="ts".

Svelte components that use lang="ts" still aren't strongly typed (with props, etc) when consumed by an app using lang="ts", afaik they still need a proper class declaration like sveld generates. So it'd be great if sveld could generate that declaration for typed components, as well as plain ones.
I may be wrong here, but that's been my experience when using my own distributable Svelte components (written with lang=ts) in projects.

Interesting. So you author components in TS and want them to be consumable by non-TS apps.
Just thinking a loud here, but would the following work for you use case?

write TS Svelte components
use svelte-preprocess to strip any TypeScript
emit uncompiled, non-TS Svelte source files to a different folder

So I actually want to use them in TS apps, but Svelte/TS isn't smart enough to pick up on props etc without a declaration file for the component.
But to your point, that doesn't really work anyway. Apps like Sapper that consume svelte components need the uncompiled .svelte source, and afaik svelte-preprocess is only a buildstep tool as part of compiling an (m)js output.

Understood – that's a compelling use case.

https://github.com/firefish5000/svelte2dts does something like this already but is not that shaped out as sveld yet. Essentially it uses svelte2tsx to create a tsx file, then lets tsc generate type definitions from that, and some cleanup afterwards. The advantage is that you get all the advanced stuff like "component imports interfaces" for free. Not sure how that would fit the existing architecture of sveld though. svelte2tsx would likely need some adjustments, too, if you decide to go that route.

Ooh looks promising! I'll give it a try for my next component

For anyone stumbling across the same problem, @betaboon has a nice solution for lang=ts: svelte-type-generator.

sveld 0.8.0 does typescript preprocessing using svelte-preprocess with default options so it shouldn't error now in most cases. I still encountered an error when a component imports a .ts file. But was able to work around it by changing the .ts to a .svelte and wrapping everything in a <script context="module" lang="ts">


[SP-5175] Backport of PDI-18148 - java.lang.NullPointerException is t…

…hrown when a transformation is executed remotely on a Pentaho Server/Carte when File logging is enabled. (7.1 Suite)
@LeonardoCoelho71950 @pentaho-lmartins @ppatricio

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -f core/build.xml checkstyle publish-local
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -f engine/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/logging/SimpleLoggingObject.java
  engine/src/org/pentaho/di/www/BaseJobServlet.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.logging.SimpleLoggingObject

Complexity Change: -2.5% :small_red_triangle_down:
Instruction Change: -2.2% :small_red_triangle_down:
Line Change: -2.7% :small_red_triangle_down:
Method Change: -2.6% :small_red_triangle_down:

org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.2% :small_red_triangle_down:
Complexity Change: -7.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dbproc.DBProcMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Method Change: -1% :small_red_triangle_down:

org.pentaho.di.trans.steps.ldapoutput.LDAPOutputMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -2.2% :small_red_triangle_down:
Complexity Change: -2.6% :small_red_triangle_down:

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.setvalueconstant.SetValueConstantMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.webservices.WebServiceMeta

Branch Change: -1.7% :small_red_triangle_down:
Complexity Change: -1.2% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.www.TransformationMap

Branch Change: -1.2% :small_red_triangle_down:
Complexity Change: -1.5% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.7% :small_red_triangle_down:


[WIP] bitwise operator mask

Closes #7332

Can one of the admins verify this patch?

add to allowlist

@ek234 I see the CI hasn't run all the tests because there are conflicts. I believe that these conflicts are causing some checks not passing, notice that one says "AppVeyor was unable to build non-mergeable pull request" and the gpuCI is probably failing for the same reason.
You might want to merge main into your branch, fix the conflicts, and push again. That way the full CI suite will run and if we get any fails we will be able to assist you better.

Thanks for the review
I did as you said and then went through the readthedocs errors
Let me know if you would like me to make any changes.

bruh it's all green now:P

@ek234 thank you for your patience, I'm pinging another maintainer to see if they can review the code.
@jrbourbeau Would you mind reviewing this PR? We are at a point that we need a maintainer to take a look. I've suggested some changes, but I think we need a deeper look.

Thanks for all your work here @ek234, and apologies for the delayed review. This issue turned out to be a bit more complicated than a good-first-issue (apologies for the mislabeling). Since where interacts with out (which mutates the passed array), and dask arrays are effectively immutable, this required some nuanced changes to how elemwise works internally. I've pushed up a commit to your branch that makes the required changes on top of your initial PR. Thanks for your work here, hope to get this merged soon.

Looks like this PR may take care of what https://github.com/dask/dask/pull/8322 is trying to accomplish

Ah, that it does. I've added it to the top-level comment to auto-close.

@jcrist Is there anything left to be done here? Looks like CI is now passing, though there are now merge conflicts to be resolved.

Thanks for the ping, I'd forgotten about this. Merge conflicts fixed, should be good to merge once tests pass.

Thanks @ek234, this is in.


Sort network plugin lists alphabetically

This PR structures the various - currently unstructured - lists of networking plugins through alphabetization.

This change is

needs a rebase, sorry

@thockin rebased.


get-started/nodejs/develop relies on a project not included in part 1 or 2

File: get-started/nodejs/develop.md
this page refers to a project notes-service from Part-1 that the current node-js track and get-started pages don't have. there is no mongodb set-up example.
the current https://docs.docker.com/get-started/nodejs/run-containers/ and https://docs.docker.com/get-started/nodejs/build-images/ build node-docker which runs a mock server, db.

Thanks for sharing the issue. This was resolved by https://github.com/docker/docker.github.io/pull/11770
If the issue still persists, please let us know.


Drill error when using a filter in Superset with a CASE WHEN in the SQL query

Hello,
Describe the bug
Apache Drill 1.21.1
Apache Superset 3.1.1
In Superset, we setup a connexion to Drill as source for our dashboards
To Reproduce

In Superset, I created a graph (several in fact) using a SQL query with a CASE WHEN to display labels instead of the data. Here is an example I'm using for a graph :

with
tmp_etablissements as
(
select distinct
id, uai, nom, aca_id, nature_id
from base_kinto.vss_etablissements
),
tmp_domaines as
(
select
id, libelle
from base_kinto.vss_domaines
),
tmp_offres_lmd as
(
select
id, uai_principal
from base_kinto.vss_offres_lmd
),
tmp_diplomes_doctorat as
(
select
id, intitule, inf, id_parent, type_diplome, domaine
from base_kinto.vss_diplomes_doctorat
),
tmp_diplomes_capa as
(
select
id, intitule, inf, id_parent, type_diplome, '' as domaine
from base_kinto.vss_diplomes_capa
),
tmp_diplomes_daeu as
(
select
id, intitule, inf, id_parent, type_diplome, '' as domaine
from base_kinto.vss_diplomes_daeu
),
tmp_diplomes_deust as
(
select
id, intitule, inf, id_parent, type_diplome, domaine
from base_kinto.vss_diplomes_deust
),
tmp_diplomes_licence as
(
select
id, intitule, inf, id_parent, type_diplome, domaine
from base_kinto.vss_diplomes_licence
),
tmp_diplomes_licence_pro as
(
select
id, intitule, inf, id_parent, type_diplome, domaine
from base_kinto.vss_diplomes_licence_pro
),
tmp_diplomes_master as
(
select
id, intitule, inf, id_parent, type_diplome, domaine
from base_kinto.vss_diplomes_master
),
tmp_diplomes as
(
select * from tmp_diplomes_doctorat
union all
select * from tmp_diplomes_capa
union all
select * from tmp_diplomes_deust
union all
select * from tmp_diplomes_daeu
union all
select * from tmp_diplomes_licence
union all
select * from tmp_diplomes_licence_pro
union all
select * from tmp_diplomes_master
)
select
tmp_diplomes.id as ID,
tmp_diplomes.intitule as Nom du diplôme,
case
when tmp_diplomes.type_diplome = 'D' then 'Doctorat'
when tmp_diplomes.type_diplome = 'L' then 'Licence'
when tmp_diplomes.type_diplome = 'LP' then 'Licence Pro'
when tmp_diplomes.type_diplome = 'M' then 'Master'
else tmp_diplomes.type_diplome
end as Type diplôme,
tmp_domaines.libelle as Domaine,
tmp_etablissements.uai as UAI de l'établissement,
tmp_etablissements.nom as Nom de l'établissement
from tmp_diplomes
inner join tmp_offres_lmd on tmp_diplomes.id_parent = tmp_offres_lmd.id
inner join tmp_etablissements on tmp_offres_lmd.uai_principal = tmp_etablissements.uai
left join tmp_domaines on tmp_diplomes.domaine = tmp_domaines.id
;
As you can see, the CASE WHEN is used to change some data:
when tmp_diplomes.type_diplome = 'D' then 'Doctorat'
when tmp_diplomes.type_diplome = 'L' then 'Licence'
when tmp_diplomes.type_diplome = 'LP' then 'Licence Pro'
when tmp_diplomes.type_diplome = 'M' then 'Master'

Then I created a filter in the dashboard containing this graph.

When using this filter with one of this label from the CASE WHEN, it works fine. But when I used multiple labels from the CASE WHEN (see screenshot), I have an error message from Drill:

Error: Final Drill query state is FAILED. Unexpected exception during fragment initialization: Error while applying rule ReduceAndSimplifyFilterRule, args [rel#440596:LogicalFilter.NONE.ANY([]).[](input=RelSubset#440443,condition=SEARCH(CASE(=($4, 'D'), 'Doctorat', =($4, 'L'), 'Licence', =($4, 'LP'), 'Licence Pro', =($4, 'M'), 'Master', $4), Sarg['Licence':CHAR(11), 'Licence Pro']:CHAR(11)))]
I tested the same SQL query but without the CASE WHEN, using 'L', 'LP' in the filter, it works fine.
I think that Drill doesn't like when using values other than the initial data.
Since it is a Drill error message, I opened this ticket here, but maybe you will check with your Apache colleague in charge of Superset and the ossie may be in Superset for every source, not only Drill ?
Let me know if you need more information.
Regards,

Hello,
Kind reminder about this issue.
Regards,

Can you share the SQL that Drill tries to execute? It should be written to the Drill logs...


split function don't work as expected

Hi,
the split function don't work as expected. The problem seems to be in this lines:

if w == "" then
n = n + 1
end

This works for me:

if w ~= "" then
ret[n] = w
n = n + 1
end

Maybe you can fixit.
Thanks!

Done, thx!


xerrors: Add a function to test an error's chain against a predicate function

I'm splitting this off from #29934 to allow for more focused discussion.
There are three common patterns used in Go code to make control flow decisions based on an error's value.

Comparison to a sentinel: err == X.
Conversion to a known type: _, ok := err.(T); ok
Testing against a predicate function: f(err).

The error values proposal provides Is and As functions to test an error's chain against a sentinel value or underlying type, respectively. It does, however, not currently provide direct support for the third pattern of  predicate functions.
Proposal: Add an IsFunc function to test an error's chain against a predicate function to the golang.org/x/xerrors and errors packages.
// IsFunc calls f for each error in err's chain. IsFunc immediately returns true if f
// returns true. Otherwise, it returns false.
func IsFunc(err error, f func(error) bool) bool { ... }

IsFunc can be used directly with existing predicate functions like os.IsNotExist:
if errors.IsFunc(err, os.IsNotExist) { ... }

Why not update os.IsNotExist et al. to unwrap errors?

No good way to write code that works with current and future versions of Go: You can't rely on os.IsNotExist unwrapping so you need to do it yourself to support pre-1.13 Go.

This puts the onus on the user to determine if any given predicate function supports unwrapping, and as of what version.

Passing a wrapped error to a predicate which doesn't unwrap is a silent runtime bug. The error can't be detected at compile time, and it isn't even a runtime panic; you just silently take the wrong branch.

If we were starting entirely anew, then it might make sense to put the unwrapping in the predicate functions. Doing so at this time seems difficult to accomplish without encouraging the creation of many subtle bugs.

I also played with a version that returns the error that matches the predicate or nil, but

it's almost never needed. In situations where this comes up you mostly just care whether there is an error that matches the predicate.
when it's not needed, you have to tack a != nil on the end
when it is needed, you still need to do whatever assertion/testing again to recover the desired error so at that point it makes more sense to write your own helper that does the tests and returns the correct kind of error

The example predicate I used in the previous thread:
func temporary(err error) bool {
  t, ok := err.(interface{ Temporary() bool })
  return ok && t.Temporary()
}

There's talk in the original thread of updating As to let you assign to interfaces. With that you could do
type temp interface { Temporary() bool }
if xerrors.As(err, &temp) && temp.Temporary() { ... }

but note a subtle difference: IsFunc(err, temporary) returns true if any error in the chain both matches that interface and returns true but the As example only takes the error path if the first error in the chain that matches the interface returns true. Which is correct depends on the application and the potential composition of the error chain, so it's hard to say whether that subtlety is a feature or a bug. This would apply to xerrors.IsFunc(err, os.IsTimeout).
For os.IsExist et al., many of those predicates has a corresponding sentinel error like os.ErrExist that is among the errors that cause the predicate to return true. With appropriate Is methods on *os.PathError et al., those methods would allow you to write xerrors.Is(err, os.ErrExist). That would work nicely and consistently for code that does not need compatibility but otherwise has the same drawbacks as updating the predicates themselves.

With appropriate Is methods on *os.PathError et al., those methods would allow you to write xerrors.Is(err, os.ErrExist).

I think this is absolutely the cleanest API to expose to a user, and we should consider doing it. It does, as you say, have the same drawback of potentially becoming a silent bug in older Go versions. On the other hand, if you always write errors.Is(err, os.ErrExist) (not xerrors.Is), then the failure is at compilation time.

If a predicate function eventually adds support for unwrapping for the user, wouldn't this result in a O(n^2) runtime?
Suppose you had errors E3 (outer-most), E2, and E1 (inner-most). None of which match the predicate function. Then calling:
xerrors.IsFunc(E3, MyFunc)

would result in a call tree like:
call xerrors.IsFunc(E3, MyFunc)
├── handle E3
│   └── call MyFunc(E3)
│       ├── handle E3
│       ├── handle E2
│       └── handle E1
├── handle E2
│   └── call MyFunc(E2)
│       ├── handle E2
│       └── handle E1
└── handle E1
    └── call MyFunc(E1)
        └── handle E1

The problem is that both IsFunc and the predicate function walks the entire chain. IsFunc doesn't know if the provided predicate function will already walk the chain, and the predicate function doesn't know if it is being called by code that is already walking the chain. As such, both functions duplicate the work and walk the chain.
For sufficiently long error-chains, this can be kinda costly.

If a predicate function eventually adds support for unwrapping for the user, wouldn't this result in a O(n^2) runtime?

O(n log n), I think?
But yes, adding errors.IsFunc implies that predicate functions should never add support for implicit unwrapping. Fortunately this doesn't require any work, since none of them unwrap today.

I also played with a version that returns the error that matches the predicate or nil, but

I use a version that returns an error

it's almost never needed. In situations where this comes up you mostly just care whether there is an error that matches the predicate.

HTTP error type: passing the user visible msg+error code
Crossing RPC boundaries: some of my errors implement an interface that allows them to be serialized and be recovered by the RPC client
Monitoring: my prometheus reports not just error, but the component which first caused the error
Structured logging: I used zap and must collect all such errors when I log.

when it's not needed, you have to tack a != nil on the end

same as the universal if err := ...; err != nil {...}, it's the go way.

when it is needed, you still need to do whatever assertion/testing again to recover the desired error so at that point it makes more sense to write your own helper that does the tests and returns the correct kind of error

Yes, but the helper might as well use the error-returning version. Also Code generation makes helper writing trivial (if it wasn't already).

After discussing this internally, we've decided not to add errors.IsFunc or the equivalent at this time.
We believe that the cleanest and best API to expose to users is one based on sentinel errors. You should write errors.Is(err, os.ErrIsNotExist), not errors.IsFunc(err, os.IsNotExist). Adding IsFunc would encourage packages to use the latter. We will update the os package to permit the former.
We will not update os.IsNotExist to unwrap errors, for the reasons detailed in the original message above: Having this function behave differently in Go 1.12 and Go 1.13 is too hazardous.
Nothing, of course, prevents third-party packages from adding IsFunc. We can revisit the decision to add it in the future if it turns out to be broadly useful.


Develop

Hello @gwenchee! Thanks for submitting the PR.

In the file d3ploy/solver.py, following                are the PEP8 issues :

Line 78:80: E501 line too long (82 > 79 characters)

In the file d3ploy/supply_driven_deployment_inst.py, following                are the PEP8 issues :

Line 57:80: E501 line too long (84 > 79 characters)
Line 138:80: E501 line too long (86 > 79 characters)
Line 145:80: E501 line too long (94 > 79 characters)
Line 149:80: E501 line too long (85 > 79 characters)
Line 158:80: E501 line too long (83 > 79 characters)
Line 159:80: E501 line too long (80 > 79 characters)
Line 164:80: E501 line too long (83 > 79 characters)
Line 165:80: E501 line too long (80 > 79 characters)
Line 186:80: E501 line too long (108 > 79 characters)
Line 187:80: E501 line too long (86 > 79 characters)
Line 198:80: E501 line too long (83 > 79 characters)
Line 214:80: E501 line too long (90 > 79 characters)
Line 240:80: E501 line too long (86 > 79 characters)
Line 242:80: E501 line too long (84 > 79 characters)
Line 243:80: E501 line too long (81 > 79 characters)
Line 244:80: E501 line too long (82 > 79 characters)
Line 245:80: E501 line too long (86 > 79 characters)
Line 246:80: E501 line too long (81 > 79 characters)
Line 249:80: E501 line too long (86 > 79 characters)
Line 258:80: E501 line too long (82 > 79 characters)
Line 260:80: E501 line too long (82 > 79 characters)
Line 262:80: E501 line too long (82 > 79 characters)
Line 263:80: E501 line too long (82 > 79 characters)
Line 267:80: E501 line too long (82 > 79 characters)

In the file d3ploy/timeseries_inst.py, following                are the PEP8 issues :

Line 42:80: E501 line too long (85 > 79 characters)
Line 48:80: E501 line too long (86 > 79 characters)
Line 49:80: E501 line too long (82 > 79 characters)
Line 56:80: E501 line too long (91 > 79 characters)
Line 57:80: E501 line too long (89 > 79 characters)
Line 59:80: E501 line too long (84 > 79 characters)
Line 80:80: E501 line too long (80 > 79 characters)
Line 147:80: E501 line too long (86 > 79 characters)
Line 153:80: E501 line too long (87 > 79 characters)
Line 157:80: E501 line too long (85 > 79 characters)
Line 166:80: E501 line too long (83 > 79 characters)
Line 167:80: E501 line too long (80 > 79 characters)
Line 172:80: E501 line too long (83 > 79 characters)
Line 173:80: E501 line too long (80 > 79 characters)
Line 198:80: E501 line too long (108 > 79 characters)
Line 199:80: E501 line too long (84 > 79 characters)
Line 210:80: E501 line too long (83 > 79 characters)
Line 226:80: E501 line too long (88 > 79 characters)
Line 252:80: E501 line too long (82 > 79 characters)
Line 254:80: E501 line too long (80 > 79 characters)
Line 256:80: E501 line too long (82 > 79 characters)
Line 257:80: E501 line too long (82 > 79 characters)
Line 261:80: E501 line too long (82 > 79 characters)
Line 274:80: E501 line too long (86 > 79 characters)
Line 276:80: E501 line too long (84 > 79 characters)
Line 277:80: E501 line too long (83 > 79 characters)
Line 278:80: E501 line too long (86 > 79 characters)
Line 279:80: E501 line too long (86 > 79 characters)
Line 280:80: E501 line too long (83 > 79 characters)
Line 283:80: E501 line too long (86 > 79 characters)

In the file tests/integration_tests/constraint_test.py, following                are the PEP8 issues :

Line 2:11: W291 trailing whitespace
Line 34:80: E501 line too long (89 > 79 characters)
Line 40:80: E501 line too long (88 > 79 characters)

In the file tests/integration_tests/tech_pref_test.py, following                are the PEP8 issues :

Line 2:11: W291 trailing whitespace
Line 43:80: E501 line too long (93 > 79 characters)
Line 47:80: E501 line too long (83 > 79 characters)
Line 89:80: E501 line too long (82 > 79 characters)
Line 101:80: E501 line too long (81 > 79 characters)
Line 102:79: W291 trailing whitespace
Line 103:48: W291 trailing whitespace
Line 104:76: W291 trailing whitespace
Line 105:80: E501 line too long (80 > 79 characters)
Line 106:11: W291 trailing whitespace
Line 114:80: E501 line too long (94 > 79 characters)
Line 127:1: E302 expected 2 blank lines, found 1
Line 134:71: W291 trailing whitespace
Line 137:15: W291 trailing whitespace
Line 138:21: E231 missing whitespace after ','
Line 138:40: W291 trailing whitespace
Line 139:35: W291 trailing whitespace
Line 140:23: W291 trailing whitespace
Line 141:18: W291 trailing whitespace
Line 145:80: E501 line too long (81 > 79 characters)
Line 147:73: W291 trailing whitespace
Line 148:31: E225 missing whitespace around operator
Line 155:80: E501 line too long (92 > 79 characters)
Line 176:71: W291 trailing whitespace
Line 179:15: W291 trailing whitespace
Line 180:21: E231 missing whitespace after ','
Line 180:40: W291 trailing whitespace
Line 181:44: W291 trailing whitespace
Line 182:23: W291 trailing whitespace
Line 183:18: W291 trailing whitespace
Line 187:80: E501 line too long (81 > 79 characters)
Line 188:74: W291 trailing whitespace
Line 189:28: W291 trailing whitespace
Line 190:74: W291 trailing whitespace
Line 191:25: E225 missing whitespace around operator
Line 198:80: E501 line too long (95 > 79 characters)
Line 219:71: W291 trailing whitespace
Line 221:80: E501 line too long (87 > 79 characters)
Line 223:55: W291 trailing whitespace
Line 224:15: W291 trailing whitespace
Line 225:21: E231 missing whitespace after ','
Line 225:40: W291 trailing whitespace
Line 226:35: W291 trailing whitespace
Line 228:27: W291 trailing whitespace
Line 229:22: W291 trailing whitespace

There are no PEP8 issues in the file tests/unit_tests/deploy_solver_unit_tests.py !


No error notification when wrong Topic name given

Im using diffusion sdk 5.9.0 and able to connect and subscribe to topic is correct connection props and topic name are given.
Now, if i give incorrect topic name to session.subscribe function I don't get any error event on my session. Can you help how can i get the error event in above case?

You can't really subscribe to an incorrect topic name.
If you subscribe to a topic that doesn't exist, the subscription is treated as pending the creation of the topic. If the topic is created later, the session will be subscribed to it.
The backend can be notified of subscriptions to missing topics but it's only possible to be notified about all sessions not individual ones.
When subscribing it is possible to use selectors that select multiple topics not just one.
If the topic exists, then the stream should receive a notification that you have been subscribed to it. If it doesn't exist the notification won't happen.

So there is no way to show the caller that he has given a wrong topic name?
Get Outlook for Androidhttps://aka.ms/ghei36

From: Matt Champion<EMAIL_ADDRESS>Sent: Wednesday, September 18, 2019 10:02:52 PM
To: pushtechnology/diffusion-examples<EMAIL_ADDRESS>Cc: amit12cool<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [pushtechnology/diffusion-examples] No error notification when wrong Topic name given (#3)
You can't really subscribe to an incorrect topic name.
If you subscribe to a topic that doesn't exist, the subscription is treated as pending the creation of the topic. If the topic is created later, the session will be subscribed to it.
The backend can be notified of subscriptions to missing topicshttps://docs.pushtechnology.com/docs/6.3.2/manual/html/developerguide/client/topics/topiccontrol/missing_topic_notify.html but it's only possible to be notified about all sessions not individual ones.
When subscribing it is possible to use selectorshttps://docs.pushtechnology.com/docs/6.3.2/manual/html/designguide/data/publication/topic_selector_unified.html that select multiple topics not just one.
If the topic exists, then the stream should receive a notification that you have been subscribed to it. If it doesn't exist the notification won't happen.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/pushtechnology/diffusion-examples/issues/3?email_source=notifications&email_token=ABTB2JAUF7ASPYIYKE3MCALQKJJ3JA5CNFSM4IYA6BO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7AVMPI#issuecomment-532764221, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABTB2JFIGBCWLAUUAMI2UZLQKJJ3JANCNFSM4IYA6BOQ.

In more recent versions of the JS SDK or other language SDKs you can use something like the following to get close to what you want.
It's important to remember subscribing expresses interest in the paths described by the selector. That interest isn't affected by whether or not topics exist at those paths. If a session subscribes to a path without a topic, the session will receive notifications if a topic is ever created at that path.
/**
 * Attempt to subscribe to a topic and report an error if the topic does not
 * exist.
 *
 * Returns a promise.
 */
function subscribe_to_topic(session, path, datatype) {
  return new Promise((resolve, reject) => {
    var success = false;
    // Add a stream to receive the topic notification
    let stream = session.addStream('>' + path, datatype);
    stream.on({
        subscribe : function (path, specification) {
          // Record that a subscription notification is received
          success = true;
        }
    });

    // Subscribe to the path
    session.select('>' + path).then(() => {
      // If the topic existed, the stream would have received an event before
      // this callback is called
      if (success) {
        // The session has been subscribed to a topic that exists
        resolve();
      } else {
        // The topic did not exist at the time of subscription or
        // the session doesn't have permission to subscribe to it.
        // Unsubscribe from the path and reject the promise.
        // Streams may receive events for this path if the topic is
        // created between the subscription and unsubscription.
        session.unsubscribe('>' + path);
        reject(new Error('Topic does not exist'));
      }

      // Clean up stream
      stream.close();
    }, (e) => {
      // The subscription failed so reject the promise and remove the stream
      stream.close();
      reject(e);
    });
  });
}


Add Tabula, WebPlotDigitizer, and WaveDrom to documentation

Add these tools that are useful for interacting with and creating documentation.

Thanks!


Compile effectively on windows

As a developer
I wish to be able to develop on a windows platform and use GroundUpDB
So that I can use GroundUpDB for development on any platform, and any project

Compile on windows using cmake and msvc++
Windows build instructions verification
All tests passing on Windows

@battleguard Please check that this new CMake support for Windows. It's merged in to Stem. Tested with the latest MSVC community via visual studio code and cmake on windows 10 with the latest win 10 sdk.


The scaleoutbot does not work when dialog has an OAuthPrompt. Getting "OAuthPrompt.GetUserToken(): not supported by the current adapter"

Github issues for C# /JS / Java/ Python should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Sample information

Sample type: [\samples\ or \solutions]
Sample language: [dotnetcore or webapi or es6 or nodejs or typescript]
Sample name:

Describe the bug
Give a clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Give a clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
[bug]

Closing this as a duplicate of How to add Iconnectorclient to the botframeworkadapter. If it turns out that this is a bug, will reopen this issue.


basic columnar-based data structure

bit_mask.h: for bitmask
cypher_string_t.h: A special implementation of string type. The data structure is designed to store a small string or a pointer to a larger string. It consists of a prefix that stores the first few bytes (4 bytes) of the string, followed by a union that can either hold an 8-byte array called data (to store the remaining part of the string) or an 8-byte pointer called overflowPtr. If the total string length fits within the defined SHORT_STR_LENGTH (which is 12 bytes), it can be stored directly within the structure using the prefix and data. If the string is longer, the overflowPtr is used to point to an external memory location that stores the complete string.
column_vector.h: support int and string vector.

LGTM


OneWire support

Hi, I was wondering if you are planning to get a running sample for the OneWire support? I'm in the middle of trying to work out building a C# project for Raspberry Pi Zero, and instead of using Windows IoT Core (which is not supported on Raspberry Pi Zero), I'm looking into porting my project to run on Raspbian and mono runtime.
The sensors I'm currently trying to run from Raspberry Pi Zero are:
DS18B20 (temp sensor)
TSL2561 (Light sensor)
MCP3008 (to connect to a moisture sensor)
I have these running on the Raspberry Pi 3, but I would like to reduce the footprint of the device(s), and the Raspberry Pi Zero seems to be a good choice. I usually do all my work in Visual Studio building apps in C#.
With that said, I've been looking into your library and would be interested in using it if I could use it to support those devices I listed.
I understand it's a work in progress, and if you have any suggestions for me, or thoughts on if your library could support those devices currently, please let me know.

Hello, Yes I have some demos using OneWire. I will add them ASAP.
The library is under test but I'm using it in production with no problems. In few weeks, I will update nuget to production.

      Hello, Yes I have some demos using OneWire. I will add them ASAP.

The library is under test but I'm using it in production with no problems. In few weeks, I will update nuget to production.

Hey, thank you. Much appreciated. I'll check back from time to time to see what is in the repo and give it a try. Thank you again!

Onewire works now


fixed issue #22 : import StringIO ERROR

The StringIO and cStringIO modules are gone. Instead, import the io module and use io.StringIO or io.BytesIO for text and data respectively.

stringio-in-python3

the maintainer is not responding, all mege requests are on hold.


[FEATURE] - Unify the user table

Reference Issues
#106
Summary
The current user setup of a super class of users and "is a" relations app users and anon users should be unified to a single users table.
This mean mail and passwordhash should be nullable, and a new column "isAnonymous" should be added.
Unresolved questions
No response
Definition of Done
when a single user class can be made, and functionality still works in related to anonymous users joining a one of session.

Fixes and pushed to master from #106


Publish plugin to Plugin Portal

Currently pending manual approval

Currently pending manual approval

Available here https://plugins.gradle.org/plugin/com.google.secrets_gradle_plugin

Available here https://plugins.gradle.org/plugin/com.google.secrets_gradle_plugin


Flashing

Tried flashing with hex files v2.1,rev1, v2.1 and v2.0 to my cc2531 using cc debugger.
The driver after debugger notifies us that everything went ok, doesn't show up in device manager and seems to be missing. Installing the default cc2531 back works without troubles.
Anyone got a solution to that as to what might be wrong?

The only version that was possible to flash was 1.1


Improve Documentation (How to setup)

In general it's pretty well documented but the last steps seem to be missing to get it up and running.
Under "How to use" you describe the routes.js file setup.
const routes = module.exports = require('next-routes')()

routes
.add('about')
.add('blog', '/blog/:slug')
.add('user', '/user/:id', 'profile')
.add('/:noname/:lang(en|es)/:wow+', 'complex')
.add({name: 'beta', pattern: '/v3', page: 'v3'})

But you don't explain how and what to export.
In the section "On the server" there is routes imported/required but we didn't export anything in routes.js.
...
const routes = require('./routes')
...

If I do every step as explained and export routes from routes.js as:
// routes.js
...
module.exports = routes;

I still get an 404 after refresh and my node server (express) doesn't find my defined routes.
Also you explain in "On the client", Link should also be used from routes.js but we didn't export that either.
Maybe an example would help as well.

Ok, I got it:
// routes.js
const routes = module.exports = require('next-routes')();

routes
    .add('p', '/p/:slug', 'product')
    .add('c', '/c/:slug', 'content')
    .add('service', '/service/:slug')
    .add('legal', '/legal/:slug');

module.exports.Link = routes.Link;
module.exports.Router = routes.Router;
module.exports = routes;

and I had to add/remove
// server.js
...
- const handle = app.getRequestHandler();
+ const handler = routes.getRequestHandler(app);
...
- server.get('*', (req, res) => {
-     return handle(req, res)
- });

This line const routes = module.exports = require('next-routes')(); is is an export. You can see module.exports getting assigned right there.

I'm having issues with this too .. external links to the app throw error 404. Don't know what I'm doing wrong

@mherodev that's right!
@chrisehlee If your getting 404 please check if your starting the app by running node server.js (instead of next start)


[Feature]: Support TPM for easing tmux setup

Similar Issues

[X] Before filing, I have searched for similar issues.

Description
TPM is a plugin manager for tmux. Users install the plugin with something like
set -g @plugin 'mrjones2014/smart-splits.nvim' in the config file. And that's it.
This is simple, just need to create a shell script ending with .tmux in the root of the repo. It will be used to add configurations to tmux. See docs and similar plugin (which, btw works with this project without having the custom pane-is-vim variable setup)

Easy enough. Would you like to submit a PR?


Generate UPDATE statement

There is one feature I use in SQLWorkbench (another open source java based SQL Editor) that I use on occasion.
It is Generate UPDATE statement.
It works just like generate INSERT statement, with the exception that if the primary key of the table cannot be detected (we have a REALLY OLD database without primary keys on a lot of tables), then it pops up a dialog box to put a checkbox next to the columns you wish to consider the primary key, and then it leaves the generated statement in the clipboard and puts it into the active editor with the WHERE clause based on the primary key you selected, or what was auto-detected as the primary key in the table.
This is great for bring some production data to a test environment to try setup "test" scenarios.
It would be great if this feature were in DBeaver, especially now that I have switched to it ;-)

You can do this in DBeaver.

Define virtual unique key for a table (bottom toolbar->Define virtual key)
Change your table contents
Click on "Script" button - it will generate INSERT/DELETE/UPDATE queries which you can copy/paste.

Isn't this what you need?

Thanks for showing me the virtual key.
What I am trying to do is the following:

Highlight a specific row in the grid.
Right click and go to Generate SQL
I only see this:

These actions generate SQL for inserting/deleting of existing data.
Do you need a query which uses unique key and updates ALL table columns (besides key)?

Yes I need a query which uses a unique key that updates all the table columns (besides the key).
I basically highlight a row, or series of rows in SQL Workbench and it generates the UPDATE statements for me.
It helps to synchronize some data between TEST/DEV/PROD databases.

I see. This makes sense.

Thanks so much!!!! You are awesome!


Fixes 2320

Fixes #2320

Hmmm the last commit fixed the phpunit tests on my local machine, not sure why it's still failing in travis.

We'll want to adjust the migration file this goes into if it gets merged in. Let me know if/when I need to make any changes


[REFACTORING] Use standard configuration for webadmin integration tests

This is closer to runtime conditions thus prevents some bug.
Modify guice injections to associate value 0 with a random port.

Force pushed to squash commits...

Resolve conflicts please


RuntimeError: PyTorch was compiled without NumPy support

PythonProjects/pytorch-semseg-master/train.py
RUNDIR: runs/fcn8s_pascal/27405
Traceback (most recent call last):
File "/home/lxc/PythonProjects/pytorch-semseg-master/train.py", line 231, in
train(cfg, writer, logger)
File "/home/lxc/PythonProjects/pytorch-semseg-master/train.py", line 77, in train
model = get_model(cfg["model"], n_classes).to(device)
File "/home/lxc/PythonProjects/pytorch-semseg-master/ptsemseg/models/init.py", line 23, in get_model
model = model(n_classes=n_classes, **param_dict)
File "/home/lxc/PythonProjects/pytorch-semseg-master/ptsemseg/models/fcn.py", line 321, in init
get_upsampling_weight(m.in_channels, m.out_channels, m.kernel_size[0])
File "/home/lxc/PythonProjects/pytorch-semseg-master/ptsemseg/models/utils.py", line 814, in get_upsampling_weight
return torch.from_numpy(weight).float()
RuntimeError: PyTorch was compiled without NumPy support
Process finished with exit code 1

Reinstall anaconda and pytorch


File missing

Hello! I was running the hico dataset and following the data preparation instruction. But the code cannot run and it reports missing the /data/hico_20160224_det/json/hoi_list.json file. I cannot find this file from the oringinal tar.gz file of hico dataset. Looking forward for your help, thx.

I find how to extract these json files, from: https://github.com/BigRedT/no_frills_hoi_det

我找到如何从中提取这些json文件：https://github.com/BigRedT/no_frills_hoi_det

Hello, I also encountered the same problem, how to get this file ？


Fix README.md links to elm-compiler and core

Hey everyone, great to see the progress that's being made here! This is just a minor fix to README.md which previously returned a 404. I've verified that the links work now.

Thanks for the fix, @mk!


[Feature] Table button doesn't have an isDisabled/isVisible Property

Summary
There should be an option to disable the button in the table so that they can be controlled conditionally.
This is used by a user to disable the refund button if the order is already refunded.
Similarly, the isVisible property is also missing

@Nikhil-Nandagopal we're picking up #3250. Closing this.


Traceback error

18.11 11:23:01 [Bot] Traceback (most recent call last):
18.11 11:23:01 [Bot] File "/bot.py", line 4, in
18.11 11:23:01 [Bot] from classes.discordbot import DiscordBot
18.11 11:23:01 [Bot] File "/classes/discordbot.py", line 7, in
18.11 11:23:01 [Bot] from typing import List, Self
18.11 11:23:01 [Bot] ImportError: cannot import name 'Self' from 'typing' (/usr/lib/python3.9/typing.py)

Thanks for the report, the problem has been identified and I'm working on a fix that will be available soon.


This app store app might be copying off you

https://itunes.apple.com/us/app/apns-tool/id963558865?mt=12
Seems like it's a direct copy of this app, down to the UI.

I think this one is more of a copy, even took the previous name of this project. :)
Doesn't really mater tho, just aiming to make the best one.


Add support for 10.0.17017.1000

termsrv.zip

Hello,
what about 10.0.16299.19 (Fall Creators Update)? :)

@Szazi what about reading Readme and being on-topic?

@binarymaster  Hello, i know you're busy and can't always update all your projects, and i'd like to ask for a little tutorial or a batch file so we can obtain the need values of the rdpwrap.ini and add them when an update of W10 come to light
or from where you can obtain those values?
It will be very useful and less people keep asking the same thing on every windows update, also others can contribute to keep it updated just adding those values to the ini
also greetings for your great work and thanks a lot for all your time

@steev666 please see README, links section.

@binarymaster  i really tried but the latest versions are too different from what we can seem on the video, i guess im still too green to help
adding termsrv.dll from 10.0.17025.1000 x64
termsrv.zip

@steev666 an issue already exists for that version: https://github.com/stascorp/rdpwrap/issues/339
Also, each version should be in a separate issue, so posting that here is off-topic.

Provide x86 architecture DLL.


feat: add nodejs/node

nodejs/node: Node.js JavaScript runtime
$ aqua g -i nodejs/node

Setup
To execute tools installed by npm, you need to add the following to your PATH:
if node_path="$(dirname "$(aqua which node 2>/dev/null)" | grep aquaproj 2>/dev/null)"; then
  export PATH="$node_path:$PATH"
fi

[!NOTE]
I'd like to simplify the command like this:
eval "$(aqua env)" # `aqua env` outputs shell scripts to set environment variables like PATH

Reference

https://github.com/aquaproj/aqua-registry/pull/855
https://github.com/aquaproj/aqua-registry/pull/1437
https://github.com/aquaproj/aqua-registry/issues/1436
https://github.com/aquaproj/aqua/issues/2996

https://github.com/aquaproj/aqua-registry/releases/tag/v4.214.0-1

https://github.com/aquaproj/aqua-registry/releases/tag/v4.215.0-2


Reorganize readme

Codecov Report

Merging #91 (6bd567f) into main (4a83954) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #91   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           11        11
  Lines          333       333
  Branches        42        42
=========================================
  Hits           333       333

Continue to review full report at Codecov.

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


Support creating new client from existing client's connection

Is your feature request related to a problem? Please describe.
People need to create a client from an existing connection but just change the non-connection options
Describe the solution you'd like
Options:

Accept something a WorkflowService in client options which means all connection options are ignored (this same will have to be done for operator service if/when we get there)
Accept a grpc.ClientConn in client options which means all connection options are ignored. We'd also have to expose this connection from the client somehow (really hoping not to add a new interface method)
Make a Clone(existingClient Client, newOptions Options) (Client, error) call

There is a bit of a problem here. We use gRPC interceptors, which are only done at dial time, to put the namespace on the following all client methods (i.e. temporal[_long]_request[_latency|_failure][_attempt]). We set this as a fixed value.
I could technically extract this from most operation requests, but what do I do with the calls that don't have namespace? The only client interface call this would apply to is health check, but technically there are some direct-to-gRPC calls they can make. Today they are given a namespace tag in the metrics. For those rare calls, I can either:

Set the namespace tag on those calls to "<unknown>" or "" or something, but now I've just changed people's metrics
Leave the namespace as the original client's namespace, which means a health check call from the new client will have the old client's namespace

Thoughts?


[New game]: Hit the numbers game

🎮 Game Request
Game logic and basic description
A retro game where the player has to hit the numbers displayed on the screen for extra bonus in 60 seconds. The numbers keep on changing and are displayed at random
Point down the features
Game points
Mobile Apps
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

/assign

Hey @DiwareNamrata23 !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @DiwareNamrata23 ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


alternative rom repository

https://mdk.cab/

Hello @InitialXKO thanks I noticed this URL in your fork.
Cheers Sam

how to change the  rom repository? thanks

Manually download it in your browser and then import it
获取Outlook for Androidhttps://aka.ms/AAb9ysg

From: charliesxia @.>
Sent: Sunday, October 27, 2024 12:09:09 PM
To: sam-ludlow/mame-ao @.>
Cc: InitialXKO @.>; Mention @.>
Subject: Re: [sam-ludlow/mame-ao] alternative rom repository (Issue #58)
how to change the rom repository? thanks
―
Reply to this email directly, view it on GitHubhttps://github.com/sam-ludlow/mame-ao/issues/58#issuecomment-2439836365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AK43PGEHR2HB73HNI3Z5T6LZ5RROLAVCNFSM6AAAAABQULZCS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZZHAZTMMZWGU.
You are receiving this because you were mentioned.Message ID: @.***>


Test improvement

I went through all tests in this repo. We have unit test, integration test and end to end test. The tests running against each PR should be fast and stable. And test should be easy to make contribution. I have some thoughts on test:

Keep running unit test, it's fast and easy to make contribution. Enable code coverage?
end to end test can be removed because it takes long time to run and QE has a daily end to end test against latest main copr build.
Integration test should have all bootc commands and args included.
Now we have nushell and python for integration test. I like nushell a lot. But looks python is generic for test code.
TMT + Packit is good for Fedora and CentOS, but it does not support the other distros.

The reason I am opening this issue is to start a discussion about testing. Comments are welcome!

end to end test can be removed because it takes long time to run and QE has a daily end to end test against latest main copr build.

Yes, though I'd like to be able to opt-in to it for specific PRs; I think we can do that with a label trigger or a comment trigger.

Now we have nushell and python for integration test. I like nushell a lot. But looks python is generic for test code.

TMT + Packit is good for Fedora and CentOS, but it does not support the other distros.

Yes, though for the most part just building across other distros/OSes is trivial in containers in GHA; the harder part is reference base images and builds.


hungarian translation updateted

This package has improved a lot since I last was here. Congrats guys :-)

Thank you, it would not really reached this point without your help and the great contribution as well from the other heroes @FusionDesign and @fishmad :)

@balping  Is it possible to solve the merge conflict?

I dont really understand why is there a merge conflict, I think the easiest
way is if you just copy my two modified files to your own repo and then
make a commit. But if you'd like to, I can try making another pull request
2015. nov. 5. 9:32 ezt írta ("thekordy" notifications@github.com):

@balping https://github.com/balping Is it possible to solve the merge
conflict?
—
Reply to this email directly or view it on GitHub
https://github.com/thekordy/ticketit/pull/79#issuecomment-153987369.

Done :+1: