feat: add alarm system icon

Description
Adding alarm logo. Needed for rewriting post call wrap-up banner
Demo:

Pull Request Checklist

[x] Ask the contributors if a similar effort is already in process or has been solved.
[x] Review the contribution guidelines.
[x] Use staging as your pull request's base branch. (All PRs using production as its base branch will be declined).
[x] Ensure all gulp scripts successfully compile.
[x] Update, remove, or extend all affected documentation.
[x] Ensure no private Dialpad links or info are in the code or pull request description (Dialtone is a public repo!).
[x] Request a review from Brad Paugh, David Becher, or Drew Chandler.

Looks great thanks!

Thanks Brad! Do you know when the new version will be released? I have a subtask to use the new icon

Thanks Brad! Do you know when the new version will be released? I have a subtask to use the new icon

Yep I can release for you right now.

@braddialpad

Thanks Brad! Do you know when the new version will be released? I have a subtask to use the new icon

Yep I can release for you right now.

Thanks!!


How To Stream This Url On JW Player

@leandromoreira
http://mhdtvlive.online/delta/airtel.php?c=chutti&e=.m3u8
This link Open on google chrome browser normaly showing on playlist
How To stream Jwplayer On this link

??? this is not jwplayer repository, maybe https://github.com/jwplayer/jwplayer?


Mpi fixes

Fixes #4662 and the error mentioned in the comments of #4540
Proposed Changes
These are assorted patches that fix some small inconsistencies in the MPI futures layer.
This is being pushed to prevent duplicated effort on the MPI backend, but should not be merged yet as there may be some more patches applied (subject to further testing).

@weilewei please try this latest version of the mpi branch (rebased onto master today) and tell let me know if this fixes #4752 #4662 etcetc. I still have more work to do on this branch, but if this works and passes tests, then I can continue work on a new branch and let this one me merged.

The problem is that if you turn off networking, distributed_runtime and don't use async_mpi then mpi_base is not loaded
[ 75%] Building CXX object libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/src/command_line_handling.cpp.o
/apps/daint/UES/biddisco/src/hpx/libs/command_line_handling/src/command_line_handling.cpp: In member function 'bool hpx::util::command_line_handling::handle_arguments(hpx::util::manage_config&, boost::program_options::variables_map&, std::vector<std::__cxx11::basic_string<char> >&, std::size_t&, bool)':
/apps/daint/UES/biddisco/src/hpx/libs/command_line_handling/src/command_line_handling.cpp:795:31: error: 'hpx::util::mpi_environment' has not been declared
         bool have_mpi = util::mpi_environment::check_mpi_environment(rtcfg_);
                               ^~~~~~~~~~~~~~~
make[3]: *** [libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/build.make:63: libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/src/command_line_handling.cpp.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:21331: libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:61919: tests/performance/local/CMakeFiles/future_overhead_test.dir/rule] Error 2

you need to protect the call to mpi_environment

The problem is that if you turn off networking, distributed_runtime and don't use async_mpi then mpi_base is not loaded
[ 75%] Building CXX object libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/src/command_line_handling.cpp.o
/apps/daint/UES/biddisco/src/hpx/libs/command_line_handling/src/command_line_handling.cpp: In member function 'bool hpx::util::command_line_handling::handle_arguments(hpx::util::manage_config&, boost::program_options::variables_map&, std::vector<std::__cxx11::basic_string<char> >&, std::size_t&, bool)':
/apps/daint/UES/biddisco/src/hpx/libs/command_line_handling/src/command_line_handling.cpp:795:31: error: 'hpx::util::mpi_environment' has not been declared
         bool have_mpi = util::mpi_environment::check_mpi_environment(rtcfg_);
                               ^~~~~~~~~~~~~~~
make[3]: *** [libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/build.make:63: libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/src/command_line_handling.cpp.o] Error 1
make[2]: *** [CMakeFiles/Makefile2:21331: libs/command_line_handling/CMakeFiles/hpx_command_line_handling.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:61919: tests/performance/local/CMakeFiles/future_overhead_test.dir/rule] Error 2

you need to protect the call to mpi_environment

Thanks @biddisco! Excellent point. I had somehow looked that check_mpi_environment was defined in command_line_handling but this makes much more sense. I'll change that back.

retest


HTTP 1MB upload limit

Uploading a file larger than 1MB to an HTTP endpoint will return a 413 Request Entity Too Large error. 1MB is the default client_max_body_size setting for Nginx so I expect this is a limit at the HTTP proxy.
Nginx config and default: http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size
Error returned:

<title>413 Request Entity Too Large</title>

413 Request Entity Too Large

nginx

@tombeynon , we have been facing the same issue while uploading docker images to Skynet through Akash.
Usually, docker images are larger than 5 MBs for most projects and even larger for Nodejs, Ruby and Python based projects.
We're currently developing Open Registry on Akash and Skynet and this is the only challenge we've been facing to get it through.

Thanks all.  We can change this to something larger quite easily.  We'll look into it next week.

@boz would it be possible to also add support for setting a custom value for this in our deployment manifest?

@boz would it be possible to also add support for setting a custom value for this in our deployment manifest?

It should be possible with our current backend tooling.  If it is, it'd be a matter of adding support for it in the manifest and provider services.  It's a very reasonable feature request, we'll try to prioritize it.

Looks like the right way to achieve this should be this expose.http_options.max_body_size
Changing proxy-body-size in the ingress-nginx-controller ConfigMap like here does not seem to help as that would only change the upstream-default-backend, you can verify by running this command on the provider:
# kubectl -n ingress-nginx exec $(kubectl -n ingress-nginx get pods -l app.kubernetes.io/component=controller -o jsonpath='{.items[0].metadata.name}') -- cat /etc/nginx/nginx.conf | grep -Ei 'proxy_upstream_name|client_max_body_size'

However, the expose.http_options.max_body_size isn't seem to be implemented on the akash provider side itself as it didn't change the ingress configuration. (akash v0.14.1-rc0).
# kubectl -n dsuaebrpld2tpjrtcl13cl5fptmiebns2aqjvleo1beti get ing -o yaml | grep -i body-size
      nginx.ingress.kubernetes.io/proxy-body-size: "104857600"
      nginx.ingress.kubernetes.io/proxy-body-size: "104857600"
      nginx.ingress.kubernetes.io/proxy-body-size: "104857600"
``

That was to akash1f6gmtjpx4r8qda9nxjwq26fp5mcjyqmaq5m6j7, it is an older deployment actually. I'll test a fresh deployment now

Appreciate your patience with this, I did some more testing today.
I created a deployment with my SDL I use for testing this

1 megabyte file POST works OK

I've redeployed the whole thing (Akash Provider & Kubernetes) from scratch, using https://nixaid.com/deploy-akash-provider-with-kubeadm/ -- cannot reproduce this issue anymore.
I've used gcr.io/google_containers/echoserver:1.10 image.
@hydrogen18 you might need to fix your image hydrogen18/http_behavior_diagnostic:20210914b as always returns 413 for anything >= 10MiB:
$ docker run -p 8080:8080 --rm -ti hydrogen18/http_behavior_diagnostic:20210914b
======== Running on http://<IP_ADDRESS>:8080 ========
(Press CTRL+C to quit)

2021-10-31 22:25:42,800 aiohttp.access  INFO     START 'POST' '/body-size'
2021-10-31 22:25:42,814 aiohttp.access  INFO     <IP_ADDRESS> [31/Oct/2021:22:25:42 +0000] "POST /body-size HTTP/1.1" 200 217 "-" "curl/7.68.0"
2021-10-31 22:25:45,344 aiohttp.access  INFO     START 'POST' '/body-size'
2021-10-31 22:25:45,356 aiohttp.access  INFO     <IP_ADDRESS> [31/Oct/2021:22:25:45 +0000] "POST /body-size HTTP/1.1" 413 276 "-" "curl/7.68.0"

$ dd if=/dev/urandom of=testfile bs=1M count=9
9+0 records in
9+0 records out
9437184 bytes (9.4 MB, 9.0 MiB) copied, 0.0396766 s, 238 MB/s
$ curl -s -X POST localhost:8080/body-size -T testfile ; echo
request body size is 9437184 bytes

$ dd if=/dev/urandom of=testfile bs=1M count=10
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0442269 s, 237 MB/s
$ curl -s -X POST localhost:8080/body-size -T testfile ; echo
Maximum request body size 10485760.0 exceeded, actual body size 10485760

Hey Guys,
any update on this issue ?
We're really waiting to use this feature

@arno01 said he cannot reproduce the issue any longer, so I'm closing this


Unable to start sidecar when using secrets components with dapr run -f

Expected Behavior
When running the a daprized app using the dapr cli, it should be able to read secrets defined in a configuration
Actual Behavior
The dapr sidecar is never started.
Steps to Reproduce the Problem
See a small repro here - https://github.com/bondz/dapr-secrets
Clone the repo.
cd my-service
npm install

There's a single secret defined in the .dapr/secrets.json file that the app (my-service) reads.
When running the app directly using dapr multi-app run in the root directory, the sidecar is never started.
dapr run -f .

It hangs for a while, eventually errors and exits.

However, if you use vscode and run the app using the launch configuration, passing the config flags directly, it works fine.

When using dapr run -f ., daprd is looking for the file in the my-service directory rather than relative to where  dapr run was invoked.
Moving the secret file to the same directory as the service is a workaround.

Bot comment

Bot comment

Bot comment


Updating branch Espresso-2 - Adding test 'Search'

Search test check we are getting at least one result under each label.

ha, you closed it :)
Yeah, we wouldn't merge pull requests like these.
Make sure the pull request contains only the commits you made.
You can start a new branch that stems off of the most recent point on master, apply your changes and then send the pull request.


128x128 output not supported

Hello,
I'm trying to generate events from a sequence of images. When I tried to use the --dvs128 option that is specified in the readme I got the following error message:

ValueError: AEDAT-2.0 output width=128 height=128 not supported; add your camera to v2ecore.output.aedat2_output or use one of the predefined DVS cameras, e.g. --dvs346 or --dvs240

Using --dvs240 and --dvs346 works, I'm wondering, is the --dvs128 option not supported?
Thanks!

Hmm, we maybe didn't implement it. It should be very easy to add
following AEDAT-2.0 data structure instructions from
https://inivation.github.io/inivation-docs/Software user guides/AEDAT_file_formats.html#aedat-20
The DVS128 2.0 format is the same as 1.0 format but address is widened
to 32 bits (unused bits are set to zero). It is much simpler than the
DAVIS AEDAT-2.0 format. But v2e only writes DVS events, not frames or
IMU samples so far, for DAVIS cameras.


use a code generator for not implemented tests

Instead of having a static snippet that requires to be manually edited I thought to create a generator by taking all the methods from cpython

@andrew-ld thank you for contributing to this project!


Proposal to add e2e-testing using TestCafe

Hi,
This PR is a proposal to add e2e tests for bootstrap components using the TestCafe testing framework.
For demonstration, I've created two tests for your tests/visual/modal.html page.
While creating these tests, I've found a behavior that looks like a bug:

Open the modal dialog
Hover over the link that shows a tooltip
Then try to close the modal dialog.
It's not closed, and the Tooltip is transitioning JS-error is raised.

I've created a test for this case (Demonstrate Modal page is not closed issue) and it fails so far (https://travis-ci.org/twbs/bootstrap/jobs/198761611#L1190).
If you are interested in e2e tests, I can take this task and create tests for all components, or I can assist those who will do it.
If necessary, it is possible to setup e2e testing on headless browsers or on saucelabs (you can see the details about it in the How to set up E2E browser testing for your GitHub project article)
What do you think about it?

Maybe I'm failing to understand something, but I'm not sure what the benefit of this over QUnit is. QUnit can already interact with the DOM, press buttons, etc. Possibly our tests are not comprehensive enough, but that's a different problem. Additionally, I've never heard of TestCafe before and I'm not sure it's quite as polished as I'd like.

Closing per previous comment.


PowerShell commands broken when project opened from a file share

Moved from https://github.com/aspnet/EntityFramework.Docs/issues/346
cc @Klipi
I'm following the tutorial here: https://docs.microsoft.com/en-us/ef/core/get-started/aspnetcore/new-db up to the point where I need to run the first migration:
PM> Add-Migration MyFirstMigration
Unable to resolve startup project 'Microsoft.PowerShell.Core\FileSystem::\\mac\home\documents\visual studio 2017\Projects\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.csproj'.
To undo this action, use Remove-Migration.
Add-Migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character.
Parameter name: basePath"
At line:1 char:1
+ Add-Migration MyFirstMigration
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException,Add-Migration

I'm running Visual Studio 2017 RC3 under a Win10 VM in Parallels, so that might be the cause of some issues. However I have no idea on how to start to debug this, as I'm quite new to the .NET Core world and Entity Framework.

Copying this over from the documentation side
PM> $DTE.Solution.SolutionBuild.StartupProjects
EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.csproj
PM> $DTE.Solution.Properties.Item('Path').Value
\\mac\home\Documents\Visual Studio 2017\Projects\EFGetStarted.AspNetCore.NewDb\EFGetStarted.AspNetCore.NewDb.sln

I'll try to redo the tutorial under C:\ and see what happens. Not sure if anything else is breaking, been away from Windows and VS for a couple of years. A quick HelloWorld-type web app works nicely and I was even able to publish it to Azure without a hitch. Trying to add the database layer (and EF along it) is the first I'm running into trouble.

@bricelam, No issue running under C:\

Groovy. I suspect this is the root of our problems:
PS> Split-Path \\mac\home -IsAbsolute
False

im having a similar issue except that im not in a file share. I just got vs2017 and i get this error when i try to add-migration
`add-migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character.
Parameter name: basePath"
At line:1 char:1

add-migration init

  + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
  + FullyQualifiedErrorId : ArgumentException,Add-Migration

`

I have the same error message as @ojorma
Using VS2017 ASPNET CORE & EF CORE 1.1 versions
I am using a class library for the DataContext Objects
I only get this error with the DataContext which also is the context object which is used for ApplicationDbContext
When I try it with other DataContext objects which are for small stand alone databases I don't get the error.
I also noticed that when I tried to run the web app and use the build in apply migrations button that EF-Core could not login to the database and was trying to use my Microsoft Login for the Windows/Microsoft Account, even when I have set the connection string in the app settings to use a trusted connection.
The message asked me to create the migration manually for the ApplicationDbContext
I created it manually, no error, I updated the database with no error
Once I had done this manually via the nuget command window in VS2017
I was then able to create the same migration which I got the above error for
but this time I got no error and was able to update the database and everything worked as it normally does with no errors

@ojorma @dotnetnoobie Are you using Docker? You may be hitting #7439.

@bricelam I am using a console app. I first tried it with a class library but thesame thing so i tried it again in a console app. I just got vs2017 and testing the basic stuff out. I got burnt with version 1.0 cause of entityframework core.

this is what my sample project looks like

@bricelam  I am not using docker
Just a standard projects
AspNetCore 1.1 app which references Class Library

netcoreapp1.1

....

I have the DataContext objects on a separate project which is a
.NetCore App 1.1 (Class Library)

netcoreapp1.1

@bricelam I also had problems with the class library originally
what I did was create a test website with individual auth set in the options
I then opened the .csproj file and copied the correct EF Core related references for the nuget packages
and added them to the class library .csproj file
This seemed to solve the issues I has of not actually having all the correct nuget packages referenced to get everything working
@rowanmiller @dotnetnoobie

@dotnetnoobi @rowanmiller it turns out the problem is caused as a result of having multiple dotnetsdk and the wrong one been called in the environmental variables. if you dont want to uninstall the earlier sdk make sure you move

i moved the 64bit dotcli path up (C:\Program Files\dotnet ) which had the current sdk

Hello @ojorma
I'm facing the same problem with migration on VS 2017. Where can I set the environment variable order please ?
It's not the Windows interface for environment variables you're showing in the screen shot ?
Thank you.

Hello @ojorma,
I face the same problem with migration on Visual Studio 2017 under Windows 8.1 . I've checked and I have only one SDK installed the 1.0.0 at C:\Program Files\dotnet.
Have you tried something else ? cause I have exactly the same error message.

@imad24  when you type dotnet --version in the command line what does it give you? this is mine

you could still try installing the x86 version of the dotnet sdk.  if you could share a sample project on onedrive or something, I could download an check

@ojorma I've got the same version as you can see (along with two others installed i think)

@bricelam Everything seems ok with the Powershell commands as well:
PM> $DTE.Solution.SolutionBuild.StartupProjects
HPCRM\HPCRM.csproj
PM> $DTE.Solution.Properties.Item('Path').Value
C:\Users\imad.rahmouni\documents\visual studio 2017\Projects\HPCRM\HPCRM.sln
PM>
The error message just in case:

@ojorma I'll try to install the x86 version as you suggested, then give it another try with a sample project. I'll send  you a link if it still not work.
Thank you

@imad24    im seeing 1.0.0-preview2-1...... That means there are multiple sdks on your system.

Please try to delete both folders that have the preview thing. you can leave them in the recycle bin, then check a similar path on the programfiles x86 folder, if there is anyone with preview in it delete the folder. You can use add remove programes to uninstall later. Then check your environmental variables as I mentioned earlier.
I think visual studio is some how invoking the older sdks. Please let us know your outcome. Good luck

@ojorma I didnt want to delete the older preview version because I have other projects pointing to them that I haven't migrated yet. But I thought since the "dotnet --version" is displaying "1.0.0" then the right SDK is used. Anyway:
1- I deleted the two folders: not working, same error.
2- I have no dotnet folder in the x86 programs(not yet)
3- In the environment variables i only have one line for dotnet which points to "C:\Program Files\dotnet"
Next i'll install and try with the x86 version. I'll keep you updated.

Hello again @ojorma,
As you mentionned I tried to recreate the same conditions as yours, I installed the x86 version, made the changes to the environment variables and it didnt work. (naturally I didnt have the x86 line before)

After installing the x86 version I realized the 1.0.1 skd was out, so installed the 1.0.1 x64 and made the same tests, I even inverted the env variables, still nothing.
Here is a screenshot of most of the tests I made, I dont think it's related to the multiple SDKs as you can see (PM console VS cmd console)
It's not related to the paths either since I am on an exclusively windows environment and the powershell commands results seem ok as I mentionned earlier.

Please tell me if you have other suggestions.

while the project is open in visual studio type dotnet  alone and dotnet --version. Let see what gets invoked

Lastly if its a demo project you can send to my email. Dont know if its allowed here<EMAIL_ADDRESS>Let me check if it runs. if not I will assume its some wrong reference from nugget package.

@ojorma I'm sending you the project by email.

Hello everyone,
Just to point out that i fixed my problem. Actually it had to do with the data model on which I was applying the migration.
Many "design errors" were on it (a foreign key property that references a key that doesn't exist on the target type for example.)
I don't understand why it displayed that exception message though.
Thanks for your help @ojorma

Hello, Im having this problem too...
ps: the exact command was working last week, not sure if its related with VS2017 update yesterday.

@Cae2 For me it was related to the model classes, there were some errors so the migration was raising this "generic error".
Try to scaffold a simpler model (with just one table for example) and see if it displays the same message.

@imad24 created a very simple table to test, but the same error occurs:

also tried the @bricelam command:

Well, it may be something else.
One last thing, when creating a migration from a class with "add-migration" you have to specify a primary key for each entity, I see that you didn't on the table you're willing to scaffold. can you give it a last try with primary key set ?

@imad24
To be honest, it seems that doesnt even reach the point to scaffold something...

@imad24  glad u fixed it. I even went to the extent of living just one table in the dbcontext and still got the error  but I never checked the table it self. That error message is highly misleading. I guess Entityframework core is still evolving.

lol, this is really strange... I just keep flooding the PMC and it works eventually...

What type of project are you using? This may be an issue with the new project system...

I am getting the same error as well on new Class Library (.NET Standard) project while trying to do database first initialisation with connection string:
Scaffold-DbContext "Data Source=Server1;Initial Catalog=MyDb;Persist Security Info=True;User ID=Developer;Password=Password" Microsoft.EntityFrameworkCore.SqlServer -OutputDir Models -v -t MyTable1
I am running Windows 10 with VS 2017. My .csproj file looks like:
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>netstandard1.4</TargetFramework>
  </PropertyGroup>
  <ItemGroup>
    <PackageReference Include="Microsoft.EntityFrameworkCore" Version="1.1.1" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Design" Version="1.1.1" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer" Version="1.1.1" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.SqlServer.Design" Version="1.1.1" />
    <PackageReference Include="Microsoft.EntityFrameworkCore.Tools" Version="1.1.0" />
  </ItemGroup>
</Project>

My scenario is to create a common .NET Standard library so that it can be used in both .NET Core and Xamarin projects. Can someone please point out if I am on right path. The error message isn't helping much. Thank you.

@themausam  I dont think codefirst can run from a .netstandard library

I am gettin same error after updating my project microsoft packages most to 1.1.2. Before that i did not had this error. Any suggestion?

I can confirm that this has to do with invalid data modelling. Had this issue as well with a type on an inverse property attribute causing the generic errror.

I started getting error out of nowhere (I did upgrade by VS2017 Preview verison, but doubt that has reference).
I have a Dot Net Core 2 Console App (2.0.0-preview1-005977) that I am using to do Migrations using Package Manager. The Context is in a .Net Standard 2.0(2.0.0-preview1-25301-01) CL. Here is my Context and the Factory
    public class BlogContext : DbContext
    {
        public BlogContext(DbContextOptions<BlogContext> options) : base(options) { }
        public DbSet<ContactEntity> Contacts { get; set; }

        public DbSet<UserEntity> Users { get; set; }
        public DbSet<PostEntity> Posts { get; set; }
        public DbSet<PostTagEntity> PostTags { get; set; }
        public DbSet<TagEntity> Tags { get; set; }
        public DbSet<CategoryEntity> Categories { get; set; }
   }

    public class BlogContextFactory : IDbContextFactory<BlogContext>
    {
        public BlogContext Create(DbContextFactoryOptions options)
        {
            var builder = new DbContextOptionsBuilder<BlogContext>();
            builder.UseSqlServer(
                "Server=localhost;Database=Blog;Trusted_Connection=True;MultipleActiveResultSets=true");

            return new BlogContext(builder.Options);
        }
    }

I have the Console Project as Startup and the Default Project the CL and when I run Add-Migrations Test, I get
System.ArgumentNullException: Value cannot be null.
Parameter name: contentRootPath
   at Microsoft.EntityFrameworkCore.Utilities.Check.NotEmpty(String value, String parameterName)
   at Microsoft.EntityFrameworkCore.Design.Internal.MigrationsOperations..ctor(IOperationReporter reporter, Assembly assembly, Assembly startupAssembly, String environment, String projectDir, String contentRootPath, String rootNamespace)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.<>c__DisplayClass4_0.<.ctor>b__4()
   at Microsoft.EntityFrameworkCore.Internal.LazyRef`1.get_Value()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.AddMigrationImpl(String name, String outputDir, String contextType)
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.<>c__DisplayClass3_0`1.<Execute>b__0()
   at Microsoft.EntityFrameworkCore.Design.OperationExecutor.OperationBase.Execute(Action action)
Value cannot be null.

And if I set the CL as the Startup project, I get
Startup project 'Database' targets framework '.NETStandard'. This framework is not intended for execution and may fail to resolve runtime dependencies. If so, select a different startup project and try again.
To undo this action, use Remove-Migration.
Add-Migration : Exception calling "AddFromFile" with "1" argument(s): "'basePath' cannot be an empty string ("") or start with the null character.
Parameter name: basePath"
At line:1 char:1
+ Add-Migration Blog
+ ~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-Migration], MethodInvocationException
    + FullyQualifiedErrorId : ArgumentException,Add-Migration

This was working fine but all of a sudden it isn't. All my nuget packages are from 5/9 so I am totally lost here.

@isaac2004 - See https://github.com/aspnet/EntityFramework/issues/8731

I got the same issue as well, I have try all the solutions mentioned above, and the issue still occurs.

@oldsand an issue with the same exception was reported again and we are tracking it at #10044. It would be great if you could help us repro it. Please reply there with repro steps and project.

if u are facing issue in Package manager console, try using dotnet cli with the following commands:
for add migration:=>dotnet ef migrations add MyFirstMigration
and for update database:=> dotnet ef database update, it worked for me

Related issues: #14349 & #14781


add flake8-comprehentions

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Before submitting (must do checklist)

[x] Did you read the contribution guide?
[ ] Did you update the docs? We use Numpy format for all the methods and classes.
[ ] Did you write any new necessary tests?
[ ] Did you update the CHANGELOG?

Type of Change

[x] Examples / docs / tutorials / contributors update
[ ] Bug fix (non-breaking change which fixes an issue)
[x] Improvement (non-breaking change which improves an existing feature)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Proposed Changes

Related Issue

Closing issues

Codecov Report

Merging #689 (2827670) into master (d483087) will not change coverage.
The diff coverage is 75.00%.

@@           Coverage Diff           @@
##           master     #689   +/-   ##
=======================================
  Coverage   83.80%   83.80%
=======================================
  Files         119      119
  Lines        6398     6398
=======================================
  Hits         5362     5362
  Misses       1036     1036

Impacted Files
Coverage Δ

etna/analysis/plotters.py
21.27% <0.00%> (ø)

etna/datasets/tsdataset.py
90.08% <100.00%> (ø)

etna/ensembles/base.py
100.00% <100.00%> (ø)

etna/transforms/feature_selection/base.py
100.00% <100.00%> (ø)

etna/transforms/missing_values/resample.py
96.42% <100.00%> (ø)

etna/transforms/utils.py
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


Similar to #210 WARNING: parse invoke code failed, This may affect feature of export code.

Hi
I am getting the above warning during runserver using pygwalker 0.3.7 with Django 4.2.1.(#210 was with notebook)
Can I safely ignore?
Kind Regards
Terry

yes, you can ignore it.
import logging

logging.getLogger("pygwalker").setLevel(logging.ERROR)

Thanks a ton!
Cheers
Terry
Kind Regards
Terry Lewis

From: Douding @.>
Sent: Wednesday, September 27, 2023 1:44:05 PM
To: Kanaries/pygwalker @.>
Cc: terryelewis @.>; Author @.>
Subject: Re: [Kanaries/pygwalker] Similar to #210 WARNING: parse invoke code failed, This may affect feature of export code. (Issue #247)
yes, you can ignore it.
import logging
logging.getLogger("pygwalker").setLevel(logging.ERROR)
—
Reply to this email directly, view it on GitHubhttps://github.com/Kanaries/pygwalker/issues/247#issuecomment-1736738484, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH4JUYBXMJLMHXRSNP4CBATX4O4KLANCNFSM6AAAAAA5IXBBVE.
You are receiving this because you authored the thread.Message ID: @.***>


Settings: Bluetooth sensor not selectable when Bluetooth is off

If Bluetooth is off, a heart rate sensor cannot be selected (OS does not report any devices).
Therefore, disable this settings when the Bluetooth is turned off.
We need to use a BroadCastReceiver listening for BluetoothAdapter.ACTION_STATE_CHANGED.
Note: this feature could also be interesting for the TrackDetailActivity while recording (show and hide heartrate).

This was also fixed in #58: the preference does not show the selection dialog.


Simplified SCT list serialization

Builds off the work of #1124 but trims the public interface a bit. Since the SCT list is a mix of TLS and ASN.1 encoding styles (thanks to cloudflare/cfssl for reminding me of this) we can't just use encoding/asn1, in the places where TLS style encoding is required I've just reused existing functions (i.e. writeVarBytes/writeUint).
This also updates the test case as the previous one did not parse correctly under other SCT implementations (namely OpenSSL, the easiest way to test this is to generate a OCSP response/cert that contains the SCT extension which OpenSSL will happily parse + print). Since there are no explicit test vectors for SCT/list serialization I've just used one I generated that parsed properly with OpenSSL.

Sorry about not finishing this. Real life got in the way. Anyway I agree to my commits being used

Generally looks good. @AlCutter could you take a look, and also maybe fix up the CLA tag? Roland tells me that both he and @mehmooda have signed the CLA.

Looks good, but the CLA bot is choking on the merge-commit (for future reference it's better to rebase onto master); I suspect it wants me to add everyone who ever committed anything here and get their approval to (re)commit their commits :/.
I've re-built the string of commits based on master at AlCutter/sctlist-trim, so I could merge that and we'll just close this with a "merged as ..." comment, or you can bump your branch to that commit (or recreate it yourself) and re-push?

Bumped.

@googlebot? Are you happy? 😃

So it appears there's some issues with @googlebot, where it can't always identify the authors on GitHub properly, because some of the APIs it uses only give the GitHub username? And it gets confused, due to some bugs... I checked the CLAs manually, though, and it's all fine.
@rolandshoemaker, I think it might help in the future if you went to https://cla.developers.google.com/ and updated your contact information to have your GitHub username?


can't run tests with same name multiple times

JUnit supports running tests with the same fully-qualified name several times.
It can be achieved by using some non-standard built-in runners or some custom runners.
Here is the easiest example of such test using org.junit.runners.Suite
build.sbt
name := "junit-with-sbt"
version := "0.1"
scalaVersion := "2.13.6"
// NOTE: by default junit-interface ignores `org.junit.runners.Suite`, we need to disable it
Test / testOptions += Tests.Argument( "--verbosity=3", "--ignore-runners=")
libraryDependencies += ("com.novocode" % "junit-interface" % "0.11" % Test).withSources()

MyCompositeTest.scala:
package example

import junit.framework.{TestCase, TestSuite}
import org.junit.Assert.fail
import org.junit.runner.RunWith
import org.junit.runners.Suite.SuiteClasses

@RunWith(classOf[org.junit.runners.Suite])
@SuiteClasses(Array(
  classOf[example.MyActualTest],
  classOf[example.MyActualTest],
  classOf[example.MyActualTest]
))
class MyCompositeTest extends TestSuite

class MyActualTest extends TestCase {
  def test1_Success(): Unit = {
    println("running success test")
  }

  def test2_Failed(): Unit = {
    println("running failed test")
    fail("some reason")
  }
}

Note that in practice, those tests can have different contexts but have the same name.
Intellij IDEA, for example, successfully runs such tests:
(note, that in total, there were 6 tests run.

And thisis what testOnly example.MyCompositeTest outputs:

I will prepare a PR with a fix soon


Is it time to release 0.7.0 to crates.io?

I am currently linking openexr-rs from GitHub repositories as they contain latest updates.
Since 0.6.0 there have been significant changes:

data window fixes (crash bug)
exception message management fixes (crash/corruption bug)
set_global_thread_count() (enhancement)
set_multiview() (enhancement)

For consistency I would be happier to use crates.io repo instead.

I'm not sure we've actually made any breaking changes? Guess it doesn't hurt to play it safe.

There are no breaking changes but the API has been extended.

Semantic Versioning 2.0.0
Given a version number MAJOR.MINOR.PATCH, increment the:

MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.

From https://semver.org/
Now, this is a still a 0.x so it's ok to play loose.

In the Rust ecosystem, and in particular in cargo, pre-1.0 versions are
treated as a right shift; minor versions have the semantics of major, and
patch of minor.
On Sat, Jul 13, 2019, 13:06 Nico Orrù<EMAIL_ADDRESS>wrote:

There are no breaking changes but the API has been extended.
Semantic Versioning 2.0.0
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner,
and
PATCH version when you make backwards-compatible bug fixes.
From https://semver.org/
Now, this is a still a 0.x so it's ok to play loose.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cessen/openexr-rs/issues/41?email_source=notifications&email_token=AAAZQ3U5NZ2YPTAY6IGK4PTP7IYTRA5CNFSM4IC5AEW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3YQKQ#issuecomment-511150122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAZQ3S355OIUEXHGLW6DALP7IYTRANCNFSM4IC5AEWQ
.

I've seen it in many other projects, found confusing :)
Either way is fine.

I think it is definitely time for a new release, yes!  I've been thinking about that too, actually.  I'll take care of it this coming weekend.
As for 0.6.1 vs 0.7.0 , for some reason 0.7.0 feels more right to me, but I have zero actual rationale for that.  In the end, I don't really care one way or the other, and I suspect doesn't really matter that much...?  If anyone feels strongly one way or the other, let me know.  Otherwise I'll probably just do 0.7.0.

Done!
0.7.0 is live on crates.io


att method of BaseSynth is not recognised on Synth object

When trying to replicate the 'germany' example, I get the following error:
Traceback (most recent call last):
  File "/Users/<...>/test/german_reunification_example.py", line 89, in <module>
    print(synth.att(time_period=range(1990, 2004)))
AttributeError: 'Synth' object has no attribute 'att'

The example I ran was exactly the one you provided, but as a python script.
For completion ...
import pandas as pd
from pysyncon import Dataprep, Synth

df = pd.read_csv("german_reunification.csv")

dataprep_train = Dataprep(
    foo=df,
    predictors=["gdp", "trade", "infrate"],
    predictors_op="mean",
    time_predictors_prior=range(1971, 1981),
    special_predictors=[
        ("industry", range(1971, 1981), "mean"),
        ("schooling", [1970, 1975], "mean"),
        ("invest70", [1980], "mean"),
    ],
    dependent="gdp",
    unit_variable="country",
    time_variable="year",
    treatment_identifier="West Germany",
    controls_identifier=[
        "USA",
        "UK",
        "Austria",
        "Belgium",
        "Denmark",
        "France",
        "Italy",
        "Netherlands",
        "Norway",
        "Switzerland",
        "Japan",
        "Greece",
        "Portugal",
        "Spain",
        "Australia",
        "New Zealand",
    ],
    time_optimize_ssr=range(1981, 1991),
)

synth_train = Synth()
synth_train.fit(dataprep=dataprep_train)

dataprep = Dataprep(
    foo=df,
    predictors=["gdp", "trade", "infrate"],
    predictors_op="mean",
    time_predictors_prior=range(1981, 1991),
    special_predictors=[
        ("industry", range(1981, 1991), "mean"),
        ("schooling", [1980, 1985], "mean"),
        ("invest80", [1980], "mean"),
    ],
    dependent="gdp",
    unit_variable="country",
    time_variable="year",
    treatment_identifier="West Germany",
    controls_identifier=[
        "USA",
        "UK",
        "Austria",
        "Belgium",
        "Denmark",
        "France",
        "Italy",
        "Netherlands",
        "Norway",
        "Switzerland",
        "Japan",
        "Greece",
        "Portugal",
        "Spain",
        "Australia",
        "New Zealand",
    ],
    time_optimize_ssr=range(1960, 1990),
)

synth = Synth()
synth.fit(dataprep=dataprep, custom_V=synth_train.V)

print(synth.weights())

synth.path_plot(time_period=range(1960, 2004), treatment_time=1990)
synth.gaps_plot(time_period=range(1960, 2004), treatment_time=1990)
print(synth.att(time_period=range(1990, 2004)))
print(synth.summary())

This is published now to PyPI as @v1.2.0
Run python -m pip install pysyncon==1.2.0 to get it.

Thanks, this worked.
On Tue, Jan 30, 2024 at 2:30 PM Stiofáin Fordham @.***>
wrote:

This is published now to PyPI as @v1.2.0
https://github.com/sdfordham/pysyncon/releases/tag/v1.2.0
Run python -m pip install pysyncon==1.2.0 to get it.
—
Reply to this email directly, view it on GitHub
https://github.com/sdfordham/pysyncon/issues/38#issuecomment-1916998445,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWWG6XPICKGUM2KKCQH53TYRD7X3AVCNFSM6AAAAABCLM5TVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJWHE4TQNBUGU
.
You are receiving this because you authored the thread.Message ID:
@.***>


Release based on version in tag name

Your checklist for this pull request

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side) and not your master branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[ ] Link to relevant issues in GitHub or in Jenkins JIRA
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Did you provide a test-case? That demonstrates feature works or fixes the issue.

Shouldn't we also change the other workflow in this PR to build on every pull request?


Change name of OpenFOAM module to ExtInflow

This PR is ready to merge, but should not be merged until the FSI PR is ready for merging (this will be marked as draft until that PR is ready).
Feature or improvement description
Many years ago, OpenFAST was linked to SOWFA through the code OpenFOAM.  The module in OpenFAST that linked to OpenFOAM was also called OpenFOAM.
However, now multiple CFD codes, including SOWFA, NALU-Wind, and AMR-Wind, provide wind information to OpenFAST.  Thus the OpenFOAM module name no longer makes sense as the OpenFOAM software package is not the only code used.  So the OpenFOAM module in OpenFAST is changing names to the  more descriptive name of ExtInflow.
Related issue, if one exists
None
Impacted areas of the software
The CFD codes that use OpenFAST will need to change the names of the routines they call.
Additional supporting information
Module short name changed from OpFM to ExInf (this is only used within the OpenFAST code).
Test results, if applicable
No test results change, but the input files have a minor change for the CompInflow line.

Cancelling this PR as dev has changed too much.


Shoud OpenMetrics be compatible with or consider dropwizard metrics?

Dropwizard metrics format is diffrent from prometheus metrics. And now, dropwizard metrics is widely used in in the field of big data, like Hadoop，Kafka，Spark，JStorm.Shoud OpenMetrics be compatible with or consider dropwizard metrics?

Wrong repo, answered elsewhere.


build fails on Java 9+ (sbt-jdi-tools isn't compatible)

f9c534f93c630f21cff4dee03cb96e77e01364a8 added addSbtPlugin("org.scala-debugger" % "sbt-jdi-tools" % "1.0.0") but this breaks the build (as in, you can't even start sbt) on Java 9 and 10, because of https://github.com/chipsenkbeil/sbt-jdi-tools/issues/5
yes, Scalameta is normally built on Java 8, but we want to build it on Java 9 and 10 as part of the Scala community build. or at least, we want the build definition to be loadable, so we can use the same project list regardless of JDK version

@xeno-by I've submitted https://github.com/chipsenkbeil/sbt-jdi-tools/pull/6 which should fix sbt-jdi-tools, but that repo isn't set up to cross-publish for sbt 0.x and 1.x, only 1.x.
is there anything blocking you from upgrading this repo to sbt 1.x?

is there anything blocking you from upgrading this repo to sbt 1.x?

I submitted https://github.com/scalameta/scalameta/pull/1720 on this, but it will need some additional work before it can be merged.

if the sbt 1 upgrade stalls out, and/or if my sbt-jdi-tools PR stalls out, another path forward would be to remove the binary dependency on sbt-jdi-tools and instead, copy the plugin's one source file (with my fix) into your project directory and call it good

We can backport your fix, @SethTisue, to the plugin's 1.0 release or update the plugin to cross-compile for 0.13.x and 1.x. I've not done sbt plugin cross-compiling myself, though.

@chipsenkbeil thanks Chip!!

Thank you everyone! 🤝

Just finished signing, publishing, and releasing versions 1.0.1 (for sbt 0.13.x) and 1.1.1 (for sbt 1.x) of the plugin. Once Maven Central gets the resources in order, feel free to give it a try and see if it helps.

PR: https://github.com/scalameta/scalameta/pull/1732


Screen information not available from WSL (need monitor EDID from Windows host).

Environment
Windows build number: 10.0.22000.258
Your Distribution version: Ubuntu 20.04
Your WSLg version: 1.0.28

Steps to reproduce
Using Qt 5.15.
Fetching the manufacter and model.
  auto screens = QApplication::screens( );
  for ( const auto& item : screens )
  {
    addItem( item->manufacturer( ) + " - " + item->model( ));
  }

Creating a screenshot.
    auto screen = data_->screen;
    auto map = screen->grabWindow( 0 );
    setPixmap( map );

WSL logs:
weston.log
pulseaudio.log
versions.txt
WSLg ( x86_64 ): 1.0.28+Branch.main.Sha.8b5993a2190de8954de59fbca93ff8b4ed5f8330
Mariner: VERSION="1.0.20210224"
FreeRDP: b05321cd4e6a862aef76163a69db4e1910245736
weston: 9a55de1bde7ad5a9774391d83ed3371a68370502
pulseaudio: 2f0f0b8c3872780f15e275fc12899f4564f01bd5
mesa:

Expected behavior
The application should look like this:

Actual behavior
Qt's QScreen API is not able to fetch information about the available screens. It is not able to screenshot any of the displays too.

@gaeqs, thanks for reporting the issue. Currently WSLg doesn't virtualize monitor and export EDID to WSL VM, thus application (including Qt) can't obtain monitor EDID via either X11 or Wayland. We can look into this future. Thanks!

For the benefit of future Googlers, I am leaving here some Python/PySide6 code which reproduces the problem (and can thus be used quickly to verify a potential fix). Here, the issue is that the QPixmap.isNull() is true on WSLg.
Install python with pip, run pip install PySide6-Essentials, then run this code:
"""Pixmap is NULL on WSLg."""
from PySide6.QtWidgets import QApplication, QMainWindow

class Window(QMainWindow):
    def __init__(self) -> None:
        super().__init__()
        self.show()
        print(self.screen())
        print(self.effectiveWinId())
        pixmap = self.screen().grabWindow(self.effectiveWinId())
        assert not pixmap.isNull()

application = QApplication()
window = Window()
application.exec()

1.5 years later, I have found out that there are two different, unrelated issues:

WSLg does not export monitor information to WSL VM, hence info such as EDID are not available in WSL
QScreen.grabWindow() is not implemented for Wayland, hence screens cannot be captured in Wayland, compare https://bugreports.qt.io/browse/QTBUG-34976. My (now hidden) repro code in https://github.com/microsoft/wslg/issues/511#issuecomment-1427569799 concerns that issue.

Now, if you run WSL using Wayland, you will encounter both issues, but the necessarily resolutions are distinctly different. In particular, issue 2 cannot be fixed by WSLg and needs to be fixed by Qt.

As a workaround for issue 2, try using X11 by setting QT_QPA_PLATFORM=xcb- that should enable screenshots at least.


Stack overflow tests don't work on the main thread on Windows

This past Friday some tests were done on CI - https://github.com/bytecodealliance/wasmtime/pull/3853 - to figure out what was going wrong and the culprit ended up being the stack overflow tests on Windows. Our testing efforts were thwarted by the fact that if the test harness is run with --test-threads 1 then stack overflow tests will all legitimately stack overflow on Windows, presumably because we're by default giving too much stack space to WebAssembly.
This can be reproduced locally on Windows with:
$ cargo test --test all -- --test-threads 1

The best fix for this is likely to decrease the default amount of stack given to WebAssembly (specified here), perhaps only on Windows.

I'm performing a test run at https://github.com/alexcrichton/wasmtime/actions/runs/1911049688 to see what happens when we limit the stack size of wasm for the entire test suite, and then run the tests on windows with --test-threads 1

Learnings so far:

According to https://github.com/alexcrichton/wasmtime/runs/5361838714?check_suite_focus=true the test suite works as-is (as of b57dc5e3346747824dcb512cc99f94c14763cbab) with 64k to 256k, of wasm stack.

At 512k and above of wasm stack this test fails as the host tries to probe that it has 512k of stack.
At 16-32k of wasm stack this test fails because it's intermingling host/wasm stack and the wasm stack's allocation starts at the first recursive call, it's not per-call.
At 8k and below of wasm stack we start seeing lots of various failures in the test suite

According to https://github.com/alexcrichton/wasmtime/runs/5361992788?check_suite_focus=true if we probe for 128k bytes of stack in this test then the test suite passes with 512k of wasm stack.


Version selector overlap

Noticed that when selecting the v0.37-rc2 version on the version selector dropdown, the version text overlaps with the down arrow

Browser: Firefox
OS: Ubuntu

Noticed this on Firefox (Linux Fedora)

This got fixed somewhere along the way.


update stm32g0 SVD ZIP to v1.4

This should fix, among other things, the missing peripherals on g0b0.
(This PR is a draft because I expect some conflicts with the patches in this repository.)

Please, don't use _replace_enum here.
Better remove all enums with
_clear_fields: ["*"]

Please, don't use _replace_enum here.

Sure thing; may I ask you to be more specific? Are you referring to the patches under peripherals/, those directly under devices/, those under devices/common_patches/, or all three?

Replaced by #947


Propagate program and team in SNS and SQS messages

This PR adds check metadata (program-team) to SQS and SNS messages in order to be able to correlate metrics related to tenants in different Vulcan components.

Hi @danfaizer , I reviewed the PR.
My concern is more about the approach than the implementation itself.
I see we are propagating a new parameter program-team to the Agent, that parameter is built in persistence based on the scan program name and the teams tag, but for me that parameter is very specific to the metrics tag. Is true that at the moment we will use it for that, but shouldn't we propagate something more generic in the same way we have been propagating the data from API - scan engine - persistence, for example passing two parameters, one for the program and one for the team's tag? And then from the Agent we can build whatever tag or whatever combination we want for any use case we want.
What do yo think?

Totally agree @ka3de.
I will add metadata field and this will contain a key:value structure so we can provide whichever information in this format.
In the vulcan-agent side we will look for team and program values in our specific case.
Does this sounds OK to you?


Doc: Need better documentation for bootstrap C and Rust projects.

Description
Seeing that we now have a CLI binary, users and developers could have a easy use case on zkwasm. The current docments is a design document than a getting started or quick introduction We may give a better and clean README.md for people to be interested in our projects.

@aseaday I was trying to look around for something like this, so I could explore the project. currently having a hard time understanding some possibly basic things:

how is the bsearch.c file currently compiled?
how would I go about using rust code instead of C? I'm getting some errors when trying to use something compiled via wasm_bindgen

We now have zkWASM-C repo as a project template: https://github.com/DelphinusLab/zkWasm-C. rust to zkWASM problem is solved in  #69. Will leave this thread to track the progress of documentation.

We now have two more demo projects:
Rust project demo: https://github.com/xgaozoyoe/zkWasm-Rust-Demo
Assembly script demo: https://github.com/DelphinusLab/zkWasm-AssemblyScript-Demo

@xgaozoyoe I'm still not sure how to read input in rust? Basically how do I call wasm_input?
This is not shown in the rust demo, could you help me?

@KuTuGu here's an example:
extern "C" {
    fn wasm_input(x: i32) -> i64;
}

#[wasm_bindgen]
pub fn add() -> i64 {
    let x = unsafe { wasm_input(1) };
    let y = 5;

    x + y
}


esbuild error with this package

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?
Sentry Saas (sentry.io)
SDK Version
7.61.1
Link to Sentry event
No response
What environment is your node script running in?
aws lambda node16.x
How is your code deployed and bundled?
esbuild
Steps to Reproduce
lambda includes sentry dependencies
"dependencies": {
"@sentry/node": "^7.61.1",
"@sentry/profiling-node": "^1.1.2",
"@sentry/serverless": "^7.61.1"
}
we run npm install then esbuild using the AWS SAM cloudformation setup as follows
Metadata:
BuildMethod: esbuild
BuildProperties:
Minify: true
Target: "es2020"
Sourcemap: true
EntryPoints:
- index.js
Expected Result
a bundle is produced that I can deploy to AWS cloud
Actual Result
Build fails with:
Error: NodejsNpmEsbuildBuilder:EsbuildBundle - Esbuild Failed: ✘ [ERROR] No loader is configured for ".node" files<EMAIL_ADDRESS>This is probably the same issue as https://github.com/getsentry/profiling-node/issues/170 but since that was for Next.js and this is for esbuild I didnt want to cause any confusion.

esbuild doesn't know how to process a .node file, you need to configure the appropriate loader. The copy loader will ensure the binary is copied to your dist and it's path is properly referenced.
loader: {
    // ensures .node binaries are copied to ./dist
    '.node': 'copy',
  },

Let me know if that doesn't work, there is a full bundling how-to in the readme.md


[4.2] [ConstraintSystem] Allow LValues for the bindings of an IUO @optional…

… requirement.
We were failing to bind the alternatives for an IUO @optional
requirement because we forgot to set the appropriate type variable option.
Fixes: rdar://problem/40868990
(cherry picked from commit 803fbee0dd4a0c80fa2c26b59d0cb9ad13bacefe)

@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 3c47c29200960af059531338a2a529ca004c4af6

@swift-ci Please smoke test OS X platform

@swift-ci Please smoke test OS X platform

@swift-ci Please test


Test visibility by role

This shows event managers if test is hidden from teachers, and hides those tests from teachers and students.
Also makes sure that adding student to hiddenFromRoles and visibleToStudent being true do the same thing. We assume that if a test is hidden from teachers, then it is also hidden from students to make the logic easier.

Ah, I think I am happy enough on reflection to just go with the generified versions because as you say they can then be used for other cases where we care about the role of a user that isn't the currently logged in user.


Use a Local Launch Page

Tutorials: https://developers.sap.com/tutorials/btp-app-launchpage.html
In step 3, I don't understand why the first answer of the quiz is correct.
The note before tells me that cds watch would replace the default page if the file name is index.html. That's we choose launchpage.html here, to create an additional individual page (right?).
The problem with the first answer may be that readers don't know what "it" refers to, launchpage.html or index.html. My point is that by choosing launchpage.html we in fact prevent that the default page is replaced, so the first answer didn't seem right to me.
A possible answer could be: "To avoid that cds watch replaces the default page".

Hi @je-hal,
Agreed that it's confusing, I'll improve it.
Best regards,
Maha

this tutorial has been removed so, I'll close this issue.


Tests and code formatting

Added tests for all function except these -
TEST_ATTRIBUTES - replace_attributes
TEST_DESCRIPTION - replace_descriptions, process_description
TEST CLEANER - remove_unused_lessons, rename_dirs, move_content
TEST_TEXT_PROCESSOR - process_text -> IndexError: list index out of range
In the last case the function return index error. I investigated it little bit but I don't find out anything. In rest of the cases I don't know how to test it.
I also added formatting and xml that contain exercise data.

Already cherry-picked and deployed :+1:


Update README.md

Thanks for catching that typo @unmeimusu!

you're welcome
On Sun, Apr 30, 2023 at 11:08 AM Rahim Alwer @.***>
wrote:

Thanks for catching that typo @unmeimusu https://github.com/unmeimusu!
—
Reply to this email directly, view it on GitHub
https://github.com/maverick-js/maverick/pull/3#issuecomment-1528934151,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK6RHV6XLT6EUY2ZTKG3WHLXDXQSRANCNFSM6AAAAAAXO55CX4
.
You are receiving this because you were mentioned.Message ID:
@.***>


Can this work with binaries written in Swift?

+------------------------+
| Describe Your Question |
+------------------------+
Hello! Awesome work on this tool first off. I was testing it and it works great with binaries written in C and ObjC but I haven't been able to get it working with Swift binaries. I played around with it a bit and thought maybe it was some error calculating offsets with Swift binaries but I manually ran the Ruby commands and saw the offset was correct. Maybe some funkiness with Swift shellcode? Wondering if you had some insight!

I have made some updates.
I tried a simple Swift macho just now, and it worked.

Hey @usiegl00, were the updates pushed to the main branch? I don't see any recent updates. Made sure I had the latest commit but it still didn't appear to work. For reference, I'm using a simple Swift binary that just prints "Hello from Swift!"

Hmm, what version of Mac OS are you using?

 (This project does not support ARM right now.)

I'm not on an M1 :/ just a normal Intel Core

What macOS version are you on?

Catalina. Could you send me the swift code you are using to test?

Yep, it's a very basic program.
//
//  main.swift
//  SwiftHelloWorldBasic
//
//  Created by Justin Bui on 11/18/21.
//
import Foundation
NSLog("Hello, World!")

I was not able to replicate this issue on Big Sur. (11.2)
Following the build steps (here)[https://www.swift.org/getting-started/#building-an-executable].
Both print and NSLog worked normally.
Could you send me your "tamatoa.bin" and "macho.s" so that I can take a look at the generated files?
If you are using any specific swift build flags, could you post them here as well?

Interesting, I was able to get it to build a basic Swift binary following the steps you mentioned. I wonder what XCode is doing that makes the executable format slightly different.

So I've done a good amount of testing with Swift and tamatoa and wanted to share my results:

print("Hello World") compiled with swiftc ✅
NSLog("Hello World") compiled with swiftc ❌
print("Hello World") compiled with Xcode ❌
NSLog("Hello World") compiled with Xcode ❌
print("Hello World") compiled according to https://www.swift.org/getting-started/#building-an-executable ✅
NSLog("Hello World") compiled according to https://www.swift.org/getting-started/#building-an-executable ✅
More complex Swift program (https://github.com/slyd0g/SwiftLiverpool) compiled with Xcode ✅

Not sure if that helps at all, but just wanted to share incase other people were looking into this 😬

It might be related to some build flags that are being set by Xcode and swiftc.
Can you check what build command Xcode is running?

This is from the "Compile Swift source files" section in Xcode:
CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler (in target 'SwiftHelloWorldBasic' from project 'SwiftHelloWorldBasic')     cd /Users/slyd0g/Projects/SwiftHelloWorldBasic     export DEVELOPER_DIR\=/Applications/Xcode.app/Contents/Developer     export SDKROOT\=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk     /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -incremental -module-name SwiftHelloWorldBasic -Onone -enable-batch-mode -enforce-exclusivity\=checked @/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/Objects-normal/x86_64/SwiftHelloWorldBasic.SwiftFileList -DDEBUG -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk -target x86_64-apple-macos11.3 -g -module-cache-path /Users/slyd0g/Library/Developer/Xcode/DerivedData/ModuleCache.noindex -Xfrontend -serialize-debugging-options -enable-testing -index-store-path /Users/slyd0g/Library/Developer/Xcode/DerivedData/SwiftHelloWorldBasic-eseejzupwjyervgiunwndspktfpu/Index/DataStore -swift-version 5 -I /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/Debug -F /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/Debug -c -j16 -output-file-map /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/Objects-normal/x86_64/SwiftHelloWorldBasic-OutputFileMap.json -parseable-output -serialize-diagnostics -emit-dependencies -emit-module -emit-module-path /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/Objects-normal/x86_64/SwiftHelloWorldBasic.swiftmodule -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/swift-overrides.hmap -Xcc -iquote -Xcc /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/SwiftHelloWorldBasic-generated-files.hmap -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/SwiftHelloWorldBasic-own-target-headers.hmap -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/SwiftHelloWorldBasic-all-target-headers.hmap -Xcc -iquote -Xcc /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/SwiftHelloWorldBasic-project-headers.hmap -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/Debug/include -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/DerivedSources-normal/x86_64 -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/DerivedSources/x86_64 -Xcc -I/Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/DerivedSources -Xcc -DDEBUG\=1 -emit-objc-header -emit-objc-header-path /Users/slyd0g/Projects/SwiftHelloWorldBasic/build/SwiftHelloWorldBasic.build/Debug/SwiftHelloWorldBasic.build/Objects-normal/x86_64/SwiftHelloWorldBasic-Swift.h -working-directory /Users/slyd0g/Projects/SwiftHelloWorldBasic

Okay, then compare that with running swift build -v.

slyd0g@Justins-MacBook-Pro~/Projects/SwiftHelloWorldCLIBuild$ swift build -v
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/usr/bin/xcrun --sdk macosx --find xctest
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
Planning build
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -print-target-info
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/4_2/libPackageDescription.dylib
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swiftc -L /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/4_2 -lPackageDescription -Xlinker -rpath -Xlinker /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/4_2 -target x86_64-apple-macosx10.15 -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk -F /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks -I /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib -L /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/usr/lib -swift-version 5 -I /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/pm/4_2 -sdk /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.3.sdk -package-description-version 5.3.0 /Users/slyd0g/Projects/SwiftHelloWorldCLIBuild/Package.swift -o /var/folders/kc/jc64g3ss3n529s1r3d44b0tw0000gn/T/TemporaryDirectory.62lifh/swifthelloworldclibuild-manifest
/usr/bin/sandbox-exec -p '(version 1)
(deny default)
(import "system.sb")
(allow file-read*)
(allow process*)
' /var/folders/kc/jc64g3ss3n529s1r3d44b0tw0000gn/T/TemporaryDirectory.62lifh/swifthelloworldclibuild-manifest -fileno 6
/usr/bin/xcrun --sdk macosx --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk iphoneos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk appletvos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/AppleTVOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest
/usr/bin/xcrun --sdk watchos --show-sdk-platform-path
/usr/bin/xcrun vtool -show-build /Applications/Xcode.app/Contents/Developer/Platforms/WatchOS.platform/Developer/Library/Frameworks/XCTest.framework/XCTest

Try adding the flag: -enable-objc-interop

Sorry, I'm not the quickest with Xcode settings but it appears this might be a similar setting?

What lead you to believe that was the difference? I didn't see that within the swift build output.

It was in my swift build output, but not in your Xcode output.
Did it work?

It didn't unfortunately, the setting was already enabled. I'll look into how to add that exact CLI argument in Xcode and let you know.

It appears that CLI argument doesn't exist on my version of swiftc

It's particularly odd because I was able to compile this project in Xcode and get it working with tamatoa https://github.com/slyd0g/SwiftLiverpool

Are there any Xcode build config differences between SwiftLiverpool and SwiftHelloWorldBasic?

Not to my knowledge, I didn't modify any particular settings for either projects.

It might have to do with the executable size...
Try removing the strip commands from the Makefile.

Removed the strips under the tamatoa: section. Still no luck unfortunately, I can give you all the source code if that makes it easier. SwiftHelloWorldBasic fails, but SwiftLiverpool still works.

It's honestly not too big of a deal, I've tried a couple other Swift projects also compiled with Xcode and they work fine. I'm just confused as to why a simple Hello World in Xcode does not.

So am I.

I'll let you know projects that work and projects that don't as I continue testing and maybe we can narrow something down. Thank you again for your work on this project, it's really awesome and very useful :)

The other case that particularly stumped me was NSLog compiled with swiftc. The same exact program with print works just fine:

This is very strange...
That exact series of commands works for me on Big Sur.
Do you have a computer that you can borrow to run the same test on?
The errors could be specific to your device.

It works about half the time in lldb.

Okay, tamatoa is running the swift code at the correct entrypoint.
However I believe the garbage collector is causing the program to crash every other time.
Maybe we can change the mmap flags?
Right now they are MAP_EXECUTABLE and MAP_PRIVATE.

The garbage collection is removing the memory that argv points to.
This memory is being accessed later by NSLog.
There must be a way that we can allocate a new page for the args and copy them over.

Even after correcting argv and argc, swiftc still fails around half the time.

Yeah very odd, I wonder if it's just an issue with "smaller" programs that causes this race condition. I'm consistently able to get more complex Swift programs to work.

I have added a Wiki page recommending the use of swift build instead of swiftc or Xcode.

Ah awesome :) you can consider this closed then. Appreciate you looking into that!

I've made some changes and have been unable to trigger the crash.
Do you want to take another look at replicating this issue?

I've made a note to test the cmdline argument patching + this fix, will take a look as soon as I can and let you know!

I re-tested with some binaries that didn't work previously and it seems they work consistently now! :)
Awesome work


fix: typo and expired link

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I've agreed with the maintainers that I can plan this task.

Description
There are many expired links and typos for example
https://github.com/autowarefoundation/autoware.universe/pull/2216
Purpose
To eliminate typos and expired link to pass CI test
Possible approaches
Fix readme and codes.
Definition of done
pre-commit optional and spell check
https://github.com/autowarefoundation/autoware.universe/actions/workflows/pre-commit-optional.yaml
https://github.com/autowarefoundation/autoware.universe/actions/workflows/spell-check-differential.yaml

I started to fix links in #2842!

I found that pre-commit-optional is failed when no link errors are occured.
https://github.com/autowarefoundation/autoware.universe/pull/2842#issuecomment-1422356593
So, we need to debug and fix in another PR.

@HansRobo @taikitanaka3 Do you still have other action items for this issue?

@HansRobo
I think this is done. how about you.


Autofix PLW0108 unnecessary-lambda (preview)

It would be great to add an autofix to https://github.com/astral-sh/ruff/pull/7953 as it's fix is pretty straightforward (just deleting the lambda and calling the function / method directly). The logic / autofix is somewhat similar to PIE807 which already has an autofix.

At the very least, the cases where the lambda takes no arguments should be trivial to fix.


Support standard stream

Similar to the Node.js module codecov, would be useful if the bash script accepted a coverage report from stdin; e.g.,
$ cat ./lcov.info | bash <(curl -s https://codecov.io/bash) -F test

This would allow support for pipelining without the need to write to disk in order to upload.

Hey @kgryte thank you for the feature suggestion. I do not know of a way to have both these options work without locking stdin on the first call below:
bash <(curl -s https://codecov.io/bash)

-vs-

echo "<report data>" | bash <(curl -s https://codecov.io/bash)

All my attempts to read /dev/stdin have locked the IO waiting for content to be written to stdin. My research into this has not resolved well... :(


Note limitation about OAuth client types

OAuth developers expect to be able to specify client type during OAuth registration, so it's worthwhile to note this limitation.
Check off the following:

[x] I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Thanks for the PR @hickford, I'll get this triaged for review as well.

@github/ecosystem-apps-reviewers Could you review this from a technical standpoint?

I'd like to not include this. We are updating docs to add nuance here, but I don't want to say that we assume all are confidential. That's not quite true and we're adding additional logic now that distances us even further.


[Feature] Change contribution guide

Checklist

[ ] 1. If the issue you raised is not a feature but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.
[ ] 2. Please use English, otherwise it will be closed.

Motivation
https://sgl-project.github.io/references/contributor_guide.html
This has been outdated for long. We need to add guide on:

How to run docs CI, build it locally, compile it and clean the output and make PR.
How to do unit tests locally and add unit tests to CI.
How to write elegant unit test following other tests.
How to pre-commit.

Related resources
No response

@shuaills This is a great issue to you 😂

@shuaills Set up environments for beginner who even never use GPU.


Implementing haystack

Discussed on yesterday's meeting and can be considered after the barcamp in april.

See also #54 and #101


require globs are not expanded

Looks like glob expansion that protractor did for us is missing for the require option. I did it manually in my conf file, but it would be nice if this could be brought back.
before:
    cucumberOpts: {
      format: ['json:build/test-results/protractor.json', 'pretty'],
      require: ['features/step_definitions/**/*.js', 'features/support/**/*.js']
    },

after:
    cucumberOpts: {
      format: ['json:build/test-results/protractor.json', 'pretty'],
      require: glob.sync('features/step_definitions/**/*.js').concat(glob.sync('features/support/**/*.js'))
    },

Yep. Due to #1 I will look at ASAP

Fixed in https://github.com/mattfritz/protractor-cucumber-framework/commit/23bd1ba53b671215aa04e8abc7a81fb7c07a24ec
Thanks for the heads up @darrinholst


feat(forge): filter through artifacts on invariant testing

Motivation
The ability to filter addresses/functions through their artifacts, instead of just their addresses.
Solution
function targetArtifacts() returns (string[] memory) // ["Contract1","src/Contract2.sol:Contract2"]
function excludeArtifacts() returns (string[] memory) // ["Contract1","src/Contract2.sol:Contract2"]
function targetArtifactSelectors() returns (string, bytes4[])[] memory) // [("Contract1", [Contract1.hello.selector])]

This touches both the addresses coming from the setUp(), as well as any contract generated through a run (testdata/fuzz/invariant/targetAbi/TargetArtifactSelectors2.t.sol).
Priorities when clashing:
targetSelectors | targetArtifactSelectors > excludeContracts | excludeArtifacts > targetContracts | targetArtifacts

lgtm, merge wen ready

great, just need to fix some issue introduced on 13813f4


Feature request: Offer an alternative to setData for the composition API

Is your feature request related to a problem? Please describe.

I haven't found a way to set a component's internal variables to the values I need.
This is in order to properly test it.
I found something close to it here: https://test-utils.vuejs.org/api/#setdata but it comes with a note that says:
Also, notice that setData does not modify composition API setup() data.
But it does not link to an alternative for composition API. So I assume it does not exist. :thinking:
Describe the solution you'd like

It would be great to have a way to change a component's internal variables to properly test them.
Describe alternatives you've considered
Unfortunately, I don't have any. :(
Additional context
Just starting with test-utils :pray:

I would only rely on internal variables if there is no better way. The component should be a closed scope and you should only test the user facing side (input events, etc.).
To modify the variables (which must be returned from setup) you can do:
wrapper.vm.myVar = 1
await nextTick()

Alright, thanks for the advice and for the answer!

And I think you meant:
await wrapper.vm.$nextTick()

Right?

Yes, or you can import it from vue


Referring to View created in DSL

I am trying to test my layout written in Anko DSL with the use of Robolectric, but I am struggling at the very beginning. I can't find any way to refer to any of the views within my layout. This is a simple activity layout created with the use of AnkoComponent.
After doing some web research I found that it is possible in the following way:
@RunWith(RobolectricGradleTestRunner::class)
@Config(constants = BuildConfig::class)
class ExampleRobolectricTest {

    @Test
    fun itShouldDisplayHelloWorld() {
        val activity = Robolectric.setupActivity(MainActivity::class.java)
        val textView = activity.findViewById(R.id.main_text) as TextView

        assertThat(textView.text).isEqualTo("Hello World!")
    }
}

The problem is, in order to do that I would have to have an xml for this layout, but I don't want to do this that way.
So is there any other way to add an id to specific view? Or maybe there is some other way of referring to it?

You can use View.generateViewId() to create unique ids.
https://github.com/fboldog/AnkoMaterialSamples/blob/master/src/main/kotlin/com/ferencboldog/ankomaterial/extensions/AnkoViewCompat.kt
After this, you can use this ids in your test code, like this:
val list = activity.find(ReferenceToYour.VIEW_ID)
or this: https://github.com/fboldog/AnkoMaterialSamples/blob/master/src/main/kotlin/com/ferencboldog/ankomaterial/launcher/ui/LauncherComponent.kt
FYI: if you would like test android-23 targets, you need build roboelectric from source and if you run similar error:
e: /Volumes/REPOS/own/AnkoMaterialSamples/src/test/kotlin/com/ferencboldog/ankomaterial/ExampleRobolectricTest.kt: (28, 9): org.jetbrains.kotlin.codegen.CompilationException: Back-end (JVM) Internal error: Error type encountered: ('[ERROR : Unresolved java classifier: Path]'..'[ERROR : Unresolved java classifier: Path]?') (DelegatingFlexibleType).
Cause: Error type encountered: ('[ERROR : Unresolved java classifier: Path]'..'[ERROR : Unresolved java classifier: Path]?') (DelegatingFlexibleType).
File being compiled and position: (28,9) in /Volumes/REPOS/own/AnkoMaterialSamples/src/test/kotlin/com/ferencboldog/ankomaterial/ExampleRobolectricTest.kt
PsiElement: assertThat(list)
The root cause was thrown at: JetTypeMapper.java:436

change your kotlin version to 1.0.2-eap-15 or newer (maven repository: https://dl.bintray.com/kotlin/kotlin-eap)
I will publish working roboelectric test code to AnkoMaterialSamples later today.

What about extracting the view DSL into AnkoComponent and using it inside your tests?


Options for cooperation with django-stubs

Hi! I'm one of the maintainers of the django-stubs project.
I sense that there is significant duplication of effort between django-stubs and django-types. Our pace of development has picked up recently, but still we're struggling to cover the Django API surface. If we joined forces, we could get more done.
If you're open to that, we need an understanding about the differences between the projects, here's what I'm aware of:

I think the initial reason for forking was that django-stubs requried mypy? As of django-stubs version 4.2.6, mypy is no longer a required dependency.
django-stubs relies on our mypy plugin magic for inferring Models/QuerySets. django-types instead documents how users should annotate Django's magic attributes on Model classes.
There are differences in how mypy and pyright interpret type stubs. Hopefully not mutually incompatible, other projects (e.g. typeshed) work fine with multiple type checkers. We have already seen some contributions from pyright users.
Discussion #147 points out that django-stubs uses _pyi_private_... attributes in Model fields for our magic. I wouldn't think their existence interferes when using pyright though?

(1) is solved and the rest don't look insurmountable.
Some relevant discussion:

https://github.com/sbdchd/django-types/discussions/147

Ping @sobolevn for visibility.

I found this in Django wiki (GSoC 2023): https://code.djangoproject.com/wiki/SummerOfCode2023#Mergingdjango-typesbackintodjango-stubs
I'm wondering if you agree with this characterisation:

There is a spin-off project from django-stubs called django-types. The original intention here was for it to be merged back into django-stubs, but that's never happened.
django-types removes the need to use any mypy plugins, making it possible to use type checkers other than mypy, such as Pyrite, Pyre, etc.
django-types is not actively maintained, however, and having competing stubs implementations means neither is as strong as could be.
There is a small project in extracting the work from django-types and creating a PR for django-stubs allowing it to be merged back in, and effort to be concentrated on the single implementation.

Here's also a description about django-stubs/django-types differences:

https://github.com/typeddjango/django-stubs/issues/579#issuecomment-950200788

I found this in Django wiki (GSoC 2023): https://code.djangoproject.com/wiki/SummerOfCode2023#Mergingdjango-typesbackintodjango-stubs
I'm wondering if you agree with this characterisation:

There is a spin-off project from django-stubs called django-types. The original intention here was for it to be merged back into django-stubs, but that's never happened.
django-types removes the need to use any mypy plugins, making it possible to use type checkers other than mypy, such as Pyrite, Pyre, etc.
django-types is not actively maintained, however, and having competing stubs implementations means neither is as strong as could be.
There is a small project in extracting the work from django-types and creating a PR for django-stubs allowing it to be merged back in, and effort to be concentrated on the single implementation.

Tbh it was a while ago but I think the original intention was to get autocomplete to work in VSCode to make my job (and coworkers) working in the Django codebase easier. I was cool with maintaining the project solo since we didn’t use that many Django features, a small surface area. I think we only used Django as a JSON API so the admin and related tools weren’t that important.
So once the models and query sets were working I considered the project good enough and would occasionally add some more types if autocomplete wasn’t working in some cases.
Ideally I was hoping for Django to incorporate types but I think they said no a while back.
I no longer work for that company or work in Django regularly so this project is more of a, “whenever I check GitHub and have the time to merge a PR”
I’m open to merging the projects, I think there would need to be parity since people are using this project as a dependency

Edit: forgot that you could set Model().article = <a_pk>, hence the need for the two type vars :/

Which can be practically worked around by setting article_id instead. Still, typing the same thing twice is a tad verbose.

That's right, it's Unknown in Pyright when I try to directly reference it.

The same code when not using django-stubs and only using django-types:

This means that with django-stubs, I only get type-safety for the first level of accessing attributes - if I did fx_rate.foo, that would be an error. But I don't get type-safety beyond that - I can do fx_rate.company.foo without any errors, while django-types catches that.

That's exactly the point of this issue: to make django-stubs and pyright compatible.

Yep. I have looked into the tricks that django-types uses to get better type inference for model fields without the plugin. It should be possible to achieve the same results one way or another, without degrading experience with mypy. But I haven't had the time to continue with that work.

@sobolevn, I was clarifying since @Viicos's message implied that one would need to manually annotate even with django-types, which is not the case (at least in Pyright, I'm not sure about Mypy).

@tylerlaprade Thanks for the clarification. Both mypy and pyright should support the provided snippet with django-types. But this only works when using a direct reference to the model (instead of the string version {app_label}.{model_name}/{model_name}).
Actually django-stubs could support this use case as well by defining:
class ForeignKey(ForeignObject[_ST, _GT]):
    # As an extra overload:
    def __init__(
        self,
        to: type[_GT],
        ...
    )

But the set type can't really be parametrized this way, and this doesn't take into account nullability anyway.
FYI, I'm working on an alternative solution to support dango-stubs natively without plugins and without modifications to the actual type variables used. I will share more info soon.

I apologize for appearing in the middle of the discussion, but this might be related. I was recently searching for how to get type hinting for ForeignKey fields using string references in Vscode (which uses django-types), and I got some advice in this discussion.

Is there any reason for django-stubs to have both a distinct set and get type for forein keys & co?

Edit: forgot that you could set Model().article = <a_pk>, hence the need for the two type vars :/

After further investigation and looking at the descriptor implementation, you can't set the foreign field by it's primary key, so I don't think having two type vars for foreign fields is necessary? Or at least make both the set and get type the same typevar.
Or am I missing something?

FYI, I'm working on an alternative solution to support dango-stubs natively without plugins and without modifications to the actual type variables used. I will share more info soon.

You can find more info about this in the following article: https://viicos.github.io/posts/an-alternative-to-the-django-mypy-plugin/
django-autotyping is available here: https://github.com/Viicos/django-autotyping
Would love getting some feedback on this.

Yep. I have looked into the tricks that django-types uses to get better type inference for model fields without the plugin. It should be possible to achieve the same results one way or another, without degrading experience with mypy. But I haven't had the time to continue with that work.

I've been looking at this when implementing django-autotyping. I will come back here later with my findings on this subject.

@Viicos, interesting idea, but I don't understand why it's necessary. Pyright already knows the underlying type of a ForeignKey without any annotations when using django-types.

I don't understand why it's necessary

Well as I said here, it doesn't support string references to models, which are pretty common (I would even recommend using them over direct reference to the actual related class for different reasons). The article also explains a bit about this.
Apart from support for ForeignKey, the tool will support a lot of features from the mypy plugin:

Signature for model __init__: your IDE will actually show what are the available fields when typing MyModel(...
Signatures for queryset/manager methods (get, filter, create, etc). Here as well, you will get IDE support, with a custom signature for the current model being queried.

Ah I see, thanks for clarifying!


Accessibility Quiz Step 16

Describe the Issue
The wording here is awkward:

To the section elements, give the following aria-labelledby attributes:

Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-accessibility-by-building-a-quiz/step-16
Your code
N/A
Expected behavior
Simpler grammatical structure should be used in the curriculum:

Add the following aria-labelledby attributes to the section elements:

Screenshots
No response
System
All
Additional context
No response

Hate to hijack this issue, but while we are rewording this step, the first sentence needs some help as well. Ya, I know I'm being very picky here. We accessibility nerds are like that.

Every region role requires a visible label, which should be referenced by the aria-labelledby attribute.

Regions do not require a visible label. What they do require is an accessible name, which can be given by either aria-labelledby or aria-label. If there is an element on the page that can be used for the accessible name (such as a heading element inside the region) then definitely use aria-labelledby for the accessible name. If there is no appropriate element on the page then use aria-label.
My first shot at a rewrite.

Every region role requires a label, which helps screen reader users understand the purpose of the region. One method for adding a label is to add a heading element inside the region and then reference it with the aria-labelledby attribute.

Also, I think it might make more sense to rearrange the steps in the instructions to have them add the headings with ids first and then the aria-labelledby attributes on the divs. But I can live with the way it is now.

Sounds good to me.
Then, this issue is to change

Every region role requires a visible label, which should be referenced by the aria-labelledby attribute.

To the section elements, give the following aria-labelledby attributes:

into

Every region role requires a label, which helps screen reader users understand the purpose of the region. One method for adding a label is to add a heading element inside the region and then reference it with the aria-labelledby attribute.

Add the following aria-labelledby attributes to the section elements:

Alright, I am going ahead!


Update netlify's js-client and semver ranges

Update netlify's js-client and semver floors.

"@iarna/toml": "^2.2.3",
"netlify": "^2.4.0",
"@oclif/dev-cli": "^1.21.1",
"dependency-cruiser": "^4.13.2",

Coverage remained the same at 100.0% when pulling 0f637bbe713c96a82c39f19a9d9dd2071fcad5f6 on deps into 5507344ce781f2eba398df52da1c37d9fbaaeaad on master.


Move selection panel UI to new re_selection_panel crate

What
☝🏻
Chained to #6427
I made the following calls (along with @Wumpf):

Moved the SpaceViewStates to re_view_context (along with the space view class stuff).
Very partially renamed "space view" -> "view" for the stuff that I moved around.
Attempted to bring consistency to argument order in selection panel (ViewerContext -> ViewportBlueprint [-> ViewStates] -> egui::Ui -> other args).

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[x] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

deps graphs via cargo depgraph --all-deps --workspace-only --all-features --dedup-transitive-deps | dot -Tpng > deps.png
0.16:

now:

cargo clean && cargo build -p re_viewer --timings on M1
On this branch: 2m 29s
0.16: 2m 19s
slower unfortunately but this might be within the margin of error


DataTable selection filtered rows

This function solves the problem (这个功能解决的问题)
DataTable column type "selection" has options param which can check or uncheck row from ALL table, and you can create your own selection method on single active page.
But there's no way how to check filtered rows from all rest pages by an "selection" option.
Ofcourse it can be resolved by filtering "data" without  DataTable API, but if this native filters support exists why not extend it?
Expected API (期望的 API)
Make DataTable API return filtered rows/keys

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem

Yes, this would be very useful. Selecting all source data makes no sense for any usecase I can think of. By default 'all' should only select the filtered table data.


Add permission for android 8

In android 8 you need add a permission in plugin.xml

cordova-plugin-app-update

to worked fine  on smartphone.
I added directly into androidmanifest.xml and work well for myself.
<uses-permission android:name="android.permission.REQUEST_INSTALL_PACKAGES" />

Fixed #28


Crash when scanning EAN<PHONE_NUMBER>371

http://de.openfoodfacts.org/produkt/4039228005371/pizza-alla-california-veganz
i had added the product with the android app with just Quantity and one picture (i took 3 pictures but they overwrite the earlier :()

after i added more information on the website, scanning works again.

Version 0.2.3 installed from F-Droid

I can't reproduce the bug :/

Try the OBF version. Somebody reported the same bug. Just take pictures. Click send. rescan the product.

scan product
take picture
upload

here a barcode to reproduce:


Update ingress-demo.md

as the tutorial is outdated, some revisions are made!

Yes, these tutorials are old version, we are working on it, will update in a week.


Create readme in russian

It russian version of readme file.

Proposed changes
Summarize your changes here to communicate with the maintainers and make sure to put the link of that issue
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[ ] I have signed the commit for DCO to be passed.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have added necessary documentation (if appropriate)

Dependency

Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

The formatting and path of this README are both inappropriate. Also we are looking at native speakers to help us with the translations! Hope to receive other contributions we can take @vinayak017 ! Thanks for the attempt.


Required test upload mods release060

Issue #, if available:
Description of changes:
skip the upload of components override if it's not present
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


Update routes from interactive-sicp to sicpjs

Description

Type of change

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

How to test

Checklist

[x] I have tested this code
[ ] I have updated the documentation

Pull Request Test Coverage Report for Build 966578216

2 of 5 (40.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 30.072%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/commons/navigationBar/subcomponents/SicpNavigationBar.tsx
0
1
0.0%

src/pages/sicp/Sicp.tsx
0
1
0.0%

src/pages/sicp/subcomponents/SicpToc.tsx
0
1
0.0%

Totals

Change from base Build 964899119:
0.0%

Covered Lines:
3208

Relevant Lines:
9827

💛  - Coveralls


Allow description inside mappings

Is your feature request related to a problem? Please describe.
Hello, I am not sure if it's possible to add description for each mapping inside the config?
Thus, I could use telescope.builtin.keymaps to find each operation?
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Are you talking about mappings such as those for actions (move, rename, copy, etc) within the file_browser telescope picker?
If so, no, there is currently no way to add description to the mappings. Adding a feature like that would probably come from upstream (telescope.nvim).
And even if there were, the mappings would not show up in telescope.builtin.keymaps since the mappings are only local to the picker window and don't exist when the picker isn't open.
The closest thing to want you're looking for that we can offer right now is the which-key feature that built into all telescope pickers. You can hit <C-/> in insert mode or ? in normal mode (by default) to see a list of mappings attached to the picker.

Hello, yes but thanks anyway.
Yeah I would dig more about this, I also find the nvim-mapper plugin may suit in this case as well.


my bad, used lazy f"{}" string formatting

replaced with more compatible "{}".format

Coverage remained the same at 80.591% when pulling 667713515c59e4a3bd3bc98646e5b5a8ae0756f8 on briochh:develop into 13eb6876044f1cad862bd0d26832f4597ea56fc6 on jtwhite79:develop.