envelope encryption: filter selects topics to encrypt

Type of change

Enhancement / new feature

Description
Resolves #811
With this change the User can configure the encryption filter to only apply Encryption logic to specific filters using inclusion/exclusion lists of exact topic names and topic name prefixes.
Example config:
    - type: EnvelopeEncryption
      config:
        kms: VaultKmsService
        kmsConfig:
          vaultTransitEngineUrl: http://vault.vault.svc.cluster.local:8200/v1/transit
          vaultToken: myroottoken
        topics:
          includeNames: ["encryptedTopic"]
          excludeNames: ["unencryptedTopic"]
          includeNamePrefixes: ["include_prefix_"]
          excludeNamePrefixes: ["exclude_prefix_"]
        selector: TemplateKekSelector
        selectorConfig:
          template: "${topicName}"

Note this is a nonsensical configuration to show the 4 lists.
Selection Logic

Topic selection is permissive by default. So all topics would be selected for encryption if topics is not set, is set to null, or has only empty/missing/null lists.
If includeNames or includeNamePrefixes is not empty, then the topic must  match an inclusion rule to be selected.
If excludeNames or excludeNamePrefixes is not empty, then the topic must be included and not match any exclusion rules to be selected.
Exclusion beats inclusion, so (include["mytopic"], exclude["mytopic"]) would result in mytopic not being selected for inclusion.

More realistic examples:

Target only topic encryptedTopic, leave everything else unencrypted

topics:
  includeNames: ["encryptedTopic"]

Target only topics with prefix encrypted_, leave everything else unencrypted

topics:
  includeNamePrefixes: ["encrypted_"]

Target only topics with prefix encrypted_ except for encrypted_special

topics:
  includeNamePrefixes: ["encrypted_"]
  excludeNames: ["encrypted_special"]

Target all topics except for always_unencrypted

topics:
  excludeNames: ["always_unencrypted"]

Target all topics except for topics prefixed unencrypted_

topics:
  excludeNamePrefixes: ["unencrypted_"]

Target all topics except for topics prefixed unencrypted_ and the topic special_unencrypted

topics:
   excludeNames: ["special_unencrypted"]
  excludeNamePrefixes: ["unencrypted_"]

Why:
Currently we rely on the KMS response when resolving aliases to determine if encryption should be applied. We take the existence of the key to mean that we should encrypt. This has some negative implications. Like if most of the topics do NOT have a key then we will hit the KMS on every produce request going through the filter for those unencrypted topics. Also, there are more places where misconfiguration could mean writing unencrypted data to a topic we really hoped would be encrypted (mismatched key name in vault and kek selector).
By making the filter aware of which topics we require encryption for, we can make it an exceptional case that the key is not found in the KMS. This logic may change when we come to using features other than topic name for key selection, but it will likely always be useful to be able to configure which topics need some amount of encryption applied so we can short-circuit for unencrypted topics. We also reduce the cases where unencrypted data could be unexpectedly written because a configuration mismatch and key missing in the KMS would result in exceptions rather than unencrypted data forwarded to the cluster.
Checklist
Please go through this checklist and make sure all applicable tasks have been done

[ ] Write tests
[ ] Make sure all tests pass
[ ] Review performance test results. Ensure that any degradations to performance numbers are understood and justified.
[ ] Make sure all Sonar-Lint warnings are addressed or are justifiably ignored.
[ ] Update documentation
[ ] Reference relevant issue(s) and close them after merging
[ ] For user facing changes, update CHANGELOG.md (remember to include changes affecting the API of the test artefacts too).

Firstly, it's great that you're looking at this!
We need to think through what config we want to offer, because we'll have to support it in terms of compatibility. What you propose is an improvement, but it's still not terribly flexible. Here's what I'd like in an ideal world, which we won't get to overnight:
    - type: EnvelopeEncryption
      config:
        kms: VaultKmsService
        kmsConfig:
          vaultTransitEngineUrl: http://vault.vault.svc.cluster.local:8200/v1/transit
          vaultToken: myroottoken
        - topics:  # <1, 2, 8>
            includeNames: ["encryptedTopic"]
            excludeNames: ["unencryptedTopic"]
            includeNamePrefixes: ["include_prefix_"]
            excludeNamePrefixes: ["exclude_prefix_"]
            selector: TemplateKekSelector # <3>
              selectorConfig:
              kekTemplate: "${topicName}"
            encrypt: # <4>
              record_value: true
              record_headers: true
            aad: [topic_name, batch] # <5, 7>
            cipher: aes_128_gcm_128 # <6, 7>

Only topics is a top-level thing, the selector is a property of an individual item
topics is a list. So you can have different configurations for topics beginning with foo and bar.
The selector is a property of an individual topic. This means we can evolve in the future so that topic foo is using topic-named based selector, but topic bar is using record-key based selector
In addition to specifying the kek we also can specify the fields to be encrypted. Note that this schema for the configuration should generalise quite nicely to per-field
When we support AAD we should allow to configure it on a per-topic basis
We need to allow specifying the cipher too.
Most users are quite likely to want to specify some of these settings globally (e.g. aad and cipher), which is fine. I think there per-topic ones would be overrides for whatever was global.
Ideally we would validate that the (include|exclude)Name(Prefixe)?s of two different topics can't both match. This would mean the order of the topics didn't matter (which is a nice property if topics gets long because it allows someone to safely reorganise it without the possibility of breaking things), but this is definitely a stretch goal and the lowest priority thing.

For 0.5.0 specifically I think we could consider:
    - type: EnvelopeEncryption
      config:
        kms: VaultKmsService
        kmsConfig:
          vaultTransitEngineUrl: http://vault.vault.svc.cluster.local:8200/v1/transit
          vaultToken: myroottoken
        - topics:  # <1>
            includeNames: ["encryptedTopic"]
            excludeNames: ["unencryptedTopic"]
            includeNamePrefixes: ["include_prefix_"]
            excludeNamePrefixes: ["exclude_prefix_"]
            selector: TemplateKekSelector
              selectorConfig:
              kekTemplate: "${topicName}"

I'm quite happy to add the restriction that we only support a single topic here in 0.5.0 (and it's a config error if more than one is given). But the point is that in the config schema this should be a list in 0.5.0, so we can support more than one later on without breaking compat.

cool If topics is a list of instructions about what to encrypt and how to do it, maybe it should be called something like encryptionRules (I think these are oriented around encryption only), or profiles or something like that.
Do you think we would event want to make decryption targetable like this? For decrypt it feels more like we can look into all traffic for encrypt headers. But I suppose you could tactically reduce how much work the filter needs to do if you know encryption is only applied to something like a particular topic name prefix.

cool If topics is a list of instructions about what to encrypt and how to do it, maybe it should be called something like encryptionRules (I think these are oriented around encryption only), or profiles or something like that.

I'm not wedded to the name of the property topics. But rules and profiles aren't really great either imho.

Do you think we would event want to make decryption targetable like this? For decrypt it feels more like we can look into all traffic for encrypt headers. But I suppose you could tactically reduce how much work the filter needs to do if you know encryption is only applied to something like a particular topic name prefix.

Certainly I think decrypt is going to work via headers for a while.
One thing I've shied away from so far is using knowledge on the decrypt path that's from outside the record itself. Speaking generally, it's easy to break things when a topic gets changed.
In this case, what if a proxy is initially encrypting topic foo and is later reconfigured to not encrypt it any more? In that case under your proposed optimization we would not be inspecting fetch responses for foo even for records appended during the encrypted era, so we'd pass through encrypted records.
There are other alluring optimizations we could do which are fragile in the face of changing topic config. For example, if we know a topic is not compacted, then it's trivial to encrypt the record key, and doing so won't break Kafka's semantics because for a non-compacted topic the record key is never compared on the broker. But that doesn't work when a topic is compacted. And because a topic can change between compacted and not (a request that may happen via a different proxy instance) it means we can't safely do this.
I think there are tradeoffs we can take in due course to make the decryption path less costly, but we shouldn't rush into those just yet.

This is requiring too much brain for me right now, but one point stood out.

Exclusion beats inclusion, so (include["mytopic"], exclude["mytopic"]) would result in mytopic not being selected for inclusion.

Seems like a problematic rule, I see the appeal of it, as it results in un-encrypted data being written to a topic. I think we should err on the side of encrypting data in the event of a conflict. As the encryption is reversible but unencrypted data will remain in the topic for the configured retention period and thus represent a data leek.

As Tom says it would be cool to made it a validation that each topic is is unambiguously selected. So it  might be better to invalidate if a topic name is both included or excluded. Same with the prefixes:
includePrefix: xyz
excludePrefix: xyz

is ambiguous and could be invalidated.
Might pay to be specific and say that "longer prefixes are more specific than shorter ones". So it is okay to have any combination like:
includePrefix: xy
excludePrefix: xyz

includePrefix: xyz
excludePrefix: xy

Superceded by #991


Broken OT 1.2 support in openthread/ot-nrf528xx

It looks like for retransmissions of a frame with CSL IE and security enabled are corrupted.
Since the CSL IE phase is updated after the frame was secured.
See nrf_802154_tx_started() from https://github.com/openthread/ot-nrf528xx/blob/main/src/src/radio.c#L1216

Hi @George-Stefan, thanks for spotting this. This PR should fix it: https://github.com/openthread/ot-nrf528xx/pull/149
Please notice that even after the fix the CSL IEs will be outdated for the retransmitted frames. This is a known issue and Thread Group is currently discussing a proper approach to address it.

In any case OpenThread has a workaround already for the out of sync issue: https://github.com/openthread/openthread/pull/6342


Fix typo in Deployment templating

Fixes the templating for Deployment.envFrom.secretRef
Fixes the error error converting YAML to JSON: yaml [...] did not find expected key

@JustinLex Validation Successful


use pathlib

@wolfv the metadata.py module could use more pathlib but the rest is fine with os.path b/c you are not really doing much with paths there.

Thanks!


AppBar/Toolbar Captions and Single Pass Stereo Rendering

Not sure if this is too special, but if i have enabled Single Pass Stereo Rendering to optimize the Performance i have checked that the AppBar/Toolbar Labels are only visible for one eye therefore very difficult and unpleasant to read (flickering effect).
Best Regards and big praise to your great project!
Tachoron

Yep, those are older shaders that were never updated for single pass instance rendering.  I'll look at patching them shortly.
thanks,
-pat


Made release notes output only link to latest component release

To support this change, the layout of our data was changed so that we
have per-component hierarchy rather than per-changelog so that we can
enumerate releases as well as only show the latest one per component in
the templates.

Issue: #71

@sgnn7 this would be a good PR to have an example of what the changes look like - I think I understand what's happening, but without an example / running it myself it's hard to know (and I'd love to be able to stay updated on how the output evolves).
One thing that's not clear to me from your description is whether the changes are still enumerated from all tags added since the previous suite release - does this update mean we only show the changes on the current tag, or that we include all changes but only link to the current included tag?
And to clarify, does this apply only to release notes (which for now afaik is just for the github release description in this repo) and not to the changelog of this repo?

this would be a good PR to have an example of what the changes look like

In this repo, we have pretty good test coverage so you can check the template test changes in the PR to see what it looks like but these are the direct links:

Release Notes
Changelog

One thing that's not clear to me from your description is whether the changes are still enumerated from all tags added since the previous suite release - does this update mean we only show the changes on the current tag, or that we include all changes but only link to the current included tag?

We still include all changes from version "a.b.c" to "x.y.z" as we did before in both release note and changelog. The only change here in the PR is that in the release notes instead of saying that component that was released is "a.b.c", "d.e.f", ... "x.y.z" as part of the suite, we now just say that it's "x.y.z" (the latest release we pinned).

And to clarify, does this apply only to release notes (which for now afaik is just for the github release description in this repo) and not to the changelog of this repo?

Correct. Only the release notes changed since they are the only ones talking about what components constitute the release.

Thanks! It's looking really great - but here is a question that comes to mind. The linked items are the ones that have changed in this release - but other components are also included (they just haven't changed since the last release.
What do you think is the best way to communicate that in the release notes?

The linked items are the ones that have changed in this release - but other components are also included (they just haven't changed since the last release.

Yeah this is an issue right now that we can't even start addressing without having an initial suite release since we will need logic to figure out that component "A" didn't actually change between suite v<n> and v<n+1>` :(

Would it help to create an initial RC based on the current versions tagged everywhere, and leverage that to de-risk building follow-on versions? I can see that helping with:

fully fleshing out the release notes
enable figuring out the diffs
enable testing out the script to find unreleased changes
etc

if that would help, I can dig into what to include in the first RC so that we can begin this testing - maybe we delete the RC tags later?

Would it help to create an initial RC based on the current versions tagged everywhere, and leverage that to de-risk building follow-on versions?

I think it would currently add an undue burden to include functionality that was not slated for first release. I don't think it would buy us much other than adding more work into the release that doesn't need to be there.

fully fleshing out the release notes

The release notes won't change much in output but the method for calculating what is included will. We can do this iteratively (and we probably should).

enable figuring out the diffs

There is no need to tackle diffing suite releases at this point. We could do it but I don't see why we need to front-load it since the technical risk side is mostly clear except some design decisions on how to structure the suite repo. @doodlesbykumbi - you could also chime in here to make sure I'm not missing something.

enable testing out the script to find unreleased changes

This is parallel work that doesn't require the version diffing. Also would not benefit much from front-loading.

just fyi, figuring out what's unreleased is a high priority for PM - they will be acting as release manager and feel it is critical to know what is out there that hasn't been included in a release yet
I too am looking forward to understanding better what's newly available in the suite in gh

@doodlesbykumbi the two CC failures are just CC noise:

Function componentFromRepo has 54 lines of code (exceeds 50 allowed)
Function componentFromRepo has 6 return statements (exceeds 4 allowed).


chore(spdk-rs): add an enum to be used as channel traversal context

This enum will be used to get the context about dynamic reconfiguration event happening on a device.
Based on this we'll do the minimum work required to adjust channels for this device, and not refresh for all devices.

I'm trying out a change to use the existing Ctx generic type by creating a tuple with new info I need to pass. Once that is done, we''' not need this change in spdk-rs.

I'm closing this PR as the mayastor repo changes(https://github.com/openebs/mayastor/pull/1469) are now using existing Ctx parameter for this purpose.
https://github.com/openebs/spdk-rs/pull/35#issuecomment-1647763070


Sarif support

Is your feature request related to a problem? Please describe.
SARIF is an OASIS Standard for static analysis alerts. GitHub/Azure DevOps support uploading SARIF formatted alerts.
Describe the solution you'd like
Add sarif as one of the available reporters
Additional context
https://sarifweb.azurewebsites.net/
https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/uploading-a-sarif-file-to-github
https://github.com/microsoft/sarif-azuredevops-extension

thank you, will add

The report was added in<EMAIL_ADDRESS>


Account Support

This PR introduces accounts and account isolation. Users are assigned to one account per connection and that defines their subject space.
We also introduce streams and services. These are ways to share messages across accounts with the proper permissions. Streams are pub/sub and Services are usually req/reply semantics.
We allow explicit permissions to services to also generate implicit permissions in realtime for one time use responses.
We also have support for configuration parsing.
/cc @nats-io/core

Note this work is backwards compatible, but only works for a single server. The cluster updates will be a separate PR.

Coverage decreased (-0.7%) to 91.615% when pulling b4ef7032c04085f9f7492da958d937c3c4ba4c7b on accounts into a065d13228a40dbbfc2fd7014969304f66868e37 on master.


Widget Speaking time: permission problem

Description: Users who don't have the permission to administrate the projector (Can manage the projector) see the 3-dot-menu in the new widget speaking time. The menu can be used, but content can't projected, because this is currently not working. Nevertheless it's wrong, that user can see it.
Example: 3-dot-menu on the right side

Repro:

open a meeting
open settings > list of speakers > enable the new widget
open agenda > create an item > project it
open participants: create a new user without the group delegates
log in with the new created user and open the autopilot you should see the new widget with the wrong permission

What should happen:
The three-dot-menu in the new widget should only be available for persons with the permission 'Can manage the projector'. Other user should not see it.

The user needs the "can see los" right to see the los and the speaking times.

The use of the permissions system is wrong in the speaking times component. I will add a PR to fix this.
I cannot fully test it, because of non-functional speaking times for non-superadmins.

Included in #3176


[Feature] Added System Tray App

In raising this pull request, I confirm the following (please check boxes):

[x] I have read and understood the contributors guide.
[x] I have checked that another pull request for this purpose does not exist.
[x] I have considered, and confirmed that this submission will be valuable to others.
[x] I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
[x] I give this submission freely, and claim no ownership to its content.

My familiarity with the project is as follows (check one):

[x] I have used the project briefly.

In the Readme.md, an area of improvement identified for Swag Lyrics was to add a system tray application for easy access to lyrics. I have implemented this using Infi.Systray and Tkinter in Python. I did not use electron due to issues mentioned here. If this is not the best modules to use or what you envisioned let me know and I'd be willing to redo it. I have kept the design of the monospace theme of the project. Note: the reason "cureband" made commits is that I had GitHub desktop configured for when I was working on that project. I will be adding documentation in the next commit.

Tests failed as unit tests need updating to new description.

Hello @sampoder! Thanks for updating this PR.

In the file setup.py:

Line 22:62: E231 missing whitespace after ','

In the file swaglyrics/__main__.py:

Line 32:1: W293 blank line contains whitespace
Line 90:121: E501 line too long (135 > 120 characters)
Line 104:3: E117 over-indented
Line 105:4: E117 over-indented
Line 108:4: E117 over-indented

In the file swaglyrics/systray.py:

Line 1:1: F401 'argparse' imported but unused
Line 3:1: F401 'sys' imported but unused
Line 4:1: F401 'requests' imported but unused
Line 5:1: F401 'time' imported but unused
Line 7:1: F401 'swaglyrics.cli.clear' imported but unused
Line 8:1: F401 'swaglyrics.tab.app' imported but unused
Line 9:1: F401 'swaglyrics.unsupported_txt' imported but unused
Line 9:1: F401 'swaglyrics.SameSongPlaying' imported but unused
Line 9:1: F401 'swaglyrics.version as version' imported but unused
Line 9:1: F401 'swaglyrics.backend_url' imported but unused
Line 10:1: F403 'from tkinter import *' used; unable to detect undefined names
Line 11:1: E302 expected 2 blank lines, found 0
Line 12:1: W293 blank line contains whitespace
Line 14:5: F841 local variable 'x' is assigned to but never used
Line 14:10: W291 trailing whitespace
Line 15:5: E306 expected 1 blank line before a nested definition, found 0
Line 19:22: F405 'Tk' may be undefined, or defined from star imports: tkinter
Line 20:22: F405 'Scrollbar' may be undefined, or defined from star imports: tkinter
Line 21:30: F405 'RIGHT' may be undefined, or defined from star imports: tkinter
Line 21:42: F405 'Y' may be undefined, or defined from star imports: tkinter
Line 22:20: F405 'Text' may be undefined, or defined from star imports: tkinter
Line 22:38: F405 'NONE' may be undefined, or defined from star imports: tkinter
Line 26:30: E226 missing whitespace around arithmetic operator
Line 26:37: E226 missing whitespace around arithmetic operator
Line 27:13: F405 'mainloop' may be undefined, or defined from star imports: tkinter
Line 27:23: W291 trailing whitespace
Line 31:5: E306 expected 1 blank line before a nested definition, found 0
Line 32:9: F405 'program' may be undefined, or defined from star imports: tkinter
Line 34:41: E241 multiple spaces after ','
Line 38:20: W292 no newline at end of file

In the file tests/test_main.py:

Line 84:121: E501 line too long (127 > 120 characters)
Line 96:121: E501 line too long (126 > 120 characters)
Line 118:121: E501 line too long (126 > 120 characters)
Line 136:121: E501 line too long (126 > 120 characters)

Do you have a screencast or something?

Do you have a screencast or something?

I'll share one when I get back from school (7 hrs to go) cause right now I'm on my mac

For now I'm going to work on code coverage

For now I'm going to work on code coverage

First you should focus on the product then tests :)

To-Do:

[ ] Improve Aesthetics to be more cohesive with -- tab
[ ] Package as .exe using either pyinstaller or other tool

Is this ready to review?

Yes, sorry I couldn't request a review.

Still needs fixing on the code coverage but I can do that

How can I work on this? I can't do GCI anymore this year for personal reasons but still wouldn't mind working on this.


Can't do much on the main page

I’m getting started with Solid, and I just tried logging in to the Plume app here:
https://thewebalyst.solidcommunity.net/plume/
All I’m getting is a blog title page saying:
“Plume (theWebalyst)”
The only option on the menu is “logout”. I’m not seeing any way to edit anything, If I click on the “Plume (etc)” link it briefly changes to “Blog Title” before reverting back. The only other button that works is the profile button, which does take me to my profile.
Is there something else I’m supposed to do to set this up?
If you have any time to help it would be greatly appreciated.
Thanks

No something has changed, this may be due to changes in the backend.
Thanks for reporting, I'll have a look and see if it's an easy fix.

No something has changed, this may be due to changes in the backend.
Thanks for reporting, I'll have a look and see if it's an easy fix.

If you open the browser console you will see that after a couple of minutes (ignoring all the CSS warnings and errors which also seem new), we get to this which I believe is the main problem:
HEADhttps://thewebalyst.solid.community/public/posts/
CORS Failed

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thewebalyst.solid.community/public/posts/. (Reason: CORS request did not succeed).

I'll ask on the forum if this is a known feature/issue of the server and it if is easy to fix.

If you open the browser console you will see that after a couple of minutes (ignoring all the CSS warnings and errors which also seem new), we get to this which I believe is the main problem:
HEADhttps://thewebalyst.solid.community/public/posts/
CORS Failed

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://thewebalyst.solid.community/public/posts/. (Reason: CORS request did not succeed).

I'll ask on the forum if this is a known feature/issue of the server and it if is easy to fix.

This should now be fixed so closing this. It was due to Plume looking for posts on the old server address which moved domains a couple of months ago.

This should now be fixed so closing this. It was due to Plume looking for posts on the old server address which moved domains a couple of months ago.

Hi again,
Thanks for your work on the earlier fix. I'm sorry I didn't have time to look at it until just now.
I just tried your plume instance and although the page now loads with the "How to deploy Plume blog on your Solid pod" post preview, it gives an error after trying to lode when I hit "-more-" : "- 999 undefined".
Also the "Plume Deployment Guide" in the README.md file here is directing to the old host.
I'm assuming that something in the guide would help me figure out how to configure Plume once I've uploaded it to my Solid pod. right now I have put the contents of the most recent release in a /plume/ folder in my public directory, and when I try to load https://mypodname.mypodprovider.net/plume/ I get the following:
Can't find file requested: [object Object]
So, does this need to be reopened?
Thanks again for your time

Hi again,
Thanks for your work on the earlier fix. I'm sorry I didn't have time to look at it until just now.
I just tried your plume instance and although the page now loads with the "How to deploy Plume blog on your Solid pod" post preview, it gives an error after trying to lode when I hit "-more-" : "- 999 undefined".
Also the "Plume Deployment Guide" in the README.md file here is directing to the old host.
I'm assuming that something in the guide would help me figure out how to configure Plume once I've uploaded it to my Solid pod. right now I have put the contents of the most recent release in a /plume/ folder in my public directory, and when I try to load https://mypodname.mypodprovider.net/plume/ I get the following:
Can't find file requested: [object Object]
So, does this need to be reopened?
Thanks again for your time

Yet, I'm sorry I didn't have time to test so I'll have another look tomorrow. Thanks for your patience and for again reporting back.

Yet, I'm sorry I didn't have time to test so I'll have another look tomorrow. Thanks for your patience and for again reporting back.

I've updated more URL refs and can load the deployment guidelines, but there may still be an issue editing posts when you are logged in (so I did this with https://otto-aa.github.io/solid-filemanager/ rather than Plume). Closing again for now.

I've updated more URL refs and can load the deployment guidelines, but there may still be an issue editing posts when you are logged in (so I did this with https://otto-aa.github.io/solid-filemanager/ rather than Plume). Closing again for now.

Requesting to open this again, per our discussion on  forum.solidproject.org.
Having redone the install, changing the "owners" and "postsURL" fields to include mypod.provider.tld in place of localhost:---, what I'm getting hasn't changed.
Can't find file requested: [object Object]
I'm on inrupt.net, and I've been using Solid Filemanager at otto-aa.github.io for my file operations. That has caused me some consternation, as it won't let me rename directories, or copy a directory with subdirectories. I'm wondering if that app might be part of the problem.
If there's any other info you need let me know

Requesting to open this again, per our discussion on  forum.solidproject.org.
Having redone the install, changing the "owners" and "postsURL" fields to include mypod.provider.tld in place of localhost:---, what I'm getting hasn't changed.
Can't find file requested: [object Object]
I'm on inrupt.net, and I've been using Solid Filemanager at otto-aa.github.io for my file operations. That has caused me some consternation, as it won't let me rename directories, or copy a directory with subdirectories. I'm wondering if that app might be part of the problem.
If there's any other info you need let me know

Can you include you pod URI and config.txt so I can compare with mine. Thanks.

Can you include you pod URI and config.txt so I can compare with mine. Thanks.

my instance of plume would be here:
https://thescooterking.inrupt.net/solid-plume-0.11 (as I said, I can't rename directories)
the contents of my config.txt file follows:
{
"owners": [
"https://thescooterking.inrupt.net/profile/card#me"
],
"title": "Plume (thescooterking)",
"tagline": "Weird as a dumptruck",
"picture": "img/logo.svg",
"fadeText": true,
"showSources": true,
"cacheUnit": "days",
"defaultPath": "public/posts",
"postsURL": "https://thescooterking.inrupt.net/public/posts/",
"postsElement": ".posts",
"loadInBg": true
}

my instance of plume would be here:
https://thescooterking.inrupt.net/solid-plume-0.11 (as I said, I can't rename directories)
the contents of my config.txt file follows:
{
"owners": [
"https://thescooterking.inrupt.net/profile/card#me"
],
"title": "Plume (thescooterking)",
"tagline": "Weird as a dumptruck",
"picture": "img/logo.svg",
"fadeText": true,
"showSources": true,
"cacheUnit": "days",
"defaultPath": "public/posts",
"postsURL": "https://thescooterking.inrupt.net/public/posts/",
"postsElement": ".posts",
"loadInBg": true
}

Your config looks good. I'm not sure it will be an issue for you, but if I try to load https://thescooterking.inrupt.net/solid-plume-0.11 I find it isn't public so I can't load the app to look at the error myself.
I think making the solid-plume-0.11 directory public should be enough so try that, and if the problem persists and let me know.

Your config looks good. I'm not sure it will be an issue for you, but if I try to load https://thescooterking.inrupt.net/solid-plume-0.11 I find it isn't public so I can't load the app to look at the error myself.
I think making the solid-plume-0.11 directory public should be enough so try that, and if the problem persists and let me know.

I think making the solid-plume-0.11 directory public should be enough so try that, and if the problem >persists and let me know.

I just tried loading my site with .../public/solid-plume-0.11/ and it worked.
... I'll just go sit in the corner and think about what I've done...
You can close this now. Thanks.

I think making the solid-plume-0.11 directory public should be enough so try that, and if the problem >persists and let me know.

I just tried loading my site with .../public/solid-plume-0.11/ and it worked.
... I'll just go sit in the corner and think about what I've done...
You can close this now. Thanks.

Glad you figured out out. Good luck with your new blog!
And you're done with that, feel free to have a go at https://dweb.happybeing.com and see How to set up your own dWeb Blog :wink:.

Glad you figured out out. Good luck with your new blog!
And you're done with that, feel free to have a go at https://dweb.happybeing.com and see How to set up your own dWeb Blog :wink:.


Atomic puppy should read /forward/20 on startup

Atomic puppy should read streams/mystream//forward/20 when starting, not backward.

:+1: although building our own URIs is a hack and one day it will break :D

Is this still an issue?


Implement Node Generator Module for vllm Serving API Integration

Purpose of Development

When using the existing vllm module, each test requires model reinitialization, leading to significant test time overhead.
By enabling API-based connections, similar to the OpenAI module, model reinitialization time can be saved, improving testing efficiency.

Testing Instructions

Start the vllm serving server:
vllm serve Qwen/Qwen2.5-14B-Instruct-AWQ -q awq --port 8012

Here is sample of evaluate_config.yaml file.
    - node_type: generator
      strategy:
         metrics:
             - metric_name: rouge
       modules:
             - module_type: vllm_api
               uri: http://localhost:8012
               llm: Qwen/Qwen2.5-14B-Instruct-AWQ
               temperature: [0, 0.5]
               max_tokens: 400

Execute the evaluation process.

@korjsh Hello! Thanks for the contribution.
Before merging, we have to make a two more things.

The test code. You should make a test code at the tests/autorag/nodes/generator
The docs. You should make a new documentation at docs/source/nodes/generator

If you feel overwhelmed to make the test code and docs, we can cover it.
If you want the PR merge faster, it is always great to do it yourself.
Thanks a lot :)


Error accessing the Dashboard

I get this error after trying to add the LatestUsers widget to the dashboard.
I even tried to remove the widget and clear the artisan cache but nothing seems to work.
I can access all other pages I have created.
TypeError
Phpsa\FilamentAuthentication\Widgets\LatestUsersWidget::getTableQuery(): Return value must be of type Illuminate\Contracts\Database\Eloquent\Builder, Illuminate\Database\Eloquent\Builder returned (View: C:\laragon\www\Laravel-Test\vendor\filament\filament\resources\views\components\widgets.blade.php)
Thanks

Can you advise PHP & Laravel Version

Can you confirm if the latest version fixes this,
issue around laravel 9 vs 8 was found
also to disable should be a config variable now and not needed to manually add to the config file anymore

Ran composer update on the installation and this resolved the problem.
Thanks for the help


Upgrade to DNN 9.11.0: Search broken on FIPS enabled systems

Description of bug
After upgrading to DNN 9.11.0 from 9.10.1 the search is broken on FIPS enabled systems.  It looks like something is using MD5 per the exception text when it shouldn't in a FIPS compliant environment.
Steps to reproduce
List the precise steps to reproduce the bug:

Windows server with FIPS compliance enabled
Upgrade existing DNN 9.10 system to 9.11
Doing a search returns no results but will log an exception
Doing a search re-index doesn't run but will log an exception
See error

Current behavior
Doing a search returns no results and attempting to re-index the website fails both dropping exceptions in the logs.  When the scheduler runs the search crawl it throws exceptions too.
Error information
AbsoluteURL:
DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
ExceptionGUID:c053665e-e300-40d7-820c-1a7b795139d3
AssemblyVersion:
PortalId:-1
UserId:-1
TabId:-1
RawUrl:
Referrer:
UserAgent:
ExceptionHash:oVoRwz/44xNPaHBu2oFFcOe6kOI=
Message:The type initializer for 'Lucene.Net.Store.FSDirectory' threw an exception.
StackTrace:
   at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.get_Writer()
   at DotNetNuke.Services.Search.Internals.LuceneControllerImpl.Delete(Query query)
   at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteSearchDocumentInternal(SearchDocument searchDocument, Boolean autoCommit)
   at DotNetNuke.Services.Search.Internals.InternalSearchControllerImpl.DeleteAllDocuments(Int32 portalId, Int32 searchTypeId)
   at DotNetNuke.Services.Search.SearchEngine.DeleteOldDocsBeforeReindex()
   at DotNetNuke.Services.Search.SearchEngineScheduler.DoWork()
InnerMessage:System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation.
---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms. at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
--- End of inner exception stack trace
--- at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) at System.Reflection.Ru
InnerStackTrace:
   at Lucene.Net.Store.FSDirectory..cctor()
Source:DotNetNuke
FileName:
FileLineNumber:0
FileColumnNumber:0
Method:

Additional context
Verified the App_Data\FipsCompilanceAssemblies\Lucene.Net.dll was correctly in the bin\ folder already.  I used a compare tool and saw that the 9.11.0 DLL is actually identical to what was there from 9.10.1 so the issue is likely not in that DLL but somewhere else?
Affected version

[ ] 10.00.00 alpha build
[X] 09.11.00
[ ] 09.10.02
[ ] 09.10.01

Affected browser

[ ] Chrome
[ ] Firefox
[ ] Safari
[ ] Internet Explorer 11
[ ] Microsoft Edge (Classic)
[ ] Microsoft Edge Chromium

The FIPS compliant encryption provider was never FIPS compliant because of the very reason this feature is broken.  The chosen algorithm isn't what FIPS expects.
More details can be seen in this README:
https://github.com/UpendoVentures/Dnn.FipsAesCryptoProvider#readme

I understand what's there about Triple DES vs AES but the issue being kicked out here causing the exception is the use of MD5.  Even if not for FIPS compliance MD5 should have been replaced with SHA.  We've been running in Windows FIPS mode for a very long time and it was working in every version of DNN 8/9 we've installed on our websites until 9.11.0.

DNN Platform has not changed anything with Lucene.net in many years. Perhaps there was an issue during the upgrade with copying the FIPS assembly into the bin folder. Have you tried copying that assembly from the App_Data\FipsCompilanceAssemblies into the bin?

I did verify the App_Data\FipsCompilanceAssemblies version of the file was in the bin folder.  It's slightly larger than the non-FIPS one.
I did a fresh install and it works under FIPS enforced mode but the upgraded website does not.  Are there some other DLLs I can look to verify they're correct?

@brentil Are you on Evoq by chance?  Also, do you have any third-party search modules installed or anything that may have modified Lucene?

@brentil Are you on Evoq by chance? Also, do you have any third-party search modules installed or anything that may have modified Lucene?

@mitchelsellers we are no using Evoq, just the normal DNN.  We do not have and 3rd party search modules installed or modified Lucene.  This happens to us on a default fresh DNN installation.  We ended up having to makes changes to the specific IIS websites running the DNN installs to disable FIPS for their applications.  I have not tested again with 9.12 though.

We had a client in a FIPS environment run a test on 9.12.0 and they had no issues.

[like]  Jeremy Farrance reacted to your message:

From: David Poindexter @.>
Sent: Tuesday, September 19, 2023 9:58:24 PM
To: dnnsoftware/Dnn.Platform @.>
Cc: Subscribed @.***>
Subject: Re: [dnnsoftware/Dnn.Platform] Upgrade to DNN 9.11.0: Search broken on FIPS enabled systems (Issue #5344)
We had a client in a FIPS environment run a test on 9.12.0 and they had no issues.
—
Reply to this email directly, view it on GitHubhttps://github.com/dnnsoftware/Dnn.Platform/issues/5344#issuecomment-1726597642, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAE7P5KXAPAFOMI5PO7GYXTX3IIQBANCNFSM6AAAAAARIKR3PQ.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

We had a client in a FIPS environment run a test on 9.12.0 and they had no issues.

When DNN 9.13.0 final drops I will run through testing with it.

We had a client in a FIPS environment run a test on 9.12.0 and they had no issues.

When DNN 9.13.0 final drops I will run through testing with it.

@brentil thanks for the offer to test.  Please test with DNN 9.13.0-rc3 so that any potential bugs can be resolved before the official release of 9.13.0.


Performance problems with API

Hi
maybe I'm alone with this problem, but since November 29th I've started noticing strange problems. Toyota API often returns HTTP 429 answer on vehicleStatus endpoint. Problem didn't stopped even after implementing strong throttling, and it looks that API has performance problems. In the same time application works correctly, and I'm just wondering if Toyota hasn't changed its API endpoints to new ones with the application (while leaving old ones scaled down for older application instances). Last update for the application was on November 18th.
Do you have an option to verify traffic generated from the application? I have locked phone :(.

Hi @Iture,
You are not the only one. I'm also having problems since November 29th.
I'm receiving: 'ToyotaApiError':'HTTP: 429 - Too Many Requests. Please try again later.'
I already created a ticket  on my own plugin that is using mytoyota, as I was not sure if it applies to mytoyota in general or only my own plugin.
Based on your problem report, I do expect that we are observing the same. I didn't have time yet to further investigate the problem. It could indeed be that toyota has changed to other servers. The strange thing is that the mytoyota app on my phone is still working correctly, and doesn't seem to be influenced.
There certainly is something going on....

The version of the MyT app on my phone as of now is: "Version 4.14.0 (30167)"

Your hypothesis seems valid to me, this sounds very plausible.
I'm also searching on internet fora, if other users are seeing the same problem. Cannot find any clear report yet.
There however also seems to have been some problem in the last week of October. At that moment my car was not registered anymore, and I had to re-register it in the Toyota MyT App I now understand that more people have had that problem at the end of October. Did you also have to re-register it in the MyT App?
I'm sadly also not able to monitor the network traffic, so I cannot check the address of the servers.

I already tried to update the "X-TME-APP-VERSION" to "4.14.0", to determine if it fixes the problem. No, it isn't. 😒

It is really strange:
I just generated curl commands print ('curl -H "Cookie:%s" -H "uuid:%s" %s' % (headers['Cookie'],self.uuid,url))
in the controller.request method and they are working flawlessly. Event more - i tried to isssue single request to single endpoint: await client.api.get_vehicle_status_legacy_endpoint(vin) and got the same 429 error.
Even tried older versions of httpx, no success
Running out the ideas.

I've got something:

when I'm issuing 100 requests sequentially (from request module) everything works
when I'm issuing one request using httpx client, got 429
and the best: making the same 100 request with aiohttp library works

Absolutely no idea why, but t looks that problem lies somewhere in the httpx module

I've got a solution: set user-agent header. It looks that Toyota introduced some protection mechanism, and discards unknown user-agents. Adding user-agent header (I just set it to the same value as my browser), helped imediately

@Iture Awesome job finding out how to fix this!! 🚀 🙇
Funny enough I actually choose httpx back when I started because aiohttp didn't work with toyota's servers. 😆

It works, new versions have been released! Including a legacy version for the HA integration.
Again, thanks for the detective work @Iture It is much appreciated 🚀


[bug] Broken in ComfyUI Frontend 1.5.7+

Describe the bug
I'm still investigating as the issue solved in b0d52f73051368df6de2d1e10ad28ca56df72803 was just something that failed without blocking anything before, but now I get

First report of the issue:
https://github.com/Comfy-Org/ComfyUI_frontend/issues/1834
Reproduction
No response
Expected behavior
No response
Operating System
Windows (Default)
Comfy Mode
In a custom virtual env (venv, virtualenv, conda...)
Console output
No response
Additional context
No response

@huchenlei does this ring a bell? This comes from my documentation system

[!WARNING]
Bug identified upstream, it's in the internationalization combined with mtb note+ and mtb's documentation system.

solved in https://github.com/Comfy-Org/ComfyUI_frontend/pull/1838 (details there ;) )


Update StuyLib to 2023

bro your spotless update completely changed the formatting and makes the PR impossible to review


Check for ActiveRecord in subject

Checks for ActiveRecord to fix #672
Also address #676

Is new tag pushed for this?


provide sd/card  and notification download sample in demo

ok. I will provide such demos as soon as possible.

This demo will be provided before release 1.0.0.


Fix broken Table of contents links on Q&A with RAG page

Summary
Fix broken Table of contents links on the Q&A with RAG page. Also added a new link for the Citations page.
Side note: I don't know where the page is for the Per-user retrieval link. I can update this if someone points me to the right page.

Thank you!

"Per user retrieval" would probably tie in best here:
https://js.langchain.com/docs/use_cases/chatbots/memory_management
But let's merge this first

Oh hmm actually we are missing that page in JS. @bracesproul do you know why? I think you looked at this last.


lack of UI during long time waiting before the first video frame was rendered

Required Info

Host Operating System & Version
{Ubuntu 20.04.2}

Kernel Version (Linux Only)
(5.x)

Branch
{ kantv }

Android Studio Version
4.2.1

NDK Version
NDK-r14b

Xcode Version
12.5

Language
{C }

Section
{ HLS }

Issue Description
black screen during long time waiting before the first video frame was rendered
How to reproduce the issue

open online TV https://biglife.sinclair.wurl.com/manifest/3000.m3u8 ( Big Life TV - English )

launch playback

long time black screen before the first video frame was rendered
Root cause
TBD
anyway, UI status should be added during long time waiting to improve APK's user experience

this issue is similar/equivalant with #19  actually


VP indicator how width works?

Which version are you running? The lastest version is on Github. Pip is for major releases.
import pandas_ta as ta
print(ta.version)

Upgrade.
$ pip install -U git+https://github.com/twopirllc/pandas-ta

I'm calculating VP over 50 candles of 1h.
I don't understand how width works in VP indicator. I run a test with different width values (1,2,3 and 10). Check my output and pay attention to "close high". Are this VP values right?
To Reproduce
vp1=df.ta.vp(width=1)
vp2=df.ta.vp(width=2)
vp3=df.ta.vp(width=3)
vp10=df.ta.vp(width=10)
print(df)
print(vp1)
print(vp2)
print(vp3)
print(vp10)
OUTPUT
timestamp    open    high     low   close        volume
0   2020-12-31 16:00:00.000000  739.88  742.00  737.36  738.83   14810.28022
1   2020-12-31 17:00:00.000000  738.76  744.50  737.61  743.96   14700.26345
2   2020-12-31 18:00:00.000000  743.96  745.00  736.52  738.24   18490.32151
3   2020-12-31 19:00:00.000000  738.23  742.50  735.88  740.48   11375.60510
4   2020-12-31 20:00:00.000000  740.46  741.70  731.83  736.42   19450.08215
5   2020-12-31 21:00:00.000000  736.42  739.00  729.33  734.07   27932.69884
6   2020-12-31 22:00:00.000000  734.08  749.00  733.37  748.28   52336.18779
7   2020-12-31 23:00:00.000000  748.27  749.00  742.27  744.06   33019.50100
8   2021-01-01 00:00:00.000000  744.06  747.23  743.10  744.82   17604.80859
9   2021-01-01 01:00:00.000000  744.87  747.09  739.30  742.29   18794.15424
10  2021-01-01 02:00:00.000000  742.34  743.23  739.50  740.65   14948.26447
11  2021-01-01 03:00:00.000000  740.72  743.25  737.04  739.97   17106.99495
12  2021-01-01 04:00:00.000000  739.87  740.51  734.40  737.38   21624.68945
13  2021-01-01 05:00:00.000000  737.37  738.48  725.10  730.07   52992.04892
14  2021-01-01 06:00:00.000000  730.07  734.77  728.77  733.68   22836.46973
15  2021-01-01 07:00:00.000000  733.69  738.87  733.27  736.81   22895.59711
16  2021-01-01 08:00:00.000000  736.82  741.76  736.11  738.85   29384.09871
17  2021-01-01 09:00:00.000000  738.85  743.33  732.12  733.19   50190.47228
18  2021-01-01 10:00:00.000000  733.19  741.99  733.00  740.08   23543.56362
19  2021-01-01 11:00:00.000000  740.08  742.67  736.46  738.00   22098.37395
20  2021-01-01 12:00:00.000000  738.01  740.00  733.50  735.39   25671.61199
21  2021-01-01 13:00:00.000000  735.39  737.73  733.01  735.83   22249.34205
22  2021-01-01 14:00:00.000000  735.76  736.45  726.57  727.94   40914.26505
23  2021-01-01 15:00:00.000000  727.94  731.80  714.29  724.60   66427.75355
24  2021-01-01 16:00:00.000000  724.57  728.28  720.95  725.34   26866.35862
25  2021-01-01 17:00:00.000000  725.34  730.71  722.50  729.48   22422.29118
26  2021-01-01 18:00:00.000000  729.48  730.61  726.69  728.23   14582.15316
27  2021-01-01 19:00:00.000000  728.23  731.97  725.65  728.90   14614.20353
28  2021-01-01 20:00:00.000000  728.97  730.58  727.65  728.91   14058.19051
29  2021-01-01 21:00:00.000000  728.91  730.66  716.26  719.90   46190.17553
30  2021-01-01 22:00:00.000000  719.90  731.75  714.91  729.38   37985.46001
31  2021-01-01 23:00:00.000000  729.39  734.40  729.05  729.44   21870.25220
32  2021-01-02 00:00:00.000000  729.45  731.96  728.40  730.39   13138.56186
33  2021-01-02 01:00:00.000000  730.39  730.67  726.26  729.45   13117.64933
34  2021-01-02 02:00:00.000000  729.45  733.40  729.22  731.99   19342.91315
35  2021-01-02 03:00:00.000000  731.99  740.49  730.53  737.04   41590.31856
36  2021-01-02 04:00:00.000000  737.08  738.66  733.07  735.12   23887.39609
37  2021-01-02 05:00:00.000000  735.12  738.35  728.21  733.84   32631.45363
38  2021-01-02 06:00:00.000000  733.84  734.64  723.06  725.41   38970.42653
39  2021-01-02 07:00:00.000000  725.24  733.93  723.01  728.47   34642.76548
40  2021-01-02 08:00:00.000000  728.55  731.10  727.17  729.70   14020.08545
41  2021-01-02 09:00:00.000000  729.70  757.00  728.25  752.38<PHONE_NUMBER>0
42  2021-01-02 10:00:00.000000  752.39  772.80  749.11  770.77<PHONE_NUMBER>7
43  2021-01-02 11:00:00.000000  770.77  771.28  753.00  760.94   88376.02018
44  2021-01-02 12:00:00.000000  760.99  768.99  760.86  768.43   51945.86127
45  2021-01-02 13:00:00.000000  768.45  782.98  764.50  781.94<PHONE_NUMBER>1
46  2021-01-02 14:00:00.000000  781.94  784.66  774.04  778.84   74461.65986
47  2021-01-02 15:00:00.000000  778.77  784.39  772.00  780.01   57755.77853
48  2021-01-02 16:00:00.000000  780.00  787.69  776.77  784.79   56561.31490
49  2021-01-02 17:00:00.000000  784.79  785.48  750.12  756.55<PHONE_NUMBER>5
low_close  mean_close  high_close    pos_volume    neg_volume  total_volume
0      719.9    740.7906      784.79  1.228753e+06<PHONE_NUMBER>9  1.976821e+06
low_close  mean_close  high_close    pos_volume    neg_volume  total_volume
0      724.6    737.1692      748.28<PHONE_NUMBER>6<PHONE_NUMBER>8  6.882638e+05
1      719.9    744.4120      784.79<PHONE_NUMBER>6<PHONE_NUMBER>1  1.288557e+06
low_close  mean_close  high_close    pos_volume    neg_volume  total_volume
0     730.07  739.344706      748.28<PHONE_NUMBER>9<PHONE_NUMBER>4  4.103021e+05
1     719.90  730.261765      740.08<PHONE_NUMBER>3<PHONE_NUMBER>9  4.759407e+05
2     725.41  753.513750      784.79<PHONE_NUMBER>0<PHONE_NUMBER>6  1.090578e+06
low_close  mean_close  high_close    pos_volume    neg_volume  total_volume
0     736.42     739.586      743.96   52750.68388   26075.86855   78826.55243
1     734.07     742.704      748.28   99063.04087   50624.30959<PHONE_NUMBER>6
2     730.07     736.350      740.65   91723.73332   37784.73420<PHONE_NUMBER>2
3     733.19     737.386      740.08<PHONE_NUMBER>0   45641.93757<PHONE_NUMBER>7
4     724.60     729.820      735.83<PHONE_NUMBER>9   49115.70067<PHONE_NUMBER>6
5     719.90     727.084      729.48   60804.37906   51062.63485<PHONE_NUMBER>1
6     729.38     730.130      731.99   19342.91315   86111.92340<PHONE_NUMBER>5
7     725.41     731.976      737.04<PHONE_NUMBER>2   58530.16157<PHONE_NUMBER>9
8     729.70     756.444      770.77<PHONE_NUMBER>7<PHONE_NUMBER>0<PHONE_NUMBER>7
9     756.55     776.426      784.79<PHONE_NUMBER>6<PHONE_NUMBER>9<PHONE_NUMBER>5

Check that total total volume is diferent with each width, for example with width=1 for high_close=784.79 total_volume=  1.976821e+06 and with width=2 total_volume=1.288557e+06.
I think this issue is relationated with the array_sort() by close

Check that total total volume is diferent with each width, for example with width=1 for high_close=784.79 total_volume=  1.976821e+06 and with width=2 total_volume=1.288557e+06.
I think this issue is relationated with the array_sort() by close

Hello @casterock,
Thanks for trying Pandas TA.
When you have some time, please check out How to plot Volume Profile? Issue #74. Hopefully that may address your question. If not, we can go from there. If it is inaccurate and you know how to make it better, I would greatly appreciate a PR.
Hope this helps.
Thanks,
KJ

Hello @casterock,
Thanks for trying Pandas TA.
When you have some time, please check out How to plot Volume Profile? Issue #74. Hopefully that may address your question. If not, we can go from there. If it is inaccurate and you know how to make it better, I would greatly appreciate a PR.
Hope this helps.
Thanks,
KJ

Hello @casterock,
I assume the suggestion in Issue #74 was sufficient. Thus I will be closing this Issue in a few days. If you are still having Issues, reopen it and we can go from there.
Thanks,
KJ

Hello @casterock,
I assume the suggestion in Issue #74 was sufficient. Thus I will be closing this Issue in a few days. If you are still having Issues, reopen it and we can go from there.
Thanks,
KJ


PEP 740: Post-deployment tasks

The main roadmap for PEP 740 is in https://github.com/pypi/warehouse/issues/15871; this tracks related items that aren't blockers, but need to be thought about more and/or addressed in the medium-to-long term.

[ ] Support for other attestation types. Right now the "PyPI Publish" and SLSA types are supported, although the SLSA type is currently gated off since nothing is uploading it yet. The latter should be enabled.
[ ] Evaluate additional forms of domain separation in the attestation body. Right now there's a scenario in which a single workflow identity can sign publish attestations for both PyPI and TestPyPI, and those two attestations are indistinguishable (since a publish attestation doesn't currently encode its intended "recipient" index). This leaves open a subset of index poisoning attacks, where an attacker manages to obtain attestations intended for TestPyPI and gets PyPI to serve them instead. @alex and I originally discussed this ~2 years ago and the original approach within Fulcio itself didn't pan out, so it needs to be tackled within the attestation body itself.

The solution to this is to encode a domain separator in the attestation payload, which could be as simple as the current OIDC audiences for PyPI and TestPyPI (pypi and testpypi respectively). We have a strong source of timeliness in the form of signed time, so we could add these and then require them in new attestations after a period of adoption.

[ ] Enable attestation support for other Trusted Publisher providers, e.g. GCB and ActiveState. This should be straightforward, just needs tests.

Support for other attestation types. Right now the "PyPI Publish" and SLSA types are supported, although the SLSA type is currently gated off since nothing is uploading it yet. The latter should be enabled.

Is it possible to do this in a job following pypi-upload?

Support for other attestation types. Right now the "PyPI Publish" and SLSA types are supported, although the SLSA type is currently gated off since nothing is uploading it yet. The latter should be enabled.

Is it possible to do this in a job following pypi-upload?

Not at the moment -- in principle we could add a separate upload endpoint/codepath for uploading attestations to an already-uploaded release, but that doesn't exist yet. For the time being, the assumption is that one or more attestations get uploaded with the release itself, so a user who wants to upload a SLSA attestation should put it in their dist/ alongside their publish attestation.
In other words, a dist/ structure like:
dist/
  foo-1.2.3.tar.gz
  foo-1.2.3.tar.gz.publish.attestation
  foo-1.2.3.tar.gz.slsa.attestation

(The interstitial .publish. and .slsa aren't semantically meaningful -- twine just looks for dist.*.attestation).

@woodruffw so I'm usually structuring my workflows to do any mutations post initial PyPI publish. That's my point of no return. Besides, the official SLSA automation for GHA is a reusable workflow. So running it before publishing would be a separate job with a hope that dists will get uploaded eventually, which may not happen in case of release rejection. This is my primary motivation for uploading attestations post-release (which could be useful in tandem with the very old request to have draft releases for transactional uploads).
By the way, I've researched a little how the attestations are uploaded to GH: https://github.com/pypa/gh-action-pypi-publish/issues/288.


Render Image inside MD content

Does this support image rendering?
I'm trying to render this content inside the component. It renders the text, however, it does not render the image. Doe it support image rendering?
MD Content:
This is a sample text for rn-mdx

![React Native Picture](https://upload.wikimedia.org/wikipedia/commons/thumb/a/a7/React-icon.svg/120px-React-icon.svg.png)

I just saw the source code, inside my MD content, I saw instead of using
![React Native Picture](path-to-img.png)

I had to use
<img src="path-to-img.png" alt="React Native Picture" />

Closing this issue.


AppCenter.Start() rises an exception

Hello,
When I try to call AppCenter.Start("androidkey", typeof(Push)) from App.xaml.cs I get the following error on Android;
Java.Lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Resources android.content.Context.getResources()' on a null object reference

@Disjes The comments feature of our documentation is intended to enable customers to suggest changes to the docs or ask clarifying questions about the docs.
App Center support is provided directly from within the App Center portal. Any time you need help, just click the blue chat button in the lower-right corner of any page and our dedicated support team will respond. For additional information, see the App Center Help Center.


Split Axis into two classes? SpatialAxis and Axis?

The problem is that there many cases in which the Axis needs to be spatial, so that has to be checked.
Might be nice to let the type system express that directly.
See Util.mustBeSpatial(Axis), which has 13 references at present.

Not so sure about this one. May create the issue of moving between types, which may be even more annoying.


cleanup deprecated code and bump bitcoin core version

closing in favor of https://github.com/Start9Labs/lightning-terminal-startos/pull/17


We've made several changes to this code with rippled 1.1.1 which I believe should address this issue. I'm closing it, but if you continue having problems, please feel free to reopen.

We've made several changes to this code with rippled 1.1.1 which I believe should address this issue. I'm closing it, but if you continue having problems, please feel free to reopen.

excuse me, I meet the same problem New quorum of<PHONE_NUMBER>3709551615 exceeds the number of trusted validators
the detail info in debug.log is as follow:
2019-Jan-14 23:37:36.676261277 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 16698ms
2019-Jan-14 23:37:36.676282620 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 19580ms
2019-Jan-14 23:37:36.676443416 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 13696ms
2019-Jan-14 23:37:36.676523252 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 7694ms
2019-Jan-14 23:37:36.676569343 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 10696ms
2019-Jan-14 23:37:36.676671027 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 1693ms
2019-Jan-14 23:37:36.676684432 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 4692ms
2019-Jan-14 23:45:31.170064459 Peer:WRN [325056] onReadMessage: Connection reset by peer
2019-Jan-14 23:47:25.541382117 LoadMonitor:WRN Job: processLedgerData run: 10764ms wait: 0ms
2019-Jan-14 23:47:25.541496212 LoadMonitor:WRN Job: InboundLedger run: 0ms wait: 8367ms
2019-Jan-14 23:47:25.541525938 LoadMonitor:WRN Job: processLedgerData run: 10360ms wait: 0ms
2019-Jan-14 23:47:25.573421814 LoadMonitor:WRN Job: InboundLedger run: 32ms wait: 7866ms
2019-Jan-14 23:47:25.573432698 LoadMonitor:WRN Job: InboundLedger run: 32ms wait: 4829ms
2019-Jan-14 23:51:13.438445475 LoadMonitor:WRN Job: processLedgerData run: 1389ms wait: 0ms
2019-Jan-14 23:51:13.438548683 LoadMonitor:WRN Job: processLedgerData run: 0ms wait: 1229ms
2019-Jan-14 23:51:13.438597187 LoadMonitor:WRN Job: processLedgerData run: 1448ms wait: 0ms
2019-Jan-14 23:51:27.901913617 Peer:WRN [325098] onReadMessage: Connection reset by peer
2019-Jan-15 00:00:00.235820248 ValidatorList:WRN New quorum of<PHONE_NUMBER>3709551615 exceeds the number of trusted validators (0)
2019-Jan-15 00:00:22.243129908 NetworkOPs:WRN We are not running on the consensus ledger
2019-Jan-15 00:00:22.243207871 ValidatorList:WRN New quorum of<PHONE_NUMBER>3709551615 exceeds the number of trusted validators (0)
2019-Jan-15 00:00:22.243263837 LedgerConsensus:WRN Need consensus ledger 4059DF5BA121A44C3F19AD366E9B77A375385D8AA0892CE255E8AACDCFAAB123
2019-Jan-15 00:00:23.247307864 LedgerConsensus:WRN View of consensus changed during open status=open,  mode=wrongLedger
2019-Jan-15 00:00:23.247352930 LedgerConsensus:WRN 4059DF5BA121A44C3F19AD366E9B77A375385D8AA0892CE255E8AACDCFAAB123 to DDFBFD8C6E372C52A1787557E5236EE0444A25255D16CF900B5F4EC4B1D890FC
2019-Jan-15 00:00:23.247404692 LedgerConsensus:WRN {"accepted":true,"account_hash":"B13D1AD764F1DD3253127A3DA02C6141B9093A2A7986B8E9940CE9143C995767","close_flags":0,"close_time":600825620,"close_time_human":"2019-Jan-15 00:00:20.000000000","close_time_resolution":10,"closed":true,"hash":"DDFBFD8C6E372C52A1787557E5236EE0444A25255D16CF900B5F4EC4B1D890FC","ledger_hash":"DDFBFD8C6E372C52A1787557E5236EE0444A25255D16CF900B5F4EC4B1D890FC","ledger_index":"16090546","parent_close_time":600825601,"parent_hash":"E7FA10FF2E422A41A5B4437422029B9265C6B60491A3C6043F182CCB32D50160","seqNum":"16090546","totalCoins":"99997075910029940","total_coins":"99997075910029940","transaction_hash":"0000000000000000000000000000000000000000000000000000000000000000"}

you can see that, before 2019-Jan-14 23:51:13 everything is ok, and my node can receive and persist the closed ledger normally.
but at 2019-Jan-14 23:51:27 the Peer:WRN [325098] onReadMessage: Connection reset by peer message happen, and then at 2019-Jan-15 00:00:00 it tell me New quorum of<PHONE_NUMBER>3709551615 exceeds the number of trusted validators, and at 2019-Jan-15 00:00:23, my node is at  View of consensus changed during open status=open,  mode=wrongLedger, after that my node can only receive closed ledger but cannot sync it.
my node is run at ubuntu18.04 in testnet with rippled 1.1.1
I have restart the node, and lose all the ledger I have sync, can you tell me how to avoid this problem?
Originally posted by @hippo-dalaoshe in https://github.com/ripple/rippled/issues/2611#issuecomment-456638545

I suspect this was caused by lack of peer connections on the test net. If you don't have enough peer connections who are on the same net as you (i.e. not "insane") then it can be hard for your server to stay synced.
If you are behind a firewall and you don't open the peer protocol port (51235 by default), then you can only rely on outbound peers, who tend to be busier and may drop you as a peer. It's also possible you may end up connected to test net peers only when you want to be on the main net, or vice versa (look for "insane in the peers response)
So two actions you can take to reduce connectivity-related problems are:

Make sure you configure port forwarding in your firewall. (It can help to restart your server afterward, since that'll prompt it to look for new peers including ones who can now connect to you.) After you do this, you should see some "type": "in" peers in the Peer Crawler response.
Actively manage your peers, for example with a script such as rbh

Anyway, this issue hasn't been updated in a while, so I'm closing it as stale, but feel free to reopen if you are still having problems.


ARROW-14016: [C++] Wrong type_name used for directory partitioning

Trivial change to fix the type_name provided by DirectoryPartitioning. It appears to have been left from when it was called SchemaPartitioner. See: https://github.com/apache/arrow/pull/6153

Looks some tests also need to fix.
e.g., https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/builds/40797296/job/7iantqaoaltgbmig#L2138
https://github.com/apache/arrow/pull/11172/checks?check_run_id=3624000341#step:8:2620


Imx708 test fixes

A couple of tests were failing with the imx708 because it makes images wider than the GPU can handle.

Ah, that's failed again. I guess I need to do a rebase and then re-push.


FAIL: TestWorkflowShutdownStrategy/TerminateStrategy

FAIL: TestWorkflowShutdownStrategy/TerminateStrategy is flake
https://github.com/argoproj/argo-workflows/runs/2071978101

Close?


Add --debug option

To help with customer support, this PR adds a --debug option to log the following info:

path of loaded config files
command line arguments
filename and filemode (added, removed, modified) of scanned documents
sha of scanned commits
scan exit code

Codecov Report

Merging #290 (5fd709d) into main (e81fedb) will decrease coverage by 0.30%.
The diff coverage is 73.68%.

@@            Coverage Diff             @@
##             main     #290      +/-   ##
==========================================
- Coverage   93.66%   93.36%   -0.31%
==========================================
  Files          62       62
  Lines        2511     2546      +35
==========================================
+ Hits         2352     2377      +25
- Misses        159      169      +10

Flag
Coverage Δ

unittests
93.36% <73.68%> (-0.31%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ggshield/scan/scannable.py
93.56% <54.54%> (-2.69%)
:arrow_down:

ggshield/cmd/main.py
91.52% <78.94%> (-6.15%)
:arrow_down:

ggshield/core/config/user_config.py
90.41% <87.50%> (-0.36%)
:arrow_down:

Continue to review full report at Codecov.

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


Avoid install script crashing on Yarn

The version check added in https://github.com/lovell/sharp/commit/d406cb619c9a9db336f138b58bfde267e573e1ce expects process.env.npm_package_engines_node to exist. Yarn 2 (not sure about v1) doesn't expose fields from package.json like npm does, so the build instantly fails, rendering 0.26.1 uninstallable.
I've added a fallback that reads and parses package.json directly if the expected variable isn't found.

Coverage remained the same at 100.0% when pulling 8e0bb3755bf1a83697e9a679569cbb18d9237ce5 on jalovatt:fix-yarn-engines into c4c43d525bbf22f0b7700f539bfcfdcb33999037 on lovell:master.

Thanks for the PR. Could we perhaps simplify this with something like the following?
- process.env.npm_package_engines_node
+ process.env.npm_package_engines_node || require('../package.json').engines.node

Thanks for the PR. Could we perhaps simplify this with something like the following?
- process.env.npm_package_engines_node
+ process.env.npm_package_engines_node || require('../package.json').engines.node

Done. I've been working with ES modules for so long that I forgot we could pull JSON files in that way; good call. :)

Thank you!


Make metadata available at runtime

Here is a draft of an idea I have had a long time ago. It is not complete. I don't know if this kind of feature could be possible and coherent. I just submit it as is.
The Types Metadata
This is JavaScript data that represents the TypeScript types.
Primitive types
{type: 'string'}
{type: 'number'}
{type: 'boolean'}

Literal types
They are simply represented by their values.
Unions (|), Intersections (&)
{
    type: '|',
    items: [...types here...]
}

{
    type: '&',
    items: [...types here...]
}

Interfaces
{
    type: 'object',
    members: {
        member1: ...type here...,
        member2: ...type here...
    }
}

{
    type: 'indexer',
    index: ...type here...,
    indexMember: ...type here...,
    members: {
        member1: ...type here...,
        member2: ...type here...
    }
}

{
    type: 'function',
    name: ...string here...,
    arguments: [...types with names here...]
}

Additionaly, each type object can have a name member, when it is used as a function argument.
There is something to be found to represent optional members. Maybe a suffix '?' in the member name? However, all metadata should remain the same with or without the strictNullCheck option.
A syntax to import the metadata in the TypeScript code
We need something that can be opened and then closed. Maybe ~~?
~~ here the metadata code ~~

The metadata code is evaluated at compile time, and replaced by a type data. In the metadata code, each type name is a constant to which the type value is assigned.
For example, here is a TypeScript code that uses metadata:
type Color = 'blue' | 'orange' | 'red'
let colors = ~~Color.items~~

This code is equivalent to:
type Color = 'blue' | 'orange' | 'red'
let colors = ['blue', 'orange', 'red']

NB: Here the inferred type of colors is string[].
Use case
The main use case I see would be, to make robust DRY code to check JSON data.

Looks the same as https://github.com/Microsoft/TypeScript/issues/3628, and what is mentioned in https://github.com/Microsoft/TypeScript/issues/3015#issuecomment-98852421. the same concerns listed in these two issues are still there. i suggest keeping the discussion https://github.com/Microsoft/TypeScript/issues/3628

Thank you for the links. I searched, but didn't find.


Not working since recent updates

It does not work anymore since the recent updates with both ctrl + shift + y (nothing happens) or menu > Goto > Rails Go to Spec (grayed) or from the command palette (not available).
I'm using SublimeText 4143 on ArchLinux x64.
I don't know what other relevant information I could provide.

I made some updates and changed the repo name.
Waiting for this PR to be merged in the channel repo https://github.com/wbond/package_control_channel/pull/8791
So I suppose it is not going to work until that PR gets merged

I made a copy of the repo using the old name.
But still disabled for me. Not sure what is wrong now. Trying to figure it out.

Hi,
I've tried to uninstall/reinstall but RailsGoToSpec is not in the repo anymore :confused:

@RomainMorlevat Yes, the crawler says is missing.
It should appear again soon.

There is a workaround I'm using for now
In the command menu select Package Control: Add Repository
Add
https://github.com/sporto/rails-go-to-spec-sublime.git

The you can install the package rails-go-to-spec-sublime

Thank you for the workaround, it works again. And thank you for this plugin, it's really usefull.

I got the same problem, fixed it this way today, now it works fine

There is a workaround I'm using for now
In the command menu select Package Control: Add Repository
Add
https://github.com/sporto/rails-go-to-spec-sublime.git

The you can install the package rails-go-to-spec-sublime


Feature request: Does Tealium have a plugin for Single Page Web Apps based on React/Redux?

Nothing for React/Redux specifically (yet), but the pattern should be similar to the following (if you'd like to build and share),..
(1) Create a tracking wrapper function that accepts an eventName, and dataLayer object of key/values)
(2) If the utag.js file is loaded, fire utag.track( eventName, dataLayer );  // eventName is typically "view" for a content-viewed event
(3) If the utag.js file is not-yet-loaded, get the utag.js script and fire utag.track when it completes
For more reading:

http://tealium.com/blog/tag-management/ajax-tracking-urls-longer-change/

// Wrapper function as seen inside of angular js integration
var track = function( ev, data ) {
        var data = data || tealiumData.getDataLayer( $location.path() );
        var ev = ev || "view";
        var src = config.script_src;

        if ( typeof utag == "undefined" ) {
          getScript( src, function(){
            utag.track( ev, data )
          })
        } else {
          utag.track( ev, data )
        }
      };


various improvements

Removed gulp, grunt and bower
Improved control system
Removed gradle
Layout changed
packages were renamed

merged


Bump os_info to 3.5.0

close https://github.com/rust-lang/cargo/issues/10940

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit df8f33b4f218c958f4f9c03bba1feb7909482228 has been approved by epage
It is now in the queue for this repository.

:hourglass: Testing commit df8f33b4f218c958f4f9c03bba1feb7909482228 with merge 0ced33b1656b0dbe3dece629a77768db74ed5bd7...

:sunny: Test successful - checks-actions
Approved by: epage
Pushing 0ced33b1656b0dbe3dece629a77768db74ed5bd7 to master...


[Bug]: Could not retrieve latest CLI release info. Try again later.

Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the Issue Tracker for a bug that matches the one I want to file, without success.
[X] This issue is specifically related to Conduit's CLI

CLI version
0.0.15
Installation Type
MacOS
Describe the Bug
After installation, I execute the following command in terminal
conduit deploy setup

It gave me an error.
Error: Could not retrieve latest CLI release info. Try again later.
Expected Behavior
I guess it should give me the regular output.
How to Reproduce
conduit deploy setup

Additional Information
I searched in the source code, and I find this error output in an axio request. So I guess, it might be some problem in my proxy setup. But I have no idea how to debug it. Normally, If I set
ALL_PROXY=host:port

everything will be okay.
It doesn't work this time.
Environment
macosx 12.4

Yes, I can confirm,  the URL above is accessible for me via browser and curl.

I pushed a branch logging the axios response error.
Could you try the following and share the exact error that's being returned to you?
git clone git@github.com:ConduitPlatform/CLI.git && cd CLI && git checkout debug-pessimo && yarn --frozen-lockfile && npm run prepack && node bin/run deploy setup

sure, I'll try it. But I'm not good at js stacks :P ...


Git fatal error 🚨

Summary

When .git file is deleted, yarn start causes fatal error.
When git init, yarn start  causes fatal error.

Basic example
PS D:\DEV\hyas-git-error> yarn start
yarn run v1.22.5
$ hugo server --disableFastRender
Start building sites …
ERROR 2020/10/10 10:35:33 Failed to read Git log: fatal: not a git repository (or any of the parent directories): .git
Built in 1596 ms
Error: Error building site: logged 1 error(s)
error Command failed with exit code<PHONE_NUMBER>.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

PS D:\DEV\hyas-self-clone> yarn start
yarn run v1.22.5
$ hugo server --disableFastRender
Start building sites …
ERROR 2020/10/10 10:47:54 Failed to read Git log: fatal: your current branch 'master' does not have any commits yet
Built in 1171 ms
Error: Error building site: logged 1 error(s)
error Command failed with exit code<PHONE_NUMBER>.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Motivation
Making it work again 😬

enableGitInfo = true triggers fatal error
enableGitInfo = false triggers no error

https://github.com/gohugoio/hugo/issues/6035

Change default to enableGitInfo = false 👉 patch release https://github.com/h-enk/hyas

https://github.com/h-enk/hyas/releases/tag/v1.2.8


Error in creation: error: no context exists with the name: "hello-world-master3"

Hello,
I attempted to run the command hetzner-k3s create --config hetzner-k3s_cluster_config.yaml multiple times across different projects. However, I consistently encounter the same error.
I'm using verison: 2.0.9
error: no context exists with the name: "hello-world-master3"
...
Unhandled exception in spawn: timeout after 00:00:30 (Tasker::Timeout)
  from /usr/lib/crystal/core/channel.cr:453:10 in 'timeout'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/src/kubernetes/installer.cr:124:7 in 'run'
  from /usr/lib/crystal/core/fiber.cr:143:11 in 'run'
  from ???

Here is the full log:
[Configuration] Validating configuration...
[Configuration] ...configuration seems valid.
[Private Network] Creating private network...
[Private Network] ...private network created
[SSH key] Creating SSH key...
[SSH key] ...SSH key created
[Placement groups] Creating placement group hello-world-masters...
[Placement groups] ...placement group hello-world-masters created
[Placement groups] Creating placement group hello-world-small-2...
[Placement groups] ...placement group hello-world-small-2 created
[Instance hello-world-master1] Creating instance hello-world-master1 (attempt 1)...
[Instance hello-world-master3] Creating instance hello-world-master3 (attempt 1)...
[Instance hello-world-master2] Creating instance hello-world-master2 (attempt 1)...
[Instance hello-world-master3] Instance status: off
[Instance hello-world-master3] Powering on instance (attempt 1)
[Instance hello-world-master3] Waiting for instance to be powered on...
[Instance hello-world-master2] Instance status: off
[Instance hello-world-master2] Powering on instance (attempt 1)
[Instance hello-world-master2] Waiting for instance to be powered on...
[Instance hello-world-master1] Instance status: off
[Instance hello-world-master1] Powering on instance (attempt 1)
[Instance hello-world-master1] Waiting for instance to be powered on...
[Instance hello-world-master3] Instance status: running
[Instance hello-world-master2] Instance status: running
[Instance hello-world-master3] Waiting for successful ssh connectivity with instance hello-world-master3...
[Instance hello-world-master3] ...instance hello-world-master3 is now up.
[Instance hello-world-master3] ...instance hello-world-master3 created
[Instance hello-world-master2] Waiting for successful ssh connectivity with instance hello-world-master2...
[Instance hello-world-master1] Instance status: running
[Instance hello-world-master2] ...instance hello-world-master2 is now up.
[Instance hello-world-master2] ...instance hello-world-master2 created
[Instance hello-world-master1] Waiting for successful ssh connectivity with instance hello-world-master1...
[Instance hello-world-master1] ...instance hello-world-master1 is now up.
[Instance hello-world-master1] ...instance hello-world-master1 created
[Firewall] Creating firewall...
[Firewall] ...firewall created
[Instance hello-world-pool-small-worker2] Creating instance hello-world-pool-small-worker2 (attempt 1)...
[Instance hello-world-pool-small-worker1] Creating instance hello-world-pool-small-worker1 (attempt 1)...
[Instance hello-world-master3] Cloud init finished: 26.62 - Mon, 11 Nov 2024 11:26:48 +0000 - v. 24.3.1-0ubuntu0~24.04.1
[Instance hello-world-master3] Private network IP in subnet <IP_ADDRESS>/16 is up
[Instance hello-world-master3] [INFO]  Using v1.23.3+k3s1 as release
[Instance hello-world-master3] [INFO]  Downloading hash https://github.com/k3s-io/k3s/releases/download/v1.23.3+k3s1/sha256sum-amd64.txt
[Instance hello-world-master3] [INFO]  Downloading binary https://github.com/k3s-io/k3s/releases/download/v1.23.3+k3s1/k3s
[Instance hello-world-master3] [INFO]  Verifying binary download
[Instance hello-world-master3] [INFO]  Installing k3s to /usr/local/bin/k3s
[Instance hello-world-master3] [INFO]  Skipping installation of SELinux RPM
[Instance hello-world-master3] [INFO]  Creating /usr/local/bin/kubectl symlink to k3s
[Instance hello-world-master3] [INFO]  Creating /usr/local/bin/crictl symlink to k3s
[Instance hello-world-master3] [INFO]  Creating /usr/local/bin/ctr symlink to k3s
[Instance hello-world-master3] [INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[Instance hello-world-master3] [INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[Instance hello-world-master3] [INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[Instance hello-world-master3] [INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[Instance hello-world-master3] [INFO]  systemd: Enabling k3s unit
[Instance hello-world-master3] [INFO]  systemd: Starting k3s
[Instance hello-world-master3] Waiting for the control plane to be ready...
[Instance hello-world-pool-small-worker2] Instance status: off
[Instance hello-world-pool-small-worker2] Powering on instance (attempt 1)
[Instance hello-world-pool-small-worker1] Instance status: off
[Instance hello-world-pool-small-worker1] Powering on instance (attempt 1)
[Instance hello-world-pool-small-worker1] Waiting for instance to be powered on...
[Control plane] Generating the kubeconfig file to /home/sudo_ninja/kubeconfig...
[Instance hello-world-pool-small-worker2] Waiting for instance to be powered on...
error: no context exists with the name: "hello-world-master3"
[Control plane] ...kubeconfig file generated as /home/sudo_ninja/kubeconfig.
[Instance hello-world-pool-small-worker1] Instance status: running
[Instance hello-world-pool-small-worker2] Instance status: running
[Instance hello-world-pool-small-worker1] Waiting for successful ssh connectivity with instance hello-world-pool-small-worker1...
[Instance hello-world-pool-small-worker2] Waiting for successful ssh connectivity with instance hello-world-pool-small-worker2...
[Instance hello-world-pool-small-worker1] ...instance hello-world-pool-small-worker1 is now up.
[Instance hello-world-pool-small-worker1] ...instance hello-world-pool-small-worker1 created
[Instance hello-world-pool-small-worker2] ...instance hello-world-pool-small-worker2 is now up.
[Instance hello-world-pool-small-worker2] ...instance hello-world-pool-small-worker2 created
Unhandled exception in spawn: timeout after 00:00:30 (Tasker::Timeout)
  from /usr/lib/crystal/core/channel.cr:453:10 in 'timeout'
  from /home/runner/work/hetzner-k3s/hetzner-k3s/src/kubernetes/installer.cr:124:7 in 'run'
  from /usr/lib/crystal/core/fiber.cr:143:11 in 'run'
  from ???

Servers in the Hetzner Dashboard.

hetzner-k3s_cluster_config.yaml
hetzner_token: ...
cluster_name: hello-world
kubeconfig_path: "./kubeconfig" # or /cluster/kubeconfig if you are going to use Docker
k3s_version: v1.23.3+k3s1

networking:
  ssh:
    port: 22
    use_agent: false
    public_key_path: "~/id_ed25519.pub"
    private_key_path: "~/id_ed25519"
  allowed_networks:
    ssh:
      - <IP_ADDRESS>/0
    api:
      - <IP_ADDRESS>/0

masters_pool:
  instance_type: cpx11
  instance_count: 3
  location: nbg1

worker_node_pools:
  - name: small
    instance_type: cpx11
    instance_count: 2
    location: nbg1

See the note in https://github.com/vitobotta/hetzner-k3s/blob/main/docs/Creating_a_cluster.md about the embedded registry mirror. You are using an older version of k3s that doesn't support it, so either use a more recent version that supports it (as described on that page), or disable the embedded registry mirror and try again.


Can I combine fastertransformer to make it faster

Um, not really.
It would be better to use DeepSpeed inference or faster transformer separately


ping_of_death.c:72]: (style) Suspicious condition

ping_of_death.c:72]: (style) Suspicious condition (assignment + comparison); Clarify expression with parentheses.
Source code is
if (argc != 2 || ((target = libnet_name2addr4(l, argv[1], LIBNET_RESOLVE) == -1)))

Maybe better source code
if (argc != 2 || ((target = libnet_name2addr4(l, argv[1], LIBNET_RESOLVE)) == -1))

could you PR  that? It does look better!

I don't understand your comment. Please feel free to fix it.

I think you have found a bug in the example code. I don't have time to fix it. You can clone this repo, fix it, and I will accept the fix, or perhaps some other collaborator has the time.
How to make a PR: https://help.github.com/articles/creating-a-pull-request/

Perhaps I've been slightly less than clear. I've found a bug in this code.
I just find them, I don't fix them. I leave that to other folks who have more knowledge
of the project.

I have every confidence you could fix it if you wanted it fixed, because you included the fix in the issue description. If you don't want to, that's OK, I don't blame you, I don't have the time or interest in fixing it either.

@sam-github
Hi
My fork is currently a bit of a mess. Do you mind if I push this patch directly to master (so no PR for this. I would clone, edit and push)?


⚠ ClamAV has degraded performance

In ab8f46a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 84 ms

Resolved: ClamAV performance has improved in ef6d919.


Adding byte and Seq[Byte] generators inside of NumberGenerator

Coverage remained the same at 91.008% when pulling 7ab22f879603189d7fb14e981e794abd2706f71a on Christewart:master into 71630141a9a9bcf46a090a7c6ae452716ccdbdf4 on bitcoin-s:master.

ACK

tACK.


Various doc updates

This is a collection of documentation updates that have been in my todo list for a while. Each change is in a separate commit.
The "features" chapter will probably get significant changes in the future, as it is pretty bare right now. Similarly the "workspace" chapter could probably use more examples.
Closes #3062
Closes #3817
Closes #3971
Closes #4212
Closes #4438
Closes #4756
Closes #5822
Closes #6913
Closes #7055

r? @Eh2406
(rust_highfive has picked a reviewer for you, use r? to override)

Looks like maybe you did not add the new overriding-dependencies.md to this commit, or I am just misunderstanding.

Oh thanks!  Fixed.

@bors r+

:pushpin: Commit 493eb34327932964081c90bec8284a01b85aa0ad has been approved by Eh2406

:hourglass: Testing commit 493eb34327932964081c90bec8284a01b85aa0ad with merge 741f0e586a74f65c10200ae42b13bceea40d5957...

:sunny: Test successful - checks-azure
Approved by: Eh2406
Pushing 741f0e586a74f65c10200ae42b13bceea40d5957 to master...


Modification of TextLabel, TextEntry, Button behavior

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/widget/spk_value_selecter_widget.hpp:9
Compound spk::ValueSelector is not documented.

Sparkle/src/widget/components/spk_sprite_sheet_renderer.hpp:8
Compound spk::WidgetComponent::SpriteSheetRenderer is not documented.

Sparkle/src/widget/components/spk_font_renderer.cpp:127
no uniquely matching class member found for
void spk::WidgetComponent::FontRenderer::render()

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/graphics/texture/font/spk_font.hpp:105
Member operator<(const Size &p_other) const (function) of struct spk::Font::Size is not documented.

Sparkle/src/graphics/texture/spk_image.hpp:55
Member size() const (function) of class spk::Image is not documented.

Sparkle/src/graphics/texture/spk_image.hpp:55
Member size() const (function) of class spk::Image is not documented.

Sparkle/src/widget/spk_button.hpp:86
Member computeOptimalFontSize(const float &p_ratio) (function) of class spk::Button is not documented.

Sparkle/src/widget/spk_button.hpp:88
Member setPadding(const spk::Vector2Int &p_padding) (function) of class spk::Button is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_text_label.hpp:67
Member computeOptimalFontSize(const float &p_ratio) (function) of class spk::TextLabel is not documented.

Sparkle/src/widget/spk_text_label.hpp:69
Member setPadding(const spk::Vector2Int &p_padding) (function) of class spk::TextLabel is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:61
Member ValueSelector(spk::Widget *p_parent) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:62
Member ValueSelector(const std::string &p_name, spk::Widget *p_parent) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:102
Member decrementValueButton() (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:107
Member incrementValueButton() (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:112
Member valueDisplayer() (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:117
Member defineConvertionCallback(const std::function< std::string(const TType &)> &p_callback) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:122
Member addValue(const TType &p_value) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:127
Member selectValue(const TType &p_value) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:140
Member setIndex(const size_t &p_index) (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_value_selecter_widget.hpp:147
Member value() (function) of class spk::ValueSelector is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/spk_widget.hpp:237
Member forceGeometryChange(const spk::Vector2Int &p_anchor, const spk::Vector2UInt &p_size) (function) of class spk::Widget is not documented.

Sparkle/src/widget/components/spk_font_renderer.hpp:108
Member computeOptimalFontSize(const spk::Vector2Int &p_availibleArea, const float &p_outlineRatio) (function) of class spk::WidgetComponent::FontRenderer is not documented.

Sparkle/src/widget/components/spk_font_renderer.hpp:106
Member size (variable) of class spk::WidgetComponent::FontRenderer is not documented.

Sparkle/src/widget/components/spk_sprite_sheet_renderer.hpp:31
Member setSpriteSheet(const spk::SpriteSheet *p_spriteSheet) (function) of class spk::WidgetComponent::SpriteSheetRenderer is not documented.

Sparkle/src/widget/components/spk_sprite_sheet_renderer.hpp:37
Member setSprite(const spk::Vector2UInt &p_spriteCoord) (function) of class spk::WidgetComponent::SpriteSheetRenderer is not documented.

Sparkle/src/widget/components/spk_sprite_sheet_renderer.hpp:43
Member setSprite(const size_t &p_spriteID) (function) of class spk::WidgetComponent::SpriteSheetRenderer is not documented.

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/widget/components/spk_font_renderer.cpp:127
no uniquely matching class member found for
void spk::WidgetComponent::FontRenderer::render()

Sparkle/src/widget/components/spk_font_renderer.hpp:108
Member computeOptimalFontSize(const spk::Vector2Int &p_availibleArea, const float &p_outlineRatio) (function) of class spk::WidgetComponent::FontRenderer is not documented.

Sparkle/src/widget/components/spk_font_renderer.hpp:106
Member size (variable) of class spk::WidgetComponent::FontRenderer is not documented.

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/widget/components/spk_font_renderer.cpp:127
no uniquely matching class member found for
void spk::WidgetComponent::FontRenderer::render()

Sparkle/src/widget/components/spk_font_renderer.hpp:108
Member computeOptimalFontSize(const spk::Vector2Int &p_availibleArea, const float &p_outlineRatio) (function) of class spk::WidgetComponent::FontRenderer is not documented.

Sparkle/src/widget/components/spk_font_renderer.hpp:106
Member size (variable) of class spk::WidgetComponent::FontRenderer is not documented.

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/widget/components/spk_font_renderer.cpp:127
no uniquely matching class member found for
void spk::WidgetComponent::FontRenderer::render()

Sparkle/src/widget/components/spk_font_renderer.hpp:108
Member computeOptimalFontSize(const spk::Vector2Int &p_availibleArea, const float &p_outlineRatio) (function) of class spk::WidgetComponent::FontRenderer is not documented.

Sparkle/src/widget/components/spk_font_renderer.hpp:106
Member size (variable) of class spk::WidgetComponent::FontRenderer is not documented.

There is a list of documentation error you need to fix before merging this PullRequest :

Sparkle/src/widget/components/spk_font_renderer.cpp:127
no uniquely matching class member found for
void spk::WidgetComponent::FontRenderer::render()


CSS fixes for Microsoft Edge browser

Attached below are the screenshots of the pages where CSS is not proper in Edge browser.

Jar name missing while updating existing custom processor

Raised PR https://github.com/hortonworks/streamline/pull/788


"doh-client --noverify" encounter error

hi.
yudeMacBook-Air:quart-doh-by-treussart brite$ doh-client --noverify
Traceback (most recent call last):
File "/usr/local/bin/doh-client", line 11, in
load_entry_point('quart-doh==0.1.0', 'console_scripts', 'doh-client')()
TypeError: main() missing 1 required positional argument: 'args'
yudeMacBook-Air:quart-doh-by-treussart brite$
how to let doh-client to connect to doh-server?

Sorry but now : main(args)
Use this file instead
https://github.com/treussart/quart-doh/blob/master/quart_doh/client.py
python quart_doh/client.py  --noverify


Timeout with P2P > WebRTC

When I live stream my Eufy cameras through either the Lovelace WebRTC card or the GotoRTC http page (http://:1984) I find the stream stops after what seems to be about 10 minutes. If I live view the camera in the Eufy mobile app I get no such limitation. These are AC powered cameras btw.
Is there a timeout I can change? How can I ensure the live stream keeps running?
Also, I notice if I switch focus away from any WebRTC card that is live streaming, that too will disconnect the stream within a few seconds. Is there a way to ensure lovelace webrtc card live streams keep running when not displayed in the active browser tab? (Firefox).

You haven't provide info about source. Eufy doesn't tell me anything. I don't have these cameras.

Sorry the Eufy cameras are S100.

Didn't help much. What kind of stream format is used there? How did you get it?

The codec is h264, provider is P2P, resolution is 2K (2048×1536).

go2rtc haven't support P2P out of box.

Ok maybe it relates to the RTSP Simple Server HASS add-on that's needed to handle the P2P. I'll raise an issue there: https://github.com/fuatakgun/eufy_security.


ci: upload coverage reports for all test environments

Yup, it works. Last time I tried something like this I had issues.