Command rgrep fails with (wrong-type-argument string ...) when using the default wildcard

Steps to reproduce the problem:
M-x rgrep RET
Hello RET
RET (to accept the default wildcard)
Base directory: Whatever and RET
Actual result:

Debugger entered--Lisp error: (wrong-type-argument stringp (".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm"))
string-match("[ \f\11\n\15\13]+" (".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm") 0)
split-string((".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm"))
rgrep-default-command("Hello" (".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm") nil)
rgrep("Hello" (".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm") "<..>/Resources/lisp/p..." nil)
funcall-interactively(rgrep "Hello" (".gz" "all" "el" "ch" "c" "cc" "cchh" "hh" "h" "l" "m" "tex" "texi" "asm") "<...>/Resources/lisp/p..." nil)
call-interactively(rgrep record nil)
command-execute(rgrep record)
execute-extended-command(nil "rgrep" nil)
funcall-interactively(execute-extended-command nil "rgrep" nil)
call-interactively(execute-extended-command nil nil)
command-execute(execute-extended-command)

If I type the default wildcard manually, for example, *.gz, the command works correctly.

With the recipe provided I am seeing this as well.

Thanks, the fixed version is up on MELPA


Add version to core components

Description
This PR fixes adds version to the core component's definition json.
For each service mesh version, we will have the core component with the version specified. Earlier we just had one unversioned core component.
Notes for Reviewers
Signed commits

[ ] Yes, I signed my commits.

@gr455 This was the PR I was referring to. This needs to be propagated across all repos

Error: error: failed to check packages: errors while loading package github.com/layer5io/meshery-istio/istio: [/home/runner/work/meshery-istio/meshery-istio/istio/oam.go:119:23: comp.Spec.Version undefined (type "github.com/layer5io/meshkit/models/oam/core/v1alpha1".ComponentSpec has no field or method Version) /home/runner/work/meshery-istio/meshery-istio/istio/oam.go:189:23: comp.Spec.Version undefined (type "github.com/layer5io/meshkit/models/oam/core/v1alpha1".ComponentSpec has no field or method Version)]
[28](https://github.com/meshery/meshery-istio/runs/7166751938?check_suite_focus=true#step:4:29)
Error: Process completed with exit code 2.

Yeps that is because older patternfiles will be incompatible after this change. They all will require a version field inside of each patternfile service. Changing the patternfiles now in my PR. In some cases this field can be optional as well but especially while deploying IstioMesh, it has to be passed explicitly in the service.

Merge conflict.

Merge conflict.

Will be winding it off today.

@leecalcote  Merging this now. The failing test will pass after new Meshery release.


Bug: keys not extracted from typescript files after an explicit coercion expression

Is there an existing issue for this?

[X] I have searched the existing issues

Is this a regression?
Yes
Current behavior
Strings passed to a translate call that follow a coercion expression or some other expression containing <> are not extracted.
import {Component} from "@angular/core";
import {translate} from "@jsverse/transloco";

@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrl: './app.component.scss'
})
export class AppComponent {
  constructor() {
    translate("This first key will be extracted");
  }

  getString(): string
  {
    return "5";
  }

  extractionProblem(): void
  {
    translate("This second key will be extracted");
    const foo = <string>this.getString();
    translate("This third key will NOT be extracted");
  }
}

Expected behavior
All strings should be extracted
Please provide a link to a minimal reproduction of the bug
https://stackblitz.com/~/github.com/dalyl-zero/transloco-bug-report
Transloco Config
No response
Debug Logs
No response
Please provide the environment you discovered this bug in
Transloco: 7.1.0
Transloco Keys Manager: 4.1.0
Angular: 17.3.0
Node: 18.13.0
Package Manager:
OS: Windows/Mac

Additional context
This does not happen on transloco-keys-manager 3.8.0 and is independent of the version of Transloco
I would like to make a pull request for this bug
No

Also stumbled upon this issue!
It is very sneaky, it ignores the remaining part of the file from key extractor perspective, with no clear errors so it can be overlooked very easily.

The issue was that the TypeScript prefix cast operator, the AST thinks this is a JSX element, and that's also the original reason why the as operator was introduced back in v1.6.
Nice catch 👍


atscan.net down?

Hi! I'm a big fan of atscan.net, and noticed it has been down at least a few days.
Any chance it will come back up? If you're busy with other stuff that's cool, just curious.

Hello! Thanks a lot for asking.
Yes, atscan has been unavailable for quite some time. Unfortunately I don't have the capacity for development and maintenance right now - so I have to put the project on hold.
The architecture of experimental backend (Javascript & Deno) is currently not optimal and not scalable. It's not ready for today or future numbers (I worked on it when bluesky had low hundreds of thousands of users). For me it was more of an experiment to learn how the AT Protocol works, and now it would need a complete rewrite. That's the main reason.
If anyone would like to take over or adopt the project and continue working on it - I'd be happy to assist, but unfortunately I don't have the time to do the rewriting and everything around it right now :(
Thank you very much for your support!

thanks for the update! it is a pretty nice demonstration and inspiration for future tools.
best of luck with other projects


Changelog entry to zlib update.

You should target stable now.

It also needs a description

Changelog entries should consist of one title line, a blank separator line, and a description.

You should target stable now.

Will it get moved over for 2.100.0?

You should target stable now.

Will it get moved over for 2.100.0?

2.100 has already been tagged, master won't be merged into stable for another two months.

ping @ibara

ping @ibara

Sorry. Just been busy with end of semester things.
Will try to get on it today.


Increase number of CPUs

Increase number of CPUs to fix error 'invalid cpu for jvm jobs. must be 1 or 8'

No problem!


added 'heard_about' value to mentee intake migration table and seed d…

…ata file
Description
Added 'heard_about' value to mentee intake migration table and seed data file, to match new question added to the mentee intake form on the front end.
Video Link
Loom Video
Trello Link
https://trello.com/c/c3PAVHge/348-mentee-intake-additional-questions
Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have removed unnecessary comments/console logs from my code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] No duplicate code left within changed files
[x] Size of pull request kept to a minimum
[x] Pull request description clearly describes changes made & motivations for said changes

More than approved! I like the verbiage used here.

Simple and clean solution. Not much to add :)


Possible deadlock with dataloader

Hey guys, my dataloader seems to be locking up and not accepting any new request after using the request several times.
This seems to be the only dataloader with this issue, but it is also the only dataloader that i use reqwest rather than my tiberius sql db.
It happens after receiving several interupted request from the client, but never happens if i send a single request using the playground.
That dataloader will not process any further request, and the rest of the query can succeed if i take that part out of the query
The expected behavior is that it does not hang ever.
Please let me know if you require the implementation of any of the functions shown.
#[derive(
    Default,
    Clone,
    PartialEq,
    serde_derive::Serialize,
    serde_derive::Deserialize,
    SimpleObject,
    Debug,
)]
#[graphql(complex)]
#[serde(rename_all = "camelCase")]
pub struct ServiceNowRelCi {
    #[serde(rename = "connection_strength")]
    pub connection_strength: ConnectionStrength,
    pub parent: Parent,
    #[serde(rename = "sys_mod_count")]
    pub sys_mod_count: SysModCount,
    #[serde(rename = "sys_updated_on")]
    pub sys_updated_on: SysUpdatedOn,
    #[serde(rename = "sys_tags")]
    pub sys_tags: SysTags,
    #[serde(rename = "type")]
    pub type_field: Type,
    #[serde(rename = "sys_id")]
    pub sys_id: SysId,
    #[serde(rename = "sys_updated_by")]
    pub sys_updated_by: SysUpdatedBy,
    pub port: Port,
    #[serde(rename = "sys_created_on")]
    pub sys_created_on: SysCreatedOn,
    #[serde(rename = "percent_outage")]
    pub percent_outage: PercentOutage,
    #[serde(rename = "sys_created_by")]
    pub sys_created_by: SysCreatedBy,
    pub child: Child,
}

#[ComplexObject]
impl ServiceNowRelCi {
    pub async fn children(&self, ctx: &Context<'_>) -> FieldResult<Option<Vec<ServiceNowRelCi>>> {
        let data: Option<Vec<ServiceNowRelCi>> = ctx
            .data_unchecked::<DataLoader<ServiceNowRelCiChildrenLoader>>()
            .load_one(self.child.value.clone())
            .await?;

        Ok(data)
    }
//rest
}

pub struct ServiceNowRelCiChildrenLoader(Client);

impl ServiceNowRelCiChildrenLoader {
    pub fn new(pool: Client) -> Self {
        Self(pool)
    }
}

fn query_rel_ci_from_sn_url(keys: &[String]) -> String {
    format!("https://nb.service-now.com/api/now/table/cmdb_rel_ci?sysparm_query=parentIN{}&sysparm_display_value=all",keys.join(","))
}

///DataLoader with an array as child.
///DataLoader using a rest endpoint
#[async_trait]
impl Loader<String> for ServiceNowRelCiChildrenLoader {
    type Value = Vec<ServiceNowRelCi>;
    type Error = FieldError;

    async fn load(&self, keys: &[String]) -> Result<HashMap<String, Self::Value>, Self::Error> {
        let query = query_rel_ci_from_sn_url(keys);

        let stream: Vec<ServiceNowRelCi> = CmdbCiService::query_service_now_get_builder::<RootServiceNowRelCi>(
            self.0.clone(),
            query.as_str(),
        )
        .await?
        .result;

        let stream = stream
            .clone()
            .into_iter()
            .map(|data: ServiceNowRelCi| {
                (
                    data.parent.value.clone(),
                    stream
                        .clone()
                        .into_iter()
                        .filter(|filtered| &data.parent.value == &filtered.parent.value)
                        .collect(),
                )
            })
            .collect::<HashMap<String, Vec<ServiceNowRelCi>>>();

        Ok(stream)
    }
}

    ///Get request from service now, just requires url
    async fn query_service_now_get_builder<T>(
        client: reqwest::Client,
        url: &str,
    ) -> anyhow::Result<T>
    where
        T: DeserializeOwned,
    {
        dotenv().ok();
        let username = env::var("SN_API_KEY_USER").expect("SN_API_KEY_USER must be set");
        let password = env::var("SN_API_KEY_PASS").expect("SN_API_KEY_PASS must be set");
        client
            .get(url)
            .basic_auth(username, Some(password))
            .send()
            .await?
            .json()
            .await
            .map_err(Into::into)
    }

This was my first time doing a rest api call rather than a database call inside a dataloader, and this is the only dataloader which has this issue.
Wonder if there is any correlation. Maybe interrupted request never finish and get locked?  Not sure

Can you provide a minimal use case that can reproduce this problem? 😁

Can you provide a minimal use case that can reproduce this problem? 😁

Sorry I am not sure how to reduce it, as all other data loaders I've ever created do not have this issue. Only difference was not using Tiberius for data but instead reqwest

I am intermittently encountering what appears to be a similar issue with Elasticsearch. After the .await for the request the server just deadlocks, but only occasionally.
@servonlewis are you happening to use the work around mentioned at the end of #489 to get actix-web v4 working with Tokio 1.0? Wonder if that's to blame.

I am intermittently encountering what appears to be a similar issue with Elasticsearch. After the .await for the request the server just deadlocks, but only occasionally.
@servonlewis are you happening to use the work around mentioned at the end of #489 to get actix-web v4 working with Tokio 1.0? Wonder if that's to blame.

Hey I am actually using warp with tokio 1

I've just ran into this exact issue - in developing my backend app I've had no issues querying via the playground but taking a proper client (apollo client in this case) into it and developing a frontend I've ran into this.
I'm unsure what exactly is causing this (I'm using foundationdb in my dataloader), but I'll attempt to produce a small POC for further debugging.
One of the many times I ran into this, I did manage to produce a panic out of it:
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Canceled', /Users/tom/.cargo/registry/src/github.com-1ecc6299db9ec823/async-graphql-2.9.9/src/dataloader/mod.rs:334:18

I am unsure if this is related though; it is possible it is entirely unrelated.

I think I have narrowed it down:

the deadlock seems to happen when a pending request is cancelled (see screenshot below) (I am using apollo client in react for example)
I can call the GQL service with 10+ requests/sec using curl with no deadlocks
the action inside the dataloader is Delay, whereas other requests it is StartFetch

cancelled screenshot: all localhost requests are POSTs to the graphql endpoint, you can see the first is cancelled which makes the third pending forever

In this code here in the dataloader: https://github.com/async-graphql/async-graphql/blob/master/src/dataloader/mod.rs#L359-L366
When a request is successful, the action is StartFetch
when I get a deadlock, the action is Delay
I added a println here https://github.com/tombowditch/async-graphql/blob/dataloader-race/src/dataloader/mod.rs#L379
Working request:

Deadlocked request:

Which leads me to believe the await here https://github.com/async-graphql/async-graphql/blob/master/src/dataloader/mod.rs#L368 is awaiting forever?
@sunli829 your input would be appreciated, this is where my lack of knowledge of the codebase fails me :) I hope that is helpful at least :)

Thank you, these can definitely help me. @tombowditch

Thank you, these can definitely help me. @tombowditch

Hey there,
I appreciate you guys taking this up, as I am starting to see the error again.
As the individual said above, it is only occurring after canceling a request. I am also using Apollo client, so I wonder if there is a proper cancel mechanism on that library.
Has there been any update to this issue?

I think I have found the cause of the problem and I am fixing it.

I fixed this in the master branch.
Now the dataLoader::new function adds a parameter to specify the function that spawning task, because I don't want async-graphql to depend on a specific runtime.
DataLoader::new(MyLoader, tokio::spawn)
DataLoader::new(MyLoader, async_std::spawn)

@sunli829 thank you - I just pulled down the latest commit in Cargo and can confirm I'm not seeing the locks anymore! This is with tokio

I fixed this in the master branch.
Now the dataLoader::new function adds a parameter to specify the function that spawning task, because I don't want async-graphql to depend on a specific runtime.

DataLoader::new(MyLoader, tokio::spawn)

DataLoader::new(MyLoader, async_std::task::spawn)

Thank you!  How can I pull it down to test?  Can you please show me the toml snippet?

@servonlewis like this:
async-graphql = { git = "https://github.com/async-graphql/async-graphql.git", features = ["log", "apollo_tracing", "tracing", "dataloader"], rev = "d2a71377a933eb32f8f3f0e23854638ac52ca927" }
async-graphql-warp = { git = "https://github.com/async-graphql/async-graphql.git", rev = "d2a71377a933eb32f8f3f0e23854638ac52ca927" }

(make sure to change if you're not using warp & the features)

@servonlewis like this:

async-graphql = { git = "https://github.com/async-graphql/async-graphql.git", features = ["log", "apollo_tracing", "tracing", "dataloader"], rev = "d2a71377a933eb32f8f3f0e23854638ac52ca927" }

async-graphql-warp = { git = "https://github.com/async-graphql/async-graphql.git", rev = "d2a71377a933eb32f8f3f0e23854638ac52ca927" }

(make sure to change if you're not using warp & the features)

Thank you!  Will give it a test now. How long does a typical change like this take before it is updated in the main branch and crates.io?
I really appreciate the help

How long does a typical change like this take before it is updated in the main branch and crates.io?

All depends on when @sunli829 publishes a new version - but once it's published it's super quick :)

Release in v3.0.12 🙂

Release in v3.0.12 slightly_smiling_face

Thanks!
I've updated to that rev, but now i get these errors:
| #[Object]
| ^^^^^^^^^ the trait OutputType is not implemented for VsphereMetrics
and same for InputType.
I am not sure if that has documentation for it yet, as i am still looking around.
This is one my InputObject structs that it is complaining about.

#[derive(Serialize, Deserialize, Debug, InputObject, Clone)]
#[serde(rename_all = "camelCase")]
pub struct VsphereMetricsInput {
    pub interval_type: Option<IntervalType>,
    pub roll_up_type: Option<RollupType>,
    pub resource_id: String,
    pub begin: Option<i64>,
    pub end: Option<i64>,
}

@servonlewis did you go from 2.x to 3.x or from 3.x to 3.0.12?

@servonlewis did you go from 2.x to 3.x or from 3.x to 3.0.12?

2.0

Please upgrade to 3.x 😁

Please upgrade to 3.x grin

It looks like the book is still on 2.x, do you have any migration docs?

Please upgrade to 3.x grin

looks like it's having trouble with an InputObject that has an enum as a field.
#[derive(Serialize, Deserialize, Debug, InputObject, Clone)]
#[serde(rename_all = "camelCase")]
pub struct VsphereMetricsInput {
    pub interval_type: Option<IntervalType>,
    pub roll_up_type: Option<RollupType>,
    pub resource_id: String,
    pub begin: Option<i64>,
    pub end: Option<i64>,
}

#[derive(Enum, Copy, Clone, Eq, PartialEq, Serialize, Deserialize, Debug)]
pub enum RollupType {
    Sum,
    Avg,
    Min,
    Max,
    None,
    Latest,
    Count,
}

#[derive(Enum, Copy, Clone, Eq, PartialEq, Serialize, Deserialize, Debug)]
pub enum IntervalType {
    Hours,
    Minutes,
    Days,
    Weeks,
    Months,
    Years,
}

error[E0277]: the trait bound `RollupType: InputType` is not satisfied
   --> query_tiberius\src\v_sphere.rs:145:41
    |
    |                                         ^^^^^^^^^^^ the trait `InputType` is not implemented for `RollupType`
    |
    = note: required because of the requirements on the impl of `InputType` for `std::option::Option<RollupType>`

Please disregard, I had forgot to update the version in the other libs in my workspace :(
my apologies!

Looking to test, but the new version doesn't allow for multiple objects with the same name...been going through them all for a while now. Will let you know how it works soon!

It works!!!! Thank you!

Please upgrade to 3.x grin

It looks like the book is still on 2.x, do you have any migration docs?

I forgot to update the version in the book, it has been changed now. 🙂

Please upgrade to 3.x grin

It looks like the book is still on 2.x, do you have any migration docs?

I forgot to update the version in the book, it has been changed now. 🙂

I really appreciate your help with this. The library is too awesome man.


Batch table

Adds a batch table similar to what is used by 3D tiles, but can also be used for batched polylines and geometry. Currently only hooked up to the PolylineCollection. It can replace the implementation of per-instance attributes for Primitive, but that won't happen for this PR.
This needs to be merged before #4309.

It can replace the implementation of per-instance attributes for Primitive, but that won't happen for this PR.

Submit an issue or update the appropriate roadmap.

@pjcozzi This is ready for another look.

Even though this doesn't change the Cesium API, can you update CHANGES.md to say that the extension is now required?

The following test passes in master and fails in this branch:
Scene/PolylineCollection does not render with width 0.0
Expected [ 0, 0, 0, 255 ] not to equal [ 0, 0, 0, 255 ].

Just those comments.

@pjcozzi This is ready.


Remove direct noting of port 10

We use number_small as the capture for all port commands, which includes 10.
Comment at https://github.com/knausj85/knausj_talon/pull/871#discussion_r889588800
suggests it was initially included for debugging and is no longer required.

Missed the change of master to main in my local pull


Build and Deploy Job Failed

.So i'm using GitHub actions to CI CD to Azure. My app has frontend(angular) and backend(django) directories each so decided to run the backend on an azure app service and the angular frontend on an azure static web app but after connecting my frontend service to my github repo, the workflow was created and ran but it keeps failing on the "Build and Deploy Job". Below is the log :
Run Azure/static-web-apps-deploy@v1
  with:
    azure_static_web_apps_api_token: ***
    action: upload
    app_location: frontend
    output_location: dist/frontend
    github_id_token: ***
    skip_app_build: true
/usr/bin/docker run --name bdc3e63db450cc4[2](https://github.com/Workmayte/workmayte/actions/runs/12141072101/job/33852294191#step:6:2)26bb0ca8[3](https://github.com/Workmayte/workmayte/actions/runs/12141072101/job/33852294191#step:6:3)0357b4143_b3ad22 --label 9404bd --workdir /github/workspace --rm -e "INPUT_AZURE_STATIC_WEB_APPS_API_TOKEN" -e "INPUT_ACTION" -e "INPUT_APP_LOCATION" -e "INPUT_API_LOCATION" -e "INPUT_OUTPUT_LOCATION" -e "INPUT_GITHUB_ID_TOKEN" -e "INPUT_SKIP_APP_BUILD" -e "INPUT_API_BUILD_COMMAND" -e "INPUT_APP_ARTIFACT_LOCATION" -e "INPUT_APP_BUILD_COMMAND" -e "INPUT_REPO_TOKEN" -e "INPUT_ROUTES_LOCATION" -e "INPUT_CONFIG_FILE_LOCATION" -e "INPUT_SKIP_API_BUILD" -e "INPUT_PRODUCTION_BRANCH" -e "INPUT_DEPLOYMENT_ENVIRONMENT" -e "INPUT_IS_STATIC_EXPORT" -e "INPUT_DATA_API_LOCATION" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_RE
DeploymentId: 092e05a8-f8fb-[4](https://github.com/Workmayte/workmayte/actions/runs/12141072101/job/33852294191#step:6:4)ba5-9528-a6363780388[5](https://github.com/Workmayte/workmayte/actions/runs/12141072101/job/33852294191#step:6:5)
Try to validate location at: '/github/workspace/frontend'.
App Directory Location: 'frontend' was found.
Try to validate location at: '/github/workspace/swa-db-connections'.
Looking for event info
Skipping step to build /github/workspace/frontend with Oryx
Failed to find a default file in the app artifacts folder (frontend). Valid default files: index.html,Index.html.
If your application contains purely static content, please verify that the variable 'app_location' in your workflow file points to the root of your application.
If your application requires build steps, please validate that a default file exists in the build output directory.

For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
Exiting

Just in case, here's my repo Workmayte you can see my structure

👍🏽 I'm getting the same exactly error

I also have the same problem.
I thought it might be related to the unbuntu-latest moving to 24.04, but I got the same error when I tried forcing it to 22.04


google cloud speech api is not working in node js

I am using Google Cloud Speech API in Node.js. When I send a local audio file it gives the result but when I try to send a live stream it gets stopped within a second. Can anyone help me with this?
I am using this file: [recognize.js][1]

  [1]: https://github.com/GoogleCloudPlatform/nodejs-docs-samples/tree/master/speech

@jagadesh18 can you give more info about how to reproduce?

@jagadesh18 Without reproduction steps, I'm not sure how to reproduce. It sounds unique to the modules you're using and your code. It might be best to ask on StackOverflow. If you discover there is a bug in this library, please come back and let us know.


Link to download eBook no longer active.

I've purchased a hard copy of Geospatial Analysis with SQL book and would like to download the pdf.  The link provided is no longer working, so can you please advise how I can do this?  Cheers.

SAME ...

Same here. Please provide a new way to access the pdf


Display words with artificial="elliptic" correctly

Fixes https://github.com/perseids-tools/treebank-react/issues/15
There are two parts to this pull request:

2a404fb sorts the words in the sentence by the insertion_id (if it exists) or id (if there is no insertion_id).
23d26a9 reduces the font size for words with artificial="elliptic"

Thanks again for the review @balmas!


 not rerendering after a route change

Version
2.4.0
I have a project with a lot around react-router (react-router-redux among other things) so I'm still trying to isolate the problem but I'm posting the issue in the meantime if someone is having the same problem at the same time... or even an idea of where to look for.
Test Case
Clicking on a <Link /> in a header
Steps to reproduce
Working on it
Expected Behavior
The active style being added to the Link I just clicked and removed from the Link of the route we just left.
Actual Behavior
Rendering the right component but since no props changed in my header's Link they don't re-render. By adding Link.componentDidMount = () => this.context.router.listen(this.render.bind(this)) it re-render but is always keeping the active style once it has been active once.

After using JSBin, the problem doesn't reproduce, so the problem is probably coming from the combinaison with react-router-redux or just in my set-up. I'll continue to work on that
http://jsbin.com/cuvoyucife/edit?html,js,output

I got this issue too, and after searching for the answer, I think it might be something related to Redux. As being discussed at #3536 , a container component which is wrapped by Redux's connect() will make all the Links in it fail to change their active state. Also in the comment section @mertkahyaoglu said that he would simply put an option {pure: false} to connect() but it does not work for me.

Thanks for the info mate :D
I don't know if you've seen but they said that the problem should be fix with react-router@next and 3.0. It worked for me :)
Cheers gaulucky !


Installing from Homebrew on M1 mac

==> Downloading https://github.com/thoughtbot/complexity/archive/0.3.0.tar.gz
Already downloaded: /Users/briantenggren/Library/Caches/Homebrew/downloads/ccb5fd1da73aa8733102237a645c4bdebb8ac258d9fbd417a20f694f0a2a3505--complexity-0.3.0.tar.gz
==> Installing complexity from thoughtbot/formulae
==> cargo install
Last 15 lines from /Users/briantenggren/Library/Logs/Homebrew/complexity/01.cargo:
     |
1254 |     let div = n / bits;
     |                 ^ no implementation for `usize / u32`
     |
     = help: the trait `Div<u32>` is not implemented for `usize`

   Compiling dirs-next v2.0.0
Some errors have detailed explanations: E0277, E0308.
For more information about an error, try `rustc --explain E0277`.
error: could not compile `lexical-core` due to 27 previous errors
warning: build failed, waiting for other jobs to finish...
error: failed to compile `complexity v0.3.0 (/private/tmp/complexity-20220302-14250-1nwsd5q/complexity-0.3.0)`, intermediate artifacts can be found at `/private/tmp/complexity-20220302-14250-1nwsd5q/complexity-0.3.0/target`

Caused by:
  build failed

If reporting this issue please do so at (not Homebrew/brew or Homebrew/core):
  https://github.com/thoughtbot/homebrew-formulae/issues

These open issues may also help:
Release complexity 0.4.1 https://github.com/thoughtbot/homebrew-formulae/pull/71

When running
brew tap thoughtbot/formulae
brew install complexity

Successfully installed! Unable to run though

@brimatteng yeah, that exception you're seeing isn't super helpful – I'm sorry about that.
Any chance you have a working Rust environment set up locally? I have a hunch that it's related to MiMalloc (it speeds up execution by ~22% on my machine over the default Rust allocator, which isn't nothing!) If you do, I'm happy to push a branch up for you to build locally and verify MiMalloc is the culprit.

@brimatteng as a reference, here's the corresponding change in another tool I'd built https://github.com/unused-code/unused/pull/37 and the corresponding Homebrew formula change: https://github.com/unused-code/homebrew-formulae/commit/c8abd145963af5347d4c2bde698766ee75c8bec2

Ive maybe got some time tomorrow i can take a crack at it. It's hard to debug the brew version so building it locally might do better


fix: prepaid recycle host not check storage types

这个 PR 实现什么功能/修复什么问题:
修复: prepaid recycle host 调度时不校验　storage_type
是否需要 backport 到之前的 release 分支:

release/2.9.0
release/2.8.0

/cc @swordqiu
/area scheduler

/cherrypick release/2.9.0

Codecov Report

Merging #591 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #591      +/-   ##
=========================================
+ Coverage    7.41%   7.41%   +<.01%
=========================================
  Files         346     346
  Lines       54718   54718
=========================================
+ Hits         4055    4057       +2
+ Misses      50283   50282       -1
+ Partials      380     379       -1

Flag
Coverage Δ

#aFlag
7.41% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/util/seclib2/seclib.go
95.74% <0%> (+4.25%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


WIP: Fix broken test

@James-Sangalli the debug button seems to be missing here https://travis-ci.com/alpha-wallet/alpha-wallet-ios. Maybe after the repo migration? Do you know how we can get it back?

@James-Sangalli oh. According to https://docs.travis-ci.com/user/running-build-in-debug-mode/#enabling-debug-mode

Private repositories have debug mode enabled by default, and no changes need to be made. To limit access to debug, grant users only read access to the repo, and use a fork + PR workflow. For public repositories, we have to enable it on a repository basis.
To enable debug for your public repositories, please email us at<EMAIL_ADDRESS>and let us know which repositories you want activated.

@hboon just transferred the subscription to alpha-wallet org


Add reflection checking

We want to add reflection checking of java codes for OOP courses.
The high-level operations should probably be like the following:

The request comes through the bouncer, which detects that the checker is set to reflection and invokes ReflectionCheckerJava lambda instead of CodeRunner<LANG> lambda.
ReflectionCheckerJava is a lambda with a Java runtime. It should follow the request/response model present in models.py

The changes required:

Add a new directory for reflection checking
Add a new lambda for reflection checking
invoke that lambda from the bounce if the appropriate checker is set

Would be great to have this for Python instead of Java. This will be a great foundation for the advanced Python course.

Apparently, we are able to do this without a specific checker - we just use the inspect module of Python + custom checker.


Reorganize tendermint_proto::abci to clean up module organization and conform to Rust RFC356

Currently, the ABCI types in tendermint_proto have the structural content filled in, but aren't nicely organized yet:

Rust's RFC356 recommends that type names should avoid having common prefixes, and instead use module paths to factor a name into components, for instance having abci::request::{Commit, CheckTx} instead of abci::{RequestCommit, RequestCheckTx}.  This has the advantage that the user of the name can decide which parts of the name are required, writing any of

abci::request::Commit,
request::Commit,
Commit,

depending on how much context is assumed at the use site. It also makes navigating the related types in the docs more clear, since the types are organized into categories.
What's the definition of "done" for this issue?
To tidy the module organization:

[ ] rename and move RequestFoo to request::Foo;
[ ] move the Request enum to request and pub use it in the abci module;
[ ] rename and move ResponseFoo to response::Foo;
[ ] move the Response enum to response and pub use it in the abci module;
[ ] eliminate the response_apply_snapshot_chunk and response_offer_snapshot modules, by either:

option A: rename response_apply_snapshot_chunk::Result to response::ApplySnapshotChunkResult (least impact on code that currently uses the structure, it's a clean rename);
option B: change the data modeling of ApplySnapshotChunk and OfferSnapshot to hold enums internally (need to make non-mechanical changes to using code, but potentially cleaner in the long run);

I would pick option A above.
To fill in the documentation:

[ ] Document all requests and responses and all fields, copying descriptions from the Methods and Types spec page.

To make it easier to model the four ABCI connections:
Create per-connection enums:

[ ] ConsensusRequest/ConsensusResponse;
[ ] MempoolRequest/MempoolResponse;
[ ] InfoRequest/InfoResponse;
[ ] SnapshotRequest/SnapshotRequest;

with conversions impl From<FooRequest> for Request (infallible, all variants of the per-connection enum are variants of the full enum) and impl TryFrom<Request> for FooRequest (fallible, not all variants of the full enum are variants of the per-connection enum).

The data modeling suggested above could instead be done on a set of domain types in the tendermint crate, with conversions to/from the proto types.

Makes sense :+1:

Cool, I'll instead work on a PR to produce those types as part of tendermint::abci?

Yes, I think that makes sense. I've been debating whether or not to implement domain types for the ABCI data structures for some time now, and can summarize the pros and cons I've thought of as follows:
Pros

We can potentially shield ABCI users from breaking Protobuf changes (e.g. through the use of defaults for new fields, where applicable).
We can structure them in a way that's more consistent with Rust's API guidelines (as per the core issue here in #856).
We can attach additional documentation to them, explaining them better.
We have the freedom to implement conversions to/from other types quite easily.

Cons

For significant breaking changes in the Protobuf definitions, we need to manually update these data structures.
There's more code to maintain (structures, documentation and conversions).

Ultimately it comes down to the fact that it's more work to maintain them, but I think the benefits are worth the effort.
@romac, what do you think?

I am personally a bit wary of exposing the Protobuf type directly, as to me they are a serialization concern only, and I would rather expose properly designed Rust domain types, for all the pros you list above.
At the same time I don't want to dismiss the cost of having to maintain this extra code, but if you ask me the pros outweigh the cons for the benefit of the users of the library.

I don't think there's a tension between exposing domain types and exposing protobuf types. There are use-cases that require domain types and use-cases that require raw protos.  It seems like the problem is that if there's only one set of types, those use cases get conflated.
Even if there are well-modeled domain types and the protos are only a serialization concern, they're still required for anything that needs to work with serialization.  For example, I'm working on an alternative ABCI interface.  I would like that interface to use well-modeled domain types, but internally it needs to know about the protos to be able to speak TSP.
I'm not sure exactly what was meant by "wary of exposing the Protobuf type directly", so my apologies if I misunderstood what you meant, but I don't think it makes sense to try to hide the protos completely, since they're part of the ecosystem.  Keeping them in a separate crate means they can be versioned independently of the main API, and people don't need to use them by default. They can opt-in by using the tendermint_proto crate, which has a different level of API.

@hdevalence I fully agree with you! I should have been clearer about what I meant by "wary of exposing the Protobuf type directly", which is that I would not want to expose the Protobuf types directly in the public API. We definitely want to export them somehow (either in the tendermint_abci or tendermint_proto crate) for others to use for serialization. Apologies for the misunderstanding, and thank you for your comment!

Closed by #1022


Update GitHub Actions workflow and remove unused SVG file

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

Project coverage is 98.71%. Comparing base (6bdb989) to head (3d2701c).
Report is 6 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #124   +/-   ##
=======================================
  Coverage   98.71%   98.71%
=======================================
  Files          45       45
  Lines        1870     1870
=======================================
  Hits         1846     1846
  Misses         24       24

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


I can't download older photos from profiles

Ripme version: 1.7.82
Java version: Java SE 12.0.1
Operating system: Windows 10 Pro

Exact URL you were trying to rip when the problem occurred: https://twitter.com/mattyan7010
Please include any additional information about how to reproduce the problem: I was trying to download older photos from this profile (which are many many) but I couldn't. There's no error display or anything, it just doesn't download older pictures. Can you help me? I apologize for any problem. I'm new to Github and I know nothing about this place. Just wanted to post my issue. Thank you for reading.

Expected Behavior
Detail the expected behavior here.
Actual Behavior
Detail the actual (incorrect) behavior here. You can post log snippets or attach log files to your issue report.

This is a known issue


Room Setup Connection Loss - SteamVR-OSVR-Win-Build-v0.1-170-g09dc772-core-v0.6-1194-g0c54f5e

Hey guys,
I've tried out the new SteamVR driver and it seems to be working well.
I can confirm I've gotten it to work in direct mode.
Setup required a .json replacement with the directmode.json and a restart for it to take effect.
The only issue I'm having, is that Room Setup is still kicking up a fuss. When running games normally, things are running fine (feels like better than before tbh) but when running room setup, the connection is dropping every 4-6 seconds.
I was still able to the initial room setup procedure and get to the "put your headphones and HMD on now", at which point, when loaded into the livingroom, the OSVR would lose connection to SteamVR and jutter in one direction for half a second then reset it's position.
After roughly a minute, Room Setup just crashed.
I have the SteamVR output log below. If you require a video demonstration of the issue I'm running into, let me know and I'll setup the camera.
output_log.txt

Hi,
I've the connection issue in Unity using OpenVR too..

We recently updated the SteamVR-OSVR plugin to allow it to complete room setup. Please try the latest version of the plugin with the latest released version of SteamVR and see if this resolves the problem.


and_wrap_original doesn't work with kwargs in Ruby 3.2

and_wrap_original doesn't work with kwargs in Ruby 3.2
Your environment

Ruby version: 3.2.1
rspec-mocks version: 3.12.3

Steps to reproduce
Add the following spec to the "on a partial double" context of and_wrap_original_spec.rb, which is based on a similar spec from and_call_original_spec.rb:
if RSpec::Support::RubyFeatures.kw_args_supported?
  binding.eval(<<-CODE, __FILE__, __LINE__)
  it "works for methods that accept keyword arguments" do
    def instance.foo(bar: nil); bar; end
    allow(instance).to receive(:foo).and_wrap_original { |m, *args| m.call(*args) }
    expect(instance.foo(bar: "baz")).to eq("baz")
  end
  CODE
end

It will fail on the current version of rspec-mocks with wrong number of arguments (given 1, expected 0). Work was done to fix this for and_call_original in #1464 but a similar workaround was not added for and_wrap_original. If you modify the definition of and_wrap_original like so:
def and_wrap_original(&block)
  block = block.ruby2_keywords if block.respond_to?(:ruby2_keywords) # New

  wrap_original(__method__, &block)
end

It will pass the additional spec above, but other specs will fail with:
Failure/Error: raise "Warnings were generated: #{output}" if has_output?

      RuntimeError:
        Warnings were generated: rspec-mocks/lib/rspec/mocks/message_expectation.rb:163: warning: Skipping set of ruby2_keywords flag for proc (proc accepts keywords or proc does not accept argument splat)

I can't say that I understand enough about the inner workings of ruby2_keywords and its use with different types of procs/blocks to figure this out, otherwise I would've opened up a PR for the change. You can see my WiP on my branch here.
Expected behavior
and_wrap_original works with methods that expect kwargs
Actual behavior
and_wrap_original fails with methods that expect kwargs

The following crutch worked, but I have serious doubts that it would work correctly for all cases of user-provided blocks:
        if block && block.parameters.first.first == :rest
          block.ruby2_keywords if block.respond_to?(:ruby2_keywords)
        end

So I ran your spec and it passed without any code changes on 3.1, so it only fails on 3.2 and using **kwargs here in the block works correctly for both 3.1 and 3.2, so I'm honestly leaning towards saying "you should manage this block yourself here", I think any improvement we should make here should be more directed at it failing correctly...

Closing this but going to increase documentation over in #1525 this spec works as:
it "works for methods that accept keyword arguments" do
  def instance.foo(bar: nil); bar; end
  allow(instance).to receive(:foo).and_wrap_original { |m, **kwargs| m.call(**kwargs) }
  expect(instance.foo(bar: "baz")).to eq("baz")
end


fix bugs: cannot get lookup value when lookup source field is not def…

…ault Title field

Q
A

Bug fix?
[x]

New feature?
[ ]

New sample?
[ ]

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Fix bug: #1215
DynamicForm cannot display lookup value when the lookup source field is not Title. The SPService class loading lookup value always expand lookupField/Title.
Guidance

You can delete this section when you are submitting the pull request.
Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to dev branch.

This pull request cannot fix the issue.

Hello
I have a bug in this component
cannot get lookup value when lookup field to show is not Title
exemple: field/Title worked but field/othercolumn not work
defaultSelectedItems={[{key:'1733',name:'undefined' }]}  in ListItemPicker
this bug in ListItemPicker  only

attached a picture of the difference between fields with Title and other.
cordially,
Zied


Any idea about image caption implementation.

HI there,
Thanks for the great reproduction!
I just wonder if there is any plan to implement image caption under the framework proposed in tranfusion paper.
Thanks

@Ma-Weijian the example here is by default captioning - for text-to-image, just set this to True

@Ma-Weijian had it backwards, my bad!

This script generates following error when turned "IMAGE_AFTER_TEXT = False" for image captioning , I have tried multiple times and got same result.
Traceback (most recent call last):
File "/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/train_mnist.py", line 130, in
one_multimodal_sample = ema_model.sample(max_length = 384)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/ccs/home/palashmr/packages/miniconda/pyt_env/transfusion/lib/python3.12/site-packages/torch/utils/contextlib.py", line 116, in decorate_context
return func(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^
File "/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/transfusion_pytorch/transfusion.py", line 154, in inner
out = fn(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/transfusion_pytorch/transfusion.py", line 1322, in sample
*, last_modality_sample = modality_sample
^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected at least 1, got 0)

ah I'll have to get back to you on this next week, it is the weekend here.
On Sat, Nov 30, 2024, 12:09 PM mijanur132 @.***> wrote:

This script generates following error when turned "IMAGE_AFTER_TEXT =
False" for image captioning , I have tried multiple times and got same
result.
Traceback (most recent call last):
File
"/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/train_mnist.py",
line 130, in
one_multimodal_sample = ema_model.sample(max_length = 384)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File
"/ccs/home/palashmr/packages/miniconda/pyt_env/transfusion/lib/python3.12/site-packages/torch/utils/
*contextlib.py", line 116, in decorate_context return func(*args,
**kwargs) ^^^^^^^^^^^^^^^^^^^^^ File
"/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/transfusion_pytorch/transfusion.py",
line 154, in inner out = fn(self, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^ File
"/lustre/orion/stf218/proj-shared/brave/transfusion-pytorch/transfusion_pytorch/transfusion.py",
line 1322, in sample **, last_modality_sample = modality_sample
^^^^^^^^^^^^^^^^^^^^^^^^
ValueError: not enough values to unpack (expected at least 1, got 0)
—
Reply to this email directly, view it on GitHub
https://github.com/lucidrains/transfusion-pytorch/issues/26#issuecomment-2509187522,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA2Q3NRTHWRIU6SWNSTFOD2DILRNAVCNFSM6AAAAABSR6V6HOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBZGE4DONJSGI
.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Compatibility with MultiDiscrete spaces as observation_space

Using a space_observation of type MultiDiscrete throws an error on PPO (also tested with ACKTR) use. The error is no present if a Discrete type observation_space is used.
For a very basic test environment the broken env uses:
self.observation_space = spaces.MultiDiscrete([[0, 12], [0, 250]])
With returned observation:
 def _get_obs(self):
 return np.array([self.variable1,  self.variable2])

Whereas for testing purposes, which works, a Discrete environment:
self.observation_space = spaces.Discrete(3000)
With returned observation:
def _get_obs(self):
return np.array([self.variable1])

When using a MultIDiscrete type observation_space, the thrown error is then:

Traceback (most recent call last):
File "", line 1, in
runfile('C:/Users/MainUser/Desktop/untitled0.py', wdir='C:/Users/X/Desktop')
File "D:\Programs\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 705, in runfile
execfile(filename, namespace)
File "D:\Programs\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 102, in execfile
exec(compile(f.read(), filename, 'exec'), namespace)
File "C:/Users/MainUser/Desktop/untitled0.py", line 44, in
env = DummyVecEnv([lambda: env])  # The algorithms require a vectorized environment to run
File "D:\Programs\Anaconda3\lib\site-packages\stable_baselines\common\vec_env\dummy_vec_env.py", line 35, in init
self.buf_obs = {k: np.zeros((self.num_envs,) + tuple(shapes[k]), dtype=dtypes[k]) for k in self.keys}
File "D:\Programs\Anaconda3\lib\site-packages\stable_baselines\common\vec_env\dummy_vec_env.py", line 35, in
self.buf_obs = {k: np.zeros((self.num_envs,) + tuple(shapes[k]), dtype=dtypes[k]) for k in self.keys}
TypeError: 'tuple' object cannot be interpreted as an integer

As for the code which originates said problem, it was simply retrieved from the examples page (the random agent, meaning, evaluate function works fine for both cases, the problem is in directly using the models) to ensure the problem wasn't in my code:
def evaluate(model, num_steps=1000):
  """
  Evaluate a RL agent
  :param model: (BaseRLModel object) the RL Agent
  :param num_steps: (int) number of timesteps to evaluate it
  :return: (float) Mean reward for the last 100 episodes
  """
  episode_rewards = [0.0]
  obs = env.reset()
  for i in range(num_steps):
      # _states are only useful when using LSTM policies
      action, _states = model.predict(obs)
      # here, action, rewards and dones are arrays
      # because we are using vectorized env
      obs, rewards, dones, info = env.step(action)

      # Stats
      episode_rewards[-1] += rewards[0]
      if dones[0]:
          obs = env.reset()
          episode_rewards.append(0.0)
  # Compute mean reward for the last 100 episodes
  mean_100ep_reward = round(np.mean(episode_rewards[-100:]), 1)
  print("Mean reward:", mean_100ep_reward, "Num episodes:", len(episode_rewards))

  return mean_100ep_reward

env = gym.make('Test-v0')
# vectorized environments allow to easily multiprocess training
# we demonstrate its usefulness in the next examples
env = DummyVecEnv([lambda: env])  # The algorithms require a vectorized environment to run

model = ACKTR(MlpPolicy, env, verbose=0)

# Random Agent, before training
mean_reward_before_train = evaluate(model, num_steps=10000)

# Train the agent for 10000 steps
model.learn(total_timesteps=10000)

# Evaluate the trained agent
mean_reward = evaluate(model, num_steps=10000)

Hello,
Thanks for reporting the issue.
Could you please follow the issue template and provide a minimal yet complete code to reproduce the error?

Hello,
Thanks for the update.
I suspect your issue is related to this one: https://github.com/openai/gym/issues/1191
What is your gym version?

Are you sure you are using 0.10.5? Did you install it with pip?
On my computer, the following code raises an error (with this gym version):
spaces.MultiDiscrete([[0, 12], [0, 250]])

AssertionError: nvec should be a 1d array (or list) of ints
What you want to do is:
spaces.MultiDiscrete([12, 250])

no ? (12 and 250 discrete actions)

That's strange, yes I installed it via Pip and it is definitely 0.10.5.
I never got an error, it is how the Hands‑On Intelligent Agents with OpenAI Gym book defines the space is to be used, but, I have changed it to your recommendation (although I'm working with an observation space, not an action space but I take it its the same), and the problem persists, exactly as before.

I never got an error

I created a colab notebook so you can reproduce the error (with gym 0.10.5): https://colab.research.google.com/drive/1KDWriJMxBv8rtqjvGEu6Qz9bzZvtKt-B
With the latest version of gym (0.10.8), there is no error but the shape is changed (and that causes the error in the vec env): https://colab.research.google.com/drive/1oDOxpECm5mU-joHy_lnLwPGBQkgTaHCh

I have changed it to your recommendation

If you don't have any error with your original, then my recommendation won't work anyway.

Ah I see.
Should I then use an older gym version before the shape is changed?

Yes,
I would recommend using 0.10.5 (with my recommendation for declaring the space).
I am waiting for OpenAI answer. If breaking things (i.e. no backward compatibility) is what they wanted, we will have to patch stable-baselines, otherwise, we will wait for a fix from gym.

You are right.
All fixed up, thank you for your help. Hopefully they will fix their end soon enough.
Now to get SubprocEnv working, which seems to not work. I'll run some more testing and open a new issue if needed.
Once again, thank you.


💡[FEATURE]: Add a Customized Scrollbar to match the theme of the site.

Is your feature request related to a problem? Please describe.
Currently, RapiDoc lacks a customized scrollbar that matches the overall theme, which affects the visual coherence and user experience.
Describe the solution you'd like
Integrate a customized scrollbar that harmonizes with the site's theme. This enhancement will not only improve aesthetics but also contribute to a seamless browsing experience.
kindly assign me this issue.

@Vimall03 Hi! can you please assign me this issue under GSSoC'24

I am thrilled to be participating in GirlScript Summer of Code 2k24 as a passionate computer science student with a keen interest in web development. I am eager to contribute to your project and leverage my skills to make meaningful contributions. I look forward to collaborating with you and the team to create impactful solutions.
@HimanshuNarware Sir, I would really like to work on this issue, so please assign it to me.


Subprocess

Hello,
i created a script using subprocess.call ('playerctl play', shell = True) and playerctl indicates no player found while in linux terminal it works, why?

Please open this on the playerctl repo.


Fix for #1775 - Added missing voume mounts to docker compose file

Related issues
#1775
Short description and why it's useful
Added missing volume mounts to default docker-compose.yml file

Thanks!


Update config to allow TLS config passing

In order to work in certain situations; it would be useful if Levant allows the user to pass TLS certificate details on deployment including the following:

ca-cert
cert
cert-key

As far as I can tell this should already work.
func NewNomadClient(addr string) (NomadClient, error) {
	config := nomad.DefaultConfig()

This returns a defaultconfig from github.com/hashicorp/nomad/api which parses the following ENV vars:
NOMAD_ADDR (Nomad HTTP API endpoint)
NOMAD_HTTP_AUTH (basic auth username:password)
NOMAD_CACERT (path to a PEM-encoded CA cert file )
NOMAD_CAPATH (path to a directory of PEM-encoded CA cert files)
NOMAD_CLIENT_CERT (path to the client certificate)
NOMAD_CLIENT_KEY (path to the client key)
NOMAD_SKIP_VERIFY (enable or disable verification; (true|1) / (false|0) )


works fantastic but i'm not that smart to understand the underlying mechanism of auto pipelining...

All non-blocking concurrent commands are automatically pipelined through connections, which reduces the overall round trips and system calls, and gets higher throughput.

questions:

can u show an example of non-blocking concurrent commands vs blocking "concurrent" or "non-concurrent" commands? do u mean multi-exec in this case or... set command that does not need returned values?
can u put this into readme of ruiedis front page under FAQ?
i'm using it heavily across deployments and hope that this "mechanism" is explained for reference (in terms of roadmap of ruiedis dev. i'm not sure if u are looking for us to be able to send at lowest latency or highest throughput or how to do settings for those)
how to set the "auto pipelining settings?" as in time (by duration) or batched connection "pushing" / command sending. (number of bytes over txn per second)
where is the "code section" / files that does this magic of auto pipelining? (for reference)

currently being used in production as IPC and it's working as expected. hope to push the limitations further!
when there's a buymeacoffee section, hope to be the first to buy u coffee!

Hi @ultperf,
The non-blocking I mentioned in that section refers to Redis non-blocking commands, such as GET, and SET commands. Whereas BLPOP and XREAD BLOCK are Redis blocking commands. Then the concurrent commands means multiple client.Do() invocations from multiple goroutines at the same time.
Hope that now you can understand more about this mechanism. I have updated the auto-pipelining section of the readme with more detail and a new example.
The auto-pipelining mechanism tries to fully utilize your go runtime scheduling capability by default. Currently, there are only two options to tune its behavior, which are PipelineMultiplex and MaxFlushDelay of rueidis.ClientOption.
All the magic behind the mechanism is at here https://github.com/rueian/rueidis/blob/main/pipe.go#L222.


libsnowcrash.so not found

Just installed this on a clean ubuntu 14.04 VM, and getting this error:
could not open library '/var/lib/gems/1.9.1/gems/redsnow-0.2.1/ext/snowcrash/build/out/Release/lib.target/libsnowcrash.so': /var/lib/gems/1.9.1/gems/redsnow-0.2.1/ext/snowcrash/build/out/Release/lib.target/libsnowcrash.so: cannot open shared object file: No such file or directory (LoadError)

I notice that the snowcrash library was recently updated. Could it be related? If not, any other ideas?

Redsnow was removed from apiary-client.


Refactor: introduce Publisher class

As per subject.
This introduces a lightweight abstraction around writing serialised message tables to the file descriptor we use to communicate with the Python side.
Besides making the code in modROS.lua somewhat easier to read, this also prevents implementation details about how we currently publish from leaking everywhere.
This is also preparation for the introduction of sensor classes, which are responsible for publishing their own messages.
Tested in FS.

Edit: I've gone back and added a "connection" abstraction as well. Right now this is just a simple wrapper around the file descriptor, but if/when we have something else (a socket?) this would make it easy to switch to that. The connection also decouples initialisation of dependent objects (such as the publishers) from the state of the file descriptor itself, making for slightly nicer resource management.

Updated the PR and rebased.

Thanks @tckarenchiang.


Create CONTRIBUTING.md

Starting a mini-project to add contribution guidelines to PACE-HRH

Now that Ryan has finished a first sizeable PR, I'm going to start adding him as a reviewer on my own PRs so he continues to gain familiarity with the codebase.

I see that you fixed a file to match the new style requirements. Do we intend to clean up all the source files as part of this PR?

I see that you fixed a file to match the new style requirements. Do we intend to clean up all the source files as part of this PR?

Great question! I think we should pull together a deliberate plan to fix everything up. So not everything right now ... but let's put a plan in place.

Is this tool https://github.com/r-lib/styler compatible with the style defined?

Styler is a great alternative to the RStudio Code/Reformat Code command to get code quickly to a good place.
But that said, lintr should be our definitive reference tool because we can eventually automate lintr::lint() checking into a GH Action, if we so choose.

template for GA https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287 , maybe we can customize based on above info

Almost finished! With these commits the code in the R directory (not the unit test code) passes linting.

@MeWu-IDM  and @RHull-IDM :
Ready to review. I apologize for touching pretty much every source file. https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/286/commits/a93e611d523a5477e712b56e4d8b1f7ca2258cbd is the only commit that makes a substantial code change. Note that I added a .lint file for lint configuration.

I saw warning from the check:, I think you should add these files to the  .Rbuildignore

.lintr
 vignettes/.gitignore
These were most likely included in error. See section ‘Package
structure’ in the ‘Writing R Extensions’ manual.

When I run lint check on the package, I am still seeing a few issues

Error: Not lint free
R\pace_exp_control.R:53:6: style: [indentation_linter] Indentation should be 8 spaces but is 6 spaces.
      is.null(BVE$seasonalityCurves) ||
     ^~~

R\pace_prevalence_matrix.R:100:10: style: [indentation_linter] Indentation should be 8 spaces but is 10 spaces.
          tasks$ServiceCat == "Tuberculosis" | tasks$ServiceCat == "HIV"
        ~^

R\pace_table_schemas.R:135:4: style: [indentation_linter] Indentation should be 2 spaces but is 4 spaces.
    )
  ~^

tests\testthat\setup.R:40:1: style: [object_name_linter] Variable and function name style should match camelCase, CamelCase or symbols.
local_vars <- function(vars = vector(), envir = parent.frame(), .local_envir = parent.frame()){
^~~~~~~~~~

tests\testthat\setup.R:40:65: style: [object_name_linter] Variable and function name style should match camelCase, CamelCase or symb

Files added to .gitignore (practicing my Perl-style regex)
Turns out my version of lintr wasn't up-to-date, and didn't include the indentation_linter(). Frustratingly, styler was up-to-date, but fails sometimes to style in a way that passes the default indentation_linter() settings. Indentation problems are easy to fix, so I stopped trying to configure indentation_linter() to line up with styler.
@MeWu-IDM : I fixed up the files in the R directory, but I wasn't planning on styling the unit test code (tests\testthat*). Can the build-time linting be restricted to the R directory?

@MeWu-IDM : Please investigate.

@celiot-IDM
This error is due to debian release 12.1 on July22
I have a temporary fix in  https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287/files
I also add tests to exclude list
I see this lint_check still fails in https://github.com/InstituteforDiseaseModeling/PACE-HRH/actions/runs/5767054196/job/15636111794#step:7:142
are these warning appear on your end?

@celiot-IDM This error is due to debian release 12.1 on July22 I have a temporary fix in https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287/files I also add tests to exclude list I see this lint_check still fails in https://github.com/InstituteforDiseaseModeling/PACE-HRH/actions/runs/5767054196/job/15636111794#step:7:142 are these warning appear on your end?

Those lint failures make no sense ... they imply that the package references list (eg. traceMessage function label) has disappeared. More likely a build problem than a lint problem.

@celiot-IDM This error is due to debian release 12.1 on July22 I have a temporary fix in https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287/files I also add tests to exclude list I see this lint_check still fails in https://github.com/InstituteforDiseaseModeling/PACE-HRH/actions/runs/5767054196/job/15636111794#step:7:142 are these warning appear on your end?

Those lint failures make no sense ... they imply that the package references list (eg. traceMessage function label) has disappeared. More likely a build problem than a lint problem.

Are you looking at the error link from my other PR? They are something like this:
Error: Not lint free
R/pace_cadre_config.R:8:40: warning: [object_usage_linter] no visible binding for global variable '.defaultCadreRolesSheet'
loadCadreRoles <- function(sheetName = .defaultCadreRolesSheet) {

@celiot-IDM This error is due to debian release 12.1 on July22 I have a temporary fix in https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287/files I also add tests to exclude list I see this lint_check still fails in https://github.com/InstituteforDiseaseModeling/PACE-HRH/actions/runs/5767054196/job/15636111794#step:7:142 are these warning appear on your end?

Those lint failures make no sense ... they imply that the package references list (eg. traceMessage function label) has disappeared. More likely a build problem than a lint problem.

Are you looking at the error link from my other PR? They are something like this:
Error: Not lint free R/pace_cadre_config.R:8:40: warning: [object_usage_linter] no visible binding for global variable '.defaultCadreRolesSheet' loadCadreRoles <- function(sheetName = .defaultCadreRolesSheet) {

Yep, we're looking at the same thing. This message is claiming that .defaultCadreRolesSheet isn't defined, but it is in pace_package_env.R:

Something else is going on in the build to lose track of global variable names.

@celiot-IDM This error is due to debian release 12.1 on July22 I have a temporary fix in https://github.com/InstituteforDiseaseModeling/PACE-HRH/pull/287/files I also add tests to exclude list I see this lint_check still fails in https://github.com/InstituteforDiseaseModeling/PACE-HRH/actions/runs/5767054196/job/15636111794#step:7:142 are these warning appear on your end?

Those lint failures make no sense ... they imply that the package references list (eg. traceMessage function label) has disappeared. More likely a build problem than a lint problem.

Are you looking at the error link from my other PR? They are something like this:
Error: Not lint free R/pace_cadre_config.R:8:40: warning: [object_usage_linter] no visible binding for global variable '.defaultCadreRolesSheet' loadCadreRoles <- function(sheetName = .defaultCadreRolesSheet) {

Yep, we're looking at the same thing. This message is claiming that .defaultCadreRolesSheet isn't defined, but it is in pace_package_env.R:

Something else is going on in the build to lose track of global variable names.

It might be this https://github.com/r-lib/lintr/issues/1137
I Will Check more on Monday


Web UI hangs in main.js

running MPD.FM at the console returns:
sh-5.1$ /usr/bin/node /home/srv-mpd-fm/MPD.FM/bin/www
Station file "/home/srv-mpd-fm/MPD.FM/data/stations.json" will be used
MPD client ready and connected to localhost:6600
then a connect from browser returns:
GET / 200 46.571 ms - 5045
GET /css/pure-min.css 200 10.389 ms - 16449
GET /css/main.css 200 14.537 ms - 2835
GET /js/plugins.js 200 26.256 ms - 760
GET /js/vendor/ReconnectingWebSocket.js 200 25.816 ms - 14429
GET /js/main.js 200 26.496 ms - 9383
GET /img/pause.svg 200 23.674 ms - 865
GET /img/play.svg 200 24.604 ms - 820
GET /icon.png 200 3.814 ms - 16358
In the browser I see an incompletely loaded page, with progress dots marching over a amshed up combo of play\pause buttons. In viewing the browsers dev tools... Console...
Uncaught TypeError: Vue.component is not a function
 http://<IP_ADDRESS>:4200/js/main.js:17
main.js:17
Vue.component('radio-station', {
props: ['station']
})
There's also a warning about using a development version of vue.global.js instead of a production version. It appears to be loading from a cdn in the cloud.
The incompletely load webpage reports:
Can't reach server - trying to reconnect...
The server can't reach MPD - trying to reconnect...
in the page. This is as far as I get. The default stations.json never loads.
I'm running this on intel hardware and Debian Bullseye.

I'm seeing the same thing.  I'm not sure how to debug this.  I don't know if the error is in the MPD service itself or if the issue is with MPD.FM.   There hasn't been any updates to MPD.FM since 2018 so it's entirely possible that something has changed with MPD that broke it.
Also, I think the URL for the first station in the stations.json file isn't valid anymore...
https://bytefm.sslcast.addradio.de/bytefm/main/high/stream.mp3
I believe that this is a working streaming URL for ByteFM...
https://bytefm--di--nacs-ice-01--01--cdn.cast.addradio.de/bytefm/main/mid/stream.mp3

I've managed to update the app so that it works correctly with the latest version of Vue.  I've created a pull request...
https://github.com/florianheinemann/MPD.FM/pull/8
...from my modified fork...
https://github.com/wkrick/MPD.FM

@wkrick Just wanted to say thanks for the fork. My PI had been in storage for some time, and MPD.FM had stopped working. Switching to your fork has it up and running again. Super happy!


Document leader-election configuration

Changes
The leader-election config did not describe what the options did and were set to the default values. See https://github.com/knative/pkg/blob/e60d250dc6378c387c8c9d149774ee21e9a827ab/leaderelection/config.go#L121-L127
This commit adds block of commented out example config (like we do in config-defaults). The actual content was taken from https://github.com/knative/serving/blob/f9951ecf37709bb160fd513591e84b6e6f50f6f8/config/core/configmaps/leader-election.yaml
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] Has Docs included if any changes are user facing
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
[x] Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

Are we currently actively using these configuration options, and this PR is replacing them with invalid configuration? Is this documentation code block intended for tekton developers or cluster operators using tekton?

Are we currently actively using these configuration options,

Yes, we support a HA mode. The config file was essentially a no-op since it was supplying default values - those values are also present in the code.

and this PR is replacing them with invalid configuration? Is this documentation code block intended for tekton developers or cluster operators using tekton?

This is a configuration with no values specified which means the HA code will use the default config from the code. The docs are mostly intended towards cluster operators.


core: fix join position in select sql builder

Welcome to Codecov :tada:
Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


⚠ Mobitopup has degraded performance

In 8ad394f, Mobitopup (https://napcard.voz.tech) experienced degraded performance:

HTTP code: 200
Response time: 6410 ms

Resolved: Mobitopup performance has improved in 5d2e3d0.


Dependency uprade to 1.25

Signed-off-by: Ambika Nair<EMAIL_ADDRESS>

Events:
  Type    Reason          Age   From               Message
  ----    ------          ----  ----               -------
  Normal  Scheduled       17s   default-scheduler  Successfully assigned kube-system/ibm-vpc-block-csi-controller-0 to <IP_ADDRESS>
  Normal  AddedInterface  17s   multus             Add eth0 [<IP_ADDRESS>/32] from k8s-pod-network
  Normal  Pulling         17s   kubelet            Pulling image "k8s.gcr.io/sig-storage/csi-snapshotter:v6.1.0"
  Normal  Pulled          16s   kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/csi-snapshotter:v6.1.0" in 816.591928ms
  Normal  Created         16s   kubelet            Created container csi-snapshotter
  Normal  Started         16s   kubelet            Started container csi-snapshotter
  Normal  Pulling         16s   kubelet            Pulling image "k8s.gcr.io/sig-storage/csi-provisioner:v3.3.0"
  Normal  Pulled          15s   kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/csi-provisioner:v3.3.0" in 909.001587ms
  Normal  Created         15s   kubelet            Created container csi-provisioner
  Normal  Started         15s   kubelet            Started container csi-provisioner
  Normal  Pulling         15s   kubelet            Pulling image "k8s.gcr.io/sig-storage/csi-attacher:v4.0.0"
  Normal  Pulled          14s   kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/csi-attacher:v4.0.0" in 1.013998586s
  Normal  Created         13s   kubelet            Created container csi-attacher
  Normal  Pulling         13s   kubelet            Pulling image "k8s.gcr.io/sig-storage/csi-resizer:v1.6.0"
  Normal  Started         13s   kubelet            Started container csi-attacher
  Normal  Pulled          12s   kubelet            Successfully pulled image "k8s.gcr.io/sig-storage/csi-resizer:v1.6.0" in 820.895865ms
  Normal  Created         11s   kubelet            Created container csi-resizer
  Normal  Started         11s   kubelet            Started container csi-resizer
  Normal  Pulled          11s   kubelet            Container image "k8s.gcr.io/sig-storage/livenessprobe:v2.8.0" already present on machine
  Normal  Created         11s   kubelet            Created container liveness-probe
  Normal  Started         10s   kubelet            Started container liveness-probe
  Normal  Pulling         10s   kubelet            Pulling image "ambikanair/ibm-vpc-block-csi-driver:thelatest"
  Normal  Pulled          9s    kubelet            Successfully pulled image "ambikanair/ibm-vpc-block-csi-driver:thelatest" in 1.157464365s
  Normal  Created         9s    kubelet            Created container iks-vpc-block-driver
  Normal  Started         9s    kubelet            Started container iks-vpc-block-driver
  Normal  Pulling         9s    kubelet            Pulling image "ambikanair/armada-storage-secret:latest"
  Normal  Pulled          8s    kubelet            Successfully pulled image "ambikanair/armada-storage-secret:latest" in 992.057015ms
➜  demo
➜  demo
➜  demo oc get pods -n kube-system | grep block
ibm-vpc-block-csi-controller-0          7/7     Running   0          25s
ibm-vpc-block-csi-node-2xcft            4/4     Running   0          26s
ibm-vpc-block-csi-node-ndlrz            4/4     Running   0          26s
ibm-vpc-block-csi-node-pnpsb            4/4     Running   0          26s
➜  demo oc get pvc
NAME           STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS              AGE
myvirtualpvc   Bound    pvc-ce66c3b9-4a45-46fd-9bea-28cf54a8bf2f   20Gi       RWX            ibmc-s3fs-cold-regional   86m
➜  demo oc create -f pvc.yaml
persistentvolumeclaim/csi-block-pvc-custom-one created
➜  demo oc get pvc
NAME                       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                AGE
csi-block-pvc-custom-one   Bound    pvc-19376e0e-c123-4ba1-9530-24eddb8b1cd6   10Gi       RWO            ibmc-vpc-block-5iops-tier   21s
myvirtualpvc               Bound    pvc-ce66c3b9-4a45-46fd-9bea-28cf54a8bf2f   20Gi       RWX            ibmc-s3fs-cold-regional     86m
➜  demo oc create -f pod.yaml
Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "container-name" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "container-name" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "container-name" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "container-name" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
deployment.apps/testcustom created
➜  demo oc get pods
NAME                         READY   STATUS    RESTARTS   AGE
pod-devtest-two              1/1     Running   0          88m
testcustom-cfd587b66-vls4z   1/1     Running   0          112s
➜  demo oc create -f volumeSnapshot.yaml
volumesnapshot.snapshot.storage.k8s.io/snapshot-csi-block-6 created
➜  demo oc get volumesnapshots
NAME                   READYTOUSE   SOURCEPVC                  SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS            SNAPSHOTCONTENT                                    CREATIONTIME   AGE
snapshot-csi-block-6   false        csi-block-pvc-custom-one                           1Gi           ibmc-vpcblock-snapshot   snapcontent-578e9fd3-cdd4-4d58-9d4b-7bce3337ebe7   6s             8s
➜  demo oc get volumesnapshots
NAME                   READYTOUSE   SOURCEPVC                  SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS            SNAPSHOTCONTENT                                    CREATIONTIME   AGE
snapshot-csi-block-6   false        csi-block-pvc-custom-one                           1Gi           ibmc-vpcblock-snapshot   snapcontent-578e9fd3-cdd4-4d58-9d4b-7bce3337ebe7   16s            18s
➜  demo oc get volumesnapshots
NAME                   READYTOUSE   SOURCEPVC                  SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS            SNAPSHOTCONTENT                                    CREATIONTIME   AGE
snapshot-csi-block-6   true         csi-block-pvc-custom-one                           1Gi           ibmc-vpcblock-snapshot   snapcontent-578e9fd3-cdd4-4d58-9d4b-7bce3337ebe7   26s            28s
➜  demo oc create -f snapvol.yaml
persistentvolumeclaim/restore-pvc1 created
➜  demo oc edit pvc csi-block-pvc-custom-one
persistentvolumeclaim/csi-block-pvc-custom-one edited
➜  demo oc get pvc
NAME                       STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                AGE
csi-block-pvc-custom-one   Bound    pvc-19376e0e-c123-4ba1-9530-24eddb8b1cd6   10Gi       RWO            ibmc-vpc-block-5iops-tier   3m38s
myvirtualpvc               Bound    pvc-ce66c3b9-4a45-46fd-9bea-28cf54a8bf2f   20Gi       RWX            ibmc-s3fs-cold-regional     90m
restore-pvc1               Bound    pvc-6d0ade67-d414-4023-817d-c4859155ac0b   100Gi      RWO            ibmc-vpc-block-5iops-tier   24s
➜  demo oc create -f podt
error: the path "podt" does not exist
➜  demo oc create -f podtwo.yaml
Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "container-name" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "container-name" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "container-name" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "container-name" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
deployment.apps/podtwo created
➜  demo oc get pods
NAME                         READY   STATUS              RESTARTS   AGE
pod-devtest-two              1/1     Running             0          89m
podtwo-59f696d697-wwc74      0/1     ContainerCreating   0          11s
testcustom-cfd587b66-vls4z   1/1     Running             0          3m34s
➜  demo oc get pods
NAME                         READY   STATUS              RESTARTS   AGE
pod-devtest-two              1/1     Running             0          89m
podtwo-59f696d697-wwc74      0/1     ContainerCreating   0          15s
testcustom-cfd587b66-vls4z   1/1     Running             0          3m38s
➜  demo oc get pods
NAME                         READY   STATUS              RESTARTS   AGE
pod-devtest-two              1/1     Running             0          89m
podtwo-59f696d697-wwc74      0/1     ContainerCreating   0          18s
testcustom-cfd587b66-vls4z   1/1     Running             0          3m41s
➜  demo

➜  demo oc get pods
NAME                         READY   STATUS    RESTARTS   AGE
pod-devtest-two              1/1     Running   0          93m
podtwo-59f696d697-wwc74      1/1     Running   0          3m53s
testcustom-cfd587b66-vls4z   1/1     Running   0          7m16s
➜  demo oc delete -f pod.yaml
deployment.apps "testcustom" deleted
➜  demo oc delete -f podtwo.yaml
deployment.apps "podtwo" deleted
➜  demo oc delete -f pvc.yaml
persistentvolumeclaim "csi-block-pvc-custom-one" deleted
➜  demo oc delete -f snapvol.yaml
persistentvolumeclaim "restore-pvc1" deleted
➜  demo oc delete -f volumeSnapshot.yaml
volumesnapshot.snapshot.storage.k8s.io "snapshot-csi-block-6" deleted
➜  demo oc create -f pvc.yaml
persistentvolumeclaim/csi-block-pvc-custom-one created
➜  demo oc create -f pod.yaml
Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "container-name" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "container-name" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "container-name" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "container-name" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
deployment.apps/testcustom created
➜  demo oc get pods
NAME                         READY   STATUS    RESTARTS   AGE
pod-devtest-two              1/1     Running   0          96m
testcustom-cfd587b66-6c44t   1/1     Running   0          38s
➜  demo oc exec -it testcustom-cfd587b66-6c44t   /bin/bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
root@testcustom-cfd587b66-6c44t:/# cd /m
bash: cd: /m: No such file or directory
root@testcustom-cfd587b66-6c44t:/# cd /myvolumepath/
root@testcustom-cfd587b66-6c44t:/myvolumepath# echo "new" > hi.txt
root@testcustom-cfd587b66-6c44t:/myvolumepath# exit
exit
➜  demo oc create -f volumeSnapshot.yaml
volumesnapshot.snapshot.storage.k8s.io/snapshot-csi-block-6 created
➜  demo oc create -f snapvol.yaml
persistentvolumeclaim/restore-pvc1 created
➜  demo oc create -f podtwo.yaml
Warning: would violate PodSecurity "restricted:latest": allowPrivilegeEscalation != false (container "container-name" must set securityContext.allowPrivilegeEscalation=false), unrestricted capabilities (container "container-name" must set securityContext.capabilities.drop=["ALL"]), runAsNonRoot != true (pod or container "container-name" must set securityContext.runAsNonRoot=true), seccompProfile (pod or container "container-name" must set securityContext.seccompProfile.type to "RuntimeDefault" or "Localhost")
deployment.apps/podtwo created
➜  demo oc get pods
oc exec -it NAME                         READY   STATUS    RESTARTS   AGE
pod-devtest-two              1/1     Running   0          102m
podtwo-59f696d697-kxt5t      1/1     Running   0          2m27s
testcustom-cfd587b66-6c44t   1/1     Running   0          7m16s
➜  demo oc exec -it podtwo-59f696d697-kxt5t /bin/bash
kubectl exec [POD] [COMMAND] is DEPRECATED and will be removed in a future version. Use kubectl exec [POD] -- [COMMAND] instead.
root@podtwo-59f696d697-kxt5t:/# ls /myvolumepath/
hi.txt	lost+found
root@podtwo-59f696d697-kxt5t:/# exit
exit
➜  demo

E2E Test: https://ibm-argonauts.slack.com/archives/CLMDLHW13/p1669111541956899


Issue while executing multiple test data via test runner file with more than two threads

We have four feature files which contains 31 scenarios with 60 test data and  some scenarios has more than three test data. We are executing all four feature files in test runner like ( String CucumberTags = "@feature1,@feature2,@feature3,@feature4";) with more than two threads ( .parallel(3);). Sometimes tests are getting passed, sometimes two or three tests are getting failed. As per our observation, only the scenarios having more than three test data/Examples are getting failed.
Also, tests are getting passed when we are executing through feature files. Please check below examples
Examples:
| Data 1 |
| Data 2 |
| Data 3 |
| Data 4 |
| Data 5 |
| Data 6 |
Is their any specific reason for failed scenarios?
Any solution to this would be highly appreciated.

most likely an issue with your code not being multi-thread ready. follow this process to reopen: https://github.com/karatelabs/karate/wiki/How-to-Submit-an-Issue
also try stack overflow: https://stackoverflow.com/search?q=[karate]+parallel+java


feat: add support for milestone, assignees and requested reviewers

@korthout This patch intends to add three new config options:

copy_milestone
Copies the milestone from the original PR to all its backport PRs.

copy_requested_reviewers
Assigns the same requested reviewers to the backport PRs as were on the original PR.

copy_assignees
Assigns the same individuals to the backport PRs as were assigned to the original PR.

All of these options are disabled by default.
Addresses: https://github.com/korthout/backport-action/issues/2

Wow 😲 thanks for this awesome contribution. I'll give a proper review for this in the coming days, but it looks super useful!

Thanks for the quick response! Lgtm


when mic on the game audio doesn't mirror

when i type "scrcpy --audio-source=playback --audio-dup" as u said i get this :
ERROR: Unsupported audio source: playback (expected output or mic)

Because you are using an old version.

im playing on android 14 and the latest version of scrcpy ? provide a link to the latest version of scrcpy so i dont be wrong

Please post the full console output.

ERROR: Unsupported audio source: playback (expected output or mic)

The FULL console output (with the command you executed, the scrcpy version, the device, etc).

poco x6 pro , android 14

You're using version 2.3.1, the latest is 2.6.1.
https://github.com/Genymobile/scrcpy#get-the-app

okay now the game audio get mirrored but my friends voices doesn't get mirrored (all when my mic is on)


[Backend] Fix errors and Remove unused methods

Fix error at EventService and SeatService
Remove "/manager" mapping methods

If you mention specific class, method, or smth, please write what I wrote(compare with before-version).


Accessing Azure Function on Linux via FTP

It is possible to retrieve FTP credentials for an Azure Function (based on Python in that case) running on Linux. However, when I connect via FTP, the wwwroot folder is empty. There is also a LogFiles folder which is empty as well.
Is this intended? Is it a bug? Is FTP access supported for Azure Functions on Linux? If no, what is the supported way to get or view files, my Azure Function is creating?

FTP credential is available thru Portal or Azure Resource Manager CLI tool.  If this is Consumption Linux Function, you are likely using run-from-package/zip.   In that case, the content is provided thru Zip file and FTP's wwwroot will not have any content.
@balag0 to help clarify.

Thanks for the response @suwatch, I deploy the Function App via the VS Code Azure Function extension. The function runs periodically and writes content to a file. I'd like to get access to that file. I know, there are workarounds like writing those files to external storages but I thought there must be an easier way to get the file content directly on the function host.

Please confirm if this is a linux consumption.   If so, I am afraid you can only push log to storage.  @balag0  is there another way to get log?

Yes, it uses a Linux consumption plan.

Currently on Linux consumption we do not have a shared persistent drive between kudu and the main site.
So like Suwat mentioned writing to storage is the only option for now. We adding a feature make reading/writing to a persistent store easily. We mount a storage account as a fileshare inside the container which the functions code can access using regular file system apis.
Is this something you would be interested in?  This should be available sometime next week.
cc @anirudhgarg

From a user's perspective it would be great to have more control over the Linux Function App. Because right now, I can't SSH to the host, I can't use FTP to see the files, there is no Log Streaming. I don't really know if my app on Azure is doing what it should do (without using external tools like Application Insights), it feels like a black box.
However, for my specific use case, a file share would make life already a bit easier.

Agreed on all the points. Most of these are already in the backlog but no ETA at this time.
Regarding the file share mounting, will provide a link to a wiki page with the instructions early next week when we are closer to deployment. Thanks for the feedback.

Any progress on any of this?

Sorry forgot to update here. Yes, we added support to mount file shares for Linux.
Let us know if you have any questions.
https://docs.microsoft.com/en-us/azure/azure-functions/storage-considerations#mount-file-shares-linux

Hi
If the problem persists and is related to running it on Azure App Service, please open a support incident in Azure:
https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request
This way we can better track and assist you on this case
Thanks,
Joaquin Vano
Azure App Service


Shared Public Stakeholder Pool

Shared pool of stakeholders that can be accessed and used by any scenario

Whoever is working on the database will need to oversee these stakeholders being added to the database
On the frontend side of things, all that would need to be done is give the ability to editors to access this pool of stakeholders and potentially to allow editor users to add new stakeholders to this shared pool

BACKLOGGED: Ran out of time to implement; needed to focus on integrating with the backend team to set up new endpoints that worked with the new schema before deploying changes to the server.

This is a quality of life issue. However, the customers have expressed a keen interest in making this stakeholder pool a reality.


Memory machine: Don't use selectors to distinguish operations

Pulled out of #1129.
This PR changes how we implement the memory machine, in a way that's closer to the PIL we'll compile to once we've extracted the memory machine as a separate ASM machine in the standard library (#1129).
Previously, constraints looked like this:
    instr mload -> X { { ADDR, STEP, X } is m_is_read { m_addr, m_step, m_value } }
    instr mstore X { { ADDR, STEP, X } is m_is_write { m_addr, m_step, m_value } }

Now, it looks like this:
    instr mload -> X { { 0, ADDR, STEP, X } is m_selector1 { m_is_write, m_addr, m_step, m_value } }
    instr mstore X { { 1, ADDR, STEP, X } is m_selector2 { m_is_write, m_addr, m_step, m_value } }

The selector no longer serves the role of "communicating" which operation should be performed. This makes it similar to how we connect machines via lookups, and it is also how Polygon does it.
This generalizes to more memory operations as follows:
    let operation_id = m_is_write + 2 * m_is_bootloader_write;
    instr mload -> X { { 0, ADDR, STEP, X } is m_selector1 { operation_id, m_addr, m_step, m_value } }
    instr mstore X { { 1, ADDR, STEP, X } is m_selector2 { operation_id, m_addr, m_step, m_value } }
    instr mstore_bootloader X { { 2, ADDR, STEP, X } is m_selector3 { operation_id, m_addr, m_step, m_value } }

While this adds more witness columns for now (one per selector, but also removes m_is_read), in the future this could compile to a single permutation with a single selector, like so:
    (main.instr_mload + main.instr_mstore + main.instr_mstore_bootloader) {
        main.instr_mstore + 2 * main.instr_mstore_bootloader, main.ADDR, main.STEP, main.X
     } is main.m_selector {
        (main.m_is_write + (2 * main.m_is_bootloader_write)), main.m_addr, main.m_step, main.m_value
     };

Which should actually be more efficient than the previous approach! (same amount of witness columns, but only one permutation)
I changed witgen accordingly; it does not work anymore for machines that constrained the "old" way.

I think we should come up with a new name that is not "selector". It's too easy to confuse it with the selector of a lookup.

I think we should come up with a new name that is not "selector". It's too easy to confuse it with the selector of a lookup.

Yes, and it's doing the same in both cases, no? Why would it be called differently if the selected multiset is used in a permutation?


Nikost/rosetta budget

Description
/construction/preprocess:

Request: May or may not have metadata field and metadata may or may not have budget field.
Response: May or may not have options field and options may or may not have budget field.

/construction/metadata:

Request: May or may not have options field and options may or may not have budget field
Response: Always has metadata field and metadata field always has budget field. If Request above included budget, this is returned. If not, computation_cost + storage_cost is used.

Test Plan
Added /tests/gas_budget_tests.rs

Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

@patrickkuo note commit Remove unused InternalOperationRequest enum.
My understanding is that this is not needed.


Are there any negative impact from CVE-2020-15522? Thank you!

I found gradle of IntelliJ IDEA's plugin have used Bouncy Castle BC Java,
Is there any negative impac from CVE-2020-15522?

I'm not familiar with what the plugin does but it is unlikely. To start with the plugin would have to be making use of long-term EC private keys. They'd have to be using 1.65 or earlier (we're at 1.69 now). If they were using BC prior to 1.66, they'd then have to also be using deterministic EC DSA multiple times with the same key (which would also be unusual). And then the attacker would need to be able to measure the differences in signature generation times, which if you are using this in an IDE I am guessing you might notice the interference.

Inactive


Feature Request: Enhance Sampling Mechanism in presidio-structured to Exclude Null Values

The current implementation of presidio-structured samples a fixed number of rows at random to limit computation. However, this approach does not account for null values within the sampled rows. This can lead to a scenario where the sampled data is not representative due to a high volume of null values, thereby reducing the effectiveness of sensitive data identification.
I propose an enhancement to the sampling mechanism where the system iterates through each column individually to perform the sampling. This iteration would ensure that the sampled rows for each column are devoid of null values, thus maintaining the representativeness and integrity of the sample. Such a method would improve the accuracy of sensitive data detection by ensuring that the analysis is performed on meaningful data rather than null or empty values.
As an alternative, a pre-sampling data cleaning step could be introduced, where rows with a high volume of null values are filtered out before the sampling process begins. However, this might lead to the exclusion of potentially relevant data and increase preprocessing overhead. Another approach could involve a more complex sampling algorithm that weighs the presence of non-null values across different columns, but this could significantly increase computational complexity and processing time.

Hi @ebotiab,
as the user is the one who is passing the data frame, can't this be done a priori? Moreover, one can sample the data frame using the logic of their choice, perform the analysis of which columns are sensitive, and then apply this on the full data.
Having said that, if you have a specific idea of a pre-sampling step which could be extended to support arbitrary logic, that would be a great addition to the tool.