Performance tips when transforming larger number of shapes

Expected behavior and actual behavior.
Hi, I'm working on a geometry project in which I'm will have to operate on a larger number of different shapes. Those operation will usually involve: translation, scaling, homography mapping, custom transforms, filtering etc.  Most of them when implemented in pure numpy can be easily vectorized, however with shapely I have encountered a basic performance issues: a large fraction of time is consumed by shape construction. Additionally, wrapping shapes with GeometryCollection introduces another notable delay in the processing, same for conversion from geometry to numpy array (this was actually a surprise for me).
My question is then: what is the recommended solution for my issue ?
Steps to reproduce the problem.
Here is some benchmark I made to check different options, note that this benchmark is tested only for Point class, my expectation for more complex shapes like Polygon is that it will go even worse.
        import time
        from shapely.geometry import Point, MultiPoint, GeometryCollection
        import numpy as np
        import shapely.ops as shapely_ops

        objs = [Point(0.3, i / 10.0) for i in range(100000)]
        print("Point creation:", time.time() - start_time)
        start_time = time.time()

        transform_fn = lambda x, y: (100.0*x*(y - 1), 200*(y - x))
        new_objs = [shapely_ops.transform(transform_fn, o) for o in objs]
        print("Time #1 (points in loop)", time.time() - start_time)
        start_time = time.time()
        coll = GeometryCollection(objs)
        print("Time #2 (collection creation):", time.time() - start_time)
        start_time = time.time()
        new_objs = shapely_ops.transform(transform_fn, coll)
        print("Time #2 (collection transform):", time.time() - start_time)
        start_time = time.time()
        np_objs = np.concatenate([o.coords for o in objs])
        print("Time #3 (convert to numpy):", time.time() - start_time)
        start_time = time.time()
        x, y = transform_fn(*np_objs.T)
        new_objs = np.vstack([x, y]).T
        print("Time #3 (numpy transform):", time.time() - start_time)
        start_time = time.time()
        new_objs = GeometryCollection(MultiPoint(new_objs).geoms)
        print("Time #3 (convert numpy to points):", time.time() - start_time)
        start_time = time.time()

Output:
Point creation: 0.7066037654876709
Time #1 (points in loop) 3.342881917953491
Time #2 (collection creation): 0.3173365592956543
Time #2 (collection transform): 4.738433837890625
Time #3 (convert to numpy): 1.3321762084960938
Time #3 (numpy transform): 0.013933897018432617
Time #3 (convert numpy to points): 2.368988513946533

Numpy is fast as expected, but I don't gain so much since I lose a lot of time on types conversion.
Operating system
Ubuntu 16.04LTS
Shapely version and provenance
numpy==1.14.3
Shapely==1.6.4.post2

@kmkolasinski I regret that we don't have a support mailing list or forum for this kind of question. The Shapely issue tracker is not really the right place. I'm becoming 👎 on GIS Stack Exchange these days and don't spend much time there.
Basically, the creation of GEOS coordinate sequences by Shapely is slow. I think I've got an issue deep in this tracker about creating a new GEOS C++ class that can read directly from numpy arrays, but haven't acted on it and don't know when I will have the time. I think that's about the only thing that will solve this problem. Until then, we just have to deal with the slowness.

Hi, thanks for the answer, I realized that shapely is good for the case with small number of shapes but when those shapes contain a larger number of points. My requirement  is opposite, small shapes but in a larger number of them. For me the solution for now is to implement a custom library in python and not using shapely.

@kmkolasinski How did you fix this performance issue?

@Haitham-Khedr in the meantime, the internals of Shapely have been refactored to tackle (among other things) the performance, see https://shapely.readthedocs.io/en/latest/release/2.x.html#version-2-0-0-in-progress
There is currently an alpha release you can test -> https://github.com/shapely/shapely/discussions/1464 (and beta will be out soon)
To take the first example of the code snippet in the top post to illustrate the improvement:
# with the manual for loop
In [11]: %timeit [shapely_ops.transform(transform_fn, o) for o in objs]
5.47 s ± 1.02 s per loop (mean ± std. dev. of 7 runs, 1 loop each)

# using a new vectorized method (the transform function needs a small rewrite
# to work on a 2D array instead of separate x, y
def transform_fn2(xy):
    x = xy[:, 0]
    y = xy[:, 1]
    xy[:, 0], xy[:, 1] = (100.0*x*(y - 1), 200*(y - x))
    return xy

In [23]: %timeit shapely.transform(objs, transform_fn2)
102 ms ± 3.25 ms per loop (mean ± std. dev. of 7 runs, 10 loops each)


TRG 5.11 Upgradeability

No upgrade testing availble as it's commented in workflow file:
https://github.com/eclipse-tractusx/portal-cd/blob/52812dc8cf84c66417984f88366c84f45eb713c7/.github/workflows/portal-chart-test.yaml#L97-L105

@carslen Due to the major version upgrade in the subchart of the subchart, this upgrade step will inevitability fail so I disabled it until the release of the 1.7.0 version. I mentioned this in the office hour as something to consider for this TRG.


Run on https

HI Guys
Is there any chance to config this lib to run on https?
Thanks

Hey @alex-clear 👋
Thanks for the idea but restapify is intended for the development phase of your app where commonly a https certificate is not a requirement. So I don't think it will be a priority for now. However if you want to implement it I would be happy to guide you in your process 👍

@johannchopin Thanks for the answer


bevy_reflect: reflect_hash and reflect_partial_eq inconsistent on Dynamic types

What problem does this solve or what need does it fill?
The Issue with Reflect::reflect_hash
Currently, DynamicMap is the only place we make use of Reflect::reflect_hash. It uses this to dynamically hash a dyn Reflect so it can be stored in an internal HashMap<u64, usize>.
Unfortunately, Dynamic types (e.g. DynamicStruct, DynamicTuple, etc.), do not implement refelct_hash. Why? They can't make use of the Hash impl of the concrete type they represent.
This means that doing the following will panic:
#[derive(Reflect, Hash)]
#[reflect(Hash)]
struct Foo(i32);

let mut map = DynamicMap::default();

let foo = Foo(123);
let foo_clone: Box<dyn Reflect> = foo.clone_value(); // Creates a boxed `DynamicTupleStruct`

map.insert_boxed(foo_clone, Box::new(321)); // PANIC: "the given key does not support hashing"

Ideally, a Dynamic value's reflect_hash should be the same as its concrete counterpart. This reduces the burden of validating types on the user and reduces their need for unnecessary FromReflect::from_reflect calls.
The Issue with Reflect::reflect_partial_eq
Similarly, Reflect::reflect_partial_eq can often work completely differently between a concrete type and its Dynamic representation. If a user adds #[reflect(PartialEq)] to a type, it suddenly breaks on certain comparisons and only in one direction:
#[derive(Reflect, PartialEq)]
#[reflect(PartialEq)]
struct Foo(i32);

let a = Foo(123);
let b = Foo(123);
let c: Box<dyn Reflect> = a.clone_value(); // Creates a boxed `DynamicTupleStruct`

// 1. Concrete vs Concrete
assert!(a.reflect_partial_eq(&b).unwrap_or_default()); // PASS
// 2. Dynamic vs Concrete
assert!(c.reflect_partial_eq(&b).unwrap_or_default()); // PASS
// 3. Concrete vs Dynamic
assert!(b.reflect_partial_eq(&*c).unwrap_or_default()); // FAIL

In the above example, we fail at Assertion 3 because Foo uses its actual PartialEq impl when comparing, which will obviously fails when compared to a Dynamic.
What solution would you like?
We should make both Reflect::reflect_hash and Reflect::reflect_partial_eq completely dynamic for non-ReflectRef::Value types. That is, for a given container type (e.g. a struct, tuple, list, etc.), the results of those operations should be determined based on the values that make up the type.
This means that both Foo(i32) and its DynamicTupleStruct representation can return the same value for each, and the user can rest a little easier when using Reflect::clone_value.
Requirements
Equality
Together, these methods should work much like Hash + Eq. We should uphold that if two values are equal according to reflect_partial_eq, their reflect_hash values should be equal as well:
reflect_partial_eq(a, b) -> reflect_hash(a) == reflect_hash(b)

Optionality
There may be cases where a value cannot be hashed or compared. These values should return None. If a type contains another type whose reflect_partial_eq or reflect_hash is None, then it should return None as well. So if one field of a struct returns None, then the entire struct returns None. The None-ness bubbles up.
Skipping Fields
In order to give users more control over this behavior, it would be best to allow them to "skip" certain fields that are either known to return None or simply not desired to be included in the operation.
#[derive(Reflect)]
struct MyStruct {
  a: usize,
  #[reflect(skip_hash)]
  b: f32, // `f32` cannot be hashed
  #[reflect(skip_partial_eq)]
  c: i32, // We don't want this field to influence equality checks
}

The #[reflect(skip_hash)] attribute will remove the given field from reflect_hash checks, while the #[reflect(skip_partial_eq)] attribute will remove it from reflect_partial_eq checks.
Type Data
There may be cases we want to still make use of the concrete impls of PartialEq and/or Hash.
To do this, we can add two new TypeData structs: ReflectHash and ReflectPartialEq. Both will simply contain function pointers that can be be used to perform the concrete implementations. This data can then be retrieved from the TypeRegistry. And since getting TypeData returns an Option<T>, the functions stored in these structs no longer need to return Option<bool> and Option<u64> like they currently do. They can simply return bool and u64.
What alternative(s) have you considered?
These issues can be avoided by always checking that a type is not a Dynamic and using FromReflect::from_reflect if it is. However, we often don't have access to the concrete type required to make use of the FromReflect trait, which makes this solution not ideal.
Additional context
Based on a Discord discussion with @soqb.

is the only case for returning None from from_reflect when all fields have the #[reflect(skip_equivalence/ignore)] attribute (and similarly when they have no fields)? couldn't these types be thought of as "always equivalent" and just return an empty hash (0) instead?

is the only case for returning None from from_reflect when all fields have the #[reflect(skip_equivalence/ignore)] attribute (and similarly when they have no fields)? couldn't these types be thought of as "always equivalent" and just return true from reflect_partial_eq and write nothing to the hasher in reflect_hash?

Since each container boils down to a list of base value types, we only return None if one of those types cannot perform the operation. For example, f32 cannot be hashed. This means that the following wouldn't normally compile:
#[derive(Hash)]
struct Foo(f32);

To replicate this dynamically, f32's reflect_hash would return None. And Foo's reflect_hash would also return None unless the f32 field is skipped/ignored.
So no, ignoring/skipping all fields should not return simply return None.
In fact, we might might want to compare type_names as well (we currently make use of this in the reflect_hash operation anyways). Since Dynamic types takes on the type_name of the value they are clone_value'd from. So we may not always return true or None (hash).

That might be too restrictive and we can think about if we really want that behavior. Or we can even have a more restrictive method like reflect_strict_eq or something.

On a side note, I realize there are actually cases where we want to separate out equality and hashing. I gave the example of f32 above. This type can be compared using PartialEq but it cannot be hashed. Therefore, containers may want to use it for equality comparisons but not for their hashing strategy. For example, they may have a u64 ID field in the struct and prefer to use only that. This might be a case where we want to use attributes like #[reflect(skip_hash)] and #[reflect(skip_partial_eq)] over #[reflect(skip_equivalence)].

Here's another issue we need to consider with this proposed solution: Dynamic types are unaware of type information, such as which fields are marked skip_hash/skip_partial_eq.
I can't think of a perfect solution to this, but one idea I had was to store Option<&'static TypeInfo> in these Dynamic types. This would allow us to access field-specific data (assuming we store them in NamedField/UnnamedField). And so Reflect::clone_value would copy this static reference to their generated Dynamics so most users won't need to worry about this themselves.
The idea is that this would allow us to respect skip_hash even in something like a DynamicStruct.
Any thoughts on this?

imo the correct reflect_hash and reflect_partial_eq implementations are crucial behavior - dynamics should behave as close to their concrete counterparts as we can reasonably support. storing an Option<&'static TypeInfo> seems like a reasonable way to do this.
in terms of storing the info on NamedField/UnnamedField this would make sense as it allows the info to be retrieved from both a dyn Reflect and the type registry. in this case we should probably merge SerializationData into TypeInfo for consistency (in a different pr).
i can think of four Typed implementation for dynamics:

current behavior - return TypeInfo::Dynamic which does not contain any information on internal types.
keep returning TypeInfo::Dynamic but with information on fields, variants etc.
if the Option<&'static TypeInfo> field is available return that or else return TypeInfo::Dynamic as described in either of the solutions outlined above.
same as 2/3 but don't wrap in TypeInfo::Dynamic e.g. a DynamicStruct will always return TypeInfo::Struct.

in this case we should probably merge SerializationData into TypeInfo for consistency (in a different pr).

Hm, I'm still hesitant to fully tie reflection to serialization like this. And keeping SerializationData separate allows it to be configured at runtime if needed (but maybe that's not great anyways). We can certainly discuss that more in a future PR though haha.

i can think of four Typed implementation for dynamics:

current behavior - return TypeInfo::Dynamic which does not contain any information on internal types.
keep returning TypeInfo::Dynamic but with information on fields, variants etc.
if the Option<&'static TypeInfo> field is available return that or else return TypeInfo::Dynamic as described in either of the solutions outlined above.
same as 2/3 but don't wrap in TypeInfo::Dynamic e.g. a DynamicStruct will always return TypeInfo::Struct.

I'm not sure 2 is possible since this info is returned statically. Regardless, I think we'd be better off adding a separate method outside Typed that returns the Option<&'static TypeInfo>. This way we can still branch on whether or not the type is Dynamic:
fn foo(value: &dyn Reflect) {
  match value.reflect_ref() {
    ReflectRef::Struct(value) => {
      match value.type_info() {
        TypeInfo::Dynamic(_) => {
          // Probably should add a cleaner way to get here lol
          let value: DynamicStruct = value.downcast_ref().unwrap();
          let info: Option<&'static TypeInfo> = value.represents();
          // ...
        }
        // ...
      }
    }
    // ...
  }
}

And doing this I think sets us up better for Unique Reflect, but I could be wrong.
Additionally, knowing that a type is Dynamic is important for certain operations (such as for serde stuff), so I don't think we should hide the (currently) only method for getting that information.

Starting work on this now!


Camera not working (permission allow)

Hi dev, compile apk is done but cant access camera back or front.
Just loading.
How to fix it??
Thanks sir

Create storage in firebase console which is under the database option in firebase.

You have to enable the storage development platform in firebase console, please read the readme.md file for more detail.


Removed hardcoded optional scopes

Summary
Some optional scopes which should be configurable were hardcoded (email, profile). These scopes were moved to config as default values.

OpenID Connect defines the following scope values:
openid
    REQUIRED. Informs the Authorization Server that the Client is making an OpenID Connect request. If the openid scope value is not present, the behavior is entirely unspecified.
profile
    OPTIONAL. This scope value requests access to the End-User's default profile Claims, which are: name, family_name, given_name, middle_name, nickname, preferred_username, profile, picture, website, gender, birthdate, zoneinfo, locale, and updated_at.
email
   OPTIONAL. This scope value requests access to the email and email_verified Claims.
address
    OPTIONAL. This scope value requests access to the address Claim.
phone
    OPTIONAL. This scope value requests access to the phone_number and phone_number_verified Claims.
offline_access
    OPTIONAL. This scope value requests that an OAuth 2.0 Refresh Token be issued that can be used to obtain an Access >  Token that grants access to the End-User's UserInfo Endpoint even when the End-User is not present (not logged in).

https://openid.net/specs/openid-connect-basic-1_0.html
Type
[x] Bug fix
[] Feature request
[] Enhancement
[] Docs

Hmm, it is not that simple as I thought. The problem is mostly extractIdentity function from user_context.go which requires some scopes (email, profile and keycloak custom claim realm_access + resource_access - from scope roles). But all these scopes are optional and if user deletes these scopes from keycloak (or change client config or remove mapper), gatekeeper will stop working (if I am getting it right). But this type of information (email and profile) do not fit for access token, but for ID token. Also, most of the applications do not need roles scope (realm_access and resource_access), so it can be omitted.
Everything described above is quite complex and breaking change. :slightly_frowning_face:

@praserx i need to check, i removed it more then year ago and i think it  was for some reason, but i assume it is fixable by adding scopes to client so it should not be big problem

@praserx i removed all scopes from client, having this token:
{
  "exp":<PHONE_NUMBER>,
  "iat":<PHONE_NUMBER>,
  "jti": "2992ad89-c021-4c28-b115-a7b72fb5ee42",
  "iss": "http://<IP_ADDRESS>:8081/auth/realms/test",
  "sub": "844c2220-f661-4f0a-a65e-742b4f09da97",
  "typ": "Bearer",
  "azp": "test-client",
  "acr": "1",
  "allowed-origins": [
    "*"
  ],
  "scope": "",
  "clientHost": "<IP_ADDRESS>",
  "clientId": "test-client",
  "clientAddress": "<IP_ADDRESS>"
}

and everything works

@p53 Nice :+1:

Uhm @p53 I think we misunderstood each other. I thought it works with this change, because for me, current state do not work.
If I remove email and profile scope from client configuration on Keycloak side, then it leads to this response:
https://myweb.local/oauth/callback?error=invalid_scope&error_description=Invalid+scopes%3A+openid+email+profile&state=9c4xxxx7-xxx-4a86-xxxx-2ea21xxxxb77

For me I need this PR to be merged. Be cause I don't want to request access token with scopes email and profile (only with openid scope). These scopes are not allowed for some clients and if gatekeeper making request with these missing scopes it lead to error if these scopes are missing on Keycloak side. So I need config possibility to remove these scopes from token request.

ok i didn't try auth code flow you are using, there would be problem

according history https://github.com/gogatekeeper/gatekeeper/blob/086d19741cea8fcde0e208492e1cd81eb413dd65/oauth.go#L52  and if you check oidc package default scopes https://github.com/coreos/go-oidc/blob/v1/oidc/client.go email, profile was always appended to scopes so there is no change in that behaviour, but i agree it would be better to be configurable

ok i didn't try auth code flow you are using, there would be problem, but it would be always be good to provide full description with some example, error output etc...because otherwise it is like guessing

My bad, sorry. The explanation should be better. For me that was so clear that I didn't think some more info were needed.

and if you check oidc package default scopes https://github.com/coreos/go-oidc/blob/v1/oidc/client.go email, profile was always appended to scopes so there is no change in that behaviour, but i agree it would be better to be configurable

Yep I understand that due to compatibility and for some future issues it was better do it the same way as previous. The think is that scopes like email or profile should be optional and configurable. It looks like nothing of these changes breaks anything.


build: eslint, tslint, prettier consolidation, purge from non-root pkgs

We had dozens of different versions of ESLint, TSLint, Prettier
declard in package.json files. Most versions were so old that they had
ben EOL for several years too.
The presence of these and their scripts/config files/etc were making
it impossible to run the linter on the sub-folders where these were
being used.
As part of the big push to consolidate linting and code formatting on
the entire project, this is phase 1 where I purged the mentioned dependencies
from the project and now only the root package.json file declares them
which is currently using the latest and greatest versions.
I know that the diff is huge in this pull request but there are no
code changes that would cause bugs or logic modification at all. It's all
just applying automated formatting and linting on sub-directories where
previously this was impossible. E.g., this entire change should not cause
any sort of bugs (but of course we'll see what the CI execution has to
say about that).
The follow-up phases will consist of slowly applying more brazen
refactoring in a much more targeted and surgical manner with small
pull requests that are easy and quick to review.
The smaller pull requests will target sub-directories that we still
cannot include in the linting (see the .eslintignore file for a list) and
then culminate in us finally enabling the linter for everything.
The root folder's ESLint ignore file was refactored in a way that the
files that we plan on fixing later are now ignored on a one by one basis
instead of using patterns. This makes the ignore file a collection of
to-dos where one can delete a single line from the ignore file (pertaining
to a single file that is being ignored) and then proceed to fix the linter
issues and send a small, easy to review pull request that does not overwhelm
the maintainers when they are trying to review a huge diff with a large
batch of linter fixes. Phase two of this project is then to one by one
drain the ignore entries of these mentioned files from the ESLint ignore
file.

So, the bottom line is that this might look like a hugely disruptive
change, but I've done my best to keep it as simple as possible so that
we don't have to worry about reviewing it line by line and instead just
focus on the big picture and the principle idea(s) behind it (code quality).
If it does end up introducing a bug or CI breakage, I'll volunteer to fix
those because I'm very confident that even if this does happen, it will
be very minor and quick fixes necessary only so I don't mind being on the
hook for it.
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>Pull Request Requirements

[x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

@petermetz Weaver tests are failing

@petermetz Weaver tests are failing

@outSH Oops, thank you, I'm working on a fix!
cc: @sandeepnRES @VRamakrishna

@outSH Weaver tests are now passing!


chore: add github.com/ntk148v/hugo-toigian

From Netlify log:
11:43:55 AM: verifying<EMAIL_ADDRESS>checksum mismatch
11:43:55 AM: 	downloaded: h1:kWbaK5JXp1sIqzOsrcS6cWw+OlzMjaFOIH1ZLsIu99g=
11:43:55 AM: 	go.sum:     h1:8Vy+1nQCgKgr9aDFZ4pAUjp0sVE/ZzXgsRrqCYehuaA=
11:43:55 AM: SECURITY ERROR
11:43:55 AM: This download does NOT match an earlier download recorded in go.sum.
11:43:55 AM: The bits may have been replaced on the origin server, or an attacker may
11:43:55 AM: have intercepted the download attempt.
11:43:55 AM: For more information, see "go help module-auth".
11:43:55 AM: Got Hugo Modules in 1628 ms
11:43:55 AM: error: exit status 1
11:43:55 AM: exit status 1
11:43:55 AM: go failed: exit status 1


Bug: Migrator config unnecessarily calls fixupConfigRules and fixupPluginRules on typescript-eslint

Which packages are affected?

[ ] @eslint/compat
[ ] @eslint/config-array
[ ] @eslint/core
[X] @eslint/migrate-config
[ ] @eslint/object-schema

Environment
Node version: 22.4.1
npm version: n/a
ESLint version: 9.x
Operating System: n/a
What did you do?
git clone https://github.com/MariuzM/expo-starter
cd expo-starter
npx @eslint/migrate-config .eslintrc

What did you expect to happen?
The generated config should only call fixupConfigRules and fixupPluginRules on configs/plugins that need it. As of typescript-eslint releasing 8.0.0, that's no longer typescript-eslint.
For example, from the sample linked repo:
import { fixupConfigRules } from '@eslint/compat';
import typescriptEslint from '@typescript-eslint/eslint-plugin';
import tsParser from '@typescript-eslint/parser';
import path from 'node:path';
import { fileURLToPath } from 'node:url';
import js from '@eslint/js';
import { FlatCompat } from '@eslint/eslintrc';

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
const compat = new FlatCompat({
  baseDirectory: __dirname,
  recommendedConfig: js.configs.recommended,
  allConfig: js.configs.all,
});

export default [
  {
    ignores: [
      // ...
    ],
  },
  ...fixupConfigRules(
    compat.extends(
      'plugin:react-hooks/recommended',
      'plugin:import/recommended',
      'plugin:import/typescript'
    )
  ),
  ...tseslint.configs.recommended,
  {
    settings: {
      'import/ignore': ['react-native'],
    },

    rules: {
      // ...
    },
  },
];

What actually happened?
typescript-eslint packages are stilled wrapped in the fixup functions.
import { fixupConfigRules, fixupPluginRules } from '@eslint/compat';
import typescriptEslint from '@typescript-eslint/eslint-plugin';
import tsParser from '@typescript-eslint/parser';
import path from 'node:path';
import { fileURLToPath } from 'node:url';
import js from '@eslint/js';
import { FlatCompat } from '@eslint/eslintrc';

const __filename = fileURLToPath(import.meta.url);
const __dirname = path.dirname(__filename);
const compat = new FlatCompat({
  baseDirectory: __dirname,
  recommendedConfig: js.configs.recommended,
  allConfig: js.configs.all,
});

export default [
  {
    ignores: [
      // ...
    ],
  },
  ...fixupConfigRules(
    compat.extends(
      'plugin:@typescript-eslint/recommended',
      'plugin:react-hooks/recommended',
      'plugin:import/recommended',
      'plugin:import/typescript'
    )
  ),
  {
    plugins: {
      '@typescript-eslint': fixupPluginRules(typescriptEslint),
    },

    languageOptions: {
      parser: tsParser,
    },

    settings: {
      'import/ignore': ['react-native'],
    },

    rules: {
      // ...
    },
  },
];

Link to Minimal Reproducible Example
https://github.com/MariuzM/expo-starter
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
I'm a little pressed for time right now, so omitting the minimum repro because I think this is a fairly straightforward request. I can take the time to make one if you really need. 🙂

This isn't technically a bug because this was needed, but since things have changed, we can update the tool.

So I took a look at this and it's not a bug, it's working as intended.
The issue is that the config is using extends with some configs that still require fixupConfigRules():
    compat.extends(
      'plugin:@typescript-eslint/recommended',
      'plugin:react-hooks/recommended',    // requires fixupConfigRules()
      'plugin:import/recommended',    // requires fixupConfigRules()
      'plugin:import/typescript'    // requires fixupConfigRules()
    )

Because it's referenced in the same extends, typescript-eslint is also being wrapped by fixupConfigRules(). As a result, the typescript-eslint plugin object that is added behind the scenes would be different than the one directly from the import. To fix that, typescript-eslint must be passed through fixupPluginRules() in order to have the same object in both places.
So if this config stops using configs that require fixupConfigRules(), typescript-eslint will no longer be wrapped in fixupPluginRules().
As-is, this doesn't cause any change in functionality.


New v2 version should update import path

What version of Go are you using (go version)?
go 1.13.7
Which database and its version are you using?
MySQL/PostgreSQL
Please provide a complete runnable program to reproduce your issue. IMPORTANT
As code new upcoming version have some different APIs. If it become to v2.0, it should be update import path to github.com/jinzhu/gorm/v2 to better go module support.

We decided to use the import path gorm.io/gorm instead of github.com/jinzhu/gorm/v2
Thank you for your report.


Effective MACs

Adding high-level tasks finalized from dev meeting.

For SNNs can calculate effective MACs similarly to calculating synaptic operations, see example code here: https://github.com/open-neuromorphic/snnmetrics/blob/main/snnmetrics/synops.py


fix: [IC-272] use query call on management canister fetch_canister_logs method

Description
The management canister method fetch_canister_logs can only be called as a query, not an update call, so this PR fixes the issue.
How Has This Been Tested?
Built and run dfx locally to verify a rust canister collects the logs and they can be retrieved by using dfx canister logs <canister_id>.
Output example:

Checklist:

[x] The title of this PR complies with Conventional Commits.
[x] I have edited the CHANGELOG accordingly.
[x] NO NEED for the changes to the documentation.

Can you add a test for this?

Done, PTAL.


Error when installing chaincode

When I follow the instructions to install chaincode (node install_chaincode.js) locally on Ubuntu I get an exception:
Error: Cannot find module 'stream-buffers'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (/home/padraic/marbles/node_modules/fabric-client/lib/packager/Golang.js:23:12)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
Any ideas to resolve?
Thanks
Padraic

npm install stream-buffers  due to reasons unknown it appears to not install on certain systems, even though its in the SDK's package json....

That fixed that issue - thanks so much.
However when I try to issue the join channel command node test/integration/e2e/join-channel.js I initially get a timeout error. I updated the timeout value in app.js and re-run. 4 of 6 tests pass but I get an exception thrown
Error: Cannot find module '/home/padraic/marbles/scripts/fabric-sdk-node/test/fixtures/test/integration/e2e/join-channel.js'
at Function.Module._resolveFilename (module.js:469:15)
at Function.Module._load (module.js:417:25)
at Module.runMain (module.js:604:10)
at run (bootstrap_node.js:389:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:504:3
padraic@padraic-VirtualBox:~/marbles/scripts/fabric-sdk-node/test/fixtures$ sudo node test/integration/e2e/join-channel.js
sudo node test/integration/e2e/join-channel.js
sudo: node: command not found
padraic@padraic-VirtualBox:~/marbles/scripts/fabric-sdk-node/test/fixtures$ node test/integration/e2e/join-channel.js
node test/integration/e2e/join-channel.js
module.js:471
throw err;


Flutter How to Detect combination keys like ctrl+s or ctrl+p

i want to detect ctrl+s i have found a function butt that just detect single key.
import 'package:flutter/material.dart';

import 'package:flutter/foundation.dart';
import 'package:flutter/services.dart';

void main() => runApp(MyApp());

/// This is the main application widget.
class MyApp extends StatelessWidget {
  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: _title,
      home: Scaffold(
        appBar: AppBar(title: const Text(_title)),
        body: MyStatefulWidget(),
      ),
    );
  }
}

/// This is the stateful widget that the main application instantiates.
class MyStatefulWidget extends StatefulWidget {
  MyStatefulWidget({Key key}) : super(key: key);

  @override
  _MyStatefulWidgetState createState() => _MyStatefulWidgetState();
}

/// This is the private State class that goes with MyStatefulWidget.
class _MyStatefulWidgetState extends State<MyStatefulWidget> {
  // The node used to request the keyboard focus.
  final FocusNode _focusNode = FocusNode();
// The message to display.
  String _message;

// Focus nodes need to be disposed.
  @override
  void dispose() {
    _focusNode.dispose();
    super.dispose();
  }

// Handles the key events from the RawKeyboardListener and update the
// _message.
  void _handleKeyEvent(RawKeyEvent event) {
    setState(() {
      if (event.logicalKey == LogicalKeyboardKey.keyQ) {
        _message = 'Pressed the "Q" key!';
      } else {
        if (kReleaseMode) {
          _message =
              'Not a Q: Key label is "${event.logicalKey.keyLabel ?? '<none>'}"';
        } else {
          // This will only print useful information in debug mode.
          _message = 'Not a Q: Pressed ${event.logicalKey.debugName}';
        }
      }
    });
  }

  @override
  Widget build(BuildContext context) {
    final TextTheme textTheme = Theme.of(context).textTheme;
    return Container(
      color: Colors.white,
      alignment: Alignment.center,
      child: DefaultTextStyle(
        style: textTheme.headline4,
        child: RawKeyboardListener(
          focusNode: _focusNode,
          onKey: _handleKeyEvent,
          child: AnimatedBuilder(
            animation: _focusNode,
            builder: (BuildContext context, Widget child) {
              if (!_focusNode.hasFocus) {
                return GestureDetector(
                  onTap: () {
                    FocusScope.of(context).requestFocus(_focusNode);
                  },
                  child: const Text('Tap to focus'),
                );
              }
              return Text(_message ?? 'Press a key');
            },
          ),
        ),
      ),
    );
  }
}

@abdulrehmananwar
this issue seems more a question than a big report or a feature request
if you need assistance with your code please follow the link I want help writing my application in the new issue menu

@abdulrehmananwar
this issue seems more a question than a big report or a feature request
if you need assistance with your code please follow the link I want help writing my application in the new issue menu

requesting a feature

requesting a feature

@abdulrehmananwar
could you please provide the information listed in the feature request template located in the new issue selection

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

@abdulrehmananwar
could you please provide the information listed in the feature request template located in the new issue selection

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->

@abdulrehmananwar
As also mentioned in your earlier issue, please provide the issue details in above requested template, because otherwise your issue sounds more of a support question rather than a bug or feature request in the framework.

@abdulrehmananwar
As also mentioned in your earlier issue, please provide the issue details in above requested template, because otherwise your issue sounds more of a support question rather than a bug or feature request in the framework.

ok i have submited this as a new feature request thanks. now i am closing this from here

ok i have submited this as a new feature request thanks. now i am closing this from here


There is no scalar implementation for the named  'LocalDateTime' scalar type

Hello. Thank you very much for making this library publicly available. I'm trying to use LocalDateTime for a project and I'm getting a message saying there's no scalar named LocalDateTime scalar type, as below:
Caused by: graphql.schema.idl.errors.SchemaProblem: errors=[There is no scalar implementation for the named  'LocalDateTime' scalar type]
	at graphql.schema.idl.SchemaGenerator.makeExecutableSchema(SchemaGenerator.java:80) ~[graphql-java-17.3.jar:na]
	at graphql.schema.idl.SchemaGenerator.makeExecutableSchema(SchemaGenerator.java:56) ~[graphql-java-17.3.jar:na]
	at org.springframework.graphql.execution.DefaultGraphQlSourceBuilder.build(DefaultGraphQlSourceBuilder.java:142) ~[spring-graphql-1.0.0-M5.jar:na]
	at org.springframework.boot.autoconfigure.graphql.GraphQlAutoConfiguration.graphQlSource(GraphQlAutoConfiguration.java:88) ~[spring-boot-autoconfigure-2.7.0-M1.jar:2.7.0-M1]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_202]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_202]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_202]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_202]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) ~[spring-beans-5.3.15.jar:5.3.15]
	... 108 common frames omitted

What I've done
Step 1
Added the Maven dependency.
<dependency>
	<groupId>com.zhokhov.graphql</groupId>
	<artifactId>graphql-datetime-spring-boot-starter-webflux</artifactId>
	<version>4.1.0</version>
</dependency>

Step 2
Added scalar LocalDateTime to my .graphqls schema file.
Question
Is there anything I'm missing? I looked through the README and the WebFlux sample project, but couldn't figure it out. If further data is needed, the pet project I'm working on is publicly available here.

Hello, @mdevino !
The reason why these starters doesn't work in your project is because you are using official Spring's starter from GraphQL:
		<dependency>
			<groupId>org.springframework.boot</groupId>
			<artifactId>spring-boot-starter-graphql</artifactId>
		</dependency>

When this library was created at that moment there is no official starter from the Spring team, only a starter from the GraphQL Kickstart project: https://github.com/graphql-java-kickstart
I'm planning to add support for the official Spring Boot GraphQL starter in 5.0.0 version. If you can help me with this, it will be amazing to receive a such PR.

Hi @donbeave. Thanks for the reply. I'm a beginner to the Spring ecossystem as well as GraphQL. I'm not sure on how to make such integration, but I'm willing to try.
I'll take a look at the projects and try to figure out how to get this done and open the PR if I manage to get it working (any directions on where to look, if you'd have them, are welcome).

@mdevino To make it work, you need to find a place where Spring GraphQL is initializing GraphQLSchema. I think it will use SchemaParserBuilder where you can register scalars by adding them with such method .scalars(new GraphQLLocalDate()), you can check this code as an example:
https://github.com/tailrocks/graphql-java-datetime/issues/32#issuecomment-692239086

@donbeave Thank you very much. I'll give it a go.

@mdevino I have added support for Spring GraphQL here: https://github.com/tailrocks/graphql-java-datetime/tree/master/graphql-datetime-spring-boot-starter
It will be released with the new version.
There is a sample application that shows how it works: https://github.com/tailrocks/graphql-java-datetime/tree/master/samples/spring-boot-webmvc

Hi, @donbeave. Thanks for that, and sorry for not getting back to you.
Does this commit contains all the code you had to write to make it work with Spring?
Just so I can take a look on what was needed, in case a PR to fix it again in the future might be needed.

@mdevino the basic implementation was here: https://github.com/tailrocks/graphql-java-datetime/commit/e92ad82f1679052dda7932ca49ba57dcf1b6ad28#diff-480bdde79e42752eaabd3eea934260dbfbc8b51825e0b371f497dfd040faa5b5
The next commit was added Spring Boot's configuration https://github.com/tailrocks/graphql-java-datetime/commit/8822f81e0a24abfd0dcab72e509ad85e17ac9b85#diff-312967364a736fd7f317b159835888e048de63d81ad1e2c9b139f51de00f3936

Hey, thanks for the update!

@setchy I'm thinking to publish it with the release of the GraphQL Java Kickstart Spring Boot 13.0.0 version. But I'm not sure when that version will be released.

Released 5.0.0: https://github.com/tailrocks/graphql-java-datetime/releases/tag/v5.0.0


[ ] All tests have passed. If this feature is not already covered by the tests, new tests have been added.
[ ] The pull request is targeting the dev branch.
[ ] The code has been validated to compile successfully by running go vet ./....
[ ] The code has been formatted properly using go fmt ./....

I have read the CLA Document and I hereby sign the CLA

Hey @SuperSandro2000,
Thanks for submitting the PR.
We've recently updated the CLI to Go 1.22.3, which should resolve the issue you encountered. We didn't merge your PR since updating the Go version affects some of our internal release tools.
I'm closing this pull request, but feel free to reach out if you have any questions.

We didn't merge your PR since updating the Go version affects some of our internal release tools.

Newer go versions are a lot more strict about using older or newer versions for no good reason sadly...
Now I am encountering the following but I can work around that
 ▶ go mod tidy
go: go.mod requires go >= 1.22.3 (running go 1.22.2; GOTOOLCHAIN=local)

The new go toolchain changes are annoying....


[FEATURE] Add prefix

Description
Lots of use cases for having something shown before the value, as a prefix. For example, many currrencies put the symbol first (e.g. £150.00 or €300,00) as well as some other measurements (e.g. V for climbing grades, such as V5)
Tech notes
Originally reported here: fredericojordan/progress-bar#14 by @CharliW90
Screenshots or Diagrams

Additional information
No response

 ->
https://progressbar-guibranco.vercel.app/180/?scale=10&title=mark&prefix=R$&suffix=
 ->
https://progressbar-guibranco.vercel.app/420/?scale=500&title=funds&width=120&color=babaca&prefix=R$&suffix=


0.13.1 insecurely fetches data at build time

The minify-html-common/build.rs script seems to fetch https://www.unpkg.com/<EMAIL_ADDRESS>from a third-party site. This is problematic because:

The file is fetched from a third-party site and there is no authenticity verification which means that if the file is hijacked, it could be used to inject vulnerabilities into the package.
Since the file is fetched unconditionally without caching, it is impossible to build the package in an offline environment (or otherwise on a server where unpkg.com is blocked by a firewall).

We're building packages in Gentoo in a network-restricted environment to protect users privacy, so this version cannot be built here at all.

I've updated the code to avoid downloading the JSON on build (it's now stored in the repo), this will be released in version 0.13.3. Let me know if this works for you.

Yes, thank you!


Allow adding note to completed txn

If you forget to add a note while sending a transaction, you are unable to add a note.
We should allow editing of notes and adding notes to transactions after send.

@mide66 to design UX.

@ASN-BitHyve This issue is not feasible!

@ASN-BitHyve @antuz123


How to solve the problem that  cluster status is not ClusterSuccess

Detailed description of the question.
How to solve the problem that _cluster status is not ClusterSuccess?
I have installed the sealos and excute the following steps:
1.
wget https://github.com/labring/sealos/releases/download/v4.1.4/sealos_4.1.4_linux_amd64.tar.gz && tar zxvf sealos_4.1.4_linux_amd64.tar.gz sealos && chmod +x sealos && mv sealos /usr/bin
2.
echo "deb [trusted=yes] https://apt.fury.io/labring/ /" | sudo tee /etc/apt/sources.list.d/labring.list
sudo apt update
sudo apt install sealos

sealos pull labring/kubernetes:v1.25.0
sealos save -o kubernetes.tar labring/kubernetes:v1.25.0

sealos load -i kubernetes.tar
sealos images
sealos run kuberentes:v1.25.0 --single

The first error what I met is such as the following pictrue:

And the second I delete all packages related to sealos and try again.
But the error is that  cluster status is not ClusterSuccess
Runtime environment is wsl2 + unbuntu22.04
Some reference materials you see.
No response

sealos run kuberentes:v1.25.0 --single  ==> sealos run labring/kuberentes:v1.25.0 --single
use 4.2.0 version

sealos run kuberentes:v1.25.0 --single ==> sealos run labring/kuberentes:v1.25.0 --single use 4.2.0 version

@bxy4543 hello,I have delete the package of sealos and install according to the new version.But there is also some problems.

The error is that initializing source docker://labring/kuberentes:v1.25.0: reading manifest v1.25.0 in docker.io/labring/kuberentes: requested access to the resource is denied
The images is such as the following:

@ElonMuskkkkkk kubernetes diff kuberentes

@bxy4543 thank you，I copied the commands in the Manual  without checking, which caused this error. Now I corrected this small error, but there were still new problems in the subsequent execution.

What kind of environment? It seems that systemctl cannot be used normally

@bxy4543 My enviroment is as follows:

The version of the ubuntu is 22.04

https://learn.microsoft.com/zh-cn/windows/wsl/wsl-config#systemd-support

这个报错到底是什么意思啊？是一个通用的错误消息吗？

这个报错到底是什么意思啊？是一个通用的错误消息吗？

哪个？

这个报错到底是什么意思啊？是一个通用的错误消息吗？

哪个？

"Error: cluster status is not ClusterSuccess"

这个报错到底是什么意思啊？是一个通用的错误消息吗？

哪个？

"Error: cluster status is not ClusterSuccess"

安装过程哪一步失败了，reset下重新安装吧


File System Bug

On Windows if mkdir() is run within a non-existent dir it does not create one there.

 File System Bug

Fixed


Dil template - Amazon

dil template for Amazon custom component

The template contains defined parameters that are not used, while the used {{options}} is not defined.
In a routetemplate you need to define the parameter and then use them in the route. With optional defined parameters this is not mandatory, but those make no sense in this case.

I made a little change.
check if now makes sense.


How to use Facebook login with this SDK?

I have enabled facebook as an identity provider on User Pools. I have also set my facebook testApp public. However, I got this error after I tried to sign in.
This is the error and url I see
Can't Load URL: The domain of this URL isn't included in the app's domains. To be able to load this URL, add all domains and subdomains of your app to the App Domains field in your app settings.
https://www.facebook.com/v2.9/dialog/oauth?client_id=157166428323868&redirect_uri=https%3A%2F%2Ftest-social.auth.us-east-1.amazoncognito.com%2Foauth2%2Fidpresponse&scope=public_profile%2C+email&response_type=code&state=ZXlKMWMyVnlVRzl2YkVsa0lqb2lkWE10WldGemRDMHhYM1JNYjNjMFRHRkhSaUlzSW5CeWIzWnBaR1Z5VG1GdFpTSTZJa1poWTJWaWIyOXJJaXdpWTJ4cFpXNTBTV1FpT2lJeU1qQnpaekptTTNGa1lqTmliRzFqY25KMk56bGtiV1J3YnlJc0luSmxaR2x5WldOMFZWSkpJam9pYUhSMGNITTZMeTl5WVhkbmFYUXVZMjl0TDBwMWJqY3hNUzloYldGNmIyNHRZMjluYm1sMGJ5MWhkWFJvTFdwekwzTnZZMmxoYkMxc2IyZHBiaTl6WVcxd2JHVXZhVzVrWlhndWFIUnRiQ0lzSW5KbGMzQnZibk5sVkhsd1pTSTZJblJ2YTJWdUlpd2ljSEp2ZG1sa1pYSlVlWEJsSWpvaVJtRmpaV0p2YjJzaUxDSnpZMjl3WlhNaU9sc2liM0JsYm1sa0lpd2ljSEp2Wm1sc1pTSmRMQ0p6ZEdGMFpTSTZJamhyWlc5V1IzcGxlblpvVUdsUWIyWnVhSFF4UjJWeVRVNVNRbTEyVEVOMUlpd2lZMjlrWlVOb1lXeHNaVzVuWlNJNmJuVnNiQ3dpWTI5a1pVTm9ZV3hzWlc1blpVMWxkR2h2WkNJNmJuVnNiQ3dpYm05dVkyVWlPbTUxYkd3c0luTmxjblpsY2todmMzUlFiM0owSWpvaWRHVnpkQzF6YjJOcFlXd3VZWFYwYUM1MWN5MWxZWE4wTFRFdVlXMWhlbTl1WTI5bmJtbDBieTVqYjIwaUxDSmpjbVZoZEdsdmJsUnBiV1ZUWldOdmJtUnpJam94TlRJd016Z3lPVFl5ZlE9PTpMSjQyK051OGhwcUtyRytwUVNVT1ZxZXFkbVozcmxxbGRRMkZ5cnZRK2prPQ%3D%3D

I think it is domain issue on facebook, so I just wonder what domain I should put. As of this case, I had test-social.auth.us-east-1.amazoncognito.com and https://test-social.auth.us-east-1.amazoncognito.com/ as the site url. And, I host my testApp on RawGit: https://rawgit.com/Jun711/amazon-cognito-auth-js/social-login/sample/index.html
I appreciate any pointer. thanks. please delete it if it is not supposed to be here. thanks

This is the issue:
In March, we're making a security update to your app settings that will invalidate calls from URIs not listed in the Valid OAuth redirect URIs field below.This update comes in response to malicious activity we saw on our platform, and we want to protect your app or website by requiring a new strict mode for redirect URIs.
So, it worked after I whitelisted test-social.auth.us-east-1.amazoncognito.com.


Generate -debug/-dbg packages

RPM at least has a simple addition to the .spec file which can be used to make a -debug package. While doing that, it strips the other binaries, making them much smaller. CPack, unfortunately, doesn't natively support adding that one line. There's two options:

Call CPack in 2 phases: One to generate the spec it would use, perform surgery to add the appropriate stanzas, then call cpack again with the newly-modified spec
Bring our own patched CPackRPM.cmake, modified to support this use case

I have no idea how .deb would do it.

The RPM half fixed by #47. Deb part solved in #54.

Once PR 54 is merged is there anything more we need to do before we consider this issue closed?

AFAIK, it Does The Right Thing. Once this goes in, I'll change over the jenkins packaging to use the unified one

Fixed by #47/#54


The 'app' library and additional application libraries created are linked differently

Users should be able to describe complex applications that are organized into a hierarchy of libraries with different build properties.
To this end, it must be documented and exemplified how to create and use new app CMake libraries.
The desired model for application libraries is that they be organized as pure CMakeLists.txt libraries that could in theory be copied verbatim from a CMake project. So, no reliance on Zephyr CMake extensions or conventions. This is believed to lower the barrier of entry for application developers as they do not have to learn about Zephyr's CMake model and can instead use the standard CMake API to describe their application.
But it is not clear how to achieve this goal. One problem relates to linking. In the zephyr model, libraries are --whole-archive'd together to resolve unresolved references. But in the CMake model libraries should instead be explicitly linked together. There exists build script code that is aware of the 'app' library and ensures that it is whole-archived, but there is no mechanism to ensure that extra application libraries are linked in (and it is not clear if it desirable to use whole-archive on these libraries).

Example of the problem in action:
https://github.com/SebastianBoe/zephyr/commit/fa499525dade0973f08769e03758ad1174de001a
The above does build because app_lib is not whole-archived, this again causes symbols in the 'kernel' library to be omitted.
A temporary workaround/solution (not sure if this is a clean solution yet) is to use the CMake model and explicitly link 'app_lib' with the 'kernel' library, like so:
https://github.com/zephyrproject-rtos/zephyr/commit/5b8619f63466f5bd93b9a8e2cb23113655103302
This ensures that the 'kernel' references that 'app_lib' is using are not dropped. But is there any way for the user to figure this out on his own?

Issue originally reported in: https://github.com/zephyrproject-rtos/zephyr/issues/5554#issuecomment-377183960
@pboettch : Hi, any thoughts on this workaround? https://github.com/zephyrproject-rtos/zephyr/commit/5b8619f63466f5bd93b9a8e2cb23113655103302

Sorry for getting back a little late. I will try your work-around as soon as I can, but it looks promising.
It seems (to be tested) that the whole-archive and start/end-group-stuff is not necessary when using LINK_INTERFACE_MULTIPLICITY .
I tried playing around with it in zephyr's CMakeLists.txt (and getting rid of the not very cmakely overriding of linker-flags) but I must have missed something.
If this works, it would enable this features without further kludges to the CMake-build-system of zephyr.

"It seems (to be tested) that the whole-archive and start/end-group-stuff is not necessary when using LINK_INTERFACE_MULTIPLICITY ."
When initially porting the build system from Kbuild to CMake I tried and failed to get rid of --whole-archive. I can't remember the details, but I remember using LINK_INTERFACE_MULTIPLICITY. So it is still an open question whether --whole-archive can be removed.
As an aside, if one eventually gets rid of --whole-archive one should make sure that the mechanism that replaces it is compatible with LTO.

With LTO you mean real LTO or garbage-collection via gc-sections?

real LTO


Update Python and Django versions

Some of the stylistic code updates in this PR are not intended as-is and they are still WIP and subject to cleanup.

Hey @dominicrodger! I made updates for upgrading the test setup and compatibility for newer Python and Django versions as well as running tests with GitLab Actions, but the tests won't run, probably because they are not enabled yet? Would it be possible to enable them via the Actions UI?
https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow#enabling-a-workflow

It seems that Python 3.7 - 3.10 all work for Django versions up to version 4.0 which has deprecated the use of pytz in favor of the standard library zoneinfo package:

https://docs.djangoproject.com/en/4.0/releases/4.0/#zoneinfo-default-timezone-implementation
https://docs.python.org/3/library/zoneinfo.html#module-zoneinfo

The code will require updates in order to handle .localize() correctly or deprecate them.

Hi @aleksihakli - thanks for all this! Sorry, I've never used GitHub actions before - I see you've added a filed called .github/dependabot.yml - which type of action do I need to enable for that? I tried a couple, but they seemed to just want me to create config files. Perhaps I need to merge this PR first?

Hey @dominicrodger, seems like the actions might require upstreaming in order to run properly.
I'm still validating all the CI and test flows with the updates but you can see the progress here: https://github.com/aleksihakli/django-recurrence/actions
I'll ping you back once the PR passes the test suite with GitHub actions and is a viable candidate for review and merging.

The PR is now ready for review and merging if you think it looks OK @dominicrodger.
I've added support for newer Python 3 versions as well as added PyPy 3.8 to the test matrix since it's a good validator for cross-implementation compatibility.
I've mainly updated the project infrastructure settings, moved from Travis to GitHub Actions, and removed some legacy Python 2 code that would prevent newer Django version compatibility, there should be no code logic changes at all in this PR.
Django 4.0 and development main branch support is still pending because the source code needs updates to deprecate the use of pytz localize() method usage, but I think that would ideally be solved by another PR as it would change actual code logic?

Great - merged - what do I need to do next here for GitHub Actions?

It seems like the Actions based builds are now properly rolling and working so that should be OK :) They seem to have started functioning with the merge.
Next thing to do would be to probably fix the docs build (seems to be failing for some reason), update the Django 4.0 support and possibly add an automated release pipeline?
I am mostly familiar with the Jazzband release automation and was thinking that I could first try to upgrade the source code for Django 4.0 support, and then open a proposal for the project and PyPI release automation via the Jazzband org if that's OK with you?

That all sounds good to me - thank you so much!


Fix commit_version_bump which required all detected files to change

Now it only needs to be a subset of the detected files.
This should fix issue #470.

Looks good to me, thanks for contributing @Liquidsoul :+1:


Move digests to providers

Checklist

[x] documentation is added or updated
[x] tests are added or updated

The evp_tests fail because the digests are in the legacy provider. Anyone got any nice way of resolving this failure?
The 2nd failure it probably related to the changes that test the output size in the final (appeared after I merged back to master).
Also I wasnt sure what to do with the headers - I assume they should be public so other providers have access to them (rather than just the internal ones). Thoughts anyone?

What do you think of the macros? (they seemed to make sense to use as most things were common in the method tables).

Regarding SHA3, it's completely internal, so I'm wondering it it shouldn't be moved entirely to the providers...

Regarding SHA3, it's completely internal, so I'm wondering it it shouldn't be moved entirely to the providers...
They are still referenced by the legacy const EVP_MD.. So I dont know that its a good idea yet.

ping

ping

Some of the algorithms are fairly new and have no public API; sm3 and blake2 are those I immediately recognise.  With those, you could be more brutal and move all of their base source to providers/common/digests, with additional code to make the proper dispatch tables.  That would also allow you to avoid making header files like blake2_locl.h less private.
What should remain in the end is m_blake2.c, with just an EVP_MD with the NID and all other attributes empty, and blake2_mac.c, which I'm in the process of moving anyway...

@levitte . Can I get this merged in its current state - before I end up in merge hell with your changes :)

I'm strongly opposed to the move of certain headers to include/internal, especially blake2_locl.h.  The way I see it, that's an interim until we've move those files entirely into providers/common.  In that case, I much prefer to see direct inclusions (such as, I imagine, providers/common/digests/blakesomething.c including "../../../crypto/blake2/blake2_locl.h"), clearly marked with a "TODO(3.0)" comment explaining what should happen before the release.  I fully expect a number of such inclusions until we've moved enough stuff.

Isnt that effectively the same as just putting a
TODO(3.0) into the headers that are currently sitting in internal?

rebased and updated commit message

@ping @mattcaswell and @levitte

Ping?

I have general remark: it would be nice if we all could stick to using present term in commit messages when describing the changes made by a pull request. IMO this would not only result in more consistency among the log messages, but also improve readability in the following use case:
Sometimes it makes sense to describe  in a commit message the behaviour of the code before the change together with the description of the change itself (e.g., when the commit fixes a bug). Having two tenses (past tense for the previous behaviour,  present tense for the change) for the two parts really helps the reader sorting those two things apart.
So in your case, the commit message
digests moved to providers

Moved digest code into the relevant providers (fips, default, legacy).
The headers have been temporarily moved into internal, and will be moved
into providers after all external references are resolved. The deprecated
digest code can not be removed until EVP_PKEY (signing) is supported by
providers. EVP_MD data can also not yet be cleaned up for the same reasons.

would become
Move digests to providers

Move digest code into the relevant providers (fips, default, legacy).
The headers are temporarily moved into internal, and will be moved
into providers after all external references are resolved. The deprecated
digest code can not be removed until EVP_PKEY (signing) is supported by
providers. EVP_MD data can also not yet be cleaned up for the same reasons.

(P.S.: every commit will become historical after a while, but this does not mean they need to formulated like historical events...)

@mattcaswell  The 2 commits with !fixup in the name contain the updates.

ping

Commit message lgtm. The review I'll leave to others.

@levitte are you happy with this PR?

Only a trivial rebase to fix the .num file has been done after the approval.

So here's an interesting twist: when SHAKE128 is a fetched algorithm and is then used with HMAC, the code aborts.  Why?  Because EVP_MD_meth_get_flags(md) won't look if there's a provider, or try to get any flags.  The fetched implementation's structure has 0 in the flags field, so the XOF flag can't be set.

It turns out that the deprecation of EVP_MD_CTX_ctrl in favour of EVP_MD_CTX_set_params was premature because you still need to use EVP_MD_CTX_ctrl if you want to do a DigestSign/DigestVerify operation (or if you are using an ENGINE). In those cases you don't have a provider, so we're still using legacy handling. There are actually a couple of instances of this in libssl, so we're going to need to back that change out until DigestSign/DigestVerify works with providers, as well as ENGINEs.

The fetched implementation's structure has 0 in the flags field, so the XOF flag can't be set.

Which means most things need to stay except for the methods.

It turns out that the deprecation of EVP_MD_CTX_ctrl in favour of EVP_MD_CTX_set_params was premature. There are actually a couple of instances of this in libssl, so we're going to need to back that change out until DigestSign/DigestVerify works with providers, as well as ENGINEs.

See https://github.com/openssl/openssl/pull/9103
I dont know how you are testing this.

The fetched implementation's structure has 0 in the flags field, so the XOF flag can't be set.

Which means most things need to stay except for the methods.

No, it means that the provider based digests need to be able to answer about flags.

[extended tests] in the commit message will trigger the extended tests in Travis.

It turns out that the deprecation of EVP_MD_CTX_ctrl in favour of EVP_MD_CTX_set_params was premature because you still need to use EVP_MD_CTX_ctrl if you want to do a DigestSign/DigestVerify operation (or if you are using an ENGINE). In those cases you don't have a provider, so we're still using legacy handling. There are actually a couple of instances of this in libssl, so we're going to need to back that change out until DigestSign/DigestVerify works with providers, as well as ENGINEs.

So it sounds like DigestSign/DigestVerify can't handle when the purely public key algo and the purely MD algo come from different places, is that it?

I dont know how you are testing this.

./config -d --strict-warnings enable-ssl3 enable-ssl3-method
make
make test

So it sounds like DigestSign/DigestVerify can't handle when the purely public key algo and the purely MD algo come from different places, is that it?

No. DigestSign/DigestVerify can only handle legacy EVP_MD objects. We haven't coded the support for providers there yet. There are some complicated interactions between the signing and the digest code which need picking apart, but I was waiting for the provider signing code to go in before tackling that problem.

No. DigestSign/DigestVerify can only handle legacy EVP_MD objects. We haven't coded the support for providers there yet. There are some complicated interactions between the signing and the digest code which need picking apart, but I was waiting for the provider signing code to go in before tackling that problem.

Ok.  Are you working on that, or should someone else tackle it?

Ok. Are you working on that, or should someone else tackle it?

Its on the same critical path as the rand code. I can't do signing until bignum is done. I can't do bignum until rand is done.


context menu on background

Is there any selector with which I can add a context menu to the background?
It would be very useful for adding new nodes at right-clicked position and general commands like changing layout, saving/exporting the graph...

:+1: +1

Use core selector


Is it possible to request Unix Socket with cpr ?

I wonder if we can request unix socket with cpr library ?
Thanks

I add unix socket parameters in cpr https://github.com/whoshuu/cpr/pull/282

Nice. Thanks for your help!

Related issue:
https://github.com/whoshuu/cpr/issues/344


New package: MvNormalCalibration v0.2.1

Registering package: MvNormalCalibration
Repository: https://github.com/RomeoV/MvNormalCalibration.jl
Created by: @RomeoV
Version: v0.2.1
Commit: a5923835cb6b396ba045ec9db93e8136f03245c5
Reviewed by: @RomeoV
Reference: https://github.com/RomeoV/MvNormalCalibration.jl/commit/a5923835cb6b396ba045ec9db93e8136f03245c5#commitcomment-143916999

[noblock] I would probably be prone to mistyping MvNormalCalibration as MVNormalCalibration (capital V), but it’s up to you

@goerz Thanks for your comment. It is named after Distributions.MvNormal, so I think if one is accustomed to typing MvNormal then MvNormalCalibration would be the natural fit.

[noblock] Agreed.
BTW, your response is a blocking comment and you have to edit it to contain [noblock]


Unmet peer dependency issue with angular-cli and @listr2/prompt-adapter-inquirer

Command
other
Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
├─┬ @angular/cli 19.0.0-rc.2
│ └─┬ @listr2/prompt-adapter-inquirer 2.0.17
│   └── ✕ unmet peer @inquirer/prompts@">= 3 < 7": found 7.1.0

RC2 is using 2.0.17 of @listr2/prompt-adapter-inquirer but using an incompatible version of @inquirer/prompts
Minimal Reproduction
pnpm i -g @angular/cli@next
 WARN  1 deprecated subdependencies found<EMAIL_ADDRESS>Packages: +109 -61
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-------------------------------------------------------------
Progress: resolved 500, reused 500, downloaded 0, added 109, done

/Users/andrew/.local/share/pnpm/global/5:
- @angular/cli 18.0.0
+ @angular/cli 19.0.0-rc.2

 WARN  Issues with peer dependencies found
.
└─┬ @angular/cli 19.0.0-rc.2
  └─┬ @listr2/prompt-adapter-inquirer 2.0.17
    └── ✕ unmet peer @inquirer/prompts@">= 3 < 7": found 7.1.0

Exception or Error
WARN  Issues with peer dependencies found

Your Environment
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/

Angular CLI: 19.0.0-rc.2
Node: 22.11.0
Package Manager: npm 10.9.0
OS: darwin arm64

Angular:
...

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1900.0-rc.2
@angular-devkit/core         19.0.0-rc.2
@angular-devkit/schematics   19.0.0-rc.2
@schematics/angular          19.0.0-rc.2

Anything else relevant?
No response

It looks like this was fixed in listr2 by officially expanding the peer dep range without other changes but it's not released yet? https://github.com/listr2/listr2/commit/e68e009ce26c6e646a93bb060029734ca295fee6


Support type promotion for supported datatypes in BGP matching

Problem description
Given the following data
:foo :bar "5"^^xsd:int

and the following sparql query:
select * where { ?s ?p 5 }

We will get an empty result (the cause being that the '5' in the query is a literal of type xsd:integer, not xsd:int, so it is not a direct match).
However, when we instead query:
select * where { ?s ?p ?v . filter(?v = 5) }

We do get a result, because the comparison operator applies type promotion as defined in https://www.w3.org/TR/xpath-functions/#comp.numeric .
Although strictly speaking correct with regards to the SPARQL 1.1 specs, this is un-intuitive. We should consider adding the same type promotion logic we use for comparison operators into BGP matching when typed literals are involved.
Preferred solution
An internal query (algebra) rewrite could be applied to change any StatementPattern involving a typed literal of a recognized datatype into a StatementPattern with a filter condition.
Pending vetting against the full test suite, we can support this as the default behavior by just building it straight into the TupleExprBuilder, while translating the parser AST into an algebra tree. In this case we can support "turning it off" by having a query optimizer check a config param and if set to disable, optimize back into a straight match
Are you interested in contributing a solution yourself?
Yes
Alternatives you've considered
Instead of the preferred approach we could leave the TupleExprBuilder as-is and instead  build it a query optimizer that checks a config param and if set to enable, rewrite the algebra to use a filter/comparison operator (with type promotion). This has the advantage of leaving the default behavior as-is, but a downside is that this conceptually stretches what we mean by "optimization". Also it does not fully address the fact that the current (default) behavior is a little inconsistent.
A third option is to support this by means of a stacked sail. This has the advantage of not needing a new config parameter, but the downside of not easily making it applicable to existing data stores.
Anything else?
This draft proposal is an outcome of this dicussion thread: https://github.com/eclipse/rdf4j/discussions/3804

Fwiw which solution we end up with is heavily dependent on how this affects compliance (I don't see any problems but there may be some test cases in our suite that contradict my reading of the specs), as well as any measurements we can do on performance impact.

Another option is to build this as part of the ExtendedEvaluationStrategy.

Hi
what if this is seen as a form of inference? (and thus, the configurations applies to that inferencer, moving outside the concept of optimization to another metaphor)

@seralf good point. I could imagine that we could support something similar to this by offering an inferencer specific for datatype entailment - or at least a restricted form of datatype entailment. I doubt this would be a forward-chaining inferencer (it would blow up the materialized set of inferred statements too much), but it's possible for an inferencer to work as a query rewriter - tweaking the algebra tree.
After further back-and-forth on the discussion thread, I don't think we want to pursue the original idea of implementing this as part of the core query engine or the extended strategy. The asked-for behavior seems to be non spec-compliant for simple/RDF entailment, and while the original request reported that for example Jena supports this, it turns out that it only does so in one particular (and now legacy) store implementation, and is certainly not standard behavior. But a D-entailment inferencer could probably offer this kind of thing without breaking specs. It also makes it more of an explicit configuration choice on the user's part.


Replace deprecated methods

https://trello.com/c/SMoYZ3RF/322-upgrade-govuk-components-gem-from-330-400
Changes in this PR:
Version 3.0.0 of the view-component gem removes the deprecated slots setter method, now we need to use with_SLOT_NAME instead. See here: https://github.com/ViewComponent/view_component/releases/tag/v3.0.0.
We need to make this change in order to be able to Bump govuk-components from 3.3.0 to 4.0.0. I have made these changes in a separate PR in order to keep the dependabot PR clean and understandable.
NOTE: I found the uses of the deprecated methods by running the specs while using the warn_on_deprecated_slot_setter flag set in our components. There may be deprecated methods used on pages that are not touched by the tests that will still break if/when we upgrade to govuk-components 4.0.0.
Screenshots of UI changes:
Before
After
Next steps:

[ ] Terraform deployment required?

[ ] New development configuration to be shared?

 Upgrade govuk-components gem from 3.3.0 -> 4.0.0


System.BadImageFormatException

Hi,
I'm trying to use the last version of zeroconf(2.8.0) in a project with Xamarin Forms and when I run the project and execute any code from zeroconf it shows this error:
System.BadImageFormatException - Could not resolve field token 0x0400000f
Does anybody knows what's wrong?
Some info about my environment:
Xamarin Community Version: 6.2(build 1821)
Taget Profile: .NET portable - PCL 4.5 - Profile 259
IOS and Android project
Operational System: MacOs Sierra

I would suggest filing an issue with Xamarin...not sure at all, sorry.

@onovotny Does it not work with PCL library (v4.5, Profile111) projects?

It should...but you're not getting a NuGet restore/install error, you seem to be hitting some sort of runtime exception.

Ok, So I'm gonna use dependency services and develop a solution for each platform, thanks!

Closing due to age.


[ACS] warn user that aks browse won't work in Cloud Shell

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

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

Command Guidelines

[X] Each command and parameter has a meaningful description.
[X] Each new command has a test.

(see Authoring Command Modules)

View a preview at https://prompt.ws/r/Azure/azure-cli/5715
This is an experimental preview for @microsoft users.


error when using autocomplete_light.ChoiceField

My autocomplete is :
class ProfessionAutocomplete(autocomplete_light.AutocompleteListBase):
    choices = []
    def choices_for_request(self):
        self.choices = ['dae', 'abc', 'daa']
        return super(ProfessionAutocomplete, self).choices_for_request()

Form is :
from django import forms
class RegisterForm(forms.Form):
    profession = autocomplete_light.ChoiceField('ProfessionAutocomplete')

View is :
def test(request):
    if request.method == 'POST':
        # create a form instance and populate it with data from the request:
        f = RegisterForm(request.POST)
        # check whether it's valid:
        if f.is_valid():
            return HttpResponseRedirect('/thanks/')
    else:
        f = RegisterForm()
    return render(request, 'admin_crm/register_document_edit.html', {'form':f})

However, when I post the resquest with 'dae' as the profession, 'f.is_valid()' failed saying that 'dae' is not a valid choice. What the matter?

What versions ?
Maybe Django is passing unicode and it can't compare with items which are in your str list.

My django version is 1.5.2, python 2.7.5, mac os, firefox browser.
I think it has nothing to do with compare between items in my str list and django unicode, because when I stepped into the error , I found that the choice list of  autocomplete_light.ChoiceField, which was actually empty, didn't change when the ProfessionAutocomplete instance's choices field changed due to override of choices_for_request method. So the error seems to be reasonable.
I think this is a bug. What do you think?

I think that the problem is that you haven't overridden choices_for_values(). So choices_for_values will use choices=[].

I think you haven't got my point.
The choices variable of AutocompleteListBase have been dynamic already. However, the choices variable of ChoiceField, which is assigned at the __init__ period of ChoiceField, is still static. That's why 'dae' is not a valid choice show up.

On Wed, May 13, 2015 at 4:44 AM, zhiyajun11<EMAIL_ADDRESS>wrote:

The choices variable of AutocompleteListBase have been dynamic already.
However, the choices variable of ChoiceField, which is assigned at the
init period of ChoiceField, is still static. That's why 'dae' is not
a valid choice show up.

I'm sorry, but choices_for_request() is for the autocomplete view to render
a list of choices to the user in JS. validate_values() is for the
autocomplete widget to validate choices, so it should be the root cause of
the validation problem.
http://django-autocomplete-light.readthedocs.org/en/stable-2.x.x/api.html#autocomplete_light.autocomplete.base.AutocompleteInterface.validate_values
http://django-autocomplete-light.readthedocs.org/en/stable-2.x.x/api.html#autocomplete-class-api
As I said, that:
class ProfessionAutocomplete(autocomplete_light.AutocompleteListBase):
    choices = []
    def choices_for_request(self):
        self.choices = ['dae', 'abc', 'daa']
        return super(ProfessionAutocomplete, self).choices_for_request()

Is wrong, because obviously choices is set only in one method, and
not in the other. It
If you want to continue that path, override validation.
--
http://yourlabs.org http://blog.yourlabs.org
Customer is king - Le client est roi - El cliente es rey.

The choices variable of AutocompleteListBase has been dynamic already.

That's not how it works. You can't set some instance variable in one request (ajax GET request), and then expect it to still be there in another request (form POST submit).

def validate(self, value):
    """
    Wrap around Autocomplete.validate_values().
    """
    super(FieldBase, self).validate(value)

    # FIXME: we might actually want to change the Autocomplete API to
    # support python values instead of raw values, that would probably be
    # more performant.
    values = self.prepare_value(value)

    if value and not self.autocomplete(values=values).validate_values():
        raise forms.ValidationError('%s cannot validate %s' % (
            self.autocomplete.__name__, value))

The above code, which is the method of FieldBase of autocomplete-light, shows that it failed at super(FieldBase, self).validate(value) , in which is the validation of django's ChoiceField, before validate_values(). That's my problem and what I mean  :).
Maybe I should define my own field to meet my needs.

Nice catch !
There's even a docstring issue there because it doesn't mention the super
call.
It would probably have been better in the beginning to pass the field
instance to the autocomplete instance in that code and let
Autocomplete.validate_values() call field.validate(value). It's a bit
a harsh BC break but might be a good idea for v3.
A perhaps simple way would be to add a field attribute, ie.
ChoiceField('FooAutocomplete', skip_field_validation=True).
What do you think ?

I think that fix works, but I can't release it without making a proper security audit.

It would probably have been better in the beginning to pass the field
instance to the autocomplete instance in that code and let
Autocomplete.validate_values() call field.validate(value). It's a bit
a harsh BC break but might be a good idea for v3.

That's will be fine. But it's not an easy job based on current structure. Hoping for v3 and autocomplete-light is really a nice project. Good luck.

Closing in favor of PR #416 which should be in the next release.

Could you try with 2.2.0rc1 which was released yesterday ?
Thanks.

The backend seems to go well. But there is a js error in the front-end, which result in the disappearing of  prompt box. The error is:
ReferenceError: isOpera is not defined
autocomplete.js line 82

My browser is firefox.


How to use stream setting scan.incremental.snapshot.enabled

I want to use stream setting scan.incremental.snapshot.enabled, but i don't how to use it?

scan.incremental.snapshot.enabled should be used in table options. Pass true or false value for it.


[Quaternion] Missing Essential Functionality

No common mathematical operations exist for the Quaternion type. Also, division does not currently work.

Basic functionality has been added to quaternion. The type is now considered usable.


allow filters to work when listing containers

enable filters when listing containers on the libpod endpoint.
Fixes: #5841
Signed-off-by: Brent Baude<EMAIL_ADDRESS>

/lgtm
/hold

/hold cancel


Fix:30071 - Button of file field in customization product has a smaller height rather than its field

Questions
Answers

Description?
Fix for issue#30071

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes {30071}.

How to test?
Follow Issue reproduce steps.

Possible impacts?
NA.

Can we trigger the CI to make sure it doesn't break anything in the pipeline. Hopping to get it tested by QAs soon.

Hello @Arpit-Gulgulia,
I have tested your PR and it's OK for me. Thank you ! :tada:

Thank you @Arpit-Gulgulia


Compiler failed

`Compiler message:
file:///C:/Users/wangxin/AppData/Roaming/Pub/Cache/hosted/pub.flutter-io.cn/flutter_sticky_header-0.3.4/lib/src/widgets/sticky_header_layout_builder.dart:147:16: Error: The argument type 'String' can't be assigned to the parameter type 'DiagnosticsNode'.

'DiagnosticsNode' is from 'package:flutter/src/foundation/diagnostics.dart' ('file:///D:/ProgramFiles/FlutterSDK/flutter/packages/flutter/lib/src/foundation/diagnostics.dart').
Try changing the type of the parameter, or casting the argument to 'DiagnosticsNode'.
context: context);
^
Compiler failed on D:\workspace\flutter\flutter_pulltorefresh\example\lib\main.dart
Finished with error: Gradle task assembleDebug failed with exit code 1`

不清楚，注意flutter版本还有包是否有引入。另外，这类问题问stackoverflow好点


feature: expose apply function

hi there!
would it be possible to expose the apply function?
thanks for all your work! highly appreciate this package!
cheers!

@gm0stache
This function was added only for test cases, because I wasn't satisfied with evanphx/json-patch and it was buggy for some valid JSON Patches.
However, this package only focuses on the creation of patches, not applying them. Also note that you probably wouldn't want to use the apply function that this package use, because it is not optimized.


fix(deps): update module github.com/tubenhirn/dagger-ci-modules/v4 to v5

This PR contains the following updates:

Package
Type
Update
Change

github.com/tubenhirn/dagger-ci-modules/v4
require
major
v4.4.20 -> v5.0.0

Release Notes

tubenhirn/dagger-ci-modules (github.com/tubenhirn/dagger-ci-modules/v4)
v5.0.0
Compare Source
Bug Fixes

deps: update module dagger.io/dagger to v0.7.3 (45ffd3b)
deps: update module github.com/tubenhirn/dagger-ci-modules/v4 to v4.4.20 (13d15b0)

Features

support new renovate slim/full images (42141b3)

Miscellaneous Chores

deps: update renovate/renovate docker tag to v35.159.3 (5648303)
deps: update renovate/renovate docker tag to v36 (76090f1)
update module version to v5 (785db1a)

BREAKING CHANGE

support new renovate slim/full images

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 5.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bump MRV to 1.42

One of our dependency object us subslice pattern I think it's okay to change our MRV to 1.42.
If we did it we can also use this feature in our code, it should simplify bytes2type.

@luizirber did you have an opinion on this ?

I try to be conservative on the MSRV bumps, but if it is beneficial go for it!

Fixed in #42


[bug]: The enclave argument of kurtosis service logs doesn't have tab-complete enabled

What version of the Kurtosis CLI were you running when you encountered this bug?
0.70.7
(Optional) What is your metrics user ID?
0497e811755b8f775ef0d99cd22b1ef221708b5a95119857a310cbc4f2eabcae
What is the severity of this bug?
Critical, I am blocked and Kurtosis is unusable to us because of this bug.
Description & steps to reproduce
Type kurtosis service logs <TAB> with an existing enclave. Note that no completion happens. Service completion seems to be fine.
Relevant logs from kurtosis enclave dump
No response
Desired behavior
Enclave completion happens as expected.

It does have tab complete enabled but it doesn't work if you restart the engine as it stores uuid / name mapping in memory; wonder if we can change this and fetch everything from disk/docker

I have created #374 that is a best effort fix for this that gets all enclaves registered in the backend in case we our in memory map returns empty (no enclaves registered / restart); longer fix here is to persist identifiers as this doesn't get your removed enclaves for which we might still have logs

For context @Peeeekay ran into this while demo'ing pari


Add properties to set the correct color channels for 850 and 940 IR LEDs

@clarebcook unfortunately i think the best place for this code is in our other repository. It has to do with alot of things that are quite specific to design decisions we made to integrate the system with the MCAM.
We might decide to fully make the illumination portion open source, but now right this second.


Add github actions, upgrade languages and libraries, remove DB from test setup, remove coveralls

I think the only additional thing I'd like to do with this is to wire up a GH action to deploy to hex on release publication, then we can get it merged, release a major version (b/c of the language version bump) and then get the ESM PR merged


Prevent wierd bytestring rendering on py3

When using the plugin with python 3, I was seeing the following rendering:

This PR, should fix that.

Thanks Sarah!


Accessing pyaedt from IronPython Command window

To access the pyaedt from the IronPython command window, I copied the pyaedt folder from the installed location to the this folder
C:\Users....................\Documents\Ansoft\PersonalLib\pyeaedt
but I get this error message when I try to use pyaedt

What should I do now ?

Issue transferred from the PyMAPDL repository. Pinging @ansys/pyaedt-maintainers  for visibility

Hi @SK-mechcoder,
PyAEDT dropped the Ironpython compatibility in v0.9.0, it is documented in the Readme, under the PyAEDT compatibility requirements section:
https://github.com/ansys/pyaedt/blob/main/README.md
As suggested by @mikerife, PyAEDT is a CPython library, but in previous versions PyAEDT gave Ironpython support (during 2 years), to easily transfer old Ironpython scripts to CPython.  PyAEDT roadmap is public: https://github.com/orgs/ansys/projects/12
If you want to use PyAEDT and Ironpython, you will need to download PyAEDT 0.8.11 (the latest version compatible with Ironpython) and paste it into the PersonalLib as you did.
I will close the issue because this is not currently supported, and we encourage you to move to CPython, we have created an easy installer to avoid this kind of problem:
https://aedt.docs.pyansys.com/version/stable/Getting_started/Installation.html#install-from-pyaedt-installer

Thanks for the solution. The doubt raised because of how it is given in the ALH platform.


Rendertron static serving for Facebook, Twitter Crawl

Hi everyone,
I have been trying to serve static rendering with the proper meta tags for the last few days.
Rendertron rendered and serialized all the meta tags we added with react-helmet, however, for some reasons Facebook scrappers did not pick up the meta tags.
This is the command that we used:
curl -v --compressed -H "Range: bytes=0-524288" -H "Connection: close" -A "facebookexternalhit/1.1 (+http://www.facebook.com/externalhit_uatext.php)" https://apicafe.io/
The above command returns results that we expected.
However, running the Facebook scrapper from the debug console returns none of our expected metadata:
https://developers.facebook.com/tools/debug/echo/?q=https%3A%2F%2Fapicafe.io%2F
Apparently it was cut off by the size of the massive inline stylings? How should we resolve this?
Thank you all and have a good day.

That's a great question for Facebook's developer support. As Rendertron produces the relevant HTML, I would report an error via their support options.

Hi @AVGP , do you see anything unusual from my curl above?

Nothing unusual. I tried via Chrome with the relevant UA from the FB bot, too - all good.
I don't know why Facebook's scraper doesn't see the full HTML - and it's not the first time that people struggle with their scraper in general.
As the issue isn't on our end, I don't know what to do with this, unfortunately.

Thanks you for answering me.

@AVGP I've just fix the issue. The problem come from the my end. Because of fetch a lot of style inline css and it's take much time and size to load them so facebook and twitter can't crawl the meta tag after

Interesting. So FB / Twitter have very short timeouts, I guess?

Yes, With following of document of FB, it's required all meta tag must render before the request exceed 1MB.


Generate artefacts

The scripts/generate_artifacts.jl now updates Artifacts.toml based on the tarball hosted at the given (GitHub) link. Whenever the artefact is used in scripts, the same file gets downloaded and decompressed.
I think the artefact-related problems we had in PR #1 are resolved, but @cortner would you mind running the tests locally to check?
If all looks good, ACEData PR #1 can be merged. Then I'll update the links here and merge this PR.

Some notes ...

when you do regression on a different hardware, with different blas, then the errors won't be the same to within machine precision, so you can only test error <= 2 * expected_error or something like that. I'm trying this now.

I had to make a few small changes, but the tests now pass locally

Thank you very much for the tips! I have updated the download links and I think everything works as it should, so I will merge this in a bit.


Using {{for array}} with filtering

I'd like to suggest supporting some JavaScript array functions, so it is not necessary to write and pass helper functions on rendering a template. The most common usage might be filtering, e.g.
{{for people filter=~ageRange minAge=20 maxAge=40}} =>  {{for people.filter(item => item.details.age > 20 && item.details.age < 40)}}...{{/for}}
Others usages:
{{for array sort=~compareFn}}...{{/for}} => {{for array.sort((a, b) => ...)}}...{{/for}}
{{for array reverse=true }}...{{/for}} => {{for array.reverse()}}...{{/for}}
{{for colors start=1 end=-1}}...{{/for}} => {{for colors.slice(1, -1)}}...{{/for}}
etc.

Your examples with array.reverse() or colors.slice() should already work. But the array.sort and people.filter examples you show won't work, because you are declaring functions (in your example, arrow functions) inline within the template markup. That is not something we will be able to support.


mat: Diagonal should be strided

This would allow for Diag.DiagView(), as an example.

I'm going to work right now on adding TriBanded, then we can fix the surrounding Diagonal things.


[Feature]  Allow remote store caching for the profiles file

Description
Similar to PR https://github.com/astronomer/astronomer-cosmos/pull/1147 that allows remote store caching for dbt ls output, enable/support caching remotely the profiles file
Are you willing to submit a PR?

[x] Yes, I am willing to submit a PR!

@dosubot


v0.13.0

Does anyone have any comments / last items before the release? There's been plenty of work on the ADC and of course the new stm32-rs pac v0.15.0 🎉
@burrbull @diondokter @nkrackow @pwnorbitals

The release is on crates.io!


Getting started with Qiskit and introduction to Qiskit tutorials are very similar

Informations

Qiskit version:
Python version:
Operating system:

What is the current behavior?
https://qiskit.org/documentation/intro_tutorial1.html and https://qiskit.org/documentation/tutorials/circuits/1_getting_started_with_qiskit.html are both supposed to be "getting started" guide covering similar topics.
Steps to reproduce the problem
What is the expected behavior?
There should be only one "getting started"
Suggested solutions
We should remove one of these two tutorials

Actually https://qiskit.org/documentation/tutorials/circuits/01_circuit_basics.html is also very similar to the two tutorials mentioned above.

This looks like something I can help with.
Is there something you would like done to start?

@InfamousPlatypus Thank you. To start with, I think it will help if you can do a detailed comparisons of the three so that we can decide which one to keep.

Introduction to Qiskit
Four steps: Build, Compile, Run, Analyze
Example: Simulate 2 qbit circuit with an H and Cnot.
Run, draw and plot.
Workflow Step by Step
Six steps, Import packages, Initialize variables, Add gates, Visualize Circuit, simulate, Visualize results.
Imports Numpy, qiskit QuantumCircuit, aer QasmSimulator, visualization plot_histogram

After that we initialize a 2 qbit circut.
(I do like how this one shows you need 2 registers up front. The others do a better job of showing a separation between the quantum register and classical register though)

Build the circuit (bell state) then measure.
    Basic description of the gates. Keywords (superposition state and entangled state) are highlighted. I feel like this doc has quite sparse links, this may be a good place to use them.

Visualize Circuit
    Just has QC.draw(), but tells us to change the settings.conf to mpl if we prefer that. Also lists valid backends.

Simulate experiment with Aer or basic Aer.
    Qasm simulator
    get_counts

Visualize results
    plot_histogram

Next Steps: tutorials, Textbook, Coding With Qiskit
This is for sure the Introduction. It is most basic, simple and easy to follow. Some sections of the others feel like a wall of text
Getting Started with Qiskit
Two stages, Build and Execute.
Do the imports
Circuit Basics
Building the Circuit
Create a 3 qbit GHZ gate.
Shows what the gates do using math.
Visualize Circuit
Uses mpl
It has a text box explaining endiness, Probably something good to keep.
Simulating circuits with Aer
Statevector backend
Be careful because it returns 2^n where n is the number of qbits
There is a nice tip and note that I did not know. I guess I did not read this tutorial before. I think these are important to know.
Outputs: Statevector, plot_state_city
Unitary Backend
This does not look like the statevector. It's unclear why it's different?
OpenQASM backend
It redoes the circuit with the required classical bits. I can see it's backend is slightly different from the other two and requires measurements.
Version info
This is a lot more math-y. Has some notes that I think were useful.
#Circuit Basics
Uh, this appears to be the same as "Getting Started with Qiskit" but we also draw with latex, qsphere, and hinton. The drawing for OpenQASM also uses mpl instead of text.
Summary
We appear to have two different tutorials, Introduction to Qiskit seems to be best for getting started tutorials. The other two seem to primarily be quick explanations of backends/visualizations and can be merged.

@InfamousPlatypus Thanks for writing the summary. I agree with you that the introduction to Qiskit is the most concise and best suited as the getting started while the other two are very similar. I would vote for removing https://qiskit.org/documentation/tutorials/circuits/1_getting_started_with_qiskit.html and keep https://qiskit.org/documentation/tutorials/circuits/01_circuit_basics.html at least. (may need to make sure the link to the first will redirect to the second) as the first step.

That sounds good, I will do that.

Nevermind, I can't. I thought I saw a way to send one notebook to another, but that's an exploit.

On hold until https://github.com/Qiskit/qiskit/issues/1520 is fixed.

Closing this as it is supersede by  https://github.com/Qiskit/qiskit-terra/issues/10315


Added support for FileVersion, Version, Product and Copyright fields in C# projects

Added support for FileVersion, Version, Product and Copyright fields in C# projects

Merged, thanks!