Security group not found in VPC

I'm receiving an error when trying declare a instance in a VPC subnet
[root@admin1001 ~]# puppet agent -t
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/local/rvm/gems/ruby-1.9.3-p551/gems/puppet-3.8.1/lib/puppet/settings.rb:1141:in `issue_deprecation_warning')
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Info: Caching catalog for admin1001.usw2
Info: Applying configuration version '1435777315'
Info: Checking if VPC USW1 exists in us-west-1
Info: Checking if subnet Admin subnet exists in us-west-1
Notice: Using ec2 data and code
Notice: /Stage[main]/Main/Notify[Environment]/message: defined 'message' as 'Using ec2 data and code'
Info: Checking if subnet DB subnet exists in us-west-1
Info: Checking if security group mysql exists in region us-west-1
Info: Creating security group mysql in region us-west-1
Notice: /Stage[main]/Riskiq::Dr::Mysql/Ec2_securitygroup[mysql]/ensure: created
Info: Checking if instance db1001.usw2 is running in region us-west-1
Info: Checking if instance db1001.usw2 is stopped in region us-west-1
Info: Starting instance db1001.usw2 in region us-west-1
Error: Security groups 'mysql' not found in VPCs 'vpc-5c7f643e'
Error: /Stage[main]/Riskiq::Dr::Mysql/Ec2_instance[db1001.usw2]/ensure: change from absent to present failed: Security groups 'mysql' not found in VPCs 'vpc-5c7f643e'
Notice: Finished catalog run in 3.75 seconds

Below is part of the manifest that sets up the security group and the instance.
ec2_securitygroup { 'mysql':
    ensure      => $ensure,
    description => 'Security group for mysql instances',
    region      => $region,
    vpc         => $vpc,
    tags        => {
      'Name' => 'mysql'
    },
    ingress     => [{
      protocol => 'tcp',
      port     => 3306,
      cidr     => '<IP_ADDRESS>/0',
    }],
}
ec2_instance { 'db1001.usw2':
    ensure            => $ensure,
    region            => $region,
    availability_zone => $avail_zone,
    image_id          => 'ami-57cfc412',
    security_groups   => ['mysql'],
    instance_type     => 't2.medium',
    key_name          => 'riskiq-primary',
    subnet            => 'DB Subnet',
    tags              => {
      'Name' => 'db1001.usw2',
    },
}

When I query the ec2_securitygroup resource, I get back results that imply the security group is assigned to the VPN
[root@admin1001 ~]# puppet resource ec2_securitygroup mysql
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/local/rvm/gems/ruby-1.9.3-p551/gems/puppet-3.8.1/lib/puppet/settings.rb:1141:in `issue_deprecation_warning')
ec2_securitygroup { 'mysql':
  ensure      => 'present',
  description => 'Security group for mysql instances',
  ingress     => [{'cidr' => '<IP_ADDRESS>/0', 'from_port' => '3306', 'protocol' => 'tcp', 'to_port' => '3306'}],
  region      => 'us-west-1',
  vpc         => 'USW1',
}

I'm missing something, but not sure what.

Is the subnet "DB Subnet" in the same VPC?
You could try and check with puppet resource ec2_vpc_subnet "DB Subnet" I think?
Also, what is the value of $avail_zone?
It could be the error message here is not specific enough.

$avail_zone gets set by a params class
class riskiq::dr::params {
  $ensure = 'present'
  $region = 'us-west-1'
  $avail_zone = 'us-west-1b'
  $vpc = 'USW1'
}

VPC
# puppet resource ec2_vpc
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/local/rvm/gems/ruby-1.9.3-p551/gems/puppet-3.8.1/lib/puppet/settings.rb:1141:in `issue_deprecation_warning')
ec2_vpc { 'USW1':
  ensure           => 'present',
  cidr_block       => '<IP_ADDRESS>/16',
  instance_tenancy => 'default',
  region           => 'us-west-1',
}

Subnet
# puppet resource ec2_vpc_subnet "DB subnet"
Warning: Setting modulepath is deprecated in puppet.conf. See http://links.puppetlabs.com/env-settings-deprecations
   (at /usr/local/rvm/gems/ruby-1.9.3-p551/gems/puppet-3.8.1/lib/puppet/settings.rb:1141:in `issue_deprecation_warning')
ec2_vpc_subnet { 'DB subnet':
  ensure                  => 'present',
  availability_zone       => 'us-west-1b',
  cidr_block              => '<IP_ADDRESS>/24',
  map_public_ip_on_launch => 'false',
  region                  => 'us-west-1',
  route_table             => 'DR Route Table',
  vpc                     => 'USW1',
}

I'm having the same issue while trying to launch an instance in a vpc using puppet open source, even though the security group is very much present.
Error: Security groups 'chef-launch' not found in VPCs 'vpc-XXXXXXXX'
Error: /Stage[main]/Main/Ec2_instance[test01.dev]/ensure: change from absent to present failed: Security groups 'chef-launch' not found in VPCs 'vpc-XXXXXXXX'

I have the same issue if I omit the 'subnet' attribute on my ec2_instance resources with Puppet OSE 4.2.1. If the 'subnet' attribute is set correctly, the instance is created without fault. However, this attribute is documented as being optional. I believe the issue is caused by the following line in lib/puppet/provider/ec2_instance/v2.rb, in determine_subnet
! s.tags.any? { |t| t.key == 'Name' }
If the ! is omitted, and subnet attribute on the ec2_instance is not set, the expected correct behavior is observed, of the first subnet being used, along with a warning about the ambiguous subnet choice.

I have encountered this error message and found a solution to my problem. It is probably not related to the problem you are having or the solution for you. I also have not debugged it to catch the problem in source, so I don't have a patch for my particular problem.
But for future reference if anyone encounters the same error message with the same cause as me:
The problem I was having is that the subnet had an empty 'Name'. This resulted in the same error message as described above. I was able to deduct this from @evidex 's message above.
Simply adding a name to the subnet solved my problem.

@garethr ,
I encountered the same problem (i.e. Error: Security groups ..... not found in VPCc). My manifest was very similar to what @hundredacres mentioned in the top.
Found out this happens when the particular subnet you try to use in the ec2_instance doesn't have a value set for its Name tag. It's hard to pinpoint the problem because the error doesn't mention about the subnet.
Thanks

I encountered this issue as well. The error message is misleading.
The issue I encountered was do to an invalid subnet ( I was using the ec2 id, and not the Tag Name ) not returning the id from determine_subnet()
subnet = determine_subnet(vpc_groups.keys)
if subnet.nil?
raise Puppet::Error,
"Security groups '#{groups.join(', ')}' not found in VPCs '#{vpc_groups.keys.join(', ')}'"
end
Suggest correcting error message.

Looks as though @DavidS has fixed this issue in 47091d4.

It'd be great if someone could validate the fix in the 1.4.0 release.

I'm getting this problem with v1.4.0 :(
luckily I found the workaround here.

@mvernimmen-CG which workaround did work for you?

Adding the subnet in the resource declaration. Then it works fine. Leaving it out means getting the "Error: Security groups 'xxxxx' not found in VPCs 'vpc-########'" message.

I just did a fresh new standalone install in order to try the puppetlabs-aws modules. I'm running a clean version of CentOs 7.2 with puppet 3.8.7 and all the updates installed. I followed the installation instructions and installed aws-sdk-core, retries and the puppetlabs-aws module.
So when I tried a simple ec2 instance creation with my AWS credentials export, I got the following error message:
Notice: Compiled catalog for ip-172-31-49-17.ec2.internal in environment production in 0.03 seconds
WARNING: jmespath gem requires json gem >= 1.8.1; json 1.7.7 already loaded
Error: Security groups 'default' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[my-instance-name]/ensure: change from absent to present failed: Security groups 'default' not found in VPCs 'vpc-0e038a6b'
Notice: Finished catalog run in 1.02 seconds

The content of the manifest file is:
ec2_instance { 'my-instance-name':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-d97897b4',
  instance_type => 't2.micro',
}

When I try the stack test example, I'm able to create all the security groups but not instances. Here is the output error:
Notice: Compiled catalog for ip-172-31-49-17.ec2.internal in environment production in 0.08 seconds
WARNING: jmespath gem requires json gem >= 1.8.1; json 1.7.7 already loaded
Notice: /Stage[main]/Main/Ec2_securitygroup[lb-sg]/ensure: created
Notice: /Stage[main]/Main/Ec2_securitygroup[web-sg]/ensure: created
Error: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[web-2]/ensure: change from absent to present failed: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[web-1]/ensure: change from absent to present failed: Security groups 'web-sg' not found in VPCs 'vpc-0e038a6b'
Notice: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Dependency Ec2_instance[web-1] has failures: true
Notice: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Dependency Ec2_instance[web-2] has failures: true
Warning: /Stage[main]/Main/Elb_loadbalancer[lb-1]: Skipping because of failed dependencies
Notice: /Stage[main]/Main/Ec2_securitygroup[db-sg]/ensure: created
Error: Security groups 'db-sg' not found in VPCs 'vpc-0e038a6b'
Error: /Stage[main]/Main/Ec2_instance[db-1]/ensure: change from absent to present failed: Security groups 'db-sg' not found in VPCs 'vpc-0e038a6b'
Notice: Finished catalog run in 5.60 seconds

I tried the subnet workaround without any success. Any help would be appreciate

It is finally working with the subnet parameter with a name specified. Note: before using the script, I set the name of all the subnet manually using the AWS dashboard.
ec2_instance { 'my-instance-name':
  ensure        => present,
  region        => 'us-east-1',
  image_id      => 'ami-d97897b4',
  instance_type => 't2.micro',
  subnet        => 'subnet-us-east-1',
}

In the aws web portal,
go to services -> Networking & Content Delivery -> VPC
in the side panel click on subnets there will be list of subnets with subnet id and the name may be left blank provide some name in those fields and use them as daveside suggested
"subnet        => 'subnet-us-east-1',"  in ur manifests. remember to check which zone subnet belongs to by click the subnet and checking the description


Updated README.md fixed github links

Github links were not correct, fixed them to the proper location.

Awesome! Thanks for the help!


Can orm2 create a table automatically?

I use Hibernate in J2ee, when the datebase has't table the framework can create table and when fields changed it can update datebase,  Can this be done?

It can manually create tables by calling .sync but does not do this automatically.
It had some initial work done on updating fields, but this functionality was never completed and is disabled.
I recommend using database migrations which are described in the readme. It is the only way to guarantee data integrity when columns change.

OK,Thanks


API call to help closing the "Download and Install Roblox" modal on the website

Hey,
There seems to be an API call from the official launcher that helps closing this modal whenever you've successfully launched a game

Doesn't really bother me that much but it feels unusual having to close the modal when I close the game to continue browsing the website.
From my initial observations I found that the website will poll an endpoint that's supposed to return client status every 3 seconds after a game's been launched. Apparently the player client doesn't make the player appears to have launched a game so it must be from the launcher.

In the requests from the image above, they all returned "Unknown".
I'll have to do some more digging with the official launcher to see how to replicate that request and close the modal.
Thank you for the great work!

Oh, I kinda forgot about that. Yeah, I should add that, thanks for reminding me.

Huh, thought the browsertrackerid was there for analytics only. Guess I was wrong.


Suggestion to start with a simpler introductory example

I suggest to start the article with a simpler introductory example:
Read a value from appsettings.json directly into a view
appsettings.json
{
 "Grandfather": {
   "Father": {
     "Child": "myvalue"
   }
 }

A View
@inject Microsoft.Extensions.Configuration.IConfiguration configuration
@{
     string myValue = configuration["Grandfather:Father:Child"];
}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ed756b9c-1d37-cd29-dbca-2838ddf152fb
Version Independent ID: 06064983-8ada-c25d-2adc-ffb4059978f2
Content: Dependency injection into views in ASP.NET Core
Content Source: aspnetcore/mvc/views/dependency-injection.md
Product: aspnet-core
GitHub Login: @ardalis
Microsoft Alias: riande

Just a quick note in case this becomes an actionable issue: It's fine to provide a different or new example anywhere, but let's (mostly) stick with gender-neutral examples. It would be sad to see things go back to the way that they were. https://github.com/aspnet/Docs/pull/2314

Good point @guardrex


ELISA assay run details - fix issue to restore display of run details information panel above plot

Rationale
As we are about to update the ELISA assay run details page, I thought it would be good to fix the current issue that was preventing the run details information panel from showing on the current run details page. This way we know where we are actually starting from before making changes.
Changes

simplify the data loading logic for the Ext4 store
fix JS error with Ext.util.Format.number instead of Ext4.util.Format.number

Almost forgot that a merge to 20.7 should have a triage approved issue open for it. Let me get that created now and a link added to this PR.


BHBC-2092

Overview

removing template configuration from database migration

Note: this branch is based off of a PR that removed security label DB objects.
Links to Jira tickets

BHBC-2092

Description of relevant changes

{List all relevant changes, in particular anything that will help the reviewers test/verify this PR}

PR Checklist
A list of items that are good to consider when making any changes.
The following SQL must be run in target promotional environment before applying this release:
delete from public.migration where name in ('20221206121332_update_summary_template_species.ts',
'20221105123456_update_templates_ids.ts',
'20221018121332_add_summary_template_species.ts',
'20221018121331_add_summary_templates.ts',
'20221005142000_deer_aerial_non_srb_templates.ts',
'20220916142000_elk_srb_non_srb_templates.ts',
'20220909191230_update_elk_trasect_and_distance_sampling_validation_schemas.ts',
'20220901133100_update_survey_validation_schemas.ts',
'20220301093900_update_sheep_validation_transformation.ts',
'20220228103100_update_goat_template_schemas.ts',
'20220224160300_update_moose_template_schemas.ts',
'20211216095022_update_moose_template_schemas.ts',
'20211206121200_update_transformation_schema.ts',
'20211202093900_insert_sheep_validation_transformation.ts',
'20211201093900_insert_goat_validation_transformation.ts',
'20211126135830_update_transformation_validation_schema.ts',
'20211020095230_update_validation_schemas.ts',
'20211015106029_transformation_schemas_2.ts',
'20211015105029_validation_schemas_2.ts',
'20210927010804_transformation_schema.ts',
'20210909000000_validation_schemas.ts'
);
Note: this list is not exhaustive, and not all items are always applicable.
Code

[ ] New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
[ ] I have avoided duplicating code when possible, moving re-usable pieces into functions
[ ] I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
[ ] My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
[ ] My code changes account for null/undefined values and handle errors appropriately
[ ] My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

Style

[ ] My code follows the established style conventions
[ ] My code uses native material-ui components/icons/conventions when possible

Documentation

[ ] I have commented my code sufficiently, such that an unfamiliar developer could understand my code
[ ] I have added/updated README's and related documentation, as needed

Tests

[ ] I have added/updated unit tests for any code I've added/updated
[ ] I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

Linting/Formatting

[ ] I have run the linter and fixed any issues, as needed
See the lint commands in package.json
[ ] I have run the formatter and fixed any issues, as needed
See the format commands in package.json

SonarCloud

[ ] I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

@cgarrettjones
Looks like the formatter is failing.
Could also remove the Dashboard page from the APP as well, and any related code, as I think it is no longer needed? Was meant to show projects with pending security reviews I believe.

removal of Dashboard being pushed in https://github.com/bcgov/biohubbc/pull/896.


Team kiwiz (Challenge-2)

Closing this PR as default template has been edited. Please check-in a separate .md file as per instructions in https://github.com/skill-a-thon


Can't keep the display settings?

When I stream the screen to my pad using the virtual screen in Sunshine Moonlight, I also want it to appear on pc monitor at the same time, so I use desktop extensions in my window display settings. But every time I run Moonlight, the settings reset, is there a way to fix this?

Can I make sure that the virtual screen is maintained even when the Moonlight is shut down? I don't like that the virtual screen driver is turned off and on.

Hello,

You can’t directly get the virtual screen to your main monitor without doing manual change. A workaround to do every time you start a streaming session is to mirroring or extend your desktop with the keys combination Windows + P and select the desired mode to get your monitors back.

I don’t understand why you want to keep the virtual monitor available when you don’t use it. First it consumes useless GPU/CPU/RAM ressources to display a non-existent screen that you will never use unless you stream this screen to another device.

But if you want to do this for any reasons, you have to do this manually until i add an option for this. But with my current tests, it’s not that easy to implement right now.


Update and fix Python matrixing

This package doesn't install anything in $PREFIX/lib/python*, but it turns out that it does depend on Python at run-time — as per #1. This PR causes us to matrix across Python versions properly. It also updates to a slightly newer upstream release.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Bracket

Added playoffSeries template and pages. I didn't want to mess around with the existing pages too much and there is some code difference between a normal series and a playoff series. There is a small amount of duplication in the templates+pages between series and playoff series. I think it's a low enough amount, it makes some sense that a series and playoff are shown differently, plus they have different routes. I also didn't want to re-write everything :X
Added a new page called bracket. This displays all of the series that exist for a defined season. It uses round and match_number to determine how to place the matches/series in the bracket.

Round determines which column the match goes into
Match number determines the order of the matches within that column.
Using incorrect numbers will moderately disfigure the layout of the bracket, but if done correctly it should look something like this.

In order for the bracket to resemble the challonge bracket someone has to make all the series. All admins have the ability to do so. Admins also see an edit tag on the bracket.

OLD PR can be found here

@kabobrocks @dambrisco Not sure why I felt the necessity to remake this PR, but alas.
I left in the pages and templates for the playoff_series. I didnt want to re-write all of my PR or mess with the existing pages too much. Plus they have different routes.
Lemme know what you think. It would be nice to get this out in time for this playoff as well

Discussed over slack updating the footer and also adding a link to bracket on the division hub

@kabobrocks @dambrisco Addressed your comments.


Will this mod be updated to 1.17?

Yes, it basically works as is for 1.17 as far as I can tell (tho the current release will crash due to the jabric.json).
I was gonna update it yesterday, but got caught up in other tasks.


fix: resolve redirect paths containing non-ascii characters

When using non-ascii characters in a URL, the redirect path fails upon upload. This encodes the URI to use encoded path symbols. For non-ascii paths this will make no change

Thanks for contributing!
I haven't had a chance to test this yet, but would it be better to call encodeURIComponent on redirectPath instead? Is it possible that redirectPath might contain characters such as "#" or "?", and if it does should these also be escaped?
How are your redirects being generated that they contain non-ASCII characters, is toPath always unencoded? Or are there situations where this change might result in double encoding?


[Azure Communication Services] update rooms doc

Learn Build status updates of commit e84db87:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/communication-services/quickstarts/rooms/get-started-rooms.md
:white_check_mark:Succeeded

articles/communication-services/quickstarts/rooms/includes/rooms-quickstart-azcli.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@joannajiang112628
Microsoft authors and contributors need to make content contributions through the private repository so the content can be staged and validated by the current validation rules.
After you make your changes in the private repo, review the articles on staging, and fix any validation issues, you can add the sign-off comment to let PR reviewers know that the updates are ready to be merged.
Read about authors working in the public repo for more information.
If you need help getting set up to work in the private repo, see Set up Git repository locally for documentation.
We'll close this PR. Thank you.


RTD build is broken

Can look at this, leaving as note as reminder.

I'm not sure what this means?
They appear to be populated?
https://googlecloudplatform.github.io/google-cloud-python/latest/storage-client.html

Sorry opened issue with customer next to me.
@daspecster realizing its' the read the docs docs that are missing.
https://google-cloud-python.readthedocs.io/en/latest/storage-client.html

Indeed, another example: https://google-cloud-python.readthedocs.io/en/latest/datastore-transactions.html
Latest build is green (but must be secretly not green): https://readthedocs.org/projects/google-cloud-python/builds/5028739/

@tseaver @daspecster We should tackle this. I'm not sure if there is another issue, but the RTD build has been b0rken for a few days:
https://readthedocs.org/projects/google-cloud-python/builds/
e.g.
https://readthedocs.org/projects/google-cloud-python/builds/5060236/

OK the fix is easy, we just need to get all subpackages on the same version of google-cloud-core. DERP!

This is a P0 issue that must be fixed ASAP. It's a poor user experience.
How can we avoid this with future google-cloud-core releases?

@bjwatson #3056 should do it AFAICT.

@bjwatson It's not the release, it's just a broken build.

Looks like it's still broken :(
https://readthedocs.org/projects/google-cloud-python/builds/5066476/

Jinx.
I think it's because of cached deps, so i'm blowing up the cache.

It was because of cached deps, but now it's because of an accidental missing comma in proto-google-cloud-pubsub-v1==0.15.0.
@lukesneeringer is on the case!

Waiting on an LGTM and I will push the packages.

Packages to be added / pushed to 0.15.1 (proto only):

[ ] datastore (0.90.1)
[ ] error reporting
[ ] functions
[ ] language
[ ] monitoring
[ ] pubsub
[ ] spanner-admin-database
[ ] spanner-admin-instance
[ ] spanner
[ ] speech
[ ] vision

Whoa that's a lot! Thanks @lukesneeringer

Sooner or later I am going to automate this... :-)

All launched except Speech.

Speech launched.

Builds still failing, but it's because the umbrella package refers to versions other than the ones in source (this is an argument against getting too far out of sync)

Okay. Let's make a concerted effort to get this across the finish line tomorrow morning.

Still b0rken but now it's not our fault: https://readthedocs.org/projects/google-cloud-python/builds/5071900/
pkg_resources.UnknownExtra: proto-google-cloud-datastore-v1 0.90.1 has no such extra feature 'grpc'

@lukesneeringer and I are aware of this, but we weren't aware it'd keep RTD from building

At least the /latest/ RTD is showing content now: https://googlecloudplatform.github.io/google-cloud-python/latest/datastore-usage.html

@bjwatson I was looking at /latest/ the other day and it was fine? Was there a time when it wasn't showing content?

@bjwatson That isn't RTD, this is: http://google-cloud-python.readthedocs.io/en/latest/datastore-usage.html

Ugh, you're right. Sorry, I'm juggling too many things at once right now.
Is there a plan to resolve the remaining issue?

@daspecster Yes.

Yeah, I know what needs to happen to fix that.

Ok, cool.

Correction: It is every proto- package, so after I fix it I will have to regenerate all of them, and every GAPIC.

Got it. Will we make grpc an option for every proto- package?

Yeah, that is exactly what needs to happen. We thought we were thorough when we changed grpc to optional but clearly I made a small mistake here.

Another note: A high priority needs to be that RTD builds from CI. We need to know about failures without having to check RTD.

Correction to my correction: Just Datastore.

@lukesneeringer We do build docs on CI, we just use different flags than RTD uses.

We had one build pass a couple days ago but we're back to this it looks like.
pkg_resources.UnknownExtra: proto-google-cloud-datastore-v1 0.90.1 has no such extra feature 'grpc'

See: https://readthedocs.org/projects/google-cloud-python/builds/5080674/

@dhermes You said this is fixed, correct?

As of https://readthedocs.org/projects/google-cloud-python/builds/5081679/ it seems to be fixed (a new build after it also passed: https://readthedocs.org/projects/google-cloud-python/builds/5081815/)

Is it fair to say that documentation links are broken again?
https://googlecloudplatform.github.io/google-cloud-python/latest/pubsub/usage.html throws a 404 error

@chlela No, that URL no longer has documentation (Pub/Sub recently had a very large change, docs included).


First Setup of dynamic PKI

Short Summary:
This PR enforces an mTLS connection between a Remote cluster (SKR) and the control-plane cluster (KCP).
The docs have been updated and thus can be used for testing this PR.
Please build your own docker image and use it for deploying the KLM, since the latest image does not include the changes from this PR. Or you can also use my build image to test it.
# Use this in Step 4
make local-deploy-with-watcher-secured IMG=jaythedevil666/klm:latest

The Setup
In the KCP the SREs will take care of deploying the cert-manager by Jetstack. For the local setup a dedicated cert-manager will be deployed.
To sign each Certificate for the KymaCRs, we will use a self-signed RootCA Certificate. The Issuer and RootCACert setup can be found here.
We have a ClusterIssuer which will issue the RootCACert. When this certificate is created and signed, the Issuer watcher-selfsigned-issuer will use this certificate as CA to sign all certificates for the KymaCRs.
(This is an adoption of a popular cert-manager architecture, can be found here - This has been clarified by our Security experts and the SREs)
The Istio Gateway also needs a certificate to use strict mTLS. It will use the issued self-signed RootCACertificate. For this to work, a small sync has been implemented in the Watcher Reconcile loop, which checks for the secret and copies/updates/deletes it to the Istio default namespace. This has to be done, since the certificates for Istio Gateways always need to be stored in the Istio default namespace (in our case: istio-system). And the Issuer of cert-manager always issues the certificates in the same namespace as the Issuer recites. Thus, the Issuer setup and all kyma certificates would be in the Istio namespace. I think, we should separate those domains, and only Istio relevant component should be in the istio-system namespace and the resources for KCP should be in the kcp-system namespace. Thus, this small sync is needed. The other way, as said, would be to have all Istio resources and cert-manager resources in one namespace, which does not make too much sense in my opinion.
How does it work?
In the reconciliation loop of a KymaCR, the loop will check if a Certificate exists on the KCP cluster for the currently reconciled KymaCR. If not, if will create a cert-manager Certificate. The deployed cert-manager will pick up the certificate, will create a CertificateRequest, and the deployed Issuer will create and sign the certificate using the RootCACert.
On the next step it will check if the secret of the Certifiacte is ready, if yes it will fetch the Secret, and copy it into the manifest of the watcher. Thus, it will directly be installed with the runtime-Watcher and thus get updated on each reconcile loop - Certificate Rotation automatically working. For the general certificate rotation the cert-manager will take care of. I used the default values for the cert-manager, but this can be discussed in future (default: expires after 90days, will be rotated after 60 days).

/hold

Not ready fro review, just converted from draft to normal PR to trigger pipelines for testing

/retest

/unhold

The docs have been updated and thus can be used for testing this PR. Please build your own docker image and use it for deploying the KLM, since the latest image does not include the changes from this PR. Or you can also use my build image to test it.
# Use this in Step 4
make local-deploy-with-watcher-secured IMG=jaythedevil666/klm:latest

I believe we have an image build in our PR job which you can use instead:
make local-deploy-with-watcher-secured eu.gcr.io/kyma-project/lifecycle-manager:PR-340

/test pull-lifecycle-mgr-lint

/test pull-lifecycle-mgr-lint

The local testing was working fine for me 💯 But I was getting the following error in the lifecycle-manager logs:
E0206 09:32:53.5106651 reflector.go:140] pkg/mod/k8s.io/client-go@v0.26.1/tools/cache/reflector.go:169: Failed to watch *v1.Certificate: unknown (get certificates.cert-manager.io)

Also, the SKR watcher logs need to be updated to reflect that it's connecting via https to 9433 port instead of 9080.

I will create an issue for the KSR-Watcher to resolve this, since this is an issuer from the runtime-watcher repo
Regarding the log error in the KLM, I will double check why this happens

Thank you for double checking 👍
About the logs, I meant the logs in the local testing guide not on the SKR-watcher side.


Unable to login to angular 9 application using msal v1.3.3 in chrome incognito mode

Hi,
We are using msal library v1.3.3 in an angular 9 application and we are unable to login to the application in chrome incognito mode. We are using azure b2c authentication. Below is the configuration.
auth: {
clientId: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx',
authority: 'https://login.microsoftonline.com/tfp/tenant/policyname',
validateAuthority: true,
redirectUri: 'http://localhost:4200/',
postLogoutRedirectUri: 'http://localhost:4200/',
navigateToLoginRequestUrl: true
},
cache: {
cacheLocation: 'localStorage' as 'localStorage',
storeAuthStateInCookie: isIE
},
system: {
logger: new Logger(loggerCallback, {
correlationId: '1234',
level: LogLevel.Verbose,
piiLoggingEnabled: true
})
}
We are seeing the below error.
GET: https://login.microsoftonline.com/common//discovery/instance?api-version=1.1&authorization_endpoint=https://login.microsoftonline.com/tfp/tenant/policyname/oauth2/v2.0/authorize  is a bad request
Redirect Error:  Error: could not resolve endpoints. Please check network and try again.
The same application works fine on other browsers.
The application works well in chrome incognito mode when I turn off the feature 'Block third-party cookies'.
Could someone point to a solution programmatically as we cannot ask our clients to unblock third-party cookies.
Thanks.

Latest Chrome (83) blocks third party cookies by default, I think the only solution Microsoft suggests is to switch to MSAL 2.0 which implements a new authentication mechanism.
I feel your pain as well

@corrspt  How to switch to MSAL 2.0 ?

@rv90 Unfortunately, it is expected that the library may not work correctly when third-party cookies are disabled. MSAL.js v2.0 mitigates those issues by switching to the auth code flow. MSAL-Angular has not yet been updated to work with MSAL 2.0, so in the meantime you can switch to using MSAL 2.0 directly if you no longer want to use MSAL.js v1.3.3.
@vlafranca Here are the steps to migrate to 2.0 from 1.x: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/v1-migration.md

@jo-arroyo thx for infos, unfortunately we are using B2C tenants, and 2.0 does not support B2C yet according documentation.
I ended up with executing acquireTokenPopup in case acquireTokenSilent fails. It's quiet a good solution as the popup has the same behavior as the iframe.

This issue is also being tracked here #2042

Closing as a duplicate.


Trigger Dashboard resync if appbinding changes

Signed-off-by: Tamal Saha<EMAIL_ADDRESS>

LGTM!


Flow doesn't work with npm v5.4.0

Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
There is no problem with npm 4.x and 5.3.0, only with npm 5.4.0.
Environment
node -v: v8.4.0
npm -v: v5.4.0
npm ls react-scripts: I tried with 1.0.10, 1.0.11 and 1.0.12
npm ls flow-bin: I tried with 0.52.0 and 0.53.1
Operating system: macOS Sierra v10.12.6
Steps to Reproduce

In Terminal:

$ create-react-app test-flow
$ cd test-flow
$ npm install --save-dev flow-bin

Add "flow": "flow" to the scripts section of your package.json.
Run npm run flow init
And you will see the error:

><EMAIL_ADDRESS>flow /Users/admin/Sites/test-flow
> flow "init"

internal/child_process.js:325
    throw errnoException(err, 'spawn');
    ^

Error: spawn EACCES
    at _errnoException (util.js:1041:11)
    at ChildProcess.spawn (internal/child_process.js:325:11)
    at exports.spawn (child_process.js:493:9)
    at Object.<anonymous> (/Users/admin/Sites/test-flow/node_modules/flow-bin/cli.js:17:3)
    at Module._compile (module.js:573:30)
    at Object.Module._extensions..js (module.js:584:10)
    at Module.load (module.js:507:32)
    at tryModuleLoad (module.js:470:12)
    at Function.Module._load (module.js:462:3)
    at Function.Module.runMain (module.js:609:10)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>flow: `flow "init"`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>flow script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Flow worked good a few days ago (with react-scripts 1.0.10), but now it doesn't work (even with react-scripts 1.0.10).

I was running into this same error after upgrading to Flow 0.54 today, but I was seeing really inconsistent success even between various versions of npm and flow-bin. I believe this issue is probably caused by https://github.com/npm/npm/issues/18324

Ran into the same issue, yarn global add flow-bin worked well.

I ran into the same issue and overcame it by running chmod +x node_modules/flow-bin/flow-osx-v0.54.0/flow.

Thank you @sandersky your workaround/solution worked.

Thank you @sandersky it worked for me as well.

Thank you @sandersky for the suggestion.
Looking forward to the fix as I don't want to be running chmod +x .... everytime :wink:

PSA: npm 5.4.1 has been released and it fixes this issue for me. It's npm i npm@latest -g time.

had same problem on mac with npm 5.4.0.  updated npm to 5.5.1 then uninstalled flow and reinstalled now all good.


The method 'resize' isn't defined in a superclass of 'BoxGame'.

In box-game.dart, at this point there is an error complaining thet the super class Game doesn't have any resize method.
void resize(Size size) {
    screenSize = size;
    super.resize(size); <---
  }

I just realized this is related to the versions of flutter and flame...
I don't know why everything changes so much in such a short period of time...so much so that nothing will compile.
Great tutorial though, thanks

I just realized this is related to the versions of flutter and flame...
I don't know why everything changes so much in such a short period of time...so much so that nothing will compile.
Great tutorial though, thanks

I think they changed names of quite a number of variables.
And they now use Vector2 instead of Size, so instead of .width and .height, it should now be .x and .y
late Vector2 screenSize;
@override
void onGameResize(Vector2 canvasSize) {
screenSize = canvasSize;
super.onGameResize(canvasSize);
}
Src: https://github.com/flame-engine/flame/issues/517


peek_definition mappings are broken (again)?

Describe the bug
Hi, I just did the usual update of my plugins, and now my bindings for peek_definition window don't work anymore; there was no change in my config.
The responsible commit seems to be commit b8d210f, since if I go back to the commit before that, things work as expected.
My config:
beacon = {
  enable = true,
  frequency = 16,
},
definition = {
  edit = '<C-c><cr>',
  quit = 'q',
  split = '<C-c><C-x>',
  tabe = '<C-c><C-t>',
  vsplit = '<C-c><C-v>',
},
finder = {
  keys = {
    expand_or_jump = '<C-c><cr>',
    vsplit = '<C-c><C-v>',
    split = '<C-c><C-x>',
    tabe = '<C-c><C-t>',
    quit = { 'q', '<ESC>' },
    close_in_preview = '<ESC>',
  },
},
outline = {
  win_width = 60,
  preview_width = 0.5,
  keys = { -- defaults; for reference
    expand_or_jump = 'o',
    quit = 'q',
  },
},
ui = {
  border = 'rounded',
},

Steps to reproduce

Update lspsaga to the latest version
Open a peek_definition window
Try to use your custom keybindings and they don't work

Expected behavior
I expect my configured keybindings to work as before.
Can we please have some tests for this as it keeps braking. I REALLY, really like this plugin, but it's hard to troubleshoot things every time there's an update.
Neovim version (nvim -v)
0.9.0
lspsaga commit
83d78e2
Terminal name/version
wezterm 20230408-112425-69ae8472

I tried <C-c><cr> (open) and <C-c><C-v> (vertical split) and none of them seemed to work

open peek_window then :verb nmap <C-c><CR>

sry I can't reproduce it . works fine in my test .

Sad 🙁

open peek_window then :verb nmap <C-c><CR>

It gives no mapping found for some reason. Even if I do :verb nmap q it shows that it's bound to record macro

because that commit just do delete map when window close.  you opened window then do  verb command then the map not  mapped to lspsaga .so it's wired.  and a test on my local like gif it works fine. so idk . another tip is the definition is refactored in next version.  The current implementation has some confusion.

the definition is refactored in next version

So, I guess that's not live yet, is it?

@glepnir I tried the following:
https://gist.github.com/farzadmf/3f922d8ec7aaafe09854763b060b7649
And it seems to solve the issue. Didn't create a PR since I'm not totally sure if that's the right fix, but let me know what you think

I had the same question. What's interesting is that the same config and Neovim version I use in both Windows and WSL but Windows works properly but WSL not.

I'm having the same issue. After update my keybindings don't seem to work.

@glepnir Seems like 2 other people have confirmed the same issue (and that the change works for them). I'm going to create a PR for it


Default port 10000 overlaps with juju-backup-all

By default hardware-observer uses port 10000 which overlaps with another Solutions Engineering project https://code.launchpad.net/juju-backup-all. In our deployments, juju-backup-all usually runs on physical machines so almost every time we run into this conflict.
I'm aware of juju config hardware-observer exporter-port.
Can the defaults be updated so there's no overlap between these two projects?

This seems simple enough to fix. Is there any preference or can I just pick a random default port which isn't 10000 (say 9000)?

Maybe we can try to allocate a port here.
https://github.com/prometheus/prometheus/wiki/Default-port-allocations

Maybe we can try to allocate a port here. https://github.com/prometheus/prometheus/wiki/Default-port-allocations

10200 looks good, what do you say? Doesn't seem to be taken up by any other default port allocations.


Xnero: Watch articlehot.com

Xnero requests the watch of the watch_keyword articlehot\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

articlehot\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Cody Gray in Charcoal HQ


Document API unit tests are not run by CI because they still use JUnit 4 features

Powermock/Mockito versions are ones that are compatible with JUnit 4, however the runner for CI is now JUnit 5. So the unit tests can be run locally, but do not get picked up and run by CI.

Followup: Is there even a version of Powermock that is compatible with JUnit 5?

Looks like you can use a JUnit 4 runner?
https://github.com/powermock/powermock/issues/929

@dimas-b didn't you fix this?

@dimas-b didn't you fix this?

This is fixed by #527

This is fixed by #527


Increase unit tests code coverage for install page controller

Current coverage is 83.66% (diff: 100%)

Merging #469 into master will increase coverage by 1.83%

@@             master       #469   diff @@
==========================================
  Files            18         18
  Lines          2069       2167    +98
  Methods         371        371
  Messages          0          0
  Branches        181        181
==========================================
+ Hits           1693       1813   +120
+ Misses          376        354    -22
  Partials          0          0

Powered by Codecov. Last update 82f22d1...586ed4c


[Question] What are you using for for marketGrowth in the multipliers table?

https://github.com/boknows/cFIREsim-open/blob/master/cfiresim.sql#L42-L185
Guessing the S&P, U.S. Total, or World Total Stock?

Hi Peter--the FAQ for the old version of cfire (http://gator3089.hostgator.com/~boknows/docs/faq.php) says it comes from Schiller's data, found at http://www.econ.yale.edu/~shiller/data.htm .
Although Schiller doesn't state which S&P index he's using on the link above, it appears to be the S&P 500 (or similar, you'll have to read in Schiller's work to find how he constructs his ersatz indexes before hand).
Hope this helps!
=r2u


IXSWarpshipOS not showing up in CKAN client

IXS Warpship OS was not showing up in CKAN anymore. I suspect because it uses the same directory name as its predecessor (Sofia's Warpship mod). Took the opportunity to update dependencies and add KSPInterstellarExtended and the preceding Warpship mod as a conflict.
Summary of the changes:

Changed mod's directory to be different from its predecessor's (Sofia's Warpship mod)
Added predecessor's mod as conflicting
Added KSP Interstellar Extended mod as conflicting, it uses same DLL references.
Added Fendrin's Spacedock mod as suggestion after removing purely structural spacedock parts from IXSWarpshipOS
Added Community Resource Pack as a dependency

Failing because USI mods are not updated to 1.2.1. Waiting on roverdude to update

#rebuild


vscode-tslint: Cannot read tslint configuration - 'linter.findConfiguration is not a function'

Bug Report

TSLint version: 4.0.0
TypeScript version: 2.0.10
Running TSLint via: Visual Studio Code 1.7.1, TSLint extension 0.5.40

TypeScript code being linted
empty .ts file

with tslint.json configuration:
{
	"rules": {
		"no-unused-expression": true,
		"no-duplicate-variable": true,
		"no-duplicate-key": true,
		"no-unused-variable": true,
		"curly": true,
		"class-name": true,
		"semicolon": ["always"],
		"triple-equals": true
	}
}

Actual behavior
TSLint should work
Expected behavior
vscode-tslint: Cannot read tslint configuration - 'linter.findConfiguration is not a function'
I did some googling for this problem, but only found resolved issues for older versions.

https://github.com/Microsoft/vscode-tslint/issues/123


Writing tutorials 2.

No code was changed in this PR. I want to see the new documentation online, so I'm skipping the tests.


fix the install using apt snippet

Proposed changes
Change the install snippet using apt (docs changes)
the original install snippet was wrong, the apt repository don't holds packages named docker-ce
Unreleased project version (optional)
Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 39f2ba7246ebc220fd6e2716b47fef518beb8223
https://deploy-preview-8813--docsdocker.netlify.com

Nice catch and thanks for contributing!

Since when? I just followed this on a arm64 cluster I was setting up and had to remove docker and install docker-ce because of this seeminly incorrect change resulting in the wrong version of docker being installed. My ubuntu-disco laptop also shows docker-ce as present. Maybe the OP didn't add the docker repo?
pfeerick@pfeerick-E6430:~$ apt-cache madison docker-ce
 docker-ce | 5:19.03.1~3-0~ubuntu-disco | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages
 docker-ce | 5:19.03.0~3-0~ubuntu-disco | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages
pfeerick@pfeerick-E6430:~$ apt-cache madison docker
    docker |      1.5-2 | http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/universe amd64 Packages
    docker |      1.5-2 | http://mirror.aarnet.edu.au/pub/ubuntu/archive disco/universe i386 Pack
pfeerick@pfeerick-E6430:~$ apt-cache madison docker-ce-cli
docker-ce-cli | 5:19.03.1~3-0~ubuntu-disco | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages
docker-ce-cli | 5:19.03.0~3-0~ubuntu-disco | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages
pfeerick@pfeerick-E6430:~$ apt-cache madison containerd.io
containerd.io |    1.2.6-3 | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages
containerd.io |    1.2.5-1 | https://download.docker.com/linux/ubuntu disco/stable amd64 Packages

Yes, this change doesn't look correct; the docker and docker-compose packages are likely coming from the ubuntu package repositories, not from the official docker repositories.
I'll open a PR to revert this change once I'm back at my computer

opened https://github.com/docker/docker.github.io/pull/9154 to revert


Improved CSS of navbar

Resolves #1105

Hi, thanks for the PR but I would prefer to hold off on reviewing any PR before a decision is made on the issue, which at this point hasn't been agreed on whether the navbar should be changed or not. In addition the original author of the issue indicated that they would like to work on the issue so they would get priority for working on this if it is decided that we will change the navbar.
I'm closing this PR for now. Thanks.

Okay, @limzykenneth. Thanks for your time though.


Initial pass at fragment interpolation

Simple proof of concept for the ideas discussed in apollostack/eslint-plugin-graphql#19 - just to open up for discussion / feedback.

See my comment here: https://github.com/apollostack/eslint-plugin-graphql/issues/19#issuecomment-254295602
I think using interpolation is not the right approach. Unfortunately, both Relay and Lokka use it, but I think it makes building great tools harder, and deviates from "just GraphQL".
And if we do build interpolation, I think it should preserve fragment names, so:
const todoItem = gql`
  fragment todoItem on Todo {
    name
    completed
  }
`

gql`{
  todos {
    ...${todoItem}
  }
}`

Should result in:
todos {
  ...todoItem
}

fragment todoItem on Todo {
  name
  completed
}

This will make it easier to analyze queries on the server-side, rather than losing the fragment name information. For example, it will be easier to find where that fragment came from in the client-side code.

And if we do build interpolation, I think it should preserve fragment names, so:

Yep, this currently does do that, it just uses the fragment name. The ... is being added internally but there's no reason that couldn't change.

I think using interpolation is not the right approach. Unfortunately, both Relay and Lokka use it, but I think it makes building great tools harder, and deviates from "just GraphQL".

I don't think it really deviates much from "just GraphQL", it just leverages the power of tagged templates to allow you to compose fragments rather than referencing them by a string name, which might not scale as well to larger codebases.
Also, If you need to change the fragment name, you currently need to update in every place it's used throughout the codebase / referenced in the query, rather than in just one place.
I am going to look a bit further into how difficult it'll be to get ESLint working with this.

Oh, oops - I misread the code.
I think it would be fine to add interpolation features that preserve the fragment names, but I do think it makes it harder to generate stuff like persisted queries. If you have a build tool, let's say you see:
const query = gql`
{
  todos {
    ${todoItem}
  }
}
`;

Now you need to understand the module system to understand what fields todoItem might have. If you don't use interpolation but use the fragment name directly, then it's really easy to find the matching fragment, wherever it may be in the code.
IMO having globally unique fragment names in the app makes like pretty easy. Let's say you have a fragment:
const myFrag = gql`
  fragment todoItem on Todo { completed, text }
`;

Now if you rename that fragment, it's actually really easy to update all queries, you just search your codebase for ...todoItem.
Again, with interpolation it's not that easy - you need to follow module imports/exports, etc.
Is there a benefit to using interpolation that I'm missing, over just using unique fragment names? From where I'm sitting, it seems like it actually makes it harder to work with the code.

I guess the way I'm thinking about it is more similar to how the Facebook GraphQL tools work, as outlined here: https://github.com/graphql/graphql-js/pull/456
They just treat GraphQL queries and fragments as an app-global namespace, so that you can store and validate queries really easily without even looking at app code at all.

Actually now that I've looked at the graphql-js issue you linked and looked a bit more into relay2 and how they're betting on fully static queries, I'm not sure this is the best idea. I think I'll look more into into approaches for that cli helper you mentioned.


[1][Easy][App] Default PearAI Theme

Solarized Dark for dark mode
Solarized Light for light theme

Change name to PearAI Dark and PearAI Light.
These should be set as default theme for PearAI

Can I try this? Will get onto it tomorrow


Add bootstrapSelfManagedAddons to Cluster EKS Provider spec

What problem are you facing?

Currently, EKS Cluster creation defaults to installing several components: CoreDNS, kube-proxy, and VPC CNI. Announced by Amazon yesterday, here, a new CLI flag is available, bootstrapSelfManagedAddons, to disable the automatic deployment of these components.
Creating an Amazon EKS cluster
By default, EKS installs multiple networking add-ons during cluster creation. This includes the Amazon VPC CNI, CoreDNS, and kube-proxy.
If you'd like to disable the installation of these default networking add-ons, use the parameter below. This may be used for alternate CNIs, such as Cilium. Review the EKS API reference for more information.
aws eks create-cluster --bootstrapSelfManagedAddons false

we depend on the TF Provider: https://github.com/hashicorp/terraform-provider-aws/issues/38156 and this open PR here: https://github.com/hashicorp/terraform-provider-aws/pull/38162

Great that Amazon addresses this! This would be a high priority issue for us since we currently have to work with all kinds of workarounds in order to get rid of the Amazon VPC CNI and reinstall a new CNI afterwards.

Looks like bootstrapSelfManagedAddons attribute was introduced with the Terraform provider v5.58.0 version bump.


Support react 15.6: bug version detection causes usage of React.Proptypes

versions:
{
    "glamor": "^2.20.25",
    "glamorous": "^3.23.2",
    "global": "^4.3.2",
    "next": "^3.0.0-beta15",
    "prop-types": "^15.5.10",
    "react": "^15.6.1",
    "react-dom": "^15.6.1"
}

Relevant code.
https://github.com/paypal/glamorous/blob/55b3f07f8b9926ecf0576821614c0306bc50af2e/src/react-compat.js#L6
if (React.version.slice(0, 4) === '15.5') {

What you did:

I used the newest version of React + glamorous
This causes this warning to appear:

Suggested solution:
if (ParseFloat(React.version.slice(0, 4)) >= 15.5) {

Ah yes! This is a great first timers only issue! Let me prep it :)

Hi there! 👋
This is a "first-timers-only" issue. That means that we will only accept a pull request from someone who's never contributed to open source before! :tada: If that's you, read on. If that's not you, spend the time instead setting up an issue like this for someone else in one of your own projects :wink:
So here's how things are going to go, I'll explain clearly what needs to happen for this issue to be closed. You "claim the issue" by commenting on here saying that you'd like to work on it as soon as you're able to start. Then you follow the steps I've outlined. Feel free to ask any questions if you get stuck along the way.

Make sure to claim the issue by commenting that you're working on it right now.
Probably the most useful thing you could do before getting started is to watch this free video course. That will help you understand the terms and concepts of the following steps.
Read the contributing guidelines
Fork the repo
Clone your fork
Create a branch for your changes (git checkout -b pr/fix-react-version-detection)
Open the directory in your favorite text editor
Normally, this is the part that you'd write a test to verify the bug exists, or enable one that I've written for you, but testing this particular bug is more work than it's worth, so we'll skip that part.
Open the file src/react-compat.js and change this line to: if (ParseFloat(React.version.slice(0, 4)) >= 15.5) {
Run npm start contributors.add and follow the prompt (you're contributing code)
Commit your changes following our commit message format (you can use npm start commit if you want, but I normally just write it manually). You can do something like: git commit -am "fix(compat): improve react version detection"
Push your changes to your forked repo
Open a pull request
Fill out the prefilled PR description
Wait patiently for a response
Address any feedback you receive and push updates (if necessary)
Get merged
Celebrate and tweet! Woo! :tada:

Thanks so much for your contribution! We're here to help you land it!

I would like to work on it

I would like to work on it :)

Super! @Oalbacha was first so we'll leave this one to you! But maybe there's something we could find for @srajappa too 🤔

@kentcdodds  :) thanks for helping us first timers out :) I will be in a look out here and in twitter

How are things coming @Oalbacha? How can we help?

Hi Kent,
I will be working on this and finishing it hopefully by tomorrow. I am in Dubai and it is 1140pm. Unless these is a deadline and it needs to be finished tonight? Please advise.

No worries! You're good. This can be done tomorrow no problem. I'll need another maintainer to merge it though because I'm on a family vacation for a week starting tomorrow.
One important lesson in open source is never do any more than you're able/want to do. We can wait until you can get to it. If it's high enough priority for someone, they can fix it. That mentality is how you avoid becoming a slave to OSS.

@Oalbacha take your time and do not hesitate to ask for help if you need it.
I'll be around during the week end.
Cheers and thanks a lot

Thanks guys! I will get on it right away first thing inthe morning. Will keep you posted if I hit a brickwall :-)

Oh no! I totally just merged a pull request from someone else thinking it was @Oalbacha 😞 I'm so sorry about that @Oalbacha. This particular issue has now been resolved. But if I think of something else I'll reach out to you first! That was my mistake.

No worries, thanks! As long as I get the next one for sure :)

@oalbacha Opening issues is just as valuable of a contribution as the PRs that solve them. 😀 Thank you!
If you want to take on a PR that helps glamorous there are some issues that are great first PRs on the repo to build the glamorous website: https://github.com/kentcdodds/glamorous-website/issues
Take a look, claim one if you think it's interesting, and ask questions if you need any guidance. Thanks! 🙌


Fields Queried are not returned in the same order

In the below image the products field is a Dataloader hence execution is deferred until the end. Do notice in the query at line 4 where the products is supposed to be resolved.

Interesting I'll take a look @e-lobo . Is field order important to you though? I'm trying to understand when this might be problem.

e the products is supposed t

not a issue although according to the specs i guess it should resolved as per the query..

@e-lobo it should be fixed in 0.1.1


Social Media Accounts should be unique

Expected behavior
A social media account should be unique. If somebody try to create an already existing social media account he/she should get a warning flash message with a link to the user who already has it.

Interesting obstacle to this: Phoenix uses a "safe" typing when embedding things in a template. Anything not "safe" will be escaped, so you can't have functional html in a function translate to the template without first making sure you mark it as "safe". I use this is several locations, such as the pagination page link helper function. However all form errors are automatically run though gettext, and it just so happens that gettext doesn't expect to receive "safe" tuples rather than plain binaries, preventing me from embedding an <a> element in the error message. Right now I have the message saying Someone has already claimed this account
What this boils down to is I either implement a very hackish solution to bypass the existing error helpers in this specific case, or I spend a lot of time investigating a solution that works. Either way, I'm creating a 1.2 issue for the second half of this issue. There were no problems encountered making social media accounts unique, just make sure there are no duplicate accounts in the database before the migration, or else you'll have problems.


go.dev: Searching for package "is" returns no results.

What is the URL of the page with the issue?
https://pkg.go.dev/search?q=is
What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0

Screenshot

What did you do?
I searched for the package name, "is".
What did you expect to see?
I expected to see a link to this page: https://pkg.go.dev/github.com/matryer/is
What did you see instead?
A page with zero results.

Thanks for the feedback! The reason is because "is" is a stopword and being filtered out. We'll work on fixing this - I added it to our search feedback tracking issue #38766.


Design Nunjucks API for notification banner component

What
Work out what the API for the notification banner component should look like.
Where possible, it should be consistent with the APIs for our existing components.
There are a few things we need to consider:

Do we want a single option to set the 'type' of alert? For example, setting type: 'error' which then adds the modifier class for the style and also sets the role? Or do we just set both explicitly in every example in the Design System?
If we do have a single option to set the 'type', do we also allow users to override the role?
Should we make it callable?

Depends on

Making a decision about whether the notification banner is a single component.

Why
By designing and agreeing the API for the component upfront we can ensure that it behaves consistently with our other components.

I picked this up but then saw that there's another meeting booked to firm up the final details. The below is where I got to in case it's helpful when this is picked up:
Different options for Nunjucks API
1. Require team to set attributes/styles etc. manually
This is more flexible but increases the risk of team making a mistake by missing an attribute etc. However it also means that they would hopefully spend some time trying to understand what attributes etc. are most appropriate for their use case.
{{ govukNotification({
  style: "red/green/blue", //could also be "error/success/information"
  role: "region/alert",
  tabindex: "-1",
  initialfocus: true/false,

  titleText: "",
  titleHtml: "",
  text: "",
  html: "",
  classes: "",
  attributes: {}
}) }}

2. Set all attributes/styles etc. based on one option
Macro sets appropriate role, tabindex, initialFocus based on type.
{{ govukNotification({
  type: "red/green/blue",

  titleText: "",
  titleHtml: "",
  text: "",
  html: "",
  classes: "",
  attributes: {}
}) }}

2. Set all attributes/styles etc. based on one option but allow them to be overridden
Would make it easy to use a variant but is more flexible than 2.
{{ govukNotification({
  type: "red/green/blue",
  role: "region/alert", // to override default
  tabindex: "-1", // to override default
  initialfocus: true/false, // to override default

  titleText: "",
  titleHtml: "",
  text: "",
  html: "",
  classes: "",
  attributes: {}
}) }}

Discussed in a meeting, I think we settled on Option 3 as the preferred option. It might need some tweaking if we change the design of the banner to this:


vscode started 7 processes and took up 200+M memory even with NO files opened

VSCode Version: Code 1.18.1 (929bacba01ef658b873545e26034d1a8067445e9, 2017-11-16T18:32:36.023Z)
OS Version: Windows_NT x64 10.0.16299
Extensions:

Extension
Author (truncated)
Version

python
ms-
0.8.0

cpptools
ms-
0.14.4

csharp
ms-
1.13.1

Steps to Reproduce:

just start vscode, and no files opened;
the task manager shows that it started 7 processes and took up 200+M memory!
if I open any other files, more processes begins working.

I don't know weather it is normal or a bug.

This is normal, VS Code is a multi-process application.


slab/stair infestation and block datagen

adds infested variants for stairs, slabs, and walls, and tag infested variants for fences and fence gates. also there is datagen if you want to use it but it doesn't iterate over the block registry or anything so you can just ignore it

Wow, thanks for the contribution, I will review this to make sure everything works correctly :)

I will merge this once I'm finalizing the next major update.

Fantastic Work! I made a fix for wooden stairs and an edit to account for the bamboo set of blocks. Other than that, great work!


Czech font coding

Hi, I have builded a prototype your HA Switch and is working with my Home Assistant.
Now, I tried edit a HMI file with Nextion Editor and I used a font generator with coding ISO-8859-2 with czech letters, as a "ěščřžýáíéúů", I replaced the first four font positions with the same size, but new codding, I change coding in Device settings.
Then I generated a new tft file, load to display.
Now, if I use texts for buttons with czech diacritics, on display in buttons I have a "loose tea"
I thing, that coding of mqtt messages have a limits, but I dont know, where I can set it if is possible.
Please, have somebody any idea?
Thank you

Closing as this repo is not being maintained.  Check here for the updated project!


Consider support for multiple levels of submenu

While I don't like it, it would make the script more useful to more people if this supported multiple levels of submenus. That said, doing then must not come at the expense of being able to make "mega menus" that show nested lists within the top-level submenu. Therefore, the secondary submenu feature would need to be configurable in a way that makes it opt-in.

I'd really appreciate support for multi-level menus. The accessibility of this offering is great - I'm a blind developer supporting blind end-users, so this is vital for me. However, I have multiple projects that need to create multi-level menus dynamically by reading in an XML file that defines the interface and this is where Clicky falls short.

I third this (no pun intended). This would be a fantastic addition and I would use this script even more.

I'm working on a website right now that could use this. It's a mega menu where clicking on the top level links toggle open the submenu but inside the submenu are 2nd and 3rd level links.
In my design, in this case, I just want the top level to open links. The second level parents should just display the 3rd level link below it and nothing else. But they themselves are links so they should also not turn into buttons.

@ajplopez I'd love to make it easier to handle that, although there is one thing you can do to make that easier. Take a look at the "Custom Submenu Selector":
<ul class="clicky-menu" data-clicky-submenu-selector=".clicky-menu > li > ul">
    <!-- menu items -->
</ul>```

Doing that will only target the first level of nested menus as hidable submenus. You'll still need to do a bit of work to reset some of the sites (`visibility: visible` for sure), but that at least gets you past the script trying to show/hide nested/tertiary submenus.

@mrwweb Yes! Sorry, I realized after what I needed so I deleted that last comment. Got it working great.

I'm working on a new project where this would be super useful.

I've thought about this for a long time and am closing this issue with no plans to add the feature. For folks seeking this, I strongly recommend considering a mega menu as an alternative.


XR Remoting does not work [XR SDK, 2019.x]

Describe the bug
XR Remoting silently fails when using XR SDK in 2019.x.
No errors are thrown. The device XR remoting window also says that the device has successfully connected.
To reproduce

Follow the XR SDK setup instructions: https://microsoft.github.io/MixedRealityToolkit-Unity/Documentation/GettingStartedWithMRTKAndXRSDK.html
Set up all packages as stated in the instructions, with the versions listed below
Connect your device with XR Remoting
Hit Play
Observe that no remoting occurs. Head tracking does not occur, the headset display is blank. The editor acts as if there is no remoting active at all.

Expected behavior
The head pose is shown in the editor, and the view is correctly rendered to the display. Hand tracking + eye tracking should also work.
Screenshots

Your setup (please complete the following information)
Package setup:

XR Plugin Management - Version 3.2.10
Windows XR Plugin - Version 2.1.6 preview 3
XR Legacy Input Helpers- - Version 2.1.4

The MixedRealityToolkit component is using the DefaultXRSDKConfigurationProfile.
Unity version:

Tested on 2019.3 and 2019.4, both fail to work.
MRTK 2.4.

Target platform (please complete the following information)

HoloLens 2

Additional context
The XR remoting setup works great in 2018.x with the legacy XR stack.

Marking as External, as this is almost definitely a Unity-side bug. I'll dig in.

Any news on this?

Same problem here🙁
Tested with Holographic Remoting Player <IP_ADDRESS> app and two project:
Unity 2019.4.2f1, XR Plugin Management 3.2.13, Windows XR Plugin 2.2.0
Unity 2019.4.0f1, XR Plugin Management 3.2.10, Windows XR Plugin 2.1.5

Same issue here.
However, if I uninstall the "Windows XR Plugin" and "XR Plugin Management" packages and I switch to the deprecated built-in XR API, it works as expected.

Update: it looks like the editor takes the XR settings from the Windows Standalone build. Please ensure Windows Mixed Reality and Initialize XR on Startup are checked under the standalone settings:

It's being investigated as a doc / workflow issue on the Unity side, but this should resolve it.

I'm not sure this is the same issue or not, but I can't use XR Remoting.
I set Windows Mixed Reality in Plug-in Providers checked for 'Standalone' platform, but XR Plugin Remoting panel still indicates alert.
Unity Ver: 2019.4.12f1
Windows XR Plugin: 2.3.0
XR Plugin Management: 3.2.16
MRTK: 2.5.0

I set Windows Mixed Reality in Plug-in Providers checked for 'Standalone' platform, but XR Plugin Remoting panel still indicates alert.

I believe that info block is always visible, even if you have the settings set up correctly. Are you unable to connect?

I didn't try, but panel of Remoting is showing alert like above and there is no combobox to select device(Hololens1 and 2 are the candidates). Still, can I connect?

I tried. But it seems not to work. Instead of that, Mixed reality portal waked up.

From one of my engineers on Slack:
(Working on HoloLens 2 with unity 2019.4.16, latest Remoting App on HL2, MapsSDK SampleProject that includes MRTK etc. Also tried on a blank project with XR SDK and WMR plugin).
So does "Remote to Device" work for play mode in the Unity Editor? I've been working with older projects for a while and the "legacy" holographic remoting works flawlessly. This new one doesn't ever seem to work for me. I've never been able to get the XR SDK Windows Mixed Reality Remote to Device to work.
After I hit "Connect" it says Remoting connect returned: True and no other errors/messages. The connection status is "Connected" but disconnects after I end each play session.
I often get this error: [XRInputSubsystem] A device disconnection with the id  has been reported but no device with that id was connected.  In play mode.
I was able to actually see my unity scene on the HL once after I changed the bitrate setting but it's inconsistent (this only occurs in my blank project). Still no tracking here either.
Any help would be greatly appreciated.

Any help on this? We'd like to adopt the new ecosystem, but we can't dev without remoting. Thanks

After I hit "Connect" it says Remoting connect returned: True and no other errors/messages. The connection status is "Connected" but disconnects after I end each play session.

That sounds like the currently expected behavior. Can you confirm the Windows Standalone XR Plug-in Management settings are enabled for WMR?

That sounds like the currently expected behavior.

The disconnection after play has ended is not the issue I'm facing. Though, thank you for clarifying that it's not a bug.

Can you confirm the Windows Standalone XR Plug-in Management settings are enabled for WMR?

Yes it is.
The primary issue I'm having is that once connected and in play mode I don't see anything. Head rotation / position is not tracked. The game window shows a black screen. I also often see an error message like this being spammed with different IDs:
[XRInputSubsystem] A device disconnection with the id has been reported but no device with that id was connected.

This happens 98% of the time.
The other 2% of the time (after messing with bitrate, audio, and video) I'm able to see the scene rendered on the HL and in the game window. No head tracking so I had to rotate the camera in the editor.
I appreciate the support!

I'm also having trouble with Remote to Device. Unity's Windows Mixed Reality windows fails to connect with the message:
Connection Failure Reason: None
I'm using MRTK 2.4.0, Unity 2019.4 and HoloLens 1. According to this thread:
https://forum.unity.com/threads/hololens-1-windows-xr-plugin-remoting-not-working.827970/
due to Microsoft not providing certain APIs and libraries, remoting on XR SDK is limited to HoloLens 2.
Could you please confirm this?

I'm also having trouble with Remote to Device. Unity's Windows Mixed Reality windows fails to connect with the message:
Connection Failure Reason: None
I'm using MRTK 2.4.0, Unity 2019.4 and HoloLens 1. According to this thread:
https://forum.unity.com/threads/hololens-1-windows-xr-plugin-remoting-not-working.827970/
due to Microsoft not providing certain APIs and libraries, remoting on XR SDK is limited to HoloLens 2.
Could you please confirm this?

Could you please confirm this?

I can. Windows XR Plugin only supports remoting to HoloLens 2.

I'm going to close this one out. The most common resolution has been to double check your Standalone XR Plugin Management settings. Unity has also defaulted to connecting automatically when you hit play, so if that doesn't work, reverting to a manual connection might help as well.


Failed to install elasticsearch in docker

Got this error while trying to setup ES in docker for dev:
Failed to install lmenezes/elasticsearch-kopf/1.2, reason: failed to download out of all possible locations..., use --verbose to get detailed information
Wondering if either of you saw this while working on your own boxes.

This time through i had no trouble, save with docker itself.


[firebase] Problem when run after upgrade Flutter to 2.0.4

Hi,
After run flutter upgrade to version 2.0.4 (latest) and run my app i get this errors:
/Users/paulo/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_crashlytics-1.0.0/ios/Classes/FLTFirebaseCrashlyticsPlugin.h:8:9: 'Flutter/Flutter.h' file not found

/Users/paulo/Developer/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-1.0.2/ios/Classes/FLTFirebaseCorePlugin.h:8:9: fatal error: 'Flutter/Flutter.h' file not found
#import <Flutter/Flutter.h>
        ^~~~~~~~~~~~~~~~~~~
1 error generated.
2 errors generated.
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Constructing build description
Could not build the application for the simulator

Can anyone have any help?

@paulo-coutinho
There's similar open issue describing your case, https://github.com/FirebaseExtended/flutterfire/issues/5660
Please follow-up there for updates.
Closing this as duplicate.


Couple fixes

*Issue:*https://github.com/bcgov/entity/issues/22109 and https://github.com/bcgov/entity/issues/22106
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

/gcbrun


Discontinuity in TEWK data FTT:Tr

The historical shares data has a discontinuity between 2017 and 2018. This is particularly acute for the US, but is also visible in other countries. I'm computing the stock of cars by age group, and this poses some problems there:

Any chance this has to do with the total fleet size estimates, i.e. is there a jump going from history to simulation period?

The FTT:Tr data is now updated to 2022, so it's not a jump from history to simulation. The issue is RFLT, which sees this jump in the input files. I imagine there may have been reclassification of what constitutes a car (given that the US has loads of van-like huge cars, that may have been freight before). Where do we get RFLT?

I believe RFLT is based on a Gompertz equation that takes in GDP per cap, saturation levels of vehicle ownership, and estimated parameters. We plug those projections in as an exogenous input.


Add [Richard Barnett] #personal GBEFEX…UO6UDL

Address: GBEFEXVXLIOKYUCROOL5DD5PFSQN65IO64N7JRTSLBEFPTSYFWUO6UDL
Tags: personal
Title: Richard Barnett
Requested by @aerogrudge

@Aerogrudge we do not tag/label personal wallets in the stellar.expert database . With over 7 million accounts that would not be possible. We hope you understand.
Please feel free to reopen this issue if there is something else involved.
Looking Towards The Future With You,
Rob TheCryptoHobbyist


Update "show password" checkbox to use Stimulus

Fixes #3087.
This is my first issue -- please let me know of any feedback, especially with controller/target naming.

@aalmazan thanks for your contribution! Is there any chance we'll see you at the PyCon sprints in May?

@di Thank you for the feedback! I must have missed a few things while going through Stimulus's docs. Thank you for pointing them out. Changes are commited on: 7a0de64.

@di  Ah, apologies. Didn't pay attention that the checkbox was on the other pages. These should now be updated, as well as the other 2 requested changes.

Thanks @aalmazan!

Thanks, @aalmazan! Would you like a suggestion for a next issue to work on?