purescript: 0.15.8 -> 0.15.9

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for purescript is: A strongly-typed functional programming language that compiles to JavaScript
meta.homepage for purescript is: https://www.purescript.org/
meta.changelog for purescript is: https://github.com/purescript/purescript/releases/tag/v0.15.9
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.9 with grep in /nix/store/wilcbjsrm5sz53dc63ybsr9zfmmg4l9q-purescript-0.15.9
found 0.15.9 in filename of file in /nix/store/wilcbjsrm5sz53dc63ybsr9zfmmg4l9q-purescript-0.15.9

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
pulp
purescript

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wilcbjsrm5sz53dc63ybsr9zfmmg4l9q-purescript-0.15.9 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A purescript https://github.com/r-ryantm/nixpkgs/archive/86236aacd57821a65e3bb9115b47d66e5a9c0bbb.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wilcbjsrm5sz53dc63ybsr9zfmmg4l9q-purescript-0.15.9
ls -la /nix/store/wilcbjsrm5sz53dc63ybsr9zfmmg4l9q-purescript-0.15.9/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

pulp
purescript

Maintainer pings
cc @justinwoo @mbbx6spp @cdepillabout for testing.

Spago tests and purescript tests still work, so this LGTM.

supposedly there are ARM builds for purescript now but i leave this as an exercise for the reader


adb still running after scrcpy terminates causes rebuilding failure

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: Windows
scrcpy version: 1.24
installation method: manually built from wsl ubuntu 20.04
device model: Xiaomi M2011K2C (Android 11)
Android version: 11

Describe the bug
When scrcpy is initially built using ./release.sh (in which DIST is modified to /mnt/e/Tools/dist, which should be irrelevant from my perspective), it works fine. After I run scrcpy, terminate it, and then rebuild it, it says
rm -rf "/mnt/e/Tools/dist" "build-test" "build-server" \
        "build-win32" "build-win64"
rm: cannot remove '/mnt/e/Tools/dist/scrcpy-win64/adb.exe': Input/output error
rm: cannot remove '/mnt/e/Tools/dist/scrcpy-win64/AdbWinApi.dll': Input/output error
rm: cannot remove '/mnt/e/Tools/dist/scrcpy-win64/AdbWinUsbApi.dll': Input/output error

It seems to me that this is because adb.exe is still running, and after I kill it using the task manager in Windows, the rebuilding process works perfectly fine.
So I think adb.exe should be killed on exit.

https://github.com/Genymobile/scrcpy/issues/205#issuecomment-406776834


better formating for GS1_128

I would think about 3 patches, relative to gs1_128, not sure were to place them:

having a text with the Application Identifiers betwen parenthesis, optionaly having the said text with spacing for the SSCC code (to hard to retype otherwise)
avoiding repeating u'\xf1' if already written per the user
u'\xf1' is not super ... allow also the use of '<FNC1>' (translated when writing)

it would so something like that:

what of these ideas would be considered pertinent for python-barcode team ?

what of these ideas would be considered pertinent for python-barcode team ?

Generally, improvements are welcome as long as backwards compatibility is maintained and it doesn't break anything.
Suport for '<FNC1>' sounds reasonable and useful.
I'm not sure I fully understand the parenthesis. Do you just allow then in the input but ignore them for the barcode itself?


In the narrow view, close button for the panel disappears

Testing #36571

Toggle Terminal using Ctrl+`
Move the panel to the right
Keep decreasing the panel size and stop before the whole panel disappears

The close button is missing

Now choose "Debug Console" from the overflow menu

The close button is back

Choose Problems or Output, close button disappears

Dup of https://github.com/Microsoft/vscode/issues/37242


Code quality suggestions

Here are some suggestions that I have as I am working through as part of my review at https://github.com/openjournals/joss-reviews/issues/1824.
I don't consider any of these to be blocking for the review, so feel free to act on or not to act on my suggestions as you are able!

[ ] Don't shadow names of built in functions (Atom having an id attribute) or standard library modules (the pickle.py module and all the tests importing the sys module, but then the API uses sys = pc.System(), overwriting that name) (reference)
[ ] Don't use mutable parameters as default function arguments, examples: "customkeys=[]" and "repetitions=[1, 1, 1]" (reference)

Thanks for the great suggestion. I have fixed most of the above issues in the commit 50ebe76d9ceda5c4dbacdac118c2534c6c9f02ce except for Atom having an id attribute. I think I will keep this as it is for now so that the keyword makes sense to the users.


Set account currency.

Add a field to Sender to specify account currency (not necessarily equal to transaction currency). If nil or not supplied, keep using EUR.
Also pulls recent (as in 2013) changes from upstream.

The code is still poor, it probably needs a rewrite to look more Ruby, less rewrite-this-C-code-I-have-lying-here. Didn't change that.

Commits to check: 8f02110 and 06f9244. all the rest is upstream.


Updating hello-thirdparty to have a subproject to download gpg-sdk

This minimizes the configuration steps needed to make the sample run.
Also, adding .gitignore files to the project.

Seems like gradle can publish arbitrary artefact https://docs.gradle.org/current/userguide/artifact_management.html is that something we should explore in parallel?

don't worry about appveyor failing that's a work in progress.

@proppy  - Updated based on your feedback. PTAL

@claywilkinson can you also update travis to remove gpg download and extraction?

@proppy  - travis.yaml updated.

small nits but apart from that LGTM if travis is green.

travis is green, merging.


Implement garbage collection to prevent memory leaks

Opening this as a draft. This works to resolve the specific issue described in https://github.com/pydantic/pydantic/issues/5136, but probably we'll take a completely different approach before merging that will be cleaner.
Copying some messages out of slack:

you might be able to add traverse to Validator trait, with default doing nothing
then implement it for Model
they way you can just call self.serializer.traverse
I mean Validator and Serializer

you mean TypeSerializer?

probably
the thing  which enum_dispatch requires all members to implement
on both serializer and validator

any chance we can add a test which would have broken before?

Codecov Report

Merging #415 (1082404) into main (ad5005a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #415   +/-   ##
=======================================
  Coverage   95.49%   95.50%
=======================================
  Files          90       90
  Lines       10685    10695   +10
  Branches       10       10
=======================================
+ Hits        10204    10214   +10
  Misses        480      480
  Partials        1        1

Impacted Files
Coverage Δ

src/serializers/type_serializers/model.rs
86.66% <ø> (ø)

src/serializers/mod.rs
99.28% <100.00%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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

Do we also need to call __traverse__ on SchemaValidator.schema?
@adriangb added SchemaValidator.schema last year so pickling of SchemaValidator worked, but I think we should let such pickling fail, and just rebuild SchemaValidator when unpickling a BaseModel or Validator.
maybe we __traverse__ it for now, and discuss removing it on a new issue?

Do we also need to call __traverse__ on SchemaValidator.schema?
@adriangb added SchemaValidator.schema last year so pickling of SchemaValidator worked, but I think we should let such pickling fail, and just rebuild SchemaValidator when unpickling a BaseModel or Validator.
maybe we __traverse__ it for now, and discuss removing it on a new issue?

It seems like just visiting SchemaValidator.schema works, so no need to remove it. If we re-built it every time that would crush performance when sending things across process boundaries (which pickles the object IIRC).

Closing in favor of #416


Add new parameter  AccountTypeID. Fix Username Bug.

Add new parameter AccountTypeID, allowing you to set an account type icon.
Switched to using PSBoundParamaters, which fixed bug where username would not be sent.

Thanks!


Deploying Keras Models To Android

Summary
Tutorial on how to deploy Keras model to Android
Related Issues
Fixes #11778
PR Overview

[n] This PR requires new unit tests [y/n] (make sure tests are included)
[y] This PR requires to update the documentation [y/n] (make sure the docs are up-to-date)
[y] This PR is backwards compatible [y/n]
[n] This PR changes the current API [y/n] (all API changes need to be approved by fchollet)

@saadmanrafat if you need some inspiration for an end to end example I have done this here: https://github.com/skonto/talks/blob/master/spark-summit-2018-London/models/iris.py
and here:
https://github.com/skonto/talks/blob/master/spark-summit-2018-London/mltest/feature/src/main/java/com/github/com/ml_test/feature/IrisClassifier.java

@skonto thanks. I will take a look at them.


Adjusted ordering string matching to be exact when wildcard is not pr…

I encountered an issue with orderOfOperations that appear to stem from issue https://github.com/apideck-libraries/portman/issues/122 and the fix https://github.com/apideck-libraries/portman/pull/216.
The matching for ordering was performing a starts with match, which would cause GET::/endpoint/:id to also match GET::/endpoint/:id/someOtherEndpoint, which threw off any other operations I have would between the two.
I experienced some success locally with adding a string terminator to the regex matching, so that non-wildcard entries would expect match operation.

I just ran into this myself. Do you know when this will be released?

hi @jackdclark
We want to include 2 more PRs (including your #520) in the next release. We have asked for some minor changes to be made by you and the other contributor. Once they land, we will release a new version.
If it takes longer, we will release a new version without the PRs.


Bartek branch

Made the nav/sidebar component"

Mike, can you please add my code back in there and clean up the files so that any code that is not needed outside of the facebook oAuth. I want to make sure we are keeping all this clean. I'd rather you test it with the code i have in there instead of putting it in comments ans then we realize that its not working when we merge it. Thank you sir.

Mike, can you please add my code back in there and clean up the files so that any code that is not needed outside of the facebook oAuth. I want to make sure we are keeping all this clean. I'd rather you test it with the code i have in there instead of putting it in comments ans then we realize that its not working when we merge it. Thank you sir.


This project is compatible with Visual Studio 2008. The issue here is that you are building with a later version of Visual Studio and there has been significant (breaking) changes with later versions of Visual Studio.
I have frozen development on this project as it is the final year project of my bachelors degree.

@collinsmichael good luck finishing up the degree! It'll be neat to see this project working again at some point if you ever get time


fix: Fix exceptions in StreamingEngine when reloading

When reloading MediaSourceEngine via StreamingEngine, some logic executed before the reload cancels operations and aligns StreamingEngine state with MediaSourceEngine.
However, additional logic was executed after setStreamProperties, which caused a race condition that broke StreamingEngine state by manipulating it out of the usual sequence and outside the usual methods, leading to exceptions and failed assertions.  This removes that unnecessary logic and leaves subtle state management to the functions that are meant to do it.
Closes #6458

@shaka-bot test


[Question] Problem with EF Core migrations with IHostBuilder

Hi,
I came across an issue regarding the change from WebHostBuilder to HostBuilder in 3.0 Prev2.
We're using EF Core migrations.
With the new HostBuilder the cmdlet Add-Migration fails with complaining about either a missing parameterless constructor or IDesignTimeDbContextFactory (design-time DbContext creation).
This was not necessary when using a WebHostBuilder in 2.1 It seems that the DbContext options are not injected properly.
In the meantime, I can workaround this using the WebHostBuilder.
Is there any workaround for this change?
Thanks
Sven

Also cc @ajcvickers @divega @bricelam

cc @Tratcher

Fixed here: https://github.com/aspnet/EntityFrameworkCore/pull/14378 (preview 3?)

Does your Program.cs match this? https://github.com/aspnet/AspNetCore/blob/dffe9abf6b6b009e183e808459e65770c9210a52/src/ProjectTemplates/Web.ProjectTemplates/content/EmptyWeb-CSharp/Program.cs#L14-L26

@Tratcher
Yes that's the code in my Program.cs
I get the error
Unable to create an object of type 'QualityAssuranceDataContext'. Add an implementation of 'IDesignTimeDbContextFactory' to the project, or see https://go.microsoft.com/fwlink/?linkid=851728 for additional patterns supported at design time.

Closing as external since I believe this is already fixed for preview3.

🤦♂ This will land in core 3.0? So for us in 2.2 using IHostBuilder there's no way to get EF Add-Migration to work.

@oliverjanik can you clarify what you mean? We switched to use the IHostBuilder as part of 3.0, there's no known regression here in 2.2.

IHostBuilder should work with EF Core 2.2 (however you managed to do that) if you name the method CreateWebHostBuilder


smoke-test

Docs Build status updates of commit 2c06afd:
:clock10: Full build: the average full build time is 73 min(s) 21 sec(s), this is based on the last 380 build(s) for this repository.

Docs Build status updates of commit 2c06afd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

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.

Docs Build status updates of commit 10c111d:
:clock10: Full build: the average full build time is 73 min(s) 22 sec(s), this is based on the last 381 build(s) for this repository.

Docs Build status updates of commit 10c111d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.azure.sdk.iot.device.DeviceTwin.Property.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.microsoft.azure.sdk.iot.service.devicetwin.Pair.yml
:white_check_mark:Succeeded
View (azure-java-stable)

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.

Docs Build status updates of commit 5e7a033:
:clock10: Full build: the average full build time is 73 min(s) 26 sec(s), this is based on the last 387 build(s) for this repository.

Docs Build status updates of commit 5e7a033:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docfx.json
:white_check_mark:Succeeded

docs-ref-autogen/com.microsoft.azure.sdk.iot.device.DeviceTwin.Property.yml
:white_check_mark:Succeeded
View (azure-java-stable)

docs-ref-autogen/com.microsoft.azure.sdk.iot.service.devicetwin.Pair.yml
:white_check_mark:Succeeded
View (azure-java-stable)

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.


Fix docker run command for BAMOE Canvas

Environment variables should be set before the image name in the command: https://docs.docker.com/engine/reference/commandline/run/#usage

@LightGuard I don't have an answer for that :confused:
If the image repo changes in the future there might be more things to change in the documentation.

Yes! Should I open another PR cherry-picking this to 9.x?

@tiagobento Not sure why it isn't recognizing your approval as one of the ones necessary.


feat: Support GCS custom query files

Closes #1148
Allows for GCS file paths for custom query source/target files.

/gcbrun

/gcbrun


{Servicebus} Add Breaking change message for az servicebus georecovery-alias fail-over cmdlets

Related command

Description
parameters argument will be removed from az servicebus georecovery-alias fail-over cmdlets in future release.
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Servicebus

Hey @evelyn-ys , the fail-over cmdlets is not present in param.py file.
I want to deprecate the parameters argument from az servicebus georecovery-alias fail-over cmdlets.
Where do i write the deprecate_info here. So instead of this I have added warning & description.

@schaudhari6254888  If there's no existing argument definition, you can add by yourself

@schaudhari6254888 If there's no existing argument definition, you can add by yourself

Hey @evelyn-ys, I have tried like this
with self.argument_context('eventhubs georecovery-alias fail-over') as c:
c.extra('parameters', deprecate_info=c.deprecate(expiration='2.50.0'))
   But CI's were failing saying that missing help for parameters in fail-over command

Add help=... for the argument
You shouldn't use c.extra but c.argument

Please learn how to authoring CLI first https://github.com/Azure/azure-cli/blob/dev/doc/authoring_command_modules/authoring_commands.md#customize-arguments


feat: Introduce compatibility with native namespace packages

Similar to https://github.com/googleapis/google-auth-library-python/pull/1205
Also see https://packaging.python.org/en/latest/guides/packaging-namespace-packages/#native-namespace-packages

Adding do not merge as there is an upcoming release freeze. This should be merged after the release freeze ends on November 29th.


Make INFO-level logs not red in PyCharm

Description & Motivation
In PyCharm, informational messages from Lightning are printed in red, which doesn't look great and obscures real errors.
This is because the logger is printing to stderr and PyCharm by default makes that red.

Pitch
You can fix this by tweaking your root logger to print to stdout for INFO and below, and stderr for everything else. All the other loggers will inherit from this
In pytorch_lightning/__init__.py:
_logger = logging.getLogger(__name__)
_logger.setLevel(logging.INFO)

# log lower levels to stdout
stdout_handler = logging.StreamHandler(stream=sys.stdout)
stdout_handler.addFilter(lambda rec: rec.levelno <= logging.INFO)
_logger.addHandler(stdout_handler)

# log higher levels to stderr (red)
stderr_handler = logging.StreamHandler(stream=sys.stderr)
stderr_handler.addFilter(lambda rec: rec.levelno > logging.INFO)
_logger.addHandler(stderr_handler)

Which then prints like so:

Alternatives
No response
Additional context
No response
cc @borda

I'm not sure if there is a real reason behind why we default to stderr. Sounds good to me, we can give this a try.

It's actually a Python default, nothing Lightning has done specifically.
If you're feeling really fancy, you can define a handler that will log in the appropriate color for each level:
class ColorHandler(logging.StreamHandler):
    # https://en.wikipedia.org/wiki/ANSI_escape_code#Colors
    GRAY8 = "38;5;8"
    GRAY7 = "38;5;7"
    ORANGE = "33"
    RED = "31"
    WHITE = "0"

    def emit(self, record):
        # Don't use white for any logging, to help distinguish from user print statements
        level_color_map = {
            logging.DEBUG: self.GRAY8,
            logging.INFO: self.GRAY7,
            logging.WARNING: self.ORANGE,
            logging.ERROR: self.RED,
        }

        csi = f"{chr(27)}["  # control sequence introducer
        color = level_color_map.get(record.levelno, self.WHITE)

        print(f"{csi}{color}m{record.msg}{csi}m")

logging.getLogger(__name__).addHandler(ColorHandler())

If you're feeling really fancy, you can define a handler that will log in the appropriate color for each level:

sounds cool to me, mind sending a draft PR? :rabbit:

Sorry I've got a full study schedule, I'm trying not to get too bogged down in other things for now. When I've finished learning AI and have a job then I'll be able to contribute more :)

When I've finished learning AI and have a job then I'll be able to contribute more :)

sure no problem, no rush :)

Logging to stderr is usually on purpose for libraries/frameworks. The main benefit is that it uses a different stream than the regular prints/logs that are generated from the user code.
This decision is mainly a "stylistic standard" but changing it would be an unavoidable breaking change.
For example, I've written PL scripts where I print results relevant to my experiment (to stdout) and pipe the command into a text file (python script.py > out.txt). Doing this change would break such workflow and would make it difficult to separate user logs from library logs.
The same can be said for colored logs. Many terminals do not support rendering so adding them can add intentionally annoying lines in between the valuable messages for the color output. Maybe this is fine as long as we adhere to the requirements in https://no-color.org. Still, a too-colorful choice can be distracting so I would ask for examples of how some experiment logs would show first.

Ah, that's a good point about libraries printing to stderr as a way to split user/3rd party logs. And thanks for letting me know about NO_COLOR.
Re the colourfulness, for the most part it makes the output less colourful (I do this in my own project to modify the output of all packages) since most things are 'info' and I see them 800 times a day.
Example of how PL looks to me:

Compared to the default (in PyCharm, which renders stderr red)

As a side-effect, this highlights places where a package is using print (first two lines) but should perhaps be using logging.info().
Adapted code to write to stderr and respect NO_COLOR:
class ColorHandler(logging.StreamHandler):
    # https://en.wikipedia.org/wiki/ANSI_escape_code#Colors
    GRAY8 = "38;5;8"
    GRAY7 = "38;5;7"
    ORANGE = "33"
    RED = "31"
    WHITE = "0"

    def emit(self, record):
        # We don't use white for any logging, to help distinguish from user print statements
        level_color_map = {
            logging.DEBUG: self.GRAY8,
            logging.INFO: self.GRAY7,
            logging.WARNING: self.ORANGE,
            logging.ERROR: self.RED,
        }

        csi = f"{chr(27)}["  # control sequence introducer
        color = level_color_map.get(record.levelno, self.WHITE)

        self.stream.write(f"{csi}{color}m{record.msg}{csi}m\n")

# See https://no-color.org/
if not os.environ.get("NO_COLOR"):
    logging.getLogger().addHandler(ColorHandler())

Implementing would still be quite a task as those greys don't print the same in all terminals so there's a lot of testing to be done to get things just right, while being mindful of accessibility contrast guidelines.

It's probably more involved than that, because in the wild people use really different terminals. I suggest looking at the rich.Console implementation as a reference. If you cmd+F for "color" in the file, you'll see several interesting details.
If you are feeling brave, feel free to open a PR for color support specifically and we can discuss details there.


biprobit or similar for binary endogenous explanatory variable

Hi,
I've asked the same question on pystatsmodels forum, sorry if it is inconvenient to use the issue tracker here for the purpose of this question.
I have a model similar to what is described in Wooldridge (econometric analysis of cross section and panel data 2nd ed.) 15.7.3 (eqs. 15.51 and 15.52). There it is said that a bivariate probit model can be used to estimate parameters. Is this or something similar implemented in linearmodels, or are you planning to implement it? e.g. systems probit/logit
Best

No plans to add non-linear models.


Revert "Merge pull request #9265 from milseman/tls_ftw"

This reverts commit 26f7659efe4c675ed1cbffcd8a691c16660dddd4, reversing
changes made to 7b927e55e8f503d2cae08fcd018df31b8615ab6c.

@swift-ci please smoke test

To unblock CI, I am going to merge this with out running CI testing.


CASSANDRA-19837: Support ORDER BY ANN in query builder

Fix CASSANDRA-19837.

There is already another PR opened for same functionality PR-1931.


Different TTS models

Great work, thank you for your contribution!
For cost purposes I tried using Neets.ai and Deepgram's TTS but cant get them to work. Terminal seems to log GPT-->TTS but not TTS --> Twilio despite following the docs and matching encoding.  Any advice would be greatly appreciated.
Thanks again!
Abe

thank you so much for the prompt response,  yes both neets.ai and deepgram tts can produce output format ulaw_8000  (mulaw_8000 in neets.ai) and i added it as a param in the request, per docs, but still not able to pass the audio to twilio.   When using base64 there is just a loud static and without base64 just silent and in both cases the terminal is showing no activity.   Any advice would be appreciated.  I just looked at openAI TTS and it seems to be a feasible solution so will try it next.  Any other ideas would be greatly appreciated.  Thanks so much! Abe

@teledoc2 Have you managed to successfully implement it with openAI TTS? I have tried but only hear static on my end. If you did, could you please share your solution?

Neets was fairly easy to implement as they support output in mulaw, worked without any issues. To get openAI TTS to work you would probably need to use something like wavefile to convert it from wav to mulaw.
      const response = await fetch(
        'https://api.neets.ai/v1/tts',
        {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
            'X-API-Key': 'xxxxxx',
            accept: 'audio/wav',
          },
          body: JSON.stringify({
            text: partialResponse,
            voice_id: 'vits-eng-1',
            fmt: 'mulaw',
            params: {
              model: 'vits'
            }
          })
        }
      )

@c0dr  Thanks! Your code works well for Neets ai API.
Do you know how we can add fillers like 'Umm', 'Sure' or 'Let me think'? I'm planning to add fillers to reduce the perception of latency between the 'human voice input' and the 'tts of gpt response'.


Add support for OpenID Connect Discovery

Publish the information of TAccounts OpenID connect implementation in a well known location so clients can automatically get the endpoint_location, public keys to verify JWT tokens, supported flows, soppurted scopes, etc.
Here are samples of implementations from Microsoft, Google and Paypal:
https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration
https://accounts.google.com/.well-known/openid-configuration
https://www.paypal.com/.well-known/openid-configuration
And the specification
https://openid.net/specs/openid-connect-discovery-1_0.html
Best regards.

This applies to Accounts Server. Please follow this at https://github.com/TDAF/accounts/issues/344


Async.converge and Async.all would be nice

Make things easier on the user.
While it is nice to use the liftA* functions for parallelism, it is such a common pattern with Async that it warrants a couple built ins to avoid a lot of boilerplate "configuration".

[ ] converge : (b -> ... -> z -> a) -> [ Async e (b...z)] -> Async e a - Takes a converge/merging function with the same arity of the length of the list of Asyncs passed as the second argument. This will fork the Asyncs in parallel and reject the lot of em if one is rejected. converge should ignore and not fork any Asyncs beyond the arity of the curried convergence function
[x] all : [ Async e a ] -> Async e [ a ] - Takes a list of Asyncs and returns an Async that when forked will fork each in parallel and result in an array of the results (just your basic traverse here, nothing fancy, but people like having something called all, so lets give'em what they want). This will reject the lot of em if one is rejected.

Submitted and merged PR#43 which takes care of the implementation of Async.all

So as I implement Async.converge I am noticing some REALLY nasty bits arising. Going to punt on that function. It is not that cool and it is easy for the consumer to map in ramda's converge if they wanna go that route.
If it gets requested, we should consider it again.


Unable to click on lookup value in UCI after saving the record with version 9.0

Hello
I am trying to check some validations on customized form in UCI, by clicking on the lookup value after saving the record.
Functionality:

Open the form and create record.
Click on specific lookup field value(which opens the specific record).
Verify specific fields to pass the test.

I am unable to to click on the lookup value after saving the record.
Multiple ways i tried:

Find the element and click
Result: NoSuchElementException

Switching to DefaultContent and than tried to find the element and click
Result: NoFrameFound exception

Has anyone faced the same problem and resolved it? Or any suggestions on how to handle this please?
Thanks

From what i understand (tell me if i'm wrong), you fill the lookup field when creating your record and then after that you want to come back to see if your field is populated?
If the case why not use getValue() on lookup instead to get the value of the field?

@Haywaii
No that is not what i said, See the screenshot below. I want to click on the lookup value marked in green after saving the record, which takes me to that record.

@Skumar2crr ah ok.
Never got this problem when clicking on a lookup value to open something else.
What's the element you try to use to click?
I got a similar action where i do
"[FindsBy(How = How.CssSelector, Using = "[data-id='customerid.fieldControl-Lookup_customerid']")]
protected internal IWebElement AccountLink { get; set; }"
I used data-id property to reach my element.
Be aware after clicking, It can give you a stale exception so you need to try/catch your click as well.


JDSB Website Redesign

Hey, everybody! I was looking at the open issues for this repo and saw that #6 and #40 suggested a change to the styling of the resources page so I thought I would give it a whirl. After completing the resources page, I realized that if we went with that design, we'd probably have to change the rest of the pages to match. Anyway, I'm not wed to anything here. If you feel now is not the time for a redesign that is fine. I'm open to any and all feedback.
Here are the mockups:
Home

Resources

I added a search bar here. I was thinking it could filter the results on the page as you type. Another idea I had but did not include was to add toggles that expand and collapse each section so the page doesn't get too long.
Upcoming Events

About

Huge fan of the redesign!
What's needed to get this done?


Build-in support for many different methods instead of only default

Expected Behavior
Users should be given an option to setup more methods instead of only primary method.
Current Behavior
When user setup for example yubikey, then in two_factor view sees "Primary method: Use your Yubikey device" and setup for another methods is not possible.
In setup this is clearly visible that this is intentional disabled:
https://github.com/jazzband/django-two-factor-auth/blob/95255bbe714830152e68c9ff2dd09dee4087a2a1/two_factor/views/core.py#L486-L492
However, in login view, many different methods are handled if they exist, for example created in custom form or via admin panel
https://github.com/jazzband/django-two-factor-auth/blob/95255bbe714830152e68c9ff2dd09dee4087a2a1/two_factor/views/core.py#L359-L367

And here how it looks when i add more methods in admin panel:

Possible Solution
Allow users to setup 2fa many times. It's already handled in login so that's for free and could be supported in account and setup views with relatively moderate code changes. Note that I am not sure why is it not a case, maybe there are some non trivial things to consider or breaking changes like that are not acceptable for some reason.
Context
For yubikey setup for eaxmple it totally makes sense and is popular to have 2 or more different keys for example one dedicated to pc, second to laptop and alternatively some backup one.

Sounds good, we would ideally want this either as part of or after #347


Randomly getting a message to update the workload

When I start the Aspire host, I randomly get the following error (and the app stops):
info: Aspire.Dashboard.DashboardWebApplication[0]
      Now listening on: http://localhost:15267
info: Aspire.Dashboard.DashboardWebApplication[0]
      OTLP server running at: http://localhost:16276
Newer version of .NET Aspire workload is required to run the application. Run 'dotnet workload update' to get it.

If I re-run the app without even recompiling, it works.
Currently using Preview 2 bits with the updated workload as of today.

Can you show the output of dotnet workload list

@davidfowl Here it is:
>dotnet workload list

Installed Workload Id      Manifest Version                     Installation Source
-----------------------------------------------------------------------------------
wasm-tools                 8.0.1/8.0.100                        VS 17.9.34414.90
aspire                     8.0.0-preview.2.23619.3/8.0.100      VS 17.9.34414.90

I'm using devcontainers and made this devcontainer feature for zero effort daily installs.
I got a similar update workload error on some of the devcontainer builds, but during a dotnet restore. It's sporadic and does not happen 100% of the time.  Of course I also did it like 50 times while building the feature 😂 rebuilding did make it go away, but rebuilding daily to get latest bits.
Next time I get it I'll paste the output here if it's the same as it may be the same issue.

I'm not 100% sure why this is happening randomly, it's coming from here.
Any ideas @bwateratmsft?

I wonder if this could be related to https://github.com/microsoft/usvc/issues/126, though it is so strange that it's not happening consistently.

I wonder if this could be related to https://github.com/microsoft/usvc/issues/126, though it is so strange that it's not happening consistently.

FYI I have no visibility over the linked repository ...

@raffaeler In %USERPROFILE%\.nuget\packages\microsoft.developercontrolplane.windows-amd64, what versions do you see?

@bwateratmsft there is no such entry:

Sorry, I gave the wrong path. That's where they used to be when packaged as a NuGet. The current location is here: C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64

No worries, here is the name of the folder inside the new location:
8.0.0-preview.1.23557.2

I currently have VS 17.9.0 Preview 4.0 .
If you believe this won't happen in Aspire Preview 3, I can live with that.

That's interesting, we would expect there to be an 8.0.0-preview.2... folder in there. What happens if you do dotnet workload update --interactive or dotnet workload repair --interactive?

Here is the full log of those two commands.
Please note that:

during the update I was requested to elevate the dotnet installer
the outcome of the repair is just what you can read below (no elevation or anything else).

**********************************************************************
** Visual Studio 2022 Developer Command Prompt v17.9.0-pre.4.0
** Copyright (c) 2022 Microsoft Corporation
**********************************************************************

C:\Program Files\Microsoft Visual Studio\2022\Preview>cd C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64

C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64>dir
 Volume in drive C has no label.
 Volume Serial Number is 6A09-FF05

 Directory of C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64

05-Jan-24  12:04    <DIR>          .
05-Jan-24  12:04    <DIR>          ..
05-Jan-24  12:04    <DIR>          8.0.0-preview.1.23557.2
               0 File(s)              0 bytes
               3 Dir(s)  383,183,831,040 bytes free

C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64>dotnet workload update --interactive

Welcome to .NET 8.0!
---------------------
SDK Version: 8.0.200-preview.23624.5

Telemetry
---------
The .NET tools collect usage data in order to help us improve your experience. It is collected by Microsoft and shared with the community. You can opt-out of telemetry by setting the DOTNET_CLI_TELEMETRY_OPTOUT environment variable to '1' or 'true' using your favorite shell.

Read more about .NET CLI Tools telemetry: https://aka.ms/dotnet-cli-telemetry

----------------
Installed an ASP.NET Core HTTPS development certificate.
To trust the certificate, run 'dotnet dev-certs https --trust'
Learn about HTTPS: https://aka.ms/dotnet-https

----------------
Write your first app: https://aka.ms/dotnet-hello-world
Find out what's new: https://aka.ms/dotnet-whats-new
Explore documentation: https://aka.ms/dotnet-docs
Report issues and find source on GitHub: https://github.com/dotnet/core
Use 'dotnet --help' to see available commands or visit: https://aka.ms/dotnet-cli
--------------------------------------------------------------------------------------

No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.
Updated advertising manifest microsoft.net.workload.emscripten.net7.
Updated advertising manifest microsoft.net.workload.mono.toolchain.net7.
Updated advertising manifest microsoft.net.workload.emscripten.net6.
Updated advertising manifest microsoft.net.workload.mono.toolchain.current.
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.workload.emscripten.current.
Updated advertising manifest microsoft.net.workload.mono.toolchain.net6.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.sdk.maui.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.sdk.tvos.
Failed to update the advertising manifest microsoft.net.sdk.aspire: Failed to validate package signing.

Verifying Microsoft.NET.Sdk.Aspire.Manifest-8.0.100.Msi.x<IP_ADDRESS>-preview.4.24079.1

error: NU3004: The package is not signed.

Package signature validation failed.

.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Downloading microsoft.net.sdk.android.manifest-8.0.100.msi.x64 (34.0.80)
Installing microsoft.net.sdk.android.manifest-8.0.100.msi.x64 .... Done
Downloading microsoft.net.sdk.ios.manifest-8.0.100.msi.x64 (17.2.8020)
Installing microsoft.net.sdk.ios.manifest-8.0.100.msi.x64 .... Done
Downloading microsoft.net.sdk.maccatalyst.manifest-8.0.100.msi.x64 (17.2.8020)
Installing microsoft.net.sdk.maccatalyst.manifest-8.0.100.msi.x64 .... Done
Downloading microsoft.net.sdk.macos.manifest-8.0.100.msi.x64 (14.2.8020)
Installing microsoft.net.sdk.macos.manifest-8.0.100.msi.x64 .... Done
Downloading microsoft.net.sdk.maui.manifest-8.0.100.msi.x64 (8.0.6)
Installing microsoft.net.sdk.maui.manifest-8.0.100.msi.x64 .... Done
Downloading microsoft.net.sdk.tvos.manifest-8.0.100.msi.x64 (17.2.8020)
Installing microsoft.net.sdk.tvos.manifest-8.0.100.msi.x64 .... Done
No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.

Successfully updated workload(s): .

C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64>dir
 Volume in drive C has no label.
 Volume Serial Number is 6A09-FF05

 Directory of C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64

05-Jan-24  12:04    <DIR>          .
05-Jan-24  12:04    <DIR>          ..
05-Jan-24  12:04    <DIR>          8.0.0-preview.1.23557.2
               0 File(s)              0 bytes
               3 Dir(s)  383,170,129,920 bytes free

C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64>dotnet workload repair --interactive

No workloads are installed, nothing to repair. Run `dotnet workload search` to find workloads to install.

C:\Program Files\dotnet\packs\Aspire.Hosting.Orchestration.win-x64>

Is the NuGet signing error the culprit?

@danegsta do you have any ideas? It's strange the workload doesn't seem to be fully installing and even stranger that the error is intermittent.

@raffaeler how often does this error occur?

It used to happen quite often. After you asked me to run the two command lines, now it always fails.
This is what I see in the output window:
Build started at 21:27...
1>------ Build started: Project: AspireStarter.ServiceDefaults, Configuration: Debug Any CPU ------
1>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
1>Skipping analyzers to speed up the build. You can execute 'Build' or 'Rebuild' command to run analyzers.
1>AspireStarter.ServiceDefaults -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ServiceDefaults\bin\Debug\net8.0\AspireStarter.ServiceDefaults.dll
2>------ Build started: Project: AspireStarter.Web, Configuration: Debug Any CPU ------
3>------ Build started: Project: AspireStarter.ApiService, Configuration: Debug Any CPU ------
3>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
2>Skipping analyzers to speed up the build. You can execute 'Build' or 'Rebuild' command to run analyzers.
2>AspireStarter.Web -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.Web\bin\Debug\net8.0\AspireStarter.Web.dll
3>Skipping analyzers to speed up the build. You can execute 'Build' or 'Rebuild' command to run analyzers.
3>AspireStarter.ApiService -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ApiService\bin\Debug\net8.0\AspireStarter.ApiService.dll
4>------ Build started: Project: AspireStarter.AppHost, Configuration: Debug Any CPU ------
4>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To build this project, the following workloads must be installed: aspire
4>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.ImportWorkloads.targets(38,5): error NETSDK1147: To install these workloads, run the following command: dotnet workload restore
4>Done building project "AspireStarter.AppHost.csproj" -- FAILED.
========== Build: 3 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
========== Build completed at 21:28 and took 05.902 seconds ==========

@raffaeler It looks like your machine has an advertising manifest for the main branch build of aspire (that would happen if you're running the dotnet workload commands from the Aspire repo).
If you want to install the latest main branch build of Aspire, you can follow the instructions here.
From an elevated powershell terminal:
dotnet workload update --skip-sign-check --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json
dotnet workload install aspire --skip-sign-check --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json

If you want the latest release build (preview 3 is currently being finalized) you can run the script from the Aspire repo mentioned here.
From an elevated powershell terminal in the Aspire repo (with main or release/8.0-preview3 checked out):
./eng/installLatestFromReleaseBranch.ps1

@danegsta This is a fresh-installed VM with VS2022 and VS2022 Preview.
I never cloned the Aspire repo on this machine. I cloned the Aspire-samples repo.
Finally, you can see that I repeated the workload commands from a folder which does not contain any repo and the result were the same.
The big question is: what else could have happened here? Apparently my machine does not fit the scenario you mentioned.
If you want me to run the scripts, please tell me if you prefer me to clone the Aspire repo and try the Preview 3 pre-release or the first two commands.

@raffaeler dotnet maintains a local cache of available workload versions (pulled from nuget feeds) that can get updated by seemingly unrelated actions like restoring projects. I see a reference to version 8.0.0-preview.4.24079.1 of the Aspire workload (which is a recent main branch build). That means you've likely got a project somewhere that references the dotnet8 feed and restoring that unexpectedly caused your dotnet to pickup the main branch Aspire workload as the next available version.
If you don't mind running the latest development build, running those first two commands would be the fastest option for getting you unblocked.
If you don't want to run a development build, a third option that doesn't require cloning the Aspire repo would be to use a rollback file to install a specific version of the workload:
Create a file named aspire-rollback.txt somewhere:
{
  `"microsoft.net.sdk.aspire`": `"8.0.0-preview.2.23619.3/8.0.100`"
}

Then, from an elevated terminal in the same directory you created that file, run:
dotnet workload update --source https://api.nuget.org/v3/index.json --from-rollback-file .\aspire-rollback.txt
dotnet workload install aspire --source https://api.nuget.org/v3/index.json --from-rollback-file .\aspire-rollback.txt

That'll force dotnet to install the current public preview 2 version of the workload from nuget.org.

@danegsta

I see a reference to version 8.0.0-preview.4.24079.1 of the Aspire workload (which is a recent main branch build). That means you've likely got a project somewhere that references the dotnet8 feed and restoring that unexpectedly caused your dotnet to pickup the main branch Aspire workload as the next available version.

Unless the Aspire-samples repo has some reference to it, I don't see how this could ever happen. I never cloned the main Aspire repo on this machine.
I just run the first two commands and this is the result:
C:\Program Files\Microsoft Visual Studio\2022\Preview>dotnet workload update --skip-sign-check --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json

No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.
Advertising manifest not updated. Manifest package for microsoft.net.workload.emscripten.current doesn't exist.
Advertising manifest not updated. Manifest package for microsoft.net.workload.mono.toolchain.current doesn't exist.
Skipping NuGet package signature verification.
Updated advertising manifest microsoft.net.sdk.maui.
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.sdk.tvos.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.workload.emscripten.net7.
Updated advertising manifest microsoft.net.workload.emscripten.net6.
Updated advertising manifest microsoft.net.sdk.aspire.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.workload.mono.toolchain.net7.
Updated advertising manifest microsoft.net.workload.mono.toolchain.net6.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Downloading microsoft.net.sdk.aspire.manifest-8.0.100.msi.x64 (8.0.0-preview.4.24079.3)
Installing microsoft.net.sdk.aspire.manifest-8.0.100.msi.x64 .... Done
No workloads installed for this feature band. To update workloads installed with earlier SDK versions, include the --from-previous-sdk option.

Successfully updated workload(s): .

C:\Program Files\Microsoft Visual Studio\2022\Preview>dotnet workload install aspire --skip-sign-check --source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet8/nuget/v3/index.json

Advertising manifest not updated. Manifest package for microsoft.net.workload.mono.toolchain.current doesn't exist.
Advertising manifest not updated. Manifest package for microsoft.net.workload.emscripten.current doesn't exist.
Skipping NuGet package signature verification.
Downloading Aspire.Hosting.Sdk.Msi.x64 (8.0.0-preview.4.24079.3)
Installing Aspire.Hosting.Sdk.Msi.x64 .... Done
Downloading Aspire.ProjectTemplates.Msi.x64 (8.0.0-preview.4.24079.3)
Installing Aspire.ProjectTemplates.Msi.x64 .... Done
Downloading Aspire.Hosting.Orchestration.win-x64.Msi.x64 (8.0.0-preview.4.24079.3)
Installing Aspire.Hosting.Orchestration.win-x64.Msi.x64 ...... Done
Downloading Aspire.Hosting.Msi.x64 (8.0.0-preview.4.24079.3)
Installing Aspire.Hosting.Msi.x64 .... Done
Downloading Aspire.Dashboard.Sdk.win-x64.Msi.x64 (8.0.0-preview.4.24079.3)
Installing Aspire.Dashboard.Sdk.win-x64.Msi.x64 ..... Done

Successfully installed workload(s) aspire.

Unhandled exception.
C:\Program Files\Microsoft Visual Studio\2022\Preview>

The last Unhandled exception and the 8.0.0-preview.4.24079.3 version are not encouraging and in fact the rebuild all fails but with a different error:
Rebuild started at 22:46...
1>------ Rebuild All started: Project: StressApp, Configuration: Debug Any CPU ------
2>------ Rebuild All started: Project: AspireStarter.ServiceDefaults, Configuration: Debug Any CPU ------
Restored C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.Web\AspireStarter.Web.csproj (in 206 ms).
Restored C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ApiService\AspireStarter.ApiService.csproj (in 206 ms).
Restored C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ServiceDefaults\AspireStarter.ServiceDefaults.csproj (in 4 ms).
Restored C:\dev.git\Experiments\Aspire\AspireStarter\StressApp\StressApp.csproj (in 17 ms).
Restored C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.AppHost\AspireStarter.AppHost.csproj (in 221 ms).
2>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
1>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
2>AspireStarter.ServiceDefaults -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ServiceDefaults\bin\Debug\net8.0\AspireStarter.ServiceDefaults.dll
3>------ Rebuild All started: Project: AspireStarter.Web, Configuration: Debug Any CPU ------
4>------ Rebuild All started: Project: AspireStarter.ApiService, Configuration: Debug Any CPU ------
4>C:\Program Files\dotnet\sdk\8.0.200-preview.23624.5\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.RuntimeIdentifierInference.targets(311,5): message NETSDK1057: You are using a preview version of .NET. See: https://aka.ms/dotnet-support-policy
1>StressApp -> C:\dev.git\Experiments\Aspire\AspireStarter\StressApp\bin\Debug\net8.0\StressApp.dll
3>AspireStarter.Web -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.Web\bin\Debug\net8.0\AspireStarter.Web.dll
4>AspireStarter.ApiService -> C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.ApiService\bin\Debug\net8.0\AspireStarter.ApiService.dll
5>------ Rebuild All started: Project: AspireStarter.AppHost, Configuration: Debug Any CPU ------
5>C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.AppHost\Program.cs(11,46,11,70): error CS0234: The type or namespace name 'AspireStarter_ApiService' does not exist in the namespace 'Projects' (are you missing an assembly reference?)
5>C:\dev.git\Experiments\Aspire\AspireStarter\AspireStarter.AppHost\Program.cs(14,29,14,46): error CS0234: The type or namespace name 'AspireStarter_Web' does not exist in the namespace 'Projects' (are you missing an assembly reference?)
5>Done building project "AspireStarter.AppHost.csproj" -- FAILED.
========== Rebuild All: 4 succeeded, 1 failed, 0 skipped ==========
========== Rebuild completed at 22:46 and took 04.379 seconds ==========

This is even more unexpected ...

Preview 3 introduced some breaking build changes (that are also in Preview 4 builds) that can cause issues if your project nugets aren't on Preview 3 or greater, particularly with regards to ProjectReference handling in the AppHost, which is likely what's causing those build failures. Since aspire-samples is still targeting 8.0.0-preview.2.23619.3 for the Aspire nuget packages it references, I'd recommend creating that workload rollback file I mentioned and using it to install preview 2 again.

@danegsta I created the file and run the first command with the elevated prompt:
C:\dev.git>dotnet workload update --source https://api.nuget.org/v3/index.json --from-rollback-file .\aspire-rollback.txt

Updated advertising manifest microsoft.net.workload.mono.toolchain.net7.
Updated advertising manifest microsoft.net.sdk.macos.
Updated advertising manifest microsoft.net.sdk.maccatalyst.
Updated advertising manifest microsoft.net.sdk.ios.
Updated advertising manifest microsoft.net.workload.emscripten.current.
Updated advertising manifest microsoft.net.workload.emscripten.net6.
Updated advertising manifest microsoft.net.workload.mono.toolchain.current.
Updated advertising manifest microsoft.net.workload.emscripten.net7.
Updated advertising manifest microsoft.net.workload.mono.toolchain.net6.
Updated advertising manifest microsoft.net.sdk.aspire.
Updated advertising manifest microsoft.net.sdk.android.
Updated advertising manifest microsoft.net.sdk.maui.
Updated advertising manifest microsoft.net.sdk.tvos.
Workload installation failed. Rolling back installed packs...
Installation rollback failed: Failed to verify authenticode signature for C:\ProgramData\dotnet\workloads\microsoft.net.sdk.aspire.manifest-8.0.100.msi.x64\8.0.0-preview.4.24079.3\cecef4140073a3a948b64581d7aa0eda-x64.msi. Error: 0x800b0100. No signature was present in the subject.
Workload update failed: Failed to verify authenticode signature for C:\ProgramData\dotnet\workloads\Aspire.Hosting.Sdk.Msi.x64\8.0.0-preview.4.24079.3\0342ec2c11552c143d61a2cdbfffd2b7-x64.msi. Error: 0x800b0100. No signature was present in the subject.

Given the above error, I didn't run the second command

Can you add --skip-sign-check to the commands? It's likely failing because the installed workload isn't signed.

@danegsta it finally worked.
I believe the whole story around the workload versions should be easier to troubleshoot.
I have indeed the dotnet8 feed on the nuget sources as suggested by another repo. But I never found any doc suggesting that a Nuget source feed could cause all this trouble.
How can I avoid this for the future?

In the short term, I would recommend removing the dotnet8 feed, since it would have only be necessary while the .NET 8 SDK was still is preview; you may also want to clear your dotnet workload advertising cache to be safe (%userprofile%\.dotnet\sdk-advertising) to make sure you don't still have references to the dev builds of Aspire there. That would keep the dotnet workload commands from trying to install preview 4 builds.
Long term, the .NET SDK team is working on several improvements to the workload experience that would include the ability to pin the workloads for a project via global.json.

Great work @danegsta and @bwateratmsft ! This is definitely painful @raffaeler, thanks for your patience! I'm going to close this issue as resolved for preview3. @danegsta if you can point to any issues with the future work it would be appreciated.
Again, thanks for the quick root causing here.

you may also want to clear your dotnet workload advertising cache to be safe (%userprofile%\.dotnet\sdk-advertising)

Thank you @davidfowl and @danegsta, I removed the feed and deleted the folder. I hope I understood correctly.

@danegsta @davidfowl
For your info, after upgrading to the latest preview of VS2022, it happened again.
I repeated this procedure specifying the Aspire preview 3 release, and I could fix that, but I didn't expect this to happen again in the first place.
Please also note that I did not re-added the nuget preview feed, so this happened with just the default nuget feed.
HTH

Create a file named aspire-rollback.txt somewhere:
{
  "microsoft.net.sdk.aspire": "8.0.0-preview.2.23619.3/8.0.100"
}

Then, from an elevated terminal in the same directory you created that file, run:
dotnet workload update --source https://api.nuget.org/v3/index.json --from-rollback-file .\aspire-rollback.txt
dotnet workload install aspire --source https://api.nuget.org/v3/index.json --from-rollback-file .\aspire-rollback.txt

That'll force dotnet to install the current public preview 2 version of the workload from nuget.org.


Added a bash script to test program-list.json order

I added "Synology" program to the list below "Synack" to respect the alphabetical order, hope it makes your life easier @codingo

Added a tool to adress issue #113. This is my first code contribuition to a project, it was pretty fun, so thank you for the encouragement @codingo. I gonna upgrade this tool later... Thinking in add a option to receive a json file via link, so that way you don't have to download every "program-list.json" file for every pull request. What do you think? Any other ideas?

Also, I used the python script from #145 (with some little changes) to order the json file, but could'nt find a good way to compare two json's with in python, hences the bash script. Gonna give a look on that later too, and try to make it all in python :)

Oh, nice one @mendesfabio, ty for that

Removed the Synology program I added earlier, because it was added on #150

@adiffpirate could you please resolve the conflicts here and then I'll revisit?

I think it's all resolved @codingo

Sorry for bother you @codingo, but I just remembered about your tweet last week and wondered if that offer applies in my case 😅 Again, sorry if I'm being indiscreet or something like that

I was confident I'd already sent you one in another pull request but I can't find a reference. Could you let me know your twitter account and I'll send you a voucher?

Here sir, thank you so much ❤

Thank-you, sent to you now!


How to add features elementwise to separate GRU

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[x] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/fchollet/keras.git --upgrade --no-deps

[x] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[x] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

Hi all,
I am new to ML and Keras and I have a question about the connection between CNN and RNN.
My current network has 3 CNN- and 1 RNN (GRU) -Layers. Data is TimeDistributed, but I think it doesn't matter.  My model looks like the following:
model = Sequential()
model.add(TimeDistributed(Conv2D(16, (5, 3), kernel_initializer="he_normal", activation='relu'), input_shape=self.input_shape))
model.add(TimeDistributed(Conv2D(32, (3, 3), kernel_initializer="he_normal", activation='relu')))
model.add(TimeDistributed(Flatten()))
model.add(GRU(128))
model.add(Flatten())
model.add(Dense(512))
model.add(Dropout(0.5))
model.add(Dense(self.nb_classes, activation='softmax'))

I'm trying to add the features separately into a GRU-Unit for each to get a feature-vector over time for each feature (see image below (red frame)). Now, the only thing I have is a feature-vector of 32 flatted features, which are all feed into one GRU-Layer (see image below ("current situation")).

Is there anything that I can do between the CNN and RNN to get the desired behavior?
Thank you so much in advance.

To solve your issue you have to use the Keras' functional API (https://keras.io/getting-started/functional-api-guide/) to be able to split a layer output and define which input the model should use for your following layers.
An example for this would be the following (and excuse me for using my dimensions):
input = Input(shape=(400, 65, 17))   # 400 frames of 65x17 image
time_distr_conv = TimeDistributed(Conv2D(4, (3, 3), kernel_initializer='he_normal', activation='relu'))(input)
flatten_conv = TimeDistributed(Flatten())(time_distr_conv)

first_quarter = crop(2, 0, 945)(flatten_conv)
second_quarter = crop(2, 945, 1890)(flatten_conv)
third_quarter = crop(2, 1890, 2835)(flatten_conv)
fourth_quarter = crop(2, 2835, 3780)(flatten_conv)

gru1 = GRU(256)(first_quarter)
gru2 = GRU(256)(second_quarter)
gru3 = GRU(256)(third_quarter)
gru4 = GRU(256)(fourth_quarter)

merge_grus = keras.layers.concatenate([gru1, gru2, gru3, gru4])
dense_merge = Dense(256, kernel_initializer='normal', activation='relu')(merge_grus)
...
model = Model(inputs=[input], outputs=output)
model.summary()

marc-moreaux commented his crop function on this issue: https://github.com/keras-team/keras/issues/890 (thanks btw!)
def crop(dimension, start, end):
    # Crops (or slices) a Tensor on a given dimension from start to end
    # example : to crop tensor x[:, :, 5:10]
    # call slice(2, 5, 10) as you want to crop on the second dimension
    def func(x):
        if dimension == 0:
            return x[start: end]
        if dimension == 1:
            return x[:, start: end]
        if dimension == 2:
            return x[:, :, start: end]
        if dimension == 3:
            return x[:, :, :, start: end]
        if dimension == 4:
            return x[:, :, :, :, start: end]
    return Lambda(func)

In order to make this approach work for your task, you simply have to adjust the dimensions used in the input and the gru variables.
I hope this helps and let me know if this works for you!
Cheers,
Pascal


Pwa-450 e2e test cart

Pull Request Test Coverage Report for Build 1310

0 of 39 (0.0%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 35.594%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pages/Cart/components/PaymentBar/components/Content/components/SubTotal/index.jsx
0
1
0.0%

pages/Cart/components/PaymentBar/components/Content/components/ShippingCostsLabel/index.jsx
0
1
0.0%

e2e/integration/ProductPage.js
0
1
0.0%

pages/Cart/components/Item/components/Product/index.jsx
0
1
0.0%

e2e/helper/cart.js
0
5
0.0%

e2e/integration/CartPage.js
0
30
0.0%

Totals

Change from base Build 1308:
-0.2%

Covered Lines:
1234

Relevant Lines:
3374

💛  - Coveralls


[CI:TOOLING] Fix missing uuidgen tool

Previously this tool was used by a few container images as a half-hearted attempt at thwarting guesses of the credentials filename.  For whatever reason the uuidgen command is no longer present in the latest base images but this anti-thwart measure is also unnecessary and not very effective, remove it.

Oh, thanks @edsantiago I was intending to merge this, but was stuck in a meeting.


ModuleNotFoundError: No module named scipy.special._cdflib with SciPy-1.13.0

python -m nuitka --version
2.1.4
Commercial: None
Python: 3.11.0 (main, Oct 24 2022, 18:26:48) [MSC v.1933 64 bit (AMD64)]
Flavor: CPython Official
Executable: C:\Users\SrikanthRavipati\AppData\Local\Programs\Python\Python311\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.35.32215\bin\Hostx64\x64\cl.exe  (cl 14.3).

Installed Nuitka using pip
python -m pip install --upgrade nuitka

The specific PyPI names and versions, using python -m pip freeze
numpy==1.26.4
scipy==1.13.0

Example
from scipy.stats import median_abs_deviation

Provide in your issue the Nuitka options used
python -m nuitka --standalone .\test_scipy_1.13.py

Traceback (most recent call last) -- last two lines:
 File "scipy\\special\\_ufuncs.pyx", line 1, in init scipy.special._ufuncs
 ModuleNotFoundError: No module named 'scipy.special._cdflib'```

i got the same issue with pyinstaller

Thanks for your report, this is fixed on the factory branch, which is a development version under rapid development. You can try it out by going here: https://nuitka.net/doc/factory.html
Feedback if this is working is very welcome, just please do not share plans of doing it, but rather confirmations or denials of it working.

Part of the 2.1.5 hotfix I just made.

It's working. Thanks for the prompt response!


curl_multi with event loop.

Don't write you own loop, use https://packagist.org/packages/react/event-loop as it is the most active on packagist.

Implemented! Works nicely.


Fix sanic tests for 20.12.x

What does this pull request do?
Sanic 20.12.3 supports string type but not str type. Sanic 22.3.0 supports str but not string. 🤦♂
Skip the test for the old version, which is less important than the newest version.

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-04-07T15:51:41.959+0000

Duration: 21 min 52 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
4820

Skipped
3208

Total
8028

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

/test linters : Run the Python linters only.

/test full : Run the full matrix of tests.

/test benchmark : Run the APM Agent Python benchmarks tests.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Harmonize the generated C code from apps/dhparam with apps/dsaparam

I'm not convinced the harmonisation is required.

It's a matter of consistency. I find it surprising to have different styles in the output of a single tool. But of course, there's no technical need for the harmonization.

I'm pushing v2 of this series. I hope I have addressed all remarks.

We seem to have been removing NULL checks on entry to the library.  The documentation, in this case, doesn’t say anything about p or g being NULL, only that q being NULL is handled properly.  Is this a case of can’t be NULL or shouldn’t be NULL?
Personally, I’m in favour of all public APIs checking their parameters for being NULL (and other easy to check failure conditions).  Based on commits I’ve seen, the toolkit seems to be moving away from this.
I’ll support the consensus of regardless of my opinion.
Pauli

On 27 Jul 2018, at 7:21 pm, Andy Polyakov<EMAIL_ADDRESS>wrote:
@dot-asm commented on this pull request.
In apps/dhparam.c https://github.com/openssl/openssl/pull/6797#discussion_r205715675:

                     "\n"

                     "    if (dh == NULL)\n"
                     "        return NULL;\n");

   BIO_printf(out, "    dhp_bn = BN_bin2bn(dhp_%d, sizeof(dhp_%d), NULL);\n",

   BIO_printf(out, "    if (!DH_set0_pqg(dh,\n");

The current code catches NULL but these checks are being (slowly) removed as per the current policy.
??? Goal is not to remove all NULL checks, but to remove redundant checks. Those that can't be NULL (e.g. EC_GROUP->order), or are not permitted to be NULL (e.g. similar to memcpy).
As for break or not. One has to recognize that we are looking at new structure, i.e. without parameters being set. In this case set0 performs the NULL checks. And those checks are not going away. Well, one can still argue that this is equivalent to making an assumption about implementation...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/openssl/openssl/pull/6797#discussion_r205715675, or mute the thread https://github.com/notifications/unsubscribe-auth/ARFiwX_wmF7b8l9UoO1v6MqY3xLAA8Beks5uKtuVgaJpZM4VisE5.

We seem to have been removing NULL checks on entry to the library.  The documentation, in this case, doesn’t say anything about p or g being NULL, only that q being NULL is handled properly.  Is this a case of can’t be NULL or shouldn’t be NULL?

There are some conditions, but if you look at the implementation of DH_set0_pqg, you'll see that we do check for NULL.

Personally, I’m in favour of all public APIs checking their parameters for being NULL (and other easy to check failure conditions).  Based on commits I’ve seen, the toolkit seems to be moving away from this.

We had quite some debate about that a few years ago, and the conclusion was that indeed, we do not check for NULL on input arguments unless NULL is a valid value (such as for the freeing functions)

I'm with the group decision here.  That DH_set0_pqg currently checks for NULL arguments doesn't mean it always will.  The changes here will fail catastrophically if one of the called routines fails and returns NULL and DH_set0_pqg ever doesn't check for the condition.
Defensive programming is generally a good thing.

@paulidale do you still think this needs changes?

For the record, I don't agree with squashing these commits into one, especially when you don't put a proper one-line commit summary at the top. The number of commits is not rationed, is it? I am the author of this patch and this reflects badly on me, not on the committer.

I apologise for squashing them.


Enable regular pylint error checks

Rationale
pylint is a useful tool that performs rather thorough linting of Python code, and its --errors-only mode will only report suspected bugs, letting us continue using black and flake8 for style guidance.
This is more of an umbrella issue, as the effort to enable regular Pylint runs would mean fixing all the bugs it finds first, and right now it detects 150+ issues (some of which are definitely false positives).

@vnlitvinov can you please give us a summary comparison of pylint vs bandit?

why was it closed?

I think pylint will be good, let's reopen.


Feature/avatar component

Description
Task link: https://trello.com/c/Fvz98TFA/216-avatar-component
Added Avatar component
Test Steps

Ensure the component's structure, stories, and testing suite are robust.
Confirm that all tests are successful.
Check that the Avatar component displays correctly in both storybook and sample downstream applications.

 <AvatarFallback className={classNames.fallback}>
        <panda.div
          height="inherit"
          justifyContent="center"
          alignItems="center"
          display="flex"
        >
          {fallback}
        </panda.div>
      </AvatarFallback>
      ```
test

this seems redundant with the panda.div inside the fallback, but it was a struggle to get content aligned without doing this. If anyone cares to give it a go and see what they can do, please do!
 <AvatarFallback className={classNames.fallback}>
        <panda.div
          height="inherit"
          justifyContent="center"
          alignItems="center"
          display="flex"
        >
          {fallback}
        </panda.div>
      </AvatarFallback>
      ```

Close! Make sure that the closing dashes are on the same indent level as the opening, example:
 <AvatarFallback className={classNames.fallback}>
        <panda.div
          height="inherit"
          justifyContent="center"
          alignItems="center"
          display="flex"
        >
          {fallback}
        </panda.div>
  </AvatarFallback>

this seems redundant with the panda.div inside the fallback, but it was a struggle to get content aligned without doing this. If anyone cares to give it a go and see what they can do, please do!
 <AvatarFallback className={classNames.fallback}>
        <panda.div
          height="inherit"
          justifyContent="center"
          alignItems="center"
          display="flex"
        >
          {fallback}
        </panda.div>
      </AvatarFallback>
      ```

Will check it out in PR! Ty for the grind man. You are killing it

Had some inspiration with the text being offset in the fallback and added a margin to counterbalance the borderWidth which was affecting it.


ESP32 with OV2640 get 0x20001

I have the MAKERFACTORY M5Stack ESP32 Kamera mit OV2640 (2.0 MP)
(https://www.conrad.de/de/p/makerfactory-m5stack-esp32-kamera-mit-ov2640-2-0-mp-1888217.html)
with USB-C.
I can flash, everything is running and in the menuconfig i prepared it for OV2640 support.
But I get:
I (0) cpu_start: App cpu up.
I (446) heap_init: Initializing. RAM available for dynamic allocation:
I (452) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (458) heap_init: At 3FFB91D0 len 00026E30 (155 KiB): DRAM
I (465) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (471) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (477) heap_init: At 40095858 len 0000A7A8 (41 KiB): IRAM
I (484) cpu_start: Pro cpu start user code
I (502) spi_flash: detected chip: gd
I (502) spi_flash: flash io: dio
I (502) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (552) I2S: DMA Malloc info, datalen=blocksize=256, dma_buf_count=8
I (552) I2S: PLL_D2: Req RATE: 39062, real rate: 39062.000, BITS: 16, CLKM: 16, BCK: 8, MCLK: 10000000.000, SCLK: 1249984.000000, diva: 64, divb: 0
I (562) camera_xclk: PIN_CTRL before:3ff,39062
I (572) camera_xclk: PIN_CTRL after:7fff
E (4582) camera_demo: Camera probe failed with error 0x20001
Do yyou have any idea to get it to work with that USB integrated? Thanks!!!!

More information:
I (360) esp_image: segment 5: paddr=0x000b3d2c vaddr=0x40080400 size=0x19fc0 (106432) load
I (429) boot: Loaded app from partition at offset 0x10000
I (429) boot: Disabling RNG early entropy source...
I (429) psram: This chip is ESP32-D0WD
I (435) spiram: Found 64MBit SPI RAM device
I (438) spiram: SPI RAM mode: flash 40m sram 40m
I (444) spiram: PSRAM initialized, cache is in low/high (2-core) mode.
I (451) cpu_start: Pro cpu up.
I (454) cpu_start: Application information:
I (459) cpu_start: Project name:     esp32-cam-demo
I (465) cpu_start: App version:      0d87564-dirty
I (470) cpu_start: Compile time:     Dec  4 2019 22:13:55
I (476) cpu_start: ELF file SHA256:  e698264323feb2e0...
I (482) cpu_start: ESP-IDF:          v4.1-dev-1086-g93a8603c5
I (489) cpu_start: Starting app cpu, entry point is 0x40081448

Note README.md
Note:
If log debug come out "Camera probe failed with error 0x20001",please check whehter the camera connect to Board or check the pin Num.

@seblee 强 厉害 赞 真棒

@tobearlabs absoultely yes,I make sure the demo can work.Please check your camera or pin num.

@donny681 Thanks for your reply:
My nums are, given by the supplier:
D2 -> IO32
D3 -> IO35
D4 -> IO34
D5 -> IO5
D6 -> IO39
D7 -> IO18
D8 -> IO36
D9 -> IO19
in the pin configuration in "make menuconfig" I added all the values starting in your config with D0 with my D2...up to your D7 (which used my D9 so 19).
I set all the other values regarding to my table...still the ame error with my OV2460.
Any ideas?

This is the output with the right NUMS:
E (1477) ledc: requested frequency and duty resolution can not be achieved, try reducing freq_hz or duty_resolution. div_param=12
E (1487) camera_xclk: ledc_timer_config failed, rc=ffffffff
E (5507) camera_demo: Camera probe failed with error 0x20001


add xsrf-token to headers if there is xsrf-token cookie

many app framework have this xsrf token protected for post/put/patch/delete action, like Laravel,
Now angularjs will automatically set the X-XSRF-TOKEN based on XSRF-TOKEN cookie value, so I created this patch that jQuery-File-Upload can also have this header set on each request,
It's a extremely simple solution, I home you can have this in official codes.
Thanks

Thanks for your contribution, @steve3d
However, there's absolutely no need to include the code snippet you added inside of this library.
Simply add it into a new file and include it in your HTML documents.

sorry, but I don't think include this in other scripts will make this easy,
xsrf-token will change every 900 seconds or less, laravel will set the new token value in cookie whenever it changes, so I can not set this header in some fixed documents or scripts, it must be refreshed on every request,
So is there another way to intercept the _beforeSend event?

ok, got it.

Yes, for changing XSRF tokens, you will need to set this either in your response handlers, or in a handler before each request.
However this also doesn't need to be part of this library, since you could for e.g. make use of https://api.jquery.com/ajaxSend/
In any case, you will need the token for other requests than just file upload requests, so adding this here only will not be sufficient.

If there's really no other way for you to implement this, please have a look at the available callback options:
https://github.com/blueimp/jQuery-File-Upload/wiki/Options#callback-options

just tried with event fileuploadsend, and fileuploadstart, in both event , there is no way to get the jqXHR object, and use $.ajaxSetup({ headers: ...}) in those event will have no effect,
I'm using angularjs, the event system in angular can not make sure these callbacks are called before the actual request, so it seems there is really no way to add this header with angularjs' event system.

also tried this
        $( document ).ajaxSend(function() {
            $.ajaxSetup({ headers: {'X-XSRF-TOKEN': $cookies.get('XSRF-TOKEN')} });
        });

still not working

In the fileuploadsend callback, the second argument is the options object that is handed over to $.ajax. You can override any ajax option there, e.g.:
$('#fileupload').bind('fileuploadsend', function (e, data) {
  data.headers['X-XSRF-TOKEN'] = 'BANANA'
})

I still recommend you to make use of $.ajaxSend. However you don't call $.ajaxSetup in there, but make use of the jqxhr argument passed to the handler function, e.g.:
$(document).ajaxSend(function(event, jqxhr, settings) {
  jqxhr.setRequestHeader('X-XSRF-TOKEN', 'BANANA')
})


Incorporate kogito-tooling-go

Related PRs:
https://github.com/kiegroup/kogito-tooling/pull/615
https://github.com/kiegroup/kogito-tooling-go/pull/22
I'm also including a new Workflow to publish @kogito-tooling/jitexecutor-native, with native distributions of JIT Executor for Windows, macOS, and Linux.

⚠
DO NOT SQUASH
⚠

@jomarko Thanks for the review! Updated the PR with some fixes.

Added Go minimum version
Fixed URLs
Fixed packages to install on Fedora


set tsx=on in GRUB_CMDLINE_LINUX starting with RHEL 8.3 (Intel platform onl)

to revert the default Intel TSX being deactivated for certain CPUs from RHEL 8.3 onward, see Red Hat bug https://bugzilla.redhat.com/show_bug.cgi?id=1828642

The source for this will likely be SAP note 2777782.


[Feature] Support PointRCNN in MMDet3D

Motivation
Support PointRCNN in MMDet3D.

@xiliu8006 Thank you for implementing PointRCNN!
Is it alright to ask a question about the implementation here?
The paper states (p.6, Sec. 4.1 Implementation Details, The training scheme)

The two stage sub-networks of PointRCNN are trained separately.

From reading the implementation config and code, it looks like both the stage 1 (Bottom-up 3D Proposal Generation) and stage 2 (Canonical 3D Box Refinement) sub-networks are trained simultaneously with the same schedule and training pipeline.
Could you confirm if I'm missing something, or if separate sequential training is found to be unnecessary?

PS can confirm that I managed to reproduce the performance on KITTI reported in the paper on my system by just running the PR code.
Single RTX 3090 experiment
Batch size: 8x1 = 8 samples
LR: 0.001

Comparison with PointRCNN paper results (Moderate 'car' on validation set)

|    [AP] |  Easy | Moderate |  Hard |
--------------------------------------
| MMDet3D | 89.31 | 78.86    | 78.55 |
| Paper   | 88.88 | 78.63    | 77.38 |
--------------------------------------

@xiliu8006 Thank you for implementing PointRCNN!
Is it alright to ask a question about the implementation here?
The paper states (p.6, Sec. 4.1 Implementation Details, The training scheme)

The two stage sub-networks of PointRCNN are trained separately.

From reading the implementation config and code, it looks like both the stage 1 (Bottom-up 3D Proposal Generation) and stage 2 (Canonical 3D Box Refinement) sub-networks are trained simultaneously with the same schedule and training pipeline.
Could you confirm if I'm missing something, or if separate sequential training is found to be unnecessary?
PS can confirm that I managed to reproduce the performance on KITTI reported in the paper on my system by just running the PR code.
Single RTX 3090 experiment
Batch size: 8x1 = 8 samples
LR: 0.001

Comparison with PointRCNN paper results (Moderate 'car' on validation set)

|    [AP] |  Easy | Moderate |  Hard |
--------------------------------------
| MMDet3D | 89.31 | 78.86    | 78.55 |
| Paper   | 88.88 | 78.63    | 77.38 |
--------------------------------------

it is unnecessary to separate the training steps! we reimplement PointRCNN following this codebase. This codebase is made by the author of PointRCNN.


Version issue: scikit-learn >= 1.1 requires python>=3.8

Description
Can't use slideflow>=1.3.0 on python 3.7 since scikit-learn >= 1.1 requires python>=3.8. Installation info states that slideflow works on python 3.7 .
To Reproduce
Steps to reproduce the behavior:

Install python 3.7 .
Try installing slideflow using pip.

Expected behavior

Sucessful installation of slideflow on python 3.7 .
Environment:

Slideflow Version (e.g., 1.0): 1.3.0
OS (e.g., Ubuntu): Ubuntu
How you installed Slideflow (pip, source): pip
Python version: 3.7
Any other relevant information: Kaggle environment (as of 2022/10/20)

Additional context

Kaggle is a very popular environment for machine learning. It seems there currently is no way of updating python version on a Kaggle environment: https://www.kaggle.com/questions-and-answers/210493. As such, I ask that slideflow be compatible to python 3.7 .

Thanks for opening this issue - we somewhat recently increased the version requirement of scikit-learn to >= 1.1, but I didn't realize that it causes an incompatibility with python 3.7. I'll work on a solution that retains python 3.7 compatibility and update here when it's finished.

I appreciate that, thank you.

All tests have passed with scikit-learn == 1.0.2 on Python 3.7, so I've removed the >= 1.1 requirement. The scikit-learn >= 1.1 requirement was added during development of 1.3.0, but final released version did not include features that requires 1.1. This change will be included in Slideflow 1.3.3, which should be released in the next week or so.
With that said - I haven't included Kaggle environments in my testing approach yet, so there may be other issues you encounter. The big issue I imagine will be getting Libvips configured. I'll see if I can get a testing pipeline set up for Kaggle in the next month or so. Let me know if you encounter any other issues in the meantime.

Alright. I had no problem with libvips using apt. I also installed openslide-tools, python3-openslide and libcudnn8.
Using pip I had to update tensorflow-io to 0.26.0 and install versioneer if building from source (perhaps these could be included in the requirements?).
The big difference in workflow is tile extraction. It seems libvips need write permission and kaggle input directory, which contains slides, is read-only. Because the working directory has write permissions but only 20GB, to extract slides, you must iterate through the slides copying one to the working directory, extracting tfrecords and deleting it. tfrecords themselves can also leave little space, so you may need to upload them to kaggle and use them in the input directory.

Slideflow has ways of avoiding TFRecords entirely (use the argument P.train(..., from_wsi=True) during training), but I'd like to do some additional testing to see if any other workaround are needed to get Kaggle environments working smoothly. I will open a separate issue and we can discuss there.


No device

I would like to use my sonoff devices in automation. However to allow that I need to know the device for the action.
In the configuration-> devices sonoff device is NOT shown.
How can I then create an automation for eg switching on a TH16 at sun set? The switch from the TH16 is shown in the switches card on lovelace.
regards

Duplicate #83


tour: use print() in sections on interfaces

Context: https://tour.golang.org/methods/15
https://play.golang.org/p/ofPUaxb9sL
I was thinking that interfaces were somehow the same as types due to the way they're both displayed when using fmt.Println() and the fact that you can interact with the two in very similar ways. In my head, they were both just tuples of concrete values and types.
Then I got to the part about Type Assertions and realized they were actually quite different, but it didn't become clear to me until I used print(i) to display an interfaces' value and compared it to another variable. This may be a naive thing to get stuck on but I thought it would be a good place to use print() instead of fmt.Println() for the examples given. The raw output gave me a much clearer way of thinking about the different types being used.

Suggesting the use of print/println in the tour is a bad idea. They shouldn't be used, they're in the language for bootstrapping/debugging reasons.
Also what you saw when you started using print on interfaces is actually already explained in the tour, at tour.golang.org/methods/11, where it says:

Under the covers, interface values can be thought of as a tuple of a value and a concrete type:
(value, type)

this should already make quite clear that interfaces and types are different things.

I believe this is WAI, closing here.


Unknown Server error (400) when running ruby script.rb

When I run ruby scan.rb I get:
/usr/local/rvm/gems/ruby-2.3.0/gems/uirusu-1.0.2/lib/uirusu.rb:73:in `parse_response': Unknown Server error. (400) (RuntimeError)
        from /usr/local/rvm/gems/ruby-2.3.0/gems/uirusu-1.0.2/lib/uirusu.rb:48:in `query_api'
        from /usr/local/rvm/gems/ruby-2.3.0/gems/uirusu-1.0.2/lib/uirusu/vturl.rb:61:in `query_report'
        from scan.rb:6:in `<main>'

My code is as follows:
require 'uirusu'

urls = "url1.com\nurl2.com\url3.com\url4.com[,...urln.com\n]" # I'm using multiple URLs; VirusTotal exemplifies in their Python script that you can append \n between URLs to query multiple entries
API_KEY = "not_for_you"

results = Uirusu::VTUrl.query_report(API_KEY, urls)
result  = Uirusu::VTResult.new(urls, results)
if result != nil then print result.to_stdout else puts "Sorry, there was an error." end

Why would I get this error? Have you encountered this before?

Does it work with 1 hostname?

It does work with just one hostname. Maybe that should be a future feature, to work with multiple URLs.

I'll take a look at it.

I fixed a few bugs and multiple URLs can be submitted via scan_urls, I haven't updated VTurl.query_report yet, but it is easy to customize to support, just looping the result from the query to get the multi scan IDs then querying each of those or bulking those. Going to go ahead and close this. As I am moving the repo to my personal github.


Add test for #2515

Hello
Add tests for https://github.com/rspec/rspec-core/pull/2515
I'm not sure about the test title.

I'm not that familiar with this code or how this would happen in practice ("parent and child have same file" seems pretty suggestive though), but this looks pretty safe. Worst case we should be coding defensively against find not finding anything.

thank you!


how can I get the dataset in this project?

Hello, I'm really intersted in this project, but I can't find the dataset. Can you help me?

Hi, thanks for your interest.
It seems the Sunnybrook database web page has changed, it seems is possible to get the data from here. I will fix the link on the README.
https://www.cardiacatlas.org/studies/sunnybrook-cardiac-data/

I have got the dataset from your link，but I found that the format of this dataset was different from your’s．eg．It did not contain the Sunnybrook Cardiac MR Database ContoursPart%s(1, 2, 3) or challenge_%s(training, online, validation) files. So I don't know how to map the contours to images.
the new dataset's images file are looked like this:
Can you share your dataset  with me? Appreciate your generous.
------------------ 原始邮件 ------------------
发件人:                                                                                "fperdigon/LVNet"<EMAIL_ADDRESS>发送时间: 2021年3月9日(星期二) 凌晨2:27
收件人<EMAIL_ADDRESS>抄送: "海浪一方"<2397585063<EMAIL_ADDRESS>主题: Re: [fperdigon/LVNet] how can I get the dataset in this project? (#1)
Hi, thanks for your interest.
It seems the Sunnybrook database web page has changed, it seems is possible to get the data from here. I will fix the link on the README.
https://www.cardiacatlas.org/studies/sunnybrook-cardiac-data/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Skip test in internal build.

The test injects the user space instrumentation lib. For unknown reasons
this sometimes works; that's why I missed it in the previous PR.

I don't understand. Why you are just adding commented lines?

These comments are "magic" in the sense that they instruct copybara to insert the code in the comment when the import is done.


deprecation warnings

When I compile go-ceph I get:
# github.com/ceph/go-ceph/rados
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_objects_list_close’:
cgo-gcc-prolog:348:2: warning: ‘rados_objects_list_close’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3750:21: note: declared here
 CEPH_RADOS_API void rados_objects_list_close(
                     ^
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_objects_list_get_pg_hash_position’:
cgo-gcc-prolog:364:2: warning: ‘rados_objects_list_get_pg_hash_position’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3741:25: note: declared here
 CEPH_RADOS_API uint32_t rados_objects_list_get_pg_hash_position(
                         ^
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_objects_list_next’:
cgo-gcc-prolog:384:2: warning: ‘rados_objects_list_next’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3746:20: note: declared here
 CEPH_RADOS_API int rados_objects_list_next(
                    ^
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_objects_list_open’:
cgo-gcc-prolog:403:2: warning: ‘rados_objects_list_open’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3738:20: note: declared here
 CEPH_RADOS_API int rados_objects_list_open(
                    ^
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_objects_list_seek’:
cgo-gcc-prolog:423:2: warning: ‘rados_objects_list_seek’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3743:25: note: declared here
 CEPH_RADOS_API uint32_t rados_objects_list_seek(
                         ^
cgo-gcc-prolog: In function ‘_cgo_c03cef46a91f_Cfunc_rados_read_op_omap_get_vals’:
cgo-gcc-prolog:497:2: warning: ‘rados_read_op_omap_get_vals’ is deprecated [-Wdeprecated-declarations]
In file included from ../../../ceph/go-ceph/rados/ioctx.go:6:0:
/usr/include/rados/librados.h:3271:21: note: declared here
 CEPH_RADOS_API void rados_read_op_omap_get_vals(rados_read_op_t read_op,

My librados is from luminous

Um, actually these are not just warnings, the list objects code doesn't work anymore on luminous (it returns rados: Operation not supported). These have to be replaced by the new versions that include the namespace.

Thank you for reporting this. I knew something like this would come along eventually. I guess we'll need to think about how to handle this general Go+C compat issue now.
My initial thought is to just now cut releases of Go and match them up with the span of Ceph versions that is compatible. I'm open to suggestions.
Another option would be to have the Go code introspect the librados version and adapt dynamically, but I'm not sure what limitations that has since presumably Go would have to link against the symbols even if they aren't being used in a newer version.

Cutting the go versions seems reasonable. I personally have had bad experiences trying to do dynamic adaption with cgo stuff because all the C symbols are in the same namespace so you cannot actually build and link against multiple versions of librados. Detecting at build time and only linking against one is no more useful than just using the correct go branch and is significantly more complex and error prone.

Thanks for the input. Also I misread your second comment above. It seems like you are saying that the methods are not just deprecated, they're not working either? :/

Yes, as of luminous those methods have been removed in librados. They just return not supported :(

This is still affecting me BTW

The rados_objects_list_* functions can harmlessly be changed to their namespace-aware versions rados_nobjects_list_* (which exist in jewel), passing nil as the namespace. It won't magically make go-ceph support namespaces, but will at least squash that warning.
The rados_read_op_omap_get_vals function needs to be replaced by rados_read_op_omap_get_vals2, which takes an additional flag-pointer to indicate if there are more values to fetch. This function doesn't exist in the jewel API, so it's going to need some conditional compilation.

Is the code in @hangzws's fork going to be merged back here? Given that this is completely broken for luminous now, I am going to PR the nobjects functions first. It appears the deprecated omap function is still implemented so apart from the warning it will still work.

Hello everyone, this problem can't compile ceph_exporter, how should I solve it?

Hello everyone, this problem can't compile ceph_exporter, how should I solve it?

Hello everyone, this problem can't compile ceph_exporter, how should I solve it?

Met the same issue, have you solved?

Hello everyone, this problem can't compile ceph_exporter, how should I solve it?

@lnsyyj   Met the same issue, have you solved?

I have not solved it, no, but the warning does not cause any problems. You can ignore it

I'm speculating a bit here as I haven't tried any local experimentation yet, but it might make sense to move deprecated (or new) functions into files using go build constraints and provide tags to the build based on the ceph release codename (for example).

That might be possible, but it's a bit tricky because the problem is actually in C

This is something worth investigating. It's been a while but I remember there being some complications because the code in question is in C