fix: add authorizationGroups property to K8s SAR authorization, fixes #506

@guicassolato I was thinking back to an authorization requirement we had in managed openshift connectors, where we were authorizing against an org field in JWT, and a groups claim. I'm wondering whether we should support the following scenarios as well:
* Groups selector could resolve to a single scalar string

* Multiple groups selectors are needed to aggregate a list of groups

@dhirajsb, I think it should be straightforward and match the SAR API, i.e., authorizationGroups always resolves to an array of strings.
For cases like the one you described, one can always use CEL. E.g., the following resolves to a list containing a single string equal to the org name used as group.
authorizationGroups:
  expression: [auth.identity.org_name]

Because it's CEL, we can do fancy stuff. E.g.: [auth.identity.org_name] + auth.identity.groups.

Because it's CEL, we can do fancy stuff. E.g.: [auth.identity.org_name] + auth.identity.groups.

I was thinking about CEL after I wrote that comment, but wasn't sure how capable it was. Good to know we can cover fairly complex use cases with it. :+1:

Thanks for testing a built version @guicassolato . I'm also working on testing this locally with a modified model registry. I'll let you know if I run into any issues.


Add an option to stage docker images locally to KIND

This PR addresses a compromise for development workflows requiring different patterns for loading images into the KIND / kubernetes cluster.

For casual / default usage, the docker images are loaded from the public container registries (docker.io and ghcr.io)

For developers with network issues connecting to public registries, this PR allows for an offline "pull" and stage to the KIND control plane:

export TEST_NETWORK_STAGE_DOCKER_IMAGES=true
./network kind     # << this will pull from the public repos, and run kind load docker-image ...

./network up

For test/development of the CI latest build outputs, the container registry and revision can be overridden:

export TEST_NETWORK_FABRIC_VERSION=amd64-latest
export TEST_NETWORK_FABRIC_CA_VERSION=amd64-latest
export TEST_NETWORK_FABRIC_CONTAINER_REGISTRY=hyperledger-fabric.jfrog.io

./network up

For active development of core Fabric images (e.g. peer, orderer), the KIND control plane can be directly loaded with local builds:

make docker # (in fabric)

export TEST_NETWORK_FABRIC_VERSION=2.4.0

./network load-images
./network up

@mbwhite and @SamYuan1990 can you please give this PR a test run to double-check that it meets your target use cases?   Matthew I had some difficulty testing out PR #507 and the candidate-use-builtin-ccs-builder branch with the mainline network scripts.  I think this is a better fit for that workflow.
Signed-off-by: Josh Kneubuhl<EMAIL_ADDRESS>

yuanyi@192 test-network-k8s % docker images | grep localhost:5000/fabric-ca
localhost:5000/fabric-ca                                          1.5.2                                                   4ea287b75c63   7 weeks ago     69.8MB
yuanyi@192 test-network-k8s % docker pull localhost:5000/fabric-ca:1.5.2
1.5.2: Pulling from fabric-ca
Digest: sha256:faa3b743d9ed391c30f518a7cc1168160bf335f3bf60ba6aaaf1aa49c1ed023e
Status: Image is up to date for localhost:5000/fabric-ca:1.5.2
localhost:5000/fabric-ca:1.5.2

and it seems harmless to pull the image again?

Hi Sam, no this is incorrect.  With this PR we no longer use the localhost:5000 registry for core fabric images:

The localhost:5000 registry is used for building, testing, and running chaincode and gateway client applications.

The kind image plane is used to run the core fabric images.

Here are four different scenarios:
A)  Default use case:  fabric images are pulled from public docker.io and ghcr.io repositories directly into KIND:
./network kind
./network up

B)  Network errors reading from docker.io/ghcr.io into KIND.  Solution : pre-pull and load images into the KIND control plane:  (This is option (A) above)
export TEST_NETWORK_STAGE_DOCKER_IMAGES=true

./network kind
./network up

C)  Run the daily/CI builds of fabric (not available at docker.io):
./network kind

export TEST_NETWORK_FABRIC_VERSION=amd64-latest
export TEST_NETWORK_FABRIC_CA_VERSION=amd64-latest
export TEST_NETWORK_FABRIC_CONTAINER_REGISTRY=hyperledger-fabric.jfrog.io

./network up

D) Run a local / custom build of core fabric images:
./network kind

make docker # in fabric/

./network load-images
./network up

The important change here is that this no longer uses the localhost:5000 registry for core fabric images.
Also in general it is OK to re-pull an image, but preferable to denote this only when using an imagePullPolicy: Always and the latest tag for images.  This is OK for interactive development but not ideal for production release pipelines, which should use clear labels/tags tied to semantic revisions numbering and the imagePullPolicy: IfNotPresent strategy.
@SamYuan1990 can you try option "B" above and see if this solves your issues loading the fabric base images?

@jkneubuh,

localhost:5000 is just a sample here for me to do the test.
Let's talk about the 4 options.
In my point of view,

The different between Option A/B is that we docker image from local docker and load into kind or not.

export TEST_NETWORK_STAGE_DOCKER_IMAGES=true

It resolve may things, as for sample the network issue/delay with local kind to access remote docker reg.

C is a specific case that show customer use image... well it may due to ci using other image reg?

And for B/D share one case that upload image from local to kind.(same way as A/C)

so, just focus on load image to kind or not.

AC is the same case as download image via kind.
BD is the same case as load image from local to kind.

Description
Image via kind
load Image

Default image
A
B

Customer image via Env/Make
C
D

which in my point of view,
Plan B/C/D, as kind fails to download image from docker reg.
export TEST_NETWORK_STAGE_DOCKER_IMAGES=true
./network kind

<customer script here to download the images>
#B: docker pull
#C: export TEST_NETWORK_FABRIC_VERSION ...
#D: make docker # in fabric

./network load-images
./network up

considering, it seems no harmful to pull image again.
yuanyi@192 test-network-k8s % docker images | grep localhost:5000/fabric-ca
localhost:5000/fabric-ca                                          1.5.2                                                   4ea287b75c63   7 weeks ago     69.8MB
yuanyi@192 test-network-k8s % docker pull localhost:5000/fabric-ca:1.5.2
1.5.2: Pulling from fabric-ca
Digest: sha256:faa3b743d9ed391c30f518a7cc1168160bf335f3bf60ba6aaaf1aa49c1ed023e
Status: Image is up to date for localhost:5000/fabric-ca:1.5.2
localhost:5000/fabric-ca:1.5.2

in which case, ./network load-images  and export TEST_NETWORK_STAGE_DOCKER_IMAGES=true duplicated.
we can change the behavior to below and remove TEST_NETWORK_STAGE_DOCKER_IMAGES ?
./network kind
# costumer scripts here
./network load-images
./network up

Hi @SamYuan1990
When TEST_NETWORK_STAGE_DOCKER_IMAGES=true, the images are:

Pulled from TEST_NETWORK_FABRIC_CONTAINER_REGISTRY  (calls pull_docker_images)
loaded into the KIND control plane.      (calls load_docker_images)

When running network load-images:

images are loaded into the KIND control plane (calls load_docker_images)

Is there something about the use case above that makes it difficult for your use case?   If you have custom scripts to pull images locally, then the option "D" is also available.
@mbwhite does this new scheme enable your scenario to run with local Fabric images?  I was able to run this without the auto "pull" overwriting the local images.


Hrm, this is an interesting one. Thanks for filing an issue — I'll try to reproduce this tonight. :)

If you're running 0.6.2, the problem is the same as in #206, where the crawler is actually started twice, which generates two main loops, of which only one is cleared when the crawler finishes. Solution would be to remove the crawler.start call on line 19 (or use the latest master, which protects against the crawling starting again when it's already running).
A new release is coming some time in the next two weeks that protects against this scenario as well!

Closing this until further notice. Just let us know if the problem persists, @weisjohn!


add utils and numeric ops for Value

TODOs:

[x] Doc
[x] Tests

@chfanghr any blockers here?

Nope, let me address the comments from @szg251 and then we can merge.

@chfanghr thank you!


core / eosjs: support for offline signing

It seems its not possible to use offline signing with scatter right now
It would be nice to have API support in the plugins for offline transactions.

its possible with the hookProvider scatter.eosHook
:)


docker-compose is deprecated

From July 2023 Compose V1 stopped receiving updates. It’s also no longer available in new releases of Docker Desktop.

https://docs.docker.com/compose/migrate/
I think it is sufficient to replace the - with a space in the readme
https://github.com/ER-FIZKarlsruhe/fiz-oai-docker/blob/64b7ead2e2ee5f578025e136e5423b4ecc468bb3/README.md?plain=1#L13C24-L13C25

README has been adapted.


Replace IndexRequest.Builder.value() call with call to .document()

Description
Current documentation for the new  Java client uses a call to org.opensearch.client.opensearch.core.IndexRequest.Builder.value() but as of 2.2.0 I do not believe this method exists. I believe the correct method to call is document()
Please double check that this is correct! I have not scoured the commit history of the relevant project to make sure that this method used to be called value()!
Issues Resolved
Update documentation to reflect the state of the 2.2.0 release of the opensearch-java client with regards to indexing a document.
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Thank you, @VachaShah! We'll change in all versions.


[WIP] Implement block / indent based parsing

... and enforce that defs can only occur in blocks (or, inside parenthesized expressions)
... plus some refactoring

Sorry @joshuawarner32, I cancelled this run, I need the servers to release basic-ws, which Luke needs for the meetup in 45 minutes.

Aha! I was wondering what happened. Better cancel this run too, since I just squashed and pushed

Servers are available again @joshuawarner32

I would personally appreciate Doc comments in the parser

👍

I noticed a new program crates/compiler/test_syntax/src/bin/minimize.rs, what is this used for?

This is a debugging tool I built while working on these parser changes. There were a few cases where I had the parser mostly working (all the unit tests passed) - except for one of the larger examples was failing. minimize applies some simple heuristics to try to find a smaller example that fails to parse in the same way as the original one, with the intent of being easier to debug.


adds the turrets back to the nukie ship

About the PR

adds the turrets back
1 on the back
2 on the front
3 on each side
1 in the cockpit
1 in the break room
1 in the power room
1 in that horizontal hall above the break room
moved the gravity generator to the south part of powergen to fit the turret better
moved the power monitor console so the turret doesnt shoot that instead of the doorway
moved the disposals unit in the break room
removed the chairs and banners in the horizontal hall, replaced banners with wall flags
Why / Balance

too easy for non-kies to break in and FTL the ship with the nuke and make it unwinnable for nukies without admin intervention
lasers invalidate em anyway
Technical details

i had to do code surgery to get this to work
Media

all types of reinforcement + commander not gettin shot

dots placed on the turrets

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog
Make sure to take this Changelog template out of the comment block in order for it to show up.
:cl: JoeHammad

add: the nukie shuttle now has its turrets back, think twice about breaking in!

12:46 i go to bed

None of the issues that originally caused their removal seem to be addressed, i.e. parking it on top of the nuke.

Why were they removed? The PR that removed them does not have a lot of details.

someone planted nuke close to shuttle so its turret always covered it, really shitty tactic

make it unwinnable for nukies without admin intervention

just drag the nuke with you

None of the issues that originally caused their removal seem to be addressed, i.e. parking it on top of the nuke.

Here are some ways to satisfy this:

Make sure the nuke cannot be unanchored when armed & counting down
Also make sure that the floor under it can't be cut off to prevent cheese
Prevent nukie ship from parking too close to station

None of the issues that originally caused their removal seem to be addressed, i.e. parking it on top of the nuke.

Here are some ways to satisfy this:

Make sure the nuke cannot be unanchored when armed & counting down
Also make sure that the floor under it can't be cut off to prevent cheese
Prevent nukie ship from parking too close to station

Or you could just make the turrets not fire on people on a different grid.

aka only put them on the inside

Now there are restrictions that a nuclear bomb can't be put close to space.

insane idea but what if we made it station nuke only and that nuke remained anchored at all times

No because that makes it too easy. There's been enough playdata from 13 to show a regular nuke can work fine, when coded properly.

insane idea but what if we made it station nuke only and that nuke remained anchored at all times

No because that makes it too easy. There's been enough playdata from 13 to show a regular nuke can work fine, when coded properly.

easy for whom

if its too easy (for nukies presumably) remove the random code and just make it always give the code to the infiltrator's nuke

if its too easy (for nukies presumably) remove the random code and just make it always give the code to the infiltrator's nuke

I don’t really see how it’s too easy for the nukies when it gives the crew a consistent location to defend which also allows large and dramatic firefights to occur (the highlight of the mode)
babysitting a bomb is pretty boring but I wouldn’t call it hard when you can just dump it or wall off some exterior part of the station

just readd internal turrets only and should be fine, also take into account that nuke actually needs to be inside now to be armable

test fail seems erroneous

Or you could just make the turrets not fire on people on a different grid.

place lattice under yourself and turrets will ignore you

No because that makes it too easy. There's been enough playdata from 13 to show a regular nuke can work fine, when coded properly.

keep in mind that in ss13 (TG station) the nuke cant be disarmed without the disk, which can be taken out after arming (because nukies need to escape alive to get major)

thing is if i remove the turrets from the front you can just laser the turret in the cockpit for free.. but you could just close the shutters actually

okay ill remove the turrets from the outside but i'm keeping the one on the inside and at the back

all turrets have been removed from the outside except for the one at the back

erroneous test fail

Here are some ways to satisfy this:

Make sure the nuke cannot be unanchored when armed & counting down
Also make sure that the floor under it can't be cut off to prevent cheese

if its unanchored you dont get syndie major

idc if i get banned for being off topic or rude or w/e but you are literally the worst PR creator for the history of this game, no clue why you were un repo banned and I would genuinely spend your time wiser elsewhere. also if you switch the 1844 to 1488 in your name it becomes a hate symbol, always found that kind of odd.

idc if i get banned for being off topic or rude or w/e but you are literally the worst PR creator for the history of this game, no clue why you were un repo banned and I would genuinely spend your time wiser elsewhere. also if you switch the 1844 to 1488 in your name it becomes a hate symbol, always found that kind of odd.

Christ, calm down, how else do you expect people to learn and improve?

idc if i get banned for being off topic or rude or w/e but you are literally the worst PR creator for the history of this game, no clue why you were un repo banned and I would genuinely spend your time wiser elsewhere. also if you switch the 1844 to 1488 in your name it becomes a hate symbol, always found that kind of odd.

Christ, calm down, how else do you expect people to learn and improve?

idk the 1844 / 1488 thing always struck me as weird tho

fellas, is it hateful to checks notes have 4 random numbers at the end of your name?

Maybe i understand one in the cockpit, everywhere else is meh in my opinion

also if you switch the 1844 to 1488 in your name it becomes a hate symbol, always found that kind of odd.

This doesn’t even make sense???? Why are you randomly switching a 4 out for a 8????

idc if i get banned for being off topic or rude or w/e but you are literally the worst PR creator for the history of this game, no clue why you were un repo banned and I would genuinely spend your time wiser elsewhere. also if you switch the 1844 to 1488 in your name it becomes a hate symbol, always found that kind of odd.

huh

Don't worry about it

first they came for lex sosa
i did not speak out because i was not lex sosa
then they came for the maintainers
i did not speak out because i was not a maintainer
but when they came for the contributors, there was no one left to speak for me

please keep discussion relevant to the PR. thank you.

it definitely needs the internal turrets to stop people from just taking the shuttle and flying off then proceeding to do nothing the remainder of the shift
also stops nuke stealing if nukies leave it on the ship
needs to make sure people can't just break the front window and ignore the turret because it's behind the console, or build a thindow to be able to pilot the console from behind while not in los of the turret
could relocate the navigation console deeper in maybe?

it definitely needs the internal turrets to stop people from just taking the shuttle and flying off then proceeding to do nothing the remainder of the shift also stops nuke stealing if nukies leave it on the ship needs to make sure people can't just break the front window and ignore the turret because it's behind the console, or build a thindow to be able to pilot the console from behind while not in los of the turret could relocate the navigation console deeper in maybe?

there are shutters

it definitely needs the internal turrets to stop people from just taking the shuttle and flying off then proceeding to do nothing the remainder of the shift also stops nuke stealing if nukies leave it on the ship needs to make sure people can't just break the front window and ignore the turret because it's behind the console, or build a thindow to be able to pilot the console from behind while not in los of the turret could relocate the navigation console deeper in maybe?

there are shutters

shutters and blast doors are useless as long as there's the possibility to build a button

i think safely stealing the nukie shuttle should require you to deconstruct at least one reinforced wall

superceded

i cri evri tiem


Fire analytics event when push notification is opened

Description
Firing an analytics event when a push notification is opened
Other changes
N/A
Tested
Manually looking at the logs
How others should test
Hard to test tbh. If you have access to the logs you can try sending you a push notification in different states (app opened, app backgrounded and app closed) and see that the push_notification_opened event shows up there in all cases.
Related issues

Fixes #413

Backwards compatibility
N/A

Hey @gnardini I have verified this issue using latest Android internal build V1.15.0 and Test Flight 1.15.0 & observed following:
Observations:

[ ]  User is able to see "push_notification_opened" message for all three events while app is in open , background as well as closed state.
Logs:
appopened
appbackground
app closed

Verified On Devices: Redmi Note 8 (9.0), iPhone 6+ (12.4.5)
Thanks..!!


Rendering of engagement list by year and month categorisation

Currently the way engagements entries are listed is very basic. It would be sensible for them to put into year and month pages. The same approach could be applied to how project list and stakeholder list renders, but by group.

Changing name of issue as data tables is the potential solution to this issue.

Done. data tables implemented


Accessibility - Unable to open selected file from the files explorer with voiceover [macOS]

VSCode Version: 1.26.1
OS Version: macOS High Siera 10.13.6

Steps to Reproduce:

Turn voiceover on by pressing command plus F5
Launch the VSCode
Press command plus shift plus E a couple of times until you hear "Files explorer table"
Now, press ctrl plus option plus down arrow to interact with the files explorer.
Try navigating with up or down arrow.
NOTE: If you disable quick navigation (press left and right arrow at the same time) and you may be able to navigate between files.

Expected result:
By interacting with the file navigator, I should be able to use arrows to navigate between files regardless of whether quick navigation is on or off. Also, I should be able to open selected file by pressing ctrl plus shift plus space.
Actual result:
When the quick navigation is on, voiceover only pronounces "Empty table". When quick navigation is off, voiceover reads the filenames but I am not able to open them.
What I tried:
I tried pressing the enter key when file is selected, but it only tries to rename the file.
Reference suggestion:
You can try using XCode navigator with voiceover as a comparison.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

Cmd + down should open the file just like the Finder on mac.
You can also customise this keybinding by changing the list.select keybinding in Preferences > Keyboard Shortcuts.
Does this solve your issue?

Oh yes, that works fine.

Great to hear.


[NEW ALGORITHM] I would like to add Finite State Automaton Algorithm under String Algorithms

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
Finite State Automaton Algorithm
About:
Propose a new algorithm to be added to the repository :  Finite State Automaton Algorithm
A Finite State Automaton (FSA) in string algorithms can be implemented in C to recognize patterns within strings efficiently. The algorithm constructs a state transition table based on the input alphabet and processes the input string character by character, transitioning through states according to defined rules. If the automaton ends in an accept state after processing the entire string, it indicates that the string matches the desired pattern
Labels:
new algorithm, gssoc-ext, hacktoberfest, level2

Assignees:

[✓ ] Contributor in GSSoC-ext
[✓ ] Want to work on it

@pankaj-bind  Hi Pankaj , it's been a while . I have been busy with some personal work . Hope you are doing well :)
Can you please assign this issue to me . I would love to work on it. Thanks

@pratheekv39 assigned


chore(main): release 1.4.0

:robot: I have created a release beep boop
1.4.0 (2023-02-27)
Features

implement fastly:secret-store package (cde22e3)

Bug Fixes

Bump to spidermonkey 110, and viceroy 0.3.5 (#420) (e17cdfd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fastly/js-compute-runtime/releases/tag/v1.4.0 :sunflower:


Hello World app not working on appengine java8

Thanks for stopping by to let us know something could be better!
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
The issue you're having must be related to a file in this repository. We are unable to provide assistance for issues unrelated to samples in this repository.
Please include as much information as possible:
In which file did you encounter the issue?

https://github.com/GoogleCloudPlatform/java-docs-samples/tree/main/appengine-java8/helloworld
No particular file seems to be a default.
Did you change the file? If so, how?
I did not
Describe the issue
When I follow the instructions to deploy to a project, it deploys successfully, the the page immediately errors out with a 500.
Here is the resultant stack trace.
Failed startup of context c.g.a.r.j.AppEngineWebAppContext@71d0dfdb{/,file:///base/data/home/apps/p~helloworld-284118/20230920t105743.455057659338210870/,UNAVAILABLE}{/base/data/home/apps/p~helloworld-284118/20230920t105743.455057659338210870}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.jetty.webapp.IterativeDescriptorProcessor.visit(IterativeDescriptorProcessor.java:86)
at org.eclipse.jetty.webapp.IterativeDescriptorProcessor.process(IterativeDescriptorProcessor.java:74)
at org.eclipse.jetty.webapp.MetaData.resolve(MetaData.java:399)
at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1412)
at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916)
at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288)
at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524)
at com.google.apphosting.runtime.jetty94.AppEngineWebAppContext.doStart(AppEngineWebAppContext.java:218)
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73)
at com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.doCreateHandler(AppVersionHandlerFactory.java:207)
at com.google.apphosting.runtime.jetty94.AppVersionHandlerFactory.createHandler(AppVersionHandlerFactory.java:125)
at com.google.apphosting.runtime.jetty94.AppVersionHandlerMap.getHandler(AppVersionHandlerMap.java:82)
at com.google.apphosting.runtime.jetty94.JettyServletEngineAdapter.serviceRequest(JettyServletEngineAdapter.java:176)
at com.google.apphosting.runtime.RequestRunner.dispatchServletRequest(RequestRunner.java:264)
at com.google.apphosting.runtime.RequestRunner.dispatchRequest(RequestRunner.java:229)
at com.google.apphosting.runtime.RequestRunner.run(RequestRunner.java:194)
at com.google.apphosting.runtime.ThreadGroupPool$PoolEntry.run(ThreadGroupPool.java:273)
at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.eclipse.jetty.apache.jsp.JettyJasperInitializer
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at org.eclipse.jetty.plus.annotation.ContainerInitializer.(ContainerInitializer.java:62)
at org.eclipse.jetty.quickstart.QuickStartDescriptorProcessor.visitContextParam(QuickStartDescriptorProcessor.java:187)
... 22 more
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!

Thanks so much for your quick response!!
We suddenly started having issues deploying all of applications to production and I had to do a sanity test with a sample app.

I suspect a regression in the Cloud SDK CLI tool which is using a newer AppEngine version.
For now, maybe you can pin in your pom.xml as previous Cloud SDK version number:
For ex:
420.0.0

If this does not work, we might have to rollback something on our side.

I did try moving to an earlier version of the CLI took, but it did not help
On Wed, Sep 20, 2023 at 2:37 PM Ludovic Champenois @.***>
wrote:

I suspect a regression in the Cloud SDK CLI tool which is using a newer
AppEngine version.
For now, maybe you can pin in your pom.xml as previous Cloud SDK version
number:
For ex:
420.0.0
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8659#issuecomment-1728248161,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGIMDY52YXURQP4G64OIVJDX3MZXHANCNFSM6AAAAAA5AG2EEU
.
You are receiving this because you modified the open/close state.Message
ID: @.***
com>

--
Joe Ciaramitaro
CTO / cofounder

Ok, we are trying a rollback, try in another few minutes (hopefully not hours, not sure)

What is you appId?

helloworld-284118 is the specific one I was testing on
On Wed, Sep 20, 2023 at 3:12 PM Ludovic Champenois @.***>
wrote:

What is you appId?
—
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/java-docs-samples/issues/8659#issuecomment-1728291024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGIMDY3GUMLRR7RFVQ7U5DTX3M5ZZANCNFSM6AAAAAA5AG2EEU
.
You are receiving this because you modified the open/close state.Message
ID: @.***
com>

--
Joe Ciaramitaro
CTO / cofounder

Well, we investigated a bit more, and for us, using the previous Cloud CLI version 446.0.0 work.
The way we did it is in the pom.xml adding  cloudSdkVersion like:
            <plugin>
                <groupId>com.google.cloud.tools</groupId>
                <artifactId>appengine-maven-plugin</artifactId>
                <version>2.4.4</version>
                <configuration>
                    <projectId>xxxx</projectId>
                    <version>yyyy</version>
                    <promote>false</promote>
                    <cloudSdkVersion>446.0.0</cloudSdkVersion>
                </configuration>
            </plugin>

Can you confirm it still does not work for you?

And it worked for us, so we know it is the newer Cloud CLI version 447.0.0 which is broken.

Maybe you did not do a clean build first.?


revamp server logs writing

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1088  👈
#1005 : 1 other dependent PR (#1045 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BelSasha and the rest of your teammates on  Graphite


Change default of DefaultResponseReferenceTypeNullHandling to NotNull

This PR:

Changes the default of DefaultResponseReferenceTypeNullHandling from Null to NotNull.
Adds support for the "nullable" xml docs attribute

Details:

Currently there is no way to specify nullability of the response with ProducesResponseTypeAttribute. This could be solved with a new "nullable" attribute in the XML docs (which always wins if specified):

/// <summary>
/// Gets an order.
/// </summary>
/// <response code="200" nullable="true">Order created.</response>
...

Most of the time (I assume?) people want a not nullable response and use 404 in the not found case and do not return null
I think Swagger UI 3 still cannot handle nullable responses (spec in the first example)
In the Swagger 2 the difference is only in the x-nullable property and thus the impact is lower.

Sample operation:
        [HttpGet("{petId}", Name = "FindPetById")]
        [Produces("application/json")]
        [ProducesResponseType(typeof(Pet), StatusCodes.Status200OK)]
        [ProducesResponseType(typeof(SerializableError), StatusCodes.Status400BadRequest)]
        [ProducesResponseType(StatusCodes.Status404NotFound)]
        public async Task<ActionResult<Pet>> FindById(int petId)

With DefaultResponseReferenceTypeNullHandling = Null (current default, OpenAPI 3)
    "/pet/{petId}": {
      "get": {
        "operationId": "Pet_FindById",
        "parameters": [
          {
          }
        ],
        "responses": {
          "200": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "nullable": true,
                  "oneOf": [
                    {
                      "$ref": "#/components/schemas/Pet"
                    }
                  ]
                }
              }
            }
          },

With DefaultResponseReferenceTypeNullHandling = NotNull (new default, OpenAPI 3)
    "/pet/{petId}": {
      "get": {
        "operationId": "Pet_FindById",
        "parameters": [
          {
          }
        ],
        "responses": {
          "200": {
            "description": "",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/Pet"
                }
              }
            }
          },

Open questions:

Should we change the default?

Pro: Most devs probably already design their APIs so that they don't return null and thus expect the default to be NotNull
Con: NotNull does not really reflect what the actual API is allowed to return (i.e. it is a missmatch between the spec and the runtime)

/cc @pranavkm @dougbu What's your take on this?

How does that impact the generated C#/TS code?

CSharp does not change because reference types cannot be made non nullable
TypeScript will change from Person | null as response to Person

You can still change this default back to how it is now

I see another problem in the future: Even with Nullable Reference Types you cannot describe nullability with the ProduceResponseTypeAttribute, because this [ProducesResponseType(typeof(Pet?), StatusCodes.Status200OK)] is not allowed (because it's just a Type object with no context and there is no place to generate the NullableAttribute).
Maybe it would be best to also add also an IsNullable attribute to the ProducesResponseTypeAttribute? /cc @rynowak @dougbu @pranavkm

@StasPerekrestov good to know... what’s your opinion on the default?

Most of the time (I assume?) people want a not nullable response and use 404 in the not found case and do not return null

I don't know the whole history here but agree with this sentiment. Provide a well-documented override of this default and all would be well from my perspective.

you cannot describe nullability with the ProduceResponseTypeAttribute

Your point is valid but leave nullable reference types out of it: Knowing the compiler will allow a null assignment is very different from knowing the user will assign null in some cases.
Agree a ReturnsNull property or similar may be needed if we find users return null in a few but not all actions.

Your point is valid but leave nullable reference types out of it: Knowing the compiler will allow a null assignment is very different from knowing the user will assign null in some cases.

The problem here is the inconsistency from a user perspective: As a user in an NRT world, I'd expect that typeof(Pet) is automatically treated as not nullable and typeof(Pet?) is nullable (but this probably does not compile, right?), but from a tooling perspective we cannot assume not nullable because typeof(Pet?) is not allowed. As a user I'd like to express nullability in the same way as I do it everywhere else (e.g. parameters) - not  with an additional property on the attribute...

I guess, you are looking for something like Optional/Maybe to avoid
using attributes, however usage of these patterns isn't common in c#
world...
On Mon, Jun 10, 2019, 12:07 PM Rico Suter<EMAIL_ADDRESS>wrote:

Your point is valid but leave nullable reference types out of it: Knowing
the compiler will allow a null assignment is very different from knowing
the user will assign null in some cases.
The problem here is the inconsistency from a user perspective: As a user
in an NRT world, I'd expect that typeof(Pet) is automatically treated as
not nullable and typeof(Pet?) is nullable (but this probably does not
compile, right?), but from a tooling perspective we cannot assume not
nullable because typeof(Pet?) is not allowed. As a user I'd like to
express nullability in the same way as I do it everywhere else (e.g.
parameters) - not with an additional property on the attribute...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/pull/2215?email_source=notifications&email_token=AAGMTTKPGBYC32FLGPAYFQTPZYKVZA5CNFSM4HVSWCIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJK7EI#issuecomment-500346769,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGMTTKXBBQ7XY4PWRBZ6TDPZYKVZANCNFSM4HVSWCIA
.

I guess, you are looking for something like Optional/Maybe to avoid
using attributes, however usage of these patterns isn't common in c#
world...

Or Nullable<T> but that's only for value types - however as a user I just expect that Pet vs Pet? just works everywhere and thus I'm a bit worried that people will be quite confused.

On one hand we have the issue described in the task,
On the other hand there is an issue related to reference types handling,
so, basically, we have two related issues.
In c# world we don't have to many options to go with. We need either to
wrap instances, e.g. Maybe monad, but c# doesn't have appropriate sugar
syntax to deal with it, or use Attributes to express the disired behavior.
On Mon, Jun 10, 2019, 12:25 PM Rico Suter<EMAIL_ADDRESS>wrote:

I guess, you are looking for something like Optional/Maybe to avoid
using attributes, however usage of these patterns isn't common in c#
world...
Or Nullable but that's only for value types - however as a user I just
expect that Pet vs Pet? just works everywhere and thus I'm a bit worried
that people will be quite confused.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RicoSuter/NSwag/pull/2215?email_source=notifications&email_token=AAGMTTM3JN2KAP3YQ76GFPTPZYMXLA5CNFSM4HVSWCIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXJMETY#issuecomment-500351567,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGMTTLLPY37HHTSPTFPM6TPZYMXLANCNFSM4HVSWCIA
.

In c# world we don't have to many options to go with. We need either to
wrap instances, e.g. Maybe monad, but c# doesn't have appropriate sugar
syntax to deal with it, or use Attributes to express the disired behavior.

My point is that this should have been solved with the C# 8 NRT feature somehow, but typeof() cannot "store" this nullability info...
However this PR is not really about NRT or C# 8 but about changing the default of DefaultResponseReferenceTypeNullHandling to NotNull and adding the "nullable" attribute to the xml docs (this will solve the problems for now). My big question is: What is the best default for DefaultResponseReferenceTypeNullHandling?

What concerns me, is that XML docs now change the behavior of XML schema generation. This is something, not many developers are aware of and also may be a source of confusion.
From my point of view, I'd rather look for an appropriate .net attribute to change the required behavior than for an attribute of XML doc.

Regarding the new defaults, I'm OK with that. However, the information that describes the behavior and the way of changing it should be more easy to find.

What concerns me, is that XML docs now change the behavior of XML schema generation. This is something, not many developers are aware of and also may be a source of confusion.

Yes, somehow you are right, but the alternative is even more verbose:
/// <summary>
/// Gets an order.
/// </summary>
/// <response code="200">The order.</response>
[HttpGet("{orderId}", Name = "GetOrder")]
[ProducesResponseType(typeof(Pet), StatusCodes.Status200OK)]
[ProducesResponseTypeNullable(true, StatusCodes.Status200OK)]
public async Task<ActionResult<Order>> GetOrder(int orderId)

I think it's the still the nicest way to do as xml docs attribute as it is the only way to avoid having specifying a single response code three times...
Ideally there's just a IsNullable (or similar) property on the ProducesResponseTypeAttribute but for backward compat. we'd still keep the "nullable" xml docs attribute.

Docs: https://github.com/RicoSuter/NSwag/wiki/AspNetCoreOpenApiDocumentGenerator#response-nullability


How do I set the download location/path in the Python Module?

I haven't found any solutions for this in Python, only for CLI. The code that I currently have is
instance = instaloader.Instaloader()
user = input ('What is the username: ')
userpic = instance.download_profile(user, profile_pic_only=True)

асс = input('Enter the Account Username: ')
test.download_profile(acc, profile_pic_only = True)


Warning: Expected server HTML to contain a matching  in .

What version of Remix are you using?
1.3.4
Steps to Reproduce
Run npx create-remix@latest and inspect the Developper Tools
Expected Behavior
Not having this error out of the box
Actual Behavior
I wanted to start my project using the basic setup for Remix but no matter what I instantly get this error message, even if I pick "Remix App Server". What am I missing?

Hi @miguderp, can you try in Incognito Mode? Some browser extension is maybe injecting something in <head>

We can't expect our users to use Incognito Mode or uninstall their extensions! How do we go about fixing this?


Update dataflows-configure-consume.md

Recommend revising availability statement to reflect similar documentation located at  Introduction to dataflows and self-service data prep.  This broad statement does not apply to all customers within DoD but may to GCC, GCC-High or other sovereign clouds.

@davidiseminger
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Looks like a good clarification - thanks @marcadamcarter
#sign-off


Calling createLocation statically is deprecated warning on server

I get this warning on my server now:
Warning: [history] Calling createLocation statically is deprecated; instead call the history.createLocation method - see docs/Location.md

This is how I use createLocation now:
import React from 'react';
import ReactDOMServer from 'react-dom/server';
import createLocation from 'history/lib/createLocation';
[...]

module.exports = {
    viewApp: function (req, res) {
        var location = createLocation(req.url);
        [...]

If I try to do what https://github.com/rackt/history/blob/master/docs/Location.md says:
import React from 'react';
import ReactDOMServer from 'react-dom/server';
import { createHistory } from 'history';
[...]

module.exports = {
    viewApp: function (req, res) {
        var history = createHistory();
        var location = history.createLocation(req.url);
        [...]

I get this error:
 Error: Invariant Violation: Browser history needs a DOM
    at Object.invariant [as default] (/home/stein/repositories/livvin/node_modules/history/node_modules/invariant/invariant.js:44:15)
    at Object.createBrowserHistory [as createHistory] (/home/stein/repositories/livvin/node_modules/history/lib/createBrowserHistory.js:35:25)

What am I missing? Should this not work when run outside of a browser?

Are you using this with React-Router's match? As of the the current release, you don't actually need to pass in a Location object: https://github.com/rackt/react-router/blob/v1.0.0-rc3/docs/guides/advanced/ServerRendering.md; you just need the URL.

Ah, that was it. Thanks, @taion


How to pass environment variables to build ?

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.2.0
Electron version
v28.2.3
Operating system
macOS 14.2.1
Last known working Electron Forge version
No response
Expected behavior
I have an issue on using the make command and passing env variables.
As on a lot of projects, I'm setting all my env variables in a .env file at the root of the project.
When running the project using npm run start, no issue, everything works well (_VITE and also dotenv related variables are load)
But when trying to build the DMG using npm run make the variables are not loaded.
Actual behavior
The variables are not loaded in main / loader / renderer. (undefined)
Steps to reproduce
Run npm run make using a .env file and some variables in the the main or renderer.
Additional information
No response

+1

@alxpereira hi bro, do you have any solution to fix this problem?

@alxpereira hi bro, do you have any solution to fix this problem?

for the moment, nope.. I will in the end maybe pass the env file directly in the build process forcing dot-env to parse it. But that won't be the final clean solution.

@alxpereira Hi, my application bulit it with electron-forge & vite-typescript & vue, so I found this https://github.com/electron/forge/issues/3375 can sovle my problem, and BTW I pass NODE_ENV from npm command as environment variable. hope it can help you or give you some inspires. thanks your replay.

Thanks for reaching out and logging this issue! Because we treat our issues list as the team's backlog, we close issues that are questions since they don't represent a task needing to be completed. For most questions about Electron there are a lot of options.
Check out the Electron community. There are also a bunch of helpful people in this Discord that should be willing to point you in the right direction. For your question, I'd recommend the Discord - we have many active help channels and mentors, as well as fellow devs, who can help you out.

I ran across this issue as well and after some research came up with this approach using env-cmd (this would work with dotenv as well):
File: .env
SERVER_PORT=
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=

File: package.json
"scripts":{
    "start": "env-cmd -f .env.dev electron-forge start",
    "package": "env-cmd electron-forge package",
}

File: webpack.main.config.js

const webpack = require("webpack"); //to access built-in plugins

module.exports = {

 . . .

   plugins: [
    new webpack.EnvironmentPlugin({
      SERVER_PORT: process.env.SERVER_PORT,
      AWS_ACCESS_KEY_ID: process.env.AWS_ACCESS_KEY_ID,
      AWS_SECRET_ACCESS_KEY: process.env.AWS_SECRET_ACCESS_KEY,
    }),
  ]
  . . .
};

I ran across this issue as well and after some research came up with this approach using env-cmd (this would work with dotenv as well):
File: .env
SERVER_PORT=
AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=

File: package.json
"scripts":{
    "start": "env-cmd -f .env.dev electron-forge start",
    "package": "env-cmd electron-forge package",
}

File: webpack.main.config.js
const webpack = require("webpack"); //to access built-in plugins

module.exports = {

 . . .

   plugins: [
    new webpack.EnvironmentPlugin({
      SERVER_PORT: process.env.SERVER_PORT,
      AWS_ACCESS_KEY_ID: process.env.AWS_ACCESS_KEY_ID,
      AWS_SECRET_ACCESS_KEY: process.env.AWS_SECRET_ACCESS_KEY,
    }),
  ]
  . . .
};

Worked perfectly. I used dotenvx.

I use webpack to build the app and to pass the environment variable, there are two tools:

cross-env-shell
webpack's DefinePlugin

If you're not using Webpack, for example,
"make": "cross-env-shell NODE_ENV=prod \"pnpm run build-prod && electron-forge make\"",

Since I use webpack, in webpack.plugins.ts,
import type IForkTsCheckerWebpackPlugin from 'fork-ts-checker-webpack-plugin';
const webpack = require('webpack'); // <------ add this line
// eslint-disable-next-line @typescript-eslint/no-var-requires
const ForkTsCheckerWebpackPlugin: typeof IForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');

export const plugins = [
  new ForkTsCheckerWebpackPlugin({
    logger: 'webpack-infrastructure',
  }),
  // use the plugin to pass environment variable
  new webpack.DefinePlugin({
    'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV),
  }),
];

Please refer to the Webpack template for details.


Updated with update-to-date images for iOS 8 and later.

Updated Core with update-to-date images for iOS 8 and later. Added @3x images. Updated DTLoupeView.m to accommodate the updated images. Updated Demo to use a Launch Screen storyboard.
Note - The Demo xib files need some work on their layout. The layout is messed up on most devices.

Ok, since I'm updating, I'll merge this in as well.


Is EasyIB still working?

I am using a PAPER account for the test.
Some of requests work, but some of them do not work.
Do you have any idea how to fix them?
① Get live orders

Response:
{'error': 'Please query /accounts first'}

② Get auth status, Get ping server
→ This one works, but why I am not still authenticated?

 Are you sure you logged in at https://localhost:5000 in a web browser?

@ashpipe
Yeah, I logged in by typing my paper account username and password, and I saw
"Client login succeeds".
However, the login page did not ask me to enter security code by using my phone.
Is that the reason why I do not get authenticated?   Have you ever tried a paper account with EasyIB?

@ashpipe
And.. the demo site does not work as well.
I don't know how to authenticate myself.


Exception when trying to create LlamaCpp wrapper for deepseek coder 1.3b

The bug
I get an exception:
terminate called after throwing an instance of 'std::out_of_range'
  what():  _Map_base::at

when trying to create a LlamaCpp wrapper for deepseek coder 1.3b
I tried to debug and it seems that this line fails when i == 32015.
Can't tell whether it is a guidance or llama.cpp issue.
To Reproduce
lm = models.LlamaCpp(model="/home/ggufs/deepseek-coder-1.3b-instruct.Q5_K_M.gguf") # you can download the exact model from the link above

System info:
OS: Windows 11, under wsl
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3296

 $ uname -a
Linux columpio <IP_ADDRESS>-microsoft-standard-WSL2 #1 SMP Thu Jan 11 04:09:03 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

>>> print(guidance.__version__)
0.1.13

It now works just fine with

guidance==0.1.14
llama_cpp_python==0.2.74
https://huggingface.co/RichardErkhov/deepseek-ai_-_deepseek-coder-1.3b-instruct-gguf/resolve/main/deepseek-coder-1.3b-instruct.Q5_K_M.gguf

So I close the issue.


Issue-434: Added custom CSS rule for external links

Pull Request Template
Description
Added the former rule for .externalLink class from custom.css (legacy) to Just the Docs's custom.scss file.
Fixes #434
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Ran the local preview before and after fix.
Additional Context (Please include any Screenshots/gifs if relevant)
...
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[x] I have checked my code and corrected any misspellings
[x] I have tagged the reviewers in a comment below incase my pull request is ready for a review
[x] I have signed the commit message to agree to Developer Certificate of Origin (DCO) (to certify that you wrote or otherwise have the right to submit your contribution to the project.) by adding "--signoff" to my git commit command.

Before:

After:


Prisma init generates incorrect docker-compose file for mongodb

Describe the bug
prisma init workflow with existing mongo yields an incorrect docker file with a field called schema but it should be named database.
To Reproduce

Try prisma init on existing mongodb with any database and observe the generated docker file.
Try to use docker-compose -up -d and the server will go into a restart loop with: "Exception in thread "main" java.lang.RuntimeException: Unable to load Pri│ sma config: com.prisma.config.InvalidConfiguration: Expected host to be n│ on-empty"

Expected behavior
Prisma init workflow should generate a correct docker-compose.yml file.
Versions (please complete the following information):

Connector: MongoDB
Prisma Server: 1.30
prisma CLI: 1.30

Additional context:
Omitting the database field also works if the database name is present in connection string, which relates this issue to https://github.com/prisma/prisma/issues/4360

Related to https://github.com/prisma/prisma/issues/4434

For me all the ideas to fix it did not help out:

remove schema
rename schema to database

Maybe you have tips to me:

prisma 1.34
Windows latest docker desktop

yml:
version: '3'
services:
  prisma:
    image: prismagraphql/prisma:1.34
    restart: always
    ports:
    - "4466:4466"
    environment:
      PRISMA_CONFIG: |
        port: 4466
        # uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
        # managementApiSecret: my-secret
        databases:
          default:
            connector: mongo
            uri: 'mongodb://localhost:27017/admin'

Prisma deploy:
prisma deploy
 !    Could not connect to server at http://localhost:4466. Please check if your server is running.

docker compose logs:

prisma_1  | Exception in thread "main" java.lang.RuntimeException: Unable to load Prisma config: com.prisma.config.InvalidConfiguration: Expected host to be non-empty
prisma_1  |     at scala.sys.package$.error(package.scala:26)
prisma_1  |     at com.prisma.config.ConfigLoader$.load(ConfigLoader.scala:40)
prisma_1  |     at com.prisma.local.PrismaLocalDependencies.(PrismaLocalDependencies.scala:48)
prisma_1  |     at com.prisma.local.PrismaLocalMain$.delayedEndpoint$com$prisma$local$PrismaLocalMain$1(PrismaLocalMain.scala:13)
prisma_1  |     at com.prisma.local.PrismaLocalMain$delayedInit$body.apply(PrismaLocalMain.scala:8)
prisma_1  |     at scala.Function0.apply$mcV$sp(Function0.scala:34)
prisma_1  |     at scala.Function0.apply$mcV$sp$(Function0.scala:34)
prisma_1  |     at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:12)
prisma_1  |     at scala.App.$anonfun$main$1$adapted(App.scala:76)
prisma_1  |     at scala.collection.immutable.List.foreach(List.scala:388)
prisma_1  |     at scala.App.main(App.scala:76)
prisma_1  |     at scala.App.main$(App.scala:74)
prisma_1  |     at com.prisma.local.PrismaLocalMain$.main(PrismaLocalMain.scala:8)
prisma_1  |     at com.prisma.local.PrismaLocalMain.main(PrismaLocalMain.scala)


YAML Pipeline Documentation

With the recommended approach for Azure DevOps Pipelines now to use YAML over the UI\Display what would be the approach to building a YAML based pipeline for Azure Service Fabric?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 95e331af-2350-c9cc-1205-f17ae4d17eb0
Version Independent ID: a69e5b1f-1195-b191-58a4-0caf73cceccc
Content: Deploy a Service Fabric app with continuous integration (Azure DevOps Services) in Azure
Content Source: articles/service-fabric/service-fabric-tutorial-deploy-app-with-cicd-vsts.md
Service: service-fabric
GitHub Login: @rwike77
Microsoft Alias: ryanwi

Thanks for the question! We are investigating and will update you shortly.

@rwike77 could you comment further on this?
CC @aljo-microsoft

@jockerman-ipspark I will assign this to the author to review and comment further and update the doc if needed.

@MicahMcKittrick-MSFT Thank you!

@jockerman-ipspark
If you need help building YAML for Azure DevOps for an SF Application, then use the portal workflow to provision an Azure DevOps project for Service Fabric Application; then within the edit pipeline UI click 'View YAML' to get YAML used to build that pipeline. You can version this YAML, and make edits for your use case.
@MicahMcKittrick-MSFT
If the user is satisfied, please close this.


Split SearchMessagesScreen in several components

Automated message from Dropbox CLA bot
@borisyankov, it looks like you've already signed the Dropbox CLA. Thanks!


Add chyt_nb connection

We have some problems with CI now. Failed task E2E Tests / Publish E2E Report (pull_request) is okay


Handler of Branch.getInstance().initSession isn't being called

Is there any case that when hit a short link ex: app.md.com/GHHDI76878H, app calls (2) only instead of (1)
Our app: start app -> hit initSession handler (1), send to background -> hit short link -> it called (2) only
Our sample app: start app -> hit initSession handler (1), send to background -> hit short link -> it called (1) only as expectation
The difference is 1 app integrated a lot of third parties: Facebook, Google, Firebase, Twitter, etc...
The other didn't
(1)Branch.getInstance().initSession(launchOptions: launchOptions) { (params, error) in             // do stuff with deep link data (nav to page, display content, etc)             print(params as? [String: AnyObject] ?? {})         }
(2) func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([Any]?) -> Void) -> Bool {     Branch.getInstance().continue(userActivity) }

It happens with version: 0.25.6
And works well with version: 0.25.5

Thanks for the heads up.  I'm looking into this now.

Are you using the Segment-Branch integration.

Are your apps, your app and your sample app using the identical Branch keys and Branch set up?

At the beginning, our app is integrated Branch via Fabric.
Our sample is integrated follow this guide (manual install): https://docs.branch.io/pages/apps/ios/
Then i removed Fabric and it's related things, then tried re-integrate with manual install follow that guide, but no luck. But older version works well.
Our app and sample app are using the same bundle id and Branch key.

Our sample app is attached in issue https://github.com/BranchMetrics/ios-branch-deep-linking/issues/865

The short link https://app.md.com/GHHDI76878H isn't a Branch link, so the call back handler won't indicate that it is a Branch link.
A link like https://megadeeds.app.link/LZPi5iO3KQ is a Branch link, and the callback handler will indicate that it's a Branch link and the associated data will be returned.

I hope this clarified things for you! Happy deep linking.

@E-B-Smith  Sorry for making confuse, I just gave an example. But the link is definitely a Branch link, like : https://megadeeds.app.link/LZPi5iO3KQ. Do you have any ideas ?

When you click on the link, does it open the app?
If you're running it on a device, is it code signed correctly?

Have you added both these functions to your app delegate?
func application(_ application: UIApplication, open url: URL, sourceApplication: String?, annotation: Any) -> Bool {

    // Pass the url to the handle deep link call
    let branchHandled = Branch.getInstance().application(application,
        open: url,
        sourceApplication: sourceApplication,
        annotation: annotation
    )
    if (!branchHandled) {
        // If not handled by Branch, do other deep link routing for the
        // Facebook SDK, Pinterest SDK, etc
    }

    return true
}

func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
    let handledByBranch = Branch.getInstance().continue(userActivity)

    return handledByBranch
}

@E-B-Smith,
When you click on the link, does it open the app? -> Yes
If you're running it on a device, is it code signed correctly? -> Yes
Are you using your live key? -> Yes
Have you added both these functions to your app delegate? -> Yes

Are you testing with a link that is not desktop only or one time use?

Yes it's weirds that the demo app is working fine.
And the fact that if i replace with older Branch SDK, our app works normally.
I think i will simplify our app (remove all businesses) and send you for checking.

Are you calling Branch.setIdentity before initializing Branch?
Sometimes that causes problems.
Move it to right after initializing Branch if so.

Are you calling Branch.setIdentity before initializing Branch? -> NO
Below is the link of project which able to demonstrate the bug. Please take a look @E-B-Smith .
Thanks.
https://drive.google.com/open?id=14Vb5BgjnyGgciqhRndsl9xcsP6bBUrrS

Are you using Swift 3 or Swift 4?

Thanks for your example - I was able to find a solution for you.
Put the call to Branch.getInstance().continue(userActivity) first in your continueUserActivity: method, like this:
    //** universal links
   // Make sure this method isn't marked `private`!
    func application(_ application: UIApplication, continue userActivity: NSUserActivity, restorationHandler: @escaping ([UIUserActivityRestoring]?) -> Void) -> Bool {
        Branch.getInstance().continue(userActivity) // <= Put this line first!
        BranchManager.userCompletedAction("ActionLog.startappUL") // Then this line.
        // pass the url to the handle deep link call
        return true
    }

This should solve your problem now, and I'll patch the SDK to prevent problems like this in the future.

@E-B-Smith Swift 4

Thanks @E-B-Smith E
it works like a charm, simple but takes time to configure it out

Cheers :)


Rework USART API to reduce macro usage

It is showing more and more that generating the entire API for the HAL crates from macros is a bad idea.  Reasons include:

It obscures the code.  People have trouble finding where a certain type is defined, especially if they are not too well aquainted with rust macro_rules!().
It breaks auto-completion in IDEs because they'd need to introspect the macros.
It leaves many types with the same methods instead of a single one.  This also makes code that is generic over the exact peripheral impossible to write.
It makes it much harder to cleanly support different peripherals under a common interface.

To mitigate these problems, shift to a different design:  A single Usart type provides the public API and is generic over the USART peripherals which all implement a common interface called UsartOps.  Only this trait implementation will be macro generated and thus there is no user-facing macro-generated API left.
This design also makes it much easier to implement support for multiple different hardware peripherals: As long as the UsartOps are expressive enough to fit all of them, we can simply provide multiple macros for generating the implementation for each one.
As the diff in this PR is quite unreadable, please look at the new API here: https://github.com/Rahix/avr-hal/blob/refactor-usart/avr-hal-generic/src/usart.rs
Remaining work:

[x] Add back reader and writer halves (.split() API).
[x] Add back interrupts API.
[x] Add API documentation.
[ ] Investigate how we can "hide" UsartOps from downstream code or make it unsafe to access.
[ ] Verify expressiveness by implementing UsartOps for ATmega4809 (#97, #101).

Investigate how we can "hide" UsartOps from downstream code or make it unsafe to access.

This part is still a big question mark for me.    My original idea was to just make the functions in UsartOps unsafe to call but this has the nasty side-effect that it means all the implementations of the functions are large unchecked unsafe blocks.  As the code they contain is usually mostly safe rust, this would be very unfortunate.
Ideally, we can find a way to make those functions "private" in some sense, but I am not quite sure how.  The trait must be public because downstream code might want to be generic over it:
fn takes_any_usart<USART: UsartOps<RX, TX>, RX, TX, CLOCK>(any_usart: Usart<USART, RX, TX, CLOCK>) {
    // ...
}

@Rahix  Could a possible solution be to create a type within the macro that implements UsartOps. Something like I've hashed together here: https://github.com/chris-ricketts/avr-hal/blob/adff98e9d38d2224d3a0e4e6915bc0be4c397734/avr-hal-generic/src/usart.rs#L423
This would expand to:
    // Excuse the underscore - I didn't realise the macro created a `Uart1<..>` type alias
    pub struct _Usart1 {
        peripheral: crate::pac::USART1,
    }
    impl core::ops::Deref for _Usart1 {
        type Target = crate::pac::USART1;
        fn deref(&self) -> &Self::Target {
            &self.peripheral
        }
    }
    impl core::ops::DerefMut for _Usart1 {
        fn deref_mut(&mut self) -> &mut Self::Target {
            &mut self.peripheral
        }
    }
    pub fn usart1<CLOCK>(
        peripheral: crate::pac::USART1,
        rx: portd::PD2<
            ::avr_hal_generic::port::mode::Input<::avr_hal_generic::port::mode::Floating>,
        >,
        tx: portd::PD3<::avr_hal_generic::port::mode::Output>,
        baudrate: ::avr_hal_generic::usart::Baudrate<CLOCK>,
    ) -> ::avr_hal_generic::usart::Usart<
        _Usart1,
        portd::PD2<::avr_hal_generic::port::mode::Input<::avr_hal_generic::port::mode::Floating>>,
        portd::PD3<::avr_hal_generic::port::mode::Output>,
        ::avr_hal_generic::usart::Baudrate<CLOCK>,
    > {
        let usart = _Usart1 { peripheral };
        Usart::new(usart, rx, tx, baudrate)
    }

This would meant that a downstream user doesn't have ready access to a type that implements UsartOps - they'd have to explicitly create _Uart1.
It would mean creating the uart like:
let serial = hal::usart::usart1(
       dp.USART1,
       pins.d0,
       pins.d1.into_output(&mut pins.ddr),
       57600.into_baudrate(),
   );
   // instead of
   let serial = hal::usart::Usart1::new(
       dp.USART1,
       pins.d0,
       pins.d1.into_output(&mut pins.ddr),
       57600.into_baudrate(),
   );

Maybe we can define FSM? https://docs.rs/rust-fsm/0.4.0/rust_fsm/
Not sure if this is good way in Rust... and embedded code.

@Rahix it's possible to help you to push forward this?

@Rahix it's possible to help you to push forward this?

Hey @explicite,
sorry for the inactivity here ... I hope I can allocate some time next weekend to get this resolved.  I did some work in other HAL layers (for other MCUs) in the meantime and I think I now got some new ideas which could be applied here as well.

Hey @explicite,
sorry for the inactivity here ... I hope I can allocate some time next weekend to get this resolved.  I did some work in other HAL layers (for other MCUs) in the meantime and I think I now got some new ideas which could be applied here as well.

Okay, I've decided to just use a simple solution for now: The methods are now named raw_... to reflect that they are low-level API.  In the future we can think about a more elegant design...
I'll merge this state and we'll do any future changes ontop of it later.

https://rust-embedded.github.io/book/static-guarantees/index.html pinned here for further reading


electrum: 3.0.5 -> 3.0.6

This change bumps the version of Electrum to 3.0.6.
Notice that due to #33146 this still doesn't work out-of-the-box, but that's true for the previous version of Electrum and other Qt applications as well.

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Thanks! :)


SINGA-125 Improve Python Helper

Update model.py to get TANH for gpu when activation='tanh'. (It was STANH)

This was solved in SINGA-126.


matplotlib: analysis failed when use some package

I met some problems when use pylance analysis.

Recognition failed in this fig.

Couldn't search this method in variable 'patch'
However, it has no effect on running code. That is, running normally but analysis wrong.
I just use this for a short time, so I'm not sure about whether it's a common problem.

This issue has been fixed in version 2021.3.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202130-3-march-2021


[WIP] Adding basic Multitask Models

This PR ports over multitask models for pytorch over from DeepChem contrib and adds some basic tests.

One cool thing about PyTorch is gradient accumulation - so you can feed the model with smaller batch sizes, but accumulate the gradients for a few steps, allowing an effectively higher batch size

@VIGS25 Thanks for the pointer! Do you have an example of how to do gradient accumulation correctly?

def _train_step(self, inputs: Tuple[Tuple[torch.Tensor, ...], ...],
                    step_count: int, **kwargs) -> Dict[str, float]:
        """Runs a train step.

        Parameters
        ----------
        inputs: tuple of tuples of torch.Tensors
            Inputs to the WLNDisconnect forward pass
        optimizer: torch.optim.Optimizer:
            optimizer used for gradient computation
        """
        total_loss, metrics = self.model.train_step(*inputs)
        assert torch.isfinite(total_loss).all()

        accum_every = kwargs.get('accum_every', None)
        if accum_every is not None:
            apply_grad = (step_count % accum_every) == 0
            total_loss /= accum_every
            total_loss.backward()

            if apply_grad:
                if "clip_norm" in kwargs:
                    nn.utils.clip_grad_norm_(self.model.parameters(), kwargs["clip_norm"])

                self.optimizer.step()
                self.optimizer.zero_grad()

                if step_count % self.print_every == 0:
                    if torch.cuda.is_available():
                        alloc_memory = torch.cuda.memory_allocated() / 1024.0 / 1024.0
                        cached_memory = torch.cuda.memory_cached() / 1024.0 / 1024.0
                        print(f"Memory: Allocated: {alloc_memory:.3f} MB, Cache: {cached_memory:.3f} MB")
                        sys.stdout.flush()

                if torch.cuda.is_available():
                    torch.cuda.empty_cache()

This is how I do it for my thesis right now. You only call optimizer.step() after the required number of steps have passed. But you keep using loss.backward(), because that keeps adding the gradients.

If you want to create new tensors which are not parameters in the model, then PyTorch has functions for that - https://pytorch.org/docs/stable/tensors.html#torch.Tensor
This allows you to retain the device of existing tensors that you create the new tensor(s) from

I'm going to merge in this open PR so we get things more setup in the main repo. Can continue the work started here in subsequent PRs


Claim private command not working as expected

Old scenario
/claimprivate on = false
/claimprivate off = true
/claimprivate  = always true
New scenario
/claimprivate on = true
/claimprivate off = false
/claimprivate  = toggle

I don't think this logic is right, is it? If the user enters /claimprivate true, it should make the claim private and trigger the event as is the current behaviour. Also inverting the Boolean there will double invert the toggle check. Is the current logic really not correct?

The logic wasn't right. If you did /claimprivate on
It disabled the private claim.

Could you maybe take a look at it again? 👍


Allow to move elements of array in the value viewer

Currently we don't support changing the order of elements of arrays.

verified


Use xla.abstractify in xla_computation.

The previous version was dropping weak-types for scalars.

This one is broken.


How to select only single line in vertically

please help me to get only vertical item selection like this using drag only

yes i m trying for the same but can u please let me know why it's not working in nested scrollview


[CI Fix] Disable Some Clojure Integration tests that are having connection problems

The dependencies in some of the examples are having trouble connecting to the repo
Could not transfer artifact origami:origami:pom:4.0.0-3 from/to vendredi (https://repository.hellonico.info/repository/hellonico/): Failed to transfer file: https://repository.hellonico.info/repository/hellonico/origami/origami/4.0.0-3/origami-4.0.0-3.pom. Return code is: 502 , ReasonPhrase:Bad Gateway
Example:
http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/PR-14377/1/pipeline
This will temporarily disable them until we can troubleshoot what is going on

@lanking520 there also seems to be problems with the static Scala build? http://jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/mxnet-validation%2Funix-cpu/detail/disable-clojure-origami-tests/2/pipeline/254

I just tested and the origami repo seems to be back up so this PR may not be needed after all.
@hellonico what do you think? We could merge this and investigate ways to mitigate an outage to the repo or close it for now?

@gigasquid  We have them tracked there https://github.com/apache/incubator-mxnet/issues/14174. It's weird, but not sure what are the next step

I'm going to go ahead a close this PR since the problem with the repo is resolved. I'll open an issue to discuss a long term fix.


CORS error on page load after deploying to Walrus Testnet

What happened?
Deployed Sui dApp Starter demo to Walrus:
Site object ID: 0xdaf4d7b1631ff366c04d500446342bbcc14023c655cbc6be841c0425d6e7f59e
Browse the resulting site at: https://5gglkxavijbcc4hgtmv772efvqx9vn2urydcny8ob60h38ck9q.walrus.site

Received a blank page.
The script which I deployed with is here https://github.com/suiware/sui-dapp-starter/blob/main/packages/frontend/scripts/walrus-site-deploy.cjs
Search terms
for gut sake!
Steps to reproduce

Scaffold a new project with pnpm create<EMAIL_ADDRESS>or alternatively clone its repo https://github.com/suiware/sui-dapp-starter
cd [your project folder]
pnpm i
pnpm testnet:start
pnpm frontend:deploy:walrus

Deviation steps
Used Suibase.io for network management
Relevant log output
Access to fetch at 'https://aggregator.walrus-testnet.walrus.space/v1/w0BmI4r3iSXOCj2BvhonanH2cudHE81JHeGWnzvwxdM' from origin 'https://5gglkxavijbcc4hgtmv772efvqx9vn2urydcny8ob60h38ck9q.walrus.site' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

Version

[X] walrus and site-builder are up to date.

If applicable, what browsers are you seeing the problem on?
Chrome
Code of Conduct

[X] I agree to follow this project's Code of Conduct.

hi @kkomelin , thanks for the report. Just to understand, how do you go from the steps above to deploying onto walrus? I'm not familiar with pnpm create<EMAIL_ADDRESS>

Hi @giac-mysten ,
Thanks for reaching back.
I've updated the description to clarify things a bit better.
I'm using my suiware/sui-dapp-starter and the [script which I deploy with](The script which I deployed with is here https://github.com/suiware/sui-dapp-starter/blob/main/packages/frontend/scripts/walrus-site-deploy.cjs).

hey @kkomelin , sorry i did not reach back to you sooner.
Is the issue still present? I think we may have already solved the root issues on our side.

Hey @giac-mysten ,
Last week I successfully redeployed to Walrus without any problems, so we can consider this issue addressed.
Thanks for your assistance!


Upload uncompressed .mltbx as release asset

The currently posted mltbx is compressed with a .mltbx.zip extension. Should change to uncompressed file with .mltbx format.

Resolved in Version 1.7.0


implement missing expressions

Is your feature request related to a problem or challenge? Please describe what you are trying to do.

[x] conv
[x] row_number
[x] lower
[x] lpad
[x] concat_ws
[x] hex
[x] md5
[x] parse_url
[x] first_value
[x] regexp
[x] ceil
[x] rlike
[x] to_date
[x] concat
[x] pow
[x] lag
[x] find_in_set
[x] floor
[x] rand
[x] hash
[x] bin
[x] Remainder
[x] get_json_object

Describe the solution you'd like
implement these expressions in arrow/gandiva and gazelle
Describe alternatives you've considered
N/A
Additional context
N/A

Fixed.


Release 4.5

Release 4.5 for ARO

move to go mod
Architecture differences
Single NSG for all components.
Single Public loadbalancer for all components
cgmanifest refactored to use gomod

Installer updated fork: https://github.com/jim-minter/installer/commits/release-4.5-azure
TODO:
[] Installer do no fail in node provisioning fails

@jim-minter  this is still needs polishing, but it is getting closer. I think first round of reviews can be done.  Your old branch is at https://github.com/jim-minter/ARO-RP/tree/mjudeikis/release-4.5-old in case you want to diff.
Some outstanding tasks that need to be done before merge:

refactor installer/release-4.5-azure to sanitise commits [MJ]
review usage of context.TODO(), context.Background() [either]
review go.mod settings for sanity - validate we're bringing in the right releases of things [JM]

@hawkowl please also review this PR.

/az run e2e

/azp run ci

/azp run e2e

successful e2e. running again.

/azp run e2e

successful e2e. running again.

/azp run e2e


wine: gecko 2.47.1 -> 2.47.2 and add tests

Motivation for this change
Wine complains about not having gecko & tries to fetch it over the internet because nixpkgs is providing the wrong version of gecko.  Fix this, and add a test so it's easy to notice in the future if the required & provided gecko versions come apart again.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[x] Fits CONTRIBUTING.md.

FYI: @SFrijters

Oh, good catch. Looks like this is needed for all 6.0+ versions, so this has been broken for a while.
I have never added anything to nix tests yet, so I don't know what is good/bad there. hello.exe is some test executable that requires gecko to work?
@avnik

hello.exe is GNU Hello.  It prints "Hello, world!".  It doesn't require gecko, but wine notices that gecko is missing while it is initialising ~/.wine/ and mentions this.  A smarter, better wine might wait until gecko is actually needed before attempting to load it, which would allow this test to pass incorrectly.  So it's not a great test, but it's much better than nothing.

I have one  game, which using mshtml (and indirectly gecko via it), and it works with latest 6.9.
(old wineprefix)


convert_keras fails with quantize_model

Following example fails with error AssertionError: dense_input:01 is disconnected, check the parsing log for more details..
        model = quantize_model(
            keras.Sequential([
                layers.Dense(3, activation='relu', input_shape=(5,)),
                layers.Dense(3, activation='relu', input_shape=(3,)),
            ]))
        model.compile(optimizer="Adam", loss="mse", metrics=["mae"])
        print(model.summary())
        x = np.array([[0, 1, 2, 3, 4]], dtype=np.float32)
        y = model.predict(x)
        print(y)
        model_onnx = convert_keras(model)

Using quantize_model causes the model input tensor is not found in the model tf graph. Need further solution to handle this.


The description (below repo name) still says "Sinatra" instead of "Roda"

Just letting you know.

Nice catch ty!


New-ExternalHelp is not including all remarks for an example

The problem
The current platyps schema for Examples allows the following:
## Examples

### Example 1

0 or more paragraphs
1 or more code blocks
0 or more paragraphs

When the markdown is converted to MAML, only the paragraphs after the code blocks are written to the MAML file.
The problem is that most of our help content has been updated to use the pattern shown above.
Example case
I have the following example in markdown.
### EXAMPLE 3 - Run only the DSC rules with the Error severity

This example runs only the DSC rules with the Error severity on the files in the **MyDSCModule**
module.

```powershell
$DSCError = Get-ScriptAnalyzerRule -Severity Error | Where-Object SourceName -eq PSDSC
$Path = "$home\Documents\WindowsPowerShell\Modules\MyDSCModule\*"
Invoke-ScriptAnalyzerRule -Path $Path -IncludeRule $DSCError -Recurse
```

Using the **IncludeRule** parameter of `Invoke-ScriptAnalyzerRule` is more efficient than using its
**Severity** parameter, which is applied only after using all rules to analyze all module files.

The MAML that is produced contains:
      <command:example>
        <maml:title>-- EXAMPLE 3 - Run only the DSC rules with the Error severity --</maml:title>
        <dev:code>$DSCError = Get-ScriptAnalyzerRule -Severity Error | Where-Object SourceName -eq PSDSC
$Path = "$home\Documents\WindowsPowerShell\Modules\MyDSCModule\*"
Invoke-ScriptAnalyzerRule -Path $Path -IncludeRule $DSCError -Recurse</dev:code>
        <dev:remarks>
          <maml:para>Using the IncludeRule parameter of `Invoke-ScriptAnalyzerRule` is more efficient than using its Severity parameter, which is applied only after using all rules to analyze all module files.</maml:para>
        </dev:remarks>
      </command:example>

Notice that the <dev:remarks> element only contains the paragraph after the code block.
Suggested fix
New-ExternalHelp should create a <dev:remarks> element for every paragraph in the example. Inside the <command:example> element the <dev:remarks> and <dev:code> elements should be ordered as written in the markdown.
Proof of concept
I edited the MAML file to add the missing paragraph:
      <command:example>
        <maml:title>-- EXAMPLE 3 - Run only the DSC rules with the Error severity --</maml:title>
        <dev:remarks><maml:para>This example runs only the DSC rules with the Error severity on the files in the **MyDSCModule** module.</maml:para></dev:remarks>
        <dev:code>$DSCError = Get-ScriptAnalyzerRule -Severity Error | Where-Object SourceName -eq PSDSC
$Path = "$home\Documents\WindowsPowerShell\Modules\MyDSCModule\*"
Invoke-ScriptAnalyzerRule -Path $Path -IncludeRule $DSCError -Recurse</dev:code>
        <dev:remarks>
          <maml:para>Using the IncludeRule parameter of `Invoke-ScriptAnalyzerRule` is more efficient than using its Severity parameter, which is applied only after using all rules to analyze all module files.</maml:para>
        </dev:remarks>
      </command:example>

Now Get-Help displays both remarks (though not in the written order).
PS C:\Git> (Get-Help -full Get-ScriptAnalyzerRule).examples.example[2]

-- EXAMPLE 3 - Run only the DSC rules with the Error severity --

$DSCError = Get-ScriptAnalyzerRule -Severity Error | Where-Object SourceName -eq PSDSC
$Path = "$home\Documents\WindowsPowerShell\Modules\MyDSCModule\*"
Invoke-ScriptAnalyzerRule -Path $Path -IncludeRule $DSCError -Recurse

This example runs only the DSC rules with the Error severity on the files in the **MyDSCModule** module.
Using the IncludeRule parameter of `Invoke-ScriptAnalyzerRule` is more efficient than using its Severity parameter,
which is applied only after using all rules to analyze all module files.

Get-Help and the HelpInfo object model need to support this better.

This is fixed in Microsoft.PowerShell.PlatyPS v1.


Protocol Phoenix.HTML.FormData not implemented for #Ash.Changeset

Describe the bug
I'm creating login where I try to mix phx.gen.auth and example_with_auth. I hit this bug which prevents me from rendering forms.
To Reproduce
Create
This throws error above:
<.form let={f} for={@changeset} action={Routes.accounts_user_registration_path(@conn, :create)}>
eex equivalent: <%= form_for @changeset, Routes.accounts_user_registration_path(@conn, :create), fn f -> %>
When changing changeset for :user form works but is pretty much useless.
<.form let={f} for={:user} action={Routes.accounts_user_registration_path(@conn, :create)}>
eex equivalent: <%= form_for :user, Routes.accounts_user_registration_path(@conn, :create), fn f -> %>
Both heex and eex cause this bug.
Expected behavior
Form to be rendered into HTML.
** Runtime
I tried also latest master of ash and ash_phoenix with the same result.

Elixir version: 1.13.0
Erlang version: Erlang/OTP 25
OS: Ubuntu LTS 20.04
Ash version: 1.51.2
Ash_Phoenix: 0.7.1
Phoenix; 1.6.10
Phoenix_HTML: 3.2.0

Additional context
Maybe I'm using too complex forms here but I doubt it. My code is basically the same as user_registration_controller.ex and new.html.eex.
If you need access to code you can look on my GitLab. Prepare for mid upgrade mess on a small toy project with no tests. Just try to register. Oh and use env variables from .envrc.tmpl to get it up and running.
Url to trigger bug: http://localhost:4000/accounts/users/register
As you can tell I wasn't expecting someone else to use that code for anything. But I'm happy to test any changes that might help solve the issue.

Hey there! So unfortunately, the example_with_auth project is pretty out of date. What you need to do is create an AshPhoenix.Form for the changeset, and assign that. Then, to submit it, you'd create a form again, validate it with the input, and then submit it. Check out AshPhoenix.Form for more information and examples. In the case of user registration, it would end up looking something like this:
defmodule ExampleWithAuthWeb.UserRegistrationController do
  use ExampleWithAuthWeb, :controller

  alias ExampleWithAuth.Accounts
  alias ExampleWithAuth.Accounts.User
  alias ExampleWithAuthWeb.UserAuth

  def new(conn, _params) do
    form = AshPhoenix.Form.for_create(User, :register)

    render(conn, "new.html", form: form)
  end

  def create(conn, %{"user" => user_params}) do
    User
    |> AshPhoenix.Form.for_create(:register)
    # You could call `AshPhoenix.Form.validate/2` here, but passing `params` into submit does it for you
    |> AshPhoenix.Form.submit(params: user_params, api: Accounts)
    |> case do
      {:ok, user} ->
        user
        |> Ash.Changeset.for_update(:deliver_user_confirmation_instructions, %{
          confirmation_url_fun: &Routes.user_confirmation_url(conn, :confirm, &1)
        })
        |> Accounts.Api.update!()

        conn
        |> put_flash(:info, "User created successfully.")
        |> UserAuth.log_in_user(user)
      {:error, form} ->
        render(conn, "new.html", form: form)
    end
  end
end

Closing for now since there isn't a specific action to be taken for this, but feel free to continue discussing here or on the discord 👍🏻

I'll also add, I'm working on fully revamping the documentation, and given that people are still consulting example_with_auth, I'll consider updating it since that would be much faster than waiting on ash_authentication to happen.

@KronicDeth on Elixirconf EU told me about this project and auto-generated admin. I was warned that docs are not good. I'm glad you take these things seriously.

Correct, the documentation has not been the focus as the project is still in beta. It will be taken out of beta in the near future once the documentation has been fully rebuilt.


Delete .travis.yml because the service is no longer free to open source

#468 on the dev branch.

@bennr01 Your review, Please

Farewell travis, you've served us well...
I've already written it one the previous two PRs, but once again thank you for your contribution and sorry for the delay.

https://github.com/ywangd/stash/tree/dev says:

This branch is 38 commits ahead, 24 commits behind master.

How do we reconcile this?


Create a notebook to highlight filtering

Functions to highlight:

LiPD:

[x] filter_by_geo_bbox

[x] filter_by_archive_type

LiPDSeries:

[x] filter_by_name

Done in https://github.com/LinkedEarth/pylipdTutorials/commit/3a9d6fad455168082d6b09ee69241d1ddac36cba


Tokens

Coverage decreased (-4.03%) to 95.968% when pulling 8aefb2c715f477b97626b54024aa5a32c3f61aa4 on tokens into 38c6892b8a9a853b50fc47ef748f7a64dfcbe882 on master.

Coverage decreased (-3.7%) to 96.269% when pulling ffbd0291c6488e835a32aff5e1d692ecb6e85ffb on tokens into 38c6892b8a9a853b50fc47ef748f7a64dfcbe882 on master.

Coverage decreased (-52.9%) to 47.115% when pulling 63e9c1ee93965c87ee52a3f89fe223f533fc26b6 on tokens into 38c6892b8a9a853b50fc47ef748f7a64dfcbe882 on master.

Coverage remained the same at 100.0% when pulling 40869332f603daa17d8d89168c308780dc28d170 on tokens into 38c6892b8a9a853b50fc47ef748f7a64dfcbe882 on master.


Problem in using xlnet-base model

Hi, I'm trying to use the DialogXL you provide, but I have a problem.
At first, I used Transformers 3.0.2 as shown in the requirement, but a Segment fault error occurred, so I used the latest version of transformers.
This solved the above error, but "UnicodeDecodeError:'utf-8' codec can't decode byte 0x80 in position 0" error occurred.
Can you tell me how to fix that error or a link to download xlnet-base-case for transformers 3.0.2?
Thanks for conducting an interesting research.

Hi, could you show me the full error description? It seems that this error usually occurs when the program reading the dataset files rather than when loading the model.

Thanks for the answer.
When I used Transformers 3.0.2, the segment fault error mentioned above was resolved, but the following error occurred.

Hi, @so-hyeun, thanks for the interest in our work，we have updated the relevant files, you can kindly check it out.

Thanks for the quick feedback, but is the changed file correct for Transformers 3.0.2 version?
The error has not been resolved yet.

ImportError: cannot import name 'silu' error occurs
When I delete silu and run it, the same error as the picture above occurs.

Thanks again for the quick feedback.

Thanks, it works fine.

We found some problems with the previous IEMOCAP files and we have now updated the relevant files. Thanks for your friendly reminder.

Hello, first of all, thank you for always quick feedback.

By the way, the same phenomenon occurs when running the train using the newly uploaded IEMOCAP file. Can you check it again?

In addition, when I change line 131 of run.py to model =nn.DataParallel(model) to use 2 GPUs, an error occurs. If you have used multi-GPU, please advise.

Hello, first I'd like to thank you for working on such an interesting subject
I am also trying to use the model provided in the repository :
Training with MELD gives good results (comparable to your article), unfortunately, I also encountered the same issue as @so-hyeun where training with IEMOCAP gives bad performance.
Did you manage to find what was the issue ?


AMQP-652: Use Base64 By Default for Anon. Queues

JIRA: https://jira.spring.io/browse/AMQP-652

Merged as https://github.com/spring-projects/spring-amqp/commit/bbc474327cba66f8974b9c4a65fdfef97a0cee25


Default featurization and underscoring of raw fts

issue #16

default features are embedded and kept in raw format
default underscores added in separate features

not sure about right solution, but maybe auto embedding should be turned off if choices have numeric types

yeah we can play around with this a bit


Fix deprecation of passing timeout as positional argument to brpop

The recent v4.8.0 of the redis gem deprecated passing timeout as a
positional argument in blocking commands like brpop:
https://github.com/redis/redis-rb/commit/08eea742485c054680ade3f9afd83f313c355595
v4.6 or greater of the redis gem is currently required and it already
included support for a :timeout hash option:
https://github.com/redis/redis-rb/blob/v4.6.0/lib/redis/distributed.rb#L465
Therefore we can switch to passing the timeout as a hash option.
Fixes #136.

Thanks for the PR!