Some parameters are not provided if : is inside the string for at least LiteralPath, Path

Steps to reproduce
Type:
 get-content -LiteralPath 'c:\test.html'

Continue typing - and press CTRL+SPACE
 get-content -LiteralPath 'c:\test.html' -

Notice how RAW is not on the list. If you will choose -R and ctrl+space it will work

It behaves like that for all PowerShell versions losing parameters inside. If you don't use : inside the string:
get-content -LiteralPath 'c\test.html'

All parameters will be provided. The workaround for this is to type RAW first. I've seen it multiple places not just for get-content where some parameters are missing from parameterset. I was able to track it down to the :  being a problem. It may be strictly related to Path/LiteralPath.

Expected behavior
Should not matter what is inside the string, at least I think it shouldn't. Otherwise, all paths on windows break it.
Environment data

Name                           Value
----                           -----
PSVersion                      7.0.0-rc.2
PSEdition                      Core
GitCommitId                    7.0.0-rc.2
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Distilled repro:
$script = 'Get-Content -Path "C:\test" -'
TabExpansion2 -inputScript $script -cursorColumn $script.Length |
    % { $_.CompletionMatches.CompletionText } |
    Should -Contain '-Raw'

Interesting to note that these pass:
# Bare word argument
Get-Content -Path C:\test -

# No drive separator character.  Position in string doesn't matter, always fails if it's present
Get-Content -Path "C\test" -

-Raw is a dynamic parameter added by the PS file-system provider, so by design it should only be offered if the Get-Content command can be inferred to be targeting a file-system location.
Here's how it mostly works at the moment - except for the bug:

If the path starts with a reference to a valid drive (e.g, C:, env:), the target provider is inferred from that.

If the drive being referred to doesn't exist, it seemingly excludes any provider-specific parameters (it becomes provider-agnostic, which is defensible).
Note that it is only the drive's existence that is considered; whether the rest of the path exists is irrelevant.

If there is no path at all , or the path doesn't start with a drive spec, it assumes the provider underlying the current location is being targeted.

Thanks to your repro, @SeeminglyScience , I think the bug is specific to the following scenario:

A path that does include a (valid) file-system drive spec that is also quoted (whether singly or doubly).

So it seems like it's reversed now. It only shows up if there is no -Path/-LiteralPath used. It also shows if no drive is specified. It disappears as soon as the drive is specified.

It also shows if no drive is specified

Only if the current location is a file-system location (which, in fairness, is by far the most common scenario). If you do Set-Location env: first, you'll see that it disappears - as it should (see explanation above).

It disappears as soon as the drive is specified.

Only if the path is quoted - that is the bug.
P.S.: My previous comment originally claimed that a non-existent drive results in provider-agnostic behavior, but that's not true: it falls back to inferring the target provider from the current location; I've updated the comment.

My guess is that the problem is here:
https://github.com/PowerShell/PowerShell/blob/a578347b5a9d4b7c48f2cd303f876dfa6f27cdce/src/System.Management.Automation/engine/CommandCompletion/PseudoParameterBinder.cs#L1237-L1243
The argument should be added as ((StringConstantExpression)ast).Value instead of as ast.Extent.Text.

That's promising, @SeeminglyScience, but it won't work with VariableExpressionAst (e.g, $var) and ExpandableStringExpressionAst (e.g, $var\sub).
Perhaps simply trimming the quotes explicitly is the solution?
var unquotedText = System.Text.RegularExpressions.Regex.Replace(
  expressionArgument.Extent.Text,
  @"^(['""])(.*)\1$", "$2"
);
argumentsToGetDynamicParameters?.Add(unquotedText);

(I've had to amend the previous comment yet again: a non-existent drive indeed causes no provider's dynamic parameters to expand (which is sensible) - except for the potentially distinct bug described in #11848, which is where my confusion stemmed from.)

imo just get dynamic parameters based on current location if it's an expandable string.
If you wanted to go the extra mile you could maybe use the SafeExprEvaluator but that might be overkill.  Either way, using Extent.Text has more issues than the quotes.  It won't translate ` or special character sequences using them either.  Plus here-strings...etc... trying to evaluate based on extent text gets dicey quick.

imo just get dynamic parameters based on current location if it's an expandable string.

That's certainly one way to resolve it, but it would misbehave in cases such as OtherProviderDrive:\sub\$foo
Good point that merely trimming enclosing quotes from Extent.Text isn't fully robust, but I feel it would cover more scenarios than simply falling back to the current location's provider in the presence of any expandable string: `-escaping  or escape sequences are unlikely to occur in the drive-spec portion of a path, and use of here-strings for path arguments is similarly unlikely.
Either approach would certainly be an improvement, though.
(Knowing nothing about SafeExprEvaluator, I can't speak to how much more effort a robust solution would require.)


Publish 11/17/2021, 10:30 AM

Docs Build status updates of commit 8a3edb1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/New-CsOnlineVoiceRoute.md
:bulb:Suggestion
View (skype-ps)
Details

exchange/exchange-ps/exchange/Set-ExternalInOutlook.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-OrganizationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

skype/skype-ps/skype/Get-CsOnlineAudioFile.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/New-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Remove-CsOnlineAudioFile.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsOnlineVoiceRoute.md
:white_check_mark:Succeeded
View (skype-ps)

skype/skype-ps/skype/Set-CsTeamsMeetingPolicy.md
:white_check_mark:Succeeded
View (skype-ps)

teams/teams-ps/teams/Set-CsPhoneNumberAssignment.md
:white_check_mark:Succeeded
View (teams-ps)

skype/skype-ps/skype/New-CsOnlineVoiceRoute.md

Line 0, Column 0: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'cmdlet' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Removed everything related to windows-build-tools, removed from PATH and node still seeing it - how to remove windows-build-tools completely?

Hello,
I tried windows-build-tools but it was not working and also it broke something in my Node.js installation. When trying
npm install

in directory of project, it says
gyp verb check python checking for Python executable "C:\Users\Sebastian\.windows-build-tools\python27\python.exe" in the PATH

I removed Windows Kits, Visual Studio Installer, Python (also from PATH), removed folder
.windows-build-tools

and Node still see windows-build-tools. Please help because I'm struggling with it second day.

Your issue is likely related to npm still being configured to look for Python in that path. Run this:
npm config delete python


Build with cv 4.0

Description
Build with cv 4.0
Changes
Change CV_IMWRITE_PNG_COMPRESSION to cv::IMWRITE_PNG_COMPRESSION
Change CV_IMWRITE_JPEG_QUALITY to cv::IMWRITE_JPEG_QUALITY
Comments

Adapt to the new opencv.

Thank you for the contribution!
We need the compatibility with the lower version of OpenCV.
Could you please define some macros in src/io/opencv_compatibility.h, rather than replacing them?

Thank you for the contribution!
We need the compatibility with the lower version of OpenCV. The lower version doesn't define cv::IMWRITE_PNG_COMPRESSION and cv::IMWRITE_JPEG_QUALITY.
I recommend to re-define the macro when using OpenCV4, like src/io/opencv_compatibility.h.
#if CV_VERSION_MAJOR >= 4
#include <opencv2/opencv.hpp>
#define CV_IMWRITE_PNG_COMPRESSION cv::IMWRITE_PNG_COMPRESSION
#define CV_IMWRITE_JPEG_QUALITY cv::IMWRITE_JPEG_QUALITY
#endif  // CV_VERSION_MAJOR >= 4

Thanks again : )

Many Thanks, and let me test that.

@ewail Welcome to submit the PR : )


Added Dispatch Command & integrated with Inbox Command

Codecov Report

Merging #147 into master will decrease coverage by 3.1%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #147      +/-   ##
============================================
- Coverage     38.22%   35.12%   -3.11%
+ Complexity      258      254       -4
============================================
  Files            64       67       +3
  Lines          1703     1791      +88
  Branches        181      183       +2
============================================
- Hits            651      629      -22
- Misses         1007     1125     +118
+ Partials         45       37       -8

Impacted Files
Coverage Δ
Complexity Δ

src/seedu/addressbook/common/HttpRestClient.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/common/Utils.java
91.66% <ø> (+49.35%)
7 <0> (ø)
:arrow_down:

...edu/addressbook/data/PoliceOfficers/Personnel.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/commands/Command.java
82.14% <ø> (ø)
11 <0> (ø)
:arrow_down:

src/seedu/addressbook/logic/Logic.java
77.41% <ø> (ø)
9 <0> (ø)
:arrow_down:

src/seedu/addressbook/common/Location.java
0% <ø> (ø)
0 <0> (?)

...rc/seedu/addressbook/data/PoliceOfficers/Case.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/commands/InboxCommand.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/common/Messages.java
0% <ø> (ø)
0 <0> (ø)
:arrow_down:

src/seedu/addressbook/PatrolResourceStatus.java
0% <0%> (ø)
0 <0> (?)

... and 19 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 668fcbb...4fe80c7. Read the comment docs.


Please transfer repository from jcentre to maven central

When did you transfer repository from jcentre to mave central

https://github.com/barteksc/AndroidPdfViewer/issues/1049


Does this support failover?

Hello, everyone,
Sorry for not following the format but this is a simple question that doesn't really fit into it.
Basically, what happens if one of the slave databases is unreachable for any reason? It will surely not fallback to another slave since you can only have one slave per instance, but would it fallback to master?
I think this information should be added to README.md.
LMK, thank you
Sorry if I created an issue for something that might not be one.

There are no plans to support failover, since that kind of capability would have to be part of the Active Record drivers themselves to detect the failure condition and switch servers.


Clean up inconsistency with tabs and spaces.

Some files had tabs while others had spaces.  I replaced all of the tabs with 4 spaces to make this consistent.

this maybe a bit too big undertaking ... but I agree with @gorzell , whitespace usage should be consistent all around
I suggest adopting tabs for indentation and maybe we should add a coding guideline to the root of the repo
hiding behind something to avoid rocks thrown at me

I have been out of the java scene for a while, but it used to be that the most common style was 4-4-8 with spaces rather than tab characters.  I believe this was also the most common practice within Netflix.
Not sure about the too big an undertaking part.  If it is fixed once and there is a standard it should be done.  Also there may even be a gradle plugin to enforce the standard pre-commit.

I used to prefer spaces but I've been consistently been using tabs for a 2+ years now and I find myself spending much less time fixing formatting issues. I also find Indentation errors are much easier to spot.
Having to modify all files just to fix just a formatting issue seems a bit overkill to me but it would certainly make working with the codebase a bit easier.
As for plugin, in theory there are good idea but they are always case where the auto-formatting will do a bad job and format the code in an ugly way so I'm not too fond of this forced approach.


Add Swong87 responsive table

Congratulations for your Open source contribution. Don't forget to add a star on this repo.. Happy hacking


Review file paths helper functions abs_file in tagui_parse.php and tagui_header.js

general review of abs_file() function and also checking if steps with filenames work correctly on Linux, macOS, Windows

Thanks @Aussiroth looks good! I'll continue with review of the various TagUI steps involving files to check for inconsistency or use scenarios which will not work across Windows / macOS / Linux.

Steps to check -

[ ] save
[ ] load
[ ] dump
[ ] write
[ ] snap
[ ] table
[ ] tagui
[ ] upload
[ ] download
[ ] receive
[ ] run
[ ] r
[ ] py
[ ] vision

Steps to be checked for tagui_parse.php & tagui_header.js. Closing issue and raising #206 to follow-up.
below looks like need to convert '\' to '\\'

[ ] run
[ ] r
[ ] py
[ ] vision


Zarf-Seed-Registry Installation Fails on Init with Deployment is not ready: zarf/zarf-docker-registry error

Environment
Device and OS: Azure AKS Linux Ubuntu 20.04
App version: 0.19.6
Kubernetes distro being used: AKS Kubernetes V 1.22.6
Other:
Steps to reproduce

Create an AKS Cluster
Run zarf init --components git-server.

Expected result
Command succeeds and Zarf is initialized in the cluster.
Actual Result
The following message repeats until the init run timesout
Deployment is not ready: zarf/zarf-docker-registry. 0 out of 1 expected pods are ready

output of kubectl -n zarf get events
LAST SEEN   TYPE      REASON              OBJECT                                       MESSAGE
15m         Normal    Scheduled           pod/injector                                 Successfully assigned zarf/injector to aks-agentpool-40722291-vmss000001
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-018" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-023" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-013" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-008" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-009" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-019" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "stage1" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-027" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 MountVolume.SetUp failed for volume "zarf-payload-007" : failed to sync configmap cache: timed out waiting for the condition
15m         Warning   FailedMount         pod/injector                                 (combined from similar events): MountVolume.SetUp failed for volume "zarf-payload-027" : failed to sync configmap cache: timed out waiting for the condition
15m         Normal    Scheduled           pod/zarf-docker-registry-789d8ddfb8-4pfgj    Successfully assigned zarf/zarf-docker-registry-789d8ddfb8-4pfgj to aks-agentpool-40722291-vmss000000
14m         Normal    Pulling             pod/zarf-docker-registry-789d8ddfb8-4pfgj    Pulling image "<IP_ADDRESS>:32178/library/registry:2.7.1"
14m         Warning   Failed              pod/zarf-docker-registry-789d8ddfb8-4pfgj    Failed to pull image "<IP_ADDRESS>:32178/library/registry:2.7.1": rpc error: code = Unknown desc = failed to pull and unpack image "<IP_ADDRESS>:32178/library/registry:2.7.1": failed to resolve reference "<IP_ADDRESS>:32178/library/registry:2.7.1": failed to do request: Head "https://<IP_ADDRESS>:32178/v2/library/registry/manifests/2.7.1": http: server gave HTTP response to HTTPS client
14m         Warning   Failed              pod/zarf-docker-registry-789d8ddfb8-4pfgj    Error: ErrImagePull
34s         Normal    BackOff             pod/zarf-docker-registry-789d8ddfb8-4pfgj    Back-off pulling image "<IP_ADDRESS>:32178/library/registry:2.7.1"
13m         Warning   Failed              pod/zarf-docker-registry-789d8ddfb8-4pfgj    Error: ImagePullBackOff
15m         Normal    SuccessfulCreate    replicaset/zarf-docker-registry-789d8ddfb8   Created pod: zarf-docker-registry-789d8ddfb8-4pfgj
15m         Normal    ScalingReplicaSet   deployment/zarf-docker-registry              Scaled up replica set zarf-docker-registry-789d8ddfb8 to 1

output of kubectl -n zarf get all
NAME                                        READY   STATUS             RESTARTS   AGE
pod/injector                                1/1     Running            0          40m
pod/zarf-docker-registry-789d8ddfb8-4pfgj   0/1     ImagePullBackOff   0          40m

NAME                           TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)          AGE
service/zarf-docker-registry   NodePort   <IP_ADDRESS>     <none>        5000:31999/TCP   40m
service/zarf-injector          NodePort   <IP_ADDRESS>   <none>        5000:32178/TCP   40m

NAME                                   READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/zarf-docker-registry   0/1     1            0           40m

NAME                                              DESIRED   CURRENT   READY   AGE
replicaset.apps/zarf-docker-registry-789d8ddfb8   1         1         0       40m

Severity/Priority
😕  Blocked on deploying zarf packages to Azure AKS

We haven't run into this issue on AKS before, but it looks like the node container runtime is trying to call localhost via https vs http, which is the standard for containerd and crio.  Is there any special config or other details about this provisioning that might change the container runtime by chance?
Would be helpful to run 'zarf destroy --confirm --remove-components' and then 'zarf init -l=trace'.
Sorry if markdown is weird, using the GitHub app right now.

Thanks @erikschlegel this definitely looks like a CRI change on AKS we'll need to play with a bit, I'll spin up AKS again this weekend to see if we can reproduce it.  Are you provisioning AKS with IaC or via the Azure web interface?

I'm provisioning the cluster directly through the Azure Portal. I confirmed that I was able to initialize zarf usong K8 version 1.21. I suspect this is a containerd issue as it's configured slightly different on AKS version 1.22+. This is worth checking out https://github.com/Azure/AgentBaker/pull/1369/files#diff-fb591749d1d0d4f2901cce9539d1ddae91a0389dfccd96bc7822ea0a6f9e35f2

@jeff-mccoy Any update on this?

Hi @jeff-mccoy - AKS K8 version 1.21 is no longer available for deployment in the portal and now none of the AKS supported versions appear to work with zarf. Do you happen to have an update?

I can confirm this is still an issue.

Hello, I am experiencing the same issue. Here is my output from kubectl describe pods:
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  48s                default-scheduler  Successfully assigned zarf/zarf-docker-registry-796648965f-2fjw5 to aks-demo-97972695-vmss000000
  Normal   BackOff    19s (x2 over 48s)  kubelet            Back-off pulling image "<IP_ADDRESS>:32380/library/registry:2.7.1"
  Warning  Failed     19s (x2 over 48s)  kubelet            Error: ImagePullBackOff
  Normal   Pulling    8s (x3 over 48s)   kubelet            Pulling image "<IP_ADDRESS>:32380/library/registry:2.7.1"
  Warning  Failed     8s (x3 over 48s)   kubelet            Failed to pull image "<IP_ADDRESS>:32380/library/registry:2.7.1": rpc error: code = Unknown desc = failed to pull and unpack image "1
<IP_ADDRESS>:32380/library/registry:2.7.1": failed to resolve reference "<IP_ADDRESS>:32380/library/registry:2.7.1": failed to do request: Head "https://<IP_ADDRESS>:32380/v2/library/registry/manifest
s/2.7.1": http: server gave HTTP response to HTTPS client
  Warning  Failed     8s (x3 over 48s)   kubelet            Error: ErrImagePull

version 21.2 in an Azure US Government AKS cluster

Yeah they must be doing something special, containerd upstream still serves localhost on http and even tests for it, digging into this more this week:  https://github.com/containerd/containerd/blob/main/pkg/cri/server/image_pull_test.go

While we work on this, as a note on a potential work around, you can also use an external registry as described here: https://docs.zarf.dev/docs/user-guide/the-zarf-cli/cli-commands/zarf_init
Under the Integrations tab in the Azure console you can tie an Azure Container Registry to your cluster and then init it with something like this:
zarf init --registry-push-password={PASSWORD} --registry-push-username={USERNAME} --registry-url={REGISTRY}.azurecr.io
(you can also specify a separate --registry-pull-password and --registry-pull-username and can load the username(s)/password(s) from a zarf-config.toml as described here: https://docs.zarf.dev/docs/user-guide/the-zarf-cli/cli-commands/zarf_prepare_generate-config#synopsis)

Put some notes in a new issue after digging around a bit.  Will try to test an older version of AKS later on tonight.

Also tested on AKS 1.22.11 and seeing the same results.

Added some new notes at https://github.com/Azure/AKS/issues/3303#issuecomment-1306328925.
Looks like a bug in containerd that was patched 2 weeks ago. In the interim, Acorn ran into this issue too and did what we've been trying to avoid (modify the containerd config).  Root cause is the change @erikschlegel identified to allow containerd registry config overrides in AKS actually highlighted the underlying containerd issue.

@cheruvu1 if you have any other data you'd like to drop on this issue, please leave it here. Thanks!

hi folks, as a workaround (that includes patch by iceberg you can update containerd in your cluster.
Just apt update and upgrade the node. I do it through a DaemonSet (example):
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: update-cluster
  labels:
    app: update-cluster
spec:
  selector:
    matchLabels:
      app: update-cluster
  template:
    metadata:
      labels:
        app: update-cluster
    spec:
      containers:
      - name: update-cluster
        image: alpine
        imagePullPolicy: IfNotPresent
        command:
          - nsenter
          - --target
          - "1"
          - --mount
          - --uts
          - --ipc
          - --net
          - --pid
          - --
          - sh
          - -c
          - |
            # apt update and upgrade
            export DEBIAN_FRONTEND=noninteractive apt update && apt upgrade -y
            sleep infinity
        securityContext:
          privileged: true
      dnsPolicy: ClusterFirst
      hostPID: true

I was able to initialize zarf:

I did also deploy the Big Bang into AKS, but has couple of "bumps"

if aks has more than one node the zarf init fails because of a pvc already being claim (zarf registry)
gatekeeper has the label control-plane: controller-manager in their NS... preventing the hook to change the image ... after removing it, everything went smoothly.

Incurred this problem while attempting to initialize zarf on a Nutanix kubernetes cluster running v1.22.9 of kubernetes and 1.6.6 of containerd.

NAMESPACE     NAME                                                         READY   STATUS             RESTARTS   AGE
kube-system   aws-node-4k6m4                                               1/1     Running            0          111m
kube-system   aws-node-9s5gv                                               1/1     Running            0          111m
kube-system   aws-node-qxgrn                                               1/1     Running            0          111m
kube-system   aws-node-termination-handler-79dbd64446-svh7r                1/1     Running            0          17h
kube-system   cluster-autoscaler-aws-cluster-autoscaler-65b5fb5c6f-tlf4d   1/1     Running            0          17h
kube-system   cluster-proportional-autoscaler-coredns-6ccfb4d9b5-gvrnc     1/1     Running            0          17h
kube-system   coredns-b5bccb59b-cqlxx                                      1/1     Running            0          17h
kube-system   coredns-b5bccb59b-xwsq9                                      1/1     Running            0          17h
kube-system   ebs-csi-controller-6b7c4667c4-kk6s2                          6/6     Running            0          17h
kube-system   ebs-csi-controller-6b7c4667c4-xv8wx                          6/6     Running            0          17h
kube-system   ebs-csi-node-dthh8                                           3/3     Running            0          17h
kube-system   ebs-csi-node-h88hj                                           3/3     Running            0          17h
kube-system   ebs-csi-node-mtxgt                                           3/3     Running            0          17h
kube-system   kube-proxy-dhkmt                                             1/1     Running            0          17h
kube-system   kube-proxy-t4mvh                                             1/1     Running            0          17h
kube-system   kube-proxy-zgwnl                                             1/1     Running            0          17h
kube-system   metrics-server-7cd9d56884-ffhbw                              1/1     Running            0          17h
zarf          injector                                                     1/1     Running            0          15m
zarf          zarf-docker-registry-7c64687bfc-547xp                        0/1     ImagePullBackOff   0          14m

Events:
Type     Reason                  Age                From                     Message

Normal   Scheduled               65s                default-scheduler        Successfully assigned zarf/zarf-docker-registry-7c64687bfc-547xp to ip-10-1-10-64.us-gov-east-1.compute.internal
Normal   SuccessfulAttachVolume  63s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-82baccc9-bcf0-4bb6-8c18-fead693b07cd"
Normal   Pulling                 30s (x2 over 55s)  kubelet                  Pulling image "<IP_ADDRESS>:30778/library/registry:2.8.1"
Warning  Failed                  20s (x2 over 45s)  kubelet                  Failed to pull image "<IP_ADDRESS>:30778/library/registry:2.8.1": rpc error: code = Unknown desc = failed to pull and unpack image "<IP_ADDRESS>:30778/library/registry:2.8.1": failed to resolve reference "<IP_ADDRESS>:30778/library/registry:2.8.1": failed to do request: Head "https://<IP_ADDRESS>:30778/v2/library/registry/manifests/2.8.1": net/http: TLS handshake timeout
Warning  Failed                  20s (x2 over 45s)  kubelet                  Error: ErrImagePull
Normal   BackOff                 5s (x2 over 44s)   kubelet                  Back-off pulling image "<IP_ADDRESS>:30778/library/registry:2.8.1"
Warning  Failed                  5s (x2 over 44s)   kubelet                  Error: ImagePullBackOff

EKS v1.23 works without issue because it is still using docker vs. containerd

quick update, containerd was updated and I could deploy bigbang 1.48.0. Ticket can be closed ;) thanks for your help

Tracking EKS AMI containerd update: awslabs/amazon-eks-ami#1162

Upstream issue has been closed and @brianrexrode has successfully tested zarf v0.25.2 with EKS V1.26

@AbrohamLincoln thanks for the note! We're looking at exploring other options too, and for others this will affect newer versions of containerd 1.7 (>1.7.7) (and 2.0 if anyone is on the betas) as well.

Seeing similar behavior on EKS 1.26  - 1.29 all of which are using containerd 1.7.11. Zarf init was previously (late January) working on EKS 1.26 with containerd 1.7.2. Confirmed that going back to EKS 1.23 with docker runtime 20.10.25 does work, but that version is out of service.

Seeing this on RKE2 1.27 as well with upgrade to containerd v1.7.7

Hi guys. Any plans here? Still having a problem with k8s 1.27+ versions with containerd 1.7.11.
Any recommendations from the community on how we can "tune" a containerd config to avoid this issue?

Hi guys. Any plans here? Still having a problem with k8s 1.27+ versions with containerd 1.7.11.
Any recommendations from the community on how we can "tune" a containerd config to avoid this issue?

Commenting out the containerd config lines mentioned in this post got things working again for me.

Also ran into this issue on newer RKE2 versions. It seems linked back to this commit which introduced the config_path line. The containerd update to 1.7.7+ actually did not immediately cause the issue (RKE2 1.29.0 works and is on containerd 1.7.11), it was specifically the introduction of that containerd config line 👀.
Just for reference affected versions of k3s/rke2 appear to be 1.29.1+, 1.28.6+, and 1.27.10+. Definitely curious if there is anything to address this on the zarf side or if this should make its way into the docs as a recommended pre-req/setup for the cluster?

All things coming around, we may need to look to a way to avoid the localhost/http behavior since containerd has introduced bugs multiple times for this in the past year or so. https://github.com/containerd/containerd/pull/9188

A new issue has been opened against containerd to address this: https://github.com/containerd/containerd/issues/10014

Hi guys. Any plans here? Still having a problem with k8s 1.27+ versions with containerd 1.7.11.
Any recommendations from the community on how we can "tune" a containerd config to avoid this issue?

Commenting out the containerd config lines mentioned in this post got things working again for me.

Does anyone know if this config line fix is in the default zarf init version of k3s?
I've been playing around with this issue and am observing the ImagePullBackOff for the zarf-docker-registry in various versions of containerd when I connect to a cluster I started on my own, but not when I use the K3S that Zarf initiates as part of zarf init.

Kubernetes Version
Container-Runtime
CR version
zarf-docker-registry init
Zarf K3S

v1.28.8+k3s1
containerd
1.7.10
Fails
No, Rancher Desktop

v1.28.8+k3s1
docker
24.0.7
Works
No, Rancher Desktop

v1.28.8+k3s1
containerd
1.7.11-k3s2
Fails
No, standard K3S install

v1.28.4+k3s2
containerd
1.7.7-k3s1
Works
Yes

Error message observed when it fails
err="failed to \"StartContainer\" for \"docker-registry\" with ImagePullBackOff: \"Back-off pulling image \\\"<IP_ADDRESS>:31585/library/registry:2.8.3\\\"\"" pod="zarf/zarf-docker-registry-6c9d98c95d-z7k6r"

A fix has been merged in and backported to 1.7 and pending 1.6 for containerd: https://github.com/containerd/containerd/pull/10109
I have not tested the fix myself yet, but hoping it resolves this issue 🤞

Containerd fix has been released in v1.7.16: https://github.com/containerd/containerd/releases/tag/v1.7.16


docs: add WSL installation guide

Relates to:
AI Agent Dev School Video 1 : https://www.youtube.com/watch?v=ArptLpQiKfI
Risks
Low
Background
Shaw suggests using WSL to code with Eliza but there are some steps missing from the instructions in order for installation to work.
What does this PR do?
Fixes pnpm installation error when using WSL for the first time.
What kind of change is this?
Documentation
Why are we doing this? Any context or related work?
Documentation changes needed?
My changes require a change to the project documentation.

Testing

Verified all commands work in a fresh WSL installation
Confirmed formatting matches existing documentation

Where should a reviewer start?
Video:
https://www.youtube.com/watch?v=ArptLpQiKfI
Detailed testing steps

none

GM @jkbrooks thanks for approving! I just realized I put down node 20 instead of 23 for step 3. I also didn't write code to make the guide visible, I figures you guys would decide where it best fits in the docs. Cheers.

okay, reverted for now @ileana-pr https://github.com/ai16z/eliza/pull/959


Symbol’s value as variable is void: wend

When I search with :ag and I hit return on one of the occurrences I get this error:
nlinum-hl-flush-window: Symbol’s value as variable is void: wend

Sorry, this is a problem with nlinum-hl, I've fixed it upstream in https://github.com/hlissner/emacs-nlinum-hl/commit/294037f5231375ac63836637651585f8b82b962d

Forgot to mention: while we wait for Melpa to pull the update you can fix this with (remove-hook 'nlinum-mode-hook #'nlinum-hl-mode)

Thanks

With #59 almost resolved, I've removed nlinum-hl entirely in https://github.com/hlissner/.emacs.d/commit/7ba22d0d8676907d83db9f6b7f5575583309ff0e. If you update, this problem should be gone either way.


Add Tuya _TZE204_p3lqqy2r

Proposed change

Adds _TZE204_p3lqqy2r
Additional information

Fixes: https://github.com/zigpy/zha-device-handlers/issues/2868
Closes: https://github.com/zigpy/zha-device-handlers/pull/3565
Checklist

[X] The changes are tested and work correctly
[X] pre-commit checks pass / the code has been formatted using Black
[X] Tests have been added to verify that the new code works

Everything is working as it should now.


Edit CSS Live can not @import google fonts?

Bug description
I try to @import google font in Edit CSS Live section. It not effect ???
@import url('https://fonts.googleapis.com/css2?family=Prompt:ital,wght@0,100;0,200;0,300;0,400;0,500;0,600;0,700;0,800;0,900;1,100;1,200;1,300;1,400;1,500;1,600;1,700;1,800;1,900&display=swap');
body{
font-family:'Prompt';
}
Screenshots/recordings
No response
Superset version
4.1.1
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

You can, but dosubot is rigjt... you will have to punch a hole in TALISMAN_CONFIG for it.

Closing this since it's not a bug, but a question that's now been answered. Holler if you have any further troubles with it :)


library build & UT running on netstandard

please check and let me know if this helps!

Sweet! I'll check this out in the next 2 days. Sorry I can't be more specific than that.

And I didn't get to it like I wanted to. Holiday havoc and all. My apologies.

Hey, no problem. Happy Holidays and I'm glad if i can be of help!

@ckolumbus I noticed there's a failed unit test "ShouldBeAbleToUseMultipleTheFirsts()"... it's been in the master branch for a long time. What do you think we should do about it?

@lorddev I'll check on Tuesday, right now we're on Easter holiday

This issue was resolved in Issue #55


[dv] Verify ICache Integrity and Scrambling

Verify the ICache integrity and scrambling features
For integrity create a testbench component to corrupt icache data and icache tags. Ensure corruptions triggered the required alert. This will require targeting to corrupt data and tags that relate to instructions that are going to get execute. Understanding of scrambling will need to be employed to determine the appropriate memory locations to corrupt.
For scrambling I'm uncertain if we need to do anything further as we're using a existing OT primitive component. @ctopal any thoughts from your OTBN experience?
old estimate 16, new estimate based upon more detailed analysis by @andreaskurth

estimate 4
remaining 2022-10-28 1

In OTBN, this checking of responses to integrity failures is done as this:

Read scrambled data from RAM using encrypt_sram_addr and decrypt_sram_data from sram_scrambler_pkg.
Apply 1 or 2 bit flips to generate an integrity error when said data gets read back.
Write corrupted data to scrambling memory using encrypt_sram_addr and encrypt_sram_data from sram_scrambler_pkg.

A task will need to include incorporating  sram_scrambler_pkg to our core_ibex DV environment (or maybe block level ICache DV environment?) and writing up the sequence that uses the functionality mentioned above.
For verifying scrambling itself, OTBN side maps smoke and calls it a day (not sure if it's good to do that, maybe we need to have a talk about it as well?) https://github.com/lowRISC/opentitan/pull/13335#discussion_r903922037

I've looked into the integrity verification, and I think the following approach should work:

For each data and tag memory, track which memory entries have been written thus contain valid values (using the req_i, write_i, and addr_i signals).
For each data and tag memory, track which memory entries are being read (using the same three signals). If an entry is being read that has been written before, corrupt one bit in the output data with a certain probability.
If the corruption happened, check that the required alert is fired.

I'm estimating 4 for that.

Thanks @andreaskurth I will update the estimate with your new one and assign you to the issue.

Closing this as completed in #1879.


Augment subjects with Indigenous Studies where appropriate

Using a list of subject terms provided by PUL catalogers, at index time
add the term "Indigenous Studies" where appropriate.
Work toward #1548

It looks great. We exported a fixture form Alma and tested locally the changes. The subject keyword search works and the show page display the desired term. I will approve the pr but it should not be merged before https://github.com/pulibrary/orangelight/issues/2755 is done and tested on staging.


fix: inputs height on validation

Related issue

Closes #1027
Scope of work

add min-height to input and select
fix styles
add form template example

Screenshots of visual changes

Checklist

[ ] No commented blocks of code left
[ ] Run tests and docs
[ ] Self code-reviewed

If applicable:

[ ] I followed composition rules for my component
[ ] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)
[ ] I accept Individual Contributor License Agreement

awesome, thanks @martaradziszewska 💚


App has been crashed suddenly

Flutter doctor -v
[√] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.18363.1110], locale en-US)
• Flutter version 2.0.1 at C:\Users\nabil\AppData\Local\Flutter_sdk_1.9.1\flutter
• Framework revision c5a4b4029c (6 weeks ago), 2021-03-04 09:47:48 -0800
• Engine revision 40441def69
• Dart version 2.12.0
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at C:\Users\nabil\AppData\Local\Android\sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
[√] IntelliJ IDEA Community Edition (version 2019.2)
• IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA Community Edition 2019.2.1
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
[√] Connected device (3 available)
• Mi 9 Lite (mobile) • f893814a • android-arm64  • Android 10 (API 29)
• Chrome (web)       • chrome   • web-javascript • Google Chrome 89.0.4389.114
• Edge (web)         • edge     • web-javascript • Microsoft Edge 89.0.774.75
• No issues found!
This error :
E/Dart    (17978): ../../third_party/dart/runtime/vm/timeline.cc: 671: error: unimplemented code
E/DartVM  (17978): version=2.12.0 (stable) (Thu Feb 25 19:50:53 2021 +0100) on "android_arm64"
E/DartVM  (17978): pid=17978, thread=18372, isolate_group=main(0x7083daf300), isolate=(nil)(0x0)
E/DartVM  (17978): isolate_instructions=7021d14b00, vm_instructions=7021d14b00
E/DartVM  (17978):   pc 0x0000007021e15904 fp 0x0000007084e64710 /data/app/com.roaa_tech.saeed-rq6FiZUgcESYxfjoqDUGHA==/lib/arm64/libflutter.so+0x17d1904
E/DartVM  (17978): -- End of DumpStackTrace
F/libc    (17978): Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 18372 (DartWorker), pid 17978 (roaa_tech.saeed)

Build fingerprint: 'Xiaomi/pyxis/pyxis:10/QKQ1.190828.002/V<IP_ADDRESS>.QFCMIXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2021-04-13 12:28:25+0300
pid: 17978, tid: 18372, name: DartWorker  >>> com.roaa_tech.saeed <<<
uid: 10266
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
x0<PHONE_NUMBER>000000  x1<PHONE_NUMBER>0047c4  x2<PHONE_NUMBER>000006  x3<PHONE_NUMBER>e64690
x4<PHONE_NUMBER>000000  x5<PHONE_NUMBER>000000  x6<PHONE_NUMBER>000000  x7<PHONE_NUMBER>800000
x8<PHONE_NUMBER>0000f0  x9  ceeac7175e71f2bc  x10<PHONE_NUMBER>000001  x11<PHONE_NUMBER>000000
x12 fffffff0fffffbdf  x13<PHONE_NUMBER>000003  x14<PHONE_NUMBER>000002  x15<PHONE_NUMBER>bf0e7d
x16<PHONE_NUMBER>724738  x17<PHONE_NUMBER>703180  x18<PHONE_NUMBER>3d0000  x19<PHONE_NUMBER>00463a
x20<PHONE_NUMBER>0047c4  x21 00000000ffffffff  x22<PHONE_NUMBER>00463a  x23<PHONE_NUMBER>000000
x24<PHONE_NUMBER>1c67a0  x25<PHONE_NUMBER>1d5000  x26 000000707faa9f10  x27<PHONE_NUMBER>09bf28
x28<PHONE_NUMBER>1d5000  x29<PHONE_NUMBER>e64730
sp<PHONE_NUMBER>e64670  lr<PHONE_NUMBER>6b486c  pc<PHONE_NUMBER>6b4898
backtrace:
#00 pc<PHONE_NUMBER>073898  /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 745f6147935e4ea7837d3e6fc6def1e1)
#01 pc<PHONE_NUMBER>6cfce8  /data/app/com.roaa_tech.saeed-rq6FiZUgcESYxfjoqDUGHA==/lib/arm64/libflutter.so (BuildId: 4f453a1bb64d1244a9dd8bd68e926b4779043b43)
#02 pc<PHONE_NUMBER>a516a4  /data/app/com.roaa_tech.saeed-rq6FiZUgcESYxfjoqDUGHA==/lib/arm64/libflutter.so!libflutter.so (offset 0x1a1a000) (BuildId: 4f453a1bb64d1244a9dd8bd68e926b4779043b43)
Lost connection to device.

@nabil-hfz
Can you provide a complete minimal reproducible code sample that we can use to replicate this issue locally ?
Thanks.

@darshankawar
Actually it's a big project and belongs to the company that I work with, so I can not provide  a complete minimal code.
If you want we can skip it

/cc @bkonyi @rmacnak-google seems like a crash writing timeline events to JSON

This is going to be a tricky one without a reproduction case as we're running into an unrecognized timeline event type. I'm guessing this is coming through an event posted through the C API in the engine, but it's hard to say. @mraleph are we able to symbolize anything from this crash report?

@nabil-hfz
Can you provide more details if possible like, when does it crash, ex: upon launch or while interacting with it ? Is there a pattern to it which leads to this crash ?

@bkonyi this one does not symbolise to anything useful, but there is one more https://github.com/flutter/flutter/issues/75410 which has a full stack
I briefly looked at the code but I can't really say I understand what exactly can go wrong here, except that we maybe try to serialise either corrupted or not-fully initilized event (maybe event type is somehow set to kNone?).


[Syntax lookup] Add doc for explicit string interpolation

Another proposal for https://github.com/rescript-association/rescript-lang.org/issues/162

[ ] `` (explicit string interpolation)

Probably a mistake from my side for defining it as a explicit string interpolation syntax... it should actually just be called string interpolation syntax.
The older formats like j`` should not be used anymore anyways.


Argo API Server

Currently Argo UI is powered by a lightweight API server written in node, is readonly, and can only do visualization of workflows.
We plan to have a more formalize API server, rewritten in go, which can handle things like submit, resubmits, retries, deletes, suspend, resume, etc...
The API server should also be able to run locally. e.g.:
argo server

Which would then make the api server available via https://localhost:8080, to manage workflows using the current kubeconfig context.
The API server would also work in tandem with the controller's persistence configuration, allowing workflows to be listed from a database (instead of kubernetes API).

Diagram explaining the proposed authentication mechanism:

The idea is that we will be trying very hard not to have our own RBAC, and rely on existing kubernetes RBAC. For this to work, the Argo API server would make K8s API requests using forwarded credentials supplied by the client, basically acting as a proxy to the requests.

Thanks for the awesome work btw.!
Just wanted to mention that there is a huge demand for this feature, so we don't have to do this by ourselves by getting it out of the "raw" DB by ourself (with 2.4.0 out :heart: ).


Chapter 4 / cancelling-requests-and-resetting-state is not working as it should

I just commented promise.cancel() as said in the book(4th Edition) and i am not getting error as said in the book.
Please fix the package.json (I guess).Maybe this problem of cleaning was in older versions.

I just modified package.json as
    "bluebird": "^3.5.5",     "react": "^17.0.0",     "react-dom": "^17.0.0",     "react-scripts": "^4.0.3"
and index.js as
import App from "./App";
import React from 'react';
import ReactDOM from 'react-dom';

const rootElement = document.getElementById("root");
ReactDOM.render(<App />, rootElement);

This change is showing error.Please update the code.


Add way to specify CMAKE_GENERATOR_TOOLSET by using option -T

https://cmake.org/cmake/help/v3.12/variable/CMAKE_GENERATOR_TOOLSET.html

Sorry for the delay. I've been busy with other projects.
CMake Tools should already support this via the cmake.toolset option, or the toolset option in a Kit. Do these options support your use case?

not document at https://vector-of-bool.github.io/docs/vscode-cmake-tools/kits.html

It's already been fixed.


Fix error on release dates

Pull Request Test Coverage Report for Build 667476480

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 662760432:
0.0%

Covered Lines:
2878

Relevant Lines:
2878

💛  - Coveralls

Awesome! Thank you! 👍


Retries can be 0

Giving a chance to set retries to 0. The errors from micro service may not be just some network error, but also created by application. For example, we notify user the password is wrong by returning error. On this situation, I don't want the gateway to request twice.

What if it's a negative number? The logic should stay the same just >=

Did you gofmt?

I editted the file using the online editor.


Allow opening scenes in text editor

It is sometimes useful to read the scene code or even edit it. But looks like now it's only possible through external means.
To avoid confusion inside editor, it'd be nice to have separation in document list (e.g. groups like "scripts", "scenes", "misc")

Is this (a slightly far-fetched) duplicate of #1390, per chance?

I would say it's more of an addition to it, because it means adding some special action of opening scene in text editor (rather than just using file->open) and hopefully some syntax highlighting.

For now I'll close this as strictly dependent on #1390 (can't happen without the former being implemented), and I'll add a mention there of potential scene-specific features in the text editor. Eventually if/when #1390 is being worked on, this issue could be reopened if need be to track the scene-specific changes separately.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1034 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit fcacc71:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-02-14-01-53-17 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Move MSU Commons groups and site onto HCommons

The admin of the STEM Ed PaCER would like their site and two groups (STEM Ed PaCER Meet the Mentors and STEM Ed PaCER Internal Project Workspace)  moved from MSU Commons to HCommons.

STEM Ed PaCER is now at https://stemedpacer.hcommons.org/
STEM Ed PaCER Meet The Mentors is now at https://stemedpacermeetthementors.hcommons.org/
The old commons.msu.edu URLs redirect to the new sites.
I created a script to change group type here: https://github.com/MESH-Research/dev-scripts/blob/master/commons/change-group-type.php
But that doesn't move the discussion forum or discussion posts, which breaks the group. This is a challenge because the discussions and discussion posts are in the MSU posts table and would need to be exported and then imported into the HC posts table, and then linked back up to the groups. Making this work correctly will take some significant work. If possible, it would be far quicker to just recreate the groups.


Use vendored_libraries

This is the right way to ship a prebuilt library as a Pod. Once CocoaPods/CocoaPods#3859 is merged, this will mean that CardIO also works fine when users are integrating with use_frameworks!
cc @keith

+1 this fixes https://github.com/card-io/card.io-iOS-SDK/issues/115

+1

Sorry for the delay. Unfortunately, I'm not qualified to review this.
@dgoldman-ebay what do you think?
@neonichu I presume that you read the thread at #115 and that this is compatible with our policy of supporting the two most released iOS versions (so right now, iOS 7 and iOS 8)?

@josharian yes, this doesn't change that in any way.

After further look @neonichu this particular pod spec brings a new issue into play
target has transitive dependencies that include static binaries
Seems to be consistent with this https://github.com/CocoaPods/CocoaPods/issues/3194

@flippinjoe21 yes, you won't be able to use Pods which depend on CardIO when integrating with frameworks until it is a dynamic framework.
It can however be used directly by apps.

@burnto thoughts?

+1

@neonichu forgive me if I'm wrong but I tried using your version of the Spec in a project that has a private Spec using CardIO as a dependency. This fails with the "target has transitive dependencies that include static binaries" error.
Basically what I'm asking is: Is it possible to use a vendored library dependency across two or more pods?
My setup is as follows:

An internal spec: lets call it Checkout. This spec uses CardIO as a dependency
An Example project for checkout now declares pod 'Checkout', :path = '..'
In order to get the example project to work with frameworks I set use_frameworks! and then reference your fork so that we get vendored library support (pod 'CardIO', :git => 'https://github.com/neonichu/card.io-iOS-SDK')

This fails because the library is now linked to Checkout and Example. The only solution I can think of is forking your spec and pushing it to an internal repository(with a different name) so that I don't have to reference it in the podfile.
My understanding is that by using frameworks I can not have two or more pods that reference the same library?

@danielgalasko to be used as a transitive dependency when integrating as frameworks, vendored libraries need to be dynamic.

Thanks @neonichu!

:green_apple:
Looks reasonable to me. Thanks @neonichu

Thanks, @burnto!

does this merge mean we can use CardIO with use_frameworks! now?

@jlubeck Yes it does, as long as its not a dependency for more than one of your pods. Try it on a new installation, its possible you might need to clean your project:)

I tried a brand new project which you can see here: https://github.com/jlubeck/CardIO-SwiftTest
But it still doesn't work. Any ideas?

Hmm @jlubeck So I think you're misunderstanding what actually happens with the vendored_libraries.   All this does is tell any libraries defined in the vendored_libraries to be linked in to the top-level project so that the symbols can be found.   This does not create a module.   Because you cannot include static library within a .framework.
So in order to have your project work the way you expect.   You would have to have a bridging header, and #import <CardIO/CardIO.h>.  Then you can use it in your swift project without importing the module

Ok, I must've missunderstood. I used the bridging header and everything works fine with that.
Will it ever work without the header and just an Import CardIO like other libraries? Just curious.
Thanks!

I'm not 100% sure.  That is up to the cocoa pods team.   There is a discussion about handling it here.
https://github.com/CocoaPods/CocoaPods/issues/3701

I'm slightly confused.
What then is the difference between a pod that has vendored_libraries set to a .a file and has public_header_files set to a collection of headers compared with a pod that sets the preserve_paths to a .a file, libraries set to the name of that .a file (which sets the OTHER_LINKER_FLAGS), and finally sets the xcconfig LIBRARY_SEARCH_PATHS to point to the path to the .a and header files?
It is my understanding that vendored_libraries signals to CocoaPods that "the library is to be linked in to the top-level project so that symbols can be found", without creating a module, which can't be used within the context of a dynamic dependency (framework). I'm assuming that without vendored_libraries set, this linking to the top-level project will not happen for the second scenario.
Is the second scenario considered a "fake" framework? If so, I was under the impression that they couldn't be used when integrating with dynamic dependencies.
I have a situation where a dynamic dependency requires Google Analytics, which is currently still a vendored library, while also requiring CrittercismSDK, which isn't a vendored library but instead has a podspec similar to the second scenario mentioned above. Google Analytics throws the transitive dependency contains static binary error during a pod install on an iOS app that has a dependency on a dynamic framework which has the dependency on Google Analytics. However, CrittercismSDK, which is a sibling of GA in my dependency tree, is not throwing any such errors and appears to be fine.
GoogleAnalytics 3.14: https://github.com/CocoaPods/Specs/blob/master/Specs/GoogleAnalytics/3.14.0/GoogleAnalytics.podspec.json
CrittercismSDK 5.4.5: https://github.com/CocoaPods/Specs/blob/master/Specs/CrittercismSDK/5.4.5/CrittercismSDK.podspec.json

More context about not being able to import CardIO from Swift here: https://github.com/card-io/card.io-iOS-SDK/issues/115#issuecomment-234332701

I've submitted a simple PR that accomplishes this https://github.com/card-io/card.io-iOS-SDK/pull/210
I will probably delete this fork regardless of whether or not the PR is merged so please do not depend on it in your projects.


Allow to specify securityContext for vaultConfigurer container

Preflight Checklist

[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.
[X] I agree to follow the Code of Conduct.

Problem Description
Vault operator does not allow to specify securityContext for the vaultConfigurer pod container, it only allows to specify the podSecurityContext for the whole pod
This is not sufficient in all cases. For example, we deploy in a managed rancher kubernetes cluster with strict security policies. All containers are forced to have the following security profile or they won't be scheduled:
securityContext:
  runAsNonRoot: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: [ "ALL" ]
  seccompProfile:
    type: RuntimeDefault

Some but not all of them can be set by using the pods security context on a pod level, however, e.g., allowPrivilegeEscalation and capabilities can only be set on a container level
This missing feature prevents us from using bank-vaults operator, because it is impossible for us to deploy the vaultConfigurer pod
Proposed Solution
Add a vaultConfigurerContainerSpec that allows to configure/extend container spec for vaultConfigurer - similar to the already existing vaultContainerSpec - to the VaultSpec API
Alternatives Considered
No response
Additional Information
No response

@ramizpolic any news on this? :) I think @msg-gregor is not the only one (we are at least 2 haha) to not be able to use bank vault in prod because of vaultConfigurerContainerSpec missing in a restricted environment. Would be amazing if faisable :)

@fakeNews-jpg (cool nickname btw), yes, we will focus on this in the upcoming weeks, will share more details once we start working on it

Along the same lines... feature request to also add it to the config-templating initContainer too, please.


preview screen

If you use the magic want the text is replaced. This is nice but it would be more nice if you would get a popup with a split screen or something to see what has been changed on you text. And only if you sure you accept the changes.
Would it be possible to make this popup so that it works with a diff. Like git conflicts and you need to merge it ? Then you can accept a rewrite line per line if needed :)

Thanks @onno-timmerman! I think we'll be covering this as part of #60 #61 and #62, but if you're thinking of something else please feel free to reopen.


Update store-policies.md

See https://github.com/microsoft/microsoft-ui-xaml/issues/8213.

Looks good; thanks, @JaiganeshKumaran


SIM-BE-Add production WSGI server for backend and webrequest containers

We have identified that the backend is running using the Werkzeug development server in debug deployment. This is evidenced by the following warning message:
WARNING | Werkzeug appears to be used in a production deployment. Consider switching to a production web server instead.
Also, using the Flask development server to run the application in a production environment is not recommended due to performance and security concerns:

Performance Limitations: The development server is not optimized for handling high traffic loads and concurrent requests. Flask is a single-threaded application.
Security Risks: It lacks essential security features and may expose debugging information that could be exploited.
Stability Concerns: The server is not designed for long-term stability required in production settings.

Recommendation:
To ensure optimal performance, security, and stability, it is recommended to replace the Werkzeug development server with a production-grade server. Consider using one of the following options:

Gunicorn: A Python WSGI HTTP server suitable for UNIX. Widely used in production environments; compatible with various web frameworks.
Waitress: A pure-Python WSGI server with support for both Python 2 and 3.
uWSGI: A full-stack server for hosting Python WSGI applications.
gevent: A coroutine-based Python networking library that can be used as a WSGI server.
eventlet: A concurrent networking library for Python supporting WSGI.
ASGI Servers: For asynchronous applications, consider ASGI servers like Uvicorn or Daphne.

Action Items:

Evaluate Server Options: Assess the listed servers to determine the best fit based on our application's requirements and deployment environment.
Update Deployment Configuration: Replace the Flask and Werkzeug server with the chosen production server in the deployment scripts and configurations.
Testing: Conduct thorough testing to ensure the application runs smoothly with the new server and that there are no regressions.
Documentation: Update the project's documentation to reflect the changes in the deployment process.
Security Review: Perform a security assessment to ensure that the new server is properly configured and does not introduce vulnerabilities.

Benefits:

Improved Performance: Enhanced ability to handle multiple concurrent requests and higher traffic volumes.
Increased Security: Better protection against common web vulnerabilities and attacks.
Greater Stability: Improved reliability for long-running production environments.

@mentatbot


Accessory not supported

Hey guys. I have completed all the setup, all is running but I am getting 'Not supported in the Home app' on the accessory.
Did I miss something ? Thanks

Ok I added:
"alternate-playpause-switch": true,
and I can see it now appears as a switch but I am confused about using it. For example, I want to automate a sequence of buttons eg. menu, right, left. I have enabled input controls but I don't see them in the home app to start an automation. Thanks

Have you seen: https://github.com/grover/homebridge-dacp/blob/master/docs/configuration/macros.md
You have to predefine the sequence of keys in the config and it'll create a Power Switch for the sequence. Unlike described on the page it should also work in Apple Home.
Also please take a look at https://github.com/grover/homebridge-dacp/blob/master/docs/configuration/features.md
You need set more flags if you want this plugin to work with Apple Home. I plan to add a cross reference table with compatibility lists for each App and example configurations exposing all features.

Thanks Michael. I'll play around with this. Have waited for a long time for a plugin like so thank you very much.

So this is what I am noticing with the below macro. The macro is designed to:

Go to the home screen
Go to the First app which is the TV app
Go two apps to the right and then go up to use the top shelf items. It scrolls along the top shelf 9 times and presses select to select the stream

Issues:

It doesn't go to the home screen and first app if I am somewhere else on the page
When it scrolls and finds the stream in the top shelf, it doesn't execute select

 "macros": {             "9": [               "topmenu",               "wait5s",               "topmenu",               "right",               "right",               "wait5s",               "up",               "right",               "right",               "right",               "right",               "right",               "right",               "right",               "right",               "right",               "select"
Thanks

Any ideas with this one ?

Macros are tricky to create. I start my macros with a sequence of topmenu, wait5s, left and up commands to make sure I'm on the main Apple TV screen on the top left.

Thanks I'll give that a go


AKS webservice deploy and Update

Package Name:
azureml.core.webservice
Package Version:
1.26.0
Operating System:
Linux
Python Version:
3.6.2

Describe the bug
Running a deployment step inside azureml Pipeline im getting a weird behavior when trying to deploy vs update.
The first time I run the pipeline everything works fine, the second time (webservice exists) so I want to Update it instead, I'm getting
FileNotFoundError: [Errno 2] No such file or directory: '/var/azureml-app/04374e9c-f034-440c-8433-8359dab1b6ac/predict.py'
To Reproduce
Steps to reproduce the behavior:
Create a Pipeline step that runs
    deployment_step = PythonScriptStep(
        script_name="deploy-model.py",
        source_directory="./src",
        compute_target=compute_target,
        runconfig=pipeline_run_config,
        allow_reuse=True,
    )

Inside deploy-model I deploy or Update depending on if the Webservice exists
    inference_config = InferenceConfig(
        source_directory="./",
        entry_script="predict.py",
        environment=env,
    )

    deployment_config = AksWebservice.deploy_configuration(autoscale_enabled=False,
                                                        num_replicas=1,
                                                        cpu_cores = 4,
                                                        memory_gb = 24,
                                                        )
    """ Search for the Webservice, and if it exists, Update Instead of deploy """

    try:
        service = Webservice(workspace=ws, name=endpoint)
        service.update(models=[my_model], inference_config=inference_config)
    except WebserviceException:
        """ Service did not exist, so lets create it from scratch """
        service = Model.deploy(ws, name=endpoint,
                    models=[my_model],
                    inference_config=inference_config,
                    deployment_target=aks_target,
                    deployment_config=deployment_config)

    service.wait_for_deployment(show_output=True)

Expected behavior
I expect the update to find the files just as model.Deploy finds them, seeing as the inference config is the same.

@shbijlan thank you for reporting, we will investigate this ASAP!

Closing legacy issue.
Please consider upgrading to AzureML v2 CLI/SDK. https://learn.microsoft.com/en-us/azure/machine-learning/concept-v2


Data saver toggle is shown ON even when the user turn off data saver toggle  after tapping on the “Restart To Switch” option from “Restart To switch OFF data saver” pop up.

Frequency: 100%
Repro App version: Play store (Internal Build) v1.8.2
Does not repro: Celo Alfa 1.8.0 (101848577)
Repro on device: Google pixel XL (8.1), Vivo 1606 (6.01)
Tested Account:<PHONE_NUMBER> / Backup key
Repro Steps:

Launch app and login with tested account
Tap on the Cog icon from the wallet tab.
Tap on  Data saver option from setting
Turn ON data saver toggle.
Enter PIN and make sure Toggle is ON now.
Turn OFF Data saver toggle.
Tap on Restart To switch option from “Restart To Switch OFF data Saver” pop up.
After Restart App navigate to Data saver and observe Data saver toggle is shown ON.

Current Behavior: Data saver toggle is shown ON even after user turned it OFF.
**Expected Behavior:**Data saver toggle should Turn OFF.
Investigation:
Some time Restart To switch OFF data saver” pop up is not shown and user is able to turn off dat saver toggle.
Attachment: DatasaverIssue.mp4 (Bug observe at 1:27 sec)

@jeanregisser Verified with App store v1.8.0 and able to reproduced the issue

Data saver toggle is shown ON even when the user turn off data saver toggle after tapping on the “Restart To Switch” option from “Restart To switch OFF data saver” pop up.

Attachment: DataSaverIssue.mov

Does not reproduce on v1.8.2

Hi @nityas i have verified issue on iOS test flight celo integration buid v1.8.2 (39) and Android: Play store build v1.8.2 and found that issue is still reproduced.

Data saver toggle is shown ON even when the user turn off data saver toggle after tapping on the “Restart To Switch” option from “Restart To switch OFF data saver” pop up.

Verified on : Iphone 6+ (12.4.5) , Google Pixel XL (8.1)
Please find the attachment for the same:
Attachment : IOS_DataSaverIssue.mp4

Verified with latest IOS test flight Valora build v1.0.0(6) and observed that issue is Fixed

Device Used: iPhone 5(12.4.5)


Support Colorized Output

Related to #34.
Many applications use colorized strings that start with \e[XXm. But Tuw doesn't.

On Windows, you can set ENABLE_VIRTUAL_TERMINAL_INPUT to console with SetConsoleMode.


Blur (Backdrop-Filter) not working

I'm submitting a ...  (check one with "x")
[x] Bug report => search github for a similar issue or PR before submitting
[ ] Feature request
[ ] Other, please describe

Tell about your platform

Vue.js version : 3.2.31
Browser name and version : Chrome(100.0.4896.88)|Edge (100.0.1185.44)|Firefox (FF does not support backdrop-filter yet)
This package version : 5.0.3

Current behavior
The Blur Option does not work (does not blur anything)
Expected behavior
Content behind the background should be blured
Minimal reproduction of the problem with instructions
Using default settings will already show that the background does not get blured, also additional options do not blur anything. The problem lies in the css setting of "opacity: 0.5" this does make the background div transparent but backdrop-filter does not work with the opacity value. A fix is to use "background: rgba(255,255,255,0.5) instead of "background: #FFF; opacity: 0.5". Then the blur does worl correctly.
Currently i added an addistional sass file which does these settings here:
.vld-parent{
    .vld-background{
        background: rgba(136,136,136,0.5) !important;
        opacity: 1 !important;
    }
}

So i get a grey background which is transparent with the blur working as it should.
Also maybe it would be wise to have different options for the opacity, where one is for the icon and one for the background.

Something might have broken during vue 2 to 3 upgrade.
I will check soon

The blur feature was taken from
https://bootstrap-vue.org/docs/components/overlay#overlay-backdrop-color

Maybe it was removed in a Webkit Update, when i look at the Page, it also does not show the blur effect:

When i modfify it in the developer console it works:

Thanks for update, i will look into it soon

You can make the blur effect working with a combination of these 3 props, see example:
let loader = this.$loading.show({
        backgroundColor: 'rgba(136,136,136,0.1)',
        opacity: 1,
        blur: '2px'
      });

Good that it can be worked around like that, question is if it would make sense to implement this into the component itself so it can set the values correctly internally, so that current users do not have to change their code.
Also there is a difference on this approach and the expected behavior from before, as now it sets the opacity to 1, the loader icon is not transparent anymore, thus it might be better to implement the change here into the component itself, as it can set the opacity of the icon to "0.1" and the overlay to opacity 1 but with background-color using the opacity value supplied as a property.
This would surely require a calculation from the standard css value "#888" to its corresponding rgb value. This could be difficult, as the component would also have to check which version the color was supplied to it, for example [#888, #888888, #88888819, rgb(136,136,136), rgba(136,136,136,0.1)]

It would be better to remove the blur feature, and let developer to style it.

The buggy prop has been removed in v6


Cayman refuses to work when other themes will

Minima works completely fine but Cayman just leaves me with every page blank except for my 404. Demonstration: https://comwriters.github.io

Was a problem with the theme not having the right type of page. Make sure your layout types are default and nothing else, @mjy625


Add ability to deliver initial static set of endpoints in CDS update when using EDS

This would prevent Envoy from sending 503 Service Unavailable responses, in the time between CDS and EDS updates, when Envoy didn't learn about available endpoints yet.
It could be implemented without changing existing API, in a backward-compatible way, by sending CDS update with type = EDS and non-empty list of hosts.
The question is whether provided list of hosts should be used only until first EDS update arrives, or also as a fallback.
cc @louiscryan @jmarantz @htuch @andraxylia @costinm

https://github.com/envoyproxy/envoy/issues/1930 is a different solution of the same problem.

What's preferable about this approach compared to the cluster warmup approach in #1930?
It seems that all you get here over cluster warmup is an small decrease in availability lag time for what is a previously nonexistent cluster. The cost is an API hack and whatever headaches come along with determining hosts to provide from your CDS implementation.
Meanwhile, if you really need the immediate consistency, you can always implement ADS and provide CDS/EDS results simultaneously right off the bat.
Your proposed mechanism seems ok for an optional fallback, but I think it shouldn't be the primary solution over cluster warmup. I don't know what the current story around EDS fallback is, though.

The context here is Istio 0.7, where they don't have ADS (or v2) yet.
@jsedgwick  If no EDS arrives today, you just have a dead cluster. If you have an EDS response and then the EDS server dies, we just latch the last response forever. I can see a potential use case for this solution to provide a way to fall back on some known endpoints (e.g. like a hospital service for bad requests) when EDS goes away. But, I haven't ever heard someone ask for this, so this issue is a good place to solicit this feedback.
My take is that I think CDS warming is the preferable solution, but if there is community interest in the above behavior for other reasons (e.g. low latency serving from new clusters), then it's worth adding.

@jsedgwick it's not strictly preferable, I think we should have both. Also, ADS doesn't really solve this problem, it just significantly shortens the time between CDS and EDS updates, but it's still non-zero.
The biggest advantage of this solution is that in case EDS is down (e.g. when CDS and EDS are separate services, or when Envoy is using static clusters with EDS), then you can still serve traffic (maybe with sub-optimal load assignments), instead of returning 503s.
Also, as @htuch mentioned, we need to fix 503s in Istio sooner rather than later, and the cost of implementing this solution is quite smaller than cluster warming.

@PiotrSikora I'm not thrilled about adding this feature when CDS cluster warming IMO is the real solution to this problem and fits really well with how we do LDS, etc. When is a solution needed by? What date do we need to deliver CDS warming before this becomes a real blocker?

In Istio we could use it by mid-March, when the next release 0.7 is planned.

@PiotrSikora @andraxylia I would prefer to implement CDS cluster warming. IMO this is a much better solution that a) fits well with how we do LDS and b) also will work for other cluster types including DNS. If I can do warming by mid-march is that sufficient?

@mattklein123 Mid-march would be great, thank you!

I'm going to go ahead and close this. I looked at CDS warming and it's not that difficult. I will do it in the next 2 weeks. If I don't deliver we can reopen and reconsider.


MIAD-214 /add-any-alert screen

MIAD-214

Codecov Report
Attention: Patch coverage is 58.05085% with 99 lines in your changes missing coverage. Please review.

Project coverage is 69.95%. Comparing base (467b332) to head (e3346b1).

Files with missing lines
Patch %
Lines

server/middleware/validationMiddleware.ts
15.15%
27 Missing and 1 partial :warning:

server/routes/common/controller.ts
18.51%
20 Missing and 2 partials :warning:

server/routes/add-any-alert/schemas.ts
20.83%
18 Missing and 1 partial :warning:

server/routes/add-any-alert/controller.ts
35.29%
11 Missing :warning:

server/utils/datetimeUtils.ts
62.96%
10 Missing :warning:

server/utils/viewUtils.ts
20.00%
7 Missing and 1 partial :warning:

server/middleware/authorisationMiddleware.ts
83.33%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #93      +/-   ##
==========================================
- Coverage   73.00%   69.95%   -3.06%
==========================================
  Files          54       61       +7
  Lines        1356     1531     +175
  Branches      198      238      +40
==========================================
+ Hits          990     1071      +81
- Misses        353      443      +90
- Partials       13       17       +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix List.isList return type in the docs

List.isList shows a return type of maybeList in the documentation, but the examples clearly show it returning a boolean.

This is actually a bug in the documentation generator, not a bug in the type definitions. This is a user defined type guard function:
https://www.typescriptlang.org/docs/handbook/advanced-types.html#user-defined-type-guards

I just opened an issue for this at #1068 but would still appreciate help in fixing the doc generator!


add fallback and hardfail logic

If there are no negatives and therefore no triplets, it's possible to get a somewhat confusing Colbert error like:
ckpt_path = manage_checkpoints(config, colbert, optimizer, batch_idx+1, savepath=None, consumed_all_triples=True)
UnboundLocalError: cannot access local variable 'batch_idx' where it is not associated with a value

I propose we forbid the trainer from proceeding when there are no triplets. Additionally, if the user specified mine_hard_negatives and this obtains no negatives, we should produce a warning and fall back to random negatives. This latter choice is more opinionated and it's equally sensible to simply hard fail in that case too.

I propose we forbid the trainer from proceeding when there are no triplets.

Agreed, this makes the most sense.

Additionally, if the user specified mine_hard_negatives and this obtains no negatives, we should produce a warning and fall back to random negatives. This latter choice is more opinionated and it's equally sensible to simply hard fail in that case too.

Yeah, as discusses, I think that's the current philosophy of RAGatouille -- let people know something went wrong but try and be as frictionless as possible for newcomers (i.e. it's a pretty negative experience for a new user to spend ages preparing data that they haven't saved to disk, only to crash because of this, when it could've ran in a suboptimal way), but I think this will have to be revisited when the library grows.
Thanks for the PR, LGTM!


New PR to test SignCLA at 2019-06-25 14:13:50.398185242 -0700 PDT m=+6.589254608

Body of PR

indiv-pass-fork-staging: test succeeded


Update content to reflect more generic usage

In particular, the "GitHub setup" and "Post your guide" pages will need some work.
"Advanced features" also needs some love.

Lots of progress on this in #9, but still have to update the images, maybe mention Bitbucket webhooks.


Using Meteor.call in step definitions and hooks

I've tried wrapping several parts such as
var callback = Meteor.bindEnvironment(next);

By the stack trace it appears to be that line causing the error, but also it is Meteor.call if that get's called first.
and have checked https://github.com/meteor-velocity/velocity-examples as well as https://github.com/xolvio/Letterpress.
The error it's giving me is
Error: Meteor code must always run within a Fiber. Try wrapping callbacks that you pass to non-Meteor libraries with Meteor.bindEnvironment.

Chasing my tail on this one, any help is appreciated.

Can you show me the code you're using?

If I add the following to the before hook
  var boundCallback = function () {
    world.browser.
      init().
      setViewportSize({
        width: 1280,
        height: 1024
      }).
      timeoutsImplicitWait(1000).
      call( function(){} );//Meteor.bindEnvironment(next) );
  };
  var connection = DDP.connect(helper.world.mirrorUrl);
  connection.call('clearState', boundCallback);

then I get the error, specifically the last art of the code referenced in the stack trace is the var connection = DDP.connect(helper.world.mirrorUrl); line.

    this.Before(function () {

      var world = helper.world;
      var next = arguments[arguments.length - 1];

      var boundCallback = function () {
        world.browser.
          init().
          setViewportSize({
            width: 1280,
            height: 1024
          }).
          timeoutsImplicitWait(1000).
          call(next);
      };

      var connection = DDP.connect(helper.world.mirrorUrl);
      connection.call('clearState', boundCallback);

    });

I just tested this code and it worked with the previous version of Meteor. Looks like the latest update to <IP_ADDRESS> has broken the bindings. I'll look at this and report back

I suggest downgrading temporarily to keep progressing

Ok, another workaround that will work in the latest Meteor is this:
    this.Before(Meteor.bindEnvironment(function () {

      var world = helper.world;
      var next = arguments[arguments.length - 1];

      var boundCallback = function () {
        world.browser.
          init().
          setViewportSize({
            width: 1280,
            height: 1024
          }).
          timeoutsImplicitWait(1000).
          call(next);
      };

      var connection = DDP.connect(helper.world.mirrorUrl);
      connection.call('clearState', boundCallback);

    }));

Notice the bindEnvironment at the before callback. This is something that xolvio:cucumber does automatically (here) but that seems to be broken. You may need to apply the same fix for other places you see this error (like step definitions), until I fix this issue.

Awesome, thanks for the great work.

I'm not sure if it's the meteor version.  If I clone Letterpress, then upgrade only cucumber to 0.3.8 and webdriver to 0.2.2 I get the same error.  The meteor version stays at<EMAIL_ADDRESS> That being said I also tried downgrading cucumber all the way to 0.3.0 which also didn't seem to have an effect.
Using bindEnvironment before and the other functions does seem to work though.

With the most recent version, I no longer get the last error mentioned.
Wrapping functions in bindEnvironment seems to work, thanks for everything.

Thanks for reporting back. I'm going to keep this open so I can fix the auto binds :)

You no longer need to this manually in 0.3.10

0.3.10 throws this exception:
Exception in callback of async function: TypeError: object is not a function
at /Users/sunil/meteor/meteor-boiler/tests/cucumber/features/support/hooks.js:45:7
at runWithEnvironment (/Users/sunil/meteor/meteor-boiler/.meteor/local/build/programs/server/packages/meteor.js:1052:24)
My before hook is fairly simple. This exception happens at callback().
My before hook:
this.Before("@beforeHookLogin", function(callback){
  console.log("start @beforeHookLogin");
  //always signout before sigingin in
  helper.world.browser.
    url(helper.world.cucumber.mirror.rootUrl).
    waitForExist('#at-nav-button').
    waitForVisible('#at-nav-button').
    click('#at-nav-button');

  // make sure the user is Authenticated
  helper.world.browser.
    url(helper.world.cucumber.mirror.rootUrl+"sign-in").
    waitForExist('.at-pwd-form').
    waitForVisible('.at-pwd-form').
    setValue('#at-field-email', 'sunil@y.com').
    setValue('#at-field-password', 'sunil123').
    click('#at-btn');

  console.log("End @beforeHookLogin");

  callback();
});


Add squircle

The now so fashionable shape between a square and a circle.
I made it 19px in size, this makes it .5px off grid, which might be a problem.
Use: Icon shape chooser.

Yeah, on a high DPI display it looks neat, but it's pretty damn blurry at 1x.

We could consider unifying the badge, circle and square, currently we have a bunch of different icons for each shape.

I'm ok with this shape icon. Looking at the 24px DPI preview it looks fine to me.

I change it so it is the same size as the square, before it was 0.5px bigger.

@jguddas Awesome!
@karsa-mistmere you also ok with this?


TESS cutouts with requests: download from only one sector

Small change: instead of downloading all available cutouts, just download from sector 1. This is so that we are downloading a smaller file (40 MB vs 216 MB).
Prompted by https://github.com/spacetelescope/notebooks/issues/122.

@mustaric Reviewed and OKed offline.


alt_bn128 use stack instead of heap

Problem
I'm currently trying to use alt_bn128 to verify Groth16 ZKP. I'm using this repository which in turns uses the  alt_bn128 module from the solana-program crate.
The problem I face when I run my program is:
Error: memory allocation failed, out of memory
Let me share some details about my circuit. It has 246 outputs i.e. public inputs. I've checked the code and I noticed the usage of the following functions:

https://github.com/solana-labs/solana/blob/973d05c098b24364ad29a5066e78884c5c3a7537/sdk/program/src/alt_bn128/mod.rs#L306
https://github.com/solana-labs/solana/blob/973d05c098b24364ad29a5066e78884c5c3a7537/sdk/program/src/alt_bn128/mod.rs#L326

These functions return a vector of data on the heap which means they allocate data on the heap not stack. Looking into the non-solana version of the functions I can see the following line
let mut input = input.to_vec();
input.resize(ALT_BN128_MULTIPLICATION_INPUT_LEN, 0);

//  pub const ALT_BN128_MULTIPLICATION_INPUT_LEN: usize = 128;

For circuits like mine which has 246 inputs this will result in allocating 246 times a vector of size 128 which would quickly hit the Solana heap size limits.
Proposed Solution
I wonder if could use the stack instead of creating vectors on the heap. The issue with the heap is that there is no way to free a previously allocated memory. However, with stack (correctly if I'm wrong) we still have a limit but the stack at least can grow and shrink, so as long as a function call stays within the stack limit we should be (in theory ok).
Most of the practical circuits will have public inputs of that size if not bigger. As it stands, it's hard to use the alt_bn128 for any practical circuit.

Hi @ppoliani, do you have an example program that you are running using the bn128 operations? and also where are you running the program (testnet, devnet, mb?).
It appears to me that the size of the return vector should be fixed and small enough to fit inside either the stack or the heap. My guess is that you are running out of memory because the operation is being invoked as bpf instructions rather than natively as syscalls.


Discoveryplus ERROR 404

Checklist

[X ] I'm reporting a broken site support
[X ] I've verified that I'm running youtube-dl version 2021.12.17
[X ] I've checked that all provided URLs are alive and playable in a browser
[X ] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X ] I've searched the bugtracker for similar issues including closed ones

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--username', 'PRIVATE', '--password', 'PRIVATE', '--cookies', 'discoveryplus.com_cookies.txt', '--list-formats', '--geo-bypass', '--verbose', 'https://www.discoveryplus.com/video/jackass-shark-week-20-us/jackass-shark-week-20']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 2022-07-21-git-f7d510b33f-full_build-www.gyan.dev, ffprobe 2022-07-21-git-f7d510b33f-full_build-www.gyan.dev
[debug] Proxy map: {}
[debug] Using fake IP <IP_ADDRESS> (US) as X-Forwarded-For.
[DiscoveryPlus] jackass-shark-week-20-us/jackass-shark-week-20: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\extractor\common.py", line 634, in _request_webpage
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpupik7c6w\build\youtube_dl\YoutubeDL.py", line 2288, in urlopen
  File "C:\Python\Python34\lib\urllib\request.py", line 470, in open
  File "C:\Python\Python34\lib\urllib\request.py", line 580, in http_response
  File "C:\Python\Python34\lib\urllib\request.py", line 508, in error
  File "C:\Python\Python34\lib\urllib\request.py", line 442, in _call_chain
  File "C:\Python\Python34\lib\urllib\request.py", line 588, in http_error_default

C:\plex files\Shark Weeek>youtube-dl --version
2021.12.17

Description

WRITE DESCRIPTION HERE
getting ERROR 404 from discoveryplus.com US website

do you have an account to share for testing?

Unfortunately it looks like this unsolved problem: https://github.com/yt-dlp/yt-dlp/issues/2361.

See https://github.com/yt-dlp/yt-dlp/issues/2138#issuecomment-1544407575.


orubase

orubase tool information added.

Please submit an image with this PR. Or, if I understand correctly, please close this PR since it looks like you've made another more recent one with updated changed.

Could please use this attached image.

Hi @dblotsky
We have not able to commit a image directly using browser so we have submitted image in the previous update. Could you let me know is this enough?


Need to support Kubernetes Secrets

The VPC API key should be in a Kubernetes Secret, not a ConfigMap. Likewise the SSH configuration for OnPrem should be in a Secret.

https://github.com/ibm-hyper-protect/k8s-operator-hpcr/pull/17

done


Language change

selectable language function can be added.
If you send me the language file I can help with the translation

https://www.christianengvall.se/electron-localization/

Thank you, Good idea!
Want to help and implement it?

I've just started learning Electron JS. When I saw your project, I gave up. I am a software developer and I have skills in html js php .net. I would like to help you learn Electron

Why you gave up? Also, I'm curious, how did you find this project?

You really designed it. it only gives a security warning when installing the software (Win10).
Design changes can help

it makes more sense to help and develop the car's engine rather than re-design it when someone has designed it

Yah, I'm not a designer :)
I'm appreciating any feedback you have and if you want to contribute to this project, I'll glad to help you with that.

Of course I would like to contribute. I want to learn both electron :)

Great! So you want to try to take and work on this issue?

yes but I have basic knowledge of electron js

No rush. You can give a shot. Review the code, if you have questions, let me know.

?

What are you trying to do?
To run it locally: npm start (or yarn start)
To build the app locally: npm run build (or yarn build)

thanks :) I am also experimenting with language file

Great! Let me know how it goes.

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli   'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli   'run', 1 verbose cli   'build' 1 verbose cli ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true 8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\electron\y2mp3\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Git\cmd;C:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs\;C:\Users\oguzs\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\JetBrains\PhpStorm 2019.1.1\bin;;C:\Users\oguzs\AppData\Roaming\Composer\vendor\bin;C:\Users\oguzs\AppData\Roaming\npm 9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\electron\y2mp3 10 silly lifecycle<EMAIL_ADDRESS>Args: [ 10 silly lifecycle   '/d /s /c', 10 silly lifecycle   'npm run generate-icons && tsc && webpack --config webpack.prod.js' 10 silly lifecycle ] 11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 2  signal: null 12 info lifecycle<EMAIL_ADDRESS>Failed to exec build script 13 verbose stack Error<EMAIL_ADDRESS>build: npm run generate-icons && tsc && webpack --config webpack.prod.js13 verbose stack Exit status 2 13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16) 13 verbose stack     at EventEmitter.emit (events.js:210:5) 13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack     at ChildProcess.emit (events.js:210:5) 13 verbose stack     at maybeClose (internal/child_process.js:1021:16) 13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) 14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\electron\y2mp3 16 verbose Windows_NT 10.0.18362 17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build" 18 verbose node v12.13.1 19 verbose npm  v6.12.1 20 error code ELIFECYCLE 21 error errno 2 22 error<EMAIL_ADDRESS>build:npm run generate-icons && tsc && webpack --config webpack.prod.js22 error Exit status 2 23 error Failed at the<EMAIL_ADDRESS>build script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 2, true ]

0 info it worked if it ends with ok 1 verbose cli [ 1 verbose cli   'C:\\Program Files\\nodejs\\node.exe', 1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js', 1 verbose cli   'run', 1 verbose cli   'build' 1 verbose cli ] 2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] 5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>7 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true 8 verbose lifecycle<EMAIL_ADDRESS>PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\electron\y2mp3\node_modules\.bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Git\cmd;C:\xampp\php;C:\ProgramData\ComposerSetup\bin;C:\Program Files\nodejs\;C:\Users\oguzs\AppData\Local\Microsoft\WindowsApps;;C:\Program Files\JetBrains\PhpStorm 2019.1.1\bin;;C:\Users\oguzs\AppData\Roaming\Composer\vendor\bin;C:\Users\oguzs\AppData\Roaming\npm 9 verbose lifecycle<EMAIL_ADDRESS>CWD: C:\electron\y2mp3 10 silly lifecycle<EMAIL_ADDRESS>Args: [ 10 silly lifecycle   '/d /s /c', 10 silly lifecycle   'npm run generate-icons && tsc && webpack --config webpack.prod.js' 10 silly lifecycle ] 11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 2  signal: null 12 info lifecycle<EMAIL_ADDRESS>Failed to exec build script 13 verbose stack Error<EMAIL_ADDRESS>build: npm run generate-icons && tsc && webpack --config webpack.prod.js13 verbose stack Exit status 2 13 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16) 13 verbose stack     at EventEmitter.emit (events.js:210:5) 13 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14) 13 verbose stack     at ChildProcess.emit (events.js:210:5) 13 verbose stack     at maybeClose (internal/child_process.js:1021:16) 13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5) 14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd C:\electron\y2mp3 16 verbose Windows_NT 10.0.18362 17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build" 18 verbose node v12.13.1 19 verbose npm  v6.12.1 20 error code ELIFECYCLE 21 error errno 2 22 error<EMAIL_ADDRESS>build:npm run generate-icons && tsc && webpack --config webpack.prod.js`
22 error Exit status 2
23 error Failed at the<EMAIL_ADDRESS>build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]

What is that?

npm run build


SKIP_AD functionality

Now that you can skip ads on the Chromecast Youtube app, Google thinks it's cool to sometimes send you a 5 minute ad.
No thank you.
There's probably a few nice to haves that I couldn't work out:

Rather than trying 30 times to skip an ad, make a query that returns an object containing "whenSkippable". For example: https://developers.google.com/cast/docs/reference/web_receiver/cast.framework.ui.PlayerData?hl=en
^ This would also be good to have another method of determining if an ad is playing rather than relying on some random hard coded number.
Update "title" to output "advertisement" while player_state_id == 1081

I think it must be a relatively recent addition. I'm keen to integrate it into https://github.com/erdnaxeli/castblock


Can client access support polaris registration center

Question
At present, I think Tencent's open-source Polaris registration center will become popular. Can Shenyu support client access to the Polaris registration center

pls see https://github.com/apache/shenyu/pull/4410 I think it will merge in future.

pls see #4410 I think it will merge in future.

OK，thank you very much