Laravel 5.8 update breaks third-party composer libraries

Laravel Version: 5.8.5
PHP Version: 7.2.12
Database Driver & Version: n/a

Description:
When upgrading our applications to use Laravel v5.8 there is a major breaking change in the way environment variables are being handled which renders useless the majority of third-party composer libraries that use PHP's getenv function.
This change is documented here: https://laravel.com/docs/5.8/upgrade which is great, and which we are using to upgrade our systems. Unfortunately this guide does not cover the actual change that was made in the underlying way the Dotenv library is being used. For whatever reason the adapter that was being used to populate the environment that getenv uses is no longer being loaded. This is a huge breaking change that effects an entire ecosystem of third-party libraries when being used with Laravel.
There was an issue raised here which was recently closed: https://github.com/laravel/framework/issues/27913 In that issue, the response was to use the Laravel env helper instead of PHP's getenv function. This is good advice for Laravel applications where you are in control of all code but for third-party composer libraries this is not possible. There are literally thousands of libraries out there that have no idea they are being used with Laravel and use getenv internally.
What this ultimately means is that it's impossible for us to upgrade any of our applications to Laravel 5.8 while this is broken.
Steps To Reproduce:
Use any code (including any third-party composer library) that uses getenv to load an environment variable from the .env file. It always returns false.

getenv & putenv work just fine for any environment variable outside Laravel's .env environment. I've just tested this on a fresh 5.8 app. If you have an integration which relies on integrating with Laravel you should use a custom config file and use the env helper.

Use any code (including any third-party composer library) that uses getenv to load an environment variable from the .env file. It always returns false.

This indeed won't work anymore but that's documented in the upgrade guide. In this situation you should replace getenv with the env helper.

getenv & putenv work just fine for any environment variable outside Laravel's .env environment.

Yes, I understand that but we are using Laravel here.

I've just tested this on a fresh 5.8 app. If you have an integration which relies on integrating with Laravel you should use a custom config file and use the env helper.

This would make sense if we are the ones who were responsible for the code. This code is in a third-party library that uses getenv throughout. We have no access to the code other than changing the vendor'ed dependency loaded through composer.

This indeed won't work anymore but that's documented in the upgrade guide. In this situation you should replace getenv with the env helper.

How can I do this if it's a third-party library? Also you are implying the library uses Laravel and has access to the helper. We are using an AWS library which is framework agnostic and will never be able to use the Laravel env helper. This also applies to hundreds, if not, thousands of framework agnostic PHP libraries that use getenv.
Do you understand that the Laravel env helper function is not available outside of the Laravel framework? Developers rely on the getenv function instead when writing a composer library that requires ENV variables.
Why has this been closed? This is a huge breaking change that affects lots of PHP libraries which essentially can't be used with Laravel now.

You should ask the maintainer to update their library to support 5.8. Which library are we talking about exactly?
Can you provide a practical code example which demonstrate how this breaks your app? Please provide third party libraries in the exact version you're using them.

Amazon AWS SDK v3.90.4

Another related issue: https://github.com/laravel/framework/issues/27828

Please link to the library in question.

I can't understand why there has been no deprecation notices regarding this or notices about such a huge change in functionality on a minor revision. This is disappointing coming from you guys.

Please read our upgrade guide before upgrading.

Please link to the library in question.

Are you being serious? https://github.com/aws/aws-sdk-php
Here's another we're having the same problem with:
https://github.com/braintree/braintree_php

Please read our upgrade guide before upgrading.

We were following it to upgrade our services. Nowhere does it say that the Laravel .env file is no longer populating the getenv PHP function and that any third-party libraries that rely on it will fail.
Maybe I can't see it, so can you point that part out please?

Here's a few more libraries we've identified as affected:
https://github.com/FriendsOfPHP/PHP-CS-Fixer
https://github.com/googleapis/google-api-php-client-services
https://github.com/vyuldashev/laravel-queue-rabbitmq

Are you being serious? https://github.com/aws/aws-sdk-php

Yes, I was. I wanted to make sure we were talking about the same one. This library doesn't integrate with Laravel. There's a separate one which does but it's updated to be used with 5.8 and makes use of the env helper in its config file: https://github.com/aws/aws-sdk-php-laravel

Here's another we're having the same problem with: https://github.com/braintree/braintree_php

This library doesn't directly integrates with Laravel either.

Maybe I can't see it, so can you point that part out please?

The docs here: https://laravel.com/docs/5.8/upgrade#environment-variable-parsing link to https://github.com/vlucas/phpdotenv/blob/master/UPGRADING.md where at the bottom it details how we implemented the library according to their upgrade guide in a way not to call functions that aren't tread-safe (like getenv). But I can agree with you that this isn't super obvious. I'll send in a PR to the docs to make this more explicit.

@nomad-software I really think you're missing the point of what's being discussed here. If you are using the .env file you should always use the env helper and not the getenv function. If you set env variables in any other way (CLI, php config) you can use the getenv function.

So we are only allowed to use libraries officially supported by Laravel now? You do realise that packagist contains are little more than that right?

I really think you're missing the point of what's being discussed here.

No you are missing the point. You are breaking developer's environments for no good reason (on a minor release I may add) and have not informed anyone of such a big change.
Why would you introduce a nice elegant way of handling environment variables (the .env file) that developers have been using for years then all of a sudden cripple its use and now advocate defining env vars in multiple different places? This is a huge step backward for no advantage. There is litterally no upside here. You've even broken your own server: https://github.com/laravel/framework/issues/27828

I have to agree with @nomad-software here , you are essentially saying that from now on all packages will need to have a version made to work with Laravel. I am also not seeing understanding why you are fighting a "FIX" that is literally adding two words to a method.

I've tried being patient and helping to figuring out your problem but because of the negativity going on here and the remarks I've decided that this is where this conversation ends.
If you genuinely feel that there's a problem you are free to open up a new issue where we can discuss this in a calm and peaceful manner and I'll be happy to help you figure everything out.

What is the fix? I'm not familiar with DotEnv 3.0.

I've unlocked this again in an hopeful attempt we can perhaps resolve this peacefully.

As a reminder to all unaware users, Laravel does not follow semver, so 5.7 --> 5.8 is a major update, not a minor update.
https://laravel.com/docs/5.8/releases#versioning-scheme

We fixed it by altering the createDotenv  function in the LoadEnvironmentVariables class to look like the below.
protected function createDotenv($app)
    {
        return Dotenv::create(
            $app->environmentPath(),
            $app->environmentFile(),
            new DotenvFactory([new EnvConstAdapter, new ServerConstAdapter, new PutenvAdapter])
        );
    }

Essentially just adding the PutenvAdapter object back into the   DotenvFactory  constructor this then tells DotEnv to push the env variables into the php enviroment by using putenv().

I think Laravel developers know in general that Laravel does not follow semver. However this change would make the life of developers 'harder' by default, and make an upgrade path more complicated than it should be.

@AndyMac2508 like said above this would re-introduce the issue about tread-safety as detailed in the phpdotenv upgrade guide: https://github.com/vlucas/phpdotenv/blob/master/UPGRADING.md
But at this point we're thinking about maybe adding the PutenvAdapter just for the sake of it since this seems to be affecting much more than the original PR considered.
For reference, here's the original PR and a detailed explanation of why these changes were made: https://github.com/laravel/framework/pull/27462

Don't disagree, but OP kept referring to this as a minor update, so I wanted to make sure everyone was on the same page.

Gotcha, I don't mind adding the PutenvAdapter back in. Sorry, I'm on vacation and just woke up to this thread.

I've released 5.8.6 with the PutEnvAdapter in place by default to be more similar to 5.7 behavior.

You should never rely on getenv being set by Laravel .env files, because if you cache the config file, the .env isn't loaded in production anymore.

@taylorotwell Thankyou.

You should never rely on getenv being set by Laravel .env files, because if you cache the config file, the .env isn't loaded in production anymore.

Yes but for dev, staging and test environments it's a god send.

As a for future reference, I think @driesvints should get more support when it comes to tickets like this. It's clear that he didn't understand the issue and closed the issue out of frustration that people were continuing to disagree with him.

You should never rely on getenv being set by Laravel .env files, because if you cache the config file, the .env isn't loaded in production anymore.

Isn't the entire point of .env is to overwrite system env variables for development access?
We shouldn't rely on a .env within production, but .env is extremely useful for local development overrides. Let's assume it's a Docker container: system env will be set within docker, and .env is meant to override those values on a server-by-server instance.

I asked for this a while back, Graeme gave his reasons why it was changed in the first place.
See #27814

You should never rely on getenv being set by Laravel .env files, because if you cache the config file, the .env isn't loaded in production anymore.

Isn't the entire point of .env is to overwrite system env variables for development access?

This whole issue is brought up time and time again. I really don't understand why it's so difficult for developers to understand some basic things when it comes to the env:

NEVER use getenv, env, etc outside of your configs. EVER.
php artisan cache:config - always in production, and sometimes required in development when you do cross-application communication

That's it. If developers actually did that, they would never run into any env problems. When you cache your config, dotenv isn't even loaded. It just pulls your env values straight from a simple compiled php file.

@garygreen that's all well and fine in Laravel but illuminate/support is a generic package that can be used outside of Laravel. Let's take Lumen as an example, you can't config cache there.

@Kieran-Brown That's true. I'm being simple minded, didn't realise third parties rely heavily on envs being defined in getenv etc, which I guess makes sense as it's framework agnostic.

@AndyMac2508 like said above this would re-introduce the issue about tread-safety as detailed in the phpdotenv upgrade guide: https://github.com/vlucas/phpdotenv/blob/master/UPGRADING.md

Which is more important: not breaking support for thousands of third-party libraries or being able to parallelize reading an .env file across multiple processors? :man_facepalming:

This tweet explains why the change was made perfectly:

Third party libraries are using the wrong function. They should instead use the superglobals.

Which is more important: not breaking support for thousands of third-party libraries or being able to parallelize reading an .env file across multiple processors? 🤦♂

Third party libraries are just calling the wrong thing. They should be updated to use the correct method of getting env variables safely. This is unrelated to Laraavel.

I've been going over the comments here a few times since the issue was opened again and want to say a few things. First of all, I'd like to apologies to you, @nomad-software for being too quick to judge and close and lock this issue. I now see how this would affect other libraries much better and it took a while before that sank in. I'm sorry for the way I handled this and I hope to be better at judging these situations in the future. Thank you for reporting this.
I do however, still want to voice my concern about the adding of the PutenvAdapter. I do agree with @GrahamCampbell and others that this isn't the most ideal situation and that the reasons stated in this thread as well as in the newly opened PR (https://github.com/laravel/framework/pull/27961) and the original issue [here[(https://github.com/vlucas/phpdotenv/issues/76) are valid and would be addressed by this.
However, I also acknowledge that this simply affects too much libraries atm. So maybe it's better if we provide an upgrade path for this and do this in a next version while letting people know up front a long time in advance.

Or maybe we could somehow make it configurable for now? to allow both new and old behaviour depending on preference? As I understand both ways are useful at the moment and for sure we don't have the power to force thousands of PHP libraries to switch to "correct" way

I love Laravel. I love being a user of Laravel. The people who make Laravel are incredible, generous human beings. A buddy of mine sent this thread to me because he knows I have a lot of projects that depend on Laravel—I don't think he's doing any Laravel work himself, so it was super cool and generous of him to alert me to it. It shocks me zero that this issue was found, reported, discussed (passionately) and ultimately fixed. Huge props to everyone—restored a bit of faith in humanity today.

@driesvints

I've been going over the comments here a few times since the issue was opened again and want to say a few things. First of all, I'd like to apologies to you, @nomad-software for being too quick to judge and close and lock this issue.

Fair enough, apology accepted. Please, please, please try and understand the problem before closing tickets, many big open source projects do this and it drives me absolutely nuts.

I do however, still want to voice my concern about the adding of the PutenvAdapter. I do agree with @GrahamCampbell and others that this isn't the most ideal situation and that the reasons stated in this thread as well as in the newly opened PR (#27961) and the original issue here are valid and would be addressed by this.

If this is a major problem we need to take this up with the PHP devs instead of not using it. If that avenue of attack has been exhausted then, by all means, revisit this decision. If the decision is made again to remove it, please make it configurable. Then make sure everyone is aware it's going to happen and what the ramifications are. Write a blog post, spam reddit, post on the official Laravel twitter, etc. but please let people know.
Thanks anyway. We have got it sorted. :+1:

@GrahamCampbell

Third party libraries are using the wrong function. They should instead use the superglobals.

If it's in the standard library, it's going to get used. Frameworks need to deal with it.

Third party libraries are using the wrong function. They should instead use the superglobals.

Maybe you're the guy to correct the millions of PHP developers then?

Is the answer as simple as a config item to let people enable/disable threadsafe env vars?

Third party libraries are using the wrong function. They should instead use the superglobals.

My two cents: I checked php.net - no mention about 1) not being thread-safe and 2) recommendations of using superglobals over PHP's own functions.
As long time PHP developer, this is honestly the first time I've ever heard of using a superglobal over php's built-in functions.

Talking about thread safety on a non-threadding language. This must be a php-first haha

I think that @driesvints shouldn't be the person who's handling ticket support anymore. This thread is a good example of rudeness and not understanding the issues. Yes, he apologized, but the way it started... I'm a huge fan and user of Laravel framework but people like him are making my blood boil and stay away from the framework until there's a guy who's gentle and listening.

On the contrary, he does an incredible job here and should be commended for his work across the Laravel ecosystem. I'm thankful that he continues the thankless job of open source pr/issue maintenance.

I agree, he's probably a good developer and person but what I've been reading is simply not acceptable. Laravel is an amazing thing that deserves amazing people.

I have to vaguely agree with @deniamnet - however it’s not a problem isolated to him and shouldn’t be called out.
Historically everybody involved in Laravel is typically very abrupt and quick to shut people down, if you look at the typical attitude towards issues on github - there is generally a negative attitude, I’ve seen countless tickets by the whole team discarding people’s problems who do not subscribe to their beliefs. I’m not saying their reasons are not valid - however often unless they see it as a problem, they just won’t care - despite their business model being around providing a service to the public, it is why there is a sense of “Laravel elite” amongst the community where close friends share support between each other, and anybody else gets shut down immediately.
There’s countless tickets you can go through and see examples of this, the last 2 I can think of being on the Nova issues with the lack of breadcrumbs and being dismissed saying “use the back button” without having the knowledge or taking the time to understand the problems with back buttons, in fact the British government has whole research saying why you should provide your own. Another example is relationships in nova when attaching the same model twice causes a JavaScript error, but the issue was just closed because they couldn’t be bothered to explore the problem.
What will be a testament to the above, will be the fact the above will NOT get addressed, and it will be closed down almost immediately proving the point 😂

Here is another data point: due to the popularity, the number of "low effort" issues and PR is insane at times:

People not able to read the basic template and create a issue without any information
People creating bug report issues which are actually support requests best asked somewhere else (even though there are clear links / hints)
People creating PRs with breaking change left and right and no tests until nudged, etc.

Ah well, and sometimes you simply misjudge an issue. Human error. It's natural. Happens all the time. To everyone.
Somewhere, forgot where, Dries was called out. I was shocked about the unfair treatment. IMHO he does a great at polite job, all the times. But still, like everyone else, he's just a human. Luckily 😄

IMHO he does a great at polite job, all the times - mfn

Apparently not, from reading the above comments and related issues. The issue was closed without proper thought and @nomad-software was constantly told he was wrong. I know it must be frustrating that lots of people (including myself) sometimes open issues that are incorrectly formatted or a number of other reasons, which ultimately waste time, but that's no excuse to shut someone down without properly hearing them out.
This isn't a poke at anyone, I'm just trying to say that people need to be understanding and to not be quick to jump to conclusions.
I'm glad this is getting resolved though, thanks to all the contributors!

Dotenvy is a package I wrote that generates server environment variables from your .env files: https://github.com/nystudio107/dotenvy

I have liberated Laravel 5.7's env() from the dustbin of the git repo and made it its own package. What's more, using some real composer hacks, I have ensured that it will always be autoloaded first, overriding whatever Laravel's current env() does.
Benefits:

Works with any package, even non-Laravel ones (it was my secondary reason)
You no longer have to fear Laravel just going one day "Oops! We're not going to read from the environment anymore! Too bad!" on a non-major release.

https://github.com/phpexpertsinc/Laravel57-env-polyfill
To install: composer require phpexperts/laravel-env-polyfill.

I'll say it again for the people in the back....
5.7 --> 5.8 IS A MAJOR RELEASE


Edit embed config to allow overriding the label on the search box

Overview
Edit embed config to allow overriding the label on the search box
Depend on  model updates in #1533
Describe the solution you'd like

Update API to allow passing text_search_label when updating EmbedConfig

Normalize empty string to null

Update embedded map UI to add a "Text search label"
- Include a subsection for 'Custom search text label' under the Fields section of the embed config
- Info text should describe the use of the custom search text and that it's available when fields are marked searchable
- Disable the custom search label when no fields are searchable
- Set the default value to the default search text
- onBlur, if the text search label is blank, replace it with the default text
- If at any time no fields are marked searchable, the custom search box is should be reset to the default text and disabled
Update search sidebar UI to show custom label which is set on the EmbedConfig

@jwalgran Just for clarification - do we need to update the placeholder for the input here accordingly?

Yes. We do want to change the placeholder text.


geoid.exe: small spelling error at command line reference for --direction option: “Ellispoid" [sic]  (v 1.2.6, 06 SEPT)

ISSUE TYPE: Minor typo
URGENCY:  NOT urgent
Description
** geoid.exe**  command line referencing contains a typo at option --direction: “Ellispoid” [sic]
Steps to reproduce
COMMANDS (command line):

geoid --help

Expected behaviour / Recommendation
RECOMMEND:

Correct the text of the command line reference
Note: DynAdjust Users Guide does NOT contain this typo.

** Operating Environment**
Windows 10 Enterprise
DynAdjust v1.2.6
DynAdjust Users Guide.PDF (‘Sept 2022’) gather 06/SEPT/2022 from fork rogerfraser/DynAdjust

This issue is updated 09/09 to be a general catch-all for typographical errors in  the text.
(Original issue referred to a single error only]

geoid.exe  command line referencing contains a typo at option --direction: “Ellispoid” [sic]
geoid --help  command will demonstrate this error.
Note: DynAdjust Users Guide does NOT contain this typo.
Operating Environment
Windows 10 Enterprise
DynAdjust v1.2.6
DynAdjust Users Guide.PDF (‘Sept 2022’) gather 06/SEPT/2022 from fork rogerfraser/DynAdjust

Section 3.3.1 Reference frame / Default Reference frame.
The subsection title should only have the first word capitalised: i.e. Default Reference frame =>  Default reference frame
I'm channeling my 'inner-german' today ;-)

Thanks @jhaasdyk-au. These changes have been made on my copies and will appear in the next release.


MTDSA-509 bug invalid date

@rakeshavasarala , this address the actual bug (not returning an error when validation fails). I think we also have a bigger question about how to deal with the validations errors that get returned to JsError branch inwithJsonBody. Basically, they don't get codes, so we must use a generic code. Theres is a mechanism for translating errors https://www.playframework.com/documentation/2.5.x/ScalaI18N. These errors are separate from the ones that validate for things like making sure commencementDate is in the past.

👍


Implement the CUI

Implements the below command:

Login(boot)
Logout(Quit)
Type SOQL
Show execute result
Set format

Actually connect to SFDC and confirm operation.
We plan to correct test classes, logs and comments.

Remaining tasks

CommandProcessorTest
DialogProcessorTest
ProcessorFactoryTest

Commited command and dialog mode.


feat: Download icon is (only) visible (or enabled) when the batch is complete

Description

References

#0000

Codecov Report

Merging #1071 (ffdfaa4) into main (3c01078) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1071   +/-   ##
=======================================
  Coverage   69.17%   69.17%
=======================================
  Files          18       18
  Lines         266      266
  Branches       25       25
=======================================
  Hits          184      184
  Misses         72       72
  Partials       10       10

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


26 benchmarking  with benchmarks

The current issue with failing benchmarks is that the branch needs to be up-to-date


Small margin column variant

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fixes #
Changelog:

Added small-margin column variant

Test URLs:

Original: https://www.sunstar.com/about/history

Before: https://main--sunstar--hlxsites.hlx.live/about/history

After: https://no-margin-columns--sunstar--hlxsites.hlx.live/about/history

[ ] New Blocks introduced in this PR
If yes, please provide details below

Block Name
Documentation

For e.g. cards
doc-link

[ ] New variations introduced in this PR

Variation Name
Documentation

For e.g. cards (grid)
doc-link

@ehrro I fixed that, I somehow missed the flex-direction change, thanks for pointing it out
The purpose of this variant is for stuff like this where the default margin for the columns would push the text below it way too low, so we basically want it to be "inline" (not sure it's the best term but I hope it makes sens) with the rest of the paragraphs
With small-margin

Without small-margin

@jindaliiita also has some use cases for this

Actually I was looking for that variant for one of the use cases. Thanks It's all good now.


PMID:17248775 proline, tyrosine, glutamate, tryptophan auxotrophy

thats all....

also add "auxotrophic" to "auxotrophy" parent as synonym.

growth auxotrophic for proline FYPO:0005875
growth auxotrophic for tyrosine FYPO:0005876
growth auxotrophic for glutamate FYPO:0005877
growth auxotrophic for tryptophan FYPO:0005878
edit file: e73dcd46b4e928057ad850069eacfd62e2b9db82
release: 718d910492a2fa5fc1c780279990ef57ebb480a6


Week 3 - Tasks List

Docker Deployment

[x] #24
[x] #25

Update README.md

[x] #26

Comparing Technology

[ ] Study the tech & write some description in https://github.com/UBC-MDS/dash-tableau-shiny_comparison @miyer26

Peer Review

[x] Open an Issue in https://github.com/UBC-MDS/DSCI532-peer-review @miyer26
[x] Persona @miyer26
[x] Frontend / layout @MacyChan
[x] Backend @PhilsChan
[x] Documentation @MacyChan
[ ] Post-review improvement idea on own project @plevchen

Here is the write-up for the tech study. Please feel free to add on to it before we do the final submission. Thanks!
Short:
There are multiple ways to deploy a Shiny app on the web. These include deployment to the cloud through Shinyapps.io, open source virtual private cloud through the Shiny Servers and commercially in a premises/virtual private cloud using RStudio Connect. Shinyapps.io is a flexible and easy to use option to deploy apps as quickly as a few minutes that is hosted in servers operated by R Studio1. Hence it is suitable for hosting prototypes, individual projects but also more  complex projects. It can be used for free to host upto 5 apps, and if there is a need for more, there are tiered paid versions. The open source Shiny server has the advantage that it can run behind private firewalls, can be used to host multiple applications using the same server, each with a unique URL. Again this version is free. The recommended option for commercial deployment is through RStudio Connect, which is a standalone product that supports both Python and R , and can host applications, dashboards and even Jupyter Notebooks3. The servers it is deployed on can be controlled by the organization, whether it is on some server behind a firewall or a VPC. It also includes a whole host of other features including integration with RStudio, easy scale up and web application support.
Long:
In general, there are two main ways to host Shiny apps on the web: through servers hosted by RStudio or on personal servers.
Shinyapps.io is a flexible and easy to use cloud based option to deploy apps in  as quickly as a few minutes. It is a software as service package that is hosted in servers operated by R Studio1. It is suitable for hosting prototypes, individual projects and also more complex projects due to its ease of use.  It can be used for free to host upto 5 apps, and if there is a need for more, there are tiered paid versions. Scalability is also very easy as this method is cloud based. However the disadvantage is that there is no firewall protection for the app, so commercial or company specific apps may not be suited for this type of deployment (1).
The open source Shiny Server package has the advantage that it can run behind private firewalls and can be used to host multiple applications using the same server, each with a unique URL2. The professional version of Shiny Server offers additional features such as access restrictions for the applications, SSL encryption and performance management. Shiny Server open source is free, whereas the professional version is paid (2,3).
The recommended option for commercial deployment is through RStudio Connect, which is a standalone product that supports both Python and R , and can host applications, dashboards and even Jupyter Notebooks3. It is also integrated with Git and provides a user interface. The servers it is deployed on can be controlled by the organization, whether it is on some server behind a firewall or a VPC. It also includes a whole host of other features including integration with RStudio, easy scale up and web application support. It is designed to be used by many users within an organization. It is however only available as a paid version (4).
References:
https://shiny.rstudio.com/deploy/
https://www.rstudio.com/products/shiny/download-server/
https://docs.rstudio.com/shiny-server/#introduction
https://www.rstudio.com/assets/img/RStudio-Connect-12July2021.pdf

Some issue to be fixed

[ ]   Should place it as favicon.ico in a folder called assets in the root of the project, currently it is not at the root. @plevchen
[ ]  PR merge the above at here @miyer26

Comment for dash-tableau-shiny_comparison will be posted separately

Regarding the favicon.ico I have tried placing the image to assets/ at root folder, but the icon does not render as before. I guess our current location makes more sense.

Did some final edits and PRed
https://github.com/UBC-MDS/dash-tableau-shiny_comparison/pull/33
Seems I don’t have access to merge


Fix typos

Motivation
There is no dedicated test requirement document specified, so the full requirements should include the requirements for test.
This PR also fixes a couple of typos on the way.
Checklist

[x] Have you checked our Contributing document?
[x] Have you ensured the PR description clearly describes the problem and solutions?
[x] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
[x] If this PR fixes an issue, is the first line of the PR description fix #XXX where XXX is the issue number?

Update
The requirement issue is already fixed in main, this PR only adds typo fixes

It's so odd that the CI isn't finding the DANDI_API_KEY secret: https://github.com/catalystneuro/nwb-conversion-tools/runs/7342649698?check_suite_focus=true
I suppose it's because this is submitted from @JuliaSprenger's fork, but the actions appear to be going through the main repo...

Wow, hmm... OK I had figured that it was possible to skip the entire test class that way, but apparently not...
@JuliaSprenger So sorry, but can you try skipping just that one function instead https://github.com/catalystneuro/nwb-conversion-tools/blob/main/tests/test_internals/test_tools.py#L209?

Hi @CodyCBakerPhD Now only the issue of secret tokens not being available in PR triggered runs remains. It's a security feature to prevent secrets to be accessible by non-project administrators. A safe way on how to still have the key available is to use the pull_request_target trigger in combination with a manual label of the PR by an administrator, e.g. like I did it here: https://github.com/INT-NIT/DigLabTools/blob/main/.github/workflows/run_tests.yml

A safe way on how to still have the key available is to use the pull_request_target trigger in combination with a manual label of the PR by an administrator

Looks like that is indeed working! Thanks!


Multiple meanings of DID (and Plurality)

The book overall and the Identity chapter in particular have the challenge that Plurality and DID are both used to refer to similar phenomena, both very different from the way they are used in the book, namely people with many fully distinct selves.  I am open to suggestions of how to most thoughtfully and consistent with other parts of the book address this issue in the text.  See issue #56 for more discussion here and I would welcome a constructive PR from @mg138 on this topic.

Plurality would be the preferred wording, as DID is highly medical and specifically a diagnosis. (Think "transgender" v.s. "gender identity disorder")
Could you link the relevant sections, or is it just Identity? We admit, although the book seems very interesting, we haven't gotten the mindset to read it yet, we have slight dyslexia and that made reading a pain for us.

DID is not something this book is helping introduce....it is very widely used for Decentralized Identity.  It will be hard to understand the context without reading the full Identity chapter.

If @Identitywoman has anything to add here, I'd value her perspective and textual intervention to note this.

It would be great to save the acronym "DID" for Decentralized Identifier a particular actual standard that was recently approved by the W3C.  This is how the folks who gather in the communities working on the community commonly use this acronym.
The community says "decentralized identity" if it means the idea- which is mostly about a philosophy and idea that says people have identity from multiple places, they should be the locust of control or pivot point of information moving between contexts.  Decentralized identity is often used to describe a a high level an architecture that includes the standard Verifiable Credentials (blobs of signed data from sources that may or may not be authoritative).   It is a term liked by governments adopting the tech - because it doesn't have the word "sovereign" in it.  Self-Sovereign Identity is another term in use in the market that basically refers to the same architecture - but with a little bit more of an "edge" of dislike towards any centralized source issuing anything to anyone - however accepts that it might.
The term Plurality as Glen and Audrey are defining in this book is bigger then any particular standard  or even terminology nomenclature in around decentrlaized technology it is rooted in a discussion of human nature as we understand it now with new nuroscience and coming out of existing sociology and other disciplines.
There is overlap but I don't see them as the same.
Do decentralized identity and SSI and the particular technical protocols DIDs and VCs play a role in enabling Plurality - totally - this is why I've contributed to the work..
Then I see this thread in another issue also talked about Dissociative Identity Disorder and the term Plurality.  I don't have opinions on this discussion.
I think the fact Plurality can mean many things sort of helps make the point.  :)

@Identitywoman I think you may have missed the key point.  @msparkles is concerned that DID is so closely associated with the medical condition that its use to refer to a decentralized identifier may be harmful.

Okay so, thinking about this for a while now, here are our final thoughts:

it's not a suitable mindset to approach this problem thinking "well names are just like this, just the way it is." Just look at the name "Meta," it used to have a meaning, a specific, hard to explain one, but now people are gonna be like "metadata is that like the Metaverse?" It doesn't help that the meaning of "meta" is hard to describe/little known, a lot of people don't actually know what metadata means. We're talking normies, not techies, because eventually those terms are gonna reach normies- most people have heard of a HTML or HTTP.
yes, in the end, it doesn't matter, because a highly stigmatized and little understood minority will most likely stay that way regardless of if we try to avoid confusion or not. but the world never was about doing things right, just doing things in the right direction.
DID- we don't necessarily have a problem with the acronym. it is widely different in contexts- as Dissociative Identity Disorder is highly medical and usually unused. but "plurality" here seems to manifest orders of meaning beyond a technical usage, apparently philosophical, and to put plural people's context into perspective- we're already switching from the name "multiplicity" to "plurality" and struggling in doing so.

Madeleine, I agree with your general point and that your concerns deserve more engagement than I feel Kaliya gave.  That said, the more I study it the less I believe that Plurality is a plausibly problematic conflict here.  The term Plurality has been used I roughly the way we mean it for decades, dating at least to Hannah Arendt's work, and is also extensively used in political science.  Some collusion is inevitable therefore.  The additional collision caused by our usage, which I believe is even less likely to cause stigma-inducing confusion given it's a normative positive idea in our context, seems minimal. Further we have shifted from Plurality to this symbol ⿻, which I do not believe has such a collision, partly to address these ambiguities.  If you believe this issue needs to be discussed further, I'd appreciate if you would engage with the substance of the book enough to appreciate the relevant context and try to persuade the community, in that context, that a change makes sense.

Research Lead, Plural Technology Collaboratory (https://aka.ms/plural), Research Special Projects

Outside of Microsoft I am Founder of RadicalxChange (https://radicalxchange.org) and Founder and Chair of the Plurality Institute (https://plurality.institute)

From: Madeline Sparkles @.>
Sent: Tuesday, February 27, 2024 7:18:25 PM
To: pluralitybook/plurality @.>
Cc: Glen Weyl @.>; Comment @.>
Subject: Re: [pluralitybook/plurality] Multiple meanings of DID (and Plurality) (Issue #87)
Okay so, thinking about this for a while now, here are our final thoughts:

it's not a suitable mindset to approach this problem thinking "well names are just like this, just the way it is." Just look at the name "Meta," it used to have a meaning, a specific, hard to explain one, but now people are gonna be like "metadata is that like the Metaverse?" It doesn't help that the meaning of "meta" is hard to describe/little known, a lot of people don't actually know what metadata means. We're talking normies, not techies, because eventually those terms are gonna reach normies- most people have heard of a HTML or HTTP.
yes, in the end, it doesn't matter, because a highly stigmatized and little understood minority will most likely stay that way regardless of if we try to avoid confusion or not. but the world never was about doing things right, just doing things in the right direction.
DID- we don't necessarily have a problem with the acronym. it is widely different in contexts- as Dissociative Identity Disorder is highly medical and usually unused. but "plurality" here seems to manifest orders of meaning beyond a technical usage, apparently philosophical, and to put plural people's context into perspective- we're already switching from the name "multiplicity" to "plurality" and struggling in doing so.

—
Reply to this email directly, view it on GitHubhttps://github.com/pluralitybook/plurality/issues/87#issuecomment-1967954347, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABIRKSAFBH5KDUWQ3MPPB6DYVZZVDAVCNFSM6AAAAAA4EWBOZGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRXHE2TIMZUG4.
You are receiving this because you commented.

Very well.
On a side note, we really need to get around to checking it out :sweat:


UI can only be used on local machine.

Installed with docker-compose.  Runs very well on local machine (using local AI).
If I try to access from other machine on the LAN, I get the UI, everything looks normal.
But when I ask a question, the question simply gets posted in the page instead of generating answer.
In the docker-compose the address of Ollama is : http://<IP_ADDRESS>:11434, which, again, works very well if I access from the browser at local machine with http://<IP_ADDRESS>:3000 and, in the UI, choosing "local".
But from other machine if I access http://<IP_ADDRESS>:3000, I get the behavior described above. i.e.: when I ask a question, the question simply gets posted in the page but no answer is generated.
My docker-compose
services:
  backend:
    build:
      context: .
      dockerfile: ./src/backend/Dockerfile
    restart: always
    ports:
      - "8000:8000"
    environment:
      - OLLAMA_HOST=${OLLAMA_HOST:-http://<IP_ADDRESS>:11434}
#      - TAVILY_API_KEY=${TAVILY_API_KEY}
#      - BING_API_KEY=${BING_API_KEY}
#      - SERPER_API_KEY=${SERPER_API_KEY}
#      - OPENAI_API_KEY=${OPENAI_API_KEY}
#      - GROQ_API_KEY=${GROQ_API_KEY}
      - ENABLE_LOCAL_MODELS=${ENABLE_LOCAL_MODELS:-True}
      - SEARCH_PROVIDER=${SEARCH_PROVIDER:-tavily}
      - SEARXNG_BASE_URL=${SEARXNG_BASE_URL:-http://host.docker.internal:8080}
#      - REDIS_URL=${REDIS_URL}
    develop:
      watch:
        - action: sync
          path: ./src/backend
          target: /workspace/src/backend
    extra_hosts:
      - "host.docker.internal:host-gateway"
  frontend:
    depends_on:
      - backend
    build:
      context: .
      dockerfile: ./src/frontend/Dockerfile
    restart: always
    environment:
      - NEXT_PUBLIC_API_URL=${NEXT_PUBLIC_API_URL:-http://localhost:8000}
      - NEXT_PUBLIC_LOCAL_MODE_ENABLED=${NEXT_PUBLIC_LOCAL_MODE_ENABLED:-true}
    ports:
      - "3000:3000"
    develop:
      watch:
        - action: sync
          path: ./src/frontend
          target: /app
          ignore:
            - node_modules/

  searxng:
    container_name: searxng
    image: docker.io/searxng/searxng:latest
    restart: unless-stopped
    networks:
      - searxng
    ports:
      - "8080:8080"
    volumes:
      - ./searxng:/etc/searxng:rw
    environment:
      - SEARXNG_BASE_URL=https://${SEARXNG_BASE_URL:-localhost}/

networks:
  searxng:

Change http://localhost:8000 to the private IP of the machine you are running.

Great!  That works fine for me.  Many thanks!!!
On 2024-06-14 15:01, Alok Saboo 'notifications at github.com' wrote:

This email was sent to @.*** from
@.***
Click here
https://app.addy.io/deactivate/022cc3db-6fd8-4177-8ee9-e7c2e50b7a0f?signature=c71858ffacf8d3e9be43c2aa0cb6d980030174651ae2fda2b9e769c21abf2a88
to deactivate this alias
Change |http://localhost:8000| to the private IP of the machine you
are running.
—
Reply to this email directly, view it on GitHub
https://github.com/rashadphz/farfalle/issues/51#issuecomment-2168817490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHRKLJ327TYLKVEHJVTZSK3ZHNR2TAVCNFSM6AAAAABJK4WWDGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRYHAYTONBZGA.
You are receiving this because you authored the thread.Message ID:
@.***>


Integrate code directly into a script from add-ins

it would be better to stay directly in RStudio instead of opening the app in a web browser. A button to copy the produced code should be available and (even better) the code could be integrated directly into a script (add-ins provided by questionr for factor recoding are a good example of that spirit)

Instead of direct copy into script field, this app implements "copy to clipboard button."


HTTPStatus.UNAUTHORIZED

So I'm trying to use this library on JellyFin 10.8.13. I went to Administration -> API Keys and created a new key.
I'm attempting to get a list of items and so here's my code, obviously with BASE_URL and TOKEN being set to valid values.
from jellyfin_api_client import AuthenticatedClient
from jellyfin_api_client.api.items import get_items
import pprint

BASE_URL="BASE_URL"
TOKEN="TOKEN"

with AuthenticatedClient(base_url=BASE_URL, token=TOKEN) as client:
        pprint.pp(client)
        data = get_items.sync_detailed(client=client)
        pprint.pp(data)

I'm receiving this result
AuthenticatedClient(raise_on_unexpected_status=False, _base_url='BASE_URL', _cookies={}, _headers={'Authorization': 'Bearer TOKEN'}, _timeout=None, _verify_ssl=True, _follow_redirects=False, _httpx_args={}, _client=<httpx.Client object at 0x1058e6cf0>, _async_client=None, token='TOKEN', prefix='Bearer', auth_header_name='Authorization')
Response(status_code=<HTTPStatus.UNAUTHORIZED: 401>, content=b'', headers=Headers({'alt-svc': 'h3=":443"; ma=2592000', 'content-length': '0', 'date': 'Sun, 07 Apr 2024 18:02:56 GMT', 'referrer-policy': 'no-referrer', 'server': 'Kestrel', 'strict-transport-security': 'max-age=315360000; includeSubDomains; preload', 'x-content-type-options': 'nosniff', 'x-frame-options': 'allow-from BASE_URL', 'x-response-time-ms': '1', 'x-robots-tag': 'none', 'x-xss-protection': '1; mode=block'}), parsed=None)

When looking at the jellyfin logs
[11:09:12] [DBG] [67] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was not authenticated.
[11:09:12] [DBG] [67] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was not authenticated.
[11:09:12] [INF] [67] Jellyfin.Api.Auth.CustomAuthenticationHandler: AuthenticationScheme: CustomAuthentication was challenged

Is there a different api key location I need to generate? or am I using the AuthenticatedClient incorrectly?
Thank you very much!

Hello,
This is expected behaviour, but it's also my fault for not documenting the project so much.
The expected token is not an API key, but a session token handed by the server.
Here is a snippet extracted from Marmalade's code showing how that token is obtained :
from http import HTTPStatus

from jellyfin_api_client.api.user import authenticate_user_by_name
from jellyfin_api_client.errors import UnexpectedStatus
from jellyfin_api_client.models.authenticate_user_by_name import AuthenticateUserByName
from jellyfin_api_client.models.authentication_result import AuthenticationResult
from src.jellyfin import JellyfinClient, make_device_id

def main(username: str, password: str, base_url: str) -> AuthenticationResult:
    device_id = make_device_id()
    client = JellyfinClient(base_url=base_url, device_id=device_id)
    response = authenticate_user_by_name.sync_detailed(
        client=client,
        json_body=AuthenticateUserByName(username=username, pw=password),
    )
    if response.status_code == HTTPStatus.OK:
        return response.parsed
    if response.status_code == HTTPStatus.UNAUTHORIZED:
        raise ValueError("Invalid username or password")
    raise UnexpectedStatus(response.status_code, response.content)

def on_success(result: AuthenticationResult) -> None:
    print(f"Authenticated {result.user.name}")
    print(f"Access token: {result.access_token}")

Don't hesitate to ask me if you have any more questions.
I suggest poking around Marmalade's codebase to get more examples of how to use that library, but beware, it's experimental and I've not touched it in a while.


[SPARK-45768][SQL][PYTHON] Make faulthandler a runtime configuration for Python execution in SQL

What changes were proposed in this pull request?
This PR proposes to make faulthandler as a runtime configuration so we can turn on and off during runtime.
Why are the changes needed?
faulthandler feature within PySpark is really useful especially to debug an errors that regular Python interpreter cannot catch out of the box such as a segmentation fault errors, see also https://github.com/apache/spark/pull/43600. It would be very useful to convert this as a runtime configuration without restarting the shell.
Does this PR introduce any user-facing change?
Yes, users can now set spark.sql.execution.pyspark.udf.faulthandler.enabled during runtime to enable faulthandler feature.
How was this patch tested?
Unittest added
Was this patch authored or co-authored using generative AI tooling?
No.

I'm testing them.

Build: https://github.com/HyukjinKwon/spark/actions/runs/6729423885/job/18290311390

cc @ueshin

Thanks all, addressed!

All related tests passed.
Merged to master.


name 'smi_out' is not defined - fast_stable_diffusion notebook

Info Here:

Happens for me too

Commit that causes the issue: https://github.com/TheLastBen/fast-stable-diffusion/commit/6a44c8159d8c795a32f960b1d5bc618a93708b74

Commit that causes the issue: 6a44c81

Thanks for pointing this, it´s not hard to change on Colab as temporal fix.

will fix it in a bit

Getting an error on this line now

did you run the cell before ?

yeah i did.. although i've tried again by restarting the runtime, and got it to run, thanks.


EntryPointNotFoundException on FaceRecognizer.Create*FaceRecognizer()

I am using the latest from NuGet (<IP_ADDRESS>60622). This line:
OpenCvSharp.Face.FaceRecognizer f = OpenCvSharp.Face.FaceRecognizer.CreateEigenFaceRecognizer();
results in:
System.EntryPointNotFoundException was unhandled
HResult=-2146233053
Message=Unable to find an entry point named 'face_createEigenFaceRecognizer' in DLL 'OpenCvSharpExtern'.
Source=OpenCvSharp
TypeName=""
StackTrace:
at OpenCvSharp.NativeMethods.face_createEigenFaceRecognizer(Int32 numComponents, Double threshold)
at OpenCvSharp.Face.FaceRecognizer.CreateEigenFaceRecognizer(Int32 numComponents, Double threshold)
at FaceCounterTester.Program.Main(String[] args) in C:\Users\jgauthie\Documents\Visual Studio 2015\Projects\FaceCounter\FaceCounterTester\Program.cs:line 63
at System.AppDomain._nExecuteAssembly(RuntimeAssembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException:
All .dll files appear to be in the right place - I am trusting that NuGet has done this properly. I see OpenCVSharpExtern.dll in bin\debug\dll\x86 & x64. I also tried copying it to bin\debug.
Other face recognizers result in the same error.
My project is in .net 4.5.2 using visual studio 2015. All other functions I've tried thus far have worked perfectly - face detection, image conversion, and more.
Help? Thanks!

It's the same as issue #180

You're correct.


Speed up HLL presentation by 100x

This changes the use of math.pow(2.0,-mj) when computing the estimates in SparseHLL and DenseHLL to 1.0 / (1 << mj).
To benchmark the difference this makes, I first had to change the HLLPresentBenchmark to clone the HLL instances before asking for their approximateSize, otherwise the estimate gets cached as a lazy val and the benchmarks are meaningless.
Having done that, you can see a dramatic difference. Because I'm impatient I have so far only run this with a single set of parameters, where it led to a 40x speedup.
Before:
[info] Benchmark                            (bits)  (max)  (numHLL)   Mode  Cnt    Score   Error  Units
[info] HLLPresentBenchmark.timeBatchCreate      12  10000        10  thrpt  200  141.569 ± 5.010  ops/s

After:
[info] Benchmark                            (bits)  (max)  (numHLL)   Mode  Cnt     Score    Error  Units
[info] HLLPresentBenchmark.timeBatchCreate      12  10000        10  thrpt  200  5984.351 ± 60.770  ops/s

This is failing on the HLL downsize test (which passes on my machine). Is this a known-flaky test, or is this maybe pointing to some actual issue?

The two builds actually failed on two different tests, one of them was that, the min hasher one too. Both are alas flaky tests. Restarted both

LGTM though, merge when green

I just tested with @kamalmarhubi using a lookup table as well as (1/ (1 << mj)), and the lookup table is twice as fast, which seems worthwhile to me. (val lut: Array[Double] = (0 until 256).map(x => 1.0 / (1 << x)).toArray). Shouldn't block this though!

This breaks when mj > 30.  If we're not concerned about that, can we at least add an assertion so we fail instead of giving the wrong result?
scala> 1.0 / (1 << 31)
res4: Double = -4.6566128730773926E-10

scala> 1.0 / (1 << 32)
res5: Double = 1.0

@jnievelt in principle it can be up to 124, though that's exceedingly unlikely. Still, @jvns's suggestion of a lookup table would take care of this and is faster anyway, so I'll revise to take that approach.

Ok, yeah, with a lookup table (pushed) it's over 100x as fast:
[info] Benchmark                            (bits)  (max)  (numHLL)   Mode  Cnt      Score     Error  Units
[info] HLLPresentBenchmark.timeBatchCreate      12  10000        10  thrpt  200  14693.743 ± 206.868  ops/s

If/when we clean this up to fix the name, can will also make the table private[this]?

Could you not replace all instances of Math.pow(2, X) with X << 1 across the entire code base?

@johnynek it's used in the HLL subclasses but defined in the HyperLogLog object, so private[this] won't work. We could do private[algebird]?

yeah, private[algebird] is good, once its classed as an implementation detail outside the project so we can change it later

@zg not, for two reasons:

math.pow allows non-integral exponents (which we sometimes use), which we can't use with 1 << X
per my comment above it would only work if we're sure that X <= 30.  And per the results here, we'd probably be better off using a lookup in that case anyway

Do we have an ETA on when a version of algebird with this optimization will be released?

@eigenvariable Latest algebird was released only 2-3 days ago? Check out the releases section for more info.


Relationship between maxTrialNum and population_size

Short summary about the issue/question:
What is the difference between maxTrialNum and population_size in the Evolution tuner?
Assuming: maxTrialNum = 5 and population_size = 10
Is there an initial population of 10 available for each of the 5 experiments?

Hello @martsalz.
The maxTrialNum in config means 'maxTrialNum specifies the max number of trial jobs created by NNI, including succeeded and failed jobs.'  Usually, we will set a large number, like 1000. You could reference here
And the population_size means the initial size of the population(trial num) in evolution tuner. For example, if population_size is 5, means the evolution tuner will randomly generate 5 trials as its initial population, then evolve from this population by mutation.
If you set maxTrialNum = 5 and population_size = 10, I guess it won't work.
Thank you~ Feel free to ask me anything.

Thanks.
At which point is an experiment completed? Is there a maximum number of generations per experiment that can be set?

Hello @martsalz.  The maxTrialNum is the max number of an experiment. So if the trial number exceeds the maxTrialNum, the experiment will be stopped.
Thank you.

At which point is an trial completed? Is there a maximum number of generations per trial that can be set? (for Evolution as tuner)

I am not sure I understand your question totally. But I try to answer it.
In nni, trial code is written by users. Which means you get params(or config) generated by tuner, and used in your trial code. Then return the metric(like acc) to tuner.
So the trial completed when finishing execute your  trial code.
"Is there a maximum number of generations per trial that can be set" --> For this question, if you want to ask how to set the number of mutation trial, I think you could set trialConcurrency in config.yml.  Which could specify the max num of trial trials run simultaneously.

Assume Evolution is selected as tuner and population_size is specified.
Models are trained -> individuals are selected from the population -> crossover / mutation -> insert into the population.
How often is this process performed?

@martsalz
maxTrialNum  means the max number of trial jobs created by NNI.
trialConcurrency means the max num of trial jobs run simultaneously.
The process of Naive Evolution Tuner:
Initial population -> models are trained -> new individuals are inserted  into the population -> individuals are selected from the population (random select 2 individuals from the population, the individual with better result can crossover and then it pops up)-> crossover / mutation -> generate parameter for model to train -> models are trained -> ... (loop)
NNI does mutation when it generates parameter from config so the frequency of this process is related to trialConcurrency. The source code of the mutation is here
The implementation is based on the paper Large-Scale Evolution of Image Classifiers.
Also, you can refer to the document of NNI for more details.


use of in memory file system

when we do office file conversion, I guess that there are disk I/O activities.
I think of using a in memory file system like(tmpfs) for following reasons:

better performance
no document will be stored on disk in any moment

Is this possible and how should I do it?
Thanks in advance.

Hello @Simplici
Indeed there is some I/O activities.
I guess it should be possible to use in memory file system - dunno how to though.

Docker and Podman can do tmpfs: https://docs.docker.com/storage/tmpfs/
I've got tons of SVGs, which are needed inside my FODTs. I'm mounting them on tmpfs.


Opened doors render differently depending on agent_dir

Opened doors change position depending on the direction the agent is facing.

open_doors.zip

Seems acceptable to me.

Sorry, the observations were stitched together in the wrong order so it may have been unclear, updated it above. Could you take another look at this?
In particular:

It's because doors are not directional objects. They occupy one grid cell, but they don't have an orientation per-se.


add FAQ about multiple monitor setup

Thanks for your contribution!
Related to: https://github.com/huan/docker-wechat/issues/28#issuecomment-595741652


320159: main part (work in progress)

@3rd-Eden This is basically a set of monkey-patch fixes to the regexes by doing some basic modifications to make them less prune to DoS attacks.
It fixes most of the issues (I hope), but is labelled as work in progress because it still breaks something. See attached lists and the code comments.
This is based on top of https://github.com/3rd-Eden/useragent/pull/138, but we can rebase it out of here (though that would require resolving conflicts).
Also /cc @davisjam.
We could try to finish fixing them in this PR, and then try to submit to uap-core first before merging this?
Hopefully, monkey patching won't be needed at all, but this branch is needed nevertheless, because we need to test those regexes.
Discussing in my private fork didn't work, hence opening it up here for feedback on the specific regex modifications and the approach.

So, any thoughts about the approach?

It looks like uap-core updated regexes and fixed at least some of the DoS issues.
This has to be reevaluated.
@3rd-Eden A re-sync with uap-core would be helpful, I guess. Combined with #137.

@ChALkeR Did you want to me to update the master branch with latest set of uap-core?

@3rd-Eden Yes, that would be good, I guess? That fixes at least some known EDA.
Do you want a PR for that? I assumed that it could be easier to just run that locally than review a PR, but I can definitely file a PR if you would like me to,

Just #137 is not effective and just uap-core update is not effective (I have testcases against both), but combined #137 and uap-core update might be effective -- I will try to review the regexes tomorrow.

FYI: as of May 19th, Snyk is classifying this lib as having a high severity vulnerability for this issue.
https://snyk.io/vuln/SNYK-JS-USERAGENT-174737


airflow image

Looks like puckel/docker-airflow is no longer avilable. Had to pull the image from https://hub.docker.com/r/apache/airflow

Looks like puckel/docker-airflow is no longer avilable. Had to pull the image from https://hub.docker.com/r/apache/airflow

Hi @kartikra , thanks for your message. Yes, this work was done some time ago and after it Airflow adds their own official image. I'll try to update the code here to use it.


Getting error ./node_modules/@zeit/dns-cached-resolve/lib/dns-resolve.js:6:0

I'm trying to use this package in my nextjs project. When importing import { getConfig } from '@bigcommerce/storefront-data-hooks/api' I'm getting a Module not found: Can't resolve 'dns'.
Is there any dependency that I need to install?

If so, can you share which version of npm,  yarn and node you are using?

I just experienced this issue as well. I tried both with npm (6.14.9) and yarn (1.22.10). node (14.15.3)

Can you show me the output of yarn list --pattern @vercel/fetch? It seems that this dependency is not installed

Hey all - I managed to track this issue down to a misunderstanding on my side. I saw this error if I had a error in the code. Specifically noticed it when trying to use some of the API operations client-side. If I moved them to server-side, it worked fine.

Cool! Thank you very much for letting us know 🙌


aptly web ui not showing any repos and snapshots

hi,
i installed the aptly web ui using nginx. The website is working but it doesn't show any existing snapshots or repos. I already have 3 repos and numbers of snapshots or it and even in serve state.
Am i having any issue here or is this how it works?

Definitely not normal, but without more informations I can not really understand what's going on. Best guess is the static server is working but not the reverse proxy to the API.
Are you sure aptly's API is running at all?

thanks for quick reply.
Ya, this is not as expected. My aptly is running, here is the ps status of it.
ubuntu   27421  0.0  0.1  42184 15972 ?        Sl   Apr05   0:12 /usr/bin/aptly api serve -no-lock -listen=:8088 -config=/home/ubuntu/.aptly.conf
ubuntu   27422  0.0  0.2  32672 17212 ?        Sl   Apr05   0:26 aptly serve -listen=:8080 -config=/home/ubuntu/.aptly.conf

I wonder I should be the right way to set reverse proxy in nginx.
I extracted the archieve as mentioned in documentation, and setup nginx with root folder pointing to
/home/ubuntu/.aptly/public
thanks.

hi,
i again served the aptly in different port addition to above.
aptly api serve -listen=:8085 -no-lock
and in nginx proxy to 8085 port
proxy_pass http://<IP_ADDRESS>:8085
and it worked. I can see all the repos and snapshots created by aptly under user ubuntu.
But web ui is all messed up might be due to large number of repos and snapshots. May be UI wasn't designed to handle large number of data.
please let me know where did i get things wrong.
thanks

Can you provide me a screenshot? It's totally possible that the UI breaks on  larger number of repos. I admit I've never tested it past ~3/4 repos...

I have attached two images, compared with chrome on left and firefox on right. Safari was total mess. :)

beside, the upload function seems not working in firefox. In chrome i can't even find it.

OK it looks like a bad layout for larger repo counts. I'll look into it when I have some spare time.

cool, thanks.


Simulated states from hidden Markov model should be sampled from {1, 2,...,N} (rather than 0,1,2,...,N-1)

Summary + Description:
For the new hidden Markov model functionality, hmm_latent_rng() uses the foward-filtering backward-sampling algorithm to simulate from the joint posterior distribution of the underlying state process, implemented in the generated quantities block below. Given an N-state HMM, the underlying states should be drawn from {1, 2, ..., N} at each point in time, rather than {0, 1, ..., N-1} as is implemented now. This facilitates using the states as indices when generating draws from the posterior predictive distribution of the observations.
Reproducible Steps:
Stan code for an HMM using the functionality in CmdStan.
data {
int<lower = 0> N;  // number of states
int<lower = 1> T;  // number of observations
real y[T];
}
parameters {
simplex[N] theta[N];  // N x N tp
ordered[N] mu;  // state-dependent parameters
vector<lower=0>[N] sigma;
simplex[N] init_dist;
}
transformed parameters {
matrix[N, T] log_omega;
matrix[N, N] Gamma;
// build log_omega
for (t in 1:T)
for (n in 1:N) log_omega[n, t] = normal_lpdf(y[t] | mu[n], sigma[n]);
// build Gamma
for (n in 1:N) Gamma[n, ] = theta[n]';
}
model {
// priors
mu ~ normal(2, 3);
sigma ~ normal(0.5, 1);
target += hmm_marginal(log_omega, Gamma, init_dist);
}
generated quantities{
matrix[N, T] states_prob = hmm_hidden_state_prob(log_omega, Gamma, init_dist);
int states_pred[T] = hmm_latent_rng(log_omega, Gamma, init_dist);
vector[T] y_pred;
for (i in 1:T)
y_pred[i] = normal_rng(mu[states_pred[i] + 1], sigma[states_pred[i] + 1]);
}
Current Output:
Currently, my defined states_pred object in generated quantities stores a sequence of underlying states that could include 0. For instance, for a 3-state HMM, we could have the underlying posterior draw:
states_pred = c(0, 0, 1, 1, 2, 0, 1, 2)
However, this means that I need to add a 1 if I would like to use the predicted states as indices, as shown below:
for (i in 1:T)      y_pred[i] = normal_rng(mu[states_pred[i] + 1], sigma[states_pred[i] + 1]);
Desired Output:
It would be great to not have to add a 1, so rather than the code above, I could write:
for (i in 1:T)      y_pred[i] = normal_rng(mu[states_pred[i] ], sigma[states_pred[i]]);
Current Version:
v2.24.0

Thanks for reporting.  I marked it as a bug and assigned @charlesm93 who wrote most of the code.  Should be easy to fix for the next release.  We should also make sure the documentation matches.

Posting this issue under stan-dev/math#2112.

Closed by https://github.com/stan-dev/math/pull/2113


Moving v1beta1 kubectl examples to v1beta3

Follow up of https://github.com/GoogleCloudPlatform/kubernetes/pull/6377
Am running e2e to verify that all is fine.

@bgrant0607

Just one comment.
Let me know when e2e passes.

LGTM

e2e passed!!


Latest version support

Does this support producers and consumers fully in kafka <IP_ADDRESS>? I'm frequently getting errors Error committing offsets: Kafka::UnknownMemberId

Can you post some logs that could give more insight into what's happening?
0.10 is supposed to be backwards compatible with 0.9, which is the version we're currently testing against.

This was the issue related to timeout which kicked the worker out of group after some idle time. Got is solved by changing configuration.

@vivekmarakana I've just released v0.5.0.beta1 with support for Kafka 0.10. Would you be willing to run this in production for some time and see if everything works as expected?


Remove fs from package.json - it's a built in module

Change-type: patch

@balena-ci I self-certify!


mat-form-field: Outline appearance not compatible with Universal/SSR

Bug, feature request, or proposal:
Bug
What is the expected behavior?
Outlined form fields shouldn't hinder rendering in Universal applications.
What is the current behavior?
Server middleware fails with this error:
TypeError: this._connectionContainerRef.nativeElement.getBoundingClientRect is not a function
    at MatFormField.updateOutlineGap (d:\Workspace\a-typical-blog\node_modules\@angular\material\bundles\material-form-field.umd.js:701:112)
    at d:\Workspace\a-typical-blog\node_modules\@angular\material\bundles\material-form-field.umd.js:459:19

What are the steps to reproduce?
Placing a <mat-form-field appearance="outline"> element with a label should trigger the error since it doesn't seem like getBoundingClientRect() is supported on the server platform.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Currently on Angular 6.0.0-rc.1 and Angular Material 6.0.0-rc.0
Is there anything else we should know?
To get this far I had to work around angular/material2#10586 and angular/universal#844 before I could get SSR working consistently.

Closing since I think this was fixed by #10943.


Token22 Support

Support token22 transfers for all user actions

Not Included:

LM Token22 support

CI:

https://github.com/mrgnlabs/marginfi-v2/actions/runs/9065187888/job/24905202397?pr=208
https://github.com/mrgnlabs/marginfi-v2/actions/runs/9065187888/job/24905203870?pr=208

here's a note: the usdc_f bank in TestFixture::new was a made a token22 bank. I reverted that change in my most recent commit. So now there's a tokenkeg udsc bank and a token22 usdc bank, instead of two token22 usdc banks

Closed in favor of #208


Add api generation to modules

Hi, any plans to add a api generator for the modules manager?

Yes we have plan for that.
Please check out plan / features here.
http://laraadmin.com/features
Best Regards,

when did the api generation gonna be finish ?


ie9，列表页跳转到详情页时，先出现404再显示详情

?

您好，您的邮件我已收到

Having used several platforms to buy Bitcoin, I can confidently say that Paybis is one of the best. The combination of speed, security, ease of use, and low fees makes it a superior choice compared to many others https://paybis.com/blog/glossary/buy-wall/. What sets Paybis apart is its commitment to customer satisfaction and its transparent approach to fees and transactions. While other platforms might offer similar services, Paybis consistently delivers a better overall experience. Whether you’re a beginner or an experienced trader, Paybis provides a platform that is both accessible and reliable, which is why I keep coming back to it for my crypto purchases.

您好，您的邮件我已收到


Spice language

Add hello world program in the Spice language.

Thanks for contributing!!! If you're interested in programming languages, please check out my tiny Batch superset language: https://github.com/FreakC-Foundation/FreakC


feat: lint dockerfiles

Many times it is difficult to lint dockerfiles during a build or bake.
This adds a new CLI option --lint to build and bake that runs hadolint
on any dockerfiles.
--lint has three options: ignore, warn, and error.

ignore does not lint (default).
warn will warn about linting issues in the dockerfiles.
error will fail the build or bake on linting issues.

One other thought: right now, linter failures report as build failures in the API. I think conceptually that makes sense, but we should probably report whether --lint was used, with what options, in the initiator details, and should track whether the failures was in the lint or build phases, so that we can display that in the UI.

[x]  The More info: URL could use the new link thing from build summary to be clickable

Ok! Added in 9ad2d60

[x]  I wonder if we should separate out whether linting is enabled and which severity fails the build. Like maybe --lint should be a boolean flag, and if enabled linting happens and the build fails if any ERROR issues are found. I imagine that's the most common desired behavior. Then there could be some other flag that controls which severity fails the build, not sure what it should be called, maybe there's some prior art, but something like --lint-fail-on warning

Ok! --lint is now a bool and --lint-fail-on can be error (default), warn, info  or none.
1f39f39
Here is an  example failing on info.

One other thought: right now, linter failures report as build failures in the API. I think conceptually that makes sense, but we should probably report whether --lint was used, with what options, in the initiator details, and should track whether the failures was in the lint or build phases, so that we can display that in the UI.

Added in 8895f2c


feat: login with prime ng

Pull Request
Thank you for your contribution to the Bulwark. Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes #373  (issue)
Type of change

[ ] A new feature
[ ] A bug fix
[ ] Documentation only changes
[ ] Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] A code change that neither fixes a bug nor adds a feature
[ ] A code change that improves performance
[ ] Adding missing tests or correcting existing tests
[ ] Changes that affect the build system or external dependencies
[ ] Changes to our CI configuration files and scripts
[ ] Other changes that don't modify src or test files

Add description here

Checklist

[ ] My code follows the contributing guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

old layout:
desktop:

mobile

new layout:
desktop

mobile

Looks good, thank you for another contribution!


[stable/kafka-manager] configurable liveness and readiness probes

Signed-off-by: moody<EMAIL_ADDRESS>What this PR does / why we need it:
Make probes configurable
Which issue this PR fixes

fixes #16377

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

/assign @ssalaues

@giacomoguiulfo
@ssalaues

/ok-to-test

@agolomoodysaada It looks like the PR needs rebase off the master branch and bump the version again. After that it should be good to merge.

@ssalaues , thank you!
I made the changes as requested.

/lgtm


Suggestion Filter by Name/Entitys

Right now it spectates Docile Locust Bees and the Manticoils which isn't that good/usefull.
Also would recommend adding a hotkey to switch back to the player1 so when you click Mous1 you switch again to player2,3,4
Right now you can't got like Player1 -> Player2 -> Player3 -> Player2 -> Player1, like revert back like most other games do it (because Right Mousebutton is Vote Leave)

I plan on adding an option to disable passive enemies next update.
As for your other suggestion, did you mean you wanted a hotkey to immediately switch back to a player instead of having to click through all of the enemies?

Either a key that switches you to Player1 so when you left click it goes again from the beginning.
Or
Just make a toggle key with Indicator that you are no in "Spectator Mode: Player" or "Spectator Mode: Enemy" :o

Resolved as of v1.2


Fighting Fantasy

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is:  Fighting Fantasy    (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is:  Steve Jackson and Ian Livingstone (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: Faghting Fantasy (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at:    Fighting Fantasy
[x] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description
I have always  been a huge fan of Fighting Fantasy books by Steve Jackson and Ian Livingstone. Hope you enjoy this character sheet and may your games be fun!

Character Sheet Info Roll20 Internal Use only.

Hi! What is wrong with the sheet, please?


Change - qualify key names with the module name

This resolves warnings (in the puppetserver.log) to the effect of:
 WARN  [puppetserver] Puppet Module 'bacula': Value returned from data_hash function 'yaml_data', when using location '/etc/puppetlabs/code/environments/bacula/modules/bacula/data/common.yaml', must use keys qualified with the name of the module
 WARN  [puppetserver] Puppet Module 'bacula': Value returned from data_hash function 'yaml_data', when using location '/etc/puppetlabs/code/environments/bacula/modules/bacula/data/os/RedHat.yaml', must use keys qualified with the name of the module

This resolves the warnings I was seeing regarding the unqualified variables.  However, I still get the Error: Evaluation Error: Unknown variable: 'bacula::client::packages' so I cannot verify that this change does not introduce other issues.  Merge this at your own risk.

Thanks for the PR.  Fewer warnings sound good.

How does this look?  I totally missed that those class parms were commented out.  Apparently there's also a bug in syntax/puppet.vim as only the pound char was highlighted as a comment.  I put too much faith in the color.  ;-/

Cool!   Thanks for the contribution.  Voxpupli has an updated puppet.vim.


feat: global hot reload setting in cli

#670
If I got this correctly one more thing would be to add test.
I wanted to add test in start.test.mjs something like https://github.com/platformatic/platformatic/blob/e9f7daaf620ff10562eea9b10b443066e661138d/packages/db/test/cli/start.test.mjs#L246
But seems like this one is already failing ?
 FAIL  test/cli/start.test.mjs
 ✖ test unfinished

  test: start with hotreload disabled
  stack: |
    file://test/cli/start.test.mjs:246:1
  at:
    line: 246
    column: 1
    file: file://test/cli/start.test.mjs

Is no-hotreload.json correct since I can't find that
  "watch": {
    "hotReload": false
  }

is valid setting?

@salesh the current tests are OK for me (and for CI):

Which OS / node version are you using?

can you add a test for this feature?

Hey @mcollina @marcopiraccini, sorry for my late answer, I am at the moment on vacation and I didn't see mail until now. I will commit this test at Monday, I hope that's not issue..
@marcopiraccini my OS is Ubuntu 18 and Node is 18

sure no prob


Returning false from canDeactivate removes history entry (browser history back)

When navigating back by browser history and return false from canDeactivate, then history record is removed (replaced).
How to reproduce:

run skeleton-navigation application
Go to "Child Router" page
Go to "Github Users" page
Go to "Welcome" page
Change first name
Press browser back
In promt choose Cancel
Press browser back again
In promt choose Ok

Effect:
"Child Router" page is open instead of "Github Users"
Additional:
If you repeat 6-7 steps few times more, application will close without promt, since application history becomes empty.
Question:
Is any way to do not allow deactivate without loosing navigation history?
It will be logical, for example if I have "users" page, then go to user editing, edit something without saving changes, on browser back I'm asked if I want to leave without saving changes, I choose - no, then save changes, and press history back again. In such case I expect return back to "users" page instead of somewhere else where I was earlier.

I have workaround for this issue, but it seems dirty...
Idea is return redirect to previous page to avoid loosing navigation history.
How to apply:
in welcome.js
import router and redirect
import {Router, Redirect} from 'aurelia-router';
inject router
static inject(){     return [Router]; }
constructor(router){     this.router = router; }
in canDeactivate change
 return confirm('Are you sure you want to leave?');
to
  if(!confirm('Are you sure you want to leave?')){
                  return new Redirect(this.router.history.previousLocation, {trigger:false, replace: false})
      }
And still, is there some non dirty way to achieve same behavior?

Hi,
I am experiencing the same problem, but your workaround doesn't work for me.
In all case, this.router.history.previousLocation returns my current page

as another not very clean temp workaround - you can call this.router.history.navigateBack() instead of returning false in canDeactivate(). so
if(!confirm('Are you sure you want to leave?')){       this.router.history.navigateBack();    }

The history entry that is being removed should be the one that was cancelled. So, it makes sense for that to be removed, given that that route was never actually allowed to activate or be visited. If you want different behavior, then using a redirect is a perfectly valid solution.


Generated DDL contains CONSTRAINT UNIQUE KEYandCREATE UNIQUE INDEX` at the same time.

System information:

Operating system (distribution) and version: MacOS
DBeaver version: 7.1.4
Additional extensions

Connection specification:

Database name and version: MySQL5.7
Driver name
Do you use tunnels or proxies (SSH, SOCKS, etc)?

Describe the problem you're observing:

the same unique index not only in DDL but also in create index statement separately. It is fail when I use generate DDL script recreate table.
the problem does not show every time. I can not figure out how to reproduce it.
Steps to reproduce, if exist:

right click a table and click Generate SQL context menu
use generated DDL recreate table

Include any warning/errors/backtraces from the logs

Wrong description.


test(cli): add tests for core/helm module

Description
This pull request changes the following:

Add tests for core/helm module

Related Issues

Closes #548

:tada: This PR is included in version 0.14.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


com.google.android.gms.maps.MapView screenshot transparent

hello,
I have a problem when I get the screenshot of a fragment that contain a  MapView. The map view is transparent.
Screennshot using KarumiShot

Screenshot using the phone (the map appear correctly

Here is my test code:
class AdvertFullScreenMapFragmentTest: ScreenshotTest {

    @Test
    fun launchFragment() {
        val bundle = Bundle().apply {
            putString(BUNDLE_ADVERT_LOCATION, "loc")
            putString(BUNDLE_ADVERT_PRICE, "price €")
        }
        val fragment = launchFragmentInContainer<AdvertFullScreenMapFragment>(factory = object : FragmentFactory() {
            override fun instantiate(classLoader: ClassLoader, className: String): Fragment {
                return AdvertFullScreenMapFragment()
            }
        }, fragmentArgs = bundle, themeResId = R.style.AppTheme).waitForFragment()

        // wait until map load
        Thread.sleep(10000)

        compareScreenshot(fragment)
    }
}

Any idea why this doesn't work with MapView (com.google.android.gms.maps.MapView)?

Right now the library we use under the hood when using plain old MapView components don't work. You can review the details here. I'm afraid until this feature is fixed on their end we won't be able to provide support for maps. I'm sorry.


Fix setting default value of request.PostData of HarEntry

since har entry is of type [src]
interface Entry {
  request: Partial<HarRequest>;
}

so request.postData could have the value undefined
The current approach of setting the default value for this key will fail when postData is undefined
This then breaks the switch case inside the prepare method because there is no optional chaining
This PR is broken into two commits. If only either one feels sufficient, the changes can be cherry-picked or both can be squashed.

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


Add file path in error messages of I/O operations

Ref #1502
We want to add file path in the error message when I/O operations fail.
The corresponding parts are;
https://github.com/pytorch/audio/blob/1f136671b84071a2fe1d5b762df64f3a76310c31/torchaudio/csrc/sox/io.cpp#L16-L24
https://github.com/pytorch/audio/blob/1f136671b84071a2fe1d5b762df64f3a76310c31/torchaudio/csrc/sox/io.cpp#L117-L127
https://github.com/pytorch/audio/blob/14dd917ec60fa69ce3f7c6e3f2eaf520e67928b5/torchaudio/csrc/sox/effects.cpp#L98-L104
https://github.com/pytorch/audio/blob/14dd917ec60fa69ce3f7c6e3f2eaf520e67928b5/torchaudio/csrc/sox/utils.cpp#L84-L87
Note that there the first two checks the file validity directly where as the third case uses the helper function that performs the same check. This helper function is also used by in-memory I/O operations, which does not have paths. So there is a design choice to be made either we want to consolidate the check to this helper function or we want to keep doing the direct checks and add error message generation there. If we consolidate the error handling in the helper function, then we will need to optionally pass the file path that need to be included in the error message.
We need to construct error message dynamically, by attaching the path. For this one can use std::ostream as the example bellow.
https://github.com/pytorch/audio/blob/14dd917ec60fa69ce3f7c6e3f2eaf520e67928b5/torchaudio/csrc/sox/types.cpp#L27-L29
Steps

Make the change described above.
Add test that tries to load a file that does not exist and inspect the error message to see if the provided path exist.
Make a PR and tag cc @mthrok in description or comment.

Note
For setting up the development environment, please refer to CONTRIBUTING.md and torchaudio_unittest

Temporarily closing for internal task assignment.


Forward port 3 to 6

➡ Forward port
Port ign-sensors3 to ign-sensors6
Branch comparison: https://github.com/gazebosim//compare/<TO_BRANCH>...<FROM_BRANCH>
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

@osrf-jenkins run tests please

A few Jammy integration tests failing.  Is this expected currently?

yes the rendering tests have been failing on Ubuntu Jammy github actions for a while. Haven't had the chance to figure out why yet.


How to disable implicit import feature of dotnet 6 globally on Ubuntu/Linux?

I am learning C# and recently installed dotnet 6 on Ubuntu. Since, I am learning C#, I find the automatic import is not ideal for learning as I really dotnet get to see which namespace includes the class I am instantiating. Also, per project disabling of the feature is not as efficient for me either. Also, I have read an article for microsoft docs that disabling DisableImplicitNamespaceImports msbuild property will disable this feature globally, but I not sure how can do that. Therefore, I would be glad if someone helps me to achieve that. Thank You.

This change cause a large number of conflicts with the Fluxor framework. To fix this you can add:

To your .csproj file. I also had to restart visual studio for the change to be picked up.


Next step for Symplectic IVP ODE integrators

[ ] Variable step size
[ ] Specify output as in scipy ?
[ ] Related : continuous output
[ ] Newton iterations instead of fixed point ?
[x] #113
[x] Add optional compensated summation (idem in quadrature)

ask Julia's GeometricIntegrator team about Variable step size

mpmath's computation of Gauss quadrature node/weights is much faster.
cf https://github.com/mpmath/mpmath/blob/master/mpmath/calculus/quadrature.py

Continuous output =>
Lagrange barycentrc interpolation. Needs wlag weights.
Maybe merge SegmQuad and ImplicitRKTable since both would benefit from Lagrange Barycentric Interpolation.
Needs support for partially initialize object.


MacOS install without Homebrew

Hello crew,
I tried the scrcpy install via homebrew for mac and received the following error once it got to installing ninja:
Error: An exception occurred within a child process:  Utils::InreplaceError: inreplace failed/usr/local/Cellar/glib/2.62.1/lib/pkgconfig/glib-2.0.pc:  expected replacement of "Libs: -lintl -L${libdir} -lglib-2.0" with "Libs: -L${libdir} -lglib-2.0 -L/usr/local/opt/gettext/lib -lintl"
I tried both brew upgrade and brew doctor with no luck. The Homebrew folks on the IRC believe it's because I am on 10.12.6 and said I should install directly here without Homebrew. How can I install here without homebrew? I followed the manual install as well and run into the exact same issue/error with ninja when running: brew install sdl2 ffmpeg. Thank you for any help!

Just follow BUILD.md.
# install dependencies
brew install sdl2 ffmpeg pkg-config meson

# download prebuilt server v1.10
wget https://github.com/Genymobile/scrcpy/releases/download/v1.10/scrcpy-server-v1.10.jar
# check its checksum
echo 'cbeb1a4e046f1392c1dc73c3ccffd7f86dec4636b505556ea20929687a119390  scrcpy-server-v1.10.jar' | sha256sum -c

# configure
meson x --buildtype release --strip -Db_lto=true \
    -Dprebuilt_server=scrcpy-server-v1.10.jar
# build
ninja -Cx
# install
ninja -Cx install

I am getting 'Command not found' when doing:
wget https://github.com/Genymobile/scrcpy/releases/download/v1.10/scrcpy-server-v1.10.jar
I downloaded manually and placed on the desktop and am getting:
Annas-MBP-3:~ anna$ meson x --buildtype release --strip -Db_lto=true \

-Dprebuilt_server=/Users/Anna/Desktop/scrcpy-server-v1.10.jar

ERROR: Neither directory contains a build file meson.build.
Any further help would be appreciated! Thank you!

Just download the file with anything you want (your browser for example).

Thank you for all the help. Still running into issues :( here is where I am at now:
`Last login: Fri Oct 11 12:37:57 on ttys000
Annas-MBP-3:~ anna$ echo 'cbeb1a4e046f1392c1dc73c3ccffd7f86dec4636b505556ea20929687a119390 scrcpy-server-v1.10.jar' sha256sum -c
cbeb1a4e046f1392c1dc73c3ccffd7f86dec4636b505556ea20929687a119390 scrcpy-server-v1.10.jar sha256sum -c
Annas-MBP-3:~ anna$ eson x --buildtype release --strip -Db_lto=true \

-Dprebuilt_server=scrcpy-server-v1.10.jar

-bash: eson: command not found
Annas-MBP-3:~ anna$ ninja -Cx
ninja: Entering directory x' ninja: error: loading 'build.ninja': No such file or directory Annas-MBP-3:~ anna$

eson: command not found

It's meson.

sha256sum: command not found

It's just to verify the checksum of the file. Skip this step if you don't care.

`Annas-MBP-3:~ anna$ meson x --buildtype release --strip -Db_lto=true \

-Dprebuilt_server=scrcpy-server-v1.10.jar

ERROR: Neither directory contains a build file meson.build.
Annas-MBP-3:~ anna$ `

Neither directory contains a build file meson.build.

You need to run this command from the repo of scrcpy that you cloned:
git clone https://github.com/Genymobile/scrcpy
cd scrcpy
meson ...


Add tiered access rhmi 3scale dump

JIRA: INTLY-5281
Tag @mrbarge for review/merge as requested in JIRA

/retest

@mrbarge Thanks for the review and suggestions.  Its tough to add logic into such a complex chain of scripts when you can't actually test the full flow yourself.

/retest

/lgtm


[addon-cssresources] Resource IDs are not displayed in panel

Describe the bug
Per documented behaviour, I expect to see the ID of each resource I have added in the addon panel interface. However, it prints a # without any name value for each stylesheet.
To Reproduce

Add cssresources options as documented:

addDecorator(
  withCssResources({
    cssresources: [
      {
        id: 'core-framework',
        code: '<link rel="stylesheet" type="text/css" href="/assets/css/main.min.css">',
        picked: true
      }
    ]
  })
);

Click on 'CSSRESOURCES' addon panel.
See no name/ID label and React key usage warning (see screenshot below).

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Code snippets
Error message (pre stack trace):
Warning: Each child in a list should have a unique "key" prop.

Check the render method of `CssResourcePanel`. See https://fb.me/react-warning-keys for more information.

System:

OS: Served on Ubuntu 18.04 via WSL, viewed in browser on Windows 10
Browser: Chrome
Framework: vue
Addons: cssresources 4.1.13
Version: 4.1.12

cc @nm123github

Is this issue still present in V5?

same history with vue storybook installed withvue-cli-plugin-storybook, but i changed prop "id" to "name", and it works
Working example:
addParameters({     cssresources: [{         name: bluetheme,         code: ,         picked: true,       },     ],   })

@Nejik Same use case here with Vue, looks to just be a documentation blip then!

@huntie @Nejik mind creating a small PR to fix the docs?

It appears that the default branch on this repository (and therefore the docs) is simply ahead of the currently distributed version (4.1.13), and includes https://github.com/storybooks/storybook/commit/412cd179849fdc442206b93616d57faf30a0c0cd where id is used consistently and documented. Probably worth moving forward with that release, and having this issue as reference. Maybe docs in this repository should be published at the same released version of each package.

@huntie There are a couple things going on here:

master branch is equivalent to latest npm tag (version 4.1.x currently)
next branch is equivalent to next npm tag (version 5.0-rc.x currently)

If there is a breaking change in next we should document this in MIGRATION.md so that people who are upgrading from 4.x to 5.x can expect it and know how to fix it. Better yet, we deprecate the old behavior so that nothing breaks, and then remove it in 6.0. Can you let me know whether this is a breaking change?

@shilman Understood. What I meant is that a user (like myself on this occasion) will commonly jump to a GitHub homepage for a project, ignore the default branch and essentially read the documentation there, which is ahead. On npm however, the correct state of README.md is present for the release and the documentation is correct.
A breaking change will therefore be introduced between 4.1.x and 5.0.0 :+1: I'll open the PR for MIGRATION.md soon. :wink:


OIDC: More claims for GitHub's provider

GitHub has added claims that allow us to attest to the repository owner's stable ID, which in turn allows us to prevent "account resurrection"-style attacks.
Needs test updates, but this should be functionally complete. The migration is primarily to make the comparisons during claim verification more straightforward.

Ref: https://github.com/pypa/warehouse/issues/10645#issuecomment-1106910136

Refactored the migration to use renames 🙂