Reasonable Defaults For Centrally Controlled PackageReference Version

Here's a potential Approach for #46 and #49
Utilizing this SDK will now provide "reasonable" default version numbers for certain PackageReferences

Directly setting the Version metadata when no Central management is detected (behavior existed already)
Creating PackageReference Update statements when CentralPackageVersionSdk is enabled (and only when Packages.targets does not provide version value)
Creating PackageVersion Include statements when CentralPackageManagement is enabled (and only when Directory.Packages.targets does not provide version value)

This Sdk will provide an inforrmational "Warning" level message during build recommending the project owner to add an entry into their package management system of choice... for those packages that do not have a centralized version entry, and the Sdk default value was applied.
@brandon-hurler and @CZEMacLeod See if this aligns with what you were looking for

This looks very good and well thought out. There are some very clever bits of MSBuild stuff there with metadata and item group transforms but I like it. How much testing have you done to check these work as expected?
The only thing I think I would like to tweak is the line that controls the application of the PackageReference updates to include the version numbers - Condition=" '$(UsingMicrosoftCentralPackageVersionsSdk)' != 'true' AND '$(ManagePackageVersionsCentrally)' != 'true' "
Could we introduce a property, something like ApplySystemWebSdkPackageVersions which will be set to true if it isn't set, and the existing conditions aren't set. This means you could manually disable that section more easily.
I really like the target with the warning SystemWebSdkProvidedPackageVersionDefaultWarning  - I think that is very much the issue I had with applying the defaults when using CPM. Can you explain where EnableMimicControlPackageVersion comes from? Is this just the property used to disable the default versions? Is that the best name? Should it be EnableMimicCentralPackageVersions? I don't want to nit-pick, especially as this is great work, but one thing I think is missing in this project is the documentation and making the properties have obvious names to what they do is the first step.

The testing I focused on was to create 2 projects (one CPM and one CPV) and walked it through the following phases

Initially having "zero" entries in the respective "central" files (Directory.Packages.props and Packages.targets) -> results in the SDK default versions being injected, and 4 warnings total (1 warning for each of the 2 Packages for each of the 2 projects)
Adding an entry for the  toolset PacakgeReference -> results in the SDK default versions being injected, and 2 warnings total (1 warning for the CompilerPlatform Packages for each of the 2 projects)
Adding the entry for the CompilePlatform -> results in the Sdk default versions being ignored, and zero warnings generated
If you'd like to wait to take this until there are unit tests in place, I can probably make that happen too, as I was starting to play with that again.

For your question about tweaking an area and potentially adding a new property to govern disabling that section, were you referring to this section below? This is the part that sets the "Version" metadata when there is NO central management of package versions, so I'm thinking that we wouldn't ever turn this particular section off.  But Maybe I misread your question.
    <PackageReference Update="@(PackageReference->WithMetadataValue('SystemWebSdkIncludedPackage','true')->HasMetadata('SystemWebSdkIncludedPackageVersion'))"
                      Condition=" '$(UsingMicrosoftCentralPackageVersionsSdk)' != 'true' AND '$(ManagePackageVersionsCentrally)' != 'true' ">
      <Version>%(SystemWebSdkIncludedPackageVersion)</Version>
    </PackageReference>

I would love better ideas on the EnableMimicControlPackageVersion name, as I wasn't sure exactly what to call it either.
This is the project owner configurable property that governs whether or not the Sdk will attempt to "mimic" an entry in the detected centralized package version mechanism.

It doesn't "persist" anything to a file in the obj\ directory or do any writes to the Directory.Packages.props or Packages.props
It doesn't duplicate or overwrite anything previously set by the project owner
It does it for both CentralPackageVersion and CentralPackageManagement, so it seemed odd to call it specifically one of those
It just does it's best (when not explicitly set to false) to ensure that a new project can be created with the Sdk under a directory that has enabled centralized control.  So in my head it was only "mimicking" the things that the warning was reminding the project owner they should be doing

I whole heartedly agree though, even if most people will never need to set it to false, we should strive to come up with meaningful names.

@CZEMacLeod  I added Unit Tests for the 3 simplest of cases. If this seems worthwhile I can add coverage for the other cases as well.  And if you have a unit test "Fluent Assertion" flavor preference (should be able to swap in/out whichever one)
I added a description about the Property, and the behaviors for version metadata to the documentation Sdk.md. I noticed that the RazorLibrary.md does not currently have the same table describing properties, Should I add a similar one there as well?

@leusbj I've pushed a small update V4.0.88 which addresses some of the outstanding issues.
I would really like to include your cleverness from this PR around applying packages and versions - perhaps you could rebase it off the latest. Hopefully some of the changes there will simplify how this goes.
I've added some info to the documentation for the properties used.

Property
Default value
Description

ExcludeSDKDefaultPackages
false
Do not include the default packages Microsoft.Net.Compilers.Toolset and Microsoft.CodeDom.Providers.DotNetCompilerPlatform

ApplySDKDefaultPackageVersions
true*
Apply default version numbers to packages unless using a Central Package Management system

*Version numbers are not applied if you are using Microsoft.Build.CentralPackageVersions version 2.1.1 or higher. Remember to include the packages in your central package versions file.
You will see that ApplySDKDefaultPackageVersions is now set to false if either of the CPM solutions are in use.
I think these property names make sense.
I'm not sure about the unit testing stuff - I think it would need to be added to the build scripts, and the main issue I wanted to ensure was not so much that it worked in all the situations we wanted to cover, but that any other packagereferences in the main project file would not get their version numbers messed up (something I have done in the past when trying to update an item from another item).
Specifically, with
    <PackageReference Update="@(PackageReference->WithMetadataValue('SystemWebSdkIncludedPackage','true')->HasMetadata('SystemWebSdkIncludedPackageVersion'))"
                      Condition=" '$(UsingMicrosoftCentralPackageVersionsSdk)' != 'true' AND '$(ManagePackageVersionsCentrally)' != 'true' ">
      <Version>%(SystemWebSdkIncludedPackageVersion)</Version>
    </PackageReference>

to make sure that it does not overwrite all packagereferences or updates them all to the value of %(SystemWebSdkIncludedPackageVersion) of last one matched.
As I said, assuming this logic behaves correctly I really like everything done here.

@leusbj I've pushed a small update V4.0.88 which addresses some of the outstanding issues.
I would really like to include your cleverness from this PR around applying packages and versions - perhaps you could rebase it off the latest. Hopefully some of the changes there will simplify how this goes.
I've added some info to the documentation for the properties used.

Property
Default value
Description

ExcludeSDKDefaultPackages
false
Do not include the default packages Microsoft.Net.Compilers.Toolset and Microsoft.CodeDom.Providers.DotNetCompilerPlatform

ApplySDKDefaultPackageVersions
true*
Apply default version numbers to packages unless using a Central Package Management system

*Version numbers are not applied if you are using Microsoft.Build.CentralPackageVersions version 2.1.1 or higher. Remember to include the packages in your central package versions file.
You will see that ApplySDKDefaultPackageVersions is now set to false if either of the CPM solutions are in use.
I think these property names make sense.
I'm not sure about the unit testing stuff - I think it would need to be added to the build scripts, and the main issue I wanted to ensure was not so much that it worked in all the situations we wanted to cover, but that any other packagereferences in the main project file would not get their version numbers messed up (something I have done in the past when trying to update an item from another item).
Specifically, with
    <PackageReference Update="@(PackageReference->WithMetadataValue('SystemWebSdkIncludedPackage','true')->HasMetadata('SystemWebSdkIncludedPackageVersion'))"
                      Condition=" '$(UsingMicrosoftCentralPackageVersionsSdk)' != 'true' AND '$(ManagePackageVersionsCentrally)' != 'true' ">
      <Version>%(SystemWebSdkIncludedPackageVersion)</Version>
    </PackageReference>

It looks good to me as well. I agree that there was some clever MSBuild work in here. I kept circling back in my free time trying to think how to solve the issues @CZEMacLeod and you had presented but I hadn't come up with a set that addressed everything.
I would like to assist in testing this after the rebase and outstanding issues are addressed. Let me know how I can help.

@CZEMacLeod
I am starting to merge the recent updates down into the branch that is the source for this PR, but I think I'm to a point where I want to get some opinions merging a couple of conflicts.

To-Version or Not-To-Version (and if so... do it appropriately)
a. The recent property ApplySDKDefaultPackageVersions is set to false whenever either of the two "Centralized" methods are incorporated. Then is used to prevent a build errors by preventing the Version metadata from being set by this SDK at all.
b. The property EnablePackageVersionDefaultsFromSdk from this PR isn't based on the presence of the presence of "Centralized" methods. Instead the assumption is made that this Sdk will make every attempt to bring in the Version metada using the correct time and itemgroup, unless it is told not to... And this EnablePackageVersionDefaultsFromSdk property is the project/repo owner's opportunity to explicitly prevent this SDK from making ANY attempt  to incorporate the appropriate items at the appropriate times.
c. I would like to repurpose your property name, to take on the meaning/behavior to be the more complicated concept. But if you would like to leave that property in place, and for me to use a differently named variable for the more complicated behavior let me know.
The latest version of CentralPackageVersions will under certain circumstances set a EnableCentralPackageVersions property to false. and it will only perform it's validation when that property is != false.  I am intending to interrogate that property to make decisions about To-Version or Not-To-Version... because in the case of a project that incorporates the SDK, but doesn't create a packages.props, it will have UsingMicrosoftCentralPackageVersionsSdk == true but it will not actually enforce anything... and our goal of setting Version whenever we can should understand that.  If you disagree, let me know.
Please take a look at this proposed messaging, about times where this SDK has given version information, that a project/repo owner should likely be incorporating into their "Centralized" mechanism
a. The PackageReference '{PackageName}' was implictly included defaulting to Version='{VersionAsProvided}'. Centralized management of package versions was detected, consider adding an entry to your centralized package version listing.
b. Please suggest something different if so desired.

@leusbj

To-Version or Not-To-Version (and if so... do it appropriately)
a. The recent property ApplySDKDefaultPackageVersions is set to false whenever either of the two "Centralized" methods are incorporated. Then is used to prevent a build errors by preventing the Version metadata from being set by this SDK at all.
Yes - however, it can be manually set to false to prevent the application of package versions - e.g. if you were applying them in Directory.Build.targets but not doing CPM.

b. The property EnablePackageVersionDefaultsFromSdk from this PR isn't based on the presence of the presence of "Centralized" methods. Instead the assumption is made that this Sdk will make every attempt to bring in the Version metada using the correct time and itemgroup, unless it is told not to... And this EnablePackageVersionDefaultsFromSdk property is the project/repo owner's opportunity to explicitly prevent this SDK from making ANY attempt  to incorporate the appropriate items at the appropriate times.
The new property was designed to take on this role.

c. I would like to repurpose your property name, to take on the meaning/behavior to be the more complicated concept. But if you would like to leave that property in place, and for me to use a differently named variable for the more complicated behavior let me know.
It is basically the same role - so yes. If you don't manually set ApplySDKDefaultPackageVersions to false, then try to apply those versions, even with CPM, unless CPM has already set the version numbers.

The latest version of CentralPackageVersions will under certain circumstances set a EnableCentralPackageVersions property to false. and it will only perform it's validation when that property is != false.  I am intending to interrogate that property to make decisions about To-Version or Not-To-Version... because in the case of a project that incorporates the SDK, but doesn't create a packages.props, it will have UsingMicrosoftCentralPackageVersionsSdk == true but it will not actually enforce anything... and our goal of setting Version whenever we can should understand that.  If you disagree, let me know.
I'm not aware of this behaviour, but if you can handle those circumstances, then please do.
I don't feel that this SDK should really cover people doing silly things, but if it can JustWork™ in most circumstances, and prevent issues where e.g. it can't restore packages property and ends up in a 'broken' state then I'm all for it.

Please take a look at this proposed messaging, about times where this SDK has given version information, that a project/repo owner should likely be incorporating into their "Centralized" mechanism
a. The PackageReference '{PackageName}' was implictly included defaulting to Version='{VersionAsProvided}'. Centralized management of package versions was detected, consider adding an entry to your centralized package version listing.
Looks good to me. Do we want to add the text that a user should add (like binding redirects does)? Although that will have to have 2 versions depending on which CPM is in use...
b. Please suggest something different if so desired.
Does this have the ability to detect if a package downgrade is happening? I feel that if the SDK says version 5.2.9 of MVC and you have CPM set to 5.2.8 it should perhaps warn? Maybe that isn't really within the scope and in general we don't actually need a specific version of packages (other than perhaps the compilers toolset as that can cause a break on some versions of VS2022).
Maybe we can shelve that for now and make it an option in the future, just to complete this part.

Do you want me to take a stab at adding a "Unit Test" to the azure-pipelines.yml ?

You can certainly add that in. At the moment the pipeline doesn't run for PRs, and I can mess with it (if need be) once this is merged.
I'll look into doing some tests on running the pipeline on PRs (obviously without any signing/publishing) and maybe enable that in the future.

Closing this PR for now, as the goals and design has moved quite a long way since this version


ifs, lambdas, type declarations, etc.

A few notes that I have regarding this great piece of work. Hopefully not too late and not too pretentious.
if

I think there's more to expressions than just small expressions and large expressions. Could this be clarified a bit? How about differentiating between multi-line, single-line short (simple values) and single-line long (function evaluations) expressions?
When e1 and e2 are both single-line (short or long) expressions, I almost always choose this:if cond
then e1
else e2

I like the way it looks like a match. then and else are same length - great coincidence (or design!) IMHO. I guess one drawback is that you kind of need IDE to highlight the relevant bits to look really nice.
I would personally avoid this even if expressions are of different size:if cond then e1
else
    e2

I prefer e1 and e2 to be at the same distance from the left side of the window (on the same level). The example above breaks the logical structure of the construct.

Lambdas
Why not like this:
let printListWithOffset a list1 =
    List.iter
        (fun elem ->
            c1) // When c1 is multi-line
        list1

Or:
let printListWithOffset a list1 =
    List.iter
        (fun elem -> c1) // When c1 is single-line
        list1

This matches nicely with the function parameter application formatting guidelines. No dangling parentheses.
Other notes

One-liner match example looks complicated. Is there a good reason not to break that into three lines?
I'm missing guidelines on how to format explicit type declarations. Especially of interest are the more complicated cases - multiple parameters, generics, functions.
I see value in the multi-line comments. When changing the content of the comment I often need to break the lines in different places than previously. In those cases the // are in the way.
And finally, perhaps all of my questions could have been avoided :) I think it's very valuable with controversial topics such as style guides to have argumentation close at hand to justify the choices taken in more detail. Not necessarily in the guide itself, but perhaps in a separate article, or footnotes?

Again, thanks for the lovely work.

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

ID: 8c09996f-24ac-cf39-ef43-d7909cbc2b89
Version Independent ID: 1efdd523-8552-6421-e149-74f76826ef8f
Content: F# code formatting guidelines
Content Source: docs/fsharp/style-guide/formatting.md
Service: unspecified
Product: dotnet-fsharp
GitHub Login: @cartermp
Microsoft Alias: phcart

Let's brainstorm a bit on the if section. It's currently short (and hopefully sweet) to cover what I believe to be a common question beginners have w.r.t how to format the expressions. But you're right that there is more to it than just how long the expressions will be.
I think the following are considered by people:

Size of each expression
Aligning stylistically with other code in their codebase (e.g., looking similar to a match expression)
How long (character count) a line is before it deserves a line break
If expressions should be aligned with each other or not

What else do you feel are considerations?

@cartermp
First off, after reading your comments, I realized that I might have looked at the guide a bit differently to begin with. To me, it is about two things. As a starting point for beginners, but also as a guidance to get everyone aligned on the same style. This was my primary motivation, FYI. I do hope to be challenged before we actually do any changes.

Since this document is a live article and absolutely subject to change based on feedback, feel free to make that PR and how it's worded.

I can prepare something, but it will probably take a little while before I get to it.
Here's the changes that I would make:

Change the wording a bit: instead of small / large, use single-line / multi-line (where appropriate) and short / long.
Remove this:if cond then e1
else
    e2

and this:if cond then
 e1
else e2

Add this instead:if cond
then e1
else e2

What else do you feel are considerations?

Well put, I can't think of anything at the moment, but I'll let my brain process this a bit in the coming days and get back to you, if I remember anything important.
if section definitely needs challenge, but I'm not sure how to get that. Do you think a PR would help?

@cartermp any updates to this one? Can you assign a milestone?

@cartermp any updates to this one? Can you assign a milestone?

Hey there, sorry for the lack of response.
@giedriusbruzas please do submit a PR and we can review there.


Bar chart outside range of axis

I don't know if this is related to the other issue regarding binning of timestamps. I minimised my input file to this set:
datetime,events
2017-02-16T01:04:18,20
2017-02-16T02:03:05,1
2017-02-16T03:04:37,10
2017-02-16T04:04:21,20
2017-02-16T05:21:21,8
2017-02-16T06:04:18,10
2017-02-16T07:04:43,10
2017-02-16T08:35:05,1
2017-02-16T09:04:21,20
2017-02-16T10:37:52,1
2017-02-16T11:01:05,5
2017-02-16T12:43:04,1
2017-02-16T13:03:56,1
2017-02-16T14:04:21,20

I used a statement like the following
bar x(datetime) y(events:linear) sum(events)  tooltip(datetime,events)&width=400&height=200
The width and height at the end are there because I use this in a browser window using the rest interface.
The resulting chart consists of mainly two peaks: one on 02AM and one on 03AM.
If I size and grab the chart, I can see there are also peaks more to the right.
If I remove the three last records from my input file, the graph collapses to a single bar that coincides with the y-axis, and the labels on the x-axis are gone.

I have been re-working the data pipeline, which includes some major changes, and on the code I am working on, this issue looks resolved, so I expect I have solved it as a byproduct of the current work I'm doing. I expect to check in these changes in a few days

Fix now checked into master


Wine Quality Prediction using ML

I want to add a beginner Winequality prediction program that predictis the quality of wine based on Multiple factors

@sanjay-kv Can You assign me this


SAF Import '-resume' option not working + poor performance

Describe the bug
A clear and concise description of what the bug is.  Include the version(s) of DSpace where you've seen this problem. Link to examples if they are public.
DSpace 7.5
Importing files in Simple Archive Format with the -R (-resume) option will not save the items listed in the mapfile before the resume.
Also the performance is very poor: cca.4 hours for 1500 items imported.
To Reproduce
Steps to reproduce the behavior:

Import some items in Simple-Archive-Format
Provide a wrong metadata value for a field (ex. for dc.contributor.author provide as value John Doe-)
The error will stop the import. Try to fix the error (remove the '-' from author's value)
Resume the import using the -R option and providing the mapfile with the previously imported documents
After completion, check the repository for the files imported (by number or by handle)
Only the items after the resume can be found in the repository!

Expected behavior
After the resume, all the items listed in the mapfile should be imported.
I noticed that the items are not committed to the DB until all the items are added.
ItemImport.java -> line 229.
Would context.commit() after each item solve the resume problem and improve the performance as the data is not cached in memory for thousands of items till all items are added? see ItemImportServiceImpl.java -> line 810

Just at a glance, it does look like ItemImport.java is missing any type of incremental commit.  The only commit I see is the complete() statement that you reference: https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/app/itemimport/ItemImport.java#L229
Ideally, there should be an incremental commit (perhaps even configurable), maybe along the lines of what was done for the CSV import code: https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/app/bulkedit/MetadataImport.java#L601-L604
Likely this lack of incremental commit is also the cause of the issues with the resume option, as the previously added items were never committed before the error occurred.
This does seem like a bug, so I'm pulling it over to the 7.6.x maintenance branch in search of a volunteer.

Adding c.commit() at line 810 in ItemImportServiceImpl.java solves the 'resume' problem (tested yesterday). And I guess that the performance is similar or even better because for long imports the data (1000xitems) is not cached in memory till the end.


Fix typo

Typo in CommentControllerBase class.

Thank you for the PR, but we follow the same guidelines as https://github.com/microsoft/vscode and prefer not to take PRs that just fix spelling errors: https://github.com/microsoft/vscode/wiki/How-to-Contribute#spell-check-errors


Trivial typo

Greetings,
This is rather trivial and insignificant.
In "Authoring environment" / "Formula separators and chaining operator"
(right below the "dot" vs "comma" table...)
"The change in the PowerApps list separator is consistent with that happens to the Excel list separator."
>> should be " [...] consistent with what happens to [...] "

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

ID: 864e69eb-925d-45a3-e79e-0356ee826ad9
Version Independent ID: 1833ba5a-da61-7c5a-c4b2-2a7c6d983494
Content: Build global support into canvas apps - PowerApps
Content Source: powerapps-docs/maker/canvas-apps/global-apps.md
Service: powerapps
GitHub Login: @gregli-msft
Microsoft Alias: gregli

Fixed. Thanks, @a-zaf!


The MMMU evaluation in the  InternVL2.5

I have some confusion about the evaluation in the InternVL2.5 technical report.
How to understand "We report the maximum accuracy achieved across both direct-answer and CoT reasoning approaches on the MMMU validation and test sets" ？
Does it mean that we evaluate multiple times, and then choose the best result (in direct-answer and CoT setting) ?

Yes, we test twice for each model, with or without the CoT prompt, and then report the highest value. This evaluation method was inspired by the MMMU-Pro paper.

I will update our CoT evaluation code to VLMEvalKit soon.


Updated email link signin to use latest format for ActionCodeSettings

Description
ActionCodeSettings changed in current (2.0.1) auth in action_code_settings.dart, so changed example to fit
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (flutter analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[ ] I updated CHANGELOG.md to add a description of the change.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Hey @PaulTR - thanks for sending this over, appreciate it :)

@googlebot I consent.


Put zcache in XDG_CACHE_HOME if it exists

Resolves #5, by using $XDG_CACHE_HOME if it exists for the zoxide cache. If not the current behavior prevails, using the dir containing __file__.

Thanks!


Qt 5.12.3

Motivation for this change
This is carried over from #60119, but rebased onto the staging branch, and with a fix to one of our patches of qtbase.
CC: @vandenoever @bkchr
Things done

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

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

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

@GrahamcOfBorg eval


correct spelling

'sources' and lower case 'harvest'

this has not been merged nor deployed so can't be tested

This has been addressed


error new update

good morning, with the new update of the repair of December failure to stop working and gives error, to changed some way to set it? thank you very much a great job klaus3d3

Thanks for your recommendations, but it could not be made to work. I also format the clock and it did not work. I reinstall the previous version and it works perfectly. Thanks for your help

I'm in the same situation as Andres ... Impossible to work with this new version.
I have exactly the same screenshots that the partner attached, with this last version it does not work for me.
I have returned to the previous version and everything is perfect again.
Thank you all for your work

Sorry: I cannot test it for some weeks because I need it to be fully operative (mine is Pace). I will try it later (I need a couple of weeks).
Anyway, I realized that there are several changes, the size increased from 2,11 MB to more than 11MB and there is also a major change relative to the SDK language level from 1_7 to 1_8 and some other relative to compiling versions (target SDK version 27 vs 22 and other similar changes). Could this cause any problem when deploying it to the watch due to any incompatibility with current version of watch's software?
I will try the updated version in a couple of weeks, provided I can go back to previous one

I have had same issue. 2018 klaus'es xdrip and old watchface worked but that version made g5 transmitter battery drain. So, I updated Xdrip to the latest nightly and Pace xdrip watchface stopped to work.
What made it work? I reset watch to factory settings and then installed latest klaus'es xdrip watchface and it got connected after 1 'resend glucose to watch' from xdrip
cheers!


docs(examples): add tests and example of array styles

What: This adds tests and documents how glamor(ous) handles arrays of style objects

Why: Closes #118

How:

Renamed the test files (don't need *.test.js when the files are in __tests__)
Added a note in the README
Added an example in the examples
Added a test to make sure this existing functionality never breaks, because it's really useful!

Checklist:

[x] Documentation
[x] Tests
[ ] Code complete
[ ] Added myself to contributors table
[x] Followed the commit message format

I'm going to go ahead and let anyone of the maintainers review and merge this one! Make sure to follow the maintainer guidelines :)

Codecov Report

Merging #120 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #120   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         124    124
  Branches       32     32
=====================================
  Hits          124    124

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 18db572...692f65a. Read the comment docs.


openthread: fix source IP address selection

This series of commits adds 2 new function pointers to the L2 layer API:
get_best_match_ipv6()
get_best_match_ipv4()
This allows the L2 layer to override the default logic which chooses the source IP address for outbound traffic.
This is important for OpenThread, because the current logic is completely broken.  OT uses several non-link local unicast IPs for mesh local purposes (like routing, etc), but these should not be used for outbound traffic if a border router prefix is assigned.  OpenThread already has it's own logic to correctly select the IP, so we should be able to use it.

Addresses: https://github.com/zephyrproject-rtos/zephyr/issues/12203

@turon Adding you for review.

Fixing checkpatch issues.

@mike-scott, thanks for your patches, I confirm it fixes the issue I was seeing with UDP source address selection for COAP. Note that I do not use global addresses on my devices, just Mesh-Local EID addresses. I guess than if/when I add a global address, then ML-EID addresses will break with COAP as the global address will be used for the answer. That said it's already a huge improvement and much better than the workaround I implemented in my COAP server.
Note that I haven't really looked at your code yet.

Codecov Report

Merging #12343 into master will decrease coverage by <.01%.
The diff coverage is 78.12%.

@@            Coverage Diff             @@
##           master   #12343      +/-   ##
==========================================
- Coverage   48.32%   48.31%   -0.01%
==========================================
  Files         294      294
  Lines       44189    44193       +4
  Branches    10600    10598       -2
==========================================
  Hits        21354    21354
- Misses      18569    18571       +2
- Partials     4266     4268       +2

Impacted Files
Coverage Δ

subsys/net/ip/net_if.c
62.46% <78.12%> (-0.2%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 330cbfa...451bd2d. Read the comment docs.


examples: provide an example for postgres plugin

Provide a full example on how the OpenTelemetry JS library can be used to instrument postgres and export them to Jaeger/Zipkin backend using OpenTelemetry Jaeger/Zipkin exporter.
https://github.com/open-telemetry/opentelemetry-js/tree/master/packages/opentelemetry-plugin-postgres/opentelemetry-plugin-pg

I can take this if it's still available. 👀

@xiao-lix idk if you have started working on this or not but the example I'm using in my local development of mysql should be fairly easy to swap out for the pg module.
https://github.com/dynatrace-oss-contrib/opentelemetry-js/tree/f99e1743fc1e8f1d9180289aea8da7d8c735b79f/examples/mysql

if you have not started working, I could easily modify my example to include pg as an option, the same way the examples allow Zipkin or jaeger as an option

@dyladan Hi, I've started working on it and almost done. May have different implementation with your example, please feel free to comment after I create the PR. Thanks. :)


.github/actions: tests that appimage work (currently doesn't)

Signed-off-by: Matthias Gatto<EMAIL_ADDRESS>

the PR doesn't work because github action seems to fail at initializing curses.


Add wordpress CMS

[Insert URL to the list here]
https://github.com/miziomon/awesome-wordpress
[Explain what this list is about and why it should be included here]
it's all about wordpress cms a huge cms based on php
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
WTFPL and Unlicense are not acceptable licenses.
If you use a license badge, it should be SVG, not PNG.
To verify that you've read all the guidelines, please add comment with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

I was surprised to see that there wasn't already a Wordpress awesome list - though there's one  which isn't included in the main list: this one by designwall. It looks like you aren't the original author of this list, and I presume it will require some changes on a forked version.
It may be a good idea to read over the requirements list to see if there's anything you (or the original author, seeing as they last updated two years ago) may have missed.

See also https://github.com/sindresorhus/awesome/pull/286

Duplicate of #286

The list has not been updated in more than a year.


[Cinder CSI] Race condition in volume deletion between attacher and provisioner

/kind bug
What happened:
When volumes are deleted. Both detaching and deletion are executed same time. This causes race condition where volume can be deleted before detacher found out that it was detached.
After this the detaching will never succeed and VolumeAttachment is forever try to detach the volume.
What you expected to happen:
If we are detaching volume and we do not find the volume it should be quite safe to assume that it isn't attached to the host VM.
How to reproduce it (as minimally and precisely as possible):
Create big deployment with multiple pods with volumes and delete them. Looping this should eventually cause this problem. Also if volume is long time in detaching state (over 1min timer that WaitDiskDetached is waiting) and is finally detached it might be that provisioner deletes it before attacher retries to detach it.
Anything else we need to know?:
One solution could be to catch 404 error from os.GetVolume(volumeID) and then assume that volume is detached if we get that error while detaching.
Environment:
csi-attacher:v0.3.0
csi-provisioner:v0.3.1
cinder-csi-plugin:v0.3.0

@mape90 is this specifically openstack related or do you think that this will happen for all CSI impls?
cc @adisky @flaper87

I think this is generic for all CSI plugins. As external-provisioner will not check if volume is still having VolumeAttachment with attached status.
It also seems that AWS EBS CSI has fixed this issue with the solution I proposed. As they just return success if volume isn't found:
if err == cloud.ErrNotFound {
	glog.V(4).Info("DeleteVolume: volume not found, returning with success")
	return &csi.DeleteVolumeResponse{}, nil
}

It most likely would be possible to implement something in external-provisioner level. So that it would check if the PV has VolumeAttachment. However then there is still the case when someone deleted manually the volume on backend. So simplest way to solve this would be to succeed always when we are deleting or detaching something and we can not find. As that is anycase the intended behavior.

@mape90 Delete should not be executed before attach complete
as mentioned here
https://github.com/kubernetes/community/blob/master/contributors/design-proposals/storage/container-storage-interface.md#attaching-and-detaching
"the PersistentVolume referenced by VolumeAttachment so the PV cannot be deleted while the volume is attached", so ideally delete should not happen before detach.
please log the issue in external-provisioner also.

I did not anything in cinder driver that should cause it, you should log issue to external-provisioner as well

The failure happens when detaching takes a long time and Attacher is polling in function 'WaitDiskDetached'. Then during one of those wait phases the volume might get detached and then provisioner might delete it before attacher checks it state again. After this all request to get any data about this volume will return ErrNotFound. And as current implementation do not handle this case it will fail forever.
What happens:
Delete PV
-> Attacher sends detach command to Openstack for this volume
-> Volume gets in detaching state
-> Attacher polls the volume state (gets that it is still in detaching state)
-> Attacher "sleeps"
-> Volume gets detached in backend
-> Provisioner tries to delete volume and succeed as volume is in available state. (Volume is deleted in backend)
-> Attacher wakes from sleep and tries to get volume state.
-> Fails as it gets ErrNotFound
-> Detaching will never succeed as the volume is already deleted form backend.

ok ,thanks for the detailed info
so the key cause here is provisioner and attacher do the job concurrently... and during sleep time the provisioner deleted the volume, that make sense but curious on Provisioner/Attacher  do the job at same time, anyway, will try to submit a fix and see folks' opinion


Using Qwertz Keyboard Ctrl + doesn't work

Version: 1.29.1 (user setup)
Commit: bc24f98b5f70467bc689abf41cc5550ca637088e
Date: 2018-11-15T19:13:36.375Z
Electron: 2.0.12
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Steps to Reproduce:

Press Ctrl + (or in German Strg +) keys.
The screen zooms in, instead of the Settings page opening up.

I'm not 100% positive it has to do with the Qwertz Keyboard.
Workaround: I've now reset the Keyboard Shortcut and it is working. I'll test this evening on my Win 10 Pro computer at home.
Scott

@smolinari What OS are you using? What keyboard layout are you using? What key are you pressing? The key located to the left of backspace?

Windows 1 Pro is the OS. Keyboard layout is the German Qwertz.
Pressing Ctrl and +. But it isn't located next to the backspace key on a Qwertz keyboard. It's just below it.
Scott

scott

@smolinari This is expected. Strg++ is bound out of the box to zoom in. Here I have an instance running without any keybinding customizations with the German keyboard layout:

Uh. Oh. My bad. I saw this in the menu.....

...and thought the command was "ctrl" and "+". I missed the comma there. 😊
Nevermind. Sorry for wasting your time.
Scott


Alert box not hiding if appropriate style file is not loaded.

Alert box not hiding if appropriate style file is not loaded.

default.css is mandatory

This is what I have and doesn't disappear:
import 'react-s-alert/dist/s-alert-default.css';
import 'react-s-alert/dist/s-alert-css-effects/scale.css';
<Alert effect='slide' html={true} offset={50} position='top-right' stack={ { limit: 3 } } timeout={5000} />

there is 'scale' in imports and 'slide' in configuration. This is probably why. There is probably some fallback needed for such situation.


refactor: move target/provider to server

Move target/provider to server
Description
Moved target and provider to server
/claim #297
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[x] I have performed a self-review of my own code
[ ] 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

Related Issue(s)
This PR addresses issue #297
Screenshots
If relevant, please add screenshots.
Notes
Please add any relevant notes if necessary.

@ezhil56x thanks for the PR!
Unfortunately, this was not the aim of the issue. We only wanted to move the CLI commands to the server scope.
This was done right in #324 and we'll be going with that.


Create project and items template

As this project avance we need to easily start a new project using the dotnet CLI or visual studio and also add items to the project.
This will made easy the day to day development.

This is not exactly a priority right now. But if you wanna do it, go right ahead. I'll close this as we're not going to do anything about it in the near future.


Cipher-Decipher Java Algorithm

ISSUE NUMBER
this does not have a issue number it is based on a earlier pull request which was closed.
https://github.com/codeIIEST/Algorithms/pull/77
SHORT DESCRIPTION
Now along with the code i have added readme file also which properly describes the problem and solution.
TESTING
For testing the solution you need:

JDK
Eclipse IDE or others

do i have to do something more on this pull request or it is okay . cause its showing tags enhancement and to be merged?

i have made another pull request #141 with latest revisions please review it. i am closing this pull request.


Add the metadata support for decode/encode the lyric.

The missing part found in https://github.com/jellyfin/jellyfin/pull/12543

@Shadowghost i'v notice this issue.
But I'm on vacation now so this issue will start at 9/14


Standard disaggregations missing on QA

This system message seems to be appearing on every result form on QA:

I've never seen this message before, and my understanding is that every single program and every single indicator is supposed to have the SADD standard disaggregations hard-wired in.
Some additional weirdness -- this is program 544 that has custom disaggregations set up in additional to standard. Note the system message with two types of disaggregation below, that seem to be lacking the styling Paul introduced with Huckleberry -- blue links instead of gray boxes, etc.

I'm going to split the styling issue onto a separate ticket (#1165), it's pretty straightfoward.
The other thing though…that one is really weird. Looks like @camgnostic might be able to shed some light on that:
[paul@Aphelocoma TolaActivity]$ git blame templates/indicators/results/result_form_disaggregation_fields.html | ack organizations
93ad20bfb (Cameron Mcfee 2018-12-20 01:29:06 -0800  36)         <p>{% trans "Standard disaggregations are entered by the administrator for the entire organizations.  If you are not seeing any here, please contact your system administrator." %}</p>

Testing this on QA, I notice an errant character:

…looks like Cameron fixed this in 1942771

Deployment Verification

[x] Confirmed “Ready for Deploy” status
[x] No longer see errant "/" as reported
[x] Reported error no longe occurs as originally pictured/written


DA-BEAT DAC improvements

Resolves L2B-6727
Resolves L2B-7055
Maybe it will Resolve L2B-6932
And definitely will Resolve L2B-7084

nova causes verification check to fail - I'll re-run it/change it in the meantime


Some table cleanup

The main thing here is the compaction assert under constants.verify. They might not be worth it in terms of making CI even slower. But I'm not entirely sure how much of a difference it will be.

Tagging @matklad


Step 8 wording accuracy

Under "Run the Notebook" Step 8, the menu option is "File > Close and Halt" not "File > Halt and close"

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

ID: 39b2c82b-3624-18ac-de45-446049ca11c1
Version Independent ID: 9f5f6ed4-c8d0-2010-8463-07c2e51b6eca
Content: Create and share a Jupyter notebook on Azure
Content Source: articles/notebooks/quickstart-create-share-jupyter-notebook.md
Service: notebooks
GitHub Login: @kraigb
Microsoft Alias: kraigb

Thanks for pointing that out! I'll get it fixed.
BTW, this is something that you could also fix directly using the Edit button the top right of the page above the heading. I've been lobbying to make command that more visible down by the Issues. So let me know if you'd like to do the honors and get some contribution credits. :)

Sure, I can make the edit. I just wasn't sure what the expected protocol
was for edits that didn't have issues.
--Steve
On Tue, Mar 5, 2019 at 9:41 AM Kraig Brockschmidt<EMAIL_ADDRESS>wrote:

Thanks for pointing that out! I'll get it fixed.
BTW, this is something that you could also fix directly using the Edit
button the top right of the page above the heading. I've been lobbying to
make command that more visible down by the Issues. So let me know if you'd
like to do the honors and get some contribution credits. :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/26267#issuecomment-469728368,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARydUAIQ1-t68yJWLUn_R8y_eCA_VJcqks5vTpAegaJpZM4be2mG
.

You can just make edits whenever you want. It generates a PR that I then review and merge.

This is handled in https://github.com/MicrosoftDocs/azure-docs/pull/26271 .
#please-close


Vendor k/* and c-r dependencies

How to categorize this PR?

/area open-source
/kind task
What this PR does / why we need it:
Vendors<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and adapts to the breaking / most notable changes (see https://github.com/gardener/gardener/issues/4174#issuecomment-862098004).
Which issue(s) this PR fixes:
Main part of #4174, a few optional cleanups will follow in dedicated PRs to keep this one limited to the minimum scope.
Special notes for your reviewer:
To ease the review, changes are split into dedicated commits, each targeting "one step" / "one adaption" to an upstream change.
Commits marked with [automated] are results of make * with exception of minimal manual changes described in the commit message.
/squash
Release note:

The following golang dependencies have been upgraded, please consult the upstream release notes and [this note](https://github.com/gardener/gardener/issues/4174#issuecomment-862098004) for guidance on upgrading your golang dependencies when vendoring this gardener version:
- `k8s.io/*` to `v0.21.1`
- `sigs.k8s.io/*` to `v0.9.0`

Thanks for the fast review, @rfranzke! ❤


generate custom js test code

Summary
I would like to develop a vs code plugin using rust. Therefore I'm currently in the process of implementing a lib with bindings to corresponding vs-code API types and functions. Now, I would like to test APIs against a vs code instance. Therefore I would like to load vs-code and types in the javascript that executes before my wasm tests are run.
So my question is: Is there a way to customize test execution javascript?

At this time I don't think that this is supported, no.


http://issuestats.com is no longer up

issuestats does not seem to be running, the site isn't up and badges are broken

@hstove any updates on this? Our Shields.io badges for this service are unhappy at the moment! 😄

any news?


oldUI - save only enabled services on clicking Save in Configure and Install section

https://github.com/Shippable/pm/issues/10092

verified on RC, old UI does not crash while updating replica counts of services.
closing


Getting exception at DryIoc.Interpreter.TryInterpretAndUnwrapContainerException when I try to intergrate Shiny with Prism

Component/Nuget
Other (Message Bus, Startup Task, NPC Persistence)
What operating system(s) are effected?

[ ] iOS 12
[ ] iOS 13
[ ] iOS 14
[ ] iOS 15
[ ] Mac Catalyst
[ ] Android 8
[ ] Android 9
[ ] Android 10
[ ] Android 11
[X] Android 12

What platform(s) are effected?

[ ] MAUI
[ ] Xamarin Native
[X] Xamarin Forms

Steps To Reproduce

Add Shiny to your project
Try to integrate Prism with Shiny see Integrate with Prism
See the detailed code below.

Expected Behavior
The app should run.
Actual Behavior
App is crashing.The app
Exception or Log output

Code Sample
It's been 2 weeks since I have been trying to add Shiny to my application. It's an excellent library providing so many great features out of the box. I am stuck integrating my app with Prism.  I do not know if it's a bug or something wrong with my app.
There is not much help on the internet most of the blog posts about integrating Shiny with Prism are outdated. There is only one helpful sample Integrate Shiny with Prism
I am using:
DryIoc.Microsoft.DependencyInjection 5.1.0
Prism.DryIoc.Forms 8.1.97
Prism.Forms.Extended 8.0.62
and latest Shiny libraries.
My other packages:
ProjectPackages.txt
My main activity:
[assembly: ShinyApplication(
    ShinyStartupTypeName = "SampleApp.Startup",
    XamarinFormsAppTypeName = "SampleApp.App"
)]
namespace SampleApp.Droid
{
    [Activity(Label = "Sample", Icon = "@mipmap/ic_launcher", Exported = true, Theme = "@style/MainTheme", ConfigurationChanges = ConfigChanges.ScreenSize | ConfigChanges.Orientation)]

    public partial class MainActivity : global::Xamarin.Forms.Platform.Android.FormsAppCompatActivity, IMessageSender
    {

        protected override async void OnCreate(Bundle savedInstanceState)
        {

            TabLayoutResource = Resource.Layout.Tabbar;
            ToolbarResource = Resource.Layout.Toolbar;

            base.OnCreate(savedInstanceState);
            LoadApplication(new App(new AndroidInitializer()));
        }

        protected override void OnActivityResult(int requestCode, Result resultCode, Intent data)
        {

            base.OnActivityResult(requestCode, resultCode, data);
            this.ShinyOnActivityResult(requestCode, resultCode, data);
        }

        public override void OnRequestPermissionsResult(int requestCode, string[] permissions, Android.Content.PM.Permission[] grantResults)
        {
            Xamarin.Essentials.Platform.OnRequestPermissionsResult(requestCode, permissions, grantResults);

            base.OnRequestPermissionsResult(requestCode, permissions, grantResults);
            this.ShinyOnRequestPermissionsResult(requestCode, permissions, grantResults);
        }
    }

    public class AndroidInitializer : IPlatformInitializer
    {
        public void RegisterTypes(IContainerRegistry containerRegistry)
        {
            // Register any platform specific implementations
        }
    }
}

MainApplication:
namespace SampleApp.Droid
{
    [Application]
    public partial class MainApplication : Application, Application.IActivityLifecycleCallbacks
    {
        public MainApplication(IntPtr handle, JniHandleOwnership transer)
            : base(handle, transer)
        {
        }

        public override void OnCreate()
        {
            this.ShinyOnCreate(new Startup());
            base.OnCreate();
            RegisterActivityLifecycleCallbacks(this);

            //A great place to initialize Xamarin.Insights and Dependency Services!
        }
}
}

Startup class:
using System;
using DryIoc.Microsoft.DependencyInjection;
using Microsoft.Extensions.DependencyInjection;
using Prism.DryIoc;
using Prism.Ioc;
using Shiny;
    public class Startup : ShinyStartup
    {

        public override void ConfigureServices(IServiceCollection services, IPlatform platform)
        {
            services.UseGeofencing<GeofenceDelegate>();
            services.UseNotifications();
            services.UseGps();
            Console.WriteLine("Shiny Added");
        }

        public override IServiceProvider CreateServiceProvider(IServiceCollection services)
        {
            ContainerLocator.SetContainerExtension(() => new DryIocContainerExtension());
            var container = Prism.Ioc.ContainerLocator.Container.GetContainer();
            DryIocAdapter.Populate(container, services);
            return container.GetServiceProvider();
        }
   }

I also added in the App.cs class:
    public partial class App : Prism.DryIoc.PrismApplication
Here is how I am registering types in App.cs:
 protected override void RegisterTypes(IContainerRegistry containerRegistry)
        {

            containerRegistry.RegisterForNavigation<NotificationArea, NotificationViewModel>();
            containerRegistry.RegisterForNavigation<ServerRegion>();

}

Code of Conduct

[X] My reproducible sample is NOT FROM THE SHINY SAMPLES REPOSITORY!  If you file an issue that says 'use shiny sample', YOU WILL BE BANNED FROM THE SHINY REPOS.  Read the code of conduct for why we care about this!
[X] I am using the latest stable version from nuget (sponsors can discuss previews in discord)
[X] I agree to follow this project's Code of Conduct

This is a 3rd party integration and has nothing to do with this library.  I use prism, shiny, & dryioc with every single app I write without issue.
There are samples here: https://github.com/shinyorg/samples & Shiny Framework which brings Prism+Shiny together: https://github.com/shinyorg/framework
Also, if you want help with anything in the future, you must supply a FULL REPRODUCIBLE sample otherwise your issue will be closed without comment.

No reproducible sample has been supplied and based on the code snippet provided as well as the project references, there is obviously a lot missing.


S3Object.store $stdin

Hey,
I've been trying to build a tool that allows me to put some data from STDIN into S3, and I have hit a brick wall with your S3 library. When I try to call AWS::S3::S3Object.store(path, $stdin, bucket) I get an exception thrown...
/Library/Ruby/Gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/connection.rb:41:in `request': undefined method `size' for #<IO:0x106464bd0> (NoMethodError)
	from /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/net/http.rb:543:in `start'
	from /Library/Ruby/Gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/connection.rb:52:in `request'
	from /Library/Ruby/Gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:69:in `request'
	from /Library/Ruby/Gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/base.rb:88:in `put'
	from /Library/Ruby/Gems/1.8/gems/aws-s3-0.6.2/lib/aws/s3/object.rb:241:in `store'
	from ./s3pipe.rb:115

Everything works great if I call $stdin.read however the data i'm piping into my ruby program is upwards of 2GB, and i'm running this on low memory machines.
By the looks of things, your relying on a few methods that are only defined in the File class, and not handling raw IO objects. It would be aweseomeee if you could fix this bug :-)! I can't wait to open source this little ruby file i'm writing!
Thanks.

@tarnfeld, as a work-around, check out the aws-sdk gem.
http://docs.amazonwebservices.com/AWSRubySDK/latest/AWS/S3/S3Object.html#multipart_upload-instance_method
Unfortunately, the aws-sdk gem currently doesn't support unbuffered download from s3. I ended up having to use both aws-s3 and aws-sdk gems when I made my s3stream gem. The namespace collision was not fun.
https://github.com/kindkid/s3stream


George format fixes

@devoncarew
Fixing formatting issues.

Lgtm
On Jul 14, 2015 11:35 AM, "George He"<EMAIL_ADDRESS>wrote:

@devoncarew https://github.com/devoncarew
Fixing formatting issues.
You can view, comment on, or merge this pull request online at:
https://github.com/dart-lang/dart-pad/pull/576
Commit Summary

Export dialog word fix
Formatter on dialogs, embed, mobile.dart

File Changes

M lib/dialogs.dart
https://github.com/dart-lang/dart-pad/pull/576/files#diff-0 (35)
M lib/embed/embed.dart
https://github.com/dart-lang/dart-pad/pull/576/files#diff-1 (21)
M lib/mobile/mobile.dart
https://github.com/dart-lang/dart-pad/pull/576/files#diff-2 (7)

Patch Links:

https://github.com/dart-lang/dart-pad/pull/576.patch
https://github.com/dart-lang/dart-pad/pull/576.diff

—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/dart-pad/pull/576.

Also added the dialog changes in this PR.

lgtm

Merging


fix(Subject): throw ObjectUnsubscribedError when unsubecribed …

This PR tries to close #859, now Subject throws ObjectUnsubscribedError if it's unsubscribed. Updated operator behavior and test cases also to not emit after subject completion(error, complete, unsub)

PR's updated to add test coverage for changed behavior.

LGTM... merged as of 64bf6b1. Thanks @kwonoj


zipl: update stage3 objcopy command for gcc9

The objcopy command for stage3.bin needs to take the new rodata section into account.
See also PR #60.
Signed-off-by: Dan Horák<EMAIL_ADDRESS>

Thanks for the contribution. Already integrated internally.


should-accept-drop appears to fires more times than expected

I've been building a "lifecycle" demo to fully understand how things work in Smooth DnD. (I'll submit this as a PR when done)
If I start with 3 columns of draggables, then drag item 1 from column 1 to column 3:

I get the following lifecycle events:
--> MOUSEDOWN + DRAG

    get-child-payload

3 x should-accept-drop

    should-accept-drop
    drag-start
    should-accept-drop
    drag-start
    should-accept-drop
    drag-start

    drag-enter

--> MOUSE MOVE

    drag-leave
    drag-enter
    drag-leave
    drag-enter

--> MOUSEUP

    should-animate-drop

    should-accept-drop
    drag-end
    should-accept-drop
    drag-end
    should-accept-drop
    drag-end

3 x drop

The docs for should-accept-dropstate it is: "the function to be called by all containers before drag starts to determine the containers to which the drop is possible".
Therefore, I don't understand why there appear to be two very similar executions of should-accept-drop at the start of the drag. The wording above suggests it should be the second set, though the first set seems more obvious:

the 3 x should-accept-drops before all drag-starts
the extra should-accept-drops before each of the drag-starts

Then, there is this additional set at the end of the drag:

the extra should-accept-drops before each of the drag-ends

I have the latest master, and have installed all the latest dependencies.
I've forked the repo and the demo is here:

https://github.com/davestewart/vue-smooth-dnd/blob/feature/events-demo/src/demo/pages/events.vue

Is this expected?
Thanks!

Hey Dave,
The life cycle demo idea sounds great! Thanks for the all the effort you made, really appreciate it!
For the question: Yes should-accept-drop is called several times during the drag and drop process just like you said. For instance, before the drag-end is it called to get the value of the 'willAcceptDrop' parameter to pass to drag-end function. So I agree that it looks a bit weird to be called several times but it should not cause any bugs since should-accept-drop function is just has to be a pure function that has no side effects. Or may be I have to call it once and cache it.
PS: Its summer season so I can't spent much time to reply issues or maintenance these days. Probably I will start to go over them starting from next month. Sorry for that.

Thanks for the all the effort you made, really appreciate it!

Hey, no worries! It's a great library, I really enjoy the final result; everything looks and feels so great, so I am invested in understanding it as well as I can.
I know I've created a lot of tickets recently, I'd actually like to be able to contribute to the core at some point, but I recognise there are of course ramifications for the dependent libraries.
I will make 2 PRs once I nail this:

the lifecycle demo itself
a docs update (to the Vue version of the lib only; you may want to disseminate to the other versions)

One other thing I could do if you like, and that is rewrite the Vue Demo to use Vue Router; this way the URL would update as you change demos, making it easier to share links and develop in general, as you always stay on the same demo.
Let me know if that's something you're interested in.
:D

By the way, how does the library know WHICH of the should-accept-drop calls to recognise?
That is, I could return a different result from each, but it seems that one of them has to win out.
For example, what happens if I return true from the first, false from the second, and skipped the third?

Each should-accept-drop corresponds to, in your example, a given column of draggables.  It's designed so you can return a different value from each, because each column might have different criteria for rejecting potential drops.
Take the Trello example for instance, and imagine that you cannot have duplicate items for a given card.  That would mean when you drag an item each one of the cards (columns) should fire their own should-accept-drop and return potentially a different value depending on whether or not the item is already present for them.
So going back to your hypotethical...if you return true from first, false from second and skipped the third you would be able to drop your dragged item on the first and third column (assuming by skip you mean you don't supply a should-accept-drop function).

Great work! Closing the issue


Macro Arguments Cannot Be Opcodes

In the Huff by Example section of the docs under Macros and Functions > Macros > Macro Arguments it is mentioned that "Macro arguments may be one of: label, opcode, literal, or a constant" however it doesn't currently seem to be possible to use opcodes as macro arguments (as of huffc v0.2.0, latest version at time of writing).
Specifically the lexer module of the Huff compiler does not recognize opcodes outside of the body of macros / functions at the moment (lexer reference). Personally I haven't dived deep enough into the codegen module so I'm unsure if there's any logic to support opcode args there already.
While this could be quite a useful feature in certain instances, it doesn't seem to be possible just yet.

Thanks for pointing this out! @abigger87 fixed this thismorning in https://github.com/huff-language/huff-rs/pull/188, I also fixed constants as macro args in https://github.com/huff-language/huff-rs/pull/190. Should be in tonight's nightly build, or for now, can update to the stage branch with huffup -b stage


Generalize ParametricType and use it for ObjectCollections

ObjectCollection subclasses are fairly similar to the checked
collections found in common.checked, and the reflection infrastructure
could benefit from a more specific collection type specification in
fields.
This also adds limited support for forward references in type arguments.

Generic ObjectList is 🔥🔥🔥


Refresh token - refreshApi with a type issue and console error

Describe the bug
Using the refresh token in refreshApi.ts like indicated in the documentation and I get an error in the console.
Also TS is not happy about refreshApiCallback type:
Type '({ refreshToken }: { authToken?: string | undefined; authTokenExpireAt?: Date | undefined; refreshToken?: string | undefined; refreshTokenExpiresAt?: Date | undefined; authUserState: AuthStateUserObject | null; }) => void' is not assignable to type 'refreshTokenCallback'.
  Type 'void' is not assignable to type 'Promise<RefreshTokenCallbackResponse>'.ts(2322)
types.d.ts(95, 5): The expected type comes from property 'refreshApiCallback' which is declared here on type 'createRefreshParamInterface'

To Reproduce
Implement the refresh api like this -> https://authkit.arkadip.dev/refreshtoken/#api-builder-example
Screenshots

Desktop (please complete the following information):

OS: mac OS 12.6
Browser chrome
Version 108

Failure Logs
Uncaught TypeError: Cannot read properties of undefined (reading 'then')
    at Object.current (AuthProvider.tsx:55:16)
    at tick (hooks.ts:40:38)

Same issue here.

A fix for the Cannot read properties of undefined (reading 'then'):
Return the axios with your .post() and .then/ .catch() instance in the refreshApiCallBack function.
`refreshApiCallback: ({
authToken,
authTokenExpireAt,
refreshToken,
refreshTokenExpiresAt,
authUserState,
}) => {
let promise = {
isSuccess: false,
newAuthToken: authToken,
newAuthTokenExpireIn: authTokenExpireAt,
newRefreshToken: refreshToken,
newRefreshTokenExpiresIn: refreshTokenExpiresAt,
newAuthUserState: authUserState,
};
return <your axios instance>.post("/token/refresh")...`

PS. You still need to return the result in the .then and .catch clause:
`return {
     isSuccess = true,
     ...
  }`

Fixing the documentation would already be sufficient to "fix" the issue, since there is only a return statement missing at the beginning of the arrow-function (before the axios.post...) To be more precise: Changing the documentation from
{refreshApiCallback: (
    {   // arguments
      authToken,
      authTokenExpireAt,
      refreshToken,
      refreshTokenExpiresAt,
      authUserState
    }) => {
    axios.post('/api/refresh',
      {
        refreshToken: refreshToken,
        oldAuthToken: authToken
      }
    ).then(({data})=>{
      return {
        // As the request is successful, we are passing new tokens.
        isSuccess: true,  // For successful network request isSuccess is true
        newAuthToken: data.newAuthToken,
        newAuthTokenExpireIn: data.newAuthTokenExpireIn
        // You can also add new refresh token ad new user state
      }
    }).catch((e)=>{
      console.error(e)
      return{
        // As the request is unsuccessful, we are just passing the isSuccess.
        isSuccess:false // For unsuccessful network request isSuccess is false
      }
    })
  }
}

to
{refreshApiCallback: (
    {   // arguments
      authToken,
      authTokenExpireAt,
      refreshToken,
      refreshTokenExpiresAt,
      authUserState
    }) => {
    return axios.post('/api/refresh',
      {
        refreshToken: refreshToken,
        oldAuthToken: authToken
      }
    ).then(({data})=>{
      return {
        // As the request is successful, we are passing new tokens.
        isSuccess: true,  // For successful network request isSuccess is true
        newAuthToken: data.newAuthToken,
        newAuthTokenExpireIn: data.newAuthTokenExpireIn
        // You can also add new refresh token ad new user state
      }
    }).catch((e)=>{
      console.error(e)
      return{
        // As the request is unsuccessful, we are just passing the isSuccess.
        isSuccess:false // For unsuccessful network request isSuccess is false
      }
    })
  }
}

would already fix this and close the issue.


[docs] Clarification for some MacOS users using install_ddev.sh and missing /usr/local/bin

The Issue
Surprising script failure on a fresh MacOS install.
How This PR Solves The Issue
Provides guidance on this issue.
Manual Testing Instructions
n/a
Automated Testing Overview
Documentation change only.
Related Issue Link(s)
n/a
Release/Deployment Notes
n/a

Thanks so much for helping us understand @iparr , please see if

https://github.com/ddev/ddev/pull/4752

would have solved it for you.


Reorder opentelemetry-collector HPA metrics

A current issue between ArgoCD (https://github.com/argoproj/argo-cd/issues/1079) and Kubernetes (https://github.com/kubernetes/kubernetes/issues/74099) makes the HPA stay constantly out of sync. This affects Gitops pipelines when both memory and CPU metrics are used to autoscale the deployment.
This change reorders HPA metrics to make sure that they remain in the order that the Kubernetes HPA controller currently expects them to be.

@danielgblanco, thanks for the contribution!


修复VID/PID匹配逻辑

原来逻辑是匹配VID或者PID即返回，应该需要同时匹配吧？

Summary by CodeRabbit

Bug Fixes

Improved error handling for freeing device addresses.

Refactor

Simplified logic for matching USB device IDs, enhancing clarity and potential performance.

匹配的是两者都不满足

恩，这边应该是 || 的关系，写错了

感谢pr


PasswordVisible Property of PasswordTextBox & its zh_CN translation

this allowed PasswordTextBox to be switched to Visible mode(seems like TextBox) and also can be switched back easily

@ColinTree If you can address the requested changes, we should be able to put this into the upcoming components release.

I would like to keep password text box component as a completely different component.

@moliata it is however not another individual textbox, it is changed by a property.

Yea that's what I meant, I would like to keep PasswordTextBox component

@ewpatton Done.

@ewpatton I tested on a series of devices including the old official appinvenor emulator, it should works now with an extra TYPE_CLASS_TEXT

@ColinTree Thanks. I'll take a look.

I'm still having trouble with the most recent change and the emulator. Try your build with this aia. If I click on the "One true" it will not change to visible, but if I hit "One false" then "One true" it will. I did find that if I moved the PasswordVisible(false); statement in the constructor to the end, it worked as one would expect. It might be an interaction with the setTransformationMethod call. I would recommend moving the call to PasswordVisible to the end of the constructor.

@ewpatton Looks good to me now, at least I tested on more devices and no unexpected situations (with your aia).

LGTM. Thanks @ColinTree.


python dump if called without parameter

Calling py2pack 0.8.4 w/o parameter:
docb@X1E:~/buildservice> py2pack
Traceback (most recent call last):
File "/usr/bin/py2pack", line 10, in
sys.exit(main())
File "/usr/lib/python3.8/site-packages/py2pack/init.py", line 350, in main
args.func(args)
AttributeError: 'Namespace' object has no attribute 'func'
...if help is displayed, this would be much appreciated

Duplicate of https://github.com/openSUSE/py2pack/issues/121 and already fixed in master

I pushed a 0.8.5 tag and this will be available soon on pypi (and openSUSE Tumbleweed afterwards)


fix: fixed dependecy checksum for grpc-middleware

Changes
I was getting on make build
go: verifying<EMAIL_ADDRESS>checksum mismatch
    downloaded: h1:BWIsLfhgKhV5g/oF34aRjniBHLTZe5DNekSjbAjIS6c=
    go.sum:     h1:Iju5GlWwrvL6UBg4zJJt3btmonfrMlCDdsejg4CZE7c=
Makefile:183: recipe for target 'go-mod-tidy' failed

It looks like the checksum has changed so I updated it if that is ok?
Verification
Now make build passes

hm.. It's something in my setup/old deps.. closing since it works in clean docker image

So how you fixed that on your setup ? Looks like others have similar problem

unset GOPATH pass


New document to track the progress of each app

Type of change

Documentation

Changes
The following changes have been made:

Overview
Initial structure for apps

Related Issues
Closes #207

Would it be possible to have the info for each dapp, game, tutorial inside of a dropdown? Imo it would make it easier to navigate.

For plain markdown, no.
For advanced markdown that uses HTML tags, yes.
I was hoping something like this would exist. It doesn't solve the issue of plain text being a pain to work with and in-fact it will make it worse but that's for us to deal with and not a user. I will look into making these changes soon.


[NOT FOR REVIEW] test 1.0 kind tests

Signed-off-by: Zhecheng Li<EMAIL_ADDRESS>

Codecov Report

Merging #2402 (bc11628) into release-1.0 (b14ed7d) will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release-1.0    #2402   +/-   ##
============================================
  Coverage        41.38%   41.38%
============================================
  Files              131      131
  Lines            16433    16433
============================================
  Hits              6801     6801
  Misses            9050     9050
  Partials           582      582

Flag
Coverage Δ

unit-tests
41.38% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apiserver/storage/ram/store.go
77.44% <0.00%> (-1.51%)
:arrow_down:

pkg/apiserver/handlers/endpoint/handler.go
70.58% <0.00%> (+11.76%)
:arrow_up:


Add request header changes for customized code

Verified with e2e tests

Does this affect recorded tests?

Does this affect recorded tests?

you're right it does. Let me add it quickly


XCode 6.4 Support:Nonnull Exports Outside of Class

Problem:
Extern strings cause issues with sdk's before xcode 7.
Solution:
Leverage NS_ASSUME_NONNULL method to provide support

Pretty embarrassed by this, but one of our dependencies is still using Xcode 6.4. We're in the process of updating, but are currently delayed in migrating our CodeCoverage tools.
Seeing if this could be considered to provide compatible support with Xcode 6.4?

Yeah that's fine.
Thanks!

This is now released as part of version 1.2.3. Thanks for the heads up and the pull request!


build metrics count build-watch requests, not builds

The builds metrics, such as BUILDS_INPROGRESS and BUILD_COUNT/BUILD_TIME, do not count actual builds. They track requests to start or watch a build. To be precise, this metric does not measure the number of builds, but rather the number of attempts to launch a repo that has not been built. 100s of requests for one repo which is already in the middle of a build will register as 100s of 'new builds' in this metric. It's still a useful metric, especially the inprogress gauge, in that it tells us how many users are waiting for a build to complete. But it doesn't tell us if that's 1 actual build request or 100.
This means that our current total builds metric in grafana doesn't track new builds at all, it tracks requests to watch a build. Using the incident last week as an example, we have this suspected peak of builds:

However, because those are more precisely requests to watch a build, adding a direct query to replacing the build query with one that tracks actual new build pods, we get:
sum(kube_pod_status_phase{pod=~"build-.*"})

producing the very different blue line here, which tells a very different story:

(note: build_time is a lagging indicator, as it is updated when the build completes or fails, not when the build starts).
We should probably try to move our build metrics to a place in the code that tracks the actual builds, rather than the requests to watch them. It may still be useful to keep the BUILDS_INPROGRESS metric under a different name, which tells us how many users are waiting on a build.

At some point we had a problem that lots and lots of people requested a build of a repository which took a while to build. They then all ended up watching the build which each used up one thread in the thread pool. As a result no other repos could be built. I think we fixed this, but not sure. However the problem hasn't happened in a long time either :-/
Point being that this is a reason to continue to track the "builds being watched" metric and another failure mode that I thought is obscure enough to post here to bump it in people's minds.


issue about rnn_train.py

Hi, thanks for your repo. I have a question about training RNN model. In rnn_train.py, there is a parameter name n_epoch=10, how should I change this epoch number if I use my own datasets? I found it's totally different if I set this parameter to 5,10,20. Should I save multiple models and test them all to get the best result?

Yes, n_epoch is a hyperparameter. You need to decide the optimum number of epochs for which the model should train (avoiding over/underfitting)


CORS cloudfront/s3 caching

I've encountered an issue today where:
1- My first request to my css file on cloudfront (from head) would get cached.
2- The second (CORS) request to my css from this library would still get the
same cached response even though there's a valid origin header in the request.
3- That would result in Safari denying the CORS because Cloudfront won't
return the proper headers.
I hacked it by adding changing the url in the getCors function to:
url = url + "?rng=" Math.random()

It works like a charm in my case because I needed to make sure that the CORS request wouldn't receive a cached response.
Here's the issue I'm talking about:
https://forums.aws.amazon.com/thread.jspa?messageID=555417&#555417
http://stackoverflow.com/questions/12498704/cached-non-cors-response-conflicts-with-new-cors-request
I would like to transform this issue into a PR, but I think it's best that I get your opinion on how you would want to implement the fix first.
Thanks.

This should definitely be a configurable thing. importCrossOriginLinks() is the embedded utility that loads cross origin content automatically. I guess we could make initialize() accept an optional argument initOptions.loadCrossOriginContent which would be a function that has the same signature as getCors() and take over the loading entirely. This is the most flexible extension, as you're no longer limited to loading data via HTTP/S.
Does that sound reasonable to you?

sounds good, I'll try to submit a PR this weekend.


Deobfuscator

https://github.com/Fadi002/BlankOBF-deobfuscator

Might be patched as of 10/2/2023

Might be patched as of 10/2/2023

he ddn't even update his obfuscator lol

Yeah my bad lol, someone sent me a file with this github repo and I wanted to read in and the obfuscation in the file looked completely different from the one this gives now that I run it

Might be patched as of 10/2/2023

he ddn't even update his obfuscator lol

Yeah my bad lol, someone sent me a file with this github repo and I wanted to read in and the obfuscation in the file looked completely different from the one this gives now that I run it


Minor speed-up for sum sq dev when jit compiled (slower if not)

Morning - what do you reckon on this?  It's a little faster when jit compiled and skips the abs step since the diff is squared anyway.  (But it's slower if not jit compiled.)  Just a thought.

Awesome, thanks!
Definitely worth having a discussion about this - if it's faster jitted then we should include it.
My plan for the project is to have multiple versions of functions depending on accuracy/performance characteristics, so if you've sped it up that's great and we should merge.
Could you add a notebook/markdown file showing the performance differences over a range of data sizes, say 10-1e8?
i have a couple of comments on the code as well, but nothing major,
Thanks!

Top stuff, yep - let's chew it over - I have a few questions jotted down & will follow up next week.  Loving the OLS stuff btw :)

Hey, so I just took out the abs from the original fn.  Will create branch my fork and put in the possible optimised version with some evidence on speed-up and ping you & some other ideas

I added a notebook to one of my branches showing evidence of the possible speedup - lemme know what you think:
https://github.com/rjenc29/fastats/blob/projects/fastats/notebooks/Experimental ideas.ipynb

Perfect, that notebook says it all, thanks!
Perhaps stick the notebook as 'sum_sq_dev' in a _notebooks folder under fastats.maths ?
Alternatively we could create a top level notebooks folder with the same hierarchy as the code.

@rjenc29 do you want to add the notebook to this commit and we can merge this one as well?


support multiple flavor of notebooks

This PR fixes #12157
This enables @SQLvariant to contribute PowerShell notebooks for our deployment scenarios.
this is only enabled for configuration + notebook based dialog deployment targets, since wizards are more complicated and even generate python code cell and add to notebook at runtime.
This is how it looks at runtime, a notebook type selector is automatically added to the end of the dialog if multiple notebooks are provided for that deployment option.

@SQLvariant These are all the deployment options:

you can contribute PowerShell notebooks for the follow scenarios:

SQL Server container image - 2 notebooks: https://github.com/microsoft/azuredatastudio/blob/main/extensions/resource-deployment/package.json#L96 and https://github.com/microsoft/azuredatastudio/blob/main/extensions/resource-deployment/package.json#L147
Azure SQL Edge - 5 notebooks: https://github.com/microsoft/azuredatastudio/blob/main/extensions/asde-deployment/package.json#L62, all the notebooks in the extension can have PS version

How to provide additional notebooks:
Replace the notebook value in the package.json
              "notebook": "./notebooks/edge/deploy-sql-edge-local.ipynb",

with
              "notebook": [
                {
                  "type": "Python",
                  "path": "./notebooks/edge/deploy-sql-edge-local.ipynb"
                },
                {
                  "type": "Powershell",
                  "path": "./notebooks/edge/deploy-sql-edge-local-PS.ipynb"
                }
              ],

Pull Request Test Coverage Report for Build 240281830

3 of 13 (23.08%)  changed or added relevant lines in 2 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.01%) to 39.09%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/resource-deployment/src/services/resourceTypeService.ts
1
4
25.0%

extensions/resource-deployment/src/ui/deploymentInputDialog.ts
2
9
22.22%

Files with Coverage Reduction
New Missed Lines
%

extensions/resource-deployment/src/ui/deploymentInputDialog.ts
2
13.92%

Totals

Change from base Build 240274353:
0.01%

Covered Lines:
19013

Relevant Lines:
44421

💛  - Coveralls

I am curious about the business need for multiple notebooks for the same deployment sicenario. Is this because we expect the end users to understand and extend the notebooks as per their own need?

@ranasaria that is correct.  The way the Notebooks currently come out, they look like incomprehensible jibberish to many customers.  If they get an error, they might have no idea where to start troubleshooting.

@SQLVariant, I think type may not be best way to distinguish onenotebook from another. I think a short description string might be more appropriate.


virt-manager does not display device information from pci.ids file

Describe the bug
When viewing the list of PCI devices in my system, virt-manager only displays the bus/device/function numbers of each. It does not give any descriptive information, which is usually pulled from /usr/share/misc/pci.ids or similar
Steps To Reproduce

Open virt-manager
File -> New Virtual Machine
Continue through VM creation steps. The details are not necessary - you do not need to boot the VM
View hardware details for the virtual machine
Click "Add Hardware"
Click "PCI Host Device"

Expected behavior
PCI devices in my system are listed with bus/device/function numbers as well as vendor / product description.
Screenshots
What the UI should look like:

What it looks like on NixOS:

Additional context
Following nixos-unstable channel
virt-manager-4.1.0
Notify maintainers
@qknight @offline @fpletz @globin @K900
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 6.2.6, NixOS, 23.05 (Stoat), 23.05pre464727.ac718d02867`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - channels(root): `"nixos"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Closing since it sounds like this was fixed by the merge of #221885. Happy to reopen if I'm mistaken.