{modified.sec} seems to not be working in filename template

I am trying to use {modified.sec} in the output file name template.
--filename "{exiftool:EXIF:Make}{media_type}{created.yy}{created.mm}{created.dd}_{modified.sec}"
But osxphotos is outputting _ instead.
photo/2014/October/24/photo_141024 (30).json:[{"SourceFile": "photo_141024 (30).JPG", "ExifToolVersion": "12.00", "FileName": "photo_141024 (30).JPG", "Keywords": ["Fall", "adult cat", "animal", "cat", "feline", "mammal"], "Subject": ["Fall", "adult cat", "animal", "cat", "feline", "mammal"], "TagsList": ["Fall", "adult cat", "animal", "cat", "feline", "mammal"], "DateTimeOriginal": "2014:10:24 15:03:50", "CreateDate": "2014:10:24 15:03:50", "OffsetTimeOriginal": "+00:00", "DateCreated": "2014:10:24", "TimeCreated": "15:03:50+00:00", "ModifyDate": "2014:10:24 15:03:50"}]

Not all files have a modified time.  If the file is edited, modified time is null.

In your example json, you'll see that CreateDate and ModifyDate are the same.  When exporting, Photos sets ModifyDate to CreateDate if the photo has not been modified though internally, Photos stores a null modification date if there are no edits (see issue #247 for the details).  I emulate this behavior in the json export but not in the template.  I suppose the best behavior is to emulate this behavior in the {modified} template so that if there's modification date, it uses the create date.
Does this fit your use case?

Do you mean if there is no modification date then use create date right?
If so then yes that is ok. I am just trying to use the modified second as a way to prevent file name collision.
Actually wondering if it is possible to add a sequence number to the template. Something similar to what Lightroom does. You can specific a starting number and then the sequence updates by one for every file exported. So this way collisions in file names are avoided globally rather than on a per folder basis.
Thanks!
—————
Naren Sankar
On Dec 31, 2020, 12:41 PM +0800, Rhet Turnbull<EMAIL_ADDRESS>wrote:

In your example json, you'll see that CreateDate and ModifyDate are the same. When exporting, Photos sets ModifyDate to CreateDate if the photo has not been modified though internally, Photos stores a null modification date if there are no edits (see issue #247 for the details). I emulate this behavior in the json export but not in the template. I suppose the best behavior is to emulate this behavior in the {modified} template so that if there's modification date, it uses the create date.
Does this fit your use case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Do you mean if there is no modification date then use create date right?

Yes.  That's what the json export does but the template doesn't currently do that.
I've considered doing a global sequence number or even a per folder sequence number but given the current implementation of the template system and the --update code, it would require some significant work.  The update system in particular would have to be able to map the sequence number to a photo in a deterministic way for every export.

Ok. Yes I understand that. Did not think of the update. It will be very problematic to make it work reliably I guess. Can only work for full export.
For now I will just use the modified or created seconds to disambiguate. That should take care of everything except for bursts.
Thanks!
—————
Naren Sankar
On Dec 31, 2020, 1:47 PM +0800, Rhet Turnbull<EMAIL_ADDRESS>wrote:

Do you mean if there is no modification date then use create date right?
Yes. That's what the json export does but the template doesn't currently do that.
I've considered doing a global sequence number or even a per folder sequence number but given the current implementation of the template system and the --update code, it would require some significant work. The update system in particular would have to be able to map the sequence number to a photo in a deterministic way for every export.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

When I get a chance I'll update the {modified} template to use created time if modified time is null.
If your primary need is to avoid collisions, osxphotos will add (1), (2), etc. to the end of the filename if it detects a file with the same name already exists.  (This is what Photos does as well).  This works with --update which searches for the correct file when updating.
Each photo also has a universally unique identifier (UUID) which is how Photos (and osxphotos) manages photos internally.  I could expose that to the template system (issue #314) to allow a guaranteed unique identifier to be added to each file name.  The UUID has format of:
44107FE0-AA2E-4E25-A5F3-60CA63109141

The primary need is to avoid collisions but globally amongst many libraries. So that is why I am trying to use the seconds - so that way it is highly unlikely that everyone in my family took a picture at the exact same second. The current system that osxphotos uses still causes collisions across libraries.
UUID would be good. Maybe the lowest 12 digits or something.
Thanks!
—————
Naren Sankar
On Dec 31, 2020, 2:40 PM +0800, Rhet Turnbull<EMAIL_ADDRESS>wrote:

When I get a chance I'll update the {modified} template to use created time if modified time is null.
If your primary need is to avoid collisions, osxphotos will add (1), (2), etc. to the end of the filename if it detects a file with the same name already exists. (This is what Photos does as well). This works with --update which searches for the correct file when updating.
Each photo also has a universally unique identifier (UUID) which is how Photos (and osxphotos) manages photos internally. I could expose that to the template system (issue #314) to allow a guaranteed unique identifier to be added to each file name. The UUID has format of:
44107FE0-AA2E-4E25-A5F3-60CA63109141
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

In v0.39.3 modified date templates will use creation date if photo has not been modified.

I added {uuid} template in release v0.39.5.  Will work on a short uuid at some future point (#314).

I added {uuid} template in release v0.39.5.  Will work on a short uuid at some future point (#314).


Update .NET 5 literal to .NET 6 or .NET

Update .NET 5 literal to .NET 6 or .NET
This PR updates .NET 5 with .NET 6 or just .NET, depending on context.
Some part of docs I could not update, for example the following text:
Starting with .NET 5, a different approach to establishing uniformity has been adopted, and this new approach eliminates the need for .NET Standard in many scenarios. For more information, see [.NET 5 and .NET Standard](../../standard/net-standard.md#net-5-and-net-standard).

We should remove ".NET 5" from the docs at this point. It is now EOL.

So should I remove/rename all .NET 5 to .NET 6?

I think that text should be reworded to say something like ".NET Standard is not longer recommended. You should target the net family of target frameworks (like net6) for both apps and libraries going forward." We no longer need the "starting with .NET 5" sort of wording. .NET Core 3.1 is not in (or very close) to its maintenance phase. We can assume that all new development is .NET 6.

@terrajobst


2 pieces of 8*32

hi - I like your project - I'm using iobroker
my question: is it somehow possible to add a second matrix in a row and controll it with your software - so we could use 8*64
thanx

got he answer there https://github.com/o0shojo0o/PixelIt/discussions/75

@liv-in-sky did you find a way to chain more matrixes together?

@liv-in-sky did you find a way to chain more matrixes together?

sorry - I didn't pursue it further


[Bug]: Extension install fails in monorepo due to insufficient package manager detection

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
Extension
Expected behavior
Running shopify generate extension in an app folder inside a monorepo should work fine. It should scaffold the extension, and install new dependencies using the correct package manager.
Actual behavior
When creating extensions, during "Installing dependencies ..." the CLI will error out with:
── external error ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Error coming from `npm install<EMAIL_ADDRESS>--save-prod`

Command failed with exit code 1: npm install<EMAIL_ADDRESS>--save-prod
npm WARN ignoring workspace config at /path/to/repo/apps/my-shopify-app/.npmrc
npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:^0.0.0

The CLI did not correct the right package manager (see "Reproduction steps" below). Expected pnpm, but npm was used as a fallback.
Looks like the internal getPackageManager(fromDirectory) tries to check for local lockfiles, but in a monorepo, that would only be found at the root repo directory, but not in the nested app/package directory.
Possible solutions(?):

Add a flag to skip installation

already present in app build and app dev via --skip-dependencies-installation

Improve package manager detection (TBD how)
Add flag to force a specific package manager

not preferred, but already present in app init via --package-manager

Verbose output
...
[DATETIME]: Reading the content of file at package.json...
[DATETIME]: Obtaining the dependency manager in directory /path/to/repo/apps/my-shopify-app...
[DATETIME]: Reading the content of file at package.json...
...

Reproduction steps
Sample monorepo project setup:
./
├── package.json
├── pnpm-lock.yaml
└─┬ apps/
  └─┬ my-shopify-app/
    ├── package.json
    └─┬ extensions/
      └── ...

Sample step:

Run cd apps/my-shopify-app
Run shopify generate extension
Pick any extension that will auto-trigger a package install step, e.g. Checkout UI, and follow the remaining prompts

Operating System
Multi platform
Shopify CLI version (check your project's package.json if you're not sure)
v3.61.2
Shell
No response
Node version (run node -v if you're not sure)
v20.11.1
What language and version are you using in your application?
No response

Hey @echocrow, thanks for the bug report! I've merged a PR to update the package manager detection logic, which should cover your use case.
I should note, however, that the CLI itself uses workspaces in a setup where the workspace root is the app project root, and each extension is a workspace. So if the apps themselves are workspaces, you are now creating nested workspaces.
It's a bit difficult to find explicit documentation about this, but my understanding is that support for nested workspaces among package managers is still a bit iffy, and we can't guarantee that the CLI will work correctly in this setup. There may be a number of bugs we're unable to solve, and since this seems to be a rare setup among our users so far, it is also questionable whether we'll be able to dedicate time even if bugs are fundamentally solvable.
If you're willing to take on those risks, then I earnestly wish you the best of luck pioneering the use of nested workspaces for Shopify apps. Let us know how it goes!

@amcaplan Thanks for the update and fast PR! TIL, npm prefix also works in a pnpm monorepo. ✅
RE workspaces: Cheers for the precautionary note, and well understood! We've already been using this setup successfully for a few months now, including another app that also uses nested ./extensions packages. Both pnpm and turborepo have been working perfectly as expected. Our pnpm-workspace.yaml file looks something like this:
packages:
  - 'apps/*'
  - 'apps/our-other-app/extensions/*'
  - 'apps/shopify/extensions/*'
  - 'packages/*'

Thanks to your PR, we won't have to work around the Shopify CLI anymore. (Previously we'd be passing --skip-dependencies-installation wherever possible, and be limited to scaffolding new extensions in a throw-away repo). There may indeed still be some small caveats, e.g. when  invoking the CLI from the monorepo root instead of after cd apps/shopify. We'll be sure to keep an eye out for those.


Added a login page for future uses

Created a Login Page for future uses

If you'd like to attempt to improve the indenting in the code you could try running npm run prettier:fix (of course after updating your branch locally) and then keep the changes proposed.


Fixups for baseline test script

Small amount of clean up on the baseline script to handle failing
on error.  I also added an option to not use docker at all for platoforms
where docker cannot be installed.
Signed-off-by: baude<EMAIL_ADDRESS>

@TomSweeneyRedHat ptal

bot, retest this please

bot, retest this please

bot, retest this please

bot, retest this please

bot, retest this please

@rh-atomic-bot r+

@rh-atomic-bot retry

@rh-atomic-bot retry


Support for custom pages in UserProfile component

Just managed to do initial implementation of Clerk into our SvelteKit project with this library, and everything has gone pretty smooth.
I tried to customize UserProfile with custom pages, but i think it does not support it.
https://clerk.com/docs/customization/user-profile#add-a-custom-page-to-user-profile
It would be lovely and quite necessary feature to add. We wanna use pre-made components as much as possible, but UserProfile is one that actually needs lot's of our own settings and toggles for user account.
Sincerely, Seppo
And Big Thanks for great library!

I'm on vacation right now but I'll tackle this as soon as I return 🫡


Discuss practical usages of algebraic structures in real world code

At the end of the day, the intention of this library is to provide a common basis for generic programming in Rust. It would be good to experiment with real world use cases, and then use those to drive the design of the library. It would also allow us to convince people of the benefits of this approach. As asked by @nical on gitter:

I'm going to ask some rather silly questions, I am more used to focusing on maths to fix a specific problem (like building a graphics engine) rather than design abstractions around math concepts.
silly question 1) what are the common use cases for high level math abstractions like this ?
Or phrased differently, can we list (roughly) the motivations

At the end of the day, we want this to be of a benefit as opposed to a hindrance. I can certainly see that we could get side-tracked down the route of mathematical taxonomic insanity without considering whether this is actually useful and confusing to end users. Thoughts?

In particular, I am interested in cases where it is more practical and/or useful to reason with abstract vector spaces rather than just implicitly work with a simple euclidean space and the implied rules.
The taxonomy is definitely intimidating, but if it has its uses we should not shy away from accepting it as the right tool for the right job. As a newcomer I don't know what these right jobs are.

[...] to reason with abstract vector spaces rather than just implicitly work with a simple
euclidean space and the implied rules

I'm not sure I understand what you mean here. Are you wondering what is the point of defining traits for vector spaces where we could just work with the exact types like Vector3? What do you mean by simple euclidean space (what is "simple")?

Or phrased differently, can we list (roughly) the motivations

I can give a concrete example by listing the motivations behind my contributions to this library. For ncollide, I need three kinds of abstractions:

dimensional-genericity: most algorithms will work fine for 2D, 3D, et often higher dimensions. There is usually no point in writing a 2D or 3D-specific version because given the proper abstract mechanisms they are all equivalent. Of course some algorithms (like convex hull computation) still require a dedicated implementation in which case we can select the right one at runtime by testing the dimension of the vector space (and this test will probably be optimized away by llvm).

representation-genericity: transformation groups (isometries, rotations, translations,
etc.) are often seen as matrix groups. However, other representations are possible and may be preferred by the user for some reasons. For example, 3D rotations (the group SO(3)) have two major representations: 3x3 matrices and (unit) quaternions. Both have their advantages and inconvenient depending on the applications so I want to let the user choose which one he wants.

substructure-genericity: this one is the most useful and allows code refactoring and performances improvements! I'll take the specific example of ray-casting here, but that applies at many, many places on ncollide. To cast a ray you need three elements:

a geometrical shape s (a ball, a cube, a convex polyhedra, etc.)
the position p of that shape (typically an isometry: translation * rotation * reflexion)
the ray r (its origin and direction).

A typical ray-casting function will thus usually take three arguments: cast_ray(s, p, r) -> hitpoint and returns a hit point. If the implementation works for isometries, it will work for any
of its subgroups as well. Thus p may be a pure rotation or a pure translation. Being generic wrt the transformation group will allow you to sometimes pass for p only a 3D vector (pure
translation), a 3D matrix (pure rotation) or a 3x4 matrix (isometriy). Obviously, the specialized
version using a 3D vector will be faster than the one using the 3x4 matrix.  But it goes even
further! It is not unusual for the positions of the shape to be already encoded inside of the shape data structure itself. For example a ball in space can either be fully described as a center and a radius:
Ball { center: Point, radius: Scalar }

or as a radius alone and a separate transformation matrix:
Ball { radius: Scalar }
Isometry { translation: center, rotation: identity }`

This also applies to more complicated structures (convex polyhedra, triangle meshes, etc.) that may not be rotation-invariant. If we don't have substructure-genericity, a user of cast_ray will be forced to pass a 3x4 matrix which will always be the identity transformation. Obviously multiplying anything by this matrix will be a complete waste of computational time. With substructure-genericity, we can use a very special subgroup of the isometry group: the
0-dimensional subgroup which contains only the identity element. In nalgebra, this is the
Identity structure. The implementation of multiplications by it are all no-ops so the compiler will just remove them when it will specialize the call to cast_ray(s, Identity::new(), r).
By the way, I know that we could just expose ray-casting with cast_ray(s, r) -> hitpoint where r is the ray multiplied by the inverse of p. But all my preceding reasoning applies in more complex situations, e.g., the GJK algorithm, where the multiplication by the transformation must be inside of a loop and may become a bottleneck.
So I need all those kinds of abstractions and they are all well expressed by common mathematical concepts: finite-dimensional vector spaces, group actions and subgroups. Euclidean spaces tie all of them together.

(For people interested in this discussion, it is continuing on gitter).


Adding _remote to comply with PouchDB deprecation notice.

I was getting a lot of warnings while using the newest version of pouchdb-react-native due to db.type() being used. Checking PouchDB's 6.2.0 release. I noticed the following: "deprecate .type() in favor of ._remote". Looking into one of their adapters, I noticed that, for now, they are simply adding api._remote = false to non-http adapters to comply with the deprecation notice.

I noticed a new version was published to npm less than an hour ago immediately after this request was merged in. I checked it out, but it didn't have the fix from this request. When I was looking at the commit feed, I noticed that both pouchdb-react-native and the pouchdb-adapter-asyncstorage were bumped to 6.2.1, but the dependency in pouchdb-react-native for pouchdb-adapter-asyncstorage was left at 6.2.0. Is this why the change seems to be missing, or am I just being overly impatient and the new version has nothing to do with this pull request?
Anyway, thank you for the quick review and merge!

sorry, should be fixed with 6.2.2


The minCompileSdk (31) specified in a dependency's AAR metadata

Description
Hello, I am using version shown below. I need to downgrade sdkversion to 29 to run in my mobile phone, because it crashes when I install apk. When I changed sdk version to 29, and run gradlew assembleRelease It gives me below error.
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkReleaseAarMetadata'.
> A failure occurred while executing com.android.build.gradle.internal.tasks.CheckAarMetadataWorkAction
   > The minCompileSdk (31) specified in a
     dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)
     is greater than this module's compileSdkVersion (android-29).
     Dependency: androidx.work:work-runtime:2.7.1.
     AAR metadata file: C:\Users\.gradle\caches\transforms-3\065a2447fd4e6c84e24a7e1c451d413f\transformed\work-runtime-2.7.1\META-INF\com\android\build\gradle\aar-metadata.properties.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BU¦LD FAILED in 2m 26s

buildscript {
    ext {
        buildToolsVersion = "30.0.2"
        minSdkVersion = 29
        compileSdkVersion = 29
        targetSdkVersion = 29
        ndkVersion = "21.4.7075529"
    }

    "@notifee/react-native": "^5.0.0",
    "@react-navigation/native": "^6.0.8",
    "@react-navigation/stack": "^6.1.1",
    "native-base": "^2.15.2",
    "react": "17.0.2",
    "react-native": "^0.67.4",
    "react-native-gesture-handler": "^2.3.2",
    "react-native-paper": "^4.11.2",
    "react-native-reanimated": "^2.3.0",
    "react-native-safe-area-context": "^4.2.2",
    "react-native-screens": "^3.13.1",
    "react-native-vector-icons": "^9.1.0",
    "reanimated-bottom-sheet": "^1.0.0-alpha.22"

Version
^0.67.4
Output of npx react-native info
System:
OS: Windows 10 10.0.19044
CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Memory: 16.76 GB / 31.82 GB
Binaries:
Node: 15.2.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.14.9 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels: 23, 26, 28, 29, 30, 31
Build Tools: 26.0.3, 28.0.3, 29.0.2, 30.0.0, 30.0.1, 30.0.2, 30.0.3, 31.0.0
System Images: android-23 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom_64, android-30 | Google Play Intel x86 Atom, android-31 | ARM 64 v8a, android-31 | Intel x86 Atom_64
Android NDK: 22.0.7026061
Windows SDK: Not Found
IDEs:
Android Studio: Not Found
Visual Studio: 16.11.31702.278 (Visual Studio Community 2019)
Languages:
Java: 17.0.1 - C:\Program Files\Common Files\Oracle\Java\javapath\javac.EXE
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: ^0.67.4 => 0.67.4
react-native-windows: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
gradlew assembleRelease
Snack, code example, screenshot, or link to a repository
No response

You (or one of your dependency) is using work-runtime-2.7.1 from the Work Manager: https://developer.android.com/jetpack/androidx/releases/work which has a minCompileSdk to 31
You should either:

Bump your minCompileSdk to 31
Remove that dependency, use an older version of it or ask the maintainer to downgrade the WorkManager version.

As an alternative you could force a version of WorkManager to a older one, but that's not recommended.
Closing as this is not related to React Native but to another dependency.

How can I find which dependency using work-runtime-2.7.1. Because app crash during installation apk. I know I need to write 31. But I need to downgrade to 29 and I have less knowledge about it. Because it I am writing here. @cortinico

You can find it by doing so:
cd android && ./gradlew :app:dependencies

Post the output here.

@cortinico Please I am using expo managed workflow and I want to build it but I keep getting the same error. How do I find the dependency that is using this?? And what do I do to fix it? Thank you!!!


Implement Filter for known Disposable Email Providers

This issue is imported from pivotal
This is a list of well-known disposable email providers. We do not want these domains to register for an eduID. Implement a blocklist for these domains. When a user wants ro register a new eduID with one of these domains in the email, deny the creation of the account, and inform the user to contact<EMAIL_ADDRESS>if he thinks the email-domain is valid.

The blocklist can be found at  https://github.com/7c/fakefilter in different formats and should be updated every 24 hours

Reason for this feature is the abuse of eduVPN using eduID accounts created with disposable email adresses (Peter Havekes - Sep 29, 2022)

https://github.com/OpenConext/OpenConext-myconext/commit/edf5b2b470d100cce9256bb044d782620e32dbd0 (Okke Harsta - Oct 1, 2022)

Could you add a feature-toggle for this feature? (Peter Havekes - Oct 3, 2022)

https://github.com/OpenConext/OpenConext-myconext/commit/06f1fabce665fcba1c9d2f9815ac4c6cec5b04b8
https://gitlab.surf.nl/surfconext/surfconext-deploy-environments/-/commit/62d24412cdecb9ada3e298bbd4114fc095f9fe55
https://github.com/OpenConext/OpenConext-deploy/commit/02c7492e5e57eeaa8ef45c6f5497c3cc6428f7b3 (Okke Harsta - Oct 3, 2022)

(Okke Harsta - Oct 3, 2022)


Support sparse pointwise division by vectors or matrices

Closes https://github.com/cupy/cupy/issues/3830
This PR is to support sparse matrix point-wise division by another matrix or vector.

pfnCI, test this please

Jenkins CI test (for commit f1988541157d2bdbe8764e107d14ef0580996910, target branch master) succeeded!

pfnCI, test this please.

Jenkins CI test (for commit ed6d03a0ca26899eef05b847b4ff9ebd6139f500, target branch master) failed with status FAILURE.

The CI issue seems irrelevant to the PR.  Please give me a little more time.

Jenkins, test this please

Jenkins CI test (for commit ed6d03a0ca26899eef05b847b4ff9ebd6139f500, target branch master) succeeded!

Thanks, @emcastillo.
It's nice to backport this PR also because the division by a scalar (#3680) is going to be available in v8.


Check Freshdesk feedback widget

@jfryman proposed to take a look at Freshdesk feedback widget as a replacement for "Report a bug" link to Github issues.
http://freshdesk.com/customer-engagement/feedback-widget

Would you try to just log into https://stackstorm.freshdesk.com with your StackStorm Google account. If that doesn't work, I'll create an account. It should do the needful.

After some experimentation, I remember us left unsatisfied with the whole process of adding new user to admins.
@jfryman what have we decided, are we going to give freshdesk another try or should I close the issue?

@enykeev I actually totally agree. I was really turned off by the apparent lack of integration with Google Apps, which was actually one of my draws to them based on their marketing. I'm not proceeding with them.
Closing for now. Still would like to see something like this, but Freshdesk ain't it.


MAINT: sparse.linalg: Missing tfqmr in the re-entrancy test

Reference issue

What does this implement/fix?

TFQMR implementation is re-entrant, forget to add it to test_reentrancy, this PR fixed the hole.
Additional information

I'm not sure this is intended or not, but test_atol is also missing tfqmr?

There are two point.

I am modifying the PR #15149 (a new GMRES implementation is faster than the original, the former is reentrant and the latter is non-reentrant), and find the reentrant test for tfqmr is missing when adding the new GMRES to test_entrancy.
For tfqmr, the test case in the test_atol is not suitable for TFQMR because the algorithm will be not converged in this extreme case, so a new test case of atol needs to be re-designed in the future version, test_x0_equals_Mb is also same.

Dear Atsushi @AtsushiSakai , this PR is closed but it cannot be reopened because I remove my forked scipy repository by mistake. Could this PR be merged? Thanks.

@zhaog6 I believe this was closed by mistake when the main branch was activated as the default - can you create a new PR with these changes? Thanks!

Dear @melissawm Sorry that I reply so late. Yes, I'll create a new PR. Thank you.


Memory consumption

Hi, I find your paper interesting. However, as a newbie in this field, I am wondering the T (number of frames) used here. Does each dataset samples the same T which are always small? and how much GPU memory will the proposed dense aggregation consumes over prior sparse methods? Thx.

Thank you for your interest in my work. The memory requirements for FreeVA w/ LLaVA-1.5 are as follows:

Method
MLLM
Frames
GPU Memory
MSVD-QA Acc.

FreeVA S1
LLaVA-1.5 7B
4
16.1G
69.6

FreeVA D1
LLaVA-1.5 7B
4
19.1G
70.5

FreeVA D1
LLaVA-1.5 13B
4
32.0G
71.1

FreeVA D2
LLaVA-1.5 13B
8
32.0G
71.8

GPT-3.5-Turbo-0613 API is employed for above evaluation.


Set Up SAP Business Application Studio for Development

Tutorial URL: https://developers.sap.com/tutorials/appstudio-onboarding.html
Hi Raz,
I think the first steps are not needed anymore in trial. One can access the Business Application Studio right from the start from the Quick Tool Access section without subscribing or assigning roles.
Could you check that? It worked for me with a new trial account and I also heard that from others.
Thanks,
René

Hi @renejeglinsky ,
That's correct. For new trial accounts, BAS setup is automated and the subscription si auto-enabled.
I plan to update the tutorial accordingly.
Regards - Raz

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


[SPARK-29512][SQL] REPAIR TABLE should look up catalog/table like v2 commands

What changes were proposed in this pull request?

Add RepairTableStatement and make REPAIR TABLE go through the same catalog/table resolution framework of v2 commands.
Why are the changes needed?

It's important to make all the commands have the same table resolution behavior, to avoid confusing end-users. e.g.
USE my_catalog
DESC t // success and describe the table t from my_catalog
MSCK REPAIR TABLE t // report table not found as there is no table t in the session catalog

Does this PR introduce any user-facing change?

yes. When running MSCK REPAIR TABLE, Spark fails the command if the current catalog is set to a v2 catalog, or the table name specified a v2 catalog.
How was this patch tested?

New unit tests

cc: @cloud-fan @rdblue @viirya

Test build #112294 has started for PR 26168 at commit 6135df9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/17278/
Test PASSed.

Test build #112294 has finished for PR 26168 at commit 6135df9.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class RepairTableStatement(tableName: Seq[String]) extends ParsedStatement

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/112294/
Test PASSed.

Thanks! Merging to master.


Crash Opening Shops & Piggy Bank

Minecraft 1.19.2
Fabric 0.15.0
Numismatic Overhaul 0.2.9
owo-lib 0.9.3
As the title says, the game crashes every time I open any containers from Numismatic Overhaul. I tried to do my due diligence and found that it only crashes when I have Charm (4.4.4) enabled.
Here's the crash report as well:
crash-2023-11-30_04.45.47-server.txt

Duplicate of #49
Installing Charm-Fixer mitigates this problem: https://www.curseforge.com/minecraft/mc-mods/charm-fixer

Duplicate of #49 Installing Charm-Fixer mitigates this problem: https://www.curseforge.com/minecraft/mc-mods/charm-fixer

I had decided to bite the bullet and not use Charm, but it started crashing again...


Improve Async{Poll,Retry} test readbility.

This follows the sugestions from #1441.

This change is

Travis times out again. Is there a way I can retry it?


rule: blank-lines should ignore comments immediately before top level declarations

contract Abc {
}

/*foo bar*/
contract Bcd {
}

This should pass without lint errors from the blank-lines rule because there's a 2-line gap between both contracts.
it should ignore the comment /*foo bar*/

This should include line comments also. I get a warning for this:
contract Abc {
function a() {}

//this function is temporary
function temp() {}
}

@4gn3s yep agreed!
will notify you once this whole mess is sorted out

I'm looking forward to it. The project is great, thanks!

@4gn3s the bug has been fixed in v0.1.7 (latest).
Once you update, traverse to your root dir & run solium --sync, you need not --init again. (sync adds entries for new rules added in the latest version into your .soliumrc.json, I've added indentation)
If you still see it malfunctioning, feel free to re-open the issue=)


Difference between Fortify and Jetstream

Is there difference between kui-laravel-fortify and kui-laravel-jetsrream?
CannI use the kui-laravel-fortify  version in jetstream installation?

kui-laravel-fortify will scaffold ui for laravel/fortify without adding any new functionality related to the back-end, it is just ui for existing laravel/fortify routes because fortify is just a back-end without front-end. but kui-laravel-jetsrream will replace the ui that came with laravel/jetstream already with another ui without adding any new back-end functionality.
so
use kui-laravel-fortify wilh laravel/fortify to generate ui for fortify.
and kui-laravel-jetsrream with laravel/jetstream to replace the laravel/jetstream's ui.


In an environment behind a proxy kurl.sh installer does not configure docker to use proxy

Set up the environment
export HTTP_PROXY=...

edit ~/.curlrc
proxy = ...

Install
curl https://kurl.sh/latest | sudo bash

Create a pod
cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: Pod
metadata:
  name: test-pod
spec:
  containers:
  - name: nginx
    image: nginx
EOF

The pod will fail to start
$ kubectl get pods
NAME            READY   STATUS          RESTARTS   AGE
test-pod        0/1     ErrImagePull    0          74s

After configuring docker with proxy and restarting the service, the image is pulled successfully and the pod is started.

Is this because sudo does not preserve the environment without the -E flag?
curl https://kurl.sh/latest | sudo -E bash

I tested this morning and it worked find with sudo HTTPS_PROXY=x bash ...

Closing this issue as it seems to be resolved


kraft build creates empty Makefile.uk on builds

Describe the bug
After building images for a given path, an empty Makefile.uk file appears which makes the git history of the repository dirty.
This should not be created, or at least should be removed.
Steps to reproduce
No response
Expected behavior
No response
Which architectures were you using or does this bug affect?
No response
Which operating system were you using or does this bug affect?
No response
Relevant log output
No response

I think this is an artifact of the Unikraft core. If we don't touch this file, it complains.


Master

What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 8 committers have signed the CLA.:white_check_mark: heibaijian:white_check_mark: hehechen:white_check_mark: Lloyd-Pottiger:white_check_mark: breezewish:white_check_mark: CalvinNeo:x: ti-srebot:x: pingyu:x: tonyxuqqiYou have signed the CLA already but the status is still pending? Let us recheck it.

We close this pr for now, since it is a waste to our limited ci resource.


Duplicate events firing

Having a problem with vm appearing to create multiple identical event listeners on elements. Repro at https://github.com/hluz/vmEvt.git.
To reproduce execute it and just add new Steps. The second time you add a step it fires two click events (causing two Steps to be created). The third time it fires three click events... Also, deleting existing Step(s) will also increase the number of events being fired the next time you add a new Step.

This can also be observed at https://github.com/arggh/viewmodel-click-bind, just pull the latest changes which updates ViewModel from 4.0.6 -> 4.0.9. The amount of events fired increases on every click.

@arggh, my repro is already at 4.0.9...

@hluz That is the repro which resulted in ViewModel updates 4.0.7, 4.0.8 and 4.0.9, so I thought I'd share the finding that the issue appeared somewhere between 4.0.7 and 4.0.9 and can be easily switched to appear or disappear in a repo that the creator of ViewModel already is familiar with :)

@arggh  Ok. I interpreted that you were saying that 4.0.9 fixes it, since the #214 (the issue your repro relates to) has been closed...

Fixed on v4.0.10

Many thanks!

Reopen if it doesn't work in v4.0.11

v4.0.11 did not regress it. All fine. Thanks.


[BUG] - dist folder missing from installed Select component in node_modules

NextUI Version
<EMAIL_ADDRESS>Describe the bug
Hi,
I install different components with npm.
When I run npm install @nextui-org/select, the component gets correctly added in the package.json et the node_modules folder is created, but I can't import it in my project, I get this error :

Cannot find module '@nextui-org/select' or its corresponding type declarations.

When i go in /node_modules/@nextui-org/select, I find a node_modules folder and not a dist folder as for the other components :

Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

In NextJs 15.0.2 project, run npm install @nextui-org/select

Try to import the component in a NextJs component

Expected behavior
I expect to be able to import the component as any other NextUI component.
Screenshots or Videos
No response
Operating System Version
Windows
Browser
Firefox

Dublicate: https://github.com/nextui-org/nextui/issues/4315

Dublicate: #4315

Not really, I can use many other components like the buttons, forms and all... I just have this issue on the Select component.
I just tried  to install the Chip component and it works.

Ok!
The Version 2.6.7 fixes the issue. for me.

Yes it's all good ! Thank you :)


feat: total divider below

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add symbolic name code generation support to Bicep

Add environmental variable BICEP_SYMBOLIC_NAME_CODEGEN_EXPERIMENTAL to enable experimental symbolic name code generation.

Can you add a description that summarizes the changes?

    private LanguageExpression? ConvertModulePropertyAccess(ModuleSymbol moduleSymbol, SyntaxBase? indexExpression, string propertyName)

indexExpression appears unused. Shouldn't that be incorporated into the expression that gets generated?

Refers to: src/Bicep.Core/Emit/ExpressionConverter.cs:254 in a2f1658. [](commit_id = a2f1658d94732abd1655f026070f5c45339c87a5, deletion_comment = False)

        // TODO - could probably optimize the case where indexExpression is an integer literal and avoid using format() unneccessarily.

Yeah, we should. If you don't want to do it in this one, can you open an issue for it?

Refers to: src/Bicep.Core/Emit/ExpressionConverter.cs:827 in a2f1658. [](commit_id = a2f1658d94732abd1655f026070f5c45339c87a5, deletion_comment = False)

indexExpression appears unused. Shouldn't that be incorporated into the expression that gets generated?

I might be misunderstanding how this stuff works, but wouldn't that have already been taken care of by the creation of the new converter using CreateConverterForIndexReplacement()? I'll remove the unused param.

indexExpression appears unused. Shouldn't that be incorporated into the expression that gets generated?

I might be misunderstanding how this stuff works, but wouldn't that have already been taken care of by the creation of the new converter using CreateConverterForIndexReplacement()? I'll remove the unused param.

If the index expression was already consumed by creating a converter before this was called, then it should be fine.

This is great! Btw, do we need to do anything in the decompiler to block symbolic name templates?

This is great! Btw, do we need to do anything in the decompiler to block symbolic name templates?

Good point. I've created https://github.com/Azure/bicep/issues/4278 to track.


OWASP Dependency Check found 83 Critical Security Vulnerabilities in react-scripts:4.0.1, 3.4.4 package

Hi,
I used OWASP Dependency Check jenkins plugin to detect security vulnerability in my reactjs application built using create-react-app cli. Mainly critical issues are due to these packages present in react-scripts:4.0.1 and 3.4.4
<EMAIL_ADDRESS>><EMAIL_ADDRESS>(most of the issues are due to this package)
<EMAIL_ADDRESS>><EMAIL_ADDRESS>- >=3.0.2
<EMAIL_ADDRESS>>   --<EMAIL_ADDRESS>– upgrade set-value >=3.0.0<EMAIL_ADDRESS>>    --<EMAIL_ADDRESS>- > upgrade merge >=1.2.1
<EMAIL_ADDRESS>><EMAIL_ADDRESS>- <2.0.2, ~<3.0.2
<EMAIL_ADDRESS>><EMAIL_ADDRESS>- > 0.11.2
<EMAIL_ADDRESS>><EMAIL_ADDRESS>- > 4.17.12
Steps to reproduce it.

build react application using create-react-app
use OWASP Dependency Check maven/Jenkins plugin to scan project.
see the report clicking on 'Dependency Check' link once project is built.

Here is snapshot of report.

This is our package.json
"dependencies": {
"@hv/uikit-react-core": "^3.5.1",
"@hv/uikit-react-icons": "^3.1.0",
"@hv/uikit-react-lab": "^3.0.7",
"@material-ui/core": "^4.11.2",
"@material-ui/lab": "^4.0.0-alpha.57",
"@testing-library/jest-dom": "^4.2.4",
"@testing-library/react": "^9.3.2",
"@testing-library/user-event": "^7.1.2",
"axios": "^0.21.1",
"core-js": "^3.8.1",
"dayjs": "1.8.26",
"easy-soap-request": "^4.1.1",
"node-sass": "^4.14.1",
"plotly.js-basic-dist": "^1.58.4",
"react": "^16.13.1",
"react-app-polyfill": "^1.0.6",
"react-cron-builder": "1.0.4",
"react-dom": "^16.13.1",
"react-google-charts": "3.0.15",
"react-idle-timer": "4.2.12",
"react-monaco-editor": "^0.36.0",
"react-redux": "^7.2.0",
"react-router-dom": "^5.1.2",
"react-scripts": "^4.0.1",
"redux": "^4.0.5",
"redux-saga": "^1.1.3",
"xml2js": "^0.4.23"
}
Please suggest a remediation for these issues.

There is no actual vulnerability here. This is a transitive dependency of webpack (a build tool — not a part of your app!), and you can bring it up with them, but we're not using webpack in any way that would cause this vulnerability to affect your project.


Swift Compiler Error (Xcode): No such module 'XPaySDK'

Swift Compiler Error (Xcode): No such module 'XPaySDK'

I do not have this error
Have you been able to resolve it ?

Nope, still having the issue
On 10 May 2024 at 17:28 +0200, PaoloGi @.***>, wrote:

I do not have this error
Have you been able to resolve it ?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Hi @PaoloGi and @alextarana I patched it in my code forcing to use Nexi_XPay (1.2.9) instead of (1.4.6) in the Podfile.lock

Hi, I have the same problem, but @andemengo's  solution doesn't work in my project. You can Help me?

Hi, I have the same problem, but @andemengo's  solution doesn't work in my project. You can Help me?

Hi, I can try! Could you share your Podfile.lock? Thanks.
(Beacuse in my case the problem was related to a pub update that changed few libraries also used by nexi_payment).

Yes for me it's the same, I also used the pub next_payment. Thanks for your help !
This is my Podfile.lock:
PODS:

app_links (0.0.1):

Flutter

connectivity_plus (0.0.1):

Flutter
FlutterMacOS

DKImagePickerController/Core (4.3.9):

DKImagePickerController/ImageDataManager
DKImagePickerController/Resource

DKImagePickerController/ImageDataManager (4.3.9)
DKImagePickerController/PhotoGallery (4.3.9):

DKImagePickerController/Core
DKPhotoGallery

DKImagePickerController/Resource (4.3.9)
DKPhotoGallery (0.0.19):

DKPhotoGallery/Core (= 0.0.19)
DKPhotoGallery/Model (= 0.0.19)
DKPhotoGallery/Preview (= 0.0.19)
DKPhotoGallery/Resource (= 0.0.19)
SDWebImage
SwiftyGif

DKPhotoGallery/Core (0.0.19):

DKPhotoGallery/Model
DKPhotoGallery/Preview
SDWebImage
SwiftyGif

DKPhotoGallery/Model (0.0.19):

SDWebImage
SwiftyGif

DKPhotoGallery/Preview (0.0.19):

DKPhotoGallery/Model
DKPhotoGallery/Resource
SDWebImage
SwiftyGif

DKPhotoGallery/Resource (0.0.19):

SDWebImage
SwiftyGif

file_picker (0.0.1):

DKImagePickerController/PhotoGallery
Flutter

Flutter (1.0.0)
flutter_email_sender (0.0.1):

Flutter

flutter_exit_app (1.1.2):

Flutter

flutter_inappwebview_ios (0.0.1):

Flutter
flutter_inappwebview_ios/Core (= 0.0.1)
OrderedSet (~> 5.0)

flutter_inappwebview_ios/Core (0.0.1):

Flutter
OrderedSet (~> 5.0)

flutter_keyboard_visibility (0.0.1):

Flutter

flutter_native_splash (0.0.1):

Flutter

geocoding_ios (1.0.5):

Flutter

geolocator_apple (1.2.0):

Flutter

image_picker_ios (0.0.1):

Flutter

nexi_payment (1.0.0):

Flutter
Nexi_XPay

Nexi_XPay (1.4.6)
open_file (0.0.1):

Flutter

OrderedSet (5.0.0)
path_provider_foundation (0.0.1):

Flutter
FlutterMacOS

permission_handler_apple (9.3.0):

Flutter

pointer_interceptor_ios (0.0.1):

Flutter

SDWebImage (5.19.2):

SDWebImage/Core (= 5.19.2)

SDWebImage/Core (5.19.2)
shared_preferences_foundation (0.0.1):

Flutter
FlutterMacOS

SwiftyGif (5.4.5)
url_launcher_ios (0.0.1):

Flutter

webview_flutter_wkwebview (0.0.1):

Flutter

DEPENDENCIES:

app_links (from .symlinks/plugins/app_links/ios)
connectivity_plus (from .symlinks/plugins/connectivity_plus/darwin)
file_picker (from .symlinks/plugins/file_picker/ios)
Flutter (from Flutter)
flutter_email_sender (from .symlinks/plugins/flutter_email_sender/ios)
flutter_exit_app (from .symlinks/plugins/flutter_exit_app/ios)
flutter_inappwebview_ios (from .symlinks/plugins/flutter_inappwebview_ios/ios)
flutter_keyboard_visibility (from .symlinks/plugins/flutter_keyboard_visibility/ios)
flutter_native_splash (from .symlinks/plugins/flutter_native_splash/ios)
geocoding_ios (from .symlinks/plugins/geocoding_ios/ios)
geolocator_apple (from .symlinks/plugins/geolocator_apple/ios)
image_picker_ios (from .symlinks/plugins/image_picker_ios/ios)
nexi_payment (from .symlinks/plugins/nexi_payment/ios)
open_file (from .symlinks/plugins/open_file/ios)
path_provider_foundation (from .symlinks/plugins/path_provider_foundation/darwin)
permission_handler_apple (from .symlinks/plugins/permission_handler_apple/ios)
pointer_interceptor_ios (from .symlinks/plugins/pointer_interceptor_ios/ios)
shared_preferences_foundation (from .symlinks/plugins/shared_preferences_foundation/darwin)
url_launcher_ios (from .symlinks/plugins/url_launcher_ios/ios)
webview_flutter_wkwebview (from .symlinks/plugins/webview_flutter_wkwebview/ios)

SPEC REPOS:
trunk:
- DKImagePickerController
- DKPhotoGallery
- Nexi_XPay
- OrderedSet
- SDWebImage
- SwiftyGif
EXTERNAL SOURCES:
app_links:
:path: ".symlinks/plugins/app_links/ios"
connectivity_plus:
:path: ".symlinks/plugins/connectivity_plus/darwin"
file_picker:
:path: ".symlinks/plugins/file_picker/ios"
Flutter:
:path: Flutter
flutter_email_sender:
:path: ".symlinks/plugins/flutter_email_sender/ios"
flutter_exit_app:
:path: ".symlinks/plugins/flutter_exit_app/ios"
flutter_inappwebview_ios:
:path: ".symlinks/plugins/flutter_inappwebview_ios/ios"
flutter_keyboard_visibility:
:path: ".symlinks/plugins/flutter_keyboard_visibility/ios"
flutter_native_splash:
:path: ".symlinks/plugins/flutter_native_splash/ios"
geocoding_ios:
:path: ".symlinks/plugins/geocoding_ios/ios"
geolocator_apple:
:path: ".symlinks/plugins/geolocator_apple/ios"
image_picker_ios:
:path: ".symlinks/plugins/image_picker_ios/ios"
nexi_payment:
:path: ".symlinks/plugins/nexi_payment/ios"
open_file:
:path: ".symlinks/plugins/open_file/ios"
path_provider_foundation:
:path: ".symlinks/plugins/path_provider_foundation/darwin"
permission_handler_apple:
:path: ".symlinks/plugins/permission_handler_apple/ios"
pointer_interceptor_ios:
:path: ".symlinks/plugins/pointer_interceptor_ios/ios"
shared_preferences_foundation:
:path: ".symlinks/plugins/shared_preferences_foundation/darwin"
url_launcher_ios:
:path: ".symlinks/plugins/url_launcher_ios/ios"
webview_flutter_wkwebview:
:path: ".symlinks/plugins/webview_flutter_wkwebview/ios"
SPEC CHECKSUMS:
app_links: e70ca16b4b0f88253b3b3660200d4a10b4ea9795
connectivity_plus: ddd7f30999e1faaef5967c23d5b6d503d10434db
DKImagePickerController: 946cec48c7873164274ecc4624d19e3da4c1ef3c
DKPhotoGallery: b3834fecb755ee09a593d7c9e389d8b5d6deed60
file_picker: 817ab1d8cd2da9d2da412a417162deee3500fc95
Flutter: e0871f40cf51350855a761d2e70bf5af5b9b5de7
flutter_email_sender: 10a22605f92809a11ef52b2f412db806c6082d40
flutter_exit_app: f2e47c6d0b9c5137c33fab74bc4a9d5d54113bdc
flutter_inappwebview_ios: 97215cf7d4677db55df76782dbd2930c5e1c1ea0
flutter_keyboard_visibility: 0339d06371254c3eb25eeb90ba8d17dca8f9c069
flutter_native_splash: edf599c81f74d093a4daf8e17bd7a018854bc778
geocoding_ios: d7460f56e80e118d57678efe5c2cdc888739ff18
geolocator_apple: 6cbaf322953988e009e5ecb481f07efece75c450
image_picker_ios: b545a5f16c0fa88e3ecbbce3ed4de45567a8ec18
nexi_payment: 16aa9f86a00369c8b41704f15cf0d0e3ba5998be
Nexi_XPay: ed96855029e3b9fb21be07e79e16656c7e6f8f35
open_file: 02eb5cb6b21264bd3a696876f5afbfb7ca4f4b7d
OrderedSet: aaeb196f7fef5a9edf55d89760da9176ad40b93c
path_provider_foundation:<PHONE_NUMBER>ac71e43754bd15e0653ccfd36a147c
permission_handler_apple:<PHONE_NUMBER>a2b0d0fc1e048d9f43605f92e6cec2
pointer_interceptor_ios: 508241697ff0947f853c061945a8b822463947c1
SDWebImage: dfe95b2466a9823cf9f0c6d01217c06550d7b29a
shared_preferences_foundation: b4c3b4cddf1c21f02770737f147a3f5da9d39695
SwiftyGif: 706c60cf65fa2bc5ee0313beece843c8eb8194d4
url_launcher_ios: 6116280ddcfe98ab8820085d8d76ae7449447586
webview_flutter_wkwebview: 2a23822e9039b7b1bc52e5add778e5d89ad488d1
PODFILE CHECKSUM: 53c9414f86d2ea46d5da661b739f619265a12e02
COCOAPODS: 1.15.2

Yes for me it's the same, I also used the pub next_payment. Thanks for your help !
This is my Podfile.lock:
PODS:

app_links (0.0.1):

Flutter

connectivity_plus (0.0.1):

Flutter

FlutterMacOS

DKImagePickerController/Core (4.3.9):

DKImagePickerController/ImageDataManager

DKImagePickerController/Resource

DKImagePickerController/ImageDataManager (4.3.9)

DKImagePickerController/PhotoGallery (4.3.9):

DKImagePickerController/Core

DKPhotoGallery

DKImagePickerController/Resource (4.3.9)

DKPhotoGallery (0.0.19):

DKPhotoGallery/Core (= 0.0.19)

DKPhotoGallery/Model (= 0.0.19)

DKPhotoGallery/Preview (= 0.0.19)

DKPhotoGallery/Resource (= 0.0.19)

SDWebImage

SwiftyGif

DKPhotoGallery/Core (0.0.19):

DKPhotoGallery/Model

DKPhotoGallery/Preview

SDWebImage

SwiftyGif

DKPhotoGallery/Model (0.0.19):

SDWebImage

SwiftyGif

DKPhotoGallery/Preview (0.0.19):

DKPhotoGallery/Model

DKPhotoGallery/Resource

SDWebImage

SwiftyGif

DKPhotoGallery/Resource (0.0.19):

SDWebImage

SwiftyGif

file_picker (0.0.1):

DKImagePickerController/PhotoGallery

Flutter

Flutter (1.0.0)

flutter_email_sender (0.0.1):

Flutter

flutter_exit_app (1.1.2):

Flutter

flutter_inappwebview_ios (0.0.1):

Flutter

flutter_inappwebview_ios/Core (= 0.0.1)

OrderedSet (~> 5.0)

flutter_inappwebview_ios/Core (0.0.1):

Flutter

OrderedSet (~> 5.0)

flutter_keyboard_visibility (0.0.1):

Flutter

flutter_native_splash (0.0.1):

Flutter

geocoding_ios (1.0.5):

Flutter

geolocator_apple (1.2.0):

Flutter

image_picker_ios (0.0.1):

Flutter

nexi_payment (1.0.0):

Flutter

Nexi_XPay

Nexi_XPay (1.4.6)

open_file (0.0.1):

Flutter

OrderedSet (5.0.0)

path_provider_foundation (0.0.1):

Flutter

FlutterMacOS

permission_handler_apple (9.3.0):

Flutter

pointer_interceptor_ios (0.0.1):

Flutter

SDWebImage (5.19.2):

SDWebImage/Core (= 5.19.2)

SDWebImage/Core (5.19.2)

shared_preferences_foundation (0.0.1):

Flutter

FlutterMacOS

SwiftyGif (5.4.5)

url_launcher_ios (0.0.1):

Flutter

webview_flutter_wkwebview (0.0.1):

Flutter

DEPENDENCIES:

app_links (from .symlinks/plugins/app_links/ios)

connectivity_plus (from .symlinks/plugins/connectivity_plus/darwin)

file_picker (from .symlinks/plugins/file_picker/ios)

Flutter (from Flutter)

flutter_email_sender (from .symlinks/plugins/flutter_email_sender/ios)

flutter_exit_app (from .symlinks/plugins/flutter_exit_app/ios)

flutter_inappwebview_ios (from .symlinks/plugins/flutter_inappwebview_ios/ios)

flutter_keyboard_visibility (from .symlinks/plugins/flutter_keyboard_visibility/ios)

flutter_native_splash (from .symlinks/plugins/flutter_native_splash/ios)

geocoding_ios (from .symlinks/plugins/geocoding_ios/ios)

geolocator_apple (from .symlinks/plugins/geolocator_apple/ios)

image_picker_ios (from .symlinks/plugins/image_picker_ios/ios)

nexi_payment (from .symlinks/plugins/nexi_payment/ios)

open_file (from .symlinks/plugins/open_file/ios)

path_provider_foundation (from .symlinks/plugins/path_provider_foundation/darwin)

permission_handler_apple (from .symlinks/plugins/permission_handler_apple/ios)

pointer_interceptor_ios (from .symlinks/plugins/pointer_interceptor_ios/ios)

shared_preferences_foundation (from .symlinks/plugins/shared_preferences_foundation/darwin)

url_launcher_ios (from .symlinks/plugins/url_launcher_ios/ios)

webview_flutter_wkwebview (from .symlinks/plugins/webview_flutter_wkwebview/ios)

SPEC REPOS:
trunk:
- DKImagePickerController

- DKPhotoGallery

- Nexi_XPay

- OrderedSet

- SDWebImage

- SwiftyGif

EXTERNAL SOURCES:
app_links:
:path: ".symlinks/plugins/app_links/ios"

connectivity_plus:
:path: ".symlinks/plugins/connectivity_plus/darwin"

file_picker:
:path: ".symlinks/plugins/file_picker/ios"

Flutter:
:path: Flutter

flutter_email_sender:
:path: ".symlinks/plugins/flutter_email_sender/ios"

flutter_exit_app:
:path: ".symlinks/plugins/flutter_exit_app/ios"

flutter_inappwebview_ios:
:path: ".symlinks/plugins/flutter_inappwebview_ios/ios"

flutter_keyboard_visibility:
:path: ".symlinks/plugins/flutter_keyboard_visibility/ios"

flutter_native_splash:
:path: ".symlinks/plugins/flutter_native_splash/ios"

geocoding_ios:
:path: ".symlinks/plugins/geocoding_ios/ios"

geolocator_apple:
:path: ".symlinks/plugins/geolocator_apple/ios"

image_picker_ios:
:path: ".symlinks/plugins/image_picker_ios/ios"

nexi_payment:
:path: ".symlinks/plugins/nexi_payment/ios"

open_file:
:path: ".symlinks/plugins/open_file/ios"

path_provider_foundation:
:path: ".symlinks/plugins/path_provider_foundation/darwin"

permission_handler_apple:
:path: ".symlinks/plugins/permission_handler_apple/ios"

pointer_interceptor_ios:
:path: ".symlinks/plugins/pointer_interceptor_ios/ios"

shared_preferences_foundation:
:path: ".symlinks/plugins/shared_preferences_foundation/darwin"

url_launcher_ios:
:path: ".symlinks/plugins/url_launcher_ios/ios"

webview_flutter_wkwebview:
:path: ".symlinks/plugins/webview_flutter_wkwebview/ios"

SPEC CHECKSUMS:
app_links: e70ca16b4b0f88253b3b3660200d4a10b4ea9795
connectivity_plus: ddd7f30999e1faaef5967c23d5b6d503d10434db
DKImagePickerController: 946cec48c7873164274ecc4624d19e3da4c1ef3c
DKPhotoGallery: b3834fecb755ee09a593d7c9e389d8b5d6deed60
file_picker: 817ab1d8cd2da9d2da412a417162deee3500fc95
Flutter: e0871f40cf51350855a761d2e70bf5af5b9b5de7
flutter_email_sender: 10a22605f92809a11ef52b2f412db806c6082d40
flutter_exit_app: f2e47c6d0b9c5137c33fab74bc4a9d5d54113bdc
flutter_inappwebview_ios: 97215cf7d4677db55df76782dbd2930c5e1c1ea0
flutter_keyboard_visibility: 0339d06371254c3eb25eeb90ba8d17dca8f9c069
flutter_native_splash: edf599c81f74d093a4daf8e17bd7a018854bc778
geocoding_ios: d7460f56e80e118d57678efe5c2cdc888739ff18
geolocator_apple: 6cbaf322953988e009e5ecb481f07efece75c450
image_picker_ios: b545a5f16c0fa88e3ecbbce3ed4de45567a8ec18
nexi_payment: 16aa9f86a00369c8b41704f15cf0d0e3ba5998be
Nexi_XPay: ed96855029e3b9fb21be07e79e16656c7e6f8f35
open_file: 02eb5cb6b21264bd3a696876f5afbfb7ca4f4b7d
OrderedSet: aaeb196f7fef5a9edf55d89760da9176ad40b93c
path_provider_foundation:<PHONE_NUMBER>ac71e43754bd15e0653ccfd36a147c
permission_handler_apple:<PHONE_NUMBER>a2b0d0fc1e048d9f43605f92e6cec2
pointer_interceptor_ios: 508241697ff0947f853c061945a8b822463947c1
SDWebImage: dfe95b2466a9823cf9f0c6d01217c06550d7b29a
shared_preferences_foundation: b4c3b4cddf1c21f02770737f147a3f5da9d39695
SwiftyGif: 706c60cf65fa2bc5ee0313beece843c8eb8194d4
url_launcher_ios: 6116280ddcfe98ab8820085d8d76ae7449447586
webview_flutter_wkwebview: 2a23822e9039b7b1bc52e5add778e5d89ad488d1
PODFILE CHECKSUM: 53c9414f86d2ea46d5da661b739f619265a12e02
COCOAPODS: 1.15.2

I see Nexi_XPay (1.4.6)
Change it with 1.2.9, clean and build again. Please do not update any dependencies only flutter clean, pub get, and build. Let me know!


Provide a Default Policy for Built-In Retries via Resiliency

In what area(s)?
/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the proposal
With the initial launch of Resiliency in 1.7, we should provide an easier way for people to adopt it. Specifically, there will be a time when we want people to move to Resiliency and remove the internal, built-in Dapr retries. This proposal is to get users to a place where they can more confidently adopt Resiliency without worrying that they'll lose all the retries that Dapr provides.
Existing Retries
Dapr performs it's own retries in a few places already (this list may not be complete):

Service invocation (specifically calling remote hosts)
Actor invocation (specifically calling remote hosts)
Actor state management (retries around storing reminders)
Internal initialization (listing subscriptions, listing components)

Aside from the internal calls, the above calls can be covered by a Resiliency policy. As of 1.7, they exist in tandem with the Resiliency policy, which can cause more retries than intended.
The goal here will be to allow users to easily cover the existing retries and give them an avenue for using only Resiliency for all of their retry/backoff needs.
Providing a Default Configuration
The easiest way to do this will be to provide a default configuration for Dapr's own retries. This configuration will use special names that we can recognize where retries exist and utilize them in our code base. This is necessary because Resiliency targets specific entities. The built-in retries are global. So, we'll need a way to make the policies recognize the global aspect of it.
This configuration can either be provided by default or setup by the customer. For an initial revision, it would be good to bundle it with Dapr so users are guaranteed their retries. Resiliency allows the setting of multiple policies (in k8s) and thus anything the customer wishes to set can be added without having to touch this configuration.
The policy itself will be provided in our documentation, but in Dapr, it will exist as part of the base level structure and be loaded into memory as a constant. The reason for this is that there has been a concern with users deleting/removing built-in retries entirely without intending to. By having it as an in-memory constant as part of the binary, the customer won't be able to delete it without explicitly overriding it. That can be accomplished by taking the documented configuration and changing the values which will override it, but not delete it. If a user goes through this much effort to override the built-ins we can assume they are a power user and responsible for their own actions.
Utilizing the Configuration/Opting-Out of Built-ins
Built-in retries don't always take place in the same area of code that the Resiliency policy retries do. So, in order to allow customers to utilize their own policy/opt-out of built-in retries we need to reference the policies in multiple places.
The new policies that we're defining are intended to be global as we don't know the name of every customer service/actor/component. As such, they can be seen as a default or fall-through policy. So, in the areas where we utilize them, we simply need to check to see if there is a user set policy covering the given target.
In short, we will utilize user defined policies first and only default to the built-in.
Yes, this does mean they can define a policy with less retries than the built-in, but they have actively defined the policy. A valid use case is for them to not want to retry certain things and that has to be supported.
Summary
This proposal intends to:

Provide an in-memory constant policy that represents the existing built-in retries
Reference that policy in areas where we are performing built-in retries
Let users override the defaults by setting their own
Not use the default if a user has defined a more specific policy

@halspang for service invocation -- could we also have circuitbreakers that can use a scope of per app, per path, or both? similar to how we have scopes for actors?

@berndverst mentioned that this sounds like it could cover all defaults, like all bindings/statestores/etc. The goal here is just to cover the built-in retries that Dapr already has, but as a future thought, we could use a similar thing here to cover all operations. This does let users simplify their policies if they have a lot of components for example.
Food for thought, not planning on targeting it here but I see the value in it for the future.

@halspang for service invocation -- could we also have circuitbreakers that can use a scope of per app, per path, or both? similar to how we have scopes for actors?

That's something we could add. I think it'd be worth compiling an issue with ideas for future thoughts of Resiliency, in addition to the Phase 2 plans already in the original issue. I'll open one for discussion later :)

Aside from the internal calls, the above calls can be covered by a Resiliency policy. As of 1.7, they exist in tandem with the Resiliency policy, which can cause more retries than intended.

The service invocation API has an internal retry that needs to retry based on a very specific gRPC status code (Unauthenticated). How do we enable that with a Resiliency policy today?

The goal here will be to allow users to easily cover the existing retries and give them an avenue for using only Resiliency for all of their retry/backoff needs.

I'm not sure this sentence is accurate (specifically the give them an avenue for using only Resiliency part) because users do not proactively use any internal retries today. It's completely transparent to them and used to ensure the very basic reliability and/or stability of a call.

The service invocation API has an internal retry that needs to retry based on a very specific gRPC status code (Unauthenticated). How do we enable that with a Resiliency policy today?

Resiliency policies just retry on errors, they don't care what they are except for 2 special cases for Circuit Breakers that indicate a permanent failure. What you can do though is:
policy(func(ctx context.Context) error {
    err := grpcStuff()
    if errors.Is(err, grpc.Unauthenticated) {
        return err
    }
    return nil
})

I'm not sure this sentence is accurate (specifically the give them an avenue for using only Resiliency part) because users do not proactively use any internal retries today. It's completely transparent to them and used to ensure the very basic reliability and/or stability of a call.

What I'm going for here is to bring the built-in retries into the resiliency space so that we can master everything under one path. Since we provide defaults, most people will never have to use the built-in retries, but if you are so inclined you could now interact with it more directly through your resiliency policy.

To make that overwriting part a bit clearer, here's what I'm thinking terms of the default policy and how a customer can overwrite it. Yaron, if you don't think overwriting is a good idea for now, we can also reserve these names and error out if they try and overwrite them.
In-Memory Constant
apiVersion: dapr.io/v1alpha1
kind: Resiliency
metadata:
  name: resiliency
spec:
  policies:
    retries:
      DaprServiceInvocationRetry:
        policy: constant
        duration: 5s
        maxRetries: 10

      # These might be folded into 1 if their values in the runtime are the same.
      DaprActorInvocationRetry:
        policy: constant
        duration: 5s
        maxRetries: 10

targets:
    # Note that both targets only have retries.
    apps:
      DaprDefaulServiceTarget:
        retry: DaprServiceInvocationRetry

    actors:
      DaprDefaultActorTarget:
        retry: DaprActorInvocationRetry

User Overwrite
apiVersion: dapr.io/v1alpha1
kind: Resiliency
metadata:
  name: resiliency
spec:
  policies:
    timeouts:
      fiveSeconds: 5s

    retries:
      DaprServiceInvocationRetry:
        policy: constant
        duration: 5s
        maxRetries: 5 # Default now has 5 retries.

      retryForever:
        policy: exponential
        maxInterval: 15s
        maxRetries: 0 # Retry indefinitely

targets:
    # Note that both targets only have retries.
    apps:
      DaprDefaulServiceTarget:
        retry: DaprServiceInvocationRetry
        timeout: fiveSeconds # Introduce a timeout to default service invocation.

    actors:
      DaprDefaultActorTarget:
        retry: retryForever # Change the retry policy for default actors.

So like I said, the goal is to allow users full control, but to do everything for them if they don't want to actually engage. Thoughts, @yaron2? Again, if you don't think it's wise for us to be able to overwrite the defaults, we can reserve these keywords. Though I still think we shouldn't use the policy at all if the user has defined one for that specific target.
@berndverst - This is an example of what I was talking about ^

@artursouza / @yaron2 - Any more thoughts here before I get started on an implementation?

In short, we will utilize user defined policies first and only default to the built-in.

Yes, this does mean they can define a policy with less retries than the built-in, but they have actively defined the policy. A valid use case is for them to not want to retry certain things and that has to be supported.

This does mean that they have to define the policy for that building block specifically otherwise the default policy would be used right? As in if user defines policy only for Actors, the default policy for service invocation should not be ignored. Is that correct?

Not use the default if a user has defined a more specific policy

In 1.7 if my understanding is correct, even if a more specific policy is defined, the default retries exist for the more generic use case. For example even if a user defines service invocation policy for specific remote hosts, the default retry policy of constant retries still exists and is executed for other remote hosts. Isn't that the case today?

@mukundansundar

This does mean that they have to define the policy for that building block specifically otherwise the default policy would be used right? As in if user defines policy only for Actors, the default policy for service invocation should not be ignored. Is that correct?

That is correct. We'll use the default policy where they don't define a more specific one. So if they only specify actors we'll use the default for service. It is worth noting though, that this is trying to cover just the retries that exist, it doesn't intend to give a full "backup" policy for every component. That being said though, it seems a logical next step after this as this code would enable it.

In 1.7 if my understanding is correct, even if a more specific policy is defined, the default retries exist for the more generic use case. For example even if a user defines service invocation policy for specific remote hosts, the default retry policy of constant retries still exists and is executed for other remote hosts. Isn't that the case today?

Also correct. We decided that without a good way to migrate away from built-ins we would rather do more retries as opposed to accidentally no retries.


Test min

Before
=== 290 failed, 534 passed, 1810 skipped, 2 warnings in 27.88s ===
After
=== 287 failed, 537 passed, 1810 skipped, 2 warnings in 28.06s ===
Issue: _broadcasted was returning float32 results for scalar operations like 0.0 - self.

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/tensor.py                         1               2
------------------------------------------------------------
lines added in the tinygrad folder: -1


Fix an error for Lint/EmptyConditionalBody

This PR fixes an error for Lint/EmptyConditionalBody when missing if body and using method call for return value.
if condition
end.do_something

% rubocop lint_empty_conditional_body.rb --only Lint/EmptyConditionalBody -d
(snip)

undefined method `loc' for :do_something:Symbol
/Users/koic/src/github.com/rubocop/rubocop/lib/rubocop/cop/mixin/comments_help.rb:72:in `find_end_line'
/Users/koic/src/github.com/rubocop/rubocop/lib/rubocop/cop/mixin/comments_help.rb:20:in `comments_in_range'
/Users/koic/src/github.com/rubocop/rubocop/lib/rubocop/cop/mixin/comments_help.rb:15:in `contains_comments?'
/Users/koic/src/github.com/rubocop/rubocop/lib/rubocop/cop/lint/empty_conditional_body.rb:72:in `on_if'

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


Iterate directly over index ranges in EditDistance

In the EditDistance.calcDamerauLevenshtein function, modify the for loops to iterate directly over the index ranges instead of creating intermediate lists from the ranges and iterating over those lists.
cc @forki

There's a slightly faster way to implement levenshtein distance
Here's the implementation and my benchmark results using BenchmarkDotNet
open System
open System.IO
open BenchmarkDotNet.Attributes
open BenchmarkDotNet.Running

let private min3 a b c = min a (min b c)

let levenshtein (s: string) (t: string) =
    let distance (m, u) (n, v) =
        let d1 = Array.init n id
        let d0 = Array.create n 0
        for i=1 to m-1 do
            d0.[0] <- i
            let ui = u i
            for j=1 to n-1 do
                d0.[j] <- 1 + min3 d1.[j] d0.[j-1] (d1.[j-1] + if ui = v j then -1 else 0)
            Array.blit d0 0 d1 0 n
        d0.[n-1]
    distance (s.Length, fun i -> s.[i]) (t.Length, fun i -> t.[i])

let private calcDamerauLevenshtein (a:string, b:string) =
    let m = b.Length + 1
    let mutable lastLine = Array.init m id
    let mutable lastLastLine = Array.zeroCreate m
    let mutable actLine = Array.zeroCreate m

    for i in 1 .. a.Length do
        actLine.[0] <- i
        for j in 1 .. b.Length do
            let cost = if a.[i-1] = b.[j-1] then 0 else 1
            let deletion = lastLine.[j] + 1
            let insertion = actLine.[j-1] + 1
            let substitution = lastLine.[j-1] + cost
            actLine.[j] <-
              deletion
              |> min insertion
              |> min substitution

            if i > 1 && j > 1 then
              if a.[i-1] = b.[j-2] && a.[i-2] = b.[j-1] then
                  let transposition = lastLastLine.[j-2] + cost
                  actLine.[j] <- min actLine.[j] transposition

        // swap lines
        let temp = lastLastLine
        lastLastLine <- lastLine
        lastLine <- actLine
        actLine <- temp

    lastLine.[b.Length]

let CalcEditDistance (a:string) (b:string) =
    if a.Length > b.Length then
        calcDamerauLevenshtein(a, b)
    else
        calcDamerauLevenshtein(b, a)

let getStrings len = Array.init len (fun _ -> Path.GetRandomFileName())

type EditDistanceComparison () =
    let mutable arr : string [] = [||]

    [<Params (100, 500, 1000, 2000)>]
    member val public ArrayLength = 0 with get, set

    [<Setup>]
    member self.SetupData() =
        arr <- getStrings self.ArrayLength

    [<Benchmark>]
    member self.CalcEditDistance() =
        arr |> Array.iter (CalcEditDistance "targetstring" >>ignore)

    [<Benchmark>]
    member self.Levenshtein () =
        arr |> Array.iter (levenshtein "targetstring" >>ignore)

let [<EntryPoint>] main args =
    (BenchmarkSwitcher [|typeof<EditDistanceComparison>|]).Run args
    |> string |> printfn "%s"
    0

Benchmark Results

Host Process Environment Information:
BenchmarkDotNet=v<IP_ADDRESS>
OS=Microsoft Windows NT 6.2.9200.0
Processor=Intel(R) Core(TM) i7-3820 CPU 3.60GHz, ProcessorCount=8
Frequency=3515683 ticks, Resolution=284.4398 ns, Timer=ACPI
CLR=MS.NET 4.0.30319.42000, Arch=32-bit RELEASE
GC=Concurrent Workstation
JitModules=clrjit-v4.6.1532.0

Type=EditDistanceComparison  Mode=Throughput  GarbageCollection=Concurrent Workstation

       Method | ArrayLength |        Median |     StdDev |

----------------- |------------ |-------------- |----------- |
CalcEditDistance |         100 |   106.8777 us |  3.9923 us |
Levenshtein |         100 |    97.4189 us |  1.6145 us |
CalcEditDistance |         500 |   551.6745 us | 20.4686 us |
Levenshtein |         500 |   497.0457 us | 11.2616 us |
CalcEditDistance |        1000 | 1,094.9636 us | 21.9253 us |
Levenshtein |        1000 |   986.3376 us | 17.1519 us |
CalcEditDistance |        2000 | 2,195.0671 us | 73.5009 us |
Levenshtein |        2000 | 1,988.9683 us | 86.5691 us |

@rickasaurus pointed out on Twitter that we shouldn't use damerau levensthein.
I personally think we don't need the damerau part here (which makes it faster)
perf is not really big issue here since strings are small (this stuff usually used to compare DNA) and we only call it in error case. That said if we can improve it, then of course we should.

This looks good to me.


improve website menus levels

from @jennyxxdance:

I wanted to bring this up because I noticed there seems to have three different rows of tabs and I’m wondering how we could bring the UI a little better

there are different alternatives already in some PRs:
https://github.com/cmu-delphi/www-covidcast/pull/506

https://github.com/cmu-delphi/www-covidcast/pull/445

closing in favor of the new website design


ynamics-365-Workflow-Tools ( Force Calculate Rollup Field)

Rollup field should auto refresh when an associated record which contributes to the rollup is created/modified. The auto refresh does not occur I get an error.
I want a custom rollup field on the Quote form to refresh as soon as a Quote Line is created/modified.
Created a workflow with the entity as Quote Line. The Quote Line entity is where the data is added, and the rollup field is on the Quote record. I tried to implement the steps as described, but I keep getting an error that “The specified field does not exist in Microsoft Dynamics 365.” These are the properties I set…I believe they align with what is suggested. And I have the trigger on the workflow for Quote Line create and field changes which impact the total unit cost value which contribute to the Total Unit Cost value on the Quote. Any suggestions would be appreciated.
CRM Version - Version 1710 (<IP_ADDRESS>4) online - WorkflowTools version <IP_ADDRESS>

Hi skmancuso,
you are not using the parameters correctly. On the first one (FieldName) you should set a string with the schame name of the field, like "new_totalamount", and in this case you are passing a number from a field value, this is not correct.
please check the documentation: https://github.com/demianrasko/Dynamics-365-Workflow-Tools/blob/master/docs/Force Calculate Rollup Field.md
best regards!


Pie chart in editor

Summary
Documentation of tui.chart says about the uses with javascript, but i did't found any documentation to render different chart in the editor.
How can i render pie chart in the editor?
Using JS
import Chart from '@toast-ui/chart';

const chart = Chart.pieChart({el, data, options});

Here, Chart.pieChart defines pie chart,how can we do this in editor.

@ats1999
We cannot support all chart type with editor's csv format. I need to check it with the toastui chart.
I will check it!

@js87zz  most of the tui.chart have  the same data format, we can support all types of chart by just taking parameter of in yaml format from markdown.
---
chart-type:line
 series-names : rahul, kumar,..
.....
...
---


"Connection closed" error running unit test

My abc_page_test.dart test file was missing an import line, which caused an unresolved reference to a class used within the file. When I ran flutter test, it gave me this error:
jimbe:/media/jimbe/myproject$ flutter test
00:00 +0 -1: loading /media/jimbe/myproject/test/abc_page_test.dart
  Failed to load "/media/jimbe/myproject/test/abc_page_test.dart": Connection closed before test suite loaded.
00:01 +5 -1: Some tests failed.

Ideally, the Dart error for the unresolved class would be displayed.
Flutter Version
Flutter from https://github.com/flutter/flutter.git (on master)
Framework: 229253f43e222de4dd91813779a1a9d4ff22e9f8 (2 days ago)
Engine:    787e69fc453787089140b3b031ada932d7dad38e

/me can repro the issue.  Investigating.

I'm not sure what's going on.  We eventually call a function that seems to throw an uncatchable error and then the connection to the runner is closed.  I'm not sure what's causing the connection to be closed.

Good new, we don't get the connection error anymore.  Bad news: we hang forever.  :)

It seems like we have a bunch of related issues with our package:test integration which could all be duped together or closed.  #2182 is another potential.

This appears to be better than it was in the past but still not perfect.  I get a sensible error:
Shell: [ERROR:../../lib/tonic/logging/dart_error.cc(16)] '///Users/abarth/git/flutter/flutter/packages/flutter/test/widget/dismissable_test.dart': malformed type: line 107 pos 41: cannot resolve class 'StatelessWidget' from 'Test1215DismissableWidget'
Shell: class Test1215DismissableWidget extends StatelessWidget {
Shell:                                         ^

But the test command hangs rather than exits.

Probably we need the engine to exit if there's an error at start in non-interactive mode.

Fixed by https://github.com/flutter/flutter/pull/7269

Got same problem...
[✓] Flutter (Channel stable, v1.17.1, on Mac OS X 10.15.4 19E287, locale zh-Hans-CN)
    • Flutter version 1.17.1 at /Users/xxzz/flutter
    • Framework revision f7a6a7906b (7 days ago), 2020-05-12 18:39:00 -0700
    • Engine revision 6bc433c6b6
    • Dart version 2.8.2

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/xiangzhipan/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = /Users/xiangzhipan/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[!] IntelliJ IDEA Ultimate Edition (version 2020.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[!] IntelliJ IDEA Community Edition (version 2020.1.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • For information about installing plugins, see
      https://flutter.dev/intellij-setup/#installing-the-plugins

[✓] VS Code (version 1.45.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.10.2

[!] Proxy Configuration
    • HTTP_PROXY is set
    ! NO_PROXY is not set

after switching channel  from stable to dev and to stable again
It works。
between the switching, flutter notice me to add remote oring: git  remote add origin http://xxxx.
but can only work after run  git branch -set-up-stream... 。

It's a proxy problem.
From #30892 comment, if you have set proxy, you need to set no_proxy for <IP_ADDRESS>.


Usability Testing | Patterns Documentation

Provide an evidence-based set of recommendations re: understanding of the users and the documentation design forward.
Identify elements of documentation design needed to facilitate efficient and error free work for design system users.
### Tasks
- [ ] Develop research brief
- [ ] Coordinate with Design re: prototypes to use in testing

### Deliverables
- [ ] Research brief
- [ ] User interviews protocol
- [ ] Recommendation report

pattern docs on hold

Oct-6 - picking workstream up; planning session today

Oct-11: Held planning session with @mikearildbrown @shey-v; working session next week to confirm consistencies/inconsistencies with current docs + identify design attributes to test

Oct-30: awaiting wireframe from design for testing.

3 Nov - Meeting next Monday, test with MDX instead of Figma

Meeting had earlier this week. Button Bar pattern to be used an an example.

Round of edits done on Button Bar pattern page. Usability testing date to be arranged soon.

20 Nov - working on test script

22 Nov - discussed with Renae, testing script

24 Nov - testing scripts, same above

27 Nov - waiting for feedback from Renae

8 Dec - Links being review, to be launched on next week

18 Dec - Meeting tomorrow.


Add averageDistanceThreshold Option for Stroke Matching Leniency

This pull request introduces an averageDistanceThreshold option to the strokeMatches function, allowing users to configure the leniency of stroke matching based on distance.
This change provides more flexibility for users who want to adjust the leniency of stroke matching, especially in scenarios where the direction of the stroke is more important than its exact position.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (319ea83) 96.40% compared to head (b9799b7) 96.41%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #307   +/-   ##
=======================================
  Coverage   96.40%   96.41%
=======================================
  Files          32       32
  Lines        1141     1144    +3
  Branches      209      212    +3
=======================================
+ Hits         1100     1103    +3
  Misses         37       37
  Partials        4        4

Files Changed
Coverage Δ

src/defaultOptions.ts
100.00% <ø> (ø)

src/Quiz.ts
96.00% <100.00%> (ø)

src/strokeMatches.ts
100.00% <100.00%> (ø)

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

Looks good!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Breaking Change] Remove auto_bind feature and make accessible CLI param from task

CLI parameter auto binding is useful, but in complex workflow, it's hard to avoid wrong binding. Because it is bind by name, so if user use very common parameter name like day, it might be wrong binding.
So I decided to remove auto_bind feature and instead of that, introduce Tumugi::Application.params to access CLI parameters hash from task class.
Before
task :task1 do
  param :param1, auto_bind: true
end

After
task :task1 do
  param :param1, default: Tumugi.params['param1']
end

I think this idea is not good idea. So I close this now.


Public domain media not using the Creative Commons Public Domain Mark

Discussed in https://github.com/WordPress/openverse/discussions/89

Originally posted by zackkrida October  5, 2021
Currently, Openverse does not include public domain works unless they use the Public Domain Mark PDM tool from Creative Commons[^1]. This is because without PDM, a work may be:

in the 'public domain'
have 'no known copyright restrictions'

in one jurisdiction, but could in others. Here are CC's recommendations for when not to use PDM in their entirety[^2]:

The Public Domain Mark is recommended for works that are free of known copyright around the world. These will typically be very old works.  It is not recommended for use with works that are in the public domain in some jurisdictions if they also known to be restricted by copyright in others.
A work may have limited or “hybrid” public domain status for several reasons.  Some jurisdictions have unusually long copyright terms, which may mean that a work free from copyright restrictions most everywhere in the world could still be protected by the copyright laws of that particular country.  Sometimes a work is no longer restricted by copyright in a jurisdiction because the author or owner failed to comply with local formalities such as renewal, where those formalities apply.  It could also be the case for works that are deemed not protected by copyright by operation of law in a particular jurisdiction, but that are afforded protection under the copyright laws of other jurisdictions.
CC does not recommend the Public Domain Mark for works with limited, hybrid public domain status at this time.

We need to decide if we want to continue this practice or support these works.
[^1]: Public Domain Mark 1.0
[^2]: PDM Guidelines

Consensus seems to be^1:

display a message saying something like "this work has not been marked as PDM nor CC0 but it belongs to the public domain in some jurisdictions" and link to a page that details the legal implications.
From the value proposition perspective, we do want to boost the use of PDM content. The best experience for its correct use is the work we that need to do.

How can we codify this and close the issue? Is there technical work that needs to be done to resolve this? @zackkrida maybe you have an idea as the original discussion author?

I had updated the package only for the sake of completeness, and I have not checked if we actually have works with any of the extra licenses added in the update.

@sarayourfriend my general recommendation would be that we close this and spin it into a (potential) project for including non-Creative Commons licensed works into Openverse.
That would probably involve tasks like establishing criteria for what sufficiently "open" licenses are which meet the project ethics and objectives, a task which itself would require us to more explicitly define those terms.
It's a large undertaking and one we would need to consider carefully, weighing it against efforts to continue to identify and include all of the, likely hundreds of millions, of CC-licensed works that are not yet part of Openverse.

Sounds good! I'd love to see that project through, one day :slightly_smiling_face:. Closing this as won't do, for now.


Support without file extensions in nacos-config

Hey, I found a little problem. if I configure a data-id without file extensions in extension-configs , but config content type is yaml. then there is a proble, configuration is invalid. because the configuration is parsed by properties. so I want to add fileExtension field in NacosConfigProperties.Config.
我发现一个小问题, 如果在extension-configs里的data-id没有带文件后缀,并且配置内容格式是yaml或者其他类型,那么这个配置就会无效,因为会按照properties的格式进行解析. 所以我想添加一个fileExtension属性到NacosConfigProperties.Config里,用于支持这种场景.
about issues: https://github.com/alibaba/nacos/issues/8289
相关问题: https://github.com/alibaba/nacos/issues/8289

Welcome to contribute this feature.

Ok, I will finish it.


Could you please simulat this bug in https://github.com/planette/playground/blob/master/contributte-datagrid/README.md and send me your repo? Thanks!
Or maybe you can send a PR with fix?

It looks like, that this is fixed in v6.x branch, I have 6.0.1 in my project, where it is not fixed yet...

Is it fixed also in master? master is current development branch.

No it is not, i found pull request to v6.x
https://github.com/contributte/datagrid/pull/778

I have the same issue. If I set $grid->setRememberState(false);
the pressing reset filter button gives
TypeError
Argument 1 passed to iterator_to_array() must implement interface Traversable, array given

I have the same issue in v6.1.1 Argument 1 passed to iterator_to_array() must implement interface Traversable, array given

@paveljanda I can confirm the iterator_to_array() problem when remember state is set to false. Also for the master branch. However I think it is a different issue than the reported one.
The problem is that the default value in Datagrid::getSessionData() is an empty array when $key is null and remember state is set to false. And arrays cannot be passed to iterator_to_array().
So the question is - should the code be rewritten the foreach to $key => $value one like in the pull request above or replace the empty array with sth like  \EmptyIterator() in the Datagrid::getSessionData() method or something else?
In both solutions mentioned above remains a potential problem when a non iterable will be passed as a default value. Maybe $defaultValue should be Traversable too and the defauld value should not be null? But this is an another problem, I have not checked any consequences so I mention it only for reference at the moment as it does not affect the possibility of mentioned changes.


requestId always returns value "test-invoke-request"

Framework version: 0.9.1
Implementations: Spring

Scenario
Pulling the requestId value from the request payload at: ((AwsProxyHttpServletRequest) request).getAwsProxyRequest().getRequestContext().getRequestId().
Expected behavior
The value of this should be the UUID that is generated from API gateway as described here under "Input Format of a Lambda Function for Proxy Integration" -> https://docs.aws.amazon.com/apigateway/latest/developerguide/set-up-lambda-proxy-integrations.html#api-gateway-simple-proxy-for-lambda-input-format
Actual behavior
Instead, the requestId in the requestContext of the response is returning a string constant of "test-invoke-request".
Steps to reproduce
Make a call to your lambda function through API gateway and read the value of requestId in the proxyRequest object.

hey @thallium205, that request id is set by the AwsProxyRequestBuilder used in the unit tests for the framework: https://github.com/awslabs/aws-serverless-java-container/blob/master/aws-serverless-java-container-core/src/main/java/com/amazonaws/serverless/proxy/internal/testutils/AwsProxyRequestBuilder.java#L69
Are you saying we should set a valid UUID for the unit tests?

I think I know what's going on. API Gateway also automatically sends the test-invoke-request value for requestId when you use the test interface from the console - you can see it in the logs generated on the right on the Endpoint request body after transformations: line. Are you testing using the console or calling an API that is actually deployed?
"stage":"test-invoke-stage",
"requestId":"test-invoke-request"

Argh!  You're absolutely correct: when using the API Gateway's "Method Test" feature, it will include that constant as the requestId as revealed in the generated logs.  However, when hitting the endpoint using the invocation URL (through curl, for example), it generates the expected UUID requestId.
Sorry about this report... it is clearly not an issue with this library.  Thanks.


Azure.Data.Tables 12.0.0-beta.8 - NullReferenceException in tableClient.DeleteEntity

Describe the bug
NullReferenceException in tableClient.DeleteEntity call
Expected behavior
Row added and deleted.
Actual behavior (include Exception or Stack Trace)
Row is added but not deleted because of exception.
To Reproduce
            var tableClient = new TableClient(<cs>, <table>);
            var entity = new TableEntity("a", "b")
            {
                { "Product", "Marker Set" }
            };
            tableClient.AddEntity(entity);
            tableClient.DeleteEntity("a", "b");

Environment:

Azure.Data.Tables 12.0.0-beta.8
Win 10 .NET 3.1
Visual Studio 16.9.6

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

I'm also seeing System.NullReferenceException: Object reference not set to an instance of an object.    at Azure.Data.Tables.TableClient.DeleteEntity(String partitionKey, String rowKey, ETag ifMatch, CancellationToken cancellationToken)        at MyTimerTriggeredAzureFunction(TimerInfo timer, ILogger log) when trying to delete

Thanks @dan5082 Could you provide a simple code snippet that reproduces the problem? This one is a bit odd because it works in our current tests.

Windows 10 VS Code using:
Azure Functions Core Tools
Core Tools Version:       3.0.3160 Commit hash: 00aa7f43cc5c5f15241b5e6e5363256f19ceb990
Function Runtime Version: 3.0.14916.0
"Azure.Core" Version="1.14.0"
[FunctionName("ReproduceDeleteIssue")]
public static async Task ReproduceDeleteIssue(
[TimerTrigger("0 */12 * * *", RunOnStartup = true)] TimerInfo timer,
ILogger log
)
{
TableClient client = new TableClient(storageTableConnectionString, "deleteThisTable");
client.CreateIfNotExists();
var entity = new TableEntity("TestPartitionKey", "testRowKey")
{
{ "Product", "Marker Set" }
};
client.AddEntity(entity);
entity = client.GetEntity("TestPartitionKey", "testRowKey");
Console.WriteLine($"created entity {entity.RowKey} {entity.PartitionKey}");
await client.DeleteEntityAsync(entity.PartitionKey, entity.RowKey);
Console.WriteLine($"Entity Deleted from table");
client.Delete();
       return;
    }

using 12.0.0-beta.6

using newest Azure.Data.Tables 12.0.0-beta.8:

Thanks for providing this info. Unfortunately I still can't reproduce with similar code.
Could you please try with the latest dev build which has the very latest version of the implementation?
https://dev.azure.com/azure-sdk/public/_packaging?_a=package&feed=azure-sdk-for-net&package=Azure.Data.Tables&protocolType=NuGet&version=12.0.0-alpha.20210603.1&view=overview

unfortunately the latest build has the same behavior for me. stack trace doesn't have any useful data (just at Azure.Data.Tables.TableClient.DeleteEntity(String partitionKey, String rowKey, ETag ifMatch, CancellationToken cancellationToken) and no inner exceptions).
maybe I have to setup some symbols?

Can you reproduce it outside of an Azure Function?

I get the same NullReferenceException in a server-side blazor app. Reverting to 12.0.0-beta.7 fixes it with no code changes.

I'm having the same issue when working with the 12.0.0 version. The 12.0.0-beta.7 works fine.
Delete of both Entity as Table give the same exception.

I'm having the same issue when working with the 12.0.0 version. The 12.0.0-beta.7 works fine.
Delete of both Entity as Table give the same exception.

@kristapratico Is your repro also in an Azure function? If so, can you reproduce outside of the function? If not, can you provide a snippet of sample code that demonstrates the exception?

I get the same NullReferenceException in a server-side blazor app. Reverting to 12.0.0-beta.7 fixes it with no code changes.

Hi @jkalweit Could you provide a stack trace of the exception?

Disregard the code requests, I have a repro now. Thanks!

I have a fix, but here is a workaround in the meantime. The issue only exists when the TableClient is created with the connectionString constructor. Here is how you can take a connection string and turn it into a TableSharedKeyCredential so that the other ctor can be used until a fix is available:
var pairs = storageTableConnectionString
    .Split(';')
    .Select<string, KeyValuePair<string,string>>(p =>
    {
        var pair = p.Split('=', 2);
        return KeyValuePair.Create(pair[0], pair[1]);
    })
    .ToDictionary(p => p.Key, p => p.Value);

string accountName = pairs["AccountName"];
var cred = new TableSharedKeyCredential(accountName, pairs["AccountKey"]);
var uri = new Uri($"https://{accountName}.table.core.windows.net");

TableClient client = new TableClient(uri, "deleteThisTable", cred);

@christothes This solves the issue for me.
To awnser your question, for me it wasn't in an Azure Function context. I was using it to write my workflow data to tablestorage.