No issues just follow up

I have installed both of your add-ons and are working fine.  It would be nice to add the charging limits if you were going to do so.  That way I don't need to create a fork.  There is a Emporia Vue in my breaker panel that tracks power fot the circuits that are not montiored by SHP.  Such as 240 appliances.  The CT clamps are on the two input mains too.  So I get the total grid power and all circuits (SHP & Emporia Vue) .  Took a while to get it all setup.  I would have never got this far if it wasn't for your sensor and dashboard examples.
My question 2 was about updating the SHP from HA.  You answered that in your respose to question 3.
I figured it would take a lot of work to replace mqtt.  As long as it keeps working no reason to change.
I just started using HA.  There is a lot to learn about how it all works.
Thanks again.

Just got the update for the powershell add-on.  Thanks for adding the charging and discharging limits.

No worries. I've noticed a quirk of how it works when setting the value using MQTT. Obviously there's a delay between the setting being made and the polling of the add-on to get the new value, if you just wait for the next polling cycle of the add-on, it does get updated but that can take up to 5 minutes, which isn't ideal.
I had planned to simply add another action to the YAML to update the value of the add-on's number entity but for whatever reason, the action does exactly nothing and there's a message in the HA log saying "referenced entities either missing or unavailable."
Clearly, they are not missing and are very much available, but it doesn't work and I've no idea why - could be a HA bug for all I know.

How that the SHP and Delta Pros 99.9% configured in HA, it's not a big deal not being able to updating them from HA.  Since I will continure to use the phone app and updating is not a frequent thing.
This has been a hugh learning experience.  Can't thank you and others enough who have worked hard to get this put together.
How to dust off the powershell brain cells and do more experimenting. Along with learning python.

I take back what I said about updating from HA.   I have discovered that is earier that doing it on HA rather than the phone app.


Cannot select text without focusable container when Dialog is open

🐛 Bug report
Current behavior
As discussed in discussions/805.
Unable to select text when a dialog is open when the text is not in a focusable container.
Steps to reproduce the bug
This is the demo code from the Reakit site:
import { Button } from "reakit/Button";
import { useDialogState, Dialog, DialogDisclosure } from "reakit/Dialog";

function Example() {
  const dialog = useDialogState();
  return (
    <>

Hello Joe!

      <DialogDisclosure {...dialog}>Open dialog</DialogDisclosure>
      <Dialog {...dialog} tabIndex={0} aria-label="Welcome" hideOnClickOutside={false} modal={false}>
        <Button onClick={dialog.hide}>Close</Button>
      </Dialog>
    </>
  );
}

Reakit website:

CodeSandbox https://rxk92.csb.app/ :

Expected behavior
Should be able to select text.
Possible solutions
Add tabIndex={-1} to the text or a parent of the text.
Environment
Please, run the command below inside your project directory.
System:
    OS: Linux 5.9 Arch Linux
    CPU: (8) x64 Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz
    Memory: 2.74 GB / 31.30 GB
    Container: Yes
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.19.1 - ~/.nvm/versions/node/v12.19.1/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 6.14.8 - ~/.nvm/versions/node/v12.19.1/bin/npm
  Browsers:
    Brave Browser: unknown
  npmPackages:
    react: 16.10.0 => 16.10.0
    react-dev-utils: 8.0.0 => 8.0.0
    react-dom: 16.10.0 => 16.10.0
    reakit: 1.3.0 => 1.3.0

This should be fixed in the latest version.


missing class HarvestingTimeStat

What steps will reproduce the problem?
1. No build ( missing class HarvestingTimeStat )
2.
3.

What is the expected output? What do you see instead?
Correct build

What version of the product are you using? On what operating system?

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 8 Oct 2012 at 2:46

This has likely been fixed since then. Please reopen if necessary.


saas: create token

saas: creating a token
assumptions

user has purchased an offering, and sales cycle has finished
enterprise and tenant are not critical pieces for creating an account or signing in
no external identity providers yet
user has signed in
user has already created at least one tenant and changed their view to that tenant

overview
after a user has signed in and creating at least one tenant they can then create api tokens that are associated with tenants.
design details

on token creation, they get the value one time only can not access it again

creating a token
user provided
all required

name
id

recorded data

time created
name
id
value

Issue moved to chef/platform-auth #3 via ZenHub

Issue moved to chef/platform-auth #4 via ZenHub


InvalidCloudWatchLogsRoleArnException

When I run apply, I get the following error message:
* aws_cloudtrail.default: InvalidCloudWatchLogsRoleArnException: Access denied. Check the trust relationships for your role.
	status code: 400, request id: ABCDEFG-d217-4b86-b34b-2a8a41ca4ea7

The code I'm running is a direct copy/paste from your example.

`# See https://github.com/cloudposse/terraform-aws-cloudtrail-cloudwatch-alarms
data "aws_caller_identity" "current" {}
provider "aws" {
region = "${var.region}"
Make it faster by skipping something
skip_get_ec2_platforms      = true
skip_metadata_api_check     = true
skip_region_validation      = true
skip_credentials_validation = true
skip_requesting_account_id  = true
}
This is the module being used
module "cloudtrail_api_alarms" {
source         = "git::https://github.com/cloudposse/terraform-aws-cloudtrail-cloudwatch-alarms.git"
region         = "${var.region}"
log_group_name = "${aws_cloudwatch_log_group.default.name}"
}
Everything after this is standard cloudtrail setup
resource "aws_s3_bucket" "default" {
bucket_prefix = "cw-bucket-${var.region}"
region        = "${var.region}"
}
resource "aws_s3_bucket_policy" "default" {
bucket = "${aws_s3_bucket.default.id}"
policy = <<EOF
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "AWSCloudTrailAclCheck20150319",
"Effect": "Allow",
"Principal": {"Service": "cloudtrail.amazonaws.com"},
"Action": "s3:GetBucketAcl",
"Resource": "${aws_s3_bucket.default.arn}"
},
{
"Sid": "AWSCloudTrailWrite20150319",
"Effect": "Allow",
"Principal": {"Service": "cloudtrail.amazonaws.com"},
"Action": "s3:PutObject",
"Resource": "${aws_s3_bucket.default.arn}/AWSLogs/${data.aws_caller_identity.current.account_id}/*",
"Condition": {"StringEquals": {"s3:x-amz-acl": "bucket-owner-full-control"}}
}
]
}
EOF
}
resource "aws_iam_role" "cloudtrail_cloudwatch_events_role" {
name_prefix        = "cloudtrail_events_role"
assume_role_policy = "${data.aws_iam_policy_document.assume_policy.json}"
}
resource "aws_iam_role_policy" "policy" {
name_prefix = "cloudtrail_cloudwatch_events_policy"
role        = "${aws_iam_role.cloudtrail_cloudwatch_events_role.id}"
policy      = "${data.aws_iam_policy_document.policy.json}"
}
data "aws_iam_policy_document" "policy" {
statement {
effect    = "Allow"
actions   = ["logs:CreateLogStream"]
resources = ["${aws_cloudwatch_log_group.default.arn}::log-stream:"]
}
statement {
effect    = "Allow"
actions   = ["logs:PutLogEvents"]
resources = ["${aws_cloudwatch_log_group.default.arn}:log-stream:*"]
}
}
data "aws_iam_policy_document" "assume_policy" {
statement {
effect  = "Allow"
actions = ["sts:AssumeRole"]
principals = {
  type        = "Service"
  identifiers = ["cloudtrail.amazonaws.com"]
}

}
}
resource "aws_cloudwatch_log_group" "default" {
name_prefix = "cloudtrail"
}
resource "aws_cloudtrail" "default" {
name                          = "cloudtrail-${var.region}"
enable_logging                = "true"
s3_bucket_name                = "${aws_s3_bucket.default.id}"
enable_log_file_validation    = "false"
is_multi_region_trail         = "true"
include_global_service_events = "true"
cloud_watch_logs_role_arn     = "${aws_iam_role.cloudtrail_cloudwatch_events_role.arn}"
cloud_watch_logs_group_arn    = "${aws_cloudwatch_log_group.default.arn}"
depends_on                    = ["aws_s3_bucket_policy.default"]
}
output "sns_topic_arn" {
value = "${module.cloudtrail_api_alarms.sns_topic_arn}"
}
output "dashboard_individual" {
value = "${module.cloudtrail_api_alarms.dashboard_individual}"
}
output "dashboard_combined" {
value = "${module.cloudtrail_api_alarms.dashboard_combined}"
}
`

@Jamie-BitFlight any idea why it might not be working?

Yes, I think it’s because of the change I made to the resources in the policy today.
It should be a quick fix. Sorry guys. I’ll be online in about 10 hours and will fix it then.

@oddietaco I have just submitted a PR for the fix.
But in your code you can hopefully just swap the current "aws_iam_policy_document" "policy" for this one.
data "aws_iam_policy_document" "policy" {
  statement {
    effect  = "Allow"
    actions = ["logs:CreateLogStream"]

    resources = [
      "arn:aws:logs:${var.region}:${data.aws_caller_identity.current.account_id}:log-group:${aws_cloudwatch_log_group.default.name}:log-stream:*",
    ]
  }

  statement {
    effect  = "Allow"
    actions = ["logs:PutLogEvents"]

    resources = [
      "arn:aws:logs:${var.region}:${data.aws_caller_identity.current.account_id}:log-group:${aws_cloudwatch_log_group.default.name}:log-stream:*",
    ]
  }
}

Closing for now. Please reopen if the problem persists.


Reenable more tests; fix a bug

Reenable the HostCRDWildcards test
Add a unit test for hostglob_matches, which is the internal function that decides whether DNS glob match
Fix a bug in hostglob_matches revealed by said tests
Also, reenable the demo test, which verifies that we can use docker run to run the demo

These were XFailed during the 2.0-EA cycle, but should never have been allowed to stay that way.

[x] I made sure to update CHANGELOG.md.
[x] This is unlikely to impact how Ambassador performs at scale.
[x] My change is adequately tested.
[x] I didn't need to update DEVELOPING.md

Note that I'd written an Envoy-compatible hostglob_matches python function in https://github.com/datawire/apro/pull/1923


"Address already in use" when trying to start DB

Hello,
So I have been using mariadb4j for my junits, and its really great! thanks for that!
So what I have is multiple test classes which all use this mocked mysql db to test different things.
In my pom.xml, I make sure all the tests run synchronously so only one test uses the mock every time.
It works well most of them time - but I had a failure saying:
16:48:05.782 [Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mysqld: 2019-02-11 16:48:05<PHONE_NUMBER>34240 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use
16:48:05.797 [Exec Stream Pumper] ERROR ch.vorburger.exec.ManagedProcess - mysqld: 2019-02-11 16:48:05<PHONE_NUMBER>34240 [ERROR] Do you already have another mysqld server running on port: 50108 ?

What I have is a class extending ExternalResource which has before and after.
This those before and after methods should run per test method in each class.
private DBConfigurationBuilder builder = DBConfigurationBuilder.newBuilder()
            .setPort(0).addArg("--character-set-server=latin1");
private DB db;

@Override
    protected void before() throws Throwable {
        db = DB.newEmbeddedDB(builder.build());
        int count = 0;
        boolean success = false;
        while (count < ATTEMPTS && !success) {
            try {
                db.start();
                success = true;
            } catch (Exception e) {
                count++;
                System.out.println("Attempt " + count + " out of " + ATTEMPTS);
                if (count == ATTEMPTS) {
                    throw e;
                }
            }
        }

        db.source(schemaPath);
  }

@Override
    protected void after() {
        try {
            db.stop();
        } catch (ManagedProcessException e) {
            e.printStackTrace();
        }
    }

I figured the after method will make sure to stop the DB before the next test starts, but from the error What I understand is that a previous mock instance didn't stop and there is a collision in the ports used for the mock (I use port 0 to take an available port).
I there anything I can do to solve this? I seems to work most of the time, but I get failures sometimes.
Using version 2.3.0.
Thanks!

What I have is a class extending ExternalResource

@OfekCyberX did you see that the just released MariaDB4j v2.4.0 includes a cool new MariaDB4jRule JUnit rule which @yiftizur contributed?
You can probably just use that?
OK to close this issue?

@OfekCyberX maybe the MariaDB4jRule after() method will stop test run if stopping the DB isntance fails... I does not solve the issue of why a DB instance may fail to stop, but at least you will not try to start a new one while there is one running...

@vorburger thanks for your answer.
This issue still happens to me when using MariaDB4jRule.
Error is
2019-02-17  9:30:53<PHONE_NUMBER>86016 [Note] Server socket created on IP: '::'.
2019-02-17  9:30:53<PHONE_NUMBER>86016 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 98: Address already in use
2019-02-17  9:30:53<PHONE_NUMBER>86016 [ERROR] Do you already have another mysqld server running on port: 47838 ?

The way I use this class is, I have another class extending MariaDB4jRule which has a static variable for the DBConfigurationBuilder with port 0 (to detect a free port on the File System).
public class MysqlMockResource extends MariaDB4jRule {

    private static DBConfigurationBuilder builder = DBConfigurationBuilder.newBuilder().setPort(0);

I use this class with @Rule annotation in my test classes.
Now, the class had failed test, for example, had 13 tests in it, so what happens is that the port is set only once per class, because its the configuration is static.
But - for each test method the before and After methods are called, so the db starts and stop every test, and the port stays the same for all the test methods in the class.
Maybe this is what causing the issue? What is the best practice to using MariaDB4jRule , because I keep getting this error of "Address already in use".

I have another class extending MariaDB4jRule which has a static variable

but why? It's not clear to me what you are trying to achieve...
... would you like MariaDB4j to create a fresh new DB for:

each @Test annotated method
once for each class which has @Test annotated methods (but shared among all such methods)
one single one shared among all of your test classes

So for 1. you can use the MariaDB4jRule as is; for 2. may be making the rule field static helps (not tested), and for 3. I'm guessing a little bit more new work would be needed, probably a separate new rule, or a flag - something like what it seems like you are trying to achieve with that static...
@yiftizur may or may not be motivated to help further with this?

For #2, use this class as a @ClassRule and then it will be created before all tests, and stopped after all tests... But that is assuming you're OK with handling data between tests...

@vorburger @yiftizur I thought about using @ClassRule, but it doesn't work together with PowerMockRunner, and I need it.
https://stackoverflow.com/questions/38772027/powermockrunner-does-not-apply-junit-classrules
So ideally I would want to init it once for class, and clear it between test methods - but can't use @ClassRule.
So, I used regular @Rule, but I keep getting the "Address already in use" error - which to me sounds like an issue with the mariadb mock not stopping fully.
It doesn't happen always, but it does, so I am looking for a fix that will handle this reoccurring error.

using @ClassRule, but it doesn't work together with PowerMockRunner

oh. But that's perhaps a pretty... "exotic" combination? MariaDB4j is more IT and PowerMock isn't.
Unfortunately I personally won't the time to help further for this - but others in the MariaDB4j user community who may be reading this issue may want to chime here, so leaving this open; close it when you figured out how to solve your problem! Best of luck.

@OfekCyberX Can you use the MariaDB4jRule as it is with the constructor:
@Rule MariaDB4jRule db = new MariaDB4jRule(0);
The for each test, the db will be created on a random port, and even if the previous test db cleanup didn't finish cleanly (for some reason - maybe worth checking if there are any db connections hanging or anything of that sort), the next test will use a different port....
If you need the DB process to be created once for the entire class, and run with the powermock runner, did you try the suggestion in that stackoverflow thread (using PowerMockRunnerDelegate to use the JunitRunner) ?
If all fails, maybe simply use the DB directly in the Class Setup?
`
public class TestDBTest {
private static DB db;

@BeforeClass
public static void setupDB() throws ManagedProcessException {
    DBConfigurationBuilder builder = DBConfigurationBuilder.newBuilder().setPort(0).addArg("--character-set-server=latin1");
    db = DB.newEmbeddedDB(builder.build());
    db.start();
}

@AfterClass
public static void stopDB() throws ManagedProcessException {
    db.stop();
}

@Test
public void test1() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test2() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test3() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test4() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test5() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test6() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test7() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test8() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test9() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test10() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test11() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test12() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test13() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

@Test
public void test14() {
    System.out.println(db.getConfiguration().getURL("foo"));
}

}
`

@OfekCyberX could #95 be useful for you re. this?


inital checkin

@kr1sp1n I added the required refinements. Please check again.

@kr1sp1n Added the missing link. Anything else? ;)


Deployment of custom rooms to Heroku

Description
The Heroku button is great for a very quick PoC that shows us briefly what #Matrix can do but now I wanna make deepers tests with it.
I tried deploying manually (with Heroku CLI) by following the variables.env file instructions and I just can't make it work with Heroku deploys. Neither docker build nor heroku container:push allow us to use the env_file at build. I tried editing docker-entrypoint.sh file to source the env_file at run time but with no success whatsoever.
I see there is an issue with instructions to add variables manually in Heroku dashboard but we should really have a way to setup things with code.
Steps to Reproduce
First Try

Create variables.env file as per instructions.
edit docker-entrypoint.sh file to source variables.env at runtime.
Run heroku container:push web
Run heroku container:release web
If you run heroku logs --tail you'll see that the environment variables were not loaded. None of them.

Second Try

Instead of creating variables.env, edit heroku.yml and add variables to setup > config
Same results.

Expected Behavior

Environment variables should be detected and setup should be properly executed.

Current Behavior

No setup variables are detected. I can't create custom rooms neither setup Google App Id.

Suggestion

Update documentation to allow us setup #Matrix in environments without Docker-Compose.

Hi, @sidneydemoraes Thanks for all the explanations.
Could you try to follow this Heroku Documentation. If Works feel free to Open a PR improving our documentation about this issue.


Disable image upload during setup for non persistent file storage

closes #5550

passes config.fileStorage into gh-profile-image component
does not render input tag if fileStorage is set to false

@jason I have set the initial fileStorage value to true to match the default value of fileStorage but it can still be overridden by passing the value into component. Let me know if that is not sane

Nope, seems like what we want to me :+1:


export ES7 class and writting a comment with the word "from"

Hi,
I have an issue when formatting this code:
export class myClass{
  execute() {
		//comment from me
  }
}

If I remove either "export" or "from", all is working fine.
My test comes from sublime text 3 using jsfmt:
{
  // autoformat on save
  "autoformat": true,

  // array of extensions for autoformat
  "extensions": ["js", "jsx", "sublime-settings"],

  // options for jsfmt
  "options": {
    "preset": "jquery",
    "indent": {
      "value": "  "
    },
    // plugins included
    "plugins": [
      "esformatter-jsx"
    ],
    "jsx": {
      "formatJSX": true, //Duh! that's the deafault
      "attrsOnSameLineAsTag": false, // move each attribute to its own line
      "maxAttrsOnTag": 3, // if lower or equal than 3 attributes, they will be kept on a single line
      "firstAttributeOnSameLine": true, // keep the first attribute in the same line as the tag
      "alignWithFirstAttribute": false, // do not align attributes with the first tag
      "spaceInJSXExpressionContainers": " ", // default to one space. Make it empty if you don't like spaces between JSXExpressionContainers
      "htmlOptions": {
        // put here the options for js-beautify.html
      }
    },
    "options-JSON": {
      "plugins": [
        "esformatter-quotes"
      ],
      "quotes": {
        "type": "double"
      }
    },
    "node-path": "node",
    "alert-errors": true,
    "ignore-selection": false
  }
}

Is there any way to avoid this problem?
Thank you

@damienleroux  The issue should be fixed now in v2.3.9

Thank you very much


Unknown platform gcp when upgrading istio-base Helm chart from 1.22.2 to 1.24.0

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Steps to Replicate:

Have an existing deployment of istio-base with the following values:

global:
  platform: "gcp"

Add the "managed by helm" labels to CRDs as documented here: https://istio.io/latest/news/releases/1.24.x/announcing-1.24/upgrade-notes/#istio-crds-are-templated-by-default-and-can-be-installed-and-upgraded-via-helm-install-istio-base
Upgrade the istio-base helm chart via Terraform from 1.22.2 to 1.24.0

Expected Behavior:
Update applies and CRDs are upgraded
Actual Behavior:
Error: execution error at (base/templates/zzz_profile.yaml:45:3): unknown platform gcp
Version
$ istioctl version
client version: 1.24.0
control plane version: 1.24.0
data plane version: 1.22.2 (1 proxies), 1.24.0 (1 proxies)

$ kubectl version
Client Version: v1.30.1
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.30.5-gke.1014003

$ helm version --short
v3.14.4+g81c902a

helm version in tf lock file: 2.16.1

Additional Information
No response

There are only 5 platforms configured this way: https://github.com/istio/istio/tree/master/manifests/helm-profiles. I'm not exactly sure why we didn't have one for gcp, given it doesn't require some customizations, but for gcp no config is needed (while there is customizations needed, they are auto detected anyways)

The base-charts default values.yaml lists "gcp" as one of two values for this parameter.
https://github.com/istio/istio/blob/0d9721d804a72a7a0d1c64a2c0df5eca6bb2b03e/manifests/charts/base/values.yaml#L14
So if this value is not needed for GCP, the values.yaml should probably be changed?

Thanks! that is confusing. fixed in https://github.com/istio/istio/pull/53929


feature(update) update to AppVersion 0.26.1

Signed-off-by: Daniel Werdermann<EMAIL_ADDRESS>
What this PR does / why we need it:

Update to upstream 0.26.1
Mostly update securityContext in teh deployments

Which issue this PR fixes

fixes #67

Special notes for your reviewer:
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] helm-docs are updated
[x] Helm chart is tested
[x] Update artifacthub.io/changes in Chart.yaml
[x] Run make reviewable

It’s time to deprecate the multi-tenancy chart and offer here an option for platform admins to lock down Flux. Please see which flags are needed to accomplish this: https://fluxcd.io/docs/installation/#multi-tenancy-lockdown

Already done. The PR uses 0.26.1 now.


Don't depend on a Git repository in package.json

Hey,
I'm checking out Nearley and noticed it depends on a Git repository (https://github.com/tabatkins/railroad-diagrams). Please don't. That's not particularly future proof, especially in the light of recent SNAFUs regarding retracted NPMs (e.g. left-pad). If that author hasn't published the version Nearley needs, please consider forking and/or publishing it as a scoped module under your own NPM username.

Hello moll,
I appreciate your concern for future-proofing nearley's package.json. However, I do not think the railroad-diagram situation is worth worrying about. When developing for nodejs, we make certain assumptions about services like GitHub and npm staying alive, and I think it is worthwhile to accept those assumptions rather than be paranoid about future-proofing against them. That is an endless rabbit-hole I would rather not venture down into. I think an I'll-cross-that-bridge-when-it-comes attitude is more productive in the fast-moving nodejs ecosystem, and for me it has worked well for over two years of nearley-development.
The left-pad situation was regrettable, but I believe that the problem there was that so many people felt the need to include something so frivolous as a dependency (I am extremely picky about adding more dependencies to nearley). The railroad feature is small, non-essential, and currently used by exactly zero people that I know of. In the worst-case scenario, I can always ship off a copy of the dependencies' sources with nearley. But I do not want to publish a copy of an old version of someone else's work under my name just to appeal to a package manager, let alone a package manager as whacky as npm!
P.S. In theory I'm working on a homegrown in-house version of a railroad diagram generator—a more worthwhile contribution might be to finish that off for me! ;-)

Thanks for the response.
Necessity of having GitHub up while developing (or at least when starting) is perhaps tolerable, but not while deploying. People deploying through NPM proxies with locked versions (or shrinkwrapped dependencies) are entirely independent of the global NPM site. There's no comparable GitHub proxy for that and I don't think there's a need for it. I would argue repositories are not a good dependency source solution.
There's no need for slippery slopes. Not using dependencies outside of NPM is all I'm advocating. That, and not locking patch versions (for libraries), but the latter you're not doing.
As a quicker fix, you could move the railroad dep to an optional dependency, saving builds from breaking when GitHub et al. are unavailable. After that, maybe extract charting to an independent module. :)

Ah, I'm not familiar enough with the package.json format to create an "optional dependency". If you could create a PR that lets me do something like
npm install -g nearley --without-railroad-diagrams
or something, I would be happy to merge it. :-)


1 bit depth BMP support

Hi! Thank you for helping out with Embedded Graphics development! Please:

[x] Check that you've added passing tests and documentation
[ ] Add a simulator example(s) where applicable
[x] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, etc) and appropriate crate (embedded-graphics, simulator, tinytga, tinybmp) if your changes affect the public API
[x] Run rustfmt on the project
[x] Run ./build.sh (Linux/macOS only) and make sure it passes. If you use Windows, check that CI passes once you've opened the PR.

PR description
[add your PR description here]
Added basic support for 1 bit depth BMP images to tinybmp.

LGTM! If @jamwaffles doesn't have anything to comment on this is ready to be merged.

Just released in 0.2.3.


can support java8

We currently build and deploy with Java 17.  I'm sure you could rebuild it for Java 8 if you want.


newCardTemplate when i try to add extra field inside  customAddCard Template its not working.. can anyone help me in this.

Here is the code and scrrenshot.
`import React from "react";
import ReactDOM from "react-dom";
import data from "./data.json";
import "./styles.css";
import Board from "react-trello";
const NewCard = props => {
return (

<input
type="button"
value="Add"
onClick={() => props.onNewCardAdd(props.laneId, props.cp)}
/>

);
};
class App extends React.Component {
state = {
cp: ""
};
onNewCardAdd = (laneId, cp) => {
let newData = data.lanes;
newData.map(data => {
if (data.id === laneId) {
data.cards.push({ id: "sdasdsdas23123asdaskdlas", title: cp });
}
return data;
});
this.hideEditableCard();
};
onCardChange = event => {
this.setState({
cp: event.target.value
});
};
render() {
return (

react-trello demo
<Board
data={data}
draggable
editable
newCardTemplate={
<NewCard
onNewCardAdd={(laneId, cp) => this.onNewCardAdd(laneId, cp)}
/>
}
onCardChange={this.onCardChange}
/>

);
}
}
const rootElement = document.getElementById("root");
ReactDOM.render(, rootElement);
`
how can i add cp in card data and when i click on add that time textbox is not hide in lane.

how can i use is generate function uuid ?
please can anyone help in this ?
@rcdexta @Cody Fitzpatrick

I’m working on it here - https://github.com/BrandyMint/react-trello/pull/2

Wait until implement new way to inject components

@mehuljariwala try to use this branch - https://github.com/rcdexta/react-trello/pull/274

Now dependency injection in master. You can override any used components.
https://github.com/rcdexta/react-trello#3-completely-customize-the-look-and-feel-by-using-components-dependency-injection
Pls open the issue if something is wrong


resources and navigation

Part of #43

THE best PR and proposition I have seen so far! Very simple and minimalistic.
Really easy to understand and start building schemas. What we need is to refine operations and filters :)


☂ CSV rework

I've collected several issues regarding CSV reading / readDelim to be reworked. Most are marked with the new CSV label.
I marked them all, because most are related and solving one will require solving others and vice versa.
Let this issue be an umbrella issue linking to the relevant issues:

[x] https://github.com/Kotlin/dataframe/issues/787

[x] Split readDelim and readCsv into different files, possibly a different module?
[x] Deprecate .read() overload, this should only exist in guess.kt https://github.com/Kotlin/dataframe/pull/902
[x] KDocs for each overload
[x] Check which CSVFormat options we can put in the readDelim and readCsv functions to create overloads without it. (Like setting the quote mark)
[x] Keep one overload for readDelim and readCsv with CSVFormat as option so people can set advanced settings with it.

[x] https://github.com/Kotlin/dataframe/issues/826
[x] https://github.com/Kotlin/dataframe/issues/508
[x] https://github.com/Kotlin/dataframe/issues/746
[x] https://github.com/deephaven/deephaven-csv/issues/212
[x] https://github.com/Kotlin/dataframe/issues/687
[x] https://github.com/Kotlin/dataframe/issues/607 Covered by https://github.com/Kotlin/dataframe/pull/935
[x] ~https://github.com/Kotlin/dataframe/issues/593~ Covered by https://github.com/Kotlin/dataframe/pull/925
[x] https://github.com/Kotlin/dataframe/issues/589
[x] https://github.com/Kotlin/dataframe/issues/507
[x] https://github.com/Kotlin/dataframe/issues/469
[x] https://github.com/Kotlin/dataframe/issues/383
[x] https://github.com/Kotlin/dataframe/issues/100
[x] https://github.com/Kotlin/dataframe/issues/834
[x] https://github.com/Kotlin/dataframe/issues/921
[x] https://github.com/Kotlin/dataframe/issues/527
[x] Remove opt-in
[ ] https://github.com/Kotlin/dataframe/issues/765
[ ] Extend CsvOption in ImportDataSchema annotation and Gradle Task
[ ] Change drag-and-drop behavior in notebooks
[ ] Documentation about new CSV implementation on the website/examples when it's no longer experimental.
[ ] Move Compression to :core and apply to other io's

Not all tasks are finished. The "dataframe-csv" implementation is entering experimental stage at the 0.15.X version of DF.
The next version will stabilize it and deprecate the old implementation.


modules: hal_nordic: Enforce nrf-regtool minimum version

Require the presence of the nrf-regtool package as well as requiring
a minimum version, failing the build whenever a suitable version is not
found in the system.

In order for CI not to fail, this PR requires a Docker image update that includes 5.1.0. @stephanosio

This must go in before #70411 otherwise when nrf-regtool is not present, west flash will silently erase UICR without putting a new one.

note that this has always been the case, it's not related to #70411

This must go in before #70411 otherwise when nrf-regtool is not present, west flash will silently erase UICR without putting a new one.

note that this has always been the case, it's not related to #70411

Without #70411 west flash is simply failing here and does not leave board supposedly flashed but not working.

This must go in before #70411 otherwise when nrf-regtool is not present, west flash will silently erase UICR without putting a new one.

note that this has always been the case, it's not related to #70411

Without #70411 west flash is simply failing here and does not leave board supposedly flashed but not working.

This is likely because we now only have the JLink runner, which is only usable for debugging purposes. However, west flash on SOC1/EngA used nrfjprog backend (now removed), where UICRs were erased.

Btw, having nrf-regtool 5.1.0 will fix any UICR related problems, CMake should actually warn if not present (not fail).

Why only warn instead of failing? I would agree to warn only if and only if west flash would determine that UICR is missing and would refuse to flash in such case.

Btw, having nrf-regtool 5.1.0 will fix any UICR related problems, CMake should actually warn if not present (not fail).

Why only warn instead of failing? I would agree to warn only if and only if west flash would determine that UICR is missing and would refuse to flash in such case.

This was likely done as a shortcut to skip the hassle of upgrading CI image for every nrf-regtool release. It was a bad idea, though, because UICR is essential to build something that boots.

ping @stephanosio @carlescufi

just hit that. Would be good to get that in.

It's a slow process, we should start thinking on simplifying regtool as a repo-script, so it evolves together with Zephyr.

ping


[Feature] Add efficientnet_fpn_backbone

Add efficientnet_fpn_backbone

The specific FPN Backbone that you propose is aligned with the ResNet approach

This is "maskrcnn" to build easily backbond for other networks.

The method is not used by any pre-trained model or model builder.

The method used pre-train efficientnet backbond that come with pytorch. you must missed that.

It's rather a utility that fits better in downstream applications.

It the same as resnet and mobilenet function that help you to build backbond for maskrcnn and other network for detection.

@talregev I'm aware the we offer an Efficientnet backbone; I'm the one who added it. :)
My point is that, even though you follow a "maskrcnn" approach, this doesn't mean it's a canonical implementation of a model described on a paper. Unless you can send us a reference of a specific paper you are implementing and also decide to offer pre-trained weights for that model, then this PR can't be merged.
I don't doubt that this utility method can be useful for users (this is why you could consider creating a small project for it at Github). But consider what would happen if we try to create methods for virtually every architecture/backbone that TorchVision supports. We would have to add tens of methods, duplicating massive amount of code. It would be nice at one point to offer a utility that creates an FPN out of arbitrary backbones but the main problem is that there are too many ways to build an FPN and each paper tends to do something different. That's the reason we currently don't offer such a general purpose utility.

But consider what would happen if we try to create methods for virtually every architecture/backbone that TorchVision supports

There is only 17 files inside models, with ~15 backbond models. most of them is not used for detection.
This is a detection utils file. it tend to help to build backbond for detections networks, as the name of the file imply.
We should add as many backbond support for detections, and if we see duplications, we can start refactoring and generalize.
until it happen, we can another useful support and easy access like mobilnet and resnt that found in the same file.

Unless you can send us a reference of a specific paper you are implementing

Not sure I understand this policy. This is raise a difficult questions for the community.
Are you accepting only novel things that come from papers?
There is no new things that come from engineer and try new stuff?
Also there is a paper (not my paper) that use cascade mask-rcnn with efficientnet backbond with NAS-FPN:
https://arxiv.org/pdf/2012.07177v2.pdf

@talregev Please review our general contribution and the model contribution guides for details on what kind of improvements we usually accept and what is the recommended approach for maximizing the chances of getting them merged.
As I explained earlier, this utility can't be added in TorchVision without having a specific canonical architecture using it. Moreover, prior implementing new architectures you would need to open an issue and discuss it with the maintainers as per the guide above. I see that you already separated some of the test improvements you made to a different PR at #5552. I'm happy to help you review and merge the other PR but unfortunately this one is not something we can accept. I don't argue that some people will find it useful; I'm saying that this is not the kind of utility we want to add in the library.


Implement WBEM client

create a simple WBEM client
Fixes #1752.
Signed-off-by: Joe Grund<EMAIL_ADDRESS>

This change is

Landed as 31cf641cf649ef3dd2bd2bd75f98ee4ddb994708


[Feature] Show lint errors in the code editor

We are generating lint errors but we are not displaying them inside the code editor, we should highlight them via error underlining and give information about it.

Note that linters don't show runtime errors. For example if you have a binding {{ JSON.str(value) }}. Parser will throw str is not a function. However the linter won't catch this.

@mohanarpit @ajinkyakulkarni @vnodecg is there a better approach we can take here? There are browser IDEs that have solved this


Allow for extra columns in the CSV that are not in the DB

My CSV seeder data files sometimes have extra columns, which caused errors during import.
I added code to cross reference the columns being imported to the database structure.
Extra input columns are now ignored and do not throw a SQL insert error.
This means that laravel-csv-seeder is now more robust:

Column order is unimportant
missing columns in the CSV that exist in the DB are inserted with NULL
Extra columns in the CSV that do not exist in the DB are ignored (new functionality added by this pull request)

Does this require doctrine be installed?

This can already be done by providing a mapping.

Hmm, good question, I've not installed Doctrine, but I believe a few Laravel libraries use Doctrine.
You can accomplish the same thing with a mapping, but creating a mapping is a manual process.
Thanks for at least considering it!
My use case is a little different than intended -  I'm using it as a way of importing data on a monthly basis. The people uploading the csv files each month won't have a clue how to build a mapping.  What you have here is a great head start, and saved me some time from doing it manually.  Thanks so much for posting it!

The mapping doesn't have to be manual. In your seeder read the first line of your CSV, then read your DB. Generate a mapping config and pass it to my seeder.
I can't include a huge number of configuration options (especially inefficient ones) because this script needs to remain ridiculously fast to support thousand+ line CSVs. A bit of prep work to generate the option to pass to my package is the way to go here.

I can totally see that/agree with the thinking.  I'll work on that - it would be more efficient that calling out to see if each field exists for every. single. row.
Thanks again for the feedback, I appreciate it, and I really appreciate the package - Easily saved me a night of work, and introduced me to a few new concepts I hadn't considered, which really simplified things in my code on my end.

Jack


Using call_js_keyword in Plugin API should not need the dummy page , logger or playwright  arguments.

Describe the bug
Using call_js_keyword in Plugin API should not need the dummy page , logger or playwright  arguments. Instead calling the call_js_keyword function just need the custom arguments.

Fixed in https://github.com/MarketSquare/robotframework-browser/pull/2559


Most ValidateFooUpdate don't call ValidateFoo

This results in it being possible to update all sorts of fields to illegal values.
@smarterclayton I think we want to either make all ValidateFooUpdate() call ValidateFoo() or else make REST objects call both sets of Validate functions.  What think?

So certain things are legal on create that are illegal on update.  The REST object definitely is the final arbiter of calling the right method which does the right thing.  I'm think it would work if individual REST strategies call validateX before validateXUpdate, but we should be sure that validate* now stops mutating the resource (which a few did before PrepareBeforeUpdate was added).
----- Original Message -----

This results in it being possible to update all sorts of fields to illegal
values.
@smarterclayton I think we want to either make all ValidateFooUpdate() call
ValidateFoo() or else make REST objects call both sets of Validate
functions.  What think?

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/6219

So you think the REST object should call ValidateFoo(new); ValidateFooUpdate(old, new) in their own ValidateUpdate() methods?
Why would it not be correct to call strategy.Validate(new); strategy.ValidateUpdate(old, new) in BeforeUpdate()?  It seems to me
that every updated object must also be a valid object.
That also make it very clear what  ValidateUpdate() should be checking and
what it should not.

On Mar 31, 2015, at 3:03 PM, Tim Hockin<EMAIL_ADDRESS>wrote:
So you think the REST object should call ValidateFoo(new); ValidateFooUpdate(old, new) in their own ValidateUpdate() methods?
Why would it not be correct to call strategy.Validate(new); strategy.ValidateUpdate(old, new) in BeforeUpdate()? It seems to me
that every updated object must also be a valid object.
That also make it very clear what ValidateUpdate() should be checking and
what it should not.

Part of the reason ValidateUpdate was separate to allow that decision to be made by the strategy.  I would prefer to keep that factoring, because they are separate.

—
Reply to this email directly or view it on GitHub.

@thockin Where does this currently go wrong? I know I asked for both to get called when I reviewed a change for rep. ctrls.

Until I fixed it, for example, ValidateServiceUpdate() allowed through
perfectly invalid services.
On Tue, Mar 31, 2015 at 3:51 PM, Daniel Smith<EMAIL_ADDRESS>wrote:

@thockin https://github.com/thockin Where does this currently go wrong?
I know I asked for both to get called when I reviewed a change for rep.
ctrls.
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/6219#issuecomment-88276724
.


Py36 add features

Coverage decreased (-0.9%) to 94.795% when pulling 34a5aaf88a2aaffc8bcd76d0e19f5695a788aaac on russell-lewis:py36-add-features into cf26b72b0cdfaeb6e765597c43de8fddf6244746 on Netflix:master.


Added YouTube Download feature.

This time it should be more clean and easyer to read.

This PR has a lot of changes, 37 changed files  with 61,559 additions and 6,816 deletions but only a handful of files are added and modified. You only have to add the new form and code required for it for example these 3 files packages.config, YTDL.vb  and YTDL.resx. Overwriting the entire repo like this will cause a bunch of issues, for instance your gitignore overwrites the projects default isn't set to ignore the Debug folder which also shouldn't be included in the repo.
 That way only the modified lines and new files are in the PR.
Thanks


Reduce intrusiveness of make clean

make clean currently removes all empty directories recursively. This is far too intrusive. It can even break git repositories by deleting directories inside .git, causing git to longer recognize the repository (this can usually be repaired with git init).
We should only clean the temporary directories that were created by the Makefile.

Possible implementation:
Iterate through the directories of {OBJ|DEP}DIR_{R|D} from right to left and remove empty directories only along those paths.

I'd propose using something like
rm $(OBJS_R) $(OBJS_D) $(DEPS)
rmdir -p --ignore-fail-on-non-empty $(dir $(OBJS_R))
rmdir -p --ignore-fail-on-non-empty $(dir $(OBJS_D))
rmdir -p --ignore-fail-on-non-empty $(dir $(DEPS))

This should also work in comibnation with #2.

On second thought, we should probably use
find $(OBJDIR) -type f -name '*.o'  -delete 2>/dev/null
find $(DEPDIR) -type f -name '*.d'  -delete 2>/dev/null
find $(DEPDIR) -type f -name '*.Td' -delete 2>/dev/null
find $(OBJDIR) $(DEPDIR) -type d -empty -exec 'rmdir' '-p' '--ignore-fail-on-non-empty' {} \; 2>/dev/null

This is definitely an improvement, but it's not quite perfect yet: if the user sets either OBJDIR, DEPDIR or BINDIR to ., this still causes empty directory cleaning in ., and it's not very unusual for the user to set BINDIR to ..
In #5, I have changed this to the code below. See my commits there for the reasons. Note that this still doesn't solve the above issue.
.PHONY: c
c:
	-find . -type f -path './$(OBJDIR)/*.o'  -exec $(RM) {} +
	-find . -type f -path './$(DEPDIR)/*.d'  -exec $(RM) {} +
	-find . -type f -path './$(DEPDIR)/*.Td' -exec $(RM) {} +
	-find $(OBJDIR) $(DEPDIR) -type d -empty -exec 'rmdir' '-p' {} \; 2>/dev/null || true

.PHONY: clean
clean: c
	-$(RM) $(BIN_R)
	-$(RM) $(BIN_D)
	-find $(BINDIR) -type d -empty -exec 'rmdir' '-p' {} \; 2>/dev/null || true

Since we're not creating subdirectories inside BINDIR, it would suffice to remove that with
if [ -d $(BINDIR) ]; then rmdir --ignore-fail-on-non-empty -p $(BINDIR); fi

The same isn't true for object and dependency files, but it's very unlikely for the user to set those to go to .
It might save us a lot of headaches if allow the user to set something like BLDDIR in which the object and dependency files are placed and then just assume that it is not . and recursively clean it. In fact, I believe we could then even hardcode the names obj, dep, release and debug, since I don't actually think it is very useful for the user to be able to change these names. If we do that, it would be very safe to clean $(BLDDIR)/obj and $(BLDDIR)/dep recursively. Do you agree with this?

The BLDDIR idea I agree with. We could even add a check that errors if BLDDIR==.. Do watch out with using --ignore-fail-on-non-empty though. This doesn't suppress errors but instead allows rmdir to delete non-empty directories.

Do watch out when using --ignore-fail-on-non-empty though. This doesn't suppress errors but instead allows rmdir to delete non-empty directories.

Are you sure? For me it just suppresses errors.

Do watch out when using --ignore-fail-on-non-empty though. This doesn't suppress errors but instead allows rmdir to delete non-empty directories.

Are you sure? For me it just suppresses errors.

Turns out the rmtrash command I use is implemented incorrectly. I opened an issue for this. Conclusion, we should use --ignore-fail-on-non-empty.

Since we're not creating subdirectories inside BINDIR, it would suffice to remove that with
if [ -d $(BINDIR) ]; then rmdir --ignore-fail-on-non-empty -p $(BINDIR); fi

That would work as well yes. Good thinking.

The same isn't true for object and dependency files, but it's very unlikely for the user to set those to go to .
It might save us a lot of headaches if allow the user to set something like BLDDIR in which the object and dependency files are placed and then just assume that it is not . and recursively clean it. In fact, I believe we could then even hardcode the names obj, dep, release and debug, since I don't actually think it is very useful for the user to be able to change these names. If we do that, it would be very safe to clean $(BLDDIR)/obj and $(BLDDIR)/dep recursively. Do you agree with this?

Using a $(BLDDIR) variable seems sensible. We could even error out when $(BLDDIR) is set to . with a message like ''you monster!'' I'd propose implementing this after merging #5 since we have stalled #5 for long enough and it is not the point of #5.

Using a $(BLDDIR) variable seems sensible. We could even error out when $(BLDDIR) is set to . with a message like ''you monster!''

I'm a fan of this :). I did something similar when I integrated testing into a personal Makefile version.

I'd propose implementing this after merging #5 since we have stalled #5 for long enough and it is not the point of #5.

Agreed. I can clean up #5 soon.


ebs_config could not take effect

Description
If you specifiy ebs_config in core_instance_fleet section, it will be ignore when running "terraform plan", for example:
core_instance_fleet = {
name                      = "core fleet"
target_on_demand_capacity = 10
instance_type_configs = [
  {
    bid_price_as_percentage_of_on_demand_price = 100
    ebs_config =
      {
        size                 = 256
        iops                 = 4000
        type                 = "gp3"
        volumes_per_instance = 4
      }
    instance_type     = "r6a.2xlarge"
    weighted_capacity = 1
  }
]
launch_specifications = {
  on_demand_specification = {
    allocation_strategy = "lowest-price"
  }
}

}
will output:

core_instance_fleet {
+ id                             = (known after apply)
+ name                           = "core fleet"
+ provisioned_on_demand_capacity = (known after apply)
+ provisioned_spot_capacity      = (known after apply)
+ target_on_demand_capacity      = 10
+ target_spot_capacity           = 0
   + instance_type_configs {
       + bid_price_as_percentage_of_on_demand_price = 100
       + instance_type                              = "r6a.2xlarge"
       + weighted_capacity                          = 1

       + ebs_config {
           + size                 = 64
           + type                 = "gp3"
           + volumes_per_instance = 1
         }
     }

   + launch_specifications {
       + on_demand_specification {
           + allocation_strategy = "lowest-price"
         }
     }
 }

The output EBS storage is just 64G. Obviously it's not expected.
When I  changed it into:
core_instance_fleet = {
name                      = "core fleet"
target_on_demand_capacity = 10
instance_type_configs = [
  {
    bid_price_as_percentage_of_on_demand_price = 100
    ebs_config = **[**
      {
        size                 = 256
        iops                 = 4000
        type                 = "gp3"
        volumes_per_instance = 4
      }
    **]**
    instance_type     = "r6a.2xlarge"
    weighted_capacity = 1
  }
]
launch_specifications = {
  on_demand_specification = {
    allocation_strategy = "lowest-price"
  }
}

}
terraform plan will output:
core_instance_fleet {
+ id                             = (known after apply)
+ name                           = "core fleet"
+ provisioned_on_demand_capacity = (known after apply)
+ provisioned_spot_capacity      = (known after apply)
+ target_on_demand_capacity      = 10
+ target_spot_capacity           = 0
      + instance_type_configs {
          + bid_price_as_percentage_of_on_demand_price = 100
          + instance_type                              = "r6a.2xlarge"
          + weighted_capacity                          = 1

          **+ ebs_config {
              + iops                 = 4000
              + size                 = 256
              + type                 = "gp3"
              + volumes_per_instance = 4
            }**
        }

      + launch_specifications {
          + on_demand_specification {
              + allocation_strategy = "lowest-price"
            }
        }
    }

Although plan 256 GB, but after EMR Cluster is created, you will noticed that it in fact also just has 64 G EBS Storage.
Versions

Module version [Required]:
source                      = "terraform-aws-modules/emr/aws"
version                     = "1.2.2"

Terraform version:
terraform --version
Terraform v1.5.3
on linux_amd64

provider registry.terraform.io/hashicorp/archive v2.4.0
provider registry.terraform.io/hashicorp/aws v5.31.0
provider registry.terraform.io/hashicorp/random v3.5.1
provider registry.terraform.io/hashicorp/template v2.2.0

Your version of Terraform is out of date! The latest version
is 1.7.5. You can update by downloading from https://www.terraform.io/downloads.html

Provider version(s):
Terraform v1.5.3
on linux_amd64

provider registry.terraform.io/hashicorp/archive v2.4.0
provider registry.terraform.io/hashicorp/aws v5.31.0
provider registry.terraform.io/hashicorp/random v3.5.1
provider registry.terraform.io/hashicorp/template v2.2.0

Your version of Terraform is out of date! The latest version
is 1.7.5. You can update by downloading from https://www.terraform.io/downloads.html
Reproduction Code [Required]
Please refer to above terarform snippet.
Steps to reproduce the behavior:
I use S3 as the backend.
terraform init -backend-config=backend.config
terraform plan
terraform apply
Expected behavior
EC2 in setup EMR CLuster has EBS storage of 256 GB other than 64 GB.
Actual behavior
EC2 in setup EMR CLuster has EBS storage of  64 GB.

We are also facing the same issue, it seems.

I've opened a PR to update the examples to show the correct syntax - however, please checkout the note https://github.com/terraform-aws-modules/terraform-aws-emr/pull/20#issue-2225791964 - I would suggest opening a ticket on the upstream AWS provider to have this fixed there

This issue has been resolved in version 2.0.0 :tada:

Thank you @antonbabenko


make: pick up all privileged tests in make tests-privileged

As seen in #10729 some privileged tests currently aren't picked up by
the tests-privileged rule because it expects the privileged_tests
build tag to directly follow +build. However, some *_test.go files
use additional build tags before that. Account for that when evaluating
the privileged tests to run. At current HEAD this will pick up 3 more
privileged test packages:
% grep --include='*.go' -ril '+build privileged_tests' . | wc -l
16
% grep --include='*.go' -ril '+build [^!]*privileged_tests' . | wc -l
19

To be merged after #10729
/cc @joestringer @christarazi

Coverage decreased (-0.01%) to 45.526% when pulling a81cf0fc606e1378b5131e7783ad8c765154f4cc on pr/tklauser/run-all-privileged-tests into 88f11f48d940a92c2b40810b4f44a0cae84f75ca on master.

test-me-please

Cherry-picked @christarazi's fix from #10729 to be able to run tests (commit fe4bbd5e3430f3768190c63870ae3e8e538c0d9f in this PR).

test-me-please

Needed to add an additional fix for the tests in pkg/sysctl: ebd4b1881d8eec90d2459f3df7bc44f19bfb1f4f
/cc @pchaigno


VCS does not push changes?

Godot version:
3.2 alpha
OS/device including version:
windows 10
Issue description:
i have to manually push changes done and commited in godot's new VCS system
Is this supposed to be this way or am i missing the push / pull button ?

Is this supposed to be this way or am i missing the push / pull button ?

It is not implemented yet.

ah, that explains it ;)

Shouldn't this be as simple executing a git push command when a button is pressed? Or am I missing something? If that's all it is, I can try adding this feature.

Shouldn't this be as simple executing a git push command when a button is pressed? Or am I missing something? If that's all it is, I can try adding this feature.

You need to add on the Godot's side :

a way to select the branch you want to push to,
eventually be able to force push (maybe display a warning in that case),
add a button to push
define the interface to allow force pushing so that it can call a gdnatice function

And on the git implementation side:

implement the push function using libgit2

Note, we also have to make sure this is compatible with other VCS (like perforce).

@groud For perforce I am thinking to move the commit dock inside plug-in rather than Godot itself. It will allow dock customization per VCS requirements. Does this sound logical?

@groud For perforce I am thinking to move the commit dock inside plug-in rather than Godot itself. It will allow dock customization per VCS requirements. Does this sound logical?

That might be, though we have to make things consistent. One difficult part is likely to figure out what is really needed in the interface then. Maybe the interface could be made even lighter, I am not sure.


rudimental location status column - only one state

in the locations table there is a "state" column - as a user i expect to see different states e.g. at least active and archived....

Which one of those locations is archived?

its the test_location

Also fixed. Changes live in <24hrs.
Re-open after if this is an issue again.


Problem if boost and cuda toolkit is installed from repository using APT

I have installed cuda-toolkit, boost and libboost-all-dev (version <IP_ADDRESS>) etc using APT
When making, I get following error:
gcc: error: /usr/include/boost/libs/thread/src/pthread/thread.cpp: No such file or directory
gcc: error: /usr/include/boost/libs/thread/src/pthread/once.cpp: No such file or directory

Which doesn't surprise me, because there are no such files (cpp's) installed in the system. But how can I get them using APT or is the only chance to download and compile boost from the source files?
gcc (Debian 8.3.0-6) 8.3.0
Os: Debian 10 with all updates from the buster repo
Same with boost <IP_ADDRESS> and gcc (Debian 10.2.1-6) 10.2.1 (Debian 11)

Same problem here. I solved it by simply downloaded the boost library v1.77 from boost.org and set the BOOST_LIB_PATH to where the folder is. After make source you can delete the newly downloaded boost library so that it won't take extra disk space.

I have installed cuda-toolkit, boost and libboost-all-dev (version <IP_ADDRESS>) etc using APT When making, I get following error:
gcc: error: /usr/include/boost/libs/thread/src/pthread/thread.cpp: No such file or directory
gcc: error: /usr/include/boost/libs/thread/src/pthread/once.cpp: No such file or directory

Which doesn't surprise me, because there are no such files (cpp's) installed in the system. But how can I get them using APT or is the only chance to download and compile boost from the source files?
gcc (Debian 8.3.0-6) 8.3.0 Os: Debian 10 with all updates from the buster repo
Same with boost <IP_ADDRESS> and gcc (Debian 10.2.1-6) 10.2.1 (Debian 11)


Add C API for regular expressions

See miniSphere feature request here:
http://forums.spheredev.org/index.php/topic,1215.msg9623.html#msg9623
It would be nice to have Ecmascript code be able to pass a regular expression to e.g. a Duktape/C function and later be able to use the passed regexp to do pattern matching against arbitrary strings, all directly through the C API.

First, for completeness, the current way to use RegExps (or any other Ecmascript binding without a C equivalent).
Unless a lot of RegExp instances are created all the time, it should be reasonably OK to just do:
duk_get_global_string(ctx, "RegExp");
duk_push_string(ctx, "[a-z]+");
duk_new(ctx, 1);

For matching there are a few more steps which may matter if RegExps are used in a very performance critical section (but then, Duktape regexp engine is not fast in general so it's not an ideal match there):
duk_get_prop_string(ctx, regex_idx, "exec");
duk_dup(ctx, regex_idx);
duk_push_string(ctx, "aiee");
duk_call_method(ctx, 1);
/* Inspect result. */

As for adding to the C API, I don't see why not. A few issues with these particular API bindings:

RegExp constructor takes a string source and string options. For C code the string options are somewhat weird (compared to ordinary flags) but since it's also used in script code, maybe it's OK.
Some version compatibility risks: RegExp constructor gains new options that aren't representable as a string. Or custom RegExp features are exposed, and a new argument is needed in the API.
RegExp match result is an object and each capture is a separate string in the result. Inspecting the result is not very convenient in C code. But I'm not sure how the regexp result with all the captures etc could be conveniently provided in a C API considering memory lifecycle issues, strings with NULs, etc.

Right, I know I can just call the RegExp constructor/methods.  But that's not ideal for sandboxing because someone could overwrite RegExp and/or mutate the prototype. :)

I know, just mentioned it for completeness because the Minisphere discussion seems to imply it can't be done from C API at all. In my opinion it can be done, and reasonably well for most cases when the RegExp is constructed at init and then used multiple times.
Mutating the RegExp binding is also more of a theoretical problem IMO. If user code did that, it would also break script code like new RegExp() or even /[a-z]/ if the RegExp prototype object was mutated. It's not generally a big concern unless the sandboxed code is potentially hostile, as opposed to just careless.
But if it's an issue, you can just stash the RegExp constructor into the global stash on init and use the same method. This won't fix RegExp.prototype mutation though, but adding a C API wouldn't fix that issue I'm afraid.
Even so I do agree that a C API would be nice.

Mutating the RegExp binding is also more of a theoretical problem IMO. If user code did that, it would also break script code like new RegExp() or even /[a-z]/ if the RegExp prototype object was mutated. It's not generally a big concern unless the sandboxed code is potentially hostile, as opposed to just careless.

Agreed; I'm mostly thinking of user expectation here, i.e. principle of least surprise.  Obviously any hostile mutation of the RegExp prototype would prevent normal JS code from functioning properly like you say, but for non-hostile code, if someone were to "enhance" the RegExp object via monkey-patch, they might not expect (or want) those changes to extend to a function known to be implemented natively.
...I guess that's pretty theoretical too, though.  There's not a lot you can ultimately do to change the underlying behavior by monkey-patching RegExp methods.

But if it's an issue, you can just stash the RegExp constructor into the global stash on init and use the same method. This won't fix RegExp.prototype mutation though, but adding a C API wouldn't fix that issue I'm afraid.

I don't understand.  Assuming a C API existed, I would expect it to access the internal regular expression engine directly, without involving the "userland" built-ins at all?  Although... I guess if one passed in a regular expression as /.../ that would involve the RegExp prototype anyway, but that could be worked around by passing them as strings instead.

Because the argument of "someone may mutate the built-ins" comes up from time to time, just a few notes on why that isn't generally a huge problem IMO and why I don't find the argument "X needs a C API because of sandboxing" very appealing.
Just generally, providing a C API for every case where some built-in might be tampered with by an application is not really a solution, unless one assumes that every Ecmascript API is eventually mirrored into the C API. If one doesn't assume that, then there's always one more API that might be needed by e.g. a module loader, etc, which leads to a gradual pressure to expand the C API to fully match the Ecmascript API. If that's not an OK outcome (and I don't think it is), then the process has to stop somewhere.
Also, if one is truly trying to prevent user code from breaking built-in objects, all the objects need to be sealed and frozen manually before any user code runs.
if one does that, then both script code and C code are protected against modifications, and things like:
duk_eval_string(ctx, "new RegExp('[a-z]+');");

and
var re = new RegExp('[a-z]+');

will be equally protected from tampering.
As far as I can imagine, the main case where stronger stability guarantees provided by a C APi matters is e.g. where:

Some "platform" mechanisms (like a module loader) runs in the same Duktape context and one wants to protected those mechanisms from being tampered with.
It's still OK for the application to break its own environment, e.g. by mutating or deleting built-ins - and it's important that the platform mechanisms still continue to work as before.

But if this is the basic scenario, I'd probably just isolate e.g. a module loader completely by running it in a different context (in the same heap). This is very cheap, and protects against a lot of tampering in one step, and doesn't prevent using Ecmascript built-ins which one needs from time to time.
The main sandboxing cases that I've frequently come across are:

Protecting application code from accidents. Configurable but non-writable properties are generally good enough for that because a Object.defineProperty() call is rarely an accident.
Protecting against a truly hostile application. This requires a lot of measures beyond just protecting built-ins, e.g. censoring of tracebacks and careful analysis of every native binding for escalation possibilities.

But if it's an issue, you can just stash the RegExp constructor into the global stash on init and use the same method. This won't fix RegExp.prototype mutation though, but adding a C API wouldn't fix that issue I'm afraid.
I don't understand. Assuming a C API existed, I would expect it to access the internal regular expression engine directly, without involving the "userland" built-ins at all? Although... I guess if one passed in a regular expression as /.../ that would involve the RegExp prototype anyway, but that could be worked around by passing them as strings instead.

The most obvious implementation would be that a C API allowed one to create a RegExp instance. Many properties of RegExp instances like .source, .global, etc are inherited getters, and they're inherited from the RegExp prototype.
If they didn't inherit from the RegExp prototype, then they'd really be a different data type rather than an API to work with RegExp instances.

It's still OK for the application to break its own environment, e.g. by mutating or deleting built-ins - and it's important that the platform mechanisms still continue to work as before.

Right, this is my approach whenever possible.  I mostly try to separate "userland" from "kernel/engine space" to avoid surprising users and having to use eval runs counter to that :)
Obviously an experienced JS coder is going to know not to overwrite built-ins, but someone just learning about JavaScript (and Sphere is heavily geared towards newbies :) may accidentally overwrite a built-in with their own global variable.  I've actually seen code that does just that which worked fine in the old Sphere 1.x but broke in early versions of miniSphere because they assumed the constructors wouldn't be overwritten.

So maybe what you'd really want is access to the regexp engine directly, rather than a C API to deal with RegExp instances?
Conceptually that'd be straightforward to do, but in practice it's not trivial to avoid the RegExp instance or the RegExp match result object because the internal code revolves around passing objects. There's no lower level representation for RegExps or RegExp match results.
The next best thing would be the ability to create a RegExp instance which didn't inherit from RegExp prototype and would thus be free of any outside influence. You could still match against it using a C API which wouldn't need to look up a match method from the prototype, but such RegExps wouldn't work in the script side.

Obviously an experienced JS coder is going to know not to overwrite built-ins, but someone just learning about JavaScript (and Sphere is heavily geared towards newbies :) may accidentally overwrite a built-in with their own global variable.

True. It would be easier to avoid accidents if all built-in bindings were non-writable but configurable. That way all write attempts would fail by default and you'd need to think a bit more if you really want to redefine the built-in. Unfortunately many built-ins are writable :-/
Btw, here's an example of what happens with Node.js interactive session when one overwrites RegExp.prototype.test:
$ nodejs
> RegExp.prototype.test = 123
123
> readline.js:924
            throw err;
            ^

TypeError: /^[0-9A-Za-z]$/.test is not a function
    at emitKeys (readline.js:1239:32)
    at next (native)
    at ReadStream.onData (readline.js:918:36)
    at emitOne (events.js:77:13)
    at ReadStream.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at ReadStream.Readable.push (_stream_readable.js:110:10)
    at TTY.onread (net.js:523:20)

So maybe what you'd really want is access to the regexp engine directly, rather than a C API to deal with RegExp instances?

Yes, this would be ideal.  I also wanted users to be able to pass regular expressions as /.../ too but I guess I can't have it both ways :)

Conceptually that'd be straightforward to do, but in practice it's not trivial to avoid the RegExp instance or the RegExp match result object because the internal code revolves around passing objects. There's no lower level representation for RegExps or RegExp match results.

I empathize with this, very much so.  Early in miniSphere's life several objects were represented only in the Ecmascript environment without a persistent C-side counterpart.  Nowadays almost every built-in class has a native reference-counted equivalent but that wasn't true back then and it often made it hard to compose things internally.

Long story short: I want to use Duktape in lieu of adding another dependency for regular expression handling, but still outside the context of the Ecmascript environment if possible.  Sorry for not just coming out and saying that before. :-)

Supposing the regexp API was not Ecmascript-inspired but optimized for C callers instead, how would that look like?

I'd have to think about that for a bit to give you an answer to that question.  Maybe it would help to look at other regular expression engines for some inspiration, hmm...

Conceptually at least:

Compiling a regexp, with a set of options (at least flags or a flag string 'gi' as in Ecmascript).
Running a regexp against an input string, probably interpreted as CESU-8.
Checking for match or no match.
Extracting captures.
Continuing matching from previous position (for "find all").

On a related note: I know a few projects that use Duktape for JSON encoding/decoding, choosing it over a JSON library because the API is good enough for that purpose (e.g. automatic memory management via value stack is easy to understand) and because it provides a way forward if it becomes necessary to use more features. This regexp use case is somewhat similar. Duktape isn't really designed with that in mind though, but it's nice if it works out at least in some cases.
Btw, a long time ago when I wrote the regexp compiler/executor I first tried to write it as a separate library rather than it being deeply integrated with the Ecmascript semantics. This turned out to be too difficult in practice so I gave up on that goal. It's certainly doable, but there would be a relatively large intermediate API and a significant footprint impact (relatively speaking, of course) due to that API.

I've been known to use Duktape's JSON functionality to the same end.  I figure I'm already compiling in code to parse and interpret JSON data, why not take advantage of it?  So it's kind of the same rationale here with regexps, why add an additional dependency when I already have access to code that does everything I need :)

Hm, thinking about the sandboxing issue some more, I guess it would be easy enough just to create an additional context which wouldn't be used to run "untrusted" code and therefore would remain isolated from the uncertainties of arbitrary code execution.
Of course that kind of thing wouldn't be practical on low-memory targets, but on desktop platforms the additional heap might as well be free.

It doesn't even need to be a separate Duktape heap for isolation: two contexts created with separate global objects don't share any objects by default. You can exchange objects between them though and must be careful to avoid that. But for example a module loader can just pass in a string and pass back another string, and both contexts will live in entirely separated global object spaces.


The GX_EVENT_FOCUS_LOST event is not sent if the parent does not have focus

Describe the bug
The GX_EVENT_FOCUS_LOST event is not sent if the parent does not have focus
For example, there is the following hierarchy

Widget 1

Widget 1.1

Widget 1.1.1

Widget 1.2

Widget 1.1 does not accept focus. Focus on Widget 1.1.1. If you click on Widget 1.2, then Widget 1.1.1 will not receive the GX_EVENT_FOCUS_LOST event. This happens because when focus is transferred, there is a widget with a common parent, in our case it is Widget 1.1 and the focus loss event is passed to it, but it does not pass it to children because it does not accept focus.
Please also mention any information which could help others to understand
the problem you're facing:

What target device are you using? Cortex M7
Which version of Azure RTOS? 6.1
What toolchain and environment? IAR
What have you tried to diagnose or workaround this issue?  We have to make sure that all widgets accept focus, but this does not work with vertical lists, because widgets there do not accept focus and we have to write special handlers for them so that they pass the focus loss event to children

To Reproduce

Create a project with 4 widgets, with hierarchy and settings, as shown in the description
Add event processing for GX_EVENT_FOCUS_LOST Widget 1.1.1
Click on Widget 1.1.1
Click on Widget 1.2

Expected behavior
Widget 1.1.1 will receive the GX_EVENT_FOCUS_LOST event
Impact
Widget 1.1.1 does not receive GX_EVENT_FOCUS_LOST event
Logs and console output
No
Additional context
No

@maxim-lbmv Thank you for your feedback! We can reproduce the issue and we'll fix it in the future.

@maxim-lbmv This issue has been fixed in this PR: https://github.com/azure-rtos/guix/pull/92.


Change 'an' to 'a' on line 45

You pronounce unique with a j, like junique, which means the 'n' is not needed.
Sorry.

Thanks, merged. As you see my English isn't that good, but shall be good enough to understand my documentation :-)

Haha np.
Oh, yes!


urh: 2.0.1 -> 2.0.2

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/urh/versions.
These checks were done:

built on NixOS
ran ‘/nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin/.urh-wrapped --version’ and found version 2.0.2
ran ‘/nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin/urh --version’ and found version 2.0.2
found 2.0.2 with grep in /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2
directory tree listing: https://gist.github.com/fd267c85c4f90f14b9af167c50b169a0

cc @fpletz for review

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: urh
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Attempted: urh
Partial log (click to expand)
shrinking /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/lib/python3.6/site-packages/urh/dev/native/lib/hackrf.cpython-36m-x86_64-linux-gnu.so
shrinking /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/lib/python3.6/site-packages/urh/cythonext/signalFunctions.cpython-36m-x86_64-linux-gnu.so
shrinking /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/lib/python3.6/site-packages/urh/cythonext/util.cpython-36m-x86_64-linux-gnu.so
shrinking /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/lib/python3.6/site-packages/urh/cythonext/path_creator.cpython-36m-x86_64-linux-gnu.so
strip is /nix/store/j75dgadrff2d1fyc4fczmcgqkid2imdx-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/lib  /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin
patching script interpreter paths in /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2
checking for references to /build in /nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2...
wrapping `/nix/store/cs9vqxk0xqcpqcs10bbqhq6h7vdbmyny-urh-2.0.2/bin/urh'...
postPatchMkspecs

Failure on aarch64-linux (full log)
Attempted: urh
Partial log (click to expand)
g++ -c -pipe -DNDEBUG -DQT_IMAGE_DECODERS -DRAPIDJSON_HAS_STDSTRING=1 -DMBGL_USE_GLES2 -D__QT__ -O3 -ftemplate-depth=1024 -fvisibility-inlines-hidden -fvisibility=hidden -DMBGL_VERSION_REV=\"qt-v1.2.0\" -O2 -fPIC -std=c++1z -w -D_REENTRANT -fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I. -Ideps/boost/1.62.0 -Ideps/boost/1.62.0/include -Ideps/cheap-ruler/2.5.3 -Ideps/cheap-ruler/2.5.3/include -Ideps/earcut/0.12.4 -Ideps/earcut/0.12.4/include -Ideps/geojson/0.4.2 -Ideps/geojson/0.4.2/include -Ideps/geojsonvt/6.3.0 -Ideps/geojsonvt/6.3.0/include -Ideps/geometry/0.9.2 -Ideps/geometry/0.9.2/include -Ideps/kdbush/0.1.1-1 -Ideps/kdbush/0.1.1-1/include -Ideps/pixelmatch/0.10.0 -Ideps/pixelmatch/0.10.0/include -Ideps/polylabel/1.0.3 -Ideps/polylabel/1.0.3/include -Ideps/protozero/1.5.2 -Ideps/protozero/1.5.2/include -Ideps/rapidjson/1.1.0 -Ideps/rapidjson/1.1.0/include -Ideps/shelf-pack/2.1.1 -Ideps/shelf-pack/2.1.1/include -Ideps/supercluster/0.2.2 -Ideps/supercluster/0.2.2/include -Ideps/unique_resource/cba309e -Ideps/unique_resource/cba309e/include -Ideps/variant/1.1.4 -Ideps/variant/1.1.4/include -Ideps/vector-tile/1.0.0-rc7 -Ideps/vector-tile/1.0.0-rc7/include -Ideps/wagyu/0.4.3 -Ideps/wagyu/0.4.3/include -Iinclude -Iplatform/default -Iplatform/qt -Iplatform/qt/include -Isrc -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1/QtCore -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore -I.moc -I/nix/store/gjx0451k3vnz8f11dpq56955f3kwyfxx-mesa-noglu-17.3.8-dev/include -I/nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/mkspecs/linux-g++ -o .obj/src/mbgl/renderer/render_light.o src/mbgl/renderer/render_light.cpp
g++ -c -pipe -DNDEBUG -DQT_IMAGE_DECODERS -DRAPIDJSON_HAS_STDSTRING=1 -DMBGL_USE_GLES2 -D__QT__ -O3 -ftemplate-depth=1024 -fvisibility-inlines-hidden -fvisibility=hidden -DMBGL_VERSION_REV=\"qt-v1.2.0\" -O2 -fPIC -std=c++1z -w -D_REENTRANT -fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I. -Ideps/boost/1.62.0 -Ideps/boost/1.62.0/include -Ideps/cheap-ruler/2.5.3 -Ideps/cheap-ruler/2.5.3/include -Ideps/earcut/0.12.4 -Ideps/earcut/0.12.4/include -Ideps/geojson/0.4.2 -Ideps/geojson/0.4.2/include -Ideps/geojsonvt/6.3.0 -Ideps/geojsonvt/6.3.0/include -Ideps/geometry/0.9.2 -Ideps/geometry/0.9.2/include -Ideps/kdbush/0.1.1-1 -Ideps/kdbush/0.1.1-1/include -Ideps/pixelmatch/0.10.0 -Ideps/pixelmatch/0.10.0/include -Ideps/polylabel/1.0.3 -Ideps/polylabel/1.0.3/include -Ideps/protozero/1.5.2 -Ideps/protozero/1.5.2/include -Ideps/rapidjson/1.1.0 -Ideps/rapidjson/1.1.0/include -Ideps/shelf-pack/2.1.1 -Ideps/shelf-pack/2.1.1/include -Ideps/supercluster/0.2.2 -Ideps/supercluster/0.2.2/include -Ideps/unique_resource/cba309e -Ideps/unique_resource/cba309e/include -Ideps/variant/1.1.4 -Ideps/variant/1.1.4/include -Ideps/vector-tile/1.0.0-rc7 -Ideps/vector-tile/1.0.0-rc7/include -Ideps/wagyu/0.4.3 -Ideps/wagyu/0.4.3/include -Iinclude -Iplatform/default -Iplatform/qt -Iplatform/qt/include -Isrc -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1/QtCore -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore -I.moc -I/nix/store/gjx0451k3vnz8f11dpq56955f3kwyfxx-mesa-noglu-17.3.8-dev/include -I/nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/mkspecs/linux-g++ -o .obj/src/mbgl/renderer/render_source.o src/mbgl/renderer/render_source.cpp
g++ -c -pipe -DNDEBUG -DQT_IMAGE_DECODERS -DRAPIDJSON_HAS_STDSTRING=1 -DMBGL_USE_GLES2 -D__QT__ -O3 -ftemplate-depth=1024 -fvisibility-inlines-hidden -fvisibility=hidden -DMBGL_VERSION_REV=\"qt-v1.2.0\" -O2 -fPIC -std=c++1z -w -D_REENTRANT -fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I. -Ideps/boost/1.62.0 -Ideps/boost/1.62.0/include -Ideps/cheap-ruler/2.5.3 -Ideps/cheap-ruler/2.5.3/include -Ideps/earcut/0.12.4 -Ideps/earcut/0.12.4/include -Ideps/geojson/0.4.2 -Ideps/geojson/0.4.2/include -Ideps/geojsonvt/6.3.0 -Ideps/geojsonvt/6.3.0/include -Ideps/geometry/0.9.2 -Ideps/geometry/0.9.2/include -Ideps/kdbush/0.1.1-1 -Ideps/kdbush/0.1.1-1/include -Ideps/pixelmatch/0.10.0 -Ideps/pixelmatch/0.10.0/include -Ideps/polylabel/1.0.3 -Ideps/polylabel/1.0.3/include -Ideps/protozero/1.5.2 -Ideps/protozero/1.5.2/include -Ideps/rapidjson/1.1.0 -Ideps/rapidjson/1.1.0/include -Ideps/shelf-pack/2.1.1 -Ideps/shelf-pack/2.1.1/include -Ideps/supercluster/0.2.2 -Ideps/supercluster/0.2.2/include -Ideps/unique_resource/cba309e -Ideps/unique_resource/cba309e/include -Ideps/variant/1.1.4 -Ideps/variant/1.1.4/include -Ideps/vector-tile/1.0.0-rc7 -Ideps/vector-tile/1.0.0-rc7/include -Ideps/wagyu/0.4.3 -Ideps/wagyu/0.4.3/include -Iinclude -Iplatform/default -Iplatform/qt -Iplatform/qt/include -Isrc -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1/QtCore -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore -I.moc -I/nix/store/gjx0451k3vnz8f11dpq56955f3kwyfxx-mesa-noglu-17.3.8-dev/include -I/nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/mkspecs/linux-g++ -o .obj/src/mbgl/renderer/render_static_data.o src/mbgl/renderer/render_static_data.cpp
g++ -c -pipe -DNDEBUG -DQT_IMAGE_DECODERS -DRAPIDJSON_HAS_STDSTRING=1 -DMBGL_USE_GLES2 -D__QT__ -O3 -ftemplate-depth=1024 -fvisibility-inlines-hidden -fvisibility=hidden -DMBGL_VERSION_REV=\"qt-v1.2.0\" -O2 -fPIC -std=c++1z -w -D_REENTRANT -fvisibility=hidden -fvisibility-inlines-hidden -DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_DEBUG -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_SQL_LIB -DQT_CORE_LIB -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURCE -I. -Ideps/boost/1.62.0 -Ideps/boost/1.62.0/include -Ideps/cheap-ruler/2.5.3 -Ideps/cheap-ruler/2.5.3/include -Ideps/earcut/0.12.4 -Ideps/earcut/0.12.4/include -Ideps/geojson/0.4.2 -Ideps/geojson/0.4.2/include -Ideps/geojsonvt/6.3.0 -Ideps/geojsonvt/6.3.0/include -Ideps/geometry/0.9.2 -Ideps/geometry/0.9.2/include -Ideps/kdbush/0.1.1-1 -Ideps/kdbush/0.1.1-1/include -Ideps/pixelmatch/0.10.0 -Ideps/pixelmatch/0.10.0/include -Ideps/polylabel/1.0.3 -Ideps/polylabel/1.0.3/include -Ideps/protozero/1.5.2 -Ideps/protozero/1.5.2/include -Ideps/rapidjson/1.1.0 -Ideps/rapidjson/1.1.0/include -Ideps/shelf-pack/2.1.1 -Ideps/shelf-pack/2.1.1/include -Ideps/supercluster/0.2.2 -Ideps/supercluster/0.2.2/include -Ideps/unique_resource/cba309e -Ideps/unique_resource/cba309e/include -Ideps/variant/1.1.4 -Ideps/variant/1.1.4/include -Ideps/vector-tile/1.0.0-rc7 -Ideps/vector-tile/1.0.0-rc7/include -Ideps/wagyu/0.4.3 -Ideps/wagyu/0.4.3/include -Iinclude -Iplatform/default -Iplatform/qt -Iplatform/qt/include -Isrc -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork/5.10.1/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui/5.10.1/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql/5.10.1/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1 -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore/5.10.1/QtCore -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtNetwork -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtGui -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtSql -isystem /nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/include/QtCore -I.moc -I/nix/store/gjx0451k3vnz8f11dpq56955f3kwyfxx-mesa-noglu-17.3.8-dev/include -I/nix/store/1f2ds40wp45h57sn1ll3z4vmx5zsp11c-qtbase-5.10.1-dev/mkspecs/linux-g++ -o .obj/src/mbgl/renderer/render_tile.o src/mbgl/renderer/render_tile.cpp
building of '/nix/store/x56ixk2lzq5yyxq5pzjfq7rkmn2lx4f2-qtlocation-5.10.1.drv' timed out after 3600 seconds
cannot build derivation '/nix/store/3xiarg5csm07i2pfida5qwwnspwjkml4-qtwebengine-5.10.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/yg3xymxpal44vbcaz3ab6h14hcw81s1s-qtwebkit-5.9.1.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/kmcbz4h2j2qz06assk4gw2573nfv9pmd-python3.6-PyQt-5.10.drv': 2 dependencies couldn't be built
cannot build derivation '/nix/store/4kspph6c31r5nyh95h82kzv1s11l4jfd-urh-2.0.2.drv': 2 dependencies couldn't be built
error: build of '/nix/store/4kspph6c31r5nyh95h82kzv1s11l4jfd-urh-2.0.2.drv' failed