Map freeze after pushing view, since certain commit

I'm submitting a ...  (check one with "x")

[ ] question
[x] any problem or bug report
[ ] feature request

If you choose 'problem or bug report', please select OS:  (check one with "x")

[x] Android
[x] iOS

cordova information:  (run $> cordova plugin list)
branch-cordova-sdk 2.6.17 "branch-cordova-sdk"
com.googlemaps.ios 2.6.0 "Google Maps SDK for iOS"
cordova-open-native-settings 1.4.1 "Native settings"
cordova-plugin-advanced-http 1.11.0 "Advanced HTTP plugin"
cordova-plugin-ble-central 1.1.4 "BLE"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-device 2.0.2 "Device"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-googlemaps 2.3.2-beta-20180515-1309 "cordova-plugin-googlemaps"
cordova-plugin-inappbrowser 3.0.0 "InAppBrowser"
cordova-plugin-insomnia 4.3.0 "Insomnia (prevent screen sleep)"
cordova-plugin-ionic-webview 1.1.16 "cordova-plugin-ionic-webview"
cordova-plugin-ios-non-exempt-encryption 1.0.0 "ITSAppUsesNonExemptEncryption false"
cordova-plugin-network-information 1.3.4 "Network Information"
cordova-plugin-qrscanner 2.5.0 "QRScanner"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.2 "StatusBar"
cordova-plugin-swift-support 3.1.1 "SwiftSupport"
cordova-plugin-whitelist 1.3.3 "Whitelist"
ionic-plugin-keyboard 2.2.1 "Keyboard"

"@ionic-native/core": "4.7.0",
"@ionic-native/google-maps": "^4.8.2",

Current behavior:
Since commit https://github.com/mapsplugin/cordova-plugin-googlemaps/commit/0dbe65d6a92fcbf1bca9793d7238b507dc802729 the map is frozen after new view is pushed into NavController (map.setDiv(null) is called in ionViewWillLeave and map.setDiv(mapDiv) is called on onViewWillEnter) and pushed view is dismissed.
On Android - map is frozen on new view closed
On iOS - map is blank on new view closed
No error in console is provided.
With previous commint https://github.com/mapsplugin/cordova-plugin-googlemaps/commit/d783ff0d95b802250ac57c5c86cc09a0447bc706 is no problem.

I also experience this issue. What I did temporarily is use modal instead of push.

It is the same repository as I shared to you in https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/2252

Try the multiple_maps branch code
$> cordova plugin rm cordova-plugin-googlemaps

$> cordova plugin add https://github.com/mapsplugin/cordova-plugin-googlemaps#multiple_maps --variable ...

$> cordova plugin list
cordova-plugin-googlemaps 2.3.4-beta-20180517-1004 "cordova-plugin-googlemaps"

The patch is applied to master, not multiple_branch.
Anyway,
iOS: map is not blank after returning to map, but is frozen
Android: map is blank after returning to map, not frozen
So: the behaviour is swapped.

No, my repository is https://github.com/homeportcz/freebike

Oh, I didn't notice your invitation.

Ok, is there any problem?

My fault, setClickable has been called on ionViewWillEnter() not ionViewDidEnter().
I can confirm the bug is fixed. Thanks.


Not running on GPU even though the GPU memory has been taken up.

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 375.66                 Driver Version: 375.66                    |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla P100-PCIE...  Off  | 0000:08:00.0     Off |                    0 |
| N/A   29C    P0    30W / 250W |  15649MiB / 16276MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla P100-PCIE...  Off  | 0000:0B:00.0     Off |                    0 |
| N/A   30C    P0    30W / 250W |  15477MiB / 16276MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                       GPU Memory |
|  GPU       PID  Type  Process name                               Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+
The GPU is not actually working. just taking up all memory of GPU.

Are you solve this problem? The GPU is not work for calculate but only spend memory

Use "watch -n 1 nvidia-smi"  to find out which process take up your GPU memory then enter "sudo kill -9 PID" to stop it

did you manage to solve this? I am facing the same problem.

i have meet the same question,anyone is solve the problem?


Incompatibility with labymod 4

Hey,
As this is related to labymod 4 it might not be able to be fixed by you / might have to be fixed by laby. But if it could be would be much appreciated.
https://paste.labymod.net/ojowewegiv

This crash is very strange. Long story short, I don't think I'll be able to fix this, especially without any experience with Labymod. I didn't find a Github, and it appears that the Labymod website has a special way to report bugs. I don't know if there is a special system for beta testers of 4, since it doesn't appear to be released yet. You might be interested in sending them a link to this issue, though I'm guessing it would be very difficult to fix on their end too, especially considering they're trying to load Forge and Fabric mods at the same time. Here are the details:
The error that is spammed in the log refers to the enchantment display feature. It appears that the config value for how to display enchantments isn't loaded. Looking further down, it seems there is a second exception, which occurs before the config is loaded, causing this issue. It seems like Labymod should have crashed at this point, rather than continuing while the NBT Editor mod is in a "corrupted" state. (Can you specify when the game crashed?) It is possible that it attempted to continue loading without the NBT Editor mod, but forgot to undo the mixins (if that is even possible).
The exception that I identified as the source of the issue seems to indicate that class org.joml.Matrix4f doesn't exist. This doesn't make sense, since Minecraft 1.19.4 is supposed to have switched to this Matrix library. This difference in expectation vs reality throws an exception.
There is also another exception on line 352 of the log. Did you attempt to open NBT Editor's config menu? This issue would also be caused by the Matrix4f exception.
Finally, the stacktrace seems to be using fully obfuscated class names. I don't know if Labymod has a special way to make it work, but due to the remap = false in several of my mixins and how I assume intermediary mappings in a lot of my code, I wouldn't be surprised if there were lots of other issues relating to this as well.

It crashes as soon as you open your inv.
Also /nbt says unknown command the error that occurs.
Yea, I assume it is 100% laby related and only they will be able to fix it. Fabric support is experimental atm was just taking a shot in the dark just incase. Thank you

I still have issues with Labymod, when i join a server or world its just stuck in the loading screen on Joining World making this mod unusable with Laby :/

This issue wasn't ever fixed, as it would be extremely complicated - in other words, I don't support Labymod


Rewarded Videos and InMobi

InMobi does offers rewarded videos, and the plugin does offers integration with InMobi by installing the cordova-inmobi-sdk. Does this means that I can use rewarded videos from InMobi? Any way, I am trying, but I am having an error: "Attempt to invoke virtual method 'int org.json.JSONObject.length()' on a null object reference".
I already configurated the mediation in AdMob.

Have you installed both cordova-inmobi-sdk and cordova-plugin-admob-inmobi? You need to install the InMobi SDK as well as the mediation adapter.

@johnborges, I have both those plugins installed. And my code is:
      videoReward = () ->
        alert("reward init")
        options =
          adId: "ca-app-pub-****************"
          autoShow: true
        success = ()->
          alert("loaded rewarded video")
          return
        fail = (data)->
          alert("fail rewarded video"+data)
          return
        if AdMob
          AdMob.prepareRewardVideoAd(options, success, fail)

But "AdMob.prepareRewardVideoAd(options, success, fail)" is failing with "'int org.json.JSONObject.length()' on a null object reference". I have no idea of what it means.

Don't know why but now it is working. I just changed alert by console.log.


[FEATURES]add dataload options to enhance runtime cache usage

What feature you'd like to add:
Why is this feature needed:

fixed by #1217


protect dummy getWorksheetFunctions in dependents unittest builds

Codecov Report

Merging #53 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   81.63%   81.63%
=======================================
  Files          28       28
  Lines        1688     1688
=======================================
  Hits         1378     1378
  Misses        310      310

Impacted Files
Coverage Δ

source/xlld/wrap/traits.d
70.96% <ø> (ø)
:arrow_up:

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 842fe85...d5cd9b7. Read the comment docs.


feat: 3116 enhancement session middleware

Description

For server side sessions, the session id is now generated before the route handler. Thus, on first visit, a session id will be available inside the route handler's scope instead of afterwards
A new abstract method get_session_id was added to BaseSessionBackend since this method will be called for both ClientSideSessions and ServerSideSessions. Only for ServerSideSessions it will return an actual id.
Using request.set_session(...) will return the session id for ServerSideSessions and None for ClientSideSessions
The session auth MiddlewareWrapper now refers to the Session Middleware via the configured backend, instead of it being hardcoded

Looking forward to your feedback!
Closes
Closes #3116

Okay, I see there are quite a few failures. Gonna collect my questions here on how to solve them:

Pyright flags that "session_id" is not a valid key in Scope. Can I just add it as session_id: str | None or should it be of a different type spec?
Mypy also flags some issues with "session_id" being None when it should be string. Technically, this is only flagged on server side where it should never be None. Should I change the code instead for client side to return "null" so that the type is always str?

Will take some more time to work through the failed tests.

Okay, I see there are quite a few failures. Gonna collect my questions here on how to solve them:

Pyright flags that "session_id" is not a valid key in Scope. Can I just add it as session_id: str | None or should it be of a different type spec?
Mypy also flags some issues with "session_id" being None when it should be string. Technically, this is only flagged on server side where it should never be None. Should I change the code instead for client side to return "null" so that the type is always str?

Will take some more time to work through the failed tests.

Regarding session_id not being part of the scope, that's my fault. In my example I had shown it being added to the scope because I was being lazy :P The better way to do this is to set this to ScopeState (in litestar.utils.scope.state which is what we use to maintain all the state that Litestar needs to maintain.
Regarding your second point, while str | None is the accurate type hint, I think it may make the life of users far easier if we could just annotate it as str so I think your idea of returning null for the client side sessions is a good idea.

Regarding session_id not being part of the scope, that's my fault. In my example I had shown it being added to the scope because I was being lazy :P The better way to do this is to set this to ScopeState (in litestar.utils.scope.state which is what we use to maintain all the state that Litestar needs to maintain.
Regarding your second point, while str | None is the accurate type hint, I think it may make the life of users far easier if we could just annotate it as str so I think your idea of returning null for the client side sessions is a good idea.

I think I'm gonna need a bit more help here. I thought I'd have to add session_id to litestar.types.asgi_types.BaseScope or .HTTPScope (since we probably dont want to have this for .WebSocketScope). You suggest to add it to ScopeState instead, but how and where is that used? I see that litestar.connection.base.ASGIConnection has both state (from self.scope.get("state") and _connection_state where only the latter is ScopeState... but it is build from the scope. Being new to the framework, it is not 100% clear to me how this scope state should be used and how it can be reached throughout the lifetime of a request.

@aranvir the reason that we can't add it directly to HTTPScope because that's taken directly from the ASGI specification. The state is what's meant to be used for anything specific to the application, or framework.
While we can use scope["state"]["session_id"], the reason I suggest against that is because users are allowed to store stuff in state and if someone unkowingly overrides the session_id, then it will mess things up. To maintain state internal to Litestar we use the ScopeState.
The Request class has a _connection_state attribute which is an instance of ScopeState. You can see examples of how it's used in the various properties like accept, content_type etc. (ref).  Also, you can instantiate a new ScopeState by using the from_scope class method and just pass in the scope. You would need to this in the middleware when setting the session_id before we process the request.
NOTE: All the properties on the Request class cache the attributes that we retrieve from ScopeState, but I don't think that's needed for retrieving the session ID since I doubt that there's going to be any real benefit to caching the session_id.

Hi @guacs changed it to storing the session_id in the ScopeState instead of the scope. Is this implementation okay? Also fixed the linting and testing.
Regarding the other failed pipeline jobs:

Validate PR target: Should I re-open this pull request to point it to the develop branch? For sake of keeping these threads I would continue working this pull-request until all checks pass and then I can make a new pull request. Or edit the target - don't know what makes more sense.
codecov: Never worked with this before so I also don't really understand what it is complaining about. Does this track how much of the code is tested? I barely changed the failing file, and what I added was just so the tests would pass AND mypy would stop complaining about None not having the get_session_id method.

Hi @guacs changed it to storing the session_id in the ScopeState instead of the scope. Is this implementation okay? Also fixed the linting and testing.
Regarding the other failed pipeline jobs:

Validate PR target: Should I re-open this pull request to point it to the develop branch? For sake of keeping these threads I would continue working this pull-request until all checks pass and then I can make a new pull request. Or edit the target - don't know what makes more sense.
codecov: Never worked with this before so I also don't really understand what it is complaining about. Does this track how much of the code is tested? I barely changed the failing file, and what I added was just so the tests would pass AND mypy would stop complaining about None not having the get_session_id method.

I don't think you need to re-open the pull request. You can retarget it to the develop branch. As for codecov, you can look at details of the test and you should be able to find a link to the codecov website for this PR where it'll show which lines that aren't being covered in the tests.
I'll take a look at this later today :)

@aranvir could you add tests as well?

@guacs what tests do you have in mind? The only one that I can come up is to modify the middleware integration test to confirm that the session id is set in the route handler scope - and that it is not None for the server side config and None for the client side config. But I did not see any assert statements in the route handlers of the other tests, so I wanted to check if this really goes into the right direction.

@aranvir could you add tests as well?

@guacs what tests do you have in mind? The only one that I can come up is to modify the middleware integration test to confirm that the session id is set in the route handler scope - and that it is not None for the server side config and None for the client side config. But I did not see any assert statements in the route handlers of the other tests, so I wanted to check if this really goes into the right direction.

I think you can add new tests to the test_middleware.py and make sure that the session ID that is returned by get_session_id is the same as the one set in the cookies. Also, I think a test to ensure that the session ID that is returned is the existing session ID when a session has already been created. That is, we don't want to create a new session ID when one already exists.

Also, I just realized that you're targeting the wrong branch. You should be targeting develop since this is a new feature.

@aranvir Can you address the coverage? Once that's through, this is good to go in :)


ClientError: 500 Server Error: Internal Server Error

Hi,
I revisited one of my old projects today and got this error when trying to send a direct answer: instagrapi.exceptions.ClientError: 500 Server Error: Internal Server Error for url: https://i.instagram.com/api/v1/direct_v2/threads/broadcast/text/
I don't know what this exactly means or how to solve this as I did not find it here: https://adw0rd.github.io/instagrapi/exceptions.html
Thanks

500 Server error means an internel server error with instagram. This could be due to anything, but I suspect that the URL you're making calls to has been deprecated. That means that you can't really do anything to fix it, because this is an issue with Instagram. Try to see if there is another endpoint available with the same functionality as this one.

Thank you so much, have a good day.

I've been trying to find one, but I did not really find anything since I do not fully understand what I'm looking for. Do you know any that I could try, and how to try? I am really sorry if I'm being annoying but I am very new to api-s.

I don't know the exact functionality of the request you mentioned earlier but I think this could be useful: https://adw0rd.github.io/instagrapi/usage-guide/direct.html
I assume that the request you mentioned was used to send a message to many threads so to replicate that you could use:
To get all the threads in your inbox:

direct_threads(amount: int = 20, selected_filter: str = "", thread_message_limit: Optional[int] = None)

then you could send a message to the desired threads using this:

direct_send(text: str, user_ids: List[int] = [], thread_ids: List[int] = [])

so for example:
threads = client.direct_threads(amount=10, selected_filter="", thread_message_limit=10)

# Extract the thread IDs from the threads list
thread_ids = [thread.id for thread in threads]

# Send a message to the desired threads
client.direct_send(text="Cool message here", thread_ids=thread_ids)

Let me know if you need any more assistance, I'll try to help!

Thanks I figured it out. I was accidentally giving it the message id-s not the thread id-s.


Resource API feedback

Overview
Based on this readme listing I'm adding feedback based on existent implementations and expected lib user competencies (as we target many almost non-tech users - publisher, data wranglers etc).
use frictionlessdata\datapackage;

// add a resource - will raise exception in case of validation error for the new descriptor
$resource = Factory::resource((object)[
    "name" => "new-resource", "data" => ["tests/fixtures/foo.txt", "tests/fixtures/baz.txt"]
])
$datapackage->addResource($resource);

General
See - https://github.com/frictionlessdata/datapackage-php/issues/18
Resource properties
Implementations reference provides some useful properties (https://github.com/frictionlessdata/implementations):

resource.tabular -> true if resource is tabular
resource.table -> to access tableschema.Table for tabular resource
source/source_type (this two are still under consideration)

getting the underlying table object is possible, for each data stream (each data stream object corresponds to a path or data element)
// get the tableschema table object for the first path
$table = $resource->dataStreams()[0]->table

I'll add a comment to #22 to add this detail to the README

fixed the general comments in v0.1.4
see the README for the updated usage examples
opened an issue to add the additional properties / methods to Resource object: #23


Vector Field

This example is lifted from the 4.1 cookbook:
var vectors = new List<RootedCoordinateVector>();
double[] xs = Generate.Consecutive(20, 0.5, -5);
double[] ys = Generate.Consecutive(20, 0.5, -5);
float r = 0.5f;

for (int i = 0; i < xs.Length; i++)
{
    for (int j = 0; j < ys.Length; j++)
    {
        vectors.Add(new RootedCoordinateVector(new(xs[i], ys[j]), new((float)ys[j], -9.81f / r * (float)Math.Sin(xs[i]))));
    }
}

var field = new VectorField(new VectorFieldDataSourceCoordinatesList(vectors));
WpfPlot1.Plot.PlottableList.Add(field);

Thanks @bclehmann, this is a great start! Pulling some convo from Discord (#1966)

I would like at a minimum to have less ugly arrows, a method in the plottable factory, and options to anchor the arrows on their midpoint, rather than the vector tail. Colormap support would be cool too

These are all good extensions for this plot type! I'll review and merge this PR in now, and refinements can be made in future PRs 👍

Also (let me know if I'm messing up here) I'm going to rename RootedCoordinateVector.Distance to RootedCoordinateVector.Magnitude because I think that word better matches the concept of a vector, and it may be representing things which are not spatial

Also (let me know if I'm messing up here) I'm going to rename RootedCoordinateVector.Distance to RootedCoordinateVector.Magnitude because I think that word better matches the concept of a vector, and it may be representing things which are not spatial

Magnitude is actually what I named it originally but I realized some of our other classes used Distance so I tried to be consistent. And then I learned Vector2 uses Length so I guess consistency is going to be hard.

I think the main thing that's missing is in the plottable factory, I don't think it automatically assigns a colour to the vector field (so it will be black by default). I don't think we should release a new version without that, but fortunately that's a 2 minute fix.
I also wonder if the legend should have a little arrow (right now it's just a line, which isn't great). As for all the colourmap stuff, that would be cool and probably pretty easy, but maybe not essential.

Good points! Thanks for your feedback.

Magnitude is actually what I named it originally but I realized some of our other classes used Distance so I tried to be consistent. And then I learned Vector2 uses Length so I guess consistency is going to be hard.

Now that you mention it, I can see multiple sides to this. Since the RootedCoordinateVector and RootedPixelVector both have a unit baked in (coordinates and pixels), perhaps distance or length makes sense over magnitude.

I think the main thing that's missing is in the plottable factory, I don't think it automatically assigns a colour to the vector field (so it will be black by default). I don't think we should release a new version without that, but fortunately that's a 2 minute fix.

#3630

I also wonder if the legend should have a little arrow (right now it's just a line, which isn't great). As for all the colourmap stuff, that would be cool and probably pretty easy, but maybe not essential.

#3631


Update Travis configuration to use Xcode 8

Default to using Xcode 8 for Travis builds.
Testing on iOS 8.x currently times out on Travis with Xcode 8, so those tests will remain on Xcode 7.3. This is also useful for ensuring continued support for building with Swift 2.2.

Current coverage is 92.37% (diff: 100%)

Merging #89 into master will increase coverage by 0.54%

@@             master        #89   diff @@
==========================================
  Files             6          6
  Lines           367        367
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            337        339     +2
+ Misses           30         28     -2
  Partials          0          0

Powered by Codecov. Last update f4370aa...11b2b76


fix(texttracks): unable to disable sideloaded texttracks in the AVPlayer

This PR will fix #1144. I previously submitted PR #1468 but that branch become stale and is therefore closed. I forked the repo from scratch and applied the fix to the changes made in this repository in the last few years.
The issue:
The AvPlayer will freeze the last shown subtitle when you disable sideloaded text tracks. There is no way to disable them. This is only an issue with sideloaded subtitles on iOS and tvOS. Android ExoPlayer or subtitles embedded in the HLS manifest work perfectly.
Reproduce steps:

Load a video and set VTT texttracks using the texttracks property.
Select one of the subtitles
Disable the subtitles exactly when there is a subtitle visible (set selectedTextTrack prop to {type: 'disabled'}.
Notice how the last shown subtitle is frozen

The solution
The exact cause of the issue is unknown (as can be seen in #1144). All enabled states are set to false so you would expect that all tracks would disappear:
https://github.com/react-native-video/react-native-video/blob/master/ios/Video/RCTVideo.m#L1238
A solution to fix this would be to load an empty VTT file that gets selected when {type: 'disabled'} is given. This would fake disabled subtitles if there are no cues in the VTT file to display.
This PR adds the generation of the VTT file into react-native-video. This solves the problem in the Video component and it doesn't need a dependency on rn-fetch-blob. The VTT file is almost empty, it only shows a small dot for 1 ms at the 99:59:59.000 timestamp (I guess it's safe to assume that it's empty). The file is only added in the player when you are sideloading texttracks, there are no texttracks loaded when the texttracks prop is not set. The file is written into the Caches directory to make this fix work on both iOS and tvOS.
Final note: the original code was made a few years ago. I tried to look into the problem again but couldn't find another solution. If there is anyone with a suggestion please let me know. Loading this file seems like a dirty hack but there appears to be no other solution for now.

@nbennink Before spending more time rebasing this again, let's wait for some feedback to make sure this is the correct fix.
@nickfujita @freeboub Can you take a quick look?

Hi, i am really not an expert in ios :/ but code looks good to me and the workaround make sens i think. I just have a doubt about the data of the blank vtt track. There is no index... (Maybe i miss something i just read the code) . It is important from my experience on Android to have an index on each track. This index shall be used to select subtitles. In case you have 2 tracks with the same language you must select them by index. Can you please ensure an index is provided on api level please ? Else it is ok for me!

Hi, I have a similar problem with iOS, Android works fine.
I use TextTrackType.VTT for textTracks. Is there any solution to fix this?

Hi, I have a similar problem with iOS, Android works fine. I use TextTrackType.VTT for textTracks. Is there any solution to fix this?

Please test this PR and approve it if it works fine ! :)

Hi, i am really not an expert in ios :/ but code looks good to me and the workaround make sens i think. I just have a doubt about the data of the blank vtt track. There is no index... (Maybe i miss something i just read the code) . It is important from my experience on Android to have an index on each track. This index shall be used to select subtitles. In case you have 2 tracks with the same language you must select them by index. Can you please ensure an index is provided on api level please ? Else it is ok for me!

Thanks for checking it out! This tracks should technically not be selected manually in your own code using an index. The package handles it automatically with {type: "disabled"}. That being said, the language of the disabled track is disabled so that can technically cause an issue when you provide a track with that language as well.
I see that the Swift PR is merged to master as well. Let me check if this issue still exists in the new codebase. If it does I can refactor this with Swift and add an index as well 👍

Thanks, i totally agee, expect that user will lost to see a track but will not be able to select it. Selecting Disable, or this fake track should have the same behavior... Or you should explicitly say in doc that this track cannot be selected  (i think it 's better to allow selection of this track :) )

textTracks = [{                   title: 'English',                   language: 'en',                   type: TextTrackType.VTT,                   uri: "subtitleLink",                }];             selectedTextTrack= {type: 'title', value: 'English'};
I tested this pr, and it works better.
But sometimes it still has a problem that automatically corrects itself in a matter of seconds (3-4)

Hi, i am really not an expert in ios :/ but code looks good to me and the workaround make sens i think. I just have a doubt about the data of the blank vtt track. There is no index... (Maybe i miss something i just read the code) . It is important from my experience on Android to have an index on each track. This index shall be used to select subtitles. In case you have 2 tracks with the same language you must select them by index. Can you please ensure an index is provided on api level please ? Else it is ok for me!

Thanks for checking it out! This tracks should technically not be selected manually in your own code using an index. The package handles it automatically with {type: "disabled"}. That being said, the language of the disabled track is disabled so that can technically cause an issue when you provide a track with that language as well.
I see that the Swift PR is merged to master as well. Let me check if this issue still exists in the new codebase. If it does I can refactor this with Swift and add an index as well 👍

In fact, let me correct myself, this track should not be shown to application. As it is not shown with other subtitles/player, there is no reason to show it in this use case. It should be only an internal 'mixture'. Thanks !

@nbennink can you fix conflicts please ?

@nbennink Is it all ready now?


Fix object cannot be nil (key: userId) when initialising Snowplow tracker

Describe the bug
When upgrading to version 3.1.0 and initialising the snowplow tracker, there is no session ID in the session dictionary, defaulting to nil and throwing an exception, crashing the app.
This issue is not present in 3.0.2 or below
To Reproduce
Upgrade to 3.1.0, initialise a snowplow tracker
Expected behavior
Snowplow tracker is initialised and ready for use
Device information (please complete the following information):

Device: iPhone 11 Simulator, from Xcode 13.2.1
OS: iOS 15.2

Additional context
Specifically this exception is thrown in the SPSessionState.m on line 88...
[self.sessionDictionary setObject:userId forKey:kSPSessionUserId];
As a test, I've also tried explicitly setting a user ID in the subject configuration (which we don't usually use at all) but this made no difference.

Thanks a lot @adamcarter93  for reporting this issue.
We just released the new version 3.1.1 that should fix the issue.
Please, let us know if you face any problem with this version.


Cannot find wildcard import module in buildSchema

Hi,
I'm trying to do the wildcard import as described in the docs, but it continuously throws an error cannot find the module.
Code I'm using

async function bootstrap() {
  const schema = await buildSchema({
    resolvers: [__dirname + "/**/*.resolver.ts"],
  });

  // other initialization code, like creating http server
}

bootstrap(); // actually run the async function

The error I'm getting:
{ Error: Cannot find module './src/recipes/recipe.resolver.ts'
    at Function.Module._resolveFilename (module.js:548:15)
    at Function.Module._load (module.js:475:25)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at filePaths.map.fileName (/Users/tamas.lorincz/Projects/graphql-test/node_modules/type-graphql/dist/helpers/loadResolversFromGlob.js:10:47)
    at Array.map (<anonymous>)
    at Object.loadResolversFromGlob (/Users/tamas.lorincz/Projects/graphql-test/node_modules/type-graphql/dist/helpers/loadResolversFromGlob.js:10:31)
    at options.resolvers.forEach.resolver (/Users/tamas.lorincz/Projects/graphql-test/node_modules/type-graphql/dist/utils/buildSchema.js:36:37)
    at Array.forEach (<anonymous>)
    at loadResolvers (/Users/tamas.lorincz/Projects/graphql-test/node_modules/type-graphql/dist/utils/buildSchema.js:34:23) code: 'MODULE_NOT_FOUND' }

Anyone has faced this issue or knows how to resolve it?

      resolvers: [path.resolve(__dirname, '**', '*.resolver.{js,ts}')],

try that I find it more reliable

@thomsa-swi
Try to use the same path pattern with raw glob to see what files does it find, what path it generates, etc.

Closing for a housekeeping purposes 🔒


Need default location for CLI

Having to add --location for az create can be defaulted to either a global setting or by subscription.
related https://github.com/Azure/azure-cli/issues/2662

it is supported already in the current master branch, like az configure --defaults location=westus


fix(nix): Add config directory to resulting package

It was missed in #474, bring it back here.

@mkazlauskas Done.


Is SSL enabled by default?

Is it? no need to add anything in the config ?

LP doesn't enable SSL at all...
You have to enable it in the settings of your database, if that isn't already enabled.
LP will - at most - check if the connection to the database (MySQL for example) has SSL enabled.

okay thanks!


docs-dev isn't highlighting code

https://docs-dev.raku.org/language/modules.html#use
for example looks like it's just putting blocks around code, not colorizing.

This may be hiding an issue on #124

the default when there is no highlighter is to put <pre> blocks around code. It is not hiding colorising. there is no highligher present in the build environment. The fix is quite easy.
Closing as a duplicate of #124


Interactive Chart Example - filter, ranges, brush selection, etc...

Feature Description
Hi, I've looked at sample projects on the Evidence's site and all the demo app are what you could call static. They do have interactive tooltips or toggleble legends, but I couldn't find any example where I could, for example, filter a chart based on dates or brush select a cross section on one chart and it would reactively select the data on a linked chart or some filter or dropdown selection applied.
Thanks

Hey @kuatroka
These are on our roadmap, but not supported yet!

https://github.com/evidence-dev/evidence/issues/848

The point I was making is to enable the interactivity of the charts. The filtering option is just one many (selection single value/multiple values, dropdown, select range of dates, linked charts). See examples below:
Linked Charts with brush selection
Date Filtering.
Thanks

Makes sense, thanks for the ideas!
Happy to open new issues for those individually - I suspect there is not an easy way to enable all types of "interactivity" globally.
We try to keep our issues quite "narrow" so they are easier to work on!


Weird behavior for  with multiple <*Amt>s

This commit introduced a bug where a <AmtDtls> with multiple kinds of <*Amt> leads Transaction#parse_currency and #parse_amount to concatenate the values of all <*Amt>s.
E.g., this XML leads to the currency being EUREUREUR and the amount 0.03 (== "<IP_ADDRESS>".to_f):
<AmtDtls>
  <InstdAmt>
    <Amt Ccy="EUR">0.03</Amt>
  </InstdAmt>
  <TxAmt>
    <Amt Ccy="EUR">0.04</Amt>
  </TxAmt>
  <PrtryAmt>
    <Tp>IBS</Tp>
    <Amt Ccy="EUR">0.03</Amt>
  </PrtryAmt>
</AmtDtls>

Oh, damn.
Thank you for reporting the issue, I will take a look.

Released as v2.6.3

Thanks for the quick reaction! This changes the behavior from 2.6.1 though, where it always used the TxAmt. I'm assuming the Amts don't have a specified order, so the current behavior is random.

That's true, but that was already changed in 2.6.2, so 2.6.3 only fixes the error introduced by that change.
The previous behaviour was already "random" also, as it would take the upper level Amt if that was provided. That part hasn't changed.
In 2.6.2/2.6.3 it was changed that also other amounts may be considered and in fact TxAmt may not be the first.
While the different amounts are optional, the order should always be the same. In XML schema as far as I am aware you'd otherwise have to go through some lengths to allow a changed order.
Therefore it should be in order InstdAmt, TxAmt, CntrValAmt, AnncdPstngAmt, PrtryAmt.
Unfortunately not every bank has this implemented the same way, but for the same bank it generally also behaves consistently.
The change in 2.6.2/2.6.3 reflects that it will always take the first amount there.
If you need a very specific amount and currency, I would suggest adding specific methods for that, which then also wouldn't consider the upper level Amt


Fix callback-example.yaml

The runtime expression must be quoted as it starts with a '{' - an indicator character, otherwise it's invalid YAML.
I also added the 'openapi' and 'info' properties because they are required and, thus, the spec file is invalid without them.

Was this example ever intended to be complete / self-contained? It also has a missing definition of #/components/schemas/UserLogData

#TDC: @tfesenko Thank you for submitting this PR.  Would you please update per @MikeRalphson's comment so this is a complete example.
You may want to align with what @whitlockjc is drafting for Issue #1245

@tfesenko If you would like to get this addressed ASAP and not wait for #1245, I would just make the following changes to your PR as it will align with our plans:

Replaces lines 1-4 with # ... (this will be our way to indicate "omitted for brevity")
Resolve the $ref on line 51:
a. Add # ... as the last line of the document
b. Replace $ref with an inline schema

I guess 2.a could be documented in #1245 but for now, being explicit might not be a bad thing.

ACTION: @tedepstein to reach-out to @tfesenko when she's back (likely Mon, 7/10)

@whitlockjc , I addressed your suggestions in commit ccf0169. Can you please have a look? Thanks!

:shipit:

Since this is a non-spec change, we should be able to branch/merge into master instead of a release-specific branch.  I will have to merge this manually.

Merged manually 542fc445ced49073d277b0db526bc0bcccc3234b

Weird, it didn't keep your commits but the commit message clearly points to your commit.

@tfesenko I apologize the merged commit didn't retain your authorship of the two commits.  I did it this way to avoid asking you to delete this PR and recreate a new one from master.  Next time, I'll just ask you to create a new PR so your details in up in the commit log.  I apologize.


Change dbt back to a runtime dependency

This commit (presumably accidentally) changes dbt from a standard dependency to a development dependency (which means it isn't installed when not working on this gem). This causes apps to fail to compile when they hit this line unless dbt has been already included as a dependency of the project.

Oh shoot, sorry about that - thanks!

Available in 1.0.3 (thanks for the reminder, btw!).

@colinta it looks like you bumped the version on RubyGems but didn't push it onto master :)

DUH!  Thanks again.  Pushed, and tagged 1.0.3

On Oct 18, 2016, at 12:28 PM, Jonathan Bender<EMAIL_ADDRESS>wrote:
@colinta https://github.com/colinta it looks like you bumped the version on RubyGems but didn't push it onto master :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/motion-kit/motion-kit/pull/140#issuecomment-254596683, or mute the thread https://github.com/notifications/unsubscribe-auth/AABrsm0edP9TruTWZYD1V-nuTLksftzIks5q1Q_DgaJpZM4KZ-R8.


dtc: layer3 results filter out internal fields.

layer3 results filter out internal fields: id & visible_time.

#191


Spark 3.2.0 support

Updated to Spark 3.2.0 and Scala 2.12.15.
Tests seem to work

@Jolanrensen thank you! Does this version work with older Spark?

@asm0dey I'm not sure! I haven't tested that yet. I simply updated the versions and fixed like one override. We don't have any tests that try this, maybe you could look into that?
Although, not much has changed regarding the API, especially since all the tests we do have passed immediately, so I think it might be fine.

I thought about such tests, but it's something non-trivial to implement because it will force us to have somehow tested with different Spark versions.

Yeah exactly. But how would you want to test it then? Use the API with spark 3.2.0 as library in a project that used 3.0.0 before?

Set up a new project built with kotlin-spark built against spark 3.2 and add an explicit dependency on Spark 3.0 to it, I think.

Ah, that seems to give errors. Like Exception in thread "main" java.lang.NoSuchMethodError: 'scala.collection.Seq org.apache.spark.sql.catalyst.expressions.objects.Invoke$.apply$default$5()'.
This means that the API needs to have the same version of Spark as the end-user will use.

And this automatically means we need a separate spin-off for 3.2 :(

If you still want to support 3.0.0, then yes

What errors does it give when you use current version with 3.2?

I get the same error as when mismatching the versions the other way around.
I also read complaints on Slack that it was broken.
I'm pretty sure that a cross-version solution is not the best way to go, though. So I'd say, drop 3.0 support for the next version, since 3.2.0 is the last 3.x Spark version anyways.
What I would do is always target the latest version, which now is 3.2, and then one LTS version which currently is 2.4 (according to Wikipedia).

Sounds reasonable, but it requires some further thinking about the process. Should we bump the major version because it's backward incompatible? And also… what if we find a bug affecting both 3.0 and 3.2 versions? It sounds like we should somehow release the support branch.

Hmm maybe we can make it 1.1.0? As Spark also only changed the second number.
Hmm, yeah if you want to have a support branch for 3.0 still, you can create that, but then it also needs to be maintained when we find a bug. The project, however, isn't very active all the time, so I think only supporting the latest version would be enough. That is, unless there's still a lot of requests for a 3.0 version.
It's up to you, it's your project after all :).

Maybe you're right. It's interesting that folks from Spark broke backward compatibility in a minor release. Maybe we should really bump the version to 1.1.0 and support the old version in the 1.0 branch.

Possibly we should create branch like spark-3.2 here, bump there version and add compatibility with spark 3.2 in this branch. And do releases from there too.

I would choose the option that is the least work for the future so that we can make updates faster when a new scala- or spark update comes around :)

The next Scala is 3 and I think that it'll be a huge piece of work to support it…

Not sure how quickly spark is updated to scala 3 however. I was more aiming towards another scala 2.x.x version.
But I'd say spark 3.2 support should be released as soon as possible anyways as there are people now dropping Kotlin because they cannot use the API on 3.2 yet :/
So we should either drop support for 3.0 or keep it on a separate branch.

@Jolanrensen may I ask you please to do the following: change your fork to work with the spark-3.2 branch, remove support for spark 2 there and change the code to work with 3.2

Sure, this will also remove scala 2.11 then right? Since that only works with Spark 2

https://github.com/Jolanrensen/kotlin-spark-api/tree/spark-3.2 Alright, here is my branch based on your spark-3.2 brach. Old Scala and Spark 2 is removed and everything is 3.2 now.

I think you can just create aPR against my branch!

Alright, moving to https://github.com/JetBrains/kotlin-spark-api/pull/118


Part 2 does not continue on Part 1

Part of 1 of the doc was based on the scoring of two models side by side and then the evaluation at the end.
Part 2 starts with a different pipeline in which only one model is loaded (linear regression).
Therefore, Part 2 is not really a continuation of Part 1, as the article says at the beginning.
The screenshot that shows where the inference button is also contains a "map" or "visual representations" of the building blocks in the designer that are not equivalent to what was done in part 1.

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

ID: e6fbc978-36aa-d15b-c770-e9140fb89f79
Version Independent ID: ba3e2bc4-d812-c405-15cc-02660b374676
Content: Tutorial: Deploy ML models with the designer - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-designer-automobile-price-deploy.md
Service: machine-learning
Sub-service: core
GitHub Login: @likebupt
Microsoft Alias: keli19

@eyast I think in part 1 of the tutorial also linear regression is used which is a continuation in part 2. Which other model are you referring to in part 1?
In the second part of your question are you referring to screen shot in this section? The designer modules in the second part are the same but since the experiment has completed the modules are shown in green.

@eyast I think in part 1 of the tutorial also linear regression is used which is a continuation in part 2. Which other model are you referring to in part 1?
In the second part of your question are you referring to screen shot in this section? The designer modules in the second part are the same but since the experiment has completed the modules are shown in green.

Thabks a lot for the reply. I remember now that I actually didn't build the model step by step but just loaded the sample pipeline for auomobiles,assuming it would be the same.
The sample in the library trains two models,and evaluates them against each other .sorry,my bad,I thought what's in the library represents what's detailed on the pages because I think this was mentioned somewhere on the page
Get Outlook for Androidhttps://aka.ms/ghei36

From: RohitMungi-MSFT<EMAIL_ADDRESS>Sent: Friday, January 29, 2021 9:31:51 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Eyas Taifour<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Part 2 does not continue on Part 1 (#69693)
@eyasthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feyast&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167287388|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lGJuIVguarvvx%2B%2FWVRMa80lMtjGFNCmyWxf2F6Ttz6U%3D&reserved=0 I think in part 1 of the tutorial also linear regression is used which is a continuation in part 2. Which other model are you referring to in part 1?
In the second part of your question are you referring to screen shot in this sectionhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fmachine-learning%2Ftutorial-designer-automobile-price-deploy%23create-a-real-time-inference-pipeline-1&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JdNL8FWx9JjpyoVAKSk6FFfJ0m4MQTlSQHUe9DKrVmk%3D&reserved=0? The designer modules in the second part are the same but since the experiment has completed the modules are shown in green.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F69693%23issuecomment-769722002&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Jgn4hmQFgRrx540FBANVDauQHrJV22eQi8KAraWhZt4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALUEL5GKR4QE35QLBGHXKZ3S4KFBPANCNFSM4WYJWR2Q&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=UbwA7aCnTtHLq21TY%2B2s0sLI1eMwQqolisF4D2dBvLE%3D&reserved=0.

Thabks a lot for the reply. I remember now that I actually didn't build the model step by step but just loaded the sample pipeline for auomobiles,assuming it would be the same.
The sample in the library trains two models,and evaluates them against each other .sorry,my bad,I thought what's in the library represents what's detailed on the pages because I think this was mentioned somewhere on the page
Get Outlook for Androidhttps://aka.ms/ghei36

From: RohitMungi-MSFT<EMAIL_ADDRESS>Sent: Friday, January 29, 2021 9:31:51 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Eyas Taifour<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Part 2 does not continue on Part 1 (#69693)
@eyasthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Feyast&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167287388|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=lGJuIVguarvvx%2B%2FWVRMa80lMtjGFNCmyWxf2F6Ttz6U%3D&reserved=0 I think in part 1 of the tutorial also linear regression is used which is a continuation in part 2. Which other model are you referring to in part 1?
In the second part of your question are you referring to screen shot in this sectionhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fmachine-learning%2Ftutorial-designer-automobile-price-deploy%23create-a-real-time-inference-pipeline-1&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=JdNL8FWx9JjpyoVAKSk6FFfJ0m4MQTlSQHUe9DKrVmk%3D&reserved=0? The designer modules in the second part are the same but since the experiment has completed the modules are shown in green.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F69693%23issuecomment-769722002&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=Jgn4hmQFgRrx540FBANVDauQHrJV22eQi8KAraWhZt4%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FALUEL5GKR4QE35QLBGHXKZ3S4KFBPANCNFSM4WYJWR2Q&data=04|01|eyast%40microsoft.com|7dea6faa69874019b0b208d8c44117ae|72f988bf86f141af91ab2d7cd011db47|1|0|637475131167297343|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=UbwA7aCnTtHLq21TY%2B2s0sLI1eMwQqolisF4D2dBvLE%3D&reserved=0.

We will now proceed to close this thread as the tutorial part 1 and part 2 are a continuation of the steps to be followed. If there are further questions regarding this matter, please tag @RohitMungi-MSFT in your reply.


styled FAQ page and initial setup of cms

After cleaning up this branch, this PR will run.
Let's get this merged in and we can get main back into a working state.

As a general note I would love to see a review of faq/styles.js to see how many of those styles could be moved into a site-wide styles file rather than in this local styles file.
@shinjonathan up to you - is now a good time to be thinking about this or do we need to save this for a general refactoring down the line?

A sidewide stylesheet would be good. We can start moving towards that general direction, I would like to take a look at the outstanding branches that are currently being worked on just in case someone has already started making that move.

We can likely dismiss this PR once we see the accordions used for the contributers page.


Handle conflicts between class attributes and artifacts

Class attributes override artifacts, which can be confusing. In this example, the value of myval is 1, not 5, in steps after start. We should show a warning or handle this better.
class MyFlow(FlowSpec):
    myval = 1
    @step
    def start(self):
        self.myval = 5

I guess this is fixed and flow fails in such a case. Can this be closed?
raise AttributeError(
2023-04-09 03:43:26.784 [1681004606440465/start/1 (pid 44888)] AttributeError: Flow level attributes and Parameters are not modifiable

This is indeed throwing an exception now when trying to reassign class attributes. The original bug is covered, though it is not the greatest user experience as the exception is only raised during step execution, which is quite late in the lifecycle.


Add string "verbose" for -v help

Usually I grep for "verbose" string to see if any command have such capabilities. I believe many do the same, because that is a commonly used term (And I missed the verbose flag because of that, which might be a funny to say).
So, it might be better to reword the help string of "-v" to include the word "verbose" somewhere.
Thanks

Maybe just add --verbose as an alternative spelling?

Sure, that would help too


Upgrade to Spring Boot 3.0.0-RC1

Purpose
Upgrade to Spring Boot 3 for SpringBoot module, it's used to test with Spring Cloud Azure 6.0 for GA.
Does this introduce a breaking change?

[x] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test
N/A

Test the code
N/A

What to Check
N/A
Other Information

Hi @felipmiguel  this upgrade is to prepare the Spring Boot 3 support in the branch feature/spring-boot-3, any feedbacks are welcome!


Update IES El Rincon domains

We previusly only used to give students the licenses, we now have teachers on the same domain, I didnt see a way whitelist only the domain and the subdomain,
Changelog:
Added IES El Rincon Domain ( didnt remove subdomain)

@Meganitrospeed Pull request merged. Thank you!


Transpose Of Matrix

I would like to contribute to the C++ repository.

hello sir, you haven't added file name extension which is a bad habit. Make sure you read rules to contribute carefully and mention your name in file as a comment.
Don't make this mistake again!
Waiting for your next PR!!!

Hello sir, thank you for merging the pr and also for pointing out mistakes.
I will perform better in next prs.
On Sat, 1 Oct, 2022, 6:33 pm Adarsh Addee, @.***> wrote:

hello sir, you haven't added file name extension which is a bad habit.
Make sure you read rules to contribute carefully and mention your name in
file as a comment.
Don't make this mistake again!
Waiting for your next PR!!!
—
Reply to this email directly, view it on GitHub
https://github.com/AdarshAddee/Hacktoberfest2022_for_Beginers/pull/54#issuecomment-1264358394,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVYXSTHTVOZKYC5ETSPKPY3WBAZDTANCNFSM6AAAAAAQ2OC3AM
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

Good!!!


kafka(ticdc): column selector allow filter out columns if there are at least primary key or one unique key

What problem does this PR solve?

Issue Number: close #10042
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/test verify

/test verify

/cherry-pick release-7.5


run scripts/tests/ at Travis

I'm not sure if you want this @sloria (depends on how you manage the scripts directory, what the lifespan and workflow is for scripts), but over at https://github.com/pattisdr/osf.io/pull/2#issuecomment-191476364 I noticed that we're not actually running scripts/tests/ at Travis. From the looks of it (and as one might expect), this test suite is in a broken state:
============================== 24 failed, 57 passed, 15 error in 142.83 seconds ===============================

Other than the scripts that run on cron jobs, the scripts are one-offs that target older versions of the database, so the tests are expected to fail.


80-finishing-the-chat-bot-ui

code structure changed
code not needed deleted
chatbot name added
keyboard bug fixed

closing because this is integrated into one combined PR


"Active notifications" that were edited and shouldn't be notifiable

I have two messages on chat.zulip.org with the active_mobile_push_notification bit set -- even though I'm fully caught up.
This becomes conspicuous with #15179, which is currently deployed on chat.zulip.org for testing though it's not yet merged. With that PR, I see a red badge reading "2" on the Zulip app on the iPhone home screen. This would be a pretty bad experience if I were any normal user -- specifically if I couldn't go look in the server's database to debug.
Both messages are indeed unread. But all the other UserMessage flags are clear -- they're both stream messages, and don't have any mention or wildcard-mention flags. With my settings, that should mean they'd never have caused notifications in the first place.
But, both were edited:

One message originally @-mentioned me, and was "deleted", i.e. edited to "(deleted)".
One message originally @-mentioned the @mobile group, and... actually it seems to have been edited to a version that still says @*mobile*. So there may be a second bug there -- it should still have the wildcard-mention flag. Nevertheless, given that it lost that flag, it's an instance of this bug too.

Both were to streams I've muted, so it's natural that they remain unread even though I'm caught up.
The deleted message was from 2020-04, just a couple of months ago; the one with @*mobile* was from 2019-01.
We should ensure that when a message is edited so that it no longer should cause a notification:

a remove notification-message is sent to remove the notification;
the active_mobile_push_notification bit is cleared.

We should also likely produce a migration to do this for existing messages, before merging #15179 or deploying on zulip.com. Otherwise anyone with previous messages affected by this bug (and using iOS) will have a bad experience where probably the best outcome is they simply disable Zulip from being able to show a badge count.

The part that isn't a migration can be done via looking at prior_mention_user_ids - mention_user_ids, and calling do_clear_mobile_push_notifications_for_ids in a loop over such users.
This will either need a loop over users in that set and a bit of refactoring, at least to do_clear_mobile_push_notifications_for_ids to accept a user_profile_id rather than a UserProfile to avoid uselessly fetching objects we don't need.
But better might be to make do_clear_mobile_push_notifications_for_ids to accept a list of user IDs and do a bulk query on filtered_message_ids rather than calling it in a loop.

The deleted message was from 2020-04, just a couple of months ago; the one with @mobile was from 2019-01.

I think this secondary bug was fixed in https://github.com/zulip/zulip/pull/14945.

Just to summarize the state for the category of messages that are particularly problematic here:

They are unread -- otherwise the active_mobile_push_notification flag would have been cleared already.
They at one point mentioned the user, but then were edited to not do so
They are be in a muted stream or topic (Since this means the user can be fully caught up on their messages and still have this unread count).

We highlight unread mentions in muted streams/topics ... but not unread former mentions in muted streams/topics.

The deleted message was from 2020-04, just a couple of months ago; the one with @mobile was from 2019-01.

I think this secondary bug was fixed in #14945.

No.


PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

This issue has been moved from a ticket on Developer Community.

Sorununuzu burada açıklayın
===BU SATIRIN ALTINI DÜZENLEMEYİN===
PackageId:CPython39.Exe.x64;PackageAction:Install;ReturnCode:1603;

Original Comments
Feedback Bot on 12/15/2022, 05:04 PM:
(private comment, text removed)

Original Solutions
(no solutions)

duplicate of https://github.com/microsoft/PTVS/issues/7238


Update LAPACKE to latest master

Would it be possible to update (at least) lapack-netlib/LAPACKE to the latest master? It contains a fix for the bug https://github.com/Reference-LAPACK/lapack/issues/59 that is causing failures in our tests https://github.com/gonum/lapack/pull/143.

Probably quicker to do a pull request with just the fix for lapack#59. (As far as I know, OpenBLAS tends to synchronize to major releases of LAPACK and just cherry-pick patches in between. At least in the past when the "netlib" LAPACK was not yet on github and there was only their user forum to go to, lapack bugs were sometimes fixed here first.)


Error when compiling ros2-control

Hi!
I am trying to compile ros2-control but I am having problems when compiling controller-manager-msgs:
| cd build/tmp/work/cortexa72-cortexa53-xilinx-linux/controller-manager-msgs/1.1.0-1-r0/build && build/tmp/work/cortexa72-cortexa53-xilinx-linux/controller-manager-msgs/1.1.0-1-r0/recipe-sysroot-native/usr/bin/python3-native/python3 build/tmp/work/cortexa72-cortexa53-xilinx-linux/controller-manager-msgs/1.1.0-1-r0/recipe-sysroot/usr/lib/rosidl_typesupport_fastrtps_cpp/rosidl_typesupport_fastrtps_cpp --generator-arguments-file build/tmp/work/cortexa72-cortexa53-xilinx-linux/controller-manager-msgs/1.1.0-1-r0/build/rosidl_typesupport_fastrtps_cpp__arguments.json
| Traceback (most recent call last):
|   File "build/tmp/work/cortexa72-cortexa53-xilinx-linux/controller-manager-msgs/1.1.0-1-r0/recipe-sysroot/usr/lib/rosidl_typesupport_fastrtps_cpp/rosidl_typesupport_fastrtps_cpp", line 6, in <module>
|     from rosidl_typesupport_fastrtps_cpp import generate_cpp
| ModuleNotFoundError: No module named 'rosidl_typesupport_fastrtps_cpp'

Does someone know why this recipe is not finding rosidl_typesupport_fastrtps_cpp? What should I change?
Thank you very much,
Jorge

controller-manager-msgs_.bb needs to add this two new build dependencies
ROS_BUILD_DEPENDS += " \
    rosidl-typesupport-fastrtps-c-native \
    rosidl-typesupport-fastrtps-cpp-native \
"


Enable partial clone by default

Enable partial clones(which are by default disabled from git) by default, unless configured otherwise.
Resolves #18190

This is a feature, not sure if code-freeze is already in-use, otherwise this PR could wait.

Codecov Report

Merging #18195 (1486c72) into main (1514e13) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main   #18195      +/-   ##
==========================================
+ Coverage   45.63%   45.64%   +0.01%
==========================================
  Files         828      828
  Lines       91812    91814       +2
==========================================
+ Hits        41895    41910      +15
+ Misses      43185    43176       -9
+ Partials     6732     6728       -4

Impacted Files
Coverage Δ

modules/setting/git.go
33.33% <ø> (ø)

modules/git/git.go
39.59% <100.00%> (+0.82%)
:arrow_up:

modules/charset/charset.go
71.71% <0.00%> (-4.05%)
:arrow_down:

modules/queue/workerpool.go
48.85% <0.00%> (-0.39%)
:arrow_down:

services/pull/pull.go
41.70% <0.00%> (ø)

routers/api/v1/repo/pull.go
28.85% <0.00%> (+0.50%)
:arrow_up:

models/issue_comment.go
54.80% <0.00%> (+0.56%)
:arrow_up:

modules/process/manager.go
82.94% <0.00%> (+1.55%)
:arrow_up:

modules/git/repo_base_nogogit.go
82.50% <0.00%> (+2.50%)
:arrow_up:

modules/git/utils.go
70.83% <0.00%> (+2.77%)
:arrow_up:

... and 1 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 1514e13...1486c72. Read the comment docs.


'from' route object in context undefined in ssr but not in spa mode.

With this code:
async asyncData ({ from }) {
  console.log("from", from")
}

On browser refresh, this page will log undefined in ssr mode but in spa mode it logs it's own route. This problem defeats the 'shallow routing' trick described by @Atinux here:
https://github.com/nuxt/nuxt.js/issues/1322

This seems to be resolved with 1.4.0. Closing. Reopen if still happens.


Rename "split_selection_into_lines" to "selection_into_lines" in docs

According to this

Cool, this looks right to me. @scholtzan?

I signed it!

Thanks!


[feature-wip][udf] support java udf in FE

Proposed changes
Issue Number: #8389
Problem Summary:
First step to support Java UDF in Doris. After this PR, we can create Java UDF in doris.
For example, we create Java UDF function by code below.
CREATE FUNCTION test_udf(int) RETURNS int  PROPERTIES ( "file"="file:///root/hive-udf-1.0-SNAPSHOT.jar", "symbol"="udf.Main",  "type"="JAVA_UDF" )

file indicate where user file is.
symbol for java udf means udf class in this jar.
type indicate this function is a java udf.

Checklist(Required)

Does it affect the original behavior: (No)
Has unit tests been added: (No Need)
Has document been added or modified: (No Need)
Does it need to update dependencies: (No)
Are there any changes that cannot be rolled back: (No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

hi @Gabriel39 , thanks for your contribution.
The Java UDF is an important feature for Doris, and we just prepare to using DSIP to help better document and standardize the design details of some important features.

hi @Gabriel39 , thanks for your contribution. The Java UDF is an important feature for Doris, and we just prepare to using DSIP to help better document and standardize the design details of some important features.
Could you please read the following guide and take good lead? https://cwiki.apache.org/confluence/display/DORIS/Doris+Improvement+Proposals

@morningman Sure, thanks for your advice! I will do this in next few days

I have created a new DIP about my ideas for this feature. Please refer to https://cwiki.apache.org/confluence/display/DORIS/DSIP-001%3A+Java+UDF and give me some feedback if you have some suggestions or concerns.


Publish to Existing Target - can't modify

Publish to Existing Target is referencing an Environment Name that doesnt exist anymore:

When I click on Edit Settings, everything is grayed-out and I cant change the environment name:

How can I just remove the target and start over?

Hi @rmasonjr , this existing deployment target represents a previous deployment, which is performed through CloudFormation. If you want to remove this Beanstalk environment from your account, you can look through your CloudFormation stacks to find the deployment associated with this Beanstalk environment, and tear down the stack. Keep in mind this will remove any other resources associated with that deployment stack.

ah - thanks - I was so focused on the environment I didnt consider CloudFormation.
That worked!


No fake Diagnosis Key submissions triggered randomly by the app

Describe the bug
In several places, the requirement to generate random "fake" network traffic to specific endpoints is stated (e.g. here: "This attack surface is mitigated by random fake messages that are indistinguishable from valid ones. This way, key submission and the retrieval of test results are indistinguishable from the system's background noise, creating plausible deniability for users even if network traffic is observed.")
However, I do not find source code that creates such fake key submissions.
asyncSubmitKeysToServer() has a parameter faked, but I do not see calls to the function where the parameter is set to true.
Expected behaviour
The app should randomly (e.g. about once per day) trigger the same sequence of network traffic (marked as 'fake' in the encrypted data), which would happen if the user is infected.

@mh- thanks for your feedback.
This functionality will be activated and delivered with v.1.1.

@ChristopherSchmitz Is it correct to assume that you will publish V1.0 on the Google Play Store without this advertised security/privacy feature? Will other security/privacy features be missing from V1.0? And when do you plan to publish V1.1?
(Sorry, I didn't find a release plan in the documentation.)

We can confirm this - we also made our FAQ more precise with respect to this question.
As we are working in a very dynamic setup, we can't provide any release plans for upcoming versions. Thank you for your understanding.
Mit freundlichen Grüßen/Best regards,
SW
Corona Warn-App Open Source Team


hoist imports

closes #36

The -> v2.0.5 bump commit ended up on this branch instead of on master. I've cherry-picked it over and re-deleted this branch.

The -> v2.0.5 bump commit ended up on this branch instead of on master. I've cherry-picked it over and re-deleted this branch.

Actually, that was a bad idea because that was still the tagged commit. I've undone the cherry-picking and just merged gh-36 back into master instead.

Actually, that was a bad idea because that was still the tagged commit. I've undone the cherry-picking and just merged gh-36 back into master instead.

oh whoops — thanks

oh whoops — thanks


How to solve mouse freeze / windows freeze / you can not click on any after playing around with interceptor?

If you tried to use input.MouseFilterMode = MouseFilterMode.All;
And everything worked but after that you could not use your mouse to click on anything?
The problem is caused by "Thread.Sleep".
If you are the one who use "await Task.Delay" instead to make a delay and never use the "Thread.Sleep", since the Thread.Sleep(x) will freeze your GUI for x millisecond, well, this is the solution for you.
Here is the things you can try:
Solution 1: Remove the Thread.Sleep in SendLeftClick() and SendRightClick() function - for those who didn't use the Thread.Sleep:
        public void SendLeftClick()
        {
            SendMouseEvent(MouseState.LeftDown);
            //Thread.Sleep(ClickDelay);
            SendMouseEvent(MouseState.LeftUp);
        }

        public void SendRightClick()
        {
            SendMouseEvent(MouseState.RightDown);
            //Thread.Sleep(ClickDelay);
            SendMouseEvent(MouseState.RightUp);
        }

Solution 2: Add "using System.Threading;" in your main code.

:| Easier
If you are using both keyboard and mice function of interceptor, then, just use 2 seperate Input for them:
Input input_mouse = new Input();
Input input_keyboard = new Input();

and do stuff separate like:
input_mouse .SendRightClick();
input_keyboard.SendKeys(Interceptor.Keys.A);

Also you may want to Load and Unload both:
input_mouse.Load();
input_keyboard.Load();
////
input_mouse.Unload();
input_keyboard.Uload();


Convert Storage Mappings screen to Console page

LGTM, some nitpicks, mainly using the new types :tada:
about the editing thing https://github.com/kubev2v/forklift-console-plugin/pull/186#discussion_r1105414327 not a blocker, but I would like to remove this things when/if we can.


Ambiguity between Reference Object and PathItem Object

Hi everybody, not sure if this is the right place to ask this, but I've intercepted an ambiguity while building tooling for OAS 3.1
{
  "openapi": "3.1.0",
  "components": {
    "pathItems": {
      "pathItem1": {
        "$ref": "#/components/pathItems/pathItem2",
      },
      "pathItem2": {
        "summary": "path item summary",
        "description": "path item description",
        "get": {}
      }
    }
  }
}

Given following document, pathItem1  can be interpreted either as Reference Object or Path Item Object. It's hard to tell what the author intended. He could have intended for pathItem1 to be a Reference Object. Or he may have intended pathItem1 to be a Path Item Object. As Path Item Object can have exactly the same shape as Reference Object the  intention of the author is lost.
Can you please advice how to approach that?
Instead of having this ambiguity and $ref field in Path Item Object, wouldn't it be cleaner to use Reference Object explicitly in every place where Path Item Object is allowed?
Current workaround could be assert the presence of $ref field and one of the other fixed fields from Path Item Object (like get, post, etc...). If assertion like that passes, we can say with limited certainty that author intended to define a Path Item Object.

I didn't notice this before. The schema doesn't validate this properly. It only allows for a Path Item Object (with no Reference Object properties) OR a Reference Object. A Path Item Object with Reference Object properties would fail validation.
What is the reason for including Reference Object properties in Path Item Object as opposed to just using a Reference Object? It's the only type that does that. It also doesn't seem very well specified. It doesn't specify how a reference works in this context, but implies that there differences from a normal Reference Object. A Reference Object has rules for merging "summary" and "description", but other properties are not merged in the referenced object. Path Item Object implies that some merging takes place, but doesn't specify how (e.g. deep or shallow merge). Is it assumed that Reference Object behaviors apply here unless otherwise specified? Do the merging rules for "summary" and "description" in a Reference Object apply?
As a workaround, I think you can always treat a $ref as part of the Path Item Object and never a Reference Object and always get what the user intended. If a Path Item Object only has Reference Object properties, it would evaluate the same as if it were a Reference Object. The only difference in processing it as a Reference Object is that any Path Item Object properties will be ignored. Since the user wouldn't include Path Item properties if they expected those properties to be ignored, we can be confident that if those properties appear, we should process it as a Path Item Object. I think that in all cases, processing it as a Path Item Object should result in the desired behavior.

@jdesrosiers it's an old remnant of version 2.0, where we allowed the reference without knowing back then that it cannot live alongside other properties. So back then (and now), it allows siblings and does not ignore them.
Granted, with 3.1, we could have used the current Reference Object and allow for siblings, but we didn't. It's one of the few places in the spec where the $ref is not JSON Schema Reference nor the Reference Object, but its own thing.

The schema doesn't validate this properly. It only allows for a Path Item Object (with no Reference Object properties) OR a Reference Object. A Path Item Object with Reference Object properties would fail validation.

So this technically means that if Object looks like a Reference Object, it will always be considered a Reference Object.

What is the reason for including Reference Object properties in Path Item Object as opposed to just using a Reference Object?

As @webron mentioned it's a remnant from older specifications, where components/pathItems fields did not exist and Paths Object only allows Path Item Object as a value of it's pattern fields. So including $ref field in Path Item Object was the only way ho reference another Path Item Object from Paths Object.

It also doesn't seem very well specified. It doesn't specify how a reference works in this context, but implies that there differences from a normal Reference Object. A Reference Object has rules for merging "summary" and "description", but other properties are not merged in the referenced object. Path Item Object implies that some merging takes place, but doesn't specify how (e.g. deep or shallow merge)

As the merging rules as undefined by the specification, tooling authors have to come up with something that makes sense. I've chosen the same merging rules as Reference Object and Schema Object follows. Fields from referencing object will shallowly override fields from referenced object.

Is it assumed that Reference Object behaviors apply here unless otherwise specified? Do the merging rules for "summary" and "description" in a Reference Object apply?

Acoording to this: Allows for a referenced definition of this path item. The referenced structure MUST be in the form of a Path Item Object. In case a Path Item Object field appears both in the defined object and the referenced object, the behavior is undefined. See the rules for resolving Relative References. the Reference Oject behaviors don't apply and the behavior is undefined.

As a workaround, I think you can always treat a $ref as part of the Path Item Object and never a Reference Object and always get what the user intended.

This would contradict the current schema validation. IMHO better way and possibly more forward compatible one would be to stay with the current validation and consider everything that looks like a Reference Object a Reference Object.

If a Path Item Object only has Reference Object properties, it would evaluate the same as if it were a Reference Object. The only difference in processing it as a Reference Object is that any Path Item Object properties will be ignored. Since the user wouldn't include Path Item properties if they expected those properties to be ignored, we can be confident that if those properties appear, we should process it as a Path Item Object. I think that in all cases, processing it as a Path Item Object should result in the desired behavior.

So if I understand this correctly, whenever there there is a choice between Reference Object | Path Item Object and the Object defines a $ref field, we should always consider it a Path Item Object. This will have an implication on fields merging as Path Item Object doesn't define it and every tooling author can choose how to define the merging. It is also not aligned with current schema validation.
I still think that this is problematic and opens door for unnecessary interpretations. In order to reduce the complexity and eliminate the ambiguity I propose following:

remove $ref field from Path Item Object
define a Type for Paths Object as this: Path Item Object | Reference Object

This small change will make things right in backward compatible manner.

So this technically means that if an Object looks like a Reference Object, it will always be considered a Reference Object.

Yes. If it has a $ref, the schema will consider it a Reference Object which means that it will be invalid if it contains any additional properties other than "summary" and "description". However, the schema is non-normative so it doesn't tell us how OpenAPI should behave. If the spec and the schema disagree, the schema is wrong.

I've chosen the same merging rules as Reference Object and Schema Object follows. Fields from referencing object will shallowly override fields from referenced object.

References in a Schema Object don't do any merging (not in any version of JSON Schema). Reference Object doesn't expressly specify a shallow merge, but I think the term "override" does imply a shallow merge.

whenever there there is a choice between Reference Object | Path Item Object and the Object defines a $ref field, we should always consider it a Path Item Object. This will have an implication on fields merging as Path Item Object doesn't define it and every tooling author can choose how to define the merging.

Right. This workaround only works if the tooling uses similar merging rules to Reference Object.

I still think that this is problematic and opens door for unnecessary interpretations.

I'm sure everyone can agree with that. I completely agree with your proposed changes.

References in a Schema Object don't do any merging (not in any version of JSON Schema). Reference Object doesn't expressly specify a shallow merge, but I think the term "override" does imply a shallow merge.

Right, there is only section of <IP_ADDRESS> which kind of defines what the behavior could be, and that behavior is aligned with OAS 3.1 Reference Object.

I'm sure everyone can agree with that. I completely agree with your proposed changes.

Should I push this forward by creating a PR with a proposed change?
Thank you for your time and all the answers!

From TDC call:
3.1.1 :  1) Remove the use of reference Object for WebHooks and Components/PathItems
2) Identify $ref  on its own as a ReferenceObject
3) Make PathObjects array of PathItem | ReferenceObject
4) Deprecate the use of $ref alongside other operation fields?
3.2.: 1) Remove $ref from PathItem fixed fields?
Should we continue to support "merging" PathItems?

@darrelmiller IMHO 3.1.1 - 1 and 3.1.1 - 3 contradict each other. If our aim is to remove $ref field field from Path Item Object in next breaking change release following steps seems like more appropriate:
3.1.1
The aim here is provide clarification to limit ambiguity

Clarification - Change Type Reference Object | Path Item Object in all places within spec to Path Item Object
Deprecate the use of $ref fixed field in Path Item Object

3.2.0
The aim here is to have only one referencing mechanism iwithing OAS 3.2 spec (reducing complexity) - Referece Object (JSON Schema spec has it's own $ref mechanism)

Remove $ref from Path Item Object fixed field
Change Type Path Item Object in all places within spec to Reference Object | Path Item Object

I've scanned ~200,000 OpenAPI document and apart from my test file, I've found precisely 3 occurrences of a pathItem object having a $ref and one or more operation objects (all OpenAPI 2.0).
All three files are exactly the same and are in test folders of the pyswagger/pyopenapi projects:

https://raw.githubusercontent.com/joequant/pyswagger/master/pyswagger/tests/data/v2_0/resolve/path_item/swagger.json
https://raw.githubusercontent.com/pyopenapi/pyopenapi/develop/pyopenapi/tests/data/v2_0/resolve/path_item/swagger.json
https://raw.githubusercontent.com/pyopenapi/pyswagger/develop/pyswagger/tests/data/v2_0/resolve/path_item/swagger.json

During the week I should have some numbers from SwaggerHub as well.

As discussed and agreed on TDC, I've issued a 3 PRs that fix the ambiguity in progressive steps between 3.1.1 and 3.2.:

https://github.com/OAI/OpenAPI-Specification/pull/2655
https://github.com/OAI/OpenAPI-Specification/pull/2656
https://github.com/OAI/OpenAPI-Specification/pull/2657

I didn't notice this before. The schema doesn't validate this properly. It only allows for a Path Item Object (with no Reference Object properties) OR a Reference Object. A Path Item Object with Reference Object properties would fail validation.

It's worse than that... the json schema does not allow for this document at all:
---
openapi: 3.1.0
info:
  title: ..
  version: ..
components:
  /foo:
    ...
paths:
  /foo:
    $ref: '#/components/~1foo'

Because the top level paths is defined as #/$defs/paths' which is an object of path-items, not path-items-or-references.  I think we could resolve all issues by letting /paths/` be an object of path-items-or-references, and amending the spec to match.

(for email readers: previous comment amended to fix typos)

Because the top level paths is defined as #/$defs/paths which is an object of path-items, not path-items-or-references. I think we could resolve all issues by letting /paths/ be an object of path-items-or-references, and amending the spec to match.

Would a PR to this effect be accepted?  I am encountering tooling errors when trying to use a $ref for a path-item that exactly duplicates another path-item (except for a different path template), because the schema document does not accept this, and the tool uses schema validation to parse the document.

Hello. When OAS 3.2.0 is released, could I use Reference Objects in Paths Object like below?
paths:
  $ref: foo.yaml
  $ref: bar.yaml

@gimbimloki whenever 3.2.0 is released, any syntax change won't involve duplicate keys as per your example, which have undefined behaviour in both JSON and YAML.

What's the status of this? It appears to have stalled just before execution of all the action items listed.

Because the top level paths is defined as #/$defs/paths which is an object of path-items, not path-items-or-references. I think we could resolve all issues by letting /paths/<path> be an object of path-items-or-references, and amending the spec to match.

I think that change would cover any real use cases, but I don't think it completely brings the schema in line with the spec. That change would not allow properties next to $ref other than description and summary (as defined by ReferenceObject), but the PathItemObject seems to allow any properties that are part of PathItemObject alongside the $ref (even tho it's undefined how to interpret those properties).
The get the specified behavior, I think we'd have to add $ref the PathItem schema and change path-item-or-reference to be use anyOf instead of if/then.


Add API to specify a file path for TLS certificates

It would ease usage if users could just specify a path to a certificate instead of requiring it be parsed first, such as:
let client = Client::builder()
    .certificate_file("/some/user/path")
    .build()?;

I'd be happier if the argument for this new API could be a std::fs:File instead of a path.
The reason is that (at least on Linux) a program can receive a file-like object as a file-descriptor from its parent or as a memfd from some peer. In both cases those file-objects have no corresponding file-system entries, thus a path-based API won't work without further workarounds.
Additional question: how does the current "pkcs12 vs pem" split fit here? Do you plan to have two separate helpers for those two cases?

Allowing to provide a File seems fine also. I think providing a path option is important, because otherwise everyone needs to import File and call File::open and etc, when we can reduce that boilerplate.
A couple options to support both:

Have 2 methods, certificate_file and certificate_path.
Or have certificate_file be generic over some sealed PathOrFile trait (naming is hard).

If we can easily try both PEM and DER without the user being bother, that's probably best...
What do you think?

As a consumer I prefer handling file opening on my side, but I think we just have a different API taste so I won't keep arguing this further.
On the format topic, the pkcs12 has an additional mandatory parameter (the password), and that's the reason why I was asking how you want to handle the two cases. I'm not seeing right now how to make auto-detection and password input work at the same time.

Oh right, for Identity...
Just thinking out loud here: following the thoughts in my previous comment, we could either:

Have multiple methods, one for PEM and one for DER.
Use a new trait such that we could pass File as PEM, and (File, &str) for DER.


Add tokio bindings

Fixes #20

While I love the idea of upstreaming this awesome tokio PulseAudio mainloop into libpulse_binding, would you be open to publishing a separate crate for others (like me!) to be able to depend on it and use it?
From my perspective - and correct me if I'm wrong @jnqnfe - this crate seems to be more of a 1:1 binding between PulseAudio's APIs rather than "a bunch of rust tools and integrations for PulseAudio". So to me, a separate crate makes sense for what is essentially "a tokio implementation of a PulseAudio mainloop".
TL;DR: I would love it if the libpulse-tokio crate added in this PR could be published to crates.io. Whether that's by upstreaming here, or by publishing it separately.

@acheronfail - I just published the current version of this branch. While it still has a few limitations, those can be fixed in future versions. I'd be open to adding the maintainers here to the crate if it was merged, so it could be maintained/released in lock-step.

I just published the current version of this branch.

On crates.io? I couldn't find it.

https://crates.io/crates/libpulse-tokio

Thank you, I don't know why neither crates.io nor lib.rs could find it :(


RDKTV-16992: Added timeout and synchronisation when stopping containers

Reason for change: It was possible for successive calls to DobbyContainer::Stop
to be made due to the WPEFramework not being notified quickly enough
that a container had stopped.
This change implements the missing timeout functionality
within that method to prevent the opportunity for quick multiple calls.
When the timeout is zero this method behaves as previous.
Test Procedure: Stop containers with zero and non-zero timeouts and
ensure there are no occurrences of containers being stopped multiple
times.
Risks: Low
Signed-off-by: Will Tallentire<EMAIL_ADDRESS>

@pwielders In DobbyContainer::~DobbyContainer(), there is a Stop(Core::infinite), which does not make much sense as this could cause a hang. Passing zero instead would make the Stop method work as it did previously before this change. Would there be any objection to changing this to zero or a reasonable timeout value, and do you know where else this Stop method may be called?


[FEAT] Remove GraphQL and @ngrx dependency requirements from main lib packages

:bulb: Feature request
Feature Name

Daffodil Subpackaging
The Desired Behavior

When I require a subpackage such as @daffodil/contact/driver/hubspot, I don't want to be forced to install additional deps such as @ngrx or graphql unless I actually need them.
Your Use Case

As a developer, I would like to use Daffodil drivers without unecessary deps such as the state library.
As a developer, I would like to reference Daffodil models without pulling in unnecessary deps such as the state library or drivers.
Others:

In the pursuit of being as modular as possible, we should separate the different layers of Daffodil into separate packages. This will prevent unnecessary dependencies as well as enforce layer decoupling.

Closed buy #1091


(WIP) sct_process_segmentation: Major refactoring to bring few improvements (Warning: cross-compatibility broken with v3.2.2)

Description of the Change
Long overdue improvements on sct_process_segmentation, including:

single csv output (removed support for txt, xls and pickle, which can easily be generated with csv)
flag -ofolder (output folder) replaced with -o (output file). Fixes #1789
compute_csa: nifti volumes for CSA and ANGLE are no more output because nobody uses it (I think). The code is still there and could manually be activated (global variable at the beginning of the code)
now possible to output CSA values per slice (flag: -perslice) and per level (flag: -perlevel), as recently introduced in sct_extract_metric (see: https://github.com/neuropoly/spinalcordtoolbox/pull/1875). Fixes #1920
Clarified document about how CSA is computed. Fixes #1841
Removed feature that smoothes CSA along z, because (i) this feature could be dangerous if not properly understood (e.g. subtle compression can be missed if large smoothing kernel is used) and (ii) easy to apply smoothing subsequently from the output csv file. Indirectly fixes #718.

JULIEN TODO:

Default flags are now explicit in the usage. Fixes #1589
Compact slice and vert level information in output csv file. Fixes #1932
Adapt perlevel/perslice fix to compute_shape()
create a spinalcordtoolbox.process_segmentation module that would be called by sct_process_segmentation.main()
Add tests

@perone: agreed about the -ofolder

In relation with #1875 and #1920, I would like to externalize a function inside a spinalcordtoolbox module to do this: https://github.com/neuropoly/spinalcordtoolbox/blob/jca/1920-process_seg-csa-perslice/scripts/sct_process_segmentation.py#L820
Do you have any suggestion how to best call this module? output_metrics? or should it be part of an already-existing module?

I think we should have a new module inside the spinalcordtoolbox package called metrics where we implement the metrics (Dice, etc) in the most generic way as a documented Python API, so it will follow the refactoring idea.

Regarding the -o flag option, I suggest it is used for file name without extension, and the extension would be added based on the process being run. Example with -o xxx:

centerline: xxx.csv (centerline coordinates as csv), xxx.nii.gz (centerline as binary nifti volume). Default: xxx=centerline.
label-vert: xxx.nii.gz (labeled segmentation). Default: xxx=fname_seg with suffix "_labeled"
csa: xxx.csv (output csa values). Default: xxx=csa

other flags: -csa_volume xxx.nii.gz and -angle_volume xxx.nii.gz

shape: xxx.csv (output shape). Default: xxx=shape
length: xxx.csv (spinal cord length). Default: xxx=cord_length

before i move forward i would like some feedback on the way the outputs of sct_process_segmentation are handled. In the current approach, there is a new module and function metrics.average_per_slice_or_level() that will take as input a list of vectors, that represent metrics (e.g., CSA, shape features, etc.) for each slice, and aggregate those metrics across slices or vertebral levels (as specified by the user). This module also deals with csv output. Note that this module could ultimately replace similar code in sct_extract_metrics().
I would like to know if this approach for dealing with slice-wise metric output is the right one, or if we should instead use another approach and/or recent developments (e.g. Slicer).

thank you for your comments @zougloub. In response to this, we are talking about the first scenario (i.e. group already-computed metrics across slices/levels).
i am now thinking that the name of the module should be more specific, e.g., aggregate_slicewise.average_per_slice_or_level()


fix(EG-726): pages not following tab value provided in query param

@CodiumAI-Agent /describe
--pr_description.extra_instructions="
For the title, use the format [type]: [summary]
"
--pr_description.generate_ai_title=true
--pr_description.final_update_message=true

Title
Bug fix and enhancement for tab navigation and lifecycle hooks

PR Type
Bug fix, Enhancement

Description

Fixed the issue where pages were not following the tab value provided in the query parameter by setting tabIndex based on query parameters.
Refactored code to remove redundant functions and simplify lifecycle hooks.
Corrected the back button navigation to ensure it directs to the correct lab page.
Improved the navigation logic when clicking on a lab row.

Changes walkthrough 📝
Relevant filesBug fix

index.vueFix tab index initialization and back navigation

packages/front-end/src/app/pages/labs/[labId]/[workflowId]/index.vue
Changed tabIndex to a reactive reference and set it based on query parameters.  Removed redundant function merging and simplified tab index initialization.  Updated back action to navigate to the correct lab page.

+9/-17

Enhancement

index.vueImprove tab index handling and lifecycle hooks

packages/front-end/src/app/pages/labs/[labId]/index.vue
Set tabIndex based on query parameters.  Simplified onBeforeMount lifecycle hook.  Removed redundant watch for route changes.

+8/-13

index.vueSimplify lab row click navigation

packages/front-end/src/app/pages/labs/index.vue

Refactored onRowClicked function to simplify navigation logic.

+3/-8

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information


Fixes #959

Problem:
Python 2.6 on Travis is depracated
Analysis:
We drop testing for python 2.6 on Travis with this patch, also previous disabled properties method is enabled
Tests:
Unit
Flake8

hmm this does not do what I would expect it to

bounced this to see if the test is skipped, as it should run, and python 2.6 testing should not be executed

i like to live on the edge, so I am merging this :) feel free to frown upon later (for disabling py 2.6)


New SIP010 token not selectable in send form yet displayed under balances

Quote from Chan at ALEX:
_Hi Mark and @kyranjamie we recently deployed sUSDT (the wrapped USDT) on mainnet, but at the moment I am unable to select from the Hiro wallet to send (it does not appear on the "Choose asset", while I can see it under "Balances").
Would you please take a look?
The deployment address is https://explorer.alexlab.co/txid/SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-susdt?chain=mainnet
Also, it's not picking up sUSDT's metadata (https://cdn.alexlab.co/metadata/token-susdt.json)_
@aalksnv#6998 recently added a fix so tokens of which metadata is not loaded would still be selectable. https://github.com/hirosystems/wallet/pull/3540
The token contract was deployed two days ago, seems ample time for it to get picked up by the new indexing service https://github.com/hirosystems/token-metadata-api
Is a metadata update notification required before the service picks it up?

@rafaelcr thoughts on whether this might be an API-related issue?

@314159265359879 @markmhx the orphan blocks are affecting our ability to pick up new contracts (we might miss some of them), so I'm going to be refreshing this contract manually ASAP. Will let you know when it's updated.

Actually, I checked the logs and the API did detect the contract but the metadata JSON was unreachable at the time. I've refreshed it and it works now: https://api.hiro.so/metadata/ft/SP3K8BC0PPEVCV7NZ6QSRWPQ2JE9E5B6N3PA0KBR9.token-susdt
Closing this issue