docs: Gateway implementation guide for managed vs. unmanaged gateway lifecycles and intra vs extra cluster

What would you like to be added:
This is a request for documentation for implementations which would provide additional guidance and prescription on how to implement Gateway controllers for different kinds of underlying Gateway infrastructure options. Particularly the guide should cover:

Gateways which are "unmanaged" and refer to an existing deployment

Additional Goals:

define clear terminology about the underlying lifecycle management and network location of Gateways

Why this is needed:
This is a direct follow up from a community meeting where the overall topic was discussed, and was a follow up to:

@howardjohn's Document on the subject
A related discussion which suggested some implementation details for how to solve some of the problems in this domain with spec changes: https://github.com/kubernetes-sigs/gateway-api/discussions/877

As per our conversation in zoom today, I'll be taking this one on.
/assign @shaneutt

while the originally wording of this issue may need some updating as it hasn't aged as well as I would like I still think some guidance on implementation of the "unmanaged" Gateway mode (which in my team's implementation we are supporting in addition to the "managed" mode) is valuable for future developers. I'm not sure it's going to be something I do right away, but if nobody else wants to take this one I will intend to do it as soon as is feasible.
/assign

I've gone through a couple drafts that I have reviewed with peers on this one. I've always found my own results wanting. The fact of the matter is that trying to implement for unmanaged mode is difficult, and it's problematic to provide any prescription for others to do the same since it gets deep into implementation-specific territory for each implementor.
I'm also convinced now that the value of writing this guide is pretty limited since we expect that most implementors are going to be able to implement Gateway in a native way, and my team is even considering not releasing the unmanaged way. My main suggestion to anyone reading this who might actually be looking for guidance is to ensure their implementation passes the conformance tests. Since I created this, I am going to close it for now. If anyone is looking to work on this I'll be happy to re-open it.


New API & Integration

@CharlesGillanders have you given any thought to upgrading the library and the HA integration with using the new Alpha public API?
Given that its now possible to register systems that aren't yours with a developer key, I think the HA Integration should take the serial number as a parameter, with the possibility of adding the integration multiple times - rather than how it will behave now retrieving all systems for the account.
i.e. AppId, AppSecret, SysSN for each integration setup.

I haven’t (yet) been able to get the new API working on my own system.  I'm running into roadblocks figuring out my check code.  I can't work on getting the library updated to use the proper public API until that's resolved.

Here's my postman collection which is working.
Just need to add your AppId and AppSecret to the variables
AlphaESS Open API.postman_collection.json.zip
I was getting a 6007 error last week and had to generate a new AppSecret for it to work again.

I have just managed to get my own system registered with the developer portal so I can start looking at this now.  Thanks for the Postman collection - that's incredibly helpful!


use filter by hash when first rendering

I want to the feature like this
It's a convenience when writing the issue.

Thanks!


Bug when passing blank option with in

param :gender, in: %w[male female], blank: false should't be valid if gender = "", but is considering it a valid parameter

sorry, I forgot to include the type String and for this reason the validation was being bypassed. Nonetheless, it would be nice if it could catch this kind of errors.


Bugfix for short-hand rotation

Fix #60

We both missed it. I will also from now on describe my PRs better to make them easier to review. New one is coming in a few minutes :wink:


Typeerror when passing custom class in CreateFromObjectLayerConfig

Version

Phaser Version:
3.60.0-beta.17

Description
Getting a type error when defining an alternative GameObject Type in Phaser.Tilemaps.Tilemap.createFromObjects()
Type 'typeof Image' is not assignable to type 'CreateFromObjectsClassTypeConstructor'.
Example Test Code
map.createFromObjects('background', [
		{ gid: 1, key: 'background1', classType: Phaser.GameObjects.Image },
		{ gid: 2, key: 'background2', classType: Phaser.GameObjects.Image },
	])

If you are getting a TypeError when passing a custom class in the createFromObjectLayer method in Phaser 3, it could be because the class is not being properly mapped to the type in the ObjectLayerConfig object.
The createFromObjectLayer method expects the ObjectLayerConfig object to contain a type property that maps to the class you want to create. For example:
const config: ObjectLayerConfig = {
  type: MyCustomClass,
  ...
};

createFromObjectLayer(config);

If the type property is not correctly mapped to the custom class, you will get a TypeError when trying to create an instance of the class.
To fix this issue, make sure that the type property in the ObjectLayerConfig object is correctly set to the custom class. Here is an example of how you can do this:
class MyCustomClass extends Phaser.GameObjects.Sprite {
  // Class implementation
}

const config: ObjectLayerConfig = {
  type: MyCustomClass,
  ...
};

createFromObjectLayer(config);

I guess this is a TypeScript limitation and these need to be changed back to Function. 😞

CreateFromObjectsClassTypeConstructor
GroupClassTypeConstructor
ParticleClassConstructor

@samme  Yeah I think that might make sense.
Also, bit fed up with the OpenGPT spam issue comments I'm seeing here now.


Default labels not working

I followed the README instructions up to point 8.

But there's no runner with the [self-hosted, linux, codebuild] labels.

I confirm that the following custom label works perfectly on the other hand.

Can you include the workflow and the code you originally used?
If you used the defaults, it might be that the documentation is wrong and you need to remove the linux label from the workflow.

Can you include the workflow and the code you originally used?

test.yml
name: test

on:
  workflow_dispatch:

jobs:
  test:
    runs-on: [self-hosted, linux, codebuild]
    steps:
      - run: echo "Hello World!"

Yeah that documentation got broken with #385. Thanks for letting me know.


USB c hub issue

Hi! Thanks for your efforts, firstly. ddcutil detect is not able to find my monitor connected via a USB c hub? What can I do in this case?

ddcutil should work just fine with USB-C/Thunderbolt hubs and does in my setup. Try to plug the monitors directly into your device. Also make sure ddcutil is correctly setup (first section of the install guide) and make sure DDC/CI is enabled on the monitors (using the on-screen menu).

The extension only works when connect the monitor directly with HDMI and doesn't work when connected via the USB-C/Thunderbolt hub. I guess it's due to the hub not supporting certain "circuits". Anyway, thank you.


Node names in tree sometimes don't match User language

Sometimes I have seen that the node names in the tree don't always match the User language.
E.g. here I am logged in as admin user which is set to English (UK), but the node names are in Danish. But there is another user created which use Danish.
Using Umbraco 6.2.4 and Tea Commerce 3.0.0

However when I browsed to another section and came back it was updated.

Have you guys seen that before?

Not experienced this before. Maybe upgrade to Umbraco 7 and see if its fixed.

It also happpens in a clean Umbraco 7.3.1 with Tea Commerce 3.0.7 .. when you switch user language it doesn't seems to switch the language correct ..


Added missing value to EAGLRenderingAPI enum and a property to get current version of rendering API

added missing value to EAGLRenderingAPI enum
added readonly property in order to be able to get current version of OpenGL  API
code styling changes according to ClangFormat

Hi @jboich, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;


More efficient opam image generation

Switching on Fedora 35 has increased the need to fix two problems:

We build bubblewrap whether we need it or not (there was network access or something going on in F35)
We build OCaml 3 times in the opam image stage - once for each opam binary

This PR adopts https://github.com/avsm/ocaml-dockerfile/pull/85. Headline changes:

opam 2.1 and 2.0 are now built with OCaml 4.13.1, same as opam-dev
The ltsc2022 tag is removed from the Windows images and is now 21H2. This is more consistent with Microsoft's code numbering (I think)
bubblewrap is only built if it's needed and the OS package is never installed if we've built it (which was happening before)

This along with #151 is presently deploying on live.

opam 2.1 and 2.0 are now built with OCaml 4.13.1, same as opam-dev

Why not simply backport the necessary changes to the 2.1 and 2.0 branches? e.g. https://github.com/ocaml/opam/pull/4943 is also a problem for macOS images

We should do both - what we're already doing at the moment in the base image builder in unacceptably inefficient/wasteful! It'd be even worse if we intentionally build the same compiler three times.

Ah, it’s only the compiler, I see. I thought there was more of src_ext shared for some reason

I've used the "make -C src_ext cache-archives" trick to share the archives between the builds, but that's only a cheap trick to reduce network access for instances where the versions of the dependency are the same between branches. Otherwise, it's just the compiler (I've temporarily swallowed compiling dune 3 times, as that's at least a lot faster than compiling OCaml 3 times 🙂)

Fix for the OCaml 4.14 failure https://github.com/ocurrent/docker-base-images/pull/156/commits/d81e7916a2ca3efe00d8f7a9e3c42f7e75f3fafd


enableDefocus not working

Hi
I went to disable defouces  but not working.
const markers = [
{
id: 1,
city: 'Singapore',
color: 'red',
coordinates: [1.3521, 103.8198],
value: 50,
},
];
<ReactGlobe
markers={markers}
focusOptions={{enableDefocus: false}}
globeOptions={{
texture:
'https://raw.githubusercontent.com/chrisrzhou/react-globe/main/textures/globe_dark.jpg',
}}
/>

Hey I'll be taking a look at the repo and going over bugs and improving some stability in v5.  Will probably take 1-2 weeks to get everything updated and in place.  Will address this in the release!

v5.0.0 is just released and this bug is addressed.  You can test the behavior by checking the second example in this page: https://react-globe.netlify.app/usage/focus where enableDefocus is set to false.
v5.0.0 introduces some breaking changes, so if you intend to upgrade to it, please refer to the changelog.md or Github release notes for details.  In general, the props are simplified/flatter and renamed.


De-duplicating fragments in document

Per #27, de-duplicating fragments as we're iterating over them to check for fragment name uniqueness.
This will result in the expression
gql`query { ...SomeFragment } ${SomeFragment} ${SomeFragment}`

only emitting one of the fragment definitions
gql`query { ...SomeFragment } fragment SomeFragment on SomeResource { someField }`

Looks like this is ready to merge. Can you confirm @stubailo ?

ping @helfer @stubailo if there are changes that i need to make here

@jnwng
Sorry it took so long to circle back on this. Quick question before I merge: how would this work with the newly added #import preprocess statements? So, for example, if you have the following:
#import "file1.graphql"
#import "file2.graphql"
query {
  ...someFragment
}

// file1.graphql
fragment someFragment on RootQuery {
  # ...
}

// file2.graphql
fragment someFragment on RootQuery {
  #...
}

It seems to me that in this case, no de-duplication would happen. I think that's probably fine but I'm wondering if you think that should be the intended behavior.

We could just merge a version that only works with the gql tag right?

Sure, I think that's fine - I was just wondering if the graphql-tag/loader direction had been considered. I think we can merge this and maybe figure out some equivalent thing for the loader later if needed.

Released as 1.2.3.

Does it work only for Fragments? Seems that inputs can use same behaviour.


broadcast extra '/' cause change in the base url

Slash in the first of this line cause instead of the url like to https://example.com/trx-fullnode/wallet/broadcasttransaction convert to https://example.com/wallet/broadcasttransaction
https://github.com/andelf/tronpy/blob/9e869fb508c3f77b432948cc56cd66985375843d/tronpy/tron.py#L869
If we remove the first '/' this works correctly.

Sorry for keep asking if this is already merged, shouldn't be available in PyPi already?


Decide approach for updating dependencies and resolving CVEs

Resolved by:

https://github.com/gchq/sleeper/issues/937


Missing VM information from .../vcenter/vm/{vm}

I noticed recently while writing a CMDB integration, that {cluster} is not included in the information retrieved from the above endpoint. {resource_pool} is not included as well, which could be a way to work around the issue.
Also, (since we're talking missing information), while the above endpoint shows datastore, it does not show datastore cluster, which would really be handy to have, as the VM can move at any given point in time.

Hi @dkalaluhi, thanks for letting me know about this. I'm going to log this internally. I appreciate the feedback and definitely welcome your continued feedback. Let me know about anything you run into. Thanks!

{
"name": "com.vmware.vapi.rest.httpNotFound",
"localizableMessages": [
{
"defaultMessage": "Not found.",
"id": "com.vmware.vapi.rest.httpNotFound"
}
],
"majorErrorCode": 404
}
any idea ???

@houcinedz A 404 typically means that the resource you are looking for is not found. I would need more information about the call you made to help with diagnosing why your request failed.

i think i can't use REST API with vSphere 6.0
Le mar. 9 avr. 2019 à 16:02, J.R. Garcia<EMAIL_ADDRESS>a
écrit :

@houcinedz https://github.com/houcinedz A 404 typically means that the
resource you are looking for is not found. I would need more information
about the call you made to help with diagnosing why your request failed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/vmware/vsphere-automation-sdk-rest/issues/14#issuecomment-481265027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYf8NwKDLHc4JrNwxiRK6bogRl0hQBuqks5vfJ1jgaJpZM4QAyz2
.

@houcinedz You can use one of the management SDKs that use the SOAP-based APIs. There is a Java version available as well as pyvmomi for Python, rbvmomi for Ruby, and govmomi for Go.

@houcinedz If you are having issues with pyvmomi, please report them on their issues or request an invite to the VMware {code} Slack team and join the #pyvmomi channel.

I wish vm folder name was also included in the vm data coming back from rest api
rest/vcenter/vm/vm-1914/guest/folder
rest/vcenter/vm/vm-1914/folder


Style guidelines

In case the project would be deploy under ebi.ac.uk I will recommend reviewing some of the guidelines.
http://www.ebi.ac.uk/web/style is specially useful the part related with patters http://www.ebi.ac.uk/web/style/patterns icons together with the resources http://www.ebi.ac.uk/web_guidelines/images/icons/

perfect, thanks!


Fix examples links in HELP.md

At https://github.com/brycecurtis/dfs-trucreds-hackathon/blob/main/HELP.md#digital-trust-use-cases, the "Internal Examples" and "External Examples" links are not valid and need fixing.

Works for me.


How to skip steps based on the specific value?

I want to skip 2nd and 3rd step if user enter a number instead of URL.

I also want this functionality. Did you found a solution?


test-branch/execute-job/quoted-authorization/54bd01a6-14c4-4f59-882f-c06b9987358e

PR for testing a466bdc73d51b78e4e4311c34c0801963c282934

/canonical/self-hosted-runners/run-workflows a466bdc73d51b78e4e4311c34c0801963c282934


The PayPal client is installed, but now you can only call the web payment in the app

The PayPal client is installed, but now you can only call the web payment in the app.
Can we call the client on the mobile phone with PayPal client, and then call the web page without the client.
This makes the user feel more optimized.

Hey @kebenxiaoming can you provide additional details when you say:

but now you can only call the web payment in the app

Are you talking about authentication with the Checkout SDK going through a web browser as opposed to the PayPal Android app or something else?

@CodyEngel Yes, is it possible to log in and pay only through a web browser. Can we call the client on the mobile phone with PayPal client, and then call the web browser without the client?

@kebenxiaoming login without a browser switch is not something we have plans of supporting as it would deviate from best practices for OAuth 2.0.

@CodyEngel Thank you for your reply.


Available statuses are not reloaded after status change

'Workflow - Status transitions' configuration doesn't allow to change from status 'In Progress' to status 'Resolved'. Status 'Resolved' only available from status 'Testing'.
After status changed from 'In Progress' to 'Testing' status 'Resolved' still unavailable.
Refreshing page shows correct statuses for choice.

Hello @TrumanRu
Last update fixed this enhancement. After the AJAX call, we use the returned page value to update the status dropdown list ( https://github.com/Ilogeek/redmine_issue_dynamic_edit/commit/efe0d790651fddc1e8fafdd5bb3e7844176e223e#diff-96bb972d1dd0a7bda840ba8234dd84be )
Don't hesitate to update this issue if you find any problem


feat: 🎸 add useStartTypings hook

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


refactor(WEG-131): Change appearance of location switch to impr. ux

People were confused about the location switch and didn't know when it was on or off.
This is the new look of the location switch:
https://user-images.githubusercontent.com/2759340/202417669-27da7fdf-2fce-46ab-b7a6-1e9bee115c52.mov

Thx for the review!

I am not sure whether this change is necessary. If we need to change the visual language of the whole page, the change to rounded corners may work. But with the current CI requirements, I am hesitant to deviate from the defined toggle style. Rounded corners seem like a pretty strong contrast to the otherwise sharp edges.

These are the results of the user tests. Many people were apparently confused with this UI element. I think that switches are most commonly round and this appearance is more recognizable for most. I don't think however that this means we need to change the whole UI language. UX has priority over UI-language consistency. But we could discuss that again it you'd like. I'd be curious about @edgalindo's opinion on that too. How strict should we be about following Berlin's guide if the UX tests show some difficulties with it?

I think that switches are most commonly round and this appearance is more recognizable for most

Totally agree with that!
I am under the assumption that the CI guide (and the toggle) has been tested thoroughly for UX, perhaps invalidating our rather small-scoped tests. But then again, this is an assumption, so I actually don't have much of an argument here, and personally also agree that the new toggle is clearer.

I am under the assumption that the CI guide (and the toggle) has been tested thoroughly for UX

I'm not sure about that. The company that developed the CI-guidelines isn't specialized in UX and I would bet that thorough UX tests have been done. Or are you aware of some tests and where can I find more about it?

Or are you aware of some tests and where can I find more about it?

No, absolutely not. That's why I think my initial concern is not really valid. From my side this can be merged.

:tada: This PR is included in version 1.3.0-rc.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


small room fixes

wont be merging this one myself since theres more than one(1) change and i dont want everything to crumble after doing so so uh hi dps

haha oops theres more stuff so will be making another pull req later


Sharing buttons

Buttons to share on Facebook, Twitter, LinkedIn, and Hacker News, would be useful!

Currently looking at https://sharingbuttons.io/ for basic sharing buttons. These buttons won't require registering with Facebook, LinkedIn, ect.

Currently looking at https://sharingbuttons.io/ for basic sharing buttons. These buttons won't require registering with Facebook, LinkedIn, ect.


os/exec/exec.go: CombinedOutput()  segmentation fault (core dumped)

What version of Go are you using (go version)?
linux   go1.12.7

$ go version

Does this issue reproduce with the latest release?
What operating system and processor architecture are you using (go env)?
debian in docker
go env Output
$ go env

What did you do?

What did you expect to see?
no segment fault
What did you see instead?

As far as I can see your screenshot, the crashed program is mpclient not Go.

I find "ProcessState" Field. I add  fmt.Printf("state.....", state)  to wait() function.As shown:

Then I saw the output as shown below：

Yes, it is state of child process. So the crashed program is mpclient.

@drwpeng - please let us know if the above diagnosis is incorrect. You can also run the "./mpclient " manually to check if it generates a seg fault. As far as I can see, the Go program runs fine because it prints other lines properly after the seg fault.
And it is preferred to directly have the text output rather than a screenshot. In this case, I could not copy paste your mpclient command just because it was an image. A minor inconvenience, but it could be bigger if I had to use any of the text to reproduce some other issue.

Yes, it is a problem with mpclient. Thank you for your help.


Modified SDE tool for maglev run

Can you cherry-pick the SDE update change as it is?
And then do your changes on top of it?

Can you cherry-pick the SDE update change as it is?
And then do your changes on top of it?

Ok. Will update that

Updated after cherry-picking

Closing this PR as another PR with proper changes is created


Fix server request in UI

The web ui currently only sends the link from textbox. The api definition from the link should be fetched first and then send to the server.

@fmueller Yep what I will do is fetching the definition on the server side to avoid CORS problems by trying to fetch directly from the browser.


Auction implementation

add auction phase before preflop to have player bid for power to see river card.
tie handling: all winners get to see river card.

Sorry, this was meant to be pushed to my fork.


How diff for miner

I try to use your ether-proxy but i don't know how much  for my rigs.
I using rx470: 164MH/s.
Thanks!
P/s: i don't know how contact you so i post here. Sorry about that.


unsafe: allow Offsetof for array entries

It would be nice if unsafe.Offsetof could handle array entries as well as struct fields.
package main

import "unsafe"

type T struct {
	a int
	b [3]int
}

func main() {
	println(unsafe.Offsetof(T{}.b))
	println(unsafe.Offsetof(T{}.b[1]))
}

At the second line of main, I get an invalid expression error:
go/tmp1.go:12: invalid expression unsafe.Offsetof((T literal).b[1])

@griesemer @mdempsky

@edressel

See #16727

Note that currently Offsetof(a.b.c) tells the offset of c from a.b, not from a.  So to be consistent, in your example, Offsetof(T{}.b[1]) would be 4 (the offset from T{}.b), not 8 (the offset from T{}).

A minor language change, would be backward-compatible.

Another tricky bit: should we require the index to be constant?  If not, then there's some evaluation that needs to happen inside the Offsetof(), which is contrary to what Offsetof does now.
@mdempsky : I didn't realize that it only applied to the last field.  That's surprising.

So if Offsetof only works on the last offset, then this proposal isn't useful.
Offsetof(a.b.c[2]) would be the same as 2 * Sizeof(a.b.c[0]).
Or maybe it could do the last two offsets if the last one was an index, so at least a.b[2] would work.  But this is getting weird, I'm just as inclined to drop it.

FWIW, I've brainstormed before about extending Offsetof to take two parameters like C++'s offsetof operator.  Then you could write Offsetof(a, b.c) vs Offsetof(a.b, c) to distinguish intent.
It would be a bit awkward though because then "b" in Offsetof(a, b) doesn't actually refer to a free variable b.  Not a problem per se, but some tools might need to be aware of that.
It also wouldn't work for array indexes since Offsetof(a, [1]) isn't currently valid syntax, but at least Offsetof(T{}, b[1]) would be.


Add CPU time to metrics for segment scanning.

This is an alternative to #1298
This PR only reports CPU usage during the compute heavy portions of the query runner by wrapping the yielder calls (or at least is supposed to) and only reports metrics once per query including having a query ID.
The prior PR (#1298) reported cpu usage as part of the metrics emitting executor service by wrapping the runnables and callables, and didn't have a good way to get context for why the CPU was being used.
Overall I think this PR is a better way to go because it has better reporting over the context of the CPU usage.

:+1:

:+1:

@drcrallen are we intentionally not making ServerManager like updates for the broker so that broker also report same metric?

@himanshug Not in this PR. The appropriate runner could be wrapped at the broker level using the same approach but I purposefully left it out of this PR to limit the scope.

LGTM


solve

iam solution this error because in Apple Pay not support in Egypt test in Saudi Arabia and ensuring add one cart at lest in apple wallet , and Make sure there is at least one card in apple wallet

Hi @El-sayed-mahmoud, what's the error/issue that you are experiencing?


Transform doesn't work with type assertion in params

For a function with a type asserted parameters, oxc-transform reporting an error incorrectly.
Given this code:
interface T0 {}

export function test(_ = {} as T0): void {}

Current behaviour
Getting an error:
  x TS9011: Parameter must have an explicit type annotation with
  | --isolatedDeclarations.
   ,-[test.ts:3:32]
 2 |
 3 | export function test(_ = {} as T0): void {}
   :                                ^^
   `----

Expected behaviour
According to TypeScript, this is valid, and generate dts bellow in Isolated Declaration:
export interface T0 {
}
export declare function test(_?: T0): void;

Playground link

Thanks for the feedback. This is a false positive, the result is correct


[web_wallet]  Failed to lineman build

>> Tasks directory "tasks" not found.

Running "clean:dist" (clean) task

Running "clean:bower" (clean) task

Running "common" task

Running "bower:install" (bower) task
Fatal error: Unable to find suitable version for angular

npm WARN package.json<EMAIL_ADDRESS>No repository field.
npm WARN prefer global<EMAIL_ADDRESS>should be installed with -g

Gona to ok after update angular resolution to "~1.3.x"

TODO: update the document

I will try to build a fresh wallet tomorrow and reproduce this.

@AlexChien I've fixed this, will give a commit in seconds


Safe list access

When accessing list by index (ie. "item[3]"), if the index does not exists, it throws a java.lang.IndexOutOfBoundsException, instead of the expected behavior of returning "null".
A simple try/catch at line 103 of GetAttributeExpression should work.

I like this idea but only if it still throws an error if the user sets the "strictVariables" setting. In that case it should actually wrap the IndexOutOfBoundsException with a PebbleException that contains the line number.
We would also want to implement the same for accessing lists by index (a few lines down in the same GetAttributeExpression class).

Would you like to submit a pull request for this one?


OpenAPI spec

Write a swagger file for our API.

Done. Unfortunately I pushed it into master directly instead of a feature branch, so - no merge request,


packages tsconfig files shouldn't include compilerOptions and exclude fields

Since the packages are now transpiled with tsup,  from my understanding their tsconfig.json files shouldn't include compilerOptions and exclude fields as those are managed by tsup.

From the documentation only
because compilerOptions are required in the packages, it's where most settings are located


BDD-style macros

They are not on the roadmap, but they are important. https://github.com/doctest/doctest/blob/master/doc/markdown/testcases.md#bdd-style-test-cases
The tests written in BDD are a lot more readable. https://github.com/zhihaoy/nontype_functional/blob/main/tests/function_ref/test_return_reference.cpp

Based on what I read in the Catch2 and doctest documentations, you can easily do this with sections:
TEST_CASE("BDD") {
    SECTION("given: a vector") {
        std::vector<int> v;

        SECTION("when: resized") {
            v.resize(5u);

            SECTION("then: size changed") {
                CHECK(v.size() == 4u); // oops, wrong value for testing
            }
        }
    }
}

And if you want the extra convenience of dedicated macros:
#define SCENARIO(NAME, ...) TEST_CASE("scenario: " NAME, __VA_ARGS__)
#define GIVEN(WHAT) SECTION("given: " WHAT)
#define WHEN(WHAT) SECTION("when: " WHAT)
#define AND_WHEN(WHAT) SECTION("and when: " WHAT)
#define THEN(WHAT) SECTION("then: " WHAT)
#define AND_THEN(WHAT) SECTION("and then: " WHAT)

SCENARIO("BDD") {
    GIVEN("a vector") {
        std::vector<int> v;

        WHEN("resized") {
            v.resize(5u);

            THEN("size changed") {
                CHECK(v.size() == 4u); // oops, wrong value for testing
            }
        }
    }
}

Although the dedicated macros look nice, they may provide a false sense of security. There is no check done in case you forget to write a GIVEN(), a  WHEN(), or a  THEN(), or if they are specified in the wrong order. Both Catch2 and doctest have the same issue. It might be possible to implement such checks at compile-time (run-time would be easy), but this would be a fair bit of work. I won't feel comfortable adding them to snitch until such checks are in place.
There's also some more more minor issues:

SCENARIO() would need separate macros to support template test case, etc., which means more macros to maintain.
GIVEN, WHEN, and THEN are fairly common words; I would be a bit wary of adding them to the global namespace. The prefixed version (SNITCH_GIVEN(), etc.) would be far less readable, which defeats the purpose.

Given that the exact same behavior can be obtained with plain sections, at the expense of typing a few extra characters, I'm not sure this is worth it. My recommendation would be to stick to simple sections, as in the first example, and arrange then in a BDD-style if you like.


[SPARK-16664][SQL] Fix persist call on Data frames with more than 200…

What changes were proposed in this pull request?
Cherry-pick from d1d5069aa3744d46abd3889abab5f15e9067382a and fix the test case
How was this patch tested?
Test updated

Test build #63008 has started for PR 14404 at commit 555b67f.

Can you fix the title?

Test build #63008 has finished for PR 14404 at commit 555b67f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

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

Great, thank you @breakdawn . It looks good as a re-submit of the original PR, and passes, so I'm merging.

You can close this PR now; we can't auto-close it and neither can the bot in this situation.


HSIEO-5499: Package Manager Class Renaming (New)

Renaming according to the proposal sheet:
Copy of zpm_to_ipm_rename (version 2).xlsx

But why is this PR here? I'm glad you are asking!
This is a PR with all the comments duplicated from https://github.com/Beiming-Zhang/zpm/pull/3
Why is the above PR merged before resolving any of its issues?
I was trying a variety of ways to fix the Add+Delete != Rename issue, during which I downloaded github desktop to preview the changes I made, to see whether they are recognized as A+D or R, before pushing.
Then I saw a friendly button:

...and I clicked it, which pushed the commits before I noticed that it's on master branch and threw my laptop out of the window to stop it.
So all changes in the 211 files went into master, and that PR auto closed due to the merge.
I reverted changes in the master branch, but cannot re-open that PR as that has been marked merged.
Therefore, I have to re-open this new PR, from the same branch to master, and copying comments here. But still, all the work are preserved here.

Cannot find a way to enable rename in a single PR (can discuss why later)
Ready for another round of review

Put back the DEFAULTGLOBAL parameter.
Update the spreadsheet with decisions made on any additional class renames/moving classes to other repos
Fix the rename/move items flagged as TODO

@Beiming-Zhang Have taken a look and all issues seem to be addressed. Great work!


[Bug]: Laravel: Website Sub-Page returns nginx 404

Description
Deployed a Laravel App using the docs from https://coolify.io/docs/frameworks/laravel which works for the index page.
But for some reason every sub page like /test returns a 404 from nginx - not handled by Laravel.
Minimal Reproduction (if possible, example repository)
Using this simple example:
Route::get('/', function () {
    return view('welcome');
});

Route::get('/test', function () {
    return "test123";
});

Exception or Error
No response
Version
v4.0.0-beta.146

Just updated the docs. You need one more env variable and it will work.
https://coolify.io/docs/frameworks/laravel


[PostCSS] Support glob property in dir-dependency messages

Changes
Following on from #3309, this pull request updates @snowpack/plugin-postcss to add support for the glob property of dir-dependency messages registered by PostCSS plugins. Relevant documentation: https://github.com/postcss/postcss/blob/main/docs/guidelines/runner.md#3-dependencies
Testing
No tests added, discussed in #3309.
Docs
No docs added as this is not a user-facing change. The messages are created by PostCSS plugins and handled internally by @snowpack/plugin-postcss

Brilliant, thanks again @drwpow!


feat: networkx datasets gml and graphml

Description
Introduces feature described in https://github.com/quantumblacklabs/kedro/issues/828
Development notes
Follow up from https://github.com/quantumblacklabs/kedro/pull/830 with comments processed, based on the lastest development branch. Thanks @ignacioparicio for reviewing!
Omitted GPickleDataSet as GPickle is deprecated in NetworkX and will be removed in the third version (ref).
Included GraphML in addition to GML. Some tools prefer GraphML as it's able to perfectly preserve internal property maps (ref).

Checklist

[X] Read the contributing guidelines
[X] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[X] Updated the documentation to reflect the code changes
[X] Added a description of this change and added my name to the list of supporting contributions in the RELEASE.md file
[X] Added tests to cover my changes

Notice

[X] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.

I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorised to submit this contribution on behalf of the original creator(s) or their licensees.

I certify that the use of this contribution as authorised by the Apache 2.0 license does not violate the intellectual property rights of anyone else.

Thanks for the reviews @AntonyMilneQB and @MerelTheisenQB ! I've updated the branch to incorporate the suggestions.


ZCLI theme and apps uses same port

Expectations
I can run zcli apps:server and zcli theme:preview concurrently for both changing a theme and an app that runs in Agent environment.
useful for integrations (e.g. custom objects) that run on both the Help Center and a sidebar app for Agents.
Reality
I get a port collision error
zcli themes:preview

Uploading theme... Ok
node:events:368
      throw er; // Unhandled ‘error’ event
      ^
Error: listen EADDRINUSE: address already in use <IP_ADDRESS>:4567
    at Server.setupListenHandle [as _listen2] (node:net:1334:16)
    at listenInCluster (node:net:1382:12)
    at GetAddrInfoReqWrap.doListen [as callback] (node:net:1520:7)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:73:8)
Emitted ‘error’ event on WebSocketServer instance at:
    at Server.emit (node:events:390:28)
    at emitErrorNT (node:net:1361:8)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  code: ‘EADDRINUSE’,
  errno: -48,
  syscall: ‘listen’,
  address: ‘<IP_ADDRESS>’,
  port: 4567
}

Steps to Reproduce
run zcli apps:server and zcli theme:preview on an app and theme at the same time

Hi @verschoren,
Both commands accept a --port flag which should allow for starting them on different ports and avoid the collision error.


Bump bindgen version

Due to https://github.com/rust-lang/cargo/issues/5237 I have a conflict between versions of bindgen used in different crate's build scripts. In order to work around this for the time being, I have increased the version of bindgen used in lttng-ust-generate. No code changes are required. Just a dependency version change.

Is there anything preventing this PR from getting merged @bobtwinkles?

I didn't know anyone was actually using this thing and missed the notification 3 years ago. This change looks OK, though the bindgen version is also now 3 years out of date =P. I'll merge it and maybe find some time to wire this up to profiling/tracing at some point.

Would it be possible to push a new crate minor revision with the update dependencies?


Refactor sign/verify message

Code refactor: drop some wrappers, split methods to different files, extract methods
Do signing/verification parallel
benchstat compare with master:

I think api-go: can be replaced with a signature: in the commit header, it should designate a component in this repo (or omitted). Also I believe it should be Verify parts IN parallel.

fixed


Issue compiling on M1 Pro MacBook.

Bug Report
Hello! I'm having an issue compiling a basic hello world on my computer.
The code I am using
puts "hello world"

I run it with crystal run test.cr
and I get the following error:
Undefined symbols for architecture arm64:
  "_iconv", referenced from:
      _*Crystal::Iconv#convert<Pointer(Pointer(UInt8)), Pointer(UInt64), Pointer(Pointer(UInt8)), Pointer(UInt64)>:UInt64 in C-rystal5858I-conv.o
  "_iconv_close", referenced from:
      _*Crystal::Iconv#close:Nil in C-rystal5858I-conv.o
  "_iconv_open", referenced from:
      _*Crystal::Iconv#initialize<String, String, (Symbol | Nil)>:Nil in C-rystal5858I-conv.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Error: execution of command failed with code: 1: `cc "${@}" -o /Users/arc/.cache/crystal/crystal-run-test.tmp  -rdynamic -L/opt/crystal/embedded/lib -lpcre -lgc -L/opt/homebrew/Cellar/libevent/2.1.12/lib -levent -liconv`

I am using the crystal installed from the .pkg file. Here is my crystal -v:
Crystal 1.4.1 [b7377c041] (2022-04-22)

LLVM: 10.0.0
Default target: aarch64-apple-darwin

And here is uname -a if it helps:
Darwin Caryophyllus.local 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:46:32 PDT 2022; root:xnu-8020.101.4~15/RELEASE_ARM64_T6000 arm64

Update:
adding --link-flags -L/usr/lib makes it work???

Duplicate of https://github.com/crystal-lang/crystal/issues/10653?

Seems to be, but this shouldn't be something I have to fix. Also #10653 was closed

It seems odd that /usr/lib is apparently not available as default path.
Can you please share the output of crystal env?
And the manpage for your linker?

This is still an issue as of Crystal 1.6.1. Running on a M1 Max MacBook Pro.

I concur.  This issue exists on my MBP+M1.
507 rmills@rmillsm1:~ $ sw_vers
ProductName:		macOS
ProductVersion:		13.2.1
BuildVersion:		22D68
508 rmills@rmillsm1:~ $

My investigation is incomplete.  Here's what I know:
With macOS BigSur, Monterey and Ventura (macOS 11, 12,13) the file /usr/lib/libiconv.2.dylib is not installed.  This is in the release notes:  https://developer.apple.com/documentation/macos-release-notes/macos-big-sur-11_0_1-release-notes search for 62986286
There is magic to enable dlopen() to access /usr/lib/libiconv.2.dylib although the file is not in the file system.  crystal has been correctly compiled to use that library, yet it fails to do so at run-time.
516 rmills@rmillsm1:/opt $ otool -L /opt/crystal/embedded/bin/crystal
/opt/crystal/embedded/bin/crystal (architecture x86_64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
/opt/crystal/embedded/bin/crystal (architecture arm64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
517 rmills@rmillsm1:/opt $

crystal crashes at runtime:
519 rmills@rmillsm1:/opt $ cat ~/gnu/crystal/hello/src/hello.cr
# TODO: Write documentation for `Hello`
module Hello
  VERSION = "0.1.0"

  puts "Hello World!"
end
520 rmills@rmillsm1:/opt $ crystal run ~/gnu/crystal/hello/src/hello.cr
Undefined symbols for architecture arm64:
  "_iconv", referenced from:
      _*Crystal::Iconv#convert<Pointer(Pointer(UInt8)), Pointer(UInt64), Pointer(Pointer(UInt8)), Pointer(UInt64)>:UInt64 in C-rystal5858I-conv.o
  "_iconv_close", referenced from:

I will continue to investigate.
Here is a confusing red-herring.  Programs access libiconv.2.dylib differently on Apple and GNU.  When you call _iconv with GNU (/usr/local/lib/libiconv.2.dylib) uses entry _libiconv_XXX.  Apple uses entry _iconv_XXX.  Apple support for my 10 year old MacMini terminated with Calalina (10.15) and has both /usr/lib/libiconv.2.dylib (provided by Apple) and /usr/local/lib/libiconv.2.dylib (which I built from source),
530 rmills@rmillsmm-local:~/gnu/libiconv/libiconv-1.15 $ nm -g /usr/local/lib/libiconv.2.dylib  | grep conv
00000000000e4090 D __libiconv_version
00000000000052e0 T _iconv_canonicalize
0000000000004b20 T _libiconv
0000000000004b50 T _libiconv_close
00000000000036a0 T _libiconv_open
0000000000004b60 T _libiconv_open_into
0000000000017410 T _libiconv_set_relocation_prefix
0000000000004fd0 T _libiconvctl
00000000000050e0 T _libiconvlist
531 rmills@rmillsmm-local:~/gnu/libiconv/libiconv-1.15 $ nm -g /usr/lib/libiconv.2.dylib | grep conv
00000000000f2710 D __libiconv_version
0000000000002390 T _iconv
00000000000026ab T _iconv_canonicalize
00000000000023b2 T _iconv_close
0000000000001095 T _iconv_open
00000000000023bf T _iconvctl
00000000000024b4 T _iconvlist
0000000000013fac T _libiconv_set_relocation_prefix
532 rmills@rmillsmm-local:~/gnu/libiconv/libiconv-1.15 $

Apple's libiconv magic in their SDK works.  I can compile and link the program test-to-wchar.c from libiconv-1.17 to use the fictional /usr/lib/libiconv.2.dylib
Conclusion:

crystal is linked correctly.
/opt/local/lib/libxml2.2.dylib has been incorrectly linked and searching for _libiconv

680 rmills@rmillsm1:/opt $ /opt/crystal/embedded/bin/crystal run ~/gnu/crystal/hello/src/hello.cr
dyld[37150]: Symbol not found: _libiconv
  Referenced from: <9A70615A-9B35-3C97-8E8D-9E596C8A51CE> /opt/local/lib/libxml2.2.dylib
  Expected in:     <E6B7DE43-596F-32E8-8EDD-2CA0ED0DFD3D> /usr/lib/libiconv.2.dylib
Abort trap: 6
681 rmills@rmillsm1:/opt $

Here's my investigation:
665 rmills@rmillsm1:~/temp $ cc     test-to-wchar.c   -o test-to-wchar -I/Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/usr/include /Library/Developer/CommandLineTools/SDKs/MacOSX13.1.sdk/usr/lib/libiconv.tbd
666 rmills@rmillsm1:~/temp $ ./test-to-wchar
667 rmills@rmillsm1:~/temp $ otool -L test-to-wchar
test-to-wchar:
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
668 rmills@rmillsm1:~/temp $ nm test-to-wchar | grep iconv
                 U _iconv
                 U _iconv_open
669 rmills@rmillsm1:~/temp $

crystal and test-to-wchar have been linked in the same way:
678 rmills@rmillsm1:/opt $ otool -L /opt/crystal/embedded/bin/crystal
/opt/crystal/embedded/bin/crystal (architecture x86_64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
/opt/crystal/embedded/bin/crystal (architecture arm64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
679 rmills@rmillsm1:/opt $ nm  /opt/crystal/embedded/bin/crystal | grep iconv
                 U _iconv
                 U _iconv_close
                 U _iconv_open
680 rmills@rmillsm1:/opt $

I made two tiny changes to the 1.17 code:
672 rmills@rmillsm1:~/gnu/libiconv-1.17 $ diff ./tests/test-to-wchar.c ~/temp/test-to-wchar.c
18c18
< #include "config.h"
---
> /* #include "config.h" */
43c43
<                       (ICONV_CONST char **) &inptr, &inbytesleft,
---
>                       /*(ICONV_CONST char **)*/ &inptr, &inbytesleft,
673 rmills@rmillsm1:~/gnu/libiconv-1.17 $

How to fix this?  I don't know.  I will be motivated to continue this investigation with encouragement from Team Chrystal.  Specifically, I would like to discuss this bash script:
501 rmills@rmillsm1:~ $ cat /opt/crystal/bin/crystal
#!/usr/bin/env bash
...
realpath() {
    canonicalize_path "$(resolve_symlinks "$1")"
}
...
SCRIPT_PATH="$(dirname "$(realpath "$0" || echo $0)")"
INSTALL_DIR="$(realpath "$SCRIPT_PATH/..")"
EMBEDDED_CRYSTAL_PATH=$("$INSTALL_DIR/embedded/bin/crystal" env CRYSTAL_PATH)
export CRYSTAL_PATH="${CRYSTAL_PATH:-"$EMBEDDED_CRYSTAL_PATH:$INSTALL_DIR/src"}"
export CRYSTAL_LIBRARY_PATH="${CRYSTAL_LIBRARY_PATH:+$CRYSTAL_LIBRARY_PATH:}$INSTALL_DIR/embedded/lib"
"$INSTALL_DIR/embedded/bin/crystal" "$@"
502 rmills@rmillsm1:~ $

Solved!
From my analysis above, I believe crystal is correctly built and the executable is experiencing a dynamic library loading crisis (probably involving libiconv.2.dylib)
I have this working by installing the pkg from github.  I used:
https://github.com/crystal-lang/crystal/releases/download/1.7.2/crystal-1.7.2-1.universal.pkg
Before installing I did the following:

Clean out sudo rm -rf /opt/*
Removed all references to /opt in my bash profile script (~/.profile)
Simplified the libraries in /usr/local/lib and /usr/local/include.  I have:

596 rmills@rmillsm1:~/gnu/crystal $ ls -l /usr/local/lib/*.dylib | grep -v ^l
-rwxr-xr-x  1 root  wheel    34271 14 Feb 13:07 /usr/local/lib/libcharset.1.dylib
-rwxr-xr-x  1 root  wheel  2948312 16 Feb 16:59 /usr/local/lib/libexiv<IP_ADDRESS>.dylib
-rwxr-xr-x  1 root  wheel  3128792 16 Feb 09:22 /usr/local/lib/libexiv<IP_ADDRESS>.9.dylib
-rwxr-xr-x  1 root  wheel   189197 16 Feb 16:57 /usr/local/lib/libexpat.1.8.10.dylib
-rwxr-xr-x  1 root  wheel   106025 16 Feb 16:56 /usr/local/lib/libz.1.2.13.dylib
597 rmills@rmillsm1:~/gnu/crystal $

Crystal (and supporting artefacts) are in /opt/crystal.  The executable is in /opt/crystal/embedded/bin/crystal:
510 rmills@rmillsm1:/opt $ ls -l $(which crystal)
lrwxr-xr-x  1 root  wheel  24 16 Feb 17:30 /usr/local/bin/crystal -> /opt/crystal/bin/crystal
511 rmills@rmillsm1:/opt $ otool -L /opt/crystal/embedded/bin/crystal
/opt/crystal/embedded/bin/crystal (architecture x86_64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
/opt/crystal/embedded/bin/crystal (architecture arm64):
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1311.100.3)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.23.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1858.112.0)
512 rmills@rmillsm1:/opt $

This will not run crystal play:
503 rmills@rmillsm1:~ $ crystal play
Listening on http://<IP_ADDRESS>:8080
Undefined symbols for architecture arm64:
  "_ERR_load_crypto_strings", referenced from:
      ___crystal_main in _main.o
  "_OPENSSL_add_all_algorithms_noconf", referenced from:
      ___crystal_main in _main.o

So, I installed brew using the instructions here:  https://brew.sh  Then installed crystal using brew:
$ 507 rmills@rmillsm1:~ $ brew list
==> Formulae
bdw-gc		ca-certificates	crystal		gmp		libevent	libyaml		llvm@14		<EMAIL_ADDRESS>openssl@3	pcre		pkg-config

508 rmills@rmillsm1:~ $ brew play
Listening on http://<IP_ADDRESS>:8080

.... happiness in the browser http://localhost:8080 ...
^C
509 rmills@rmillsm1:~ $

I can successfully run $ crystal play on both /usr/local/bin/crystal on and /opt/homebrew/bin/crystal.
510 rmills@rmillsm1:/opt $ finder crystal $L | grep -v ^d | grep -v ^l
-rwxr-xr-x  1 rmills  admin  13073808 17 Feb 07:39 ./homebrew/Cellar/crystal/1.7.2/libexec/crystal  <--- from brew
-rwxr-xr-x  1 root  wheel  136228538 23 Jan 20:18 ./crystal/embedded/bin/crystal  <--- from universal.pkg
511 rmills@rmillsm1:/opt $ otool -L homebrew/Cellar/crystal/1.7.2/libexec/crystal
homebrew/Cellar/crystal/1.7.2/libexec/crystal:
<EMAIL_ADDRESS>(compatibility version 1.0.0, current version 14.0.6)
	/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 1300.32.0)
	/opt/homebrew/opt/pcre/lib/libpcre.1.dylib (compatibility version 4.0.0, current version 4.13.0)
	/opt/homebrew/opt/bdw-gc/lib/libgc.1.dylib (compatibility version 7.0.0, current version 7.1.0)
	/opt/homebrew/opt/libevent/lib/libevent-2.1.7.dylib (compatibility version 8.0.0, current version 8.1.0)
	/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
	/usr/lib/libffi.dylib (compatibility version 1.0.0, current version 30.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1319.0.0)
512 rmills@rmillsm1:/opt $

It seems this can be closed. Please report if you keep seeing this issue, we'll reopen.


How do I know if this worked?

What would I do to test?
Please add to readme

Please elaborate. Try to include screenshots, also you could use a sample barebones .vimrc file.


Adaptive RaisedButton

Description
Adaptive implementation for RaisedButton per #33830

Tests
Added the following basic tests:

Adaptive RaisedButton displays CupertinoButton in iOS
Adaptive RaisedButton does not display CupertinoButton in non-iOS

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

RaisedButton will be deprecated in the next week or two and should not be the basis for new work, please see:  flutter.dev/go/material-button-system-updates.
Adaptive buttons are not part of the material spec, https://material.io/design/platform-guidance/cross-platform-adaptation.html#cross-platform-guidelines, and should not become part of the material library.


chore: release main

:robot: I have created a release beep boop
swc: 0.4.26
0.4.26 (2024-12-11)
Bug Fixes

deps: update rust crate serde to v1.0.216 (#1634) (bb2d418)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

swc0.4.26
:sunflower:


Add MetaSoccer Universe logo

As requested, we've opened GitHub issue with all token details here: https://github.com/sushiswap/default-token-list/issues/346 .
This PR adds the logo related to the token we'd like to include to your default list as per referenced issue.

Added


stdlib: Fix SR-587 – Array(count:repeatedValue:)

What's in this pull request?

Fixes SR-587 by removing the specific array implementation of Array(count:repeatedValue:) and instead using the RangeReplaceableCollection -protocol's implementation.
Resolved bug number: (SR-587)

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

This implementation is likely faster than the default.  Did you benchmark it?

Sorry, no didn't benchmark it, I though this was the way to fix SR-587...

SR-587 was primarily about adding a new defaulted requirement to RangeReplaceableCollection (which we already did).
Whether concrete types should keep its customization is a different story.  If a concrete implementation is faster, then we should keep it.  About this one in particular, it looks like it would be faster than calling append() in a loop.

Ok, misunderstood what the bug was about then. Still learning about all this stuff :)


03/28/2018 10:52 : Create Pull Request for branch prTesting_2018032810 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.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.


Hello Microverse project pull request

Microverse Hello Project Pull Request 1
In this project, the following was done:
Created HTML and Style sheet files.
Incorporated Microverse HTML and CSS linters for code validation
-Added gitignore file to prevent the node/modules and test.md files from being commit to the git repository

@roshan-bajgain I am not understood the MIT licence broken could you please explain it .


Material source code folder doesnt open in vscode

Bug, feature request, or proposal:
Bug
What is the expected behavior?
The title bar shows that the folder is opened and the files and folder should be visible in the sidebar.
What is the current behavior?
Folder is not opened and the files and folder are not visible in the sidebar but the title bar shows the folder is opened correctly. If the parent folder is opened there is no issue and check the attached pictures
when opened directly

When open by selecting the parent folder

Is there anything else we should know?
OS: Arch

This has nothing to do with the material2 source code at all!
You should post this issue here.

Yes i was not sure if i should post it here or vscode since material source is only folder which is effected, ty.
Will post it over there.

Closing as this seems to be an issue in VSCode.


Resolves Laravel Error: Class UDPSocket cannot extend final class Socket

I imported Condenser into a Laravel Framework 10 project and I got the error "Class UDPSocket cannot extend final class Socket". I troubleshooted it for a few hours and then realized that it might be a name conflict. So first I changed UDPSocket.php and changed:
class UDPSocket extends Socket {
to: class UDPSocket extends scSocket {
Then in socket.php I changed:
abstract class Socket {
to: abstract class scSocket {
Then TCPSocket.php I changed:
class TCPSocket extends Socket {
to: class TCPSocket extends scSocket {
This worked!
Also to get it working on Laravel 10 with Php 8 I also modified my composer.json with different versions:
"require": {
"monolog/monolog": "~3.5"
"require-dev": {
"phpunit/phpunit": "^10.1",
and removed phpdocumentor, not sure what that breaks?
Note, I didn't modify the composer.json file in the pull request.

This can’t be a thing. The library operates in its own namespace. If you’re using Composer and its autoloader you shouldn’t be having any issues.
The Socket class here is abstract, not final. It sounds like you’re pulling in the files manually and removing or mixing namespaces oddly causing conflicts with an existing finalised Socket class.
Seems unlikely to be caused by this project.

So this came about when I restored an old project which worked quite a few years ago. I installed the latest laravel, php and condenser library. When i first tested it, I set it up in composer and composer was generating the exact same error message. E.g. when I typed the command in the debian shell 'composer update'. So then I temporarily removed the condenser autoload entries - 'files' and 'psr-4', which got past the composer error. But then when I tried to run a server query via my php code I got the error again. I thought the issue was related to laravel, like it somehow loaded another socket class that conflicted. Because it was saying the class was 'final', but when I checked it the condenser class is not set as 'final'. That gave me the idea to use a different class name, which solved it. I am not an expert on these things, but I got it working so got inspired to do a pull request. So I think Laravel is the cause but I understand if you guys decide not to use the changes. I guess If someone finds my fork from a google search, then that should be enough. cheers

also, as you mention, technically what you said was correct. I was pulling in the files manually. I was adding the composer parts myself to an already populated comopser file (which gets filled by laravel). Im then calling the extension using a Controller. Using commands like:
use SourceServer
use MasterServer;
use SteamId;
Doing that everything works except for the socket class name conflict.

For Composer dependencies you shouldn't be touching those yourself. Especially entries in lockfiles or the autoloader. The composer command should managed those fully. That also means that the files in your vendor directory populated by Composer, which includes the files from this library, must not be touched. If you do need to work on a modified version of this library, consider forking this repo to your on github account, or creating a local repo. Instructions to set those up are in Composer repositories documentation.
Composer errors are probably dependency / conflicts? in which case you do need to resolve those on your own. I doubt Laravel has an odd setup for Composer, so getting this library should be a matter of composer require in your root directory. Perhaps ask around in the Laravel community, but of course paste in the messages that Composer is spitting out.

I replied to you before with 2 messages at once, I feel you may have missed the first one?
But to summarise from your message: The composer error was the same as the function error I got: Class UDPSocket cannot extend final class Socket.
I did create a fork and the changes I made already fixed my issue. I did use composer require to add Condenser, next time I can reference my own fork if I ever install it again or need to update my composer. I had to change the versions of some other libraries because those older versions were too old for the dependencies Laravel was using. I do not edit lockfiles. The reason I suggested the pull request was because I thought it would not effect the main branch functionality, but it definitely does resolve the issue with socket class name for anyone trying to use Condenser with the laravel framework.


pull request for e2e test at 12/05/2016 09:56:01

:white_check_mark: Validation status: passed
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.


freeze version of furo to prevent breaking doc builds

[ ] I have added the tests to cover my changes.
[x] I have updated the documentation and CHANGELOG accordingly.
[x] I have read the CONTRIBUTING document.

Hello. You may have forgotten to update the changelog!
Please edit CHANGELOG.md with a one-to-two sentence description of the change in the UNRELEASED section. You may include a small working example for new features.


Outdated Ratatui Dependency

It has to either be bumped to 25.0 or removed completely.

Hiya @gin66, my users of youtui are reporting breakage due to mismatched ratatui versions and I think it tracks back to this change. Is it possible to have changes to the ratatui version accompanied by a change to the most major version number in future? https://github.com/nick42d/youtui/issues/16

Thanks for the hint. Will do so in the future

Thanks for the hint. Will do so in the future

Cheers! I think it may be possible to automate in your github actions using cargo-semver-checks. If I can figure it out will shoot through a PR.

I swear by release-plz for this. Once it's setup, you don't need to worry - handles semver changes automatically.


NullPointerException on PutJobSuccessResult for builds with artifacts (version 0.29)

This issue appears to be new in version 0.29. I'm getting these errors at the end of my builds now:
[AWS CodePipeline Plugin] Publishing artifacts
[AWS CodePipeline Plugin] Build succeeded, calling PutJobSuccessResult
ERROR: Build step failed with exception
java.lang.NullPointerException
	at java.util.regex.Matcher.getTextLength(Matcher.java:1283)
	at java.util.regex.Matcher.reset(Matcher.java:309)
	at java.util.regex.Matcher.<init>(Matcher.java:229)
	at java.util.regex.Pattern.matcher(Pattern.java:1093)
	at java.util.Formatter.parse(Formatter.java:2547)
	at java.util.Formatter.format(Formatter.java:2501)
	at java.util.Formatter.format(Formatter.java:2455)
	at java.lang.String.format(String.java:2940)
	at com.amazonaws.codepipeline.jenkinsplugin.LoggingHelper.log(LoggingHelper.java:28)
	at com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelinePublisher.perform(AWSCodePipelinePublisher.java:170)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:735)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:676)
	at hudson.model.Build$BuildExecution.post2(Build.java:186)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:621)
	at hudson.model.Run.execute(Run.java:1760)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:405)
Build step 'AWS CodePipeline Publisher' marked build as failure
Finished: FAILURE

Sometimes there is no stack trace:
[AWS CodePipeline Plugin] Publishing artifacts
[AWS CodePipeline Plugin] Build succeeded, calling PutJobSuccessResult
ERROR: Build step failed with exception
java.lang.NullPointerException
Build step 'AWS CodePipeline Publisher' marked build as failure
Finished: FAILURE

These builds all have a single artifact with a blank location (to zip up the whole workspace). Our build which doesn't have any artifacts is succeeding.
The PutJobSuccessResult call appears to have been successful because CodePipeline thinks the job has succeeded. The Jenkins job is marked as failed however.

I could not reproduce the issue. Would you mind posting more details about your environment?

This appears to be an issue with upgrading from 0.28 to 0.29. If you create a fresh job on 0.29 it will work fine. If you create a job on 0.28 and then upgrade the plugin to 0.29 it will fail. It will succeed again after you save the job configuration on 0.29 (without making any changes).
I did the following test:

Create a test job on 0.28 and run the pipeline (succeeds)
Upgrade plugin to 0.29
Run the pipeline again (fails)
Go to the job configuration and click save
Run the pipeline again (succeeds)

I took a snapshot of the job directory before and after step 4. Before saving, this was the job config.xml:
<?xml version='1.0' encoding='UTF-8'?>
<project>
  <description></description>
  <keepDependencies>false</keepDependencies>
  <properties/>
  <scm class="com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM"<EMAIL_ADDRESS>    <clearWorkspace>true</clearWorkspace>
    <projectName>CodePipeline_Test_2</projectName>
    <actionTypeCategory>Build</actionTypeCategory>
    <actionTypeProvider>Jenkins</actionTypeProvider>
    <actionTypeVersion>4</actionTypeVersion>
    <region>eu-west-1</region>
    <awsAccessKey></awsAccessKey>
    <awsSecretKey></awsSecretKey>
    <proxyHost></proxyHost>
    <proxyPort>0</proxyPort>
    <awsClientFactory/>
  </scm>
  <canRoam>true</canRoam>
  <disabled>false</disabled>
  <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
  <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
  <triggers>
    <hudson.triggers.SCMTrigger>
      <spec>* * * * *</spec>
      <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
  </triggers>
  <concurrentBuild>false</concurrentBuild>
  <builders/>
  <publishers>
    <com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelinePublisher<EMAIL_ADDRESS>      <outputArtifacts>
        <com.amazonaws.codepipeline.jenkinsplugin.OutputArtifact>
          <location></location>
        </com.amazonaws.codepipeline.jenkinsplugin.OutputArtifact>
      </outputArtifacts>
      <awsClientFactory/>
    </com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelinePublisher>
  </publishers>
  <buildWrappers/>
</project>

After saving, this was the new job xml:
<?xml version='1.0' encoding='UTF-8'?>
<project>
  <actions/>
  <description></description>
  <keepDependencies>false</keepDependencies>
  <properties/>
  <scm class="com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelineSCM"<EMAIL_ADDRESS>    <clearWorkspace>true</clearWorkspace>
    <projectName>CodePipeline_Test_2</projectName>
    <actionTypeCategory>Build</actionTypeCategory>
    <actionTypeProvider>Jenkins</actionTypeProvider>
    <actionTypeVersion>4</actionTypeVersion>
    <region>eu-west-1</region>
    <awsAccessKey></awsAccessKey>
    <awsSecretKey></awsSecretKey>
    <proxyHost></proxyHost>
    <proxyPort>0</proxyPort>
    <awsClientFactory/>
  </scm>
  <canRoam>true</canRoam>
  <disabled>false</disabled>
  <blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
  <blockBuildWhenUpstreamBuilding>false</blockBuildWhenUpstreamBuilding>
  <triggers>
    <hudson.triggers.SCMTrigger>
      <spec>* * * * *</spec>
      <ignorePostCommitHooks>false</ignorePostCommitHooks>
    </hudson.triggers.SCMTrigger>
  </triggers>
  <concurrentBuild>false</concurrentBuild>
  <builders/>
  <publishers>
    <com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelinePublisher<EMAIL_ADDRESS>      <outputArtifacts>
        <com.amazonaws.codepipeline.jenkinsplugin.OutputArtifact>
          <location></location>
          <artifactName></artifactName>
        </com.amazonaws.codepipeline.jenkinsplugin.OutputArtifact>
      </outputArtifacts>
      <awsClientFactory/>
    </com.amazonaws.codepipeline.jenkinsplugin.AWSCodePipelinePublisher>
  </publishers>
  <buildWrappers/>
</project>

I think the relevant difference is probably that after saving the outputArtifact has an (empty) artifactName.

Thank you for bringing this issue to us. We have been able to reproduce this issue, and new release aws-codepipeline-0.32 fixes the problem.

Thanks. I can confirm this issue is fixed with version 0.32.


Implement RFC 52

Description of changes
Issue #, if available
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):

[ ] A breaking change requiring a major version bump to cedar-policy (e.g., changes to the signature of an existing API).
[ ] A backwards-compatible change requiring a minor version bump to cedar-policy (e.g., addition of a new API).
[ ] A bug fix or other functionality change requiring a patch to cedar-policy.
[ ] A change "invisible" to users (e.g., documentation, changes to "internal" crates like cedar-policy-core, cedar-validator, etc.)
[ ] A change (breaking or otherwise) that only impacts unreleased or experimental code.

I confirm that this PR (choose one, and delete the other options):

[ ] Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).
[ ] Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

[ ] Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.
[ ] Requires updates, and I have made / will make these updates myself. (Please include in your description a timeline or link to the relevant PR in cedar-spec, and how you have tested that your updates are correct.)
[ ] Requires updates, but I do not plan to make them in the near future. (Make sure that your changes are hidden behind a feature flag to mark them as experimental.)
[ ] I'm not sure how my change impacts cedar-spec. (Post your PR anyways, and we'll discuss in the comments.)

Progress track

[ ] policy
[ ] schema
[ ] EST

Noting that this fixes a failure in the fuzz target convert-schema-json-to-human by correctly rejecting the __cedar namespace in JSON format schema.

This needs a couple more tests cases:

__cedar in the middle of a path: A::__cedar::B
in extensions function names (which are implemented as paths IIRC): __cedar::decimal("0.0")
in non-path ids: e.g., {__cedar: 0}, @__cedar("foo") permit(...)

I think we should allow __cedar in the annotations as well as attribute names. We already allow certain reserved keywords in them.

I think we should allow __cedar in the annotations. We already allow certain reserved keywords in them.

I agree, but I still think test cases for these would be wise

Thank you for your reviews, @cdisselkoen @john-h-kastner-aws. I've addressed existing comments and will wait Monday to merge it so that we don't need to address potential DRT failures over the weekend.


Fixed JSDoc

Fixed some JSDoc to avoid warnings of the IDE of not matching object types.

Why do you think lowercase string is correct?

See official documentation:
http://usejsdoc.org/tags-param.html
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/typeof
Primitive data types are wirtten in lower case, classes in CamelCase.
Main change was the change of variable "code" from string to number.

The variable code is not necessarily a number.
And for the lower case discussion, we don't use JSDoc, but the common known syntax to document functions. The primitives types like String, Number, Boolean are written with a starting capital letter as https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects points out.


Fix slow response

Problem:
curl -XGET localhost:8432/a/1AuGvfDfNhbeVNUDzXHjLmEnFnWv3pkjjG/utxos
Response time: ~60 seconds or time out.
Debug:
To get utxos, we searchRange all blocks by addressToScriptID:
If latest block is ~1M6.  Split all blocks to n time to hit db by chunkSize.
Example, latest block is ~1M6. / chunkSize(10) = 160k times.
i found that chunkSize too small, hit to leveldb too much.
Reduce n to help reduce response time
Solution:
I tried to increase chunkSize value to 100, 1000, 10_000 and 100_000.
Benchmark show that with chunkSize = 10_000 return good response Time
< 1 seconds on mainnet
$ time curl localhost:8432/a/1AuGvfDfNhbeVNUDzXHjLmEnFnWv3pkjjG/utxos
real	0m0.638s
user	0m0.005s
sys	0m0.015s

$ time curl localhost:8432/a/1Afb76aMKPTpSppV9nZrf3Nfmg4KXvikeA/utxos
real	0m0.169s
user	0m0.006s
sys	0m0.005s

$ time curl localhost:8432/a/19s5TAWJNdsRxzoHN51TPsWnCieD2h1M1y/utxos
real	0m0.090s
user	0m0.006s
sys	0m0.004s

I just noticed this pull requests and applied the suggested fix to the indexd instances on my servers and it seems to be running MUCH faster. Thank you very much @longhoangwkm for submitting this fix.

You're welcome. Btw, we sometimes have problems with exceeding the max limit for the number of node object errors. I think we should keep developing this CIP: https://counterpartytalk.org/t/cip22-change-indexd-to-addrindexrs/5870.  We need a big change, I'm eager to contribute to a new project.


Tag a new version

Hi,
Would it be possible to tag a new version of this package?
I'm using the github.com/gin-contrib/sessions package, which depends on this package (v2.0.0), which in turn depends on github.com/mattn/go-sqlite3 v2.0.3. The whole v2 version branch of that go-sqlite3 package was a mistake by the maintainer and they continued to release packages as v1.* versions.
You've already fixed this in your master branch, but did not yet tag a new version, which would likely fix my problem.
For now I downgraded to a lower version of github.com/gin-contrib/sessions, which doesn't depend on this package, which allows me to use the latest go-sqlite3 package.
Thanks,
Bert

Hey, sure no problem, good you reminded me. Have tagged master with v2.0.1 now.

I choosed to bump minor version, i hope that is appropriate if only dependencies have changed

Thanks! :)

👍 haven used v2 sub directory and v2 tags before so let me know if something seems strange


Status of this Java Client SDK ?!?

I am currently evaluating emitter.io as an alternative to deepstream which has some outdated and buggy client SDKs, especially when it comes to Java/Android.
First, I was very happy when I read about the concepts of emitter.io and excited to give it a try. But now that I see this 4 year old Java SDK I am really frustrated. :-( It cannot be integrated in Android as a simple Gradle dependency, the API seems to be outdated compared to the Javascript SDK, it only has 4 stars (???), ...
All in all, this does not seem worth an evaluation at all.
And again (like with deepstream) I am asking myself WHY IS THIS?  Or am I missing something?
Are there any plans for updating this SDK?

We certainly do wish to have all our clients up to date. However, writing and maintaining multiple SDKs is very time consuming, so we have to focus our efforts on the most demanded ones. The Go SDK is up to date, I'm just done updating the Python one, and I'm currently busy updating the C# version (should be done this week). I think there are just a couple of stuff I need to add to the Javascript SDK.
I'm probably going to fill a table with the features each SDK has or lack and put it in the documentation.
Now, honestly, you are not the first, but still one of the firsts to complain about the Java SDK, that's why it wasn't a priority to update it.
As you said, it's an open-source project, and we are always happy to receive contributions. For example, the Dart and Angular libs are external contributions.
I can certainly put the update of the Java SDK on our roadmap. About Android however, I'm not sure at this point how to solve the problem described here: Android Platform Support #91.

Thank you for your fast and informative response. In the first place, this signals a "living project" and that we agree on the ultimate goal of having all clients up to date. Perfect.
A table with features/status of each SDK would be a first step.
Regarding Java/Android: by simply looking at the number of devices out there, Java/Android is IMHO the must have SDK besides web. I think it's not only me who would honor an up to date SDK here. You already mentioned Issue#91 but I'm sure theres way more. Java/Android could give you a real boost compared to your competitors.
I also commented in Android Platform Support #91 as I don't understand some of the details mentioned there.

I spent some more hours on finding a "realtime pub/sub solution" for my requirements:

open source, self-hosted, simple, fast, stable
support for Java/Android, Python, JavaScript
presence, persistence
security, scalability

On a first glance, it looks like there are a lot of options. But like one year ago, I ended up with:

deepstream.io --> outdated/buggy/inactive Java/Android client and maybe doing a bit too much
socket.io --> also several complaints about Java/Android and does not cover all my requirements
emitter.io --> my new preferred option which covers everything except for the Java/Android client

Why do I tell this?
Well, probably because I hope that we will have an up-to-date Java/Android client very soon. :-)
And because I think my requirements are quite common which underlines what I said before:

Java/Android could give you a real boost compared to your competitors.

One more thing...
You said: Go, Python, C# (all based on Paho) and Javascript SDKs are (almost) up-to-date --> PERFECT!
Looking at your Python implementation, am I right that we basically "just" need to port emitter.py and subtrie.py to Java/Android with the according Java/Android implementation of Paho?
Most important: How long would this roughly take for you as an expert in Emitter/MQTT/other SDKs?
I am just asking to get a feeling how much time I would need because at the moment this seems like my best option out of the 3 possibilities mentioned above.
Thanks for your time and support.

I haven't touch a line of Java since school. First, I'm going read and understand the previous version thoroughly, how it was done with Future, Promise, Dispatch queues, ... I'll probably need to integrate a newer version of the MQTT lib. Only then I'll start updating Emitter, and testing. Finally, you mentioned Gradle, well I have no idea how to package a java application.
It's difficult for me to evaluate but it's for me at least several full days of work. If you know Java and its async model well, you know how to package, and you read the Python version to understand how Emitter works, maybe 3 days for you?


CiaB as edge appliance

Maybe we have a use case for this idea that we could illustrate well.
We designed and built a prototype for our lab intended for automation in discrete manufacturing (less important now). But: the software that records the process and system data is currently running on a local workstation. We would like to virtualize this computer and run it as an edge solution (VM). The SW part in the VM in the edge device communicates than with the software in our private cloud (still pure OpenStack).
Maybe that's a possibility? Above all, this is a possibility that we could realize in the short term - alongside all other activities...
Feedback welcome.

Indeed, thanks @rholling - imho there are several good use-cases for CiaB as an edge appliance.
I'd actually like to also look into being able to orchestrate a set of CiaBs (moving this closer towards being actually an edge solution). Other setups could benefit from this as well, since one CiaBs is basically like one single scs deployment being able to orchestrate multiple of them (and having things like observability across all of them, ...) would be really nice.


IO pins on user_analog_project_wrapper

It would be great to know the structure of the gpio_analog, gpio_noesd and io_analog pins on the pad-frame. Knowing the load resistance or capacitance present would help in designing efficient measurement circuits and buffers for analog designs.

We need additional documentation, as some of the specs for the I/O cells in particular are in SkyWater documentation that did not get into the public repository.

This diagram explains the data connections to the pads on the caravan chip.  For the eleven pads across the top, there is a straight-through wire from the pad to the core, with no ESD protection.  Those are the io_analog pins.  The GPIO pads are more flexible;  they have digital input and output buffers, but those can both be turned off by configuration, and analog signals can be connected via gpio_noesd (straight wire through from the pad) or gpio_analog (wire to the pad in series with a 150 ohm resistor).  Both of these analog connections have ESD protection diodes---the "noesd" in the name refers to the fact that there is no additional machine-model (MM) ESD protection.  Do not use gpio_noesd unless your circuit cannot tolerate the 150 ohm series resistance (and if you do use it, be aware that your chip will be considerably more ESD-sensitive).


I want AaC to determine definition dependencies

As an AaC user, I want AaC to determine definition dependencies, so that I can perform actions such as deleting definitions that are depended on by others.
AC:

[ ] Validate identifies definition dependencies

Validate identifies which definitions, if any, that the target definition references or requires be present in the language context. (e.g. definition dependencies) (?? Maybe scope too big. Move to new story?)

[ ] Validate validates/adds definitions in dependency order

If a definition has no dependencies outside the current context, it is validated first
If definition A has some reference or requirement on definition B, then B is added to the context before A.

[ ] Validate does not validate definitions with a dependency on invalid definitions.

[ ] If a definition is not validated because it has an invalid dependency, then a message is returned to the user with the name of the definition and its invalid dependency. (?? Do we need this? This would prevent users from understanding the full-breadth of the issues when validating.)
[ ] If definition A has a dependency on an invalid definition B, then definition A is neither validated nor added to the context

This task needs to be re-evaluated and broken apart into smaller chunks.
Needs to be updated to reference new API and new terminology.
Definition dependency evaluation will likely be one chunk of logic and behavior and will potentially be solidified by supporting constraints to work off the definition dependency information. This implementation logic will likely make use of the dependency graph that is requested in #473
This work is hefty and would likely not be worked in the future.


Rename root branch to main

This is an old repo, and the main branch is still called master. I will rename to main for the mixs 6 release.

done


recursive JSON $ref in schema goes into infinite loop

ditto

looks like this was a problem in go-jsschema.


python3Packages.anyio: disable all socket-related tests on darwin

Motivation for this change
@SuperSandro2000 #99521
They don't work in their sandbox.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 102193 run on x86_64-darwin 1

4 packages failed to build:

python37Packages.anyio
python37Packages.ircrobots
python38Packages.anyio
python38Packages.ircrobots

Pushed a version disabling the correct file. Please retest.

Pushed a version disabling the correct file. Please retest.

@SuperSandro2000

Result of nixpkgs-review pr 102193 run on x86_64-darwin 1

4 packages built:

python37Packages.anyio
python37Packages.ircrobots
python38Packages.anyio
python38Packages.ircrobots


[Docs] Meshery CRD Reference: Broker

Current State
The Meshery CRDs are not included in Meshery Docs.
Desired State
Create a "CRDs Reference" page in the "Reference" section of Meshery Docs. Include the following information:
CRD Name
description of the CRD's purpose
YAML Synopsis
apiVersion: core.meshery.io....
kind: Broker
metadata:
  name:
spec:
.
.
.

Fields

apiVersion – API version being used. Must be v1alpha3 or later for this syntax.

kind – Resource type. Must be set to...

metadata -

name –

spec -

property – description

property – description

property – description

property – description

Usage
sample use scenario
Example Use
explanaation of example
apiVersion: core.meshery.io....
kind: Broker
metadata:
  name:
spec:
.
.
.

explanaation of example
See Also
link to other Meshery CRD

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

@leecalcote this issue can be closed too

Good work. Mr. Kiptoon.


Consistent reporting native module name on crash on native side

Summary
Reopened PR https://github.com/facebook/react-native/pull/24704#issuecomment-490017599
PR https://github.com/facebook/react-native/pull/24633 introduced some inconsistency in crash messaging, this PR fix it. Asked by @mhorowitz
Changelog

[General] [Added] - Consistent reporting native module name on crash on native side
Test Plan

Actually I didn't managed to reproduce this kind of crash, looks like something changed here.

Thank you, again, and sorry we unlanded it accidentally.

No problem, it happens! ;) Thank you for developing such a great framework.


DefaultLoadingIndicator not working on loading more, any idea?

@Jaafar-abusair You may want to share some code so we can better understand your situation.
I've also noticed that the loading indicator doesn't work if I return from my function that is called for onLoadMoreAsync immediately, e.g. if the component is already loading more and I don't want to load again. Is that what you're doing too?

@markymc Where's loading indicator surpose to be? There's no screenshot, and i cloudn't see it, it supposedly displays on the bottom of the list

@Tom29 Yes, in the usual place in the bottom of the list. :)


Fix dialog window creation position

When creating new windows through certain prompts on Windows (ex: through preferences menus), the windows are created at position (0, 0) (top left), thereby obscuring the window controls from view until the window is resized.

A separate commit in master has fixed this.


Some Questions about Picker's rem

I use picker components when I make mobile pages, but there are some problems in the style of picker components. Because I use rem, the style of picker components has not changed into rem, which leads to very small picker on high-resolution models such as the iPhone X, which is very unpleasant for the user experience. Quickly, I don't know the way I use it, or how. I read the document and didn't find that the picker component has relevant interfaces. I hope I can get an answer. Thank you.

Sorry，I think I know why.I solved it.


Add convenience methods to context object.

Closes #125

This change is

Review status: 0 of 9 files reviewed at latest revision, all discussions resolved.

demo/vaadin-router-route-actions-demos.html, line 38 at r1 (raw file):

context.next [function] proceed to resolving the next
          matching route (if any)

context.redirect(path) [function] redirect to the path specified

Let's emphasize that only calling the context.redirect() function would not redirect anywhere, and that redirect happens only if the return value from the context.redirect() function is returned as the action 'result'.

demo/vaadin-router-route-actions-demos.html, line 39 at r1 (raw file):

          matching route (if any)

context.redirect(path) [function] redirect to the path specified

context.render(component) [function] that calls

How about renaming the render method to component so that the it matches the route property name?

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions.

demo/vaadin-router-route-actions-demos.html, line 151 at r1 (raw file):

    </vaadin-demo-snippet>

Redirecting from an action

let's capitalise this: "Redirecting from an Action"

demo/vaadin-router-route-actions-demos.html, line 162 at r1 (raw file):

      Note: If you need only to redirect to another route, defining an action might be an overkill.
      More convenient way is described in Router redirect section.

let's change "Router redirect" to "Redirects" so that the link text is consistent with the navigation

demo/vaadin-router-route-actions-demos.html, line 192 at r1 (raw file):

    </vaadin-demo-snippet>

Returning custom element as an action result

let's capitalise this: "Returning Custom Element as an Action Result"

demo/vaadin-router-route-actions-demos.html, line 201 at r1 (raw file):

      Note: If the only thing your action does is custom element creation, it can
      be replaced with component property of the route.
      See Basic demos section for examples.

"Basic demos" is now called "Getting Started"

Comments from Reviewable

Review status: 5 of 9 files reviewed at latest revision, 6 unresolved discussions.

demo/vaadin-router-route-actions-demos.html, line 38 at r1 (raw file):
Previously, vlukashov (Viktor Lukashov) wrote…
Let's emphasize that only calling the context.redirect() function would not redirect anywhere, and that redirect happens only if the return value from the context.redirect() function is returned as the action 'result'.

Done.

demo/vaadin-router-route-actions-demos.html, line 39 at r1 (raw file):
Previously, vlukashov (Viktor Lukashov) wrote…
How about renaming the render method to component so that the it matches the route property name?

Sounds nice, done.

demo/vaadin-router-route-actions-demos.html, line 151 at r1 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
let's capitalise this: "Redirecting from an Action"

Right, always forget about this, thanks.

demo/vaadin-router-route-actions-demos.html, line 162 at r1 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
let's change "Router redirect" to "Redirects" so that the link text is consistent with the navigation

Done.

demo/vaadin-router-route-actions-demos.html, line 192 at r1 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
let's capitalise this: "Returning Custom Element as an Action Result"

Done.

demo/vaadin-router-route-actions-demos.html, line 201 at r1 (raw file):
Previously, web-padawan (Sergey Kulikov) wrote…
"Basic demos" is now called "Getting Started"

Thanks, done.

Comments from Reviewable

Review status: 5 of 9 files reviewed at latest revision, 4 unresolved discussions.

src/resolver/resolver.js, line 146 at r2 (raw file):

      currentContext = Object.assign({}, context, matches.value);
      currentContext.redirect = path => redirect(currentContext, path);
      currentContext.component = component => context.render(component, currentContext);

(dependencies) Can this be done without introducing a dependency from Resolver to Router?
The resolver layer should not know about the component and redirect properties.

Comments from Reviewable

Review status: 5 of 9 files reviewed at latest revision, 5 unresolved discussions.

src/router.js, line 191 at r2 (raw file):

        }
      }
      return Router.renderComponent(route.component, context);

For consistency with the redirect property this could be return context.component(route.component). And then the Router.renderComponent() method can be made private. What do you think?

Comments from Reviewable

Review status: 5 of 9 files reviewed at latest revision, 6 unresolved discussions.

src/router.js, line 191 at r2 (raw file):
Previously, vlukashov (Viktor Lukashov) wrote…
For consistency with the redirect property this could be return context.component(route.component). And then the Router.renderComponent() method can be made private. What do you think?

Sounds great, done.

src/resolver/resolver.js, line 146 at r2 (raw file):
Previously, vlukashov (Viktor Lukashov) wrote…
(dependencies) Can this be done without introducing a dependency from Resolver to Router?
The resolver layer should not know about the component and redirect properties.

Sure, done.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Changing Map Design and make it in a pop up view in events feature section

Hey, I saw the map that you have used in the events feature of the site. I want to change that map and make it look more representative by making it in a pop-up view and changing the overall map design. I will be highly thankful if you can assign this to me.
Also, I am a contributor in GSSOC 2023.

Hey, @akshitagupta15june Please assign this to me!


Include ng2-qrcode to angular 2-webpack-starter

Hi, I need ng2-qrcode connect to angular2-webpack-starter. How I can connect the script qrcode.js to project?

👍  Need this also


[RFC]Exposed Core.VlcMediaPlayer and Interops.VlcManager

It allows users to unlock features that are not yet implemented/too low-level to be implemented in the VlcControl.
What do you think about this? Is it too dangerous to let users play with the internals of this library?
Fixes #239

If you have a use for it and probably other people will as well, I don't see why it should not be exposed.

I do have a warning, but not all caps, should I change that?
Thanks for your answer.

I would, that way they know you mean business. But the important part is that there is a warning :thumbsup:


Search results don't include terms from a block's drop-down

Describe the bug
When searching, drop down values are not considered.
To Reproduce
Steps to reproduce the behavior:

Go to arcade.makecode.com/beta
Search for "stay in screen"
Notice there is no good match

Expected behavior
This match should appear:

@darzu please file bugs on the target (even though it is generic issue). We triage bugs on the target for every release. Pxt is only for setup & high level feature request..


[Flink-17644] Add state expiration to the Java SDK

This PR adds state expiration (state TTL in Flink land) to the persisted states in the Java SDK. follow up PR would expose that to the model.yaml.
There are two types of expirations:

expiration after the last write
expiration after the last write or read

The change was verified manually by modifying the Greeter example to
expire it’s state 5 seconds after writing.

Closed in dd85b1184715a4e19aac527584e00f9e17c47aeb


Loggerd on PC

issue https://github.com/commaai/openpilot/issues/2277

[ ] c++ encoder
[ ] encoder for pc

That was fast :)
Can you make sure encoder.c is properly git moved to encoder.cc? It'll make it much easier to review the diff.


Unreal Development Kit Achievements Received Without Ownership

I received achievements randomly for a game or tool called Unreal Development Kit, which I have never owned. When I try to reset or remove the achievements, they don't appear on the Steam Achievement Manager list because I don't own it.
the app id : 13260

Some app codes have been removed, but the program can still add achievements. I have tested it.

I tried adding the ID manually, but received an error saying 'You don't own this game.' I also attempted to use the Steam console to remove the achievements one by one, but that didn't work either. I got the following error message: 'achievement_clear failed: EUTA_EXPLORE_EveryMutator.

If an achievement is added to the list of deleted apps, the item cannot be deleted.