translate selection to selected language directly without having to choose

Currently when one uses the translate selection to selected language command, a modal pops up.
Having to click the modal or press return is a pain when doing many translations in a row.
I would like a command that just translates directly into the last language used.
Thanks.

Many thanks for the feedback!
I'm thinking of renaming the current Translate selection to selected language into Translate selection (select language), and adding a new command called: Translate selection (specific language).
This command would have an option under the Functionality settings that allows you to set which language it should translate to. The options would be as following:

Last language used: every time you execute a translation command, the target language will be saved to the settings, and used whenever executing the Translate selection (specific language) command - if none is set, it will run the Translate selection (select language) instead.
Display language: always translate to Obsidian's display language
Custom language: always translate to user-specified language

Would this solution work for you? The only problem with this, is that user could get confused between Translate selection (select language) and Translate selection (specific language). I'm not entirely sure how to solve that.

@ksdavidc, I've tried implementing above functionality. Below you can find a pre-release for the feature. Please let me know what you think.
https://github.com/Fevol/obsidian-translate/files/10387656/translate.zip

Many thanks for the feedback!

Likewise. I think the implementation you are suggesting is quite good, but agree some confusion is possible. Comments below.

I'm thinking of renaming the current Translate selection to selected language into Translate selection (select language), and adding a new command called: Translate selection (specific language).

"select language" is okay, but I feel it could be better somehow. (for one, the word select and selection are a bit similar, but the difference in meaning is significant.)
Some ideas:
Translate selection (choose language via modal)
Translate selection (choose language from list)
"Specific language". I considered specified, but I think it falls for the same reason as above. Why not use default?
Translate selection (default language)

This command would have an option under the Functionality settings that allows you to set which language it should translate to.

I suggest calling this the default language, or command custom default
I know you use a "default" source and target language for the translation view already. I suggest renaming as follows:
Translation View Defaults:
Source Language
Target Language
Command Custom Default Language
maybe "Hotkey Command Default Language"? not sure if that is accurate.

The options would be as following:

Last language used: every time you execute a translation command, the target language will be saved to the settings, and used whenever executing the Translate selection (specific language) command - if none is set, it will run the Translate selection (select language) instead.
Display language: always translate to Obsidian's display language
Custom language: always translate to user-specified language

Would this solution work for you? The only problem with this, is that user could get confused between Translate selection (select language) and Translate selection (specific language). I'm not entirely sure how to solve that.

Good choice of options. I suggest a 4th option "same as translation view target language". I can imagine wanting to always translate into whatever language is being used in the translation view. Or having a fixed, "command custom" language.
Maybe Custom language could be "command custom language".

@ksdavidc, I've tried implementing above functionality. Below you can find a pre-release for the feature. Please let me know what you think.
Be aware that it may be quite buggy in places, I'm testing out an unreleased component of the API, and some code could definitely be improved. https://github.com/Fevol/obsidian-translate/files/10387656/translate.zip

I appreciate your sending the zip file. Other than using BRAT, I don't know how to use a pre-release...

Okay, I just copied the unzipped folder into a blank vault and it seems to be working. I hope that is the correct way. Instead of hotkey, I guess global might be the word, but global sounds as if it supercedes Translation View....

Tested and working fine. Looking forward to when you have the kinks out because I have need of it!!! Good job!

FYI. I tried copying the unzipped folder into my actual work vault (bad bad bad) and it didn't work. The settings for the various languages were blank pages, but the general settings were okay. It did work in the generic vault, though. Reinstalled the latest release but strange that it worked in one and not the other...

I'm really grateful for all the responses, they help me immensely! Based on your feedback, I've made a newer test version - though some of the other suggestions will take me a while longer to implement. I'm going to be pretty busy with work for the next two weeks, so I'll mainly be focusing on fixing critical bugs whenever they pop up.
Plugin zip with incorporated suggestions: https://github.com/Fevol/obsidian-translate/files/10392143/translate.zip

"select language" is okay, but I feel it could be better somehow. (for one, the word select and selection are a bit similar, but the difference in meaning is significant.)
Some ideas:

Translate selection (choose language via modal)
Translate selection (choose language from list)

"Specific language". I considered specified, but I think it falls for the same reason as above. Why not use default?
Translate selection (default language)

Agreed, Translate selection (choose language) and Translate selection (default language) are much better descriptors for the command, changed them.

I know you use a "default" source and target language for the translation view already. I suggest renaming as follows:
Translation View Defaults:

Source Language
Target Language

Global/Hotkey/Custom Defaults:

Command Custom Default Language

maybe "Hotkey Command Default Language"? not sure if that is accurate.

Personally, I think it is fine if the default target language is used for both the translation view and the target language for the translate command, as they fulfill the same uses. Making them separate would introduce unnecessary bloat to the already rather messy settings.
Though your suggestion of separating the translation view and 'global' settings is very helpful. I'm really not happy with the fact that the current settings are a mishmash of settings that apply only to the 'global translator' (i.e. the one used for the commands), settings that only apply to translation views, and both. I'm going to have to think about this for a while.

Good choice of options. I suggest a 4th option "same as translation view target language". I can imagine wanting to always translate into whatever language is being used in the translation view. Or having a fixed, "command custom" language.
Maybe Custom language could be "command custom language".

While it is technically perfectly possible for me to add that option, I'm not sure if it would make intuitive sense to the users: you can have multiple translation views open at the same time, each with a different target language, so how do you determine which one of those to use? The last view that was focused? The last view that actually executed a translation request?

I appreciate your sending the zip file. Other than using BRAT, I don't know how to use a pre-release...

Ah yeah, the zip I've sent you is more of a pre-pre-release, it's faster (& much more convenient) for me to just compile the plugin, than to make a beta release for it.

FYI. I tried copying the unzipped folder into my actual work vault (bad bad bad) and it didn't work. The settings for the various languages were blank pages, but the general settings were okay. It did work in the generic vault, though.

Agh, sorry for that! If you're talking about the Functionality settings having a blank page, that means that an error occurred while loading it. Whenever that happens, make sure to open the devtools (Ctrl/Cmd + Shift + I) to see where it is giving an error, and share it with me.

Please take everything below with a grain of salt. I will be pleased no matter what you do, but now that I am here I'll offer my views directly.

I'm really grateful for all the responses, they help me immensely! Based on your feedback, I've made a newer test version - though some of the other suggestions will take me a while longer to implement.

Thanks. Will try it when I get the chance.

I'm going to be pretty busy with work for the next two weeks, so I'll mainly be focusing on fixing critical bugs whenever they pop up.

No worries. I understand. Take your time. I know it must have sounded like I was rushing you, but I was just expressing zeal...

Agreed, Translate selection (choose language) and Translate selection (default language) are much better descriptors for the command, changed them.

Sounds good!

Personally, I think it is fine if the default target language is used for both the translation view and the target language for the translate command, as they fulfill the same uses.

I understand what you are saying. For me, the two modes don't quite "fulfill the same uses". My use cases might be unusual, but it might make things concrete if I share them.

I sometimes create a presentation in English for which I like to have a translation in my text for reference. This doesn't need to be so accurate so a first-order translation is good enough. Also, I have a macro that takes an individual line and copies it and provides a translation underneath my original. The macro calls the command at one point, and because it is a macro having to press enter interferes with the flow in the macro, so it would be nice if there were a command default. Having the command default be my second language is good here.
Secondly, I often take notes from texts in my second language that I want to translate into English. I usually use the translation view (tabbed into the sidebar) to translate into English, and then I extract relevant information into my notes. Here I repeatedly use the same target (English), so it is nice if my default translation view is into English.
Sometimes, I create a short report in the target language. Here I am aiming for a more accurate translation, so I try to get a higher order translation. I use the translation view (snapped into my right sidebar) to take my English, translate it, then I use the switch button to bring the translation into the source panel, and then translate again to see how well my translation translates. Rinse and repeat until the original and final are a good match, and I paste the final result into my report. (You know the old joke: Out of sight out of mind -> target -> blind fool) Here I am going back and forth.

Though your suggestion of separating the translation view and 'global' settings is very helpful. I'm really not happy with the fact that the current settings are a mishmash of settings that apply only to the 'global translator' (i.e. the one used for the commands), settings that only apply to translation views, and both.

I see your point. To be honest, I don't understand fully at this point all your settings and it took me a while to suss out that there were even two things involved. That said, I think it clear for me to have two modes, maybe call them view mode and command mode, and each has a target and source default. The symmetry here would ease comprehension. I was originally going to suggest it that way, but then I realized that admittedly the command default source language might not be so useful, since autodetect works. On the other hand, as I keep thinking about possible use cases, it might in cases when languages are mixed in a document and autodetect doesn't work. Again, I think if the settings are symmetrical, then it becomes easy to understand. It is the asymmetry that confused me I think.
Now my gears are turning. This is probably not the direction you are taking, but this is how I think, naively and crudely, and without knowing the details of how it is coded. You should do what is best for you, but I put it out here since it came to me. The guiding principle is as much symmetry as possible.
View Mode
source language: options: auto (the default), last with default to auto, display, custom, same as last used other mode*, same as other mode setting**
target: last (tied to the individual window), display (the default?), custom, same as last used other mode, same as other mode setting*
Command Mode
source language: options: auto (the default), last with default to auto, display, custom, same as last used other mode*, same as other mode setting*
target: last(? once you decide what that means for command)*, display (the default?), custom, same as last used other mode, same as other mode setting
Target and command are essentially the same, except, the tricky bits (that I see):

the workflow here is you start using one mode, then decide to jump into the other mode, but it maintains your state across modes...that could be another name for it, "maintain state across modes"
** "Same as other mode setting" should only be available in one mode at a time. This would allow both to work identically, but have one or the other be the master.
***Command mode target: last. What does that mean? see below

you can have multiple translation views open at the same time, each with a different target language, so how do you determine which one of those to use?

Good point. I hadn't considered that situation, since I usually have only one view open at a time. I was thinking of a modified 3rd use case from above where I am sometimes going from one language to another for a few rounds, then in reverse for a few rounds in both the translation view and my note document. I was thinking last (hotkey initiated) translation request, in fact, but your point is valid.

If you're talking about the Functionality settings having a blank page, that means that an error occurred while loading it. Whenever that happens, make sure to open the devtools (Ctrl/Cmd + Shift + I) to see where it is giving an error, and share it with me.

Actually, it wasn't the functionality settings, but the settings for the individual translators (all of those). Sorry I forgot check for errors. I was rushing through it as I was trying to get work done at the same time..will do next time. :-)
Was about to send and another thought came to me:
If I were doing this (admitedly :-D I am not) and I was really intent on user-friendliness I would create some presets for different workflows, like the workflows above, and the user could just tick a box in the settings that would preselect all four cases for that workflow. Taking that further, the user could create their own custom modes.... Okay, you must really hate me by now, but really, I mean it all in the friendliest spirit. Don't take me too seriously, take your time, and carry on as you would normally. Ignore anything that doesn't suit you and I will take no umbrage whatever you do. I am already more than satisfied with what you did...

Tried out the second zip. Last used setting worked perfectly for the command and it was great for my workflow. Thanks.
Some observations...though I imagine you are still working on it and maybe it will all come out in the wash.
I expected last used would also do the same for the view mode, but it appears not, at first glance. My expectations could be wrong.... It appears to be using the last language I selected when I "manually selected", not the last language I used....or something. I need to do further testing.
It was odd when choosing "manually selected" to have another setting suddenly appear (sans indentation to show it was a subheading). I wasn't sure what this "manually selected" meant. Did it mean that I would get some kind of an option to choose from when translating (not sure that would make sense), or (as it appears) that I would have to choose from one of the options below...this is the custom default we talked about, I think, but that didn't seem to work for translation view. When I opened a new translation view, I got a different language and it stayed at that language no matter what other languages I used it for. Sorry not a very good explanation. I didn't properly test it, but something was odd.
Again, this is probably just me, but my intuition read the text below the heading as being an explanation of the setting in general, not as an explanation of the particular setting. Because one has to select to see the options, I didn't understand there were other options at first (I thought you had eliminated them somehow). I think this might be confusing for new users.

can't give a full response, but looking good. I'll share some thoughts once I can.

Tried out the new zip, then I noticed the update, and went with that. Working fine. I like the settings...putting default at top is very good!

...This entire discussion has been a delight to me, and I'm extremely thankful for the time you've spent adressing issues, offering up ideas and describing your workflow. I really cannot overstate how much it helps me with making design choices and what functionality is actually important.

I am glad to hear that.

...I've been thinking about how to implement an action/view where the user can compare their original text with the translation (see also issue #34), be it a single selection, or an entire note. Not sure how I would implement it, but one solution (and perhaps the simplest conceptually) is to just add a View original text button next to what was translated before, which will disappear after x amount of new translations were made.

This is cool. It's a nice touch. For me, though, the problem is how do I act on the information in the case of a mistranslation. For example, let's say I click on the button...I see the original text. For me this isn't so useful because I wouldn't be able to detect the discrepancy, but I can see it might be useful.
I am interested in comparing my original text with the translation of the translation. I know it is silly, but it works in my situation. I can think of two ways to get at that. One is in view mode to have an optional/collapsible 3rd window that can be set, when open/activated, to do the second translation. This would allow for tweaking the original to get rid of mistranslations.
I am not sure if something like that could work in your button scenario. I imagined a second (optional) button that would show the second level translation. The user could undo to try again if they want. Of maybe it would copy the 2nd level to the clipboard...isn'T quite clear for me yet.

The main issue with this workflow, is that I want to avoid adding any type of metadata to notes, unless I really have no other options. So for comparing translation and original, everything would have to be stored temporarily by the plugin itself.

I don't understand this clearly. If you think it is relevant, I might need a little explanation of what metadata means in this context.

Personally, I think it is fine if the default target language is used for both the translation view and the target language for the translate command, as they fulfill the same uses.

For me, the two modes don't quite "fulfill the same uses". (...) I usually use the translation view (tabbed into the sidebar)

You're absolutely right, the two different usages of the default target language setting are not the same, though I should probably clarify what I meant by that. Concretely, the default target language is used in three places:

Whenever the user executes the Translate selection (default language) command or clicks the 'Translate' button in the editor context menu, this language will be selected as the target language for the translation
Whenever the user executes the Translate selection (specific language) command, translates a note, or translates via the context menu, this language/these languages will appear at the top of the selection
Whenever a new translation view is opened, this language will be set as the initial target language for said view, and only then - existing views will never have their target language replaced by the default one

So when I say that they fulfill the same uses, I just meant that in the sense that when the user executes the Translate selection (default language) command, or opens a new translation view to quickly translate a few things, you'd want it to be the language that you're most likely to translate to (i.e the default target language). (So, if the translation view is a core part of the user's workspace & they never close it, then the setting wouldn't matter that much to them.)

I see. I think for me, I would use 1  and 2 and 3 in different ways, for different purposes:

quickly/directly translating given text in a document, or using it as part of command sequence (via templater, for example)
situations where I am not using my default/most used language
situations where I want to examine the output in more detail or where I am not actually trying to insert the translation in my document

My point was that the "default", aka the language I would often use, might not be the same in all 3 cases.
HOWEVER,  I fully understand this is overly complicated, and maybe really beyond the scope of what you ought to try to accomplish. It has downsides (is this the metadata you are talking about?), and so I am just dreaming...

I don't understand fully at this point all your settings and it took me a while to suss out that there were even two things involved

I appreciate you saying that, it's a clear sign that the design of the settings needs to be overhauled completely.

IT might be because we've been talking about it so much, but it does seem much better now and the added context you provide is helpful.

I realized that admittedly the command default source language might not be so useful, (...) On the other hand, as I keep thinking about possible use cases, it might in cases when languages are mixed in a document and autodetect doesn't work.

Even when multiple languages are mixed in a document, the autodetect will almost always perform better than setting the source language manually. For text where multiple languages are mixed in, it is a non-trivial (probably impossible) task¹ to properly translate every language individually, and still producing a readable/flowing output sentence.
¹ Unless the languages are separated per paragraph/sentence, where this is a slightly more manageable issue

Point well taken. I wasn't really thinking about trying to translate mutliple languages concurrently. I meant trying to isolate out one particular language. I have once or twice, as you imply, not in general, found it helps if I turn off autodetect...it depends on the service. But you are quite right...at any rate, target is what concerns me.

Again, I think if the settings are symmetrical, then it becomes easy to understand. It is the asymmetry that confused me I think.

I fully agree with you here! I'll definitely take that into consideration when revamping the settings.

View Mode
...
Command Mode
...
Target and command are essentially the same, except, the tricky bits (that I see):
1 the workflow here is you start using one mode, then decide to jump into the other mode, but it maintains your state across modes...that could be another name for it, "maintain state across modes"
2 "Same as other mode setting" should only be available in one mode at a time. This would allow both to work identically, but have one or the other be the master.

These are very good suggestions. I'll have to try implementing it first to see how it feels, but there are two problems with the 'default language' system that I'll first need to figure out:

If the user selects a specific language (be it source, or target), there is no guarantee that said language will actually be available for the service they're using. When it is not available, what should happen? Error message? Automatically set to auto/display language for the source/target language respectively? I've skirted around this issue until now, but there definitely needs to be a proper solution for this

excellent point. I can see how it would get dicey. I think it depends on where in the process we are. For example, if they are in the settings, choosing a default, then I would imagine you would limit to the just the currently avaiable languages. If you are changing hte service, then I think you would have to prompt the user to select a new language? Very ugly. Generally you don'T want ot make assumptions for the user. Would you be able to account for all possible sources of conflict and resolve them all. I see the problem. And that is without even taking into account the logistics of coding it.

For default source language specifically, it would always be better to use automatic language detection than to select a specific source language. However, the Bergamot service does not come with automatic language detection, and I cannot assume that the user would have installed FastText, which normally would implement this.²

² Though, maybe I really should automatically install FastText whenever the user installs Bergamot, that should hopefully reduce the initial set-up confusion.

What are the downsides of this?

I expected last used would also do the same for the view mode, but it appears not, at first glance. My expectations could be wrong.... It appears to be using the last language I selected when I "manually selected", not the last language I used....or something. I need to do further testing.

You're right, it indeed keeps using the last manually selected language (defaults are only used on opening a new view). It should be pretty easy to add an option to the translation view's dropdown like: Last used language, though I don't know if that is practically useful, since the only way you would be able to set that the 'last used language', is to execute translation commands - so why use the translation view then?

I think it would be useful in the case where you have a master mode and slave mode. The slave would use whatever the last language chosen was. Another mode would tie them to each other. change the language in one changes the language in the other, but the last used one is the master for the other.
(I think. Maybe I am missing something...)

It was odd when choosing "manually selected" to have another setting suddenly appear (sans indentation to show it was a subheading).

Some very good points! I didn't realize it myself, probably because I'm used to this mess, but it's indeed visually unclear which settings are normal settings, and which depend on another setting being set to a particular value.
For now, I've indented all settings that are considered 'subsettings', but I'll need to find a better representation, since that won't work well on mobile platforms.

It looks good now. On mobile can you put an arrow symbol?

I wasn't sure what this "manually selected" meant. Did it mean that I would get some kind of an option to choose from when translating (not sure that would make sense), or (as it appears) that I would have to choose from one of the options below...

Again, this is probably just me, but my intuition read the text below the heading as being an explanation of the setting in general, not as an explanation of the particular setting. Because one has to select to see the options, I didn't understand there were other options at first (I thought you had eliminated them somehow). I think this might be confusing for new users.

I've tried fixing the styling and rewriting the descriptions a bit, it looks like this now:
Admittedly, I struggle a lot with finding concise but clear settings descriptors, hopefully it should be a bit more clear now with the current default language being provided directly in the description, but let me know if (and how) I could improve it further!

It is much better, and I was probably quibbling too much. It is much easier to understand for me now, so I really appreciate your attention and thoughtfulness on it. I am an amateur and no expert, but you've listened very conscienciously and given my suggestions their full due. I really appreciate, as someone who is using this plugin several times a week, that someone has taken the time to address my complaints so generously and pleasantly. I hope you are having a great day, and am looking forward to seeing where it ends up! Cheers...D

I'm sorry for not being able to reply sooner, it was a pretty busy period these past few weeks, but I'm finally able to spend more time on plugin development again!

I am interested in comparing my original text with the translation of the translation. I know it is silly, but it works in my situation. I can think of two ways to get at that. One is in view mode to have an optional/collapsible 3rd window that can be set, when open/activated, to do the second translation. This would allow for tweaking the original to get rid of mistranslations.

If I understand correctly, you usually translate your text twice, i.e: from X -> Y -> Z, and after translating from X -> Y, you'd like to have the option to open a 3rd text input field to (manually?) do the translation from Y -> Z in, while also being able to see original inputs X and Y?
If so, I maybe have an idea that should be a little bit easier to implement, but also allows that workflow: chaining translation views.
Say I have two translation views AX->Y and BY->Z, you'd have the option to chain B to A, essentially linking those two views; this would do the following:

Changing the target language of A from Y to O, will automatically change the source language in B from Y to U likewise. [i.e.: AX->Y and BY->Z becomes AX->O and BO->Z]
When translating any text in A, its output will automatically be set as the input for B

Apologies if this is not what you envisioned, this is what came to my head when reading your use-case.

I don't understand this clearly. If you think it is relevant, I might need a little explanation of what metadata means in this context.

In this case, I see metadata as the plugin storing the original text of the translation in some form, such that it can be retrieved at a later point for comparisons/reverting translations/.... It's not strictly relevant per se, just something I'm thinking about if I were to implement a 'Show original text' action at some point.

² Though, maybe I really should automatically install FastText whenever the user installs Bergamot, that should hopefully reduce the initial set-up confusion.

What are the downsides of this?

Not too many, except that I intended for the FastText service to be a separate service, that users can install if they want to do so, though I guess I could provide that option by opening a modal whenever the user installs the Bergamot service, to ask if they also would like to install FastText.

Not sure which of the aforementioned things I'll be implementing for the next update; there are many ideas floating around in my head, plus I'd also like to get started on two other plugin ideas I've had for a while.

Changing the target language of A from Y to O, will automatically change the source language in B from Y to U likewise. [i.e.: AX->Y and BY->Z becomes AX->O and BO->Z]
When translating any text in A, its output will automatically be set as the input for B

Yes, very nice.

I don't understand this clearly. If you think it is relevant, I might need a little explanation of what metadata means in this context.

In this case, I see metadata as the plugin storing the original text of the translation in some form, such that it can be retrieved at a later point for comparisons/reverting translations/.... It's not strictly relevant per se, just something I'm thinking about if I were to implement a 'Show original text' action at some point.

Having some kind of stored text memory (like a button that would save the text) available would be useful. One thing I often do is tweak my original text a few times to get the double translation right. Being able to store an original result would help in having a place to return to once I have made my tweaks, to see what I changed, or compare to my original.

... I intended for the FastText service to be a separate service, that users can install if they want to do so, though I guess I could provide that option by opening a modal whenever the user installs the Bergamot service, to ask if they also would like to install FastText.

For me, having it optional is fine is not a problem. People like to have control. Knowing that one difference is that it offers autodetect makes me want to install it, but some might not need that.
These are good ideas, and I'd be excited if you implement them, but let me add that even as it is, the plugin is working nicely for me and I am happy with it. Keep up the good work!


Java exec format error when running amarr on portainer

Amarr Apparently runs ok when I deploy the container in portainer, but soon after  exits with this error:
    exec /usr/local/openjdk-17/bin/java: exec format error

This is my configuration file:

version: "2.1"
services:
amarr:
image: vexdev/amarr:latest
container_name: amarr
environment:
- AMULE_HOST=<IP_ADDRESS>
- AMULE_PORT=4712
- AMULE_PASSWORD=xxxxxx
- AMULE_FINISHED_PATH=/finished
- AMARR_LOG_LEVEL=INFO
volumes:
- /var/lib/docker/volumes/amarr:/config
- /media/HDD/Media/downloads/complete:/finished
ports:
- 8080:8080
Am I doing something wrong?
Thanks in advance.

Should be fixed with version 1.6.0 released with arm support (#83 ) please re-open if not working.

I weren't aware that arm wasn't supported. Anyway, I moved to an i386 minipc and amarr is running ok, so I can't test it in arm anymore. Thank you.


The simulators' background are same when choosing RGB(222,222,222) and RGB(0,0,0)

Describe the bug
The simulators' background are same when choosing RGB(222,222,222) and RGB(0,0,0)
Steps to reproduce the behavior

Navigate to https://arcade.makecode.com/beta#editor
Click "Scene" in tool box -> drag block "set background to" -> choose RGB(222,222,222) and RGB(0,0,0)

Expected behavior
The simulator's background should be different
Actual behavior
The simulators' background are same when choosing RGB(222,222,222) and RGB(0,0,0)

Desktop (please complete the following information)

OS: Windows
Machine build: 17763.1.amd64fre.rs5_release.180914-1434

Additional context

arcade version:  0.2.24
Microsoft MakeCode version:  5.2.13
repro on Chrome, Firefox, Edge and IE

Fixed


Changed a further occurence of State A into solid, and so on

In my previous pr I missed another occurence of State A.

Looks good, except there are two places where you now have a dictionary with duplicate keys. E.g.,
states = [
    State(name='solid'),
    'liquid',
    { 'name': 'gas', 'name': 'plasma'}
    ]

This won't work; the plasma state needs to be a separate element in the list. You could do [ ... {'name': 'gas'}, {'name': 'plasma'} ... ], which would work fine. If you can change that, I'm happy to merge this as well. Thanks!

Thanks!


Add new wrapperStyle prop for styling wrapping View component

I needed to style the wrapping View component to enable my flex based layout to work, so thought I'd offer this up as a PR so others can do likewise.

Hey Fred,
Thanks a lot for making this PR, very clean.
Let's merge this, I'm sure this can be helpful to others!
Have a great day

Totally welcome, thanks for this repo, it was the third tooltip lib I've tried and definitely the best of the lot.


Adding the Labels :

🎮 feature Request
You have not labelled the issue for the GSSoC 24, according to which any contribution will not be counted as for the scoreboard
Point down the features
Labels like
GSSoC
Level 1
etc
Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

@anythingkartik Could you please explain more what you want to do, we have already levels & gssoc batch

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

Thank you, you have added the labels


Sphinx Docs

We should start using sphinx.

+1 for this, I was looking for the documentation link in the readme. Took me some time to figure out there is none :)

Yeah proper docs instead of a huge readme might be a good improvement.  It just kind of grew that way.

We have docs now! https://vcrpy.readthedocs.org/en/latest/


ARXIVNG-298 ARXIVNG-301 improvements to advanced search form

Coverage decreased (-0.2%) to 65.406% when pulling dcc68b5591ccb7c3d72b4bac262939e342dffa7f on feature/ARXIVNG-298 into ca2c0a8f85c6c42c922d18fefd42d16e61f3ea79 on develop.

Adds focus triggers for physics category, specific year, date range filter options.

Addresses #69

Resolves #46


Update CHANGELOG

The changelog could do with some ❤, it's a really useful tool to know what's changed with new versions!

@brendo thanks for pushing me! 👍

No thank you :)


[YouTube] Get the list of IDs of the recommended videos of a video

Checklist

[x] I'm reporting a feature request
[x] I've verified that I'm running youtube-dl version 2020.09.20
[x] I've searched the bugtracker for similar feature requests including closed ones

Description

I'd like to retrieve the list of IDs of the suggested/recommended videos of a certain video (the ones shown on the right side in the desktop page). As it stands these are updated as we scroll through, so even just having the ones appearing at the page load would be great (I believe there are about 20).
The list of IDs could gets added by default to the JSON dump obtained with -j, or it could be a new simulation option --json-related or similar.

I'd like to work on a PR for this (first time contributor).

Seems like no progress has been made on this issue; @vishnunair6 and I would like to begin work on this issue!


Mogenius not responding ever after waiting several minutes

Hi team,
I tried the playground for Omniparser to try out schemas but the screen is stuck and not responding for several minutes.
Can you have a look at it?

Unfortunately both haroku and mogenius get rid of free tier and I'm in search for another hosting solution.
In the mean while you can clone the repo and use ./cli.sh to test out schemas and inputs.


Javascript-goodies wiki page has probably a problem

Hello @apneadiving,
By following this link on http://stackoverflow.com/questions/14054628/typeerror-gmaps-map-is-undefined
This wiki page seems it had been erased :
https://github.com/apneadiving/Google-Maps-for-Rails/wiki/Javascript-goodies
Is it normal ? Here the diff :
https://github.com/apneadiving/Google-Maps-for-Rails/wiki/Javascript-goodies/_compare/83a2c51b54eb905508f6257363a0c6476d6cf133
By the way, thanks for your awesome work on this Gem !

Hi Brice,
Yes, this page referred to the 1.x, and is completely deprecated with the current 2.x
What do you need?
Ben

Nothing special, i'm trying to figure out why i've these errors :
Uncaught TypeError: Cannot read property 'offsetWidth' of nullxk @ js?v=3.18&sensor=false&client=&key=&libraries=geometry&language=&hl=&region=:70ll @ js?v=3.18&sensor=false&client=&key=&libraries=geometry&language=&hl=&region=:78Map @ map.self.js?body=1:13build @ builder.self.js?body=1:9Gmaps.Objects.Handler.Handler.buildMap @ handler.self.js?body=1:18(anonymous function) @ application.self.js?body=1:95
handler.self.js?body=1:108 Uncaught TypeError: Cannot read property 'getServiceObject' of undefined

But i've not finished to inspect my code.
Thanks for your answer.


Add support for Swift 5.7

[x] Open validation for 5.7-only packages

[ ] https://github.com/SwiftPackageIndex/PackageList/pull/2717 → update nightly to official release and update validation as well

[ ] Use 5.7 for package dump (or else 5.7-only packages won't show package pages)
[ ] Add support for 5.7 in builder
[ ] Install 5.7 on Mac builders
[ ] Update matrix in server
[ ] Decide what to do about DocC default - probably bump it to latest automatically

Of these 5.7 packages that I've just added:

https://swiftpackageindex.com/tevelee/SwiftUI-Flow.git
https://swiftpackageindex.com/rnapier/RNAJSON.git
https://swiftpackageindex.com/akardas16/SideMenu.git
https://swiftpackageindex.com/orchetect/OSCKit.git
https://swiftpackageindex.com/NeilsUltimateLab/AutolayoutExtension.git
https://swiftpackageindex.com/apple/swift-nio-imap.git
https://swiftpackageindex.com/icanzilb/MarkCodable.git

only

https://swiftpackageindex.com/orchetect/OSCKit.git

is showing up in the index. Since we're using 5.6 to dump the package I would have expected none of them to pass analysis. Not sure yet how that one is different - it definitely has // swift-tools-version:5.7 in its Package.swift.

Failing as expected
~/D/OSCKit on  main
❯ env DEVELOPER_DIR="/Applications/Xcode-13.4.1.app" xcrun swift package dump-package
'osckit': error: package 'osckit' is using Swift tools version 5.7.0 but the installed version is 5.6.0
error: invalid manifests at [<AbsolutePath:"/Users/sas/Downloads/OSCKit">]
~/D/MarkCodable on  main
❯ env DEVELOPER_DIR="/Applications/Xcode-13.4.1.app" xcrun swift package dump-package
'markcodable': error: package 'markcodable' is using Swift tools version 5.7.0 but the installed version is 5.6.0
error: invalid manifests at [<AbsolutePath:"/Users/sas/Downloads/MarkCodable">]

Did it start as a 5.6 project and evolve to 5.7?

Mmm, that shouldn’t make a difference - plus when it was first seen after adding it earlier it was 5.7 🤔

Not sure what exactly happened - but they're all there now. Just as I'd run the analysis locally and found no problem 😅

Ok, the package-dump failure mentioned above does not prevent the package from showing up in the index anymore. We're not getting all the info (like the proper package name) but we are saving versions etc. It's still not quite clear to me how for instance MarkCodable showed up in search but wasn't available yet (indicating analysis hadn't run) or why none of the package above other than OSCKit showed up in the "Recently Added" (still not, even now that they're available).
Not going to dwell on that though for the moment.

This is done


Fixed #26333 -- Made GEOS Geometry classes deconstructible.

Thans!
Tests should be moved to tests/gis_tests/geos_tests/test_geos.py instead.

I don't think this qualifies for a backport to 1.9 as the issue isn't a regression or a serious crashing issue.
Merged in e158ec0ba0b43cbe9b509d4ed5587fa3b2ae3cc6, thanks!


Can not upgrade from wsl 1 to 2, i9-9900X intel, and bios virtualization and virtual machine platform are on.

Environment
Windows build number: 10.0.19042.685
Your Distribution version: Ubuntu 20.04
Whether the issue is on WSL 2 and/or WSL 1: Can't update from wsl1 to wsl2

Steps to reproduce + error screen

System Info:

By any means i am not WSL expert, but is possible some running software blocks Hyper-V functionality
I am using  some kind of this software for local wordpress development with Docker, uninstall them and problem gome

By any means i am not WSL expert, but is possible some running software blocks Hyper-V functionality
I am using  some kind of this software for local wordpress development with Docker, uninstall them and problem gome

/dupe #5363. Please collect WSL logs and post the backlink to the feedback in that issue.

/dupe #5363. Please collect WSL logs and post the backlink to the feedback in that issue.


HideFromThisPC also hides from Userprofile

HideDocumentsFromThisPC and similar also hides the folder from Userprofile.
Method used before change to using ThisPcPolicy does not have this potentially unwanted behavior.

That method sometimes didn't have even the wanted behavior, that's why it was changed in the first place. Is this behavior new in 1709 or has it always been there?

I have only tested with 1709 so don't know if existed before that.


Add missing docs for module: 'none' in tsc --init

Fixes #16941

@ikatyang,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by Microsoft. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Tests should be fixed by ivogabe/gulp-typescript#522

Thanks @ikatyang !


Fix flag comments for statspusher ttls

Description:
Correct the flag comments for dataset, bundle, and node ttl config flags.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Can we use the default medusa backend?

Hello Team!
is it necessary to use your backend or can we use our prebuilt backend?

You can copy and paste files from our medusa/src into your Medusa backend. This includes models for materials and colors, store API endpoints for custom fields, models, and product types, as well as admin API endpoints, routes, and widgets for custom fields and models.


YARN-8898. [Addendum] Improve NodeManager#TestFederationInterceptor Setup Code

Description of PR
JIRA: Fix FederationInterceptor#allocate to set application priority in allocateResponse
In YARN-8898, we store the ApplicationSubmissionContext of a Job in the FederationStateStore, and this field can be null. However, in NodeManager's TestFederationInterceptor, the Application is submitted through a mock, which causes there to be no relationship between the Application and HomeSubcluster stored in the MemoryFederationStateStore. This does not affect the execution of the unit test, but the following information will be printed in the log.
2023-06-10 16:08:42,501 ERROR [pool-18-thread-1] utils.FederationStateStoreFacade (FederationStateStoreFacade.java:getApplicationSubmissionContext(1006)) - getApplicationSubmissionContext error, applicationId = application_123456_0001.
org.apache.hadoop.yarn.server.federation.store.exception.FederationStateStoreException: Application application_123456_0001 does not exist.
	at org.apache.hadoop.yarn.server.federation.store.utils.FederationStateStoreUtils.logAndThrowStoreException(FederationStateStoreUtils.java:172)
	at org.apache.hadoop.yarn.server.federation.store.impl.MemoryFederationStateStore.getApplicationHomeSubCluster(MemoryFederationStateStore.java:294)
	at org.apache.hadoop.yarn.server.federation.utils.FederationStateStoreFacade.getApplicationSubmissionContext(FederationStateStoreFacade.java:1001)
	at org.apache.hadoop.yarn.server.nodemanager.amrmproxy.FederationInterceptor$2.run(FederationInterceptor.java:1283)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

We should avoid such information. In TestFederationInterceptor#setup, we initialize the relationship between Application and HomeSubcluster to avoid this issue.
How was this patch tested?
Junit Test.
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 28s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m  8s

trunk passed

+1 :green_heart:
compile
2m 36s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
2m 26s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 27s

trunk passed

+1 :green_heart:
mvnsite
1m 35s

trunk passed

+1 :green_heart:
javadoc
1m 38s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 26s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m  5s

trunk passed

+1 :green_heart:
shadedclient
21m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 32s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 10s

the patch passed

+1 :green_heart:
compile
2m 25s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
2m 25s

the patch passed

+1 :green_heart:
compile
2m 16s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
2m 16s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 10s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server: The patch generated 1 new + 1 unchanged - 0 fixed = 2 total (was 1)

+1 :green_heart:
mvnsite
1m 17s

the patch passed

+1 :green_heart:
javadoc
1m 12s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 10s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m 54s

the patch passed

+1 :green_heart:
shadedclient
21m 54s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 20s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
24m 30s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

144m 19s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5732

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 80e6d46212c9 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fc01cca1e6c46bf19153e517f2f02f12c9d24305

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/1/testReport/

Max. process+thread count
557 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
19m 50s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
21m  3s

trunk passed

+1 :green_heart:
compile
2m 32s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
2m 26s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
1m 38s

trunk passed

+1 :green_heart:
javadoc
1m 40s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 25s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m  5s

trunk passed

+1 :green_heart:
shadedclient
22m 39s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 34s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 10s

the patch passed

+1 :green_heart:
compile
2m 22s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
2m 22s

the patch passed

+1 :green_heart:
compile
2m 15s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
2m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
1m 11s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server: The patch generated 1 new + 1 unchanged - 0 fixed = 2 total (was 1)

+1 :green_heart:
mvnsite
1m 16s

the patch passed

+1 :green_heart:
javadoc
1m 14s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m  7s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m  1s

the patch passed

+1 :green_heart:
shadedclient
21m 49s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 20s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
24m 36s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 43s

The patch does not generate ASF License warnings.

145m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5732

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 54443f741cf7 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / fc01cca1e6c46bf19153e517f2f02f12c9d24305

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/2/testReport/

Max. process+thread count
558 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@goiri Can you help review this pr? Thank you very much!

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 38s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
18m 47s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 51s

trunk passed

+1 :green_heart:
compile
2m 35s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
compile
2m 22s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
checkstyle
1m 26s

trunk passed

+1 :green_heart:
mvnsite
1m 37s

trunk passed

+1 :green_heart:
javadoc
1m 39s

trunk passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m 25s

trunk passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
3m  7s

trunk passed

+1 :green_heart:
shadedclient
22m  4s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 34s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
1m 10s

the patch passed

+1 :green_heart:
compile
2m 24s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javac
2m 24s

the patch passed

+1 :green_heart:
compile
2m 18s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
javac
2m 18s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
1m 12s

the patch passed

+1 :green_heart:
mvnsite
1m 14s

the patch passed

+1 :green_heart:
javadoc
1m 13s

the patch passed with JDK Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1

+1 :green_heart:
javadoc
1m  8s

the patch passed with JDK Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

+1 :green_heart:
spotbugs
2m 58s

the patch passed

+1 :green_heart:
shadedclient
22m 10s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
3m 22s

hadoop-yarn-server-common in the patch passed.

+1 :green_heart:
unit
24m 29s

hadoop-yarn-server-nodemanager in the patch passed.

+1 :green_heart:
asflicense
0m 42s

The patch does not generate ASF License warnings.

144m 32s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5732

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux f29f279f1d5e 4.15.0-206-generic #217-Ubuntu SMP Fri Feb 3 19:10:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c44cc50322041bb259099aa5032ae9564f64cfc3

Default Java
Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.19+7-post-Ubuntu-0ubuntu120.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_362-8u372-ga~us1-0ubuntu1~20.04-b09

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/3/testReport/

Max. process+thread count
726 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-common hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5732/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@goiri Thank you very much for your help in reviewing the code!


Wrong color #16 in Freya

The color_16 in the picture above looks like white, but in freya.sh:
COLOR_16="#6c71c4"

@alim0x, yep — good catch.

Is this still a problem or can this be closed? I've tried using the Freya theme but didn't encounter any problems with the gnome-terminal (see below) or guake:

If you still have problems with the colorscheme, will you give us some details on how to reproduce this behaviour, i.e. which OS/terminal/shell you use?
ps. On your screenshot color 9 seems to be off (black), too. Might it be the case your terminal settings override certain colors?

@bohlender now freya theme looks as expected. @alim0x since it has been fixed could you close the issue please.


Render billing contact from the billing API.

Fixes an issue where the billing contact couldn't be rendered.

:+1:


Plugin references in documentation links are dead

On http://angular.github.io/protractor/#/plugins when clicking on any of the 3 default plugins, we do not get to the appropriate page (if any exists).

The linked content is further down on the same page. Using ng-hint as an example, the links navigate incorrectly from
http://angular.github.io/protractor/#/plugins
to
http://angular.github.io/protractor/#/#nghint-plugin
instead of
http://angular.github.io/protractor/#/plugins#nghint-plugin

Thanks for pointing this out - this is an issue with converting our markdown docs to also work on the website


[Stream] Fix stream ssl verify

Hey!
I'm currently implementing SSL verification in egeloen/ivory-http-adapter#62 which test all adapters of guzzle http in order to be sure everything is working fine. When doing it, I discover an inconsitence between Curl (Single/Multi) and the Stream one. Basically, in my test suite I have generated a self signed certificate which allow me to test the feature. For Curl and MultiCurl, if I enable ssl verification, I got an exception because it does not allow self signed cetificate whereas the stream one does not use the same strategy and allow it. This PR rationalizes this behavior.
Feedback welcome!

@mtdowling Any thought?

Looks good.

Thank you!


Consume the API Proxy in SAP Web IDE

Tutorial URL: https://developers.sap.com/tutorials/hcp-apim-webide-int.html
I'm referring to steps 12-13.
I have created destinations in my HCP account as specified in steps 6-7. But I'm still unable to see list of APIs in webide service catalog when creating new project from template.
What settings can I fix to see the list of APIs in webide?
Destinations parameters are:
Description=for OpenSAP APImgmt demo Type=HTTP TrustAll=true Authentication=BasicAuthentication WebIDEUsage=api_mgmt_proxy Name=APIMgmt_APIPortal WebIDEEnabled=true URL=https\://s**********trial-trial.apim1.hanatrial.ondemand.com\:443/ ProxyType=Internet User=**********
Name=APImgmt URL=https\://devportalu34f5b50f-s***********trial.hanatrial.ondemand.com/ ProxyType=Internet Type=HTTP WebIDEEnabled=true Authentication=AppToAppSSO WebIDEUsage=api_mgmt_catalog Description=for apimgmt OpenSap demo dev portal

Thanks!

Hello,
In order to have API Products, you need to create one in API Management and even then if the APIs doesn't come up the there is a problem with dev portal destination. Please check the spaces
Regards
Shilpa

Hello, Shilpa
Thanks for your answer!
I have created API Products in API Management and I've logged in to webide and api management from the same s-user account.  In the network tab of WebIDE I can see the same list of my API applications as in Dev portal, so destination is probably configured correctly.

The same Application in dev portal:

API product is also associated with API in API Portal

Best regards,
Anna

Hello Anna,
I am able to get the APIs. Rechecked. Kindly setup a call with me to check your details.
Regards
Shilpa

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


The --record flag should be removed from the documentation

What happened?
The --record command line flag for kubectl has been removed with one of the previous versions.
The documentation for well-known annotation, specifically kubernetes.io/change-cause, still mentions the flag.

It is populated when adding --record to a kubectl command that may change an object.

What did you expect to happen?
Mentions of the flag should be removed from the documentation.
How can we reproduce it (as minimally and precisely as possible)?
Try to run the kubectl set image with the --record flag. The flag is not recognized anymore.
Anything else we need to know?
No response
Kubernetes version

$ kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short.  Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:20:07Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v5.0.1
Server Version: version.Info{Major:"1", Minor:"27", GitVersion:"v1.27.2", GitCommit:"7f6f68fdabc4df88cfea2dcf9a19b2b830f1e647", GitTreeState:"clean", BuildDate:"2023-05-17T14:13:28Z", GoVersion:"go1.20.4", Compiler:"gc", Platform:"linux/amd64"}

Cloud provider
Any
OS version

$ uname -a
Darwin xxx 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:56 PDT 2023; root:xnu-8796.141.3~6/RELEASE_X86_64 x86_64

Install tools

Container runtime (CRI) and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)

@bmuschko   what about the example line  Example: kubernetes.io/change-cause: "kubectl edit --record deployment foo

/assign @akshayamadhuri

@akshayamadhuri Yes, that would have to be changed as well.
@Ritikaa96 Thanks, will do.

/triage accepted
/priority backlog

@akshayamadhuri Are you still working on this issue?


How to set a public key to provider cache?

When I have deployed the provider, template and constraint, but I encounter an error (response: {"errors": null, "responses": null, "status_code": 400, "system_error": "key is not found in provider cache"}) when trying to deploy the example yaml file. How can I set the public key in the cache? thanks..

Hi @jacckyyy,
Actually I have no idea where is key is not found in provider cache throwing from. Could please share the steps you have followed, full logs, HTTP response, and some kind of other stuff to reproduce this? Thanks.

Hi @Dentrax,
I'm sorry, my previous description was too brief. My steps were based on the article in the following link.

https://github.com/sigstore/cosign-gatekeeper-provider

Starting with the installation of gatekeeper, and installed cosign-gatekeeper-provider,

finally confirmed the deployment of ConstraintTemplate and Contraint policy.

However, at the last step, when I verified the signature using the example in the policy/example, I got the following error message regardless of whether I signed with cosign or not.

It seems that the provider did not set the public key. I don't know what the problem is with this part? Did I miss anything? Thanks... Orz

+1
getting the same error response

Hitting the same issue with gatekeeper 3.14.0. @Dentrax Could it be something not working with Gatekeeper internal cache? I tried disabling it and still getting the same error. It seems gatekeeper is not even calling the external provider when printing that error.

The error comes from this line https://github.com/open-policy-agent/frameworks/blob/359cf1b785c9f630f61f58366e685918153c5357/constraint/pkg/externaldata/cache.go#L103

Maybe related to https://github.com/open-policy-agent/gatekeeper/pull/3132
Maybe Upgrade to >3.15 https://github.com/open-policy-agent/gatekeeper/releases/tag/v3.15.0 will fix

@houdini91 Thank you! Upgrading to 3.15 and setting --external-data-provider-response-cache-ttl=0 seems to help address the issue. Not sure why cache needs to be disabled for the provider to work.


what is best way to delete the map .

Hi there, I'm using the map for a while now. I used the map in ionic application, and every time the user leave the "Page" I try to delete, remove and clear the map. My approach something like
map.clear();
map.empty(); // <-- no idea how this is helpful
map.remove();

but the problem is the map events still working and never get cleared ! but I found a function in the "src" but not in the  Docs
map.off()

so now my final code is
map.clear();
map.empty(); // <-- no idea how this is helpful
map.off();
map.remove();

do you think guys this will remove every related to the map ? and will help avoiding memory leaks in both sides "JS" and "Native";

If you use the maps plugin v2, just executes map.remove() is the best.
The map.remove() does map.clear() and map.off() internally

It looks you use the v1.4.
There is no method map.empty() (but I didn't know for the ionic wrapper case).
map.clear();
map.off();
map.remove();

At lease the above steps are very fine to avoid memory leak.

thanks @wf9a5m75 for answering my question .


Issue number- 245: updated docs/readme, svc-aggregation/readme, svc-systems/readme, svc-update/readme files

svc-aggregation/ readme changes:

Added connection methods in the aggregation service root response.
Included connection method info in the request body for adding a plugin and BMC.
Removed OEM info from the request body for adding a plugin and BMC.

svc-update/readme changes:
Included Task responses for simple and start update actions.
svc-systems/readme changes:

Added single network adapter information.
Added PCIedevices information.
Modified response of storage subsystem for storage controllers.
Included the following note for creation and deletion of volumes:
"Reset is required for the changes to reflect."

docs/readme changes:

All of the above changes.
Updated TOC.
Updated list of APIs.

Wrong PR.


Allow classes on  and  elements

This PR enables classes to be added to th and td elements of the table like so...
<table-column
    show="income"
    label="Income"
    header-class="is-primary"
    cell-class="has-right-text">
</table-column>

I'm working with a table where I need columns that contain numbers right justified. Instead of doing an nth child css selector, which I'll have to update if I ever change my column order, I can now just apply class to that column.
I think it would also be handy to be able to specify different classes for the header cell, thus I've added a seperate property for that.
I'm new to Vue and fumbled my way through working out how to do this, so please let me know any corrections if this is of interest to the project.

Hi Tim, we're currently finalising some other changes to the row & column rendering, which will probably collide with these changes.
I'll get back to you when we're done with those, then we can see what's necessary to finish and merge this PR :)

no worries

Thanks! Gonna make some more tweaks and add some tests myself, will ping back when released later today :)

oh nice! Thanks @sebastiandedeyne let me know if you want me to do anything with it. Thanks for writing the tests - I'd probably just break things playing in there with my lack of JS testing. Might pay attention to the changes you make and learn a thing or two!

Patched everything up and gonna tag later today or tomorrow!

I added the new classes to the settings, so you can set a default too instead of manually adding it to every component
Classes can be anything that Vue accepts in v-bind:class, so also an array or an object
Added some basic snapshot tests for this feature

very freakin' sweet! Thanks for the update!


Designs: Land acknowledgement for DUP

Description:
This ticket is to create designs for adding a land acknowledgement to DUP, that will be consistent across bcparks.ca, and camping.bcparks.ca
Desktop design for camping.bcparks.ca:

Mobile design for camping.bcparks.ca:

Acceptance Criteria:

[ ] The acknowledgement reads: "We acknowledge all First Nations on whose claimed territories BC Parks were established. We honour their connection to the land and respect the importance of their diverse teachings, traditions, and practices within these territories.”
[ ] designs for land acknowledgement are in figma and linked here

Development Checklist:

[ ] ...
[ ] ...
[ ] ...

Dependencies

Blocked by
Blocking

Relevant documentation as reference
Definition of Ready

[ ] Acceptance criteria are included
[ ] Wireframes are included (if applicable)
[ ] Design / Solution is accepted by Product Owner (if applicable)
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

Definition of Done

In progress:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] UI meets accessibility requirements
[ ] Unit tests are written
[ ] Work is traceable in GitHub
[ ] PR linked to ticket number
[ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment

Code review:

[ ] Code is peer reviewed and has passed CI/CD tests

QA:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Code is potentially shippable to the production environment
[ ] Functional features have been tested and passed by QA
[ ] UI components tested by designer
[ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)

PO Review:

[ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
[ ] Reviewed and approved by Product Owner

Notes:

Sprint Planning notes: Could be a good place for @pavelcreates  to start, with support from @meredithom

If there is capacity to pick this design ticket up before end of week I would be very grateful! Reservation Services is working on a decision note for exec and would like include designs in the note (@ndelraye @meredithom @pavelcreates)

sure, seems simple enough

Reference: CMS ticket: https://bcparksdigital.atlassian.net/browse/CMS-256?focusedCommentId=23251

@ndelraye - Reservation services indicated that they no longer require these designs and will let us know next steps after DM approval. Thanks for picking this up.


ClearCache FilterKeys should be a string[] array

Update the rest api spec to reflect the PR in https://github.com/elastic/elasticsearch/pull/20292/
Rename FilterKeys string array property to FilterCacheKeys to maintain backwards binary compatibility.
Mark all usages of the bool FilterKeys value as Obsolete, including the error flag.
Bump ApiGenerator to point at 1.7 branch.
Make FluentRequestParameters a partial class so that generated types can be extended.
Add PatchMethod to IDescriptorOverrides to allow patching on a per method basis.
Move Csharp property naming on Request types to ApiQueryParameters type so that property naming can be modified independently of the underlying query string parameter name.

Fixes #2229

Added url tests for both fluent and object initializer syntax 👍

@gmarz, would you mind reviewing please?

LGTM


How does vis-network get the real-time position of the center of the node and the top left corner under any circumstances?

I hope that the coordinates of the node and the upper left corner can be obtained in real time. In any case, for example, the position of 'node1' is obtained when zooming in. After the node is moved, it is a new position. It should be changed. The distance from the red dot should be calculated.

.wrap{
  position: relative;
  margin: 100px auto 0;
  width: 400px;
  height: 400px;
  border: 1px solid black;
}
#mynetwork {
  width: 100%;
  height: 100%;
}
.origin {
  position: absolute;
  left: -5px;
  top: -5px;
  width: 10px;
  height: 10px;

  background: red;
  z-index: 1;
  border-radius: 50%;
}

// create an array with nodes
var nodes = [{
  id: 1,
  "shape": "dot",
  label: 'node1',
  x: 5,
  y: 5
}, {
  id: 2,
  "shape": "dot",
  label: 'node2',
  x: 50,
  y: 75
}];

// create an array with edges
var edges = [
  { from: 1, to: 2 },
  { from: 1, to: 3 }
];

// create a network
var container = document.getElementById('mynetwork');
var data = {
  nodes: nodes,
  edges: edges
};
var options = {
  interaction: {
    hover: true,
  },
  physics: {
    enabled: false
  }
};
var network = new vis.Network(container, data, options);
network.on("hoverNode", function (t) {
  var nodeID = t.node;
  // I want to get the real-time position of the center of the node and the upper left corner under any circumstances (zoom in, zoom out, move)
  // ... ?
});

component: vis-network
vis-network version: latest version
browser: Chrome
os: Mac

jsfiddle demo

// You can query nodes locations at any time:
const node = network.getPositions([nodeID])[nodeID]

// Top left corner is always zero in DOM coordinates, just convert it to canvas coordinates:
const corner = network.DOMtoCanvas({
  x: 0,
  y: 0
})

console.log(node, corner)

PS: This is more of an StackOverflow question though.
PPS: Use numeric version instead of latest, especially if your “latest” is three years older than the latest.

// You can query nodes locations at any time:
const node = network.getPositions([nodeID])[nodeID]

// Top left corner is always zero in DOM coordinates, just convert it to canvas coordinates:
const corner = network.DOMtoCanvas({
  x: 0,
  y: 0
})

console.log(node, corner)

PS: This is more of an StackOverflow question though.
PPS: Use numeric version instead of latest, especially if your “latest” is three years older than the latest.

    const node = network.getPositions([nodeID])[nodeID]
    const corner = visGraph.canvasToDOM({
      x: node.x,
      y: node.y
    })

Your reply is too fast, very timely!  Perfect problem solving. Thank you for your thoughts and have made changes on your basis.This is the result I want.
Thank you! I will adjust to use the digital version to ask questions, and pay attention next time.
Thanks again!


Support for CSP configuration

oCIS x (version to be checked) supports CSP configuration.
Example: https://github.com/owncloud/ocis/blob/0cf3298fbd72cdaff74fd6c40484942774b726ce/deployments/examples/ocis_wopi/config/ocis/csp.yaml

I can take care of providing at least a basic draft for this


fix search delegation

adds --conv to inbox search cli
fixes render bugs on search delegation with cli
triggers delegate search if query < search.MinTokenLength
fixes bugs around delegation for name searches and streaming back thread results
triggers SelectiveSync in RPC method instead of indexer so we can trigger/cancel a sync when the search is delegated

outstanding on GUI:

[x] show inbox index percentage on hover
[x] fix duplication of results on thread search in GUI

Don't think so, I am fine having it run in thread search, but I don't see the point in the full inbox. It just makes everything slower when typing, and makes this code more complicated.


Custom filterComponent and filter function

The pull request enables

The ability of specify a custom filter component, to enable

Building complex filter inputs, filters with more components than the simple text box
Faceting, the result set is passed down to the filter, so that the filter can change according to what is selected.

The ability to specify a custom filter function, to enable

Swapping out the underscore based filterer, to a more performant alternative.
Enables consumption of the custom filter object that the customFilterComponent might create.

@tinygrasshopper Please update your branch with the latest master which includes #241. This will allow your tests to run on Travis.  Thanks!

@tinygrasshopper nice work!

@kevinold any thoughts on the pull-request? Is it clear how one might use these extensions? Should I include some sample code, on how we use this to build filters based on the results?

@kevinold Please review PR if its possible.

would love to see this functionality added!

When is this getting merged?

@tinygrasshopper Please update to the latest master and I will get this merged this weekend.  Thanks!

@kevinold Updated

+1. When is this getting merged?

looks like this has been updated - any word on getting this merged?

Seems good
On Mon, Oct 26, 2015 at 4:46 PM Kevin Hughes<EMAIL_ADDRESS>wrote:

looks like this has been updated - any word on getting this merged?
—
Reply to this email directly or view it on GitHub
https://github.com/GriddleGriddle/Griddle/pull/238#issuecomment-151279733
.

:cake:

:clap:

:+1:

hello @tinygrasshopper ,
can you include some sample code, on how we use this to build filters based on the results as you suggested?


Datafusion IndexError - Return fields from the lhs and rhs of a join

Closes: #584

Codecov Report

:exclamation: No coverage uploaded for pull request base (datafusion-sql-planner@ba50d24). Click here to learn what that means.
The diff coverage is n/a.

@@                    Coverage Diff                    @@
##             datafusion-sql-planner     #599   +/-   ##
=========================================================
  Coverage                          ?   60.81%
=========================================================
  Files                             ?       71
  Lines                             ?     3560
  Branches                          ?      722
=========================================================
  Hits                              ?     2165
  Misses                            ?     1247
  Partials                          ?      148

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[Cosmos] replace node-abort-controller with @azure/abort-controller

Replacing the use of node-abort-controller and abort-controller with @azure/abort-controller (#5264)

/azp run


add support for [GitHubActions] via API

Refs #2574. An alternative approach to #3898 that leverages the GH v3 Check Suites API instead of badge scraping the native GH Workflow result badge.
Although I still prefer this approach to #3898, there is one downside in instances where a repo has more than one Workflow running on a given ref (branch, etc.) vs. #3898.
In such a scenario, the response from the check-suites will include multiple records for each Workflow but there's no way to associate the record in the API response to a named Workflow, at least not that I've been able to find. For example, https://api.github.com/repos/actions/setup-python/commits/master/check-suites
The badge scraping approach in #3898 does allow the user to explicitly specify which Workflow they want by workflow name, but it only works on the master branch. The API approach allows the user to pick the branch/ref, but not the specific workflow by name

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @calebcartwright!

  Generated by :no_entry_sign: dangerJS against 4768ce9a0cb640ae75537b805b1ea2696e6b02e7

Failing service tests were other unrelated GitHub badge tests (and didn't fail in services@node-latest) so I'm going to update the PR title to only run the tests for this new service

Thanks for reviewing @PyvesB!
I'm most likely going to just close this PR. I understand (and agree with) the preference for the API over badge scraping, but this approach simply isn't viable without the ability to utilize the workflow name (it's as core as being able to specify the GH owner and repo).
The badge scraping approach is the only option that's available right now, and I've updated that PR with more detail in https://github.com/badges/shields/pull/3898#issuecomment-554768572.
The Check Suite and Status APIs are not specific Actions/Workflow, but perhaps GitHub will eventually roll out Actions/Workflow APIs that we could switch to down the road. However, IMO we should proceed with the badge scraping approach as there is a huge community demand for this badge that we can meet, today, with that approach.

Could we simply ask for the workflow name feature on the GitHub community forums? GitHub staff have been quite good at solving issues and responding to user queries regarding GitHub actions. I will look at the other PR in the evening.

This feature request may well do the trick when implemented: https://github.community/t5/GitHub-API-Development-and/How-to-retrieve-the-full-list-of-Actions-workflow-runs-shown-on/m-p/39171

Closing this as #3898 has been merged and deployed


Closes #403

This patch contains both the missing query method for RDF::Changeset (which I made protected) , as well as ameliorated behaviour on the part of RDF::Repository.
I had originally had the query method return just an array as that's all RDF::Mutable#delete needs to proceed, but then changed it to return an RDF::Query with the partial statement as a single pattern. The other solution would be for RDF::Changeset to just go around RDF::Mutable#delete.
The separate branch test-wildcard-changeset contains a test case that will demonstrate the crash scenario. You are right however that without its own modifications, RDF::Repository would not correctly apply the partial statement, so in effect this one test case probes both scenarios. I don't know if you want a separate/duplicate test case for that.

Coverage decreased (-0.04%) to 92.219% when pulling ee5ab43346ec916148a2075e26144c548a8ff7c6 on doriantaylor:wildcard-changeset into 28307eb5db441e9fc42b3924aa4404f7bcd8afae on ruby-rdf:develop.

Coverage decreased (-0.04%) to 92.219% when pulling ee5ab43346ec916148a2075e26144c548a8ff7c6 on doriantaylor:wildcard-changeset into 28307eb5db441e9fc42b3924aa4404f7bcd8afae on ruby-rdf:develop.

Unsurprisingly the test blows up all over the place when adding the it_behaves_like… business. Should an RDF::Changeset even be an RDF::Mutable? I mean, it makes sense for its components to be…

It inherits some behavior from RDF::Mutable, but doesn't otherwise correspond to its contract. It would be worth experimenting with removing that include, but RDF::Mutable is never designed to work on it's own, but when backed by some mutable dataset, such as RDF::Repository, so this could be tested by attaching it to a repository, or implementing some mock.

My inclination then is to try disentangling RDF::Changeset from RDF::Mutable as a separate endeavour…

Okay, I'll pull this PR if you'll look into disentangling changeset and mutable.


travis CI broken

integration lost due to handoff

actually looks like it was just an old log and GitHub Actions is used


GitHub Authentication

Discussed in https://github.com/fasmide/remotemoe/discussions/14

Originally posted by fasmide November 24, 2022
So, in light of #12 I've been thinking about how to authorize remote.moe's users without getting too much in the way
One way of doing it could be leveraging GitHubs public key API https://github.com/<username>.keys and use these keys for identification of users
At the moment, remotemoe does not use the username for anything, it shouldn't be a problem to have users provide their GitHub username and then lookup their keys on the fly

im waiting hope it will back in 1-2 days


django中的views调用 脚本中的函数时，报错，参考网上建议修改monkey.patch_all(thread=False)，报错详情如下 When views in Django calls the function in the script, an error is reported. Please refer to the online suggestions for modification monkey.patch_ All (thread = false), the details of error reporting are as follows

OS: centos7
Python version: 3.6.5
Locust version:1.0.3
Locust file contents (anonymized if necessary):

@task
def my_task(self):
self.client.get("/")
@task
def task_404(self):
self.client.get("/non-existing-path")
def main(press):
print("xxxxxxxxxx")
# id = press.if_id
print(press)
user_dict = dict(wait_time=between(1, 3), host="https://docs.locust.io", my_task=my_task, task_404=task_404)
# setup Environment and Runner
Users = type('Users', (HttpUser,), user_dict)
env = Environment(user_classes=[Users])
env.create_local_runner()
# start a WebUI instance
env.create_web_ui(port=8081)

# start a greenlet that periodically outputs the current stats
gevent.spawn(stats_printer(env.stats))

# start the test
env.runner.start(1, hatch_rate=10)
gevent.spawn_later(60, lambda: env.runner.quit())
env.runner.greenlet.join()
env.web_ui.stop()

The above is the content of script file.
django:
from .pressure import main
def press_run(request):
if request.method == 'POST':
thread_task = threading.Thread(target=main, args=(press,))
thread_task.start()
return HttpResponseRedirect("/pressure/case_list")
Before modifying site-packages/locust/init.py  monkey.patch_all(thread=False)：error：
RuntimeError: cannot release un-acquired lock
and
MonkeyPatchWarning: Monkey-patching ssl after ssl has already been imported may lead to errors, including RecursionError on Python 3.6. It may also silently lead to incorrect behaviour on Python 3.7. Please monkey-patch earlier. See https://github.com/gevent/gevent/issues/1016. Modules that had direct imports (NOT patched): ['aiohttp.client_exceptions (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/client_exceptions.py)', 'aiohttp.client (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/client.py)', 'aiohttp.client_reqrep (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/client_reqrep.py)', 'urllib3.util (/root/anaconda3/envs/safe/lib/python3.6/site-packages/urllib3/util/init.py)', 'aiohttp.web_runner (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/web_runner.py)', 'aiohttp.web (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/web.py)', 'urllib3.util.ssl_ (/root/anaconda3/envs/safe/lib/python3.6/site-packages/urllib3/util/ssl_.py)', 'aiohttp.connector (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/connector.py)', 'aiohttp.worker (/root/anaconda3/envs/safe/lib/python3.6/site-packages/aiohttp/worker.py)'].
_monkey.patch_all()
After modifying site-packages/locust/init.py  error：greenlet.error: cannot switch to a different thread and
maximum recursion depth exceeded while calling a Python object and locust no data
When Django is not used：business as usual

I'm sorry, but I can't understand this issue. It seems to be related to the gevent/locust monkey patching somehow together with Django?

抱歉，我无法理解此问题。它似乎与Django一起打补丁的gevent /蝗虫猴有关？
Yes, about this reason, Django can't start the thread to call locust normally,locust no data,Hope to find a solution for Django calling locust

I'm sorry, but I can't understand this issue. It seems to be related to the gevent/locust monkey patching somehow together with Django?

Yes, about this reason, Django can't start the thread to call locust normally,locust no data,Hope to find a solution for Django calling locust

I'm sorry, but I can't understand this issue. It seems to be related to the gevent/locust monkey patching somehow together with Django?

Problem solved, in Django manage.py , added
import gevent
from gevent import monkey
monkey.patch_all()


Load data from numpy arrays

Not yet optimised for speed, but this allows running the new counting on data straight from a numpy array. I've compared outputs from this and the old repos, and they're pretty similar. Not exactly the same, because the boxes aren't quite in the same place, but once I implement full control over box positions on the new repo, we should be able to make that comparison.

(please don't merge currently)

(please don't merge currently)

You can select that this PR is a draft if you prefer :)

ah good to know you can do that, thanks!


[SPARK-35421][SS] Remove redundant ProjectExec from streaming queries with V2Relation

What changes were proposed in this pull request?

This PR fixes an issue that streaming queries with V2Relation can have redundant ProjectExec in its physical plan.
You can easily reproduce this issue with the following code.
import org.apache.spark.sql.streaming.Trigger

val query = spark.
  readStream.
  format("rate").
  option("rowsPerSecond", 1000).
  option("rampUpTime", "10s").
  load().
  selectExpr("timestamp", "100",  "value").
  writeStream.
  format("console").
  trigger(Trigger.ProcessingTime("5 seconds")).
  // trigger(Trigger.Continuous("5 seconds")). // You can reproduce with continuous processing too.
  outputMode("append").
  start()

The plan tree is here.

Why are the changes needed?

For better performance.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

I run the same code above and get the following plan tree.

Test build #138619 has started for PR 32570 at commit 6cdcf4c.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43139/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43139/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43139/

Test build #138619 has finished for PR 32570 at commit 6cdcf4c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138619/

cc: @cloud-fan

Test build #138701 has started for PR 32570 at commit 4574440.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43222/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/43222/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/43222/

thanks, merging to master!

Test build #138701 has finished for PR 32570 at commit 4574440.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/138701/


[WIP] Lib cache

:white_check_mark: Build AElf <IP_ADDRESS>21 completed (commit https://github.com/AElfProject/AElf/commit/e66b8a1fc0 by @jason-hoopox)

:x: Build AElf <IP_ADDRESS>49 failed (commit https://github.com/AElfProject/AElf/commit/0339a58d35 by @jason-hoopox)

:white_check_mark: Build AElf <IP_ADDRESS>64 completed (commit https://github.com/AElfProject/AElf/commit/d2af626e20 by @jason-hoopox)

Do not need this PR.


Payloads: carry around the ingest type from the ingests API

There’s an experimental attempt at doing this in a more generic way in #222.


Make FIR parser the default

Refs #19

[x] CHANGELOG.md's "Unreleased" section has been updated, if applicable.

Wait I think this found an actual bug that I thought was a Wasm JS bug. Whoops.

Fix in https://github.com/cashapp/redwood/pull/2210


Add Flex Outdoor RGBW Model info

Added model info for OSRAM Flex Outdoor RGBW
fixed model comment in line 1

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 80.319%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5440

Relevant Lines:
6773

💛  - Coveralls

Codecov Report

Merging #1536 (5a41281) into dev (d120c7a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #1536   +/-   ##
=======================================
  Coverage   80.31%   80.31%
=======================================
  Files         227      227
  Lines        6773     6773
=======================================
  Hits         5440     5440
  Misses       1333     1333

Impacted Files
Coverage Δ

zhaquirks/osram/flexrgbw.py
100.00% <ø> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d120c7a...5a41281. Read the comment docs.


background music while waiting

Background music should be played during main menu and lobby while waiting for other players for more immersion

Estimated time: 2h

6e85be735a439ff25b40d840baf5e9dd0a434926


bgset support for Angular 2

Hi,
I'm trying to use the bgset plugin in my Angular 2 website and the following error appears:
EXCEPTION: Template parse errors: Can't bind to 'bgset' since it isn't a known native property
This is because of Angular, right?

Here's how I declare things:
index.html

  ...

  ...

  <app>Loading...</app>

template.html

Thanks for the help and all the work you put into this library, is really awesome!!!

This might help:
http://stackoverflow.com/questions/34542619/angular-2-data-attributes/34542844

Setting attr.data-bgset does the trick. That's it, there's no issue...


⚠ Bofrost.de has degraded performance

In 4f38751, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1009 ms

Resolved: Bofrost.de performance has improved in 32a70ae.


Add a flyway-community-db-support-archetype to help development

Hi @Barry-RG , do you mind I make a commit to your PR to add what has been done in https://github.com/flyway/flyway-community-db-support/pull/22, including the version.txt, the implementation of  getPluginVersion.

Will do a rebase after #30 is merged.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: Barry-RG:x: JasonLuo-RedgateYou have signed the CLA already but the status is still pending? Let us recheck it.


SIDC from name possibility

Hi, is there is a way to get SIDC instead of SVG symbol?

Please test out 2aa9d846cb7c4a1ab84787804d0334574072ccec - this adds the -d or --sidc-only command line options, which will print out a list of SIDCs corresponding to the inputted names when you use the -n or --by-name option. For example, milsymbol -nd "friendly infantry squad" will output "10031000121211000000". If the verbose option is selected, a list of "input string" -> SIDC pairs will be printed.
Let me know if this addresses your need.

Working like a charm