Setup ci and codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@567ec31). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   91.57%
=========================================
  Files             ?        9
  Lines             ?       95
  Branches          ?       10
=========================================
  Hits              ?       87
  Misses            ?        5
  Partials          ?        3

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 567ec31...46672eb. Read the comment docs.


TOOL:  Add technical rule to reject nul forms without GUID and IDIR value

As a program area technical team, I want to ensure that any forms without GUID or IDIR value are rejected

@Abuchana I've started the ticket and pulled it into this sprint, thinking we'll want to implement this rule soon (and before the 1.10 form is launched)
We'll need a dev estimate of effort

@T854236
I sent three Telework applications on DEV:
7191 => no bcguid (has idir)
7192 => no bcguid no idir
7193 => no idir (has bcguid)

@iman-jamali-fw
Thanks Iman.  That didn't work as expected.  Restrictions is now on the database level.  Can you try again?
Please let me know if the same can be applied for the schedule column or are there cases where it can be Null.

Disregard my question on schedule column, I see there is a scenario for it

@T854236
Just sent one with applicationId 7205. I can see my request to ODS failed with 500 error.

Added Fazil to this ticket with so many folks away today/this week - let's keep an eye on this one

@iman-jamali-fw
Perfect, thank you.  I see in the logs that it rejected it because of missing IDIR value.

@T854236
I sent two more to have all the conditions (IDIR null, GUID null, and both NULL) and can see all three stopped with 500 errors. Which I believe is the expected result we want for this ticket :)

@iman-jamali-fw
Yes, I see 9 tests total.  All expected to test the Null values.  We will add this change to our next BI change in January.

Will go to Telus change window in January - approved


The problem of training latent discriminator

Very wonderful work! But I meet the following question when training the discriminator:
pc_path = os.path.join(self.mesh_dir, code, f"coacd/pc_2048_{rand_id:03d}.npy")
with open(os.path.join(self.mesh_dir, code, f"coacd/pc_norm_latent_LION_{rand_id:03d}.pk"), 'rb') as f:

It seems that there is no file of npy and pk and I can not skip reading these files. How can I get these files to train the discriminator?
I appreciate you taking the time to look into this.

Try use scripts/save_pc_latent.py to presave those latents.


Handle duplicate file upload, TypeScript dropzone-widget component

Purpose
Duplicates show up after overriding a file
Summary of Changes
TypeScript dropzone-widget
Handle duplicate upload
Side Effects / Testing Notes
Ticket
https://openscience.atlassian.net/browse/EMB-
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Coverage decreased (-0.6%) to 30.0% when pulling 6c0249e49dfb3f13e658b69694250b212a07f813 on binoculars:fix/duplicate-upload into 5fec8b6bf4cc9a94f5f31307c9910963e80ed087 on CenterForOpenScience:develop.


What happened to the listing of the minor parties on the party page

They used to be there and now they are gone.

Our ingestion workflow modifies the Opposition Party (which is the name of two unrelated parties, one in the 34th and one in the 36th) -- something in this broke, which cause the congresses active field for the Opposition party to be wrong, which broke display of all parties after the Opposition Party.
Temporary mitigation: saner error handling for the congresses active field. DONE.
Long-term fix: re-run the party stuff to fix the underlying data issue.

This is fully fixed.


Introduce mul_by_inverse_unchecked, and use it

Description
Resolves https://github.com/arkworks-rs/r1cs-std/pull/70#issuecomment-874472795.

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (master)
[x] Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
[ ] Wrote unit tests
[x] Updated relevant documentation in the code
[x] Added a relevant changelog entry to the Pending section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer

Do you have a good way to add a regression test for this behaviour?

Ok I added a check to make sure domain.offset is non-zero by construction. I don't know if this is a good idea: is there ever a case where domain.offset is supposed to be zero? If so, then I can change it to enforce the check inside lagrange_interpolate_with_non_constant_offset, instead of in Radix2DomainVar::new

domain.offset should never be zero for multiplicative domains, but I don't think that needs to be proven in circuit. Thats about the circuit definition being valid. (The circuit definition has defined an invalid codeword domain if its zero, the offset derivation shouldn't allow construction of zero domain offsets)

I think @tsunrise's code require offset to be a variable, so we have to enforce non-zeroness at some point.

Oh I see. If necessary as a temporary defense in depth for correctness seems like an alright fix then.
What I'd rather see is we assert this on the DomainVar itself (that its offset and generator are non-zero). Basically in the constructor for DomainVar, include an argument for the inputs being guaranteed to be non-zero. If false, then do the non-zero checks once there.

Yeah, that's what I changed it to do: https://github.com/arkworks-rs/r1cs-std/blob/213e53d6c33fc3eb4c77791a90dc8b5bb5f549aa/src/poly/domain/mod.rs#L28

I meant explicitly including an argument to not get a constraint created. Currently it seems like a constraint is always created if offset is not a constant?

Ah so like a new_unchecked method?

Its constructed once per query per round, so ~200 times.

I see, with a different offset each time?

I think I addressed all comments, except for the new_unchecked for DomainVar. I think for the time being it's fine to use new, as it only adds a couple hundred constraints, which would be dominated by the rest of the circuit.
Technically, this is a breaking change due to the changes to the DomainVar API, but since the only consumer of that is ark-ldt, I believe, I think it's fine to do that.
(Maybe we should have "in-flux" features hidden behind a unstable feature flag?)


pueue: 1.0.3 -> 1.0.4

Motivation for this change
Bump pueue to latest revision
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 145731 run on x86_64-linux 1

1 package built:

pueue


V5(added missing functions/updated usage)

Archive thread, this needs to be waited for @USERSATOSHI's merge request on aoi.js v5.1.2

@Leref, now it is ready to be merged.

If you weren't aware, SUMMARY.md must be updated as well for these new functions to appear.

Sure, we can also update it too.

Your merge has conflicts. Please resolve them!

@Leref , deleted ./SUMMARY.md and updated ./src/SUMMARY.md.


Can not click Add query

Describe the bug
I can not click the Add query button from the Docs panel to add query to the query panel.
Pleasse help.
To Reproduce
Steps to reproduce the behavior:

Go to Docs panel
Click on 'Add query' (red box in the attached image)
Nothing happen in the query panel

Expected behavior
The query from docs panel should automatically be added to the query panel
Screenshots

Desktop (please complete the following information):

OS: Windows 10 ver 21H1
Platform: desktop app
Version <IP_ADDRESS>

Unfortunately that is not sufficient information. Can you check the developer tools console (similar to Google chrome since it's an electron app) if there are any errors?

Unfortunately that is not sufficient information. Can you check the developer tools console (similar to Google chrome since it's an electron app) if there are any errors?

Thanks, here is the error from developer console:

Seems I'd need to update the graphql package to the latest version

Seems I'd need to update the graphql package to the latest version

May I ask when it will be available?

This should have been fixed by now. Feel free to comment on this issue again if it hasn't.

I still encounter an error when retrieve Graphql Docs

Can you share the schema you're having issues with?

Oh I found the problem, the endpoint Graphql does not allow public query.
It's working now. Thanks!


test(PersonaWrap): add smoke visual tests

maybe like a https://github.com/gravity-ui/uikit/pull/1776

https://github.com/gravity-ui/uikit/pull/2021

component will be deleted


[Bug]:

Search for answers in existing issues

[X] I have searched issues, there is no issue related to the problem I encountered

Python version
python 3.8
Issue description

config set the use_azure api = true, however still request an openai endpoint.
my azure endpoint is like https://xxxxx.openai.azure.com/openai/deployments/chatbot/chat/completions?api-version=2023-03-15-preview
Repro steps
No response
Relevant log output
No response

According to your screenshot, openai_api_base and model are empty, and yet they need to be filled with valid values to make azure service work.


Run in release mode, compile error report Undefined symbol: _rust_greeting

I know this problem has been raised by many people, but I also followed the solution they said, but it did not solve the problem.
Flutter 1.25.0-8.3.pre • channel beta • https://github.com/flutter/flutter.git
Framework • revision 5d36f2e7f5 (3 weeks ago) • 2021-01-14 15:57:49 -0800
Engine • revision 7a8f8ca02c
Tools • Dart 2.12.0 (build 2.12.0-133.7.beta)

I first clone the project by executing the command:
git clone https://github.com/brickpop/flutter-rust-ffi

Then when debugging, an error occurred, I deleted the project IOS folder and executed the following command:
flutter create .

At this time, the debugging operation was successful, but it failed when it was released. The error screenshot is as follows
Then, I found the following information to solve this problem, but it didn't work after trying.
https://github.com/brickpop/flutter-rust-ffi/issues/7
https://github.com/dart-lang/ffi/issues/41
https://github.com/shekohex/flutterust/issues/17

In Xcode, go to Target Runner > Build Settings > Strip Style.
Change from All Symbols to Non-Global Symbols.

Test result: No
https://github.com/dart-lang/ffi/issues/41#issuecomment-751496383
enable testability.

Test result: No

https://github.com/brickpop/flutter-rust-ffi/issues/16 might be the one relevant here.
The STRIP_STYLE setting may not be needed on the Flutter project, but on the plugin project you export (Pod spec file)

brickpop/flutter-rust-ffi#16 might be the one relevant here.
The STRIP_STYLE setting may not be needed on the Flutter project, but on the plugin project you export (Pod spec file)

I found the solution:
Step 1:
When publishing, it must be tested on a real machine, otherwise it will prompt that "Module'mylib" is not found
Step 2:
Find "Architectures" in "Build Seetings" and make the following modifications

XCode's default "standard architecture (arm64, armv7)" and ".a" files do not contain "armv7", and the new version of Rust has eliminated armv7.
I am a little depressed. Before I went to bed, I could still publish my work normally, but when I was preparing for the Pull Request the next day, a new problem appeared.
After compilation, after the new version is released, the application will be grayed out.

Apple is currently supporting arm64 and x86_64 only. If your app is targeting iOS 9 or earlier, then you'd need to compile the static library for armv7, but the amount of people still using iphone 5 in 2021 is negligible I think.
The greyed out problem is new to me :(

Hey @Aaron009 if this solution worked well for you, could you please add these steps to the flutterust README? it would be appreciated

@brickpop @brickpop
Regarding the gray screen of running App after release, I solved it by recreating the Flutter plug-in project.


Hesai pandar 40M--No transform to fixed frame [map]

I play the bag file which was collected by Hesai laser pandar 40M, and I get nothing in rviz. There is also a error in rviz For frame [base_link]: No transform to fixed frame [map]. TF error: [Could not find a connection between 'map' and 'base_link' because they are not part of the same tree. Tf has two or more unconnected trees.]
I changed the topic in utility.h and those parameters you had mentioned in https://github.com/RobustFieldAutonomyLab/LeGO-LOAM/issues/3.
I also uncomment line 159 and catkin_make again. Nothing changes.
How can I fix this problem?

have you fixed the problem? I add tf trans, but it still did not work.

My wechat account:
xxp18500728702
---Original---
From: "Siyuan @.>
Date: Wed, May 26, 2021 00:39 AM
To: @.>;
Cc: @.>;"State @.>;
Subject: Re: [RobustFieldAutonomyLab/LeGO-LOAM] Hesai pandar 40M--No transform to fixed frame [map] (#221)
have you fixed the problem? I add tf trans, but it still did not work.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.

那行不要注释，把hesailidar的launch里面timestamp_type的默认值改为realtime


[Bug]: Inconsistent Results for Overlapping AOIs

I am writing to bring to your attention  that I have encountered while working with different AOIs that have an overlap area. I have performed tests using the same scenes and parameters with SBAS, yet I am receiving different results for the overlapping regions.
AOI area is 10kmx20km with buffer 0.02, overlaped area is 4km
Despite these efforts to maintain consistency, the results for the overlapping areas are diverging.
Is SBAS suitable for analyzing small surfaces, considering the significant difference observed in deformation results on a particular surface? If applicable, how can one determine which set of results from SBAS analysis should be considered more trustworthy when encountering such variations?
Screenshots

Two diff AOI with OverLaps

Results from two diff AOI

See difference in zoom, gradient of color is for  same values

for same point i create charts with LOS displacement and also STL,  see

System and software version:

OS: Docker, latest pygmtsar
GMTSAR version: Latest

SBAS results depend on unwrapping accuracy, and we need to control it effectively. This involves detrending, removing atmospheric phase, and other steps, including the removal of excessively noisy interferograms.
For example, let's compare these unwrapped interferograms where no visible patterns are apparent:

Now, take a look at the cleaned ones, where you can easily recognize a subsidence area at the center:

SBAS Phase, [rad]0-100

SBAS Trend Phase, [rad]0-100

SBAS Phase - Trend, [rad]0-100.

Histogram for Standard Deviation with Mean and Std Lines - pairs_best.jpg

SBAS Best Pairs Quality

Your detrended phases are very noisy because you don't check the connected components map. Use unwrapping without a correlation threshold to unwrap all the pixels and prevent disconnected areas.

i will try with out correlation threshold !


Inject don't work for my all friends

Hello! I have a big problem with cheat. I inject for me without any problems, i give the friends my dll cheat end don't inject. How to fix this?

#519


Get full filenames?

I get in response not full filenames; it breaks my logic- for one file its "test1.js" - for Tern test files its "test/util.js". How to get full pathed filenames in response?
Or how to expand partial filenames?
(i use autocomplete, go-to-definition)

You get project-relative path names, so prefix the project dir, and you've got an absolute path name.


pysteps.io with xarray

Include new xarray-based data model into the pysteps.io module (See #12).
The imported data are converted into an xarray Dataset by means of a decorator.
See below for an example using MeteoSwiss data.
> precip_ds = pysteps.io.import_mch_gif(filename, "AQC", 5.0)
> precip_ds.info()

xarray.Dataset {
dimensions:
        y = 640 ;
        x = 710 ;

variables:
        float64 precipitation(y, x) ;
                precipitation:standard_name = precipitation_rate ;
                precipitation:long_name = Precipitation product ;
                precipitation:product = AQC ;
                precipitation:unit = mm ;
                precipitation:accutime = 5.0 ;
                precipitation:transform = None ;
                precipitation:zerovalue = 0.0 ;
                precipitation:threshold = 0.0009628129986471908 ;
                precipitation:zr_a = 316.0 ;
                precipitation:zr_b = 1.5 ;
        float64 x(x) ;
                x:standard_name = projection_x_coordinate ;
                x:units = m ;
        float64 y(y) ;
                y:standard_name = projection_y_coordinate ;
                y:units = m ;

// global attributes:
        :institution = MeteoSwiss ;
        :projection = +proj=somerc  +lon_0=7.43958333333333 +lat_0=46.9524055555556 +k_0=1 +x_0=600000 +y_0=200000 +ellps=bessel +towgs84=674.374,15.056,405.346,0,0,0,0 +units=m +no_defs ;
}

the same for a BOM file:
xarray.Dataset {
dimensions:
        y = 512 ;
        x = 512 ;

variables:
        float64 precipitation(y, x) ;
                precipitation:standard_name = precipitation_rate ;
                precipitation:long_name = Precipitation product ;
                precipitation:product = None ;
                precipitation:unit = mm ;
                precipitation:accutime = 6 ;
                precipitation:transform = None ;
                precipitation:zerovalue = 0.0 ;
                precipitation:threshold = 0.05 ;
                precipitation:zr_a = None ;
                precipitation:zr_b = None ;
        float64 x(x) ;
                x:standard_name = projection_x_coordinate ;
                x:units = m ;
        float64 y(y) ;
                y:standard_name = projection_y_coordinate ;
                y:units = m ;

// global attributes:
        :institution = Commonwealth of Australia, Bureau of Meteorology ;
        :projection = +proj=aea  +lon_0=144.752 +lat_0=-37.852 +lat_1=-18.000 +lat_2=-36.000 ;
}

edit: limit the scope of this PR to the io module only.

Spontaneous questions:

should we use "precipitation" to name the main variable? Can we make it more general so that to make it clear that other variables can be used (e.g. cloud cover)?
we should revise the metadata to better align them to CF standards and other libraries used for radar data processing (e.g. wradlib).

"units" instead of "unit"
remove any metadata that can be easily derived from the data (e.g. threshold, zerovalue)
...

Spontaneous responses:

* should we use "precipitation" to name the main variable? Can we make it more general so that to make it clear that other variables can be used (e.g. cloud cover)?

at this point I believe that "precipitation" is a good choice, but I agree that we may have other cases such "rain_rate"

* we should revise the metadata to better align them to CF standards and other libraries used for radar data processing (e.g. wradlib).

Yes ... it is better to follow CF standards as xarray use them as well
but I would prefer to keep key metadata in the structure as parameters of the variable ... because those metadata that initially would easily derived from the data may be lost after a number of data transformations, or they could not be that easy to derive, for example if radar field is full of non zero_values then how the zero_value can be derived?

OK, for the moment I decided to return a DataArray instead of a Dataset (hence ignoring the quality field, which we never used anyway). This way, we remain agnostic in what variable we are reading (could be anything).
 <xarray.DataArray (y: 640, x: 710)>
array([[nan, nan, nan, ..., nan, nan, nan],
       [nan, nan, nan, ..., nan, nan, nan],
       [nan, nan, nan, ..., nan, nan, nan],
       ...,
       [nan, nan, nan, ..., nan, nan, nan],
       [nan, nan, nan, ..., nan, nan, nan],
       [nan, nan, nan, ..., nan, nan, nan]])
Coordinates:
  * x        (x) float64 2.555e+05 2.565e+05 2.575e+05 ... 9.635e+05 9.645e+05
  * y        (y) float64 -1.595e+05 -1.585e+05 ... 4.785e+05 4.795e+05
Attributes:
    unit:         mm
    accutime:     5.0
    transform:    None
    zerovalue:    0.0
    threshold:    0.0009628129986471908
    zr_a:         316.0
    zr_b:         1.5
    institution:  MeteoSwiss
    projection:   +proj=somerc  +lon_0=7.43958333333333 +lat_0=46.95240555555...

I was thinking that it would make more sense if the DataArray would include a singleton "t" dimension with the timestamp of the radar image, what you think?

my personal preference is to use Dataset from source input as stores together multiple variables, like 'precipitation' and 'projection' information. The 'main/interset' variable always can be selected from the Dataset before to pass into pySTEPS routines.
Also, "time" should be a coordinate as that is what really differentiate one radar field from other one (assuming that all of them share common metadata for all time steps)  ... also using 'time' as coordinate helps to open and concatenate multiple radar files using xarray.open_mfdataset

I see your point concerning the dataset, @cvelascof, and this could be easily implemented for importers. I just wonder the need for datasets when we mostly work with single variables (radar precip). One can always build a new dataset when needed (adding NWP data for example).
And do we need an extra variable for the projection? I've seen it done before for netcdfs, but we could try to simplify this by adopting EPSG codes, at which point it would be enough to add a crs=EPSG:xxxx attribute. What do you think?
also most of our methods work on single arrays, and thus the migration on xarrays would be easier on DataArrays. Also, we shouldn't make any assumption on the name of the variables.
One possible solution could be to return a dataset when importing but then the user would have to pass the variable of interest to a given method, for example:
ds = pysteps.io.read_timeseries() # or xr.open_mfdataset()
precip = ds.precip.pysteps.to_rainrate()
motion = pysteps.motion.dense_lucaskanade(precip)

That could work, @dnerini (thanks for all the work, by the way)! We only should not forget to change that in the examples in that case (to avoid confusion).
@cvelascof, does projection need to be a variable? I.e., can't it just be an attribute as in @dnerini's example?
I find it hard to judge whether we need to move to DataArrays or -Sets. As @dnerini pointed out, we generally work with single arrays. What I can imagine with our move towards blending and perhaps later machine learning techniques, is that we want to involve (at some point..) more variables than just precipitation. If the information originates from one dataset, e.g. the NWP model, it may be a bit double to import that in multiple DataArrays that contain similar grid, time and metadata information. However, either way will work and I think we just have to decide on what we see as both a clearer and cleaner method. I personally have no preference.

This PR is by no means definitive, but should be seen instead as a first step to integrate the xarray data model into pysteps. I suggest we merge it pretty soon and advance in other modules, knowing that we will anyway have to come back to the io to make more adjustments before V2 will be ready.

Great work @dnerini! I agree that we should merge it soon and advance in other modules.
I pushed two commits that add a temporary "legacy" option to allow the importers and readers to behave as in version 1. Also, the tests that are still written for v1, were updated to use this new legacy option. The tests that couldn't be easily fix were manually skipped and tagged with a TODO message. This legacy option will allow maintaining the testing functionality through the migration to xarray.

Ah very nice @aperezhortal , thanks! Looks like tests are now failing because of missing dependencies. I'll cherry-pick commit b4c165ade1f31fb7567457a6bd95686702d8f70a to fix it as soon as possible (should have some time this afternoon).


deny_unknown_fields docs misleading

Code below.
I found a use case where deserializing to structs within an enum of structs can create a problem.
When deserializing a json file as the following:
{
    "current_user_prompt": {
        "type": "share-credentials",
        "client_name": "example.com",
        "logo_uri": null,
        "options": [
          "37626466-3738-6437-6165-623533613665"
        ]
    }
}

It would actually deserialize to the struct PasswordRequired before I added the deny_unknown _fields attribute.
Firstly, I found a quick fix by changing the order in the enum, putting PasswordRequired last.
This indicates the deserializer goes to the CurrentUserPrompt enum and, as expected, checks the json content with the structs one by one from first to last. As it is allowed to throw away unknown fields by default, the obvious ShareCredential struct in the json file was deserialized to the simpler PasswordRequired struct with the same first field and the rest of the fields were thrown away.
So finally the deny_unknown_fields attribute was the solution. But the docs did throw me off at first.
"
Always error during deserialization when encountering unknown fields. When this attribute is not present, by default unknown fields are ignored for self-describing formats like JSON.
Note: this attribute is not supported in combination with flatten, neither on the outer struct nor on the flattened field.
"
I would suggest changing the first two words "Always error..." which definitely deterred me from using this solution at first, the only one that works as far as I know. Perhaps "Forces deserialization to find a match for all fields, otherwise it will error.". In a sense it's logical that it will keep looking for the right struct in the enum. Yet still I think the docs do not hint at this whatsoever, which was misleading for me.
use serde::{Deserialize, Serialize};
use ts_rs::TS;

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/Redirect.ts")]
#[serde(deny_unknown_fields)]
pub struct Redirect {
    pub r#type: CurrentUserPromptType,
    pub target: String,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/Warning.ts")]
#[serde(deny_unknown_fields)]
pub struct Warning {
    pub r#type: CurrentUserPromptType,
    pub message: String,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/Selection.ts")]
#[serde(deny_unknown_fields)]
pub struct Selection {
    pub r#type: CurrentUserPromptType,
    /// An option is in the form: (<option_name>, <option_value>)
    // pub options: Vec<(String, String)>,
    pub options: Vec<String>,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/CredentialOffer.ts")]
#[serde(deny_unknown_fields)]
pub struct CredentialOffer {
    pub r#type: CurrentUserPromptType,
    pub issuer_name: String,
    pub logo_uri: Option<String>,
    #[ts(type = "object")]
    pub credential_offer: serde_json::Value,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/PasswordRequired.ts")]
#[serde(deny_unknown_fields)]
pub struct PasswordRequired {
    pub r#type: CurrentUserPromptType,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/AcceptConnection.ts")]
#[serde(deny_unknown_fields)]
pub struct AcceptConnection {
    pub r#type: CurrentUserPromptType,
    pub client_name: String,
    pub logo_uri: Option<String>,
    pub redirect_uri: String,
    pub previously_connected: bool,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/ShareCredentials.ts")]
#[serde(deny_unknown_fields)]
pub struct ShareCredentials {
    pub r#type: CurrentUserPromptType,
    pub client_name: String,
    pub logo_uri: Option<String>,
    pub options: Vec<String>,
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[serde(untagged)]
#[ts(export, export_to = "bindings/user-prompt/CurrentUserPrompt.ts")]
pub enum CurrentUserPrompt {
    Redirect(Redirect),
    Warning(Warning),
    Selection(Selection),
    CredentialOffer(CredentialOffer),
    PasswordRequired(PasswordRequired),
    AcceptConnection(AcceptConnection),
    ShareCredentials(ShareCredentials),
}

#[derive(Clone, Serialize, Deserialize, Debug, TS, PartialEq)]
#[ts(export, export_to = "bindings/user-prompt/CurrentUserPromptType.ts")]
pub enum CurrentUserPromptType {
    #[serde(rename = "redirect")]
    Redirect,
    // TODO: remove or rename generic warning
    #[serde(rename = "warning")]
    Warning,
    #[serde(rename = "accept-connection")] // SIOPv2
    AcceptConnection,
    #[serde(rename = "share-credentials")] // VP
    ShareCredentials,
    #[serde(rename = "credential-offer")]
    CredentialOffer,
    #[serde(rename = "password-required")]
    PasswordRequired,
}

I think that’s a duplicate of #2384.

Although my example doesn't include flatten, it more or less comes down to the same point I think yes: This attribute is very useful in a range of scenario's but the docs make it seem fit only for a very specific use-case.


Comparing arrays of different dtype kinds

In array-api-strict, I've had this behavior
>>> import array_api_strict as xp
>>> xp.asarray(0, dtype=xp.int64) < xp.asarray(1, dtype=xp.uint64)
TypeError: array_api_strict.int64 and array_api_strict.uint64 cannot be type promoted together

However, this is very annoying, as it makes it basically impossible to compare uint64 and int64. However, I noticed that the standard doesn't actually say anywhere that the inputs to greater/__gt__ need to be type-promotable, only that they should be real numeric. So from my reading of the standard, even comparing integers and floats should be allowed (but not complex numbers or booleans).
That's all good and fine, and I'm going to update array-api-strict. The only question there is whether the standard should be more explicit about this, or if the current wording is OK. It might also be a good idea to update the wording to explicitly state that the comparison should be based on the full values of the operands. There was an issue in NumPy pre-2.0 where < sometimes gave wrong answers because it would downcast float64 to float32, leading to a wrong answer if the rounding went wrong. In other words, the types should promote (or virtually promote) internally before comparing. I actually don't know if all libraries handle the uint64/int64 case correctly since it isn't tested in the test suite. I know NumPy has historically promoted those types to float64, which is dumb since float64 can't even represent the maximum int64. I suppose one could also consider cases of Python int scalars that are very large which should probably compare without doing an overflowing cast, but this could also be treated as unspecified.
The main question I had is with equal/== and not_equal/!=. For those functions, the standard only says the inputs can be "any data type" https://data-apis.org/array-api/latest/API_specification/generated/array_api.equal.html#equal. This implies, by the above reasoning, that comparing any two arrays of any two data types should be allowed. But this implies things like comparing complex arrays to real arrays, and comparing booleans to integers. It might be a good idea to clarify either whether this should not be allowed (or implementation defined), or if it is allowed, how these different types compare to one another. We can probably reuse some other text, for instance, the text at https://data-apis.org/array-api/latest/API_specification/generated/array_api.array.bool.html#bool for comparing with a bool array and the text at https://data-apis.org/array-api/latest/API_specification/generated/array_api.array.complex.html#complex for comparing with a complex array.

The agreement from the meeting Thursday is that cross-kind comparison should be undefined.
Perhaps unsurprisingly, PyTorch does not allow comparing int64 and uint64:
>>> torch.asarray(9223372036854775807, dtype=torch.int64) < torch.asarray(18446744073709551615, dtype=torch.uint64)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
RuntimeError: Promotion for uint16, uint32, uint64 types is not supported, attempted to promote Long and UInt64

PyTorch only has partial support for uint64 anyways. So it's maybe not the best point of comparison. I wonder if CuPy and other libraries do the right thing.

https://github.com/data-apis/array-api/pull/822

FWIW the RuntimeError of https://github.com/data-apis/array-api/issues/819#issuecomment-2229503135 seems to be a torch bug / artifact of incomplete uintN (N> 8) support. (until very recently, torch only had uint8).
With uint8, pytorch behavior is consistent with numpy and the rest of the ecosystem:
>>> torch.asarray([9223372036854775807], dtype=torch.int64) < torch.asarray([1], dtype=torch.uint8)
tensor([False])
>>> np.asarray(9223372036854775807, dtype=np.int64) < np.asarray(18446744073709551615, dtype=np.uint64)
np.True_

Mixed comparisons with integer/fp types are also OK in torch:
>>> torch.asarray([9223372036854775807], dtype=torch.int64) < torch.asarray([1], dtype=torch.float16)
tensor([False])
>>>
>>> torch.asarray([9223372036854775807], dtype=torch.uint64) < torch.asarray([1], dtype=torch.float16)
tensor([False])

So all in all disallowing this in array_api_strict on the grounds of a pytorch definiciency seems too strict IMO.


Documentation of MessageObject "deprecated" property

Describe the bug
The schema of the MessageObject contains a deprecated property. This property is not included in the MessageObject documentation or the markdown. Shouldn't it be though?

/help

@KhudaDad414 have a look, I luckily made it stop 😆

Also, when fixing can you also improve below message. My bot complains it is not much positive, probably because of wrong

/help


GPTQ Env vars: catch correct type of error

What does this PR do?
When passing in environment variables like gptq_bits, we still get errors thrown from TGI because the try/catch block is catching the wrong type of error. This PR aims to fix that.
@Narsil - let me know if this is how you want this formatted. My Python is a little shaky, so I hope this syntax is correct.

Can you provide an example of model where this error is triggered instead ?I 'm very surprised that this error could be raised.

100% !
Catching and reraising at its best...

Merging, tests are red because you don't have access to our secrets.

@olivier FYI

Quick update, I've got a model in a private repo that I quantized with GPTQ-for-Llama that triggers this reliably. That's here: https://huggingface.co/ssmi153/student-feedback-llama-30b-guanaco-2023-07-03-final-gptq and I can DM over a HuggingFace token to give you access to it (probably shouldn't put that out in public though!).
I've been trying to find other public GPTQ model files that do it too, but for all of TheBloke's conversions I run into another issue:
2023-07-12T10:57:26.137426358-07:00 {"timestamp":"2023-07-12T17:57:26.137143Z","level":"ERROR","fields":{"message":"Error when initializing model\nTraceback (most recent call last):\n  File \"/opt/conda/bin/text-generation-server\", line 8, in <module>\n    sys.exit(app())\n  File \"/opt/conda/lib/python3.9/site-packages/typer/main.py\", line 311, in __call__\n    return get_command(self)(*args, **kwargs)\n  File \"/opt/conda/lib/python3.9/site-packages/click/core.py\", line 1130, in __call__\n    return self.main(*args, **kwargs)\n  File \"/opt/conda/lib/python3.9/site-packages/typer/core.py\", line 778, in main\n    return _main(\n  File \"/opt/conda/lib/python3.9/site-packages/typer/core.py\", line 216, in _main\n    rv = self.invoke(ctx)\n  File \"/opt/conda/lib/python3.9/site-packages/click/core.py\", line 1657, in invoke\n    return _process_result(sub_ctx.command.invoke(sub_ctx))\n  File \"/opt/conda/lib/python3.9/site-packages/click/core.py\", line 1404, in invoke\n    return ctx.invoke(self.callback, **ctx.params)\n  File \"/opt/conda/lib/python3.9/site-packages/click/core.py\", line 760, in invoke\n    return __callback(*args, **kwargs)\n  File \"/opt/conda/lib/python3.9/site-packages/typer/main.py\", line 683, in wrapper\n    return callback(**use_params)  # type: ignore\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/cli.py\", line 78, in serve\n    server.serve(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/server.py\", line 175, in serve\n    asyncio.run(\n  File \"/opt/conda/lib/python3.9/asyncio/runners.py\", line 44, in run\n    return loop.run_until_complete(main)\n  File \"/opt/conda/lib/python3.9/asyncio/base_events.py\", line 634, in run_until_complete\n    self.run_forever()\n  File \"/opt/conda/lib/python3.9/asyncio/base_events.py\", line 601, in run_forever\n    self._run_once()\n  File \"/opt/conda/lib/python3.9/asyncio/base_events.py\", line 1905, in _run_once\n    handle._run()\n  File \"/opt/conda/lib/python3.9/asyncio/events.py\", line 80, in _run\n    self._context.run(self._callback, *self._args)\n> File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/server.py\", line 142, in serve_inner\n    model = get_model(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/__init__.py\", line 215, in get_model\n    return FlashLlama(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/flash_llama.py\", line 65, in __init__\n    model = FlashLlamaForCausalLM(config, weights)\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 371, in __init__\n    self.model = FlashLlamaModel(config, weights)\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 310, in __init__\n    [\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 311, in <listcomp>\n    FlashLlamaLayer(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 246, in __init__\n    self.self_attn = FlashLlamaAttention(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/models/custom_modeling/flash_llama_modeling.py\", line 121, in __init__\n    self.query_key_value = TensorParallelColumnLinear.load_multi(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/layers.py\", line 251, in load_multi\n    weight = weights.get_multi_weights_col(\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/weights.py\", line 125, in get_multi_weights_col\n    w = [self.get_tensor(f\"{p}.g_idx\") for p in prefixes]\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/weights.py\", line 125, in <listcomp>\n    w = [self.get_tensor(f\"{p}.g_idx\") for p in prefixes]\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/weights.py\", line 62, in get_tensor\n    filename, tensor_name = self.get_filename(tensor_name)\n  File \"/opt/conda/lib/python3.9/site-packages/text_generation_server/utils/weights.py\", line 49, in get_filename\n    raise RuntimeError(f\"weight {tensor_name} does not exist\")\nRuntimeError: weight model.layers.0.self_attn.q_proj.g_idx does not exist\n"},"target":"text_generation_launcher","span":{"rank":0,"name":"shard-manager"},"spans":[{"rank":0,"name":"shard-manager"}]}
This is from this model: https://huggingface.co/TheBloke/orca_mini_v2_7B-GPTQ
It's also a conversion using GPTQ-for-Llama so should be broadly compatible. Here's the quantization config:

{
| "bits": 4,
  | "group_size": 128,
  | "damp_percent": 0.01,
  | "desc_act": false,
  | "sym": true,
  | "true_sequential": true
  | }

Is this incompatibility due to the desc_act = false, or something else?

Annnnd this is why I don't particularly enjoy maintaining external models...
I'm not sure I have the bandwidth to really investigate an escape hatch.

@Narsil , I worked out how to get at least some of the quantised versions of TheBloke’s conversions working which is good news. Take a look at https://github.com/huggingface/text-generation-inference/issues/601 where I’ve added more details.


Issue #1060 New Page for Semester Recap/Year Recap Added

Issue #1060 has been addressed - I have added the 'New Page for Semester Recap/Year Recap" as sem_temp.html. There is still some issues with the .untitled-shutters overflowing below the recap space on my end, but kindly let me know what I can improve or work on further, if at all! Thank you very much. @anushbhatia @smaranjitghose

.

Hi @smaranjitghose @anushbhatia thank you so much for merging the pr and for all your amazing tips!! I will definitely take all your valuable tips into account and make a second pr fixing all these changes by next week!! Thanks again!! 😇


Doesn't support RxSwift 4.0

Hi,
It seems that this extension hasn't been updated to RxSwift 4.0
Could this be done?
Thanks!

@sergdort when you can you could push a new spec for this version 2?

The new RxSwift 4.0 support of this library is not supported on CocoaPods :/

@Azogord just direct your Podfile directly to this repo until there’s a new Podspec live

Didn't know that was possible, thanks 👍

@Azogord Insert pod 'RxSegue', :git => 'https://github.com/RxSwiftCommunity/RxSegue.git'


1,07GB file bug ?

Hi, when I use aviglitch and command $ datamosh, it always cut my avi file to 1,07GB. Whatever if it is 3GB fil source, 4GB or more... So I don't think it is related to the 32Bits 4,7GB avi limit. Config is Mac Os Yosemite and files are between 4K and 6K, x264 100mbps (less than 1' and 2 or 3 cuts max). Regards, IJC

same in osx sierra

Slice your file with ffmpeg

En ligne Impressions, 2012, 48' https://vimeo.com/38519895
Jacques Perconte
+33 660 615 408
http://www.jacquesperconte.com
→ http://timeline.technart.fr / news
→ https://twitter.com/jacquesperconte / voix
Le 30 janv. 2017 à 15:13 +0100, 12georgiadis<EMAIL_ADDRESS>a écrit :

same in osx sierra
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub (https://github.com/ucnv/aviglitch/issues/2#issuecomment-276072125), or mute the thread (https://github.com/notifications/unsubscribe-auth/AN3ekwDCt-N44Ujq0S9Sj9cYUdlgVyGBks5rXfASgaJpZM4LxW8t).

Thanks for the tip, I forgot that there was this function in ffmpeg

ffmpeg -i "input.avi" -acodec copy -f segment -segment_time 120 -vcodec
copy -reset_timestamps 1 -map 0 output%2d.avi
;)
j.
☀
En ligne Impressions, 2012, 48' https://vimeo.com/38519895
Jacques Perconte
+33 660 615 408
http://www.jacquesperconte.com
→ http://timeline.technart.fr / news
→ https://twitter.com/jacquesperconte / voix
On Mon, Jan 30, 2017 at 10:34 PM, 12georgiadis<EMAIL_ADDRESS>wrote:

Thanks for the tip, I forgot that there was this function in ffmpeg
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ucnv/aviglitch/issues/2#issuecomment-276198156, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AN3ekyPVtzoTMdNI4sKCHyk_wlxP9XoNks5rXldYgaJpZM4LxW8t
.

Great! I'll give a try with these main options command. Good news is that I can even improve the bitrate to be closer to the raw footage. Many thx, I

There is always a solution +
j.
http://www.jacquesperconte.com
→ http://timeline.technart.fr / news
→ https://twitter.com/jacquesperconte / voix
On Tue, Jan 31, 2017 at 9:39 AM, 12georgiadis<EMAIL_ADDRESS>wrote:

Great! I'll give a try with these main options command. Good news is that
I can even improve the bitrate to be closer to the raw footage. Many thx, I
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/ucnv/aviglitch/issues/2#issuecomment-276305330, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AN3ek4pnK8vqZqkPRy1Hw8LQ6Z3FlaOwks5rXvNBgaJpZM4LxW8t
.

Hi @12georgiadis
Over 4 years passed since you reported this issue...!
I have released new version of the library which should solve this issue.
The problem was that this library didn't support the advanced AVI format which is generally called AVI2.0.
In the latest version it was totally refined to handle AVI 2.0 files.
And now we finally can process the files larger than 1GB.
Please check the new version of AviGlitch (if you're still in there)...!
Also thank @jacques-perconte for the conversation.


Committee System Implemented

Members must be able to apply to committees.
They would then get accepted or rejected by the person in charge of the committee.
This would award them points if they get accepted. The amount should be editable by the eBoard.
This should also add some privilege to them so they can see things from that committee such as announcements and such

duplicate issue


split properties and change backend initlocation for E83001

Details:

item1
...

Tickets:

ticket-id

CID compile_tool failed:

benchmark CID:
root@IRL-MTL-P-231:~/WORK/ld/bin_83001# ./compile_tool -m ../testConfigandData/add_abc.xml -d NPU
OpenVINO Runtime version ......... 2024.2.0
Build ........... 2024.2.0-15456-f1fd91ce88a-test_draft_dry_on
Parsing command-line arguments
Checking FLAGS_LOG_LEVEL
Reading model
Performing reshape
Configuring model pre & post processing
Printing Input and Output Info from model
Network inputs:
    A : f32 / [...] / [1]
    B : f32 / [...] / [1]
    C : f32 / [...] / [1]
Network outputs:
    Y/sink_port_0 : f32 / [...] / [1]
Parsing configuration file
Compiling model
=========check 1==========
=========check 2========== lMY,
=========check 4======get_property name=SUPPORTED_PROPERTIES,
=========check 4======get_property name=INTERNAL_SUPPORTED_PROPERTIES,
=========check 3========== MY,
=========check 4======get_property name=SUPPORTED_PROPERTIES,
=========check 5======compile_model(1),
=========check 6==========compile_model(2)
=========check 8==========compile_model(4)
[WARNING] 10:00:12.492 [NPUPlugin] not init backend. it is ok for compilation only, so not apply set_batch_config()
[WARNING] 10:00:12.492 [NPUPlugin] not init backend. device for empty. incompildation inference, need to update device!!s
=========check 9==========compile_model(5)
=========check 9==========compiledmodel(5)
=========check 4======get_property name=EXCLUSIVE_ASYNC_REQUESTS,
Writing into file - add_abc.blob
Done. LoadNetwork time elapsed: 142 ms
root@IRL-MTL-P-231:~/WORK/ld/bin_83001# ./benchmark_app -m ../testConfigandData/add_abc.xml -d NPU
[Step 1/11] Parsing and validating input arguments
[ INFO ] Parsing input parameters
[Step 2/11] Loading OpenVINO Runtime
[ INFO ] OpenVINO:
[ INFO ] Build ................................. 2024.2.0-15456-f1fd91ce88a-test_draft_dry_on
[ INFO ]
[ INFO ] Device info:
=========check 1==========
=========check 2========== {XV,
=========check 4======get_property name=SUPPORTED_PROPERTIES,
=========check 4======get_property name=INTERNAL_SUPPORTED_PROPERTIES,
=========check 3========== {XV,
[ INFO ] NPU
[ INFO ] Build ................................. 2024.2.0-15456-f1fd91ce88a-test_draft_dry_on
[ INFO ]
[ INFO ]
[Step 3/11] Setting device configuration
=========check 4======get_property name=SUPPORTED_PROPERTIES,
[ WARNING ] Performance hint was not explicitly specified in command line. Device(NPU) performance hint will be set to THROUGHPUT.
=========check 4======get_property name=SUPPORTED_PROPERTIES,
[Step 4/11] Reading model files
[ INFO ] Loading model files
[ INFO ] Read model took 3.95 ms
[ INFO ] Original model I/O parameters:
[ INFO ] Network inputs:
[ INFO ]     A (node: A) : f32 / [...] / [1]
[ INFO ]     B (node: B) : f32 / [...] / [1]
[ INFO ]     C (node: C) : f32 / [...] / [1]
[ INFO ] Network outputs:
[ INFO ]     Y (node: Y) : f32 / [...] / [1]
[Step 5/11] Resizing model to match image sizes and given batch
[ WARNING ] A: layout is not set explicitly. It is STRONGLY recommended to set layout manually to avoid further issues.
[ WARNING ] B: layout is not set explicitly. It is STRONGLY recommended to set layout manually to avoid further issues.
[ WARNING ] C: layout is not set explicitly. It is STRONGLY recommended to set layout manually to avoid further issues.
[Step 6/11] Configuring input of the model
[ WARNING ] No batch dimension was found, asssuming batch to be 1. Beware: this might affect FPS calculation.
[ INFO ] Model batch size: 1
[ INFO ] Network inputs:
[ INFO ]     A (node: A) : f32 / [...] / [1]
[ INFO ]     B (node: B) : f32 / [...] / [1]
[ INFO ]     C (node: C) : f32 / [...] / [1]
[ INFO ] Network outputs:
[ INFO ]     Y (node: Y) : f32 / [...] / [1]
[Step 7/11] Loading the model to the device
=========check 4======get_property name=SUPPORTED_PROPERTIES,
=========check 5======compile_model(1),
=========check 6==========compile_model(2)
=========check 8==========compile_model(4)
[WARNING] 10:01:13.653 [NPUPlugin] not init backend. it is ok for compilation only, so not apply set_batch_config()
[WARNING] 10:01:13.653 [NPUPlugin] not init backend. device for empty. incompildation inference, need to update device!!s
=========check 9==========compile_model(5)
=========check 9==========compiledmodel(5)
=========check 4======get_property name=EXCLUSIVE_ASYNC_REQUESTS,
[ INFO ] Compile model took 153.51 ms
[Step 8/11] Querying optimal runtime parameters
[ INFO ] Model:
[ INFO ]   DEVICE_ID:
[ INFO ]   ENABLE_CPU_PINNING: NO
[ INFO ]   EXECUTION_DEVICES: NPU
[ INFO ]   EXECUTION_MODE_HINT: PERFORMANCE
[ INFO ]   INFERENCE_PRECISION_HINT: f16
[ INFO ]   LOADED_FROM_CACHE: NO
[ INFO ]   MODEL_PRIORITY: MEDIUM
[ INFO ]   NETWORK_NAME:
[ INFO ]   OPTIMAL_NUMBER_OF_INFER_REQUESTS: 8
[ INFO ]   PERFORMANCE_HINT: THROUGHPUT
[ INFO ]   PERFORMANCE_HINT_NUM_REQUESTS: 1
[ INFO ]   PERF_COUNT: NO
[Step 9/11] Creating infer requests and preparing input tensors
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
=========check 9==========compiledmodel -- create_infer_request(6)
[ WARNING ] No input files were given: all inputs will be filled with random values!
[ INFO ] Test Config 0
[ INFO ] A  ([...], f32, [1], static):  random (binary data/numpy array is expected)
[ INFO ] B  ([...], f32, [1], static):  random (binary data/numpy array is expected)
[ INFO ] C  ([...], f32, [1], static):  random (binary data/numpy array is expected)
[Step 10/11] Measuring performance (Start inference asynchronously, 8 inference requests, limits: 60000 ms duration)
[ INFO ] Benchmarking in inference only mode (inputs filling are not included in measurement loop).
[ INFO ] First inference took 3.68 ms
[Step 11/11] Dumping statistics report
[ INFO ] Execution Devices: [ NPU ]
[ INFO ] Count:               612576 iterations
[ INFO ] Duration:            60001.46 ms
[ INFO ] Latency:
[ INFO ]    Median:           0.77 ms
[ INFO ]    Average:          0.77 ms
[ INFO ]    Min:              0.32 ms
[ INFO ]    Max:              11.06 ms
[ INFO ] Throughput:          10209.35 FPS


Layer events affecting another sessions (other tabs, other users)

Let's say we have user A and user B. And in the blazor app we have a layer in the azure map and some events in there, see a code as example:
layer.OnMouseOver += mouseEventArgs => {     _navigationManager.NavigateTo("test"); };
If there's only user A, it will work fine, when the user hovers the mouse over the layer it will navigate to this test page.
But let's say User A opened the map, then User B. If User A over the mouse, it will open the page in User B tab. Why? Is this a bug or am I doing something wrong?
If someone can point what's wrong, I'll appreciate!
To Reproduce
Steps to reproduce the behavior:

Create a layer
Add a event to layer
Add layer to map
Open two tabs
Invoke events from first tab opened and see the reaction in another

Expected behavior
The events should happen in the tab that invoked events

I can confirm the same behavior.
In my case, I first ran into a problem when creating two independent map components within the same Blazor page, each with a mouseover event to display a popup on the map canvas.  Whichever map after being rendered first receives a mouseover event works fine, until the second map processes a mouse event. Then events on the first map stop working and vice versa.
Thanks to @phpb1997, I tried opening a map in two different browser tabs and see the same behavior.
To Reproduce:

Download and run the AzureMapsControls.Components.Sample
Open the HTML marker popup sample in two different browser tabs or windows.
Open browser developer tools => debug console
Click on the marker in the first tab to open the popup.
Click on the marker in the second tab, which will fail with an exception
Refresh the second tab and click on the marker. The popup should open.
Click again on the marker in the first tab, which will fail.

Expected behavior:
Support for more than one map instance with event handling

@phpb1997 @markbeau First of all, sorry for the delay!
Thanks to your description, I was also able to reproduce the issue and fix it. I just published a version 1.16.0-alpha0003. Could you please check if the issue is fixed with this version and give me a feedback ?

Glad to hear! Thanks for the feedback! I just published a stable version 1.16.0 with the fix, so I will close this issue.

@arnaudleclerc
Likewise, it's looking good here too.  Thanks a bunch!!!


Address Joda-Time CVE-2024-23080.

As per https://github.com/hyperledger/fabric-chaincode-java/issues/337

@benjsmi
BTW if you use a term like "Resolves" instead of "As per" when referencing an issue, it will create a link and automatically close the issue when the pull request is merged. See the list of magic key words at:
https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword

@benjsmi
And another BTW... if you know you are going to open a pull request, you don't even need to open a corresponding issue. You can just open the pull request. We typically open issues as a reminder for future work items.

I don't completely understand this change. CVE-2024-23080 is currently listed as Disputed for a vulnerability in joda-time v2.12.5. Before this change, the version of joda-time resolved by fabric-chaincode-shim was v2.10.2. After this change the version of joda-time resolved is still v2.10.2. There is no vulnerability showing up in the scheduled vulnerability scan.
What does this change fix?

Yeah we may want to reopen this issue (https://github.com/hyperledger/fabric-chaincode-java/issues/337). I attempted to resolve this problem with my PR but it doesn't seem to have done the trick as @bestbeforetoday indicates.
Specifically, I was under the impression that moving to latest org.everit.json.schema (that is v1.14.4) was going to move us to latest handy-uri-templates, which would, in turn, move us to latest joda-time.  It did not make the change.
It looks like the whole Everit JSON Schema project has moved from https://mvnrepository.com/artifact/com.github.erosb/everit-json-schema/1.14.4 over to https://mvnrepository.com/artifact/com.github.java-json-tools/json-schema-validator?  Is it possible to use this in place of the other? everit-json-schema seems to have gone end of life.
The trace is:
everit-json-schema -> handy-uri-templates -> joda-time...
So, I think maybe we are more stuck than I thought, unless we are able to override transitive dependencies in Maven (I've never known how to do that). From where I sit, we'd need handy-uri-templates to move to a newer/later version of joda-time and then we'd need everit-json-schema to move to that newest version of handy-uri-templates.
Regarding the disputed nature of CVE-2024-23080... a few things: 1) the tools that I am required to use don't show it as disputed, even though I agree with you that it is.  2) it's easier to just move to the latest version than to just explain over and over again that it's a disputed CVE. 3) I've seen many CVEs be disputed until they just aren't, so it's probably a temporary thing.

I can totally relate to just updating the dependency as being the easiest path. I've been in the same situation many times.
Maven prefers the closest dependency in the dependency tree. This means a top-level POM file dependency on a component at a specific version will take precedence over the versions of any transitive dependencies on the same component. This is generally not a good idea since changes between versions can break the other components that depend on it at a specific version. If possible, it safer to update just the direct dependencies to versions where the transitive dependency is at a good version.
At a quick glance, it doesn't look like everit-json-schema leaks out into the public API anywhere so I'd be quite happy for it to replaced by something newer/better.


docs(extension) add description for consumer.id

the conditional should check for the underscored value, whereas the description should have dot notation; these were reversed.
also improved the definition of "consumer" and style.


increased nipple pigmentation

Add new term:
increased nipple pigmentation (a child of abnormal nipple morphology MP:0006078 and hyperpigmentation MP:0001188)
DEF: visually detectable excess of pigment present on the surface of the nipple and/or areola
SYN: nipple hyperpigmentation
SYN: hyperpigmented nipples
SYN: darkened nipples
Annotations in J:13077, J:147434

Added new term:
increased nipple pigmentation MP:0030931


Fix the error related with absolute path

Fix the error with build script:
"
Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

configuration.output.path: The provided value "examples/build" is not an absolute path!
"

Thanks alot!


[IGNORE] Upgrade react-router from 6.3.0 to 6.11.2

Temp branch to hopefully upgrade react router without breaking a bunch of stuff 🤞
Follow up to closed PR #1153 - I think this is safe to upgrade now, finally got RTL tests to pass again

looks good for me. I'm just wondering why we need the router history for the dashboard tests :o

looks good for me. I'm just wondering why we need the router history for the dashboard tests :o

We test query params for TimeRangeControls to make sure start is applied correctly here, might be better to do that as an e2e in the future, but I did finally get it to work again 😂


not parsing log files in foreign languages

If the log file is not in english language, the program seems to be unable to parse the queries and other stuff even if all the track properties are set.

Ops, it was already specified in the README, sorry for the noise.


Issue with new Hugo Version 0.56

With new hugo version 0.56 some elements of my page are not rendered correctly, e.g. the hero and feature component.
Contact, header, footer works ...
Syna Version: v0.15.0

Will look into it as soon as possible. Seems like this didn't come up with the automated deploy for the themes site.

Any open source code I can check out, where this might happen?

Thank you. I've fixed it by forcing Hugo version 0.55.6, issue reappears with version 0.56 (local and on gitlab pages). I've invited you to the project on gitlab.
temporary fix in file gitlab-ci.yml:
image: registry.gitlab.com/pages/hugo:0.55.6

I've just realized it also happens with the exampleSite -> fragments, so maybe easier to test.

Just ran into this again. Recommended version for now is 0.55.6. Seems like 0.56+ breaks our fragment overwrites as well as subdirectory usage for fragments such as member, items etc.

I still can't find a fix. The problem occurs due to a change in how .Page.Resources works in v0.56 which removes the [page]/[fragment]/index.md file from page resources. I'm still working on the issue and hopefully will fix the problem in the near future. Any help would be much appreciated.
A temporary fix for now would be to move [page]/[fragment]/index.md to [page]/[fragment].md and keep subitems inside the [page]/[fragment]/ directory.

Thanks for taking a look. I hope that I have some time next week myself to take another look. Also if this feels like a regression and you have the specifics. Happy for you to open an issue (it's breaking) or I'll create it.

Would be great if that could be fixed. I have two issues when using the latest hugo:

hugo server live reloading doesn't work with syna. You can reproduce this with https://github.com/okkur/syna-start by changing the content of the About page.
When changing anything in the content/_global or content/_index directories the whole Hugo server crashes.

The master from Syna should have this fixed. With syna-start update the submodule to master.
Sometimes caches don't like the Syna fragments using --ignoreCache should help.

Thanks for the quick reply @stp-ip. I can confirm that switching to master solved the issues. Thank you very much for your efforts!


Add a new page for Books which shows a few books using Google Books API and also adding a few styles

I have noticed that your page has horizontal overflow and the title of the website can be changed to BOOKISH-NERD. I also thought of adding a new page for Books which uses API to fetch the books.

Sure go ahead!


Can't setTitle

I am trying to setTitle in actionbar like this:
Bundle bundle	= getIntent().getExtras();
String keyword	= bundle.getString("com.taste.android.keyword");

getSupportActionBar().setTitle(keyword);

But the results didn't show the text of the keyword
the result is the name of the application

Is this for version 3 or the version 4 betas?

I'm uses version 4 beta #5 ...

I use getSupportActionBar().setTitle(...) several places in my applications, never had an issue. You might want to check that keyword isn't null.

I tried getSupportActionBar().setSubtitle(...) .. it runs fine
but when I try getSupportActionBar().setTitle(...) keyword is not out, only show text from application name


Account adress is not correct

when doing result.toJson()
the wallet address is not correct, also is possible to add new logo and make the library working for IOS?

child: TextButton(
onPressed: () {
// 2. Authorize application with wallet.
adapter
.authorize()
.then((result) => setState(
() => _output =
result.toJson()))
.catchError((error) =>
setState(() =>
_output = error));
},

Hi Mariano,
On Android the address is base-64 encoded. The Account class has a toBase58() method to convert the base-64 address to base-58.
The Mobile Wallet Adapter Specification doesn't currently support iOS: iOS Support.

Thank you so much, I have some other questions about the solana wallet mobile adapter, if you can help me reply it will help me a lot, would like to directly speak with you if possible too, since I see you are the only one working on solana with Flutter

Shall we have a chat on Discord? What's your ID and when would be a good time to chat?

Username: meryakamariano
ID:<PHONE_NUMBER>73369877
Send me a message!