⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 51 ms

Resolved: ClamAV performance has improved in 0dfefb9.


PowerShell installation on OS X install /usr/local/bin/pwsh, /usr/local/bin/powershell

Steps to reproduce
Install PowerShell using instructions here or by downloading the latest version from GitHub
Expected behavior
Powershell can be started from Terminal
Actual behavior
The command that needs to be used is pwsh, which doesn't seem to be mentioned anywhere.
Environment data

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      6.0.1
PSEdition                      Core
GitCommitId                    v6.0.1
OS                             Darwin 17.4.0 Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

The first linked page says near the top:

Once the package is installed, run pwsh from a terminal.

Generally, such issues are better raised at the docs repo
Note that you now even get a direct Edit link on the published pages themselves, which allows you  to suggest edits (via pull request).

There was an issue with pulling some of the install docs over to the docs repo. Those are being addressed with https://github.com/PowerShell/PowerShell-Docs/issues/2166


(3.0.53) SUnit browser running test method in wrong class

RwProjectTonelReaderWriterTest>>testWriterReader_A is the selected test, however, the stack from the debugger indicates that the RwProjectfileTreeTonelReaderWriterTest class is being used to execute the test:

Note the method #_writerVisitorClass in debugger and contrast the #_writerVisitorClass method in RwProjectTonelReaderWriterTest class in project browser ...
It does happen that the test method is defined in RwProjectfileTreeTonelReaderWriterTest, but it is inherited ...

Same problem shows up when running test from Project Browser:


integration with laravel microscope

The works dine are great, but I wanted to ask if you can integrate it with laravel-microscope so that the user can scan his project code by clicking buttons on the UI and see the reports.
Currently, PHP artisan check:psr4 is ready to serve HTTP requests and is decoupled from the command line.

Tahnks for your suggestion. I will check it.


Add dropdown in primary actions

[Action Header] Add dropdown in primary actions

@JohnnP , the dropdown is just for the secondary action.

Because i want a second dropdown and i want to change the icon of the dropdown

@JohnnP
can you provide a screenshot of your need. Or a wireframe ? Please.

@JohnnP I think your request is interesting. Some others projects will have the same need.
But you don't agree with your proposition.
Instead that providing an array of actions, we prefer to open the possibility to provide a custom component.
Can you implement that ?


[dv] remove unfinished tests from nightly dashboard

Some ROM E2E tests that were not yet running in in DV were mistakenly added to the testplan "tests" reference field, which makes them show up incorrectly in the nightly dashboard.
Signed-off-by: Timothy Trippel<EMAIL_ADDRESS>

LGTM! Sorry for the confusion.

No worries!

Thanks @timothytrippel, sorry for the noise!


Bump eks go minor versions for 1.18, 1.19

Issue #, if available:
Description of changes:
In response to https://groups.google.com/g/golang-announce/c/L_3rmdT0BMU, we're bumping EKS Go tracking versions for 1.18 to 1.18.9 and for 1.19 to 1.19.4
This PR includes a bump to the git tag, an update of the spec file to track those versions, and a re-generation of the README. It also includes a small adjustment to the readme generator.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Github skill issue

Update fabric and some weird things that i dont have any idea, github 😡

Looks good for me 👍


Reader-friendly modifications - help needed ?

Thanks for your effort!
However it's not very reader-friendly - have you thought about using any docs system for your project ? (with reading mode, etc ?).
Would you like your repo to be converted into reader-friendly site? (I thought about mkdocs with material).
This would adding indexes to files & commiting some code from mkdocs. Here is example screenshot of what I tried locally.
Note the features:

index on the left (unordered due to alphabetical sorting)
chapters on the right
page changes on the bottom

Please let me know if I should start working on it.
Then you can publish it on github pages & everyone can look at it in more reader-friendly mode.

Implemented in #14 .
Please pin this issue in case someone would have other requests / issues with PDF or mkdocs site.

Also known issue is PDF links - i'm not sure what is the best way to fix cross-reference for now.
Maybe someone can update links, so all of them would have some kind of # prefix that is recognized in pdf ?

Dark theme is also a good thing to do
https://squidfunk.github.io/mkdocs-material/setup/changing-the-colors/

Implemented dark color theme. Thanks Tasmota!

Thank you @shafr . This is awesome. I was very slow at reacting to the change, but now I have time. Keeping this issue pinned as requested until we merge the PR.


BIGTOP-2923: Bump kafka to 1.0.0

closed https://github.com/apache/bigtop/pull/301 , because adding the issue number to name didn't seem to link to the the issue automatically, so recreated the PR with the right name.

Haven't test it.


Update how-to-schedule-pipelines.md

Addressing #52967

@sfilipi : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for the fix @sfilipi !


onBeforeUpload Not Treating True Correctly?

I have this in my onBeforeUpload function:
var planDisk = {value returned from function1};
var diskUsage = {value returned from function2};
var diskUsagePlusFile = diskUsage + file.size;
var enoughSpace = (planDisk >= diskUsagePlusFile);
if (enoughSpace) {
    return true;
} else {
    toastr.error(TAPi18n.__('outOfDiskSpace'));
    return false;
}

Even though it's returning "true", the upload is not sticking and it's like it returned false (but didn't).
If I put a "return true;" as the 1st statement, the uploads work.
Any ideas?

Hello @SeraVault ,
Sorry for the late reply. Have you solved it on your own?
If so, what was the issue?

Hi,
I wasn't able to solve the problem.  I implemented code outside of the
onBeforeUpdate event to handle the situation.
Thanks!
On Wed, Jul 11, 2018 at 1:02 AM, dr.dimitru<EMAIL_ADDRESS>wrote:

Hello @SeraVault https://github.com/SeraVault ,
Sorry for the late reply. Have you solved it on your own?
If so, what was the issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/VeliovGroup/Meteor-Files/issues/627#issuecomment-404054738,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhAsCxfjgCciXzDPHINZevxZO0f4TLDQks5uFZUAgaJpZM4VIoop
.

Do you wish to reopen this ticket and post full definition of your collection, so we can proceed further with fix?


[BUG] Deploy harvester error

# kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"clean", BuildDate:"2021-11-17T15:48:33Z", GoVersion:"go1.16.10", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.11+rke2r1", GitCommit:"38d3c1f3d5306401bcf39a71bad3b5a5106033d7", GitTreeState:"clean", BuildDate:"2022-03-16T22:50:09Z", GoVersion:"go1.16.15b7", Compiler:"gc", Platform:"linux/amd64"}

>>> get pod --all-namespaces
NAMESPACE          NAME                                                    READY   STATUS      RESTARTS   AGE
harvester-system   harvester-798866ff75-5r5gs                              1/1     Running     0          19m
harvester-system   harvester-load-balancer-59bf75f489-266hn                1/1     Running     0          19m
harvester-system   harvester-network-controller-manager-747bc5898-vzcf9    1/1     Running     0          19m
harvester-system   harvester-network-controller-wqd9n                      1/1     Running     0          19m
harvester-system   harvester-node-disk-manager-4hpnl                       1/1     Running     0          19m
harvester-system   harvester-webhook-78b5d4f4bd-zljrm                      1/1     Running     0          19m
harvester-system   kube-vip-b6kql                                          1/1     Running     0          19m
harvester-system   kube-vip-cloud-provider-0                               1/1     Running     0          19m
harvester-system   virt-api-79448ff685-7pg9s                               1/1     Running     0          17m
harvester-system   virt-api-79448ff685-92xqn                               1/1     Running     0          17m
harvester-system   virt-controller-6c7f5d4fbf-cwvw6                        1/1     Running     0          16m
harvester-system   virt-controller-6c7f5d4fbf-sd468                        1/1     Running     0          16m
harvester-system   virt-handler-hpnq4                                      1/1     Running     0          16m
harvester-system   virt-operator-78b84587c9-jx2xn                          1/1     Running     0          19m
kube-system        cloud-controller-manager-izj6c8c48epotfcjobyxcmz        1/1     Running     0          22m
kube-system        etcd-izj6c8c48epotfcjobyxcmz                            1/1     Running     0          22m
kube-system        helm-install-rke2-canal-hftrc                           0/1     Completed   0          23m
kube-system        helm-install-rke2-coredns-dzl4x                         0/1     Completed   0          23m
kube-system        helm-install-rke2-ingress-nginx-ps5g8                   0/1     Completed   0          23m
kube-system        helm-install-rke2-metrics-server-hpwqt                  0/1     Completed   0          23m
kube-system        kube-apiserver-izj6c8c48epotfcjobyxcmz                  1/1     Running     0          23m
kube-system        kube-controller-manager-izj6c8c48epotfcjobyxcmz         1/1     Running     0          22m
kube-system        kube-proxy-izj6c8c48epotfcjobyxcmz                      1/1     Running     0          23m
kube-system        kube-scheduler-izj6c8c48epotfcjobyxcmz                  1/1     Running     0          23m
kube-system        rke2-canal-fk2q5                                        2/2     Running     0          22m
kube-system        rke2-coredns-rke2-coredns-687554ff58-m87qc              1/1     Running     0          22m
kube-system        rke2-coredns-rke2-coredns-autoscaler-7566b44b85-m5wlk   1/1     Running     0          22m
kube-system        rke2-ingress-nginx-controller-bl7sz                     1/1     Running     0          21m
kube-system        rke2-metrics-server-8574659c85-xtmn9                    1/1     Running     0          22m
kube-system        snapshot-controller-9f68fdd9-j6qch                      1/1     Running     0          19m
kube-system        snapshot-controller-9f68fdd9-vfskw                      1/1     Running     0          19m
longhorn-system    csi-attacher-5f46994f7-lnsfz                            1/1     Running     0          18m
longhorn-system    csi-attacher-5f46994f7-tq27g                            1/1     Running     0          18m
longhorn-system    csi-attacher-5f46994f7-v6rq9                            1/1     Running     0          18m
longhorn-system    csi-provisioner-6ccbfbf86f-5zzs5                        1/1     Running     0          18m
longhorn-system    csi-provisioner-6ccbfbf86f-gh646                        1/1     Running     0          18m
longhorn-system    csi-provisioner-6ccbfbf86f-h75h9                        1/1     Running     0          18m
longhorn-system    csi-resizer-6dd8bd4c97-46ll5                            1/1     Running     0          18m
longhorn-system    csi-resizer-6dd8bd4c97-75w6j                            1/1     Running     0          18m
longhorn-system    csi-resizer-6dd8bd4c97-zznft                            1/1     Running     0          18m
longhorn-system    csi-snapshotter-86f65d8bc-2sm2f                         1/1     Running     0          18m
longhorn-system    csi-snapshotter-86f65d8bc-8j6kw                         1/1     Running     0          18m
longhorn-system    csi-snapshotter-86f65d8bc-ztvvs                         1/1     Running     0          18m
longhorn-system    engine-image-ei-4dbdb778-2fvlr                          1/1     Running     0          18m
longhorn-system    instance-manager-e-6e76829e                             1/1     Running     0          18m
longhorn-system    instance-manager-r-2734222b                             1/1     Running     0          18m
longhorn-system    longhorn-csi-plugin-jwk2p                               2/2     Running     0          18m
longhorn-system    longhorn-driver-deployer-cb9dcf594-p64ht                1/1     Running     0          19m
longhorn-system    longhorn-manager-rg4fr                                  1/1     Running     0          19m
longhorn-system    longhorn-ui-74d4bd689d-fgt57                            1/1     Running     0          19m
>>> logs -f -n harvester-system harvester-798866ff75-5r5gs
WARNING: proto: message VersionResponse is already registered
See https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

WARNING: proto: file "rpc.proto" is already registered
See https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

WARNING: proto: file "rpc.proto" has a name conflict over VersionResponse
See https://developers.google.com/protocol-buffers/docs/reference/go/faq#namespace-conflict

time="2022-04-17T14:12:50Z" level=info msg="Starting controller"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Setting"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD apiservices.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD KeyPair"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Upgrade"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Version"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD VirtualMachineImage"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD VirtualMachineTemplate"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD VirtualMachineTemplateVersion"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD VirtualMachineBackup"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD VirtualMachineRestore"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Preference"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD SupportBundle"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD BackingImage"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD BackingImageDataSource"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Backup"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Volume"
time="2022-04-17T14:12:50Z" level=info msg="Do not update the existing CRD Setting"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD clusters.provisioning.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD settings.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD users.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD groups.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Waiting for CRD clusters.provisioning.cattle.io to become available"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD groupmembers.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD tokens.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Applying CRD nodedrivers.management.cattle.io"
time="2022-04-17T14:12:50Z" level=info msg="Waiting for CRD nodedrivers.management.cattle.io to become available"
time="2022-04-17T14:12:51Z" level=info msg="Done waiting for CRD clusters.provisioning.cattle.io to become available"
time="2022-04-17T14:12:51Z" level=info msg="Done waiting for CRD nodedrivers.management.cattle.io to become available"
time="2022-04-17T14:12:53Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:12:58Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:03Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:08Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:13Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:18Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:23Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:28Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:33Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:38Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:43Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:48Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:53Z" level=info msg="Waiting for ValidatingWebhookConfiguration harvester-validator..."
time="2022-04-17T14:13:53Z" level=info msg="Waiting for MutatingWebhookConfiguration harvester-mutator..."
time="2022-04-17T14:13:53Z" level=info msg="Admission webhooks are ready"
I0417 14:13:53.489959       7 leaderelection.go:243] attempting to acquire leader lease kube-system/harvester-controllers...
I0417 14:13:53.808036       7 leaderelection.go:253] successfully acquired lease kube-system/harvester-controllers
E0417 14:13:53.828765       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:13:53.831418       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:13:54.652613       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:13:54.691730       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:13:56.615599       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:13:57.532307       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:14:02.004167       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:14:03.655057       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:14:08.453672       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:14:15.636336       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:14:30.507153       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:14:31.662492       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:15:06.007496       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:15:17.357015       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:15:44.678521       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:16:15.832659       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:16:42.318059       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:17:12.864495       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:17:22.526829       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:17:54.512867       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:18:16.844475       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:18:36.679093       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:19:09.237165       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:19:13.007790       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:19:46.434720       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:19:57.564809       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:20:36.637489       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:20:44.046322       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:21:26.059088       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:21:28.635636       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:22:02.854257       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:22:19.075805       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:22:55.615784       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:23:12.180666       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:23:44.919485       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:23:47.988464       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:24:30.310182       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:24:43.649060       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:25:01.163568       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:25:23.495606       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:25:44.326295       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:26:07.766980       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:26:19.062496       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:26:38.809300       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:26:56.901680       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:27:12.669602       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:27:30.583700       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:28:07.619009       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:28:10.652499       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:28:52.863652       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:29:00.007152       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:29:23.622114       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:29:41.402507       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:30:12.909534       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:30:40.981513       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:30:51.079163       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)
E0417 14:31:34.367199       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v1.App: failed to list *v1.App: the server could not find the requested resource (get apps.meta.k8s.io)
E0417 14:31:34.912570       7 reflector.go:138] github.com/rancher/lasso/pkg/cache/cache.go:124: Failed to watch *v3.ManagedChart: failed to list *v3.ManagedChart: the server could not find the requested resource (get managedcharts.meta.k8s.io)

@xiaofan-linux:
Could you please add those information:

Hardware/VM resources to deploy Harvester, CPU, memory, storage;  single-node or multi-nodes;  when CPU/MEMORY are not meeting minimum requirements, the deploy will fail, things like OOM will hapen
How Harvester is installed, from Harvester ISO or other ways? the Harvester version.
From the POD list, it looks the "rancher-*" related POD are not there, PODs under "cattle-monitoring-system" are also missing.
...

normally there are more PODs like:
NAMESPACE                   NAME                                                     READY   STATUS      RESTARTS   AGE
cattle-fleet-local-system   fleet-agent-57497ff7dc-8npt6                             0/1     Unknown     5          2d19h
cattle-fleet-system         fleet-controller-5746685958-4m9zc                        0/1     Unknown     6          2d19h
cattle-fleet-system         gitjob-cc9948fd7-pjmcj                                   0/1     Unknown     5          2d19h

cattle-monitoring-system    prometheus-rancher-monitoring-prometheus-0               3/3     Running     0          19h
cattle-monitoring-system    rancher-monitoring-grafana-d9c56d79b-8btbx               0/3     Unknown     0          19h
cattle-monitoring-system    rancher-monitoring-kube-state-metrics-5bc8bb48bd-szftx   0/1     Unknown     5          2d19h
cattle-monitoring-system    rancher-monitoring-operator-559767d69b-jg4s8             0/1     Unknown     6          2d19h
cattle-monitoring-system    rancher-monitoring-prometheus-adapter-8846d4757-l54bl    0/1     Unknown     5          2d19h
cattle-monitoring-system    rancher-monitoring-prometheus-node-exporter-ldvf9        0/1     Unknown     5          2d19h

cattle-system               harvester-cluster-repo-56b5f7b585-xdlm8                  0/1     Unknown     5          2d19h
cattle-system               rancher-8bc9f456d-gqgcm                                  0/1     Unknown     5          2d19h
cattle-system               rancher-webhook-54c75c9d4-mb4w8                          0/1     Unknown     5          2d19h
cattle-system               system-upgrade-controller-5b6457d644-x42w4               0/1     Unknown     6          2d19h

When Harvester is installed in developer mode, please check if it follows the steps listed in https://docs.harvesterhci.io/v1.0/dev/dev-mode/ , thanks.

cattle-monitoring

Is harvester strongly dependent on pod's such as cat fleet and cat monitoring?

@xiaofan-linux: Could you please add those information:

Hardware/VM resources to deploy Harvester, CPU, memory, storage;  single-node or multi-nodes;  when CPU/MEMORY are not meeting minimum requirements, the deploy will fail, things like OOM will hapen
How Harvester is installed, from Harvester ISO or other ways? the Harvester version.
From the POD list, it looks the "rancher-*" related POD are not there, PODs under "cattle-monitoring-system" are also missing.
...

normally there are more PODs like:
NAMESPACE                   NAME                                                     READY   STATUS      RESTARTS   AGE
cattle-fleet-local-system   fleet-agent-57497ff7dc-8npt6                             0/1     Unknown     5          2d19h
cattle-fleet-system         fleet-controller-5746685958-4m9zc                        0/1     Unknown     6          2d19h
cattle-fleet-system         gitjob-cc9948fd7-pjmcj                                   0/1     Unknown     5          2d19h

cattle-monitoring-system    prometheus-rancher-monitoring-prometheus-0               3/3     Running     0          19h
cattle-monitoring-system    rancher-monitoring-grafana-d9c56d79b-8btbx               0/3     Unknown     0          19h
cattle-monitoring-system    rancher-monitoring-kube-state-metrics-5bc8bb48bd-szftx   0/1     Unknown     5          2d19h
cattle-monitoring-system    rancher-monitoring-operator-559767d69b-jg4s8             0/1     Unknown     6          2d19h
cattle-monitoring-system    rancher-monitoring-prometheus-adapter-8846d4757-l54bl    0/1     Unknown     5          2d19h
cattle-monitoring-system    rancher-monitoring-prometheus-node-exporter-ldvf9        0/1     Unknown     5          2d19h

cattle-system               harvester-cluster-repo-56b5f7b585-xdlm8                  0/1     Unknown     5          2d19h
cattle-system               rancher-8bc9f456d-gqgcm                                  0/1     Unknown     5          2d19h
cattle-system               rancher-webhook-54c75c9d4-mb4w8                          0/1     Unknown     5          2d19h
cattle-system               system-upgrade-controller-5b6457d644-x42w4               0/1     Unknown     6          2d19h

Is harvester strongly dependent on pod's such as cat fleet and cat monitoring?

@xiaofan-linux Honestly, it is not easy to explain a complex system in short words.  https://docs.harvesterhci.io/v1.0/ may give you a brief idea of this sytem.
To get a Harvester cluster, please follow the official guide in https://docs.harvesterhci.io/v1.0/install/iso-install/  or
https://docs.harvesterhci.io/v1.0/dev/dev-mode/ .
With un-offical methods, they are not even well designed/developed/tested/documented, many issues may occur. In case you have interest and time, you may dive into :)


Getting Started with Development Guide

This looks like a really interesting project, but when I cloned it, it wasn’t really clear what I needed to do to build and deploy it so that I could try to add a new target.
It would be really handy to have a “Getting Started” guide for developers that describes the tools needed and the steps to build and deploy.
Thanks!

Haven't looked at this in a while, but took a look today.
So far, it looks like tools needed are: npm, nodejs, zip, docker
I haven't tried deploying yet, but that's probably going to need aws-sam-cli and python.
To build the runtimes, I had to comment out the upload code from s3-uploader/app.js, then run it with these commands in the s3-uploader directory:
$ npm install
$ node app.js

Most of the runtimes build inside a freshly created docker instance with the build tools installed via the Dockerfiles for those. The exception is the nodejs runtimes, which just use the zip command to zip up the source folder.
I suspect that my next step is to modify s3-uploader/app.js to upload to my own S3 bucket, and build the rest of the pieces. It seems like each one has to be build separately.

My goal is to be able to contribute more runtimes, but there's just a lot of discovery to do in order to do that.


Fix 1843 1844

title: Pull Request
description: Template to use in your Pull Requests.
Hey :wave:,
Thank you for submitting the PR. I am so excited to see what you've build. To shorten the merge time as much as possible, I recommend you check all the items on the list below before submitting it.

PS.: No worries if some of them are missing, I will try to look at it ASAP :slightly_smiling_face:

Things to look after:

[x] Make sure all of the significant new logic is covered by tests
[x] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass

Description of changes:

Looks good, but there is a merge conflict to fix.
Also it's containing changes from the other PR, which makes it more difficult to review (and merge in isolation).

@znarf I'll wait for the first PR to get merged and fix the changes in this one afterwards


Disappearing picrutes

After loading all pictures on some screen dimention last pictures aren't show. For example when i got automaticly created 3 rows from 15 pic where row has 4 pic so there is missing 3 pic (script set this last 3 pic on display none). Is this some of bug or what? How can i fix this?

Hi @okosurona, seems like the normal behavior for some of the maxRowHeightPolicy settings, have you checked this part of the documentation? Cheers!

Since I'm not getting any answer and it's been a long time, I'm closing this issue.


[DRTV] "Historien om Danmark" actually downloads sign language version

Please follow the guide below

You will be asked some questions and requested to provide some information, please read them carefully and answer honestly
Put an x into all the boxes [ ] relevant to your issue (like that [x])
Use Preview tab to see how your issue will actually look like

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2017.05.07. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2017.05.07

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your issue

If the purpose of this issue is a bug report, site support request or you are not completely sure provide the full verbose output as follows:
Add -v flag to your command line you run youtube-dl with, copy the whole output and insert it here. It should look similar to one below (replace it with your log inserted between triple ```):
$ youtube-dl -v https://www.dr.dk/tv/se/historien-om-danmark/-/historien-om-danmark
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.dr.dk/tv/se/historien-om-danmark/-/historien-om-danmark']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.05.07
[debug] Python version 3.6.0 - Linux-4.10.1-1-ARCH-x86_64-with-arch
[debug] exe versions: ffmpeg 3.2.4, ffprobe 3.2.4, rtmpdump 2.4
[debug] Proxy map: {}
[drtv] historien-om-danmark: Downloading webpage
[drtv] historien-om-danmark: Downloading video JSON
[drtv] historien-om-danmark: Downloading f4m manifest
[drtv] historien-om-danmark: Downloading m3u8 information
[drtv] historien-om-danmark: Downloading f4m manifest
[drtv] historien-om-danmark: Downloading m3u8 information
[debug] Invoking downloader on 'http://drod01e-vh.akamaihd.net/i/all/clear/streaming/53/590762baa11f9f0ce0604053/HISTORIEN-OM-DK-5-10-010517-TO_fae3a3dbba11441497dbef1ba974556b_,328,531,1019,2205,3192,.mp4.csmil/index_4_av.m3u8?null=0'
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 359
[download] Destination: Historien om Danmark - Sen middelalder (5)-historien-om-danmark.mp4
[download] 100% of 1.34GiB in 06:32
[debug] ffmpeg command line: ffprobe -show_streams 'file:Historien om Danmark - Sen middelalder (5)-historien-om-danmark.mp4'
[ffmpeg] Fixing malformated aac bitstream in "Historien om Danmark - Sen middelalder (5)-historien-om-danmark.mp4"
[debug] ffmpeg command line: ffmpeg -y -i 'file:Historien om Danmark - Sen middelalder (5)-historien-om-danmark.mp4' -c copy -f mp4 -bsf:a aac_adtstoasc 'file:Historien om Danmark - Sen middelalder (5)-historien-om-danmark.temp.mp4'

<end of log>

Description of your issue, suggested solution and other information
When I try to download this show, for some reason, I get the sign language version. The link I used, if opened in the browser, shows the regular version, and not the sign language one.

Alright, working on it myself, figured out the code and all.


Long Time running(over 2 days) will cause tokio panic

I've been setup the latest version behind cdn and wrap wireguard's data flow,things runs great.
how ever each 2days or more the server will panic and exit by itself.
I tried rerun it with rusttrace=1 to capture logs like below:
2023-11-18T04:26:27.399641Z ERROR tunnel{peer="<IP_ADDRESS>:37174" forwarded_for="<IP_ADDRESS>" id="018be0a8-f0d9-7ec1-8399-14dfe175433b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: error while reading from websocket rx Unexpected EOF
2023-11-18T04:26:27.400209Z INFO tunnel{peer="<IP_ADDRESS>:37174" forwarded_for="<IP_ADDRESS>" id="018be0a8-f0d9-7ec1-8399-14dfe175433b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: Closing local rx <== websocket rx tunnel
2023-11-18T04:26:27.400500Z INFO tunnel{peer="<IP_ADDRESS>:37174" forwarded_for="<IP_ADDRESS>" id="018be0a8-f0d9-7ec1-8399-14dfe175433b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: Closing local tx ==> websocket tx tunnel

... (additional logs)

2023-11-19T22:07:27.735475Z ERROR tunnel{peer="<IP_ADDRESS>:52784" forwarded_for="<IP_ADDRESS>" id="018be6be-bcfd-7d11-acfb-2951cff24f2b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: error while reading from websocket rx Unexpected EOF
2023-11-19T22:07:27.736010Z INFO tunnel{peer="<IP_ADDRESS>:52784" forwarded_for="<IP_ADDRESS>" id="018be6be-bcfd-7d11-acfb-2951cff24f2b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: Closing local rx <== websocket rx tunnel
2023-11-19T22:07:27.736275Z INFO tunnel{peer="<IP_ADDRESS>:52784" forwarded_for="<IP_ADDRESS>" id="018be6be-bcfd-7d11-acfb-2951cff24f2b" remote="<IP_ADDRESS>:55111"}: wstunnel::tunnel::io: Closing local tx ==> websocket tx tunnel

... (additional logs)

thread 'tokio-runtime-worker' panicked at library/std/src/time.rs:408:33: overflow when adding duration to instant
./ss.sh: line 2: 65592 Aborted                 ./wstunnel server --restrict-http-upgrade-path-prefix 123456ABCDEFG ws://<IP_ADDRESS>:5566 --restrict-to <IP_ADDRESS>:55111

... (additional logs)

RUST_BACKTRACE=1 ./ss.sh

... (additional logs)

full log gonna paste in below

setup was like
wstunnel client->CDN->nginx->wstunnel server

command was like:
-> client
./wstunnel client -L udp://<IP_ADDRESS>:55111:<IP_ADDRESS>:55111?timeout_sec=0 --http-upgrade-path-prefix 123456ABCDEFG wss://www.google.com

->server
./wstunnel server --restrict-http-upgrade-path-prefix 123456ABCDEFG ws://<IP_ADDRESS>:5566 --restrict-to <IP_ADDRESS>:55111

Hello,
Thank you for reporting the issue.
I don't have a computer at hand at the moment, and will likely be able to take a look at ot sunday.
In the meantime, would you mind starting the server with RUST_BACKTRACE=full and RUST_LOG=DEBUG env variables set, and post the result. of the crash.
Thanks in advance

Would you mind trying this pre-release and letting me know if you still encounter the issue ?
https://github.com/erebe/wstunnel/releases/tag/v7.9.4

Would you mind trying this pre-release and letting me know if you still encounter the issue ? https://github.com/erebe/wstunnel/releases/tag/v7.9.4

Thank you so much,gonna try this version with RUST_BACKTRACE=full and RUST_LOG=DEBUG to see if it crashes again:)

Would you mind trying this pre-release and letting me know if you still encounter the issue ? https://github.com/erebe/wstunnel/releases/tag/v7.9.4

Hi it's been over 3 days and no new error log showed,I think it might be fixed


Segmentation fault in tensorflow::FileSystemRegistryImpl::Register

Syntaxnet package was built, tf package ver 1.01 was installed from repo by pip as dependency. Fortunately tf installed following these instructions https://www.tensorflow.org/versions/r0.10/get_started/os_setup#create_the_pip_package_and_install works fine.
[New LWP 31764]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `python2 -c from syntaxnet import load_parser_ops'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f3303cf0d47 in std::_Hash_bytes(void const*, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(gdb) bt
#0  0x00007f3303cf0d47 in std::_Hash_bytes(void const*, unsigned long, unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#1  0x00007f33065f509c in tensorflow::FileSystemRegistryImpl::Register(std::string const&, std::function<tensorflow::FileSystem* ()>) ()
   from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#2  0x00007f33065f26b3 in tensorflow::Env::RegisterFileSystem(std::string const&, std::function<tensorflow::FileSystem* ()>) ()
   from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#3  0x00007f3328d327b5 in _GLOBAL__sub_I_env.cc () from /usr/local/lib/python2.7/dist-packages/syntaxnet/parser_ops.so
#4  0x00007f3332df04ea in call_init (l=<optimized out>, argc=argc@entry=3, argv=argv@entry=0x7ffe61a27428, env=env@entry=0x265a8b0) at dl-init.c:72
#5  0x00007f3332df05fb in call_init (env=0x265a8b0, argv=0x7ffe61a27428, argc=3, l=<optimized out>) at dl-init.c:30
#6  _dl_init (main_map=main_map@entry=0x2a41360, argc=3, argv=0x7ffe61a27428, env=0x265a8b0) at dl-init.c:120
#7  0x00007f3332df5712 in dl_open_worker (a=a@entry=0x7ffe61a263e0) at dl-open.c:575
#8  0x00007f3332df0394 in _dl_catch_error (objname=objname@entry=0x7ffe61a263d0, errstring=errstring@entry=0x7ffe61a263d8, mallocedp=mallocedp@entry=0x7ffe61a263cf,
    operate=operate@entry=0x7f3332df5300 <dl_open_worker>, args=args@entry=0x7ffe61a263e0) at dl-error.c:187
#9  0x00007f3332df4bd9 in _dl_open (file=0x7f332e1634cc "/usr/local/lib/python2.7/dist-packages/syntaxnet/parser_ops.so", mode=-2147483646,
    caller_dlopen=0x7f33065fa9ea <tensorflow::internal::LoadLibrary(char const*, void**)+26>, nsid=-2, argc=<optimized out>, argv=<optimized out>, env=0x265a8b0)
    at dl-open.c:660
#10 0x00007f33325f6f09 in dlopen_doit (a=a@entry=0x7ffe61a26610) at dlopen.c:66
#11 0x00007f3332df0394 in _dl_catch_error (objname=0x252e0d0, errstring=0x252e0d8, mallocedp=0x252e0c8, operate=0x7f33325f6eb0 <dlopen_doit>, args=0x7ffe61a26610)
    at dl-error.c:187
#12 0x00007f33325f7571 in _dlerror_run (operate=operate@entry=0x7f33325f6eb0 <dlopen_doit>, args=args@entry=0x7ffe61a26610) at dlerror.c:163
#13 0x00007f33325f6fa1 in __dlopen (file=<optimized out>, mode=<optimized out>) at dlopen.c:87
#14 0x00007f33065fa9ea in tensorflow::internal::LoadLibrary(char const*, void**) ()
   from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#15 0x00007f33065f9b97 in tensorflow::(anonymous namespace)::PosixEnv::LoadLibrary(char const*, void**) ()
   from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#16 0x00007f33064f6f93 in tensorflow::LoadLibrary(char const*, void**, void const**, unsigned long*) ()
   from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#17 0x00007f3304e11e67 in TF_LoadLibrary () from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#18 0x00007f3304d1206a in _wrap_TF_LoadLibrary () from /usr/local/lib/python2.7/dist-packages/tensorflow/python/_pywrap_tensorflow.so
#19 0x00000000004c468a in PyEval_EvalFrameEx ()
#20 0x00000000004c2765 in PyEval_EvalCodeEx ()
#21 0x00000000004ca8d1 in PyEval_EvalFrameEx ()
#22 0x00000000004c2765 in PyEval_EvalCodeEx ()
#23 0x00000000004c2509 in PyEval_EvalCode ()
#24 0x00000000004c061b in PyImport_ExecCodeModuleEx ()
#25 0x00000000004bd6ee in ?? ()
#26 0x00000000004afbad in ?? ()
#27 0x00000000004af7e9 in PyImport_ImportModuleLevel ()
#28 0x00000000004b0f78 in ?? ()
#29 0x00000000004b0cb3 in PyObject_Call ()
#30 0x00000000004ce5d0 in PyEval_CallObjectWithKeywords ()
#31 0x00000000004c6ed6 in PyEval_EvalFrameEx ()
#32 0x00000000004c2765 in PyEval_EvalCodeEx ()
#33 0x00000000004c2509 in PyEval_EvalCode ()
#34 0x0000000000521186 in PyRun_StringFlags ()
#35 0x0000000000521dfc in PyRun_SimpleStringFlags ()
#36 0x000000000049de94 in Py_Main ()
#37 0x00007f333281a830 in __libc_start_main (main=0x49dab0 <main>, argc=3, argv=0x7ffe61a27428, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7ffe61a27418) at ../csu/libc-start.c:291
#38 0x000000000049d9d9 in _start ()

@keveman I think it's yet another case of overriding symbols with different underlying static variables.
@inferrna I think it's a known bug with tensorflow that wherein external ops outside of the main tensorflow code are unstable. Try linking against _pywrap_tensorflow instead.
/CC: @nealwu

/CC: @skye

friendly ping: is this still an issue?

Yes, I believe this is a case of #9525

It has been 14 days with no activity and this issue has an assignee.Please update the label and/or status accordingly.


Add option to use annotations

Thanks you for the tools.
Great job !!
Could we improve it by adding annotation handler ?
In fact Sealed Secret encrypt data but also annotations. So adding annotation on SealedSecret object will not add it when unseal it.
We have to  add first annotation on the Secret ressource and only then we can seal it in order to take annotation in count.
Can we improve the GUI for letting us add some annotations like :
sealedsecrets.bitnami.com/managed
sealedsecrets.bitnami.com/namespace-wide
sealedsecrets.bitnami.com/cluster-wide

We`ll have a look on that.

closed with #153


Add BlockApi trait.

Solves #634 by moving the Block's API into a separate trait.
The same principle can probably be applied also to RegionRef and OperationRef.

Looks good to me, it duplicates a bit of code but I don't know another way that isn't a big rewrite, what do you think @raviqqe ?

The alternative would be to duplicate the methods manually, but doing it this way allows us to have functions that accept both Block and BlockRefs by declaring the argument as block: impl BlockApi.

Thank you for the changes! I'm gonna take a look soon.

@edg-l @azteca1998 It doesn't have to be addressed here. But FYI, we should technically have BlockRefMut in the future although we use BlockRef for both immutable and mutable references now. 😅

Ah, sorry I somehow force pushed to your branch!

@azteca1998 @edg-l Can you take a look at this? https://github.com/azteca1998/melior/pull/1

Ah, sorry I somehow force pushed to your branch!

No problem.

Can you take a look at this? https://github.com/azteca1998/melior/pull/1

Merged.


Scheduling AutomateTasks via the console

Purpose or Intent

This PR allows scheduling of an AutomationTask through the rails console using a correctly formed new MiqSchedule object. Once the new scheduled task is added it will run on a schedule as expected - though being an automation task it will follow the below rules.

An AutomationRequest will be created when the schedule runs

This iteration will allow for auto approval of all Scheduled Automate Tasks
Automate runs the task via the existing mechanism

Note: The Automation Request will be built on schedule, but the task itself will run within the timeframe allowed within the other Queued jobs.

Links

https://www.pivotaltracker.com/story/show/126161699

Steps for Testing/QA

Create an instance of your task in /System/Process

Open the appliance rails console rails console
Paste the included hash (details obviously have to match your instance) into your console to build the MiqSchedule for your AutomationTask.

auto_schedule = {:name=>"ShowStuff", :description=>"ShowStuff", :towhat=>"AutomationRequest", :userid=>1, :enabled=>true, :run_at=>{:tz=>"UTC", :start_time=>4.minutes.from_now.utc, :interval=>{:unit=>"daily", :value=>"1"}}, :sched_action=>{:method=>"automation_request"}, :filter=>{:uri_parts=>{ :instance=>"ShowStuff", :message=>"create"}, :parameters=>{}}}
MiqSchedule.create(auto_schedule)

@gmcculloug - Please review
cc @jrafanie, @bdunne

@miq-bot add_label enhancement

@miq-bot add_label automate

:+1: LGTM

Close/open to for sporadic "TestClass superclass mismatch failure" fixed by #10491

@gmcculloug - I rebased master into this - hence the new notifications

Euwe Backport details:
$ git log -1
commit f68dd3073c5f8cd1103cabe53f84b75e04dc4cc5
Author: Greg McCullough<EMAIL_ADDRESS>Date:   Thu Oct 20 13:05:55 2016 -0400

    Merge pull request #9987 from syncrou/add_automation_to_schedule

    Scheduling AutomateTasks via the console
    (cherry picked from commit 6c9d5ee1233d7733a823fb871988de40d8f39dfd)


Unsupported modules detected

In android studio I'm getting
Compilation is not supported for following modules: react-native-device-info. Unfortunately you can't have non-Gradle Java modules and Android-Gradle modules in one project.

react-native info
System:
    OS: macOS 10.15.3
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 33.04 GB / 64.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 10.17.0 - /usr/local/opt/node@10/bin/node
    Yarn: Not Found
    npm: 6.11.3 - /usr/local/opt/node@10/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.0. - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>92135
    Xcode: 11.4.1/11E503a - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_241 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

version ^5.5.6

Fixed this in Android studio with File -> Invalidate caches and restart.

Spoke too soon, this did not help

This worked.
https://stackoverflow.com/a/49397748/5187459

This happens to me sometimes as well - it's very frustrating. The stack overflow link you posted is the thing I use too


[Coil][Glide] Deprecate the libraries

Following on from the release of coil-compose in Coil 1.3.0, this PR deprecates Accompanist Coil.
This left Accompanist Glide is a weird situation, where most of imageloading-core was there to only support Glide. Since Coil is better suited for use in Compose I've decided to deprecate everything: accompanist-coil, accompanist-glide and accompanist-imageloading-core. All of the libraries will be removed soon (likely v0.16.0)
I need to migrate DrawablePainter over to a new library, but that can wait for now (tracked in #540).

Check this. https://github.com/bumptech/glide/issues/4459
Glide doesn't support compose. Also, the major contributor of Glide said he is not familiar with Compose or Kotlin.
Someone else need to add compose support for Glide.
Instead of deprecating it, can you make this as a recommended way until someone adds support in Glide out of the box

No, we won't be un-deprecating the Glide library. I heavily recommend moving to Coil.

If someone is looking for compose support for Glide, try this one
https://github.com/sanjeevirajm/GlideCompose/


Add My New Year Countdown Timer Project

Issue Type: Hey admin! I want to add my New Year Countdown Timer Project to your site , I am contributor at GSSoC'22. Please assign this issue to me.

[ ] Bug Report
[x] Feature Request
[ ] Documentaion

Describe the bug

A clear and concise description of what the bug is.

Possible solution
I want to add this here.
It's animated and responsive too.

Repository Link:- https://github.com/Susmita-Dey/Happy-New-Year-CountDown-Timer-Project
Live demo:- https://susmita-dey.github.io/Happy-New-Year-CountDown-Timer-Project/

Screenshots

If applicable, add screenshots to help explain your problem.

https://github.com/arpit456jain/Amazing-Js-Projects

Ok, I'm creating an issue there.


[Tests] Add unittests for Jobs in Project

Let's add unittests for Jobs in Project.
ONE-vscode-DCO-1.0-Signed-off-by: Yongseop Kim<EMAIL_ADDRESS>

PTAL @Samsung/one-vscode


Combine blocks when possible.

This change is

crates/cairo-lang-lowering/src/optimizations/match_optimizer_test.rs line 48 at r1 (raw file):

    let mut after = before.clone();
    optimize_matches(&mut after);
    topological_sort(&mut after);

This is currently broken as the output of optimize_matches is not SSA, so I can’t remove unnecessary remapping between blocks and merge them.
Code quote:
  topological_sort(&mut after);

crates/cairo-lang-lowering/src/topological_sort.rs line 27 at r1 (raw file):
Previously, spapinistarkware (Shahar Papini) wrote…
This logic has some issues I think regarding removing unreachable blocks. For example, if we have a chain of blocks that with the first having 0 incoming gotos?

not sure what the issue is.

crates/cairo-lang-lowering/src/topological_sort.rs line 27 at r1 (raw file):
Previously, ilyalesokhin-starkware wrote…
not sure what the issue is.

None of thes blocks are reachable in this case, so all of them are going to be removed before the filter operation bellow.

crates/cairo-lang-lowering/src/topological_sort.rs line 12 at r1 (raw file):
Previously, orizi wrote…
but the result is actually different blocks - this is no longer a sort.


Example of search docker compose doesnt work

'using docker compose for https://github.com/dbpedia/dbpedia-lookup/tree/master/examples/dbpedia-lookup-search
Overall started without errors, however once accessing http://localhost:{mapped port from docker}
and getting localhost didn’t send any data.

I managed to build up the container by placing a  homepages_en.ttl file into the data folder before running docker-compose up.
However, running http://localhost:9273/lookup-application/api/search?query=<ENTER_QUERY_HERE> still did not send any data. Is there any solution to this?

Hi, could you give the new main branch a go? I updated the documentation and also added a section about building the docker image at the bottom of the readme.
There is an example documented and some additional example indexing requests in the examples folder. The examples cover

indexing from file
indexing from SPARQL endpoint
indexing from Databus collection URI


DOCTYPE is not self-closing

We found out in our team that DOCTYPE is not self-closing when we tried to use a HTML => PDF converter that choked on the self-closing DOCTYPE that HEML generates.
https://stackoverflow.com/questions/19199106/why-isnt-doctype-self-closing

We are encountering the same issue, we are running the output through a DOM/HTML parser, which doesn't work because of the self-closing tag in the DOCTYPE.


A question about shape/appearance codes

When I tried to analyze how the Shape/APPEARANCE CODES was generated, I found that there was no obvious part in the code. In the Forward code of NERF, there seemed to be no APPEARANCE CODE, and the shape code was the input coordinate?This is strange. What should be like?

They all exist in z,separated during training


Fix #4

Includes test with better mwe

Codecov Report

Merging #5 (8f0eee1) into main (c0771e4) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main       #5   +/-   ##
=======================================
  Coverage   80.00%   80.00%
=======================================
  Files           1        1
  Lines         295      295
=======================================
  Hits          236      236
  Misses         59       59

Impacted Files
Coverage Δ

src/KLU.jl
80.00% <100.00%> (ø)

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 c0771e4...8f0eee1. Read the comment docs.


Seperate the single Autoplay option for Videos AND GIFs into two

Looking at this post, having the option to disable autoplay for videos OR gifs instead of both could be a good idea
There are times a user may not want to have videos Autoplay, which they can disable in settings but this causes GIFs to stop autoplaying as well, which seems fairly inconvenient to hit play on every gif just because you don't want videos to autoplay
It's not bad to give the option to users who want it, essepcially with certain types of video content that the user may not want to view which doesn't necessarily extend to gifs 🩵🩷🩵🩷
(If it's not too much to ask???)

I agree - videos also consume way more bandwidth than GIFs. I don't mind downloading some gifs but streaming every video passing by the timeline, especially in mobile networks, can be too much

I would like this since it seems like auto playing videos seems to trip up last.fm when scrolling through the timeline (at least on the Android version.)


Figure out correct way to export components in ES6 modules for Babel to work with ES5 code

When babel was upgraded from v5 to v6, they changed the transpiling result of the export default function.  You used to be able to do this:
// a.js
exports default 'some code';

// b.js
var someCode = require(`./a`);

And everything was fine.  But (from what I understand) people were using the import statements incorrectly, and the transpiling behavior was allowing code to work that was actually in conflict with the ES6 spec. So in v6, the code above no longer works, and now you have to add .defaults to the require statement like this:
// a.js
exports default 'some code';

// b.js
var someCode = require(`./a`).defaults;

Somehow/somewhere there's a proper way to export and import in babel v6 that conforms to ES6 but also works with require statements and ES5 code, so you can mix and match ES5 and ES6 (or transpiled and not transpiled) code as you need to.
Need to figure that out and update the framework's ES6 code appropriate, and change any ES5 code that has incompatible behaviors.  Adding .defaults to require statements is not an acceptable solution.
While there is this a babel-plugin-add-module-exports plugin for babel that would remove the issue in v6, I believe it's intended to supply the old behavior only as a interim solution to buy more time (seeing as the behavior is not in spec in the first place).

#107 makes it possible to create an ES6 project using lore new app-name --es6 and sets a flag in the .lorerc file of the project that notifies all generators to create an ES6 version of whatever they produce as well.
The pattern it uses to do that will also easily support creating an ES.Next experience once I confirm the lore.connect decorator works using the @lore.connect syntax, and then we can have the generators use static types and decorators and whatever other else is useful but still in a draft stage.
As for the original subject of this issue, I was able to solve most of the issues by ES5/ES6 interoperability issues by using the babel-plugin-add-module-exports, but not all of them. There was one place in lore I needed to add a line to detect and use .default if it existed.
I had to do the same in webpack-requiredir to get the config to load correctly. I don't understand why, but I gave up trying to figure it out after a while. I'll remove the hack in the future when it's no longer needed.
Also, while Node v6.2 has 96% compatibility with ES6, it looks like we're still waiting for v8 to support import/export syntax, which is waiting on the module loader. No ETA that I can find, it's just "in progress".
Once v8 (and Node) support the import/export for module loading, I'll be open to switching the default to ES6. As it is right now, using ES6 modules breaks CLI tools like gulp that use vanilla node, and webpack only works if you kick it off with babel-node, which appears to have a negative impact on the development experience (loading times) and prevents setting breakpoints during testing (at least in IDEs, not sure about elsewhere).

So given the changes above, I think the last thing that remains before I can close out this issue is upgrading React-Router to v2 and adding support for it in the ES6 generator templates for components.

Closing this as #109 updates react-router to v2 and integrates routing into the ES6 templates.


Property: "keyVaultSecretId" must use one of the following expressions for an resourceId property

In app gateway keyVaultSecretId takes the following format:
"sslCertificates": [
                    {
                        "name": "mycert",
                        "properties": {
                            "keyVaultSecretId": "[concat(reference(resourceid('Microsoft.KeyVault/vaults',parameters('keyVaultName')),'2019-09-01').vaultUri,'secrets/mycert')]"
                        }
                    }
                ],

Not sure I can do this with one of the resource ID functions?
Thanks.

hold one... wrong test

ok fixed in #68


Implement mapPartitions(..) operation

At the moment I don't believe there is a need to expose the actual mapPartitions(..) method as it is more of a non-functional concern and rarely comes up. Having said that support was enabled in a very unobtrusive way (via thread local). At any point if time if user wants to know which partition a particular value belongs to, all it needs to do is call PartitionIdHelper.getPartitionId().


ACM-10812: Fix status report

We are still having issues with status reporting. In the latest instance, the endpoint-operator fails to update the metrics-collector deployment because of a conflict, then sets the status to degraded. And it remains in that state while the metrics are forwarded.
This PR:

Adds retry on conflict error to the metrics-collector related updates.
Changes the comparison between the found resources version and the desired ones to use DeepDerivative. This will reduce the number of unnecessary updates.
Adds retry on conflict for status updates made by the metrics-collector.
Sort conditions before updating the status in the metrics-collector to ensure it handles the most recent one.

I tried to change as few things as possible.

/retest

/cherrypick release-2.10

/cherrypick release-2.10


Handle autoscale in the initializer worker

This change causes autoscale events to be handled in the initializer worker. All autoscale events are serialized through this worker, which prevents multiple autoscale events from being triggered at the same time by contacting different workers.
If an autoscale event is signaled at a non-initializer worker the message is proxied through to the initializer. The initializer coordinates the work, or signals to the client requesting the autoscale event that it cannot carry out the autoscale action at this time.

@aturley Changes look good


Dependabot ran out of disk space during its update

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
npm
Package manager version
lts
Language version
lts
Manifest location and content before the Dependabot update
No response
dependabot.yml content
https://github.com/Th3S4mur41/mh-photography.com/blob/main/.github/dependabot.yml
Updated dependency
No response
What you expected to see, versus what you actually saw
Dependabot has no issues updating actions but fails when updating npm dependencies with the following error:
proxy | 2023/10/20 09:55:19 proxy starting, commit: 177b79b3279d896f40d0106a42f112a74926e34e
  proxy | 2023/10/20 09:55:19 Listening (:1080)
updater | 2023-10-20T09:55:20.317465694 [738542567:main:WARN:src/devices/src/legacy/serial.rs:222] Detached the serial input due to peer close/error.
updater | time="2023-10-20T09:55:22Z" level=info msg="guest starting" commit=e75527fd04f889bbb6beb6fe359fa9ae5657ef2e
updater | time="2023-10-20T09:55:22Z" level=info msg="starting job..." fetcher_timeout=10m0s job_id=738542567 updater_timeout=45m0s updater_version=1d5b6488ed9dd0227d254f64d9bfe4748993af18-npm
updater | 2023/10/20 09:55:24 INFO Raven 3.1.2 ready to catch errors
updater | 2023/10/20 09:55:26 INFO <job_738542567> Starting job processing
  proxy | 2023/10/20 09:55:26 [002] GET https://github.com:443/Th3S4mur41/mh-photography.com/info/refs?service=git-upload-pack
  proxy | 2023/10/20 09:55:26 [002] * authenticating git server request (host: github.com)
  proxy | 2023/10/20 09:55:26 [002] 200 https://github.com:443/Th3S4mur41/mh-photography.com/info/refs?service=git-upload-pack
  proxy | 2023/10/20 09:55:26 [004] POST https://github.com:443/Th3S4mur41/mh-photography.com/git-upload-pack
  proxy | 2023/10/20 09:55:26 [004] * authenticating git server request (host: github.com)
  proxy | 2023/10/20 09:55:26 [004] 200 https://github.com:443/Th3S4mur41/mh-photography.com/git-upload-pack
  proxy | 2023/10/20 09:55:26 [006] POST https://github.com:443/Th3S4mur41/mh-photography.com/git-upload-pack
  proxy | 2023/10/20 09:55:26 [006] * authenticating git server request (host: github.com)
  proxy | 2023/10/20 09:55:27 [006] 200 https://github.com:443/Th3S4mur41/mh-photography.com/git-upload-pack
updater | 2023/10/20 09:59:34 ERROR <job_738542567> Error during file fetching; aborting
updater | 2023/10/20 09:59:34 INFO <job_738542567> Finished job processing
updater | 2023/10/20 09:59:34 INFO Results:
updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | +-------------+
updater | |   Errors    |
updater | +-------------+
updater | | out_of_disk |
updater | +-------------+
updater | time="2023-10-20T09:59:34Z" level=info msg="task complete" container_id=job-738542567-file-fetcher exit_code=0 job_id=738542567 step=fetcher
updater | time="2023-10-20T09:59:35Z" level=warning msg="failed during fetch, skipping updater" job_id=738542567

Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

It would seem more discussion is happening in #8613, perhaps these two tickets should be merged (or this one marked a dupe).

#8613 has been marked as closed, but the solution appears to be tied to the "Dependabot on Action (private beta)". It looks like "anyone can join" the private beta. The information requested for enrollment is:

Repository names
Will onboarding be on Github hosted runner or self-hosted runner?

Note: Make sure, that the GitHub actions is enabled on the repo before we do the onboarding.

The folks doing the enrollment appear to be:

@honeyankit
@jakecoffman

The last response from them in that thread was on Jan 16th 2024

Sounds indeed like the same issue...
@honeyankit  @jakecoffman would you be so nice to enable the beta where Dependabot jobs run on Actions for the following repository?
https://github.com:443/Th3S4mur41/mh-photography.com

@Th3S4mur41 : I will enable the repo Th3S4mur41/mh-photography.com the on Dependabot on actions (private beat) for GitHub hosted runners.

Repo Th3S4mur41/mh-photography.com is onboarded to Depebdabot on actions (private beta)

Thanks @honeyankit I'm no longer getting the issue 👍

@honeyankit and @jakecoffman could I trouble you to do the same for the following repositories?

teamupstart/typescript-platform
teamupstart/upstart-web-frontend


fix(TFD-999): Use CSV as the default Kafka format.

What is the current behavior? (You can also link to an open issue here)
The default Kafka format is Avro.
What is the new behavior?
The default Kafka format is CSV.
Please check if the PR fulfills these requirements

[X] The commit message follows Talend standard
[X] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[X] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[X] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


Sentry portico

Add ability to report errors on logged-out pages to frontend Sentry.

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

Looks reasonable, merged, thanks @alexmv! As noted above, I think it's possible (but am unsure) that it could make sense to move a bit more of the logic into what the server provides for realm_sentry_key, but that can be fixed forward if desired.


Merge PR to target branch before building

This PR adds a new piece of ocurrent incantations to merge PR to their target branch before testing.
A new Merge_commit module is added to take care of that logic. A Merge_commit.t can be transformed into a child build (Obuilder_spec.t)  that exports the merged repository state in a /merged folder. It can then be copied into the main build.

more than 1.5 years later, and me not understanding much of this code, I wonder what the status of this PR is? from the title it sounds like that's the right way to go forward :)


Security Fix for Cross site scripting - huntr.dev

@arjunshibu (https://huntr.dev/users/arjunshibu) has fixed a potential Cross site scripting vulnerability in your repository 🔨. For more information, visit our website (https://huntr.dev/) or click the bounty URL below...
Q | A
Version Affected | *
Bug Fix | YES
Original Pull Request | https://github.com/418sec/boxbilling/pull/2
If you are happy with this disclosure, we would love to get a CVE assigned to the vulnerability. Feel free to credit @arjunshibu, the discloser found in the bounty URL (below) and @huntr-helper.
User Comments:
📊 Metadata *
Bounty URL: https://huntr.dev/bounties/3-other-boxbilling/
⚙ Description *
The Create new redirect functionality is accepting user input without sanitizing which leads to Cross-Site Scripting (XSS). This fix sanitizes those user inputs before storing in the database.
💻 Technical Description *
Used the htmlspecialchars() function and the ENT_QUOTE attribute in order to avoid reflection of inputs inside the HTML resulting in the page.
🐛 Proof of Concept (PoC) *
Video: https://drive.google.com/file/d/1bkFc1xaJo7h2sR6A9znLQbzSnMai6lCj/view?usp=sharing
🔥 Proof of Fix (PoF) *
Before fix:

After fix:

👍 User Acceptance Testing (UAT)
I've executed unit tests and nothing breaks after the fix as there is only minor changes.

@fordnox can you merge this? travis doesn't respond for some reason.


KeyboardAwareScrollView scrolls to top when keyboard dissapears

Even with enableResetScrollToCoords={false} KeyboardAwareScrollView scrolls to top when keyboard dissapears
www_screencapture_com_2022-9-30_11_22.webm

@bekatd did you find out why it does that ??


[Bugfix] Dbt docs operator should not look for graph.gpickle file when --no-write-json is passed.

Fixes #882

@tatiana

I removed graph.gpickle entirely, and opened #894 to discuss more generally how artifact uploads should be handled.
I noticed in the tests that test_operator_execute_deps_parameters does not assert one of its conditions. However when I add the assert, it fails 🤔 This is a separate issue entirely from what I'm trying to do, but I found it curious and felt like I should note it.


Remove duplicated java option concats in common.sh

What is this PR for?
There are some java option concats in common.sh, which are executed twice when start an interpreter. This makes some of the options invalid, such as remote debugging options
What type of PR is it?
Bug Fix
Todos
Is there a relevant Jira issue?
ZEPPELIN-686
How should this be tested?
Set remote debug options:
export ZEPPELIN_INTP_JAVA_OPTS=-agentlib:jdwp=transport=dt_socket,server=y,address=8000,suspend=n

Start the Zeppelin daemon, then create & run a job to trigger starting an interpreter. The job should fail without the fix.
Screenshots (if appropriate)
Questions:

Does the licenses files need update?
NO

Is there breaking changes for older versions?
NO

Does this needs documentation?
NO

Thanks @zhongneu for the patch.
Looks good to me.

Merge if there're no more discsussions

what if someone has set JAVA_OPTS in the env? shouldn't we be additive?

@felixcheung I am not sure about this, but I would like to make it additive if we have such case.

I think @felixcheung got valid point. It's incompatible change to people who has JAVA_OPTS.
One alternative is document changes in
https://github.com/apache/incubator-zeppelin/blob/master/docs/install/upgrade.md

That sounds like a reasonable approach, we could say something like
"if you are setting JAVA_OPT, set ZEPPELIN_JAVA_OPTS instead for Zeppelin, set ZEPPELIN_INTP_JAVA_OPTS instead for interpreter process" in more words ;)

I've reverted the change for JAVA_OPTS, which is fine, because it is not used by bin/interpreter.sh

LGTM

looks good. I think we might want to deprecate JAVA_INTP_OPTS and replace with something more Zeppelin specific for clarify, and allow for admin to override it.
merging if no more comment.


Add Mint example

Description
Reopen #378 .
Tried with Mint 0.17.5 .
ref: https://github.com/yonaskolb/Mint#advanced
Motivation and Context
Help all users of Mint.
How Has This Been Tested?
I tried it on my app.

https://github.com/uhooi/UhooiPicBook/blob/a6fb0e062b79bc87bee26f7d50c68a935c23c5b2/.github/workflows/main.yml#L26-L27
https://github.com/uhooi/UhooiPicBook/blob/a6fb0e062b79bc87bee26f7d50c68a935c23c5b2/.github/workflows/templates/setup-ios/action.yml#L24-L30

Screenshots (if appropriate):
None.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation (add or update README or docs)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

Thanks @uhooi for raising the PR.


Tracking PR lifecycle in GitHub Project

[Transferred from legacy agenda on behalf of @stephenpdeos]
Problem: PR review assignment is not well reflected within project and standups

Are PR assignments explicit on the PRs some or all of the time in the current system?
Rather than duplicate the assignment in a ticket, maybe we should make efforts to ensure the assignments are explicit and build a quick dashboard for visibility? That could be helpful to the RFP and Grant processes as well.
If we are looking to track time or the lifecycle of the PR (as we would any task) then making them into issues does make more sense.  I wonder in that case if we can automate the PR's data so we don't have dueling sources of truth.


Feature Request: Custom Listings Messages for specific item(s)

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

Describe the feature you'd like

From: StarLord
Custom listings messages for specific items.
Describe alternatives you've considered

Additional context

@Nicklason @Zeckatz


mbed test linker fails when using --build option due to duplicate main.cpp

Description

mbed-os 5.9.2
custom board based upon STM32 F429ZI
mbed test
gcc_arm 7.2.1

On Windows we're stuck to the maximum command length of 32k.
To bypass the mbed test compile errors we use the --build option.
Unfortunately the linker has some problems with duplicate main.cpp found.
For example when we try to execute the sd-driver tests we use following command:
C:\work-mbed\myproject>mbed test -m MY_DEVICE -t GCC_ARM -n sd-driver-tests-block_device-basic --profile=profiles/release11.json --compile --build "C:/BUILD"

Here is the output:
[mbed] Working path "C:\work-mbed\myproject" (program)
Scan: .
Scan: FEATURE_LWIP
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Scan: TESTS
Building library mbed-build (MY_DEVICE , GCC_ARM)
Scan: .
Scan: FEATURE_LWIP
Compile [100.0%]: main.cpp
Scan: BUILD
Scan: FEATURE_LWIP
[Error] @,: Compiler version mismatch: Have 7.2.1; expected version >= 6.0.0 and < 7.0.0
Building project basic (MY_DEVICE , GCC_ARM)
Scan: BUILD
Scan: basic
Scan: FEATURE_LWIP
Link: basic
../../BUILD/sd-driver/TESTS/block_device/basic/basic.o: In function `main':
C:\work-mbed\myproject/.\sd-driver\TESTS\block_device\basic/basic.cpp:177: multiple definition of `main'
../../BUILD/main.o:C:\work-mbed\myproject/.\main.cpp:16: first defined here
collect2.exe: error: ld returned 1 exit status
Memory map breakdown for built projects (values in Bytes):
+------+--------+-----------+------------+-------------+
| name | target | toolchain | static_ram | total_flash |
+------+--------+-----------+------------+-------------+
+------+--------+-----------+------------+-------------+

Build successes:
  * MY_DEVICE ::GCC_ARM::MBED-BUILD

Build failures:
  * MY_DEVICE ::GCC_ARM::SD-DRIVER-TESTS-BLOCK_DEVICE-BASIC
        [Error] @,: Compiler version mismatch: Have 7.2.1; expected version >= 6.0.0 and < 7.0.0
        Building project basic (MY_DEVICE , GCC_ARM)
        Scan: BUILD
        Scan: basic
        Scan: FEATURE_LWIP
        Link: basic
        ../../BUILD/sd-driver/TESTS/block_device/basic/basic.o: In function `main':
        C:\work-mbed\myproject/.\sd-driver\TESTS\block_device\basic/basic.cpp:177: multiple definition of `main'
        ../../BUILD/main.o:C:\work-mbed\myproject/.\main.cpp:16: first defined here
        collect2.exe: error: ld returned 1 exit status

[mbed] ERROR: "c:\python27\python.exe" returned error.
       Code: 1
       Path: "C:\work-mbed\myproject"
       Command: "c:\python27\python.exe -u C:\work-mbed\myproject\mbed-os\tools\test.py -D MBED_TEST_MODE --profile profiles/release11.json -t GCC_ARM -m MY_DEVICE --source . --build C:/BUILD --test-spec C:/BUILD\test_spec.json -n sd-driver-tests-block_device-basic"
       Tip: You could retry the last command with "-v" flag for verbose output
---

Issue request type
[ ] Question
[ ] Enhancement
[x] Bug

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1200

You'll need to remove main.cpp in the root directory.
See Note on this page https://os.mbed.com/docs/mbed-os/v5.12/tools/test-and-debug.html
Note: mbed test does not work in applications that contain a main function that is outside of a TESTS directory.

Okay, but is also states # Optional main.cpp with main() if it is an application module.
Could you elaborate a bit more? Because it is a bit weird for me to have my testing farm pull my application repository and next run a script that delete files in that repo.

That segment shows typical code directory structure. For example, when you import a program such as blinky, you'll find a main.cpp in the root directory. You also get TESTS as well but "mbed compile" knows the code under TESTS needs to be excluded.
Now if you want to run "mbed test", it picks up the main.cpp in the TESTS directory, as well as "main.cpp" under the root directory. You just can't have two main.cpp files. Therefore the main.cpp at the root directory has to be removed/renamed.
One possible enhancement might be, ignore main.cpp at the root directory when "mbed test" is invoked. I would have to check with our tools team to see how much effort it requires. In the mean time, I think you'll have to run a script to rename that main.cpp to say main.txt during test.

I can confirm that simply removing the application's main.cpp is indeed working.
I've also tried adding a .mbed file with content ROOT=. within the to be tested library, but mbed test failed in finding its tools.
One other way I can think of solving this issue is to create an empty application that contains all of the libraries that we want to test, but that would require extra maintenance and we wouldn't be able to test our application code.
As a result, mbed test can't be used "out of the box" for testing application code and non mbed-os libraries (for example sd-driver from within an application). I'd be interested in an enhancement, I think it would also improve the user experience in general. Your solution could work for us. One other possible solution would be of we could have something like .mbedignore work specifically for testing, i.e. something like .mbedtestignore. That would add flexibility for developers to choose their preferred directory structure. What do you think?

@linlingao
I've just noticed in the latest mbed-os documentation that a special compile guard was added specifically for mbed test :
#if !MBED_TEST_MODE
int main() {
    // Application code
}
#endif

After upgrading our toolchain and adding that compile guard to our application I was able to perform the greentea tests without any linking errors occurring. So I think we have a solution there, I'm closing this one, feel free to reopen if you'd like anything to be added.


musl fixes

Motivation for this change
With these changes I can build not-os with musl.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

build on e06355f (#115841):
builder for '/nix/store/6m1bcxxzrx7xxhigazvn33bxyj09jakd-systemtap-4.1.drv' failed with exit code 1; last 25 log lines:                                                         checking to see if sdt probes should be the default... yes                                                                                checking whether g++ supports C++11 features by default... yes                                                                                configure: Compiling with gcc -fstack-protector-all et al.                                                                                checking pkg-config is at least version 0.9.0... yes                                                                                checking for sqlite3... no                                                                                checking for latex... no                                                                                checking for dvips... no                                                                                checking for ps2pdf... no                                                                                configure: will only install prebuilt documentation                                                                                checking for xmlto... no                                                                                checking for fop... no                                                                                checking for nss... no                                                                                checking for openssl... no                                                                                configure: using dracut module directory /usr/lib/dracut/modules.d/99stap                                                                                configure: using dracut binary /sbin                                                                                configure: WARNING: will not build systemtap compile server, cannot find nss headers                                                                                configure: WARNING: compile-server client functionality will be disabled, cannot find nss development files                                                                   checking for avahi... no                                                                                configure: WARNING: some compile-server functionality will be restricted, cannot find avahi development files                                                                 checking for rpmtsInitIterator in -lrpm... no
  checking for rpmdbNextIterator in -lrpmdb... no
  checking for rpmFreeCrypto in -lrpmio... no
  checking how to link readline libs... none
  configure: error: python version 2 is required

I removed the systemtap change again.

Not really sure what is happening here:
error: --- ParseError ---------------------------------------------------------------------------------------------------------------------------------------------------- nixat: (23:5) in file: /home/hotpi/.cache/nixpkgs-review/pr-115841-4/nixpkgs/pkgs/os-specific/windows/mcfgthreads/default.nix

    22|     substituteInPlace Makefile.am --replace '-Werror' ''
    23|   '';
      |     ^
    24|

syntax error, unexpected end of file, expecting IND_STR or DOLLAR_CURLY or IND_STRING_CLOSE
(use '--show-trace' to show detailed location information)
nix --experimental-features nix-command eval --json --impure --expr (import /nix/store/v9bjqm0wzg71cq0cgcwsc5s4fj5mb5j4-nixpkgs-review-2.5.0/lib/python3.8/site-packages/nixpkgs_review/nix/evalAttrs.nix /run/user/1000/tmpnmnks6ui) failed to run, /run/user/1000/tmpnmnks6ui was stored inspection
https://github.com/NixOS/nixpkgs/pull/115841 failed to build

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 115841 run on x86_64-linux 1

4 packages failed to build and are new build failures:

lvm2: log was empty
pcsclite: log was empty
procps-ng: log was empty
util-linux: log was empty

4 packages built:

argp-standalone
aws-sdk-cpp
libsmbios
nix

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:

argp-standalone:

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/development/libraries/argp-standalone/default.nix:32:5:
   |
32 |     license = licenses.gpl2;
   |     ^

See: https://github.com/jtojnar/nixpkgs-hammering/blob/master/explanations/unclear-gpl.md

@Mic92 please resolve the merge conflict and target staging

done.

@Mic92 ofborg still fails but I am not sure why:
install flags: SHELL=/nix/store/wq541npf2ni6gcwdwpjm8m01kdvycfkg-bash-4.4-p23/bin/bash install
  /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl//bin/ash -> busybox
  /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl//bin/sh -> busybox
patching script interpreter paths in /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl/default.script
/nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl/default.script: interpreter directive changed from "#!/bin/sh" to "/nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl/bin/sh"
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl
shrinking /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl/bin/busybox
patchelf: cannot find section '.dynamic'. The input file is most likely statically linked
aarch64-unknown-linux-musl-strip is /nix/store/ygzwsvvxv336im1mi019ikp6si8j6ijc-aarch64-unknown-linux-musl-binutils-2.35.1/bin/aarch64-unknown-linux-musl-strip
stripping (with command aarch64-unknown-linux-musl-strip and flags -S) in /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl/bin
patching script interpreter paths in /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl
checking for references to /build/ in /nix/store/73ml7a20janvsmnmg0xyvvj0vgwpaz6r-busybox-1.32.1-aarch64-unknown-linux-musl...
patchelf: cannot find section '.dynamic'. The input file is most likely statically linked
error: 5 dependencies of derivation '/nix/store/j5f8y0mq9vlvf0qjq1iwjwwv2rkr7dga-nix-2.3.10.drv' failed to build
error: 3 dependencies of derivation '/nix/store/9lw3b09j20g9b39mnlp31b04qrncdi0m-pcsclite-1.9.1.drv' failed to build
error: 1 dependencies of derivation '/nix/store/ijq7f1z6sfi76mwqr2zhmh8j6qv6ql46-util-linux-2.36.1.drv' failed to build
error: 8 dependencies of derivation '/nix/store/7q77c2az5mqfbbkjgmid64i15qlgmfky-aws-sdk-cpp-1.8.121.drv' failed to build
error: build of '/nix/store/7q77c2az5mqfbbkjgmid64i15qlgmfky-aws-sdk-cpp-1.8.121.drv', '/nix/store/9lw3b09j20g9b39mnlp31b04qrncdi0m-pcsclite-1.9.1.drv', '/nix/store/ijq7f1z6sfi76mwqr2zhmh8j6qv6ql46-util-linux-2.36.1.drv', '/nix/store/j5f8y0mq9vlvf0qjq1iwjwwv2rkr7dga-nix-2.3.10.drv', '/nix/store/z564jpg8khis8i21gh0bnmpsgc6gfp42-lvm2-2.03.11.drv' failed

I actually only tested x86 musl. I have not tested aarch64.


Add Timer.recordNanoseconds Generic Overload (#28)

Motivation:
As discussed in Issue #28, there are a few preferred lightweight APIs for getting timestamps such as DispatchTime but those APIs return UInt64 types, which need to be handled for overflow.
Modifications:
Added a generic BinaryInteger overload method for recordNanoseconds that guards against accidental overflows from UInt64 to Int64
Result:
Users now have access to a new method to record nanosecond measurements with Timer that guards against overflows.

This PR includes a commit that is open for review in a separate PR (#29)

@swift-server-bot test this please

thank you @Mordil can you please rebase and i will mege

@Mordil i think we can also change the call at https://github.com/apple/swift-metrics/blob/master/Sources/Metrics/Metrics.swift#L55 to now

@tomerd Done!

@Mordil see comment re  https://github.com/apple/swift-metrics/blob/master/Sources/Metrics/Metrics.swift#L55

Whoops! Didn't see that comment in emails or when I was reviewing the PR.

@swift-server-bot test this please

thanks @Mordil tagged as 1.1.0