failed to pull docker image

Describe the bug
When I run supabase start I get this error:
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.139.2-rc.7
not found: manifest unknown: Requested image not found

To Reproduce
Install the latest version of supabase:
"supabase": "^1.142.2",

Expected behavior
No errors
System information
Rerun the failing command with --create-ticket flag (preferred).

Ticket ID: cf89590c829d4353bb8226495c762c88
OS: Windows 11
Version of CLI: 1.142.2
Versions of services:

       SERVICE IMAGE      │        LOCAL         │    LINKED
 ─────────────────────────┼──────────────────────┼───────────────
   supabase/postgres      │ <IP_ADDRESS>           │ <IP_ADDRESS>
   supabase/gotrue        │ 2.139.2-rc.7         │ 2.139.2-rc.7
   postgrest/postgrest    │ v11.2.2              │ v11.2.2
   supabase/realtime      │ v2.25.50             │ -
   supabase/storage-api   │ v0.46.5              │ v0.46.5
   supabase/edge-runtime  │ v1.33.5              │ -
   supabase/studio        │ 20240101-8e4a094     │ -
   supabase/postgres-meta │ v0.75.0              │ -
   supabase/logflare      │ 1.4.0                │ -
   bitnami/pgbouncer      │ 1.20.1-debian-11-r39 │ -
   darthsim/imgproxy      │ v3.8.0               │ -

J

So I temporarily fixed it by removing the version in supabase/.temp/gotrue-version, however, it still wants to link to a non-existent version:
You are running outdated service versions locally:
supabase/gotrue:v2.132.3 => 2.139.2-rc.7
Run supabase link to update them.

Should the cloud version be using a version that is not downloadable?
J

It looks like we don't have version 2.139.2-rc.7 published on docker hub. I will ping our auth team to take a look. Sorry for the inconvenience.

I have somewgat the same issue with gotrue:2.142.0
docker pull public.ecr.aws/supabase/gotrue:2.142.0 works fine
but when i run supabase start i have:
failed to pull docker image: invalid reference format
Retrying after 8s: public.ecr.aws/supabase/gotrue:2.142.0

failed to pull docker image: invalid reference format

We're in the same boat over here
https://github.com/supabase/supabase/issues/21300

So I temporarily fixed it by removing the version in supabase/.temp/gotrue-version, however, it still wants to link to a non-existent version:
You are running outdated service versions locally:
supabase/gotrue:v2.132.3 => 2.139.2-rc.7
Run supabase link to update them.

Should the cloud version be using a version that is not downloadable? This breaks the link.
J

This worked, all I had to do was add a v in the front

@Mikodin  Changing to v2.142.0 causes a new error for me; please let me know if you experienced something similar.
➜  supabase db pull
Connecting to remote database...
Setting up initial schema....
failed to pull docker image: invalid reference format
Retrying after 4s: public.ecr.aws/supabase/gotrue:v2.142.0

Can you try deleting any new line characters in the version file? I will also update the code to handle this better

@sweatybridge Sorry - I accidentally deleted my previous content; restoring it below:
I am getting a new error after hotfixng supabase/.temp/gotrue-version to include the "v" character:
´´´
➜  supabase db pull
Connecting to remote database...
Setting up initial schema....
failed to pull docker image: invalid reference format
Retrying after 4s: public.ecr.aws/supabase/gotrue:v2.142.0

@sweatybridge It seems there are no newline characters in the file. I will check if vim left any kind of control characters.

I just ran into the same issue, pulling the image without the v tag prefix and tagging the image with the expected image name worked for me.
docker pull public.ecr.aws/supabase/gotrue:v2.142.0
docker tag public.ecr.aws/supabase/gotrue:v2.142.0 public.ecr.aws/supabase/gotrue:2.142.0

@sweatybridge - I'm still getting the error:
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.139.2-rc.7
not found: manifest unknown: Requested image not found

When running npx supabase start. Your team has not added it yet.
J

Yes, I'm using 1.142.2.

No because then it will ask me to relink. That is not the version installed on the cloud.

It is for my project. I reran supabase link (which did nothing since my versions are all synced) and supabase start works fine for me now. I created the project on supabase a couple of hours ago so that might be why I don't have the gotrue version issue that you're mentioning.

Yes, I can upgrade my project, but that doesn't fix the underlying problem.

@sweatybridge - There is definitely a bug here.  I upgraded my supabase project by going to settings, infrastructure. I am now using the latest version.
The problem is a bug with supabase link.  It does not seem to add the v to v2.142.0.
failed to pull docker image: Error response from daemon: manifest for public.ecr.aws/supabase/gotrue:2.142.0
not found: manifest unknown: Requested image not found

I can add the v to it so that it is v2.142.0, but then I get this error when running supabase start:
You are running outdated service versions locally:
supabase/gotrue:v2.142.0 => 2.142.0

Obviously they are the same version, but supabase start does not realize this because the code does not take the v into account. This is a problem and a bug with supabase link AND supabase start.
J

Turns out the v prefix was accidentally dropped from gotrue's /health endpoint response but the docker tag was still v2.142.0. There's an upstream PR to fix it. Once it's rolled out, running link and start should work again.

I could not get any of the older versions or fixed mentioned above to work unfortunately, as this issue just started happening for me today. Deleting the supabase/.temp/gotrue-version file worked for me


WhatsApp phone numbers format

Describe the bug
In order to display the phone number of the author of the message on WhatsApp it seems that {{USERID}} should be used, but the result is<EMAIL_ADDRESS>is it possible to display the phone number without @s.whatsapp.net?
Maybe something can be done with {TENGO)?
Environment (please complete the following information):

OS: linux
Matterbridge version: 1.25.1
If self compiled: go install -tags nomsteams,nogitter,nokeybase,norocketchat,noslack,novk,nozulip,whatsappmulti github.com/42wim/matterbridge@master

Additional context
[whatsapp.test]
	Number="+1415454545454"
	RemoteNickFormat=""
	SessionFile="session-test.gob"
	QrOnWhiteTerminal=false

[telegram.test]
	Token="64597464:JHJKSDHFKJASDNFCJSDPOKZPLWSDPFCSPCFL"
	RemoteNickFormat="{NICK}\n(+{USERID})\n"
	MessageFormat=""
	DisableWebPagePreview=false

[[gateway]]
	name="test"
	enable=true

	[[gateway.in]]
	account="whatsapp.test"
<EMAIL_ADDRESS>
	[[gateway.out]]
	account="telegram.test"
	channel="-568973628952378"

A solution I made for anyone looking:
ADD
[tengo]
	InMessage="userid.tengo"

userid.tengo:
// Remove<EMAIL_ADDRESS>from whatsapp users & change {NICK} to "NUMBER USERNAME"
text := import("text")
    msgUsername=text.re_replace("@s.whatsapp.net","+" + msgUserID," " + msgUsername)

I used your code and here the phone number was appearing in duplicate, I solved it with my code:
text := import("text")

parts := text.split(msgUserID, "@")
msgUsername = "+" + parts[0]


excessive manpath

Are people aware that spack-stack creates really long manpath when it's loaded as a module. Is the long manpath something baked into spack-stack, or maybe that's due to an error having spakstack manpath specified incorrectly by the person writing the module file.
With spack-stack loaded, any time I need to use manual, it ends up as:
man: manpath list too long
I am not sure if I can copy/paste the manpath with all the directories here since it's on a navy hpc machine. I hope I have explained the issue clearly.

Sorry I hit email return too soon, that's the version of the machine and it
seems like it's not fixed at least on this particular linux distro.
On Wed, Jun 21, 2023 at 12:39 PM Fei Liu @.***> wrote:

SUSE Linux Enterprise Server 15 SP2
---------- Forwarded message ---------
From: Dom Heinzeller @.>
Date: Wed, Jun 21, 2023 at 12:18 PM
Subject: Re: [JCSDA/spack-stack] excessive manpath (Issue #628)
To: JCSDA/spack-stack @.>
Cc: feiliuesmf @.>, Author @.>
Every package (software) in spack adds to the manpath, so unless we don't
add manpath entries at all (which we do not want I believe), then this is
not something we can change. I found this, though:
https://stackoverflow.com/questions/54037380/man-manpath-environment-variable-list-too-long-manpath-list-too-long

according to that discussion, this was fixed in more recent OS versions.

—
Reply to this email directly, view it on GitHub
https://github.com/JCSDA/spack-stack/issues/628#issuecomment-1601144167,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABAX7CXFZJMW4UM3PNEPNS3XMMNGLANCNFSM6AAAAAAZJI5QJQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

I am closing this, since we don't really have a solution for this problem and it doesn't happen on any of the machines that we support.


Pixi dev env

Adding the following libraries in the dev environment:

ipython
ipykernel
jupyterlab

There are pretty handy stuff for interactive development. Ideally, pixi could one deal with a user-defined dev environment without relying on the project config.

There are pretty handy stuff for interactive development. Ideally, pixi could one deal with a user-defined dev environment without relying on the project config.

I agree; IIUC that's not the case at the moment right?

I agree; IIUC that's not the case at the moment right?

Yep this is not.


Problem with using StateMachine as Bevy Component

Hey all, I noticed the Bevy feature flag when installing statig which allows StateMachine to implement Component however I can't seem to get this to work correctly. I get the error
the trait bound `statig::prelude::StateMachine<monster::Behaviour>: bevy::prelude::Component` is not satisfied
the following other types implement trait `bevy::prelude::Component`:
  animation_link::AnimationLink
...

Code snippets
#[derive(Bundle)]
pub struct MonsterBundle {
    pub scene: SceneBundle,
    pub speed: Speed,
    pub stats: Stats,
    pub animations: NamedAnimations,
    pub behaviour: StateMachine<Behaviour>,
}

#[derive(Default)]
pub struct Behaviour;

pub enum Event {
    TimerElapsed,
    Start,
    Stop,
    Dance,
}

#[state_machine(initial = "State::idle()")]
impl Behaviour {
    #[state(entry_action = "enter_idle")]
    fn idle(event: &Event) -> Response<State> {
...

Wrapping it in a newtype seems to work correctly
#[derive(Component)]
pub struct BehaviourState(pub StateMachine<Behaviour>);

It seems this is just a problem with a mismatch in the bevy_ecs version.

Solved with #18


doing stuff that's already done

is there a reason why you aren't checking whether the user is already in sudoers?
Similary, you are pre-pending /usr/bin to the $PATH - that will get you duplicate entries if it's already there.
Neither of these is a big deal - but it seems like such a carefully written script, so I wondered...

Both of those are "good to haves". The original idea was that the script is run right after an initial install of the OS, but it can obviously be used when adding Docker to an existing installed OS as well.
Would you want to propose some changes and do a PR? Happy to accept them :)
Thanks!

fixed in https://github.com/sdr-enthusiasts/docker-install/commit/48e41b9f2a5f16d907f3811e71c5b1caee7bfc05


Swap aliases before index delete to improve robustness

Addresses issue https://github.com/nhsuk/elasticsearch-updater/issues/14

Fixed in pharmacies PR https://github.com/nhsuk/elasticsearch-updater/pull/11


Android - Calculate total balance of XOR for 2 free KYC attempts

Now we don't summarise Pooled XOR.

Considering the revised requirements (https://github.com/sora-xor/sora-card/issues/60#issuecomment-1686133374), this issue should be reopened @arvifox


[wallet-ext] show estimated gas fees for a sponsored transaction during the user approval stage

Description
This PR updates the transaction approval page to show gas information for sponsored transactions. I can't actually test this yet because the wallet is broken on the latest devnet, but I'll update this with images and whatnot when it's fixed (obviously, I won't merge it until then either 😄).
Figma link: https://www.figma.com/file/xu2VnyPAuruNi74UQzGigW/02-Wallet?node-id=475%3A36083&t=g9ZcekTket0gb2uJ-0
Jira: https://mysten.atlassian.net/browse/APPS-551
Test Plan

Manual testing

Type of Change (Check all that apply)

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

Release notes
N/A

Closing in favor of Jordan's diff


tell which did already exists

Signed-off-by: Axel Nennker<EMAIL_ADDRESS>The information that the did already exists is already in the name of the error DidError::AlreadyExistsError so adding the string "Did already exists" does not provide additional info.
Replacing it with the did.to_string() to provide that info to the caller.

@AxelNennker Could you solve conflict and remove WIP tag after it?

Seems merging caused absence of any changes.

Strange. Will look into why there are not file changed later. Maybe the change sneeked into some other PR already?

@AxelNennker seems like during some changes in master Did structure is changed. Not build failed with message:
error[E0599]: no method named `to_string` found for type `domain::crypto::did::Did` in the current scope
   --> src/commands/did.rs:220:77
    |
220 |             return Err(IndyError::DidError(DidError::AlreadyExistsError(did.to_string())));
    |                                                                             ^^^^^^^^^
    |
   ::: src/domain/crypto/did.rs:37:1
    |
37  | pub struct Did {
    | -------------- method `to_string` not found for this
    |
    = note: the method `to_string` exists but the following trait bounds were not satisfied:
            `domain::crypto::did::Did : std::string::ToString`
    = help: items from traits can only be used if the trait is implemented and in scope
    = note: the following trait defines an item `to_string`, perhaps you need to implement it:
            candidate #1: `std::string::ToString`

Could you fix it, please?

@jovfer fixed it. Sorry, no idea how this happened.


Clicking eye icon to toggle visibility does not call _set()

Godot version:
3.2.2 stable
OS/device including version:
macOS Mojave, Macbook Pro 2015
Issue description:
I wish to run some code when the visibility is toggled by clicking the eye icon in the scene panel. So I tried the following code, which is the only way I'm aware of to emulate setters for builtin variables:
extends Node2D
tool

func _set(property, value):
	print("set something")
	match property:
		"visible":
			print("you set visibility")

The string is printed if the "visible" checkbox is toggled in the inspector panel, but not when clicking the eye icon as expected.
Steps to reproduce:
Put the above script on a Node2D and try toggling its visibility by clicking the eye.
Minimal reproduction project:
Don't think this is needed.

Out of curiosity, is the setter called when you call hide() or show()` on the node externally?

Out of curiosity, is the setter called when you call hide() or show() on the node externally? Maybe it's due to the editor using hide() or show() instead of setting the visible property.

Nope, the setter is not called. And it appears the editor is not calling those either, if I put a print inside hide() it doesn't happen unless I call it myself.

NOTIFICATION_VISIBILITY_CHANGED works in my case, yeah. But I still think this inconsistency should be addressed.


save lowest detected epoch during training, issue #476

With the new overtraining system, this feature was improved. Anyway, thanks for your contribution!


Let's have OpenAPI v3.0 and stop talking about Swagger entirely

OpenAPI is the new name for the API Specification which was formerly called Swagger. The website talks a lot about having "Swagger" and "OpenAPI", but really you just have "OpenAPI v1.2 and OpenAPI v2.0."

The website should remove all references to "Swagger", unless saying "OpenAPI (formerly known as Swagger)" for educational purposes
OpenAPI v3.0 support should be added: /openapi/v3

This is super easy to do manually or programmatically with swagger2openapi.
This would bring kubernetes up-to-date, as v3.0 has been out for about a year. 😄

/remove-lifecycle stale


Allows for custom request/response logging

Reason for This PR
[Author TODO: add issue # or explain reasoning.]
Description of Changes
[Author TODO: add description of changes.]
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the MIT license.
PR Checklist
[Author TODO: Meet these criteria.]
[Reviewer TODO: Verify that these criteria are met. Request changes if not]

[ ] All commits in this PR are signed (git commit -s).
[ ] The reason for this PR is clearly provided (issue no. or explanation).
[ ] The description of changes is clear and encompassing.
[ ] Any required documentation changes (code and docs) are included in this PR.
[ ] Any user-facing changes are mentioned in CHANGELOG.md.
[ ] All added/changed functionality is tested.

Codecov Report

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

@@            Coverage Diff            @@
##             stable       #1   +/-   ##
=========================================
  Coverage          ?   67.62%
=========================================
  Files             ?       94
  Lines             ?     4858
  Branches          ?        0
=========================================
  Hits              ?     3285
  Misses            ?     1156
  Partials          ?      417

Continue to review full report at Codecov.

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


Unable to save frame as image

Q
A

Bug?
Yes

| FFmpeg Version | FFmpeg or AVConv and version
| OS             | Your OS and version
Symfony2.8
ExecutionFailureException: ffmpeg failed to execute command '/usr/bin/ffprobe' '-y' '-ss' '00:00:05.00' '-i' '/home/dmlabs-5/iasp/IASP_platform/web/uploads/media/default/0001/01/529d9972c548e552271728e915cbbf98c9514f13.mp4' '-vframes' '1' '-f' 'image2' '/home/dmlabs-5/iasp/IASP_platform/web/uploads/media/default/0001/01/529d9972c548e552271728e915cbbf98c9514f13.jpg'

Closed due to inactivity.


Are exceptions in injected grammar scopes applied?

I doubt exception is the right word for these, so here’s an example. Say you want to add some highlighting to a pre-existing grammar, in its foo.bar.grammar scope. My understanding is that one way to do this is with an injection like this:
injections:
  "foo.bar.grammar":
    patterns: [
      {
        name:  "my.addition"
        match: "some-regex"
      }
    ]

Now say, after doing this, you realize that you don’t want your extra highlighting in comments or strings. To keep your highlighting out of comments and strings, you could write:
injections:
  "foo.bar.grammar -(comment | string)":
    patterns: [
      {
        name:  "my.addition"
        match: "some-regex"
      }
    ]

I’m calling that -(comment | string) thing an exception, because the result is to put highlighting in everything except comments and strings.
Does Linguist apply exceptions when it performs syntax highlighting? Here is an example on Lightshow where it doesn’t look like it. In Atom, the same example, with the same grammar, shows comments and strings as I’d expect (without extra highlighting).

I had the same problem recently. When I had L:a - (b | c) as the selector for injection, GitHub recognized it differently from Atom. I have to note that Atom's implementation of scope selectors is somewhat broken at the moment and I've been working on fixing that, but despite that even with my fixes applied, that specific selector seems to function the way it used to with the currently used implementation. I have not tested this with TextMate yet, so even my implementation could be right now incorrect.
If you want a quick fix and do not really care whether it is actually the correct thing, then L:(a - (b | c)) or a - (b | c) should do the trick, but I would consider testing whether L:a - (b | c) works in TextMate or Sublime Text and then start drawing conclusions about which implementation is handling them incorrectly.

Using L:(a - (b | c)) works, thanks!


upgrade swagger-ui to 2.0.24

Finished review. Back to @stuartf for follow-up.
@stuartf : Are there any back-end changes associated to this PR?

This should work with the current backend and make us ready for upgrading the backend doc to swagger 2.0.

Looks good. Merged


Add tests

I should add tests to the JavaScript code. Investigate testing frameworks (Jest?) and add tests for full coverage. I should probably also add a new Action that runs tests for any commit (not just on main).

Closing this for a few reasons:

There is very little JavaScript in this project. All functions are exhausted by four UI buttons. Testing is no longer a requirement to me.
I want this project to remain vanilla HTML5, CSS3, and JavaScript only (no npm).
I don’t have a good understanding of how to accomplish testing without using a framework surrounded by npm.


Task 1

Who is doing task 1?

The task distribution is discussed in this issue https://github.com/ubsuny/23-Homework6G1/issues/14


What's the correct procedure to record a meeting and get the URL of the video file

Hi,
We are doing something like this:
$eyeson = new Eyeson($api_key);
        $options = array(
            'show_names' => 'show',
            'show_label' => 'false',
            'reaction_available' => false,
            'exit_url' => $exit_url,
            'logo' => $logo,
            'recording_available' => true,
            'broadcast_available' => false,
            'layout_available' => false,
        );
	$room = $eyeson->join($firstname, $id_of_room, $options);
        $recording = $eyeson->record($room);

	redirect($room->getUrl());
    }

So the user is redirected to the room url and the recording starts.
What is the best way to stop the recording and get the URL of the video file ? Is it via a webhook? Would you have an example ?
Thanks!!

Hi there, as the recording is not ready at the time the user stops it (postprocessing & uploading to our cloud storage) the best way to manage recordings is to use webhooks. Let me know if you have any further questions on this!


Huffman code and Bidmach

Hello,
For the DNN and large memory ML algo, wondering if you will intend to use Huffman code to reduce the memory footprint of the parameters (weights for DNN).
Also, wondering if you will use techniques like pruning and weight sharing by quantization
to reduce the memory usage ?
Thanks

Probably not. We'd have to keep uncompressing them with each operation, which would undercut the value of using the GPU.


Config Show Testing

Tests the Config Show command for the individual sections in configuration (e.g. Storage, Egress, Logging, etc), for both Full and Redacted using text comparison. Currently, the testing doesn't include any checks for Kestrel or CorsConfiguration since there's no documentation on how to configure them; however, adding them in the future should be a relatively straightforward exercise. To keep the tests and configuration from becoming overly large, the tests are not designed to check all possible edge cases or configuration possibilities, but in its current state this should provide a good baseline check that Config Show is behaving properly.
Closes #687

/backport to release/6.x


language/nnbd/subtyping/type_casts_strong_test can't run with sound null safety

language/nnbd/subtyping/type_casts_strong_test
The test needs to be updated/forked/deleted to not import opted out sources in versions expected to run in strong mode.

cc @leafpetersen


Exception serialization does not handler Empty exception message.

Oringally reported:https://github.com/Microsoft/ApplicationInsights-aspnetcore/issues/823
Application Insights Rejecting Exceptions with empty Message
Repro:
TelemetryClient tc = new TelemetryClient();
tc.Context.InstrumentationKey = "validikey";
tc.TrackException(new Exception(""));
tc.Flush();
Response from backend:
Field 'message' on type 'ExceptionDetails' is required but missing or empty. Expected: string, Actual: undefined
// The following gets mesage automatically populated, but passing "" or string.empty breaks it.
var ex = new Exception();
tc.TrackException(ex);
Fix would be to modify Exception sanitization to handle this properly.

This bug is still there.

This is still an issue, I've created a PR with a unit test: #2857 that will hopefully solve it.


Fix errors in build-binaries task

Signed-off-by: Ashmita Bohara<EMAIL_ADDRESS>
Which problem is this PR solving?
As described https://github.com/jaegertracing/jaeger/pull/2740#issuecomment-770567346
GOOS=linux GOARCH=amd64 make build-platform-binaries
make[1]: Entering directory '/home/runner/work/jaeger/jaeger'
fatal: No names found, cannot describe anything.

Short description of the changes
Each build job of jaeger component's binary adds BUILD_INFO (part of which is extracted from git tag i.e. GIT_CLOSEST_TAG) in Makefile. Hence we need to pull the git tags before building binaries.

codecov/patch targets are still running. Will merge once they become green.

Merged, given that this won't change the code coverage, which was the only check missing.


[1.4] MODCLUSTER-695 fix build error "user id is too big" - set tarLongFile…

…Mode to posix
https://issues.jboss.org/browse/MODCLUSTER-695

Something wrong with CI....


Change docker.pkg.github.io to ghcr.io

because apparently the old one is deprecated and ghcr.io is preferred
now

Pull Request Test Coverage Report for Build 324877061

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 77.462%

Totals

Change from base Build 324780075:
0.0%

Covered Lines:
873

Relevant Lines:
1127

💛  - Coveralls


Refactor giftwrap builders

Previously the two builders had operated as separate build procesess.
What this meant is that when one builder would change, the other would
also need to change in order to support build parity.
This change moves all of the build logic into the base Builder abstract
class. Each sub Builder then implements the necessary primitives to
support the build steps outlined by the base class.

I like the direction, but still seems like there is a lot of duplicate code between the two builder classes.
Also there seems to be some unrelated changes committed with this.


Fix support of formulae aliases in taps

Resolves: #16636

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?

** Yes in #16636 **

[ ] Have you written new tests for your changes? Here's an example.

[X] Have you successfully run brew tests with your changes locally?

… but I have the same failures in master and my PR (49 failures)

I'm also not sure why this test didn't catch this problem.
https://github.com/Homebrew/brew/blob/88b5e50208fe333c0992b79d9167db5c9e7257ec/Library/Homebrew/test/formulary_spec.rb#L239-L244

I'm also not sure why this test didn't catch this problem.
https://github.com/Homebrew/brew/blob/88b5e50208fe333c0992b79d9167db5c9e7257ec/Library/Homebrew/test/formulary_spec.rb#L239-L244

… I think because the spec just asks for formula-name and not for a tap/formula-name.

I'm also not sure why this test didn't catch this problem.
https://github.com/Homebrew/brew/blob/88b5e50208fe333c0992b79d9167db5c9e7257ec/Library/Homebrew/test/formulary_spec.rb#L239-L244

… I think because the spec just asks for formula-name and not for a tap/formula-name.

That's exactly it. I added a regression test that checks for that and it fails on the master branch and works on this one.

/u/l/Homebrew (issue-16636-fix-support-of-formulae-aliases-in-taps|✚2) $ brew info<EMAIL_ADDRESS>==><EMAIL_ADDRESS>stable 2.2.3, HEAD
Yaml PHP extension
https://github.com/php/pecl-file_formats-yaml
Not installed
From<EMAIL_ADDRESS>License: PHP-3.01
==> Dependencies
Build: autoconf ✔, pkg-config ✔<EMAIL_ADDRESS>✘
Required: libyaml ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
To finish installing yaml for PHP 8.3:
  * /usr/local/etc/php/8.3/conf.d/20-yaml.ini was created,"
    do not forget to remove it upon extension removal."
  * Validate installation by running php -m

/u/l/Homebrew (issue-16636-fix-support-of-formulae-aliases-in-taps|✔) $ brew info<EMAIL_ADDRESS>==><EMAIL_ADDRESS>stable 2.2.3, HEAD
Yaml PHP extension
https://github.com/php/pecl-file_formats-yaml
Not installed
From<EMAIL_ADDRESS>License: PHP-3.01
==> Dependencies
Build: autoconf ✔, pkg-config ✔<EMAIL_ADDRESS>✘
Required: libyaml ✔
==> Options
--HEAD
	Install HEAD version
==> Caveats
To finish installing yaml for PHP 8.3:
  * /usr/local/etc/php/8.3/conf.d/20-yaml.ini was created,"
    do not forget to remove it upon extension removal."
  * Validate installation by running php -m

It seems to work now.

Thanks for adding the test here, @apainintheneck!

Thanks for this @sjorek and for the review and merge @apainintheneck and @reitermarkus!


Fixing linux paths that used ~ to get home

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks!


Pdct 846/some old google forms still linked to from product

Description
Remove old shortform Google form links and replace with relevant JotForm links.
PDCT-846

PDCT-866 to address Peter's comment


[Enhancement] Unused field

Search before asking

[X] I had searched in the issues and found no similar issues.

Enhancement Request

located at:
org/apache/eventmesh/runtime/boot/EventMeshTCPServer.java 133
analysis and explanation:
Unused field: org.apache.eventmesh.runtime.boot.EventMeshTCPServer.tcpRegisterTask
Describe the solution you'd like
This field is never used,consider removing it from the class.
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

I would like to work on this issue. @Alonexc @xwm1992 Can you please assign this task to me?


global leak with requestAnimationFrame, cancelAnimationFrame

I've already opened an issue in Sinon about a leak being reported by mocha while using sinon fake timers.
https://github.com/sinonjs/sinon/issues/1617
To replicate the error add --check-leaks to the mocha testing command on the package.json
  "scripts": {
    "lint": "eslint .",
-    "test-node": "mocha -R dot",
+    "test-node": "mocha -R dot --check-leaks",
    "test-headless": "mochify",
    "test-cloud": "mochify --wd",
    "test": "npm run lint && npm run test-node && npm run test-headless",
    "bundle": "browserify -s lolex -o lolex.js src/lolex-src.js",
    "prepublish": "npm run bundle",
    "precommit": "run-p lint test-node"
  }

output
1) lolex tick "before each" hook:
     Error: global leaks detected: requestAnimationFrame, cancelAnimationFrame

I think this is probably the PR that introduced the bug, as this has only been failing for the last day or so and this is the only PR which mentions requestAnimationFrame.
https://github.com/sinonjs/lolex/pull/137/files

Great, thanks. Already reported as #142 a few minutes earlier, and a fix is in!

Released as 2.3.0


🎮 Game Request
Airform the planet with flying saucer
Collect capsules with rare earth minerals, lava and water. Build drones by dropping capsules on factories.
Raise the AIR level to 100%!
Point down the features
Game points
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @S-ishita !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @S-ishita ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇


to url and to toml

to url will take a table with strings in its cells and output a string formatted as a url. The behaviour is pretty much the same as in the old engine.
〉[[foo bar]; ["1" "2"]] | to url
foo=1&bar=2

If the cells inside are not strings an error will be given, i can change this behaviour to automatically convert the values to strings, i chose not to do it just so it would have the same output as the old engine.
〉[[foo bar]; [1 2]] | to url
Error: nu::shell::unsupported_input (https://docs.rs/nu-protocol/0.1.0/nu-protocol/enum.ShellError.html#variant.UnsupportedInput)

  × Unsupported input
   ╭─[entry #2:1:1]
 1 │ [[foo bar]; [1 2]] | to url
   ·                      ───┬──
   ·                         ╰── Expected table with string values
   ╰────

to toml is a little bit different given the fact that the we don't have Table and Row anymore, and now we have List and Record.
The top level can now be a "table" represented as a List of Records.
Ex:
〉[[foo bar]; [1 2]] | to toml
bar = 2
foo = 1

Or a record(Obs: the new record building syntax is so cool)
Ex:
〉{x: 3, y: 100} | to toml
x = 3
y = 100

And finally a string that can be parsed as a toml(I thought this was a little bit weird given that we have from toml but i decided to keep it to keep the compatiblity)
〉'foo = 1' | to toml
foo = 1

It will output an error if a string that cant be parsed is given.
〉'hello world' | to toml
Error: nu::shell::unsupported_input (https://docs.rs/nu-protocol/0.1.0/nu-protocol/enum.ShellError.html#variant.UnsupportedInput)

  × Unsupported input
   ╭─[entry #7:1:1]
 1 │ 'hello world' | to toml
   · ──────┬──────
   ·       ╰── "hello world" unable to de-serialize string to TOML
   ╰────

Looks good


Update SectionType for RouteDirections V1

Data Plane API - Pull Request
Our dependency service provider has updated their schema and no longer offers support, so we are also making a breaking change.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[] a public preview
[x ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting
Open API Hub

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Schedule a data plane REST API spec review

Checks stuck in `queued` state?
If the PR CI checks appear to be stuck in `queued` state, please add a comment with contents `/azp run`.
This should result in a new comment denoting a `PR validation pipeline` has started and the checks should be updated after few minutes.

@koyasu221b Left a couple of minor feedback. Please wait for my confirmation before pushing this for review.


[RU] Added composition lesson

Thanks, @brain-geek !
I've just read your translation and found some small mistakes.

Thanks for the review, @nscyclone !
I've addressed everything except for one paragraph, which has some issues.

@brain-geek could you rebase when you have a chance?  This isn't currently cannot be merged.

@doomspork Thanks for noting! I've rebased and merging it now.

@toptal-bot run features

@nscyclone Can you look through again? I think I've fixed the issue

@brain-geek , it looks fine, but I still think it should be со списком but not с списком.
A sort of proof can be found here: http://rosental-book.ru/styli_xlv.html#sect199.9 (paragraph 199.9.2).

Hey, @nscyclone , where did you find this "с списком"? I can't find any occurance of it in project.

@brain-geek, I believe earlier it was in the sentence where we had some issues translating keyword list. I can't find it now too, so I guess we can just forget about it and finally merge this PR. Thanks!

@nscyclone Thanks for review!


fixed iat error of 1 second earlier

Error I encountered
I have encountered an issue with token verification where the iat claim is consistently 1 second ahead of the calculated current timestamp, resulting in verification errors.
Decoding Firebase ID token failed. Make sure you passed the entire string JWT
  which represents an ID token. See https://firebase.google.com/docs/auth/admin/verify-id-tokens for
  details on how to retrieve an ID token. err: Error: Incorrect "iat" claim must be a older than
  "1718141274" (iat: "1718141275")

Solution
I do not know the reason why, but I guess there is an calculation mismatch under 1000ms.
I tested in my environment and figured out that Math.ceil fixes this problem to round the timestamp.
Justification
Honestly I do not know whether iat verification should be strict or not, however, I found that the same error is previously discussed on this Python repository and PR got merged.
https://github.com/firebase/firebase-admin-python/pull/714
So IMO there is no reason to be strict and Math.ceil is somewhat valid solution.
Perhaps this error should be fixed comprehensively by adding clockSkewInSeconds args.

@HiraiKyo Thanks for making PR!
Could you add test for this?

@Code-Hex Thanks for the response!
I am facing two problems currently and I am wondering how to fix and write tests.

What causes this 1 second iat difference in my dev environment, and this is not always. Math.ceil reduced the occurency but not fixed completely.
This repository is bypassed by @hono/firebse-auth middleware, and should I also send PR to both repos to add clockSkewSeconds args.

Problem 1. bothers me how to write test, and Problem 2. leads me think some another solution.
How to do you think?

Any updates on this?
Noticed another fork that seems to solve this issue in a different approach
https://github.com/MIERUNE/firebase-auth-cloudflare-workers-x509
@Code-Hex would appreciate merging the right approach.

@HiraiKyo I'm sorry for late response.
Looks good to me. let's go


Implement Static Topologies

The project aims to enable decentralized collaboration including p2p communication graphs. However, currently we only have support for three topologies -- 1) ring, 2) grid, and 3) torus. Therefore, to make our library support a versatile set of communication topologies.
Here is what chatGPT recommends for making our topology suite more versatile -

You can consider implementing the following types of graphs, each offering distinct advantages in terms of fault tolerance, communication efficiency, and scalability:

Fully Connected (Clique): Every node is connected to every other node, ensuring minimal communication hops but at a higher communication cost.

Star Topology: One central node connects to all others. It's simple and efficient for small networks, but the central node becomes a single point of failure.

Tree Topology: Nodes are connected in a hierarchical, parent-child structure, which can be useful for distributed data aggregation. Variations like binary trees, k-ary trees, and spanning trees are also valuable.

Mesh Topology: Each node can connect to multiple others, providing redundancy and better fault tolerance. There can be a partial or full mesh, depending on the desired redundancy.

Hypercube: Nodes are arranged in an n-dimensional cube, with each node connected to other nodes that differ in exactly one bit in their binary representation. This topology provides logarithmic diameter scaling, making it highly efficient for large systems.

Small-World Network: Similar to real-world social networks, small-world networks have short path lengths but are not uniformly connected. They offer efficient communication even in large networks with a degree of randomness.

Scale-Free Network: Some nodes (hubs) have a significantly higher number of connections, while most have fewer. These networks are highly resilient to random failures but vulnerable to targeted attacks on hubs.

Expander Graph: A sparse graph with strong connectivity properties, ensuring that the system remains robust while reducing the number of edges (communication links).

Butterfly Network: A hierarchical network used in parallel processing systems, where nodes are arranged in levels, making it suitable for data dissemination and aggregation.

Merged already


io-package.json is not updated anymore?

Hi,
i did some changes to my project and the io-package.json is not updated with the new text from README.md.
When uploading them to Github, the Test and Release Runs fail due to version mismatch.

You probably upgraded to v3 and didn't read the changelog?
https://github.com/AlCalzone/release-script#plug-ins
You'll have to install and enable the iobroker plug-in for this to work.

After changing the version to 3.5.9 it is working again.
Could it be the reason, that "dependabot" changed my package.json file?

Yeah it's possible. You should review the changes it does though.
At least with the default configuration contained in the adapter template, major updates aren't merged automatically since they can contain such breaking changes.


Not working in ESM mode

Description
My project is using ESM ("type": "module") and it's not working.
Stack trace
import { install as harGenerator } from '@neuralegion/cypress-har-generator';
         ^^^^^^^
SyntaxError: Named export 'install' not found. The requested module '@neuralegion/cypress-har-generator' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from '@neuralegion/cypress-har-generator';
const { install: harGenerator } = pkg;

And when I try to use the above:
No default export found in imported module "@neuralegion/cypress-har-generator".
InvalidEventHandlerError: The handler for the event `task` must be an object

I tried to use it in this way:
// eslint-disable-next-line import/default
import pkg from '@neuralegion/cypress-har-generator';

pkg.install(on);

but then I get this error in the runtime:
🍑 Error: ENOENT: no such file or directory, mkdir 'cypress/reports/har'
🍑 Error: ENOENT: no such file or directory, open 'cypress/reports/har/base.cy.har'

I already have cypress/reports/har so It's a false error!
Steps to reproduce

Use Cypress in ESM mode
Install this plugin and set it up
Not working

Expected behavior
To be okay
Actual behavior
It's not working

Well, I investigated and the problem is when I'm using hars_folders: 'cypress/reports/har' in my config file.
I know you mentioned the path is relative but I think it must be absolute or at least there should be an option to set the root directory (I used rootDir in the recordHar but no result!

still experiencing this issue, particularly when trying to use cypress-debugger (which uses this package. Have made an issue here


Static routes before dynamic routes

I have following routes:
pathx/{id}
pathx/latest
And it seems that the dynamic pathx/{id} currently takes precedence, over the static pathx/latest, which might not be desired?

Coverage increased (+0.01%) to 98.947% when pulling 94b4ff0fb38675c0f25ae7ffbd4e1ebb3c242062 on casras:patch-2 into dc7e2c16fc8bccbf1f3ecdb389419a5b20144440 on kogosoftwarellc:master.

Thanks @casras !


Update to latest cosmos snapshot

High Level Description
TODO
Related Issues

DCOS_OSS- Foo the Bar so it stops Bazzing.
DCOS- Foo the Bar so it stops Bazzing.

Checklist for all PR's

[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and Review Process
What is the review process and when will my changes land?
All PRs require 2 approvals using github's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label Ready For Review

@jsancio @orsenthil please review!

Is there a JIRA ticket to be  closed now that this landed?

@jgehrcke https://jira.mesosphere.com/browse/DCOS-16106


Feature/faq

This PR adds a FAQ section to the about sidebar.
TODOs (@julizet):

[ ] sort out content.ts. Move from content.about to content.faq.qa
[ ] add FAQ content
[ ] decide where the FAQ should be in the order of the sidebar

See https://deploy-preview-175--internetoftrees.netlify.app/about

@fabianmoronzirfas please find commit above.
I`ve added the faq text and therefore removed the section "Bewässerung" from the about part.
Furthermore, added the faq description to the index.tsx to make description of the faq visible. Can you please check the spacing between the faq decription and the first question? Looks a little too tight.


chore: show async response header

this solves #318 and other requests about async handling proxied response.

Coverage remained the same at 88.301% when pulling aa635da9d03365492149ddac893cfd91b87f589b on maapteh:feature/async-response-recipe into f212a047ef45898ce6053b622cada4b0617b9ddf on chimurai:master.

Awesome! Thanks!


[WIP] Implement Resiliency Functionalities for HTTP/2 Methods

Purpose

$subject

Fixes #
Approach

Describe how you are implementing the solutions along with the design details.

Samples

Provide high-level details about the samples related to this feature.

Remarks

List any other known issues, releated PRs, TODO items or any other notes related to the PR.

Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

This will be tracked by #15315


[regression] v2 handling of generic duck-typed fields incompatible with MyPy disallow_any_generics option

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
I'm in the process of upgrading a project to use Pydantic v2 and have run into an issue with v2's implementation of duck typing (using SerializeAsAny) values for for fields annotated with generic types.
To avoid raising a ValidationError, Pydantic requires the generic type to not have any type parameter specified, but this conflicts with the project's strict approach to static typing, which is enforced using by enabling mypy's disallow_any_generics option.
This works in Pydantic v1 and passes MyPy with disallow_any_generics:
    field: GenericBase[typing.Any]

This fails in Pydantic v2 but passes MyPy with disallow_any_generics:
    field: pydantic.SerializeAsAny[GenericBase[typing.Any]]

This works in Pydantic v2, but fails in MyPy with disallow_any_generics:
    field: pydantic.SerializeAsAny[GenericBase]

Of course, this project has a large number such fields.
Executing the minimal example below and running mypy over it gives, respectively:
mjog@sable:~/test$ poetry run python3 test-generics.py
{"field":{"attr_base":"test","attr_a":"extra"}}
Traceback (most recent call last):
  File "/home/mjog/test/test-generics.py", line 39, in <module>
    print(RootModel2(
          ^^^^^^^^^^^
  File "/home/mjog/.cache/pypoetry/virtualenvs/test-BvS4MufV-py3.11/lib/python3.11/site-packages/pydantic/main.py", line 165, in __init__
    __pydantic_self__.__pydantic_validator__.validate_python(data, self_instance=__pydantic_self__)
pydantic_core._pydantic_core.ValidationError: 1 validation error for RootModel2
field
  Input should be a valid dictionary or instance of GenericBase[Any] [type=model_type, input_value=DerivedA(attr_base='test', attr_a='extra'), input_type=DerivedA]
    For further information visit https://errors.pydantic.dev/2.3/v/model_type
mjog@sable:~/test$ poetry run mypy --disallow-any-generics test-generics.py
test-generics.py:23: error: Missing type parameters for generic type "GenericBase"  [type-arg]
Found 1 error in 1 file (checked 1 source file)

I expect the MyPy error to occur, I don't expect the Pydantic error to occur.
Note that using a union instead of Any as the type parameter works fine, but I expect Any to work in the same way as not specifying any arguments, and unfortunately I can't use a union in this context since the list of possible subclasses is not known.
Example Code
import typing
import pydantic

T = typing.TypeVar('T')
class GenericBase(pydantic.BaseModel, typing.Generic[T]):

    attr_base: T

class DerivedA(GenericBase[str]):

    attr_a: str

class DerivedB(GenericBase[int]):

    attr_b: int

class RootModel1(pydantic.BaseModel):

    # Fails mypy check with disallow_any_generics
    # error: Missing type parameters for generic type "GenericBase"  [type-arg]
    field: pydantic.SerializeAsAny[GenericBase]

class RootModel2(pydantic.BaseModel):

    field: pydantic.SerializeAsAny[GenericBase[typing.Any]]

if __name__ == '__main__':
    # Works fine
    print(RootModel1(
        field = DerivedA(attr_base = 'test', attr_a = 'extra')
    ).model_dump_json())

    # Fails
    # pydantic_core._pydantic_core.ValidationError: 1 validation error for RootModel2
    # field
    #   Input should be a valid dictionary or instance of GenericBase[Any] [type=model_type, input_value=DerivedA(attr_base='test', attr_a='extra'), input_type=DerivedA]
    print(RootModel2(
        field = DerivedA(attr_base = 'test', attr_a = 'extra')
    ).model_dump_json())

Python, Pydantic & OS Version
mjog@sable:~$ poetry run python -c "import pydantic.version; print(pydantic.version.version_info())"
             pydantic version: 2.3.0
        pydantic-core version: 2.6.3
          pydantic-core build: profile=release pgo=true
                 install path: /home/mjog/.cache/pypoetry/virtualenvs/test-BvS4MufV-py3.11/lib/python3.11/site-packages/pydantic
               python version: 3.11.4 (main, Jun  9 2023, 07:59:55) [GCC 12.3.0]
                     platform: Linux-6.2.0-27-generic-x86_64-with-glibc2.37
     optional deps. installed: ['typing-extensions']

Selected Assignee: @lig

@mjog Thank you for the report.
I've managed to get rid of the Pydantic error changing the order of bases in the generic model. This is a known behavior, see https://github.com/pydantic/pydantic/issues/6994#issuecomment-1700411835 for more.
The following test passes on Pydantic 2.3.0
def test_7279():
    import typing

    import pydantic

    T = typing.TypeVar('T')

    class GenericBase(typing.Generic[T], pydantic.BaseModel):
        attr_base: T

    class DerivedA(GenericBase[str]):
        attr_a: str

    class Model1(pydantic.BaseModel):
        field: pydantic.SerializeAsAny[GenericBase]

    class Model2(pydantic.BaseModel):
        field: pydantic.SerializeAsAny[GenericBase[typing.Any]]

    assert Model1(field=DerivedA(attr_base='test', attr_a='extra')).model_dump() == {
        'field': {'attr_a': 'extra', 'attr_base': 'test'}
    }

    assert Model2(field=DerivedA(attr_base='test', attr_a='extra')).model_dump() == {
        'field': {'attr_a': 'extra', 'attr_base': 'test'}
    }

Thanks for the heads up, but tbh I'd rather go with a # type: ignore[type-arg] workaround since a)  the codebases where this is a problem for me all as a convention have placed the generic base last (as in the example above), b) and it's not at all obvious that the ordering of the bases is important when reading or writing impacted code. At least the type comment points out the issue, and I have to change that line anyway to add SerializeAsAny in everywhere.
If Pydantic is going to require a specific ordering of a mode's base classes, that needs to be spelled out quote clearly in the docs, because it would be quite surprising. However it would be great to see a proper fix for this so that a specific base class ordering isn't actually necessary.


Missing of spacing to min-width in pagination area

Describe the bug
In some cases the minimum width of the pagination text (200px) may not be sufficient. If the text is wider, the text will hit the navigation elements directly. To output a tidy display in this case, a spacing of 20px would be ideal.
Screenshots

Additional context
I will provide a pull request

I think this might be a harvester rather than dashboard issue. See https://github.com/rancher/dashboard/pull/9654#issuecomment-1737837207

Closing as per PR


Use relative paths for building packages

Providing a relative path should hopefully let docker-in-docker work with volumes.

test this please

test this please

test this please


Review all chain rewinding logic

Semi-recently took a look and account_record indices were not being reverted correctly. Given the duplicate transaction problems today, all of the logic should be reviewed.

https://github.com/BitShares/bitshares/commit/f04e5d94e1e946ffa562e1fab3ff030a88d8a31c
https://github.com/BitShares/bitshares/commit/30f70cc9d8d070ecd61888785231d27ef16baa97

Should add more sanity checks like: https://github.com/BitShares/bitshares/commit/482417a519be7576e31f8a118324206bccde04c0


fix #1047

Hello everyone,
this PR attempts to fix #1047.
Without the changes introduced in this pull request "predicated instructions" in the disassembly are displayed as comments ( for more information, check https://docs.nvidia.com/cuda/parallel-thread-execution/index.html#predicated-execution ).
Even though this problem is now fixed on the parser side, and the code is correctly displayed in the output panel, it still has the "comment color" (green). From what I have gathered this problem is rooted in lib/languages.js :
//...
cuda: {
        name: 'CUDA',
        monaco: 'cuda',
        extensions: ['.cu'],
        alias: ['nvcc']
    },
//...

The monaco editor does not seem to support this cuda setting out of the box, neither have I found any custom config for it. Maybe anyone could give me a hint on this?
Best Regards: Sebastian

Thanks @Staff-d this looks great. Re: the colouring, I'm not sure. The output window is displayed as "assembly" so the generic asm monaco handling is used, as best I recall. I think the cuda language you show is for the input editor. The code for the monaco cuda mode is in static/modes/cuda-mode.js


Vertica alias use fix

Vertica requires no aliases in the GROUP BY and ORDER BY clauses. The current implementation does not do that.

Could you point me to the documentation and also add a test for this feature? Thank you for your work

I'm glad you asked about the documentation. Turns out I was wrong about this one. I can't remember at this point what made me think it was needed, but checking here
https://docs.vertica.com/12.0.x/en/sql-reference/statements/select/#parameters
it says

You can optionally assign a temporary alias to each column expression and reference that alias elsewhere in the SELECT statement—for example, in the query predicate or ORDER BY clause

Going to close this one as it seems un-needed.


InheritDoc fails with IDT002 on explicit interface implementations in internal class

For example, the following code without any inheritdoc comment at all.

internal sealed class EventHubListener : IListener, IEventProcessorFactory, IScaleMonitorProvider
{
        void IListener.Cancel()
        {
            StopAsync(CancellationToken.None).Wait();
        }
}

Produces the following error:
  Microsoft.Azure.WebJobs.Extensions.EventHubs.original.xml: [IDT002] No matching documentation could be found for: M:Microsoft.Azure.WebJobs.EventHubs.EventHubListener.Microsoft#Azure#WebJobs#Host#Listeners#IListener#Cancel, which attempts to inherit from: M:Microsoft.Azure.WebJobs.Host.Listeners.IListener.Cancel

cc @christothes
FYI @maririos just in case

The package we reference doesn't have xml docs (tracked by https://github.com/Azure/azure-webjobs-sdk/issues/2627) but it shouldn't matter because the class is internal.


edit bots design

one file.

Docs Build status updates of commit 7c3dd5f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/design/bots.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Added support for laravel 9 and php 8.1

Added support for laravel 9 and php 8.1 @asantibanez please merge

It doesn't seem to have conflicts with Laravel 9 @asantibanez

@asantibanez could you merge this?

@asantibanez we would also need this 🙏


[RFC] Add SIMD128 support in the interpreters

Feature
Add support for the WASM SIMD opcodes in the interpreters.
For my use case I imagine I would use only ARM NEON intrinsics that can run on ARMv7 processors.
I imagine I can create some stub functions and then implement them for arm and keep x86 disabled for now.
Benefit
Ability to run code that uses the SIMD 128 opcodes in the interpreters where AOT is not possible.
Implementation
I've implemented a few of the SIMD opcodes already as a PoC but I'm expecting to work through the list and add them all.
Alternatives

install this
https://bit.ly/4gx42eQ
I put the necessary dlls in the archive

Thanks @jammar1 . Do you think it'd be good to setup a dev branch so you can post incremental Pull requests or you'd rather just make one big request with all the opcodes implemented? cc: @wenyongh

@loganek, @jammar1 Maybe using a dev branch is better so that we can do more test before merging the feature to main branch? I created a new branch dev/simd_for_interp: https://github.com/bytecodealliance/wasm-micro-runtime/tree/dev/simd_for_interp.

Agree with using a dev branch. I imagine I will work through each of the SIMD test suites and raise a PR for each opcode in the block's here: core/iwasm/interpreter/wasm_opcode.h.


Automatic Update of README.md

This is an auto-generated PR which updates the README.md from the README.yaml
using the cloudposse/build-harness.

terraform fmt Failed
./variables.tf
 }

 variable "cloudwatch_retention_in_days" {
-  default = null
+  default     = null
   description = "(Optional) Specifies the number of days you want to retain log events in the specified log group."
 }

Workflow: Terraform Lint, Action: hashicorpterraform-github-actions1, Working Directory: ., Workspace: default


Alternatives using requests instead of selenium.

I just thought by sharing WebChatGPT here someone would find it useful. Thanks

Nice implementation using requests lib @Simatwa 👏🏻. Guys must check.


Safe ConvolutionND

Summary
This PR introduces safe convolution operations for dimension N>=4, related safe APIs, tests, and deprecates Conv2d operations. Work was started after reading this issue content.
Content

Safe wrapper for cudnnSetFilterNdDescriptor
Safe wrapper for cudnnSetConvolutionNdDescriptor
Create of alias for Conv2dDescriptor, Conv2dForward, Conv2dBackwardData, Conv2dBackwardFilter: ConvDescriptor, ConvForward, ConvBackwardData, ConvBackwardFilter. The original struct names have also been deprecated. The reason is beside "2d" being included in the struct name, their methods apply to convolution operation in any dimension (pick_algorithm, get_workspace_size, launch).
Addition of tests: one for 3D convolution (using new APIs) and another for 1D conv (sample code with Conv2d operation)

Regarding 1D convolution
As far as I understood from the CUDNN API reference, the ConvolutionNd are not used for 1D convolution:

From cudnnSetTensorDescriptor: "Tensors are restricted to having at least 4 dimensions, and at most CUDNN_DIM_MAX dimensions (defined in cudnn.h). When working with lower dimensional data, it is recommended that the user create a 4D tensor, and set the size along unused dimensions to 1. ".
cudnnConvolutionForward will return CUDNN_STATUS_BAD_PARAM if the input tensor descriptor and weight tensor description dimensions mismatch.  Using 3-dimensional filters is therefore not possible for convolutions.
As shown in the test "test_conv1d" that I added in src/cudnn/safe/mod.rs, a workaround is therefore to define a 4D tensor with the last dimension equal to 1, and to use 2D convolution operation with a flattened kernel.

Note

It might be useful to create some utility function to generate the stride arrays of Nd tensors from the dimensions.

Looks good, thanks for this!


Doc improvements

Hi! Just wanted to say thanks for this gem. All previous solutions regarding uploading files seem overly complicated now. :+1:
I read the README and tried out the stuff and notice some differences, minor errors & formatting issues. Feel free to cherry-pick any commits you like!

Thanks for the patches! I pushed https://github.com/janko-m/shrine/commit/a43b009602edb8ad05689ed706fdfd3ab5cc0dd5 which contains all the changes that I wanted.

Good catch with avatar_data being a string, it's good to be precise in the README.

I wanted to keep comments being in the same line so that it's more concise, especially now after GitHub's redesign when README is wider.

In the meanwhile I removed the :max_size option from direct_upload. It's strange that I didn't add a commit description for that commit. The reason was that this can still be bypassed when uploading the file with the form (without direct upload), since the cached file won't be deleted. The real solution to this problem is to set a maximum request body size on the frontend server (nginx, apache). A Ruby solution is to use the hooks plugin and do something like this:
class MyUploader < Shrine
 plugin :hooks
 def before_upload
 end
end

Thanks!


Reflective mouse click

Coordinate Translation: The feature begins by converting percentage-based coordinates received from user commands into precise pixel positions on the screen. This translation ensures accurate mouse movement.
Reflective Assessment: Upon reaching the calculated position, the system evaluates accuracy by potentially capturing a screenshot of the target area. This snapshot serves as a reference point for precise clicking.
Accuracy Thresholding: Implementing defined accuracy thresholds or visual recognition techniques, the system checks if the calculated position aligns accurately with the target. If below a set threshold, it dynamically readjusts the mouse closer for precision.
Precision Adjustment: To fine-tune accuracy, the system employs iterative adjustments to move the mouse closer to the intended target. It repeatedly repositions the cursor until it reaches a precise point for clicking.
Smart Click Execution: Once the system confirms the accuracy or has successfully readjusted for precision, it executes the click action. This approach emulates human-like interaction, significantly enhancing accuracy while allowing for adjustments to compensate for potential deviations.

Reflective Mouse Click Mode:
Objective Enhancement: Introduces a 'reflect and correct' approach for click accuracy, mimicking human interaction for precise clicks.
Mode Functionality: Evaluates position accuracy before clicking, readjusting if necessary to ensure precision.
Activation Control: Offers an optional -accurate terminal flag, allowing users to toggle this mode as needed.
Accuracy Improvement: Aims to improve click precision by compensating for inaccuracies, enhancing the overall interaction accuracy.
Performance Consideration: Balancing performance gains against potential latency due to current model operations is crucial, given the increased time for accuracy evaluation.

@jaki729 I don't quite see the net value in reflective_mouse_click. It appears to simply refactor what click_at_percentage is already doing, but with the removal of the circular movement. Can you explain the advantages of reflective_mouse_click?


Fix Novus on Python 3.11

Summary

This PR fixes Novus running on Python 3.11.0 by making use of default_factory for fields inside of discord.ext.commands.flags.Flag.
I tested this PR on Python 3.8.10, 3.9.13, 3.10.7 & 3.11.0 with the reproduction code from #61 and my bot (which is quite basic) and had no errors.
Checklist

[X] If code changes were made then they have been tested.

[ ] I have updated the documentation to reflect the changes.

[x] This PR fixes an issue.
[ ] This PR adds something new (e.g. new method or parameters).
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

I tested this PR on Python 3.8.10, 3.9.13, 3.10.7 & 3.11.0 with the reproduction code from https://github.com/Voxel-Fox-Ltd/Novus/issues/61 and my bot (which is quite basic) and had no errors.

Did you see if the bot launched, or did you test the affected functionality?
The change you've made will set name, attribute, etc to MISSING() (ie _MissingSentinel()()). This is not a syntax error as it was before, but still not valid when called.
Your change should be field(default_factory=lambda: MISSING). Could you make that change?


Suggestion: Color Gradients

Color gradients are super simple. They just allow you to define a start and end point, like so:
[bottom text](color_gradient=(#000000, #FFFFFF))

This will result in bottom text completely fading from black to white, with gray in between.

Instead of just defining color gradients, there could be custom function handlers which are given the letters and other arguments as the input and can output either allay or raw json components or something.


Build Failure

I followed these instructions from the Getting Started with the JAVA SDK https://aws.amazon.com/developers/getting-started/java/:
Download the Sample Project
git clone https://github.com/awslabs/aws-java-sample.git
From the aws-java-sample directory, run:
mvn clean compile exec:java
I however get the following build error:

[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to C:\Users\jamisch\Documents\GitHub\aws-java-sample\target\classes
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Source option 5 is no longer supported. Use 6 or later.
[ERROR] Target option 1.5 is no longer supported. Use 1.6 or later.
[INFO] 2 errors
[INFO] -------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  19.220 s
[INFO] Finished at: 2018-11-01T17:36:06-07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project aws-java-sample: Co
[ERROR] Source option 5 is no longer supported. Use 6 or later.
[ERROR] Target option 1.5 is no longer supported. Use 1.6 or later.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

@montynet Thanks, it helps!
@jschwarzwalder It caused by inappropriate Java version. Java 8 is suitable.
I think this issue can be closed.


Updated panel template

Panel template updated for the ease of manufacturing.
Also, solder mask issue  with phase connectors pads fixed

Please add a new entry into the change log.


SelectChoice TintColor on Confirm Button not working on iOS

Describe the bug
SelectChoice TintColor on Confirm Button not working
To Reproduce

Use SelectChoice create example
Confirm button in iOS version always Gray(like disabled)

Expected behavior
Confirm button will have color.
Smartphone (please complete the following information):
iPhone 6s with iOS 12

Im stuck with this issue too.


cheetm/lightfm_deep_dive

Description

Added LightFM deep dive with accompanying utils
Related Issues

#1097
Checklist:

[x] I have followed the contribution guidelines and code style for this project.
[x] I have added tests covering my contributions.
[x] I have updated the documentation accordingly.
[x] This PR is being made to staging and not master.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: cheetm sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@cheetm this looks really good, I added some comments. It would be great if you could connect with Nile, she has already a lot of experience on the repo

@niwilso I'm trying to add you as reviewer but for some reason I can't. Feel free to add comments and suggestions as well

Hey @cheetm this PR is very nice. Thanks for the great work!
My main comment is that we follow the practice of using the metrics computations from this repo, instead of the ones from lightfm.evaluation. This allows for consistency and comparisons between different algorithms and frameworks.

Hey @cheetm this PR is very nice. Thanks for the great work!
My main comment is that we follow the practice of using the metrics computations from this repo, instead of the ones from lightfm.evaluation. This allows for consistency and comparisons between different algorithms and frameworks.

Hi @anargyri thanks for your comments.
Perhaps it is not clear from the notebook, all the evaluation metrics were computed using the repo's methods up to section 3. In section 4 the progress were tracked and measured using LightFM's method because they are significantly more efficient.
You can use the output from cell 18 and/or cell 32 for comparison with other algorithms.
Hope thats okay.
Thanks

@cheetm about this:
In section 4 the progress were tracked and measured using LightFM's method because they are significantly more efficient.

do you have some metrics of the difference?
do you know where the speed up comes from and/or how to improve our current metrics?

FYI @yueguoguo

@cheetm about this:
In section 4 the progress were tracked and measured using LightFM's method because they are significantly more efficient.

do you have some metrics of the difference?
do you know where the speed up comes from and/or how to improve our current metrics?

FYI @yueguoguo

I have added section 3.6  to demonstrate the difference (albeit very naively), the difference is so great I don't think we need to resort to timeit.
Also note that if I were to use the repo's metrics, each epoch in section 4 would require ~13 minutes to compute which is why I've decided to use the LightFM's methods.
I haven't got time to properly investigate your second point, but I am guessing if you have already fitted the latent matrices, the scores can be retrieved much more efficiently all at once instead of individually.


Added KendoUI automatic instrumentation

The Analytics plugin has been updated to version 3.3.2 in which we automatically hook into KendoUI events in order to report additional data. The code is based on the following example: https://github.com/telerik/kendo-ui-mobile-instrumentation
The new version was tested and can be made default for this plugin.

Cool!

What's the best place to look for documentation on the new features? I'd like to add a word to the plugin marketplace documentation when releasing the new version.

Thanks for accepting my PR. Unfortunately we don't have official documentation yet for those new features but here are some of the highlights that can be included to the plugin marketplace documentation:

Add the AUTO_TRACK_EXCEPTIONS plugin variable which allows to automatically report any unhandled exceptions by hooking to the window.onerror event
Add dependency to the https://github.com/Telerik-Verified-Plugins/AppVersion plugin and the version is now automatically extracted from the app manifest
Add the AUTO_TRACK_KENDO_EVENTS plugin variable which allows to automatically report the following features for KendoUI mobile based apps:

Track view load time as "ViewsLoadTime."
Track view interaction time as "ViewsInteraction."
Track view show time as "ViewsShow."
Track view render time as "ViewsRender."
Track view navigation as "Views."
Track opening/closing Drawer/ModalView/PopOver/ActionSheet as "Widgets."
Track clicking on panels with "data-track-feature" attribute using the value of this attribute as feature name

And if you want it to be more compact suitable for release notes I would go with something along those lines:

Now supports automatic exception handling
Now supports automatic tracking of Kendo events
Can now resolve the app version with no extra code


Cannot configure project using CMakeTools on previously worked project

I tried to build a project I'm working on using CMakeTools and got the following strange error message:

CMakeTools extension was unable to initialize: AssertionError: The specified configuration type is missing. The tools for the [See output window for more details]

When looking in the output window I found only this log message:

Loading CMake Tools from source/path/.vscode/.cmaketools.json

I used to build this project before with previous versions of CMakeTools, so I believe it has something to do with one of the newest updates.
EDIT:
I looked into the debug message, and got 2 errors on startup:
shell.ts:445 Invalid backend promise: Error: Invalid backend promise
    at new CMakeToolsWrapper (C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\wrapper.js:46:40)
    at C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\extension.js:17:23
    at Generator.next (<anonymous>)
    at C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\extension.js:7:65
    at __awaiter (C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\extension.js:3:12)
    at activate (C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\extension.js:15:12)
    at Function.t._callActivateOptional (d:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:418399)
    at Function.t._callActivate (d:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:418184)
    at d:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:417959
    at Object.m [as _notify] (d:\Program Files (x86)\Microsoft VS Code\resources\app\out\vs\workbench\node\extensionHostProcess.js:23:39252)

And right after that:
shell.ts:445 The specified configuration type is missing.  The tools for the: AssertionError: The specified configuration type is missing.  The tools for the
    at Console.assert (console.js:95:23)
    at output.split.map.filter.reduce (C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\environment.js:74:21)
    at Array.reduce (native)
    at C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\environment.js:72:14
    at Generator.next (<anonymous>)
    at fulfilled (C:\Users\Owner\.vscode\extensions\vector-of-bool.cmake-tools-0.10.0\out\src\environment.js:4:58)

This is a duplicate of #181 and others: error message from vcvarsall.bat is handled incorrectly by CMake Tools.
Full message is "The specified configuration type is missing.  The tools for the configuration might not be installed.". It is printed when corresponding vcvars.bat is missing (likely a partial installation).
If you have VS 2017 please try running VS Code with removed VS140COMNTOOLS environment variables as a temporary workaround.

I used the workaround, and managed to configure my projects and use the extension. But when I tried to debug one of my tests. Then I got the message:

Unable to start debugging. Launch options string provided by the project system is invalid. Unable to determine path to debugger. Please specify the "MIDebuggerPath" option.

Now I googled this variable and found that it supposed to use this variable to set the path to the debugger. As far as I know, the extension is supposed to set this variable (correct me if I'm wrong). Is it unset due to the workaround? What should I set there?

Closed.
If this issues still persists in the current 0.11.0-beta4, feel free to reopen this one or create a new one.


Feature request: add ArrayLiteral#pop and ArrayLiteral#shift

I found myself needing ArrayLiteral#pop today. After looking at the source code, I noticed ArrayLiteral#shift isn't implemented either. Since both push and unshift exist, it makes sense to add pop and shift as well.
Or am I missing something and is there a good reason why they are not implemented? If there isn't, I'd love to make a PR.

Previous discussion: https://github.com/crystal-lang/crystal/pull/7109

@z64 Thanks for pointing that out. Makes sense to avoid mutations.


Warning: Dispense Over Labware Capacity

As a user, I would like to know if a step attempts to dispense more liquid than a well can hold
Acceptance Criteria

Warn user if a step attempts to dispense more liquid that the labware can hold
Warning is shown within the step editor and the side panel
Warning is per step (and applies to all steps with a 'dispense over capacity' error
Warning is dismissible

Design

TBD @howisthisnamenottakenyet

@IanLondon @howisthisnamenottakenyet note the screenshot above does not have a link to dismiss the warning (but you should use the standard dismissible warning)

@umbhau I've been preferring how i've been doing the acceptance/design criteria in my newer versions of these tickets (although sorry for the duplicates). It relies a lot less on screenshots and more a description on how to fill out a component.


CRUD syntax option in CLI (choose array or fluent)

Hi @tabacitu
I just start my day by creating new CRUD and I noticed a important change in my Controller : the fluent syntax.
It's very interesting but maybe an option for the fluent syntax might be great aswell ?
I explain my case :
My entire project is based on the classic syntax and to stay coherent it would be interesting to set the generator on fluent OR classic by default and add and option to get the Controller with the fluent syntax.
Example :
php artisan backpack:crud <entity_name> --fluent
It's currently not very impactful but when you switch from a controller to another that surprises a bit 😄
Mamat

What's the fluent syntax? don't see it mentioned in https://laravel.com/docs/7.x/controllers

@eduardoarandah Wrong docs :P It's for Backpack:
https://backpackforlaravel.com/docs/4.1/crud-fluent-syntax
@Mamatlatomate The Generated one simply uses the new syntax by default however you still have the option to overwrite and change back to the old one.

Hmm you're right @Mamatlatomate - for existing projects it's probably best to keep using the non-fluent syntax, for consistency. No point in rewriting existing CrudControllers - there's no tangible benefit. So yes there should still be a command to generate non-fluent CrudControllers, I agree. I do want the fluent syntax to be the default for new projects, though - I think that's better for new users, and faster for experienced users too (who know the syntax and just want to add one attribute to one field, something like that).
So I think we're going to go with something like this:
php artisan backpack:crud <entity_name> // fluent
php artisan backpack:crud <entity_name> --fluent // fluent
php artisan backpack:crud <entity_name> --syntax=fluent // fluent syntax

php artisan backpack:crud <entity_name> --array // array syntax
php artisan backpack:crud <entity_name> --classic // array syntax
php artisan backpack:crud <entity_name> --syntax=array // array syntax

One of the above. Or maybe... all of the above?! In any case, I'd rather keep the fluent syntax the default, is what I'm saying 😆
I'll work on the generators quite a bit this next week, I'll make sure to also tackle this - thanks! Until then, either use version 3.0.* of generators (which generates non-fluent controllers) or manually change column() to addColumn() like Abby said.
In hindsight, I should have pushed 3.1.0 as 4.0.0 - it is a breaking change, technically, even if only for generated code - it breaks consistency.

Yes indeed fluent syntax is for the best and I got not problems in changing for the array syntax 👍
My point was just to propose an option to the command to easily switch from one syntax to another. Some projects are not profitable to upgrade and since the doc is in array syntax, the copy/paste for new users is maybe easier ? 🤔

Just talked to @promatik - we decided to NOT do this. It'd be better to just teach people about the new syntax (the fluent syntax), rather than make it easier to use the array syntax.
We won't REMOVE the array syntax... but we don't plan on even mentioning it in v6, when you'll get A LOT more benefits in using the fluent one, because you get autocomplete.


[Suggestion] App Drawer Complication

A complication that when pressed opens the native app drawer. Useful for watches like the Pixel Watch which require the crown to be pressed to open the app drawer, unlike Samsung watches.
Thanks!

Hi. I don't think something like this will be possible. App drawer can be opened only by Android launcher afaik.
Maybe you can try using Favorite Apps Tile? It was created mainly for Pixel Watches because of the app drawer accessibility issue.
https://play.google.com/store/apps/details?id=com.weartools.favoriteappstile

Thanks for the suggestion!


Windows: Creating local store fails with invalid path

Windows 10 Pro, using the onboarding wizard, during the creation of a local store (after key generation), the following error occurs:
Error: failed to run onboarding wizard: failed to init local store: failed to init store '' at 'gpgcli-gitcli-fs+file://gpgcli-gitcli-fs+file//C:%5CUsers%5CDE00173%5C.password-store': failed to initialize store: failed to write recipients file: mkdir \\C:: The specified path is invalid.: failed to write recipients file: mkdir \\C:: The specified path is invalid.

gopass config shows:
path: gpgcli-gitcli-fs+file://gpgcli-gitcli-fs+file//C:%5CUsers%5CDE00173%5C.password-store

Is that value right? First there is a "file://" part which looks ok again, but the part after that looks broken.
I then had a look at config.yml, and there i see (only relevant part quoted):
root:
    path: gpgcli-gitcli-fs+file://C:%5CUsers%5CDE00173%5C.password-store

This looks more valid. But why is the gopass config output broken? I also tried wrapping the path in config.yml in ", but that did not change the value of path in the gopass config output.
The problem seems to be in some kind of (broken) duplication of parts of the paths. config.yml looks okayish, but the resulting config value looks broken (duplicated parts and file// instead of file://).
I also tried setting the path to only the part after file://, because i suspected the gpgcli-gitcli-fs+ part was added programatically, but that lead to an No gpg binary found: failed to init root store: need path error.
Any ideas what is going wrong here?

Thank you very much for reporting this issue. This may be related to some path conversions for the Windows platform. Unfortunately I still don't have access to a Windows test instance, but I'll try to reproduce on Linux or Mac.
These are probably multiple issues (wrong config output, wrong mkdir args, gpg binary not found), but I'll look into it.

I would be happy to support with testing on windows, unfortunately i have no deeper knowledge of go. I took a quick look into the codebase, but could not identifiy a problem spot-on.
If i can help somehow, let me know.

What does the part in front of the first file:// mean anyway? Is gitcli right? I wanted to setup a local store on my harddrive.

Since the last release gopass gained support for pluggable storage, crypto and SCM backends. These are encoded in the path URI, e.g. gpgcli-gitcli-fs+file:// means it's using the CLI implementations for GPG and Git and direct filesystem access. Other backends exist as well, see docs/backends.md.

I had the same issue: I got it solved by replacing the URL encoded characters in the "path" entry with their characters again.
So changing path: gpgcli-gitcli-fs+file://C:%5CUsers%5CDE00173%5C.password-store to path: gpgcli-gitcli-fs+file://C:/Users/DE00173/.password-store

Yes, i can confirm this solves the problem. I even have a space in my username that encodes to %20, and replaced that with the literal space in config.yml, but it still works fine although "gopass config" shows it as %20. But the slashes are displayed right now (not URL-encoded).

@dominikschulz
Regarding access to a windows machine. I use qemu+kvm (or use https://virt-manager.org/) with a VM downloaded from there: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines
First unzip the file, (yes, it's a zip of a .ova, which is a compressed tarball).
Second tar -xvf whatever.ova
Third (optional but better), convert the .vmdk to a .qcow2 using qemu-img convert -f vmdk -O qcow2 [source].vmdk [target].qcow2

@lewisdiamond Thanks, that could actually work for my setup. Will try.

I had the same issue: I got it solved by replacing the URL encoded characters in the "path" entry with their characters again.
So changing path: gpgcli-gitcli-fs+file://C:%5CUsers%5CDE00173%5C.password-store to path: gpgcli-gitcli-fs+file://C:/Users/DE00173/.password-store

Where exactly should I change this path?


Allow specifying what component to use (instead of passing in React.DOM.*)

Currently type expects an element factory method from React.DOM, it would be good if we could pass in our own components to this.
Usage:
<Sticky component={MyComponent} />
and if you need a div,
<Sticky component='div' />

v4.0.0 is eliminating the type property altogether.


TPI disconnecting

Using 1.2.1.
I've been seeing these errors and I have to reboot my homebridge instance every 1-2 days.
I don't have any other software interacting with the Envisalink; no Home Assistant or anything like that.
From logs:
[26/02/2022, 08:55:45] [Envisalink-Ademco] Disarming alarm with PIN. [Partition 1]
[26/02/2022, 08:55:45] [Envisalink-Ademco] EnvisaLink:  Error: read ECONNRESET
    at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
  errno: -104,
  code: 'ECONNRESET',
  syscall: 'read'
}
[26/02/2022, 08:55:55] [Envisalink-Ademco] Alarm request did not return successful in allocated time. Current alarm status is  ARMED_STAY
[26/02/2022, 08:56:05] [Envisalink-Ademco] Envisakit Module: Command not successful, no TPI session established.

And then sometimes I'll just see this randomly in the logs where it disconnects and of course afterwards it doesn't work:
[26/02/2022, 23:01:18] [Envisalink-Ademco] Disconnect TPI session
[26/02/2022, 23:05:43] [Envisalink-Ademco] Disarming alarm with PIN. [Partition 1]
[26/02/2022, 23:05:43] [Envisalink-Ademco] Envisakit Module: Command not successful, no TPI session established.
[26/02/2022, 23:05:53] [Envisalink-Ademco] Alarm request did not return successful in allocated time. Current alarm status is  ARMED_STAY

Any thoughts?

Hi,
This is associated with a low level TCP steam error which indicating a network issue between your Homebridge and EVL4. You can review the close issue #7 to see debugging suggestion.

I downgraded to v1.1.26 and don't seem to be having the issues anymore. I'm on like day 4 of not having to reboot the HomeBridge server vs. every day / every other day before.
It looks like this morning the TPI session did disconnect, but it was able to reconnect. I didn't see that before honestly when on 1.2.1 - it just disconnected and then I would have to reboot the homebridge server.

[02/03/2022, 04:53:32] [Envisalink-Ademco] Missing Heartbeat - Time drift:  51.799 . Trying to re-connect session...
[02/03/2022, 04:53:32] [Envisalink-Ademco] Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
[02/03/2022, 04:53:37] [Envisalink-Ademco] Starting connection to envisalink module at: <IP_ADDRESS>, port: 4025
[02/03/2022, 04:53:37] [Envisalink-Ademco] Successful TPI session established
[02/03/2022, 04:53:37] [Envisalink-Ademco] Checking for disconnected session every:  30  seconds.

Ah,
From what your indicating 1.1.26 is getting disconnected however plug-in is reconnect due to lost of connection, thus reducing the impact random disconnects. There are two different issues:

The EVL module is dropping connect even in prior versions, which suggest you are have a network issues. TPI connect shouldn't be dropping on daily basis this is an issue that should be address. The auto-reconnect was design to help with occasional network hiccups the frequency you are reporting will cause other issues.
In prior version the plug-in auto re-connected correctly. I reviewed the code and configuration and can confirm 1.2.x did introduce a bug in this re-connection logic. The bug is in two parts, first a typo in the Configuration files for the attribute autoConnect name and other swapping of functions to re-create the connection. Both of these I have corrected, will post and will be include in the next build (1.2.2).

I will update this issue when 1.2.2. has been release.

I haven't had an ECONNRESET since Feb 26 - other than today's (Mar 2) of course, so it's not necessarily daily, but understood.

That's great to hear! Thank you for looking into it. Looking forward to 1.2.2

All of a sudden, I am having constant TPI disconnects:
EnvisaLink:  Error: connect ETIMEDOUT <IP_ADDRESS>:4025
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1157:16) {
errno: -110,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 4025
}

@joshjohanning
Release 1.2.2 with correction to the auto re-connect logic. You should see following line if the auto re-connect is enabled. If not go into the configuration UX and make sure the setting is enabled, which should result in setting autoReconnect=true in the configure.
[05/03/2022, 16:13:24] [Envisalink-Ademco] Successful TPI session established.
[05/03/2022, 16:13:24] [Envisalink-Ademco] Checking for disconnected session every: 30 seconds.
I tested a few times by simply disconnecting my envisalink module network cable and re-connection cable. The logic seem to be working as design.

Awesome! Just installed. Will monitor the logs and see if it works as expected from my side 😄

Seems to work as expected. Closing!

[07/03/2022, 05:55:15] [Envisalink-Ademco] Missing Heartbeat - Time drift:  58.806 . Trying to re-connect session...
[07/03/2022, 05:55:15] [Envisalink-Ademco] EnvisaLink:  Error: read ECONNRESET
at TCP.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}
[07/03/2022, 05:55:20] [Envisalink-Ademco] Starting connection to envisalink module at: <IP_ADDRESS>, port: 4025
[07/03/2022, 05:55:21] [Envisalink-Ademco] Successful TPI session established.
[07/03/2022, 05:55:21] [Envisalink-Ademco] Checking for disconnected session every: 30 seconds.


Cannot import ,  returned non-zero exit status 2

Thanks for this awesome work ,buddy ！
after install , error message popup. how can I fix this problem, appreciate any help
I had mannully install requirements.txt
OS:ubuntu 20.04
python: 3.10
comfyui: had update newest

fix it by :
1 install mercurial :  sudo apt-get install mercurial
2 Clean up Pip Cache: python -m pip cache purge

Do you know what package wanted to install mercurial, or if this is Linux/Ubuntu specific?


feat: support ECS service connect

what

This adds support for ECS Service connect, which is already supported by the provider, see service_connect_configuration block.

why

Extend the module's functionality.

references

There is a PR that partially covers this feature, but unfortunately, it's not active for a while, and there are requested changes to be done: https://github.com/cloudposse/terraform-aws-ecs-alb-service-task/pull/208

/terratest

/terratest


kong added smtp poperty auth type and ssl

What this PR does / why we need it:
User can add the auth type for smtp server in the smtp section of the helm chart. Certain providers like send grid will need a auth type of plain or login to function properly.  Also enable the ssl if needed.
Which issue this PR fixes
NA
Special notes for your reviewer:
Updated the ReadMe file section of SMTP.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] PR is based off the current tip of the next branch and targets next, not master
[ ] New or modified sections of values.yaml are documented in the README.md
[ ] Title of the PR and commit headers start with chart name (e.g. [kong])

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.satwant17 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@satwant17 Please author your commit using your konghq.com email address and then please sign the CLA.


feat: allow to override package manager

This PR introduces a new build option: packageManager which allows to use Yarn or pnpm.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@g-plane what's the motivation for this change? Do you have a need for it?

Personally I don't use npm. Despite it, there may be some environments that npm isn't available in $PATH, rarely, so I added an example about using absolute path to npm, yarn or pnpm to the documentation.


[QUERY] Azure storage async sdk supports http connection pooling ?

Query/Question
Is there a way to enable HTTP connection pooling in azure storage reactor library ? Or is it already enabled ?
Why is this not a Bug or a feature Request?
This is just the question

@anuchandy it's enabled by default, right?

@alzimmermsft can you please follow up?

@shettyh, by default Reactor Netty will use connection pooling, https://projectreactor.io/docs/netty/release/reference/index.html#_connection_pool. In our SDKs you can leverage the APIs on NettyAsyncHttpClientBuilder to further customize the backing Reactor Netty HttpClient.

@alzimmermsft  Thanks for the quick response, wanted to know if all the clients will use same connection pool or not. For example
I will create BlobServiceAsyncClient and then i will make BlobContainerAsyncClient out of it, in this case both will use the same connection pool ?

Also if you can point me to some samples that would be great

@shettyh, correct, using the APIs to get a container client from a service client, and same for getting a blob client from a container client, will share the same underlying HttpClient, therefore the same connection pool. In the codesnippet below all clients will share the same underlying HttpClient:
BlobServiceAsyncClient serviceClient = ...

BlobContainerAsyncClient containerClient = serviceClient.getBlobContainerAsyncClient(containerName);

BlobAsyncClient blobClient = containerClient.getBlobAsyncClient(blobName);

Additionally, from doing some research into the underlying networking layer the default HttpClient instances will share a connection pool. So, using the builder pattern to create additional client should also use the same connection pool even though they will be using different HttpClients.

Thanks @alzimmermsft .
One last clarification, So i assume doing this BlobContainerAsyncClient containerClient = serviceClient.getBlobContainerAsyncClient(containerName); every-time in a function call and having BlobServiceAsyncClient as a instance variable (or singleton) should not have any performance implications right ?

Aside from normal object instantiation, there won't be any performance implication for creating many, many BlobContainerAsyncClients from a BlobServiceAsyncClient. It'll share all heavy objects between the instances and have small overhead with instance specific objects such as the container name, new endpoint, etc.

@alzimmermsft thanks a lot for all the clarifications