text:
Skeleton for action

Description
Adds a Juju action named get-issued-certificates which outputs the certificates issued by the charm.
Fixes #9
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have bumped the version of the library
[ ] Check if possible change event.set_results({"result": msg}) to event.set_results({"app-1": data})

Sample output for the action:
ubuntu@ip-172-31-43-34:~/interview/self-signed-certificates-operator$ juju run self-signed-certificates/0 get-issued-certificates --format=json | jq
Running operation 11 with 1 task
  - task 12 on unit-self-signed-certificates-0

Waiting for task 12...
{
  "self-signed-certificates/0": {
    "id": "12",
    "results": {
      "result": "{\"traefik-k8s2-2\": {\"certificates\": \"[{\\\"certificate\\\": \\\"-----BEGIN CERTIFICATE-----\\\\nMIIDGDCCAgCgAwIBAgIUBqa5v1xfAR82/NHgwLQrf3RN+gowDQYJKoZIhvcNAQEL\\\\nBQAwOTELMAkGA1UEBhMCVVMxKjAoBgNVBAMMIXNlbGYtc2lnbmVkLWNlcnRpZmlj\\\\nYXRlcy1vcGVyYXRvcjAeFw0yMzA2MjkxNjM2MTJaFw0yNDA2MjgxNjM2MTJaMFMx\\\\nIjAgBgNVBAMMGWlwLTEwLTEtMC0xMi5lYzIuaW50ZXJuYWwxLTArBgNVBC0MJGRi\\\\nNWY5MmNhLTZjZWYtNGJjNS04YWZmLTkzMjUyYmY0ZmEwNjCCASIwDQYJKoZIhvcN\\\\nAQEBBQADggEPADCCAQoCggEBALyiCSF6tJPk4K9yXxPkkxWUD5q32Mg12HdKrwwG\\\\nK5leCPeOWasWir72zRdtRziKhDOwYDiOVpYGukgJQJKt/EMysb9OIoF9ho0BQuAn\\\\n2RqPQ3lxgozXPlaojRHwrTghCoMThrLuEVIUI2iYGNaHEGrzy194hFscNwiATCy/\\\\nOjQSA0ah3hDm/IbECg3/gOL1bsa8Cuou8CRCGHu7FdWrHnbcwBqG2KHY1iEf+2Kc\\\\nEvt4eUj22lRJ4UaQH/MlxEwhajrGPn+J6gs6vG5Uaz+zDxdC9A4zFnTzMQZt5IY5\\\\nyx61KIudzxNZSdyW4kHbhxWTKYy5QXvLsknMviTiHMBn7W8CAwEAATANBgkqhkiG\\\\n9w0BAQsFAAOCAQEABVOtMe2LFkjOIE+fMF9jrCUYSrf3Fo8L6wkFwhZYfF74D2KC\\\\n/ARSZLVd/sR7Gq9/WiOxd1NQP4LCTfp2mtk4W7RjTHf1HF4ZdMGPAnOcH9pXptXJ\\\\nRGPu3oPJszxaRObiC9MrcitASgWEX/KDAW4Js3vUOxyL/0Zkvh2hFwqX8OwRkOOZ\\\\n89B9oTF6G61AAKzsnvRhYuReo4wu2Vt92MznEQjU6zo1DE0LJmhWpbTajxvnuS3Q\\\\nPquobHYwf0cEEgCfzPebE60fGRt0LjzKrw2BB86kLjvGJ0VJvVxGrfEn3k7+i0oN\\\\n2oxjamAw8uXvwUjxS6pKrL7UPvCsRDaJHADZEQ==\\\\n-----END CERTIFICATE-----\\\", \\\"certificate_signing_request\\\": \\\"-----BEGIN CERTIFICATE REQUEST-----\\\\nMIICmDCCAYACAQAwUzEiMCAGA1UEAwwZaXAtMTAtMS0wLTEyLmVjMi5pbnRlcm5h\\\\nbDEtMCsGA1UELQwkZGI1ZjkyY2EtNmNlZi00YmM1LThhZmYtOTMyNTJiZjRmYTA2\\\\nMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvKIJIXq0k+Tgr3JfE+ST\\\\nFZQPmrfYyDXYd0qvDAYrmV4I945ZqxaKvvbNF21HOIqEM7BgOI5Wlga6SAlAkq38\\\\nQzKxv04igX2GjQFC4CfZGo9DeXGCjNc+VqiNEfCtOCEKgxOGsu4RUhQjaJgY1ocQ\\\\navPLX3iEWxw3CIBMLL86NBIDRqHeEOb8hsQKDf+A4vVuxrwK6i7wJEIYe7sV1ase\\\\ndtzAGobYodjWIR/7YpwS+3h5SPbaVEnhRpAf8yXETCFqOsY+f4nqCzq8blRrP7MP\\\\nF0L0DjMWdPMxBm3khjnLHrUoi53PE1lJ3JbiQduHFZMpjLlBe8uyScy+JOIcwGft\\\\nbwIDAQABoAAwDQYJKoZIhvcNAQELBQADggEBAIdcyqzp2Xx86DhfC7p3QwLr/9uA\\\\n7bwZ2HxYjHN/8Zds2ZxjIT9dwkwqiM6NnWM0zi9W5CMGIHFX2I3vyIiQyGLcQYvb\\\\no8AM85Qwh6mixAzvbz5COeS62MOV+FL63i9glTgbcfM1QD7ow0vJQ6oQ7DTnb5cY\\\\nnRXx/Mfc5OtoWLdlngubvpRjzXlatKA3rmY2ejFctbmpSsAygS/2A8u/TmVXTxwd\\\\nTBYDGJnzNYnTYQwTm+oFKub4ESD5Bh2GxHm+VPoLsIMuM/tuJRhusvHCop7sXC0C\\\\nf2TW+ImofXtAkTYkMsyW5P0xPflLhKlIwahTy8llqff6LRWgL8TBjsY4Z3U=\\\\n-----END CERTIFICATE REQUEST-----\\\", \\\"ca\\\": \\\"-----BEGIN CERTIFICATE-----\\\\nMIIDVzCCAj+gAwIBAgIUV8gF9UsXqqAyKvZbXiTWLCvASEswDQYJKoZIhvcNAQEL\\\\nBQAwOTELMAkGA1UEBhMCVVMxKjAoBgNVBAMMIXNlbGYtc2lnbmVkLWNlcnRpZmlj\\\\nYXRlcy1vcGVyYXRvcjAeFw0yMzA2MjkxNjE0MThaFw0yNDA2MjgxNjE0MThaMDkx\\\\nCzAJBgNVBAYTAlVTMSowKAYDVQQDDCFzZWxmLXNpZ25lZC1jZXJ0aWZpY2F0ZXMt\\\\nb3BlcmF0b3IwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCKQgBuN05o\\\\nnp9wxIB1ggRdvoTswGjy6xzv1O2MHulIUJY7lXqNn57j4lugMu+pE1zpubyFLoL4\\\\nnt6U+zYuqYgYuY2eX+z6RSqPFpe3H0PUwDPZkYSMY4dqONsOmnd9AZPaohWYOodX\\\\nNhG8g7RN3HfO8VLs6vG6I3stxSqg7Cr4Ex4943n2FX8rYYHfhma01Sgs7OV+12vT\\\\n4JBQeqECftGpQ7jAkNFoL75OW4zTWjJiZandqD05svLagax9zqWgbQTIKiAZSTCm\\\\n/d7GeduufVx5jye2oTvD0d/muRzByCz0BNT3c0CXwIW+pQDSjuHDsMt+boSd2/vi\\\\nVsEh/bzCh+17AgMBAAGjVzBVMB8GA1UdDgQYBBYEFJZ/yTjkDm5Yk0GCSMEApBAV\\\\n8fNtMCEGA1UdIwQaMBiAFgQUln/JOOQObliTQYJIwQCkEBXx820wDwYDVR0TAQH/\\\\nBAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAQEASh21nXuHBeJ2o10k2SkNo8RnE7kx\\\\nCNED+av236OqH2LTJL27jUD7VsTh86LsSJkAlXRv0vtuLMCFjnwM/2nu154tyWFA\\\\n5LsYm7RRAV48gHvvmSUzwLGb1eRrFc6/HX8Tpqll1Uep1I4z4m+8iqYpwRBHvXhC\\\\nAQNqUBD56IiAG1rWTgqEhAcbbxxZEtq++vy3pLkRDIEiq+oRiXoGuyYOZATJewV/\\\\nWVNivndsC7An16wavgNBZWKVNPKXxoLV7/y6A3LjdkDkTAqxuRpT9sYqpko9jI17\\\\nVpLSElzzKZLwHYnp4pkHo9GrXQLMKbh7LXR+MFZ7s2Wn+WJdLh8gj3j6Aw==\\\\n-----END CERTIFICATE-----\\\", \\\"chain\\\": [\\\"-----BEGIN CERTIFICATE-----\\\\nMIIDVzCCAj+gAwIBAgIUV8gF9UsXqqAyKvZbXiTWLCvASEswDQYJKoZIhvcNAQEL\\\\nBQAwOTELMAkGA1UEBhMCVVMxKjAoBgNVBAMMIXNlbGYtc2lnbmVkLWNlcnRpZmlj\\\\nYXRlcy1vcGVyYXRvcjAeFw0yMzA2MjkxNjE0MThaFw0yNDA2MjgxNjE0MThaMDkx\\\\nCzAJBgNVBAYTAlVTMSowKAYDVQQDDCFzZWxmLXNpZ25lZC1jZXJ0aWZpY2F0ZXMt\\\\nb3BlcmF0b3IwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCKQgBuN05o\\\\nnp9wxIB1ggRdvoTswGjy6xzv1O2MHulIUJY7lXqNn57j4lugMu+pE1zpubyFLoL4\\\\nnt6U+zYuqYgYuY2eX+z6RSqPFpe3H0PUwDPZkYSMY4dqONsOmnd9AZPaohWYOodX\\\\nNhG8g7RN3HfO8VLs6vG6I3stxSqg7Cr4Ex4943n2FX8rYYHfhma01Sgs7OV+12vT\\\\n4JBQeqECftGpQ7jAkNFoL75OW4zTWjJiZandqD05svLagax9zqWgbQTIKiAZSTCm\\\\n/d7GeduufVx5jye2oTvD0d/muRzByCz0BNT3c0CXwIW+pQDSjuHDsMt+boSd2/vi\\\\nVsEh/bzCh+17AgMBAAGjVzBVMB8GA1UdDgQYBBYEFJZ/yTjkDm5Yk0GCSMEApBAV\\\\n8fNtMCEGA1UdIwQaMBiAFgQUln/JOOQObliTQYJIwQCkEBXx820wDwYDVR0TAQH/\\\\nBAUwAwEB/zANBgkqhkiG9w0BAQsFAAOCAQEASh21nXuHBeJ2o10k2SkNo8RnE7kx\\\\nCNED+av236OqH2LTJL27jUD7VsTh86LsSJkAlXRv0vtuLMCFjnwM/2nu154tyWFA\\\\n5LsYm7RRAV48gHvvmSUzwLGb1eRrFc6/HX8Tpqll1Uep1I4z4m+8iqYpwRBHvXhC\\\\nAQNqUBD56IiAG1rWTgqEhAcbbxxZEtq++vy3pLkRDIEiq+oRiXoGuyYOZATJewV/\\\\nWVNivndsC7An16wavgNBZWKVNPKXxoLV7/y6A3LjdkDkTAqxuRpT9sYqpko9jI17\\\\nVpLSElzzKZLwHYnp4pkHo9GrXQLMKbh7LXR+MFZ7s2Wn+WJdLh8gj3j6Aw==\\\\n-----END CERTIFICATE-----\\\", \\\"-----BEGIN CERTIFICATE-----\\\\nMIIDGDCCAgCgAwIBAgIUBqa5v1xfAR82/NHgwLQrf3RN+gowDQYJKoZIhvcNAQEL\\\\nBQAwOTELMAkGA1UEBhMCVVMxKjAoBgNVBAMMIXNlbGYtc2lnbmVkLWNlcnRpZmlj\\\\nYXRlcy1vcGVyYXRvcjAeFw0yMzA2MjkxNjM2MTJaFw0yNDA2MjgxNjM2MTJaMFMx\\\\nIjAgBgNVBAMMGWlwLTEwLTEtMC0xMi5lYzIuaW50ZXJuYWwxLTArBgNVBC0MJGRi\\\\nNWY5MmNhLTZjZWYtNGJjNS04YWZmLTkzMjUyYmY0ZmEwNjCCASIwDQYJKoZIhvcN\\\\nAQEBBQADggEPADCCAQoCggEBALyiCSF6tJPk4K9yXxPkkxWUD5q32Mg12HdKrwwG\\\\nK5leCPeOWasWir72zRdtRziKhDOwYDiOVpYGukgJQJKt/EMysb9OIoF9ho0BQuAn\\\\n2RqPQ3lxgozXPlaojRHwrTghCoMThrLuEVIUI2iYGNaHEGrzy194hFscNwiATCy/\\\\nOjQSA0ah3hDm/IbECg3/gOL1bsa8Cuou8CRCGHu7FdWrHnbcwBqG2KHY1iEf+2Kc\\\\nEvt4eUj22lRJ4UaQH/MlxEwhajrGPn+J6gs6vG5Uaz+zDxdC9A4zFnTzMQZt5IY5\\\\nyx61KIudzxNZSdyW4kHbhxWTKYy5QXvLsknMviTiHMBn7W8CAwEAATANBgkqhkiG\\\\n9w0BAQsFAAOCAQEABVOtMe2LFkjOIE+fMF9jrCUYSrf3Fo8L6wkFwhZYfF74D2KC\\\\n/ARSZLVd/sR7Gq9/WiOxd1NQP4LCTfp2mtk4W7RjTHf1HF4ZdMGPAnOcH9pXptXJ\\\\nRGPu3oPJszxaRObiC9MrcitASgWEX/KDAW4Js3vUOxyL/0Zkvh2hFwqX8OwRkOOZ\\\\n89B9oTF6G61AAKzsnvRhYuReo4wu2Vt92MznEQjU6zo1DE0LJmhWpbTajxvnuS3Q\\\\nPquobHYwf0cEEgCfzPebE60fGRt0LjzKrw2BB86kLjvGJ0VJvVxGrfEn3k7+i0oN\\\\n2oxjamAw8uXvwUjxS6pKrL7UPvCsRDaJHADZEQ==\\\\n-----END CERTIFICATE-----\\\"], \\\"revoked\\\": true}]\"}}",
      "return-code": 0
    },
    "status": "completed",
    "timing": {
      "completed": "2023-06-29 17:51:18 +0000 UTC",
      "enqueued": "2023-06-29 17:51:18 +0000 UTC",
      "started": "2023-06-29 17:51:18 +0000 UTC"
    },
    "unit": "self-signed-certificates/0"
  }
}

Closing as this was implemented in https://github.com/canonical/self-signed-certificates-operator/pull/17

authors: gruyaume sanchezfdezjavier


text:
Pin juju terraform provider to 0.8.0

sunbeam-terraform fails with new versions of
juju terraform provider, see [1]. Pin the
version to 0.8.0 until [1] is fixed and released.
[1] juju/terraform-provider-juju#310

Depends on:

https://github.com/canonical/sunbeam-terraform/pull/8

source: gharchive/pull-request

repo: canonical/snap-openstack

license_type: permissive

license_source: github-api


text:
Building from source fails on M2 Pro

Python 3.9.16
I tried to build from source by running ./build-macos.sh
[ 23%] Building CXX object external/protobuf/cmake/CMakeFiles/libprotobuf.dir/__/src/google/protobuf/util/type_resolver_util.cc.o
[ 23%] Building CXX object external/protobuf/cmake/CMakeFiles/libprotobuf.dir/__/src/google/protobuf/wire_format.cc.o
[ 23%] Building CXX object external/protobuf/cmake/CMakeFiles/libprotobuf.dir/__/src/google/protobuf/wrappers.pb.cc.o
[ 23%] Linking CXX static library libprotobuf.a
[ 23%] Built target libprotobuf
make: *** [all] Error 2
Traceback (most recent call last):
  File "/Users/X/git/onnxruntime-silicon/onnxruntime/tools/ci_build/build.py", line 2812, in <module>
    sys.exit(main())
  File "/Users/X/git/onnxruntime-silicon/onnxruntime/tools/ci_build/build.py", line 2727, in main
    build_targets(args, cmake_path, build_dir, configs, num_parallel_jobs, args.target)
  File "/Users/X/git/onnxruntime-silicon/onnxruntime/tools/ci_build/build.py", line 1349, in build_targets
    run_subprocess(cmd_args, env=env)
  File "/Users/X/git/onnxruntime-silicon/onnxruntime/tools/ci_build/build.py", line 740, in run_subprocess
    return run(*args, cwd=cwd, capture_stdout=capture_stdout, shell=shell, env=my_env)
  File "/Users/X/git/onnxruntime-silicon/onnxruntime/tools/python/util/run.py", line 49, in run
    completed_process = subprocess.run(
  File "/opt/homebrew/Cellar/python@3.9/3.9.16/Frameworks/Python.framework/Versions/3.9/lib/python3.9/subprocess.py", line 528, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['/opt/homebrew/bin/cmake', '--build', '/Users/X/git/onnxruntime-silicon/onnxruntime/build/MacOS/Release', '--config', 'Release', '--', '-j8']' returned non-zero exit status 2.

see this https://github.com/microsoft/onnxruntime/issues/16230#issuecomment-1577252969

As @gauravphoenix already mentioned, the build error was because of the flatbuffers variables and should be fixed now in #9 . Tested on macOS Ventura 13.5.

Closing since it has been fixed.

source: gharchive/issue

authors: aqgasa cansik gauravphoenix

repo: cansik/onnxruntime-silicon

license: MIT


text:
List platform compatibility

I tried to install on Windows XP but it needs .NET 4.5, which is not available on XP.  Please list in the readme which OSes it's compatible with.

Fair request. Didn't think anyone still used XP :smile:

It's required to interface with old hardware, and IT doesn't allow it on the company network, so I'm using Syncthing over the internet to transfer files easily. :)

Fair enough!
Unfortunately .net 4.5 adds some rather useful stuff which I do rely on, so I'm afraid XP support isn't a possibility. Sorry!

That's fine; it would just be good to mention

I am not very familiar with the .net ecosystem. Does SyncTrayzor work with mono? mono is apparently supported on Windows XP.

No, only Microsoft .NET. Mono does not support the GUI framework I use.

authors: canton7 endolith hrj

license: mit

license_source: bigquery


text:
🛑 Koha is down

In 2702266, Koha (https://bibo.cantorgymnasium.de/) was down:

HTTP code: 502
Response time: 3433 ms

Resolved: Koha is back up in ac468b8 after 11 minutes.

repo: cantorgymnasium/status


text:
🛑 Webmin is down

In 249f8a1, Webmin (https://webmin.cantorgymnasium.de:10000/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Webmin is back up in 065915e after 33 minutes.


text:
🛑 Keycloak is down

In 3258d7a, Keycloak (https://id.cantorgymnasium.de/) was down:

HTTP code: 502
Response time: 589 ms

Resolved: Keycloak is back up in 09f154e after 17 minutes.


text:
请教下米家插件开发固件升级的问题

抱歉，看到你在米家sdk上提的issue，是关于固件升级的：
https://github.com/MiEcosystem/miot-plugin-sdk/issues/481
看到小米有UI导航，直接打开固件升级页面的，但是小米方面又说这个固件升级需要自己做，请问下你的固件升级是自己实现的吗？自己用RN调用小米的RN蓝牙框架写一个dfu的升级库吗？
请恕冒昧了，盼复！

蓝牙升级是要自己写的，自己另外写一个界面的，调用米家的蓝牙库

我可以给你一个demo,希望帮助你快速完成

太好了，能把demo发给我吗？
我的邮箱地址是：yiyeshu1015@vip.qq.com
非常感谢！

你好，我这边也需要自己完成OTA功能，能否请教几个问题？

authors: caojunhua dessmann dgutkai

repo: caojunhua/crashAlert


text:
Release new highland version

There have been a number of features / bugfixes that have landed on the 2.x branch since 2.3.0.
It would be useful to push a new release so we can make use of these changes.

Pinging @jeromew for this; he has npm publish access.

@jgrund @LewisJEllis I just came back online after a trip. I will bump a new version in a few hours

2.4.0 is published.

@jeromew @LewisJEllis Thanks!

/cc @ibash

Thanks!

authors: LewisJEllis ibash jeromew jgrund vqvu

repo: caolan/highland


text:
Mirror ORBOS docker image to docker hub

A nice thing to have as an external user would be to have the docker image somewhere available where there is no need for a docker login.
The readme states that you need to create a docker config secret to pull the boom image. It would be nice if this step would be obsolete.

closed in favor of githubs registry #318

authors: buehler fforootd

repo: caos/orbos


text:
Several crashes on Android reported by Crashlytics

Describe the bug
I'm getting many crashes reported by Firebase Crashlytics caused by some messaging dependency (com.google.firebase.iid.zzbe and com.getcapacitor.CapacitorFirebaseMessagingService) .
To Reproduce
I was not able to reproduce it consistently. The error happened more frequent in production.
Expected behavior
While I can handle some crashes here and there due to huge ecosystem Android has, I've had a very small number Crash-Free users on Android, 64%.
Screenshots
Link to gallery
SS 1
SS 2
SS 3
SS 4
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
Android devices. No pattern has been found in terms of OS Versions
Additional context
I'm also using some other capacitor-community plugins that may have some impact (@capacitor-community/admob, @capacitor-community/firebase-analytics, @capacitor-community/firebase-crashlytics, @capacitor-community/firebase-remote-config, @capacitor-community/media). I'll attach the complete plugin list below:
ionic info

Ionic:

   Ionic CLI                     : 6.12.0
   Ionic Framework               : @ionic/angular 5.3.4
   @angular-devkit/build-angular : 0.901.12
   @angular-devkit/schematics    : 9.1.12
   @angular/cli                  : 9.1.12
   @ionic/angular-toolkit        : 2.3.3

Capacitor:

   Capacitor CLI   : 2.4.2
   @capacitor/core : 2.4.2

Utility:

   cordova-res                          : not installed
   native-run (update available: 1.2.1) : 1.0.0

System:

   NodeJS : v14.6.0
   npm    : 6.14.8
   OS     : macOS Catalina

package.json
"dependencies": {
    "@angular/common": "^9.1.12",
    "@angular/core": "^9.1.12",
    "@angular/forms": "^9.1.12",
    "@angular/platform-browser": "^9.1.12",
    "@angular/platform-browser-dynamic": "^9.1.12",
    "@angular/router": "^9.1.12",
    "@capacitor-community/admob": "^1.2.0-0",
    "@capacitor-community/firebase-analytics": "^0.2.0",
    "@capacitor-community/firebase-crashlytics": "^0.3.0",
    "@capacitor-community/firebase-remote-config": "^0.1.3",
    "@capacitor-community/media": "^1.0.1",
    "@capacitor/android": "^2.4.0",
    "@capacitor/core": "^2.4.0",
    "@capacitor/ios": "^2.4.0",
    "@ionic-native/core": "^5.28.0",
    "@ionic-super-tabs/angular": "^7.0.8",
    "@ionic/angular": "^5.3.2",
    "@ionic/storage": "^2.3.0",
    "@ngx-translate/core": "^12.1.2",
    "@ngx-translate/http-loader": "^4.0.0",
    "cordova-sqlite-storage": "^5.0.1",
    "ngx-countup": "^7.3.3",
    "rxjs": "~6.5.1",
    "tslib": "^1.10.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^0.901.12",
    "@angular/cli": "^9.1.12",
    "@angular/compiler": "^9.1.12",
    "@angular/compiler-cli": "^9.1.12",
    "@angular/language-service": "^9.1.12",
    "@capacitor/cli": "^2.4.0",
    "@ionic/angular-toolkit": "^2.3.3",
    "@types/jasmine": "^3.5.14",
    "@types/jasminewd2": "~2.0.3",
    "@types/node": "^12.12.54",
    "codelyzer": "^5.1.2",
    "jasmine-core": "~3.5.0",
    "jasmine-spec-reporter": "~4.2.1",
    "karma": "^5.2.0",
    "karma-chrome-launcher": "~3.1.0",
    "karma-coverage-istanbul-reporter": "~2.1.0",
    "karma-jasmine": "~3.0.1",
    "karma-jasmine-html-reporter": "^1.4.2",
    "ts-node": "~8.3.0",
    "tslint": "^6.1.3",
    "typescript": "~3.8.3"
  }

That doesn't look like this plugin

@distante 's comment is right. Thit is not cause of AdMob Plugin. I will close this issue.

authors: distante masterbd rdlabo

repo: capacitor-community/admob


text:
hotfix: correct events for interstitial ads #40

fixes, relates and closes #40

@rdlabo can you please check that the Swift part is correctly done?

@rdlabo hi, can you please take a look?

Thank you for waiting, I got time. Swift has no problem. I will merge. Thanks.

authors: distante rdlabo


text:
bug: Simultaneous write operations broken on web and electron

Describe the bug
I'm working on a chat app. That means, that my app receives events asynchronously. For example such an event could be a new message.
It happens pretty often, that multiple messages are received at the same time, which means that the app tries to add multiple messages at the same time to the database. On Android that works perfectly fine. But on iOS web and electron it doesn't work as expected at all.
On iOS and web only one of the multiple messages are saved. The other datasets are discarded without any error.
On electron the following exception is thrown:

To Reproduce
The following code does not work as expected (on web and electron):
 async addDataToTestDB() {
    // Since I'm not using await here, these operations are called simultaneously.
    this.insertData('id1', 'Bob');
    this.insertData('id2', 'Lina');
    this.insertData('id3', 'Maria');
  }

  async insertData(id: string, name: string) {
    const dbConnection = await this.sqlite.openDB('test-db');
    const result = await dbConnection.run('REPLACE INTO test(id, name) VALUES(?,?)', [id, name]);

    // The following line is only necessary on web platform
    await this.sqlite.saveToStore('test-db');
  }

But if I actively take care that there are no simultaneous db queries, the bug does not appear.
 async addDataToTestDB() {
    await this.insertData('id1', 'Bob');
    await this.insertData('id2', 'Lina');
    await this.insertData('id3', 'Maria');
  }

Expected behavior
Simultaneous database write actions should work.
Desktop (please complete the following information):

OS: macOS 12.3.1
Browser: Safari
Version: 15.4

Demo code

clone repo: git@github.com:tobiasmuecksch/capacitor-sqlite-angular.git
test web: npm run start
test electron: npm run electron:start

Click buttons in this order (while looking at the js console):

"Create Tables"
"Insert some data"
"print select all to console"
"drop database"

@tobiasmuecksch you must do it with the await to make sure that the transaction is completed  or add them to a queue that you execute within the same transaction

@tobiasmuecksch when you insertion an item avoid to open each time the db test if it is open and if not open it that slow down the process

@tobiasmuecksch when you insertion an item avoid to open each time the db test if it is open and if not open it that slow down the process

@jepiqueau Thanks for the hint. In fact my openDB method checks if there already is a connection, and re-uses it.

@tobiasmuecksch you must do it with the await to make sure that the transaction is completed or add them to a queue that you execute within the same transaction

Hm. That's not how I'd expect a database to work. No database I have ever worked with, required the developer to take care of execution locks and/or queues.
As I already explained, data is added to the database as a reaction to asynchronous events which are triggered by the sever via web-socket. Therefore await does not have any effect inside an event callback.
If I understand you right, I have to implement a query-queue for the platforms web and electron.
But why doesn't the plugin implement a queue for these platforms under the hood? It would make the plugin way easier to use and make it act more like a real database.

@tobiasmuecksch can you test  executing this statement
PRAGMA journal_mode=WAL

after the db.open()
This must solve the issue

I just tried that, and the following exception occurred:
[Error] ERROR – Error: Uncaught (in promise): Execute: ExecuteSQL: ExecuteSQL: Execute: cannot change into wal mode from within a transaction

@tobiasmuecksch just do your execute command with transaction to false

Allright; I got rid of the exception with a little workaround.

Screenshot: Workaround Code

On line 89 I'm querying and printing the journal_mode to make sure that it really is applied. And it seems to be successfully changed.
But the problem of described in this issue is still there 😢

@tobiasmuecksch just do your execute command with transaction to false

Ah, you are right. I overlooked that there is a transaction parameter on this method. I changed my code accordingly. The problem is still the same :(

Screenshot corrected code

@jepiqueau I've done some research and found out that there is a wal2 mode.
Soruce: https://stackoverflow.com/a/54475279/1646019
I'm still testing it, but it seems to fix the issue.
If this really fixes the issue. Can you make it the default mode for all connections?

On android, setting the journal_mode to wal2 fails with this error:
ERROR Error: Uncaught (in promise): Error: Execute: unknown error: Queries cannot be performed using execSQL(), use query() instead.

On electron changing to wal2 does not fix the exception

@tobiasmuecksch
        await this.db.open();
        if (this.platform !== 'android') {
          await this.db.execute(`PRAGMA journal_mode=WAL;`,false);
        }

@jepiqueau as I already said, WAL does not fix the problem. Only WAL2 does fix this problem for ios and web. electron automatically sets WAL instead of WAL2. So I still need a solution for electron.
What do you think about, making wal2 the default pragma on iOS and web ?

@jepiqueau No need to hurry 😉
All right. I do understand. Since it's not possible to run simultaneous write operations anyways, what do you think about implementing a queue into the plugin? We could add a configuration variable with which developers can turn it off, if they want to.

@tobiasmuecksch @jepiqueau I stumbled upon the second error in this thread and I think this is still a unresolved bug, right?

I did some research, and if I understand https://github.com/mattn/go-sqlite3/issues/709#issuecomment-485295884 correctly, it could be that the plugin misinterprets the response of sqlite as an error, although no error has occurred.

Setting the PRAGMA throws, although it's not an actual error.

Yes this is still an issue. I circumvented it, by writing my own Queue in order to always execute SQL statements and queries in sequence instead of parallel.
I would advice you, to do the same.

@tobiasmuecksch could you share your que ingénieur implementation or make a PR to jeep-sqlite and @capacitor-community/sqlite electron so every developer can benefit from this.

@jepiqueau @tobiasmuecksch Queueing was the initial issue here. But you guys discusssed a second issue, which is a seperate bug:

I did some research, and if I understand https://github.com/mattn/go-sqlite3/issues/709#issuecomment-485295884 correctly, it could be that the plugin misinterprets the response of sqlite as an error, although no error has occurred.

When executing this sql, it throws an error, although no error has happened. This should be fixed independently of queueing.

@tobiasmuecksch if you update to @capacitor-community/sqlite@4.1.0-8 and upgrade in the electron folder of your app  sqlite3 to 5.1.0 it works fine with WAL2. You can have a look at test with Wal2 & readonly hope this help

@jepiqueau Thanks. I will test that and close the issue if the problem is fixed

@jepiqueau I'm still having the same issues :-(

@tobiasmuecksch you must provide me a repro app on github as i never experiences this problem

@tobiasmuecksch any progress on this? I am still waiting some code to reproduce the error

@jepiqueau I haven't had the time yet, to update the repro app. I will do that asap.

@jepiqueau I have updated the repro app to the latest version of sqlite3@5.1.2 and to @capacitor-community/sqlite@4.2.0.
Additionally I have added a statement to set the journal_mode to WAL2. The issue is still there.
(See changes regarding WAL2 here: https://github.com/tobiasmuecksch/capacitor-sqlite-angular/commit/37b44a761910f012deedb019f5718faab71c4df5#diff-f076088e0454292ba7d4c88f1eb19181a115deb2a35a4b265da42abf9344a7b6R137)
How to reproduce:

clone repo: git@github.com:tobiasmuecksch/capacitor-sqlite-angular.git
test electron: npm run electron:start

Click buttons in this order (while looking at the js console):

"Create Tables"
"Insert some data"
"print select all to console"
"drop database"

@tobiasmuecksch i test it it works fine for iOS, Android and Web but not for Electron. To make it working in Electron seems the you must put the transaction to false in the db.run

@tobiasmuecksch i think i may have find the reason but i cannot this this morning run electron:start both on Windows and MAC i got the following error : Error: Cannot find module 'node:fs/promises' and i have no glue of what it is. when i git clone your project last evening it was working fine and reproducing the error with Wal  in Electron. Now even if i re-clone it today i got always Error: Cannot find module 'node:fs/promises' . Any idea? I put a release 4.2.2-1 but i am enable to test it. Any idea about this. Can you upgrade to 4.2.2-1 on your side and tell me if it works

@jepiqueau thank you for your effort. I'm currently out of office. I will test it on Saturday, and let you know whether I'm experiencing the same issues. Maybe I can find a solution.

@tobiasmuecksch i update to "electron": "^15.5.7" and it is working back
in 4.2.2-1 i implement BEGIN CONCURRENT instead of BEGIN TRANSACTION  when the journal_mode start with wal. But i get a syntax error near CONCURRENT meaning that for me it has not be implemented in node sqlite3. On top of this when we change to wal2 instead of wal it does not work too the journal_mode return is delete. again it does not seem to be implemented. So i do not think i can do something for your case i spent a full day on it and i do not have a solution

@jepiqueau Thank you so much for your effort. According to this issue https://github.com/TryGhost/node-sqlite3/issues/408 this seems not to be implemented for sqlite3.
The author of the follow comment, recommends to switch to better-sqlite3. Are there any reasons, you decided to use sqlite3 instead of better-sqlite3?
https://github.com/TryGhost/node-sqlite3/issues/408#issuecomment-354013490

@tobiasmuecksch At the time in Electron i was using @journeyapps/sqlcipher to give the ability to encrypt the database which is based on sqlite3.  Finally i fall back to sqlite3 when developers had some problems to create a Windows executable.
In fact i look this morning at the Web part jeep-sqlite based on sql.js the mode Wal2 does not exist too. and when setting to mode WAL i got cannot start a transaction within a transaction if i do not keep the await in front of the db.run the only way to have it working with no await is to select transaction false.
Moving to better-sqlite3 could be feasible but it is quite a work and would necessary before starting to test in a simple case that it is working with the WAL mode or WAL2 mode.

Okay. I think we should add a warning to the readme for example that WAL/WAL2 is not officially supported by this plugin.
For now I'm thinking about a clean way to add a queue mechanism to this plugin. Can you imagine to add that to the plugin, or do you want to keep this out of the plugin?
I could make a proposal / merge request for that.

@tobiasmuecksch i want googling through a lot of docs this morning and i could not find a way. I will stop on this. For me the queing will make the the execution of each transaction one after other which is similar to what the async is doing.
In that case i do not really understand what the wal mode differs from the delete mode.
There is may be something that i do not understand .
if you develop a queue mechanism for the Electron part of this plugin and you have a PR ready with an example that i can test i will merge it but i will have to implement it in the jeep-sqlite plugin too.
For the time being i will stop working on this as it took me some day work. i am sorry to not have found solution for this

@jepiqueau All good. I completely understand that, and I'm thankful, that you tried to find a solution. As I said; I'd suggest to add a note about this on the readme, to prevent future duplicate issues.

@tobiasmuecksch finally i got it see the code in capacitor-sqlite-angular🤪😅

@jepiqueau I'm confused. Does that mean, the problem needs to be fixed by changing files in the electron project?

@tobiasmuecksch no  i change only the sqlite.service.ts and the package.json scripts to make them compatible mac and windows

@tobiasmuecksch in web and electron i run the dbConnection.run with transaction false and i encapsulates the  await PromiseAll with BEGIN TRANSACTION ... COMMIT TRANSACTION or ROLLBACK TRANSACTION

@tobiasmuecksch i also upgrade Electron to "electron": "^15.5.7" in Electron/package.json file

Okay, thank you for the information. I will try that too.

Sample code: https://github.com/jepiqueau/capacitor-sqlite-angular/blob/main/src/app/services/sqlite.service.ts#L103-L113

This should be in the documentation on the web version :)

authors: caiorsantanna jepiqueau mousepotato phal0r tobiasmuecksch

repo: capacitor-community/sqlite


text:
WIP: feat(): update to capacitor3

Android

[ ] Card verification
[ ] Card tokens
[ ] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[ ] Google Pay
[x] Apple Pay

iOS

[ ] Card verification
[ ] Card tokens
[ ] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[x] Google Pay
[ ] Apple Pay

Web

[ ] Card verification
[ ] Card tokens
[x] Source tokens
[ ] PII tokens
[ ] Account tokens
[ ] Payment Methods
[ ] Payment Intents
[ ] Setup Intents
[x] Google Pay
[x] Apple Pay

https://github.com/capacitor-community/stripe/compare/master...paystory-de:master

Amazing!

https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-0

Few issues still there on iOS:
Android build is fine.
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:41:102: cannot convert value of type 'Error?' to expected argument type 'String?'
                    callback.reject("unable to create payment method: " + err!.localizedDescription, err)
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:53:93: cannot convert value of type 'NSError?' to expected argument type 'String?'
                            callback.reject("payment failed: " + err!.localizedDescription, err)
❌  /Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/PKAuthViewDelegate.swift:79:93: cannot convert value of type 'Error?' to expected argument type 'String?'
                    callback.reject("unable to create token: " + err!.localizedDescription, err)

and
        call.error("Google Pay is not available on iOS")
             ^~~~~
             reject
/Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/StripePlugin.swift:668:33: warning: 'getSavedCall' is deprecated: renamed to 'savedCall(withID:)'
        if let c = self.bridge?.getSavedCall(ctx.callbackId) {
                                ^
/Users/vagrant/git/node_modules/@capacitor-community/stripe/ios/Plugin/StripePlugin.swift:668:33: note: use 'savedCall(withID:)' instead
        if let c = self.bridge?.getSavedCall(ctx.callbackId) {

@patrickbussmann Thanks for check working. I fixed and pre-released 3.0.0-1. This is still working.

https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-1

@rdlabo do we have documentation to follow?
ie
Vue
Angular

@donPuerto not yet. For the time being, I plan to spend my time on refactoring and feature checking.
But Capacitor 3 don't support IE, so this plugin don't support IE too. Thanks.

@rdlabo Thanks for the work mate. Yeah dump that IE :)

Secret key of Stripe is not public key. This plugin suggest input secret key to code. This is not recommended.
It seems that it will need to be remade into a completely new style in v3 support.

Secret key of Stripe is not public key. This plugin suggest input secret key to code. This is not recommended.
It seems that it will need to be remade into a completely new style in v3 support.

You mean removing the secret key?
Can we help you somehow with this new style?

@rdlabo
Hi team!
I think we should remove these classes and methods.
https://github.com/capacitor-community/stripe/blob/feat/v3/src/web.ts#L376-L430
https://github.com/capacitor-community/stripe/blob/feat/v3/src/web.ts#L319-L373
There using a Stripe secret key, but the key should not use on the frontend.
I think we should recreate it to follow the Stripe JavaScript SDK.
If you wanna try this, I can help you.

@patrickbussmann @hideokamoto YES. I will remove secret key and method of using this.
Currently this plugin can create payment alone. But will be change to have to using backend. The big role of the plugin will be to create a payment UI.
I will do the rough development, so I would appreciate it if you could help me with the tests and reviews.

I get no response from Google Pay.
 const { success, token } = (await stripePlugin.payWithGooglePay({
gets never resolved.

gets never resolved.

Because of missing upgrade: https://capacitorjs.com/docs/updating/plugins/3-0#android-request-codes
Lets give @rdlabo some time. Then we can start writing tests and then all people can start using this with Capv3.

@patrickbussmann @hideokamoto YES. I will remove secret key and method of using this.
Currently this plugin can create payment alone. But will be change to have to using backend. The big role of the plugin will be to create a payment UI.
I will do the rough development, so I would appreciate it if you could help me with the tests and reviews.

Do you have time to take a look into that issue?

@hideokamoto I created draft of web implements.
https://github.com/capacitor-community/stripe/pull/74/commits/d2b0d2199a0a88b0f988135f29248024b59fccae
Stripe's "Elements" is not useful for Plugin, so we should create Web Components like PaymentSheet in iOS & Android. Can you create with StencilJS?

YES!!!!

This is Android!!

Released: https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-2
Support only these method:

initialize
createPaymentSheet
presentPaymentSheet

ApplePay and GooglePay is included at PaymentSheet. So these method is removed.

Released: https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-2
Support only these method:

initialize
createPaymentSheet
presentPaymentSheet

ApplePay and GooglePay is included at PaymentSheet. So these method is removed.

README is here: https://github.com/capacitor-community/stripe/tree/feat/v3
Demo Implements is here: https://github.com/capacitor-community/stripe/tree/feat/v3/demo

 Stripe.addListener(PaymentSheetEventsEnum.Completed, (response) => {
      console.log('PaymentSheetEventsEnum.Completed', response);
    });

@danielehrhardt Thanks try and sorry missing. I fixed type and release at https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-3
If it is possible, please try again. Thanks.

@danielehrhardt Thanks try, and sorry mistake. I fixed type and release at https://github.com/capacitor-community/stripe/releases/tag/v3.0.0-3
If it is possible, please try again. Thanks.

To be on the safe side I added your case to the demo app so that the build process will fail when its an issue.
https://github.com/capacitor-community/stripe/pull/78

@danielehrhardt @patrickbussmann Thanks for try🙏
I will merge to master branch. Let's discuss Individual new issues!

authors: danielehrhardt donPuerto hideokamoto patrickbussmann rdlabo

repo: capacitor-community/stripe


text:
Product dashboard questions

Hi,
Thanks for support.
I have some questions here. Can you please help me here..

On product dashboard page, it displays data for commit, build, dev,qa, int, perf... prod.
Many time team deploys code in QA and Perf at the same time.
Also, some time they really skip deployment in INT environment..
how does product dash board behave in such cases.. or its always compulsory to follow sequence of   deployments.

Jenkin plugin push build and deployment data to Hygieia into build, artifact and environment_compontents collections.
Do we still need run any deployment collector?

thanks so much.

We are refactoring the pipeline to allow more flexible way to set up the stages and name them
With Jenkins push, you dont need collectors.

@anjana83 closed.

repo: capitalone/Hygieia


text:
Latest jira collector issue with story status

Hi i have an issue with the JIRA collector.
when querying  the mongodb for the sStatus and sState, all of the tickets are set to Backlog, even though the tickets/issues have other states.
Any idea?

@sjalee82  when is it last collected data

@sjalee82 : Please validate the data that you are getting from the JIRA API:

https:///rest/agile/1.0/board?name=
Get the board id from the response, and then use that to get the issue data using the API below

https:///rest/agile/1.0/board//issue
See what the statuses are on the response.
If there is a discrepancy, as nireeshT suggested, check your properties file as well.
This is what I had at a minimum when I tested it last time.

feature.pageSize=100
feature.cron=0 * * * * *
feature.queryFolder=jiraapi-queries
feature.storyQuery=story
feature.epicQuery=epic
feature.jiraProxyUrl=
feature.jiraProxyPort=
feature.jiraBaseUrl=
feature.jiraQueryEndpoint=rest/api/2/
feature.jiraCredentials=
feature.jiraIssueTypeNames=Story
feature.jiraSprintDataFieldName=customfield_10007
feature.jiraEpicIdFieldName=customfield_10003
feature.jiraStoryPointsFieldName=customfield_10004
feature.jiraTeamFieldName=customfield_11248
feature.jiraBoardAsTeam=true
feature.deltaStartDate=
feature.masterStartDate=
feature.deltaCollectorItemStartDate=

i get the same response from both rest queries
Below is my configruation:
feature.pageSize=1000
feature.cron=0 * * * * *
feature.queryFolder=jiraapi-queries
feature.storyQuery=story
feature.epicQuery=epic
feature.jiraProxyUrl=
feature.jiraProxyPort=
feature.jiraBaseUrl=
feature.jiraQueryEndpoint=rest/api/2/
feature.jiraCredentials=
feature.jiraIssueTypeNames=Task,Bug,Sub-task,Story,Spike,Production Support,New Feature,Improvement
feature.jiraSprintDataFieldName=customfield_10104
feature.jiraEpicIdFieldName=customfield_10100
feature.jiraStoryPointsFieldName=customfield_10106
feature.jiraTeamFieldName=#do not have Team
feature.jiraBoardAsTeam=false
feature.deltaStartDate=2018-03-01T00:00:00.000000
feature.masterStartDate=2018-01-01T00:00:00.000000
feature.deltaCollectorItemStartDate=2008-01-01T00:00:00.000000

Excerpt from MongoDB:
"_id" : ObjectId("5b2417b836d1a0000b7935d3"),
"_class" : "com.capitalone.dashboard.model.Feature",
"collectorId" : ObjectId("5b22889230c49e000c0a8cf1"),
"sId" : "10126",
"sNumber" : "DP-38",
"sName" : "deleted",
"sTypeId" : "10001",
"sTypeName" : "Story",
"sStatus" : "Backlog",
"sState" : "Backlog",
"sEstimate" : "5",
"sEstimateTime" : 0,
}
response from rest/api/latest/issue/DP-38
"expand": "renderedFields,names,schema,operations,editmeta,changelog,versionedRepresentations",
"id": "10126",
"self": "http://:8080/rest/api/latest/issue/10126",
"key": "DP-38",
"fields": {
"issuetype": {
"self": "http://:8080/rest/api/2/issuetype/10001",
"id": "10001",
"description": "Created by JIRA Software - do not edit or delete. Issue type for a user story.",
"iconUrl": "http://:8080/images/icons/issuetypes/story.svg",
"name": "Story",
"subtask": false
},
"updated": "2018-06-18T13:24:09.960+0000",
"status": {
"self": "http://:8080/rest/api/2/status/10101",
"description": "",
"iconUrl": "http://:8080/images/icons/statuses/generic.png",
"name": "In-Progress",
"id": "10101",
"statusCategory": {
"self": "http://10.145.94.133:8080/rest/api/2/statuscategory/4",
"id": 4,
"key": "indeterminate",
"colorName": "yellow",
"name": "In Progress"
}
},

@sjalee82: This could be a configuration issue in your properties file
Can you please call the api below, to get the story information for your board, and then in that response json, there is a section as below (from what I got last time I worked on it) that lists the field names. Make sure your properties file has the correct field name configuration. You will have to update the query parameters as needed.
https://{jira server domain name}/rest/agile/1.0/board/{board-id}/issue?jql=updatedDate%3E%3D'2016-03-01+00:00'+AND+issueType+IN+('Story')+ORDER+BY+updated+ASC&expand=schema,names&fields=*all,-comment,-watches,-worklog,-votes,-reporter,-creator,-attachment&maxResults=100&startAt=0
"names": {
"customfield_15521": "AE",
"customfield_15400": "Approvals",
"customfield_13100": "Time Scope Variability",
"customfield_17700": "Definition of Done",
"customfield_15522": "Bank Priority",
"customfield_15401": "Satisfaction",
"customfield_15520": "Requesting LOB",
"customfield_13101": "JSD EazyBI Account Name",
"customfield_15525": "Intent Lead",
"resolution": "Resolution",
"customfield_15526": "Overall Status",
"customfield_15402": "Satisfaction date",
"customfield_15523": "Complexity",
"customfield_15524": "Delivery Model",
"customfield_17701": "To Do",
"customfield_12800": "System Team Area",
"customfield_15518": "Operations Area Goal Alignment",
"customfield_15519": "Operations Imperatives",
"customfield_12802": "Customer Priority Justification (if Medium, High & Critical)",
"customfield_15516": "Key Initiative",
"customfield_12801": "Customer/LOB Priority",
"customfield_15517": "LOB Impacts",
"customfield_12804": "Sprint Requested",
"customfield_12803": "EASE WEB Environment (What Environment Does this Exist in?)",
"customfield_12806": "Additional Assignee #1",
"customfield_12805": "Feature mapping to Test Case",
"customfield_12808": "Resolution Area (Where was issue Resolved)",
"customfield_12807": "External Dependency",
"customfield_12809": "If External Resolve:  What External Team or Teams Owned & Resolved?",
"customfield_18100": "Target start",
"customfield_18101": "Target end",
"lastViewed": "Last Viewed",
"customfield_14300": "Squad",
"customfield_15510": "Estimated Benefit - Baseline",
"customfield_12000": "Software Cap Type",
"customfield_16600": "CSGE Resource Type",
"customfield_14301": "Impediment Reason",
"customfield_15511": "Estimated Benefit - Current",
"customfield_15514": "Milestone Delta",
"customfield_15515": "CR Type",
"customfield_15512": "Estimated Total Benefit ($)",
"labels": "Labels",
"customfield_15513": "Estimated Total Cost ($)",
"customfield_15507": "Current End Date",
"customfield_15508": "Current Start Date",
"customfield_15505": "Benefit Achievement Date Current",
"customfield_15506": "Current Due Date",
"aggregatetimeoriginalestimate": "Σ Original Estimate",
"customfield_15509": "RTG Date",
"issuelinks": "Linked Issues",
"assignee": "Assignee",
"components": "Component/s",
"customfield_17000": "Region",
"customfield_15500": "Benefit Categories",
"customfield_13200": "JSD PluginType",
"customfield_15504": "Benefit Achievement Date Baseline",
"customfield_15501": "Baseline Due Date",
"customfield_17800": "Feature Readiness",
"customfield_12227": "Volume",
"customfield_10600": "Rank",
"customfield_14405": "Requesting IT Director",
"subtasks": "Sub-Tasks",
"customfield_12220": "Date/Time ISO Lead Review",
"customfield_14400": "Software Cap Asset Name",
"customfield_12222": "Date/Time Approved",
"customfield_12101": "Release Name Introduced",
"customfield_12221": "Date/Time ISRM Review Complete",
"customfield_12100": "Application",
"customfield_14403": "Original Estimate",
"customfield_12224": "Point of Contact",
"customfield_14404": "Requesting Team Product Owner",
"customfield_12223": "Date/Time Retired",
"customfield_12102": "Scope",
"customfield_14401": "Requesting Team Name",
"customfield_12226": "Real Time",
"customfield_16701": "R&D Tax Credit Applicable",
"customfield_14402": "Accountable Executive/Stakeholder",
"customfield_12225": "Batch",
"customfield_16700": "Total SG's",
"customfield_11248": "Team",
"customfield_12219": "Date/Time Peer Review",
"progress": "Progress",
"issuetype": "Issue Type",
"customfield_17100": "Risk Resolution (ROAM)",
"project": "Project",
"customfield_13300": "JSD eazyBI Description",
"customfield_11000": "Feature Label",
"customfield_11001": "Testing Work Stream",
"customfield_11002": "Testing Cycle",
"customfield_13301": "Class of Service",
"customfield_17901": "Compliance",
"customfield_15600": "BAP CI",
"customfield_11246": "Customer Email Address",
"customfield_17900": "Legal",
"customfield_15601": "Policy",
"customfield_13303": "Current Efforts",
"customfield_12214": "ISRM Risk Manager",
"customfield_11237": "Is the product currently in market?",
"customfield_12206": "Peer Review Assignee",
"customfield_11238": "Product Lead",
"customfield_10700": "Customer Request Type",
"customfield_10701": "Request participants",
"customfield_10702": "Time to resolution",
"customfield_12209": "ISO Lead",
"resolutiondate": "Resolved",
"customfield_16000": "Incident Number",
"customfield_12561": "Process Instructions (3)",
"customfield_12560": "Process Instructions (2)",
"customfield_12200": "Project Status (RYG)",
"customfield_12202": "Forward to FAs",
"customfield_12201": "Kanban",
"customfield_12564": "LOB (Other)",
"customfield_12558": "Date/Time Customer",
"customfield_12557": "MS-Project ID",
"customfield_10810": "Priority Reason",
"customfield_11228": "Cost Center",
"customfield_12559": "Process Instructions (1)",
"customfield_10811": "Assigned PO",
"customfield_10812": "Assigned Team",
"customfield_10813": "LOE",
"customfield_10814": "Closed Reason",
"customfield_10815": "Blocked Reason",
"updated": "Updated",
"customfield_17201": "Supply Chain Manager",
"customfield_17200": "Category Manager",
"timeoriginalestimate": "Original Estimate",
"customfield_12550": "Gantt Options",
"customfield_17205": "Sourcing Intake Number",
"description": "Description",
"customfield_17204": "Contracting Intake Number",
"customfield_12552": "Baseline End",
"customfield_11220": "Feedback Rating",
"customfield_17203": "Contract Signatory",
"customfield_12551": "Baseline Start",
"customfield_17202": "Contract Manager",
"customfield_12554": "Baseline Effort",
"customfield_10012": "Release Version History",
"customfield_12553": "Date of Baselining",
"customfield_13400": "Software Testing",
"customfield_11224": "Is this story being copied from the "Engagement Stories" Project templates?",
"customfield_11103": "Requested By",
"customfield_12555": "Velocity %",
"customfield_11104": "Deliverable URL",
"timetracking": "Time Tracking",
"customfield_12547": "Actual End",
"customfield_10005": "Business Value",
"customfield_12304": "Lessons Learned",
"customfield_11216": "LOB (Unofficial)",
"customfield_10006": "Rank (Obsolete)",
"customfield_12549": "Latest End",
"customfield_10007": "Sprint",
"customfield_12548": "Latest Start",
"customfield_10800": "Feature",
"customfield_10801": "Found by",
"customfield_11219": "Type of Feedback",
"customfield_10802": "Date",
"customfield_10803": "Steps to Reproduce",
"customfield_10804": "Expected Results",
"customfield_10805": "Actual Results",
"customfield_10806": "Client Device",
"customfield_10807": "App Build Version",
"customfield_10808": "Environments",
"customfield_10809": "Impact/Severity",
"summary": "Summary",
"customfield_16101": "Business Functional Team",
"customfield_16100": "Use Case(s)",
"customfield_12541": "Target Production go-live date",
"customfield_10000": "[CHART] Time in Status",
"customfield_11210": "Peer Sign-off",
"customfield_12540": "Provide link to project workspace (KL, GitHub, OneDrive, etc)",
"customfield_16102": "Model Change Type",
"customfield_10001": "[CHART] Date of First Response",
"customfield_11211": "Cascading Select",
"customfield_12543": "Customer SME",
"customfield_11212": "TEST Field Type "Labels"",
"customfield_12542": "Date/Time AE Review Complete",
"customfield_10002": "Flagged",
"customfield_11213": "User Field",
"customfield_10003": "Epic/Theme",
"customfield_12544": "Application name",
"customfield_14600": "Gumbo PI Issues",
"customfield_10004": "Story Points",
"customfield_12536": "Data Elements",
"customfield_11204": "QA Completed On",
"customfield_12535": "Data Classification",
"customfield_11205": "Total Days Spent",
"customfield_12414": "Needs Enhancement",
"customfield_12538": "Where is application hosted?",
"customfield_11206": "End Date",
"environment": "Environment",
"customfield_15802": "Dependency Due Date",
"customfield_12537": "Third Parties Involved?",
"customfield_11207": "Testing Notes status",
"customfield_15803": "Theme",
"customfield_11208": "Link to play",
"customfield_12539": "Are there any high-risk transactions involved?",
"customfield_11209": "Frustration",
"duedate": "Due Date",
"customfield_15000": "Program Increment List",
"customfield_12530": "ASV Name",
"fixVersions": "Fix Version/s",
"customfield_12532": "ART PI",
"customfield_13500": "Engagement Level",
"customfield_12411": "ALM_Severity",
"customfield_11200": "Effort",
"customfield_15800": "Dependency Status",
"customfield_12410": "ALM_Sprint End Date Introduced",
"customfield_12531": "ART Name",
"customfield_11201": "Incorporated Version",
"customfield_15801": "Dependency Delivery Description",
"customfield_12534": "Internal or External facing?",
"customfield_11202": "Founder Sign-off",
"customfield_11203": "Morale",
"customfield_12404": "Program Increment",
"customfield_12403": "Epic Type",
"customfield_12406": "Workstream",
"customfield_12405": "Feature/Enabler",
"customfield_12408": "ALM_Application",
"customfield_10901": "Developer(s)",
"customfield_12407": "Planned Start",
"customfield_10902": "QA",
"customfield_12409": "ALM_Release Name Introduced",
"customfield_16200": "Start Date",
"customfield_16201": "Progress",
"customfield_12400": "Expected Remediation Date",
"priority": "Priority",
"customfield_12402": "Planned End",
"customfield_16206": "Risk probability",
"customfield_16205": "Risk consequence",
"customfield_15901": "Time to first response",
"customfield_12515": "Risk Issue Title",
"customfield_12518": "Risk Issue Type",
"timeestimate": "Remaining Estimate",
"versions": "Affects Version/s",
"customfield_12519": "Risk Issue Description:",
"status": "Status",
"customfield_15100": "TIR Updated?",
"customfield_11300": "Phase Found",
"customfield_15900": "Approvers",
"customfield_13601": "Incident Severity",
"customfield_13600": "Incident Type",
"customfield_12624": "CLI Project Key",
"customfield_11414": "Time in Status",
"customfield_11413": "Acknowledged Date",
"customfield_12502": "Targeted UATE migration date",
"customfield_12625": "Dependencies",
"aggregatetimeestimate": "Σ Remaining Estimate",
"customfield_16303": "Regulatory Impact",
"customfield_16302": "Global Finance Required",
"customfield_16301": "IT Required",
"customfield_16300": "Audit Driven",
"aggregateprogress": "Σ Progress",
"customfield_11531": "Date/Time Complete",
"customfield_11410": "System Impact: Secondary",
"customfield_11530": "Date/Time In Progress",
"customfield_14800": "Rank Number",
"customfield_11412": "System Impact: Additional",
"customfield_12501": "Targeted SITE migration date",
"customfield_12622": "Production Deployment Date",
"customfield_11411": "System Impact: Tertiary",
"customfield_12621": "EIDs Needing EazyBI access",
"customfield_11524": "Additional Stakeholders",
"customfield_11523": "Primary KPI",
"customfield_13701": "Parent Link",
"customfield_11526": "Division (ISRM)",
"customfield_11525": "Accountable Executive (AE)",
"customfield_11407": "VersionOne ID",
"customfield_11527": "Task Details",
"customfield_11406": "Is issue in VersionOne?",
"customfield_11409": "System Impact: Primary",
"customfield_11529": "ISRM POC",
"customfield_11408": "Prod Deploy Date",
"timespent": "Time Spent",
"customfield_15200": "Delivery Status",
"customfield_17500": "Release Train",
"aggregatetimespent": "Σ Time Spent",
"customfield_13700": "Team",
"customfield_11522": "URL",
"customfield_14902": "Primary CTQ",
"customfield_12602": "NIST Alignment",
"customfield_11634": "Impact",
"customfield_11633": "Date/Time Canceled",
"customfield_14900": "Portfolio Plan Name",
"customfield_12604": "Investment Estimate",
"customfield_11515": "Hypothesis",
"customfield_14901": "Sub-Portfolio Plan Name",
"customfield_12603": "Epic Owner",
"customfield_11635": "Next Steps",
"customfield_11514": "Problem Statement",
"customfield_11517": "Undesired Metrics",
"customfield_12606": "WSJF (Weighted Shortest Job First)",
"customfield_11516": "Secondary KPI",
"customfield_12605": "Funded",
"customfield_12608": "Expected Value",
"customfield_12607": "Additional Notes",
"customfield_11518": "Reporters",
"workratio": "Work Ratio",
"created": "Created",
"customfield_14100": "Exposure",
"customfield_16400": "Change Order",
"customfield_14101": "Potential Loss Avoided (PLA)",
"customfield_11630": "Risk Level",
"customfield_11632": "ISRM - Prime ID",
"customfield_12600": "Systems Impacted",
"customfield_11631": "Risk Response Rationale",
"customfield_11623": "Impediment Risk",
"customfield_11502": "eID",
"customfield_13800": "Flagged reason",
"customfield_12835": "All Tickets EM & TDM",
"customfield_11504": "JSD How much money and time saved?",
"customfield_11625": "LOB (Cyber)",
"customfield_11503": "JSD How many teams would use?",
"customfield_11506": "JSD Is LOB willing to pay?",
"customfield_11627": "Risk Issue Description",
"customfield_11626": "Risk ISRM Area",
"customfield_11505": "JSD Are there alternatives?",
"customfield_11508": "Category",
"customfield_11629": "Risk Issue Type",
"customfield_11507": "JSD Does JIRA Sponsor Support?",
"customfield_11628": "Risk Issue Title",
"customfield_11509": "On Behalf Of",
"customfield_15540": "Status Summary",
"customfield_15543": "Intent Requestor",
"customfield_13001": "EASE Web Tech Service Desk Request Type",
"customfield_13000": "Deploy/Toggle Type",
"customfield_17600": "Acceptance Criteria (AC):",
"customfield_15541": "Upcoming Milestones",
"customfield_15542": "Intent Approver",
"customfield_13002": "Design Skills",
"customfield_15545": "Owner",
"customfield_15303": "Requirement Status",
"customfield_15546": "Delivery Approver",
"customfield_11620": "Automation Status",
"customfield_12701": "Applicable Stakeholders",
"customfield_12822": "NIST Category",
"customfield_12700": "Project Category",
"customfield_15538": "Objectives",
"customfield_12824": "JSD Rename EazyBI account",
"customfield_15539": "Resolution Plan",
"customfield_12826": "Goals",
"customfield_12825": "JSD Group",
"customfield_12828": "Stage(s)",
"customfield_12827": "Required Resources (ORM)",
"customfield_11619": "Client/Device",
"customfield_12829": "Division ORM",
"customfield_18000": "Risk Impact Advisors",
"customfield_15532": "Strategic Alignment",
"customfield_16501": "Incident",
"customfield_15533": "Sub-Portfolio",
"customfield_16500": "Benefit Category",
"customfield_15530": "Service Impact",
"customfield_15531": "Sponsor",
"customfield_15536": "Impacts of Change",
"customfield_15537": "Key Accomplishments",
"customfield_12820": "Automation Closing Access ticket",
"customfield_15534": "Trend",
"customfield_15535": "Business Justification",
"customfield_10400": "Epic Link",
"customfield_15529": "Schedule",
"customfield_13900": "Service Type",
"customfield_12811": "System Team Comments",
"customfield_12810": "External Resolver Team Comments",
"customfield_15527": "Portfolio",
"customfield_13902": "Sub-LOB / Portfolios (CML TECH)",
"customfield_15528": "Resources",
"customfield_13901": "Acceptance Criteria",
"customfield_12812": "External Resolver Team Priority",
"customfield_12815": "System Team Priority",
"customfield_13904": "ValidatorBridge",
"customfield_13903": "ValidatorNameEID",
"customfield_12817": "Pending reason",
"customfield_13906": "Type Of Role",
"customfield_12816": "System Team Status/Resolution",
"customfield_13905": "ValidationSteps",
"customfield_12819": "EazyBI Role Request",
"customfield_13907": "AWS Account(s)",
"customfield_12818": "Reference"
}

@sjalee82 : Since we didn't hear back from you, I am assuming this issue is resolved at your end, and therefore closing this issue. Thanks !

Hi All,
I am new to this api and I have one issue in our project.
Currently, I am facing the issue for collecting all jira items for a specific project. Sometimes jira collectors are not able to collect all the data. I want to understand the three parameters here,
feature.deltaStartDate=2018-03-01T00:00:00.000000
feature.masterStartDate=2018-01-01T00:00:00.000000
feature.deltaCollectorItemStartDate=2008-01-01T00:00:00.000000
Also, how jira collectors collect data after any exception occurs in midway? Is it atomic?
Please help me to understand.
Thanks,
Sandip

authors: nireeshT sandipbhaumik sjalee82 subodhbattina


text:
CLI Enhancements

Freshly rebased so it’ll merge cleanly. This includes:

moving the vocabulary tool to a subcommand
moving the schema tool to a subcommand
moving the policy metrics tool to a subcommand
validation of multiple config files
tests for both new and old command-line functionality

For multiple config validation, you can just pass the filenames, but the -c will be accepted for backward compatibility. So these are equivalent:
custodian validate one.yaml two.yaml
custodian validate -c one.yaml two.yaml

Here are some examples from @scotwk of using the new schema sub-command.
custodian schema --summary

custodian schema --json

custodian schema
custodian schema ec2
custodian schema ec2.actions
custodian schema s3.filters.event

woot! excited.

Thanks @kapilt. I’ve addressed a few of your comments. @scotwk said he’d be able to look at the rest tonight.

thanks, i'm not going to have a chance for another review till tomorrow fwiw.

I think I've addressed everything except for moving policymetrics.py into a commands subpackage.  It wasn't clear from Kapil's comment if that was necessary, and it's something that can be done as a post-release refactor if the timing of this release is imminent.

happy to see this through to the finish line if it needs help. i'd like to get this merged.

lgtm, thanks

a couple of minors now apparent, tests are spewing to stdout/stderr, metrics.py should be folded into cli, and --json param on schema should probably be supressed since it doesn't play nice with selectors.

authors: kapilt scotwk skurfer

repo: capitalone/cloud-custodian


text:
adding docstrings to cfn.py

adding docstrings to cfn.py

the test here is extraneous, please remove.

docstrings & examples here have been checked for validity/confirmed functional

thanks, this still has the data files from the removed test that can also be removed.

authors: joshuaroot kapilt


text:
Fabric 1.18.1 Server Issues

Hello, I love this mod and works amazing on single player. However, on my server I get this error;
[03:22:15] [main/WARN]: Error loading class: net/minecraft/class_746 (java.lang.ClassNotFoundException: net/minecraft/class_746) [03:22:15] [main/WARN]: @Mixin target net.minecraft.class_746 was not found archeology.mixins.json:entity.ClientPlayerEntityMixin [03:22:20] [main/WARN]: @Inject(@At("INVOKE")) Shift.BY=3 on fabric-lifecycle-events-v1.mixins.json:server.WorldChunkMixin::handler$zef000$onLoadBlockEntity exceeds the maximum allowed value: 0. Increase the value of maxShiftBy to suppress this warning.
Hope this helps! I would love to get this on my server to play around with. By the way, great job!

Found what causes the crash, sorry for the inconvenience

authors: capsey jexline

repo: capsey/archeology-mod


text:
docker - export functionality all collections to a ZIP file

Hi, I'm using your provided docker solution and have one question about it.
It works when I execute an export but it creates a lot of separate .md files for each collection...
It would be great if you add an option to export all collections at once AS ZIP.
This way I'm able to import all collections with just one ZIP file.
is this something you can work on?
Now I need to import all .md files one for for, that's not very practical.
Thanks

Can't this be done with a simple wrapper script?
docker run ... /mnt/outliner-export
zip -qr /backups/outliner-$(date +"%y-%d-%m").zip /mnt/outliner-export


text:
feat(leadspace & button group): add print friendly styles

Related Ticket(s)
DDS Issue: https://github.com/carbon-design-system/carbon-for-ibm-dotcom/issues/7413
HC JIRA Ticket: https://jsw.ibm.com/browse/HC-2297
Description

This PR adds print-friendly styles for the Button Group and Leadspace components and variations based on the design specs (see below).

Lead space: https://ibm.ent.box.com/file/879963299367
Button group: https://ibm.ent.box.com/file/879964531443

Changelog
Changed

Add href prop to renderInner() event so that we can showcase the button href for print mode type and hide it on normal media types.

Expected designs

Testing

Visit the "Button group" and "Leadspace" components within the Storybook preview.
Inspect the page using Chrome DevTools and open the rendering tab.
Scroll down to the Emulate CSS Media Type and selected "Print"
From here you should be able to view the print style and compare it with the design specs to ensure the styling are looking as expected.

Thanks for this @proeung! This is looking good, the one issue I noticed is that the URL appears in parentheses when the CTA copy should end with a colon and then followed by the URL
Design specs

:
Current build

@RichKummer Looking at the current design specs, it looks to me like we're using both parentheses and colon (see attached), so if I'm understanding what you're saying above correctly, there should NOT be any parentheses, but a colon right next to the CTA text? Is that correct?

@RichKummer Looking at the current design specs, it looks to me like we're using both parentheses and colon (see attached), so if I'm understanding what you're saying above correctly, there should NOT be any parentheses, but a colon right next to the CTA text? Is that correct?

Yes, that's correct. The button should appear as CTA copy: url
Ex. Bring AI to your business: https://www.ibm.com/services/artificial-intelligence?lnk=hpmsc_bups)
I'll update the Design specs.

@RichKummer Thanks for verifying the correct treatment for the CTA print style. I just pushed up a commit that removes the parentheses and adds the colon.

I have read the DCO document and I hereby sign the DCO.

@annawen1 just checking if you accepted the DCO yet?

I have read the DCO document and I hereby sign the DCO.

authors: RichKummer annawen1 jeffchew proeung


text:
Data table website live demo, sandbox, link to React code, not working

Found problems with:

the live demo of Data Table , props/options don't work.
the sandbox
the React link redirects to Accordion. https://react.carbondesignsystem.com/?path=/story/datatable--with-selection

Question: How can developers see the effect of applying certain props, such as "tall" for the height of rows?

Hey @emyarod,
please add something like the following part to the sandbox, to get it running right from the start. Maybe as a separate file, to not obfuscate the initial JS file. I use this sandbox a lot and I always need to first paste this part. The DataTable is also an important component, so to see the broken sandbox is not a good experience for the Carbon design system.
      const rowData = [
        {
          id: 'a',
          name: 'Load Balancer 3',
          protocol: 'HTTP',
          port: 3000,
          rule: 'Round robin',
          attached_groups: 'Kevin’s VM Groups',
          status: 'Disabled',
        },
        {
          id: 'b',
          name: 'Load Balancer 1',
          protocol: 'HTTP',
          port: 443,
          rule: 'Round robin',
          attached_groups: 'Maureen’s VM Groups',
          status: 'Starting',
        },
        {
          id: 'c',
          name: 'Load Balancer 2',
          protocol: 'HTTP',
          port: 80,
          rule: 'DNS delegation',
          attached_groups: 'Andrew’s VM Groups',
          status: 'Active',
        },
        {
          id: 'd',
          name: 'Load Balancer 6',
          protocol: 'HTTP',
          port: 3000,
          rule: 'Round robin',
          attached_groups: 'Marc’s VM Groups',
          status: 'Disabled',
        },
        {
          id: 'e',
          name: 'Load Balancer 4',
          protocol: 'HTTP',
          port: 443,
          rule: 'Round robin',
          attached_groups: 'Mel’s VM Groups',
          status: 'Starting',
        },
        {
          id: 'f',
          name: 'Load Balancer 5',
          protocol: 'HTTP',
          port: 80,
          rule: 'DNS delegation',
          attached_groups: 'Ronja’s VM Groups',
          status: 'Active',
        },
      ];

      const headerData = [
        {
          key: 'name',
          header: 'Name',
        },
        {
          key: 'protocol',
          header: 'Protocol',
        },
        {
          key: 'port',
          header: 'Port',
        },
        {
          key: 'rule',
          header: 'Rule',
        },
        {
          key: 'attached_groups',
          header: 'Attached Groups',
        },
        {
          key: 'status',
          header: 'Status',
        },
      ];

(from: https://github.com/carbon-design-system/carbon/blob/master/packages/react/src/components/DataTable/stories/shared.js)

Maybe you can also fix the link to the react storybook to:
https://react.carbondesignsystem.com/?path=/story/datatable--usage
The current one is not available anymore, therefore it opens the Accordion

the first point was resolved by https://github.com/carbon-design-system/carbon-website/pull/1960 a few months ago, I will open a PR to address the second and third points

authors: ConradSchmidt andrea-gm emyarod

repo: carbon-design-system/carbon-website


text:
RemoveModal fixes

[x] buttons not spanning entire modal
[x] docs broken
[x] remove close icon

just as a reminder that a template with state management will always be necessary in stories for use for the mdx docs otherwise there's no way to trigger the modal


text:
fix: adds sort and filter functionality to add select columns

Contributes to #1752
adds the filter and sort functionality to multi select with hierarchy columns.

accomplishing this required a refactor of the items schema because previously there was no way (as far as i could tell) to support dynamically loading in sort and filter options. now the schema looks more like this
{
   "items":{
      "sortBy":[
         "title"
      ],
      "entries":[
         {
            "id":"1",
            "value":"folder 1",
            "title":"folder 1",
            "children":{
               "sortBy":[
                  "title",
                  "size"
               ],
               "filterBy":"fileType",
               "entries":[
                  {
                     "id":"1-1",
                     "value":"file1.pdf",
                     "title":"file1.pdf",
                     "fileType":"pdf",
                     "size":"100"
                  },
                  {
                     "id":"1-2",
                     "value":"index.js",
                     "title":"index.js",
                     "fileType":"js",
                     "size":"200"
                  },
                  {
                     "id":"1-3",
                     "value":"sitemap.xml",
                     "title":"sitemap.xml",
                     "fileType":"xml",
                     "size":"10"
                  }
               ]
            }
         },
         {
            "id":"2",
            "value":"folder 2",
            "title":"folder 2"
         }
      ]
   }
}

most notably is the change from items and children being just an array of items to being an object that contains additional props for sortBy and filterBy. now the items will live in an entries prop.
the soryBy prop represents an array of existing props that will be used as options for the sort dropdown. sortBy: ['title', 'size'], in this example title and size will be used to sort the items. note- there can be multiple attributes to sort by, which is why the value should be an array.
similarly, filterBy represents the prop that will be used to filter items. filterBy: 'fileType', in this example fileType will be used to filter items. as per the spec you can only use a single attribute to filter by, which is why this is not an array.
when there are no values for either sortBy or filterBy the filter and sort dropdown menus should not be present.

Seems that one of your tests is failing, maybe because of the change in the items schema that you mentioned.

@matthewgallo you're correct. thank you. fixed.

authors: davidmenendez matthewgallo


text:
[Locale Selector] Does not load in IE11

Detailed description

Describe in detail the issue you're having.

This was reported from URX. The locale selector loads as blank when in IE11. Test environment from their end:
https://wwwstage.ibm.com/account/reg/us-en/signup?formid=urx-19907
This was also reproducable on our nextjs ssr environment:

The issues appear to be missing polyfills for IE11:

What browser are you working in?

IE11

What version of the IBM.com Library are you using?

v1.4.0-rc.2
Steps to reproduce the issue

Go to http://ibmdotcom-nextjs-test.mybluemix.net/ in IE11
See locale selector button in the footer

This was an issue submitted by URX.  DDS dev provided a work around to turn off the Locale Selector for IE11.

authors: RobertaJHahn jeffchew

repo: carbon-design-system/ibm-dotcom-library


text:
fix(lightbox-media-viewer): fixed linting error

Related Ticket(s)
https://github.com/carbon-design-system/ibm-dotcom-library/issues/1985
Description
Fixes linting error within the lightbox-media-viewer.scss file

Deploy previews are broken currently, but this looks good and ci checks pass so will merge this in.


text:
fix(MegaMenu): explicity set focus to HeaderMenu L0 item when clicked

Related Ticket(s)
[MM] My IBM maintaining focus when switching to mega menu #3617
[HP] [MM] multiple menus open at once #3731
Description
The <OverflowMenu /> component that we are using for the profile menu has logic to trap the focus when user clicks outside of the component. This affects the megamenu when user opens the profile menu, then clicks on the L0 nav item. The focus is trapped in the <OverflowMenu /> which affects the onBlur event triggered used when opening another L0 nav item.
This PR forces focus on the L0 nav item when it is clicked.
BEFORE:

AFTER:

Changelog
Changed

force focus on the HeaderMenu L0 item

@annawen1 Looks good!
I'm thinking through this, and we are already set to go as-is with what we have currently tonight, so I'm thinking of having this retargeted to a release branch for a patch release instead, so let's hold on merging this for now.

@annawen1 one other thought I have, perhaps we can target master for now so we can test around this on canary, and if we do a patch we can always cherry pick this commit. Thoughts?

@annawen1 one other thought I have, perhaps we can target master for now so we can test around this on canary, and if we do a patch we can always cherry pick this commit. Thoughts?

@jeffchew yeah sure that works


text:
🛑 mainnet - API is down

In ae3644e, mainnet - API (https://api.beta.explorer.cardano.org/api/v1/epochs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mainnet - API is back up in fd3b953 after .

repo: cardano-foundation/cf-explorer-status


text:
Fix issue with deserializing card that has cycle in linksTo

This issue came down to not handling relative URL’s correctly in our identity context, as well as not detecting cycles in our unsubscribe logic.

argh, the CI test failure revealed deeper changes that need to be made... working on it...

repo: cardstack/boxel


text:
[ERROR] carla compiled version 0.9.3

After I started the simulator, I got the following error:
LogShaders: Error: The global shader cache file data/carla_093-compiled/Engine/GlobalShaderCache-GLSL_150.bin is missing
xxxxxxx
Your application is built to load COOKED content No COOKED content was found his usually means you did not cook content for this build.
xxxxxxx
Exiting abnormally (error code: 1)
It seems that the content files is not in the correct directory, but after I put the content files in Content/carla, it can not work yet.
My system version is Ubuntu 16.04 in a docker container. The 0.9.1 compiled version can be successfully started in the container.
@nsubiron

Following the installation instructions at Running in a Docker and doing
docker pull carlasim/carla:0.9.3
docker run -p 2000-2001:2000-2001 --runtime=nvidia carlasim/carla:0.9.3

works for me

@nsubiron I extracted the CARLA_0.9.4.tar.gz file and ran the sh file directly on an Ubuntu 18.04 machine(no Docker) with Tesla K80 and OpenGL 3, like this:
./CarlaUE4.sh -opengl3
But it gives below error:
[2019.03.12-02.37.21:730][  0]LogShaders: Error: The global shader cache file '/content/Engine/GlobalShaderCache-GLSL_150.bin' is missing.```
Your application is built to load COOKED content. No COOKED content was found; This usually means you did not cook content for this build.
It also may indicate missing cooked data for a shader platform(e.g., OpenGL under Windows): Make sure your platform's packaging settings include this Targeted RHI.
Alternatively build and run the UNCOOKED version instead.

Here's the full log:
[log.txt](https://github.com/carla-simulator/carla/files/2955047/log.txt)

Any help is appreciated!

I find that the cache file /Engine/GlobalShaderCache-GLSL_150.bin is missing, but there is a cache file of "/Engine/GlobalShaderCache-GLSL_430.bin". I wonder that is this bug related to the version of OpenGL?
@nsubiron

I tried run the carla 0.9.4 compiled version on my local pc with OpenGL version 4.3, it works.
So I guess this bug is because the 0.9.4 compiled version is compiled under OpenGL 4.3 ?
Maybe you should try compiled the code under OpenGL 3.0?

I tried run the carla 0.9.4 compiled version on my local pc with OpenGL version 4.3, it works.
So I guess this bug is because the 0.9.4 compiled version is compiled under OpenGL 4.3 ?
Maybe you should try compiled the code under OpenGL 3.0?

That's exactly what I was wondering, but wanted some kind of confirmation. I think I'll have to compile for 3.0 and rerun. Will post any updates, thanks!

I tried run the carla 0.9.4 compiled version on my local pc with OpenGL version 4.3, it works.
So I guess this bug is because the 0.9.4 compiled version is compiled under OpenGL 4.3 ?
Maybe you should try compiled the code under OpenGL 3.0?

Hey I read the build instructions but don't know where to pass the -opengl3 flag, it is not mentioned in the instructions: How to build on Linux.
I don't want to launch the project in Unreal editor, just want the binaries generated by "make package" command but where do I say its for -opengl3?

May be it is not related to OpenGL version only.
I've build Carla from master-release on Windows 10. The error (with the cache file GlobalShaderCache-PCD3D_SM5.bin) appears with "Shipping" and "Development"  configurations.  Though it runs fine with "Development editor" or "Debug-editor configuration.

run with opengl4

I am also seeing this issue when running with the -opengl3 flag, in a Linux VM/Mac OS host (I cannot run OpenGL 4 in this configuration), using the tar.gz bundle, release 0.9.9.

authors: Johnnyswong JunningHuang MaxHBor aayushARM delenius jediofgever nsubiron

repo: carla-simulator/carla


text:
Failed to connect Carla server from a remote machine

Hi all,
I run the Carla server on a Windows PC and tries to connect a client running on a Linux remote machine.
Both machines are in the same network (using VPN). After running a server on port 2000, I can connect a client to host_address:2000 via telnet host_address 2000 for a quick check. However, when I try a simple Carla script to get_world from the Carla client, I keep reporting time-out message: cannot connect to the server. Here is that script:
import carla
client=carla.Client(settings._HOST,settings._PORT)
client.set_timeout(10)
world = client.get_world()
Error message: RuntimeError: time-out of 10000ms while waiting for the simulator, make sure the simulator is ready and connected to host_address:2000
One thing I notice, the host machine does receive the message from the client during that 10 seconds, but the connection has not been successfully established:
.
FYI, the client's machine is actually an nvidia-docker container. I cannot set up the UnrealEngine on the client's machine since it couldn't display and render GUI. But the client machine only needs to connect to Carla environment on my host server and train the agent without rendering any images. It should be able to run PythonAPI without any problem, I assume.
Could you please advise?
Thank you
Here are my system specifications:
Carla version: 0.9.8, note that I use a pre-built Carla by following "Quick installation" document,
Server's machine: Windows 10,
Client's machine: Ubuntu 16.04.

@StevePhan97 how are you running the docker container? Please, provide more information.

@germanros1987 Hi, I have solved the issue. Thanks anyway.

Hi @StevePhan101, I ‘m suffered the same issue, how did you solve this?

Any solution to this?

Any solution to this?

Any solution to this?


text:
TypeError: unsupported operand type(s) for *: 'int' and 'ENUCoordinate' when toggle RSS visualization

Run Carla 0.9.11_RSS
Run manual_control_rss.py
In game window press F2

OBSERVED in logs:
Destroyed RSS sensor
File "/mnt/old/home/alexey/Downloads/CARLA_0.9.11_RSS/PythonAPI/examples/rss/rss_sensor.py", line 412, in _on_rss_response
self.debug_visualizer.tick(self.route, not response.proper_response.isSafe,
File "/mnt/old/home/alexey/Downloads/CARLA_0.9.11_RSS/PythonAPI/examples/rss/rss_visualization.py", line 621, in tick
self.visualize_route(dangerous, route)
File "/mnt/old/home/alexey/Downloads/CARLA_0.9.11_RSS/PythonAPI/examples/rss/rss_visualization.py", line 648, in visualize_route
self.visualize_enu_edge(edge, color, self._player.get_location().z)
File "/mnt/old/home/alexey/Downloads/CARLA_0.9.11_RSS/PythonAPI/examples/rss/rss_visualization.py", line 663, in visualize_enu_edge
carla_point = carla.Location(x=float(point.x), y=float(-1 * point.y), z=float(point.z + z_offset))
TypeError: unsupported operand type(s) for *: 'int' and 'ENUCoordinate'
EXPECTED:  Visualization enabled
ENVIRONMENT:

Carla 0.9.11_RSS
Ubuntu 20.04
Python 3.8.5

Looks like I manager to overcome this issue by changing:
carla_point = carla.Location(x=float(point.x), y=float(-1 * point.y), z=float(point.z + z_offset))

to
carla_point = carla.Location(x=float(point.x), y=float(-1 * float(point.y)), z=float(point.z + z_offset))

in def visualize_enu_edge(self, edge, color, z_offset): of rss_visualization.py..
However I am still not able to get those colored lines between ego and object as it was shown in demo.

@fpasch could you follow up on this please?

This is not fixed yet! I have the same issue.


text:
🛑 SUAP is down

In d9e7de7, SUAP (https://suap.ifms.edu.br) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SUAP is back up in aec8f3e after 11 minutes.

repo: carlitos-ifms/uptime


text:
I don't understand the purpose of the library

I feel stupid, but even after reading the docs several times with a few weeks between to digest it , I still don't understand the raison d’être of the crate.
I've used it it a couple of times to prepare a Vec<u8> packet with a couple of u16's, u32's etc to be later sent to some device, using it just as a sort of in-memory writer that takes care of advancing the pointer to Vec and handling endianness correctly. But I feel like I'm misusing the library. I don't understand when does the underlying storage grow automatically and when not and why. I don't understand the purpose of multiple handles to one underlying storage. The naming confuses me, starting with "A utility library for working with bytes." - does "working with bytes" really explain the purpose of the crate the best?
I don't want to be negative, I'm sure the crate is very useful for it's purpose and maybe even I need it today, but I just don't get it. I would really appreciate a typical scenario or two involving the core features of the crate playing together. Splitting "Hello, world" into two "Bytes" doesn't do that for me.

A potentially relevant line from the documentation:

Bytes values facilitate zero-copy network programming by allowing multiple Bytes objects to point to the same underlying memory. This is managed by using a reference count to track when the memory is no longer needed and can be freed.

@dvtomas does the above snippet help clarify things? Do you understand the value of zero-copy network programming or is that where the disconnect lies?

Dear @hawkw ,
no, not really, I've read the above snippet before. I'll try to elaborate on what I fail to understand in more detail.
The snippet says that the crate helps us (allows us?) to do zero-copy network programming without further explaining WHAT exactly it enables me to do and HOW should I use it. I understand that perhaps each library user might have specific needs, but I still suspect that there are some typical exemplary usages of the library. Unfortunately, the documentation is totally silent on them, so from here on I can only guess :(

I suspect that the library allows me to do zero-cost parsing of data that have arrived, is that correct? I currently use the library for something like that, but I'd be happy with just a buffer(&[u8]), sliding pointer to the buffer, and a bunch of get_i32 and similar methods. Clearly the library offers much more (different implementations of buffer and the mythical "multiple bytes object pointing to the same memory"), so I'm missing something here.

I suspect that the library allows me to do zero cost generation of binary packets to be sent somewhere, is that correct? But again, most of the stuff from 1. applies here as well, in the end I need a &[u8] buffer of data to send (Writer.write()) somewhere. Right now I'm generating them with just buf.put_i32 et al. methods. I'm even more lost here, because some underlying storages automatically grow and some not, and I totally don't understand which do, which not, when is it better to choose the auto-growing ones and when the static, and most importantly - WHY? What is the intuition behind some growing and some not? Another thing: I'm having trouble implementing the following scenario: I'm generating packets with this structure: [Len Len Len Len MessageCode ..... Len bytes .... CSum CSum]. I only know the len after generating the bytes, but in order to generate the binary representation with Bytes I need to fill it before generating the rest. Currently I do this by creating the underlying storage first, then converting it to Bytes, generate dummy zero Len bytes, then generate the data, convert it back to the storage (Vec) and ultimately modify the len bytes in the Vec inplace. Is this the idiomatic use of Bytes or should I use another approach, perhaps Chaining the data or something? I dunno, there is no such recipe on this anywhere in the docs...

So, these are the two use cases I commonly deal with, and none of them involves "multiple Bytes objects to point to the same underlying memory", different types of underlying storage, growable/non-growable bufs or any other more fancy stuff the crate provides. I still have no idea at all on how these concepts are supposed to be used, how do they work together, and the docs don't help. I have a gut feeling that I'm missing something useful, I just don't know how to reach for it and what exactly to look for, and that's a little  frustrating. Perhaps the crate implements some design pattern I don't know and others do, so they immediately recognize it and just know how to use the crate and what to expect from it? I don't know, but if that is the case, please, at least point me to the relevant document. Maybe it's just that my use-cases aren't a good fit for the crate, or that they are perfectly happy with just a small subset of the crate. Even if that was the case, I'm still curious about the "grownup" uses of the crate.
Hope I've made myself more clear. Thank you for reading this.

After further thinking, I have to admit that I don't have experience with zero-copy network programming. If the case with Bytes is that it is not useful outside the zero-copy network programming domain, perhaps I'm barking at the wrong tree and just misusing the library, and people experienced with zero-copy network programming immediately recognize the patterns employed in the crate and feel comfortable understanding and using it. I can't tell for lack of knowledge. If that is indeed the case, I apologize for this issue.

Working with &[u8] introduces lifetimes. Bytes uses reference counting. If working with slices is sufficient, then you should just use that.
Anyway, I don't really see any action items to take away from this issue. So, I will close it. Thanks for the report though.

authors: carllerche dvtomas hawkw

repo: carllerche/bytes


text:
Create a CloudFormation installation option.

It would be great to make a web-only - you could publish a pre-signed "requester pays" S3 URL to a cloud formation template, and the cloud formation template would load the Lambda function code from a "requester pays" bucket. You need to use Mappings so that a bucket in the same region as the stack is being created in is used as the Lambda function source.  See my attached sample template for an example of this.
think-perform-waste-analysis-apigateway-V1-stack.template.txt
With any luck you should be able to use the following presigned requester pays URL in cloud formation to try this out:
https://au-com-thinkronicity-opencode-apne1.s3-ap-northeast-1.amazonaws.com/think-perform-waste-analysis-apigateway-V1-stack.template?AWSAccessKeyId=ASIAIOS4QBXNGP2P7J4A&Expires=1456536663&Signature=2A%2BByLVAqy1%2FSBGItXVwr9cAW6g%3D&x-amz-request-payer=requester&x-amz-security-token=AQoDYXdzEJr%2F%2F%2F%2F%2F%2F%2F%2F%2F%2FwEawAIXPK1yZCBttmz16XicQ5%2F%2BbXatKq2GIZjsdITeElLmEap56Ue1Q%2FsZi8Q%2FB7QVagKie6ya4f1mngorzN7dCl1%2FiLLbmVEddm0H1zKNm0OrD6FlCyOVLzvogkwsy8oZv8UQTDDT6KIb0fcKx2hvQnYhYG8EM8oQPMqo8piwCLJe1wWG3lp%2F6%2FzGZukLQcS9CbCOqU7QbgmvI7k1GwAN8fTu%2FsK1ISOAu6hWQsesi9wJ27iKtgLhKLOBLdf5OKynQw9vvStCycBPZzuLOQ34qxAJDrcW1qmHJTwDhQ5zqEsrKqLxuoWVk%2BQf8eOojyUdVKLgPeRunmRW6dK2Awp6qs1tz9k9lVV4ojbalW6E%2BaUfTXracOcMTW9PkJI2p56idASYv3Yv0%2BjXwiD1OCOw61llgBQt9dUZ4l77VIFkwrJWfiDF3MO2BQ%3D%3D

Bu webobly you mean the installation? Not a bad Idea at all. I'll see what I can do :)

Console deploys are supported from version 1.2.0. In fact, they have completely replaced the previous installation scripts.

authors: carlnordenfelt imhogan


text:
Unable to load Quantized models

GGML_ASSERT: /private/var/folders/q9/ms4_8l4970q525dlsjp_b9n0x6l4j9/T/pip-install-jqga24o3/whisper-cpp-python_e0149178a136485cadb677b46e61e602/vendor/whisper.cpp/ggml.c:4288: wtype != GGML_TYPE_COUNT

Facing Above Exception When loading Quantized Whisper Model
Python Version : Python 3.9.6
whisper_cpp_python version : 0.2.0
Macbook M1 Pro
Model used : https://huggingface.co/ggerganov/whisper.cpp/blob/main/ggml-tiny-q5_1.bin
Kindly help me with this ..

Because it use old whisper.cpp without support Quantized models.
You need compile new whisper.cpp libs by youself

@magicse , what would happen if repo would point vendor folder to latest whisper.cpp version?

This is whisper_cpp.py for new model
whisper_cpp.zip

authors: kishorekaruppusamy magicse slavanorm

repo: carloscdias/whisper-cpp-python


text:
Specifying type: infra with Infra-Nodes for other roles adds all in the load balancer

Describe the bug
Using type: infra in a cluster that have Infra-Nodes that are dedicated for another application like OpenShift Data Foundation, includes those nodes together in the balancer even though they don't have routers running.

If you have in your cluster Infra-Nodes for different roles (for example Infra-nodes dedicated for OpenShift Data Foundation), don't use type: "infra" config as the Load Balancer will point to all nodes with that label. Instead use the nodelabels: syntax as below specifying the correct labels for the nodes that have the routers/ingress controllers. The listed labels follow an "AND" rule.

repo: carlosedp/lbconfig-operator


text:
🛑 API is down

In faaf750, API (https://api.pinbus.com) was down:

HTTP code: 502
Response time: 396 ms

Resolved: API is back up in d05d0df after 12 minutes.

repo: carlosmathiasen/pinbus-status


text:
Updated Calling Cards to be Broken Down by Prestige

Hi! I made quite a few changes with this request:

Created Categories for each Prestige "Prestige 1 through to Prestige 25"
Renamed and categorized existing Category "Prestige" as Prestige 1 - 5 Calling Cards to match as is on the Game
Renamed 2 operator challenges (symbolic end and chattering soldier) as the original challenges were renamed to vengeful stance and symbolic end. Also, updated png names to match, so these will need updating on online storage.
Updated prestige.js to have all categories of calling cards up to current season.
Updated US languages to have all Prestige Categories, Labels and Descriptions as appropriate. (Other regions will need to be actioned by another contributor)

Verified Build Runs as expected. (Search / Filter etc).
Still need to add images for new challenges. Will work on those tomorrow.

@carlssonemil - Hey i actually dropped you an email from my private email earlier. Thought I would go a step ahead and just do the work - let me know if you want to discuss before merge. I suggest waiting until I upload all the new calling card images as well.

repo: carlssonemil/orion


text:
Daily connection issue

Hi,
I have to reset my JIRA password every day in order to get the JIRA StopWatch (v2.0.1) app to connect to my JIRA cloud instance.  I don't have to change the password, just reenter it into JIRA. So daily what I do to get the system working is:

Log in to JIRA cloud.
Launch JIRA StopWatch. This shows a status of 'Not connected'
Browse to my JIRA profile, select change password, enter the current password, enter the current password as my new password (i.e. do not change the password).
Select the JIRA StopWatch configure cog to open the settings dialogue, select the OK button to close the dialogue (without changing anything).
JIRA StopWatch connects and shows a status of 'Connected'

What do you suggest I do to resolve this issue?
Thanks
Mark

You are using Jira Cloud. Have a look at this section in the documentation, that addresses this.http://jirastopwatch.com/doc/#basicsetup
Let me know if this helps.

Yes, as stated in my original comments for this issue I am using JIRA cloud.
I have already reviewed the linked document, but it does not address the issue I am experiencing as outlined in my original comment - which happened again this morning. As originally stated, I can connect to JIRA using the JIRA StopWatch app (I am connected now as we speak), the issue is the steps I have to go through every morning to get the app to connect.
Please review the points I originally posted and let me know if any of those need clarification.
Thanks
Mark

What I first need to know is: Do you use your e-mail address or your username in Jira StopWatch?  It might be significant.

I have tried both, and am now using my user name.

That is very strange, I must admit that I haven't heard about this behavior before. Since you say that this only started a week ago, and due to you having to do a fix in your Jira account, I'm quite sure, that the problem originates in your Jira Cloud instance.
Do you maybe have some other script, that tries to log into your account with a wrong password, and thereby locks your account?

Maybe you could try to log an issue on Atlassian's support, detailing the steps needed to make login to work. Jira StopWatch simply uses the authentication schemes described on the Cloud Rest API documentation page: https://docs.atlassian.com/jira/REST/cloud/#auth/1/session

@ECGroupIT have you found a resolution for this)

Hi Carsten,
Thanks for looking into this.  Like you I think that this is likely some sort of issue with my cloud account.  I do not have any other scripts trying to connect to my account as far as I am aware.  Having said that, I'm unaware of any way to monitor this on the JIRA cloud - I'll raise a ticket with Atlassian to check this.  Also, I am not getting locked out of JIRA itself, it is just StopWatch that can't connect until I reset the password to the same password.
All very strange.
I'll pursue this with Atlassian and see what they can find.
Thanks
Mark

authors: ECGroupIT carstengehling

repo: carstengehling/jirastopwatch