Panels in demo generate: TypeError: Cannot read property '_owner' of undefined when expanded

On the View Live Demo page (and the downloaded same) Navigate
Sidebar->Components->Panels
on the panels page attempt expand either the standard bootstrap or accordion panel
Expected to see the sub-text in an expanded region.
On the creative tim website, got a blank page.
Using the downloaded code received the following message:
TypeError: Cannot read property '_owner' of undefined
Panels.componentDidUpdate
C:/_src/_BI_Alternative/Knoa-Proto/src/views/Components/Panels.jsx:18
  15 | class Panels extends Component {
  16 |   componentDidUpdate(e) {
  17 |     if (window.matchMedia(`(min-width: 960px)`).matches && !this.isMac()) {
18 |
this._reactInternalInstance._currentElement._owner._instance._reactInternalInstance._currentElement._owner._instance.componentDidUpdate(
  19 |         e
  20 |       );
  21 |     }

Local development server environment is
Windows 10
Chrome 73.0.3683.86
light-bootstrap-dashboard-pro-react 1.1.1
node.js v9.3.0
package.json
bootstrap 3.3.7
react 16.2.0
The following appears in the Chrome Dev console.
Panels.jsx:18 Uncaught TypeError: Cannot read property '_owner' of undefined
    at Panels.componentDidUpdate (Panels.jsx:18)
    at commitLifeCycles (react-dom.development.js:8778)
    at commitAllLifeCycles (react-dom.development.js:9946)
    at HTMLUnknownElement.callCallback (react-dom.development.js:542)
    at Object.invokeGuardedCallbackDev (react-dom.development.js:581)
    at invokeGuardedCallback (react-dom.development.js:438)
    at commitRoot (react-dom.development.js:10050)
    at performWorkOnRoot (react-dom.development.js:11017)
    at performWork (react-dom.development.js:10967)
    at batchedUpdates (react-dom.development.js:11086)
    at batchedUpdates (react-dom.development.js:2330)
    at dispatchEvent (react-dom.development.js:3421)
componentDidUpdate @ Panels.jsx:18
commitLifeCycles @ react-dom.development.js:8778
commitAllLifeCycles @ react-dom.development.js:9946
callCallback @ react-dom.development.js:542
invokeGuardedCallbackDev @ react-dom.development.js:581
invokeGuardedCallback @ react-dom.development.js:438
commitRoot @ react-dom.development.js:10050
performWorkOnRoot @ react-dom.development.js:11017
performWork @ react-dom.development.js:10967
batchedUpdates @ react-dom.development.js:11086
batchedUpdates @ react-dom.development.js:2330
dispatchEvent @ react-dom.development.js:3421
index.js:2178 The above error occurred in the <Panels> component:
    in Panels (created by Route)
    in Route (at Dashboard.jsx:131)
    in Switch (at Dashboard.jsx:112)
    in div (at Dashboard.jsx:102)
    in div (at Dashboard.jsx:99)
    in Dashboard (created by Route)
    in Route (at index.js:16)
    in Switch (at index.js:14)
    in Router (created by HashRouter)
    in HashRouter (at index.js:13)

Hello there @fallenwoods ,
Thank you for your interest in working with our products.
Firstly, I would like to ask you, why haven't you used our ISSUES_TEMPLATE?
!!! IF YOU DO NOT USE THIS ISSUES TEAMPLATE, YOUR ISSUE IS LIABLE TO BEING IGNORED BY US

# Prerequisites

Please answer the following questions for yourself before submitting an issue.

- [ ] I am running the latest version
- [ ] I checked the documentation and found no answer
- [ ] I checked to make sure that this issue has not already been filed
- [ ] I'm reporting the issue to the correct repository (for multi-repository projects)

# Expected Behavior

Please describe the behavior you are expecting

# Current Behavior

What is the current behavior?

# Failure Information (for bugs)

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

## Steps to Reproduce

Please provide detailed steps for reproducing the issue.

1. step 1
2. step 2
3. you get it...

## Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

* Device:
* Operating System:
* Browser and Version:

## Failure Logs

Please include any relevant log snippets or files here.

Then, are you sure you have opened the ticket on the right repository?
I've made a search inside all of the light-bootstrap-dashboard-react project folder for the keyword Panels and haven't got anything.
Best,
Manu


Provide a mechanism to hide charts built into Rancher

Is your feature request related to a problem? Please describe.

In our application, we have certain components always installed into our Kubernetes clusters and we need to hide some of the the Rancher Marketplace's built-in charts (e.g., istio) to prevent users from accidentally trying to install them and hosing their environment.   We currently accomplish this by injecting code into filterAndArrangeCharts function in store/catalog.js but as we move to the new plugin model, we would like to be able to accomplish this from the plugin without having to modify the shell.
Describe the solution you'd like

We don't have any particular solution in mind, we just want some mechanism to do this from the plugin that doesn't require modifying the shell.
Describe alternatives you've considered

As I stated above, we are already doing this by modifying the store/catalog.js file but that requires us to fork your repo.  We have also looked at modifying the ConfigMap where the list of charts is stored and changing the attribute on the charts to make them hidden.  Since this data is stored in binary form in the ConfigMap, we were concerned about doing this since it seemed like you didn't want users messing with this data (since you didn't leave it in plain text).
Additional context

@richard-cox

Note - I've removed references to plugins, although that is one option for a solution.
There is a chart annotation to do this, catalog.cattle.io/hidden : true however this cannot be used if there's no ownership of the charts (for example from one of the rancher repos).

I would also be interested in seeing functionality that would allow restrictions to the list of available chart by only enabling access to the chart repositories themselves at the project or user level.
I'm working in an environment where I would like to maintain access to all the packaged charts that come with Rancher (Partners, Rancher, RKE2) for the cluster admins while only allowing developer access to a particular set of approved chart repositories.

I believe it's at least theoretically possible to filter out any Helm charts that would require cluster level permissions to install. We could check if the user has permission to edit the cluster, then if they don't have that, go through the Helm chart YAML and filter out charts that require cluster level access.

We also need this. Most of these charts should only be presented to cluster admins, not ordinary users. We want to provide a curated list of Helm charts to our users. Cluster admins need access to a broader set of charts.
For users, the visibility of some of these charts within the UI will only lead to a confusing user experience. Kubernetes is hard enough as is. We must have the ability to hide charts like "Istio" or "Nginx Ingress Controller" to prevent curious users from digging themselves into a hole.

Ah. So, it sounds like, in addition to a permissions filter, there also needs to be a way to mark individual charts with minimum permissions levels such as admin permissions required or cluster-owner permissions required, on a case-by-case basis.
Does the catalog also need to vary based on the cluster itself? As in, owners of Cluster A should see A, B, and C charts, but owners of cluster B should see X, Y and Z charts? Or would all cluster owners see the same thing?

There is a chart annotation to do this, catalog.cattle.io/hidden : true however this cannot be used if there's no ownership of the charts (for example from one of the rancher repos).

What does "ownership" mean here? Is there a way for us to modify the chart YAML to attach ownership? Perhaps with an annotation like field.cattle.io/creatorId ?

There is a chart annotation to do this, catalog.cattle.io/hidden : true however this cannot be used if there's no ownership of the charts (for example from one of the rancher repos).

What does "ownership" mean here? Is there a way for us to modify the chart YAML to attach ownership? Perhaps with an annotation like field.cattle.io/creatorId ?

Ownership as is being in control of the helm repository where the chart in question lives. For instance if you wanted to hide a Rancher chart, you cannot apply the label to a chart in the Rancher owned helm repo. In theory you could fork them, make the change and then add those forked repos to Rancher, you would also need to ensure the fork was updated/maintained.

But the ownership of the Helm chart in a repo is irrelevant for what is needed—that is, to prevent the chart from being displayed in the Rancher Dashboard.  From this discussion, it seems clear that there is a missing mechanism to accomplish customizing the UI without worry about which repo or who owns it…


.js: Enforce stricter check on accessing bot pass

Clever users with js access can do something like ".js this.say(room, '/pm ' + user.id + ', ' + Config.pass);", which would bypass the current check for reporting users attempting to access the bot pass. This checks the string for any index of Config.pass and reports it if the user ID isn't axebane. If you'd like, I can add a line or two that will splice users attempting to view this from Config.excepts.

TBH I haven't really bothered trying to enforce stricter restrictions of this because it can be bypassed simply by using something such as ;js this.uploadToHastebin('Output:\n\n' + JSON.stringify(this.Config), function (link) { this.say(room, link);}.bind(this));. There's almost infinitely more ways to end up printing the bot's password, really. Plus, if a user's in the excepts list, they should be an extremely trusted user by default, so really, there's not much point in enforcing this at all, since you should be able to trust the user with the rights.

Alright, I guess this could be closed then.


Add IE/Edge’s Streams API to Stream Reader test

Various places in HTML5Test award for older implementation (menu element, Chrome's older Shadow DOM support, Chrome's support of pre-promises getUserMedia, etc.)
To be consistent, the same should be afforded to the MS proposed Streams API, which is the equivalent of SteamReader. This was initially proposed and there wasn't vendor interest outside MS, but then the Streams API that exists today appeared as another proposal, which seems to have got traction.
https://msdn.microsoft.com/en-us/library/hh772328(v=vs.85).aspx
https://dev.windows.com/en-us/microsoft-edge/platform/documentation/apireference/interfaces/msstreamreader/
http://html5labs.interoperabilitybridges.com/streamsapi/

Edge ended up adding Readable Streams as part of Fetch, so probably not worth looking into this now.


[Event Publisher] 2000019 "Suggest Vendor Payments EB" - OnAfterApplyVendLedgEntryFilters

Describe the request
In report 2000019 "Suggest Vendor Payments EB" we would like to add extra filters to the VendledgEntry record, by adding a new publisher OnAfterApplyVendLedgEntryFilters.

Suggested fix:
[Scope('OnPrem')]
   procedure SuggestPayments()
   begin
       OnBeforeSuggestPayments(Vend, PaymJnlLine, VendLedgEntry);

       Vend.CheckBlockedVendOnJnls(Vend, VendLedgEntry."Document Type"::Payment, false);
       // select vendor ledger entries
       VendLedgEntry.Reset();
       VendLedgEntry.SetCurrentKey("Vendor No.", Open, Positive, "Due Date");
       VendLedgEntry.SetRange("Vendor No.", Vend."No.");
       VendLedgEntry.SetRange(Open, true);
       if Vend.GetFilter("Currency Filter") <> '' then
           VendLedgEntry.SetFilter("Currency Code", Vend.GetFilter("Currency Filter"));
       VendLedgEntry.SetFilter("Global Dimension 1 Code", Vend.GetFilter("Global Dimension 1 Filter"));
       VendLedgEntry.SetFilter("Global Dimension 2 Code", Vend.GetFilter("Global Dimension 2 Filter"));

       OnAfterApplyVendLedgEntryFilters(VendLedgEntry); // ADD EVENT HERE

       // first take credit memo's into account
       if IncCreditMemos then begin
           // no filtering on "due date" here
           VendLedgEntry.SetRange(Positive, true);
           VendLedgEntry.SetRange("On Hold", '');
           VendLedgEntry.SetRange("Applies-to ID", '');
           if VendLedgEntry.FindSet() then
               repeat
                   SetPaymJnlLine();
               until VendLedgEntry.Next() = 0;
       end;

Event
 [IntegrationEvent(false, false)]
    local procedure OnAfterApplyVendLedgEntryFilters(var VendLedgEntry: Record "Vendor Ledger Entry")
    begin
    end;

Additional context
We want to add an extra filter to exclude vendor ledger entries with a specific payment method.
Internal work item: AB#550933

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 25061.


GCP OIDC - support strings in project ID

Right now we expect project ID to be number. A customer has asked to support this.
gcp:
login:
fn::open::gcp-login:
project:
oidc:
workloadPoolId:
providerId:
serviceAccount:

I don't think that this is possible, unfortunately.
All of the documentation, examples, etc. that I can find--including Google's official authentication action for GitHub Actions--explicitly expects the project number.

STS API docs: https://cloud.google.com/iam/docs/reference/sts/rest/v1/TopLevel/token#request-body
Official google-github-actions/auth@v2 action documentation: https://github.com/google-github-actions/auth?tab=readme-ov-file#inputs-workload-identity-federation

From what I can tell, the most straightforward way to get the number for a project is to use the gcloud CLI to print the number to the terminal:
$ gcloud projects describe [project ID] --format="get(projectNumber)"
1234567890123

@pgavlin Having bumped into it today and following a discussion on Slack with @automagic here's some context :
The documentations related to the GCP OIDC configuration https://www.pulumi.com/registry/packages/gcp/installation-configuration/ and https://www.pulumi.com/docs/pulumi-cloud/oidc/gcp/ make it unclear what should be put in the project parameter of the gcp-login function.
There's a sentence "Enter the numerical ID of your Google Cloud project in the “Project ID” field." in the section https://www.pulumi.com/docs/pulumi-cloud/oidc/gcp/#pulumi-deployments-1 but that's in a dedicated section you can skip (I did), everywhere else it's labelled project-id, which is misleading.
You should at least change in the documentation the label as project-number to match Google's own nomenclature, and maybe add a note about how to retrieve it.


improve external link design

fixes https://github.com/bluesky-social/social-app/issues/2556
fixes https://github.com/bluesky-social/social-app/issues/2555
Improves the sizing of external embeds so they don't take up so much screen space.

Reduce thumb size on mobile from 200 to 180
Reduce thumb size on web from 300 to 250
Reduce number of description lines from 4 to 2 unless there is no thumbnail
Cleanup unnecessary styles and move everything to the stylesheet

https://github.com/bluesky-social/social-app/assets/153161762/dec24810-ae9e-4715-bd8f-10186c822e1b

@haileyok wdyt about moving to an aspect ratio for the thumbs? we could try to match what the existing platforms have established

@pfrazee yea just asked @mozzius about that, sounds like 1.91 is the way to go. looks better on mobile and web that way, good call

wunderbar! thanks @haileyok and @mozzius


fix(types): add missing exported types

adding types for:

adding type Request
change Request / Response to classes (otherwise lint complains about instantiating interfaces)

Thanks!

btw: you might want to cleanup the exports a bit....I more or less copied the types from node-fetch

Thanks!

btw: you might want to cleanup the exports a bit....I more or less copied the types from node-fetch


Allow commands to run in tabs without panes

Sometimes it is useful to have a single tab dedicated to a command. For example I like to run my rails console in a separate tab.

Thanks @glasnoster :)


fix(snapshot): live migration deletes snapshots

New created engine for migration will have empty snapshot list in Status, and running syncSnapshotCRs will delete all snapshot CRs of this volume before engine monitor synchronize the snapshots into Status.Snapshots.
Ref: longhorn/longhorn#5992

We can block the migration confirmation if the new/target engine does not hold the same snapshot map as the old engine.

Modified. Check if snapshots sync before volume attachment controller set MigrationNodeID ""
Thanks.

@mergify backport v1.4.x v1.3.x


fix(concurrency): fix the tx_index offset in validate_reads and apply…

…_writes

This change is

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

Project coverage is 78.38%. Comparing base (4505d16) to head (758e4f4).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1982   +/-   ##
=======================================
  Coverage   78.38%   78.38%
=======================================
  Files          62       62
  Lines        8855     8855
  Branches     8855     8855
=======================================
  Hits         6941     6941
  Misses       1475     1475
  Partials      439      439

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


Is it Redundant to VMProtect the VAC Bypass Loader?

I currently VMProtect the .dll itself. I'm just wondering if it's necessary to do the same with the loader. I also use Process Hacker 2 as an injector. I ask of this because of the recent VAC Bans many have been receiving. I'm a little hesitant to inject anything into the game and use the loader to launch Steam as of last week as well as this week. (FYI: None of my accounts have been banned yet.)

Stop bullshitting around... VM Protect does nothing against signature scans! It just add an signature which is easier to detect for VAC and don't come up with junk code it does nothing against VAC!

Ok, well Floraly is very wrong, so don't mind him/her.
To answer OP's question(s), no, there isn't any point in VMProtecting VAC Bypass Loader. Yes, VMProtecting can help against signature scans in terms of a cheat itself, however, Steam itself isn't protected by any VAC Modules or anything similar, obviously; so the VAC Bypass is fine left alone.
It's probably worth mentioning; VAC Bypass is kind of redundant in of itself now a days, my PC has been flagged thanks to it and there is really no need to use it anyways so as long as you are taking the necessary precautions. Although, who gets flagged seems to be very... selective at times, and I am yet to figure out why.
gl, Jimmy.

Well, don't cheat on accounts you don't want to get banned. (Like mains and such.)
Second of all, no need to VMP a dll or the bypass itself, you can just give it a go by itself.

Alrighty, thanks for the Information!

Ok, well Floraly is very wrong, so don't mind him/her.
To answer OP's question(s), no, there isn't any point in VMProtecting VAC Bypass Loader. Yes, VMProtecting can help against signature scans in terms of a cheat itself, however, Steam itself isn't protected by any VAC Modules or anything similar, obviously; so the VAC Bypass is fine left alone.
It's probably worth mentioning; VAC Bypass is kind of redundant in of itself now a days, my PC has been flagged thanks to it and there is really no need to use it anyways so as long as you are taking the necessary precautions. Although, who gets flagged seems to be very... selective at times, and I am yet to figure out why.
gl, Jimmy.

what to do u mean by flagged?

Ok, well Floraly is very wrong, so don't mind him/her.
To answer OP's question(s), no, there isn't any point in VMProtecting VAC Bypass Loader. Yes, VMProtecting can help against signature scans in terms of a cheat itself, however, Steam itself isn't protected by any VAC Modules or anything similar, obviously; so the VAC Bypass is fine left alone.
It's probably worth mentioning; VAC Bypass is kind of redundant in of itself now a days, my PC has been flagged thanks to it and there is really no need to use it anyways so as long as you are taking the necessary precautions. Although, who gets flagged seems to be very... selective at times, and I am yet to figure out why.
gl, Jimmy.

what to do u mean by flagged?

That's just what I was referencing as VAC flagging your PC as a 'cheater pc', once this happens, supposedly every account you use on that computer is put straight into red trust so that you verse other cheaters... However, this methodology isn't confirmed, but it isn't pure speculation either, it seems to be the case for some people. Valve works in strange ways . x(

Ok, well Floraly is very wrong, so don't mind him/her.
To answer OP's question(s), no, there isn't any point in VMProtecting VAC Bypass Loader. Yes, VMProtecting can help against signature scans in terms of a cheat itself, however, Steam itself isn't protected by any VAC Modules or anything similar, obviously; so the VAC Bypass is fine left alone.
It's probably worth mentioning; VAC Bypass is kind of redundant in of itself now a days, my PC has been flagged thanks to it and there is really no need to use it anyways so as long as you are taking the necessary precautions. Although, who gets flagged seems to be very... selective at times, and I am yet to figure out why.
gl, Jimmy.

what to do u mean by flagged?

That's just what I was referencing as VAC flagging your PC as a 'cheater pc', once this happens, supposedly every account you use on that computer is put straight into red trust so that you verse other cheaters... However, this methodology isn't confirmed, but it isn't pure speculation either, it seems to be the case for some people. Valve works in strange ways . x(

i read about this unknowncheats forum...it tells that vac only affects the account you are getting detected with, but still no one knows how it works..
1.https://www.unknowncheats.me/forum/counterstrike-global-offensive/143570-vac-flagging.html
2.https://www.unknowncheats.me/forum/counterstrike-global-offensive/139652-vac-flagged.html

Ok, well Floraly is very wrong, so don't mind him/her.
To answer OP's question(s), no, there isn't any point in VMProtecting VAC Bypass Loader. Yes, VMProtecting can help against signature scans in terms of a cheat itself, however, Steam itself isn't protected by any VAC Modules or anything similar, obviously; so the VAC Bypass is fine left alone.
It's probably worth mentioning; VAC Bypass is kind of redundant in of itself now a days, my PC has been flagged thanks to it and there is really no need to use it anyways so as long as you are taking the necessary precautions. Although, who gets flagged seems to be very... selective at times, and I am yet to figure out why.
gl, Jimmy.

what to do u mean by flagged?

That's just what I was referencing as VAC flagging your PC as a 'cheater pc', once this happens, supposedly every account you use on that computer is put straight into red trust so that you verse other cheaters... However, this methodology isn't confirmed, but it isn't pure speculation either, it seems to be the case for some people. Valve works in strange ways . x(

i read about this unknowncheats forum...it tells that vac only affects the account you are getting detected with, but still no one knows how it works..
1.https://www.unknowncheats.me/forum/counterstrike-global-offensive/143570-vac-flagging.html
2.https://www.unknowncheats.me/forum/counterstrike-global-offensive/139652-vac-flagged.html

Yes, this is good insight, we don't know how it works, but from what I've seen I've made up a likely scenario and stuck to it because it's safer to than not to. :)

Okay believe what you want. ;-) I just say what I know and he says what he googled on Unknowncheats...

Okay believe what you want. ;-) I just say what I know and he says what he googled on Unknowncheats...

This is fair enough. :)


feat(opentelemetry-plugin-ioredis): provide a custom serializer fn for db.statement

Which problem is this PR solving?
IORedis plugin currently serializes the command name and arguments in the db.statement tag. This may yield to a big payload serialized inside the tag (for example, while mgetting many values or setting large json objects). It may also be an issue when data saved inside Redis should not be accessible inside logs/traces.
Short description of the changes
This PR adds an optional function inside the configuration that can be used to define a custom serialization function for db.statement. The function will receive cmdName and cmdArgs and will return a serialized string.
With this, one may decide (for example) to serialize only the cmdName for specific commands, or to have a separate handling for each command.
First contribution to the project so I hope I have done everything right :D

Codecov Report

Merging #33 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
+ Coverage   94.24%   94.29%   +0.04%
==========================================
  Files          57       57
  Lines        3252     3277      +25
  Branches      345      346       +1
==========================================
+ Hits         3065     3090      +25
  Misses        187      187

Impacted Files
Coverage Δ

node/opentelemetry-plugin-ioredis/src/ioredis.ts
100.00% <0.00%> (ø)

.../opentelemetry-plugin-ioredis/test/ioredis.test.ts
95.15% <0.00%> (+0.39%)
:arrow_up:

node/opentelemetry-plugin-ioredis/src/utils.ts
84.61% <0.00%> (+1.28%)
:arrow_up:

@naseemkullah any way to get your approval on this since you contributed the ioredis plugin?

LGTM 👍

@mayurkale22 this is ready to merge


clickhouse: copy object storage files on restore

When restoring from an object storage that is different from the default one,
copy files from the restoring storage config to the default storage config.
This adds support for restoring tables using object storage files
as well as tables using local storage.
This relies on an unmerged version of romhu to allow copying files
between buckets.

Codecov Report

Merging #135 (ee73a20) into master (c0cc73c) will increase coverage by 1.13%.
Report is 131 commits behind head on master.
 Consider uploading reports for the commit c0170df to get more accurate results

@@            Coverage Diff             @@
##           master     #135      +/-   ##
==========================================
+ Coverage   87.02%   88.16%   +1.13%
==========================================
  Files         122      136      +14
  Lines        7648     8940    +1292
==========================================
+ Hits         6656     7882    +1226
- Misses        992     1058      +66

Files Changed
Coverage Δ

astacus/server.py
0.00% <0.00%> (ø)

setup.py
0.00% <ø> (ø)

tests/system/test_astacus.py
100.00% <ø> (ø)

tests/unit/coordinator/test_cleanup.py
94.28% <ø> (ø)

version_from_git.py
0.00% <0.00%> (ø)

...tion/coordinator/plugins/clickhouse/test_plugin.py
28.83% <18.84%> (-11.36%)
:arrow_down:

...tion/coordinator/plugins/clickhouse/test_client.py
36.36% <36.36%> (-4.07%)
:arrow_down:

astacus/coordinator/cluster.py
89.60% <50.00%> (ø)

astacus/coordinator/plugins/m3db.py
87.03% <50.00%> (-2.69%)
:arrow_down:

...ation/coordinator/plugins/clickhouse/test_steps.py
40.00% <50.00%> (-11.73%)
:arrow_down:

... and 89 more

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


armadillo: 9.400.4 -> 9.500.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/armadillo/versions.
meta.description for armadillo is: '"C++ linear algebra library"'.
meta.homepage for armadillo is: '"http://arma.sourceforge.net"

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
/bin/sh passed the binary check.
1 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 9.500.2 with grep in /nix/store/a1p2r1djaavkfbv06pqm8zyr23f0ly48-armadillo-9.500.2
directory tree listing: https://gist.github.com/f8b9a115412cd21ca75a8f9a20da4664
du listing: https://gist.github.com/0e46c12dcf627864b8e284e8ef9cc76d

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

10 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
armadillo
gnss-sdr
openmolcas

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a1p2r1djaavkfbv06pqm8zyr23f0ly48-armadillo-9.500.2 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A armadillo https://github.com/r-ryantm/nixpkgs/archive/0a2f247a73d60da3ee0b7646366cf0136b79a561.tar.gz

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

cc @juliendehos @knedlsepp for testing.

Tested. Seems ok. Thanks.


Allow non-primitive types in Where

I've been trying to create a model where one of the database fields is automatically parsed into a class on read, and serialised on write such that my app code only ever has to deal with the class instance (not the string that's written to the database. I've been able to achieve this with the Mode lifecycle methods like so
class ModelWithResource extends PaginatedModel {
  id!: String
  resource!: Resource

  $parseDatabaseJson(json: Pojo): Pojo {
    json = super.$parseDatabaseJson(json);
    if (json.resource) {
      json.resource = new Resource(json.resource);
    }
    return json;
  }

  $formatDatabaseJson(json: Pojo): Pojo {
    json = super.$formatDatabaseJson(json);
    if (json.resource instanceof Resource) {
      json.resource = json.resource.toString();
    }

    return json;
  }
}

What I would like to do is be able to pass a resource class into a query like so
const resource = new Resource("Movie:123");
ModelWithResource.query().where("resource", resource);

I've been experimenting and as my backing database is Postgres, by adding a toPostgres method to my class I can make this work.
There are still two issues though.
1: Objection/Knex typescript typings don't allow me to pass a class instance into a where.
2: I think objection should be handling this as it is at the Model layer that all these transforms should happen.
Is this already possible and I'm not sure how to make it work? Or would it be possible to accept an object the implements something like a toPrimitive() function in objection and have this called before being added to the where bindings?

Implementing this would be very difficult. If you have control over the Resource class, you can already implement a toKnexRaw method for it and it will get handled by objection. You need to return a knex Raw objection from that method. Something like this
class Resource {
  toKnexRaw(query) {
    // `query` is the objection query buier this will be part of
    return query.knex().raw('?', this.toString())
  }
}

toKnexRaw is not yet documented, but it will be.

Can confirm this works for my situation. Problem is still that typescript is obviously not happy so will have to still wrap this in my own function and ignore the type warnings there for now.
Do you plan to enhance the typings to allow this when you add the docs, otherwise I can open a PR?

Note for the others. On knex 0.20.13 and objection 2.1.3, adding toKnexRaw() broke our app.
After adding toKnexRaw() to Engine class , if we passed Car.insert({ engine: engineAsClass }), where engineAsClass was an instance of the Engine class, the Car would be created, but with engine: undefined.
After updating to knex 0.21.1 and objection 2.2.0 , problem disappeared.


Use structuredClone instead of spread when handling layers input

structuredClone would prevent any references passed over on a deeper level.

Currently we are stringifying and parsing the layer config: https://github.com/EOX-A/EOxElements/blob/main/elements/map/src/generate.ts#L128
Thus, this is currently not an issue anymore, closing for now.


Apk build failed after installing

build failed after installed react-native-pip-android

go to node_modules/react-native-pip-android/android/build.gradle and do these changes

compileSdkVersion safeExtGet('PipAndroid_compileSdkVersion', 29)
buildToolsVersion safeExtGet('PipAndroid_buildToolsVersion', '29.0.2')

compileSdkVersion safeExtGet('PipAndroid_compileSdkVersion', 33)
buildToolsVersion safeExtGet('PipAndroid_buildToolsVersion', '33.0.0')

and

   minSdkVersion safeExtGet('PipAndroid_minSdkVersion', 16)

   targetSdkVersion safeExtGet('PipAndroid_targetSdkVersion', 29)

   minSdkVersion safeExtGet('PipAndroid_minSdkVersion', 26)

   targetSdkVersion safeExtGet('PipAndroid_targetSdkVersion', 33)


[Test] Added more extensive IntegrationTests for MergeAll operation.

This has been checked-in to the master branch.


[BUG] Opening of blog/post takes more time to open than expected!

project Information
Repository: https://github.com/esteemapp/esteem-mobile
Project Name: esteem-mobile
Expected behaviour
The post should have been opened immediately or within 3 -4 secs
Actual behaviour
Here when I clicked on post it took longer time to open.
How to reproduce
1-Download the application
2- Go to the blog/post
3- Open it and notice the error
Browser/App version: v2.1.0
Operating system: 7.1.2
Smartphone: redmi 5A
Recording Of The Bug
https://youtu.be/g2Qt-FtmaGM
My Github Account
https://github.com/peerzadaaabid

In this case, this post is very long, so it is expected behaviour. We changed render method with next release, it will more faster but long post takes more time than short posts @peerzadaaabid

It is fixed, you can test with next release (v2.1.1)


Do not skip page header for basebackup LSN

Looks ok, but why it was there in the first place? Perhaps we should do the reverse, i.e. normalize_lsn at safekeeper side?

That kind of change should come with a rigorous explanation of why it won't cause a crash during Postgres launch, and I think it actually will crash -- this normalization was to please Postgres. We now have a decent restriction -- pageserver returns normalized LSN's. And instead of imposing this rule on a safekeeper too, this patch removes restrictions at all.
+1 to coding it in the safekeepers (ideally but not sure how that will play with other code there) or in the wal_proposeser (normalize LSN tight after reading it).

I force pushed to run CI.
I also examined StartupXLOG to check whether something on compute side requires skipped page header LSN. As far as I see nothing. XLogBeginRead is ok with page header.
The only thing I see obviously incorrect is
			xlogPageHdr->xlp_info = XLP_FIRST_IS_CONTRECORD; // FIXME
			xlogPageHdr->xlp_rem_len = offs - SizeOfXLogShortPHD;

but I doubt anyone ever reads this page header.

XLogBeginRead is ok with page header.

XLogRecPtrToBytePos() asserts Assert(offset >= SizeOfXLogLongPHD);
StartupXLOG() calls XLogRecPtrToBytePos()

Did it per above. @knizhnik please have a look.


Compiling ajv jsonSchema doesnt throw errors

Hi!, when using the following schema with an invalid type on 'date' property
  static get jsonSchema() {
    return {
      type: 'object',
      required: ['firstName', 'lastName'],

      properties: {
        id: { type: 'integer' },
        parentId: { type: ['integer', 'null'] },
        firstName: { type: 'string', minLength: 1, maxLength: 255 },
        lastName: { type: 'string', minLength: 1, maxLength: 255 },
        date: {type: 'unexisting-type'},
        age: { type: 'number' },
      }
    };
  }

No errors are returned, I get success even inserting an object like this:
{
    "firstName":"sample",
    "lastName":"sample",
    "date":"2018-12-21 10:20"
}

I tested in a minimal JSFiddle example and it does return an error at compile time (AJV v6.6.2) https://jsfiddle.net/ads80y5j/
Im testing Objection in a modified version of https://github.com/Vincit/objection.js/blob/master/examples/express-es6/models/Person.js
I have a big app with many models using 'date-time' as type and now I realice its not a valid type but I couldnt detect it :(
So Im missing something?

@adefrutoscasado It may be because of the options we pass to Ajv when we create it. You can override those options by overriding the createValidator method.

I think wrong schemas can be a common mistake so throwing an error would make sense for me.
Thanks! And thanks for such an amazing ORM!

Thanks! :heart:
If you find a workaround until 2.0, could you post it here?

Not sure if theres a better approach but extending the Objection Model using Custom Validation worked for me:
const {Model, AjvValidator} = require('objection')

class ValidatedModel extends Model {
  static createValidator() {
    return new AjvValidator({
      onCreateAjv: (ajv) => {
        // Here you can modify the `Ajv` instance.
      },
      options: {
        allErrors: true,
        validateSchema: true,
        ownProperties: true,
        v5: true
      }
    })
  }
}

module.exports = ValidatedModel

Then when creating your own models, extend from this custom ValidatedModel:
const ValidatedModel = require('./ValidatedObjection.js')

class Person extends ValidatedModel {

  static get jsonSchema() {
    return {
      type: 'object',
      properties: {
        id: {type: 'integer'},
        user_id: {type: ['integer', 'null'], default: null, maxLength: 11},
        user_agent: {type: ['string', 'null'], default: null, maxLength: 500},
        ip: {type: ['string', 'null'], default: null, maxLength: 255},
        fingerPrint: {type: ['integer', 'null'], default: null, maxLength: 20},
        date: {type: 'unexisting-type'},
      },
      additionalProperties: false
    }
  }

Then, invalid schema errors will be thrown at AJV compile time:
schema is invalid: data.properties['date'].type should be equal to one of the allowed values

In the options property that is passed to the AjvValidator constructor, I would suggest setting strictKeywords to true.  Also, I prefer to set format to full.

This didn't get into 2.0 unfortunately. Luckily you can always provide your own options for the validator by overriding it as shown above.


The overview page crashed: TypeError: i is not iterable

What happened:

After successfully deploying Karmada and the dashboard, and logging into the dashboard successfully, when redirecting to the overview page, the page crashes immediately. All components are running normally, and the API returns responses as expected:

How to reproduce it (as minimally and precisely as possible):
The issue should be reproducible in a newly deployed environment.
Anything else we need to know?:
Environment:

Karmada version: 1.11
Karmada Dashboard version: latest

/cc @warjiang

@iawia002 Can you provide the http response of overview api, it will be helpful for me to solve the problem.

Hi, @iawia002. I appreciate you for spotting this!
If you want to join us in the dashboard development, It would be great!

@iawia002 Can you provide the http response of overview api, it will be helpful for me to solve the problem.

{
    "code": 200,
    "message": "success",
    "data": {
        "karmadaInfo": {
            "version": {
                "gitVersion": "v1.11.0",
                "gitCommit": "e579560af57f9d370295b94b3a33b102f464413a",
                "gitTreeState": "clean",
                "buildDate": "2024-08-31T12:08:03Z",
                "goVersion": "go1.22.6",
                "compiler": "gc",
                "platform": "linux/amd64"
            },
            "status": "running",
            "createTime": "2024-09-11T06:39:19Z"
        },
        "memberClusterStatus": {
            "nodeSummary": {
                "totalNum": 2,
                "readyNum": 2
            },
            "cpuSummary": {
                "totalCPU": 8,
                "allocatedCPU": 4.022222222222222
            },
            "memorySummary": {
                "totalMemory":<PHONE_NUMBER>,
                "allocatedMemory": 781294282.4160941
            },
            "podSummary": {
                "totalPod": 220,
                "allocatedPod": 47
            }
        },
        "clusterResourceStatus": {
            "propagationPolicyNum": 0,
            "overridePolicyNum": 0,
            "namespaceNum": 8,
            "workloadNum": 0,
            "serviceNum": 3,
            "configNum": 9
        }
    }
}

@iawia002 Can you describe the karmada-dashboard-web pod and show me the sha256 of the image

BTW,  It is probably a problem with react-router and i18n.

docker.io/karmada/karmada-dashboard-web@sha256:066b4ceaf1be713cf6a40ada20c292dc0b88675fe107c42f304e5e3e57eb44f8

@iawia002 I tried to replace the image as you metioned, but still cannot reproduced the problem,  I want to make an online meeting(20 miniutes est.) for more details if it's ok.

Sure, email me the meeting link z2d at jifangcheng.com

After some online debugging with @warjiang, we confirmed that the issue was caused by a missing configuration file. The dashboard's Helm charts were not updated in time, which led to the problem when installing the dashboard via Helm chart. I will submit a patch later to fix the issue in the chart.

Good job! That explains why @warjiang can not reproduce it.  Thank you @iawia002 , assigning this issue to you.
/assign @iawia002


Failed firestore write on schoology reset

Same issue as mentioned a month ago in  https://discordapp.com/channels/795043639214604370/796534035874447360/960309922829045830. Resetting schoology and clicking the confirmation button fires a firestore write with options.sgy set to true, but when resetting options.sgy is already true in the firestore userData and this write is blocked by the stricter firestore rules implemented after The Incident, causing the button to be unresponsive.

The firestore rules in question. A potential fix is to only attempt a firestore write if options.sgy is false, though I'm unsure if that would break something else.

(from @124274sashimi)

I would fix it, but it seems that Schoology authentication is completely down at the moment. Seems to be the recurring problem of Schoology not recognizing oauth_callback as a callback URL.

Closed in https://github.com/GunnWATT/watt/commit/7f0f8436e18ead1df201795e58ecfb1ce98cb416? A more elegant fix may exist but until then this solves the problem.


Added validator check for Mac OS private paths #309

@pstirparo could you spot check this PR and see if this is inline with our conversation.

Sorry for the interference, but what about
- type: FILE
  attributes: {paths: ['/private/etc/ssh/sshd_config']}
  supported_os: [Darwin]
- type: FILE
  attributes: {paths: ['/etc/ssh/sshd_config']}
  supported_os: [Darwin,Linux]

instead of
- type: FILE
  attributes:
    paths:
    - '/etc/ssh/sshd_config'
    - '/private/etc/ssh/sshd_config'
  supported_os: [Darwin]
- type: FILE
  attributes: {paths: ['/etc/ssh/sshd_config']}
  supported_os: [Linux]

Sorry for the interference, but what about

Interesting idea but IMHO a couple of downsides of that approach:

slightly more complex conditional logic is necessary to validate
easy to overlook the second source as one that applied to Darwin

For now I opt to keep it as is, and revisit this idea when I address the supported_os https://github.com/ForensicArtifacts/artifacts/issues/274

Validation of duplicate paths #41 is more complicated this way.

Validation of duplicate paths #41 is more complicated this way.

could you explain/elaborate why you think this is the case?

With the current solution there are duplicates of file paths when ignoring the supported os. My solution prevents duplicate file paths.

My solution prevents duplicate file paths.

How? I'm missing the necessary context.
Your suggested approach reduces the need for duplication in a single artifact definition/
However duplication can still exist across artifact definitions, which is what hinted at in #41.

A simple validator for duplicate file paths will find the duplicate /etc/ssh/sshd_config in
- type: FILE
  attributes:
    paths:
    - '/etc/ssh/sshd_config'
    - '/private/etc/ssh/sshd_config'
  supported_os: [Darwin]
- type: FILE
  attributes: {paths: ['/etc/ssh/sshd_config']}
  supported_os: [Linux]

but not in
- type: FILE
  attributes:
    paths:
    - '/etc/ssh/sshd_config'
    - '/private/etc/ssh/sshd_config'
  supported_os: [Darwin]
- type: FILE
  attributes: {paths: ['/etc/ssh/sshd_config']}
  supported_os: [Linux]

Anyway it does not matter to much, I just have to make my duplication checker aware of different supported_os.

Anyway it does not matter to much, I just have to make my duplication checker aware of different supported_os.

Note that supported_os is on the list to be changed, I opt not to invest too much effort here yet.


Debounce?

I see the delay prop but i'm unsure of the role or use as it's described as animation delay. Using delay gives an error.
<Action_tooltip> was created with unknown prop 'delay'

So the bottom line question is how would I go about debouncing the execution (not just the display) of this tooltip?

I created a REPL with examples of using a timer + show prop and the delay prop here https://svelte.dev/repl/4562d5e5af1541c5b8b35589778f25b1?version=4.2.18


Fix for 404 in docs

https://github.com/docker/docker.github.io/issues/1413

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "patch-3" git@github.com:johndmulhausen/docker.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Does this require android.permission.SYSTEM_ALERT_WINDOW?

We're cleaning up our permissions and I'm curious if the error overlay takes advantage of the system alert window (draw over other apps) permission.

In the default implementation - no . But if you want to do something custom like that, you can add a custom native error handler and give the permission if needed. @lwansbrough

OK, thank you!


Data retrieval from GitHub repository

The tester currently builds its structure using information from the catalog available on the user's computer (the user must provide the path for the catalog content folder as an argument). However, this "offline" information may be outdated. The best option would be to read the information directly from the web GitHub repository.
We can only implement this enhancement after solving the Issue #1.

@mozzherina, please solve this issue only after the re-generation of the dataset.

There is one more thing here. Collecting data from GitHub would be slow. We must provide a user with the possibility to load from the local folder.


[BUG] Custom JsonMapper not working for RequestBody

Information

Version: 7.29.1
Packages:

I have a custom JsonMapper. This mapper is correctly used for PathParams but it is not used in BodyParams
Example
// custom ID class
export class OrganizationId extends Id {
    public static PREFIX = 'OG'

    public getPrefix(): string {
        return OrganizationId.PREFIX;
    }
}

// JsonMapper
import { JsonMapper, JsonMapperCtx, JsonMapperMethods } from "@tsed/json-mapper";
import * as Ids from "@/ids";
import IdUtils from "@/ids/IdUtils";

@JsonMapper(...Object.values(Ids))
export class IdMapper implements JsonMapperMethods {
  deserialize<T extends Ids.Id>(data: any, ctx: JsonMapperCtx): T  {
    return IdUtils.fromHex(data);
  }

  serialize(id: Ids.Id): string {
    return id.getValue();
  }
}

// My protocol
import { UserId } from "@/ids";
import {Property, Required, Description} from "@tsed/schema";

export class AddUserToOrganizationRequest {
    @Property()
    @Required()
    @Description('The user id to add')
    userId: UserId;
}

// Controller method
@Post('/')
  @Returns(201, User)
  async create(@PathParams("organizationId") OrganizationId: OrganizationId, @BodyParams() body: AddUserToOrganizationRequest)

When I run this I get
{
  "name": "AJV_VALIDATION_ERROR",
  "message": "Bad request on parameter \"request.body\".\nAddUserToOrganizationRequest.userId must be object. Given value: \"US0d250728edf78ddcc9e4d5786bf86b00\"",
  "status": 400,
  "errors": [
    {
      "instancePath": "/userId",
      "schemaPath": "#/definitions/UserId/type",
      "keyword": "type",
      "params": {
        "type": "object"
      },
      "message": "must be object",
      "data": "US0d250728edf78ddcc9e4d5786bf86b00",
      "modelName": "AddUserToOrganizationRequest",
      "dataPath": ".userId"
    }
  ]
}

If I change the type to string, the everything works fine, including OrganizationId in the path parameter be in fact deserialized correctly. Why isn't this working for RequestBody?
Acceptance criteria

[ ] JsonMapper be used for request body as well

Hello @ktalebian
You just misunterstood the error. Jsonmapper are executed after the ajv validation.
this is why you have a validation error.
Try this code:
class AddUserToOrganizationRequest {
    @Property(String)
    @Required()
    @Description('The user id to add')
    userId: UserId;
}

see you

@Romakita ah perfect that works great thanks! I think I'm reading this TypeORM too much like a Java application 😅


doesn't compile with pty.js Version 0.2.7-1

Hi,
the verion 0.2.7-1 of pty.js doesn't compile with my aktuall Arch Linux Version, gcc Version 5.2.0?
With the version 0.3.0 of pty.js the installation workes and wetty is runnning.
Thanks for the greate work.
mfG Matthias

@schmimat good to know that wetty is running fine. closing this issue.

Hi,
sorry for reopen, but to compile in the file package.json the version of pty.js had to be set to 0.3.0.
Can you change it in the file?
"pty.js": "^0.2.7-1", --> "pty.js": "^0.3.0-1" or so
Best regards Matthias

@schmimat :+1:  What Matthias said -- took me a while to track down the issue before changing the pty.js version in package.json


Adding a hovering effect on the rating stars.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Currently on the rate us page, there is not effect on hovering. I can add the hovering effect on the page there. Kindly assign this issue to me under GSSOC'24.

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

hey kindly close this issue. @RishabhDhawad


Check whether an install script reaches out to arbitrary network connections.

Install scripts that reach out to the internet, other than pulling down a specified version of a dependency from a trusted repository, are potentially dangerous.
For example @mapbox/node-pre-gpy allows a package owner to specify an arbitrary URL to download native dependencies from for installation. This means I not only have to trust the source of the package, but also the entire supply chain of the arbitrary URL.

This is possible now after #200 and #203 and the work to add hostnames to IP addresses.


The size of the blocks in the main page are different

@baimingze The size of the each block in the main page is different, it would be good if all of them have the same size, see the image.

done


🚀[FEAT: ] Keyboard shortcuts for better UX.

Is your feature request related to a problem? Please describe.
When coding inflow, we usually don't prefer to leave our keyboard and use the mouse to do some repetitive action. Hence for the betterment of user experience let's introduce short-cut keys for various commands such as Run, download file, copy, etc.
Describe the solution you'd like
The solution is pretty easy with implementing a library like React Hotkeys
Motivation
Many famous online Coding IDE's provide this feature for better UX.
Are you willing to contribute to this issue? [Yes/No]
Yes, I am willing to contribute to this issue under GSSOC21
Describe alternatives you've considered
Alternatives may only vary in choosing different libraries for hotkeys, but the approach for this feature remains almost the same. Still open to suggestions as usual ✌
Additional context
Following is the screenshot of keyboard shortcuts from Leetcode

Hi @amaan-ahmad, First of all, thank you so much for taking out the time to create this issue.
Definitely, the short-cut keys will help to improve user experience 🙌, Please go forward to work on this issue. I am assigning this Issue to you 👍
And last but not least,
Keep Contributing 🙏🔥

Thanks @Akash-Salvi ✌💯

can I work on this

hey @kothariji, I am really apologetic, I was really caught up in my internship. Will continue working on it and make a PR in a day or two. Again apologies 🙏

Hey, no issues @amaan-ahmad ...... Sure 🙌


add object-shorthand

http://eslint.org/docs/rules/object-shorthand, and autofixable
Each of the following properties would warn:
/*eslint object-shorthand: "error"*/
/*eslint-env es6*/

var foo = {
    w: function() {},
    x: function *() {},
    [y]: function() {},
    z: z
};

In that case the expected syntax would have been:
/*eslint object-shorthand: "error"*/
/*eslint-env es6*/

var foo = {
    w() {},
    *x() {},
    [y]() {},
    z
};

:+1:

:+1:


Rethink Grammar::generate logic

I'd like to be smarter about how we generate random sentences from a given grammar.
There's a danger that a valid grammar can result in an infinite loop when randomly generating, so atm we just take an guess at if we're looping in a way that looks like it's not going to stop any time soon by checking the stack and bailing before we recurse too far.
For instance the case used in the tests is <nonterm> ::= <nonterm>. We can't get to a terminal state so we're doomed to failure if we try to generate a sentence.
I'm not sure what an ideal solution is here, for one, it'd be nice to figure something that didn't have to short circuit the potential for "maybe infinite loops".
Maybe there's a way to check for impossible grammars for the generate logic first and error early if that's the case. Then... if we have the potential for a terminal state but aren't reaching it because of random chance we need to do something sensible... maybe allow a configurable max generated length and do the work to find some terminal nodes when we get there?
If can manage a max length, I like the idea of implementing a minimum length too 🤔

What would you think of

reducing a grammar to a directed graph structure
where nodes are rule names and edges go from a rule to its dependents. For example: <A> ::= <B> | <C> <D> would result in a graph

(A) --> (B)
   \
    `-> (C) --> (D)

then check for cycles that can't be reached from terminals

I think that'd be doable using petgraph.

Ah petgraph looks cool! I like your proposed solution too, I'd have to poke at it a bit if I were implementing, but fwiw I'd totally support a solution like this in a PR.

Has this question been resolved already? If not I think I have proposal for it (I was skeptical that the proposed solution would work).
This problem can be reduced to solving the emptiness problem for CFLs. I have added a solution strategy below:

We mark every non-terminal that produces a sequences of terminals
We then recursively mark every non-terminal that can produce a sequence of marked elements
We check whether the initial non-terminal is marked

I don't think this needs any special libraries but just a poly-space recursion on the existing grammar would work well.
What do you guys think?

@notDhruv this hasn't been solved yet 😄 I think your approach sounds great, seems like it'd for definitely give us a mechanism for avoiding the infinite loop issues, and I can imagine that if we have some known-to-be-finite paths to terminals to traverse, we could work in the min - max generated sentence length too.


Update toml library and add test

This pull request includes:

[X] adequate testing for the new functionality or fixed issue

[ ] 1st commit of any rhbz# related PR contains bug reproducer; CI reports FAIL or

[X] PR contains automated tests for new functionality and

[ ] QE has approved reproducer/new tests and

[ ] Subsequent commits provide bug fixes without modifying the reproducer; CI reports PASS and

[ ] QE approves this PR; RHBZ status is set to MODIFIED + Verified=Tested

Closing, no chance of the PR working at this point.

@bcl I think that this bug was fixed on main by basically dependabot updating the dep. However, it would be nice to have the new test on main as well. Would it take much effort to "port" it?

Ignore me, this was done in https://github.com/osbuild/osbuild-composer/pull/3099, I failed at using the git log.


Need config syntax to set a default icon

Apply the same icon to all nodes (with any labels as, far as icons are not set for the labels)

    icon: {
      _default: "akar-icons:person",
    },

_default is added only for icon (not for other items such as size) so far.

https://docs.blitzboard.io/visualization/nodes#node-icon


S2U-39 <IP_ADDRESS> Wiki: Add group support to Wiki pages - fix

There is a hardcoded condition, I don't think this is valid since the role could be dynamic.


fix POWER BI STANDARD license name

fixed the POWER BI STANDARD license name

@mmascolino : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


lnurl-login call doesn't provide signature

Besides suffering from the same querystring problems described in https://github.com/btcontract/lnwallet/issues/145, when performing a login the k1 is borked and sig is empty.
If the initial lnurl is https://testurl.example.com/lnurl-login?tag=login&k1=378be88a4da486f610b94af4768ffbbff089ec78be6dfd3a312030a828087b36 the callback hits at:
/lnurl-login?tag=login&k1=378be88a4da486f610b94af4768ffbbff089ec78be6dfd3a312030a828087b36?k1=[B@2509b20&sig=&key=0226a0b9de7a671d4cebd97a3fb34c656c0d1b203e53a2b6712591c49fb335068e

Fixed in https://github.com/btcontract/lnwallet/commit/911efbd35f5b7a223bdc1d58011adefe030e69f2


Fix: adapt function to translate cached prompts in place.

Address issue #888
It enables the following functionality in order to generate a testset in a language other than English.

from ragas.testset.prompts import testset_prompts
from ragas.testset.generator import TestsetGenerator

...
# some other imports
...

# adapts all prompts to a given language, here german
for p in testset_prompts:
    p.adapt("german", translator_llm)

# run the test set generation
generator = TestsetGenerator(
        docstore=docstore,
        generator_llm=generator_llm,
        critic_llm=critic_llm,
        embeddings=embeddings
    )

dataset = generator.generate(
        test_size=TEST_SIZE,
        distributions=DISTRIBUTION
)

Without this fix, this would only work the first time. The first time, when the prompts are translated the "adapt" method changes the prompt instances (that is, in place). Therefore, the generate below uses the translated prompts. However once the prompts are in the cache, running adapt on all prompts doesn't change them "in place" and then generate will access the original prompts completely in English. This PR makes this approach to work also when the translated prompts are already cached.
I also added the testset_prompts variable for convenience.

thanks alot for the PR @HerrIvan ❤
I know you pushed this a while back, really sorry for not merging it in earlier. but would love to catchup with you sometime if you are interested. Just to meet you 🙂


Partially take over modifications added by bazel_to_cmake in non-strict mode

Updates to the CMake configuration, assisted by bazel_to_cmake.py.

One remaining problem that prohibits to run bazel_to_cmake.py in strict mode is that it adds file(GLOB _GLOB_X_TD CONFIGURE_DEPENDS *.td), but grumbles about Unimplemented filegroup: td_files. Actually, I don't see the reason for these filegroups, at least not in the OSS version.


EPS: Error with bitcoin json-rpc

I've been trying to setup my raspiblitz with eps and followed the instructions to the T, but i'm getting the following error:
 JsonRpcConnectionError('authentication for JSON-RPC failed',)
So, i thought i might have made a typo or some stupid mistake. I checked all the config files in /home/bitcoin/.bitcoin/bitcoin.conf /home/admin/.bitcoin/bitcoin.config & ~/eps/config.cfg for rpc_user & rpc_password and they are identical.
So, what am i missing or doing wrong?
Thank you!

Working on updating the EPS guide, there have been some major changes.

Is this about RPC username/password method being depricated? I'm gonna try to change it to the cookie method. Will post if i can resolve it or find something.

The RPC user/pw is still the way to go, no changes there.

I updated my Pi's image with LND 0.5.1, and it worked seamlessly. I still don't know why did i face that problem, would like to know that. But, for now my problem has been resolved but the question still remains.
Using RPC user/pw for authentication.

Closing for now. If you come accross an answer, I would be interested as well. :-)


Set CWD as an option in launch.json before debugging

There is currently no way to specify a cwd to run / debug venus from

Hey, great suggestion.
Can you specify what purpose setting the cwd should serve?
I can only think of setting the cwd to manipulate the origin point for relative imports.
Are there potentially more use-cases?


[FR]

Is your feature request related to a problem? Please describe.
Do you have a Discord server for this module? its a really nice one and it would really benefit users who need direct support either with you or other staff/helpers/any one else.
Describe the solution you'd like
A discord support server
Describe alternatives you've considered
I understand they can make bug and FR issues but a server would be easier with the ability to reach everyone else that has used your module.

This is the official Discord Server of this module: https://ssumbot.xyz/discord


added header_image.jpg to avoid FileNotFound error

Pull Request Title

Related Issue

Description

Type

[ ] Bug Fix
[ ] Feature Enhancement
[ ] Documentation Update
[ ] Code Refactoring
[ ] Other (please specify):

Proposed Changes

Screenshots / Code Snippets (if applicable)

How to Test

Checklist

[ ] The code compiles successfully without any errors or warnings
[ ] The changes have been tested and verified
[ ] The documentation has been updated (if applicable)
[ ] The changes follow the project's coding guidelines and best practices
[ ] The commit messages are descriptive and follow the project's guidelines
[ ] All tests (if applicable) pass successfully
[ ] This pull request has been linked to the related issue (if applicable)

Additional Information

@thakoreh can you please check if the issue still persists?

@srbhr Yes it has been fixed now


Update deployment scripts

Fix couple errors introduced during the last round of beautification
Add a check on null resource group location when creating a new resource group
Changes to make the coding style consistent

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

@tongwen11 I did some additional minor changes, can you check that it works fine?

Validated. Thanks!


Detected OSIRIS

I was using Osiris with a VAC bypass. Was hacking for 2 hours and i got banned
"Global Cooldown"
"This account is Permanently Untrusted"

too high max angle delta

yeah "untrust" doesnt mean its detected

This can mean a multitude of things. It could happen due to certain features being enabled like choking packets in competitive play or enabling aimbot with low smoothing that snaps.

its a server thing, there is something wrong with your setting

This can mean a multitude of things. It could happen due to certain features being enabled like choking packets in competitive play or enabling aimbot with low smoothing that snaps.

Personally, ive used osiris on 3 different accounts as of right now. My aimbot is set to pretty much as blatant as it ever could be, hitting instant heads while looking 90 degrees away from people. None of the accounts have been banned, the first one even after a week.


Peer connection attempts reported as failed

What you expected to happen?
Peer connection attempts to self not to be reported as failed.
Background
We got alarmed by these.  After some research, the takeway is that it's noise.  However, also saw a lot of issues about peers not being able to join shortly after CONN_LIMIT.  We don't scale nodes much, so less of a concern for us, but still thought we should pay attention to this metric just in case.  Our workaround is simply to treat N failed connections for N nodes in the cluster as normal.
Some Ideas

Adding a new state just for this might be a no-go.
Adding special handling in the metrics reporting to ignore when Info ~ "cannot connect to ourself" might be too brittle.
Patch something in the kubernetes add-on so that a node doesn't try to connect to itself.  The hope is that something in kubernetes land can better inform weave which peers to try.

If core devs provide a bit of guidance, we might be able to submit a PR.
Versions:

weave 2.4.0
kubernetes 1.11

Logs:
kubectl -n kube-system exec weave-net-fqv5t -c weave -- /home/weave/weave --local report | jq -r '.Router.Connections[] | select(.State != "established")'
{
  "Address": "<IP_ADDRESS>:6783",
  "Outbound": true,
  "State": "failed",
  "Info": "cannot connect to ourself, retry: never",
  "Attrs": null
}

If core devs provide a bit of guidance, we might be able to submit a PR.

@erik-stephens Apologies for the delay in response. Please give it a try to submit a PR.
Please take a look at the kube-utils program which when called returns the list of the current set of Kubernetes node Ip'ss. That list is passed by launch.sh to launch main weave program by passing passing the llist as argument.
So try to exclude the self node in the returned list by kube-utils.


Question: npx bddgen is not getting exited properly.

Hi @vitalets - Good Day. Am trying to execute the npx bddgen with the below version. I see that the features-gen folder is successfully created with test *.spec.js files, but the process is not getting exited properly. Not sure what causes this problem. In  local am able to do "Ctrl + C" and continue with my execution. But in pipeline, this particular step npx bddgen is taking longer time and its not getting exited. Also, tried debugging with nodemon mentioned in the documentation, still no luck. Can you help me here how can I fix this issue ?
Attached is the screenshot for your reference.
Please let me know if you need any other information.

Note: tried clearing npm cache, uninstall and reinstall playwright-bdd,

Hi @dpjp !

Could you run locally npx bddgen --verbose and share the output?
Could you clone playwright-bdd-example and run npx bddgen there?

Hi @vitalets ,
I tried the above commands. The npx bddgen works fine in the playwright-bdd-example project. And alsom observed that the issue was causing because of aspose.cells nodejs via java npm package. Am using this package in my project for excel manipulations.
Aspose.cells npm package
https://www.npmjs.com/package/aspose.cells
If I have aspose.cells installed in my project, the npx bddgen is not exiting properly. But after uninstalling the aspose.cells, I see that the npx bddgen seems to be working fine.
Aspose,cells is must library for my project as we deal with different excel templates. It would be great if you could help me with a work around.

I've tried to install aspose.cells but getting an error (osx, m1):
> npm i aspose.cells

...
../src/java.h:7:10: fatal error: 'jni.h' file not found

But I see in readme they highly recommend to migrate to Aspose.Cells for Node.js via C++. I've checked - it installs correctly and npx bddgen works.
Could try with it?
Looks like support for aspose.cells will be dropped anyway in future.

Hi @vitalets @VitaliyPotapov - For the past few days, I had been following up on this with aspose.cells support and my project engineering team. Due to security concerns and performance issues, I will not be able to use aspose.cells for Node.js via c++ as they set license using a file and cannot have the license file in shared repository, whereas, for nodejs via java we use metered license and we can store the keys in secrets.  Also, aspose support team confirmed that they will be supporting this aspose.cells for nodejs via Java in the future and dont have any plans to retire/deprecate it.  So I think we have only this option(use aspose.cells for nodejs via Java) to go with.
Aspose support ticket reference: https://forum.aspose.com/t/aspose-cells-node-version-24-7-npm-library/288564
Issue Description:
I can say exactly when this npx bddgen is not exiting properly.
I was able to do npm install for aspose.cells and Java.
I installed Java JDK(v22) in my machine.
After the above installation steps, npx bddgen works fine.
In order to use the aspose.cells for nodejs via java in my office laptop, I am forced to set the certificate in Java bin folder using keytool command as mentioned below
"keytool -import -trustcacerts -file /ca-certificatename -alias custom-Root-CA -keystore ..\jre\lib\security\cacerts"
Only after setting the certificate, am facing this issue.(npx bddgen is not exiting properly).
Can you help me if you have any workaround towards this ?

Hey @dpjp
Such issue is very difficult to reproduce.
Lets try the following:

When you run pure Playwright tests, do es it exit correctly with and without installed certs?
Try to run this command with and without installed certs, to check what causes node to hang (uses this module):npx why-is-node-running node_modules/playwright-bdd/dist/cli/index.js --verbose

Hi @vitalets, @VitaliyPotapov - Sorry.. Ignore my previous recent post. I see the issue is in the below lines. In one of my .ts class,
am importing the aspose.cells using the below lines.
var aspose:any = aspose || {};
aspose.cells= require("aspose.cells");

The same code works with playwright test runner(excluded playwright-bdd).  Do you have any work around for this ?

If you just run the following file with node, does it exit properly?
// file.js
var aspose = aspose || {};
aspose.cells= require("aspose.cells");

Run:
node file.js

Ok. Then please try this command, to get the exact reason of hanging:
npx why-is-node-running file.js

Also, haven't you open an issue in aspose forum? Because hanging of require("aspose.cells"); looks like a more general issue than related to playwright-bdd.
In Playwright it exists, because Playwright internally calls process.exit() to force exiting.

Hi @vitalets - I tried running this command 'npx why-is-node-running file.js' and I see the below error.

Yes, I did posted in the aspose.cells forum and I got the below response and still no luck.

Then we can try to wrap the call of bddgen and force exit when files are generated:
// bddgen.cjs
const { spawn } = require('node:child_process');
const child = spawn('./node_modules/.bin/bddgen', ['--verbose']); // for windows there can be bddgen.bat

child.stdout.on('data', (data) => {
    console.log(`stdout: ${data}`);
    if (data.includes('Generating Playwright tests')) {
        setTimeout(() => child.kill(), 2000);
    }
});

And run it:
node bddgen.cjs

Let me know, does it work?
Note:
Now it uses timeout for 2000 ms.
This could be improved in the next version of pw-bdd, I will add a string Done. as a final output to let child process know that files are generated.

Hi @vitalets  - Am I doing anything wrong here? Tried executing the same. I get the below error and says that its unable to locate the executable.

Also, in the bin folder under node modules, I see the below files.

Hi @dpjp
Could you try with const child = spawn('./node_modules/.bin/bddgen.cmd', ['--verbose']);

Hi @vitalets  - Yes. I did try the same previously. I was getting the below error.

Also, wanted to check on the below. I had generated the steps definitions for these steps. But still it says undefined steps and when pressed "F12" from the feature file, Its not navigating to the corresponding step definition. I tried setting the cucumber. Glue in settings.json file as well.

I did try the same previously for .cmd and .ps1. I was getting the below error.

I'm not on windows, so tried to ask chatgpt to check, that's the suggested code:
const { spawn } = require('child_process');
const path = require('path');

// Assuming `bddgen` is installed as a dependency in your project
const bddgenPath = path.resolve(__dirname, 'node_modules', '.bin', 'bddgen');

const child = spawn(bddgenPath, ['--verbose'], {
  stdio: 'inherit',  // This option will output the child process logs in the parent process
  shell: true        // Helps with path resolution on Windows
});

child.on('error', (err) => {
  console.error('Failed to start subprocess:', err);
});

child.on('close', (code) => {
  console.log(`Child process exited with code ${code}`);
});

Please try with it.

Also, wanted to check on the below...

Lets track it in a separate issue. Please share project structure or try to reproduce it based on https://github.com/vitalets/playwright-bdd-example

Version 8.0.1 shipped improved output for npx bddgen. Now it prints Done when all files have been generated.
It allows to detect end of process with third-party tools.
Example output:
$ npx bddgen --verbose

Loading features: features/*.feature
Found feature files: 1
  - features/homepage.feature
Loading steps: features/steps/*.ts
Found step files: 2
  - features/steps/fixtures.ts (0 steps)
  - features/steps/index.ts (3 steps)
Clearing output dir: .features-gen/**/*.spec.js
Generating Playwright test files: 1
  - .features-gen/features/homepage.feature.spec.js
Done (0.5s).


reinstall/upgrade/install: always output options.

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew tests with your changes locally?

This is both easier for debugging and to communicate with users what is being done.
Found this useful when working on https://github.com/Homebrew/homebrew-core/issues/7630.

Should we warn when we throw out an option that's unrecognized?

Not sure. It's debatable how much that'll be useful information vs. options passed for other formulae, bad stuff in the tab, etc. Thoughts?

I guess if people are doing
brew install --without-test openssl python

they don't want to be told that --without-test is unrecognzed with respect to python.
Also, I guess we don't want user reports every time we retire an option because it has become a baked-in-always-on feature.
But it does still feel icky to silently drop options, especially if they were manually entered on the command line as opposed to coming from the tab.

Let's ship as-is and can iterate on adding more stuff in here if people 😭

:+1:


Gradle project sync failed on release proguard settings

Error:
Error:(56, 0) Cannot convert the provided notation to a File or URI: [./proguard-rules/android-support-rules.pro, ./proguard-rules/autovalue-rules.pro, ./proguard-rules/okhttp3-rules.pro, ./proguard-rules/picasso-rules.pro, ./proguard-rules/retrofit2-rules.pro, ./proguard-rules/retrolambda-rules.pro, ./proguard-rules/rxjava2-rules.pro, ./proguard-rules/okio-rules.pro, ./proguard-rules/picasso-rules.pro].
The following types/formats are supported:

A String or CharSequence path, for example 'src/main/java' or '/usr/include'.
A String or CharSequence URI, for example 'file:/usr/include'.
A File instance.
A URI or URL instance.
Open File

Line:
proguardFiles getDefaultProguardFile('proguard-android.txt'), releaseProguardFiles
P.S. If comment this line build work :)
Thanks
Ubuntu 16.04

This occurs when using classpath 'com.android.tools.build:gradle:2.2.0', it behaves correctly using 2.1.3.

We need to define a solution for abstractly defining a list of Proguard file which works on the latest Gradle build.

Hmmm I use 2.2.1

My guess is that the API changed slightly after 2.1.3 which has broken it for us. Stick with 2.1.3 for now.


feat: locale option for dates and number formatting

verry sorry making trouble with git...
+/- all modifications included, please check...

You can git pull and you'll get my changes into your branch.
The change looks almost good to me. I'm playing with some remaining stuff:

use locale date for ChartJs defaults
add en-GB locale which is more useful for people who non-US dates but still in english.

Ah ok, perfect, I wanted to understand if you had not done the merge because I had to carry out some operations.
In fact I hadn't thought about using chart.js otherwise I would have tried to look at the implementation ...
Maybe you could also enter some other default locale - I have no idea of the nationality of TileBoard users - for example be, cz, tk, dk ... cn?

Maybe you could also enter some other default locale - I have no idea of the nationality of TileBoard users

I think the defaults you've selected are pretty good. We can add more later if needed.

use locale date for ChartJs defaults

This would be a bit tricky actually because ChartJs uses moment to format dates and times and the formats defined by angular-i18n are not always fully compatible with moment...
I'm good with those changes now and will merge if you don't see any issues.

Very well, I think we can proceed with the merge, I will also try to study the chartjs / moment problem ...

why relative path?

If TileBoard is deployed to a non-root path like site.com/local/tileboard/ then absolute would most likely not work. Relative will.

why relative path?

If TileBoard is deployed to a non-root path like site.com/local/tileboard/ then absolute would most likely not work. Relative will.

right

Very well, I think we can proceed with the merge, I will also try to study the chartjs / moment problem ...

Here is what I was experimenting with: 4d0b77536e5d29a69ce4ecaa02002eff2b243e80
This breaks graph tooltips though because the "medium": "d MMM y HH:mm:ss" format from locale files is not supported by moment.

trying to investigate on chart, I created an HIstory item then I got this error:
Code -1 retrieved for http://<IP_ADDRESS>:8123/api/history/period/2021-02-17T19:05:04.995Z?end_time=2021-02-22T19:05:04.995Z&filter_entity_id=sensor.temperatura_cpu.
any idea ?

You are probably hitting this issue https://github.com/resoai/TileBoard/issues/386
I've made a PR with a fix at https://github.com/home-assistant/core/pull/43679 but it was confusingly rejected...

hi Rafal,
yes, this is certainly issue # 386.
I have read everything you wrote in the pull request on home assistant; in fact your solution could be approved as a temporary workaround but the problem should be fixed in a better way.
I looked a little in the Homeassistant code and saw that the History component is asynchronous and therefore also its initialization process. You should probably intervene in the process upstream of the async_setup call and check if CORS has been enabled in the configuration; in that case (and only in that case) it should be correctly enabled for the history resource (as for any others that follow that logic).
I don't know the logic behind HomeAssistant; if you set the flag to true (as in your proposed change) CORS is enabled to any address if nothing has been specified in configuration.yaml?
If this were the case, I think that the auditor was right not to accept your change ... As far as the change concerns the history, it is also true that through that passage you could possibly request sensitive information such as the shutdown and start times of a alarm...
Let's try to think of a solution by looking better in the Home Assistant code!
In the meantime I will move TileBoard to the HomeAssistant server to try out charts and dates!
I will tell you that I am proceeding in the localization of the states of the Weather component. I am also trying the OpenWeatherMap integration instead of DarkSky which - as you know - closes at the end of the year (so I read); I'll let you know how it goes.
See you soon
Michele

yes, this is certainly issue # 386.
I have read everything you wrote in the pull request on home assistant; in fact your solution could be approved as a temporary workaround but the problem should be fixed in a better way.

We could discuss more on the HA issue but the last time I checked, I didn't see other API actually checking the origins whitelisted by the user.

OK ...
Please note that I am NOT a Python / Javascript / Angular programmer ... I am a really very  old C / C ++ programmer!
For this reason I find it really difficult to deal with things like: blocks defined by indentation, untyped variables, weird ways of defining the visibility of methods and objects, implicit initialization processes, like init.py and bad things like that.
Now, but then, there is no other way to activate CORS on history than to install it on localhost?
Okay, let's go, I've been thinking about these kinds of changes, tell me what you think ... (at least on a theoretical level, it's obvious that the Home Assistant folks will never accept them ... Patience, I'll have to fork everything ... I have to have fun somehow ...)
Since History is an API, the idea is to move the definition of the HistoryPeriodView class to the api component ...
Therefore:

move

class HistoryPeriodView(HomeAssistantView):
"""Handle history period requests."""
url = "/api/history/period"
name = "api:history:view-period"
extra_urls = ["/api/history/period/{datetime}"]

def __init__(self, filters, use_include_order):
    """Initialize the history period view."""
    self.filters = filters
    self.use_include_order = use_include_order

bla, bla, bla...

in api component (and relative initialization)
OR
create a derived class in api.py leaving this in place
class APIHistoryPeriodView(HistoryPeriodView):
"""View to handle Status requests."""
url = URL_API_HISTORYPERIOD     <-- DEFINE THIS IN CONST AS THE OTHERS AND REMOVE CORRESPONDING BASE CLASS DEFINITION
name = "api:status"

and then do the initialization at the right time!!!
async def async_setup(hass, config):
"""Register the API with the HTTP interface."""
hass.http.register_view(APIStatusView)
hass.http.register_view(APIEventStream)
hass.http.register_view(APIConfigView)
hass.http.register_view(APIDiscoveryView)
hass.http.register_view(APIStatesView)
hass.http.register_view(APIEntityStateView)
hass.http.register_view(APIEventListenersView)
hass.http.register_view(APIEventView)
hass.http.register_view(APIServicesView)
hass.http.register_view(APIDomainServicesView)
hass.http.register_view(APIComponentsView)
hass.http.register_view(APITemplateView)
ADDED!

hass.http.register_view(APIHistoryPeriodView)   OR  hass.http.register_view(HistoryPeriodView) IF MOVED INSTEAD MAKE DERIVED CLASS

if DATA_LOGGING in hass.data:
    hass.http.register_view(APIErrorLog)

return True

I have not checked what happens with regard to the dependencies also local of the HistoryPeriodView class or its references but I think it is an easily solvable problem.
In this way I believe the safety principle is respected and yet there should be no interference between the levels because api and history are both in components.
Finally, I didn't even try to figure out what the timing of the Home Assistant initialization workflow was (i.e. the reason for the current malfunction) because the project is too complex and there are no flow and class diagrams ... they have everything in mind, I don't!
See you

Sorry, but at the moment I don't have time to go deep into this and try to understand how to fix this the best way.
I would prefer to discuss those things inside appropriate issues because otherwise, things get messy and hard to follow and find. This issue is about locale formatting so it's kinda out of place to discuss CORS issues here.


PKGBUILD: Add missing dependency and cleanup

This adds the missing  pcsclite dependency to the build. Also a couple
of cleanups:

The vcs package should reverse conflict. This is not the job of this package
quoted $pkgdir as it might contain spaces
Remove the --version check as any linking issues should be detected during build
Add --frozen and ensure the building in inline with guidelines

https://wiki.archlinux.org/title/Rust_package_guidelines
Signed-off-by: Morten Linderud<EMAIL_ADDRESS>

Thanks, @Foxboron!
Do you know what would be the best way to release these AUR packages (based on tag push)? I've seen some GitHub Actions floating around that deal with AUR expecting a standalone git repo push, and experimented with git subrepo, but it all seems hacky.

I use subtrees for my stuff. Should be fairly trivial to implement.
https://github.com/Foxboron/sbctl/blob/master/Makefile#L52

I incorporated most of your changes in release v0.0.7 (with credit, was easier this way).
If you have more suggestions regarding that latest PKGBUILD, I'd be happy to take them!

You need to revert this line: https://github.com/solokeys/solo2-cli/commit/1a1089f6ccd3e9193dcbdedced6df2e46bc02bfa#diff-7b4a3ca95ccfe814ecfc3fab667be2f639e808c7ad691627db1e57602dd17f9aL16
makepkg is going to look for the file existing before downloading, and in this case it is always going to exist regardless of the package version. This works in a CI context, but building manually from the AUR is going to just repackage the same solokey version every time.

Thanks. I think I managed to mess up the subtree push (probably by doing a force push on the main branch). Is there a way to "rebase the pkg/arch directory onto the AUR repository"?

Is there some way to suggest to the user that PCSC should be running for most things to work? I have the ccid dependency now (just pcsclite is not enough), and an info to the user if they e.g. run solo2 ls or solo2 update with PCSC off, but that still doesn't communicate "if you want to use this, you should probably systemctl start pcscd.

You could do a post install hook that echos a recommendation. But this is Arch and the fact that pcscd should be running for smartcards to work is documented over several places.
Example here: https://github.com/archlinux/svntogit-community/tree/packages/cri-o/trunk
I didn't realize ccid had some more stuff. I have all of this running and was mostly fixing the build error :)


Fix issue #756 (restore HTTP authentication support)

@kennedyoliveira Here is the fix restoring basic authentication. Most of the code there is the test code, to make sure we do not miss this feature in the future. We do not use HTTP basic authentication as it is inherently insecure.

Thanks @tbak, we have folks that use it in conjunction with SSL.  Looks good!

NetflixOSS » eureka » eureka-pull-requests #585 SUCCESS
This pull request looks good

@tbak, thank you very much! I know it's not safe, but i was planing to use with SSL as @spencergibb, there is any alternative to this method for eureka?

There's some SSL certificate security, but other than that...

@kennedyoliveira We are using client side certificates, to authenticate both sides of the connection.

:+1:

@tbak, sounds interesting, how is that?

@kennedyoliveira Sorry, I have to take it back about the client side certificate validation. There are however some ways to do that (via SSL system properties or creating custom EurekaJerseyClient).

@tbak, hmm i will search about that, i don't know much about SSL, just the basic, anyway, thank you for fixing it! If you have any source of documentation/books/ anything about this case and could tell me, i appreciate :D


the question about TE quantification

Hi juheon,
I have read your recent published paper "Epigenetic therapy potentiates transposable element transcription to create tumor-enriched antigens in glioblastoma cells", it is really solid results for TE specific antigens for tumor.
There I have some questions:

I noticed that you normalized the TE for gene's expression, but you do not mention the gene's expression whether normalized for TE. In my opinion, they should nomalize separately.
Meanwhile, I did not see the reference of TE's locus refered, I am curious about how many reference TE contain.
Yours sincerely.

Hello,
For TE annotation, we utilized Repeatmasker from the UCSC Table Browser for the hg38 genome assembly.


[IoT] Adds IoT Operations Extension v0.4.0b3

Notes for this release can be found here:
https://github.com/Azure/azure-iot-ops-cli-extension/releases/tag/v0.4.0b3

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

IoT


Add doc to all-in-one install mode

doc is here https://github.com/IBM/cp4waiops-gitops/blob/release-3.3/docs/deploy-cloudpak-with-sample-apps.md


Search feature is not working

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Expected Result:
Jump to the chat
Actual Result:
Blank screen and JS error
Action Performed:

CMD+k
Select a person to chat
See blank screen

Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platform:
Where is this issue occurring?
I only tested in web and in staging
Version Number:
Notes/Photos/Videos:

Expensify/Expensify Issue URL:
View all open jobs on Upwork

We're also able to reproduce this.
Another bit of info, this same error is displayed when trying to create a new chat or group

This was me thanks I broke it.

This doesn't happen on main and the PR that will fix it is here -> https://github.com/Expensify/Expensify.cash/pull/2525
So, I also fixed it already, but the timing is just bad.

So, should we CP that to staging?

Sorry, no looking into it some more and it's broken. I should probably quit while I'm ahead.


Theme is not set properly

The app refuses to exit dark mode. This may be due to having omnirom theming on my device (even though that is set to light mode).

Hmmm. Your phone might be telling MNML that night mode is enabled globally on your device, in which case the resources are overriding the manual setting which should probably be hidden.

Yeah I figured it was my phones themes. The theming doesn't apply to any other non-system apps, so I'm confused why it did it with MNML.

MNML specifies night theme overrides that Android will automatically use if the device is in night mode, this is a recent change for Android Q dark mode support.

Oh I see. That makes sense then.


Propagate scaled attribute through IRISMapCube slicing

This PR alters the slicing of IRISMapCube so that the scaled attribute is propagated.

Hi @BaptistePellorceAstro.  Could you give this a quick review?  It's only a couple line change.

Thanks @BaptistePellorceAstro


Error during build.

ERROR  (node:19700) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)

ERROR  failed to load config from D:\Projects\vite-template\vite.config.js

 ERROR  error during build:

ERROR  error during build:
D:\Projects\vite-template\node_modules\vite-plugin-webp\lib\vite-plugin-webp.esm.js:6
import fs from 'fs';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1088:15)
    at Module._compile (node:internal/modules/cjs/loader:1123:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)

I have   "type": "module", in package.json. So I don't understand why I get this error.
What I need to do it basically convert jpg & png to webp and create a picture tag with an srcset for webp and a fallback jpg/png in dist/index.html.
I added :
    webp({
      include: path.join(__dirname, 'index'),
      imageType: ['.png', '.jpg'],
    }),

It looks like you should update your syntax to es6. There are things like 'var fs = require('fs');' inside of the plugin.

Same error with:
import fs from 'fs';
^^^^^^
SyntaxError: Cannot use import statement outside a module

Same.  Hope the dev fixes this.  Vite lacks image conversion plugins.

ERROR  (node:19700) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)

ERROR  failed to load config from D:\Projects\vite-template\vite.config.js

 ERROR  error during build:

ERROR  error during build:
D:\Projects\vite-template\node_modules\vite-plugin-webp\lib\vite-plugin-webp.esm.js:6
import fs from 'fs';
^^^^^^

SyntaxError: Cannot use import statement outside a module
    at Object.compileFunction (node:vm:360:18)
    at wrapSafe (node:internal/modules/cjs/loader:1088:15)
    at Module._compile (node:internal/modules/cjs/loader:1123:27)
    at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:169:29)
    at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:530:24)

I have "type": "module", in package.json. So I don't understand why I get this error. What I need to do it basically convert jpg & png to webp and create a picture tag with an srcset for webp and a fallback jpg/png in dist/index.html. I added :
    webp({
      include: path.join(__dirname, 'index'),
      imageType: ['.png', '.jpg'],
    }),

It looks like you should update your syntax to es6. There are things like 'var fs = require('fs');' inside of the plugin.

Please provide your machine information and version

Same here.

Any news on this?

Also having this issue, really want to use this plugin.