RUPD and TICK Specification Discrepancies

This concerns the Reward Update and Chain Tick Transition rules.
Page 75 Formal Spec:

In the formal spec the createRUpd function takes 3 parameters, while in the code there are 4 parameters. The first parameter should be the epoch. Relevant code is here: https://github.com/input-output-hk/cardano-ledger-specs/blob/25f504bd95104607be722979eb911f8330d1a921/shelley/chain-and-ledger/executable-spec/src/Shelley/Spec/Ledger/STS/Rupd.hs#L75

This is also reflected anywhere else createRUpd is mentioned such as on page 63 of the formal spec.

Page 76 Formal Spec:

I believe the "s" in Fig. 65 should be called "slot" to be consistent, this is what is is called in the code.
The ru' and es' variables in the code should be ru'' and es'' to be matching the formal specification in Fig. 65. Relevant code: https://github.com/input-output-hk/cardano-ledger-specs/blob/25f504bd95104607be722979eb911f8330d1a921/shelley/chain-and-ledger/executable-spec/src/Shelley/Spec/Ledger/STS/Tick.hs#L113-L115

I think that the right thing to do here is to make both the code and the spec pass slotsPerEpoch to createRUpd. The complication comes from the fact that slotsPerEpoch is a constant in shelley, but the hard fork combinator can change it, so createRUpd was using the epoch number to get slotsPerEpoch.


ObjcProxy interacts poorly with weak references

I have an API that has an interface +j +o object (call it "Platform") with an interface +c delegate (call it "Delegate") that are going to want to talk to each other. The easiest and most natural way to break the refcount cycle is to have Platform retain a weak reference to Delegate, since a Platform matters exactly as long as a Delegate is interested in it.
But I can't do this since Platform's reference to Delegate is actually to a Djinni proxy that nobody else retains a reference to.
An alternative would be to have some mechanism of keeping track of all the Platforms that currently matter, and some way of notifying Delegates when platforms go out of scope (I suppose a did_finish method or something), but this is adding needless complication to the API.
I'd love to hear about other alternatives.

The way we solve this is to split the Delegate up in two where one half is registered with Djinni and it itself has a weak reference to the actual Delegate that is doing the real work.
In our case it's typicall the ViewController/Activity owning a +c ViewModel and also a +o+j ViewModelDelegate.  Threfore ViewModelDelegate is its own type and holds a weak reference to the ViewController/Activity to break the cycle. If ViewController/Activity implemented the ViewModelDelegate interface there would be a ref cycle and it would need manual breaking in viewDidUnload or onDestroyed.

So you solve this with ViewController (strong) -> ViewModel, ViewController (strong) -> ViewModelDelegate, ViewModelDelegate (weak) -> ViewController. And I suppose ViewModelDelegate (weak) -> ViewModel?

ViewController (strong) -> ViewModel
ViewModel (strong) -> ViewModelDelegate
ViewModelDelegate (weak) -> ViewController
The ViewController does not require a reference to the Delegate and the Delegate does not need to know about the ViewModel, it's only job is forwarding calls to the ViewController because in a "typical" OC-only world one would have the ViewController implement the ViewModelDelegate protocol and the reference to the delegate is weak, but that's not possible here. So if the ViewModel owner implements the ViewModelDelegate it has to break the cycle manually. That's why we have an additional object inbetween. So when the ViewController dies it takes the ViewModel with it, resulting in the Delegate's death as there are no other refs to it, and if there are, then the weak pointer is nil and all calls get dropped.
In Java the whole thing works the same except weak references in Java are a bit more tedious to work with.

Fair enough.  Since Owner doesn't need to do anything to Delegate aside from break the refcount cycle, I used something sort of like this to hold the ref:
https://gist.github.com/mrdomino/5cd01e67b6ccf9498433

In Java the whole thing works the same except weak references in Java are a bit more tedious to work with.

Can anyone tell me if using a weak reference is necessary in Java in the case that mknejp describes? It appears to me that the system has a simple reference cycle that the GC is going to detect and handle appropriately.


Correct typo in docs > Get Details > Smart contracts & dApps > Smart contracts and signatures > Introduction.

This is a small typo correction. We have 'Alog' where we should have 'Algo'.

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


December 2023 iteration plan

I'm not sure if we'll be able to land enough new features to warrant a new minor release as this cycle is cut short due to vacations around Christmas. It might happen that we'll skip this one and move it to January. That said, we'll likely cut a patch release before ending the year.
I kinda do want to spent time updating our site and docs as well.
The current plan is to work on these items, although it's likely that they will continue into January.

[ ] View Transitions https://github.com/denoland/fresh/pull/1532
[ ] HMR explorations
[ ] Support JSX precompile transform
[ ] Pending states for Partials

I kinda do want to spent time updating our site and docs as well.
I noticed while reading the blog that the docs still use a lot of the deprecated interfaces. It should be a pretty quick fix to ensure it avoids deprecated interfaces, and I might help out with a PR, but I think that would help a lot for existing and new users to get a feel for the "suggested" approach.

Is this repo dead?

@mustafa-hanif What makes you say that?

Next roadmap plan is here https://github.com/denoland/fresh/issues/2363


Discord Invite is broken

I tried to join the server but it tells me the invite link is invalid.
I never joined the server before so I can't be banned

https://discord.com/invite/rtBQX5D3bD


[feaLib] use feaLib's addOpenTypeFeaturesFromString function

feaLib's API is in constant change. See https://github.com/behdad/fonttools/pull/556
In the latest fontTools HEAD, the function addOpenTypeFeatures now takes either a path or a file-like object as the input featurefile.
A new addOpenTypeFeaturesFromString was added to parse features from a string -- which is what ufo2ft wants to use. The 'filename' argument is optional in this case, as it's only used for error messages and relative include paths (a bit unusual for a feature files contained inside a UFO folder).

(a bit unusual for a feature files contained inside a UFO folder)

It's not unusual, often used to include family FEA file.

Oh sorry, I shall retract my statement then :)


RPC Client Library

ACs

[ ] We are able to build a new program that imports the interface and is able to make calls to the RPC node
[ ] RPC server & client make use of this interface

Notes

Would be helpful to have name of method, the serializer for request, deserializer for response, request handler in one place
Currently we build the server from a hardcoded builder command
A crate for interacting with Filecoin (i.e. Forest & Lotus RPC servers)
This would include a refactor of RPC methods in RPC router
This would be the first step in testing our RPC programatically
This would be like a web3.js in Rust for Filecoin

After looking at Lotus, I think this feature will be essential for authorization and permissioning. It also shouldn't take me too long, and should unstuck me to better implement JWT authentication #997.
My approach I'm thinking is going to be to loosely replicate the data structure in this file:
https://github.com/filecoin-project/lotus/blob/b54b1303f9f6bcc3b57ae25cfc1174b59f44b943/api/apistruct/struct.go
It would be in two parts:
/// permissions.rs
pub enum Common {
    AuthNew {
        name: 'Filecoin.AuthNew',
        auth: Authorization::Admin,
        input: auth_api::auth_new::<DB, KS, B>,
        output: Result<String, jsonrpc_v2::Error>,
    }
}

And then I'll have a static const HashMap using https://github.com/matklad/once_cell where I can do iteration and lookup with the key as the method name string.
@creativcoder and I discussed options such as lazy_static and phf, but we wound up on once_cell so we can avoid the use of macros. This will create the static const HashMap between method name and its corresponding enum member at compile-time.
Thoughts?

Interesting. If we do method routing using the static HashMap, then we won't need to use jsonrpc_v2, if I'm understanding this correctly. Is that right?

We will, I'll just build the router at runtime by iterating over the correct hashmap(s). Also, lotus can be configured to provide a few different APIs; for mining, storage, fullnode, etc.

So, I've been working on this for about a week now (excluding my work on #1033), and I'm gonna give you guys an opportunity to call this a "research spike" and have me work on other things. However, if you do give me the opportunity to solve it, I think I have the knowledge needed to do so. I'll provide some of that knowledge here, to report on requirements and provide recommendations of priority.
So, first some background.
I looked into OpenRPC (such as via https://github.com/etclabscore/ethereum-json-rpc-specification), and I find it to be of limited utility. The API definition is in JSON. It'd be one thing if there were existing OpenRPC definitions, but that's unfortunately not the case.
Further, authorization (access levels) is not something OpenRPC has properties available for us to describe, which is the major "win" I wanted from this. Ideally, we'd have a builder pattern akin to the one here:
https://github.com/ChainSafe/forest/blob/d245f14cbcb0f7c0848fbddbdf802931b83b35e8/node/rpc/src/lib.rs#L50~L204
But it would also allow us to describe endpoints like this:
pub mod auth_new {
    pub const METHOD: &str = "Filecoin.AuthNew";
    pub type Params = (Vec<String>,);
    pub type Result = Vec<u8>;
}

These types and constants can then be referenced in handlers and router builders.
I also wanted to describe access in an enum like this:
/// Access levels to be checked against JWT claims
pub enum Access {
    Admin,
    Sign,
    Write,
    Read,
}

That way it could be easily matched against validated JWT claims.
I could do that by building an access table like this:
/// Access mapping between method names and access levels
/// Checked against JWT claims on every request
pub static ACCESS: Lazy<HashMap<&str, Access>> = Lazy::new(|| {
    let mut access = HashMap::new();

    access.insert(auth_new::METHOD, Access::Admin);
    access.insert(auth_verify::METHOD, Access::Read);

    access
});

And this would be done referencing the following Lotus code:
https://github.com/filecoin-project/lotus/blob/b54b1303f9f6bcc3b57ae25cfc1174b59f44b943/api/apistruct/struct.go#L50~L776
This approach would work fine for the jsonrpc-v2 backend, considering its implementation of the builder pattern for its router as linked above.
I also investigated Parity's work on jsonrpsee, and while promising, I find its practical utility limited by its use of procedural macros.
In fact, macros have been a major headache with regards to making a useful abstraction. The reason being, variables can't seem to be passed to jsonrpsee's client, and several other Rust JSON-RPC clients also employ this approach to describe the client API.
Ideally there would be a client builder pattern, similar to jsonrpc-v2's approach. I haven't been able to find anything existing that provides that, however.
I'd estimate it'd take me a month to drive this home, but I'd recommend sandbagging that estimate 2x, like the refactor of the HTTP server, so more like 2 months. I'm just being overly cautious, which I think is important to communicate while undertaking these more open-ended refactors.
I think it'd be very worthwhile to solve this, but only if we do it the right way. That said, I think we'd get more bang for the buck if we focused on the actual CLI client implementation using the existing 0.1.0 version of the jsonrpsee client. Work there will have limited reusability due to its use of macros, but I think the Forest client's lack of certain useful commands that the lotus client has reduces its utility much more, and thus, should be of higher priority to address.


Update version of evv4esm

Fix for E3SM issue 4759 (https://github.com/E3SM-Project/E3SM/issues/4759)

@mkstratos, is this ready to deploy?  If so, I'll do so tomorrow.

@xylar Yup, this should be good to go, the new evv4esm version has propagated to the conda-forge repo

This has been deployed on Chrysalis (and Anvil), Andes, Badger, Compy, Cooley and Cori.
Permissions are still updating, but should be done in the next few hours


fix: presets ls

:tada: This PR is included in version 4.0.0-stage.1 :tada:
The release is available on:

npm package (@stage dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bump Dependencies #136

Bumps dependencies for product-is.

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

closing as https://github.com/wso2/product-is/pull/6232 has more updates


Make the new UI work in Firefox

There are a few things that don't work in Firefox right now:

Polymer and Angular don't get along very well. However this is easy to fix, just load webcomponents.js instead of the lite version.
Some Angular bindings don't seem to get updated automatically (i.e. the board doesn't resize properly and the scoresheet as well). I don't know how to fix this yet.
merge.js (used by chessground) causes a "too much recursion" error. The reason seems to be that whenever the chessground config (including legal moves, so after every move) is updated, the complete config is merged with itself and then with the new on (see https://github.com/yeikos/js.merge/blob/master/merge.js#L121). Especially the piece list takes a while. Fix: change merge.js (start at index 1 instead of 0 if clone option is false).

So the main problem seems to be number 2 at the moment.

and 3. have been fixed completely.
has also largely been fixed, the only problem is that the board still doesn't resize automatically.


Add demo cert migration

Description
This PR adds the secure migration to add the demo cert to the client_certs table. All secure migrations have already been uploaded to their respective environments (exp, stg, and prd have empty placeholder files). It is ready to be deployed and tested!

Warnings

:warning:
Please add the JIRA issue key to the PR title (e.g. MB-123)

  Generated by :no_entry_sign: dangerJS against 26bafc07267b3e5fd6a167f0dfeab9ebf968f88f


Problem deploying files with non-ascii characters

Environment

Server - VSTS
Agent - Hosted

Issue Description
I have a .js file that contains non-ascii characters (french/spanish translations) and the multi byte characters seem to be converted when deployed to an Azure App Service using the "Azure App Service Deploy" task v3
One of my build artifact files contains a js file with some language translations such as:
{"user_name": "Nom d’utilisateur"}
After it gets deployed I have
{"user_name": "Nom d���utilisateur"}
I'm I missing some setting to handle this?

Sorry, closing this as its not a bug here.  I have tracked this down to an earlier task that does token replacement.


i beg you please take this time

im new to python please can you fix this error 'authentication' object has no attribute 'user_path' please i need this good tool so badly ✅

replace authentication().start() with visual.initialize() at the bottom


Tracking usage and Exception events

Looks like we can use Google Analytics  to gather usage and exceptions related information for Lazymine.
https://github.com/ggendre/GALocalStorage

Added user session tracking with 2f8d895d5b1f22df08438aad83dcd4741c607b23


SP-Intiated SLO - need to destroy session before requesting SLO

When Logout is initiated from Drupal, it looks like the onelogin_saml Drupal module doesn't actually destroy the user's session until the Logout Response comes back from the IdP. (The initial Drupal logout is interrupted when the module's user_logout_hook redirects and exits.)
When the Logout Response doesn't come back, users are not logged out - and these users probably don't know they aren't logged out. Worst-case scenario is when the IdP session has timed out. In this case, the user ends up at the Login page of the IdP. The Logout Response never comes back. The user cannot log out of Drupal unless he logs back in to the IdP and then logs out.
IdP = Onelogin, in my case.
I can provide a trace, if desired.

Why the Logout Response doesn't come back?
The issue that you reported is the common SLO problem related to SAML.
But at the SAML workflow for SAML SSO Web Profile, the session of the application is destroyed once the Logout Response arrives and not before.

The example I gave is a common one: The session at the IdP has timed out. In this case, OneLogin does not return a response. We need to have a longer local session for our Drupal app, so this situation will frequently happen.
It seems like your Moodle plug-in - which we are also using - does destroy the user’s local session before requesting SLO from the IdP.
Not sure what you mean by "But at the SAML workflow for SAML SSO Web Profile, the session of the application is destroyed once the Logout Response arrives and not before.” Are you saying that the SAML specification mandates this? (That would be news to me.) Or that the Drupal module behaves this way? (Which I know.)

On May 27, 2015, at 4:51 PM, Sixto Martin<EMAIL_ADDRESS>wrote:
Why the Logout Response doesn't come back?
The issue that you reported is the common SLO problem related to SAML.
But at the SAML workflow for SAML SSO Web Profile, the session of the application is destroyed once the Logout Response arrives and not before.
—
Reply to this email directly or view it on GitHub https://github.com/onelogin/drupal-saml/issues/19#issuecomment-106070337.

See line 1218 in the current SAML Specification (I'm reading the pdf version). It says "The SP sp1.example.com destroys the local authentication session state for the user and then sends
the idp.example.org identity provider a SAML  message requesting that the user's
session be logged out."
This prevents an accident that might leave the user logged in without their knowledge.

@cagedartist, thanks for reporting this issue.
At the OneLogin platform we are reviewing the session time out issue.
And you were right, in the way how the SP-Intiated SLO workflow should work. I mistook the flows.
I will fix that asap.

@cagedartist, please let me know if that commit solved your issue.

Thanks. I’ve done some testing. The change destroys the user session before redirecting, so it fixes the worst-case scenario. User is always logged out.
Not sure this is related — it might be a different issue: I’ve had a problem with the drupal_saml_login cookie. I had to disable the cookie code to get SLO to work. Other departments at the college have reported the same problem. The code and logic seem simple, but I’ve found that the cookie value is 1 when it should be 0 (user has logged out) and it’s missing when it should be 1 (user is logged in with SSO). It looks like the purpose of the cookie is to avoid SLO if the user has logged in locally.  Correct?

Yes that was the case. Maybe you had some phantom cookie from a previous attempt.
Please clean all cookies and let me know if something is wrong.


Add support for simulation in ungauged catchments (16)

This can be done by running models for nearby calibrated catchments and averaging the outputs.
TODO: Clarify method and split in smaller issues.

I will have Jean-Luc do this task. We'll need to upload a dataset of parameters for pre-compiled models and predefined catchments. The algorithm itself has been built in Matlab, now we will convert it to Python.
Steps:
1- Push a series of catchments to the server (including contours and observed streamflow)
2- Calibrate the 3 main hydro models on each site using the RAVEN framework once it's functional, and using observed climate date (we can provide reference climate data if need be, i.e. gridded NLWIS data for now)
3- Convert Matlab Code to Python for the regionalization strategy
4- Implement the WPS to automate the process given an input catchment contour (i.e. select 5 closest calibrated watersheds with the model chosen by the user, run the hydromodel on the ungauged site using the parameter sets from these 5 catchments and the gridded climate data at that site, then average the 5 outputs).

Could this be relevant: doi:10.5194/hess-15-3591-2011 ?

It is actually a relevant topic in theory, but is difficult to apply in practice. I did my PhD partly on this, the problem is that the regression relationships between model parameters and exogenous characteristics are very difficult to model and not very robust. So it's not really an applicable method... yet.

Ok, I got carried away. We're looking to implement methods people are familiar with, not do research.

Maybe in maintenance phase! It's a good idea though, just not mature enough.

@marteljeanluc
@marteljeanluc
This will be accomplished in 3 phases:
(1) Pre-calibrate HMETS, GR4JCN and MOHYSE on CANOPEX database in Canada and USGS database in USA. This will give a set of parameters for use in the regionalization method application.
(2) Implement the Spatial proximity regionalization method (with inverse-weighted donor averaging). Need the climate data for the ungauged catchment, latitude, longitude and area, as well as any other info to run the model at the ungauged site. The algorithm finds the parameter sets from the closest catchments that have a reasonable calibration NSE (>0.7 usually, can be reduced to 0.6) and runs the hydro model on the ungauged site using these parameters. We can then use 1-10 "donor" catchment parameter sets to average out the hydrographs.
(3) Expand on this by adding physical descriptors to the datasets (can use PAVICS GIS WPS for this...) and implement the physical similarity regionalization variants.


add thumbnail regeneration

We usually add 'Thumbnail Regeneration' functionality via the very popular "Regenerate Thumbnails" plugin by Viper007Bond. ref: https://wordpress.org/plugins/regenerate-thumbnails/
However, this plugin only regenerates thumbnails from images that are stored locally. So if your images are only stored on Google Cloud Storage (GCS) and not locally, this plugin will skip thumbnail regeneration for that image.
We need to recreate this thumbnail regeneration functionality as a feature of WP-Stateless with the modification that it regenerates images that are stored on GCS.

Done


[Bug] BetterDiscord not working

BetterDiscord not working on discord PTB
Screenshots

Discord Version
<PTB Stable 115008 (97968e1) Host 1.0.9003 Windows 10 64-Bit (10.0.19044) >

Discord released an update that broke Discord for Canary and PTB. This is also mentioned in #1214

same betterdiscord is not working anymore :<

Yup latest update blocked better discord

BetterDiscord not working for me either

These comments are entirely unhelpful


Default alignment option + ability to align at index 0.

I add a couple of features that I wanted for commenting that others may find useful:

an option to set the default alignment value used by commands which don't have a specific intended alignment.  Using this I can specify how I want NERDCommenterToggle to align my comments.
a new alignment value, 'start', which indicates that the comment characters should be inserted at index 0 (column 1) of the line.  As a personal convention, when I'm temporarily commenting code out, I prefer my comment delimiters to be at the very start of the line so that I can quickly pick out what comments are temporary vs permanent.

In addition to updating the help file to document these new features, please also note one gotcha where using the 'start' alignment with g:NERDRemoveExtraSpaces can result in the undesired removal of spaces.  I thought about adding some code to detect and warn the user in this situation, but decided against it at the time.  Its something worth considering when decided whether these changes are worth merging in.

+1

:+1:

+1

+1 exactly what would come handy for me

@scrooloose  Why the on Earth this haven't been merged yet! You seem to be alive, judging by your activity on github. Maybe you would accept a little help with managing this code?

Fork notice: With the upstream project sitting stale after nearly 8 months since the last activity, 71 outstanding pull requests, no comments from the original developer, and dozens of developers duplicating efforts while scratching their own itches, I've decided to step in and run a fork for a while. Hopefully the original developer will eventually consider picking this plugin up again or adding more maintainers so that the user base doesn't end up fragmented, but for now I would invite anyone interested in the latest updates to consider installing from and contributing pull requests to my fork.
About this PR: I have merged this PR as is. Please consider installing the plugin from alerque/nerdcommenter for this and (so far) over two dozen other updates.

Change of plans. Thanks to @scrooloose who has added me as a maintainer to this repo, I'll be going through and taking care of business here instead of in a fork.
Thanks for your contribution @purpleP!


question: how to test a cask binary?

Various casks provide binary stanzas to symlink some binary or script within a cask-installed app.
Would it be possible or desirable to provide some lightweight functionality to automatically test that the binary actually results in a working command?
For example, the praat cask creates a symlink
/usr/local/bin/praat -> /opt/homebrew-cask/Caskroom/praat/#{installed_version}/Praat.app/Contents/MacOS/Praat

It would be nice to automatically check when the cask is tested or installed that running praat actually does run that .../Praat.app/Contents/MacOS/Praat binary.
Because sometimes paths inside apps are changed upstream, and the symlinks would break on installing an updated cask. Or some other stuff happens upstream, and the binary itself no longer works.
Catching this sort of issue during the test builds, and guarding against it during postflight might be a good idea.

I don’t really see this as desirable, because it really isn’t a problem. Also, with https://github.com/caskroom/homebrew-cask/issues/15603 this will only become less of a problem. That said, I also wouldn’t mind.
Lets see other opinions.

I've floated a simple test balloon in #18879

That’s not really the same thing as a test. You’re using postflight for it, mudding it’s usage. Either we make a proper test block for this, or we don’t do it at all.

@vitorgalvao I agree that's not what the postflight is for; it was intended as a proof of concept.
  binary 'Praat.app/Contents/MacOS/Praat', target: 'praat'

  # verify binary
  postflight do
    cmd = "praat --version"
    raise "Cannot run command `#{cmd}`" unless system cmd
  end

does provide the functionality I proposed above, though: it fails the installation if the praat command provided by the binary cannot be run.
Would it be possible to port the test block logic over from the main brew formula code?

Would it be possible to port the test block logic over from the main brew formula code?

Might be (especially with https://github.com/caskroom/homebrew-cask/issues/14384), but we’re still not agreed on if this is desirable (waiting for more maintainers to chime in).

Fair enough. Thanks for linking to the integration issue -- I'll subscribe to that!

Seems like there isn’t much interest in this. Closing.


Update with new language syntax

Purpose

Updates the Ballerina Quick Tour – Community Engagement page with the new language syntax changes.

I guess firstNumber and secondNumber makes more sense in a quick start tutorial.


Create YouTube setup video(s)

Create a YouTube video to show how to setup the callattendant. The video should cover the following topics

Hardware setup: Show how to connect the Pi and modem to the home phone system
Software setup: Show how to start and configure the call attendant
Software usage: Show how to use the web interface
Advanced setup: Show how to configure running as a service
Advanced add-on: Show how to add and configure LED indicators

I have no plans to do this.


update(hooks/UseWasm): update scap option

What type of PR is this?
/kind bug
Any specific area of the project related to this PR?
/area frontend
What this PR does / why we need it:
This PR updates -e option to use -o engine.kind=replay -o engine.replay.capture_file=some_file.scap for running Falco with snap file.
Which issue(s) this PR fixes:
Fixes  #55
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Rohith-Raju
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Rohith-Raju]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: ec6a09412e453466ea9f68642a636bd009e8150b

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leogr, Rohith-Raju
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Rohith-Raju,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Add Missing Performance Tests for Monitor Query

Add performance tests for

Making a simple query to the service "requests | summarize count() by bin(timestamp, 1h)", "timestamp = P1D"
Use $batch to run 5 queries in 1 api call
Get query statistics (cpu usage / memory / execution time)

@pakrym could you follow up on this issue?

Related https://github.com/Azure/azure-sdk-for-python/pull/19941 and https://github.com/Azure/azure-sdk-for-java/pull/23280

Not done yet. Reassigned to @nisha-bhatia


Ledger device turns off making it impossible to sign certain transactions

See here https://github.com/leather-io/extension/issues/5857
Ledger Nano S+ firmware 1.1.2 and stacks app 0.24.2 (I checked with two devices same model).

:link: zboto Link

Reproduction steps
Connect Ledger to Leather (Stacks)
Click swap in the wallet
Choose a token pair and any amount
Click review and swap
Click Swap
See error: in leather shows loading animation with "Waiting for your approval"
Ledger device turns off, or screen goes blank which makes it look turned off.

Reproduction steps Connect Ledger to Leather (Stacks) Click swap in the wallet Choose a token pair and any amount Click review and swap Click Swap See error: in leather shows loading animation with "Waiting for your approval" Ledger device turns off, or screen goes blank which makes it look turned off.

@314159265359879 seems like you're encountering an issue with your Ledger device when trying to swap tokens using Leather (Stacks). It sounds like your query would be best dealt with by the support team.
I'll have to refer you to the official support live chat with the ticket ID LED07638
Please see the link below to our dedicated support line:
Ledger Network DApps Support Ticket Requests.
Note; Click on the live chat icon at the bottom corner of the page to initiate chat with a live support agent.

Retested with Xverse, the issue is the same there, screen turns off.
used app.bitflow.finance/trade to initiate a transaction to sign on the device.

Retested with Xverse, the issue is the same there, screen turns off. used app.bitflow.finance/trade to initiate a transaction to sign on the device.

@314159265359879 are you able to get it solve with the support team ?

Received a user report that attempting this multiple times caused their Ledger to reset completely, with them needing to re-enter their seed phrase. It happened multiple times after multiple attempts.

Withdraw LP on Alex have the same issue and Alex LP tokens can't send to another wallet, so my fund have been stuck because of this bug.

Withdraw LP on Alex have the same issue and Alex LP tokens can't send to another wallet, so my fund have been stuck because of this bug.

Thanks for sharing, I am checking with the Zondax team for an update on this issue and its resolution. We are aware this is a serious blocker.
This is not an issue with 0.23.3 of the Stacks app, perhaps Zondax has a step by step guide on how to revert to an older version of the app to allow transactions in case of a dire need.

Withdraw LP on Alex have the same issue and Alex LP tokens can't send to another wallet, so my fund have been stuck because of this bug.

Thanks for sharing, I am checking with the Zondax team for an update on this issue and its resolution. We are aware this is a serious blocker.
This is not an issue with 0.23.3 of the Stacks app, perhaps Zondax has a step by step guide on how to revert to an older version of the app to allow transactions in case of a dire need.

Is the sideload the app only work on Ledger Nano S and Nano S plus ?
I only have Nano X.

Withdraw LP on Alex have the same issue and Alex LP tokens can't send to another wallet, so my fund have been stuck because of this bug.

Thanks for sharing, I am checking with the Zondax team for an update on this issue and its resolution. We are aware this is a serious blocker.
This is not an issue with 0.23.3 of the Stacks app, perhaps Zondax has a step by step guide on how to revert to an older version of the app to allow transactions in case of a dire need.

Is the sideload the app only work on Ledger Nano S and Nano S plus ? I only have Nano X.

Hi again, sideloading doesn't work on the Nano X, because that device doesn't allow sideloading by design. In addition, I tested side loading 0.23.3 and that wasn't supported via hub.zondax.ch/stacks when I tried a couple days ago (with nano S+), I have asked someone from Zondax to see what is causing the issue, I have not yet heard back. I will share here when I do have a viable workaround.

You should be able now to install through Ledger Live the previous version on your NanoX while this issue is being investigated

Hey guys, I'm not a developer but an web3 user and ether.fi moderator :)
I'm here to share my experience in the previous 3 days, where I've tried to use Bitflow's pool (stx-ststx) and at the moment of signing the transaction, my Ledger Nano X would bug, do not show the approval part and reset completely to fabric conditions (3 times) in the same scenario. Once, when trying to figure if the problem was in Ledger/Stacks app or Leather/Xverse, I've taken the device out and he went to booting mode for 3 full days on the plug.
Anyways, I see people are aware of the bug and hope to be fixed soon. Thanks!

Hi @rzucher we have rolled back to previous version while we keep investigating this issue. You should be able to instal 23.3 again from Ledger Live. Sorry for the inconveniences.

Hi @rzucher @314159265359879
I am investigating this issue, so it happens after transaction is reviewed and upon approval(where the transaction signing comes in) it crashes?

Hello Natanael, actually my problem went a little bit further my device
actually reseted to fabric conditions three times. it would bug when the
transaction should be appearing, and then it would turn off and back to
fabric. Once it even went to a booting screen where it took 3 days on the
plug to come back working normally
Rodrigo M. Zucher
On Thu, 10 Oct 2024 at 03:39 Natanael Mojica @.***>
wrote:

Hi @rzucher https://github.com/rzucher @314159265359879
https://github.com/314159265359879
I am investigating this issue, so it happens after transaction is reviewed
and upon approval(where the transaction signing comes in) it crashes?
—
Reply to this email directly, view it on GitHub
https://github.com/Zondax/ledger-stacks/issues/171#issuecomment-2404170728,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BL4ZUOC2LFZYNET7CA3VRMDZ2YOIVAVCNFSM6AAAAABOEBRVGKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUGE3TANZSHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

1- No, the transaction (entering stx-ststx pool on Bitflow) never actually goes to the device screen, it only appears as generating/generated on Xverser/leather (tried both)
2- crashes few seconds after requesting the transaction
If you want, drop me your email I can share my logs if you think is useful :)

Can you share those logs here? so everyone can be aware of the data we are looking at. and we can share here parts of it while going through

yep sure, I was double guessing if its ok to share it, anyways here u go:
Uploading Logs RMZ.json…

@neithanmo

In case helpful in debugging, here's a Leather build that logs the tx before it's passed to the device https://github.com/leather-io/extension/pull/5885

yep sure, I was double guessing if its ok to share it, anyways here u go: Uploading Logs RMZ.json…

it seems the link is pointing to this issue, no logs file

@neithanmo

In case helpful in debugging, here's a Leather build that logs the tx before it's passed to the device leather-io/extension#5885

it seems the dev run(to run in testnet with some funds) does not allow doing swaps which I believe is the transaction type that triggers this issue sometimes

We could reproduce the issue and got the testing data we needed. fix on the making via #173

I could signed a swap transaction:
https://explorer.hiro.so/txid/0xb3e88ea9f8319d6bab31a598c5b9c0f3de7ba3cc9d6720b09a0dfbccdbc26d82?chain=mainnet
so will close this issue via #173

@neithanmo hey guys, bringing that up , now on Ledger Flex 😭 , it's not going back to fabric conditions, it just doesn't load transactions. but it was indeed working before Nakamoto... idk

@rzucher what is the version number of the Stacks App and firmware shown in Ledger Live?

@314159265359879 24.2

@rzucher what is your firmware version? maybe you should update it in ledger live

@neithanmo OS 1.1.1 , no update available on my side

I is difficult to tell, the fix was in the UI section, way before transaction is loaded and parsed
the fix was using a rust library that does not use core::fmt implementation for integer to string conversions, we actually have a test from the blob I got here, and runs just fine on flex device.
Let me check again, but it could be dev mode or something, flex is new and we are still adding support for in other ledger applications we have built

Just got my device reseted for the 4th time, I've also raised this matter on support channel of stacks community. It happened specifically when trying to use Bitflow's swap aggregator. Isn't it possible to return the app to previous version like you guys did with nano x? (using ledger flex)


Fixed customer installer link to point to stable.

Description

Urgency

[x] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, and 1.9).
See the contribution guidelines.

The current link is pointing to 1.9.0


how to make the respective sub menu visible?

How can we make the sub menu visible on the initail mounting of sidebar as well as on chnaging the route from the address bar as well.Please Please need help.

hello @Parasbuda
How did you resolve it !

Your wish will not come true because of the following lines in MetisMenu's source file.
https://github.com/onokumus/metismenujs/blob/master/src/index.ts#L67-L69
if (target && target.tagName === 'A') {
  evt!.preventDefault();
}

I can't think of any other solution for now.


Fix requirements list notation in README.rdoc

Previously the (2) bullet point was repeated twice
Down the line, it could make sense to change the README to a Markdown file, which has better support for ordered lists

Thank you! md would be a good idea :)


20354 task share destination selector refactor

Details

This PR's primary objective is to replace the  to  component in the . Also the main search and list section logic have been refactored for performance and reduction of render cycles.
A loading bool flag has been added to BaseSelectionList component.
Fixed Issues

$ https://github.com/Expensify/App/issues/20354
PROPOSAL: no proposal
Tests

same as QA
[ ] Verify that no errors appear in the JS console

Offline tests

same as QA

QA Steps

[ ] On the main screen of the app tap FAB and choose "Assign task"
[ ] Give it a name, move next and select "Share somewhere"
[ ] Check for any differences/odd stuff in the behaviour of the list
[ ] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/134388952/571cc80f-c116-448c-8e7a-1c67ba5815c1

Android: mWeb Chrome
https://github.com/Expensify/App/assets/134388952/16324755-d62b-4eab-bd79-d5e0290da166

iOS: Native
https://github.com/Expensify/App/assets/134388952/8373d1bf-d50a-4bc7-b42c-cc3a864090aa

iOS: mWeb Safari
https://github.com/Expensify/App/assets/134388952/4b070f4c-b497-4a1c-8532-5e9ff175be7f

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/134388952/411ec7ec-04dd-4106-9e80-ad281c916a64

MacOS: Desktop
https://github.com/Expensify/App/assets/134388952/7e2336cc-056a-4843-bf2f-c3a818930016

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@rushatgabhane brought back the offline text input hint. Looks like that weird glitch is gone after merging with main

Thanks! Let me check this out again

@lukemorawski the app crashes on opening task share page. I merged with main too -

@rushatgabhane not good. Will have a look in few minutes

@rushatgabhane after merging main crash occurred after all. It's fixed now.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/cristipaval in version: 1.4.46-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/roryabraham in version: 1.4.46-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


DB query with bindings always return empty array

$q = "as";
$res = DB::select(DB::raw("SELECT * FROM groups WHERE LOWER(name) LIKE LOWER('?%')"), [$q]);
return []
but
$q = "as";
$res = DB::select(DB::raw("SELECT * FROM groups WHERE LOWER(name) LIKE LOWER('$q%')"));
return [{"id":477,"name":"asd"}]
DB::selectRaw("SELECT * FROM groups WHERE LOWER(name) LIKE LOWER('?%')", [$q]);
MySqlConnection does not have a method 'selectRaw'
Group::selectRaw("SELECT * FROM groups WHERE LOWER(name) LIKE LOWER('?%')", [$q])->get() generate wrong sql query: select SELECT * FROM groups WHERE LOWER(name) LIKE LOWER('э%') from groups
(adds to end 'from groups')
Group - my class extends Model
$q = "as";
$res = Group::whereRaw("LOWER(name) LIKE LOWER('?%')", [$q])->get(); return empty array
but
$q = "as";
$res = Group::whereRaw("LOWER(name) LIKE LOWER('$q%')")->get(); return [{"id":477,"name":"asd"}]

Please ask questions on the forums.


Setup dapr and debug run environment

Parent issue
https://github.com/IT-REX-Platform/wiki/issues/8
Description
Set up dapr for the real project in a sophisticated way in a separate docker container.
Acceptance Criteria

[x] dapr is ready to use
[x] Basic setup to run dapr instances with microservices in a nice way (Docker containers)
[ ] IntelliJ run configurations
[x] documentation is updated if necessary

@LG1401 this is done IMO.
IntelliJ run configuration are not necessary (IntelliJ automatically creates them when you run the app or a script). Also they would not be pushed to the repository.


Improve sync yarn script

Add a couple of files to yarn sync script
Add package-lock to gitignore (we should use only yarn, not npm)

LGTM.


Extend functionality for outlier sample exclusion workflow

This PR extends the existing outlier sample exclusion workflow, wdl/FilterOutlierSamples.wdl, in several respects:

Accept one or more vcfs. This is necessary for large cohorts (e.g., gnomAD) where each chromosome is stored as a separate VCF for improved parallelization in the cloud, but we need to define outliers based on the sum of variants across all VCFs.

Add an optional VCF preprocessing step (with bcftools) prior to collecting sample counts. This is necessary in situations where we want to restrict to certain subsets of variants for defining outliers. Two empirical use cases from gnomAD v3 include: (a) restricting to rare (AF<1%), non-singleton (AC>1) deletions between 300bp - 1kb to deal with the artifact deletion bump we sometimes see in various callsets, and (b) restricting to PASS-only variants for defining our final set of samples at the very end of all QC & post-processing.

Allow outlier samples to be defined on one or more independent subsets of samples within the same VCF. This is necessary when cohorts contain a mixture of samples with different properties (e.g., PCR+ vs. PCR-) and we want to fit their SV count distributions separately when defining outliers. These are optional inputs to the workflow; if no values of sample_subset_prefixes and sample_subset_lists are provided, then outliers will be defined for all samples in the VCF together.

Enable (optional) plotting of outlier distributions from within the workflow. I understand that there is a separate workflow for plotting outlier distributions (PlotSVCountsPerSample.wdl) and the intention is for users to optionally run that workflow after collecting per-sample counts, but from a convenience perspective I thought it would be useful to have plotting as an option of the main outlier workflow. If there is a design reason why this is undesirable, we can remove the plotting, but I know I have enjoyed having this convenience added for gnomAD.

I have tested the above changes on gnomAD v3 (24 VCFs & ~120k samples) and can confirm that they work as expected. I have not tested a cohort with a single VCF but I believe it should work as long as the VCF is passed as an array of one element.

Thanks for pointing that out, @VJalili! This made me realize I had rebased versus the old master branch before submitting this PR, so I just pulled the main branch and rebased this PR versus the main. That should have reverted all of the changes to dockers.json but let me know if anything else looks odd!

Thanks, @RCollins13, that looks great.

@RCollins13 if you rebase your branch on the latest main, some errors in the Test WDLs action should be resolved.


Global/XilinxISE.gitignore: + Commenting *.ngc files to track compiled cores. +adding *.vhi, *.lo…

…g and work directory, ignoring some OS fies
Reasons for making this change:
by ignoring *.ngc files compiled cores are ignored, which they are used in lots of FPGA projects.
*.log and *.vhi files/work directory may also be ignored.
Links to documentation supporting these rule changes:
-for *.ngc files: CORE Generator Output Files

No documentation i can find for *.vhi files, but they exist in some my projects, noting lost by ignoring them in tests.
Log files always my be ignored. same for OS junk files.

Closing this out due to inactivity. Feel free to submit a new PR that doesn't add OS-specific rules.


无法使用本地的ts视频吗

我在data中引用本地的ts视频时会导入：
data() {
return {
url: "url(" + require("../assets/test.ts") + ")"
}
}
Module parse failed: Unexpected character '@' (1:1)
File was processed with these loaders:

./node_modules/eslint-loader/index.js
You may need an additional loader to handle the result of these loaders.
(Source code omitted for this binary file)
但我在导入其他格式的视频时可以

我在data中引用本地的ts视频时会导入：
data() {
return {
url: "url(" + require("../assets/test.ts") + ")"
}
}
Module parse failed: Unexpected character '@' (1:1)
File was processed with these loaders:

./node_modules/eslint-loader/index.js
You may need an additional loader to handle the result of these loaders.
(Source code omitted for this binary file)
但我在导入其他格式的视频时可以

You may need an additional loader to handle the result of these loaders.

看起来是需要配置对应的 loader，本地的视频可以试试 http://localhost:1234/assets/test.ts 这样的资源地址。

我在data中引用本地的ts视频时会导入：
data() {
return {
url: "url(" + require("../assets/test.ts") + ")"
}
}
Module parse failed: Unexpected character '@' (1:1)
File was processed with these loaders:

./node_modules/eslint-loader/index.js
You may need an additional loader to handle the result of these loaders.
(Source code omitted for this binary file)
但我在导入其他格式的视频时可以

You may need an additional loader to handle the result of these loaders.

看起来是需要配置对应的 loader，本地的视频可以试试 http://localhost:1234/assets/test.ts 这样的资源地址。


return test 6053 from quarantine

Release note:

NONE

/hold
@ShellyKa13 we need to follow the procedure described here https://github.com/kubevirt/kubevirt/blob/main/docs/quarantine.md to manage quarantined tests. In particular, to get a test out of quarantine we need to check that it is not failing for 14 days after its fix has been merged.
Looking at the board where we are tracking the quarantined tests I see that the fix for this one is still in progress, is that correct?

@fedepaol I thought it failed but I saw that it started passing regularly after some day so I followed it and I saw it hasn't failed for the last 14 days according to this search: https://search.ci.kubevirt.io/?search=6053&maxAge=336h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

Something seems to be wrong with that search, I see in flakefinder that the tests failed in the rook-ceph periodic between 2021-06-24 and 2021-06-30 https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/flakefinder-2021-06-30-168h.html#row18
If you think the test should be taken out of quarantine let's follow the procedure and start now the 14 days period to check if it fails again. If it doesn't fail passed this period let's propose a PR for taking it out of quarantine, wdyt?

For completeness this is the failed execution https://prow.ci.kubevirt.io/view/gcs/kubevirt-prow/logs/periodic-kubevirt-e2e-k8s-rook-ceph/1408002066273538048 failed after the fix was merged https://github.com/kubevirt/kubevirt/pull/5825

@fgimenez yeah I know that it failed after the merge but then I saw that it didnt fail for a long period of time so I thought it was fixed regardless after the merge. so last time it failed was on the 24th? whats the best way to find it? and sure we can start the countdown again starting today if thats what you think is needed

so last time it failed was on the 24th?

yes, I didn't find any more recent failure

whats the best way to follow it?

should be https://search.ci.kubevirt.io/ as you did, but for some reason it is not working as expected, will take a look at it. This time I searched for this concrete tests through the 168h reports of flakefinder here https://storage.googleapis.com/kubevirt-prow/reports/flakefinder/kubevirt/kubevirt/index.html

and sure we can start the countdown again starting today if thats what you think is needed

yep, I think it's the best thing we can do now, I'll set the due date to 2021-07-19 in the ticket.

OK then, closing for now


Some fixes to the linear algebra functions

As I noted on Slack, the broadcasting rule for matmul is wrong too (the last bullet point). It should not broadcast the "matrix dimensions". But I'm having a hard time figuring out a way to rewrite it that isn't too verbose. Any suggestions are welcome.

Re: matmul. Will submit a follow-up PR to address broadcasting.


[material-ui][Menu] Listbox stay fixed while scrolling outside of the menu

Steps to reproduce
https://github.com/mui/material-ui/assets/95575765/96b6c6f9-5e02-4a4e-8259-81448df3ff09
Steps:
1.Navigate to the button;
2.Select the button;
3.Open a drop-down menu;
4.Position your mouse cursor outside the drop-down menu and scroll up or down the page;
5.Observe the outcome;
Current behavior
We are using "antd": "4.24.15",
When trying to use drop-down menu for selecting, If you select the drop-down menu it will open, and when you position your mouse cursor outside the menu, if you start scrolling up or down the page, the drop-down menu will travel with you.
Expected behavior
We should be able to scroll through the page while there is an active drop-down menu, but the menu should stay stationed to its position.
Context
The dropdown menu is fixed to its input component
Your environment
No response
Search keywords: dropdown menu

Hey @TinaDermaku, thanks for the report! Could you provide a minimal reproduction? This would help a lot. A live example would be perfect. This StackBlitz sandbox template may be a good starting point. You mention you're using antd. Are you integrating it with Material UI's Menu? The minimal reproduction should show how it's setup so I can help you figure it out.
Thank you!


fix(javascript-calculator): removing +0 and -0 from the expression displayed on calculator.

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Partially closes #49045
With the 6 trailing zeros gone, I think it's still useful to remove any arithmetic involving zeros. That way the expression looks cleaner and the fix can even handle cases where the user types --0.

Hey maintainers...
Where can I tag in @spiritanand as my fellow contributor?

@scissorsneedfoodtoo thanks for the edge case.


Add rule hash-data-using-sha512managed-in-dotnet.yml

Adds rule for detecting hashing using .NET's Sha512Managed class

thank you!


Switching Workspaces stop functionality

When I switch Workspaces the functionality stops. What I can see is that the newly added "Pin" button also doesn't render, which feels like the plugin isn't "reloaded" (I'm not familiar with Obsidian events) when the workspace is loaded. No errors appear in the Dev Tools Console logs.

Fixed in 0.4.2!
thank you for information.


minor: remove useless code

Proposed changes
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Data Ingestion Stage

[x] Update config.YAML
[x] research or analysis
[x] Update the entity
[x] Update the configuration manager in src config.
[x] Update the components
[x] Update the pipeline

Dry run success for stage 01


What's the difference between static folder and the examples folder?

I don't get the distinction between these two folders?  Can you elaborate on this a bit?

Hi @elucidsoft !
The difference is that static is ment to be used for static (marketing) content with static pages which just display info without much functionality. In our case it's about and features pages. But in Angular terms its a feature module. Just a way to organize code.
 Again its more about code organization.
In your app you will have different feature modules based on your needs.


chore(main): release 1.12.0

:robot: I have created a release beep boop
1.12.0 (2024-04-12)
Features

nvim: add vim-tmux-navigator, using M-<hjlk> (051ac4e)
tmux: add vim-tmux-navigator, using M-<hjlk> (051ac4e)

Bug Fixes

fish: remove old zsh command from my custom fish commands (463686a)
tex matplotlib: plotting with tex works from a clean cache (569b2f9)

Miscellaneous

dprint: add css plugin and remove comments (845a6ec)
mise/fish: add alias x="mise x --" (69e3069)
nvim: small adjust of plugin configs (f2cbe32)
nvim: update deprecated harpoon command (26694cd)
software: update installed (d2eb673)
software: update installed (13375da)
software: update installed (594f5ca)
software: update installed (e13ec24)

Styles

alacritty: change italic font to Cartograph CF, a cursive font (8244623)

Code Refactoring

mise: specify env source file in the common config.toml file (69e3069)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/engeir/stowfiles/releases/tag/v1.12.0 :sunflower:


⚠ Bofrost.lu has degraded performance

In d489b86, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1082 ms

Resolved: Bofrost.lu performance has improved in e44f2cb after 10 minutes.


BLD: 1.0.x pin cython language level to '2'

This PR applies #451 to the 1.0.x branch.
I should backport a couple of the other bug fixes that were merged to master and then we can make a new release.

LGTM, thanks @grlee77


Using RGB stream causes Logitech webcam startup delay

We have HD Pro Webcam C920 and B525 HD Webcam. For them, it takes around one minute to start receiving frames. Same delay when changing resolution.

It happens only on laptops. Tested on two different laptops with clean Win11
No issues on Win11 PCs and other platforms
Other types of webcams is OK
Other apps like OBS, Skype etc. has no such big delay

Issues like these are likely at the driver level for the webcam. At the NatDevice level, we're simply asking Windows MediaFoundation to (1) create a media reader from the device; and (2) read samples in a loop.

This looks like a known issue, but I'm reopening this issue because there's a suggestion in the thread that we might want to try out:

RGB24 can cause this, you might want to try the other two instead, whichever ends up being faster. Also, if you have audio delay, you may want to try the latest test build with it.

Also renaming this issue to be more informative.

This looks like a known issue, but I'm reopening this issue because there's a suggestion in the thread that we might want to try out:

RGB24 can cause this, you might want to try the other two instead, whichever ends up being faster. Also, if you have audio delay, you may want to try the latest test build with it.

Also renaming this issue to be more informative.

This topic on OBS is about video stream delay, not the startup time.

Moving this issue to VideoKit.


save changes to default helix group

If changes are made to the default helix group, without adding new groups, then the changes are not saved in JSON.
To reproduce, select a small example design such as the 2-helix example origami. Select "adjust current group":

Rotate the group 90 degrees on the pitch axis:

It will rotate the group:

However, changes are not saved in localStorage, nor reflected if you examine the Saved .sc file:
{
  "version": "0.12.1",
  "grid": "square",
  "helices": [
    {"grid_position": [0, 0], "max_offset": 48},
    {"grid_position": [0, 1], "max_offset": 48}
  ],
  "modifications_in_design": {
    "/5Biosg/": {
      "display_text": "B",
      "idt_text": "/5Biosg/",
      "display_connector": false,
      "location": "5'"
    }
  },
  "strands": [
    {
      "color": "#0066cc",
      "sequence": "AACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACGTAACG",
      "is_scaffold": true,
      "domains": [
        {"helix": 1, "forward": false, "start": 8, "end": 24, "deletions": [20]},
        {"helix": 0, "forward": true, "start": 8, "end": 40, "insertions": [[14, 1], [26, 2]]},
        {"loopout": 3},
        {"helix": 1, "forward": false, "start": 24, "end": 40}
      ]
    },
    {
      "color": "#f74308",
      "sequence": "ACGTTACGTTACGTTTTACGTTACGTTACGTT",
      "domains": [
        {"helix": 1, "forward": true, "start": 8, "end": 24, "deletions": [20]},
        {"helix": 0, "forward": false, "start": 8, "end": 24, "insertions": [[14, 1]]}
      ]
    },
    {
      "color": "#57bb00",
      "sequence": "ACGTTACGTTACGTTACGCGTTACGTTACGTTAC",
      "domains": [
        {"helix": 0, "forward": false, "start": 24, "end": 40, "insertions": [[26, 2]]},
        {"helix": 1, "forward": true, "start": 24, "end": 40}
      ],
      "5prime_modification": "/5Biosg/"
    }
  ]
}

The changes are saved if either the name of the default group is changed, or a new group is added. Probably a problem with checking for default values in to_json_serializable and mistakenly thinking it's the default value if there's only one group and its name is "default_group".

Fixed in https://github.com/UC-Davis-molecular-computing/scadnano/commit/8b9a2b71e4c6cf9c3982c4a38100c1b671005b4a


How to update data in gatsby?

Node.js version:10.13.0
npm version:6.4.1
Database: Mongodb v3.6.4
Operation system : MacOS 10.14.1

Now,I hace successfully build my website(or blog) using strapi、gatsby、gatsby-source-strapi， ,the quesition is when I update data in strapi,I must rebuild gatsby to see the modification.I want to know how to rebuild it automatically without rebuilding gatsby by gatsby develop.
I also read this,but It doesn't work
So,is there any details for it? I need some help

Please anyone correct me if I'm wrong:
Gatsby is a Static Site Generator so you have to rebuild it with gatsby build to update your generated site when tour data change.
Although, there are many ways to automatically trigger the rebuild.
For example, webhooks, git hooks. These hooks would have to be handled by your building environment.

@mabhub  thanks for your explanation, I have already realized it. And now I use webhook to rebuild it!


Possibility of data loss due to asynchronous checkpointing in kinesis consumer

Describe the bug
The KinesisRecordProcessor pushes each record to a blocking queue and proceeds to checkpoint shard progress on every checkpoint interval. But at the point of checkpointing, there is no guarantee of successful delivery of pending records in the queue, which can lead to data loss in case of instance failure.
Source: https://github.com/apache/pulsar/blob/master/pulsar-io/kinesis/src/main/java/org/apache/pulsar/io/kinesis/KinesisRecordProcessor.java
To Reproduce
N/A
Expected behavior
All records retrieved by a consumer up until a certain checkpoint is expected to be processed successfully since any future retrievals will always return a new batch of records past the latest checkpoint.
Additional context
As per my understanding, the fix should ideally cover the following scenarios:

Periodic checkpointing at each checkpoint interval should be performed after pending records are processed up until that point

Checkpoint when onShardEnded is invoked should be performed after pending records are processed.

Checkpoint when shutdownRequested is invoked should be performed after pending records are processed.

Closed as stale. Please create a new issue if it's still relevant to the maintained versions.


openstack-scs-1-29-v1 / openstack-scs-1-28-v2 not deployable (cilium issues)

/kind bug
What steps did you take and what happened:
Create an openstack-scs-1-29-v1 or openstack-scs-1-28-v2 cluster.
The  cluster deployment stucks at 3/3 worker nodes and 1/3 control plane node. All nodes stuck in the status NotReady.
The nodes do not get an internal IP:
NAME                                   STATUS     ROLES           VERSION   INTERNAL-IP
cluster-scs-n64mk-f4xgt                NotReady   control-plane   v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-n596p   NotReady   <none>          v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-npxzf   NotReady   <none>          v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-vrtdl   NotReady   <none>          v1.29.6   <none>

Different pods have the following line in their logs:
Error from server: no preferred addresses found; known addresses: []

One of the first errors in the nodes /var/log/syslog is:
cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config

The directory /etc/cni/net.d is empty on the nodes.
What did you expect to happen:
The cluster is created successfully and usable.

This could be the reason:
{"level":"ERROR","time":"2024-07-18T15:36:24.881Z","file":"kube/kube.go:206","message":"failed to apply object","controller":"clusteraddon","controllerGroup":"clusterstack.x-k8s.io","controllerKind":"ClusterAddon","ClusterAddon":{"name":"cluster-addon-cluster-scs","namespace":"project-test"},"namespace":"project-test","name":"cluster-addon-cluster-scs","reconcileID":"ca7c0a4b-19a8-47f6-a99a-04c254712b1d","obj":"apps/v1, Kind=DaemonSet","name":"cilium","namespace":"kube-system","error":"failed to apply object: failed to create typed patch object (kube-system/cilium; apps/v1, Kind=DaemonSet): .spec.template.spec.securityContext.appArmorProfile: field not declared in schema","stacktrace":"github.com/SovereignCloudStack/cluster-stack-operator/pkg/kube.(*kube).Apply\n\t/src/cluster-stack-operator/pkg/kube/kube.go:206\ngithub.com/SovereignCloudStack/cluster-stack-operator/internal/controller.(*ClusterAddonReconciler).templateAndApplyClusterAddonHelmChart\n\t/src/cluster-stack-operator/internal/controller/clusteraddon_controller.go:737\ngithub.com/SovereignCloudStack/cluster-stack-operator/internal/controller.(*ClusterAddonReconciler).Reconcile\n\t/src/cluster-stack-operator/internal/controller/clusteraddon_controller.go:276\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile\n\t/src/cluster-stack-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:119\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\t/src/cluster-stack-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:316\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\t/src/cluster-stack-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:266\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\t/src/cluster-stack-operator/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:227"}

These should be all relevant parts of the helm chart with checks for Kubernetes < 1.30: https://github.com/search?q=repo%3Acilium%2Fcilium "<1.30.0"&type=code

CSO does helm template | kubectl apply -f - and that's why Cilium's helm chart semverCompare logic doesn't work here. It should work for 1.30 as you wrote. But for <1.30.0 it is a bug.

Yes it does work for 1.30.

See https://github.com/SovereignCloudStack/cluster-stack-operator/issues/153.

By the way: It seems that older Kubernetes 1.28/1.29 openstack-scs releases do not work as well because of a missing security group „0“ according to cspo. But I guess as soon as the new versions work the old ones are obsolete anyway.

By the way: It seems that older Kubernetes 1.28/1.29 openstack-scs releases do not work as well because of a missing security group „0“ according to cspo. But I guess as soon as the new versions work the old ones are obsolete anyway.

AFAIK CSPO only cares about node images. What do you mean by security group „0“?

/kind bug
What steps did you take and what happened:
Create an openstack-scs-1-29-v1 or openstack-scs-1-28-v2 cluster.
The cluster deployment stucks at 3/3 worker nodes and 1/3 control plane node. All nodes stuck in the status NotReady. The nodes do not get an internal IP:
NAME                                   STATUS     ROLES           VERSION   INTERNAL-IP
cluster-scs-n64mk-f4xgt                NotReady   control-plane   v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-n596p   NotReady   <none>          v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-npxzf   NotReady   <none>          v1.29.6   <none>
cluster-scs-worker-dsvk6-56cwn-vrtdl   NotReady   <none>          v1.29.6   <none>

Different pods have the following line in their logs:
Error from server: no preferred addresses found; known addresses: []

One of the first errors in the nodes /var/log/syslog is:
cni config load failed: no network config found in /etc/cni/net.d: cni plugin not initialized: failed to load cni config

The directory /etc/cni/net.d is empty on the nodes.
What did you expect to happen:
The cluster is created successfully and usable.

Hi @Nils98Ar, I just tested the creation of the cluster using the main branch of the cluster-stacks repo, built it via csctl, and did not encounter your error. The Kubernetes version is 1.28.11.
NAME                                            STATUS   ROLES           AGE     VERSION
test-cluster-5cgr8-4pj6m                        Ready    control-plane   3m38s   v1.28.11
test-cluster-5cgr8-tst5n                        Ready    control-plane   31m     v1.28.11
test-cluster-5cgr8-xdwvh                        Ready    control-plane   24m     v1.28.11
test-cluster-default-worker-b6fx8-8zrmf-2v865   Ready    <none>          28m     v1.28.11
test-cluster-default-worker-b6fx8-8zrmf-jdldc   Ready    <none>          24m     v1.28.11
test-cluster-default-worker-b6fx8-8zrmf-p5wh7   Ready    <none>          24m     v1.28.11

@michal-gubricky, what is the state of the ClusterAddon object?

@michal-gubricky, what is the state of the ClusterAddon object?

Here are all pods in kube-system namespace and also state of the cluster-addon resource:
ubuntu@mg-cluster-stack-vm:~$ k get clusteraddons.clusterstack.x-k8s.io cluster-addon-test-cluster
NAME                         CLUSTER        HOOK   READY   AGE   REASON   MESSAGE
cluster-addon-test-cluster   test-cluster          true    79m

ubuntu@mg-cluster-stack-vm:~$ k get po -n kube-system --kubeconfig test-cluster.kubeconfig
NAME                                                     READY   STATUS    RESTARTS         AGE
cilium-fk2b9                                             1/1     Running   1                66m
cilium-gmh4x                                             1/1     Running   0                39m
cilium-l9jgw                                             1/1     Running   0                63m
cilium-lgmsv                                             1/1     Running   0                60m
cilium-mj7qz                                             1/1     Running   1 (49m ago)      60m
cilium-ncxr4                                             1/1     Running   0                52m
cilium-operator-8645b8bb4f-ppd9l                         1/1     Running   9 (3m28s ago)    66m
cilium-operator-8645b8bb4f-v9vl7                         1/1     Running   9 (5m46s ago)    66m
coredns-5dd5756b68-fhdn2                                 1/1     Running   0                66m
coredns-5dd5756b68-r7mwx                                 1/1     Running   0                66m
etcd-test-cluster-5cgr8-4pj6m                            1/1     Running   1 (19m ago)      39m
etcd-test-cluster-5cgr8-tst5n                            1/1     Running   1 (19m ago)      66m
etcd-test-cluster-5cgr8-xdwvh                            1/1     Running   0                60m
kube-apiserver-test-cluster-5cgr8-4pj6m                  1/1     Running   2 (21m ago)      39m
kube-apiserver-test-cluster-5cgr8-tst5n                  1/1     Running   5 (23m ago)      67m
kube-apiserver-test-cluster-5cgr8-xdwvh                  1/1     Running   4 (23m ago)      60m
kube-controller-manager-test-cluster-5cgr8-4pj6m         1/1     Running   1 (27m ago)      39m
kube-controller-manager-test-cluster-5cgr8-tst5n         1/1     Running   9 (3m33s ago)    66m
kube-controller-manager-test-cluster-5cgr8-xdwvh         1/1     Running   3 (5m48s ago)    60m
kube-proxy-5dhjg                                         1/1     Running   0                39m
kube-proxy-649sl                                         1/1     Running   0                60m
kube-proxy-7gs4w                                         1/1     Running   0                63m
kube-proxy-7hpxb                                         1/1     Running   0                66m
kube-proxy-c62mx                                         1/1     Running   0                52m
kube-proxy-ch5fd                                         1/1     Running   0                52m
kube-scheduler-test-cluster-5cgr8-4pj6m                  1/1     Running   2 (3m28s ago)    39m
kube-scheduler-test-cluster-5cgr8-tst5n                  1/1     Running   8 (24m ago)      67m
kube-scheduler-test-cluster-5cgr8-xdwvh                  1/1     Running   3 (5m46s ago)    60m
metrics-server-666c6745d5-d6nvf                          1/1     Running   0                66m
openstack-cinder-csi-controllerplugin-78c4557887-qhvjr   6/6     Running   17 (3m30s ago)   66m
openstack-cinder-csi-nodeplugin-qxmdq                    3/3     Running   0                60m
openstack-cinder-csi-nodeplugin-rvppn                    3/3     Running   0                63m
openstack-cinder-csi-nodeplugin-ssll9                    3/3     Running   0                39m
openstack-cinder-csi-nodeplugin-t6cql                    3/3     Running   0                66m
openstack-cinder-csi-nodeplugin-vt9z6                    3/3     Running   0                60m
openstack-cinder-csi-nodeplugin-w8lcr                    3/3     Running   0                60m
openstack-cloud-controller-manager-4vdcl                 1/1     Running   2 (2m47s ago)    52m
openstack-cloud-controller-manager-6dkfw                 1/1     Running   2 (5m48s ago)    35m
openstack-cloud-controller-manager-f84zp                 1/1     Running   4 (19m ago)      46m

AS @Nils98Ar wrote, the breaking change was introduced in the cilium chart version 1.15.5. The main branch installs version  1.15.2, that's why it works for you @michal-gubricky. I checked cluster-addon/Chart.lock vs cluster-addon/Chart.yaml, which differs. We are missing helm dependency update command there.

AS @Nils98Ar wrote, the breaking change was introduced in the cilium chart version 1.15.5. The main branch installs version 1.15.2, that's why it works for you @michal-gubricky. I checked cluster-addon/Chart.lock vs cluster-addon/Chart.yaml, which differs. We are missing the helm dependency update command there. Please also check the release- branches, where it is correct.

Yeah, I was just looking at the version in Chart.yaml and there is 1.15.6.

Hi @janiskemper, can you please take a look? IMO we have two options here:

Use a workaround from #150
Use helm template --kube-version ... in the CSO cluster-addon logic if it is possible for this controller to know the workload k8s version. This of course needs to be tested if it is enough first.


Error with theme generator

running
$ rails g ctheme my_theme_name

the result is
/Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1386:in `copy': unknown file type: /application_path/lib/generators/ctheme_template/app (RuntimeError)
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:471:in `block in copy_entry'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1497:in `call'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1497:in `wrap_traverse'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:468:in `copy_entry'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:443:in `block in cp_r'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1570:in `block in fu_each_src_dest'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1586:in `fu_each_src_dest0'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:1568:in `fu_each_src_dest'
  from /Users/my_user/.rvm/rubies/ruby-2.2.3/lib/ruby/2.2.0/fileutils.rb:442:in `cp_r'
  from /Users/my_user/Development/camaleon-cms/lib/generators/ctheme_generator.rb:26:in `create_initializer_file'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/invocation.rb:133:in `block in invoke_all'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/invocation.rb:133:in `each'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/invocation.rb:133:in `map'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/invocation.rb:133:in `invoke_all'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/group.rb:232:in `dispatch'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/generators.rb:157:in `invoke'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands/generate.rb:13:in `<top (required)>'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `require'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `block in require'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:240:in `load_dependency'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/activesupport-4.2.4/lib/active_support/dependencies.rb:274:in `require'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:130:in `generate_or_destroy'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:50:in `generate'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
  from /Users/my_user/.rvm/gems/ruby-2.2.3@gemset_name/gems/railties-4.2.4/lib/rails/commands.rb:17:in `<top (required)>'
  from ./bin/rails:4:in `require'
  from ./bin/rails:4:in `<main>'

I'm using RVM with ruby 2.2.3.
I've replaced the my application path with 'application_path' in the output above.

Fixed!
Don't forget to do:
bundle update
Regards,

It works.
Thanks a lot!


no_std Support

Dear all,
as roxmltree only depends on xmlparser, would it be possible to make roxmltree support no_std environments?
xmlparser is no_std ready, so that would already take some effort away.
Best regards,
Andreas

It's not possible, because roxmltree allocates. We can do no_str + alloc, but I don't see a point in it.

@RazrFalcon Wasm is no_std and has full support for alloc.  I’d be willing to make a PR if you were interested.

I haven't worked with wasm, so I'm not sure. But if this is something you're interested in, I will accept the patch.
I just want to avoid unnecessary restrictions. And no_std is one of them.

I understand not wanting to restrict yourself.  As long as roxmltree uses neither I/O nor threads, it should be fine with alloc.

The no_std+alloc support have been added.


Docs: The onSubmitCompleted$ handler

Tried my best to add a section about the onSubmitCompleted$ event handler in the docs.
Can someone explain to me the need for
{15-18} /firstName/#a /lastName/#b /email/#c
At the top of the code examples? I left it out since I didn't quite understand what it meant.
I hope my documentation changes can help! A friend in the discord came across this event handler in the type definitions and it was the perfect solution to my EditForm component in my todo app. Here's the live version to see how it works
https://qwik-todo-app.netlify.app/
What is it?

[ ] Feature / enhancement
[ ] Bug
[x] Docs / tests

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Use cases and why

One use case

Another use case

Checklist:

[x] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

@manucorporat I've gone ahead and stripped whatever I could to keep it as minimal as possible. I was able to get it down to 45 lines and checked that the edit functionality still works on my localhost after making the following changes.

@hamatoyogi let me know if there's anything I could've done further here! I think you mentioned getting some time to show what you meant earlier.


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove re:run/3 to parse_url and use uri_string:parse/1 or http_uri:parse/1 depending on OTP version

In preparation of trying to pull aws_signature into aws-erlang (aws-beam/aws-erlang#63) I'd like to try and negate a few of the quick wins that I've encountered in aws_signature, this PR being one of them. I have tested below performance tests with OTP 22 :-)
It might not seem like much but considering tight loops, it's something at least. The end result is the same either way and a number of tests exists that prove this :-)
1> c(aws_signature_utils, [export_all]).
Recompiling /home/onnovos/src/github/aws_signature/src/aws_signature_utils.erl
{ok,aws_signature_utils}

aws_signature_utils:parse_url/1 old (first) vs new (second):
Summary:
median: 10.000us vs 4.680us
average: 11.615us vs 5.095us
2> perftest:test([fun() -> aws_signature_utils:parse_url(<<"https://example.com/te%20st/path">>) end]).
Method                                           Loops               Min               Max            Median           Average
empty loop                   178069 *  333 =  59296977           0.003us           1.180us           0.003us           0.005us
erl_eval:'-expr/5-fun-3-'()    1679 *   50 =     83950           8.360us          32.880us          10.000us          11.615us
3> c(aws_signature_utils, [export_all]).
Recompiling /home/onnovos/src/github/aws_signature/src/aws_signature_utils.erl
{ok,aws_signature_utils}
4> perftest:test([fun() -> aws_signature_utils:parse_url(<<"https://example.com/te%20st/path">>) end]).
Method                                           Loops               Min               Max            Median           Average
empty loop                   195655 *  333 =  65153115           0.003us           0.312us           0.003us           0.004us
erl_eval:'-expr/5-fun-3-'()    3791 *   50 =    189550           4.060us          10.500us           4.680us           5.095us

Thanks for whichever ninja enabled the workflow :smile:  I'll take a look at the failures on OTP 19 :+1:

Let me know if you'd like me to benchmark OTP 19 which I haven't done but can if you so wish :)
Let me know if you'd like a squash of the 3 commits that are currently there :)


Add simple marshaller which marshal only null COM interfaces

This idea was proposed by @MichalStrehovsky in #7994
Implemented only marshalling of in parameters, since this is case which I found in the stack trace of the issue. I think other directions can be implemented in same way, I just lack of examples for testing.
Tested code
// [DllImport(Libraries.UiaCore, CharSet = CharSet.Unicode)]
// public static extern IntPtr UiaReturnRawElementProvider(IntPtr hwnd, IntPtr wParam, IntPtr lParam, IRawElementProviderSimple el);
IntPtr result = UiaCore.UiaReturnRawElementProvider(IntPtr.Zero, IntPtr.Zero, IntPtr.Zero, null);

Closes #7994

@MichalStrehovsky I was little bit lazy and do not create specific functions in native code. I take existing sample which I have. Should I implement function for marshalling in native code?

Should I implement function for marshalling in native code?

Yes please - it will be even less code that way (the interface doesn't need to have any members, etc.).
I don't know what UI automation would do with this call - I don't want the test to accidentally break screen readers, so it's better to call into "known" code.


Logging for Parameter Store

Type: Bug / Help needed
Component:
"Parameter Store"
Describe the bug
I ran the sample for spring-cloud-aws-parameter-store and tried adding debug logging in order to see which parameters should be retrieved from SSM.
The Documentation states that

In order to find out which properties are retrieved from AWS Parameter Store on application startup, turn on DEBUG logging on io.awspring.cloud.paramstore.AwsParamStorePropertySource class.
logging.level.io.awspring.cloud.paramstore.AwsParamStorePropertySource=debug

I added that to application.properties but I can see no debug logs. Can you please explain how to enable debug logging in your sample? Without that debugging will be a nightmare.
Thank you.
Sample
See https://github.com/awspring/spring-cloud-aws/tree/2.3.x/spring-cloud-aws-samples/spring-cloud-aws-parameter-store-sample

Not sure, but might be helpful
we use logback as a logging framework, so I just added this on our logback.xml:
<logger name="io.awspring.cloud.paramstore" level="DEBUG"/>

2021-12-21 19:54:31,880 INFO  logger="io.awspring.cloud.paramstore.AwsParamStorePropertySourceLocator" marker="" message="Loading property from AWS Parameter Store with name: hgfdhgfdhgfd, optional: false" thread="restartedMain"
2021-12-21 19:54:31,993 DEBUG logger="io.awspring.cloud.paramstore.AwsParamStorePropertySource" marker="" message="Populating property retrieved from AWS Parameter Store: xxx.client_id" thread="restartedMain"

it might depend on your log framework