Document known differences between .NET Framework and .NET Core

I couldn't find any specific documentation about major diferences between .NET Framework and Core, but some of the topics that should be covered:

Replacement for AppDomain's scenario of assembly isolation
Replacement for AppDomain's scenario of remoting

There are probably other topics, but I encountered these two recently and figuring out what should be done to replace it was difficult. Samples for it would be helpful.

I think we talk about these differences on the porting docs but we don't have a top-level topic on these differences: https://docs.microsoft.com/en-us/dotnet/articles/core/porting/libraries

There is also Porting to .NET Core on the .Net Blog, which contains a section on what you should use instead of discontinued technologies like AppDomain.

Moving to backlog for now until we get more clarification on API changes.

@terrajobst @weshaggard would you guys be the right people to talk about this issue?

@jkotas would probably be the best person to talk with on this subject but I don't think we really have any clear cut guidance for replacements in this space.

Remoting: Doc update tracked by https://github.com/dotnet/corefx/issues/18394. The issue has some discussion about the options.
Assembly isolation: AssemblyLoadContext is the replacement. Documentation in https://github.com/dotnet/coreclr/blob/master/Documentation/design-docs/assemblyloadcontext.md. https://blogs.msdn.microsoft.com/dotnet/2016/05/27/making-it-easier-to-port-to-net-core/#comment-77765 and https://github.com/dotnet/coreclr/issues/295#issuecomment-75266259 has some more context.

There is good source material here on the corefx wiki

@terrajobst @weshaggard would you guys be the ones helping with this request?

We do cover higher level differences at https://docs.microsoft.com/en-us/dotnet/standard/choosing-core-framework-server

@sdmaclea it's assigned to you. For milestones, we use specific sprints. I'll add you to the docs-write team, so you can make changes to label/issues as needed.

Will there be a document listing all the changes that have been made in .Net Core but not ported to  .Net Framework for compatibility reasons? If I was even considering doing a port I would want to see that list.
I'm thinking of things like the change to floating point parsing & formatting that was announced today. Without a central list of these things it's down to each developer to search around for blog posts, GitHub issues, etc.
Us NetFX developers are used to having that high AppCompat guarantee, so it's already going to be a jarring experience coming over to corefx's brave new world. The more undocumented "small" gotchas that are waiting for us, the worse it will be.

@swythan
We have https://docs.microsoft.com/dotnet/standard/analyzers/portability-analyzer which will
analyze the actual API usage of your app and generate a portability report for any port target
There is also an interactive list in the https://apisof.net/catalog/ if you want to browse.

Those are for API changes, not behavioural charges.
My issue is that .Net Core is accepting changes that .Net Framework wouldn't because they might break existing code. That's fine, but if I'm porting from one to the other I'd really like to know where I should be testing.

@swythan

Will there be a document listing all the changes that have been made in .Net Core but not ported to .Net Framework for compatibility reasons? If I was even considering doing a port I would want to see that list.

Realistically, no. .NET Core is the future of .NET and as such will be the only thing that gets new capabilities. So it's best to assume that nothing new will be backported.

@swythan

I'd really like to know where I should be testing.

We try to maintain backward compatibility where possible. The changes in the API surface are obviously the primary change.
There are a few APIs which are implemented by throwing PlatformNotSupportException. The https://docs.microsoft.com/en-us/dotnet/standard/analyzers/api-analyzer will help with those.
There are subtle backward compatibility behavioral differences. Most of them are unintentional so generating a list would prove difficult.
One of the areas which might be worth noting is in the area of locating assemblies.  .NET Core does not support a GAC and the loading model is different. Luckily these problems fail dramatically, which simplifies testing.
Certainly all the quirk support has also been removed.
Two of the most painful for customers are mentioned above, (but these are API changes)

Replacement for AppDomain's scenario of assembly isolation
Replacement for AppDomain's scenario of remoting

When porting, a fairly exhaustive test is probably in order.

Realistically, no. .NET Core is the future of .NET and as such will be the only thing that gets new capabilities. So it's best to assume that nothing new will be backported.

I know that nothing else is being back-ported. I accept that.
What I would really like to see is a list of known behavioural differences between .Net Framework and .Net Core.
Here's my approximate position:

Company uses .Net Framework for years. Gets used to the high levels of compatibility between releases and long support cycles.
.Net Core is released but company doesn't adopt it (even for new projects) due to real/perceived issues.
Lots of blog posts about new features, bug fixes & performance improvements in .Net Core.

ALL of them say "We won't be back-porting this to .Net Framework because it would/might break compatibility"

.Net Core 3.0 comes along and .Net 5 is announced. Looks like now might be the time to port stuff over.
I'm now left thinking: " I wonder how many of those fixes that were made actually broke compatibility in a way I'm going to care about?"

I'm thinking of "little stuff" like the double parsing stuff I mentioned above; the recent changes to exception stack trace output (I think); things like that. They aren't going to show up in a compatibility scanner.
Without a central list, everyone that does a port is going to have to work this all out for themselves by digging through release notes and GH issues. I believe there was a presentation at NDC (?) this week where they said (I paraphrase): "The compatibility issues are only going to get worse, so port now."
I personally feel like it is Microsoft's duty to help out with this, if they want developers to get off NetFx.

Unfortunately, it's impossible to document what you are asking for. Even switching your project to use PackageReference can result in semantic differences that are impossible to enumerate. There are some major pieces we document (i.e., no support for Windows Workflow) but every single behavioral difference is not possible. Doubly so if you're running your application on something other than Windows. For example, the networking libraries call into different things based on what platform you're on, leading to performance characteristics that are not identical across OS's. Since these are also moving targets, whatever we exhaustively documented at some point in time are likely to be very different just a few months later. That sort of situation would only make things worse for people looking to move to .NET Core, because then there's incorrect documentation about something.

I seem not to be making my point effectively. @sdmaclea has made me think of a better way of expressing it:

Certainly all the quirk support has also been removed.

Could we have a list of known changes for which .Net Framework would have (probably?) added a Quirk option?
I'm not looking for an exhaustive list of everything that might have a compatibility  effect. I'm looking for a list of changes where the .Net Core team actively chose that a breaking change was OK (e.g. in the interests of the future of the platform).
At the risk of diluting my point (and I don't want to get in a semantic argument), it's not impossible to generate an exhaustive list, just likely to be very expensive. The sort of thing I'm asking for wouldn't be as hard as that, but still might require looking through a lot of history of where these decisions were made. That's probably still expensive, but my employers (and many others) do pay Microsoft tens of thousands a year for developer tools. Normally the documentation is excellent.
Another thought: Does anyone maintain a list of functional differences between different .Net Standard implementations? Is there a compliance test suite? What I'm asking for is similar to that.

Could we have a list of known changes for which .Net Framework would have (probably?) added a Quirk option?

The .NET Framework servicing policy for last number of years has been that any observable behavior change has to be quirked (except for security fixes). .NET Core contains a lot (many hundreds) bug fixes that are observable behavior changes. Most of them would need quirks in .NET Framework. I doubt that a list of many hundreds of subtle differences would be useful to anybody.
We used to run .NET Core corefx tests against .NET Framework and have tests annotated with differences. We have stopped doing that recently since we have maximized what we can bring over from .NET Framework and this coverage was not useful anymore. https://github.com/dotnet/corefx/pull/37972/ is PR that deleted a bulk of this special casing. You can get the idea about the amount and nature of the .NET Core and .NET Framework differences from this PR.
We had other customers asking for a list of changes with high breaking potential. This list should be much smaller and more manageable. It would have changes like the floating point parsing/formatting changes. Note that such list is applicable for both going from .NET Framework to .NET Core, as well as for going from older version of .NET Core to newer version of .NET Core. @swythan Would having list like this address your concern?
CoreCLR repo has a breaking-change label that we use to tag changes with high breaking potential:
https://github.com/dotnet/coreclr/issues?utf8=✓&q=label%3Abreaking-change . It is very low overhead way to track this. However, this convention is not consistently followed across .NET Core repos today - something that would need to be fixed to make this work.

@jkotas

We had other customers asking for a list of changes with high breaking potential. This list should be much smaller and more manageable. It would have changes like the floating point parsing/formatting changes. Note that such list is applicable for both going from .NET Framework to .NET Core, as well as for going from older version of .NET Core to newer version of .NET Core. @swythan Would having list like this address your concern?

Yes, that's exactly what I'm asking for. Thank you. I also agree about it being just as useful when moving between versions of .Net Core.
Given that you think think the list of observable behaviour changes would be hundreds of items long, I can see that such a would probably not be useful enough to justify the expense of creating it. A link to dotnet/corefx#37972 and that breaking change query (or this discussion) might be of help to those that want more detail, perhaps?

a list of changes with high breaking potential

@danmosemsft @karelz Does it sound reasonable to you to use breaking-change label to tag issues and changes with high breaking potential in CoreFX repo? It is in use for CoreCLR repo already. (Or suggest an alternative way how we can keep track of changes with high breaking potential.) Once we agree on the plan, I will update the repo documentation with it.

This is bigger and broader than what I will take on.  I will remove my assignment and open separate issues for the pieces I will tackle.

@danmosemsft @karelz Does it sound reasonable to you to use breaking-change label to tag issues and changes with high breaking potential in CoreFX repo?

Moving forward, I'd say yes. There is another effort right now to formalize our breaking change process between .NET Core versions. I've asked to include .NET Framework as an explicit section in that guidance. While we're not shooting for a 100%, we do try to maintain ABI compat whenever possible. Behavior is much more of a gray area though and tracking that is hard. I'm totally OK with tracking intentional breaking changes.

Yes, labeling sounds like a good idea. @terrajobst do you want to send a mail to corefx users (the area owners alias)?

Closing this issue as it is covered here:
https://docs.microsoft.com/en-us/dotnet/core/porting/net-framework-tech-unavailable
and here:
https://docs.microsoft.com/en-us/dotnet/core/compatibility/

@IEvangelist @gewarren
It's a shame that the breaking-change PR searches that are linked to from the docs added in #18155 don't actually return much useful info. For example, I don't think the floating point parsing/formatting changes change I mentioned above are in that list.

@swythan Are these the changes you are referring to?
https://docs.microsoft.com/en-us/dotnet/core/compatibility/corefx#floating-point-formatting-and-parsing-behavior-changed

@swythan Are these the changes you are referring to?
https://docs.microsoft.com/en-us/dotnet/core/compatibility/corefx#floating-point-formatting-and-parsing-behavior-changed

Yes! Those pages are exactly what I wanted! 🎉🤦🏻♂
In my defence I'm on a phone, so when I followed the link in the comment from @IEvangelist I only saw the guidance page, not all the sub pages with the actual lists of breaking changes. Once I knew the page existed I spotted the Table of Contents button and I'm a happy camper now.
If I was being really picky I'd point out that the NetFX to NetCore page mostly only lists WinForms issues, but most other changes will be covered elsewhere in these pages, though, so that's OK.
Having these lists available will be very useful when porting. Thanks to everyone who worked on them.

@swythan Oh good! Yes, the Framework -> Core page started its life as WinForms only, which is why it seems heavily focused on WinForms. It's only in the last few months we've expanded its scope, and it's a work in progress. We also have the APIs that always throw PNSE on .NET Core documented here: https://docs.microsoft.com/en-us/dotnet/core/compatibility/unsupported-apis


Added generator send method

This PR enables yield keyword to be used in expression and introduces send method to generator in voc.
Some example of things you can do with yield expression and send method:

Echoes what is sent

def gen():
    # echoes what is sent in
    while True:
        x = print((yield))

g = gen()
next(g)
g.send("Hi there!")
g.send("Sup")

Output:
Hi there!
Sup

Yield square of value sent

def gen():
    # yield square of value sent
    while True:
        x = yield("ready")
        yield x ** 2

g = gen()
next(g)
print(g.send(2))
next(g)
print(g.send(-1))

Output:
4
1

Comparing value sent into it

def gen():
    while True:
        x = 1 < (yield) < 5
        print(x)

g = gen()
next(g)
g.send(1)
g.send(3)

Output:
False
True

Note:

Once this PR and #821 are confirmed stable, I will implement the same features to yield from keyword

@freakboy3742 Conflicts resolved as per request :-)


list out loans/holds

added the ability to view loans in https://github.com/albinouty/shibby/pull/12. Will address viewing holds next.


Ability scores not applied to saves.

Con, Dex, and Wis scores weren't applied to saving throws.

Nice catch!


Errors

All I get is errors!
Potentially unhandled rejection [7] SyntaxError: Unexpected token < in JSON at position 0
    at Object.parse (native)
    at Object.eval (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/can-connect-feathers/src/can-connect-feathers.js!eval:155:46)
    at fire (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3187:31)
    at Object.self.fireWith [as rejectWith] (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3317:7)
    at Object.<anonymous> (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3373:41)
    at fire (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3187:31)
    at Object.self.fireWith [as rejectWith] (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3317:7)
    at done (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:8759:14)
    at .<anonymous> (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:9123:9)
    at onload (/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/done-ssr/lib/zones/xhr.js:21:20)
Potentially unhandled rejection [8] SyntaxError: Unexpected token < in JSON at position 0
    at Object.parse (native)
    at Object.eval (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/can-connect-feathers/src/can-connect-feathers.js!eval:155:46)
    at fire (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3187:31)
    at Object.self.fireWith [as rejectWith] (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3317:7)
    at Object.<anonymous> (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3373:41)
    at fire (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3187:31)
    at Object.self.fireWith [as rejectWith] (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:3317:7)
    at done (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:8759:14)
    at .<anonymous> (file:/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/jquery/dist/jquery.js:9123:9)
    at onload (/Users/marcgodard/Desktop/AnywhereGym/AnywhereGym/node_modules/done-ssr/lib/zones/xhr.js:21:20)

Also you should add http://semantic-ui.com/ to the frameworks

Opps Wrong github repo... my bad...


Issue/138/xgal pz tutorial

This PR addresses issue #138, I've updated the tutorial cells based on feedback from two people who I asked to work through the tutorial, and I am now happy with the tutorial.
There is still a sys.path.insert to load the newest version of the reader, but that single cell can be removed once gar-catalogs v0.19.0 is propagated to the desc-python kernel.

Ah, I should have noticed that use_only_master_attr, thanks for pointing this out!
I'll wait until desc-python is updated to v0.19.0, check that everything works, then delete the path before merging just to be sure it all works smoothly.

Ok, I added only_use_master_attr =False in the two locations and removed the local loading of gcr-catalogs, everything works now that desc-python points to v0.19.0.  Everything looks ready to go.


Command 'imap' not found, but there are 15 similar ones.

How should this problem be solved？

do you install the tool? if not you can use below cmd to install
pip3 install imap_box

Yes, I installed the tool
| |
郝璐璐
|
|
@.***
|
---- Replied Message ----
| From | @.> |
| Date | 04/6/2023 17:22 |
| To | @.> |
| Cc | @.> ,
@.> |
| Subject | Re: [daohu527/imap] Command 'imap' not found, but there are 15 similar ones. (Issue #79) |
do you install the tool? if not you can use below cmd to install
pip3 install imap_box
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I don't know why, it looks like you may have installed to the user directory, you can add path use below cmd
export PATH=./.local/bin/:$PATH


the gpu memory is out of, what model are you using?

I'd like to ask a question,The size of the graphics device you are using to run the Clothing1M and WebVision data sets?I reproduced the results and found that the memory required for these two data sets was large

Hi, I'm experimenting with Nvidia 3090Ti.


Remove organisation logos from NFS

See: alphagov/asset-manager#272
Organisation logos are now being saved to, and served from[1], Asset
Manager. Any new logos are not being saved to NFS[2]. Existing logos
have been migrated to Asset Manager[3]. This means we can remove these
assets from the file system.
This PR adds AssetRemover#remove_organisation_logos to remove
the directory that "clean" organisation logos were moved to after
virus scanning, and all of its contents. We also add a Rake task asset_manager:remove_organisation_logos to allow this code to be run via Jenkins.
[1] alphagov/asset-manager#283
[2] alphagov/asset-manager#274
[2] alphagov/asset-manager#276

I've rebased this on master in preparation for merging.


Develop Third Theme (New Visuals)

We can illustrate how easily we can retheme our automotive framework by having several unique looking visual styles.

Give it a name
Create a new visual style using the agate/styles/colors.less and agate/styles/variables.less files
Add it to the skins.less applySkins() mixin
Add it to the agate/Skinnable.js file
Add it to the skin switcher in Agate Storybook

https://github.com/enactjs/agate/pull/65
https://github.com/enactjs/agate-apps/pull/63


Error using in zsh

I get error when trying to use this script using zsh + oh-my-zsh.
Using commit 511ec3d
Ξ external/jenkins git:(master) ▶ gradle --
_gradle:83: parse error near `]]'
_gradle:83: parse error near `]]'
_gradle:83: parse error near `]]'

The lines I added to .zshrc
zstyle ':completion:*' use-cache on
export PATH=".:$PATH"
fpath=(/home/stalle/.zsh/gradle-completion $fpath)

@staffanf Which version of zsh are you using? This sounds similar to #4 where we discovered zsh 5.0.5 has a bug and upgrading fixed the issue.

Built and updated to zsh 5.3.1. Now this bug seems to have gone way....
If I now do gradle [TAB] in a gradle init --type basic dir, I get:
zsh: do you wish to see all 262 possibilities (116 lines)?  where the last 2 lines looks like
'test'.    [incubating]    all       buildscript    components       declared        dependency    files.    help    insight    message.    new    produced    properties    runnable    sub-projects    the
Gradle     a               build.    by             configuration    dependencies    dependent     from      in      into       model       of     project     root          specific    tasks           wrapper

This looks kinda messed up... maybe a separate bug though...

Thanks for the additional report @staffanf. It is captured in #8.


Fix dead code in gdnative_interface.cpp

This pull request fixes dead code found in gdnative_interface.cpp.
This code originally had an assignment operation done after a return statement. This code would never be reached during execution, so this pull request solves that.
Resolves: #50843

Thanks!


Generalize the codebase to run in accountable and non-accountable modes

Currently, the tower runs only in accountable mode, meaning that signatures of agreement are sent by the tower to the users so it can be held accountable in case of misbehaviour.
While this may make sense for towers run by third parties, it may not if the same person is running the tower and the client. Running in accountable mode means having to store the signed receipts by the client, which may not be desirable in this case.
Generalize the tower so it can be run in both modes. This should be configurable via compilation flags so the tower is run in one of the two modes (and advertised to the users during registration).
Further info: https://www.summerofbitcoin.org/project-ideas-details?recordId=recYp3MeVaI79Jocg
DISCLAIMER
This is a Summer Of Bitcoin (SOB) project. If you're considering tackling this but you are not part of SOB, please leave it until SOB is over. After that, feel free to jump in.

I will be working on this for my SOB project, I am asking my doubts on discord as Aditya Gupta.
I have few questions..

So customizing rust-teos to run in non-accountable mode would need me to modify public APIs so that they do not exchange signatures when called and make it such that the client does not store any receipts??
Also what other things need to be modified when running in non-accountable mode??


Added "Badssentials:AOPChange" event that is called for intergration and updated readme for this change.

I needed this to code a script I am working on easier lol.

Also updated gitbook documentation
https://github.com/JaredScar/Badger-Docs-Gitbook/pull/2


HMR does not work for Angular projects, containing lazy loaded modules and the code snippet

Environment
CLI: @rc
To Reproduce
Create Master Detail NG app
Add nativescript-dev-webpackа@next
Add nativescript-angular@next
Add the code snippet from: https://github.com/NativeScript/nativescript-angular/wiki/HMR in main.ts file
Deploy on device.
Expected behavior
App should refresh the changes.
Actual behavior
The app is restating and there are info messages in the Console.
Additional context
Related to https://github.com/NativeScript/NativeScript/issues/6398

Thanks to @vakrilov, we found some manual steps that looks like are valid workaround:

To every lazy loaded NgModule that you want to be hot module replaced add the following snippet:

// imports ...

if (module['hot']) {
    module['hot'].accept();
}

@NgModule({
    imports: [

Register onBeforeLivesync and onAfterLivesync callbacks to preserve the URL you are app is navigate to as per this Gist:

livesync-navigation.ts
import { Router } from "@angular/router";
import { onBeforeLivesync, onAfterLivesync } from "nativescript-angular/platform-common";
import { RouterExtensions } from "nativescript-angular/router";
import { NgZone } from "@angular/core";
 let cachedUrl: string;
onBeforeLivesync.subscribe(moduleRef => {
    console.log("#### onBeforeLivesync");
    if (moduleRef) {
        const router = <Router>moduleRef.injector.get(Router);
        cachedUrl = router.url;
        console.log("-------> Caching URL: " + cachedUrl);
    }
});
 onAfterLivesync.subscribe(({ moduleRef, error }) => {
    console.log(`#### onAfterLivesync moduleRef: ${moduleRef} error: ${error}`);
    if (moduleRef) {
        const router = <RouterExtensions>moduleRef.injector.get(RouterExtensions);
        const ngZone = <NgZone>moduleRef.injector.get(NgZone);
        if (router && cachedUrl) {
          ngZone.run(() => { // <--  should be wrapped in ngZone
            router.navigateByUrl(cachedUrl, { animated: false });
          });
        }
    }
});

Import the livesync-navigation to your main module (main.ts)

I've followed all the instructions but now I'm getting a new error:
Module not found: Error: Can't resolve 'css-loader' in '/Applications/MAMP/htdocs/MyApp/app'
 @ ../node_modules/nativescript-dev-webpack/load-application-css-angular.js 5:49-65
 @ ./main.ts```

This issue should be fixed with https://github.com/NativeScript/nativescript-dev-webpack/commit/6a9db32b9ef0205194d017f1803d2a5c6d21b4b8.
The fix will be part of the 0.19.0 release of nativescript-dev-webpack.

Still an issue: HMR does not work if any router resolve involved.


added funded mobile scenario

Codecov Report
Patch and project coverage have no change.

Comparison is base (a1941ab) 59.74% compared to head (cd94a49) 59.74%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##              dev     #419   +/-   ##
=======================================
  Coverage   59.74%   59.74%
=======================================
  Files          34       34
  Lines        5227     5227
=======================================
  Hits         3123     3123
  Misses       2104     2104

Impacted Files
Coverage Δ

zingo-testutils/src/lib.rs
79.42% <ø> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


English grammar fix

fixes old pull 2736

Thanks, please sign off the commit with your real name.

🌊

Finally, you did it ... :thumbsup:
Many thanks!


Update el.coffee

few additions and small corrections in leaderboard section for better displaying

Awesome job, @micman73! Thanks


Policy as code support

Do you have any plans to develop for 1st class support for Policy as Code in BICEP?
Right now, the suggested approach is to create the initiatives and polices in JSON as described here
It would be incredible to be able to specify, create and modify an entire governance structure using BICEP to describe

Management Groups
Initiatives
Policy definitions
Policy assignments

...drawing on modules for re-use, along with what-if deployments. This could be a game-changer for policy as code!

@eladperets thoughts?

A couple of thoughts:

All of the above is possible in bicep. MGs, Policy assignment, and initiative assignment should all be fairly straightforward. Examples:

Policy definition and assignment
Initiative definition and assignment
I don't have one handy for MGs in bicep, but here is one for ARM templates that can be decompiled.

While policy and initiative definition are both possible, it's not as easy because you need to handle functions that pertain to both the ARM Deployments runtime (bicep) and the policy runtime. So you end up with bicep code like this. This is where I think we have the most opportunity for improvement.

There have been discussions on whether (and how) we should integrate policy with bicep , but I'm not aware of any concrete plans. @LizMS probably knows best.

Hi @cloudfright, the Policy team is investigating integrating policy with bicep. As of right now, we do not have any ETAs or projections on if we are going to commit to bicep or another language in adjacent to JSON. We will have more updates Fall 2021.  Thanks.

Related to this, at the very least it'd be nice if bicep extension intellisensed the parameters from the policy definition API based on the policydefinitionId specified so they don't have to be manually looked up and typed leading to lots of manual errors.


Mypy issues part 3

More miscellaenous mypy fixes.

Looks like a legitimate conflict with #867 -- which was just merged.


Google Calendar search missing items, possibly because of special characters

Home Assistant release with the issue: 0.87

Operating environment (Hass.io/Docker/Windows/etc.): Linux (Archlinux)

Component/platform: calendar.google

Description of problem:
Using "Groente, fruit- en tuinafval" in a search does not return the calendar items that include "Groente, fruit- en tuinafval". If I search for "Groente" it does. Possibly it does not like the comma or minus sign?
Problem-relevant google_calendar.yaml entries and:
- cal_id<EMAIL_ADDRESS>  entities:
  - device_id: container
    ignore_availability: true
    name: Afvalkalender RMN
    track: true
  - device_id: container_brown
    ignore_availability: true
    name: Groente, Fruit- en Tuinafval
    search: "Groente"
    track: true
  - device_id: container_gray
    ignore_availability: true
    name: Plastic, Metaal en Drankkartons
    search: "PMD"
    track: true
  - device_id: container_green
    ignore_availability: true
    name: Restafval
    search: "Restafval"
    track: true
  - device_id: container_blue
    ignore_availability: true
    name: Papier en Karton
    search: "Papier en karton"
    track: true

CC @mnestor @happyleavesaoc @scop

This is limitation of the Google app. We can't do complex search strings here.

Thanks @mnestor.  Closing the issue.


Fix typo in dependency-injection.md

The sentence:

...let's consider you have different implementation of the interface...

Should read:

...let's consider you have different implementations of the interface...

However, beyond the small typo, I think this version is slightly easier to read, so that's what I ended up with:

...let's consider the case where you have different implementations of the interface...

Internal previews

📄 File
🔗 Preview link

docs/core/extensions/dependency-injection.md
.NET dependency injection

Thanks @IEvangelist for following up as always 🙏


Allow for bulk connect on Seq?

In chisel2 I was able to create a Vec of nodes and bulk connect them to another Vec of the same type as follows
  val issue = Vec(io.abox(0), io.pbox(0),
    agent.io.span(io.abox(1), io.pbox(1)), io.abox(2))
  issue <> agent.io.issue

In order to use chisel3 this is transformed to
  val issue = Seq(io.abox(0), io.pbox(0),
    agent.io.span(io.abox(1), io.pbox(1)), io.abox(2))
  issue zip agent.io.issue map {case(s,d) => s := d}

The issue Vec/Seq in this case will not be dynamically indexed itself but the agent.io.issue Vec will be, so it seemed reasonable to match the types for the previous <> usage.
Is this transformation the only way chisel3 will support this operation?

We'd have to add an implicit conversion from Seq to a new type that has :=
and performs the same map.  But it is possible.
On Wed, Apr 20, 2016 at 7:32 PM, Colin Schmidt<EMAIL_ADDRESS>wrote:

In chisel2 I was able to create a Vec of nodes and bulk connect them to
another Vec of the same type as follows
val issue = Vec(io.abox(0), io.pbox(0),
agent.io.span(io.abox(1), io.pbox(1)), io.abox(2))
issue <> agent.io.issue
In order to use chisel3 this is transformed to
val issue = Seq(io.abox(0), io.pbox(0),
agent.io.span(io.abox(1), io.pbox(1)), io.abox(2))
issue zip agent.io.issue map {case(s,d) => s := d}
The issue Vec/Seq in this case will not be dynamically indexed itself but
the agent.io.issue Vec will be, so it seemed reasonable to match the types
for the previous <> usage.
Is this transformation the only way chisel3 will support this operation?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ucb-bar/chisel3/issues/152

You can also do:
for((i, a) <- issue zip agent.io.issue) { i <> a }

Resolution: we should do this.

Does this work yet?

Why would it work know without anyone submitting a PR against this issue?

Well, this issue exists: https://github.com/freechipsproject/chisel3/issues/482

It looks like the issue is connecting to Seq as the lhs value which does require an implicit conversion as Andrew proposed

Discussed at the dev meeting today:

apparently there is already support for Seq as the RHS of a connect
so the work left is supporting Seq as the LHS of a connect
some kind of implicit conversion would be required - whether a fully general Seq -> Vec conversion (and analysis of potential side effects) or a limited Seq -> LhsConnectable (or something similar that only provides the limited connect APIs) would be a point for discussion
potentially a good starter issue, though limitations of implicits might make things interesting

Done in 3.5.0 via DataView and experimental import:
import chisel3._
import chisel3.experimental.conversions._

class SeqExample extends RawModule {
  val a, b = IO(Input(UInt(8.W)))
  val x, y = IO(Output(UInt(8.W)))
  Seq(x, y) := Seq(a, b)
}

println(getVerilogString(new SeqExample))

https://scastie.scala-lang.org/17fTL4WKTYOvPioFO6VOGA


OCPBUGS-15067: Bump helm to v3.8.2

/retest

closing in favor of https://github.com/openshift/operator-framework-olm/pull/528


Fix a hyperlink in comment

Fix hyperlink of "Use cookie authentication without ASP.NET Core Identity"

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

File
Status
Preview URL
Details

aspnet-core/xml/ns-Microsoft.AspNetCore.Authentication.Cookies.xml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

per the readme:
API PR's ( api/autoapi/... ) should not be made here. Changes to API documentation should be made in the source repository against the triple slash /// comments.


Setup php-cs-fixer (@PSR2 rules only); Enable running in CI

Split off from https://github.com/mrclay/minify/pull/659: It was too aggressive changes, no real explanation why the rule should be enabled, so decided to enable only PSR-2

Works as expected (including allowed failures):

https://travis-ci.org/github/mrclay/minify/builds/670460226


fix: 🐛 Copy output of unsupported images

Description
For images with extensions that do not support optimization, a simple copy is applied.
This is to be similar to the image optimization process in Next.js.
Fixes #82
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings

🎉 This pull request is included in version v1.5.1.


Make robust against field removal in grpc protocol

(These are mostly notes to self, for anyone wondering why I'm being so long-winded about this...)
Several times in the past, SpaceX has removed fields from the dish's grpc protocol that the scripts in this project were using, resulting in a script crash on attempt to read any data from the same category (status, history stats, bulk history, or location). While loss of that data is unavoidable unless it can be reconstructed from some other field, it would be much better if it didn't cause a crash. I mentioned in issue #65 that I would put some thought into how to accomplish that. After all, one of the intentions of the core module (starlink_grpc.py) is to insulate the calling scripts from the details of the grpc protocol, even though it's mostly just passing the data along as-is in dictionary form instead of protobuf structure.
The problem here is a result of using grpc reflection to pull the protobuf message structure definitions instead of pre-compiling them using protoc and delivering them along with this project. It's pretty clear from the protobuf documentation that the intended usage is to pre-compile the protocol definitions, but there's a specific reason why I don't do it that way: SpaceX has not published those protocol definitions other than by leaving the reflection service enabled, and thus have not published them under a license that would allow for redistribution without violating copyright. Whether or not they care is a different story, but I'd prefer not to get their legal team thinking about why reflection is even enabled.
Before I built use of reflection into the scripts (by way of yagrc), I avoided the copyright question by making users generate the protocol modules themselves. This complicated installation, caused some other problems, and ultimately didn't actually fix this problem, it just moved it earlier, since it was still just getting the protocol definitions via reflection.
So, other than use of pre-compiled protocol definitions, I can think of 2 main options:

Wrap all (or at least most) access to message structure attributes inside a try clause that catches AttributeError or otherwise access them in a way that won't break if the attribute doesn't exist. This could get messy fast, since I don't want a single missing attribute to cause total failure, but would probably be manageable. It also really fights against the design intent of how rigidly these structures are defined by the protoc compiler, but I find myself not really caring about that, as it's exactly this rigidity that is causing the problem here.

Stop using the protocol message structures entirely and switch to pulling fields by protobuf ID instead. This would make the guts of the code less readable, but would insolate this project against the possibility that SpaceX ever decides to disable the reflection service. I have no reason to believe they would do so, but I also have little reason to believe they wouldn't. I'm not sure how difficult this would be, though, as the low-level protobuf Python module is not meant to be used in this way, as far as I can tell. Also, this would still cause problems if SpaceX were to reuse field IDs from obsoleted fields that have been removed, but they haven't been doing that (and it's bad practice in general, as it can break their own client software), as far as I can tell. If I were writing this from scratch, knowing what I do now, I would probably try to do it this way.

However it's done, I should note that this will make obsoleted fields less obvious. The removed data will just stop being reported by the tools. I have been using these failures as an opportunity to update the documentation on which items are obsolete, but I suspect this will still get noticed, and I'd rather have the documentation lag behind a bit than have the scripts break.

Before I forget again:
I did look into option 2 noted above, and just as I have the last several times I looked into such, I concluded that it'd be technically possible, but not worth it at this point. As far as I can tell, there is code that could be called for serializing and deserializing raw protobuf messages, but it is in an internal package, so directly using it would be subject to breakage as that package gets updated. On top of that, that is in the pure Python implementation, so using it would mean losing the performance benefit of the native code versions. As an alternative, it should be possible to build descriptors for the messages dynamically, and then just run those through the same process as yagrc uses to create the message classes. There's another problem here, though: there are a couple cases where the strings used for some fields are taken from the reflected protocol data, because SpaceX periodically adds things, and I really don't want to go back to having to update the starlink_grpc module to support every new new alert type or outage reason.
Meanwhile, I believe option 1 will not be so messy as I was thinking, so I guess I'll just stop whining about it and go with that option.

Those changes should be sufficient for anything that uses the core module (starlink_grpc).
The only significant script that does not use that module is dish_control.py. I may switch that over to use the core module now that it actually has some (minimal) value add for those grpc requests, but if the protocol changes on them, the related functionality is just going to stop working, anyway.


Chrome Web Store Version “not found”

Are you experiencing an issue with...
shields.io
🐞 Description
Chrome version “not found”：

This extension exists in the web store as normal:
https://chromewebstore.google.com/detail/ikhdkkncnoglghljlkmcimlnlhkeamad
🔗 Link to the badge
https://img.shields.io/chrome-web-store/v/ikhdkkncnoglghljlkmcimlnlhkeamad
💡 Possible Solution
No response

This is now happening on all my chrome extensions.

This one relies on a library. I've raised an issue upstream https://github.com/awesome-webextension/webextension-store-meta/issues/7

Chrome changed the URL's from chrome.google.com to chromewebstore.google.com, probably related.

fix for this is deployed - might take a few mins for old badges to drop out of cache


README.md: update version and fix a typo

Hello, the README is behind by a lot more than just the version. A lot of changes happened in the project since then. We are going to address that by the end of this week as the project will be ready to be released to early adopters later today. I'm closing this PR as it will be superseded by a thorough rework of the README.
Thank you for your interest and the heads up nonetheless, and stay tuned!


brew: fix typo in task name

@jazzdan are you in the Discord? If so what's your username, so I can add the contributor role?

Hi @elviskahoro, my discord user name is null#0252. Thanks! :)


Multiple startup projects add-migration command error

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

When I have Multiple startup projects set up and if I run add-migration command it gives below error
No database provider has been configured for this DbContext
But if I set to single startup project this does not occur

Original Comments
Visual Studio Feedback System on 11/10/2019, 11:32 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
BTW we're not just doing this to be mean :smile:... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.
For a guide on submitting good bug reports, read Painless Bug Tracking.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

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


Remove assert statements from Wagtail API

This PR fixes #4186:

There's a few places in Wagtail API where we used assert statements to check parameters. These statements are removed when Python optimisations are enabled so we should replace these.

This PR is best reviewed commit by commit. The asserts have been removed and tests have been added for the filters which have been changed.

The tests are failing due to missing pages on the CircleCI tests. In the screenshot below I'm printing the result from Page.objects.all():

On my dev env two pages are present:

What is the correct solution to make those pages available in the test on CircleCI? I could create the pages in setUp() when the pages are not present. But this doesn't seem like a proper solution.

Thanks! The removal of the assert statements look good to me!
I'm not sure what the benefit of unit testing those classes is, they don't seem to be specifically checking for any issue that would be caused by the assert statements and all of this code is already covered by the functional tests.
When I developed the Wagtail API, I aimed to create a very comprehensive set of functional tests and avoided unit testing the internal implementation (except for parts where it really makes sense to do so such as parsing the syntax of the fields parameter) which makes refactoring the internal code much easier.

I'm not sure what the benefit of unit testing those classes is, they don't seem to be specifically checking for any issue that would be caused by the assert statements and all of this code is already covered by the functional tests.

I've removed the tests from this branch, I agree that the usefulness of these tests is questionable.

Thanks!


(GH-323) Update the readme with gifs

This PR adds new gifs for each feature listed in the readme. It removes the large all-in-one gif from the readme, as it's replaced by the smaller and more targeted gifs. It also moves the debugger gif to after the description so its before configuration detail, which was also bulleted for easier reading.
NOTE The relative links need to be changed before this is MERGED!

@michaeltlombardi @glennsarti please review with commit as-is. I will update the links after review, but they are relative links right now so you can view in github

Links updated for final release. Pls merge @michaeltlombardi


unar: init at 1.10.1

Motivation for this change
https://github.com/NixOS/nixpkgs/issues/16868
Thanks to @matthewbauer for https://github.com/NixOS/nixpkgs/pull/16762
Things done

[X] Tested using sandboxing
(nix.useChroot on NixOS,
or option build-use-chroot in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[X] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

Almost forgot to mention I've omitted zlib, OpenSSL and ICU that were mentioned in https://unarchiver.c3.cx/commandline since I'm only interested in the .rar extraction facilities as requested in https://github.com/NixOS/nixpkgs/issues/16868.

Thanks!


IA recommendation refinement

User story
As a user, I want the ReportStream website to match my mental model.
Background & context
We don't know if the site is structured in a way that allows users to find what they need and complete the task at hand. We don't have a scalable framework for launching and housing new features. After coming up with a main research synthesis, we need to refine category names and category items based on those research results to help with navigation development.
Open questions
Working links
Mural
Acceptance criteria

[ ] Category names and items drafted and shared with WebX design

@audreykwr How is this work different from the IA summary deck you shared in the design channel?

That was focused on research synthesis, this is getting into application. As nav design work begins, this is to hone actual category/section names and refine what it is them since the synthesis only included the cards from the sort as the sources. Let me know if I can explain more. This is referenced in the slide slide of the summary deck as well.

@audreykwr ok that helps. Can you include a more defined AC? I think that's what threw me off. It doesn't sound like the AC here is a summary, but rather the actual category/section names.

updated to be more specific! Let me know what else I can do to make this clearer

Application notes added to this deck
Site map rec in this sheet


WSL support?

On Debian / WSL2 I get
$ curl -Ls https://solugo.github.io/gitversion/run.sh | bash
Architecture unknown is not supported

Wsl is reporting the "unknown" architecture. I changed the way it is resolved.
Could you please confirm, that it is working now?


How to change the default timeout in generated client

Problem Statement
So when generating a client, as shown here the default client timeout is set to cr.DefaultTimeout which is 30 seconds.
So what would be the easiest solution to change that default timeout for all my requests, for example if I want to change that default to 5 seconds.
Of course I can change the timeout for each request by using WithTimeout constructor or SetTimeout method but what I want is to change the default, so I don't have to manually change it for each request.
Possible Solution That Could Be Implemented
If this is not possible currently (did not find anything in the docs), a possible solution would to allow the user to set the default timeout with a CLI argument that the user optionally sets when generating a client.
For example:
swagger generate client --default-timeout-seconds=5 ...

And then in the params structs we see:
func NewAddOneParams() *AddOneParams {
	return &AddOneParams{
		timeout: 5 * time.Second,
	}
}

Environment
swagger version: 0.26.1
go version: 1.16.2
OS: macOS 10.15.7

Pass a context with a deadline

@casualjim Thanks for your swift response, but would not that be very similar? I would have to worry what the default timeout is at the code using the generated client and not well defined in the generated client.
Passing a context with deadline is pretty similar to calling WithTimeout constructor. I'll have to set it every time I call the request and for all requests. But instead I wanted to just have the client generated code deal with the default timeout without having to worry about it every time I need to use the generated client, exactly the same as we have now but with the possibility to use a default timeout other than the 30 seconds one.
A semi solution that I can see is to implement ClientTransport interface but that is not perfect as well and have many drawbacks:

Using default constructor would use the 30 seconds timeout and not the one we want, other that we would have two timeouts which would be confusing.
If we want to use the structs directly we would have to assume that if the timeout is not set then we use the default which means we would loose the option to set no timeout.

What do you think? Am I missing something?

Default timeout is fixed. You either need to pass ctx or use withtimeout(). You can try implement the interface.

You can also change the value of the global default timeout, it's an exported var: https://github.com/go-openapi/runtime/blob/master/client/runtime.go#L216
There are constructor methods for per client override too.
https://github.com/go-swagger/go-swagger/blob/master/examples/todo-list/client/todos/add_one_parameters.go#L33-L47

Changing the global variable affects all the generated clients in case you have more than one, as this variable is commonly used in all generated clients. So you will not have the flexibility to set a different timeout for each client. In addition, it can affect other places that uses that variable.
As for the constructor, as I mentioned in the description, we will have to set it every time, and we will have to define what the default timeout is at the code using the client and not at the client itself.
Anyways, this is not a blocker for me and should not be a blocker for anyone, but would be nice to have.


Update docs for cython magic

Merge docs from https://ipython.org/ipython-doc/2/config/extensions/cythonmagic.html with docs from IpythonMagic.py
Not sure if I got the RST formatting quite right....

Thanks. The file you edited is in the "quickstart" folder, so I'd rather not fill it up with lengthy command line parameters. Could you move this list over to the reference/compilation.rst and just link to it? Would be good to have a Jupyter section in there anyway.

Superseded by #2178.


EBIT wrongly returns Opreating Income for (quaterly) financials

import yfinance as yf
msft = yf.Ticker('msft')
msft.financials.iloc[:, 0]

Under 'Ebit', the value is wrong. In fact, it seems to be returning Opreating Income instead. Same issue for both quarterly and yearly.
Running latest 0.1.77, same issue exist in 0.1.75 which means is a long-term bug. Tested with INTC as well.
https://finance.yahoo.com/quote/MSFT/financials?p=MSFT

Have you searched through existing issues? It likely already exists

Yes, found 7 open issues, none had a proper solution, its all workarounds. I already have a workaround, but I would still like to report this because this is clearly a bug with the library.

We haven't forgotten about those 7 issues, so please don't duplicate. Just comment on those threads.


Source map failed warning issue

WARNING in ./node_modules/face-api.js/build/es6/tinyYolov2/leaky.js
Module Warning (from ./node_modules/source-map-loader/dist/cjs.js):
Failed to parse source map from '.\node_modules\face-api.js\src\tinyYolov2\leaky.ts' file: Error: ENOENT: no such file or directory, open 'D:\Security\DigiSchedulerWebApp\node_modules\face-api.js\src\tinyYolov2\leaky.ts'
actually file is not in this location " 'D:\Projects\node_modules\face-api.js\src\tinyYolov2\leaky.ts'" in node module. those files present in " 'D:\Projects\node_modules\face-api.js\build\es6\tinyYolov2\leaky.d.ts'"
how to make this to locate correct location?
This is the issue after upgrading face-api. How to resolve it?

how to avoid this warning in terminal.


Added serialize functions for common Unity types.

For everyone who uses Lidgren with Unity this might be useful.
You can now simply write your Vector3, Quaternion etc. directly
to the Lidgren Netbuffer by calling (for example):
NetBuffer.Write(new Vector3(1.0f, 1.0f, 1.0f));

How about creating a new project called Lidgren.Unity project in the same solution and put all Unity related code in there? Since this is only one file it doesn't really matter but if we get more Unity specific code this might be a better approach than to add all files directly to the main Lidgren project.

Hi! Thanks for the code; I changed it slightly since the NetBuffer is already a partial class, it makes sense to just incorporate them there. Let's add a special project when we get enough files to warrant it.

Cool! Thanks for accepting :)

Thanks again for the code... I don't use Unity so it's all untested (even uncompiled!) from my side; please sync and verify I didn't leave any compile errors in there...


Add AppVeyor CI config

supersedes #2707
Addition of a config file to build successful with AppVeyor CI.
This is not meant as a replacement of the current build server, TeamCity CI.
Building with AppVeyor, next to TeamCity gives the following benefits:

In a PR it's clear if the submitted code compiles and won't break any unit tests
The build and test status is clear en public visible
It looks professional IMO ;)

downsides:

None

Example output:
https://ci.appveyor.com/project/304NotModified/nugetgallery/build/1.0.6
This PR only creates a config file. To add the AppVeyor webhook to GitHub, AppVeyor should be integrated to this repository. This can be done by the following (simple) steps:

Sign in to AppVeyor (https://ci.appveyor.com)
Click button "new project"
GitHub / select repository, click "add"
Click button "new build"
Build
Add AppVeyor webhook (should be automatically added? But failed last time to me)
(optional) Add badge with build/test status :)

Hi @304NotModified, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, DNFBOT;

@maartenba
Is it a possibility to enable the web hook as described above? (the steps)
Because in https://github.com/NuGet/NuGetGallery/pull/2716 I failed an unit test, and that is currently not clear.
See: https://ci.appveyor.com/project/304NotModified/nugetgallery/build/1.0.13

Would prefer to have an AppVeyor account under the NuGet name. Let me check and see what we can do.
@yishaigalatzer Okay if we create an official NuGet Gallery AppVeyor build so that we can report build status publicly?

I’m ok with it, the priority for this is very low.
From: Maarten Balliauw<EMAIL_ADDRESS>Sent: Sunday, October 4, 2015 11:31 PM
To: NuGet/NuGetGallery<EMAIL_ADDRESS>Cc: Yishai Galatzer<EMAIL_ADDRESS>Subject: Re: [NuGetGallery] Add AppVeyor CI config (#2715)
Would prefer to have an AppVeyor account under the NuGet name. Let me check and see what we can do.
@yishaigalatzerhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fyishaigalatzer&data=01|01|yigalatz%40microsoft.com|fb8f07f2b54c4f3c3fdd08d2cd4e7829|72f988bf86f141af91ab2d7cd011db47|1&sdata=akXdS232cD3k5o7%2BAJokKyZg3RN8K%2FG3u0Hu3jSgPbM%3D Okay if we create an official NuGet Gallery AppVeyor build so that we can report build status publicly?
—
Reply to this email directly or view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNuGet%2FNuGetGallery%2Fpull%2F2715%23issuecomment-145442323&data=01|01|yigalatz%40microsoft.com|fb8f07f2b54c4f3c3fdd08d2cd4e7829|72f988bf86f141af91ab2d7cd011db47|1&sdata=ASgC2YgTV76vxqfqCYsnzzDagAHRYm3c29mEvzJLmqA%3D.

Made a few changes to appveyor.yml and added build badge to README.

Nice! I'm pretty sure you guys will benefit from this feature :)

The webhook to our build is also active - check the README for build badge :)

Hey @maartenba ,
I saw the build badge :)
But the web hook isn't working? I don't see it in the PR, see https://github.com/NuGet/NuGetGallery/pull/2723
We need to see something like this:

We have successfully configured it like this:

@csharpfritz can you check if the hook on the gallery fired successfully?

Hook has been updated.

Strange that it still doesn't work :(
see https://github.com/NuGet/NuGetGallery/pull/2728

Does AppVeyor need anything special to enable status reporting to GitHub? I suspect that is what is missing here.

Only the web hook AFAIK.

Will check with them.

You need to disable this:

I enabled it on NLog, and then also the webhooks were not working.

@csharpfritz Can you edit the above for the gallery GitHub repo? It's an organization setting it seems.

There are no restrictions today -
for any required changes in policies of the github site, please work with me.

There are no restrictions today -
for any required changes in policies of the github site, please work with me.

I don't understand what you mean with this.
Anyway, to make it more clear I have the following questions

Is it clear what isn't working?
Do you know how to test it?
Any idea how to fix it?

Working on it :)

:+1:


Updated docs

I updated the docs so they describe how to send a push message. I was fooled by the previous example that sent a data push message, as my app wasn't tailored to accept that.
I believe these new examples will provide an easier onboarding to new users.

Ping @spacialdb this would be great to merge in.


[Question] ImportError: No module named elasticsearch

Recently I was learning how to connect Storm with Elasticsearch. In storm bolt I import elasticsearch module, which could be imported correctly in other python projects, however failed to import when I executed pyleus build command, with a error hint below:

How should I solve this problem?

Oops, requirements file is needed..


sealed secrets update

Updating Sealed Secrets to use the upstream YAML. This saves from having to duplicate the same YAML. This is pinned to version 0.16.0 currently. Also, the need to set "anyuid" has been removed.

/assign @pittar

LGTM.  Thanks!


Why is App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService triggering even when console report is off?

Asp.net core 2.0 project: it is my understanding that unless you add the console reporter
App.Metrics.Reporting.Console
there would be no background process running, however I just turned on tracing to debug a separate issue and my trace log started getting hammered with this:

2018-05-02 08:06:29.9057|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:30.4074|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:30.9221|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:31.4356|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:31.9377|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:32.4403|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:32.9568|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:33.4588|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000
2018-05-02 08:06:33.9671|TRACE|App.Metrics.AspNetCore.Reporting.ReportSchedulerHostedService|Delaying for 00:00:00.5000000

I did try out the console reporter as per the example earlier but then removed that assembly from my project file and also removed the line of code calling it in Program.cs so I didn't expect to see this at all.
The docs seem to indicate that there is no background process running with the sole exception of the console reporter and it's up to us to trigger reporting so this code should not be running as far as I can tell.
What is happening here and how do I stop it?

Are you able to debug the AspNet Core project to confirm? See https://github.com/AppMetrics/AspNetCore/blob/4199a4cc89d26e778869d6199b6e678982a7b279/src/App.Metrics.AspNetCore.Reporting/ReportSchedulerHostedService.cs#L75

I'm not sure I understand; what would you like confirmed?

Try switching off reporting in your appsetting.json
{
  "MetricsOptions": {
    "ReportingEnabled": false
  }
}

Will this setting interfere with reporting to InfluxDB?

Yes that flag will disable reporting altogether.
Why not use your own configuration settings? e.g.
            return WebHost.CreateDefaultBuilder(args)
                          .ConfigureMetricsWithDefaults(
                              builder =>
                              {
                                  if (configuration.GetValue<bool>("EnableConsoleReporting")
                                  {
                                      builder.Report.ToConsole();
                                  }

                                  builder.Report.ToInfluxDb(influxOptions);
                              })
                          .UseMetrics()
                          .UseSerilog()
                          .UseStartup<Startup>()
                          .Build();

Thank you, this information helped.


SWAP-1186 Factory tests

Description

Motivation and Context

How Has This Been Tested

Fixes

Changes

Tests included/Docs Updated?

[ ] I have added tests to cover my changes.
[ ] All relevant doc has been updated

Comes after https://github.com/UserOfficeProject/user-office-factory/pull/1 , adds unit test for testing generated PDF content


Please included Source Sans Pro

Source Sans Pro is another good font to include.

Sure, could you wrap it in a pull request? Please include the license as well.

Okay. I made a pull request.


Add command to create a junction (mklink)

link to create a junction from modFolder to starbound/mod
unlink to remove junction
debug as chained command

link
run starbound and wait for starbound to be closed
unlink

as a hint for myself: mklink will need admin rights on windows, not sure how this is handled in unix.


Fix return for format API

Apologies the changes merged yesterday didn't actually return the formatted string. Had the fix locally but forgot to push up.

No worries! Just saw it myself as I tried to use one of my macros. Managed to fix it before seeing this PR, so fixed in https://github.com/chhoumann/quickadd/commit/b6a4d05666b70438c76b83a2489e4605803b4c59 and released in https://github.com/chhoumann/quickadd/releases/tag/0.11.9
Thanks though!
I should have been more aware when merging yesterday. Was too excited by the prospect, haha.


Very long loop while parsing in MachOFile::parse

Hello, while fuzzing I found a binary file (probably ill-formed) that takes around 10 minutes to be parsed on my machine. But the file is only 396 bytes. This might not be a bug and just an expected outcome of the binary lying about its data, but it would be nice if this can be avoided.
What I've discovered if this can help is that this while loop in MachOFile::parse is looping all the time over commands.next()
https://github.com/gimli-rs/object/blob/a3706b514992d8292b799ae67652096aa0085ca3/src/read/macho/file.rs#L58-L69
And the next implementation of LoadCommandIterator is decrementing its inner variable ncmds by 1 each iteration and returning None when it's 0. But the thing is the initial value of ncmds is 3 992 977 412 😮
Here is the file to reproduce: test.zip

Thanks very much for the report. That test file also uncovered a couple more bugs, all fixed in #516.


Tom/autogmm joss

add joss material to my fork for submission

I think it may not be worth working on such a large merge for what we want to do which is just find a home for the JOSS paper


Disable ACL or Auth using docker

Situation
This plugin manage both ACL and Authentication through http. One can be deactivated by commenting the unused options in the config file. However using emqx in docker (https://github.com/emqx/emqx-rel/tree/master/deploy/docker), the configuration are set from environment variables with no possibility to comment unused config.
Possible solution
Changing the way docker is setting variables to add a way to comment lines looks overkill and not the proper solution. (This is done here: https://github.com/emqx/emqx-rel/blob/master/deploy/docker/docker-entrypoint.sh#L122).
What do you think about having new variables to enable ACL and auth with a default value equals true? Something like this:

auth.http.auth_enabled = true
auth.http.acl_enabled = true

Actually I'm wrong, this is working fine when passing an empty string for the environment variables such as

EMQX_AUTH__HTTP__SUPER_REQ=
EMQX_AUTH__HTTP__SUPER_REQ__METHOD=
EMQX_AUTH__HTTP__SUPER_REQ__PARAMS=
EMQX_AUTH__HTTP__ACL_REQ=
EMQX_AUTH__HTTP__ACL_REQ__METHOD=
EMQX_AUTH__HTTP__ACL_REQ__PARAMS=

Thanks to this line: https://github.com/emqx/emqx-rel/blob/master/deploy/docker/docker-entrypoint.sh#L137.
Maybe I've missed something in the documentation otherwise I'm happy to create a PR to add some docs about how to comment a variable line in here: https://github.com/emqx/emqx-rel/tree/master/deploy/docker. If yes let me know where I can find 'how to contribute' for this repo.

Hi @dufourc Thank you for carefully verifying this content.  'How to Contribute' document in preparation...
btw, after v4.2.0, All you have to do is comment these lines:

EMQX_AUTH__HTTP__SUPER_REQ=
EMQX_AUTH__HTTP__ACL_REQ=

Thanks @HJianBo !


Support searching by XPath

As the title says, allow easy searching by XPath.

I started working on this. I am currently implementing my own XPathNavigator which internally uses the treewalker.

It's basically implemented. Need to do some more tests before I release it. You can use FindFirstByXPath and FindAllByXPath on any AutomationElement.

Released with newest version (1.0.0-beta1).


[feature] Add allowMultiQueries Option to MySqlConnectionConfiguration

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
It is currently not possible to use the allowMultiQueries option in MySqlConnectionConfiguration.
Describe the solution you'd like
Please add an option to specify allowMultiQueries in ConnectionFactoryOptions or MySqlConnectionConfiguration.
Additional context
Add any other context or screenshots about the feature request here.
Code Example:
            val connectionFactory =
                MySqlConnectionFactory.from(
                    MySqlConnectionConfiguration.builder()
                        .host(url)
                        .username(username)
                        .password(password)
                        .database(dbname)
                        .sslMode(SslMode.DISABLED)
                        .port(port)
                        .allowMultiQueries(false) // <-
                        .build(),
                )

Yes, because I don't want to allow multiple queries. I want to prevent SQL injection vulnerabilities, so it would be nice to have an option.

You're generally safe from SQL injection when you write static SQL and bind parameters using Statement#bind. However, in case you find any vulnerabilities, please report them via security.
That said, you make a valid point—utilizing the allowMultiQueries flag can help reduce the attack surface.
Thanks!

Thank you.


Transformer model fails to translate certain input

Description
I have used the available checkpoints for get the English to German translation task to run.
I observed that some outputs given by the model are wrong and the model fails for certain input:
CASE 1: MODEL FAILS
ENGLISH: different
ERROR ENCOUNTERED:
decoded_output = decode(model_output)
return encoders["inputs"].decode(np.squeeze(integers))
File "/usr/lib/python2.7/site-packages/tensor2tensor/data_generators/text_encoder.py", line 522, in decode
tokenizer.decode(self._subtoken_ids_to_tokens(subtokens)))
File "/usr/lib/python2.7/site-packages/tensor2tensor/data_generators/text_encoder.py", line 571, in _subtoken_ids_to_tokens
[self._subtoken_id_to_subtoken_string(s) for s in subtokens])
TypeError: iteration over a 0-d array
How can this error be resolved?
CASE 2: INCONSISTENT OUTPUT FOR DIFFERENT CAPITALIZATION OF INPUT
ENGLISH:  this is german
GERMAN:  Das ist ein sehr schönes Hotel.
ENGLISH:  This is German
GERMAN:  Das ist Deutsch
The output is completely wrong when all lowercase letters are used here. Is this the expected behavior of the model? Why does it generate completely unrelated output here?
DEATILS:
tensor2tensor==1.6.3
tensorflow==1.5.0rc1
Problem: translate_ende_wmt32k
Model: transformer
hparams_set: transformer_base

TypeError: iteration over a 0-d array

This should not happen. Which of the available en-de checkpoints have you used? And which vocabulary file?

The output is completely wrong when all lowercase letters are used here

This is expected. The subword tokenization is case-sensitive, so you end up with a different sequence of subword IDs if you lowercase some letters.
Moreover, "German" as a proper name is always capitalized in English, at least in the en-de training data (which contains no Twitter, sms etc.).
Thus most probably there is no lowercase "german" in the training data.

I am using checkpoint 'transformer_ende_test' and voaculary file 'vocab.ende.32768'.
I see that there is another checkpoint for English to German Translation named 'transformer_ende_test_1201'. Using this checkpoint and vocabulary file 'vocab.ende.32768', I get the following results.
ENGLISH:  different
GERMAN:  Unterschiedliche Unterschiede
ISSUE: The translation is accurate. The German translation given corresponds to English text 'different differences' rather than just 'different'
ENGLISH:  Different
ERROR ENCOUNTERED:
decoded_output = decode(model_output)
return encoders["inputs"].decode(np.squeeze(integers))
File "/usr/lib/python2.7/site-packages/tensor2tensor/data_generators/text_encoder.py", line 522, in decode
tokenizer.decode(self._subtoken_ids_to_tokens(subtokens)))
File "/usr/lib/python2.7/site-packages/tensor2tensor/data_generators/text_encoder.py", line 571, in _subtoken_ids_to_tokens
[self._subtoken_id_to_subtoken_string(s) for s in subtokens])
TypeError: iteration over a 0-d array
ISSUE: Model fails with this error
Which is the better checkpoint to use?

Please could I get some help with this issue.

How exactly do you run the decoding? Do you use t2t-decoder?
Have you tried decoding at Google Colab? This should work for everyone.


Android: Links to websites whose apps are installed on the device don't open

Bug description:
If I try to open a link to say youtube.com, but I have the youtube app installed on the test-device, the link won't open. Linking.canOpenUrl will return false. External links that are not whitelisted but without apps on device work fine.
I have two unsatisfactory "solutions" for the problem:

Adding the package name of the specific app to AndroidManifest.xml

<queries>
   <package android:name="com.google.android.youtube" />
</ queries>

Adding the QUERY_ALL_PACKAGES permission
<uses-permission android:name="android.permission.QUERY_ALL_PACKAGES" />

Solution Nr. 1 is bad, because I can't anticipate which apps a user has. Nr 2 is bad because it will be flagged as a privacy issue.
Any ideas how to approach this?
To Reproduce:
AndroidManifest: https://github.com/orbiting/app/blob/main/android/app/src/main/AndroidManifest.xml
Expected behavior:
I expect links that are excluded from the whitelist to open in an external browser OR the app that captures the url via deeplinking.
Environment:

OS: Android
OS version: Android 11
react-native version: 0.64.2
react-native-webview version: 11.18.1

I'm encountering the same issue. Still looking for a workaround!

Any solution for this?

The solution to this issue was fixing a configuration error ind AndroidManifest.xml. We had to define a wildcard to the host of the https: intent scheme:
<intent>
     <action android:name="android.intent.action.VIEW" />
     <data android:scheme="https" android:host="*" />
 </intent>

In my case I try to open the DeepLink bunq://x-bunk-app/token-qr-request-ideal?token=xxxxxxx, or can be any other bank app installed on the user's device. But pressing those deep links in the web view does not give any positive result. I just can see a warning in the console Can't open URL: ....
Looking for solution

@aymkin
Add the following line inside the web-view component:
originWhitelist={['*']}
Then, you can listen all scheme inside onShouldStartLoadWithRequest method and pass the URL with linking. hope this will work.


apply_test files mixed up diffs (want, got) and (got, want)

Changes
While reviewing a PR to add helpers around cmp.Diff I noticed
that these apply_test files used both orderings (got, want) and
(want, got) in their tests.
I've updated the tests to use ordering of (want, got) uniformly.
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Commit messages follow commit message best practices

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

/test pull-tekton-pipeline-integration-tests

thanks @sbwsg
/lgtm


DropbboxClient Upload closes Stream

When calling a DropboxClient to upload a file via a stream, the function has the side effect of closing the stream:
using var dropbboxClient = new DropboxClient("apitoken");
using var stream = new MemoryStream(Encoding.UTF8.GetBytes("a text file"));
var request = new UploadArg("my new text file.txt");
var result = await dropbboxClient.Files.UploadAsync(request, stream);
stream.Seek(0, SeekOrigin.Begin); //Exception. Stream is closed

What happens:
dropbboxClient.Files.UploadAsync closes the stream after upload.
What should happen:
dropbboxClient.Files.UploadAsync should not close the stream. This is a hidden side effect that shouldn't happen.
Temporary Workaround:
Copy the stream into another stream.
AWS has some nice convenience features parallel to this with their s3 SDK.
var putRequest = new PutObjectRequest()
{
    BucketName = Bucket,
    Key = s3FileKey,
    AutoCloseStream = false,
    AutoResetStreamPosition = true,
    InputStream = stream,
};

The default of the sdk should be to NOT close the stream as this is a hidden side effect. However a nice enhancement would be to provide convenience properties in the class UploadArg of "AutoCloseStream" and "AutoResetStreamPosition" which can be set.
Thank you for reviewing.

Thanks for writing this up! I'll ask the team to look into changing this behavior and offer options for it.


[Duplicate]Adding custom floating action button to bottom navigation bar in android

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #4756

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Happy new year @WanjaMIKE?
Hope you are doing well.
Have made all the changes and opened a new pr.

Noted @Jackline-ke

Plagiarism check done ✅

@Jackline-ke please add a hero image and your author's information just as stated in the documentation. Thanks

Hello @WanjaMIKE  am so sorry for the inconvenience have included the author profile and also the hero image
Thanks

Great work team. @Jackline-ke @WanjaMIKE


baseline: support for custom reference keys

Allow user to specify a reference key in the
test case's refctx setting.  For example:
refctx = ["key:vp9.decode.10bit"]
will lookup the test case reference value with
the following key:
vp9.decode.10bit:<test_function(params...)>
This feature enables the ability to share a single
reference value (e.g. MD5) across different
middleware that implement the same test function for
each defined case (e.g. decode tests).
Signed-off-by: U. Artie Eoff<EMAIL_ADDRESS>

comments please!


[Feature-Request] Better installation instructions

Start with the why:
For a newbie like me, your installation instruction are confusing..
first i cloned the repo, then git submodules
then did the cmake thing and it doesnt work
CMake Error: The source directory "" does not exist.
How would one install this as a static library. I need to get this working with RTABMAP, any advice ?
Move to the how:
Is it possible to have a step by step installation process ..

@Huynh-Anh sorry for a late answer on this.
Does following this https://github.com/luxonis/depthai-core#building steps not work for you?
In that case, do you mind sharing:

Your OS
CMake version (cmake --version)
Your Toolchain (if using anything custom)


Two Data Type fields are shown for columns in Oracle

System information:

Operating system (distribution) and version win10 x64
DBeaver version 7.0.3

Connection specification:

Database name and version Oracle

Describe the problem you're observing:
Two Data Type fields are shown for columns in Oracle

Fixed

verified


feat: Added a static counter example

For a better example, I've enhanced the Counter-example.
** For now, I've created a static application, I'll be pushing small and clean commits while wiring up Kladi in the example.

@Souvikns @imabp , please keep having a look on this PR, and let me know if you find something wrong.

I haven't added links in the footer as I don't think documentation is available.
So, I'll add another issue and whenever docs and all are ready we can add it there.


Error on applying Azure Stack policy module to an Azure Subscription's Resource Group

I am trying to apply the Azure Stack policy module as per this link ( https://docs.microsoft.com/en-us/azure/azure-stack/azure-stack-policy-module ) onto my subscription, but get the following error. The tools download is from the public GitHub repo for Azure-Stack tools. Am I doing something wrong OR is this a bug?
PS C:\AzureStack-Tools-master> New-AzureRmPolicyAssignment -Name AzureStack -PolicyDefinition $policy -Scope /subscriptions/$s.Subscription.SubscriptionId/resourceGroups/$resourceGroupName
New-AzureRmPolicyAssignment : The pipeline has been stopped.
At line:1 char:1

New-AzureRmPolicyAssignment -Name AzureStack -PolicyDefinition $polic ...

  + CategoryInfo          : CloseError: (:) [New-AzureRmPolicyAssignment], PipelineStoppedException
  + FullyQualifiedErrorId : Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzurePolicyAssignmentCmdlet

New-AzureRmPolicyAssignment : BadRequest : The subscription identifier 'Microsoft.Azure.Commands.Profile.Models.PSAzureContext.Subscription.SubscriptionId' exceeded the
maximum length of '64' characters.
At line:1 char:1

New-AzureRmPolicyAssignment -Name AzureStack -PolicyDefinition $polic ...

  + CategoryInfo          : CloseError: (:) [New-AzureRmPolicyAssignment], ErrorResponseMessageException
  + FullyQualifiedErrorId : BadRequest,Microsoft.Azure.Commands.ResourceManager.Cmdlets.Implementation.NewAzurePolicyAssignmentCmdlet

Thanks,
Girish.

Hey Girish,
It looks like you specified the scope of the policy as:
-Scope /subscriptions/$s.Subscription.SubscriptionId/resourceGroups/$resourceGroupName
Instead, retrieve the subscription ID ahead of the scope request.
The following example on the ReadMe may be helpful:
Import-Module .\AzureStack.Policy.psm1

Login-AzureRmAccount
$s = Select-AzureRmSubscription -SubscriptionName "<sub name>"
$subId = $s.Subscription.SubscriptionId

$policy = New-AzureRmPolicyDefinition -Name AzureStack -Policy (Get-AzureStackRmPolicy)

New-AzureRmPolicyAssignment -Name AzureStack -PolicyDefinition $policy -Scope /subscriptions/$subId

With the above, I was unable to reproduce any error. Closing at this time.


don't work on nuxt 3.0.0-rc.14, ok on 3.0.0-rc.13

Version
@nuxtjs/supabase: 0.3.0
nuxt: 3.0.0-rc.14
Issue
Just adding module in nuxt.config.ts and launch server with yarn dev -o cause this error : Cannot read properties of undefined (reading 'supabase')
Fix
Change nuxt: 3.0.0-rc.14 to nuxt: 3.0.0-rc.13 in package.json
sudo rm -rf node_modules/
yarn install
yarn dev -o

Can you try with the Nuxt3 stable version (v3.0.0) ?

It's ok ! my bad, didn't see the 3.0.0 nuxt 3 stable version.
Thks!


'overlap' in 'configs/tdmatch/3DMatch.pkl' and 'configs/benchmarks/3DMatch/7-scenes-redkitchen/gt_overlap.log'

Thank you for your great work. can you tell me why the 'overlap' in 'configs/tdmatch/3DMatch.pkl' and 'configs/benchmarks/3DMatch/7-scenes-redkitchen/gt_overlap.log' is different,please.

Thank you for your great work. can you tell me why the 'overlap' in 'configs/tdmatch/3DMatch.pkl' and 'configs/benchmarks/3DMatch/7-scenes-redkitchen/gt_overlap.log' is different,please.

I encountered an issue while running "Compile C++ and CUDA scripts". What versions of CUDA and C++ are you using? Thank you.


ng-file-upload with ionic file  dialog open twice

http://embed.plnkr.co/xrQXOuFncBBA7c1R5t0W/preview

Greetings @Jaware!
My sensors indicate that you need to update your issue through our custom issue form. We are now requiring all issues to be submitted this way, to ensure that we have all of the information necessary to fix them as quickly as possible.
Click Here To Update Your Issue
I will have no choice but to close this issue if it is not resubmitted through the form. Please fill out the rest of the form, so that I may use my friendly robot powers to assist you.
Thank you!

it is ok on pc while both android and ios open file dialog twice,the first dialog can not work,only the second dialog can upload file

Greetings @Jaware!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


Update from rsa 0.3.0 to 0.5.0.

This should put a stop to the nightly test failures.

This should put a stop to the nightly test failures.

I find it so annoying that nightly runs don't usually send emails even to those who are supposedly watching for all activity and are repo admins. Do you happen to know if there's an option to change this?

Do you happen to know if there's an option to change this?

I don't know, but I was getting an e-mail every night because of my fork of the repo.


Asset Card Component

Construct an Asset Card Component that can be reused across transaction events (minting, burning), sending/receiving assets on the transaction details.  The Asset card should be similar to the stakepool card, in that it uses a flex grid layout for responsiveness.
Each asset contains the following fields:

Name
Policy
Fingerprint (this is like the unique id for an asset)
Total Supply

Assets contain optional Metadata that describes the asset.  Unfortunately the optional metadata is schemaless and can contain almost anything.  However there are some key characteristics we need to verify.

Image - This is the main image associated with the token, in general this will be a web url, or an IPFS identifier.

Ipfs Identifiers may need to be translated into a URL.

ipfs://ipfs/QmXc7RbxHrTg7KumsMS2BrZjk7aKCbG7hRDKpAG5ZX86oT =>https://ipfs.io/ipfs/QmXc7RbxHrTg7KumsMS2BrZjk7aKCbG7hRDKpAG5ZX86oT
ipfs://QmXc7RbxHrTg7KumsMS2BrZjk7aKCbG7hRDKpAG5ZX86oT =>https://ipfs.io/ipfs/QmXc7RbxHrTg7KumsMS2BrZjk7aKCbG7hRDKpAG5ZX86oT

Arweave identifiers may need to be translated

ar://bTYB-gK-DLKO1roap6-ZR-jR5P3UA-6RxR3o4ndDVCk => https://arweave.net/bTYB-gK-DLKO1roap6-ZR-jR5P3UA-6RxR3o4ndDVCk

will need to do some analysis on schemaless metadata to determine where the image keys are most often found.

Attributes - Often times an NFT will contain attributes (rarity, etc) and there should be an attributes section of the card.

again will need to do some analysis on the schemaless metadata to determine how to get the attributes

Might look at doing some of this translation work on the serverside so the API returns standard values so we don't need this logic in the UI.  For example adding a specific image attribute to the json response.  Will do some analysis on this.
A couple options for using the card on the wallet view.

Could add a drill down from the Asset Holdings table when you click on a row to bring up the details for the asset holding (including asset card)
Modify the asset holdings from a table to a gallery of asset cards. (I prefer this option)

Sample wallet with assets: stake1uylw5ges065hhcexl7vyc8fgpeqpdja9mqlmpxp4fr6lmvsqn9m47

@johnnuy  Do we have a default image that should be displayed for cases when the assets image is unable to be parsed?

@lefebvk I'm working on adding an imageUrl attribute to the Asset json model.  If I am unable to determine an image url from the asset metadata then I will be setting this value to a default url supplied by our CDN, which will have the following format:
https://cdn-dev.canadastakes.ca//tokens//logo.png
where network is {testnet, preview, preprod, mainnet) and fingerprint is the asset fingerprint.  This endpoint on the CDN is available on the cdn-dev only at the moment.
working example with the default image:
https://cdn-dev.canadastakes.ca/preview/tokens/asset1tvh6cs0q40l6nlgf8a52les0jg94gzfuvl2e7q/logo.png
One thing to note, there is no standard image size or ratio (4:3, 16:9, etc), so hopefully there's a way you can set a fixed width on them, and then the browser (or a js lib) can auto scale them to keep them from displaying large...
I'm hoping to have the updated Asset model done this week.  Additionally i've added some new fields for registered tokens that I will be posting at the same time.    Registered tokens, are assets that have been registered with the cardano token registry and have a couple additional elements to their name.  Generally these are fungible tokens that act as separate currencies on the cardano network, such as World Mobile Tokens.

The asset metadata is just unbelievably diverse with no real standards, so might need to have some sort of a generic bucket that can show a range from 1 to in some cases 50 different key/value pairs that are associated with a given asset.  I'm hoping you won't have to actually parse the metadata, and you can maybe display it in like a tree structure or something?  because some of the metadata attributes are objects themselves.

Adding 3 new fields to the asset response that are derived from the metadata:
contentUrl --> fully qualified url translation of the asset content
contentType --> mime type of the asset content
contentData --> when the asset content is on chain, instead of offchain at a url, this is generally an embedded image format.
There will always be at least one of {contentUrl, contentData}. There could be both.  if contentData is available, this is onchain data and should take precedence.   The url will be from onchain data, or will be a default image from the CDN.  You shouldn't have to parse the metadata to get the URL now.  There certainly are gobs of garbage on chain, so I will be able to over time add additional logic to help parse metadata, but for now it appears to be about 95% of assets have a contentUrl.
One thing is I can't guarantee the onchain content url's are valid.  I will be looking at potentially validating all of the asset content URL's and downloading associated image data to the CDN so that all contentURL will load from our CDN, but that process is likely to be slow when validating/downloading 8m+ assets, so I will need to determine a systematic way to do that, also one that minimizes storach needs.

The following wallet currently has an Asset with onchain content rather than offchain content
https://api-dev.canadastakes.ca/mainnet/api/wallets/stake1u8lf2avlhd3zvu4jzymrxnm2yew90euqz46nkt2ewmg4xdsqxg3hl/assets/asset100065rx7jxjxrkq362npyglyure0c8wltkz4wy

Can the grid be modified so that it goes as up to 6 cols x 2 rows for ultrawide?
Can you remove the fingerprint from the initial grid, it's on the drilldown and looks odd there.
Registered tokens have additional information such as precision which should be used to display the quantity.  Such as
https://api-dev.canadastakes.ca/mainnet/api/wallets/stake1uylw5ges065hhcexl7vyc8fgpeqpdja9mqlmpxp4fr6lmvsqn9m47/assets/asset105nh988tzzzk3duk6relug69td98ja3nl3uv2c
where supply and quantity should be divided by 1,000,000.  displayed similar to ada values which are 6 decimals precision also.

@lefebvk
when the precision is availble for a registered token, the value should be divided by 10^p where p is the precision.
So for example with precision 6 take the value and divide by 1,000,000.
so 16,878,000 with precision 6 would display as 16.878
this is similar to ADA which is really lovelace with a precision of 6.

Examples of the image squishing/stretching with various resolutions.


Update Travis config

When reenabled the Travis status should now be green again.
The image that is built on Travis is reported to be 276 MB.
https://travis-ci.com/github/abitrolly/cheat.sh/builds/177627315#L386
Now need to find a way to run tests with it.

We have a test script that can access an external url, so we can use the script for the beginning

@abitrolly do we need an issue for the tests, or you are already experimenting with it?

@chubin well, manual instruction wouldn't hurt, but I see this is already documented at https://github.com/chubin/cheat.sh/blob/master/tests/run-tests.sh


Build time and run time mistaken?

MSBuild properties
[...]
They also overwrite any options you set in the [appname].runtimeconfig.json file at build time.

Shouldn't this rather read "[...] at run time."?

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

ID: 2aa7bda7-581d-9654-c7c5-5ff0292ddfb3
Version Independent ID: 7f32162e-ec95-0a16-7618-14b7a7c80cff
Content: Run-time config options - .NET
Content Source: docs/core/run-time-config/index.md
Product: dotnet-fundamentals
GitHub Login: @gewarren
Microsoft Alias: gewarren

@SetTrend I believe it's written correctly. At build time, any options in the [appname].runtimeconfig.json file will be updated to match the MSBuild properties for run-time configuration.

Excellent! Thank you for taking the time to deal with this! 👍

Excellent! Thank you for taking the time to deal with this! 👍


Compatibility issue

plugin is not compatible with Lighty's message logger v2 plugin, the button covers it up. also appears to not play nice with user notes by creating 2 member list buttons.

plugin is not compatible with Lighty's message logger v2 plugin, the button covers it up.
Unfortunately you are going to have to ask Lighty to account for this, as the plugin you mentioned is against BetterDiscord's and Discord's ToS and I cannot support it.

also appears to not play nice with user notes by creating 2 member list buttons.
I tried it with UserNotes, it works fine? Are you certain that that is the plugin it is conflicting with?