How to do partial deserialization

Hey, I'm struggling with deserialization.
I'm making a API with Axum that, upon request, can return records from a ScyllaDB based on some criteria and with certain fields. for example I can request records with specific IDs and fields, let's say request to my API would look like
{
  "columns": ["id", "action_ts_utc", "name", "description", "for_distribution"],
  "keys": [
    ["some_uuid_here1"],
    ["some_uuid_here2"],
    ["some_uuid_here3"],
    ["some_uuid_here4"]
  ]
}

And my rust struct look like
#[derive(DeserializeRow)]
pub struct MyTableRow {
    pub id: String,
    pub action_ts_utc: DateTime<Utc>,
    pub joined_ts_utc: DateTime<Utc>,
    pub is_active: bool,
    pub name: String,
    pub description: String,
    pub for_distribution: bool,
    pub type: String,
}

So my select query would be like
SELECT id, action_ts_utc, name, description, for_distribution FROM myks.mytable WHERE id IN ('some_uuid_here1', 'some_uuid_here2', 'some_uuid_here3', 'some_uuid_here4');

And i will get an error, something like
TypeCheckError: Failed to type check the Rust type myapi::api::handlers::tables::mytable::schema::MyTableRow against CQL column types [Text, Boolean, Uuid, Int, Timestamp] : wrong column count: the statement operates on 5 columns, but the given rust types contains 1%

Types can be different, it's just an example

I understand error, which says that columns I selected doesn't match with struct, and something like following not working too.
#[scylla(flavor = "enforce_order", skip_name_checks)]

Making struct fields optional doesn't working, also as #[scylla(skip)]
So how do i properly handle partial deserialization?

@wprzytula this sounds like we should add #[scylla(allow_missing)] to DeserializeRow too, now it is only available in DeserializeValue.

@wprzytula this sounds like we should add #[scylla(allow_missing)] to DeserializeRow too, now it is only available in DeserializeValue.

Thanks for fastp reply!
#[scylla(allow_missing)] would be perfect!
How often do you release? And how long can I expect to see a new version with this feature?

TypeCheckError: Failed to type check the Rust type myapi::api::handlers::tables::mytable::schema::MyTableRow against CQL column types [Text, Boolean, Uuid, Int, Timestamp] : wrong column count: the statement operates on 5 columns, but the given rust types contains 1%

What I can't understand is that 1%.
This is what should be written:
write!(f, "wrong column count: the statement operates on {cql_cols} columns, but the given rust type contains {rust_cols}")

Looking at your struct, I'd expect 8, not 1%. What does the percent sign even come from???

What I can't understand is that 1%. This is what should be written:
write!(f, "wrong column count: the statement operates on {cql_cols} columns, but the given rust type contains {rust_cols}")
Looking at your struct, I'd expect 8, not 1%. What does the percent sign even come from???

It may be a simple error when copying and pasting the error. Is that really relevant to the issue?

What I can't understand is that 1%. This is what should be written:
write!(f, "wrong column count: the statement operates on {cql_cols} columns, but the given rust type contains {rust_cols}")
Looking at your struct, I'd expect 8, not 1%. What does the percent sign even come from???

It may be a simple error when copying and pasting the error. Is that really relevant to the issue?

It is, because I don't understand what's the underlying problem.
If I understand the case correctly, #[scylla(skip)] applied on non-deserialized fields should be the solution to the described issue. But @73rr0r mentioned that skip is not doing what he wants to achieve - so I'm wondering why.

It may be a simple error when copying and pasting the error. Is that really relevant to the issue?

It is, because I don't understand what's the underlying problem.
If I understand the case correctly, #[scylla(skip)] applied on non-deserialized fields should be the solution to the described issue. But @73rr0r mentioned that skip is not doing what he wants to achieve - so I'm wondering why.

The way I understand it the user want's to dynamically select a subset of column for select statement. So if the API user sends
{
  "columns": ["id", "action_ts_utc", "name", "description", "for_distribution"],
  "keys": [
    ["some_uuid_here1"],
    ["some_uuid_here2"],
    ["some_uuid_here3"],
    ["some_uuid_here4"]
  ]
}

then the query will be
SELECT id, action_ts_utc, name, description, for_distribution FROM myks.mytable WHERE id IN ('some_uuid_here1', 'some_uuid_here2', 'some_uuid_here3', 'some_uuid_here4');

and if the API user sends
{
  "columns": ["id", "joined_ts_utc", "for_distribution", "type"],
  "keys": [
    ["some_uuid_here1"],
    ["some_uuid_here2"],
    ["some_uuid_here3"],
    ["some_uuid_here4"]
  ]
}

then the query will be:
SELECT id, joined_ts_utc, for_distribution, type FROM myks.mytable WHERE id IN ('some_uuid_here1', 'some_uuid_here2', 'some_uuid_here3', 'some_uuid_here4');

Now the problem is how to deserialize it. Creating a separate struct for each subset of column is infeasible. Using something like #[scylla(allow_missing)] seems like a perfect fit here.

The way I understand it the user want's to dynamically select a subset of column for select statement.

Makes sense. Then, implementing allow_missing's support for DeserializeRow would indeed help here.

TypeCheckError: Failed to type check the Rust type myapi::api::handlers::tables::mytable::schema::MyTableRow against CQL column types [Text, Boolean, Uuid, Int, Timestamp] : wrong column count: the statement operates on 5 columns, but the given rust types contains 1%

What I can't understand is that 1%. This is what should be written:
write!(f, "wrong column count: the statement operates on {cql_cols} columns, but the given rust type contains {rust_cols}")
Looking at your struct, I'd expect 8, not 1%. What does the percent sign even come from???

Yeah, look like my terminal displays % or something like that somehow. In my first message i slightly renamed columns and struct itself just for simplicity, here is a real column names. For privacy purposes I'am not gonna share with you all of my real code, I'll share only specific part.
Here is a real struct:
#[derive(DeserializeRow, Debug)]
#[scylla(flavor = "enforce_order", skip_name_checks)] // https://docs.rs/scylla/latest/scylla/derive.DeserializeRow.html#struct-attributes
pub struct VideoMetaRow {
    pub video_id: Uuid,
    #[scylla(skip)]
    pub channel_id: Option<String>,
    #[scylla(skip)]
    pub origin_type: Option<String>,
    #[scylla(skip)]
    pub created_ts_utc: Option<DateTime<Utc>>,
    #[scylla(skip)]
    pub tv_id: Option<String>,
    #[scylla(skip)]
    pub season: Option<i32>,
    #[scylla(skip)]
    pub episode: Option<i32>,
    #[scylla(skip)]
    pub category_id: Option<i32>,
    #[scylla(skip)]
    pub title: Option<String>,
    #[scylla(skip)]
    pub publication_ts_utc: Option<DateTime<Utc>>,
    #[scylla(skip)]
    pub is_active: Option<bool>,
    #[scylla(skip)]
    pub is_adult: Option<bool>,
    #[scylla(skip)]
    pub duration_sec: Option<i32>,
    #[scylla(skip)]
    pub has_high_quality: Option<bool>,
    #[scylla(skip)]
    pub has_preview: Option<bool>,
}

Here is a two requests to my API, first is returning correct result and second is not:
curl -X 'POST' \
  'http://<IP_ADDRESS>:8000/feature_set/video_meta' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "features": ["video_id"],
    "keys": [["k1"], ["k2"], ["k3"], ["k4"]]
  }'

curl -X 'POST' \
  'http://<IP_ADDRESS>:8000/feature_set/video_meta' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
    "features": ["video_id", "channel_id"],
    "keys": [["k1"], ["k2"], ["k3"], ["k4"]]
  }'

And the SQL statements which is generated for the first and second requests:
SELECT video_id FROM video_meta WHERE video_id IN (?);

SELECT video_id, channel_id FROM video_meta WHERE video_id IN (?);

And my responses from API:
[["k1"],["k2"]]%

Repository error: Query error: TypeCheckError: Failed to type check the Rust type fsrs_api::api::handlers::feature_set::video_meta::schema::VideoMetaRow against CQL column types [Uuid, Int] : wrong column count: the statement operates on 2 columns, but the given rust types contains 1%

As you can see % is only in my logs in terminal. About meaning of 1, I don't see any patterns for e.g. increasing the number of columns.
Also i have to mention that I'm using CachingSession with prepared statements and session.execute_iter(query, values).await?.rows_stream::<T>()?
I tried to:

Marking fields as Optional.
Using #[scylla(flavor = "enforce_order", skip_name_checks)].
Using #[scylla(skip)] with #[scylla(flavor = "enforce_order", skip_name_checks)].
Everything together.

And nothing helped to me.
Then i read source code and realized that there is not implementation to allow select not all fields from ScyllaDB and then use new deserialization API. With old API that was possible, i guess with FromRow, but I am not sure, because I did not use old deserialization API.
Also, found no info in docs about macro attributes like #[scylla(skip)]. I don't rule out the possibility that I might be blind ;) But would be good to add some docs about deserialization aspects.
My service is a simple Axum application.
You can think about it as a layer between ScyllaDB and my other microservices. It maps incoming request into SQL statement and then returns deserialized result in a response as only values, a.k.a records, e.g. [ ["k1", 123], ["k2", 456] ] to reduce size of response.
Of course my code can be not the best example of Rust programming, but still i think ScyllaDB driver should give an opportunity of partial deserialization, maybe marking fields as Optional or with #[scylla(allow_missing)] would be a good approach.
As i said I am not an Rust expert, but in other languages i know, this feature is available.
Hope now i provided enough context to you. If any other questions, feel free to ask.

Also, found no info in docs about macro attributes like #[scylla(skip)]. I don't rule out the possibility that I might be blind ;) But would be good to add some docs about deserialization aspects.

The attributes are described here: https://docs.rs/scylla/latest/scylla/derive.DeserializeValue.html

Also, found no info in docs about macro attributes like #[scylla(skip)]. I don't rule out the possibility that I might be blind ;) But would be good to add some docs about deserialization aspects.

The attributes are described here: https://docs.rs/scylla/latest/scylla/derive.DeserializeValue.html, https://docs.rs/scylla/latest/scylla/derive.DeserializeRow.html

Yep, thats right, I found them exactly in crate docs, thats not very obvious, because the first link in Google leads to website i mentioned earlier ;). For me thats fine, but for simple users i guess thats not obvious to check macro attributes somewhere in crate docs, it's like finding Rust docstrings in source code at GitHub repo I think, only experienced users do that. But that only my opinion, not the real problem.

i guess thats not obvious to check macro attributes somewhere in crate docs, it's like finding Rust docstrings in source code at GitHub repo I think, only experienced users do that.

Hmm, that's surprising. For us it's been intuitive that crate docs are a basic source of knowledge about a Rust crate.

@wprzytula this sounds like we should add #[scylla(allow_missing)] to DeserializeRow too, now it is only available in DeserializeValue.

Thanks for fast reply! #[scylla(allow_missing)] would be perfect!
How often do you release? And how long can I expect to see a new version with this feature?

We are currently focusing our efforts on stabilizing the library and releasing 1.0 version.
#[scylla(allow_missing)] for DeserializeRow is an addition that is backwards-compatible, se we won't be able to prioritize it before releasing 1.0. You are welcome to send a PR with this change of course.

i guess thats not obvious to check macro attributes somewhere in crate docs, it's like finding Rust docstrings in source code at GitHub repo I think, only experienced users do that.

Hmm, that's surprising. For us it's been intuitive that crate docs are a basic source of knowledge about a Rust crate.

Yeah, it's obvious for me too, but for example I have some colleagues for whom this was not obvious, probably because they are like jun-middle level. So i guess people who are going deep dive into the Rust not gonna realize immediately what he has to look at crate docs instead of official db docs.
It's looks like a holywar about where should be the source of truth for libs and services, in some Confluence, some local wiki or something like that or in the code and docstrings itself.
Personally i prefer it in both places, but with links to source code docs in Confluence for example.

Overall if i will have some time in non-working hours, maybe I will try to contribute, but I am not 100% sure about it


support default value (IR only)

Add support for default value.
For now, default value lives only in IR.
It is considered helpful for a GUI.

Is this ready for review?

It is good enough for simply showing default value (as an expression when necessary).
More functionalities can be left for future.

Default value validation is added.
It is probably not perfect but it should cover most cases.

It serves as a hint only

nice work! thanks!


Disappearing auction

Please make sure your issue complies with these guidelines:

[ ] Server Software must be the official PMMP w/o vanilla patching plugins (i.e. TeaSpoon)

[ ] Issue must have not been reported previously

[ ] Make sure you are on the latest version of PMMP & PiggyAuctions

[ ] Have a detailed title (i.e "Auctioned items remain in inventory")

Issue Description

Expected result: What were you expecting to happen? Item remain
Actual result: What actually happened? Begone item

Steps to Reproduce the Issue
1)create auction
2)put any item
3)edit the minimum bid amount after putting up the item
4)submit with any numeric value
5)reedit the bid (gold ingot)
6)place any amount on the bid
7)close the UI instead of pressing submit
8)item gone
OS and Versions

PocketMine-MP: Latest
PiggyAuctions: Latest
PHP:
Server OS:

Extra Information

Please make sure your issue complies with these guidelines:

[ ]  Server Software must be the official PMMP w/o vanilla patching plugins (i.e. TeaSpoon)

[ ]  Issue must have not been reported previously

[ ]  Make sure you are on the latest version of PMMP & PiggyAuctions

[ ]  Have a detailed title (i.e "Auctioned items remain in inventory")

Issue Description

Expected result: What were you expecting to happen? Item remain
Actual result: What actually happened? Begone item

Steps to Reproduce the Issue
1)create auction
2)put any item
3)edit the minimum bid amount after putting up the item
4)submit with any numeric value
5)reedit the bid (gold ingot)
6)place any amount on the bid
7)close the UI instead of pressing submit
8)item gone
OS and Versions

PocketMine-MP: Latest
PiggyAuctions: Latest
PHP:
Server OS:

Extra Information

Actually by simply closing the UI instead of hitting submit will still take away the item


Error while using GPU

I have a NVIDIA 4090 and an Intel GPU on my machine. I want to load model to my 4090. However, it only checked my intel gpu and said it's now support.
How to use my NVIDIA GPU not the Intel One?
Thank you.

I try to load the library manually, but it said The specified module could not be found. (sd-abi_cuda12.dll)
When I try to load sd-abi_avx2.dll, It works.

@Mars160  Can you run the following command in powershell
Get-WmiObject Win32_VideoController | Format-List Name,AdapterCompatibility,AdapterRAM

Thanks for your reply.
And here is the output
Name                 : Virtual Desktop Monitor
AdapterCompatibility : Virtual Desktop, Inc.
AdapterRAM           :

Name                 : NVIDIA GeForce RTX 4090
AdapterCompatibility : NVIDIA
AdapterRAM           :<PHONE_NUMBER>

Name                 : Virtual Display
AdapterCompatibility : Xiaomi
AdapterRAM           :

Name                 : Intel(R) UHD Graphics 770
AdapterCompatibility : Intel Corporation
AdapterRAM           :<PHONE_NUMBER>

Thanks for your hard work! The GPU selection issue was fixed!
However, there is another issue. I can load 'sd-abi_cuda12.dll'
2024/01/10 13:55:31 get gpu info: NVIDIA GeForce RTX 4090
2024/01/10 13:55:31 Use GPU CUDA instead.
2024/01/10 13:55:31 If you want to try offload your model to the GPU. Please confirm the size of your GPU memory to prevent memory overflow.
The specified module could not be found.

And I found we should blame it on golang's package. I tried
package main

import "syscall"

func main() {
	lib, err := syscall.LoadLibrary("sd-abi_cuda12.dll")
	if err != nil {
		panic(err)
	}
	defer syscall.FreeLibrary(lib)
}

I got
panic: The specified module could not be found.

goroutine 1 [running]:
main.main()
        C:/other/AI/sd-go/test.go:8 +0x79
exit status 2

When I change the library from sd-abi_cuda12.dll to sd-abi_avx2.dll, It loaded it successfully.
I'm not so familiar to stable diffusion library. Is there a way to fix this?
Thank you!

@Mars160  Have you installed cuda?

Thank you! You solved my problem perfectly!


fix(ngAnimate): run structural animations with cancelled out class ch…

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bugfix
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)

Other information:
…anges
When multiple animations on the same element are queued before a $digest passes,
the animator tries to create as few actual animations as possible by joining / canceling
redundant animations. Class-based animations for example are cancelled when the classes that
are added and removed are the same, and the result is no class-change. This however must only
happen if there's no structural animation currently queued.
Fixes #14249

@gkalpak can you take another look at this?

Other than the minor comments (whitespaces and unused var?), it LGTM :+1:

Landed as  cc1de81f5e2867e9ee6db9ecb2a4fd9d19fa2588 and c7813e9ebf793fe89380dcad54e8e002fafdd985


Drop off

https://www.linkedin.com/safety/go?messageThreadUrn=urn%3Ali%3AmessageThreadUrn%3A6&url=https%3A%2F%2Fwww.bandlab.com%2Fjoin%2Frsy4egr&trk=flagship-messaging-android

@saket ![Screenshot_2022-09-22-16-31-58-952.jpg](https://user-images.githubusercontent.com/96916434/191857009-ca16f1cd-a5a4-479f- - - [ ] -b89a-d61cb95ced7b.jpg)


[Impeller] Devise DisplayList ops that express more fine grained rendering intent.

Today, display-list ops are fairly high level and there is a 1-1 relationship between the operations that can be performed on a display list builder and the opcodes supported by display lists.
Having more fine grained "mid-level" ops might make it optimizations easier to express.

Filing a followup based on the discussion in the Impeller Weekly. cc @flar @jonahwilliams
@gaaclarke @bdero

I thought we said we didn't want to make display list more expressive, but instead lift the optimizations from skia into the display list interpreter (in this case the dispatcher).

Oh. I totally could have misinterpreted what was being said as I was taking notes!
My take was that we'd keep the builder API the same (with high level intent) but introduce more "mid-level" ops in the display list itself. And lift optimization into DL.
But yeah, Jonah did mention he is going to write a doc for this. So maybe we can take the discussion there.

@chinmaygarde that is correct. I'm writing up a doc for this now.

I think @gaaclarke and @chinmaygarde are saying the same thing. The recording API doesn't change, while the dispatching API does.

We'll see in the design doc but I think chinmay and I are saying different things, imagine the following machine code for int x = 3 * 5;:
ld r0, 5
add r0, r0, 5
add r0, r0, 5

Do we change the compiler and the processor so it could write out:
mul r0, 3, 5

Or do we make the processor smart enough to interpret those 3 commands as 1 multiplication?
Making display list more expressive is the first case, lifting the optimizations to the dispatcher is the second case.

I thought we said we didn't want to make display list more expressive, but instead lift the optimizations from skia into the display list interpreter (in this case the dispatcher).

Terminology is making this confusing.
We have DlCanvas which is the language you use to talk to a DlBuilder to fill it with rendering stuff.
We have DlOpReceiver which is the language you use to receive the data from a DisplayList.
We also have DlOps which are the recording format inside the DL buffer and map closely to DlOpReciever.
We talked about keeping DlCanvas, or the input side to DlBuilder, high level but make DlOpReceiver, or the output side of DlBuilder, lower level or more fine grained.
The title of the issue says "DisplayList ops" which is sort-of the output side, which is the part we want to make more fine-grained.


Change install to add in Readme

change "yarn install next-translate" to "yarn add next-translate"

Thank you so much! I'm going to change it now!


FIX: Failing nightly CI tests due to IA3 config

Same idea as in PR as #1094, but for yet more ill-configured IA³ configs. The tests are now failing because we do stricter checks on incorrect IA³ configs.
These are the failing tests:
https://github.com/huggingface/peft/actions/runs/6806502406/job/18507828825
https://github.com/huggingface/peft/actions/runs/6806502406/job/18507829021
With this fix, they now pass locally.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Code review for "isolate side components in side.n part of object"

This issue is to set up a bit of navigation for the code review of #313, since it contains a lot of file changes and a number of different concepts.
Changes are related to these categories:

clean up and re-structuring files (e.g., moving side functions into utils-side.R)
documentation (e.g., in #312 )
Most of the rest of the changes focus on #290 , and the various user-facing changes required to support that.
speed of the iterative building of gsplot. I created a few short-circuit changes to the summarize_x functions no longer repeat across the entire object every time something changes. This also means that the high-level functions in calc_views aren't as high level anymore (note set_view_lim and set_view_log are no long in that function).

I am going to set up some explanations of these things below to steer our discussion.

For 1 and 2 ☝  I just moved some things around and added a bunch of roxy docs on the functions.
for 3, here is the new experience:
gs <- gsplot() %>%
    points(1, 2, legend.name="Cool points", xlim=c(0,NA)) %>%
    lines(x=1:5, y=1:5, legend.name="Cool lines", ylab='taco night') %>%
    legend(location="topleft")

names(gs)
[1] "view.1.2" "side.1"   "side.2"   "par"      "legend"

names(gs$view.1.2$window)
[1] "side"       "axes"       "ann"        "frame.plot" "ylab"       "xlab"
#although I expect to have `lab` moved into the sides too, if that makes sense to others

the usr.lim is where we can tell if a user has specified the limit (see above, it was set with c(0, NA), so it is TRUE FALSE
gs$side.1
$lim
[1] 0 5

$log
[1] FALSE

$label
[1] NA

$usr.lim
[1]  TRUE FALSE

limits now use the sides instead of the window
xlim(gs)
$side.1
[1] 0 5

xlim(gs, side=1)
[1] 0 5

ylim(gs)
$side.2
[1] 1 5

within print, the way we use the limits and logs is a bit different:
# new way:
plot.window(xlim = xlim(views, x.side), ylim = ylim(views, y.side), log = as.log(views, view.name))

# old way:
plot.window(xlim = window$xlim, ylim = window$ylim, log = view.info$log[i==view.info$index])

# note that the new way should change too, so that we don't have overplotting of the sides in the future

the view_info is a bit different too:
view_info(gs)
         x y log index     name x.side.defined.by.user y.side.defined.by.user
view.1.2 1 2         1 view.1.2                  FALSE                  FALSE

# vs old way
x y  log index x.side.defined.by.user y.side.defined.by.user
1 1 2 NULL     1                  FALSE                  FALSE

I added a bunch of little helper functions, like
gsplot:::as.side_name(1)
[1] "side.1"

gsplot:::as.side("side.1")
[1] 1

gsplot:::as.view_name(1)
[1] "view.1.2"
gsplot:::as.view_name(2)
[1] "view.1.2"
gsplot:::as.view_name(c(1,2))
[1] "view.1.2"
gsplot:::as.x_side_name("view.1.2")
[1] "side.1"

logged now works for the sides instead of relying on being right for only one view when they share sides:
usrDef <- gsplot(mar=c(4,4,4,4), xaxs='r', yaxs='r') %>%
     points(x=1, y=2, side=c(3,2), legend.name="Points 1", cex=3, xlab='cat') %>%
     points(x=3:10,y=4:11, side=c(1,2)) %>%
     lines(1:2,4:5, side=c(3,2), log='xy')

logged(usrDef)
$side.1
[1] FALSE

$side.2
[1] TRUE

$side.3
[1] TRUE

# vs the old way:

logged(usrDef)
$side.3.2
[1] "xy"

$side.1.2
[1] ""

note, the old way is actually wrong here, as it should return "y" for side.1.2, but ***this is an API breaker because the return structure is different.


[FLINK-14421][Table-API]Normalize field definition

What is the purpose of the change
In SqlDateTimeUtils、DateTimeUtils and ApiExpressionUtils,
MILLIS_PER_DAY field is defined as：
public static final long MILLIS_PER_DAY = 86400000;
This pr changes it to 86400000L and to be consistent with other fields
Brief change log
change 86400000 to 86400000L
Verifying this change
This change is a trivial work.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): ( no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
The S3 file system connector: ( no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Thanks for the contribution @wangxlong, btw, please pay more attention on the commit message, you can refer https://flink.apache.org/contributing/code-style-and-quality-pull-requests.html for more details.

Thanks for the contribution @wangxlong, btw, please pay more attention on the commit message, you can refer https://flink.apache.org/contributing/code-style-and-quality-pull-requests.html for more details.

Oh, i am sorry fot that. I will pay more attention on it


Remove pygen dependency

Description
Please describe the change you have made.
Checklist:

[ ] Tests added/updated.
[ ] Documentation updated.
[ ] Changelog updated in CHANGELOG.md.
[ ] Version bumped. If triggering a new release is desired, bump the version number in pyproject.toml per semantic versioning.

Obsolete


Not able to authenticate using project-api

I tried to generate a new API key and provided the same as shown below:
token <- anonymous_login(project_api = "new_API_key")
If I try to access token$idToken, I am getting NULL. Please find the content of token below:
$error
$error$code
[1] 400
$error$message
[1] "ADMIN_ONLY_OPERATION"
$error$errors
$error$errors[[1]]
$error$errors[[1]]$message
[1] "ADMIN_ONLY_OPERATION"
$error$errors[[1]]$domain
[1] "global"
$error$errors[[1]]$reason
[1] "invalid"
Can anyone please help me on this?
Thanks!

You may need to change your authentication rules in your project settings to enable Anonymous login


Fix javadoc for PrepareForTest annotation

From<EMAIL_ADDRESS>on November 10, 2008 17:46:39
Fix javadoc for PrepareForTest and PrepareOnlyThisForTest annotations
Original issue: http://code.google.com/p/powermock/issues/detail?id=70

From<EMAIL_ADDRESS>on November 14, 2008 06:15:00
Status: Fixed


update PPP

Codecov Report

Merging #249 (c3ecc2a) into master (96d9ae1) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #249   +/-   ##
=========================================
  Coverage     72.95%   72.95%
  Complexity      585      585
=========================================
  Files            89       89
  Lines          1749     1749
  Branches        210      210
=========================================
  Hits           1276     1276
  Misses          405      405
  Partials         68       68

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 96d9ae1...c3ecc2a. Read the comment docs.


Terminal options color not respected

Testing #129009
Terminal options screen Recording.zip
Not sure if there are additional steps in the setup.
Version: 1.59.0-insider
Commit: c3b4df8f5d9c14aa4cfddb587231d0d52e72e5a2
Date: 2021-07-27T15:07:54.419Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Linux x64 5.11.22-100.fc32.x86_64

You need to pass in a ThemeColor:
vscode.window.createTerminal({
	name: `Ext Terminal #${NEXT_TERM_ID++}`,
	color: new vscode.ThemeColor('terminal.ansiYellow')
} as any);


[SampleGen] 🚀 Enable Google Cloud client library repo support

🚀 Enable SampleGen functionality for client library repos
» Tracking issue 🐞
Now that gapic-generator supports generating code samples in C#, Go, Java, Node.js, PHP, Python, and Ruby, each of the respective client library repositories should enable support for generated code samples so that autosynth distributes generated samples for publication.

🖋 Sample Authoring [Journey] – (same journey as making library config changes)

googleapis is updated – (with new sample and/or test configs)
autosynth triggers synthtool – (results in new/updated sample/test files being generated)
autosynth creates a Pull Request – (b/c generator output changed including sample/test files)
Pull Request runs sample tests – (requires running $ sample-tester)
That's all!

📝 Two changes are required in client library repos to enable support for generated samples:

Update the CI / test scripts to run sample tests (*.test.yaml) using $sample-tester

On a per-API per-Library basis, each synth.py needs to be updated to generate samples
(intentionally manual process to enable; enabling requires setting include_samples=True)

This issue tracks #1 – Enable CI / test scripts to run sample tests (for each language / API)

Status / Blocking Issues
In Review

[ ] PHP – 🤖 Generated code samples for Natural Language and Speech-to-Text [🐘]
[x] Python – 🤖 Generated code samples for Natural Language and Speech-to-Text [🐍]
[ ] Ruby – 🤖 Generated code samples for Natural Language and Speech-to-Text [💎]

Upcoming (issues not yet filed against library repos)

🐹 Go
🚀 Node.js
☕ Java
#⃣ C# / .NET

(... I'll fill in the above with links as they become available ...)

go/library-samples (internal)

@googleapis/samplegen

Moved to backlog. https://github.com/googleapis/gapic-generator/wiki/feature-backlog


Add several tasks for SEACrowd

Changelog:

Add classification for domain knowledge related (unrelated to NLP task) both for single-label and multi-label, relates to https://github.com/SEACrowd/seacrowd-datahub/pull/259.
Add Abusive Language Prediction task, relates to https://github.com/SEACrowd/seacrowd-datahub/pull/240.

Whoops, forgot abt that. Thanks for reminding!


[capsule] First eth transaction not completing

Description
Currently there is an issue when building capsule fresh and performing an Ethereum transaction. The first transaction will always fail or take an unusual long time to complete. This causes the FE UI to freeze without ever showing that the transaction has been completed/submitted successfully.
This is further investigated by ops:
https://vegaprotocol.slack.com/archives/CD4AKTFQT/p1670270033616939
In the mean time a workaround was created to perform an eth transaction at the start of the test run with an explicit wait #2229
Once this issue is fixed, the workaround should no longer be needed and can be deleted.

Need support from the capsule guys Joe to check if they have a ticket for this

@jtsang586 to create a ticket for Ops and flag with Gordon so it gets planned in

Ticket created for Ops to investigate here:
https://github.com/vegaprotocol/devops-infra/issues/1773

Capsule ... wont do


If app starts in certain paths redirect to root

This issue requires knowledge of react and react-router.
Thank you for your help :heart:
What is this project?
DAV (Decentralized Autonomous Vehicles) is a new foundation working to build an open-source infrastructure for autonomous vehicles (cars, drones, trucks, robots, and all the service providers around them) to communicate and transact with each other over blockchain.
Missions
The DAV project you are looking at is Missions. Missions is the client facing side of the marketplace connecting DAV users looking to ship packages, with autonomous vehicles such as drones.
How you can help
Missions is a web app built using React and React Router. When a user clicks links in the app the url gets updated. If the user refreshes the page when the url is pointing at certain routes (or enters those urls directly) we do not have all the information needed to display those pages, and would want to redirect the user to the root route instead.
Add code to a central location that will check the current url when the app loads, and if it is /searching push the / url to the history (which will cause it to navigate there). In the future we will have more conditions here which will cause it to navigate. My initial instinct is to do this in the App component (as it has access to the router, and it is the first component to load (after its wrapper: Main)).
To run the project locally, you will need to clone it, run npm run, and then visit http://localhost:3333/. Detailed instructions are below:
Contributing to Missions

[ ] Fork the repository from the Missions GitHub page.
[ ] Clone a copy to your local machine with $ git clone git@github.com:YOUR-GITHUB-USER-NAME/missions.git
[ ] Make sure you have node.js and npm installed on your machine. You can use this guide for help.
[ ] Install all of the project's dependencies with npm. $ cd missions; npm install
[ ] Run gulp watch:js to start a local server and watch your local code for changes. The server will restart automatically every time you change the code.
[ ] Code! code! code!
[ ] Before committing your code, run gulp one last time and make sure no errors (including linting errors) are thrown.
[ ] Once you've made sure all your changes work correctly, and committed all your changes, push your local changes back to github with $ git push -u origin master
[ ] Visit your fork on GitHub.com (https://github.com/YOUR-USER-NAME/missions) and create a pull request for your changes.
[ ] Make sure your pull request describes exactly what you changed and references this issue (include the issue number in the title like this: #26)

can I pick this ? 🙂

This task is open to whoever knows react + react-router, and can send a pull request. 👍

Sorry, I couldn't figure this out. Its open for anyone to pickup. Thanks 🙂

🤔 I'm going to try working on a solution for this one

Hey I owe an update on this one. Working on it has essentially just been going through learning react and react-router docs, making notes and going through working with some examples. At first i just wrote a couple of redirects which was pretty hacky and  not a sustainable solution. I think this issue could actually be solved by using browserhistory with a Switch and passing the previousURL to the next path using nested routes... i'm going to try experimenting with it this week and report back

I figured out a solution and made a pr #12.

Is this still open?

My apologies @ZackTaylor
I completely lost track of this one, and should have helped merge it. My apologies.
This has been fixed already since.
🙇


Az.Network for PrivateLink - Set-AzPrivateEndpointConnection, Dictionary Issue

Set-AzPrivateEndpointConnection -ResourceId  -PrivateLinkServiceConnectionState "Approved"
Set-AzPrivateEndpointConnection: The given key 'Microsoft.Network/privateEndpoints' was not present in the dictionary.
AZ.network version 3.2.0

Please open this issue to PowerShell repo.


Update project URL - [merged]

In GitLab by @kinow on Jun 18, 2024, 22:01
Merges update-url -> master
Closes #111

In GitLab by @kinow on Jun 18, 2024, 22:01
requested review from @LuiggiTenorioK

approved this merge request

In GitLab by @kinow on Jun 19, 2024, 10:10
Thanks Luiggi! Merging...

I just noticed that this branch was never merged. Merging!

In GitLab by @kinow on Jun 18, 2024, 22:04
Commented on paper/paper.bib line 50
Most of the file had spaces, with a few tabs here and there. Normalized to just spaces, and most had 4 spaces, so adjusted so everything has 4 spaces (OCD :laughing: !)

In GitLab by @kinow on Jun 18, 2024, 22:03
added 1 commit
a1b11cdf - GL-111: Update project URL
Compare with previous version

mentioned in commit 4e1074d947fffd676d3ea0a1577f2e772b48ddd1

In GitLab by @kinow on Jun 18, 2024, 22:04
Commented on docs/source/installation/index.rst line 19
Space at the end removed by IDE. Can add it back if you think it's better :thumbsup:

Thanks @kinow!! It looks good. I didn't check this when we updated the repository URL :sweat_smile:
Merge it whenever you want :raised_hands:

In GitLab by @kinow on Jun 18, 2024, 22:02
Sorry, didn't know if there was a milestone to use. Feel free to update issue/MR, or let me know the milestone and I'll do it :thumbsup: Cheers


Added min tokens to project creation.

Add min_tokens field in project creation form
min_tokens field is stored in project task_config
Filter HighlightGroup based on min_tokens

log2.txt


[Bug] Fix dataTables bootstrap js version differ.

FE logs ERROR (nioEventLoopGroup-3-2|84) [StaticResourceAction.executeGet():160] Request with wrong path. url: /static?res=DataTables-1.10.21/js/dataTables.bootstrap.js
because dataTables bootstrap js version differ, The thirdparty/vars.sh is 1.10.23, The WebBaseAction.java is 1.10.21.
We can consider through configuration way to perfect it in the future.

close this pr, and push it to master branch, Thanks!


Transfer Notifications

Adds optional Atom notification upon completion of transfers
I like seeing a notification when transfers are finished, so I added it on the "upload" and "download-selected-local" functions. Off by default so it shouldn't impact existing users unless they turn it on.

I just noticed that upon being disconnected due to inactivity, if I triggered an upload, nothing would happen. I made another modification that reconnects if no connection is present on upload request, then re-requests the upload.

Just pushed another commit. I usually have the FTP tree view hidden. When it connects on upload or download, it un-hides the tree. I set it to re-hide the tree if it was hidden before connect was called.


Update design-specs.md

关联的Issues (Related Issues)

close https://github.com/ipfs-force-community/sophon-docs/issues/10
改动 (Proposed Changes)

附注 (Additional Info)

自查清单 (Checklist)
在你认为本 PR 满足被审阅的标准之前，需要确保 / Before you mark the PR ready for review, please make sure that:

[x] 符合Venus项目管理规范中关于PR的相关标准 / The PR follows the PR standards set out in the Venus project management guidelines
[x] 具有清晰明确的commit message / All commits have a clear commit message.
[x] 包含相关的的测试用例或者不需要新增测试用例 / This PR has tests for new functionality or change in behaviour or not need to add new tests.
[x] 包含相关的的指南以及文档或者不需要新增文档 / This PR has updated usage guidelines and documentation or not need
[x] 通过必要的检查项 / All checks are green

CC @simlecode review req

怪怪。。。 check 挂了。。。 合不进去。。 😂

Codecov Report

Merging #349 (d1f5139) into master (5901fbd) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files

@@           Coverage Diff           @@
##           master     #349   +/-   ##
=======================================
  Coverage   53.87%   53.87%
=======================================
  Files          74       74
  Lines        8070     8070
=======================================
  Hits         4348     4348
  Misses       3372     3372
  Partials      350      350

Flag
Coverage Δ

unittests
53.87% <ø> (ø)

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


Support custom SASL mechanisms

There is some interest in supporting various SASL mechanisms not
currently included in the library:

#2110 (DMS)
#2204 (SSPI)
#2232 (AWS_MSK_IAM)

Adding these mechanisms in the core library may be undesirable due to:

Increased maintenance burden.
Unavailable testing environments.
Vendor specificity.

This PR provides a quick prototype for a pluggable SASL system (and potential alternate route to supporting #2255).
I don't want to be presumptuous about the support for custom SASL extensions on the behalf of the maintainers of kafka-python.
I hope that this quick example can serve as a venue for discussion about the viability of the idea!

Example
To define a custom SASL mechanism a module must implement two methods:

def validate_config(conn):
    # Check configuration values, available libraries, etc.
    assert conn.config['vendor_specific_setting'] is not None, (
        'vendor_specific_setting required when sasl_mechanism=MY_SASL'
    )

def try_authenticate(conn, future):
    # Do authentication routine and return resolved Future with failed
    # or succeeded state.

And then the custom mechanism should be registered before initializing
a KafkaAdminClient, KafkaConsumer, or KafkaProducer:

import kafka.sasl
from kafka import KafkaProducer

import my_sasl

kafka.sasl.register_mechanism('MY_SASL', my_sasl)

producer = KafkaProducer(sasl_mechanism='MY_SASL')

Notes
ABCs
This prototype does not implement an ABC for custom SASL mechanisms.
Using an ABC would reduce a few of the explicit assertions involved with
registering a mechanism and is a viable option. Due to differing feature
sets between py2/py3 this option was not explored, but shouldn't be
difficult.
Private Methods
This prototype relies on some methods that are currently marked as
private in BrokerConnection.

._can_send_recv
._lock
._recv_bytes_blocking
._send_bytes_blocking

A pluggable system would require stable interfaces for these actions.
Alternative Approach
If the module-scoped dict modification in register_mechanism feels too
clunky maybe the addtional mechanisms can be specified via an argument
when initializing one of the Kafka* classes?

This change is

Going to merge https://github.com/wbarnha/kafka-python-ng/pull/146 first then this PR.

Actually, let's pull in the tests and make life easier to manage this PR.

On further though, it would actually be better to pull in changes from #147 into this PR.


fix: horizontal scroll bar on topics in drawer

Pre-Flight checklist

[ ] Screenshots and design review for any changes that affect layout or styling

[ ] Desktop screenshots
[ ] Mobile width screenshots

[ ] Testing

[ ] Code is tested
[ ] Changes have been manually tested

What are the relevant tickets?
Closes https://github.com/mitodl/ocw-hugo-themes/issues/255
What's this PR do?

Hides horizontal scroll on course info for screens where content fits in/is adjusted.
Makes border same for course home page and course info on other pages, to maintain consistency, which got different due to a merged PR.
Adjusts little padding and margins

How should this be manually tested?

Visit any course ( e.g )
Using responsive mode, set the browser width to "Laptop with MDPI screen" ( width: 1280, height: 800 )
Verify that there is no horizontal scroll.

Screenshots (if appropriate)
Before:

After:

@MAbdurrehman12 if this is ready for review, you should add the "Needs Review" label.

@MAbdurrehman12 if this is ready for review, you should add the "Needs Review" label.

Actually, I was a bit concerned about the issue being discussed here, once it's resolved, I guess we are good to proceed!

@alicewriteswrongs are you reviewing this PR?

Sorry I lost track of this after the comments above! I'll review this morning

Sorry I lost track of this after the comments above! I'll review this morning

Looks like there is a conflict, I'll resolve it after standup.

@alicewriteswrongs Ready for review


Qt candidate window: window size is still too small

The Qt candidate window of 2.26.4632 is still too small and all the its contents are not shown. Please see the screen shot attached.
Physical DPI of the display might be related to this problem.
Qt version: 5.15.2
Desktop: Xfce (also confirmed with KDE Plasma)

Hi Fuminobu,
Thank you for the report with the screenshot. It's helpful for us.
The margins of the low are different from our expectations.

Would you share your display settings?
If you keep using the candidate window, is the margin changed to the expected size?

Because I cannot reproduce this issue on my environment (Debian testing, Qt 5.15.2+dfsg-14), I need helps to identify the problem.
Thank you,

Hi, here is additional information

HW: Virt Manager (libvirt graphics + Spice)
OS: openSUSE Tumbleweed
Desktop environment: Xfce

Font DPI: 96
QT_AUTO_SCREEN_SCALE_FACTOR, QT_SCREEN_SCALE_FACTORS not set

Virtual display

I'm not sure if there are some mechanisms to pass host's physical display metrics (using 27 inch 4K and 12 inch Full HD display)

> xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
Virtual-1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 370mm x 267mm
   1457x1055     75.00 +
   5120x2160     50.00
   4096x2160     50.00
   3840x2160     50.00
   1920x1440     60.00
   2560x1080     50.00
   1856x1392     60.00
   1792x1344     60.00
   2048x1152     60.00
   1920x1200     59.88
   1920x1080     60.00    50.00
   1600x1200     60.00
   1680x1050     59.95
   1400x1050     59.98
   1280x1024     60.02
   1440x900      59.89
   1280x960      60.00
   1360x768      60.02
   1280x768      59.87
   1024x768      60.00*
   800x600       60.32
   640x480       60.00    59.94

One interesting fact is that this problem does not reproduce under icewm. So I'm wondering there are some padding from window managers.

I performed the whole refactoring to the Qt candidate window.
It has replaced Mozc's thread and mutex in the implementation with Qt's ones.
This issue doesn't happen my environment.
Would you confirm if the build 4656 works or not?

Unfortunately, 4656 does not resolve this problem.
According to my quick survey writing a simple Qt application, it seems that there is some minimum column-width and thus setColumnWidth() does not always set to the specified width.
One idea to resolve this problem is getting the actual width of column after calling setColumnWidth(). However, I think the minimum width is a bit wide for the shortcut column so I'm wondering if there's a way to adjust the min-width.

The following code seems to reduce the minimum width of colomun.
auto header = candidates_->horizontalHeader();
header->setMinimumSectionSize(1);

Thank you for the investigation.
I am going to make a change to call setMinimumSectionSize.

81108defe472953a7fc8df7444022f21d83e22a6 added a change to call setMinimumSectionSize.
Would you try the build 4660?

I'm glad to hear that the issue is fixed.
The padding in your first comment is wider than our expectation, and the padding in your last comment is our expectation.
We will modify the padding based on the font size, if the current paddings don't work on some environments.
Please feel free to file another issue for this topic as a reminder.
Thank you again for you reports and investigations.


Add possibility to use without StatefulWidget

It would be really nice if it were possible to use a telescope without having to use StatefulWidgets all the time.
This would also allows you to actually stop listening to the widget when it unmounts.
Alternatively do something similar to what provider and riverpod do with a consumer widget.
TelescopeConsumer(
  telescopes: [value1, value2],
  builder: (context) => Text('${value1.value}, ${value2.value}'),
);

Sidenote: please review the notifyAll method of the main telescope. What if the user provides a Function(VoidCallback)? Then any error will just get swallowed. You could try to listen to the right type of error and if that happens you also remove the function from the callback list.

Hi.
Great Idea👍
Are you planning to implement it yourself?
If the answer is yes I will be so happy😀.
If the answer is no let me know. i will plan to implement it myself.
Thanks for your consideration.

I'm probably not going to have the time to implement it right now. Also I have not used the package a lot so it would not be a great idea for me to try and make changes to the code, especially since the main telescope class does not have any tests right now.
Would really love to see this grow into a well-established solution, and would be willing to contribute after exploring the package  a little bit more and using it in a real project.

Ok👍
I actually have some integration tests, check out the example module to explore them.
Thanks for your time. I will plan to get this done✅ in next versions.


EAVH16S23DA6V - ERR: Time out on register ...

Dear all specially developers,
Thank you for this great work and for any help you could provide to me.
I have a Daikin Altherma with internal ( EAVH16S23DA6V) and external unit (EPGA14DAV3).
It is from 2021, so a fairly new machine.
I have followed this instructions using an ESP32 board. As described in instructions I have connected GPIO16 and 17 to X10A-pin2 and pin3 respectively.
Issue:
I am not extracting any LabelDef values at all. I have then use the serial monitor at PlatformIO to understand what is going on. This is what I am getting:

Querying register 0x60... ERR: Time out on register 0x60! got 4/96 bytes
0x03 0x40 0x60 0x5c Querying register 0x10... ERR: Time out on register 0x10! got 4/16 bytes
0x03 0x40 0x10 0xac Retrying...
Querying register 0x10... ERR: Time out on register 0x10! got 4/16 bytes
0x03 0x40 0x10 0xac Retrying...
Querying register 0x10... ERR: Time out on register 0x10! got 4/16 bytes
0x03 0x40 0x10 0xac Retrying...
Querying register 0x10... ERR: Time out on register 0x10! got 4/16 bytes
0x03 0x40 0x10 0xac Querying register 0x20... ERR: Time out on register 0x20! got 4/32 bytes
0x03 0x40 0x20 0x9c Retrying...
Querying register 0x20... ERR: Time out on register 0x20! got 4/32 bytes
0x03 0x40 0x20 0x9c Retrying...
Querying register 0x20... ERR: Time out on register 0x20! got 4/32 bytes
0x03 0x40 0x20 0x9c Retrying...
Querying register 0x20... ERR: Time out on register 0x20! got 4/32 bytes
0x03 0x40 0x20 0x9c Querying register 0x21... ERR: Time out on register 0x21! got 4/33 bytes
0x03 0x40 0x21 0x9b Retrying..._
I have tried with several include/def/models and uncomment many LabelDef without any result in any of the attends.
Any help would be much appreciated.
Current seeting:

Connect the ground pin of x10a to a ground pin of your ESP32.

Thank you Andrea, I will try it out!

Connect the ground pin of x10a to a ground pin of your ESP32.

Thank you @andreapier, after connecting the ground it is now sending data to MQTT broker. Fantastic! solved

Glad you got it working @robertogarciaalvarez
Thanks @andreapier, I guess it's still not big enough on the readme page... ;)


3d Reconstruction

Has anyone been able to come up with a colab notebook for 3d reconstruction, I am facing problems in the conflicting libraries, still trying my best, but if anyone has been able to achieve this let me know. Thanks. I am facing this problem mainly, It does not install properly.
#!pip install git+https://github.com/NVlabs/tiny-cuda-nn/#subdirectory=bindings/torch

Does setting the GCC/G++ version to 8 or higher cause the same problem?

Please feel free to open a new issue if you have any other questions or concerns.


The label "input" type "number" allows to write the letter "e"

This isn't something we affect, it looks like I can switch to non-numerical values for a form field regardless of that input type.


We need to enable Proxy Protocol

https://www.getambassador.io/reference/core/ambassador/
This links to https://github.com/caos/orbiter/issues/18

Proxy protocol can be enabled through the Module-crd


[BUG]error: can't copy 'deepspeed/accelerator': doesn't exist or not a regular file

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
the official doc
git clone https://github.com/microsoft/DeepSpeed.git
cd DeepSpeed
pip install .

bug
      writing manifest file 'deepspeed.egg-info/SOURCES.txt'
      error: can't copy 'deepspeed/accelerator': doesn't exist or not a regular file
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for deepspeed
  Running setup.py clean for deepspeed
Failed to build deepspeed
Installing collected packages: deepspeed
  Running setup.py install for deepspeed ... error
  error: subprocess-exited-with-error

  × Running setup.py install for deepspeed did not run successfully.
  │ exit code: 1
  ╰─> [355 lines of output]
      DS_BUILD_OPS=0
      Install Ops={'async_io': False, 'cpu_adagrad': False, 'cpu_adam': False, 'fused_adam': False, 'fused_lamb': False, 'quantizer': False, 'random_ltd': False, 'sparse_attn': False, 'spatial_inference': False, 'transformer': False, 'stochastic_transformer': False, 'transformer_inference': False, 'utils': False}
      version=0.9.0+0b5252b, git_hash=0b5252b, git_branch=master
      install_requires=['hjson', 'ninja', 'numpy', 'packaging>=20.0', 'psutil', 'py-cpuinfo', 'pydantic', 'torch', 'tqdm']
      compatible_ops={'async_io': True, 'cpu_adagrad': True, 'cpu_adam': True, 'fused_adam': True, 'fused_lamb': True, 'quantizer': True, 'random_ltd': True, 'sparse_attn': True, 'spatial_inference': True, 'transformer': True, 'stochastic_transformer': True, 'transformer_inference': True, 'utils': True}
      ext_modules=[]

Expected behavior
A clear and concise description of what you expected to happen.
ds_report output
Please run ds_report to give us details about your setup.
Screenshots
If applicable, add screenshots to help explain your problem.
System info (please complete the following information):

OS: [centos]
GPU count and types [4 GPU]
Python version 3.9.16
Any other relevant info about your setup

same problem

I have solved it. Setup.py packages does not support soft links. You need to comment the following code in seup.py first:
  create_dir_symlink('..\\..\\csrc', '.\\deepspeed\\ops\\csrc')
  create_dir_symlink('..\\..\\op_builder', '.\\deepspeed\\ops\\op_builder')
  create_dir_symlink('..\\accelerator', '.\\deepspeed\\accelerator')

And then manually copy csrc, op_builder and accelerator to the corresponding directory.

@ucas010  The bug is in setup.py. On line ~270+ where the setup() call is made, you have to add one more argument:
package_dir={"": "."},
so it should become:
setup(name='deepspeed',
      version=version_str,
      description='DeepSpeed library',
      long_description=readme_text,
      long_description_content_type='text/markdown',
      author='DeepSpeed Team',
<EMAIL_ADDRESS>      url='http://deepspeed.ai',
      project_urls={
          'Documentation': 'https://deepspeed.readthedocs.io',
          'Source': 'https://github.com/microsoft/DeepSpeed',
      },
      install_requires=install_requires,
      extras_require=extras_require,
      packages=find_packages(include=['deepspeed', 'deepspeed.*']),
      package_dir={"": "."},
      include_package_data=True,
      scripts=[
          'bin/deepspeed', 'bin/deepspeed.pt', 'bin/ds', 'bin/ds_ssh', 'bin/ds_report', 'bin/ds_bench', 'bin/dsr',
          'bin/ds_elastic'
      ],
      classifiers=[
          'Programming Language :: Python :: 3.6', 'Programming Language :: Python :: 3.7',
          'Programming Language :: Python :: 3.8', 'Programming Language :: Python :: 3.9',
          'Programming Language :: Python :: 3.10'
      ],
      license='MIT',
      ext_modules=ext_modules,
      cmdclass=cmdclass)`

Also if you are running Windows and you encounter compile errors like error
`C2398:` Element '2': conversion from 'size_t' to '_Ty' requires a narrowing conversion`

Consider going to:
deepspeed\csrc\transformer\inference\csrc\pt_binding.cpp  . There you have to make two typecasts:

On prev_key:

```cpp

auto prev_key = torch::from_blob(workspace + offset,
                                     {bsz, heads, all_tokens, k},
                                     {hidden_dim * InferenceContext::Instance().GetMaxTokenLenght(),
                                      k * InferenceContext::Instance().GetMaxTokenLenght(),
                                      k,
                                      1},
                                     options);

to become:

auto prev_key = torch::from_blob(workspace + offset,
                                     {bsz, heads, all_tokens, k},
                                     {static_cast<int64_t>(hidden_dim * InferenceContext::Instance().GetMaxTokenLenght()),
                                      static_cast<int64_t>(k * InferenceContext::Instance().GetMaxTokenLenght()),
                                      k,
                                      1},
                                     options);

Repeat the same typecast for prev_value. What the error means is that basically the second argument (the array), has value of size size_t which is uint64 while we expect int64. We cast all to int64 since int64's max positive value is pretty large and safe

I'm seeing the same issue: error: can't copy 'deepspeed/accelerator': doesn't exist or not a regular file
And indeed: This is a symlink after https://github.com/microsoft/DeepSpeed/pull/2560 got merged: https://github.com/microsoft/DeepSpeed/blob/master/deepspeed/accelerator
So it doesn't even required the line in setup.py which creates the symlink, which now(?) is run on Windows only anyway. Hence removing this doesn't solve the issue.
It is furthermore complicated by this not always happening. Haven't fully verified but I suspect it only appears when the wheel package is installed, which isn't always the case.
The package_dir={"": "."}, line addition from @ldilov fixes this for me.

I found the related bug #1909 and the solution there: https://github.com/microsoft/DeepSpeed/issues/1909#issuecomment-1225113348
Basically:
rm deepspeed/ops/{csrc,op_builder}
rm deepspeed/accelerator
cp -R csrc op_builder deepspeed/ops/
cp -R accelerator deepspeed/

And all works as far as I can tell.
I'd suggest to not use symlinks in this repo at all which will avoid this issue in the first place.
Or if you have too for development ease: Do the other way round: Create symlinks to the convenience places not where the files are actually required (i.e. reverse source and target)

Currently working on #4323 to remove the symlinks and hopefully resolve this issue. Please try that PR if you are still seeing this error.

I found the related bug #1909 and the solution there: #1909 (comment)
Basically:
rm deepspeed/ops/{csrc,op_builder}
rm deepspeed/accelerator
cp -R csrc op_builder deepspeed/ops/
cp -R accelerator deepspeed/

And all works as far as I can tell.
I'd suggest to not use symlinks in this repo at all which will avoid this issue in the first place.
Or if you have too for development ease: Do the other way round: Create symlinks to the convenience places not where the files are actually required (i.e. reverse source and target)

This work for me, thanks!

this did not fix it for me. on arch linux. still says error: can't copy 'deepspeed/accelerator': doesn't exist or not a regular file even though I deleted the symlinks and copied the directories over.

spoke too soon. changing the symlinks for copying didn't work, but adding package_dir={"": "."}, did fix it

I think I am seeing the problem only on Ubuntu 22.04 not on Ubuntu 24.04. (Need to double check)
rm deepspeed/ops/{csrc,op_builder}
rm deepspeed/accelerator
cp -R csrc op_builder deepspeed/ops/
cp -R accelerator deepspeed/
But on AMD ROCM platform there is potential hipify problem. If I do these steps before the build starts, I get it building.
because the hipify command is creating the hip-files from cu-files on csrc folder, not on op_builder deepspeed/ops/csrc
[lamikr@miley DeepSpeed ((7940129a...))]$ find ./csrc -name *.hip | wc
30      30    1222
[lamikr@miley DeepSpeed ((7940129a...))]$ find ./deepspeed/ops/csrc/ -name *.hip  | wc
0       0       0
Luckily it seems that this does not cause problem and Deepspeed seems to work when this workaround i used.
Is there some good reason why csrc, op_builder and accelerator directories are in root-directory and symlinked then under deepspeed/accelerator, deepspeed/ops/csrc and deepseepd/ops/op_builder? Would it make more sense to just put them in real location without symlink in future versions?


[TCID-DIR-TEAMING-USER-ROLE-UPDATE]: Teaming tests for user role update

Below test cases will be covered in this tcid:

Change user role to ProjectAdmin from ProjectMember

Change user role to ProjectAdmin from ProjectReadAdmin

Change user role to ProjectMember from ProjectAdmin

Change user role to ProjectMember from ProjectReadAdmin

Change user role to ProjectReadAdmin from ProjectAdmin

Change user role to ProjectReadAdmin from ProjectMember

https://github.com/mayadata-io/oep-e2e-aws/pull/29
https://github.com/mayadata-io/gui-automation/pull/24


v0.9.23 release

It is not a private fork URL but a GitHub Security Advisory. It won't disappear even after the deletion of a private fork. But I'll use cve.mitre.org as we used to or cve.org link instead.

OK - thanks for the info.


Updating taskDefinition(ECS) falls into ReconcileError

What happened?

I am getting the following error when I update the spec.forProvider.containerDefintions section after initial deploy.
  - lastTransitionTime: "2023-08-11T12:45:46Z"
    message: 'observe failed: cannot run plan: plan failed: Instance cannot be destroyed:
      Resource aws_ecs_task_definition.test2-ecs-ns1 has lifecycle.prevent_destroy
      set, but the plan calls for this resource to be destroyed. To avoid this error
      and continue with the plan, either disable lifecycle.prevent_destroy or reduce
      the scope of the plan using the -target flag.'
    reason: ReconcileError
    status: "False"
    type: Synced

Here is my entire manifest
apiVersion: ecs.aws.upbound.io/v1beta1
kind: TaskDefinition
metadata:
  labels:
    app.kubernetes.io/part-of: ecs-test
    apps.tanzu.vmware.com/has-tests: "true"
    apps.tanzu.vmware.com/workload-type: ecs
    app.kubernetes.io/component: run
    carto.run/workload-name: test2
  name: test2-ecs-ns1
  annotations:
    boot.spring.io/version: 3.1.2
    conventions.carto.run/applied-conventions: |-
      appliveview-sample/app-live-view-appflavour-check
      spring-boot-convention/auto-configure-actuators-check
      spring-boot-convention/spring-boot
      spring-boot-convention/spring-boot-graceful-shutdown
      spring-boot-convention/spring-boot-web
      spring-boot-convention/spring-boot-actuator
      spring-boot-convention/spring-boot-actuator-probes
      spring-boot-convention/app-live-view-appflavour-check
      spring-boot-convention/app-live-view-connector-boot
      spring-boot-convention/app-live-view-appflavours-boot
    developer.conventions/target-containers: workload
spec:
  deletionPolicy: Delete
  providerConfigRef:
    name: aws-provider
  forProvider:
    containerDefinitions: |-
      [
         {
            "cpu": 0,
            "environment": [
               {
                  "name": "JAVA_TOOL_OPTIONS",
                  "value": "-Dmanagement.endpoint.health.probes.add-additional-paths=\"true\" -Dmanagement.health.probes.enabled=\"true\" -Dserver.port=\"8080\" -Dserver.shutdown.grace-period=\"24s\""
               }
            ],
            "essential": true,
            "image": "ghcr.io/mhoshi-vm/tap/workloads/test2-ecs-ns1@sha256:d9c14cb82c2b5c838a7d8e3123fe4cc9fd3727c7f0c3505dcae0510361352a43",
            "mountPoints": [],
            "name": "workload",
            "portMappings": [
               {
                  "containerPort": 8080,
                  "hostPort": 8080,
                  "protocol": "tcp"
               }
            ],
            "user": "1000",
            "volumesFrom": []
         }
      ]
    family: test2-ecs-ns1
    region: us-west-2
    cpu: "512"
    memory: "1024"
    networkMode: awsvpc
    skipDestory: true
    requiresCompatibilities:
    - FARGATE
  initProvider: {}
  managementPolicies:
  - '*'

How can we reproduce it?

Deploy above and modify anywhere in containerDefinitions such as enviroments.
What environment did it happen in?

Crossplane Version: 1.12.up-2
Provider Version: v0.38.0
Kubernetes Version: 1.26
Kubernetes Distribution: EKS

btw i realized i miss spelled skipDestroy to skipDestory in the above example.
However even fixing that i still see the issue

Hi @mhoshi-vm,
Thank you for raising this issue, it can be reproduced with provider-aws v0.39.0:
  - lastTransitionTime: "2023-08-28T18:10:08Z"
    message: 'observe failed: cannot run plan: plan failed: Instance cannot be destroyed:
      Resource aws_ecs_task_definition.sample-taskft has lifecycle.prevent_destroy
      set, but the plan calls for this resource to be destroyed. To avoid this error
      and continue with the plan, either disable lifecycle.prevent_destroy or reduce
      the scope of the plan using the -target flag.'
    reason: ReconcileError

I'll mention my team and I were getting a similar error with an RDS resource, upgrading from 0.38.0 to 0.47.4 resolved it for us


Fix branch protection with OSS forks

GitHub update the preview API to update the branch protection, which is used by the OSS forking script. For this reason, mirrored branches silently failed to be protected.
This adjusts for the changes in the preview API, namely by setting the required field required_pull_request_reviews.

Thank you 👍 😄


using material design , how to change the help text

Hello ,
i use framework as material design...  haven't see any option to put help text in schema or in form but it show help text seems converting the text passed as key . how can i change that text for text field.
Also how can i show radio button as required. for text field or drop down if i mentioned those field in required:[textfield1,dropdown2,radiobutton3] those comes as * in help text but not for radio button.
how to show it as required. title with *

found the answer for question i asked so ignore it .


Links redirecting to Magybu.net in Chrome

Domain
https://ckk.ai/V7x4eu57
Link
https://ckk.ai/V7x4eu57
Version
0.0.0
What browsers are you seeing the problem on?
Chrome
What OS are you seeing the problem on?
Windows
Anything else?
When clicking on the link, it would take you to a urlshortener, most likely by adf.ly, and after do a 'I'm not a robot' gatcha, you click 'Get Link' It would look like it is bypassing the rest but it take you do magybu.net stating that This page isn't working and that the site redirected you too many times.
Clicking reload does nothing. I have turn off FF and the same result happens. Not sure if it is on my end or not but this never happen before until yesterday when I went to download from the link.
Links works correctly with FF on in Edge but not with Google Chrome.

Also based on what type of bypass it makes i suggest that removing or at least make it work without crowdbypass enabled

Duplicate of #668.
However, @Dragoonity, I highly recommend you post the behavior of the site on that issue so that the developers can see everything in one issue,


paper: fix formatting of bib

:wave: @arfon, this is a counter proposal to #7.
Please take a look.

👍 this looks good:

http://joss.theoj.org/papers/10.21105/joss.00234
https://github.com/openjournals/joss-papers/raw/master/joss.00234/10.21105.joss.00234.pdf

Thanks.


Fix typescript compile issues with simple-http-example

For now i just marked them as 'ts' instead of 'typescript' as it's better to remove/reduce this tutorial step/page anyway.

fixed


openvpn, startup locking sequence to prevent issues around pid file / process management

openvpn, startup locking sequence to prevent issues around pid file / process management
fixes: https://redmine.pfsense.org/issues/6940

I'm afraid it will slow down boot in cases where many tunnels are configured.

6940 was marked as duplicate of https://redmine.pfsense.org/issues/6132


[Bug]: Browsers not getting installed in Linux Alpine Image

Playwright version
1.13.0
Operating system
Linux
What browsers are you seeing the problem on?
Chromium
Other information
Java version - Open JDK 11
Linux Distribution - Alpine image (Linux 67e56ec3db81 5.10.25-linuxkit #1 SMP Tue Mar 23 09:27:39 UTC 2021 x86_64 Linux)
What happened? / Describe the bug
We have been following the script - https://github.com/microsoft/playwright-java/blob/master/Dockerfile.focal  to install playwright in a Linux Alpine Image.  It was noticed that the Java Process Builder (https://github.com/microsoft/playwright-java/blob/master/driver-bundle/src/main/java/com/microsoft/playwright/impl/DriverJar.java#L47) is unable to find the node executable present inside the temp directory while installing the browsers.
On some debugging, we found that the executable was indeed present at that location and the it works fine if we copy the executable and run the same command through bash terminal.
Strangely the above error persists even if we run export PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 which should ideally print Skipping browsers download because PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD env variable is set
Code snippet to reproduce your bug
mvn exec:java -e -D exec.mainClass=com.microsoft.playwright.CLI -D exec.args="install-deps" -f playwright/pom.xml --no-transfer-progress

Relevant log output
/tmp/playwright-java-10445247894034150309/playwright.sh: line 3: /tmp/playwright-java-10445247894034150309/node: not found
[WARNING]
java.lang.RuntimeException: Failed to create driver
    at com.microsoft.playwright.impl.Driver.ensureDriverInstalled (Driver.java:54)
    at com.microsoft.playwright.CLI.main (CLI.java:32)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:254)
    at java.lang.Thread.run (Thread.java:834)
Caused by: java.lang.RuntimeException: Failed to install browsers, exit code: 127
    at com.microsoft.playwright.impl.DriverJar.installBrowsers (DriverJar.java:58)
    at com.microsoft.playwright.impl.DriverJar.initialize (DriverJar.java:38)
    at com.microsoft.playwright.impl.Driver.ensureDriverInstalled (Driver.java:52)
    at com.microsoft.playwright.CLI.main (CLI.java:32)
    at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java:254)
    at java.lang.Thread.run (Thread.java:834)

We have been following the script - https://github.com/microsoft/playwright-java/blob/master/Dockerfile.focal  to install playwright in a Linux Alpine Image. It was noticed that the Java Process Builder (https://github.com/microsoft/playwright-java/blob/master/driver-bundle/src/main/java/com/microsoft/playwright/impl/DriverJar.java#L47) is unable to find the node executable present inside the temp directory while installing the browsers.

You probably saw the note about Alpine not being officially supported by Playwright. With that said you might be able to make it work with existing Chromium build on Alpine by setting custom executable path and PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1.

Strangely the above error persists even if we run export PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD=1 which should ideally print Skipping browsers download because PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD env variable is set

There was a regression of PLAYWRIGHT_SKIP_BROWSER_DOWNLOAD behavior in 1.13 which is fixed by #551 and should make it into the next 1.14 release which will be published in the next few days.
Also note that install-deps only works on Ubuntu distros and will fail for Alpine.

Thanks a lot !! Just a follow up question -

Also note that install-deps only works on Ubuntu distros and will fail for Alpine.

What exactly do these exec.args="install-deps" and  the exec.args="install-deps" steps (present in the dockerfile) do ? Will it be sufficient if we are able to download all the drivers and do a mvn install [till - (https://github.com/microsoft/playwright-java/blob/master/Dockerfile.focal#L27)] in the Alpine image for a successful playwright installation ?
Note this is while skipping the browser download and adding a custom path as suggested by you.

Also note that install-deps only works on Ubuntu distros and will fail for Alpine.

What exactly do these exec.args="install-deps" and the exec.args="install-deps" steps (present in the dockerfile) do ?

They install third party libraries that the browsers depend on: https://github.com/microsoft/playwright/blob/master/src/nativeDeps.ts

Will it be sufficient if we are able to download all the drivers and do a mvn install [till - (https://github.com/microsoft/playwright-java/blob/master/Dockerfile.focal#L27)] in the Alpine image for a successful playwright installation ?

If you have working Chromium browser on Alpine AND you replace the Node binary that we bundle with another one that runs on Alpine it might work.


test:server failure

I used the mern cli tool to create  a new app and see these errors when i run the test:server tests
GET /api/getPosts
✓ Should correctly give number of Posts (1539ms)
GET /api/getPost
✓ Should send correct data when queried against a title (615ms)
POST /api/addPost
1) Should send correctly add a post
POST /api/deletePost
2) "before each" hook: connect and add one Post entry
3) "after each" hook for "Should connect and delete a post"
2 passing (12s)
3 failing

POST /api/addPost Should send correctly add a post:
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.

POST /api/deletePost "before each" hook: connect and add one Post entry:
Uncaught TypeError: Cannot read property 'name' of null
at post.spec.js:118:18
at Query. (node_modules/mongoose/lib/query.js:2149:28)
at node_modules/mongoose/node_modules/kareem/index.js:177:19
at node_modules/mongoose/node_modules/kareem/index.js:109:16

POST /api/deletePost "after each" hook for "Should connect and delete a post":
Error: timeout of 2000ms exceeded. Ensure the done() callback is being called in this test.

I find it very strange just upgraded and run test: server and there is no problem could you please provide more information or have modified the test

All tests are passing for me too.. Check again and let me know!

Im seeing different issue now - i think there might be an issue with the computer as it is acting really slow, do you know how long should it take to run npm install in a new mern project? it is taking me about 3 and a half minutes which seems really long
GET /api/getPosts
1) Should correctly give number of Posts
GET /api/getPost
✓ Should send correct data when queried against a title (529ms)
POST /api/addPost
✓ Should send correctly add a post (878ms)
POST /api/deletePost
webpack built b60656cce612f1addf89 in 6195ms
✓ Should connect and delete a post
3 passing (6s)
1 failing

GET /api/getPosts Should correctly give number of Posts:
Uncaught AssertionError: expected 2 to equal 1

expected - actual

-2
+1

tests run again the fault is in your pc run them when I vuelvelo do and fixed pass, were attentive you warn us

I believe there is an issue with the deletePost test - that while it reports successful it does so without running
expect(post).to.equal(null);
What I believe is happening is the afterEach() cleanup is being called prior to executing deletePost in the post.controller.js
and the test is falling through without reporting a failure.
I have yet to understand why this is though

I believe the problem is that the 'done' state is not passed into the deletePost test
it('Should connect and delete a post', function () {
should be
it('Should connect and delete a post', function (done) {
I'll raise a pull request for review


DQNAgent.fit having MultiInputProcessor crashes with "verbose=2"

Steps to reproduce :

Go to file keras-rl/tests/rl/agents/test_dqn.py
In function test_multi_dqn_input
replace the line
        agent.fit(MultiInputTestEnv([(3,), (4,)]), nb_steps=10)
with
        agent.fit(MultiInputTestEnv([(3,), (4,)]), nb_steps=10, verbose=2)

error :
Traceback (most recent call last):
  File ".../keras-rl/tests/rl/agents/test_dqn.py", line 31, in test_multi_dqn_input
  File "/usr/local/lib/python2.7/dist-packages/rl/core.py", line 158, in fit
    callbacks.on_episode_end(episode, episode_logs)
  File "/usr/local/lib/python2.7/dist-packages/rl/callbacks.py", line 57, in on_episode_end
    callback.on_episode_end(episode, logs=logs)
  File "/usr/local/lib/python2.7/dist-packages/rl/callbacks.py", line 170, in on_episode_end
    'obs_mean': np.mean(self.observations[episode]),
  File "/usr/local/lib/python2.7/dist-packages/numpy/core/fromnumeric.py", line 2885, in mean
    out=out, keepdims=keepdims)
  File "/usr/local/lib/python2.7/dist-packages/numpy/core/_methods.py", line 65, in _mean
    ret = umr_sum(arr, axis, dtype, out, keepdims)
ValueError: operands could not be broadcast together with shapes (3,) (4,)

The problem probably comes from the fact that np.mean with a list of np.array doesn't manage to correctly merge the arrays before computing the mean.

Same issue here I have patched and modified a couple of callbacks.py lines of code and right now is working, but I'm not sure what kind of side effects could have.
Line 176. I have removed the parts that reference observation... so patched this line....
#template = '{step: ' + nb_step_digits + 'd}/{nb_steps}: episode: {episode}, duration: {duration:.3f}s, episode steps: {episode_steps}, steps per second: {sps:.0f}, episode reward: {episode_reward:.3f}, mean reward: {reward_mean:.3f} [{reward_min:.3f}, {reward_max:.3f}], mean action: {action_mean:.3f} [{action_min:.3f}, {action_max:.3f}], mean observation: {obs_mean:.3f} [{obs_min:.3f}, {obs_max:.3f}], {metrics}'
copy and this is the line 177 now
template = '{step: ' + nb_step_digits + 'd}/{nb_steps}: episode: {episode}, duration: {duration:.3f}s, episode steps: {episode_steps}, steps per second: {sps:.0f}, episode reward: {episode_reward:.3f}, mean reward: {reward_mean:.3f} [{reward_min:.3f}, {reward_max:.3f}], mean action: {action_mean:.3f} [{action_min:.3f}, {action_max:.3f}], {metrics}'
And what now are lines 192, 193, 194
    # 'obs_mean': np.mean(self.observations[episode]),             # 'obs_min': np.min(self.observations[episode]),             # 'obs_max': np.max(self.observations[episode]),
Hope it helps, and I hope someone involved with keras-rl can help.
Thanks in advance.


Fillable forms

Can I create a form in html and export it as a fillable PDF? That doesn't seem to be happening by default with my html form.
Edit: To elaborate, I am trying to build a pdf journal so my users can enter their reflections in input fields and use checkboxes to mark tasks complete. I have built these with a form but am not able to interact with the form when I export the PDF.

A major part of html2PDF is a dependency on htmltocanvas before creating the pdf with jsPDF. This middle step created an image to put into the pdf. It being an image means it is not text and cannot be interacted with or even copied. This is fine if printing and filling out the paper, but not if you want to fill out digitally. You might need to look into trying to build your form more directly with jsPDF, but I have no experience with that.  But really, I would recommend them filling the form in the browser and storing the "journal" into a database or something. Not sure what your exact use-case is however.


[Website Improvements]  Individual component specification pages (see Jakarta specification pages for reference) MPWG repo #145

Features and background on task:

MPWG repo issue Individual component specification pages (see Jakarta specification pages for reference) #145
David's specific comments and description on requirements: https://github.com/microprofile/microprofile-wg/issues/145#issuecomment-1650470090
related to git ticket  [draft mock-ups of separate specification pages
#795](https://github.com/eclipse/microprofile-marketing/issues/795)
and closed tickets https://github.com/eclipse/microprofile-marketing/issues/795#issuecomment-1649782637

@rstjames,
As discussed, previews work on this task is dropped and refocused. David has been added to the ticket. Should you have any questions, he is your task support. :)

@dblevins is this what you were thinking?

Items to add:

TCK Link
Status of the spec (under development, final)
Maven coordinates
Compatible Implementations

For the demo the Maven coordinates for JWT 2.1 are:
<dependency>
    <groupId>org.eclipse.microprofile.jwt</groupId>
    <artifactId>microprofile-jwt-auth-api</artifactId>
    <version>2.1</version>
</dependency>

Note that specs under development may not yet have a links such as spec pdf, spec html, tck or compatible implementations

Here is a compatible implementation to add to the JWT 2.1 page:

Open Liberty <IP_ADDRESS>-beta

Basic elements of a spec release page:

Spec name and title and status
Description from the Plan Review or Release Review ballot
Compatible implementations (this section will have links to approved Certification Requests)
Links (this will have the spec pdf, spec html, tck and maven coordinates)

These sections can have any heading  or be arranged on the page in any way that looks visually appealing.

@dblevins
here is the latested version. I used Metrics 5.1 because I could find most of the content we discussed should be there.
Thoughts?

not sure what info should be on the Compatible Implementations so I just put a filler for now.
light code section or dark
Think it could be "designed up" bit more but need to have all content we feel should be there.

@rstjames TCK Results should be TCKs to point to the download location for TCK jars.

Updated layout and content:

@Emily-Jiang, how do I move this forward? For me to do this, I will need the template content for each spec. After that, I can make each individual page.
I think each spec page should have its own ticket. That way, we can have content for each in one spot and review each before putting them live.

I like having a ticket per spec page

@Emily-Jiang I created git tickets for each specification; please check if I didn't miss something. Also, I created a doc that can be used for organizing each spec content.
https://docs.google.com/document/d/1i2I8zwvoVYx3Dx_d2hXqHwmqv-cVCFxNobWOOhpVhAo/edit?usp=sharing
Can you please read over this and let me know what you think?
@aeiras you too :)

@rstjames,
Great work on drafting a how to template the Spec. I provided my feedback and recommend you lead the show and tell and finalize its review before documentation becomes a wiki under the MPWG repo.  Really good draft.


fix(demo): unsubscribe subscriptions to avoid memory leaks

Please check if the PR fulfills these requirements

[x] The commit messages follow our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] A unit test has been written for this change.
[x] Running npm run build produced a successful build. (Unit testing can be done by running npm test;)
[x] My code has been linted. (npm run lint to do this. npm run build will fail if there are files not linted.)

Hello 👋
As part of our project, we are using Facebook's new Memlab tool to detect memory leaks in SPA applications and their libraries. While running the tool and analyzing the code of ngx-formly, we saw that your project does a very good job of ensuring that all async operations are cancelled when components destroy. However, as per Memlab execution results, we found some unsubscribed subscriptions, causing the memory to leak (screenshots below).
[before]

Hence we added the fix by unsubscribing the subscriptions on component destruction, and you can see the heap size and count of leaks reducing noticeably:

Note. Host listener is used to ensure that ngOnDestroy is called not only when the class destroy, but also when the page refreshes, tab or browser closes or the user navigates away from the page [1]
We executed the test suite after the fixes and it successfully passed 56 of 56 total (in watch + non-watch mode)
You can analyze this and other potential leak sources, if you like, by running Memlab with a scenario file covering maximum count of use cases.
Following is a sample of the scenario file we used (it needs to be a .js file but attaching here in .txt form):
ngx-formly-scenario.txt
Note that some other reported leaks (in Memlab) originated from Angular's internal objects, and hence were ignored.
References:
[1] https://wesleygrimes.com/angular/2019/03/29/making-upgrades-to-angular-ngondestroy.html

bump @aitboudad

Thank you @Arooba-git!


Enables basic health check support in docker, so the container can be marked as unhealthy on failure instead.

Validation:

Confirm that the container sleeps after a backup failure: Done
Confirm that the container is marked unhealthy after exiting starting state: In Progress
Confirm that the container is marked healthy when issue causing unhealthy state is fixed: Todo


Use VMWare ISV Service for CI clusters

Previously infra provided TAS clusters in AWS. This commit switches
to using clusters provided by VMWare. These clusters are single use,
allocated and deallocated during the pipeline.

Rebased on https://github.com/cyberark/conjur-service-broker/pull/274 to fix the vulnerability scan.


Manually ASIM Deployment - Failed to validate, Conflict

Describe the bug
Upon trying to deploy ASIM parsers via the 'Deploy to Azure' button and filling out the required parameters, a 'Conflict' error appears with the following error: (workspace, location and resource group have been omitted)
The resource '<SENTINELWORKSPACE> already exists in location <LOCATION> in resource group <RESOURCEGROUP>. A resource with the same name cannot be created in location <LOCATION>. Please select a new resource name.

Upon giving it a different name, it creates a new LAW in the designated resource group.
To Reproduce
Steps to reproduce the behavior:

Go to list of parsers https://github.com/Azure/Azure-Sentinel/tree/master/ASIM
Deploy any of them
Fill out the workspace name in the 'Workspace' field and pick the correct resource group containing the LAW
Deploy

Expected behavior
The parsers should deploy into the targeted workspace and become available for query.
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser: Edge
Version: 115

Additional context
I have all required permissions to deploy this content.

Hi @rcegan, we are checking on this and we will provide an update soon.

Hi @rcegan, waiting for update from concerned team, once we receive an update will let you know.

Hi @rcegan, waiting for update from concerned team, once we receive an update will let you know.

Hi @rcegan, we are still waiting for update from concerned team, we will get back to you once there is an update.

Hi @rcegan, we are still waiting for update from concerned team, we will get back to you once there is an update.

I was able to work around the problem by deploying the resources to a different location than the log analytics workspace itself. Solves my issue but I suspect that's probably not the intended behaviour

I was able to work around the problem by deploying the resources to a different location than the log analytics workspace itself. Solves my issue but I suspect that's probably not the intended behaviour

According to the error message, it is working as expected.

@rcegan thanks for raising this issue. Can you please share the location details where it failed and where it worked for you?

I was working with Australia Southeast and Australia East. Deploying to Australia Southeast, with the log analytics workspace in the same location, the deployment failed (due to a resource already existing in that location - the workspace itself). Picking a different location (Australia East) it appeared to work fine.

Hi, This behavior is as expected due to the following reason.
When deploying the ASIM parsers using the ARM templates a POST request is done at the background.
Because the ASIM parsers already exists, this will result in an error as described above.
There are 2 workarounds to remediate this issue:

Remove the existing ASIM parsers for the workspace using the Microsoft PowerShell script
Deploy the updated parsers using the API using the UPDATE method.

It is more an issue related to Log Analytics than Microsoft Sentinel or ASIM as they are dependent on Log Analytics.
What I can do is create a PowerShell script that updates the ASIM parsers is they already exists and use the ASIM yaml files as input. Or create and ARM template that uses a Script Extension to run the PowerShell script in a different context.
This might need some extra permissions in the Azure Subscription / Resource Group but need to validate this first.
@rcegan @vakohl

@rcegan I created a new workspace, deployed Process Event parsers multiple times on same workspace. I didn't got that error. Am I missing anything that you tried? What schema parser you were trying to deploying. Can you please retry on a new and on the same workspace you previously tried, see if you are still getting that error?

Hi @rcegan,
Gentle Reminder: We are awaiting for your response on this issue. If you still need to keep this issue active please respond on it in the next 2 days. If we don't receive response, we will be close this issue.

Sorry to add to the noise, but I'm having the exact same problem. Tried deploying all ASIM parsers and then just one-by-one, same error message "Conflict"

I've tried putting the LAW in Australia Southeast and the LAW in Australia East, and also putting them in the same region, no difference to the output.
Drilling into the error message isn't any more help, just states eTAG for specific error was outdated
newer data exists. If you are using eTag please use the latest one and try again in a few minutes. Operation Id: '4918a525df68776dd0a7063aaa6db6dd' (Code: NewerDataExists)

@rcegan @jusso-dev FYI, this issue is being investigated.

@rcegan @jusso-dev @azurekid
This issue is still being looked into. This seems more of Log Analytics issue than Sentinel, we are working with concerned teams to get this fixed.

tagging related issue, raised by another user - https://github.com/Azure/Azure-Sentinel/issues/10481

The root cause of the issue is that each parser deployment script deploys the Log Analytics workspace before deploying the saved search. The conflict happens when tens of parser deployment ARM templates are trying to deploy the Log Analytics workspace at the same time.
The current version of ASIM parser deployment could create a new Log Analytics workspace, which could be unwanted behavior. I would expect the ASIM parser deployment ARM template only to create parsers for the already existing Log Analytics workspace and not create another one if I, for example, type the workspace name wrong into the template.
The issue does not relate to the existing versions of the ASIM parsers, as I have seen this issue occur when deploying the ASIM parsers for the first time to a given Log Analytics workspace. The error messages always refer to the workspace, which is constantly redeploying itself by the referenced ARM templates. Also, the referenced parser templates always seem to define "etag": "*", meaning they always overwrite the existing resource.
I made an example commit on how the issue could be solved by only verifying the Log Analytics workspace exists by declaring the workspace as an existing resource: 0986d7f
@vakohl, what do you think of this solution? Would you like me to implement it for the other parsers as well, or would you prefer to tackle the issue in-house?

Any news on this?
Ive deployed a few sentinels the last few months and all of them had these issues. I started deploying each entity by itself and i have about 70% success and 30% fails with "Newer data exists".
Here is when running the DNS asim by itself as an example:

"Failed to modify resource '/subscriptions/xxxxxxxxxxxxxxx' Microsoft.OperationalInsights/workspaces/xxxxxxxxx', newer data exists. If you are using eTag please use the latest one and try again in a few minutes"

I found a way to deploy the saved search without deploying the Log Analytics workspace and without using the languageVersion 2.0. I believe this should be the least possible change for each parser ARM template file to fix the issue of unnecessarily redeploying the Log Analytics workspace.
Example: 5aa3b7537996d7a4abfb31e352d3f4b3b366d827
I will prepare the required changes for the parser ARM templates and create a PR.


How to unistall?

Hello, As the title suggests, how can I uninstall completely?

Release 1.2
Can I ask why you want to uninstall?

Nothing, I thought it didn't work, then I realized that I was using 2 versions of canary and one was giving me problems, I solved it by removing the wrong version and now glasscord works.


Make checker disabled by default to increase stability of LazyVim

Currently checker is on, which is just distracting people, often at the bad time too.
Updating LazyVim is pretty eazy, but sometimes updates break something at the WRONG TIME.
Let people decide when to update themselves. After all, if they are smart enough to use Neovim, they are smart enough to know how to press space + l  and S when they have free time.
-- at lua/config/lazy.lua
  checker = {
    enabled = true, -- check for plugin updates periodically
  },

check again....
checker notifications are disabled.
checker is only enabled to show the lualine component.
Besides, users are smart enough to change the settings if they don't like them.


Replace Postman test with another type of test

Replace letter-generation-testing-ci postman test with another tool

For @sbhamani and @thoughtworks-vwong to discuss

Currently researching tools and I will also be speaking to my QA team and QA manager and ask for their input.

Primarily written in Java
Has built in library that already handle API calls
Designed for testing RESTful APIs
Use standard HTTP methods (GET, POST, PUT, DELETE)
Allow for flexible data formats, such as JSON or XML
Can take advantage of HTTP caching mechanisms to improve performance and reduce server load
REST APIs can be secured using standard HTTP authentication mechanisms like OAuth or API keys, as well as HTTPS encryption for secure data transmission
Great community support + extensive documentation

@thoughtworks-vwong to have a meeting w/ @sbhamani to discuss another framework today

Feature
Jest
Vitest

Focus
Primarily unit testing, supports other types
Primarily unit testing, limited native support for E2E

Framework Integration
Requires separate configuration
Seamless integration with Vite configuration

Built-in features
Requires additional libraries for assertions and mocks
Includes Chai assertions and Tinyspy for mocks and stubs

API
More complex API
Simpler and cleaner API

Speed
Fast, but Vitest generally considered faster, especially in watch mode
Extremely fast, particularly for watch mode re-runs

Community and Support
Large and established community, extensive documentation and resources
Growing community, active development, but less established resources compared to Jest

Maturity
Mature and well-established
Newer framework, still under development

Compatibility
Wide compatibility with different JavaScript projects
Primarily designed for projects using Vite

Testing libraries
Works directly with various testing libraries like React Testing Library
Requires manual integration with specific testing libraries