Traefik V2 (alpha8) : TLS options not applied ?

Do you want to request a feature or report a bug?
Bug
Did you try using a 1.7.x configuration for the version 2.0?

[ ] Yes
[x] No

What did you do?
I set up a simple whoami service and try to configure specific TLS Options to the associated router

I'm not sure this is a bug or if I'm missing something obvious, but I really tried to follow the documentation and it does not seems to work, so I'm filling this issue.
I can't open a topic on https://community.containo.us/ for now as my account is temporary on hold.

What did you expect to see?
I expect to see no errors and get my TLS Option properly applied to my router
What did you see instead?
I get unknown TLS options: mintls13@file on the whoami router.
I got this file provider log:
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Configuration received from provider file: {\"http\":{\"middlewares\":{\"redirect-to-https\":{\"redirectScheme\":{\"scheme\":\"https\"}}}},\"tcp\":{},\"tls\":{}}" providerName=file

It seems my TLS config for options and defaultcert are not acknowledged by traefik as the tls section is empty :
{
  "http": {
    "middlewares": {
      "redirect-to-https": {
        "redirectScheme": {
          "scheme": "https"
        }
      }
    }
  },
  "tcp": {},
  "tls": {}
}

Output of traefik version: (What version of Traefik are you using?)

Complete example with all files and config to reproduce available here
docker-compose
version: "3.3"

services:

  traefik:
    image: "traefik:v2.0.0-alpha8-alpine"
    command: "--configFile=/etc/traefik/config/static/traefik.toml"
    container_name: "traefik"
    ports:
      - "<IP_ADDRESS>:80:80"
      - "<IP_ADDRESS>:443:443"
      - "<IP_ADDRESS>:8080:8080"
    volumes:
      - "./config:/etc/traefik/config"
      - "./secrets/pki/clients:/etc/pki/clients:ro"
      - "./secrets/pki/ca/ca.pem:/etc/pki/ca/ca.pem:ro"
      - "/var/run/docker.sock:/var/run/docker.sock:ro"

  whoami:
    image: containous/whoami
    expose:
      - "80"
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.whoami.entrypoints=https"
      - "traefik.http.routers.whoami.tls=true"
      - "traefik.http.routers.whoami.rule=Host(`calvin.benefice.io`)"
      - "traefik.http.routers.whoami.tls.options=mintls13"

static config
[Global]
	CheckNewVersion = false
	SendAnonymousUsage = true

[Log]
  Level = "DEBUG"
  FilePath = ""
  Format = "common"

[API]
  Dashboard = true

[Providers]
  ProvidersThrottleDuration = 2

  [Providers.Docker]
    Watch = true
    ExposedByDefault = false
    endpoint = "unix:///var/run/docker.sock"
    SwarmMode = false

  [Providers.File]
    Watch = true
    Directory = "/etc/traefik/config/dynamic"

[entryPoints]

   [entryPoints.http]
      address = ":80"

   [entryPoints.https]
      address = ":443"

dynamic config
[tls]

  [[tls.certificates]]
    certFile = "/etc/pki/clients/client.pem"
    keyFile = "/etc/pki/clients/client-key.pem"
    stores = ["default"]

  [tls.stores]
    [tls.stores.default]
      [tls.stores.default.defaultCertificate]
        certFile = "/etc/pki/clients/client.cert"
        keyFile = "/etc/pki/clients/client.key"

  [tls.options]

    [tls.options.mintls13]
      minVersion = "VersionTLS13"

    [tls.options.mutualauth]
      [tls.options.mutualauth.clientAuth]
        caFiles = ["/etc/pki/ca/ca.cert"]
        clientAuthType = "RequireAndVerifyClientCert"

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)
traefik    | time="2019-07-17T10:01:10Z" level=info msg="Configuration loaded from file: /etc/traefik/config/static/traefik.toml"
traefik    | time="2019-07-17T10:01:10Z" level=info msg="Traefik version 2.0.0-alpha8 built on 2019-07-01T17:46:52Z"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Static configuration loaded {\"global\":{\"sendAnonymousUsage\":true},\"serversTransport\":{\"maxIdleConnsPerHost\":200},\"entryPoints\":{\"http\":{\"address\":\":80\",\"transport\":{\"lifeCycle\":{\"graceTimeOut\":10000000000},\"respondingTimeouts\":{\"idleTimeout\":180000000000}},\"forwardedHeaders\":{}},\"https\":{\"address\":\":443\",\"transport\":{\"lifeCycle\":{\"graceTimeOut\":10000000000},\"respondingTimeouts\":{\"idleTimeout\":180000000000}},\"forwardedHeaders\":{}},\"traefik\":{\"address\":\":8080\",\"transport\":{\"lifeCycle\":{\"graceTimeOut\":10000000000},\"respondingTimeouts\":{\"idleTimeout\":180000000000}},\"forwardedHeaders\":{}}},\"providers\":{\"providersThrottleDuration\":2000000000,\"docker\":{\"watch\":true,\"endpoint\":\"unix:///var/run/docker.sock\",\"defaultRule\":\"Host(`{{ normalize .Name }}`)\",\"swarmModeRefreshSeconds\":15000000000},\"file\":{\"directory\":\"/etc/traefik/config/dynamic\",\"watch\":true,\"traefikFile\":\"/etc/traefik/config/static/traefik.toml\"}},\"api\":{\"entryPoint\":\"traefik\",\"dashboard\":true},\"log\":{\"level\":\"DEBUG\",\"format\":\"common\"}}"
traefik    | time="2019-07-17T10:01:10Z" level=info msg="\nStats collection is enabled.\nMany thanks for contributing to Traefik's improvement by allowing us to receive anonymous information from your configuration.\nHelp us improve Traefik by leaving this feature on :)\nMore details on: https://docs.traefik.io/basics/#collected-data\n"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="No default certificate, generate one"
traefik    | time="2019-07-17T10:01:10Z" level=info msg="Starting provider aggregator.ProviderAggregator {}"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Start TCP Server" entryPointName=http
traefik    | time="2019-07-17T10:01:10Z" level=info msg="Starting provider *file.Provider {\"directory\":\"/etc/traefik/config/dynamic\",\"watch\":true,\"traefikFile\":\"/etc/traefik/config/static/traefik.toml\"}"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Start TCP Server" entryPointName=https
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Start TCP Server" entryPointName=traefik
traefik    | time="2019-07-17T10:01:10Z" level=info msg="Starting provider *docker.Provider {\"watch\":true,\"endpoint\":\"unix:///var/run/docker.sock\",\"defaultRule\":\"Host(`{{ normalize .Name }}`)\",\"swarmModeRefreshSeconds\":15000000000}"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Configuration received from provider file: {\"http\":{\"middlewares\":{\"redirect-to-https\":{\"redirectScheme\":{\"scheme\":\"https\"}}}},\"tcp\":{},\"tls\":{}}" providerName=file
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Adding certificate for domain(s) calvin.benefice.io"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="No default certificate, generate one"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Provider connection established with docker 18.09.2 (API 1.39)" providerName=docker
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Configuration received from provider docker: {\"http\":{\"routers\":{\"http-catchall\":{\"entryPoints\":[\"http\"],\"middlewares\":[\"redirect-to-https@file\"],\"service\":\"traefik_traefik\",\"rule\":\"hostregexp(`{host:[a-z-.]+}`)\"},\"whoami\":{\"entryPoints\":[\"https\"],\"service\":\"whoami_traefik\",\"rule\":\"Host(`calvin.benefice.io`)\",\"tls\":{\"options\":\"mintls13\"}}},\"services\":{\"traefik_traefik\":{\"loadBalancer\":{\"servers\":[{\"url\":\"http://<IP_ADDRESS>:80\"}],\"passHostHeader\":true}},\"whoami_traefik\":{\"loadBalancer\":{\"servers\":[{\"url\":\"http://<IP_ADDRESS>:80\"}],\"passHostHeader\":true}}}},\"tcp\":{}}" providerName=docker
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Adding certificate for domain(s) calvin.benefice.io"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="No default certificate, generate one"
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating middleware" routerName=http-catchall@docker serviceName=traefik_traefik entryPointName=http middlewareType=Pipelining middlewareName=pipelining
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating load-balancer" routerName=http-catchall@docker serviceName=traefik_traefik entryPointName=http
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating server 0 http://<IP_ADDRESS>:80" serverName=0 entryPointName=http routerName=http-catchall@docker serviceName=traefik_traefik
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Added outgoing tracing middleware traefik_traefik" entryPointName=http routerName=http-catchall@docker middlewareName=tracing middlewareType=TracingForwarder
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating middleware" middlewareName=redirect-to-https@file middlewareType=RedirectScheme entryPointName=http routerName=http-catchall@docker
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Setting up redirection to https " middlewareType=RedirectScheme entryPointName=http routerName=http-catchall@docker middlewareName=redirect-to-https@file
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Adding tracing to middleware" entryPointName=http routerName=http-catchall@docker middlewareName=redirect-to-https@file
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating middleware" entryPointName=http middlewareName=traefik-internal-recovery middlewareType=Recovery
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating middleware" serviceName=whoami_traefik middlewareName=pipelining middlewareType=Pipelining entryPointName=https routerName=whoami@docker
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating load-balancer" serviceName=whoami_traefik entryPointName=https routerName=whoami@docker
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating server 0 http://<IP_ADDRESS>:80" routerName=whoami@docker serviceName=whoami_traefik serverName=0 entryPointName=https
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Added outgoing tracing middleware whoami_traefik" entryPointName=https routerName=whoami@docker middlewareName=tracing middlewareType=TracingForwarder
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="Creating middleware" entryPointName=https middlewareName=traefik-internal-recovery middlewareType=Recovery
traefik    | time="2019-07-17T10:01:10Z" level=debug msg="unknown TLS options: mintls13@docker" entryPointName=https routerName=whoami@docker

Not 100% sure but: shouldn't the label of the whoamitcp container be
- "traefik.http.routers.whoami.tls.options.whoami-mintls13.minVersion=VersionTLS13"

?
I might be wrong, but the label should define a "TLS option" confgiuration structure, instead of referencing one from the global dynamic configuration right?
N.B. your account should have been unlocked in the Community forum. The Discourse bot locked it because less than 3s where measured between 2 messages/actions. Not sure why, sorry for the inconvenience.

Hi @dduportal, Thanks for the quick reply =)
If I refer to this section of the documentation Here, within the expendable block Configuring the TLS options I see :
[http.routers]
  [http.routers.Router-1]
    rule = "Host(`foo-domain`) && Path(`/foo-path/`)"
    service = "service-id"
    # will terminate the TLS request
    [http.routers.Router-1.tls]
      options = "foo"

[tls.options]
  [tls.options.foo]
    minVersion = "VersionTLS12"
    cipherSuites = [
      "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
      "TLS_RSA_WITH_AES_256_GCM_SHA384"
    ]

Where it seems you need to define an Option named foo that you refer to whith options = "foo" in the http config.
In any case I gave it a try using the label you provided but I get the following error :
time="2019-07-17T14:39:58Z" level=error msg="invalid node options: string" providerName=docker container=whoami_traefik-28e0ef210aba9f1df375c86a2550492bbc1f3a75bb36ff0d36ea1d4e5b11c51e

Hi @pbenefice , sorry for the bad comment: I was wrong :)
The label traefik.http.routers.whoami.tls.options=mintls13 is (almost) right.
It has to reference the tls.options structure.
But based on the last line of the traefik log you provided, it should be namespaced to the "file" provider, where the tls13 tls option is defied, as the labels are namespaced in the @docker provider.
Can you confirm that it works using traefik.http.routers.whoami.tls.options=mintls13@file ?

Hi again @dduportal,
My mistake I forgot the @file when opening this issue as I tried multiple things before opening it, but this is something I am aware of, and I have the same issue when using it : time="2019-07-17T15:25:55Z" level=debug msg="unknown TLS options: mintls13@file" entryPointName=https routerName=whoami@docker

I'll update my examples

I think the first problem is that the tls section of the configuration gathered from the file provider is empty in the logs :
level=debug msg="Configuration received from provider file: {\"http\":{},\"tcp\":{},\"tls\":{}}" providerName=file

I might be wrong but if i receive tls{} as config from the provider file, I won't be able to go further.
what do you think ?

Hi again @dduportal,
For what it's worth, it seems I have a similar issue with the tls.stores.default.defaultCertificate directive that does not seem to be applied either.
If you have the time please feel free to use this example that should expose the problem easily : https://github.com/pbenefice/wip_traefik_tls
I'll also open a topic on the community forum.
I'm pretty sure the problem come from the fact that I receive an empty config from the file provider, but again I might miss something.
In any case thanks for your time.

I propose to continue the discussion on Discourse:
https://community.containo.us/t/treafik-v2-alpha8-tls-configuration-options-default-cert-not-applied/921

ok with that, so I close this issue.

Thank you @dduportal, @ldez, I manage to fix my issue by changing the provider file configuration. I used filename instead of directory in the [Providers.File] section, and the problem disappeared.

For later readers (as the rest of the conversation took place in the Community forum):
thanks to @pbenefice , a bug in v2.0.0-alpha8 was undercovered and is fixed by #5118.
(Reference: https://community.containo.us/t/traefik-v2-alpha8-tls-configuration-options-default-cert-not-applied/921/7?u=dduportal)


Feature - Cached Tiles

This addresses #46 by caching to a temporary directory.

Coverage increased (+0.6%) to 91.513% when pulling e9f2fe827b8bf7369b12a22e2d5aa3802641f45b on szmoore:feature/cached-tiles into d7db0ef2d13a242182fbd872c62aa75028f11d9a on darribas:master.

Coverage increased (+0.6%) to 91.513% when pulling e9f2fe827b8bf7369b12a22e2d5aa3802641f45b on szmoore:feature/cached-tiles into d7db0ef2d13a242182fbd872c62aa75028f11d9a on darribas:master.

I believe this differs from #57 because it caches to files on disk rather than memory. For my usage the cache on disk is more useful, but I haven't explored if CacheControl can do this already.

Thank you very much for the PRs!!! A bit slow here... @jorisvandenbossche / @ljwolf how does this look to you?

The joblib based caching is merged, see https://github.com/darribas/contextily/issues/46#issuecomment-516580038 for some context.

I think this PR can be closed because with PR #85 it is possible to cache tiles using the following line:
import contextily
contextily.tile.memory.store_backend.location = 'my/cache/path'

@szmoore What do you think?

Closing as #106 takes this forward.


Improve onboarding flow for new merchants

@Taiteilija Feedback on the first version:

The "Test mode" button on the popup should enable the Test mode by checking the Test mode checkbox, submitting the form and refreshing the page
Move the Test mode toggle next to the Merchant keys setting and disable input for those incase Test mode is activated
Add some notification nearby telling to disable the test mode in order to input the keys
When test mode is active the on-boarding popup should not be displayed when entering the page
When test mode is active we should have general notification at the top of the page pointing out that Paytrail for WooCommerce is running on test mode. The Notification should also encourage registering to our service and have a link that will trigger the on-boarding popup. Something like "Notice: Paytrail for WooCommerce is currently in test mode. To enter production mode you need to submit your Merchant ID and Key."
We need to improve the UI of the registration form: let's move the input fields to two columns and add this text above the form: "To begin the Paytrail registration process, please review the following information:"

Was done in #139


Badly needs a property reference

I would love to be able to try this out and play around with it, but without a reference of what properties I can use and what they do, playing around with it would be limited to trying out css properties to see if they do anything. I see this page has been started, but it depressingly incomplete: http://gridstylesheets.org/guides/references/

In short, most numerical CSS values can be constrained.
In addition to top and left, GSS introduces bottom, right, center-x, and center-y.
Also, intrinsic-width and intrinsic-height exist and behave as documented here.
Many 2D properties have a way to reference both dimensions at once for convenience:

bottom-left (bottom, left)
bottom-right (bottom, right)
center (center-x, center-y)
intrinsic-size (intrinsic-width, intrinsic-height)
position (x, y)
size (width, height)
top-left (top, left)
top-right (top, right)

That's great info! Would you mind adding it somewhere in the docs?

I'll keep this issue open as a reminder to do that.


stage1 handling: new behavior proposal

Actually --stage1-hash and --stage1-path are mutually exclusive.
I propose to change this behavior to:

if there is no image with provided hash in store - unpack aci pointed by --stage1-path
if unpacked image have other hash than given as --stage1-hash - abort
do rest as usual

Reason for change of this behavior is to have a possibility to use same parameters in two situations, when stage1 is already unpacked, or when it should be unpacked for the first time.
At this moment k8s driver have a possibility to select desired stage1 image, but when --stage1-path is used - the same image is unpacked over and over on every command execution. Changing this to proposed way - should have (IMO) nice impact on speed, so probably would improve overall rkt usage comfort.
What do You think about this? This makes sense?

@jellonek The rktnetes uses --insecure-options=image,ondisk,  shouldn't that already enable rkt to use rendered images?

No, this only works for pod images.

RFC

It makes sense to me but I don't know enough how k8s uses images to say more. How does k8s know the hash of the image?

Yeah, wanted to ask the similar question. What would k8s driver pass to rkt for the first time? --stage1-hash=whoopdedoo-bogus-hash --stage1-path=/a/valid/path/to/image.aci?

Correct me if i'm wrong - stage1 image hash is based on it's content? If it's know (stable for release version) it could be saved in configuration of kubelet?

Correct me if i'm wrong - stage1 image hash is based on it's content? If it's know (stable for release version) it could be saved in configuration of kubelet?

Are you suggesting kubelet takes a flag --rkt-stage1-hash or something like that? If so, what if we want to run with another stage1? e.g. run fly-stage1?

I'm trying to find a reasonable way to keep possibility of specifying stage1 image and to reuse unpacked one if it's already on fs, or to unpack it for the first time.


[Killzone 2][BCES00081] The injection doesn't work on update 01.29

After updating the European version of Killzone 2 to update 01.29, the injection doesn't work anymore. Pressing the bound On/Off button locks the cursor in place, but there's no reaction to mouse movements of the ingame camera. Everything works properly in the non-updated game (version 01.01).
This is particularily important because the patch for removal of some effects and allowing the game to be played without enabling Write Color Buffers (and thus improving performance) is available for version 01.29 only.
I haven't tested the update 01.28 or other version of the game, though.

tested it and it is still not working, bummer

Fixed as of #49
Download new 0.0.3 release to test

It works, you are a gift to mankind. You made so many people very happy for reliving one of their favorite games on PC.


Logs and websockets

Add a good log styling and implement a web socket client with the minimal setup

Go formatting is off, easy fix tho 😀


Remove old-style grid widgets

These widget don't have any clients anymore. Consider using GridView instead.

@Hixie


Ralpmh time update

We should also keep a variation log on the project google drive somewhere, just to keep track of any changes (so we don't later have to root around the git logs).

cool, added here https://docs.google.com/spreadsheets/d/1b2y0-gHB8O7dHv_CnbilQso3_syee5ZNN8yzw1pI9zo/edit#gid=0


Will you share the checkpoint of your relighting diffusion model

Thanks for your nice work, we want to use your RDM as research propose, would you mind share the checkpoint for us?

Hi, thanks a lot for your interest in our work.
It is impossible for us to release the RDM at this time. The main reason is stated in the README: though we only fine-tune the diffusion model on Objaverse (a public dataset), the base diffusion model is trained on an in-house dataset, which prevents us from open-sourcing.
I apologize for the inconvenience.

Hi, thanks a lot for your interest in our work.
It is impossible for us to release the RDM at this time. The main reason is stated in the README: though we only fine-tune the diffusion model on Objaverse (a public dataset), the base diffusion model is trained on an in-house dataset, which prevents us from open-sourcing.
I apologize for the inconvenience.

thank you for your response


Module not found

It works in the previous version 4.1.11. After updating to 4.1.12, it returns
Compiled with problems:

ERROR in ./node_modules/youtube-sr/dist/mod.mjs 1:0-58

Module not found: Error: Can't resolve 'module' in 'C:\Users\arnok\OneDrive\Desktop\Bots item\React-JS\youtubedownload\node_modules\youtube-sr\dist'

Are you using esm?

Module is imported here https://github.com/DevAndromeda/youtube-sr/blob/0935cf008c787af84cb2be7331c4971f7d28c881/scripts/postbuild.js#L5

Are you using esm?

yes

es modules import seems to work fine on the latest version, is it still happening? @DMNight6
/* test.mjs */
import { YouTube } from "youtube-sr";

console.log((await YouTube.search("levitating"))[0].title);
// node test.mjs -> "Dua Lipa - Levitating Featuring DaBaby (Official Music Video)"

Fixed by using backend

now its invalid url (youtube itself)

invalid url?

invalid url?

yep
when I tried to getVideo using url

could you provide the url? @DMNight6

stale, re-open if needed


The terminal doesn't  changes to default terminal profile while debugging python and error appears while opening terminal using "ctrl + ~"  that  "& was unexpected at this time".

Environment data

VS Code version: 1.56.2
Extension version: 2021.5.842923320
Pylance Version: 2021.5.2
OS and version: Windows 10 Home
Python Version: 3.9.1
Type of virtual environment used:  python3 venv
Value of the python.languageServer setting: pylance

I am trying select command prompt as my default terminal for debugging

when I press F5 then it doesn't changes to command prompt

when I press ctrl + ~ 'It shows & was unexpected at this time'

Duplicate of #16175 . The underlying cause of #16175 is also responsible for this one.


Dismiss more than one feature

Description
I use tree-based navigation provided TCA. In some cases I need to dismiss to root feature. It works, but I see runtime warning about dismiss action that not handled because feature is nil.
I'm not sure that it's bug, but don't know how to remove this warning
Checklist

[ ] I have determined whether this bug is also reproducible in a vanilla SwiftUI project.
[X] If possible, I've reproduced the issue using the main branch of this package.
[X] This issue hasn't been addressed in an existing GitHub issue or discussion.

Expected behavior
You dismiss to root feature and not see runtime warning
Actual behavior
You dismiss to root feature and see runtime warning
Steps to reproduce
LongDismissExample.zip

You tap "Forward" button on the First screen and go to the Second
You tap "Forward" button on the Second screen and go to the Third
You tap "Back" button on the Third screen and return to the First
You see runtime warning

The Composable Architecture version information
1.10.1
Destination operating system
iOS 17.4
Xcode version information
15.3
Swift Compiler version information
swift-driver version: <IP_ADDRESS> Apple Swift version 5.10 (swiftlang-<IP_ADDRESS> clang-15<IP_ADDRESS>)

Thanks for the report! We'll be suppressing that warning in the next release, which should come later today.
I'll note that SwiftUI doesn't support nested navigation destinations like this very well, so you may want to consider stack navigation in the future, but if it works for you and the OSes you deploy to, at least you should be warning-free soon :smile:

Thank you too!
I will consider using stack navigation soon, thanks one more time


app-catalog: fix and updates cards styles

Description
This PR fixes a bug in the App-Menu plugin that caused singular cards to render squished. The issue affected the visual appearance and usability of the cards, especially when only one card was present.
Key Changes

Fixed Card Rendering:

Updated the rendering logic to ensure singular cards display correctly without being squished.
Improved the layout to make card sizes consistent regardless of the number of cards.

Improved Card Sizing:

Adjusted the size and spacing of cards to enhance the overall user experience.
Ensured that the layout remains visually appealing across various card counts and screen sizes.

Images
Before

After

Steps to Test

Navigate to the App-Menu plugin in the application.
Test the rendering of cards in the following scenarios:

Search for Headlamp and filter

Verify:

Singular cards display properly without being squished.
Card sizes are consistent and align correctly across different layouts.

last push fixes the resize for md view point to show double cards before moving to single cards when on sm

updated all the style tags to use sx, not noticing any differences on my end


Convert some REST values so they work in a query object

See https://github.com/BestBuy/api-playground/blob/master/src/hooks/index.js

i would rather traverse the whole object, as i did in my code in the related issue, because it is unlikely you only want to use it in the root where object.

I agree.

I think its best people use the traverse hook to normalize their values.


IE9 doesn't work

Tried to get it running with IE9, stops on setCallerURL...somehow the flash isn't initialized properly.

No similar issue reported so far, so assuming environment-specific issue. Closing.


fix(Card): add link prop to typings

We've merged #1359, but forgot to add prop to typings.

Codecov Report

Merging #1369 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1369   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files         140      140
  Lines        2345     2345
=======================================
  Hits         2339     2339
  Misses          6        6

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 76dfe9b...08e0716. Read the comment docs.

Released in<EMAIL_ADDRESS>


[CodeCompletion][Sema] Don't guess whether a solution will be applied to the AST based on solutions formed for code completion.

When solving for code completion, we do several things differently than when solving for regular type checking, such as ignoring missing arguments after the argument containing the code completion location, not favoring overloads with a number of params matching the number of arguments in a call, and so on. Because of this, we shouldn't assume multiple solutions being formed when solving for code completion means there won't be a single best solution formed when solving for regular type-checking, but were.
In the example below, when typeCheckExpression is called for the call to foo, typeCheckForCodeCompletion forms a solution for both overloads of bar because it doesn't do overload favoring, while regular type checking does and ignores the overload with a defaulted parameter. Because of this difference typeCheckForCodeCompletion incorrectly assumes regular type-checking won't apply any solution to the AST and won't call typeCheckExpression for the expressions within the closure body. Because of this, in an attempt to still give some useful completion results, it manually type checks in isolation the expression in the closure body that contains the completion expression in case that lets us gets us types for the completion expression or its base that we can use to form the completion results. It doesn't though because no type has been applied to v yet.
struct S {
    var someProp = true
}
func foo(_: (S)->()) {}
func bar(_: ()->()) {}
func bar(_: ()->(), _ defaulted: Int = 10) {}

foo { v in
  bar {
    if v.#^COMPLETE^# {}
  }
}

This PR works around this issue by not immediately falling back to solving the expression within the closure in isolation, and instead falling back to the regular type checking path. If there is no subsequent typeCheckExpression call for the body, there is already higher-level fallback logic that considers the expression in the closure in isolation. We will end up solving twice (once for code completion, and once for regular type-checking) in such fallback cases when we wouldn't have before, but will also now give correct results in cases like the above.
Resolves rdar://problem/72362275

@swift-ci please test


Adds ability to save simple name io. fully qualified

UnionType and AllImplementations (in cooperation with SaveClassName) use the fully-qualified class name of a class to determine the run-time type of a record. The fact that the fully-qualified name is used, makes it more difficult to refactor a project’s package structure, after its initial release to production.
In order to alleviate this problem, for projects that are in full control of the package structure of the entities they are storing and want to keep their options open, this change adds “simple” versions of SaveClassName, UnionTypesand AllImplementations (SaveSimpleName, SimpleUnionTypes and SimpleAllImplementations, respectively), that do the same except that they store and match on the classes’ simple names.

Considering that the last three (open) pull requests have failing tests (that I can’t reproduce locally) in the same area, I assume that these changes are not the cause of the failing tests.
How should I proceed?

lgtm

Rebased in #360


Created Feature Card 23 black

Here is the component I have built.
Here is a screenshot of that.
 Screenshot

Done


Request for a binary release

I would like to request a binary, standalone release, perhaps, like for pandoc itself, as a deb package.
Thanks in advance.

The pandoc deb installs both pandoc and pandoc-citeproc.
+++ Antony Lee [Nov 15 15 22:32 ]:

I would like to request a binary release, perhaps, like for pandoc
itself, as a deb package.
Thanks in advance.
—
Reply to this email directly or [1]view it on GitHub.
References

https://github.com/jgm/pandoc-citeproc/issues/193

My apologies, I got confused by the (Arch) Linux package I'm using.


is vala a gud lang

pls tell I want to write os and this is totally rerl aiphihahihiauhwruhorffrdcuhjn (I'm sorry ^^)

YOU MORON WRITE AN OS IN C OR C++, AND IF YOU HAVE BALLS WRITE IT IN 16 BIT X86 ASSEMBLER

but Vala compiles code down to blazingly fast, fully native binaries. You're also able to reuse existing C Code in your Vala programs as well as generate C Code from Vala.

go ahead implement an interrupt handler in vala

go ahead implement an interrupt handler in vala

I'll interrupt joe mama

okay let's stop idk if The Vala community on GitHub likes this :) lmao


coordinates good!

This change adds another viewcube that shows x,y,x coordinates

So the use case for removing command duplication is for example:
Start at 0,0,0
G90 X40
G91 Y-2
G90 X0
You can face a part by just going back in the history 3 times and it cycles along moving the step over.
I also found I was rarely going back into the history and editing at the beginnig of the command so I moved the curser to the end when selectionchanged is fired.
  Currently if you click send the last command stays in the editable window.

This change adds another viewcube that shows x,y,x coordinates

I will add this as an option in the Settings: App tab:

So the use case for removing command duplication...

Not sure I understand your use case. Perhaps better to limit duplication check to the last entered command rather than completely remove it?
                if (!string.IsNullOrEmpty(cmd) && (Commands.Count == 0 || Commands[0] != cmd))
                    Commands.Insert(0, cmd);

The rest saved me from coding it myself, was annoyed by the last command remaining when running tests on my lathe. Thanks!

Do you want me to make the above change to merge this or are you going to merge it some other way?
Also, do you have a prioritized list of things your are doing on this?  I'd like to help out more.

I have already made the changes to my master and I am going to merge in some other way that I have not yet figured out. This as my master repository is a local subversion repository - not git. And I am not going to switch to git as I have a lot of stuff in that repository I am not going to publish.

Also, do you have a prioritized list of things your are doing on this?

Not written down, however my top priority (for the sender) is probing. The camera UI needs attention, if I am going to do that I need to finish a camera mount for my spindle.
User defined interface would be nice but that has a low priority, surely not something I want to start working on during the summer months.
For myself I want to add parting and facing(?) wizards for the lathe - but that is not easy for you to work on? Or do you want to try to add spindle sync to the ESP32 driver and use that for your lathe?
The next MCU I will add spindle sync support for is the IMXRT1062 - a pity that I cannot use a debugger for that.
In your opinion what else needs attention?


Save users' followers into file example

I wanted to fix #505, I think it's really useful for large numbers of followers. I also added the "save users following into file" example. I'm not sure if the best way to do it, but it worked for me at least. :smile:

Codecov Report

Merging #550 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #550   +/-   ##
=======================================
  Coverage   38.49%   38.49%
=======================================
  Files          25       25
  Lines        2073     2073
=======================================
  Hits          798      798
  Misses       1275     1275

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 da3f9fd...a713cfe. Read the comment docs.

Yes looks good! I made a very small change though, using utils.file.

Great job, guys!
@ofou @basnijholt


Signals + subprocesses may lead to livelock

When you're profiling a view that uses subprocess.Popen(), it might livelock:

the clone() syscall (used to implement os.fork() under the hood) may take 2-3 milliseconds on my machine (as measured by strace -T while the flamegraph was off)
a SIGALRM arrives every 1 ms and interrupts the clone()
clone() returns -EINTR
the signal handler runs
clone() is then restarted
go to step 1

This is very clearly visible in strace output.  Externally this is visible as a Django process eating 100% CPU and sometimes not making any progress.
Sometimes the view would actually finish, after an extra 10-20 seconds of this processing, which shows in the flamegraph as a call stack terminating in subprocess.Popen._wait().
I don't know if this can be fixed.
Possible mitigations: don't use subprocess.Popen() from the main thread, use a lower sampling frequency for the SIGALRM timer.

Does raising the sampling frequency to say, 5, remove the issue?

I haven't actually tried that.
Background: I was trying to figure out why precisely django-pipeline caused an 800m delay in my template render, and I hacked the django-pipeline source to do the subprocess invocation in the main thread instead of using concurrent.futures.ThreadPoolExecutor.  That's when I stumbled upon this problem.  It's a classical race condition: sometimes clone() finishes before the next SIGALRM arrives, and so I was able to see the flame graph I was interested in after a few retries (that required me to kill and restart the livelocked django server).
This issue is not causing me pain, since I reverted the debugging change to django-pipeline once I was done investigating.  I only filed a bug because I thought the problem analysis might be useful to anyone else who happens to encounter this issue.
I expect raising the sampling interval to 5 ms would make this problem harder to hit, but not remove the underlying issue.

Apparently you can ask that signals not interrupt system calls with signal.siginterrupt(sig, False).
Source: https://news.ycombinator.com/item?id=9243855

Ah, cool thank you. Does it work for you?
Sorry about the lack of updates. It has been working for us and I've been really busy lately. I still have this on my TODO though :smile:

I haven't had a chance to try it out yet.
(Also, oops, I see I promised some smaller PRs doing something about the sampling inaccuracies I mentioned in #1, and I haven't delivered yet.  Been busy too :/  What's worse -- I completely forgot the ball was in my court! )


Simpler pure nixpkgs

Description of changes
Make it easier to use the pure version of nixpkgs by allowing the system argument. I'm happy that localSystem and crossSystem exist, but the common case for me is to pass the relevant system.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Maybe we should rename those inputs to hostPlatform and targetPlatform, if anything?

Ok, let me quickly unroll a few thoughts and see where we agree.

Having the same function signature for the pure and impure functions is a nice property. It makes it easier to swap one for the other.
Now the impure entrypoint is purely about injecting impure variables, no mixed concern.
Calling nixpkgs with { inherit system; } is the common case. Typing { localSystem = { inherit system; }; } is more complicated. That's what I meant by simplifying, making it easier for the user by optimizing for the common case.
The reality is that flakes will be around for a while now, and they solidify the position of the system tuple (sorry).

I just really care about the usability of the user in that scenario.
Another variation might be to allow localSystem and crossSystem to also take strings. And then either deprecate the system entirely, or clarify that system is localSystem and deprecate the latter.

I am have not opinion on the PR, but that system is meant to be legacy is at least on my opinion quite clearly stated out on the impure entrypoint comments.
https://github.com/NixOS/nixpkgs/blob/6337682f24aa554b0f7738a3a3f5ca6e2dfc1d34/pkgs/top-level/impure.nix#L14

If I am not mistaken, that was @Ericson2314's idea; he did a ton of work on the cross-compilation and his idea was that we would move to more advanced system declarations and deprecate the old system attribute. The problem is that most people don't use cross-compilation so all of this is just making their usage more complicated. Ideally, we can find a middle ground that works well for both cases.

Yes it was my idea. Cross or no cross, the system string is very rough and doesn't capture enough information to characterize the system.

The problem is that they are not going away. We have builtins.currentSystem and flakes, and they are conveniently short. So it's better to embrace and extend.

it's time to close some old PRs


Sending message right before closing websocket

I have an issue with letting the client know about disconnection purpose.
I wanted to use deadline timer to have a timeout on async_read operation. If the client is inactive for 30 seconds, we send him message with such info and THEN disconnect.
Part of my code:
boost::asio::yield_context yield
boost::beast::flat_buffer buffer;
boost::beast::websocket::stream<boost::beast::ssl_stream<boost::beast::tcp_stream>>* ws
boost::asio::deadline_timer t(ioc, boost::posix_time::seconds(session.timeout));
t.async_wait(boost::bind(&Connection::setInactivity, this, boost::asio::placeholders::error()));
(*ws).async_read(buffer, yield[ec]);
setInactivity method is just setting session.active to false.
then I perform :
boost::beast::multi_buffer resp;     boost::system::error_code ec;
`(*ws).text((*ws).got_text());
size_t n = buffer_copy(resp.prepare(response.size()), boost::asio::buffer(response));
resp.commit(n);

(*ws).async_write(resp.data(), yield[ec]);
if (ec)
{

    return showErrorMessage(ec, "method: async_write");
}
else
{
    PRINT_INFO("Request processed - sent response");
}`

It looked just fine, but when I called async_write, I got the following error:
Operation canceled
Is it even possible to send a message before disconnecting?
Note: I found it impossible with built-in timeout which disconnects automatically.

definitely don't use beast::tcp_stream's internal timeout with websocket.
As I read it, your t.async_wait(...) code won't execute until after the async_read has completed, because you are yielding the coroutine.
It might be a good idea if you can link a github repo containing a complete, small, self-contained program that demonstrates what you are trying to do. I can then offer suggestions on how to correct it.

I guess it will be hard to link a github repo as it is confidential.
I pasted the code in wrong order, sorry.
Firsty I start the timer, then I call async_read.
As far as I understand, I'm not "closing" the async_read, so I can't perform async_write.. but I don't know how to close/end/stop async_read.

Don't copy your company's code. Write a new, very small, program which demonstrates the principle of what you want to achieve.
This is a websocket read with a timeout, yes?

Start reading from readMessageToByte.
`void Connection::setInactivity(const boost::system::error_code& e)
{
if (e == boost::asio::error::operation_aborted)
{
// Timer was stopped due to an incoming message - it's fine
return;
}
else if (e)
{
PRINT_INFO("Timer failed - ", e.what());
}
else
{
PRINT_INFO("Disconnecting client due to timeout - was ", session.timeout);
session.active = false;
}
}
void Connection::sendResponse(std::vector<uint8_t> response, boost::asio::yield_context yield)
{
boost::beast::multi_buffer resp;
boost::system::error_code ec;
(*ws).text((*ws).got_text());
size_t n = buffer_copy(resp.prepare(response.size()), boost::asio::buffer(response));
resp.commit(n);

(*ws).async_write(resp.data(), yield[ec]);
if (ec)
{

    return showErrorMessage(ec);
}
else
{
    PRINT_INFO("Request processed - sent response");
}

}
std::vector<uint8_t> Connection::readMessageToByte(boost::asio::yield_context yield, boost::asio::io_context& ioc)
{
boost::beast::flat_buffer buffer;
std::vector<uint8_t> data;
boost::system::error_code ec;
session.active = true;
boost::asio::deadline_timer t(ioc, boost::posix_time::seconds(session.timeout));
t.async_wait(boost::bind(&Connection::setInactivity, this, boost::asio::placeholders::error()));

(*ws).async_read(buffer, yield[ec]);

if (!session.active)
{
    std::vector<uint8_t> messageBeforeDisconnect = {1,2,3,4}

    sendResponse(messageBeforeDisconnect, yield);
    return data; //empty
}
else if (ec == boost::beast::websocket::error::closed || ec)
{
    PRINT_INFO("Connection terminated - ", ec.message());
    return data; //empty
}

data.resize(buffer.data().size());
boost::asio::buffer_copy(boost::asio::buffer(data, data.size()), buffer.data(), buffer.data().size());

return data;

}`

Start reading from readMessageToByte.
`std::vector<uint8_t> Connection::readMessageToByte(boost::asio::yield_context yield, boost::asio::io_context& ioc)
{
boost::beast::flat_buffer buffer;
std::vector<uint8_t> data;
boost::system::error_code ec;
session.active = true;
boost::asio::deadline_timer t(ioc, boost::posix_time::seconds(session.timeout));
t.async_wait(boost::bind(&Connection::setInactivity, this, boost::asio::placeholders::error()));

(*ws).async_read(buffer, yield[ec]);

if (!session.active)
{
    std::vector<uint8_t> messageBeforeDisconnect = {1,2,3,4}

    sendResponse(messageBeforeDisconnect, yield);
    return data; //empty
}
else if (ec == boost::beast::websocket::error::closed || ec)
{
    PRINT_INFO("Connection terminated - ", ec.message());
    return data; //empty
}

data.resize(buffer.data().size());
boost::asio::buffer_copy(boost::asio::buffer(data, data.size()), buffer.data(), buffer.data().size());

return data;

}`
`void Connection::sendResponse(std::vector<uint8_t> response, boost::asio::yield_context yield)
{
boost::beast::multi_buffer resp;
boost::system::error_code ec;
(*ws).text((*ws).got_text());
size_t n = buffer_copy(resp.prepare(response.size()), boost::asio::buffer(response));
resp.commit(n);

(*ws).async_write(resp.data(), yield[ec]);
if (ec)
{

    return showErrorMessage(ec);
}
else
{
    PRINT_INFO("Request processed - sent response");
}

}`
void Connection::setInactivity(const boost::system::error_code& e) {     if (e == boost::asio::error::operation_aborted)     {         // Timer was stopped due to an incoming message - it's fine         return;     }     else if (e)     {         PRINT_INFO("Timer failed - ", e.what());     }     else     {         PRINT_INFO("Disconnecting client due to timeout - was ", session.timeout);         session.active = false;     } }

void Connection::setInactivity(const boost::system::error_code& e)
{
    if (e == boost::asio::error::operation_aborted)
    {
        // Timer was stopped due to an incoming message - it's fine
        return;
    }
    else if (e)
    {
        PRINT_INFO("Timer failed - ", e.what());
    }
    else
    {
        PRINT_INFO("Disconnecting client due to timeout - was ", session.timeout);
        session.active = false;
    }
}

void Connection::sendResponse(std::vector<uint8_t> response, boost::asio::yield_context yield)
{
    boost::beast::multi_buffer resp;
    boost::system::error_code ec;

    (*ws).text((*ws).got_text());
    size_t n = buffer_copy(resp.prepare(response.size()), boost::asio::buffer(response));
    resp.commit(n);

    (*ws).async_write(resp.data(), yield[ec]);
    if (ec)
    {

        return showErrorMessage(ec);
    }
    else
    {
        PRINT_INFO("Request processed - sent response");
    }
}

std::vector<uint8_t> Connection::readMessageToByte(boost::asio::yield_context yield, boost::asio::io_context& ioc)
{
    boost::beast::flat_buffer buffer;
    std::vector<uint8_t> data;
    boost::system::error_code ec;

    session.active = true;
    boost::asio::deadline_timer t(ioc, boost::posix_time::seconds(session.timeout));
    t.async_wait(boost::bind(&Connection::setInactivity, this, boost::asio::placeholders::error()));

    (*ws).async_read(buffer, yield[ec]);

    if (!session.active)
    {
        std::vector<uint8_t> messageBeforeDisconnect = {1,2,3,4}

        sendResponse(messageBeforeDisconnect, yield);
        return data; //empty
    }
    else if (ec == boost::beast::websocket::error::closed || ec)
    {
        PRINT_INFO("Connection terminated - ", ec.message());
        return data; //empty
    }

    data.resize(buffer.data().size());
    boost::asio::buffer_copy(boost::asio::buffer(data, data.size()), buffer.data(), buffer.data().size());

    return data;
}

The Websocket CLOSE message has a place to put both a numeric close code and a textual close reason, why don't you use that? Beast lets you set them both:
https://www.boost.org/doc/libs/1_80_0/libs/beast/doc/html/beast/ref/boost__beast__websocket__stream/async_close.html

I think there's a limit of 256 bytes

/// The type representing the reason string in a close frame.
using reason_string = static_string<123, char>;

/// The type representing the payload of ping and pong messages.
using ping_data = static_string<125, char>;

https://github.com/boostorg/beast/blob/6ada618c120b50a3a394e4427d99d14ae78b3066/include/boost/beast/websocket/rfc6455.hpp#L158

123, close enough :)

I think it will work out for me, I just don't know how to call async_close..
template<
    class CloseHandler = net::default_completion_token_t<[executor_type](https://www.boost.org/doc/libs/1_80_0/libs/beast/doc/html/beast/ref/boost__beast__websocket__stream/executor_type.html)>>
[DEDUCED](https://www.boost.org/doc/libs/1_80_0/doc/html/boost_asio/reference/asynchronous_operations.html#boost_asio.reference.asynchronous_operations.automatic_deduction_of_initiating_function_return_type)
async_close(
    close_reason const& cr,
    CloseHandler&& handler = net::default_completion_token_t< [executor_type](https://www.boost.org/doc/libs/1_80_0/libs/beast/doc/html/beast/ref/boost__beast__websocket__stream/executor_type.html) >{});
    ```

    what is CloseHandler?

Is that possible to get some help with that? @vinniefalco or @madmongo1

CloseHandler is an asio-style completion handler or completion token. Just like any other asio async operation.

Could you provide me any example of its usage? I can't find anything that would help me with completing that task.

Did you have a look at the documentation? https://www.boost.org/doc/libs/1_80_0/libs/beast/doc/html/beast/using_websocket/control_frames.html#beast.using_websocket.control_frames.close_frames

I've just read in the documentation that for the async operations we have to use a handler. As you mentioned above, CloseHandler may be good, but as @rdzienis said, we can't find any examples of its usage.
Should we implement it from the beginning just like any other handler or is there a way we could use an already written one?
We want to use the "ws.close(close_code::normal);" function that @vinniefalco recommended, but it is impossible without the handler.
Could you explain in more detail how exactly should we manage with the handlers in our situation @madmongo1?

I've just read in the documentation that for the async operations we have to use a handler. As you mentioned above, CloseHandler may be good, but as @rdzienis said, we can't find any examples of its usage. Should we implement it from the beginning just like any other handler or is there a way we could use an already written one?
We want to use the "ws.close(close_code::normal);" function that @vinniefalco recommended, but it is impossible without the handler. Could you explain in more detail how exactly should we manage with the handlers in our situation @madmongo1?

I recommend reading about Completion Tokens in the Asio documentation.


follow OSGi best practice

among these

Jackson should not be exported from the shared library.

This needs to be provided by the container
AEM Provides v2.9 w/ 6.5.0; the Manifest was configured to bind to this version up to, but not including, 3.0.

The use of Feign is an implementation detail of the embedded Jars. It should not be exported from the libraries and exposed to the OSGi context

see https://github.com/adobe/aio-lib-java/pull/58


services/authorization/mgmt/2020-10-01/authorization uses the apiversion "2015-07-01"

Bug Report

What happened?

https://github.com/Azure/azure-sdk-for-go/tree/main/services/authorization/mgmt/2020-10-01/authorization still uses the apiversion "2015-07-01".
https://github.com/Azure/azure-sdk-for-go/blob/main/services/authorization/mgmt/2020-10-01/authorization/roleassignments.go#L93

What did you expect or want to happen?

Since the directory is "2020-10-01/", I think, the api version should be "2020-10-01".
But it seems there's no api version "2020-10-01".
{"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.","details":[{"code":"NoRegisteredProviderFound","message":"No registered resource provider found for location 'eastus2' and API version '2020-10-01' for type 'roleAssignments'. The supported api-versions are '2014-04-01-preview, 2014-07-01-preview, 2014-10-01-preview, 2015-05-01-preview, 2015-06-01, 2015-07-01, 2016-07-01, 2017-05-01, 2017-09-01, 2017-10-01-preview, 2018-01-01-preview, 2018-07-01, 2018-09-01-preview, 2018-12-01-preview, 2019-04-01-preview, 2020-03-01-preview, 2020-04-01-preview, 2020-08-01-preview, 2020-10-01-preview, 2021-04-01-preview, 2022-01-01-preview'. The supported locations are ''."}]}

cc @Alancere @lirenhe

@bingosummer, the SDK is generated based on the readme config in https://github.com/Azure/azure-rest-api-specs/blob/main/specification/authorization/resource-manager/readme.md#tag-package-2020-10-01
Some of the Swagger are with earlier version. So could you try to use another version or preview version of this SDK?

      	{
      	  "error": {
      	    "code": "UnsupportedApiVersionForRoleDefinitionHasDataActions",
      	    "message": "Assignments to roles with DataActions and NotDataActions are not supported on API version '2015-07-01'. The minimum required API version for this operations is '2018-01-01-preview'."
      	  }
      	}

I hit the above error when assigning a role.

So could you try to use another version or preview version of this SDK?

Seems the azure-sdk-for-go has only two versions for authorization (2015-07-01 and 2020-01-01). Is there a way to use another version or perview version of this SDK?
I checked the azure cli debug log, and found it's using api version 2020-04-01-preview. azure-sdk-for-python has many versions for authorization. https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/authorization/azure-mgmt-authorization/azure/mgmt/authorization

switched to template deployment with the version 2020-04-01-preview as a workaround.

@bingosummer,  you could find the preview version here https://github.com/Azure/azure-sdk-for-go/tree/main/services/preview/authorization/mgmt/2020-04-01-preview/authorization


match api change: call --> callAsFunction

see also #165.
rest work with this pr, following are broken:
- Catch (needs love)
- CIFAR (tensorhandles)
- ResNet (tensorhandles)
- Transformer (_vjpGathering)

move to #166


Run Tiny iree on RISC-V 32-bit bare-matel

A list of things to check/change based on the works done in Tiny IREE based on RISCV 32-bit bare-metal toolchain/Emulator

[ ] Test elf loader (https://github.com/google/iree/tree/main/iree/hal/local/elf)
[ ] Test embedding library loader (https://github.com/google/iree/tree/main/iree/hal/local/loaders)
[ ] Test threading/synchronization
[ ] Build/Test a sync_driver with the embedding library loader (https://github.com/google/iree/blob/main/iree/hal/local/sync_driver.h), and hook the driver with simple_embedding_example
[ ] Plug stdout with the system logging mechanism.
[ ] Strip the unused dependencies

RE stdout: it'd be good to know what the system logging mechanism is that you are targeting; musl/newlib support fprintf(stderr and if we can live with that for now that's going to keep things really nice and simple. There's #2843 to fix it properly but if we can avoid that for now to get started at the cost of a few more KB in the binary that'd be good.

The RV toolchain uses newlib, In our emulation environment the stdout is routed to UART, so things like fprintf(stdout should work.

Awesome! We don't rely on that in the core anywhere but being able to use it in demos/tools will make it easier to share them!

elf loader (https://github.com/google/iree/tree/main/iree/hal/local/elf) seems to work, but the linker artifacts generated for rv32 creates a simple_mul_dispatch call that causes segfault. The header lookup in the linker artifact (iree_hal_executable_library_query) can look up the header from the module artifact correctly (iree_elf_cal_p_ip works).
Tracking the issue in https://github.com/google/iree/issues/6121

Tested iree/samples/simple_embedding/simple_embedding_embedded_sync with qemu-system-riscv32 with a bare-metal linker script and crt0. The .text section is 216348 B. Need to see if it can be stripped down more.
fprintf works fine connecting to the qemu-system-riscv32 console. Both stdout and stderr can be tunneled through.


Steam Overlay Disabled

Hi,
The patch is working perfectly fine. Kudos to Yamashi! However I'm facing a small problem. My steam overlay is disabled after installing the patch and I can't get the game to open it. I use the overlay to monitor my fps. Can you please help?
Thanks in advance :)

I don't have a solution, but if you open another game, and the show-up the steam overlay, you can go inside the settings and then manage the fps counter! (is not a real fix, however, you can still display the fps, and use it meanwhile waiting for a fix)

Alright guys I'm real sorry for the trouble. I fixed it myself. Turns out running the game in administrator mode doesn't allow the overlay to work. If anyone else is having this same issue please try disabling it.


Download events not ignored

Download events sent to the frontend should ignore those status:
 if (
                status == Status.ALREADY_EXISTS.value
                or status == Status.DOWNLOAD_COMPLETE.value
                or status.startswith("Pulling from")
                or status.startswith("Pulling fs layer")
            ):
                continue

Why? IMO if a user has half the layers, download should start at 50% not 0%.

Check the previous code and why we ignore some status.


ImageNet example shows contradictions

📚 Documentation
Hi ! :)
There is a puzzling fact for newcomer found at the dataloader definitions of the ImageNet example script here
There is a sampler that is manually defined.
The documentation mentions that With Lightning, you don’t need to do this because it takes care of adding the correct samplers when [needed.(source)
What is the correct stance for the sane Lightning beginner ?

Yes I'm also very confused by this, please explain, thanks!

@sebastienwood I tried to just remove the manual sampler, and the code seems to work fine. It's supposed to automatically replace the sampler anyway. Could you please verify?


Re-implement Client waiting for asynchronous Room onLeave

This was the previous behaviour sometime last year - an asynchronous onLeave in the Server-side Room would mean the Client waits for it to complete before firing the onLeave event. However, the Client is now automatically disconnected from the Room when calling onLeave, not waiting for the Server to finish the asynchronous onLeave call.
This means that persisting data between two rooms joined one-after-the-other doesn't work very well, if at all.
Given the onLeave Event is emitted client-side when the room connection is dropped, it should be as simple as not disconnecting the Client before onLeave has finished.

This should be refactored not to close the WebSocket connection immediately: https://github.com/gamestdio/colyseus/blob/3f9d8d3415c0c0a5740865d6f090a2230b665312/src/Room.ts#L437-L438

Hey @oyed, just released<EMAIL_ADDRESS>with a fix for this.
As the connection now keeps open while async onLeave() is running, I'm now ignoring all messages the client might still be sending to the server, to avoid potential exceptions in your room handler.

@endel Thanks, you're a legend!


Homogeneize logging system

Make it so both model types can run tensorboard evals.
This should be good to go, but will need to wait for an update in huggingface_hub before merging, as the lib stops the job if ŧensorboard is installed when it's not needed (see Slack for discussions), and cc @Wauplin :)
Closes #118

Opened https://github.com/huggingface/huggingface_hub/pull/2205 for the huggingface_hub part :)

Thanks :) In which huggingface_hub release will this be included?

0.23.x
Not sure when it'll be though (not before ~10 days I think, given last release was recent and not much has been done since then).

A possible solution if you want a quick fix is to install from source. Not the best if the lib' is used "in prod".

We'll wait for your release then! :)

Understandable!

@Wauplin is your release coming soon? :)

Not at short term actually (with ~10 days). I haven't pushed much changes to huggingface_hub since this fix.

If it were possible to push a patch for this it would be great, but else we'll leave it hanging - it's a part of the code we're not usually touching a lot so it won't be a hassle to merge in the future.

I'd prefer not to do a patch release for that as other "import-related" stuff has been fixed as well in huggingface_hub and cherry-picking commits would be hazardous (and taking from main would not be a patch release).
Another solution is to rely on the main branch for 2 weeks and I can take care of pinning again the version once huggingface_hub 0.23 is out.

Nope we'll wait - it's better for us to only rely on releases to avoid unexpected silent failures - but thanks :)

hey @Wauplin ! any news on the state of the release ? :)

Sorry sorry, forgot to let you know before going on holidays :see_no_evil: Huggingface_hub 0.23 has been shipped 3 weeks ago :grimacing: https://github.com/huggingface/huggingface_hub/releases/tag/v0.23.0

@NathanHB tested it and it should be good and mergeable when you've got the time :)


TransformerLens Dependency, Hidden States, and Hooks

There is some chatter regarding this library's over-reliant dependence on TransformerLens. (See https://github.com/FailSpy/abliterator/issues/10#issuecomment-2156118931)
I agree that it would be best to move away from TransformerLens (TL). One suggestion has been to use the technique from https://github.com/Sumandora/remove-refusals-with-transformers, which uses the "hidden_states" parameter offered from the Model HuggingFace transformer library.
Using hidden_states might be a good quick fix. It is mostly compatible across many models and presumably works for these purposes.
However, there are some quirks that deserve awareness.
(Personally, it feels slightly "hacky" and limiting for future work, but I may be suffering "purism".) It also removes the ability to interact with the resid_mid between the attention and mlp in each block.
It seems there are slight discrepancies between the resid_pre and resid_post subcache tensor values in TL and the hidden_states in HF. It is a tiny difference, but seems to grow over layers. And then the hidden_state[-1] or  last_hidden_state is completely different from TL's last layer's resid_post. I have not been able to determine why.
If this is problematic method would be to roll-our-own hooks into the residual streams. I had started this prior to finding this library. This would be most direct (allow us to use the resid_mid too), but would probably require re-implementing the multi-model configurations found in TransformerLens.
I hereby open this up for discussion!

Yeah, you can set output_attentions=True and I thought it might be possible to calculate resid_mid via looking at the previous hidden_state, but didn't look much deeper and the docs aren't really all that clear exactly if the output_attentions are before or after the o_proj.weight tensor is applied...

It seems there are slight discrepancies between the resid_pre and resid_post subcache tensor values in TL and the hidden_states in HF. It is a tiny difference, but seems to grow over layers. And then the hidden_state[-1] or last_hidden_state is completely different from TL's last layer's resid_post. I have not been able to determine why.

One thing to double check is that the layer induces are lining up: hidden_states in HF returns 1 more set of hidden states than there are layers and the 1st of these is the hidden state from before the first layer. IIRC, the code in abliterator was off by one and there was a comment in the code about "nan in the first layer" which was actually caused by this.
Regarding the second point:

When passing output_hidden_states=True you may expect the outputs.hidden_states[-1] to match outputs.last_hidden_states exactly. However, this is not always the case. Some models apply normalization or subsequent process to the last hidden state when it’s returned.

See: https://huggingface.co/docs/transformers/en/main_classes/output

It seems there are slight discrepancies between the resid_pre and resid_post subcache tensor values in TL and the hidden_states in HF. It is a tiny difference, but seems to grow over layers. And then the hidden_state[-1] or last_hidden_state is completely different from TL's last layer's resid_post. I have not been able to determine why.

Another problem that many people seem to overlook is that my code actually generates one token and then grabs the attentions.  Also floating-point operations are not commutative, so if HF Transformers does operations different to TransformerLens, then there are errors, which increase with every layer. My code is not supposed to be feature-complete or anything, as you said. I just wanted to have support for more models, I hope my POC will make that a reality soon... or arguably already made it one.

The full paper has been released
And an expanded codebase has been published here
In that, they actually use PyTorch hooks, and have actually a very nice little util class specifically for hooking into models.


Upgrade GH Actions

説明 / Description
非推奨になった GitHub Action を最新版へアップグレードする。
チェックリスト / Checklist

MUST

[x] npm test passed
[x] npm run lint was applied without warnings
[x] console.log not included (except script file)

RECOMMENDED (it depends on what you change)

[ ] unit test added/updated

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.57%. Comparing base (02a62b5) to head (2dd1222).
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main       #8   +/-   ##
=======================================
  Coverage   94.57%   94.57%
=======================================
  Files          18       18
  Lines        6457     6457
  Branches     1257     1257
=======================================
  Hits         6107     6107
  Misses        350      350

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


Determine latency for visuals

We need at least a rough estimate on how long it takes Unity to draw the environment to screen (monitor or headset) as well as a latency for the sensor data to propagate to Unity/screen.

@oliverlee is this still relevant?

Yes.
Time for motion to be sampled, fed into Kalman filter + dynamics simulation, and a completed transmission from microcontroller to desktop should be < 1 ms from previous testing with a blocking usbTransmit() call in the simulation loop. Here we don't explicitly take into account the 'sampling time' of the encoder as we are using a timer in encoder mode, and pose messages aren't sent at 1 kHz, but I think a 1 ms upper bound for all the microcontroller stuff is reasonable.
Now we need to estimate the time from being read in Unity to photon output. This should be less than 13 ms as we consistently display 75 FPS, otherwise we would be dropping frames.
Looks like there are some tools to use to test out motion-to-photon latency:
https://www.reddit.com/r/oculus/comments/43p3a6/does_anybody_know_the_motiontophoton_latency_of/
https://forums.oculus.com/developer/discussion/43597/whats-your-motion-to-photon-latency
https://www.reddit.com/r/oculus/comments/55avya/high_motiontophoton_latency_how_to_find_the_cause/

Also it looks like we should just buy CV1 to reach 90 FPS.

Using the following commits:
1ac3acf154fb4a79309a687d3840f06c67babf7b
https://gitlab.com/bikelab/phobos-visualizer/commit/4c315acc6d99940e6e612ee1f0f77ca1739562b8
I observe an app motion-to-photon latency of ~ 23 ms.
Log file here: https://docs.google.com/spreadsheets/d/1be0ZcxpZIkWNshU5prqRswj9LfAd-1It74HtP4rDpAc/edit?usp=sharing
So roughly 24 ms total latency.


Use LocalminimumTouchTarGetenForcement to cause crash

Describe the bug
Android: Use LocalminimumTouchTarGetenForcement to cause crash
iOS: no problem
Jetpack Compose: no problem
CompositionLocalProvider(LocalMinimumTouchTargetEnforcement provides  false) {
    Checkbox(
        checked = selected,
        onCheckedChange = { onSelectedChange() }, modifier = Modifier
            .background(Color.Gray)
    )
}

use device: HONOR(DUK-AL20)-9.0 / emulator-13.0
Affected platforms
Select one of the platforms below:

Android

If the bug is Android-only, report it in the Jetpack Compose tracker
Versions

Kotlin version*: 1.8.20
Compose Multiplatform version*: 1.5.0-dev1080
OS version(s)* (required for Desktop and iOS issues): MacOS 13.4.1
OS architecture (x86 or arm64): arm64
JDK (for desktop issues): 17.0.7

I have copy&pasted your code and it does not crash on my side with 1.5.0-dev1080 on Android.
BTW, does it crash with CMP 1.4.1 on your side?
Can you provide the whole reproducer?

Jetpack Compose: no problem

When you see that Jetpack Compose does not have an issue but Compose Multiplatform has on Android, please check version of Jetpack Compose and compare it with Compose Multiplatform redirection version to Jetpack Compose (https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.4.1). Compose Multiplatform is just Jetpack Compose on Android, so the most probably the versions do not match.

I have copy&pasted your code and it does not crash on my side with 1.5.0-dev1080 on Android. BTW, does it crash with CMP 1.4.1 on your side? Can you provide the whole reproducer?

Jetpack Compose: no problem

When you see that Jetpack Compose does not have an issue but Compose Multiplatform has on Android, please check version of Jetpack Compose and compare it with Compose Multiplatform redirection version to Jetpack Compose (https://github.com/JetBrains/compose-multiplatform/releases/tag/v1.4.1). Compose Multiplatform is just Jetpack Compose on Android, so the most probably the versions do not match.

@pjBooms Thank you for your reply. You are right. I have introduced an incompatible version in the Android branch

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


completion of constants includes value

I think this is a bingo bug, but feel free to close if it isn't.
Using neovim with:

autozimu/LanguageClient-neovim (branch: next)
ncm2/ncm2
fatih/vim-go

When completing a constant e.g. typing pkg.Fo where there exists const pkg.Foo = "bar" will complete with pkg.Foo = "bar" instead of just pkg.Foo.
This seems related to #15

@joshuarubin
--> request #51: textDocument/completion: {"textDocument":{"uri":"file:///home/saibing/git/go/source/hello/math.go"},"position":{"line":15,"character":7},"context":{"triggerKind":2,"triggerCharacter":"."}}
<-- result #51: textDocument/completion: {"isIncomplete":false,"items":[{"label":"Foo = \"bar\"","kind":21,"detail":"string","sortText":"00000","insertText":"Foo","insertTextFormat":2,"textEdit":{"range":{"start":{"line":15,"character":7},"end":{"line":15,"character":7}},"newText":"Foo"}}]}

bingo's return is ok:
"label": "Foo = \"bar\""
"insertText" = "Foo"
"newText" = "Foo"

coc.nvim, vsocde works well.
Maybe you can try coc.nvim.
I think it better than autozimu/LanguageClient-neovim or ncm2/ncm2.


AP-5465 Replace old secrets references

What
Link to story
Replace references to old secrets with the new secret.
Secrets updated:

googleDataStudioUrl
legalFrameworkApiHost
legalFrameworkApiJsHost

NB: This will be tested before merging (UAT), after merging (on Staging) and before and after deployment to production as it affects all environments and will affect the proceedings page.
Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
The standards in the Git Workflow document on Confluence should be followed
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

Code change looks fine, but the secret values in production are pointing at staging!
I think it was just a copy/paste error but it should be updated before merging!

Oh yes, good spot 🤦♀  thank you @colinbruce , have now updated!


Add a simple action to run the tests suite

Modify the CI workflow so it tests the action
The action does not use the Makefile since that felt quite awkward

Bit of self-review:

The action does not use Makefile: this is annoying in the sense that we now have two separate ways of installing and executing the suite
I did this because input arguments and Makefiles don't feel like a great combo. Currently we only have  --entrypoint but there will be more
that said, the action still looks clean and I suppose the Makefile can remain a development aid. I think this is acceptable

This was quite quick to whip up: I'm happy to try different ideas if you have any @AdamKorcz, @DavidKorczynski  but I think this should work. I'll document some further plans in #35

I think not invoking the Makefile here is fine. I don't expect the way we run the test suite to change often, so it shouldn't be a lot of maintenance.


Naughton/popover

Alaska Airlines Pull Request
Fixes: https://github.com/AlaskaAirlines/auro/issues/22 and https://github.com/AlaskaAirlines/auro/issues/157
Summary:
Implements auro-popover.
Pending work:

[x] Finalize tests for placement validation
[x] add drop shadow to arrow
[x] fix karma issue with the process global not existing

Type of change:

[x] New capability

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Issue with tests pending for the event-driven cases:
In the demo, this event is dispatched correctly and the popover fires:

In Karma, this event seems to not dispatch correctly - the same query selector can't be used.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Python Cleanup cores in case of multiple instances configured

If multiple Hyperion instances are configured, the Python clean-up during ~PythonInit fails as subinterpreters were not cleaned-up properly.
...
[hyperiond HYPERION] <INFO> Hyperion instance 'First LED Hardware instance' has been stopped
[hyperiond LedDeviceWrapper] <INFO> LedDevice 'file' closed
[hyperiond HYPERION] <INFO> Hyperion instance 'Test Instance' has been stopped
[hyperiond LedDeviceWrapper] <INFO> LedDevice 'file' closed
[hyperiond V4L2:auto] <DEBUG> <GrabberWrapper.cpp:36:~GrabberWrapper()> Close grabber: V4L2:auto
[hyperiond DAEMON] <DEBUG> <PythonInit.cpp:33:~PythonInit()> Cleaning up Python interpreter
Fatal Python error: PyInterpreterState_Delete: remaining subinterpreters

Aborted (core dumped)

Tested on Ubuntu 19.10, Python 3.7.5

This should also happen with one instance, when the EffectEngine does not run a proper shutdown (or Hyperion destructure won't wait) (?)

Wie ist der stand? Lassen?

@tpmodding Still an open issue

@Lord-Grey Maybe this is resolved with latest Effect leak fix ?


Does not detect typescript is installed and will not install

On my Mac I have typescript 1.8.2 installed.  I verified it with
charizard:~ stevel$ tsc --version
Version 1.8.2

however, if I try to install tslint, I get
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.

UPDATE
I also tried installing tslint@next, but that also fails:
npm WARN EPEERINVALID<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >=1.8.0-dev || >=1.9.0-dev but none was installed.

Hi @smlombardi, please see #815 which is the same issue as this. We haven't ben able to figure out yet why NPM gives that warning, however things should still work correctly as long as they're both installed despite the ominous warning.


Chore: Action - Setup dependabot & fast forward merge

Description
Enable two actions

Dependabot
Fast Forward

/fast-forward


Support passing arguments to async main

Adds a new static main function to AsyncParsableCommand to allow users to manually pass in arguments. The new functions behaves identically to the version found in ParsableCommand (see: https://github.com/apple/swift-argument-parser/blob/main/Sources/ArgumentParser/Parsable Types/ParsableCommand.swift#L126). This functionality is useful for manually building an argument list, e.g. when building a busybox~like binary.
Checklist

[ ] I've added at least one test that validates that my change is working, if appropriate
[X] I've followed the code style of the rest of the project
[X] I've read the Contribution Guidelines
[X] I've updated the documentation if necessary

Thanks, @Austinpayne! This is a great addition — when I saw it I thought, "don't we have that already?"
Would you mind adding a test that verifies that this will parse and run an async command correctly? Thank you!

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test


syslog router preprocessor: crash

What are the steps to reproduce this issue?

unknown

What happens?
crash
What were you expecting to happen?
not crash
Any logs, error output, etc?
goroutine 41 [running]:
github.com/gravwell/syslogparser.DetectRFC({0xc00035aab0?, 0xc00049c420?, 0x20?})
    github.com/gravwell/syslogparser@v0.0.0-20230331221307-ab77654a9657/syslogparser.go:36 +0x97
github.com/gravwell/gravwell/v3/ingest/processors.crackData({0xc00035aab0, 0x8, 0x8})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:129 +0x3a
github.com/gravwell/gravwell/v3/ingest/processors.(*SyslogRouter).Process(0xc00051e3c0, {0xc000068470, 0x1, 0xdf5200?})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:108 +0xac
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).processItems(0xc00032ac60, {0xc000068470?, 0x8?, 0x8?})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:425 +0x8a
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).ProcessContext(0xc00032ac60, 0xc0001ba1c0, {0x1127738, 0xc00037c460})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:376 +0xe5
main.rfc5424ConnHandlerTCP({0x112c408?, 0xc0003ee530}, {{0xc000319840, 0xa}, 0xc, 0x7, 0x0, 0x1, 0x0, {0x0, ...}, ...})
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/rfc5424Handlers.go:122 +0xa6d
created by main.acceptor in goroutine 65
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/simple.go:187 +0x759

Any other comments?
happened a few times
goroutine 6 [running]:
github.com/gravwell/syslogparser.DetectRFC({0xc00032be68?, 0xc000744960?, 0x20?})
    github.com/gravwell/syslogparser@v0.0.0-20230331221307-ab77654a9657/syslogparser.go:36 +0x97
github.com/gravwell/gravwell/v3/ingest/processors.crackData({0xc00032be68, 0x4, 0x8})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:129 +0x3a
github.com/gravwell/gravwell/v3/ingest/processors.(*SyslogRouter).Process(0xc00046e600, {0xc000120750, 0x1, 0xdf5200?})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:108 +0xac
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).processItems(0xc000493410, {0xc000120750?, 0x8?, 0x8?})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:425 +0x8a
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).ProcessContext(0xc000493410, 0xc0004dff10, {0x1127738, 0xc00009a320})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:376 +0xe5
main.rfc5424ConnHandlerTCP({0x112c408?, 0xc0001207d0}, {{0xc00033b7e0, 0xa}, 0xc, 0x7, 0x0, 0x1, 0x0, {0x0, ...}, ...})
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/rfc5424Handlers.go:122 +0xa6d
created by main.acceptor in goroutine 48
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/simple.go:187 +0x759

goroutine 73 [running]:
github.com/gravwell/syslogparser.DetectRFC({0xc000319b90?, 0xc000505760?, 0x20?})
    github.com/gravwell/syslogparser@v0.0.0-20230331221307-ab77654a9657/syslogparser.go:36 +0x97
github.com/gravwell/gravwell/v3/ingest/processors.crackData({0xc000319b90, 0x7, 0x8})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:129 +0x3a
github.com/gravwell/gravwell/v3/ingest/processors.(*SyslogRouter).Process(0xc0006300c0, {0xc000b82190, 0x1, 0xdf5200?})
    github.com/gravwell/gravwell/v3/ingest/processors/syslogrouter.go:108 +0xac
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).processItems(0xc00032a2d0, {0xc000b82190?, 0x8?, 0x8?})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:425 +0x8a
github.com/gravwell/gravwell/v3/ingest/processors.(*ProcessorSet).ProcessContext(0xc00032a2d0, 0xc0006e8230, {0x1127738, 0xc0003f42d0})
    github.com/gravwell/gravwell/v3/ingest/processors/processors.go:376 +0xe5
main.rfc5424ConnHandlerTCP({0x112c408?, 0xc000b82088}, {{0xc000319840, 0xa}, 0xc, 0x7, 0x0, 0x1, 0x0, {0x0, ...}, ...})
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/rfc5424Handlers.go:122 +0xa6d
created by main.acceptor in goroutine 84
    github.com/gravwell/gravwell/v3/ingesters/SimpleRelay/simple.go:187 +0x759

What versions of software are you using?
5.5.0

There just isn't a bounds check there at all:
https://github.com/gravwell/syslogparser/blob/1b31d9cb1c977cd056ec07b066807080fdead4f2/syslogparser.go#L36

There just isn't a bounds check there at all:
https://github.com/gravwell/syslogparser/blob/1b31d9cb1c977cd056ec07b066807080fdead4f2/syslogparser.go#L36

well that's just comically bad.

i'll put in something to guard us and then get a PR fired upstream

5.6.0-beta2 LGTM


Rewrite TimeSeriesImputerTransform to work without per-segment wrapper

Before submitting (must do checklist)

[x] Did you read the contribution guide?
[x] Did you update the docs? We use Numpy format for all the methods and classes.
[x] Did you write any new necessary tests?
[x] Did you update the CHANGELOG?

Proposed Changes
Look #1287.
Closing issues
Closes #1287.

Codecov Report

Merging #1293 (e6de921) into master (3b0027f) will increase coverage by 0.02%.
The diff coverage is 98.76%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master    #1293      +/-   ##
==========================================
+ Coverage   88.08%   88.11%   +0.02%
==========================================
  Files         187      187
  Lines       10886    10905      +19
==========================================
+ Hits         9589     9609      +20
+ Misses       1297     1296       -1

Impacted Files
Coverage Δ

etna/transforms/missing_values/imputation.py
98.98% <98.73%> (+1.62%)
:arrow_up:

etna/transforms/utils.py
90.90% <100.00%> (ø)

... and 4 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fps.js

看来是积分

Sorry, we only accept pull requests in English.

sorry,I don't know how to use github . just.....
------------------ 原始邮件 ------------------
发件人: "Francois<EMAIL_ADDRESS>发送时间: 2019年6月5日(星期三) 下午2:38
收件人<EMAIL_ADDRESS>抄送: "冰"1350396534<EMAIL_ADDRESS>主题: Re: [marmelab/gremlins.js] fps.js (#130)
Closed #130.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Cold-storage signing fails

I can load a transaction successfully (into an off-line wallet) but when trying to sign the transaction, the wallet throws an error message-box saying only "value". It does not sign the transaction. Any way of getting the off-line signing to work again?

you're using QR codes?

No, just Tools->Load Transaction->From Text.

and this is on 2.9.3?

Yes, I specifically upgraded first to 2.9.3 hoping that the problem would go away by itself, but yeah, it didn't. ;-)

I cannot reproduce the problem.  Its not a 2fa or anything weird, just a standard wallet?  Is it electrum seed or bip39? Can you try the verbose version and see if there is any useful console error msg, thx

It is an electrum seed. In my impression, it tries to access the network, which is not possible, because it is disconnected from the network:
$ cat tx.txt | ./electron-cash signtransaction -w ~/.electron-cash/wallets/cold  -
Password:
Traceback (most recent call last):
  File "./electron-cash", line 419, in <module>
    result = server.run_cmdline(config_options)
  File "/home/vm/Electron Cash-2.9.3/packages/jsonrpclib/jsonrpc.py", line 288, in __call__
    return self.__send(self.__name, args)
  File "/home/vm/Electron Cash-2.9.3/packages/jsonrpclib/jsonrpc.py", line 238, in _request
    check_for_errors(response)
  File "/home/vm/Electron Cash-2.9.3/packages/jsonrpclib/jsonrpc.py", line 567, in check_for_errors
    raise ProtocolError((code, message))
jsonrpclib.jsonrpc.ProtocolError: (-32603, u'Server error:   File "/home/vm/Electron Cash-2.9.3/lib/transaction.py", line 727, in serialize_preimage | KeyError: \'value\'')

In the GUI, it sends up a dialog box with the KeyError (="value") in jsonrpc.ProtocolError. In Electrum, in the same circumstances, it does not try to access the network. There is no need to access the network for the signtransaction command, is there?

it doesnt need to access network.  weird that your error message save cmdline as youre not running it command line. i'll try to dig a bit . on my end works fine

I had this exact issue.
Basically the QR code option doesn't work like it does in Electrum.
So I opened the unsigned file and just copied the hash and imported it to the cold computer and it tries to connect to the server because it needs the input values.
You need to copy the entire unsigned.tx file for it to work. Just copying the hash "0100000....." won't work.
Trying QR codes gives this error
type object 'QApplication' has no attribute 'primaryScreen'
This is with Ubuntu with qrencode dep installed.

@eriksank can you try with 3.0 ?

@fyookball It works like a charm now! Super! Thanks!


api: updated with latest swagger, including get ports by id

Adds only the changes from the latest equinix-metal.swagger.json, focused on changes in support of the hybrid-bonded port configurations.

FindPortByID added (GET /ports/{id})
/ports/{id}/assign now returns added Port property disbond_operation_supported: bool

Signed-off-by: Marques Johansson<EMAIL_ADDRESS>

@displague thanks for the PR. I see you updated the swagger api json. Will running gen.sh rewrite the api json? If yes, updating equinix-metal.swagger.json is pointless, isn't it? Maybe we could have 2 scripts - download_and_gen.sh and gen.sh. The latter one would use the swagger json from the repo without downloading it.

@displague thanks for the PR. I see you updated the swagger api json. Will running gen.sh rewrite the api json? If yes, updating equinix-metal.swagger.json is pointless, isn't it? Maybe we could have 2 scripts - download_and_gen.sh and gen.sh. The latter one would use the swagger json from the repo without downloading it.

I disabled the download and patch to generate a smaller diff for the 0.26 PR and then updated the spec to cherry-pick these port related changes.

I disabled the download and patch to generate a smaller diff for the 0.26 PR and then updated the spec to cherry-pick these port related changes.

It does seem helpful to split the download and patch functionality from the generator. Maybe we make these two Makefile tasks.

It does seem helpful to split the download and patch functionality from the generator. Maybe we make these two Makefile tasks.

@displague when I run the examples from code checked out from this PR, it didn't compile because of some iisue in the ports code. I had to run the swagger generating, and with the commit I pushed, the examples run.
bafe047 looks good? If yes, I merge.

@displague when I run the examples from code checked out from this PR, it didn't compile because of some iisue in the ports code. I had to run the swagger generating, and with the commit I pushed, the examples run.
bafe047 looks good? If yes, I merge.

@t0mk feel free to merge.
What I notice is that when you run the swagger command, we get these empty var () blocks. I suspect we are running different versions of go-swagger, which is what #9 tried to address 🙁 .

@t0mk feel free to merge.
What I notice is that when you run the swagger command, we get these empty var () blocks. I suspect we are running different versions of go-swagger, which is what #9 tried to address 🙁 .

@displague you're right, sorry. I rebased this on current main (where there's swagger-gen from docker) and verified that make gen didn't change the sources, and the examples run. I retracted my last commit and I'm merging.

@displague you're right, sorry. I rebased this on current main (where there's swagger-gen from docker) and verified that make gen didn't change the sources, and the examples run.


4632 rename commencement_date to trainee_start_date in the database and in register

Context
We've changed the name of 'commencement_date' to 'trainee_start_date' in the exports and reports from Register. We need to rename it in the database and code as well, so it's less confusing for us. Its a looooot of changes.
Changes proposed in this pull request
Guidance to review
I did a global find and replace of 'commencement_date with trainee_start_date.
Check the site still runs, the test suite still passes so i think its all good.
Important business

[ ] Does this PR introduce any PII fields that need to be overwritten or deleted in db/scripts/sanitise.sql?
[ ] Does this PR change the database schema? If so, have you updated the config/analytics.yml file and considered whether you need to send 'import_entity' events?

NB: Please notify the #twd_data_insights team and ask for a review if new fields are being added to analytics.yml

 [S] Rename 'commencement_date' as 'trainee_start_date' in the database and in Register


Small set of fixes done while making our first builds using a clean environment based on jethro

Merged - Thanks
Side wonder how many doxygen culprits we'll face: Have it installed on
my build host...

On Mon, Nov 9, 2015 at 8:42 PM, schnitzeltony<EMAIL_ADDRESS>wrote:

Side wonder how many doxygen culprits we'll face: Have it installed on
my build host...

We will figure out; soon we will include it in our autobuilder and the more
we use it, more fixes we will provide.
--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1<PHONE_NUMBER>


Support for function operations

Is there interest in having support for function operations added to this library? For example renaming, creating, deleting, etc, or is the sql helper good enough here?

What is the right way to create triggers? Using pgm.sql?

Yes, unfortunately that is the only way right now.
I will try to look on proper function this week.