[Task]: Check  CodeMirror v6 vs v5 performance

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
No response

Task completed
Ref: https://www.notion.so/appsmith/CodeMirror-Upgrade-7bd44bf4244f43c1bd4a422f26ce4fb2?pvs=4#0c04e60904714ea1b041396e8817e211


Compiler incorrectly warns about type mismatch

/**
 * @param {?Blob} blobOrNull
 */
function fn(blobOrNull) {
	/** @type {!Blob} */
	var blob;

	if (blobOrNull) {
		blob = blobOrNull;
	}
	(function() {
		blobOrNull = null;
	})();
}

test.js:9: WARNING - [JSC_TYPE_MISMATCH] assignment
found   : (Blob|null)
required: Blob
		blob = blobOrNull;
		^^^^^^^^^^^^^^^^^

0 error(s), 1 warning(s), 85.7% typed

But no warning here:
/**
 * @param {?Blob} blobOrNull
 */
function fn(blobOrNull) {
	/** @type {!Blob} */
	var blob;

	if (blobOrNull) {
		blob = blobOrNull;
	}
	blobOrNull = null;
}

0 error(s), 0 warning(s), 100.0% typed

The compiler assumes that it cannot predict when the code within nested functions run.  We could maybe do something smarter in the special case of an IIFE, but it is unlikely we'll do this.


Possible to Stream a Video using POST Method

All Video Links are GET method based.
I want to disable link sharing which requires converting links to POST.
where link is https://dev.foldersapi.hashhackersapi.workers.dev/download
and POST body is something like file="Detailsoffileid"
Is it possible to load these POST method videos in plyr.io

+1


Command line option of the pipeline

Also, please let me know if I use the following command, does the pipeline cover all the steps from 1 to 5 of the workflow operations and generate the phylogeny tree.
I am using the pipeline at Galaxy but it is taking very long time. I have total 70 isolates.
$python bin/snvphyl.py --deploy-docker --fastq-dir example-data/fastqs --reference-file example-data/reference.fasta --min-coverage 5 --output-dir output1

@sekhwal yes, repeat region identification using MUMMer happens automatically in the below highlighted step in Galaxy:


Add JSON_PRESERVE_ZERO_FRACTION flag

The native json_encode method trims trailing zeros after the decimal point, which can be a problem.
For example typed properties in PHP7.4 they can expect float (e.g. product price), but receive int, which triggers a runtime error.

Thanks, I launched tests

@DavertMik Do you have any plans about releasing this bugfix?


Basic Auth/TLS broken in marathonClient.AddEventsListener()

When we create a marathon client with basic auth and/or TLS, the call to marathonClient.AddEventsListener() returns an error:
401:

<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1"/>
<title>Error 401 </title>

HTTP ERROR: 401

Problem accessing /v2/events. Reason:

    Unauthorized

Powered by Jetty:// 9.3.z-SNAPSHOT

with TLS:
x509: certificate is valid for *.mydomain.net, mydomain.net, not ***.***.***.***.mydomain.net

Here is the code used to register listeners: https://github.com/containous/traefik/blob/master/provider/marathon.go#L67
It seems marathonClient.AddEventsListener() doesn't use TLS/basic auth client config.

Any resolution on this?

@arichardet I suppose PR #142 will provide a fix for the problem once it has been merged.

@timoreimann ... i think #142 fixes the auth but not TLS. I've raised a PR https://github.com/donovanhide/eventsource/pull/22 to permit overriding the client

Good point, those are indeed two different issues. Thanks!

was fixed in #156

Thanks a lot @gambol99 :)


Path Formatting Helpers

Assuming that we feel like #2442 is worth completing, then a further level of convenience would be provided by adding static formatting methods to the path types.
For example, instead of
string path = new CryptoKeyName(project, location, keyRing, cryptoKey).ToString();

A caller could do
string path = CryptoKeyName.Format(project, location, keyRing, cryptoKey);

The latter feels more canonical to a .NET programmer.

Note that the equivalent already exists in Java; see e.g. https://github.com/GoogleCloudPlatform/google-cloud-java/blob/master/google-api-grpc/proto-google-cloud-kms-v1/src/main/java/com/google/cloud/kms/v1/CryptoKeyName.java#L70

Yeah, calling static string Format "more canonical" was probably the wrong way to characterize it.  I should've said something like "feels more right" (at least, to me).  In any case, I'd raise the following points in support of offering something other than new Foo(bar, baz).ToString():

Relying on a ToString value will always requires a visit to the documentation, if for no other reason than to confirm that the default implementation has been overridden.  Along these lines, a developer looking for valid methods/properties in Intellisense will likely visit ToString only after excluding the other available options.

The discussion of ToString in the .NET Framework Design Guidelines book describes ToString as "intended to be used for general display and debugging purposes".  It then offers some anecdotes of how attempting to use a value returned by ToString has burned the annotators in the past, even when ToString seemed to provide the intended output on casual inspection (pp 271-273).  This may ultimately be in the same family as the point above, but I think just further emphasizes that it's a time sink for developers to confirm that ToString indeed does what they want.

Calling a static Format method avoids allocating a throwaway object.

Yes this looks like a helpful feature.
We're currently working on a new code-gen implementation (soon to be in github), in which we'll put this feature. We don't have a firm release-date for this, but should be in the next couple of months.

@chrisdunelm: As you've been working on resources and resource names recently, is now a good time to implement this?

Thanks for the reminder. Yes, I'll implement these in the micro-generator.

This feature is now implemented in the micro-generator. So it won't appear in the generated code until we start using the micro-generator; which is not yet the case for any library.

Given that there's no action left beyond "start using the microgenerator when we can" I'd propose closing this issue. @bdhess are you okay with that?

Closing as this is now present in both generators,

Reopening but assigning to myself as I have a bit of work left to do - where we have resource name classes that aren't generated in the regular way.

Sorry, I was too enthusiastic ;)


Feature request: setSlots - Updates component slots

I can't find way to updating slots like a setProps does with props updating.
So, what if setSlots to updating slots content?
Example
describe('When mounting', () => {
     let wrapper: any

     beforeAll(() => {
            wrapper = mount(FooComponent, {
                props: {
                    foo: true,
                },
                slots: {
                    default: () => 'Foo'
                }
            })
        })

        describe('When foo', () => {
            describe('When foo bar', () => {
                it('should render foo', () => {
                    wrapper.setProps({foo: false }
                    wrapper.setSlots({ default: () => 'Bar' }) // !!! CHANGING default slot

                    expect(wrapper.text()).toBe('Bar')
                })
            })
        })
})

💚 Thank you for awesome projects!

Hi!
Does this represent a real use case? A slot can't just randomly change - why do you want to update it mid test? Do you have a more realistic scenario you can share?
I would really recommend just writing another test with the desired slot.

I agree with @lmiller1990 , I don't think this is needed.
You can write several tests to test different slots or use a "test component" and change its slot dynamically.
Something like (pseudo code):
const TestComponent = defineComponent({
  template: `<Foo>{{ content }}</Foo>`,
  components: { Foo },
  setup() {
    const content = ref('foo');
   return { content }
  }
});
// ...

const wrapper = mount(TestComponent);
expect(wrapper.html()).toContain('foo');

wrapper.vm.content = 'bar';
await nextTick();

expect(wrapper.html()).toContain('bar');


Add attributes delete to page and page_type bulk delete mutation

I want to merge this change because it adds missing associated attributes delete function to page and page_Type bulk delete mutation.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-5087 Reference is not removed when user will remove object


Show EKS cluster nodegroups in JL Compute UI section

Displaying EKS cluster nodegroups. Till EKS supports vpc endpoints, created lambda outside of isolated subnets to handle EKS service specific calls from orbit SDK.


Improve certificate prefetching

Skip non-HBONE workloads, who should not need certs
Use Warmup priority. We implemented prioritization for certificate fetching to favor on-demand fetchers but forgot to start using it.

We have traces but they need refinement and they are only going to stdout.
Metrics - agree.
ztunnel cert - I think ztunnel itself doesn't declare "hbone" protocol so
this might fix it. Let me check
On Thu, May 4, 2023, 9:39 AM Costin Manolache @.***>
wrote:

@.**** approved this pull request.
Looks great. The other issue I mentioned: ztunnel shouldn't get a cert for
itself ( until we have a 'delegated' mode where ztunnel uses its own cert
and doesn't need each workload
cert).
In src/workload.rs
https://github.com/istio/ztunnel/pull/513#discussion_r1185256895:

     tokio::spawn(async move {

         while let Some(workload_identity) = rx.recv().await {

           match cert_manager.fetch_certificate(&workload_identity).await {

           match cert_manager

               .fetch_certificate_pri(&workload_identity, Warmup)

               .await

           {
               Ok(_) => debug!("prefetched cert for {:?}", workload_identity.to_string()),
               Err(e) => error!(
                   "unable to prefetch cert for {:?}, skipping, {:?}",

Unrelated to this PR: should we add some metrics to ztunnel, so admin can
alert on such errors ? We need to do some 'production' review for ztunnel -
make sure it generates enough signals, on-call like docs, etc.
Wouldn't hurt also generating traces if otlp is well supported in rust and
instrumenting the grpc client and server calls ...
—
Reply to this email directly, view it on GitHub
https://github.com/istio/ztunnel/pull/513#pullrequestreview-1413490440,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXN3MUM5CDV7BCWOVH3XEPLUHANCNFSM6AAAAAAXWALFFE
.
You are receiving this because you authored the thread.Message ID:
@.***>


Support training resume and saving best model for SWA

🚀 Feature
To support stop-resume and saving the model based on the best validation performance when using Stochastic weight averaging.
Motivation
If one does not reach the end of the training, the SWA model would not be saved to the checkpoint.
For example:

One may want to save the best validation performance model before overfitting.
The training becomes unstable to reach the final epoch.

I observe that the saved checkpoint is still the original model even if I use an SWA callback.
Pitch

Use SWA model to run validation step instead of the original model.

We may consider to Load SWA weight before validation and Restore original model weight after validation

Save both original model weight and SWA model weight into checkpoint for resume training.

With the concern of say one want to load the model for testing, he/she might expect the model be the SWA weight. Therefore, we can save the SWA weight to the checkpotint['state_dict'] and let the original model weight saved as a callback state.

Alternatives
Additional context
@Borda @MilesCranmer, I do not have much experience on coding neither am I familiar with PyTorch Lightning. would you help? Thx a lot. :wink:

I've been looking into how batch normalization currently works when using SWA to better understand how this should be handled during validation. The mean and variance of inputs to the BatchNorm layers depend on the weights of lower layers so the running estimates computed by the underlying model won't be accurate when the weights are replaced with average weights. Therefore the mean and variance are computed with a full pass over the training set at the end of training, after replacing the weights with the averaged weights. This is done by increasing the number of epochs by one but setting _skip_backward to True for the last epoch to skip the optimization step, and modifying the batch norm layers to reset their mean and variance tensors before this final epoch and setting momentum to None so that they compute a simple cumulative moving average.
The validation passes should probably also update the batch norm parameters in order to accurately represent the model performance. Using the same approach of adding extra non-optimization training epochs before validation seems like it could get quite awkward though. I'm wondering whether it would be simpler to do this without modifying the training loop parameters by just using the training data fetcher directly. I've updated my draft PR to use this approach but I'm not that familiar with the PyTorch code base so am not sure what I might be missing by using the data fetcher directly rather than letting the training loop handle this.
The StochasticWeightAveraging.restore_average_parameters_from_checkpoint method will also need to be updated to take a data module or training data loader so that it can recompute batch norm parameters.

Implemented in https://github.com/Lightning-AI/lightning/pull/9938


Weird bogofile errors in the Emacs binding

Using Rust nightly 2015-04-12 on Ubuntu 14.04 and HEAD of racer, upon completing use std::io::B (the only contents of the file) from Emacs it doesn't work. On the command line it works fine. Tested with a clean emacs environment in only rust-mode and company enabled.
When I debug racer--candidates [(racer.el:56)] (https://github.com/phildawes/racer/blob/master/editors/racer.el#L56), while evaluating the let form of lines I get the following message from racer:
Result: ("PREFIX 13,14,B" "bogofile:1:15: 1:16 error: expected one of `::`, `;`, or `as`, found `<eof>`"
"bogofile:1 use std::io::B" "                         ^" "bogofile:1:15: 1:16 error: expected one of `::`, `;`, or `as`,
found `<eof>`" "bogofile:1 use std::io::B" "                         ^")

Newlines added to clarify the message. But if I invoke it on the command line it prints out a few lines of what apparently are correct results.

Hi @ane,
I haven't been able to reproduce this on my setup. I created a clean user on ubuntu 14.04. My emacs and rust nightly versions are:
$ emacs --version
GNU Emacs 24.3.1
$ rustc --version
rustc 1.0.0-nightly (6436e348e 2015-04-08) (built 2015-04-09)

I'm on rust-mode HEAD and racer HEAD.
I eval'd the following from .emacs file:
;; rust mode
(add-to-list 'load-path "/usr/local/src/rust-mode/")
(autoload 'rust-mode "rust-mode" nil t)
(add-to-list 'auto-mode-alist '("\\.rs\\'" . rust-mode))

;; racer
(setq racer-cmd "/home/clean/racer/target/release/racer")
(setq racer-rust-src-path "/usr/local/src/rust/src/")
(add-to-list 'load-path "/home/clean/racer/editors")
(eval-after-load "rust-mode" '(require 'racer))

;; company
(add-to-list 'load-path "/home/clean/company-0.8.2/")
(autoload 'company-mode "company" nil t)

Pressing tab after
use std::io::B
works ok. I will try pulling a more recent nightly tonight after work, but if things are working on the command line then I suspect that won't be it. Do my versions of the various pieces of software differ substantually?
Thanks,
Phil

A-ha! I found what caused it!
I had rust installed in ~/rust/, so my racer-rust-src-path was set to that. On the command line, the shell racer runs in does the expansion for it, but I suspect that Emacs' (setenv "RUST_SRC_PATH" racer-rust-src-path) does not expand the ~ in it.
I managed to fix it by adding (expand-file-name racer-rust-src-path)) to the setenv` calls. I can submit a PR for this later.

Also out of curiosity: in racer.el, why is company-idle-delay set to nil? I'd like to have automatic completion after the minimum amount of chars are typed, setting the variable forces manual completion.

same here, after adding expand-file-name tab works fine (maybe specify this on example configuration?)


Error calling PublicClientApplication

PublicClientApplication is undefined unless I change the code to:
const myMsal = new msal.PublicClientApplication(config);

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

ID: 5e6e5855-ef79-2759-6773-f3a44886cb14
Version Independent ID: 73154754-ea03-f123-3506-9173f7472322
Content: Configure single-page app - Microsoft identity platform
Content Source: articles/active-directory/develop/scenario-spa-app-configuration.md
Service: active-directory
Sub-service: develop
GitHub Login: @mmacy
Microsoft Alias: marsma

@x509cert
Thanks for your feedback! We will investigate and update as appropriate.

@x509cert
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thanks for the issue, @x509cert. Reassigning to @derisen for fix - thanks, Dogan! #reassign:derisen #label="doc-bug"
@JamesTran-MSFT can you remove the doc-enhancement label?

Resolved by #170792
#please-close


How to declare the order in which Initialisers are applied?

Currently Initialisers are applied in a pseudo-random order. It is simply the order the end up in the list of Resources which depends on how qualified they are. Assuming all are equally qualified the order is simply the order in which the declaration binding was encountered during bootstrapping. While this is a (mostly) deterministic order it is not useful in any way for the user.
Ideally users could give an additional priority for Initialiser of the same qualification level. This is most likely best solved by adding a general feature that allows adding a priority to bindings. Note that this only makes sense and is needed for declarations of type MULTI as other types would mean that equally qualified bindings for the same instance clash.

Implemented by #110


Add a WorkspaceSettings.xcsettings in the RNTester project to turn off new Xcode build system.

Please select one of the following

[ ] I am removing an existing difference between facebook/react-native and Microsoft/react-native :thumbsup:
[ ] I am cherry-picking a change from Facebook's react-native into Microsoft/react-native :thumbsup:
[X] I am making a fix / change for the macOS implementation of react-native
[ ] I am making a change required for Microsoft usage of react-native

Description of changes
The RNTester and its aggregated projects (React, etc) do not build using the new XCode build system, its relies on the Legacy build system.   The Azure DevOps build steps pass a flag to xcodebuild to ensure the legacy build system is used.  But developers must manually change the IDE to the legacy build system.   This change adds a RNTester.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings file and the only key in the file sets BuildSystemType=Original.
Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run


Issues/#748 clean up tests using deprecated methods

This PR addresses GitHub issue: #748.
Briefly describe the changes proposed in this PR:
Ahead of removing deprecated methods from Model, fix the tests that still use those methods.

Everyone: given that my involvement with the project is currently a lot less than it was, I have less time to do proper PR reviews, so I'm relying on your explicit input. Please leave comments or reviews on any pull requests, indicating if you are happy for it to be merged or not.
I will not merge any pull request unless I see a comment/review from at least one other reviewer that he/she is ok with a merge.

This is scheduled for the next major release, so we need to be careful about where this gets merged, to avoid it accidentally ending up in a minor release. Possibly the best way to go about it is to create a 3.0 release branch and merge this PR into that, rather than master. Or we just leave it open for the time being.

Er. Never mind, should have read the description on the PR. This only fixes usage of deprecated methods in the test classes, so this can go into master just fine.

Yes, apologies for the incorrect 'Fixes' in the description. This is a just a test change; after this, the actual fix for #748 is a simple deletion of methods. I'll wait for a 3.0 branch (or master to be bumped) before opening that PR.


LoggingClient::entries returns logs that never finish iterating

When I execute the code below, even though I am using the parameters to limit the number of results, the page never returns.  I've put in debug code, and PageIterator::next is continuously called. But nothing is ever returned.
Environment details

OS: Mac OSX
PHP version: 7.2
Package name and version: google/cloud-logging v1.21.0

Steps to reproduce
    $logging = new Google\Cloud\Logging\LoggingClient([
        'projectId' => 'MY_PROJECT_ID'
    ]);
    $logger = $logging->logger('logging-sample');
    $logs = $logger->entries([
        'pageSize' => 1,
        'resultLimit' => 1,
        // 'orderBy' => 'timestamp desc'
    ]);

    foreach ($logs as $log) {
        // this is never reached
        echo "we retrieved a log!";
    }

Adding some additional filters should help. For example, with the following I get results immediately:
$logs = $logger->entries([
    'filter' => 'timestamp >= "2021-03-01T00:00:00Z"', // assuming my log was written sooner than this
    'pageSize' => 1,
    'resultLimit' => 1,
    // 'orderBy' => 'timestamp desc'
]);

Also, enabling the order by clause to sort by descending should help too, otherwise logs will be searched from oldest to newest which is potentially what is causing the delay.

I'll try that, but the API call itself isn't what takes long. That returns in a few seconds. The issue is (seemingly) that the iterator becomes an infinite loop.

Adding the timestamp filter returns quickly! Closing this and I'll update the samples to include a filter by default.


How can I fix this bug?

When i open minecraft and crashed forge ver: 40.2.0 minecraft ver:1.18.2
crash-2024-05-04_10.28.20-client.txt

NTE doesn't support MTR 4.


Project URL pointing to non-existing GitHub Pages site

The Project URL in setup.py is pointing to https://allenai.github.io/SciSpaCy/ which doesn't exist.
In the absence of that, it should point to https://github.com/allenai/scispacy.
(The Project URL is for example displayed on PyPI)

Thanks! Feel free to open a PR fixing this if you like.


Is there anything about Matterport Preprocessing

Download PanoBasic
Copy stitching_Matterport3D.m to PanoBasic
Modify the directories in stitching_Matterport3D.m, i.e., changing source_dir to the folder of Matterport3D and changing target_dir as the output folder of panorama images and depth maps.
Execute stitching_Matterport3D.m using Matlab.

It seems that stiching_Matterport3D uses stich.m, while stich.m is missing in PanoBasic.
@robertsheng

Please download the code of Matterport3D pre-processing again. I missed some .m files for the first time. We have added them now.

Do you mean that I should copy stich.m to PanoBasic? I'm confused about how PanoBasic and stitching_Matterport3D.m work together,  which is shown in https://github.com/alibaba/UniFuse-Unidirectional-Fusion/blob/fece286301838efef7967d7030ab449e8ea0e449/UniFuse/Matterport3D/README.md.

You should copy all the .m files under the folder Matterport3D to PanoBasic. stitching_Matterport3D.m has to call other .m files by us. The README.md has not been updated yet, although we had added these .m files several days ago.

That's great!

Sorry to bother you again. It seems that you have changed the combineViews.m in PnnoBasic, would you please share the code?

We have updated the code for pre-processing Matterport3D. Please try again according to readme.


Deprecate @bufbuild/* packages

Is your feature request related to a problem? Please describe.
The @bufbuild/connect-* packages still exist on the npm registry and there's no indication of or reference to the new @connectrpc/* packages there. This means that people who usually regularly run pnpm update -irL will not see that updates are indeed happening, just under a different package name ;-)
Describe the solution you'd like
Tag the @bufbuild/connect-* packages as deprecated with a hint pointing at their successor(s).

Good call 🙂
Within the last week, a good chunk of users moved from<EMAIL_ADDRESS>to @connectrpc/connect. We want to ride that momentum for a bit, but definitely deprecated the old names soon.

All Connect packages in the @bufbuild scope have just been deprecated.
To switch to the new scope @connectrpc, you can run npx @connectrpc/connect-migrate@latest. For details, see https://github.com/connectrpc/connect-es/releases/tag/v0.13.1


No common error description for failed element search by condition inside ElementsCollection when calling action

The following test with Selenide 3.7 (and actually all other versions):
public class NotFoundByConditionSelenideElementErrorMessageTest {

    @Test
    public void shouldContainInfoWithAllDetails_WhenCallingAction(){
        open("http://todomvc4tasj.herokuapp.com/");

        // assume that task should have "automatically added dot" in the end
        $("#new-todo").setValue("a").pressEnter();
        $$("#todo-list>li").findBy(exactText("a.")).hover().find(".destroy").click();
        $$("#todo-list>li").shouldBe(empty);
    }
}

implicitly waits common 4 seconds, and then fails with non-informative error:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

While the following test:
public class NotFoundByConditionSelenideElementErrorMessageTest {

    @Test
    public void shouldContainInfoWithAllDetails_WhenCallingAction(){
        open("http://todomvc4tasj.herokuapp.com/");

        // assume that task should have "automatically added dot" in the end
        $("#new-todo").setValue("a").pressEnter();
        $$("#todo-list>li").findBy(exactText("a.")).shouldBe(visible);
    }
}

Fails with:
Element not found {#todo-list>li.filter(exact text 'a.')}
Expected: visible

Screenshot: file:/Users/ayia/projects/tmp/selenide-tests/build/reports/tests/1470245512550.0.png
Timeout: 4 s.
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0

First of all - both errors should contain the same info.
Second - when fixing this bug, I would recommend to improve the message in other aspects.
E.g. It would be much more informative if error message contains the "actual" texts of all elements in collection.
Third - it may have sense to fix this bug along with #243. Because the same code seems to be modified (actually currently there is no much of "such code" to put a fix in, but we could create it in #243, so it will be a good chance to fix this bug too)
Fourth :) - there are many similar edge cases. And I would recommend to test all of them, provide correspondent test coverage, and fix other probable bugs of such type.

@yashaka This issue describes another problem with collections: http://automated-testing.info/t/pomogite-razobratsya-s-problemoj-czikla-v-selenide/10467
Probably we can fix both.

@asolntsev Actually this issue is already known and was filed here more than a year ago.
Here it is: #181
So just mark it as "Let's do it" and we will fix it :)

Merged.


feat: Solid community server Docker image

The Solid community server can be automatically published as a package and run.
Requirements for this action to work:

In the Solid organisation go to: Feature preview and enable "Improved container support"
In the Solid organisation, go to: Settings > Developer settings > Personal access tokens > Generate new token and select scopes write:packages and delete:packages; Generate the token
In the repository's settings, create a secret called CONTAINER_REGISTRY_PERSONAL_ACCESS_TOKEN and paste the Personal access token in it

On all new releases, the workflow should now be triggered.

Also, the package will need to be made public once it is published.
It's done from there:
https://github.com/orgs/solid/packages

Also, the package will need to be made public once it is published.
It's done from there:
https://github.com/orgs/solid/packages

In the Solid organisation, go to: Settings > Developer settings > Personal access tokens > Generate new token and select scopes write:packages and delete:packages; Generate the token

That does not exist for organizations; do you want me to register an application?

In the Solid organisation, go to: Settings > Developer settings > Personal access tokens > Generate new token and select scopes write:packages and delete:packages; Generate the token

That does not exist for organizations; do you want me to register an application?

Oh, correct, we need to:

Enable improved container support in the Organisation: https://github.com/organizations/solid/settings/packages
Also enable Public container creation
We still need to create a personal Access Token from a profile that would have sufficient rights to create a secret on the solid/community-server repo and sufficient rights to publish a package in the organisation.

It could be good at some point to have an overview of generally how permissions are handled in the Solid organisation. And possibly, a solid-admin account could be an adequate place from where to create such an access token.
But it will potentially be a lot of process and difficult to get right. I would suggest maybe creating the Personal Access Token using your account for now. The only security risk I can think of is that someone might be able to get to push a GitHub action that publishes or deletes a package in your account if they have sufficient rights to do so. But that's a little far fetched.

Oh, correct, we need to:

Enable improved container support in the Organisation: https://github.com/organizations/solid/settings/packages
Also enable Public container creation
We still need to create a personal Access Token from a profile that would have sufficient rights to create a secret on the solid/community-server repo and sufficient rights to publish a package in the organisation.

It could be good at some point to have an overview of generally how permissions are handled in the Solid organisation. And possibly, a solid-admin account could be an adequate place from where to create such an access token.
But it will potentially be a lot of process and difficult to get right. I would suggest maybe creating the Personal Access Token using your account for now. The only security risk I can think of is that someone might be able to get to push a GitHub action that publishes or deletes a package in your account if they have sufficient rights to do so. But that's a little far fetched.

3\. We still need to create a personal Access Token from a profile that would have sufficient rights to create a secret on the solid/community-server repo and sufficient rights to publish a package in the organisation.

Mmm, I dislike that though, as this:

Requires that person to give access to all of their repos (I couldn't scope it)
Requires that person to not lose access to the Solid repo.

@matthieubosquet Could you tag someone from Inrupt knowledgeable about Docker? It looks fine to me, but I am not an expert.

3\. We still need to create a personal Access Token from a profile that would have sufficient rights to create a secret on the solid/community-server repo and sufficient rights to publish a package in the organisation.

Mmm, I dislike that though, as this:

Requires that person to give access to all of their repos (I couldn't scope it)
Requires that person to not lose access to the Solid repo.

@matthieubosquet Could you tag someone from Inrupt knowledgeable about Docker? It looks fine to me, but I am not an expert.

Hey @matthieubosquet! I just wrote a Dockerfile too for my work on https://github.com/solid/community-server/pull/568. I think we should probably merge our two work streams, happy to introduce your changes to my PR or vice-versa. There are some things I do differently in mine which I think will better serve our needs, I'll leave comments on your changes with what I think those are.

Hey @matthieubosquet! I just wrote a Dockerfile too for my work on https://github.com/solid/community-server/pull/568. I think we should probably merge our two work streams, happy to introduce your changes to my PR or vice-versa. There are some things I do differently in mine which I think will better serve our needs, I'll leave comments on your changes with what I think those are.

I would suggest using Dockerhub as mentioned in one of the comments.

@pheyvaer I'd publish it to DockerHub as well as soon as we retrieve the credentials!
See also: https://github.com/solid/community-server/pull/561#discussion_r567700819

My branch has gone AWOL, so I created a new Draft pull request there: https://github.com/solid/community-server/pull/580
It is draft for now until the issue of publishing the docker image is resolved.


tests: Run more tests in Travis and catch DB locks

Signed-off-by: Stéphane Graber<EMAIL_ADDRESS>

Note that this expands coverage for all pull requests by a huge amount, however it also makes things much slower, mostly due to the download and repack of the Ubuntu image.
I'll work on server-side lxd images on Thursday as well as introducing a minimal busybox image target to lxd-images.


Hover card to show approval information

Q
A

Bug fix?
no - yes?

New sample?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch.

Thanks for your contribution! Sharing is caring.

Thanks again for the cool sample @sudeepghatak !!


Swift version?

This looks like a great library. Will there be a Swift version? Or does someone know a equivalent library for Swift? I'd use this one with CocoaPods, but it the XLRemoteDataStoreController requires an AFHTTPSessionManager, whereas in Swift I use Alamofire.
Otherwise I'll have to come up with sometime to do everything (data loading, progress showing, endless scrolling, filtering, empty state, error state, etc.) generically myself.
Thanks!

I agree this would be awesome for Swift!  Maybe they're working to convert it like they did with Eureka for XLForm

Glad you find it useful! At Xmartlabs we are using another library to face same problematic, https://github.com/xmartlabs/Opera, fully written in Swift and also developed by Xmartlabs team.
The idea behind Opera is different from XLData, it uses Reactive programming and the code is more swiftly.
Please, try it out and let me know your thoughts.


Unavailable simulator being selected for Snapshot

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 am running fastlane snapshot to create screenshots for multiple devices, including the iPhone 8 Plus. I have accidentally removed the device data from the /Users/X/Library/Developer/CoreSimulator/Devices directory.
Now my snapshot lane is failing with the following error:
File /Users/zandorsmith/Library/Developer/CoreSimulator/Devices/88F09B72-CFCB-499B-AE81-CC4E15BC8896/device.plist not readable!

If I run xcrun simctl list devices I get the following list of devices:

```
== Devices ==
-- iOS 16.4 --
-- iOS 16.4 --
    iPhone 8 Plus (02CC7B8D-1BD7-41F7-AAE7-C2F19FB2F5BD) (Shutdown)
    iPhone 12 Pro Max (5ED6FE74-FFCB-4E78-94B9-C804912B622E) (Shutdown)
    iPhone 13 Pro Max (783AA616-A2F3-49D0-AF2D-97B81207A0D8) (Shutdown)
    iPhone SE (3rd generation) (ED449CB7-4BB3-469D-9840-6D5ABF364ED6) (Shutdown)
    iPhone 14 (89A87809-56A5-4E0A-A749-A65631275058) (Shutdown)
    iPhone 14 Plus (40F9B6A6-548E-450F-BE7E-E58E9FB2035D) (Shutdown)
    iPhone 14 Pro (58284B29-173E-4C7F-A8A6-72C0AD2B58F4) (Shutdown)
    iPhone 14 Pro Max (8E6B87F3-571C-4EFF-ADFE-56C7E52972A1) (Shutdown)
    iPad Pro (12.9-inch) (2nd generation) (AD585A7A-700A-47EB-B922-90024F508702) (Shutdown)
    iPad Pro (12.9-inch) (3rd generation) (F76AA2DA-C089-4C68-8EBF-8A9FC7D6975D) (Shutdown)
    iPad Pro (12.9-inch) (4th generation) (3A5B204B-DAA7-4D6D-9D8A-EA51084FED60) (Shutdown)
    iPad (9th generation) (91D0D56A-4F6B-46E9-883B-12FC376E80CD) (Shutdown)
    iPad Pro (11-inch) (3rd generation) (5C32FA98-A1D2-45D9-9366-D016FE051046) (Shutdown)
    iPad Pro (12.9-inch) (5th generation) (562AC690-29C6-4109-9E42-DAA701715500) (Shutdown)
    iPad Air (5th generation) (6C1BEEE7-F949-481A-AA57-A911D72DF46B) (Shutdown)
    iPad (10th generation) (C0E311C2-5B90-437F-A2AF-D94215C060C0) (Shutdown)
    iPad mini (6th generation) (7DBF8D57-75FE-4FBC-AC54-397A80DFAA0C) (Shutdown)
    iPad Pro (11-inch) (4th generation) (D9ADEDEF-3267-4F47-B5BD-A417C684BD22) (Shutdown)
    iPad Pro (12.9-inch) (6th generation) (3D5BE387-2DD4-4EB2-B473-575A560F5522) (Shutdown)
-- iOS 17.0 --
    iPhone SE (3rd generation) (F639FE36-4A2A-416E-9B8F-51B0455A15C8) (Shutdown)
    iPhone 14 (410392BB-7F41-4FAC-A3DE-6B2EA15D75F2) (Shutdown)
    iPhone 14 Plus (86B4975E-7DD5-4B27-A197-513690071A8F) (Shutdown)
    iPhone 14 Pro (AA6D3C80-311F-4A86-9884-B9A7295ADFB8) (Shutdown)
    iPhone 14 Pro Max (72B379C0-CD01-4559-921D-C5B43B054923) (Shutdown)
    iPad Air (5th generation) (44F2FE43-1461-4A85-975F-127E9946E4B9) (Shutdown)
    iPad (10th generation) (417D2226-A7A7-4505-92D9-8B5425CC2A17) (Shutdown)
    iPad mini (6th generation) (C92C5DC0-98A8-44A0-A835-45FC5960385D) (Shutdown)
    iPad Pro (11-inch) (4th generation) (FB9C9A2D-961A-49A6-A1F6-430D2E660A63) (Shutdown)
    iPad Pro (12.9-inch) (6th generation) (4722F8AA-9333-4F79-9DF1-3E27134990D1) (Shutdown)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-16-1 --
    iPhone 8 Plus (88F09B72-CFCB-499B-AE81-CC4E15BC8896) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPhone 12 Pro Max (41247BF5-D846-414C-98DD-F22B96F700D6) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPhone 13 Pro Max (0D43A209-E13D-4430-B5C5-4ED4C66A425E) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPhone 14 Pro Max (86D4CC54-1253-4A8D-9459-2CADB8D7F0E7) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPad Pro (12.9-inch) (2nd generation) (A805B347-8F24-4588-9115-E71C6BA82FD7) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPad Pro (12.9-inch) (3rd generation) (C872637E-FEBB-4607-A070-C50F211B061F) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPad Pro (12.9-inch) (4th generation) (9AD3D216-C501-4967-B375-5FC774D60EB9) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPad Pro (12.9-inch) (5th generation) (401095FD-B6E1-4A31-82AF-71EC58F0548D) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
    iPad Pro (12.9-inch) (6th generation) (608C4CF2-9298-4706-91B9-1F144C58B686) (Shutdown) (unavailable, runtime profile not found using "System" match policy)
```

Notice the lines in the following truncated version of the output above:
-- iOS 16.4 --
    iPhone 8 Plus (02CC7B8D-1BD7-41F7-AAE7-C2F19FB2F5BD) (Shutdown)
-- Unavailable: com.apple.CoreSimulator.SimRuntime.iOS-16-1 --
    iPhone 8 Plus (88F09B72-CFCB-499B-AE81-CC4E15BC8896) (Shutdown) (unavailable, runtime profile not found using "System" match policy)

I've narrowed down the available simulator selection being done here in the following function:
https://github.com/fastlane/fastlane/blob/614eadf46fe0eb56c90587f97de2043d27187086/fastlane_core/lib/fastlane_core/device_manager.rb#L14
But this function has some logic that should exclude the unavailable simulator, but for some reason that isn't working correctly. It has a perfectly fine and working iPhone 8 Plus simulator available to it but it doesn't want to select it and it still selects the unavailable iPhone 8 Plus simulator.
Command executed

    snapshot(
      workspace: "ShopCrate.xcworkspace",
      concurrent_simulators: false,
      skip_open_summary: is_ci
    )

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

[20:31:02]: ----------------------
[20:31:02]: --- Step: snapshot ---
[20:31:02]: ----------------------
[20:31:02]: Successfully loaded '[REDACTED]/fastlane/Snapfile' 📄
+----------------------------+--------------------------------------------------------------------------------------------------------------------------+
|                                                      Detected Values from './fastlane/Snapfile'                                                       |
+----------------------------+--------------------------------------------------------------------------------------------------------------------------+
| devices                    | ["iPhone 12 Pro Max", "iPhone 8 Plus", "iPad Pro (12.9-inch) (3rd generation)", "iPad Pro (12.9-inch) (2nd generation)"] |
| languages                  | ["nl-NL"]                                                                                |
| scheme                     | [REDACTED]Screenshots                                                                                |
| clear_previous_screenshots | true                                                                                |
| override_status_bar        | true                                                                                |
+----------------------------+--------------------------------------------------------------------------------------------------------------------------+
[20:31:02]: Resolving Swift Package Manager dependencies...
[20:31:02]: $ xcodebuild -resolvePackageDependencies -workspace [REDACTED].xcworkspace -scheme [REDACTED]Screenshots
[20:31:03]: ▸ 2023-08-17 20:31:03.118 xcodebuild[72860:20188569] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
[20:31:03]: ▸ Command line invocation:
[20:31:03]: ▸     /Applications/Xcode-14.3.1.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace [REDACTED].xcworkspace -scheme [REDACTED]Screenshots
[20:31:03]: ▸ User defaults from command line:
[20:31:03]: ▸     IDEPackageSupportUseBuiltinSCM = YES
[20:31:03]: ▸ resolved source packages:
[20:31:03]: $ xcodebuild -showBuildSettings -workspace [REDACTED].xcworkspace -scheme [REDACTED]Screenshots
2023-08-17 20:31:03.707 xcodebuild[72863:20188634] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
[20:31:06]: Command timed out after 3 seconds on try 1 of 4, trying again with a 6 second timeout...
2023-08-17 20:31:06.772 xcodebuild[72897:20188863] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
+--------------------------------------+--------------------------------------------------------------------------------------------------------------------------+
|                                                                  Summary for snapshot 2.214.0                                                                   |
+--------------------------------------+--------------------------------------------------------------------------------------------------------------------------+
| workspace                            | [REDACTED].xcworkspace                                                                                |
| concurrent_simulators                | false                                                                                |
| skip_open_summary                    | true                                                                                |
| devices                              | ["iPhone 12 Pro Max", "iPhone 8 Plus", "iPad Pro (12.9-inch) (3rd generation)", "iPad Pro (12.9-inch) (2nd generation)"] |
| languages                            | ["nl-NL"]                                                                                |
| launch_arguments                     | [""]                                                                                |
| output_directory                     | [REDACTED]/fastlane/screenshots                                        |
| output_simulator_logs                | false                                                                                |
| skip_helper_version_check            | false                                                                                |
| clear_previous_screenshots           | true                                                                                |
| reinstall_app                        | false                                                                                |
| erase_simulator                      | false                                                                                |
| headless                             | true                                                                                |
| override_status_bar                  | true                                                                                |
| localize_simulator                   | false                                                                                |
| app_identifier                       | [REDACTED]                                                                                |
| buildlog_path                        | ~/Library/Logs/snapshot                                                                                |
| clean                                | false                                                                                |
| scheme                               | [REDACTED]Screenshots                                                                                |
| number_of_retries                    | 1                                                                                |
| stop_after_first_error               | false                                                                                |
| result_bundle                        | false                                                                                |
| disable_slide_to_type                | false                                                                                |
| skip_package_dependencies_resolution | false                                                                                |
| disable_package_automatic_updates    | false                                                                                |
| xcodebuild_formatter                 | xcpretty                                                                                |
| use_system_scm                       | false                                                                                |
| xcode_path                           | /Applications/Xcode-14.3.1.app                                                                                |
+--------------------------------------+--------------------------------------------------------------------------------------------------------------------------+
[20:31:10]: Clearing previously generated screenshots
[20:31:10]: Building and running project - this might take some time...
[20:31:10]: Patching simulators '/Users/zandorsmith/Library/Preferences/com.apple.iphonesimulator.plist' to scale to 100%
[20:31:17]: Launch Simulator iPhone 12 Pro Max
[20:31:17]: $ xcrun simctl bootstatus 5ED6FE74-FFCB-4E78-94B9-C804912B622E -b &> /dev/null
[20:31:22]: Waiting 0 seconds for device to fully boot before overriding status bar... Set 'SNAPSHOT_SIMULATOR_WAIT_FOR_BOOT_TIMEOUT' environment variable to adjust timeout
[20:31:22]: Overriding Status Bar
[20:31:22]: $ xcrun simctl status_bar 5ED6FE74-FFCB-4E78-94B9-C804912B622E override --time 2007-01-09T09:41:00+01:00 --dataNetwork wifi --wifiMode active --wifiBars 3 --cellularMode active --operatorName '' --cellularBars 4 --batteryState charged --batteryLevel 100 &> /dev/null
[20:31:23]: Running snapshot on: iPhone 12 Pro Max
[20:31:23]: $ set -o pipefail && xcodebuild -workspace [REDACTED].xcworkspace -scheme [REDACTED]Screenshots -derivedDataPath /var/folders/41/w0bv8v613tz8v7pnfnnvs1fr0000gn/T/snapshot_derived20230817-72773-bls12c -destination 'platform=iOS Simulator,name=iPhone 12 Pro Max,OS=16.4' FASTLANE_SNAPSHOT=YES FASTLANE_LANGUAGE=nl-NL build test | tee /Users/zandorsmith/Library/Logs/snapshot/[REDACTED]Screenshots-[REDACTED]Screenshots.log | xcpretty
[20:31:23]: ▸ Loading...
[20:31:24]: ▸ 2023-08-17 20:31:24.270 xcodebuild[73262:20191052] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
[20:31:24]: ▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:
[20:31:24]: ▸ { platform:iOS Simulator, id:5ED6FE74-FFCB-4E78-94B9-C804912B622E, OS:16.4, name:iPhone 12 Pro Max }
[20:31:24]: ▸ { platform:iOS Simulator, id:5ED6FE74-FFCB-4E78-94B9-C804912B622E, OS:16.4, name:iPhone 12 Pro Max }
[COMPILATION REDACTED]
[20:31:45]: Running Tests: ▸ Touching [REDACTED].framework (in target '[REDACTED]' from project 'Pods')
[20:31:45]: Running Tests: ▸ Touching Connectivity.framework (in target 'Connectivity' from project 'Pods')
[20:31:45]: ▸ Processing [REDACTED]-Info.plist
[20:31:45]: ▸ Linking [REDACTED]
[20:31:45]: ▸ Linking Sentry
[20:31:45]: Running Tests: ▸ Touching [REDACTED].framework (in target '[REDACTED]' from project 'Pods')
[20:31:45]: Running Tests: ▸ Touching Sentry.framework (in target 'Sentry' from project 'Pods')
[20:31:45]: ▸ Processing Pods-[REDACTED]-Info.plist
[20:31:45]: Running Tests: ▸ Touching Pods_[REDACTED].framework (in target 'Pods-[REDACTED]' from project 'Pods')
[20:31:45]: ▸ Running script '[CP] Check Pods Manifest.lock'
[COMPILATION REDACTED]
[20:31:58]: ▸ Processing Info.plist
[20:31:58]: ▸ Compiling [REDACTED]_vers.c
[20:31:58]: ▸ Linking [REDACTED]
[20:31:58]: ▸ Running script '[CP] Embed Pods Frameworks'
[20:31:59]: Running Tests: ▸ Touching [REDACTED].app (in target '[REDACTED]' from project '[REDACTED]')
[20:31:59]: ▸ Processing Info.plist
[20:32:04]: ▸ Linking [REDACTED]Screenshots
[20:32:04]: ▸ Running script 'Run Script'
[20:32:04]: Running Tests: ▸ Touching [REDACTED]Screenshots.xctest (in target '[REDACTED]Screenshots' from project '[REDACTED]')
[20:32:05]: ▸     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target '[REDACTED]Screenshots' from project '[REDACTED]')
[20:32:05]: ▸ Build Succeeded
[20:32:05]: ▸ --- xcodebuild: WARNING: Using the first of multiple matching destinations:
[20:32:05]: ▸ { platform:iOS Simulator, id:5ED6FE74-FFCB-4E78-94B9-C804912B622E, OS:16.4, name:iPhone 12 Pro Max }
[20:32:05]: ▸ { platform:iOS Simulator, id:5ED6FE74-FFCB-4E78-94B9-C804912B622E, OS:16.4, name:iPhone 12 Pro Max }
[20:32:05]: ▸ Linking [REDACTED]
[20:32:06]: ▸ Linking [REDACTED]
[20:32:06]: ▸ Running script '[CP] Embed Pods Frameworks'
[20:32:06]: ▸ Linking [REDACTED]Screenshots
[20:32:07]: ▸ Running script 'Run Script'
[20:32:07]: ▸     Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target '[REDACTED]Screenshots' from project '[REDACTED]')
[20:32:21]: ▸ All tests
[20:32:21]: ▸ Test Suite [REDACTED]Screenshots.xctest started
[20:32:21]: ▸ ScreenshotTests
[20:32:53]: ▸     ✓ testScreenshots (31.680 seconds)
[20:32:53]: ▸ 	 Executed 1 test, with 0 failures (0 unexpected) in 31.680 (31.682) seconds
[20:32:53]: ▸
[20:32:56]: ▸ 2023-08-17 20:32:56.555 xcodebuild[73262:20191052] [MT] IDETestOperationsObserverDebug: 49.392 elapsed -- Testing started completed.
[20:32:56]: ▸ 2023-08-17 20:32:56.555 xcodebuild[73262:20191052] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
[20:32:56]: ▸ 2023-08-17 20:32:56.555 xcodebuild[73262:20191052] [MT] IDETestOperationsObserverDebug: 49.392 sec, +49.392 sec -- end
[20:32:56]: ▸ Test Succeeded
[20:32:58]: Clearing Status Bar Override
[20:32:58]: $ xcrun simctl status_bar 5ED6FE74-FFCB-4E78-94B9-C804912B622E clear &> /dev/null
[20:32:58]: Copying '[REDACTED]/fastlane/screenshots/nl-NL/iPhone 12 Pro Max-01 [REDACTED].png'...
[20:32:58]: Copying '[REDACTED]/fastlane/screenshots/nl-NL/iPhone 12 Pro Max-02 [REDACTED].png'...
[20:32:58]: Copying '[REDACTED]/fastlane/screenshots/nl-NL/iPhone 12 Pro Max-03 [REDACTED].png'...
[20:32:58]: Copying '[REDACTED]/fastlane/screenshots/nl-NL/iPhone 12 Pro Max-04 [REDACTED].png'...
[20:33:01]: Patching simulators '/Users/zandorsmith/Library/Preferences/com.apple.iphonesimulator.plist' to scale to 100%
+------------------------------------+-----------------------------------------------------------------------------+
|                                                   Lane Context                                                   |
+------------------------------------+-----------------------------------------------------------------------------+
| DEFAULT_PLATFORM                   | ios                                                                         |
| XCODES_XCODE_PATH                  | /Applications/Xcode-14.3.1.app/Contents/Developer                           |
| PLATFORM_NAME                      | ios                                                                         |
| LANE_NAME                          | ios screenshots                                                             |
| SIGH_PROFILE_TYPE                  | app-store                                                                   |
| MATCH_PROVISIONING_PROFILE_MAPPING | {"[REDACTED]"=>"match AppStore [REDACTED]"} |
+------------------------------------+-----------------------------------------------------------------------------+
[20:33:06]: File /Users/zandorsmith/Library/Developer/CoreSimulator/Devices/88F09B72-CFCB-499B-AE81-CC4E15BC8896/device.plist not readable!
+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 2    | xcodes           | 0           |
| 3    | is_ci            | 0           |
| 4    | match            | 0           |
| 5    | is_ci            | 0           |
| 💥   | snapshot         | 124         |
+------+------------------+-------------+
[20:33:06]: fastlane finished with errors
Looking for related GitHub issues on fastlane/fastlane...
Found no similar issues. To create a new issue, please visit:
https://github.com/fastlane/fastlane/issues/new
Run fastlane env to append the fastlane environment to your issue
bundler: failed to load command: fastlane ([REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane)
[REDACTED]/vendor/bundle/ruby/3.1.0/gems/CFPropertyList-3.0.6/lib/cfpropertylist/rbCFPropertyList.rb:333:in load': \e[31m[!] File /Users/zandorsmith/Library/Developer/CoreSimulator/Devices/88F09B72-CFCB-499B-AE81-CC4E15BC8896/device.plist not readable!\e[0m (IOError) 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/CFPropertyList-3.0.6/lib/cfpropertylist/rbCFPropertyList.rb:238:in initialize'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:282:in new' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:282:in plist'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:59:in rescue in devicetype' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:56:in devicetype'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:151:in block in get_device_type_with_simctl' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:148:in map'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:148:in get_device_type_with_simctl' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:109:in verify_devices_share_os'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:77:in destination' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:15:in generate'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:85:in launch_simultaneously' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:70:in block (3 levels) in take_screenshots_simultaneously'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:69:in each' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:69:in block (2 levels) in take_screenshots_simultaneously'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in each' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in each_with_index'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in block in take_screenshots_simultaneously' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:45:in each'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:45:in take_screenshots_simultaneously' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/runner.rb:45:in work'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/actions/capture_ios_screenshots.rb:14:in run' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:229:in chdir' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:229:in execute_action'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing'
from Fastfile:57:in block (2 levels) in parsing_binding' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/lane.rb:33:in call'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:49:in block in execute' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:45:in chdir'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:45:in execute' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:110:in block (2 levels) in run'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:354:in run'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:43:in start' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in take_off'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/bin/fastlane:23:in <top (required)>' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane:25:in load'
from [REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane:25:in <top (required)>' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in load'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in kernel_load' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:23:in run'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:486:in exec' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:31:in dispatch' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:25:in start' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/exe/bundle:48:in block in <top (required)>'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/friendly_errors.rb:120:in with_friendly_errors' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/exe/bundle:36:in <top (required)>'
from /opt/homebrew/bin/bundle:25:in load' 	from /opt/homebrew/bin/bundle:25:in '
[REDACTED]/vendor/bundle/ruby/3.1.0/gems/CFPropertyList-3.0.6/lib/cfpropertylist/rbCFPropertyList.rb:333:in load': File /Users/zandorsmith/Library/Developer/CoreSimulator/Devices/88F09B72-CFCB-499B-AE81-CC4E15BC8896/device.plist not readable! (IOError) 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/CFPropertyList-3.0.6/lib/cfpropertylist/rbCFPropertyList.rb:238:in initialize'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:282:in new' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:282:in plist'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/simctl-1.6.10/lib/simctl/device.rb:57:in devicetype' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:151:in block in get_device_type_with_simctl'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:148:in map' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:148:in get_device_type_with_simctl'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:109:in verify_devices_share_os' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:77:in destination'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/test_command_generator.rb:15:in generate' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:85:in launch_simultaneously'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:70:in block (3 levels) in take_screenshots_simultaneously' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:69:in each'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:69:in block (2 levels) in take_screenshots_simultaneously' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in each'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in each_with_index' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:46:in block in take_screenshots_simultaneously'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:45:in each' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/simulator_launchers/simulator_launcher.rb:45:in take_screenshots_simultaneously'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/snapshot/lib/snapshot/runner.rb:45:in work' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/actions/capture_ios_screenshots.rb:14:in run'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:263:in block (2 levels) in execute_action' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/actions/actions_helper.rb:69:in execute_action'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:255:in block in execute_action' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:229:in chdir'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:229:in execute_action' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/fast_file.rb:159:in method_missing' 	from Fastfile:57:in block (2 levels) in parsing_binding'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:45:in chdir' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/runner.rb:45:in execute'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/lane_manager.rb:47:in cruise_lane' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:110:in block (2 levels) in run' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/command.rb:187:in call'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/command.rb:157:in run' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/runner.rb:444:in run_active_command'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:124:in run!' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/commander-4.6.0/lib/commander/delegates.rb:18:in run!'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:354:in run' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/commands_generator.rb:43:in start'
from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/fastlane/lib/fastlane/cli_tools_distributor.rb:123:in take_off' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/gems/fastlane-2.214.0/bin/fastlane:23:in <top (required)>'
from [REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane:25:in load' 	from [REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane:25:in <top (required)>'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in load' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:58:in kernel_load'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli/exec.rb:23:in run' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:486:in exec'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/command.rb:27:in run' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in invoke_command'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor.rb:392:in dispatch' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:31:in dispatch'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/vendor/thor/lib/thor/base.rb:485:in start' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/cli.rb:25:in start'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/exe/bundle:48:in block in <top (required)>' 	from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/lib/bundler/friendly_errors.rb:120:in with_friendly_errors'
from /opt/homebrew/lib/ruby/gems/3.1.0/gems/bundler-2.3.22/exe/bundle:36:in <top (required)>' 	from /opt/homebrew/bin/bundle:25:in load'
from /opt/homebrew/bin/bundle:25:in `'

Environment

🚫 fastlane environment 🚫
Stack

Key
Value

OS
13.4

Ruby
3.1.2

Bundler?
true

Git
git version 2.39.2 (Apple Git-143)

Installation Source
[REDACTED]/vendor/bundle/ruby/3.1.0/bin/fastlane

Host
macOS 13.4 (22F66)

Ruby Lib Dir
/opt/homebrew/Cellar/ruby/3.1.2_1/lib

OpenSSL Version
OpenSSL 1.1.1s  1 Nov 2022

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
14.3.1

Swift Version
5.8.1

System Locale

Error

No Locale with UTF8 found 🚫

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)
xcodes(
  select_for_current_build_only: true
)

platform :ios do

  lane :screenshots do
    match(type: "appstore", readonly: is_ci)
    snapshot(
      workspace: "[REDACTED].xcworkspace",
      concurrent_simulators: false,
      skip_open_summary: is_ci
    )
  end

end

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

itc_team_id("[REDACTED]") # App Store Connect Team ID
team_id("[REDACTED]") # Developer Portal Team ID

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.214.0
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

error_highlight
0.3.0

did_you_mean
1.6.1

bundler
2.3.22

pathname
0.2.0

rake
13.0.6

rexml
3.2.5

CFPropertyList
3.0.6

concurrent-ruby
1.2.2

i18n
1.12.0

minitest
5.17.0

tzinfo
2.0.6

zeitwerk
2.6.7

activesupport
<IP_ADDRESS>

public_suffix
4.0.7

addressable
2.8.4

httpclient
2.8.3

json
2.6.3

algoliasearch
1.27.5

artifactory
3.0.15

atomos
0.1.3

aws-eventstream
1.2.0

aws-partitions
1.786.0

aws-sigv4
1.6.0

jmespath
1.6.2

aws-sdk-core
3.178.0

aws-sdk-kms
1.71.0

aws-sdk-s3
1.130.0

babosa
1.0.4

claide
1.1.0

fuzzy_match
2.0.4

nap
1.1.0

netrc
0.11.0

ffi
1.15.5

ethon
0.16.0

typhoeus
1.4.0

cocoapods-core
1.12.1

cocoapods-deintegrate
1.0.5

cocoapods-downloader
1.6.3

cocoapods-plugins
1.0.0

cocoapods-search
1.0.1

cocoapods-trunk
1.6.0

cocoapods-try
1.2.0

colored2
3.1.2

escape
0.0.4

fourflusher
2.3.1

gh_inspector
1.1.3

molinillo
0.8.0

ruby-macho
2.5.1

nanaimo
0.3.0

xcodeproj
1.22.0

cocoapods
1.12.1

colored
1.2

highline
2.0.3

commander
4.6.0

declarative
0.0.20

digest-crc
0.6.5

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.8.1

emoji_regex
3.2.3

excon
0.100.0

faraday-em_http
1.0.0

faraday-em_synchrony
1.0.0

faraday-excon
1.1.0

faraday-httpclient
1.0.1

multipart-post
2.3.0

faraday-multipart
1.0.4

faraday-net_http
1.0.1

faraday-net_http_persistent
1.2.0

faraday-patron
1.0.0

faraday-rack
1.0.0

faraday-retry
1.0.3

ruby2_keywords
0.0.5

faraday
1.10.3

http-cookie
1.0.5

faraday-cookie_jar
0.0.7

faraday_middleware
1.2.0

fastimage
2.2.7

jwt
2.7.1

memoist
0.16.2

multi_json
1.15.0

os
1.1.4

signet
0.17.0

googleauth
1.6.0

mini_mime
1.1.2

trailblazer-option
0.1.2

uber
0.1.0

representable
3.2.0

retriable
3.1.2

webrick
1.8.1

google-apis-core
0.11.0

google-apis-androidpublisher_v3
0.45.0

google-apis-playcustomapp_v1
0.13.0

google-apis-iamcredentials_v1
0.17.0

google-apis-storage_v1
0.19.0

google-cloud-env
1.6.0

google-cloud-errors
1.3.1

google-cloud-core
1.6.0

google-cloud-storage
1.44.0

mini_magick
4.12.0

naturally
2.2.1

optparse
0.1.1

plist
3.7.0

rubyzip
2.3.2

security
0.1.3

simctl
1.6.10

terminal-notifier
2.0.0

unicode-display_width
1.8.0

terminal-table
1.8.0

tty-screen
0.8.1

tty-cursor
0.7.1

tty-spinner
0.9.3

word_wrap
1.0.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.1

xcode-install
2.8.1

generated on: 2023-08-17

It looks like you're encountering an issue with Fastlane's snapshot action due to the unavailability of a specific simulator device. The error message suggests that the device.plist file for an iPhone 8 Plus simulator is not readable.
To address this issue, you can try the following steps:
You mentioned that you accidentally removed the device data from the CoreSimulator directory. It's possible that the simulator state became inconsistent. You can try cleaning up your simulators using the following Fastlane command:
fastlane snapshot reset_simulators
This command will reset your simulators to a clean state, which may resolve the issue.
Specify the Simulator: You can explicitly specify the simulator you want to use in your Fastfile by adding a devices parameter to your snapshot block. For example:
snapshot(
workspace: "ShopCrate.xcworkspace",
devices: [
"iPhone 8 Plus (02CC7B8D-1BD7-41F7-AAE7-C2F19FB2F5BD)"
],
concurrent_simulators: false,
skip_open_summary: is_ci
)
Replace the device identifier with the one that corresponds to an available simulator.
Update Fastlane: Ensure you are using the latest version of Fastlane by running:
fastlane update_fastlane
Upgrading to the latest version may resolve any known issues related to simulator selection.
Check Simulator Configuration: Verify that the unavailable simulator (with the problematic device.plist) is not explicitly specified or referenced elsewhere in your Fastlane configuration.
Check Xcode Configuration: Ensure that your Xcode installation and configuration are up-to-date and consistent with your project requirements.
Recreate Unavailable Simulator: If none of the above steps work, you might consider recreating the unavailable simulator manually through Xcode's simulator manager. Give it a different name or identifier and then try to specify that in your Fastlane configuration.
If none of these steps resolve the issue, you may need to provide additional context or investigate further into your specific setup, as it could be related to project-specific configuration or a potential bug in Fastlane or Xcode. Additionally, checking the Fastlane GitHub repository for similar issues and solutions may be helpful.

Running fastlane snapshot reset_simulators solved the issue.
Thank you bot user for helping me fix my issue. Reported for advertisement.


Fix tiny logging/comment/naming bugs in virtualservice status test

Rename function from virtualServiceCalledTimes to proberCalledTimes, which is more accurate
Fix a comment and an error log that both assumed n always == 1.

/assign @nak3 @JRBANCEL since zhimin and mustafa probably won't look at this


Suggestion: default the pie chart to non-blank lines (that is including comments), and provide a toggle

I suggest that the pie chart should default to showing to non-blank lines including comments, rather than as currently only the actual lines containing code. I think it's the most useful metric, since comments aren't easier to write than code, and a lack of comments also suggests less fleshed out code IMHO. It might be useful to also provide a toggle for those who prefer other metrics like the old one.

I like the idea.
Since I have to replace counting tool (is inactive) i willl implement it


Non-equidistant integration for gMAM

The current bottleneck in gMAM is the interpolation step which has to be doen every optimization step. This also makes it that any other solver than gradient descent and LBGFS is not usable in the current implementation with Optim.jl. The reason why we have to interpolate is to make the path equidistant to allow for easy integration needed for the action. Is this the only reason? In case so we could opt for non-equidistant integration to compute the action.

having equidistant of gMAM is a feature rather than a bug.  In the gMAM rework #25 the interpolation is not the bottleneck anymore


Should TransformToStart also be removed？

TransformToStart in featureAssociation.cpp acts like TransformToEnd. I wonder it should also be removed.

yes


[BEAM-1353] Easy PTransform style guide compliance fixes

This leaves out the more complex / potentially-controversial ones.
R: @dhalperi

Coverage decreased (-0.006%) to 69.599% when pulling e4ff84309210127d3a1ad746cb9755db07704a09 on jkff:style-guide into 8c1a577fe52ffd02e57f3e65924aced10e38a82a on apache:master.

I've revised my changes to the "glorified combine" transforms according to the beam-dev thread.

Changes Unknown when pulling 3e46f943ed09f51b24af0ac012092ed6f6eaa387 on jkff:style-guide into ** on apache:master**.

Changes Unknown when pulling 3e46f943ed09f51b24af0ac012092ed6f6eaa387 on jkff:style-guide into ** on apache:master**.

Coverage increased (+0.001%) to 69.136% when pulling 74ab2e00d82b6a6db6a4ba5d151dd3d00138184d on jkff:style-guide into 16736a6b612ba38b19694ae2a23dea7f5fab1563 on apache:master.

Coverage decreased (-0.02%) to 69.182% when pulling a3e26ddad5457c620c21bb389a298353863f9866 on jkff:style-guide into a41afdc68ae71b478872596ee60f813be7e78557 on apache:master.

Thanks Eugene. I will merge when green.

Coverage increased (+0.07%) to 69.197% when pulling 0739a38997c02a2e2f015c237be03c5e1a9a2e3b on jkff:style-guide into 352af855edf9e07978d1d6d2a61fde372f927165 on apache:master.

retest this please

Coverage increased (+0.06%) to 69.193% when pulling 0739a38997c02a2e2f015c237be03c5e1a9a2e3b on jkff:style-guide into 352af855edf9e07978d1d6d2a61fde372f927165 on apache:master.

OK, this failure is pretty clearly a flake, as well as the previous one.

+1 will merge when i get back. Any other committer welcome to preempt me
On Tue, Feb 28, 2017 at 18:38 Eugene Kirpichov<EMAIL_ADDRESS>wrote:

OK, this failure is pretty clearly a flake, as well as the previous one.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/1943#issuecomment-283227700, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgITyDEP2rNZgjJL0zLSNQLk9GjG8B_ks5rhNobgaJpZM4L6Q0m
.


Explorer Crashes

Type: Bug
Everytime when I launch vs code of open a new project vs code explorer which placed on left side bar close autometically after some time like 5 to 6 sec. Its happens each time its very annoying and distract me and loose my mental peace and productivity, please fix the issue asap.
VS Code version: Code 1.77.0 (7f329fe6c66b0f86ae1574c2911b681ad5a45d63, 2023-03-29T10:02:16.981Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx   (8 x 2096)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
9.95GB (4.32GB free)

Process Argv
--crash-reporter-id 945dfca0-6539-44fb-9711-bd91ffc5ed36

Screen Reader
no

VM
0%

Extensions (18)

Extension
Author (truncated)
Version

codesnap
adp
1.3.4

vscode-styled-jsx
bla
2.1.1

bracket-pair-color-dlw
Bra
0.0.6

simple-react-snippets
bur
1.2.7

multi-cursor-case-preserve
Car
1.0.5

dscodegpt
Dan
2.1.3

prettier-vscode
esb
9.10.4

auto-close-tag
for
0.5.14

auto-rename-tag
for
0.1.10

copilot
Git
1.79.10634

path-autocomplete
ion
1.23.1

material-icon-theme
PKi
4.25.0

svg-preview
Sim
2.8.3

swdc-vscode
sof
2.7.0

code-spell-checker
str
2.20.4

errorlens
use
3.8.0

highlight-matching-tag
vin
0.11.0

vscode-import-cost
wix
3.3.0

(1 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1:30587005
2e4cg342:30602488
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
vsccsb:30705552
functionswalk:30687959
pythonms35:30701012
pythonclientmvcf:30705674

Please use the Start Extension Bisect command to investigate whether the problem is being caused by one of your extensions

I have the same. The only thing that has changed is the update:
Version: 1.77.0
Commit: 7f329fe6c66b0f86ae1574c2911b681ad5a45d63
Date: 2023-03-29T10:05:35.165Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 6.2.6-76060206-generic
Sandboxed: No

@Darpan-favfly Disable dscodegpt extension.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

I have the same. The only thing that has changed is the update:
Version: 1.77.0 Commit: 7f329fe Date: 2023-03-29T10:05:35.165Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: <IP_ADDRESS>-electron.0 OS: Linux x64 6.2.6-76060206-generic Sandboxed: No
I did the Start Extension Bisect but no extension could be found as a cause for the problem. The issue is in Code. (according to Start Extension Bisect).
Update: downgraded to Version: 1.76.2 Commit: ee2b180 Date: 2023-03-14T17:57:21.103Z Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: <IP_ADDRESS>-electron.0 OS: Linux x64 6.2.6-76060206-generic Sandboxed: No
but I have the same issue.
Update-2: I did a Start Extension Bisect again. This time, it came out that the extension https://github.com/davila7/code-gpt-docs was the culprit. I added an issue there: davila7/code-gpt-docs#107
Uninstalled the extension, updated again to 1.77.0, and the issue is gone.

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines. If you don't know which extension is causing the problem, you can run Help: Start extension bisect from the command palette (F1) to help identify the problem extension.
Happy Coding!

I did, see https://github.com/microsoft/vscode/issues/179232#issuecomment-1497154706.
So it is an issue from https://github.com/davila7/code-gpt-docs, not Code.


Publish for azps-4.2.0

Docs Build status updates of commit 612642c:
:clock10: Full build: the average full build time is 27 min(s) 23 sec(s), this is based on the last 400 build(s) for this repository.

Docs Build status updates of commit 612642c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-4.2.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-4.2.0)

docs-conceptual/azps-4.2.0/uninstall-az-ps.md
:white_check_mark:Succeeded
View (azps-4.2.0)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


895 copy changes to project create fields

Changes
Content changes to new project screen including hints and errors.

[x] Title change (for voluntary / in-voluntary projects) Done already
[x] Involuntary academies description mentions Directive academy order Done already
[x] Voluntary conversions mention Academy order Done already
[x] School URN / Trust UKPRN hint text says what URN / UKPRN is then gives link on new line
[x] Advisory board conditions hint is Enter details of conditions that must be met before the school can convert.
[x] Advisory board notes and date goes above provisional conversion date
[x] Provisional conversions date hint is The provisional conversion date is always the first day of the month.
[x] Provisional conversion date no entry error is Enter a month and year for the provisional conversion date, like 01 2023. If you do not know the provisional conversion date then enter a date that is at least six months after the advisory board..
[x] School Sharepoint hint text should be Provide a link to the SharePoint folder for this school. This is where you save all the relevant school documents.
[x] Trust Sharepoint hint text should be Provide a link to the SharePoint folder for the incoming trust. This is where you save all the relevant trust documents.
[x] Handover comment hint is Provide a brief overview of how the project has progressed so far, including any issues or concerns.
[x] Handover comment dropdown guidance is summary =What to make comments about content = Useful things to comment on include whether the:

 - provisional conversion date has been agreed by the school, trust and local authority
- local authority proforma has been received or requested
[x] Advisory date no entry error is Enter a date for the advisory board, like 01 04 2023
[x] Add missing GDS tags to add project page

Checklist

[x] Attach this pull request to the appropriate card in Trello.
[x] Update the CHANGELOG.md if needed.

Checked the content with Rich. Looks good to me.


Thanks

Not an issue but just wanted to say thanks it been +1 year i've searched a solution to install ms store apps externally because my ms store was broken. Hope your app will stay up:)

hello, glad to hear that it was helpful to you!


enhance: Add zh locale.

This PR add zh locale.

Closing in favor of #23. Please open an issue if the translation should be better, as I can't confirm which one is better


Prepare release notes for v1.6.0-beta.4

No changelog updates this time, fixes a regression from beta.3 https://github.com/containerd/nerdctl/pull/551

Btw. Will there be still many beta versions before cutting to RC? Looks that K3s is planning to do quote big refactor for 1.23.x versions because containerd 1.6.0 is still in beta: https://github.com/k3s-io/k3s/pull/4623

Even if v1.6.0 was out of beta we wouldn't be able to avoid the refactor, as there are several modules that 1.6.0 uses that conflict with what Kubernetes 1.23 and etcd 3.5 require.


Ubiquiti UVC: finds cameras, but unable to get image from cameras.

Home Assistant release (hass --version): 0.29.7 (Hassbian 1.0)
Python release (python3 --version): 3.4.2
Component/platform: camera / uvc
Description of problem:
the uvc platform seems to find the two cameras connected to my NVR and the frontend shows two new groups for the cameras but show (error loading image) for both. Log is showing a error:
Oct 11 03:47:00 HASSelhoff hass[25659]: return self.handle(camera)
Oct 11 03:47:00 HASSelhoff hass[25659]: File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/__init__.py", line 175, in handle
Oct 11 03:47:00 HASSelhoff hass[25659]: response = camera.camera_image()
Oct 11 03:47:00 HASSelhoff hass[25659]: File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/uvc.py", line 153, in camera_image
Oct 11 03:47:00 HASSelhoff hass[25659]: if not self._login():
Oct 11 03:47:00 HASSelhoff hass[25659]: File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/camera/uvc.py", line 111, in _login
Oct 11 03:47:00 HASSelhoff hass[25659]: addrs = [caminfo['host'], caminfo['internalHost']]
Oct 11 03:47:00 HASSelhoff hass[25659]: KeyError: 'internalHost'

Expected:
Images instead of (Error Loading Images)
Problem-relevant configuration.yaml entries and steps to reproduce:
configuration.yaml:
camera:
  platform: uvc
  nvr: <IP_ADDRESS>
  port: 7080
  key: 1234

Additional info:
I'm l running UniFi NVR 3.1.1
I'm running my cameras on a seperate network. i.e. The cameras are on their own network and the NVR is on the same network as HASS
While trying to debug this, I stepped thru some lines of uvc.py interactively and found that the caminfo does indeed lack the internalHost key. I post the keys that did return below.
caminfo.keys()
dict_keys(['zones', 'lastRecordingId', 'videoProperties', 'mapSettings', 'channelSettings', 'firmwareBuild', 'osdSettings', 'uuid', 'recordingSettings', 'serverUuid', 'conflictedHost', 'name', 'systemInfo', 'upgradeStatus', 'host', 'state', 'model', 'username', 'ispSettings', 'firmwareVersion', 'videoSettings', 'status', 'isInFallbackMode', 'adoptionCode', 'lastSeen', 'mac', 'uptime', 'deleted', 'okToOverrideConflict', 'provisioned', '_id', 't', 'sshPort', 'deviceSettings', 'updateTimestamp', 'scheduleUuid', 'lastRecordingStartTime', 'protocolVersion', 'isConnecting', 'managementRequested', 'targetFirmwareCode', 'managed', 'networkStatus'])

Let me know if there's more I can submit. Thanks!

This looks like it's related to https://github.com/home-assistant/home-assistant/issues/2979

This issue still exists in HA version 0.35.2.

Also experiencing this issue.


Trying to fix the parsing of .tex and .txt file extensions when parsing templates

I was trying to create a template for some latex and noticed that it wouldn't parse. The other option of .tpl removed my lsp and syntax highlighting, so I wanted to see why it wouldn't parse
From what I saw, within the function temp.get_temp.list() the call to vim.filetype.match({ filename = name }) will not match .tex and .txt file extensions by design (see https://www.reddit.com/r/neovim/comments/1cb4kty/vimfiletypematch_returns_nil/) for why.
Because of this, templates in latex .tex, and also incidentally .txt files, will not parse requiring you to use .tpl files with a header comment of ;; tex to be read properly.
To fix this I reimplemented the functionality of vim.filetype.match and adjusted the code according to the new function's api.
If you have time feel free to review and adjust the code as needed or contact me if I made a mistake in understanding when adjusting the code.
Thank you for your time.

I noticed that when pasting multiple versions of the template into one file there was a nil exception so I added a guarding if statement to mitigate that. It looks as though the output is correct none the less

thanks I think we need a test here

No problem!


[Table] Adjust padding on empty state placement

What package is this for?

[x] React
[ ] Angular

Summary
In the current implementation of an empty state of a table, adjust the left padding of the components to align with the table empty state guidance .
Current alignment:

Proposed alignment:

large default breakpoint - with grid overlay
Large default breakpoint - without grid overlay
Looks alright here, I could not get it to respond to my browser size in the storybook to test the smallest "large" breakpoint (673px) so I mocked it up for a test.

Smallest lg breakpoint - with grid overlay

Smallest lg breakpoint - without grid overlay

@dianatran18 Didn't Carbon state that the grid was not intended for a components internal layout, only for its placement on a page?


lean/persistent repo clonning for discover step

Currently, tmt clones the whole git repository to discover tests every time the plan is run.
Since some repositories are extremely large, I was wondering whether it wouldn't make sense to have an option to either do a 'sparse' clone, or to have a persistent-ish directory with the cloned repo and do a git pull instead of clone.

Since #1253 we are using shallow clone if 'ref' is not used. Is that enough for your use case?

I see, I was using 'ref' for testing. Shallow clone by default sounds good. Thanks Lukas.


Korean Single Speaker Speech Analysis

ML-Crate Repository (Proposing new issue)
:red_circle: Project Title : Korean Single Speaker Speech Analysis
:red_circle: Aim : Create a ML model which will predict the speech from the given input.
:red_circle: Dataset : https://www.kaggle.com/bryanpark/korean-single-speaker-speech-dataset
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.
Hello, ML-Crate contributors, this issue is only for the contribution purposes and allocated only to the participants of SWOC 2.0 Open Source Program and JWOC '22 Open Source Program.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.
This issue is only for 'SWOC' and 'JWOC' contributors of 'ML-Crate' project.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Participant ID :
Approach for this Project :
What is your participant role?

[ ] SWOC 2.0 Participant.
[ ] JWOC 2022 Participant.
[ ] Contributor

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Name:Harsh khandelwal
GitHub link:https://github.com/harshkh-001
Participation I'd:NA
Approach: First I will take data than do extracting features on it than I will choose and train a model then I will evaluate and integrate it .
Event: JWOC

Use the following models for model creation,

Random forest
Decision tree
Logistic
Linear
Lasso
Ridge
MLP
XgBoost
Gradient Boosting

Issue assigned to you @harshkh-001


I need a help.

Tell me please, can I change http headers, or set mine before making OpenAsync?
Thank you.


Fix: atlas connector

Describe your changes :

I worked on improving atlas connector
Fix: #1308

Type of change :

[x] Bug fix
[x] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Not sure about the migrations though, are we handling it somewhere?

Not sure about the migrations though, are we handling it somewhere?

@ayush-shah I think for this case we will not require migration script because we never created a service for atlas!