[BUG] Panic during receiving events occurs

Describe the bug

What are you trying to do?
I'm trying to use pubsub pattern with default broker. v4.7.0

What did you expect to happen?
Successful publishing and receiving events

What happens instead?

2022-06-21 14:45:59  file=server/rpc_router.go:513 level=error goroutine 84 [running]: runtime/debug.Stack()         /usr/lib/go/src/runtime/debug/stack.go:24 +0x65 go-micro.dev/v4/server.(*router).ProcessMessage.func1()         /home/racoon/go/pkg/mod/go-micro.dev/v4@v4.7.0/server/rpc_router.go:513 +0xc5 panic({0xf79dc0, 0x11f8aa0})         /usr/lib/go/src/runtime/panic.go:844 +0x258 reflect.Value.Addr({0x10544a0?, 0xc000290ff0?, 0xc0002f6348?})         /usr/lib/go/src/reflect/value.go:273 +0x65 go-micro.dev/v4/server.(*router).ProcessMessage(0xc0001c0ab0, {0x12007a0, 0xc000290fc0}, {0x1202570?, 0xc000632480})         /home/racoon/go/pkg/mod/go-micro.dev/v4@v4.7.0/server/rpc_router.go:560 +0x553 go-micro.dev/v4/server.(*rpcServer).HandleEvent(0xc00017c780, {0x1200ce0?, 0xc000290f60?})         /home/racoon/go/pkg/mod/go-micro.dev/v4@v4.7.0/server/rpc_server.go:129 +0x47a go-micro.dev/v4/broker.(*httpBroker).ServeHTTP(0xc0001fc0f0, {0x11ffd58, 0xc00029e540}, 0xc000220400)         /home/racoon/go/pkg/mod/go-micro.dev/v4@v4.7.0/broker/http.go:345 +0xab5 net/http.(*ServeMux).ServeHTTP(0xc00001c147?, {0x11ffd58, 0xc00029e540}, 0xc000220400)         /usr/lib/go/src/net/http/server.go:2462 +0x149 net/http.serverHandler.ServeHTTP({0x11fdbf8?}, {0x11ffd58, 0xc00029e540}, 0xc000220400)         /usr/lib/go/src/net/http/server.go:2916 +0x43b net/http.(*conn).serve(0xc0005300a0, {0x12007a0, 0xc000290120})         /usr/lib/go/src/net/http/server.go:1966 +0x5d7 created by net/http.(*Server).Serve         /usr/lib/go/src/net/http/server.go:3071 +0x4db
How to reproduce the bug:
just run simple example with the newest go-micro version
Environment:
go version go1.18.3 linux/amd64
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/racoon/.cache/go-build"
GOENV="/home/racoon/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOMODCACHE="/home/racoon/go/pkg/mod"
GOOS="linux"
GOPATH="/home/racoon/go"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/racoon/develop/racoon-devel/examples/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2203251113=/tmp/go-build -gno-record-gcc-switches"

Your code works fine for me

Hm.. Surprise.. I need time to handle it...

Stop. It's not work. There no messages about events on server! log is empty. In my case too, but i use debugger for determine where errorr occurs

publishing is success, but receiving does not work

Ahh I see. I'll have a look

Jeezz that was a rabbit hole. Turns out the issue is with the json to proto reflection in github.com/golang/protobuf/jsonpb. It fails to unmarshal nested proto messages. If you try to send a proto message without another nested proto message it works fine.
To get the example to work, you would need to get the following to work, as this is basically what happens in the go-micro event handling:
func TestNotification(t *testing.T) {
	ev := &pb.Notification{
		Event: &pb.Event{
			Time: timestamppb.Now(),
			Text: fmt.Sprintf("Messaging you all day on %s", "mytopic"),
		},
		Kind: pb.Notification_DownloadComplete,
	}

	b, _ := json.Marshal(ev)

	t.Log(string(b))

	var out *pb.Notification
	if err := jsonpb.Unmarshal(bytes.NewReader(b), out); err != nil {
		t.Fatal(err)
	}
	t.Logf("Output: %+v\n", out)
}

The high-level go-micro pub/sub methods as used in the example try to be accommodating and allow you to send and receive any type, it does this through reflection, but reflection can be bit wonky at times. The golang/protobuf package is now superseded by the google.golang.org/protobuf package, which doesn't even include the jsonpb package anymore.
If you want to send nested protobuffer events, you will have to marshal/unmarshal them yourself, and pub/sub them as proto/bytes json/string.
Personally, I write my own prototypes using an envelope with a custom decoder, and pub/sub them using the events interface with NATS as backend.

Ohhh.. I guessed that warning github.com/golang/protobuf is deprected can lead to problems...
Thank you so much, I'll rework my event handling according to this issue..

Please note that you need a later version of protoc as well, i use the following Dockerfile for a start:
FROM golang:1.19

# Install packages
RUN apt-get update && \
    apt-get --no-install-recommends --no-install-suggests --yes --quiet install \
        git-core ca-certificates make wget unzip && \
    cd /tmp && wget https://github.com/protocolbuffers/protobuf/releases/download/v21.5/protoc-21.5-linux-x86_64.zip && \
    unzip protoc-21.5-linux-x86_64.zip -d /usr/local/ && chmod +x /usr/local/bin/protoc

# Create appuser (/etc/passwd entry for the runner container)
RUN useradd appuser

# Install protoc-gen-go + protoc-gen-micro
RUN cd /tmp; go install<EMAIL_ADDRESS>go install<EMAIL_ADDRESS>
# Create the Volumes
RUN mkdir /microlobby && chown -R root: /microlobby && cd /microlobby

# Run as user from here
WORKDIR /microlobby

ENV GOPATH="/go"

VOLUME [ "/go", "/microlobby" ]

COPY ./scripts /scripts


deps: update ephemeral cluster to latest main

Overview

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

Codecov Report

Merging #695 (717cf3a) into main (d8679cc) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #695      +/-   ##
==========================================
+ Coverage   54.49%   54.53%   +0.03%
==========================================
  Files          49       49
  Lines       10305    10305
==========================================
+ Hits         5616     5620       +4
+ Misses       3820     3816       -4
  Partials      869      869

Impacted Files
Coverage Δ

block/manager.go
64.35% <0.00%> (-1.74%)
:arrow_down:

state/executor.go
69.17% <0.00%> (ø)

rpc/json/ws.go
61.90% <0.00%> (+7.93%)
:arrow_up:

types/validation.go
51.16% <0.00%> (+13.95%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Closing this. @tzdybal please reopen if needed.


scrot: 0.8 -> 0.8-17 (Debian patches)

scrot itself is unmaintained, but the Debian patches are widely adopted.
They fix some issues with the manpage, add --focused and --silent, and fix a minor bug.

tnx!


mat-slider thumbLabel wrong format

Bug, feature request, or proposal:
I experienced that while using the thumbLabel option on a mat-slider element, sometimes the label is doing some weird rounding. Instead of 57 for example, it shows 56.999999999999 and in the label I only see the nines. But only in the .mat-slider-thumb-label element is wrong, the slider component knows the value right (displayValue read-only property).
Here is a screenshot
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.0.1, Material 5.0.0-rc0, Windows10, TypeScript 2.4.2

Sorry, I had an error in my code.


plugin-publish: Plugin published but not activated

I've published a plugin using publishPlugins task, but for some reason activation failed and the plugin stuck in the state when it is uploaded but not activated.
> Task :infrastructure-publish:publishPlugins FAILED
Publishing plugin com.redmadrobot.publish version 0.16.2
Publishing plugin com.redmadrobot.publish-config version 0.16.2

Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':infrastructure-publish:publishPlugins'.
> Unauthorized!
    Login from command line using:
      gradle login
    or login and download user API keys on:
      https://plugins.gradle.org/user/login

After this error, I've restarted publishPlugins (without login) and "Unauthorized" error just gone. But now I get another error:
Execution failed for task ':infrastructure-publish:publishPlugins'.
> Failed to post to server.
  Server responded with:
  Plugin: 'com.redmadrobot.publish', version: '0.16.2' exists already. It was created: 2022-06-17 09:52:13.076

Expected Behavior

There is possibility to activate or delete uploaded version, via website, for example.
Current Behavior

I can't publish version again (it is already uploaded) as well as I can't delete the uploaded version because it is not activated.

Your Environment

com.gradle.plugin-publish:0.21.0

The only workaround I found - manually activate version adding the following code to the build script:
import com.gradle.publish.OAuthHttpClient
import com.gradle.publish.protocols.v1.models.publish.PublishActivateRequest

val client = OAuthHttpClient(
    /* baseUrl = */ "https://plugins.gradle.org",
    /* publishKey = */ property("gradle.publish.key").toString(),
    /* publishSecret = */ property("gradle.publish.secret").toString(),
)
val request = PublishActivateRequest("com.redmadrobot.publish", "0.16.2")
client.send(request)


docs: add a table of contents

I think this PR is relatively self explanatory. I don't think I can add anything of meaning here even if I tried

Hey, thanks Hamza 👈😎👈, this looks great.
I'm back to online school and am free rn If you'd like to chat.
Anyway, merging!

I think I might move the TOC to be in the #overview section, because it is quite long and takes up a lot of space at the top.


Update 'master' branch to CX version 1.6.2

post release version change from 1.6.1 to 1.6.2

Signed-off-by: Paul Elder<EMAIL_ADDRESS>

Addresses #345 on 'master' branch.


Prefer Direct mode over Gateway

With 2.4 release its mentioned that Direct mode access is supported now. Per docs its mentioned that Direct mode if supported by SDK should be preferred over gateway mode.
Wanted to check if its fine to always enable direct mode now or there are some other aspects pne need to consider before enabling this mode

@chetanmeh go with direct mode. if you face any issue we are here to help. :-)

In the next major version of the SDK, we'll be making Direct mode on by default (with opt-in to use Gateway mode instead).

Done in V3


Adds support for capturing i18n translation updates within a theme

References
Add references/links to any related issues or PRs. These may include:

Supports #1299

Description
This PR adds a script which can be used to merge i18n translation files from within a theme with the base/default translation files. This allows translation file updates to follow the same theme pattern as most other UI updates.
Note that this PR does not add the merge script into the build or deploy process. The included script will not be run unless it is executed directly. Once the script has been tested and accepted, it may be desirable to execute the script as part of the build, pointing to the configured theme(s).
Instructions for Reviewers
List of changes in this PR:

Adds a script that can be run at any time to merge two i18n translation files. It is assumed that the two files to be merged will have the same name and exist in different directories.
Updates package.json to make the script available under the name merge-i18n, following the pattern of the existing sync-i18n script.
Adds a simple translation customization example to the custom theme. Running the script and pointing to this file (as described in the comments within the script) will result in the English translation file (en.json5) being updated such that two label values are overridden.

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.
From within the top level /scripts directory, run yarn merge-i18n -s src/themes/custom/assets/i18n. The script will run and update the top-level en.json5 file in src/assets/i18n to replace the two labels included in the custom en.json5 file. Additional overrides can be added, as well as new label name/value pairs.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.

@bbranan and @artlowel :  I wonder if this should be documented briefly somewhere?  It seems very useful, but only if people are aware of it.  Maybe we should minimally add a section on "i18n management" to the README.md?
Or maybe it's better placed in the official docs here: https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization ? Perhaps with a note saying that the feature is coming in 7.1?
If possible, I'd appreciate help on the docs so that this feature isn't built & accidentally forgotten about. 😉

@tdonohue I added documentation for this in the official docs here: https://wiki.lyrasis.org/display/DSDOC7x/User+Interface+Customization#UserInterfaceCustomization-CustomizeUIlabelsusingInternationalization(i18n)files with a note about the merge-i18n script only being available in 7.1. I didn't see a place where it fit in the README.md (or in docs/Configuration.md), so didn't make any changes there.


feat: Lido staking

Summary

Closes: https://github.com/snapshot-labs/pitches/issues/45

How to test
Test space: sep:0x44C51B0f96029b5e03dBABe83849e26A1deCB66d
Example of executed proposal: https://bafybeiascrg3qrtipklsubtwtbdqk5zwrllbyp6vczrhp6y4bhpwvo5z6y.on.fleek.co/#/sep:0x44C51B0f96029b5e03dBABe83849e26A1deCB66d/proposal/9

Go to a space with treasury
It should always show the ETH token for eth and sepolia network, even without 0 balance
There should be a new STAKE icon next to the ETH token
Clicking on the STAKE button should open a modal, prompting for the amount of ETH to stake
Clicking on the "max" button will fill the max balance of the ETH token, available in the treasury
Clicking on "confirn" should redirect to the create proposal page, with the execution for Lido stake filled
You can edit the execution
The execution simulation should pass as long as the amount of staked token is valid (<= ETH balance)
Create a proposal, and vote for it to pass
It should execute the tx, and stake the given amount of ETH on Lido

Note
I am not familiar with execution strategies, and may have missed a few scenarios

@Sekhmet let's move on with code review, as there's a pitch this time.


METRON-211 Enable creation of new Kafka topics during deployment

METRON-211

Removed hadoop_setup role
Kafka topics needed by Metron are now created in a new metron-kafka role

The Kafka topics that are created are defined via properties.
Each Kafka topic can have unique retention, replication, and partition settings.
Using the metron_kafka_setup host group to target this role at hosts.

HBase tables needed by Metron are now created in a new metron-hbase role

The HBase tables that are created are defined via properties.
Using the metron_hbase_setup host groups to target this role at hosts.

Using separate host groups to target each role. This is more flexible than before as there may not be a single host with both Kafka and HBase clients installed.

👍 on this. Looks great to me.

+1 this looks good


banned 0 (trying to ban someone sometimes can ban a random person)

Bug
when banning someone it will sometimes ban a random person and not the person whos name was typed in
also trying to use the persons listing in the server using the status command does the same thing as well
the 0 id will also show up in the banlist
Steps to reproduce

in console type ban <player name>  example ban alexa15
console will output banned 0
random person will then be ban

Specifications

Northstar version: 1.4.0
Platform: steam

I think you have to ban by UID, typing status in console will print them
So a correct command would be ban 12

I'd like to confirm that this issue is consistent, on three separate servers I and BulletMemes have tried banning through a variety of means, but it always bans the person in slot 0 (whoever joined first).
Commands we have tried:
ban name
ban "name"
ban 1 (join order)
ban UID (unique id)
So far the only way to ban the correct person right now it seems is to somehow get their unique id, put it in banlist.txt and restart your server.

hey do we have any way to ban/remove people from a server while this gets fixed?
my server is becoming kinda toxic and i cant do anything about it

TEMP FIX: you can block connections with firewall
status will give player IPs on server console
VPNs are still a thing tho

i believe the issue with banning the 0th person was fixed here: https://github.com/R2Northstar/NorthstarLauncher/commit/bd2d7e3deadb3d9142630ae633a17b02e2b09fff

i think its still a bug
0 was banned is still happening
also not to be rude
but that was 16 days ago
if it was fixed then this issue would not be a thing

if it was fixed then this issue would not be a thing

this is in newest github commit, not current release

also not to be rude but that was 16 days ago if it was fixed then this issue would not be a thing

just to explain some more: on GitHub we track individual changes to the code, those are called commits. They are only code changes for now, for them to end up in your game files there needs to be a new release, thats when the code with all the newest changes is compiled and you can download it. Thats when fixes will actually arrive in your game/server. For now knowing it as fixed in a commit means "come next release this won't be a issue anymore"

ahh yea sorry im kinda new to GitHub thanks for the info
sorry


Keycloak Authentication

Added and modified several commands related to authentication to git services:

arc auth will open a browser window of a token specified in the arc config. The user can login there and a the credentials to a specific git service (like a gitlab instance) will be automatically stored using the git credential manager interface. The response from the token service additionally contains user metadata (name and email) used in signing commits. These will be stored in the arc config. (Command name deprecated, see this comment)
arc sync now checks whether this user metadata in the arc config matches the metadata in the git config. If not, it will abort and suggest to the user to run the following command:
arc config setgituser will take the git user metadata stored in the arc config and transfer it to the git config. Per default only the local git config of the repo will be overwritten. But this can be changed via --local and --global flags. Additionally, alternative name and email can also be provided

So a common workflow will look like this:
A user must use arc auth once for each distinct gitlab instance he wants access to. Then they can download arcs from that gitlab using arc get. If they want to store their git user metadata for each arc locally they then have to run arc config setgituser. Alternatively they can run it once globally after authentication. Afterwards they can use arc sync everytime they want to pull or push changes for this arc.
Edit: Pronouns
Edit2: Added reference to comment showing new command syntax

Interesting work! Could you elaborate briefly what the intended use cases are? It almost reads as if direct auth with some GitLab instance is now the preferred way of accessing ARCs, which I think should not be the goal, due to breaking the prior constraint of not taking advantage of any specific implementation (could have a GitHub repo or some other Git host).
I do think it's ok to have functions in the ARC commander to help users set up SSH keys / access tokens in specific circumstances, e.g. for DataPLANT HUB. From a security POV, I don't think it's wise to store user credentials inside an ARC?

Mini-nitpick: not all users are male, suggest using "they/them" as pronouns.

Thanks for your input!

Interesting work! Could you elaborate briefly what the intended use cases are? It almost reads as if direct auth with some GitLab instance is now the preferred way of accessing ARCs, which I think should not be the goal, due to breaking the prior constraint of not taking advantage of any specific implementation (could have a GitHub repo or some other Git host).

The arc auth functionality is not meant to directly connect to a GitLab instance. Sry that was a bit missworded. The goal here is to receive an access token from an authorization service. This will enable hopefully seemless authorization for the specific git service this token is meant to be used for.
The arc sync and arc get are not necessarily dependent on this. One could directly use these commands on e.g. an arc stored in Github or an GitLab instance.

I do think it's ok to have functions in the ARC commander to help users set up SSH keys / access tokens in specific circumstances, e.g. for DataPLANT HUB. From a security POV, I don't think it's wise to store user credentials inside an ARC?

The user name and password are only used in the browser window of the token service. The received username and access token  for the git service then get handed directly to git and not stored in the arc config. Stored in the arc config is only the the metainformation used to sign commits: Full name and e-mail of the user. But that is something anyone can see if he checks git locally or visits the git service online.

Mini-nitpick: not all users are male, suggest using "they/them" as pronouns.

Done ;)

New commit: Moved arc auth into a command tree for handling remote access to make its name more descriptive of what it actually does. The command now also takes the authentication protocol and the host address as arguments. E.g.:
arc remoteaccess accesstoken get --openid -s "https://keycloak.dev.bwsfs.uni-freiburg.de/auth/realms/sandbox"
I'm currently working on functionality to receive tokens via the oauth2 authentication protocol, which Github uses. This will then hopefully look like this:
arc remoteaccess accesstoken get --oauth2 -s "https://GitHub.com"

Will merge this for now, receiving access token trough oauth2 will be added in a later PR


Use stderr for error reporting

#14

The travis builds actually succeeded, regardless of their apparent status. So I will merge this.


Typeguard typeof !== with || sets never in "else"

🔎 Search Terms
typeguard typeof unknown not or never
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries with the keywords

⏯ Playground Link
~~https://www.typescriptlang.org/play?#code/FAMwrgdgxgLglgewgAhgBgBQEMBOBzALmUgGsIEB3CASiIGcYc4I9kBvYZL5OEZDVAE8ADgFMEfXKwCEAXlnIA5ACMECADaisERcmrtO3I1CQNkg5AqkBuQ0a45RMMDhSLFtowF9gd5CYgzAC9LZBs-R2dXJQ9gH1BIWEQUGABGbHwiUnIqWmQGJhYDI15+ITEJMPxkOQUVNU1tXQAfZvLxSWrapQLmPF19DntuALMLK3xPYeRIlzdY719jUxhkEIm8a2QAem3kACEAVQBxegALBDB1ABNkZVE7hq0IZt6i5gYtW8qIUQA3UQ4fjqOAkB7MVAAVmoESccxitni4Gg8CQqAAzBlCMQIGRKDR6Iw+sVuKUBDARB0qjJ5EpVBpnroAGRM9qVKQ1WmKN79PQk4ajVbjalTYazaLuUXIeLLQKrdYi2FReaI3zIpJomAAFixWVxOQJ+SJRSGpL45Mp7Oq8jq9MaOj5poFK3MoXC0xmcIlC24MpGLoV7u44pVcTViVRKUhupxeNyhMKrCdPHNbM6rBtdKeTWQrTT1MsXJ5A359kFro2UqMIYRfj9XHLgcmSvhkrDQA~~
💻 Code
removed
🙁 Actual behavior
line 18 "z" is "never"
🙂 Expected behavior
line 18 "z" is "boolean|string"
Additional information about the issue
No response

I don't see a correlation to https://github.com/microsoft/TypeScript/issues/44366 . It's not a bug - your test case is using typeof with two different values and an or condition. Everything is matched by that, even if - let's say - you pass a boolean to this function then it won't be matched by typeof arg !== 'boolean' but will be matched by the alternative condition: typeof arg !== 'string'


Complete model-model relationships

In the YACS app, a school has many departments, which have many courses, which have many sections.
Sections belong to a course
Courses belong to a department
A department belongs to a school
Implement these relationships in the models themselves.

See commit d7cb2fc20bddaa4bd1775f63b50ca7c61004a3b7


Add tooltip and focus ring to counterparty input field, when taker address not valid

https://www.figma.com/file/DTJwC2mQ9kvyjM0171tqHR/airswap-web?node-id=13189%3A15515&t=2hoAzepk26s6r1p4-4
Same tooltip as in https://github.com/airswap/airswap-web/issues/678
See also: https://github.com/airswap/airswap-web/issues/667#issuecomment-1310558246

Assigned this to helloitsme3


Make a SimpleSequenceGenerator for compas.datastructure.Assembly

AssemblySequenceGenerator

@jckenny59 even though it wouldn't be super elegant, we could also just allow caller to pass in an Assembly and then in case it's a TimberAssembly assign Steps to assembly.beams and otherwise to assembly.parts().
if isinstance(assembly, TimberAssembly):
    parts = assembly.beams
else:
    parts = assembly.parts()

for part in parts:
    # add part to building plan

@chenkasirer Very true this would for sure be an option. I am fine either way and can do it however you prefer. This way would be an even easier implementation on my side, because then I don't have to care if it is an Assembly or TimberAssembly... But I think if we want to move the AssemblySequenceGenerator out of Timbers sometime, then it also makes sense to do it separately. I can do either way, whichever you prefer!

@jckenny59 for sake of documentation and future reference: we agreed to do it the way of checking the type for now, so no new class.


WIP #153 material desing

Neste pull request foi feito:
Alterações no desing do app, foi escolhido Native-Base.
Issue #153

Pull Request Test Coverage Report for Build 343

1 of 18 (5.56%) changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 43.627%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Components/AGRButton.js
0
1
0.0%

src/Components/BotaoTransparente.js
0
1
0.0%

src/Screens/EditScreen.js
0
1
0.0%

src/Screens/LoginScreen.js
0
1
0.0%

src/Screens/ProfileManagerScreen.js
0
1
0.0%

src/Screens/NewManager.js
0
6
0.0%

src/Screens/InitialScreen.js
0
6
0.0%

Totals

Change from base Build 330:
0.8%

Covered Lines:
72

Relevant Lines:
160

💛  - Coveralls

Pull Request Test Coverage Report for Build 343

1 of 18 (5.56%) changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.8%) to 43.627%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Components/AGRButton.js
0
1
0.0%

src/Components/BotaoTransparente.js
0
1
0.0%

src/Screens/EditScreen.js
0
1
0.0%

src/Screens/LoginScreen.js
0
1
0.0%

src/Screens/ProfileManagerScreen.js
0
1
0.0%

src/Screens/NewManager.js
0
6
0.0%

src/Screens/InitialScreen.js
0
6
0.0%

Totals

Change from base Build 330:
0.8%

Covered Lines:
72

Relevant Lines:
160

💛  - Coveralls


New docs

Hi, @marcingrzejszczak. Any ETA on when this will be merged?

@sabbyanandan After Greenwich.SR1 next week we will branch for Hoxton work (based on boot 2.2.x). Then it can be merged.


feat: add jsx transfrom

Description

Additional context

What is the purpose of this pull request?

[ ] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the Pull Request Guidelines and follow the PR Title Convention.
[ ] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[ ] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

Current dependencies on/for this PR:

feat_migrate_optimizer_to_rollup

PR #3

PR #4

PR #5

PR #6

PR #7

PR #8

PR #9

PR #10   👈

This stack of pull requests is managed by Graphite.

Current dependencies on/for this PR:

feat_migrate_optimizer_to_rollup

PR #3

PR #4

PR #5

PR #6

PR #7

PR #8

PR #9

PR #10   👈

This stack of pull requests is managed by Graphite.


loader importModule api breaks webpack silently

Bug report

What is the current behavior?
Using this.importModule on a .js file causes webpack to exit without output and without error.
https://webpack.js.org/api/loaders/#thisimportmodule
1. Create a new project with the following 4 files:
loader.js
module.exports = async function (source) {
  const config = await this.importModule(this.rootContext + "/config.js");
  result = source.replace("hello", config.text);
  return result;
};

config.js (the file loader by loader.js)
export const text = "Greetings"

index.js (the file to be compiled)
console.log("hello WORLD!")

webpack.config.js
module.exports = {
    entry: "./index.js",
    module: {
        rules: [
        {
            test: /\.js$/,
            use: [
            {
                loader: require.resolve("./loader.js"),
            },
            ],
        },
        ],
    },
}

Run webpack
npx webpack
Result:
webpack-cli exits without any error and without generating any file
webpack-dev-server freezes in <i> [webpack-dev-middleware] wait until bundle finished: /

What is the expected behavior?

webpack should show an error or create a bundled file
importModule should provide an easy way to exclude the current loader

Other relevant information:
the problem seems to be an endless recursion:

webpack loads index.js
webpack calls loader.js
the loader calls importModule on config.js
import module calls loader.js
goto step 3

webpack --version

  System:
    OS: macOS 13.4
    CPU: (10) arm64 Apple M1 Max
    Memory: 140.73 MB / 64.00 GB
  Binaries:
    Node: 18.16.0
    Yarn: 1.22.19
    npm: 9.5.1
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 116.0.5845.187
    Chrome Canary: 119.0.6028.0
    Safari: 16.5
    Safari Technology Preview: 17.0
  Packages:
    webpack: ^5.88.2 => 5.88.2
    webpack-cli: ^5.1.4 => 5.1.4
    webpack-dev-server: ^4.15.1 => 4.15.1

Please let me know if I can be of any help to understand, reproduce or fix this problem

bu,p


Implementation details

It is probably too early to discuss this, but I think it is important to clarify early on. Where would the content of the standard library be implemented? Would they be part of JS engines, or part of the runtime on top?

So far, specifications that TC39 produces tend to be implemented in JS engines. I was imagining that this layering would likely continue in the future, but as you say, this is an implementation detail that we can't mandate in TC39. Do you see issues with implementing a standard library at the engine level?
However, there has been discussion about whether these libraries could be implemented in JavaScript. This has motivated a number of JavaScript language feature proposals, including #13 and https://github.com/domenic/proposal-function-prototype-tostring-censorship .

For the love of Turing implement it test-driven, in Rust, on Gihub, and with Microsoft, Google, Apple and Mozilla devs collaborating.

@littledan

For modules, my understanding was that there was ongoing work to let CJS modules import ESM modules as part of the modules effort, cc @guybedford

Yes, using import() but I think the question from @mcollina was about synchronous loading without a wrapper Promise. @mcollina does that sound correct? If so, it would mean ensuring engines are able to put expose these synchronously, but might be a host  / engine concern for implementation rather than a TC39 concern. This follows how https://github.com/nodejs/dynamic-modules/ is being driven by Node but intended to upstream to engines.
I like the approach of leaving this specific API as a host operation (could be a concrete op if desired?) since I think this topic will come up again regarding specifiers.

I don't see any particular barriers to figuring out a mechanism that JS's built-in modules could be imported as CJS modules. However, for scripts on the web, import() would be required.

For the record, I find it an absolute necessity for this proposal to be able to synchronously access any “builtin modules” in both Modules and Scripts, on the web and elsewhere - import() is not sufficient.

I think a way for loading those synchronously is necessary, yes.

@ljharb Why is synchronous loading from scripts necessary?

To ensure no other code has the ability to run before polyfilling and environment setup is completed - it requires ensuring that the setup entrypoint runs first, of course. Without synchronous loading from Scripts, my current understanding is that that list of 1 caveat would become longer.

I see, that makes sense. I'm curious about whether this comes up in other virtualization cases, cc @bakkot.

@ljharb it's weird we are requiring a built in module to be loaded from Script code and the way ES specs sync module loading is with modules. I respectfully disagree as I feel like await import() should be sufficient. Top-level await would not apply here but I'm already fine that we can handle a way to load these built-ins in Script.
It sounds like creating a way to sync load built-ins in Script is for a discussion apart of this proposal.

@leobalter it should be discussed (and added) before updating of this proposal to the next stage because a proper way of polyfilling modules is one of the main issues which should be resolved before the next stage. I (as polyfills author) know that await import() is not enough.

@leobalter if a new language feature is not going to be provided by a global, then providing it synchronously in Scripts is not a feature that should be taken away.
In other words, if this proposal wants to proceed as is, that would have to go along with a commitment to continue providing all new language features as globals or syntax - which i suspect isn’t the intention here.

if a new language feature is not going to be provided by a global, then providing it synchronously in Scripts is not a feature that should be taken away.

@ljharb I really don't see any solution for sync loading in Scripts that is not similar to the static import from Modules. FWIW, built-in modules might even be immediately available and just one (promise) tick away from Script modules.
IMO, the great part of having a built-in modules is to not pollute the global and load more content if necessary. If I really need a built-in in a code that is limited to Script records I imagine my requirement is specific enough to be wrapped in a promise or an async function. I can't see a reason yet to block scripts for sync loading.
Maybe this could be offered directly from Node as some extension for require(). To allow that we could just use the spec in a way it allow built-in modules being loaded from impl. defined forms. Would this work for you? Browsers might already do it using the script tag, setting a way to save the binding names.

it should be discussed (and added) before updating of this proposal to the next stage because a proper way of polyfilling modules is one of the main issues which should be resolved before the next stage. I (as polyfills author) know that await import() is not enough.

@zloirock It's hard for me to see it without more examples. You have more experience with polyfills  than I do. WRT discussing, I believe this is in the right track. We should discuss it here and during the meetings, regardless of stage advancement.

@leobalter see this note and comments from #2.

Why wouldn't this work?
<script>
// polyfill
import("std-lib-array").then(({ default: Array }) => {
  if (!Array.prototype.forEach) {
    Array.prototype.forEach = function (cb) {
      for (const el of this) cb(el);
    };
  }
});
</script>
<script>
// user code
import("std-lib-array").then(({ default: Array }) => {
  new Array(1, 2, 3).forEach(el => console.log(el));
});
</script>

the promises execution order is well-defined, so the polyfill will always run first.

I don’t agree that “polluting the global” is a problem that this proposal solves. All it does is create a new global namespace. The polyfilling requirements (and import maps) mean that user code is precisely as able to pollute built in specifiers as it is the global object.

@nicolo-ribaudo at least, because it could depend on some other standard library features and it's more async tasks. Like:
<script>
// polyfill
import("std-lib-array").then(({ default: Array }) => {
  if (!Array.prototype.forEach) {
    import("std-lib-object").then(({ default: Object }) => {
      Object.defineProperty(Array.prototype, 'forEach', { value: function (cb) {
        for (const el of this) cb(el);
      } });
    });
  }
});
</script>
<script>
// user code
import("std-lib-array").then(({ default: Array }) => {
  new Array(1, 2, 3).forEach(el => console.log(el)); // missed
});
</script>

I don’t agree that “polluting the global” is a problem that this proposal solves. All it does is create a new global namespace. The polyfilling requirements (and import maps) mean that user code is precisely as able to pollute built in specifiers as it is the global object.

A key difference between globals and modules is that modules may differ per callsite importing them such as using import maps or a loader, globals do not have different values for different locations accessing them.

Not without wrapping and shadowing, that is true.
However, no such capability exists in the language - import maps isn’t a language proposal.

@ljharb

import maps isn’t a language proposal.

That isn't relevant? The language explains that hosts can do it by any means they see fit.

@bmeck I think it's relevant in that adding new API in the language must provide a language feature to add/delete/repair/polyfill it - it's not sufficient to just hope that hosts will all provide a mechanism.

@ljharb that wasn't related to my conversation? I'm pointing out they are very much not the same.

@bmeck i agree that https://github.com/tc39/proposal-javascript-standard-library/issues/41#issuecomment-484605279 is a difference that this proposal provides - but it does not contradict https://github.com/tc39/proposal-javascript-standard-library/issues/41#issuecomment-483817859.

@ljharb it isn't meant to contradict but point out that the idea that polyfilling is prevented by this is false. Hosts are allowed to do all sorts of things including preventing polyfilling on their own. The host has the power to ensure that polyfilling remains, but in this case is able to do so in a way that does not force a shared global namespace be created for modules. Forcing hosts to have polyfilling work is not present even in the current scenario and can be seen where embedded does freeze the global before any user code can be run. I do not see how the ability to polyfill is harmed by this proposal as the ability to polyfill is not guaranteed to begin with.

Hosts aren't permitted to make ES globals nonconfigurable or immutable - so in fact the current state of the language does force hosts to support polyfills/shims, as well as various security use cases (deniability).

@ljharb
In InitializeHostDefinedRealm

"Create any implementation-defined global object properties on globalObj."

Does not prevent replacing properties nor exotic globals from altering things.
In RunJobs

In an implementation-dependent manner, obtain the ECMAScript source texts (see clause 10) and any associated host-defined values for zero or more ECMAScript scripts and/or ECMAScript modules.

Which could run host-defined code prior to user code that does any sort of global mutation.
What do you mean that they cannot make globals non-configurable or immutable?
Deniability can still be achieved with the exotic globals or through usage of other means like creating Realms/Compartments even with all of that in place. In addition, even when talking in the Realms calls the ability to deny access is generally not universal and the idea of a root realm commonly comes up. At some level the host provides all the capabilities including globals and module loading to that root Realm. The ability to virtualize module specifier->namespace mappings is missing from the language but does not mean that the ability is unable to be provided by hosts. Similarly to how hosts can deny globals from users as well, the ability to virtualize everything is not guaranteed.

It definitely does prevent that - "create" means additive, the host is not permitted to alter mandated characteristics of the ES globals, which includes their property descriptor.

@ljharb even if that quote is meant to be purely additive (I disagree on term litigation here), SetDefaultGlobalBindings does fire traps that can modify things on the exotic globals provided by hosts.


How to contribute to gh-pages

At https://handsontable.github.io/angular-handsontable/support you've written that we should always target our PRs at the develop branch. This is a good approach when doing changes to the library itself, but doesn't really make sense if we want to fix some things in the documentation, located in the gh-pages-src branch.
Therefore: How should we create a PR for changes in the documentation?

Hi @madoar, You're right. We didn't wrote how to contribute in documentation.


Support trailing whitespace

For example, I use
    <dict>
      <key>name</key>
      <string>TrailingWhitespace</string>
      <key>scope</key>
      <string>trailingwhitespace</string>
      <key>settings</key>
      <dict>
                <key>foreground</key>
                <string>#222222</string>
      </dict>
    </dict>

It would be nice if this was included by default, so that updates don't break it / or I don't have to update manually. Of course, name can be changed.

closing based on age, but I'd still be happy to review a pr for this, especially if it's a configuration option for the user.


ENOENT Error upon start

Error: ENOENT: no such file or directory, stat '/app/dist/views/index.html' is causing the application not to function correctly (not start).

Install instructions updated to add the missing "build" step with gulp in README which caused the errror.
Pull the project again, and then do:
npm install
npm run gulp build
npm start
The app should start normally provided you have the required .env file


More verbosity with "Attempted to dereference a null autowired field"

I get this error frequently, but the message is very unhelpful. Surely with RTTI we can at least print out a string representation of the offending type?

:+1: I am sure there should at least be a way to communicate the type?

This would be a nice to have feature, but I don't really blame autowiring for lacking it.
I mean, even without autowiring if you do nullptr->Func() you get a segfault (i.e. the error message is unhelpful) and may have to resort to running in gdb or the Visual Studio debugger to get your stack trace and find where your obj->Func() should be something like obj && obj->Func(). But that's what we get for dereferencing a null object.

@jdonald definitely agree, I just hope that since the autowiring syntax includes a template<T> parameter, it would help if the exception message could classify what that template type is.

Yes, null objects should not be dereferenced. But typically they come as a result of some high level code reshuffling. The specific example I ran into today only happens on Mac and Linux so I don't have a local machine where I can debug it.
It could, for instance, be caused by something as subtle as calling Autowired when I'm in the wrong context, which leads me to assume that the object exists.

Have a look at the above PR, let me know if this is what you want.


Home Assistant 2023.3.0 - 0.6.0 Home Connect Alt issue with configuration

Describe the bug
The new version of Home Assistant (2023.3.0) breaks Home Connect Alt integration (0.6.0). I got a configuration issue with it.
Debug log
When checking configuration trought Home Assistant -> Developers Tools -> Yaml i got an error with home-connect-async.
Integration error: home_connect_alt - Requirements for home_connect_alt not found: ['home-connect-async==0.7.5'].

+1

@DimitriTeerink @grego1981 are you sure you've updated to the latest version?
I also had this issue, but updating to 0.6.0 fixed it for me

Same for me, I think since the update to 0.6.0 while also updating HACS itself and some other integrations.. My HA now refuses to restart because of the validation error. I'm tempted to try to restart my server in the hope that that will magically solve any problem but I'm not sure what will happen then.

Just updated, then disabled the integration from the config yaml and from integrations, restarted the HA and re enabled it in both places. Everything now works as before!

Everything ok here also after a reboot of my server.

A manual restart of HA is required. The easiest way to do that is through the command line.


download fescar-develop source build not pass

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
the source build not pass
com.alibaba.fescar.core.service.ServiceManagerStaticConfigImpl.java on 66 line StringUtils.isEmpty method not found
branch: develop
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)

xxx
xxx
xxx

Ⅴ. Anything else we need to know?
your can use org.apache.commons.lang.StringUtils.isEmpty or com.alibaba.fescar.common.util.StringUtils.isNullOrEmpty
Ⅵ. Environment:

JDK version : 1.8
OS : windows
Others:

What commands do you use to build it?

try this
mvn clean install -DskipTests -U

@xingfudeshi mvn clean install -DskipTests

@xingfudeshi mvn clean install -DskipTests

thanks for the feedback.i just used the commands you've provided to build Fescar.and it passed.
Please pull the latest source code,and try it again.

i will close this issue.if you have further question with build problem,please comment here,or open a new issue.thanks.


Food spawning at the edge

Disallow food from spawning on the edge of the environment.
Estimated time: 10 m.

Closed by 12cac3e.


epic(esl-select): reworked using esl-popup (#1321)

Closes: #1321
Closes: #1421

Accepted for nearest versions

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature Request: Add a way to start the app after every update.

Is your feature request related to a problem? Please describe:
After every update, the app is closed (for obvious reasons) and I have to start it again everytime from the Start menu.
Describe the solution you'd like:
Please add a way to start the app after every update.

Hey @Cyberdroid1,
I remember sending you links to the MS documentation for this feature on Telegram.
Could you resend me the links? I forgot the name of the API 😅.

Sorry, I think our chat had got cleared some time back. The links might have been swept away with that...

I think could hell us https://www.codeproject.com/articles/74249/application-recovery-and-restart-c-quick-reference

https://docs.microsoft.com/en-us/windows/apps/desktop/modernize/desktop-to-uwp-extensions#restart-automatically-after-receiving-an-update-from-the-microsoft-store
Got it thanks @Cyberdroid1!

Got another one with complete code
https://docs.microsoft.com/en-us/windows/msix/non-store-developer-updates#automatically-restarting-your-app-after-an-update
😁

Did my best pals - 981017e4f726211e1c8c95188fdcf64f40aab15d
I'm still not 100% sure if this would work perfectly. As the app sometimes starts without a package identity when restarted programmatically [other than the startup task and manual launch by the user] some APIs misbehave quite often and may cause instabilities.
I don't know if this will work or not. We may need to wait till v0.8.3 (because this feature will be added to v0.8.2 and will only be valid in future updates) is released and updated via the Store to actually see if this works.
To check its validity it will show a message stating "App update successfully!" [only for v0.8.3 just to check if it works. I will remove this message in the future versions].
Let's hope it works 😅.


Latvian Language request

Description
Hello. I would like to help translate Homarr in Latvian (LV). Can the Latvian language be added in Crowdin?
Priority
Medium (Would be very useful)

Hi, thank you for your issue.
Please message us on Discord for this matter.
Make sure that you've read the guidelines for translations on our documentation:
https://homarr.dev/docs/community/translations

Added via #1027


Not able to view Signatures in PDF with latest PDF.js - where to set enableSignature in recent pdf.js

Attach (recommended) or Link to PDF file here:
10016583 Lake Elsie RFDS v11(Crump).pdf
Configuration:

Web browser and its version: chrome 110.0.540
Operating system and its version: Windows
PDF.js version: latest
Is a browser extension:

Steps to reproduce the problem:

Opening this file , in PDF.js viewer. it does not show the signature.
We used to add enableSignature = true, in default_preferences.json to get this working.

With recent pdf.js, we want to know how to add default preferences to enableSignature. Most of the preferences such as disableFontFace , disableRange are all now added to the getDocument task itself.
What is the expected behavior? (add screenshot)
What went wrong? (add screenshot)
Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

PDF.js version: latest

Please provide an actual version number, since latest unfortunately isn't helpful.

Opening this file , in PDF.js viewer. it does not show the signature.

Since some time back we render signatures, however we don't validate them. As the following screen-shot shows, when opening your PDF document with e.g. https://mozilla.github.io/pdf.js/web/viewer.html there's a signature rendered on the first page:

We used to add enableSignature = true, in default_preferences.json to get this working.

Sorry, but no such option/preference has ever existed and you must have been using e.g. a custom version of the viewer.

Finally, please see https://github.com/mozilla/pdf.js/blob/master/.github/CONTRIBUTING.md (emphasis mine):

If you are developing a custom solution, first check the examples at https://github.com/mozilla/pdf.js#learning and search existing issues. If this does not help, please prepare a short well-documented example that demonstrates the problem and make it accessible online on your website, JS Bin, GitHub, etc. before opening a new issue or contacting us in the Matrix room -- keep in mind that just code snippets won't help us troubleshoot the problem.


New doc Schema for 1.5

Description
Adds Schema.org declarations to doc pages for richer search results.
Testing
I've tested it manually by changing the file in my local copy of the website repo and ran the resulting schemas through Google's Structured Data Testing Tool.

I've updated the code with @LukeShu 's suggestions and took the opportunity to abstract the complex Schema logic into a custom React hook (useDocSEO) to make organization easier. In the future I'd suggest moving this hook into its own file to make doc-page.js more approachable for contributors.
If you're both satisfied with the end result, let me know and I'll update the other branches for other releases 😉
PS: This was my first ever thorough code review. As someone who rarely works with teams, your feedback has been immensely valuable and the experience was very enriching for me. Thank you so much for the patience and level of detail, I'm striving to meet your expectations!

@LukeShu build is fixed! Let me know if you need anything else to merge this :)


bpftune: unstable-2023-12-20 -> 0-unstable-2024-05-17

Diff: https://github.com/oracle/bpftune/compare/0e6bca2e5880fcbaac6478c4042f5f9314e61463...83115c56cf9620fe5669f4a3be67ab779d8f4536
Description of changes
Fixes https://github.com/NixOS/nixpkgs/issues/313204

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test bpftune


modernize MolViewer

use subprocess instead of os.system thread
automatically start headless server
stop() method
stop server if instance goes out of scope
display: wait for image, show progress bar

Minimal example to show a ray traced image:
from ipymol import viewer as pymol
pymol.fetch('3odu')
pymol.display()

thanks @cxhernandez for merging!


Align istioctl get with kubectl and add --all-namespaces flag

Revert https://github.com/istio/istio/issues/4325 to align istioctl get with kubectl get. By default istioctl get will return list of resources by type in the specified namespace (defaults to default namespace). The --all-namespaces` flag can be used to retrieve all resources of a specific type.
Fixes https://github.com/istio/istio/issues/5870

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS [ayj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @yangminzhu @SeriyBg

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
9a25e47c620d6119106af7c27cbfb651983bfdb7
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
9a25e47c620d6119106af7c27cbfb651983bfdb7
link
/test istio-unit-tests

prow/istio-presubmit.sh
9a25e47c620d6119106af7c27cbfb651983bfdb7
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
c5d6de2bb11501ecb79a163d192bb3cbeb4f3c3d
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
c5d6de2bb11501ecb79a163d192bb3cbeb4f3c3d
link
/test istio-pilot-e2e

prow/istio-unit-tests.sh
1cc2ad90d40f3fc4d1f0692099408b94f3ea4e5e
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
1cc2ad90d40f3fc4d1f0692099408b94f3ea4e5e
link
/test istio-unit-tests

prow/istio-pilot-e2e.sh
1cc2ad90d40f3fc4d1f0692099408b94f3ea4e5e
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
71812cd4f1426df0e3c67d5faede7d7de1a41572
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: ayj, gyliu513
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

istioctl/OWNERS [ayj]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ayj: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e.sh
71812cd4f1426df0e3c67d5faede7d7de1a41572
link
/test istio-pilot-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


[stable/logstash] Add nodePort configuration

Statically assign nodePort
Signed-off-by: Johnathan Rodgers<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[ ] DCO signed
[ ] Chart Version bumped
[ ] Variables are documented in the README.md

/lgtm


Forward type to implicit casts if part_of_explicit_cast

Currently, casts are not added in clang AST translation except in a couple special cases, seemingly because adding them would break existing checkers. This change fixes many of the casting cases that used to result in information loss without adding Exp.Cast expressions. When an ImplicitCastExpr has the part_of_explicit_cast bit set, it will be forwarded the type of its outer cast. This is particularly useful with LValueToRValue casts because it means the dereference assignment generated has the correct type.
Here are a couple cases where this prevents information loss (included as unit tests):
void integral_cast() {
    int a;
    int b = ((char) a) + 2;
}

struct object {
    int field;
};

void pointer_cast() {
    void *obj;
    int f = ((struct object *) obj)->field;
}

Here are the clang ASTs for the casts:
|-ImplicitCastExpr 0x55e4e4986500 <col:13, col:22> 'int' <IntegralCast>
| `-ParenExpr 0x55e4e49864c0 <col:13, col:22> 'char'
|   `-CStyleCastExpr 0x55e4e4986498 <col:14, col:21> 'char' <IntegralCast>
|     `-ImplicitCastExpr 0x55e4e4986480 <col:21> 'int' <LValueToRValue> part_of_explicit_cast
|       `-DeclRefExpr 0x55e4e4986450 <col:21> 'int' lvalue Var 0x55e4e4986350 'a' 'int'

`-MemberExpr 0x55e4e49869a8 <col:13, col:38> 'int' lvalue ->field 0x55e4e4986630
  `-ParenExpr 0x55e4e4986988 <col:13, col:35> 'struct object *'
    `-CStyleCastExpr 0x55e4e4986960 <col:14, col:32> 'struct object *' <BitCast>
      `-ImplicitCastExpr 0x55e4e4986948 <col:32> 'void *' <LValueToRValue> part_of_explicit_cast
        `-DeclRefExpr 0x55e4e4986858 <col:32> 'void *' lvalue Var 0x55e4e4986758 'obj' 'void *'

Without this change, the integral_cast assignment has nothing indicating a got truncated to a char:
n$0=*&a:int
*&b:int=(n$0 + 2)

With this change, the assignment has the correct type:
n$0=*&a:char
*&b:int=(n$0 + 2)

The pointer_cast assignment without this change does not give any information about what type the field access is on:
n$0=*&obj:void*
n$1=*n$0.field:int
*&f:int=n$1

(edit: I realized that there actually is a typ stored in Exp.Lfield, but it only gives the struct type, not the pointer type, so it's still not ideal. For example, here you'd only have void* and object, and would have to reconstruct the object* yourself. So it's not strictly information loss, but this is much nicer.)
After this change, it has the correct type, allowing checkers to do things with that information:
n$0=*&obj:object*
n$1=*n$0.field:int
*&f:int=n$1

Thank you for your contribution! Sorry it took so long to get merged, just slipped out of my mind over the summer...


DBT install fails due to incorrect constraint

According to the recommended constraints file (https://raw.githubusercontent.com/apache/airflow/constraints-2.6.3/constraints-3.10.txt) the sqlparse==0.4.4. When I perform a pip3 list inside MWAA (v 2.6.4) it shows sqlparse==0.4.3.
This causes an error when trying to install other libraries (specifically dbt_core==1.5.0) on the local installation that don't exist when installing in the cloud.
A workaround will be to implement a bespoke constraints file which overrides the constraint but this is prone to on-going maintenance issues and it would be great to have this solved without having to replicate the majority of the file.

How did you fix this issue?


New phone number format need to be added

Hello. Forgive my poor English.
Recently, I use the repo intl-tel-input which alias libphonenumber,  and i found that phone num like this<PHONE_NUMBER>2 (start with 173) can't pass the validate, this type of number started with '173' is added by China Network Operator.
So I use the demo and judge the number, get result as follow:

Thanks.

@humanPursuit
Thank you for taking the time to improve libphonenumber!
We are able to connect to number<PHONE_NUMBER>2.
We have found official evidence as well for this mobile range.
http://www.itu.int/oth/T020200002B/en
Please see our contribution guidelines for future use.
We've accepted this issue and will fix this in an upcoming release.

@penmetsaa seems this issue still exists in version 7.2.5

pn = phonenumbers.parse('+8617301201883')
phonenumbers.is_possible_number(pn)
True
phonenumbers.is_valid_number(pn)
False

any idea if this will be fixed in next version? Thanks.

@humanPursuit
We are still working on this issue . Will keep you posted with all further updates .

@padmaksha  thanks a lot for the reply. Please keep me updated.

@humanPursuit and @judyyanluo
Fixed in release 7.2.8: https://libphonenumber.appspot.com/phonenumberparser?number=17321044282&country=CN


DBZ-3610 Support for grant/revoke role

https://issues.redhat.com/browse/DBZ-3610
Upstream PR - https://github.com/antlr/grammars-v4/pull/2231

Thx!


Error when using pug template

Describe the bug
I'm trying to run the plugin on a Quasar/Vite app. But if I use pug templates I get the following error and nothing is rendered.

This error don't appears when I'm using HTML templates.
Reproduction
https://github.com/marco-quintella/youmove-frontend/tree/vue-plugin-demo
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 Intel(R) Core(TM) i9-10980HK CPU @ 2.40GHz
    Memory: 46.12 GB / 63.79 GB
  Binaries:
    Node: 16.15.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - C:\Program Files\nodejs\yarn.CMD
    npm: 8.17.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (105.0.1343.53)
    Internet Explorer: 11.0.22000.120

Used Package Manager
pnpm
Logs

runtime-core.esm-bundler.js:38 [Vue warn]: Component is missing template or render function.
  at <App>
| warn2 | @ | runtime-core.esm-bundler.js:38
-- | -- | -- | --
  | finishComponentSetup | @ | runtime-core.esm-bundler.js:7325
  | setupStatefulComponent | @ | runtime-core.esm-bundler.js:7221
  | setupComponent | @ | runtime-core.esm-bundler.js:7143
  | mountComponent | @ | runtime-core.esm-bundler.js:5495
  | processComponent | @ | runtime-core.esm-bundler.js:5470
  | patch | @ | runtime-core.esm-bundler.js:5060
  | render2 | @ | runtime-core.esm-bundler.js:6231
  | mount | @ | runtime-core.esm-bundler.js:4424
  | app.mount | @ | runtime-dom.esm-bundler.js:1606
  | start | @ | client-entry.js:131
  | await in start (async) |   |
  | (anonymous) | @ | client-entry.js:160
  | Promise.then (async) |   |
  | (anonymous) | @ | client-entry.js:149
  | Promise.then (async) |   |
  | (anonymous) | @ | client-entry.js:142

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

You linked a full repo instead of a minimal reproducible.
Please try to reproduce a minimal example e.g. at StackBlitz: https://vite.new/


Reviewing against awesome list reqmts

This is a review as part of the awesome list request that each list look to review two other lists in order to be added. These are good-faith points which fall into the following two categories:

copyedit,
all entries must have comments

You have a very detailed list. Regards, Mike @thekitty, as part of efforts for Adafruit CircuitPython

Resource description

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

[ ] I have read and understood the Contribution Guidelines
[ ] I am making an individual pull request for each suggestion
[ ] I have used the correct spelling and capitalisation for BBC micro:bit, micro:bit, and Micro:bit Educational Foundation (resource title could be excluded if there is a good reason)
[ ] The content linked is in English, or it contains an English translation
[ ] I have added the new entry to the bottom of its the category
[ ] I have used the following format:

- [Resource Title](link) - Resource short Description (2 lines or less in total)

Hi @TheKitty,
By any chance did you mean to send this PR to http://github.com/carlosperate/awesome-microbit?
It ended up as a PR from your branch to your master.
I'd love to merge your changes upstream if that's okay with you!

it was meant to assist in getting awesome micro:bit ready for the awesome
list
On Fri, Aug 17, 2018 at 10:00 AM, Carlos<EMAIL_ADDRESS>wrote:

Hi @TheKitty https://github.com/TheKitty,
By any chance did you mean to send this PR to http://github.com/
carlosperate/awesome-microbit
https://github.com/carlosperate/awesome-microbit?
It ended up as a PR from your branch to your master.
I'd love to merge your changes upstream if that's okay with you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheKitty/awesome-microbit/pull/1#issuecomment-413875077,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0scNRMsjaUbkHhSyjEu7RyZtkEcA9Uks5uRsxpgaJpZM4Vqmmk
.

Does that mean somebody else will submit a PR to the repo? Or should I manually patch it?

Thanks @TheKitty, I have applied some of these in https://github.com/carlosperate/awesome-microbit/commit/ffa7903f73b9571c7c47c16a89dff9a46a004cde.

No problem, look forward to seeing your list up.
On Mon, Aug 20, 2018 at 1:10 PM, Carlos<EMAIL_ADDRESS>wrote:

Thanks @TheKitty https://github.com/TheKitty, I have applied some of
these in carlosperate@ffa7903
https://github.com/carlosperate/awesome-microbit/commit/ffa7903f73b9571c7c47c16a89dff9a46a004cde
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/TheKitty/awesome-microbit/pull/1#issuecomment-414392314,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0scMXdOFJuJbFJz3u_Bmkv0e5shN4dks5uSu2egaJpZM4Vqmmk
.


define appr interface and wire with chart resource

Towards https://github.com/giantswarm/giantswarm/issues/1902
Connects appr service and chart resource. I've added also an interface to appr in order to have both components properly decoupled.

Actually the mock is already there :) Nice!

For me, the previous name makes more sense because we are getting the release that has been pushed to the specified channel.

Thanks a lot for pointing it out, previously the client was getting information about the package without including channel info, that's why the returned release was the default one, which led me to rename the method. I've changed it back the GetRelease and added channel info to the query, PTAL.


WIP: immutable put-get

tests to do

there was a race issue, which is solved in #8f1932b

This is currently non-functional but it seems like it might be an issue with dht-rpc (or otherwise I'm missing something).
node examples/put-get.js

Results in
  if (err) throw err
           ^

Error: No close nodes responded
    at QueryStream._finalize (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:220:20)
    at QueryStream._sendUpdate (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:190:10)
    at QueryStream._moveCloser (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:203:12)
    at QueryStream._read (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:235:39)
    at QueryStream._readMaybe (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:227:70)
    at QueryStream._onresponse (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/query-stream.js:93:12)
    at IO._finish (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/io.js:132:9)
    at IO._onmessage (/Users/dave/code/hyperswarm/dht/node_modules/dht-rpc/lib/io.js:104:14)
    at Socket.emit (events.js:198:13)
    at UDP.onMessage [as onmessage] (dgram.js:628:8)

I get the same error when copy pasting the instructions for creating commands under usage in https://github.com/mafintosh/dht-rpc readme - this what makes me think it's a dht-rpc issue

closing for now, taking another run


ValueError in viz_map.py

Line 76 of the code produces a "shape mismatch" message. This appears to caused by preds.shape being too large (499385,256) to be pasted into op_im (shape: (499385,)).  Which slice of preds is the correct one to use?

Hi there.
Can you confirm that you have not modified this line:
https://github.com/elijahcole/sinr/blob/df676beece3234382d9623530d6bfef5ee9c699a/viz_map.py#L65
preds should have the same number of entries as rows in locs_enc and have a single value for each entry.

Hello,
I didn't modify any of the code. After replacing the faulty imagecodecs
package I opened a terminal from Anaconda and ran viz_map code in the pdb
debugger. Here's the output - with irrelevant lines removed.
(GeoModel) D:\Data\PyCharm\sinr-main>python -m pdb viz_map.py
--taxa_id=870009

d:\data\pycharm\sinr-main\viz_map.py(1)()
-> """
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(6)()
-> import torch

....
-> main(eval_params)
(Pdb) s
--Call--

d:\data\pycharm\sinr-main\viz_map.py(18)main()
-> def main(eval_params):
....

Loading taxa: 870009
...

d:\data\pycharm\sinr-main\viz_map.py(61)main()
-> locs_enc = enc.encode(locs).to(eval_params['device'])
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(64)main()
-> with torch.no_grad():
(Pdb) locs_enc.shape
torch.Size([499385, 4])

(Pdb) n

d:\data\pycharm\sinr-main\viz_map.py(65)main()
-> preds = model(locs_enc, return_feats=False,
class_of_interest=class_of_interest).cpu().numpy()
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(68)main()
-> if eval_params['threshold'] > 0:
(Pdb) preds.shape
(499385, 256)
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(74)main()
-> if not eval_params['disable_ocean_mask']:
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(75)main()
-> op_im = np.ones((mask.shape[0] * mask.shape[1])) * np.nan  # set to NaN
(Pdb) n
d:\data\pycharm\sinr-main\viz_map.py(76)main()
-> op_im[mask_inds] = preds
(Pdb) n
ValueError: shape mismatch: value array of shape (499385,256) could not be
broadcast to indexing result of shape (499385,)
(Pdb) q

Cheers,
Martin
On Sun, 24 Sept 2023 at 18:53, Oisin Mac Aodha @.***>
wrote:

Hi there.
Can you confirm that you have not modified this line:
https://github.com/elijahcole/sinr/blob/df676beece3234382d9623530d6bfef5ee9c699a/viz_map.py#L65
preds should have the same number of entries as rows in locs_enc and have
a single value for each entry.
—
Reply to this email directly, view it on GitHub
https://github.com/elijahcole/sinr/issues/9#issuecomment-1732630709, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A5UY5LWTPOPDX2LPXZIWY7TX4BXP3ANCNFSM6AAAAAA5FCKB5U
.
You are receiving this because you authored the thread.Message ID:
@.***>

The code here
https://github.com/macaodha/geo_prior/blob/b0c761712a0aeced56eba86dd19eda657fbe895a/geo_prior/models.py#L58
uses "torch.matmul(x, ...)" rather than the equivalent line in this package which uses "x * ...". Is that significant?

Thanks for flagging this. Yes, it was an issue with how "*" is treated in the version of torch specified in the requirements. Should be fixed with the latest commit.


Any updates on when the code will be released ?

sorry for the delay! the code for both DA-score and Eval&Refine based iterative refinement is now online.


Updating model object

how can we update the model value. Im doing it in version5 with spread operator.but with v6 im getting model is a read only property error. Sample code with v5 as follows:
this.model= {...this.model, email: 'email'}

Angular version: 14
Formly version: 6

Hi,
could you please provide a reproduction, you can use our starter example:
https://stackblitz.com/edit/ngx-formly-ui-bootstrap
Thanks!

I have added the example in onsubmit function https://stackblitz.com/edit/ngx-formly-ui-bootstrap-4ugz7j?file=src/app/app.component.ts

@aitboudad i created a similar case, could you pplase check the following fork and help?
https://ngx-formly-ui-bootstrap-wwudsq.stackblitz.io
fork

@aitboudad i'm trying to achieve something like this: https://github.com/ngx-formly/ngx-formly/issues/1116#issuecomment-412297872
Added stackblitz as well, could you please help?

Duplicate of #3607


Cluster failed to start with 2.18 RC5 docker image

Using self-signed certificates, working fine for 2.17, but when creating cluster with 2.18 RC5 docker image, the cluster failed to start with the following error, am I missing anything?
java.lang.IllegalStateException: failed to load plugin class [org.opensearch.security.OpenSearchSecurityPlugin]
Likely root cause: java.security.cert.CertificateExpiredException: NotAfter: Thu Sep 28 04:20:03 UTC 2023
	at java.base/sun.security.x509.CertificateValidity.valid(CertificateValidity.java:182)
	at java.base/sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:534)
	at java.base/sun.security.x509.X509CertImpl.checkValidity(X509CertImpl.java:507)
	at org.opensearch.security.ssl.config.KeyStoreUtils.validateKeyStoreCertificates(KeyStoreUtils.java:147)
	at org.opensearch.security.ssl.config.TrustStoreConfiguration.createTrustManagerFactory(TrustStoreConfiguration.java:61)
	at org.opensearch.security.ssl.SslConfiguration.lambda$buildServerSslContext$0(SslConfiguration.java:84)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:571)
	at org.opensearch.security.ssl.SslConfiguration.buildServerSslContext(SslConfiguration.java:73)
	at org.opensearch.security.ssl.SslContextHandler.<init>(SslContextHandler.java:42)
	at org.opensearch.security.ssl.SslContextHandler.<init>(SslContextHandler.java:38)
	at org.opensearch.security.ssl.SslSettingsManager.lambda$buildSslContexts$0(SslSettingsManager.java:96)
	at java.base/java.util.Optional.ifPresentOrElse(Optional.java:196)
	at org.opensearch.security.ssl.SslSettingsManager.buildSslContexts(SslSettingsManager.java:95)
	at org.opensearch.security.ssl.SslSettingsManager.<init>(SslSettingsManager.java:80)
	at org.opensearch.security.ssl.OpenSearchSecuritySSLPlugin.<init>(OpenSearchSecuritySSLPlugin.java:249)
	at org.opensearch.security.OpenSearchSecurityPlugin.<init>(OpenSearchSecurityPlugin.java:318)
	at java.base/jdk.internal.reflect.DirectConstructorHandleAccessor.newInstance(DirectConstructorHandleAccessor.java:62)
	at java.base/java.lang.reflect.Constructor.newInstanceWithCaller(Constructor.java:502)
	at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:486)
	at org.opensearch.plugins.PluginsService.loadPlugin(PluginsService.java:796)
	at org.opensearch.plugins.PluginsService.loadBundle(PluginsService.java:744)
	at org.opensearch.plugins.PluginsService.loadBundles(PluginsService.java:545)
	at org.opensearch.plugins.PluginsService.<init>(PluginsService.java:197)
	at org.opensearch.node.Node.<init>(Node.java:523)
	at org.opensearch.node.Node.<init>(Node.java:450)
	at org.opensearch.bootstrap.Bootstrap$5.<init>(Bootstrap.java:242)
	at org.opensearch.bootstrap.Bootstrap.setup(Bootstrap.java:242)
	at org.opensearch.bootstrap.Bootstrap.init(Bootstrap.java:404)
	at org.opensearch.bootstrap.OpenSearch.init(OpenSearch.java:181)
	at org.opensearch.bootstrap.OpenSearch.execute(OpenSearch.java:172)

@ruanyl I wasn't able to reproduce with RC5 docker image listed here.

 Expand to see docker-compose.yml I used
version: '3'
services:
  opensearch-node1:
    image: opensearchstaging/opensearch:<IP_ADDRESS>66
    container_name: opensearch-node1
    environment:
      - cluster.name=opensearch-cluster
      - node.name=opensearch-node1
      - discovery.seed_hosts=opensearch-node1,opensearch-node2
      - cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
      - bootstrap.memory_lock=true # along with the memlock settings below, disables swapping
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m" # minimum and maximum Java heap size, recommend setting both to 50% of system RAM
      # - "plugins.security.disabled=true"
      - "OPENSEARCH_INITIAL_ADMIN_PASSWORD=${OPENSEARCH_INITIAL_ADMIN_PASSWORD}"
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536 # maximum number of open files for the OpenSearch user, set to at least 65536 on modern systems
        hard: 65536
    ports:
      - 9200:9200
      - 9600:9600 # required for Performance Analyzer
    networks:
      - opensearch-net
  opensearch-node2:
    image: opensearchstaging/opensearch:<IP_ADDRESS>66
    container_name: opensearch-node2
    environment:
      - cluster.name=opensearch-cluster
      - node.name=opensearch-node2
      - discovery.seed_hosts=opensearch-node1,opensearch-node2
      - cluster.initial_cluster_manager_nodes=opensearch-node1,opensearch-node2
      - bootstrap.memory_lock=true
      - "OPENSEARCH_JAVA_OPTS=-Xms512m -Xmx512m"
      # - "plugins.security.disabled=true"
      - "OPENSEARCH_INITIAL_ADMIN_PASSWORD=${OPENSEARCH_INITIAL_ADMIN_PASSWORD}"
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536
        hard: 65536
    networks:
      - opensearch-net
  opensearch-dashboards:
    image: opensearchstaging/opensearch-dashboards:<IP_ADDRESS>47
    container_name: opensearch-dashboards
    ports:
      - 5601:5601
    expose:
      - "5601"
    environment:
      OPENSEARCH_HOSTS: '["https://opensearch-node1:9200","https://opensearch-node2:9200"]'
    networks:
      - opensearch-net

networks:
  opensearch-net:

This indicates that your self-signed certificates have expired could you please generate new ones. Closing this as it is not an issue.

The expired certificate was in the file in the settings
plugins.security.ssl.transport.pemtrustedcas_filepath: root-ca.pem

You can quickly check everything through
while openssl x509 -noout -text; do:; done < root-ca.pem | grep After

Then find which ones have expired and delete PEM section from the file
remove block of expired certificate from root-ca.pem
Block like this
---BEGIN CERTIFICATE----
adkdlkag
---END CERTIFICATE----

find the block you need and remove it from the file
The real problem is that the log does not indicate which certificate has expired; you have to look for it manually. The problem started with the fact that the validator added a check for trusted certificates, which is generally unnecessary


Added relational mini placeholders support & conditional placeholders

Fixed some problems
Removed 300ms delay after joining a server
Code refactor

Also added more time placeholders for https://github.com/WiIIiam278/Velocitab/issues/195

Added docs for https://github.com/WiIIiam278/Velocitab/issues/193


feat: display lottery factor on Repository Table

Description
Update the repository table with Lottery Factor, replacing the PR Velocity column. Implements a new LotteryFactorBadge that is lifted from LotteryFactorChart into its own component.

Related Tickets & Documents
Closes #4007

Mobile & Desktop Screenshots/Recordings

Steps to QA

Go to the explore or workspace page
See the new table; check in mobile as well

Tier (staff will fill in)

[ ] Tier 1
[ ] Tier 2
[x] Tier 3
[ ] Tier 4

[optional] What gif best describes this PR or how it makes you feel?

We don't have to tackle this right away, but as a followup, this view of the table looks pretty messy. This is narrow enough where it collapses but not so narrow that it goes to the "card" view that you'd see on mobile.


Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
(Optional) Module Version
0.1.0
(Optional) Correlation Id
No response
Description
The databricks workspace is not pulling the correct public and private CIDR range.

│ Error: creating/updating Workspace (Subscription: "************"
│ Resource Group Name: "emea-******-p-rgrp"
│ Workspace Name: "emea-******-p-dbx"): polling after CreateOrUpdate: polling failed: the Azure API returned the following error:
│
│ Status: "SubnetIsNotWithinVnetError"
│ Code: ""
│ Message: "The subnet privates CIDR range '<null>' is not within the Virtual Network CIDR range '<IP_ADDRESS>/24'"
│ Activity Id: ""
│
│ ---
│
│ API Response:
│
│ ----[start]----
│ {
│   "status": "Failed",
│   "error": {
│     "code": "SubnetIsNotWithinVnetError",
│     "message": "The subnet privates CIDR range '<null>' is not within the Virtual Network CIDR range '<IP_ADDRESS>/24'"
│   }
│ }
│ -----[end]-----
│
│
│   with module.databricks_workspace_emea.azurerm_databricks_workspace.this,
│   on .terraform\modules\databricks_workspace_emea\main.tf line 7, in resource "azurerm_databricks_workspace" "this":
│    7: resource "azurerm_databricks_workspace" "this" {

The subnets on the specified vnet are as follows.
vnet_emea = {
  address_space   = ["<IP_ADDRESS>/24"]
  endpoint_prefix = ["<IP_ADDRESS>/25"]
  private_prefix  = ["<IP_ADDRESS>/26"]
  public_prefix   = ["<IP_ADDRESS>/26"]
}

If I create the databricks workspace manually specifying the correct CIDR ranges (as in that list above) it creates without issue.
I don't know if this is relevant but this issue occurs since using the latest terraform-azurerm-avm-res-network-virtualnetwork module to create our vnets which had breaking changes and started using the azapi provider to create subnets and other elements.

Issue seems to occur using the azurerm-provider as well. Due to landing zone policies, which require a nsg assigned to subnets during creation, we created subnets using the azapi_resource and avm-solution - the subnets created using those methods are causing the API error mentioned here.

Hey @Dipak-Mistry-WTW ,
Today i just tested my setup and i resolved it by setting up the subnet correctly.
The issue on my site was that you have to specify "addressPrefix" and not just "addressPrefixes" when using the azapi_resource for your subnet creation:
# Create Subnet via azapi due Policy, which requires NSG during creation!
resource "azapi_resource" "dbw_public_2" {
  type      = "Microsoft.Network/virtualNetworks/subnets@2023-11-01"
  name      = "dbw-public"
  parent_id = azurerm_virtual_network.vnet.id

  locks = [
    azurerm_virtual_network.vnet.id,
#    azapi_resource.dbw_private.id
  ]

  body = jsonencode({
    properties = {

      # List of Address prefixes in the subnet.
      **addressPrefix = "<IP_ADDRESS>/24"
      addressPrefixes = ["<IP_ADDRESS>/24"]**

      # Service delegations for the subnet.
      delegations = local.subnet_delegations

      # Service Endpoints for the subnet.
      #serviceEndpoints = local.subnet_serviceEndpoints

      # Conditionally include networkSecurityGroup
      networkSecurityGroup = {
        id = azurerm_network_security_group.dbw.id
      }
    }
  })
}

Issue seems to occur using the azurerm-provider as well. Due to landing zone policies, which require a nsg assigned to subnets during creation, we created subnets using the azapi_resource and avm-solution - the subnets created using those methods are causing the API error mentioned here.
Edit: I've created an issue in the terraform-provider-azurerm as it is the used module in avm-res-databricks-workspace.

Thanks @Matze-Li do you mind referencing your issue here?

Hey @Dipak-Mistry-WTW ,
Today i just tested my setup and i resolved it by setting up the subnet correctly.
The issue on my site was that you have to specify "addressPrefix" and not just "addressPrefixes" when using the azapi_resource for your subnet creation:
# Create Subnet via azapi due Policy, which requires NSG during creation!
resource "azapi_resource" "dbw_public_2" {
  type      = "Microsoft.Network/virtualNetworks/subnets@2023-11-01"
  name      = "dbw-public"
  parent_id = azurerm_virtual_network.vnet.id

  locks = [
    azurerm_virtual_network.vnet.id,
#    azapi_resource.dbw_private.id
  ]

  body = jsonencode({
    properties = {

      # List of Address prefixes in the subnet.
      addressPrefix = "<IP_ADDRESS>/24" ###### HERE WAS THE ISSUE WITH WRONG CIDR, IF NOT SPECIFIED #######
      addressPrefixes = ["<IP_ADDRESS>/24"]

      # Service delegations for the subnet.
      delegations = local.subnet_delegations

      # Service Endpoints for the subnet.
      #serviceEndpoints = local.subnet_serviceEndpoints

      # Conditionally include networkSecurityGroup
      networkSecurityGroup = {
        id = azurerm_network_security_group.dbw.id
      }
    }
  })
}

Do we need to keep this issue open @Matze-Li ?

This was the vnet module issue.  Closing.

I'm also seeing this when creating an azurerm_databricks_workspace against pre-existing subnet's using azurerm 3.113.0.
@Dipak-Mistry-WTW Do you know what the solution is when you already have subnet's in-place which use addressPrefixes[]?

@Philcartmell - I managed to convert mine to use AddressPrefix.  Thankfully I don't have multiple address spaces for my subnets.


Retrieval of fully hydrated domain object is inconsistent.

Using Neo4j OGM 2.0.1
I have a domain object UserAccount that has a relationship with any number of Drive domain objects.
To find a specific Drive I retrieve the UserAccount by id at depth 1 and then find the Drive's id.
Next, using the id, I retrieve the drive using load by id with depth -1.
However, when loading multiple Drives via UI actions, only the most recently retrieved Drive is returned in full.  All of the others are still returned at depth 1.
There's some sort of weird cause and effect here which may or may not be a bug; maybe I'm just missing something.  As you can see from the code, I am using a fresh session to retrieve the Drive after a portion of it was retrieved in the previous session.
This is a follow-on from http://stackoverflow.com/questions/36635261/new-neo4j-ogm-session-contains-entities-from-older-session (sorry Luanne, I never received a notification from Stack Overflow that you had responded).
def find(driveName: String, userId: Long): Option[Drive] = {
// TODO Check for error
// TODO Write wrapper around load functions to return Options instead of null - then error check this
// A wrapper around session creation.  .session function returns new session from factory
val ua = Neo4jSessionFactory.session.load(classOf[UserAccount], userId)

val driveOpt = ua.drives.asScala.find(_.name == driveName).map(_.id)
val drive = driveOpt.map(Neo4jSessionFactory.session.load(classOf[Drive], _, -1))
println(s"drive = $drive")
drive

}

@sjnester I've written a test based on my understanding of the problem: https://github.com/neo4j/neo4j-ogm/commit/99ca368b8d07ac3e8d726eb3ecbb770e4e3f2efe#diff-23d750acb2032cda68106db9cb4b4b0bR173
The test passes - what am I missing?

Closing this issue based on a passing test, please feel free to reopen if the issue resurfaces.


The tests in webnn-polyfill can run continuously without crash

@huningxin  PTAL, thanks.

Let's merge it for testing.