EACCES permission denied | X-Pack integration

I am receiving an error after installing x-pack along with the search-guard. Kibana is unable to start and keeps restarting in a loop with the following output logged in the log file:
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/plugins/searchguard","message":"Found plugin at /usr/share/kibana/plugins/searchguard"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/plugins/x-pack","message":"Found plugin at /usr/share/kibana/plugins/x-pack"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/console","message":"Found plugin at /usr/share/kibana/src/core_plugins/console"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/elasticsearch","message":"Found plugin at /usr/share/kibana/src/core_plugins/elasticsearch"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/input_control_vis","message":"Found plugin at /usr/share/kibana/src/core_plugins/input_control_vis"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/kbn_doc_views","message":"Found plugin at /usr/share/kibana/src/core_plugins/kbn_doc_views"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/kbn_vislib_vis_types","message":"Found plugin at /usr/share/kibana/src/core_plugins/kbn_vislib_vis_types"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/kibana","message":"Found plugin at /usr/share/kibana/src/core_plugins/kibana"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/markdown_vis","message":"Found plugin at /usr/share/kibana/src/core_plugins/markdown_vis"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/metric_vis","message":"Found plugin at /usr/share/kibana/src/core_plugins/metric_vis"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/metrics","message":"Found plugin at /usr/share/kibana/src/core_plugins/metrics"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/region_map","message":"Found plugin at /usr/share/kibana/src/core_plugins/region_map"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/spy_modes","message":"Found plugin at /usr/share/kibana/src/core_plugins/spy_modes"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/state_session_storage_redirect","message":"Found plugin at /usr/share/kibana/src/core_plugins/state_session_storage_redirect"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/status_page","message":"Found plugin at /usr/share/kibana/src/core_plugins/status_page"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/table_vis","message":"Found plugin at /usr/share/kibana/src/core_plugins/table_vis"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/tagcloud","message":"Found plugin at /usr/share/kibana/src/core_plugins/tagcloud"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/tile_map","message":"Found plugin at /usr/share/kibana/src/core_plugins/tile_map"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/timelion","message":"Found plugin at /usr/share/kibana/src/core_plugins/timelion"}
{"type":"log","@timestamp":"2018-05-11T10:54:29Z","tags":["plugin","debug"],"pid":28977,"path":"/usr/share/kibana/src/core_plugins/vega","message":"Found plugin at /usr/share/kibana/src/core_plugins/vega"}
{"type":"ops","@timestamp":"2018-05-11T10:54:32Z","tags":[],"pid":28977,"os":{"load":[0.64404296875,0.8876953125,0.8994140625],"mem":{"total":16826417152,"free":10633158656},"uptime":2695225},"proc":{"uptime":8.567,"mem":{"rss":188813312,"heapTotal":153804800,"heapUsed":118666592,"external":385550},"delay":3.379054069519043},"load":{"requests":{},"concurrents":{"5601":0},"responseTimes":{},"sockets":{"http":{"total":0},"https":{"total":0}}},"message":"memory: 113.2MB uptime: 0:00:09 load: [0.64 0.89 0.90] delay: 3.379"}
{"type":"error","@timestamp":"2018-05-11T10:54:32Z","tags":["fatal"],"pid":28977,"level":"fatal","error":{"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'","name":"Error","stack":"Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'\n    at Error (native)","code":"EACCES"},"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'"}

Steps to reproduce the issue:

Install Elasticsearch & Kibana
Install x-pack on Elasticsearch
Update the basic license using curl
Install search-guard on Elasticsearch
Configure ssl using the Offline SSL Tool provided by search-guard
Use the default sgconfig to update the configuration
Install x-pack and search guard on Kibana

Below is the config for kibana.yml:
# Use HTTPS instead of HTTP
elasticsearch.url: "https://localhost:9200"

# Configure the Kibana internal server user
elasticsearch.username: "kibanaserver"
elasticsearch.password: "kibanaserver"

# Configure ssl for elasticsearch
elasticsearch.ssl.verificationMode: certificate
elasticsearch.ssl.certificateAuthorities: "/etc/elasticsearch/root-ca.pem"

# Whitelist the Search Guard Multi Tenancy Header
elasticsearch.requestHeadersWhitelist: [ "Authorization", "sgtenant" ]

## X Pack
xpack.monitoring.enabled: true
xpack.graph.enabled: false
xpack.ml.enabled: false
xpack.security.enabled: false
xpack.watcher.enabled: false

Please suggest what is the issue. I will be happy to share any more information that could be needed.
I am using the latest version of ELK and search-guard (v6.2.4).
Also Elasticsearch is up and working. I am able to query the same using curl. Issue exists with Kibana alone.
Regards,
N

@jochenkressin @mgustafsson1 any idea what can cause this?

This is the relevant log entry:
{"type":"error","@timestamp":"2018-05-11T10:54:32Z","tags":["fatal"],"pid":28977,"level":"fatal","error":{"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'","name":"Error","stack":"Error: EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'\n    at Error (native)","code":"EACCES"},"message":"EACCES: permission denied, open '/usr/share/kibana/optimize/bundles/searchguard-login.entry.js'"}
When a plugin is loaded by Kibana, the corresponding files get "optimized" via webpack. The optimized version is then put in the /optimize directory.
This is an access permission on file level. The most likely case is that the Search Guard plugin was installed by a user other than the user that runs the Kibana process.
Can you please check the file permissions for the SG Plugin and also for the "optimize" directory and check that the user that runs the Kibana process has access.

Hi,
Yes. I ran the following command on the /usr/share/kibana/optimize/bundles directory:
chown kibana:kibana -R /usr/share/kibana/optimize/bundles/*

After this, kibana optimized the plugins once again and I was able to see the monitoring app in Kibana. However, this feels a little weird, given that the output of ls -la /usr/share/kibana is as follows:
root@slave1:~# ls -la /usr/share/kibana/
total 1196
drwxrwxr-x  10 root   root      4096 May 12 16:16 .
drwxr-xr-x 126 root   root      4096 May 14 13:25 ..
drwxr-xr-x   2 root   root      4096 May 12 16:16 bin
-rw-rw-r--   1 root   root       562 Apr 13 02:27 LICENSE.txt
drwxrwxr-x   6 root   root      4096 May 12 16:16 node
drwxrwxr-x 909 root   root     36864 May 12 16:16 node_modules
-rw-rw-r--   1 root   root   1134238 Apr 13 02:27 NOTICE.txt
drwxrwxr-x   3 kibana kibana    4096 May 12 16:16 optimize
-rw-rw-r--   1 root   root       721 Apr 13 02:27 package.json
drwxrwxr-x   4 kibana kibana    4096 Jun 10 20:48 plugins
-rw-rw-r--   1 root   root      4772 Apr 13 02:27 README.txt
drwxr-xr-x  15 root   root      4096 May 12 16:15 src
drwxrwxr-x   5 root   root      4096 May 12 16:16 ui_framework
drwxr-xr-x   2 root   root      4096 May 12 16:16 webpackShims

Why is the permission for some directories set to root and some to kibana? I have installed the entire ELK stack using the deb repository.

As this is not really Search Guard but Kibana related I like to close the issue.
I guess the right place for further discussion would be https://discuss.elastic.co

Sure. Thanks for the information.


Accessibility Issue: WCAG 2.0 AA Color Contrast Issue on page /index.html

Description
Color contrast is not 3:1 as needed by WCAG 2.0 AA compliance for large text.
Device Information
Device:
Operating System (incl. version):
Browser (incl. version):
Additional Details:
Element(s) Information
Page:
CSS Selector(s) (if possible and applicable):
Additional Identifier(s) (if possible and applicable):
Additional Details:  All text elements
Screenshot(s) (if possible)

Additional information or thoughts
results from scan #704

@ElminaIusifova will reassign this to myself. Good work !


chore: migrate Callout to TypeScript, remove prop-types & flow

Description
Just a bit more cleanup towards TS.
Checklist

[ ] I have tested this on a device/simulator for each compatible OS
[ ] I updated the documentation with running yarn generate in the root folder
[ ] I added/updated a sample - if a new feature was implemented (/example)

Screenshot OR Video

I was also thinking, if we should switch from javascript directory to src? It's the default for builder-bob.

I was also thinking, if we should switch from javascript directory to src? It's the default for builder-bob.

Yep we can do that.


click 'Retry' button throws error

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
so a workflow failed, then i clicked 'retry' button in UI and received this screen:

Version
v3.4.1
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
n/a

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
kubectl logs -n argo -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

I can't reproduce this one on v3.4.1 and latest on master branch.
I tested with https://github.com/argoproj/argo-workflows/blob/master/examples/continue-on-fail.yaml
Could you help to provide example workflow that able to reproduces the issue ?

@tooptoop4  can you provide the reproducible workflow?

this still affects 3.4.3

be sure to click retry without clicking any task circle

fixed by https://github.com/argoproj/argo-workflows/pull/11071/files


Error at Export job dataset

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Steps to Reproduce

Mark up data
Try to download the dataset in Segmentation mask 1.1 format
You will get this error.

Expected Behavior
No response
Possible Solution
No response
Context
No response
Environment
The work was carried out in the online version

Hello,
Solved in #8185
Release in progress, app.cvat.ai will be updated today.


add and expose etcdctl in k2cli tool

Note: Please file issues for subcomponents under the appropriate repo

Component
Repo

k2
samsung-cnct/k2cli

k2-charts
samsung-cnct/k2-charts

k2-tools
samsung-cnct/k2-tools

What keywords did you search in k2cli issues before filing this one? (If you have found any duplicates, you should instead reply there.): none

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature request

k2cli version (use k2cli version): all
Environment: blank
Please be sure not to submit any confidential information (e.g. ssh keys, provider secrets, etc.) as issues are publicly accessible.

Environment variables (e.g. env | grep 'KRAKEN_):
**Configuration files (~/.kraken/config.yaml or the file passed to k2cli --config) **:
Others:

What happened:
feature request
What you expected to happen:
etcdctl should be available from the k2cli tool subcommand.  it should also, if possible, auto-load the correct SSL certs for the specified cluster.  this will, obviously, require the original output directory to be reachable.
How to reproduce it (as minimally and precisely as possible):
feature request
Anything else we need to know:
When this is complete we should add checking for etcdctl versions weekly.

I should be able to do so fairly quickly, and it will be useful for comcast also. Going to add myself to the ticket.


Fix jenkins test script.

run integration

run integration tests

run integration tests

run integration tests

don't merge this PR. I am testing the e2e test system with this PR.

run integration tests

run integration tests

run integration tests

run integration tests

test this please :)

test this please

test this please

test this please


⚠ Bofrost.es has degraded performance

In 2654afb, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1476 ms

Resolved: Bofrost.es performance has improved in 8a3f8bf after 10 minutes.


ci: don't check branch on e2e publish

Should prevent the error in master seen on https://circleci.com/gh/angular/angular-cli/68840.

Superseded by https://github.com/angular/angular-cli/pull/14982


Add a note into the documentation about fingerprint.prepend

I just read this article by @Kerry350 and it mentioned adding fingerprint.prepend to get the files prepended with the cdn url.  Whilst I know this isn't technically part of ember-cli-deploy it would be nice to put a note in the documentation.

One item to note (@Kerry350 - I don't think I mentioned this yesterday), the prepend should be a value like //<your-assets>.s3.amazonaws.com/ (include slashes).
As another reference, for a more complex scenario with different environment deploys, I'm doing something like the following...
/* global require, module, process */

var EmberApp = require('ember-cli/lib/broccoli/ember-app');
var env = EmberApp.env();
var isProductionBuild = ['production', 'stage'].indexOf(env) > -1;

var config = require('./config/environment')(env);

var app = new EmberApp({
  vendorFiles: { 'handlebars.js': null },
  fingerprint: { prepend: config.assetPrefix },
  minifyCSS: { enabled: isProductionBuild },
  minifyJS: { enabled: isProductionBuild },
  tests: process.env.EMBER_CLI_TEST_COMMAND || !isProductionBuild,
  hinting: process.env.EMBER_CLI_TEST_COMMAND || !isProductionBuild,
});

@danshultz Yeah, checking the article it's not explicit about the forward slash being needed, I'll add it in now (you miss the silliest things writing stuff up). I'll make it schemeless too.
Thanks for your environment snippet. I'm enjoying seeing how everyone is handling this.
@varblob Hope the article was useful in some way :)

@Kerry350 I was stuck on the link rewriting issue until I found out about the prepend through your article.  I realize I forgot to link to it in my original comment.  http://kerrygallagher.co.uk/making-ember-deploy-adapters/ for posterity.


profile doesn't load

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Just as a heads-up: Your profile page takes too long to display since a few days. I always get

I think it's the GH stats in your README.

It's due to a bug in GitHub, about which I'm lazy to open a support ticket to GitHub 😅

Yes, it does! 🎉


[BUG] Tap to focus and zoom does not trigger when archived

I’m using your CameraView package for easy camera integration in my iOS app, and it’s been working great locally. However, I’ve encountered an issue when distributing the app via TestFlight.
Both UIPinchGestureRecognizer and UITapGestureRecognizer work perfectly in both debug and release configurations locally, but they fail to work when archived to a .ipa file. I’ve tried to set the build configuration of the archive to debug as well, but they do not trigger there as well
Here’s the relevant code snippet from the package:
    fileprivate` class UICameraInputView: UIViewController {
        var cameraManager: CameraManager!

        override func viewDidLoad() {
            super.viewDidLoad()
            setupCameraManager()
            setupTapGesture()
            setupPinchGesture()
        }

        override func viewDidLayoutSubviews() {
            super.viewDidLayoutSubviews()
            cameraManager.fixCameraRotation()
        }
    }

    private extension UICameraInputView {
        func setupCameraManager() {
            cameraManager.setup(in: view)
        }

        func setupTapGesture() {
            let tapRecognizer = UITapGestureRecognizer(target: self, action: #selector(handleTapGesture))
            view.addGestureRecognizer(tapRecognizer)
        }

        func setupPinchGesture() {
            let pinchRecognizer = UIPinchGestureRecognizer(target: self, action: #selector(handlePinchGesture))
            view.addGestureRecognizer(pinchRecognizer)
        }

        @objc func handlePinchGesture(_ pinch: UIPinchGestureRecognizer) {
            if pinch.state == .changed {
                let desiredZoomFactor = cameraManager.attributes.zoomFactor + atan2(pinch.velocity, 33)
                changeZoomFactor(desiredZoomFactor)
            }
        }
    }

I’ve ensured that the build settings for the archive configuration match those that worked locally, but the gesture recognizers do not trigger in the TestFlight and adhoc distribution.
Have you encountered this issue before, or do you have any suggestions on what might be going wrong?
Thanks in advance for your help!

I tested it on a clean app, archived it, and installed the .ipa file to my phone locally, without going through TestFlight and the zoom and focus gestures are not triggering.

Hey @Andreasgejlm,
I suspected that this bug would occur because Apple has changed a few things related to concurrency in iOS 18. Unfortunately the same problems have appeared in our other libraries and I am currently working on Popups that I plan to finish in the middle of November.
Next on my list is this library and I'm hoping that my experiences with Popups will help me fix it significantly faster.
I apologise for the inconvenience, but I am currently the only person maintaining our six public and two private repositories +  I have several other responsibilities at the same time, therefore my efficiency is quite low, for which I sincerely apologise 😉
Have a nice day,
Tomasz
PS. You can join our Discord to get the latest updates 😉

Hi Tomasz,
No problem at all. I'm happy you're taking the time to maintain all of this. We are many happy customers.
Interesting with Apples changes to concurrency. I will have to read up on that 😊

Hi Tomasz,
No problem at all. I'm happy you're taking the time to maintain all of this. We are many happy customers.
Interesting with Apples changes to concurrency. I will have to read up on that 😊

/cc @FulcrumOne
I face a new issue with focus. When I open camera the first time, focus works. But after I captured a photo, dismiss the camera view, and I open camera again (to capture another photo) then focus no longer work.
Tested on iPhone 11 and iOS 17.7

@tiendq, @Andreasgejlm,
Both problems should be resolved in the branch patch-3.0.0. Could you please confirm this?
Thanks for your help,
Tomasz

It's an iPhone 13 Mini and yes, I've only tested it on this device.

Thanks, I'll try to get back with something to test soon

@Andreasgejlm, sorry one more thing - could you try archiving demo project to eliminate the possibility that this is caused by part of your application code?

No problem! I just did and the issue still persists.
Please, let me know if there's anything else you need.

@Andreasgejlm,
Could you please try archiving now? I have put the Discord webhooks in the code, which will allow me to check that the methods have actually been called

(but first please update to the head of that - patch-3.0.0 branch)

Done. I reinstalled the demo app with patch-3.0.0 and tapped around.

Could you also use a pinch gesture?

Sure. I just noticed something weird. On first open, the tap and pinch gestures are not registered. However, after a capture a photo and return to the capture screen, it suddenly works.

Yeah, I can see it

Looks to me like gestures are captured not in the main thread (for some reason)

Ok, sorry, but could you try updating the branch and archiving the app one more time? 😅

I tapped and pinched a bit - no result. Captured an image, returned, and then it works.

@Andreasgejlm, ok, let's test another idea then - could you please repeat the action? And thank you very much for your help!

@Andreasgejlm, @tiendq,
Both issues have been fixed in the patch-2.1.1 branch.

@Andreasgejlm, @tiendq,
Both issues have been fixed in the patch-2.1.1 branch.

Sorry to not be able to reply soon, I just tested and it's fixed in main branch (v2.1.1). Thank you.


Question: Network Mode Host

Hi,
I'm trying to run Node-RED in Docker with NRCHKB (a Node-RED nodes pack to simulate Apple HomeKit devices).
Everything is fine —But— I cannot get it to access my HomeKit network which, well… is a big deal :)
I read multiple times that a quick fix is (should be) to set the docker container in Network Mode Host
Since Orbstack is said to support this out of the box, I've made the following:
Node-RED Docker Composer file
services:
  node-red:
    image: nodered/node-red:latest
    container_name: Node-RED
    restart: on-failure:5
    hostname: node-red
    environment:
      TZ: "Europe/Paris"
    volumes:
      - /Users/myUser/Documents/Docker/Node-RED/Data:/data
    network_mode: "host"

docker network inspect host
Sure enough, when I inspect the "host" network, I can since my Node-RED container.
Network seems to work since I can ping the printer on the same network from Node-RED Web UI/
However, HomeKit connectivity seems inexistant since no NRCHKB devices appears as available in Node-RED and  I'm surprised I cannot see any MacAddress, IPv4Address, etc. with docker network inspect host
Am I missing something? Any thoughts about mDNS?
[
    {
        "Name": "host",
        "Id": "93182d3b0411b823bd4ad31c31aaaa40e4c8f",
        "Created": "2024-09-10T15:17:10.883716291+02:00",
        "Scope": "local",
        "Driver": "host",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": null,
            "Config": null
        },
        "Internal": false,
        "Attachable": false,
        "Ingress": false,
        "ConfigFrom": {
            "Network": ""
        },
        "ConfigOnly": false,
        "Containers": {
            "af8d79a37318db276f976a634d6c2": {
                "Name": "Node-RED",
                "EndpointID": "80cbfd9d3780478fbaea84cf0e10bb8ee3e65b31b",
                "MacAddress": "",
                "IPv4Address": "",
                "IPv6Address": ""
            }
        },
        "Options": {},
        "Labels": {}
    }
]

I’m trying to figure this out as well. Seeing the exact same issue between Home Assistant and Homebridge, my guess is because they both use the same protocols when trying to connect to HomeKit.


Sql: Add support for VirtualNetworkRules

Description
Added VirtualNetworkRules feature including scenario tests.

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

[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Jenkins infra error, rerunning: http://azuresdkci.cloudapp.net/job/NetCore-SdkCI/480/


support new file layout

c/o meo:
Would be easier for me to list them and you to decide how best to do it honestly; basically the issue with the lua-path library is the new relative paths used in the interface tree don't allow TOC files inside say Interface/AddOns/... to reference files in ../../../Interface_TBC/AddOns/....
That's the main one.
Once you've gotten past that, you need to process all the client-specific TOC files, so you'll need to read "FrameXML.toc", "FrameXML_TBC.toc", and "FrameXML_Vanilla.toc".
Same applies for addons.
The TOC files for addons are still present in Interface/AddOns.
Same with the TOCs for Frame/Glue.
Bindings.xml files are also err... awkward at present.
While the FrameXML TOC is in Interface\FrameXML, the client reads the bindings from Interface_TBC\FrameXML\Bindings.xml.
The same logic presumably applies to Blizzard addons but I can't confirm.

Another statement by meo:
Small PSA for per-client TOC files; the suffix expected by each client will be changing in future patches to support the following:
For Classic, the client will now additionally search for AddonName_Vanilla.toc.
For BCC, the client will now additionally search for AddonName_TBC.toc.
For Retail, the client will now additionally search for AddonName_Mainline.toc.
The existing suffixes will continue to be supported for backwards compatibility.  The use of _ as the separator can be exchanged with -, so AddOnName-TBC.toc is valid, as well as AddonName_BCC.toc.
Support for the new suffixes should appear in a future hotfix build for patch 2.5.1 and patch 9.1, and is presently implemented on the 2.5.2 PTR.

Unclear if the above is necessary to interpret blizzard addons (yet).


Broken streaming when subscribing both to price stream and client account margin stream

Both streams seem to subscribe successfully, but sometimes one of them (or both) never send any updates

The problem still persists with CIAPI.CS .226
sample: https://github.com/fandrei/SimpleCiapiTest

was this an issue prior to the refactor of streaming client?

yes

so i would think that this is server side.
David, this one needs your attention.

Turns out .NET defaults the concurrent HTTP connection limit to 2; which is only enough for one LSClient.
I've altered the LSClient instantiation process to bump up the number of concurrent HTTP connections allowed each time it's called.


Invalid for_each argument on aws_default_tags

Getting the error while running the EKS cluster creation
│ Error: Invalid for_each argument
│
│   on .terraform/modules/eks/main.tf line 71, in resource "aws_ec2_tag" "cluster_primary_security_group":
│   71:   for_each = { for k, v in merge(var.tags, var.cluster_tags, data.aws_default_tags.current.tags) :
│   72:     k => v if local.create && k != "Name" && var.create_cluster_primary_security_group_tags
│   73:   }
│     ├────────────────
│     │ data.aws_default_tags.current.tags is a map of string, known only after apply
│     │ local.create is true
│     │ var.cluster_tags is map of string with 3 elements
│     │ var.create_cluster_primary_security_group_tags is true
│     │ var.tags is map of string with 3 elements
The "for_each" map includes keys derived from resource attributes that cannot be determined until apply, and so Terraform cannot determine the full set of keys that will identify the instances of this resource.
This is happening because of  data "aws_default_tags" "current" {}.
There is no proper documentation to fix this error, any suggestions ?

I am getting the same issue.  I have tried v18.30.0, v18.30.1, and v18.30.2.  Going back to v18.29.1 fixes the issue for me.

Hi! I have same issue but on different resource. What is more interesting, I'm getting this error on both eks and self managed node groups, for policy attachments, even though EKS group for me has only one policy which is hardcoded arn.
│ Error: Invalid for_each argument
│
│   on .terraform/modules/eks/modules/eks-managed-node-group/main.tf line 448, in resource "aws_iam_role_policy_attachment" "this":
│  448:   for_each = var.create && var.create_iam_role ? toset(compact(distinct(concat([
│  449:     "${local.iam_role_policy_prefix}/AmazonEKSWorkerNodePolicy",
│  450:     "${local.iam_role_policy_prefix}/AmazonEC2ContainerRegistryReadOnly",
│  451:     var.iam_role_attach_cni_policy ? local.cni_policy : "",
│  452:   ], var.iam_role_additional_policies)))) : toset([])
│     ├────────────────
│     │ local.cni_policy is a string, known only after apply
│     │ local.iam_role_policy_prefix is a string, known only after apply
│     │ var.create is true
│     │ var.create_iam_role is true
│     │ var.iam_role_additional_policies is list of string with 1 element
│     │ var.iam_role_attach_cni_policy is true
│
│ The "for_each" set includes values derived from resource attributes that
│ cannot be determined until apply, and so Terraform cannot determine the
│ full set of keys that will identify the instances of this resource.
│
│ When working with unknown values in for_each, it's better to use a map
│ value where the keys are defined statically in your configuration and where
│ only the values contain apply-time results.
│
│ Alternatively, you could use the -target planning option to first apply
│ only the resources that the for_each value depends on, and then apply a
│ second time to fully converge.

iam_role_additional_policies = ["arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy"]

the use of default tags added in v18.30 was unfortunately found to have introduced some issues and we will be correcting this in v19 since its removal is a breaking change. Apologies for any headache experienced by this

This issue has been resolved in version 19.0.0 :tada:


restrict date/year fields to accepted format

Describe the improvement
For some fields in which a date or a year is expected, it is not clear from the interface what format should be used.
For dates we want to use the ISO standard (ie. yyyy-mm-dd).

Publication year
Conference date
embargo period (wrong formatting)

example:
Foutmelding is cryptisch (er stond een spatie in het Publication year wat er niet mocht staan)

TODO: add placeholder

related: https://github.com/ugent-library/biblio-backend/issues/278

There are different cases which we cannot capture in one story; to be split up:
Publication year requires freedom – not only YYYY

Sometimes you do not know what the publication year is (especially for old entrances: s.d. sine dato, approximately this year, ...)
Sometimes the date is B.C. (larger context of our library)
needs freedom, so we avoid "asking people to lie"
We can give guidelines on how to fill it out for consistency, but we should "capture" the essence in the back-end without restricting the user (uniform first, validate after)
-> we need business rules for guidance and to be able to capture the essence. To consult existing best practices.

Conference date also requires freedom

Sometimes you do not know what the publication date is (especially for old entrances: s.d. sine dato, approximately this year, ...), or they only know the year or month
Sometimes the date is B.C. (larger context of our library)
needs freedom, so we avoid "asking people to lie"
We can give guidelines on how to fill it out for consistency, but we should "capture" the essence in the back-end without restricting the user (uniform first, validate after)
-> we need business rules for guidance and to be able to capture the essence. To consult existing best practices.

Embargo period does require exact dates, time stamp

from YYYY/DD/MM until YYYY/DD/MM
important to do reasoning on in back-end
this is okay in this case, because we are not "asking people to lie"

Note: weird notation will not happen anymore when new back-end is fixed. Business rules still need to be figured out.

This does not work at the moment, no validation happens on field level. Year can be filled out with plain text atm.

Need to rethink this:

Flow for 90% of the population: pick/write a year
Flow for internal use: be able to add "sd" or approximations.


Add relaxed rigid contacts model

This PR adds an alternative rigid contact model in which the holonomic constraint is relaxed. This allows some penetration, while guaranteeing more stability with respect to the spring-damper model. It is worth noting that the slipping behavior is not considered.

📚 Documentation preview 📚: https://jaxsim--223.org.readthedocs.build//223/

Good to go! Last, can you please link in the first comment the link to code/documentation of Mujoco/Brax from where this contact model got inspired? Thanks!


Changes to implement OAuth2 based authentication

Use OAuth2 based authentication

@nitinjavakid seems like a good start, i'm going to push ahead with the guzzle 6 rewrite, but this could smooth it over while i get back into this.
Can you write some tests for these classes?
And go ahead and drop all the php 5.* from travis config.

Done.

Sorry to keep bugging...
How are you guys getting and setting the 'access_token' ?
Also whats the best way to bring this into the project? I couldn't find this through composer so, i am just updating the vendor directory manually from a zip downloaded from github. But obviously i will not be able to composer update from now on...

@interludic I've used https://gitlab.com/WitteStier/oauth2-meetup which supports the PHP League OAuth2 package.
You can take some ideas from my implementation here: https://github.com/pavlakis/notts-digital/tree/feature/create-oauth2-meetup-authorisation


fix: move Focused visualstate to CommonStates group

closes https://github.com/unoplatform/uno/issues/14633
closes #1293
PR Type
What kind of change does this PR introduce?

Bugfix

Description
Move Focused visual state into CommonStates VisualStateGroup to avoid conflicts between the FocuseStates and the CommonStates when an element is Focused and then becomes Disabled.
This sort of VisualState organization can be seen in the Fluent styles as well.
Previous Behavior

New Behavior

@mergifyio backport release/stable/4,1

@mergifyio backport release/stable/4.1


question about alpha

Alpha is learnable in the paper, but inside the code
"Flags.metric_multiplier_trainable=False" means that alpha is a fixed value. Could you tell me why?

This is because alpha is cross-validated on the validation set. There has been other configurations in which alpha was learnable, that included the polynomial with learnable coefficients of the metric fed into softmax.


Make a new release to ensure nfov is not removed from Homebrew

Homebrew has decided to deprecate nfov because of the lack of recent releases: https://github.com/Homebrew/homebrew-cask/pull/184697.
Even if you don't have a new release ready with bug fixes or features, you may want to bump some dependencies and make a new release to prevent nfov from being removed from Homebrew.

nfov is not supported anymore. I'm not posting a new release to trick homebrew to think its in development.


new sensor type for janelia lick detector

Could "conductive" be added as a lick sensor type? To describe the janelia lick sensor, which detects a completed circuit when the tongue touches the lick spout, e.g. using the mouse as a switch. Open to other suggestions on how to describe this type of sensor.

I can add this, but isn't this the same as capacitive?

@galenlynch created this diagram illustrating the difference. Top is lickety split, bottom is Janelia sensor. The lickety split detects changes in capacitive load when the mouse licks the metal tube and thus draws voltage from it. The Janelia sensor detects current flowing through the mouse when the mouse licks the tube and completes the circuit.


[Improvement] Touch (ripple) effect should be implemented for all the clickable views

Currently there touch feedback (ripple effect) is not implemented in most of the views, but ideally it should be available at least in Button, Recyclerview items, CardView, etc.

I guess simply moving all activities to AppCompatActivity will do it
automatically.
On 25 October 2016 at 23:42, Paresh Mayani<EMAIL_ADDRESS>wrote:

Currently there touch feedback (ripple effect) is not implemented in most
of the views, but ideally it should be available at least in Button,
Recyclerview items, CardView, etc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-android/issues/763, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABQ_ygFEX48SgMivqRKpC95FMXygYwyxks5q3kaLgaJpZM4KgTvL
.

Currently all the activities are extending AppCompatActivity through BaseActivity.

@PareshMayani Any Updates?


[feat] add course events to calendar

Description
LEARNER-8301
As a user, I want to add all course events to my device's calendar, for a self-paced course
How to test this PR

[ ]   An "add to calendar" message and CTA (switch) is shown on the Course Dates page
[ ] Audit track users see the message, To complete graded assignments as part of this course, you can upgrade today.
[ ] Verified track users see a different message, We built a suggested schedule to help you stay on track. But don’t worry – it’s flexible so you can learn at your own pace. If you happen to fall behind, you’ll be able to adjust the dates to keep yourself on track.
[ ] Message/CTA is shown only for self-paced, and hidden for instructor-paced courses
[ ] Remote flags exist to show/hide the message and CTA
[ ] Switching a CTA from off to on for the first time prompts the user for permission to modify their calendar
[ ] If the user does not allow permission, switching a CTA from off to on notifies the user that the app does not have permission, and directs them to Settings to change their app permissions
[ ] Android experience varies a bit, should be the standard experience by platform
[ ] Switching the CTA from off to on from the Course Dates page presents a native alert or modal to confirm adding the course events:
Title: Add calendar “Technical Support Fundamentals”
Body: Would you like to add the edX calendar <Calendar Name>? You can edit or remove your course calendar any time in Calendar or Settings.
[ ] Confirming adding course events adds all events found on the Course Dates page to the device's calendar. Events are visible in the calendar.
[ ] Added course events
[ ] Calendar events are added to a course specific calendar named edX -
[ ] The calendar "edX" is created if it does not already exist (sub calendar is created on device with course name)
[ ] Are 1 hour in duration
[ ] Start 1 hour before the due time
[ ] Have the name Assignment Due:
[ ] Have a description with the same text as in the Dates tab, without the deep link (deep link is in a different story).  For example: “Homework 6 Peer Assessment (Submission)” or “MA1 section graded exam questions: MA1 Section 3 graded exam questions”
[ ] Switching the CTA from on to off from the Course Dates page deletes the previously added events
[ ] Analytics events

After adding the events to the calendar if a user removes the calendar access from the settings then turning off the sync isn't deleting the calendar events. We need to decide what message we should show to the user.

I think we need to handle this in a followup ticket and show some message to user that we are unable to delete events because calendar is not found.

Design is not exactly in party with the Figma design, font sizes and spacing are not the same.

I have addressed design changes

Figma design is using a different snack bar for success messages.

I have added a new snackbar for calendar actions.


Updated to webpack 3 after resolving the chunks issue + added the missing coins and placed them at the bottom of the list

Better review it since it's a little bit hacky..
Issue
Github issue: #88

You know what, it's a hack so I'll just merge it.
Please npm install next time you pull


chore: change storage log level to WARN for playground

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
It's still too noisy:
2023-03-07T19:32:08.823380Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>142592 is sealed
2023-03-07T19:32:08.823399Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>142592 to seal has no data
2023-03-07T19:32:09.822730Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>678592 is sealed
2023-03-07T19:32:09.822750Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>678592 to seal has no data
2023-03-07T19:32:10.823186Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>214592 is sealed
2023-03-07T19:32:10.823204Z  INFO risingwave_storage::hummock::event_handler::uploader: epoch<PHONE_NUMBER>214592 to seal has no data

Note this is info_in_release, and I'm using docker playground
Documentation

[x] My PR DOES NOT contain user-facing changes.

Click here for Documentation
Types of user-facing changes
Please keep the types that apply to your changes, and remove the others.

Installation and deployment
Connector (sources & sinks)
SQL commands, functions, and operators
RisingWave cluster configuration changes
Other (please specify in the release note below)

Release note

BTW, these log keeps being produced after CREATE TABLE. Is this expected? cc @wenym1

I think we should make all kinds of periodical logs DEBUG... BTW, should we also change this level?
https://github.com/risingwavelabs/risingwave/blob/7fcfeb34ae36a364f87972db50a60d1f7ff5c5f0/src/utils/runtime/src/lib.rs#L52

BTW, should we also change this level?

@BugenZhao I didn't look at the storage log very often, so I'm not sure about its proper level. Please fix that if you think so. 😄

I think we should make all kinds of periodical logs DEBUG

From the doc comment of info_in_release, these logs shouldn't be "periodical"? I have no idea.
https://github.com/risingwavelabs/risingwave/blob/abe0bfe1c91d33ee8c55e978b0bffc9fa001ae15/src/storage/hummock_sdk/src/lib.rs#L56-L64


Inference case for real use cases

Hello. thank you for sharing the code. I have question about inference of single image.
In the evaluation.py
You use the "for loop"
for click_indx in range(max_clicks):
However in the real world, there is no ground truth. I can remove the for loop and give the coordinate positive and negative however i am quite not sure, How we can update the previous information not only the mask, but also the previous click. Do you just keep stacking the mouse click list like below
{  'pclicks' : [],     'nclicks' : []}
I am wondering how you can use the previous click properly.
Thank you.

In real world applications,  users also place clicks iteratively in many rounds. The final input for the model is "two click maps(positive and negative click map) for all clicks,  the previous mask, and  the last click coordinations".
Hence,  as you said, "directly stacking historical clicks" is OK.

Thank you for answering. Does your code consider the previous history of click? when the setting becomes the focal click?
Thank you.

All settings would consider the historical clicks, but do not consider their order

Thanks


typo fix

Fixing a long lasting bug in our documentation, i.e. a space in the name of a vm flavor with a space between the number of cores and the word "cores" itself. Convention is that flavor names do not have spaces.


Type mismatch of mesh id

The function setMeshLayerProperty(mesh: number, layer: number, key: keyof NVMeshLayer, val: number) expects a number as first argument for the mesh identity.
The id of a mesh is a string (from uuidv4())
export class NVMesh {
  id: string

It seems to still work in the demo (https://niivue.github.io/niivue/features/mesh.4D.html), but confuses the linting.

@korbinian90 , We are working on making the use of string IDs and int indices more clear. This is part of the documentation PR #890. As you say, the code does still work because of this slightly naughty function that uses ID in the name to imply strings, but can also work with number index inputs:
// not included in public docs
  getMeshIndexByID(id: string | number): number {
    if (typeof id === 'number') {
      if (id >= this.meshes.length) {
        return -1
      } // range 0..len-1
      return id
    }
    const n = this.meshes.length
    for (let i = 0; i < n; i++) {
      const id_i = this.meshes[i].id
      if (id_i === id) {
        return i
      }
    }
    return -1 // -1 signals that no valid index was found for a volume with the given id
  }

However, I don't have any linting errors in my vs code, and our linting config isn't highlighting this as an error. Could you share more about your linting config?
Regardless, this should be made more clear in the upcoming documentation PR (that will include a few code cleanups too).


background is not set to white with dark mode enabled in admin

@calvintam236 Oh, that's new, I didn't know that you can see a live preview right in the admin. Anyway, it should be fixed now.

Fix confirmed.


Commit line ending switch for log.bat

Git seems to think every line of this file was rewritten even though nothing has changed. This is usually due to Windows or certain editors forcing certain line endings on a file. The line endings in this PR are CRLF.
To verify that i wasn't having a local issue I deleted my entire repo from GitHub, removed my local folder, made a new fork, cloned, and this issue was still present (just cloning the repo fresh from master changed the line endings).

Thanks for noticing this @nemchik. Approved.


Fixes #1265: Use JSCS preset crockford.

What do you think @mikesherov?

Sounds good. I don't see though where it is saving the .jscsrc file in this PR?

I don't see though where it is saving the .jscsrc file in this PR?

Not sure I follow. .jscs.json is removed in this commit because it's not needed anymore.


Spelling Errors in Plan Create query

Hey i have just found that on create billable page (link given below). you have written wrong spelling in query.
link : https://github.com/ohmybrew/laravel-shopify/wiki/Creating-a-Billable-App
"VALUSE " should be "VALUES" and "trials_days" should be "trial_days".
Thank You.

Fixed: https://github.com/ohmybrew/laravel-shopify/wiki/Creating-a-Billable-App

Thanks! Closing.


⚠ ClamAV has degraded performance

In d9b466a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 477 ms

Resolved: ClamAV performance has improved in 2792213.


Forecast Reconciliation

I am not sure if GluonTS currently supports something like forecast reconciliation of hierarchical or grouped time series. This means that the sum of all forecasts that make up a hierarchy matches to the forecast of the hierarchy. Say, you forecast several time series that are within the same hierarchy + the time series of the total (e.g., all tourism visits in Australia within all territories + Total Tourism of the territories as an aggregate). What forecast reconciliation does it makes sure that the bottom level forecasts match the top-level aggregate forecast. You may find a very good overview here
https://otexts.com/fpp2/hierarchical.html
As GluonTS is a probabilistic framework, we also need to make sure that the uncertainty attached to the forecasts are corrected. You may find the corresponding paper here
https://robjhyndman.com/publications/coherentprob/
Besides cross-sectional hierarchies, you may also want to include temporal hierarchies, so that you train the  model on daily, weekly and monthly data, and you make sure that all sum up to the monthly forecast. You may find a very good overview here
https://kourentzes.com/forecasting/2019/02/09/towards-the-one-number-forecast/
And a paper on how to combine cross-sectional and temporal aggregation here
https://kourentzes.com/forecasting/wp-content/uploads/2019/02/Kourentzes_2019_Cross_temporal_coherent_forecasts__the_case_of_Australian_tourism_flows.pdf
The paper shows that Cross-temporal coherent forecasts improve accuracy compared to not taking the information into account.

It doesn't currently! I'm aware of some of the papers, though and it's a line of research that I quite like, but I'd probably try something else instead -- e.g., a big model instead of many small models that you then reconciliate.
For the moment, you can always try a multivariate model or a global model and use the hierarchy as categorical features. Or, of course, contribute reconcilation back to GluonTS :-)

Thanks Tim! I see what I can do with respect to the reconciliation contribution :-)
A somewhat off-topic, I hope you don`t mind: is the deep-factor model still maintained? I am asking because I can find very little notebooks / examples. This is related to this DeepFactor Question. Would great if you could help. Thanks!

Very relevant topic.


Font-Awesome Remove uploaded Image

I set  :useFontAwesome="true"  on the component, the cloud image works, but the uploaded images remove icon is just a white frame.
greetings

Hi @patpaskoch
Sounds like you haven't loaded don't awesome on your site, you need to include it in the head of your site like
   <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.7.0/css/font-awesome.min.css" rel="stylesheet">

Let me know how you get on

well if the upload-cloud appears font awesome should be there and I work with weppack and import font awesome.scss from my node modules

Ah sorry @patpaskoch I misread your initial message.
I've just checked and everything works as expected. One thing to check is to make sure that you're passing thorugh the parameter name correctly it needs to be done like
<dropzone :use-font-awesome="true">

If that doesnt work for you could you please send through a screenshot?
Thanks

Import Font Awesome 4.7.0
@import "node_modules/font-awesome/scss/font-awesome.scss";
html dropzone
<dropzone id="vueDropzone"
			:language="language"
			:use-font-awesome="true"
			:url="'url'"
			:show-remove-link="true"
			v-on:vdropzone-success="showSuccess"
		>
	        	<input type="hidden" name="_token" :value="csrf ">
	    </dropzone>

so the first and second screenshot show dropzone without prop :useFontAwesome
third and last show with :use-font-awesome

so if I add the prop the cloud works and also the check-mark if images got successfully uploaded apears.

Can you remove :show-remove-link="true" , I don't normally set this as it defaults to true anyway

removed it, didn't changed a thing

How about your language object, it looks like you are passing through a custom object, does it contain a dictRemoveFile property?

language: {
dictDefaultMessage: '
Drag and Drop files in this area or click in it.'
}

the html that gets displayed

also, the error icon has troubles

Hi @patpaskoch
Any language object that you pass through does not merge on to the default object, so you have to pass through all the language settings, this isn't ideal, I'll try and get it fixed at some stage although Im open to a pull request

Ok I get it, removed the language prop and everything works just fine.

Thanks for your fix @patpaskoch , Im going to mark this as closed and I'll drop a note here when it's published to npm


Creating missing repos for image push by providers

Is your feature request related to a problem? Please describe.

In kairos 1.5.0, opensuse repo is changed to -leap and -tumbleweed . In providers, we are bumping up kairos version to 1.5.0 and opensuse image to opensuse-leap and I have noticed that repos core-opensuse-leap-k3s, core-opensuse-leap-rke2 and core-opensuse-leap-kubeadm aren’t there as of now and release build of providers will fail.
Describe the solution you'd like

Repos should be present so that provider images can be pushed.
Describe alternatives you've considered

Additional context

done :+1:


events.endTurn() doesn't work with multiplayer: local

I'm trying to get Local Master multiplayer working, looking at
https://boardgame.io/#/multiplayer
In the version  in the codesandbox,

the onClick handler for the TicTacToeBoard is
 onClick(id) {   if (this.isActive(id)) {     this.props.moves.clickCell(id);   } }
and we have  set
flow: {   movesPerTurn: 1, ... }
so that the framework knows to end the turn after every move.

This works as expected, you can play as both players by alternating between the first client and the second client.
However, if we modify the code as follows, to match with the beginning tutorial at  https://boardgame.io/#/tutorial:

Adding an explicit endTurn() to the click handler:
 onClick(id) {  if (this.isActive(id)) {    this.props.moves.clickCell(id); this.props.events.endTurn();  } }
Removing the movesPerTurn property from flow,

then the game stops working. Clicking on the first client results in error:
ERROR: invalid stateID, was=[1], expected=[0]
and it seems as the turn doesn't end.
Shouldn't both methods work?
Note: If we run without local multiplayer mode by using
const App = Client({   game: TicTacToe,   board: TicTacToeBoard, }); export default App;
Then everything works fine.

Thanks for the report.
This is due to a race condition where the client is not seeing the new game state between the move and the end turn event. I'll take a closer look soon.

A workaround for now (until this gets fixed) would be to wrap the endTurn in a setTimeout like this:
this.props.move.clickCell(id);
setTimeout(() => this.props.events.endTurn(), 0);

Fixed in v0.31.5.
Can you upgrade and try?


Remove engine usage from attach

ping @tiborvass

LGTM waiting for CI

LGTM

Well I was waiting for Windows CI to re-run, but you seemed to have pushed an update  now :(

@cpuguy83 yup :) No worries, windows was failed only on TestPullVerify.

shakes fist in air at that test

LGTM


Saleor ran into an unexpected problem.  When login /dashboard?

Saleor ran into an unexpected problem.  When login /dashboard.
Please help me !

That’s problem with your API_URI. Open chrome and the developer tools, check the console. And paste the error here or an screenshot

Saleor ran into an unexpected problem. When login /dashboard.
Please help me !

I had the same issue when trying to connect to a remote installation (not on localhost).
I had to set API_URI and STATIC_URL to URLs with the right IPs (or FQDN), not localhost like in the documentation.
You can check that the dashboard is connecting to the right instance by checking with your browser developper tools as acidlake said above.

@aselam So did you solve this on production ? I am trying to deploy everything on production, but I am not sure what need to change in settings.py
I have the same problem as @theanhvo on localhost and I've decide to do on production, but not sure how to start with it. I have install saleor, storefornt and dashboard, but when I want to test my web server crashed.
Have you any solution ?
Thanks

index.js?cf67:88 POST http://localhost:9000/graphql/ 405 (Method Not Allowed)

@milanmaximo I was just testing saleor on a virtual machine, nothing fancy.
In production as you said, even if you installed all components on the same server, your browser is loading storefront/dashboard and making queries by themselves from your... browser. So from saleor's perspective, it's not a connection from localhost (the server), it's a remote connection (from your computer).
When you said it crashed, what crashed exactly?
By default, when you start saleor to test it:

it's listening on localhost. If you want to test it in a VM, you need to specify that the development server should listen on VM's private IP (``)
it accepts remote connections only from localhost: you need to specify which IPs are allowed to connect to it by setting ALLOWED_HOSTS in django settings.py

Also, you need to set API_URI and STATIC_URL before starting Saleor:
export API_URL='http://<Saleor IP>:<Saleor port>/graphql/'
export STATIC_URL='http://<Dashboard IP>:<Dashboard port>'

Then, after starting saleor with manager.py runserver <IP>:<port>, you should see the GraphQL Playground
Regarding Dashboard, in a test environment, you'll need to configure webpack to start the server on your private IP in webpack.config.js:
devServer: {
      compress: true,
      contentBase: path.join(__dirname, dashboardBuildPath),
      historyApiFallback: true,
      hot: true,
      host: '<IP_ADDRESS>',
      port: <Dashboard port>
    },

After npm start (beware, can take some time), the dasboard should be up and running on http://:
Regarding Storefront, still in a test environment, settings are in cypress.json
"baseurl": "http://<Storefront IP>:<Storefront port>",
"env": {
"API_URI": "http://<Saleor IP>:<Saleor port>"
}

After npm start (beware again, can take some time), Storefront should be up and running on http://:
Note: I'm not sure if it's the right file to set, as it's the first time I play with Nodejs and Webpack... maybe somewhere else in Webpack's configuration?..

I have the same problem. As I see everything  is configured as need.

I have the same problem too and as I am still very new to django and webdev as a whole I am confused as to how to change the EnvironmentPlugin - API_URI and APP_MOUNT_URI variables. Because these are my errors when I try to access the dashboard:
These are my dev logs

EnvironmentPlugin - API_URI environment variable is undefined.
EnvironmentPlugin - APP_MOUNT_URI environment variable is undefined.

@OmniOracle hello there, you just need to open a terminal, and:
API_URI="http://yoururl:8000/graphql/" APP_MOUNT_URI="/" npm start
and that's it, also this Repo is for SALEOR server, you should comment about this on the repo for the DASBOARD

Thank you mate, Now I am getting somewhere!

@milanmaximo I was just testing saleor on a virtual machine, nothing fancy.
In production as you said, even if you installed all components on the same server, your browser is loading storefront/dashboard and making queries by themselves from your... browser. So from saleor's perspective, it's not a connection from localhost (the server), it's a remote connection (from your computer).
When you said it crashed, what crashed exactly?
By default, when you start saleor to test it:

it's listening on localhost. If you want to test it in a VM, you need to specify that the development server should listen on VM's private IP (``)
it accepts remote connections only from localhost: you need to specify which IPs are allowed to connect to it by setting ALLOWED_HOSTS in django settings.py

Also, you need to set API_URI and STATIC_URL before starting Saleor:
export API_URL='http://<Saleor IP>:<Saleor port>/graphql/'
export STATIC_URL='http://<Dashboard IP>:<Dashboard port>'

Then, after starting saleor with manager.py runserver <IP>:<port>, you should see the GraphQL Playground
Regarding Dashboard, in a test environment, you'll need to configure webpack to start the server on your private IP in webpack.config.js:
devServer: {
      compress: true,
      contentBase: path.join(__dirname, dashboardBuildPath),
      historyApiFallback: true,
      hot: true,
      host: '<IP_ADDRESS>',
      port: <Dashboard port>
    },

After npm start (beware, can take some time), the dasboard should be up and running on http://:
Regarding Storefront, still in a test environment, settings are in cypress.json
"baseurl": "http://<Storefront IP>:<Storefront port>",
"env": {
"API_URI": "http://<Saleor IP>:<Saleor port>"
}

After npm start (beware again, can take some time), Storefront should be up and running on http://:
Note: I'm not sure if it's the right file to set, as it's the first time I play with Nodejs and Webpack... maybe somewhere else in Webpack's configuration?..

could you tell me how to solve https://github.com/mirumee/saleor-storefront/issues/646  when in production mode?

There is an error in documentation: https://docs.saleor.io/docs/developer/installation/windows#running-the-dashboard
Command Prompt it is written: set API_URI "http://localhost:8000/graphql/"
But should be: set "API_URI=http://localhost:8000/graphql/"
or: set API_URI=http://localhost:8000/graphql/

Hi i have same probleam


[Flaky CI] Creating a VirtualMachineInstance with user-data without k8s secret [test_id:1629][posneg:negative]should not be able to start virt-launcher pod

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

/kind enhancement

/triage build-watcher
What happened:
The test failed on prow on lane pull-kubevirt-e2e-k8s-1.18
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:

KubeVirt version (use virtctl version):
Kubernetes version (use kubectl version):
VM or VMI specifications:
Cloud provider or hardware configuration:
OS (e.g. from /etc/os-release):
Kernel (e.g. uname -a):
Install tools:
Others:

duplicate


Upgrade sonobuoy from 0.56.4 to 0.56.8

sonobuoy:0.56.4 still tries to pull images from "k8s.gcr.io", which is deprecated. The default image registry should be migrated to "registry.k8s.io" to support the latest Kubernetes release. So the sonobuoy should be upgraded to 0.56.8.

/test-ipv6-e2e
/test-e2e
/test-conformance

@tnqn Hi Quan. Could you please take a look at this PR since the new testbed is deployed with Kubernetes v1.27.2

@hjiajing thanks, however this is duplicate with https://github.com/antrea-io/antrea/pull/5184.

@tnqn Thanks for the reminder. I'll close this one.


editorial: get_all_datasets

See curation-api.

The correct way to retrieve all datasets for a Collection is GET /collections/{collection_id} and grabbing the .datasets array off of the response body.
We should not create a new endpoint for this. We can add the collection_id to the attributes for each dataset if that is desired cc @jahilton

Generating a Dataset table will be a common occurrence. I would see an endpoint to be consistent with UI behavior (I can browse all Collections or I can browse all Datasets).
Without an endpoint for this, I believe my process will be to GET /collections, append the id to a list of all dataset ids, then run GET /dataset for each of those ids. (this will return more full metadata than getting the dataset 'preview' in GET /collections). Adding collection_id to the response from GET /dataset will be incredibly helpful.

I also disagree with @danieljhegeman - the mitigation requires N*dataset API calls to get the full metadata for each dataset. The number of datasets will not be getting smaller.

Acknowledged, if we need to be able to, given a dataset_id and not a collection_id, fetch a dataset, then that is a valid need for this proposed endpoint, assuming I am understanding the need correctly

Adding collection_id to the response from GET /dataset will be incredibly helpful.

@jahilton is this related to the central issue? I'm still a bit fuzzy on the workflow here.

the mitigation requires N*dataset API calls to get the full metadata for each dataset. The number of datasets will not be getting smaller.

As long as the number of calls is not scaling past constant O(1) per dataset retrieved, I am not worried. One call per dataset will work out just fine.
There could be reason to support batch retrieval of datasets, but that would also require some retooling on the backend to parallelize certain operations, things which are currently sequential, because it's easier and because we do not yet need to return (tens of) thousands of datasets with extremely low latency.

Per triage with @jahilton and @Bento007 - there is a request to include a convenience function in the notebooks. No endpoint required at this time.

Per agreement with @jahilton , this will be accomplished by (trivial) custom programming on the client side to loop over Collections and populate a list with the full dataset metadata that is returned for each GET /collections/{collection_id} call. No further work needed from us.


Color scheme - determine color scheme for site

https://coolors.co/user/palettes/6308ca06c1f366000ba25599

Color scheme attached


Player does not recover if license server unreachable.

Have you read the FAQ and checked for duplicate issues: Yes
What version of Shaka Player are you using: 2.2.4
Can you reproduce the issue with our latest release version: Yes
Can you reproduce the issue with the latest code from master: Yes
Are you using the demo app or your own custom app: Custom App
If custom app, can you reproduce the issue using our demo app: Yes
What browser and OS are you using: Chrome 62 / Firefox 56
What are the manifest and license server URIs:
(you can send the URIs to<EMAIL_ADDRESS>instead, but please use GitHub and the template for the rest) Emailed
What did you do?
First scenario: (to easily demonstrated the issue)

Make custom asset request to a custom license server which in unreachable (for example, an invalid web application path (404 response)).
Enter correct path for license server.
Select 'Load' again.

Second scenario: (which is the most likely issue in deployment, e.g. where the license server is unreachable) can be demonstrated by doing the following.

Stop webserver
Make custom asset request to custom license server (request eventually fails)
Start webserver
Select 'Load' again.

What did you expect to happen?
The first request will give a NETWORK ERROR.
The second request will hit the license server and serve a license or give an expected error.
It is not expected that the player application should need reloaded.
What actually happened?
The first request give a NETWORK ERROR.
The second request is not made as the player appears to have frozen.
To make the second request the page must be reloaded.

I think I'm having the same issue, I believe it's a Chrome bug, and I feel like it's new because I've never noticed it before.
Here's what's happening to me:

Load playback and force license request to fail (I'm setting error response in Charles Proxy)
Change Charles Proxy settings to allow license request to succeed
Try to load again
Player hangs

I traced it down to this line in DrmEngine:
var p = activeSession.session.close() || Promise.resolve();

The call to MediaKeySession#close is never resolving.

I can also reproduce in the demo app using the same steps as @KieronAllsop described.

Yes it occurs in both Firefox and Chrome, but not in Edge with the same steps so must at some level be related to Widevine ?
In response to your thought @chrisfillmore that it could be related to license server configuration, neither the first play request, which causes the hang, nor the econd play request ever reach the license server.

This looks similar to https://crbug.com/690583.  But I cannot reproduce.  I went to the hosted demo and entered one of the protected demo asset URLs into the custom asset field and used a bad URL for the license server.  I get an error and the video stops at the end of the clear lead.  If I select a different asset and click Load again, the new asset plays fine.
Can you reproduce with just the hosted demo without an external proxy?  Can you provide a manifest URL to a content that reproduces?  What is the exact version of Chrome you are using?  What version of the Widevine plugin are you using?  You can get it from navigator.plugins (unfortunately chrome://plugins doesn't work anymore).

Version of Chrome is 62.0.3202.75
Widevine Content Decryption Module - Version: <IP_ADDRESS>9
Windows 10.15063
Navigate to https://urm.latens.com/boomplayer/demo/ (v2.2.5-debug)
Select 'Custom Asset'

Asset = https://storage.googleapis.com/shaka-demo-assets/angel-one-widevine/dash.mpd
License = https://www.random_address.com/license
Select 'Load'

Immediate error:
"Shaka Error DRM.LICENSE_REQUEST_FAILED (shaka.util.Error { "severity": 2, "category": 1, "code": 1002, "data": [ "https://www.random_address.com/license" ], "handled": false, "message": "Shaka Error NETWORK.HTTP_ERROR (https://www.random_address.com/license)", "stack": "Error: Shaka Error NETWORK.HTTP_ERROR (https://www.random_address.com/license)\n at new shaka.util.Error (https://shaka-player-demo.appspot.com/lib/util/error.js:72:13)\n at XMLHttpRequest.xhr.onerror (https://shaka-player-demo.appspot.com/lib/net/http_plugin.js:92:14)" })"
Clear lead plays, then video stops.
If I go to drop down and select a different asset (clear or widevine) nothing happens when I select 'Load'
I must reload page to get anything to play again.
Does the same in iOS Sierra 10.12.6 (Chrome and Widevine versions the same)

I can't reproduce with our nightly build or the v2.2.5 official release:
https://nightly-dot-shaka-player-demo.appspot.com/demo/#asset=https://storage.googleapis.com/shaka-demo-assets/angel-one-widevine/dash.mpd;license=https://www.random_address.com/license;lang=en-US
https://v2-2-5-dot-shaka-player-demo.appspot.com/demo/#asset=https://storage.googleapis.com/shaka-demo-assets/angel-one-widevine/dash.mpd;license=https://www.random_address.com/license;lang=en-US
In both cases, the first video stops after the clear lead.  If I select another video from the list and click "Load", it loads.
I am also unable to reproduce in your demo app: https://urm.latens.com/boomplayer/demo/
I am running the same Chrome and Widevine versions as you.

@joeyparrish can I ask what operating system you are running Chrome on?
I agree the issue is not reproducible in linux (Fedora 25 specifically).
However having tried both links given above and the same version of Chrome/Widevine I can reproduce the issue on our Windows 10 (v15063), Windows 10 Insiders (v17025), High Sierra and Sierra test machines.

I've been using Linux, but I will go retest on Windows and Mac.

Confirmed on Mac.  It definitely appears to be caused by https://crbug.com/690583, because the closed Promise on the session is never resolved.  I will try to escalate the issue with Chrome team.

Sorry, I was on vacation and didn't respond earlier. Thanks for the update @joeyparrish!

@joeyparrish would Shaka team consider this workaround?
I've deployed a fork of Shaka in our projects which uses this workaround, and haven't encountered any issues in the wild (that I know of). In general I prefer not to maintain a fork though.

The bug in Chrome is still not fixed, but the workaround by @chrisfillmore will appear in the v2.2.8 bug fix release of Shaka Player.  Thanks!


Notify the client on failure.

When the server does not load because it is not on the allowed list for example the client stays on stand-by and does not get notified.

Fix by #10


Provide twitch user documentation

Provide comprehensive documentation on commands supported by the twitch app.

Added in v1.7.2: https://brainswax.github.io/thegoatchick/Commands.html


[test] Migrate tool checks to hpctools.git

Will fix https://jira.cscs.ch/browse/UES-675

Hello @jgphpc, Thank you for submitting the Pull Request!

In the file cscs-checks/tools/profiling_and_debugging/roofline/berkeley-ert-serial.py:

Line 7:1: E265 block comment should start with '# '
Line 32:1: E265 block comment should start with '# '
Line 34:1: E265 block comment should start with '# '
Line 35:1: E302 expected 2 blank lines, found 1
Line 39:7: E114 indentation is not a multiple of four (comment)
Line 39:7: E116 unexpected indentation (comment)
Line 39:7: E265 block comment should start with '# '
Line 118:14: W291 trailing whitespace
Line 141:39: E127 continuation line over-indented for visual indent
Line 143:39: E127 continuation line over-indented for visual indent
Line 145:39: E127 continuation line over-indented for visual indent
Line 170:1: E265 block comment should start with '# '

Do see the ReFrame Coding Style Guide

@jgphpc We cannot merge this until you fix the conflicts. They are due to the fact that we have changed the files in the master (added a copyright notice) and you are now removing them.

@vkarak tests 🆗 on daint  (and dom)


servicemonitor in chart is empty

servicemonitor in chart is empty
https://github.com/spidernet-io/spiderpool/blob/main/charts/spiderpool/templates/servicemonitor.yaml

https://github.com/spidernet-io/spiderpool/pull/1009


Franz opens off screen edges

When I open Franz for the first time every day it tries to open it on my second screen even if the second screen is not connected. In addition when the second screen is not to the right but below the first screen it still opens on the right side of my first screen
Expected Behavior
Franz should open on an active screen or the position you last used it. Not reset to a position that is no longer available
Current Behavior
Franz opens off screen the window is not reachable using the mouse.
Possible Solution
It looks like Franz is using a fixed position to open the window, suggestion would be that it would open on the first monitor.
Steps to Reproduce (for bugs)

Start computer
Open Franz

Context
Every time I use Franz (every day) for the first time I have to use key commands to move the window back to a visible position. (ALT + SPACE) then press R and move the window with the arrow keys.
Your Environment

Franz Version used: Franz 5.0.0 Beta 14
Operating System and version: Windows 10 Pro

@janacm do you mean the shortcut for disabling notifications and audio ctrl+shift+m?
i'm intrigued as to what workaround that is? :) i'm assuming you're on Windows?

merging this into #222
Duplicate of #222

merging this:
Duplicate of #222

Duplicate of #222

@janacm I think the shortcut is actually alt+space, then M


Dead link in README

Paragraph 5, “API” is a dead link.

https://github.com/sovrin-foundation/sovrin/pull/109


Filter commands from get_properties

The get_properties of the ContextEntity model currently returns all Attributes that do not have the type Relationship.
It should also filter out the commands (cretaed by Fiware).

@djs0109 if you want all attributes you can simply use get_attributes. Properties are attribues that describe the object itselft but not its relationships. In ngsi-ld this concept becomes much more clear.
Relationships should usually not alter over time. If that happens old relationships should be deleted first and new attributes of type relationship created.
Please open a new issue if there is any problem with this.

#145


i18n(fr): update api-reference.mdx

Description (required)

Update French version of api-reference.mdx with changes from #9422 and from #9261 (it seems we missed some updates)

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

fr
reference/api-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Static Code Analysis to SonarCloud

Description
The Hyperledger foundation has a SonarCloud instance with a pre-configured Besu project, located here. The Besu gradle project should be configured to do analysis on demand. CI jobs can then be set up to require that analysis on a yet to be determined basis.
As a starting point, default analysis rules should be used, open to further refinement by contributors.
Acceptance Criteria

There exists a new gradle task in the root project, which will run sonar static analysis on all projects, and publish results at the sonarcloud instance described above.

Assuming it can be run more quickly than the acceptance tests I see no downside to wiring it up and putting the badges on the readme.
But, the interesting question is what action will be taken next.
We might want to run it on each build and flag up any serious increase in say cyclomatic complexity or we might want to raise/block a build with a critical cve (is this done already?!).

For an example run, take a look here


rehex: 0.3.92 -> 0.4.1

Motivation for this change
Tool update +

enable parallel building
use SPDX 3.0 license identifier
fix Darwin build
add meta.changelog

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Ah not yet ok on Darwin... Now that it can locate png2icns there is a problem with the Makefile


FALCON-1724 Falcon CLI.twiki in docs folder is not pointed by index page

Currentlt Faclon CLI.twiki is not pointed by any page we need to remove it to avoid the confusion.

@PraveenAdlakha, a quick search shows that Recipes.twiki has some reference to old FalconCLI. Can you please update that too?
$ find . -name "*.twiki" | xargs grep -r FalconCLI | grep -v FalconCLI.twiki
./src/site/twiki/index.twiki:[[falconcli/FalconCLI][Falcon CLI]] implements [[restapi/ResourceList][Falcon's RESTful API]] and
./src/site/twiki/Recipes.twiki:Recipe command usage is defined here.
./src/site/twiki/Recipes.twiki:   * Invokes a Tool to substitute the properties in the templated process for the recipe. By default invokes base tool if tool option is not passed. Tool is responsible for generating process entity at the path specified by FalconCLI
./src/site/twiki/Recipes.twiki:   * Looks for the patten ##[A-Za-z0-9_.]*## in the templated process and substitutes it with the properties. Process entity generated after the substitution is written to the empty file passed by FalconCLI

+1. Will merge.


Include Kyunghee University global campus

khu.ac.kr
Request a full request for use on Kyung Hee University's global campus.
The existing Kyung Hee University email is currently approved on swot and I don't know if that email domain is still used that was registered in the past, but the university is using khu.ac.kr domain.
So, I would like to request additional approval for that domain.

@koosco First stage of verification passed, official domain is khu.ac.kr as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision. Proof of domain ownership: https://www.khu.ac.kr/eng/sub/tab.do?MENU_SEQ=1000680

@koosco Your request contains a file that represents khu.ac domain, not khu.ac.kr. Please clarify:

What is "The existing Kyung Hee University email is currently approved on swot"?
What is the domain that you wish to add to this repository?

Thank you!

@philipto I think I made a mistake. domain is khu.ac.kr

The existing Kyung Hee university email domain is kyunghee.ac.kr and the path is kr/ac/kyunghee.txt
And the domain I wish to add is khu.ac.kr

Should I send a full request again?
Thank you

@koosco  Thank you for the clarifications. You don't need to submit a new request. I updated your pull request and merged it. Thank you!


Edit to OSS files and README

Now that we have open sourced our instrumentation using the standardization best practices laid out in the open-by-default repository, we need to revisit repositories that were previously open source and make updates to achieve consistency in our open instrumentation repositories.

Pull Request Test Coverage Report for Build 216618131

0 of 0   changed or added relevant lines in 0 files are covered.
6 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at ?%

Files with Coverage Reduction
New Missed Lines
%

internal/integrations/v4/runner/stderr_queue.go
6
20.0%

Totals

Change from base Build 215377799:
0%

Covered Lines:

Relevant Lines:
0

💛  - Coveralls


masscode: Add version 2.10.0

Relates to #8928

[x] I have read the Contributing Guide.

/verify

config location: $Env:UserProfile\massCode
(This is a reminder. No need to modify anything regard to this.)


DSL for $brooklyn:location()

(I've removed the commit "DslComponent: code tidy" because that broke existing tests!)

Looks good, nothing to add to @geomacy's comments

hi @aledsage just checking what do you think about merging this PR?

Thanks @geomacy @nakomis
I've added testDslLocationIndexOutOfBounds, which asserts that we get a nice exception when one tries to retrieve in anger the config value that has an invalid index.
I think this is tricky to improve, without going into bigger more general changes.
As you point out, for the blueprint:
location: localhost
services:
  - type: org.apache.brooklyn.entity.stock.BasicApplication
    brooklyn.config:
      config1: $brooklyn:location()
      config2: $brooklyn:location("0")
      config3: $brooklyn:location("1")
      config4: $brooklyn:attributeWhenReady("sensorDoesNotExist")

br app obrjk09hec config returns:
Key                  | Value
config1              | map[type:org.apache.brooklyn.api.location.Location id:whoq9008c0]
defaultDisplayName   | <nil>
camp.template.id     | ClysL4Gs
config2              | map[type:org.apache.brooklyn.api.location.Location id:whoq9008c0]
config3              | map[component:map[componentId: componentIdSupplier:<nil> scopeComponent:<nil> scope:THIS] index:1]
config4              | map[component:map[componentId: componentIdSupplier:<nil> scopeComponent:<nil> scope:THIS] sensorName:sensorDoesNotExist]

The config3 evaluation has only been logged at debug, because the value isn't yet being used - it's just retrieved for display purposes, so hasn't blocked. It failed to resolve immediately, so we go the DSL object back. You can see we get the same behaviour for an attributeWhenReady that cannot yet be evaluated.
If we wrote a blueprint that actually tried to use it (i.e. that caused entity.config().get("config3") to be called), then it would throw the exception, which would be logged at warn.
The two things you point out would be good more general improvements:

/v1/applications/<appId>/entities/<entityId>/config/current-state?raw=false should return nicer representation of DSL objects (e.g. calling toString() on it, rather than showing the values of the fields component and index).

Location representation in the above call doesn't give much info - just the id, and that it's a location. It would be good to give more info as well (e.g. the display name).

Are you ok with merging this PR as-is, and us making those more general improvements separately?

LGTM apart from a minor comment on the test. I agree it would be nice to be able to tell whether DSL simply hasn't resolved yet or whether it's permanently failed to resolve, but I'm happy for this PR to be merged in the meantime

Thanks @geomacy @nakomis - merging now. Brooklyn issues are probably the best way to record and track further improvements, I think.


Getting Error While Installing Netcal (Pyro-ppl library Issue)

File "/workspace/system-paper/main_util.py", line 23, in
from netcal.scaling import TemperatureScaling
File "/opt/conda/lib/python3.6/site-packages/netcal/scaling/init.py", line 28, in
from .AbstractLogisticRegression import AbstractLogisticRegression
File "/opt/conda/lib/python3.6/site-packages/netcal/scaling/AbstractLogisticRegression.py", line 26, in
import pyro
File "/opt/conda/lib/python3.6/site-packages/pyro/init.py", line 4, in
import pyro.poutine as poutine
File "/opt/conda/lib/python3.6/site-packages/pyro/poutine/init.py", line 4, in
from .handlers import (
File "/opt/conda/lib/python3.6/site-packages/pyro/poutine/handlers.py", line 60, in
from .collapse_messenger import CollapseMessenger
File "/opt/conda/lib/python3.6/site-packages/pyro/poutine/collapse_messenger.py", line 7, in
from pyro.distributions.distribution import COERCIONS
File "/opt/conda/lib/python3.6/site-packages/pyro/distributions/init.py", line 4, in
import pyro.distributions.torch_patch # noqa F403
File "/opt/conda/lib/python3.6/site-packages/pyro/distributions/torch_patch.py", line 87, in
@patch_dependency("torch.distributions.constraints._CorrCholesky.check")
File "/opt/conda/lib/python3.6/site-packages/pyro/distributions/torch_patch.py", line 18, in patch_dependency
module = getattr(module, part)
AttributeError: module 'torch.distributions.constraints' has no attribute '_CorrCholesky

Hi, could you please give me some more information about your environment? Which Python version are you using?

Just try installing pyro-ppl==1.3. I had the same issue, but changing my earlier pyro-ppl 1.8 version to pyro-ppl 1.3 worked out.


feat: checkpoint logic for EVM, ICON, and WASM chains

This pull request adds checkpoint logic for the EVM, ICON, and WASM chains.
The checkpoint logic allows for efficient tracking of the last processed height for each chain making relayer more smarter.
This improves the reliability and performance of the relayer by reducing the number of unnecessary RPC queries and improves recovery.
The change auto makes websocket connection optional, supporting RPC only setups.
fixes: #328

why not expose the height saving functionality to the chain providers as well ??

why not expose the height saving functionality to the chain providers as well ??

Why write that many time on disk?
And it is not that fool proof either.

will be reviewed later as it is not major issue now.


Switch macos detection to use SystemVersion.plist

The way Python detects the MacOS version uses the file /System/Library/CoreServices/SystemVersion.plist:
❯ cat /System/Library/CoreServices/SystemVersion.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>ProductBuildVersion</key>
    <string>22D49</string>
    <key>ProductCopyright</key>
    <string>1983-2023 Apple Inc.</string>
    <key>ProductName</key>
    <string>macOS</string>
    <key>ProductUserVisibleVersion</key>
    <string>13.2</string>
    <key>ProductVersion</key>
    <string>13.2</string>
    <key>iOSSupportVersion</key>
    <string>16.3</string>
</dict>
</plist>

Would it be faster and potentially more efficient to use this rather than invoking sw_vers and parsing the output?

Thank you for the suggestion, I think it is a good idea. I can do that myself, but please let me know if you want to try to implement that. 🙃

I love to try and implement it, thanks! I’ll give it a shot this weekend or next weekend.


Comment out the project URLs configured in setup.cfg

In #32 we added defaults for project URLs in setup.cfg. We've since had some feedback that developers don't really know where that information comes from on the napari hub, and how to change it. At the very least, we should comment out these URLs so that plugins don't show information that hasn't been explicitly exposed by the plugin developer.

I rather prefer to add some detailed documentation than remove this. This is one of the core python packaging features.

@Czaki I agree that it's a core feature and we should encourage people to provide these URLs - I added them in the first place! However, what we're finding is that people are not aware of these URLs, and they're not editing them. This is despite clear instructions after creation that you should go and edit these. So I don't think it's a matter of more detailed documentation.
My hope is that we can move more towards conscious and explicit actions from developers to provide appropriate metadata and documentation for their plugins, rather than us providing them with default values. By commenting these values out, developers will be alerted to this lack of metadata on the PyPI project page, their napari hub plugin page and the napari hub preview page. This will allow them to go and make the conscious choice of adding these URLs back in, and considering where they point to, rather than having "complete" metadata they are unaware of.

Good point @DragaDoncila, if this comes with a "plugin completeness" warning of some sort from the hub, I agree with commenting them out.

developers will be alerted to this lack of metadata on the PyPI project page

I worry that they will not notice this. But in general I agree with @brisvag that with Warning on napari hub it may be enough.


Non-root layouts not loaded in v0.21.8

I think there's a bug in v0.21.8. The list of found path segments with _layout.tsx files is incorrect. It includes undefined and [object] strings. I think the fix is to use segment.name instead of segment [edit: and use index instead of index - 1].
--- a/dist/router/create-pages.js
+++ b/dist/router/create-pages.js
@@ -185,10 +185,10 @@ export const createPages = (fn)=>{
     };
     const getLayouts = (spec)=>{
         const pathSegments = spec.reduce((acc, segment, index)=>{
-            if (acc[index - 1] === '/') {
-                acc.push('/' + segment);
+            if (!acc[index] || acc[index] === '/') {
+                acc.push('/' + segment.name);
             } else {
-                acc.push(acc[index - 1] + '/' + segment);
+                acc.push(acc[index] + '/' + segment.name);
             }
             return acc;
         }, [

There should probably be a test case to catch this...

@tylersayshi

I think this patch is missing something. I'm still getting errors. Working on debugging...

index - 1 needed to be index. I edited the diff in my original post above.

Ah, yea, I don't think we have any e2e tests to check nested layouts.
Sorry about this, I can help look into a fix today

#1063

Sorry... @tylersayshi  I think we missed something here. I had to apply this patch to v0.21.9.
diff --git a/dist/router/create-pages.js b/dist/router/create-pages.js
index f4e7afb30f4f1a6c7cf6172692c9dcc95e22e210..bcbf749487dbfd24a190f3157806905f6019af9b 100644
--- a/dist/router/create-pages.js
+++ b/dist/router/create-pages.js
@@ -188,7 +188,7 @@ export const createPages = (fn)=>{
             if (index === 0) {
                 acc.push('/' + segment.name);
             } else {
-                acc.push(acc[index - 1] + '/' + segment.name);
+                acc.push(acc[index] + '/' + segment.name);
             }
             return acc;
         }, [

I wonder if we can write a test for it.

I wonder if we can write a test for it.

Yeah, I assumed https://github.com/dai-shi/waku/blob/main/e2e/21_create-pages_standalone.spec.ts#L36-L39 would catch...
For my error, my layout was two levels deep - so maybe we can reproduce by adding /nested/baz/layout.tsx with a /nested/baz/[id]/view.tsx page route.

 -                acc.push(acc[index - 1] + '/' + segment.name);
 +                acc.push(acc[index] + '/' + segment.name);

This part of the diff I intentionally omitted, it's not correct, but thanks for sharing still because this does help explain the issue.
I'll add a test to replicate the further nested path and make sure layouts are applied there as well. 👀


GithubPRPlanPlugin Max Comment Issue

When the plan to post is more than the max character the pipeline will fail. The error is not very informative. When posting Jenkins only returns ERROR: Creating GitHub comment failed: HTTP/2 422
When running the body manually in verbose mode was I able to determine the actually error was
{
  "message": "Validation Failed",
  "errors": [
    {
      "resource": "IssueComment",
      "code": "unprocessable",
      "field": "data",
      "message": "Body is too long (maximum is 65536 characters)"
    }
  ],
  "documentation_url": "https://docs.github.com/enterprise/3.1/rest/reference/issues#create-an-issue-comment"
}

Proposal

We break up the body txt into multiple posts.
We don't hard fail if the body.txt is over a certain size and just skip the PR posting and echo out that error

Interesting, the code seems to indicate that that should already be happening:
https://github.com/manheim/terraform-pipeline/blob/master/src/GithubPRPlanPlugin.groovy#L170-L171


No stripe_customer() returned

Hi there - firstly, great work on this memberkit!
I've got an issue where your 'customer' => kirby()->user()->stripe_customer() return nothing which leads to an error in the Stripe logs "resource_missing - customer".
Thoughts on why this is?
The Stripe customer id is not being stored in the relevent customer's index.php file when the user is created. In the documentation, the automatic "create stripe useres" hook states: "Creates a stripe customer and store the stripe customer id (stripe_customer) and the root subscription tier name (tier) in the Kirby user information." This doesn't seem to be occuring in my iteration. I'm using the Add-on Usekit.
The document states "Check out the Kirby Add-on Userkit to allow self-registration and updates to kirby users." Not clear to me what this instruction means, but perhaps I'm missing a step here?
Thanks!
*Update:
I also checked the plugin's hooks.php and can see there is the following hook (the first Stripe customer creation step works, but this second update Kirby user hook does not seem to work (an no error is thrown either):
try {

      // UPDATE KIRBY USER - ROOT TIER (INDEX=0)
      kirby()->user($user->email())->update([
        'stripe_customer' => $customer->id,
        'tier' => option('kreativ-anders.memberkit.tiers')[0]['name']
      ]);

    } catch (Exception $e) {

      // LOG ERROR SOMEWHERE !!!
      throw new Exception('Could not update kirby user!');
    }

I can't explain why, but this piece of code in the register.php controller that is part of the kirby-userkit prevented the hook.php code quoted above in the kirby-memberkit plugin from executing properly:
 // SUCCESSFUL
      if (empty($alert) === true) {

        // LOGIN USER
        if($user and $user->login($data['password'])) {
          go();
        }

        $data = [];
      }

First of all: I am sorry!
I did not receive a single notification that new issues have been created, so I was totally unaware until I received a notification from Stripe regarding some changes on the API. 🙄😒

Step by Step

The Stripe customer id is not being stored in the relevent customer's index.php file when the user is created.

This will never be the case since this information will be stored in the customer´s user.txt.

Thoughts on why this is?

Remove the user.login:after hook in your config:
(Just had the same issue and removing was my solution. Surprisingly it happens not all the time. 😵)
'hooks' => [
    'user.login:after' => function ($user, $session) {
      $user->update([
        'lastLogin' => date("m.d.Y")
      ]);
    }
  ],

Even though hooks are great, they can cause a lot of trouble, especially when those hooks access the same object. (For instance the user object by user.login:after and user.create:after hook.) There is already an issue on https://github.com/getkirby/kirby/issues/2828.

The document states "Check out the Kirby Add-on Userkit to allow self-registration and updates to Kirby users." Not clear to me what this instruction means, but perhaps I'm missing a step here?

No steps missed. This means the Memberkit Plug-In does not provide the logic for user registration itself (that´s what Userkit does). What this Plug-In does is to listen to user.create:after hook to create a Stripe user automatically and write the information back to the user.txt.
Stripe-customer: cus_K6V*******
----
Tier: Premium
----
Stripe-subscription: sub_K6V********
----
Stripe-status: active

So you can write your own logic for user registration/creation and the Plug-In should work as well.

Removing that (which prevent auto-login) has solved the entire issue. The auto-login can be moved to execute after the hook.

Yes, either this way or removing the hook user.login:after at all. (I plan to remove from Userkit anyway 🙈)
So I hope my late response did not prevent progress on your side! Are there any open issues?
P.S. feel free to also write on the Kirby´s forum for this Plug-In. At least there I have no notification issues.