Adding some usefull commands

Hello, thank you for sonos-cli I love it !
It would be so nice if you could add some commands like this one  :

if_coordinator : I must do : if [[ $(sonos $speaker if_playing info | grep 'is_coordinator = True') ]] then; for example for grouping to the coordinator but it take a long time to execute

if_queued  and if_not_queued: For example for not adding to queue every time we want to play the queue : `sonos $speaker if_queued play_queue  : $speaker if_not_queued add_playlist_to queue playlist : play_queue

rel_subgain : I must do bass_sub_level=$(sonos $speaker sub_gain); new_bass_sub_level=$((bass_sub_level-5)); sonos $speaker sub_gain $new_bass_sub_level" and it's very long too

rel_treble : I must do treble_level=$(sonos $speaker treble); new_treble_level=$((treble_level-5)); sonos $speaker treble $new_treble_level

rel_bass

And also some  commands for having the state of all speaker :
For example :

info_state :
which return for example :

speaker_1 :  is_coordinator = False
Playback is in progress: Artist: xx Album: Untitled (xxx) Title: xx
Volume : 60
Treble : 0
Bass : 0
Balance : 0
Loudness : on

speaker_2 :  is_coordinator = True
Using Line In (state: PAUSED_PLAYBACK
Volume : 60
Treble : 0
Bass : -3
Balance : -25
Loudness : off

speaker_3 : Using Line In (state: PAUSED_PLAYBACK)
Volume : 60
Treble : 0
Bass : -3
Balance : 25
Loudness : on

speaker_4 : Using Line In (state: PAUSED_PLAYBACK)
Volume : 25
Treble : -1
Bass : 0
Balance : 0
Loudness : on

speaker_5 : Playback is stopped
Volume : 25
Treble : 0
Bass : 0
Balance : 0
Loudness : on

speaker_6 : Playback is stopped: Channel: Radio.com Elapsed: 0:00:00
Volume : 25
Treble : -3
Bass : 0
Balance : 0
Loudness : on

speaker_Sub : on
Volume : 2

info_playing :
which return for example :

speaker_1 :
Playback is in progress: Artist: xx Album: Untitled  Title: xxxx

speaker_2 :
Using Line In (state: PAUSED_PLAYBACK)

speaker_3 :
Using Line In (state: PAUSED_PLAYBACK)

speaker_4 :
Using Line In (state: PAUSED_PLAYBACK)

speaker_5 :
Playback is stopped: Elapsed: 0:00:00

speaker_6 :
Playback is stopped: Channel: Radio.com Elapsed: 0:00:00

And the ability to group many speakers to the coordinator in one command. For example : sonos speaker_1 speaker_2 speaker_3 group if_coordinator speaker 4 or better the ability to define a coordinator :   sonos speaker_1 speaker_2 speaker_3 group $speaker as_coordinator and this action as_coordinator make the speaker $speaker the coordinator

I hope you will find the time to do it; it would be so helpful to me.
Thanks :-)

Thanks for the comments!

I've added an if_coordinator conditional modifier. Note that some commands already get automatically redirected to the coordinator for a group/pair.
I've added if_queue and if_no_queue conditional modifiers
The relative_bass (rb) and relative_treble (rt) actions already existed, but I've added the rel_bass and rel_treble synonyms
I've added a relative_sub_gain (rel_sub_gain, rsg) action
It's possible to operate on all speakers using the _all_ speaker redirect. E.g., sonos _all_ info will run the info action for all speakers, although this doesn't quite have the selection of fields you're interested in.
Similarly, sonos _all_ track will report the results of the track action for all speakers
I've added a multi_group (mg) action that will group more than two speakers in a single action. Note that the target speaker will become the coordinator and the remaining speakers are the ones to be grouped (i.e., it operates differently to the group action): sonos <coordinator_spkr> multi_group <grouped_spkr_one> <grouped_spkr_two> ....

These changes are all released in soco-cli v0.4.65. Let me know if you encounter any problems.

Thanks for testing.

_all_ info and _all_ track works well but if speakers are grouped we just see the name of the coordinator, so we don’t know what are the states of the grouped speakers.

I've modified the behaviour of _all_ to include non-coordinator speakers, which I think is probably more logical. Released in v0.4.66.

sonos _all_ info andsonos _all_ trackworks well.
There is a little print problem when using  "line in" with sonos _all_ track :
sonos _all_ track :
AA:
 Playback is stopped:
   Channel:     Radio.com
   Elapsed:     0:00:00

BB: Using Line In (state: PAUSED_PLAYBACK)
CC: Using Line In (state: PAUSED_PLAYBACK)
DD: Using Line In (state: PAUSED_PLAYBACK)
EE: Using Line In (state: PAUSED_PLAYBACK)
FF:
 Playback is stopped:
   Elapsed:     0:00:00

GG:
 Playback is paused:
   Artist:                Kalax
   Album:                 Kalax
   Title:                 Carousel (feat. World Wild)
   Playlist Position:     1
   Duration:              0:04:00
   Elapsed:               0:00:01

instead of :
AA:
 Playback is stopped:
   Channel:     Radio.com
   Elapsed:     0:00:00

BB:
 Using Line In (state: PAUSED_PLAYBACK)

CC:
 Using Line In (state: PAUSED_PLAYBACK)

DD:
 Using Line In (state: PAUSED_PLAYBACK)

EE:
 Using Line In (state: PAUSED_PLAYBACK)

FF:
 Playback is stopped:
   Elapsed:     0:00:00

GG:
 Playback is paused:
   Artist:                Kalax
   Album:                 Kalax
   Title:                 Carousel (feat. World Wild)
   Playlist Position:     1
   Duration:              0:04:00
   Elapsed:               0:00:01

And for AA I don't know if "Elapsed" is justified even if "Playback is in progress" or "Playback is stopped" because it's a radio and not a track, but it's not a real problem
Thank you so much ;-)

I have another problem :  with search_artists and search_albums
sonos $speaker search_artists "cinnamon chasers" :
  Sonos Music Library Albums including Artist: Cinnamon Chasers
  =============================================================
      1: Album: A Million Miles from Home | Artist: Cinnamon Chasers
      2: Album: Aether | Artist: Cinnamon Chasers
      3: Album: Anjunadeep 08 | Artist: Cinnamon Chasers
      4: Album: Best of... | Artist: Cinnamon Chasers
      5: Album: Burn the Fire | Love Is Gone | Artist: Cinnamon Chasers
      6: Album: Doorways | Artist: Cinnamon Chasers
      7: Album: Dreams & Machines | Artist: Cinnamon Chasers
      8: Album: Drench | Artist: Cinnamon Chasers
      9: Album: Edits | Artist: Cinnamon Chasers
     10: Album: Electro Classics 2.0 (House, Deep-House, Techno, Minimal, Electronica, Future Bass and Many | Artist: Cinnamon Chasers
     11: Album: Exclusive Unreleased Music 2008 to 2012, Vol. 1 | Artist: Cinnamon Chasers
     12: Album: Exclusive Unreleased Tracks 2008 to 2012, Vol. 2 | Artist: Cinnamon Chasers
     13: Album: Excuse My French (Remixes) | Artist: Cinnamon Chasers
     14: Album: Falcon | Artist: Cinnamon Chasers
     15: Album: Great Escape | Artist: Cinnamon Chasers
     16: Album: Great Escape (Summer 2015 Mix) | Artist: Cinnamon Chasers
     17: Album: Group Therapy 215 | Artist: Cinnamon Chasers
     18: Album: Highway Pacific | Artist: Cinnamon Chasers
     19: Album: Hunter | Artist: Cinnamon Chasers
     20: Album: Hurts Too Much EP | Artist: Cinnamon Chasers
     21: Album: I Like Watching You (Diamond Cut Remix) | Artist: Cinnamon Chasers
     22: Album: Jetstreams | Artist: Cinnamon Chasers
     23: Album: Jody Wisternoff: The Story So Far | Artist: Cinnamon Chasers
     24: Album: Luv Deluxe Remixes | Artist: Cinnamon Chasers
     25: Album: Myracom | Artist: Cinnamon Chasers
     26: Album: Perfectly High | Artist: Cinnamon Chasers
     27: Album: Remix Competition: The Winners | Artist: Cinnamon Chasers
     28: Album: Reworks, Vol. 1 (A special collection of new reworks, edits & unreleased gems) | Artist: Cinnamon Chasers
     29: Album: Science | Artist: Cinnamon Chasers
     30: Album: Science Remixes, Part. 1 | Artist: Cinnamon Chasers
     31: Album: Science Remixes, Vol. 2 | Artist: Cinnamon Chasers
     32: Album: Set the Sky on Fire | Artist: Cinnamon Chasers
     33: Album: She Loves | Artist: Cinnamon Chasers
     34: Album: So Hard to Say (EP) | Artist: Cinnamon Chasers
     35: Album: Speeder | Artist: Cinnamon Chasers
     36: Album: Sunset Drive - EP | Artist: Cinnamon Chasers
     37: Album: The Archives, Vol. 4: Analog Soundscapes | Artist: Cinnamon Chasers
     38: Album: The Day That Never Came Ep | Artist: Cinnamon Chasers
     39: Album: The Elements | Artist: Cinnamon Chasers
     40: Album: Time.Body.Tears | Artist: Cinnamon Chasers
     41: Album: Two Hours Time | Artist: Cinnamon Chasers

  Sonos Music Library Albums including Artist: Americans In Paris; Cinnamon Chasers
  =================================================================================
      1: Album: Excuse My French (Remixes) | Artist: Americans In Paris; Cinnamon Chasers

  Sonos Music Library Albums including Artist: Swimming Pools; Cinnamon Chasers
  =============================================================================
      1: Album: Move to Love Remixed | Artist: Swimming Pools; Cinnamon Chasers

Note: multiple artists found ... search not saved

instead of :
  Sonos Music Library Albums including Artist: Cinnamon Chasers
  =============================================================
      1: Album: A Million Miles from Home | Artist: Cinnamon Chasers
      2: Album: Aether | Artist: Cinnamon Chasers
      3: Album: Anjunadeep 08 | Artist: Cinnamon Chasers
      4: Album: Best of... | Artist: Cinnamon Chasers
      5: Album: Burn the Fire | Love Is Gone | Artist: Cinnamon Chasers
      6: Album: Doorways | Artist: Cinnamon Chasers
      7: Album: Dreams & Machines | Artist: Cinnamon Chasers
      8: Album: Drench | Artist: Cinnamon Chasers
      9: Album: Edits | Artist: Cinnamon Chasers
     10: Album: Electro Classics 2.0 (House, Deep-House, Techno, Minimal, Electronica, Future Bass and Many | Artist: Cinnamon Chasers
     11: Album: Exclusive Unreleased Music 2008 to 2012, Vol. 1 | Artist: Cinnamon Chasers
     12: Album: Exclusive Unreleased Tracks 2008 to 2012, Vol. 2 | Artist: Cinnamon Chasers
     13: Album: Excuse My French (Remixes) | Artist: Cinnamon Chasers
     14: Album: Falcon | Artist: Cinnamon Chasers
     15: Album: Great Escape | Artist: Cinnamon Chasers
     16: Album: Great Escape (Summer 2015 Mix) | Artist: Cinnamon Chasers
     17: Album: Group Therapy 215 | Artist: Cinnamon Chasers
     18: Album: Highway Pacific | Artist: Cinnamon Chasers
     19: Album: Hunter | Artist: Cinnamon Chasers
     20: Album: Hurts Too Much EP | Artist: Cinnamon Chasers
     21: Album: I Like Watching You (Diamond Cut Remix) | Artist: Cinnamon Chasers
     22: Album: Jetstreams | Artist: Cinnamon Chasers
     23: Album: Jody Wisternoff: The Story So Far | Artist: Cinnamon Chasers
     24: Album: Luv Deluxe Remixes | Artist: Cinnamon Chasers
     25: Album: Myracom | Artist: Cinnamon Chasers
     26: Album: Perfectly High | Artist: Cinnamon Chasers
     27: Album: Remix Competition: The Winners | Artist: Cinnamon Chasers
     28: Album: Reworks, Vol. 1 (A special collection of new reworks, edits & unreleased gems) | Artist: Cinnamon Chasers
     29: Album: Science | Artist: Cinnamon Chasers
     30: Album: Science Remixes, Part. 1 | Artist: Cinnamon Chasers
     31: Album: Science Remixes, Vol. 2 | Artist: Cinnamon Chasers
     32: Album: Set the Sky on Fire | Artist: Cinnamon Chasers
     33: Album: She Loves | Artist: Cinnamon Chasers
     34: Album: So Hard to Say (EP) | Artist: Cinnamon Chasers
     35: Album: Speeder | Artist: Cinnamon Chasers
     36: Album: Sunset Drive - EP | Artist: Cinnamon Chasers
     37: Album: The Archives, Vol. 4: Analog Soundscapes | Artist: Cinnamon Chasers
     38: Album: The Day That Never Came Ep | Artist: Cinnamon Chasers
     39: Album: The Elements | Artist: Cinnamon Chasers
     40: Album: Time.Body.Tears | Artist: Cinnamon Chasers
     41: Album: Two Hours Time | Artist: Cinnamon Chasers

  Sonos Music Library Albums including Artist: Americans In Paris; Cinnamon Chasers
  =================================================================================
      **42**: Album: Excuse My French (Remixes) | Artist: Americans In Paris; Cinnamon Chasers

  Sonos Music Library Albums including Artist: Swimming Pools; Cinnamon Chasers
  =============================================================================
      **43**: Album: Move to Love Remixed | Artist: Swimming Pools; Cinnamon Chasers

It's the same with sonos $speaker search_albums "cinnamon chasers" but works well with search_tracks
So I can't play with :
sonos $speaker queue_search_number \"$num\" play_next : $speaker shuffle off : $speaker next : $speaker play

This one is intentional -- single line outputs aren't surrounded by blank lines.
BB: Using Line In (state: PAUSED_PLAYBACK)
CC: Using Line In (state: PAUSED_PLAYBACK)
DD: Using Line In (state: PAUSED_PLAYBACK)
EE: Using Line In (state: PAUSED_PLAYBACK)
FF:
 Playback is stopped:
   Elapsed:     0:00:00

However, I can make this a little neater by adding a blank line after a sequence of one or more single line outputs, i.e.:
BB: Using Line In (state: PAUSED_PLAYBACK)
CC: Using Line In (state: PAUSED_PLAYBACK)
DD: Using Line In (state: PAUSED_PLAYBACK)
EE: Using Line In (state: PAUSED_PLAYBACK)

FF:
 Playback is stopped:
   Elapsed:     0:00:00

The 'multiple artists found' issue is a limitation of the current rather lazy, implementation for saving search results (hinted at by the warning Note: multiple artists found ... search not saved).
I'll have a look at whether it can be Improved, although I think it might require some major code surgery.

Ok thank you. It was very helpfull to me.
It’s not an emergency so when you will find the time it would be great to be able to use search_artists and search_albums and why not a search_and_play command which include :  sonos $speaker queue_search_number \"$num\" play_next : $speaker shuffle off : $speaker next : $speaker play  after we enter a number 😊.
_all_ track will be perfect like this.
Thank you again for all this usefull improvement 😉

The search_artists action now saves its search results if there are multiple artist matches. It turned out not to be too bad to implement. Note that search_albums already saved its search results correctly.

Yes it’s perfect now.  search_artists and search_albums works well.
Do you know if there is a way to add to the queue all results of search_artists ?
For now I search the artist then copy the name of the album then search the album for having more than one song in the queue. But it’s ok I will stop asking you so many requests, I understand it’s a lot. Thank you very much again, I really appriciate what you have done. 😊

Do you know if there is a way to add to the queue all results of search_artists?

There's a new action called queue_multiple_search_results (or qmsr) that allows all results from the last search to be queued, or specific items and/or item ranges can be specified, e.g.:
sonos <speaker> qmsr all
sonos <speaker> qmsr 1,3,5
sonos <speaker> qmsr 1-3,7-10

Thank you it's working perfectly.
I will finally be able to enjoy a customized playlist simply and quickly on my Sonos speakers ! ;-)
Unfortunately, the play_next function has disappeared when using qmsr, so to play music, you have to do a clear_queue before the qmsr command and then play_from_queue 1 because the songs are added to the end of the queue.
In this case, the solution is to create a new queue like this: sonos $speaker clear_queue : $speaker queue_multiple_search_results all : $speaker play_from_queue 1 : $speaker if_stopped play : $speaker add_library_playlist_to_queue playlist.m3u"
Thank you again ! 😊

Unfortunately, the play_next function has disappeared when using qmsr, so to play music, you have to do a clear_queue before the qmsr command and then play_from_queue 1 because the songs are added to the end of the queue.

Yes, this is a little tricky to implement for multiple queue additions, so I've omitted it for now.
Note that you can play from the queue at the point of the last additions using pfq last_added. This will use the queue position of the first track of the set that were added.

Doing it this way without the play_next command is perfect because we can listen to the songs we have chosen and play them in shuffle mode without the risk of playing another artist or album.
I didn't know the pfq last_added I will try.
So with the pfq last_added all is fine.
I really appreciate the work you have done, it has greatly improved my Sonos installation. I wish you all the best in your projects. If I have other ideas to improve soco-cli, I will let you know, but not right away because it is already more than enough compared to what I expected.
Thank you for everything :-)

If I had time I will implement a Chat-GPT plugin to Soco-cli to install in addition, but not now. I will see in the futur because I have no more money. I have spent to much on Chat-GPT. Like this it will be possible to simply ask to Chat-GPT : "search 'Genesis' and play only all there songs with a volume set to 20 in my room 6 and activate shuffle mode...."
I will see if I have enough money and time for this.
Thanks :-)

Let me know if you make progress with the ChatGPT front-end -- would be very cool.
If I decide to invest significant further time in SoCo-CLI, it will probably be to add Sonos Cloud API integration, which I think is probably required to get good streaming service integration.
Now, I've done some tidying up and consolidated all the queue search result actions under a single action called queue_search_results (qsr), which now covers both single and multiple item use cases. (Don't worry, all the previous action names are still there and will remain so, but I've removed them from the README.)
I also figured out how to enable next|play_next for multiple selections, so that option is back.
Finally, there is now a strict option for all the music library searches, in case an exact match is preferred.

The commands queue_search_results all play_next and queue_search_results 1 play_next work very well. It's easier this way, and you are right; there's no need to put an if [ "$num" = all ] condition for playing the search results.
The play_next command doesn't play the next song but puts it after the current song, similar to next. It's a little confusing, and it would be more logical if play_next played the next music and next put the music next to the current one. However, it's okay; you can simply add next and play commands after a play_next command to achieve the desired behavior.
I'm facing another small issue with if_coordinator. I'd like to do something like: sonos AA group BB if_coordinator or sonos BB if_coordinator multi_group AA CC. Additionally, having an option like is_not_coordinator for sonos AA if_not_coordinator group BB would be helpful. This is because when I use the line-in with a Sonos connect, it automatically becomes the coordinator when music comes from the line-in, causing a problem when another Sonos device was already the coordinator before.
The commands search_albums "AA BB" strict and search_artists "CC DD" strict work fine.
Currently, I don't have enough energy to develop a Chat-GPT functionality. Teaching Chat-GPT to use a program without any errors is a lengthy process, as Chat-GPT learns by making mistakes. For each command, we must ask it why it's a mistake and to correct this error, but it may make new mistakes until it works perfectly. Each time returning to it an error message generates tokens, making it costly. While it's not impossible to achieve, it's similar to executing all the possibilities of a readme page in various ways, along with all the inventions of Chat-GPT. Additionally, each request to Chat-GPT includes all instructions (the readme file in json format), generating a lot of tokens. I think that making a plugin for Chat-GPT might be a better approach rather than creating an API like a PyPI packet soco-cli-gpt, but I'm not sure how to do it. I will explore this possibility in the future if Chat-GPT becomes less expensive to develop an API.
For making a Chat-GPT plugin it will be necessary to develop a Sonos Cloud API that allows users to interact with Sonos devices and services through the cloud. It might enable functionalities like controlling Sonos devices remotely, accessing music libraries, creating playlists, and more, all through cloud-based communication. But finally I like the idea of a local and secure program like soco-cli.
For now I prefer Claude to Chat-GPT but it has not been officially launched on the market. I will see if a Claude API offer more possibility.
Thank you again ;-)

The play_next command doesn't play the next song but puts it after the current song, similar to next. It's a little confusing, and it would be more logical if play_next played the next music and next put the music next to the current one. However, it's okay; you can simply add next and play commands after a play_next command to achieve the desired behavior.

This is intentional -- it's to allow tracks to be queued to be played next, without interrupting the currently playing track, and play_next next are just synonyms. I guess I could change the behaviour of play_next to advance playback to the just-added track(s), but as you note, one can just use the next action to do this.

I'm facing another small issue with if_coordinator. I'd like to do something like: sonos AA group BB if_coordinator or sonos BB if_coordinator multi_group AA CC. Additionally, having an option like is_not_coordinator for sonos AA if_not_coordinator group BB would be helpful. This is because when I use the line-in with a Sonos connect, it automatically becomes the coordinator when music comes from the line-in, causing a problem when another Sonos device was already the coordinator before.

It's easy to add if_not_coordinator, so that will be in the next release  (i.e., I've coded it but not yet released it).

ok thank you it will be perfect with if_not_coordinator command. No matter with play_next; indeed, it would be confusing to modify a command for users who already use this command.
Have a nice summer and & good continuation in your project

It's easy to add if_not_coordinator, so that will be in the next release (i.e., I've coded it but not yet released it).

This is released now.

Thanks. Works perfectly


pathnameIsActive() doesn't take route hierarchy into consideration (1.0.0-beta3)

pathnameIsActive() should match only the most specific corresponding route in the hierarchy and all of its parents. It currently does string matching between the given path and the current URL, which can lead to false positives.
For example, <Link to="/"> is showing as active  for all routes when they are defined as such (note that / is a sibling to the other routes, not a parent):
<Route component={App}>
  <Route path="/" component={Dashboard}/>
  <Route path="/integrations" component={Integrations}/>
  <Route path="/settings" component={Settings}/>
</Route>

Seems like this just hasn't been handled yet.
https://github.com/rackt/react-router/blob/master/modules/RouterContextMixin.js#L11

I'm taking a crack at a PR for this. Seems like RoutingUtils.getState() would get me the branch of matched routes, except it's asyncronous, so pathnameIsActive() and Router#isActive() would also have to become async. Just wanna make sure that's ok before I head down that path. @mjackson @ryanflorence

Looks like this was actually a dupe of #1441 and its corresponding PR #1465


feat: add CA cert support for helm-sync

This change adds a caCertSecretRef API field for the helm api which is analogous to the existing git/oci api fields. This can be used by users to provide a CA certificate for verifying the authenticity of the helm repository.

/assign @karlkfi


Remove I18N prefix from our scalar types

Changing all of the names of our overwritten types to their default names. This will make it easier for external clients to connect to our API, as having changed the names of all the primitive scalar types is possibly a weird gotcha.
I18NDate -> Date
I18NBoolean -> Boolean
I18NInt -> Int
I18NString -> String
I18NFloat -> Float
Also changed the return types of a couple fields in the final commit. @buckley-w-david, do those changes look okay to you?

Those return type changes seem correct to me 👍

Cool, I'll fix the linter error and then merge this in.


Empty interfaces accept anything

interface I { }
let i1: I = null;
let i2: I = function () { };
let i3: I = 0;

Ideally, interface I { } would behave the same as type I = { }.

Now all of them behave the same as {...}


Update the Global Device Endpoint and ID Scope

Open DeKitDPS.ino -> Should be DevKitDPS.ino

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

ID: 57d1d61a-9a93-7979-d562-21c6b712c22e
Version Independent ID: e485312b-15fd-b681-fd6c-855651ffd751
Content: How to use Azure IoT Hub Device Provisioning Service auto-provisioning to register the MXChip IoT DevKit with IoT Hub
Content Source: articles/iot-dps/how-to-connect-mxchip-iot-devkit.md
Service: iot-dps
GitHub Login: @liydu
Microsoft Alias: liydu

@perkops Thanks for the feedback! We are currently investigating and will update you shortly.

@liydu Would you please review the issue and the PR? Thanks!

@perkops Thanks again for your help! I merged the PR with the fix so we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


NEW INDEX: LAI (Utilized to estimate foliage cover and to forecast crop growth and yield)

I found the following index and I think it should be included.
LAI=SpectralIndex(
    short_name='LAI',
    long_name='Utilized to estimate foliage cover and to forecast crop growth and yield',
    formula='3.618 * (g * (N - R) / (N + C1 * R - C2 * B + L)) - 0.118',
    reference='https://doi.org/10.1016/S0034-4257(01)00342-X',
    application_domain='vegetation',
    date_of_addition='2024-07-23',
    contributor="https://github.com/eomasters-repos"
)

Hi @eomasters-repos!
Thank you for the suggestion. However, LAI (Leaf Area Index) is not an spectral index and wouldn't fit for the scope of ASI.
Cheers!
David

Okay, But I wonder why EVI is qualified as a spectral index, but LAI not. It is simply derived from EVI.

Hi @eomasters-repos!
The main reason EVI (Enhanced Vegetation Index) is classified as a spectral index and LAI (Leaf Area Index) is not, lies in their definitions and how they are derived:
Spectral Index Definition: A spectral index is typically a quantitative measure derived from remotely sensed spectral reflectance data. It involves mathematical combinations of different spectral bands, which are designed to highlight specific properties of the Earth's surface, such as vegetation, water, or soil.
EVI: The Enhanced Vegetation Index (EVI) is indeed a spectral index. It is calculated directly from reflectance values in different spectral bands (specifically the blue, red, and NIR bands). Its formula is designed to optimize the vegetation signal, correct for atmospheric conditions, and reduce soil background noise.
LAI: The Leaf Area Index (LAI), on the other hand, is a biophysical parameter that describes the total leaf area per unit ground area. It can be estimated through various methods, including empirical models that use spectral indices like EVI or NDVI as inputs. However, LAI itself is not calculated directly from spectral reflectance data in the same manner that EVI is. Instead, LAI often requires additional models, ground-truth data, or indirect methods for estimation.
In summary, while EVI is a spectral index derived directly from specific spectral bands using a set mathematical formula, LAI is a derived biophysical parameter that may utilize spectral indices among other data sources but is not a spectral index itself.
I hope this clarifies the distinction!
Cheers,
David


Admin UI 1675

Problem
#1675 Admin UI Bug
Solution
Modification to add_success_message, Adding tracking of IMPORT_TYPE_DELETE and IMPORT_TYPE_SKIP.
Modifications where made to a number of Test to insure  expected Results where up to date.
Acceptance Criteria
The Test I have added is test_import_for_deletion line 143 of test_admin_integration
What the Message looks like now:

I have NOT added the changes to the documentation.
1 Failed Test, Import Legacy Book, Failure due to incorrect string return.

Regarding
Git merge release-4
Not something we can merge.
I'm not sure how I am to merge a branch from your repo, into a branch on my fork.

Thanks Rob - I have changed the base branch on the PR to release-4 and we now have your changes, but we're missing the tests.

working tests now, seems to be String related again, should be done within the next hour. If nothing comes up.


Day 467

Good morning! Here's your coding interview problem for today.
Given a real number n, find the square root of n. For example, given n = 9, return 3.

Identical to Day 129: https://github.com/vaskoz/dailycodingproblem-go/issues/263


add retry for TransferSui transaction builder call at faucet

This PR adds a simple retry functionality for calling gateway's transaction building api transfer_sui. Also it extends the RpcError to include the error code for more info.
Context
We started to observe a very strange thing recently:
When running the cluster test  on the CI pipeline (aka the runner) against continuous cluster, gateway always fails get_object through aggregators, thus faucet errors out when building Transaction for transferSui.
example error msg:
2022-08-12T21:06:29.352719Z ERROR sui_faucet::faucet::simple_faucet: Encountered error in transfer sui: Err(RPC call failed: ErrorObject { code: ServerError(-32000), message: "Too many authority errors were detected for get_object_by_id: [(k#839e99f8b03f0f5563d6cd9cc39e10a8cf483ad2775aecbb927031370925ef4e, RpcError(\"transport error\")), (k#89cafd721eeb1b13483d5fb0968500e78103e8146b45edb30d93781d946d0aeb, RpcError(\"transport error\")), (k#e97638a9e10b9cc46d85b81191a60a6a6fcae63dacd811c07502db9c5cfc55b5, RpcError(\"transport error\"))]", data: None }

However when triggering the test locally, it does not have this problem at all.. The interesting part is regardless of where the test harness runs, gateway shouldn't behave differently, not to mention faucet is hit in the same way too.
We don't see this issue in any other apis such as execution_transaction, but probably just because they have retries already

@longbowlu great observation. If I understand correctly, we don't know the RC, but we this as a stopgap?

@longbowlu great observation. If I understand correctly, we don't know the RC, but we this as a stopgap?

correct. I'm very confused. But gateway is really doing strange things recently.

@longbowlu great observation. If I understand correctly, we don't know the RC, but we this as a stopgap?

correct. I'm very confused. But gateway is really doing strange things recently.

good thing its going away :)


TypeError: Cannot read property 'autoUpdater' of undefined at install

Hello! When I'm trying to use updater.install() but it seems that updater is undefined. Here you can find the source code.
Details

Electron 1.0.2
electron-gh-releases 2.0.3 (Also tried 2.0.2)

Source Code
const updater = new GhReleases(autoUpdateOptions);

updater.on('error', (event, message) => {
  console.log('ERRORED.');
  console.log('Event: ' + JSON.stringify(event) + '. MESSAGE: ' + message);
});

updater.on('update-downloaded', (info) => {
  console.log('Update downloaded');
  confirmAutoUpdate(updater.install);
});

The Error
Uncaught Exception:
TypeError: Cannot read property 'autoUpdater' of undefined
    at install (/Applications/Gitify.app/Contents/Resources/app.asar/node_modules/electron-gh-releases/GhReleases.js:197:11)
    at Function.<anonymous> (/Applications/Gitify.app/Contents/Resources/app.asar/main.js:45:9)

Screenshots
The value of updater:

The error:

Update
It looks like it is actually updating the app but it still throws that error

Looks like the problem was that I had to pass the updater object instead of the updater.install function. Works great now!


docs: specify docutils 0.12

The new 0.13.1 release appears to be break our docs build so just
require 0.12 for now. Also upgrade sphinx to 1.5.0.

@lyft/network-team


chore: openapi proto annotation

Closing in favor of https://github.com/bucketeer-io/bucketeer/pull/1087


Broker apb rpm

Create automation-broker-apb-role RPM

Coverage remained the same at 38.907% when pulling 8659b4f7d8cbcadcbad6bbdba05bb491158d90ff on djzager:broker-apb-rpm into a5be9dd9bc3eb15ee613e90083698aad584f92a0 on openshift:master.


Created OSX playbook

In preparation for a shiny M1/M1X machine, make this playbook OSX-compatible.

Moved to https://github.com/artis3n/osx-dev-setup/issues/2


Feature/hit 152

Automated below test cases

Area count verification of geo heatmap for Health Board and council area for Cases and Death button selection
verifying single value bar visibility
verifying FACTS container visibility
verifying NEWS container visibility
verifying Timespan bar for all type of charts with each timespan selection

Good work so far - a few comments

@donal-s Thank you for all review and comments. I will make all the suggested changes and push them for re-review.


feat: ensure all delete pipeline params are passed to pods

This commit ensures that we pass through all the fields from the Kratix Pipeline object to the Pods that are created for a delete Job.

Fixes #95
The functionality for configuring Jobs for Pipelines now sits in a central place such that any future updates to the properties of Containers will applied to both Delete and Configure pipelines


Rename project to Shindig for Rdio

Still needs the new domain name, but that could be a separate pull request


claws-mail: add glib_networking for fancy to load HTTPS content (for master)

For bug #10421.  Tested locally and works.

Travis passed thanks.


Stop Loss

I do a little naive query, positions does not have a defined stop loss, only one is executed when it reaches profit?

I am not sure I understand your question. Can you give me more explanation?

I already understood that it does not use a stop loss, would it not be nice to incorporate it?

Sorry for the English, but yes, what I mean is if the incorporation of a stop is in the plans, example: you buy a currency in $ 100, this currency breaks the support and falls to $ 80, you could add an option to put a sell order if the percentage is very negative.

Oh @chopeta made me realise what you are asking.
Now I understand what you are trying to say.
As mentioned in #72, I won't add that feature.

I assuem your question is answered, I close the issue. Please open a new issue if you have a new question.


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-k8s-28-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4601

Questions ?
Please refer to the Backport tool documentation


change origin schema in ReduceResolution method of histogram and float histogram

          @fatsheep9146 / @beorn7 shouldn't there be `h.Schema = targetSchema`? While the comment only speaks about spans and buckets, name and the API of this method would make me expect that the whole histogram gets reduced as such.

Same question applies to the integer histogram below.
Originally posted by @linasm in https://github.com/prometheus/prometheus/pull/13001#discussion_r1387548416
fix the bug found by @linasm in #13111 13001

@beorn7 Thanks for your quick review, I fix as @linasm suggests, could you have a quick review again?


Change field name for Rail Line Name from “RLNameE” to “RLName”

Structural change between versions 1 and 2 or NENA-STA-006
Change field name for Rail Line Name from “RLNameE” to “RLName” in the RailroadCenterLine layer.
Source
NENA-STA-006.2-2022 from sub-bullets in "Specific structural changes to the Data Model that were made:" bullet on page 13 under the Reason for Issue/Reissue section.

Adopted by Data Model Template working group Consent Agenda on 2022-11-23.


Add tests for vault create command when vault_name arg is passed

Current
We have some tests covering the command when creating a vault for a given node (passing the node argument). We recently added a new argument vault_name that creates a vault that is not attached to any node.
Desired
We want to add a test on the commands.bats file to cover this case.

We love helping new contributors!
If you have questions or need help as you work on your first Ockam contribution, please leave a comment on this discussion.
If you're looking for other issues to contribute to, checkout this discussion and labels -  https://github.com/build-trust/ockam/labels/good first issue or https://github.com/build-trust/ockam/labels/help wanted

Shouldn't ockam vault create --vault-name throw error if vault with same exists?
https://github.com/build-trust/ockam/blob/develop/implementations/rust/ockam/ockam_command/src/vault/create.rs#L61

Shouldn't ockam vault create --vault-name throw an error if a vault with the same name exists?

I've just saw your changes on your PR, it makes total sense to return that error :+1:


Replace phantomjs with puppeteer

Hi @jkphl :wink:
This is an attempt to get rid of the phantom.js dependency (see #254):

replaced phantomjs with puppeteer
replaced svg2png with sharp.

So far I have encountered the following problems:

All PNG renderings with puppeteer differ very slightly from the originals from phantom. Because the images are not pixel-perfect I had to replace all expected images for the tests to be green again. Because a pixel-perfect for PNG renderings can not be ensured I would consider this a breaking change.
The sharp library prints a "CSS parsing error" while saving a SVG as PNG. I'm not sure were exactly this problems occurs and why. I'm going to create an issue with the sharp library to see if this can be solved.
The test case view\png\css.horizontal.mixed.png is still failing.

I would consider this a first proof of concept and would be happy If you folks could test this branch an see if it still works in you setup.

@mojoaxel Hi Alex! Awesome, thank you! I will review this as soon as possible, but it will take me some time due to general overload. Please bear with me. :)

@jkphl are we doing this?

@jkphl are we doing this?

let me know it I can help. I met @jkphl last week and this PR came back to mind. I'll try to have a look this week and see if I can improve it. I still think it's worth a breaking change.

Sorry all. I'm totally swamped with tasks for months now and I just don't find any time to take care for my OS side projects.
@mojoaxel very thankful for your efforts! Maybe we should have a personal chat before you go a head and do something about this? You can catch me in the office whenever you find some time to call me.

Thanks to @bung87 we could improve this further. Now there are still 3 tests failing and we should talk about on how to handle this!
creates visually correct sprite with - packed layout
expected

current

creates visually correct sprite (horizontal.mixed)
expected

current

creates visually correct sprite with - packed layout

Strangely I get the same failed tests also with master. So it looks like this problem has nothing to do with this PR.

While the debate here goes on I published the phantomjs and svg2png free version on npm:
@fullstax/svg-sprite

While the debate here goes on I published the phantomjs and svg2png free version on npm:
@fullstax/svg-sprite

Hey I just tested the lib and I encountered differences between our old sprite and the new one:

But there is no need to provides fixes. We just continue to use the old lib.

@gabbersepp, that's an optimalisation, those ones and zeros are booleans, that's why the spaces can be removed.

@gabbersepp, that's an optimalisation, those ones and zeros are booleans, that's why the spaces can be removed.

Good to know. Is there a possibility to disable this? I just want to see if both sprites are absolutly equal.

Good to know. Is there a possibility to disable this? I just want to see if both sprites are absolutly equal.

No clue, but maybe you can optimise the old sprite file with svgo?

@gabbersepp My changes introduce a major change! It is naturally not a perfect drop-in replacement. The results should be optically and functionality but not binary identical!

@gabbersepp My changes introduce a major change! It is naturally not a perfect drop-in replacement. The results should be optically and functionality but not binary identical!

Thanks for your work! I did an "optical" comparization and everything seems good.

@mojoaxel i dropped your plugin replacement and puppeteer came back with an error file://dummy.svg not found

@mojoaxel i dropped your plugin replacement and puppeteer came back with an error file://dummy.svg not found

@mojoaxel I'd be interested in this after we land some of the other open PRs first to drop Node.js 8.x and sort out some things.
The test failures are something I haven't figured them out. Not sure if it's the test code, phantomjs or something in Node.js but happens in all Node.js versions >= 10.
Also, it'd would be indeed nice to lazyload puppeteer, make it an optional dependency and throw a nice error if someone tries to use the feature that needs puppeteer.

In fact, we could land the looks-same patch much sooner if you could make a PR for that separately.

Rebased this. We need to finish with #398 first.
What would help is if:

someone could split the looks-same patch. I gave this a go in https://github.com/jkphl/svg-sprite/commit/8eea02e332a739110e3ddd4e7d79a5e1ff2340b2 but I'm not 100% sure it's OK yet
make puppeteer optional
see if we really need sharp
this PR still doesn't seem to fix the Node.js > 10 test failures
update puppeteer to the latest version

Rebased and updated the TODO in the PR description. Any help would be appreciated to sort the TODO so that we can land this.

@ert78gb might be easier if you made a new PR with your fixes. See also the TODO in the PR's first post.

Yesterday I wanted to investigate the #421 but on Mac, not every test pass. If I check the diff png I don't see any difference. I ran the #417 on my machine and every test passed.
Don't you think it worth adding windows and mac to the test matrix?
If you merge #417 I will create a new PR.

@ert78gb that's normal because phantomjs has known issues with DPI and produces different images, at least on Windows. My plan is to at least add Windows on CI after we remove puppeteer.
Temporarily you could use the CI, that's what I've been using all this time too. When tests fail, the images are uploaded on CI.
So, the puppeteer change doesn't need to be tied to looks-same, they are 2 different things AFAICT.
#417 isn't ready either AFAICT; it has its own TODO.

Wait for CI is increase the development time, but I will try. CI is great to run the test matrix, but when the tests fail in local ... :(
If you have TODO for a PR and it is not a blocker I think worth creating a separate issue. Do everything in 1 PR is not efficient.
I think this refactoring period worth doing many small PR, because the review is much easier.
I am a little bit worried about this project because wait 2-3 week for a PR merge not good.
If I see well not @XhmikosR the bottleneck.

Well, we are all volunteers, so you know. I explained to you the current TODOs and I have already broken this PR into 2 parts.
Unfortunately, I can't help you with CI, it is what it is. And it was much worse before my recent patches; they never passed on Node.js > 10. Although, I'm tempted to just drop Node.js 10 support too being that it goes EOL at the end of April. I'd still like to have a stable sorting algo, but it's one less thing to worry about.


Add v1.3.0 perf and scale benchmarks data

What this PR does
Before this PR:
There is no doc for v1.3
After this PR:
This PR adds  perf and benchmarks data doc for v1.3 release.
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

Add perf-scale benchmarks for release v1.3

/lgtm
Thanks @Sreeja1725

/approve

/cherry-pick release-1.3

PR looks great but a related question quickly while folks are looking at this for 1.3, I see the following still listed:
https://github.com/kubevirt/kubevirt/blob/2eb515574f9f963e9fe883f87f4bb5a31fa45cb9/docs/perf-scale-benchmarks.md#L22
Are there any plans to provide this? Is there anything I can do to help with this?

@lyarwood yes there are a bunch of steps needed for getting the instance types metrics, your help will be very much appreciated. I think the best way would be to file an issue with sig/scale label so we can track it for 1.4 and discuss in sig-scale calls.

/retest-required

@xpivarc / @lyarwood someone needs to give this PR an approve tag. Please take a look, thanks

@alaypatel07 @Sreeja1725 Do you want to re-run with https://github.com/kubevirt/kubevirt/pull/12249 ?

@xpivarc the release benchmarks will not change since the fix will show data for 1.4 code due to branching. We don't have the ability to run on release branches yet.

@xpivarc the release benchmarks will not change since the fix will show data for 1.4 code due to branching. We don't have the ability to run on release branches yet.

Thanks
/approve


Two instances of new-relic browser app targeting diferents accounts are colliding

two instances of new-relic browser app targeting diferents accounts are colliding
Description
I am part of a team developing a widget that gets integrated into various websites. To monitor the widget's performance, we employ New Relic MicroAgents usint this library available at https://www.npmjs.com/package/@newrelic/browser-agent. However, a challenge arises as this widget is loaded onto pages that already have the New Relic Browser tracking code embedded (using the JS snippet provided by New Relic in the application settings). Consequently, when clients load the widget, it appears to collide with the existing MicroAgent instance, causing the New Relic tracking of their websites stop sending data to this new relic and start sending data to our account it. it seems that the microAgent is overriding the information  of the other agent
Is there a solution to circumvent this issue and enable multiple New Relic agents to target different New Relic accounts simultaneously on the same website?
Steps to Reproduce

use a JS snippet code provided by new relic for browser applications and execute in a script targeting to new-relic account A
load a MicroAgent instance  targeting to new-relic account B

Expected Behavior

every script should send the data to it's respective account

Relevant Logs / Console output

ex: BrowserApp
ex: chrome last version

npm package is using: 1.238.0
JS snippet browser agent: nr-loader-spa-1221.min.js

Thanks for the additional info @Khaos93 . We have made a few changes in the agent since 1221 that could help with this issue. Is there any way you could try upgrading the agent that is injected on the page to the latest version?

we already update the agent to 1.247 the version that new-relic recommend us in the browser-application but the issue is still happening

Thanks @Khaos93 . Just to confirm, you tried using 1.247 for both the page agent and the micro agent? If so, I will try to look into this as soon as possible.

yes, the test was using the 1.247 version for both the page agent and the micro agent, thanks

Hi @Khaos93 . I was able to setup a test case locally using https://github.com/mits-gossau/event-driven-web-components-realworld-example-app as a test base project. The page loads a full agent and the article page component loads a micro agent. In our testing, we do not see the page level agent changed to start reporting to the micro agent app ID. Is it possible for you to provide a small reproduction of this issue?

Hi @Khaos93 . I was able to setup a test case locally using https://github.com/mits-gossau/event-driven-web-components-realworld-example-app as a test base project. The page loads a full agent and the article page component loads a micro agent. In our testing, we do not see the page level agent changed to start reporting to the micro agent app ID. Is it possible for you to provide a small reproduction of this issue?

@patrickhousley wondering if you might have the test code you used against this https://github.com/mits-gossau/event-driven-web-components-realworld-example-app repo that you can share?

Hey @shaun0024 let me reopen this and recreate the code for you.

Hey @shaun0024 let me reopen this and recreate the code for you.

Thank you @patrickhousley , much appreciated

@shaun0024 Please find attached the example app. Just use python3 -m http.server in the root directory to start the server. The src/index.html file contains a a full agent using copy/paste and loading assets from our CDN while the component src/es/components/molecules/TagList.js has a micro agent.
When you load the page, you will get data for the full agent in the page and a PageView and JSError from the micro agent.  You will need to update both agents with valid license keys and settings from New Relic.
event-driven-web-components-realworld-newrelic-test.zip

@shaun0024 Please find attached the example app. Just use python3 -m http.server in the root directory to start the server. The src/index.html file contains a a full agent using copy/paste and loading assets from our CDN while the component src/es/components/molecules/TagList.js has a micro agent.
When you load the page, you will get data for the full agent in the page and a PageView and JSError from the micro agent.  You will need to update both agents with valid license keys and settings from New Relic.
event-driven-web-components-realworld-newrelic-test.zip

Thank you very much @patrickhousley!

@shaun0024 I am going to close this ticket due to the lack of engagement. If there is a bug or issue you would like us to look at, please feel free to open a new ticket.


Support for more languages

I'd love to set at least the web part of Ao in more languages, like Spanish.

Ouch... I forgot to add the feature-request label...

@earthwormjimx3 Why don't you start translating it yourself? The source code is available after all...

@earthwormjimx3 Why don't you start translating it yourself? The source code is available after all...

Doesn't the source code exclude the website components?

@earthwormjimx3 This app is more a wrapper for the front-end. If the source code excludes the front-end then you shouldn't even be asking because it's not possible for anyone to do what you are requesting.
Also note that the link above says ISSUES not "FEATURE REQUESTS". In open source, if you want a feature, you provide it yourself. This field is for defining issues and putting forth bug reports to the team.

Ah! Alright. That's my own mistake, and I apologise for that.
Thanks in advance for helping me know about this 😅

If you want to request features then you can do so here: https://gitter.im/klaussinani/ao
If you want the feature to be added more quickly, you could consider supporting the developers work here: https://github.com/sponsors/klaussinani
Otherwise you could check the source documents and contribute the translation yourself and then make a push request to have it added.

Alright! I'll evaluate these options and see what I can do.
And, next time, I'll be sure to not misuse the issues section on any GitHub project like I did right now.

By the way @earthwormjimx3. This might be of some use. It's literally available in the main readme: https://github.com/klaussinani/ao/blob/master/contributing.md#translating-documentation

@earthwormjimx3 please close this "issue" at the bottom of this page and refer to the gitter.im link above that I mentioned for making this request.


Make CDP builds run in parallel

Enable concurrent steps
Enable dependencies caching
Move docker images build into CDP pipeline and remove build bash script
~Add test reporting~ (moved to a separate ticket - #1298)

Fixes #1279

Codecov Report

Merging #1288 (83c15f3) into master (f923592) will increase coverage by 10.23%.
The diff coverage is n/a.

:exclamation: Current head 83c15f3 differs from pull request most recent head 0286ab2. Consider uploading reports for the commit 0286ab2 to get more accurate results

@@              Coverage Diff              @@
##             master    #1288       +/-   ##
=============================================
+ Coverage     76.03%   86.27%   +10.23%
+ Complexity     1017       85      -932
=============================================
  Files           187       20      -167
  Lines          2938      255     -2683
  Branches        508       16      -492
=============================================
- Hits           2234      220     -2014
+ Misses          435       25      -410
+ Partials        269       10      -259

Impacted Files
Coverage Δ

...lin/org/zalando/zally/apireview/EndpointCounter.kt

...src/main/kotlin/org/zalando/zally/core/ast/Util.kt

...src/server/dev/webpack-dev-server-proxy-handler.js

...alando/zally/ruleset/zally/NoProtocolInHostRule.kt

...alando/zally/ruleset/zalando/ExtensibleEnumRule.kt

...ly/ruleset/zally/StringPropertyLengthBoundsRule.kt

...r/src/main/kotlin/org/zalando/zally/Application.kt

...alando/zally/ruleset/zalando/NoVersionInUriRule.kt

...ando/zally/ruleset/zalando/CommonFieldTypesRule.kt

...org/zalando/zally/rule/SupportedRulesController.kt

... and 157 more

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 f923592...0286ab2. Read the comment docs.

There is a bug with an infrastructure tool. Waiting for a reply from infrastructure team.

Depends on #1295

Sorry, for not reviewing this so long.
I still would like to have small scripts or a Makefile with targets to execute each step also on a local machine for testing. However, I will approve and leave it for a later change.

:+1:

@tkrop there is build-and-run.sh which does the same.


Dockerfile.runtime: Pull in custom iproute2 changes

Pull iproute2 from https://github.com/joestringer/iproute2/releases/tag/4.20.0-1ubuntu0bjn2 .
This facilitates #6618 by allowing static data loads from the code in #7095 .
This PR pairs with https://github.com/cilium/packer-ci-build/pull/119.
To do:

[x] Build and update references for new cilium-runtime image
[x] Pull in SERVER_VERSION from the new VM image

This change is

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please

test-me-please


Nightly release Windows CLI failing

The Windows CLI is not created (cross compile script)

It's a regression due to
../../go/pkg/mod/github.com/container-tools/spectrum@v0.6.27/pkg/builder/build.go:219:38: undefined: syscall.Stat_t
../../go/pkg/mod/github.com/container-tools/spectrum@v0.6.27/pkg/builder/build.go:220:38: undefined: syscall.Stat_t


revert PR#245 and #241 for gemm performance regression

PR#241 caused performance regression for GEMM performance, and PR#245 depends on PR#241, so we have to revert both to avoid the GEMM performance regression.
After reverting these two PRs, the best performance we can get for GEMM is (Unit: TFLOPS, larger is better.):
         M      cuBLAS     Triton
0    256.0    2.036070   1.466540
1    384.0    5.573140   3.976341
2    512.0   11.570494   8.224126
3    640.0   23.918249  12.900787
4    768.0   34.110305  19.391473
5    896.0   49.677011  25.328279
6   1024.0   59.918627  31.880696
7   1152.0   50.825260  34.094899
8   1280.0   68.985262  42.555845
9   1408.0   84.278666  42.446917
10  1536.0   58.149528  51.888298
11  1664.0   80.549702  42.535283
12  1792.0   90.938448  49.404061
13  1920.0  102.045671  51.229645
14  2048.0  115.828971  55.490534
15  2176.0   75.360647  56.093793
16  2304.0   84.232423  50.623200
17  2432.0  106.582439  56.215227
18  2560.0   99.156121  58.254122
19  2688.0  108.914707  57.816471
20  2816.0  109.484449  55.537322
21  2944.0  118.042138  58.213223
22  3072.0  114.425998  57.357950
23  3200.0  111.455590  56.873042
24  3328.0  105.675142  60.552494
25  3456.0  113.927424  58.105592
26  3584.0  121.430369  58.422145
27  3712.0  109.664204  60.066013
28  3840.0  114.325324  60.801311
29  3968.0  122.348805  61.021442
30  4096.0  129.113578  62.631608

@alefimov-amd How does this affect your current work of vec load?

How does this affect your current work of vec load?

If this is merged, I definitely need to rework some code, I think this is a work for ~1/2 a day

Could you take a look at https://github.com/ROCmSoftwarePlatform/triton/pull/269 ?
It introduces switch between fast and slow codegen paths for dot operands loading.
I've tested it on FA and it took performance back

@binarman Thank you Alek. I'll take a look at https://github.com/ROCmSoftwarePlatform/triton/pull/269 next Monday and check the performance. We'll then decide if we still need to merge this one.

Given #269 doesn't yet mitigate, I'll merge this revert until we have things working.


"Unlicensed" in package.json, but license file is MIT

See this.
...
"license": "UNLICENCED",
...

No don't close this GitHub I haven't accepted the #10 pull request! 📦


can u add docker, docker compose, http, webdav and ftp support?

can u add docker, docker compose, http, webdav and ftp support?

Hello, wdym about docker and docker compose? :thinking:
You don't need a docker/docker-compose to use this package. Just add the package to the requirements.txt file on your project :grin:

am use to use to docker and docker compose to deploy and maintain open source projects, it makes management easier than installing stuff in the host os. if u can make this project into a docker image i will appreciate it.


[Docs] Add End of Support plan to POS UI Extensions

Background
Part of https://github.com/Shopify/pos-next-react-native/issues/43667
Resolves https://github.com/Shopify/ui-extensions/issues/2295
Solution
Adds a section to the Versions page describing the End of Support Plan for POS UI Extensions.
Tack-on: Removes customValidator from FormattedTextField
🎩
https://shopify-dev.ui-extensions-k324.nathan-oliveira.us.spin.dev/docs/api/pos-ui-extensions/unstable/versions
Checklist

[X] I have :tophat:'d these changes
[X] I have updated relevant documentation

I wonder if theres a way to put the notice as a "note" so it stands out and doesn't get lost in the version log. We can probably be committed with putting future change log sections underneath this section but just a thought!

https://shopify.dev/docs/api/usage/versioning --> "Each stable version is supported for a minimum of 12 months. This means that there are at least nine months of overlap between two consecutive stable versions. When a new stable version is introduced and contains changes that affect your app, you have nine months to test and migrate your app to the new version before support for the previous version is removed."
Instead of updating POS UI Ext dev docs with versions supported, we should have POS UI Ext listed on the above Shopify API versioning. This would be consistent with other Shopify extensibility practices.


Integration test for Stackdriver

Create a fluent-bit agent that generates dummy logs with a random logid which we then query for in the integration test.

LGTM


Tools: Move fpgainfo boot page info to board specific modules

-boot page info is different  from N3000 card and N6010 cards,
-N3000 boot page info  Factory or user
N61010 boot page Factory or user1 or user2
Read power_on_image  syfs string from DFL MAX10 feature and find boot order from sysfs string.
-cat /sys/class/fpga_region/region0/dfl-fme.0/dfl_dev.2/n6010bmc-secure.2.auto/power_on_image  fpga_user2 fpga_user1 fpga_factory
Signed-off-by: anandaravuri<EMAIL_ADDRESS>

Coverage decreased (-0.08%) to 63.486% when pulling d925d9644fc7a3b8bdf332d568e36ee7282c55ff on aravuri/fpgainfo_boot into 4b8ce45f270e7a30a7da1a7c384137d802701f52 on master.


add ambertools version in command line?

if not, always install newest version?

Always newest version.  We only release updates against the latest version.  This means we only support the latest version.
There should be no option to install an unsupported product.

cool. I agree.


Drop support for macOS 10.11 and 10.12

VS Code Version: 1.56.0
OS Version: OSX El Capitan 10.11.6

Steps to Reproduce:

Try to start Code on OSX 10.11.6 (El Capitan)

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

See the attached crash_report.txt file
crash_report.txt

I've been getting Visual Studio Code freezes too which may be Electron related.

OS Version: Windows 10 Pro 64bit, 20H@, 19042.928
Visual Studio Code: 1.56.0

My symptoms are that VSC works fine for some days then, all of a sudden, freezes on startup. After killing it via task manager rerunning results in a freeze on startup. The uninstaller freezes (so that I can't uninstall it). The installer freezes (so that I can't reinstall it, over an existing install). Another electron based app, Typora, opens but menu command can't work (so Typora sort of freezes too).
Other parts of Window become frozen. For example (Win Search > "Restore" > "Create a restore point" > The  "System Properties" Dialog becomes frozen).
Restarting Windows doesn't resolve this. Instead, as a temporary work around, I've had to:

Restore Windows to an earlier restore point that avoids going through "System properties" (Windows Start > Settings > Update & Security > Recovery > Advanced Start-up [Restart now] > {Once restarted choose to recover from a restore point}); and
Immediately upon restart uninstall my Electron apps (Visual Studio Code and Typora).

My suspicions are there is some interaction that is causing the freeze, between one or more of the following:

Electron.
Windows Update.
The Powershell extension (this was recently installed).
The Visual Studio Code terminal (when it tries to load a Powershell session).
That my version of Powershell is installed via the Store.
Windows Terminal, Preview edition.

I've tried opening VSC with code --disable-gpu, as advised at https://code.visualstudio.com/docs/supporting/faq#_vs-code-gets-unresponsive-right-after-opening-a-folder. That didn't work. I'm on Nvidia drivers 456.71 with a GTX 1660 TI. And downloading to the latest drivers is something I'm about to do.
These problems occur on one of my machines (my desktop) but not another (my laptop)
So, just as for @veriotis's post, there's not much to go on to help anyone who isn't experiencing a freeze to be able to reproduce the problem. And my freezes might have a different cause to the one @veriotis is experiencing. But hopefully I've provided some clues that someone else experiencing a freeze might pick up on. That is, to help us narrow in on a cause.

@deepak1556

VS Code Version: 1.56.1
OS Version: OSX El Capitan 10.11.6
For the DMP-file see the attached zip file

vsc-1.56.1-crash.zip
It looks like the Electron crash reason is always associated with spdlog.node logging!

@veriotis can you attach the crash report following the steps at https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-and-symbolicating-local-crash-reports, thanks!

Im also seeing instant crash using 10.11.6
after using this code i get this prompted in the terminl
[0512/130304.252922:WARNING:process_memory_mac.cc(93)] mach_vm_read(0x7fff577e0000, 0x2000): (os/kern) invalid address (1)
[0512/130304.935965:ERROR:http_transport_mac.mm(283)] A server with the specified hostname could not be found. (NSURLErrorDomain -1003)

@veriotis can you try with the latest insiders https://code.visualstudio.com/insiders/ which has updated spdlog version.
@schroef it should either be code --crash-reporter-directory /tmp/vscode-crash or open -b com.microsoft.VSCode --args --crash-reporter-directory /tmp/vscode-crash

@deepak1556 I've just tried with the latest insiders release, but it's the same behavior and crashing too in the spdlog.node context ...
vsc-insiders-crash.zip

Operating system: Mac OS X
10.11.6 15G22010
...
Crash reason:  EXC_BAD_INSTRUCTION / EXC_I386_INVOP
Crash address: 0x11a2a44c3
Process uptime: 1 seconds
Thread 0 (crashed)
0  spdlog.node + 0xa4c3
rax = 0x0000000000000001   rdx = 0x0000000000000000
rcx = 0xffffffffffffff01   rbx = 0x00007fa960c8d6f0
rsi = 0x0000000000000038   rdi = 0x0000000116b04a00
rbp = 0x00007fff51712c90   rsp = 0x00007fff51712c40
r8 = 0x0000000000000010    r9 = 0x00000000fffffe00
r10 = 0x0000000000000009   r11 = 0x00007fa960c00000
r12 = 0x00007fa960c8d700   r13 = 0x000000011a2dc0f8
r14 = 0x0000000000000000   r15 = 0x9ae16a3b2f90404f
rip = 0x000000011a2a44c3
Found by: given as instruction pointer in context
1  spdlog.node + 0x9eb8
rbp = 0x00007fff51712d20   rsp = 0x00007fff51712ca0
rip = 0x000000011a2a3eb8
Found by: previous frame's frame pointer
2  spdlog.node + 0x8ac3
rbp = 0x00007fff51712d50   rsp = 0x00007fff51712d30
rip = 0x000000011a2a2ac3
Found by: previous frame's frame pointer
3  ...

The problem is with binary node modules located in VSCode.app/Contents/Resources/app/node_modules.asar.unpacked/
spdlog, native-keymap and vscode-sqlite3 were compiled with SSE4.2 optimizations and crash VSCode on older macs that can't upgrade beyond macOS 10.10 and 10.11 due to lack of SSE4 support
Node modules must be rebuild with -mcpu=core2 or macOS 10.10 / 10.11 (10.12 probably too) support should be removed.
Rebuild may be complicated for universal binary, but should be easy for x86_64-only build.

@digital-pers0n If a build/compilation with SSE4.2 optimizations is the cause of evil here, then the responsible people for the VSCode Mac related build processes should take this into account. Otherwise VSCode isn't OSX 10.11.6 compliance at all any more and thus not usable on these MacOS systems.
@deepak1556 You should cross-check this (SSE4.2 optimizations) with the Mac related build process settings, since it probably influences the overall app behavior for Mac OS systems <= 10.12 then here.
BTW nothing changed in this behavior so far for VSCode v.1.57, same sort of crashing, thus actual VSCode versions are unusable on OSX 10.11.6 (El Capitan) systems!

@veriotis just checking since the issue is > 4 months old, are you still facing the issue in the latest build ? If not we can close this I guess.

Noting I'm not the OP and @deepak1556's earlier request to me was reasonably to open a separate issue (given I'm on Windows rather than the OP's OSX), I'll mention that I tracked my issues down, about those 4 months ago, to a Sync problem. That is, I got so far as establishing that turning on Sync Settings caused the freeze (both under VSC and Preview VSC).
So if anyone was highly motivated to try to reproduce a freeze with Sync Settings on, they'd be doing us all a great service. But, with respect to this sync issue, it would be reasonable to close the current issue on the grounds it's encumbent on me to open a new one and try to reproduce the freeze under the latest version(s) of VSC.

Still (or again) crashes on BIg Sur 16'' Macbook Pro.
When I start VSCode from within Applicatiosn folder, it crashes after startup. If I start it from another folder, it runs - how comes?

Still (or again) crashes on BIg Sur 16'' Macbook Pro.
When I start VSCode (1.6.1) from within Applicatiosn folder, it crashes after startup. If I start it from another folder, it runs - how comes?

With Electron 22, LSMinimumSystemVersion is 10.13. Following are the action items for dropping support
January milestone:

[ ] Push EOL message via top status bar and notification
[ ] Make relevant changes in VSCode and Server to push the above message but do not state it is the last release
[ ] (Optional) Make the changes generic to allow for future version updates
[ ] @isidorn to help with updating requirements and FAQ section in the website

February milestone:

[ ] Flip switch in update server to disable updates


Instead of uuids, list out node hostnames in Kepler dashboard

Update all queries to use hostname label instead.

/test telemetry-operator-build-deploy-kuttl

With node_exporter we are using fqdn now (https://github.com/openstack-k8s-operators/telemetry-operator/pull/535). Please, rebase on top of main and use fqdn instead of hostname for the Label to keep everything in sync.

/lgtm

/cherry-pick 18.0-fr1

Wait for https://github.com/openstack-k8s-operators/telemetry-operator/pull/543 to merge first

/cherry-pick 18.0-fr1


chore: Do not install poetry in install-dev make target

CI is failing because it's triggered by pull_request_target.


[Gene] Scroll locking

Oooook, that's got one of the trickyest bits in, handling the scroll locking inside the scroll

These changes are super documented, so it's better to read the source than for me to re-write it here.

          1 Error

:no_entry_sign:
No CHANGELOG added.

          1 Warning

:warning:
The following files do not have tests: lib/containers/gene.js

  Generated by :no_entry_sign: danger

I liiiike!
Useful component, parallax scroll view :o.


Extend the "Proxying Class Methods" section

Quick addition to the readme to explain how to access class methods defined on the decorator when an association with the model has been set up correctly.

Thanks 😄


Module import & Endpoint error

Hi.
I've added your module and I'm running in an error importing the schema from the virtual module #graphql/schema.
The error said: The requested module '~/.nuxt/graphql-schema.mjs' does not provide an export named 'schema'
At times the scheme is null and at others it is not.
I verified this by printing the object returned by the module to the console.
Also when trying to access the /api/graphql endpoint, I saw the following error:
ERROR  [h3] [unhandled] write EPIPE
at afterWriteDispatched (node:internal/stream_base_commons:160:15)
at writeGeneric (node:internal/stream_base_commons:151:3)
at Socket._writeGeneric (node:net:905:11)
at Socket.connect (node:net:887:12)
at Object.onceWrapper (node:events:627:28)
at Socket.emit (node:events:525:35)
at Socket.emit (node:domain:489:12)
at PipeConnectWrap.afterConnect [as oncomplete] (node:net:1263:10)
OS: Win10
Node versions tested: 18.16.0, 16.20.0 & 14.21.3
    "devDependencies": {     "@types/node": "^18",     "nuxt": "^3.5.1"   },   "dependencies": {     "@apollo/server": "^4.7.1",     "@as-integrations/h3": "^1.1.5",     "graphql": "^16.6.0",     "nuxt-graphql-server": "^2.0.0"   }

Can you please give me the content of the file .nuxt/graphql-schema.mjs when its not working?

At times the scheme is null and at others it is not.

Do you have an idea when its not working? Could it be that you sometimes run say the npm dev command from a subfolder?

Hi Tobias.
The file content becomes intermittent. At times it's empty (and that is when it marks the error) and suddenly it has the code with the schema.

I'm running the yarn dev command from the root folder and I'm just trying to make a HelloWorld example.
~/server/api/graphql.ts
import { Resolvers } from '#graphql/resolver';
import { schema } from '#graphql/schema';
import { ApolloServer, BaseContext, ContextFunction } from '@apollo/server';
import {
  H3ContextFunctionArgument,
  H3HandlerOptions,
  startServerAndCreateH3Handler,
} from '@as-integrations/h3';

const resolvers: Resolvers = {
  Query: {
    hello: () => 'Hello world!',
  },
};

console.log('TypeDefs ::: ', schema);

const apollo: ApolloServer<BaseContext> = new ApolloServer({
  typeDefs: schema,
  resolvers,
});

const context: ContextFunction<[H3ContextFunctionArgument], BaseContext> = (
  event
): Promise<BaseContext> => {
  return new Promise<BaseContext>(() => {
    console.log('Context Event ::: ', event);
  });
};

const options: H3HandlerOptions<BaseContext> = {
  context,
};

export default startServerAndCreateH3Handler(apollo, options);

~/server/graphql/hello.graphql
type Query {
  hello: String
}

This looks very strange, and I never experienced something like this before. My guess is that some file watcher is updating the graphql schema in the background, which then triggers the HMR. Do you have a git extension running in the background, or is your code in dropbox or something similar?
What you can try is to locally uncomment https://github.com/tobiasdiez/nuxt-graphql-server/blob/9d81c92bb7ff8535ec291eb6a740baf77a20e6e8/src/module.ts#L109-L118 (in your node-modules folder, find the nuxt-graphql-server addin and then this code should be under the dist folder). If you feel investing a bit more time, you can also set a debug breakpoint in https://github.com/tobiasdiez/nuxt-graphql-server/blob/9d81c92bb7ff8535ec291eb6a740baf77a20e6e8/src/module.ts#L66 and see when this method is called. It should only be called once at the beginning, and then every time you change your schema file.
Sorry that I have to put the debug work on your shoulders, but I sadly cannot reproduce this here on my system.

Closing this in the hope that it's fixed by https://github.com/tobiasdiez/nuxt-graphql-server/pull/68.


syslog-tls multi-line log output is often out of order

The syslog-tls drain often fails to keep multi-line log outputs in order (whereas the cf logs --recent output maintains the correct order in all cases).
An example of this behavior:
Here's a set of log lines from the cf logs --recent output:
2017-05-09T11:31:27.50-0700 [APP/TASK/create-invoices/0]OUT Creating container
2017-05-09T11:31:28.12-0700 [APP/TASK/create-invoices/0]OUT Successfully created container
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT Executing (default): SELECT rih.id as invoiceId, rsh.id as shipmentId, rih.invoiceNumber, roh.id as orderId,
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT roh.requestedDeliveryDate, roh.customerPONumber, ro.duns as receiverDUNS,
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT parentOrg.duns as senderDUNS, ra.storeNumber, ro.divisionCode
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT FROM RetailInvoiceHeaders rih
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailOrderHeaders roh ON rih.orderId = roh.id
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailShipmentHeaders rsh ON rsh.orderId = roh.id
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailOrganizations ro ON ro.id = roh.shipToOrganizationId
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailPicknpacks pick ON roh.picknpackId = pick.picknpackId
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailOrganizations pickOrg ON pickOrg.id = pick.retailOrganizationId
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailOrganizations parentOrg ON pickOrg.parentId = parentOrg.id
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT JOIN RetailAddresses ra ON roh.shipToAddressId = ra.id
2017-05-09T11:31:39.95-0700 [APP/TASK/create-invoices/0]OUT WHERE rih.status = 'Preliminary' AND rsh.status = 'Shipped'
2017-05-09T11:31:40.05-0700 [APP/TASK/create-invoices/0]OUT Found 0 invoices
2017-05-09T11:31:40.05-0700 [APP/TASK/create-invoices/0]OUT Process done
2017-05-09T11:31:40.10-0700 [APP/TASK/create-invoices/0]OUT Exit status 0
2017-05-09T11:31:40.15-0700 [APP/TASK/create-invoices/0]OUT Destroying container
2017-05-09T11:31:44.13-0700 [APP/TASK/create-invoices/0]OUT Successfully destroyed container

In Papertrail, fed by syslog-tls, the same log lines were recorded as:
May 09 11:31:27 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Creating container
May 09 11:31:28 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Successfully created container
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailOrganizations pickOrg ON pickOrg.id = pick.retailOrganizationId
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailOrganizations parentOrg ON pickOrg.parentId = parentOrg.id
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailAddresses ra ON roh.shipToAddressId = ra.id
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailShipmentHeaders rsh ON rsh.orderId = roh.id
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: WHERE rih.status = 'Preliminary' AND rsh.status = 'Shipped'
May 09 11:31:39 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: FROM RetailInvoiceHeaders rih
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Found 0 invoices
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Executing (default): SELECT rih.id as invoiceId, rsh.id as shipmentId, rih.invoiceNumber, roh.id as orderId,
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: roh.requestedDeliveryDate, roh.customerPONumber, ro.duns as receiverDUNS,
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: parentOrg.duns as senderDUNS, ra.storeNumber, ro.divisionCode
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailOrderHeaders roh ON rih.orderId = roh.id
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailOrganizations ro ON ro.id = roh.shipToOrganizationId
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: JOIN RetailPicknpacks pick ON roh.picknpackId = pick.picknpackId
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Process done
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Exit status 0
May 09 11:31:40 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Destroying container
May 09 11:31:44 fresh-retail-test 63585d1c-95b9-413b-9269-f894db934202/[APP/TASK/CREATE-INVOICES/0: Successfully destroyed container

These log files were from a single cf run-task execution with no other tasks running.

@johngrogg Thanks for submitting. Loggregator doesn't do any ordering of logs but the cf cli does do a best effort ordering by holding logs for a brief period. We have a new architecture for syslog drains and I was already considering this as a potential feature so that we closer matcher the cli experience of cf logs --recent

This might be a bug with papertrail. The RFC syslog message struct we are using supports sub second times. We should test to make sure this is isolated to papertrail.

The same behavior is occurring in the Pivotal Web Service dashboard log screen.
 I suppose the PWS log screen uses a stream without doing any ordering on their end. All the information to do the ordering is there.
@ahevenor Since this affects more than one environment perhaps it is something we should consider. I thought of a way we can do this without using sorting windows and timestamps but use sequence IDs so there is no additional latency.

We are incorporating this into our roadmap as a feature. I am going to keep this open but delete the automatically created tracker story.

We have made several updates to the documentation and ensure that nano-second timestamp should ensure ordering. This is effective in most places, but not Elastic unfortunately. Closing this issue.


FRITZ!Box Fon WLAN 7360: Can't parse inetstats

My boxinfo:
Model:     FRITZ!Box Fon WLAN 7360, ADSL standard 'B', branded as 'avm'
Firmware:  FRITZ!OS 06.85 (124.06.85 revision 61714)
Running:   5 years, 2 months, 7 days, 4 hours, 517 reboots

when running fritzctl   list inetstats, I get:
2018/12/10 16:39:43 Login successful
2018/12/10 16:39:43 Recent upstream/downstream time series:

Downstream/internet       [kb/s]:
Downstream/media          [kb/s]:
Downstream/guest          [kb/s]:
Upstream/low priority     [kb/s]:
Upstream/default priority [kb/s]:
Upstream/high priority    [kb/s]:
Upstream/realtime         [kb/s]:
Upstream/guest            [kb/s]:  0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00

TCPDump:
GET /internet/inetstat_monitor.lua?action=get_graphic&sid=XXXXXXXXXX&myXhr=1&xhr=1&useajax=1 HTTP/1.1
Host: <IP_ADDRESS>:80
User-Agent: Go-http-client/1.1
Accept-Encoding: gzip

HTTP/1.1 200 OK
Cache-Control: no-cache
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-type: text/html; charset=utf-8
Date: Sat, 08 Dec 2018 14:47:31 GMT
Expires: -1
Pragma: no-cache
Keep-Alive: timeout=60, max=300

[{"downstream":25088000,"upstream":5054000,"prio_realtime_bps":[129,525,1422,844,960,3830,742,5002,161,328,550,583,2452,1923,396,316,434,4498,4122,434],"max_us":631750,"dynamic":false,"guest_us_bps":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"prio_low_bps":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"ds_guest_current_bps":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"_node":"sg0","prio_default_bps":[89,258,159,112,697,0,89,701,1113,1082,534,342,320,428,499,545,89,0,361,0],"ds_current_bps":[983,2781,4284,1717,3713,359,5310,17212,2058,16130,1282,1434,9757,3921,1961,453,1241,4044,7132,420],"name":"sync_dsl","max_ds":3136000,"mc_current_bps":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"prio_high_bps":[48,291,381,73,86,0,86,173,48,95,48,41,454,128,65,0,48,91,841,32],"mode":"VDSL"}]

seems the fritzctl JSON schema doesn't match the data returned by my box:
type TrafficMonitoringData struct {
	DownstreamInternet      []float64 `json:"ds_bps_curr"`
	DownStreamMedia         []float64 `json:"ds_mc_bps_curr"`
	DownStreamGuest         []float64 `json:"ds_guest_bps_curr"`
	UpstreamRealtime        []float64 `json:"us_realtime_bps_curr"`
	UpstreamHighPriority    []float64 `json:"us_important_bps_curr"`
	UpstreamDefaultPriority []float64 `json:"us_default_bps_curr"`
	UpstreamLowPriority     []float64 `json:"us_background_bps_curr"`
	UpstreamGuest           []float64 `json:"guest_us_bps"`
}

Hi @juergenhoetzel,
thanks for reporting this issue. I assume that you are using a very recent version from git/master. There is a known incompatibility between FRITZ!OS 6.x and 7.x. The commit f117d8a broke support for 6.x. Is it an option for you to use one of the releases, e.g. v1.4.23 or earlier?
Greets

@juergenhoetzel Closing this issue as it is related to FRITZ!OS Compatibility. Currently git/master addresses firmwares 7.x.


fix: avoid repeat foldclose or foldopen chars when 'wrap' is set

Before:

After:

And I think there's no need to offer an option to configure.

Agreed, thanks!


encryption: move encryption config to under security config

What problem does this PR solve?
Move encryption config to under security config, i.e. [encryption] becomes [security.encryption]
Also update config template for encryption config.
What is changed and how it works?
Move encryption config to under security config, i.e. [encryption] becomes [security.encryption].
To achieve that, move tikv_util::security to its own crate, otherwise since encryption crate depends on engine_trait which depends on tikv_util, there will be cyclic dependency if tikv_util::security also depends on encryption.
Related changes
No.
Check List
Tests
Existing CI
Side effects
Encryption config is incompatible with previous versions.
Release note

Move config of encryption to under security config, i.e. [encryption] becomes [security.encryption] in tikv config.

/rebuild

We also need to update tiup and tidb-ansible.


Error: TypeScript compilation failed

What is the Current behavior?
I start to get error after I'm trying to execute a test  using this command ./node_modules/.bin/testcafe 'chrome --incognito' e2e/tests
Error:
ERROR Cannot prepare tests due to an error.
Error: TypeScript compilation failed.
<EMAIL_ADDRESS>(9, 23): ']' expected.
<EMAIL_ADDRESS>(9, 48): '(' expected.
<EMAIL_ADDRESS>(13, 43): ',' expected.
<EMAIL_ADDRESS>(13, 50): ',' expected.
<EMAIL_ADDRESS>(13, 64): '(' expected.
<EMAIL_ADDRESS>(18, 1): Unterminated template literal.
<EMAIL_ADDRESS>(31, 16): ',' expected.
<EMAIL_ADDRESS>(32, 12): ',' expected.
    at TypeScriptTestFileCompiler._reportErrors (/.../node_modules/testcafe/src/compiler/test-file/formats/typescript/compiler.ts:118:15)
    at TypeScriptTestFileCompiler._compileFilesToCache (/.../node_modules/testcafe/src/compiler/test-file/formats/typescript/compiler.ts:143:18)
    at TypeScriptTestFileCompiler._precompileCode (/.../node_modules/testcafe/src/compiler/test-file/formats/typescript/compiler.ts:172:18)
    at TypeScriptTestFileCompiler._compileCodeForTestFiles (/.../node_modules/testcafe/src/compiler/test-file/api-based.js:111:29)
    at /.../node_modules/testcafe/src/compiler/test-file/formats/typescript/compiler.ts:124:30
    at Compiler._precompileFiles (/.../node_modules/testcafe/src/compiler/index.js:64:33)
    at Compiler._compileTestFiles (/.../node_modules/testcafe/src/compiler/index.js:99:9)
    at Compiler.getTests (/.../node_modules/testcafe/src/compiler/index.js:117:34)
    at /.../node_modules/testcafe/src/runner/bootstrapper.ts:266:25
    at Object.guardTimeExecution [as default] (/.../node_modules/testcafe/src/utils/guard-time-execution.ts:6:31)

The NGRX is a 3 party package  that not relevant to Testcafe
When I execute my build script all pass.
I check if there are real issue with the file above for example on this file feature_creator.d.ts it say it (9, 23): ']' expected. but I check this file and everything is correct.

Here is the file feature_creator.d.ts
import { ActionReducer } from './models';
import { MemoizedSelector } from './selector';
export declare type Feature<AppState extends Record<string, any>, FeatureName extends keyof AppState & string, FeatureState extends AppState[FeatureName]> = FeatureConfig<FeatureName, FeatureState> & FeatureSelector<AppState, FeatureName, FeatureState> & NestedSelectors<AppState, FeatureState>;
export interface FeatureConfig<FeatureName extends string, FeatureState> {
    name: FeatureName;
    reducer: ActionReducer<FeatureState>;
}
declare type FeatureSelector<AppState extends Record<string, any>, FeatureName extends keyof AppState & string, FeatureState extends AppState[FeatureName]> = {
    [K in FeatureName as `select${Capitalize<K>}State`]: MemoizedSelector<AppState, FeatureState>;
};
declare type Primitive = string | number | bigint | boolean | null | undefined;
declare type NestedSelectors<AppState extends Record<string, any>, FeatureState> = FeatureState extends Primitive | unknown[] | Date ? {} : {
    [K in keyof FeatureState & string as `select${Capitalize<K>}`]: MemoizedSelector<AppState, FeatureState[K]>;
};
declare type NotAllowedFeatureStateCheck<FeatureState> = FeatureState extends Required<FeatureState> ? unknown : 'optional properties are not allowed in the feature state';
export declare function createFeature<AppState extends Record<string, any>, FeatureName extends keyof AppState & string = keyof AppState & string, FeatureState extends AppState[FeatureName] = AppState[FeatureName]>({ name, reducer, }: FeatureConfig<FeatureName, FeatureState> & NotAllowedFeatureStateCheck<FeatureState>): Feature<AppState, FeatureName, FeatureState>;
export {};

What is the Expected behavior?
To not throw error and run the automation
What is your web application and your TestCafe test code?
This is private project and I can't share it
Your Environment details:

testcafe version: 1.14.0
node.js version:  v14.15.5
command-line arguments:  'chrome --incognito'
browser name and version: Chrome Version 91.0.4472.114 (Official Build) (x86_64)
platform and version:         macOS big sur 11.4
other:           typescript 4.2.4

Hello,
The TS compiler used in TestCafe cannot parse such complex expressions as in the feature_creator.d.ts file.
Try connecting another compiler as written in the documentation: https://testcafe.io/documentation/402639/reference/command-line-interface#--compiler-options-options.

@felis2803
Can you upgrade please your typescript ?

Updating the typescript compiler to 4.x is a breaking change. So, we can't do this until we release TestCafe 2.0. Meanwhile, please use the workaround I suggested.


Separate GVK from ApiResource

This pull request shrinks GVK (so that it contains only G, V and K :smile: ), additionally making GVK fields public. It introduces a new ApiResource type which is much bigger (maybe it even contains too much stuff and should be split further). Also, two ways to obtain ApiResource are provided:

from GVK (with some guessing)
from APIResource

This PR also affects #491, because Discovery would contain a method to go from GVK to ApiResource (using discovered information), and this is intended to be both a simple and correct way to get an ApiResource.

Ok, sorry for being so slow on this one.
Short story, I am happy with the functionality here, but uneasy about the name ApiResource as it introduces clashes with k8s_openapi's APIResource which we also require users deal with.
The re-use of names in the kube::Resource from k8s_openapi::Resource were fine because we are ok with only using one of them, here's it's like asking for trouble.
We could change the name, but what if we instead change our Client::list_api_group_resources and Client::list_core_api_resources so that we return something usable by the Discovery module directly? That way there's no need for us to rename, and we provide a more holistic interface.

uneasy about the name

I'll be happy to rename ApiResource into any other more appropriate name.

also require users deal with

Hmm, I don't completely understand this point. kube::client::Discovery is intended to completely hide APIResource and other metav1 stuff.

change our Client::list_api_group_resources and Client::list_core_api_resources so that we return something usable by the Discovery module directly

If these methods are only useful as an implementation detail of discovery (i.e. there is no need for the majority of users to look at raw APIResource), then maybe we should make them private?

Hmm, I don't completely understand this point. kube::client::Discovery is intended to completely hide APIResource and other metav1 stuff.

Yeah, but the client listers ultimately expose primitives from k8s-openapi with very similar names, and it's unclear that we have easier alternatives (with almost the same name).

change our Client::list_api_group_resources and Client::list_core_api_resources so that we return something usable by the Discovery module directly

If these methods are only useful as an implementation detail of discovery (i.e. there is no need for the majority of users to look at raw APIResource), then maybe we should make them private?

Oh, yeah. That might be a better idea :D
I was thinking having the Client listers return something closer to GroupVersionData instead, but that doesn't sound that smart given how the discovery module works.
Maybe we just deprecate the client listers instead.

I'll just merge this and make small changes to it in master. Have already held this up for too long.

Released in 0.54.0 with some minor modifications (Group -> ApiGroup, and most of it is now actually in kube-core (but re-exported from kube). Thanks again.


Adds some tests for FunctorT

namely for transPrepro, transPostpro, and transPara.
I decided to learn about matryoshka, and in doing so, wrote some tests.

PRing to the correct fork would be important...