Exporting in 4.3 RC2 using CLI headless mode without a .godot folder freezes the build

Tested versions

Reproducible in v4.3.rc2.official [3978628c6]
Not reproducible in v4.2.2 official

System information
Ubuntu 20.04.6 LTS
Issue description
Hi team,
I've been using Godot 4.2 for a while now and am recently trying out 4.3 RC2 to port my project over.
I'm having trouble with my automated build machine pipeline when exporting my game.
In Godot 4.2, when exporting my the game using the command line, I'd run this command:
$GODOT_ROOT/godot --verbose --headless --path $WORKING_DIR/ravageous/game --export-release Release_Linux_x86_64 $outFolder/ravageous

This works fine in 4.2. Even though I don't commit the .godot folder, running that above command would re-generate that folder.
However, in Godot 4.3, the build is stuck.
root@8a0c47065a83:/tmp# $GODOT_ROOT/godot --headless --path $WORKING_DIR/ravageous/game --export-release Release_Linux_x86_64 $outFolder/ravageous
libfontconfig.so.1: cannot open shared object file: No such file or directory
Godot Engine v4.3.rc2.official.3978628c6 - https://godotengine.org
(stuck)

It may be related to how re-generating the .godot folder is done using the headless mode.
In Godot 4.2, the below command would re-create the .godot and the process would exit gracefully.
godot --editor --path $WORKING_DIR/ravageous/game  --headless --quit

If I run the same command in 4.3.rc2.official, it creates the .godot folder, but it doesn't terminate (even though I have the --quit argument). I think it just has the editor window open in the background in the build server, which is why exporting is stuck.
If I export the game in 4.3 with the .godot folder, the export is successful.
Steps to reproduce

Create an empty/basic project in Godot 4.3 RC2.
Using the CLI, export the game using the headless mode.
Sample command:

$GODOT_ROOT/godot --verbose --headless --path $WORKING_DIR/ravageous/game --export-release Release_Linux_x86_64 $outFolder/ravageous

The same command in 4.2 works fine.

Minimal reproduction project (MRP)
Any empty/basic project created in Godot would be fine

Related to https://github.com/godotengine/godot/issues/92833.

Can you test 4.3.rc3?

My guess from the error message "No such file or directory" is the problem were caused by the global class name file missing when no gdscript are present in the projecr. This has been fixed with #94991 and has been merged for 4.3 rc3.

Hi. I'll try this in RC3 tonight. Thanks

I can't reproduce the issue with 4.3.rc2. I tried with a fully empty project (refuses to export), one with just export presets configured (refuses to export since there's no content), adding just a main Node2D scene (exports fine), adding a GDScript (exports fine).
Could you provide a reproduction project?

Hi @akien-mga
I think I found the root cause.
So it turns out, it's not related to upgrading from 4.2 to 4.3, but rather, after upgrading to 4.3, I also installed the Jolt addon.
So now, when I delete the .godot folder and run
/home/saleem/software/godot/godot --headless --editor --path /home/saleem/CLionProjects/ravageous/game --quit

It freezes. But when I remove the --headless and --quit argument (so the GUI is opened), I get a warning box: 'Some extensions need the editor to restart to take effect`

I think that's why when I run with --headless on the first time it gets stuck - because it's waiting for me to press the 'Continue' or 'Restart' button.
If I leave it running for like 10 seconds (so we give enough time for the .godot folder to be created), and then kill the process, and re-run it with --headless again, it works because the editor is restarted.
I'm not sure if the issue is present with 4.2 because I didn't have the Jolt addon installed there. I can try it if you want?
Anyway, this ticket can be closed.
But ideally, a warning message should come up when running in headless mode if it needs to be restarted. I can raise an issue if you want?
Thanks

Great news! Thanks for testing.
For your information, there's a PR to fix this problem this Jolt (and any other GDExtensions) that should be merged for the next Godot version that will fix the need to restart the editor on first start: #93972

For the record, I've just run into this problem, on 4.3, when .godot is timestamped identically to the rest of the files in the project.
In my case, this'd happened because I'd just duplicated the entire project using cp -r. Using cp -a instead (which preserves timestamps) fixed this, and Godot ran the export fine.

This issue was fixed by #93972 already.
@snoopdouglas Are you using GDExtensions? If yes, your issue might be fixed too. If not, this is likely a separate bug that should have its own bug report with a reproduction project.

@akien-mga Ah right, no GDExtension - will open a new issue.


Parent macro_insert's angles getting messed up

An entity (particle_shooter from Featureful SDK, in case it's somehow relevant) within a macro_template sets its angles to {angles}. That, supposedly, reads the angles property of the macro_insert instantiating it. It, in turn, has its angles set to 17 270 0.
Expected behavior is that the angles of the particle_shooter will get set to 17 270 0. Instead, the angles end up being set to 16.236122131347656<PHONE_NUMBER>8496094 -17.729080200195312.
Example map for reproduction is provided:
mess_bad_angles.zip
The .rmf file is the source map, the .map file is the result of macro expansion.
MESS version used is <IP_ADDRESS>.

When an instance is created, the content of the chosen template is automatically moved, rotated and scaled depending on the position, orientation and scale of the instance-creating macro entity. That affects not only brushes but also the origin, angles and scale properties of entities.
So by setting the angles of the particle_shooter to {angles}, you're effectively rotating it twice - first {angles} is evaluated to 17 270 0, and then the entity is rotated by 17 270 0, which produces the angles that you're seeing. Set angles to 0 0 0 instead.


Logical flaw in "lift & shift" path

There is a logical flaw in the "lift & shift" path of the "Choose a candidate service" flowchart.
In the path following "lift & shift", there is a decision "can it be containaerized?". If you follow the "No" path, it leads to a decision "COTS app that can't be containerized?". This is the flaw: it is already decided at this point, that the app can't be containerized. So the decision that is left is basically "COTS app?" instead of "COTS app that can't be containerized?".
This should be fixed IMHO.
Further thoughts of mine:
if the app is a COTS app, the flowchart advises to use a VM. Now if it isn't a COTS app, you should use app services. But there are limitations for app services (such as the supported frameworks, etc.) which would not allow running any non-COTS app on app services.
Anyway, I find it great that there is some advice on which platform you should run COTS apps (here: VM). I already ran COTS apps on app services, which kind of worked, but I was left with the impression that this is rather an unusual usage for app services (as there was little documentation on this usage scenario). So I appreciate some official statement to this scenario very much.
Thanks for the architecture docs!

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

ID: 510808e8-db5d-6b07-9a04-6edb743a2dfc
Version Independent ID: 20d098aa-ef31-cb26-d677-765cfc9a7164
Content: Choose an Azure compute service - Azure Architecture Center
Content Source: docs/guide/technology-choices/compute-decision-tree.yml
Service: architecture-center
Sub-service: azure-guide
GitHub Login: @EdPrice-MSFT
Microsoft Alias: edprice

@khaliddermoumi we'll review your feedback and get back to you shortly. Thanks.

@khaliddermoumi - I am going to close this issue, as the flow chart was updated to address your issue. Your point about App Services having limitations, it is true. This is meant to be a high-level decision tree that does not take into account all cases.


spotify-player crashes on launch with rodio-backend

Describe the bug
Immediately on launch, spotify-player prints its gui and the error message "Aborted", then crashes. Occurs either with or without dbus-launch.
To Reproduce
Launch spotify-player. I believe the rodio-backend feature is the culprit, see below.
Expected behaviour
The player should not crash on launch.
Log and backtrace
2024-11-23T14:35:51.875908Z  INFO spotify_player: Configurations: Configs { app_config: AppConfig { theme: "default", client_id: "0157ccd61a3a4370bdf81566433e5495", client_port: 8080, player_event_hook_command: None, playback_format: "{status} {track}\n {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, page_size_in_rows: 20, play_icon: "|>", pause_icon: "||", liked_icon: "<3", border_type: Hidden, progress_bar_type: Rectangle, playback_window_position: Top, cover_img_length: 6, cover_img_width: 3, cover_img_scale: 1.0, playback_window_width: 6, enable_media_control: true, enable_streaming: Always, enable_cover_image_cache: true, default_device: "x230", device: DeviceConfig { name: "x230", device_type: "computer", volume: 70, bitrate: 320, audio_cache: true, normalization: false } }, keymap_config: 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: [Alt(Char('r'))] }, command: ToggleFakeTrackRepeatMode }, 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: Mute }, 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: [Ctrl(Char('z'))] }, command: AddSelectedItemToQueue }, 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('O'))] }, command: OpenSpotifyLinkFromClipboard }, 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 }, Keymap { key_sequence: KeySequence { keys: [None(Char('N'))] }, command: CreatePlaylist }] }, theme_config: ThemeConfig { themes: [Theme { name: "default", palette: Palette { background: None, foreground: None, black: Color { color: Black }, blue: Color { color: Blue }, cyan: Color { color: Cyan }, green: Color { color: Green }, magenta: Color { color: Magenta }, red: Color { color: Red }, white: Color { color: Gray }, yellow: Color { color: Yellow }, bright_black: Color { color: DarkGray }, bright_white: Color { color: White }, bright_red: Color { color: LightRed }, bright_magenta: Color { color: LightMagenta }, bright_green: Color { color: LightGreen }, bright_cyan: Color { color: LightCyan }, bright_blue: Color { color: LightBlue }, bright_yellow: Color { color: LightYellow } }, 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, playlist_desc: None, table_header: None, selection: None } }] }, cache_folder: "/home/moe/.cache/spotify-player" }
2024-11-23T14:35:51.876140Z  INFO spotify_player::state::data: Loading Playlists data from /home/moe/.cache/spotify-player/Playlists_cache.json...
2024-11-23T14:35:51.877490Z  INFO spotify_player::state::data: Successfully loaded Playlists data!
2024-11-23T14:35:51.877500Z  INFO spotify_player::state::data: Loading FollowedArtists data from /home/moe/.cache/spotify-player/FollowedArtists_cache.json...
2024-11-23T14:35:51.877521Z  INFO spotify_player::state::data: Successfully loaded FollowedArtists data!
2024-11-23T14:35:51.877529Z  INFO spotify_player::state::data: Loading SavedAlbums data from /home/moe/.cache/spotify-player/SavedAlbums_cache.json...
2024-11-23T14:35:51.891698Z  INFO spotify_player::state::data: Successfully loaded SavedAlbums data!
2024-11-23T14:35:51.891713Z  INFO spotify_player::state::data: Loading SavedTracks data from /home/moe/.cache/spotify-player/SavedTracks_cache.json...
2024-11-23T14:35:51.891729Z  INFO spotify_player::state::data: Successfully loaded SavedTracks data!
2024-11-23T14:35:52.210000Z  INFO spotify_player::auth: Successfully used the cached credentials to create a new session!
2024-11-23T14:35:52.289606Z  INFO spotify_player::token: Getting new authentication token...
2024-11-23T14:35:52.338980Z  INFO spotify_player::token: Got new token: Token { access_token: "BQBStDLFCu6Vp9_UXUi3zX7qmuHkj53B6RxlGirv_pmVfQzdB0z6rX8_yOkAmWecH1wlv30n4u_CSziX8AAddVMRRB82VPmQOPEUH3uPqRlDAIbwqqOmkwFpV__0g5GhDOdKyhiE24EZuKwJjA8R_jIm4KDUr3iou9QDZUB26ETL3L9IoG0qO45K5DjA7HEbl7Z2lkCyaT14DucwHoQ62fI59UnvDNVCK57DV9lw3ZgKPLfYhGD4ls4wCC8a-XHWpwuAr2krV-N82RBhBMERszwQCTxwf2fcRMfXJcFNGWCIJy0oAEDvCXVA5x8pUPPNgH4VX_gDZ20", expires_in: TimeDelta { secs: 3600, nanos: 0 }, expires_at: Some(2024-11-23T15:35:52.338973741Z), refresh_token: None, scopes: {} }
2024-11-23T14:35:52.339047Z  INFO spotify_player::streaming: Application's connect configurations: ConnectConfig { name: "x230", device_type: Computer, initial_volume: Some(45875), has_volume_ctrl: true, autoplay: false }
2024-11-23T14:35:52.339076Z  INFO spotify_player::streaming: Initializing a new integrated player with device_id=523a39cd-98b8-45b5-8546-efe6238d677e
2024-11-23T14:35:52.339224Z  INFO spotify_player::streaming: Starting an integrated Spotify player using librespot's spirc protocol
2024-11-23T14:35:52.506922Z  INFO spotify_player: No playback found on startup, trying to connect to an available device...
2024-11-23T14:35:52.506986Z  INFO spotify_player: Starting a client socket at <IP_ADDRESS>:8080
2024-11-23T14:35:52.507644Z  INFO spotify_player::media_control: Initializing application's media control event watcher...
2024-11-23T14:35:52.510699Z ERROR spotify_player: Failed to start the application's media control event watcher: err=DbusError(
    D-Bus error: /usr/bin/dbus-launch terminated abnormally without any error message (org.freedesktop.DBus.Error.Spawn.ExecFailed),
)
2024-11-23T14:35:52.605917Z  INFO client_request{request=GetUserFollowedArtists}: spotify_player::client: Successfully handled the client request, took: 98ms
2024-11-23T14:35:52.668047Z  INFO client_request{request=GetCurrentUser}: spotify_player::client: Successfully handled the client request, took: 160ms
2024-11-23T14:35:52.678395Z  INFO client_request{request=GetUserSavedTracks}: spotify_player::client: Successfully handled the client request, took: 171ms

Got a panic: PanicHookInfo {
    payload: Any { .. },
    location: Location {
        file: "/home/moe/.cargo/registry/src/index.crates.io-6f17d22bba15001f/librespot-playback-0.4.2/src/audio_backend/rodio.rs",
        line: 178,
        col: 53,
    },
    can_unwind: true,
    force_no_backtrace: false,
}

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: start
             at /home/buildozer/aports/main/musl/src/musl-1.2.5/src/thread/pthread_create.c:207:2

Environment
Linux x230 6.6.61-0-lts #1-Alpine SMP PREEMPT_DYNAMIC 2024-11-14 19:34:11 x86_64 Linux
spotify_player 0.18.1
lyric-finder,media-control,rodio-backend,sixel,streaming
Additional context
The panic in the backtrace is caused by the unwrap on the following line:
let (sink, stream) = create_sink(&host, device).unwrap();

I'll update this issue after retrying with the pulseaudio backend (via pipewire).

apologies lol, i haven't updated my apkbuild for this in a while. i'll delete if it isn't broken on v20.1.

closing as i can no longer rebuild, opening a new issue for that


Access request for M Felt

Access level:

[ ] Non-privileged
[x] jenkins user
(I might already have this)
[x] root/Administrative
(I already have this)
[x] other (Please specify):
Dashboard builds
System for which access is needed: AIX systems

Please explain why you need this access including whether it is a temporary or permanent request:
need access to re-run build jobs (for tracking purposes), permanent

Added to the infrastructure github team so you should now be able to run build on all of the hotspot build jobs 👍🏻


Support suffix matches for headers

The gateway API allows wildcard hostnames such as *.example.com to be used in HTTPRoutes https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io%2Fv1beta1.Listener

Added a suffix match in the Xds IR as well as the xds matcher translation to support this case

Fixes: https://github.com/envoyproxy/gateway/issues/738
Signed-off-by: Arko Dasgupta<EMAIL_ADDRESS>

picked suffix instead of regex, since suffix matches are faster


Updated advisory data for Percona

Any chance we know specifically which version or git commit fixed this, that we could include in the note? Also curious if we know why the scanner found this!

I'm not able to find exact documentation for CVE-2021-27928 regarding Percona for mySQL. The closest I could find was this documentation about it being fixed in Percona for mySQL with XtraDB here https://docs.percona.com/percona-xtradb-cluster/8.0/release-notes/Percona-XtraDB-Cluster-8.0.22-13.1.html


colab pro

Hello;
Thank you for your amazing job!
Can I run this code on google colab pro? If so, what changes should I done to have the outputs?
Thank you in advance.

Hi. Thank you for your interest.
I do not have experience with colab, so I cannot provide any supports.
But, our code work in linux OS, so it'll work in the colab platform if it provides linux-based environments.


The bug with the slope of a template reaction with two nodes is fixed

a straight line is defined for both source edge style and target edge style of template_reaction_edge_style1 plugin

the bug with getting the connectedToCentroidNodeControlPoint of MyConnectedToEndCentroidShapeLineGraphicsItem class is fixed (control point 2 should be returned by this function)

This PR fixes the #125 issue.


radar 2.0 crashes

radar 2.0 does not work any more. It becomes shortly green, then it went to red.
There are some debug messages von radar 2.0
Thanks for your help
adar2.0	2020-02-23 14:19:27.010	info	(17800) radar2 set to scan every 20 seconds and printers every 720 minutes.
radar2.0	2020-02-23 14:19:27.008	info	(17800) arp-scan will use the following interfaces: [ 'br0' ]
radar2.0	2020-02-23 14:19:27.005	info	(17800) Remove name end for host names: .fritz.box
radar2.0	2020-02-23 14:19:27.003	info	(17800) use known IP list: [ '<IP_ADDRESS>' ]
radar2.0	2020-02-23 14:19:27.000	info	(17800) use known BT list: [ '01:12:23:34:45:56' ]
radar2.0	2020-02-23 14:19:26.995	info	(17800) radar2 set to flag items away if they are not seen for 2 minutes
radar2.0	2020-02-23 14:19:26.993	info	(17800) found 'node-bluetooth'
radar2.0	2020-02-23 14:19:26.961	info	(17800) found '@abandonware/noble'
radar2.0	2020-02-23 14:19:26.425	info	(17800) Adapter disconnected and stopped with dostop(false) and callback(true)
radar2.0	2020-02-23 14:19:26.419	error	at process._tickCallback (internal/process/next_tick.js:63:19)
radar2.0	2020-02-23 14:19:26.419	error	at state.handle.lookup (dgram.js:242:18)
radar2.0	2020-02-23 14:19:26.419	error	(17800) Error: bind EACCES <IP_ADDRESS>:67
radar2.0	2020-02-23 14:19:26.417	error	(17800) uncaught exception: bind EACCES <IP_ADDRESS>:67
radar2.0	2020-02-23 14:19:25.829	info	(17800) net-ping not available! Will try to use normal ping!
radar2.0	2020-02-23 14:19:25.797	info	(17800) radar2 initialization started...
radar2.0	2020-02-23 14:19:25.583	info	(17800) starting. Version 1.0.9 in /opt/iobroker/node_modules/iobroker.radar2, node: v10.19.0

same problem here after update node.js to 12.16.3 and npm to 6.14.4

As listed in readme, you need to rerun the scripts after updating node or even after updating system with some new versions of BT or other drivers because the new versions do not have authority!

what do you mean with rerun scripts?

In the readme of the adapter you find installation section where you are asked to do this:
`sudo apt-get install -y coreutils libcap2-bin arp-scan bluetooth bluez libbluetooth-dev libudev-dev net-tools
and below need to be run whenever you update nodejs!
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which arp-scan)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which node)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which arp)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which hcitool)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which hciconfig)
sudo setcap cap_net_admin,cap_net_raw,cap_net_bind_service=+eip $(eval readlink -f which l2ping)`
You need to rerun the commands below the second line!

Hi Frank,
ok. I'll try this. Thanks!!
Have you any news about the adapter without bluetooth device? I've a virtual machine without bluetooth device. Unfortunately the adapter crashes because of this.
thank you in advance
best regards

I tested this on one of my VMs without BT and it works if you switch noble off (use hcitool instead of noble) for me. Did you test this?

Hi,
it works both (without bluetooth and after nodejs update). Thank you very much!!
best regards

Hi,
It works for me now too.
First I copied the above setcap lines but there were some missing " ' ".
So I copied them from the radar2 readme in github. After this restart radar2 failed again.
Then I switched from noble to hcitool in the radar2 config and now radar2 works fine.
My BananaPI M3 has BT onboard, but this BT is not supported with raspbian on the bananapi.
Thanks for your help
Axel


Allow oauth services to be verified against services manager

This pull buries the service into the OAuth access token (TGT) and encodes the final result as base64. The profile controller decodes the access token, and verifies the result against services manager for service access as well as attribute release.
Presently, the service will not be checked if it's disabled after TGT is granted to it as an access token, and ALL attributes are released regardless of the service attribute release policy.

I think I get the idea, but does it really bring additionnal security? I can forge an access token with a TGT and a service identifier, cannot I?
If we want to go down that way, we should generate a JWT using the JWTGenerator from pac4j (with encryption and signature): the subject and attributes would come from the current authenticated user and the audience would be the service identifier.
Does it make more sense?

I think I get the idea, but does it really bring additionnal security?

First note that the intent of this PR is not to add additional security measures on the token format itself. Maybe base64 encoding of the token provides a layer of obfuscation, but it absolutely does nothing to strengthen the integration security-wise. From that perspective, this work is equal to what is in master right now.

I can forge an access token with a TGT and a service identifier, cannot I?

You cannot forge a TGT. It needs to exist in CAS, and additional checks run to ensure it is valid.
Also, the main goal, (which you would count as a security measure) is to ensure the relying part only gets attributes that CAS has authorized. I would call this a security issue in the current impl. "Receiving things one has no business of getting" is a security issue.
I am completely in favor of using JWTs as alternatives to access tokens, but that seemed like an approach better suited for a long-term dev effort. We can review that for 4.3 and have this patch be of immediate use in 4.2. I'd also be open in cancelling this pull and documenting the work to be done in a separate issue to be handled perhaps by you in form of JWTs. All options are valid to me.

You cannot forge a TGT hopefully, but my point was that you can forge an access token by using an existing TGT and another service identifier than the one for which the TGT was delivered (as I can encode / decode base64 easily).
I can only agree that the current implementation is not satisfactory.
After my unsuccessful attempts to move on to a brand new OAuth / OpenId Connect implementation, I'm "just" going to improve our current implementation, starting by the use of JWT (see: https://github.com/Jasig/cas/issues/514#issuecomment-166110600).
Let's merge this one for 4.2 not to loose your efforts and this improvment.

If you think it can make sense I can encrypt the final access token using a secret and send that back and then decrypt it when the profile controller takes it. that might be something I might could be able to do

I think it would have been better with encryption, but I saw it has been already merged (I guess you prepare the release). So no problem, leave that security enforcement to JWT.

Well, we still have a couple of days before the RC1 release, so I can definitely prepare something to encrypt that token. PR upcoming.


Upgrade dependency

Upgrade<EMAIL_ADDRESS>to version 19.1.2

Added by OX Security


Socks 4 support

Even though the project name is socks5, it is still nice to have socks 4 support.

Current master fixed this issue.


VCV accession not being captured

Clinvar accession https://www.ncbi.nlm.nih.gov/clinvar/variation/813443/
has only one SCV with NO last eval date. In this case, ClinVar does not include the header line for the aggregated max last evaluated date.
The chrome extension is not picking up the data attributes needed to properly capture the annotation.
The extension presumed to always have a fixed display in the top header of the screen so when certain fields are missing or things are out of order the extension is mis-matching the data elements with the fields being captured.

The proper solution is to change the chrome extension to use javascript.evaluate with xpath expressions to look for the associated labels in the list and validate the field mappings and when they are missing. Currently it is based on the querySelectorAll function which is using array positions to presume which value appears on which row of the html list.

v1.9.1 includes fix


fixing division by zero error when csv trace too small to calc metrics

Pull Request
Title
When a user provides too small of a CSV trace (larger than window size but too small to calculate metrics, we get this error:
Traceback (most recent call last):
  File "/home/osdi-eval/vasim/tests/test_metrics_data_window.py", line 152, in test_too_small_data
    cfg = runner.run_simulation()
  File "/home/osdi-eval/vasim/simulator/InMemorySimulator.py", line 162, in run_simulation
    return self.get_metrics()
  File "/home/osdi-eval/vasim/simulator/InMemorySimulator.py", line 126, in get_metrics
    metrics = calculate_and_return_metrics_to_target(self.cluster_state_provider.data_dir, self.target_simulation_dir)
  File "/home/osdi-eval/vasim/simulator/analysis/plot_utils.py", line 116, in calculate_and_return_metrics_to_target
    metrics = calculate_metrics(merged)
  File "/home/osdi-eval/vasim/simulator/analysis/plot_utils.py", line 84, in calculate_metrics
    "slack_percentage": merged['SLACK'].sum() / merged['CURR_LIMIT'].sum() * 100,
ZeroDivisionError: division by zero

Description
This will fix the bug in calc metrics, and the secondary error in the graph, by returning {} and checking for it.

Type of Change
Mark an x in the boxes that apply:

[x ] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Refactor
[ ] Documentation update
[ ] Tests

Testing
Please see updated test file.

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

Project coverage is 72.34%. Comparing base (2a7e4ab) to head (3247463).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #55      +/-   ##
==========================================
+ Coverage   72.16%   72.34%   +0.17%
==========================================
  Files          21       21
  Lines        1031     1034       +3
  Branches      126      127       +1
==========================================
+ Hits          744      748       +4
  Misses        236      236
+ Partials       51       50       -1

Flag
Coverage Δ

unittests
72.34% <100.00%> (+0.17%)
:arrow_up:

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

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


WorkboxSW Precache doesn't allow for 'waiting' worker's precached assets to be used

Library Affected:
workbox-sw
Browser & Platform:
"all browers"
Issue or Feature Request Description:
If we take a look here: https://github.com/GoogleChrome/workbox/blob/5b97922f3d4e06561097f02870f20693b79ee738/packages/workbox-sw/src/lib/workbox-sw.js#L314-L349
You can see the precache default 'fetch' listener only will try to respond with URLs that are precached for this worker.
Shouldn't it be safe to let the 'fetch' listener for assets reply with any assets in the cache (i.e. if there is a worker in waiting that installed assets, should not those too be available to the client?) I say this because we are not a full PWA, and our HTML will not be cached (yet!).
We may do proactive updates to our SW to cause an installation of new assets to kick off in the background, but that new worker may not become active until the exit all tabs.  I think it would be safe to let an active worker reply with assets from workers in 'waiting', no?
I can probably use PrecacheController for this, or register my own 'fetch' event listener for assets which would take care of it but is there any reason why the files that are valid to reply to asset requests have to be a part of the current worker?
Thanks!
Joe
When reporting bugs, please include relevant JavaScript Console logs and links to public URLs at which the issue could be reproduced.

Basically I resolved this like this:
const workboxPrecachedAssetsCacheKey = `${cacheId}-workbox-precaching-revisioned-v1-${scope}`;

// This is a mechanism to load assets that are precached from 'waiting' workers.
// Discussion here:
workboxSW.router.registerRoute(/\.(css|js|svg|png|jpg|ico)$/, {
    handle: async ({ event }) => {
        const assetCache = await self.caches.open(workboxPrecachedAssetsCacheKey);
        return await assetCache.match(event.request) || workboxSW.strategies.networkOnly().handle({ event });
    }
});

I think the reasoning for not letting the SW return the newly cached assets from the waiting state SW is that if the new installation fails for some reason your app might end up using with different versions of assets.
It might happen that the page would get 1.js V1 and 1.css V2 and if they're not compatible the app is broken. "Broken" of course depends on the app, not the same for every app.
So it's all or nothing.

Got it! Thanks for the explanation.
I think in our case since we version the file path / file name it should be OK but in cases of unversioned filenames that makes sense
Sent from my iPhone

On Apr 8, 2018, at 9:13 PM, Pietari Heino<EMAIL_ADDRESS>wrote:
I think the reasoning for not letting the SW return the newly cached assets from the waiting state SW is that if the new installation fails for some reason your app might end up using with different versions of assets.
It might happen that the page would get 1.js V1 and 1.css V2 and if they're not compatible the app is broken. "Broken" of course depends on the app, not the same for every app.
So it's all or nothing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix dependencies and javadoc errors

@tischi this is a pull request against the scijava29.1.0 branch, in preparation of setting up Travis CI.
If you approve the changes, please merge into that branch and I'll go ahead with travisifying the repository.
(See the commit messages for detailed explanations what was done.)

Thanks so much!


set custom instructions dynamically

custom instructions can drastically change quality of the output based on specific requirements.
it would be nice to be able to set them dynamically via some option available from command palette, or even better, to be able to store the custom instruction in frontmatter or some other place directly inside the note

we are looking into it,
thanks for sharing the idea

It is possible to use the handlebar logic in the custom instructions, you have access to all the variables in the frontmatter. See  https://handlebarsjs.com/guide/builtin-helpers.html#if

you can set the custom instruction field in the settings to something like
{{yaml.instruction}}

and then go to your frontmatter and add variable
instruction: "you custom instruction here"


Beauty domain?

Current domain is doc-pad-api.vercel.app
It looks kinda ugly, what if to buy or stole a nice one? :p

Done, mrakopedia.tk


2023.38.4

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Update Model s plaid to 2023.38.4, car updated doesn't appear in Teslamate
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
2023-10-29 22:17:11.590 [error] GenStateMachine :"3" terminating
** (MatchError) no match of right hand side value: {:error, #Ecto.Changeset<action: :insert, changes: %{date: ~U[2023-10-29 22:17:11.502000Z], speed: 0, power: 0, odometer: 8852.30542, tpms_pressure_fl: Decimal.new("2.85"), tpms_pressure_fr: Decimal.new("2.85"), tpms_pressure_rl: Decimal.new("2.775"), tpms_pressure_rr: Decimal.new("2.9"), battery_heater_on: false, battery_level: 40, usable_battery_level: 39, battery_heater: false, driver_temp_setting: Decimal.new("21.0"), fan_status: 0, inside_temp: Decimal.new("22.7"), is_climate_on: false, is_front_defroster_on: false, is_rear_defroster_on: false, outside_temp: Decimal.new("20.5"), passenger_temp_setting: Decimal.new("21.0"), ideal_battery_range_km: Decimal.new("215.25"), rated_battery_range_km: Decimal.new("215.25"), est_battery_range_km: Decimal.new("182.39")}, errors: [latitude: {"can't be blank", [validation: :required]}, longitude: {"can't be blank", [validation: :required]}], data: #TeslaMate.Log.Position<>, valid?: false>}

Screenshots
No response
Additional data
No response
Type of installation
Manual
Version
1.27.3

Yes, it is covered by this issue report: https://github.com/adriankumpf/teslamate/issues/3371
Interestingly, this is now a documented change: https://developer.tesla.com/docs/fleet-api#vehicle_data

I just got 2023.38.6 (EU) the day before yesterday, and Teslamate hasn't been able to fetch data since...

Like you @cicob i have installed yesterday 2023.38.6 (EU) and i lost access in Teslmate.
i'm using a manual installation of Teslamate.
I just had to grab the file from here https://raw.githubusercontent.com/adriankumpf/teslamate/8134150b247eec5a08572e62fdc4ebe6fda22f63/lib/tesla_api/vehicle.ex and compile.
Everything worked again.

Oh, ok, thanks
In the meantime I found a compiled patch over here:
https://github.com/adriankumpf/teslamate/pull/3373
I can confirm that it helped for me. The car is back online.
´´´
$cat docker-compose.yml
version: "3"
services:
teslamate:
#image: teslamate/teslamate:latest
image: jsightler/teslamate:20231029
restart: always
...
´´´

This is resolved in the latest TeslaMate release 1e7c9a4


Site for MaptimeMSP

@geografa
MaptimeMSP is ready to set up our own site at maptime.io/msp. Will you create a new repository (named "msp") under the Maptime organization account and include our chapter's organizers to administer it? We're delighted to use Starter – it looks simple and lovely.
MaptimeMSP Organizers Github Usernames:
mtaylorlong
lpuhl
fawcett
bitner
Let me know if you need anything else from me. No rush on this. Thanks for your help!

Cool. Thanks - you're live:

http://maptime.io/msp/
https://github.com/maptime/msp

Let me know if you have questions.


Incorrect symbol chosen for various locales (e.g. "de-AT")

Started investigating this when I realized that de-AT and de-CH use the wrong currency symbol for USD, US$ instead of $. The tests were passing cause they were confirming the broken selection. GetSymbol() has a bug.

Turns out the bug is in the used helper, contains():
		if i := sort.SearchStrings(a, x); i < n {
			return true
		}

This code assumes that sort.SearchStrings returns i == n when the element was not found, but that's not true. It will gladly return an i smaller than n because that's where the element would go if it was present. I see from a Google search that I'm not the first one burned by this.


Plans to port over to OpenMQTTGateway?

Makes sense since the Switchbot Bot is working on that so just curious if there are plans or if there is a technical issue to do so.

Hey. No I don't have plans to integrate with openmqttgateway. it is coded in c++, so "technically" possible, but would be a ton of work I don't have time for. Cheers


Attempt Brigadier commands

Stuff to do before merge

make configmenu work

yeah that’s about it

Actually yknow what I’m merging it now


generate: specs.Linux needed to be a pointer

[09:47:37] <papey_lap> hi, playing with ocitools but go getting github.com/opencontainers/ocitools/generate failed because of :
[09:47:47] <papey_lap> generate.go:140: cannot use specs.Linux literal (type *specs.Linux) as type specs.Linux in field value
[09:50:59] <papey_lap> oops, wrong paste : cannot use specs.Linux literal (type specs.Linux) as type *specs.Linux in field value

Reported-by: papey_lap (on IRC)
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

ah, this is because the Godeps vendored version of runtime-spec have diverged from master.

ocitools is presently on runtime-spec 1.0.0-rc1. Perhaps time to release an rc2.

Dup of #112?  I think that's just waiting on a new spec tag.

yes!


Updating contributing instructions

Updating contributing instructions regarding environment variables and testing

hey @bshaffer can you take a look? Thanks :)


theme categories don't seem populated

After the migration, it seems like the category lists aren't populated quite correctly. Might be an indexing issue.
https://addons.thunderbird.net/En-Us/thunderbird/static-themes/other/

This is actually just because the 'featured' list is empty for certain categories. The rest is correctly populated. I will remove the featured section on the category pages when I'm back on August 5th.

This is fixed.


SPM Testing dependencies were uncommented on 14.0.1

Hey, seems like someone forgot to comment out the testing dependencies from SPM before releasing the 14.0.1 version. This adds the clone of several Packages that aren't needed by the library users.
Based on this issue (that probably should be closed since it seems to have been resolved?) there is a process for commenting and uncommenting them while in development.

Any change to fix the 4.0.1?
The same here
because SwiftGen >=6.4.0 depends on Yams 4.0.0..<5.0.0 and Rocket >=0.9.2 depends on Yams 2.0.0..<3.0.0, SwiftGen is incompatible with Rocket.
And because Moya 14.0.1 depends on Rocket 1.0.0..<2.0.0 and no versions of Moya match the requirement 14.0.2..<15.0.0, SwiftGen is incompatible with Moya.
And because root depends on Moya 14.0.1..<15.0.0 and root depends on SwiftGen 6.4.0..<7.0.0, version solving failed.

As far as I know this is still a problem 😞


How to use xeditable inside ion-list?

Is this still an issue?  Is there a specific error you are getting?

@harigna are you still having an issue?

@eugef Please close due to lack of response.


I wish /docs/admin/networking/ included opencontrail as a networking option...seems to be missing

I wish /docs/admin/networking/ included opencontrail as a networking option...seems to be missing

You're welcome to file a pull request against this doc: http://kubernetes.io/docs/admin/networking/#how-to-achieve-this
I notice there's existing information here:
http://www.opencontrail.org/opencontrail-kubernetes-integration/


Uniform comparison

Add more defense, like compare Enum to String or else.

Is there any related JIRA ticket?

You are so quick, I create WW-4544 just now.


Flag torsf msmts from Android 3.8.3 as failed

Possibly related to https://github.com/ooni/probe/issues/2406

Deployed v. 0.77~pr704-118 on -test

Deployed on FSN


Dynamic imports get bundle with reactdom

I'm using the new
const DynGmp = dynamic(import('some-react-comp')) feature and by running webpack bundle analyzer I noticed that react-dom.min.js gets bundled with some-react-comp. adding import ReactDom from 'react-dom on my page component fixed it.
Am I doing something wrong? Should I always explicitly import react-dom ?

That's weird. Can I have a sample app to play with?
That'd be pretty helpful for me to find and fix this.

I've got more insight on the problems:
It occurs when a Component imports react-dom. However the precise component that is causing this problem in my app doesn't cause any in a sample project empty I made trying to reproduce

Interesting.
How many pages you've in your app?
In how many pages you are using that component?
Is it only happening with dynamic components (I mean does it happens when you directly import it and use it)?
What's the component?

I've got 9 pages and I'm using it in 3 of them, it also happens when I directly import it.
Component is https://github.com/jasonslyvia/react-lazyload.
I'm observing the same thing with https://github.com/istarkov/google-map-react

By analyzing the webpack results here https://webpack.github.io/analyse I saw that react-dom is present in the main.js chunk and in the 3 chunks using the component causing the problem.
All of these chunks have commons as parents, is it normal that react-dom isn't located in commons but in main.js ?

after disabling all the dynamics imports and investigating each commits the problem arises when I have more than 8 pages (7 pages and 1 _error.js exactly). Could this be related to a max bundle size allowed by next?
@arunoda

I'm still running into this issue, any input?

Great catch @quentin-sommer. We are on it

@quentin-sommer could you verify is this only production deployment.
In the dev mode, it's okay to be it like that because we don't properly use code splitting in that.
But in production it should work as it is.
In production I mean, next build

Hi @rauchg & @arunoda ,
Okay bare with me because this might be confusing:
I had this issue with 8 pages and 1 _error override. (so 9 pages if you count the _error.js and 10 with the default _document.js)
I added a new page, so for a grand total of 11, and it fixed my problem.
before: http://imgur.com/q3zCsjp
after: http://imgur.com/NHowLHZ
I intensively use a google-map library which directly imports react-dom, I use it in 4 pages and in the last page as well (the one that "fixed" the problem).
I'm not experienced enough with your internals or webpack ones to solve this on my own, I can give it to you the stats.json of the two builds I've screenshotted for analysis here https://webpack.github.io/analyse if it helps

@quentin-sommer What we need is a sample app. Is it possible for your wrap a demo app with this case.
So, that helps me to fix this quickly.

I couldn't manage to reproduce it. I think it has to do with some heuristics from Webpack deciding in which chunk should each module go depending on the dependency tree and the bundle size.
Since it fixed itself and is so specific I'm going to close this. Feel free to re-open or to open another issue if you still want to address this!


Fix to bugs remaining

Added notes in user guide
Fixed bugs in find command

Codecov Report

Merging #272 (6c8478f) into master (81ce131) will decrease coverage by 0.25%.
The diff coverage is 14.28%.

@@             Coverage Diff              @@
##             master     #272      +/-   ##
============================================
- Coverage     68.41%   68.15%   -0.26%
  Complexity      710      710
============================================
  Files           112      112
  Lines          2514     2525      +11
  Branches        305      308       +3
============================================
+ Hits           1720     1721       +1
- Misses          682      690       +8
- Partials        112      114       +2

Impacted Files
Coverage Δ

...a/seedu/address/logic/commands/AddItemCommand.java
88.23% <ø> (ø)

...java/seedu/address/logic/commands/FindCommand.java
75.00% <ø> (ø)

.../seedu/address/logic/parser/FindCommandParser.java
40.74% <14.28%> (-21.76%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat: add native css color-scheme to output

Description
Adds color-scheme: light / dark to the css output. This sets the styling of native controls such as scrollbars.
before:

after:

Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).

Obligatory GIF (super important!)

Nice! I missed that while adding dialtone-tokens, isn't better to add this into dialtone-generators.js? 🤔

Hmm yes good point... Updated.


add tooltip options

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.80-alpha.90787f.0@codecademy/gamut-labs@20.0.1-alpha.90787f.0@codecademy/gamut@37.5.1-alpha.90787f.0@codecademy/monaco@0.4.6-alpha.90787f.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61426d42d4fca216e2554ab6--gamut-preview.netlify.appDeploy Logs

🚀 Styleguide deploy preview ready!https://61427020c8f9821c3b9d5fbc--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.5.80-alpha.e822b9.0@codecademy/gamut-labs@20.0.1-alpha.e822b9.0@codecademy/gamut@37.5.1-alpha.e822b9.0@codecademy/monaco@0.4.6-alpha.e822b9.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://61427f33239261289e82e37b--gamut-preview.netlify.appDeploy Logs


+247 (AC) MetaData

Imported from Google Code issue #157 created by cfkoch on 2012-06-16T05:43:15.000Z:

As of ITU Bulletin 01.VI.2012 http://www.itu.int/dms_pub/itu-t/opb/sp/T-SP-OB.1005-2012-OAS-PDF-E.pdf
Ascension Island's numbering plan has changed.
See Also: http://www.itu.int/dms_pub/itu-t/oth/02/02/T02020000AF0001PDFE.pdf
This is not yet reflected in the meta-data
Phone Numbers (Non-Geographic) have been introduced.
These are 6 digits vs the national 4 digit supported.
Valid numbers have yet to be confirmed with Justin Stevens, Operations Officer, Ascencion Island Cable and Wireless.
At the very least, possibleNumber should be changed from \d{4} to \d{4}(?:\d{2})
And National to support [5890]\d{5}

All mentioned ranges have been fixed. E.g. http://libphonenumber.appspot.com/phonenumberparser?number=+247560085&country=AC


[RND-363] Migrate postman tests from ODS / API into Meadowlark

Changes:

Copying collections from ODS repo into Meadowlark.
Modify all URLs to point to Meadowlark.
Update authentication to work against Meadowlark endpoint.
Fixing body data type validation errors. (not executed for all endpoints).
Create meadowlark specific environment.

Most tests are failing from execution errors, that will be addressed in follow up tickets.

Can you rename each file with Meadowlark Ed-Fi API instead of Ed-Fi ODS/API?
Emphasizing the difference in products here, and making sure that the names don't conflict when loading both into postman at the same time.

Most of these files are not needed because Meadowlark does not support the features, and might not ever support them. Please remove:

AuthorizationTests Multiple Key/Secret - the authorization model is very different, and changing these tests to fit the Meadowlark authorization is probably not worthwhile. The .http files cover authorization very well.
AuthorizationTests - the namespace-based definitely are not needed. The other ones might be useful, but I don't think we really need them, and again they'll probably take a lot of time to fix up for use with Meadowlark.
Multiple Authorization strategy - we only have one strategy
Profile Test - profiles are not supported

Might be worth keeping:

GetByExample Tests - although will probably need a little modification, as I think the querystring will be ?studentReference.studentUniqueId=xyz instead of ?studentUniqueId=xyz.
Multiple Edorg types - I have not studied closely enough yet to understand what these are really doing. They look very interesting and we should try them out, but carefully / slowly - one scenario at a time. Probably needs to be me or Brad who looks at these because we'll have the best understanding of the relevance.
ResponseTests are mostly good. We don't support etag right now, so those are not immediately relevant. We might in the future though.
The one simply called "Ed-Fi ODS/API Integration Test Suite" has some good tests. Seems very similar to some of our .http files. Good to keep some of those, though we might want to rename the file to something more creative.
Record Ownership - this is the authorization strategy we actually use. However, the implementation is different enough that I'm not sure these tests will make any sense. Still, it will be worthwhile to look at them more closely to see if there is anything valuable to us.


Common components of different projects？

What problem does this feature solve?
Between different vue single-page projects, share one or more vue components, and generate a js file that can be publicly referenced
What does the proposed API look like?

Sounds a bit like webpack Module Federation

Sounds a bit like webpack Module Federation
It’s an extension of that function。That’s the point that the commonjs File


No single sheet option

I can't seem to choose the single sheet option anymore. The only option I've been able to create is the full journal book. The help image (step-1.webp) shows a step 5 with the single sheet popped out. I'm not sure whether the steps are missing in the documentation or whether it's a bug.
v11

@mfozz
Yes, there is no more one-page template, however you can create a book, add 2 sheets to it and it will give exactly the same effect. When you click "show", the book will open on the right page in the players.


[wrangler tail logs] Introduce installer logic for cloudflared

We need to ensure that wrangler can download the cloudflared binary if necessary; this will require adding a new set of download logic specific to equinox.io, which is where we host our cloudflared binaries.

this is blocked on cloudflared publishing binaries on a host with a stable API.

Tunnel team now publishes releases to Github: https://github.com/cloudflare/cloudflared/releases

still no macos binaries unfortunately

Won't fix: moving away from cloudflared and using WebSockets instead.


[val] Output id names along with numbers in validate_id

This CL updates the validate_id code to output the name of the object along with
the id number. There were a few instances which already output the name, this
just extends to all of them. Now, the output should say 123[obj] instead of just
123.
Issue #1581

For the example in 1581, this would output:
error: 2856: OpStore Pointer <id> '137[obj]' is not a logical pointer.

The travis failure is due to formatting differences, probably because I ran clang-format on mac and it did some changes the linux version doesn't like.

Reformatted the test file by hand, the clang-format on my Linux machine also doesn't match what Travis expects?

Seems like formatting is under control now?
As for AppVeyor, could be the cloud weather.  I recommend doing commit --amend and force pushing onto your branch again to trigger a rebuild.


Preserve repoName:tag when building, importing and loading images

Do not qualify repository names with default registry while performing
one of the mentioned operations. So instead of:
$ docker -t myrepository .
$ docker images | grep myrepository
my.additional.registry:5000/myrepository   latest  2e11d8fd18b3

The result will be:
$ docker images | grep myrepository
myrepository   latest  2e11d8fd18b3

Signed-off-by: Michal Minar<EMAIL_ADDRESS>

$ docker -t myrepository .
Is this supposed to be
$ docker build -t myrepository .
Do we need tests units for this?

Argh, yes, build is missing there.
Integration-cli tests cover the changes but unit tests would be nice to have as well. I can add some once I finish PR for this.

FWIW: docker autotest also covers this already.


feat: 🚀 Supprted monorepo

Description
Supports monorepo format projects.
✅Closes: #142
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

🎉 This pull request is included in version v1.6.0.


Update accesspolicies.md: fixed grammar issues

Fixed grammar issues in the accesspolicies.md documentation file.

Looks good. If you adjust the target branch to 8.x, it would get into an OC release sooner.

If this applies to 7.x (or even 6.x) feel free to go back that far too.  The documentation gets rebuilt even without a release, so the further back the better.

@smarquard, will you take the official review for this patch?

@smarquard, please don't merge pull requests with failing tests. I've fixed the issue on develop but this directly caused #1133 to fail as well.

Sorry, I assumed the failure was from one of the many other failure-inducing issues in develop recently. Maybe time to change the github config to require a passing CI test before merge is allowed?


[FLINK-26991][docs] Limits docs build to main repo

Also limits nightly build only to relevant branches. Should be merged to release-0.1 too.

Please backport it to release-0.1 @mbalassi


Initial Commit

Könntest du einen eigenen Branch machen? Vielen Dank.

Merged into branch benjamin. If you can, remove the license since the code you wrote is not copyrighted by yourself but by the concern.

I created a pull request without the license.

I gave you write permissions. In the future you can push directly without a PR

Ok Thanks.
I'm a bit confused about the two readmes in my branch. Are they different?

-------- Original Message --------
Subject: Re: [kanton-aargau/project-grow] Initial Commit (#3)
Local Time: 3. Oktober 2017 9:17 AM
UTC Time: 3. Oktober 2017 07:17
From<EMAIL_ADDRESS>To: kanton-aargau/project-grow<EMAIL_ADDRESS>Apply55gx<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>I gave you write permissions. In the future you can push directly without a PR
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hmm they are both the same. Merge issue. You can delete one if you want


Laravel 11.x Compatibility

This is an automated pull request from Shift to update your package code and dependencies to be compatible with Laravel 11.x.
Before merging, you need to:

Checkout the l11-compatibility branch
Review all comments for additional changes
Thoroughly test your package

If you do find an issue, please report it by commenting on this PR to help improve future automation.

:warning: The latest version of Laravel has a dependency for phpunit/phpunit of ^10.5. If you would like to also upgrade your tests, you may run the PHPUnit 10 Shift for free.

:warning: Shift detected GitHub Actions which run jobs using a version matrix. Shift attempted to update your configuration for Laravel 11. However, you should review these changes to ensure the desired combination of versions are built for your package.

:alembic: Using this package? If you would like to help test these changes or believe them to be compatible, you may update your project to reference this branch.
To do so, temporarily add Shift's fork to the repositories property of your composer.json:
{
    "repositories": [
        {
            "type": "vcs",
            "url": "https://github.com/laravel-shift/phpunit-query-count-assertions.git"
        }
    ]
}

Then update your dependency constraint to reference this branch:
{
    "require": {
        "mattiasgeniar/phpunit-query-count-assertions": "dev-l11-compatibility",
    }
}

Finally, run: composer update


Write to a temporary directory rather than user's home directory

I run the Bioconductor builds and noticed tripr is writing to the user's home directory on both devel and release during R CMD check. This isn't allowed (see BioC Packages - Other Data). We recommend that it instead write to a temporary directory using BiocFileCache or R's default caching directory tools::R_user_dir("tripr", which="cache").
On the Linux builder, I see the following, which I've truncated:
biocbuild@nebbiolo1:~$ tree Documents
Documents
└── my_output
    ├── output_124745
    │   ├── Analysis
    │   │   ├── clonotypes_bar_plot_with_threshold0.1.png
    │   │   ├── hist3D-nucleotides_top_20clonotypes__BcellA_BcellB.png
    │   │   ├── image2D-nucleotides_top_20clonotypes__BcellA_BcellB.png
    │   │   └── persp3D-nucleotides_top_20clonotypes__BcellA_BcellB.png
    │   └── output_tables
    │       ├── Clonotypes_Summary.V.GENE+Summary.AA.JUNCTIONAll_Data.txt
    │       ├── Clonotypes_Summary.V.GENE+Summary.AA.JUNCTION_BcellA.txt
    │       ├── Clonotypes_Summary.V.GENE+Summary.AA.JUNCTION_BcellB.txt
    │       ├── filterin_clono_All_Data.txt
    │       ├── filterin_clono_BcellA.txt
    │       └── filterin_clono_BcellB.txt

We appreciate your attention to this matter as well as your contribution to Bioconductor.

Dear @jwokaty,
Thank you for raising this issue. We are currently looking into it and we plan to have an updated version within the next ~10 days.
With kind regards,
Aspa

Hi @jwokaty,
In its current version, tripr allows the user to save all datasets that are produced by its functionalities into an output directory, or to save specific tables that she/he chooses.
At the moment we are working to optimize the package and make it more robust. During the workflow of the package a lot of useful outputs are being produced and therefore it would be necessary for a user to have all generated outputs into the working directory (Analysis and output_tables from your example above).
Looking forward to your feedback. Thank you in advance for your time.
With regards,
Aspa

Hi @aspaor,
The examples and code in the vignettes should save to a temporary directory when not run interactively--e.g., R CMD check--so it doesn't pollute the current working directory. So I would set the default output path to the temporary directory and make it clear that the user should set the output path for persistence.

Dear @jwokaty ,
Thank you for your comment. We are planning to do some modifications to the output storage part as you suggested. Thank you again for your help.
All the best,
Aspa


feat: Onboarding demo interface - frontend

add pages of onboarding

Great job @dezhizhang1985
now we have to move to POST and GET methods and form validation in onboarding_registration.html if you agree

@dezhizhang1985 I wonder that I should separate onboarding demo app from trust-anchor-intermediary app.
Because someone must be able to use the trust-anchor-intermediary feature without take also the onboarding demo.
Tomorrow I'll do a refactor, after I'll merge this

here
https://github.com/peppelinux/spid-cie-oidc-django/issues/18


Using an attribute to define a report gives issues

eg.
DEFINE PRINTER (CC)  ...
WRITE (CC) NOTITLE 'x'
etc.
This fails because CC is also an attribute.

There needs to be a special parsing for report specification.
These are all the statements that can have rep: https://documentation.softwareag.com/natural/nat921unx/webhelp/natux-webhelp/pg/pg_output_rep.htm#rep_statements


VRTK_InteractableObject and GrabOverrideButton

I was debugging an issue with picking up any interactable objects when I moving fro 2.x to 3.x
It would appear that setting "GrabOverrideButton" to "Grip_Click" (instead of undefined) stops the grab from working with the Grip's click but only if the SecondaryGrabActionScript is null in the editor (this is what how I figured out how to reproduce it in example 005)
For some reason the upgrade set all my interactable objects to this (instead of undefined which iirc they were originally)
From what I can see the grip "click" is not getting into the interactable object.
If you need any further information let me know!

The reason your overrides were updated was because the button enum positions changed.
Are you saying grip click doesn't work? I think grip click only works on analogue grips like on the oculus touch. I wonder if steam vr supports an axis for grip now.

I didn't realise that "grip_clip" wasn't available on the Vive's, I had just assumed it fired when the grip button was clicked; this is what probably threw me off the longest (given it looked like it should be correct)..
Happy to close this if you feel that answers the issue :)

Yeah I can see why it's not working now.
In ControllerEvents, the click events (Trigger/Grip) are thrown when the button axis reaches it's threshold (e.g. 1f)
But SteamVR SDK Bridge always reports the Grip axis threshold as 0 which is why Grip click doesn't work for SteamVR.
Although I need to look into this further, because if SteamVR doesn't have an axis for the grip button (which may well be the case) then the Oculus touch grip axis isn't going to work on SteamVR either.

It would seem that SteamVR has 5 axis on the controller but all relate to the trigger or touchpad (?!)
So it seems there is no grip axis on SteamVR meaning Grip click would be unsupported.
https://github.com/ValveSoftware/steamvr_unity_plugin/blob/master/Assets/SteamVR/Scripts/SteamVR_Controller.cs#L23-L27
https://steamcommunity.com/app/358720/discussions/0/487876568226759993/


To link a json file to treeview automatically?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello @NanyangTaiji , Sorry for delay, but the issue has no description, if you want to map json to treeview there is already a sample and article describing how to do that
Thank you


⚠ Bofrost.be has degraded performance

In c1fe09e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1817 ms

Resolved: Bofrost.be performance has improved in c48cecd after 1 hour, 17 minutes.


terragrunt: fix typo

In my earlier PR #21901, I had pushed the wrong local branch without a '$'.
Apologies @Mic92 - please apply.
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

oh. I just test the binary, because I have not terraform setup at the moment.


Fix: Upgrading terraform bridge to 3.39.1

@kpitzen @iwahbe is this a docstring bug? https://github.com/pulumi/pulumi-aws/pull/2347/files#diff-143888737f1085bef2bd2b9c1dc0904a5bb8f20988cac636f73839ecf9de19f5L84

superceded by #2366


Nice web-based solution

I tried the angular 17 version but [scale] in directive mode does not work. The dot scale remains the same regardless of number entered.
Browser: Google Chrome 129.x
<qrcode [qrdata]="'Your data string'" [width]="256" [scale]="1" [errorCorrectionLevel]="'M'">
Any guidance is greatly appreciated.
Thanks,
Dean
https://tapple.io

Hi @professor-rage
The scale factor works when the width is set to 10 (default)
<qrcode
[qrdata]="'https://github.com/Cordobo/angularx-qrcode'"
[allowEmptyString]="true"
[ariaLabel]="'QR Code image with the following content...'"
[cssClass]="'center'"
[colorDark]="'#000000ff'"
[colorLight]="'#ffffffff'"
[elementType]="'canvas'"
[errorCorrectionLevel]="'M'"
[imageSrc]="'./assets/angular-logo.png'"
[imageHeight]="75"
[imageWidth]="75"
[scale]="32"
[title]="'A custom title attribute'"
[width]="10"

You can play around with the values here
https://cordobo.github.io/angularx-qrcode/

Perfect. Thank you.


No services installed

Hi, I've used cf_nise_installer to install Cloud Foundry V2 to Ubuntu Server 10.04. It was really cool and smooth experience,I've got my Controller running and was able to connect using CF tool. (There were no default spaces/domains installed so I had to create some to deploy simple node.js app - hope this is not an issue).
But when I've decided to run some services, I didn't found any of them. Running cf gave following

cf create-service
DL is deprecated, please use Fiddle
Cannot find services matching the given criteria.

So I suppose there were no services installed. According to README I had to run  register_service_tokens.sh script to install those, but I could not find it in source (browsing the commit history showed that it was deleted).
So what can I do to have any service provisioned? And also it seems README file needs some updates.

Hi,
I am using this environment in local, running a Node.js app. My idea is to add a MySQL Service but if I execute cf m I didn't see any service.
How to add the Service to use mysql?
https://github.com/cloudfoundry/cf-mysql-broker
Many thanks in advance.
Juan Antonio

To add a new service broker, you need to modify the manifest file in this project. I highly recommend you use BOSH to deploy complicated environments like this. Try bosh-lite.


Handle orphan core services case

If d-mon service crashes orphan cores service processes are still bound to port 5001.
This makes redeployment impossible on port 5001. Need to handle this situation.
a) In case d-mon dies kill orphan proceses
b) Try to reattach processes to new d-mon process.

Merged with #34.


Windows support & more cleanup

introduces io/windows.zig and windows impls across fs + time
moves fs bits from storage.zig into the platform io implementations
assumes direct io is always supported for Storage files on darwin & windows (not linux)
adds benchmark.bat script for easy launching for windows users
removes IO.fsync as its unused (only in tests)

I wish GitHub had a "muscle" emoji for when someone opens a PR with 55 commits in the bag, ah wait... 💪


Only for ASP.NET Core projects ?

Will this feature be available for "non-ASP.NET Core" projects ?

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

ID: 2d25dd44-f173-dd83-3afc-d6608613d450
Version Independent ID: e121cedc-5cbe-a399-e2a8-5d192aaea770
Content: File nesting rules for Solution Explorer - Visual Studio
Content Source: docs/ide/file-nesting-solution-explorer.md
Product: visual-studio-dev15
GitHub Login: @AngelosP
Microsoft Alias: angelpe

Is there a provider that will mimic folders ? I want to be able to create a structure in controllers folder - just like I would create folders.

@AngelosP Angelos, can you comment on this?

Hello! There are currently no plans to invest in this feature. There are no plans to add support for other project types. There is also no plan to make it work for folders.

"There are no plans to add support for other project types"
Can you please explain WHY there are no such plans? It seems that this would be something that'd be VERY useful for just about ALL project types. There's an extension to do this already so  why can't it be built into Visual Studio itself?


use existing julia install

I am trying to install Julia + some packages in a a docker image, and run it in python with juliacall
there seems to be quite a lot of magic going on with automatically creating new environments, downloading packages, etc. etc.
I don't want any of that. is there a way to ask juliacall to "just please use this julia environment" and go ahead and fail if there are any version incompatibilities etc. ?

Yep, check out the docs for juliapkg, which handles all that installation: https://github.com/JuliaPy/pyjuliapkg


Year is not available in datetime mode

Year is not available in datetime mode.
Is there any way to add year in datetime mode selection?

Any solution ?

@rohit-simplecrm did you find any way to enable Year for datetime mode ?


inline, vendor, client bundle script tags are not getting in page source for universal CLI app

Versions.
universal-cli: 1.0.0-alpha.universal.3
angular-cli: 1.0.0-beta.23
node: 7.5.0
os: win32 x64

server.routes.ts
export const routes: string[] = [
'*'
];
app.routes.ts
export const appRoutes: Routes = [
{ path: 'contact', component: ContactComponent },
{ path: '',   component: HomeComponent },
{ path: '**', component: PageNotFoundComponent }
];
contact.component.html

			<form #f="ngForm" (ngSubmit)="addTodo()">
			<input name="newTodo" [(ngModel)]="newValue">
			<button>Submit</button>
contact.component.ts
export class ContactComponent implements OnInit {
newValue: string = "";
constructor() { }
ngOnInit() {
}
addTodo(){
console.log(this.newValue)
}
}
index.html

			<!doctype html>
			<html>

			</html>
contact.component.html

			<head>
			    <meta charset="utf-8">
			    <title>{{ globals.metaTitle }}</title>
			    <meta name=”description” content="{{ globals.metaDescription }}" />
			    <meta name=”keywords” content="{{ globals.metaKeywords }} " />
			    <base href="/">
			    <meta name="viewport" content="width=device-width, initial-scale=1">
			    <link rel="icon" type="image/x-icon" href="favicon.ico">
			    <script src="http://localhost:35729/livereload.js?snipver=1"></script>
			</head>
			<body>
			    <router-outlet></router-outlet>
			</body>
app.component.ts
import { Component } from '@angular/core';
import { AppServiceService } from './services/app-service.service';
@Component({
selector: 'html',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css'],
providers: [AppServiceService]
})
export class AppComponent {
constructor(private globals: AppServiceService){
}
}
app-service.service.ts
export class AppServiceService {
metaTitle = 'This is the Title';
metaDescription = 'This is the Dis';
metaKeywords = 'This is the Keys';
constructor() { }
}
Page sorece

<!DOCTYPE html><html _nghost-0=""><head _ngcontent-0="">
	<meta _ngcontent-0="" charset="utf-8">
	<title _ngcontent-0="">This is the Title</title>
	<meta _ngcontent-0="" name="”description”" ng-reflect-content="This is the Dis" content="This is the Dis">
	<meta _ngcontent-0="" name="”keywords”" ng-reflect-content="This is the Keys " content="This is the Keys ">
	<base _ngcontent-0="" href="/">
	<meta _ngcontent-0="" content="width=device-width, initial-scale=1" name="viewport">
	<link _ngcontent-0="" href="favicon.ico" rel="icon" type="image/x-icon">

</head>
<body _ngcontent-0="">
	<router-outlet _ngcontent-0=""></router-outlet><app-contact _nghost-4=""><p _ngcontent-4="">
  contact works!
</p>
<div _ngcontent-4="">
<h1 _ngcontent-4="">Add Todo</h1>
<form _ngcontent-4="" class="ng-untouched ng-pristine ng-valid">
<input _ngcontent-4="" name="newTodo" ng-reflect-name="newTodo" class="ng-untouched ng-pristine ng-valid" value="">
<button _ngcontent-4="">Submit</button>
</form>
</div>
</app-contact>
</body>
</html>
Issue.
addTodo() function is not responding while submit the form in contact page
After submitting the form, values are displaying in the URL as below
http://localhost:4200/contact?newTodo=Test
Below scripts tags are not displaying in page source

			<script type="text/javascript" src="inline.bundle.js"></script>
			<script type="text/javascript" src="vendor.bundle.js"></script>
			<script type="text/javascript" src="client.bundle.js"></script>
Please resolve this issue

Hi Team,
I have Singed the CLA and my Git Hub Username is "BattiniSantthosh"
Regards,
Santhosh B
On Tue, Apr 18, 2017 at 5:11 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/pull/5996#issuecomment-294799934,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXjXmc7f3b1F1DFwPKFShKoYeedEoXVUks5rxKF7gaJpZM4NAOnO
.

This PR should go against the universal-cli repo... https://github.com/devcrossnet/universal-cli


elasticsearch index: expand update_or_remove method

Currently the elasticsearch index is only updated if a profile is updated.
What is missing: if a tag is updated (as we do sometimes as an admin) the index is not updated and the profile is not found with the changed tag even though the profile is connected with this tag.

https://github.com/elastic/elasticsearch-rails/issues/306

not needed anymore


WikidataAPITest requires Internet connection

The way the WikidataAPITest test suite is implemented requires an active Internet connection.  This should rather be stubbed, and maybe only a few tests testing actual connectivity.

Addressed in commit 9c4c4e8


wanted: meekrosoft/fff

Module location
https://github.com/meekrosoft/fff
Link to bzlmod issue in the module's repository
No response
Any other context to provide?
No response
Fund our work

[ ] Sponsor our community's open source work by donating a feature bounty

any update on this?


Add warning message in case that a test folder is present in the package

Codecov Report

Merging #280 (d32332a) into main (9c3242e) will decrease coverage by 1.56%.
The diff coverage is 91.11%.

@@            Coverage Diff             @@
##             main     #280      +/-   ##
==========================================
- Coverage   91.30%   89.74%   -1.57%
==========================================
  Files          17       16       -1
  Lines        1576     1433     -143
==========================================
- Hits         1439     1286     -153
- Misses        137      147      +10

Flag
Coverage Δ

unittests
89.74% <91.11%> (-1.57%)
:arrow_down:

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

Impacted Files
Coverage Δ

setup.py
0.00% <0.00%> (ø)

grayskull/license/discovery.py
95.62% <44.44%> (-1.52%)
:arrow_down:

grayskull/base/github.py
60.37% <60.37%> (ø)

grayskull/__main__.py
90.00% <78.78%> (-8.15%)
:arrow_down:

grayskull/strategy/abstract_strategy.py
83.33% <83.33%> (ø)

grayskull/utils.py
89.54% <85.84%> (-10.46%)
:arrow_down:

grayskull/base/pkg_info.py
85.71% <87.50%> (+0.52%)
:arrow_up:

grayskull/strategy/py_base.py
94.72% <94.72%> (ø)

grayskull/base/factory.py
93.54% <96.29%> (+3.54%)
:arrow_up:

grayskull/config.py
98.07% <98.07%> (ø)

... and 7 more

Continue to review full report at Codecov.

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


Add css from 7 more legacy subreddits

cyzon recreated css for some subsreddits that we've lost over time

cyzon realized there is a potential bug in this css. I'll update this and take it out of draft mode once I get updated data.

Okay. A bit of back and forth but it looks like the bug didn't impact any of the subs here and one of the ones here (trixquisition) is actually the original css and retains the special effects (i.e. hover) on some of the emotes. So we're good with the original change.


log store recovery issue

https://github.com/eBay/HomeObject/actions/runs/8998757900/job/24719513446?pr=173

#413


Except block in incubator.rest catches all exceptions

https://github.com/checkmate/simpl/blob/master/simpl/incubator/rest.py#L189-L190
This generic exception swallows any exceptions I raise in my wrapped route:
import myexchandler as exc

@bottle.post('/myroute')
@rest.schema(body_schema=MYSCHEMA, body_required=True,
                        default_body={})
def some_route(body, query):
  raise exc.HTTPError(body="I'M A TEAPOT!", status=418)

I would expect this to raise a 418 error. However, it will always raise a 400 because the error raised here is caught by the except in the wrapper and then a bottle.abort(400...) is called.
Is this try/except block needed? Can it be taken out or narrowed down?

Meant to ping @larsbutler as I think you probably have the most perspective on what was going on there.

@larsbutler @samstav @ziadsawalha  - I think there is a use case for the incubator validation code in some of the work @Pablosan is doing, but this issue could stand in the way. Any thoughts on a solution? In order to get this working the way I would expect it to, I just removed the whole try/except block (https://github.com/ryandub/simpl/commit/5bce9d8bacdc2146854f828e28a62c74e94ecf85), but I think that has its own implications.
Is there an ideal solution here?

@larsbutler @ryandub @ziadsawalha
I think we should just change the
except Exception as exc:

to
except MultiValidationError as exc:

@samstav What if it isn't valid JSON? Should https://github.com/checkmate/simpl/blob/master/simpl/incubator/rest.py#L160 be wrapped as well?

@ryandub good question.... Would that raise a ValueError ?

@samstav @ryandub I think we could solve this in the incubator code by following the approach here: https://github.com/checkmate/simpl/blob/master/simpl/rest.py#L39
Specifically, this moves the catch-all so that it only catches on a single line (the line that validates against the schema)
However, I am pretty sure that a call to bottle.request.json can result in an exception, so we should probably address that in both locations (rest.body and incubator.rest.schema).
Finally, why is this schema function only in incubator? It seems awfully close to what is already in simpl.rest.body, and we could get both in sync if we moved schema into simpl.rest and created a helper function that both of these functions (body and schema) could use.

Actually, it should be two helper functions: one that validates a JSON payload, and one that validates Query Params. Then they could be used independently if desired. For instance, body probably shouldn't have Query Param validation.

I am pretty sure that a call to bottle.request.json can result in an exception

Correct, it can.
I agree that these helper(s) must be consolidated. I can appreciate both approaches, that is, having one decorator called schema, or two, one called body() and one called query(). Actually, my suggestion would be that we have all three, and the developer can choose which they want to use, where schema would just delegate out to the logic behind body() and query().
Also, if schema sticks around, its implementation should change. The keyword arguments that are not supplied to the decorator should not be forwarded to the decorated function. For example, iff body= is supplied to  the decorator then only the body kwarg should be passed to the decorated function. In other words, the signature of the decorated function should only need to change for the arguments it actually uses instead of hard-coding the line that passes query and body to the decorated function. The logic in the decorator should be smart enough to detect this.

And lastly we should always keep the try/except blocks as small as possible and the exceptions caught as specific as possible.


<IP_ADDRESS>_Ternary_search.md

Description 📜
Fixes #3698

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[x] DSA
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] Java#Script
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@Sarthak-Agg sir,please review it

Hi! @Sarthak-Agg  I would love to work on this issue? can you please assign it to me?😊
Name: Priyanshi Saxena
Batch: 8
Contribution type: Audio

@Sarthak-Agg  please review

@101Priyanshi  add the audio contribution you are referring to.


Merge STR: More than one value found for END

Im trying to merge around 3 files of GangSTR output into one mergefile. while doing it, Im facing an issue of

More than one value found for END

it ran for 89k lines and it stopped after this line
(bharath) []$ tail -1 test.vcf.vcf
chr10   17809113        .       CCTCCCCTCCCCTCCCCTCCCCTCC       .       .       .       END=17809163;PERIOD=5;RU=cctcc;REF=5.0;STUTTERUP=0.05;STUTTERDOWN=0.05;STUTTERP=0.9;EXPTHRESH=-1 GT:DP:Q:REPCN:REPCI:RC:ML:INS:STDERR:ENCLREADS:FLNKREADS:QEXP   0/0:49:1.0:5,5:5-5,5-5:29,20,0,0:286.292:419.097,96.3636:0.0,0.0:5,29:NULL:-1.0,-1.0,-1.0        0/0:28:0.999683:5,5:5-5,5-5:16,12,0,0:167.282:416.998,95.8552:0.0,0.0:5,16:NULL:-1.0,-1.0,-1.0   0/0:42:1.0:5,5:5-5,5-5:25,17,0,0:251.281:415.347,94.2128:0.0,0.0:5,25:NULL:-1.0,-1.0,-1.0

I couldn't able to figure out the error from the vcf files .  the following lines are the next lines in each file, I have found out that multiple END values are given for the same location. but how do i resolve this issue?
(bharath) []$ zcat *.vcf.gz | grep -w "17813632"
chr10   17813632        .       TATA    .       .       .       END=17813701;EXPTHRESH=-1;GRID=1,5;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05     GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   0/0:27:0.970717:2,2:2-2,2-2:8,19,0,0:2,8:NULL:187.217:415.347,94.2128:0,0:-1,-1,-1
chr10   17813632        .       TATA    .       .       .       END=17813703;EXPTHRESH=-1;GRID=1,5;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05     GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   0/0:27:0.962654:2,2:2-2,2-2:8,19,0,0:2,8:NULL:187.622:415.347,94.2128:0,0:-1,-1,-1
chr10   17813632        .       TATA    .       .       .       END=17813703;EXPTHRESH=-1;GRID=1,5;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05     GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   0/0:20:0.315071:2,2:1-3,1-3:2,18,0,0:2,2:NULL:160.457:416.998,95.8552:0.466294,0.466294:-1,-1,-1
chr10   17813632        .       TATA    TATATA  .       .       END=17813701;EXPTHRESH=-1;GRID=1,6;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05     GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   0/1:24:0.33128:2,3:2-3,2-6:2,19,0,3:2,2:2,2|3,1:194.26:416.998,95.8552:0.500759,0.76488:-1,-1,-1
chr10   17813632        .       TATA    .       .       .       END=17813701;EXPTHRESH=-1;GRID=1,103;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05   GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   0/0:14:0.00196308:2,2:1-23,1-23:0,14,0,0:NULL:NULL:115.062:419.097,96.3636:7.19692,7.19692:-1,-1,-1
chr10   17813632        .       TATA    TATATA  .       .       END=17813703;EXPTHRESH=-1;GRID=1,103;PERIOD=2;REF=2;RU=ta;STUTTERDOWN=0.05;STUTTERP=0.9;STUTTERUP=0.05   GT:DP:Q:REPCN:REPCI:RC:ENCLREADS:FLNKREADS:ML:INS:STDERR:QEXP   1/1:14:0.00181527:3,3:1-24,1-24:0,14,0,0:NULL:NULL:115.131:419.097,96.3636:6.13539,6.13539:-1,-1,-1

On the line merging stopped at, looking at the POS and length of the REF allele you would conclude that the coordinate of the last base pair of the REF allele is "17809137". But the given END info field is "17809163". I assume it's erroring out because those don't match. I would look to see which of the POS/REF/END fields was incorrectly set upstream.


Sample Code Snippet updated in ReadMe

This way solved "showModal is undefined function" error.

Bingo, makes sense, thanks @frknbasaran and @hackzilla


Enabling PWM support for STM32 L152RE Platform

Enabled PWM support for STM32 L152RE target platform.
Verified PWM signals on timer3 using test application tests/drivers/pwm

The compilation error in the drivers/pwm/pwm_stm32.c :
It seems the stm32L1 soc series does not support the break function on any of its timer, so should the pwm_stm32.c include a flag on CONFIG_SOC_SERIES_STM32L1X in the pwm_stm32_init function:
#ifndef CONFIG_SOC_SERIES_STM32L0X
	/* enable outputs and counter */
	if (IS_TIM_BREAK_INSTANCE(cfg->timer)) {
		LL_TIM_EnableAllOutputs(cfg->timer);
	}
#endif


Timoshenko beam theory

https://github.com/ross-rotordynamics/ross/blob/master/paper/paper.md#L60-L63
no citation for Timoshenko beam theory ?
cc https://github.com/openjournals/joss-reviews/issues/2120

We have added the Hutchinson (2001) reference, which explains the Timoshenko beam theory.

fixed in https://github.com/ross-rotordynamics/ross/pull/504


Support Smart Touch Wifi Filter Pump

Hi! I can successfully onboard with my Bestway app credentials, but it looks like the integration is only for SPAs and not Bestway products in general, because I can't see the pump device I see in my app screen.
Is it the integration or the Bestway Cloud API doesn't expose anything else than SPAs?

I don't own any other Bestway products besides a Lay-Z-Spa, and the API is undocumented, so someone would need to do the reverse engineering to see how the Bestway product range works. If anyone can do some initial investigations and post back here I'd welcome a discussion on where to take it next.
At present, the integration is certainly not designed to cope with anything but spa systems, and even then newer spa products seem to be coming out that communicate in different ways.

I’ll do some reversing on my product and let you know!
On Sun, 11 Jun 2023 at 23:20 cdpuk @.***> wrote:

I don't own any other Bestway products besides a Lay-Z-Spa, and the API is
undocumented, so someone would need to do the reverse engineering to see
how the Bestway product range works. If anyone can do some initial
investigations and post back here I'd welcome a discussion on where to take
it next.
At present, the integration is certainly not designed to cope with
anything but spa systems, and even then newer spa products seem to be
coming out that communicate in different ways.
—
Reply to this email directly, view it on GitHub
https://github.com/cdpuk/ha-bestway/issues/23#issuecomment-1586341949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABPCNBZKLNDC524QWXX64TXKYZADANCNFSM6AAAAAAZCSCO6U
.
You are receiving this because you authored the thread.Message ID:
@.***>

I tested the above with this device and I'm able to power it ON/OFF and set filter timeout in hours. I also added status report when the device reports that a filter change is required.
https://bestwayusa.com/flowclear-smart-touch-wifi-2-000-gal-app-controlled-filter-pump-58614e

@phretor Please could you try this branch?
https://github.com/cdpuk/ha-bestway/tree/generic-bestway
This is a significant rewrite to make it easier to support a range of devices beyond Airjet spas, and may become v2.0.0 of the integration. As I have no way to test with a pump, your help would be much appreciated.

On it!