Move proof generation from SendStateLogCommit into a new preceding send state

Currently, proofs are generated in send state SendStateLogCommit. The proof generation code should be moved into a new preceding send state.
The goal of this issue is to improve code clarity.

Fixed by https://github.com/lightninglabs/taproot-assets/pull/805.


Update configure-azure-virtual-desktop.md

The output.tf is wrong, the location must be sh not rg. There is an error with the output "AVD_user_groupname" my suggestion is to remove it or add a resource for AD group.

Learn Build status updates of commit b628312:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/terraform/configure-azure-virtual-desktop.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@TomArcherMsft
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Request to Add Issue Templates: Bug Report, Feature Request, and Styling

I suggest adding three essential templates to our project: Bug Report, Feature Request, and Styling.
These templates will improve project management and collaboration by offering standardized formats for reporting bugs, submitting feature requests, and addressing styling issues. They will streamline communication, enhance issue tracking, and ensure consistency in our development and design processes.
I would like to work on this issue under the GSSoC'23.  @Abhirup-02

@Abhirup-02 have a look

Thank you for the assignment! I'm excited to contribute and will start working on the issue templates one by one from tomorrow. Kindly add the GSSOC'23 label to this issue, please. @Abhirup-02

I've raised PRs for all three templates. Kindly review them. Your attention is greatly appreciated. Thank you! @Abhirup-02


Remove common crypto++

I have removed CommonCrypto from the project as its already present in swift 4.2.
At the same time I have also migrated the project to swift 4.2 using migration in xcode, and I have fixed some warnings.

Hi, I cannot seem to get the test to work, there is an issue when calling SecKeyGeneratePair() in Heimdall.swift line 659. Its returning -34018.
I tried this solution, but cannot get it to work:
https://stackoverflow.com/questions/41258171/generating-key-pair-in-ios-using-seckeygeneratepair-failed-with-errsecinteractio

Also need to update the podspec, there is some CommonCrypto related stuff in there (as well as the platform needs to be updated). Most likely this would be a major release (as it would in essence not be backwards compatible).


usb: Correct USB setup packet endianness in USB core.

USB is sending data from LSB to MSB. Same happens for each field
of the USB setup packet.
This patch convert USB setup packet to proper form when its read
out from the line.
Follow up of: #26205
Signed-off-by: Emil Obalski<EMAIL_ADDRESS>

I've removed explicit uint8_t casts as well as 0xff masks. For deleting __packed struct I do not agree (explanation from Carles provided) and i left it in source file as its internal thing not need to end up in header where API is.

I've removed explicit uint8_t casts as well as 0xff masks. For deleting __packed struct I do not agree (explanation from Carles provided) and i left it in source file as its internal thing not need to end up in header where API is.

I think we should bring back the (uint8_t) casts as @anangl mentioned.


ECS --version improvement

While reporting an error in a sniff or fixer it's important to know the version of CodeSniffer or CS-Fixer. However currently it's actually somewhat difficult to find out what this version is since neither package is installed with composer but instead packed in ECS.
So it would be nice for the ECS console command to print the versions of these packages as well when I use --version.

I think that would be rather complicated to add and make the --version confusing for most people. This metadata can be found in vendor/* directory of ECS package.


Crash when loading up web GUI

Upon launching invoke-train-ui, then opening the local URL, the GUI loads in browser, and immediately crashes.
Environment:
Arch Linux
Firefox 122
Python 3.10
Here is the output log when the crash occurs:
Resetting UI configs for SDXL LoRA and Textual Inversion to invokeai-training/venv/lib/python3.10/site-packages/invoke_training/sample_configs/sdxl_lora_and_ti_gnome_1x24gb.yaml.
Resetting UI configs for SDXL LoRA to invokeai-training/venv/lib/python3.10/site-packages/invoke_training/sample_configs/sdxl_lora_pokemon_1x24gb.yaml.
Resetting UI configs for SDXL Textual Inversion to invokeai-training/venv/lib/python3.10/site-packages/invoke_training/sample_configs/sdxl_textual_inversion_gnome_1x24gb.yaml.
Resetting UI configs for SD LoRA to invokeai-training/venv/lib/python3.10/site-packages/invoke_training/sample_configs/sd_lora_pokemon_1x8gb.yaml.
Resetting UI configs for SD Textual Inversion to invokeai-training/venv/lib/python3.10/site-packages/invoke_training/sample_configs/sd_textual_inversion_gnome_1x8gb.yaml.
ERROR:    Exception in ASGI application
Traceback (most recent call last):
  File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 264, in __call__
    await wrap(partial(self.listen_for_disconnect, receive))
  File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    await func()
  File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 237, in listen_for_disconnect
    message = await receive()
  File "invokeai-training/venv/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 534, in receive
    await self.message_event.wait()
  File "invokeai-training/venv/lib/python3.10/asyncio/locks.py", line 214, in wait
    await fut
asyncio.exceptions.CancelledError: Cancelled by cancel scope 7340b3176f50

During handling of the above exception, another exception occurred:

  + Exception Group Traceback (most recent call last):
  |   File "invokeai-training/venv/lib/python3.10/site-packages/uvicorn/protocols/http/h11_impl.py", line 404, in run_asgi
  |     result = await app(  # type: ignore[func-returns-value]
  |   File "invokeai-training/venv/lib/python3.10/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in __call__
  |     return await self.app(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/fastapi/applications.py", line 1054, in __call__
  |     await super().__call__(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/applications.py", line 123, in __call__
  |     await self.middleware_stack(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 186, in __call__
  |     raise exc
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/middleware/errors.py", line 164, in __call__
  |     await self.app(scope, receive, _send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/middleware/cors.py", line 83, in __call__
  |     await self.app(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/middleware/exceptions.py", line 62, in __call__
  |     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/routing.py", line 758, in __call__
  |     await self.middleware_stack(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/routing.py", line 778, in app
  |     await route.handle(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/routing.py", line 299, in handle
  |     await self.app(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/routing.py", line 79, in app
  |     await wrap_app_handling_exceptions(app, request)(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 64, in wrapped_app
  |     raise exc
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
  |     await app(scope, receive, sender)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/routing.py", line 77, in app
  |     await response(scope, receive, send)
  |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 257, in __call__
  |     async with anyio.create_task_group() as task_group:
  |   File "invokeai-training/venv/lib/python3.10/site-packages/anyio/_backends/_asyncio.py", line 678, in __aexit__
  |     raise BaseExceptionGroup(
  | exceptiongroup.ExceptionGroup: unhandled errors in a TaskGroup (1 sub-exception)
  +-+---------------- 1 ----------------
    | Traceback (most recent call last):
    |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 260, in wrap
    |     await func()
    |   File "invokeai-training/venv/lib/python3.10/site-packages/starlette/responses.py", line 249, in stream_response
    |     async for chunk in self.body_iterator:
    |   File "invokeai-training/venv/lib/python3.10/site-packages/gradio/routes.py", line 663, in sse_stream
    |     raise e
    |   File "invokeai-training/venv/lib/python3.10/site-packages/gradio/routes.py", line 604, in sse_stream
    |     raise HTTPException(
    | fastapi.exceptions.HTTPException: 404: Session not found.
    +------------------------------------

When the app initially loads in the browser, it makes a call back to the server to load the default configs. It seems like this request is what's failing.
Can you check what gradio version you're on? I may have underspecified the supported gradio versions.
Also, just to confirm, are you running the browser on the same machine that you launched invoke-train-ui from?

These are the versions listed for gradio:
gradio                     4.17.0
gradio_client              0.9.0
I am also indeed running everything on the same machine.

I tried testing with your gradio version and am not able to reproduce.
This appears to be the error of interest https://github.com/gradio-app/gradio/blob/2382f741ffac98c1d929e7b253abbc8f5508feaa/gradio/routes.py#L600-L607. It seems to happen while the gradio server is SSE-streaming the response, but I haven't dug further than that.
This active issue might be related: https://github.com/gradio-app/gradio/issues/6920

Also related: https://github.com/gradio-app/gradio/issues/7189
I have now hit this issue once myself, but I can't reproduce it consistently.


diff highlights invalid differences

🐛 Bug Report
When you're comparing two objects and you use expect.any(String) for some keys, and the test fails for some reason, diff highlights all those places where you used expect.any(String) which is very confusing.
To Reproduce
expect([
            {
                a: expect.any(String),
                b: '',
            },
            {
                c: expect.any(String),
            },
        ]).toEqual([
            {
                a: 'foo',
            },
            {
                c: 'bar',
            },
        ]);

Expected behavior
In case of a failure, diff should not highlight expect.any(String).
Link to repl or repo (highly encouraged)
Not available
Run npx envinfo --preset jest
System:
    OS: macOS 10.14.6
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 11.10.0 - ~/.nvm/versions/node/v11.10.0/bin/node
    Yarn: 1.15.2 - ~/src/accidentsint/node_modules/.bin/yarn
    npm: 6.7.0 - ~/.nvm/versions/node/v11.10.0/bin/npm

Duplicate of #6184. Unfortunately way harder to fix atm than it looks


Plans for implementing UART

Thanks for the great project!
Just wanted to know what the timeline is for implementing support for the UART interface?

It should be implemented until end of this year. At this moment I'm not able give you more precisely timeline. pyIMX and imxmi projects have higher priority yet

Also interested in this feature.
On ARM Linux, want to use serial output (actually PTY) to drive another local program to talk to NXP bootloader over I2C.
Saw you did some fixing up and cleaning up of the code recently.
Can you give any status update on this issue?

For anyone else stumbling upon this issue. I ended up writing my own tool: https://github.com/Lauszus/pyblhost. It also supports uploading via CAN.


interleaved parameter is missing from shepely.transform in the released versions but not in the main branch and documentation

Please note
If you are reporting an installation or module import issue, please note that
this project only accepts reports about problems with packages downloaded from
the Python Package Index. Conda users should take issues to one of the
following trackers:

https://github.com/ContinuumIO/anaconda-issues/issues
https://github.com/conda-forge/shapely-feedstock

Expected behavior and actual behavior.
Expected
I can use the interleaved parameter in the shapely.transform method from the coordinates.py  file that is described in the Documentation (https://shapely.readthedocs.io/en/latest/reference/shapely.transform.html) as well as the main branch (https://github.com/shapely/shapely/blob/main/shapely/coordinates.py#L8).
Actual
The interleaved parameter is missing in the shapely.transform method from the coordinates.py file in the maint-2.0 branch (https://github.com/shapely/shapely/blob/maint-2.0/shapely/coordinates.py#L8)
Steps to reproduce the problem.
Download the files from the last release (https://github.com/shapely/shapely/releases/tag/2.0.3) or look into the maint-2.0 branch (https://github.com/shapely/shapely/blob/maint-2.0/shapely/coordinates.py#L8)
Operating system
any
Shapely version and provenance
2.0.2 and 2.0.3

You are looking at the "latest" version of the docs, while you want the "stable" docs for the latest released version ("latest" is a bit a confusing name for the development version ..)
See https://shapely.readthedocs.io/en/stable/reference/shapely.transform.html
The interleaved keyword will be included in a future shapely 2.1.0 release

("latest" is a bit a confusing name for the development version ..)

Although I see that our latest docs say they are for "shapely 2.0.1". That makes it even more confusing, and something we should fix to make it clear this is for the dev version.

Ah ok, thanks. I guess i was confused by the website stating "shapely 2.0.1" in the top left.
Could you maybe also mark the parameter as a future one in the docs? This would clarify it even more.

The latest docs (https://shapely.readthedocs.io/en/latest/) now say "2.1.0.dev", so that should be clearer.

Could you maybe also mark the parameter as a future one in the docs? This would clarify it even more.

Yes, that's a good idea. We should more consistently add "versions added" markers for new functions or keywords.


Image issue

Added functionality that unsubscribes/subscribes an image or disparity topic when the respective plugin is hidden.

It looks like this is properly unsubscribing when an image topic is hidden, but if the image plugin is initialized hidden, it subscribes anyway.


Enable creation of release assets

We recently had a request from a community user to have Windows binaries of zync available so they could run it without having to install Go and compile the code on their workstation. To provide this, here I've enabled the same approach we use in the Zed repo for creating tagged release assets, which in this case would allow the user to download and unpack the ZIP on their Windows system and copy the zync.exe to a folder that's in their PATH.
I've tested out the approach in this branch in a personal fork https://github.com/philrz/zync and you can see the successfully-created artifacts in https://github.com/philrz/zync/releases. As a smoke test I did unzip the Windows bundle and was able to successfully invoke the zync.exe. I also went ahead and made a fork of our Homebrew repo at https://github.com/philrz/homebrew-tap and you can see the zync formula populated ok there as well.
One thing I'll point out is that my artifact from the personal fork does not return a proper version string.
C:\Users\Phil\Downloads\zync-v1.0.0.windows-amd64>.\zync.exe version
(devel)

I suspect this problem may not show up when we create artifacts in the true zync repo, since we have a very similar known problem with Zed in personal forks (https://github.com/brimdata/zed/issues/4921). However, this whole topic of how the version strings get assembled has always been a little mysterious to me so I figured I'd point it out in case it concerns anyone enough that they want to dig deeper before merging this.

@nwt: I accepted your suggested changes, mirrored them into my personal fork at https://github.com/philrz/zync , made a test release v0.10.0, and successfully installed it via brew. So, I think this PR is ready for another look and possible Approve.

As a final test after that last commit from @nwt, I repeated the creation of a tagged release on my fork repo. The version string now appears as expected:
C:\Users\Phil\Downloads\zync-v0.10.0.windows-amd64>.\zync.exe version
v0.10.0

The same was also true on Linux and macOS (both the unpacked artifact from the GitHub Releases and the brew-installed binary).


AICommander has unused method isNearPlayer()

And it does not use the List<> interface

That's because I used it in previous versions of the AICommander code and then decided to integrate it into another method. However, I left it there since it is a good method that could be used later and didn't want to scrap the code. Will in future be moved to some form of utility, repurposed, or removed.

I'm pretty sure having unused code lying around in production is bad practice. Found this StackOverflow article that explains it quite well https://stackoverflow.com/questions/15699995/could-someone-explain-the-pros-of-deleting-or-keeping-unused-code

I repurposed this method when completing #131 to detect when an enemy is in a certain radius to an entity.


Up package version

@melvinfolkers Is there a good way to test this before merging? After merging we can first use it with a release candidate.

I don't think we should pin versions anymore in packages. I think we should change everything to >= so we don't get conflicts anymore, it will be very rare that we run into braking changes, and at that point we can always set an upper limit.
So for this PR I would suggest to keep the original versions and just put >= in there.

@erfannariman I don't see your comment anymore, but you mean like this with the >=? I was not sure whether its also desired in the requirements.txt.

@erfannariman I don't see your comment anymore, but you mean like this with the >=? I was not sure whether its also desired in the requirements.txt.

Yes I removed the comment because it would actually introduce breaking changes already, so in this case it's not valid with the Azure packages.

@erfannariman I don't see your comment anymore, but you mean like this with the >=? I was not sure whether its also desired in the requirements.txt.

Yes I removed the comment because it would actually introduce breaking changes already, so in this case it's not valid with the Azure packages.

Ready for review, limited some packages from above, and replaced the deprecated parameter line_terminator with lineterminator. All tests succeeded.

@erfannariman or @melvinfolkers can one of you check again?

Approved from my side, but note that some code is written by me also. Maybe @erfannariman can take a look as well.
@TimvdHeijden did you run the tests from the test suite?

Yes see my comment from March 17, All tests succeeded.

@erfannariman or @melvinfolkers can one of you check again?

I think we need to set pandas>=1.5.0 because of the change in argument lineterminator.

@erfannariman or @melvinfolkers can one of you check again?

I think we need to set pandas>=1.5.0 because of the change in argument lineterminator.

Done. Tests work, but thats because I already had 1.5.3 locally. and they did not work with pandas 1.4.3. So valid point.


Add python-sympy-pip

apt provides an outdated version of sympy. pip has the most recent
Example where this is a problem: https://answers.ros.org/question/304466/rosdep-pip-instead-of-apt/

No response in over a month, and we don't want to be adding new pip keys to override system packages this way (from the discussion in https://github.com/ros/rosdistro/pull/18840).  I'm going to close this out for now, but if you'd like to discuss this more, feel free to keep commenting or re-open.


[v1.2.0] use local package ( yarn link || npm link), run docz:dev error

Bug Report

mzmu is i use yarn link add local development package;
and use install mzmu is work

Does your local package mzmu have a compile/build/transpile step? I guess you need to transpile your source code before importing it. A common pattern is having mzmu/src/utils.ts, and a build step that runs babel and typescript compilation so you end up with mzmu/lib/utils.js.
You could also try to configure the doczrc build setup to run your dependency through babel... and remember typescript: true in the config.

because mzmu is local dev version, so not compile; and have been set typescript: true in my doczrc, but then not work
@draperunner


Put ID like columns in dimensions, not metrics - even if they have numeric data types

Hi team.
Currently in the semantic model generator, it seems as if the data type is looked at to identify if a field should become a measure or dimension. if a table as IDs which can be join keys, even if they are numeric, they should be classified as dimensions so that they can be joined with other tables and no aggregations can be done on those IDs. just a nice to have to ensure that "ID" like columns should become dimensions, not measures; where the current behavior is that they do become measures.

Hi team, is there any update on this issue ? This is really hindering the join experience since joins are not supported on metrics in semantic model generator.


feat(v2): Allow swizzling prism-include-languages in theme-classic

Motivation
Right now it's hard to include custom languages syntax highlighting support. It's almost impossible to do it in a simple config due to context replacement issue. Right now there are two alternatives that both have some issues:

Swizzle CodeBlock component. Issue: A local CodeBlock might eventually diverge from the CodeBlock in theme-classic.
Write a plugin. This is the approach I am currently using. See (1) and (2). However, whether the Prism object used by theme-classic will be correctly patched is completely at the mercy of package manager's hoisting behavior:

Suppose you do this in your plugin
import Prism from 'prism-react-renderer/prism';

If you declare prism-react-renderer as a dependency of your plugin, then you might end up patching a prism-react-renderer that is not used by theme-classic, since you might get a node_modules layout like:
- your-plugin
  - node_modules
    - prism-react-renderer
- @docusaurus/theme-classic
  - node_modules
    - prism-react-renderer

If you declare prism-react-renderer as a peer dependency or doesn't declare as a dependency, then you are still relying on package manager's hoisting behavior that produces this node_modules layout:
- node_modules
  - your-plugin
  - prism-react-renderer
  - @docusaurus/theme-classic

However, it's completely legal for a package manager to produce this:
- node_modules
  - your-plugin
  - @docusaurus/theme-classic
    - node_modules
      - prism-react-renderer

Then your plugin cannot find prism-react-renderer any more.
The root of the issue is that we need a way that is guaranteed to use prism-react-renderer from @docusaurus/theme-classic, while still being able to be customized easily in userland. This leaves us with only one alternative that doesn't require significant refactoring: Swizzling.
This diff moves the main implementation of prism-include-languages into src/theme folder so that it can be swizzled. The API of @theme/prism-include-languages is likely to be very stable so swizzling it wouldn't produce a huge risk of divergence.
Questions for maintainers

I noticed in the discussion that docusaurus might try to move away from swizzling. So I wonder whether this diff is a good idea.
If this is approved, should we still keep the additionalLanguages config?

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan

Swizzle prism-include-languages by yarn workspace docusaurus-2-website swizzle @docusaurus/theme-classic prism-include-languages
Edit docusaurus.config.js to include swift as an additional language:

    prism: {
      theme: require('prism-react-renderer/themes/github'),
      darkTheme: require('prism-react-renderer/themes/dracula'),
+     additionalLanguages: ['swift']
    },

Add some random swift code to a docs page, like

protocol Foo {}

yarn start, and see the code is correctly syntax highlighted.

Edit the swizzled prism-include-languages to make it an empty function.

Restart, now it's no longer syntax highlighted, which shows that the swizzled component has been correctly picked up.

Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

It’s definitely certain that we won’t be able to completely refuse from swizzling, this is actually not a bad mechanism for change built-in components.
We will also leave additionalLanguages option, because otherwise our users will need to have swizzled prism-include-languages to add more languages -- this is an unnecessary step and just unpleasant action for them.
Therefore, I think we need to update the docs for this new use case - when people want to add custom language. However in most cases this is not needed by anyone, since very few people develop their own programming languages, since this feature is intended only for them, right?

Therefore, I think we need to update the docs for this new use case - when people want to add custom language. However in most cases this is not needed by anyone, since very few people develop their own programming languages, since this feature is intended only for them, right?

That's true. I've added the docs.


how to detect system windows version if on windows?

Plugin
device_info_plugin
Use case
Does there any instructions to do with it?
Proposal
Does there any instructions to do with it?

What do you expect?
There's a ton of information present like productName or buildNumber. My recommendation will be to use buildNumber.

@alexmercerind thank u so much, just realised you are author of arcrylic plugin. very nice work. I just wanna judege the platform to avoid win10 bug you have mentioned in: https://github.com/alexmercerind/flutter_acrylic/issues/6

It seems there is enough info provided to you in device_info_plus check fields as shared on screenshot provided above.
Also check API docs for Windows part to get more info about fields and pick the one you need for your purposes: https://pub.dev/documentation/device_info_plus/latest/device_info_plus/WindowsDeviceInfo-class.html


New Config System

Look into css, which could be a really great fit for lighty — having default settings and overriding some settings for some modes

Make it configurable through Modmenu (See #43)


[type:feat] init sdk starter.

Fixes #3925

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[ ] Your local test passed ./mvnw clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #3930 (3bd0a67) into master (443fb4a) will decrease coverage by 0.41%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #3930      +/-   ##
============================================
- Coverage     70.42%   70.00%   -0.42%
+ Complexity     6765     6725      -40
============================================
  Files           923      923
  Lines         25373    25377       +4
  Branches       2310     2308       -2
============================================
- Hits          17868    17765     -103
- Misses         6133     6244     +111
+ Partials       1372     1368       -4

Impacted Files
Coverage Δ

...java/org/apache/shenyu/common/utils/JsonUtils.java
55.76% <0.00%> (-4.65%)
:arrow_down:

...n/alibaba/dubbo/cache/AlibabaDubboConfigCache.java
47.12% <0.00%> (-31.04%)
:arrow_down:

.../client/server/consul/ShenyuConsulConfigWatch.java
60.41% <0.00%> (-25.00%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
70.40% <0.00%> (-19.39%)
:arrow_down:

...yu/sync/data/http/refresh/AbstractDataRefresh.java
68.96% <0.00%> (-13.80%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

...org/apache/shenyu/admin/model/dto/AuthPathDTO.java
58.82% <0.00%> (-5.89%)
:arrow_down:

...rg/apache/shenyu/plugin/rewrite/RewritePlugin.java
66.66% <0.00%> (-5.56%)
:arrow_down:

... and 28 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Issue with intl module

Hi, thank you for creating this package, it seems really useful!
Unfortunately, the intl module doesn't seem to be working properly within PHP when using arn:aws:lambda:eu-west-2:753240598075:layer:Php82FpmNginxArm:13
Do you have any idea why this wouldn't be enabled? Thanks!

Hi, thank you for creating this package, it seems really useful!
Unfortunately, the intl module doesn't seem to be working properly within PHP when using arn:aws:lambda:eu-west-2:753240598075:layer:Php82FpmNginxArm:13
Do you have any idea why this wouldn't be enabled? Thanks!

Can you provide some logs or screenshots?


FIX: Expand options

Simple change to allow specifying the shells. I needed it sooner than I thought @agramfort :)

We apparently can't rely on Travis, so I'm going to run tests as we need it.

@dengemann can you have a look? I'm going to test locally and merge if all is okay.

Merging so we can keep progressing toward release.


Fix projectname to targetname

Resolves documentation issue of project name to target name.

duplicate of another PR.


Implement a subcommand to list a component's imports and exports

I was running through the tutorial for building and composing components earlier this week and I made a mistake when building one of the components where the component was not exporting what I thought it was and when I tried to compose the components, the import that was being looked for was simply not found.
I looked through the existing tools and found that the information necessary to debug this is tucked away behind debug logs or is printed alongside so much other information that it's difficult to find. In either case, the information I needed to find this was not easily discoverable.
Based on that I thought it'd be useful to have a small and simple tool whose sole purpose is strictly to list a component's imports and exports with the hope that it'd be a useful tool for working with component composition. I wasn't sure about the use of world for the subcommand name, if there's a better one I'd be happy to change it.
Here's some example output just from the tutorial components:
$ cargo run -- world /tmp/calculator.wat
   Compiling wasm-tools v1.201.0 (/home/ssnover/dev/wasm-tools)
    Finished dev [unoptimized + debuginfo] target(s) in 5.46s
     Running `/barge/cargo-target/debug/wasm-tools world /tmp/calculator.wat`
{
  "imports": [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  ],
  "exports": [
<EMAIL_ADDRESS>  ]
}

$ cargo run -- world /tmp/adder.wat
    Finished dev [unoptimized + debuginfo] target(s) in 0.09s
     Running `/barge/cargo-target/debug/wasm-tools world /tmp/adder.wat`
{
  "imports": [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>  ],
  "exports": [
<EMAIL_ADDRESS>  ]
}

Finally, I added a simple test based on the component in one of the dump tests, but am happy to add more tests if y'all think it'd be warranted.

This is indeed very useful! However, I think this might be the same information that one gets from wasm-tools component wit - is there a difference besides the formatting as json?

Ha! That's embarrassing, that is indeed almost identical output. Thanks for pointing me in the right direction!


Support PipelineSync on OUT_OF_SYNC

What this PR does / why we need it:
Currently, sync strategy on OUT_OF_SYNC is QUICK_SYNC and this is unchangeable feature.
This can be fixed by using SyncStrategy_AUTO to entrust strategy detection to planner.
Which issue(s) this PR fixes:
NONE
Does this PR introduce a user-facing change?:

How are users affected by this change:
ppl who configure pipeline sync and expect to use OnOutOfSync trigger forcibly QUICK_SYNC, experience PIPELINE_SYNC (I believe this is rare case)

Is this breaking change:
I don't think so

How to migrate (if breaking change):
NONE

ppl who configure pipeline sync and expect to use OnOutOfSync trigger forcibly QUICK_SYNC, experience PIPELINE_SYNC (I believe this is rare case)

@golemiso I totally agree with this point. Basically, the current spec for this part is always making the deployment quick sync to ensure that one diff happens between cluster and manifest, and sync is applied as soon as possible if users enable the onOutOfSync trigger (since they want that, we think). Maybe, after this PR, we can introduce a new flag/config to the onOutOfSync trigger like alwaysQuickSync or alwaysPipelineSync, but it's beyond this PR context. Thanks for contribution 🙏

[JFYI] https://github.com/pipe-cd/pipecd/pull/2795 might be the background of the current spec.


fix: fix JWT parse bug

fix: Access token not found in JWT payload.

update AuthService.java

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.郑旺旺 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Initial load

It's keep giving error when login into the app.
ERROR TypeError: undefined is not an object (evaluating 'this.nativeView.selectItemAnimated')

iOS 11.2.5 iphone 6
tns 3.4.0
tns ios 3.4.1

{
  "description": "xxx",
  "license": "SEE LICENSE IN <your-license-filename>",
  "readme": "NativeScript Application",
  "repository": "<fill-your-repository-here>",
  "nativescript": {
    "id": "org.nativescript.xxxx",
    "tns-android": {
      "version": "3.4.0"
    },
    "tns-ios": {
      "version": "3.4.1"
    }
  },
  "dependencies": {
    "@angular/animations": "~4.4.1",
    "@angular/common": "~4.4.1",
    "@angular/compiler": "~4.4.1",
    "@angular/core": "~4.4.1",
    "@angular/forms": "~4.4.1",
    "@angular/http": "~4.4.1",
    "@angular/platform-browser": "~4.4.1",
    "@angular/router": "~4.4.1",
    "email-validator": "^1.1.1",
    "nativescript-angular": "~4.4.0",
    "nativescript-bottom-navigation": "^1.0.2",
    "nativescript-couchbase": "^1.0.18",
    "nativescript-floatingactionbutton": "4.1.3",
    "nativescript-fontawesome": "1.0.0",
    "nativescript-geolocation": "^4.2.2",
    "nativescript-gradient": "^2.0.1",
    "nativescript-iqkeyboardmanager": "1.1.0",
    "nativescript-photoviewer": "1.2.0",
    "nativescript-pro-ui": "3.3.0",
    "nativescript-theme-core": "~1.0.2",
    "reflect-metadata": "~0.1.8",
    "rxjs": "~5.4.2",
    "tns-core-modules": "^3.4.0",
    "zone.js": "^0.8.19"
  },
  "devDependencies": {
    "babel-traverse": "6.26.0",
    "babel-types": "6.26.0",
    "babylon": "6.18.0",
    "lazy": "1.0.11",
    "nativescript-dev-typescript": "~0.5.0",
    "typescript": "~2.4.2"
  }
}

The issue is when i call selectTab()

Hi,
Can u pealse send me an example of how are you using the selectTab and when?
On Jan 31, 2018 9:21 PM, "Dalia Carlón"<EMAIL_ADDRESS>wrote:
It's keep giving error when login into the app.
ERROR TypeError: undefined is not an object (evaluating 'this.nativeView.
selectItemAnimated')

iOS 11.2.5 iphone 6
tns 3.4.0
tns ios 3.4.1

{
"description": "xxx",
"license": "SEE LICENSE IN ",
"readme": "NativeScript Application",
"repository": "",
"nativescript": {
"id": "org.nativescript.xxxx",
"tns-android": {
"version": "3.4.0"
},
"tns-ios": {
"version": "3.4.1"
}
},
"dependencies": {
"@angular/animations": "~4.4.1",
"@angular/common": "~4.4.1",
"@angular/compiler": "~4.4.1",
"@angular/core": "~4.4.1",
"@angular/forms": "~4.4.1",
"@angular/http": "~4.4.1",
"@angular/platform-browser": "~4.4.1",
"@angular/router": "~4.4.1",
"email-validator": "^1.1.1",
"nativescript-angular": "~4.4.0",
"nativescript-bottom-navigation": "^1.0.2",
"nativescript-couchbase": "^1.0.18",
"nativescript-floatingactionbutton": "4.1.3",
"nativescript-fontawesome": "1.0.0",
"nativescript-geolocation": "^4.2.2",
"nativescript-gradient": "^2.0.1",
"nativescript-iqkeyboardmanager": "1.1.0",
"nativescript-photoviewer": "1.2.0",
"nativescript-pro-ui": "3.3.0",
"nativescript-theme-core": "~1.0.2",
"reflect-metadata": "~0.1.8",
"rxjs": "~5.4.2",
"tns-core-modules": "^3.4.0",
"zone.js": "^0.8.19"
},
"devDependencies": {
"babel-traverse": "6.26.0",
"babel-types": "6.26.0",
"babylon": "6.18.0",
"lazy": "1.0.11",
"nativescript-dev-typescript": "~0.5.0",
"typescript": "~2.4.2"
}
}
The issue is when i call selectTab()
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/henrychavez/nativescript-bottom-navigation/issues/8,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF0NmbDfRBMFK3vl8K3wL2X9SpoBrTm1ks5tQR-bgaJpZM4R09Eh
.

I have a main.ts that is the hole "frame/ container" of the project, when login is redirecting to this.router.navigate(["/main/prm"], { clearHistory: true });, that execute the main.ts:
import { Component, OnInit,OnDestroy,ElementRef,ViewChild } from "@angular/core";
import { BottomNavigation, OnTabSelectedEventData, BottomNavigationTab } from 'nativescript-bottom-navigation';
import { Router} from "@angular/router";
import { Page} from "ui/page";
import {ConnectionInfo} from "../../services/connectivity.service";
import { isAndroid } from "platform";
import { AppComponent } from "../../app.component";

@Component(
  {
    selector: "main",
    moduleId: module.id,
    templateUrl: "main.component.html"
  }
)
export class mainComponent implements OnInit {
  @ViewChild("bottomNav") bottomNavChild:ElementRef;
  bottomNav:BottomNavigation;
  pestanhaInicial:number=1;

  rutas:any[] =
            [{ruta:"/main/vtc",color:"#4EDFC2"},
            {ruta:"/main/prm",color:"#FD7E7E"},
            {ruta:"/main/cnd",color:"#2196F3"},
            {ruta:"/main/news",color:"#F9883B"},
            {ruta:"/main/tips",color:"#FFB901"}]
  online:boolean = true;
  actual : number=1;

  constructor(private router:Router, private page: Page, private connectionInfo: ConnectionInfo, private component: AppComponent){}
  ngOnInit(){

    this.bottomNav = this.bottomNavChild.nativeElement;
    if(isAndroid){
      this.bottomNav.inactiveColor="lightgray";
      this.bottomNav.backgroundColor="white";
      this.bottomNav.activeColor=this.rutas[this.pestanhaInicial].color;
      this.bottomNav.selectedTabIndex = this.pestanhaInicial;
    }
    else{
      this.bottomNav.selectTab(this.pestanhaInicial);
    }

    this.router.navigate(['/main/prm'],{replaceUrl:true});
  }

  onBottomNavigationTabSelected(args: OnTabSelectedEventData){
    this.actual = args.newIndex;
    let destiny:string = this.rutas[this.actual].ruta;
    let color:string = this.rutas[this.actual].color;
    this.router.navigate([destiny],{replaceUrl:true});
    this.bottomNavChild.nativeElement.activeColor=color;

    this.component.checkToken();
  }
}

I think it is because the bottomnavigation isn't build yet.

If i don't explain well, i could explain it in spanish

@dalsscarlon sorry the delay I didn't receive a notification.
The problems is when you call the selectTab the BottomNavigationBar is not created yet.
But I see that you are using the selectedTabIndex for android and it's working, so I'll update the plugin to do the same on iOS.
I let you now when is ready so you can have
this.bottomNav.inactiveColor="lightgray";
this.bottomNav.backgroundColor="white";
this.bottomNav.activeColor=this.rutas[this.pestanhaInicial].color;
this.bottomNav.selectedTabIndex = this.pestanhaInicial;

without the if statement

The bug was fixed in the version 1.1.3 of the plugin. :D


Bilinear Search

Algorithm: Bilinear Search
Bilinear search is a modified version of linear search where it searches from both direction.
It's a variation of linear search to search a element in an list/array.It search from both side.
Languages Supported:

C : [@sparkingdark ]
CPP :
Python : [@sparkingdark ]
Java :
JavaScript :
GO :
C# :
Q# :

I can take it in c++.

@Rishabh7896 Sure. You can start working on this issue in C++.
Happy Coding.

I would like to work on this in java

@rohangawhade Assigned in Java.
Make sure you go through the Contribution guidelines.
Happy coding.


1.20.1 Ores does not spawn at all.

Please fix this, literally the only thing that shows up from your mod is oil shale on planets/moons that can spawn them. Otherwise, mod is completely broken and functionally useless.

it works for me on the ad astra version I have in dev, they may have changed things since I worked on my addon


Enable vectorization for CPUBufferOpsTileAndVectorize pipeline

I'm not able to repro the issue locally, and the e2e/matmul tests passed on my local machine. Let's see if we'll see issues on CI..

I just found that I did not add vectorization pass to the pipeline... I'll revisit it..


server side: listeners

for:

file arrived telling only which dataset and the filename (path to it)
lineage arrived telling which dataset, date, time, user, noOfSpots, noOfLinks

Also, implement example listeners that use:

call external (gnuplot) to plot a graph
use https://github.com/xulman/logs-processor

listeners are done in commit 1e1315b3b68019fc7811592b5a847e0f8be843ab

both "example" listeners were merged in commit 4a6ab4fb26606d3eafb7f5f1246ed2313c7cff49


checkbox cell editor switch support

f_switch support for checkbox cell editor

A cell editor now has a style property. This property can be used for switch detection.

and also check if editor contains f_switch.
It should be possible to use a checkbox in table and a switch for an editor...

The editor already supports f_switch.
The editor should also support f_checkbox.
This makes it possible to configure a cell editor as f_switch but show the checkbox as editor!

Now, editor contains a merged style property:
...
"cellEditor" : {
      "className" : "CheckBoxCellEditor",
      "text" : null,
      "selectedValue" : null,
      "deselectedValue" : null,
      "directCellEditor" : true,
      "horizontalAlignment" : 1,
      "verticalAlignment" : 1,
      "style" : "f_switch"
    },
"ariaLabel" : "Check",
"style" : "f_checkbox",
"parent" : "SP75",
"eventFocusGained" : true,
"indexOf" : 14,
"cellEditor_text_" : "Check",
"cellEditor_editable_" : true,
"cellEditor_horizontalAlignment_" : 1,
"cellEditor_verticalAlignment_" : 1,
"cellEditor_style_" : "f_checkbox,f_switch",
"constraints" : "t13;lm;b13;rm"
}

Now, editor contains a merged style property:
...
"cellEditor" : {
      "className" : "CheckBoxCellEditor",
      "text" : null,
      "selectedValue" : null,
      "deselectedValue" : null,
      "directCellEditor" : true,
      "horizontalAlignment" : 1,
      "verticalAlignment" : 1,
      "style" : "f_switch"
    },
"ariaLabel" : "Check",
"style" : "f_checkbox",
"parent" : "SP75",
"eventFocusGained" : true,
"indexOf" : 14,
"cellEditor_text_" : "Check",
"cellEditor_editable_" : true,
"cellEditor_horizontalAlignment_" : 1,
"cellEditor_verticalAlignment_" : 1,
"cellEditor_style_" : "f_checkbox,f_switch",
"constraints" : "t13;lm;b13;rm"
}


Add prometheus exporter for RHEL4EDGE

This PR adds a -prometheus flag to the image-builder build script. At the moment that is specifically the process-exporter which provides pidstat like data for all host processes.
Small bugfixes for build.sh also included as well as firewall customization to allow inbound connections to the exporter.

/assign @ggiguash

@sjug please squash the commits when you make the last change.

/lgtm


Token Management

related to #38
This PR begins the work for allowing accessing mollymawk solely via it's API.
API tokens are no longer created when a user creates an account.
The user can manually create an API token from their dashboard.
The API tokens now have new fields:

name : to help the user differentiate between different keys e.g (GitHub, GitLab)
last_access: when last was the specific key used to query mollymawk
usage_count: how many times this key has been used

looks fine to me, please merge when you think it is ready

Thank you @hannesm for the review.


Could not load System.Data.SqlClient?

Describe the bug
I'm creating an application which will load plugins from a directory (.\Extensions) in .NET Core 3.1 that's why I chose this library. Previously (in .NET 4.6.2) I was using AppDomain.AssemblyResolve to resolve dependencies and share some assemblies with the plugins. More details below.
My project structure is basically this :

A main host app,
a core logic library (shared with plugins),
a UI library (optionally shared with plugins)

The plugins will reference the core library and the UI library (in some cases).
The main host app will resolve dependencies of the plugins using AppDomain.AssemblyResolve and share the core logic and UI libs with them.
This method still works. But I want features of this library such Unloading, HotReload, etc.
So I switched to use this library and changed the code correspondingly.
But the problem is all 3 libraries are WPF .NET Core 3.1 libraries
The Core logic library depends on System.Drawing and the UI library depends on a 3rd party library (ModernWpf)
So to overcome the isolation boundry I have to share the types common to them like this :
private static PluginLoader GetDefaultLoader(string dllloc)
{
    return PluginLoader.CreateFromAssemblyFile(
                dllloc,
                isUnloadable: true,
                sharedTypes: new Type[]
                {
                    typeof(Core.ExtensionBase),
                    typeof(UI.BuskBar.IBuskBarItem),
                    typeof(ModernWpf.ApplicationTheme),
                    typeof(ModernWpf.Controls.AppBarButton),
                    typeof(System.Drawing.Image),
                });
}

I expected it to work like in .NET 4.6.2 (using AppDomain.AssemblyResolve) but it doesn't.
It throws this System.IO.FileNotFoundException saying
"Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified."

None of my projects/their dependencies depend on System.Data.SqlClient. I checked all of their *.deps.json. What should I do?

To Reproduce
Steps to reproduce the behavior:
I'm on a tight schedule and I can't provide any repro of it but basically

Create 2 WPF class library projects (one *.Core -> depends on System.Drawing.Common and one *.UI -> depends on ModernWpf).
Reference those 2 in a new WPF Application project.
Create a skeletal structure of my project -> a abstract class ExtensionBase in the *.Core project and a interface IBuskBarItem in *.UI project.
Create a basic WPF class library project called MyPlugin reference the UI and Core project with copy local set to false.
Try to load the plugin assembly (MyPlugin.dll) using the afore-mentioned GetDefaultLoader(path_to_plugin).
You will get a System.IO.FileNotFoundException like I mentioned above.

Expected behavior
I don't have any dependencies to System.Data.SqlClient. I want mine to work like it did in .NET 4.6.2
Screenshots

Additional context
I even tried to remove the *.Core and *.UI references from the plugin and modified the loading as
private static PluginLoader GetDefaultLoader(string dllloc)
{
    return PluginLoader.CreateFromAssemblyFile(
                dllloc,
                isUnloadable: true,
                sharedTypes: new Type[]
                {
                    typeof(Core.ExtensionBase)
                });
}

The plugin is basically just an empty dll but it still throws the same error.
It only works if there are no shared types (But what's the point of plugin then?) like this:
private static PluginLoader GetDefaultLoader(string dllloc)
{
    return PluginLoader.CreateFromAssemblyFile(
                dllloc,
                isUnloadable: true,
                sharedTypes: new Type[] { });
}

The architecture of my project :

What is your in your csproj file? SqlClient is one of the test cases in this project. https://github.com/natemcmaster/DotNetCorePlugins/blob/ad66725684cc1c9b293146bd215749a6f651cf10/test/TestProjects/SqlClientApp/SqlClientApp.csproj. Make sure you use netcoreapp, not netstandard.

Yes I use netcoreapp3.1 and not netstandard. WPF needs atleast .NET core 3.0

The error won't show when there are no shared types or assemblies

None of my projects/their dependencies depend on System.Data.SqlClient. I checked all of their *.deps.json. What should I do?

Can you share your csproj files? Perhaps you are pulling this dependency somehow transitively.

Sorry I can't for now, after a week maybe?

 The system cannot find the file specified."

while commit 1ef9c3e will work (how?) since the UseWPF tags has been removed from those projects.

You can see that those projects are just basic libs with no dependencies and if I have UseWPF, they don't work 🤔 with this lib
Should I update this issue to be This library doesn't work with WPF libraries?

I am trying to solve the same problem.
But trying your repo I have no problems in its execution, the SqlClient error does not appear.
Tested with Visual Studio Preview 16.7.0 Preview 2.0

Changing UseWPF tags has no difference.

I does throw error and I'm using the same visual studio version 😅

I will update the repo

Actually this problem appeared in the initial tests that I made of this library and then I managed to solve it, with which I took advantage of its use, but I am trying to remember what the solution path was.
Since we came from using MEF for the implementation of plugins, what was missing in the McMaster library was detecting the available plugins without loading the assemblies, so implement the metadata reading of the files through attributes, with which a list of the available plugins and their characteristics is obtained to be able to select them from a categorized list, thus obtaining the path to the assembly that contains it and the name of the plugin.
With this data the creation of the instance is done with the current library, which is where the infamous SqlClient error appears.

But I can't even load the assembly to check if it's contains a plugin

Output Window shows My Extension load

What's the .NET Core SDK you're using. It may be rooting from the sdk maybe

This is our scenario.
At left the breakpoint in the exception generated.
Ar right the plugin width the Export Attributes at MEF style

Still experiencing the bug 😞

5.0.100-preview.5.20279.10

No I asked the .NET Core 3.1 SDK version installed in your system that you used to build my repo

3.1.400-preview-015151

So we have the same SDK but it throws error on my machine? I will try to upload a more reproducible repo

And a note : it also works if no types are passed as sharedTypes. Try that and see if it still happens

One of the errors I found in your repo is in debug mode in output path for MyExtension dlls storage.
Must be "Debug" instead "Release".
Verifiy it

You are right.
return PluginLoader.CreateFromAssemblyFile(
dllloc,
isUnloadable: true,
sharedTypes: new Type[]
{
/*
typeof(ExtensionBase),
typeof(IUIItem) // Not neccessary
*/
});
Also works, when the list must be empty.

One of the errors I found in your repo is in debug mode in output path for MyExtension dlls storage.
Must be "Debug" instead "Release".
Verifiy it

..\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.exe
..\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll
They are both in the same folder 🤔

Hmmm... This branch seems to work. I removed this
[assembly: ThemeInfo(
    ResourceDictionaryLocation.None, //where theme specific resource dictionaries are located
                                     //(used if a resource is not found in the page,
                                     // or application resource dictionaries)
    ResourceDictionaryLocation.SourceAssembly //where the generic resource dictionary is located
                                              //(used if a resource is not found in the page,
                                              // app, or any theme specific resource dictionaries)
)]

from the AssemblyInfo.cs and the UseWPF tag is still present. What's happening?

Sorry, may be my mistake.
I am trying loader without types in our solution.
No error happens, and no plugin is loaded, what is correct.
Seems to be that error happens in assembly loading.
Evidently are not clear differences between your environment and our.
Your instance loads all the plugins availables in the assembly withour type defined.
and our instance don't loads without a type but fires error alt loading.

One of the errors I found in your repo is in debug mode in output path for MyExtension dlls storage.
Must be "Debug" instead "Release".
Verifiy it

..\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.exe
..\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll
They are both in the same folder 🤔

Sorry, the problem is in Release mode, that points to Debug Folder

The new repo works in the same way that previous, with or without type definition

Hey @natemcmaster, I can't choose to remove AssemblyInfo.cs since it has InternalsVisibleTo and XmlnsDefinition attributes. Any help?

Now working in a new approach to find the real problem of assembly loading.
Talk to you in a while.

As our famous friend Jack said, go by peaces.
In out case.
Eliminating types in sharedTypes resolves the SqlClient error, your big tip.
Later we select the correct plugin comparing the class name reported by loader (who has all the classes existing in the assembly) with the desired class, and instantiate that.
Your case is different because in all the scenarios we test always works.
But something is wrong in the loader code because sharedTypes seems to be irrelevant in your case, and error prone in our.
Hope this info help to your problem.
If not, we stay in contact to test your repos until find the solution.

No no... You got it wrong the SHARED TYPES are important and not sharing will cause a issue see What is a shared type. Loading assembly without passing shared types/assemblies may work in some cases but will cause bugs in many cases. There must some be some types/assemblies that have to be shared with plugins. Not passing types is pointless. I said it doesn't throw error if there are no shared types never said it will work fine. The problem is not with assembly loading but with dependency resolving of those plugins.
My host tries to load MyExtension.dll which references *.Core.dll and *.UI.dll. So they also need to resolved, not from a file but from the host. The host also references those 2 DLLs. So the host must give them to plugin, thus the types will be shared. The problem is in the dependency resolving. You get it. It may seem to work, but will crash at some point

My approach of instantiating plugins may be different since I use an abstract class instead of an interface. But my problem I have to load the assembly and resolve it's dependencies at first.
Then I look through the types in those plugin and load the type that is a derivative of the base class.
I'm not saying I can't instantiate the types. My problem is can't even load them! That's my issue. Yours case seem to be different from mine

Ok.
Looking to the original problem.
I remember that in the process of developing the MEF emulation we had the same problem.
If we installed the SqlClient library then there was another required library and so on.
What solved the problem was to load the environment libraries with
var runtimeAssemblies = Directory.GetFiles (RuntimeEnvironment.GetRuntimeDirectory (), " .dll");*
We have 2 levels, one with base implementation for all platforms and another, for example, for WPF.
At WPF level we have:
namespace TWPF.Core.Data.Plugins
{
	///
	/// Clase para administracion de plugins wpf
	///
	public class Manager
	{
		#region Metodos Publicos ------------------------------------------------------------------
		/// Devuelve lista de plugins existentes en una carpeta base
		/// <param name="folderPath"></param>
		/// <param name="key"></param>
		/// <returns></returns>
		public static ObservableCollection<TKER.Core.Data.Plugins.Base> GetFromFolder(
			string folderPath,
			string key = "")
		{
			// Get the array of runtime assemblies.
			var runtimeAssemblies = Directory.GetFiles(RuntimeEnvironment.GetRuntimeDirectory(), "*.dll");

			// Create the list of assembly paths consisting of runtime assemblies and the inspected assembly.
			var paths = new List<string>(runtimeAssemblies);

			return TKER.Core.Data.Plugins.Manager.GetFromFolder(paths, folderPath, key);
		}
		#endregion
	}
}

And at base level with NETCore
namespace TKER.Core.Data.Plugins
{
	///
	/// Clase para administracion base de plugins
	///
	public class Manager
	{
		#region Metodos Publicos ------------------------------------------------------------------
		/// Devuelve lista de plugins existentes en una carpeta base
		/// <param name="assyPaths"></param>
		/// <param name="searchPath"></param>
		/// <param name="key"></param>
		/// <returns></returns>
		public static ObservableCollection<Base> GetFromFolder(
			List<string> assyPaths,
			string searchPath,
			string key = "")
		{
			var Plugins = new ObservableCollection<Base>();
			var asm = typeof(Manager).Assembly;
			assyPaths.Add(asm.Location);

			// Busqueda de archivos en carpeta base ingresada .dll
			var pluginFiles = Directory.GetFiles(searchPath, "*.dll", SearchOption.AllDirectories);

			// Carga rutas de archivos .dll existentes
			foreach (var pluginFile in pluginFiles)
			{
				assyPaths.Add(pluginFile);
			}

			// Create PathAssemblyResolver that can resolve assemblies using the created list.
			var resolver = new PathAssemblyResolver(assyPaths);

			using (var context = new MetadataLoadContext(resolver))
			{
				// Lazo para cada archivo dll encontrado
				foreach (var pluginFile in pluginFiles)
				{
					var assembly = context.LoadFromAssemblyName(Path.GetFileNameWithoutExtension(pluginFile));

					// Lazo para cada clase del assembly
					foreach (var pluginType in assembly.GetTypes())
					{
						Global.Trace.Logger.DebugOutput(MethodBase.GetCurrentMethod(), "Plugin Found => " + pluginType.FullName);

						var pluginData = new Base();
						pluginData.AssemblyLocation = assembly.Location;
						var attrCol = pluginType.GetCustomAttributesData();
						var isAttrValid = false;

						// Lazo para cada atributo existente en la clase seleccionada
						foreach (var customAttributeData in attrCol)
						{
							if (customAttributeData.AttributeType.FullName == typeof(PluginExportAttribute).ToString())
							{
								isAttrValid = true;

								for (var i = 0; i < customAttributeData.NamedArguments.Count; i++)
								{
									Global.Trace.Logger.DebugOutput(MethodBase.GetCurrentMethod(), "Arg " + i + " = " + customAttributeData.NamedArguments[i]);
									var fieldName = customAttributeData.NamedArguments[i].ToString().GetBefore(" ");

									foreach (var propertyInfo in pluginData.GetType().GetProperties())
									{
										if (propertyInfo.Name == fieldName)
										{
											switch (propertyInfo.PropertyType.Name)
											{
												case "String":
													var dataString = customAttributeData.NamedArguments[i].ToString()
														.GetAfter("= ");

													propertyInfo.SetValue(pluginData, dataString);

													break;

												case "String[]":
													var strComma = customAttributeData.NamedArguments[i].ToString()
														.Replace(" ", string.Empty)
														.GetAfter("{")
														.GetBefore("}");

													var array = strComma.Split(',');
													propertyInfo.SetValue(pluginData, array);

													break;

												case "Guid":
													var dataGuid = customAttributeData.NamedArguments[i].ToString()
														.Replace(" ", string.Empty)
														.GetAfter("=");

													propertyInfo.SetValue(pluginData, new Guid(dataGuid));

													break;

												case "Boolean":
													propertyInfo.SetValue(pluginData, customAttributeData.NamedArguments[i].ToString().Contains("True"));

													break;

												case "TKER.Core.Data.Version":
													var dataVersion = new Version();
													dataVersion.Parse(customAttributeData.NamedArguments[i].ToString());
													propertyInfo.SetValue(pluginData, dataVersion);

													break;
											}

											break;
										}
									}
								}
							}
						}

						if ((key == "" || pluginData.PluginType == key) && isAttrValid)
						{
							Plugins.Add(pluginData);
						}
					}
				}
			}

			return Plugins;
		}
		#endregion
	}
}

We are going to test again this approach to see if loading SqlClient may be resolved, because in first attempts was not successful.
Take a look to this routines, because may be useful to you to get metadata of plugins without loading assemblies.
Ask me if you need explanation about the code.
We stay in contact

But for creating an instance you still need to load assemblies and resolve their deps

Yes.
this is where we make the instance of loaded plugin.
protected async void SolutionCreateConfirmAsync()
		{
			StringBuilder errors = new StringBuilder();

			#region Test items completos.
			foreach (var solutionProject in this.SolutionProjects)
			{
				if (solutionProject.IsSelected == true)
				{
					if (string.IsNullOrEmpty(solutionProject.Name))
					{
						errors.AppendLine("No Name in " + solutionProject.Title);
					}
				}
			}

			if (string.IsNullOrEmpty(this.NewSolutionName))
			{
				errors.AppendLine("Empty Solution Name");
			}

			if ((this.IsStorageCustom) && (string.IsNullOrEmpty(this.NewSolutionFolder)))
			{
				errors.AppendLine("Empty Solution Folder");
			}

			if (errors.Length > 0)
			{
				await Manager.ShowLocalMessage(
					"Error en Configuracion de Solucion Nueva",
					"Core_States_Error",
					"La configuracion de la solucion nueva tiene errores.",
					"Verifique los siguientes elementos faltantes",
					errors.ToString(),
					GlobalData.SysButtonId.Ok);

				return;
			}
			#endregion

			#region Solution Create
			try
			{
				var loader = PluginLoader.CreateFromAssemblyFile(
					this.SolutionTemplateSelected.AssemblyLocation,
					isUnloadable: true,
					sharedTypes: new Type[]
					{
						//typeof(TekStudio.Core.Modules.Solutions.IBase)
					}
					);

				foreach (var pluginType in loader
					.LoadDefaultAssembly()
					.GetTypes()
					.Where(t => t.Name == this.SolutionTemplateSelected.ClassName))
				{
					TekStudio.Core.Modules.Solutions.Base solution = (TekStudio.Core.Modules.Solutions.Base)Activator.CreateInstance(pluginType);

					// Carga datos de la metadata del plugin a la clase instanciada
					solution.ViewModel.Model.Config.Plugin = this.SolutionTemplateSelected;
					solution.ViewModel.Model.Config.Name = this.NewSolutionName;
					solution.ViewModel.Model.Config.StorageRootPath = this.NewSolutionFolder;
					solution.ViewModel.Model.Config.DateTimeCreated = DateTime.Now;
					solution.ViewModel.Model.Config.Version = new Version(1, 0, 0, 0);
					solution.Title=this.NewSolutionName;

					TsGlobal.App.ShellViewModel.DockApps.Add(solution);
				}
			}
			catch (Exception e)
			{
				Console.WriteLine(e);
			}
			#endregion
		}

In Solution Create region

The real problem will be seen if you do this
var loader = PluginLoader.CreateFromAssemblyFile(
    this.SolutionTemplateSelected.AssemblyLocation,
    isUnloadable: true,
    sharedTypes: new Type[]
    {
        typeof(TekStudio.Core.Modules.Solutions.IBase)
    });

instead of this
var loader = PluginLoader.CreateFromAssemblyFile(
    this.SolutionTemplateSelected.AssemblyLocation,
    isUnloadable: true,
    sharedTypes: new Type[]
    {
        //typeof(TekStudio.Core.Modules.Solutions.IBase)
    });

Ok from what I understood:

You are using MetadataLoadContext to load assemblies and PathAssemblyResolver to resolve their deps
You are getting the assembly datas from the assemblies you want which you loaded using MetadataLoadContext
You don't need MetadataLoadContext this McMaster library already can do the job of MetadataLoadContext and PathAssemblyResolver combined.
You are using var assembly = context.LoadFromAssemblyName(Path.GetFileNameWithoutExtension(pluginFile)); to get the assembly. I use loader.LoadDefaultAssembly(). Basically the same.
I use this McMaster library to both verify plugin and  load plugin. You use MetadataLoadContext to verify if it's a plugin and this library to load them.

You're manually doing things that this library can already do. That's why I'm using this library
You are not passing any shared type? read my comment

The functionality of the #first few functions is just to take the metadata info from the assemblies without loading them, which was a great MEF function.
In our project, the number of available plugins can be high, so we cannot load them all.
When consulted with McMaster, he said that this was not implemented and that it should be resolved outside the current library.
That is the reason why we do it manually without using the McMaster library.
Then we use the McMaster library to load the selected plugin, since it should solve the loading problems of the assemblies required by the plugin.
Your comment about shared types is noted and we are looking about.

So you're just getting metadata from *.dll files and store those metadata in a list -> use those metadatas to verify plugins -> load plugin using this library.
I used this library for all of them 😅. But we will have the same problem if there are sharedTypes, don't we?

Exactly.
We have the same problem.
The difference in our projects is that you load all plugins assemblies and we don't.

So the real problem is hitting when we use this library and try to load a library which is WPF library.
The problem must be with the either ManagedLoadContext or AssemblyLoadContext inside this library.
Your first approach works because MetadataLoadContext is different from AssemblyLoadContext

But...
Why your repo works in our machine?
And plugins seems to be loaded and instantiated correctly.

But...
Why your repo works in our machine?
And plugins seems to be loaded and instantiated correctly.

That's what I thinking. Honestly I don't why it happens to work for you. That's why I said

Hey @Teknel, I can't find a best example issue repro. Mine seems to be confusing. Can you provide a repro of your issue and I will update this issue to reflect yours too

Looks that we must to focus more on environment than in the library for your case.
But VS and NETCore seems to be the same.
Another info reported by System Information:
System Information report written at: 06/19/20 09:17:24
System Name: TEK-MASTER
[System Summary]
Item	Value
OS Name	Microsoft Windows 10 Pro
Version	10.0.19041 Build 19041
Other OS Description 	Not Available
OS Manufacturer	Microsoft Corporation
System Name	TEK-MASTER
System Manufacturer	Gigabyte Technology Co., Ltd.
System Model	Z390 GAMING X
System Type	x64-based PC
System SKU	Default string
Processor	Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date	American Megatrends Inc. F6, 12/4/2018
SMBIOS Version	3.1
Embedded Controller Version	255.255
BIOS Mode	UEFI
BaseBoard Manufacturer	Gigabyte Technology Co., Ltd.
BaseBoard Product	Z390 GAMING X-CF
BaseBoard Version	Default string
Platform Role	Desktop
Secure Boot State	Off
PCR7 Configuration	Binding Not Possible
Windows Directory	C:\WINDOWS
System Directory	C:\WINDOWS\system32
Boot Device	\Device\HarddiskVolume7
Locale	United States
Hardware Abstraction Layer	Version = "10.0.19041.1"
User Name	TEK-MASTER\tek-m
Time Zone	Argentina Standard Time
Installed Physical Memory (RAM)	64.0 GB
Total Physical Memory	63.9 GB
Available Physical Memory	34.8 GB
Total Virtual Memory	63.9 GB
Available Virtual Memory	28.6 GB
Page File Space	0 bytes
Kernel DMA Protection	Off
Virtualization-based security	Not enabled
Device Encryption Support	Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and device is not Modern Standby, Un-allowed DMA capable bus/device(s) detected, TPM is not usable
Hyper-V - VM Monitor Mode Extensions	Yes
Hyper-V - Second Level Address Translation Extensions	Yes
Hyper-V - Virtualization Enabled in Firmware	Yes
Hyper-V - Data Execution Protection	Yes

What I can offer you is a TeamViewer session so you can use our environment with your solution

I'm on a limited data plan, I can't use TeamViewer 😅 but thanks for your offering. I very happy you're helping with me in this issue ❤.

What I can do is to test your solution in other of our machines.
I wil do and tell you soon.

Thanks a lot @Teknel. I'm very lucky to have your help

Same result.
Repo works fine.
This is the output info:
'ExtensibilityTest.exe' (CoreCLR: DefaultDomain): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Private.CoreLib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.dll'. Symbols loaded.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\PresentationFramework.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\WindowsBase.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\System.Xaml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Step into: Stepping over non-user code 'ExtensibilityTest.App.Main'
Step into: Stepping over non-user code 'ExtensibilityTest.App..ctor'
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\System.IO.Packaging.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\netstandard.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Private.Uri.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\PresentationCore.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\mscorlib.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\DirectWriteForwarder.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.InteropServices.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.CompilerServices.VisualC.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Diagnostics.Debug.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Threading.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\Microsoft.Win32.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Collections.NonGeneric.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Linq.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Collections.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\Microsoft.Win32.Registry.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Diagnostics.TraceSource.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Collections.Specialized.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.ComponentModel.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Diagnostics.Process.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Threading.Thread.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\System.Configuration.ConfigurationManager.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Xml.ReaderWriter.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Private.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.IO.FileSystem.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Net.WebClient.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Memory.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Security.Cryptography.Algorithms.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Text.Encoding.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Threading.Tasks.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
Step into: Stepping over non-user code 'ExtensibilityTest.App.InitializeComponent'
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.ComponentModel.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Resources.ResourceManager.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.ComponentModel.TypeConverter.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\System.Windows.Extensions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Threading.ThreadPool.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Collections.Concurrent.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.ObjectModel.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\UIAutomationTypes.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\PresentationFramework.Aero2.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Drawing.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\PresentationFramework-SystemXml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'c:\program files (x86)\microsoft visual studio\2019\preview\common7\ide\commonextensions\microsoft\xamldiagnostics\Core\x64\Microsoft.VisualStudio.DesignTools.WpfTap.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Diagnostics.Tracing.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Text.RegularExpressions.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.IO.Pipes.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Console.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Threading.Timer.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Serialization.Xml.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Private.DataContractSerialization.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Serialization.Json.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Serialization.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Reflection.Emit.ILGeneration.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Reflection.Emit.Lightweight.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Reflection.Primitives.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Buffers.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Serialization.Formatters.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\UIAutomationProvider.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App\3.1.4\System.Windows.Controls.Ribbon.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\McMaster.NETCore.Plugins.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.Core.dll'. Symbols loaded.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.UI.dll'. Symbols loaded.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Loader.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll'. Symbols loaded.
My Extension, A test extension to check extensibility
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll'. Symbols loaded.
My Extension, A test extension to check extensibility
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll'. Symbols loaded.
My Extension, A test extension to check extensibility

for each button pressed
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\McMaster.NETCore.Plugins.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.Core.dll'. Symbols loaded.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\ExtensibilityTest.UI.dll'. Symbols loaded.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\3.1.4\System.Runtime.Loader.dll'. Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
'ExtensibilityTest.exe' (CoreCLR: clrhost): Loaded 'C:\Users\Tek-r\Documents\ExtensibilityTest-main\ExtensibilityTest-main\ExtensibilityTest\bin\Debug\netcoreapp3.1\Extensions\netcoreapp3.1\MyExtension.dll'. Symbols loaded.
My Extension, A test extension to check extensibility

It getting too confusing 😂

Do you have similar info in debugging output window?

Hi  @natemcmaster ! Hi @Teknel ! Hi @ShankarBUS !
Any update on this one ? It seems I am getting into same pitfall.

Host application & plugins in .Net Core 3.1 are both referencing a core library (for shared interfaces). This lib is also in .Net Core 3.1.
Some types from the core library are marked as shared types when plugin loaders are created.
Host application & plugin have UseWPF flag set to true. I have yet another plugin without the flag and everything works fine.

Then as soon as I update the core library with the UseWPF flag set to true. It breaks on
{"Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.":"System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a"}

I have tried removing the assembly: ThemeInfo mentioned above. But did not help.

Note that I have also tried to add yet another library to share UI components between host and plugins. This UI lib will have the UseWPF flag set to true, and the other core library have this flag set back to false. Also none of the types defined in this UI library will be used as shared types when loaders are created.
Sadly it still fails on the same error.

Also when removing the shared types of the PluginLoaders, the Assembly are loaded, but I cannot load them this way :)

Thanks for your feedback.

Yet another piece of information.
I tried to upgrade everything to .Net 5 (.Net Core 5) and still fails but exception is a bit different.
Could not load file or assembly 'System.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Note the version number is not set.

I think, I have found a solution that could explain the behavior and that works for me .. it is named Microsoft.Windows.Compatibility

To help those coming back here I had to do the following to get it to work:
Situation: I have a dotnetcore 3.1 lib that is of the type:
<Project Sdk="Microsoft.NET.Sdk.WindowsDesktop" ...  with <UseWPF>true</UseWPF>
I use this project to contain common things that the plugins rely on. The plugins can have UI configuration, which they themselves provide, but having a common set of controls they can use is helpful.
In this core project i had to add the following additional properties
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
    <RestoreProjectStyle>PackageReference</RestoreProjectStyle>

I then had to add a package reference to  <PackageReference Include="Microsoft.Windows.Compatibility" Version="3.1.1" />
This still resulted in some issues - namely that a specifc version of System.Data.Odbc could not be loaded. Noticed that there were no binding redirects generated in my config file for this dll, so adding an app.config to the project with the following got me further:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.Odbc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

This made progress, but still resulted in complaints about the right version of System.Data.OleDb not loaded. Noticed this binding redirect was also missing, but no matter what i tried to do to manually add it, no luck, so instead I added it as a package reference:
<PackageReference Include="System.Data.OleDb" Version="4.7.1" />
And voila, it worked.
@natemcmaster -  IMHO, this dance sucks, I dont even use any System.Data.*  libs. I wish there was an easier way to get this to work without what seems like black dll-magic hackery. But at least there's a workaround

I was getting   "Could not load ..." Error and adding CopyLocalLockFileAssemblies tag solved my issue...
<PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
   <CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
  </PropertyGroup>

I was getting the same error, but in my case I'm targeting net5.0-windows (Desktop application) in my host application and net5.0-windows (Class Library) in my Contracts and Plugin projects.
Following the steps that @pmuessig suggested I was finally able to get the plugin to load. Thank you a lot!
I think it would be worthwhile to add his guide to the documentation somewhere.

为了帮助回到这里的人，我必须执行以下操作才能正常工作：
现在：我有一个 dotnetcore 3.1 LIB 类型： <Project Sdk="Microsoft.NET.Sdk.WindowsDesktop" ... 与<UseWPF>true</UseWPF> 我用这个项目来共同拥有的东西，该插件的依赖。插件可以拥有自己提供的 UI 配置，但拥有它们可以使用的这些通用控件有帮助。
在这个核心项目中，我必须添加以下附加属性
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
    <RestoreProjectStyle>PackageReference</RestoreProjectStyle>

然后我不得不添加一个包引用 <PackageReference Include="Microsoft.Windows.Compatibility" Version="3.1.1" />
这仍然导致一些问题-即无法加载System.Data.Odbc特定的版本注意到我的配置文件中没有为这个DLL生成绑定重定向，因此向项目添加一个app.config中并使用以下内容让我更进一步：
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.Odbc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

这取得了进展，但仍然对导致System.Data.OleDb未出现版本的警告。这个目标明确的人也丢失了，但不管我做什么事手动加载添加它，没有走运，所以我将它添加为包引用：
<PackageReference Include="System.Data.OleDb" Version="4.7.1" />
瞧，它奏效了。
@natemcmaster - 恕我直言，这种饮料很糟糕，我什至不使用任何System.Data.* 库。希望我有一种更简单的方法可以找到没有黑色的 dll-magic 黑客的情况下工作。但至少有一个解决方案
There is no concept of binding redirection in core, so it is invalid to create app.config

To help those coming back here I had to do the following to get it to work:
Situation: I have a dotnetcore 3.1 lib that is of the type: <Project Sdk="Microsoft.NET.Sdk.WindowsDesktop" ...  with <UseWPF>true</UseWPF> I use this project to contain common things that the plugins rely on. The plugins can have UI configuration, which they themselves provide, but having a common set of controls they can use is helpful.
In this core project i had to add the following additional properties
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
    <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects>
    <GenerateBindingRedirectsOutputType>true</GenerateBindingRedirectsOutputType>
    <RestoreProjectStyle>PackageReference</RestoreProjectStyle>

I then had to add a package reference to <PackageReference Include="Microsoft.Windows.Compatibility" Version="3.1.1" />
This still resulted in some issues - namely that a specifc version of System.Data.Odbc could not be loaded. Noticed that there were no binding redirects generated in my config file for this dll, so adding an app.config to the project with the following got me further:
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Data.Odbc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

This made progress, but still resulted in complaints about the right version of System.Data.OleDb not loaded. Noticed this binding redirect was also missing, but no matter what i tried to do to manually add it, no luck, so instead I added it as a package reference:
<PackageReference Include="System.Data.OleDb" Version="4.7.1" />
And voila, it worked.
@natemcmaster - IMHO, this dance sucks, I dont even use any System.Data.* libs. I wish there was an easier way to get this to work without what seems like black dll-magic hackery. But at least there's a workaround

There is no concept of binding redirection in core, so it is invalid to create app.config

I am building with .net 6, creating a simple demonstration of my own with WPF user control plugins.
After getting the Could not load System.Data.SqlClient issue, and finding this thread, I found adding Microsoft.Windows.Compatibility 6.0.0 fixed it, for now.
I did not need anything project settings or config files, or OleDb reference.
I'm still not really understanding the issue, for now.