[Bug] Unable to locate Microsoft.Extensions.PlateformAbstractions

While i'm running dnu restore I got this exception Unable to locate Microsoft.Extensions.PlateformAbstractions, probably this happen after this commit https://github.com/aspnet/Localization/commit/d25ad6607e0abca395a7a1fca45d5afbee5356c9
/cc @pakrym @kirthik @Eilon

After I run build.cmd all the packages has been restored successfully, nothing but this exception is show up

/cc @kirthik

You need to upgrade dnx

I already did that yesterday it's 1.0.0-beta8-15604

New version show up in the list today 1.0.0-rc1-15838 i will upgrade and check now

@kirthik I upgrade and run dnu restore --no-cache with no luck :(, any idea

Still I'm stuck with this bug, any idea
/cc @Eilon

Could you please provide:

The output of dnx --version
The output of dnu feeds list
Your web command from project.json

Also, could you please try clearing out your .dnx/packages folder and run restore again?

1.0.0-rc1-15838
Feeds in use:
https://www.nuget.org/api/v2/
Origin: C:\Users\Hisham\AppData\Roaming\NuGet\nuget.config
https://api.nuget.org/v3/index.json [Disabled]
Offical NuGet Source, enabled by default
NuGet Config files in use:
C:\Users\Hisham\AppData\Roaming\NuGet\nuget.config
Web Command "Microsoft.AspNet.Hosting --server Microsoft.AspNet.Server.WebListener --server.urls http://localhost:5000"

Still I got the exception :(

None of those feeds have RC1 on them - where are you getting RC1 builds from?

@Eilon I just upgrade dnvm couple days ago, how can i fix it

@NTaylorMullen can you take a look at this? I still think this is just a DNX or package mismatch. Note that there's a linked bug https://github.com/aspnet/Mvc/issues/3407 where another person saw something similar.

@Eilon I did whatever I can, upgrading dnvm to rc, remove .dnx entries .. ect, no way, the sample and test units won't run

@hishamco everything on all the machines here is working fine, so clearly there's some difference in what feeds or configuration people are using.

Really I stuck @Eilon, I notice whenever I pull the latest changes from the upstream something should go wrong in my machine, so any idea how can I avoid this.
BTW when you mentioned issue #3407 I thought it's a common issue

Hey @hishamco I was able to dnu restore successfully.
DNX:
Microsoft .NET Execution environment
 Version:      1.0.0-rc2-16071
 Type:         Clr
 Architecture: x86
 OS Name:      Windows
 OS Version:   10.0
 Runtime Id:   win10-x86

Feeds:
Feeds in use:
    https://www.nuget.org/api/v2/ [Disabled]
      Origin: C:\Users\nimullen\AppData\Roaming\NuGet\nuget.config
    https://www.myget.org/F/aspnetcidev/api/v3/index.json
      Origin: C:\Users\nimullen\Documents\GitHub\Localization\nuget.config
    https://api.nuget.org/v3/index.json
      Origin: C:\Users\nimullen\Documents\GitHub\Localization\nuget.config

NuGet Config files in use:
    C:\Users\nimullen\AppData\Roaming\NuGet\nuget.config
    C:\Users\nimullen\Documents\GitHub\Localization\nuget.config

I'm not entirely sure why things are failing on your end, something may have put your machine in a bad state. Do the following and then try dnu restoring again:

Delete your %UserProfile%/.dnx/packages folder
Delete your %LocalAppData%/dnu/cache folder
Remove all project.lock.json files in your Localization directory.

@NTaylorMullen I'm using 1.0.0-rc1-15838, whenever i upgrade the dnvm 1.0.0-rc2-16071 doesn't show up on the list

@hishamco You must have an odd dnvm feed setup. To upgrade your DNX to development bits do the following in powershell:
$env:DNX_FEED="https://www.myget.org/F/aspnetcidev/api/v2"
dnvm upgrade

The problem here is that dnvm uses a different feed than the ones specified in your NuGet.config.

@NTaylorMullen i upgraded the dnvm to the same version but i got this exception in sample project

and this in unit test project

Did you dnu restore?

Of course

That's indeed odd. Could you do $env:DNX_TRACE="1" and then clean everything like I suggested and re-run then post the output?

Finally, after one week it works fine :smile: ,removing an old KRE_HOME key and  following the steps of @NTaylorMullen in Localization folder, it works like a charm :smile:

Awesome, glad I could help :smile:


Add private endpoint name to net sdk

This review is associated with the swagger changes at https://github.com/Azure/azure-rest-api-specs/pull/10264
SyncGroupCRUD and SyncMemberCRUD tests are passing with this change.
Code change has reached production. Rest api specs has been merged.

Hi @danikaZ please make sure that after the spec is merged, you generate SDK again from Azure/azure-rest-api-specs (master branch). Thanks

@isra-fel swagger change in  Azure/azure-rest-api-specs#10264 has been merged. I have regenerated the changes based on Azure/azure-rest-api-specs, there's no change to files in this PR.


Dropdown

Dropdowns would be a great widget to add. Some things to perhaps keep in mind:

Setting a minimum size or number of options visible
Scrolling, if there are more options than the specified range
Formatting the text (left/right justified, centered)
Direction of the dropdown: U/down/left/right

I'm gonna try to do this. @AustL

I have this ... It's not great, there is no direction for the moment...
The branch is here =>https://github.com/slashformotion/PygameWidgets/tree/dropdown

Looking great so far.

This is fixed in PR #24


Fixed issue #14 with getChildProps setting follow. from this.follow to this....

Fixes issue #14 here with not following directories that are symlinks. Not sure what the intended design was.

Hi @zkat, I just wanted to ping on this PR. Assuming that following nested symlinks is the intended behavior, is there any reason this (once rebased) can't be merged?

Hi @zkat and @othiym23 just wanted to ping on this again. Sorry to be a squeaky wheel.

I need to write tests for this :<

HI, @othiym23 Is there anything I can do to help with this? I'd be willing to write some tests if y'all have something I can reference to see how you want them.
p.s. We met at Cascadia, I was the guy with the hexapod.

Hey guys,
is there any progress regarding this PR?
Need this to use symbolic links in firebase (see https://github.com/firebase/firebase-tools/issues/22).
Cheers

@othiym23 can you address this (seemingly simple) issue. Since firebase-tools depend on this library, this completely blocks any use of symlinks in firebase projects(!).
https://github.com/firebase/firebase-tools/issues/22

I cannot believe this PR has been open for 6 years, contains a single line diff, and still hasn't been merged...
  As has been mentioned firebase-tools depends upon this repo and for those of us looking to structure our code in a mono-repo we need the ability to use symlinks.
If there is anything myself or any of the community members can do to get this fixed upstream please lmk.


Schema inspection report skips union types

I noticed one more false positive report on SkippedTypes
type Query {
    thing: Thing!
}

type Triangle {
    area: Int!
}

type Square {
    area: Int!
}

union Shape = Triangle | Square

type Thing {
    name: String
    description: String
    shape: Shape
}

@Controller
class ThingController {

    @QueryMapping
    fun thing() = Thing("something", "empty")

    @SchemaMapping(typeName = "Thing", field = "shape")
    fun shape() = Triangle(15)
}

sealed interface Shape
data class Triangle(val area: Int): Shape
data class Square(val area: Int): Shape

data class Thing(
    val name: String,
    val description: String
)

Schema introspection report gives output:
GraphQL schema inspection:
	Unmapped fields: {}
	Unmapped registrations: {}
	Skipped types: [Shape]

The interesting part is that if I move the shape field inside the data class as a field without having a resolver for the field, then the introspection report will not have any skipped types.
Originally posted by @smilyanovr in https://github.com/spring-projects/spring-graphql/issues/739#issuecomment-1602788114

As mentioned under https://github.com/spring-projects/spring-graphql/issues/739#issuecomment-1611153250, the inspection works by traversing the schema, starting with queries, mutations, and subscriptions, comparing schema return type against controller method return types, and descending recursively.
We stop at shape: Shape because the schema inspection does not support union types currently. We could try to iterate over the types of the union, but the controller method likely returns Object as there are no union types on the Java side (and Kotlin I think), so there is no type information to use, and we also don't know what Java type a union type corresponds to, so we can't check it, and report it as skipped instead.
In this case, the controller method returns a specific type Triangle, which is surprising. I'm not sure why the shape field is Shape then and not Triangle. Based on this mapping and controller method signature, the application always return Triangle, and never Square which the client could request. Could you clarify the intent or provide more detail to understand the use case.

Let me give more concrete real world example. I was trying to simplify the example in the report.
type Schedule {
    id: ID!
    name: String!
    description: String!
    entity: ScheduleEntity!
    type: ScheduleType!
}

union ScheduleEntity = X | Y

type X {
   # some X type specific fields
}

type Y {
   # some Y specific fields
}

Type Schedule has an enum ScheduleType that gives information on the foreign key relation, i.e. what object should be loaded for entity field.
Resolver is defined as:
@SchemaMapping(field = "entity")
fun getEntity(schedule: Schedule): ScheduleEntity {
     return when (schedule.type) {
          ScheduleType.X ->  // read entity X
          ScheduleType.Y -> // read entity Y
     }
}

sealed interface ScheduleEntity
class X(...): ScheduleEntity
class Y(...): ScheduleEntity

Sorry for the pseudo code. Hope this gives more idea about the actual report from schema introspection.

I see now, thanks.
So here ScheduleEntity acts as a marker interface? We could probably do something with that. We've been assuming a controller return value of Object for a union, but with a marker interface we could discover the implementation types, then use the registered TypeResolver to find the schema type, and try matching the two.
Some experimenting would be needed to confirm how well this works, and the TypeResolver would need to be our ClassNameTypeResolver, which we could enhance to allow checks by type rather than by instance as expected typically for TypeResolver implementations.

Yes, ScheduleEntity acts as a marker interface.

I've had a look at support for unions and interfaces (#739).
As mentioned before, the schema inspection starts from queries, mutations, and subscriptions, comparing schema output types against  the return type of the mapped controller method (or any SelfDescribingDataFetcher), descending recursively on fields that are further mapped to another controller method.
For unions and interfaces, we can't use the declared schema field type and the controller method return type as is. We must first discover all schema and Java type pairs that can be returned, and then work through each pair.
One option is to start with the Java type, discover the hierarchy, and then resolve corresponding schema types. However, there is no easy way to use reflection for that, and the controller might return Object which makes it impossible.
The better option is to start from the schema type, which provides easy access to the interface hierarchy, and likewise for a union, we know the exact types included. From there we need to map every leaf type to a Java type.
Our ClassNameTypeResolver uses a function to derive the schema type, which by default takes the Java class name. There is also a Map of explicit mappings, or you can customize the function. We can create a similar component that does the reverse, deriving the class for a schema type. We can't derive fully qualified Java class names without any help, but we could if given one or more top-level packages to look under, or in any case it would be easy for an application to provide a function that maps schema to Java types, provided there is some consistent naming pattern. Or if it's down to explicit mappings, for that we can re-use the mappings from ClassNameTypeResolver, but use it in reverse.
In short, with a little help from the application, we could extend schema inspection to union and interface types. I see no alternatives for this to work completely transparently out of the box, but what's required should be fairly straight forward, and not too different from what's required anyway for Java classname to schema type interface and union mappings with GraphQL Java.

I've created #924 for union and interface support.


delete beta_neg_binomial_lccdf test

Summary
As described by #3117, disable the test for beta_neg_binomial_lccdf.
Tests
NA
Side Effects
NA
Release notes
test/prob/beta_neg_binomial/beta_neg_binomial_ccdf_log_test.hpp will be deleted if merged.
Checklist

[x] Copyright holder: Zhi Ling
The copyright holder is typically you or your assignee, such as a university or company. By submitting this pull request, the copyright holder is agreeing to the license the submitted work under the following licenses:
- Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
- Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
dependencies checks pass, (make test-math-dependencies)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

Instead of deleting it, can we try the following

Make a beta_neg_binomial_tol_lccdf that exposes the tuning parameters.
Test that with "nice numbers" that are easy to solve with a high tol and low iteration
Have tests that use the expect_ad testing framework for the basic beta_neg_binomial_tol_lccdf

The prob testing framework is mostly to ensure that all the different varations of scalars and vectors can go into the distributions. But if we just want to test boundaries and things like that then I think it would be better for us to have those in mix/prob testing folder

Thanks to Steve's suggestion, after some debugging I found certain magic numbers and now the time for this test should be the same as other distributions. Let’s see how it works on the Jenkins machine.

Nice, now the test will not affect continuous integration.


cargo count dies if there are broken symlinks in tree

$ mkdir sample
$ cd sample
$ ln -s invalid foo
$ cargo count
Gathering information...
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: Error { repr: Os { code: 2, message: "No such file or directory" } }', src/libcore/result.rs:731

The culprit seems to be the calls to metadata in get_all_files, which will fail on a bogus symlink. Perhaps symlink_metadata would be better.

Thanks for taking the time to file this! This should be an easy fix.

This works now as cargo-count doesn't follow symlinks by default, but you can force it to by passing --follow-symlinks (or -S) and it shouldn't panic but instead function as expected.


feat(audit): Use block timestamp instead of block number.

closes: #1069
Switches the userData to check and return in events the block timestamp instead of block number.
To Test:

[x] anvil_deploy_aligned_contracts and anvil_start_with_block_time
[x] Run local testnet and ensure nothing errors.

To Test

Change modify the block time constant. You should observe the unlock time decrease in the local testnet.

Deployed in stage


Not able to authenticate sendgrid key with wisepops

Expected content
Actual content
Not able to authenticate sendgrid key with wisepops getting error like "An error occurred during the authentication. Please check your credentials or contact our support":

Hello @sewakram
We're sorry you're having this issue! Since this is not a docs-related issue, please contact our Support team directly and they can help you out. You can access support contact options by logging into https://support.sendgrid.com.
Otherwise, I found this article on their site, but you might have already seen it: https://support.wisepops.com/en/articles/753257-connect-wisepops-with-sendgrid
If our support team can't help you, I'd also recommend reaching out to Wisepop's support team.
SendGrid Docs Team


Add license explanation issue

Fixes #292
Description

issue is fixed added all explanation of licenses and ran it locally you can find the gif of it below

Other information

Checklist:

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

@patelaryan7751 This is in the context of your message on slack.
You can see in the logs that the formatting in popup.html is the cause of failing checks.
I would recommend you to read the code formatting section in INSTRUCTIONS.md to see how you can tackle this.
Also, please push the updates in the same PR and do not open new ones. You have already closed 9 PRs for the same issue.

@patelaryan7751 This is in the context of your message on slack.
You can see in the logs that the formatting in popup.html is the cause of failing checks.
I would recommend you to read the code formatting section in INSTRUCTIONS.md to see how you can tackle this.
Also, please push the updates in the same PR and do not open new ones. You have already closed 9 PRs for the same issue.

hello @makkoncept  i  have followed the guidelines and all the checks passed .

The design of the tool-tip is not one that we want. As already mentioned in the corresponding issue, The design and the content will be identical to the CC Search implementation.
Pasting the screenshot again for reference:

@makkoncept  i would implement the same design . I am working on it . I guess rest of the functionality is working perfectly.

I think the below design would do good.

i have used licenseInfo from helper.js in tooltipInfo to get the icons and their information dynamically .

I think the below design would do good.
i have used licenseInfo from helper.js in tooltipInfo to get the icons and their information dynamically .
i have created a new "tooltipInfo " because the heading of the licenses are not present in "licenseInfo".
also there are license info which has multiple symbols like" CC-BY-SA" it has mutiple icons and multiple description for this "licenseInfo" may not be sufficient (as far as license heading is concerned) hence there was a need for creating "tooltipInfo".
if we can do it better then let me know i would surely work on it.


terraform: Wrap PATH of propagatedBuildInputs

Motivation for this change
Plugins (namely terraform-provider-libvirt) may have a run time
dependency on external binaries.
See https://github.com/NixOS/nixpkgs/pull/37852
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

cc @Mic92 @zimbatm @peterhoeg @jgeerds

Success on x86_64-linux (full log)
Attempted: terraform
Partial log (click to expand)
these paths will be fetched (11.78 MiB download, 83.02 MiB unpacked):
  /nix/store/svg985ny0x19lhvz8r448vsbrqd16hcw-terraform-0.11.4-bin
copying path '/nix/store/svg985ny0x19lhvz8r448vsbrqd16hcw-terraform-0.11.4-bin' from 'https://cache.nixos.org'...
/nix/store/svg985ny0x19lhvz8r448vsbrqd16hcw-terraform-0.11.4-bin

Success on aarch64-linux (full log)
Attempted: terraform
Partial log (click to expand)
these paths will be fetched (10.81 MiB download, 78.79 MiB unpacked):
  /nix/store/68vzgjqk26vhy271wr6j9hw3gw1bqqz6-terraform-0.11.4-bin
  /nix/store/vqlb5ygj34c40lr7hcsg3kgnq6pyki8p-iana-etc-20180108
copying path '/nix/store/vqlb5ygj34c40lr7hcsg3kgnq6pyki8p-iana-etc-20180108' from 'https://cache.nixos.org'...
copying path '/nix/store/68vzgjqk26vhy271wr6j9hw3gw1bqqz6-terraform-0.11.4-bin' from 'https://cache.nixos.org'...
/nix/store/68vzgjqk26vhy271wr6j9hw3gw1bqqz6-terraform-0.11.4-bin

Success on x86_64-darwin (full log)
Attempted: terraform
Partial log (click to expand)
these paths will be fetched (15.29 MiB download, 120.41 MiB unpacked):
  /nix/store/gkslmhs5s0mx137xxn2f69157vfnzwqs-terraform-0.11.4-bin
copying path '/nix/store/gkslmhs5s0mx137xxn2f69157vfnzwqs-terraform-0.11.4-bin' from 'https://cache.nixos.org'...
/nix/store/gkslmhs5s0mx137xxn2f69157vfnzwqs-terraform-0.11.4-bin

I would not abuse setup-hook for this case. This might set build-time other only stuff we do not want to have at runtime like set PYTHONHASHSEED which can be dangerous in active usage.

Failure on x86_64-darwin (full log)
Attempted: terraform
Partial log (click to expand)
cannot build derivation '/nix/store/zy8js09gma1q7lvvnz6lv2j6cwbrfqh4-python2.7-pytest-xdist-1.22.2.drv': 10 dependencies couldn't be built
cannot build derivation '/nix/store/bjahk71667zfrjjxkpd2j48r24rj2hhy-mercurial-4.5.drv': 11 dependencies couldn't be built
cannot build derivation '/nix/store/a5six6mdihiq9n4cz6sqpsrdjdm26ic4-python2.7-hypothesis-3.45.2.drv': 13 dependencies couldn't be built
cannot build derivation '/nix/store/rkfk7d32p3h87ydv6nnfvhls72xh6gdq-python2.7-cryptography-2.1.4.drv': 21 dependencies couldn't be built
cannot build derivation '/nix/store/jlvvgi10w24g3pb1alvdciq7kdfipj53-python2.7-paramiko-2.1.1.drv': 8 dependencies couldn't be built
cannot build derivation '/nix/store/j90j2mvc1xj3cjc6jx37sd44pda7c3j4-bazaar-2.7.0.drv': 7 dependencies couldn't be built
cannot build derivation '/nix/store/jzrc0m2zh1z65piphs13mvhf8lydx1dd-go-1.9.4.drv': 17 dependencies couldn't be built
cannot build derivation '/nix/store/n6czxv2vcyrfh9w0kqb88f78gcr9fal3-govers-20150109-3b5f175.drv': 4 dependencies couldn't be built
cannot build derivation '/nix/store/19qpl68wq2pfq4l35cjrra40r237hcwn-terraform-0.11.4.drv': 5 dependencies couldn't be built
error: build of '/nix/store/19qpl68wq2pfq4l35cjrra40r237hcwn-terraform-0.11.4.drv' failed

Success on x86_64-linux (full log)
Attempted: terraform
Partial log (click to expand)
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/ChrisTrenkamp/goxpath/coverage.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/posener/complete/test.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/ulikunitz/xz/make-docs: interpreter directive changed from "/bin/sh" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/sh"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/fsouza/go-dockerclient/travis-scripts/run-tests.bash: interpreter directive changed from "/bin/bash -ex" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash -ex"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/fsouza/go-dockerclient/travis-scripts/install.bash: interpreter directive changed from "/bin/bash -x" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash -x"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/fsouza/go-dockerclient/external/golang.org/x/sys/unix/mkerrors.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/fsouza/go-dockerclient/external/golang.org/x/sys/unix/mkall.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4/share/go/src/github.com/hashicorp/terraform/vendor/github.com/golang/protobuf/ptypes/regen.sh: interpreter directive changed from "/bin/bash -e" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash -e"
checking for references to /build in /nix/store/93a41i8m32zgyii73qyqfpfa2g12np95-terraform-0.11.4...
/nix/store/j37dvmslmkd7gdad32gk97010sgfmq9c-terraform-0.11.4-bin

Failure on aarch64-linux (full log)
Attempted: terraform
Partial log (click to expand)
tests/cover/test_shrinking_limits.py .                                   [ 71%]
tests/cover/test_simple_characters.py .............                      [ 72%]
building of '/nix/store/cmdvps6qj283gnmkc71wrbay5bvb47s7-python2.7-hypothesis-3.45.2.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/pr4yqchn2cd2kgmlp90acrgk3zbs9l80-python2.7-cryptography-2.1.4.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/giz8r2sap24pb49399w5s83as9pydk7m-python2.7-paramiko-2.1.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/083yqs4xivsddkmb9yyzvdasf2b04k84-bazaar-2.7.0.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/jk90n67apangx4bcrdan4hks3g253n7p-go-1.9.4.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/58444z5b3pm4758qhclrcqfw1lqrrsjs-govers-20150109-3b5f175.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/vxyq18lhqjf30mf2wsd1h7fxyq6brnkz-terraform-0.11.4.drv': 2 dependencies couldn't be built
error: build of '/nix/store/vxyq18lhqjf30mf2wsd1h7fxyq6brnkz-terraform-0.11.4.drv' failed


Add Rethnet provider as JSON-RPC provider in Hardhat tests

Definition of Done

Add an extension of the JSON-RPC provider to Hardhat, that launches the Rethnet server in the background
Add the provider to Hardhat tests (state management tests should succeed)
Provide a list of tests that were disabled (non-state management)

I just discussed this issue with @feuGeneA, as I believe this task may lead to us discovering new issues in unrelated parts of the codebase. The reason I think this is that it'll be the first time that we run complex examples/tests with a pure-rethnet setup, as opposed to the adapter we were previously using.
I think that if this happen we should open issues for those bugs instead of fixing everything as part of this task, so that this is not a potentially-infinite task. The exception here would be issues with the JSON-RPC provider itself.

0-0.5 days left for sprint 20


Reference the translator module consistently from widgets and Form.js

Make references to translator consistent.
Ideally though, all code would probably refer to fake-translator, and leave this up to 3rd-parties to override with their own translator using e.g. browserify.

Thanks! Totally right about that error.

Ideally though, all code would probably refer to fake-translator, and leave this up to 3rd-parties to override with their own translator using e.g. browserify.

This is exactly the idea behind require(translator) and having a dummy fake-translator included that doesn't translate anything. Why would calling require('fake-translator') be better?

Why would calling require('fake-translator') be better?

There's already a published node module called translator, which is similar but has a different API.
That library doesn't look hugely popular so it's unlikely to ever cause a problem, but I was thinking if the enketo code used a relative require (e.g. require('./fake-translator') then that might be overrideable but also be guaranteed collision-free.
This would be similar to what is done with require( './xpath-evaluator-binding' ); in Form-model.js.

Thanks. Yes, that's a good reason. The only problem is that it would break things in Enketo-Core consuming apps that are already overriding translator. Maybe good to keep for a 5.x version.

Maybe good to keep for a 5.x version.

If it was changed for translator, then I guess widgets would also be worth changing.

As I'm about to make this even worse with a gui module that can overwrite native alert() and confirm() dialogs, how about using something like require('enketo/translator') with this aliasify config:
"enketo/config": "./config.json",
"enketo/widgets": "./src/js/widgets.js",
"enketo/translator": "./src/js/fake-translator",
"enketo/gui": "./src/js/fake-gui"

We're avoiding actual relative paths for easy overriding, but are using enketo/ as a namespace basically (no enketo folder present necessarily), There is also a scope feature in npm @enketo/translator but I think that may be not be appropriate to abuse.

Yes, I think I like this. And I'm changing my mind about needing to wait for a 5.0.0 version because the build system will break immediately which makes it less risky that it is overlooked.

done in 01b6a80646e0598ae33383d9da60530c2f60d4a9


Lambda

Have you considered using lambda to rapidly copy files from S3 to EBS?

Did you mean to say lambda to EC2?

I have been thinking of a system which caches S3 data in high performance storage which can be accessed as a file system from any number of EC2 instances.
Key elements:

Use Lambda instances to perform any work required, e.g. synchronization.
Store the data in EFS (still in preview).

EFS is designed to support high scalability and does not require you to create EC2 instances to serve the data.
As this project has done, this would be a limited size cache using an LRU algorithm.
Locking at the file level could be done using Dynamo or some other mechanism.

In order to determine if data in EFS is stale, i.e. S3 has been updated, one can store the edata tag in EFS and use that to compare to what is in S3.  If they are different then the cache is out of date.

Just sharing some thoughts.
It is really a shame that Amazon does not provide this system because I think that this pattern is repeated across many applications.


Use Metal on iOS

https://www.raywenderlich.com/9211-moving-from-opengl-to-metal Huh, GLKView should be replaced with MTLView... 🤔

Note: now uidriver/mobile depends on graphicsdriver/opengl. Remove this dependency.

Actually this was almost finished with ebitenmobile command, but I'll leave this open until we release the game with Metal.

Note: we need to be careful that this doesn't break backward compatibility with gomobile-build.

Now iOS's gomobile-build is broken, I cannot test it 😢
https://github.com/hajimehoshi/ebiten/issues/951


Cannot create service: subset not found

Hi All,
When I trying to connect to run the command below to check the connection, I got the timeout error.
[azureuser@aksbaseline aks-secure-baseline]$ kubectl -n a0008 run -i --rm --tty curl --image=mcr.microsoft.com/powershell --limits=cpu=200m,memory=128M -- curl -kI https://bu0001a0008-00.aks-ingress.contoso.com -w '%{remote_ip}\n'
If you don't see a command prompt, try pressing enter.

curl: (7) Failed to connect to bu0001a0008-00.aks-ingress.contoso.com port 443: Connection timed out
Session ended, resume using 'kubectl attach curl -c curl -i -t' command when the pod is running
pod "curl" deleted

And I got following error when checking the logs of the traefik pod.
[azureuser@aksbaseline aks-secure-baseline]$ kubectl logs -f traefik-ingress-controller-665bc754f9-rh2kt -n a0008
time="2020-09-05T07:31:59Z" level=info msg="Configuration loaded from file: /config/traefik.toml"
{"ingress":"aspnetapp-ingress","level":"error","msg":"Cannot create service: service not found","namespace":"a0008","providerName":"kubernetes","serviceName":"aspnetapp-service","servicePort":"http","time":"2020-09-05T07:33:43Z"}

I am wondering if anyone got this error and how to fix it?
Thanks,
Neal

The backend status of app gateway is unhealthy.

thanks for sharing this @neallee2012, it seems that the workload is not up and running in your AKS cluster for some reason.
Could you please help us to confirm this by running the following command and sharing the output?
kubectl get ingress aspnetapp-ingress -n a0008

Thanks @ferantivero, here is the output.
[azureuser@aksbaseline ~]$ kubectl get ingress aspnetapp-ingress -n a0008
NAME                HOSTS                                    ADDRESS   PORTS     AGE
aspnetapp-ingress   bu0001a0008-00.aks-ingress.contoso.com             80, 443   2d17h

@neallee2012 it's confirmed now, so please let us try to help to troubleshoot this. Please feel free to share the output from this session.
Please note that feedback is going to be really appreciated since I'm thinking we could create a troubleshooting section with the learnings from this issue:
1 - Check for errs trying to obtain your TLS certs
kubectl logs <csi-secrets-store-name> -n cluster-baseline-settings -c secrets-store

2 - In case of errors in the above step
# inspect the SecretProvideClass object and see the `Azure KeyVault Name` and `Tenant Id` are properly set.
# Try to spot empty values, white spaces or invalid chars
kubectl get SecretProviderClass aks-ingress-contoso-com-tls-secret-csi-akv -n a0008 -o yaml

3 - If everything looks good from steps 1 & 2
# wait for traefik condition to  be met
kubectl wait --namespace a0008 --for=condition=ready pod --selector=app.kubernetes.io/name=traefik-ingress-ilb --timeout=90s

4 - The condition above timeout(ed)
# inspect the ingress controller deploy to pinpoint why it is not getting scheduled
kubectl describe deploy traefik-ingress-controller -n a0008

5 - The ingress controller is up & running but still my Azure Application Gateway is in Unhealthy state
# inspect the ingress controller logs
kubeclt logs <traefik-pod-name> -n a0008

6 - None of the above steps helped me
# get the overall health the workload namespace
kubectl get pod -n a0008

# check for detected violations
kubectl logs <gatekeeper-pod-name> -n gatekeeper-system

# look for broader issues in my AKS cluster
kubectl get events --all-namespaces

Thanks @ferantivero! below are the outputs from step1 to step5.
1. Check for errs trying to obtain your TLS certs
[azureuser@aksbaseline ~]$ kubectl logs csi-secrets-store-lttgz -n cluster-baseline-settings -c secrets-store
Error from server: Get https://aks-npuser01-13050762-vmss000001:10250/containerLogs/cluster-baseline-settings/csi-secrets-store-lttgz/secrets-store: dial tcp <IP_ADDRESS>:10250: i/o timeout

[azureuser@aksbaseline ~]$ kubectl logs csi-secrets-store-x65jn -n cluster-baseline-settings -c secrets-store
Error from server: Get https://aks-npuser01-13050762-vmss000004:10250/containerLogs/cluster-baseline-settings/csi-secrets-store-x65jn/secrets-store: dial tcp <IP_ADDRESS>:10250: i/o timeout

2. In case of errors in the above step
[azureuser@aksbaseline ~]$ kubectl get SecretProviderClass aks-ingress-contoso-com-tls-secret-csi-akv -n a0008 -o yaml
apiVersion: secrets-store.csi.x-k8s.io/v1alpha1
kind: SecretProviderClass
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"secrets-store.csi.x-k8s.io/v1alpha1","kind":"SecretProviderClass","metadata":{"annotations":{},"name":"aks-ingress-contoso-com-tls-secret-csi-akv","namespace":"a0008"},"spec":{"parameters":{"keyvaultName":"kv-aks-lnzwe47afh4ja","objects":"array:\n  - |\n    objectName: traefik-ingress-internal-aks-ingress-contoso-com-tls\n    objectAlias: tls.crt\n    objectType: cert\n  - |\n    objectName: traefik-ingress-internal-aks-ingress-contoso-com-tls\n    objectAlias: tls.key\n    objectType: secret\n","tenantId":"72f988bf-86f1-41af-91ab-2d7cd011db47","usePodIdentity":"true"},"provider":"azure"}}
  creationTimestamp: "2020-09-05T07:09:05Z"
  generation: 2
  name: aks-ingress-contoso-com-tls-secret-csi-akv
  namespace: a0008
  resourceVersion: "6183"
  selfLink: /apis/secrets-store.csi.x-k8s.io/v1alpha1/namespaces/a0008/secretproviderclasses/aks-ingress-contoso-com-tls-secret-csi-akv
  uid: e1aed32f-bef5-4b03-9d78-d1672d1269e8
spec:
  parameters:
    keyvaultName: kv-aks-lnzwe47afh4ja
    objects: |
      array:
        - |
          objectName: traefik-ingress-internal-aks-ingress-contoso-com-tls
          objectAlias: tls.crt
          objectType: cert
        - |
          objectName: traefik-ingress-internal-aks-ingress-contoso-com-tls
          objectAlias: tls.key
          objectType: secret
    tenantId: 72f988bf-86f1-41af-91ab-2d7cd011db47
    usePodIdentity: "true"
  provider: azure

3. If everything looks good from steps 1 & 2
[azureuser@aksbaseline ~]$ kubectl wait --namespace a0008 --for=condition=ready pod --selector=app.kubernetes.io/name=traefik-ingress-ilb --timeout=90s
timed out waiting for the condition on pods/traefik-ingress-controller-665bc754f9-mjz6c
timed out waiting for the condition on pods/traefik-ingress-controller-665bc754f9-q92wn

4. The condition above timeout(ed)
[azureuser@aksbaseline ~]$ kubectl describe deploy traefik-ingress-controller -n a0008
Name:                   traefik-ingress-controller
Namespace:              a0008
CreationTimestamp:      Sat, 05 Sep 2020 07:31:06 +0000
Labels:                 aadpodidbinding=traefik-ingress-controller
                        app.kubernetes.io/instance=traefik-ingress-ilb
                        app.kubernetes.io/name=traefik-ingress-ilb
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app.kubernetes.io/instance=traefik-ingress-ilb,app.kubernetes.io/name=traefik-ingress-ilb
Replicas:               2 desired | 2 updated | 2 total | 0 available | 2 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  1 max unavailable, 1 max surge
Pod Template:
  Labels:           aadpodidbinding=traefik-ingress-controller
                    app.kubernetes.io/instance=traefik-ingress-ilb
                    app.kubernetes.io/name=traefik-ingress-ilb
  Annotations:      prometheus.io/port: 8082
                    prometheus.io/scrape: true
  Service Account:  traefik-ingress-controller
  Containers:
   traefik-ingress-controller:
    Image:       registry.hub.docker.com/library/traefik:2.2.1
    Ports:       9000/TCP, 8443/TCP, 8082/TCP
    Host Ports:  0/TCP, 0/TCP, 0/TCP
    Args:
      --configfile=/config/traefik.toml
    Limits:
      cpu:     200m
      memory:  128Mi
    Requests:
      cpu:        100m
      memory:     64Mi
    Liveness:     http-get http://:traefik/ping delay=10s timeout=2s period=10s #success=1 #failure=3
    Readiness:    http-get http://:traefik/ping delay=10s timeout=2s period=10s #success=1 #failure=1
    Environment:  <none>
    Mounts:
      /certs from ssl-csi (ro)
      /config from config (ro)
      /data from data (rw)
  Volumes:
   config:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      traefik-ingress-config
    Optional:  false
   ssl-csi:
    Type:              CSI (a Container Storage Interface (CSI) volume source)
    Driver:            secrets-store.csi.k8s.io
    FSType:
    ReadOnly:          true
    VolumeAttributes:      secretProviderClass=aks-ingress-contoso-com-tls-secret-csi-akv
   data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Progressing    True    NewReplicaSetAvailable
  Available      False   MinimumReplicasUnavailable
OldReplicaSets:  traefik-ingress-controller-665bc754f9 (2/2 replicas created)
NewReplicaSet:   <none>
Events:          <none>

The ingress controller is up & running but still my Azure Application Gateway is in Unhealthy state

[azureuser@aksbaseline ~]$ kubectl logs traefik-ingress-controller-665bc754f9-q92wn -n a0008
Error from server: Get https://aks-npuser01-13050762-vmss000001:10250/containerLogs/a0008/traefik-ingress-controller-665bc754f9-q92wn/traefik-ingress-controller: dial tcp <IP_ADDRESS>:10250: i/o timeout

it looks like you are having some connectivity issues with your AKS cluster @neallee2012, could you please try to re execute those steps where you've received timeout?

Hey there @neallee2012 -- I'm going to close the issue at this point since we haven't heard from you for a while.  Feel free to open it back up if there is something we can do to make this process more successful for you.  Thanks.


Style/FrozenStringLiteralComment docs and default

The documentation states that:

Frozen string literals may be default in future Ruby.

I believe that was meant for Ruby 3. However, it did not come to pass:

I consider this for years. I REALLY like the idea but I am sure introducing this could cause HUGE compatibility issue, even bigger than Ruby 1.9. So I officially abandon making frozen-string-literals default (for Ruby3).
This does not mean we are going to remove the frozen-string-literal feature that can be specified by magic comments.
Matz.

I was going to go ahead and create a small pull request to remove that sentence. But first, I wanted to clarify a few things:

Is there any other plan for Ruby to make this change that I have missed?
More importantly; since the change was abandoned, do we still want to keep the cop enabled by default? That would normally look like the preferable option, but some projects do not use it. For example, a new Rails project does not feature it, so one would need to go over all Ruby files as soon as they add Rubocop. There seems to be relatively little discussion about the current state of things at large (an example against it).

Plans to make frozen string literals the default have been resumed:
https://bugs.ruby-lang.org/issues/20205#note-35
So, I'll close this issue. Thank you.


List features in readme/documentation

We currently only highlight a single feature of the module, while there are more. I'd suggest adding those to the readme/documentation as well. Here's an attempt:

Extends Nuxt's built-in preview mode:

🚪 Enables preview mode through routing (?preview=true)
🔒 Secures preview mode with a (client-side) secret (&secret=...)
👉 Enables redirect when entering preview mode (&location=/...)
🧠 Persists preview mode through routing & page refresh using storage
🎛 Provides programmatic way to enter() and exit() preview mode
🍫 Provides <PreviewModeBar> component to display and control preview mode

Resolved in https://github.com/voorhoede/nuxt-preview-mode-module/pull/9


Add Rust ua community

Вивчаємо Rust Разом 🇺🇦:
https://t.me/rustlang_ua
🦀 Українська гілка спільноти Rust ентузіастів 💙💛
Mode information about this community: https://t.me/rustlang_ua/2383
Contributor's Checklist:

[X] I have read and understood the contribution rules. My submission complies with these rules.
[X] My submission is grammatically correct.
[X] My submission follows the general Awesome List guidelines. You can check it running the Awesome Lint locally. We also run linter on CI.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

@grem11n


🐛 [cloud_firestore] Fails to build Android app on Flutter 3.19.0-0.3.pre

Bug report
Describe the bug
The Firebase plugins fail to compile on Android with a broken GeneratedPluginRegistrant.java file. Probably related to https://github.com/flutter/flutter/issues/142796
Steps to reproduce
Steps to reproduce the behavior:
$ flutter create gtk_flutter --platforms=android
Creating project gtk_flutter...
Resolving dependencies in gtk_flutter... (1.6s)
Got dependencies in gtk_flutter.
Wrote 35 files.

All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev

In order to run your application, type:

  $ cd gtk_flutter
  $ flutter run

Your application code is in gtk_flutter/lib/main.dart.
$ cd gtk_flutter
$ flutter pub add cloud_firestore firebase_auth firebase_core firebase_ui_auth
Resolving dependencies...
+ _flutterfire_internals 1.3.19
+ args 2.4.2
+ cloud_firestore 4.15.2
+ cloud_firestore_platform_interface 6.1.3
+ cloud_firestore_web 3.10.2
+ crypto 3.0.3
+ desktop_webview_auth 0.0.15
+ email_validator 2.1.17
+ firebase_auth 4.17.2
+ firebase_auth_platform_interface 7.1.2
+ firebase_auth_web 5.9.2
+ firebase_core 2.25.2
+ firebase_core_platform_interface 5.0.0
+ firebase_core_web 2.11.2
+ firebase_dynamic_links 5.4.11
+ firebase_dynamic_links_platform_interface 0.2.6+19
+ firebase_ui_auth 1.12.1
+ firebase_ui_localizations 1.10.1
+ firebase_ui_oauth 1.4.17
+ firebase_ui_shared 1.4.1
+ flutter_localizations 0.0.0 from sdk flutter
+ flutter_svg 2.0.9
+ flutter_web_plugins 0.0.0 from sdk flutter
+ http 1.2.0
+ http_parser 4.0.2
+ intl 0.18.1 (0.19.0 available)
+ js 0.6.7 (0.7.0 available)
  leak_tracker 10.0.0 (10.0.3 available)
  leak_tracker_flutter_testing 2.0.1 (3.0.2 available)
  leak_tracker_testing 2.0.1 (3.0.0 available)
+ path_parsing 1.0.1
+ petitparser 6.0.2
+ plugin_platform_interface 2.1.8
  test_api 0.6.1 (0.7.0 available)
+ typed_data 1.3.2
+ vector_graphics 1.1.9+2
+ vector_graphics_codec 1.1.9+2
+ vector_graphics_compiler 1.1.9+2
  vm_service 13.0.0 (14.0.0 available)
+ web 0.4.2
+ xml 6.5.0
Changed 36 dependencies!
7 packages have newer versions incompatible with dependency constraints.
Try `flutter pub outdated` for more information.
$ flutter build apk

Font asset "MaterialIcons-Regular.otf" was tree-shaken, reducing it from 1645184 to 1384 bytes (99.9% reduction). Tree-shaking can be disabled by providing the --no-tree-shake-icons flag when building your app.
/Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:19: error: package io.flutter.plugins.firebase.firestore does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.firebase.firestore.FlutterFirebaseFirestorePlugin());
                                                                              ^
/Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:24: error: package com.example.desktop_webview_auth does not exist
      flutterEngine.getPlugins().add(new com.example.desktop_webview_auth.DesktopWebviewAuthPlugin());
                                                                         ^
/Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:29: error: package io.flutter.plugins.firebase.auth does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.firebase.auth.FlutterFirebaseAuthPlugin());
                                                                         ^
/Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:34: error: package io.flutter.plugins.firebase.core does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.firebase.core.FlutterFirebaseCorePlugin());
                                                                         ^
/Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java:39: error: package io.flutter.plugins.firebase.dynamiclinks does not exist
      flutterEngine.getPlugins().add(new io.flutter.plugins.firebase.dynamiclinks.FlutterFirebaseDynamicLinksPlugin());
                                                                                ^
5 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:compileReleaseJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 18s
Running Gradle task 'assembleRelease'...                           19.0s
Gradle task assembleRelease failed with exit code 1

Expected behavior
This app should compile clean. It compiles clean on iOS:
$ flutter create . --platforms=ios
$ flutter build ios --simulator
Building com.example.gtkFlutter for simulator (ios)...
Running pod install...                                             14.2s
Running Xcode build...
 └─Compiling, linking and signing...                        36.7s
Xcode build done.                                           342.9s
Built /Users/brettmorgan/Documents/GitHub/codelabs/firebase-get-to-know-flutter/gtk_flutter/build/ios/iphonesimulator/Runner.app.

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel beta, 3.19.0-0.3.pre, on macOS 14.3 23D56 darwin-arm64, locale en)
    • Flutter version 3.19.0-0.3.pre on channel beta at /Users/brettmorgan/flutter
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision 1b197762c5 (7 days ago), 2024-01-25 22:23:26 -0800
    • Engine revision 968e2945c7
    • Dart version 3.3.0 (build 3.3.0-279.2.beta)
    • DevTools version 2.31.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/brettmorgan/Library/Android/sdk
    • Platform android-34-ext8, build-tools 34.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15C500b
    • CocoaPods version 1.15.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 77.0.1
    • Dart plugin version 233.13135.65

[✓] VS Code (version 1.86.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.82.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-arm64   • macOS 14.3 23D56 darwin-arm64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 121.0.6167.139

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.3.0-279.2.beta
Flutter SDK 3.19.0-0.3.pre
gtk_flutter 1.0.0+1

dependencies:
- cloud_firestore 4.15.2 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.6
- firebase_auth 4.17.2 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 2.25.2 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_ui_auth 1.12.1 [email_validator firebase_auth firebase_core firebase_dynamic_links firebase_ui_localizations firebase_ui_oauth firebase_ui_shared flutter flutter_localizations meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math sky_engine]

dev dependencies:
- flutter_lints 3.0.1 [lints]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math leak_tracker_flutter_testing async boolean_selector characters collection leak_tracker leak_tracker_testing material_color_utilities meta source_span stream_channel string_scanner term_glyph vm_service]

transitive dependencies:
- _flutterfire_internals 1.3.19 [collection firebase_core firebase_core_platform_interface flutter meta]
- args 2.4.2
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- characters 1.3.0
- clock 1.1.1
- cloud_firestore_platform_interface 6.1.3 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.10.2 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- collection 1.18.0
- crypto 3.0.3 [typed_data]
- desktop_webview_auth 0.0.15 [crypto flutter http flutter_web_plugins plugin_platform_interface]
- email_validator 2.1.17
- fake_async 1.3.1 [clock collection]
- firebase_auth_platform_interface 7.1.2 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.9.2 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta web]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.11.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta web]
- firebase_dynamic_links 5.4.11 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.6+19 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_ui_localizations 1.10.1 [flutter flutter_localizations path]
- firebase_ui_oauth 1.4.17 [desktop_webview_auth firebase_auth firebase_ui_auth firebase_ui_shared flutter_svg flutter]
- firebase_ui_shared 1.4.1 [flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math]
- flutter_svg 2.0.9 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math]
- http 1.2.0 [async http_parser meta web]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- intl 0.18.1 [clock meta path]
- js 0.6.7 [meta]
- leak_tracker 10.0.0 [clock collection meta path vm_service]
- leak_tracker_flutter_testing 2.0.1 [flutter leak_tracker leak_tracker_testing matcher meta]
- leak_tracker_testing 2.0.1 [leak_tracker matcher meta]
- lints 3.0.0
- matcher 0.12.16+1 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.8.0 [collection]
- meta 1.11.0
- path 1.9.0
- path_parsing 1.0.1 [vector_math meta]
- petitparser 6.0.2 [meta]
- plugin_platform_interface 2.1.8 [meta]
- sky_engine 0.0.99
- source_span 1.10.0 [collection path term_glyph]
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- string_scanner 1.2.0 [source_span]
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- typed_data 1.3.2 [collection]
- vector_graphics 1.1.9+2 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.9+2
- vector_graphics_compiler 1.1.9+2 [args meta path_parsing xml vector_graphics_codec path]
- vector_math 2.1.4
- vm_service 13.0.0
- web 0.4.2
- xml 6.5.0 [collection meta petitparser]

@domesticmouse
You are probably hitting https://github.com/flutter/flutter/issues/141940

Closing as duplicate


chore: Add new tip under 'Pull Requests' for yarn test failing for packages/plexis/test/index.js

Some contributors are having yarn test failures locally and on CI for packages/plexis/test/index.js and they don't know how to remedy this issue. This issue is a result of not having the various compiled files in the correct locations resulting in various modules not being found. This is remedied by running yarn bootstrap.
I propose adding a tip under the 'Pull Requests' heading:
:bulb: Tip: yarn test failing for packages/plexis/test/index.js? Try running yarn bootstrap before running yarn test again.
Since this is a simple tip and might not affect everyone, I think it makes sense to add this information as a tip in the README. It's proven effective already in #43 .

I think this is also affecting #30 judging from the CI output.


Integrate ADCS system functions, when complete

ADCS functions (I2C interface) are being developed separately. Integrate them into this repo when complete.

Chatted with @DeemDeem52 on the path forward with this repo and using telecommands! He's working on it, and will get a unit test done for Tuesday so we can discuss any issues had!

I've gotten started updating the functions for unit testing and telecommands. It's going to take some time, though.
(The ADCS team is having problems right now, so we're not actually losing any time, though)

Refactoring is making excellent progress. I've got unit tests up and running, which are showing me that I need to do some bugfixing. The ADCS team has also maganed to fix the problem they were having, so testing can also resume!

Fantastic news and updates! Happy to hear that the unit tests are helping fix bugs before they're hard to detect later on; that's the ideal scenario!

Refactoring of the existing functions is just about complete (barring some minor things which don't affect how the code runs -- those will be fixed after I've got all the code up and functional)! Additional news, the latest bugfix combined with some troubleshooting from the ADCS team has fixed the issues with the ADCS, so we're back up and running for testing again. Although for some reason I seem to have created two divergent branches in my attempts to rename the ADCSFirmware branch... which somehow still has the latest commits. I'll get on fixing that once I can figure out how it happened.

How's the progress of the testing? I'd love to see testing and finalize the structure of just a couple telecommands to minimize any reworking we have to do across all the telecommands if there are issues/opportunities for improvement.

Our next testing date will be Saturday the 20th, so we'll likely be testing the telecommands then.

Continuing along with this.....
Implementing the CTS1 telecommands is proving slightly more difficult than anticipated -- once my other pull request is merged I'll do a rebase (which I'll need to do anyways but will probably be painful) and then should be able to continue with this.
In other news, all of the packer function unit tests are complete and the functions pass the test! I caught a good few bugs in that, so it's really good that those are done.

So, as a whole, my to-do list for this looks like:

Write and test the CTS1 telecommands
Integrate the functions I've written with the memory module somehow (need to consult someone on this)
Fix up any comments or docstrings that aren't quite right
Minor function changes: ADCS_Init() for the CRC8, any other functions that are needed or wanted
Cleanup: removing the deprecated UART functions and duplicate I2C scanner function, etc

Can we please focus on implement 2 ADCS commands, with 2 associated telecommands, and all the other functions required to make this work? You can pick any 2 commands/functions. Let's ignore the rest until we get that merged into main.
We need to get something stabilized so we can divide up the rest of the work, or re-evaluate our base driver strategy.
Sorry the initial Issue was scoped so broadly; this will be better.

Well, that's definitely my first test case here. But I don't think you need to worry about the broad scope; once I have the first couple telecommands working, the rest (which is already nearly done) will be a piece of cake!

I've written something for all of the telecommands in the commissioning manual, and cleaned up a good chunk of the warnings. I won't be able to make the telecommands work until I next test with the ADCS test device in the cleanroom, so my next objective is to see what I need to do to integrate with the memory module / data downlink protocols for telemetry requests.

Can you first please create a really good PR with only about 2 ADCS commands, with 2 associated telecommands, and all the other functions required to make this work? You can pick any 2 commands/functions. And then can you please request a review on it so we can check through if there's any major opportunities for improvement with what you have so far?

I think I can do that, though I'm not sure how to split the functions via GitHub from the current branch so as to create a PR.


[Container app] Support new configuration parameters on java component

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

az containerapp env java-component
Support more flexible configuration updates with new parameters --set-configurations, --replace-configurations, --remove-configurations and --remove-all-configurations
az containerapp env java-component gateway-for-spring
Support --bind, --unbind with minor update
General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

containerapp

Please fix CI issues

PR title guidance: https://github.com/Azure/azure-cli/blob/f9a4685d6bfee8bd5b8eff867f40a7d674515dae/doc/authoring_command_modules/README.md#format-pr-title
[Containerapp] az containerapp xxx: xxxxx

PR title guidance: https://github.com/Azure/azure-cli/blob/f9a4685d6bfee8bd5b8eff867f40a7d674515dae/doc/authoring_command_modules/README.md#format-pr-title
[] means this change is customer-facing and the message will be put into HISTORY.rst. {} means this change is not customer-facing and the message will NOT be included in HISTORY.rst.
[Containerapp] az containerapp xxx: xxxxx

Title updated

/azp run

/azp run


Write plugin integration tests

This tracks implementation of integration tests for all plugins. Add your sub-issue here:

[ ] Issue 1...
[ ] Issue 2...

We have officially decided to yeet this.


Unable to update information in ARGOS_000002 BCO

Describe the bug
A clear and concise description of what the bug is.
Information in required fields is not saved after each update.
To Reproduce
Steps to reproduce the behavior:
[EXAMPLE STEP TEMPLATE BELOW: FILL IN INFO AND ADD/REMOVE STEPS AS NEEDED]
Example 1 --

Go to 'Extension Domain'
Scroll down to 'Extension Schema'
The second extension schema (i.e. ARGOS_000002 ExtDom.txt updated via the backend is not showing)

Example 2 --

Go to 'Usability Domain'
The updated title "Sudan Ebola genome assembly using MEGAHIT" is missing before the description paragraph

Example 3 --

Go to 'IO Domain'
The updated file name and URI are not saved

Expected behavior
A clear and concise description of what you expected to happen.
The above updated information that are missing need to be shown in this BCO, in order to proceed to final completion.
Screenshots
If applicable, add screenshots to help explain your problem.
[PASTE IMAGE HERE. OPTIONALLY ADD DESCRIPTION]
Desktop (please complete the following information):

OS: macOS
Browser: Safari

Additional context
Add any other context about the problem here.
 PUT N/A IF THERE IS NONE]

Fixed via UI


updater nonzero exitcode

it appears to have updated everything, but then it gets the message "crashed with exitcode -1073741819.
This is on my friend's machine, on my own this works normally. (she might be on a vpn, would that mess with this software?)

if the VPN is transparent for http(s) it won't make any difference. the Exit code is interesting though as I never throw anything that would cause it. What is their Java version?

java8 121 x64 JDK i believe.
its a very strange problem. I tested the command on command-line and it is indeed acting like it crashed. (windows pops up its thing about doing a diagnosis on the program that failed in an unusual way).
the weird thing is it finishes its update processing before crashing.

Having the same issue, same error log.
Happens to me but doesn't happen to my friend who is on the same VPN as I am. Also, another friend of mine has the issue and isn't on any VPN at all so I'm not sure that's the issue. We're all running Java 8 and using multiMC 0.5.0-945. I can send you logs and the files I'm working with if you want.

I used a workaround
I created an update.bat:
"%1" -jar UpdaterUpdater.jar "[config-url]" "PackInfo.cfg" "." "PackUpdate.jar"
echo "ERROR LEVEL OF UPDATE SCRIPT: %ERRORLEVEL%"
exit /b 0
then set the instance to execute "$INST_MC_DIR\update.bat" "$INST_JAVA" as the pre-launch command instead, feeding the java path for the instance to the batch file and allowing it to substitute a zero return value

I'm having the very same problem. I noticed the PackInfo.cfg that gets downloaded on first run only has the first line, in my case my configs...everything after that fails. On a second run without altering anything, things work as expected.
My workaround is just to supply that PackInfo.cfg with the 1 line in the exported instance, then whoever is importing it is basically doing a second run on it.
This thing is GREAT btw. I can't stand needing "Approval" for a private modpack on Curse or ATLauncher, and Technic's launcher is far too dumbed down and lacking in configureability.

that's some very interesting behaviour. one way to work around this would be to add an optional checksum to the start of the update config file although I'm still not sure why this happens.
@kencinder I started using mcupdater instead of packupdate. It's sadly not integrated into multimc but it has way more features than my little mess of java code here ^^

I deleted my comment because I misinterpreted the issue...sorted mine out.


Newly generated extension via yeoman erorrs in test suite on Windows

ToolVersion

VS Code1.13.1
Node6.11.0
NPM3.10.10
Windows8.1
Git2.13.2.windows.1

I followed the instructions via: https://code.visualstudio.com/docs/extensions/example-hello-world
After generating an extension project, I ran npm install then ran npm test and get the following error:
C:\Users\bcardarella\projects\boomer>npm test

><EMAIL_ADDRESS>test C:\Users\bcardarella\projects\boomer
> node ./node_modules/vscode/bin/test

### VS Code Extension Test Run ###
Current working directory: C:\Users\bcardarella\projects\boomer
Downloading VS Code into "C:\Users\bcardarella\projects\boomer\.vscode-test" from: https://vscode-update.azurewebsites.net/1.13.1/win32-archive/stable
Running extension tests: C:\Users\bcardarella\projects\boomer\.vscode-test\Code C:\Users\bcardarella\projects\boomer\test --extensionDevelopmentPath=C:\Users\bcardarella\projects\boomer --extensionTestsPath=
C:\Users\bcardarella\projects\boomer\test
Failed to execute tests: Error: spawn C:\Users\bcardarella\projects\boomer\.vscode-test\Code ENOENT
Tests exited with code: -4058
npm ERR! Test failed.  See above for more details.

I am not a regular Windows user (attempting to add Windows support to another extension) so I'm not quite sure what the problem is and how best to resolve. Considering a newly generated extension isn't working I would say something is wrong with my dev environment but its not clear to me what that would be.

Actually, this may not be a valid concern. It seems if I run the test suite via the debugger in VSCode it runs OK. However, this doesn't explain why npm test would fail. What context am I missing?

Moved to https://github.com/Microsoft/vscode-extension-vscode/issues/69


Works only on browser resize (Chrome Issue)

Hi, I have some weird issue where scrolling works on Firefox like a charm, but on Chrome it doesn't. On Chrome it works only if I resize window...
Here's my JS code
if ( jQuery(window).width() >736) { jQuery(function() {   jQuery.scrollify({     section: ".about-sec"   }); });

That's odd, are you seeing the same issue on the demo site in Chrome?

i have the same issue, worked great on chrome and edge, but in firefox doesnt work after you rezise the window or do some thing that resize the web.
I found a easy solution, in scrollify options use:
afterRender: function() {                 $.scrollify.update(); }


why HTTP/3 at all?

It seems the only real benefit is the avoidance of HTTP stalls - but given all of the infrastructure limitations in existence - anything over UDP seems unlikely. As the author of a major system that used UDP to avoid some of the same TCP drawbacks, I can confirm that it is a struggle using UDP over the internet.
So, why not just use HTTP/2 and then open multiple connections and bond them. Seems it solves the major problem that QUIC is trying to solve.

That's not a question for this document though - we're not the QUIC working group. We document HTTP/3 and QUIC. If you want to design another protocol then I salute you and wish you good luck.

Fair enough. It’s a shame the working group doesn’t have a commenting section, at least that I could find.

It has a mailing list for questions and discussions. It has a github repo for issues and pull-requets against the specs.


Add infinite scroll

@mareklibra please review
Fixes: https://github.com/oVirt/ovirt-web-ui/issues/23

please rebase, this needs to be properly verified

@mareklibra made rebase, please rebase

@mareklibra fixed app according to your comments, please review


Minimal event system

Looks like we are finally succumbing to the need to have some kind of event subscribe system. Here's an attempt at a minimal one.

Looks, want to merge this?