Use my own self-signed certificate for development instead of "dev-certs"

URL
https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/run
Operating system
windows
More information about your system
I have a .pfx file created with openssl in Linux. I'd rather use that cert when creating a new blazor project. I of course would prefer not to put the private key password in code if at all possible. Is there an environment variable I can use that would contain a hash or reference to a secure location containing the private key? global.json file containing Kestrel directives to allow me to use my own cert?
Description
fail: Microsoft.Extensions.Hosting.Internal.Host[11]
Hosting failed to start
System.InvalidOperationException: Unable to configure HTTPS endpoint. No server certificate was specified, and the default developer certificate could not be found or is out of date.
To generate a developer certificate run 'dotnet dev-certs https'. To trust the certificate (Windows and macOS only) run 'dotnet dev-certs https --trust'.
For more information on configuring HTTPS see https://go.microsoft.com/fwlink/?linkid=848054.
dotnet --info
dotnet --info
.NET SDK:
Version:           8.0.204
Commit:            c338c7548c
Workload version:  8.0.200-manifests.7d36c14f
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.22631
OS Platform: Windows
RID:         win-x64
Base Path:   C:\Program Files\dotnet\sdk\8.0.204\
.NET workloads installed:
There are no installed workloads to display.
Host:
Version:      8.0.4
Architecture: x64
Commit:       2d7eea2529
.NET SDKs installed:
6.0.200 [C:\Program Files\dotnet\sdk]
6.0.202 [C:\Program Files\dotnet\sdk]
6.0.203 [C:\Program Files\dotnet\sdk]
8.0.204 [C:\Program Files\dotnet\sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Other architectures found:
x86   [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]
Environment variables:
Not set
global.json file:
Not found
Learn more:
https://aka.ms/dotnet/info
Download .NET:
https://aka.ms/dotnet/download

@danroth27 can you help with this issue? Thanks.

Thanks @danroth27 these links helped me work through this issue, although I'm not totally clear on how "dotnet user-secrets set "foo:bar" "baz"' is any different from storing passwords in an ENV: variable, security-wise?

I'm not totally clear on how "dotnet user-secrets set "foo:bar" "baz"' is any different from storing passwords in an ENV: variable, security-wise?

The User Secrets tool is just a development time tool for storing config values outside of your project folder so they don't get accidentally end up in source control. It's really just another JSON file that lives in your user profile on your dev box. An environment variable would work tool. The config system in ASP.NET Core can read from a variety of different configuration stores.


Documentation of new cqui_settings_local.sql

Change name of new file to cqui_settings_local as discussed in PR #430.
Finished the implementation of #329.
Documentation (en/de) changed to new solution.

Except the small typo I commented on I think it looks good.

@SpaceOgre Thanks

Sorry, you changed it wrong... I will correct it in the evening.


Fix more pathologic lock creation slowness.

Although #1707 was on the right track, it missed a small corner case
with partial order operators acting against patch versions of zero. More
importantly, it missed trimming the final set of versions picked using
the specifier in question once up-front. This up-front trimming pays
large amortized dividends, cutting resolve times in half or more in some
cases.
Fixes #1722

The pathologic case presented in #1722 is improved to complete with the partial order / patch 0 check to:
$ rm -rf ~/.pex && time python -mpex.cli lock create --output=lock.json --style universal --resolver-version pip-2020-resolver --indent 2 --interpreter-constraint "CPython<3.10,>=3.8" -r requirements.txt

real	3m30.979s
user	2m51.152s
sys	0m1.212s

And then improved further with the filtering of the picked version set against the specifier in question to:
$ rm -rf ~/.pex && time python -mpex.cli lock create --output=lock.json --style universal --resolver-version pip-2020-resolver --indent 2 --interpreter-constraint "CPython<3.10,>=3.8" -r requirements.txt

real	1m20.675s
user	0m58.387s
sys	0m1.114s


get_essence_data not working for all APIs

The get_essence_data() function does not work with all APIs. Below is an example, copied directly from ESSENCE with no modifications:

url <- "https://essence2.syndromicsurveillance.org/nssp_essence/api/tableBuilder?datasource=va_hosp&startDate=1Jan2013&medicalGroupingSystem=essencesyndromes&userId=5099&endDate=9May2023&percentParam=noPercent&site=934&hospFacilityType=emergency%20care&aqtTarget=TableBuilder&geographySystem=hospital&detector=nodetectordetector&timeResolution=daily&hasBeenE=1&rowFields=timeResolution&columnField=site"

data <- Rnssp::get_essence_data(url)

returns error: Error in Rnssp::get_essence_data():
! URL is not of ESSENCE type. Check your URL or use get_api_data() instead!
I do not want to use get_api_data() for a number of reasons, the big one being that I still have to manipulate it into a data frame and the point of get_essence_data() is to avoid the extra required steps every time.
When I run my version of get_essence_data() it works:

function(url, start_date = NULL, end_date = NULL) {

  api_type <- str_extract(url,"(?<=api/).+(?=\\?)")

  url_new <- Rnssp::change_dates(url, start_date, end_date)

  if (api_type == "timeSeries") {
    api_response <- myProfile$get_api_response(url_new)
    api_response_json <- content(api_response, as = "text")
    api_data <- fromJSON(api_response_json) %>%
      extract2("timeSeriesData")
  } else if (api_type == "timeSeries/graph") {
    api_png <- myProfile$get_api_tsgraph(url_new)
    knitr::include_graphics(api_png$tsgraph)
  } else if (api_type == "tableBuilder") {
    api_data <- myProfile$get_api_data(url_new)
  } else if (api_type == "tableBuilder/csv") {
    api_data <- myProfile$get_api_data(url_new, fromCSV = TRUE)
  } else if (api_type == "dataDetails") {
    api_data <- myProfile$get_api_data(url_new) %>%
      extract2("dataDetails")
  } else if (api_type == "dataDetails/csv") {
    api_data <- myProfile$get_api_data(url_new, fromCSV = TRUE)
  } else if (api_type == "summaryData") {
    api_data <- myProfile$get_api_data(url_new) %>%
      extract2("summaryData")
  } else if (api_type == "alerts/regionSyndromeAlerts") {
    api_data <- myProfile$get_api_data(url_new) %>%
      extract2("regionSyndromeAlerts")
  } else if (api_type == "alerts/hospitalSyndromeAlerts") {
    api_data <- myProfile$get_api_data(url_new) %>%
      extract2("hospitalSyndromeAlerts")
  } else {
    writeLines("Error: API did not work as expected. Please check your URL, dates, and password before trying again.")
  }

}

Thank you @sara-chronister for reporting this bug in the get_essence_data() function. A patch will be pushed shortly to the development version of the package. The fix will ultimately be part of the next version (Rnssp v0.2.1) of the package when we release it.
Again, thank you so much for your contribution.

Hi @sara-chronister , I pulled using the URL you provided with the get_api_data() function and it does not require to manipulate the api response into a data frame.
Before the release of the upcoming patch version, the get_api_data() function may be used without the need to manipulate the response into a dataframe.

A fix has been pushed to the dev branch. Feel free to check it. Again, this bug fix will be part of Rnssp v0.2.1 when we release it.


chore: Add @StackScribe to MAINTAINERS list

@mowies I don't actually want to merge anything except adding my name to the CONTRIBUTORS.md and MAINTAINERS files.  But I can't seem to get a.clean branch where I can do just that.  When I go into my fork and try to fetch updates, it gives me a button to create a PR and merge -- is that normal for keptn//keptn or is my fork just screwed up?  I thought I added myself to CONTRIBUTORS a while ago but apparently not.  Aargh!  Any advice as to how I can clear this all up?

This PR needs a rebase...

@StackScribe I will close it since there is no activity. Feel free to reopen


Update rate limits for package push & unlist APIs

Docs change for https://github.com/NuGet/NuGetGallery/issues/4679.
DO NOT MERGE YET! To be merged when change is live.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/rate-limits.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OK, just say when.

Now would be good :)


[ASTWalker] Don't visit capture list vars twice

Previously we were walking them once when visiting the capture list, and then again as a part of the pattern binding decl. Change the logic to only visit them as a part of their pattern binding decl.
This fixes a bug that's exposed by https://github.com/apple/swift/pull/37720. Because it requires that change to reproduce, I'll be adding the test case there.

@swift-ci please test

@swift-ci please test source compatibility

Source compat failures unrelated

LGTM

@swift-ci please test Windows


Implementation specific Common Lisp fixups

Work involving fixups of warnings and other routines to minimize dependencies on proprietary lispworks libraries, and in general just conform more to ANSI Common Lisp, which involves fixing numerous error/warnings caught by SBCL

Hi, are there any bite-sized portions you can direct new contributors to?
I've only read about Boxer and would love to finally play with it / help porting to fully open-source lisps, but I can't commit to much spare time.  A few hours here and there...
I mainly run linux (but can get windows VM).  It's been some years since I played with scheme and CL.  And I'm not yet familiar with any boxer internals.
So far I tried the instructions on Linux with Lispworks Personal Edition, and run out of heap :shrug:

Hi @cben !  It's a good idea to have some introductory tickets, I'll try and put a few together, and tag them appropriately.  Yeah, I'm familiar with the heap issue on the Lispworks Personal edition, haven't taken any time to look at it, or even decide if it's possible. (I'm not sure what the size limitation actually is).   Thanks for checking in, I'd like to make things more palatable to newcomers.

Greetings! I just learned about the Boxer-sunrise project.
I'm in a similar position to @cben, I've forgotten far more about Boxer than I remember from my days in the Hal & Andi group in 1982.  I took a freshman seminar course that used "Turtle Geometry" as the textbook.
Since the 80's, I've spent time developing stuff on Linux (70%), MacOS (10%), and Windows (20%)
Some of my interests are:

Porting Boxer to run on Linux (which I realize might not be possible just yet)
Running on ARM platforms like Raspberry Pi (which is 64-bit, but the Lisp environment is a 32-bit app)
Exploring Vulkan bindings and modern/ portable "media layers"  - a environment for exploring music and sound would be neat
Building authoring environments (I did professional stack development on HyperCard for a while).

BUT, I need to start with something achievable, and relearn a modern Boxer

Hi @ralphw !
That's great to hear about your Turtle Geometry days, it really is a great book.
So, a few things.  I did have a trial license of lispworks for linux for a bit, and I did make the changes so that it would run on Linux.  CAPI still uses GTK+ 2.x, so it's pretty old school looking, but it did work. As you mention I've also noticed that it runs out of heap space on the free version.
I have been working on getting more and more of the source to run on straight ECL or SBCL.  What lisp distributions do you sort of actively use? There could be some overlap there.  I saw a demo of an ECL repl running in wasm last month, and I'm quite excited about potentially running the core evaluator in a browser with WASM, and a webGL frontend, perhaps using pixi.js or something... just because it's so much manual effort to support native OpenGL usage across linux/macOS/windows. But I'm just brainstorming at the moment.
Just as a start have you been able to run any of the release binaries on macOS? (based on your post, I'm assuming you probably own at least one machine that runs macOS for the 10% of your dev time).
Cheers and welcome!

I'm kind of adopting SBCL for the time being.
TBH, It's been about 12 years since I've touched any Lisp code, I was using scala on my last contract project.
I do IT security full-time now, so there's less software work involved in that, but more python, and Ruby.
I'll give the binaries a try, I'm looking at getting a M1 Mac this winter, my Mac Pro is a bit too old to run current MacOS releases.
Linux is my daily driver for most things.


Initial support for PDF/A-1a/b

Feature

What kind of change does this PR introduce?
These changes add initial support for PDF/A-1a and PDF/A-1b which targets a profile for long-term archiving.
In order to create PDF/A files, set 'pdfa' to either '1a' or '1b' in the options of the PDFDocument.
Note: PDF/A does not support encryption and other things detailed in the docs or in the standard. This change does not prevent you from creating encrypted PDFs even if pdfa option is enabled - in those cases, your PDF may not pass PDF/A validation. This means it's down to the user to ensure all other features that are restricted from PDF/A standard are not enabled.

Checklist:

[x] Unit Tests
[x] Documentation
[x] Update CHANGELOG.md
[x] Ready to be merged

This change will currently support only PDF/A 1b and 1a ( 1a only when tagged is set to true ). If you're happy with the changes, I can continue adding support for other PDF/A standards: 2a, 2b, 2u, 3a, 3b, 3u, 4e, 4f.

@blikblum
Thanks! I agree - XML metadata should be able to replace the /Info, but I think metadata streams were added only in 1.4, therefore we'd still need to use /Info for 1.3?
Yes we can certainly store the colour profile separately - will create a folder and we can have each in their own file.
In terms of testing, I think the most reliable way would be to run verapdf's binary tool to check against the subset/profile defined in the generated pdf - otherwise we quickly find ourselves re-implementing every test and reinventing the wheel (e.g. PDF/A-1: https://github.com/veraPDF/veraPDF-validation-profiles/wiki/PDFA-Part-1-rules/)

@blikblum
I've added a more general mixin for controlling the metadata and changed it so pdf versions 1.3 uses /Info and pdf versions >1.3 do not show a /Info but rather store the info as metadata.
Although it works fine and passes PDF/A-1 validation, software like Finder's 'Get info' does not seem to parse the info stored as metadata on Monterey 12.6.
Even if it's down to each implementation to decide whether to follow the standard, I think the extra space to store the info both in /Info and /Metadata might be worth it in order to support implementation that do not parse the metadata?

AFAIR from reading the spec is fine having both /Info and /Metadata

In terms of testing

The testing is just checking is the produced output is the intended (see other tests), mostly to avoid regressions in future development

@blikblum
Should be done now! Added tests for metadata and pdfa1 subset, plus we now have /Info and /Metadata for pdf version >=1.4 and only /Info for pdf version 1.3 (added test for this too in document.spec.js).

Hey guys, sorry to be pushy - would it be possible to merge this if you're all happy? Was hoping to include the PDF/A support in our next Beta and didn't want to use a fork :/

I'm not a developer of pdfkit, so my approval for this request will not have any value.
As I'm just a user of pdfkit, I can't help you to make progress, sorry.

@blikblum Any other feedback for this PR to get approved?

Looks pretty good to me. I'll merge and wait a week or so before doing the release to see if other maintainers have objections
The only improvement i see in future is loading the profile info in demand so those that don't need can save a few kb


Issue Notes should be less ephemeral

Typical flow:

Find item with issue.
Issue uses policy statement as a note.
Justify issue.
Policy statement changes.
Issue seen as "fixed" and replaced with a new unjustified issue.

Super annoying to lose justifications in this way.
Should probably stop dumping policy statements into the notes field.  It may be important to review all the auditors and consider changing them.
Alternatively, the ItemAudit table could have a new "ephemeral_notes" column.  The display of the issue would be the concatenation of the current notes column with the new ephemeral_notes column.  The ephemeral_notes column would not be used when determining whether an issue currently exists, so things like policy statements could be placed there.
I'll leave this issue open for a few days.  Please leave your thoughts or suggested fixes.

Example issue:
Issue: IAM Role has IAM privileges.
Score: 9
Notes: {"Action": [...,iam:something,...]}

I'm going to annoyingly tag a few people for their thoughts now :)  No rush.
@ollytheninja @cstewart87 @aebie @markofu @bunjiboys @crruthe @mikegrima

@monkeysecurity this approach with the "ephemeral_notes" column seems reasonable to me.

@monkeysecurity I agree with @markofu that ephemeral_notes is reasonable, but I am looking at some "IAM Role has IAM privileges." issues and some of the actions are really lengthy and clutter the screen. It seems redundant to list the action too since the config is already right there. I think maybe this is not a proper use of the notes field.

I agree with removing the policy dumps from the notes field.  However, I'm struggling with why you would add a new "ephemeral_notes" column instead of just making the existing "notes" column ephemeral.  What's the requirement for using "notes" to determine whether an issue exists?

Fixed in #564.


App crashes when Video call is made

On clicking either the Phone icon or the Video call icon, the app crashes.

Let's see how we can debug this.

Does it work on messenger.com?
Have you managed to build the app yourself so far?

Yes both when clicked, open a new window for the call
I did download the repo and ran node build.js after installing the dependencies

Can you please do these steps:

go to ./src/package.json
change toolbar: false to true
build the app and run it
there's a cog icon near the address bar, press that and it should open a chrome dev tools window
tell me what is in there, and do you notice anything when clicking the voice call button? i.e. does any error appear there?

What OS are you running?

I am running Ubuntu 14.04 32-bit, I have attached a screenshot of the dev tools window

Thanks. Is this all that appears in the dev tools window? Those errors are about something else. I don't know why it would crash.

Well, I am not familiar of how to catch those errors, when I click on either of the buttons, I can see a new window trying to open up but then it closes and thereby everything closes including the tray icon.

I still have no clue. We'll see if more users report this, so far you seem to be the only one. Have you tried updating? There's a new release (v1.2.2).

Downloading and building it now.

Or you can just download from here https://github.com/Aluxian/Facebook-Messenger-Desktop/releases

Oops, didn't see the link. Anyway built it and ran now.  :/

Same crashing happening with me.


[Azure Cognitive Search] Various Swagger improvements

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

/azp run automation - sdk

@jhendrixMSFT Please merge. The usual disclaimer about the backcompat errors apply (we haven't GA'd any libraries generated from this Swagger yet).

@mayurid can you please merge?


"transient local" required on both ends

I recognize that it is typical to require the same QoS settings on both subscriber and receiver. However, I believe some forgiveness is in order in this regard. DDS and ROS's QoS support the idea of publishers that send their most-recent data to each new subscriber automatically. The ROS QoS uses "durability" for the name of this feature. You can set your QoS to a durability of "transient local" to keep data in RAM for sending it to each new subscriber. When using CoreDX, I'm required to specify "transient local" on the receiver as well.  I find that somewhat annoying. I can understand why a "reliable" connection would need to be specified on both ends, and with the rolling history setting it seems you would need to just use the smallest value from either end. "Durability", though is all about what the publisher does with new connections. Thoughts?

From a DDS perspective, some readers may be interested in 'historical' data (persisted at the writer for late joining readers via the durability qos), and some readers may not want the historical data, even it is available from the writer.  The ability to specify the durability at the reader is a feature that allows a refinement of the persistence behavior.


pathParse is wrong... in some cases...

Starting from here, with debug mode on:
http://8wayrun.com/articles/soulcalibur-ii.22/category
["heading into ajax", "articles/soulcalibur-ii.22/category?page=2"]
["heading into ajax", "articles/soulcalibur-ii.22/category?page=3"]
["heading into ajax", "articles/soulcalibur-ii.22/category?page=4"]
["heading into ajax", "articles/soulcalibur-ii.22/category?page=5"]
This is all correct.
But if I start from this page:
http://8wayrun.com/articles/soulcalibur-ii.22/category?page=3
["heading into ajax", "articles/soulcalibur-ii.22/category?page=4"]
["heading into ajax", "articles/soulcalibur-ii.32/category?page=4"]
["heading into ajax", "articles/soulcalibur-ii.42/category?page=4"]
["heading into ajax", "articles/soulcalibur-ii.52/category?page=4"]
How do I fix this?

Infinite Scroll v3 is out!. It's an all new re-write, so take a look at how to upgrade from v2.
Infinite Scroll v3 has better support for URLs with parameters, and it has all new support for infinite-scrolling from subsequent pages. I recommend upgrading to v3. Please open a new issue if you run into trouble with Infinite Scroll v3.


feat($parse): Allow user-defined literals

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feature

What is the current behavior? (You can also link to an open issue here)
It is not possible to add user-defined literals.

What is the new behavior (if this is a feature change)?
It is possible to have user-defined literals like Infinity and NaN

Does this PR introduce a breaking change?
No

Please check if the PR fulfills these requirements

[X] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[X] Tests for the changes have been added (for bug fixes / features)
[X] Docs have been added / updated (for bug fixes / features)

Other information:

Allow user-defined literals.
Close: #9504
Close: #9492

Nice one !
LGTM
--
Unrelated to this PR, I noticed we are copy()'ing a lot while parsing. I guess parsing expressions is not our perfrmance bottleneck, but would it make any noticable difference if we used a more efficient special-purpose copy function ?
@lgalfaso, do you have any insight on this ?

You are right. I somehow thought we were copying on every branch of the primary function (which is not the case). Just ignore the noise :grin:


No module named 'KD_Lib.KD'

What could be the cause of the above error after using
from KD_Lib.KD import VanillaKD

I can't see the error message. Can you post the error message again?

No module named 'KD_Lib.KD'
That could be because of the pip install
Now, I am tyrying to install from source to see if it works

Same error

I am unable to reproduce this error. Can you try making a fresh environment and try installing KD_Lib?

kd-lib 0.0.32 requires matplotlib==3.2.1, but you have matplotlib 3.6.1 which is incompatible.
kd-lib 0.0.32 requires pip==21.1, but you have pip 22.2.2 which is incompatible.
kd-lib 0.0.32 requires wheel==0.32.1, but you have wheel 0.37.1 which is incompatible.

Can you install the required versions in your environment? Your environment is interfered with by the package versions in your base environment.
For example to install matplotlib==3.2.1 run pip install matplotlib==3.2.1

Yeah, I am trying that now. Cheers!

Great! I'm closing it now! Merci beaucoup


Tooltip does not work with TooltipTrigger asChild property

Bug report
Tooltip does not work, when in TooltipTrigger with asChild property have children as a component
It seems to work only if asChild removed, and then i have nested button in button (im using next.js, and it warn's me for that)
or i need to put just button tag instead of component that renders it in TooltipTrigger
Current Behavior
https://github.com/radix-ui/primitives/assets/147377970/8ba62460-eb3a-46ca-8bee-8e45b714eb31
Expected behavior
Work with asChild property, where children is component that renders button

Reproducible example
CodeSandbox Template
Your environment

Software
Name(s)
Version

Radix Package(s)
@radix-ui/react-tooltip
^1.0.7

React
n/a
18.3.1

Browser
Firefox Developer edition

Assistive tech

Node
n/a
21.6.1

npm/yarn/pnpm
pnpm
9.3.0

Operating System
Windows  10
22H2

In order for asChild to work, your component needs to forward the ref and the props to an element

I am running into the same issue with React 19. I have ref being passed to the component.
button.tsx
export interface ButtonProps
  extends ButtonHTMLAttributes<HTMLButtonElement>,
    VariantProps<typeof buttonVariants> {
  asChild?: boolean
  loading?: boolean
  ref?: Ref<HTMLButtonElement>
}

export const Button: FC<ButtonProps> = ({
  className,
  variant,
  size,
  asChild = false,
  loading = false,
  disabled = false,
  ref,
  ...props
}) => {
  const Comp = pipe(
    asChild,
    Boolean.match({ onFalse: () => 'button', onTrue: () => Slot }),
  )

  return (
    <Comp
      className={cn(buttonVariants({ variant, size }), className)}
      ref={ref}
      // eslint-disable-next-line @typescript-eslint/ban-ts-comment
      // @ts-ignore
      disabled={disabled || loading}
      {...props}
    />
  )
}

notificationsButton.tsx
    <Tooltip>
      <TooltipTrigger asChild>
        <Button variant={'secondary'} size={'icon'} className={'relative'}>
          <NotificationIcon className={'h-5 w-5'} />
        </Button>
      </TooltipTrigger>
      <TooltipContent>Notifications</TooltipContent>
    </Tooltip>


Snap does not contain object content

Version
1.0.0-beta.22
Reproduction link
https://codesandbox.io/s/xr39rzv50z
Steps to reproduce
Have a child component passing a prop that is an array and generate snapshot
<child-component :myprop="{toto: 'toto', something: true}"/>

What is expected?
<childcomponent-stub
  myprop="{toto='toto', something: true}"
/>

What is actually happening?
<childcomponent-stub
  myprop="[object Object]"
/>

not sure but both tickets (this and linked) are closed, without resolution

@trollepierre  @dcrystalj
There is an experimental feature in jest-serializer-vue-tjw that will allow for this:

https://github.com/tjw-lint/jest-serializer-vue-tjw#usage-and-migrating-from-v2-to-v3

You would need to enable the experimental feature in your vue.config.js.
module.exports = {
  pluginOptions: {
    jestSerializer: {
      stringifyObjects: true
    }
  }
};

With that enabled you can easily opt-in or out of the experimental feature on a per-snapshot basis:
test('Assuming stringifyObjects is enabled', () => {
  const wrapper = shallowMount(YourComponent);

  expect(wrapper)
    .toMatchSnapshot('This will stringify objects');

  expect(wrapper.html())
    .toMatchSnapshot('Use .html() to opt out of stringify objects');
});


Latest shapshot no longer binary compatible with scalaz 7.2.x

Also, there have been no releases compatible with scalaz 7.2.x either.

monocle 1.2.x are released for scalaz 7.2.x:

1.2.1: https://github.com/julien-truffaut/Monocle/blob/v1.2.1/build.sbt#L37
1.2.0: https://github.com/julien-truffaut/Monocle/blob/v1.2.0/build.sbt#L33

I upgraded monocle snapshot to scalaz 7.3.0-M3 in prevision of monocle 1.3.x built against scalaz 7.3.x
Can you tell me more about your issue?

You're correct.
I was using some other library that had the SNAPSHOT as a transitive dependency.  After specifyingexcludeAll in sbt and then explicitly including monocle as a direct dependency, I was able to resolve the issue.
Thanks!


Extract network interfaces

This addresses #186
TODO: Rename SocketEndpoint to ISocketEndpoint (didn't do here because of the massive churn)
TODO: Check if things still work - I only checked it built.
TODO: How to switch between IConnectionManager implementations?

Please provide Breaking Change Details. We need a note on why this change was introduced/what extension surface it impacts. We also need steps for migrating to this new codebase. https://github.com/microsoft/MixedReality-SpectatorView/pull/213 should serve as an example/please include these notes in the pull request description.


add PeaNUT icon

Contribution Guidelines

[X] I have read and agree to the Contribution Guidelines

Icon Name
peanut
Icon(s)

This is for the app called PeaNUT which monitors info on your UPS from NUT server.  I only have the svg from within the app itself


Need deployment guide to host in azure

Hi team,
Can anyone help me out here to deploy the app and host it in Azure?
Do we have any supporting documentation or guide on how can we deploy it to Azure and make it work as a playground version?

Hi @loksayi — there is a guide for this in the getting started docs: Build and run your first Microsoft Teams app with React.

Hi Thure,
Thanks for responding. But I'm unable to deploy the app through visual studio code. I'm getting the attached error when I'm following the steps as per Microsoft docs.
FYI : This app is having Story book as well in the project.

Hi Thure,
Thanks for responding. But I'm still unable to provison/deploy the app through visual studio code. I'm getting the attached error when I'm following the steps as per Microsoft docs.
FYI : This app is having Story book as well in the project.
Question : Do we need to use pipelines for deploying these kind of apps ? or any other way to host/deploy it ? Kindly suggest

@thure

Hello @loksayi have you tried our Visual Studio Code extension... it will guide you through deploying to Azure and can get more support there if you have issues.
Go to VS Code and install the extension by searching for "Teams toolkit"

Hi @asnow003,
First of all thanks for responding. The errors that I have mentioned above are from the VS code Teams Toolkit extension only. It was not supporting this project type to deploy it to azure. Do we have any other options to do it?

Thanks for the replies guys.
I got the solution by building the storybook using yarn run build-storybook which gives a static website in output folder name storybook-static. Then I have referred to the following link for deploying a static website to azure blob storage which got worked.
https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website-how-to?tabs=azure-portal


[BEAM-10124] Change from RecordWithMetadata To Row

[BEAM-10124] As ResourceID is not currently usable as a field with AutoValueSchema , looking to replace with Row.

@abhiy13 FYI, this PR switch from RecordWithMetadata to Row.

@abhiy13 Do you think you will have time to merge this with your PR? If not no worries, I can raise a commit against the PR directly.

Let's continue the discussion on https://github.com/apache/beam/pull/12924, which includes commits from https://github.com/apache/beam/pull/12645 and this PR.

Should we close this?


Add storage size check to construct_runtime!

More of an idea:
Since we have https://github.com/paritytech/substrate/pull/11699, we could add it to construct_runtime! with some sensible (and configurable) default.
This would help us and para-chain teams (eg. https://github.com/NodleCode/chain/pull/655) to spot large storage structs, which bloat the PoV.
What do you think?

Does it need to be in construct_runtime!? We can first start with just a normal test, no?
Also, we can have something like a runtime level set of IntegrityCheck implementations, and just pass them to construct_runtime.

Another idea would be to add this to the integrity_check of the system pallet, as the system pallet knows the MaxBlockWeight and can actually tell you how much it should be.

I think the right way to go about this is to first solve https://github.com/paritytech/substrate/issues/13321, then, if the runtime is being built in parachain mode, we automatically check this in construct_runtime!.
@ggwpez why was the linked PR never merged?

No particular reason. It went stale, but we should revive it.

If you want less magic, you can just provide this method for checking the storage size as method in frame-support or similar. Then everyone can write a test in their own runtime to call this function with the maximum size they want to support before it should fail.

There are already tests to check call encode size. We should be able to do something similar for storage.
One way is to generate a union enum of all the storage items and assert the encoded length


docs: fix spelling issues

Hello
I fixed several spelling issues.
Br, Elias.

This change is

Summary by CodeRabbit

Documentation Updates

Improved clarity and readability of the README.md by correcting grammatical structure.
Corrected typographical error in the documentation for transfer_ownership function to enhance professionalism.
Rectified spelling mistake from "respository" to "repository" in the NEAR DA Server setup documentation.
Enhanced grammatical accuracy in the DA RPC client documentation for clarity.

Thanks for the PR! We're not accepting PRs for grammar at this stage in the project


vsd_health fails on check vsd license

We encountered an error during vsd_health check after a fresh install with license added on the vsd cluster in Nuage release 6.0.3 using MetroAE 4.0.0.
original failure

(metroae-base_minigvp-2_605U0_health) bash-4.2$ ./metroae vsd_health minigvp-2-605
TASK [Verify VSD licenses valid] ****************************************************************************************************
TASK [common : Check VSD License] ***************************************************************************************************
fatal: [nl-gv-pbl-mgvp02-sdn-nvd3-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: vspk is required for this module, or API version specified does not exist.
fatal: [nl-gv-pbl-mgvp02-sdn-nvd1-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: vspk is required for this module, or API version specified does not exist.
fatal: [nl-gv-pbl-mgvp02-sdn-nvd2-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: vspk is required for this module, or API version specified does not exist.
After some troubleshooting it looks like libimport fails to get the vspk ansible module version.
tshoot failure

TASK [common : Check VSD License] ***************************************************************************************************
fatal: [nl-gv-pbl-mgvp02-sdn-nvd1-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: Could not establish connection to VSD No module named vspk.v5_0
fatal: [nl-gv-pbl-mgvp02-sdn-nvd2-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: Could not establish connection to VSD No module named vspk.v5_0
fatal: [nl-gv-pbl-mgvp02-sdn-nvd3-mgmt.sdn-test.kpn.com -> localhost]: FAILED! =>
msg: Could not establish connection to VSD No module named vspk.v5_0
Above output has been created by modifying src/library/check_vsd_license_validity.py lines 95-98 to not be used.
Additional setup info:
(metroae-base_minigvp-2_605U0_health) bash-4.2$ pip freeze
DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 is no longer maintained. pip 21.0 will drop support for Python 2.7 in January 2021. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
ansible==2.9.0
bambou==3.1.1
bcrypt==3.1.7
certifi==2<IP_ADDRESS>
cffi==1.14.0
chardet==3.0.4
colorama==0.4.3
cryptography==2.9.2
enum34==1.1.10
functools32==3.2.3.post2
future==0.18.2
idna==2.9
ipaddr==2.2.0
ipaddress==1.0.23
Jinja2==2.10.1
jmespath==0.9.5
jsonschema==2.6.0
MarkupSafe==1.1.1
netaddr==0.7.19
netmiko==2.3.0
paramiko==2.6.0
pexpect==4.8.0
ptyprocess==0.6.0
pycparser==2.20
PyNaCl==1.3.0
pyserial==3.4
pyvmomi==7.0
PyYAML==3.13
requests==2.23.0
scp==0.13.2
six==1.14.0
tabulate==0.8.7
textfsm==1.1.0
urllib3==1.25.9
vspk==6.0.3

Are you using a python virtual environment?  Ansible is pretty finicky about virtual environments.  It doesn't use them on its own.  You have to add "-e ansible_python_interpreter=python" for it to pick up the version of Python in your virtual-env.
Please let us know if you are using virtual-env and if the above work-around works for you.

Yes, I’m using python virtual environment and that is the problem. Thanks for pointing that out this allowed me to easily fix the situation.
No how to figure out how to close this “case”.
Greetings,
Hans
From: Mike Piecuch<EMAIL_ADDRESS>Sent: Thursday, 30 April 2020 15:46
To: nuagenetworks/nuage-metroae<EMAIL_ADDRESS>Cc: Oudheusden, Hans van<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [nuagenetworks/nuage-metroae] vsd_health fails on check vsd license (#1481)
Are you using a python virtual environment? Ansible is pretty finicky about virtual environments. It doesn't use them on its own. You have to add "-e ansible_python_interpreter=python" for it to pick up the version of Python in your virtual-env.
Please let us know if you are using virtual-env and if the above work-around works for you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/nuagenetworks/nuage-metroae/issues/1481#issuecomment-621862699, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AKSQFJNZVZHB46JYXXJHH7LRPF6KHANCNFSM4MVK5HTA.

Thank you Hans!  Glad it worked for you.  Let us know if there are any other issues!


Integrated Terminal hangs on VS Code launch if previously open

If the VS Code terminal is left open when VS Code is closed, the next time VS Code is opened the terminal will fail to reach an interactive state, and must be restarted to proceed.

VSCode Version: 1.28.2 (system setup)
OS Version: Windows 10 Enterprise 1809 17763.55

Steps to Reproduce:

With CS Code open, launch the integrated Powershell terminal. Once it loads, make sure it remains open and docked.
Close VS Code
Launch VS Code again.
The terminal should still be open, but it will fail to load fully and will not reach an interactive state.

Re-open the terminal pane.
A new terminal will launch, and this time will reach an interactive state.

This appears to be a recent regression. The build from about two weeks ago (public release track) did not have this issue.

Does this issue occur when all extensions are disabled?: Yes

I reproduced the steps just as said but everything is working fine on my machine. Try on another machine.

@VaibhavAcharya I was able to make it work on another machine. However, removing all PowerShell extensions from my profile and loading without VS Code extensions still does not make it work on my impacted machine. Any ideas why it would reliably fail-and-then-work on each fresh VS Code window load?

@ThomasMichon Can you give list of extensions you are using and more detail about your workspace?

https://github.com/Microsoft/vscode/issues/57803


Enable android 21 compatibility

This PR gets rid of the AtomicReference#getAndUpdate call which was added in sdk version 24.

I already fixed this. If you can improve on the current solution I'll happily consider it :)

yeah.. that looks simpler actually!


User Dashboard theme change

The Workspace is using a newer frontend theme that is different from the one used in the User Dashboard. Ideally User Dashboard's theme should be matched up with the entire system.

@MysteriousChallenger Can you please help in updating the frontend theme of the User Dashboard?

Discussion 2022.05.12: @zuozhiw will work on this.

this issue is mostly finished.


Add note about xvfb-run, perhaps just set this to include and use it by default.

#28 addresses this issue.


Provide example automation for startup of Ankaios executables

Description
Although targeted at automotive HPCs, Ankaios can actually be used in arbitrary systems. Especially small clusters with low resources would be a good target.
To enable the usage of Ankaios in such environments, some automation for the startup of the executables would be helpful. As a start, systemd support can be added (because of the wide spread). Later other init systems could follow, e.g., crinit.
Goals
Make Ankaios easy to use in a wider range of use cases.
Tasks
TBD

In order for Ankaios server and and agent to start on system startup we should probably start them as root using systemd unit files for server and agent and maybe also one for podman (podman.socket only seems to be available in user scope). When podman service has been replaced by podman cli we do not need a unit file for podman anymore.
Then the install script needs to be extended to also install the systemd unit files and also enable and start the systemd services.
Ankaios server needs a startup state which we can place in /etc/ank/state.yaml or similar. The default startup state should be empty from my point of view.
Maybe we should also provide an uninstall script then.

As a first start I have created some systemd unit files that could do the job when stored in /etc/systemd/system.
ank-server.service:
[Unit]
Description=Ankaios server

[Service]
ExecStart=/usr/local/bin/ank-server --startup-config /etc/ank/state.yaml

[Install]
WantedBy=default.target

podman.service:
[Unit]
Description=Podman service

[Service]
ExecStart=/usr/bin/podman system service -t 0 unix:///tmp/podman.sock

[Install]
WantedBy=default.target

ank-agent.service:
[Unit]
Description=Ankaios agent
Requires=podman.service

[Service]
ExecStart=/usr/local/bin/ank-agent --name agent_A --podman-socket-path /tmp/podman.sock

[Install]
WantedBy=default.target

Then server and agent can easily be started as:
sudo systemctl start ank-server
sudo systemctl start ank-agent

Which name shall we use for the agent when installing systemd unit files? Should it be agent_A or maybe the hostname?

We need options for the install script:

install server and/or agent with default agent name( "") or specified agent name
install only agent with specified name and url (default localhost:) of the server

Maybe the state.yaml file can be prefilled with the structure and a commented out workload.


Use master branch of openshift-ansible

Oh, I accidentally made same change as part of HA patch (accidentally because it should have been a separate patch as you did). To minimize the risk of being broken by changes in openshift-ansible, I wonder if we shouldn't in future:
a) stick with git tags
b) use openshift-ansible rpm (+1 for this one)

+1 for the openshift-ansible RPM too


Apply changes suggested in #502

Needs to be discussed.

this is crucial for my software, I would appreciate if we discuss this within the next days.

I've talked with @tritao about my issue and we found the last necessary bit to keep compatibility. The last commit should provide the necessary compatibility functions for Java Projects.
cc @jonathanpeppers here because if it's going to be merged you must set the runtime assembly paths with the new function.

@tritao can you restart the CI? I would like to see this merged soon :smiley:


Gulp/Ruby Error! Gem cmd is not installed

I have poured at least 8 hours into troubleshooting with no avail to get Gulp/Ruby to work properly. I am taking a course on sass fundamentals and have downloaded its repository from github. I am running Windows 7 64-bit.
I also installed git bash, as well as, ruby, sass, and gulp from the git bash cmd line. I am able to run everything properly until running the 'gulp' command.
All the research I have seen on stackoverflow has not produced any answers unfortunately. I have attached images that show my errors, versions of all in git, and my environmental variables paths in Windows 7.
When running gulp, I get error:
" [22:32:30] Finished 'webserver' after 15 ms
Error! Gem cmd is not installed."
errorInBashGulp
When doing a search it stated that my path in environmental variables needs to be directed to the ruby folder, which it is.
**Also, when I save the .scss file in Atom, I get the other error:
" 'node-sass' is not recognized as an internal or external command,
operable program or batch file."
errorInAtomOnSave

**
I have uninstalled/reinstalled ruby 3 times and get the same error. Not sure what to do or what the problem actually is... Any help would be great. Thanks so much!
Chris Davis

i don't think this has something to do with gulp but more with sass, node-sass or gulp-sass 😄

Sorry but this is not a support forum. Please direct your support questions to StackOverflow.


cargo doc --open doesn't work on Windows

Unfortunately I can't compile Cargo on Windows, so I don't understand why.
Running start path/to/docs manually (what Cargo is supposed to do) works.

Just confirming that it doesn't work on a fresh installation of Windows 7, so the problem didn't come from my system.

Have you tested on other operating systems? Seems like you're implying that this problem only happens on Windows only and not other operating systems, or am I reading this wrong?

Yes, it works on Ubuntu.

Launching start programmatically won't work. See my solution: #1535


Extend compatibility with systemd-boot and other kernels

Hi,
I use btrfs as my main filesystem (single-disk with subvolumes), snapper for timeline snapshots and snap-pac for pacman transactional snapshots. I also use systemd-boot as a bootloader.
With this configuration, I was unable to enable secure-boot using you script.
First, I had to remove --no-dbus option from snapper comand-line because with it, it was unable to find my snapshots.
Then  had to adapt the script a bit because I use linux-hardened as my main kernel and this use case wasn't implemented.
I also had a problem due to the fact I mount efivarfs read-only for security reasons. So, to be able to add efi entries, I had to remount this vfs in rw mode.
Finally, for some reasons I still don't understand, even after fixing all these issues, adding a new efi entry using efibootmgr and setting it as the first element had no effect, and was not able to boot with secure-boot activated.
After many tries, my opinion was that systemd-boot probably interfere with vanilla EFI boot process in a way I don't understand.
Anyway, I discovered some interesting bit of information.
1st : When I copy *.efi file to $ESP/EFI/Linux, they appear in systemd-boot menu.
2nd: systemd-boot efi loader is located at $ESP/EFI/systemd/systemd-bootx64.efi
3rd: If I sign systemd-boot efi loader using sbsign, and copy it to $ESP/EFI/BOOT/BOOTX64.EFI, I'm able to securely boot on it.
So I decided to also include this use-case in arch-secure-boot script.
One more thing, after all that journey, I wanted to be able to only include Intel ucode because I don't have any AMD CPU here. So I also implemented this possibility in the script.
To resume, in this pull request, I introduce five different improvements:

Allow user to choose a main kernel other than linux (for example, linux-hardened or linux-zen)
Allow user to customize snapper options used to retrieve snapshots (eg. remove --no-dbus)
Automatically mount efivarfs if it's not mounted and remount it with write enabled if it's mounted with read-only option.
Automatically detect systemd-boot ans use it's own efi loader (and also ensure efi files will be copied to $ESP/EFI/Linux)
Allow user to restrict which cpu microcode to integrate in unified efi kernel images (keep all by default)
(maybe also a bit of refactoring)

This is not the cleanest implementation but I tried to ensure retro-compatibility.
Here is the working config I use:
ESP="/esp"
EFI="/EFI/Linux"
KERNEL="linux-hardened"
SNAPPER_OPTIONS=""
SUBVOLUME_ROOT="@"
SUBVOLUME_SNAPSHOT="@snapshots/%1/snapshot" # %1 is replaced with snapshot ID
UCODE="intel"

I hope you'll like these additions.
Regards

Closing for now due to inactivity. I have documented in README that boot managers are intentionally not supported, and specifically mentioned KERNEL=linux-hardened option for visibility. Once again, thank you for your time to open the PR, even though in this particular case it is not something that was merged, your collaboration is very much appreciated!


Page outline not responsive

Description
Navigate to the UDS CLI Guide page on the docs site. I'm on a 27 inch monitor and the horizontal scroll is introduced to see the page nav on the right. See screenshot below for comparison with the Gitlab docs for how this should look on my screen (notice the horizontal scroll on the uds docs image on the right compared to no horizontal scroll in the Gitlab docs on the left)

Strange. I've not seen this behavior.


GoPlus - TokensList.org-Style Attestation List

Hi from Goplus team,
As GoPlus, we offer security solutions for users in the crypto market. Therefore, since we work on the security of tokens, we are very experienced in the field of token classification.
We are ready to use our experience for TokensList.org-Style Attestation List.
The TokensList allows users to publish and discover lists of tokens maintained by teams and projects. These lists of tokens make it possible for teams to signal the legitimacy of certain tokens and help users filter out spam. We need this same kind of infra for the Attestation Station.
Possible Features
-An instance of an attestation list following a standard JSON schema and can -be hosted publicly on ENS, IPFS, or HTTPS.
-Context on what attestation lists are
-Directions on how to validate that a schemas follow the proposed standard
-Directions on how to author a attestation list
List data
List URL
List Name
List version
Link to the official homepage of the list manager
Attestation data
Attestation name
Attestation author
Attestation key
Attestation value
Attestation image
Attestation description
-Directions on how to deploy an attestation list
-Examples of what a attestation list looks like

Hi,
Branch has conflicts that must be resolved -- please resolve in order to be merged!
Thanks!

I will fix it as soon as possible. Thanks for letting me know
On Wed, Aug 7, 2024 at 19:45 opjulian @.***> wrote:

Hi,
Branch has conflicts that must be resolved -- please resolve in order to
be merged!
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/ethereum-optimism/ecosystem-contributions/pull/187#issuecomment-2273891810,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR255WKEBFEWU6LUPBXYBN3ZQJFMDAVCNFSM6AAAAABHTKAGCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTHA4TCOBRGA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


Documentation mirroring

The documentation contains a few duplicates at the moment, mainly https://www.apollographql.com/docs/android/essentials/get-started/ that duplicates a lot of the content from https://github.com/apollographql/apollo-android/blob/master/README.md.
We could make apollographql.com mirror github.com. The idea would be to add a script that preprocesses the markdown files before building the gatsby site:

Copy README.md to ~index.mdx~ gettting-started.md.
Add the title headers needed by gatsby.
Strip the link to apollographql.com from README.md like okhttp does: https://github.com/square/okhttp/blob/master/deploy_website.sh#L55
Fix relative links.

This way we'll have the same documentation on both sites.

@martinbonnin are you working on this or can I give it a go?

@ralphie9224 go for it !

@martinbonnin what's the best way to test this?

@ralphie9224 The changes on master get deployed automatically. If you want to test on your fork, you'll need to setup a netlify account. The configuration is in this file: https://github.com/apollographql/apollo-android/blob/master/netlify.toml

Sorry, I accidentally closed. Should this be close, tho?

Yep, it's good to close now 👍


RFE: Incorporate opencoarrays3.0 power subdirectory into CMake build system

The src/power subdirectory on the opencoarrays3.0 branch contains a handful of stubs of the new interface and one test, all in one directory.  Let's replace the Makfile with CMake scripts and either mirror the current src directory structure under the new src/power subdirectory or move the stubs and tests into their counterpart locations in the current OpenCoarrays release, e.g., src/mpi and src/tests/unit/.

@rouson: I understand the part about using CMake, but I don't quite follow how you want to re-structure the directories.

be gone stale bot

It's not clear that this work will move forward anytime soon so I'm marking this as wont-fix and closing.


FINERACT-2070: E2E testcase migration

Description
FINERACT-2070 e2e testcase migration
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ ] Write the commit message as per https://github.com/apache/fineract/#pull-requests

[ ] Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.

[ ] Create/update unit or integration tests for verifying the changes made.

[ ] Follow coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions.

[ ] Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes

[ ] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the developer mailing list for guidance, if required.)

FYI our guidelines for code reviews are at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide.

@peter-kovacs-dpc I'm sorry but this is way too big of a PR. Can you pls chunk it to max 2k line changes/PR? Thanks.


[6.0🍒] NCGenerics: enforce same-source conformance rule

Explanation: Retroactive conformances to Copyable were being permitted and that's nonsense. SE-427 actually says it has to be defined in the same source file, like Sendable.
Scope: Source breaking, but easy to remedy in the legal cases.
Issue: rdar://131486561
Original PR: https://github.com/swiftlang/swift/pull/75141
Risk: Low
Testing: Swift CI.
Reviewer: TBD

@swift-ci test


Error response from daemon: Cannot start container

docker run -i -t centos /bin/bash
Error response from daemon: Cannot start container f4426a648e255a877439a0e8545cc0fd2cf7ce6658c379a124db4a6f2181bb7d: no such file or directory
how can i do?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

centos 6.5    kernal 2.6.32-358.6.1.el6.x86_64

@naffan2014 hm, CentOS 6/RHEL 6 is no longer supported, the last version for those systems is 1.7.1, and that will no longer get patch updates. This could well be a kernel issue.
You could run this script: https://github.com/docker/docker/blob/master/contrib/check-config.sh to check if all requirements for running docker are in place, but other than that, I don't think we'll be able to help you.
I'll close this issue, because CentOS 6 / RHEL 6 is no longer supported, but feel free to comment here after I've closed

no matter  i sovled it . thank you all the same


🐛 [BUG] 'RunningStats' has no attribute 'get_state'. Did you mean: '_state' ? in both Metrics.gather() and LossStats.gather()

Describe the bug
Hi there. It seems like both Metrics and LossStats are using a .get_state method that does not exist in RunningStats. My interpretation of this issue was that the gather method was trying to accumulate the metrics and losses after the optimizer step to rank0 for output/results.
In nequip/train/metrics.py:
https://github.com/mir-group/nequip/blob/61b525f855a75883ba4631537e644c247e80d1f4/nequip/train/metrics.py#L266-L285
In nequip/train/loss.py :
https://github.com/mir-group/nequip/blob/61b525f855a75883ba4631537e644c247e80d1f4/nequip/train/loss.py#L190-L205
To Reproduce
When using the ddp branch of nequip:
torchrun --nnodes 1 --nproc_per_node 2 `which nequip-train` configs/minimal_distributed.yaml --distributed

Expected behavior
I would expect these methods to properly copy the loss stats and metrics after the optimizer is run. This is definitely easier said than done! I'm not too sure how to validate that the approach is working besides comparing it to the single gpu results for aspirin.
Environment (please complete the following information):

OS: Ubuntu
python version (python --version) : 3.10.4
python environment (commands are given for python interpreter):

nequip version (import nequip; nequip.__version__) : 0.61 - ddp branch
e3nn version (import e3nn; e3nn.__version__) : 0.51
pytorch version (import torch; torch.__version__) 1.13cu+117

(if relevant) GPU support with CUDA

cuda Version according to nvcc (nvcc --version) :
Built on Tue_May__3_18:49:52_PDT_2022
Cuda compilation tools, release 11.7, V11.7.64
Build cuda_11.7.r11.7/compiler.31294372_0
cuda version according to PyTorch (import torch; torch.version.cuda) : 11.7

Additional context
Here is the error message when I first ran the torchrun:
torchrun --nnodes 1 --nproc_per_node 2 `which nequip-train` configs/minimal_distributed.yaml -
-distributed
WARNING:torch.distributed.run:
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/__init__.py:20: UserWarning: !! PyTorch version 1.13.0+cu117 found. Upstream issues in PyTorch versions 1.13.* and 2.* have been seen to cause unusual performance degredations on some CUDA systems that become worse over time; see https://github.com/mir-group/nequip/discussions/311. The best tested PyTorch version to use with CUDA devices is 1.11; while using other versions if you observe this problem, an unexpected lack of this problem, or other strange behavior, please post in the linked GitHub issue.
  warnings.warn(
/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/__init__.py:20: UserWarning: !! PyTorch version 1.13.0+cu117 found. Upstream issues in PyTorch versions 1.13.* and 2.* have been seen to cause unusual performance degredations on some CUDA systems that become worse over time; see https://github.com/mir-group/nequip/discussions/311. The best tested PyTorch version to use with CUDA devices is 1.11; while using other versions if you observe this problem, an unexpected lack of this problem, or other strange behavior, please post in the linked GitHub issue.
  warnings.warn(
Using `torch.distributed`; this is rank 0/2 (local rank: 0)
Using `torch.distributed`; this is rank 1/2 (local rank: 1)
Torch device: cuda
Processing dataset...
Loaded data: Batch(atomic_numbers=[21000, 1], batch=[21000], cell=[1000, 3, 3], edge_cell_shift=[220186, 3], edge_index=[2, 220186], forces=[21000, 3], pbc=[1000, 3], pos=[21000, 3], ptr=[1001], total_energy=[1000, 1])
    processed data size: ~9.77 MB
Cached processed data to disk
Done!
Successfully loaded dataset `dataset` of type NpzDataset(1000)...
/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/jit/_check.py:181: UserWarning: The TorchScript type system doesn't support instance-level annotations on empty non-base types in `__init__`. Instead, either 1) use a type annotation in the class body, or 2) wrap the type in `torch.jit.Attribute`.
  warnings.warn("The TorchScript type system doesn't support "
/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/jit/_check.py:181: UserWarning: The TorchScript type system doesn't support instance-level annotations on empty non-base types in `__init__`. Instead, either 1) use a type annotation in the class body, or 2) wrap the type in `torch.jit.Attribute`.
  warnings.warn("The TorchScript type system doesn't support "
Replace string dataset_per_atom_total_energy_mean to -19318.260077821487
Atomic outputs are scaled by: [H, C, O: None], shifted by [H, C, O: -19318.260078].
Replace string dataset_forces_rms to 31.499698153708387
Initially outputs are globally scaled by: 31.499698153708387, total_energy are globally shifted by None.
Successfully built the network...
Number of weights: 41216
Number of trainable weights: 41216
! Starting training ...

validation
# Epoch batch         loss       loss_f        f_mae       f_rmse
Traceback (most recent call last):
  File "/home/myless/.mambaforge/envs/allegro-ddp/bin/nequip-train", line 8, in <module>
    sys.exit(main())
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/scripts/train.py", line 119, in main
    trainer.train()
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/train/trainer.py", line 841, in train
    self.epoch_step()
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/train/trainer.py", line 1006, in epoch_step
    self.metrics.gather()
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/train/metrics.py", line 270, in gather
    {
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/train/metrics.py", line 271, in <dictcomp>
    k1: {k2: rs.get_state() for k2, rs in v1.items()}
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/nequip/train/metrics.py", line 271, in <dictcomp>
    k1: {k2: rs.get_state() for k2, rs in v1.items()}
AttributeError: 'RunningStats' object has no attribute 'get_state'. Did you mean: '_state'?
WARNING:torch.distributed.elastic.multiprocessing.api:Sending process 706198 closing signal SIGTERM
ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 1 (pid: 706199) of binary: /home/myless/.mambaforge/envs/allegro-ddp/bin/python3.10
Traceback (most recent call last):
  File "/home/myless/.mambaforge/envs/allegro-ddp/bin/torchrun", line 8, in <module>
    sys.exit(main())
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 346, in wrapper
    return f(*args, **kwargs)
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/distributed/run.py", line 762, in main
    run(args)
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/distributed/run.py", line 753, in run
    elastic_launch(
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 132, in __call__
    return launch_agent(self._config, self._entrypoint, list(args))
  File "/home/myless/.mambaforge/envs/allegro-ddp/lib/python3.10/site-packages/torch/distributed/launcher/api.py", line 246, in launch_agent
    raise ChildFailedError(
torch.distributed.elastic.multiprocessing.errors.ChildFailedError:
============================================================
/home/myless/.mambaforge/envs/allegro-ddp/bin/nequip-train FAILED
------------------------------------------------------------
Failures:
  <NO_OTHER_FAILURES>
------------------------------------------------------------
Root Cause (first observed failure):
[0]:
  time      : 2024-07-15_20:16:16
  host      : gpu-rtx6000-04.psfc.mit.edu
  rank      : 1 (local_rank: 1)
  exitcode  : 1 (pid: 706199)
  error_file: <N/A>
  traceback : To enable traceback see: https://pytorch.org/docs/stable/elastic/errors.html
============================================================

Closed as per https://github.com/mir-group/nequip/pull/450#issuecomment-2231363709


How ti make dataset?

I have found to make my own dataset.
The example dataset is already bytestream.
Can you explain how can I add my image set?

Title is wrong spell.
How can I make dataset as bytestream?

This should be a stackoverflow question rather than a github issue.  Github issues are for bugs or feature requests that should be fixed on the tensorflow side.


Compiling for X11 aarch64 fails (undefined reference linking)

Godot version:
master
OS/device including version
Termux Arch on Android phone
Issue description:
Compiling for the aarch64 doesn't work natively in a termux Emulator with arch repo.
I've previously disabled yasm (with yasm there are other issues).
Command:
scons p=x11 target=release_debug tools=yes arch=aarch64 -j 1
Error Output:
/Recast/Source/RecastRegion.cpp              [Initial build] Linking Static Library ==> modules/recast/librecast_builtin.x11.opt.tools.aarch64.a   Ranlib Library         ==> modules/recast/librecast_builtin.x11.opt.tools.aarch64.a                   [Initial build] Linking Program        ==> bin/godot.x11.opt.tools.aarch64                            modules/libmodules.x11.opt.tools.aarch64.a(systemdependent.x11.opt.tools.aarch64.o): In function `vp8_machine_specific_config':
/godot/thirdparty/libvpx/vp8/common/generic/systemdependent.c:102: undefined reference to `arm_cpu_caps'                                                 collect2: error: ld returned 1 exit status
scons: *** [bin/godot.x11.opt.tools.aarch64] Error 1
scons: building terminated because of errors.      [19:06 godot ]$

Minimal reproduction project:

Related #7252 (same error for armv7, fixed in #7267)
modules/webm/libvpx/SCsub#L266 probably should have additional check for aarch64.


Bower support not working?

I'm trying to use Brunch for a project but run into several issues using it. One them is the following:
I want the javascript files in the bower_components (wwwroot/lib) folder to be concatenated into a libs.js file. But what I end up with is a giant libs.js file including every js file in bower_components directory and not just the main files.
Not sure if I'm using this tool wrong or if it is a bug.
 module.exports = {
    files: {
        javascripts: {
            joinTo: {
                'app.js': 'wwwroot/app/**',
                'libs.js': 'wwwroot/lib/**'
            },
            order: {
                before: ['**/*.module.js']
            }
        },
        stylesheets: {
            joinTo: {
                'app.css': 'wwwroot/**'
            }
        }
    },
    paths: {
        watched: ['wwwroot/app', 'wwwroot/content', 'wwwroot/lib'],
        public: 'wwwroot/dist'
    },
    modules: {
        definition: false,
        wrapper: false
    },
    npm: {
        enabled: false
    },
    conventions: {
        vendor: /wwwroot\/lib\//
    }
}

Hi @sjaase! Thanks for noticing!
I will be glad to help you, but can you, please, make a GitHub repo that reproduce this bug? That would be much more easier for me to fix that problem.

Also, keep in mind that Brunch uses read-components module internally. Take a look at “Component JSON file must have main property.” section and make sure all your packages are work properly.


My imagination draw me following step layout
steps:
  - name: my.package.another.module
    async: 5 # (default: 0 - sync/blocking run, 1 async run, greater than 1 make sense only when used foreach or while loop)
    register: context_key_name # (Required if async > 0, set step instance to context, step have list of running coroutines)
    timeout: 5 # (default 0, max timeout for running all coroutines, will cancel coroutines silently, but wait_for should raise exception if shallow is false)

    while:
      stop: '{keyhere}'
      blocking: True # default True, wait_for after each step, but conflicts with async property (async > 1 does not make sense if blocking is on), probably should warn about it...

  - name: pypyr.steps.wait_for
    description: special step to wait until previous async step is finished or cancelled.
    in:
        wait_for:
            - step: context_key_name

Does it make sense? May I try to implement this approach and share results?
If wait_for wasn't called directly, should we wait or cancel all pending coroutines at the end of pipeline?

No deadline, no. This is actually one of the trickier ones, and it requires careful thought and consideration given its potential for introducing regression issues, knock-on impact on consumers and downstream plug-ins. I also find myself having to balance what a pipeline is, conceptually - as a sequence of steps.
What you're effectively doing here is allowing a step to run non-blocking, or async, meaning it will move on to the next step immediately, or until you, like you're also wondering about:

If wait_for wasn't called directly, should we wait or cancel all pending coroutines at the end of pipeline?

So there are really two separate things here:

run step non-blocking
run step over multiple co-routines (similar to while, but in parallel)

Conceptually, I've done similar to 1. previously - look at waitfor in pypyraws as an example. This steps waits for an external process to finish that was initiated by any given previous non-blocking "async" step. The difference is that it's not the pypyr core that's async, it's actually up to the step to initiate a non-blocking async process.
So, let's say you're doing an expensive long-running operation. That goes in a step called mypypyrplugin.steps.longrunningoperation. This step contains code that kicks off this long running operation but returns success to the pypyr core run-time immediately, so pypyr moves on to the next pipeline steps.
Then there's another step for `mypypyrplugin.steps.waitforlongrunningoperationtofinish" that will poll whatever status needs to be polled (existence of file, web-service response, whatever it is) and block until it receives the result it's waiting for.
I know I'm not fully answering your question yet, and I'm sorry about that, just letting you know in the meantime where my thoughts are and I'm still thinking about it!

p.s if this is just about invoking the pypyr core from your aiohttp stack, you can still run the pypyr run_pipeline sync methods without blocking using something similar to this https://docs.python.org/3/library/asyncio-eventloop.html#asyncio.loop.run_in_executor

Yeap, run_in_executor probably will do the trick, thanks for the suggestion, but it's a little bit silly to my mind, because I will need to have support for both async/sync libraries, for example I can't use HTTP client from aiohttp at blocking run_step function. And it is a big deal for me, I have many other asynchronous libraries, db, redis, our sdk for internal services. Of course they may be rewritten/replaced to use as synchronous, but it wouldn't be so easy.
For now, I found a tricky workaround https://gitlab.com/pgjones/quart/blob/master/quart/flask_patch/_patch.py#L20 , this code part allow to run async coroutine from sync code, but that is monkey-patch of loop, and as result break support for uvloop. And potentially may be not compatible with even minor python releases.
From the other side I'm started experimenting to support both async def run_step(context) and original def run_step(context) for step modules. And seems it is working fine.
I create a wrapper function, which ensure that coroutine result was awaited
async def ensure_future_result(result):
    if asyncio.iscoroutine(result):
        return await result
    return result

and use it inside Step class
await ensure_future_result(self.module.run_step(context))

You may look inside my fork if you interested, Reskov@06326e912c8f58ebdbbc9e95a259611507319bb3, all unit tests and flake checks are already passed, but as you mention, this does not guarantee that I will not break the back compatibility for plugins, therefore regression of course is needed.
Also I agree with that almost all async stuff may be done running step synchronously, and seems it fairly enough to work with pipeline like script executor.
I probably need to re-think about my expectations, if you will find my experiment reasonable (it may helps with future threads decision) ping me here, I will add some test cases and prepare PR.
p.s. Sorry to bother you with my problems, I'm appreciate your help, and I'm really love your library, it seems at most fits all my needs

Hi Reskov,
I checked out your fork - it's looking good! Sorry I've taken a bit of time to respond, I've been thinking it through carefully.
I get what you're saying for your use-case, and thank you for explaining more, it's very helpful for me to understand better - invoking the pypyr api async to sync it up with the top loop with get_event_loop  or asyncio.run makes everything downstream work async too without a fuss, especially when you're invoking other apis in your steps.
I'm not too cheerful about the async creep all the way up and down through the api, though, where for almost all of there aren't actually any suspend points in the pypyr core meaning the code is going to be running synchronously anyway, until such time as it gets to a step that actually does something async (an aoihttp call, say). . .
And it feels like it's going to lead to trouble when there's fundamentally synchronous/non-async-friendly code sitting in a step's run_step, being invoked from an async core. I get in your particular case your'e going to make sure that this does not happen, but other pypyr consumers are not necessarily going to get the expected results. Especially where sub-processes kick of (e.g the shell/safe-shell steps).
So while your ensure_future_result function is a nifty bit of code, I think it'll end up causing surprises for downstream step authors/consumers.
Assuming the pypyr core is invoked synchronously (i.e no top event loop exists already), individual steps are then free to do an async.run() when and where they see fit - i.e a step can do an async invoke easily enough to call aoihtttp asynchronously, without affecting other steps or the pypyr core.

Also I agree with that almost all async stuff may be done running step synchronously, and seems it fairly enough to work with pipeline like script executor.

Yes, you've hit the nail on the hit! Pretty much all of pypyr is really wedded into the world of scripting - it's memory hungry, it makes no attempt to streamline/optimize code for the purposes of a lean and mean web-server, which is why making it behave async within the context of a web-server process is probably not going to be something the web-server will be too happy about. Off-loading memory/cpu/io hungry code like pypyr onto a queue or outside processor like an aws step function is going to make the web-server a lot happier, and then the core can happily stay doing what it's doing synchronously, while allowing individual step authors to code async functionality as appropriate when doing things like I/O or high latency calls.
So I'm very unlikely to merge this into the core, sorry!
Incidentally, not that this helps you any 😄 , the parallel functionality that I was planning on this load task, is going to be more something like this:
- name: pypyr.steps.echo
    description: loop 5 times
    in:
      echoMe: "this is step {whileCounter} of 5, all running in parallel."
    while:
      parallel: true
      max: 5

Hi @345thomas,

Especially where sub-processes kick of (e.g the shell/safe-shell steps).

I didn't get what troubles  the user will have. The running loop will be blocked until the end of process, that's true, but the same is also be true for just a sync part of code, but we have already discussed the solution for that as you suggest loop.run_in_executor or even better asyncio.create_subprocess_exec

not going to be something the web-server will be too happy about

For now I've created a  small web-service as proof of concept, which stores pypyr configs at consul and calls pypyr pipeline for each request. Inside step definition I call redis and after elasticsearch http service (also do validation and other staff). So I am happy with the results: about 400-500rps from a single core, it is not so much, but it seems to fit my needs completely.

So I'm very unlikely to merge this into the core, sorry!

P.s. Don't worry, I don't try to argue or force you to merge. I already assumed that this would happen :)

name: pypyr.steps.echo
description: loop 5 times
in:
echoMe: "this is step {whileCounter} of 5, all running in parallel."
while:
parallel: true
max: 5

Looks great! But how can be predicted number of threads,  especially in case of stop substitution (without max)?

so I am happy with the results: about 400-500rps from a single core, it is not so much, but it seems to fit my needs completely.

super, I'm very glad it's working for you! very interesting what you're doing w redis and elastic, thank you for sharing!

But how can be predicted number of threads, especially in case of stop substitution (without max)?

That bool I hurriedly typed might need to be an int 😄
The core use cases would be concurrently running long running operations like downloads, package updates, concurrently running cloud/server side provisioning jobs that take a long time.


GetNumPhysicalCPUs() without using libcpuid

I guess we could optimize it with some fixed container from eastl yeah
On Sat, Jun 24, 2023, 18:24 Sandu Liviu Catalin @.***>
wrote:

@.**** commented on this pull request.
In Source/Urho3D/Core/ProcessUtils.cpp
https://github.com/rbfx/rbfx/pull/577#discussion_r1240848632:

GetCPUData(&data);

return data.numPhysicalCores_;
+#elif defined(EMSCRIPTEN)
+#ifdef EMSCRIPTEN_PTHREADS
return emscripten_num_logical_cores();
+#else
return 1; // Targeting a single-threaded Emscripten build.
+#endif
+#elif defined(_WIN32)
unsigned cpuCount = 0;
DWORD bufferSize = 0;
GetLogicalProcessorInformation(NULL, &bufferSize);
if (ERROR_INSUFFICIENT_BUFFER == GetLastError())
{

   const size_t entryCount = bufferSize / sizeof(SYSTEM_LOGICAL_PROCESSOR_INFORMATION);

   std::vector<SYSTEM_LOGICAL_PROCESSOR_INFORMATION> entries(entryCount);

std::vector?
—
Reply to this email directly, view it on GitHub
https://github.com/rbfx/rbfx/pull/577#pullrequestreview-1496698970, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AESDTGXLTSALCWWRTCJO5O3XM4BEHANCNFSM6AAAAAAZSQ3I54
.
You are receiving this because you authored the thread.Message ID:
@.***>

@eugeneko, approval? 😁


server: use actual TenantID for multi-tenant KV admission control

PR: https://github.com/cockroachdb/cockroach/pull/67533
From release notes:

Enabling admission.kv.enabled may provide better inter-tenant isolation for multi-tenant KV nodes. [#67533][#67533]

Assuming this is not user-facing.


Use namespace mixin. Closes#1175

Closes #1175

Shouldn't something in this PR have been changed to call this.namespaceEvent()?

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks failed.

Comments from the review on Reviewable.io

Previous references already used this.namespaceEvent(). Nothing to change as before namespaceEvent was on the class, not it's being mixed in, so it is invoked the same way.

Comments from the review on Reviewable.io

should have read

now, it's being mixed in

Comments from the review on Reviewable.io


Added dependencies to the nuget file

The Newtonsoft dependency wasn't added during the build process.
I also removed the project argument from getAkkaDependency because it is not used...
Regards
Marc

Thanks!


Changed readme to reflect new image-asset tag helper

README was referencing the usage of an HtmlHelper extension for responsive image generation which has been removed and replaced by a tag helper. I have updated the content accordingly.

you were faster than me :) thanks @robertgregorywest


Make "v" in "v1.2.3" optional

Hi,
Would it be possible to make the "v" in "v1.2.3" optional? It's not strict semver. https://semver.org/#is-v123-a-semantic-version
Thanks! :)

Hi @d-miketa! We discussed this a while ago, and decided to keep v https://github.com/iterative/gto/issues/127#issuecomment-1103815257
It makes sense to keep GTO tags in a single format (not supporting it with v and without) both for simplicity of what you can expect to see and different corner cases that may arise, so I wonder, is it just something that doesn't look right (since it's not vanilla semver) or it block some scenarios for you?

Hi @aguschin :)
Thanks for that link, I'll give it a careful read. In the meantime, I can explain where I'm coming from.
I'm not aware of any strict incompatibility with another tool. My request is motivated purely by trying to put together a nice UX that's as consistent as possible - and our Python packages are indexed with regular semver. So it's less that it doesn't look right (an aesthetic concern) and more that I'll have to explain to other users, who don't know gto, that there is a special convention they have to follow for exactly one step in a multi-step process. This creates friction and opportunities for user errors. I'd rather get ahead of the support tickets and use consistent versioning across all steps.


writeWithoutResponse: true error

CharacteristicProperties{broadcast: false, read: false, writeWithoutResponse: true, write: true, notify: false, indicate: false, authenticatedSignedWrites: false, extendedProperties: false, notifyEncryptionRequired: false, indicateEncryptionRequired: false}
this is print log of characteristic, but when set writeWithoutResponse: true got this log PlatformException(write_characteristic_error, writeCharacteristic failed, null, null) and then device is disconnected; how can I write data withoutresponse?

Check your device with another bluetooth app if the behaviour is the same.

I have tested more than one device, they all works fine with WriteWithOutResponse on native iOS and Android bluetooth app, but not work on flutter app and get the same error like I said before.     Also, the version of  flutter_blue I use is 0.8.0

Check your device with another bluetooth app if the behaviour is the same.

I have tested more than one device, they all works fine with WriteWithOutResponse on native iOS and Android bluetooth app, but not work on flutter app and get the same error like I said before. Also, the version of flutter_blue I use is 0.8.0

Check your device with another bluetooth app if the behaviour is the same.

I have tested more than one device, they all works fine with WriteWithOutResponse on native iOS and Android bluetooth app, flutter app on iOS works, but not work on Android and get the same error like I said before. Also, the version of flutter_blue I use is 0.8.0

I have solved this problem, I have add a condition in BluetoothCharacteristic Class at line 123, only return result on iOS,  and the code like this
if (Platform.isIOS && type == CharacteristicWriteType.withoutResponse) {
return result;
}
when return result on android may cause the package lose, and that makes the problem.
so on android I get WriteCharacteristicResponse and send next package.
@peekpt


configure codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@361cb86). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             main        #2   +/-   ##
========================================
  Coverage        ?   100.00%
========================================
  Files           ?         3
  Lines           ?        47
  Branches        ?         3
========================================
  Hits            ?        47
  Misses          ?         0
  Partials        ?         0

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 361cb86...2f9d339. Read the comment docs.


vaultwarden: Add update script to keep web vault in sync

Adds an update script to fetch the compatible web vault version
Removes vaultwarden-vault from top-level to prevent independent
updates through e.g. r-ryantm. Istead the vault is now accessible
at vaultwarden.vault.
Downgrade vaultwarden.vault to 2022.10.0, see https://github.com/dani-garcia/vaultwarden/releases/tag/1.26.0

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg test vaultwarden

Did we had this vaultwarden in the old release already?

We have 1.26.0 in release-22.11, paired with webvault 2022.6.2. The update was stuck because it failed the nixos tests.
https://github.com/NixOS/nixpkgs/pull/206098

Downgrade vaultwarden.vault to 2022.10.0, see https://github.com/dani-garcia/vaultwarden/releases/tag/1.26.0

Can a newer frontend actually cause incompatibilities? I'd think it's just another client that sends JSON to the server and Vaultwarden is definitely compatible with multiple versions of the desktop client.

Whether new frontend versions break gracefully or not I don't know.


Extraction of SBS10a/SBS10b signatures and row order in the input matrix

Hi,
I am using SigProfilerExtractor to determine the mutational signatures of a set of 43 WGS samples with polymerase epsilon exonuclease domain mutations. Some of the samples originate from TCGA and are known POLE mutants, however in none of the cases the SigProfilerExtractor choses one of the POLE specific SBS signatures (10a, 10b, or 14). The problem is most evident for sample TCGA-AA-3510 which shows a signature very similar to SBS10a combined with SBS10b, however its matched to SBS5 95.16% and SBS1 4.84%:
Wrong_Order_TCGA-AA-3510_SBS96_Decomposition_Plots.pdf
Input matrix:
TCGA-AA-3510_SBS96.txt
The figure was obtained with:
sig.sigProfilerExtractor("matrix", "results_TCGA-AA-3510", "ORI_SigProfilerMatrix_TCGA-AA-3510_SBS96.txt", reference_genome="GRCh37", minimum_signatures=1, maximum_signatures=10, nmf_replicates=100, cpu=40)
The SigProfilerMatrix (SBS96) was created using my R script based on MuTect (v1) results (filtered), since I dont have the VCFs. I initially thought that the problem might be related to a different order of mutation counts in the input matrix, which affected the plot above (the Original panel has a different mutation order compared to the Reconstructed one). However after correcting the counts table and running SigProfilerExtractor another problem emerged, since not only the reconstruction appears to be bad, but significantly different from the first version:
Correct_Order_TCGA-AA-3510_SBS96_Decomposition_Plots.pdf
Input matrix:
TCGA-AA-3510_SBS96_v2.txt
Both input files differ only in the row order.
I also have a minor issue with the De_Novo_map_to_COSMIC_SBS96.csv results file which only rarely contains the breakdown of the reconstructed signature, while the breakdown is always shown on the SBS96_Decomposition_Plots.pdf. Can this be controlled by any of the parameters? I would like to obtain the breakdown for each of my 43 samples, which doesn’t seem to be possible in a multi-sample run and in most cases can be only read from the plot while running a single sample.
I will be very grateful for your help.
Best regards,
Roman

Samples.txt
Hi Roman,
Both the orders you are using are not correct for SigProfilerExtractor input. I have attached the correct order of the mutation which is an output of the SigProfilerMatrix generator.
Also, if Devono signatures don't decompose to the COSMIC signatures with at least 0.8 cosine-similarity, you will not see any breakdown in the De_Novo_map_to_COSMIC_SBS96.csv results file. However, you will see the breakdown in the decomposition plot.
Thanks,
Mishu

Thank you, this indeed solved the problem, providing a much better fit that includes signatures 10a and 10b.
I assumed that the software checks what’s in the first column. It would be great to have an input validation step, as this problem may lead to some false findings.

Thanks for the suggestion. We will include the validation step.
Best,
Mishu


Removed fstats command

I have removed the fstats command, which is now part of xerxes of the poseidon-analysis-hs package. I have added a brief warning message to the basic CLI, so that users who might be looking for fstats can find a pointer. We can eventually remove that, of course.

Codecov Report

Merging #151 (8f10fde) into master (b05ba8e) will increase coverage by 4.45%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #151      +/-   ##
==========================================
+ Coverage   65.44%   69.90%   +4.45%
==========================================
  Files          19       18       -1
  Lines        2101     1917     -184
  Branches      138      137       -1
==========================================
- Hits         1375     1340      -35
+ Misses        588      440     -148
+ Partials      138      137       -1

Impacted Files
Coverage Δ

src/Poseidon/SecondaryTypes.hs
20.96% <ø> (ø)

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 b05ba8e...8f10fde. Read the comment docs.

Yes, xerxes fstats is functional, but still contains a massive memory leak, which might be OK for 1240K data and few stats, but is something that needs fixing. I think we can indeed merge this. I'll bump the version nr also.


Has Symbol 0 disappeared in V5.2?

Reported by hankin on 15 Jun 2000 20:08 UTC
Mick says it used to be there in earlier versions
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/85

Comment by<EMAIL_ADDRESS>on 21 Oct 2003 20:15 UTC
Moving from the<EMAIL_ADDRESS>user to the<EMAIL_ADDRESS>user.

Comment by<EMAIL_ADDRESS>on 3 Nov 2003 23:11 UTC
lower the priority, reassign to Ansley

Comment by<EMAIL_ADDRESS>on 8 Jun 2007 22:10 UTC
Lowering the priority.

Comment by<EMAIL_ADDRESS>on 19 Nov 2007 20:56 UTC
Can't find reference to this. Closing the bug.


Bad request failure for sending messages to some contributors on Signal

See Sentry Issue 100EYES-1N.
tl;dr: Sometimes we receive a 400 Bad Request for some but not all contributors when sending a message.
This only affects production instances and we were not able to reproduce it yet so far. The next step is improving logging for failed message sending so that we get provided more information via Sentry the next time this happens.
Log:
The contributor with the same error on staging sadly was deleted already so that reproducing this on staging is not possible.
Re: Rate limiting: I had a look at the contributors which are affected by this issue. It always affects the same contributors, with an increasing number of contributors.
As the non-receiving contributors are completely consistent and no new signal contributors joined between 05.05. and 03.06, I feel like this is probably not a rate-limiting issue.
Re: Blocking: I then tested a few possible ways to block us on staging but non produced this error.
Unverifying / Not verifying our number: No error.
Blocking: No error - contributor doesn’t receive message but for us it looks like a successful send. On a positive note - unblocking works perfectly well.
Archiving: No error.
Re: Signal-Cli Settings: I then dived into the stored data in the signal-cli-config and tried to find any patterns for the three non-receiving contributors. However, no attention calling difference was consistent for all contributors. E.g. only one contributor doesn’t have unidentifiedAccessMode enabled. The trust level for the affected Contributors varies from 0 to 2, (as for all other contributors).
Re: Spam: I then noticed that two out of the non-receiving contributors have not answered any requests at all. However, the third contributor, had answered (nearly) all requests before becoming non-receiving. And one other signal contributor 7 has also never answered and still receives message without problem.
I was wondering if a contributor not answering many messages sent from a server ip address would at some point be detected as Spam. (Signal currently tries to crack down on Spam.) The inconsistent behaviour here seems to indicate that this is not the case.

When would we consider this issue to be closed @phoeinx? We have added the additional logging in  Add context to Signal errors #1391  and while it's been just two months since we deployed this, what we've discovered so far is that the bad request can happen for a variety of reasons. Ones I have personally seen are:

The contributor does not have their number registered with Signal any longer - support issue
The signal server phone number did not have a name added to its profile

We could maybe improve the handling of these errors and instead of sending everything to the #monitoring channel, we could parse the error response and check for some substring that lets us know that it's a support rather than a technical issue, but I guess with the lack of diversity in the non-successful responses, we will need to handle these errors on a case-by-case basis.