Update install_lua_modules.sh

Install packages from torch's rocks repo.
graphicsmagick and csvigo are only available on torch's rocks repo.

torch's luarocks command first uses torch's rocks repository.
Also cudnn on the master branch will not work


bug get response headers with same name

there are a bug in get  header value from a header with same name  header
Server Response:
Content-Encoding:gzip
Content-Type:application/json;charset=UTF-8
Set-Cookie:value=1; Domain=.ivona.com; Expires=Sat, 30-Aug-2036 19:26:33 GMT; Path=/
Set-Cookie:value=2; Domain=.ivona.com; Expires=Sat, 30-Aug-2036 19:26:33 GMT; Path=/
Set-Cookie:value=3; Domain=.ivona.com; Expires=Sat, 30-Aug-2036 19:26:33 GMT; Path=/
window.cordovaHTTP.post(url, { }, { }, function(response) {
var cookies = response.headers["Set-Cookie"];
console.log(cookies);
//this print  only one cookie  not 3
//"value=1; Domain=.ivona.com; Expires=Sat, 30-Aug-2036 19:26:33 GMT; Path=/"
}
//the correct is get all cookies with same name not only first
here the bug:
https://github.com/wymsee/cordova-HTTP/blob/master/src/android/com/synconset/CordovaHTTP/CordovaHttp.java#L123
parsed_headers.put(key, value.get(0));
get  only  first  value  not  all
please fix this bug
PS: this bug occurs in iOS too
@TheKiteEatingTree

Same issue affecting me, I do sugest to report it to
https://github.com/kevinsawicki/http-request
original lib used by cordovaHttp

I got the same issue and it's bugging me.
I'm trying to connect my mobile app to an existing cookie based authentication with multiple "set-cookie" entries in the response headers.

I got a little workaround (for now):
Replace
if ((key != null) && (!value.isEmpty())) {
    parsed_headers.put(key, value.get(0));
}

with
if ((key != null) && (!value.isEmpty())) {
    if (value.size() > 1)
    {
      String tempValue = "";

      for (int i = 0; i < value.size() - 1; i++)
      {
        tempValue += value.get(i);
        tempValue += ",";
      }

      tempValue += value.get(value.size() - 1);

      parsed_headers.put(key, tempValue);
    }
    else
    {
      parsed_headers.put(key, value.get(0));
    }
}

and the multiple key values will be concatenated with a ',' sign.
Problem is that the pased_headers is a HashMap wich as far as i know can not have multiple same keys.


fix(calendar): add disabled attribute & default cursor to disabled days

SDE-842
Description
Adds disabled attribute to disabled days in Calendar, along with the default cursor instead of the pointer
How to test

Go to the Calendar component with disabled days, the day button should have the attribute disabled and the cursor should be default instead of pointer

Screenshots

Before.
After.

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

[ ] codemod is created and showcased in the changeset
[ ] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


Artifact/parameter failure should not be fatal if step/task condition is false

Checklist:

[x] I've included the version.
[x] I've included reproduction steps.
[x] I've included the workflow YAML.
[x] I've included the logs.

What happened:
I have two steps that I would like to run under some condition. The first step creates an artifact that is consumed by the second. When the condition evaluates to false, the second step fails the entire workflow
What you expected to happen:
The workflow should ignore this resolution error and just skip the step.
How to reproduce it (as minimally and precisely as possible):
I've added false conditions to this example:
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: conditional-artifact-passing-
spec:
  entrypoint: artifact-example
  templates:
  - name: artifact-example
    steps:
    - - name: generate-artifact
        template: whalesay
        when: false
    - - name: consume-artifact
        template: print-message
        when: false
        arguments:
          artifacts:
          - name: message
            from: "{{steps.generate-artifact.outputs.artifacts.hello-art}}"

  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [sh, -c]
      args: ["sleep 1; cowsay hello world | tee /tmp/hello_world.txt"]
    outputs:
      artifacts:
      - name: hello-art
        path: /tmp/hello_world.txt

  - name: print-message
    inputs:
      artifacts:
      - name: message
        path: /tmp/message
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["cat /tmp/message"]

The result:
Status:              Failed
Message:             Unable to resolve: {{steps.generate-artifact.outputs.artifacts.hello-art}}

Anything else we need to know?:
Environment:

Argo version:

$ argo version
argo: v2.4.1
  BuildDate: 2019-10-08T23:14:59Z
  GitCommit: d7f099992d8cf93c280df2ed38a0b9a1b2614e56
  GitTreeState: clean
  GitTag: v2.4.1
  GoVersion: go1.11.5
  Compiler: gc
  Platform: linux/amd64

Kubernetes version :

$ kubectl version -o yaml
clientVersion:
  buildDate: "2019-08-19T11:13:54Z"
  compiler: gc
  gitCommit: 2d3c76f9091b6bec110a5e63777c332469e0cba2
  gitTreeState: clean
  gitVersion: v1.15.3
  goVersion: go1.12.9
  major: "1"
  minor: "15"
  platform: linux/amd64
serverVersion:
  buildDate: "2020-01-15T17:47:46Z"
  compiler: gc
  gitCommit: 2c6d0ee462cee7609113bf9e175c107599d5213f
  gitTreeState: clean
  gitVersion: v1.14.8-gke.33
  goVersion: go1.12.11b4
  major: "1"
  minor: 14+
  platform: linux/amd64

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Just to add a little information, I am seeing this issue on Argo v2.7.0 and using DAG instead of steps.
Not sure if that's helpful, but I was about to file an issue myself.

I have same issue. My gitlab-pipeline workflow failed when skipped clone-repository step. Because build-image step can't resolve artifacts from clone-repository step, but build-image should be skipped and workflow should not failed.
              templates:
              - name: gitlab-pipeline
                steps:·
                - - name: prepare-environment
                    template: prepare-environment
                    arguments:
                      parameters:
                      - name: message
                        value: "{{workflow.parameters.message}}"
                - - name: clone-repository
                    template: clone-repository
                    when: "{{steps.prepare-environment.outputs.parameters.event-name}} == tag_push"
                    arguments:
                      artifacts:
                      - name: cloudevent
                        from: "{{steps.prepare-environment.outputs.artifacts.cloudevent}}"
                      - name: environment
                        from: "{{steps.prepare-environment.outputs.artifacts.environment}}"
                - - name: build-image
                    template: build-image
                    when: "{{steps.prepare-environment.outputs.parameters.event-name}} == tag_push"
                    arguments:
                      artifacts:
                      - name: environment
                        from: "{{steps.prepare-environment.outputs.artifacts.environment}}"
                      - name: repository
                        from: "{{steps.clone-repository.outputs.artifacts.repository}}"

Fixed by #2657. Should be on the next release

I submitted the same workflow after updating to 2.7.2 and I am still getting the issue.
Name:                artifact-passing-dqxhs
Namespace:           kepler-feature-eks
ServiceAccount:      argo
Status:              Error
Created:             Mon Apr 13 11:42:47 -0600 (13 seconds ago)
Started:             Mon Apr 13 11:42:47 -0600 (13 seconds ago)
Finished:            Mon Apr 13 11:42:47 -0600 (13 seconds ago)
Duration:            0 seconds

STEP                       TEMPLATE       PODNAME  DURATION  MESSAGE
 ⚠ artifact-passing-dqxhs  main-dag
 ├-⚠ consume-artifact      print-message                     Unable to resolve: {{tasks.generate-artifact.outputs.artifacts.hello-art}}
 └-○ generate-artifact     whalesay                          when 'false' evaluated false

This is the workflow:
# This example demonstrates the ability to pass artifacts
# from one step to the next.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: artifact-passing-
spec:
  entrypoint: main-dag
  serviceAccountName: argo
  templates:
  - name: main-dag
    dag:
      tasks:
        - name: generate-artifact
          template: whalesay
          when: false
        - name: consume-artifact
          dependencies: [generate-artifact]
          when: false
          template: print-message
          arguments:
            artifacts:
            - name: message
              from: "{{tasks.generate-artifact.outputs.artifacts.hello-art}}"

  - name: whalesay
    container:
      image: docker/whalesay:latest
      command: [sh, -c]
      args: ["sleep 1; cowsay hello world | tee /tmp/hello_world.txt"]
    outputs:
      artifacts:
      - name: hello-art
        path: /tmp/hello_world.txt

  - name: print-message
    inputs:
      artifacts:
      - name: message
        path: /tmp/message
    container:
      image: alpine:latest
      command: [sh, -c]
      args: ["cat /tmp/message"]

@sudermanjr Will take a look today

@sudermanjr I wasn't able to duplicate this on 2.7.2 – the workflow succeeded as expected for me. Could you provide your workflow-controller logs?

In fact, there is a test case with the same Workflow to ensure that it doesn't fail:
https://github.com/argoproj/argo/blob/master/workflow/controller/dag_test.go#L55-L113/2bc0bd9c85f34d63902fbacec93500feee896bf4/workflow/controller/dag_test.go#L44

Yeah, that's really strange. I'll do some more digging on my end and see if there's something I missed when I updated.
Here's the logs pertaining to that workflow
└─ k logs argo-kepler-feature-eks-workflow-controller-8d958bbcc-8ctdc  | grep artifact-passing
time="2020-04-13T17:42:47Z" level=info msg="Processing workflow" namespace=kepler-feature-eks workflow=artifact-passing-dqxhs
time="2020-04-13T17:42:47Z" level=info msg="Updated phase  -> Running" namespace=kepler-feature-eks workflow=artifact-passing-dqxhs
time="2020-04-13T17:42:47Z" level=info msg="DAG node {artifact-passing-dqxhs artifact-passing-dqxhs artifact-passing-dqxhs DAG main-dag nil    Running   2020-04-13 17:42:47.037613039 +0000 UTC 0001-01-01 00:00:00 +0000 UTC   <nil> nil nil [] []} initialized Running" namespace=kepler-feature-eks workflow=artifact-passing-dqxhs
time="2020-04-13T17:42:47Z" level=info msg="All of node artifact-passing-dqxhs.generate-artifact dependencies [] completed" namespace=kepler-feature-eks workflow=artifact-passing-dqxhs
time="2020-04-13T17:42:47Z" level=info msg="Skipped node {artifact-passing-dqxhs-106419550 artifact-passing-dqxhs.generate-artifact generate-artifact Skipped whalesay nil    Skipped artifact-passing-dqxhs when 'false' evaluated false 2020-04-13 17:42:47.106604485 +0000 UTC 2020-04-13 17:42:47.106604485 +0000 UTC   <nil> nil nil [] []} initialized Skipped (message: when 'false' evaluated false)" namespace=kepler-feature-eks workflow=artifact-passing-dqxhs
time="2020-04-13T17:42:47Z" level=info msg="Workflow update successful" namespace=kepler-feature-eks phase=Running resourceVersion=12285835 workflow=artifact-passing-dqxhs
time="2020-04-13T20:44:47Z" level=info msg="Processing workflow" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:47Z" level=info msg="Updated phase  -> Running" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:47Z" level=info msg="DAG node {artifact-passing-2n4ss artifact-passing-2n4ss artifact-passing-2n4ss DAG main-dag nil    Running   2020-04-13 20:44:47.15127172 +0000 UTC 0001-01-01 00:00:00 +0000 UTC   <nil> nil nil [] []} initialized Running" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:47Z" level=info msg="All of node artifact-passing-2n4ss.generate-artifact dependencies [] completed" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:47Z" level=info msg="Skipped node {artifact-passing-2n4ss-375748800 artifact-passing-2n4ss.generate-artifact generate-artifact Skipped whalesay nil    Skipped artifact-passing-2n4ss when 'false' evaluated false 2020-04-13 20:44:47.151387614 +0000 UTC 2020-04-13 20:44:47.151387614 +0000 UTC   <nil> nil nil [] []} initialized Skipped (message: when 'false' evaluated false)" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:47Z" level=info msg="Workflow update successful" namespace=kepler-feature-eks phase=Running resourceVersion=12347532 workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Processing workflow" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="All of node artifact-passing-2n4ss.consume-artifact dependencies [generate-artifact] completed" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="DAG outbound nodes of &NodeStatus{ID:artifact-passing-2n4ss-375748800,Name:artifact-passing-2n4ss.generate-artifact,DisplayName:generate-artifact,Type:Skipped,TemplateName:whalesay,TemplateRef:nil,Phase:Skipped,BoundaryID:artifact-passing-2n4ss,Message:when 'false' evaluated false,StartedAt:2020-04-13 20:44:47 +0000 UTC,FinishedAt:2020-04-13 20:44:47 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[],OutboundNodes:[],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:,ResourcesDuration:ResourcesDuration{},} are [artifact-passing-2n4ss-375748800]" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Skipped node {artifact-passing-2n4ss-2947200819 artifact-passing-2n4ss.consume-artifact consume-artifact Skipped print-message nil    Skipped artifact-passing-2n4ss when 'false' evaluated false 2020-04-13 20:44:48.22488518 +0000 UTC 2020-04-13 20:44:48.22488518 +0000 UTC   <nil> nil nil [] []} initialized Skipped (message: when 'false' evaluated false)" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Outbound nodes of artifact-passing-2n4ss set to [artifact-passing-2n4ss-2947200819]" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="node &NodeStatus{ID:artifact-passing-2n4ss,Name:artifact-passing-2n4ss,DisplayName:artifact-passing-2n4ss,Type:DAG,TemplateName:main-dag,TemplateRef:nil,Phase:Running,BoundaryID:,Message:,StartedAt:2020-04-13 20:44:47 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[artifact-passing-2n4ss-375748800],OutboundNodes:[artifact-passing-2n4ss-2947200819],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:,ResourcesDuration:ResourcesDuration{},} phase Running -> Succeeded" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="node &NodeStatus{ID:artifact-passing-2n4ss,Name:artifact-passing-2n4ss,DisplayName:artifact-passing-2n4ss,Type:DAG,TemplateName:main-dag,TemplateRef:nil,Phase:Succeeded,BoundaryID:,Message:,StartedAt:2020-04-13 20:44:47 +0000 UTC,FinishedAt:2020-04-13 20:44:48.225108443 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[artifact-passing-2n4ss-375748800],OutboundNodes:[artifact-passing-2n4ss-2947200819],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:,ResourcesDuration:ResourcesDuration{},} finished: 2020-04-13 20:44:48.225108443 +0000 UTC" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Checking daemoned children of artifact-passing-2n4ss" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Updated phase Running -> Succeeded" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Marking workflow completed" namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Checking daemoned children of " namespace=kepler-feature-eks workflow=artifact-passing-2n4ss
time="2020-04-13T20:44:48Z" level=info msg="Workflow update successful" namespace=kepler-feature-eks phase=Succeeded resourceVersion=12347534 workflow=artifact-passing-2n4ss

I can't paste the whole log right now because I have other stuff running on that controller.

I re-deployed my workflow controller and it worked.
Not sure how I got into that state, but I'm good now. Thanks for looking!

Not sure how I got into that state, but I'm good now. Thanks for looking!

Woo! Glad to hear

Not sure how I got into that state, but I'm good now. Thanks for looking!

Woo! Glad to hear

For anyone reading this in the future, I have multiple controllers in multiple namespaces. It seems I hadn't isolated them as much as I though I had, and a different-versioned controller was updating the workflow.


UI: Refactor platform text handling in journey cards

TL;DR
Improved platform number display by extracting information from stop names instead of relying on platform property.
What changed?

Changed platformText type from Char to String to support full platform descriptions
Added new platformNumber field to store standalone platform values
Created regex patterns to extract platform information from stop names
Added unit tests to verify platform text and number extraction
Updated UI components to handle both platform text and number separately
Removed the buildPlatformText helper function as it's no longer needed

Screenshots
No platform info for Bus, there fore it's skipped.
Journey Card

Default
Expanded

Ferry , Train
Train with platform no. 18
Ferry with Wharf and Side, siaplyed correctly.

Train
Ferry

Why make this change?
The previous implementation relied on a single character platform property which was often incomplete or missing. By extracting platform information from stop names, we can provide more accurate and detailed platform information to users, improving their journey planning experience.

#325  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ksharma-xyz and the rest of your teammates on  Graphite

Merge activity

Nov 9, 12:40 AM EST: A user started a stack merge that includes this pull request via Graphite.

https://github.com/users/ksharma-xyz/projects/1/views/1?pane=issue&itemId=84889665


Load features faster

Closes #4312
From 280ms to 39.458984375 ms
Test URLs
All
Screenshot
None

Title good?


是否可以支持go get

既然现在不依赖gvp/gvm了，是不是可以改下目录结构来支持go get
只要设定好了GOPATH, 直接
go get -u github.com/gonet2/{agent,game}
就可以clone并安装好agent和game
方便快速的体验

可以，我尽快修改结构

@en 已经完全改为标准layout

@xtaci 路径貌似有问题，不知道这些影不影响ci那边
ys@archlinux ~ $ echo $GOPATH
/home/ys/go
ys@archlinux ~ $ go get -u github.com/gonet2/{agent,game,snowflake}
package agent/client_handler: unrecognized import path "agent/client_handler" (import path does not begin with hostname)
package agent/misc/packet: unrecognized import path "agent/misc/packet" (import path does not begin with hostname)
package agent/pb: unrecognized import path "agent/pb" (import path does not begin with hostname)
package agent/types: unrecognized import path "agent/types" (import path does not begin with hostname)
package agent/utils: unrecognized import path "agent/utils" (import path does not begin with hostname)
package game/client_handler: unrecognized import path "game/client_handler" (import path does not begin with hostname)
package game/misc/packet: unrecognized import path "game/misc/packet" (import path does not begin with hostname)
package game/proto: unrecognized import path "game/proto" (import path does not begin with hostname)
package game/registry: unrecognized import path "game/registry" (import path does not begin with hostname)
package game/types: unrecognized import path "game/types" (import path does not begin with hostname)
package snowflake/etcdclient: unrecognized import path "snowflake/etcdclient" (import path does not begin with hostname)
package snowflake/proto: unrecognized import path "snowflake/proto" (import path does not begin with hostname)

go get 还是有点问题，但是编译没有问题。

go get没有问题，只是需要把所有<"game*>和<"agent*>开头的包引用全替换成<"github.com/gonet2/game*>和<"github.com/gonet2/agent*>


feat(asset): added support for IncludeOnlyTimeRangeData

Pull Request
🤨 Rationale
We need the ability to add a flag so the service knows that it needs to query only data in the interval.
👩💻 Implementation
Updated data links and runQuery method to take into consideration isQueryScoped
🧪 Testing
Added tests for the flag
✅ Checklist

[x] This PR has a title that follows the commit message format.

One more thing I find strange is that he user doesn't know when they are with timerange only selected...
We should probably have some sort of possibility to show that this is active (maybe via a global variable) and not render the datalinks at all when you are with timerange only active

:tada: This PR is included in version 3.37.0 :tada:
The release is available on:

v3.37.0
GitHub release

Your semantic-release bot :package::rocket:


Links in scully blogs do not respect Ctrl Click

🐞 Bug report
Description
It seems for blog posts, scully takes over onclick behaviour in links, and if scully is aware of the route, it overrides the link navigation via this.router.navigate.
However, this means that ctrl-click to open link in new tab is not respected. target="_blank" is not respected either.  Also I notice sometimes when user presses back, their location in the article does not remain the same either.
The relevant code is here: https://github.com/scullyio/scully/blob/179650fc26b8951e0eaedf9edc0a0f6b9a49fc8b/libs/ng-lib/src/lib/scully-content/scully-content.component.ts#L194
🔬 Minimal Reproduction
Create angular scully app with blog post that links to a route in the app that scully is aware of.
💻Your Environment
Angular Version:
15
Scully Version:
2.1.41

Is this upgradeToRouteLink feature needed anymore btw? My links seem to work fine without it, and does not reload the page if I link within the angular app.

related to https://github.com/scullyio/scully/issues/1615 as well. I think there should be an Input to disable the scully routing upgrade for all links...

@hisham, without the upgrade, your links don't stop working. However, they will do a full-page refresh navigation.
I'm unsure that if you use a [route-link]='somelink' one can do the right click either?

Hi @SanderElias - thanks for the response. Ok, yes I do see the page refresh navigation when I remove Scully's onclick handler. While not having page refresh is ideal, to be honest, it's not so bad.
To answer your second question, yes angular's routerLink directive does respect ctrl-click. Looks like they supported this since 2016 - see https://github.com/KiaraGrouwstra/angular/commit/1ac9dda93d01e5e61a3af32a9c596e6f26d50b00 for the fix they implemented to support this. They catch the mouse event and if meta or ctrl key was pressed at same time, they let the browser do its thing and do not handle anything. So I guess Scully can do that as well maybe.
However, another issue I found is when I click on one of the links in the blog post and then go back, the scroll position in the original blog post page is not preserved. I haven't spent the time investigating why but I suspect it's due to how the scully-content component dynamically inserts blog content.

yeah I'm pretty sure scroll positioning is caused by scully's dynamic blog post content insertion. It seems to be done in a non-angular way, so maybe that's why angular is unable to preserve scroll history for blog posts. Scully might need to remember scroll positions itself like what is proposed here: https://dev.to/johncarroll/angular-how-to-refresh-scroll-position-on-back-5e1b


Charger.set_dynamic_charger_circuit_current extended

Updated code for how to set dynamic current limit on circuit level. Affects two methods:
Charger.set_dynamic_charger_circuit_current
New optional parameter, timeToLive has been added.
Circuit.set_dynamic_current
New optional parameter, timeToLive has been added.
timeToLive specifies, in minutes, the validity of the new current limit.
If timeToLive is set to zero, then the setting is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent
If timeToLive is omitted, then the old code will be executed. This means that the new current limit will be valid until the next time it is changed, a new charging sessions starts, or the charger is restarted, whichever comes first.
API documentation has been updated accordingly

Hi! This looks like a nice an simple PR but there some unnecessary repetition and a print statement.

Hi! This looks like a nice an simple PR but there some unnecessary repetition and a print statement.

Thanks for feedback. It was clumsy to leave the print statements. I will remove them.
Regarding the repetition, I take it you are referring to the old code I left in Circuit.set_dynamic_current. I was in two minds here. The two API calls don't work exactly in the same way so I kept the old one for backwards compatibility. My thinking was that perhaps someone is using this function under the assumption that the current limit will be reset whenever a car is connected. In the new API, timeToLive = None has the same effect as timeToLive = 0, which means that the setting survives car connect/disconnect and is valid until changed again.
An alternative is of course to always use the new API. Perhaps this is the best option, and clarify in the documentation how the call works so there are no surprises.

I would prefer to just call the new API, but I am not sure how you came to the conclusion that timeToLive = 0 is the same as calling the old API, I see nothing in the documentation that indicates that it is so:
https://developer.easee.cloud/reference/post_api-sites-siteid-circuits-circuitid-dynamiccurrent

This commit:

Removed print statements
Removed call to /api/sites/siteId/circuits/circuitId/settings

To summarize the new behavior implemented in this branch:
Updated code for setting dynamic current limit on circuit level. Affects two methods:
Charger.set_dynamic_charger_circuit_current
New optional parameter, timeToLive has been added.
Circuit.set_dynamic_current
New optional parameter, timeToLive has been added.
timeToLive specifies, in minutes, the validity of the new dynamic current.
If timeToLive is set to zero or omitted, then the new dynamic current is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent
The documentation has been updated accordingly.

timeToLive specifies, in minutes, the validity of the new dynamic current.
If timeToLive is set to zero or omitted, then the new dynamic current is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent

Again, where are you seeing this being documented?

timeToLive specifies, in minutes, the validity of the new dynamic current.
If timeToLive is set to zero or omitted, then the new dynamic current is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent

Again, where are you seeing this being documented?

What I mean is that I have updated the HTML files to reflect the changes I have made to the method call.

timeToLive specifies, in minutes, the validity of the new dynamic current.
If timeToLive is set to zero or omitted, then the new dynamic current is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent

Again, where are you seeing this being documented?

What I mean is that I have updated the HTML files to reflect the changes I have made to the method call.

Is my question not clear?
You state "If timeToLive is set to zero, then the setting is valid until the next time it is changed". I am asking you, where did you get that information from? The API documentation that Easee provides states no such thing as far as I am able to see. If it is the case that you have found it out by trial and error, that is completely fine, but if that is the case I want to contact Easee to verify that this is actually something they intentionally support, otherwise it could break in any if their next updates. I just want to make sure we are not doing anything based on assumptions here.
I like your intentions here, do not get me wrong, I just want to make sure we do it the right way.
PS. The HTML files are auto-generated, if you want to change what is written there, you need to change the comment first in each function in the code itself, that is where that information is collected from. Any changes you do directly in the HTML-files will be overwritten as part of the release process.

timeToLive specifies, in minutes, the validity of the new dynamic current.
If timeToLive is set to zero or omitted, then the new dynamic current is valid until the next time it is changed, or the charger is restarted. This call is used: https://api.easee.cloud/api/sites/siteId/circuits/circuitId/dynamicCurrent

Again, where are you seeing this being documented?

What I mean is that I have updated the HTML files to reflect the changes I have made to the method call.

Is my question not clear? You state "If timeToLive is set to zero, then the setting is valid until the next time it is changed". I am asking you, where did you get that information from? The API documentation that Easee provides states no such thing as far as I am able to see. If it is the case that you have found it out by trial and error, that is completely fine, but if that is the case I want to contact Easee to verify that this is actually something they intentionally support, otherwise it could break in any if their next updates. I just want to make sure we are not doing anything based on assumptions here. I like your intentions here, do not get me wrong, I just want to make sure we do it the right way.
PS. The HTML files are auto-generated, if you want to change what is written there, you need to change the comment first in each function in the code itself, that is where that information is collected from. Any changes you do directly in the HTML-files will be overwritten as part of the release process.

OK, I misunderstood your question. The statement about how "timeToLive = 0" is interpreted is coming from Easee. I asked the question in their forum and here is the response from the admin: https://developer.easee.cloud/discuss/618402c760630f0494a064f1

Ok, good, I guess that is enough. But can you please change the documentation as I indicated above?

Thanks @perjarne, this change is now included in the the latest release.


asciidoctor-pdf failed to parse a paragraph with predefined attribute for character replacement

I got the failed parse error on the following paragraphs with "predefined attribute". The html is rendered fine with asciidoctor, but the pdf rendering is wrong with asciidoctor-pdf.

A fixed parameter of the CLIC (CLICINTBITS) is how many total bits
are present in the clicintcfg registers , with 2 {lt}=
CLICINTBITS {lt}= 8.  The implemented bits are kept left-justified
in the most-significant bits of each 8-bit clicintcfg[__i__]
register, with the lower unimplemented bits treated as hardwired to 1.
These configuration bits are interpreted as mode, level, and
priority depend on the setting of the cliccfg register as
described below.
If the nmbits + nlbits {gt} CLICINTBITS, then the lower bits of
the 8-bit interrupt level are assumed to be all 1s.  If nlbits {lt}
8, then the lower bits of the 8-bit interrupt level are assumed to be
all 1s.  The following table shows how levels are encoded in either of
these two cases.
In M/S/U harts, if cliccfg.nmbits{lt} 2 then all interrupts are
either M-mode or S-mode, and all are inaccessible to U-mode.

This is not the correct use of the lt attribute. That attribute is only to be used when you need to reference the raw, unescaped character, which is usually never.
AsciiDoc already escaped XML special characters by default. So there's nothing special you need to do to escape them. You just need to escape the arrow:
with 2 \<= CLICINTBITS \<= 8

You could also write it as:
with 2 <= CLICINTBITS <= 8

The only reason this works when converting to HTML is because the browser is being extremely forgiving. The source generated from your markup is still technically incorrect.

Thanks for the answer. I understand it now.


QueryBuilder returns null even if array is expected

There is an issue in TS typings or even Objection QueryBuilder.
https://github.com/Vincit/objection.js/blob/master/lib/queryBuilder/QueryBuilder.js#L1431
If the query gets nothing from DB it returns null instead of empty array.
Have you plan to fix this behavior?

It returns null only in case a single item is queried (findById, findOne, first). Those should be correctly typed.


Support document symbol psl 7

Motivation
(Write your motivation for proposed changes here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Share your test plan here. If you changed code, please provide us with clear instructions for verifying that your changes work.)


Added Web Vitals

Hi @paulirish
Please check this I added Web Vitals to DevTools Extensions > Performance section
Thanks

hey praveen.
thanks for the contribution
the repo is mostly about things for the chrome devtools product or the protocol.  the CWV isn't related too close.
the second kinda is but apparently its gone now.
cheers

hey praveen.
thanks for the contribution
the repo is mostly about things for the chrome devtools product or the protocol.  the CWV isn't related too close.
the second kinda is but apparently its gone now.
cheers

No problem @paulirish :)


BUG: Fixed Format Ruler

I was just playing around with the new fixed format stuff and I think I found a small bug in the ruler not displaying in a certain situation.  So line 1 of the code has an H spec.  Line 2 has an F spec.  The ruler is not showing on line 2.  It will show on line 3.  If I put a blank line after the H spec it will display the ruler.  Also the Ctrl+Shift+F4 won't work on the F spec as well unless you put the blank line between it.   If I put a blank line before the H spec and leave no blank line between the H and F spec it will work.  I'm not getting and ruler for the H spec which might be by design.
     H DFTACTGRP(*NO) ACTGRP(*CALLER)
     FCRTSQLXFMNCF   E             WORKSTN INDDS(Indicators)
     D System_Table_Schema...
     D                 S             10

Also looked at your PR.  I guessing I and O specs aren't supported yet (or not planned) and I understand why (either way) since you can have two varieties of these.  I think if you really wanted to implement it you could look at position 7 and/or 17 on the I specs and see its not blank that's the equivalent of an IPI in SEU,  If those are blank then it's a IPJ.
On the O specs position 7 and/or 17 not blanks than it's a IPO spec from SEU.  If it is blank than it's a IPP spec in SEU.
Those might not be the only scenarios but those are pretty common.
I-Spec Example
     ICUST      NS
     I                                  1    1  STATUS
     I                                  2    8 0CUSNO

O-Spec Example
     OQSYSPRT   E   N21      HEADER         1
     O         AND  N41
     O                       CUSNO               75


fix: docker build error for missing spacy module

Code Pull Requests
Please provide the following:

a clear explanation of what your code dose
if applicable, a reference to an issue
a reproducible test for your PR (code, model definition and data sample)

Fixes Issue #541
The change updated the Dockerfile build instructions to reference the recently create requirements_text.txt file when install python dependencies for ludwig.
This the docker build log file with the change:
successful_docker_build_fix_spacy.txt

While running some examples, realized that the remaining requirements_[audio, image, ...].txt are required for the docker image to support full ludwig functions.

Thanks


Blockquote is not working with adaptive card

I am currently using blockquote for differentiating few chatbot response from others. Its working perfectly. Now I got requirements to implement similar thing for adaptive cards.
I tried all possible ways and nothing worked. Is there any way to highlight or differentiate few adaptive card responses from others?
If so, please provide help on it. If not, please implement the functionality or capability to it.
I want response like below in Teams
 This is sample message wanna to highlight
Channel I am using is 'MS Teams'

@srinutamada Can you confirm what platform you're seeing this behavior on (Android, iOS, Desktop)?

I tested in Teams from Mobile (Android) and Desktop (Windows-10) . In both places the chatbot behaved same.

This is not working from Adaptive cards. It is working fine for normal responses.

Per current spec block quote is not supported. We will revisit whether we want to add this support as part of our larger discussion surrounding markdown. Text Features


Hypervisor support for MNO clusters

It would be nice to have the ability to host workers from MNO clusters in hypervisors.

Proof of concept working with 1 virtual worker.

Generate Inventory with no workers and HV turned on
update workers count and allocation_node_count
copy {workers count} entries from [hv_vm]  to [workers]
update mac_address to network_mac
code changes to handle missing lab_mac (vms won't have a lab_mac)
added libvirt vendor definition to boot-iso role

Working on generating a patch to handle this and how to work around having to copy workers from hv_vm to worker inventory sections.
Working on being able to do more workers (this is related to handling lab mac properly)


Was good while it lasted

It won't sync as of August 3rd ERROR: Failed to resolve: com.github.Binary-Finery:Bungee:master-SNAPSHOT

Please use version '2.0', instead of 'master-SNAPSHOT'
Sorry for the inconvenience.


Adding maxLength, minLength to outputted swagger, if a property is a …

…string with max or min attributes.

thanks


Add grid item border to timetable grid view

Overview
The current timetable grid view lacks border lines. We need to add these lines to match the design specifications.

Links

Code: https://github.com/DroidKaigi/conference-app-2024/blob/27ea36f1ae39693bbdb51c4d90e2a126551c8fc0/feature/sessions/src/commonMain/kotlin/io/github/droidkaigi/confsched/sessions/TimetableScreen.kt#L91
Design: https://www.figma.com/design/XUk8WMbKCeIdWD5cz9P9JC/DroidKaigi-2024-App-UI

🖐

Thanks! Assigned 👍

@risako070310 Are you still up for this? 👀

@takahirom I am currently working on this issue here. Please give a little more time.

@takahirom
I think someone do this issue in another commitment. Now, may I close this issue?

Sorry, I didn't notice this change. 🙇


upgrade(react): ^0.14.0 -> ^15.0.0

Current coverage is 70.88%

Merging #700 into master will not affect coverage as of 972cd68

@@            master    #700   diff @@
======================================
  Files           12      12
  Stmts           79      79
  Branches         0       0
  Methods          0       0
======================================
  Hit             56      56
  Partial          0       0
  Missed          23      23

Review entire Coverage Diff as of 972cd68

Powered by Codecov. Updated on successful CI builds.


Add minor copy changes to tool body

Rename "unassigned" to "Ready to Deliver Restaurants"
Add overarching text on the hospitals side "Recipients" (above name, time, fulfillment)
Add label "Amount" above the amount column

Closes: https://github.com/bocoup/blocks-capacity-planner/issues/40
The other changes requested in the issue are handled in other PRs.

Looks reasonable to me.


Update the tray's Debian package

This is really important and something that is going to be expected. We cannot have the Launcher be the only way people can install the Tray. First off we're going to not have the Launcher involved in the System Administrator documentation at all. To be able to do this, we need a Debian package and a tarball distribution.

Debian package is done.


Add possibility to append to existing file for DataWriter / ctapipe-process

Please describe the use case that requires this feature.
The current processing on the GRID runs multiple ctapipe-process processes for multiple input files and then merges the resulting small files. This is done because the jobs would other wise be to short to be efficient with the GRID job submission system.
It would be more efficient to not process and then merge but to directly append to a single output file.
Describe the solution you'd like
Add possibility to DataWriter and  ctapipe-process to append to an existing outputfile.
Alternatives considered
Create a tool / modify ctapipe-process to directly run on multiple input files.

To be clear: I assume you don't mean simultaneous writing from many jobs to one, as that is what we do on the grid, but rather within one grid job  allowing multiple input files.
Really this has nothing to do with the grid processing, just more about allowing multiple EventSources to be chained (like itertools.chain)  and have DataWriter correctly write the configuration data when the input changes.   Mainly that means just to  re-run DataWriter._setup_outputfile() when the obs_id changes or something.

Really this has nothing to do with the grid processing,

Technically no, but this is where the motivation comes from.

DataWriter on it's own doesn't know about input files, only the "event" structure in memory, but it currently assumes that no "header" info changes event-to-event.

Yes, which is why it might be easier to just support running ctapipe-process multiple times, with the same output file and introduce an --append option to not overwrite / require non-existence of the output file


unsubscribeAll potentially not working

Using the SDK version 1.0.1 and the following code:
public void unsubscribeNotifications() {
    PushNotifications.start(getApplicationContext(), Constants.BEAM_INSTANCE_ID);
    PushNotifications.unsubscribe("users."+String.valueOf(DataManager.getInstance().getUserID()));
    PushNotifications.unsubscribeAll();
}

We got a customer report that the device was not being unsubscribed from the particular user id, nor from all the others after PushNotifications.unsubscribeAll().
Possible multiple calls to the PushNotifications.start?

I have a similar issue, PushNotifications.unsubscribeAll() is not working. I also have multiple calls to PushNotifications.start
At the moment I'm using PushNotifications.unsubscribe(interest) which is working.

I can confirm PushNotifications.unsubscribeAll(); is not working on v1.0.1.
I'm calling PushNotifications.start() only once.
Possibly this https://github.com/pusher/push-notifications-android/pull/60 fixes it.


Update tlp-clear-email-template.html for 2024

Needed to update the year

Covered in Update to Sendgrid and TLP Clear Template


Export ALL function

Export ALL function - export in DAMS directory format

see https://github.com/attogram/DAMS/

Issue closed - OTE v1 branch closed.   All new development on OTE v2.


v1.0.2 actually has the "An error occurred communicating with Mopé. Please try again later." problem!

Hi there,
Thank you so much for building this plugin. I'd like to inform you that v1.0.1 is more stable than v1.0.2. After my partner upgraded to v1.0.2 from v1.0.1, he started getting this error, "An error occurred communicating with Mopé. Please try again later." Luckily, I had the previous version stored on my PC, so when I downgraded to it, the payment gateway started working again.
By the way, if I wanted to make a donate select box, could I use some part of this plugin? For instance, something like this:
<select id="donate" onchange="mopeDonate()">
<option value="10.00">10 SRD</option>
<option value="20.00">20 SRD</option>
<option value="30.00">30 SRD</option>
</select>
<script>
function mopeDonate(){
var api = '';
var amount = '';
var description = '';
var currency = '';
window.location = "https://api.mope.sr/api/"+api+amount+description+currency;
}
</script>

If you have something ready, please hook me up; I'd very much appreciate it. Keep up the awesome work! <3

Hey @MrAnssaien , I'll take a look. Do you mind providing some more background as to when this error occurs?
You should be able to see the reason for failure inside of the order status, that should help me figure what's going on.

Yeah, sure. With v1.0.2, as soon as I filled in the blanks on the checkout page, and I clicked "place order", I saw the error that was supposed to be fixed, which was ironic, considering that, like I said before, when I downgraded to 1.0.1, everything was fine. I also remember changing the timeout value for some reason. Could that be the problem?

I'll run some tests in my dev environment and issue a fix if needed tonight. Thanks for reporting the issue!

Don't mention it, man. Peace.

@MrAnssaien I've put up a bug fix for the above issue.
Seems like wp_remote_retrieve_response_code() doesn't return an integer, and so the comparison failed.
I'll be pushing a new release in a few minutes - sorry about the inconvenience.


add e2e environment information into DEVELOPMENT.md

Description of the change:
This PR adds Minikube and Kind to development requirements since it's needed for running e2e tests.
Motivation for the change:
When I follow the development document to run the e2e tests, I found Minikube or an existing Kind cluster is required.
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/retest


Create an example in node.js of PartiQL and pagination

Create an example of doing pagination with PartiQL in the Node.js/WorkingWithPartiQL directory.

This issue is closed with the merge,

I am getting errors with this code.
/usr/local/bin/node /Users/kirkcon/GitHub/aws-dynamodb-examples/DynamoDB-SDK-Examples/node.js/WorkingWithPartiQL/paginated-all-data.js
/Users/kirkcon/GitHub/aws-dynamodb-examples/DynamoDB-SDK-Examples/node.js/WorkingWithPartiQL/paginated-all-data.js:18
let response = await dbclient.executeStatement(params);
SyntaxError: await is only valid in async functions and the top level bodies of modules

Now the async is saying it is not a function. It needs a ; at the end of the "let params = { }" line.
Though even once I get this to run, it does now show data of any table I connect it to and it is an endless loop.
----------- start of page ---------------
{}
----------- start of page ---------------
{}
----------- start of page ---------------
{}
What am I doing wrong?

Not quiet sure, however on my local system 14., 16.x and on Lambda function with runtime 14.x I was able to get the response. Yes the ";" is missed I've added that and checked it.


Improving type safety of KMerge.Heap.newMutableHeap

Rather than returning a Maybe a when creating a new mutable heap from an input list ([]), instead require that the input be NonEmpty and always be able to return an a value in the result tuple. This pushes the check for emptiness one level up in the computational logic, requiring the caller of newMutableHeap to have witnessed the non-emptiness of the function's input.
Type signature change (constraints removed for clarity):
newMutableHeap :: [a]        -> m (MutableHeap (PrimState m) a, Maybe a)
newMutableHeap :: NonEmpty a -> m (MutableHeap (PrimState m) a,       a)

This looks pretty reasonable.


(chore) upgrade to rc5

update dependencies
add appModule,
fix bootstrap
remove boilerplate from inner components

I signed it!

I offer to make another PR where github route will be pulled to its own module, with router async loading of this module and child routes, however since this is webpack based and router has dependency on SystemJS loader it will require upgrading to webpack 2 (2.1.beta.20, and adding a runtime of System polyfill (System.js), anyone intrested in this?

@nadavsinai thnx for the PR! I would gladly merge it but there are number of un-related changes in there and it is hard to see what is strictly needed for RC5. Could you please revert all the non-essential parts? Also, please don't change naming / formatting in this PR - we can discuss those in a separate issue / PR.
Would you be willing to make the above changes so I can merge this one?

This looks good now! I will squash while merging. Thnx!


don't import the quic-clients for the self integration test

This should speed up our CI build quite a bit.

Codecov Report

Merging #1575 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1575      +/-   ##
==========================================
- Coverage   87.69%   87.66%   -0.03%
==========================================
  Files          95       95
  Lines        6127     6127
==========================================
- Hits         5373     5371       -2
- Misses        535      537       +2
  Partials      219      219

Impacted Files
Coverage Δ

session.go
73.53% <0%> (-0.34%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 257c473...13b4781. Read the comment docs.


gunzip, gzip modules missing.

Need modules to handle .tar.gz compressed files.

pull request #38 merged.

pull request #38 merged.


CAN Bus Forwarding

Nice work, everyone. Was wondering if you have considered integrating the ability to forward messages over CAN (e.g., using the COMM_FORWARD_CAN byte) for communication with multiple VESCs. Or is this something I missed?

Hi Justin,
Personally, I haven't look at this. I just took a quick look at the VESC documentation, and I agree that this would be a useful and fit well within the scope of PyVESC. Unfortunately I haven't worked with CAN-BUS before, and I'll be pretty busy over the next couple months, so I don't think that I'd be the right person to implement this. If someone else was inclined to implement this, I'd be more than happy to review and merge it into PyVESC though!
I'm going to mark Issue #8 as an open feature request in the mean time.

Do you have a link to the message specs/structure?

Yeah, this page has some pretty good documentation of the protocol. I also see that CAN is discussed on it a bit as well.
Some of the details are a bit fuzzy in which case you might need to take a look at the actual official source code which you can find here.
Hope that helps and let me know if you need a hand with anything.

Closed with PR #9.


Looking for a way to trust the remote data service matches

It seems that the CompleterService is designed to only display exact matches to the input. Is it possible to configure or write an implementation so that the CompleterService will trust the remove data service and show all of the matches that it returns? This would allow me to display the approximate matches to the user which the remote data service is returning. Thanks.

@grenager you can do that by setting searchFields to null


Parallax Tileing Test

Changelog
add: New Parallax for testing
:cl:

add: Added fun!
remove: Removed fun!

test locally chud


DOES IT MEAN THAT IF I HAVE TO CREATE A POLICY WITH ABILITY TO REMEDIATE RESOURCE, THEN I SHOULD MINIMUM HAVE ONLY 'USER ACCESS ADMIN' RIGHTS OR EVEN CONTRIBUTOR RIGHTS?

[Enter feedback here]

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

ID: ad82c7c8-2bda-ee68-97db-66da6e17646f
Version Independent ID: b6b8a9bc-6581-859b-5a4d-8b087c04e35e
Content: Support and help options for Azure Active Directory
Content Source: articles/active-directory/fundamentals/support-help-options.md
Service: active-directory
Sub-service: fundamentals
GitHub Login: @CelesteDG
Microsoft Alias: celested

@ArjunDeb420
Thanks for your feedback! We will investigate and update as appropriate.

This question was covered in this related thread:

If you create the policy definition in the portal, Azure Policy creates the managed identity per assignment and grants this managed identity the roles defined in roleDefinitionIds using the user’s identity, so User Access Administrator or an RBAC role with Microsoft.Authorization/roleAssignments/write is required. In this way, the user creating the policy assignment doesn’t need to manually grant privileges to the managed identity. If the policy assignment is done through SDK (Azure CLI, PowerShell, etc.) then the managed identity does need to be manually granted the needed permissions from roleDefinitionIds, but it doesn’t have to be the user that assigned the policy (one can assign it and another can grant the managed identity the needed roles). In the event the user assigning the policy doesn’t have permissions to grant roles, the policy assignment is still created and will report compliant/non-compliant states.

Let me know if this helps. If you have further questions feel free to tag me in the comments or open a new post on Q&A. https://docs.microsoft.com/answers/topics/azure-active-directory.html


Missing categories and subelements

The DesktopManifestSchema ApplicationExtensionChoice, and AppXManifestTypes ST_ApplicationExtensionCategory_Desktop, define four categories.  This page contains only one and the missing ones lack their own pages for the sub-elements.

windows.FullTrustProcess (present)
windows.startupTask (missing)
windows.toastNotifictionActivation (missing)
windows.searchProtocolHandler (missing)

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

ID: daca40a6-0caf-8878-ce0f-e244ee88613a
Version Independent ID: 958ff491-0dc9-0d49-0c95-b704275f0710
Content: desktop:Extension - Windows UWP applications
Content Source: winrt-related-src/schemas/appxpackage/uapmanifestschema/element-desktop-extension.md
Product: uwp
Technology: winrt-reference
GitHub Login: @mcleanbyron
Microsoft Alias: mcleans

These categories and subelements have been added:
https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop-fulltrustprocess
https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop-startuptasks
https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop-toastnotificationactivation
https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-desktop-searchprotocolhandler


An error "UnexpectedCancel" displays in the activity log when uploading items to one attached blob container which SAS URL is created by an access policy (List, Read)

Storage Explorer Version: 1.21.0
Build Number: 20210908.7
Branch: rel/1.21.0
Platform/OS: Windows 10/Linux Ubuntu 20.04/MacOS Big Sur 11.4
Architecture: ia32\x64
How Found: From running test case
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> Blob Containers.
Create a blob container -> Right click the blob container.
Click 'Manage Access Policies...' -> Add one access policy with 'Read, List' permissions.
Generate a SAS URL via the access policy.
Attach the blob container via the SAS URL.
Upload one blob to the attached blob container -> Click 'OK' on the prompt detected dialog.
Check whether a helpful error message displays in the activity log.

Expected Experience
A helpful error message displays in the activity log.
Actual Experience
An error "UnexpectedCancel" displays in the activity log.

Error Details:
{   "message": "\"UnexpectedCancel\"" }
Additional Context

Here is the AzCopy log:
0238cd79-e76f-ab4d-6af8-414b55630e88.log
This issue also reproduces for ADLS Gen2 blob containers/file shares.
This issue doesn't reproduce when attaching via SAS permissions.

Better error messages are needed. In our case {"message": ""UnexpectedCancel""} ment that our storage destination reached it's quota limit. It took us a couple of hours to figure this out.


not a method to show on window.

UIWindow is a subclass if UIView so it works just the same.

But disappears instantly when window's root view changes.


Production use case not valid for Now 2.0?

I've tried to use the production use case for a site I was testing using Now 2.0 with GitHub integration.
But the Now bot commented that the static property cannot be used in the config and the build failed. The option cannot be seen in https://zeit.co/docs/configuration too, so is it invalid?

Can anyone confirm this?

Sorry for the late reply. That section of the Readme did indeed only apply to Now 1.0, and this module isn't necessary with the v2.0 platform, because 2.0 supports static files as a first class citizen and an external module like this one is not necessary. And for local development, the vercel dev command should be used instead of `server.
As such, I've removed that section of the Readme at this time.


Issue fixes in Java gRPC metadatagen

Preserve the file permission while copying
Add the missing javadoc task
Add the missing template file

LGTM

Codecov Report

Merging #1176 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #1176      +/-   ##
============================================
+ Coverage     86.08%   86.08%   +<.01%
  Complexity     3681     3681
============================================
  Files           372      372
  Lines         14512    14514       +2
  Branches       1626     1626
============================================
+ Hits          12493    12495       +2
  Misses         1583     1583
  Partials        436      436

Impacted Files
Coverage Δ
Complexity Δ

...metadatagen/java/JavaStaticGrpcMetadataCopier.java
100% <100%> (ø)
7 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 63b02af...29f105c. Read the comment docs.


Add branch 04-channel-upgrades of ibc-go simapp

No need to merge this, we will only use it from Hermes while we implement support for channel upgrades and until it is released in ibc-go.

Closing as this https://github.com/informalsystems/cosmos.nix/pull/153 added the channel upgrade alpha version


fix more inline things

Fixes:

When you type ( the IDE auto-fills ) - Which causing another invocation of the document listener.
This means that the first invocation will be debounced and the second one will catch - causing the completion to appear after the auto-filled char (instead of before)

To solve this, I'm disabling completions in auto import chars completely. (if you're in some brackets and hit tab, IJ catches it before us to move the caret one char forward - that's why im disabling this completely)
2. Wrong condition on caret & key listeners - just the wrong boolean condition...
3. Snippets that start with \n were presented in the wrong location

lgtm


Re-adding option to install Tiller

Backport of https://github.com/kubic-project/velum/pull/316

Thanks for taking care of this backport, @ereslibre! LGTM 👍


added CoreCharts library

Project URL
https://github.com/cagricolak/CoreCharts
Category
Charts
Description
CoreCharts is a simple powerfull yet Charts library for apple products.
Why it should be included to awesome-ios (optional)
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 / tvOS 10 or later
[x] Supports Swift 4 or later
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

1246
301
https://pusher.com/push-notifications redirects tohttps://pusher.com/beams

2344
301
https://github.com/xorshine/KafkaRefresh redirects tohttps://github.com/OpenFeyn/KafkaRefresh

  Generated by :no_entry_sign: Danger

updated checks.


Rename and document control_level vector

I was a little confused about what this vector did when reading the code. Is it some kind of vector of possible control modes for each actuator? Or a vector of current control modes for all actuators? Added a comment to clarify.
I also did some minor renaming:  lvl --> level for readability and consistency.

Codecov Report

Merging #122 (464a083) into master (bf32f38) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master    #122     +/-   ##
========================================
  Coverage    0.00%   0.00%
========================================
  Files          45       3     -42
  Lines        4410     294   -4116
========================================
+ Misses       4410     294   -4116

Flag
Coverage Δ

unittests
0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...demo_hardware/src/rrbot_system_multi_interface.cpp

...demo_hardware/src/rrbot_system_multi_interface.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

...demo_hardware/src/rrbot_system_multi_interface.cpp

...demo_hardware/src/rrbot_system_multi_interface.cpp

...l_demo_hardware/src/rrbot_system_position_only.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

.../ros2_control_demo_hardware/src/diffbot_system.cpp

... and 38 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf32f38...464a083. Read the comment docs.


No window when starting from a Remote Desktop connection

When I'm trying to open Launchbuddy, it opens the updating sequence and updating the login credentials. But when you expect the window with all your accounts this doesn't show. This problem only shows when using remote desktop. In 2.4.1 it worked perfectly. (But it might be just my fault for messing things up)
(windows 10 laptop to a windows 10 desktop)

I've tried the solution on thread #264 but didn't solve the issue.

I have the same issue but without remote desktop. With my dual screen setup it's working fine, but if I use only one screen, I have the same issue as @Errox
The second screen is connected to my computer but I have selected another input on the screen so windows is not recognized the screen
I hope this information is helpful to find a solution to fix this issue.

Thanks for the information. Tested connecting different monitors to my machine without success. So still quiet hard to me finding a workflow for this issue

So, after some testing. I've came to the conclusion that on my desktop pc, I have 3 screens. When I place the application outside the "main" screen. I can't get it visual on my laptop when being connected with Remote Desktop. But when I leave the application on my main screen, I can get a visual when connecting.
Maybe it's possible to recognize the desktop being run in Remote Desktop, and if so, start the application without storing the previous location it was shut down in?


Docker image in docker hub is outdated?

Hi,
I pulled the latest docker image from docker hub, the docker hub said that the image was Updated 3 months ago. However, the latest source code commit is https://github.com/drogonframework/drogon/commit/88236f9279c79e11c83294a25e7a75e90bccabee, which was  on Aug 5, 2021
docker run --rm drogonframework/drogon:latest drogon_ctl version

Maybe because of docker build cache. Could you check and push latest version on docker hub?
Thank you

@tuanpht Thanks for your feedback. Just pushed the latest image to dockerhub. Please check.

@an-tao
Thank you!
I've pulled image again and now it is include the latest source code


[BUG] Instance manager pod does not respect of node taint?

Discussed in https://github.com/longhorn/longhorn/discussions/5160

Originally posted by jwenjian December 28, 2022
I am confused about the instance manager pod behavior of node taint, hope anyone can help :)
I have a single node cluster with longhorn installed, then I add a new taint to the node, e.g. k=v:NoSchedule,then I delete the instance manager pod, based on my understanding, the new instance manager pod cannot be scheduled since it has no corresponding toleration.
But the new pod is scheduled and running normally, just like before.
I tried to delete the longhorn ui pod, the new UI pod is in pending status and cannot be scheduled to the node, which is expected.
Is there any other dark tech for the instance manager pods?
BTW, when I describe the instance manager pod, I just found 2 tolerations, none of them is for the new taint:
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type    Reason   Age   From     Message
  ----    ------   ----  ----     -------
  Normal  Pulled   54m   kubelet  Container image "longhornio/longhorn-instance-manager:v1_20211210" already present on machine
  Normal  Created  54m   kubelet  Created container replica-manager
  Normal  Started  54m   kubelet  Started container replica-manager

cc @longhorn/qa

I agree with @innobead's assessment in #5160. Brainstorming this afternoon, I came up with some changes we could potentially make.

Append a kubernetes.io/hostname: <im.spec.NodeID> label to the nodeSelector we already use , remove the NodeName field @innobead pointed out, and rely on the nodeSelector to cause instance-manager pods to be scheduled on the intended node. (This could also be done with a nodeAffinity, but it seems confusing to mix nodeSelector and nodeAffinity.) Pods won't be scheduled if there is a preventing taint.
Add a podAffinity constraining the instance-manager pod to the same node as the longhorn-manager pod, remove the aforementioned NodeName field, and rely on the podAffinity to cause instance-manager pods to be scheduled on the intended node. Pods won't be scheduled if there is a preventing taint.
Add a check similar to the one @shuo-wu already did for unscheduleable nodes (this one for taints with the NoSchedule effect) so that we never try to create instance-manager pods in the first place. I don't like this approach, as it largely duplicates the existing functionality of the Kubernetes scheduler. Note that @shuo-wu's check applies to nodes with spec.unschedulable=true (nodes that are cordoned), not nodes with taints.
Do nothing. Is there a valid reason to want to run a longhorn-manager pod on a node, but not instance-manager pods?

The backing image manager and backing image data source controllers also directly write the NodeName field in a similar way. If we choose to change this behavior in the instance manager controller, we should probably do it there as well.
My gut reaction is that there isn't a compelling reason to make a change here. The existing behavior is confusing, but I don't understand why we'd want to run longhorn-manager without instance-manager.
If we do want to make a change, I lean towards the second option.
Please let me know your thoughts, @innobead or @shuo-wu if you get a moment.

Add a check similar to the one @shuo-wu already did for unscheduleable nodes

YES, we encountered a similar issue before and I didn't think of the node selector labeling way. This is more like a workaround. It's great to have a better solution.
But statement #4 is valid as well. Or in other words, the instance manager pod and the backing image manager pod should have the same node affinity with the longhorn manager pod on each Longhorn worker node.

We discussed this in the community issue review meeting. Our current plan is to:

Confirm whether or not we will run replica processes on the node when it is tainted. We probably will, but we have a feature that disables scheduling when the node is cordoned, so it is not a sure thing.
Reach out to the user who initiated the question and ask if the current behavior is actually problematic, or if they are just curious.
If we don't hear back from the user or they don't provide a justification for a change, we will do nothing.

We DO currently run replicas on nodes that are tainted:
eweber@laptop:~/longhorn> k describe node eweber-v124-worker-1ae51dbb-4pngn | grep Taints
Taints:             test=test:NoSchedule

eweber@laptop:~/longhorn> k apply -f examples/
block_volume.yaml              csi/                           deployment.yaml                pod_with_pvc.yaml              rwx/                           simple_pvc.yaml                statefulset.yaml
crypto/                        data_migration.yaml            network-policy/                restore_to_file.yaml.template  simple_pod.yaml                snapshot/                      storageclass.yaml
eweber@laptop:~/longhorn> k apply -f examples/pod_with_pvc.yaml
persistentvolumeclaim/longhorn-volv-pvc created
pod/volume-test created

eweber@laptop:~/longhorn> kl get replica
NAME                                                  STATE     NODE                                DISK                                   INSTANCEMANAGER                                     IMAGE                                    AGE
pvc-bcbbb2ad-749f-465f-ac68-393980982b20-r-1cdb9b9d   running   eweber-v124-worker-1ae51dbb-4pngn   9699a051-aff8-457d-a6f4-4c067615e7ed   instance-manager-bd54850e35239b37069374780ca0f9a3   longhornio/longhorn-engine:master-head   11s
pvc-bcbbb2ad-749f-465f-ac68-393980982b20-r-2951a59c   running   eweber-v124-worker-1ae51dbb-ppvzp   711d4bcb-85ab-4cfc-ad06-fcf12de42916   instance-manager-faf47d6949e508720ae71ed3ee10e466   longhornio/longhorn-engine:master-head   11s
pvc-bcbbb2ad-749f-465f-ac68-393980982b20-r-c24b688f   running   eweber-v124-worker-1ae51dbb-pbxr9   4a758df2-1b96-4c11-a664-4f211f542923   instance-manager-4639bda14281d41f3af00d64bc364bb9   longhornio/longhorn-engine:master-head   11s

I have reached out in #5160 in preparation for closing this issue.

Good update. I agree with the conclusion below, primarily instance-manager is actually managed by longhorn-manager, so they should be atomic existence.

Longhorn-manager will continue to try to run an instance-manager pod on any node where it itself is running.
If longhorn-manager is forced off a node, instance-manager can be deleted and will not run again.

Closing this issue after further discussion in #5160.


Resource's schema description

https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/blob/1fd31cdb3ca76f8418c0209753e204e4e12c019a/src/main/resources/examples/resource/initech.tps.report.v1.json#L3
The description in the schema is being used in the Console UI, and this has led to very poorly named descriptions

https://github.com/search?q="Resource+schema+for"+org%3Aaws-cloudformation&type=Code

This is called out:
https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/blob/1e99ac138807111f16c5368cf6977ec09dbd6d42/src/main/resources/schema/provider.definition.schema.v1.json#L278
but maybe the console needs to be re-thought or description shouldn't be required:
https://github.com/aws-cloudformation/aws-cloudformation-resource-schema/blob/1e99ac138807111f16c5368cf6977ec09dbd6d42/src/main/resources/schema/provider.definition.schema.v1.json#L409-L412
based on how non-descriptive the descriptions have been so far


User Research

-participatory design
-task analysis
-contextual inquiry
-journey mapping or service design

Task flow analysis: https://methods.18f.gov/decide/task-flow-analysis/
contextual inquiry: https://methods.18f.gov/discover/contextual-inquiry/
Service design tools: http://www.servicedesigntools.org/
Journey mapping: https://methods.18f.gov/decide/journey-mapping/


nuxt.options._layers is not iterable in v3.0.0

Environment

Operating System: Linux
Node Version:     v20.8.1
Nuxt Version:     2.17.2
CLI Version:      3.10.0
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          webpack
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction

The error only occurs in production after running :
yarn build
yarn start

Describe the bug
I am in the process of updating a module in our company from v3.0.0-rc.4 to v3.0.0
We're not using nitro and vite yet, as we still have some work to do.
Our module installs other modules using installModule function from @nuxt/kit.
The following error occurs when launching the server after a production build :
yarn run v1.22.19
$ nuxt2 start

 ERROR  nuxt.options._layers is not iterable                        7:37:51 PM

  at installModule (node_modules/@nuxt/kit/dist/index.mjs:2409:32)

I traced the error back to its source
If I understand correctly,

Version v3.0.0-rc.4 uses version v3.8.2 of @nuxt/kit
Version v3.0.0 uses version v3.9.1 of @nuxt/kit.
The installModule function in v3.9.1 depends on the contents of the nuxt.options._layers property. L19
The nuxt.options._layers property is mocked by @nuxt/bridge but only in dev environment or during the build process. L61
This is the reason why the nuxt.options._layers property is undefined when the server is started.

Proposed solution:

We need to mock _layers for nitro and auto-imports outside the buildModules function.
This solves the issue locally

Additional context
No response
Logs
No response

I think we should create an issue on upstream for this.
https://github.com/nuxt/nuxt


Fast Configurable Shader goes all black on tiny scale

The Fast Configurable Shader turns some of my meshes all black when scaled to 1e-5, and none of the options seem to have an affect.
The Obsolete/Unlit shaders do work, and that's fine.
One might ask why I'm dealing with such a small scale, and that's because I'm scaling down the world.

Yeah, sounds like floating point issues.

Yeah, that's what some other similar problems say.  I don't mind that I have to use an Unlit shader, I suppose the question is if the Fast Configurable Shader can be made to work, or if there still needs to be an Unlit shader in the MRTK for edge cases like this.

@XPav have you tried the new shader system?

I have not.


[Request] Have running as background or menu bar app for macOS

It would be nice to be able to run the app in the background as a menu bar app on the Mac instead of it taking place on the Dock. I'm not quite sure if this is possible in Swing, but it's worth looking into.

This would be great.

+1 This would be awesome.

I finally added a menu bar toggle in the latest release. Sadly I couldn't hide the app icon in the dock, because it would break the GUI as it is now, but at least you can use it to hide the app's main window while it is running.


用于自定义编辑esp-idf的方法 (Methods for custom editing esp-idf ) (IDFGH-6584)

Is your feature request related to a problem? Please describe.
你好，在freertos中，“vTaskGetRunTimeStats”在一段时间后将会溢出，导致结果不准确。
在freertos论坛中存在解决方案，但是需要对freertos源代码进行修改；如果我直接修改esp-idf中的代码，明显会造成工程失去移植性，除非复制一份freertos组件到工程目录下的components文件夹。
但是这样又会增加工程的体积。
Hello, in freertos, "vTaskGetRunTimeStats" will overflow after some time, resulting in inaccurate results.
There is a solution in the freertos forum, but the freertos source code needs to be modified; if I directly modify the code in esp-idf, it will obviously cause the project to lose portability, unless a copy of the freertos component is copied to the components folder in the project directory .
But this will increase the volume of the project.
Describe the solution you'd like
在我的设想中，可以增加一个构建前，在构建文件夹对esp-idf组件进行打补丁的流程。
应用工程文件夹下patches文件夹内所有的补丁后，再使用打完补丁的文件替换esp-idf源文件来进行编译。
这样，既可以保持esp-idf的完整性，又可以对其进行修改，同时又可以保持工程的简洁性。
In my imagination, a process of patching the esp-idf components in the build folder before building can be added.
After applying all the patches in the patches folder under the project folder, use the patched files to replace the esp-idf source files to compile.
In this way, the integrity of esp-idf can be maintained, and it can be modified, while maintaining the simplicity of the project.
Describe alternatives you've considered

在以前的工程中，如果我需要对esp-idf组件进行修改，我会将被修改的组件复制一份到工程文件夹下的components文件夹内，再来进行修改。
但如果修改的组件比较多，工程的体积将变得巨大，并且难以管理。
使用工程目录下replaces文件内的文件替换esp-idf内的源文件进行编译，这实现起来也许没有打补丁那么复杂。

===========

In the previous project, if I need to modify the esp-idf component, I will copy the modified component to the components folder under the project folder, and then modify it.
But if there are many modified components, the size of the project will become huge and difficult to manage.
Use the files in the replaces file in the project directory to replace the source files in esp-idf for compilation, which may not be as complicated as patching.

Have you tried looking at overriding components?

Have you tried looking at overriding components?

Yes, that's the way it is currently used, but it will make a full copy of the component in the project directory.

Hi @Zmmfly ,
Can you show us what should be fixed exactly inside FreeRTOS component? Maybe adding a wrapper at link time would be enough?


Disappearing Ships after restart

I'm running a server, after a restart all ships vanished! They were disassembled. This also happens in singleplayer. Only DV and MovingWorld are installed.
Versions(DV and MovingWorld): 0006-full
Minecraft: 1.10.2
Forge: 1.10.2-<IP_ADDRESS>5

There's no reason this would happen at all, ships once disassembled are just blocks. I can't reproduce this on my end whatsoever.


Refactor osm cloud-config

What this PR does / why we need it:
The current implementation doesn't map the cloud-config properly, it just read the cloud provider spec from machine deployment and simply flush it in the instance which is problematic. This new implantation changes that, to read the cloud config from a secret that is created by the OSM consumer(KKP and KubeOne).
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes kubermatic/operating-system-manager#56
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

None

/approve
/lgtm

/hold


Remove ESLint rule for enum naming

I left the @typescript-eslint/prefer-enum-initializers rule in place because I think this one still makes sense
Motivation:
We tried to enforce PascalCase for enums, then camelCase for enums. In both cases, there were some edge cases that are cumbersome to fix. So we decided to use camelCase if possible from now on, but not enforce it via ESLint.

COM-889

I left the @typescript-eslint/prefer-enum-initializers rule in place because I think this one still makes sense

I agree. But is this a breaking change? Then we'd need a changeset.


Cherry pick overlapping ranges to master

Cherry pick the overlapping IP feature from v0.4.0 to master.
A small commit is added on top, where the unused parameters of the allocate.DeallocateIP function are removed.
Depends-on: #113

@s1061123 / @dougbtv I'm cherry-picking the overlapping IPs feature on top of the leader election changes.
Can I pitch in w/ the leader election changes in any way, to speed up this process ?

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

32 of 417 (7.67%)  changed or added relevant lines in 7 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-7.6%) to 29.435%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/allocate/allocate.go
0
11
0.0%

pkg/api/v1alpha1/zz_generated.deepcopy.go
0
50
0.0%

pkg/storage/etcd.go
0
78
0.0%

pkg/storage/kubernetes.go
0
246
0.0%

Totals

Change from base Build 986532013:
-7.6%

Covered Lines:
370

Relevant Lines:
1257

💛  - Coveralls

I need help understanding whatever's broken in the openshift img generation:
https://github.com/k8snetworkplumbingwg/whereabouts/runs/3017402592?check_suite_focus=true


Don't patch Array.prototype.includes

I noticed this library in the dependencies of node-ipc, and was rather shocked to see that it implements a polyfill for Array.prototype.includes, which - beyond being unnecessary nothing in this library - is incomplete in its implementation and can potentially cause unwanted side-effects for unsuspecting implementors if this is bundled into production code.
I'd greatly appreciate it if you could publish a patch to remove the polyfill so that it's no longer in my dependency tree.

removed in v5.x


[backport] Traffic Router RPM installation

What does this PR do?

[ ] Documentation
[ ] Grove
[ ] Traffic Analytics
[ ] Traffic Monitor
[ ] Traffic Ops
[ ] Traffic Ops ORT
[ ] Traffic Portal
[X] Traffic Router
[ ] Traffic Stats
[ ] Traffic Vault
[ ] Other _________

What is the best way to verify this PR?
Traffic router install and upgrade successfully from 2.1/2.2.
Check all that apply

[ ] This PR includes tests
[ ] This PR includes documentation updates
[ ] This PR includes an update to CHANGELOG.md
[ ] This PR includes all required license headers
[ ] This PR includes a database migration (ensure that migration sequence is correct)
[ ] This PR fixes a serious security flaw. Read more: www.apache.org/security

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/2839/
Test PASSed.


ICUDIR not necessary on some platforms

On some platforms (e.g. a typical Linux distribution), the default package manager will install ICU into the default include/library paths, which makes checking for ICUDIR redundant and indeed impossible to satisfy, as there's no "root" of ICU.
The root Makefile needs some basic logic to construct the ICU lib/include flags (which may both be null in the typical Linux case)

Alternatively we could rewrite the iKnow build to use autoconf but :-P


Adds failing testcase to clarify expected functionality of the decode…

…Hex method
Test that demonstrates issue #58

Closing this PR. I have now attempted to document the behaviour in https://github.com/10cella/hashids-java/pull/61


Full screen view of the grids

Hello @PablocFonseca , thanks for this great work.
Do you have plans to support full screen view of the tables/grids, just like it works, for example, for figures (see image below):

Snip taken from https://pablocfonseca-streamlit-aggrid-examples-example-jyosi3.streamlitapp.com/

I second this feature. It will be amazing. I am working with a very large table, and a fullscreen view will make it very user-friendly.


tracing: Add ISR numbers to SystemView for Cortex-M

The sysview module does not set an interrupt number when recording ISRs
for SEGGER SystemView. Added ISR numbers for Cortex-M based chips.
Signed-off-by: Jan Müller<EMAIL_ADDRESS>

There's also already code in place in isr_wrapper.S to calculate this value for the current architecture while looking up the correct handler. I've hacked this for Cortex-M in the past by just caching this value during ISR entry.


[Discuss] Update setup doc to include agent installation

What is this change about?
Updating bosh docs for work station setup.
Please provide contextual information.
[Discuss] Currently we are not specifying bosh-agent install as part of setup steps. But if you try to rake spec:integration:install_dependencies as mentioned in the later steps it will fail. So we can add it as part of setup step
go/src/github.com/cloudfoundry/bosh-agent/bin/build
rake aborted!
Command failed with status (127): [go/src/github.com/cloudfoundry/bosh-agent/...]
/Users/pivotal/gdey/bosh/src/bosh-dev/lib/bosh/dev/tasks/spec.rake:116:in `compile_dependencies'
/Users/pivotal/gdey/bosh/src/bosh-dev/lib/bosh/dev/tasks/spec.rake:55:in `block (4 levels) in <top (required)>'
/Users/pivotal/gdey/bosh/src/bosh-dev/lib/bosh/dev/tasks/spec.rake:37:in `open'
/Users/pivotal/gdey/bosh/src/bosh-dev/lib/bosh/dev/tasks/spec.rake:37:in `block (3 levels) in <top (required)>'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli/exec.rb:74:in `load'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli/exec.rb:74:in `kernel_load'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli/exec.rb:28:in `run'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli.rb:424:in `exec'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/vendor/thor/lib/thor/invocation.rb:126:in `invoke_command'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/vendor/thor/lib/thor.rb:387:in `dispatch'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli.rb:27:in `dispatch'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/vendor/thor/lib/thor/base.rb:466:in `start'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/cli.rb:18:in `start'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/exe/bundle:30:in `block in <top (required)>'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/lib/bundler/friendly_errors.rb:124:in `with_friendly_errors'
/Users/pivotal/.gem/ruby/2.4.4/gems/bundler-1.16.4/exe/bundle:22:in `<top (required)>'
/Users/pivotal/.gem/ruby/2.4.4/bin/bundle:23:in `load'
/Users/pivotal/.gem/ruby/2.4.4/bin/bundle:23:in `<main>'
Tasks: TOP => spec:integration:install_dependencies
(See full trace by running task with --trace)

What tests have you run against this PR?
NA
How should this change be described in bosh release notes?
NA
Does this PR introduce a breaking change?
NA
Tag your pair, your PM, and/or team!
solo han

@degaurab did you want to ping specific folks on the team to get this merged? It seems pretty internally focused and not really product surface area, so I trust that you can get the right people on board and work with them to prioritize this.


Reboot devices

Please add the possibility to reboot devices
https://github.com/jens-maus/node-unifi/blob/76f99562806bcd5e5abcbc3e4c0e9fc86bcfcd1d/unifi.js#L2013

That would be great!


Bug with Kibana async_search permissions

Running OSS ELK 7.8.0 using the OpenDistro security plugins.
Hit a pretty damning bug - when attempting to view any data in Kibana via the Discover pages you're hit with the following:
[security_exception] no permissions for [indices:data/read/async_search/submit] and User........

The permission isn't accessible within the Kibana UI, I've attempted to use the API to grant the permission but that also does not work (despite being visible in the UI)
PUT _opendistro/_security/api/roles/opendistro_security_anonymous
{
    "cluster_permissions" : [
      "indices:data/read/search",
      "indices:admin/mappings/get",
      "indices:admin/aliases/get",
      "indices:data/read/*"
    ],
    "index_permissions" : [
      {
        "index_patterns" : [
          "apm*",
          "logstash*",
          "filebeat-*",
        ],
        "dls" : "",
        "fls" : [ ],
        "masked_fields" : [ ],
        "allowed_actions" : [
          "crud",
          "create_index",
          "indices:data/read/async_search/submit"
        ]
      }
    ],
    "tenant_permissions" : [
      {
        "tenant_patterns" : [
          "DevOps"
        ],
        "allowed_actions" : [
          "kibana_all_write"
        ]
      },
      {
        "tenant_patterns" : [
          "global_tenant"
        ],
        "allowed_actions" : [
          "kibana_all_write"
        ]
      }
    ]
}

Async search was added in 7.7.0. This bug has been fixed by the SearchGuard guys - https://forum.search-guard.com/t/indices-data-read-async-search-submit-error/1842
Reported by another user on the OpenDistro forums; https://discuss.opendistrocommunity.dev/t/bug-indices-data-read-async-search-submit-error/3031
Is there any workarounds without granting users all_access to clusters?

Any updates regarding this? This must be breaking for anyone using Elastic's Kibana with the OpenDistro Security plugin.

This is affecting my cluster too.

This is what the searchguard guys did to fix the issue. Can you please provide a similar fix?
Override Kibana internal search

Waiting for a bug correction i rollback to elastic search 7.6.1, Kibana 7.6.1 and open distro <IP_ADDRESS> plugin and with this configuration it works. _async_search is new in 7.7. That's my configuration:
In Internal_users.yml:
readonly_user:
  reserved: false

In roles_mapping.yml:
read_only_index:
  users:
  - readonly_user
kibana_RO:
  users:
  - readonly_user
kibana_read_only:
  users:
  - readonly_user

In roles.yml:
kibana_RO:
  reserved: true
  hidden: false
  description: Provide the minimum permissions for a kibana user
  cluster_permissions:
  - cluster_composite_ops
  index_permissions:
  - index_patterns:
    - ".kibana"
    - ".kibana-6"
    - ".kibana_*"
    allowed_actions:
    - read
    - delete
    - manage
    - index
  - index_patterns:
    - ".tasks"
    - ".management-beats"
    - "*:.tasks"
    - "*:.management-beats"
    allowed_actions:
    - indices_all
  tenant_permissions:
  - tenant_patterns:
    - global_tenant

In kibana.yml:
elasticsearch.requestHeadersWhitelist: ["securitytenant","Authorization"]
opendistro_security.multitenancy.enabled: false
opendistro_security.multitenancy.tenants.enable_global: true
opendistro_security.multitenancy.tenants.enable_private: true
opendistro_security.multitenancy.tenants.preferred: ["Private", "Global"]
opendistro_security.multitenancy.enable_filter: false

opendistro_security.readonly_mode.roles: [“kibana_read_only”]

Waiting for a bug correction i rollback to elastic search 7.6.1, Kibana 7.6.1 and open distro <IP_ADDRESS> plugin and with this configuration it works. _async_search is new in 7.7. Kibana_user was nos working so i created a custom rôle kibana_RO and that's my configuration:

For anyone who's going to be attempting this, as far as I'm aware you can't roll elasticsearch back unless you've taken a snapshot to restore.

This appears to be fixed for basicauth in 1.10.2, but not for openid

This can be worked around in <IP_ADDRESS> by manually adding the indices:data/read/async_search/submit and indices:data/read/async_search/get permissions via curl. Would be nice if these could be added to the list of selectable permissions, though

hey rkbennett, iam using latest version of  open distro security plugin + 7.9.1 kibana , can u elaborate on ur answer above.
where do u add the permissions, to what role do u add them to

Same issue using the Opendistro stack v 7.8.0.
@rkbennett on which indices these perms are missing?

I saw that SearchGuard workaround was to disable async search in Kibana, is there any progress on this?

I saw that SearchGuard workaround was to disable async search in Kibana, is there any progress on this?

Maybe this will be fixed in the upcoming version (1.13)?
https://github.com/opendistro-for-elasticsearch/community/issues/220

This is my workaround form my use case:
create action group:
curl -XPUT "https://elasticsearch-host:9200/_opendistro/_security/api/actiongroups/async_fix_action_group" -H 'Content-Type: application/json' -d'{  "allowed_actions": [    "indices:data/read/async_search/submit",    "indices:data/read/async_search/submit*",    "indices:data/read/async_search/delete",    "indices:data/read/async_search/delete*",    "indices:data/read/async_search/get",    "indices:data/read/async_search/get*"  ]}'
Add to role action group.

This is my workaround for my use case:
create action group:
curl -XPUT "https://elasticsearch-host:9200/_opendistro/_security/api/actiongroups/async_fix_action_group" -H 'Content-Type: application/json' -d'{ "allowed_actions": [ "indices:data/read/async_search/submit", "indices:data/read/async_search/submit*", "indices:data/read/async_search/delete", "indices:data/read/async_search/delete*", "indices:data/read/async_search/get", "indices:data/read/async_search/get*" ]}'
Add to role action group.

Tried this, but it still doesn't work if you only allow certain indices. Kibana tries to do:
indices:data/read/async_search/submit on the allIndices=[*]. So if you don't give users permissions to all indices this doesn't work.  :(

@hkarpf I think it's different things. I've installed and tested, and you still need to make sure your user have a role with index_pattens: ["*"] and allowed_action: ["indices:data/read/async_search/submit"] at least.
In some use cases it's insecure giving those permission that grant access to all indices... even if it's only indices:data/read/async_search/submit

Hopefully the new opensearch dashboards can take advantage of this feature.

Any word on if this is fixed in the latest distros of Opendistro?

We are doing some "spring cleaning in the fall", and to make sure we focus our energies on the right issues and we get a better picture of the state of the repo, we are closing all issues that we are carrying over from the ODFE era (ODFE is no longer supported/maintained, see post here).
If you believe this issue should still be considered for current versions of OpenSearch, apologies! Please let us know by re-opening it.
Thanks!


are you planning to add any headless CMS?

Hello,
Are you planning to add any headless CMS like strapi / netlify-cms.
thanks.

i am so impressed with the concept of fast loading and static sites and netlify
so if a cms is available, i can use it in place of wordpress for client sites.
thanks.

Not on this repo as it's just an example for others to learn from or fork if they want to use it.
If you are interested, I have a video on using Gridsome with Netlify CMS: https://www.youtube.com/watch?v=ryP1RMA7P9Y


xml reading library changed to defusedxml

Contributor Checklist:

[x] I have added or updated my entry in the creators.json file
[x] I have added a changelog entry for my contribution
[x] I have added/updated documentation for all user-facing changes
[ ] I have added/updated test cases
[ ] I have included the rebuilt production build of the client (only if changes were made to the GUI)

Reviewer Checklist:

[x] /azp run libertem.libertem-data passed

Looks good, many thanks! Merging. :-)


fix: update fluent container mount path and show them using logging

closes https://github.com/ansys/pyfluent/issues/2867, https://github.com/ansys/pyfluent/issues/2865

Set EXAMPLES_PATH = os.getcwd()
Set EXAMPLES_PATH = PYFLUENT_CONTAINER_MOUNT_PATH using autouse fixture.
host_mount_path and container_mount_path are visible to user through logger.warning()

logging information of PyFluent and Fluent workdir is shown as follows.
>>> from ansys.fluent.core import launch_fluent
>>> solver = launch_fluent()
pyfluent.launcher WARNING: Starting Fluent container mounted to /mnt/c/Users/hpohekar/pyfluent, with this path available as /mnt/pyfluent for the Fluent session running inside the container.
>>>
>>> solver.exit()
>>>

We are getting following error and CI is failing. We will have to discuss proper solution for following error then we will resume this task.

https://github.com/ansys/pyfluent/actions/runs/9315232834/job/25640985375?pr=2874

I would suggest that my suggestion in #2874 (comment) be considered again, using an environment variable instead of a module constant. See below for more details.
Sorry for all the back and forth.

No issues at all. We need best solution and we can update the code each time. Thank you.