[FR] Have a repository of "supported" transaction types (different metadata models)

Something like this [0] that easily enables users to attach known JSON object types to transactions.
[0]

Section Name: MetaBuilder
Start with a few supported Schemas from Schema.org
Lets go ahead and Seed/Register these schemas on chain. (Maybe just the base 'Thing' schema)
We can always add what we support by default in the future, but this will help us understand the how to handle registered types on the app.
If a user wants to build a schema, they can construct what the schema is and 'register' the schema on the chain. We return them the transaction(*)
During send transaction, the user will need to enter a transaction id of the registered schema. we then create form of said schema for them to enter values.
*currently hard to return transaction id

Section Name: MetaBuilder
Start with a few supported Schemas from Schema.org
Lets go ahead and Seed/Register these schemas on chain. (Maybe just the base 'Thing' schema)
We can always add what we support by default in the future, but this will help us understand the how to handle registered types on the app.
If a user wants to build a schema, they can construct what the schema is and 'register' the schema on the chain. We return them the transaction(*)
During send transaction, the user will need to enter a transaction id of the registered schema. we then create form of said schema for them to enter values.
*currently hard to return transaction id


Fix Feature Engineering module Taxi Fare data mismatch

Code and Data is different in 4_keras_adv_feat_eng.ipynb lab.
https://github.com/GoogleCloudPlatform/asl-ml-immersion/blob/506ef9bea018149a3714f643ea49711a090752f6/notebooks/feature_engineering/solutions/4_keras_adv_feat_eng.ipynb?short_path=8c5445b#L99-L107
Data

@takumiohym I agree that the order of the CSV_COLUMNS and the taxi-train.csv don't match. But since the taxi-train.csv file in the feature_engineering folder has column names, my suggestion is to just re-order the CSV_COLUMNS variable accordingly and not change the training file.
The training file from introduction_to_tensorflow has only 7332 rows whereas the one in the feature_engineerin folder has 53K+ rows. It is better to train with more data rather than repeat the small dataset of 7332 rows 30 times.

Thanks!
Actually this is not only about the order but the column itself is different ( hourofday and dayofweek)
Basically I just copied the same file from the introduction_to_tensorflow directory, and I thought it would be good to stick with the same dataset to compare the performance with/without feature engineering. (And it works very well despite its size!)

I see!
The only columns which we need for training are fare_amount, pickup_longitude, pickup_latitude, dropoff_longitude, drop_off_lattitude and passenger_count. We actually do del transformed['pickup_datetime'] later so the pickup_datetime does not matter. So we could also just chose these columns from the larger dataset and re-write the original train file and potentially also copy this to the feature_engineering folder. This will avoid the having to use the *30 multiplier.
But, if you think the performance is good enough and the continuity of the data will tell a good story I am good with that too.

Thanks Sanjana :)


Need to ensure internal manager TLS secret is updated

Description
This PR fixes an issue in management clusters where the internal manager TLS secret is not updated.
This PR puts the rendering of the internal manager TLS secret in the controller, where we are tending to move the TLS secret creation logic. But for now I've left the other secrets in render/render.go alone.

For PR author

[ ] Tests for change.
[ ] If changing pkg/apis/, run make gen-files
[ ] If changing versions, run make gen-versions

For PR reviewers
A note for code reviewers - all pull requests must have the following:

[ ] Milestone set according to targeted release.
[ ] Appropriate labels:

kind/bug if this is a bugfix.
kind/enhancement if this is a a new feature.
enterprise if this PR applies to Calico Enterprise only.

@Brian-McM looks like kubecontrollers will be recreated with the updated secret so I believe we don't need any changes there: https://github.com/tigera/operator/blob/release-v1.14/pkg/render/render.go#L268

@Brian-McM looks like kubecontrollers will be recreated with the updated secret so I believe we don't need any changes there: https://github.com/tigera/operator/blob/release-v1.14/pkg/render/render.go#L268

I need to merge the changes after https://github.com/tigera/operator/pull/1117 is merged.
Once this is done I'll pick into master

I need to merge the changes after https://github.com/tigera/operator/pull/1117 is merged.
Once this is done I'll pick into master


[Serialization] Recover from more failures when reading private declarations

These two commits allow deserialization to recover from some failures reading swiftmodules that use implementation-only imports.
I’m bringing in the first commit from #27130. We saw this path being exercised only in the indexing phase which read private types and their members so it should be pretty safe to merge.
The second commit address a specific issue that we see in a complex case, but it drops too much information for my taste and may cause more problems in the future. I will consider reverting it when we have a better way to prevent such errors, such as always regenerating the swiftmodules from the public textual module interfaces before distribution.
rdar://60291019

@swift-ci Please smoke test


Return value of block from PaperTrail.request

.. making it easier to use at the call site.

Supersedes #1074


Add read -p "Press any key to exit..." at the the end of the prepare.sh script

I encountered an error but could not debug properly since the terminal would close once the script was done executing. Adding in this line helped me out in knowing, I just didn't have zip installed!
https://github.com/MindscapeHQ/raygun4node-aws-lambda/blob/62ce4333ba033114f46d37a31f42468dc9d25d8b/example/prepare.sh#L28

I will check if this affects users running the script from the command line.

I'll prefer to add a note to the README asking users to run the script from the command line, so they can see any output.
Otherwise, each time I run the script when testing, I need to tap a key again.


Add testing and document support for Python 3.7

Nice! I'm glad to see that Travis sorted out a single configuration that works for both 3.4 and 3.7.


spotify_player resumes playback on bluetooth headphone disconnect.

Describe the bug
A clear and concise description of what the bug is.
When I disconnect my bluetooth headphones from my computer (either by manually turning the off or disconnecting them from my connected bluetooth devices, or by moving out of range of my computer with my headphones), spotify-player resumes playback of the current track even if it was previously paused. This means that my computer often ends up playing music unexpectedly out of its speakers,
To Reproduce
Steps to reproduce the behavior.

Build spotify-player with media controls.
Connect bluetooth headphones to computer.
Open spotify-player and begin playing a track. Sound should be coming out of the headphones at this point.
Pause the playing track.
Disconnect the bluetooth headphones. At this point, spotify-player unpauses the playing track, and plays music out of the computer speakers.

Expected behavior
A clear and concise description of what you expected to happen.
If the current track is paused when the bluetooth headphones are disconnected, it should remain paused.
If the current track is playing when the headphones are disconnected, I have less of a strong view of what the behavior should be.
Log and backtrace
Reference log and backtrace, which are usually located in $HOME/.cache/spotify-player/, of a run reproducing the bug.
Backtrace is empty.
Log:
2023-10-17T13:22:52.669195Z  INFO spotify_player: General configurations: AppConfig { theme: "nord", client_id: "REDACTED", client_port: 8080, copy_command: Command { command: "pbcopy", args: [] }, playback_format: "{track} • {artists}\n{album}\n{metadata}", tracks_playback_limit: 50, proxy: None, ap_port: None, app_refresh_duration_in_ms: 32, playback_refresh_duration_in_ms: 0, cover_image_refresh_duration_in_ms: 2000, page_size_in_rows: 20, track_table_item_max_len: 32, play_icon: "▶", pause_icon: "▌▌", liked_icon: "♥", border_type: Plain, progress_bar_type: Rectangle, playback_window_position: Top, cover_img_length: 9, cover_img_width: 5, cover_img_scale: 1.0, playback_window_width: 6, enable_media_control: true, enable_streaming: true, enable_cover_image_cache: true, default_device: "spotify-player", device: DeviceConfig { name: "spotify-player", device_type: "speaker", volume: 100, bitrate: 160, audio_cache: false } }
2023-10-17T13:22:52.669739Z  INFO spotify_player: Theme configurations: ThemeConfig { themes: [Theme { name: "default", palette: Palette { background: None, foreground: None, black: Color { color: Black }, blue: Color { color: LightBlue }, cyan: Color { color: LightCyan }, green: Color { color: LightGreen }, magenta: Color { color: LightMagenta }, red: Color { color: LightRed }, white: Color { color: Gray }, yellow: Color { color: LightYellow }, bright_black: Color { color: DarkGray }, bright_white: Color { color: White }, bright_red: Color { color: Red }, bright_magenta: Color { color: Magenta }, bright_green: Color { color: Green }, bright_cyan: Color { color: Cyan }, bright_blue: Color { color: Blue }, bright_yellow: Color { color: Yellow } }, component_style: ComponentStyle { block_title: None, border: None, playback_track: None, playback_artists: None, playback_album: None, playback_metadata: None, playback_progress_bar: None, current_playing: None, page_desc: None, table_header: None, selection: None } }, Theme { name: "nord", palette: Palette { background: Some(Color { color: Rgb(46, 52, 64) }), foreground: Some(Color { color: Rgb(216, 222, 233) }), black: Color { color: Rgb(59, 66, 82) }, blue: Color { color: Rgb(189, 147, 249) }, cyan: Color { color: Rgb(143, 188, 187) }, green: Color { color: Rgb(229, 233, 240) }, magenta: Color { color: Rgb(180, 142, 173) }, red: Color { color: Rgb(255, 85, 85) }, white: Color { color: Rgb(187, 187, 187) }, yellow: Color { color: Rgb(136, 192, 208) }, bright_black: Color { color: Rgb(67, 76, 94) }, bright_white: Color { color: Rgb(255, 255, 255) }, bright_red: Color { color: Rgb(255, 85, 85) }, bright_magenta: Color { color: Rgb(255, 121, 198) }, bright_green: Color { color: Rgb(80, 250, 123) }, bright_cyan: Color { color: Rgb(139, 233, 253) }, bright_blue: Color { color: Rgb(189, 147, 249) }, bright_yellow: Color { color: Rgb(241, 250, 140) } }, component_style: ComponentStyle { block_title: Some(Style { fg: Some(Magenta), bg: None, modifiers: [] }), border: Some(Style { fg: None, bg: None, modifiers: [] }), playback_track: Some(Style { fg: Some(Cyan), bg: None, modifiers: [Bold] }), playback_artists: Some(Style { fg: Some(Cyan), bg: None, modifiers: [Bold] }), playback_album: Some(Style { fg: Some(Yellow), bg: None, modifiers: [] }), playback_metadata: Some(Style { fg: Some(BrightBlack), bg: None, modifiers: [] }), playback_progress_bar: Some(Style { fg: Some(Green), bg: Some(BrightBlack), modifiers: [] }), current_playing: Some(Style { fg: Some(Green), bg: None, modifiers: [Bold] }), page_desc: Some(Style { fg: Some(Cyan), bg: None, modifiers: [Bold] }), table_header: Some(Style { fg: Some(Blue), bg: None, modifiers: [] }), selection: Some(Style { fg: None, bg: None, modifiers: [Bold, Reversed] }) } }] }
2023-10-17T13:22:52.670299Z  INFO spotify_player: Keymap configurations: KeymapConfig { keymaps: [Keymap { key_sequence: KeySequence { keys: [None(Char('n'))] }, command: NextTrack }, Keymap { key_sequence: KeySequence { keys: [None(Char('p'))] }, command: PreviousTrack }, Keymap { key_sequence: KeySequence { keys: [None(Char('.'))] }, command: PlayRandom }, Keymap { key_sequence: KeySequence { keys: [None(Char(' '))] }, command: ResumePause }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('r'))] }, command: Repeat }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('s'))] }, command: Shuffle }, Keymap { key_sequence: KeySequence { keys: [None(Char('+'))] }, command: VolumeUp }, Keymap { key_sequence: KeySequence { keys: [None(Char('-'))] }, command: VolumeDown }, Keymap { key_sequence: KeySequence { keys: [None(Char('>'))] }, command: SeekForward }, Keymap { key_sequence: KeySequence { keys: [None(Char('<'))] }, command: SeekBackward }, Keymap { key_sequence: KeySequence { keys: [None(Enter)] }, command: ChooseSelected }, Keymap { key_sequence: KeySequence { keys: [None(Char('r'))] }, command: RefreshPlayback }, Keymap { key_sequence: KeySequence { keys: [None(Char('/'))] }, command: Search }, Keymap { key_sequence: KeySequence { keys: [None(Char('z'))] }, command: Queue }, Keymap { key_sequence: KeySequence { keys: [None(Char('Z'))] }, command: AddSelectedItemToQueue }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char(' '))] }, command: ShowActionsOnSelectedItem }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('a'))] }, command: ShowActionsOnSelectedItem }, Keymap { key_sequence: KeySequence { keys: [None(Char('a'))] }, command: ShowActionsOnCurrentTrack }, Keymap { key_sequence: KeySequence { keys: [None(Char('R'))] }, command: RestartIntegratedClient }, Keymap { key_sequence: KeySequence { keys: [None(Tab)] }, command: FocusNextWindow }, Keymap { key_sequence: KeySequence { keys: [None(BackTab)] }, command: FocusPreviousWindow }, Keymap { key_sequence: KeySequence { keys: [None(Char('T'))] }, command: SwitchTheme }, Keymap { key_sequence: KeySequence { keys: [None(Char('D'))] }, command: SwitchDevice }, Keymap { key_sequence: KeySequence { keys: [None(Char('u')), None(Char('p'))] }, command: BrowseUserPlaylists }, Keymap { key_sequence: KeySequence { keys: [None(Char('u')), None(Char('a'))] }, command: BrowseUserFollowedArtists }, Keymap { key_sequence: KeySequence { keys: [None(Char('u')), None(Char('A'))] }, command: BrowseUserSavedAlbums }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char(' '))] }, command: CurrentlyPlayingContextPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('t'))] }, command: TopTrackPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('r'))] }, command: RecentlyPlayedTrackPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('y'))] }, command: LikedTrackPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('L'))] }, command: LyricPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('l'))] }, command: LyricPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('l'))] }, command: LibraryPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('s'))] }, command: SearchPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('b'))] }, command: BrowsePage }, Keymap { key_sequence: KeySequence { keys: [None(Backspace)] }, command: PreviousPage }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('q'))] }, command: PreviousPage }, Keymap { key_sequence: KeySequence { keys: [None(Char('?'))] }, command: OpenCommandHelp }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('h'))] }, command: OpenCommandHelp }, Keymap { key_sequence: KeySequence { keys: [None(Char('q'))] }, command: Quit }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('c'))] }, command: Quit }, Keymap { key_sequence: KeySequence { keys: [None(Esc)] }, command: ClosePopup }, Keymap { key_sequence: KeySequence { keys: [None(Char('j'))] }, command: SelectNextOrScrollDown }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('n'))] }, command: SelectNextOrScrollDown }, Keymap { key_sequence: KeySequence { keys: [None(Down)] }, command: SelectNextOrScrollDown }, Keymap { key_sequence: KeySequence { keys: [None(Char('k'))] }, command: SelectPreviousOrScrollUp }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('p'))] }, command: SelectPreviousOrScrollUp }, Keymap { key_sequence: KeySequence { keys: [None(Up)] }, command: SelectPreviousOrScrollUp }, Keymap { key_sequence: KeySequence { keys: [None(PageUp)] }, command: PageSelectPreviousOrScrollUp }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('b'))] }, command: PageSelectPreviousOrScrollUp }, Keymap { key_sequence: KeySequence { keys: [None(PageDown)] }, command: PageSelectNextOrScrollDown }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('f'))] }, command: PageSelectNextOrScrollDown }, Keymap { key_sequence: KeySequence { keys: [None(Char('g')), None(Char('g'))] }, command: SelectFirstOrScrollToTop }, Keymap { key_sequence: KeySequence { keys: [None(Home)] }, command: SelectFirstOrScrollToTop }, Keymap { key_sequence: KeySequence { keys: [None(Char('G'))] }, command: SelectLastOrScrollToBottom }, Keymap { key_sequence: KeySequence { keys: [None(End)] }, command: SelectLastOrScrollToBottom }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('t'))] }, command: SortTrackByTitle }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('a'))] }, command: SortTrackByArtists }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('A'))] }, command: SortTrackByAlbum }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('d'))] }, command: SortTrackByDuration }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('D'))] }, command: SortTrackByAddedDate }, Keymap { key_sequence: KeySequence { keys: [None(Char('s')), None(Char('r'))] }, command: ReverseTrackOrder }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('k'))] }, command: MovePlaylistItemUp }, Keymap { key_sequence: KeySequence { keys: [Ctrl(Char('j'))] }, command: MovePlaylistItemDown }] }
2023-10-17T13:22:53.191192Z  INFO spotify_player::auth: Successfully used the cached credentials to create a new session!
2023-10-17T13:22:53.193802Z  INFO spotify_player::token: Getting new authentication token...
2023-10-17T13:22:53.377969Z  INFO spotify_player::token: Got new token: Token { access_token: "REDACTED", expires_in: Duration { secs: 3600, nanos: 0 }, expires_at: Some(2023-10-17T14:22:53.377960Z), refresh_token: None, scopes: {} }
2023-10-17T13:22:53.378116Z  INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "spotify-player", device_type: Speaker, initial_volume: Some(65535), has_volume_ctrl: true, autoplay: false }
2023-10-17T13:22:53.379063Z  INFO spotify_player::streaming: Initializing a new integrated player with device_id=75655a38-1e1b-4ae0-903e-b815b51a72f1
2023-10-17T13:22:53.379174Z  INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol
2023-10-17T13:22:53.614130Z  INFO spotify_player::streaming: Got an event from the integrated player: VolumeSet { volume: 65535 }
2023-10-17T13:22:53.669336Z  INFO spotify_player: No playback found on startup, trying to connect to an available device...
2023-10-17T13:22:53.669521Z  INFO spotify_player::cli::client: Starting a client socket at <IP_ADDRESS>:8080
2023-10-17T13:22:53.670313Z  INFO spotify_player::media_control: Initializing application's media control event watcher...
2023-10-17T13:22:53.771071Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 101ms
2023-10-17T13:22:53.783560Z  INFO client_request{request=GetCurrentUser}: spotify_player::client: successfully handled the client request, took: 113ms
2023-10-17T13:22:53.815883Z  INFO client_request{request=GetUserFollowedArtists}: spotify_player::client: successfully handled the client request, took: 145ms
2023-10-17T13:22:53.890053Z  INFO client_request{request=GetUserPlaylists}: spotify_player::client: successfully handled the client request, took: 219ms
2023-10-17T13:22:54.019127Z  INFO client_request{request=GetUserSavedTracks}: spotify_player::client: successfully handled the client request, took: 348ms
2023-10-17T13:22:54.191225Z  INFO client_request{request=GetUserSavedAlbums}: spotify_player::client: successfully handled the client request, took: 520ms
2023-10-17T13:22:54.780126Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Available devices: []
2023-10-17T13:22:54.780180Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Trying to connect to device (id=75655a38-1e1b-4ae0-903e-b815b51a72f1)
2023-10-17T13:22:55.199156Z  INFO spotify_player::streaming: Got an event from the integrated player: Started { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 21 }
2023-10-17T13:22:55.199231Z  INFO spotify_player::streaming: Got an event from the integrated player: Loading { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 21 }
2023-10-17T13:22:55.217524Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: Connection succeeded (device_id=75655a38-1e1b-4ae0-903e-b815b51a72f1)!
2023-10-17T13:22:55.217618Z  INFO client_request{request=ConnectDevice(None)}: spotify_player::client: successfully handled the client request, took: 1547ms
2023-10-17T13:22:55.294875Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 95ms
2023-10-17T13:22:55.296613Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 97ms
2023-10-17T13:22:56.351378Z  INFO spotify_player::streaming: Got an event from the integrated player: Paused { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 20, duration_ms: 162501 }
2023-10-17T13:22:56.455604Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 104ms
2023-10-17T13:22:58.679242Z  INFO spotify_player::client: Retrieving an image from the file: /Users/rollen/.cache/spotify-player/image/TRON: Legacy - The Complete Edition (Original Motion Picture Soundtrack)-Daft Punk-cover.jpg
2023-10-17T13:22:58.679890Z  INFO spotify_player::client: Retrieving an image from the file: /Users/rollen/.cache/spotify-player/image/TRON: Legacy - The Complete Edition (Original Motion Picture Soundtrack)-Daft Punk-cover.jpg
2023-10-17T13:23:00.995884Z  INFO spotify_player::streaming: Got an event from the integrated player: VolumeSet { volume: 65535 }
2023-10-17T13:23:00.999010Z  INFO spotify_player::streaming: Got an event from the integrated player: Playing { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 20, duration_ms: 162501 }
2023-10-17T13:23:00.999037Z  INFO spotify_player::streaming: Got an event from the integrated player: Playing { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 20, duration_ms: 162501 }
2023-10-17T13:23:01.010097Z  INFO client_request{request=Player(ResumePause)}: spotify_player::client: successfully handled the client request, took: 268ms
2023-10-17T13:23:01.214771Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 215ms
2023-10-17T13:23:01.252894Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 253ms
2023-10-17T13:23:01.270841Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 271ms
2023-10-17T13:23:04.969595Z  INFO client_request{request=Player(ResumePause)}: spotify_player::client: successfully handled the client request, took: 354ms
2023-10-17T13:23:04.993875Z  INFO spotify_player::streaming: Got an event from the integrated player: Paused { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 4608, duration_ms: 162501 }
2023-10-17T13:23:05.214345Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 220ms
2023-10-17T13:23:07.146417Z  INFO spotify_player::media_control: Got a media control event: Pause
2023-10-17T13:23:07.409728Z  INFO spotify_player::streaming: Got an event from the integrated player: VolumeSet { volume: 65535 }
2023-10-17T13:23:07.409808Z  INFO spotify_player::streaming: Got an event from the integrated player: Playing { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 4608, duration_ms: 162501 }
2023-10-17T13:23:07.410002Z  INFO spotify_player::streaming: Got an event from the integrated player: Playing { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 4631, duration_ms: 162501 }
2023-10-17T13:23:07.420551Z  INFO client_request{request=Player(ResumePause)}: spotify_player::client: successfully handled the client request, took: 273ms
2023-10-17T13:23:07.626386Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 216ms
2023-10-17T13:23:07.643873Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 233ms
2023-10-17T13:23:07.684584Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 274ms
2023-10-17T13:23:10.788748Z  INFO client_request{request=Player(ResumePause)}: spotify_player::client: successfully handled the client request, took: 262ms
2023-10-17T13:23:10.806242Z  INFO spotify_player::streaming: Got an event from the integrated player: Paused { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 8486, duration_ms: 162501 }
2023-10-17T13:23:11.034363Z  INFO client_request{request=GetCurrentPlayback}: spotify_player::client: successfully handled the client request, took: 227ms

Screenshots
If applicable, add screenshots to help explain your problem.
Environment

OS: macOS
Application version: Monterey 12.1
Application features: lyric-finder, image

Additional context
Add any other context about the problem here.

Looking at my log file again, I think the relevant lines are
2023-10-17T13:23:07.146417Z  INFO spotify_player::media_control: Got a media control event: Pause
2023-10-17T13:23:07.409728Z  INFO spotify_player::streaming: Got an event from the integrated player: VolumeSet { volume: 65535 }
2023-10-17T13:23:07.409808Z  INFO spotify_player::streaming: Got an event from the integrated player: Playing { play_request_id: 0, track_id: SpotifyId { id:<PHONE_NUMBER>0021058570632602234153092872, audio_type: Track }, position_ms: 4608, duration_ms: 162501 }

So the media control sends a Pause event, but the player starts playing. I think this might be because the media control Pause event gets mapped to ResumePause here: https://github.com/aome510/spotify-player/blob/4c5d25c9fa1313cb1a33264352130847739d7451/spotify_player/src/media_control.rs#L80-L82
So if the player is already paused, this will instead resume playback. Will try to implement a fix in a pull request


Tests: Silence some intentional errors

Also fix printing messages in ClassDB test.
This fixes most of the spam output we used to have when running --test.
What remains as of this PR:
$ godot-git --test
[doctest] doctest version is "2.4.9"
[doctest] run with "--help" for options
ERROR: The axis Vector3 must be normalized.
   at: set_axis_angle (core/math/basis.cpp:905)
===============================================================================
./tests/core/object/test_class_db.h:837:
TEST SUITE: [ClassDB]
TEST CASE:  [ClassDB] Add exposed classes, builtin types, and global enums

./tests/core/object/test_class_db.h:496: MESSAGE: Ignoring class 'GDScriptEditorTranslationParserPlugin' because it's not exposed.

./tests/core/object/test_class_db.h:496: MESSAGE: Ignoring class 'IPUnix' because it's not exposed.

./tests/core/object/test_class_db.h:496: MESSAGE: Ignoring class 'MovieWriterMJPEG' because it's not exposed.

./tests/core/object/test_class_db.h:496: MESSAGE: Ignoring class 'MovieWriterPNGWAV' because it's not exposed.

===============================================================================
[doctest] test cases:     582 |     582 passed | 0 failed | 1 skipped
[doctest] assertions: 2286494 | 2286494 passed | 0 failed |
[doctest] Status: SUCCESS!
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:1896)

The Vector3 error will be fixed by #63912.
The ClassDB messages should be reviewed - do we want to expose these classes, if not why are they in ClassDB?
There's 1 skipped test, didn't check which one yet. Would be good to fix and enable again?
There are leaks on exit. Passing --verbose doesn't seem to actually work to get more info.

@qarmin After this and #63912, we should be "ERROR" free on the --test output. Could be nice to add a check for this on CI so it returns non-zero error code when errors are printed, so we catch regressions in PRs.


[BUG] Erroneous "Operation cannot be fulfilled" Error in RKE2 Provisioning Logs

Rancher Server Setup

Rancher version: v2.6.9-rc1
Installation option (Docker install/Helm Chart): Helm

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): RKE1

Proxy/Cert Details: N/A

Information about the Cluster

Kubernetes version: v1.24.4+rke2r1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): EC2 Node Driver

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Admin and Standard - Cluster Owner

If custom, define the set of permissions: N/A

Describe the bug
When provisioning an RKE2 EC2 Node Driver cluster, an error is generated in the Provisioning Logs
To Reproduce

On a Rancher server, navigate to the Cluster Management page
Click the Create button
Toggle to RKE2/K3s, and then click Amazon EC2
Input a unique name as well as the correct AWS Access Key and SecretKey credentials, and then click the Create button
Input a unique name, set the Machine Count value to "3", and select a valid VPC/Subnet, and then click the Create button
After the cluster has provisioned successfully and is "Active", navigate to the Cluster Management--> Cluster page for the cluster, and then navigate to the Provisioning Log tab

Result
Note that an error is present in the logs which states "[ERROR] Operation cannot be fulfilled on machines.cluster.x-k8s.io "{MACHINE POOL NAME}": the object has been modified; please apply your changes to the latest version and try again"
Expected Result
No error is observed in the Provisioning Logs
Screenshots

Additional context
Provisioning Logs:

2:35:42 pm | [INFO ] waiting for viable init node
2:36:00 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for agent to check in and apply initial plan
2:37:33 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler, kubelet
2:38:09 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for probes: calico, etcd, kube-apiserver, kube-controller-manager, kube-scheduler
2:38:19 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for probes: calico, kube-apiserver, kube-controller-manager, kube-scheduler
2:38:25 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for probes: calico
2:39:35 pm | [INFO ] configuring bootstrap node(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q: waiting for cluster agent to connect
2:40:51 pm | [INFO ] non-ready bootstrap machine(s) jrmk3serrortest-pool1-5cf699c6fb-k6q9q and join url to be available on bootstrap node
2:41:07 pm | [ERROR] Operation cannot be fulfilled on machines.cluster.x-k8s.io "jrmk3serrortest-pool1-5cf699c6fb-sv9j2": the object has been modified; please apply your changes to the latest version and try again
2:41:09 pm | [INFO ] configuring etcd node(s) jrmk3serrortest-pool1-5cf699c6fb-sv9j2,jrmk3serrortest-pool1-5cf699c6fb-t5h9g
2:43:01 pm | [INFO ] configuring etcd node(s) jrmk3serrortest-pool1-5cf699c6fb-t5h9g: waiting for probes: calico
2:43:13 pm | [INFO ] non-ready etcd machine(s) jrmk3serrortest-pool1-5cf699c6fb-t5h9g
2:43:15 pm | [INFO ] provisioning done

journalctl -u rancher-system-agent Logs:

-- Logs begin at Fri 2022-09-23 18:36:01 UTC, end at Fri 2022-09-23 18:57:54 UTC. --
Sep 23 18:37:26 jrmk3serrortest-pool1-bdac25ec-c58nn systemd[1]: Started Rancher System Agent.
Sep 23 18:37:26 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:37:26Z" level=info msg="Rancher System Agent version v0.2.10 (6a89e30) is starting"
Sep 23 18:37:26 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:37:26Z" level=info msg="Using directory /var/lib/rancher/agent/work for work"
Sep 23 18:37:26 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:37:26Z" level=info msg="Starting remote watch of plans"
Sep 23 18:37:26 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:37:26Z" level=info msg="Starting /v1, Kind=Secret controller"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="Detected first start, force-applying one-time instruction set"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="[Applyinator] Applying one-time instructions for plan with checksum 6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="[Applyinator] Extracting image rancher/system-agent-installer-rke2:v1.24.4-rke2r1 to directory /var/lib/rancher/agent/work/20220923-184106/6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3>
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="Using private registry config file at /etc/rancher/agent/registries.yaml"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="Pulling image index.docker.io/rancher/system-agent-installer-rke2:v1.24.4-rke2r1"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="Extracting file installer.sh to /var/lib/rancher/agent/work/20220923-184106/6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0/installer.sh"
Sep 23 18:41:06 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:06Z" level=info msg="Extracting file rke2.linux-amd64.tar.gz to /var/lib/rancher/agent/work/20220923-184106/6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0/rke2.linux-amd64.tar.gz"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="Extracting file sha256sum-amd64.txt to /var/lib/rancher/agent/work/20220923-184106/6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0/sha256sum-amd64.txt"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="Extracting file run.sh to /var/lib/rancher/agent/work/20220923-184106/6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0/run.sh"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[Applyinator] Running command: sh [-c run.sh]"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + SA_INSTALL_PREFIX=/usr/local"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + mkdir -p /var/lib/rancher/rke2"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + SAI_FILE_DIR=/var/lib/rancher/rke2/system-agent-installer"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + RESTART_STAMP_FILE=/var/lib/rancher/rke2/system-agent-installer/rke2_restart_stamp"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + RKE2_SA_ENV_FILE_NAME=rke2-sa.env"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + [ ! -d /var/lib/rancher/rke2/system-agent-installer ]"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + mkdir -p /var/lib/rancher/rke2/system-agent-installer"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + check_target_mountpoint"
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + mountpoint -q "
Sep 23 18:41:07 jrmk3serrortest-pool1-bdac25ec-c58nn rancher-system-agent[1391]: time="2022-09-23T18:41:07Z" level=info msg="[6d8c502e51cd30a9866d09994365a3f0c64bd203ab58352648af3c3cda530d6b_0:stderr]: + check_target_ro"

QA TEST PLAN
| Scenarios | Test Case |
|-------------------------------|
| 1 | Fresh install with highest K8s version for RKE2 node driver cluster as Admin User |
| 2 | Fresh install with second highest K8s version for RKE2 node driver cluster as Standard User with Cluster Owner role |

It seems this error stems from Rancher updating the status field on the infrastructure object each time the machine-provision-pod job state changes. The status is updated when the job is changed, as well as during job creation.
Because these errors are benign and quickly resolve themselves I'm not sure there is much use propagating them to the UI, though they definitely should remain in the rancher logs.

/backport 2023-Q1-v2.6x

During testing on v2.7-head (Commit ID: e54432e) by following the Steps To Reproduce, I was able to verify that the error is no longer present in the Provisioning Logs for RKE2 clusters.  Therefore I am closing this ticket as Done.
Steps to Reproduce (performed on both v1.25.5+rke2r1 and v1.24.4+rke2r1:

On a Rancher server, navigate to the Cluster Management page
Click the Create button
Toggle to RKE2/K3s, and then click Amazon EC2
Input a unique name as well as the correct AWS Access Key and SecretKey credentials, and then click the Create button
Input a unique name, set the Machine Count value to "3", and select a valid VPC/Subnet, and then click the Create button
After the cluster has provisioned successfully and is "Active", navigate to the Cluster Management--> Cluster page for the cluster, and then navigate to the Provisioning Log tab
Scale the cluster up and down by 1 node
After the cluster has provisioned successfully and is "Active", navigate to the Cluster Management--> Cluster page for the cluster, and then navigate to the Provisioning Log tab

v2.7-head (Commit ID: e54432e):
After Original Provisioning:

After Scaling Up and Down:


Small improvements in topico_node.cpp

I would like to work toward compiling this as a C library so we can easily use it in MoveIt. It needs to be a library, not a ROS node.
Would you be open to more PR's to make that happen?
For example, I really want to clean up these hardcoded filepaths:
ROS/topico/src/solve_O.cpp:  "/home/lmbeul/Desktop/TopiCo/MATLAB/solve_O.m",// pName

BTW I tested this in MATLAB. The functionality is really amazing! The ability to specify "NaN" for some derivative values is something I haven't seen elsewhere.

Hey AndyZe,
thank you for the kudos! I look forward for more PR and the integration into MoveIt! How can I help in the process? You can already easily compile a static topico_wrapper.a library when changing cfg.GenCodeOnly to false and run the generate_code.m
Regarding the hardcoded filepaths: Actually I wasn't aware of the issue since I never had a thorough look at the generated CPP files. I would like to keep the CPP and MATLAB versions consistent with the CPP derived from the MATLAB version. Thus, changing the generated files would break this dependency. How can we solve this?
Best,
Marius

Let me think about it and talk it over with a few people, then I'll get back to you.


ApiVersion is incorrect for Deployment and StatefulSet resources

ApiVersion is incorrect for Deployment and StatefulSet resources.
After I generated config/apiserver.yaml and tried to kubectl apply -f config/apiserver.yaml. I got next errors:
unable to recognize "config/apiserver.yaml": no matches for kind "Deployment" in version "apps/v1beta1"
unable to recognize "config/apiserver.yaml": no matches for kind "StatefulSet" in version "apps/v1beta1"

#483

https://github.com/kubernetes-sigs/apiserver-builder-alpha/pull/488


[improve][tx] enhance validation when updating transaction topic

Master issue: #15302
Motivation
Currently executing the command bin/pulsar initialize-transaction-coordinator-metadata will directly update the number of partitions of persistent://pulsar/system/transaction_coordinator_assign.
When accidentally misoperation, the number of partitions is directly modified, and there is no way to roll back (the number of partitions cannot be reduced).
Modifications
Simplely add an argument to determine whether forced update is allowed.
Verifying this change
This change added tests and can be verified as follows:
(example:)
bin/pulsar initialize-transaction-coordinator-metadata -cs <IP_ADDRESS>:2181 -c standalone -c 1
bin/pulsar initialize-transaction-coordinator-metadata -cs <IP_ADDRESS>:2181 -c standalone -c 2

# Check for changes of partitions
bin/pulsar-admin topics get-partitioned-topic-metadata persistent://pulsar/system/transaction_coordinator_assign

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (yes)
Anything that affects deployment: (no)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[x] no-need-doc
I think command description is sufficient.

It's not able to reduce the partitions of transaction coordinators, it will lost data of transaction log.

@wuzhanpeng PTAL, and confirm if we can close this PR.

The goal of the command of bin/pulsar initialize-transaction-coordinator-metadata is to create the partition topic ersistent://pulsar/system/transaction_coordinator_assign if absent.
That is not an optional item, so the motivation of this PR is confused.
I will close this PR and you can reopen it when you have more valid feedback.


Adds Mongo instrumentation

Fixes #818

if we limiting of the size on the tag here are some things..

we dont do this elsewhere and should consider why here and not mysql etc. particularly I recall early users always expecting the whole sql for example. we have many examples of UI requests to render multiline json over our history.
our indexing already special cases at 255 characters for above reason. note it only sub string indexing but retains whole value.
agree that regardless 100 is too small. we do say spans shouldn't be over 1K as we start getting into trouble with default Kafka message sizes cc @jeqo

Thanks for the comments!
I'm not sure why the Travis build is failing. That exact command is passing for me locally.

Extremely well done! I think we do need to make a conscious decision about if it makes sense to add request tagging here, especially if default, even if it is truncated.
I now wish we had a rationale section about this to refer to, but typically we defer work like this to logging as usually a driver has a log category to dump request/response. I don't know if mongo has this or not.

Mongo has limited logging which typically does include logging the command name and collection name but not more than that.
In general, I'm not sure if we can rely on logging. A lot of companies are moving towards 12-factor apps where logging should go to stdout and it is not appropriate to log full requests/responses to stdout as it would be distracting for the developer and the size might be prohibitive as well.

I'm a fan of the iterative approach. Let's get MongoDB tracing out without tagging the full command, and let's see if people request this feature.

If it helps, you can look at the HttpRequestParser design for extending this in the future. Ex gRPC we added parsers so people who know what they are doing can tag either requests (or even links to them if using something like haystack-blobs)
Putting fixed (or fixedish) size data in the first cut allows us to move forward. I think next step will be a customizable parser and that's easier to design after anyway.

@csabakos PS if you are out of steam, it is no problem for me to sort out the last comments on the way in. You've done a ton here!

Hi @adriancole, I think I addressed all comments. Could you take another look please?

I will sort the other stuff afterwards. thanks so much for the effort!

follow-up https://github.com/openzipkin/brave/pull/1090


Revert "Queue etcd snapshots if snapshot is currently being taken"

This reverts commit 7340aeee317a76984ec5b270bf97d48772d686bc.
Discussed with @snasovich, since the last commit wasn't validated yet (and was absent from v2.5.12 entirely) it's best to revert this commit.

LGTM.
@jakefhyde  Just to confirm that this PR does not affect https://github.com/rancher/rancher/issues/36644, right?

@jiaqiluo This PR reverts a commit in that PR which with put patch2 more in line with the fixes already in 2.5.12 which is what is desired for this release.


fake change

To debug github not accepting merges.

Coverage remained the same at 97.011% when pulling 2e93af515f214760c31fcee5606d0204cdb77f5a on tianyu-testpr into ff06c887f1b3d9ff78fbf507ca5374473af2bef1 on master.

@lmwnshn This can be merged. You probably broke something,


Using dp in SimCLR with --online_ft

🐛 Bug
SimCLR module crashes when running with dp backend and --online_ft flag with an assertion error during validation sanity check.

To Reproduce
Steps to reproduce the behavior:

Run  python simclr_module.py --gpus 2 --distributed_backend dp --online_ft

Expected behavior
SimCLR should run on dp distributed_backend.

fixed


Keeping src files when publishing / downloading from GIT with NPM

When trying to use the latest incremental-dom version through npm, by adding the repository URL into the package.json file, nothing is downloaded, apart from the LICENSE and AUTHORS file. I think this happens because of the files key defined in the package.json file.
However, if the project where you want to use it uses ES6 classes, and has already a process for building, I think it makes much more sense to be able to directly link into the source files, rather than using the compiled result (which of course is not present on the repo either).
Would it be worth then for that to add the src key into the array; or is it better to point to it as a git submodule?

Even if I add index.js and the src files to the files array, the main file in package.json won't be correct if you were using the git URL instead of the published package.
One thing that could be done is create a separate repository that is used for publishing to NPM that just checks out an ES6 version from git, builds and publishes. It would still be weird because if you used the main git repo, it would be es6 but if you installed from NPM it would be es5.
I suppose I could make the git version have an install script that builds it on install. It would be rather slow, but it would work.
If you want to use the latest version for development reasons, you can download the git repo and use npm link. I haven't had a good experience with submodules in the past, but that is also a possibility.

For those ones who want to get the ES6 files and import them from their code (so incremental-dom is bundled with the rest of their main project), I think not having the index.js file directly pointing to it is a smaller issue compared to not having any ES6 file (I guess because src folder is not included as part of the files key in package.json).
In fact, the index file pointed by package.json should be kept pointing to the generated dist file.


Cannot pull an image pushed with docker 1.10 using docker 1.7.1

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version (Push side):
Client:
Version:      1.10.0
API version:  1.22
Go version:   go1.5.3
Git commit:   590d5108
Built:        Thu Feb  4 18:18:11 2016
OS/Arch:      darwin/amd64
Server:
Version:      1.10.0
API version:  1.22
Go version:   go1.5.3
Git commit:   590d5108
Built:        Thu Feb  4 19:55:25 2016
OS/Arch:      linux/amd64
docker version (Pull side):
Client version: 1.7.1
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 786b29d
OS/Arch (client): linux/amd64
Server version: 1.7.1
Server API version: 1.19
Go version (server): go1.4.2
Git commit (server): 786b29d
OS/Arch (server): linux/amd64
docker info (Push side):
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 3
Server Version: 1.10.0
Storage Driver: aufs
Root Dir: /mnt/sda1/var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 18
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Plugins:
Volume: local
Network: bridge null host
Kernel Version: 4.1.17-boot2docker
Operating System: Boot2Docker 1.10.0 (TCL 6.4.1); master : b09ed60 - Thu Feb  4 20:16:08 UTC 2016
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 996.2 MiB
Name: default
ID: QZG2:7B32:ZM2W:JTNS:4XW5:TKS7:GNUR:IDND:IW4X:IIUH:RGES:Y4SR
Debug mode (server): true
File Descriptors: 10
Goroutines: 21
System Time: 2016-02-09T04:03:37.934551172Z
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /mnt/sda1/var/lib/docker
Http Proxy: http://<IP_ADDRESS>:8888
Labels:
provider=virtualbox
docker info (Pull side):
Containers: 4
Images: 80
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 92
Dirperm1 Supported: false
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.13.0-73-generic
Operating System: Ubuntu 14.04.3 LTS
CPUs: 1
Total Memory: 1.955 GiB
Name: vagrant-ubuntu-trusty-64
ID: YUPL:RGQD:WW3N:3UYB:TNDA:NF6S:WXXG:DRF2:GANI:CKBX:AJ7S:BCVJ
Debug mode (server): true
File Descriptors: 10
Goroutines: 14
System Time: 2016-02-09T04:07:29.917292212Z
EventsListeners: 0
Init SHA1: c8f59b9547b87a6d097a72404dc29cba4e3a196e
Init Path: /usr/lib/docker/dockerinit
Docker Root Dir: /var/lib/docker
Http Proxy: http://<IP_ADDRESS>:8888
WARNING: No swap limit support
Provide additional environment details (AWS, VirtualBox, physical, etc.):
Push side is docker-machine with virtualbox on osx
Pull side is ubuntu 14.04 running under VirtualBox (vagrant), also replicated on AWS elastic beanstalk.
List the steps to reproduce the issue:
This issue appears when pushing from docker 1.10 and then pulling from docker 1.7.1

(1.10) - docker pull hello-world
(1.10) - docker tag hello-world v2privateregistry.internal/shared/hello-world
(1.10) - docker push v2privateregistry.internal/shared/hello-world
(1.7.1) - docker pull v2privateregistry.internal/shared/hello-world

Describe the results you received:
On the console:
Pulling repository v2privateregistry.internal/shared/hello-world
Error: image shared/hello-world:latest not found
From the docker logs:
DEBU[0544] provided manifest reference "latest" is not a digest: invalid checksum digest format
ERRO[0544] Error from V2 registry: error verifying manifest: verifying remote digest: verification against digest "sha256:fea8895f450959fa676bcc1df0611ea93823a735a01205fd8622846041d0c7cf" failed
DEBU[0544] image does not exist on v2 registry, falling back to v1
DEBU[0544] pulling v1 repository with local name "v2privateregistry.internal/shared/hello-world"
Describe the results you expected:
I expected to be able to pull the image successfully.
We do not have a v1 registry so I don't expect the v1 fallback to work.
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Which version of the registry are you using?

This may be related to https://github.com/docker/distribution/issues/1444

I can confirm this behaviour with registry:2.3

Closing this issue here since this is a registry issue tracked by https://github.com/docker/distribution/issues/1444. There is also an open PR to fix this https://github.com/docker/distribution/pull/1445.
@bbdimitriu downgrading to the old python registry is not necessary, 2.2.x does not have this issue. If you are having issues with 2.2.x please open up an issue at https://github.com/docker/distribution/issues so we can investigate.


Add SIP Request Ping and Registration Options Feature

⚠⚠⚠ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules:
https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma
Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description
@louislam ,
This SIP module is able to process both a failure to receive OPTIONS requests, as well as a failure to REGISTER as a valid endpoint. It supports UDP, TCP, and TLS on a user-selectable port (not just fixed to 5060/5061), and supports either No Authentication or Basic Authentication. The monitor's history shows up/down events, the reason behind them, and response latency. Additionally, there is an option to process 503 responses from the SIP server (or monitored SIP device), as "Maintenance", meaning if a 503 is received, the monitor is immediately placed into an adhoc "maintenance" rather than shown as down (upon restore of normal SIP service, the maintenance flag is removed from the monitor).
Could we talk about it further? it will be a great addition.
Fixes #(issue)
Type of change
Please delete any options that are not relevant.

User interface (UI)
New feature (non-breaking change which adds functionality)
This change requires a documentation update

Checklist

[x] My code follows the style guidelines of this project
[x] I ran ESLint and other linters for modified files
[x] I have performed a self-review of my own code and tested it
[x] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)
[x] My changes generate no new warnings
[x] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.

Here's a couple feature requests to support this Pull Request:
https://github.com/louislam/uptime-kuma/issues/1906
https://github.com/louislam/uptime-kuma/issues/5375

@CommanderStorm ,
My request to become contributor.

I did not incorporate SIP Register requests because it is irrelevant for my use cases, but maybe extend on my PR (which has had no response) #5362 ?


Curly bracket inside command causes 500 error.

This line in a .rst:
* Host is located at ``/var/lib/store/hosts/{hostname}``.
Caused this error:
sphinxcontrib.confluencebuilder error:
---
An unsupported Confluence API call has been made.

REQ: POST
RSP: 500
URL: https://company.atlassian.net/wiki/rest/api/
API: contentbody/convert/storage
---

Removing the curly brackets around hostname made the error go away.

Related to #39.

Fixed in #43

@sabinlinden please can you validate this is fixed.
pip install -e git+https://github.com/tonybaloney/sphinxcontrib-confluencebuilder.git#egg=sphinxcontrib-confluencebuilder

Unfortunately the pip install command errors out in my current environment and I have yet to figure out the reason why. I'll let you know if I figure this out.

@sabinlinden try upgrading setuptools.
pip install --upgrade setuptools

Sorry, that didn't work and I've been strapped for time so I still haven't resolved the issue with my environment.

This issue should now be resolved in db5b916e57898eb86244b4c33a801f5da5c3b984 (available on the master; see specifically ca84f547796c091d80a131bc2edb8b5bfd435441 AND b6bb29230db22ccc45a5852c75f88ef4cfbea422). To take advantage of this change, one can pull from master. This change should be made available in an upcoming v0.7 release (#29).


Alter the home of ceph conf to not interfere with other applications …

Backports https://github.com/charmed-kubernetes/ceph-csi-operator/pull/23

Since the vSphere is not available, ran the integration tests for this backport locally.


How do I get into a route and clear all routes other than the first route before then?

for example: A > B >C > D;
when i want C to D, when i get into d, clean B and C, so I can pop to A when i go back user phone home back button

I think you could use type='replace' to achieve this, not sure though.
When navigation from B to C, you'd use type='replace' and from C to D again.  Then I think you can use pop to go from D to A.
once again: not sure.

You can use popTo('A'), check Example project

But he wants to control the 'user phone home back button', which I think is the back button on android. Is it even possible to bind popTo to that button?

Oh, I see now. Then yes, you could try pop & replace.


Feat/contract update admin

Added another Button to the Contract tab in addition to Migrate which will allow the update of an admin at the Cosm/terra level we could say.
Note there is also the chance to add ClearAdmin but I specifically opted not to do this as its destructive. Is that something thats wanted? LMK.
Tried to hook up all the various bits. Open to feedback :-)

In review

e2294ae merged this


Oauth2: Supported at the request level, but not at the collection level

When configuring OAuth 2.0, it would be helpful to configure once per collection instead of requiring configuration on individual requests:
Auth configuration at the request level:

Auth configuration at the collection level:

(This is for Bruno v1.10.0)

For people that found this page via searching the issue, this is now possible with a little workaround in v1.11.0.
Set the collection level auth as OAuth 2.0 (like Insomnia/Postman)
Navigate to the "Script" pane and set the access token as a variable
  var token = res.body.access_token;
  if (token) {
    bru.setVar('oauth2_token', token)
  }

Then navigate to the "Headers" pane and set the "Authorization" header as needed.
i.e.

Once you do this, you only need to "Get the token" once and then all requests in the collection will use this access token.
Full collection.bru for anything that just wants to copy that.
headers {
  Authorization: Bearer {{oauth2_token}}
}

auth {
  mode: oauth2
}

auth:oauth2 {
  grant_type: authorization_code
  callback_url: {{RedirectUrl}}
  authorization_url: {{AuthorizationUrl}}
  access_token_url: {{AccessTokenUrl}}
  client_id: {{ClientId}}
  client_secret:
  scope: {{GatewayScope}}
  pkce: false
}

script:post-response {
  var token = res.body.access_token;
  if (token) {
    bru.setVar('oauth2_token', token)
  }
}

@jackj93 this isn't working for me either (v 1.12.1 now). Var isn't being set by the script either when hitting "Get Access Token" button on the Collection Authorization or in making a call that uses inherit authorization.

@jackj93 did you have to install an external module for this to work?
When putting the code you mention in the pre request script location on the collection, I just get this error:
Error invoking remote method 'send-http-request': ReferenceError: res is not defined

Any idea?

@jackj93 this isn't working for me either (v 1.12.1 now). Var isn't being set by the script either when hitting "Get Access Token" button on the Collection Authorization or in making a call that uses inherit authorization.

In the request themselves you have to set the "No Auth"

@jackj93 did you have to install an external module for this to work? When putting the code you mention in the pre request script location on the collection, I just get this error:
Error invoking remote method 'send-http-request': ReferenceError: res is not defined

Any idea?

All the configuration I listed go in the configuration for the collection. do NOT put anything in the request settings

Update: As of v1.11.0 I see that OAuth2 is supported at the collection level, but setting auth to 'inherit' at the request level isn't supported:

Using @jackj93 's scripting provides a workaround: we can save the collection token as a variable and use that in requests in the appropriate place (for me, I set an Authorization header with the value Bearer {{oauth2_token}}).  Is inherit going to be supported natively in the future without scripting hacks?

In addition to the Post Request script by @jackj93, I'm using this Pre Request script on Collection level, then you don't need to add the header manually on each request:
var token = bru.getVar('oauth2_token')
if (token) {
  req.setHeader('Authorization', `Bearer ${token}`)
}

Is there a way to reuse a token across multiple collections?
I have many collections but they use the same OAuth provider. So now I have to get a token for each collection individually, instead of doing it once and reusing it in all collections.
I guess a workaround would be to have only one collection per OAuth provider and group the requests in folders and subfolders.

Workarounds aside (which work, thanks for that) is there intention to work on this formally? Debating the pros and cons of waiting on this to be solved upstream and permit inheritance on the collection requests when using Oauth2 instead of injecting a pre-script one every single request.
Thanks

I am taking approach the insomnia way for this
created a request responsible for just fetching the token
and storing the variable in post response

then using the variable in header.

insomnia saves a little time in this by allowing us to directly use the attribute from some other response.

Just a suggestion: until such time that the header can be added automatically for OAuth, perhaps this message could point people to this thread:

It took me 20 mins to track this down.

After applying @jackj93's workaround (thanks for that) requests are fine, however, when attempting to get a new token I'm getting invalid_client errors. I tracked this down to the Authorization header being added, and disabling it allows a new token to be generated. Has anyone had this issue, and possibly got a better way to handle it than manually toggling the header value?

The work arounds suggested still seem to require manually clicking the "Get Access Token" on the collection every time the token expires.  This isn't great for api's that use short lived tokens.  Luckily the client credential flow can be automated fairly simply by adding the following Pre Request script on the collection:
const axios = require('axios');

let token = bru.getEnvVar('access_token_set_by_collection_script');
let tokenExpiration = bru.getEnvVar('access_token_expiration');
let currentTime = (new Date()).getTime();

if (!token || !tokenExpiration || tokenExpiration < currentTime) {
  try {
    console.log("requesting new token");
    const tokenData = (await axios.post(
      bru.getEnvVar('AccessTokenUrl'),
      {
        client_id: bru.getEnvVar('ClientId'),
        client_secret: bru.getEnvVar('ClientSecret'),
        grant_type: 'client_credentials'
      },
      {
        headers: {
          "Content-Type": "application/x-www-form-urlencoded"
        }
      }
    )).data;
    let now = new Date();
    let expiration = (now.setSeconds(now.getSeconds() + tokenData.expires_in - 60)); //Add a minute buffer to expiration time.
    bru.setEnvVar('access_token_set_by_collection_script', tokenData.access_token);
    bru.setEnvVar('access_token_expiration', expiration);
  } catch (error) {
    console.log(error);
  }
} else {
  console.log("using existing token");
}

req.setHeader('Authorization', `Bearer ${bru.getEnvVar('access_token_set_by_collection_script')}`)

This stores the access token and token expiration time in environment variables and checks each request to see if a new token needs to be retrieved.  It would be really helpful if the bruno Oauth2 documentation for client credentials provided an example like this to simplify the authentication process.

The work arounds suggested still seem to require manually clicking the "Get Access Token" on the collection every time the token expires.  This isn't great for api's that use short lived tokens.  Luckily the client credential flow can be automated fairly simply by adding the following Pre Request script on the collection:
const axios = require('axios');

let token = bru.getEnvVar('access_token_set_by_collection_script');
let tokenExpiration = bru.getEnvVar('access_token_expiration');
let currentTime = (new Date()).getTime();

if (!token || !tokenExpiration || tokenExpiration < currentTime) {
  try {
    console.log("requesting new token");
    const tokenData = (await axios.post(
      bru.getEnvVar('AccessTokenUrl'),
      {
        client_id: bru.getEnvVar('ClientId'),
        client_secret: bru.getEnvVar('ClientSecret'),
        grant_type: 'client_credentials'
      },
      {
        headers: {
          "Content-Type": "application/x-www-form-urlencoded"
        }
      }
    )).data;
    let now = new Date();
    let expiration = (now.setSeconds(now.getSeconds() + tokenData.expires_in - 60)); //Add a minute buffer to expiration time.
    bru.setEnvVar('access_token_set_by_collection_script', tokenData.access_token);
    bru.setEnvVar('access_token_expiration', expiration);
  } catch (error) {
    console.log(error);
  }
} else {
  console.log("using existing token");
}

req.setHeader('Authorization', `Bearer ${bru.getEnvVar('access_token_set_by_collection_script')}`)

This stores the access token and token expiration time in environment variables and checks each request to see if a new token needs to be retrieved.  It would be really helpful if the bruno Oauth2 documentation for client credentials provided an example like this to simplify the authentication process.

Since the majority of use-cases use the same scripts at this point, is there a reason why this functionality isn't baked into the client?

I tried it in another way.
Place below script in post response under collection setting
if(req.getAuthMode() == 'oauth2' && res.body.access_token) {     bru.setVar('access_token_set_by_collection_script', res.body.access_token); }
Then go to your request and change the Auth setting to Bearer Token and place below code
{{access_token_set_by_collection_script}}


bearing_change_rate calculation error

Hello,
Thank you for maintaining this library. I started to analyze my flight with it and wanted to inspect turn speed during thermalling. I think that there is some error on bearing_change_rate calculation.
With the below test code there are jumps in the bearing_change_rate even tough it should be quite constant when thermalling.

# file from https://www.xcontest.org/world/en/flights/detail:mikamika/9.11.2024/11:57
f='2024-11-09-XCT-MLA-05.igc'

# Parse an IGC file
flight = Flight.create_from_file(f)

bearing_change_rate = []
bearing = []
# Access individual fixes
alt = []
for fix in flight.fixes[2850:2900]:
    bearing_change_rate.append(fix.bearing_change_rate)
    alt.append(fix.alt)
    bearing.append(fix.bearing)

import pylab
pylab.plot(bearing_change_rate,'-*')
pylab.plot(bearing,'-x')
pylab.legend(['bearing_change_rate','bearing'])
#pylab.plot(alt)
pylab.show()

Hi, Thank you for raising the issue.
I'll take a look at it next week. If you find a solution along the way, feel free to raise a PR.

@surajmandalcell I found the root cause of the issue but not sure what is the best way to fix it.
If changing min_time_for_bearing_change to 3 from FlightParsingConfig then there is no such error in the bearing_change_rate but the bearing_change_rate data in general is more noisy. Some processing would be needed to take account several successive samples instead of just two which distance is min_time_for_bearing_change.
The thermalling what I did was in quite strong wind and rotation speed was quite high. This is the reason why default min_time_for_bearing_change =5 did not work.

@N00BMmika Hi, can you please test 1.1.0 and see if the issue persists. Thanks.

Hi @N00BMmika, so I went in and tried testing it, I could not download the igc you mentioned so had to use one of mine.
In my file I tried different min_time_for_bearing_change and also tested in both previous vs current version. I guess the fixes did not effect this hence the issue is not what I imagined. Can I get the igc file you mentioned and what type of representation are you expecting when you say current line is noisy.

Hi @surajmandalcell
Thanks for update but according to my test the error still remains. My IGC file attached
2024-11-09-XCT-MLA-05.zip
Regarding to:

what type of representation are you expecting when you say current line is noisy
I mean the noise what is seen also in your pictures, 1s has more peaks and 5s is more smooth.


Clarification on the Ingress scenario with Nginx

I want to use this provider to supply certificates to the Nginx Ingress.
I've deployed the driver within the AKS cluster and mounted the volume within the Ingress controller.
Like the instructions described.
The Ingress Controller is created in a separate namespace called "Ingress-nginx".
The secrets are correctly created when I create the SecretProviderClass within the "ingress-nginx" namespace.
But I don't want them there, because my applications (so also the ingresses) life in another namespace.
When I create the SecretProviderClass in the namespace where my apps life the secrets aren't created.
So my understanding is that the SecretProviderClass has to be created in the namespace where the Nginx Ingress Controller is located. But that would mean I need a Ingress Controller per namespace right?

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

ID: 99d11c89-19c6-f881-a5f7-31c17f092500
Version Independent ID: 340c35ed-ecea-ad25-efbe-e02bb8924fc0
Content: Set up Secrets Store CSI Driver to enable NGINX Ingress Controller with TLS on Azure Kubernetes Service - Azure Kubernetes Service
Content Source: articles/aks/csi-secrets-store-nginx-tls.md
Service: container-service
GitHub Login: @Nickomang
Microsoft Alias: nickoman

Thank you for your feedback! We will review and update as appropriate.

@ferronsw As per my understanding, by default nginx ingress controller would monitor all the namespaces, I believe the key point here is to have a SecretProviderClass in the same namespace of ingress.

@Karishma-Tiwari-MSFT that's correct, but because the secrets will then be created in the same namespace as the ingress controller, you have to deploy the apps/ingress in the same namespace as well.

See

Thanks for sharing the other issue. It has been answered by Product team.
Sharing the answer for others to reference from here - https://github.com/Azure/secrets-store-csi-driver-provider-azure/issues/944#issuecomment-1194326052

Secrets Store CSI Driver requires the SecretProviderClass to be in the same namespace as the pod referencing it, so it needs to be in ingress-nginx namespace if it needs to be used by the ingress controller. If you need the secret in different namespace, you can create the SecretProviderClass in the diff namespace and mount the certs to the app pods that's consuming it.

Please let me know if you have any further questions.
We will now close this issue. If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


puppeteer format coverage is missing some information

Some of the folks working on Istanbul recently released the tool puppeteer-to-istanbul, which converts from puppeteer coverage format to Istanbul format, allowing Istanbul reports to be run.
The tool works, but there does seem to be some information missing in puppeteer style output (this is discussed in #1768). Specifically:

callCount is not reported  (it seems like there should probably be a flag to enable callCount).
I noticed block level coverage is working for if statements, but not binary statements, e.g., const foo = 99 || 103.

What steps will reproduce the problem?

collect coverage for a file that executes a line multiple times (see: https://github.com/bcoe/puppeteer-to-istanbul-example, for setting up the test case).
collect coverage for a file that has a binary operation, e.g., const foo = 99 || 100.

What is the expected result?

call counts should be tracked.
partial block level coverage should be collected ([const foo = 99 ]|| 100).

What happens instead?

No callCount information is reported.
the entire line const foo = 99 || 100 is missing coverage.

It would be awesome to get all the fancy pants work that @schuay has done around block-level coverage outputting in reports collected through puppeteer.
CC: @aslushnikov, @shannon, @JoelEinbinder,  @vkoves and @rjaltman

@jackfranklin would it be possible to expose the raw v8 test coverage data? There are some tools which expect this format.
We could add a flag to the stop function to specify the format, or we could introduce a separate method. What do you think?

For additional context, I found this reference in the code that Lars is referring to: https://github.com/modernweb-dev/web/pull/174/files#diff-8365ecf94906ff774beccd6509eec588R88

Indeed. I'm using https://github.com/istanbuljs/v8-to-istanbul/ which expects the raw v8 data format.


Add filters to Find-DbaDatabaseGrowthEvent

Type of Change

[ ] Bug fix (non-breaking change, fixes #)
[x] New feature (non-breaking change, adds functionality)
[ ] Breaking change (effects multiple commands or functionality)
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] Nunit test is included
[x] Documentation
[ ] Build system

Purpose

If you are querying a heavy server that has large number of databases, use of PowerShell filtering requires the command to pull all the data out of the default trace before you can filter it. Added parameters that let you filter the data as it is pulled from the default trace. Improves performance on large systems.
Provides the ability to only pull variations of growth or shrink only, and then only evens for data files or log files.
 However how doing that where it would cover any sequence of log,growth or data,shrink required use of a collection on the event classes. So the logic in the command is backwards, in that I start the collection with all the events in it, and as the filter is tested it removes each event that is not desired.
I'm fairly sure I got the logic right but do please test and break if able.
Commands to test

Love it.  Ran it on a couple servers and does as you showed in your suggested tests.

thanks to you both!


Add copy for the health section

Adds copy for the health section. I also had to make some changes to the dependencies to get things running locally.
@alexgirard Thoughts on removing the long/concise version stuff? It seems like extra work that we don't have the time for. I can remove all of the code references if you agree.

I'm down to yeet the concise version, it doesn't look any shorter than the og one

@alexgirard Could you look at the changes to package.json and confirm you have no problems with them?

Ooh I noticed that some of 2+ word activities don't have a space between them - think it was from a previous PR but if you could patch that in this one that'd be :pray:

Also this branch with the updated packages works for me lgtm


Add: FOX 7 News

Channel Name
FOX 7 News
Alternative Names (optional)
KTBC
Network (optional)
FOX
Owners (optional)
Fox Television Stations; NW Communications of Austin, Inc.
Country
US
Subdivision (optional)
No response
City (optional)
Austin
Broadcast Area
r/<512>
Languages
eng
Categories (optional)
News
NSFW
FALSE
Launched (optional)
No response
Closed (optional)
No response
Replaced By (optional)
No response
Website (optional)
https://www.fox7austin.com/
Logo
https://yt3.googleusercontent.com/RI_Y_U9rwHVcACtGhGQFC_ag0ztuWRrXzMnhgkKtiYahML17hGt3lgkba-6VBtOg7evOZJzPtQ=s900-c-k-c0x00ffffff-no-rj
Notes
Broadcast link: https://tubitv.com/live/555112/fox-7-austin

Already in the database: https://iptv-org.github.io/?q=name:KTBC


docs: added a page for editing messages from a button click

This PR adds a page to show people how to edit messages from a button click (using stuff like dpp::ir_deferred_update_message, etc).
Documentation change checklist

[x] My documentation changes follow the docs style guide and any code examples follow the coding style guide.
[x] I tested that my change works before raising the PR (via running doxygen, and testing examples).
[x] I have not moved any existing pages or changed any existing URLs without strong justification as to why.
[x] I have not generated content using AI or a desktop utility such as grammarly.

Reverted to draft, didn't mean to publish as an open PR.


chore(net): track all bad reported messages

🤖 Generated by Copilot at 173a021
Improve network service metrics for bad transactions. Add a new metric, remove an unused attribute, and fix a double-counting issue in crates/net/network/src/transactions.rs.

Codecov Report

Merging #2321 (173a021) into main (855a7d5) will decrease coverage by 27.67%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2321       +/-   ##
===========================================
- Coverage   71.92%   44.25%   -27.67%
===========================================
  Files         476      476
  Lines       57498    57498
===========================================
- Hits        41353    25446    -15907
- Misses      16145    32052    +15907

Flag
Coverage Δ

integration-tests
16.88% <0.00%> (-2.16%)
:arrow_down:

unit-tests
38.63% <0.00%> (-27.99%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/net/network/src/transactions.rs
46.41% <0.00%> (-5.85%)
:arrow_down:

... and 240 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Clicking outside of the Sidebar

Clicking outside of the sidebar should close the sidebar if it's open

Hi, can I help you with this?

Hi can i help you with this? @jared201

Hi can i help you with this? @jared201

@Weave-Trix ok.

Please have a look at the pull request that I've made. Happy coding 👍

Please have a look at the pull request that I've made. Happy coding 👍 @jared201

will do. thanks!


Multi factor authentication is missing

Multi factor authentication is missing from the authentication flow

Method: PUT
URL: https://auth.riotgames.com/api/v1/authorization
Headers: Content-Type : application/json
Body:
{
"type": "multifactor",
"code": "YOUR 2FA CODE HERE",
"rememberDevice": true
}


clippy: remove from cargo, add to travis

This moves clippy setup from an optional cargo feature to an automatic CI check enforced via travis.
The side-effects of this is that we are now automatically checking every PR against clippy, and that we are dropping a few dependencies from the lockfile:
    Removing clippy v0.0.195
    Removing clippy_lints v0.0.195
    Removing either v1.5.0
    Removing getopts v0.2.17
    Removing if_chain v0.1.2
    Removing itertools v0.7.8
    Removing pulldown-cmark v0.1.2
    Removing quine-mc_cluskey v0.2.4
    Removing semver v0.9.0
    Removing semver-parser v0.7.0
    Removing toml v0.4.6

Travis pass is pinned to a specific clippy+nightly pair, which will need to be bumped from time to time in the future to opt-in new lints.

I usually enable hard-failures on warnings too (cargo clippy -- -D warnings) but there a few warnings reported in the current codebase, and those can be addressed later.

honestly I set it up that way because I hadn't used clippy much back then and wasn't sure of the best way to invoke it. I haven't actually activated the compiler plugin approach in quite a while, I've since just integrated clippy suggestions into my editor. I think the automatic CI approach is a better one, since it automatically validates all incoming prs instead of relying on someone to run it.

looks like the compiler plugin and optional dependency strategies have since been depricated in fact - https://github.com/rust-lang-nursery/rust-clippy/commit/654ff185881b6f5ab7048ed2b0c02227323fe0df#diff-04c6e90faac2675aa89e2176d2eec7d8 and https://github.com/rust-lang-nursery/rust-clippy/commit/fd8a1d20ccad8a2dd7b95a9a9a6fe94048a74d5f#diff-04c6e90faac2675aa89e2176d2eec7d8


Federated Namespaces

Description
Add description here
Progress Tracker

[ ] Before Alpha

[ ] Write and maintain draft quality doc

[ ] During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK

[ ] Design Approval

[ ] Design Proposal.  This goes under docs/proposals.  Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation.  Paste link to merged design proposal here: PROPOSAL-NUMBER
[ ] Initial API review (if API).  Maybe same PR as design doc. PR-NUMBER

Any code that changes an API (/pkg/apis/...)
cc @kubernetes/api

[ ] Identify shepherd (your SIG lead and/or<EMAIL_ADDRESS>will be able to help you). My Shepherd is<EMAIL_ADDRESS>(and/or GH Handle)

A shepherd is an individual who will help acquaint you with the process of getting your feature into the repo, identify reviewers and provide feedback on the feature. They are not (necessarily) the code reviewer of the feature, or tech lead for the area.
The shepherd is not responsible for showing up to Kubernetes-PM meetings and/or communicating if the feature is on-track to make the release goals. That is still your responsibility.

[ ] Identify secondary/backup contact point. My Secondary Contact Point is<EMAIL_ADDRESS>(and/or GH Handle)

[ ] Write (code + tests + docs) then get them merged.  ALL-PR-NUMBERS

[ ] Code needs to be disabled by default.   Verified by code OWNERS
[ ] Minimal testing
[ ] Minimal docs

cc @kubernetes/docs on docs PR
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io

[ ] Update release notes

[ ] Before Beta

[ ] Testing is sufficient for beta
[ ] User docs with tutorials
- Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
- cc @kubernetes/docs on docs PR
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Thorough API review

cc @kubernetes/api

[ ] Before Stable

[ ] docs/proposals/foo.md moved to docs/design/foo.md
- cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
[ ] Soak, load testing
[ ] detailed user docs and examples

cc @kubernetes/docs
cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design

Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Coding

Use as many PRs as you need.  Write tests in the same or different PRs, as is convenient for you.
As each PR is merged, add a comment to this issue referencing the PRs.  Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos.
When you are done with the code, apply the "code-complete" label.
When the feature has user docs, please add a comment mentioning @kubernetes/feature-reviewers and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing.  They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.

Docs

[ ] Write user docs and get them merged in.
User docs go into http://github.com/kubernetes/kubernetes.github.io.
When the feature has user docs, please add a comment mentioning @kubernetes/docs.
When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.

@mwielgus Are the docs ready? Please update the docs in https://github.com/kubernetes/kubernetes.github.io, and then add PR numbers and check the docs box in the issue description

Ping?  Any update on docs?

@mwielgus Another ping on docs. Any PRs you can point me to?

@kelseyhightower is working on the PR.
On Mon, Sep 12, 2016 at 4:34 PM, Jared<EMAIL_ADDRESS>wrote:

@mwielgus https://github.com/mwielgus Another ping on docs. Any PRs you
can point me to?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/features/issues/69#issuecomment-246528526,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJ6NAeGg0lGOuXKRng0ZsdN35idYM3riks5qpeGBgaJpZM4JqZlB
.

Released alpha in v1.4


Paste as plain text

Editor lacks 'Paste as plain text' menu option. It makes it hard to keep the formatting clean when pasting text from other documents

Hello @alexeyvolkoff please describe your problem in more detail. Which editor do you mean? In the community module or in the documents module?

The problem is relevant for Documents editor, but may be also relevant for Spreadsheets and Presentations.  Both in CommunityServer docker integrated over API and in Desktop version of editor.


Add search-pypi extension

Description

This PR adds a new extension for search PyPI packages, I plan to add new features in future, for now it implements a basic search and favourite system
Screencast
https://github.com/raycast/extensions/assets/667029/0bdd6926-5bbf-4900-b984-2636ffc79a4b

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

The Python extension seems to include a search pypi function

That's correct, it was added yesterday 🙂

Closing as duplicate, let's discuss further if needed

I totally missed it! thanks 😊


Entity validation

Optimise CF API requests and ad-hoc entity validation

Added new entity factory
All entity relations are now defined and normalised
When creating a new instance of an action user must specify which entity relations are required
Only those relations will be added to the requests 'include-relations' param
Only those relations will be checked when the entity is validated
Entity validation occurs..
during the api request process (in case a list is missing because it exceeds 50 items)
when an entity is fetched from the store via the entity service
when a page from the pagination helper is fetched from the store
Entity/Pagination will be marked as 'updating' if any relation is missing and fetched

TODO: Docs once merged
TODO: Generically add/remove/clear a child entity collection from it's parent when we modify it (this can be done in a similar way to when we add it)
Other changes

Improved log service
Tidied a LOT of imports
Fixed typos
Remove some undeeded OnInit's
Remove title to events table
Converted space routes and service instance table's to be non-local (if routes was fetched at orgs level each route would miss out on the apps param due to too deep inline depth, this resulted in a lot of spammy yet correct requests to fetch them)

I'm going to merge this in so we can get people using it. I think we could do a second pass on this (tidying up some of the code etc) when we do the api effect refactor.


Added generic oauth login option to teams

Implements a generic OAuth provider as mentioned in this issue: https://github.com/concourse/concourse/issues/539.
Use it by specifying the following on the command line:
concourse
  --oauth-client-id=abc \
  --oauth-client-secret=123 \
  --oauth-auth-url=https://github.com/login/outh/authorize \
  --oauth-token-url=https://github.com/login/oauth/access_token \
  --oauth-display-name=Githubz

This will present a login prompt on the web ui like:

I realise that I'm missing ahem tests and documentation, but would appreciate feedback on my approach (code, variables etc).

Looks good! (Aside from the no tests thing.)
May want to rename the flags to something like --generic-oauth or something though; it looks a bit too "normal" and I worry people may think they should use it even when more specialized providers are available (e.g. Google or GitHub). Something to call out that it does no access verification may also be in order; maybe in the help-text?

Messed up pull request and will need to resubmit.


node-memcached lost Unix socket support

In recent PR, you merged a change with below line.
https://github.com/3rd-Eden/node-memcached/blob/master/lib/memcached.js#L134
Because of that line, even when an address is a path to unix socket, it appends port :11211 to the address causing it to break.
I worked around the issue by using 2.0.0 version.

Again not working on 2.2

{ [Error: connect ENOENT /tmp/memcached.sock:11211]
code: 'ENOENT',
errno: 'ENOENT',
syscall: 'connect',
address: '/tmp/memcached.sock:11211' }


Is it possible/planned to enable assigining a PSTN number to a teams bot?

Now that the Calling API for teams is available (beta) we are very interested about assiging a PSTN phone number to a calling teams bot.
Are there any work planned around this ?
Many thanks !

Hello,
Do you know the target for when to relese thé phone calling and did assignement ?
Thanks!


regarding the metrics function in the model.compile

According to Keras docuementation, A metric is a function that is used to judge the performance of your model. Metric functions are to be supplied in the metrics parameter when a model is compiled.
Is metric used to evaluate the performance only? Will it also affect the training process? I am not very clear about this.
For instance, model.compile(optimizer=Adam(lr=1e-5), loss='binary_crossentropy', metrics=['binary_crossentropy']) . I am using binary_crossentropy as the objective function for the training process. what are the proper setup for the metrics? Here I just use binary_crossentropy as well, can I use other metrics? Does it really matter?

Hello, as far as I understand metrics are there to display additional information usually "accuracy". They are not driving the gradients. They are mainly useful as a tool to monitor over-fitting. You can decide to use them in heuristics to decide for example when to stop the training.
You can have a look at : https://github.com/fchollet/keras/blob/master/keras/metrics.py

Hello, thanks.  With respect to monitor over-fitting, I am monitoring the 'val-loss' during the training process.  In other words, when val-loss is improved, the system will automatilly save the model for this epoch; otherwise, not. Is this the right one? How can this interact with monitoring metics to collaborate to overcome over-fitting?  Thanks.

Yes what you are doing is fine. It depends on what you are interested in and what your problem is. Sometimes you want to to monitor loss, sometimes you want to monitor accuracy.
Metric are just additional information. You can use them if you want, doesn't mean you have the obligation to.


Unknown OpenFlow traffic and missing packets when following Mininet walkthrough

Issue 1: Unexpected OpenFlow traffic
The Mininet walkthrough says that after starting up Wireshark and Mininet that "for now, there should be no OpenFlow packets displayed in the main window." However, as shown in the attached screenshot, I see OpenFlow packets on the loopback interface every few seconds (ECHO_REQUEST and ECHO_REPLY). Is this expected behaviour? Am I doing something incorrectly? This may simply be a case of me not understanding something, as opposed to a problem with Mininet.
Issue 2: Missing ping packets
I also note that while running h1 ping -c 1 h2 twice (after creating a minimal topology with sudo mn) generates the expected output in the command line (ie: two successful pings, with the first having a longer RTT than the second) the expected packets do not appear in Wireshark (ie: the  PACKET_INs and PACKET_OUTs are missing). The packets expected as a result of the first ping appear, but the packets expected as a result of the second do not. After some trial and error I have found that waiting for a couple of minutes between pings results in the expected packet activity always showing up in Wireshark, but that when performing pings in quick succession I see no PACKET_INs or PACKET_OUTs for the latter pings.
Environment Setup/Background
As you can see from the attached screenshot I am running Mininet in the preconfigured VM and piping the output of Dumpcap (running on the VM) to Wireshark on my host machine via SSH. This is slightly different to the setup recommended in the Mininet VM setup notes, but I would not have expected this to cause problems. Have I missed something?

(2) should be expected behavior if you understand OpenFlow.
(1) is also expected - perhaps we should clarify the walkthrough.

Yes, my understanding of OpenFlow has improved substantially since I posted this issue (hence why I closed it) 😉
Clarifying the walkthrough would probably have helped me at the time. Let me know if you'd like any further feedback.


Spectator screen never shows killer

This feature used to work but now whenever the user presses "K" in the spectator screen seemingly no matter what happened the killer information is never "known". I have already done some preliminary investigation into this and will continue to do so.

This may not be broken as I saw it working on a mission earlier today :S

I believe it has to do with the ace intercept of the hit and killed eventhandlers. The eventhandler doing tracking (the stuff that appears at the end of the mission) should be more consistent.

I believe it has to do with the ace intercept of the hit and killed eventhandlers. The eventhandler doing tracking (the stuff that appears at the end of the mission) should be more consistent.

Have you got any suggestions as to what to look into? I remember this seemed to work consistently before Christmas. Are we aware of any ACE updates which may have affected this?

Did a bit of research into this, I think the variables being looked at are only local to the server, we'd probably need to recode this to do it the same way ACEX does, at some point.
Reference: https://github.com/acemod/ACEX/blob/master/addons/killtracker/XEH_postInit.sqf

Haven't seen this issue recently, so closing for now.


Added groupnorm and layernorm to onnx_ops.py

Added groupnorm and layernorm to onnx_ops.py

Args don't match operator args. https://github.com/onnx/onnx/blob/main/docs/Operators.md#Min


How to run browser-box?

Hello,
I've downloaded browser-box and installed the wrapper scripts as per the instructions in the README.
Could you please document how to use it?
I tried docker run -it sameersbn/browser-box:2018.07.21 and that gave me back my shell prompt (didn't seem to do anything).
Thanks!
@atsaloli

P.S. I installed browser-box on Windows 10.


feat(pkg.model) add model unit test

…-db/arana/issues/778

What this PR does:
add model unit test
Which issue(s) this PR fixes:

Fixes #778
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (108fb12) 40.33% compared to head (d743cb0) 40.47%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #802      +/-   ##
==========================================
+ Coverage   40.33%   40.47%   +0.13%
==========================================
  Files         265      265
  Lines       26711    26711
==========================================
+ Hits        10775    10812      +37
+ Misses      14782    14736      -46
- Partials     1154     1163       +9

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.