text:
Java-11 feign client issue

Not able to do a feign client call to a service :
public interface OrderClient {

  @RequestLine("POST /place/v1/order")
  @Headers({"Content-Type: application/json", "X-USER-ID: {id}"})
  Mono<OrderResponse> placeOrder(
          OrderRequest requestDto, @Param("id") String id);
}

  @Bean
  OrderClient orderClient() {

    return Java11ReactiveFeign.<OrderClient>builder()
        .objectMapper(objectMapper)
        .options(
            new Java11ReactiveOptions.Builder()
                .setRequestTimeoutMillis(2000)
                .setConnectTimeoutMillis(2000)
                .build())
        .retryWhen(BasicReactiveRetryPolicy.retry(maxRetry))
        .target(ReactiveWalletClient.class, "http://127.0.0.1:5050");
  }

Getting internal server error here, call is going to the desired endpoint.
whereas when directly hit the service I was able to get the response.
It worked fine fine with other modules , used feign-reactor-webclient earlier along with java-8.
Header : String id
Body: OrderRequest dto
what am doing wrong?
feign.FeignException$InternalServerError: [500 Internal Server Error] during [POST] to [http://127.0.0.1:5050/place/v1/order] [OrderClient#placeOrder(OrderRequest,String)]: [Encountered an internal server error]
	at feign.FeignException.serverErrorStatus(FeignException.java:250) ~[feign-core-11.8.jar:na]
	at feign.FeignException.errorStatus(FeignException.java:197) ~[feign-core-11.8.jar:na]
	at feign.FeignException.errorStatus(FeignException.java:185) ~[feign-core-11.8.jar:na]
	at feign.codec.ErrorDecoder$Default.decode(ErrorDecoder.java:92) ~[feign-core-11.8.jar:na]
	at reactivefeign.client.statushandler.ReactiveStatusHandlers$1.lambda$decode$0(ReactiveStatusHandlers.java:49) ~[feign-reactor-core-3.2.0.jar:na]
	at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:106) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxDefaultIfEmpty$DefaultIfEmptySubscriber.onNext(FluxDefaultIfEmpty.java:101) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:210) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:210) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:127) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1816) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoReduceSeed$ReduceSeedSubscriber.onComplete(MonoReduceSeed.java:165) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:368) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onComplete(FluxConcatMap.java:276) ~[reactor-core-3.4.15.jar:3.4.15]
	at org.eclipse.jetty.reactive.client.internal.QueuedSinglePublisher.proceed(QueuedSinglePublisher.java:137) ~[jetty-reactive-httpclient-1.1.11.jar:na]
	at org.eclipse.jetty.reactive.client.internal.QueuedSinglePublisher.onRequest(QueuedSinglePublisher.java:69) ~[jetty-reactive-httpclient-1.1.11.jar:na]
	at org.eclipse.jetty.reactive.client.internal.AbstractSinglePublisher.request(AbstractSinglePublisher.java:84) ~[jetty-reactive-httpclient-1.1.11.jar:na]
	at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:236) ~[reactor-core-3.4.15.jar:3.4.15]
	at org.eclipse.jetty.reactive.client.internal.AbstractSinglePublisher.subscribe(AbstractSinglePublisher.java:56) ~[jetty-reactive-httpclient-1.1.11.jar:na]
	at reactor.core.publisher.FluxSource.subscribe(FluxSource.java:67) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.InternalMonoOperator.subscribe(InternalMonoOperator.java:64) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:157) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1816) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:151) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:127) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onNext(MonoPeekTerminal.java:180) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxPeekFuseable$PeekFuseableConditionalSubscriber.onNext(FluxPeekFuseable.java:503) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxMapFuseable$MapFuseableConditionalSubscriber.onNext(FluxMapFuseable.java:295) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onNext(MonoPeekTerminal.java:180) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxPeekFuseable$PeekConditionalSubscriber.onNext(FluxPeekFuseable.java:854) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:79) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:127) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1816) ~[reactor-core-3.4.15.jar:3.4.15]
	at reactor.core.publisher.MonoCompletionStage.lambda$subscribe$0(MonoCompletionStage.java:83) ~[reactor-core-3.4.15.jar:3.4.15]
	at java.base/java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:859) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:837) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:506) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture.postFire(CompletableFuture.java:610) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:840) ~[na:na]
	at java.base/java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:479) ~[na:na]
	at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) ~[na:na]
	at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020) ~[na:na]
	at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) ~[na:na]
	at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) ~[na:na]
	at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) ~[na:na]

tried sending invalid request also, it gave the same internal server error.
Getting internal server in both the cases (valid and invalid request).
could you folks please help?

any update on this folks ?

repo: Playtika/feign-reactive


text:
Bruchfaktor Verbesserungen

Hi,
wenn ich die Regeln richtig verstehe, sollte der Bruchfaktor wie folgt abgeändert werden:
Bruchfaktor grundsätzlich nur bei bestätigten Patzern/Erfolge -> Also successLevel > 2 und nicht 1
Ebenso Bruchfaktor nur beim Parrieren von bestätigten Erfolgen -> dh der check auf "Halbe Verteidigung" muss auch durch einen successLevel Check ersetzt werden.
Bruchfaktor beim Parrieren nur wenn die Parade auch klappt, sonst parriere ich ja nicht -> prüfung auf den eigenen successLevel
Pull Request vorschlag : https://github.com/Plushtoast/dsa5-foundryVTT/pull/811

Ja das ist vermutlich auslegungssache. Die Regeln sind hier mit "#Wenn er einen Kritischen Treffer mit seiner Waffe pariert." nicht ganz klar ob der "Versuch Strafbar ist" ;)
Eine gescheiterte Parade gegen einen Crit wird halt dann sehr Punishing, da unter umständen Waffe und Rüstung beschädigt wird.
Dann wäre die abfrage einfach ohne den "testData.successLevel > 0 &&" Teil
Evtl dafür config option? oder halt einfach anzeigen man muss ja nicht auf den bruchfaktor button drücken wenn man meint eine gescheiterte parade richtet nichts aus.

Ich hab das bei uns so gemacht, dass man sich dann aussuchen kann, ob die Waffe oder die Rüstung beschädigt wird.
Aber aus dem Grund wie du es sagst. Es ist nicht 100% klar, wie es gedacht war.

Ok, ich mach das rein. Allerdings ohne die Abfrage auf erfolgreiches Parieren.
Meiner Meinung nach kann fehlgeschlagenes Parieren auch bedeuten, dass man eben doch auch dem Angriff des Gegners ungünstig entgegen wirkt. Was zb. den Parier beschädigen kann oder eine Scharte in die Waffe schlägt, aber der Angriff trotzdem durchrutscht.

source: gharchive/issue

authors: Plushtoast Qowy

license_type: permissive

license_source: github-api


text:
Comments: Add button / icon to open the original post in a new tab

Currently the only way to comment on the podcasts in the podcast index is to copy the link of the post and use it to find it in the instance where the user has and account.
The only way to get the original post link, currently, is to copy it from the timestamp. Having a link to the post/comment is a comment UX practice, but it is kind of a hidden feature, as it is not that intuitive.
I suggest that we add a more clear indication on how to open the original post or copy the post link.
A common icon for opening a link in another domain is like the one shown in the screenshot below:

Related issues

#233

Links and References

Matodon thread - https://social.oberhauser.space/@obale/109961887303322180

New mockup from @nathangathright : https://xoxo.zone/@nathan/109973226991064790
live: https://nathangathright.github.io/comment-thread-mockup/

Should make sure this works good on mobile. Popup dialogs like this tend to be a pain to use on mobile devices.

I was looking into the code today.
Since dialog requires the javascript method showModal is used to show the dialog, I'm assuming it does not work well with React. The fact that there are react components for modal stuff is likely an indication that this is complicated.
I'm tempted to use a simple prompt instead.
Also, I'll have to include an option to remove/update the saved home instance, otherwise it would be a "write once" scenario.
Aside from that, I think I understood the stuff.

The dialog element and showModal method are newer elements, but they’re available in all major browsers. I’m unclear why you think this will be an issue with React.
I actually did make a version with prompt first, but it had a major drawback: it was blocked by the browser’s popup blocker. Since I couldn’t set an EventListener on the submit button of the prompt, trying to open a new window after a prompt didn't appear to be in response to a user event, and it was blocked.
I think a way to clear the localStorage would be nice, but was unclear where we’d like to expose controls for that. Maybe we could just store it as a cookie with a short expiration date. Otherwise, asking the user to clear it manually isn’t that complicated:

Hi @nathangathright ,

I think a way to clear the localStorage would be nice, but was unclear where we’d like to expose controls for that. Maybe we could just store it as a cookie with a short expiration date. Otherwise, asking the user to clear it manually isn’t that complicated:

I thought about adding an extra item in the menu, like "forget my account home instance" or something like that.
Contextually it is not an action that belongs to any individual post, but in the other hand, it would easily educate the user on how to do it, so I think it is an ok approximation.

I’m unclear why you think this will be an issue with React.

Take into account I'm writing as someone that learns React on demand (i.e. the minimum I need to contribute).
React is state based and more descriptive and reactive (as per its name 😄) then imperative.
You typically don't give commands like showModal or show, but you change the state to with a property like isShowing and adapt your rendering method to deal with that. So I'll need to research a bit what is the best way do this in react.
Thanks for clearing out the drawback on using prompt.

Regarding the remote interact (i.e. follow, reply, etc...), the patterns https://${instance.hostname}/authorize_interaction?acct=${username}
and https://${instance.hostname}/authorize_interaction?uri=${url} are no a standard, they work for Mastodon and may work for some other instance "types". I consider it an ok first implementation, but moving forward it would be good to have something based on standard protocols.
To my best knowledge, the state of the art is to use WebFinger to find out the OStatus subscribe URL for the Actor (I'm not sure which one, the interactor or the "interactee"). My understanding is that this is intended only for subscriptions (i.e follow), but that many instances "types" (tested with Mastodon and Pleroma) also can use it for redirecting to a post, as represented in their instance, for further interaction (e.g. boosting, favoriting, bookmarking, liking, replying, etc...).
Here are some references:

https://socialhub.activitypub.rocks/t/represent-endpoint-for-remote-interaction/480
https://socialhub.activitypub.rocks/t/what-is-the-current-spec-for-remote-follow/2020
https://socialhub.activitypub.rocks/t/cross-instance-interactions-determining-the-kind-of-action-user-wants-to-perform-to-a-remote-object/734
https://www.hughrundle.net/how-to-implement-remote-following-for-your-activitypub-project/
WebFinger Spec - https://www.rfc-editor.org/rfc/rfc7033
https://en.wikipedia.org/wiki/OStatus

@nathangathright , if you have any good references for this, please share.

I did some more tests with the WebFinger protocol to get the remote interact URL pattern.
To do the WebFinger request I need to pass the account of an existing user in the instance where the interaction will happen.
As far as I can tell, the remote interact URL pattern does not change from user to user, yet we will need to pass a user to get it.
We'll have to prompt for the account of the user initiating the interaction then, not only the instance host.
Example
I want to
interact (e.g. comment) with the post https://podcastindex.social/@dave/110237990624503755 from my account, dellagustin@fosstodon.org.
I need to send the request https://fosstodon.org/.well-known/webfinger?resource=acct:dellagustin@fosstodon.org, it will return:
{
    "subject": "acct:dellagustin@fosstodon.org",
    "aliases": [
        "https://fosstodon.org/@dellagustin",
        "https://fosstodon.org/users/dellagustin"
    ],
    "links": [
        {
            "rel": "http://webfinger.net/rel/profile-page",
            "type": "text/html",
            "href": "https://fosstodon.org/@dellagustin"
        },
        {
            "rel": "self",
            "type": "application/activity+json",
            "href": "https://fosstodon.org/users/dellagustin"
        },
        {
            "rel": "http://ostatus.org/schema/1.0/subscribe",
            "template": "https://fosstodon.org/authorize_interaction?uri={uri}"
        }
    ]
}

I'll get the template from the link with rel equal to http://ostatus.org/schema/1.0/subscribe, then replace {uri} with https://podcastindex.social/@dave/110237990624503755, and open the resulting url on the browser. This should open the post in my instance so that I can interact with it there. A login flow takes place if I am not logged in yet.

Some more test results of the URLs resulting of the approach above:

https://fosstodon.org - Mastodon - v4.1.2

👍interact with post - https://fosstodon.org/authorize_interaction?uri=https://podcastindex.social/@js/110238757531058833
👍interact with user - https://fosstodon.org/authorize_interaction?uri=@js@podcastindex.social
👍interact with user - https://fosstodon.org/authorize_interaction?uri=js@podcastindex.social
👍interact with user - https://fosstodon.org/authorize_interaction?uri=https://podcastindex.social/@js

https://blob.cat - Akkoma - 3.3.1-0-gbba467b39-blob (a fork of Pleroma)

👍interact with post - https://blob.cat/ostatus_subscribe?acct=https://podcastindex.social/@js/110238757531058833
👎 interact with user - https://blob.cat/ostatus_subscribe?acct=@js@podcastindex.social

"Error fetching user"

👍interact with user - https://blob.cat/ostatus_subscribe?acct=js@podcastindex.social
👎interact with user - https://blob.cat/ostatus_subscribe?acct=https://podcastindex.social/@js

HTTP ERROR 500

Implemented with https://github.com/Podcastindex-org/web-ui/pull/253.

authors: dellagustin ericpp nathangathright

repo: Podcastindex-org/web-ui

license: MIT


text:
Some objects on map

Short Description:
Show some objects on map

@Reaver01, review and test this, please.

Doesn't put anything on the map. just throws errors

source: gharchive/pull-request

authors: Alex-Gramm Reaver01 douglascamata

repo: PokemonGoF/PokemonGo-Bot


text:
peripheral.discoverAllServicesAndCharacteristics() finds cached (outdated) services

I'm building a BLE server and as I add or remove services, they are not found through the peripheral.discoverAllServicesAndCharacteristics() and peripheral.services() commands.
Other Bluetooth scanners such as nRF Connect and LightBlue both find the changed (added/removed) services, but FlutterBleLib does not.
I've tried this with both 2.3.2 and 3.0.0-beta and both have the same issue.
I've tried flutter clean.
Uninstalled the flutter app and reinstalled through debug.
I even tried the example app from FlutterBleLib, but it also shows the old services (some of which don't even exist on the server any more).
Is there some other way to clear the cache and have it actually read the services again?

Using the big hammer method of resetting the factor defaults on the phone allowed it to find the updated services, but there must be a simpler way.

Android or iOS?

peripheral.connect(refreshGatt: true)

Thanks guys...
Platform is Android.  I'll try the refreshGatt: true.

Problem resolved.

authors: Simpler1 jobfeikens mikolak

repo: Polidea/FlutterBleLib


text:
chore: rename details to description in CreateVenueParams

The following breaking changes are from earlier commits
BREAKING CHANGE:

rename details to description in CreateVenueParams interface.

:tada: This PR is included in version 12.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 13.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 14.0.0-alpha.1 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 14.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: PolymathNetwork/polymesh-sdk


text:
v0.5.2

Support the ITN chain.
Re-design network dropdown.
Show account's locked balance in account header.

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

authors: remon-nashid wahidrahim

repo: PolymathNetwork/polymesh-wallet


text:
Default value of properties location

Please make it more clear that default values do not go in the properties block but rather in the constructor. This question has come up in multiple locations #114, slack, and twitter

I will include it in the docs

repo: Polymer/lit-element

license_source: bigquery


text:
Exceptions in firstUpdated are not logged to console

Description
In Chrome, exceptions thrown in firstUpdated() are reported differently from exceptions thrown in render(). There does not appear to be any difference in Safari.
In Chrome:
Thrown in render():

Thrown in firstUpdated(). This is only visible with "Verbose" logging enabled

Steps to Reproduce
class MyElement extends LitElement {
//....
  firstUpdated() {
    // If we throw the error here, it only appears in the console if verbose logging is enabled
    throw new Error('Thrown from firstUpdated');
  }
  render() {
    // If we throw the error here, it appears in the console in red
    throw new Error('Thrown from render');
  }
}

Expected Results
Both errors should be logged to the console in red.
Actual Results
Only the render() error is logged in red. The firstUpdated() error is only shown when Verbose logging is enabled.
Browsers Affected

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari 11
[ ] Safari 10
[ ] IE 11

Versions

lit-element: v2.2.1
webcomponents: v2.4.0

Sorry for the delay on this. We're unable to repro this issue now, see https://output.jsbin.com/meramin.
Closing as this no longer seems to be a problem. Please feel free to re-open with more info if the problem persists.

authors: chooglen sorvell


text:
[0.8] Ready callback and element initialization

The current docs for 0.8 say the following about the ready callback:

The ready method is part of an element’s lifecycle and is automatically called ‘bottom-up’ after the element’s template has been stamped and all elements inside the element’s local DOM have been configured (with values bound from parents, deserialized attributes, or else default values) and had their ready method called. Implement ready when it’s necessary to manipulate an element’s local DOM when the element is constructed.

However, I'm not seeing that "bottom-up" behavior when using parent Polymer elements containing children Polymer elements. You can see this in the JS console output of http://jsbin.com/lisave/33/edit?html,console,output
You'll see that each of the x-parent's callbacks (created, ready, attached) is invoked before the x-child elements' callbacks. It seems like what's actually happening is "top-down" rather than "bottom-up".
@arthurevans, this might be a docs issue, or the docs might be correct about the intended behavior and there's a bug in Polymer.

This is by design. The ready ordering mentioned in the documentation refers only to the fact that an element's 'local DOM' should be all call ready before the element itself calls ready. There is no ordering guarantee of ready between elements in the same dom tree, but generally it will be called in document order.

This issue was moved to Polymer/docs#1163

authors: arthurevans jeffposnick sorvell

repo: Polymer/polymer


text:
[gen-typescript-declarations + analyzer] Better class heritage handling.

The Polymer 3 (and 2) types are complete AFAIK and compiling cleanly after these changes. These last changes are mostly around handling class heritage more correctly.
Analyzer changes

Parse @extends {Foo} annotations (previously only @extends Foo worked).

Treat @constructor annotations as classes. This is helpful for understanding class heritage and fixes super classes for some of the bundled Polymer elements. It also introduces some noise, so I added some @private annotations in Polymer (I also found some regular class declarations that should have been @private while I was at it).

Add an isLegacyPolymerFactoryCall property to PolymerElement features so that we can do some special casing there. Previously there was no good way to distinguish between calls to Polymer() and any other kind of custom element (even non-Polymer CEs are considered PolymerElements by Analyzer).

Type generator changes

Handle super classes more correctly. Previously we just did it kind of wrong and assumed too many things extended PolymerElement. Now we simply trust Analyzer's model, and have a special case for legacy Polymer function calls, which now extend PolymerLegacyMixin & HTMLElement instead of PolymerElement.

Mixin instance interfaces now extend the instance interfaces for the mixins that they automatically apply. This worked before when you received an interface via a constructor call, because the constructor hierarchy was complete, and TypeScript is smart enough to figure out the instance hierarchy from that. But this way you can also cast directly to the interface and get the full picture.

Polymer source changes

Polymer 3
Polymer 2

The CLI integration test is failing because linter is now picking up the double definition of Polymer.Element in 2.x. My pending changes to the 2.x branch fix this, so if the changes look good we would need to tag a 2.x release to make the CLI tests pass again.

I've temporarily disabled the lint check for the Polymer 2.x application template because it will return a warning until https://github.com/Polymer/polymer/pull/5300 is released to bower. That change depends on this PR being released to the generator, though, so I'll re-enable this test afterwards.

repo: Polymer/tools


text:
proto2schema 1/n: Schema generation

This is one of multiple PRs that will generate schemas from manifests via protobufs. So far, this creates a copy-and-past BUILD rule using a Kotlin CLI. Later, this will change to actually generate Kotlin jars.
This PR also introduces the first use of Kotlin Poet in the project. Schema generation via this library is exercised in a test. Once @piotrswigon 's efforts to serialize manifests (read: schemas) into protos are accomplished, we'll be able to adapt this CL to generate schemas from manifests end-to-end.
I anticipate that the names for the build macros don't quite fit our project, I'm happy to take suggestions (a nod to you, @csilvestrini).

After discussions last week, the strategy for codegeneration has changed. As a result, I'm going to close this PR.
The feedback here will be useful to future PRs, however.

repo: PolymerLabs/arcs


text:
Not all 10.2 emojis are showing up on the keyboard

I noticed that when I was looking through the emojis after installing some of that flags are missing on the keyboard (still show up in the predictive text though). On a device running 10.2 there are 5 additional flag emojis before the first flag On 10.1.1 + Emoji10. And yes, I do have the appropriate font downloaded. (More may be missing but those are the ones I noticed)

Resolved.

authors: PoomSmart Zeebins


text:
recording: OnTouchEventListener try catch guard to swallow unexpected errors take 2

:bulb: Motivation and Context
Tries to fix https://github.com/PostHog/posthog-react-native-session-replay/issues/4
It's unclear if PostHog SDK is responsible for that, since the SDK intercepts the touch, the SDK will be always part of the stack trace, it does not mean its the SDK causing it.
:green_heart: How did you test it?
:pencil: Checklist

[X] I reviewed the submitted code.
[ ] I added tests to verify the changes.
[ ] I updated the docs if needed.
[X] No breaking change or entry added to the changelog.

Only comment is that we may want to move the isSessionReplayEnabled check to when generateMouseInteractios is called so we get some error logs even when session replay is not enabled. If that makes sense to you. Otherwise LGMT

this code is not even executed if session replay is disabled, so moving the check would not have any effect

repo: PostHog/posthog-android


text:
SyncPlayer crashes with two connected Android instances. When one linux and one android SyncPlayer are connected, it Resets seek to 0 when linux seeks.

I was starting to hack together a syncplay client myself and then I stumbled upon this. Seems to work, thats great! But came upon a debilitating bug. I suspect it might be a simple thing in the interaction with the media player. based on some experiments I did. Before I dive into the code myself, thought I'd ask. (More than happy to help debug if you like.)

One linux syncplay and one Android syncplayer, both connected to syncplay.pl:8996.
Works great. If you use the seek bar on the Android, then Linux also seeks, Nice.
But if you see on the Linux client, then the Android client jumps back to 0, and tells the Linux client also to jump back to zero.

(I ran tcpflow to see the traffic and I can see the sequence of linux announcing the seek, and immediately the android version responds with a seek 0, so both are now back to the start of the video).

Two androids syncplayers connected, same server and room as above.
Seek on any Android syncplayer, and it immediately crashes. The android syncplayer on which you seek is the one that crashes.

Without looking at the code, just based on the bhaviour, I am guessing that when the linux client announces a seek, the android syncplayer does the seek to the announced offset, this maybe fails for some reason, and maybe causes a jump back to 0sec. This is then announced to the server from the android syncplayer. Just a guess.
Please let me know how I can help. tcpflow dumps. logcat, test runs of modified code, run connected to you when you are watching ... anything you like, just let me know.
-- //Shrikumar

Could you send the logcat for two android syncplayers crashing while seeking? I'll look into that first.
It might also help me if you can share the tcpflow dumps where you saw linux and android seeking issues.
Thanks!

Sure thing.
Just realized that I uninstalled SyncPlayer on my 2nd android device (so that I could try linux syncplay under GNUroot Debian). I will be able to send you android logcats only later on.
But, meantime here are tcpflow from the android-syncplayer and linux-syncplay experiments.
The sequence was: I cued up the movie on both devices, let it play for a bit. Then I did a seek on the the android-syncplayer to roughly the middle of the movie, and the linux syncplay nicely caught up to it. Then I did a little seek with the keyboard on the linux mplayer/syncplay. Immediately syncplay linux told android/syncplayer to seek, and a moment later, android/syncplayer told linux/syncplay to jump back to 0:01, ie almost very start the video. Everything continues from then one, except now both are again at the start of the video.
The android/syncplayer has the nickname "zte". The linux/syncplay has no nickname. '
This tcpflow was captured on the linux device (obviously), whose IP addess is 172.20.2.122.
The sever is syncplay.pl:8996.
Hope this is useful.
If you wish a logcat from the android side, please let me know and I can repro. Or, even better, if we can co-ordinate a time, you run an android/syncplayer on your device and sync with my linux/syncplay, you can grab as many logcats as you like.
syncplayer-syncplay-jumps-back-to-0.zip
-- //Shrikumar

This should be fixed in v1.6.4.

authors: PowerInside shrikumarh

repo: PowerInside/syncplayer


text:
ADRecycleBin: Remove duplicate code

Several rows of code that exist in Get-TargetResource is duplicated in Test-TargetResource. Suggest calling Get-TargetResource from Test-TargetResource and the use the read-only property RecycleBinEnabled to determine the state. This would also simplify the unit tests for Test-TargetResource since we could mock Get-TargetResource.
Duplicated code
https://github.com/PowerShell/xActiveDirectory/blob/6cc03a65208faa8d4b8f4730983a23397de83e47/DSCResources/MSFT_xADRecycleBin/MSFT_xADRecycleBin.psm1#L149-L190

Closing this as this issue will be obsolete when PR #462 is merged.

repo: PowerShell/ActiveDirectoryDsc


text:
Add pull request template and issue templates

This is an automatic batch pull request.

Pull-request updated, HEAD is now a0dc5b187a7e2f1bc8c47b5501075628a97ad92c

repo: PowerShell/CertificateDsc


text:
New-Item Type SymbolicLink on Unix-like platforms: converts relative target paths to absolute ones, doesn't normalize path separators on macOS

PR https://github.com/PowerShell/PowerShell/pull/12797 tried to implement support for relative target paths for symbolic links (symlinks).
On Windows, this now works properly as of PowerShell Core 7.1.0-preview.4, including normalizing path separators to \.
On Unix-like platforms, a relative input path is still unexpectedly converted to a full path and stored as such in the symlink.
Curiously that doesn't happen when you use \ as a separator on macOS  - which must be normalized to / on Unix-like platforms - but the normalization doesn't happen and the \-based relative path is stored as-is, which results in a broken symlink; on Linux, the unexpected conversion to an absolute path (with appropriate separators) takes place.
Steps to reproduce
# OK on Windows, FAILS on macOS and Linux.
Describe "New-Item symlinks" {
  BeforeAll {
    Push-Location testdrive:

    $targets = "./$PID.tmp", ".\$PID.tmp"
    $lnk = "$PID-L.tmp"

    'foo' > $targets[0]

  }

  It "Can create symlink with relative target <target>" -TestCases @{ target = $targets[0] }, @{ target = $targets[1] } {
    param([string] $target)

    $null = New-Item -Type SymbolicLink  $lnk -Target $target  -Force

    # Make sure the relative target path was recorded as such and uses
    # the platform-appropriate separator.
    (Get-Item $lnk).Target | Should -Be ($target -replace '[\\/]', [IO.Path]::DirectorySeparatorChar)

  }

  AfterAll {
    Pop-Location
  }
}

Expected behavior
The tests should succeed on all platforms.
Actual behavior
On macOS and Linux, both tests fail:
The first test fails, because the relative path was converted to an absolute one.
      Expected: './95916.tmp'
      But was:  '/private/t...'

On macOS, the second test fails because \ wasn't normalized to /:
      Expected: './95916.tmp'
      But was:  '.\95916.tmp'

On Linux, by contrast, the test fails because the relative path is again unexpectedly converted to an absolute one.
Environment data
PowerShell Core 7.1.0-preview.4

@mklement0 I can not debug on Unix and investigate the issue. :-(
If you look tests in #12797 you can see that on MacOs we have to have a workaround for TestDrive - maybe it is related to the issue.
Also the fix is based on SessionState.Internal.CurrentLocation.ProviderPath - perhaps this works different on different platforms.

@iSazonov  I see. Not using TestDrive: (using a directory that isn't a symlink) on macOS doesn't make a difference - the tests still fail in the same way.

I looked on WSL. I think it is how SessionState.Internal.CurrentLocation.ProviderPath works. On Windows it contains a relative path, on Linux - absolute one, on MacOs - ???.

@iSazonov
Arguably, you shouldn't try to resolve a relative path at all: you should only check it for syntactic validity (e.g., no illegal characters) and normalize the separators.
Note that this ties in with #9067, which asks that it be possible to create symlinks to nonexistent (not yet existent) targets.

There is a fundamental problem - there is no way to verify that path is correct without accessing the OS therefore resolving paths is preferred. I believe  #9067 could be additive but explicit to avoid erroneous links due to typos.

@iSazonov
It's fine to resolve for the purpose of validation, but when it comes to creating the symlink, it's sufficient to use the given target path as-is, with only the separators normalized - this should fix the problem on macOS and Linux.
Incidentally, #9067 seemingly did get implemented in 7.0, perhaps accidentally, because it amounts to a breaking change: non-existent target paths are now quietly accepted (try New-Item -Type SymbolicLink tmpLnk -Target NoSuchTarget) - in 6.x and in Windows PowerShell you get an error instead.

The macOS path-separator problem no longer occurs.
I've created a new issue that focuses just on the relative-path issue and also has an updated (working in v5) Pester test: #1523

repo: PowerShell/PowerShell


text:
PowerShell will not allow me to enable unencrypted connections, due to missing Network Connection Profiles

Steps to reproduce

Enable Hyper-V
Install Cisco VPN client
Install Proton VPN client
Enable Windows Subsystem for Linux (WSL)
Install Wireshark with NPCAP virtual adapter

C:\Users\TrevorSullivan> Set-Item -Path WSMan:\localhost\Service\AllowUnencrypted -Value true
Set-Item: WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.
C:\Users\TrevorSullivan> Get-NetConnectionProfile

Name             : Andromeda
InterfaceAlias   : Wi-Fi
InterfaceIndex   : 3
NetworkCategory  : Private
IPv4Connectivity : Internet
IPv6Connectivity : NoTraffic

C:\Users\TrevorSullivan> Enter-PSSession -ComputerName localhost
Enter-PSSession: Connecting to remote server localhost failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.

Obviously, the Enter-PSSession command fails with Access is denied. I traced this back to the AllowUnencrypted setting on the WinRM service.

As you can see from the screenshots, the "Network Category" field is straight up missing for all but one of my network connections. Also, there's only one connection profile returned by Get-NetConnectionProfile, and it's already set to Private.
How am I supposed to discover which of my network connections is being detected as public?
Expected behavior

Network Category is set for all network connections
Get-NetConnectionProfile shows me which of my networks is public
PowerShell sets WinRM configuration to allow unencrypted, without throwing any error messages

Actual behavior
PowerShell indicates that one of my network connections is public, although as best I can tell, none of them are set that way. There's a conflict between what's being reported by PowerShell and what's being reported by Windows 10.
Environment data
Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.19041
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

@SteveL-MSFT this might need to be passed along to the windows team responsible for this module; if their module is reporting incorrect information, it'll make life difficult for folks trying to handle this kind of thing in any automated fashion.

Yeah I don't know what's up with that API, but try this:
using namespace System.Runtime.InteropServices

$ERROR_NOT_CONNECTED = 0x800708CA
$NLM_ENUM_NETWORK_ALL = 0x03

enum NlmNetworkCategory {
    Public = 0x00
    Private = 0x01
    DomainAuthenticated = 0x02
}

# Don't know the progid, but here's the docs:
# https://docs.microsoft.com/en-us/windows/win32/api/netlistmgr/nn-netlistmgr-inetworklistmanager
$type = [type]::GetTypeFromCLSID('DCB00C01-570F-4A9B-8D69-199FDBA5723B')
$netMgr = $null
$networks = $null
try {
    $netMgr = [Activator]::CreateInstance($type)

    $networks = $netMgr.GetNetworks($NLM_ENUM_NETWORK_ALL)
    foreach ($network in $networks) {
        try {
            $category = [NlmNetworkCategory]::DomainAuthenticated
            $category.value__ = $network.GetCategory()

            <# yield return #> [PSCustomObject]@{
                Name = $network.GetName()
                Category = $category
            }

            # Uncomment to set all public to private.
            # if ($category -eq [NlmNetworkCategory]::Public) {
            #     try {
            #         $network.SetCategory([NlmNetworkCategory]::Private)
            #     } catch [System.Runtime.InteropServices.COMException] {
            #         # SetCategory will throw when it's not connected, but it'll still work anyway.
            #         if ($PSItem.Exception.HResult -ne $ERROR_NOT_CONNECTED) {
            #             throw $PSItem
            #         }
            #     }
            # }
        } finally {
            if ($null -ne $network) {
                $null = [Marshal]::ReleaseComObject($network)
            }
        }
    }
} finally {
    if ($null -ne $networks) {
        $null = [Marshal]::ReleaseComObject($networks)
    }

    if ($null -ne $netMgr) {
        $null = [Marshal]::ReleaseComObject($netMgr)
    }
}

I was able to work around this problem by creating a self-signed certificate, and setting up an HTTPS listener for WinRM. That way, I don't need to worry about enabling AllowUnencrypted.
Still, this should be considered a bug.
@SeeminglyScience good idea. I tried that code, and it seems to have set the category to private. However, PowerShell is still complaining. See below.
C:\Users\TrevorSullivan> $networks | % { $_.getcategory() }
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
C:\Users\TrevorSullivan> Set-Item -Path WSMan:\localhost\Service\AllowUnencrypted -Value true
Set-Item: WinRM firewall exception will not work since one of the network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again.

Curious why you are enabling unencrypted connections, that's just plain bad behaviour and should be avoidable of any decent WinRM client.

So I had a look into this and the code that is generating this error is not in PowerShell but the native WSMan API that PowerShell is calling. You can verify this by finding that exact same error message in C:\Windows\System32\en-US\WsmRes.dll.mui

So PowerShell is effectively calling https://github.com/PowerShell/PowerShell/blob/3effa204103460c996a8612aa70718fdf924047d/src/Microsoft.WSMan.Management/ConfigProvider.cs#L2689 and the exception from this is what you are seeing in the error message. PowerShell can't do much about this as the check is performed in a dll not owned by this team so @vexx32 suggestion is the next step https://github.com/PowerShell/PowerShell/issues/13654#issuecomment-694944801.
For your actual issue, you shouldn't ever really set this config option to True. Unless you are using a 3rd party WinRM library that doesn't support message encryption over NTLM or Kerberos then your only real option is to use HTTPS as you've pointed out. By having to set this to True any data that is exchanged will be in plaintext which is really dangerous, considering how easy it is to set up a self signed cert then a HTTPS listener isn't really that harder to do. I would even consider finding a different WinRM client if possible as this should be something added from the get go.
If you really, really, really want to shoot yourself in the foot I believe you can set this policy through GPO which effectively means it's a registry key. Searching the registry for AllowUnencrypted might yield some extra info.


text:
Add a configurable timeout for IFeedbackProvider

Summary of the new feature / enhancement
As a user I would like to experiment with feedback providers that are slower than 300ms so I can validate their usefulness.
The Feedback Providers RFC is at https://github.com/PowerShell/PowerShell-RFC/pull/352
This has been discussed and it's likely that it won't be implemented but it would be good to record here:

Proposed technical implementation details (optional)
IFeedbackProvider can have an additional property TimeoutMilliseconds that can be set by the developer of a feedback provider so the FeedbackHub that dispatches the feedback tasks set the maximum task waiting time to that of the slowest provider.
This PR was created before this issue and implements the timeout TimeoutMilliseconds override: https://github.com/PowerShell/PowerShell/pull/19911

For @SteveL-MSFT concerns I have a couple of ideas but I don't know how feasible they are:

For command predictors, I don't believe they're hooked up to IFeedbackProvider's yet. PredictInputAsync() has it's own timeout of 20ms (versus the FeedbackHub's 300ms) so it could choose not to register slow providers.
In future the feedback provider results could be streamed out as they complete instead of waiting for Task.WaitAll() to be finished. On an interrupt from the user (any input, not ctrl-c) the slow tasks could be cancelled so they wouldn't be holding the prompt. This cancellation on continued typing would also mean that feedback providers wouldn't be triggered repeatedly when you paste a multi-line snippet into the terminal.

It probably makes sense for FeedbackProvider implementations to declare what they need for timeout.  However, anything that goes off the box may not work for any predefined timeout.  Different users will have different latency so what works well in an environment with high speed internet may not work for many other users.
I do think for developers, maybe it would be useful if we emitted a debug message for FeedbackProviders that timed out if DebugPreferences is set to Continue?

Are you saying that feedback providers will set their own timeouts? I think we would probably need a timeout that is controlled/set by the engine to make sure no feedback provider just hangs the users experience. It may be too complex but we could consider having the default timeout be 300ms when not specifically specified by the feedback provider and if the feedback provider declares a timer >300ms we just increase the default timeout for that one to be 2000ms (or whatever we determine) so that a feedback provider doesnt just hang the experience?

I wonder if it makes sense to bucketize the timeout options to be something like small (300ms)/medium(300-1500ms)/large (<3000ms). That way we can still let users expand it if needed but also not have undetermined timeouts from off box calls.

Based on my experience, it probably should be configurable based on trigger, like say maybe I want longer timeouts for error evaluations so they can look up something online, but I don't want this happening on every single "success line".

authors: JustinGrote ShaunLawrie SteveL-MSFT StevenBucher98


text:
Get-AzDataLakeGen2ItemContent : Service request failed.Status: 400 (BadRequest) ErrorCode: IncomingOperationUntrusted

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest released version
[X] Search the existing issues.
[X] Refer to the FAQ.
[X] Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce
I am trying to run the below PowerShell commands but keep getting the below error messages.
PS cmds:
PS C:\Users\a134363> $ctx = New-AzStorageContext -StorageAccountName 'onelake' -UseConnectedAccount -endpoint 'fabric.microsoft.com'
$workspaceName = 'ida-bi-dev-arch-poc'
$itemPath = 'MelindaTestLakhouse.lakehouse/Files/PowerQueryTemplate.pqt'
$downloadFilePath = 'PowerQueryTemplate.pqt'
PS C:\Users\a134363> Get-AzDataLakeGen2ItemContent -Context $ctx -FileSystem $workspaceName -Path $itemPath -Destination $downloadFilePath
Error Msg:
Get-AzDataLakeGen2ItemContent : Service request failed.
Status: 400 (BadRequest)
ErrorCode: IncomingOperationUntrusted
Headers:
x-ms-error-code: IncomingOperationUntrusted
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: REDACTED
Access-Control-Allow-Methods: REDACTED
Access-Control-Expose-Headers: REDACTED
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-root-activity-id: REDACTED
Date: Tue, 30 Jul 2024 16:53:12 GMT
Server: Microsoft-HTTPAPI/2.0
Content-Length: 0
At line:1 char:1

Get-AzDataLakeGen2ItemContent -Context $ctx -FileSystem $workspaceNam ...

  + CategoryInfo          : CloseError: (:) [Get-AzDataLakeGen2ItemContent], RequestFailedException
  + FullyQualifiedErrorId : RequestFailedException,Microsoft.WindowsAzure.Commands.Storage.Blob.Cmdlet.GetAzDataLakeGen2ItemContentCommand

Expected behavior
The PS script should download a DataLake file called 'PowerQueryTemplate.pqt'

Actual behavior
Instead it is throwing the below errors
Get-AzDataLakeGen2ItemContent : Service request failed.
Status: 400 (BadRequest)
ErrorCode: IncomingOperationUntrusted
Headers:
x-ms-error-code: IncomingOperationUntrusted
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: REDACTED
Access-Control-Allow-Methods: REDACTED
Access-Control-Expose-Headers: REDACTED
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-root-activity-id: REDACTED
Date: Tue, 30 Jul 2024 16:53:12 GMT
Server: Microsoft-HTTPAPI/2.0
Content-Length: 0
At line:1 char:1
+ Get-AzDataLakeGen2ItemContent -Context $ctx -FileSystem $workspaceNam ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Get-AzDataLakeGen2ItemContent], RequestFailedException
    + FullyQualifiedErrorId : RequestFailedException,Microsoft.WindowsAzure.Commands.Storage.Blob.Cmdlet.GetAzDataLakeGen2ItemContentCommand

Error details
Get-AzDataLakeGen2ItemContent : Service request failed.
Status: 400 (BadRequest)
ErrorCode: IncomingOperationUntrusted
Headers:
x-ms-error-code: IncomingOperationUntrusted
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: REDACTED
Access-Control-Allow-Methods: REDACTED
Access-Control-Expose-Headers: REDACTED
Strict-Transport-Security: REDACTED
X-Content-Type-Options: REDACTED
x-ms-root-activity-id: REDACTED
Date: Tue, 30 Jul 2024 16:53:12 GMT
Server: Microsoft-HTTPAPI/2.0
Content-Length: 0
At line:1 char:1
+ Get-AzDataLakeGen2ItemContent -Context $ctx -FileSystem $workspaceNam ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : CloseError: (:) [Get-AzDataLakeGen2ItemContent], RequestFailedException
    + FullyQualifiedErrorId : RequestFailedException,Microsoft.WindowsAzure.Commands.Storage.Blob.Cmdlet.GetAzDataLakeGen2ItemContentCommand

Environment data
Major  Minor  Build  Revision
-----  -----  -----  --------
5      1      19041  4648

Visuals
No response

When you created this issue, the template showed the following:
"
For Windows PowerShell 5.1 issues, suggestions, or feature requests please use the Feedback Hub app
This repository is ONLY for PowerShell Core 6 and PowerShell 7+ issues.
"
At the end of the day, whether reporting an issue (that isn't a feature request) in this repository is appropriate comes down to:

Whether the observed, unexpected behavior is based on code maintained in this repository ...

See #23981 for how to determine that.

... and is presumed to be a defect (note that this isn't a support forum - see below)
... and manifests in a PowerShell 7 version that is either in development or still supported - see the official support lifecycle and policy.

If you need support,  please do not post here and instead ask the community for support:

Slack and Discord Community Chat - interactive chat with other PowerShell enthusiasts. Both Slack and Discord are bridged via a bot and can seamlessly talk to each other.

StackOverflow.com and PowerShell.org Forum - search or post new general PowerShell usage questions

This is an issue with AzPowerShell and should be raised in their repo and not in here & as such I am closing this as Resolution-External

authors: kilasuit mellieb mklement0


text:
Remoting host callbacks incompatible between PowerShell 5.1 and 6.0

This is a remoting incompatibility introduced in PowerShell 6.0.  Remoting supports host callbacks to the client and the callback information includes type information and values for passed parameter arguments.  For example a PromptForChoice callback passes a ChoiceDescription type argument, which includes fields "label" and "message".  But PowerShell 6.0 changed the field names to "_label" and "_message".  When decoding the host callback message these fields names do not exist on the client and the argument decode fails with a null reference exception:(https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/remoting/common/WireDataFormat/RemoteHostEncoder.cs#L95).
We need to go through all supported host callbacks and ensure all types have not modified field names.  There are only a few callbacks supported so this shouldn't be too bad.
Steps to reproduce
PS [PowerShellCore 6.0] > Enter-PSSession -cn localhost -config microsoft.powershell
[localhost (PowerShell 5.1)]: C:\> Install-Module Razzle

Actual behavior
Null reference exception in remote decoder when handling PromptForChoice callback.

Another repro is to simply run the "clear" command, which makes host.UI.RawUI calls.
PS [PowerShellCore 6.0] > Enter-PSSession-cn localhost -config microsoft.powershell
[localhost (PowerShell 5.1)]: C:\> clear

Result: null reference exception


text:
Format-Volume on a newly created partition without assigning a Drive Letter

Steps to reproduce
$disk = Get-Disk -Number 1
$disk | Set-Disk -IsOffline $false -IsReadOnly $false
$disk | Initialize-Disk
$newpart = $disk | New-Partition -UseMaximumSize
$newpart | Format-Volume -FileSystem NTFS -NewFileSystemLabel "Label"

Expected behavior
It should create the volume, sometimes it works (on other servers)

Actual behavior
Format-Volume : Invalid Parameter
Activity ID: {dcc55555-5b20-4fe0-9abf-4d40078f4c36}
At line:1 char:12
+         Format-Volume -FileSystem NTFS -NewFileSystemLabel "Label"
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (StorageWMI:ROOT/Microsoft/...age/MSFT_Volume) [Format-Volume], CimException
    + FullyQualifiedErrorId : StorageWMI 5,Format-Volume

Environment data

> $PSVersionTable
PS 5.1 on Windows Server 2016

The repo is only for PowerShell Core. PowerShell Core does not have a Format-Volume cmdlet, yet.

my bad, sorry. Also, I've just found the solution to the issue: https://social.technet.microsoft.com/Forums/ie/en-US/c3aadbf6-1365-4d6e-bf5e-f84c1417f753/formatvolume-invalidargument-msftvolume?forum=winserverpowershell

$disk | Initialize-Disk -Passthru         @lelloz0


text:
Fix credential scan issues

Fix credential scan issues (One issue missed in #4927)

Verified cred scan is clean during daily packaging build.


text:
Adding yml for Windows builds

PR Summary
As part of improving the build process, the UI build pipeline for Windows Builds was converted to a yml-based pipeline. (everything minus compliance tasks)
Verified on AzureDevOps mirror (pipeline WIP-PowerShellCore-WindowsBuild-Yaml): automated and manual runs.
PR Checklist

[X] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[X] Summarized changes
[X] Change is not breaking
[X] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[X] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[X] Not Applicable
OR
[ ] User-facing Documentation needed

[ ] Issue filed - Issue link:

Testing - New and feature

[X] Not Applicable or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

Fixed CodeFactor issues.

@adityapatwardhan pls look again.


text:
SPManagedMetaDataServiceAppDefault: ContentType properties missing

Details of the scenario you tried and the problem that is occurring
The properties IsContentTypePushdownEnabled and IsNPContentTypeSyndicationEnabled are not implemented right now.
Verbose logs showing the problem
N/A
Suggested solution to the issue
Implement the features. We implemented it as followed.
The DSC configuration that is used to reproduce the issue (as detailed as possible)
# $parentMMD is defined within a foreach
# $parentMMD = $_
Script "MMDCustomSettings$($_.Name)"
{
    GetScript            = {
        $results = Invoke-SPDscCommand -Arguments $using:parentMMD -ScriptBlock {
            $proxy = Get-SPMetadataServiceApplicationProxy -Identity $args[0].ProxyName
            return @{
                CTPushdown    = $proxy.Properties["IsContentTypePushdownEnabled"]
                CTSyndication = $proxy.Properties["IsNPContentTypeSyndicationEnabled"]
            }
        }
        return $results
    }
    SetScript            = {
        Invoke-SPDscCommand -Arguments $using:parentMMD -ScriptBlock {
            $proxy = Get-SPMetadataServiceApplicationProxy -Identity $args[0].ProxyName
            $proxy.Properties["IsContentTypePushdownEnabled"] = $args[0].CTPushdown
            $proxy.Properties["IsNPContentTypeSyndicationEnabled"] = $args[0].CTSyndication
            $proxy.Update()
        }
    }
    TestScript           = {
        $results = Invoke-SPDscCommand -Arguments $using:parentMMD -ScriptBlock {
            $proxy = Get-SPMetadataServiceApplicationProxy -Identity $args[0].ProxyName
            return $($proxy.Properties["IsContentTypePushdownEnabled"] -eq $args[0].CTPushdown -and $proxy.Properties["IsNPContentTypeSyndicationEnabled"] -eq $args[0].CTSyndication)
        }
        return $results
    }
}

The operating system the target node is running
N/A
Version of SharePoint that is used (e.g. SharePoint 2016)
SharePoint 2016
Version and build of PowerShell the target node is running
5.1
Version of the DSC module that was used ('dev' if using current dev branch)
2.1.0.0

I think these settings are specific to one SPMetadataServiceApplicationProxy. To reflect these additions these changes should be made to the SPManagedMetadataServiceApp Resource.

@andikrueger is right, this needs to be implemented in SPManagedMetadataServiceApp instead. Marked it as Enhancement, so someone can pick this up

I'm on it.

All yours @andikrueger

authors: HeKr09 andikrueger ykuijs

repo: PowerShell/SharePointDsc


text:
Make xPSDesiredStateConfiguration a High Quality Resource Module

xPSDesiredStateConfiguration has been chosen as one of the two modules in the DSC Resource Kit to be updated to an experimental High Quality Resource Module. 'High Quality' here means that you would be willing to use this module in production.
Our current plan to update this module is available here.
We would love to hear feedback about what you think makes a resource module 'High Quality'.

For start, high quality for me is high performance which means using best practices of PowerShell programming to achieve performance. This means when you write your code, think of someone using a DSC script that has 200 registry key changes, 200 files, 200 user  creation etc and then see how your code reacts to such an amount of items. That is why I initially asked the swap to Switch statements instead of IF. And its not just in the MSFT_xRegistryResoure but rather cross the board. Thanks for putting the effort into making this more production friendly !

@ArieHein I agree that the resources should all be scalable and perform as best they can.
We can add performance tests for each resource to make sure they complete within a reasonable amount of time.
We could also add some scalability tests that wouldn't be able to run on each pull request Appveyor run but that perhaps would run more intermittently to test that the resources can handle large scripts.
I'll look at adding these tests to the plan.

@kwirkykat I wonder if it is worth to put any effort into fixing PSSA issues for xFileUpload (a composite resource) and xRemoteFile if the PowerShell team is going to integrate the functionality into the File resource as per the HQRM plan.

@Dan1el42 You're right. There's not much point in updating these resources right now when they aren't going into the HQRM anyway.

Hi @kwirkykat - as I'm working on issues #210, #212, #213 for xServiceResource, I'm actually bringing it up to HQRM at the same time. I'm hoping to submit this tonight or tomorrow- the unit tests are taking a while (trying to get 90% coverage).

@PlagueHO Thanks! :+1:

authors: ArieHein Dan1el42 PlagueHO kwirkykat

repo: PowerShell/xPSDesiredStateConfiguration

license: mit


text:
update error catch and Get return

In version 1, if the copy failed during Set the error was not properly caught and displayed.  Also updating Get so that properties are displayed based on input.  In most cases, I would not use input as what should be returned by Get, but after working with this resource I realize that is the only way to report on which parameters are being passed to the command.

That makes sense.  Only for Ensure, correct?  Otherwise the details of the configuration are not stored anywhere and the original input is actually very important to know.

correct, I think it's fine to display original input  as well if that's something user may find useful.

It is required that you provide adequate test coverage for the code you change. Contribution Guidelines -Adding test coverage for DSC resources  Please work with us to come up with a plan to cover this code.

It is required that you provide adequate test coverage for the code you change. Contribution Guidelines -Adding test coverage for DSC resources  Please work with us to come up with a plan to cover this code.

Please resolve merge conflicts.  For more information see GitHowTo - 30. Resolving Conflicts

If there is no update of the pull request within 7 days, we will close the pull request.  After that, if you have an update, feel free to reopen the pull request.

Closing because the pull request has not been updated for feedback given for 21 days.  Once you update the code, please feel free to reopen the pull request.  Thanks, Travis.

authors: KarolKaczmarek TravisEz13 mgreenegit

repo: PowerShell/xRobocopy


text:
Add xSPAppCatalog resource

The xSPAppCatalog resource will allow setting of the app catalog site collection for a given web application. It should be structured as follows:
xSPAppCatalog MainAppCatalog
{
WebApp = "https://content.sharepoint.contoso.com"
AppCatalogUrl = "https://appstore.sharepoint.contoso.com"
}

@camiloborges Tagging you here to see this one with your other app work mate, you think this fits with the other bits you are touching?

This was merged to dev in PR #133 - closing this issue

repo: PowerShell/xSharePoint


text:
Remove space between vcs sections

Apologies if this is documented somewhere and I simply couldn't find it, but I'm wondering if there's a straightforward way to remove the spacing between the branch name and the various vcs icons for untracked / unstaged / staged status.
I'm hoping that instead of master + ! ? ⇣1⇡1, I could have master+!? ⇣1⇡1.  In a perfect world, I'd like to keep a space between untracked/unstaged/staged icons and the ahead/behind icons and count.
Thanks for your help!

You can do it like this:
POWERLEVEL9K_VCS_UNTRACKED_ICON=$'%{\b?%}'
POWERLEVEL9K_VCS_UNSTAGED_ICON=$'%{\b!%}'
POWERLEVEL9K_VCS_STAGED_ICON=$'%{\b+%}'

I used this hack some time back. It does cause issues in some corner cases though, so I no longer use it.

That seems to work great, thank you!! What sort of issues does it cause?

That seems to work great, thank you!! What sort of issues does it cause?

It breaks prompt if the symbol (such as !, ? or +) is supposed be printed at the last column on the terminal line. This can happen when vcs segment is put in right prompt, or when left prompt overflows to the next line. These conditions are super rare, and even when they do happen, your zsh will still be usable.

Awesome, that's totally good enough for me then. Thanks much! 💯

By the way, is this the config you are using? https://github.com/heylookltsme/dotfiles/blob/master/.zshrc

It was; it's super out of date now. I got a new computer recently and it looks like a lot needing updating. 🙃

I see that your config is using powerlevel10k rather than powerlevel9k. It's an independent theme, so please file issues and post questions in the future at https://github.com/romkatv/powerlevel10k/.
Powerlevel10k supports custom Git status formatting where you have full control over the content. The new config templates (unlike the old ones, on which your own config is based) allow for relatively straightforward Git status format customization. Here's how you can achieve the format you are after.

Update powerlevel10k to the latest version.
Restart zsh.
Type p10k configure to generate a new config.
Open ~/.p10k.zsh and search for my_git_formatter. This function is responsible for building Git prompt segment from VCS_STATUS_* parameters set by gitstatus plugin. You'll see the following snippet:

# ⇣42 if behind the remote.
(( VCS_STATUS_COMMITS_BEHIND )) && res+=" ${clean}⇣${VCS_STATUS_COMMITS_BEHIND}"
# ⇡42 if ahead of the remote; no leading space if also behind the remote: ⇣42⇡42.
(( VCS_STATUS_COMMITS_AHEAD && !VCS_STATUS_COMMITS_BEHIND )) && res+=" "
(( VCS_STATUS_COMMITS_AHEAD  )) && res+="${clean}⇡${VCS_STATUS_COMMITS_AHEAD}"
# *42 if have stashes.
(( VCS_STATUS_STASHES        )) && res+=" ${clean}*${VCS_STATUS_STASHES}"
# 'merge' if the repo is in an unusual state.
[[ -n $VCS_STATUS_ACTION     ]] && res+=" ${conflicted}${VCS_STATUS_ACTION}"
# ~42 if have merge conflicts.
(( VCS_STATUS_NUM_CONFLICTED )) && res+=" ${conflicted}~${VCS_STATUS_NUM_CONFLICTED}"
# +42 if have staged changes.
(( VCS_STATUS_NUM_STAGED     )) && res+=" ${modified}+${VCS_STATUS_NUM_STAGED}"
# !42 if have unstaged changes.
(( VCS_STATUS_NUM_UNSTAGED   )) && res+=" ${modified}!${VCS_STATUS_NUM_UNSTAGED}"
# ?42 if have untracked files. It's really a question mark, your font isn't broken.
# See POWERLEVEL9K_VCS_UNTRACKED_ICON above if you want to use a different icon.
# Remove the next line if you don't want to see untracked files at all.
(( VCS_STATUS_NUM_UNTRACKED  )) && res+=" ${untracked}${POWERLEVEL9K_VCS_UNTRACKED_ICON}${VCS_STATUS_NUM_UNTRACKED}"

Replace it with this:

# * if have stashes.
(( VCS_STATUS_STASHES        )) && res+="${clean}*"
# ~ if have merge conflicts.
(( VCS_STATUS_NUM_CONFLICTED )) && res+="${conflicted}~"
# + if have staged changes.
(( VCS_STATUS_NUM_STAGED     )) && res+="${modified}+"
# ! if have unstaged changes.
(( VCS_STATUS_NUM_UNSTAGED   )) && res+="${modified}!"
# ? if have untracked files. It's really a question mark, your font isn't broken.
# See POWERLEVEL9K_VCS_UNTRACKED_ICON above if you want to use a different icon.
# Remove the next line if you don't want to see untracked files at all.
(( VCS_STATUS_NUM_UNTRACKED  )) && res+="${untracked}${POWERLEVEL9K_VCS_UNTRACKED_ICON}"
# ⇣42 if behind the remote.
(( VCS_STATUS_COMMITS_BEHIND )) && res+=" ${clean}⇣${VCS_STATUS_COMMITS_BEHIND}"
# ⇡42 if ahead of the remote; no leading space if also behind the remote: ⇣42⇡42.
(( VCS_STATUS_COMMITS_AHEAD && !VCS_STATUS_COMMITS_BEHIND )) && res+=" "
(( VCS_STATUS_COMMITS_AHEAD  )) && res+="${clean}⇡${VCS_STATUS_COMMITS_AHEAD}"
# 'merge' if the repo is in an unusual state.
[[ -n $VCS_STATUS_ACTION     ]] && res+=" ${conflicted}${VCS_STATUS_ACTION}"

Hopefully it's clear from the comments what's going on, so you can tune the format to your liking.
If something doesn't work quite the way you like, or if you have any questions, please open an issue at https://github.com/romkatv/powerlevel10k/.

authors: heylookltsme romkatv


text:
Шаги для установки фильтров на список не работают для перечислений и для дат

Версия Vanessa Automation 1.2.039.4
Версия платформы 8.3.20
Режим совместимости базы, где запускается Vanessa Automation 8.3.17
Операционная система windows

Если использовать шаги установки фильтров для перечислений, такие как
 И для каждой строки таблицы отбора я устанавливаю отбор в списке
 	| 'Состояние'    | 'Равно' | 'Выполнен' |
 И Я устанавливаю фильтр на список
 	| 'Состояние'    | 'Равно' | 'Выполнен' |

то при выполнении шага будет ошибка, что значение не может быть выбрано.

Выбрать перечисление можно только так
И я нажимаю кнопку выбора у поля с именем "Имя поля"
И я выбираю из списка 'Выполнено'

С этими шагами по установке фильтров связана еще одна ошибка. что нельзя установить ими отбор по дате, так как при установке отбора к полю с типом дата платформа предлагает сначала выбрать тип периода, а потом только указать дату

 И для каждой строки таблицы отбора я устанавливаю отбор в списке
 	| 'Дата'    | 'Равно' | '01.01.2022' |
 И Я устанавливаю фильтр на список
 	| 'Дата'    | 'Равно' | '01.01.2022' |

@akademik1986
Да, думаю можно эти шаги научить работать с перечислениями и датами.

repo: Pr-Mex/vanessa-automation


text:
Добавить возможность использовать для озвучки движок от Yandex

Информация тут:
https://cloud.yandex.ru/docs/speechkit/tts/request

Сделано.


text:
JUnit fails to report results of some tests if used with surefire and parallel option including methods

Example: run mvn test in JUnitParams project with following configuration:
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>2.18.1</version>

                <configuration>
                    <runOrder>filesystem</runOrder>
                    <parallel>classesAndMethods</parallel>
                    <perCoreThreadCount>false</perCoreThreadCount>
                    <threadCount>16</threadCount>
                    <useUnlimitedThreads>false</useUnlimitedThreads>
                    <threadCountSuites>0</threadCountSuites>
                    <threadCountClasses>0</threadCountClasses>
                    <threadCountMethods>0</threadCountMethods>
                    <parallelOptimized>true</parallelOptimized>
                    <includes>
                        <include>**/SubclassTest.java</include>
                        <include>**/Samples_*</include>
                    </includes>
                </configuration>
            </plugin>

This should give total of 44 tests as of today, but often it will give less than that. Contact me for details about research done so far.
Suspicious places:

org.apache.maven.surefire.junitcore.JUnitCoreRunListener#fillTestCountMap
org.apache.maven.surefire.junitcore.ClassesParallelRunListener#checkIfTestSetCanBeReported
org.apache.maven.surefire.junitcore.TestSet#setAllScheduled

Currently following values of surefire "parallel" option should not be used:

"classesAndMethods"
"methods"
"both"

I did some research about this annoying bug.
With an empirical debugging/testing method I fixed the issue by removing the index from the Utils#uniqueMethodId. I found that the index is sometime not consistent during the run.
I suppose the index in the uniqueMethodId have a good reason to be here, but all the unit tests passes without it and my tests passes as well.
I let you try and test my method and review the causes.
Don't hesitate if you have more questions.

@apierzch and @skyghis - Has there been any advance on this issue and line of research?

Sorry @dankirkd, I no longer use JUnitParams. I now use Junit5 with integrated parameterized tests.

authors: apierzch dankirkd skyghis

repo: Pragmatists/JUnitParams


text:
Implement rollback within Update

Closes #42.

Tests are passing but I'm pretty sure there's something wrong with this. Failing transactional squares, maybe?

Good enough. I'll merge and tag as a pre-release.


text:
Document Gotify notifications

I can confirm Gotify works great for me :)
While the exact URL is documented on https://gotify.net/docs/pushmsg, it's not given when you add a new app to Gotify (just the token is), so I figured I'd document the exact URL format in the README too.

Thank you for your contribution!

authors: TheLastProject maietta

repo: PremoWeb/chadburn


text:
Fixed links for ps_banner

See https://github.com/PrestaShop/ps_mainmenu/pull/9

Thanks @aleeks

authors: aleeks maximebiloe


text:
Feature/b3 d continue pot

This extends the continuegrid functionality to be able to read the existing background profile arrays (if available) and use those for collisions.
If profiles are specified in the input namelist, they take precendent and overwrite the existing ones. This allows the direct import of the background plasma from codes able to output all the quantities on a R-Z grid (like Jorek). It also allows flux-label independent profiles to be used if desired, e.g. for SOL simulations.
Note that currently the ion density is not read in from the original file, which should be adressed before merging.

Shouldn't the ability to 'continue' a run only read values from the HDF5 file and not an input namelist?

I think having the option to use profiles controlled by the input namelist adds flexibility and is easy enough to control by having the profile information there or commenting it out. At least in cases where only S and U are included in the continue file, the profile information in the input namelist is necessary. We could have the continue file take precedent over the input profile namelist, but I think the option should be there to change the profiles to whatever is in the namelist.

authors: kudav lazersos

repo: PrincetonUniversity/STELLOPT


text:
When can we drop IE11 support?

Once we can drop IE11, we will be able to depend on CSS variables.
This means we can finally get rid of the whole problem "how do all themes work with all languages?". Themes would just define variables, language definitions would just use these variables.
What do you think?

I'm personally OK w/ dropping IE11 support, but I know projects I work on generally still support it as MSFT is still supporting that browser. Additionally, IE11 still works w/ Windows 10, so MSFT may continue to support it for a while.
This is also definitely a breaking change, so we should release as a 2.0. If we drop IE11 support, we could probably go all-in on ES6 as well, if that helps the code at all.
Just some thoughts. Not really sure where I stand, tbh.

We could maybe support CSS variables and use postcss-custom-properties for rudimentary IE11 support.

I'm wondering if we could start using CSS variables without completely dropping IE11 support. We could use PostCSS or something to add fallbacks, and IE11 would just use those fallbacks. So people on IE11 would still get highlighting, just not customized highlighting. Would that make sense?

Microsoft is retiring IE11 in June 2022.

Are you planning to support it until then?

Given the current progress on v2, I can't blame you for thinking that but no :)

Technically, dropping IE11 support is a breaking change, so we really should support it until then, unfortunately.

Unless I misunderstood the comment/question. To rephrase, v1 should support IE11. v2 was never intended to. So really, we'll support IE11 until whenever v2 gets out. Or at least, that's what I think we should do.

To rephrase, v1 should support IE11. v2 was never intended to.

Yup, that's pretty much it. We'll support IE11 for the whole of v1.x and then drop it in v2.0.0.

"users stop using it" is a date that is not tightly correlated to "a company stops supporting it".

Yup, agreed too. Whoever needs IE11 support can just stay on v1.

IE11 is dropped in v2.

I don't think it's a problem to delete IE11 in V2, but I recently updated Prism.js and found that V1 can't be used in IE11. Check the error and find that it's a RexExp problem. In V1.25.0, IE11 still OK, but V1.26.0 will report an error, so is it not supported in advance ? 😭

I don't think it's a problem to delete IE11 in V2, but I recently updated Prism.js and found that V1 can't be used in IE11. Check the error and find that it's a RegExp problem. In V1.25.0, IE11 still OK, but V1.26.0 will report an error, so is it not supported now ? 😭

Can you please file this as a new bug? This is not intentional.

file this as a new bug : https://github.com/PrismJS/prism/issues/3558

authors: ExE-Boss LeaVerou RunDevelopment joshgoebel ljharb mAAdhaTTah xjArea

repo: PrismJS/prism


text:
New UI and 2 of my strategies

Somebody asked for this in the discord, not sure who.

Did you run black?


text:
Adds .then { } API

See the discussion in #176.

🎆 👍
Perhaps an enqueue(on: ProcedureQueue = ProcedureQueue()) for a Sequence of Operation? It would allow:
procedure.then { procedure2 }.then { procedure3 }.enqueue()

Though that could perhaps be for later.

authors: danthorpe jshier

repo: ProcedureKit/ProcedureKit


text:
500 No value present при создании пользователя

@iseeyouwatching посмотришь что сломалось?
Запрос на создание пользователя
curl -X 'POST' \
  'http://localhost:8080/api/users' \
  -H 'accept: */*' \
  -H 'Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJVc2VyIGRldGFpbHMiLCJwaG9uZSI6Iis3OTk5OTk5OTk5OSIsInJvbGVzIjpbIlJPTEVfU0NIT09MX1JFUFJFU0VOVEFUSVZFIiwiUk9MRV9BRE1JTiJdLCJpc3MiOiJoaXRzLWludGVybnMtYXV0aC1iYWNrZW5kIiwiZnVsbE5hbWUiOiJBZG1pbkFkbWluQWRtaW4iLCJpZCI6ImMyOWFlODcyLTdjMTEtNGNlNy04MjczLTQ5ZDEwM2ZjMWI4MiIsImV4cCI6MTc0ODAwNDg0NSwiaWF0IjoxNzE2NDY4ODQ1LCJlbWFpbCI6ImFkbWluQGdtYWlsLmNvbSJ9.DxONZdjUecH01ONJUz9o0QgIggjhFEFFD6evQiOT-0M' \
  -H 'Content-Type: application/json' \
  -d '{
  "firstName": "string",
  "lastName": "string",
  "patronymic": "string",
  "email": "string",
  "phone": "string",
  "password": "string",
  "sex": "MALE",
  "groupId": "3fa85f64-5717-4562-b3fc-2c963f66afa6",
  "isStudent": true,
  "isSchoolRepresentative": true,
  "isAdmin": true
}'

В ответе 500
{
  "messages": [
    "Непредвиденная внутренняя ошибка сервера"
  ]
}

2024-05-23 21:07:48 2024-05-23 14:07:48.389 ERROR 1 --- [nio-8080-exec-3] r.h.a.ExceptionHandlerController         : Возникла ошибка при запросе на URL: uri=/api/users;client=172.18.0.1;user=ru.hits.authservice.security.JwtUserData@32e14ce6
2024-05-23 21:07:48 2024-05-23 14:07:48.390 ERROR 1 --- [nio-8080-exec-3] r.h.a.ExceptionHandlerController         : No value present
2024-05-23 21:07:48
2024-05-23 21:07:48 java.util.NoSuchElementException: No value present
2024-05-23 21:07:48     at java.base/java.util.Optional.get(Optional.java:148) ~[na:na]
2024-05-23 21:07:48     at ru.hits.authservice.service.UserService.createUser(UserService.java:95) ~[classes!/:0.0.1-SNAPSHOT]
2024-05-23 21:07:48     at ru.hits.authservice.service.UserService$$FastClassBySpringCGLIB$$420c294d.invoke(<generated>) ~[classes!/:0.0.1-SNAPSHOT]
2024-05-23 21:07:48     at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:218) ~[spring-core-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:793) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:123) ~[spring-tx-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:388) ~[spring-tx-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:119) ~[spring-tx-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:186) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.proceed(CglibAopProxy.java:763) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:708) ~[spring-aop-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at ru.hits.authservice.service.UserService$$EnhancerBySpringCGLIB$$984a6a9c.createUser(<generated>) ~[classes!/:0.0.1-SNAPSHOT]
2024-05-23 21:07:48     at ru.hits.authservice.controller.UserController.createUser(UserController.java:53) ~[classes!/:0.0.1-SNAPSHOT]
2024-05-23 21:07:48     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
2024-05-23 21:07:48     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
2024-05-23 21:07:48     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
2024-05-23 21:07:48     at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
2024-05-23 21:07:48     at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:150) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:117) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:895) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:808) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:87) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:1072) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:965) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:1006) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:909) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at javax.servlet.http.HttpServlet.service(HttpServlet.java:555) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:883) ~[spring-webmvc-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at javax.servlet.http.HttpServlet.service(HttpServlet.java:623) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:209) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) ~[tomcat-embed-websocket-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:111) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:337) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:115) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:81) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:122) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:116) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:126) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:81) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:109) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:149) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at ru.hits.authservice.security.JWTFilter.doFilterInternal(JWTFilter.java:81) ~[classes!/:0.0.1-SNAPSHOT]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:103) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.authentication.logout.LogoutFilter.doFilter(LogoutFilter.java:89) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.web.filter.CorsFilter.doFilterInternal(CorsFilter.java:91) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.header.HeaderWriterFilter.doHeadersAfter(HeaderWriterFilter.java:90) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.header.HeaderWriterFilter.doFilterInternal(HeaderWriterFilter.java:75) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:112) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.context.SecurityContextPersistenceFilter.doFilter(SecurityContextPersistenceFilter.java:82) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter.doFilterInternal(WebAsyncManagerIntegrationFilter.java:55) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.session.DisableEncodeUrlFilter.doFilterInternal(DisableEncodeUrlFilter.java:42) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:346) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy.doFilterInternal(FilterChainProxy.java:221) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.security.web.FilterChainProxy.doFilter(FilterChainProxy.java:186) ~[spring-security-web-5.7.8.jar!/:5.7.8]
2024-05-23 21:07:48     at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:354) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:267) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:201) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:117) ~[spring-web-5.3.27.jar!/:5.3.27]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:178) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:153) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:167) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:343) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:389) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:926) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) ~[tomcat-embed-core-9.0.74.jar!/:na]
2024-05-23 21:07:48     at java.base/java.lang.Thread.run(Thread.java:829) ~[na:na]

Видимо ошибка из-за того что нет группы, должно 404 кидать

ладно, видимо будем решать по другому


text:
[Documentation] Tests for Axios

Files are here
Pre- work:

highlight code snippet and type into chat "Explain this test to me"
general question "why do we use jest framework", "what are advantages of jest over chai"

Tasks for completion:

[ ] addition to inline comments: highlight individual tests and copilot prompt "refactor to be more readable with inline comments"
[ ] addition to wiki: highlight all of the file and ask for a wiki summary for all test codes and add it here https://github.com/ProgramEquity/amplify/wiki/Setting-up-Axios

I just assigned myself, look forward to working on this issue!

@shangguanwang Hi! Is it okay to work on this issue with you?

authors: Alex-is-Gonzalez kalahasv shangguanwang

repo: ProgramEquity/amplify


text:
Style layer button

Completed https://github.com/Project-OSRM/osrm-frontend-v2/commit/bd1b210d3359430f0bb10e97f6d879ffccaceab2


text:
Formatting & Cosmetic changes to Markdown.

Cleaning up Markdown to better understand workflow.

@Project-Quantum is this too small? If so, let me work out some for fixes then and let me know.

repo: Project-Quantum/Quantum-Starter-Kit


text:
Fardina

merge req

Cool beans


text:
Missing order transaction details

The details returned from the streaming API when monitoring for onItemListedEvents does not return any information that can be used to place a buy order.  There are is no order hash included or any of the other details that can be used to directly locate the corresponding order.

Yep.
Include order details in streaming API would be much better. Right now, we have to loop rest API to get order details, which makes stream API not that useful.

This has nothing to do with the Missing Events issue.
This is a request to include the order dtails in the onItemListedEvents stream.  Please re-open this ticket.

@itsthedoom

authors: ethangao steddyman

repo: ProjectOpenSea/stream-js


text:
Try HashRouter instead of BrowserRouter

Entering the Url like "michaelprommer/about" doesn't work and shows 404
Try following answer
https://stackoverflow.com/questions/71984401/react-router-not-working-with-github-pages/71985764#71985764

react-snap doesn't seem to work with react v18+
looking into next.js

repo: Prommerbua/Portfolio-Website


text:
#108, #110, #111 | Ziyang | Refactor the service using RESTX and setup Swagger

Closes #108.
Closes #110.
Closes #111.
API Docs Page Screenshot

IBM Cloud toolchain: Delivery Pipeline deployed promotions to prod, including commit 038f426b370e848d74d3b6cf3a72395e8fe30bd4

repo: PromoSquad/promotions


text:
Update "titlePlanAccurate" to be "yesNoDetailIfNo"

The field/propertyPack/additionalLegalInformation/aboutTheProperty/titlePlanAccurate should require additional details if its yesNo property is "No".

Thanks @jmsfwk happy to merge this but first interested in your thoughts on the right version management strategy for this schema and the associated Open API spec. Do you have any thoughts on tags, releases, tools like https://github.com/wikimedia/jsonschema-tools?

Restructured the folder so added your change manually in the v1.0.1 commit, thanks! 👍

authors: edmolyneux jmsfwk


text:
Text PSM -> mzIdentML transformation tool used by the CPTAC CDAP pipeline

I can maintain this tool on a fork indefinitely, but it would be nice to bring it into the fold. This program reads a (very) verbose, but easy to generate, text stream representing the PSM data from the CPTAC CDAP DDA peptide identification analysis pipeline, and represents it as mzIdentML.
The Python based parsers live in the cptac3-cdap/cptac-mzid repository.
This code has worked, essentially unmodified, for many years, only requiring re-compilation to pick up new terms from the PSI-MS and PSI-MOD ontologies.
Let me know if you think this is suitable for inclusion in the main repository.
I will attach a small example of the text-based PSM stream this tool consumes and the resulting mzIdentML file.
example.txt.gz
example.mzid.gz
Cheers!

Great, thanks for the careful review. I'll work on the various things you've identified. I haven't used C++ actively for many years, probably haven't kept up with current best practices. Thanks for the pointers.

@chambm OK, used explicit std:: throughout, got rid of using namespace std; declared namspace pwiz::examples for my classes in TextPSMReader.hpp and used in TextPSMReader.cpp and textpsm2mzid.cpp; replaced all runtime lookups of hardcoded MS CV terms with CV enums; replaced irrelevant/misleading filename string with the empty string.
I think this addresses all of your concerns. Let me know if you find more...
Cheers!

repo: ProteoWizard/pwiz


text:
Replace "" with "" in resx files

Use "<value></value>" instead of "<value />" for empty values in .resx files

Will Visual Studio change these? How did they get to be <value/> in the first place?

Will Visual Studio change these? How did they get to be <value/> in the first place?

They got changed to <value/> by a tool that I wrote in PR #3035. We are pretty sure that Visual Studio always writes them out as  <value></value> so I changed them back to the way they were before.

authors: chambm nickshulman