Only connect to D-Bus interface for rauc on HassOS

This stops Hass.io from connecting to the D-Bus interface for rauc, which causes a warning in the logs for non-HassOS users. While cosmetic, it throws off a lot of new users.
This PR checks if the underlying system is actually HassOS, before continuing connecting.
If the host is HassOS, the behavior is unchanged and it will still throw the warning when the connection fails.
Implementation decision reasoning: I've passed in coresys, which might be overkill, however, it does match the general pattern in the codebase. Another option is passing in the D-Bus hostname instance directly (since it actually only depends on that).
Fixes #560

We should filter GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown on gdbus and trow an ie. ServiceUnknown exception. On rauc interface, we can catch this and show information or nothing

I do not agree on that, if there is an issue with the service on HassOS (whatever the reason), the ServiceUnkown should trigger the current behavior and should not be filtered.

That is addressed if we print a message later after we catch the ServiceUnkown on rauc

Addressed before


How to print tensor within GradientTape scope in TF2?

How to print tensor within GradientTape scope in TF2? i.e.
with tf.GradientTape() as tape:
    ...
    print(x)

Currently it gives me output like this:

Tensor("Identity_1:0", shape=(), dtype=float32)

This is very needed for debugging. Shouldn't the concept of computational graph already be discarded in TF2, such that it should work very much like PyTorch? Why is it still behaving like TF1 in GradientTape?

@yxchng try tf.print() insted of print

@NLP-ZY Great. Thanks!


Silent printing using IP address

Hello
I know the plugin can do IP address printing in iOS. Can it do the same for Android and Electron (windows)??

How you do it can you please tell ?


Add Lithuanian language

Adding basic translations for Lithuanian language. These could do with some improvements, but do not have enough time at the moment.

Awesome thanks. I'll release them in the next push!

This is now published in<EMAIL_ADDRESS>we'll make this the default in the next release of vue-formulate core. Thanks!


Plugin binaries

Hi there! I was unsuccessful with building AE_HapTools from sources (dx11 project reference seems to be missing, etc).
Could you provide a plugin binary along with an example patch in the downloads section please?
Seems like it'll take just a second and save quite a lot time for people like me

There's a test build in the builds folder at https://www.dropbox.com/sh/7sbvrhkfotsb1nu/AACiZo3n8-Mr1MPlXx1Cy2a8a?dl=0 - Tested on 34.2, 35.
The Hap plugin relies on an upstream change to FeralTic - vux has accepted a PR so I imagine this will make its way into a release of vvvv-dx11 at some point, but for now you'll need to replace your vvvv-dx11 pack with the one in the Dropbox link above. Usual caveats about backing up your vvvv directory, etc.
I'll probably upload something to contributions tomorrow for the wider vvvv community to have a  look at.

I got a red node for HapAVITexture (vvvv-HapTreats.dll is missing), while the DX11 nodes work ok.
Tested on vvvv_50beta35_x64

hmmm, works for us. Possibly a Dropbox sync thing - please try extracting
haptreats_1_1.zip (in the builds folder) to your packs dir.
On Thu, Jan 19, 2017 at 12:05 PM, Lev<EMAIL_ADDRESS>wrote:

I got a red node for HapAVITexture (vvvv-HapTreats.dll is missing), while
the DX11 nodes work ok.
Tested on vvvv_50beta35_x64
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/artistsandengineers/AE_HapTools/issues/1#issuecomment-273759998,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyZeFmlao4vYhJ_UovrP_Ppy-Ti43vgks5rT1GLgaJpZM4LmKRE
.

No such file!

https://www.dropbox.com/s/m7iin63hwbqw899/haptreats_1_1.zip?dl=0
On Thu, Jan 19, 2017 at 8:13 PM, Lev<EMAIL_ADDRESS>wrote:

No such file!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/artistsandengineers/AE_HapTools/issues/1#issuecomment-273885599,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAyZeB6LA3ytwjISUeW0fhnHJVqwfeYNks5rT8PtgaJpZM4LmKRE
.

Hey, I got it working! Your last response was super fast!

I saw that you've solved the issue with AVI parsing, any chance to update the binaries up to that commit?

https://www.dropbox.com/s/rolt0buoe043h0j/haptreats_1_2.zip?dl=0

Cool! It works!

Excellent - I have some suggestions by @Tebjan to implement over the weekend (inc. some performance enhancements) and then I'll probably try to shove a build into Contributions...

this DX11 build works the HAP player. https://github.com/mrvux/dx11-vvvv/releases/tag/0.9.62-alpha


How to configure accounts

Hi there
Simply put, I want to configure
leafnodes {
    port: 12345
}

accounts: {
  AUAREANKEY: {
    users: [
      {
        user: UAREANKEY
      }
    ]
  }
}
authorization: {
  users: [
    {
      nkey: UAREANKEY
    }
  ]
}
no_auth_user: UAREANKEY

I searched a bit in the code, I guess there's no "no_auth_user" and "accounts" possible with the operator ? Is there another way to inject that ? Or should I try to nuke the nats-server secret to replace it with a homemade one ?

I can't comment on the operator side of things, but this is not a valid configuration and will be rejected in the up-coming release. Having the same user in authorization{} and accounts{} will return an error saying that the user has to be unique. When using accounts{}, you should not have any user defined in authorization{} (you can fully configure users' permissions directly in the definition of the user in the accounts{} block).

There does not seem to be a way to define accounts and leafnodes that way in the operator right now. Closest that you can do is to include an auth secret but this would only work with the authorization block it seems: https://github.com/nats-io/nats-operator/blob/eef5976979e500a8077724220abc5ea8c934d9db/example/example-nats-cluster-authfile.yaml#L23-L34
I would try to migrate from the operator to a helm charts based one using the extraRoutes functionality to mesh the two clusters: https://github.com/nats-io/nats-operator/blob/71318679585df15a9b734586798f759d636e2ee0/README.md#connecting-operated-nats-clusters-to-external-nats-clusters

We're migrating out of this kubernetes cluster, so I don't want to spend a couple of days more trying to hop on another helm provisioned cluster, tried that quickly without success. Injecting the parameter with a init container is perfectly fine for me. I'll try that

Conclusion, we postponed enabling auth to after migrating out of the operator due to the above issue. Having a "wildcard" for additional configuration would be really handy.


Previous version support

Hi, I would like to ask if it was possible to put the ability to enter from previous versions?
I have server 1.18 and I wish players could join 1.8!
I have seen that there is a possibility to do this with ViaVersion and ViaBackWards etc. in the proxy, but use these plugins in the proxy it is quite heavy and not recommended and I would like to avoid!
Is it possible to have it?

This is a heavily requested feature and it might come in the future. There is not ETA atm tho.


Usage with UIKit

Hi there,
I'd love to use your lib in my current project. Is there any way to use it with UIKit as well?
thank you for your amazing work!
zwirne

Hello @zwirne, thank you for your kind words, but I'd suggest you use a UIKit native solution for UIKit project, like this one https://github.com/huri000/SwiftEntryKit. If you still prefer using this library please search for something like https://blog.logrocket.com/how-add-swiftui-uikit-project/. Have a nice day


fix: terraform plan FGR3-2215

typo 😒

Your orb has been published to the CircleCI Orb Registry.
You can view your published orb on the CircleCI Orb Registry at the following link:
https://circleci.com/developer/orbs/orb/figure/node-ecs?version=3.0.4


Read ENV VARs in helm chart configuration

Hello,
First and foremost, thanks for the module, it's really helpful.
We're using a HelmRelease resource to deploy the kafka-lag-exporter.
When connecting to a Kafka cluster, we'd like to be able to not put our credentials in clear in the fields like
ssl.truststore.password
That's why we'd like to use ENV vars, loaded through secrets (or secret file if that's possible? ) in the following manner :
values:
    clusters:
      - name: "kafka-dev"
        consumerProperties:
          security.protocol: SSL
          ssl.truststore.location: "/config/ca.jks"
          ssl.truststore.password: ${DEV_SSL_TRUSTSTORE_PASSWORD}
          ssl.keystore.type: "PKCS12"
          ssl.keystore.location: "/config/kafka-dev.p12"
          ssl.keystore.password: ${DEV_SSL_KEYSTORE_PASSWORD}
        adminClientProperties:
          security.protocol: SSL
          ssl.truststore.location: "/config/ca.jks"
          ssl.truststore.password: ${DEV_SSL_TRUSTSTORE_PASSWORD}
          ssl.keystore.type: "PKCS12"
          ssl.keystore.location: "/config/kafka-dev.p12"
          ssl.keystore.password: ${DEV_SSL_KEYSTORE_PASSWORD}

Unfortunately, the config file seems to be unable to read these ENV vars.
After a bit of research, this might be due to
https://github.com/lightbend/kafka-lag-exporter/blob/master/charts/kafka-lag-exporter/templates/030-ConfigMap.yaml#L62
Do you think there is / will be  another way to use ENV vars ?

Env vars can be used in Lightbend config (the config file format used by Kafka Lag Exporter). We would need to update the chart to create a Secret and load the keyvalues as a env vars.  Or maybe we could just make the whole ConfigMap a Secret instead.  WDYT?

On the issue at hand, it was resolved (or, workaround-ed) by just deleting the  added quotes around the generated configMap value :
ssl.keystore.password = ${?SSL_CLEAR_KEYSTORE_PASSWORD}  works, but
"ssl.keystore.password = ${?SSL_CLEAR_KEYSTORE_PASSWORD}"  doesn't.
The issue really seems to be tied to this line
https://github.com/lightbend/kafka-lag-exporter/blob/master/charts/kafka-lag-exporter/templates/030-ConfigMap.yaml#L62
Is it possible to simply not add quote in this part of your code, and expect users to quote when using strings ?
That would solve the issue, as editing a configmap post generation is not really the "way".

Same issue here, to use environment variables we must not use quotes (see https://github.com/lightbend/config) and currently the helm chart enforces them. That means we can only use a copy of the helm chart. Is there any need to have quotes at all?

Quick Update on the issue . This might deserve a separate issue on its own.
While the main issue remains ( quotes that i don't really understand why they're necessary),
we've now opted to go for loading our secrets through a secret manager (vault), which loads them in a/multiple files.
The part that's missing now is how to load these secrets in our configuration.

Option 1 would be : In the values configuration, allow reading a file to get a value, something like

ssl.truststore.password: $_file{/vault/secrets/truststore_password}
( where truststore_password contains the wanted info )

Option 2 :  allow adding an entrypoint / args /command in the values configuration, so we can source the file, as such

extraArgs:
            ['sh', '-c', 'source /vault/secrets/config && <entrypoint script>']

(where config contains a list  of  export k=v  env vars )
I've tried using the initContainers
initContainers:
    ## Init containers to be added to the pod.
      - name: source-init
        image: busybox:latest
        command: ['sh', '-c', 'source /vault/secrets/lag-exporter']

Unfortunately this add the env vars to the init container, not the main one, and as such doesn't work

Is there any need to have quotes at all?

Some values (like URL's, hostnames with ports, etc.) need to be quoted in Lightbend config or it can result in a parser error. If quoted values in the helm chart config end up as quoted values in the lightbend config then we could disable the automatic quoting that occurs in the chart, though it may break some user's config when they upgrade.

The part that's missing now is how to load these secrets in our configuration.

We could add configuration to the helm chart to mount arbitrary volumes into the container. If you're already doing something like this maybe you could open a PR for the helm chart?

Hi,
Is the issue regarding reading secrets from AWS secret manager resolved?
We are also having trouble resolving secrets for secured clusters and we don't want to put passwords in clear. Our passwords are stored in AWS secret manager and we are looking for a way for accessing these passwords in kafka-lag-exporter. Could you please help us with some more details?

added this PR : https://github.com/lightbend/kafka-lag-exporter/pull/255 which will enable kafka-lag-exporter to read passwords as environment variable

AFAIK this has been addressed. Please comment (or better yet create a PR) if the issue remains.


How to run Arrakis in KVM/QEMU

I would like to contribute to this work. Both the presentation and talk is impressive.
Can someone guide me.

Glad you'd like to contribute. Unfortunately, we don't have the manpower to guide you. The best way to contribute is to find an area of the OS that you think needs work and then to contribute your code. Please be aware that Arrakis is now fully merged with Barrelfish.

Thank you


[CNCF] On boarding - create an in repo Maintainers file in the operator repo

Part of the CNCF onboarding issue
This is the list of all bullet points from the CNCF onboarding issue : This issue will track one of those points and I'll be happy to help contribute a PR for this
I noted that CLOMonitor reports that the    Maintainers Check is not passing for the operator repo
I can see named maintainers on the CSV file in the cncf/foundation repo and that's great to have as a starting point.
Is it ok to add the maintainers listed there to a maintainers file in the operator repo?

I'm not sure exactly how the maintainers check is implemented, but for Confidential Containers we have two concepts of maintainers. First, we have the maintainers of the entire project. These are specified here. This should match the big CNCF maintainers CSV, although we actually updated our maintainers last week and have yet to update the CSV.
We also have maintainers for individual sub-projects that may or may not be the same as the first set of maintainers. For the operator the maintainers are listed here. Currently that repo just tracks the maintainers via GitHub. There is no MAINTAINERS or CODEOWNERS file. Would it help if we added one?


[CI] Build Docker Image and Github Action for CORD Demo Script

The docker image is built using buildx.
A secret variable named DOCKER_PASSWORD must be present in the repository settings.

I added a organization level variable called DOCKER_TOKEN can you use that instead?

@amarts and @NiranjanAP I have tested this workflow on my fork and tested the Docker image as well. It is designed with buildx therefore will run on multiple architecture.
To test it locally try this:
docker run dhiwayroy/cord-demo-scripts demo

Previously @Rithwik0480 was working to build the Dockerfile and Github Action to deploy the image. But I found his approach to be not correct. So I wrote the Dockerfile and Github Action from scratch.
This PR both adds the Dockerfile and release using Github Action.

@adi-a11y  @Rithwik0480 @roynrishingha docker run dhiway/cord-demo-scripts demo is working now. Good job.
can we fix https://github.com/dhiway/sahaaya/pull/39 to mention only above command? I don't want someone to build images. And all <image-name> in that document should be replaced with dhiway/cord-demo-scripts.


Decompression Fallback games don't display correctly

Description
Honeymoon doesn't display as an embedded WebGL game (presumably, all games with the .unityweb extension won't work)
Response from NP about this:

Question for NP: Is there a way to disable decompression fallback in the Player Settings window?
Yes. If we created the builds again for those affected games we could disable decompression fallback as part of the build process. We would probably have to use the version of Unity used to develop the associated game to do so. According to Unity, enabling this fallback option is intended to accommodate users when "server configuration is unavailable" but we are unsure if there are other impacts. Generally, we have used the same build settings used by the original developer(s) but have not asked them if there was a reason for the build settings they selected. Unity provides more info here about the use and impact of these build settings: https://docs.unity3d.com/Manual/webgl-deploying.html
Also, in cases where access to server configuration is limited, .htaccess can be used on Apache servers. A sample .htaccess configuration that supports the compression options listed above is provided by Unity here: https://docs.unity3d.com/2020.1/Documentation/Manual/webgl-server-configuration-code-samples.html

Solution Tips
Honeymoon has the .unityweb extension, meaning Decompression Fallback is enabled.

https://docs.unity3d.com/2021.1/Documentation/Manual/webgl-building.html

If you enable a Compression Method for your build, Unity identifies the extension that corresponds with the compression method and adds this extension to the names of the files inside the Build subfolder. If you enable Decompression Fallback, Unity appends the extension .unityweb to the build file names. Otherwise, Unity appends the extension .gz for the Gzip compression method, or .br for the Brotli compression method.

https://react-unity-webgl.dev/docs/miscellaneous-instructions/compressed-builds-and–server-configuration

Closed for now, see comment here: https://github.com/GTBitsOfGood/jennifer-anns-group/issues/84#issuecomment-2028436668


Basic minor improvements

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

Project coverage is 100.00%. Comparing base (0e44830) to head (349b2ea).

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           84        86    +2
  Lines         2423      2457   +34
=========================================
+ Hits          2423      2457   +34

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


test: add GHA testing, nuke Travis

ci: replace travis (dead) with Github Actions GHA)
ci: automatically test on ubuntu & windows
ci: automatically test on the LTS versions of node.js
deps: remove mocha & eslint, they get auto-installed by npx when needed

You can preview the test runs in the Actions tab of my fork


Defaults on Functions aren't getting picked up.

@bitner are we good with this one?
we should add tests for the functions 😅

found why https://github.com/developmentseed/tipg/blob/main/tipg/dependencies.py#L352-L353 😅


Bump openssl to 1.1.1f

Changes

Bump openssl to 1.1.1f
Remove makedepend dependency

This is failing CI everywhere.

@runlevel5 Can you try to test locally rather than just pushing commits to this PR? Thanks.

@MikeMcQuaid sure, it works locally for me. I will re-open the PR once I sort out the CI issue with my forked repo.


[ko] Fix typo in 'DNS for Services and Pods' page

modify spec.subdomain example
busy-subdomain -> busybox-subdomain
en-page: https://kubernetes.io/ko/docs/concepts/services-networking/dns-pod-service/#파드의-hostname-및-subdomain-필드
ko-page: https://kubernetes.io/ko/docs/concepts/services-networking/dns-pod-service/#파드의-hostname-및-subdomain-필드

Same update will be required in en section too.

@kundan2707 it seems that EN page has no error, only KO page has errors.

@jihoon-seo
안녕하세요. 타겟 브랜치 변경했습니다.
감사합니다.


tini: 0.17.0 -> 0.18.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/tini/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0/bin/tini -h’ got 0 exit code
ran ‘/nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0/bin/tini --version’ and found version 0.18.0
found 0.18.0 with grep in /nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0
directory tree listing: https://gist.github.com/c992fd0a24dfc0365d6b62ac567d395c

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: tini
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on aarch64-linux (full log)
Attempted: tini
Partial log (click to expand)
-- Install configuration: "Release"
-- Installing: /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0/bin/tini
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0
shrinking /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0/bin/tini
strip is /nix/store/j7d4mr0ikv974ig7yzhknpsq288js4bs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0/bin
patching script interpreter paths in /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0
checking for references to /build in /nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0...
/nix/store/m85nf5b63v8c82qfbkli0fllvkmag59f-tini-0.18.0

Success on x86_64-linux (full log)
Attempted: tini
Partial log (click to expand)
these paths will be fetched (0.01 MiB download, 0.02 MiB unpacked):
  /nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0
copying path '/nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0' from 'https://cache.nixos.org'...
/nix/store/h0h2qyxwrvsjy47m1xyv7sxzd2j0ilsi-tini-0.18.0


Design proposal of changes to the system architecture for the enhancement process adress to process data from multiple crawlers

Reason (Why?)
With the addition of further websites to crawl, the need for an expansion of the enhancement process has arise. The new data does not necessarily conform to the same standards and completion as the currently expected data and thus can require different steps during enhancement. The current approach of having a single data enhancement process for the data from each crawler would lead to duplicate code and a code base that is difficult to maintain.
Solution (What?)
Create a design proposal that addresses the enhancement of data from various websites while maintaining scaleability and which allows to perform enhancement steps both specific to the data of individual websites, as well as general enhancement steps applicable to the data of all websites.
Out of scope
None
Relation to other Issues
#165 Crawlers for various websites
#174 Remove duplicated posts
Acceptance criteria
The proposal for the new software architecture is able to enhance the data of additional websites, supports the enhancement of new data without requiring further changes to the architecture and is implemented.

Please discuss this concept with Armstrong-Arndt, Jamie John (Stud. FBI<EMAIL_ADDRESS><EMAIL_ADDRESS>and Seith, Marvin Oliver (Stud. FBI<EMAIL_ADDRESS><EMAIL_ADDRESS>I want to avoid duplicated design and implementation work.
Von: jonas-hda<EMAIL_ADDRESS>Gesendet: Samstag, 21. November 2020 13:33
An: hochschule-darmstadt/einander-helfen<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Betreff: [hochschule-darmstadt/einander-helfen] Design proposal of changes to the system architecture for the enhancement process adress to process data from multiple crawlers (#176)
Reason (Why?)
With the addition of further websites to crawl, the need for an expansion of the enhancement process has arise. The new data does not necessarily conform to the same standards and completion as the currently expected data and thus can require different steps during enhancement. The current approach of having a single data enhancement process for the data from each crawler would lead to duplicate code and a code base that is difficult to maintain.
Solution (What?)
Create a design proposal that addresses the enhancement of data from various websites while maintaining scaleability and which allows to perform enhancement steps both specific to the data of individual websites, as well as general enhancement steps applicable to the data of all websites.
Out of scope
Final implementation of the design proposal
Relation to other Issues
#165 https://github.com/hochschule-darmstadt/einander-helfen/issues/165
Crawlers for various websites #165 https://github.com/hochschule-darmstadt/einander-helfen/issues/165
Acceptance criteria
The proposal for the new software architecture is able to enhance the data of additional websites, supports the enhancement of new data without requiring further changes to the architecture and can be implemented.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/hochschule-darmstadt/einander-helfen/issues/176 , or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYWHS5R4UMTOLLAMXEKDCLSQ6XPLANCNFSM4T5YJQPA .  https://github.com/notifications/beacon/ABYWHS4CXATA2OPJOGHO3U3SQ6XPLA5CNFSM4T5YJQPKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4LEVXXEA.gif

changed scope of issue to include implementation of new design rather than creating a new issue for the implementation

Closed with the merge of #207


Support GraphQL Upload spec, add bloc example, tests, and coverage

Close  #183
Please pardon me because of this huge request, because I was building this feature on top of other 3 needed commits:

3b43a0d use stricter analysis style (#195)
68d2b3b and 93c14e7 refactor unit test and get test coverage (also address concerns at #125/#189)

Btw, here's the current unit test coverage: https://codecov.io/gh/truongsinh/graphql-flutter/tree/master/lib/src

This PR:

implements [multipart uploads]( as proposed at https://github.com/jaydenseric/graphql-multipart-request-spec)
adds coverage and more tests
adds a bloc example for alternate library usage

I think the examples could be better organized, but I want to do a larger docs/examples update later anyways

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Handle peer addition/removal in a right way

This PR makes PeerTableModel handle a peer addition/removal in a right way. See:

https://doc.qt.io/qt-5/model-view-programming.html#inserting-and-removing-rows
https://doc.qt.io/qt-5/model-view-programming.html#resizable-models

Fixes #160.
Fixes #191.

This PR is based on #18, and only last three commits are subjects to review.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased 734dd5f95168886e12dc2f07dd91902b1242ffc3 -> d325799acdd8d010d5e4b2f77d9cc67d76d4ad28 (pr164.01 -> pr164.02) due to the conflict with #162.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Will be rebased after any progress in #161 :)

Will be rebased after any progress in #161 :)

Rebased d325799acdd8d010d5e4b2f77d9cc67d76d4ad28 -> f73d340abeedf7e583fe9b2a8b3685a745a9199e (pr164.02 -> pr164.03) due to the conflict with #161.

Rebased d325799acdd8d010d5e4b2f77d9cc67d76d4ad28 -> f73d340abeedf7e583fe9b2a8b3685a745a9199e (pr164.02 -> pr164.03) due to the conflict with #161.

Why is this based on #18?

Why is this based on #18?

Why is this based on #18?

It fixes selection behavior and handling in general.

Why is this based on #18?

It fixes selection behavior and handling in general.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased f73d340abeedf7e583fe9b2a8b3685a745a9199e -> 32ce58cb18acc6eb3ac3a2c650c38b7bfdb6ad8b (pr164.03 -> pr164.04) due to the conflict with #180.

Rebased f73d340abeedf7e583fe9b2a8b3685a745a9199e -> 32ce58cb18acc6eb3ac3a2c650c38b7bfdb6ad8b (pr164.03 -> pr164.04) due to the conflict with #180.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased 32ce58cb18acc6eb3ac3a2c650c38b7bfdb6ad8b -> a3d21d3dc3d9166a60f050352ea0eff2a8c2140b (pr164.04 -> pr164.05) due to the conflict with #179.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased a3d21d3dc3d9166a60f050352ea0eff2a8c2140b -> fa95a2205e8c88b23e786a382e55f4534e7733ac (pr164.05 -> pr164.06) due to the conflict with https://github.com/bitcoin/bitcoin/pull/21015.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased fa95a2205e8c88b23e786a382e55f4534e7733ac -> b7fe2b1691330166b478f0ced2dd1b6a8835729b (pr164.06 -> pr164.07) due to the conflict with #166..

Updated b7fe2b1691330166b478f0ced2dd1b6a8835729b -> 7bb0dc97ab08ebcba84b54031874c0648367d756 (pr164.07 -> pr164.08, diff):

addressed @Talkless' comment

Rebased 7bb0dc97ab08ebcba84b54031874c0648367d756 -> ec3075d7342b65bdd72e34f5705f6cdc8a948b67 (pr164.08 -> pr164.09) due to the merging of #18.

🐙 This pull request conflicts with the target branch and needs rebase.
Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".

Rebased ec3075d7342b65bdd72e34f5705f6cdc8a948b67 -> e102c90e41fb82e534c155bd7cfb9d0e9852c092 (pr164.09 -> pr164.10) due to the conflict with #311.

Concept ACK. If this fixes what I think it does, it would be good to see it in v22 as a bug fix.

Updated e102c90e41fb82e534c155bd7cfb9d0e9852c092 -> ecbd91153875c8cdd5b92b840afc116f65e457fb (pr164.10 -> pr164.11, diff):

addressed recent @jarolrod's comments

re-ACK ecbd911
Only changes since last review are implementation of comment nits


Please define errors

In https://github.com/google/goexpect/blob/master/expect.go#L840 and https://github.com/google/goexpect/blob/master/expect.go#L1224 you return a locally defined error.  It would be great if you would define that error as an exported variable so that callers could more cleanly check for it.

Поддерживаю. Периодически возникает непонятная ошибка, а почему - неизвестно


Feature requests

Thanks for making this, great project!
Would you consider adding support for multiple disks? Sometimes you host the OS on a separate drive e.g / and attach a data drive e.g /dev/sdb.
Also a latency check would be great, measure ping between agent/hub or from agent to some service like cloudflare/google?
Ability to see hostname after the server name/title when you click on a server? Example server (hostname here)?
Just some initial ideas.

No problem, thanks for using it.
Multiple disks - yes I want to add a way to do this in the future. It would be nice if you could put the agent on a NAS and see all of your drives. I need to think about how it would be configured and displayed. It may also be tricky with docker so it's not something I'm jumping into immediately.
Latency - good idea, I'll add that to the list. Connection time to the agent and possibly round trip time to receive the stats.
Hostname - can you be a bit more specific about what you mean by hostname? Do you mean pulling the hostname from the agent machine, or are you talking about the name / host you enter when you add a system?

Hostname - the latter, just the ability to add a hostname for the server (I think it makes more sense to show it after you click on a server): Server Name (server.hostname) is what I suggest as there's lots of space to add it there.
Great to hear you might add the other stuff in the future.

To add to the hostname feature, the possibility to change the Name, IP and Port, after you created the entry in the list, would be nice.

To add to the hostname feature, the possibility to change the Name, IP and Port, after you created the entry in the list, would be nice.

You can do this from the pocketbase ui/DB.

I'm soliciting opinions on the implementation for multiple disks in https://github.com/henrygd/beszel/discussions/36, so please comment there if you have any thoughts.


⚠ Bofrost.de has degraded performance

In 2f42446, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1438 ms

Resolved: Bofrost.de performance has improved in 0fd655e after 6 minutes.


Show replica status

For deployments with multiple replicas, it is difficult to grok the overall health of all replicas with only one status indicator. Therefore, we now expose the number of replicas for each status. A component showing this is needed, which could perhaps live by the top bar, like in the following crude photoshop mockup (less wide would look nicer).

Inspiration: Rancher replica status overview

overview

expanded

Looks like this in the deployment object
  "replicaStatus": {
    "desiredReplicas": 1,
    "readyReplicas": 1,
    "availableReplicas": 1,
    "unavailableReplicas": 0
  }

Some conditions:

Only show for deployments
Only show when replicas > 1
Dropdown listing the status (Add i18n locale labels for each status)

Hi!
I started to work on this but i have a few questions,
what statuses are wanted, and what should they represent.
I currently have these:

Ready: Amount gotten from readyReplicas for replicas that are ready, no current action (showed in green)
Occupied: Amount gotten from availableReplicas - readyReplicas for replicas that are doing something (showed in blue) does this make sense?
Unavailable: Amount gotten from unavailable replicas for replicas that are unavailable.

(The colors are temporary, just using "green", "blue" and "red")

Adding @saffronjam to the loop, what do you think makes most sense, not sure what the difference between ready and available is here

Statuses are taken directly from Kubernetes. Here's a post describing them :) https://stackoverflow.com/questions/66317251/couldnt-understand-availablereplicas-readyreplicas-unavailablereplicas-in-dep

Hi!
I started to work on this but i have a few questions, what statuses are wanted, and what should they represent.
I currently have these:

Ready: Amount gotten from readyReplicas for replicas that are ready, no current action (showed in green)
Occupied: Amount gotten from availableReplicas - readyReplicas for replicas that are doing something (showed in blue) does this make sense? Edit: busy might be a better name for this
Unavailable: Amount gotten from unavailableReplicas for replicas that are unavailable.
Wanted: Amount gotten from desiredReplicas - (availableReplicas + unavailableReplicas) for replicas that the user wants but doesnt exist.

Nice updated mockup! I think this makes sense, maybe we could use Desired instead of Wanted since that seems to be the wording used in many K8s docs, but other than that it looks great :)

Thanks!
Yes, desired may be better, I just wanted to differantiate between desired at first since it is displaying the amount of:
desiredReplicas - (availableReplicas + unavailableReplicas).
Will take a look at the k8s replicaSet status docs to make sure they match.

Hi again,
I can´t get the status to show for multiple replicas, i created a deployment to test without hard-coded values and i get the same replicaStatus regardess of the number of replicas on the deployment.
{
        "id": "0fc7e863-8cb5-4ecd-b49c-ad8f8de673f5",
        "name": "joyfully-cautiously-minus",
        "type": "prebuilt",
        "ownerId": "4efea96b-2d6b-41f6-96a2-656f18d6f8d1",
        "zone": "se-flem-2",
        "createdAt": "2024-05-20T18:30:57.963Z",
        "updatedAt": "2024-05-20T18:35:39.328Z",
        "accessedAt": "2024-05-20T18:35:52.479Z",
        "cpuCores": 0.2,
        "ram": 0.5,
        "replicas": 4,
        "url": "https://joyfully-cautiously-minus.app.cloud.cbh.kth.se",
        "envs": [
            {
                "name": "NAME",
                "value": "THIS_IS_A_DUMMY"
            },
            {
                "name": "PORT",
                "value": "8080"
            }
        ],
        "volumes": [],
        "initCommands": [],
        "args": [],
        "private": false,
        "internalPort": 8080,
        "image": "nginx:latest",
        "healthCheckPath": "/healthz",
        "status": "resourceRunning",
        "replicaStatus": {
            "desiredReplicas": 1,
            "readyReplicas": 1,
            "availableReplicas": 1,
            "unavailableReplicas": 0
        },
        "pingResult": 502,
        "integrations": [],
        "teams": [],
        "storageUrl": "..."
    },

That's because we are "cheating" a little bit. Having more replicas just edits your scaler (HPA) so that you could have more given your load. So if you add more load, like http requests, more pods will probably be created.
A tool like siege is useful! ☺


Clear _subviews array on _downsertBindings

As described on #182, the subviews array is not being cleared when the subviews are removed, which means it will contain old view if eventually the parent is re-rendered after remove.

Looks good to me. Thanks for the tests, too!

Tests pass locally. Going to merge.


added new auth for ECS check app

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.“Roman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Check is io_uring or epoll syscalls interface available and use it if so

Looks pretty good, only request I have is that the duplicated part of determining the transport method be moved out to a static helper, since it's currently in both the client and the server classes.


Fix comms consoles not working

About the PR
Fixes communications consoles not working correctly.


Data Convertor between TreeWidthSolver.jl and OMEinsumContractionOrder.jl

Plan to add a backend using tree decomposition, which will be provided in TreeWidthSlover.jl.
A data convertor between OMEinsumContractionOrder.jl and TreeWidthSlover.jl, to convent tensor networks as graphs and to convert tree decomposition as contraction order, should be added in the future.

The TreeWidthSlover.jl now work as a backend of the optimizer ExactTreeWidth(), see #43

Fixed by #43


clang-format 18

Issue:
We used clang-format 9 since forever, but it's not easy for people to get such an old version anymore.
Move to 18, the latest version.
If your machine can't easily install 18, it's bundled in VSCode's C/C++ extension. If you need to run it on the command line, make a shortcut pointing here: ~/.vscode/extensions/ms-vscode.cpptools-1.20.5-darwin-x64/LLVM/bin/clang-format.
Research:
We want to update to the newest version that can easily be installed on the platforms/IDEs we develop on. These are:

VSCode: 18 is bundled into the C/C++ extension, and it's what gets used if you don't have clang-format installed on your machine.

If you have a different version on your machine, and want to use the version bundled in VSCode, edit your settings like: "[cpp]": {"editor.defaultFormatter": "ms-vscode.cpptools"},

macOS:8, 11, 18 via brew install clang-format@version

18 is the default and runs as clang-format. If you install 11, then you must run it as clang-format-11

Windows: Not sure how to install it, but 18 is available via VSCode extension
Amazon Linux 2: 11 only via yum install clang-tools-extra
Amazon Linux 2023: 15 only via dnf install clang-tools-extra
Ubuntu 24: 18 via apt install clang-format

Since 18 is latest, and easily available on all platforms via the VSCode extension, let's use that.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

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

Project coverage is 83.14%. Comparing base (24e2396) to head (da5b44a).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1113   +/-   ##
=======================================
  Coverage   83.14%   83.14%
=======================================
  Files          56       56
  Lines        5760     5760
=======================================
  Hits         4789     4789
  Misses        971      971

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

Oh hold until new ubuntu-24.04 Github runner becomes available...
https://github.com/actions/runner-images/issues/9691


Custom Themes impact

Please clarify the impact on the sites with custom themes. How will the theme be displayed on the modern home page.

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

ID: 8659498a-6c73-763a-31a0-354010572115
Version Independent ID: dc4c2e96-fb55-67c0-ec7b-6f1f608eb0cb
Content: Disable automatic modernization of classic site home pages - SharePoint Online
Content Source: SharePoint/SharePointOnline/disable-auto-modernization-classic-home-pages.md
Service: sharepoint-online
GitHub Login: @Holland-ODSP
Microsoft Alias: hokavian

@wizneeraj Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hello @wizneeraj
I think that the information you are looking for is here if I understood you well, if not, please kindly inform me and I will try to help.

Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Create github actions workflow

Switches from travis to github actions
Fixes https://github.com/image-rs/jpeg-decoder/issues/141

@HeroicKatora This is ready for merging. The testing times are greatly reduced

@Iovasoa Could you do a follow up with the status badge? Also want to see it in action ;)

of course


timer out of sync errors... still

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.41.0.dev0
Python release (python3 --version):
Python 3.5.3
Component/platform:
Description of problem:
I am still plagued with "timer out of sync" messages after a few hours... then hass is unresponsive and I have to try to restart the docker container. If i can't catch it in time, i have to actually reboot the machine to recover
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

I wish I knew....

Traceback (if applicable):
17-03-21 19:16:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.blueiris_profile is taking over 10 seconds.
17-03-21 19:17:30 INFO (Thread-1) [homeassistant.components.sensor.command_line] Running command: python3 /config/sensor/getBIProfile.py
17-03-21 19:17:34 INFO (Thread-12) [plexapi] GET http://main:32400/status/sessions
17-03-21 19:17:40 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.blueiris_profile is taking over 10 seconds.
17-03-21 19:17:57 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:18:03 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:18:09 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:18:10 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.playroom is taking over 10 seconds.
17-03-21 19:18:13 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
17-03-21 19:18:16 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:18:17 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.living_room_tv is taking over 10 seconds.
17-03-21 19:19:14 WARNING (Thread-17) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:19:25 WARNING (Thread-15) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:19:59 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:20:01 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonarr_upcoming is taking over 10 seconds.
17-03-21 19:20:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.master_bedroom_lights is taking over 10 seconds.
17-03-21 19:20:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.plex is taking over 10 seconds.
17-03-21 19:20:02 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.master_bedroom_tv is taking over 10 seconds.
17-03-21 19:20:02 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:20:29 WARNING (Thread-18) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:20:38 WARNING (Thread-16) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:20:38 WARNING (Thread-14) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:20:38 WARNING (Thread-19) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:20:38 WARNING (Thread-17) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:20:39 INFO (Thread-11) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
17-03-21 19:22:11 INFO (Thread-11) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
17-03-21 19:23:08 WARNING (Thread-18) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:23:34 WARNING (Thread-14) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:23:48 WARNING (Thread-19) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:23:48 WARNING (Thread-16) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:23:50 INFO (Thread-11) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
17-03-21 19:24:24 WARNING (Thread-17) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:24:25 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:24:25 WARNING (MainThread) [homeassistant.helpers.entity] Update of light.bens_lamp is taking over 10 seconds.
17-03-21 19:24:26 WARNING (MainThread) [homeassistant.helpers.entity] Update of media_player.living_room_tv is taking over 10 seconds.
17-03-21 19:24:28 INFO (Thread-5) [homeassistant.components.sensor.command_line] Running command: python3 /config/sensor/getBIProfile.py
17-03-21 19:24:28 WARNING (MainThread) [homeassistant.components.light] Updating hue light took longer than the scheduled update interval 0:00:30
17-03-21 19:25:29 INFO (Thread-8) [plexapi] GET http://main:32400/status/sessions
17-03-21 19:25:30 WARNING (Thread-16) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:25:25 WARNING (Thread-17) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:25:29 WARNING (Thread-19) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:25:30 WARNING (Thread-18) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-21 19:25:29 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
17-03-21 19:25:36 INFO (Thread-11) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
17-03-21 19:26:22 INFO (Thread-11) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
17-03-21 19:26:22 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-21 19:26:22 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.blueiris_profile is taking over 10 seconds.
17-03-21 19:26:22 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.sonarr_upcoming is taking over 10 seconds.
17-03-21 19:26:22 WARNING (MainThread) [homeassistant.helpers.entity] Update of sensor.plex is taking over 10 seconds.
17-03-21 19:26:23 WARNING (MainThread) [homeassistant.components.media_player] Updating braviatv media_player took longer than the scheduled update interval 0:00:10
17-03-21 19:26:24 WARNING (MainThread) [homeassistant.components.sensor] Updating command_line sensor took longer than the scheduled update interval 0:01:00
17-03-21 19:26:24 WARNING (MainThread) [homeassistant.components.light] Updating hue light took longer than the scheduled update interval 0:00:30
17-03-21 19:26:24 WARNING (MainThread) [homeassistant.components.media_player] Updating sonos media_player took longer than the scheduled update interval 0:00:10
17-03-21 19:26:24 WARNING (MainThread) [homeassistant.components.media_player] Updating webostv media_player took longer than the scheduled update interval 0:00:10
17-03-21 19:26:25 ERROR (Recorder) [homeassistant.components.recorder.util] Error executing query: (_mysql_exceptions.OperationalError) (2006, 'MySQL server has gone away')
17-03-21 19:26:25 INFO (Thread-13) [homeassistant.components.emulated_hue.upnp] UPNP responder shutting down.

Additional info:
I am running hass in a docker container. My previous issue was closed saying it was resolved... but the issue still persists for me. If there is anything I can do to try to nail this down, I am more than willing because it is becoming very frustrating.

If you are using any type of Bluetooth tracker, please disable that.

I don't have any bluetooth trackers. I have nmap and asus device trackers. Things I have tried to resolve this issue:
Disable all device trackers
Disable my command line sensor
disable my plex sensor
Switch from using mysql db to the built in db.
You can see my config here: https://github.com/iambdud/Home-AssistantConfig
What else can i try or tell you?

I have a very similar log, also in DOCKER on UnRAID
17-03-22 20:46:45 WARNING (MainThread) [homeassistant.setup] Setup of remote is taking over 10 seconds.
17-03-22 20:46:45 WARNING (MainThread) [homeassistant.setup] Setup of media_player is taking over 10 seconds.
17-03-22 20:46:45 WARNING (MainThread) [homeassistant.setup] Setup of device_tracker is taking over 10 seconds.
17-03-22 20:46:45 WARNING (MainThread) [homeassistant.components.remote] Setup of platform harmony is taking over 10 seconds.
17-03-22 20:46:45 WARNING (MainThread) [homeassistant.components.media_player] Setup of platform cast is taking over 10 seconds.
17-03-22 20:46:53 WARNING (MainThread) [homeassistant.components.sensor.template] Could not render template nexus battery, the state is unknown.
17-03-22 20:49:49 WARNING (MainThread) [homeassistant.components.remote] Updating harmony remote took longer than the scheduled update interval 0:00:30
17-03-22 20:52:23 WARNING (MainThread) [homeassistant.components.remote] Updating harmony remote took longer than the scheduled update interval 0:00:30

this last line repeats forever.
Commands that I send via the remote take many minutes to arrive at the TV

Likewise getting this same error on 0.40.2.  No bluetooth enabled

Try to disable the components that are listed as taking more than 10 seconds to update.

@Danielhiversen the components that list as taking more than 10 seconds varies every time i restart hass. For instance, in my last case of a crash (about 5 minutes ago), only "device_tracker" took "more than 10 seconds." In the past, I have disabled device_tracker to resolve my issue with out look.

FYI, I'm still having the issue even with the latest release. I am actually getting a new machine this week and I will start from scratch with hass on that machine and see what happens. I'll update this with the results. If anyone has anything else for me to try in the meantime, please let me know.

I don't see these errors unless I refresh the logbook....looks like a SD card read/write may be causing these errors. Also, it seems you are seeing far too many "more than 10 seconds warning". Where are you running HA? Is your SD card (if you are using one) Class 10 rated? Also, are you purging your recorder or using mySQL or any other db?

I'm running HA in docker on an ubuntu VM. The VM has 1GB of RAM and the VM itself resides on flash storage.
Here is my entire log from the last crash I had (last night around 11pm) https://hastebin.com/ilegukemep.sql
I am purging recorder data every 7 days. I was previously using mysql, but switched back to the built in db (to see if it helped)... so essentially started the db over.
I just set my logger level to debug... we'll see if that provides any more useful information.

It just crashed again. I had debug logging on, but I'm not sure if it's safe to share a debug log. In the log, I see that starting at 9:15 I see a whole bunch of entries (every 10 seconds it looks) for trying to configure my LG WebOS TV... I don't know if it's a cause of anything... in any case, I've disable that media_player to see if it helps.
Incidentally, i did just install grafana this afternoon and can see that memory and cpu slowly climbed until it crashed. It appears to have started at 9:15... However... I have had the system crash when I am not at home and this particular TV hasn't been turned on all day... so not sure if it's related or not.

@iambdud i don't know about LG, but Samsung TVs wake up periodically (to check for updates I presume). If LG is the same it's irrelevant whether the tv is turned on or not.

So... I've removed my LG tv as an entity... and I haven't had hass crash since then. However... at the same time, I did move hass to a new server and gave that server more specs (2gb of RAM).
I'm pretty confident that the issue was caused by the LG TV entity and the fact that it kept trying to authorize it... I never got a prompt or anything in the UI nor on the TV... so I'm not sure what happened there.
I will close this issue, but let me know if there's anything else you want me to test.

CC @wokar


Remove duplicated doc entry

Which part is duplicated? This snippet is the only part of the README that mentions FORCE_CONTAINER_REMOVAL

Bad eyesight on my part :)

No problem. Thanks for the contribution anyway! :smile:


Create main calculator screen

Need to create the first screen for the general math portion of the calculator

Resolved


Documentation SMTP settings in kapacitor.conf of the "to" value

URL for relevant page?
https://docs.influxdata.com/kapacitor/v1.5/event_handlers/email/
What products and version are you using?
kapacitor version 1.5
Where did you look before opening the issue?
the documentation and example configs in stackexchange
The example code in the documentation, under the item "Using the SMTP/Email event handler" on the page "https://docs.influxdata.com/kapacitor/v1.5/event_handlers/email/" has a typo.
Current config of the "to" parameter:
to =<EMAIL_ADDRESS>Does not work.
Starting the kapacitor service returns the following error:
"2018/08/29 09:36:25 Using configuration at: /etc/kapacitor/kapacitor.conf
ts=2018-08-29T09:36:25.927Z lvl=error msg="encountered error" service=run err="parse config: toml: cannot load TOML value of type string into a Go slice"
run: parse config: toml: cannot load TOML value of type string into a Go slice
"
Even for a single value it should be a list of one value.
Fix:
to =<EMAIL_ADDRESS>With this change the service stars without issues

Great find @mindstormsbe. You're correct. The to data needs to be formatted as an array, even for single recipients. I've updated the example.


Supported versions of Exchange

Hi,
is exchange 2013 supported by  php-ews?
I'm creating a web application connected to an exchange 2007 server.
Soon the the server will be replaced with a 2013 version.
The scripts created for 2007 version will be ok for 2013 version?
Regards

I've been able to send through Exchange 2013 on our network. I think one caveat was I had to explicitly set the version to 2010 SP2, since the class will default back to 2007 if it doesn't detect the version right.
$ews = new ExchangeWebServices(EXCHANGE_SERVER, EXCHANGE_USER, EXCHANGE_PASS, ExchangeWebServices::VERSION_2010_SP2);
I've also had some issues with connecting to AutoDiscover, but I don't know if that is just based on our domain setup.
Also, definitely make sure your cURL version is up to par with the required version in the readme, otherwise NTLM authentication will fail for sure.


chore: improve changelog generation

Summary
This PR should improve the generation of release notes.
As before, we extract the changelog part of a release and append the generated GitHub notes. However, we now exclude all PRs labelled by A-Changelog or S-Needs-changelog-update. The idea is to avoid including changelog entry already present in what we extracted.
To keep the computed Contributors section up-to-date, I propose adding who contributed to a change directly in the CHANGELOG. I updated some entries to give an example. If we decide to use this convention, I will update the rest of the CHANGELOG.
I updated the changelog section of the CONTRIBUTING guide.
I improved the script that extracts a changelog entry by always extracting the first section instead of looking for Unreleased. This should make the script more robust to potential typos.

To keep the computed Contributors section up-to-date, I propose adding who contributed to a change directly in the CHANGELOG.

Wouldn't be easier to ask the contributor to add a changelog line at this point?
This starts to be a lot of work , and it seems we're moving towards an automated system to generate the changelog.
Also, when do we need to use S-Needs-changelog-update?

Wouldn't it be easier to just ask the committer to add a changelog line at this point?

The last time we discussed this, we concluded that this was too much to ask of contributors.
My last committed changes should encourage contributors to update the changelog.
I also updated the PR template.
What do you think?

This is starting to be a lot of work, and it seems we're moving towards an automated system for generating the changelog.

The changelog is still written by hand. Only the GitHub release notes are generated from both `git log' and the manually written changelog.

Also, when do we need to use S-Needs changelog-update?

This allows tagging a PR that doesn't update the changelog, but needs to before a release.

The last time we discussed this, we concluded that this was too much to ask of contributors.
My last committed changes should encourage contributors to update the changelog.
I also updated the PR template.
What do you think?

I have always been on the fence on this one, to be honest. In Astro, we request contributors to add a changelog line (even though it's automated), and it's been working very well. If the contributor is fixing a bug, they know what they fixed, and we set guidelines on how to properly write the changelog. Language might be a barrier, but if you're contributing to this project, having some rudimentary English is essential. And we can always help people who have less English expertise.


Command creates and pushes repo from user input

Combine shell commands to take user input to create and push a repo to Github.

Depends on #3 and #4


Modernizing the docs pom

I tossed out dependencies we don't need once we start using spring-doc-resources.
NOTE: This PR depends on spring-cloud/spring-cloud-build#84
DO NOT merge this one until that one is merged.

@Buzzardo can you rebase and then we can merge?


Database migration from SQLite to Postgres

fguillot,
As the #1740, i needed to migrate from sqlite to postgres.
To make this migration, i used an amazing tool named "pgloader" availlable here.
We make some improvement in pgloader, to convert your sqlite schema. see dimitri's git
At the end, it's possible to login into kanboard and navigate, but just in "read only".
This is the problem now. It's impossible to add new projects, or make a comments, etc..
Writes on db isn't possible.
Here, this is the postgres logs. I hope it is clearer for you
2016-03-04 11:12:10 CET [13730-1] kanban@kanban ERROR:  lastval is not yet defined in this session
2016-03-04 11:12:10 CET [13730-2] kanban@kanban STATEMENT:  SELECT LASTVAL()
2016-03-04 11:12:10 CET [13730-3] kanban@kanban ERROR:  current transaction is aborted, commands ignored until end of transaction block
2016-03-04 11:12:10 CET [13730-4] kanban@kanban STATEMENT:  DEALLOCATE pdo_stmt_0000000d

Kanboard version: v1.0.26
Database type and version: postgres 9.4.6-0+deb8u1
OS: Debian

I don't really support migrations from sqlite to another db because it's a endless source of problems.

@fguillot There are many of us that are locked down using sqlite. I do realize that is my fault for no considering the possible drawbacks of using sqlite beyond speed or consistency. Nevertheless, a long time ago Kanboard stopped being "a little program downloaded from github" and it is now a full blown solution for my everyday organization. It is for personal use! but it still remains as a very important part of my day.
I tried pg_loader and it didn't work for me; half an hour after having converted the database I still was struggling to keep together all the field formats, lenghts and conversions between sqlite and PostgreSQL; I gave up. I tried another solution explained in #1740. It didn't work for me either.
I understand that you don't give support and I understand why you've made that decision; but keep in mind that more and more people will appear asking for a solution. If you don't want to give support for whatever reason it would be, please write a guideline or refer links in the documentation or some kind of "no warranty" support for us who need to convert the databases.
If you think you've got the time, please PLEASE consider writing some kind of export/import engine (to/from json, xml, whatever) in order to easily transport databases from/to any engine possible.
Thank you very much for your time and your awesome contribution to the open source community.
Best regards.

Even if I agree that a full export / import system could be great (especially because it implies that you could export a part of a Kanboard instance A and import it in an already existing Kanboard instance B), I don't think it is something easy to implement.
In the mean time, I am preparing the migration from SQLite to MySQL of a Kanboard in my company. I manage to do it manually and I am working on something more automated. Only the main steps are described at the moment: https://github.com/oliviermaridat/kanboard-sqlite2mysql


Amend argparse code to allow for subparsers

The main goal of this issue is to make the script scalable for future features.
Ultimately, I would love for a command line argument like below to be implemented:
tabletop_prototype.py tts_deckbuilder -i <path> -n <default to 60> -o <path>
tabletop_ptototype.py tts_mapbuilder -i <path> -o <path>

as a potentially reference starting point:
argparse subparsers

another resource on python argparse that might be helpful

Initial implementation of argparse subparsers was implemented. Closing this issue as complete.


Embed/Attach whole pages of PDF files

Description
I would like to be able to import whole pages of a given PDF document at specific locations in the typst document.
Use Case
Proposal writing!
For this, the LaTex package "pdfpages" was a joy to use, because I could create a pipeline that would glue all the relevant pages from the input files of my department into my proposal exactly where they should be.
That way, whenever I made a small correction in the science part of my proposal, I wouldn't need to manually glue the different PDFs together again, the latex compile would do it all for me.

Ideally, it would be possible to add the correct page numbers of the outer document onto the imported PDF pages. For this, sometimes it might be necessary to stop the import at a given height, as to not have the old page number of the imported PDF page visible. pdfpages was supporting that, I believe.

Duplicate of https://github.com/typst/typst/issues/145
(It's not going to happen anytime soon)

I would have thought that embedding PDFs as figures is technically quite a different task than attaching/adding several pages from external PDF documents to the compiled document? Hence the new issue.

I would have thought that embedding PDFs as figures is technically quite a different task than attaching/adding several pages from external PDF documents to the compiled document? Hence the new issue.

If PDF was the only output target, this would technically speaking be true. But it isn't, so both tasks boil down to having to render the PDF, which there is just no viable avenue for right now.


git clone from new ssh host

Issue Type: Bug
Setup a ssh key on a git server for passwordless ssh.
In order to reproduce this issue, it has to be a new host, not one already in ~/.ssh/known_hosts. DO NOT ssh into this git server or clone from it first or you will not be able to reproduce this (unless you remove it from the known_hosts file)
Use the Git: clone command and give it the ssh clone url.
Expected - VSCode will pop up a box about the host being unknown and ask if to trust it (same options as when running git clone from the terminal)
Actual - clone fails with unhelpful message "Host key verification failed"
Once the host is in the known_hosts, either by doing a git clone from a terminal or even just sshing into the machine from a terminal, the clone from within VSCode works fine
I tested this on my setup, which is VSCode on windows connected to a linux remote via ssh, and from there I tried to do the clone. I don't have a way to check this in a simpler setup at the moment, but I don't think it should make a difference.
VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T14:33:55.248Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 5.4.0-104-generic
Remote OS version: Linux x64 5.4.0-105-generic

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (16 x 2496)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
31.67GB (17.40GB free)

Process Argv
--folder-uri file:///d%3A/armadilinux/ArmadilloLinux --crash-reporter-id 026754aa-b996-4f12-9e27-4c515ec2b2cc

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: localhost

OS
Linux x64 5.4.0-104-generic

CPUs
11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (2 x 2496)

Memory (System)
3.83GB (2.21GB free)

VM
100%

Item
Value

Remote
SSH: <IP_ADDRESS>

OS
Linux x64 5.4.0-105-generic

CPUs
11th Gen Intel(R) Core(TM) i7-11850H @ 2.50GHz (1 x 2496)

Memory (System)
0.94GB (0.10GB free)

VM
100%

Extensions (4)

Extension
Author (truncated)
Version

jupyter-keymap
ms-
1.0.0

remote-ssh
ms-
0.76.1

remote-ssh-edit
ms-
0.76.1

vscode-icons
vsc
11.10.0

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
vscgsvid1:30447480
pynewfile477cf:30450039

@BMBurstein, apologies for not getting back to you on this until now. Are you still able to reproduce this issue with the latest version of VS Code Insiders? I am asking as in the recent months we have done some improvements when cloning using SSH. Thanks!

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Include specific content in alert email body

Hello,
I am looking for a way to include the "number of query hits" and the "number of hits" in the email body [alert_text].
Can anyone help?
Thanks in advance!

https://github.com/Yelp/elastalert/issues/637

Could the code changes suggested in #637 be included as the default?  Thanks.

@Qmando @PMDubuc @dulman
How to include some content in the email body. I get the summary_table_fields in my email body. However, I would like to add some content about the triggered rule. Are there any options to do that?


Have problem run on Mac

Hi everyone, I had a problem on running hydrogen on Mac OS.

I think the problem is the python 3 path isn't set right, and python 2.7 is the default.
Does anyone can help me to solve it?
Thank you.

Yes you are correct. you python path is set to python 2. set your python path to python 3 or modify your kernel to use the correct python. See https://github.com/jupyter/notebook/issues/2563 for some help. However this is not a hydrogen issue, but an incorrect install. We recommend opening an issue over on your kernel's repo for support. Other community member are free to comment here to help out though.
Closing because this is not a hydrogen issue.


util/libcrypto.num: fix symbol collision between 1.1.0 and master

In commit 6decf9436f7, fourteen public symbols were removed from util\libcrypto.num and the following symbols renumbered in agreement with @levitte.
Unfortunately, she symbols OCSP_resp_get0_signer and X509_get0_authority_key_id were not adjusted on OpenSSL_1_1_0-stable accordingly.
--- openssl-1.1.0/symbols-1.1.0.num	2018-05-16 16:25:09.437665266 +0200
+++ openssl-master/symbols-1.1.0.num	2018-05-16 16:25:22.452804974 +0200
@@ -27,8 +27,8 @@
 ZINT64_it                               4215	1_1_0f	EXIST:EXPORT_VAR_AS_FUNCTION:FUNCTION:
 CRYPTO_secure_clear_free                4315	1_1_0g	EXIST::FUNCTION:
 EVP_PKEY_set1_engine                    4347	1_1_0g	EXIST::FUNCTION:ENGINE
-OCSP_resp_get0_signer                   4374	1_1_0h	EXIST::FUNCTION:OCSP
-X509_get0_authority_key_id              4448	1_1_0h	EXIST::FUNCTION:
+OCSP_resp_get0_signer                   4360	1_1_0h	EXIST::FUNCTION:OCSP
+X509_get0_authority_key_id              4434	1_1_0h	EXIST::FUNCTION:
 conf_ssl_name_find                      4469	1_1_0i	EXIST::FUNCTION:
 conf_ssl_get_cmd                        4470	1_1_0i	EXIST::FUNCTION:
 conf_ssl_get                            4471	1_1_0i	EXIST::FUNCTION:

Since 1.1.0h was released only recently, the least intrusive fix is to adjust the numbers in OpenSSL_1_1_0-stable to match the numbers in master. Of course this would have to be communicated in CHANGES.
The alternative, adjusting the numbers in master, also affects a released (beta) version, and it requires more numbers to be changed, because 4374 and and 4448 are already used in master:
4374: OCSP_resp_get0_signer (1.1.0) vs. RSA_get0_multi_prime_factors (master)
4448: X509_get0_authority_key_id (1.1.0) vs. OSSL_STORE_SEARCH_by_alias (master)
Checklist

[ ] CHANGES is added or updated

Since the BETA isn't really a release, I think changing in master makes more sense.

In principle, I would agree. But in this case it's only two symbols which are brand new and probably not used by anybody yet. Changing the symbols on master would require renumbering more symbols. So one could maybe break the rules when appropriate. I would like to hear @levitte's about it. If he agrees with you, then I will follow your advice :-).

Ok, then I‘ll fix it in master (in my next time slot).

Superseded by #6278.


confusion about metrics: Successful twin reads from backend (count)

we found by testing that device twin query (device list GET) is shown by Successful twin queries (sum) metric , but metrics: Successful twin reads from backend (count) shows up as zero.  This was confusing.  Please clarify in description of Successful twin reads from backend (count) only measures direct reads, not reads via twin query.

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

ID: 128ea613-ba7a-88bc-4f2b-cc425df00fe7
Version Independent ID: e2732359-a5c9-1333-d5ec-4e5f2af0527c
Content: Use metrics to monitor Azure IoT Hub
Content Source: articles/iot-hub/iot-hub-metrics.md
Service: iot-hub
GitHub Login: @nberdy
Microsoft Alias: nberdy

@gjswalling Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@Alberto-Vega-MSFT Can you please assign to @jlian ?

Ack, I'll work on this probably in the next couple of weeks

@jlian Just checking in to see if there is any update on this feedback so that it can be closed.

PR has been created to fix this.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Refactor 3D convolution

simplify the implementation of the kernel-based (conv3d.h) and toeplitz-based variations such that they can be unit tested outside the layer_t interface
try to write the output|gparam|ginput as a single matrix multiplication

apps/convnet: compute the optimum number of feature planes (such that the number of parameters per layer is approximatively constant), given the kernel size and its connectivity per layer
extend convolution layer to support output planes that are not multiple of the connectivity factor
maybe this will make them faster or more memory efficient: no need to use m_toe_iidata and update directly m_idata and then at the end of the loop swap the connected channels.

generalize the convolution layer to use a generic connectivity matrix

try to reduce the number of buffers for the toeplitz-based operator: m_kdata_inv & buffers used for multiplication.


Updated .hound.yml to match new format

Looks like it addresses https://github.com/springernature/macmillan-utils/issues/33 .  Okay by me 👍


Error while fetching HF_TOKEN

/usr/local/lib/python3.10/dist-packages/huggingface_hub/utils/_token.py:99: UserWarning:
Error while fetching HF_TOKEN secret value from your vault: 'Requesting secret HF_TOKEN timed out. Secrets can only be fetched when running from the Colab UI.'.
You are not authenticated with the Hugging Face Hub in this notebook.
If the error persists, please let us know by opening an issue on GitHub (https://github.com/huggingface/huggingface_hub/issues/new).
warnings.warn(
WARNING:timm.models._builder:Unexpected keys (bn2.bias, bn2.num_batches_tracked, bn2.running_mean, bn2.running_var, bn2.weight, classifier.bias, classifier.weight, conv_head.weight) found while loading pretrained weights. This may be expected if model is being adapted.

I'm closing this issue due to inactivity. Feel free to comment or open a new issue if you're encountering a similar error 🤗


Media Previous/Next Track Hotkeys not Working

When I hit the media next or previous key on my keyboard, Google Play Music pauses/resumes the music.
These keys work with desktop application music players.  (I do not have these players open at the moment.)  I specified MediaPrevTrack and MediaNextTrack without Control, Alt or Shift in the Customize Bindings section.  If I right-click on the Google Music Hotkey icon in the toolbar and click on Previous Song or Next Song, then the music goes back or advances a song.  So, I know that the functionality could work if the addon could respond correctly to the keys.

Could it be related to this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1251795#c13 ?


example/lib/main.dart

example/lib/main.dart seems not updated. If I copy and paste it in main.dart it produces several error. Can you please check and update the example file so that we can have a quick look of visual usage.

Hi @jihan007 ,
Thanks for reaching out on this issue.
I am using Android Studio.
I just created a new Flutter project.
I added those lines to the dependencies section of the pubspec.yaml file:
  search_choices:
  http:

I clicked on the "Pub get" text button above the pubspec.yaml file.
I pasted the following file to replace the whole lib/main.dart:
https://pub.dev/packages/search_choices/example
I clicked the debug button.
The example app appeared on my connected and selected phone.
I stopped and clicked the run button.
I got the same successful result.
I did the same (debug and run) with the following file as the source:
https://github.com/lcuis/search_choices/blob/master/example/lib/main.dart
I got again twice the same successful result:

Please let me know if there is anything I can do as the example main.dart file seems to work fine from my perspective.

Thanks a lot. Its working now.

Excellent, thanks for letting me know @jihan007 .


Correction for raw affiliation CRAL (UMR 5574 CNRS), Ecole Normale Superieure, 69364 Lyon Cedex 07, France

Correction needed for raw affiliation CRAL (UMR 5574 CNRS), Ecole Normale Superieure, 69364 Lyon Cedex 07, France
raw_affiliation_name: CRAL (UMR 5574 CNRS), Ecole Normale Superieure, 69364 Lyon Cedex 07, France
new_rors: 02feahw73;029brtt94;05a0dhs15;0084x3h80
previous_rors: 02feahw73;029brtt94;05a0dhs15
works_examples: W2109825821;W2135655113
contact: 61624a471106dd582263e38b98cbec57:5b5ef5b34235d01140eded1ddb9b @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


bpfd-operator: Make the CSI deployment default for bpfd-operator

Support for implementing the Container Storage Interface Specification is already in-place. Update the deployment to use it by default and modify the examples to use it as well. Documentation also needs to be updated.
With this change:

When bpfd is started on the host, CSI will be off. This may be changed in the future, but more work needs to be done to allow in non-K8s.
When bpfd is started by the bpfd-operator (via daemonset.yaml), it will set the --csi-support flag on bpfd, enabling CSI.

There is a daemonset-no-csi.yaml if CSI needs to be disabled in a K8 deployment (CSI forces bpfd to K8s v1.26 or later due to K8s bug)
make run-on-kind now uses CSI.
All examples have been updated to use CSI. However, there isn't any logic to flag a Userspace pod that is not using CSI.

Fixes: #776

@astoycos Ready for review.
/hold
Adding a hold so that it doesn't merge until I remove the first commit ([DO NOT MERGE] Use updated examples from private repo)

@astoycos I think I addressed all your comments and CI is Green. When you are happy with it, I'll remove the first commit.


Improve cargo features

#214 removes the implicit features of the dependencies.
Maybe the names can be improved / simplified (mentioning telegram in the telegram related crate is superfluous).
Maybe the default feature can be removed? Using the async client requires disabling the default features which is a bit annoying. Maybe always require adding the wanted feature?

async-client and sync-client or client-async and client-sync?
Maybe go with the file names of the modules: client_ureq and client_reqwest and trait_async / trait_sync


Add option for full_host to allow Clever login from non-secure pages

This change allows you to specify the full_host for the Clever omniauth.
Example using devise:
config.omniauth :clever, Settings.clever.news.client_id, Settings.clever.news.client_secret, { name: 'clever', provider_ignores_state: true, full_host: 'https://myhost.com' }

Note that you can also set the full_host for all omniauth libraries with the following code:
OmniAuth.config.full_host = "https://myhost.com"

However, since this affects all other oauth logins, we would prefer not to have to re-test everything.
BTW, this change has been used in production for over a year, but seeing now that there is an official Clever fork, we'd like to contribute this back.

Hi @joe1chen and @jbusser , the one concerning element of this change is the following comment:
option :full_host
+

 # Allows full host to be overridden. This is important because Clever is forcing https in production,

 # so we need to use https redirect url even when our host page is http.

Clever's security policy necessitates that all production url's are SSL-signed , lest we send student PII to an unsecure server.  Any thoughts?

Our app routes all traffic over HTTPS, so this option doesn't give me anything. That said, I appreciate Clever's position on the matter, and if you decline to merge this change, I would respect your decision.

Our website does not force you to use SSL, unless you decide to login.  So
this change is require me when you are using a mixed SSL/non-SSL website.
Bottom line is when you are using Clever with our website, you are using
SSL for all communication between our site and Clever.
So this pull request is to support this kind of mixed SSL/non-SSL
environment.  We have been using this in production for over a year.
On Thursday, September 1, 2016, csmooth<EMAIL_ADDRESS>wrote:

Hi @joe1chen https://github.com/joe1chen and @jbusser
https://github.com/jbusser , the one concerning element of this change
is the following comment:
option :full_host
+

Allows full host to be overridden. This is important because

Clever is forcing https in production,

so we need to use https redirect url even when our host page is

http.
Clever's security policy necessitates that all production url's are
SSL-signed , lest we send student PII to an unsecure server. Any thoughts?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Clever/omniauth-clever/pull/5#issuecomment-244233452,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAC-AxE9YpMilVvJwLVl2HV83ivHDpQXks5ql1NJgaJpZM4Jo36e
.


Add "common misspelling" spellcheck to repo validation hooks

Is your feature request related to a problem? Please describe.
Full spell checking probably wouldn't work at this time because of the level of technical terms and products that would make the builds fail and be ignored. Adding basic blacklist of common (English) misspellings would improve article quality with less friction.
Describe the solution you'd like
Add a basic blacklist from something like https://en.oxforddictionaries.com/spelling/common-misspellings to the current docs PR validation service
Describe alternatives you've considered
There are a few documents that give examples of spellchecking in products that would always get flagged, but there are common patterns for ignoring checks in Lint/Check systems using in-line directives.

@cillroy Is this your area?


Add Initial name & number Registry Requirements

In order to ensure that there is no overlap of assignment of names and/or numbers of uEs, this commit will add in basic rules for reserving names/numbers for specific purposes.
#67

s standard serv

@sophokles73 , I incorporated your changes and also added ustreamer.proto to define the ue_id there, also changed the utwin id to be sequential (3 in lieu of 26).


[8.x] Add test coverage for Mail::alwaysTo() and Mail::alwaysReplyTo()

Just adding some test coverage.
Before
Mail Mailer (Illuminate\Tests\Mail\MailMailer)
 ✔ Global from is respected on all messages  2 ms
 ✔ Global return path is respected on all messages  2 ms

After
Mail Mailer (Illuminate\Tests\Mail\MailMailer)
 ✔ Global from is respected on all messages  2 ms
 ✔ Global reply to is respected on all messages  1 ms
 ✔ Global to is respected on all messages  1 ms
 ✔ Global return path is respected on all messages  2 ms

Linked to laravel/docs #7620 and #40561

Hey @driesvints I can see all PR builds are failing this today but none of it seems to be related to code changes.
Anything we can help with?

@clemblanco seems like an upstream library is the culprit. I sent in a report: https://github.com/voku/portable-ascii/issues/74

Awesome, thanks @driesvints!

We've fixed the build on 8.x so please rebase and mark as ready when tests pass. Thanks!

Is alwaysTo works on Notifications?

@samirmhsnv it works at the Mailer level so if your Notification is sent by email, yes it will only be sent to the address specified by alwaysTo()

But looks like it doesn’t work for me on notification emails.
Could queues affect alwaysTo ?
Because I’m using queue for toMail on notification.

On 30 Jan 2022, at 12:35 PM, Clem Blanco @.***> wrote:
@samirmhsnv https://github.com/samirmhsnv it works at the Mailer level so if your Notification is sent by email, yes it will only be sent to the address specified by alwaysTo()
—
Reply to this email directly, view it on GitHub https://github.com/laravel/framework/pull/40582#issuecomment-1025095933, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANCXJVVA75TJRMIHF3APQBDUYTZ6LANCNFSM5MU7BDQA.
You are receiving this because you were mentioned.

Sorry @samirmhsnv but I just tried on a blank new application and it does work as expected.
You need to make sure you restart your queue worker so the change is taken into consideration by the long running instance of your application.


Add a parameter to open-wsl.exe for opening your home directory

I'd like to create an shortcut to open-wsl.exe that will open /home/user directory. I know that I can just cd in .zshrc or something but a parameter would be a great way to do it.

I added a -l param to open-wsl.exe (https://github.com/goreliu/wsl-terminal/commit/1b1b74b85f54dafb57c999e4c46bf0e756a96a96), but it only works when use_tmux=0 (in etc/wsl-terminal.conf). If use_tmux=1, when I try doing this, tmux will hang like https://github.com/goreliu/wsl-terminal/issues/1.

Thanks! :smile:


CRAC JDK is not usable as criu needs SUID permissions to work

Description:
I am trying to use CRAC in GitHub Actions. With the following definition:
 - name: Set up Java
        uses: actions/setup-java@v3
        with:
          java-version: '17'
          java-package: 'jdk+crac'
          distribution: 'zulu'

I can't use criu as it's missing SUID permissions. Courtesy of @wkia, it would work if the archive was extracted using sudo tar xz.
There's not much, but here it is failing: https://github.com/spring-projects/spring-lifecycle-smoke-tests/actions/runs/10032558509/job/27724454193
With a manual setup (see https://github.com/spring-projects/spring-lifecycle-smoke-tests/commit/efd6ee22b9eafdf1276739574ff57d67e1156bba), it is working: https://github.com/spring-projects/spring-lifecycle-smoke-tests/actions/runs/10039511315
Task version:
v3
Platform:

[x] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Repro steps:
Expected behavior:
criu works out-of-the-box
Actual behavior:
criu fails as it's missing SUID permissions

Hello @snicoll,
Currently, the setup-java action does not directly support CRaC-specific configurations. CRaC relies on a fork of CRIU, which requires broad permissions, usually involving running as root granted through the SUID bit.
After setting up a CRaC-aware OpenJDK with setup-java, you need to change the CRIU ownership to root and set the SUID bit.
Please ensure the CRIU binary is owned by the root user and has the SUID bit set:

Check CRIU Permissions:
ls -la $JAVA_HOME/lib/criu

Update Permissions if Necessary:
sudo chown root:root $JAVA_HOME/lib/criu
sudo chmod u+s $JAVA_HOME/lib/criu

For more information, see: Azul CRaC Debugging Documentation

@priyagupta108 thanks very much for the reply. I've done something similar in https://github.com/spring-projects/spring-lifecycle-smoke-tests/actions/runs/10039511315 (see in the above description) although your use of $JAVA_HOME is much cleaner.
The issue here was to see if this could be done automatically. Given that jdk+crac is a supported distribution, it makes sense to me it would.

Hi @snicoll,
Thank you for your response. Since setting SUID permissions on the CRIU binary requires root access (a runner-level privilege), it might be more appropriate to address this concern in the actions/runner-images repository.
Going to transfer this issue to the actions/runner-images repository to ensure it gets the attention it needs.


bazel-gazelle: 0.36.0 -> 0.37.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/bazelbuild/bazel-gazelle/releases.
meta.description for bazel-gazelle is: Gazelle is a Bazel build file generator for Bazel projects. It natively
supports Go and protobuf, and it may be extended to support new languages
and custom rule sets.
meta.homepage for bazel-gazelle is: https://github.com/bazelbuild/bazel-gazelle
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.37.0 in filename of file in /nix/store/brb6d6sfspq721qkzzvdh24k8i1zjs36-bazel-gazelle-0.37.0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath

bazel-gazelle
envoy
pomerium

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/brb6d6sfspq721qkzzvdh24k8i1zjs36-bazel-gazelle-0.37.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A bazel-gazelle https://github.com/r-ryantm/nixpkgs/archive/239c6f09c7d7f3f768034974396831e42e2a2227.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/239c6f09c7d7f3f768034974396831e42e2a2227#bazel-gazelle

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/brb6d6sfspq721qkzzvdh24k8i1zjs36-bazel-gazelle-0.37.0
ls -la /nix/store/brb6d6sfspq721qkzzvdh24k8i1zjs36-bazel-gazelle-0.37.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

3 packages built:

bazel-gazelle
envoy
pomerium

Maintainer pings
cc @kalbasit for testing.

Result of nixpkgs-review pr 314454 run on x86_64-linux 1

3 packages built:

bazel-gazelle
envoy
pomerium


hsa api call failure at line 952, call returned 4104 R9 290x Arch Linux

secret sauce

Is your user in the video group? The strace appears to show that you do not have access to /dev/kfd/

Yessir I am.

I fixed it. AMDKFD needs to be added to initramfs so the HSA ram can be allocated. I was just using sudo modprobe amdkfd. Looks like arch will have a working ROCm stack after all. lov u @jlgreathouse

Yo if I get these packages working and accepted into AUR, and then update your ReadTheDocs page with the Arch install process can I get a namedrop somewhere in there?

Also if/when you read this @jlgreathouse you mind just deleting the issue entirely? I don't want somebody stealing my secret sauce and uploading the packages to AUR before I do.

LoadLib(libhsa-ext-finalize64.so.1) failed: libhsa-ext-finalize64.so.1: cannot open shared object file: No such file or directory
LoadLib(libhsa-ext-image64.so.1) failed: libhsa-ext-image64.so.1: cannot open shared object file: No such file or directory
Which of the source packages provide these?

How do I get the thunk package to get these two files
lrwxrwxrwx 1 maxr users   26 Nov 20 05:45 libhsa-ext-finalize64.so -> libhsa-ext-finalize64.so.1
-rwxrwxr-- 1 maxr users  12M Nov 20 05:45 libhsa-ext-finalize64.so.1
lrwxrwxrwx 1 maxr users   23 Nov 20 05:45 libhsa-ext-image64.so -> libhsa-ext-image64.so.1
-rwxrwxr-- 1 maxr users 1.1M Nov 20 05:45 libhsa-ext-image64.so.1

Hi @maxcr
If you get some build directions together (and get things into AUR), I would definitely be interested in seeing them and giving credit where credit is due.
I actually have a plan (once I return from holiday vacation) to release scripts for installing ROCm on various distros, both from packages and from source. The packages for Ubuntu and CentOS/RHEL are already available, and I'm almost done with the scripts to build from source on those distros. If you have similar directions from Arch, I can add them to that script repo once it's available.
We are aware that various pieces of documentation are out of date. I've tried to keep the installation directions and hardware requirements pages up-to-date. I, personally, don't have the time to own every piece of documentation, however. Your concern is noted.
As for the two files you're looking for with ROCr: those are closed-source components at this time and are thus only available in our binary .deb/.rpm packages. However, the ROCm stack can (mostly) function without them. The HSAIL finalizer has been deprecated and is no longer shipped as part of ROCm, while the HSA image extensions are primarily used for OpenCL images. Without that library available, images types will be disabled in our OpenCL runtime but everything else will continue to function.

I've got a PKGBUILD for the thunk portion of the package. I'll have the ROCR portion working in a few hours and then eventually all the packages.

The AUR already has packages for all the components, they just need to have
some tweaking.
On Wed, Nov 28, 2018 at 5:43 PM Max Robbins<EMAIL_ADDRESS>wrote:

I've got a PKGBUILD for the thunk portion of the package. I'll have the
ROCR portion working in a few hours and then eventually all the packages.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RadeonOpenCompute/ROCm/issues/618#issuecomment-442538829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHM2sRiW9cTTZvp0Vdp7k60NpGxg1wvOks5uzstUgaJpZM4YomV1
.


Add downloads badge

Just adding download stats, if you want to merge make sure to select "Squash and Merge"

I am not authorized to merge this pull request.

I am not authorized to merge this pull request.

:thinking: sorry about that - how about now?


Remove GitHub Sponsors button

May I ask what happens to existing sponsors (like me)? Or are you just not advertising the sponsoring anymore, but leave it open? Congrats on the funding btw.

Hi @dreis2211,
This PR is a "hot fix", but next week we will properly rethink our sponsorship, including what to do with the current balance :)
One thing we can say for sure is that existing sponsorship money will make it back to the community, e.g. in a form of a bounty program or similar :)


Yandex and Alexa verifications require missing configuration flags

[ ] This is a question about using the theme.
[x] I believe this to be a bug with the theme --- not Jekyll, GitHub Pages or one of the bundled plugins.
[ ] This is a feature request.
[x] I have updated all gems with bundle update.
[x] I have tested locally with bundle exec jekyll build.

Environment informations

Minimal Mistakes version: 3.2.1
github-pages or jekyll gem version: 3.1.6
Operating system: OS X 10.11.5

Expected behavior
Adding a value to site.alexa_site_verification or site.yandex_site_verification front matter does not output the expected meta tags given seo.html has liquid conditions requiring a flag under site.owner.[service].verify to be truthy in order to output the tag.
Steps to reproduce the behavior

Add a verification codes for Alexa or Yandex to _config.yml.
Observe no new meta tags output in the generated document head.

Here's the webmaster verification related code in seo.html as of this version:
{% if site.google_site_verification %}
  <meta name="google-site-verification" content="{{ site.google_site_verification }}" />
{% endif %}
{% if site.bing_site_verification %}
  <meta name="msvalidate.01" content="{{ site.bing_site_verification }}">
{% endif %}
{% if site.owner.alexa.verify %}
  <meta name="alexaVerifyID" content="{{ site.alexa_site_verification }}">
{% endif %}
{% if site.owner.yandex.verify %}
  <meta name="yandex-verification" content="{{ site.yandex_site_verification }}">
{% endif %}

Is there a specific reason Yandex and Alexa don't follow the same branch logic pattern used for Google or Bing?

@jhabdas Looks like you found some typos. Both Alexa and Yandex should follow the same logic as the others. owner shouldn't be in the variable names.
Happy to merge in a pull request if you want to take a stab at fixing it. It's a super easy change.


Simplify requirements

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 60.676%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1077

Relevant Lines:
1775

💛  - Coveralls