How to autogenerate route viz on maps

Hi, thanks for your work in this area -- super useful!
I'm wondering if you could point me to the code for generating route annotated maps like in the longest6 description page here.
Thanks!

https://github.com/autonomousvision/transfuser/tree/2022/tools/dataset


Add buildExtras and projectExtras

Fixes #2532
This adds support to generate synthetic subprojects from an auto plugin.
In addition, a method called projectOrigin is added to distinguish Organic, BuildExtra, ProjectExtra, and GenericRoot.
To generate subprojects, override buildExtras
method as follows:
import sbt._
import Keys._

object BuildExtrasPlugin extends AutoPlugin {
  override def buildExtras: Seq[Project] =
    List("foo", "bar", "baz") map generateProject

  def generateProject(id: String): Project =
    Project(id, file(id)).
      settings(
        name := id
      )
}

Subprojects may also be derived from an existing subproject
by overriding projectExtras.
import sbt._
import Keys._

object ProjectExtrasPlugin extends AutoPlugin {
  // Enable this plugin by default
  override def requires: Plugins = sbt.plugins.CorePlugin
  override def trigger = allRequirements

  override def projectExtras(proj: ProjectDefinition[_]): Seq[Project] =
    // Make sure to exclude project extras to avoid recursive generation
    if (proj.projectOrigin != ProjectOrigin.ProjectExtra) {
      val id = proj.id + "1"
      Seq(
        Project(id, file(id)).
          enablePlugins(DatabasePlugin)
      )
    }
    else Nil
}

/review @dwijnand, @Duhemm

Wow knocking them out the park this week, awesome.
I'm only concerned with the name buildExtras: for builds where all the projecrs are programmatically generated it sounds a bit weird. So I was thinking perhaps just "projects" (like we have projectSettings, not extraProjectSettings).
projectExtras I'm not sure of either, but I don't have any better suggestions.

So I was thinking perhaps just "projects" (like we have projectSettings, not extraProjectSettings).

If I call it projects that would imply both the organic one and synthetic ones.
If I call it syntethicProjects or extras that would imply both the build-level and project-level.

buildExtras I think has a nice symmetry with buildSettings and easy to grasp what it would do.

I see the organic/synthetic project argument. But what's a project-level
project?
On Sat, 27 Aug 2016, 12:32 eugene yokota<EMAIL_ADDRESS>wrote:

So I was thinking perhaps just "projects" (like we have projectSettings,
not extraProjectSettings).

If I call it projects that would imply both the organic one and
synthetic ones.
If I call it syntethicProjects or extras that would imply both the
build-level and project-level.

buildExtras I think has a nice symmetry with buildSettings and easy to
grasp what it would do.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sbt/sbt/pull/2717#issuecomment-242909585, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVCIpDYgoamTvO-yVRb2OUiocmtm9PUks5qkBJGgaJpZM4JuqPL
.

def projectExtras(proj: ProjectDefinition[_]): Seq[Project].
project-level extras allow you to generate a synthetic subproject from an existing stuff.

I see. Cool.
On Sat, 27 Aug 2016, 12:36 eugene yokota<EMAIL_ADDRESS>wrote:

def projectExtras(proj: ProjectDefinition[_]): Seq[Project].
project-level extras allow you to generate a synthetic subproject from an
existing stuff.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/sbt/sbt/pull/2717#issuecomment-242909741, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAVCIvR7_JMVyMReQvQjAm1MrowZ1r6uks5qkBMrgaJpZM4JuqPL
.

I'm really happy to see progress, thank you.
Reviewed, some minor tweaks, but generally LGTM.

Pushed a commit per reviews.

Docs addressing motivation (why does this feature exist, what problems does it solve) would be helpful.

I agree 100% with @dwijnand's first comment. The feature itself here is absolutely terrific. That said, calling these "extras" feels really under-descriptive to me. There are innumerable "extra" things that could be generated by a plugin, so, as a user, why would I assume that the "extras" would be projects? Also, @dwijnand indicates, this naming would feel kind of weird if you were in a setting where most projects were generated (maybe someone defines a plugin in the future for opinionated builds described by a JSON dependencies file, for instance). Why not just call them generatedProjects and generatedSubprojects?

Or derivedProjects for the second one might be more accurate

There are innumerable "extra" things that could be generated by a plugin, so, as a user, why would I assume that the "extras" would be projects?

A typical build user would not see the method name when they consume a plugin. This is mostly for advanced plugin authors.
I want the names that can be used as noun phrase like projectSettings and buildSettings that would distinguish the build- and project-level clearly. generatedProjects + derivedProjects are not bad, but they are more subtle because you can claim that both are "generated" and/or "derived" off of something like JSON. Can we come up with something that's unambiguous?

Why not just subProjects ?

How about independentProjects and derivedProjects?
One thing I'll note now that I've thought about it is that sbt's model doesn't even really include the notion of "subprojects" unless you count aggregation (which I don't think is in play here). There are just "projects". So isn't it a bit confusing to say that these generated projects are "subprojects"?

I do not believe it is accurate to say SBT does not support the concept of subprojects. See dependsOn in the multi-project build page.

ok. How about:
def extraProjects: Seq[Project]
def derivedProjects(proj: ProjectDefinition[_]): Seq[Project]

?

That combo is better than any one so far. From my point of view, the bikeshedding can stop with them ;). Thanks again for this great feature.

@mslinn That usage of "subproject" means "subproject of the build" not "subproject of another project" and is roughly synonymous with just "project".

@clhodapp if this is going to be an ongoing source of confusion, the docs should introduce a term like "build subproject" or "subbuild" - I don't care if the b's are elided or not.

Sent PR for the rename (#2738)


Reload Page - Parent Css not applied to child - UI Router

Hello,
When we reload the page on a child state (like /home/profile), the parent css (home.css)   is not applied to the child.
Is there a way to persist the css on reload ?
Thanks !

Yes, I have the same problem. It looks like module doesn't support property inheritance from the parent states. Actually this is very sad, because without this feature this module has no value to our project. We can't repeat the same definition of styles for every route, this just makes no sense.
Are you planning to implement inheritance?

We could build the chain of states from the current state to the topmost.
Iterate through the reversed chain, i.e. from topmost state to the current.
When each state is visited add all encountered CSS files to the end of the list, which is empty initially.

In the end we will have the complete list of all CSS files from top state to bottom.
Of course we will also need a mechanism to override some CSS files, this could be very useful when working with different layouts. We can introduce the concept of named styles.
Example
stateHelperProvider
  .state({
    name: 'root',
    css: [
      'bootstrap.css',
      {
        name: 'layout', // <==========  NAMED STYLE
        href: 'primary-layout.css'
      }
    ]
  })
  .state({
    name: 'foo',
    parent: 'root',
    css: 'foo.css'
  })
  .state({
    name: 'bar',
    parent: 'root',
    css: [
      {
        name: 'layout',
        href: 'alternative-layout.css' // <==========  OVERRIDING THE NAMED STYLE!
      },
      'bar.css'
    ]
  })
;

For root.foo state we will have CSS: ['bootstrap.css', 'primary-layout.css', 'foo.css'].
For root.bar state we will have CSS: ['bootstrap.css', 'alternative-layout.css', 'bar.css'].

What do you think @alexandercastillo?

its not working for me either


Adding template manifest to feedback message

Merge after https://github.com/ovotech/comms-orchestration/pull/73 has been deployed

This PR was successfully deployed to production by CircleCI build 532 at 2018-10-01 17:13 BST.


modules/API.md Add more detail to docs for RM_AutoMemory

As far as I can tell, RM_AutoMemory is only for RM objects
(RM keys, RM strings, and RM replies), and not for any type
of object. I added this information to the comments for
RM_AutoMemory and to modules/API.md.

doit, wrong repo. ugh


Fix typo

indent and typo fixes

@simonlinj Good catch!

Wait, how come JS linter didn't notice this?
https://github.com/meanjs/mean/blob/master/.jshintrc#L14

@simison not sure exactly how the rules work, maybe it's a regex and not an exact match check?


Issue/36520 android scan second tap on capture button causes error to show up

Details
Fix bug where a second tap on the camera button on native will show an error message.
There were three things fixed in this PR

Changed capturePhoto to return a Promise so it works properly with the native implementation of useSingleExecution.
Introduce new variable didCapturePhoto to prevent another call to capturePhoto while navigation is triggered and the user is still on the camera screen.
Added focus listener to reset the didCapturePhoto when the user navigate back to the scan screen.

Fixed Issues
$ https://github.com/Expensify/App/issues/36520
PROPOSAL: https://github.com/Expensify/App/issues/36520#issuecomment-1944293570
Tests

Launch New Expensify app
Tap + > Request money
Go to Scan
Tap on the capture button twice
Verify that no errors popup appear in the app

[x]  Verify that no errors appear in the JS console

Offline tests
same as tests
QA Steps
same as tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/771902/c79c9cb1-1f1b-4ad6-8bec-1cb706e02db1

Android: mWeb Chrome
https://github.com/Expensify/App/assets/771902/b828b2d3-50dd-4066-8845-00cb072526ed

iOS: Native
https://github.com/Expensify/App/assets/771902/55d9161c-2cc4-4c7c-b7de-8440b5160904

iOS: mWeb Safari
https://github.com/Expensify/App/assets/771902/0d784573-3077-4cf4-9cff-992c421b985d

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/771902/18ef3f27-6080-47cc-98d2-620284e1614e

MacOS: Desktop
https://github.com/Expensify/App/assets/771902/1d243585-a065-4c15-b4f1-f9a3fd31168e

I have read the CLA Document and I hereby sign the CLA

@agent3bood it looks like you override the checkbox requirement. Usually, it's Verify that no errors appear in the JS console. For the assertion step, you can add step 5, in this case, to verify the expectation. I.e: this PR #37398

Done.

@agent3bood I found a bug when do testing in Android Chrome, when I did double tap on the capture button, it took to next step without error but the selection list is loading forever
Screen.Recording.2024-02-28.at.17.45.27.mov

I was able to reproduce this on Android emulator for both my branch and production as well.
On device it works fine, Android & iOS, what do you suggest we do here?
Recording if from production site.
https://github.com/Expensify/App/assets/771902/1623133a-ee29-4740-900b-95155355e9a0

@agent3bood Linter seems to be complaining, can you please check it and fix. Thanks.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/techievivek in version: 1.4.46-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

Issue #36520 is still reproducible in android and iOS when tapping capture button multiple times. Evidence attached.
https://platform.applause.com/services/links/v1/external/06e6b9891f9f2c712d094cd32f0bf03ffa6680bb4456ced254da373c7ba92054
https://platform.applause.com/services/links/v1/external/263470c4f06e28cab133fa1075e41ceb6861ae6b3f6d5dfd4ed498702d4886b1

@kavimuru I am aware of this behavior and did had a solution for it, but after a discussion with @hoangzinh we decided to remove it.
Please read more here https://github.com/Expensify/App/pull/37182#discussion_r1504489094

🚀 Deployed to production by https://github.com/roryabraham in version: 1.4.46-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


CreditCard Attribute requires additional scripts

In order to have client-side validation using the CreditCard attribute you need to reference jQuery Validation Additional Methods scipts, which can be found here: https://cdn.jsdelivr.net/jquery.validation/1.16.0/additional-methods.min.js
Consider checking the latest scripts version on jQuery Validation official website:
https://jqueryvalidation.org/

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

ID: 0156ffc3-47ac-d5da-fbc2-9ff5018b071b
Version Independent ID: 615db388-a244-41f7-21b5-a4085d9ed479
Content: Model validation in ASP.NET Core MVC
Content Source: aspnetcore/mvc/models/validation.md
Product: aspnet-core
Technology: aspnetcore-mvc
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Add to the end of
[CreditCard]: Validates that the property has a credit card format.
Requires jQuery Validation Additional Methods
cc @serpent5


Update this library to work with Nuke 8.0

Note: After this is merged an update will still need to be published to the cocoapods repo.

@mcmurrym Thank you for your quick support!

There is no problem with the results of CI, so we will merge!


Add new Offset and Count parameters to Format-Hex and refactor the cmdlet

PR Summary

Add new Offset and Count parameters. Resolve #3383.
Modify ByteCollection class to support offsets up to UInt64.MaxValue size.
Hide/obsolete Raw parameter because the behavior is by default. Related #7868.
Optimize conversion to bytes to reduce allocations for large input data.

Additional comments

For review: Now Offset parameter does a shift in output byte stream. Since we accept objects as input we could consider Offset as "skip the Offset-count objects from input (array/pipeline)" although Skip parameter is more suitable for this (or  Select-Object -Skip) and this is contrary to the behavior for input streams (Path parameter or FileInfo input object).

I don't consider a scenario "get last count bytes". As a minimum, the PR should not block this enhancement.

New ReFS file system support files up to UInt64.MaxValue. So ByteCollection is modified to support UInt64.MaxValue too.
On the other hand current .Net Core limitation is Int64.MaxValue for file size/offset. In result we have to use Int64 type for Offset and Count parameters.

/cc @rkeithhill @mklement0 @adamdriscoll
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[ ] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

User-facing changes

[ ] Not Applicable
OR
[x] User-facing Documentation needed

[x] Issue filed - Issue link: https://github.com/PowerShell/PowerShell-Docs/issues/2986

Testing - New and feature

[ ] Not Applicable or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] if the change is significant or affects feature tests

@PowerShell/powershell-committee reviewed this and ok with the proposed changes

Doc Issue created.

@SteveL-MSFT @TravisEz13 Could you please review the PR?


Add support for IndexedDB in Safari 10.1+

This is after the discussion here  and should allow Safari 10.1+ to us IndexedDB

:+1:


Set revision for kBET installation

Latest commit in kBET package breaks backward compatibility for R=3.6.1.
https://github.com/theislab/kBET/blob/2e2b09179bba4808903d04e4425f9d5cdbeaa989/R/kBET.R#L195

Hi @johnarevalo ,
I tried to reproduce the issue with R 3.6.1 using the latest version of kBET, but couldn't. Could you provide the error message that you are getting?

Thanks for your reply @mumichae , I did a clean installation and the message dissapeared.


Remove duplicated S from svg.svg

https://github.com/edent/SuperTinyIcons/issues/535

Good spot! Please update the README with the new size, and I'll merge.


Rethink scrollWidth bug fix

The current scrollWidth fix is not good enough.
Consider loading  All, then filtering to a set with only a few images (i.e. no need for scrollbars) e.g. ByLocation Melbourne. This fits, now filter back—this fails.
What we need to do is keep scrollWidth throughout, and test if it exists at the current time or not, and compare against how many rows we need to fill the screen. That may mean double calculating optimalRowCount.

There's still one issue. Take the Melbourne set and resize such that it spill over to fill almost the page. Now flip the order. The last image fills the full width and thus pushes out a scrollbar. Not too sure how to deal with this scenario just yet.

This is no longer a problem since we've dropped the additional UI function of sort order.


Allow passing options to scanForPeripherals

Just allows the optional use of options and passes them along to the scanForPeripherals
This seems to be working well for me with or without the options provided.
Let me know if or how I can regenerate the docs (I'm not much of a Swift dev)
Thanks!
Closes #9

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Reland "TextField constrained layout bug (#65966)"

Description
This relands https://github.com/flutter/flutter/pull/65966, which was reverted by https://github.com/flutter/flutter/pull/66027.
The reason for the reversion was a broken Scuba test (see b/168761772).  I made an auxiliary fix in the original PR not directly related to the issue, and it seems that bug was relied upon by a dependent app.  I think the real solution there is a more complicated fix, which I'm tracking in the new issue https://github.com/flutter/flutter/issues/66050.  I've also added a new test here that should catch the problem before running post submit tests in the future.
In the meantime, let's reland this so that the original layout bug https://github.com/flutter/flutter/issues/65572 will be fixed.
Related Issues
https://github.com/flutter/flutter/issues/65572
b/168761772
https://github.com/flutter/flutter/issues/66050

Gold has detected about 3 untriaged digest(s) on patchset 2.
View them at https://flutter-gold.skia.org/cl/github/66055

Gold has detected about 3 untriaged digest(s) on patchset 2.
View them at https://flutter-gold.skia.org/cl/github/66055


Memorize gene order in user profile

Hibernate has an @OrderedBy annotation that can take a column to maintain order. Genes should be stored in a SortedSet since we don't want duplicates. Extra checks must be done to ensure that they have a total order because TreeSet will collapse elements that compare as equals.

This is not worth it. I'll be sorting user genes by symbol (and geneId) in addition to tiers and user.


python3Packages.fiblary3: init at 0.1.12

Motivation for this change
Library for Fibaro devices (used in Home Assistant).
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
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 nixpkgs-review --run "nixpkgs-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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114049 at df225f86 run on aarch64-linux 1

3 packages built:

python37Packages.fiblary3
python38Packages.fiblary3
python39Packages.fiblary3

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114049 run on x86_64-linux 1

3 packages built:

python37Packages.fiblary3
python38Packages.fiblary3
python39Packages.fiblary3

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

python37Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python39Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114049 run on x86_64-darwin 1

3 packages built:

python37Packages.fiblary3
python38Packages.fiblary3
python39Packages.fiblary3

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

python37Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python38Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

python39Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

Add a checkPhase for tests, or at least pythonImportsCheck.
See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/python-include-tests.md

Thanks, I've made the suggested changes.

The upstream repo contains tests. If possible should those tests run during the build.

I did try this before, and it looks like the tests are excluded from the PyPI distribution (I'm guessing because the test package is excluded from setup.py).  Is this a common issue?  I could build from GitHub instead, but the repo doesn't have tags for any recent releases.

If not, please add at least pythonImportsCheck. Thanks.

Done, thanks.

Is this a common issue?

Yes.

but the repo doesn't have tags for any recent releases.

Could you request tags upstream?

Could you request tags upstream?

The upstream repo doesn't have Issues enabled :)  It looks like the tests have problems, I will see if I can fix any of them and raise a PR, and ask about tags in that PR too.

Could you request tags upstream?

The upstream repo doesn't have Issues enabled :) It looks like the tests have problems, I will see if I can fix any of them and raise a PR, and ask about tags in that PR too.

It seemed worth putting some effort in since I have a sizeable dependency on this library, so I fixed the tests: https://github.com/pbalogh77/fiblary/pull/2.  They all now pass from the nix package too if I refer to my branch, so hopefully we can get this merged upstream.  Unfortunately it doesn't look like upstream has any CI so the tests had rotted quite badly.  I also asked about tags in the same PR.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114049 run on x86_64-linux 1

3 packages built:

python37Packages.fiblary3
python38Packages.fiblary3
python39Packages.fiblary3

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

python37Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python38Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python39Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 114049 run on x86_64-linux 1

3 packages built:

python37Packages.fiblary3
python38Packages.fiblary3
python39Packages.fiblary3

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

python37Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python38Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

python39Packages.fiblary3:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;' and a pythonImportsCheck.

I think until the above PR is merged upstream and or there is some sign of activity from the maintainer, it's likely best to hold off on merging this into nixpkgs.  Let me know if it's best to withdraw the PR or somehow mark it as a work in progress.

@graham33 I think you should fork fiblary and make upstream Home Assistant use your fork (in which the tests would be fixed).

It has been almost a year since I raised that PR, and no sign of activity on pbalogh77/fiblary since 2020. I can give it a try!

I've created a fork at https://github.com/graham33/fiblary and https://pypi.org/project/fiblary3-fork/ and updated this PR to use it.  Will create an issue in home-assistant upstream.

Result of nixpkgs-review pr 114049 run on x86_64-linux 1

2 packages built:

python310Packages.fiblary3-fork
python39Packages.fiblary3-fork

@mweinelt Please take a look at the changes to parse-requirements.py.

Refactor of parse-requirements.py looks fine.


'/@id/__vite-browser-external:events' does not provide an export named 'EventEmitter'

Describe the bug
I added Vite to an existing Project. When I want to opem it in the Browser i get the
localhost/:1 Uncaught SyntaxError: The requested module '/@id/__vite-browser-external:events' does not provide an export named 'EventEmitter'

Reproduction
import vue from '@vitejs/plugin-vue'
import {defineConfig } from "vite";
import * as path from "path";

export default defineConfig({
    plugins: [vue()],
    resolve: {
        alias: {
            '@': path.resolve(__dirname, './src'),
        }
    }
})

System Info
Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:
System:
OS: Linux 5.9 Fedora 33 (Workstation Edition) 33 (Workstation Edition)
CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
Memory: 2.43 GB / 31.09 GB
Container: Yes
Shell: 5.8 - /usr/bin/zsh
Binaries:
Node: 14.15.4 - /usr/bin/node
npm: 6.14.11 - /usr/local/bin/npm
Browsers:
Chrome: 87.0.4280.141
Firefox: 84.0.2
npmPackages:
@vitejs/plugin-vue: ^1.1.5 => 1.1.5
vite: ^2.1.3 => 2.1.3

Used package manager:
Logs

Before submitting the issue, please make sure you do the following

[ ] Read the Contributing Guidelines.
[ ] Read the docs.
[ ] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[ ] Provide a description in this issue that describes the bug.
[ ] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[ ] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

@arttobe Could you provide a comment how you e.g. solved your issue?
That way folks using a search engine can find a solution on their own

I don't know why my code with web pack worked. The issue was that the browser don't have an native event emitter and I just install then with npm I events. I found the exactly issue when I tried to build it with vite build. The biggest problem was that the error message was not clear.

Indeed running vite build gives a clearer error message.
My issue was when I tried to use ToneJS and @tonejs/piano. I'm not sure what fixed it. But I did the following:
npm install events
npm i --save-dev @types/events
npm install @types/node --save-dev
# I still got the error in the browser - I restarted my `vite` dev server and then the error went away


Fixed issues relating to osl_synapse_service

Added the ability to host synapse services on a singular instance
Patched an issue where postgresql was not being configured

!bump patch ~

Jenkins has merged this PR into master and has automatically performed a patch-level version bump to v1.0.1.  Have a nice day!


Updated Mac installation instructions

d12frosted's homebrew-emacs-plus was updated to Emacs 27, so the addendum is no longer necessary

This is a duplicate of #3725


add environment variable on exec

@rismoney want to fix up manifests/install.pp - WARNING: variable not enclosed in {} on line 35

i am nowhere near ready. i think i need a provider mod.

ugh- guess i just learned class level methods are only called 1x at start.  also learned about environments method... its a neverending road.

not sure what you mean by puppet_x is.
the registry!!! don't even deal with ENV.
i have been refamiliaring myself with the provider methods.  its def been a while.

Yep :)

is the idea behind using puppet_x is code reuse across the fact and the provider?

@rismoney yes sir.

so is it essentially-
puppet_x/chocolatey.rb
class foo
  def...end
end

and then require this?

That's close.
module PuppetX::Chocolatey::ChocolateyInstall
See https://github.com/puppetlabs/puppetlabs-dsc/blob/master/lib/puppet_x/puppetlabs/powershell_version.rb

updated last comment.

am i on the right track? :)

Looking pretty good so far.

Alright I'll run with this tomorrow and write the rspec. Kids wake up darn early :)

so, now I have this utility code, which is neat (as I always wondered about the why of the puppet_x namespacing) i need to have the environment variable evaluated and potentially set before each resource is evaluated, not when the provider loads.
In a previous test, I learned that there is a method called environment but that is only evaluated 1x when the provider is first loaded. ie:
environment :ChocolateyInstall => 'someval'

Is there a way to either

force a refresh of that environment  or
2.does each method in the provider need to set the session environment variable (by means of a separate method) to match the machine variable.

i thought initialize might be the ticket, but that is evaluated per resource, but before any subsequent processing.  wondering your thoughts on this before I plunge back into a fix.

think i figured it out.  ;)

forgot about self.class

think i need to make it self.set_env_chocolateyinstall so it can be accessible by self.instances. may have had a provider scoping epiphany.

it works!

Sweet!

Can you go ahead and prepend all of your commits with (GH-86)?

:ship:
@ferventcoder btw - thanks for the code reviews, insights, and your time!

Thanks for the help in tracking this one down. :)


scss_lint throwing character has '-' without escape error

Versions:
Ruby -  2.2.3p173
scss-lint - 0.42.2

above is the error I get on atom with linter-scss-lint, but is the same error that get's thrown when using scss-lint directly from the command line.

You've got to help us out, @nim23: what is the scss content that led to this error?

@srawlins, sorry should have been more explicit
.bag-page {
    display: block;
 }

Any class name's with - in them throws the warning.

Hey @nim23,
What's the ASCII code of that character from the original file you're trying to lint? When I copy/paste that code as written in GitHub, I can't reproduce this issue.
My hunch is that the character is not a dash but an en dash or em dash, which is why you are seeing the error.

it's definitely not en dash or em dash, something seems off to me about my config/settings, I have grunt scss-lint which eventually run's this scss-lint -c /Users/ngurung/.scsslint.yml /app/_small.scss command but running the same command via command line seems to throw an error.

Apparently it's not the css it's something to do with /usr/local/lib/ruby/gems/2.2.0/gems/scss_lint-0.42.2/lib/scss_lint/linter/selector_format.rb:79: warning: character class has '-' without escape: /^[_a-z0-9\/-a-z0-9]+$/ . Not a ruby expert but seems like a ruby warning, for that specific file on line 79.

Finally found the culprit. On my .scsslint.yml file I had an regex '^[_a-z0-9/-a-z0-9]+$' which was invalid and unescaped. Fixed it by changing the regex to ^[_a-z0-9/-a-z0-9]+$' . Closing the issue, thanks for replying to my queries.


soroban-rpc: Ingest temp ledger entry evictions

What
In https://github.com/stellar/go/pull/5037 temporary ledger entries which are evicted are excluded from the change reader. So, we need to handle the deletions explicitly by the EvictedTemporaryLedgerKeys() method on the LedgerCloseMeta struct.
Known limitations
[N/A]

Also, I am missing a test.


Remove Green Background of the cart

I want to remove the green background of the add to cart and align it according to the cart image and text.

I'm unable to push my changes . It's showing this error of permission denied. Can you please help me with this?

Assign to You Start working and complete in 1 week
Follow contributing.md guide for successful PR merge.
Happy Coding!!


Add openssl x509 -fingerprint -sha256 to "Show certificate info"

Nice thing is that openssl x509 respects the order of supplied arguments. It was chosen to print the one line of fingerprint above of the X509 text dump. -sha256 is needed because OpenSSL 1.0.2k-freebsd 26 Jan 2017 seems to default to SHA1 currently.
Example of the first line:
SHA256 Fingerprint=F0:E6:EB:31:E8:87:AF:52:16:4E:84:05:3B:6C:03:2C:C1:DF:5A:E7:36:F4:32:44:3B:B5:57:63:97:45:C3:77

This commit is one piece to make fully trusted bootstrapping easier.
Related to: https://github.com/opnsense/core/issues/2427
URL path of the GUI page involved: /system_certmanager.php

Merged, thanks!

You are welcome, thanks!


fix peer deps

@aruniverse you will forward-port?

@aruniverse you will forward-port?

yep, https://github.com/iTwin/itwinjs-core/pull/3447


Support Connection Params

The additional connection params were not added to the connection string
Missed to implement methods that can add connection params to the connection string


device id gets longer

I added file /etc/default/horizon like this:
SNAP_COMMON=/var/horizon
GOPATH=/usr/horizon/go
mtn_soliditycontract_block_read_delay=3
ANAX_LOG_LEVEL=5
CMTN_DIRECTORY_VERSION=999
CMTN_DEVICE_ID=stg-agbot-dal06-01.staging.bluehorizon.network
CMTN_DATA_VERIFICATION_URL=http://xx:xx.xx.xx:xxxx/all.json
CMTN_EXCHANGE_URL=https://exchange.staging.bluehorizon.network/api/v1/

And installed bluehorizon and horizon deb packages version 2.3.0.
After the installation, the CMTN_DEVICE_ID in the above file got longer:
CMTN_DEVICE_ID=6724cf3553bb8e4c9e04bb91d927f001983d251astg-agbot-dal06-01.staging.bluehorizon.network

This does not happen if I move CMTN_DEVICE_ID to the last line.

Further debugging found that it is this line that is failing.
https://github.com/open-horizon/horizon-pkg/blob/master/pkgsrc/seed/horizon/fs/usr/horizon/sbin/horizon-env-preprocess#L13
The code looks like this:
existing_device_id=$(grep -oP "${cmtn_device_id_varname}=\K([^]+)" $var_filepath)

Fixed in PR https://github.com/open-horizon/horizon-pkg/pull/29


Repeater cannot clone control for type: Microsoft.Dynamics.Framework.UI.FormHostControl because it does not implement the IRepeatable interface or the interface implementation returns a control type that is not valid.

Please include the following with each issue:
1. Describe the bug
The web client crashes when a page part is placed in the wrong location. In the event log you can find the exception error message Repeater cannot clone control for type: Microsoft.Dynamics.Framework.UI.FormHostControl because it does not implement the IRepeatable interface or the interface implementation returns a control type that is not valid..

2. To Reproduce
Steps to reproduce the behavior:

Publish these to extensions and open the Page 518 (Purchase Lines).

pageextension 50100 "Purchase Lines" extends "Purchase Lines"
{
    layout
    {
        addlast(Control1)
        {
            part("Document Comments"; "Purch. Line Comm. Factbox")
            {
                ApplicationArea = All;
                Caption = 'Document Comments';
                SubPageLink = "Document Type" = field("Document Type"),
                              "No." = field("Document No."),
                              "Document Line No." = const(0);
            }
        }
    }
}

page 50100 "Purch. Line Comm. Factbox"
{
    ApplicationArea = All;
    Caption = 'Purchase Line Comments';
    Editable = false;
    PageType = ListPart;
    SourceTable = "Purch. Comment Line";

    layout
    {
        area(Content)
        {
            repeater(Lines)
            {
                field(Date; Rec.Date)
                {
                    ApplicationArea = All;
                    Visible = false;
                }
                field(Code; Rec.Code)
                {
                    ApplicationArea = All;
                    Visible = false;
                }
                field(Comment; Rec.Comment)
                {
                    ApplicationArea = All;
                }
            }
        }
    }
}

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
The web client should not crash. Prevent this either at publishing and in the AL compiler or do not show this page part.
4. Actual behavior
Web Client crashes
5. Versions:

AL Language: 11.0.706681
Visual Studio Code: 1.73.1
Business Central: DE Business Central 22.0 (Plattform 22.0.49091.0 + Anwendung 22.0.49695.0)
List of Visual Studio Code extensions that you have installed:

AL Language

We discovered this problem in the current version of BC 21.1 and I tested it with the current next major version.
Final Checklist
Please remember to do the following:

[x] Search the issue repository to ensure you are reporting a new issue

[x] Reproduce the issue after disabling all extensions except the AL Language extension

[x] Simplify your code around the issue to better isolate the problem

Hello, this issue is out of scope for the current repository. I will pass this bug on to the relevant team and close the issue.
The reason why this is out of scope is because it relates to the behaviour of the BC client, so it needs to go to the team who handles the client. This repository only handles issues related to the AL language and compiler.
If it is a critical issue, you can follow the instructions below:
Open a support request to CSS through the PartnerSource portal
Open a bug in Collaborate
Contact your Service Account Manager (SAM) in your local subsidiary to understand what is included in your contract as of support incident and PAH (Partner Advisory Hours). Your SAM might also direct you "step by step" how to open a support request or how to get credentials, if this is the first time for you or your company
As a reminder, this repository only handles issues to do with the compiler or VSCode development experience for AL.

For future reference, this issue is covered by this UICop rule: https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/analyzers/uicop-aw0003
This should show a warning when a part is added by mistake to a repeater


Draft: Add bzlmod minimal support

Description
This is the first step of migration to Bzlmod, see https://bazel.build/external/migration
I'm gonna create a few further pull requests to bring all the changes described here: https://github.com/bazelbuild/rules_scala/issues/1482#issuecomment-1907672400
The migration process will finish once WORKSPACE.bzlmod is empty
Motivation
Resolve https://github.com/bazelbuild/rules_scala/issues/1482

I turn into a draft because will surely cause conflicts with these changes:

SCALA_VERSION dependent code has to be refactored to read this information from the toolchain

Hi, @mateuszkuta256, thanks for taking this. So as I understand this is somewhat "blocked" by required changes to toolchains and SCALA_VERSION. I'll reply in multi scala issue shortly. This change and multi scala are the big ones. So maybe lets first solve multi scala and toolchains and then bzlmod (i have a hunch that proper toolchains would make bzlmod migration easier).

Closing in favour of https://github.com/bazelbuild/rules_scala/issues/1482


dapp: Integrate udc withdrawal

Thank you for submitting this pull request :)
Fixes #1421
Short description
Definition of Done

[x] Steps to manually test the change have been documented
[x] Acceptance criteria are met
[ ] Change has been manually tested by the reviewer (dApp)

Steps to manually test the change (dApp)

Open the dApp
Go to the account page
Press the withdraw icon
Enter an amount
Wait.

Looks like failures are not handled properly
I didn't have ETH on my subkey account when tried to withdraw, the failure action was properly emitted, but dialog stayed spinning, no error shown, no hidding:

I'm going to transfer ETH to check workflow in the happy case.

Ok let me check

lgtm, tested here and working fine. Would we push the notification at some point, or this is it for the scope of this PR? Thanks

I think we should do that as part of https://github.com/raiden-network/light-client/pull/1648.
Let's coordinate with @taleldayekh to get it ready


Use property for property-based tests in MUnit

Thanks to @diesalbla for noting this.

Codecov Report

Merging #1594 (93304d1) into master (4d2edce) will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1594      +/-   ##
==========================================
- Coverage   85.26%   85.12%   -0.14%
==========================================
  Files          58       58
  Lines        2219     2219
  Branches      105      105
==========================================
- Hits         1892     1889       -3
- Misses        327      330       +3

Impacted Files
Coverage Δ

...les/core/shared/src/main/scala/io/circe/Json.scala
80.44% <0.00%> (-1.12%)
:arrow_down:

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
84.79% <0.00%> (-0.59%)
:arrow_down:

.../core/shared/src/main/scala/io/circe/Decoder.scala
85.32% <0.00%> (-0.28%)
:arrow_down:

...d/src/main/scala/io/circe/NonEmptySeqDecoder.scala
100.00% <0.00%> (+8.33%)
:arrow_up:

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 4d2edce...93304d1. Read the comment docs.


How can i change default ssh port(22) to another port?

Our online servers change ssh port to another port， and i found alluxio hardcode ssh port(22).
So,  How can i change it to another port ?

unfortunately there is no easy way of changing that right now.
We will take a look when we plan for the next release. In the meantime, you are welcome to modify the scripts and contribute a PR.

The default ssh tools provided usually have many configuration options. From my knowledge, we simply use the default port (22) when connecting. It is trivial to configure separate hosts to connect with a different port without having to specify it on the command line.
There should be a file $HOME/.ssh/config or /etc/ssh/config
The sections in the file are split by a Host section. Below is an example file.
# These properties apply to all hosts
Host *
    ForwardAgent no
    ForwardX11 no
    PasswordAuthentication no

# when calling "ssh myhost1" the following properties will apply
Host myhost1
    HostName myhost.mydomain.com
    User specialLoginUser
    Port 2202
    IdentityFile /etc/keys/id_rsa

For more thorough details refer to the man page


Create 0000-01-02-Trish-McElderry777.md.

I have created a new file in this GitHub tutorial.

I have created a new file and added a change.  I have made a pull request and have merged the file and this pull request will be now be closed with this commit message.  Thank you

I am now delete the the branch that I created as a new file from the main branch.  Thank you


Cisco talosintelligence

Hello,
For the coming future, can we add talos intelligence https://www.talosintelligence.com/ to cont3xt integrations. It's a free servie.
Thanks

doing a quick look i don’t see an api for talos. You could already just add it as a link to a link group since it has nice URLS like https://talosintelligence.com/reputation_center/lookup?search=<IP_ADDRESS>
If you wanted something else please reopen with details


Update jawn dependency to 0.8.3

Prior to 0.8.3, jawn had an unintentional runtime dependency on jmh, which is under an incompatible license. See non/jawn#33 (comment).
See https://github.com/rossabaker/jawn-streamz/pull/3, but there are also dependencies on org.spire-math:argonaut-support and :json4s-support, neither of which seems to have had an 0.8.3 release yet.

Giving this a bug label.  It's not our bug, but we can do a patch release to get people license compliant.

Figured it out.  The jawn 0.8.3 artifacts changed names in 0.8.1.  http4s-0.8.5 coming shortly.


Cluster shutdown fails in batch mode on Python >3.8

What happened:
When Dask-MPI is used in batch mode (i.e., using initialize()), it does not properly shut down the scheduler and worker processes when the client script completes.
With Python <3.9, the batch process shuts down with an error.  And with Python >=3.9, the batch process hangs.
What you expected to happen:
When the client script completes, the scheduler and worker processes should be shut down without error or hanging.
Minimal Complete Verifiable Example:
In a script called client.py:
from distributed import Client
from dask_mpi import initialize

initialize()

with Client() as c:
    assert c.submit(lambda x: x + 1, 10).result() == 11

Then run this with mpirun as:
mpirun -n 4 python client.py

With Python >=3.9, this will result in the following errors and hanging processes.

Output & Error Messages with Python >=3.9
2022-04-19 15:44:59,709 - distributed.scheduler - INFO - State start
2022-04-19 15:44:59,712 - distributed.scheduler - INFO - Clear task state
2022-04-19 15:44:59,713 - distributed.scheduler - INFO -   Scheduler at:  tcp://<IP_ADDRESS>:64417
2022-04-19 15:44:59,713 - distributed.scheduler - INFO -   dashboard at:                    :64416
2022-04-19 15:44:59,730 - distributed.worker - INFO -       Start worker at:   tcp://<IP_ADDRESS>:64418
2022-04-19 15:44:59,730 - distributed.worker - INFO -          Listening to:   tcp://<IP_ADDRESS>:64418
2022-04-19 15:44:59,730 - distributed.worker - INFO -       Start worker at:   tcp://<IP_ADDRESS>:64419
2022-04-19 15:44:59,730 - distributed.worker - INFO -          dashboard at:         <IP_ADDRESS>:64422
2022-04-19 15:44:59,730 - distributed.worker - INFO - Waiting to connect to:   tcp://<IP_ADDRESS>:64417
2022-04-19 15:44:59,730 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,730 - distributed.worker - INFO -          Listening to:   tcp://<IP_ADDRESS>:64419
2022-04-19 15:44:59,731 - distributed.worker - INFO -          dashboard at:         <IP_ADDRESS>:64423
2022-04-19 15:44:59,730 - distributed.worker - INFO -               Threads:                          1
2022-04-19 15:44:59,731 - distributed.worker - INFO -                Memory:                   2.00 GiB
2022-04-19 15:44:59,731 - distributed.worker - INFO - Waiting to connect to:   tcp://<IP_ADDRESS>:64417
2022-04-19 15:44:59,731 - distributed.worker - INFO -       Local Directory: /Users/kpaul/tst/dask-worker-space/worker-ljhbwdiz
2022-04-19 15:44:59,731 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,731 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,731 - distributed.worker - INFO -               Threads:                          1
2022-04-19 15:44:59,731 - distributed.worker - INFO -                Memory:                   2.00 GiB
2022-04-19 15:44:59,731 - distributed.worker - INFO -       Local Directory: /Users/kpaul/tst/dask-worker-space/worker-xtuties_
2022-04-19 15:44:59,731 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,750 - distributed.scheduler - INFO - Receive client connection: Client-f6204526-c029-11ec-a0ca-acde48001122
2022-04-19 15:44:59,762 - distributed.core - INFO - Starting established connection
2022-04-19 15:44:59,764 - distributed.scheduler - INFO - Register worker <WorkerState 'tcp://<IP_ADDRESS>:64418', name: 3, status: undefined, memory: 0, processing: 0>
2022-04-19 15:44:59,765 - distributed.scheduler - INFO - Starting worker compute stream, tcp://<IP_ADDRESS>:64418
2022-04-19 15:44:59,765 - distributed.core - INFO - Starting established connection
2022-04-19 15:44:59,766 - distributed.scheduler - INFO - Register worker <WorkerState 'tcp://<IP_ADDRESS>:64419', name: 2, status: undefined, memory: 0, processing: 0>
2022-04-19 15:44:59,766 - distributed.worker - INFO -         Registered to:   tcp://<IP_ADDRESS>:64417
2022-04-19 15:44:59,766 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,767 - distributed.scheduler - INFO - Starting worker compute stream, tcp://<IP_ADDRESS>:64419
2022-04-19 15:44:59,767 - distributed.core - INFO - Starting established connection
2022-04-19 15:44:59,768 - distributed.core - INFO - Starting established connection
2022-04-19 15:44:59,767 - distributed.worker - INFO -         Registered to:   tcp://<IP_ADDRESS>:64417
2022-04-19 15:44:59,768 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:44:59,769 - distributed.core - INFO - Starting established connection
2022-04-19 15:44:59,870 - distributed.scheduler - INFO - Remove client Client-f6204526-c029-11ec-a0ca-acde48001122
2022-04-19 15:44:59,870 - distributed.scheduler - INFO - Remove client Client-f6204526-c029-11ec-a0ca-acde48001122
2022-04-19 15:44:59,871 - distributed.scheduler - INFO - Close client connection: Client-f6204526-c029-11ec-a0ca-acde48001122
Exception ignored in atexit callback: <function send_close_signal at 0x10f8085e0>
Traceback (most recent call last):
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/dask_mpi/core.py", line 159, in send_close_signal
    with Client() as c:
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/client.py", line 943, in __init__
    self.start(timeout=timeout)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/client.py", line 1101, in start
    sync(self.loop, self._start, **kwargs)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/utils.py", line 376, in sync
    raise exc.with_traceback(tb)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/utils.py", line 349, in f
    result = yield future
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/tornado/gen.py", line 762, in run
    value = future.result()
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/client.py", line 1193, in _start
    await self._ensure_connected(timeout=timeout)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/client.py", line 1256, in _ensure_connected
    comm = await connect(
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/comm/core.py", line 289, in connect
    comm = await asyncio.wait_for(
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/asyncio/tasks.py", line 445, in wait_for
    return fut.result()
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/comm/tcp.py", line 439, in connect
    stream = await self.client.connect(
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/tornado/tcpclient.py", line 265, in connect
    addrinfo = await self.resolver.resolve(host, port, af)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/site-packages/distributed/comm/tcp.py", line 424, in resolve
    for fam, _, _, _, address in await asyncio.get_running_loop().getaddrinfo(
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/asyncio/base_events.py", line 860, in getaddrinfo
    return await self.run_in_executor(
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/asyncio/base_events.py", line 818, in run_in_executor
    executor.submit(func, *args), loop=self)
  File "/Users/kpaul/Software/miniconda3/envs/t/lib/python3.10/concurrent/futures/thread.py", line 169, in submit
    raise RuntimeError('cannot schedule new futures after '
RuntimeError: cannot schedule new futures after interpreter shutdown

With Python <=3.8, the process will complete with the following error.

Output & Error Messages with Python <=3.8
2022-04-19 15:58:09,211 - distributed.scheduler - INFO - State start
2022-04-19 15:58:09,215 - distributed.scheduler - INFO - Clear task state
2022-04-19 15:58:09,216 - distributed.scheduler - INFO -   Scheduler at:  tcp://<IP_ADDRESS>:64620
2022-04-19 15:58:09,216 - distributed.scheduler - INFO -   dashboard at:                    :64619
2022-04-19 15:58:09,219 - distributed.diskutils - INFO - Found stale lock file and directory '/Users/kpaul/tst/dask-worker-space/worker-ljhbwdiz', purging
2022-04-19 15:58:09,220 - distributed.diskutils - INFO - Found stale lock file and directory '/Users/kpaul/tst/dask-worker-space/worker-xtuties_', purging
2022-04-19 15:58:09,232 - distributed.worker - INFO -       Start worker at:   tcp://<IP_ADDRESS>:64621
2022-04-19 15:58:09,232 - distributed.worker - INFO -          Listening to:   tcp://<IP_ADDRESS>:64621
2022-04-19 15:58:09,232 - distributed.worker - INFO -          dashboard at:         <IP_ADDRESS>:64625
2022-04-19 15:58:09,232 - distributed.worker - INFO - Waiting to connect to:   tcp://<IP_ADDRESS>:64620
2022-04-19 15:58:09,232 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,232 - distributed.worker - INFO -               Threads:                          1
2022-04-19 15:58:09,232 - distributed.worker - INFO -                Memory:                   2.00 GiB
2022-04-19 15:58:09,232 - distributed.worker - INFO -       Local Directory: /Users/kpaul/tst/dask-worker-space/worker-oavxhitg
2022-04-19 15:58:09,232 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,234 - distributed.worker - INFO -       Start worker at:   tcp://<IP_ADDRESS>:64623
2022-04-19 15:58:09,235 - distributed.worker - INFO -          Listening to:   tcp://<IP_ADDRESS>:64623
2022-04-19 15:58:09,235 - distributed.worker - INFO -          dashboard at:         <IP_ADDRESS>:64626
2022-04-19 15:58:09,235 - distributed.worker - INFO - Waiting to connect to:   tcp://<IP_ADDRESS>:64620
2022-04-19 15:58:09,235 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,235 - distributed.worker - INFO -               Threads:                          1
2022-04-19 15:58:09,235 - distributed.worker - INFO -                Memory:                   2.00 GiB
2022-04-19 15:58:09,235 - distributed.worker - INFO -       Local Directory: /Users/kpaul/tst/dask-worker-space/worker-501yo9_d
2022-04-19 15:58:09,235 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,238 - distributed.scheduler - INFO - Receive client connection: Client-ccb4dc0e-c02b-11ec-a3ea-acde48001122
2022-04-19 15:58:09,240 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,248 - distributed.scheduler - INFO - Register worker <WorkerState 'tcp://<IP_ADDRESS>:64621', name: 3, status: undefined, memory: 0, processing: 0>
2022-04-19 15:58:09,249 - distributed.scheduler - INFO - Starting worker compute stream, tcp://<IP_ADDRESS>:64621
2022-04-19 15:58:09,249 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,249 - distributed.worker - INFO -         Registered to:   tcp://<IP_ADDRESS>:64620
2022-04-19 15:58:09,249 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,250 - distributed.scheduler - INFO - Register worker <WorkerState 'tcp://<IP_ADDRESS>:64623', name: 2, status: undefined, memory: 0, processing: 0>
2022-04-19 15:58:09,250 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,251 - distributed.scheduler - INFO - Starting worker compute stream, tcp://<IP_ADDRESS>:64623
2022-04-19 15:58:09,251 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,251 - distributed.worker - INFO -         Registered to:   tcp://<IP_ADDRESS>:64620
2022-04-19 15:58:09,251 - distributed.worker - INFO - -------------------------------------------------
2022-04-19 15:58:09,252 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,359 - distributed.scheduler - INFO - Remove client Client-ccb4dc0e-c02b-11ec-a3ea-acde48001122
2022-04-19 15:58:09,360 - distributed.scheduler - INFO - Remove client Client-ccb4dc0e-c02b-11ec-a3ea-acde48001122
2022-04-19 15:58:09,360 - distributed.scheduler - INFO - Close client connection: Client-ccb4dc0e-c02b-11ec-a3ea-acde48001122
2022-04-19 15:58:09,371 - distributed.scheduler - INFO - Receive client connection: Client-cccae17a-c02b-11ec-a3ea-acde48001122
2022-04-19 15:58:09,371 - distributed.core - INFO - Starting established connection
2022-04-19 15:58:09,374 - distributed.worker - INFO - Run out-of-band function 'stop'
2022-04-19 15:58:09,374 - distributed.scheduler - INFO - Scheduler closing...
2022-04-19 15:58:09,375 - distributed.scheduler - INFO - Scheduler closing all comms
2022-04-19 15:58:09,376 - distributed.scheduler - INFO - Remove worker <WorkerState 'tcp://<IP_ADDRESS>:64621', name: 3, status: running, memory: 0, processing: 0>
2022-04-19 15:58:09,376 - distributed.core - INFO - Removing comms to tcp://<IP_ADDRESS>:64621
2022-04-19 15:58:09,376 - distributed.worker - INFO - Stopping worker at tcp://<IP_ADDRESS>:64621
2022-04-19 15:58:09,376 - distributed.worker - INFO - Stopping worker at tcp://<IP_ADDRESS>:64623
2022-04-19 15:58:09,378 - distributed.batched - INFO - Batched Comm Closed <TCP (closed) Worker->Scheduler local=tcp://<IP_ADDRESS>:64627 remote=tcp://<IP_ADDRESS>:64620>
Traceback (most recent call last):
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/distributed/batched.py", line 94, in _background_send
    nbytes = yield self.comm.write(
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/tornado/gen.py", line 762, in run
    value = future.result()
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/distributed/comm/tcp.py", line 269, in write
    raise CommClosedError()
distributed.comm.core.CommClosedError
2022-04-19 15:58:09,378 - distributed.batched - INFO - Batched Comm Closed <TCP (closed) Worker->Scheduler local=tcp://<IP_ADDRESS>:64628 remote=tcp://<IP_ADDRESS>:64620>
Traceback (most recent call last):
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/distributed/batched.py", line 94, in _background_send
    nbytes = yield self.comm.write(
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/tornado/gen.py", line 762, in run
    value = future.result()
  File "/Users/kpaul/Software/miniconda3/envs/tt/lib/python3.8/site-packages/distributed/comm/tcp.py", line 269, in write
    raise CommClosedError()
distributed.comm.core.CommClosedError

Anything else we need to know?:
I believe this is due to changes in asyncio that occurred with the release of Python 3.9 (and continues in 3.10).  Dask-MPI depends upon calling a function to shutdown the dask cluster at exit (i.e., via the atexit module).  But it appears that the changes in CPython prevent the calling of an asyncio-dependent function at exit, resulting in the above RuntimeError: cannot schedule new futures after interpreter shutdown.
Environment:

Dask version:  2022.4.1
Python version:  3.10.4
Operating System:  Linux / MacOS
Install method (conda, pip, source):  conda

I believe that the appropriate solution to this problem is to remove the explicit atexit-registered function and require that the user call Client.shutdown() at the end of their script.
And I think there are additional simplifications that can be done following this change, but I need some time to think about it before writing anything more down.

One note.  The distributed.comm.core.CommClosedError errors can be avoided by calling Client.shutdown() instead of Dask-MPI's core.send_close_signal().  However, if we use:
def send_close_signal():
    with Client() as c:
        c.shutdown()

this will still fail with Python >3.8 when used with atexit because the loop will be closed by the time send_close_signal is called.

Note that even with the merge of #89, these errors still occur.

One potential solution to this is to not use an atexit handler to shut down the cluster.  Instead, require that the user shutdown the cluster manually at the end of the script.  This would effectively mean that the canonical use case of dask_mpi.initialize() would change from:
initialize()

with Client() as c:
    # dask stuff

with the Client.shutdown() method called by the atexit handler, to
initialize()

with Client() as c:
    # dask stuff
    c.shutdown()

with the c.shutdown() call above being required or the process will hang.  We could even encapsulate the c.shutdown() in a function that bookends the initialize() method like so:
def finalize(...):
    with Client() as c:
        c.shutdown()

so that the dask-mpi client script might look like:
initialize()

with Client() as c:
    # dask stuff

# maybe more stuff

finalize()

However, this definitely breaks backwards compatibility.  It does fix the above hanging, though.  Is this acceptable?
CC @mrocklin @jacobtomlinson

Possible API changes
If we have to break backwards compatibility, then I want to suggest some other changes that might work with the suggested changes above.
With @joezuntz's changes to allow users to pass into Dask-MPI an existing MPI communicator object and turn off explicit "shutdown" of the Dask cluster, there is now a foreseeable mechanism for stopping/restarting a Dask-MPI cluster from within a client batch process.  With my understanding, I think this requires 3 components:

a Dask-MPI initialize() function that starts the scheduler and worker processes and subsequently block on all MPII ranks except the client rank (e.g., rank==1),
a Dask-MPI is_client() function that returns True when the MPI rank is equal to the client rank, and
a Dask-MPI finalize() function that stops the scheduler and worker processes.

The general outline of how to use these three functions together would be like so:
from dask_mpi import initialize, is_client, finalize

initialize()  # Blocks scheduler and worker MPI ranks HERE!!!

if is_client():
    # Do your client dask operations here
    # When the scheduler and worker MPI ranks unblock due to the finalize call below,
    # this section will be skipped by the scheduler and worker MPI ranks

finalize() # Everything after this can act like a normal mpi4py script

...This whole thing is starting to look to me like a context manager, no?

I wonder if using a context manager would feel more natural here.
def initialize(...):
    with Client() as c:
        ...

@jacobtomlinson:  Yeah.  I was thinking of something like:
with MPICluster(...) as cluster, Client(cluster) as c:
    if cluster.is_client():
        ...

where the MPICluster(...) object would essentially be the initialize(...) method, except turned into a context manager with finalize() being called in __exit__().
...but I don't like the nested if pattern.  It's fiddly and prone to errors, I think.

This is kind of where I was going with the MPIRunner class in https://github.com/dask/distributed/pull/4710 and https://github.com/dask/dask-mpi/pull/69. The Cluster class doesn't quite line up with the use case here, given that the job and resources already exist and we are trying to populate them, rather than create them in the first place. This is why I tried to add Runner and a sibling to Cluster for this use case.
However @mrocklin suggested that Cluster would be a fine way to implement it and adding a new base class only increases complexity. So perhaps it would be good to resurrect #69 but base it on Cluster instead.

same issue here. I will try python3.8 for now

Experience the same.
Can we think of some temporary workaround here? Maybe closing the MPI cluster manually after the c.shutdown or "request killing the workers/check worker count/repeat again if needed/close scheduler"? I do already implement exiting logic manually, so that I don't mind adding a few more lines...

Yeah. If you have time for a PR, that would be great, @evgri243!


How to consume Custom Vision Object Detection ONNX models

Create new how-to guide / tutorial that shows how to consume an Custom Vision Cognitive Services object detection ONNX model with ML.NET

Add note on how to use GPU when scoring ONNX models

@luisquintanilla @gewarren I may double check this to make sure this is compatible with ML.NET 3, as well.


WebApp:webapp log tail error: Unable to find {} in RG

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp log tail
Errors:
The command failed with an unexpected error. Here is the traceback:
'str' object has no attribute 'value'
Traceback (most recent call last):
  File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 2282, in get_streaming_log
    scm_url = _get_scm_url(cmd, resource_group_name, name, slot)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 1948, in _get_scm_url
    webapp = show_webapp(cmd, resource_group_name, name, slot=slot)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 607, in show_webapp
    return _show_app(cmd, resource_group_name, name, "webapp", slot)
  File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/appservice/custom.py", line 736, in _show_app
    "Unable to find {} '{}', in RG '{}'".format(cmd_app_type.value, name, resource_group_name),
AttributeError: 'str' object has no attribute 'value'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp log tail --name rowa-dwmerge-prod-weu-func --resource-group rowa-dw-prod-weu-rg --subscription c503cf0c-3593-45d4-9d77-f0a6aac758ff

Expected Behavior
Environment Summary
Linux-5.4.0-1062-azure-x86_64-with-debian-10.2 (Cloud Shell), Common Base Linux Delridge (quinault)
Python 3.6.10
Installer: DEB

azure-cli 2.29.0 *

Extensions:
ai-examples 0.2.5
ssh 0.1.6

Additional Context

Fix has been released. Please upgrade to Azure CLI 2.29.1


AFT Cost in AWS Account

Hi,
What is the cost of the product in the AWS Account. Infra Cost I mean, Nat Gateway, endpoints etc
Thanks for your help

Hi there. You can find more info about the cost of AFT in the pricing section of the AFT documentation, including links to pricing details for the services you mentioned. That said, much of the cost of AFT is contingent on how AFT is configured and used in your accounts. If you need a more detailed cost analysis, reach out to your AWS account representative or AWS Premium Support.


integrate fastchat with langchain

Here is the official document about this integration https://github.com/lm-sys/FastChat/blob/main/docs/langchain_integration.md

This has been verified. The fastchat apiserver works very well with langchaingo


[BUG] spark400 build failed do not conform to class UnaryExprMeta's type parameter

Describe the bug
It appears that Spark 400 has updated the function signature. We have seen 2 occurrences today,
https://github.com/NVIDIA/spark-rapids/actions/runs/10918070452/job/30303402686
https://github.com/NVIDIA/spark-rapids/actions/runs/10915156719/job/30294484216
Error: ] /home/runner/work/spark-rapids/spark-rapids/sql-plugin/src/main/scala/com/nvidia/spark/rapids/GpuOverrides.scala:2406:
type arguments [org.apache.spark.sql.catalyst.expressions.Rand]
do not conform to class UnaryExprMeta's type parameter bounds
[INPUT <: org.apache.spark.sql.catalyst.expressions.UnaryExpression]

Steps/Code to reproduce bug
build with spark400
Expected behavior
Pass the build and test
Environment details (please complete the following information)

Environment location: [Standalone, YARN, Kubernetes, Cloud(specify cloud provider)]
Spark configuration settings related to the issue

Additional context
Add any other context about the problem here.

related to change https://github.com/apache/spark/pull/48004

I am taking a look


Attempt to guess the state by IP address

I'm not in India to test this out.
@captn3m0 @championswimmer @shreyas-satish ?

Site doesn't work because of mixed content warning.

@captn3m0 Bleh - switched to a service that has HTTPS support. Now?

@karthikb351 It is still enforcing UP, since that is set later after vue is initialized. Can you move the code to created method?
Add it in the mp switch/case

It's breaking but it is probably netlify's fault since my local version seems to load correctly.  It picks the correct state too.


Log Viewer should take full height of panel

Describe the bug
Because the Log Viewer is expandable, it follows that the actual log height should take the full height of the panel it's in.

Browser: Chrome

Closing as I hadn't seen https://github.com/KaotoIO/kaoto-ui/issues/577 yet :)


Fix allow-all NetworkPolicy

Empty NetworkPolicyPeer is supposed to match all addresses. This patch
corrects the implementation and slightly adjusts the log message to view
necessary fields of rules only.
Related to #131

/test-e2e

/test-e2e

/test-e2e

/test-e2e

/test-e2e


[FirebaseDatabase] Databases are disconnected temporarily on app goes inactive state.

Description
Since v10.27.0, FirebaseDatabase now temporarily goes offline when the app is in the inactive state (e.g., when control center is opened, when returning to the home screen, etc.) and comes back online after a while.
In v10.26.0, the behavior was below:

but is in v10.27.0 or later:

Reproducing the issue

Create iOS App project
Integrate Firebase project and add FirebaseDatabase package
Replace App code with like this:

import SwiftUI
import UIKit
import FirebaseCore
import FirebaseDatabase

@main
struct RtdbReproIOSApp: App {

    @UIApplicationDelegateAdaptor (AppDelegate.self) var appDelegate

    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

class AppDelegate: NSObject, UIApplicationDelegate {
    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
        FirebaseApp.configure()

        let connectedRef = Database.database().reference(withPath: ".info/connected")
        connectedRef.observe(.value, with: { snapshot in
          if snapshot.value as? Bool ?? false {
            print("Connected")
          } else {
            print("Not connected")
          }
        })

        return true
    }
}

Firebase SDK Version
10.27.0
Xcode Version
15.3
Installation Method
Swift Package Manager
Firebase Product(s)
Database
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet

{
  "originHash" : "c63c63846d9c539229e96de38d6af51417e28c0ee9a0bc48bd0f0f19d923c329",
  "pins" : [
    {
      "identity" : "abseil-cpp-binary",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/abseil-cpp-binary.git",
      "state" : {
        "revision" : "194a6706acbd25e4ef639bcaddea16e8758a3e27",
        "version" : "1.2024011602.0"
      }
    },
    {
      "identity" : "app-check",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/app-check.git",
      "state" : {
        "revision" : "3b62f154d00019ae29a71e9738800bb6f18b236d",
        "version" : "10.19.2"
      }
    },
    {
      "identity" : "firebase-ios-sdk",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/firebase-ios-sdk",
      "state" : {
        "revision" : "8bcaf973b1d84e119b7c7c119abad72ed460979f",
        "version" : "10.27.0"
      }
    },
    {
      "identity" : "googleappmeasurement",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleAppMeasurement.git",
      "state" : {
        "revision" : "70df02431e216bed98dd461e0c4665889245ba70",
        "version" : "10.27.0"
      }
    },
    {
      "identity" : "googledatatransport",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleDataTransport.git",
      "state" : {
        "revision" : "a637d318ae7ae246b02d7305121275bc75ed5565",
        "version" : "9.4.0"
      }
    },
    {
      "identity" : "googleutilities",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/GoogleUtilities.git",
      "state" : {
        "revision" : "57a1d307f42df690fdef2637f3e5b776da02aad6",
        "version" : "7.13.3"
      }
    },
    {
      "identity" : "grpc-binary",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/grpc-binary.git",
      "state" : {
        "revision" : "e9fad491d0673bdda7063a0341fb6b47a30c5359",
        "version" : "1.62.2"
      }
    },
    {
      "identity" : "gtm-session-fetcher",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/gtm-session-fetcher.git",
      "state" : {
        "revision" : "a2ab612cb980066ee56d90d60d8462992c07f24b",
        "version" : "3.5.0"
      }
    },
    {
      "identity" : "interop-ios-for-google-sdks",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/interop-ios-for-google-sdks.git",
      "state" : {
        "revision" : "2d12673670417654f08f5f90fdd62926dc3a2648",
        "version" : "100.0.0"
      }
    },
    {
      "identity" : "leveldb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/leveldb.git",
      "state" : {
        "revision" : "a0bc79961d7be727d258d33d5a6b2f1023270ba1",
        "version" : "1.22.5"
      }
    },
    {
      "identity" : "nanopb",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/firebase/nanopb.git",
      "state" : {
        "revision" : "b7e1104502eca3a213b46303391ca4d3bc8ddec1",
        "version" : "2.30910.0"
      }
    },
    {
      "identity" : "promises",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/google/promises.git",
      "state" : {
        "revision" : "540318ecedd63d883069ae7f1ed811a2df00b6ac",
        "version" : "2.4.0"
      }
    },
    {
      "identity" : "swift-protobuf",
      "kind" : "remoteSourceControl",
      "location" : "https://github.com/apple/swift-protobuf.git",
      "state" : {
        "revision" : "e17d61f26df0f0e06f58f6977ba05a097a720106",
        "version" : "1.27.1"
      }
    }
  ],
  "version" : 3
}

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet

Replace this line with the contents of your Podfile.lock!

Thanks for reporting this, @Kurogoma4D. I was able to reproduce the issue. I'll raise this to our engineers and see what we can do here.


Fix webpack hanging under certain circumstance, use process.exitCode instead of process.exit in compilerCallback

What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
No. It's hard to write test and maybe it is not necessary.
Summary

According to Node.js document, it is not correct to write something like

console.log('hello, world');
process.exit()

https://nodejs.org/dist/latest-v9.x/docs/api/process.html#process_process_exit_code

Rather than calling process.exit() directly, the code should set the process.exitCode and allow the process to exit naturally by avoiding scheduling any additional work for the event loop:

There is an issue https://github.com/webpack-contrib/sass-loader/issues/523 fixed by this pull request.

The issue is that Node.js doesn't exit itself after the process.exit(1) in line 367 of webpack.js.
Some callbacks of fs.stat and fs.readFile were never called at this time.
I am not familiar with Node.js and libuv. The following is my guess.
webpack calls fs functions many times, and they will use the thread pool of libuv.
node-sass will use the same thread pool to do its work.
After the call to process.exit(), the fs functions will fail silently and won't release their threads, but node-sass is waiting for threads and process.exit() is waiting for node-sass.
Does this PR introduce a breaking change?
No.

@crvv is this still supported for node 6, 8? You mention 9 in your document.

Those words was added in Node.js 6.0 document.
https://nodejs.org/dist/latest-v6.x/docs/api/process.html#process_process_exit_code

@TheLarkInn According to the docs, process.exitCode is added in v0.11.8.

Thanks


feat: merging the features

:tada: This issue has been resolved in version 1.1.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0-develop.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Extensions: Expose version of VS Code

My extension sends telemetry via Application Insights and it'd be great to have access to the version of VS Code used with the extension.  I found how VS Code gets that version for the Help | About dialog, but it doesn’t appear to be exposed to extensions (e.g., via env or ExtensionContext

VSCode Version: 1.10.1
OS Version: Win10

tata: vscode.version


Folded blocks in YAML cause extra line breaks

When generating code from a YAML schema definition that uses folded blocks for descriptions, the comments in the generated output code have a trailing comment line.
The issue may be related to go-yaml/yaml#789.
Example
Input
"$schema": "http://json-schema.org/draft-04/schema#"
"$id": "https://example.com/yaml_formatting"

title: MyObject
type: object
properties:
  foo:
    description: >
      I'm a multiline description in a folded block. Folded blocks should not
      have hard line breaks after parsing. They should also not end in a line break.
    type: string
  bar:
    description: |
      I'm a multiline description in a literal block. Literal blocks, on the other hand,
      should have hard line breaks and may end in a line break, too.

      This may look funky when Go code is generated to a specific line width, though.
    type: string

Expected Output
// Code generated by github.com/atombender/go-jsonschema, DO NOT EDIT.

package test

type YamlMultilineDescriptionsYaml struct {
	// I'm a multiline description in a literal block. Literal blocks, on the other
	// hand,
	// should have hard line breaks and may end in a line break, too.
	//
	// This may look funky when Go code is generated to a specific line width, though.
	//
	Bar *string `json:"bar,omitempty" yaml:"bar,omitempty"`

	// I'm a multiline description in a folded block. Folded blocks should not have
	// hard line breaks after parsing. They should also not end in a line break.
	Foo *string `json:"foo,omitempty" yaml:"foo,omitempty"`
}

Actual Output
// Code generated by github.com/atombender/go-jsonschema, DO NOT EDIT.

package test

type YamlMultilineDescriptionsYaml struct {
	// I'm a multiline description in a literal block. Literal blocks, on the other
	// hand,
	// should have hard line breaks and may end in a line break, too.
	//
	// This may look funky when Go code is generated to a specific line width, though.
	//
	Bar *string `json:"bar,omitempty" yaml:"bar,omitempty"`

	// I'm a multiline description in a folded block. Folded blocks should not have
	// hard line breaks after parsing. They should also not end in a line break.
	//
	Foo *string `json:"foo,omitempty" yaml:"foo,omitempty"`
}

I'm opening a PR to address this. The PR changes the yaml library, which I'm not sure you are happy to do.

changes merged in #52


[BUG] Chart/Values.yml:defaultDataPath not utilized/respected

Please note:
Values.yml:  defaultDataPath: ""
Is not implemented in chart:longhorn/daemonset-sa.yaml
  - name: longhorn
    hostPath:
      path: /var/lib/longhorn/

The /var/lib/longhorn path in chart:longhorn/daemonset-sa.yaml is where Longhorn store engine-binaries and it is harder coded into the manage daemonset.
the Values.yml: defaultDataPath is where Longhorn store volumes' replica and it is configurable by users.
So, they are 2 different concepts.


Improve Location docs and tests

Improve Location.timezone documentation
Add tests for the Location.timezone lookup

The PR is blocked due to missing release notes. For me this is okay as is, but please lemme know if you want to add a release note for this, and need another review.

I will skip them, as it is just a minor documentation improvement.


Easier Objects Import

Importing objects right now requires to know the filenames inside of the objects directory. Instead, I propose importing all the relevant objects into the objects/__init__.py file so that objects can be imported like this:
from quickbooks.objects import Customer, Invoice

Let me know what you guys think. If you'd like, I can submit a PR for this change.

Sounds good. Create a PR and I will merge it in.

So while doing this I found a few cases of redefinitions. Let me know how you'd like to handle them:

[ ] AttachableRef in base.py and deposit.py
[ ] DescriptionLineDetail being defined twice in detailline.py
[ ] DescriptionLineDetail being defined in detailline.py and journalentry.py
[ ] DescriptionOnlyLine being defined in detailline.py and journalentry.py

@ej2 Just bumping this up in case you missed it

@ej2 Not sure if you saw the 4 redefinitions I mentioned above. Are you okay with those?

I did. Thank you for bringing them to my attention. They have been fixed in the latest release.

Okay perfect!


Parser updates

Hi Steve,
Some small updates, the parser issues around spaces at the start of element names should be fixed now, and the parser will no longer accept duplicate attribute names.
I've also dipped my toes in the XSLT processor if thats alright, just did a basic change to add support for "disable-output-escaping" on text nodes... I am sure that'll be replaced when xsl:character-map gets implemented anyway.

Regarding getting into the XSLT code... go right ahead!

Thanks!


more visibility to setting

Fixes #2821
This PR creates a new article under "What's New in C#" for configuring the language version.  That article lists all the versions, and describes the common methods for setting it.
There were a number of locations in the C# Guide that referenced setting the LangVersion element. Those have been consolidated in the new article, and the previous locations point to the new article.
I've marked it as WIP because I have two remaining tasks and questions:

[x] The msbuild / CLI documentation does not reference the LangVersion element. It should. @mairaw which article would you recommend updating?
[x] Parallel changes and a new article should be made in the VB guide. @rpetrusha if you like this direction, I'll make the changes in the VB Guide as well.

You could also include a section describing how to set it for a complete solution at once using a Directory.Bulid.props file.

In terms of the LangVersion in the VB docs, I completely agree that adding it would be great. If you want me to do it, let me know, @BillWagner.

Regarding documenting the LangVersion element, we don't have that topic yet @BillWagner. It has been forever in my backlog to create the csproj reference (issue #2642)/

Thanks for the answers.
@dasMulli I added as section on using the Directory.build.props file.
@rpetrusha The last commits have the VB versions
@mairaw I added a comment on #2642 to note these new files.

@rpetrusha I updated this based on your feedback. It should be ready for another review.

Build seems stuck. I'll close and reopen this PR.


global: add special role any_users and authenticated_users

related to #56 and #124

Looks good to me as well - let's discuss tomorrow the details, but I think System role might be better than Special role (and define system roles as roles that are managed by the system and automatically assigned to users)? WDYT?

updated so we use system role instead

Merged in https://github.com/inveniosoftware/invenio-access/tree/feature-refactor


Search method is not working with list query

Tweepy 3.10.0
Since yesterday, query search with list:user/slug is not working.
query = "list:easoncxz/nz-official"
x = list(tweepy.Cursor(api.search, q=query).items(20))
print(len(x))
# → 0

This query is working in the web version.
https://twitter.com/search?q=list%3Aeasoncxz%2Fnz-official&src=typed_query&f=live
Normal search appears to be working correctly.
query = "twitter"
x = list(tweepy.Cursor(api.search, q=query).items(20))
print(len(x))
# → 20

https://twitter.com/search?q=twitter&src=typed_query&f=live

list:list_id is not working as well.
query = "list:1248785315763859456"
x = list(tweepy.Cursor(api.search, q=query).items(20))
print(len(x))
# → 0

web version.
https://twitter.com/search?q=list%3A1248785315763859456&src=typed_query&f=live

Did this use to work?
This seems like an issue with Twitter's API rather than Tweepy, as it is listed as a standard search operator.
Possibly already reported already as well: https://twittercommunity.com/t/standard-search-operator-list-username-slug-returning-empty-statuses/150302

See also https://twittercommunity.com/t/list-search-does-not-work-with-twitter-api-v1-1/151076.


Investigate dotnet/extensions ExcludeFromSourceBuild projects

This dependency closure in particular is causing problems with the mixed locally-built/downloaded smoke-test packages from #2375.
$ dotnet new worker

The template "Worker Service" was created successfully.

Processing post-creation actions...
Running 'dotnet restore' on hello-worker/hello-worker.csproj...
Determining projects to restore...
hello-worker/hello-worker.csproj : error NU1605: Detected package downgrade: Microsoft.Extensions.DependencyInjection from 5.0.2 to 5.0.0. Reference the package directly from the project to select a different version.
hello-worker/hello-worker.csproj : error NU1605:  hello-worker -> Microsoft.Extensions.Hosting 5.0.0 -> Microsoft.Extensions.Logging 5.0.0 -> Microsoft.Extensions.DependencyInjection (>= 5.0.2)
hello-worker/hello-worker.csproj : error NU1605:  hello-worker -> Microsoft.Extensions.Hosting 5.0.0 -> Microsoft.Extensions.DependencyInjection (>= 5.0.0)

[Triage] These package have moved to runtime.  Closing as obsolete.