Service Port validations are not consistently enforced

Creating multiple apps in the same group with a single request
POST /v2/groups/ the following:

```json
{
  "id": "/abc",
  "apps": [
    {
      "id": "app1",
      "cmd": "sleep 500",
      "container": {
        "type": "DOCKER",
        "docker": {
          "image": "busybox",
          "network": "BRIDGE",
          "portMappings": [
            {
              "containerPort": 5000,
              "hostPort": 0,
              "servicePort": 16554
            }
          ]
        }
      },
      "mem": 32,
      "cpus": 0.5,
      "instances": 0
    },
    {
      "id": "app2",
      "cmd": "sleep 500",
      "container": {
        "type": "DOCKER",
        "docker": {
          "image": "busybox",
          "network": "BRIDGE",
          "portMappings": [
            {
              "containerPort": 5000,
              "hostPort": 0,
              "servicePort": 16554
            }
          ]
        }
      },
      "mem": 32,
      "cpus": 0.5,
      "instances": 0
    }
  ]
}
```

You will get:
{
    "details": [
        {
            "errors": [
                "Requested service port 16554 conflicts with a service port in app /abc/app2",
                "Requested service port 16554 conflicts with a service port in app /abc/app1"
            ],
            "path": "/groups(0)/value"
        }
    ],
    "message": "Object is not valid"
}

This is the desired behaviour.
Create multiple apps in the same group using the POST /v2/apps endpoint
POST /v2/apps with:

```json
[
  {
    "id": "/abc/app1",
    "cmd": "sleep 500",
    "container": {
      "type": "DOCKER",
      "docker": {
        "image": "busybox",
        "network": "BRIDGE",
        "portMappings": [
          {
            "containerPort": 5000,
            "hostPort": 0,
            "servicePort": 16554
          }
        ]
      }
    },
    "mem": 32,
    "cpus": 0.5,
    "instances": 0
  }
```

And then POST /v2/apps:

```json
  {
    "id": "/abc/app2",
    "cmd": "sleep 500",
    "container": {
      "type": "DOCKER",
      "docker": {
        "image": "busybox",
        "network": "BRIDGE",
        "portMappings": [
          {
            "containerPort": 5000,
            "hostPort": 0,
            "servicePort": 16554
          }
        ]
      }
    },
    "mem": 32,
    "cpus": 0.5,
    "instances": 0
  }
]
```

We get the same validation error, which is good.
Creating apps in different groups using the PUT /v2/groups endpoint
PUT /v2/groups:

```json
{
  "id": "/",
  "groups": [
    {
      "id": "/abc",
      "apps": [
        {
          "id": "app1",
          "cmd": "sleep 500",
          "container": {
            "type": "DOCKER",
            "docker": {
              "image": "busybox",
              "network": "BRIDGE",
              "portMappings": [
                {
                  "containerPort": 5000,
                  "hostPort": 0,
                  "servicePort": 16554
                }
              ]
            }
          },
          "mem": 32,
          "cpus": 0.5,
          "instances": 0
        }
      ]
    },
    {
      "id": "/def",
      "apps": [
        {
          "id": "app2",
          "cmd": "sleep 500",
          "container": {
            "type": "DOCKER",
            "docker": {
              "image": "busybox",
              "network": "BRIDGE",
              "portMappings": [
                {
                  "containerPort": 5000,
                  "hostPort": 0,
                  "servicePort": 16554
                }
              ]
            }
          },
          "mem": 32,
          "cpus": 0.5,
          "instances": 0
        }
      ]
    }
  ]
}
```

Is allowed, but it should NOT be.
Creating apps in different groups using the PUT /v2/apps endpoint
PUT /v2/apps:

```json
[
  {
    "id": "/abc/app1",
    "cmd": "sleep 500",
    "container": {
      "type": "DOCKER",
      "docker": {
        "image": "busybox",
        "network": "BRIDGE",
        "portMappings": [
          {
            "containerPort": 5000,
            "hostPort": 0,
            "servicePort": 16554
          }
        ]
      }
    },
    "mem": 32,
    "cpus": 0.5,
    "instances": 0
  },
  {
    "id": "/def/app2",
    "cmd": "sleep 500",
    "container": {
      "type": "DOCKER",
      "docker": {
        "image": "busybox",
        "network": "BRIDGE",
        "portMappings": [
          {
            "containerPort": 5000,
            "hostPort": 0,
            "servicePort": 16554
          }
        ]
      }
    },
    "mem": 32,
    "cpus": 0.5,
    "instances": 0
  }
]
```

Is allowed, but it should NOT be.
Creating apps in different groups using two POST /v2/groups calls

`POST /v2/groups`
```json
{
  "id": "/abc",
  "apps": [
    {
      "id": "app1",
      "cmd": "sleep 500",
      "container": {
        "type": "DOCKER",
        "docker": {
          "image": "busybox",
          "network": "BRIDGE",
          "portMappings": [
            {
              "containerPort": 5000,
              "hostPort": 0,
              "servicePort": 16554
            }
          ]
        }
      },
      "mem": 32,
      "cpus": 0.5,
      "instances": 0
    }
  ]
}
```
And then POST /v2/groups:
{
  "id": "/def",
  "apps": [
    {
      "id": "app2",
      "cmd": "sleep 500",
      "container": {
        "type": "DOCKER",
        "docker": {
          "image": "busybox",
          "network": "BRIDGE",
          "portMappings": [
            {
              "containerPort": 5000,
              "hostPort": 0,
              "servicePort": 16554
            }
          ]
        }
      },
      "mem": 32,
      "cpus": 0.5,
      "instances": 0
    }
  ]
}

Is allowed, but it should NOT be.

@gkleiman how come "Creating multiple apps in the same group with a single request" is described as desired behavior?
"Requested service port 16554 conflicts with a service port in app /abc/app2",
"Requested service port 16554 conflicts with a service port in app /abc/app1"

If I am deploying multiple applications and want them to use the same service port because I want to put them behind Marathon-LB, wouldn't load balancing go out of window because each service port will have a different port address and thus only one application will be in the membership of this service port ?


0.1.1

import/export from files or clipboard
actually really compatible with FBE now
fix lost blueprint icons when importing and exporting back to Factorio

new version


cmd/go: GODEBUGCPU does not affect caching

https://golang.org/cl/91737 added a new environment variable that controls compiler output. However, cmd/go does not know about it. It should probably either migrate to a command line flag or be added to the list at https://github.com/golang/go/blob/30b6bc30b208299e4cb6598be854ec276db85661/src/cmd/go/internal/work/exec.go#L226.
(Aside: Why does this need to be protected by a GOEXPERIMENT build flag? Not obvious to me. I thought we were trying to move away from those.)
cc @martisch @bradfitz

Moving to Go 1.12. It's explicitly behind a GOEXPERIMENT flag because this isn't for users (yet?). It's for the build system to increase CPU coverage.

I guess we should add GOEXPERIMENT to the build cache invalidation magic but not GODEBUGCPU:
smoke test with sha1sum ../bin/go for:
go clean -cache
GOEXPERIMENT=debugcpu ./make.bash
e0896e5dd8578cd817ab84979c310da86309ea3f  ../bin/go

go clean -cache
GOEXPERIMENT=debugcpu GODEBUGCPU=all=0 ./make.bash
e0896e5dd8578cd817ab84979c310da86309ea3f  ../bin/go

./make.bash
04c3ef214c75d496dce67020d501dd0626a9ca74  ../bin/go

running
go cache -clean
./all.bash
GOEXPERIMENT=debugcpu GODEBUG=gocacheverify=1 ./all.bash
triggers an error:
panic: go: internal cache error: cache verify failed: id=fb2313f2883b218bc066fd82b898c2e516581ef1d98d89306189fa0ae182d009 changed:<<<
compile
goos linux goarch amd64
import "cmd/cover"
omitdebug false standard true local false prefix ""
compile hN7U-hIzcC216X9D7jJ5 [] []
GO$GOARCH=
file cover.go -HJGpdKieEMMOCO-mPxL
file doc.go q8cjgpxRyr-B4c0-BSxm
file func.go XsiVkomYxidS7PwWXQ2n
file html.go 4Y1BIbPC6AVLRyO7P_1x
file profile.go 0v22dDl9QjcWlQUwc8ke
import bufio do57MGx2Y1ny-iTSZ8xm
import bytes hzsbwNhfBvX1MeqZuX_J
import cmd/internal/browser lB6CNWIvbAQhCJ87k4lE
import cmd/internal/edit Qi-YqEtW43LLmQRtn89f
import cmd/internal/objabi pM_kmeN0dsgOwIXnNIgo
import flag 0857hOxkwQ8UOUUhlxcR
import fmt pRrKIvjNZsLODwerYD22
import go/ast oT3qx9K-aLjOT_fzqq7i
import go/build YizkSjO0wdaq5FTNZf8Z
import go/parser tr0t3-B29FTNt99c_dgU
import go/token sD6jKS2szZrhwGYNJ7oL
import html/template ViNWlmNmRpv3WreAsU4V
import io ZV1onBPpy8p0twc7gW-W
import io/ioutil A6-6ihjVqFezyIyf8BSv
import log UnhGGF8ENdh01rORi6LM
import math NObQaiwNkm25aQ7ufbjg
import os MG0j3jpTqpfUHwK7Yev0
import path/filepath 1KlWzTqUkbxUippA0PjX
import regexp PY16zyZDtBOWVLfe1Cvf
import sort _LXX0vnnL-jngm1mYtYW
import strconv BGeyFISqHJ06yQc-FtDT
import strings UCe-z-5kkJNhLZ8_Tcu0
import text/tabwriter auwReVp8BRX0TAoxw0wB
import runtime XvdKklQdiVRyO4a8YuxR

>>>
old: 0261fce9b7f23ef9875b3a343eaaa896dddca566af80d58ac9b62fe37c620d14 217732
new: bd20f251999620804f182e43e18c7b9c5e1d402683fdbf5b13cebe27823e198c 217718

actually the GOEXPERIMENT=debugcpu change is included in the compile  buildID:
../bin/go tool compile -V=full
compile version devel +fffb3a5c20 Thu May 31 07:20:38 2018 +0000 buildID=x3ITGgvcvyYJ_LgYxLW-/4TMLSzuIc14CGpo_sKdY/yFu2yIDH6xKiavoqdEVl/UMK0LpWBgLKUUJI3ZA7s

GOEXPERIMENT=debugcpu ./make.bash
../bin/go tool compile -V=full
compile version devel +fffb3a5c20 Thu May 31 07:20:38 2018 +0000 X:framepointer,debugcpu buildID=PBWLlIi2-VanQZimHm8B/UmgAcoGA4iYbgsZme20i/Qo34Q7TaurQoNlVRUeNU/hN7U-hIzcC216X9D7jJ5

which is taken into account here: https://github.com/golang/go/blob/30b6bc30b208299e4cb6598be854ec276db85661/src/cmd/go/internal/work/exec.go#L220
go cache -clean
GODEBUG=gocacheverify=1 ./all.bash
without GOEXPERIMENT seems to always fail on two different machines. Will file an extra bug for that.
Closing this bug.

Thanks, and sorry for the noise.


Publish 06/10/2022, 10:30 AM

Docs Build status updates of commit 50bb9f6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

cabgen-bootstrap.yml
: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 docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix: fix conversion error

What this PR does / why we need it?
This PR fix conversion error on the transaction， which don't use zero to default gas value
What is the impact of this PR?
No Breaking Change

CI Settings

CI Usage
Tip: Check the CI you want to run below, and then comment /run-ci.
CI Switch

[x] Cargo Clippy
[ ] Coverage Test
[x] E2E Tests
[x] Code Format
[x] Unit Tests
[x] Web3 Compatible Tests
[x] OCT 1-5 And 12-15
[x] OCT 6-10
[x] OCT 11
[x] OCT 16-19
[x] v3 Core Tests

CI Description

CI Name
Description

Chaos CI
Test the liveness and robustness of Axon under terrible network condition

Cargo Clippy
Run cargo clippy --all --all-targets --all-features

Coverage Test
Get the unit test coverage report

E2E Test
Run end-to-end test to check interfaces

Code Format
Run cargo +nightly fmt --all -- --check and cargo sort -gwc

Web3 Compatible Test
Test the Web3 compatibility of Axon

v3 Core Test
Run the compatibility tests provided by Uniswap V3

OCT 1-5 | 6-10 | 11 | 12-15 | 16-19
Run the compatibility tests provided by OpenZeppelin

/run-ci


Automatic adjustment of log display range

This PR addresses the TODO to allow the slider range for displaying number of logs to be adjusted automatically. Currently we have a fixed range of [10, 1000]. With this PR, the range will start with [10, 100] at launch. As more logs are being printed, the upper limit will increase accordingly to the nearest multiple of hundred that is greater or equal to the current log history size.

I can predict before the CI runs that this will fail web CI because of the usual wasm-bindgen bump


Network: MAC address tests validation scenarios

MAC address tests validation scenarios

Configuration & verification of out of range MAC address
Configuration & verification of less byte MAC address
Configuration & verification of more byte MAC address

gerrit link:
https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc-test-automation/+/19266/


Try to fix Elastic connection pooling issues

This creates a new connection on every request,
hopefully working around the issues with the connection pool.
This will go out on 1 web and see if it resolves the issues at all.
This is branched from rel, which seems to have caused some weirdness :/

@ericholscher When did you pushed it in production?


Readability: replace reduce with filter

Filter is definitely easier to read here, and probably more idiomatic.

Duh. Thanks! :+1:


Initial Kubernetes cluster manager implementation.

Includes the following initial feature set:

Cluster mode with only Scala/Java jobs
Spark-submit support
Dynamic allocation

Does not include, most notably:

Client mode support
Proper testing on both the unit and integration level; integration
tests are flaky

Sorry, wrong base for the fork here


closes #1377 - ensure all tables are checked ...

... when removing references to candidates that are still in use.
This is done by getting tableIds from zookeeper at the start of the
reference scan and at the end of the reference scan.  During the
reference scans, the list of tableID is tracked.  After all candidates
that are still in use have been removed, there is a one more consitency
check to ensure we looked at all tables.

This is a cherry-pick of @mjwall 's GC fix on the 1.10 branch applied to 2.1

I think all the logic is sound for this improvement but there is just some minor cleanup that could be done, most likely due to cherry picking and/or multiple contributors.

@keith-turner - I implemented your changes. I kind of expected a test failure, but that didn't happen.

@dlmarion  I made some updatesto the test  in this commit keith-turner/accumulo@78cf05d9af90bb7ba218a17cda6755df80127702 to use DataLevel and to not have to add the metadata refs

@keith-turner  - I like it. Can you create a PR against my branch and I will merge it in?

Nevermind, I grabbed the diff and applied manually

So, I'm not convinced this is the right approach.

What's the implication of this statement? Are you saying that we need to go back to the drawing board? If I implement your suggested changes, is this good to go?

So, I'm not convinced this is the right approach.

What's the implication of this statement? Are you saying that we need to go back to the drawing board? If I implement your suggested changes, is this good to go?

Unless the edge cases for table creation/deletion are addressed (like paying attention to table states, like Keith mentioned), then this should definitely not be merged as is. And, I wouldn't recommend its inclusion in any forked version of 1.10 either, because of the potential harmful side-effects I mentioned.
If the table creation/deletion edge cases are addressed, I would have to re-review. I've only reviewed what's there, not what code changes have yet to be proposed.
I'm not sure what "go[ing] back to the drawing board" would entail. It feels like we're shooting in the dark, adding a sanity check against a problem that is not well-defined.

It feels like we're shooting in the dark, adding a sanity check against a problem that is not well-defined.

I think the validation outlined in #1377 is very well defined: If table ids w/ a certain state were seen in ZK before and after metadata scan then we must  see them in metadata OR something is really really wrong.   The less the GC trust that the persisted data it reads is correct and the more it tries to verify what it can about that data the more robust GC will be.   The GC already does a good bit of checks on the metadata table as it reads it.  Checking the metadata table against ZK will make the verification more thorough.
In addition to the check outlined in #1377, another check was added in #2293 for the case where table ids were seen in metadata table and none were seen in ZK.   This situation can legitimately happen when the total number of tables goes to/from zero concurrently with a GC cycle.  This situation could also happen when ZK read is silently failing and returning no data.  There is no way to distinguish between the two causes.  If the system is actually working correctly, then the legitimate case would be transient.   We could defer this second check and open an issue to do it another PR where we try to figure out how to avoid the false positive or make the check less noisy at first (like always skip GC cycle but log info at first and warn/error on subsequent cycles if seen again).  IMO it would be good to leave this second check as it is in the current PR because it can always be removed in bug fix release.

@ctubbsii  - do these recent changes resolve the changes you requested?

Full IT passed except for the test failure identified in #2948


How to create security certificate pem for elasticsearch an kibana

I am trying to intall the helm chart of elasticsearch and kibana but in the security configuration I need to have :
certificateAuthorities: /usr/share/kibana/config/certs/elastic-certificate.pem

  key: /usr/share/kibana/config/certs/kibana/kibana.key
  certificate: /usr/share/kibana/config/certs/kibana/kibana.crt

can any one tell me how to create those file using the elasticsearch certutil.

I'm going to close this since its a duplicate of the discussions we are having in https://github.com/elastic/helm-charts/pull/205. This PR adds automation for automatically generating the certificates.


fix: revert LLVM 15 bump on MacOS aarch64

As reported by Adrien Champion and @Kha , the uploaded artifact for LLVM 15 is for x86, not aarch64. I have not tested this fix, but this should hopefully be enough to stop us building bad nightlies until @Kha has more time to investigate.

Thanks!


Discover Sales Order API from S/4HANA Cloud System

Tutorial URL: https://developers.sap.com/tutorials/cp-apim-sales-tracker-api-discover.html
Please specify the step you are referring to Step 2 point 3.
The OK button stays greyed out if I select the link as shown in picture https://developers.sap.com/tutorials/cp-apim-sales-tracker-api-discover/_jcr_content.github-proxy.1576479901.file/06-copy.png
I don't think I'm doing anything wrong.
Thanks

Hello,
Once check the base path -it should be unique and there should not be any validation errors.If you still feel you have not missed anything and its a valid OData. Please raise an issue on OPU-API-OD-DT.
Regards
Shilpa

Thank you for your feedback. The issue seems to be resolved, so I am closing the issue.
If you still have questions, feel free to reopen the issue.


fix(frontend): update online config

:tada: This PR is included in version 3.2.0-online.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.0-alpha.3 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.1-online.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.2.2-online.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 3.3.0-alpha.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.2.3-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:


error on the first run

Hi there,
I'm getting an UnhandledPromiseRejectionWarning: TypeError: tslib_1.__spreadArray is not a function error after the Conversion successful message when I run portman --cliOptionsFile portman/portman-cli.json on a basic openapi spec file with the default portman-cli.json generated by portman --init
Any hints?

{
"local": "test/api.spec.yml",
"output": "test/api.postman.json",
"envFile": "portman/.env-portman",
"includeTests": true,
"syncPostman": false,
"runNewman": false
}

@clonq We tried to reproduce the error, but we were unable to reproduce it with the following config
{
  "local": "./tmp/crm.openapi.yml",
  "output": "./tmp/api.postman.json",
  "envFile": "portman/.env-portman",
  "includeTests": true,
  "syncPostman": false,
  "runNewman": false
}

Where crm.openapi.yml contains the OpenAPI as defined to https://github.com/apideck-libraries/portman/blob/main/examples/cli-options/crm.openapi.yml
Could you check a couple of thing for us:

Bump your packages.json to use the latest version: 1.4.2

  "dependencies": {
    "@apideck/portman": "^1.4.2",

If the provided OpenAPI is valid? You can use a online service for this: https://apitools.dev/swagger-parser/online/

If the issue still remains after the above checks, would you be able to the share the OpenAPI spec with us, so we can try to reproduce the behaviour locally?

Same error after upgrading to 1.4.2 and using the sample crm file. The error seems to be in injectEnvVariables judging by the stack trace. And my .env-portman file is empty.

@clonq Could you share the stack trace? Since we seems to be unable to reproduce it.

(node:71950) UnhandledPromiseRejectionWarning: TypeError: tslib_1.__spreadArray is not a function
at Object.injectEnvVariables (testprj/node_modules/@apideck/portman/dist/application/globals/injectEnvVariables.js:46:28)
at CollectionWriter.execute (testprj/node_modules/@apideck/portman/dist/application/CollectionWriter.js:25:29)
at Portman. (testprj/node_modules/@apideck/portman/dist/Portman.js:297:34)
at step (testprj/node_modules/tslib/tslib.js:140:27)
at Object.next (testprj/node_modules/tslib/tslib.js:121:57)
at testprj/node_modules/tslib/tslib.js:114:75
at new Promise ()
at Object.__awaiter (testprj/node_modules/tslib/tslib.js:110:16)
at Portman.runPortmanOverrides (testprj/node_modules/@apideck/portman/dist/Portman.js:292:24)
at Portman. (testprj/node_modules/@apideck/portman/dist/Portman.js:252:45)
at step (testprj/node_modules/tslib/tslib.js:140:27)
at Object.next (testprj/node_modules/tslib/tslib.js:121:57)
at fulfilled (testprj/node_modules/tslib/tslib.js:111:62)

@clonq In the 1.5.0 release of Portman, it should be fixed.
The cause was that "spreadArray is not a function" since the _spreadArrays function for TypeScript has been deprecated.
If it is not fixed, feel free to reopen this item or create a new one.

Stacktrace after upgrading to 1.5.0:
(node:18695) UnhandledPromiseRejectionWarning: TypeError: tslib_1.__spreadArray is not a function
at Object.writeCollectionPreRequestScripts (testprj/node_modules/@apideck/portman/dist/application/globals/writeCollectionPreRequestScripts.js:19:75)
at CollectionWriter.execute (testprj/node_modules/@apideck/portman/dist/application/CollectionWriter.js:34:29)
at Portman. (testprj/node_modules/@apideck/portman/dist/Portman.js:303:34)
at step (testprj/node_modules/tslib/tslib.js:140:27)
at Object.next (testprj/node_modules/tslib/tslib.js:121:57)
at testprj/node_modules/tslib/tslib.js:114:75
at new Promise ()
at Object.__awaiter (testprj/node_modules/tslib/tslib.js:110:16)
at Portman.runPortmanOverrides (testprj/node_modules/@apideck/portman/dist/Portman.js:298:24)
at Portman. (testprj/node_modules/@apideck/portman/dist/Portman.js:254:45)
at step (testprj/node_modules/tslib/tslib.js:140:27)
at Object.next (testprj/node_modules/tslib/tslib.js:121:57)
at fulfilled (testprj/node_modules/tslib/tslib.js:111:62)

@clonq In PR #110, we aim to replace all spread array implementations with a compatible implementation.
After the review, it will be included in an upcoming release and should fix your errors.

@clonq The changes have been merged into the 1.5.1 release.
I'm going to leave this item open, and hope you can validate if the 1.5.1 release have fixed this unwanted error.
If the error is solved, would you be so kind to close the item.
If the error remains, could you let us know the error stack trace and share any additional info that could help us to reproduce the problem.

Looks like it works. Thanks guys.


Renaming

Some things in engi don't have idiomatic names.
Examples are:

engi.GetComponent -> engi.Component
engi.Keys.KEY_SPACE -> engi.Keys.SPACE

Also: we might want to think about removing engi.Keys.SPACE (and such) all-together? Since we have engi.Keys.Get(engi.Space) - which works for every key, and not just a few of them?

Remove the redundancy!

https://github.com/paked/engi/pull/84

My pull request doesn't fix the issue of engi.GetComponent vs Component but I think it is better to do this in steps.

done

:+1:


Update safari extension

Description

Changed the behavior of the Add to Reading List command to add the current tab to the Reading List.

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

LGTM also, thank you for the contribution @xilopaint


feat(alert): export AlertButton interface

export AlertButton interface

Sorry for the delay, add via 0ba33d9

Thanks :)
On Mon, 02 Oct 2017 at 18:15, Mike Hartington<EMAIL_ADDRESS>wrote:

Sorry for the delay, add via 0ba33d9
https://github.com/ionic-team/ionic/commit/0ba33d943f749cf65736ff30cdc4879993fa10bc
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ionic-team/ionic/pull/12545#issuecomment-333583937,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQv-Wgs2jUuWD4ofUj68c5dwOVqdERAVks5soQwngaJpZM4OqwCn
.


Non-code configuration: new Configuration APIs

Continuation of #26420
Introduces new APIs to support non-code configuration:

ConfigurationSource - implementation of property source. Expected to be able to retrieve get property names/values with given prefix
ConfigurationBuilder - capable of creting configurations
T Configuration.get(ConfigurationProperty<T>  and ConfigurationProperty to set up propetry (name, env vars, shared/local, type, converter, default value, etc)
makes Configuration immutable: put,  remove and clone are deprecated and only affect internal environment configuration.

Also adds properties for ProxyOptions (Java proxy) as an example.
Context (gists are a bit out-of-date when it comes to details such as APIs or property names):

Overview  https://gist.github.com/lmolkova/69bcee15b6f5d5aa3672f79e1c649693
Spring: https://gist.github.com/lmolkova/69bcee15b6f5d5aa3672f79e1c649693
Quarkus and Micronaut: https://gist.github.com/lmolkova/c4c84013287f7199a157c1c4392f08bd

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core-test. You can review API changes here
API changes
+     public class TestConfigurationBuilder {
+         public TestConfigurationBuilder()
+         public TestConfigurationBuilder add(String key, String value)
+         public TestConfigurationBuilder addEnv(String key, String value)
+         public Configuration build()
+         public Configuration buildSection(String section)
+     }

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core. You can review API changes here

API changes have been detected in com.azure:azure-core-amqp. You can review API changes here
API changes
+         public static ProxyOptions fromConfiguration(Configuration configuration)

API changes have been detected in com.azure:azure-core. You can review API changes here

API change check for com.azure.resourcemanager:azure-resourcemanager-deviceprovisioningservices
API changes are not detected in this pull request for com.azure.resourcemanager:azure-resourcemanager-deviceprovisioningservices

API change check for com.azure:azure-core
API changes have been detected in com.azure:azure-core. You can review API changes here

API change check for com.azure:azure-core-amqp
API changes have been detected in com.azure:azure-core-amqp. You can review API changes here
API changes
+         public static final String AMQP_PROXY_AUTHENTICATION_TYPE = "amqp.proxy.authentication-type";
+         public static final String AMQP_PROXY_TYPE = "amqp.proxy.type";
+         public static final String AMQP_PROXY_HOST = "amqp.proxy.hostname";
+         public static final String AMQP_PROXY_PORT = "amqp.proxy.port";
+         public static final String AMQP_PROXY_USER = "amqp.proxy.username";
+         public static final String AMQP_PROXY_PASSWORD = "amqp.proxy.password";
+         public static ProxyOptions fromConfiguration(Configuration configuration)

API change check for com.azure:azure-core-http-jdk-httpclient
API changes are not detected in this pull request for com.azure:azure-core-http-jdk-httpclient

API change check for com.azure:azure-core-http-netty
API changes are not detected in this pull request for com.azure:azure-core-http-netty

API change check for com.azure:azure-core-http-okhttp
API changes are not detected in this pull request for com.azure:azure-core-http-okhttp

@ki1729 can you please take a look at AMQP-core changes? Thanks!


CLASS_NAMES in Argoverse

Hi thank you for releasing code and checkpoints for Argoverse. This is really useful for the community.
I am running your model in Argoverse but the output classes seems to be different to compared to the one reported in:
tools/cfgs/lion_models/lion_mamba_1f_1x_argo_128dim_sparse_v2.yaml.
For examples, all the detections that are clearly belonging to class "Regular_vehicle" should have label 0, while they are predicted as label 1 ("Pedestrian").  Is it possible that the classes are shifted by one?
Thank you

Hi thank you for releasing code and checkpoints for Argoverse. This is really useful for the community. I am running your model in Argoverse but the output classes seems to be different to compared to the one reported in: tools/cfgs/lion_models/lion_mamba_1f_1x_argo_128dim_sparse_v2.yaml.
For examples, all the detections that are clearly belonging to class "Regular_vehicle" should have label 0, while they are predicted as label 1 ("Pedestrian"). Is it possible that the classes are shifted by one?
Thank you

Hi, please refer to the code of voxelnext head, which is used for  Argoverse. The class_id_mapping_each_head is used for mapping the prediction labels of each head to origin labels. https://github.com/happinesslz/LION/blob/d6e068eadbda05a6e4beb01bf0dda361fcf0279e/pcdet/models/dense_heads/voxelnext_head.py#L459

Thank you for your quick reply.
Apparently there is indeed a +1 on the predicted labels:
            ret_dict[bidx]['pred_labels'] = torch.cat(ret_dict[bidx]['pred_labels'], dim=0) + 1

Thank you for your quick reply. Apparently there is indeed a +1 on the predicted labels:
 ret_dict[bidx]['pred_labels'] = torch.cat(ret_dict[bidx]['pred_labels'], dim=0) + 1

Yes, be careful about whether the class labels start from 0 or 1.


Support C11 free()

With aligned_alloc() in the C11 standard, free() is called to free memory, rather than an equivalent aligned_free().
We should update our library with some logic that can be used to correctly call aligned_free() if free() is used instead.

Maybe we waste a few extra bytes in the aligned space... need a "magic" marker that indicates that this was allocated by aligned_malloc(). If the sentinel matches, then we call the aligned version.

👍  I would be all for this. It is good to mimic how GLIBC behaves. And I don't think the costs outweigh the benefit


Setup __tostring on class creation instead of per instance.

Coverage decreased (-0.1%) to 80.671% when pulling 0870bef9b78bc31c5c6dc5468ed58ae0aa1bffa6 on jvprat:class_tostring into 16d149338af9efc910528641c5240c5641aeb8db on stevedonovan:master.


Add Travis config

Note: needs travis to be enabled on the repo
Closes https://github.com/brianbianco/redisio/issues/187

It looks like Travis CI is failing with the following:
LoadError: cannot load such file -- kitchen

Ah i missed that require!
Fixed in https://github.com/brianbianco/redisio/pull/300


Additions

[x] Software: e.g. NAME - description. [GitHub] [paper]
[ ] Nice pictures to Software
[x] Add teaching
[x] Make lowercase
[x] Remove bottom bar

[ ] Add "Research" tab with details about key research directions with figures.


iptables reject requests

Describe the bug
Iptables reject requests to load-balanced services
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-EXTERNAL-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes externally-visible service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
KUBE-FORWARD  all  --  anywhere             anywhere             /* kubernetes forwarding rules */
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
ACCEPT     all  --  master.novalocal/16  anywhere
ACCEPT     all  --  anywhere             master.novalocal/16

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
KUBE-SERVICES  all  --  anywhere             anywhere             ctstate NEW /* kubernetes service portals */
KUBE-FIREWALL  all  --  anywhere             anywhere

Chain KUBE-EXTERNAL-SERVICES (1 references)
target     prot opt source               destination
REJECT     tcp  --  anywhere             anywhere             /* default/nginx:http has no endpoints */ ADDRTYPE match dst-type LOCAL tcp dpt:31541 reject-with icmp-port-unreachable
REJECT     tcp  --  anywhere             anywhere             /* default/nginx:https has no endpoints */ ADDRTYPE match dst-type LOCAL tcp dpt:30351 reject-with icmp-port-unreachable

Chain KUBE-FIREWALL (2 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             /* kubernetes firewall for dropping marked packets */ mark match 0x8000/0x8000

Chain KUBE-FORWARD (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             ctstate INVALID
ACCEPT     all  --  anywhere             anywhere             /* kubernetes forwarding rules */ mark match 0x4000/0x4000
ACCEPT     all  --  master.novalocal/16  anywhere             /* kubernetes forwarding conntrack pod source rule */ ctstate RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             master.novalocal/16  /* kubernetes forwarding conntrack pod destination rule */ ctstate RELATED,ESTABLISHED

Chain KUBE-SERVICES (3 references)
target     prot opt source               destination
REJECT     tcp  --  anywhere             <IP_ADDRESS>        /* default/nginx:http has no endpoints */ tcp dpt:http reject-with icmp-port-unreachable
REJECT     tcp  --  anywhere             master.novalocal     /* default/nginx:http has no endpoints */ tcp dpt:http reject-with icmp-port-unreachable
REJECT     tcp  --  anywhere             <IP_ADDRESS>        /* default/nginx:https has no endpoints */ tcp dpt:https reject-with icmp-port-unreachable
REJECT     tcp  --  anywhere             master.novalocal     /* default/nginx:https has no endpoints */ tcp dpt:https reject-with icmp-port-unreachable

To Reproduce
k3s v0.9.0 without traefik
service:
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app.kubernetes.io/name: nginx
  name: nginx
spec:
  replicas: 1
  selector:
    matchLabels:
      app.kubernetes.io/name: nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/name: nginx
      annotations:
        prometheus.io/scrape: "true"
        prometheus.io/port: "9113"
    spec:
      nodeName: master.novalocal
      imagePullSecrets:
        - name: regcred
      containers:
        - name: nginx
          image: registry.gitlab.com/webprod/nginx-docker:latest
          imagePullPolicy: Always
          ports:
            - containerPort: 80
            - containerPort: 443
        - name: nginx-prometheus-exporter
          image: nginx/nginx-prometheus-exporter:0.4.1
          ports:
            - containerPort: 9113
          args:
            - -web.listen-address
            - :9113
            - -nginx.plus
            - -nginx.scrape-uri
            - http://<IP_ADDRESS>:8080/api
---
apiVersion: v1
kind: Service
metadata:
  name: nginx
spec:
  selector:
    app: nginx
  ports:
    - port: 80
      targetPort: 80
      name: http
    - port: 443
      targetPort: 443
      name: https
  externalTrafficPolicy: Local
  type: LoadBalancer

Expected behavior
nginx available on 80/443 ports
Screenshots

Additional context
Add any other context about the problem here.

Sorry, I found bad selector in config


When Touch ID fails (wrong fingerprint) the passcode option does not appear. The text only shakes and shows the 'Cancel' button.

When Touch ID fails (wrong fingerprint) the passcode option does not appear. The text only shakes and shows the 'Cancel' button.
I Imported the module:
import { TouchID } from '@ionic-native/touch-id/ngx';

Injected the module into the constructor:
constructor(
    private touchId: TouchID
) {

}

And used the 'verifyFingerprint' method:
this.touchId.verifyFingerprint('Scan your fingerprint please').then(
    res => {
        console.log('Ok', res);
    }, err => {
        console.error('Error', err);
    }
);

I have Touch ID and a passcode setup on the (real) device. Am I missing a step?

I am also facing the same issue.  Its working fine in iPhone6 OS version 10 but not in iPhone6+ OS version 12

Thanks for adding information. I can only test iOS 11+ since my Capacitor is configured like that now.

The docs (https://developer.apple.com/documentation/localauthentication/lapolicy/lapolicydeviceownerauthenticationwithbiometrics?language=objc) says 'To let the system handle the fallback option by asking for the device passcode (in iOS or watchOS) or the user’s password (in macOS), use the LAPolicyDeviceOwnerAuthentication policy instead.'
I will try changing LAPolicyDeviceOwnerAuthenticationWithBiometrics to LAPolicyDeviceOwnerAuthentication in TouchID.m. I will report back another day.

It had something to do with LAPolicyDeviceOwnerAuthentication but not by simply replacing the policies in the TouchID.m file.
This repo fixes the issues described above: https://github.com/didux-io/cordova-plugin-touch-id. I have also requested a pull for this repo.
Package on npm: https://www.npmjs.com/package/@didux-io/cordova-plugin-touch-id
Behavior now:

User will be prompted for finger print if available
User will be prompted for passcode or fingerprint after one failed finger print attempt
User will be prompted for only the passcode if the fingerprint is disabled or if the fingerprint has been disabled by too many misuses.

I highly recommend using this package aswell: https://ionicframework.com/docs/native/pin-check with https://ionicframework.com/docs/native/open-native-settings
That library will check if the user has no passcode and provides you ways to navigate the user to set one, example code to use with that library:
import { PinCheck } from '@ionic-native/pin-check/ngx';
import { TouchID } from '@ionic-native/touch-id/ngx';
import { Platform } from '@ionic/angular';

.....

pinSetup = true;

constructor(
    private platform: Platform,
    private pinCheck: PinCheck,
    private touchId: TouchID
) {

}

openSecuritySettings() {
    if (this.platform.is('android')) {
        this.openNativeSettings.open('security');
    } else if (this.platform.is('ios')) {
        this.openNativeSettings.open('touch');
    }
}

checkLockScreenEnabled() {
    this.pinCheck.isPinSetup().then(
        () => {
           this.pinSetup = true;
        }, () => {
            this.pinSetup = false;
        }
    );
}

.....


R code is not executed at 'R markdown' syntax

In the current  R code is not executed at 'R markdown' syntax
I am a Korean who favored the R-box package of sublime text.
I really thank you for providing the packages R-box.
By the way, today I found the problem.
I think recently this issue occurred after sublime text 3 upgrade to the 3130 bulid.
When R markdown syntax situation in the cmd + enter code execution for the chunk of code in this does not send to command but paragraph skipped(next line). T_T

3103 introduces a new syntax format and R-Box has switched to the new format. And apparently, I didn't test enough. The version 2.9.8 should fix the issue.
Thanks for the report.

Code execution problem at R markdown syntax be fixed.
Thank you! :)


Monad flatMap/bind For Effects ?

I have been using redux-loop for a while,  it works great! In my attempt to understand Effects, and trying to add a typed mental model to it, I have reach a conclusion that an Effect is a stacked Monad of List and Promise (Promises are impure though, a better analogy would be Task monad, eg. from Data.Task).
newtype EffectOf a = EffectOf (Promise [a])
type Action = /* Plain JS Object */
type Effect = EffectOf Action

With this understanding, one thing critical in Monads, yet not exposed as public api is flatMap/bind. Effects.lift does serve as a map/fmap, though. Here's a sketch of what flatMap may look like:
const effTypes = {
  ...,
  FLATMAP : 'FLATMAP'
}
Effects.flatMap = (eff, func) => {
  return {
    type : effTypes.FLATMAP,
    effect : eff,
    factory : func,
    [isEffectSymbol] : true
  };
}
function effectToPromise(effect) {
  switch(effect.type) {
    ...
    case effTypes.FLATMAP:
      return effectToPromise(effect.effect)
        .then(actions =>
            Effects.batch( actions.map(effect.factory) ))
        .then(effectToPromise);
  }
}

This allows the creation of Effect that "evaluates" to another Effect, and run the "flattend" Effect as normal. Here's one artificial use case for it:
function getUser(action) {
  return Effects.promise(() =>
    fetch(`${apiUrl}/users/{action.payload.id}`)
      .then(user =>
          Effects.constant({ type: LOAD_SUCCESS, payload: {user} }))
      .catch(reason => Effects.none()));
}
function getProject(action) {
  return Effects.promise(() =>
    fetch(`${apiUrl}/projects/{action.payload.user.currentProjectId}`)
      .then(project =>
          Effects.constant({ type: LOAD_SUCCESS,
              payload: {...action.payload,project} }))
      .catch(reason => Effects.none()));
}
const reducer = createReducer({
  [LOAD_DATA_START](state, action) {
    const newState = { ...state, loading:true };
    // Effects.constant serves as unit/return from Monal definition
    const eff = Effects.constant(action);
    const apiEff = Effects.flatMap(
        Effects.flatMap(eff, getUser), getProject);
    // with haskell do notation:
    // const apiEff = do {
    //   userSuccessAction <- getUser(action)
    //   getProject(userSuccessAction)
    // }
    return loop(newState, apiEff);
  }
})

Although, this is easier to do with just promises (have a single Effects.promise) the above decomposition of getUser and getProject serves as small units of Effect factories, that can be reused individually in other context - and it will be nice if redux-loop includes machinery to compose them.
Another example below adapted from a real use case I had:
// dataReducer is a reducer that uses Effects.promise to fetch data
const decorateReducer = (dataReducer) => {
  return (state, action) => {
    const nextState = dataReducer(state, action);
    const effect = getEffect(nextState);
    if(effect) {
      const nextEffect = Effects.flatMap(effect, (act) =>
          (act.type === SUCCESS
          ? Effect.batch([act, hideLoadingGif()].map(Effects.constant))
          : Effect.batch([act, showErrorModal(act.payload)].map(Effects.constant))));
      return loop(state, nextEffect);
    }
    return nextState;
  };
}

import {decorateReducer} from 'somewhere-else';

const appReducer = decorateReducer((state, action) => {
  // does just data logic here
});

Lastly, I have this implemented in my fork and plan to play around with the idea a bit more (specifically how to integrate ap for applicative functor as well). If there's any interest in this direction of exploration, I can make a PR and some more examples.

Hey @yiransheng, I'm 100% willing to consider this as an addition to the API after getting the new version of the library released ( #79 ) after some further thought and discussion. In Elm, Cmds are functors only and leave off monad or applicative behavior. I would want to spend some time evaluating what the trade-offs are and if it turns out this is a net positive then I'd be happy to include it as a minor version release. Sound good?

Sounds like a reasonable plan. Let's revisit the issue some time later :) Thanks @lukewestby.

@yiransheng redux-loop will be equipped with a proper Task type in the next version which is a monad with chain and chainError functions. You can use it to compose things the way you want and then perform that resulting task to get a Cmd
https://github.com/redux-loop/redux-loop/pull/95

Thanks @lukewestby for the good work, new API looks great!


Add Into implementations for HashMap and Vec

Naturally, the elements of the Vec/HashMap also need to implement Into<Value>; plus one snowflake case for HashMap<String, Into<Value>> (since Strings aren't Into) just to make working with hashmaps a little easier.

I'll check this tomorrow

All seems simple enough anyway. We don't push out new debugger releases for a change like this so there's no reason to not merge it.


[ssoc'2023] traveling salesman problem

Is your feature request related to a problem? Please describe.
As I haven't seen tsp related problems, so I want to do this.
Describe the solution you'd like
want to solve tsp problem using c

@Kumar-laxmi Sir ji please assign me this issue as I eagerly want to contribute to this issue under SSoC'23.

@Kumar-laxmi  Sir please assign me this as I want to contribute in SSOC'23 and I am practicing dsa as well so kindly provide me this.


Failing test cases for reentrant ReplaySubject

Added 2 failing test cases for ReplaySubject:

the first is similar to an already existing test, but shows some more unexpected result
for the second I dont even know what to say. lets say the result is weird

I've implemented a possible fix in https://github.com/backbone87/rxjs/pull/1


Packaging win32 on macOS stuck after rcedit

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Please describe your issue:
When I try to package my electron app for all platforms on macOS, it always hangs up at win32 build.
(Tested on TravisCI and CircleCI)

Console output when you run electron-packager with the environment variable DEBUG=electron-packager. Please include the stack trace if one exists.
electron-packager Electron Packager 8.7.2 +0ms
  electron-packager Node v6.11.2 +3ms
  electron-packager Host Operating system: darwin (x64) +3ms
  electron-packager Packager Options: {"_":[".","my-sample-app"],"all":true,"deref-symlinks":true,"download":{"strictSSL":true},"overwrite":false,"prune":true,"quiet":false,"asar":true,"out":"dist","dir":".","name":"my-sample-app","protocols":[]} +0ms
  electron-packager Target Platforms: darwin, linux, mas, win32 +3ms
  electron-packager Target Architectures: ia32, x64, armv7l +2ms
  electron-packager Inferring appVersion from version in /Users/travis/build/phpfs/electron-quick-start/package.json +16ms
  electron-packager Inferring target Electron version from electron in /Users/travis/build/phpfs/electron-quick-start/package.json +6ms
  electron-packager Application name: my-sample-app +1ms
  electron-packager Target Electron version: 1.6.11 +0ms
  electron-packager Ignored path regular expressions: [ '/node_modules/electron($|/)',
  '/node_modules/electron-prebuilt(-compile)?($|/)',
  '/node_modules/electron-packager($|/)',
  '/\\.git($|/)',
  '/node_modules/\\.bin($|/)',
  '\\.o(bj)?$' ] +2ms
  electron-packager Downloading Electron with options {"strictSSL":true,"platform":"linux","arch":"ia32","version":"1.6.11"} +7ms
Packaging app for platform linux ia32 using electron v1.6.11
  electron-packager Creating /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32-template +4s
  electron-packager Extracting /Users/travis/Library/Caches/electron/electron-v1.6.11-linux-ia32.zip to /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32-template +2ms
  electron-packager Initializing app in /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32/my-sample-app-linux-ia32 from /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32-template template +2s
  electron-packager Ignored paths based on the out param: [ '/Users/travis/build/phpfs/electron-quick-start/dist' ] +4ms
  electron-packager Pruning modules via: npm prune --production +1s
  electron-packager Running asar with the options {} +2s
  electron-packager Renaming electron to my-sample-app in /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32/my-sample-app-linux-ia32 +1s
  electron-packager Moving /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/linux-ia32/my-sample-app-linux-ia32 to dist/my-sample-app-linux-ia32 +1ms
  electron-packager Downloading Electron with options {"strictSSL":true,"platform":"win32","arch":"ia32","version":"1.6.11"} +2ms
Packaging app for platform win32 ia32 using electron v1.6.11
  electron-packager Creating /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/win32-ia32-template +2s
  electron-packager Extracting /Users/travis/Library/Caches/electron/electron-v1.6.11-win32-ia32.zip to /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/win32-ia32-template +1ms
  electron-packager Initializing app in /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/win32-ia32/my-sample-app-win32-ia32 from /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/win32-ia32-template template +2s
  electron-packager Ignored paths based on the out param: [ '/Users/travis/build/phpfs/electron-quick-start/dist' ] +3ms
  electron-packager Pruning modules via: npm prune --production +1s
  electron-packager Running asar with the options {} +3s
  electron-packager Renaming electron.exe to my-sample-app.exe in /var/folders/my/m6ynh3bn6tq06h7xr3js0z7r0000gn/T/electron-packager/win32-ia32/my-sample-app-win32-ia32 +1s
  electron-packager Running rcedit with the options {"version-string":{},"file-version":"1.0.0","product-version":"1.0.0"} +2ms

What command line arguments are you passing? Alternatively, if you are using the API, what
parameters are you passing to the packager() function?
DEBUG=electron-packager electron-packager . my-sample-app --all --asar --out=dist

Please provide either a failing minimal testcase (with a link to the code) or detailed steps to
reproduce your problem. Using electron-quick-start
is a good starting point.
I forked electron-quick-start to phpfs/electron-quick-start and added TravisCI!
Thanks so far :)
EDIT: Added Build 2 with NodeJS 8 and Build 3 with "DEBUG=*" and NodeJS 6.

I fixed it by using your method of installing wine instead of homebrew!
I created this repo for everybody having the same problem:
https://github.com/phpfs/electron-packager-macos


Legal/Compliance for GDPR

In EU we have an upcoming regulation tightening the protection of data for any EU citizens which will extend to those registering on non-EU sites.
Currently the first use case with Red Cross presumably doesn't run into this issue, but should we start to consider how we are compliant in the future?
It's quite complex and not all the regulations are clear but here is the overview:
https://ico.org.uk/for-organisations/data-protection-reform/overview-of-the-gdpr/

cc @tonysurma @BillWagner


Error handling gifs with transparency

I'm currently using wagtail (version 1.0rc2)  and as instructed per the documentation I had wand (version 0.4.0) installed and also have Willow installed from the latest git. I've tried processing a gif and expect that will work seamlessly however this is not the case. One of the images will simply not allow me to upload it (stacktrace below) the other continues to do as what was reported in torchbox/wagtail#1084.
Image 1
Stacktrace:
Internal Server Error: /admin/images/chooser/upload/
Traceback (most recent call last):
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/django/views/decorators/cache.py", line 43, in _cache_controlled
    response = viewfunc(request, *args, **kw)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/django/contrib/auth/decorators.py", line 22, in _wrapped_view
    return view_func(request, *args, **kwargs)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/wagtail/wagtailimages/views/chooser.py", line 140, in chooser_upload
    {'image_json': get_image_json(image)}
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/wagtail/wagtailimages/views/chooser.py", line 22, in get_image_json
    preview_image = image.get_rendition('max-130x100')
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/wagtail/wagtailimages/models.py", line 191, in get_rendition
    generated_image, output_format = filter.run(self, BytesIO())
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/wagtail/wagtailimages/models.py", line 356, in run
    willow.save(willow.original_format, output)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/willow/image.py", line 67, in save
    return getattr(self, operation_name)(output)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/willow/image.py", line 28, in operation
    return func(self.backend, *args, **kwargs)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/willow/backends/pillow.py", line 81, in save_as_gif
    backend.image.save(f, 'GIF', transparency=backend.image.info['transparency'])
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/PIL/Image.py", line 1703, in save
    save_handler(self, fp, filename)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/PIL/GifImagePlugin.py", line 376, in _save
    _get_local_header(fp, im, (0, 0), flags)
  File "/home/vagrant/bacontrols_venv/local/lib/python2.7/site-packages/PIL/GifImagePlugin.py", line 412, in _get_local_header
    transparency = int(transparency)
TypeError: int() argument must be a string or a number, not 'tuple'

I have attached below the images that I seem to be having issues with.
Image 1(Will not upload, stacktrace above)

Image 2(Continues to fill transparent area with other colours as per wagtail issue torchbox/wagtail#1084, wand 0.4.0 is installed.)

Image 2 (Broken)

I am running into this identical issue. I'm currently running Wagtail 1.0, Wand 0.4.0, Pillow 2.8.1, and Willow 0.2.1. Has there been a solution to fix this yet?

To everyone who'll stumble upon this issue - it's solved by https://github.com/sehmaschine/django-filebrowser/commit/b5923202758b69a9102b7453788d4362481faf40 which was apperently not released yet

I believe the stacktrace above on transparent GIFs was caused by a if/elif bug in wagtailimages/models.py causing a second attempt to save the same file. This got fixed some time ago.


migration to null safety and fix #14

Hey @hasan-hm1, your lib is popular on pub.dev, it will be great if you provide a new version, at least for null safety!
Almost all the work is done, you just have to publish.


Xcode 8 beta fails to build

I have a swift project that runs tests on travis-ci, and once I created the swift 3 branch and tried to run the tests it failed on an assertion. The tests themselves are fine since I have successfully run them locally.
=== TEST ===

  xcodebuild build build

2016-07-04 13:15:12.969 xctool[1420:4193] *** Assertion failure in __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke(), /tmp/xctool20160411-73857-17y7ykv/xctool-0.2.9/Common/XCToolUtil.m:380

2016-07-04 13:15:13.012 xctool[1420:4193] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got error while trying to deserialize event 'User defaults from command line:': The data is not in the correct format.'

*** First throw call stack:

(

    0   CoreFoundation                      0x00007fff813f24f2 __exceptionPreprocess + 178

    1   libobjc.A.dylib                     0x00007fff80e1473c objc_exception_throw + 48

    2   CoreFoundation                      0x00007fff813f71ca +[NSException raise:format:arguments:] + 106

    3   Foundation                          0x00007fff8e9001ee -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 169

    4   xctool                              0x0000000107bf78c4 __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke + 441

    5   xctool                              0x0000000107c32c39 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke + 165

    6   xctool                              0x0000000107c32f42 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke.26 + 612

    7   xctool                              0x0000000107c330ae __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke_2.49 + 188

    8   libdispatch.dylib                   0x00007fff8b494c0b ___dispatch_operation_deliver_data_block_invoke + 118

    9   libdispatch.dylib                   0x00007fff8b47f93d _dispatch_call_block_and_release + 12

    10  libdispatch.dylib                   0x00007fff8b47440b _dispatch_client_callout + 8

    11  libdispatch.dylib                   0x00007fff8b47903b _dispatch_queue_drain + 754

    12  libdispatch.dylib                   0x00007fff8b47f707 _dispatch_queue_invoke + 549

    13  libdispatch.dylib                   0x00007fff8b479200 _dispatch_queue_drain + 1207

    14  libdispatch.dylib                   0x00007fff8b47f707 _dispatch_queue_invoke + 549

    15  libdispatch.dylib                   0x00007fff8b477d53 _dispatch_root_queue_drain + 538

    16  libdispatch.dylib                   0x00007fff8b477b00 _dispatch_worker_thread3 + 91

    17  libsystem_pthread.dylib             0x00007fff837ba4de _pthread_wqthread + 1129

    18  libsystem_pthread.dylib             0x00007fff837b8341 start_wqthread + 13

)

libc++abi.dylib: terminating with uncaught exception of type NSException

/Users/travis/build.sh: line 45:  1420 Abort trap: 6           xctool -works

https://travis-ci.org/cezheng/Fuzi/builds/140457732

Getting the same error in an objective-c framework. Works fine with xcode 7.3.1, but once I switch to 8 I get this:
2016-07-05 16:33:54.656 xctool[30021:574484] *** Assertion failure in __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke(), /Users/nekto/Projects/xctool/Common/XCToolUtil.m:380
2016-07-05 16:33:54.657 xctool[30021:574484] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got error while trying to deserialize event 'Build settings from command line:': The data is not in the correct format.'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff9a0324f2 __exceptionPreprocess + 178
	1   libobjc.A.dylib                     0x00007fff95505f7e objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff9a0371ca +[NSException raise:format:arguments:] + 106
	3   Foundation                          0x00007fff9d3d01ee -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 169
	4   xctool                              0x000000010a9ada24 __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke + 441
	5   xctool                              0x000000010a9e8d99 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke + 165
	6   xctool                              0x000000010a9e90a2 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke.26 + 612
	7   xctool                              0x000000010a9e920e __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke_2.49 + 188
	8   libdispatch.dylib                   0x00007fff8a0f7c0b ___dispatch_operation_deliver_data_block_invoke + 118
	9   libdispatch.dylib                   0x00007fff8a0e293d _dispatch_call_block_and_release + 12
	10  libdispatch.dylib                   0x00007fff8a0d740b _dispatch_client_callout + 8
	11  libdispatch.dylib                   0x00007fff8a0dc03b _dispatch_queue_drain + 754
	12  libdispatch.dylib                   0x00007fff8a0e2707 _dispatch_queue_invoke + 549
	13  libdispatch.dylib                   0x00007fff8a0dc200 _dispatch_queue_drain + 1207
	14  libdispatch.dylib                   0x00007fff8a0e2707 _dispatch_queue_invoke + 549
	15  libdispatch.dylib                   0x00007fff8a0dad53 _dispatch_root_queue_drain + 538
	16  libdispatch.dylib                   0x00007fff8a0dab00 _dispatch_worker_thread3 + 91
	17  libsystem_pthread.dylib             0x00007fff920f64de _pthread_wqthread + 1129
	18  libsystem_pthread.dylib             0x00007fff920f4341 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException```

I am getting no response travis build fails after 10 mins
Environment: osx
Target: 10.11
Command: xctool -scheme myappscheme -workspace myapp.xcworkspace
This worked xcode 7.3.1

Looks like xctool is not compatible with Xcode 8. I am hitting the same problem:
=== CLEAN ===

  xcodebuild clean CleanroomASL-iOS
2016-07-20 12:47:40.937 xctool[31294:843518] *** Assertion failure in __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke(), /tmp/xctool/Common/XCToolUtil.m:380
2016-07-20 12:47:40.940 xctool[31294:843518] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got error while trying to deserialize event '=== CLEAN TARGET CleanroomASL-iOS OF PROJECT CleanroomASL WITH CONFIGURATION Debug ===': The data is not in the correct format.'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff948bb4f2 __exceptionPreprocess + 178
	1   libobjc.A.dylib                     0x00007fff9888c73c objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff948c01ca +[NSException raise:format:arguments:] + 106
	3   Foundation                          0x00007fff8be251ee -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 169
	4   xctool                              0x0000000100de282b __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke + 683
	5   xctool                              0x0000000100e6ab7b __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke + 107
	6   xctool                              0x0000000100e6af54 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke.26 + 436
	7   xctool                              0x0000000100e6b4c3 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke_2.49 + 435
	8   libdispatch.dylib                   0x00007fff8c94bc0b ___dispatch_operation_deliver_data_block_invoke + 118
	9   libdispatch.dylib                   0x00007fff8c93693d _dispatch_call_block_and_release + 12
	10  libdispatch.dylib                   0x00007fff8c92b40b _dispatch_client_callout + 8
	11  libdispatch.dylib                   0x00007fff8c93003b _dispatch_queue_drain + 754
	12  libdispatch.dylib                   0x00007fff8c936707 _dispatch_queue_invoke + 549
	13  libdispatch.dylib                   0x00007fff8c930200 _dispatch_queue_drain + 1207
	14  libdispatch.dylib                   0x00007fff8c936707 _dispatch_queue_invoke + 549
	15  libdispatch.dylib                   0x00007fff8c92ed53 _dispatch_root_queue_drain + 538
	16  libdispatch.dylib                   0x00007fff8c92eb00 _dispatch_worker_thread3 + 91
	17  libsystem_pthread.dylib             0x00007fff97de54de _pthread_wqthread + 1129
	18  libsystem_pthread.dylib             0x00007fff97de3341 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Abort trap: 6

Unfortunately Facebook doesn't have any plans to support xctool in Xcode 8. I will keep you updated if something changes. Sorry, folks.

@ExtremeMan

Unfortunately Facebook doesn't have any plans to support xctool in Xcode 8.
Does this mean just right now or even after Xcode 8.0's final release? If latter, is this project somewhat deprecated & we should look for something else to run the tests?

Does this mean just right now or even after Xcode 8.0's final release?

We haven't decided yet but it would be safer for you to look for something else. May be we will ship Buck with some simple test utility or extend FBSimulatorControl.
I am here though if our community wants to actively work on xctool and support future releases of Xcode.

@ExtremeMan Does this mean that facebook is not internally using xctool for running Xcode tests anymore?

@cezheng we use it for Xcode 7 builds.

@ExtremeMan Thanks for the information. Wish facebook will ship an even better tool for Xcode 8 then:)

Thanks for the heads-up, @ExtremeMan. That's too bad, but I appreciate the work that went into it and the opportunity to use it for free all these years. Might I suggest updating the README to mention that xctool will no longer be supported as of Xcode 8? If you'd like a pull request for that, I'd be happy to do it.

@emaloney, I will update README as soon as we are sure we deprecate it. Also we will move it to Facebook archives if so is decided.

To clear up the error message that you're seeing here, in Xcode 8 added "Increased Xcode.app security due to runtime library validation".
What's happening with xctool is that the shims that xctool injects into the xcodebuild process is prevented from being loaded at runtime. xctool relies on these shims in order to do its magic. You can see this in the syslog in this gist, or by running syslog | grep deny | grep xctool

There is still a way to workaround added Xcode restrictions by resigning it. People are going to that to run Xcode plugins and I would expect CI system to do that as well in order to continue using such tools as xctool in future until Apple's own tools are good enough for them.

@ExtremeMan Can you please give some more details on how that resigning would work? That sounds interesting!

I found all the details here: https://github.com/alcatraz/Alcatraz/issues/475. But I haven't tried myself.

Thank you!

I have some good news to share :)
All you need to make xctool work again is use https://github.com/steakknife/unsign to unsign the XCTest binary in /Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/Library/Frameworks/XCTest.framework
Then xctool just works @plu @ExtremeMan

@oliverhu without any patches to the tool? What about application tests?

@ExtremeMan it seems you just need to wipe out all the signatures around all dependent dylib/binaries. I also wiped xcodebuild.
Prior to wiping:

khu@khu-mn1:~/ios/mntf-ios_trunk (master)$ /Users/khu/ios/dev/voyager-ios_trunk/build/xctool/bin/xctool -scheme mntf-iosSampleApp -workspace mntf-ios.xcworkspace/ run-tests
[Info] Loading settings for scheme 'mntf-iosSampleApp' ...2016-07-30 00:24:04.217 xctool[31271:341530] *** Assertion failure in -[XcodeSubjectInfo buildSettingsForATarget], /export/home/tester/hudson/data/workspace/MP_TRUNKDEV_POSTCOMMIT/li-xctool_6d91edca1256f2d73a4e6ed7f0b0646e323ea064/xctool/src/xctool/xctool/xctool/XcodeSubjectInfo.m:839

2016-07-30 00:24:04.350 xctool[31271:341530] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed while trying to gather build settings for your scheme; tried with actions: build, test, analyze. Errors above occured while running xcodebuild -showBuildSettings:
  dyld: warning: could not load inserted library '/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib' into library validated process because no suitable image found.  Did find:
	/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib: cannot load image with wrong team ID in process using Library Validation
dyld: Library not loaded: @rpath/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core
  Referenced from: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/xcodebuild
  Reason: no suitable image found.  Did find:
	/Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core: mmap() error 1 at address=0x107831000, size=0x0007E000 segment=__TEXT in Segment::map() mapping /Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core
.
  dyld: warning: could not load inserted library '/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib' into library validated process because no suitable image found.  Did find:
	/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib: cannot load image with wrong team ID in process using Library Validation
dyld: Library not loaded: @rpath/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core
  Referenced from: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/xcodebuild
  Reason: no suitable image found.  Did find:
	/Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core: mmap() error 1 at address=0x11113C000, size=0x0007E000 segment=__TEXT in Segment::map() mapping /Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core
.
  dyld: warning: could not load inserted library '/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib' into library validated process because no suitable image found.  Did find:
	/Users/khu/ios/dev/voyager-ios_trunk/build/xctool/lib/xcodebuild-fastsettings-shim.dylib: cannot load image with wrong team ID in process using Library Validation
dyld: Library not loaded: @rpath/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core
  Referenced from: /Applications/Xcode-beta.app/Contents/Developer/usr/bin/xcodebuild
  Reason: no suitable image found.  Did find:
	/Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core: mmap() error 1 at address=0x103853000, size=0x0007E000 segment=__TEXT in Segment::map() mapping /Applications/Xcode-beta.app/Contents/Developer/usr/bin/../../../PlugIns/Xcode3Core.ideplugin/Contents/MacOS/Xcode3Core.

*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff969fd4f2 __exceptionPreprocess + 178
	1   libobjc.A.dylib                     0x00007fff8ca71f7e objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff96a021ca +[NSException raise:format:arguments:] + 106
	3   Foundation                          0x00007fff9bc5e856 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 198
	4   xctool                              0x000000010c1f7754 -[XcodeSubjectInfo buildSettingsForATarget] + 955
	5   xctool                              0x000000010c1f86f9 -[XcodeSubjectInfo loadSubjectInfo] + 551
	6   xctool                              0x000000010c1e4aed -[Options validateAndReturnXcodeSubjectInfo:errorMessage:] + 3489
	7   xctool                              0x000000010c1d6780 -[XCTool run] + 2292
	8   xctool                              0x000000010c1d5497 main + 1064
	9   xctool                              0x000000010c1d0844 start + 52
	10  ???                                 0x0000000000000006 0x0 + 6
)
libc++abi.dylib: terminating with uncaught exception of type NSException

After wiping, all warnings are gone, however, I was celebrating too early, not fully working yet, now I get:

[Info] Loading settings for scheme 'mntf-iosSampleApp' ... (956 ms)

=== RUN-TESTS ===

  [Info] Collecting info for testables...2016-07-30 00:26:10.632 xctool[31341:343843] *** Assertion failure in -[SimulatorInfo systemRootForSimulatedSdk], /export/home/tester/hudson/data/workspace/MP_TRUNKDEV_POSTCOMMIT/li-xctool_6d91edca1256f2d73a4e6ed7f0b0646e323ea064/xctool/src/xctool/xctool/xctool/SimulatorWrapper/SimulatorInfo.m:283
2016-07-30 00:26:10.633 xctool[31341:343843] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Unable to instantiate DTiPhoneSimulatorSystemRoot for platform iphonesimulator and sdk version 10.0. Available roots: (null)'
*** First throw call stack:
(
	0   CoreFoundation                      0x00007fff969fd4f2 __exceptionPreprocess + 178
	1   libobjc.A.dylib                     0x00007fff8ca71f7e objc_exception_throw + 48
	2   CoreFoundation                      0x00007fff96a021ca +[NSException raise:format:arguments:] + 106
	3   Foundation                          0x00007fff9bc5e856 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 198
	4   xctool                              0x0000000106b27414 -[SimulatorInfo systemRootForSimulatedSdk] + 685
	5   xctool                              0x0000000106b2749c -[SimulatorInfo simulatedRuntime] + 63
	6   xctool                              0x0000000106b2768a -[SimulatorInfo simulatedDevice] + 76
	7   xctool                              0x0000000106b066fb CreateTaskForSimulatorExecutable + 267
	8   xctool                              0x0000000106b252a5 -[OCUnitIOSAppTestQueryRunner createTaskForQuery] + 441
	9   xctool                              0x0000000106b1234c -[OCUnitTestQueryRunner runQueryWithError:] + 361
	10  xctool                              0x0000000106b42b0f +[TestableExecutionInfo queryTestCasesWithSimulatorInfo:error:] + 411
	11  xctool                              0x0000000106b4209e +[TestableExecutionInfo infoForTestable:buildSettings:simulatorInfo:] + 304
	12  xctool                              0x0000000106b18cb2 __56-[RunTestsAction runTestables:options:xcodeSubjectInfo:]_block_invoke + 883
	13  libdispatch.dylib                   0x00007fff8dfe693d _dispatch_call_block_and_release + 12
	14  libdispatch.dylib                   0x00007fff8dfdb40b _dispatch_client_callout + 8
	15  libdispatch.dylib                   0x00007fff8dfe003b _dispatch_queue_drain + 754
	16  libdispatch.dylib                   0x00007fff8dfe6707 _dispatch_queue_invoke + 549
	17  libdispatch.dylib                   0x00007fff8dfdb40b _dispatch_client_callout + 8
	18  libdispatch.dylib                   0x00007fff8dfdf29b _dispatch_root_queue_drain + 1890
	19  libdispatch.dylib                   0x00007fff8dfdeb00 _dispatch_worker_thread3 + 91
	20  libsystem_pthread.dylib             0x00007fffa11384de _pthread_wqthread + 1129
	21  libsystem_pthread.dylib             0x00007fffa1136341 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException

Abort trap: 6

Last one looks fine because it is at least xctool failing, not Xcode tools. Thanks for the info. Probably it is worth investigating futher.

I guess https://github.com/facebook/xctool/pull/707 helps to solve the latest issue you hit, @oliverhu?

Yah, I used _dyld_register_func_for_add_image to solve that problem and #707 is also a good fix :D I made it to run tests in simulators but the test report is still broken. I'll take some time this weekend to hack more.

@oliverhu, can you share what you currently have via a PR or a forked branch? We have some people looking into this, so it might be worth sharing the progress!

Sure, it is a mess now, i'll clean things up and push to a forked branch

https://github.com/oliverhu/xctool/commit/1aff5db64312b939a18f413a34c07aee76bf7639
Still messy, but may help :D

Applied @k21's fix in #707  and now it works under https://github.com/oliverhu/xctool/tree/xcode8

Here's an update on my front:
Xcode beta >= 4 needs everything dynamically linked to be signed with:
codesign --force --sign - --timestamp=none [filename]

Therefore, otest-query, otest-shim and every .xctest bundles need to be signed.

Quick update here. @dinhviethoa has a fix for Xcode 8 which he will publish very soon. We are going to keep supporting testing features of xctool in Xcode 7 and 8.

Nice work @dinhviethoa! I've been testing and I found an issue with the way we're rewriting -simulatedRuntime in this pull request.
When I run this using -destination 'name=iPhone 6s,OS=10.0', it is finding the incorrect runtime for the given SDK. For example, given the path (which seems correct):
/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator10.0.sdk

[SimulatorInfo _runtimeWithSDKPath:path] returns the incorrect .simruntime instance:
(lldb) expr SimRuntime* $sr = [SimulatorInfo _runtimeWithSDKPath:path]
(lldb) po $sr
SimRuntime : 7.1 (11D167) - com.apple.CoreSimulator.SimRuntime.iOS-7-1 (unavailable, The iOS 7.1 simulator runtime is not supported after 10.10.5.)
(lldb) po $sr->_bundle
NSBundle </Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 7.1.simruntime> (not yet loaded)

Seems to me the string comparison is just returning the first SimRuntime instance returned by [SimRuntime supportedRuntimes].
(lldb) po [SimRuntime supportedRuntimes]
<__NSArrayI 0x101741800>(
SimRuntime : 7.1 (11D167) - com.apple.CoreSimulator.SimRuntime.iOS-7-1 (unavailable, The iOS 7.1 simulator runtime is not supported after 10.10.5.),
SimRuntime : 8.1 (12B411) - com.apple.CoreSimulator.SimRuntime.iOS-8-1,
SimRuntime : 8.2 (12D508) - com.apple.CoreSimulator.SimRuntime.iOS-8-2,
SimRuntime : 8.4 (12H141) - com.apple.CoreSimulator.SimRuntime.iOS-8-4,
SimRuntime : 10.0 (14A5339a) - com.apple.CoreSimulator.SimRuntime.iOS-10-0,
SimRuntime : 10.0 (14T5326a) - com.apple.CoreSimulator.SimRuntime.tvOS-10-0,
SimRuntime : 3.0 (14S5320a) - com.apple.CoreSimulator.SimRuntime.watchOS-3-0
)

The for loop is matching the first SimRuntime because the platformPath is the same:
(lldb) po platformPath
/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform

(lldb) expr SimRuntime *$firstRuntime = [runTimeArray firstObject]
(lldb) po [$firstRuntime platformPath]
/Applications/Xcode-beta.app/Contents/Developer/Platforms/iPhoneSimulator.platform

I think what you want to do is filter by the sdk version, which is what the previous code did. So instead of this (your change):
+ (SimRuntime *)_runtimeWithSDKPath:(NSString *)path
{
  path = [path stringByResolvingSymlinksInPath];
  NSDictionary *sdkInfo = __sdkInfoByPath[path];
  NSString *platformName = sdkInfo[@"PlatformName"];
  NSDictionary *platformInfo = __platformInfo[platformName];
  NSString *platformPath = platformInfo[@"PlatformPath"];

  NSArray *runTimeArray = [SimRuntime supportedRuntimes];
  for (SimRuntime* runTime in runTimeArray) {
    if ([[runTime platformPath] isEqualToString:platformPath]) {
      return runTime;
    }
  }
  return nil;
}

You probably want to also make sure you're getting the right version too:
+ (SimRuntime *)_runtimeWithSDKPath:(NSString *)path
{
  path = [path stringByResolvingSymlinksInPath];
  NSDictionary *sdkInfo = __sdkInfoByPath[path];
  NSString *platformName = sdkInfo[@"PlatformName"];
  NSDictionary *platformInfo = __platformInfo[platformName];
  NSString *platformPath = platformInfo[@"PlatformPath"];

  NSString *platformVersion = sdkInfo[@"Version"];

  NSArray *runTimeArray = [SimRuntime supportedRuntimes];
  for (SimRuntime* runTime in runTimeArray) {
    if ([[runTime platformPath] isEqualToString:platformPath] &&
        [[runTime versionString] isEqualToString:platformVersion]) {
      return runTime;
    }
  }
  return nil;
}

Or something that is more unique that will match the expected runtime.

I should add, I also had to run your codesign --force --sign - --timestamp=none [filename] manually before I could get your pull request with my fix to work, I think because I'm using the -appTest flag in xctool like so (actual paths omitted):
$ /Users/alan/repositories/github/xctool/xctool.sh -sdk iphonesimulator -destination 'name=iPhone 6s,OS=10.0' run-tests -appTest /path/to/AppNameTests.xctest:/path/to/AppName.app/AppName

Once I signed that test bundle:
$ codesign --force --sign - --timestamp=none /path/to/AppNameTests.xctest:/path/to/AppName.app/AppName

The xctool command worked as expected.

Should be fixed on master.

So I think we should also add a step in xctool that makes sure to also codesign the test bundle when provided via -appTest.

Is it covered in your PR @dinhviethoa?

So I think we should also add a step in xctool that makes sure to also codesign the test bundle when provided via -appTest.
Is it covered in your PR @dinhviethoa?

It's not yet!
We can take care of that in a following-up PR.

There still isn't a fix for the -appTest signing issue but we worked around it by writing a shell script that signs the xctest bundle before passing all the arguments to xctool.

@alanzeino -- I am not sure why but for my old workspace everything just works without any scripts. I think there might be additional settings somewhere in project file to sign your test bundles. Xcode can do that for you.

@ExtremeMan you might be right. We're using buck though so it won't work for us :)

Ah, for Buck - yes. I think we added an explicit step for our apps.

@alanzeino, Buck has been updated to codesign all the Apple bundles it builds in https://github.com/facebook/buck/commit/a8f2389cc90adc928292d466365c5c796ba6450b. Are you using a recent version of Buck that includes that commit? If you are and you still see the error, please file an issue in the Buck repository.

Still running into this error wtih Xcode 8:
2016-09-19 14:26:32.566 xctool[64616:8503245] *** Assertion failure in __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke(), tools/xctool/Common/XCToolUtil.m:395
2016-09-19 14:26:32.566 xctool[64616:8503245] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got error while trying to deserialize event 'User defaults from command line:': The data is not in the correct format.'
xctool is built from master, at c5d98ef3fee4467e163498fdeb59ac1cf38ec2b3
XCode is Version 8.0 (8A218a)
Command line: tools/xctool/xctool.sh -project src/test/test.xcodeproj
-scheme sin_test_all
-configuration Debug
-destination 'platform=iOS Simulator,name=iPhone 6s,OS=10.0'
-reporter plain
-reporter junit:out/test-reports/sin_test_all.xml
test
-test-sdk iphonesimulator
-freshSimulator
-freshInstall

how do I install from master?
I've tried with brew install -v --HEAD xctool, but I get this message

xctool-0.2.9 already installed

and still getting the same error

@jcesarmobile, run brew reinstall --HEAD xctool or uninstall the non-HEAD version first.

@k21 thanks, tried with both reinstall and uninstalling first, but I still have "The data is not in the correct format." error

Same here. I run
brew uninstall xctool
brew install -v --HEAD xctool
xctool --version # this is 0.2.10
xctool -workspace MyApp.xcworkspace -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 7,OS=10.0'

And I still get the error. What's the best input to give you?

It's a known issue :(
https://github.com/facebook/xctool/pull/712 was an attempt to bypass and use xcodebuild instead.

Hum? @ExtremeMan said "Should be fixed on master." But I dunno because the issue label is in progress

xctool doesn't support building since Xcode 8. But you can use xctool to run tests.

Ah ok. How would I do that? Build with xcode and test with xctool ?

Yeah, you can use xcodebuild, xcbuild or buck to build. Then you can pass application test bundle and/or xctest bundle to xctool to run tests.

So should the final thing be something like
xcodebuild -workspace MyApp.xcworkspace -scheme MyApp -destination 'platform=iOS Simulator,name=iPhone 7,OS=10.0'
xctool -workspace MyApp.xcworkspace -scheme MyApp  run-tests

? Sorry I'm not sure how to pass the bundle around

That might work but I am not sure if xctool is able to pickup correct bundles after xcodebuild. Czna you try and say it it works?
If it doesn't you might end up running xcodebuild -showBuildSettings and extracting paths to test host app and xctest bundle from the output of that command.

Doesn't look like it's working. I'm moving the discussion on how to build with something else here: https://github.com/facebook/xctool/issues/715

I'm using xctool 0.2.10 (from master) and got this error:

2016-10-04 18:50:31.047 xctool[5019:1134172] +[SimDeviceType supportedDeviceTypesByAlias]: unrecognized selector sent to class 0x10866ffe0
2016-10-04 18:50:31.180 xctool[5019:1134172] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '+[SimDeviceType supportedDeviceTypesByAlias]: unrecognized selector sent to class 0x10866ffe0'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff910d44f2 __exceptionPreprocess + 178
1   libobjc.A.dylib                     0x00007fff8922ef7e objc_exception_throw + 48
2   CoreFoundation                      0x00007fff9113e0ad +[NSObject(NSObject) doesNotRecognizeSelector:] + 205
3   CoreFoundation                      0x00007fff91044571 forwarding + 1009
4   CoreFoundation                      0x00007fff910440f8 _CF_forwarding_prep_0 + 120
5   xctool                              0x0000000107d63e18 +[SimulatorInfo deviceNameForAlias:] + 58
6   xctool                              0x0000000107d49122 -[Options _validateDestinationWithErrorMessage:] + 365
7   xctool                              0x0000000107d47b6c -[Options validateAndReturnXcodeSubjectInfo:errorMessage:] + 104
8   xctool                              0x0000000107d394ca -[XCTool run] + 2858
9   xctool                              0x0000000107d37ebd main + 1151
10  xctool                              0x0000000107d328f4 start + 52
11  ???                                 0x0000000000000009 0x0 + 9
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6

using this command:

xctool -configuration Test -destination 'platform=iOS Simulator,OS=10.1,name=iPhone 7' -showTasks test OBJROOT=./Build

anyone with the same problem?

@cegonya I've seen similar with our own projects, also on 0.2.10 and Xcode 8.1 beta 3.
I'm new to reverse engineering Xcode frameworks, but from my debugging with otool -ov /Applications/Xcode.app/Contents/Developer/Library/PrivateFrameworks/CoreSimulator.framework/CoreSimulator it looks like a lot of functionality related to devicetypes / runtimes / devices has moved from their respective classes to being accessible from the "SimServiceContext"
Where before there was:
-[SimDeviceType supportedDeviceTypesByAlias]
-[SimDeviceSet defaultSet]
+[SimRuntime supportedRuntimes]
There is now:
-[SimServiceContext supportedDeviceTypesByAlias]
-[SimServiceContext defaultDeviceSetWithError:]
-[SimServiceContext supportedRuntimes]
The class can be initialized with something like this:
[SimServiceContext<EMAIL_ADDRESS>error:nil]

xctool doesn't support building for Xcode 8 and later. Please, update to xcodebuild or other build tools. xctool will still support running tests.
0.3 release is pending approval and should be soon available via homebrew.

I have updated xctool to version 0.3.1 via homebrew, xcode 8.1 final
Currently, I cannot make the build with xctool, the terminal app said:

ERROR: Unexpected action: clean
[Info] Loading settings for scheme 'MyApp' ... (3675 ms)

=== BUILD ===
xcodebuild build MyApp
2016-12-10 23:02:05.132 xctool[44393:450979] *** Assertion failure in __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke(), /tmp/xctool-20161113-10169-11qccdv/xctool-0.3.1/Common/XCToolUtil.m:395
2016-12-10 23:02:05.136 xctool[44393:450979] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Got error while trying to deserialize event 'Build settings from command line:': The data is not in the correct format.'
*** First throw call stack:
(
0   CoreFoundation                      0x00007fff9b368452 __exceptionPreprocess + 178
1   libobjc.A.dylib                     0x00007fff8ca6d73c objc_exception_throw + 48
2   CoreFoundation                      0x00007fff9b36d12a +[NSException raise:format:arguments:] + 106
3   Foundation                          0x00007fff867351ee -[NSAssertionHandler handleFailureInFunction:file:lineNumber:description:] + 169
4   xctool                              0x00000001067bba9d __LaunchXcodebuildTaskAndFeedEventsToReporters_block_invoke + 436
5   xctool                              0x00000001067f9fed __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke + 165
6   xctool                              0x00000001067fa339 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke.26 + 679
7   xctool                              0x00000001067fa4a4 __ReadOutputsAndFeedOuputLinesToBlockOnQueue_block_invoke_2.49 + 188
8   libdispatch.dylib                   0x00007fff891a2c0b ___dispatch_operation_deliver_data_block_invoke + 118
9   libdispatch.dylib                   0x00007fff8918d93d _dispatch_call_block_and_release + 12
10  libdispatch.dylib                   0x00007fff8918240b _dispatch_client_callout + 8
11  libdispatch.dylib                   0x00007fff8918703b _dispatch_queue_drain + 754
12  libdispatch.dylib                   0x00007fff8918d707 _dispatch_queue_invoke + 549
13  libdispatch.dylib                   0x00007fff89187200 _dispatch_queue_drain + 1207
14  libdispatch.dylib                   0x00007fff8918d707 _dispatch_queue_invoke + 549
15  libdispatch.dylib                   0x00007fff89185d53 _dispatch_root_queue_drain + 538
16  libdispatch.dylib                   0x00007fff89185b00 _dispatch_worker_thread3 + 91
17  libsystem_pthread.dylib             0x00007fff9b7424de _pthread_wqthread + 1129
18  libsystem_pthread.dylib             0x00007fff9b740341 start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
./build.sh: line 27: 44393 Abort trap: 6           xctool -sdk "$sdk" -scheme "$scheme" -configuration "$configuration" OBJROOT="$PWD/build" SYMROOT="$PWD/build" ONLY_ACTIVE_ARCH=NO CODE_SIGN_IDENTITY="$identity"
warning: PackageApplication is deprecated, use xcodebuild -exportArchive instead.
error: Specified application doesn't exist or isn't a bundle directory
There is my command line : that worked well in xcode 7
./build.sh 'Release' '0.3.0' '1'
Script Build:
`#!/bin/bash
crashlytics_api_key=xxxxzzz
crashlytics_build_secret=xxxzzz
configuration='Release'
provision="MyApp_Ad_Hoc.mobileprovision"
identity="iPhone Distribution: Hai (9N7V3ZZZZ)"
sdk="iphoneos"
scheme="AirYes"
configuration=$1
version=$2
build=$3
output="$PWD/build/$scheme.$version.$build.$configuration.ipa"
PLIST_PATH="./MyApp/Application"
PLIST_FILE="Info.plist"
/usr/libexec/PlistBuddy -c "Set :CFBundleShortVersionString $version" "$PLIST_PATH/$PLIST_FILE"
/usr/libexec/PlistBuddy -c "Set :CFBundleVersion $version.$build" "$PLIST_PATH/$PLIST_FILE"
echo "Cleaning up old build..."
rm -Rf "$PWD/build/$configuration-$sdk"
echo "Building $scheme, using $configuration configuration, provisioning = $provision"
xctool -sdk "$sdk" -scheme "$scheme" -configuration "$configuration" clean OBJROOT="$PWD/build" SYMROOT="$PWD/build" ONLY_ACTIVE_ARCH=NO
xctool -sdk "$sdk" -scheme "$scheme" -configuration "$configuration" OBJROOT="$PWD/build" SYMROOT="$PWD/build" ONLY_ACTIVE_ARCH=NO CODE_SIGN_IDENTITY="$identity"
xcrun -sdk "$sdk" PackageApplication -v "$PWD/build/$configuration-$sdk/$scheme.app" -o "$PWD/build/$configuration-$sdk/$scheme.ipa" --embed "$provision"
cp "$PWD/build/$configuration-$sdk/$scheme.ipa" "$output"
echo "Uploading $output to Fabric.io..."
echo "./Crashlytics.framework/submit $crashlytics_api_key $crashlytics_build_secret -ipaPath ""$output"""
./Crashlytics.framework/submit $crashlytics_api_key $crashlytics_build_secret -ipaPath "$output"
`

xctool now supports only running tests. Replace in your script xctool with xcodebuild and should just work with Xcode 8.

Or even better xcodebuild + xcpretty for nicer output https://github.com/supermarin/xcpretty
Or use gym from fastlane if you want to build ipas. Or xcbuild.

@ExtremeMan  when I change xctool to xcodebuild - I have error "xcodebuild: error: invalid option '-reporter'"

@LavrL pipe to xctool for that

@fabb  any other solution ?

No

@LavrL oops, i meant xcpretty, not xctool.

Still met the same problem. Is this issue closed?

@guoyingtao yes
follow what @ExtremeMan said replacing xctool with xcodebuild


Max chars setting in in Layout doesn't work with DraftJS

Counter is not updated when you use this block with DraftJS inside and set max chars via DX Layout CPanel

Won't fix. DraftJS will be removed from Volto.


[SPARK-10402][DOCS][ML] Add defaults to the scaladoc for params in ml/

We should make sure the scaladoc for params includes their default values through the models in ml/

Merged build triggered.

Merged build started.

Test build #41982 has started for   PR 8591 at commit 8f49cf5.

Test build #41982 has finished for   PR 8591 at commit 8f49cf5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/41982/
Test PASSed.

Merged build triggered.

Merged build started.

Test build #42021 has started for   PR 8591 at commit 16c972e.

LGTM pending tests

Test build #42021 has finished for   PR 8591 at commit 16c972e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/42021/
Test PASSed.

Merged build finished. Test PASSed.

Merging with master and branch-1.5


Added a chunk of the report should be finalized in the next day

adding more writing now @noelpimentel


Add SZ likelihood to SOLikeT

This will add a likelihood for SZ analysis of stacked profiles.
In the main script, szlike.py, there are separate classes for three different models: kSZ and tSZ for the GNFW model, and the OBB model.
Note: The current set up is specific in places (e.g., two-halo term) to the CMASS galaxy sample as used in the ACT analysis, so some work on generalization will need to be done in the future.

@emilymmoser happy for you to mark as ready for review whenever you wish 👍


UnicodeDecodeError

Thanks for your great tool!
I wont need it, but maybe for future users somebody might want to catch this:
2024-03-08 17:51:59,082 [ERROR] UNCAUGHT EXCEPTION
Traceback (most recent call last):
  File "L:\Dropbox\ObsImported\wikidpad2markdown.py", line 421, in <module>
    RunMain()
  File "L:\Dropbox\ObsImported\wikidpad2markdown.py", line 348, in RunMain
    wiki_content = fh.read()
                   ^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 90: invalid start byte
Traceback (most recent call last):
  File "L:\Dropbox\ObsImported\wikidpad2markdown.py", line 421, in <module>
    RunMain()
  File "L:\Dropbox\ObsImported\wikidpad2markdown.py", line 348, in RunMain
    wiki_content = fh.read()
                   ^^^^^^^^^
  File "<frozen codecs>", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 90: invalid start byte

Workaround: Convert to the offending files to UTF-8,

Thank you @silidev for the bug report.
I will take a look in my next dev session.

I propose the following fixes (for non utf8 files)

Raise an error, if --strict (bonus: give a good hint on the offending line)
Convert with "replace" to utf8, then continue (bonus: write to log)

Yes, sounds great to me :)
Am So., 28. Juli 2024 um 21:00 Uhr schrieb Hartmut Leister <
@.***>:

I propose the following fixes (for non utf8 files)

Raise an error, if --strict (bonus: give a good hint on the
offending line)
Convert with "replace" to utf8, then continue (bonus: write to log)

—
Reply to this email directly, view it on GitHub
https://github.com/hardmooth/wikidpad2markdown/issues/6#issuecomment-2254611720,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AD2V77WE4TYV73U7STCYX2TZOU5VDAVCNFSM6AAAAABLJZQG4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGYYTCNZSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>


classification of neonatal epilepsy

These classes below are neonatal/infantile epilepsy disorders.

Label
MONDO ID
MONDO Label
Link to def (if not in Mondo)

Self-limited familial and non-familial neonatal seizures

https://www.epilepsydiagnosis.org/syndrome/self-limited-neonatal-overview.html

Self-limited familial and non-familial infantile seizures

https://www.epilepsydiagnosis.org/syndrome/benign-fam-nonfam-infantile-overview.html

Early myoclonic encephalopathy
MONDO_0016022
early myoclonic encephalopathy'

Ohtahara syndrome
MONDO_0000418
obsolete Ohtahara syndrome'

West syndrome
MONDO_0018097
West syndrome'

Dravet syndrome
MONDO_0011794
Dravet syndrome'

Myoclonic epilepsy in infancy
MONDO_0019486
myoclonic epilepsy of infancy

Epilepsy of infancy with migrating focal seizures

https://www.epilepsydiagnosis.org/syndrome/infancy-migrating-focal-overview.html

Myoclonic encephalopathy in non-progressive disorders

https://www.epilepsydiagnosis.org/syndrome/menpd-overview.html

Febrile Seizures plus, genetic epilepsy with febrile seizures plus

https://www.epilepsydiagnosis.org/syndrome/fbp-overview.html

Should I add the terms that are missing in MONDO?


Advanced templating

In some cases I need to render complex templates with values. Any objections to adding a 2nd CRD that allows values to be defined and the resource(s) to be a Helm template? I'm happy to do the work of adding it, just want to discuss the the feature and get a 👍.

I just noticed the Template CRDs spec.resourcesTemplate, which looks to do what I need. Closing.