Connect Cockpit Diabetes App to Trio Directly - by Lukas Schuster (@schusterlich)

From Lukas Schuster @schusterlich (primary dev of Cockpit) to connect Trio data directly to Cockpit without going through Apple Health. Doing so will enable Trio users to access the premium membership for free to view their Trio data and data analysis in Cockpit.
what needs to be done is:
Check if the App is Installed:
In the app that is calling your custom URL scheme, you need to first check if your app can handle the URL. This can be done using the canOpenURL: method of UIApplication. This method returns a Boolean indicating whether or not your app can handle the URL scheme.
Code-Snippet:
if UIApplication.shared.canOpenURL(URL(string: "diabetes-cockpit://")!) {
    UIApplication.shared.open(URL(string: "diabetes-cockpit://?activate=iaps")!, options: [:], completionHandler: nil)
} else {
    // App is not installed, open App Store link
    UIApplication.shared.open(URL(string: "[https://apps.apple.com/us/app/diabetes-cockpit/id1580577116")!](https://apps.apple.com/us/app/diabetes-cockpit/id1580577116%22)!), options: [:], completionHandler: nil)
}

Configure URL Schemes:
Make sure that the calling app has your custom URL scheme listed in its Info.plist under LSApplicationQueriesSchemes. This step is necessary for the app to check if your app is installed:
Code-Snippet:
 <key>LSApplicationQueriesSchemes</key>
<array>
    <string>diabetes-cockpit</string>
</array>

This will kind of end up looking like an in-app advertisement. But that aside; looking over the privacy policy, it collects quite a lot of data with which they can do quite much. If this (commercial? speaking of free memberships 'n all :)) app is integrated, even if the user has it installed: there should, if possible, probably be a prompt to ask if the user actually wants to enable sharing all data 1:1 to Cockpit? Doing so without clear question just because the user has Cockpit installed sounds like a potential problem as it concerns extremely sensitive private medical data.
Thing is: through Apple Health, you can control what the app can see (for example: if you only want it to see BG for stats, but that's it.). If it has full access to all data available in Trio: there's no such control other than the remaining Health-categories not collected within Trio. Would be careful adding integration and ensure the control of sharing data yes/no is on the side of this app rather than relying on the external app.

For me, this is exactly the same as adding Tidepool integration.   It needs to be disabled by default and enabled and setup by the Trio end user.

Agreed. No data sharing should be enabled by default at all.

Hey everyone :) Thanks for including me in the conversation!
Theresa and I discussed Cockpit and its benefits for more Loopers. Built with community support over the last 2 years, it’s specifically for Loopers. I put it on the official AppStore for better availability and safety, as it handles sensitive health data, and I’m personally liable. Transparency about data usage is crucial.
Since the app is for this community, I want to offer it for free to members. A simple way to enable this is through a community status, activated by the deep link Theresa mentioned. This grants free access to all usually paid features without requiring a direct data connection. Community status should maintain a 100% free app for the community. I oppose any data sharing without explicit consent and understanding, which would be illegal.
The easiest and safest path is using Apple Health, plus providing the deep link for activation, which contains no data.
There is an option to integrate data with Cockpit’s backend, but it requires significant effort and clear communication about data handling. Activating the community status would still be necessary. If you feel this is the best way of doing it, we can talk about it!
I’d ofc be happy about the visibility and if my work were useful to more people, which is why I created the project. If there are any concerns regarding data sharing, let’s talk about it. Nothing should be shared automatically; any sharing must be an informed opt-in decision and never required for free use of the app.
Thanks so much for investing your efforts into the community. Having worked in the diabets industry for 10y+ i can confirm you - its people like you that move the industry forward indirectly 🙌
TLDR:
I strongly oppose any data sharing without clear consent. Cockpit was created by the community, and I want to grant everyone free access to paid features. iAPS should not share any data by default. Theresa and I concluded that activating free access through a deep link is the easiest solution for now.
Have a good day/evening/morning :) - whichever timezone you sit in!
Best,
Lukas

On 15.05.2024, at 20:21, tmhastings @.***> wrote:
Agreed. No data sharing should be enabled by default at all.
—
Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/193#issuecomment-2113168895, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNQ3YEVG3Z56MXR5YUBEXLZCORUPAVCNFSM6AAAAABHYT7ZFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGE3DQOBZGU.
You are receiving this because you were mentioned.

Thanks for the feedback Lukas. Happy to entertain a discussion/air some of my personal concerns.
If there's going to be direct data sharing:
I oppose any data sharing without explicit consent and understanding, which would be illegal.
Thing is, that's typically the crux. Such things are covered by and governed in the Privacy Policy and thus if that was "clearly consented to" (though nobody reads that stuff, but that's on them.) when installing the app: consent is technically and legally pretty much already addressed prior to any such new integrations as proposed. But that doesn't mean people really understand the implication of linking even more data to it through Trio and stuff like that is honestly what concerns me the most. The policy states that the collected (medical) data may be shared with and/or sold to third-parties and be used for an array of commercial purposes, about which I personally feel integration with such commercial efforts should be avoided in FOSS-applications - especially those that handle extraordinary sensitive data such as Trio. (To be even more frank, if we want to actually keep it pure: Trio should probably include a warning with integrations such as Nightscout as well to warn users that (portions of) the data will leave the app and will be governed by the privacy policy of whichever company, person or organization hosts your Nightscout.)
If it does not concern direct data sharing from Trio to Cockpit but only an in-app button of sorts:
I personally don't really see the use of that. There's multiple apps for diabetes patients, such as yours, Sugarmate, Tidepool (though their app is more of an upload vessel, lol) but even Dexcom Clarity and whatnot. I personally feel that it's best to avoid de facto in-app advertisements to other apps unless it's really absolutely necessary and very useful. (And to be clear: I don't think your app is not useful, don't get me wrong - but an in-app button linking to your app wouldn't really add anything at all other than a link to a, from a grande perspective, random application). The data can be shared through Apple Health - with full control over the data you do/don't want to feed the app and extra terms set by Apple. Furthermore I'm concerned with a snowball effect: make such a button for one application and others come circling around to get the same treatment and all of course allegedly for the greater good of the loop community. (Which may me be good intentioned but may also be just a cashgrab in a nice wrapper :P You know how it can go sometimes. :)) Next thing you know there's all kinds of buttons to all kinds of apps, links to all kinds of services, etc. and if you don't then you get the discussion "why them but not me? :(" and so on and on.
Last but not least:
'Since the app is for this community, I want to offer it for free to members. A simple way to enable this is through a community status, activated by the deep link Theresa mentioned.'
If the primary drive behind this is to ensure members of the looping diabetes community can get a free membership, couldn't you just reverse this? :) Try to detect Trio, Loop or iAPS on the phone. Detected? Grant free membership. Not detected (anymore)? Do not grant free membership.
Ergo, TL;DR:

If it's direct data sharing, I think this should be handled with care (and thinking about it, I believe a warning should be placed with Nightscout and Tidepool integrations as well) and be explicitly opt-in on Trio's side as the app must be able to protect itself rather than relying on the third-party app to do the protecting of the data
If it's not direct data sharing: then at the end of the day its just an advertisement button for one out of many apps on the market (both free as well as paid) and I don't think it's wise to entertain that. The button then doesn't serve any purpose other than driving traffic to it. I don't want to deny you new users, but I also believe Trio and other FOSS apps should not be the place for this. But that is just that: my personal opinion.
If the whole point of this is just for giving away free memberships to users, detecting Trio, Loop or even iAPS from Cockpit would make more sense to me. (One place to alter the code, instead of 3 or more places to alter code. :))

Btw, I'm just one of the users and I'm just a single opinion. :) Maybe nobody else feels the same, maybe others think it's an absolutely fantastic idea and/or see no reason to think it could be harmful or become a nuisance eventually. But I'm very wary about integrating links to other apps; most notably commercial apps as it feels like a de facto advertisement then. On top of that, I greatly value proper privacy/data protection and the "consent" portion for data sharing is farrrrr too easily obtained to consider it an actually functional security barrier. :P
Oh and in this day and age I believe unfortunately disclaimers are necessary: this is nothing personal or specifically against you, your venture or your app. (I actually use your app and was one of the first beta testers. :P) Just a generic point of view and concern that doing this may open a can of worms long-term. :)

Hey Liroy & others,
Thanks for the quick response :)
Regarding "If there's going to be direct data sharing":
Part of your reasoning is why I did not suggest direct integration. It's important to keep people informed and have everything be opt-in instead of opt-out, with the opt-in being voluntary. Apart from that, I do generally think that explicit legal consent is a fair option for everyone.
However, I did not suggest direct integration anyway 😌
Regarding "If it does not concern direct data sharing from Trio to Cockpit but only an in-app button of sorts":
Fair point. This question hinges on whether you, as a team of maintainers, think there is value for people in this app specifically - and this is up to you.
Regarding "Last but not least":
Trying to detect other apps on the phone is strongly discouraged by Apple because this practice would allow apps from other big companies, like Instagram, to collect information on all installed apps on your phone. Even indirect detection via URL schemes would permanently kick you out of the app into the phone browser regularly. Hence, this is not a good solution for any user experience, and for very good reason.
Most importantly, I'm not here to convince you or sell you something. I'm here to offer what was thought could be a good addition of one project to the next. If the Trio community is not feeling it, that's totally fine with me, and we can leave it here. I’d rather everyone focus on creating value than get into lengthy discussions that pull people away from it :)
I'm happy to hear you personally seem to find value in Cockpit, and should you as a group feel that it would be a good addition to include the free pro version upgrade of Cockpit, I'm obviously happy about it, and I'm sure we can find a good and safe way of doing so.
Hope you have a good day! And thanks for the work you all do :)
Best,
Lukas

On 16.05.2024, at 00:06, Liroy van Hoewijk @.***> wrote:
Thanks for the feedback Lukas. Happy to entertain a discussion/air some of my personal concerns.
If there's going to be direct data sharing:
I oppose any data sharing without explicit consent and understanding, which would be illegal.
Thing is, that's typically the crux. Such things are covered by and governed in the Privacy Policy and thus if that was "clearly consented to" (though nobody reads that stuff, but that's on them.) when installing the app: consent is technically and legally pretty much already addressed prior to any such new integrations as proposed. But that doesn't mean people really understand the implication of linking even more data to it through Trio and stuff like that is honestly what concerns me the most. The policy states that the collected (medical) data may be shared with and/or sold to third-parties and be used for an array of commercial purposes, about which I personally feel integration with such commercial efforts should be avoided in FOSS-applications - especially those that handle extraordinary sensitive data such as Trio. (To be even more frank, if we want to actually keep it pure: Trio should probably include a warning with integrations such as Nightscout as well to warn users that (portions of) the data will leave the app and will be governed by the privacy policy of whichever company, person or organization hosts your Nightscout.)
If it does not concern direct data sharing from Trio to Cockpit but only an in-app button of sorts:
I personally don't really see the use of that. There's multiple apps for diabetes patients, such as yours, Sugarmate, Tidepool (though their app is more of an upload vessel, lol) but even Dexcom Clarity and whatnot. I personally feel that it's best to avoid de facto in-app advertisements to other apps unless it's really absolutely necessary and very useful. (And to be clear: I don't think your app is not useful, don't get me wrong - but an in-app button linking to your app wouldn't really add anything at all other than a link to a, from a grande perspective, random application). The data can be shared through Apple Health - with full control over the data you do/don't want to feed the app and extra terms set by Apple. Furthermore I'm concerned with a snowball effect: make such a button for one application and others come circling around to get the same treatment and all of course allegedly for the greater good of the loop community. (Which may me be good intentioned but may also be just a cashgrab in a nice wrapper :P You know how it can go sometimes. :)) Next thing you know there's all kinds of buttons to all kinds of apps, links to all kinds of services, etc. and if you don't then you get the discussion "why them but not me? :(" and so on and on.
Last but not least:
'Since the app is for this community, I want to offer it for free to members. A simple way to enable this is through a community status, activated by the deep link Theresa mentioned.'
If the primary drive behind this is to ensure members of the looping diabetes community can get a free membership, couldn't you just reverse this? :) Try to detect Trio, Loop or iAPS on the phone. Detected? Grant free membership. Not detected (anymore)? Do not grant free membership.
Ergo, TL;DR:
If it's direct data sharing, I think this should be handled with care (and thinking about it, I believe a warning should be placed with Nightscout and Tidepool integrations as well) and be explicitly opt-in on Trio's side as the app must be able to protect itself rather than relying on the third-party app to do the protecting of the data
If it's not direct data sharing: then at the end of the day its just an advertisement button for one out of many apps on the market (both free as well as paid) and I don't think it's wise to entertain that. The button then doesn't serve any purpose other than driving traffic to it. I don't want to deny you new users, but I also believe Trio and other FOSS apps should not be the place for this. But that is just that: my personal opinion.
If the whole point of this is just for giving away free memberships to users, detecting Trio, Loop or even iAPS from Cockpit would make more sense to me. (One place to alter the code, instead of 3 or more places to alter code. :))
Btw, I'm just one of the users and I'm just a single opinion. :) Maybe nobody else feels the same, maybe others think it's an absolutely fantastic idea and/or see no reason to think it could be harmful or become a nuisance eventually. But I'm very wary about integrating links to other apps; most notably commercial apps as it feels like a de facto advertisement then. On top of that, I greatly value proper privacy/data protection and the "consent" portion for data sharing is farrrrr too easily obtained to consider it an actually functional security barrier. :P
Oh and in this day and age I believe unfortunately disclaimers are necessary: this is nothing personal or specifically against you, your venture or your app. (I actually use your app and was one of the first beta testers. :P) Just a generic point of view and concern that doing this may open a can of worms long-term. :)
—
Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/193#issuecomment-2113530084, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNQ3YABJRX73UQZNNO5KM3ZCPL65AVCNFSM6AAAAABHYT7ZFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJTGUZTAMBYGQ.
You are receiving this because you were mentioned.

I think we should absolutely explore options that would let users more easily view and gain insight on their BG and treatment data to help reduce the burden of manually calculating this data. To me, that's the main part of the equation in automating treatment that's missing -- and that most users struggle with. Obviously we want to be cautious and transparent around privacy, but if you opt-in to make use of the data, that's the user's call. I hope we are not dismissing this idea out of hand. That is a mistake imo. Appreciate @tmhastings introducing this and @schusterlich's offer and thoughts on it as well.

Thanks for the kind response, im def happy to jump on a call!
Lets all grab a coffee or tea and have a chat :)?
Best,
Lukas

On 17.05.2024, at 17:44, Paul Heltzel @.***> wrote:
I think we should absolutely explore options that would let users more easily view and gain insight on their BG and treatment data to help reduce the burden of manually calculating this data. To me, that's the main part of the equation in automating treatment that's missing -- and that most users struggle with. Obviously we want to be cautious and transparent around privacy, but if you opt-in to make use of the data, that's the user's call. I hope we are not dismissing this idea out of hand. That is a mistake imo. Appreciate @tmhastings https://github.com/tmhastings introducing this and @schusterlich https://github.com/schusterlich's offer and thoughts on it as well.
—
Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/193#issuecomment-2117878248, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNQ3YCOUVALNI4NLPJBY5LZCYQWTAVCNFSM6AAAAABHYT7ZFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJXHA3TQMRUHA.
You are receiving this because you were mentioned.

hey 👋 - silence for 30 days 🤐 ... anybody? triage is required!

Let’s go! Would be cool to e-meet you for a coffee :)How does next week look for you?Best, LukasSent from my iPhoneOn 04.07.2024, at 03:12, Sjoerd Bozon @.***> wrote:
hey 👋 - silence for 30 days 🤐 ... anybody? triage is required!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Let’s go! Would be cool to e-meet you for a coffee :)How does next week look for you?Best, LukasSent from my iPhoneOn 04.07.2024, at 03:12, Sjoerd Bozon @.> wrote: hey 👋 - silence for 30 days 🤐 ... anybody? triage is required! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.>

We can arrange something, but after 1.0.0 Not at this moment. This was an automated message

Im flexible and open basically whole next week :), would be cool - timezone is Vienna Austria 😌.How are you all doing the last weeks?BestLukas!Von meinem iPhone gesendetAm 04.08.2024 um 04:24 schrieb github-actions[bot] @.***>:
hey 👋 - silence for 30 days 🤐 ... anybody? triage is required!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>

Can you share your emails then I setup a doodle for us to finally get this going 💪
Really looking forward to meeting the Trio Heros!
Best,
Lukas

On 04.08.2024, at 07:03, Lukas Schuster @.***> wrote:
Im flexible and open basically whole next week :), would be cool - timezone is Vienna Austria 😌.
How are you all doing the last weeks?
Best
Lukas!
Von meinem iPhone gesendet

Am 04.08.2024 um 04:24 schrieb github-actions[bot] @.***>:

hey 👋 - silence for 30 days 🤐 ... anybody? triage is required!
—
Reply to this email directly, view it on GitHub https://github.com/nightscout/Trio/issues/193#issuecomment-2267256320, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABNQ3YEZN7YPGZDJOO2SP43ZPWGHFAVCNFSM6AAAAABHYT7ZFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRXGI2TMMZSGA.
You are receiving this because you were mentioned.


Add bigger clearances on hot paths for more safety

Ahoi!
Nice design. I suggest adding a little bit more clearance to possibly hot pathways.
This (comprehensive and handy) list of safe and "deadly" AC->USB-converters shows a lot of examples on how to do it right (and how not):
https://lygte-info.dk/info/ChargerIndex UK.html
Here's a picture of a unit wich was tested against 4kV.
One trick is to use non-conducting material (e.g. hot glue) for isolation purposes, but this makes everything very messy.

Thanks for the hint and the link, I keep this issue open for a future revision C!


async_setup_platforms depreciated in HA 2023.3

Noted a warning in my HA logs regarding depreciation of async_setup_platforms failing in HA release 2023.3 onward. Thought it should be brought to attention in case it hasn't been noted yet.
Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 2:37:09 PM (1 occurrences)
Last logged: 2:37:09 PM

Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for ontario_energy_board using this method at custom_components/ontario_energy_board/__init__.py, line 21: hass.config_entries.async_setup_platforms(entry, PLATFORMS)

Same issue here.

Any updates here? Error persists in 2023.4x

Same here...any updates?

This is now fixed with v0.3.3


How can I ensure my request URL isn't encoded?

I want to make a request from a string. I don't want it encoded whatsoever, I'd like request to make a request to the string I provide without modifying it whatsoever. Is this possible?

Your URL string is parsed using the url module. You can pass such object to request:
var u = url.parse('string')
// modify some properties of u
// then pass it to request
request({uri:u})

A short code example that reproduces the behavior you expect may be helpful as well.

@AlexChesters this may help you https://github.com/request/request/issues/1678#issuecomment-121914470

I am faced with the exact same situation.
I do call request like:
request({
  url: model.url,
  method: model.method,
  strictSSL: false
})

it works the most time, but at one url it just encodes and the server answers with something like:
The requested URL "/********" , is invalid.
I can not figure out why... Can someone help me out with this issue?

Fixed. Thanks.


Version History screen: UI issue

img is cutting from left side.

Verified this issue on keeper app v 1.1.13(314)


forward/back navigation buttons: text overflows the button

On some pages the text overflows the forward/back button, for example here: https://train.oxrse.uk/material/HPCu/software_architecture_and_design/procedural/arrays_python

closed by #236


index.xsd:26-28: Index.xsd: add xsd:documentation tags...

The puzzle 134-9a3b0d90 from #134 has to be resolved:
https://github.com/yegor256/jpeek/blob/0d4a79106f05652d4c5874638278262b31a8177a/src/main/resources/org/jpeek/xsd/index.xsd#L26-L28
The puzzle was created by rultor on 19-Feb-18.
Estimate: 30 minutes, role: IMP.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@yegor256/z please, pay attention to this issue

Job #199 is now in scope, role is DEV

@0pdd all puzzles are solved

@0pdd all puzzles are solved

@robsonataide/z this job was assigned to you 5days ago. It will be taken away from you soon, unless you close it, see §8. Read this and this, please.

The user @robsonataide/z resigned from #199, please stop working. Reason for job resignation: It is older than 10 days, see §8

Resigned on delay, see §8: -30 point(s) just awarded to @robsonataide/z

The job #199 assigned to @serranya/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

The user @serranya/z resigned from #199, please stop working. Reason for job resignation: It is older than 10 days, see §8

Resigned on delay, see §8: -30 point(s) just awarded to @serranya/z

The puzzle 134-9a3b0d90 has disappeared from the source code, that's why I closed this issue.

@0pdd the puzzle #282 is still not solved.

Job gh:yegor256/jpeek#199 is not assigned, can't get performer

The job #199 is now out of scope

@0crat pay @Serranya 30min

@0crat pay @Serranya 30min (here)

@paulodamaso Argument "@Serranya" doesn't match regex \d+min

@0crat pay 30min @Serranya

@0crat pay 30min @Serranya  (here)

@paulodamaso The project is under-funded, you can't do it now, see §49

@paulodamaso/z please, pay attention to this issue

@0crat assign @Serranya

@0crat assign @Serranya  (here)

@paulodamaso The job #199 assigned to @serranya/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be no monetary reward for this job

Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @paulodamaso/z

Job was finished in 0 hours, bonus for fast delivery is possible (see §36)

The job #199 is now out of scope

Order was finished: +35 point(s) just awarded to @serranya/z

@0pdd the only puzzle #282 is solved here.


groupshared improvement discussion

This is a general issue I wanted to file to encourage open discussion about future improvements to groupshared LDS/shmem usage and allocation.
Problem Discussion
This is unlikely exhaustive, but here are the problems that are likely to crop up for users of groupshared memory (I will use groupshared, LDS, and shmem interchangeably).

LDS allocation usually scales linearly with the number of waves in a thread group, however, because WaveGetLaneCount is not a compile-time constant, the wave size cannot readily be used in a groupshared declaration. The current workaround for this is to either make (bad) assumptions about the wave size, or produce multiple specializations of each shader and dispatching the correct one with a matching WaveSize at runtime. Neither option is ideal, with the former resulting in brittle hardware-specific code, and the latter resulting in build and runtime complexity.
Currently, groupshared data must be declared in the global declaration context. This impedes code composability -- for example, if we wanted to include a header to use a function defined in that header, we may hurt occupancy by inadvertently dragging along groupshared declarations. This is a real footgun in larger (and sometimes smaller) codebases, and it is difficult to detect when it occurs (or at least, it takes some work to understand why occupancy is lower than expected).
Along the same vein of code composability, LDS memory usage must interact directly with the groupshared variable as declared, due to the lack of a user-accessible ref function parameter qualifier. A function that operates over some input data and exports output data cannot always rely on "copy-in" and "copy-out" semantics, because the in and out semantics do not permit usage of the various Interlocked* functions (which internally are modeled using ref-qualified parameters)

Possible Solutions
If possible, I think there are a few things that would immediately improve quality-of-life for compute shader authors. These suggestions are written from the perspective of an ISV (the shader writer), and it's understood that other solutions may end up being preferable due to practicality, performance, ease-of-implementation, or all of the above from the perspective of a hardware vendor or DXC compiler implementer.

Permit the use of WaveGetLaneCount in the declaration type for groupshared storage.
Permit local variables to be declared as groupshared.
Add a ref keyword that would permit use of Interlocked* intrinsics for ref-qualified parameters

The first item would allow developers to conceptually treat WaveGetLaneCount as a constexpr function, whose value is realized only when a PSO is actually created at runtime. This has implications beyond LDS allocation, but would be a very useful tool in the toolbox for other use cases.
For the second item, because functions are still fully unrolled currently, the total storage needed per-thread-group for a given compute shader should still be statically known, although DXIL may require modifications to properly alias types allocated from the virtual shmem pool. The idea here is that a static analysis pass would determine the amount of LDS memory needed in the "middle swell" of the program, accounting for all possible branches taken where groupshared variables are declared.
The counterargument to the second item is that statically knowing how much LDS is used precludes future HLSL code in a world where function calling is possible. At this point, one option would be to permit functions to allocate LDS (similar to alloca) using the same semantics as locally declared groupshared variables. The driver would need to be able to suspend thread groups if LDS isn't available, or possibly demote allocated LDS to slower vram (possibly from a fixed size pool of reserved memory).
The last item addresses the ability to perform operations on memory in LDS, regardless of where or how that LDS memory was allocated.
All that said, my main goal is to encourage discussion, and not attempt to be overly prescriptive about the solutions. I think starting from a well-defined problem statement is likely step one.

@jongreenberg-ea mentioned a related issue filed against DXC w.r.t. groupshared usage and WorkGraphs, with similar suggestions: https://github.com/microsoft/DirectXShaderCompiler/issues/5618
I think this raises a good point, code composability issues are exacerbated in a world with work graphs.

Along the same vein of code composability, LDS memory usage must interact directly with the groupshared variable as declared, due to the lack of a user-accessible ref function parameter qualifier. A function that operates over some input data and exports output data cannot always rely on "copy-in" and "copy-out" semantics, because the in and out semantics do not permit usage of the various Interlocked* functions (which internally are modeled using ref-qualified parameters)

the way we solve that is via an Accessor pattern, basically every algorithm we have takes a stateful-lambda to access whatever memory it needs.
There's a funny bug in codegen in DXC which causes inout to work exactly like a reference, we've tried it in SPIR-V for atomics, an issue was opened about it at one point.

Permit local variables to be declared as groupshared.

in spir-v land there's a capability/extension SPV_KHR_workgroup_memory_explicit_layout which allows you to alias multiple shared variable declarations (or just generally set the offset).

the way we solve that is via an Accessor pattern, basically every algorithm we have takes a stateful-lambda to access whatever memory it needs.

I don't think this relevant to this proposal, which I would rather keep to a minimal surface area if possible (lambdas feel like an entirely separate matter, which would require some form of reference semantics anyways).

in spir-v land there's a capability/extension SPV_KHR_workgroup_memory_explicit_layout which allows you to alias multiple shared variable declarations (or just generally set the offset).

This is probably more relevant to the proposal related to union support.

I don't think this relevant to this proposal, which I would rather keep to a minimal surface area if possible (lambdas feel like an entirely separate matter, which would require some form of reference semantics anyways).

Functor structs, a.k.a. the precursors to C++11 lambdas, work just fine for us.

Voila: https://godbolt.org/z/9qso3Y7eW
see it emits:
        %107 = OpAtomicIAdd %uint %particleCount %uint_1 %uint_0 %uint_1

its a codegen bug, but it works... for now

That isn't what I asked for unfortunately -- I thought it was pretty obvious I was replying to your somewhat snarky "work just fine for us" comment. As for the codegen bug, obviously this should not be relied on, and is better discussed as an actual DXC issue, and seems specific to the SPIR-V backend?

That isn't what I asked for unfortunately -- I thought it was pretty obvious I was replying to your somewhat snarky "work just fine for us" comment.

Well its not my fault if you can't ask the question plainly and clearly.

Also look, same function takes either shared or RWStructuredBuffer
https://godbolt.org/z/1j3hczKcT

Well its not my fault if you can't ask the question plainly and clearly.

If you scroll up, I am replying directly to this claim:

Functor structs, a.k.a. the precursors to C++11 lambdas, work just fine for us.

I'm not particularly interested in engaging in further discussion with you further but with respect to:

Also look, same function takes either shared or RWStructuredBuffer
https://godbolt.org/z/1j3hczKcT

Yes, obviously you can modify the snippet to exploit the same codegen bug, but this is not the same as demonstrating a working snippet working within intended language semantics using your functor struct method.

working snippet working within intended language semantics using your functor struct method

I have a whole library of them.
Write exactly what you want and I can give you an example.

There's a funny bug in codegen in DXC which causes inout to work exactly like a reference, we've tried it in SPIR-V for atomics, an issue was opened about it at one point.

DO NOT rely on this. If you do your code will break in the near future. I have a draft PR to fix this issue in the SPIR-V code generator and fix a bunch of related issues in the DXIL code generator (https://github.com/microsoft/DirectXShaderCompiler/pull/5249). The PR is currently blocked on resolving some related issues with matrix orientation annotations, but we are hoping to get both of those fixes into a DXC release this fall.

Functor structs, a.k.a. the precursors to C++11 lambdas, work just fine for us.
...
Well it's not my fault if you can't ask the question plainly and clearly.
...
There's already a DXC issue, but unlikely to get "fixed" until references are in.

@devshgraphicsprogramming, some of your comments on this thread (and others), are pretty snarky and contain non-productive language. I think you've brought up a lot of great feedback across these discussions, but it would be better if you could restrain the snark.
This project (and DXC) are both governed under the Microsoft Open Source Code of Conduct, and some of your comments here are getting awfully close to crossing into unacceptable territory. I ask that you please focus on being kind, respectful and constructive in your comments.

Functor structs, a.k.a. the precursors to C++11 lambdas, work just fine for us.
...
Well it's not my fault if you can't ask the question plainly and clearly.
...
There's already a DXC issue, but unlikely to get "fixed" until references are in.

@devshgraphicsprogramming, some of your comments on this thread (and others), are pretty snarky and contain non-productive language. I think you've brought up a lot of great feedback across these discussions, but it would be better if you could restrain the snark.
This project (and DXC) are both governed under the Microsoft Open Source Code of Conduct, and some of your comments here are getting awfully close to crossing into unacceptable territory. I ask that you please focus on being kind, respectful and constructive in your comments.

Sure thing, its a street that goes both ways.
I can obviously see what's wrong with my second comment as I was obviously unkind, I don't get the issue with the first and the last.
I'm not poking fun at anyone by using "fixed" in quotation marks, I'm just conveying that I like it being "broken" :D
This has nothing to do with the quality of #5249 , my opinion of it or anything like that.


[WIP]add base frontend

Thank you for submitting a pull request! Please provide the following information for code review:
Pull Request Summary
[TODO] add base frontend and HParam.  #61
Test Plan
[TODO] python hparam_test.py

analyfilterbank using for extract power spectrum and phase.


Fix pythonPackages.sounddevice and upgrade 0.3.12 -> 0.3.13

Motivation for this change
v0.3.12 was broken because the outdated patch didn't apply anymore.
I upgraded it to 0.3.13 and updated the patch.
Fixes #59909
Should probably be backported to 19.03.
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Backported in 9d09f02f1161272bcdae97f4b5835b9a097fd281


Bump to LoweredCodeUtils 2.4

Control-flow analysis changed considerably  in LoweredCodeUtils 2.4
(xref https://github.com/JuliaDebug/LoweredCodeUtils.jl/issues/87).
This updates to the new version. The overall trend is less
reliance on norequire as a way of blocking certain "bad"
statements, instead attempting to discover minimal statements
purely by their dependencies.
Fixes #587

Any thoughts on moving strongly_connected_components to LoweredCodeUtils? It seems likely to be useful there too.

Hmm, those OutOfMemoryError errors are not promising. From browsing the history of CI they don't seem typical, so perhaps this change is causing them 😢

Likely https://github.com/JuliaDebug/LoweredCodeUtils.jl/issues/96

Thanks for the update! I had been delaying the LCT update, so this is very helpful.

The overall trend is less
reliance on norequire as a way of blocking certain "bad"
statements, instead attempting to discover minimal statements
purely by their dependencies.

I believe this is a positive trend.

Any thoughts on moving strongly_connected_components to LoweredCodeUtils? It seems likely to be useful there too.

Absolutely! This is code I originally adapted from LightGraphs.jl a while back. While it doesn't have its own unit tests, it has been bug-free in JET's functionality so far. I'll review the most recent code from Graphs.jl and then attempt to create a PR to LCU.

Well, at least we don't get out of memory errors. I don't have time to dig into the failures any more today but I am interested in figuring out why things are failing, it could reveal further issues with LCU's current strategy.

Would be nice to get this to hopefully unbreak JET on Julia master (at least it needs a newer LCU for master, not sure if that's already sufficient)


Not Translating In wordpress

I am trying to translate my wordpress site into Italian language. I have created a Italian language file using poedit and I moved the po and mo files into my site , but the contents were not translated. Kindly can you please help me to solve this issue

This is a bug tracker, not a forum for idle questions. Please don’t add noise to it. The support page you came from explained this to you and mentioned that you should only use GitHub if you have experience with this stuff.
Also, it’s entirely inappropriate for you to email the support contact and one minute later create a duplicate issue for the same thing. Please don’t do this.


[BUG]Online cellpose failed to upload image

Now, the online cellpose failed to upload the image. The image meets the size type, but after loading, it cannot jump to the next submit page. Attempted to use images that were successfully segmented before, but also failed to load.
May I ask what the problem is？

sorry please try again now


Send Feedback Modal

Is your feature request related to a problem? Please describe.
From time to time, I see people having problems with Odysee or feedback on what they don't like, bugs or what they would like to get implemented.
Describe the solution you'd like
I would like to suggest a feedback modal that can be reached through the profile menu, this feedback modal allows to directly send feedback to Odysee Team like<EMAIL_ADDRESS>does. (pretty much just a email form that auto fills user account email)
The advantage is that there is less of a barrier to reach out to Odysee and a feedback modal can also automatically screenshot the page, send it with the feedback message, and there is a connected account email in every message.
Some might contact<EMAIL_ADDRESS>with some email they're not using on Odysee that makes it harder to resolve issues, this form would solve that.
The feedback modal link / button could be implemented on all the places where the support mail is liked right now, so people can easily reach out and report what they don't like.
Describe alternatives you've considered
E-Mail support is alright, but there will always be people that will not report because it's too much work for them to write a proper mail, but would choose to report using a modal.
Additional context
On YouTube, it looks like this:

There's one on the help page for now, but this would be nice eventually with a way to track (maybe slack hook,.etc)

We can consider integration here: https://docs.sentry.io/platforms/go/guides/echo/enriching-events/user-feedback/


General plotting scripts

[x] dataMC comparison
[x] shape comparison
[x] systematic errorband
[ ] non-uniform rebinning

Also the --debug option is broken. I tried to fix it with my PR#8 but not successful. Could you please take a look as well (starting from my PR).


Ci

Codecov Report
Patch coverage: 1.79% and project coverage change: -0.24% :warning:

Comparison is base (ddfcd80) 2.51% compared to head (1bda1ea) 2.27%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff            @@
##            main     #22      +/-   ##
========================================
- Coverage   2.51%   2.27%   -0.24%
========================================
  Files         10      10
  Lines       1312    1404      +92
  Branches     218     243      +25
========================================
- Hits          33      32       -1
- Misses      1276    1367      +91
- Partials       3       5       +2

Files Changed
Coverage Δ

etpclient/etp/etp_data_bridge.py
0.00% <ø> (ø)

etpclient/etp/etp_notifyer.py
0.00% <0.00%> (ø)

etpclient/etp/h5_handler.py
0.00% <0.00%> (ø)

etpclient/etp/hsds_bridge.py
0.00% <ø> (ø)

etpclient/etp/requester.py
0.00% <0.00%> (ø)

etpclient/etp/serverprotocols.py
0.00% <0.00%> (ø)

etpclient/main.py
0.00% <0.00%> (ø)

etpclient/websocket_manager.py
0.00% <0.00%> (ø)

etpclient/utils.py
20.91% <33.33%> (-0.52%)
:arrow_down:

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


Added VS Code icons to files.

Added extensions.json and settings.json as VS Code files.

Please do not modify this file. Go ahead into the build directory, there is a file called supportedExtensions.js Please add it there, thanks 😃

settings.json is not only a vscode related file so I think it shouldn't be changed.
extensions.json could follow the same rationale, but I'm not as certain.

I would directly close this PR. What do you think @jens1o, @JimiC?

I agree with your reasoning. settings.json isn't in any way affiliated with vscode.

I agree, too. Closing this.


⚠ Bofrost.at has degraded performance

In b94826d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1238 ms

Resolved: Bofrost.at performance has improved in bb3da4e after 15 minutes.


being to turn off the highlight of a star

it keeps running until we pick another one.
Have to be able to turn it off

I set the number of rotations at 30 max so the highlight will turn off after 30 rotations


api/client: handle LogPostResponse messages

I ran into this while working on brimdata/rug#208.

Once #2668 is merged, service/ztests/s3/postpath-s3.yaml, service/ztests/zapi/postpath-errors.yaml, service/ztests/zapi/postpath-shape.yaml, and service/ztests/zapi/postpath-warnings.yaml will provide coverage for this.


(AzureCXP) fixes MicrosoftDocs/azure-docs-powershell#1323

Better clarifying which service principal ID needs to be used.

Docs Build status updates of commit ff83559:
:clock10: Full build: the average full build time is 22 min(s) 59 sec(s), this is based on the last 309 build(s) for this repository.

Docs Build status updates of commit ff83559:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-3.5.0/authenticate-azureps.md
:white_check_mark:Succeeded
View (azps-3.5.0)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


poppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablePoppler error creating document

Got this error while parsing pdf
('read pdf file', 'astro-ph0606002.pdf')
poppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't find trailer dictionarypoppler/error: Couldn't read xref tablePoppler error creating document

As with the other issue you filed, it works fine here. You are probably using very old libraries, in which case there's nothing I can do.


Cannot find it on HACS

Just got my Alpha ESS Battery and Solar system installed and was keen to add it into Home Assistant.  I cannot find it on in HACS.  Has it been removed?

How have you tried?
HACS > Integrations > Hamburger Menu > Custom Repositories add https://github.com/CharlesGillanders/homeassistant-alphaESS with category set to integration.

Perfect.  Thanks.
I wasn't adding it as a custom just searching in HACS.
Thanks for your help and all your good work.
On Sun, Apr 2, 2023 at 12:05 AM Spookster @.***> wrote:

How have you tried?
HACS > Integrations > Hamburger Menu > Custom Repositories add
https://github.com/CharlesGillanders/homeassistant-alphaESS with category
set to integration.
—
Reply to this email directly, view it on GitHub
https://github.com/CharlesGillanders/homeassistant-alphaESS/issues/69#issuecomment-1493165114,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALD55JXT75O3M2MWHFOFJFTW7CRENANCNFSM6AAAAAAWP4RVQY
.
You are receiving this because you authored the thread.Message ID:
@.***>

Perfect. Thanks. I wasn't adding it as a custom just searching in HACS. Thanks for your help and all your good work.
…
On Sun, Apr 2, 2023 at 12:05 AM Spookster @.> wrote: How have you tried? HACS > Integrations > Hamburger Menu > Custom Repositories add https://github.com/CharlesGillanders/homeassistant-alphaESS with category set to integration. — Reply to this email directly, view it on GitHub <#69 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALD55JXT75O3M2MWHFOFJFTW7CRENANCNFSM6AAAAAAWP4RVQY . You are receiving this because you authored the thread.Message ID: @.>

I just discovered I was doing the same!


spie sprint

This Issue will be used document and drive the experimentation discussed in SPIE
Description
A dirty implementation of our prostate methods using deep learining. The volumes would be sliced (as sub volume) in a sliding manner and a decision (cancer / non-cancer) would be made for each subvolume.
Tasks

[ ] basic caffe knowledge
[ ] Initial caffe integration

[ ] volume slicing

Extra- things to try

[ ] Incorporate a position prior. Maybe you can have T1, DCE, ADC (+ a modality position or atlas) see issue #5

[ ] use Atlas Prior
[ ] use position image [X, Y, Z] of size (MxNxRx3) where the central pixel has a 0,0,0

@glemaitre I think this is what we need https://github.com/BVLC/caffe/wiki/Model-Zoo#fcn

https://www.youtube.com/watch?v=rvMVqPsXL10 @ min 40, injecting rgb images + depth, either at the first level of the network (or more fancy, inject one of the images at some deeper layer within the network). We can use this to inject the DCE and the ADC at its corresponding resolution


Rearranged Postinst and prerm used for Python setting

Added a function call for python Library path setting
Function will be called in single Rocm setup
In Multi Rocm setup the function call will be stripped from package
User has to provide the library path to python via environmental variable in Multi ROCM setup

Do we need documentation and changelog updates? Do we need to update the version number?

There could be an update to the changelog, but I dont see a need to change the documentation(this is essentially doing the same thing from a user perspective).

There could be an update to the changelog, but I dont see a need to change the documentation(this is essentially doing the same thing from a user perspective).

That is true, but the PTH option appears to be undocumented at the moment.


Row handling in Parser?

@calebkleveter I'm using CSV to load data into a database and I'm combining onHeader and onCell to effectively build a row dictionary. Do you think that is a common enough use case to merit including something like an onRow: handler in Parser.swift?

Maybe? If you are doing that it might be worth using the async CSVDecoder it will decode rows to a decodable type. I think that would handle a lot of the work for you. Plus if you have a custom type that represents your database model, you can just decode to that.
let decoder = CSVDecoder().async(for: [String: String], length 1024) { row in
    database.insert(row)\
}

try decoder.decode(chunk)

Here are the API docs:

CSVDecoder.async
CSVAsyncDecoder

Closing due to inactivity. Feel free to re-open if you want to continue the discussion.


rubygems publishing?

The readme says to reference the repo.
Can this gem be versioned and published to rubygems.org?

@tc yes, we'll publish it soon. Hope you are still able to use the GitHub version meanwhile


#GH-30 Migrated from XMLHTTPRequest to using CSRF token

Summary
Migrated from XMLHTTPRequest to using CSRF token as the former will be depricated by Mattermost.
Checklist

[x]  Added or updated test cases
[x] make test Ran test cases and ensured they are passing
[x] make check-style Ran style check and ensured both webapp and server components comply the style guides

This fixes #30.


grammar.CFG.eliminate_start throws TypeError when a new start symbol is needed

The grammar.CFG.eliminate_start method throws TypeError: 'Nonterminal' object is not iterable when the original start symbol of the grammar appears on the right side of a production. This is exactly the case where this method does anything at all—for instance, this is the first step in converting a CFG to Chomsky normal form (see grammar.CFG.chomsky_normal_form).
This error is thrown because the new start symbol is used as the right side of a new production in the grammar, without being wrapped in an iterable as would typically be done. A simple solution is to replace
result.append(Production(start, grammar.start()))

with
result.append(Production(start, [grammar.start()]))

#2453


Updated

Now its more accessible for beginners with all details at one place.

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the deploy-to-heroku link in your pull request, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (eg. a "before and after video")

Thanks for the pull request. We are unable to accept this change at this time.


Allow HTTP links for localhost in documents and extension development

Currently, I'm developing an extension that can decorate strings with images rendered from a local server on demand. This requires the extension to provide HTTP links to the contentIconPath, but unfortunately, resources from HTTP links are not allowed in VSCode:

Setting up HTTPS for each local server is unnecessary in my opinion, as the localhost should only be accessed by the user, and only GET request is used. It would be helpful if HTTP can be allowed in just localhost or a configurable set of hosts.

@bpasero Adding you because I believe this is blocked by our workbench content security policy
Marking as a feature request to gauge interest


contrib_bots: Prevent runaway bots with rate limiting

It's possible to create a runaway bot if you have a bot send a message to certain stimuli that in turns becomes a stimulus for the bot to send another message and so on and so forth.
We can prevent that in contrib_bots/run.py by adding some logic to prevent runaway bots.
Right now RestrictedClient make self.send_message just be client.send_message, but we can instead have a wrapper like this:
def send_message(self, *args, **kwargs):
     self.rate_limit()
     self.client.send_message(*args, **kwargs)

And then have appropriate logic in rate_limit() and some state variable to make sure less than N messages have been sent in the last second.  It might make sense to have a small class for rate limiting that RestrictedClient uses an instance of.
You can do a pretty naive rate limiting scheme where you just keep the last N timestamps in a Python list and truncate it off the front as new sends come in and the list grows to size N+1.

Working on this :)


Offline Mixin to extend ActiveModelAdapter

Hi,
I am using Active-Model-Adapter (https://github.com/ember-data/active-model-adapter) with Ember-Data, therefore I do not want to extend my application adapter with baseAdapter from ember-data-offline.
Is there a way how can I include some mixin that will extend my application adapter like the following:
export default ActiveModelAdapter.extend(OfflineAdapterMixin, {
...
});

Will appreciate any help. Thanks!

Hi!
Sure you can. For right now, you need to do just everything that we did in baseAdapter, but for ActiveModelAdapter. This can be achieved  in many ways. The easiest is to just copy baseAdapter and replace RESRAdapter with AM.
The main points of baseAdapter are - to link onlineAdapter and offlineAdapter, to pass some offlineSerializer params(https://github.com/api-hogs/ember-data-offline/blob/master/addon/adapters/base.js#L76) and to setup container for them. So you can do this points in the most comfortable way for you and it will be working.
For next releases we'll add more flexible adapters/serializer definition system, but for now you should do some manual work.

@igorpreston any success with this?


Startup winston logging got error

use version:

@google-cloud/logging-winston: 5.1.4
winston: 3.8.1

I try to add google winston with Nestjs project to startup. but got this error:
  const error = new Error(message);
                ^
Error: 3 INVALID_ARGUMENT: Timestamp is over a day in the future
    at Object.callErrorFromStatus (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/call.ts:81:17)
    at Object.onReceiveStatus (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/client.ts:352:36)
    at Object.onReceiveStatus (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/client-interceptors.ts:462:34)
    at Object.onReceiveStatus (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/client-interceptors.ts:424:48)
    at /Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/call-stream.ts:330:24
    at processTicksAndRejections (node:internal/process/task_queues:78:11)
for call at
    at ServiceClientImpl.makeUnaryRequest (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/client.ts:324:26)
    at ServiceClientImpl.<anonymous> (/Users/user/Desktop/project/service/node_modules/@grpc/grpc-js/src/make-client.ts:189:15)
    at /Users/user/Desktop/project/service/node_modules/@google-cloud/logging/src/v2/logging_service_v2_client.ts:384:25
    at /Users/user/Desktop/project/service/node_modules/google-gax/src/normalCalls/timeout.ts:54:13
    at repeat (/Users/user/Desktop/project/service/node_modules/google-gax/src/normalCalls/retries.ts:104:19)
    at Task._apiCall (/Users/user/Desktop/project/service/node_modules/google-gax/src/normalCalls/retries.ts:144:7)
    at Task.run (/Users/user/Desktop/project/service/node_modules/google-gax/src/bundlingCalls/task.ts:177:31)
    at BundleExecutor._runNow (/Users/user/Desktop/project/service/node_modules/google-gax/src/bundlingCalls/bundleExecutor.ts:282:10)
    at Timeout._onTimeout (/Users/user/Desktop/project/service/node_modules/google-gax/src/bundlingCalls/bundleExecutor.ts:222:14)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7)

this is my setting:
export default () => {
	const loggingWinston = new LoggingWinston({
		projectId: process.env?.GCP_PROJECT_ID,
		serviceContext: {
			service: 'my-service',
			version: 'v1',
		},
	});
	const transports: Transport[] = [
		new winston.transports.Console({
			level: 'debug',
			debugStdout: true,
		}),
		loggingWinston,
	];

return {
		format: winston.format.combine(
			winston.format.splat(),
			winston.format.label(),
			winston.format.timestamp({
				format: 'YYYY-MM-dd HH:mm:ss.SSS',
			}),
			winston.format.align(),
			winston.format.errors({ stack: true }),
			winston.format.printf((option: TransformableInfo) => ...
		),
		transports,
	};

Hi team, am I setting it wrong?

@JeffHu88 , what happens if you omit the timestamp formatting - does all works for you?

I try to omit the timestamp formatting and rebuild it work by remove node module. but I don't know why?

@JeffHu88 , I am sorry but I must admit I did not understood your comment - correct me if I wrong but omitting a timestamp formatting works for you, right?

yes, and I add timestamp back, it can work now.

Oh, I see - thanks for update!
If everything works now, I am not sure what happened and tend to believe it might be related to your environment - perhaps there were issues with clock which was misconfigured?
Also, please let me know how else I can assist here - if there is no more questions, I will be closing this issue.
Thanks!

Ok, I don't have questions. Thank you.


[GSSoC 23'] Fixed the code corrected the error of file paths

Reference issue
Issue No: 193
Description
The bug stems from the reorganized projects, where specific program features interact with a text file. This necessitates fixing the file paths used in various locations is completed.
To ensure the proper functioning of the projects, all instances of file paths are corrected.
About The Correction

The entire set of database items and files has been relocated to a distinct directory.
The paths to the file, which are referenced in various sections and modules of the code, have been recalibrated.

hello @Pranjal360Agarwal Please check this now I started from the start 🥹

@Pranjal360Agarwal please check this now

@Pranjal360Agarwal please check the PR

@Pranjal360Agarwal please check the PR

Traceback (most recent call last):
File "C:\Users\91945\OneDrive\Desktop\ApnaBharat-Bus-Booking-Reservation-System\Bus_booking_system\main.py", line 17, in
Check = SignIn.Login().mainloop()
File "C:\Users\91945\OneDrive\Desktop\ApnaBharat-Bus-Booking-Reservation-System\Bus_booking_system\Database\Modules\SignIn_Module\SignIn_page.py", line 47, in init
Image.open("Bus_booking_system\Database\Image\Background_gradient.jpg"),
File "C:\Users\91945\AppData\Local\Programs\Python\Python310\lib\site-packages\PIL\Image.py", line 3131, in open
fp = builtins.open(filename, "rb")
FileNotFoundError: [Errno 2] No such file or directory: 'Bus_booking_system\Database\Image\Background_gradient.jpg'


Investigate quinn performance on main and parallel-transmit branches

As we are starting to move to working on quinn we need to check out the baseline of quinn's main branch.  This involves porting iroh to those branches and then we can get netsim numbers.
Early tests indicate main might have a regression for 1-N transmission, but an improvement for 1-1.  The parallel-transmit branch is supposed to improve on that.  So we need to figure out if that change is enough or if we still need to understand where the 1-N perf regression came from on main.

parallel-transmit might be tricky for us, but not impossible.  for main we're probably fine but may need a bit of work.  couldn't find anything wrong with quinn.


The tap area of the globe key is smaller than expected

As seen in the attached video, the globe key has a weird behavior – if you tap it outside the center, an incorrect key will be triggered.
The following is recorded with the "English" keyboard of the demo app on an iPhone SE (3rd gen) simulator:
https://user-images.githubusercontent.com/31893391/236643184-ecc1b126-6686-4327-b0b5-4e8938e162f0.mov

Hey @f-person
That's strange - will look into it asap!

This was due to how the next keyboard button needs to wrap UIKit to properly trigger keyboard switching. It's really strange how it caused the surrounding view gestures to leak and overlap the next keyboard button.
I moved that UIKit wrapping from the system keyboard button content view to the view gesture modifier, which makes the next keyboard gestures apply to the entire button.
A nice side-effect is that this makes the view modifier behave better as well, since it will actually apply the next keyboard gestures to any view now, instead of ignoring it for the .nextKeyboard action.
This fix will be available in the next release.


Need test feedbacks on Bluetooth HID support PKG

If you have flashed my modded PKG that enables Bluetooth HID, I need some feedbacks about:

What is your device?
Does it work?
If not, what is the error?

I personally tried it on RP1 and it works with a Mac magic keybaord. But #65 says it didn't work with errors about Can't communicate with FILCO Bluetooth Keyboard.

dpt-rp1
no
Can't communicate with FILCO Bluetooth Keyboard

After receiving the repaired machine these two days, I brushed multiple versions. The first version is returned by the merchant, I rooted - select example-pkg-Bluetooth, and failure.
And then, I flashed the Taobao version, it's claim support Bluetooth Keyboard, but it didn't work (the error message is different from our version).
Then in the Taobao version of the basics, I rooted again, and flashed example-pkg-Bluetooth, it didn't work.
(On Taobao.com pages, I had seen that solders upgrade the Bluetooth function again)
Did you say "/root/error.log" on dpt? I did not find it.
$ adb shell
$ su
# mount -o rw,remount /system
# ls *log
*log: No such file or directory
# cd /root
# ls -la
#

im referring to the dmesg log, or logcat when it happens

It works on my rp1 with Microsoft Wedge Mobile Keyboard.

one also reported they cannot find bluetooth devices at all..
and just to give you some info, the bluetooth HID mod only changes the bluetooth APK profiles.xml that allows HID connections. It does not solve if you cannot find the device.

What is your device?
Logitech craft
Does it work?
no
If not, what is the error?
can't find it in bluetooth setting

Ganss GS87-D works. It requires no code when pairing with dpt-rp1

Logitech K380, I just check it's Bluetooth 3.0 version, which is same as Ganss GS87.
So I guess RP1 only support <= 3.0

Install typeeto app at Mac book pro , you can make it as rp1's bluetooth keyboard.

I bought GS87D, it worked.
and I have an idea to transfer a normal keyboard to a mechanical keyboard via USB Bluetooth, so I bought a USB-device, is worked.

Hello, I tried the PKG with a Logitech M535 mouse and I can pair them and use the mouse, but bluetooth keeps turning itself off in android settings. Sometimes I can use the mouse for many minutes, sometimes just some seconds, I haven't found a pattern, but bluetooth setting keeps getting turned off automatically. What could be the problem?

Hello, I tried the PKG with a Logitech M535 mouse and I can pair them and use the mouse, but bluetooth keeps turning itself off in android settings. Sometimes I can use the mouse for many minutes, sometimes just some seconds, I haven't found a pattern, but bluetooth setting keeps getting turned off automatically. What could be the problem?

It seems this was caused by some kind of clash between the Sony stock settings and Android settings. I went and disabled wifi and enabled bluetooth in the Sony original settings screen instead of the Android settings screen, and now the mouse works without problems. Thanks!!

Logitech K480 Keyboard.
It works.


Add Pagination for Audiobook Listings

Description: If the audiobook library grows, users may need pagination to navigate through the available books. Add pagination to display a limited number of audiobooks per page.
Tasks:
Display only a set number of audiobooks per page (e.g., 6).
Create previous and next buttons or page numbers to navigate through the pages.
Ensure pagination is responsive and works on mobile devices.

I would like to work on this issue, please assign this issue

Hey @muthahira04 go ahead. ⭐ the repo and start your task now. Happy Coding 👨🏼💻

are u working on it @muthahira04  ?

@muthahira04 are you still working ?

Hello, i would like to resolve this issue !

Hey @Phanty78 go ahead


Image asset crash when building for multiple devices

🔑
New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

I have a sample project here that

has one image asset to show. The asset contains multiple images for iPhone and iPads.
Snapshot builds for "iPad Pro (12.9-inch) (3rd generation)" and "iPhone Xs Max"

Running the UITests in Xcode works perfectly fine
Snapshot crashes with "Caught error... 65"
When removing the line imageView.image = UIImage(named: "photo")! everything works as expected
For me it looks like the compilation of image assets with multiple images for iPads and iPhones in Snapshot is not correct

Command executed

Download project
run fastlane screenshots

Complete output when running fastlane, including the stack trace and command used

Markus-Fassbender:ScreenshotTests markus.fassbender$ fastlane screenshots
[13:56:28]: fastlane detected a Gemfile in the current directory
[13:56:28]: however it seems like you don't use `bundle exec`
[13:56:28]: to launch fastlane faster, please use
[13:56:28]:
[13:56:28]: $ bundle exec fastlane screenshots
[13:56:28]:
[13:56:28]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[13:56:31]: ------------------------------
[13:56:31]: --- Step: default_platform ---
[13:56:31]: ------------------------------
[13:56:31]: Driving the lane 'ios screenshots' 🚀
[13:56:31]: --------------------------------
[13:56:31]: --- Step: clear_derived_data ---
[13:56:31]: --------------------------------
[13:56:31]: Derived Data path located at: /Users/markus.fassbender/Library/Developer/Xcode/DerivedData
[13:56:31]: Successfully cleared Derived Data ♻
[13:56:31]: ---------------------------------
[13:56:31]: --- Step: capture_screenshots ---
[13:56:31]: ---------------------------------
[13:56:32]: Successfully loaded '/Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Snapfile' 📄
[13:56:32]: No values defined in './Fastlane/Snapfile'
[13:56:33]: $ xcodebuild -showBuildSettings -scheme ScreenshotTest -project ./ScreenshotTest.xcodeproj -configuration ScreenshotTest
+----------------------------+--------------------------------------+
|                   Summary for snapshot 2.126.0                    |
+----------------------------+--------------------------------------+
| configuration              | ScreenshotTest                       |
| languages                  | [["de-DE"]]                          |
| devices                    | ["iPad Pro (12.9-inch) (3rd          |
|                            | generation)", "iPhone Xs Max"]       |
| clean                      | true                                 |
| clear_previous_screenshots | true                                 |
| erase_simulator            | true                                 |
| project                    | ./ScreenshotTest.xcodeproj           |
| scheme                     | ScreenshotTest                       |
| output_directory           | /Users/markus.fassbender/Documents/  |
|                            | Git/ScreenshotTests/fastlane/screen  |
|                            | shots                                |
| launch_arguments           | [""]                                 |
| output_simulator_logs      | false                                |
| skip_open_summary          | false                                |
| skip_helper_version_check  | false                                |
| reinstall_app              | false                                |
| localize_simulator         | false                                |
| app_identifier             | de.markusfassbender.ScreenshotTest   |
| buildlog_path              | ~/Library/Logs/snapshot              |
| number_of_retries          | 1                                    |
| stop_after_first_error     | false                                |
| result_bundle              | false                                |
| concurrent_simulators      | true                                 |
| xcode_path                 | /Applications/Xcode.app              |
+----------------------------+--------------------------------------+
[13:56:34]: Clearing previously generated screenshots
[13:56:34]: Building and running project - this might take some time...
[13:56:35]: Patching simulators '/Users/markus.fassbender/Library/Preferences/com.apple.iphonesimulator.plist' to scale to 100%
[13:56:42]: Erasing iPad Pro (12.9-inch) (3rd generation)...
[13:56:43]: Erasing iPhone Xs Max...
[13:56:46]: Running snapshot on: iPad Pro (12.9-inch) (3rd generation), iPhone Xs Max
[13:56:46]: $ set -o pipefail && xcodebuild -scheme ScreenshotTest -project ./ScreenshotTest.xcodeproj -configuration ScreenshotTest -derivedDataPath '/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce' -destination 'platform=iOS Simulator,name=iPad Pro (12.9-inch) (3rd generation),OS=12.2' -destination 'platform=iOS Simulator,name=iPhone Xs Max,OS=12.2' FASTLANE_SNAPSHOT=YES clean build test | tee /Users/markus.fassbender/Library/Logs/snapshot/ScreenshotTest-ScreenshotTest.log | xcpretty
[13:56:46]: ▸ Loading...
[13:56:49]: ▸ Clean Succeeded
[13:56:49]: ▸ Clean Succeeded
[13:56:52]: ▸ Linking ScreenshotTest
[13:56:52]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Snapfile
[13:56:52]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Fastfile
[13:56:52]: ▸ Compiling LaunchScreen.storyboard
[13:56:52]: ▸ Compiling Main.storyboard
[13:56:52]: ▸ Processing Info.plist
[13:56:52]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:56:52]: Running Tests: ▸ Touching ScreenshotTest.app (in target: ScreenshotTest)
[13:56:52]: ▸ Build Succeeded
[13:56:52]: ▸ Linking ScreenshotTest
[13:56:53]: ▸ Processing Info.plist
[13:56:53]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:56:53]: ▸ Build Succeeded
[13:56:53]: ▸ Linking ScreenshotTest
[13:56:54]: ▸ Processing Info.plist
[13:56:54]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:56:55]: ▸ Processing Info.plist
[13:56:55]: ▸ Linking ScreenshotTestUITests
[13:56:55]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Appfile
[13:56:55]: ▸ Generating 'ScreenshotTestUITests.xctest.dSYM'
[13:56:55]: ▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks/XCTAutomationSupport.framework
[13:56:55]: ▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework
[13:56:55]: Running Tests: ▸ Touching ScreenshotTestUITests.xctest (in target: ScreenshotTestUITests)
[13:56:55]: ▸ 2019-07-09 13:56:55.896 xcodebuild[56914:2384882]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[13:56:55]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult/7_Test/Diagnostics/ScreenshotTestUITests-913F1282-D167-4335-9966-1401CE1108E1/ScreenshotTestUITests-E5945BBB-AEE0-4A5D-81D3-A9F487EDE4A3/Session-ScreenshotTestUITests-2019-07-09_135655-y5hUFb.log
[13:56:55]: ▸ 2019-07-09 13:56:55.896 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (3726F106-CFBA-41D8-863B-EBE3DFE50CFB) Beginning test session ScreenshotTestUITests-3726F106-CFBA-41D8-863B-EBE3DFE50CFB at 2019-07-09 13:56:55.896 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fac5d63aa90> {
[13:56:55]: ▸ SimDevice: iPhone Xs Max (2668E388-CACE-42D1-82E5-726B31B39FD3, iOS 12.2, Shutdown)
[13:56:55]: ▸ } (12.2 (16E226))
[13:56:55]: ▸ 2019-07-09 13:56:55.928 xcodebuild[56914:2386184]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[13:56:55]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult/6_Test/Diagnostics/ScreenshotTestUITests-50A18F90-4C5A-4A3E-BA62-82F209707776/ScreenshotTestUITests-7A3ED5B9-4DF8-4FBA-8358-F03709EB8A0D/Session-ScreenshotTestUITests-2019-07-09_135655-PJE3JN.log
[13:56:55]: ▸ 2019-07-09 13:56:55.929 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (2897B5FB-6370-4BE8-8A0B-5780DDCF15E3) Beginning test session ScreenshotTestUITests-2897B5FB-6370-4BE8-8A0B-5780DDCF15E3 at 2019-07-09 13:56:55.929 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fac5d645c70> {
[13:56:55]: ▸ SimDevice: iPad Pro (12.9-inch) (3rd generation) (8E4DA4DC-9B2D-48BD-A85E-41500352D8EE, iOS 12.2, Shutdown)
[13:56:55]: ▸ } (12.2 (16E226))
[13:57:23]: ▸ 2019-07-09 13:57:23.528 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (2897B5FB-6370-4BE8-8A0B-5780DDCF15E3) Finished requesting crash reports. Continuing with testing.
[13:57:23]: ▸ 2019-07-09 13:57:23.643 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (3726F106-CFBA-41D8-863B-EBE3DFE50CFB) Finished requesting crash reports. Continuing with testing.
[13:57:35]: ▸ 2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 39.278 elapsed -- Testing started completed.
[13:57:35]: ▸ 2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[13:57:35]: ▸ 2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 39.278 sec, +39.278 sec -- end
[13:58:28]: ▸ 2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 92.515 elapsed -- Testing started completed.
[13:58:28]: ▸ 2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[13:58:28]: ▸ 2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 92.515 sec, +92.515 sec -- end
[13:58:28]: ▸ Failing tests:
[13:58:28]: ▸ ScreenshotTestUITests:
[13:58:28]: ▸ ScreenshotTestUITests.testSnapshot()
[13:58:28]: ▸ Test session results and logs:
[13:58:28]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult
[13:58:28]: ▸ ** TEST FAILED **
▸ Clean Succeeded
▸ Clean Succeeded
▸ Linking ScreenshotTest
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Snapfile
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Fastfile
▸ Compiling LaunchScreen.storyboard
▸ Compiling Main.storyboard
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Touching ScreenshotTest.app (in target: ScreenshotTest)
▸ Build Succeeded
▸ Linking ScreenshotTest
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Build Succeeded
▸ Linking ScreenshotTest
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Processing Info.plist
▸ Linking ScreenshotTestUITests
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Appfile
▸ Generating 'ScreenshotTestUITests.xctest.dSYM'
▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks/XCTAutomationSupport.framework
▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework
▸ Touching ScreenshotTestUITests.xctest (in target: ScreenshotTestUITests)
2019-07-09 13:56:55.896 xcodebuild[56914:2384882]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult/7_Test/Diagnostics/ScreenshotTestUITests-913F1282-D167-4335-9966-1401CE1108E1/ScreenshotTestUITests-E5945BBB-AEE0-4A5D-81D3-A9F487EDE4A3/Session-ScreenshotTestUITests-2019-07-09_135655-y5hUFb.log
2019-07-09 13:56:55.896 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (3726F106-CFBA-41D8-863B-EBE3DFE50CFB) Beginning test session ScreenshotTestUITests-3726F106-CFBA-41D8-863B-EBE3DFE50CFB at 2019-07-09 13:56:55.896 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fac5d63aa90> {
SimDevice: iPhone Xs Max (2668E388-CACE-42D1-82E5-726B31B39FD3, iOS 12.2, Shutdown)
} (12.2 (16E226))
2019-07-09 13:56:55.928 xcodebuild[56914:2386184]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult/6_Test/Diagnostics/ScreenshotTestUITests-50A18F90-4C5A-4A3E-BA62-82F209707776/ScreenshotTestUITests-7A3ED5B9-4DF8-4FBA-8358-F03709EB8A0D/Session-ScreenshotTestUITests-2019-07-09_135655-PJE3JN.log
2019-07-09 13:56:55.929 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (2897B5FB-6370-4BE8-8A0B-5780DDCF15E3) Beginning test session ScreenshotTestUITests-2897B5FB-6370-4BE8-8A0B-5780DDCF15E3 at 2019-07-09 13:56:55.929 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fac5d645c70> {
SimDevice: iPad Pro (12.9-inch) (3rd generation) (8E4DA4DC-9B2D-48BD-A85E-41500352D8EE, iOS 12.2, Shutdown)
} (12.2 (16E226))
2019-07-09 13:57:23.528 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (2897B5FB-6370-4BE8-8A0B-5780DDCF15E3) Finished requesting crash reports. Continuing with testing.
2019-07-09 13:57:23.643 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: (3726F106-CFBA-41D8-863B-EBE3DFE50CFB) Finished requesting crash reports. Continuing with testing.
2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 39.278 elapsed -- Testing started completed.
2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2019-07-09 13:57:35.145 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 39.278 sec, +39.278 sec -- end
2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 92.515 elapsed -- Testing started completed.
2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2019-07-09 13:58:28.381 xcodebuild[56914:2384859] [MT] IDETestOperationsObserverDebug: 92.515 sec, +92.515 sec -- end
Failing tests:
ScreenshotTestUITests:
ScreenshotTestUITests.testSnapshot()
Test session results and logs:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-56-49-+0200.xcresult
** TEST FAILED **
[13:58:34]: Exit status: 65
[13:58:34]: Copying '/Users/markus.fassbender/Documents/Git/ScreenshotTests/fastlane/screenshots/de-DE/iPad Pro (12.9-inch) (3rd generation)-01Screen.png'...
[13:58:34]: Tests failed while running on: iPad Pro (12.9-inch) (3rd generation), iPhone Xs Max
[13:58:34]: For more detail about the test failures, check the logs here:
[13:58:34]: /Users/markus.fassbender/Library/Logs/snapshot/ScreenshotTest-ScreenshotTest.log
[13:58:34]:
[13:58:34]: You can also find the test result data here:
[13:58:34]: /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test
[13:58:34]:
[13:58:34]: You can find the incomplete screenshots here:
[13:58:34]: /Users/markus.fassbender/Library/Caches/tools.fastlane/screenshots
[13:58:34]: /Users/markus.fassbender/Documents/Git/ScreenshotTests/fastlane/screenshots
[13:58:34]: Caught error... 65
[13:58:34]: Retrying on devices: iPad Pro (12.9-inch) (3rd generation), iPhone Xs Max
[13:58:34]: Number of retries remaining: 0
[13:58:34]: $ set -o pipefail && xcodebuild -scheme ScreenshotTest -project ./ScreenshotTest.xcodeproj -configuration ScreenshotTest -derivedDataPath '/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce' -destination 'platform=iOS Simulator,name=iPad Pro (12.9-inch) (3rd generation),OS=12.2' -destination 'platform=iOS Simulator,name=iPhone Xs Max,OS=12.2' FASTLANE_SNAPSHOT=YES clean build test | tee /Users/markus.fassbender/Library/Logs/snapshot/ScreenshotTest-ScreenshotTest.log | xcpretty
[13:58:34]: ▸ Loading...
[13:58:37]: ▸ Clean Succeeded
[13:58:38]: ▸ Clean Succeeded
[13:58:40]: ▸ Linking ScreenshotTest
[13:58:40]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Snapfile
[13:58:40]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Fastfile
[13:58:41]: ▸ Compiling LaunchScreen.storyboard
[13:58:41]: ▸ Compiling Main.storyboard
[13:58:41]: ▸ Processing Info.plist
[13:58:41]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:58:41]: Running Tests: ▸ Touching ScreenshotTest.app (in target: ScreenshotTest)
[13:58:41]: ▸ Build Succeeded
[13:58:41]: ▸ Linking ScreenshotTest
[13:58:41]: ▸ Processing Info.plist
[13:58:41]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:58:42]: ▸ Build Succeeded
[13:58:42]: ▸ Linking ScreenshotTest
[13:58:42]: ▸ Processing Info.plist
[13:58:42]: ▸ Generating 'ScreenshotTest.app.dSYM'
[13:58:44]: ▸ Processing Info.plist
[13:58:44]: ▸ Linking ScreenshotTestUITests
[13:58:44]: ▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Appfile
[13:58:44]: ▸ Generating 'ScreenshotTestUITests.xctest.dSYM'
[13:58:44]: ▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework
[13:58:44]: ▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks/XCTAutomationSupport.framework
[13:58:44]: Running Tests: ▸ Touching ScreenshotTestUITests.xctest (in target: ScreenshotTestUITests)
[13:58:44]: ▸ 2019-07-09 13:58:44.628 xcodebuild[57360:2394058]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[13:58:44]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult/6_Test/Diagnostics/ScreenshotTestUITests-2AAC6E1B-5ACE-44A6-98AC-E8B35C10BDE7/ScreenshotTestUITests-341333BA-3A38-452D-9D9F-714545735446/Session-ScreenshotTestUITests-2019-07-09_135844-E8uyCY.log
[13:58:44]: ▸ 2019-07-09 13:58:44.628 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (F0C98B47-B870-4759-9B0C-178237FD6A0B) Beginning test session ScreenshotTestUITests-F0C98B47-B870-4759-9B0C-178237FD6A0B at 2019-07-09 13:58:44.628 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fc7e93ee820> {
[13:58:44]: ▸ SimDevice: iPad Pro (12.9-inch) (3rd generation) (8E4DA4DC-9B2D-48BD-A85E-41500352D8EE, iOS 12.2, Shutdown)
[13:58:44]: ▸ } (12.2 (16E226))
[13:58:44]: ▸ 2019-07-09 13:58:44.662 xcodebuild[57360:2395217]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
[13:58:44]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult/7_Test/Diagnostics/ScreenshotTestUITests-63A27B5D-79D3-4FD6-86D4-61D8C48E3871/ScreenshotTestUITests-A9EEA8BD-AA77-4FAC-9D9D-FAB0D49C9902/Session-ScreenshotTestUITests-2019-07-09_135844-jnrapp.log
[13:58:44]: ▸ 2019-07-09 13:58:44.662 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (214D4F2A-7B3F-47AF-99E4-03C40E4B159D) Beginning test session ScreenshotTestUITests-214D4F2A-7B3F-47AF-99E4-03C40E4B159D at 2019-07-09 13:58:44.662 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fc7e619b8a0> {
[13:58:44]: ▸ SimDevice: iPhone Xs Max (2668E388-CACE-42D1-82E5-726B31B39FD3, iOS 12.2, Shutdown)
[13:58:44]: ▸ } (12.2 (16E226))
[13:58:59]: ▸ 2019-07-09 13:58:59.990 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (F0C98B47-B870-4759-9B0C-178237FD6A0B) Finished requesting crash reports. Continuing with testing.
[13:59:00]: ▸ 2019-07-09 13:59:00.079 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (214D4F2A-7B3F-47AF-99E4-03C40E4B159D) Finished requesting crash reports. Continuing with testing.
[13:59:10]: ▸ 2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 26.129 elapsed -- Testing started completed.
[13:59:10]: ▸ 2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[13:59:10]: ▸ 2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 26.129 sec, +26.129 sec -- end
[13:59:17]: ▸ 2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 32.487 elapsed -- Testing started completed.
[13:59:17]: ▸ 2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[13:59:17]: ▸ 2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 32.487 sec, +32.487 sec -- end
[13:59:17]: ▸ Failing tests:
[13:59:17]: ▸ ScreenshotTestUITests:
[13:59:17]: ▸ ScreenshotTestUITests.testSnapshot()
[13:59:17]: ▸ Test session results and logs:
[13:59:17]: ▸ /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult
[13:59:17]: ▸ ** TEST FAILED **
▸ Clean Succeeded
▸ Clean Succeeded
▸ Linking ScreenshotTest
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Snapfile
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Fastfile
▸ Compiling LaunchScreen.storyboard
▸ Compiling Main.storyboard
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Touching ScreenshotTest.app (in target: ScreenshotTest)
▸ Build Succeeded
▸ Linking ScreenshotTest
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Build Succeeded
▸ Linking ScreenshotTest
▸ Processing Info.plist
▸ Generating 'ScreenshotTest.app.dSYM'
▸ Processing Info.plist
▸ Linking ScreenshotTestUITests
▸ Copying /Users/markus.fassbender/Documents/Git/ScreenshotTests/Fastlane/Appfile
▸ Generating 'ScreenshotTestUITests.xctest.dSYM'
▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/Frameworks/XCTest.framework
▸ Copying /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Library/PrivateFrameworks/XCTAutomationSupport.framework
▸ Touching ScreenshotTestUITests.xctest (in target: ScreenshotTestUITests)
2019-07-09 13:58:44.628 xcodebuild[57360:2394058]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult/6_Test/Diagnostics/ScreenshotTestUITests-2AAC6E1B-5ACE-44A6-98AC-E8B35C10BDE7/ScreenshotTestUITests-341333BA-3A38-452D-9D9F-714545735446/Session-ScreenshotTestUITests-2019-07-09_135844-E8uyCY.log
2019-07-09 13:58:44.628 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (F0C98B47-B870-4759-9B0C-178237FD6A0B) Beginning test session ScreenshotTestUITests-F0C98B47-B870-4759-9B0C-178237FD6A0B at 2019-07-09 13:58:44.628 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fc7e93ee820> {
SimDevice: iPad Pro (12.9-inch) (3rd generation) (8E4DA4DC-9B2D-48BD-A85E-41500352D8EE, iOS 12.2, Shutdown)
} (12.2 (16E226))
2019-07-09 13:58:44.662 xcodebuild[57360:2395217]  IDETestOperationsObserverDebug: Writing diagnostic log for test session to:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult/7_Test/Diagnostics/ScreenshotTestUITests-63A27B5D-79D3-4FD6-86D4-61D8C48E3871/ScreenshotTestUITests-A9EEA8BD-AA77-4FAC-9D9D-FAB0D49C9902/Session-ScreenshotTestUITests-2019-07-09_135844-jnrapp.log
2019-07-09 13:58:44.662 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (214D4F2A-7B3F-47AF-99E4-03C40E4B159D) Beginning test session ScreenshotTestUITests-214D4F2A-7B3F-47AF-99E4-03C40E4B159D at 2019-07-09 13:58:44.662 with Xcode 10E1001 on target <DVTiPhoneSimulator: 0x7fc7e619b8a0> {
SimDevice: iPhone Xs Max (2668E388-CACE-42D1-82E5-726B31B39FD3, iOS 12.2, Shutdown)
} (12.2 (16E226))
2019-07-09 13:58:59.990 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (F0C98B47-B870-4759-9B0C-178237FD6A0B) Finished requesting crash reports. Continuing with testing.
2019-07-09 13:59:00.079 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: (214D4F2A-7B3F-47AF-99E4-03C40E4B159D) Finished requesting crash reports. Continuing with testing.
2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 26.129 elapsed -- Testing started completed.
2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2019-07-09 13:59:10.726 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 26.129 sec, +26.129 sec -- end
2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 32.487 elapsed -- Testing started completed.
2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
2019-07-09 13:59:17.084 xcodebuild[57360:2394019] [MT] IDETestOperationsObserverDebug: 32.487 sec, +32.487 sec -- end
Failing tests:
ScreenshotTestUITests:
ScreenshotTestUITests.testSnapshot()
Test session results and logs:
/var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test/Run-ScreenshotTest-2019.07.09_13-58-37-+0200.xcresult
** TEST FAILED **
[13:59:23]: Exit status: 65
[13:59:23]: Copying '/Users/markus.fassbender/Documents/Git/ScreenshotTests/fastlane/screenshots/de-DE/iPad Pro (12.9-inch) (3rd generation)-01Screen.png'...
[13:59:23]: Tests failed while running on: iPad Pro (12.9-inch) (3rd generation), iPhone Xs Max
[13:59:23]: For more detail about the test failures, check the logs here:
[13:59:23]: /Users/markus.fassbender/Library/Logs/snapshot/ScreenshotTest-ScreenshotTest.log
[13:59:23]:
[13:59:23]: You can also find the test result data here:
[13:59:23]: /var/folders/kk/vw_pd4gd18l6_zrgbzg6qbl00000gn/T/snapshot_derived20190709-56441-1ekwrce/Logs/Test
[13:59:23]:
[13:59:23]: You can find the incomplete screenshots here:
[13:59:23]: /Users/markus.fassbender/Library/Caches/tools.fastlane/screenshots
[13:59:23]: /Users/markus.fassbender/Documents/Git/ScreenshotTests/fastlane/screenshots
[13:59:23]: Caught error... 65
+----------------------------+-------+
|          snapshot results          |
+----------------------------+-------+
| Device                     | de-DE |
+----------------------------+-------+
| iPad Pro (12.9-inch) (3rd  |  ❌   |
| generation)                |       |
| iPhone Xs Max              |  ❌   |
+----------------------------+-------+
[13:59:23]: Generating HTML Report
[13:59:23]: Successfully created HTML file with an overview of all the screenshots: '/Users/markus.fassbender/Documents/Git/ScreenshotTests/fastlane/screenshots/screenshots.html'
+------+---------------------+-------------+
|             fastlane summary             |
+------+---------------------+-------------+
| Step | Action              | Time (in s) |
+------+---------------------+-------------+
| 1    | default_platform    | 0           |
| 2    | clear_derived_data  | 0           |
| 3    | capture_screenshots | 171         |
+------+---------------------+-------------+
[13:59:23]: fastlane.tools finished successfully 🎉

Environment

✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.5

Ruby
2.2.4

Bundler?
false

Git
git version 2.20.1 (Apple Git-117)

Installation Source
~/.fastlane/bin/bundle/bin/fastlane

Host
Mac OS X 10.14.5 (18F132)

Ruby Lib Dir
~/.fastlane/bin/bundle/lib

OpenSSL Version
OpenSSL 1.0.2g  1 Mar 2016

Is contained
false

Is homebrew
true

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE
en_US.UTF-8
✅

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do
  lane :screenshots do
      clear_derived_data()

      configuration = "ScreenshotTest"
      devices = ["iPad Pro (12.9-inch) (3rd generation)", "iPhone Xs Max"]
      languages = ["de-DE"]

      capture_screenshots(configuration: configuration,
                          languages: [languages],
                          devices: devices,
                          clean: true,
                          clear_previous_screenshots: true,
                          erase_simulator: true)
  end
end

`./fastlane/Appfile`
app_identifier("de.markusfassbender.ScreenshotTest") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.126.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

slack-notifier
2.3.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.1.3

terminal-table
1.7.3

multipart-post
2.0.0

word_wrap
1.0.0

public_suffix
2.0.5

tty-cursor
0.6.1

tty-spinner
0.9.0

babosa
1.0.2

colored
1.2

commander-fastlane
4.4.6

faraday
0.12.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20170404

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

gh_inspector
1.1.3

json
1.8.1

mini_magick
4.5.1

multi_xml
0.6.0

security
0.1.3

xcpretty-travis-formatter
0.0.4

bundler
1.14.6

faraday_middleware
<IP_ADDRESS>

naturally
2.2.0

simctl
1.6.5

jwt
2.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

mime-types
3.1

signet
0.11.0

memoist
0.16.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.3.0

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

tty-screen
0.7.0

highline
1.7.10

excon
0.64.0

rubyzip
1.2.3

CFPropertyList
3.0.0

libxml-ruby
3.0.0

plist
3.5.0

atomos
0.1.3

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.10.0

fastimage
2.1.5

addressable
2.6.0

multi_json
1.13.1

os
1.0.1

psych
2.0.8

retriable
3.1.2

mime-types-data
3.2019.0331

uber
0.1.0

generated on: 2019-07-09

When removing the line imageView.image = UIImage(named: "photo")! everything works as expected

Refers to https://github.com/dermaaarkus/ScreenshotTests/blob/328bb8a815d212fc8bb2a411f7e6f576554b4a5d/ScreenshotTest/ViewController.swift#L40

Snapshot builds for "iPad Pro (12.9-inch) (3rd generation)" and "iPhone Xs Max"

Is this specific to theses two devices or do any iPad and iPhone work?

Thanks for your attention and follow up question!
I've continued with some tests:

✅ devices = ["iPad Pro (12.9-inch) (3rd generation)"]
✅ devices = ["iPhone Xs Max"] works
✅ devices = ["iPad Pro (12.9-inch) (3rd generation)", "iPad Pro (12.9-inch) (2nd generation)"]
✅  devices = ["iPhone Xs Max", "iPhone 5s"]
✅  devices = ["iPhone Xs Max", "iPhone 5s"]
💥  devices = ["iPad Pro (12.9-inch) (2nd generation)", "iPhone 5s"]

So its not specific to these two devices! Any iPad/iPhone combination crashes and for me it looks like something (size classes of image assets?) connected to that.

The issue still exists and is relevant for my work. Thanks.

I've updated my sample project (see issue description) to Xcode 11 and iOS 13 and can not reproduce the cash 💥  anymore!