[Bug]: locale-gen  Bad system call

Problem description
locale-gen zh_CN.UTF-8
Generating locales...
en_US.UTF-8... done
zh_CN.GB18030... done
zh_CN.GBK... done
zh_CN.UTF8.../data/data/com.termux/files/usr/glibc/bin/locale-gen: line 41: 20473 Bad system call         localedef --no-archive -i $input -c -f $charset -A /data/data/com.termux/files/usr/glibc/share/locale/locale.alias $locale
System information
termux-info:
Termux Variables:
TERMUX_API_APP__VERSION_NAME=0.50.1+3035f0a
TERMUX_APP_PACKAGE_MANAGER=pacman
TERMUX_APP__AM_SOCKET_SERVER_ENABLED=true
TERMUX_APP__APK_PATH=/data/app/~~rXzLiacmu4gqO117Um3CwQ==/com.termux-TPg_dWnG0Sub6mftt-wwew==/base.apk
TERMUX_APP__APK_RELEASE=GITHUB
TERMUX_APP__FILES_DIR=/data/user/0/com.termux/files
TERMUX_APP__IS_DEBUGGABLE_BUILD=true
TERMUX_APP__IS_INSTALLED_ON_EXTERNAL_STORAGE=false
TERMUX_APP__PACKAGE_MANAGER=apt
TERMUX_APP__PACKAGE_NAME=com.termux
TERMUX_APP__PACKAGE_VARIANT=apt-android-7
TERMUX_APP__PID=11876
TERMUX_APP__SE_FILE_CONTEXT=u:object_r:app_data_file:s0:c17,c258,c512,c768
TERMUX_APP__SE_INFO=default:targetSdkVersion=28:complete
TERMUX_APP__SE_PROCESS_CONTEXT=u:r:untrusted_app_27:s0:c17,c258,c512,c768
TERMUX_APP__TARGET_SDK=28
TERMUX_APP__UID=10529
TERMUX_APP__USER_ID=0
TERMUX_APP__VERSION_CODE=118
TERMUX_APP__VERSION_NAME=0.118.0+2f40df9
TERMUX_MAIN_PACKAGE_FORMAT=pacman
TERMUX_VERSION=0.118.0+2f40df9
TERMUX__USER_ID=0
Packages CPU architecture:
arm
Subscribed repositories:
# /data/data/com.termux/files/usr/etc/pacman.conf
[main]
Usage = All
Server = https://service.termux-pacman.dev/main/arm
Server = https://s3.amazonaws.com/termux-pacman.us/main/arm
[x11]
Usage = All
Server = https://service.termux-pacman.dev/x11/arm
Server = https://s3.amazonaws.com/termux-pacman.us/x11/arm
[root]
Usage = All
Server = https://service.termux-pacman.dev/root/arm
Server = https://s3.amazonaws.com/termux-pacman.us/root/arm
[tur]
Usage = All
Server = https://service.termux-pacman.dev/tur/arm
Server = https://s3.amazonaws.com/termux-pacman.us/tur/arm
[tur-continuous]
Usage = All
Server = https://service.termux-pacman.dev/tur-continuous/arm
Server = https://s3.amazonaws.com/termux-pacman.us/tur-continuous/arm
[tur-multilib]
Usage = All
Server = https://service.termux-pacman.dev/tur-multilib/arm
Server = https://s3.amazonaws.com/termux-pacman.us/tur-multilib/arm
[gpkg]
Usage = All
Server = https://service.termux-pacman.dev/gpkg/arm
Server = https://s3.amazonaws.com/termux-pacman.us/gpkg/arm
[gpkg-dev]
Usage = All
Server = https://service.termux-pacman.dev/gpkg-dev/arm
Updatable packages:
All packages up to date
termux-tools version:
1.42.1
Android version:
12
Kernel build information:
Linux localhost 4.14.186+ #1 SMP PREEMPT Tue Nov 28 22:29:36 CST 2023 armv8l GNU/Linux
Device manufacturer:
OPPO
Device model:
PDCM00
LD Variables:
LD_LIBRARY_PATH=
LD_PRELOAD=
Installed termux plugins:
com.termux.api versionCode:51

Run the following command and send the glibc-runner-debug-strace-*.log file:
grun -d 4 -n locale-gen

I also noticed that you are using the gpkg and gpkg-dev repositories, which is not acceptable as it may break some functions due to installing packages with different settings. Please ensure that all glibc-based packages are installed from the gpkg repo. Run the following command to verify this (should return nothing):
pacman -Sl gpkg-dev | grep '\[installed\]'

Okay, it's my problem

Okay, it's my problem

Everything is fine. Feel free to ask for help if any problems arise.


FEAT: update reward rate instruction

Changes
Checklist

[ ] UAT
[ ] Passes final QA checks

Task linked: CU-1jfrahh SCORE: Ability to update SCOREVARs Ship via the authority


WebSocket connection failure

I've just discovered NeoDash, great software!
I've tried to test the on line version with one of our own databases, but I get the common generic message:
Unable to establish connection. WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver. Please use your browsers development console to determine the root cause of the failure. Common reasons include the database being unavailable, using the wrong connection URL or temporary network problems. If you have enabled encryption, ensure your browser is configured to trust the certificate Neo4j is configured to use. WebSocket readyState is: 3
The URI I'm trying is: bolt://knetminer-wheat.cyverseuk.org:7687. This doesn't require any user/password (I've both tried giving NeoDash credentials and leaving user/pwd fields empty) and works well in other contexts (eg, the Neo4j browser, a test script in python, using the latest Neo4j driver).
I've also tried to inspect the logs using the browser's developer console, but the only thing it shows is a generic connection failure, plus the unexpected URI: wss://knetminer-wheat.cyverseuk.org:7687. If I try this wss:// URI with the Python test, the driver answers me that it doesn't know the wss:// protocol.
Might it be that the server is already too old (it's v4.3.3, community edition)?
Thanks in advance for any help.

Hi Marco!
Can you check if your db was up and running during your test?
I just tried now with the online 2.0.15 version on http://neodash.graphapp.io/ and it works fine.

Bennu

I am able to connect using the following configuration, using the online version  http://neodash.graphapp.io/.
See attached.

Can you try again?
Can you try again?

Hi @nukerxy, thanks for your quick reply! It works now, the bolt connection looked fine yesterday too, no idea what happened. Many thanks!

@nukerxy, it's worth to add a note to this issue: the URL you gave above works because it starts with http://, rather than https://. I think the problem is that our server has SSL disabled (the exposed data are open, getting a certificate wouldn't be easy).
I'm leaving this info in case others come here starting from the same issue. Indeed, I've just discovered that http://charts.graphapp.io/ behaves the same.


When the list of available extensions appear, install any extension - this works fine.
Now, try the same, but try installing C# for Visual Studio Code (powered by OmniSharp)
VSCode attempts to install the extension, but after some time (about 30 seconds to a minute) this error appears:

Server returned 404

After this message appears, VSCode still looks like it is trying to install something in the bottom left corner.
Extra Details:
I have the following settings in my settings.json file:
// Place your settings in this file to overwrite the default settings
{
    "http.proxyStrictSSL": false,
    "git.autofetch": false
}

As I was not able to install any extensions before adding "http.proxyStrictSSL": false.
When I remove this line from my settings, I am again no longer able to search for extensions with this message:

Error unable to get local issuer certificate

Can you reproduce with the latest stable (1.3.1) or latest insider release?

@joaomoreno  After downloading and installing VSCode 1.3.1 I was able to download the C# extension without any issues


Function to set expire timer of an added entry.

Per discussion in the call last week, I have uploaded this PR with the proposed function to set expiry timer along with some examples.

@roop-nvda Similar to the discussion we had on add_entry_if in this issue https://github.com/p4lang/pna/pull/43 my main comment would be to express my strong preference that if we want to create extern functions that have explicit parameters to make the side effects conditional, that we do so with a single in bool condition parameter rather than two parameters val1 and val2 that restrict the condition to val1 == val2.
I have added another comment to your PR showing how one of your example calls to set_expire_time_if examples could be rewritten if it has such a bool first parameter.
As for the discussion on https://github.com/p4lang/pna/pull/43, it seems to me that doing it this way lets one express the functionality you want, as well as more general conditional expressions, e.g. (a < 5).  If a target device cannot support (a < 5), then that is up to the compiler for that target to say it is too complex, preferably with links to documentation on what kinds of expressions that target supports in such conditions.

So suppose in the kind of target that you are thinking of, the back end of the P4 compiler checked the conditional expression's IR to see if it met the following conditions.  This seems like a fairly straightforward thing for a back-end to check in time linear in the number of IR nodes of the expression, i.e. it would be very fast and simple:

verify that all leaves are metadata variables or constants
verify that all parent nodes in the IR of the leaves are == operators
verify that all other nodes in the IR tree of the expression are && operators (&& is associative, so the shape of the IR nodes in the tree does not matter)

If those were true, then it is a straightforward linear time operation (at compile time, not run time in the data plane) to know that any expression (a1 == b1) && (a2 == b2) && ... is equivalent to {a1, a2, ...} == {b1, b2, ...}.
If those conditions were not true, the back end of the target you have in mind would reject the condition as unsupported (for that target device).
Compilers for particular P4 targets are allowed to reject programs as too complex.  They do it for any number of reasons all the time, differently for each back end target device, depending on the details of the target's capabilities.  In a case like this, the error message for rejected expressions could even be very helpful in the back end: "supported conditional expressions must be of the form (a1 == b1) && (a2 == b2) && ... where all a's and b's are either header or metadata fields, or constants.
The restrictions of such a back end need not restrict OTHER P4 compiler back ends for other targets that might have different restrictions, though.  Is that 100% portable?  No, of course it isn't.  But we know that different targets will have restrictions that differ between them like: maximum number of recommended or hardware-permitted recirculate operations per packet, maximum number of table apply operations supported in a single pass, etc.  I don't think anyone involved in PNA wants to try to mandate particular numerical values for those things that all targets must comply with -- they will vary today, and they will likely vary across different devices from a single vendor, too.

Apologize if it was not clear, but I was not suggesting that numerical values of the size of tuple argument of set_expire_time_if be mandated in PNA. I merely gave an example with a fictitious target -- Acme -- to illustrate that the error message was simple for the programmer. Different targets are indeed expected to support different sized tuples for matching, but the semantic of a match is simple -- (data[0] == value[0]) && (data[1] == value[1]) ... && (data[N-1] == value[N-1])-- and obvious across the class of targets.
When compiling for bmv2 simple switch backend with a conditional in a match action we get an error message implying that only C/C++ ternary assignment type conditionals are allowed -- only conditionals like if (a > 5) { a = 5;} are allowed in match actions for this target.  Different targets expressing this and other classes of conditionals that are supported/unsupported in an error message in a way that helps the programmer fix the program can get cumbersome.

Maybe I am answering a different concern than you are worried about, but note that the bmv2 back end today can support assignment statements like this inside of P4 actions, as demonstrated by the attached program:
    action a1() {
        b1 = (hdr.ethernet.srcAddr == hdr.ethernet.dstAddr) && (hdr.ethernet.etherType == 0x0800);
    }

since it can implement that with no changes, I suspect that it should also be able to implement an action like this with the only change required to be defining and implementing an extern set_expire_time_if that has a first parameter with type in bool:
set_expire_time_if((hdr.tcp.flags == TCP_FLG_SYN) && (meta.direction == OUTBOUND),
                   tcp_connection_start_time_profile_id);

v1model_bool_expressions_supported1.p4.txt

@roop-nvda Here is another angle on the question.  Suppose we did say we were only going to implement your proposed version of set_expire_time_if, where the first two parameters must be equal in order for the side effect to be performed.
Then it is perfectly legal P4 syntax to write this:
    set_expire_time_if(a < 5, true, tcp_connection_start_time_profile_id);

because a < 5 is an expression that evaluates to a type bool value, and that is the same type as the second parameter.
So trying to require two parameters that must be equal, trying to restrict the generality of conditional expressions that can be expressed, actually does not restrict it at all.

@jfingerh  -- Agreed. I will amend and resend the PR.


Contributor console new company flow

[ ] Do not show this dialog after user has entered their new company information (i.e. URL and name)

[ ] Take user directly to "No Signed CLA Found" dialog box

[ ] If the user selects "No"

[ ] Check if the designated user has a LF Login and if they do make them Company Administrator for the new company. Add the company to SFDB. Send out the invite flow email to this user.
[ ] If the designated user doesn't have a LF Login. Add the company to SFDB. Send out an email telling the user to complete company profile and create a LF Login.

[ ] If the user selects "Yes" at "No Signed CLA Found" dialog box. Take the user all the way to Corporate console login and after that where we show the dialog box of assigning roles and at that stage insert the company in SFDB.

Testing to blocked due to #2138

Testing blocked due to #2157

Verified and found working fine. Please find the screencast attached for your reference.
https://app.zenhub.com/files/194341141/2b0a6aea-ba71-419a-b666-804944a13293/download


What about new features like a query batching and subscriptions

https://dev-blog.apollodata.com/new-features-in-graphql-batch-defer-stream-live-and-subscribe-7585d0c28b07

Definitely interested! Is there any indication on when this will end up in the official specification or some other spec document?

No, but Facebook uses these internally. The Apollo (client and server) also supports both features, the official GraphQL server supports only subscriptions.

Okay. I'm not against those features, but there are other things I need to take care of first. Effectively this means that those features will either be added when I need them myself or via PR.

I'd like to help implement these, ~maybe~
In my project, I do a pipeline where I start out defining the schema in Protobuf, and it gets converted into a variety of different things (TypeScript definitions, GraphQL schema).
Right now I'm looking at an arms race, really:

PlayLyfe - got my relatively large project working with some intermediate code-generation and interface manipulations (I generate a function to get the GraphQL schema type name for all of my ProtoBuf schemas). The code base is shit, though. I don't see adding subscriptions to that being a very easy thing.
Go-Graphql - massive, seems well made, but pretty inactive and for some reason there is no documentation / any way to convert a schema AST into a Go schema. Supports subscriptions (!)
This repo - nicely written, requires some intermediate code generation from me, but otherwise I like it more than the others. The main difficulty here is I have to do this stuff which I really hate. I can code-gen most of this, but it just seems like a mess. Some reflection could work better.

Either way, if we could support subscriptions in this repo I think I would probably adopt it for my projects. I'm going to try to write the code-gen stuff in my codebase to make everything work as-is with this repo. If I can do that, I'd love to help implement subscriptions.

I've ported all my stuff to run on this library now, nice! Requires a LOT of code generation to cover trivial member field struct resolvers, but it's worth it I think.
As for subscriptions, where are we on that? I can have a look at what would be required to add them in. Thoughts on what the API could look like @neelance ?
I'm thinking Exec( signature is the same, but it just doesn't return until the subscription terminates or the context terminates.

What documentation is out there on how subscriptions are supposed to work? How do the updates get pushed to the client? WebSockets?

I've been reading the Apollo client stuff on it, but admittedly there doesn't seem to be much. I'm using websockets and I think that's the common way to do it. I send even normal graphql requests over websockets as is right now.
There's a proposed revision to Graphql to add @defer and @live (I think) to fields. Defer would allow the field to be loaded asynchronously, and the data sent after the initial document is returned. Live would allow updates to that field to be transmitted in real time.
There's no real info about how canceling / completing these would work.
Supposedly Facebook uses them internally already.
I've been reading the article in the first message in this thread too - it has most of the info about the proposed features.
As far as I know subscriptions are done and in the spec, and basically just allow ADD operations to root query fields over time. It seems very limited and I like the defer and live annotations better, but those don't seem to be ready for primetime yet.

Facebook seems to use all of these features internally, and just hasn't bothered to put it into the spec / OSS code yet.
Other related issues:

https://github.com/apollostack/graphql-server/issues/34
https://github.com/facebook/relay/issues/541

Apollo says "we can work on it early march," not sure on relay.

In terms of graphql-go. Right now we have a single Execute( call which returns a single response object. Obviously we need a API change if we want to handle multiple responses.
There also needs to be a mechanism to pair messages coming from a server with a specific query context. In apollo-client this is left up to the network transport, and returns an integer ID for the query context, which can later be released (like a setTimeout handle). This is a good approach in my opinion.
I'm already using a similar approach in my WebSocket transport between Apollo and GraphQL-Go for just regular requests - since we don't have the context of a HTTP request, there needs to be an identifier for each request. I think this is best left up to the user / network transport to handle. There are a number of varying approaches to do this depending completely on the transport - if you're using long-lived HTTP requests for streaming requests, for example, such an identifier might be unnecessary as you still have the structure of an HTTP request.
Given that we are leaving this "data channel" stuff up to the user, it then makes sense to have graphql-go support a second mode of operation that would allow these kinds of deferred requests. Something like ExecChannel which would return a channel of *Response objects instead of just a single response. Again, the server implementation can indicate query completion when closing the response channel, and the requester can terminate the long-lived query by canceling the parent context.
Since you could send standard queries alongside complex long-lived queries together through this kind of call, it then makes sense to standardize the server code. Calling resolvers should be the same code regardless of Channel or no Channel. We can add a parameter to iExec.exec for "channel" which, when false, would cause the server to completely ignore directives like defer and live.
Right now exec returns an interface{}. Lists are executed in parallel, spawning a goroutine for each element in the list, remembering the index the result should be in. This code is already super close to what would be necessary to do a @stream directive, which returns array elements over time as they are resolved (although index would probably not be necessary in this case). Relevant code for processing things like lists is here.
I would propose allowing resolvers to return a channel, rather than an array, with an optional argument for a struct with information about the request (is it @stream or not?). If we are running a standard Execute we can wait until the channel is closed to return the result from that resolver. If we are running an ExecuteChannel with the @stream set on the field, we can send each result entry in the channel as it comes in over the wire, and not wait for the channel to close to send the initial response.
Doing @live is a bit more complex, since we need a way to describe changes to entries we've already returned. I'll leave this for later.
Again, apologies for the essays, but I need to write this somewhere and I figure here's as good a place as any.

Is it allowed to use @live and @stream everywhere? I'd expect that the schema would need to explicitly say where those modifiers are possible. In that case you could expect a different method signature for the resolver.
Imho the features are not yet properly specified. I'd rather wait for Relay 2 to be officially released. Relay 2 is supposed to have those features, so when they release it they will also have to add documentation or a spec and it will also be an official reference implementation, not just something that graphql-js happens to support.
Good luck with any experiments you want to do in a fork, I hope you can make it work for your use case. But please don't be disappointed if we can't bring it into this repo because it is too experimental.

That's fine! I know it's experimental.
Placing these specifiers on fields doesn't need a schema change, I think. For stream and defer, it should always work (stream on arrays or channels at least). For live, if we want to be aggressive we can poll the field for changes with a configurable rate. I don't think that's necessary, though. Just treat live like defer if there is no chan returned.

@neelance @defer is done at https://github.com/paralin/graphql-go/tree/feat-defer

@neelance first pass of @stream is done.
Initial: {"data":{}}
Live: {"data":[null,null,null],"extensions":{"path":["regions"]}}
Live: {"data":{"__typename":"Region","id":"test3"},"extensions":{"path":["regions",2]}}
Live: {"data":{"__typename":"Region","id":"test2"},"extensions":{"path":["regions",1]}}
Live: {"data":{"__typename":"Region","id":"test"},"extensions":{"path":["regions",0]}}
Live: {"data":"test region","extensions":{"path":["regions",0,"name"]}}
Live: {"data":"test region, delayed by 500ms","extensions":{"path":["regions",1,"name"]}}
Live: {"data":"test region, delayed by 1sec","extensions":{"path":["regions",2,"name"]}}

Same branch.

Arrays can now return channels: <-chan *ResolverType

@neelance And finally, I have finished @live. here are some demos:

Nothing but @live on just one sub-field: https://asciinema.org/a/7mzm6ohbkzg1bof0sdl8euyxz
Just @stream on the list: https://asciinema.org/a/7pl3z700mf7zhx5rdnhnbx785
No new directives (Exec compatible) https://asciinema.org/a/1s5f7dm9r7f6l58ix9vc35pna
Just @defer on the status field: https://asciinema.org/a/8tb0zbkxj81gi0os6t748z2kp

FYI https://github.com/facebook/graphql/pull/267

FYI I've moved all of my work from this thread and rewritten everything into http://github.com/rgraphql/magellan

I saw at graphql-go/graphql, and seems like they have a lot of pending PR, also the code has more boilerplate, I think the neelance has a better aproach

I also think that the neelance has a better aproach. Facebook modern relay is finally out and it supports graphQL subscriptions.  I am wondering if this library would support graphQL subscriptions? Thanks.

I've been looking at relay-modern and they don't have documentation yet for how subscriptions should work, it should be possible to follow apollo idea which i believe it should work with relay out of the box.

@lpalmes Any update on your latest experience with relay-modern on subscriptions? Thanks.

I'm still waiting for an update to the spec.

@neelance https://github.com/facebook/graphql/blob/master/rfcs/Subscriptions.md

But I guess neelance is waiting updates on this page https://facebook.github.io/graphql/

@LeeWong i'm sorry i've missed the notification, i'm having way too many github notifications, my bad. I have to try subscriptions in relay-modern and is something that just now has been added to the docs.
@neelance The spec has been updated and now it has subscriptions by this pull request and it has been implemented in graphql-js, to have a reference implementation.

@lpalmes Thanks. Very excited to see how the relay-modern could work well with this graphql-go, especially in the subscriptions.

Subscriptions have been merged into the specification: https://facebook.github.io/graphql/#sec-Subscription
I've started reading through... let's do this!

FWIW I've implemented query batching on top of this library. Works great with the Apollo client!

Hey @tonyghita, how did you go about implementing query batching on top of this library? Could you show me an example?

@sdemontfort Here is an example of implementing batched queries. https://github.com/nicksrandall/batched-graphql-handler

@sdemontfort I've been a bit short on time, but I'm planning on making an example repo like @nicksrandall to give a different approach.
The idea is more or less the same though.

Hi all! Are you happy with your decision to go with this library rather than https://github.com/graphql-go/graphql? From what I've gathered, this project is cleaner yet less complete in comparison and is more actively maintained. That could either be a result of it being less complete or a good sign of ongoing development.
I'm just trying to decide on which route I should take when starting to use graphql in a go project I'm starting soon. I asked a similar question over there https://github.com/graphql-go/graphql/issues/196#issuecomment-311431814
Thanks!

I like the API of this project a lot more. It's so much cleaner. I think I'll go with this one. I went through both star wars examples for the repos and based my decision on the number of questions I had on each and how hard they were to figure out. Although this project's example had a couple hundred more lines of code and no documentation, I could much more easily understand what was going on and trace it through the library.

I'll do my best to help this repo move forward in the future as well. I may start contributing by writing documentation :P

@ijsnow I'm happy to hear that you like the project. As a heads-up: The API will get a major change soon, see #88.

No news about the subscription?

I saw that 6 months ago, some part of the "subscription" support was done, but no tests and probably the most important part is not there yet. Any feedback?

@juliandroid did you mean that the package can parse a subscription keyword?
https://github.com/neelance/graphql-go/search?utf8=✓&q=subscription&type=
Does anyone need GraphQL subscriptions right now? We can discuss a implementation.

@mikeifomin what are the alternatives? If you want to keep track of some property/data and fetch the update?

@juliandroid I already use Apollo in my node.js stack.
But one of my project requires the golang-graphql backend and some live data features.
For now I have implemented the live data in a pure websocket + custom events + json. This cause
the invention of a wheel at the frontend.
And looking for more convenient and robust solution like the Apollo server for golang.

Basically, that means Apollo server (handler for graphql-go), plus subscription support. The only thing that I've found so far was github.com/nicksrandall/batched-graphql-handler that handles batching part.

Rgraphql should do what you want, and we will be doing stability passes on it in the coming week. It's a very different approach but in the long run I think it will win out. The binary encoding and compression is too good to pass up.

@paralin Correct me if I'm wrong, but Rgraphql requires graphql-go (the other one) and also Rgraphql from clients site doesn't support iOS and Android as it is the case with Apollo :(

Hey @neelance! Thanks for the library! Have re-written my API using it, but was initially mislead that it supports subscription, mostly because of grep returned some result by keyword subscription 😄 . Is it in your near plans to implement it?

I need graphql subscriptions as well

@pavelnikolov think we can close this one? Subscriptions is now supported and an alternative implementation of query batching has been posted by @nicksrandall.


Pod Security Standards Customization

I want to create a custom pod security baseline as currently I cannot restrict the below runAsUser in the baseline without using restricted policy which won't work in my case.
apiVersion: v1
kind: Pod
metadata:
name: nginx
spec:
containers:

name: test-container
image: nginx
securityContext:
#privileged: true  # Violating privileged containers policy
readOnlyRootFilesystem: false  # Violating read-only root filesystem policy
runAsUser: 0  # Violating non-root user policy

/language en
/sig docs
/sig node

Page related to the issue: https://kubernetes.io/docs/concepts/security/pod-security-standards/
/kind support

Hi @zakicisco, GitHub is not the right place for support requests.
For further help, you could ask on Server Fault.
You can also post your question on the Kubernetes Slack or the Discuss Kubernetes forum.

I think this is not really about the documentation but a feature request to allow adding a custom Pod security standard.
/transfer kubernetes


(ffmpeg*) descriptions missing codecs/libraries included in each

The packages "ffmpeg" and "ffmpeg-full" descriptions make no reference to the libraries included in each.
They instead refer to "essentials" and "full", neither of which exist in the upstream ffmpeg project at www.ffmpeg.org.
Expected Behavior

Be able to look at package description and see the differences between the packages.
or
Have the package description link to a site that shows the differences

Current Behavior
"ffmpeg" is described as the "essentials ffmpeg version"
"ffmpeg-full" is described as the "full ffmpeg version"
Possible Solution
The packages seem to be using builds from gyan.dev, so a reference to https://www.gyan.dev/ffmpeg/builds/#libraries could suffice, since it lists the included libraries for each there.

@slycordinator that is a good catch that we somehow had missed.
If you are interested, I have marked this issue as Up for grabs if you are willing to provide a PR to get the link containing the libraries added (only the Readme.md file need to be updated, and should be in a ## Notes section in that file).


[Bug] 因战绩更新，导致启动器无法正常使用部分功能

Checklist

[X] My issue was not mentioned by others, and it is not a duplicate issue.

Description
米哈游更新了战绩功能，导致启动器的战绩功能无法正常使用，不知是不是UA的问题
我在我手机比较新的版本的米游社抓到的UA是okhttp/4.9.3
不一定能用，技术不到家，猜测
Reproduction Steps
打开启动器的米游社工具箱，点击战绩，在我的角色一栏点击“全部角色”
Expected Behavior
正常使用全部功能，如下图

点击角色可以进入

Screenshots

Starward Version
0.12.2-preview.2
Windows Version
22635.4076
Log
[14:36:38.737] [INFO]
Welcome to Starward v0.12.2-preview.2
System: Microsoft Windows NT 10.0.22635.0
Command Line: D:\information\Starward\app-0.12.2-preview.2\Starward.dll

[14:36:38.798] [INFO] Starward.Services.DatabaseService
Database path is 'D:\information\Starward'

[14:36:38.857] [INFO] Starward.Services.DatabaseService
Database version is 9, target version is 9.

[14:36:38.941] [INFO] Starward.Pages.MainPage
Last game region is hkrpg_cn

[14:36:38.951] [INFO] Starward.Pages.MainPage
Navigate to "GameLauncherPage" with param hkrpg_cn

[14:36:39.700] [INFO] Starward.Pages.GameLauncherPage
Game install path of hkrpg_cn: "D:\information\MiHoYoGAME\Honkai Star Rail"

[14:36:39.720] [INFO] Starward.Pages.GameLauncherPage
Acutal version and gamebiz of hkrpg_cn is "2.4.0".

[14:36:40.650] [INFO] Starward.Services.UpdateService
Start to check update (Preview: True, Arch: X64)

[14:36:41.638] [INFO] Starward.Services.UpdateService
Current version: "0.12.2-preview.2", latest version: "0.12.2-preview.2", ignore version: null

[14:36:42.144] [INFO] Starward.Pages.MainPage
Navigate to "HoyolabToolboxPage" with param hkrpg_cn

[14:36:42.155] [INFO] Starward.Services.GameRecordService
Change region to China.

[14:36:43.224] [EROR] Starward.Services.HoYoPlayService
PrepareDataForServerAsync
System.Net.Http.HttpRequestException: Error while copying content to a stream.
 ---> System.Net.Http.HttpIOException: The response ended prematurely while waiting for the next frame from the server. (ResponseEnded)
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception )
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryEnsureHeaders()
   at System.Net.Http.Http2Connection.Http2Stream.ReadResponseHeadersAsync(CancellationToken)
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage, Boolean, CancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.HttpContent.LoadIntoBufferAsyncCore(Task, MemoryStream)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage, HttpCompletionOption, CancellationTokenSource, Boolean, CancellationTokenSource, CancellationToken)
   at Starward.Core.HoYoPlay.HoYoPlayClient.CommonGetAsync[T](String url, String node, CancellationToken cancellationToken) in D:\a\Starward\Starward\src\Starward.Core\HoYoPlay\HoYoPlayClient.cs:line 45
   at Starward.Core.HoYoPlay.HoYoPlayClient.GetGamePackageAsync(String launcherId, String language, CancellationToken cancellationToken) in D:\a\Starward\Starward\src\Starward.Core\HoYoPlay\HoYoPlayClient.cs:line 159
   at Starward.Services.HoYoPlayService.PrepareDataForServerAsync(String launcherId, String language) in D:\a\Starward\Starward\src\Starward\Services\HoYoPlayService.cs:line 113

[14:36:43.236] [EROR] Starward.Services.HoYoPlayService
PrepareDataForBilibiliServerAsync
System.Net.Http.HttpRequestException: The response ended prematurely while waiting for the next frame from the server. (ResponseEnded)
 ---> System.Net.Http.HttpIOException: The response ended prematurely while waiting for the next frame from the server. (ResponseEnded)
   at System.Net.Http.Http2Connection.ThrowRequestAborted(Exception )
   at System.Net.Http.Http2Connection.Http2Stream.CheckResponseBodyState()
   at System.Net.Http.Http2Connection.Http2Stream.TryEnsureHeaders()
   at System.Net.Http.Http2Connection.Http2Stream.ReadResponseHeadersAsync(CancellationToken)
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage, Boolean, CancellationToken)
   --- End of inner exception stack trace ---
   at System.Net.Http.Http2Connection.SendAsync(HttpRequestMessage, Boolean, CancellationToken)
   at System.Net.Http.HttpConnectionPool.SendWithVersionDetectionAndRetryAsync(HttpRequestMessage, Boolean, Boolean, CancellationToken)
   at System.Net.Http.RedirectHandler.SendAsync(HttpRequestMessage, Boolean, CancellationToken)
   at System.Net.Http.DecompressionHandler.SendAsync(HttpRequestMessage, Boolean, CancellationToken)
   at System.Net.Http.HttpClient.<SendAsync>g__Core|83_0(HttpRequestMessage, HttpCompletionOption, CancellationTokenSource, Boolean, CancellationTokenSource, CancellationToken)
   at Starward.Core.HoYoPlay.HoYoPlayClient.CommonGetAsync[T](String url, String node, CancellationToken cancellationToken) in D:\a\Starward\Starward\src\Starward.Core\HoYoPlay\HoYoPlayClient.cs:line 45
   at Starward.Core.HoYoPlay.HoYoPlayClient.GetGameBackgroundAsync(String launcherId, String language, CancellationToken cancellationToken) in D:\a\Starward\Starward\src\Starward.Core\HoYoPlay\HoYoPlayClient.cs:line 109
   at Starward.Services.HoYoPlayService.PrepareDataForBilibiliServerAsync(String language) in D:\a\Starward\Starward\src\Starward\Services\HoYoPlayService.cs:line 144

Additional Context
No response

这个页面就是会这样，我也不知道怎么办，但不影响使用

换下UA看看？


backup.yml always drops existing DB

this is critical issue with this role
it should be possible to apply this role multiple times to server and it should not destroy the DB if already exists
the problem is in "init db schema" task which should be executed only if "Create ttrss postgres database" created new database.
the ttrss_schema_pgsql.sql contains DROP commands

The "creates" flag coupled with && touch /root/ttrss_schema_loaded ought to prevent the task from running more than once on a server.
Under what workflow are you encountering the destructive behavior?


Fix logging of wrong feature_columns in CLI

Description
The CLI command for the FIL pipeline set a default value for --columns_file flag but some FIL pipelines like ransomeware didn't use this config property, causing the default columns file to be loaded and for the values to be logged to the terminal.

Removed default values for --columns_file and --labels-file flags
Removed redundant checks for null values if they were already being enforced by required=True
Misc pylint/flake8 errors

fixes #819
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.

Invalid PR closing in favor of PR #983


Switch type by generic enum

🔍 Search Terms
switch conditional type
✅ Viability Checklist

[X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[X] This wouldn't change the runtime behavior of existing JavaScript code
[X] This could be implemented without emitting different JS based on the types of the expressions
[X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
[X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion
A new way to define a generic type based on what another generic type extends by switch rather than chaining ternary operator
📃 Motivating Example
Current implementation
enum ModelType {
    DateTime,
    Date,
    Period,
}
type DateType< T extends (ModelType | undefined) = undefined> = T extends ModelType.Period ? DatePeriod : T extends ModelType.Date ? DateOnly : DateTime;

Potential new implementation
type DateType<T> = T switch {
    ModelType.Period => DatePeriod,
    ModelType.Date => DateOnly,
    _ => DateTime,
}

One should also be able to do this with a list of strings
💻 Use Cases

What do you want to use this for? For enforcing input model value type based on an option value
What shortcomings exist with current approaches? Long chain of ternary operators, hard to read
What workarounds are you using in the meantime? Long chain of ternary operators

Duplicate of #51375.

Closing duplicate


Update tests

After the latest refactoring, we need to update the unit tests located in the tests/ folder. Any help will be appreciated!

we still need to test batter.py and cli.py, while disk.py is half-way done

This week is busy, but if this is still open next week I'll find the time to help.


Add tx2 on Jetpack 4.2 (Draft - DO NOT MERGE)

Add tx2 on Jetpack 4.2
Update BalenaOS
Update jetson nano

Some file conflict apaprently in this Pr now since something was merged in master recently

Not needed anymore, many changes have been merged already, others will be merged when fixes are provided by l4t.


[vkontakte] use avatar redirect for Vkontakte

Vkontakte requires an access_token since April 2017[1] so our avatar
source broke. Because the access token may only be used in a server side
application I've added support for Vkontakte to Avatar Redirect
and added the vkontakte redirect source.
Resolves https://github.com/Sitebase/react-avatar/issues/146

This has been released as part of version v3.5.0!


Some side effects after replacing file Explorer with a file

Describe the bug
Some side effects after replacing file Explorer with a file
To Reproduce
1.Trying to open recycle will Open the homepage.
2.In the Task Manager, trying to open location  file no response.
3.Right click on "this PC -> Properties",will Open the homepage.
Desktop (please complete the following information):
OS Version: 20H2 Pro
App version: <IP_ADDRESS>
I think it originated from the same problem, so I wrote it together

Thanks for opening this feedback item. Please note that replacing file explorer with Files is not supported and known to have undesired side effects.
[Internal comment] we might want to add the above issues to the wiki description, so it's clear that there are additional issues wrt to the Control Panel not opening


Idle handlers should be more configurable

@adamfisk - do you have any more info on this? Was this feature implemented by the withConnectTimeout() and withIdleConnectionTimeout() methods that were added to the bootstrap?

https://github.com/adamfisk/LittleProxy/issues/23#issuecomment-105338505


add Symfony routing support for "action" type

Q
A

Bug Fix?
no

New Feature?
yes

BC Breaks?
no

Deprecations?
no

Fixed Tickets

No off course, the RequestStack was introduced AFTER Symfony 2.3! :skull:
Now I need to introduce another BC layer :tada:


How do I

Add this to my Ruby on Rails project? Sounds cool!

Well played.

nvr mind. im switching to CodeIgniter 2 instead.


Improve "required" validation in order to support "select" elements

Select one ...  (check one with "x")
[ ] bug
[ ] feature request
[x] enhancement

Expected behavior
Currently the "required" validation works only on input fields. It would be great if it works on "select" fields as well.
Actual behavior
If the "required" mechanism is used over "select" fields, the info icon is shown over the dropdown icon.
Reproduction of behavior
https://embed.plnkr.co/g3WmMI/
Environment details

Angular version: 4.x.x

Clarity version: all

OS and version: all

Browser: all

@kaleksandrov
This is a duplicate of the work currently being done on #1118
That work is currently in the design phase. Please subscribe to that issue or one of the issues related to it to track progress.
Thanks.

Hi @mathisscott
Thanks for the fast reply! I don't think this is a duplicate as #1118 is related to "optiona" parameters. The current issue is about extending its support to other DOM elements like "select" which currently is not supported.
Do you still think this is a duplicate?
There is no information about the state of this enhancement in #1118 - can you share a little bit more? When could we expect it to be shipped?
Thanks,
Kiril

@kaleksandrov
It's in design/research at the moment, so it is still a ways off.
I was wrong to point you to #1118, however. Because it is just one part of #932 <- which is what I should have directed you to.
Sorry for the confusion.


Octokit::TooManyRequests in Communication::Website::IndirectObject::SyncWithGitJob@elephant

Error in Osuny
Octokit::TooManyRequests in Communication::Website::IndirectObject::SyncWithGitJob@elephant
GET https://api.github.com/repos/osunyorg/bordeauxmontaigne-lesveteransduweb: 403 - API rate limit exceeded for user ID 90196448. If you reach out to GitHub Support for help, please include the request ID C2A2:3B47B6:1BBC320:1C058FA:66FAC329 and timestamp 2024-09-30 15:26:33 UTC. // See: https://docs.github.com/rest/overview/rate-limits-for-the-rest-api
View on Bugsnag
Stacktrace
app/services/git/providers/github.rb:129 - default_branch
app/services/git/providers/github.rb:133 - branch_sha
app/services/git/providers/github.rb:156 - tree
app/services/git/providers/github.rb:143 - tree_items_by_path
app/services/git/providers/github.rb:137 - tree_item_at_path
app/services/git/providers/github.rb:103 - git_sha
app/services/git/repository.rb:46 - git_sha
app/services/git/analyzer.rb:68 - exists_on_git?
app/services/git/analyzer.rb:12 - should_create?
app/services/git/repository.rb:86 - block in sync_git_files
app/services/git/repository.rb:84 - each
app/services/git/repository.rb:84 - sync_git_files
app/services/git/repository.rb:26 - sync!
app/models/communication/website/with_git_repository.rb:42 - sync_indirect_object_with_git
app/jobs/communication/website/indirect_object/sync_with_git_job.rb:4 - execute
app/jobs/communication/website/base_job.rb:29 - perform

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
Octokit::TooManyRequests in Communication::Website::IndirectObject::SyncWithGitJob@elephant

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::DirectObject::SyncWithGitJob@elephant

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::IndirectObject::SyncWithGitJob@elephant

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::DirectObject::SyncWithGitJob@elephant

An error linked to this issue has been reopened in Bugsnag
Octokit::TooManyRequests in Communication::Website::CleanAndRebuildJob@whale

An error linked to this issue has been marked as fixed in Bugsnag
Octokit::TooManyRequests in Communication::Website::CleanAndRebuildJob@whale


add support for useLink

https://router.vuejs.org/guide/advanced/composition-api.html#useLink

closed by https://github.com/kitbagjs/router/pull/180


ci: Updated workflows to pin commits to actions

Description
This pull request changes the following:

/.github/workflows/flow-hugo-publish.yml to pin commits to actions in the workflow

Related Issues

Closes #324

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Automator: update<EMAIL_ADDRESS>dependency in<EMAIL_ADDRESS>

Generated by Automator - 2021-01-25T21:18:14+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio_release-1.9
ea208ba91cb766586d13ff1881df20ac9de53331
link
/test integ-multicluster-k8s-tests_istio_release-1.9

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.

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-multicluster-k8s-tests_istio_release-1.9
ea208ba91cb766586d13ff1881df20ac9de53331
link
/test integ-multicluster-k8s-tests_istio_release-1.9

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.

/test integ-multicluster-k8s-tests_istio_release-1.9

/test integ-multicluster-k8s-tests_istio_release-1.9


el-patch-template

This is an implementation of the ideas in #50. I put it as a pull request to discuss the implementation and how it can be improved/refined.
All the suggested examples by @raxod502 should work. Currently, the only limitation is that ... does not work as expected inside el-patch-concat. In particular, I would expect it to match a substring so that one does not have to write the full string if one wants to replace a single word in a long string. The implementation of such a functionality is not difficult but I wanted to get some feedback before complicating the code further.
Also, currently el-patch-template simply returns the patch form rather than yanking it to the kill-ring or executing it. For now, this can be done with
(kill-new (format "%S" (el-patch-template ...))
(eval (el-patch-template ...))

respectively. (In this instance ... should be filled. el-patch-template is not magic :) )
Any feedback on the syntax or my lisp is much appreciated (I am not an expert with lisp).

String substitution now works as well. Now an el-patch-template with a string can be short an sweet
(el-patch-template
 (defun (el-patch-swap restart-emacs radian-new-emacs))
 (el-patch-concat
   (el-patch-swap
     "Restart Emacs."
     "Start a new Emacs session without killing the current one.")
   ...
   (el-patch-swap "restarted" "started")
   ...
   (el-patch-swap "restarted" "started")
   ...
   (el-patch-swap "restarted" "started")
   ...)
 (el-patch-swap
   (save-buffers-kill-emacs)
   (restart-emacs--launch-other-emacs restart-args)))

Thanks @raxod502. I've tested different forms and everything seems to work. Hopefully I didn't miss a use-case.
I've tried to follow the documentation standards as you suggested. I added a few questions in the code review that I would appreciate your input in.
Also, regarding your suggestions in #50. How about I create two versions:

el-patch-template evaluates the el-patch definition. If in init file prints a warning about the evaluation speed. If in compile time expands into the el-patch-* definition (Not 100% sure how to do that last one and would appreciate pointers).
el-patch-template* which simply returns the el-patch definition unless called interactively in which case yanks the definition in the kill-ring.

I don't know if/how I can combine all of these into one version depending on context.

How about I create two versions

Yes, two entry points seems right. I gave some thought to how to make the behavior of these functions the least surprising to the user, and came up with this proposal:

We have a macro called el-patch-define-template which doesn't actually compute anything. Rather it simply puts its arguments into a shared variable, just like defining a regular el-patch does (but this variable would be separate than the one used to keep track of all existing el-patch forms).
We have an interactive command called el-patch-insert-template which selects a template from the ones defined in the shared variable, like el-patch-ediff-patch, computes its expansion, and then inserts the expansion into the current buffer at point.
We can also have a macro called el-patch-define-compiletime-template, which will take the same arguments as el-patch-define-template, and do the same thing (namely, add arguments to a shared variable for later retrieval). However, it will also have an additional effect, which is to check whether macroexpansion is happening during compilation or not. If it is, then it will compute the template expansion and then macroexpand to the expanded template. If not, then it will skip that step and print a warning.

Then our two use cases look like this:

Simple, standard usage: Put an el-patch-template form into your init-file. Then call el-patch-insert-template to generate and insert the expanded patch into your init-file each time it's updated.
Advanced usage with byte-compilation: Put an el-patch-define-compiletime-template form into your init-file, and ensure that you byte-compile your init-file before loading it.

Also not sure how to do that last one

Here ya go!
(defmacro magic-macro ()
  (message "This message gets printed during macroexpansion")
  `(progn
     (message "This message gets printed at runtime")
     ,(if (bound-and-true-p byte-compile-current-file)
          '(message "The macro was expanded during byte-compilation")
        '(message "The macro was expanded at runtime"))))

(magic-macro)

And then you can see the results as follows:
% emacs -Q --batch -l magic.el
This message gets printed during macroexpansion
This message gets printed at runtime
The macro was expanded at runtime

% emacs -Q --batch -f batch-byte-compile magic.el
This message gets printed during macroexpansion

% emacs -Q --batch -l magic.elc
This message gets printed at runtime
The macro was expanded during byte-compilation

OK, I implemented those idea. I like the interface you suggested, but I find the fact that el-patch-define-compiletime-template throws an error during runtime a bit counterintuitive.
Instead, I made it so that el-patch-define-compiletime-template defines and evaluates a template when called in runtime. A warning is emitted in that case if el-patch-warn-on-eval-template is non-nil. If el-patch-define-compiletime-template is called in compile-time, the template is defined and its resolution is macro-expanded.
In addition to  el-patch-insert-template, I also added a function el-patch-eval-template which evaluates a template.

Sorry for the notifications! I just learned about drafts in github and converted the request to a draft

Oh, no worries, I disable notifications for newly pushed commits in any case :)

added a function el-patch-eval-template

Makes sense!

To my mind, this is the most intuitive behavior but the function name might need rethinking

Yeah, that seems pretty reasonable. Maybe could rename to el-patch-define-and-eval-template or something.

I figured we would want to have the template definition saved

Yep yep, that makes sense.

I don't know if I also need to handle the case when el-patch is not loaded

Yeah, I think we do need to handle that. It should be fairly straightforward though, I think you just need to autoload any variables that need to be defined for the macroexpansion to execute successfully even if el-patch isn't loaded, e.g.:
https://github.com/raxod502/el-patch/blob/5e823dc9a29e3be22597d93912f06119c38030d6/el-patch.el#L137-L141

I've added validation functions for templates (stolen from el-patch) and greatly simplified the implementation to avoid exceeding max-lisp-eval-depth when the template is very long.
In my tests, having my templates in my init file did not slow down my startup time significantly (especially when I autoload them). However, I am still debugging an issue where getting the source from .el.gz files fails sometimes; it seems that jka is somehow not fully loaded when my init file is executed. This might be related to my Radian config being loaded in early-init.el (see https://github.com/raxod502/radian/issues/474), but I am not sure yet.

Yeah, I think we do need to handle that. It should be fairly straightforward though, I think you just need to autoload any variables that need to be defined for the macroexpansion to execute successfully even if el-patch isn't loaded

Hmm... Maybe I am misunderstanding something here. Here's what I am thinking a use-case might be:

User generates a compiled file use-compiled-file.elc which contains el-patch templates and/or patches.
User puts (require 'use-compiled-file) in their init file. This loads their patches, i.e., their function definitions are evaluated. Loading this compiled module does not require el-patch or el-patch-template being loaded, nor does it load them. In fact, el-patch and el-patch-template need not be even available.
User later loads el-patch and el-patch-template (interactively or otherwise) and then is able to execute el-patch-* functions to validate their patches and/or templates.

In el-patch-template, the way I did this is by adding the template definition to el-patch--template, making sure to define it (without loading el-patch-template) if it wasn't bound. I thought a similar solution would need to be implemented for el-patch, i.e., the patch definition is added to el-patch--patches (without loading el-patch) and its resolution is macroexpanded.
Is this what you also have in mind? If so, maybe I am fundamentally misunderstanding autoloading. I thought autoloading variables would cause the package containing them to be loaded whenever they are used. Is that not the case?

having my templates in my init file did not slow down my startup time significantly

OK, good to know. I guess most people don't care about having literally the smallest number of milliseconds of startup time, and it's fine to support having the templates expanded during startup, as long as there's also an option to not do that.

It turns out that Radian sets file-name-handler-alist to nil

Oops, my bad :)

Here's what I am thinking a use-case might be

Your use case is the exact same one I have in mind.

In el-patch-template, the way I did this is by adding the template definition to el-patch--templates, making sure to define it (without loading el-patch-template) if it wasn't bound

That's a fine approach as well. It should have the same practical effect as what I suggested (autoloading the variable definition el-patch--templates).

rely on the user generating the autoload file and loading it correctly

By "the autoload file" do you mean the generated file which contains the autoloads of the el-patch package itself? If so, then I think it should be safe to assume that will be loaded correctly. package.el, straight.el, and other package managers should all take care of this automatically.
That said, it is true that if the user is installing and loading el-patch manually, then your solution would degrade more gracefully than mine. That would be a perfectly reasonable reason to go with your way, if you prefer it.
Note that the definition of el-patch--templates in the autoload file doesn't actually contain any user data: it's literally just (defvar el-patch--templates nil) if the variable is autoloaded. It's still up to the macroexpanded code to push values onto that list at runtime.

I couldn't find where the resolution of the el-patch is macroexpanded.

So, suppose you have this in your init-file:
(el-patch-defun company-statistics--load ()
  "Restore statistics."
  (load company-statistics-file 'noerror
        (el-patch-swap nil 'nomessage)
        'nosuffix))

Then it macroexpands to this (courtesy of https://github.com/joddie/macrostep):
(el-patch--definition
 (defun company-statistics--load nil "Restore statistics."
        (load company-statistics-file 'noerror
              (el-patch-swap nil 'nomessage)
              'nosuffix)))

And then the el-patch--definition macro expands again to:
(progn
  (puthash 'defun
           '(defun company-statistics--load nil "Restore statistics."
                   (load company-statistics-file 'noerror
                         (el-patch-swap nil 'nomessage)
                         'nosuffix))
           (or
            (gethash 'company-statistics--load el-patch--patches)
            (puthash 'company-statistics--load
                     (make-hash-table :test
                                      (function equal))
                     el-patch--patches)))
  (el-patch--stealthy-eval
   (defun company-statistics--load nil "Restore statistics."
          (load company-statistics-file 'noerror 'nomessage 'nosuffix))
   "This function was patched by `el-patch'."))

Where as you can see there is a puthash that installs the full text of the patch into the variable el-patch--patches. This would normally fail if el-patch.el has not yet been loaded, since the variable would be unbound (not even nil). However, since we autoload el-patch--patches
https://github.com/raxod502/el-patch/blob/5e823dc9a29e3be22597d93912f06119c38030d6/el-patch.el#L137-L141
then the package manager will copy the following into the autoload file:
(defvar el-patch--patches (make-hash-table :test 'equal) "\
Hash table of patches that have been defined.
The keys are symbols naming the objects that have been patched.
The values are hash tables mapping definition types (symbols
`defun', `defmacro', etc.) to patch definitions, which are lists
beginning with `defun', `defmacro', etc.

Note that the symbols are from the versions of patches that have
been resolved in favor of the modified version, when a patch
renames a symbol.")

which should be loaded before anything else happens in user configuration, even if el-patch.el is not actually loaded. Then, by time we get to evaluating the el-patch-defun form (or its macroexpanded/compiled version), the variable is defined and can be updated with the patch text.
Does that answer your question?

Does that answer your question?

Thanks for taking the time to write that answer. Yes, everything is clear now.
I didn't realize that macros keep expanding. It that case, the implementation should be complete now.
I added a section in the README and I think the branch is ready to be merged. Let me know if you think other changes are needed.

Thank you so much for your great work and patience! :rose:


Problem_Statement_83

A recent survey suggested that almost everybody knows that a palindrome is a string which reads the same backwards as forwards. Recently, Blacky invented a brand-new concept: K-palindromes. A string is called a K-palindrome if it is possible to make it a usual palindrome by replacing at most K characters. For example, a string abb can be made a palindrome by replacing one character, the second b with an a. Please note, that according to the definition, a usual palindrome is a K-palindrome for any non-negative integer K.
Blacky was walking in a garden and came across a string S of N characters. Now, he wants to know the sum of the lengths of all substrings of S which are K-palindromes. Note that two substrings are considered to be different if they cover the different ranges of indices, even if they are equal as strings.
Input
The first line of input contains an integer T denoting the number of test cases. Each of the next T lines contains a description of a separate test case.
The only line of the test case description contains two integers N and K followed by string S, all separated by single spaces. S consists of lowercase Latin characters only.
Output
For each test case, output a single line containing one integer: the answer for the test case.
Constraints
1 ≤ T ≤ 5
1 ≤ N ≤ 105
0 ≤ K ≤ 5
Sample Input 1
2
7 0 abacaba
7 1 abacaba
Sample Output 1
28
56
Explanation
Test case 1:
There are:
7 0-palindromes with length 1 (just each character)
3 0-palindromes with length 3 (aba, aca, aba)
1 0-palindrome with length 5 (bacab)
1 0-palindrome with length 7 (abacaba)
.
The total length: 71 + 33 + 15 + 71 = 28
Test case 2:
There are:
7 1-palindromes with length 1 (just each character)
6 1-palindromes with length 2 (each substring with length 2)
5 1-palindromes with length 3 (each substring with length 3)
3 1-palindromes with length 5 (abaca,bacab, acaba)
1 1-palindrome with length 7 (abacaba)
.
The total length: 71 + 62 + 53 + 53 + 7*1 = 56

Hey @priyanka989 , it seems that you have been already assigned some other issue. You will be assigned this issue only after the previous one gets closed :)

Hey Manpreet, I am sorry but the issues of this Hacktoberfest repo is only for Cummins College students who have registered.

Yaa, I am done with previous one


Moved the configuration variables out into a .env file.

Moved mongodb config out into a seperate .env file. A template for a .env file is left in the util.js where the connection string was placed.
This closes #29 and gets the code in a state to begin working on #32

Just wanted to make sure everyone seen this before merging the branch. The .env file will have to be created manually after this branch is imported into develop. But it should make it a lot easier to set up net configuration values.


Update service selector for etcd headless service

In #53 I forgot to update the label selector in the Service object for etcd. This fixes that regression.

/lgtm

/approve


Add performance note to Array.resize()

Adds a note about resizing ahead of time instead of adding new elements one by one. This would likely help some people trying to resolve performance bottlenecks.

This is kinda obvious but ... Why not)

It isn't to many, people might not now how data is allocated and how expanding reallocates and might have to move all the data, this is far from obvious even to non-beginners

Should this also be added to PackedArray classes?

Thanks!

Cherry-picked for 4.2.2.


[Desktop] Add option to not minimize to tray

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @jojejo in #desktop-development.

duplicate of #1649


#MySQL_Tasks. Dmitry Leonov

https://travis-ci.com/github/DmitriyLeonov/db-assignments/builds/176629478

accepted


Translate a Chinese README ?

hey @ParfoisMeng thanks for the suggestion.
How about sending a PR of translated Chinese README and I can work with you to get it reviewed/merged?

@jingwei423 My English is poor。Are you Chinese？Can you speak Chinese？😂---by Youdao Dictionary

Fixed in https://github.com/twitter/Serial/pull/35. Thanks!


Added ca_certificate, ‘noproxy, and no_revoke` options to client builder

I wanted to expose a few features I needed from curl:

noproxy - disable proxy usage for specific hosts / all hosts.
ca_certificate - allow specifying a custom root CA certificate bundle (useful for self-signed certs).
no_revoke - something curl only implements for Windows' Schannel. Without it I couldn't get custom CAs to work.

Thanks! This is a great library 😄

I really like those suggestions! I changed everything to match your comments.
Just a little wrinkle is that this code need to change a bit, so
.proxy("http://proxy:80".parse()?) needs to become
.proxy("http://proxy:80".parse::<http::Uri>()?)

Hmm, yeah that does look uglier than before. What about .proxy(Some("http://proxy:80".parse()?))? That's not quite as awkward. Unfortunately it means that even in our small example, the change isn't effectively backwards-compatible due to type inference changes.
I think we might be making a breaking change shortly anyway (#125) so making a breaking change here might be OK. I'm good with merging this as-is, but it won't be available until 0.8 is released.


PR: Add shortcuts to switch edit tabs for macOS

Description of Changes
Because macOS keyboards don't have PgUp/Down, I added shortcuts to switch edit tabs for macOS. The shortcuts are listed below.

command + 8 -> switch to the left tab
command + 9 -> switch to the right tab

Issue(s) Resolved

Fixes #1741
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @ryohei22

I learned that command + fn + Up/Down works instead of PgUp/Down. Still, I believe the shortcuts I added are way more convenient if there are no conflicts with other shortcuts.

Hey @ryohei22, thanks a lot for your contribution! We'd like to include it in our next release in the Spyder 5 series. For that, please make your branch to derive from our 5.x branch (instead of master), with the following commands:
git checkout 5.x
git checkout switch_tab_shortcut_for_macOS
git rebase --onto 5.x master switch_tab_shortcut_for_macOS
git push -f origin switch_tab_shortcut_for_macOS

If you decline to do that, your work will be part of Spyder 6, to be released at the end of the year.


Make location parameter inline to fix issue 1508

Make location parameter inline, so that AutoRest will not generate it as
a property of client.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Issue #1508

@dsgouda , thanks, I have opened a new PR against 'current' branch: https://github.com/Azure/azure-rest-api-specs/pull/1532


TCP listener connection rebalancing

This commit introduces optional connection rebalancing
for TCP listeners, targeted as cases where there are a
small number of long lived connections such as service
mesh HTTP2/gRPC egress.
Part of this change involved tracking connection counts
at the per-listener level, which made it clear that we
have quite a bit of tech debt in some of our interfaces
in this area. I did various cleanups in service of this
change which leave the connection handler / accept path
in a cleaner state.
Fixes #4602
Risk Level: Medium
Testing: Unit/integration/manual
Docs Changes: Added
Release Notes: Added

This is ready for review. @danzh2010 @jmarantz do you mind taking a first pass?

/azp run envoy-macos

cc @oschaaf also if you want to take a look.

So I wanted to share some thoughts. As I understand it, currently a connection/transaction is fully handled on a single thread. If we migrate sockets because of rebalancing, will we see a transaction for client <-> Envoy and Envoy <-> Origin being handled on different threads?
I wonder, how would that impact performance? And also, will plugins/extensions get caught off-guard?

We can bring in another reviewer who has more familiarity the subsystems you are modifying to help as well

I think @danzh2010 is an expert in this code so she can cover.

One medium-level comment: I see changes to the integration test infrastructure, and to unit tests, but I was thinking there might be a new integration test demonstrating the new dynamics.

See integration_test.cc. I modified the stats test to actually do balancing. I also verified that without balancing that test does not work reliably over 1000 runs.

So I wanted to share some thoughts. As I understand it, currently a connection/transaction is fully handled on a single thread. If we migrate sockets because of rebalancing, will we see transaction handling for client <-> Envoy and Envoy <-> Origin split over different threads?
I wonder, how would that impact performance? And also, will plugins/extensions get caught off-guard?

We only do rebalancing at listener accept, so once a connection is accepted, it will stay on that worker forever and have similar characteristics as today. I don't foresee any performance implications beyond the (hopefully positive) ones that this change is targeted for in particular use cases. I also don't think this will have any effect on extensions as this happens before any extensions are run.

@jmarantz @danzh2010 updated per comments. @jmarantz I tried to address your comment about the assert and lack of test. It's a little ugly but I think covers it. Let me know what you think.

@danzh2010 @jmarantz updated per comments to date.

/azp run envoy-macos

@mattklein123 at the end of https://github.com/istio/istio/issues/18152, I add a test result based on envoy proxy 1.14.1(istio1.6.1), but seems the balancing is not good, could you please help to check there is any configuration error or else I missed? thanks,


Can use this project with ASP.NET 5 and MVC6?

If No. Is there any plan?

+1

No idea right now.

I'm working out the differences but it stems from the divergence from IAppBuilder in the new pipeline builder. Admittedly, this can be reverted back to the "old" OWIN pipeline but, let's face it, if you're on vNext, you're not about reverting back ;)
I'll report back with the specific findings when I get to a working implementation.

Well, the core of MR is separate from whatever cookie middleware you use. So in theory MR should work just fine w/ ASP.NET 5 -- you'd just need to bridge the gap with a ASP.NET 5 specific AuthenticationService (the thing that manages the cookie).
Also, though, to make MR more ASP.NET 5 friendly, I'd really want to make some breaking changes and make everything Task-centric. That's more work/time I don't have right now.

That's what I'm seeing as well: it's just the configuration helpers that are antiquated. I appreciate your ambitions and hesitations for the vNext targeted revamp. What would you think about a shim project to include the new helpers in the meanwhile? Either way, I'll share my code with you (when I have the opportunity to write it, that is!)

I finally go around to getting MR working with ASP.NET 5 / MVC 6. I intend to document my findings but the most jarring diff is due to reading settings from ConfigurationManager. I've been able to sidestep it via dependency injection using the following:
// reads configuration from appsettings.json
services.AddSingleton(p => new MembershipRebootConfiguration<ApplicationUser>(p.GetService<IOptions<SecuritySettings>>().Value));

However, I just hit an unavoidable wall in the SmtpMessageDelivery due to the fact that it's reading settings from ConfigurationManager without constructor a override for SmtpSection. It's not a huge setback since the class is small and unlikely to change but, to my knowledge, I'll have to replace the class with a version that doesn't reference ConfigurationManager directly.
This dependency on ConfigurationManager seems to be the biggest issue in utilizing MR in vNext; which is not too bad!

Well, if you can come up with a proposal then I'm happy to consider it. Maybe just another ctor param for the from?

Yeah, that's exactly what I came up with:
[MembershipRebootReplacementNote(typeof(BrockAllen.MembershipReboot.SmtpMessageDelivery), "Dependency of ConfigurationManager for retrieval of SmtpSection values")]
public class SmtpMessageDelivery : IMessageDelivery
{
    private readonly StmpDeliveryConfig _config;
    private readonly bool _sendAsHtml;

    public SmtpMessageDelivery(StmpDeliveryConfig config, bool sendAsHtml = false)
    {
        _config = config;
        _sendAsHtml = sendAsHtml;
    }

    public void Send(Message msg)
    {
        Tracing.Information("[SmtpMessageDelivery.Send] sending mail to " + msg.To);
        if (string.IsNullOrWhiteSpace(msg.From))
        {
            msg.From = _config.FromEmailAddress;
        }
        using (var smtpClient = new SmtpClient())
        {
            smtpClient.Timeout = 5000;
            try
            {
                var message = new MailMessage(msg.From, msg.To, msg.Subject, msg.Body)
                {
                    IsBodyHtml = _sendAsHtml
                };
                smtpClient.UseDefaultCredentials = false;
                smtpClient.Host = _config.Host;
                smtpClient.Credentials = new NetworkCredential(_config.UserName, _config.Password);
                smtpClient.Port = _config.Port;
                smtpClient.EnableSsl = _config.EnableSsl;

                smtpClient.Send(message);
            }
            catch (SmtpException ex)
            {
                Tracing.Error("[SmtpMessageDelivery.Send] SmtpException: " + ex.Message);
            }
            catch (Exception ex)
            {
                Tracing.Error("[SmtpMessageDelivery.Send] Exception: " + ex.Message);
            }
        }
    }
}

Sure, send a PR if you'd like.

I'd be glad to. Are you wanting to maintain backward compatibility or would this be an acceptable breaking change?
I have identified at least one more non-vNext compatible concept regarding the RelativePathApplicationInformation which uses HttpContext.Current within the GetApplicationUrl method. I have a replacement method for this as well. Would you like me to continue posting such findings on this thread or save them for a PR?

I think a breaking change would be ok since it's work to support ASP.NET 5. I should start a new branch for it for the time being.

Since we're talking about breaking changes, I think I want to have the various APIs that gen a key (email, sms) to return that string as a return value. To me this is one of the most confusing parts for people using MR (rather than using a event handler).

hey @vinneyk i'm currently also working on this - do you want to create a pull request and i'll add my changes as well?
It might be a good idea to keep this in a separate branch for now while we have a chance to test

Hey @nikcub I probably won't get to it before the weekend. If you are quicker on the trigger, I'll follow your lead. Otherwise, yes, I'll fork and add my changes. Looking forward to working with you :)

Another thing I thought of -- all async. If async is ever going to get into MR, then this would be the time.
Thoughts?

I agree 100%.Do you care to have non-async options as well?

What are your thoughts about rebuilding the project on the new ASP.NET project templates? I'm thinking we'd start a new solution and just start porting projects into it one at a time. It would obviously make it more difficult to diff so your review may become more cumbersome. I don't know. What do you think? Would it be easier for you if we upgrade in place and then port to the new structure later (if at all)?

Put another way, is the aim to support ASP.NET 5 or embrace it?

@nikcub, I branched and added my few modifications in my fork. I've submitted a pull request to @brockallen. There were only two objects I've had to modify so far in order to get MR working in my MVC 6 application. In addition, I have had to include a couple settings for IServiceCollection and IApplicationBuilder configuration. That'll likely change be submitted, in some form, soon.

Sorry -- I missed your recent questions. Yea, I'm not sure about ASP.NET 5. If we do, then perhaps a new project name/assembly.etc -- I've not had time to think about it fully. Also, RC2 will bring about some changes... though, not sure how many would affect us at this level.

I saw @vinneyk pull requests about changing the target framework from 4.5 to 4.6.1, but not to the new light weight dotnet5.4.
Do you have any plan to port the projects, or create new ones to support the new .Net platform standard (dotnet5.4) framework?

@vinneyk thanks for that - i've pulled it into my fork and i'm going through it now - plan to work on it this weekend
To answer the question about how to setup the project - most projects that i've come across that are looking to port are splitting into separate projects.
and +1 to async

@VanLePham  will eventually be able to target coreclr

So do we need a new repo, or will these changes be usable from an old ASP.NET/.NET project? IOW, will these changes move MR into being more like a PCL?

From what I've seen thus far, we don't have to loose support for previous .NET versions. If we take the path of least destruction, we can simply replace dependencies on antiquated concepts and potentially support both (at least the non-core frameworks).
Admittedly, I've not had much opportunity to play with coreclr since I tend to have other dependencies which prevent it. That said, @VanLePham, I don't see any dependencies in MR which would prevent support so it should be doable. Though, as I understand it, we'd need to decide to draw a line in the sand and port to a completely new project. I could be wrong but it seems like that's the ultimate answer to your question, @brockallen: do we want coreclr support?

If we're going to rip off the bandaid, then why not support both.
To be honest, I was on the fence if I wanted to continue MR into ASP.NET 5/Core. ASP.NET Identity 3 technically has all the features necessary. The only real reason to keep working on MR was to help people support existing use.
Are there features in MR you feel are more useful than what's in ASP.NET Identity 3, such that it warrants the effort porting this to the new runtime?

You're right, Identity 3 does technically have the same features; on the surface at least.
Since I've really started to get to know MR, I've been more excited about what it has at it's core. The capability to customize the membership pipeline is a really great asset! For example, I'm writing a multi-tenant application to which users can be invited by another user. I really like the possibility of composing new membership features out of the event components. In this case, perhaps invited users aren't created using the same path as regular sign-ups. This is not something I've seen supported by ASP.NET Identity.
If you decide to deprecate support moving forward, then we can make the minimal changes required in order to add support for the full framework beyond 4.5.1. In fact, I've been able to get the current MR release working in 4.6.1 by providing a couple classes and a few lines of configuration so perhaps I could contribute that to your wiki. However, if you haven't already, I suggest you write an app on the new architecture and Identity library, or perhaps adapt an existing app with slightly more complex logic, and see for yourself if it's "good enough" for your liking. I would respect your insights if you said it was me who was missing the picture regarding Identity 3.

Maybe we start with a rev to support the minimal changes for ASP.NET Core. After that then we could maybe discuss having you contribute/fork to an ASP.NET Core version.

Did you mean to reference Core in both statements there?

I think I did :)
I did not meant to say that the next minor update of MR (mainly the one you're working on) would work on .NET Core.

Just wanted to let you know I'm still here. Big push for a demo this week so I'll continue to be quiet for a little while longer.

It's not a problem -- I don't have any cycles to put into this, so it's no rush for me.

Do you have any information of when that might drop?

https://github.com/aspnet/Home/wiki/Roadmap

Just heard your DNR interview with Dominick Baier. I'm guessing that roadmap doesn't fully encompass that 30 minute explanation of the versioning diagram but I did find the article linked on the RC2 release to be insightful. I respect this statement most of all:

It’s clear to us now that we were running too fast and didn’t take the time to fully think this one all the way through.

I agree with your earlier assessment  of waiting for RC2 as it seems that does indeed introduce some pretty radical changes. Are you getting much requests for support on using MR in RC1? If so, I could go ahead and write a wiki detailing how I got up and running. It's not altogether too involved but it did take me some time to get all the pieces in place. LMK

Are you getting much requests for support on using MR in RC1

Nope; this thread is it.

If so, I could go ahead and write a wiki detailing how I got up and running. It's not altogether too involved but it did take me some time to get all the pieces in place. LMK

Only if you really feel you need to or someone else here asks. Otherwise I'd save your energy.

I can certainly live with that :) For the most part, the necessary changes are already documented within this thread. That should be enough for anyone brave enough to be using RC1 anyways.

I was curious about it myself (how I found this issue), but like @brockallen said I don't really see what problems MR solves that ASP.NET Identity 3 doesn't.

I still think there are many ways in ASP.NET Identity to shoot yourself in the foot that MR prevents.

I too was curious about adding the support for async/await in the repo.  I am currently using MR with identityserver and am working on calling the repositories through web api service calls.
I could not tell from this thread, is this a change that you are looking to make MR, or do you not feel it is worth it?

I think it's a good idea. It would certainly be a major breaking change.

Yea, I was going to look at how big of change it would be, but I did not know based on your guys' discussion above, if some of it was already being looked into.

Sure, and I know I was vague :)
I just honestly don't know if I have time in the next ~6 months. Is someone here interested in stepping up and helping maintain?

I'm interested in porting it and doing a deep comparison feature-wise as I do so, but i'm wondering if I should wait for RC2 before I tackle this.

I just spent a day going over all of the new AspNet Identity 3 code and features. Some of the messiness of AspId 1&2 has now been cleaned up and simplified, IMO (much of that is due to a standard DI system in ASP.NET Core).
I then went and looked at the readme here to see what the purported feature list was for comparison. AspId3 has all of those features covered except for the event-bus feature and nested role definitions. On top of it, AspId3 is async, has explicit storage for tokens (minor feature IMO), security stamp validation, and arbitrary claims on roles (which somewhat makes up for the nested roles feature).
At this point, I don't think it makes sense to try to push MR forward into ASP.NET Core now that AspId3 has finally caught up with (and in many regards surpassed) MR.
What I could see going forward is: 1) a MR user store in AspId3 to maintain the existing MR DB/schema/data, and/or 2) a migration tool to move the MR data to AspId3. In either case there is a need to improve on AspId3 with an iterative password hasher (as I did with IdentityReboot), especially if existing MR data needs to be moved to AspId3.
In a sense, MR has served its purpose -- I'd like to think it somewhat forced Microsoft (and perhaps guided them even) to address the state of their identity management and bring it into a more modern time. I appreciate all the of kind and encouraging words I've heard about MR.

Brok, another feature of MR is that it provides guidance with regard to higher level workflows around password reset, change of email, etc. Specifically I'm thinking of the methods on the UserAccountService class for executing these workflows.
In your exploration of AspId3 did you find a comparable set of operations implemented?

No they don't force the same set of requirements around those areas.

So in summary:

there are a number of features in MR that are not available in AspId3
it is bad use of someone's time (certainly bad use of yours) to rewrite MR against Asp Core given just these features

I think you're right. I also think that it makes sense for a new project to be created "on top of" AspId3 that provides some of the features from MR.
You already hinted at something like this. But correct me if I 'm wrong, you have thought of this as more of a migration project with the implication that only existing MR consumers would use. Whereas I see this as providing value to anyone using AspId3.
From me the important features from MR that would be included in this new project:

higher level workflow support
event bus
multi-tenancy

C

Yep, all correct and agreed.

My opinion is that if any of these features are desired in .NET Core, then they should be added on top of ASP.NET Identity 3.

@brockallen thanks for your time looking through AspId3.  You mentioned that

Multi-tenancy is easily added by tweaking the AspId3 code in the DI system.

After looking through the code base of AspId3 I am a bit perplexed on how this could be done.  For example in the UserStore, there is code like this:
public virtual Task<TUser> FindByNameAsync(string normalizedUserName, CancellationToken cancellationToken = default(CancellationToken))
{
  cancellationToken.ThrowIfCancellationRequested();
  ThrowIfDisposed();
  return Users.FirstOrDefaultAsync(u => u.NormalizedUserName == normalizedUserName, cancellationToken);
}

Other than say intercepting the EF db connection and rewriting commands to include tenantid or authoring my own IUserStore with a DI'd tenant context, multi-tenancy feels out of reach.
I'm most likely missing something here, could you please point me in the right direction?

You'd dynamically change the stores based on the tenant in DI -- this means you need to implement the delegate to create the dependencies.

@brockallen By store, I'm assuming your referring to the physical db.  In our case we have a single db with it's tables keyed off of tenantid.  Would you suggest we move away from that approach to a db per tenant?

I mean the IXxxStore or DbContext instances. If you have one DB with a tenant column, then you'd need to instantiate the IXxxStore or DbContext and set a tenant property so that it can be included in the query. The other approach could be to inject the IHttpContextAccessor int eh IxxStore or DbContext.

understood, thanks for your help.

@brockallen It sounds like the best option for a local identity store (after catching on up these threads) is to go with the ASP.NET core identity, but it sounds like there are a few short comings to that solution that extensions would need to be developed to fill in the gaps for things that MR did that ASP.NET core identity does not.  Do you know of anyone currently working on a project to do this?  Figured I would ask.  We are looking at IdSvr4 now. We were on IdSvr3 + MR and now we're trying to figure out the roadmap to move forward since it sounds like MR is discontinued.


feat: import SDR for metadata types

Import SDR for the metadata information. Still need to declare supported meta suffixes for this plugin, but this will import the remaining information. BotVersion requires temporary code due to bug in the SDR metadata registry.
Field Names renamed to Unique ID Elements to match SDR.
fixes translation XML name which affects v1.0.0
Resolves https://github.com/mcarvin8/sfdx-decomposer-plugin/issues/21

Successful testing. Merging to push fix for Translations.


Terra Alliance API Endpoint are missing in API Swagger REST API

this url works /terra/alliances but is missing in the auto generated swagger documentation.
Sample on e.g. Terra: https://phoenix-lcd.terra.dev/swagger/

Good observation Migaloo needs this too. @faddat

Related to #144


Created a nicer readme file. Issue #2

Readme file using codeblocks and examples I got from the link in the original readme. Fixed issue #2 .

If I misunderstood what I had to do, which I might have. (I used the info in the link provided in the readme)
I can always make a new file if you give me the correct info.


Github Action Cypress run with i18n works locally but not in Github Action

So I have one test case look like this:
it('Show translation based on the language', () => {
    cy.window().should('have.property', 'store');
    cy.window()
      .its('store')
      .invoke(
        'dispatch',
        setConfig({
          lang: 'de-DE'
        })
      );
    mount(renderWithIntl(<Component />));
  });
  it('Shows translation fr', () => {
    i18n.changeLanguage('fr-fr');
    cy.window().should('have.property', 'store');
    cy.window()
      .its('store')
      .invoke(
        'dispatch',
        setConfig({
          lang: 'fr-FR'
        })
      )
      .then(() => {
        mount(renderWithIntl(<Component />));
        cy.get('[data-testid="title"]', { timeout: 20000 })
          .should('be.visible')
          .should('have.text', 'Sélectionner');
      });
  });

The second block successfully works in local, but always failed in Github Action with this error message:
Timed out retrying after 20000ms
      + expected - actual

      -'Select'
      +'Sélectionner'

Any insight why it works fine in local, but always failed in Github Action?
here are my versions:

"cypress": "12.14.0"
cypress-io/github-action@v5
"react-i18next": "11.17.2",
"i18next": "21.8.10",

@darrylsepeda
It's unlikely that the problem is directly caused by github-action. More likely would be differences in timing running in a GitHub runner compared to running locally.
What is your *.yml workflow?
You may also want to consider tapping into the know-how available within the Cypress technical community on Discord, and ask for their advice.

I agree with @MikeMcC399 's assessment.  Can you share your workflow file as well as a repo demonstrating the problem with the full test?

Unfortunately we have to close this issue due to inactivity. Please comment if there is new information to provide concerning the original issue and we can reopen.


Remove dependency between devworkspacerouting and devfile api

What does this PR do?
This PR removes the dependency between devworkspacerouting and devfile api
What issues does this PR fix or reference?
https://github.com/eclipse/che/issues/20844
Is it tested? How?

Deployed che on minikube with:
chectl server:deploy --installer=operator --platform=minikube --workspace-engine=dev-workspace

and then did
make docker install

inside of this repo and verified that everything was starting correctly. I also did the same steps on an rhpds cluster and I was able to start both the bash and the python devfiles successfully
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

/test v8-devworkspace-operator-e2e


Expand functionality of message channels by introducing a Channel ID

This PR introduces the ChannelId for the MessageChannel, the utility Channels for working with message channels, the Router for routing messages to the corresponding message channels and the RoutingSchema for storing Routes.
Highlights:

The ChannelId is the identifier of a channel based on some grouping. For instance, it can be TypeUrl allows grouping messages by the same message type.

Channels is the utility class for working with message channels and at the moment can generate channel identifiers for various objects for example for MessageClass.

Router is the base interface for routers. The router can be used to route a message based on some conditions which can be updated in runtime. Inspired by Dynamic Router pattern.

RoutingSchema is the base interface for routing schemas. RoutingSchema can be used to store message channel routes. Currently in Spine presented only the InMemoryRoutingSchema.

Route is the base interface for routes. It contains public method
MessageRouted accept(ExternalMessage message) which checks if the passed message suitable for the route or not.

Prior to these changes, the message channel was strictly tied to the type of messages it can pass. There are places in Spine in which messages should be grouped not only according to the message type. Therefore, a ChannelId has been introduced to solve this problem. At the moment ChannelId consists only of one possible grouping identifier, the message_type_url. It can be used to group messages in a channel by the MessageClass.
The method Channels.newId(MessageClass messageClass) can be used to generate the ChannelId related to the MessageClass.
In the nearest future will be added more channel identifiers for other needs.
Also, in the scope of this PR was refactored the IntegrationBus which uses message channels grouped by a message class.
The framework version is set to 0.10.2-SNAPSHOT.

@armiol PTAL

@armiol PTAL

@armiol PTAL, also I would like to discuss the command MessageSuitableByMessageType.

@armiol PTAL.

@armiol PTAL. I still need to finish some tests but I would like to get feedback on the existing code.

@dmitry-ganzha please complete the tests before the review starts. Feel free to notify me once it's done.

@armiol PTAL.

@armiol PTAL.

This feature is now included into #689.


Clearing Operations tools - lyrx file not properly being represented in Model output

Layer symbology is not being properly displayed with ArcGIS Pro project. The model does utilize the lyrx but does not display labelling or maintain the symbology for the labels once turned on.  The tools also finished with all features in the layer selected.
Current result from the tool:

Desired result (obtained from applying lyrx afterwards):

A temporary fix that I have done is to add the "Apply Symbology From Layer" tool to the model.  I was not able to simply drag and drop the tool into the model however.  I had to copy the tool into my project toolbox first then and only then was I able to drag the tool inside of the model.  I do not think this was the intended process from development.
┆Issue is synchronized with this Asana task

@mfunk - same as https://github.com/Esri/solutions-geoprocessing-toolbox/issues/219. I would verify with Pro 1.1 daily builds.

In testing this one I'm getting errors and the tool is NOT working (see issue #362). Going to defer this one until the other is resolved.

It is a known issue that the lyrx file will not apply labelling, the work around we have implemented is a task step to use the apply symbology gp tool.

This is no longer an issue because we have removed the models from the toolbox. Now the script tool handles everything correctly.


[Req] Enable automatic login checkbox

Back in the "good old days", when you fired up netplwiz, there was a check box to enable automatic login.  There is a registry tweak to re-enable it; it should be a simple thing to add.
Alternatively, you can have the tool install the Microsoft Autologin utility.
Thanks.

Just scanning through and are you retarded?   An application that auto logins?
--
Brad McConnell

On Sep 14, 2022, at 4:17 PM, N3EOP @.***> wrote:

Back in the "good old days", when you fired up netplwiz, there was a check box to enable automatic login. There is a registry tweak to re-enable it; it should be a simple thing to add.
Alternatively, you can have the tool install the Microsoft Autologin utility.
Thanks.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

I can't do a checkbox, but I can make a script that will prompt for questions like user name, domain, password then put those in registry for autologin.

Added to test branch using Microsoft's sysinternals method.
commit 8becf46bbd2c975f7df3c7482c19534f969fdf18