remove elasticsearch-async instrumentation

elasticsearch-async has been deprecated and its functionality brought
into elasticsearch-py proper.
Tests for this module have already been removed in #949

:bug: Flaky test report
:grey_exclamation: There are test failures but not known flaky tests.
Test stats :test_tube:

Test
Results

Failed
72

Passed
11061

Skipped
7933

Total
19066

:broken_heart: Tests Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Build Cause: [Pull request #950 opened]

Start Time: 2020-10-26T13:34:35.818+0000

Duration: 24 min 35 sec

Test stats :test_tube:

Test
Results

Failed
72

Passed
11061

Skipped
7933

Total
19066

Test errors
Expand to view the tests failures

    > Show only the first 10 test failures

Name: Initializing / Test / Python-python-3.7-0 / test_ping – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.164
Error Details: TypeError: 'noop' object is not iterable

Name: Initializing / Test / Python-python-3.7-0 / test_ping – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.029
Error Details: test teardown failure

Name: Initializing / Test / Python-python-3.7-0 / test_info – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.041
Error Details: TypeError: 'noop' object is not iterable

Name: Initializing / Test / Python-python-3.7-0 / test_info – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.012
Error Details: test teardown failure

Name: Initializing / Test / Python-python-3.7-0 / test_create – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.606
Error Details: TypeError: 'noop' object is not iterable

Name: Initializing / Test / Python-python-3.7-0 / test_create – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.08
Error Details: test teardown failure

Name: Initializing / Test / Python-python-3.7-0 / test_search_body – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.377
Error Details: TypeError: 'noop' object is not iterable

Name: Initializing / Test / Python-python-3.7-0 / test_search_body – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.068
Error Details: test teardown failure

Name: Initializing / Test / Python-python-3.7-0 / test_count_body – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.293
Error Details: TypeError: 'noop' object is not iterable

Name: Initializing / Test / Python-python-3.7-0 / test_count_body – tests.instrumentation.asyncio_tests.elasticsearch_async_client_tests

Age: 1
Duration: 0.052
Error Details: test teardown failure

Steps errors
Expand to view the steps failures

  > Show only the first 10 steps failures

Name: Shell Script

Description: [2020-10-26T13:45:21.444Z] + ./tests/scripts/docker/run_tests.sh python-3.7 elasticsearch-7
[2020-1

Duration: 1 min 45 sec

Start Time: 2020-10-26T13:45:21.157+0000

log

Name: Shell Script

Description: [2020-10-26T13:46:14.812Z] + ./tests/scripts/docker/run_tests.sh python-3.7 elasticsearch-7
[2020-1

Duration: 1 min 40 sec

Start Time: 2020-10-26T13:46:14.524+0000

log

Name: Error signal

Description:

Duration: 0 min 0 sec

Start Time: 2020-10-26T13:47:08.454+0000

log

Name: Shell Script

Description: [2020-10-26T13:43:51.820Z] + ./tests/scripts/docker/run_tests.sh python-3.7 elasticsearch-6
[2020-1

Duration: 1 min 55 sec

Start Time: 2020-10-26T13:43:51.531+0000

log

Name: Shell Script

Description: [2020-10-26T13:44:59.215Z] + ./tests/scripts/docker/run_tests.sh python-3.7 elasticsearch-6
[2020-1

Duration: 1 min 42 sec

Start Time: 2020-10-26T13:44:58.924+0000

log

Name: Error signal

Description:

Duration: 0 min 0 sec

Start Time: 2020-10-26T13:45:57.323+0000

log

Name: Shell Script

Description: [2020-10-26T13:46:45.564Z] + ./tests/scripts/docker/run_tests.sh python-3.8 elasticsearch-6
[2020-1

Duration: 1 min 49 sec

Start Time: 2020-10-26T13:46:45.274+0000

log

Name: Shell Script

Description: [2020-10-26T13:47:40.866Z] + ./tests/scripts/docker/run_tests.sh python-3.8 elasticsearch-6
[2020-1

Duration: 1 min 36 sec

Start Time: 2020-10-26T13:47:40.579+0000

log

Name: Error signal

Description:

Duration: 0 min 0 sec

Start Time: 2020-10-26T13:48:26.462+0000

log

Name: Shell Script

Description: [2020-10-26T13:45:27.385Z] + ./tests/scripts/docker/run_tests.sh python-3.8 elasticsearch-7
[2020-1

Duration: 1 min 44 sec

Start Time: 2020-10-26T13:45:27.057+0000

log

Log output
Expand to view the last 100 lines of log output

[2020-10-26T13:57:18.395Z] ERROR: No such saved stash ‘coverage-python-3.9-rc-mysql_connector-newest’
[2020-10-26T13:57:18.508Z] ERROR: No such saved stash ‘coverage-python-3.9-rc-pymysql-newest’
[2020-10-26T13:57:18.957Z] ERROR: No such saved stash ‘coverage-python-3.9-rc-asyncpg-newest’
[2020-10-26T13:57:19.090Z] ERROR: No such saved stash ‘coverage-python-3.9-rc-tornado-newest’
[2020-10-26T13:57:19.535Z] ERROR: No such saved stash ‘coverage-python-3.9-rc-httpx-newest’
[2020-10-26T13:57:28.620Z] + python3 -m coverage combine
[2020-10-26T13:58:07.371Z] + python3 -m coverage xml
[2020-10-26T13:58:07.419Z] [Cobertura] Skipping Cobertura coverage report as build was not SUCCESS or better ...
[2020-10-26T13:58:07.419Z]
[2020-10-26T13:58:07.820Z] + curl -sLO https://code.jquery.com/jquery-3.3.1.slim.min.js
[2020-10-26T13:58:08.121Z] + curl -sLO<EMAIL_ADDRESS>[2020-10-26T13:58:08.335Z] Archiving artifacts
[2020-10-26T13:58:08.505Z] Stage "Building packages" skipped due to earlier failure(s)
[2020-10-26T13:58:08.598Z] Stage "Integration Tests" skipped due to earlier failure(s)
[2020-10-26T13:58:08.687Z] Stage "Benchmarks" skipped due to earlier failure(s)
[2020-10-26T13:58:08.898Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-10-26T13:58:08.935Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-10-26T13:58:09.031Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-10-26T13:58:09.123Z] Stage "Prepare Release" skipped due to earlier failure(s)
[2020-10-26T13:58:09.446Z] Running on Jenkins in /var/lib/jenkins/workspace/thon_apm-agent-python-mbp_PR-950
[2020-10-26T13:58:09.596Z] [INFO] getVaultSecret: Getting secrets
[2020-10-26T13:58:09.833Z] Masking supported pattern matches of $VAULT_ADDR or $VAULT_ROLE_ID or $VAULT_SECRET_ID
[2020-10-26T13:58:10.769Z] + chmod 755 generate-build-data.sh
[2020-10-26T13:58:10.769Z] + ./generate-build-data.sh https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-950/ https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-950/runs/1 FAILURE 1414682
[2020-10-26T13:58:11.019Z] INFO: curl https://apm-ci.elastic.co/blue/rest/organizations/jenkins/pipelines/apm-agent-python/apm-agent-python-mbp/PR-950/runs/1/steps/?limit=10000 -o steps-info.json


JS console error appears after configuring two-factor authentication

Steps

Go to the "Configure Addons" page for your user settings
Enable 2-factor authentication
Refresh the page
Check your JS console

Expected
No console errors
Actual
The error message "No elements matching selector '#twoFactorScope'" appears in the console.

That's less than ideal. Everything works otherwise, though?

This is fixed now. @samanehsan Can you please verify this on production?


Metrics for comparing targets and predictions

Create metrics.cpp and metrics.hpp, similar to losses.* but for comparing targets to predictions.
E.g. accuracy:
double accuracy_score(datavec targets, datavec predictions){
    // todo: verify that target and predict have same size
    double correct = 0;
    for (int i = 0; i < targets.size(); i++){
        if (targets[i] == predictions[i]){
            correct += 1;
        }
    }
    return correct/targets.size();
}

Which metrics would we want? Here is sklearn's list for reference: https://scikit-learn.org/stable/modules/model_evaluation.html

accuracy is all we need to begin with. Precision, Recall, F1-score and the likes would be nice to have, but nothing we need. We're focusing on binary classification for the MVP, and accuracy is plenty to make comparisons between methods and runs.


pandas to_dict has wrong return type for most orient arguments

Environment data

Language Server version: 2020.9.7
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Anaconda Python 3.7.5

Expected behaviour
No error
Actual behaviour
from typing import Dict, Any
import pandas as pd

df = pd.DataFrame({"x": [1, 2, 3]})

dic: Dict[str, Any] = df.to_dict(orient="split")

reports
Expression of type "List[Dict[_str, Any]]" cannot be assigned to declared type "Dict[str, Any]"
  "List[Dict[_str, Any]]" is incompatible with "Dict[str, Any]"

Issue here is that the return type of to_dict depends on the orient argument.
Possible solution:
diff frame.pyi.ORIG frame.pyi
202c202
<         self, orient: Union[_str, Literal["dict", "list", "series", "split", "records", "index"]] = ..., into: Hashable = ...,
---
>         self, orient: Literal["records"] = ..., into: Hashable = ...,
203a204,207
>     @overload
>     def to_dict(
>         self, orient: Union[_str, Literal["dict", "list", "series", "split", "index"]] = ..., into: Hashable = ...,
>     ) -> Dict[_str, Any]: ...

This issue has been fixed in version 2020.10.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#2020100-7-october-2020


notworking: hardwareBackButtonClose: true

hardwareBackButtonClose: true
on ionic 1.3.0 with modals
not working

Hello! Thanks for opening am issue with us! Would you mind posting a code sample, plunker or codepen that we can use to reproduce this issue?

well its simple just make modal and givin in options hardwareBackButtonClose: true
and by touching back button nothing happens...
this problem starts with this new 1.3.0

@emps,
Can you provide the context for this?  We made a change to how history navigation works in 1.3.  Right now, this worksforme in a basic slide-in slide-out navigation app.  I just tested this.
Is your app a tabs app?  Can you provide a codepen showing the situation?
Thanks,
Dan

ok i need to build it , i have tabs plus left menu .. navigation with hardBack button works
but to close modal is not working
so to build this i need some time will try finish this in next hours,  thanks

ok thats strange my project that was built with 1.2.4 and updated to 1.3.0 has the problem..
but i built now demo project from clean new project based on 1.3.0 and there is no any problems
i will try play with this a bit more and update u guys

There were some changes to the way history works so I am not surprised.  Perhaps we should reconsider them.
Thanks,
Dan

ok thanks after readd platforms problem solved, i think we can close this issue


Addition of KeyPressed method

IsKeyPressed works well, but I end up with code like:
if ebiten.IsKeyPressed(ebiten.KeyEnter) {
	gbio.rows[0] &= 0x7
} else {
	gbio.rows[0] |= 0x8
}

if ebiten.IsKeyPressed(ebiten.KeyShift) {
	gbio.rows[0] &= 0xB
} else {
	gbio.rows[0] |= 0x5
}

... etc

It could be helpful to have a KeyPressed or LastKeyPressed method which returns a Key. Then we could have:
switch ebiten.KeyPressed() {
case ebiten.KeyEnter:
	// Enter key pressed
case ebiten.KeyShift:
	// Shift key pressed
}

What would KeyPressed return if multiple keys are pressed?

What do you think of KeysPressed returning a struct?
// KeysPressed returns a struct of booleans representing what keys were pressed
keys := ebiten.KeysPressed()
switch {
case keys.enter:
	// Enter pressed
	fallthrough
case keys.shift:
	// Shift pressed
default:
	// Default behavior
}

Yes, you are right :) Thanks for the suggestion, I will close.


Related items component

Headed sections of related items.
Accepts an array of sections. Each section can have a title, url, id and a list of related items.
Each item is a hash with a title and url. If the url is external, a rel value can also be provided.

Create a related-items component based on188e526 and on core stylesheets
Care must be taken when using the component so that navigation is always
correctly labelled (pattern based on http://tink.uk/screen-readers-aria-roles-html5-support/). When passing in a section id, use this to add an id attribute and a labelledby attribute. This is in favour of generating an id (eg. by parameterising the title) so that the component isn't using rails specific
features.

Trello
paired with @fofr
cc @dsingleton

The ruby bits look good to me. :+1:

@gemmaleigh @tombye I've simplified the styles in 7d9fa7e
I haven't added the print mixin as it appears to not yet be imported for components – weirdly the print mixin doesn't come from the toolkit as I expected.

I haven't added the print mixin as it appears to not yet be imported for components – weirdly the print mixin doesn't come from the toolkit as I expected.

Component print styles work differently, see https://github.com/alphagov/static/pull/638 (this is something we may want to re-examine, I can't remember the reason for going with this vs print mixin right now)

@dsingleton @tombye Updated print styles in edd2e45

Looks good to me then :+1:

The component API looks good, markup/styling looks good.
Couple of small comments. The only one i'd want to resolve before merging is the use of rel.
As discussed offline with @fofr having a list of objects, rather than an object of key/value (as we do for the metadata component) is a lot more robust. Arrays preserve order, unlike objects, and support additional values (eg, rel in this case).
We've already run into problems with the later on the metadata component, so I think thats a pattern we should avoid for future components (and consider moving away from with metadata).


redirect to login page after selecting the tariff plan

Expected Behavior
redirect to the application after selecting the tariff plan
Current Behavior
after choosing a tariff, a redirect to the login route is made.
Steps to Reproduce

enable freemium mode
select tariff plan
redirect to login

Context

Package Version: v12.1
Laravel Version: v6.18.38
PHP Version: 7.2.2

in AuthShopify middleware after choosing a tariff plan
only charge_id comes to $request and user authorization is reset.
Failure Logs
AuthShopify - handle - dd($next($request):
Symfony\Component\Debug\Exception\FatalThrowableError: Call to a member function isFreemium() on null in file /home/user/public_html/testProject/vendor/osiset/laravel-shopify/src/ShopifyApp/Http/Middleware/Billable.php on line 50

You're most likely experiencing the cookie issue that others are based on this information.


fix: Azure provider error parsing

Fixes an issue in the cleanup of azure error messages that could cause a panic.
fixes #311

The Azure tests don't run automatically on PRs, triggered a separate job for it here to verify


pkg/strings: regression: strings.Join fails with new evaluator

What version of CUE are you using (cue version)?

$ cue version
cue version +c6ade67 linux/amd64

Does this issue reproduce with the latest release?
Yes
What did you do?
exec cue eval
-- x.cue --
package x

import "strings"

x: strings.Join(strings.Split("test", "")[1:], "")

What did you expect to see?
x: "est"

(per v0.2.2)
What did you see instead?
error in call to strings.Join: not properly initialized (state: 0, value: *adt.ListMarker)

This issue has been migrated to https://github.com/cue-lang/cue/issues/500.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.


Fix Texture Picking 2

Fix #712

The test suit is now fully working: https://travis-ci.com/omichel/webots/jobs/215459551

:+1:


bump operator base image to 4.13 / 1.28.0

fixes: https://github.com/kiali/kiali/issues/6220

@jshaughn I believe we want this in the upcoming release - upgraded base images makes CVEs go away :)


Subscribe to a page

New thing
We have quite a few pages which it'd be good for users to "subscribe" to. Examples of that are like the Workers changelog, R2 changelog and other such pages.
it would be awesome to subscribe with both an email + webhook URL
This can be done with internal tools but I'm not too familiar with them. I'd love to help out if you need it and would like to do this.
Personally, I think this would be a really nice win for users. Tracking these updates are hard right now

Ooh, super cool idea.
Seems like this SO post provides some ideas that could be useful.
In terms of the overall technical help, the email / webhook subscription might be a bit out of my wheelhouse.... but I have played around a bit with the github API and looking for commit histories to specific files, so theoretically could be a bit more helpful there.

There are definitely some limitations with the new implementation (we're really just providing links to the GH-generated RSS feed), but it should provide at least some visibility into file / folder-level changes.
You add the RSS icon to the top toolbar + the <head> meta by specifying either rss: file (just watch that file) or rss: folder (watch all changes in the folder) in the page frontmatter.
These links will be broken if you attempt to do a rss: file on an _index page, which I think would be a relative edge case.


Update fritzconnection to 1.2.0 (HA 0.105)

Sadly a couple of things changed (in a strange manner). Eg. values for on/off are now booleans. Sometimes.
It was a bit of a hassle to test everything and I made some fishy changes, but it works on my setup now.
Tested:

Get value of call deflection
Set value of call deflection
Get port forward
Set port forward
Get device profile
Set device profile
Get guest wifi state
Set guest wifi state
Connectivity sensor

@AaronDavidSchneider could you test it with your setup as well? And feel free to review and provide feedback!
Closes #46
Closes #63

Homeassistant 0.105 is now available


How to add pagination without reloading Swiper component

Hi,
has anyone add pagination to swiper that works just like FlatList? I mean now, when i want to add new paginated data to Swiper I must rerender Swiper component to show this data. Anyone find better solution, without rerendering after new pagination data came from backend?

same for me

Dynamic cards list should be fixed in v2.0.11. Here is the PR. If it doesn't fix your issue, we'll have to dig into it:<


Fixes bad link

Zipkin server includes collector functionality, so might be the best link target.

Thanks for catching this!


Import error "The provided scene thumbnail does not have a valid file extension"

Hi!
I wanted to import a module that I exported with your module. However I encounter the following error I'm afraid. It imported some scene's, but skipped a lot of them! :-(

Here's the file I'm trying to import: https://drive.google.com/file/d/1Pyp3DpTijLkH6VG921AcS7dMJWHFsf8n/view?usp=sharing

Update, selecting just two scene's instead of all the scene's helped and imported them. Interestingly, both of the scenes get skipped in the bulk import.

I had to regenerate the thumbnails from the scene's and now it's importing succesfully!


XCODE 9 UrlError.Code error

Error occurred - Type 'URLError.Code' does not conform to protocol 'Hashable' in struct Retry
public var retryErrorCodes: Set<URLError.Code> = [.timedOut,
.cannotFindHost,
.cannotConnectToHost,
.dnsLookupFailed,
.networkConnectionLost
]

Cannot reproduce this anymore.


Create a bat file to install and run.

[ ] Create a bat file to install and run.
If I manage to run it, I will write a bat file I have already created for https://github.com/nagadomi/nunif

https://github.com/Atharva-Phatak/Manga-Colorizer/pull/11


I2S_CONF_RX_START

What does I2S_CONF_RX_START do in the gen_carrier() and clr_carrier()

I2S word clock is used to generate carrier frequency. I2S_CONF_RX_START is a bit flag to enable I2S functionality.


arm64 CLI support

Hey, I'm trying to deploy a docker image that uses prisma-client-rust to aws (in an arm64 machine) and seem to get problems.
Looks like it's downloading the incorrect cli distribution. I'll investigate more later
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   timestamp   |                                                                                message                                                                                |
|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|<PHONE_NUMBER>570 | [cargo-make] INFO - cargo make 0.35.11                                                                                |
|<PHONE_NUMBER>705 | [cargo-make] INFO - Build File: Makefile.toml                                                                                |
|<PHONE_NUMBER>705 | [cargo-make] INFO - Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>705 | [cargo-make] INFO - Profile: development                                                                                |
|<PHONE_NUMBER>705 | [cargo-make] INFO - Running Task: legacy-migration                                                                                |
|<PHONE_NUMBER>713 | [cargo-make] INFO - Running Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>731 | Downloading https://prisma-photongo.s3-eu-west-1.amazonaws.com/prisma-cli-3.12.0-linux.gz to /root/.cache/prisma/binaries/cli/3.12.0/prisma-cli-linux                                                                                |
|<PHONE_NUMBER>575 | Downloading https://binaries.prisma.sh/all_commits/22b822189f46ef0dc5c5b503368d1bee01213980/debian-openssl-1.1.x/query-engine.gz to /root/.cache/prisma/binaries/cli/3.12.0/22b822189f46ef0dc5c5b503368d1bee01213980/prisma-query-engine-debian-openssl-1.1.x                 |
|<PHONE_NUMBER>926 | Downloading https://binaries.prisma.sh/all_commits/22b822189f46ef0dc5c5b503368d1bee01213980/debian-openssl-1.1.x/migration-engine.gz to /root/.cache/prisma/binaries/cli/3.12.0/22b822189f46ef0dc5c5b503368d1bee01213980/prisma-migration-engine-debian-openssl-1.1.x         |
|<PHONE_NUMBER>172 | Downloading https://binaries.prisma.sh/all_commits/22b822189f46ef0dc5c5b503368d1bee01213980/debian-openssl-1.1.x/introspection-engine.gz to /root/.cache/prisma/binaries/cli/3.12.0/22b822189f46ef0dc5c5b503368d1bee01213980/prisma-introspection-engine-debian-openssl-1.1.x |
|<PHONE_NUMBER>396 | Downloading https://binaries.prisma.sh/all_commits/22b822189f46ef0dc5c5b503368d1bee01213980/debian-openssl-1.1.x/prisma-fmt.gz to /root/.cache/prisma/binaries/cli/3.12.0/22b822189f46ef0dc5c5b503368d1bee01213980/prisma-prisma-fmt-debian-openssl-1.1.x                     |
|<PHONE_NUMBER>492 | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 8, kind: Uncategorized, message: "Exec format error" }', /usr/local/cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/89df398/cli/src/prisma_cli.rs:40:18                            |
|<PHONE_NUMBER>492 | stack backtrace:                                                                                |
|<PHONE_NUMBER>492 |    0:     0xaaaaabca3448 - std::backtrace_rs::backtrace::libunwind::trace::hb72fa83b7a29f1a7                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5                                                                                |
|<PHONE_NUMBER>492 |    1:     0xaaaaabca3448 - std::backtrace_rs::backtrace::trace_unsynchronized::hbfda2dacac316277                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5                                                                                |
|<PHONE_NUMBER>492 |    2:     0xaaaaabca3448 - std::sys_common::backtrace::_print_fmt::hbdc981bfed4ce765                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:66:5                                                                                |
|<PHONE_NUMBER>492 |    3:     0xaaaaabca3448 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h0ee8113e53dd9501                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:45:22                                                                                |
|<PHONE_NUMBER>492 |    4:     0xaaaaabcc5d68 - core::fmt::write::hfeafa1b3f4cde44b                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/fmt/mod.rs:1190:17                                                                                |
|<PHONE_NUMBER>492 |    5:     0xaaaaabc9d00c - std::io::Write::write_fmt::h8e498245d185b12b                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/io/mod.rs:1657:15                                                                                |
|<PHONE_NUMBER>492 |    6:     0xaaaaabca5718 - std::sys_common::backtrace::_print::hfb8a354270630015                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:48:5                                                                                |
|<PHONE_NUMBER>492 |    7:     0xaaaaabca5718 - std::sys_common::backtrace::print::h0f1c3f701be8c977                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:35:9                                                                                |
|<PHONE_NUMBER>492 |    8:     0xaaaaabca5718 - std::panicking::default_hook::{{closure}}::hcaba4274d385417f                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:295:22                                                                                |
|<PHONE_NUMBER>492 |    9:     0xaaaaabca5360 - std::panicking::default_hook::h89cecd906305ec2a                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:314:9                                                                                |
|<PHONE_NUMBER>492 |   10:     0xaaaaabca5d98 - std::panicking::rust_panic_with_hook::haded46e2df0f4fd6                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:698:17                                                                                |
|<PHONE_NUMBER>492 |   11:     0xaaaaabca5b04 - std::panicking::begin_panic_handler::{{closure}}::he5e693fe5e4ac6b4                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:588:13                                                                                |
|<PHONE_NUMBER>492 |   12:     0xaaaaabca3900 - std::sys_common::backtrace::__rust_end_short_backtrace::hc44d591e7ee285ad                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:138:18                                                                                |
|<PHONE_NUMBER>492 |   13:     0xaaaaabca583c - rust_begin_unwind                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5                                                                                |
|<PHONE_NUMBER>492 |   14:     0xaaaaab9df7b4 - core::panicking::panic_fmt::hb04515a4b04219bf                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14                                                                                |
|<PHONE_NUMBER>492 |   15:     0xaaaaab9df858 - core::result::unwrap_failed::hf84f08a5e231dad5                                                                                |
|<PHONE_NUMBER>492 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1749:5                                                                                |
|<PHONE_NUMBER>492 |   16:     0xaaaaaba19b94 - prisma_client_rust_cli::prisma_cli::main::hff2c3c979abb2add                                                                                |
|<PHONE_NUMBER>492 |   17:     0xaaaaab9e3f40 - prisma_client_rust_cli::run::h3ae65fb93de00ed2                                                                                |
|<PHONE_NUMBER>492 |   18:     0xaaaaab9dff80 - std::sys_common::backtrace::__rust_begin_short_backtrace::h928511540dabcec3                                                                                |
|<PHONE_NUMBER>492 |   19:     0xaaaaab9dff6c - std::rt::lang_start::{{closure}}::hf2c6bacf05ad61ee                                                                                |
|<PHONE_NUMBER>492 |   20:     0xaaaaabca2c50 - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hdb45ce9c36440355                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/ops/function.rs:259:13                                                                                |
|<PHONE_NUMBER>493 |   21:     0xaaaaabca2c50 - std::panicking::try::do_call::h7e8bb9a5488c007b                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40                                                                                |
|<PHONE_NUMBER>493 |   22:     0xaaaaabca2c50 - std::panicking::try::hcc55e9ed15610d77                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19                                                                                |
|<PHONE_NUMBER>493 |   23:     0xaaaaabca2c50 - std::panic::catch_unwind::hcf59f097cd8ee652                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14                                                                                |
|<PHONE_NUMBER>493 |   24:     0xaaaaabca2c50 - std::rt::lang_start_internal::{{closure}}::h8fbfb8ff9e6d08fc                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:48                                                                                |
|<PHONE_NUMBER>493 |   25:     0xaaaaabca2c50 - std::panicking::try::do_call::hb9473916547b0c2e                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40                                                                                |
|<PHONE_NUMBER>493 |   26:     0xaaaaabca2c50 - std::panicking::try::hfd0be8714fe2c175                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19                                                                                |
|<PHONE_NUMBER>493 |   27:     0xaaaaabca2c50 - std::panic::catch_unwind::hd13ef362c9d4275f                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14                                                                                |
|<PHONE_NUMBER>493 |   28:     0xaaaaabca2c50 - std::rt::lang_start_internal::hb2f3ce624f838b60                                                                                |
|<PHONE_NUMBER>493 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:20                                                                                |
|<PHONE_NUMBER>493 |   29:     0xaaaaab9dff3c - main                                                                                |
|<PHONE_NUMBER>493 |   30:     0xffff9dcca218 - __libc_start_main                                                                                |
|<PHONE_NUMBER>493 |   31:     0xaaaaab9dfe34 - <unknown>                                                                                |
|<PHONE_NUMBER>498 | [cargo-make] ERROR - Error while executing command, exit code: 101                                                                                |
|<PHONE_NUMBER>498 | [cargo-make] WARN - Build Failed.                                                                                |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The CLI likely isn't distributed for arm64 linux, though I'd have to confirm with the Prisma team. I'd suggest generating the client outside of docker in an x86 environment, and copying it in. What docker image are you building inside of?

I'm using the normal rust:latest image. The problem is, that I need to run the CLI within the docker image, since I'm using it for the migrations as well.

Do you plan on applying the migrations at build time or run time? It's generally recommended to do so at run time before your application starts, since usually your database won't be located inside the docker image or be available at build time

Yep, at runtime. I have a multi-stage dockerfile, with one stage building the application and the runtime stage copying the target folder and then running the executables

Would you mind sharing your dockerfile? I'm confused as to why this would be failing

Sure
FROM rust:latest AS maker
RUN cargo install --no-default-features --force cargo-make

FROM maker AS chef
RUN cargo install cargo-chef --locked

FROM chef AS planner
WORKDIR /app
COPY . .
RUN cargo chef prepare --recipe-path recipe.json

FROM chef AS builder
WORKDIR /app
COPY --from=planner /app/recipe.json recipe.json
# Build dependencies - this is the caching Docker layer!
RUN cargo chef cook --release --recipe-path recipe.json
COPY . .
RUN cargo build --release

FROM maker as runner
WORKDIR /app
COPY . .
COPY --from=builder /app/target/release ./target/release
# RUN cargo build --release
CMD ["cargo", "make", "migrate-run-prod"]

The Make task that is being run:

[tasks.migrate-run-prod]
script = ["./target/release/prisma-cli migrate deploy --schema=./packages/prisma/schema.prisma", "./target/release/seed", "./target/release/service"]

Look like it's not an issue with your Dockerfile 😄
arm64 builds of the Prisma engines are available, but builds of the CLI are only available for 3.13.0, with the naming scheme of the CLI download urls set to change (https://github.com/prisma/prisma-client-go/issues/717). This should be fixed in conjunction with #52 when Prisma 3.13.0 is supported. For now I don't have a solution for you except to use x64 machines.

@John0x Can you try installing prisma_client_rust and primsa_client_rust_cli from rev = "cfeed593903e59fe6690879197065369d4bbad98" instead of tag = "0.4.1"?

@John0x Can you try installing prisma_client_rust and primsa_client_rust_cli from rev = "cfeed593903e59fe6690879197065369d4bbad98" instead of tag = "0.4.1"?

Thanks for your effort :)
Error:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   timestamp   |                                                                                message                                                                                |
|---------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|<PHONE_NUMBER>413 | [cargo-make] INFO - cargo make 0.35.11                                                                                |
|<PHONE_NUMBER>553 | [cargo-make] INFO - Build File: Makefile.toml                                                                                |
|<PHONE_NUMBER>553 | [cargo-make] INFO - Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>553 | [cargo-make] INFO - Profile: development                                                                                |
|<PHONE_NUMBER>553 | [cargo-make] INFO - Running Task: legacy-migration                                                                                |
|<PHONE_NUMBER>564 | [cargo-make] INFO - Running Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>587 | Downloading https://prisma-photongo.s3-eu-west-1.amazonaws.com/prisma-cli-3.13.0-linux.gz to /root/.cache/prisma/binaries/cli/3.13.0/prisma-cli-linux-arm64                                                                                |
|<PHONE_NUMBER>676 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/query-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-query-engine-linux-arm64-openssl-1.1.x                 |
|<PHONE_NUMBER>743 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/migration-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-migration-engine-linux-arm64-openssl-1.1.x         |
|<PHONE_NUMBER>990 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/introspection-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-introspection-engine-linux-arm64-openssl-1.1.x |
|<PHONE_NUMBER>213 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/prisma-fmt.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-prisma-fmt-linux-arm64-openssl-1.1.x                     |
|<PHONE_NUMBER>302 | thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 8, kind: Uncategorized, message: "Exec format error" }', /usr/local/cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/cfeed59/cli/src/prisma_cli.rs:40:18                                      |
|<PHONE_NUMBER>302 | stack backtrace:                                                                                |
|<PHONE_NUMBER>302 |    0:     0xaaaabca7c8b4 - std::backtrace_rs::backtrace::libunwind::trace::hb72fa83b7a29f1a7                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5                                                                                |
|<PHONE_NUMBER>302 |    1:     0xaaaabca7c8b4 - std::backtrace_rs::backtrace::trace_unsynchronized::hbfda2dacac316277                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5                                                                                |
|<PHONE_NUMBER>302 |    2:     0xaaaabca7c8b4 - std::sys_common::backtrace::_print_fmt::hbdc981bfed4ce765                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:66:5                                                                                |
|<PHONE_NUMBER>302 |    3:     0xaaaabca7c8b4 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h0ee8113e53dd9501                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:45:22                                                                                |
|<PHONE_NUMBER>302 |    4:     0xaaaabca9f1d4 - core::fmt::write::hfeafa1b3f4cde44b                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/fmt/mod.rs:1190:17                                                                                |
|<PHONE_NUMBER>302 |    5:     0xaaaabca76478 - std::io::Write::write_fmt::h8e498245d185b12b                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/io/mod.rs:1657:15                                                                                |
|<PHONE_NUMBER>302 |    6:     0xaaaabca7eb84 - std::sys_common::backtrace::_print::hfb8a354270630015                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:48:5                                                                                |
|<PHONE_NUMBER>302 |    7:     0xaaaabca7eb84 - std::sys_common::backtrace::print::h0f1c3f701be8c977                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:35:9                                                                                |
|<PHONE_NUMBER>302 |    8:     0xaaaabca7eb84 - std::panicking::default_hook::{{closure}}::hcaba4274d385417f                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:295:22                                                                                |
|<PHONE_NUMBER>302 |    9:     0xaaaabca7e7cc - std::panicking::default_hook::h89cecd906305ec2a                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:314:9                                                                                |
|<PHONE_NUMBER>302 |   10:     0xaaaabca7f204 - std::panicking::rust_panic_with_hook::haded46e2df0f4fd6                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:698:17                                                                                |
|<PHONE_NUMBER>302 |   11:     0xaaaabca7ef70 - std::panicking::begin_panic_handler::{{closure}}::he5e693fe5e4ac6b4                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:588:13                                                                                |
|<PHONE_NUMBER>302 |   12:     0xaaaabca7cd6c - std::sys_common::backtrace::__rust_end_short_backtrace::hc44d591e7ee285ad                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:138:18                                                                                |
|<PHONE_NUMBER>302 |   13:     0xaaaabca7eca8 - rust_begin_unwind                                                                                |
|<PHONE_NUMBER>302 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5                                                                                |
|<PHONE_NUMBER>302 |   14:     0xaaaabc7ba634 - core::panicking::panic_fmt::hb04515a4b04219bf                                                                                |
|<PHONE_NUMBER>303 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14                                                                                |
|<PHONE_NUMBER>304 |   15:     0xaaaabc7ba6d8 - core::result::unwrap_failed::hf84f08a5e231dad5                                                                                |
|<PHONE_NUMBER>304 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/result.rs:1749:5                                                                                |
|<PHONE_NUMBER>306 |   16:     0xaaaabc7f2888 - prisma_client_rust_cli::prisma_cli::main::h7122ddbd9e7b0666                                                                                |
|<PHONE_NUMBER>306 |   17:     0xaaaabc7bdb68 - prisma_client_rust_cli::run::h5d8df653dd21d947                                                                                |
|<PHONE_NUMBER>306 |   18:     0xaaaabc7bae00 - std::sys_common::backtrace::__rust_begin_short_backtrace::h5e611b9f00cba9d4                                                                                |
|<PHONE_NUMBER>306 |   19:     0xaaaabc7badbc - std::rt::lang_start::{{closure}}::h6d4af5e7ad6e2d00                                                                                |
|<PHONE_NUMBER>306 |   20:     0xaaaabca7c0bc - core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &F>::call_once::hdb45ce9c36440355                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/ops/function.rs:259:13                                                                                |
|<PHONE_NUMBER>306 |   21:     0xaaaabca7c0bc - std::panicking::try::do_call::h7e8bb9a5488c007b                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40                                                                                |
|<PHONE_NUMBER>306 |   22:     0xaaaabca7c0bc - std::panicking::try::hcc55e9ed15610d77                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19                                                                                |
|<PHONE_NUMBER>306 |   23:     0xaaaabca7c0bc - std::panic::catch_unwind::hcf59f097cd8ee652                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14                                                                                |
|<PHONE_NUMBER>306 |   24:     0xaaaabca7c0bc - std::rt::lang_start_internal::{{closure}}::h8fbfb8ff9e6d08fc                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:48                                                                                |
|<PHONE_NUMBER>306 |   25:     0xaaaabca7c0bc - std::panicking::try::do_call::hb9473916547b0c2e                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:492:40                                                                                |
|<PHONE_NUMBER>306 |   26:     0xaaaabca7c0bc - std::panicking::try::hfd0be8714fe2c175                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:456:19                                                                                |
|<PHONE_NUMBER>306 |   27:     0xaaaabca7c0bc - std::panic::catch_unwind::hd13ef362c9d4275f                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panic.rs:137:14                                                                                |
|<PHONE_NUMBER>306 |   28:     0xaaaabca7c0bc - std::rt::lang_start_internal::hb2f3ce624f838b60                                                                                |
|<PHONE_NUMBER>306 |                                at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/rt.rs:128:20                                                                                |
|<PHONE_NUMBER>306 |   29:     0xaaaabc7badf0 - main                                                                                |
|<PHONE_NUMBER>306 |   30:     0xffffaa2e7218 - __libc_start_main                                                                                |
|<PHONE_NUMBER>306 |   31:     0xaaaabc7bacb4 - <unknown>                                                                                |
|<PHONE_NUMBER>316 | [cargo-make] ERROR - Error while executing command, exit code: 101                                                                                |
|<PHONE_NUMBER>316 | [cargo-make] WARN - Build Failed.                                                                                |
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

@John0x Ah, I can see what's going on there. Try rev = "8429dc60ad6854a60397a43374917dcb4f59e455". It works on your mac since prisma-cli-3.13.0-darwin can run on M1 through Rosetta, but prisma-cli-3.13.0-linux is x64 only. I've made the architecture be specified so that prisma-cli-3.13.0-linux-arm64 should be downloaded on the AWS machine now.

@John0x Ah, I can see what's going on there. Try rev = "8429dc60ad6854a60397a43374917dcb4f59e455". It works on your mac since prisma-cli-3.13.0-darwin can run on M1 through Rosetta, but prisma-cli-3.13.0-linux is x64 only. I've made the architecture be specified so that prisma-cli-3.13.0-linux-arm64 should be downloaded on the AWS machine now.

That worked. Thank you very much :)

Ah, sorry, that might have been too soon 😃
Looks like it did download correctly but didn't execute the migrate command (specified by the make task). The "&operation = Read(" out comes from the seed command, which should be executed after the migrations have been applied.
Btw. the connection string is currently being logged in cleartext, which probably should be changed :)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|                                                                                message                                                                                |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [cargo-make] INFO - cargo make 0.35.11                                                                                |
| [cargo-make] INFO - Build File: Makefile.toml                                                                                |
| [cargo-make] INFO - Task: migrate-run-prod                                                                                |
| [cargo-make] INFO - Profile: development                                                                                |
| [cargo-make] INFO - Running Task: legacy-migration                                                                                |
| [cargo-make] INFO - Running Task: migrate-run-prod                                                                                |
| Downloading https://prisma-photongo.s3-eu-west-1.amazonaws.com/prisma-cli-3.13.0-linux-arm64.gz to /root/.cache/prisma/binaries/cli/3.13.0/prisma-cli-linux-arm64                                                                                |
| Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/query-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-query-engine-linux-arm64-openssl-1.1.x                               |
| Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/migration-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-migration-engine-linux-arm64-openssl-1.1.x                       |
| Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/introspection-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-introspection-engine-linux-arm64-openssl-1.1.x               |
| Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/prisma-fmt.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-prisma-fmt-linux-arm64-openssl-1.1.x                                   |
|   2022-05-04T23:30:15.232055Z  INFO quaint::pooled: Starting a postgresql pool with 3 connections.                                                                                |
|     at /usr/local/cargo/git/checkouts/quaint-9f01e008b9a89c14/a0722f2/src/pooled.rs:322                                                                                |
|     in query_core::executor::loader::exec_loader with features: [], url: "redacted connection string"                                                            |
| [/usr/local/cargo/git/checkouts/prisma-client-rust-fa967aa5ad0ec391/8429dc6/src/query.rs:27] &operation = Read(                                                                                |
|     Selection {                                                                                |
|         name: "redacted",                                                                                |
|         alias: Some(                                                                                |
|             "result",                                                                                |
|         ),                                                                                |
|         arguments: [                                                                                |
|             (                                                                                |
|                 "where",                                                                                |
|                 Object(                                                                                |
|                     {                                                                                |
|                         "name": String(                                                                                |
|                             "redacted",                                                                                |
|                         ),                                                                                |
|                     },                                                                                |
|                 ),                                                                                |
|             ),                                                                                |
|         ],                                                                                |
|         nested_selections: [                                                                                |
|             Selection {                                                                                |
|                 name: "name",                                                                                |
|                 alias: None,                                                                                |
|                 arguments: [],                                                                                |
|                 nested_selections: [],                                                                                |
|             },                                                                                |
|         ],                                                                                |
|     },                                                                                |
| )                                                                                |
| Error: Error executing query: Error occurred during query execution:                                                                                |
| ConnectorError(ConnectorError { user_facing_error: Some(KnownError { message: "The table `public.redacted` does not exist in the current database.", meta: Object({"table": String("public.redacted")}), error_code: "P2021" }), kind: TableDoesNotExist { table: "public.redacted" } })     |
| Caused by:                                                                                |
|     Error occurred during query execution:                                                                                |
|     ConnectorError(ConnectorError { user_facing_error: Some(KnownError { message: "The table `public.redacted` does not exist in the current database.", meta: Object({"table": String("public.redacted")}), error_code: "P2021" }), kind: TableDoesNotExist { table: "public.redacted" } }) |
| [cargo-make] ERROR - Error while executing command, exit code: 1                                                                                |
| [cargo-make] WARN - Build Failed.                                                                                |
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

If migrate deploy isn't applying the migrations, are you sure that your migrations are up to date by running migrate dev? Seems strange that it would download the CLI, and then end. The CLI shouldn't just fail silently like that. If that is the case though, then I've got some investigation to do 😅

If migrate deploy isn't applying the migrations, are you sure that your migrations are up to date by running migrate dev? Seems strange that it would download the CLI, and then end. The CLI shouldn't just fail silently like that. If that is the case though, then I've got some investigation to do 😅

Yep, pretty sure they are up-to-date. Works fine on my machine 😃 (using the same Dockerfile). The prisma schema points to the same env var for the connection string as the seeding package, therefore it should be able to connect to the db, since the seeding package is able to do it.
I ran the aws instance again and got an additional error message this time "Pkg: Error reading from file.".
Which, as far as I know, sometimes happens on corrupt executables. I removed the rest of the logs, since it's exactly the same as the previous run.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|   timestamp   |                                                                                message                                                                                |
|---------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|<PHONE_NUMBER>753 | [cargo-make] INFO - cargo make 0.35.11                                                                                |
|<PHONE_NUMBER>180 | [cargo-make] INFO - Build File: Makefile.toml                                                                                |
|<PHONE_NUMBER>180 | [cargo-make] INFO - Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>180 | [cargo-make] INFO - Profile: development                                                                                |
|<PHONE_NUMBER>181 | [cargo-make] INFO - Running Task: legacy-migration                                                                                |
|<PHONE_NUMBER>191 | [cargo-make] INFO - Running Task: migrate-run-prod                                                                                |
|<PHONE_NUMBER>213 | Downloading https://prisma-photongo.s3-eu-west-1.amazonaws.com/prisma-cli-3.13.0-linux-arm64.gz to /root/.cache/prisma/binaries/cli/3.13.0/prisma-cli-linux-arm64                                                                                |
|<PHONE_NUMBER>487 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/query-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-query-engine-linux-arm64-openssl-1.1.x                               |
|<PHONE_NUMBER>826 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/migration-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-migration-engine-linux-arm64-openssl-1.1.x                       |
|<PHONE_NUMBER>072 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/introspection-engine.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-introspection-engine-linux-arm64-openssl-1.1.x               |
|<PHONE_NUMBER>291 | Downloading https://binaries.prisma.sh/all_commits/efdf9b1183dddfd4258cd181a72125755215ab7b/linux-arm64-openssl-1.1.x/prisma-fmt.gz to /root/.cache/prisma/binaries/cli/3.13.0/efdf9b1183dddfd4258cd181a72125755215ab7b/prisma-prisma-fmt-linux-arm64-openssl-1.1.x                                   |
|<PHONE_NUMBER>531 | Pkg: Error reading from file.                                                                                |
|<PHONE_NUMBER>545 |   2022-05-05T11:24:08.545091Z  INFO quaint::pooled: Starting a postgresql pool with 3 connections.                                                                                |
|<PHONE_NUMBER>545 |     at /usr/local/cargo/git/checkouts/quaint-9f01e008b9a89c14/a0722f2/src/pooled.rs:322                                                                                |
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I fired up an arm64 EC2 instance with Amazon Linux and managed to run cargo prisma generate, cargo prisma migrate dev and cargo prisma migrate deploy with no troubles. Honestly not sure why it's not working in your docker image. Don't really have any other advice than using rev = "8429dc60ad6854a60397a43374917dcb4f59e455" and making sure that all the migration SQL is being generated, included in your docker image and detected by cargo prisma migrate push.

I fired up an arm64 EC2 instance with Amazon Linux and managed to run cargo prisma generate, cargo prisma migrate dev and cargo prisma migrate deploy with no troubles. Honestly not sure why it's not working in your docker image. Don't really have any other advice than using rev = "8429dc60ad6854a60397a43374917dcb4f59e455" and making sure that all the migration SQL is being generated, included in your docker image and detected by cargo prisma migrate push.

Thanks for trying :)
I'll look into it more tomorrow

Well...
Weirdly enough it seems to work now, on an automated run. Same docker image, same environment... I had it scheduled in the night and was surprised to find it working in the morning.
I will close this for now. Thank you for support :)


fastlane taking too much time to create or regenerate profiles

Hi,
From past few days I have observed that fastlane is taking too much time to create or regenerate profiles.
Most of the time its stuck on the line:
Verifying that the certificate and profile are still valid on the Dev Portal...
To generate some 10 profiles it took more than 20 hours.
Seems something has changed on Apple end.
I am using match with array of App Ids.
Everything worked well two weeks back.

Could you share the complete output too, so we can see the time stamps next to the output?

sure @KrauseFx Is there a way I can send the output privately. It contains my app ids which I would prefer to keep it private.

I am using cert & sigh, rather than match, but I have observed the same behaviour for the past ~2 weeks.
I am currently working on removing cert & sigh from my standard adhoc build and placing them in an optional lane (and caching their results) because they take approx 2 hours to run now.
Here is a sample output from an adhoc build with timestamps:
[11:02:02]: ------------------
[11:02:02]: --- Step: cert ---
[11:02:02]: ------------------

+---------------+--------------------------------------------------+
|                     Summary for cert 2.28.4                      |
+---------------+--------------------------------------------------+
| development   | false                                            |
| force         | false                                            |
| username      |<EMAIL_ADDRESS>                         |
| team_id       | XXXXXXXXXX                                       |
| team_name     | XXXXXXXXXX                                    |
| keychain_path | /Users/xxxxx/Library/Keychains/login.keychain-db |
| platform      | ios                                              |
+---------------+--------------------------------------------------+

[11:02:02]: Starting login with user<EMAIL_ADDRESS>[11:08:16]: Successfully logged in
[11:57:52]: Found the certificate XXXXXXXX (iOS Distribution) which is installed on the local machine. Using this one.
[11:57:52]: Verifying the certificate is properly installed locally...
[11:57:52]: Successfully installed certificate XXXXXXXXXX
[11:57:52]: Use signing certificate 'XXXXXXXXX' from now on!
[11:57:52]: ------------------
[11:57:52]: --- Step: sigh ---
[11:57:52]: ------------------

+-------------------------------------+--------------------------+
|                    Summary for sigh 2.28.4                     |
+-------------------------------------+--------------------------+
| adhoc                               | true                     |
| force                               | true                     |
| development                         | false                    |
| skip_install                        | false                    |
| app_identifier                      | xxxxxxxxx |
| username                            |<EMAIL_ADDRESS> |
| team_id                             | XXXXXXXX               |
| team_name                           | XXXXXXXX            |
| ignore_profiles_with_different_name | false                    |
| cert_id                             | XXXXXXX               |
| skip_fetch_profiles                 | false                    |
| skip_certificate_verification       | false                    |
| platform                            | ios                      |
+-------------------------------------+--------------------------+

[11:57:52]: Starting login with user<EMAIL_ADDRESS>[12:04:07]: Successfully logged in
[12:04:07]: Fetching profiles...
[12:04:10]: Verifying certificates...
[12:10:23]: Found 1 matching profile(s)
[12:10:23]: Recreating the profile
[12:35:07]: Creating new provisioning profile for 'xxxxxxxxxx' with name 'xxxxxxxxxx AdHoc' for 'ios' platform
[12:47:31]: Downloading provisioning profile...
[13:00:01]: Successfully downloaded provisioning profile...
[13:00:01]: Installing provisioning profile...
/Users/xxxxx/.jenkins/jobs/xxxxxxx/workspace/xxxxxxxxx.mobileprovision
[13:00:01]: Setting Provisioning Profile type to 'ad-hoc'
[13:00:01]: -----------------
[13:00:01]: --- Step: gym ---
[13:00:01]: -----------------

Note, the slow calls are not always the same, it will stall at different points each time. Occasionally it stalls long enough for ruby to simply log 'execution expired' and the build fails.
I also logged in via the interactive mode of Spaceship, and occasionally calls simply do not respond. Often in testing, if I run the same call twice it will respond immediately once, and not at all the second time.

Okay, we've done some more investigating.
It seems it is an Apple server problem, but not with all their servers.
I am in France, and by default, my developer.apple.com is resolving to a block of servers in Amsterdam eg
nlams2-vip-bx-001.aaplimg.com, nlams2-vip-bx-002.aaplimg.com etc
I forced my server to resolve it to a US West coast block of servers eg
ussjc2-vip-bx-001.aaplimg.com etc
and the problem disappears.
I think apple need to reboot their servers in NL :)

Hi @stevewallis Is there a way in fastlane I can point to the US West coast block servers?

Thanks @stevewallis ! I had the same problem.
adding folowing line to /etc/hosts temporary solves my issue
<IP_ADDRESS>    developer.apple.com

Yeah, I also had to hack it with /etc/hosts for now, which is not a good solution, but at least my builds are working again. Hopefully apple resolves the issue with the NL servers.

Thanks for sharing the details, this is super interesting. Do you think that will be resolved soon? Should we build some kind of check for this into fastlane?

worked for me too after adding <IP_ADDRESS> developer.apple.com in  /etc/hosts

Thanks everyone, that's very interesting.
To sum up, the Developer Portal servers in Europe are slower than the ones in the U.S. by a factor of about 100. To directly access the U.S. based Developer Portal servers, you have to edit your /etc/hosts files using sudo nano /etc/hosts (or any other text editor) and append
<IP_ADDRESS> developer.apple.com

Please make sure to remove that entry again in a few days/weeks, depending on when the issue is resolved.

@KrauseFx no idea for a fix time, got an apple contact? Hopefully it's just a one off issue and it will be resolved.
re: a fastlane fix -
Currently, it tries to make the SSL connection but gets stuck in SYN_SENT, with no ack coming back, so i guess that means their server is ignoring the packets for some reason.
I suppose you could check after x amount of time if the connection has received 0 bytes, and if so then force your requests to switch to a different server region?

Update - we notified Apple, and they sent us back a message to retry the Amsterdam servers and they seem to be working again, so you can all probably remove that hack from /etc/hosts.

Awesome, thanks for confirming @stevewallis

I'll close this issue for now


SysCallError: (-1, 'Unexpected EOF')

A blip in the normally flawless django-ios-notifications:
If it makes any difference I am running this within a function called with an @async decorator from here.
Exception in thread Thread-92:
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
    self.run()
  File "/home/ubuntu/Live/snaplist-website/main/apn.py", line 54, in run
    sendAPNMessage(self.device_id, self.message, self.data, self.badge)
  File "/home/ubuntu/Live/snaplist-website/main/apn.py", line 42, in sendAPNMessage
    apns.push_notification_to_devices(notification, devices)
  File "/usr/local/lib/python2.7/dist-packages/ios_notifications/models.py", line 99, in push_notification_to_devices
    self._write_message(notification, devices, chunk_size)
  File "/usr/local/lib/python2.7/dist-packages/ios_notifications/models.py", line 121, in _write_message
    self._connect()
  File "/usr/local/lib/python2.7/dist-packages/ios_notifications/models.py", line 89, in _connect
    return super(APNService, self)._connect(self.certificate, self.private_key, self.passphrase)
  File "/usr/local/lib/python2.7/dist-packages/ios_notifications/models.py", line 55, in _connect
    self.connection.do_handshake()
SysCallError: (-1, 'Unexpected EOF')

I'm getting this, anyone figure out what was going on?


Reinstate Slido

Fixes #380
Adds the following events or companies:

Slido

Checklist

[x] I have put the most recent relevant date in the "Last Update" column
[N/A] I have linked to the article about the change, not the company's website

@wptb-limenet, would you mind taking a look to make sure I didn't get any data wrong?

@drewbrew looks great, thank you!


Move instance initialization out of before_first_request (PP-92)

Description
This PR adds back in the code reverted in https://github.com/ThePalaceProject/circulation/pull/1143.
It makes some changes to our instance initialization to try to reduce issues we've had with locking:

The application does not initialize the DB on its own, this is done via a script run at startup of the docker container
The instance initialization and migration scripts were merged together
Instance initialization is done while holding a PG advisory lock, so only a single instance does the initialization / migration at a time.

Motivation and Context
JIRA: PP-92
This should allow us to:

Upgrade flask
Make sure the webserver is initialized before responding to requests. This will help our load balancer configuration for fargate.

How Has This Been Tested?
Tried testing the following locally:

Running development server

Fresh DB
Existing DB

Docker containers

Fresh DB
Existing DB

There are a lot of different cases here though, so its possible I've missed some cases that should be tested.
Checklist

[X] I have updated the documentation accordingly.
[X] All new and existing tests passed.

@jonathangreen what had failed previously with this change, before the revert?

@RishiDiwanTT Advisory locks were in use at that time, but I think it was the exclusive lock on the configurationsettings table that was causing the database deadlocks, according the logs we saw. So I'm trying to avoid that lock this time around, and just use an advisory lock.
In the end until we get rid of all the configuration settings, I think we need two advisory locks. One for setting up the DB, and one for initializing the application. I put a TODO in the code, because the one for initializing the application can go away once we move all the configuration settings over.


Get tracking angles

@shirubana : I've greatly streamlined the code, so the solarposition calculation and time adjustment is done once in the very beginning when the MetObj is created.  This cleans up a lot of the calculations in getTrackerAngles and gendaylit.

My only concern here is that it definitely changed some of the tracker angles used with gencumsky 1-axis tracking.  I could use some help validating that tracker angles and sun angles are correct.

Can I close this?


Send message without event

I can send messages just fine as a response to the 'message' event, but cannot seem to send a message outside of that.
I have tried two different things.
The first is this:
$discord = new Discord\Discord([
  'token' => env('BOT_TOKEN')
]);

$discord->factory(Discord\Parts\Channel\Channel::class, [
  'id' => 'CHANNEL_ID'
])->sendMessage('test'))

If I dump the return value of the ->sendMessage function it returns a promise object that looks like this:
React\Promise\Promise {#872
  -canceller: null
  -result: null
  -handlers: []
  -progressHandlers: []
  -requiredCancelRequests: 0
  -cancelRequests: 0
}

This wouldn't be a problem, if the other method mentioned in issue #132 didnt also seem broken.
Here is the code I tried:
$discord = new Discord\Discord([
  'token' => env('BOT_TOKEN')
]);

$guild = $discord->guilds->get('id', 'GUILD_ID'); // <-- breaks here
$channel = $guild->channels->get('id', 'CHANNEL_ID');

$channel->sendMessage('my message here');

When debugging it would appear that $discord->guilds returns null, so calling "->get()" on it results in a fatal error.
Im a bit confused because these operations seem to work a bit later down inside of the "->on('message')" event.
Any ideas? I can't seem to find anything in the docs to say i'm doing it wrong.

It has to be inside of an event, but it doesn't have to be inside of the message event. Add that code inside of $discord->on('ready', ...) and it should work. Everything has to run from a discord event in order for it to function correctly as far as I am able to discern.

@Tekner thanks for the input!
Here is what I have right now:
$discord = new Discord([
    'token' => env('BOT_TOKEN'),
]);

$discord->on('ready', function ($discord) {
    // Break from loop and send messages if needed
    $discord->on('heartbeat', function () use ($discord) {

        $guild = $discord->guilds->get('id', 'GUILD_ID');
        $DiscordChannel = $guild->channels->get('id', 'CHANNEL_ID');
        $DiscordChannel->sendMessage('message');

        echo "heartbeat called at: " . time() . PHP_EOL;
    });

    // Listen for messages.
    $discord->on('message', function ($message, $discord) {
        $Message = BotController::logMessage($User, $message);
        BotController::reply($message);
    });
});

$discord->run();

This is the result I get:
  [InvalidArgumentException]
  Illegal operator and value combination.

I have some scripts that run in the background that provide input for the bot, but i dont like the idea of needing to wait for a message to be received to be able to send messages out. The heartbeat function looks like it will do just what I need, but i cant seem to send messages from within it.
Does anything here stand out as incorrect?

I'm not familiar with the heartbeat event, but there's a much better and flexible way to execute periodic code in the context of discordphp. Simply utilize the ReactPHP loop that's included in the API like so: $discord->loop->addPeriodicTimer($tick, $func);
$tick is the period in seconds and $func can be a closure, variable reference, or string function name that accepts no arguments. You can use global within the function if you want to access $discord.
Compressed code example:
$PERIOD = 10; //seconds

//I made a wrapper function so I don't need to reference $discord->loop everywhere,
//but it's obviously not necessary.
function AddLoop($tick, $func) { global $discord; $discord->loop->addPeriodicTimer($tick, $func); }
function DoStuff() {
    global $discord;
    $guild = $discord->guilds->get('id', 'GUILD_ID');
    $channel = $guild->channels->get('id', 'CHANNEL_ID');
    $channel->sendMessage("$PERIOD seconds have passed!");
}

//You could also define DoStuff() as a closure instead of defining it beforehand and referencing it
//as a string. Alternatively, you could set a variable equal to a predefined closure and use that
//variable instead of a string here. The choice is yours in how you reference the function.
AddLoop($PERIOD, 'DoStuff');

That set me on the right track. Here is my finished code:
$discord->loop->addPeriodicTimer(10,function () use ($discord) {
  // handle asynchronous feedback outside of event
});

$discord->on('ready', function ($discord) {
  // the rest of the application
});

Many thanks!

New Information? all this not Work


Module federation and MUI doesn't work with 2 different react version

When using module federation webpack 5  plugin and using 2 projects using 2 different versions of React it's cause an error

[V] The issue is present in the latest release.
[V] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
error throw and application not loaded :

Expected Behavior 🤔
should work as expected.
Steps to Reproduce 🕹

Create APP1 with version 17.0.2  and use module federation plugin.
Create APP2  with version 17.0.0 and use module federation plugin.
install MUI in App2: npm install @mui/material @emotion/react @emotion/styled and expose some component that uses the MUI components.
In App1 you consume the exposed component that you expose from App2.
Run both apps
Get the error in the console

I solve the problem when I set both apps to use the same react version .. the q is why it's happening actually only in MUI.
sandbox:
https://codesandbox.io/s/webpack-module-f-forked-8vto1?
it's the very basic and regular implementation of the module federation that includes 2 apps.
one app is with react&react dom in 17.0.0 and the second with 17.0.2 and it didn't work.
if you change both to use 17.0.2/17.0.0 it's will work as expected!
NOTE:
The scenario of 2 diffs React versions that works can work by this configuration of the moduleFedration plugin.
App1 - with 17.0.0 version:
  shared: {
    ...deps,
    react: {
      import: "react", // the "react" package will be used a provided and fallback module
      shareKey: "oldReact", // under this name the shared module will be placed in the share scope
      shareScope: "legacy", // share scope with this name will be used
      singleton: true, // only a single version of the shared module is allowed
      requiredVersion: deps["react"],
    },
    "react-dom": {
      import: "react-dom", // the "react" package will be used a provided and fallback module
      shareKey: "old-react-dom", // under this name the shared module will be placed in the share scope
      shareScope: "legacy", // share scope with this name will be used
      singleton: true, // only a single version of the shared module is allowed
      requiredVersion: deps["react-dom"],
    },
}

App2 - with 17.0.2 version:
 shared: {
    ...deps,
    react: {
      import: "react", // the "react" package will be used a provided and fallback module
      shareKey: "newReact", // under this name the shared module will be placed in the share scope
      shareScope: "default", // share scope with this name will be used
      singleton: true, // only a single version of the shared module is allowed
      requiredVersion: deps["react"],
    },
    "react-dom": {
      import: "react-dom", // the "react" package will be used a provided and fallback module
      shareKey: "newReactDom", // under this name the shared module will be placed in the share scope
      shareScope: "default", // share scope with this name will be used
      singleton: true, // only a single version of the shared module is allowed
      requiredVersion: deps["react-dom"],
    },
  },

I try to insert MUI dependencies in the same way but it's didn't help.

hi @eps1lon thanks for the answer.
you could see that here: https://codesandbox.io/s/webpack-module-f-forked-8vto1?
it's the very basic and regular implementation of module fedration includes 2 apps .
one app is with react&react dom in 17.0.0 and the second with 17.0.2 and its didn't work
if you change both to use 17.0.2/17.0.0 it's will work as expected!
thanks again

Hey @OriAmir were you ever able to get this working?
I have the same issue, also not sure whether it's in the scope of Module Federation or MUI.
I got the container to pull in the remote successfully, with the container running react 17.0.2 and the remote running 18.2.0, but as soon as I use an MUI component in my remote application, I get the invalid hooks error.

Hey @eps1lon - hope you are well! I'm running into the same issue that @OriAmir opened here, and would like to provide an example. I know this may be a bit outside MUI support scope as it leverages Module Federation, but I think it's worth a try!
I am able to successfully run a single page application using a host service (react 17) and a remote application (react 18), but as soon as I use an MUI component in the remote application, I get the "invalid hooks" error like Ori had above.
I started with Module Federation's example of two different react versions, here: https://github.com/module-federation/module-federation-examples/tree/master/different-react-versions-16-18-typescript. I have the same exact webpack configuration as Ori does above, and I am going between React 17 and 18, which does not require the hooks adaptation the example uses.
Host MFE config in webpack.config.js:
new ModuleFederationPlugin({
      name: 'app1',
      library: { type: 'var', name: 'app1' },
      remotes: {
        app2: 'app2',
      },
      shared: {
        'react-dom': {
          import: 'react-dom', // the "react" package will be used a provided and fallback module
          shareKey: 'react-dom', // under this name the shared module will be placed in the share scope
          shareScope: 'legacy', // share scope with this name will be used
          singleton: true, // only a single version of the shared module is allowed
          requiredVersion: deps['react-dom']
        },
        react: {
          import: 'react', // the "react" package will be used a provided and fallback module
          shareKey: 'react', // under this name the shared module will be placed in the share scope
          shareScope: 'legacy', // share scope with this name will be used
          singleton: true, // only a single version of the shared module is allowed
          requiredVersion: deps['react']
        },
      },
    }),

Remote MFE config in webpack.config.js:
new ModuleFederationPlugin({
      name: 'app2',
      library: { type: 'var', name: 'app2' },
      filename: 'remoteEntry.js',
      exposes: {
        './App': './src/components/App',
        './newReact': require.resolve('react'),
        './newReactDOM': require.resolve('react-dom'),
      },
      shared: {
        ...deps,
        react: {
          import: "react", // the "react" package will be used a provided and fallback module
          shareKey: "newReact", // under this name the shared module will be placed in the share scope
          shareScope: "default", // share scope with this name will be used
          singleton: true, // only a single version of the shared module is allowed
          requiredVersion: deps["react"],
        },
        "react-dom": {
          import: "react-dom", // the "react" package will be used a provided and fallback module
          shareKey: "newReactDom", // under this name the shared module will be placed in the share scope
          shareScope: "default", // share scope with this name will be used
          singleton: true, // only a single version of the shared module is allowed
          requiredVersion: deps["react-dom"],
        },
      }
    }),

On the remote side (React 18.2.0), I am displaying a small presentational component which uses <Button> from MUI:
import { Button } from '@mui/material';
import React from 'react';

const App = () => {
  return (

App 2, running React 18.2.0

      <Button>MUI Button</Button>

  );
};

export default App;

On the host side, all I am doing is embedding that one presentational component in the UI:
import React, { lazy, Suspense } from 'react';
const App2 = lazy(() => import('app2/App'));

const App = () => {
  return (

Basic Host-Remote

App 1, Uses react version 17.0.2

        <Suspense fallback="loading...">
          <App2 />
        </Suspense>

  );
}

export default App;

Here is the package.json file for the host application:
{
  "name": "@different-react-versions-16-18-typescript/app1",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "webpack-cli serve",
    "build": "webpack --mode production",
    "serve": "serve dist -p 3001",
    "clean": "rm -rf dist"
  },
  "dependencies": {
    "@emotion/react": "11.7.1",
    "@emotion/styled": "11.6.0",
    "@mui/icons-material": "5.8.4",
    "@mui/material": "5.2.5",
    "@mui/styles": "5.12.3",
    "react": "17.0.2",
    "react-dom": "17.0.2"
  },
  "devDependencies": {
    "@babel/core": "7.21.4",
    "@babel/plugin-proposal-class-properties": "7.18.6",
    "@babel/preset-react": "7.18.6",
    "@babel/preset-typescript": "7.21.4",
    "@types/react": "16.14.40",
    "@types/react-dom": "16.9.18",
    "babel-loader": "8.2.5",
    "html-webpack-plugin": "5.5.1",
    "serve": "13.0.4",
    "typescript": "4.8.4",
    "webpack": "5.80.0",
    "webpack-cli": "5.0.2",
    "webpack-dev-server": "4.13.3"
  }
}

And here is the package.json file for the remote application:
{
  "name": "@different-react-versions-16-18-typescript/app2",
  "version": "0.0.0",
  "private": true,
  "scripts": {
    "start": "webpack-cli serve",
    "build": "webpack --mode production",
    "serve": "serve dist -p 3002",
    "clean": "rm -rf dist"
  },
  "dependencies": {
    "@emotion/react": "11.7.1",
    "@emotion/styled": "11.6.0",
    "@mui/icons-material": "5.8.4",
    "@mui/material": "5.2.5",
    "@mui/styles": "5.12.3",
    "react": "18.2.0",
    "react-dom": "18.2.0"
  },
  "devDependencies": {
    "@babel/core": "7.21.4",
    "@babel/plugin-proposal-class-properties": "7.18.6",
    "@babel/preset-react": "7.18.6",
    "@babel/preset-typescript": "7.21.4",
    "@types/react": "18.0.38",
    "@types/react-dom": "18.0.11",
    "babel-loader": "8.2.5",
    "html-webpack-plugin": "5.5.1",
    "serve": "13.0.4",
    "typescript": "4.8.4",
    "webpack": "5.80.0",
    "webpack-cli": "^5.0.2",
    "webpack-dev-server": "4.13.3"
  }
}

This should be all the primary differences between my scenario and the example from Module Federation. Alternatively, you could just use the example from the link above and use an MUI component in the remote application.
Thanks in advance for your time and support - apologies if this implementation detail is out of scope! Even knowing whether this is possible or not would be a good step forward at this point :)

Is this issue resolved? If resolved, how it is resolved? I am still facing the same use.

Maybe this reply will help.
Looks like you have to add MUI to the shared plugins.
I was having the same issues with react-query (before adding it to shared, I was getting lots of React hooks errors, after adding it, the errors went away).


Default value for Id of type GUID now no longer set in EF Core 3.0?

I Just updated to EF Core 3.0 and am getting a heap of errors.
I have an entity with an Id of type Guid. When I called the DBSet AddAsync with my new entity the Guid would be automatically populated. This meant I knew what the Guid would be prior to saving. However, since upgrading to 3.0 Id is still the default value for Guid.
Is this a deliberate change or a bug? If it's a deliberate change it's going to make upgrading very painful for people :(
In migration void BuildTargetModel(ModelBuilder modelBuilder)
b.Property<Guid>("Id")
.ValueGeneratedOnAdd()
.HasDefaultValueSql("(newid())");

In OnModelCreating(ModelBuilder modelBuilder)
entity.Property(e => e.Id).HasDefaultValueSql("(newid())");

@patricknolan Are you sure that, in your 2.2 code, the GUID set before calling SaveChanges is the same as the GUID set after calling SaveChanges? The configuration posted above should generate a temporary GUID, which is then replaced by the database-generated GUID after the row has been inserted. Using my test code below on 2.2 I see the output:
cb17f33d-83f9-4dd3-910d-fd16f50a0d52
39f3552a-ba91-4b09-9c2c-c09cd210425b

which seems to confirm this.
For 3.0, we made a change to the way temporary values are handled such that they are not stored on the entity instance but instead kept track of in the context. These means that when I run the same code on 3.0 I get:
00000000-0000-0000-0000-000000000000
678412e6-a1d5-44f0-b0c4-363313370a92

In both 2.2 and 3.0, if HasDefaultValueSql("(newid())") is not called, then the GUID will be generated on the client side when Add is called. Making this change and running the code results in:
ba355592-0199-45dd-4b05-08d7712ba2bb
ba355592-0199-45dd-4b05-08d7712ba2bb

If you are seeing something different, then please post a small, runnable project/solution or complete code listing that demonstrates what you are seeing.
public class User
{
    public Guid Id { get; set; }
}

public class BloggingContext : DbContext
{
    protected override void OnModelCreating(ModelBuilder modelBuilder)
    {
        modelBuilder.Entity<User>().Property(e => e.Id).HasDefaultValueSql("(newid())");
    }

    protected override void OnConfiguring(DbContextOptionsBuilder optionsBuilder)
        => optionsBuilder
            .UseSqlServer(@"Server=(localdb)\mssqllocaldb;Database=Test;ConnectRetryCount=0");
}

public class Program
{
    public static void Main()
    {
        using (var context = new BloggingContext())
        {
            context.Database.EnsureDeleted();
            context.Database.EnsureCreated();

            var user = context.Add(new User()).Entity;
            Console.WriteLine(user.Id);

            context.SaveChanges();
            Console.WriteLine(user.Id);
        }
    }
}

EF Team Triage: Closing this issue as the requested additional details have not been provided and we have been unable to reproduce it.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.


Tests aborted when .NET Framework version is <4.6

Runs of 'dotnet test' on AppVeyor crash with this error:
> dotnet test --configuration Debug --framework net451
Build started, please wait...
Build completed.
Test run for C:\projects\common\test\Microsoft.Extensions.CommandLineUtils.Tests\bin\Debug\net451\Microsoft.Extensions.CommandLineUtils.Tests.dll(.NETFramework,Version=v4.5.1)
Microsoft (R) Test Execution Command Line Tool Version <IP_ADDRESS>
Copyright (c) Microsoft Corporation.  All rights reserved.
Starting test execution, please wait...
Error: The active Test Run was aborted

See https://ci.appveyor.com/project/aspnetci/common/build/1.0.797#L618 for example.
This only happens on AppVeyor's machines, and appears to only occur when VSTest is running a .NET Framework test run. It doesn't repro our internal CI agents, dev machines, or Linux boxes. Any suggestions on getting more details about why this failed?
Details
Using dotnet-CLI 1.0.0-preview4-004233
Using Microsoft.NET.Test.Sdk 15.0.0-preview-20161123-03

Closing this since it has been solved.