Interactive Rebase Editor - how to turn it off?

Please, could you kindly help me to turn off the Interactive Rebase Editor? I couldn't find this option in settings. Sorry for disturbing you. Many thanks in advance ^___^

I immediately uninstalled GitLens when this was added. Please make it optional!

Really sorry for the inconvenience. You can turn it off by adding the following to you settings.json
	"workbench.editorAssociations": [
		{
			"viewType": "default",
			"filenamePattern": "git-rebase-todo"
		}
	],

I will add a feature to more easily turn it off, which I thought would be really easy but instead is going to be quite tricky without vscode changes.

Ah great - thanks for the config snippet!

Would it be possible to add a link/icon inside the interactive rebase editor that could jump back to the text version of git-rebase-todo on-click?
Similar to the vscode icon to jump to the settings.json text file from inside the Settings GUI editor:

Technically you can do this today with the vscode Reopen With command, but the problem is that vscode closes the document and then re-opens it. Which breaks the wait behavior, because once the document is closed git will start the rebase. I'm hoping we can get that fixed in vscode so that this could work properly.

I wouldn't be angrily tweeting nasty things if it'd had an off switch :(
https://twitter.com/maxoverdrive/status/1328520498548932615

For those that want to turn it off I will be adding an easy to toggle setting soon. But I would love any feedback as to what you don't like about it -- as I would love to improve it (even if you would ultimately still turn it off).

@eamodio - I turned it off because I frequently use interactive rebase and am used to my current workflow. Honestly, I might like it a lot if I was new to interactive rebasing, but as someone who already uses it a lot these things threw me off:

the ordering is backwards from what I'm used to
weirdly the spacing threw me off too, probably just cause I'm used to reading the text list, but them being farther apart than I expected was uncomfortable and felt hard to read
clicking buttons is a lot slower than just using the keyboard to move lines around to where I want them and multi-edit a bunch of commits to fix up at once
I couldn't drop the first commit, and I wanted to the first time I tried a rebase and this editor popped up (I often do something like git rebase -i master to just get my branch commits, and would like to be able modify all of them however I want)

Thank you so much for the awesome tool! I'm glad I can turn this off rather than disabling the plugin, which I really like.

I've exactly same feedback as @MandaBrown haha 👌💯
Thanks for this great plugin @eamodio !

Really sorry for the inconvenience. You can turn it off by adding the following to your settings.json
	"workbench.editorAssociations": [
		{
			"viewType": "default",
			"filenamePattern": "git-rebase-todo"
		}
	],

I will add a feature to more easily turn it off, which I thought would be really easy but instead is going to be quite tricky without vscode changes.

Can you consider having this feature be disabled by default?  That way, it won't surprise people when they first install the extension.

@MandaBrown Thanks for the feedback.

the ordering is backwards from what I'm used to

Agree, it took me a bit to get used to it this way, but imo this order is more natural/expected (if you weren't corrupted by the existing behavior). Would an option to switch the order make it better?

weirdly the spacing threw me off too, probably just cause I'm used to reading the text list, but them being farther apart than I expected was uncomfortable and felt hard to read

Hrm, I look into tightening it up a bit

clicking buttons is a lot slower than just using the keyboard to move lines around to where I want them and multi-edit a bunch of commits to fix up at once

The new UI, should be fully keyboard accessible -- just using the arrow keys to move around and the others listed:

I don't have any specific keyboard shortcut for the Start Rebase button, but maybe I should add something like Ctrl+Enter. Although since this experience is just a facade on top of the normal git-rebase-todo document, can still use the normal vscode save shortcut to save the changes you made, and the close the tab (again with the normal vscode shortcut)

I couldn't drop the first commit, and I wanted to the first time I tried a rebase and this editor popped up (I often do something like git rebase -i master to just get my branch commits, and would like to be able modify all of them however I want)

There should be no difference in the commits that can be affected as part of the rebase. I think the confusion, is that in the rebase UI, I show you a "static" view of the commit that your rebase will sit on top of for added context.

@awshelley-beckman I don't have any plans to make it off by default -- as it would be completely undiscoverable. But I am planning to add a very simple/clear opt-out option (right in the UI) to go back to the default.

@eamodio I will admit, I was so completely and immediately thrown off by the sudden change, that I assumed there was no keyboard support and immediately looked for a way to disable it. That being said, unless I'm missing something, my assumption was correct for the one bit of keyboard support I actually care about.
As far as I can see, there's no way to set actions for multiple commits at once, and that's what I'd want before re-enabling the interactive editor. Frequently, the reason that I'm rebasing is that I want to squash a large number of consecutive commits (generally small fixups). If it were possible to e.g. hold shift to select multiple commits, then press act on all of them (e.g. f or alt↓), the new editor would be an improvement for me instead of a hinderance.
There are definitely some things I like about the new interface. It prevents you from accidentally making invalid or useless edits (like misspelling command names, or uselessly modifying commit messages), and the abort button is useful too.
I also agree with the idea that the buttons (both Continue and Abort) should have keyboard shortcuts, despite the fact (as you noted) that you can just save and close the tab to "save". When I'm working in text file mode, my mental model is "this is a file, and it will be processed when I close it", so saving/closing is natural. But when presented with a UI, even though the UI is just a facade over modifying the file, "saving and closing" isn't the obvious thing to do. Instead I want to press the buttons, but then if those buttons don't have key shortcuts, the UI becomes frustrating.

@Spacerat Thank you for the feedback.
I will definitely add shortcut keys for the buttons -- ctrl+enter for start, and not sure on abort yet -- esc might be too easy to hit accidentally? Any thoughts on either of those?
As for multi-select, that had come up and I put off implementing it -- but it sound like it would be useful. At the same time, today while you can't do a shift select, you can just use arrow-down and then s to squash and just keep repeating that. I know it isn't the same, but 😄

Ah, cool, I also jumped away too soon to notice that there was keyboard support, but just like @Spacerat I often multi-select and edit that way. The suggestion there would help me, too.
Re: the spacing and order, it's probably more just what I'm used to than that this isn't better, but sometimes I do wind up with a pretty long list of commits.
Re: the static commit, I was pretty sure that the 'static' commit that was showing was the first commit that I wanted to edit in my rebase and not the commit prior. I'll see if I can repro later; I might have also just been thrown off by the new UI and confused. :)
You might be right about the order, although I would personally love an option to reverse them. When I'm doing an interactive rebase, I'm often trying to make sure my commits tell the story I want them to, so reading them oldest first makes a lot of sense in my mental model.

@MandaBrown Thanks again for the feedback! And definitely let me know on the "static" commit, because if there is an issue there, I definitely want to get that fixed.
I will definitely look to add a toggle to change the sort order (should be easy enough).

esc might be too easy to hit accidentally? Any thoughts on either of those?

Yeah I agree, you'd want to be careful there. As a mac user, I'd suggest cmd-A because I'm used to dialog button shortcuts which are "command + [first letter of dialog action]". Also for mac I think cmd-enter would be more intuitive than ctrl-enter. If the shortcuts are editable along with other vscode shortcuts, that would probably help too.

OK, will try Ctrl|Cmd+R (don't want to use S because it will conflict with save) and Ctrl|Cmd+Enter for rebase, Ctrl|Cmd+A for abort. Ctrl|Cmd will depend on mac vs windows/linux.
I don't think I want to go down the configurable shortcut key path, unless I have to (would mean a lot more complexity)

And definitely let me know on the "static" commit, because if there is an issue there, I definitely want to get that fixed.

Must have just been me being confused, so sorry about that! Tried to repro and it looks right, the static commit is exactly what I would have expected.

The new interactive rebase looks exciting, but having it enabled, without my knowledge, made it frightening the first time it popped up. Thank you for allowing it to be turned off. I'll try it out when I'm ready, not when GitLens tells me it's time.

I'm really excited about the new GUI for interactive rebase, but I have the next issue:
The merge commits aren't displayed on this new GUI.

I really appreciate the work you've done on GitLens. @eamodio, this project is fantastic! Anything below that is critical is meant to be purely informative.
I really do think that this being on by default is a bad effect. It was extremely jarring and frustrating. I am in that view dozens of times a day and a GUI is absolutely slower. Yes, an option to disable right inside the view would be good, but this is the one thing (that I have noticed) where GitLens is interjecting itself into someone's workflow without their explicit request.
I don't know what is possible within vs-code, but would you consider instead a pop-up message the first time someone does a rebase? That message could just tell the user that there is an option they can enable for a GUI. Additionally, I'd see no problem with defaulting to this new GUI when an interactive rebase is invoked from within a GitLens sidebar.
It also seems like some of the interface suggestions in comments above are ultimately trying to get this view to behave more like the simple text buffer presented by Git. I personally think that you've nailed a GUI which is actually more intuitive for a person who is unfamiliar with that text version. So in my opinion, you'd be spinning your wheels to bother with some of these tiny changes. I don't think that a GUI must necessarily reflect the CLI interface it stems from. If it did, what would be the point?
Having said all that, I am going to go make a donation to the project, because I absolutely to appreciate it!

@DanielGnzlzVll Can you open a new issue for that, and if possible provide an example repo that I can try this out with?

@eamodio sure, https://github.com/eamodio/vscode-gitlens/issues/1189

Here is a screenshot of changes coming to the rebase editor -- any thoughts?

I was very surprised by this change. I thought it was some new feature from vscode for a minute because it didn't say anything about it being gitlens.
I wouldn't have minded except I was trying to rebase a fixup commit and this had no option for it and was not auto-detecting it which I thought was very weird.
Will you be adding support for fixup? I use it constantly.

The thing about this that made me mad is that the behavior of something I have done and used for years (interactive rebasing by editing a text file) has suddenly changed without warning (apparently because of GitLens auto-updating), and there is no obvious way to turn it off.
It does seem kind of cool, but I think it should be an option that the user needs to explicitly enable, or at least have an easy way to disable it.
The backwards ordering threw me off too. It is like someone unexpectedly snuck into my garage last night and decided it would be a good idea to switch around my gas and brake pedals without my permission.

Closing this as GitLens 11.0.2 adds multiple options to enable/disable the new rebase UI. Please open new issues for any other issues that arise. And thank you all for your feedback!

Technically you can do this today with the vscode Reopen With command, but the problem is that vscode closes the document and then re-opens it. Which breaks the wait behavior, because once the document is closed git will start the rebase. I'm hoping we can get that fixed in vscode so that this could work properly.

What I found to work:

Duplicate editor tab (via icon in top right corner).
Perform "Reopen with..." on that 2nd tab while keeping 1st one open.

This way, you can edit text file only when you want to, without aborting the rebase.

Just be careful with that method - while it should work there are a few vscode bugs when you have both editors open at the same time.

Just be careful with that method - while it should work there are a few vscode bugs when you have both editors open at the same time.

Didn't run into any issues yet, but good to know, thanks. TBH I wouldn't need the text view at all, but one of the common operations during interactive rebase for me is to bulk-delete (or bulk-fixup) a range of commits.
 Maybe GitLens could allow the same?

@RReverser see https://github.com/eamodio/vscode-gitlens/issues/1182 -- feel free to add any specific requirements you'd like to see
But also note, you can currently use the arrow keys and "action" keys to move and set things very quickly -- e.g. press d, then arrow-down, and keep repeating.

#1182 looks good. Yeah, I suppose I could, but especially when rebasing between very different branches, I often end up keeping only 2-3 commits and deleting 10x.

FWIW my reason for turning it off was just that I like using my keyboard to do fast multi-line editing to change the action for each commit. The editor pushed me onto the mouse which made it all a bit slower! Appreciate it may well make things much easier for someone who wasn't used to it though :)

@peternixey The rebase UI is fully keyboard accessible (no need to use the mouse). Was there an issue you ran into with that?

Hi Eric, I didn’t see that there were keyboards shortcuts. I’m not sure that there was any issue with the visual editor but there wasn’t any particular win that I experienced either (since I’m very happy with text) so it just slowed me down a little. I felt I was going to need to do a number of things just to reach parity with what I could already do in text.
However I can see it being really nice for less experienced developers. So maybe it’s just a case of asking if you want it and making it easy to switch it off from the editor itself (ideally). Also as other commenters mentioned I found it peculiar that it ordered commits newest to oldest. Not saying it’s wrong but it wasn’t what I was expecting.
Thanks for all of your great work with GitLens btw - it’s a great piece of kit 🙏🏻


chore: ☂ Migrate BundleHermesCTaskTest.kt to AssertJ

Summary:
Issue: https://github.com/facebook/react-native/issues/45596

Changelog:
[INTERNAL] [CHANGED] - Migrate BundleHermesCTaskTest.kt to AssertJ testing library

Test Plan:
Run ./gradlew -p packages/gradle-plugin test

hello @cortinico 👋 this PR is ready for the review🚀

changes are done @cortinico

solved the issues @cortinico

I didn't know you wanted to delete isEqualTo as well @cortinico

I didn't know you wanted to delete isEqualTo as well @cortinico

@omer-ayhan the isEqualTo assertion on the size is unnecessary because of the containsExactly assertion just above.


[RPC API] data model w/ focus on read API’s: certs, objects

get object
get certificate
client service status/config

@stella3d , @patrickkuo, @lxfind  - what state is this in?

(Also, I'm taking a guess on the priority)

Once JSON-RPC server PR is merged, we will need to work on OpenRPC documentation -- to replace Postman Documentation. Also we will need to refactor/simplify GatewayAPI's response objects to make it easier to be consumed by downstream, current model contains move object bytes and move objects layout etc, which might not be very useful to downstream systems.

Need more specific issues.  Closing this one, too general.


Add conditional_probability_of_being_alive_up_to_time to ParetoNBD

There is an additional predictive capability for the ParetoNBD model that is not included in the legacy Lifetimes library:
https://github.com/CamDavidsonPilon/lifetimes/issues/213

@ColtAllen - Appreciate your help. Grateful. Can the beta release be installed just using pip install btyd?

@ColtAllen - Appreciate your help. Grateful. Can the beta release be installed just using pip install btyd?

Yes; the new release is now available for pip install as v0.1b3.


Remove redundant highp fallback that can trigger infinite loop

Say your shader error was something like Error: ERROR: 0:16: '=' :  cannot convert from 'highp 4-component vector of float' to 'highp 3-component vector of float'(…) (which is emitted by Chrome when setting a vec3 with a vec4)
Since the error contains 'highp' it tries to replace the precision statement and then runs _prepareEffect again, which doesn't resolve the issue, triggering the infinite loop.
I think the best fix immediately is to remove the check completely. Babylon is already trying to resolve highp support issues in '_processPrecision', so this fix shouldn't actually be needed.
In a broader discussion, I think the approach of string searching for complete precision statements isn't the best one, the current approach doesn't account for the variations in whitespace, we could regex search of course but it's arguable this is still fragile
Some other ideas:

If highp isn't supported, prepend #define highp mediump (ensuring it's placed after the #version directive if one exists)
We don't even need to check for highp precision support in js, this would do it:

#ifndef GL_FRAGMENT_PRECISION_HIGH
#define highp mediump
#endif

We could store desired precision as an option in js, this way Babylon can prepend the correct precision statement itself

In any case I think it's important Babylon emits a warning for the developers when it forces a change to the shaders.

I completely agree this is not required anymore (old code powa!!!!)
This is not required because we added highp check in _processPrecision


No matches on won node created when behind proxy

Hint messages are created by the matcher but not added at the wonnode to the need if the wonnode is behind a proxy e.g. test with proxy (?) satsrv06 (int) or satsrv07 (master)

on www.matchat.org matches work however

Message cannot be sent from matcher (satsrv06) to wonnode(satsrv05) behind proxy (satsrv07) => no response within 20 seconds ??
[WARN] [06/23/2016 08:47:57.264] [ClusterSystem-akka.actor.default-dispatcher-6] [akka://ClusterSystem/user/WonNodeControllerActor] Actor encountered error: akka.camel.AkkaCamelException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-fa8c8c72188b-42454-1466670992720-0-28 not received. Exchange[Message: https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u {
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u
a       http://purl.org/webofneeds/message#EnvelopeGraph ;
http://www.w3.org/2004/03/trix/rdfg-1/subGraphOf
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo .
<https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo>
        a       <http://purl.org/webofneeds/message#FromExternal> ;
        <http://purl.org/webofneeds/message#hasContent>
                <https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#content-o6g1> ;
        <http://purl.org/webofneeds/message#hasMessageType>
                <http://purl.org/webofneeds/message#HintMessage> ;
        <http://purl.org/webofneeds/message#hasReceiverNeed>
                <https://satsrv07.researchs... [Body clipped after 1000 chars, total length is 2198]]

23.6.16 08:47:57.265 [ClusterSystem-akka.actor.default-dispatcher-17] INFO  o.a.c.impl.DefaultShutdownStrategy - Starting to graceful shutdown 1 routes (timeout 300 seconds)
[ERROR] [06/23/2016 08:47:57.264] [ClusterSystem-akka.actor.default-dispatcher-17] [akka://ClusterSystem/user/WonNodeControllerActor] The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-fa8c8c72188b-42454-1466670992720-0-28 not received. Exchange[Message: https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u {
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u
a       http://purl.org/webofneeds/message#EnvelopeGraph ;
http://www.w3.org/2004/03/trix/rdfg-1/subGraphOf
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo .
<https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo>
        a       <http://purl.org/webofneeds/message#FromExternal> ;
        <http://purl.org/webofneeds/message#hasContent>
                <https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#content-o6g1> ;
        <http://purl.org/webofneeds/message#hasMessageType>
                <http://purl.org/webofneeds/message#HintMessage> ;
        <http://purl.org/webofneeds/message#hasReceiverNeed>
                <https://satsrv07.researchs... [Body clipped after 1000 chars, total length is 2198]]

akka.camel.AkkaCamelException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-fa8c8c72188b-42454-1466670992720-0-28 not received. Exchange[Message: https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u {
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u
a       http://purl.org/webofneeds/message#EnvelopeGraph ;
http://www.w3.org/2004/03/trix/rdfg-1/subGraphOf
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo .
<https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo>
        a       <http://purl.org/webofneeds/message#FromExternal> ;
        <http://purl.org/webofneeds/message#hasContent>
                <https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#content-o6g1> ;
        <http://purl.org/webofneeds/message#hasMessageType>
                <http://purl.org/webofneeds/message#HintMessage> ;
        <http://purl.org/webofneeds/message#hasReceiverNeed>
                <https://satsrv07.researchs... [Body clipped after 1000 chars, total length is 2198]]
    at akka.camel.ProducerSupport$$anonfun$produce$1.applyOrElse(Producer.scala:73)
    at scala.runtime.AbstractPartialFunction.apply(AbstractPartialFunction.scala:36)
    at akka.camel.javaapi.UntypedProducerActor.onReceive(UntypedProducerActor.scala:49)
    at akka.actor.UntypedActor$$anonfun$receive$1.applyOrElse(UntypedActor.scala:167)
    at akka.actor.Actor$class.aroundReceive(Actor.scala:480)
    at akka.actor.UntypedActor.aroundReceive(UntypedActor.scala:97)
    at akka.actor.ActorCell.receiveMessage(ActorCell.scala:525)
    at akka.actor.ActorCell.invoke(ActorCell.scala:494)
    at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)
    at akka.dispatch.Mailbox.run(Mailbox.scala:224)
    at akka.dispatch.Mailbox.exec(Mailbox.scala:234)
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)

Caused by: org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-fa8c8c72188b-42454-1466670992720-0-28 not received. Exchange[Message: https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u {
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#envelope-er2u
a       http://purl.org/webofneeds/message#EnvelopeGraph ;
http://www.w3.org/2004/03/trix/rdfg-1/subGraphOf
https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo .
<https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo>
        a       <http://purl.org/webofneeds/message#FromExternal> ;
        <http://purl.org/webofneeds/message#hasContent>
                <https://satsrv07.researchstudio.at/won/resource/event/yvc2a9k0k479rrmcdydo#content-o6g1> ;
        <http://purl.org/webofneeds/message#hasMessageType>
                <http://purl.org/webofneeds/message#HintMessage> ;
        <http://purl.org/webofneeds/message#hasReceiverNeed>
                <https://satsrv07.researchs... [Body clipped after 1000 chars, total length is 2198]]
    at org.apache.camel.component.jms.reply.ReplyManagerSupport.processReply(ReplyManagerSupport.java:133)
    at org.apache.camel.component.jms.reply.TemporaryQueueReplyHandler.onTimeout(TemporaryQueueReplyHandler.java:61)
    at org.apache.camel.component.jms.reply.CorrelationTimeoutMap.onEviction(CorrelationTimeoutMap.java:53)
    at org.apache.camel.component.jms.reply.CorrelationTimeoutMap.onEviction(CorrelationTimeoutMap.java:30)
    at org.apache.camel.support.DefaultTimeoutMap.purge(DefaultTimeoutMap.java:209)
    at org.apache.camel.support.DefaultTimeoutMap.run(DefaultTimeoutMap.java:159)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
    at java.lang.Thread.run(Thread.java:745)

[INFO] [06/23/2016 08:47:57.266] [ClusterSystem-akka.actor.default-dispatcher-18] [akka://ClusterSystem/user/WonNodeControllerActor/ActiveMqHintProducerProtocolActor-f1400e9c-c8fa-4686-8d12-e9c3b65a9edd/$a] Message [akka.camel.FailureResult] from Actor[akka://ClusterSystem/user/WonNodeControllerActor#-1179587443] to Actor[akka://ClusterSystem/user/WonNodeControllerActor/ActiveMqHintProducerProtocolActor-f1400e9c-c8fa-4686-8d12-e9c3b65a9edd/$a#86988128] was not delivered. [8] dead letters encountered. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
[ERROR] [06/23/2016 08:47:57.266] [ClusterSystem-akka.actor.default-dispatcher-18] [akka://ClusterSystem/user/DeadLetterActor] Received dead letter message DeadLetter(FailureResult(org.apache.camel.ExchangeTimedOutException: The OUT message was not received within: 20000 millis due reply message with correlationID: Camel-ID-fa8c8c72188b-42454-1466670992720-0-29 not received. Exchange[Message: https://satsrv07.researchstudio.at/won/resource/event/rpwgh5570dejdwuyvhdn#envelope-iuje {
https://satsrv07.researchstudio.at/won/resource/event/rpwgh5570dejdwuyvhdn
a       http://purl.org/webofneeds/message#FromExternal ;
http://purl.org/webofneeds/message#hasContent
https://satsrv07.researchstudio.at/won/resource/event/rpwgh5570dejdwuyvhdn#content-amwr ;
http://purl.org/webofneeds/message#hasMessageType
http://purl.org/webofneeds/message#HintMessage ;
http://purl.org/webofneeds/message#hasReceiverNeed
https://satsrv07.researchstudio.at/won/resource/need/6558567111349901000 ;
http://purl.org/webofneeds/message#hasReceiverNode
https://satsrv07.researchstudio.at/won/resource ;
http://purl.org/webofneeds/message#hasSenderNode
http://satsrv06.researchstudio.at:8983/solr/#/won/ ;
... [Body clipped after 1000 chars, total length is 2198]],Map()),Actor[akka://ClusterSystem/user/WonNodeControllerActor#-1179587443],Actor[akka://ClusterSystem/user/WonNodeControllerActor/ActiveMqHintProducerProtocolActor-f1400e9c-c8fa-4686-8d12-e9c3b65a9edd/$a#86988128])

with the current build this is not an issue anymore and is working again, even though its unclear why this behavior occured or why it disappeared ??

may it was related to the restarting of the servers since there was a electricity breakdown on friday and the servers had to be restarted?
other possible explanation, that commit 6f0c0c5ea7e0624820f8807a6f77505e0b85238c fixed the problem, but i dont see why?


Stmoy/csharp vs cpp

Adding a comment about C# vs C++ for native modules

CC: @namrog84

cc: @kikisaints might need to publish manually to get website updated

@harinikmsft not any more, thanks to Jon! just a merge'll do :)


TestHost.Create() has incompatible overloads

rc1 added a set of "Func<IServiceCollection, IServiceProvider> configureServices" overloads to TestHost.Create() that is not compatible with the existing "Action configureServices" overloads:
public static TestServer Create(Action<IApplicationBuilder> configureApp, Action<IServiceCollection> configureServices)
public static TestServer Create(Action<IApplicationBuilder> configureApp, Func<IServiceCollection, IServiceProvider> configureServices)

After upgrading to rc1 I get this error from the compiler:
Error	CS0407	'void Startup.ConfigureServices(IServiceCollection)' has the wrong return type	MediaStreams.Test.
I've currently implemented a workaround by changing signature from void to System.IServiceProvider and returning services.BuildServiceProvider() at the end of the method.

Ugh.  Perhaps we should rename the second overload?
@davidfowl

Quick workaround for now is to cast explicitely:
var startup = new Startup(hostingEnvironment, applicationEnvironment);
            var server = TestServer.Create(startup.Configure, (Action<IServiceCollection>)startup.ConfigureServices);


[eas-cli] Add submit:internal

Why
I want to add support for submissions as part of workflows, where, when we start the job, we don't have access to the repository. So, we need to resolve submission config somewhere, ideally where we are isolated, can easily clone project, install dependencies and resolve dynamic config.
As we do with eas build:internal, I expect it will make sense to do eas submit:internal which will do what eas submit does usually — resolve all the credentials, using local filesystem or Expo servers  and then fetch the actual keys from Expo servers.
How
First, I changed structure of SubmitCommand/Submitter a bit — previously, SubmitCommand would create the Submitter and call submitAsync inside runAsync(). After my changes SubmitCommand will create and return the Submitter and the call site will need to call submitAsync.
By doing it this way I was able to add a getSubmissionInputAsync to BaseSubmitter which returns all-resolved submission input, as-it-would-have-been-used-in-submission-mutation. This ensures the same behavior for eas submit and eas submit:internal.
Once we have that, eas submit:internal is relatively straightforward:

create SubmitCommand, get Submitter.
getSubmissionInputAsync.
fetch necessary credentials by IDs from www (https://github.com/expo/universe/pull/16793).
validate that we have it all (https://github.com/expo/eas-build/pull/443) and print the JSON.

Test Plan
I was able to run easd submit:internal locally and got the JSON output.

Sorry, Newly Added Update Reviewers, I updated GraphQL types and had to adjust two tests (added isPaused and changed an assumed type of a temporary type fix). All is good!


[Publishing] Create Gcloud commands and rest API for below templates

Java - GCSToBigQuery
Python - GCSToBigQuery
Java - JDBCToBigQuery
Java - HiveToGCS
Python - JDBCToGCS

Add the commands in : go/go/dataproc-gcp-documentation-internal document also contains commands for reference from other templates

Done


Updated to use CUDA7

Closes #4

This looks good to me. Have you tested it on a new vanilla ubuntu instance?
At the end of the execution of the script you should reboot the instance and then you can run the nvidia-smi to check that CUDA is properly installed.

@ogrisel Does installing fortran belong in this script? I feel that should be installed in the script that installs scipy.

Tested and this works.

Merging. Thanks. I agree for gfortran, feel free to do in another PR.


Update sketch-tutorial.md

Added a missing pre-step that needs to happen in Sketch Choose a shortname for your Workspace in Sketch;
Improved example fields for Configure Azure AD SSO section;
Fixed the Configure Sketch SSO section with the proper steps. The user can do these steps on their own without the need to contact Sketch's customer support;
Removed unnecessary Create Sketch test user section.

@hugodias
Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

Hi, @Court72. Thank you. It's adequately signed. Do I need to do anything else to get it reviewed?

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

@hugodias, we created a separate PR for your changes in our private repo, please wait for 24 hours more to get the changes live into the main article.
#please-close

Thank you @v-hgampala . Can you confirm it was changed? For me, it still shows the old version. Thank you

Our reviewer was on vacation, and he is back now, the PR will be signed off within 24hrs to merge.

Thank you @v-hgampala . I see the changes were applied, but for some reasons some things that I removed in that PR are still there. There is one particular section that I think it's important to be removed as it's incorrect.

These values are not real. Update these values with the actual Identifier and Reply URL. Contact Sketch support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.

This statement says the user should reach out to support, but those values were available in the previous step, so that's unnecessary and can lead to confusion. Ideally, should be removed.
Should I open another PR to remove that section?
Thank you!

Thank you @v-hgampala . I see the changes were applied, but for some reasons some things that I removed in that PR are still there. There is one particular section that I think it's important to be removed as it's incorrect.

These values are not real. Update these values with the actual Identifier and Reply URL. Contact Sketch support team to get these values. You can also refer to the patterns shown in the Basic SAML Configuration section in the Azure portal.

This statement says the user should reach out to support, but those values were available in the previous step, so that's unnecessary and can lead to confusion. Ideally, should be removed.
Should I open another PR to remove that section?
Thank you!

No warries, I'll create a PR for these changes. Thank you!


[SPARK-42130][UI] Handle null string values in AccumulableInfo and ProcessSummary

What changes were proposed in this pull request?

After revisiting https://github.com/apache/spark/pull/39416 and https://github.com/apache/spark/pull/39623, I propose:

checking nullability of all string fields to avoid NPE
using optional string for the protobuf definition of all string fields. If the deserialized result is None, then set the string field as null.

Take AccumulableInfo as an example, it can be null on created: https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/status/LiveEntity.scala#L744
The null value can make difference in the UI logic: https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/ui/jobs/StagePage.scala#L791
This PR updates the developer guide and introduces utility methods for serializing/deserializing string fields. It also handles null string values in AccumulableInfo and ProcessSummary for setting an example.
Why are the changes needed?

update developer guide for better handling of null string values
add utility methods for future development of string serialization/deserialization
Properly handles null string values in AccumulableInfo and ProcessSummary for setting an example

Does this PR introduce any user-facing change?

No
How was this patch tested?

Test null string input values in AccumulableInfo and ProcessSummary protobuf serializer.

cc @LuciferYang @panbingkun @techaddict let's update all the string fields to make sure null string values are well handled. To avoid creating too many PRs and making the review/merge difficult, I suggest refactoring two or more classes in one PR.

cc @LuciferYang @panbingkun @techaddict let's update all the string fields to make sure null string values are well handled. To avoid creating too many PRs and making the review/merge difficult, I suggest refactoring two or more classes in one PR.

OK

@dongjoon-hyun may I have your approval for this one? So that we can work in parallel to finish the refactoring before Spark 3.4.0 rc0

Oh, sure.

@LuciferYang @dongjoon-hyun Thanks for the review. Merging to master


invalid update packet on block break

Getting "Received invalid update packet for null tile entity at BlockPos........" in console any time a break a gear box or powered axle, appears to show up on the client side of things only. only tested currently in Dev environment. is this reproducible., if so ill do some more testing and look into the matter.

it is reproducible, it's a side effect of producing my own TE update packets when i need to update something to prevent sending a chunk update (chunk updates are laggy). It works fine despite the error, on both Embers and this, but if you want to look into it, the code is here

i see 2 options atm 1 being either dropping the sync all together and notifying the world for a block update or the method i prefer being instead of sending the old packet to the client just telling the client to update the chunk. will implement which ever method you prefer, both are working in dev.

anything that triggers a chunk update is out of the question because it produces insane amounts of lag.


fix: saving test report

Summary
Reverted previous change to ZEPHYR_ENABLE for it requires a string
Ticket Link
none
If no release notes are required write NONE. Use past-tense. Newlines are stripped.
Example:
NONE

thank you Saturn


Example with on-demand asset

Could you please provide a complete example with on-demand asset?

@marchbold @ajwfrost could you help us?

@megajogos have you solved it somehow?

I just published a test application, which I used to test my ANEs, including my opensourced version of PlayAssets extension.
You can find there:

how to init the ANE including a fast-follow pack
how to fetch an on-demand pack (including a test on exceptions, which Harman's ANE does not provide)


Tap to remove keyboard

I want to remove keyboard when user taps the screen. How shall I do it?
Thank you

Thanks @McFriend ! :smile:
This doesn't seem specific to the library. StackOverflow is a more appropriate place to ask this question. :blush:
I'm going to close this issue, but the community should feel free to continue the discussion here.
Other ways to get help:

Ask on StackOverflow with the jsqmessagesviewcontroller tag
See the FAQ
Search previous questions


Add custom user agent header

@loudmouth Yes, everything for calling is plublic, since our libraries need to change some parts at some point. Think about vault, generator.java, etc...


Drawing/refresh issue on List.Item.Detail.Metadata + List.Item.Detail.Metadata.TagList

Description
Hello,
I am currently creating an extension for personal use.
The data I want to display comes from multiple different asynchronous MySQL requests. I'm having some refresh issues and  since I am not familiar with React, I am not sure yet if the issue is on my end or with Raycast itself.
For the purpose of this post, I've removed a lot of code and all MySQL requests, replaced by local data in a variable.
The issue still happens and I'm posting here the extension code in case you want to tryout.
Here's a view of the actual extension

As you can see, the List.Item.Detail.Metadata.TagList is still displaying "Loading…" while it should have updated.
At this point, if I press down-arrow to select the "Commissions" and then Up-arrow to go back to "Overall", the tag list will be populated with the expected values. This behavior looks like a Raycast rendering bug to me, but as said, chances are high I'm completely missing something with React.
On the code, if I uncomment lines 19 & 30 to manually add a delay on the async functions, the refresh of the tag list is now working. In fact, only uncommenting line 30 is enough.

Am I doing things wrong?
Thanks —a lot— in advance for any idea or guidance.
Best,
import { useState, useEffect } from "react";
import {Action, ActionPanel, List, Icon, Detail, showToast, Toast, Color} from "@raycast/api";
import { usePromise, getProgressIcon } from "@raycast/utils";

const storage = {};

export default function myItemsRaycast() {
	const placeholders = {
		totalsStrings: {
			euros	: 'Loading…',
			dollars	: 'Loading…',
			total	: 'Loading…'
		},
		someTextStrings: 'Loading…'
	};

	const myItems = {
		getCommissions: async () => {
			// await new Promise(resolve => setTimeout(resolve, 1000)); // Uncomment this to fix the drawing/refresh bug
			storage.commissionsQuery = {
				euros			: 100,
				dollars			: 200,
				dollarsInEuros	: 0,
				total			: 0
			};
			return storage.commissionsQuery;
		},

		getSomeText: async () => {
			await new Promise(resolve => setTimeout(resolve, 2000)); // Uncomment this to fix the drawing/refresh bug
			return 'This is some text.';
		},

	};

	const {data: totalsObj, isLoading: isLoadingTotals} = usePromise(myItems.getCommissions);
	const {data: someText, isLoading: isLoadingSomeText} = usePromise(myItems.getSomeText);

	const [totalsStrings, setTotalsStrings] = useState(placeholders.totalsStrings);
	const [someTextStrings, setSomeTextStrings] = useState(placeholders.someTextStrings);

	const isLoading = isLoadingTotals || isLoadingSomeText;

	useEffect(() => {
		if (totalsObj) {
			const totalsStringObj = {
				euros: `${totalsObj.euros} €`,
				dollars: `$ ${totalsObj.dollars}`,
				total: `${totalsObj.total} €`
			};
			setTotalsStrings(totalsStringObj);
		}
	}, [totalsObj]);

	useEffect(() => {
		if (someText) {
			setSomeTextStrings(someText);
		}
	}, [someText]);

	return (
		<List isShowingDetail isLoading={isLoading}>
			<List.Item
				title="Overall"
				detail={
					<List.Item.Detail isLoading={isLoading}
						metadata={
							<List.Item.Detail.Metadata>
								<List.Item.Detail.Metadata.Label title="COMMISSIONS" />
								<List.Item.Detail.Metadata.Label title="totalsStrings.euros" text={totalsStrings.euros} />
								<List.Item.Detail.Metadata.Label title="totalsStrings.dollars" text={totalsStrings.dollars} />
								<List.Item.Detail.Metadata.Label title="totalsStrings.total" text={totalsStrings.total} />
								<List.Item.Detail.Metadata.TagList key="totalsA" title="Totals">
									<List.Item.Detail.Metadata.TagList.Item key="totalsB" icon={Icon.Coin} text={totalsStrings.euros} />
									<List.Item.Detail.Metadata.TagList.Item key="totalsC" icon={Icon.Coin} text={totalsStrings.dollars} />
									<List.Item.Detail.Metadata.TagList.Item key="totalsD" icon={Icon.Coins} text={totalsStrings.total} />
								</List.Item.Detail.Metadata.TagList>
								<List.Item.Detail.Metadata.Separator />
								<List.Item.Detail.Metadata.Label title="Some Text" text={someTextStrings} />
								<List.Item.Detail.Metadata.Separator />
							</List.Item.Detail.Metadata>
						}
					/>
				}
			/>
			<List.Item
				title="Commissions"
				detail={
					<List.Item.Detail
					/>
				}
			/>
		</List>
	);
}

Steps To Reproduce
No response
Current Behaviour
List.Item.Detail.Metadata.TagList is not refreshed when functions are instantly executed.
A manual delay must be added.
Expected Behaviour
List.Item.Detail.Metadata.TagList refresh normally.

Kind bump?

Hey! It's an issue in Raycast, we are looking into it

This should be fixed now

Good new @mathieudutour, thank you.
Not sure if anything related or not, but since v1.55.1 my extension crashes when loading it's data 75% of the time.
It was not crashing before.
Here's a typical crash report
{"app_name":"Raycast","timestamp":"2023-07-12 14:51:59.00 +0200","app_version":"1.55.1","slice_uuid":"9b6fa29c-14d0-3fe7-80d8-4c906468207e","build_version":"0","platform":1,"bundleID":"com.raycast.macos","share_with_app_devs":1,"is_first_party":0,"bug_type":"309","os_version":"macOS 13.4 (22F66)","roots_installed":0,"name":"Raycast","incident_id":"EFE22376-71A5-49E2-A88E-37EF6396B4FF"}
{
  "uptime" : 160000,
  "procRole" : "Default",
  "version" : 2,
  "userID" : 501,
  "deployVersion" : 210,
  "modelCode" : "Macmini9,1",
  "coalitionID" : 6951,
  "osVersion" : {
    "train" : "macOS 13.4",
    "build" : "22F66",
    "releaseType" : "User"
  },
  "captureTime" : "2023-07-12 14:51:58.6497 +0200",
  "incident" : "EFE22376-71A5-49E2-A88E-37EF6396B4FF",
  "pid" : 31350,
  "translated" : false,
  "cpuType" : "ARM-64",
  "roots_installed" : 0,
  "bug_type" : "309",
  "procLaunch" : "2023-07-12 14:51:55.3367 +0200",
  "procStartAbsTime" :<PHONE_NUMBER>656,
  "procExitAbsTime" :<PHONE_NUMBER>241,
  "procName" : "Raycast",
  "procPath" : "\/Applications\/Raycast.app\/Contents\/MacOS\/Raycast",
  "bundleInfo" : {"CFBundleShortVersionString":"1.55.1","CFBundleVersion":"0","CFBundleIdentifier":"com.raycast.macos"},
  "storeInfo" : {"deviceIdentifierForVendor":"B009D38E-5CCB-58D3-825D-DC5E72CFD479","thirdParty":true},
  "parentProc" : "launchd",
  "parentPid" : 1,
  "coalitionName" : "com.raycast.macos",
  "crashReporterKey" : "0B675366-D570-6C43-274B-39E66551EEDD",
  "codeSigningID" : "com.raycast.macos",
  "codeSigningTeamID" : "SY64MV22J9",
  "codeSigningFlags" : 570503953,
  "codeSigningValidationCategory" : 6,
  "codeSigningTrustLevel" : 0,
  "wakeTime" : 21005,
  "sleepWakeUUID" : "D38C4309-201D-4EB3-AE60-626BE2502F78",
  "sip" : "enabled",
  "vmRegionInfo" : "0x18 is not in any region.  Bytes before following region:<PHONE_NUMBER>19656\n      REGION TYPE                    START - END         [ VSIZE] PRT\/MAX SHRMOD  REGION DETAIL\n      UNUSED SPACE AT START\n--->  \n      MALLOC_NANO (reserved)<PHONE_NUMBER>00-600020000000 [128.0M] rw-\/rwx SM=NUL  ...(unallocated)",
  "exception" : {"codes":"0x0000000000000001, 0x0000000000000018","rawCodes":[1,24],"type":"EXC_BAD_ACCESS","signal":"SIGSEGV","subtype":"KERN_INVALID_ADDRESS at 0x0000000000000018"},
  "termination" : {"flags":0,"code":11,"namespace":"SIGNAL","indicator":"Segmentation fault: 11","byProc":"exc handler","byPid":31350},
  "vmregioninfo" : "0x18 is not in any region.

Same extension, but more complex now, since I've continued working on it.
BTW, as you can see, it leads to a complete Raycast crash, app needs to be relaunch.

All database request are made to my local server. So you won't get any data.
However, your name sounds french to me, so this means awe could be on the same time zone and could easily make a screensharing session if this could help.
You can message me to arrange that, I'm available today until 16h45

Sure, I have 15min as well, here's an Around link: https://around.co/r/74i3arif

Hi @mathieudutour, I've sent you the log privately on iMessage.
Thanks for your time and solving those bugs!!!


Initialize readonly/editable in LineEdit and TextEdit controls

fixing a couple of uninitialized variables from #28287

Can we have http://www.stroustrup.com/C++11FAQ.html#member-init soon?
It makes being disciplined about initialisation almost trivial.

Thanks!

Can we have http://www.stroustrup.com/C++11FAQ.html#member-init soon?

Yes, this is just pending on @hpvb formalizing his guidelines for C++11 usage in Godot as we discussed at the last GodotCon.


[AutoPR reservations/resource-manager] Add new reserved resource type CosmosDb

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3690

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/2518


await tracking events

Description
We used the fire and forget approach for those tracking events. However, some aren't recorded as the process is already closed with no time to send the events

Minor, but what if we await them at the end? This could look like:
const tracksEvents = [];

// Do some stuff

tracksEvents.push( trackEvent( 'wpcli_command_execute', commonTrackingParams ) );

// Do some other stuff

await Promise.all( tracksEvents );

The advantage here is that we don't wait for them unless we need to.

@joshbetz When I added this, my thinking was: lets await only the events that needs to be awaited, ie those appearing just before the closing of the process: command_cancel and command_end. For others, they still have time to report, so they aren't awaited, fired and forget about.
What do you think? 🤔

@elazzabi probably fine for now and definitely simpler to implement. If we notice problems in the future, we can do what I've suggested.

Thank you for the review Josh. This branch was behind master and had some merging conflicts. Merging now


102773 Fallback solution sending ics by SMTP when meeting API fails.

AB#102773

Add AB#xxxxxx where xxxxx is the PBI number to Descrioption of PR. A webhook will then connect PR to the PBI
Remember to add 3 manual tasks to PBI, a task for each environment. Task = Setup config pre deploy

Quick question: Did we consider using a different Library for sending mail. Seems SmtpClient is not recomended in newer projects by microsoft:
https://github.com/dotnet/platform-compat/blob/master/docs/DE0005.md

I think this PR can't be released as-is. I think the fallback solution should be implemented for Update and Cancel also (ie. all other places where calling meeting API can fail). AND: different combinations of Create, Update and Cancel together with combinations of normal update of meeting vs use of fallback solution must be tested.
Sample test: If fallback solution for create was used and a following Cancel of the same meeting leads to still existing meetings in participants calendars, this is very unfortunate. Before using more time and fixing comments in PR, I think this should be discussed

Quick question: Did we consider using a different Library for sending mail. Seems SmtpClient is not recomended in newer projects by microsoft:
https://github.com/dotnet/platform-compat/blob/master/docs/DE0005.md
and If we're going to use it, consider using SendMailAsync() as it supports async awaits ,and wrap client creating in a using statement to clean up

SmtpClient was selected for simplicity and since it is already in use in ProCoSys.
I was not aware of SendMailAsync(). Have converted to use that instead of SendAsync().

I think this PR can't be released as-is. I think the fallback solution should be implemented for Update and Cancel also (ie. all other places where calling meeting API can fail). AND: different combinations of Create, Update and Cancel together with combinations of normal update of meeting vs use of fallback solution must be tested.
Sample test: If fallback solution for create was used and a following Cancel of the same meeting leads to still existing meetings in participants calendars, this is very unfortunate. Before using more time and fixing comments in PR, I think this should be discussed

To target this challenge, it was agreed with Børje to include a message in the mail, sent from the fallback solution, informing about the consequences.

@janid1967 @TordJoranger @jsoi-eq Any further unresolved comments or questions, or do you approve this?

Add AB#xxxxxx where xxxxx is the PBI number to Descrioption of PR. A webhook will then connect PR to the PBI
Remember to add 3 manual tasks to PBI, a task for each environment. Task = Setup config pre deploy

@janid1967
Config attributes has been setup in non-prod and prod such that fake email is sent as fallback in non-prod and real email in prod.

Has it been discussed to use graph to send e-mail? Ref ongoing work by Terje Woldseth in 105625

Has it been discussed to use graph to send e-mail? Ref ongoing work by Terje Woldseth in 105625

@BorjeStangeland Can you confirm that it is still desired to use SMTP client.

@trondlindanger @janid1967 @TordJoranger @terjewoldseth : Min forståelse er at smtp mulighetene blir blokkert i nær fremtid og at all utsendelse av mail må gå via ny løsning (graph) som Terje har implementert i sak AB#105625

@janid1967 @TordJoranger Avklart med @BorjeStangeland : Oppgraderer til å bruka graph i denne branchen. Det vil skje om 1-2 veker når Håvard og Terje har funnet ut av utfordringane som Håvard har møtt på i samband med tilsvarande jobb han gjennomfører på DCP.


Bump framework version

$subject

PR builder has passed in https://github.com/wso2/carbon-identity-framework/pull/6023


Add TypeScript support

Add support for TypeScript users.You don't have to rewrite everything. A .d.ts file is enough. If you want, I can submit a PR.
Thanks in advance.

PR: #26

Currently created a custom .d.ts file for this.


Set the source and target to Java 8, making this project only support Java 8+.

This is to reflect the fact that already a lot of code is only compatible with Java 8+, mainly because of  Math.*Exact() and Files.walk().

You could then remove the few checks that still exist to determine if the JDK is 8+ or not (SystemUtils.isJavaVersionAtLeast(JavaVersion.JAVA_1_8)).


Add Homebrew installation method to README.md

Due to the successful merge of https://github.com/Homebrew/homebrew-core/pull/104251, Dooit is now part of the homebrew/core repository and can be installed by running:
brew install dooit

This pull request adds this information to the installation section of README.md that explains how to install dooit with Homebrew.

Hey there!
Thank you so much for this PR.. I had no idea that homebrew worked like AUR
Quick question: Do I need to maintain the package or will it fetch the latest release from github?

It should automatically update the formula whenever you publish a new release on GitHub, with no additional work required on your part.

Awesome! Great work <3

@@superatomic @kraanzu  Hello, it looks like something goes wrong here. I can't install dooit with the Homebrew tool.
➜  ~ brew install dooit
Running `brew update --preinstall`...
Warning: No available formula with the name "dooit".
==> Searching for similarly named formulae...
Error: No similarly named formulae found.
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...
Error: No formulae found in taps.

➜  ~ brew search dooit
Error: No formulae or casks found for "dooit".

Based on your conversation, brew install dooit should work normally now. 😊
Looking forward to your reply.  THX. ^_^

@Abeautifulsnow Can you try running brew update and trying it again? There's a possibility that you just need to pull in the newest formulae.

@superatomic Thank you for your help. Thebrew update command worked for me, and then I successfully installed dooit.


Item Serialization

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the feature
Hello there,
I need some Item Serialization, I would also implement it.
Some rudimentary serialization well be enough for what I need, would it be fine if I add a MockSerializer in UnsafeValues?
Serializes ItemStack:

Only ItemMeta
Incompatible with CraftmagicNumbers (Craftbukkit UnsafeValues)
Maype more metas as I go along

The goal is here to just add some basic serialization so that lager serializable structures can be tested.

Seems like it's unimplemented at the moment. Sure go ahead!


Clarify intended behavior of choco upgrade regarding in-place upgrades

What New Or Updated Would You Like To See?
Many native application installers do not implement upgrades internally and always install a new version, relying on the user to uninstall previous versions if desired. Choco's user and packaging documentation do not explicitly describe what the intended behavior of choco upgrade is in this situation.
Why Is It Needed?
With no explicit guidance on the intended behavior of upgrade different maintainers and users have reached different conclusions about how upgrades should be handled. This leads to an inconsistent user interface for choco packages and requires that users must be familiar with not only how the native installer of each application behaves, but also how the maintainer of each choco package has chosen to implement upgrades.
Additional Context?
This documentation request is a direct result of discussions on Issue 2156 for the Blender community package so additional context can be found there.
In short, there are at least 5 different ways packages could implement upgrades for native installers that don't handle them internally. I'm aware of 3 of these variations being used in the wild in the community repository, but other variations may also be present.
In response to choco upgrade a package could:

Just run the native installer, leaving the current version installed and installing an additional new version. Implemented by Blender maintained by @chocolatey-community.
1a. By default run the native installer, but provide a parameter to delete the current and/or previous version(s). Implemented by ?? suggested by @pauby in Blender issue report linked above.
Attempt to uninstall the current version before installing the new version. Implemented by PyCharm-Community maintained by @mkevenaar.
2a. By default attempt to uninstall the current version before installing the new version, but provide a parameter to keep previous versions. Implemented by QGIS maintained by @teknowledgist.
Report "Upgrades unsupported. This package only supports install and uninstall". Implemented by ?? suggested by @jedfrechette in Blender issue report linked above.

QGIS is the only package that I've found in the community repository that documents which of the implementations they've chosen to adopt. The result of this is that the only way for users to know what will happen during an upgrade of a given package is to either experiment with installing multiple versions of that package or inspect the source code of the package, neither of which is ideal.

Clarification of the expected behaviour is over on [Reddit]https://www.reddit.com/r/chocolatey/comments/11fnisc/comment/jakjr2e/?utm_source=reddit&utm_medium=web2x&context=3)

I don't want to repeat everything that has already been said. I feel that documenting the options available to maintainers when creating packages and stating what the default expected behaviour is (do what the installer does) would help but leave it open enough for maintainers to change that behaviour if they want to.
I've already talked about package parameters to help with unexpected behaviour in the thread linked in the original issue comment, so all I'm doing here is highlighting that.

I agree that simply documenting the intended behavior better would be a good solution.


fix(linter): fix panic in fixer for oxc/only-used-in-recursion

closes #6068

#6070  👈
main

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


Markdown syntax is not working

Hi, thanks for the plugin !
The markdown syntax from the doc  (with tabs) is not working:
@startmindmap
* root node
	* some first level node
		* second level node
		* another second level node
	* another first level node
@endmindmap

but using this syntax is ok:
 @startmindmap
* root node
** some first level node
*** second level node
**** another second level node
** another first level node
 @endmindmap

is it a correct behavior?

That does not look like correct behavior since the online server returns the correct result.
I am going to take a look in a few days.

This problem still occurs on my environment.
Obsidian Version 1.1.9 (Installer 0.15.9)
plugin version 1.6.6


Facebook flipper unknown device type

DESCRIPTION
After configuring flipper and idb to run on a real iPhone device using the RNTester app, I receive the following error:
facebook flipper unknown device type

I can see js logs in Flipper, but not native logs.
SOLUTION
Not using Flipper to display the native logs.
Closing Flipper, re-starting xcode and metro. I can see the JS and Native logs in xcode.
This only possible after fixing the idb installation.
RELATED
https://github.com/facebook/flipper/issues/2993
https://github.com/facebook/flipper/issues?q=is%3Aissue+Unknown+device+type+is%3Aclosed
https://github.com/facebook/flipper/issues/262
https://github.com/facebook/flipper/issues/3361
https://github.com/facebook/flipper/issues/3168

Thanks.

Should Android accessibilityRole map 1:1 to talkback Role? I.e. expose TTSSpan as a separate API from role, like it seems to be done on Android.

I agree. I will expose TTSSpan as a separate API from role

Is it possible to avoid exposing the APIs which only apply to text spans from view props? One idea was adding a Text specific prop like accessibilitySpan to model the API.

I will add a specific prop accessibilitySpan to model the API.

How does ARIA model this today? And should React Native offer an API that looks similar for web-style usage.

I will try to build the API to look similar to web.

Phone Number

Phone Number behaves similar to Web, an additional prop accessibilityRole="telephone" is required to identify the Text as telephone number. The accessibilityRole telephone will be renamed accessibilitySpan telephone.
HTML
https://jhalabi.com/blog/accessibility-phone-number-formatting
Reads 7 0 3(pause) 5 5 5(pause) 1 2 1 2

ReactNative
Reads using TalkBack default behaviour for phone numbers
<Text
  accessibilityRole="telephone"
  accessibilityUnit="0118888888"
  style={styles.redBackground}>
<PHONE_NUMBER>
</Text>

Units - Distances

Web does not seems to have specific support for units, aria-label includes the unit to announce with the screenreader.
HTML
https://stackoverflow.com/a/72018468/7295772
Reads as the 36 inch product
the 36"inch product

or the 36 inch product

The 36" product.

ReactNative
Reads 10 meters
10
<Text
  accessibilityRole="measure"
  accessibilityUnit="meter"
  accessible={true}
  style={styles.redBackground}>
  m
</Text>

Other type of Units

HTML
Web  does not seem to have specific support for units. Web and ReactNative already support aria-label to over-ride default Screenreader behaviour.
ReactNative
Reads 10 seconds
10
<Text
  accessibilityRole="measure"
  accessibilityUnit="second"
  accessible={true}
  style={styles.redBackground}>
  s
</Text>

Reads 10 milli
<Text
  accessibilityRole="measure"
  accessibilityUnit="milli"
  accessible={true}
  style={styles.redBackground}>
  m
</Text>

Reads 10 usd
<Text
  accessibilityRole="money"
  accessibilityUnit="USD"
  accessible={true}
  style={styles.redBackground}>
  US
</Text>

HTML
https://stackoverflow.com/a/37849100/7295772
HTML does not support currencies and requires some workaround to correctly announce it.
https://stackoverflow.com/a/54153662/7295772
aria-label does not always announced on spans.

  $38.57

38 dollars and 57 cents

ReactNative
Reads 10 usd
<Text
  accessibilityRole="money"
  accessibilityUnit="USD"
  accessible={true}
  style={styles.redBackground}>
  US
</Text>

Date
Native supports dates in different format (language of the screenreader).
More info here https://www.accessibilityoz.com/2021/06/the-trouble-with-blind-dates-screen-readers-and-date-formatting/
ReactNative
Read 7th of January 1987 in US, 2nd of July 1987 in Italy.
<Text
  accessibilityRole="date"
  accessible={true}
  style={styles.redBackground}>
  02/07/1987
</Text>

Verbatim
ReactNative
spelled as r e a c t - n a t i v e
  <Text
    accessibilityRole="verbatim"
    accessible={true}
    style={styles.redBackground}>
    react-native
  </Text>


Sync server: Load settings for single project

Description
Sync server does not have ability to retrieve settings for only one project but always cache all available projects. This is ok when sync server is running in tray but it is a big issue and slowdown when it's used in host e.g. in loader tool.
Addicitonal info
There should be also some kind of cache invalidation after some timeout to be able refresh settings after some time.
[cuID:]

Fix in https://github.com/pypeclub/OpenPype/pull/3280


Plugin crashes when upating snowflake_resource_monitor

Provider Version
v0.72.0
Terraform Version
1.6.2
Describe the bug
When trying to add a new user to snowflake_resource_monitor it crashes.
Expected behavior
It should update the resource monitor with the additional user
Code samples and commands
The error occured when adding User2 to notify_users
resource "snowflake_resource_monitor" "demo" {
  name         = snowflake_warehouse.demo.name
  credit_quota = 5

  frequency       = "DAILY"
  start_timestamp = "2023-11-01T17:00:00-07:00"
  end_timestamp   = "2024-10-31T17:00:00-07:00"

  notify_triggers           = [75]
  suspend_trigger           = 85
  suspend_immediate_trigger = 95

  notify_users = ["User1", "User2"]
  warehouses   = [snowflake_warehouse.demo.name]
}

Additional context
snowflake_resource_monitor.demo: Modifying... [id=DEMO_WH]
╷
│ Error: Request cancelled
│
│   with snowflake_resource_monitor.demo,
│   on demo.tf line 7, in resource "snowflake_resource_monitor" "demo":
│    7: resource "snowflake_resource_monitor" "demo" {
│
│ The plugin.(*GRPCProvider).ApplyResourceChange request was cancelled.
╵

Stack trace from the terraform-provider-snowflake_v0.72.0 plugin:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x8 pc=0x103669608]

goroutine 16 [running]:
github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources.UpdateResourceMonitor(0x14000f38300, {0x103f6a760?, 0x14000b0e340?})
	github.com/Snowflake-Labs/terraform-provider-snowflake/pkg/resources/resource_monitor.go:346 +0x1448
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).update(0x103fa88c0?, {0x103fa88c0?, 0x14000f2e870?}, 0xd?, {0x103f6a760?, 0x14000b0e340?})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.29.0/helper/schema/resource.go:800 +0x134
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*Resource).Apply(0x1400061fb20, {0x103fa88c0, 0x14000f2e870}, 0x14000ef5040, 0x14000f38180, {0x103f6a760, 0x14000b0e340})
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.29.0/helper/schema/resource.go:919 +0x6b0
github.com/hashicorp/terraform-plugin-sdk/v2/helper/schema.(*GRPCProviderServer).ApplyResourceChange(0x14000c92018, {0x103fa88c0?, 0x14000f2e750?}, 0x14000f14820)
	github.com/hashicorp/terraform-plugin-sdk/v2@v2.29.0/helper/schema/grpc_provider.go:1060 +0xb78
github.com/hashicorp/terraform-plugin-go/tfprotov5/tf5server.(*server).ApplyResourceChange(0x14000c9c000, {0x103fa88c0?, 0x14000f03d40?}, 0x14000edb0a0)
	github.com/hashicorp/terraform-plugin-go@v0.19.0/tfprotov5/tf5server/server.go:859 +0x3bc
github.com/hashicorp/terraform-plugin-go/tfprotov5/internal/tfplugin5._Provider_ApplyResourceChange_Handler({0x103f1dca0?, 0x14000c9c000}, {0x103fa88c0, 0x14000f03d40}, 0x14000edb030, 0x0)
	github.com/hashicorp/terraform-plugin-go@v0.19.0/tfprotov5/internal/tfplugin5/tfplugin5_grpc.pb.go:467 +0x170
google.golang.org/grpc.(*Server).processUnaryRPC(0x14000780d20, {0x103fb7e20, 0x14000c0cb60}, 0x14000e41560, 0x14000c8a180, 0x104b64c78, 0x0)
	google.golang.org/grpc@v1.57.0/server.go:1360 +0xcb4
google.golang.org/grpc.(*Server).handleStream(0x14000780d20, {0x103fb7e20, 0x14000c0cb60}, 0x14000e41560, 0x0)
	google.golang.org/grpc@v1.57.0/server.go:1737 +0x82c
google.golang.org/grpc.(*Server).serveStreams.func1.1()
	google.golang.org/grpc@v1.57.0/server.go:982 +0x84
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.57.0/server.go:980 +0x16c

Error: The terraform-provider-snowflake_v0.72.0 plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Also on 0.73.0

Also on 0.80.0 for me

I am on 0.77.0 and have the same error:

Hey @kalinon. Thanks for reporting the issue.
The fix should be really simple, I will add this today (if it is really as simple as it seems, we will add it to the nearest release).


any more detailed instruction how to install on Mac?

I am trying to install this on Mac OSX, searched qmake through HomeBrew, but could not find it. Can someone give more detailed instructions?
Currently, the doc says:
    $ export PROTOBUF_PREFIX=/path/to/protobuf-2.6.1
    $ qmake
    $ make

Hi @guozheng ,
qmake is part of Qt. One of the build requirements is Qt 5 (see top of https://github.com/estan/protoc-gen-doc/blob/master/BUILDING.md). You can install this however you want, but I suggest qt5 via Homebrew.
If you need even more detailed instructions, you can look at the Travis build file (https://github.com/estan/protoc-gen-doc/blob/master/.travis.yml). The tool is built and tested regularly on Mac OS X, and that file contains the exact steps.
In short, to get the dependencies from Homebrew:
brew update
brew install qt5 protobuf
brew link --force qt5
export PROTOBUF_PREFIX=$(brew --prefix protobuf)

and then build the tool:
git clone git@github.com:estan/protoc-gen-doc.git
cd protoc-gen-doc
qmake
make

Copy the resulting protoc-gen-doc executable to where you want it, but it must be in PATH for the protoc compiler to find it, or be specified with --plugin (explained in README.md).
Hope this helps.

hi i tried above steps but how do i get html from PROTO
when i say qmake it says could not resolve sdk path for macosx,Please help

@sumancholleti: I don't have access to a Mac myself, so I can't test. But, how did you install Qt?


anagram: fix typo s/indentical/identical; rm duplicate cases; rm all "string argument" cases

rationale in individual commit messages

Note to myself, https://github.com/exercism/xhaskell/pull/224 needs notification when this gets merged

Looks good :+1:


Allow Updatecli manifest/values to use JSON file

depends on:

[ ] https://github.com/updatecli/updatecli/pull/1457

Allow to use JSON, technically speaking json a subset of YAML and therefor fully compatible.
For complex template, I find using json more convenient than yaml as we don't have to deal with tab and space
Test
To test this pull request, you can run the following commands:
cd pkg/core/config/
go test
cd ../../
go build -o bin/updatecli .
./bin/updatecli diff --config e2e/updatecli.d/success.d/npm.jso

Additional Information
Tradeoff
/
Potential improvement

As long as JSON does not replace YAML, it looks ok 👍


Use ls instead of find for EE ansible docs

Currently find command is used to check if ansible plugins are present for a given candidate
path.
In some cases the findutils might not be bundled within execution-environments.
Hence instead find command the PR updateslogic to use ls command to figure out if ansible plugin files are present in a given path

@ssbarnea As your are aware testing is very minimal for this repository and improving the test coverage is handled as part of issue https://github.com/ansible/vscode-ansible/issues/213
This PR tries to fix a know issue with downstream EE's and not a new feature addition. So I think it's shouldn't be blocked for lack of test as it is simultaneously worked up and the issue I referenced earlier will be used to track it.


The last value along the x-axis is missing

The last value along the x-axis is showing half.

@usmanvaince do you have a fiddle that reproduces this?

Closing due to lack of test case & because I think this is a duplicate of an older issue


fix issue with update_y_X when we refit forecaster

Reference Issues/PRs
Fixes #1593
What does this implement/fix? Explain your changes.

When re-fitting (as opposed to updating) forecasting models self._y will be updated to the latest training data used.
This fix adds an additional check in update_y_X. If the forecaster is fitted it means that this is an update call (in fit the first line of code should be self._is_fitted = False). If it's fitted we use the combine first, if it's not fitted we overwrite _y with y.
What should a reviewer concentrate their feedback on?

[x] Does combine_first have a different purpose that this fix will break (maybe when update is used).   (It does)

For all contributions

[X] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[x] I've added unit tests and made sure they pass locally.

The new test fails on ColumnEnsembleForecaster because f._y and y_train[3:] have different shapes.
(47, 1) and (47,) respectively. Should I fix this in the test and make it flexible for this type of shape issues OR fix it in the ColumnEnsembleForecaster instead?

Went for the "make the test flexible on this type of shape differences" option.

the proposed fix works only for pandas, not for numpy.
lines 806ff already check whether _y exists or not. The existing check is problematic however, since _y can exist already in the case fit is called a second time. So instead of adding another if in 814, I would simply suggest to add a third condition or not self._is_fitted in 806. This would also make the fix work for numpy.

Thanks - that makes sense, the previous one was lousy.
As you said - the test will be redundant when  #1613 is fixed, but useful in the meantime.


Examine-memory debugger selections not removed on uninstall

Sometime when I invoke the Code: Examine Memory window (which is wonderful to have), it adds a new entry to the debugger list that is never removed.  Even uninstalling and reinstalling the extension twice does not remove these entries.  I'm not sure what causes them to be abandoned.
The bug is that when the extension is uninstalled, these abandoned entries should definitely be removed.
Remote:  PhotonOS, gdb RHEL 7.6.1-120.el7.  Latest extension code as of 2022 Sept 23, 4/16/2022, 02:03:38 release.
NOTES:

Deleting .vscode-server  from my home directory on the SSH host did NOT resolve the issue.
Disabling, then re-enabling extension had no effect.
Disconnect/reconnect no effect.

What do you mean by "new entry to the debugger list"?
Side question: do you know if there is an activation of extensions "onUninstall" / "onDisable"? I'm not sure that it is; and then there would be no option to remove something there (can obviously only be done when the extension is triggered).

The debugger prompt that is displayed when you run Code-Debug:  Examine
memory location:
[image: image.png]
No idea, but from having a lot of install experience, my guess is that the
extension data is located in the wrong place where the data lifetime is
permanent.  E.g., instead of being located in a per-VS-session location,
it's being stored in a permanently-scoped location, so it is left on
purpose by design.
A quick workaround would be add a command to clear the debuggers list or
delete entries from it.  Really not what's needed but hey that would help
right now!
On Fri, Sep 23, 2022 at 2:19 PM Simon Sobisch @.***>
wrote:

What do you mean by "new entry to the debugger list"?
Side question: do you know if there is an activation of extensions
"onUninstall" / "onDisable"? I'm not sure that it is; and then there would
be no option to remove something there (can obviously only be done when the
extension is triggered).
—
Reply to this email directly, view it on GitHub
https://github.com/WebFreak001/code-debug/issues/378#issuecomment-1256530583,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFCPGNT3HZSB6Q3JKSS33EDV7XYEHANCNFSM6AAAAAAQUDQVPA
.
You are receiving this because you authored the thread.Message ID:
@.***>

Images can only be posted vie GitHub online, not by mail, please post that again.


Update French translation

After updating the German translation with the huge help of two native speakers (the PR is now finished and awaiting review), I decided to also have a go at updating the French translation.
Thanks to the great efforts of @ansh and translators (including most notably @Signez and @fenarinarsa, from looking at previous PRs), the French translation is already a lot more complete which meant that there was much less for me to do to bring it up-to-date.
I again used DeepL, I tried to follow the conventions and existing translations for terms and because, unlike German, I do actually speak French (although definitely not to the level of a native speaker), I also combined that with my own French knowledge to come up with the suggested changes in this PR.
I did check it carefully, but as I'm not a native speaker and my French could most certainly be categorised as "rusty", there are doubtless quite a few errors, awkward phrasings, etc.
So if there are any native French speakers who feel like giving it a look and suggesting changes, that would be greatly appreciated 🙏

Oh, and I am sorry, but I think I disagree with the translation of tag by étiquette.
In other similar softwares, tag is translated to hashtag (in Mastodon), tag (in Threads), and other software prefer to use the word mot-clé (mots-clés as plural, literally keyword). Let's note that France Termes tried to push for mot-dièse but it was never really used by users beside jokes about how lame it was.
I have a preference for mot-clé, so if you're up to the task, I would suggest a quick find-and-replace of étiquettes into mots-clés and étiquette into mot-clé. Beware, while étiquette is feminine, mot-clé is masculine!

Oh, and I am sorry, but I think I disagree with the translation of tag by étiquette.
In other similar softwares, tag is translated to hashtag (in Mastodon), tag (in Threads), and other software prefer to use the word mot-clé (mots-clés as plural, literally keyword). Let's note that France Termes tried to push for mot-dièse but it was never really used by users beside jokes about how lame it was.
I have a preference for mot-clé, so if you're up to the task, I would suggest a quick find-and-replace of étiquettes into mots-clés and étiquette into mot-clé. Beware, while étiquette is feminine, mot-clé is masculine!

I have to confess that I chose étiquette simply because it seemed the more likely of the two options between étiquette and balise that were listed as the translations for tag (in the computing sense) in the dictionary entry I looked at:

Anyway, I have no strong feelings on the matter and I'm happy to use mot-clé. I've done the the find-and-replace and (I hope) adjusted the surrounding words correctly, but if you could double-check that all is in order that would be brilliant, thanks.

Also, should the single usage of Hashtag be left as-is or translated as Mot-clé?
https://github.com/bluesky-social/social-app/blob/1096c8a7ebe79f8f2f98a4fa192963618fce57a7/src/locale/locales/fr/messages.po#L1666
For context, it's an accessibilityLabel:
https://github.com/bluesky-social/social-app/blob/8b0e575f6423575c08e9a6748be41c888611d631/src/components/RichText.tsx#L190-L191

There should always be a space before a colon in fr-FR, either a regular one (if you don't know how to input a non-breaking space one, or don't care to) or a non-breaking space one.
💡 Tip! If there are two parts for the typographic sign, there should a non-breaking space next to it in fr-FR. Works with !, ?, : and ;!

I've made some other minor changes which I hope should be self-explanatory, but if they look iffy to you please let me know.
I've also done a find-and-replace to add non-breaking spaces before !, ? and : and immediately inside the guillemets, but not between words in the guillemets. For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?
https://github.com/surfdude29/social-app/blob/5155a50f8e2847c64fe39f372b29e55d4b1f12dd/src/locale/locales/fr/messages.po#L1133
https://github.com/surfdude29/social-app/blob/5155a50f8e2847c64fe39f372b29e55d4b1f12dd/src/locale/locales/fr/messages.po#L4548-L4550

Also, should the (for now) single usage of Hashtag be left as-is or translated as Mot-clé?

I think we should always use mot-clé, to make sure it’s always consistent thorough the product (including accessibility labels).

I've also done a find-and-replace to add non-breaking spaces before !, ? and : (there aren't any ;) and immediately inside the guillemets, but not between words in the guillemets.

You did well! I just checked the diff and it looks perfect.

For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

It's correct! 👍

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?

I spotted the usage of dépôt and I think it's a good translation; it's already the one used by some Git-related software for repository—we even say it orally sometimes (I've already suggested to a colleague to check something directly on GitHub by saying Tu peux directement vérifier ça dans le dépôt GitHub, tu verras bien), which is one of the best proof of a good translation choice imho :)

Beside this change, I think this is good to merge.
Pinging @ansh about it; if it means anything, please consider this localization update approved by myself :D

Also, should the (for now) single usage of Hashtag be left as-is or translated as Mot-clé?

I think we should always use mot-clé, to make sure it’s always consistent thorough the product (including accessibility labels).

Makes sense to me 👍

I've also done a find-and-replace to add non-breaking spaces before !, ? and : (there aren't any ;) and immediately inside the guillemets, but not between words in the guillemets.

You did well! I just checked the diff and it looks perfect.

Great 👍

For example, in « For You » there is a non-breaking space before For and after You but not between For and You. Is that correct?

It's correct! 👍

👍

One other thing I wanted to double-check is the translation of repository, in the context of downloading your account data. DeepL suggested dépôt and I thought I'd go with that; do you think that will be understandable to most users in these contexts?

I spotted the usage of dépôt and I think it's a good translation; it's already the one used by some Git-related software for repository—we even say it orally sometimes (I've already suggested to a colleague to check something directly on GitHub by saying Tu peux directement vérifier ça dans le dépôt GitHub, tu verras bien), which is one of the best proof of a good translation choice imho :)

Hehe nice :)

Beside this last comment change (which is very minor) and the atténué one, I think this is good to merge.
Pinging @ansh about it; if it means anything, please consider this localization update approved by myself :D

Excellent, thank you so much @Signez! 😊

The .po files have just been updated, so I've merged in the changes and resolved the conflicts. I've also added translations for the handful of new strings, trying to follow previous translations, so hopefully they won't need too much fixing 🤞
@Signez: If you have a chance to take a look sometime that would be great 🙏

Looks good to me! 👍

Merci beaucoup @Signez ! :)

Thank you everyone!!

Thanks! 💫


How can i get tin?

sorry if this is dumb but im kinda new to Embers on its own and im not quite sure how to get tin in the heavens mod pack. can anyone help please?

nvm i figured it out i found some icestone

In Heaven's of Sorcery, tin nuggets can be made by placing Iron Dust, Icestone (found at lower altitudes in the Aether), and Mana Powder (made from Redstone tossed into a Botania Mana Pool), thrown into a pool of Wizardry Mana (made from putting Infused Pasture seeds into water in a Cauldron) consisting of at least six source blocks.


remove locales for removed authentication columns

The code that uses a number of our authentications columns has been removed.
We cleaned them up but this is one last pass to remove the locales (and the columns)
associated with the removed functionality.
see also https://github.com/ManageIQ/manageiq-schema/pull/599

The values in the en.yml are just column names, so we can remove it when there are no more columns in any table.  e.g. if public_key doesn't exist in any table, then it can be removed from here, but if it exists in another table aside from authentications, then it has to stay.

Aside, I've never understood why 95% of the entries here exist since they could easily be defaulted to what .titleize returns.  I've never had a chance to dig into why the code requires an entry here.  It might be because of the way the .yml lookup occurs with layering of languages (i.e. if someone provided a German translation, we don't want that bleeding into English as the default).  Ideally, we would only have the exceptions here and that's all.

The values in the en.yml are just column names, so we can remove it when there are no more columns in any table. e.g. if public_key doesn't exist in any table, then it can be removed from here, but if it exists in another table aside from authentications, then it has to stay.

I highlight in ManageIQ/manageiq-schema#599 each column and their usage. It looks like Endpoint#certificate_authority is the only column that is still in use, thought login and public_key are suspect.
We can focus on that PR and then this one will just flow out of that conversation.

Aside, I've never understood why 95% of the entries here exist since they could easily be defaulted to what .titleize returns. I've never had a chance to dig into why the code requires an entry here. It might be because of the way the .yml lookup occurs with layering of languages (i.e. if someone provided a German translation, we don't want that bleeding into English as the default). Ideally, we would only have the exceptions here and that's all.

I think it may be easier to just have all the fields defined. In code it is tricky to know the difference between something unintentionally missing and something intentionally left out.

failure will be resolved when the associated schema PR is merged

doesn't locale/en.yml get generated by an i18n rake task?

@chessbyte I don't believe so, no - it should be autogenerated or not generated at all, IMO.


release x86_64-pc-windows-msvc with openssl dependency is failing

Is there a way to cope with openssl? Build release ends with
  Configuring OpenSSL version 1.1.1t (0x1010114fL) for VC-WIN64A
  Using os-specific seed configuration

  --- stderr

  ******************************************************************************
  This perl implementation doesn't produce Windows like paths (with backward
  slash directory separators).  Please use an implementation that matches your
  building platform.

  This Perl version: 5.32.1 for x86_64-linux-gnu-thread-multi
  ******************************************************************************
  thread 'main' panicked at '

  Error configuring OpenSSL build:
sl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-asm" "VC-WIN64A"
      Exit status: exit status: 127

Can you provide some context to this error please?

I'm trying to use this Dockerfile with only one difference I built it from the latest docker.io/library/rust:1.69.0-slim-bullseye.
It's a famous issue when some projects have a dependency on openssl. This is the recipe that I added https://github.com/cross-rs/cross/wiki/Recipes#openssl
openssl = { version = "0.10", features = ["vendored"] }

and to the Dockefile
dpkg --add-architecture i386
apt-get update && apt-get install --assume-yes libssl-dev:i386

I'm trying to build Windows exe from linux OS.
The last log is:
 ....
error: failed to run custom build command for `openssl-sys v0.9.80`

Caused by:
  process didn't exit successfully: `/app/target/release/build/openssl-sys-18c84857cbf9c662/build-script-main` (exit status: 101)
  --- stdout
  cargo:rustc-cfg=const_fn
  cargo:rustc-cfg=openssl
  cargo:rerun-if-env-changed=X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR
  X86_64_PC_WINDOWS_MSVC_OPENSSL_NO_VENDOR unset
  cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
  OPENSSL_NO_VENDOR unset
  running cd "/app/target/x86_64-pc-windows-msvc/release/build/openssl-sys-9377103229a86659/out/openssl-build/build/src" && "perl" "./Configur
e" "--prefix=/app/target/x86_64-pc-windows-msvc/release/build/openssl-sys-9377103229a86659/out/openssl-build/install" "--openssldir=SYS$MANAGE
R:[OPENSSL]" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-asm" "VC-WIN64A"
  Configuring OpenSSL version 1.1.1t (0x1010114fL) for VC-WIN64A
  Using os-specific seed configuration

  --- stderr

  ******************************************************************************
  This perl implementation doesn't produce Windows like paths (with backward
  slash directory separators).  Please use an implementation that matches your
  building platform.

  This Perl version: 5.32.1 for x86_64-linux-gnu-thread-multi
  ******************************************************************************
  thread 'main' panicked at '

  Error configuring OpenSSL build:
      Command: cd "/app/target/x86_64-pc-windows-msvc/release/build/openssl-sys-9377103229a86659/out/openssl-build/build/src" && "perl" "./Con
figure" "--prefix=/app/target/x86_64-pc-windows-msvc/release/build/openssl-sys-9377103229a86659/out/openssl-build/install" "--openssldir=SYS$M
ANAGER:[OPENSSL]" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-asm" "VC-WIN64A"
      Exit status: exit status: 127

      ', /usr/local/cargo/registry/src/github.com-1ecc6299db9ec823/openssl-src-111.25.0+1.1.1t/src/lib.rs:499:13
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...


Rack awareness tenant assignment.

If pinot servers joined with rack info. When creating tenant, we can do rack awareness assignment other than random pick.

It will be good to do this. However we should also take into consideration for future about placing replicas based on load on pinot-servers as well. Rack awareness should be not prohibit us from doing a load balancer type of feature in the future.

is it a good time to start using Helix algo's for placement. Lei just added zone/rack aware placement strategy in Helix.
Ravi -regarding placement based on load,
there are two options

look at the load during initial placement  ONLY
periodically change the mapping if the load has changed.

Are you suggesting both #1 and #2?

I am suggesting 2. But it can wait. Mainly to make sure that design can
accommodate this in the future
Thanks
RaCi
On Thursday, September 1, 2016, Kishore Gopalakrishna <
<EMAIL_ADDRESS>wrote:

is it a good time to start using Helix algo's for placement. Lei just
added zone/rack aware placement strategy in Helix.
Ravi -regarding placement based on load,
there are two options

look at the load during initial placement ONLY
periodically change the mapping if the load has changed.

Are you suggesting both #1 https://github.com/linkedin/pinot/pull/1 and
#2 https://github.com/linkedin/pinot/pull/2?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/linkedin/pinot/issues/438#issuecomment-244184902, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADSJ7jLYl-IHuuohZ33w31UQ8nfixXQrks5qlyZ4gaJpZM4JsuOX
.


Fix storm-sql readme to reflect improvement of submission (STORM-2016)

Since we merged STORM-2016 to master and 1.x branch, we can run storm sql easier than before. This doc change reflects the new way to submit.
This can be merged into master and 1.x-branch.

Merging this since this is a non-code change. Will also reflect to website.

Cherry-picked via 0b080fcf63ad6dad52c654e059f2493599df1d67 (master) and a3090d3135d6c33c2802692cb9f7bc4c0e889937 (1.x-branch).
Also updated storm-sql documentation on the website for 2.0.0-SNAPSHOT.
Closing.


Fixed background not resizing with output

Coverage increased (+0.007%) to 57.846% when pulling a606115de38a44c2cd11f497e6a271b9379cdce3 on background-resize-hotfix into b3b8818d40b70f9a261da6cc7c331f1ca4dd6563 on master.


Direct link to Gym/stop/monster should not respect filter

If someone gets a notification in Poracle the direct link should open the requested resource.
Actually it only shows the exact location, but without content/icons, because filter does not load the specific gym/stop/monster because filter does not match.

that would very nice


Addon TMDB Spanish Bug Report: Missing Movie Information on Mobile, TV Box, and Smart TV with TMDB Configured in Spanish

Good to all, first of all congratulations and thanks for this great Addon which is helping us a lot to use Stremio to all the Spanish community of Stremio.
As a spokesman I want to comment a Bug that we are suffering and which is somewhat curious.
The problem comes with TMDB configured in Spanish, it turns out that when we open a movie on my Mobile, Tv Box or Smart Tv, I do not see the Score, nor the Trailer or the cast, writer of the film.
At first we thought it was because this information is not available in Spanish, but it turns out that if we open the same movie with TMDB Esp on the Windows computer or in the browser if all this valuable information appears for us.
However when we open a series on a Mobile, Tv Box or Smart Tv then if all the information appears well structured and in Spanish; trailers, score, cast, writer.
The Spanish Stremio community would be very grateful if you could solve this "Bug". Thanks for your work.

This is Stremio issue. Addon and TMDB API work perfectly fine. You should try updating stremio to the latest version and clearing cache. If this helps with your issue, consider checking this as resolved.

The bug has been reported to the dev team. We expect to have this resolved in upcoming core updates.

I've installed and de-installed and configured this addon several times, but this addon does not work at all with Spanish metadata on the Nvidia Shield.
When I install this addon in the windows Desktop version, it initially works, but only to display Spanish descriptions on the "Discover" screen in Stremio. But as soon as I switch to the Home screen, none of the Spanish translations appear anymore, and then even the translations on the Discover screen revert back to English permanently.
Have you already confirmed this bug will be fixed in the next core update? If so, do you have an estimated timeline for that? Thank you.

This is a Stremio core bug and we expect it to be resolved in one of the next updates.
You said something about the homepage. If you have Cinemeta, popular and featured will be their catalogues and displayed in English, same as the Cinemeta. When you get to discover, you have to choose TMDB catalogues before you search. The problem could be resolved only if you removed Cinemeta from your Stremio installation and replaced it with TMDB, but it might result in the app breaking if done incorrectly.

The bug has been reported to the dev team. We expect to have this resolved in upcoming core updates.

Thank you very much @oleglucic for reporting the problem to Stremio, it is true that in v3.0.15 of the Addon this problem was solved to 5% and with v3.0.16 has been solved to 70/80%, most movies already have all the info, but there is still 20/30% of movies where only the description appears, without rating, or trailer, etc..
Thanks for your understanding and help.

I believe this is a bug in the stremio android client, it has already been reported to the team.
https://github.com/Stremio/stremio-bugs/issues/993


feat(frontend): type util for Optional and Nullable types

Motivation
Created common wrapper type for T | null | undefined.

Before sending to review, I wait for PRs:

PR #2327

@peterpeterparker I know there are many files changed, but theoretically it is just substitution

Can you create an eslint rule that make the usage of Option mandatory if | null | undefined is used?

Done with PR:

#2341


Normalize EVEMonDevelopmentTeam.EVEMon 4.1.3

null
Microsoft Reviewers: Open in CodeFlow

@wingetbot run