Rename to library to jasny/phpdoc-parser

Annotations have a very specific meaning coming from Java. The Doctrine annotations are similar to those in Java.
In this library we parse phpDocumentor like tags. We should call these annotations.

@minstel Can you pick this up?


[Widget] Auto start doesn't work when menu is cached

Describe the bug
When I enable the automatic start after launching (no waiting for tap), it doesn't work when the menu is cached (enabled caching of menu in settings).
IMPORTANT!
I have:

[x] Used HTTPS to access HomeAssistant (with a public certificate)
[x] Checked that my JSON Syntax is correct (options 2, 3, or 4 or otherwise)
[x] Checked that my JSON follows the schema (options 2, 3, or 4)
[x] Used the online editor to check my JSON against HomeAssistant (option 1)
[x] Checked the Docs
[x] Checked the Troubleshooting Guide

To Reproduce
Steps to reproduce the behavior:

Go to Connect IQ widget settings
Enable caching of menu and automatic start without waiting for tap
On the watch, if not cached:

open the widget
let the app load entities/items
close the widget, exit it completely

Open the widget
See the widget showing "API" and "Menu" (cached)
See error (not proceeding to menu)

Expected behavior
Starting the widget with enabled "automatically start without waiting for tap", it should proceed to menu, instead of waiting for tap.
Screenshots
If applicable, add screenshots to help explain your problem.
Garmin Device (please complete the following information):

Model: Fenix 6X Sapphire

Smartphone (please complete the following information):

Device: Samsung S23
OS: Android 14

Additional context
Add any other context about the problem here.

I'll mark this as a bug when I have decided it is so!
In the mean time, as we know that auto start does work on other devices, I need to check that you have installed the correct application as there are two. The application at https://github.com/house-of-abbey/GarminHomeAssistant does not support Widgets or autostart, the Widget at https://github.com/house-of-abbey/GarminHomeAssistantWidget does. I need to be sure you have installed the latter before this is a bug.
Thank you for reporting this, I will try and find some time later in the week to follow your instructions to reproduce using the simulator. Presently I am between desktop PCs and without the means to run up the code.

There is definitely a bug here.

In the app or in the widget version? @philipabbey

In the app or in the widget version?

Only the widget version as the app does not have a root view.

In the app or in the widget version?

Only the widget version as the app does not have a root view. Shouldn't be too hard to fix.

True. Will have a look on this. Also creating an issue for the widget repo.

This issue has been transferred to the correct repo and is now fixed.


Added chart releaser for helm

Chart releaser for helm so that we get new versions available. Also the gh-pages branch needs to be cleaned up, because it will create the index.yaml in the root dir.

@terinjokes

Doing a bit differently in #102 102


Update README.md

I just ported opencc to Android platform, and would like to introduce this library to the developers.

Thanks


Why Browser library still requires to install NodeJS

Just my concern, but I saw that playwright native python support is available, why Browser library still requires to install NodeJS to run?
Thank you for your answer!

Browser library was build before native Python support was available for Playwright. We have discussed this internally few times and the conclusion is the following.

It is lot of work
Moving to Python only land would be lot of work. There is lot of code in the node side, which would need to rewritten in Python. Also it is not only about library code, we could need be rewriting installation, providing migration, do support and many more activities. The cost of the moving to Python only land, even it is tempting and would bring benefits, is currently too high. All that time would be taken away from the library development/features and so one. Also like many other open source projects, most of the work is not funded by a company/foundation. Some people may be able to contribute hour or two in company time, but this work would require few people in few months in full time.

Losing features
Also the change would be backwards incompatible, we would loose our NodeJS library API, which we think will ease the usage in the front end development. Also we might loose something else which  I am not able remember right now.

Loosing the fun of development
At least for me this project has provided me learning platform and reason to learn NodeJS world. If we would move to Python only land, at least I would loose some part of my motivation to develop the library.

We understand that living in both Python and NodeJS worlds is not always seamless from the users point of view (also same feeling is sometimes seen in dev side), but currently we do not have any plans to move in Python only land.

Closing issue because question is from my point of view answered. If you have more questions, please don't hesitate to ask.


Add .hpp extension to migrate_includes.py

Using migrate_include.py on modules which uses the c++ header extension .hpp is currently not a supported suffix.
Added hpp as an extension to allow for c++ header files to be recognised by migrate_include.py
Looking at https://github.com/zephyrproject-rtos/zephyr/issues/44196 it seems that the extension convention hpp is being accepted.

thanks, but please make sure to check the commit guidelines. https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines

Thanks for pointing me to the commit guidelines, I believe it should be fixed now


Fix bug of multi winners on dutch phase

Coverage decreased (-0.2%) to 85.759% when pulling 522f3328f28e4fc723983bbe8de2325f3f34d853 on VDigitall:sandbox into 482d9b6e2b2fa9e16d2f3cd11e9d9b0d54036c14 on openprocurement:sandbox.


Use Gitter?

Should we add a semi-realtime medium? I know that begriffs/postgrest uses Gitter. (https://gitter.im)

Good idea, I'll give it a try once I have some non-interrupted coding time.

I just gave this a try, it generated #41

What's the advantage over IRC? That's where everyone I know is, it's non-centralized and non-owned by someone. UI isn't as fancy, but other than that?

@quchen not much. It does give trivial history though, and some github activity on the side. You brought up IRC in #1 already; which didn't gain any traction. As begriffs/postgrest used gitter, I just wanted to leave this here. It's up of course up for debate.

For what it's worth I am generally always on IRC but try to avoid Gitter. The latter's notification mechanism leaves much to be desired.

I'm fine with either. @snowleopard can we get you onto irc as well?

Alright. We are on irc. irc://chat.freenode.net/shaking-up-ghc :100:


[backport] Update ChainerX contribution guide

Backport of #6951

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 9fb5b5f4838ca08534d03814bebaa24db45d2766, target branch v6) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 9fb5b5f4838ca08534d03814bebaa24db45d2766, target branch v6) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 9fb5b5f4838ca08534d03814bebaa24db45d2766, target branch v6) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 9fb5b5f4838ca08534d03814bebaa24db45d2766, target branch v6) failed with status FAILURE.

Jenkins, test this please

Jenkins CI test (for commit 9fb5b5f4838ca08534d03814bebaa24db45d2766, target branch v6) succeeded!

LGTM


Use the standard add_common_default_values for configuration/provisioning inventory collections

The configuration and provisioning managers' inventory collections have their own logic for setting default values for the owning manager.
Update to use the standardized add_common_default_values which unifies how to find the parent manager id when refreshing multiple managers.  This brings these in line with the rest of the types of managers.
Required for:

https://github.com/ManageIQ/manageiq-providers-foreman/pull/103

Is this related to that storage_manager issue I saw yesterday?

@Fryguy no that's something different


Removes arc_weak and socket_timeout features

And updates README and CHANGELOG files.

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

Seems okay. Waiting for the CI tests.

4 hours already and windows CI warns that the test is still "queued". =(


No alert when critical events happen in silence period

Test process:

Silence a check
Then make the check from 0 (ok) to 2 (critical)
After the silence expired,  check still in critical status, but won't receive any alter unit refresh time reach.
sensu-server log showing   ""output":"only handling every 144 occurrences"     (144 is refresh time/interval time)

Therefore, If in silence/stash period, any checks become critical,  and after the time the silence expired, we still can't know the critical checks.
After silence expired, the critical occurrences is great than check occurrences setting,  so that sensu won't trigger alert and just bail a "only handling every 144 occurrences".
Anyone can help checking on the issue ?
Appreciate for any help

I feel like this needs to be addressed in the occurrences gem. ping @cwjohnston

We might want another value to track so that we could say occurrences and occurrences_after_silence attributes so that we can handle that scenario better.


WIP: add commitment parameter to get_signatures_for_address (Fixes #145)

Commit: add commitment parameter to get_signatures_for_address, also get_confirmed_signature_for_address2 as that is still suppported
Hey @michaelhly. I have added some general helpers for getting the signature RPC arguments shared between these two client methods, and I think these source changes are ready to merge. However, I would like to add unit tests for this logic. Seems there is not unit tests for argument logic, just integration tests for the client.
My idea for this is to add a pytest fixture which is a unit test client, and add a test_client_rpc_args module under tests/unit/. Probably a good practice to get unit tests going for this argument logic in general. What do you think?

@michaelhly bump. if you'd prefer not too add these tests, this commit is merge-ready

@broper2 could you show me what a unit test would look like? Either with a code snippet here or by adding it to the PR

Hey @kevinheavey yeah probably poorly-worded on my part. This is actually being ironed out in my other PR regarding custom exceptions. Once I get direction on best-practice to have non-connected client to use in unit tests there, I will revisit this. Thanks!


pod-kill not working

2020-06-01T14:01:19.145Z        ERROR   controllers.PodChaos    failed to apply chaos action    {"reconciler": "podchaos", "action": "pod-kill", "error": "no pod is selected"}
github.com/go-logr/zapr.(*zapLogger).Error
/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
github.com/pingcap/chaos-mesh/controllers/twophase.applyAction
/src/controllers/twophase/types.go:187
github.com/pingcap/chaos-mesh/controllers/twophase.(*Reconciler).Reconcile
/src/controllers/twophase/types.go:153
github.com/pingcap/chaos-mesh/controllers/podchaos.(*Reconciler).schedulePodChaos
/src/controllers/podchaos/types.go:90
github.com/pingcap/chaos-mesh/controllers/podchaos.(*Reconciler).Reconcile
/src/controllers/podchaos/types.go:51
github.com/pingcap/chaos-mesh/controllers.(*PodChaosReconciler).Reconcile
/src/controllers/podchaos_controller.go:56
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:256
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.4.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
/go/pkg/mod/k8s.io/apimachinery@v0.17.1-beta.0/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
/go/pkg/mod/k8s.io/apimachinery@v0.17.1-beta.0/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
/go/pkg/mod/k8s.io/apimachinery@v0.17.1-beta.0/pkg/util/wait/wait.go:88
2020-06-01T14:01:19.150Z        DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/mutate-pingcap-com-v1alpha1-podchaos", "UID": "5dfc931e-a410-11ea-9b91-001c4a160177", "kind": "pingcap.com/v1alpha1, Kind=PodChaos", "resource": {"group":"pingcap.com","version":"v1alpha1","resource":"podchaos"}}
2020-06-01T14:01:19.150Z        INFO    podchaos-resource       default {"name": "pod-kill-example"}
2020-06-01T14:01:19.150Z        DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/mutate-pingcap-com-v1alpha1-podchaos", "UID": "5dfc931e-a410-11ea-9b91-001c4a160177", "allowed": true, "result": {}, "resultError": "got runtime.Object without object metadata: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:,Message:,Reason:,Details:nil,Code:200,}"}
2020-06-01T14:01:19.153Z        DEBUG   controller-runtime.webhook.webhooks     received request        {"webhook": "/validate-pingcap-com-v1alpha1-podchaos", "UID": "5dfd440a-a410-11ea-9b91-001c4a160177", "kind": "pingcap.com/v1alpha1, Kind=PodChaos", "resource": {"group":"pingcap.com","version":"v1alpha1","resource":"podchaos"}}
2020-06-01T14:01:19.153Z        INFO    podchaos-resource       validate update {"name": "pod-kill-example"}
2020-06-01T14:01:19.153Z        DEBUG   controller-runtime.webhook.webhooks     wrote response  {"webhook": "/validate-pingcap-com-v1alpha1-podchaos", "UID": "5dfd440a-a410-11ea-9b91-001c4a160177", "allowed": true, "result": {}, "resultError": "got runtime.Object without object metadata: &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:,Message:,Reason:,Details:nil,Code:200,}"}
2020-06-01T14:01:19.156Z        DEBUG   controller-runtime.manager.events       Warning {"object": {"kind":"PodChaos","namespace":"chaos-testing","name":"pod-kill-example","uid":"b625cfa6-a406-11ea-9b91-001c4a160177","apiVersion":"pingcap.com/v1alpha1","resourceVersion":"40062635"}, "reason": "ChaosInjectFailed", "message": "no pod is selected"}

@kapilbalwani Hi, Can you provide your chaos config? Judging from this log, no pod was selected, You can check the definition of selectors and make sure that the target pods met the selectors defined in chaos experiment.

-----------------pod-kill-example.yaml----------------------
apiVersion: pingcap.com/v1alpha1
kind: PodChaos
metadata:
name: pod-kill-example
namespace: chaos-testing
spec:
action: pod-kill
mode: one
selector:
namespaces:
- spedev
labelSelectors:
"app": "consent"
scheduler:
cron: "@every 1m"

@kapilbalwani Seems there is no pod with app=consent in ns spedev. Could you please check with the command kubectl get po -n spedev -l app=consent?

When i executed this command i got nothing:
-bash-4.2$ kubectl get po -n spedev -l app=consent
No resources found.
-bash-4.2$ kubectl get pod -n spedev -l app=consent
No resources found.
But while checking it through i am getting the output:
-bash-4.2$ kubectl get pods -n spedev|grep consent
consent-67d5659c78-wjvrx                    2/2     Running     0          3m31s

When i executed this command i got nothing:
-bash-4.2$ kubectl get po -n spedev -l app=consent
No resources found.
-bash-4.2$ kubectl get pod -n spedev -l app=consent
No resources found.
But while checking it through i am getting the output:
-bash-4.2$ kubectl get pods -n spedev|grep consent
consent-67d5659c78-wjvrx 2/2 Running 0 3m31s

Yes, you should add the label app: consent to that pod so that it can be selected by the chaos.

Thanks a lot @yeya24 . Instead added the label which was already there. Working now.


Cannot interact in Safari browser.

Describe the bug

Reproduction
Open the docs website in safari browser.
Expected behavior
When we open the page, the aside marker and appearance button can be interactive.
System Info
-

Additional context
No response
Validations

[X] Read the docs
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

The problem caused that island.js imports  react/react-dom by import map in production.But the compatibility is really poor, https://caniuse.com/?search=import map. And it cannot be support in all safari versions. Perherps we should inject some polyfill ahead to solve the problem, via https://github.com/guybedford/es-module-shims.

I'm going to do it

I'm going to do it

https://github.com/sanyuan0704/island.js/pull/51

It's better to use defer because it will be sure that the polyfill is executed before app script, but async not.

It's better to use defer because it will be sure that the polyfill is executed before app script, but async not.

You're right. I've changed the code. Please review.


8/23/2019 路江时评：川普重磅推“即将全面脱钩中共国”！脱钩之后，中共国将会怎样打回原形？

8/23/2019 路江时评：川普重磅推“即将全面脱钩中共国”！脱钩之后，中共国将会怎样打回原形？

Donald J. Trump
@realDonaldTrump
Our Country has lost, stupidly, Trillions of Dollars with China over many years. They have stolen our Intellectual Property at a rate of Hundreds of Billions of Dollars a year, & they want to continue. I won’t let that happen! We don’t need China and, frankly, would be far....
翻译推文
下午10:59 · 2019年8月23日·Twitter for iPhone
2.8万
转推
10.3万
喜欢
Donald J. Trump
@realDonaldTrump
·
11小时
回复
@realDonaldTrump
....better off without them. The vast amounts of money made and stolen by China from the United States, year after year, for decades, will and must STOP. Our great American companies are hereby ordered to immediately start looking for an alternative to China, including bringing..
Donald J. Trump
@realDonaldTrump
·
11小时
....your companies HOME and making your products in the USA. I will be responding to China’s Tariffs this afternoon. This is a GREAT opportunity for the United States. Also, I am ordering all carriers, including Fed Ex, Amazon, UPS and the Post Office, to SEARCH FOR & REFUSE,....
Donald J. Trump
@realDonaldTrump
·
11小时
....all deliveries of Fentanyl from China (or anywhere else!). Fentanyl kills 100,000 Americans a year. President Xi said this would stop - it didn’t. Our Economy, because of our gains in the last 2 1/2 years, is MUCH larger than that of China. We will keep it that way!


Tensorflow-gpu requires AVX instruction to import; even if using gpu for all calculations

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 18.04 Bionic Beaver
AMD Phenom x4 II 965
TensorFlow installed from (source or binary): binary; docker image tensorflow-1.8.0-gpu-py3
TensorFlow version (use command below): 1.18.0
Python version: 3.5
Bazel version (if compiling from source):N/A
GCC/Compiler version (if compiling from source):N/A
CUDA/cuDNN version:
CUDA 9.0
CuDNN 7.0.5
GPU model and memory:
Geforce GTX 760 (compute capability 3.0) 2GB
Exact command to reproduce:
import tensorflow as tf on tensorflow-gpu on system without AVX

Describe the problem
Jupyter Kernel crashes when doing import tensorflow as tfusing a system that does not have AVX.
Similarly if i enter a python shell and do import tensorflow as tf i get an Illegal Instruction (core dumped) error and it exits the shell.
I have confirmed this is due to the AVX instruction because when i use the docker image Tensorflow-1.15.0-gpu-py3 I am able to successfully import tensorflow.
Unfortunately, tensorflow 1.15.0 requires compute capability 3.5 or higher which is extremely frusterating because i cannot find a build of tensorflow online that supports compute capaibility 3.0 but does not use AVX instructions.
Why do i need a CPU that supports AVX just to import tensorflow when i dont actually need the AVX instruction since i have a supported GPU (at least it is supported on all tensorflow versions other than 1.15.0).
Is there a way around this or do i need to build tensorflow from source to not use AVX but to allow compute capability 3.0? I tried using tensorflow-gpu-1.18.0-devel-py to build a new version from source but it did not even ask me what compute capabilities i wanted to build for and so i just let it build but it took over 24 hours and it was still going.
Can someone either provide a tensorflow-gpu release with CUDA 9.0 and CuDNN 7 support that does not use AVX and supports compute capability 3.0 or at least tell me the best way to obtain such a build (since apparently building using the docker-devel image wont work).

@gunan I don't see any builds linked in that issue. Only a docker image for building. Can you at least show me where the build for the non-AVX, Compute Capable 3.0, tensorflow is?


Question - additional details needed on userDescriptor

In Users Get method, we need to pass {userDescriptor} to use this but there are no details about how to get this or what to provide. Can you share some examples?
https://docs.microsoft.com/en-us/rest/api/azure/devops/graph/users/get?view=azure-devops-rest-5.0

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

ID: 30241f0f-e9d4-68ea-b8ff-3aba3899bdbb
Version Independent ID: bf7786bc-f0c4-74cf-a056-9bae37754f47
Content: Graph REST API for Azure DevOps Services - Azure DevOps Services REST API
Content Source: docs-ref-conceptual/5.0/graph/index.md
Service: vsts
Product: devops
GitHub Login: @wnjenkin
Microsoft Alias: elbatk

Hi @gmahender  to get the descriptor of the user, you'll need to call this REST endpoint. Please let me know if you have additional questions.
https://docs.microsoft.com/en-us/rest/api/azure/devops/graph/descriptors/get?view=azure-devops-rest-5.0

Hi @wnjenkin ! I have this question as well.
The linked API for getting a user's descriptor requires a storageKey. But getting a storageKey requires a descriptor...
https://docs.microsoft.com/en-us/rest/api/azure/devops/graph/storage keys/get?view=azure-devops-rest-5.0
How is this intended to work?

Any update on this? I am also trying to understand how this is intended to be used?
I am creating a custom extension and for one of my requirements, i need to check if the user is part of a specific group or not and then enable or disable some content for the user.
For this i was trying to use the GraphClient. In that i do see some functions that i can use like checkMembershipExistence, but it requires subject descriptor and container descriptor. When i checked on that i could see that getDescriptor can be used to retrieve the descriptor, but then it requires storageKey and to retrieve storageKey we can use getStorageKey, but that requires subjectDescriptor.
So, can you please provide an example of how the GraphClient can be used in a custom extension to implement the above requirement?

For us to make it work, we used the project id as the 'storageKey' to get the descriptor. I hope they can give a better documentation for this one.


add a voice recognition component

I want to add a component called "voice recognition" to extra components. Basically, it may help when using iot dashboard for example. It's based on a speech to text API that is going to translate what you say to a text. :)

that is a good idea

Ok than i'll pull my code guys 💻💻

I want to add a component called "voice recognition" to extra components. Basically, it may help when using iot dashboard for example. It's based on a speech to text API that is going to translate what you say to a text. :)


Extension: low priority keybindings support

VSCode Version: 1.3.1
OS Version: OSX 10.11.5

In my Vim extension, escape is overridden in order to mimic Vim's behavior:
{
    // ...

    "contributes": {
        "keybindings": [
            // ...
            { "command": "amVim.escape", "key": "escape", "when": "editorTextFocus" }
        ]
    }
}

This overrides escape's default behaviors since VSCode appends extension keybindings to the end of default keybindings.
However, we need only to handle escape when none of the default behaviors got invoked. (So user can dismiss messages, cancel suggestions, etc.)
A low priority keybindings which are prepended to the VSCode's default keybindings should solve my problem.

@aioutecism You can always make your key binding more restrictive by adding more when clauses. For eg, in this case, you can let amVim.escape command is executed on key press escape when editor text is in focus and editor is in insert mode. For this you need to create the respective context key for vim mode (insert or normal) and implement your key binding and vim extension accordingly.
For more information refer to our sample vim extension code here - https://github.com/Microsoft/vscode-extension-samples/blob/master/vim-sample/package.json#L21

Keybinding context won't solve the problem.
For example, when suggest widget is shown in Vim's insert mode, escape should close the widget instead of exiting to normal mode. I cloud add suggestWidgetVisible to specify the context but then I have to add all the conditions when VSCode corresponding to  escape.
This is all the default behaviors I have to deal with:
{ "key": "escape", "command": "closeReferenceSearchEditor",     "when": "inReferenceSearchEditor && !config.editor.stablePeek" },
{ "key": "escape", "command": "closeFindWidget",                "when": "editorFocus && findWidgetVisible" },
{ "key": "escape", "command": "closeBreakpointWidget",          "when": "breakpointWidgetVisible && editorFocus" },
{ "key": "escape", "command": "leaveSnippet",                   "when": "editorTextFocus && inSnippetMode" },
{ "key": "escape", "command": "closeMarkersNavigation",         "when": "editorFocus && markersNavigationVisible" },
{ "key": "escape", "command": "closeReferenceSearch",           "when": "referenceSearchVisible && !config.editor.stablePeek" },
{ "key": "escape", "command": "closeParameterHints",            "when": "editorTextFocus && parameterHintsVisible" },
{ "key": "escape", "command": "closeQuickFixWidget",            "when": "editorFocus && quickFixWidgetVisible" },
{ "key": "escape", "command": "hideSuggestWidget",              "when": "editorTextFocus && suggestWidgetVisible" },
{ "key": "escape", "command": "cancelRenameInput",              "when": "editorFocus && renameInputVisible" },
{ "key": "escape", "command": "closeAccessibilityHelp",         "when": "accessibilityHelpWidgetVisible && editorFocus" },
{ "key": "escape", "command": "workbench.action.closeMessages", "when": "globalMessageVisible" }

Besides, escape's behavior may increase/change with VSCode update. It's not a good idea to keep tracking all changes about escape.

@aioutecism Your argument makes sense to me.
@alexandrudima @jrieken Is there a way to provide priorities for key bindings?

Internally yes but externally no. I believe extension and user config gets the highest prio since that are something more explicit. I believe this must be tackled with a long and complex when clause

@aioutecism In this case, having a complex when clause is the only way for extension writers.

Appending all the default escape keybindings to the end of extension's keybinding section in package.json results in what I need. Guess I have to live with that 😞


Add Tooltips To Channel Action Buttons

First Timers Only
This issue is reserved for people who haven't contributed to our codebase before, or never contributed to Open Source. About First Timers Only.
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, consider leaving this one for someone new and looking through our general help wanted issues. Thanks!
🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
What is to be done?

Currently only the Tip button on the channel pages has a tooltip.

Having tooltips on the other buttons will improve consistency and also be helpful.
:mag_right: Files To Look Into:

The Tip button, for reference.
https://github.com/lbryio/lbry-desktop/blob/8b6c64441566f345cc9204d1906340526e741743/ui/page/channel/view.jsx#L203-L209

The Follow/Unfollow button.
https://github.com/lbryio/lbry-desktop/blob/master/ui/component/subscribeButton/view.jsx

The Share button.
https://github.com/lbryio/lbry-desktop/blob/master/ui/component/shareButton/view.jsx

The Block button.
https://github.com/lbryio/lbry-desktop/blob/master/ui/component/blockButton/view.jsx

📋 Step by Step

[ ] :scroll: Read The CONTRIBUTING File: We welcome contributions from everyone, the CONTRIBUTING will help you get started.

NOTE: Useful links:

Git Commands

Installation Instructions

[ ] Fork This Repository: A fork is a copy of this repository that is stored under your github account. A fork can be used to test out changes separately and then request to add those to the main repository as well!

[ ] :raising_hand: Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!

[ ] Create A New Branch: A branch is used to test new changes before they are merged with the stable master branch. You can create a new branch in the terminal. Make sure to name it descriptively!

[ ] :memo: Make The Requested Changes

[ ] :white_check_mark: Commit Your Changes: A Git commit is a change that is finalized and recorded in the branch.

[ ] :twisted_rightwards_arrows: Start a Pull Request(PR). There are two ways how you can start a pull request:

If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.

You can also open a PR from the browser.

[ ] 🏁 Done Ask in comments for a review :)

Please keep us updated
:speech_balloon: :bell:  - We encourage contributors to be respectful to the community and provide an update within a week of claiming a first-timers-only issue. We're happy to keep it assigned to you as long as you need it if you update us with a request for more time or help, but if we don't see any activity a week after you claim it we may reassign it to give someone else a chance. Thank you in advance!
If this happens to you, don't sweat it! Grab another open issue.
Is someone else already working on this?
🔗- We encourage contributors to link to the original issue in their pull request so all users can easily see if someone's already started on it.
👥- If someone seems stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!
🤔❓ Questions?
Leave a comment below!

Is this one fine for first-timers?

Yep!

Hi! Can I work on this issue? Thanks.

Sure. Go ahead.

@seanyesmunt new contributor already :rocket:!

@calvincodes you can ask any difficulty here.

Thanks @HarshKhandeparkar. Sure, will do.

@HarshKhandeparkar What should the language/content of these messages be?

Language should be English. Content can be whatever you feel is Intuitive.
On Tue, 28 Apr, 2020, 9:01 AM Arpit Jain<EMAIL_ADDRESS>wrote:

@HarshKhandeparkar https://github.com/HarshKhandeparkar What should the
language/content of these messages be?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lbryio/lbry-desktop/issues/4085#issuecomment-620358778,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIJI5HZPWAZQNMTM4SAPUPTROZE2RANCNFSM4MR7HCUQ
.


Vector container is not correctly created in cassDC

What happened?

The image that is ending up in the sts is actually system logger instead of the vector container that should appear.  This is despite vector being enabled. I'm pretty sure that means it should be a vector image instead of the system-logger image since this is the default from the struct tags if the vector struct is non-nil.
The podSecurityContext isn't being validated properly, I can include stuff like capabilities in this field, even though that doesn't exist on the PodSecurityContext type.
When adding configurations to the Container field for the server-system-logger container, it appears that these do not propagate into the CassDC as expected.

A test demonstrating these problems can be found here.

The image that is ending up in the sts is actually system logger instead of the vector container that should appear. This is despite vector being enabled. I'm pretty sure that means it should be a vector image instead of the system-logger image since this is the default from the struct tags if the vector struct is non-nil.

In case this ticket gets mentioned in the release notes: This isn't correct, the server-system-logger is a docker image that bundles Vector, since cass-operator uses Vector to do the tailing (and provides the capabilities to modify how Vector is used).
One should not replace the server-system-logger image with the vector.io ones.

In case this ticket gets mentioned in the release notes: This isn't correct, the server-system-logger is a docker image that bundles Vector, since cass-operator uses Vector to do the tailing (and provides the capabilities to modify how Vector is used).

Alex explained to me that this had been changed a while back. I didn't realised we'd started doing it this way - makes sense now he's explained it.


Prevent saving more than one entry per day

As of right now, you can add multiple entries for one date. This needs to be forbidden by the backend.
On saving, the backend should check if there's an entry for the given date with the same UserID - if so, return an error code.

Has been fixed already.


The output of read_memory method with libxml 2.9.3 is different from the one with libxml 2.9.2

Summary
I found that the output of read_memory method for below environment were different for each other, using read_memory testing script.
Could you tell me that it is bug or not?

nokogiri: v<IP_ADDRESS>

libxml2: 2.9.2

nokogiri: latest master branch,  commit fe57e9080a8f1c238c706f0599d5fcfaeea33f8c

libxml2: 2.9.3

Testing script for read_memory method
I prepared the testing script to test read_memory method that is c library (ext/nokogiri/).
You can download from below URL,
test_nokogiri.rb.txt
Please rename test_nokogiri.rb.txt to test_nokogiri.rb
or can copy & paste from below text for testing.
test_nokogiri.rb
require 'rubygems'
require 'nokogiri'

puts Nokogiri::VERSION

module Nokogiri
  module HTML
    class Document < Nokogiri::XML::Document
      class << self
        def test_for_parse

          expect = <<'EOS'
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
b
EOS

          html = '<b'
          doc = read_memory("#{html}", nil, "UTF-8", 2145)
          puts doc.to_s
          p(doc.to_s == expect)
        end
      end
    end
  end
end

Nokogiri::HTML::Document.test_for_parse

Reproducing
Let me report for detail.
My environment is as below things.
$ ruby -v
ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux]

$ gcc --version
gcc (GCC) 5.3.1 20160406 (Red Hat 5.3.1-6)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Case1: nokogiri: v<IP_ADDRESS> (with libxml2: 2.9.2)
$ git checkout v<IP_ADDRESS>

$ bundle install --path vendor/bundle

$ bundle exec rake test
...
1328 tests, 3051 assertions, 0 failures, 0 errors, 4 skips

$ bundle exec ruby -Ilib bin/nokogiri -v
# Nokogiri (<IP_ADDRESS>)
    ---
    warnings: []
    nokogiri: <IP_ADDRESS>
    ruby:
      version: 2.3.0
      platform: x86_64-linux
      description: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/home/jaruga/git/nokogiri_v<IP_ADDRESS>/ports/x86_64-pc-linux-gnu/libxml2/2.9.2"
      libxslt_path: "/home/jaruga/git/nokogiri_v<IP_ADDRESS>/ports/x86_64-pc-linux-gnu/libxslt/1.1.28"
      libxml2_patches:
      - 0001-Revert-Missing-initialization-for-the-catalog-module.patch
      - 0002-Fix-missing-entities-after-CVE-2014-3660-fix.patch
      - 0003-Stop-parsing-on-entities-boundaries-errors.patch
      - 0004-Cleanup-conditional-section-error-handling.patch
      - 0005-CVE-2015-1819-Enforce-the-reader-to-run-in-constant-.patch
      - 0006-Another-variation-of-overflow-in-Conditional-section.patch
      - 0007-Fix-an-error-in-previous-Conditional-section-patch.patch
      - 0008-CVE-2015-8035-Fix-XZ-compression-support-loop.patch
      - 0009-Updated-config.guess.patch
      - 0010-Fix-parsering-short-unclosed-comment-uninitialized-access.patch
      - 0011-Avoid-extra-processing-of-MarkupDecl-when-EOF.patch
      - 0012-Avoid-processing-entities-after-encoding-conversion-.patch
      - 0013-CVE-2015-7497-Avoid-an-heap-buffer-overflow-in-xmlDi.patch
      - 0014-CVE-2015-5312-Another-entity-expansion-issue.patch
      - 0015-Add-xmlHaltParser-to-stop-the-parser.patch
      - 0016-Detect-incoherency-on-GROW.patch
      - 0017-CVE-2015-7500-Fix-memory-access-error-due-to-incorre.patch
      - 0018-CVE-2015-8242-Buffer-overead-with-HTML-parser-in-pus.patch
      - 0019-Do-not-print-error-context-when-there-is-none.patch
      - 0020-xmlStopParser-reset-errNo.patch
      - 0021-Reuse-xmlHaltParser-where-it-makes-sense.patch
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      - 0016-Fix-for-type-confusion-in-preprocessing-attributes.patch
      - 0017-Updated-config.guess.patch
      compiled: 2.9.2
      loaded: 2.9.2

Check the result for read_memory testing script.
$ bundle exec ruby -Ilib test_nokogiri.rb
<IP_ADDRESS>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
b
true

Case2: nokogiri: lastest master (with libxml2: 2.9.3)
$ git checkout master

$ git log --pretty=oneline | head -1
fe57e9080a8f1c238c706f0599d5fcfaeea33f8c Merge pull request #1451 from ashivasubramanian/master

$ bundle install --path vendor/bundle

$ bundle exec rake test
...
1375 runs, 3936 assertions, 0 failures, 0 errors, 4 skips

$ bundle exec ruby -Ilib bin/nokogiri -v
# Nokogiri (1.6.8.rc3)
    ---
    warnings: []
    nokogiri: 1.6.8.rc3
    ruby:
      version: 2.3.0
      platform: x86_64-linux
      description: ruby 2.3.0p0 (2015-12-25 revision 53290) [x86_64-linux]
      engine: ruby
    libxml:
      binding: extension
      source: packaged
      libxml2_path: "/home/jaruga/git/nokogiri/ports/x86_64-pc-linux-gnu/libxml2/2.9.3"
      libxslt_path: "/home/jaruga/git/nokogiri/ports/x86_64-pc-linux-gnu/libxslt/1.1.28"
      libxml2_patches: []
      libxslt_patches:
      - 0001-Adding-doc-update-related-to-1.1.28.patch
      - 0002-Fix-a-couple-of-places-where-f-printf-parameters-wer.patch
      - 0003-Initialize-pseudo-random-number-generator-with-curre.patch
      - 0004-EXSLT-function-str-replace-is-broken-as-is.patch
      - 0006-Fix-str-padding-to-work-with-UTF-8-strings.patch
      - 0007-Separate-function-for-predicate-matching-in-patterns.patch
      - 0008-Fix-direct-pattern-matching.patch
      - 0009-Fix-certain-patterns-with-predicates.patch
      - 0010-Fix-handling-of-UTF-8-strings-in-EXSLT-crypto-module.patch
      - 0013-Memory-leak-in-xsltCompileIdKeyPattern-error-path.patch
      - 0014-Fix-for-bug-436589.patch
      - 0015-Fix-mkdir-for-mingw.patch
      - 0016-Fix-for-type-confusion-in-preprocessing-attributes.patch
      - 0017-Updated-config.guess.patch
      compiled: 2.9.3
      loaded: 2.9.3

Check the result for read_memory testing script.
$ bundle exec ruby -Ilib test_nokogiri.rb
1.6.8.rc3
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd">
<b

false

=> The result is different!!

Hi,
Thank you for the very complete information on how to reproduce what you're seeing.
Because Nokogiri on MRI relies on libxml to do markup correction, I absolutely believe that the version of libxml affects this behavior.
Further, there is no standard way to correct broken or invalid markup, and so this cannot be classified as a bug, since the behavior of parsers is undefined.
Finally, this correction behavior is entirely internal within libxml, and so the Nokogiri code cannot reasonably "fix" the output to be consistent across libxml versions (though we have on occasion tried).
I hope this explanation answers your question. If not,  please feel free to post back questions.

Hi, @flavorjones
Thank you for your kind response.
Yes, your answer is great for me. I wanted to know whether it was bug for nokogiri or not. That means whether you are going to change nokogiri's code or not for that.
Because I am developing the RPM package for the gem package: "sanitize" [1] that is using "nokogiri". and the "sanitize" is affected by "nokogiri"'s this behavior.
So, now we could close this issue.
Thank you for your taking the time for me.
[1] https://github.com/rgrove/sanitize


Draft Box Unchecked at initial term submission

YAMZ throws a "Not Found" message if a user tries to submit a term with the draft box unchecked. It does not save any information.

I can confirm based on the current yamz.net. The term does not appear in my term list.

Should work now. Need to commit db session first before adding Draft tag.

@cr625 I just tried to create a term on yamz.net and still receive the Not Found message when the Draft tag is unchecked. Has the update code been deployed to yamz.net?

I don't think yet @jkunze handles the deployment.


Installation error: "fatal error C1083: 无法打开包括文件: 'math.h': No such file or directory"

Environment:
OS: Windows
Python version: 3.8
Pytorch version: 2
CUDA version: 11.7
Visual Studio version: 14.34.31933
GroundingDINO version: 0.1.0
Description:
I encountered an error while trying to install the GroundingDINO package. The error message I received is as follows:
E:\Develop\C\VisualStudio\IDE\VC\Tools\MSVC\14.34.31933\include\cstdlib(12): fatal error C1083: 无法打开包括文件: 'math.h': No such file or directory This error seems to be related to the missing "math.h" header file.
Steps to reproduce:
Run the installation command: python setup.py develop
Observe the error during the installation process.
Error log:
log.txt
Expected behavior:
The package should be installed successfully without encountering the "fatal error C1083" related to the missing "math.h" header file.
Additional context:
Please let me know if there is any further information or steps I should take to resolve this issue. Thanks for your help in advance.

一样的问题，我是GroundingDINO\csrc\MsDeformAttn\ms_deform_attn_cpu.cpp : fatal error C1083: 无法打开编译器生成的文件: “”: Invalid argument
error: command 'C:\Program Files (x86)\Microsoft Visual Studio\2022\BuildTools\VC\Tools\MSVC\14.35.32215\bin\HostX86\x64\cl.exe' failed with exit code 1


tflite-micro-arduino-examples: micro_test.h is missing

The tflite-micro-arduino-examples repository is missing the "testing" folder and therefore "micro_test.h".
The Get started with microcontrollers documentation uses hello_world_test.cc for the general introduction. It would be extremely helpful for new users to be able to follow these examples also on Arduino. Having the testing framework available in the Arduino library would also be a useful feature.

Thank you for your interest in TFLM, we appreciate your feedback.
The Get started with microcontrollers document and the associated hello_world_test application are designed for use only with the tflite-micro repository.  The tflite-micro repository is setup for use by those comfortable with using command-line interfaces and makefiles.
The tflite-micro-arduino-examples repository was created to provide a point-and-click method for demonstrating TFLM examples on actual hardware.  This purpose of this repository is primarily to show how to use a TFLM application with a physical microcontroller (as opposed to emulators/simulators), in the easiest way possible using the Arduino IDE.  As such, we do not support any unit tests within this repository.


Error! No secret found by uid or name XXX

I ran now lipp/login-with -e LW_SESSION_SECRET=... -e LW_JWT_SECRET=... -e LW_SUBDOMAIN=... -e LW_FACEBOOK_APPID=... -e FACEBOOK_APPSECRET=..., but still got the error Error! No secret found by uid or name "lw-reddit-clientsecret" (and the error changes every time). It looks like all env vars are required, even the optional ones?

I guess it should be LW_FACEBOOK_APPSECRET (you are missing the LW_).
Anyhow, this is how my output looks (locally):
$ LW_SESSION_SECRET=123 LW_JWT_SECRET=123333 LW_SUBDOMAIN=foo.bar.com LW_FACEBOOK_APPID=33 LW_FACEBOOK_APPSECRET=333 node server.js
Using subdomain "https://foo.bar.com" for callback urls
Configured strategies: facebook
Using login with "facebook" strategy

@sedubois do you still have this issue?

Hi! Thanks for replying. Sorry I haven't been able to come back to this. Feel free to close and I can reopen if I have further issues.

Thx


Contributor Section UI Update

Specifications

Remove the cards for @anushbhatia and me
Try to have a swish effect like this
Below the pictures, put the respective names
Below the names put the Github and Linkedin icons
Use microanimations for the social media icons
Try your level best to have the images change on click (as in the reference above).
The images (max of 3 for each card), text, link to social media should be loaded dynamically from the team.js as the current codebase does

sir, I want to work on it

Assigned for 4 days

I would like to work on it as a part of GSSoC'21.
can you please assign it to me.

i want to work on this as a part of Gssoc 21

i want to work on this as a part of Gssoc 21

Assigned for 3 days


Vulnerabilities found in OpenSUSE and OpenJDK

We use cafapi/opensuse-jdk11 as the base image for our docker build. We are using Trivy scanner to check for the vulnerabilities. In the latest scan, we found some vulnerabilities at the OS level and in the OpenJDK too.
=================================================================================================
Total: 4 (UNKNOWN: 0, LOW: 0, MEDIUM: 3, HIGH: 1, CRITICAL: 0)

+--------------------------+-------------------------+----------+-----------------------+------------------------+--------------------------------+
|         LIBRARY          |    VULNERABILITY ID     | SEVERITY |   INSTALLED VERSION   |     FIXED VERSION      |             TITLE              |
+--------------------------+-------------------------+----------+-----------------------+------------------------+--------------------------------+
| java-11-openjdk          | openSUSE-SU-2021:0719-1 | MEDIUM   | <IP_ADDRESS>-lp<IP_ADDRESS> | <IP_ADDRESS>-lp<IP_ADDRESS> | Security update for            |
|                          |                         |          |                       |                        | java-11-openjdk                |
+--------------------------+                         +          +                       +                        +                                +
| java-11-openjdk-devel    |                         |          |                       |                        |                                |
|                          |                         |          |                       |                        |                                |
+--------------------------+                         +          +                       +                        +                                +
| java-11-openjdk-headless |                         |          |                       |                        |                                |
|                          |                         |          |                       |                        |                                |
+--------------------------+-------------------------+----------+-----------------------+------------------------+--------------------------------+
| liblz4-1                 | openSUSE-SU-2021:0760-1 | HIGH     | 1.8.0-lp152.4.3       | 1.8.0-lp<IP_ADDRESS>      | Security update for lz4        |
+--------------------------+-------------------------+----------+-----------------------+------------------------+--------------------------------+

Hopefully, the fixes are available after minor upgrades.

@HarshdeepSingh4084 Can you confirm the specific version of the jdk image that you found these vulnerabilities in?

I don't think there's really an issue here.  The last release was 26th March (i.e. v3.3.0).  The contemporaneous security report shows no vulnerabilities but it is natural that new issues may be discovered post-release, and so if you scan the image now these will show up.
There will be a new release soon so that should include the latest fixes.
You can pull the latest prerelease version from the prereleases repository if you'd like to test it:
docker image pull cafapi/prereleases:opensuse-jdk11-3.4.0-SNAPSHOT


User issued assets

Hi,
with next golos HF will be introduced UIA (user issued assets). It will be possible to create own currencies (assets). There will be a bunch of new operations and data types.
asset_create_operation,
asset_update_operation,
asset_update_bitasset_operation,
asset_update_feed_producers_operation,
and so on
There are also some changes on existing marked operations and so on. Steemit does not have such feature and I don't saw it on the road map of steem.
There is the golos branch commit containing changes
https://github.com/GolosChain/golos/commit/9a4ecb3e609971bb70a139aff4a6e3b2c19b9a09
Whould it possible to integrate new operations and data types into steem-js? Probably because of new operations steem-js have to be branched.
I would do this integration by my self, could you then briefly explain, how to generate files with operations, and steeps to do it properly?
Thanks

These method will not supported by Steem.js directly you will need to fork it and update few files.
1: Add the new operations manually here:
https://github.com/steemit/steem-js/blob/master/src/broadcast/operations.json
2: Update serializer. There is a method on steemd called js_operation_serializer to generate this file based on blockchain code.
https://github.com/steemit/steem-js/blob/master/src/auth/serializer/src/operations.js
3: Then update the list here with new operations: https://github.com/steemit/steem-js/blob/dafb00ffd8f022d5143fe5e4c39a95334d28c680/src/auth/serializer/src/ChainTypes.js following the same order than here: https://github.com/steemit/steem-js/blob/master/src/auth/serializer/src/operations.js#L708-L765
Hope this help.

Thank you, I will try it.

Closing


fix bug when using passed in project_dir when using the API directly

When using the API directly for example:
    e = Librarian::Puppet::Environment.new(:project_path => project_path)

The path is ignored in the DSL because of a bug. (https://github.com/logicminds/librarian-puppet/blob/master/lib/librarian/puppet/dsl.rb#L45)
This is easily fixed by traversing the path method.
specfile.path.kind_of?(Pathname)

Additionally,  I attempted to create some tests for this but they are incomplete as I am unsure how to create the test with regards to setting a target.  Hoping you can help with this so I can finish the tests and get this PR merge and tested.
  rec = Librarian::Puppet::Receiver.new(target)

Since most people never use the API like this this bug has been masked for a while.

I have created a test in master da341d5 based on your PR that is succeeding, do you see anything wrong in there?

IIUC by the time you call Librarian::Dsl::run you need to pass the specfile location, environment.project_dir is no longer applicable
If you share your code I may understand better how you are trying to call it

Ok here is what I am doing.  After reviewing the code some more and your tests the piece I refactored doesn't work in this case and also because Librarian::Specfile.new.kind_of?(Pathname) seems to magically be true the originally code works as intended.  I have no idea why this works since it doesn't extend, include or subclass Pathname.
e = Librarian::Puppet::Environment.new(:project_path => project_path)
Librarian::Puppet::Action::Resolve.new(e, :force => true).run
e.lock.dependencies.map {|d| { d.name => d.source.uri.to_s,
                                   :type => d.source.class,
                                   :version => d.requirement.to_s} }

With regards to Librarian::Puppet::Action::Resolve.new(e, :force => true).run this seems to ignore the project directory. I would prefer not to use this but I don't know the code base that well to understand how to get a list of resolved dependencies without using this method.

I think I found the real issue but I am not sure.  It lies a little bit deeper in the code but its reproducible
The code replaces the specfile that contains the passed in project_dir with the default_specfile.  Because this default_specfile is a instance of Proc the following code fails to set the proper working directory which now becomes Dir.pwd.
https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/dsl.rb#L44-L48
So because this is set incorrectly the metadata file cannot be found.
https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/dsl.rb#L61
Your tests didn't cover some of the super class code which is why they were passing.  What really need to be done is environment.dsl(environment.specfile.path, []) which is equilivent to environment.spec
Its seems like the dependent library librarianp would need to set a property file in this part(https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/dsl.rb#L44-L48) then the
following section https://github.com/rodjek/librarian-puppet/blob/master/lib/librarian/puppet/dsl.rb#L61 would need to use this property instead of Dir.pwd as the default.
@carlossg thoughts?  I have added a new test case in my tests along with rebasing against master to include your new tests.

Found the issue, and fixed librarianp to make it work, check out the issue-308 branch, you can run the test with
DEBUG=true rspec spec/action/resolve_spec.rb


Volume cannot be mounted on Pod (iSCSI login failure)

From time to time we receive the following error message during the startup of a Pod when mounting the volume. We're using the Synology CSI driver. Access mode is ReadWriteOnly for the PVC. The issue can be fixed by manual intervention when accessing the node which still has the volume mounted and then unmounting this volume. The root cause of the issue might be related to a situation when 2 or more Pods at the same time try to mount the volume which is not possible. Deleting the Pod or scaling down all pods won't unmount the volume of the old node in probably 10% of the cases. Then scaling up the Pod again shows the issue as shown below:
Events:
Type     Reason       Age                 From     Message

Warning  FailedMount  22m (x28 over 67m)  kubelet  MountVolume.MountDevice failed for volume "pvc-2b9b73b4-049f-46e5-abbc-27f92eb71ca9" : rpc error: code = Internal desc = rpc error: code = Internal desc = Failed to login with target iqn [iqn.2000-01.com.synology:nasellvicloud.pvc-2b9b73b4-049f-46e5-abbc-27f92eb71ca9], err: iscsiadm: Could not login to [iface: default, target: iqn.2000-01.com.synology:nasellvicloud.pvc-2b9b73b4-049f-46e5-abbc-27f92eb71ca9, portal: <IP_ADDRESS>,3260].
iscsiadm: initiator reported error (19 - encountered non-retryable iSCSI login failure)
iscsiadm: Could not log into all portals
Logging in to [iface: default, target: iqn.2000-01.com.synology:nasellvicloud.pvc-2b9b73b4-049f-46e5-abbc-27f92eb71ca9, portal: <IP_ADDRESS>,3260]
(exit status 19)
Warning  FailedMount  2m22s (x29 over 65m)  kubelet  Unable to attach or mount volumes: unmounted volumes=[minio], unattached volumes=[], failed to process volumes=[]: timed out waiting for the condition

You mean ReadWriteOnce.
If you have more than one node, you should not be using RWO PVCs with an app that has many pods using the same PVC which is what you seem to be describing.

No, we want to mount the RWO PVCs from just one node. But sometimes the issue might happen when there are 2 pods using the same PVC on different nodes during a Pod's RollingUpdate or ReplicaSet's re-spawn of the pod (when the pod is deleted and recreated by the ReplicaSet). Then the new Pod cannot start which is valid, but sometimes when we scale down all pods, then start one pod again, we get into the mentioned issue and receive the error message from above.
Apart from that, I guess it would be good to change either to a StatefulSet (from Deployment) or to update the updateStrategy (ensuring there can be just one pod at a time)


feat: added test 'mode' to control speed/thoroughness of llm test

also removes old "ATTACK_PACK" env
drafting to give chance for change of argument name/values.
usage:

help example:

like it 👍


Updated example configuration files to use 'origin_type' instead of 'provider' in origin configs

I noticed when configuring Trickster that some of the example config files had the out-of-date field provider in their origin configurations. It started working once I changed them to origin_type. This PR is just updating those config files. I think I got them all, but let me know if I missed one.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

hi @cwadley Trickster 2.0 will use provider instead of origin_type, which is why it is that way in the main branch (recent change, see #499). For the 1.1 codebase (in the 1.1.x branch), origin_type is correctly shown in the examples. Sorry for the confusion!


Create createSerializer function that takes in RowVector instead of rowType/numRows

Summary:
As title.
Creates a PrestoSerializer based on RowVector rather than RowType and RowVector. Will be used in callsites where the encoding is not statically available via Options.
Differential Revision: D52569963

Closing this in favor of https://github.com/facebookincubator/velox/pull/8634


chore(ConcreteCategory/Bundled): remove outdated comment about Bundled.map

the definition is not reducible, so apparently this is fine.

Can someone familiar with the category theory portion of the library have a look?
maintainer merge

I agree with the sentiment of the comment. Do we know why it is not an abbrev?

@grunweg Can you try just making it an abbrev and seeing what breaks?

!bench

bors merge


Float last selected node to the developer

In the event that communication with a node fails, the developer sees an error but is unable to tell which node was chosen. This makes it difficult to dynamically manage a list of healthy nodes.
Would it be possible to make that last node selection available as a public property of the client ?

This makes it difficult to dynamically manage a list of healthy nodes.

This should probably be implemented by the SDK as a deprioritizing a node.

the developer sees an error but is unable to tell which node was chosen.

We never return these errors in v2 because we try a different node on node network failure. I'm not sure a good place to communicate this where it would work.


prettier and linting

@aymericdelab @r0man1337 deleted some unused files. Can you confirm this is ok.


Clear all data from storage

It would be good to have this as something I can do. How would you accomplish this?

Yes. The doc is missing how to delete a store.


mariadb with outlinevpn

Hello. Does outlinevpn have some module for centrilized user auth list? I need to change user list in one place, and 10 outlinevpn servers need to update user list and creds and give apportunity to auth.

Same question
Will be grateful for help


Allow filtering by mean, median, and quantile

We should allow filtering by the mean, median, and quantile.
For example, if I want to filter a dataset for values that above its mean, we could do:
Filter by      operator       value
septal_length  greater than   mean

UI wise, this has a couple issues:

value is a number, how could we input the mean? Perhaps a select?

for quantiles, we would need a fourth input specifying the quantile but that's likely too complex, we could instead provide predefined quantiles for 10%, 20%, ..., 90%

A datalist might solve both


Guidance around AllowBulkExecution

At what point does it make sense to enable AllowBulkExecution?
Does it have any impact on reads?
At the moment we're uploading just over 100 records to one container (indexed is about 1600RUs) and another 100 key-value records to another container (non-indexed is about 1300RUs, for comparison indexed is about 6500RUs).
The containers are written in two different threads. The items are created using this approach.
Container container = cosmosClient.GetContainer("myDb", "myCollection");

// Assuming your have your data available to be inserted or read
List<Task> concurrentTasks = new List<Task>();
foreach(Item itemToInsert in ReadYourData())
{
    concurrentTasks.Add(container.CreateItemAsync(itemToInsert, new PartitionKey(itemToInsert.MyPk)));
}

await Task.WhenAll(concurrentTasks);

When locally developing against the Cosmos Emulator it executes about 4-5times slower if I set AllowBulkExecution to true.
When running in debug mode I'm seeing "DocDBTrace Information: 0 : Batch is full - Max operation count 100 reached. "
When writing to real Cosmos in Azure, the difference isn't as pronounced (could be network latency due to running function locally), but AllowBulkExecution=true is still slower.
Am I correct that for this dataset, it appears it makes sense to leave AllowBulkExecution as default (false)?
In the future we will need to handle different datasets and much larger / more numerous data.  When will it make sense to enable AllowBulkExecution?

This bulk article does a good job of explaining when you should use bulk. There is also the option to use batch.

Are you doing a nightly dump of 2 million records into your Cosmos DB container? That is bulk.
Are you processing a stream of data that comes in batches of 100 thousand items you need to update? That is bulk too.

The article calls out 100 thousand items or millions of records. You are only working with 100. What is your reasoning to try using bulk for so few of items? You could also look into transactional batch support.

There is nothing magical about Bulk. The volume of data you are sending is under your control.
Cosmos DB has a predictive RU cost, meaning that a write operation with a document of a given size will always consume that amount of RU, so if one operation costs X, and you are sending 10K operations, that will consume 10K x X if executed in the same second.
What Bulk does is, on scenarios where the provisioned RU is more or less aligned with the data you want to process, it optimizes network, and optimizes the throughput utilization to push that data faster. It will be faster than doing those operations individually. It basically let's you squeeze more your provisioned throughput on scenarios where you want to consume it all and push data as fast as possible.
But if you are underprovisioned, there is no magic around it, you just cannot provision a 400 RU/s container and expect to send 10K operations and have them complete without throttling. Operations will get throttled.
The SDK automatically retries on throttles 9 times by default, and you can customize this through the CosmosClientOptions.MaxRetryAttemptsOnRateLimitedRequests, you can set it to a very high number and the SDK will keep retrying, so it will take longer, but eventually succeed.

@ealsur missed my points.
Regarding the “volume is under my control” and if “sending  operations”: I was trying to make the point that I don’t believe we control ‘quantity’ sent per second. Not with the async/WhenAll bulk examples provided - it would just line up as many requests as possible depending on the host platform and we don’t control the host platform. Not without writing a back-off throttling client wrapper.
So my next related point is you effectively have to set throughput of cosmos based on max operations per second of the client host platform(s) and that would likely be very overprovisione d (if active clients is variable) or you could atttempt to average it out but that would require heuristics or you have to rely on cross-host back-off throttling.
If you want to do bulk then there is an implicit assumption: you have more data than you can fit in the provisioned throughput/s. This bulk implementation solves in a narrow case where required send-throughput is capped and known.
I suggest it is brittle if ‘quantity/s’ is variable
and the only throttling is reactive to server side responses (rate limit)
I was trying to suggest there are alternative ‘bulk’ scenarios (eg variable, uncontrolled or unknown quantity/s) and they might benefit from the SDK providing a client side throttling which could be configured manually (in the case of multiple clients) or automatically capped based on the container’s configured throughput (for single client work loads) by default.

Even if you take Bulk out of the picture, always the compute will play a part in how much data you can push through.
Let's step back a bit and see the base scenario.
We have a benchmark tool that helps you understand how many operations per second you can do with a certain provisioned throughput: https://github.com/Azure/azure-cosmos-dotnet-v3/tree/master/Microsoft.Azure.Cosmos.Samples/Tools/Benchmark
Cosmos DB, once you consume more than what you have provisioned, it will throttle your requests. This means that they either fail, or if you have something that retries (like the SDK) they can eventually succeed but will take longer.
If you had X amount of documents / operations that you wanted to get through utilizing as much of the available throughput as possible, with the SDK, you could technically issue all the operations concurrently, create a List of Tasks, where each Task will do an operation and the rate at which they get executed will depend on your compute + network + available throughput (this is all without Bulk into the picture). This will issue independent network requests, one per operation, and all these requests in parallel will drain the available throughput. Obviously if you send more operations than what can be processed by your available throughput, operations will get throttled.
What Bulk does is optimize this scenario, not any other. How does it optimize it? By reducing the network utilization, and reducing the payloads that are sent, and encoding the contents. This effectively increases the throughput your compute can dish out. That is all Bulk does.
Currently the Bulk implementation does have a Congestion control that reduces the rate when encounters 429s or increases the rate if the current rate is not showing signs of throttling.
Does this mean that the volume of data that you want to push in needs to be higher than the provisioned throughput? No. But the flow is optimized for a large number of operations, because the overhead of packing the operations gets offset as the volume of operations increase. If you are doing a single write, and you send it through Bulk, the packing overhead cannot be faster than simply doing that single write.
We are working on improving the scenarios where the volume of operations is low, but the main scenario for Bulk has always been optimizing throughput.


#3724 Use React Testing Library for common-properties tests - Part 2 …

…(#3724)
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

PR-for Panel folder, 4 files completed, 7 files in progress (70% completed)


allow henlo.py to be called

henlo

this is a lib, there's already a example for using it in the readme :P

heck u
merge it

no u

Pls

fine™


Get parsl.serialize.errors.SerializationError when using Parsl htex to run docking and moldesign

Describe the problem.
Hi. I was trying to use Parsl htex to run docking. Here is my docking.toml file and my command is python3 -m taps.run --config docking.toml.
[app]
name = "failures"
base = "docking"
failure_rate = 0
failure_type = "import"

[app.config]
smi_file_name_ligand = "/work/cse-zhousc/resilient_compute/resilience_test/taiyi/debug/data/docking/dataset_orz_original_1k.csv"
receptor = "/work/cse-zhousc/resilient_compute/resilience_test/taiyi/debug/data/docking/1iep_receptor.pdbqt"
tcl_path = "/work/cse-zhousc/resilient_compute/resilience_test/taiyi/debug/data/docking/set_element.tcl"

[engine.executor]
name = "parsl-htex"
retries = 3

[engine.executor.htex]
max_workers = 32
radio_mode = "filesystem"

[engine.executor.htex.provider]
kind = "LSFProvider"
init_blocks = 1
max_blocks = 1
min_blocks = 1
nodes_per_block = 2
queue = "debug"
scheduler_options = ""
walltime = "00:30:00"

[engine.executor.monitoring]
hub_address = "localhost"
logging_endpoint = 'sqlite:///parsl-runinfo/monitoring.db'
resource_monitoring_interval = 1
hub_port = 55055

But then I was reported errors as follows. Quite long error messages, but I guess the root error is TypeError: cannot pickle '_abc._abc_data' object. This also happened when I tried to run moldesign app.
[2024-09-10 19:41:42.019] ERROR (parsl.dataflow.dflow) > Task 20 failed after 3 retry attempts
Traceback (most recent call last):
  File "/work/cse-zhousc/parsl_resilient/parsl/executors/high_throughput/executor.py", line 646, in submit
    fn_buf = pack_apply_message(func, args, kwargs,
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/facade.py", line 58, in pack_apply_message
    b_func = serialize(func, buffer_threshold=buffer_threshold)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/facade.py", line 94, in serialize
    raise result
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/facade.py", line 86, in serialize
    result = method.identifier + b'\n' + method.serialize(obj)
                                         ^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/concretes.py", line 60, in serialize
    return dill.dumps(data)
           ^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 263, in dumps
    dump(obj, file, protocol, byref, fmode, recurse, **kwds)#, strictio)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 235, in dump
    Pickler(file, protocol, **_kwds).dump(obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 394, in dump
    StockPickler.dump(self, obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 487, in dump
    self.save(obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1824, in save_function
    _save_with_postproc(pickler, (_create_function, (
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1070, in _save_with_postproc
    pickler.save_reduce(*reduction, obj=obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 717, in save_reduce
    save(state)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 887, in save_tuple
    save(element)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1186, in save_module_dict
    StockPickler.save_dict(pickler, obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 972, in save_dict
    self._batch_setitems(obj.items())
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 998, in _batch_setitems
    save(v)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1824, in save_function
    _save_with_postproc(pickler, (_create_function, (
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1070, in _save_with_postproc
    pickler.save_reduce(*reduction, obj=obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 717, in save_reduce
    save(state)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 887, in save_tuple
    save(element)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1186, in save_module_dict
    StockPickler.save_dict(pickler, obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 972, in save_dict
    self._batch_setitems(obj.items())
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 998, in _batch_setitems
    save(v)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 603, in save
    self.save_reduce(obj=obj, *rv)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 692, in save_reduce
    save(args)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 887, in save_tuple
    save(element)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1824, in save_function
    _save_with_postproc(pickler, (_create_function, (
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1084, in _save_with_postproc
    pickler._batch_setitems(iter(source.items()))
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 998, in _batch_setitems
    save(v)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1698, in save_type
    _save_with_postproc(pickler, (_create_type, (
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1070, in _save_with_postproc
    pickler.save_reduce(*reduction, obj=obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 692, in save_reduce
    save(args)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 902, in save_tuple
    save(element)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 560, in save
    f(self, obj)  # Call unbound method with explicit self
    ^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 1186, in save_module_dict
    StockPickler.save_dict(pickler, obj)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 972, in save_dict
    self._batch_setitems(obj.items())
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 998, in _batch_setitems
    save(v)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/dill/_dill.py", line 388, in save
    StockPickler.save(self, obj, save_persistent_id)
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/pickle.py", line 578, in save
    rv = reduce(self.proto)
         ^^^^^^^^^^^^^^^^^^
TypeError: cannot pickle '_abc._abc_data' object

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 323, in handle_exec_update
    res = self._unwrap_remote_exception_wrapper(future)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 593, in _unwrap_remote_exception_wrapper
    result = future.result()
             ^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 653, in launch_if_ready
    exec_fu = self.launch_task(task_record)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 747, in launch_task
    exec_fu = executor.submit(executable, task_record['resource_specification'], *args, **kwargs)
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/executors/high_throughput/executor.py", line 649, in submit
    raise SerializationError(func.__name__)
parsl.serialize.errors.SerializationError: Failed to serialize objects for an invocation of function wrapper. Refer https://parsl.readthedocs.io/en/latest/faq.html#addressing-serializationerror

So I searched for this dill error message TypeError: cannot pickle '_abc._abc_data' object and found that it was addressed in dill 0.3.7 so I upgraded dill to this version. But then I was reported:
globus-compute-sdk 2.27.1 requires dill==0.3.6; python_version >= "3.11", but you have dill 0.3.7 which is incompatible.

If ignore this version conflict and run this app again, I got another error related to deserialization.
[2024-09-10 20:13:26.825] ERROR (parsl.dataflow.dflow) > Task 20 failed after 3 retry attempts
Traceback (most recent call last):
  File "/work/cse-zhousc/parsl_resilient/parsl/executors/high_throughput/executor.py", line 483, in _queue_management_worker
    s = deserialize(msg['exception'])
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/facade.py", line 130, in deserialize
    result = deserializer.deserialize(body)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/serialize/concretes.py", line 26, in deserialize
    return pickle.loads(body)
           ^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/site-packages/tblib/pickling_support.py", line 26, in unpickle_exception
    inst = func(*args)
           ^^^^^^^^^^^
TypeError: PydanticErrorMixin.__init__() missing 1 required keyword-only argument: 'code'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 323, in handle_exec_update
    res = self._unwrap_remote_exception_wrapper(future)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/parsl_resilient/parsl/dataflow/dflow.py", line 593, in _unwrap_remote_exception_wrapper
    result = future.result()
             ^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/concurrent/futures/_base.py", line 449, in result
    return self.__get_result()
           ^^^^^^^^^^^^^^^^^^^
  File "/work/cse-zhousc/miniconda3/envs/taps-docking2/lib/python3.11/concurrent/futures/_base.py", line 401, in __get_result
    raise self._exception
parsl.serialize.errors.DeserializationError: Failed to deserialize objects. Reason: Received exception, but handling also threw an exception: PydanticErrorMixin.__init__() missing 1 required keyword-only argument: 'code'

I wonder whether this dill version limit is important. If so, how can we address the _abc._abc_data object pickle problem? If not, what is this PydanticErrorMixin?
How did you install TaPS?
$ git clone git@github.com:ClaudiaCumberbatch/webs.git
# synchronized with the newest TaPS version in this repo

TaPS Version
a7001b33cf0c2907685d890e6623c433b96719ae
Python Version
3.11
OS and Platform
x86 linux

Thanks for writing this up, Sicheng! And also sorry that you've run into so many errors---we don't have a good way of doing regression testing yet since there are so many combinations of apps and executors. I hope to work on better integration testing soon.
I'll take a look at this tomorrow morning. The globus-compute-sdk pinned version of dill always causes headaches, and someone else also encountered this _abc._abc_data  error in the Flox/Flight project a couple weeks ago.
I think it would be good to let users just install which executors they plan to use. E.g.,
pip install -e .[dask,parsl]

if you didn't want Globus Compute.
The _abc._abc_data error seems to have been introduced by a recent refactor I did to the Engine internals (specifically how the task is wrapped). My suspicion is that Parsl is serializing the wrapper code which contains type annotations for some abstract base classes.

Quick update---this bug is specific to the failures app. I think because of how the task wrappers get serialized by value with dill.
Upgrading to dill==0.3.8 also solved the problem for me, but I did not encounter the PydanticErrorMixin.__init__() missing 1 required keyword-only argument: 'code' error. I tried with both the docking and moldesign apps.
Is there anything else specific to your environment that may be different? I do notice that I had to change max_workers to max_workers_per_node in your config.
[engine.executor.htex]
max_workers_per_node = 32

Since I can't replicate the second issue, I'm going to focus on the original _abc._abc_data serialization error. I tried/considered the following:

Changing the structure of the failure app task wrappers. I couldn't get this to work in a way that circumvented the serialization by value of function annotations that included pydantic models (which are the source of the _abc._abc_data errors).
I considered allowing only installing specific executors, but for the time being this is fairly complicated because of the plugin registration system.

Here's some things I will do:

Add a note to the failures app about the dill version conflict and Globus Compute incompatibility.
Reach out the the Globus Compute team about bumping that dill version.

Hopefully the second error you got after upgrading dill was transient, or can be solved via recreating your environment. Ultimately, upgrading dill is really the best solution to this problem, even if it's incompatible with Globus Compute.

Thanks for the update! I was using dill==0.3.7 the day before yesterday and now I see that dill==0.3.8 solves the problem.
(btw, I am using max_workers because I forked Parsl earlier this year for some experiments and now in the main branch it was changed into max_workers_per_node)

Hey @ClaudiaCumberbatch, I found a way to fix this issue in #155, so dill==0.3.6 should work now with the failures app.
If you run into anymore related issues, let me know. I tested a lot of combinations of executors and failure types, but I didn't test every single application.


5.0.1 release

This is the metadata for the 5.0.1 release, and some associated updates to the tooling to support the json generation

Awesome!


Possible to lint vue files via CLI?

Hi! I found this project the other day and I would love to use it as an alternative to typescript-eslint for the typed lintings, as they are currently very slow with eslint.
I created the following config based on reading some of the other issues:
import { defineConfig } from '@tsslint/config'
import { convertConfig } from '@tsslint/eslint'

export default defineConfig({
  rules: convertConfig({
    '@typescript-eslint/no-misused-promises': 'error',
    '@typescript-eslint/no-floating-promises': 'error',
  }),
})

Running the CLI is very much faster than eslint however it only shows errors in .ts files, despite Vue files being included in the config:
{
  "includes": ["src/**/*.ts", "src/**/*.vue"]
}

After some investigation it seems that the culprit is this call here, as by default the fileNames returned only include TypeScript files. I hacked around a bit and was able to get it to recognize Vue files as well with the following change:
- return ts.parseJsonSourceFileConfigFileContent(jsonConfigFile, ts.sys, path.dirname(tsconfig), {}, tsconfig);
+ return ts.parseJsonSourceFileConfigFileContent(jsonConfigFile, ts.sys, path.dirname(tsconfig), {}, tsconfig, undefined, [{ extension: 'vue', isMixedContent: true, scriptKind: 7 }]);

but unfortunately it fails once it reaches a Vue file with:
▲  Something went wrong

What's interesting is if I use the typescript-language-server plugin, the <script lang="ts"> portion of the Vue files are correctly linted and will show errors according to the config.
As I was hoping to use this as a faster linter for CI as well as locally, is there any way to apply the same checks on non-TypeScript files like it works within the language server?
Thanks!

It didn't come true because you were the first to ask for it.
Vue support is available naturally in the IDE (as long as hybrid mode is enabled). In the CLI we need to integrate @vue/language-core, I'm looking into it.

Please track #32

@gjabell it should be support in 1.4.1, could you take try? Thanks.

@gjabell thanks for the reproduction, this problem should be fixed in 1.4.2.


PubSub Webhook Registration Failing

My PubSub Webhooks are failing to register

@shopify/shopify-api version: 6.2. 0
Node version: 14.10.0
Operating system: Mac OS

// Paste any relevant logs here

Expected behavior
The registration should be successful without error
Actual behavior
The registration is unsuccessful as per my logs
Steps to reproduce the problem
This is my handler code
const pubSubProjectId = process.env.FIREBASE_PROJECT_ID;
await shopify.webhooks.addHandlers({
  APP_UNINSTALLED: {
    deliveryMethod: DeliveryMethod.Http,
    callbackUrl: "/webhooks",
    callback: async (topic, shop_domain, body, webhookId, apiVersion) =>
      delete ACTIVE_SHOPIFY_SHOPS[shop_domain],
  },
  ORDERS_CREATE: {
    deliveryMethod: DeliveryMethod.PubSub,
    pubSubProject: pubSubProjectId,
    pubSubTopic: "order-created-on-shopify",
  },
  ORDERS_FULFILLED: {
    deliveryMethod: DeliveryMethod.PubSub,
    pubSubProject: pubSubProjectId,
    pubSubTopic: "order-fulfiiled-on-shopify",
  },
  ORDERS_CANCELLED: {
    deliveryMethod: DeliveryMethod.PubSub,
    pubSubProject: pubSubProjectId,
    pubSubTopic: "order-cancelled-on-shopify",
  },
  ORDERS_DELETE: {
    deliveryMethod: DeliveryMethod.PubSub,
    pubSubProject: pubSubProjectId,
    pubSubTopic: "order-deleted-on-shopify",
  },
  ORDERS_UPDATED: {
    deliveryMethod: DeliveryMethod.PubSub,
    pubSubProject: pubSubProjectId,
    pubSubTopic: "order-updated-on-shopify",
  },
});

and this is the function that does the register
 async function registerWebhooks(session) {
    const response = await shopify.webhooks.register({ session: session });
    console.log(`Webhook register response: ${response}`);

    const appUninstalledHook = response["APP_UNINSTALLED"];
    const ordersCreateHook = response["ORDERS_CREATE"];
    const ordersFulfilledHook = response["ORDERS_FULFILLED"];
    const ordersCancelledHook = response["ORDERS_CANCELLED"];
    const ordersDeleteHook = response["ORDERS_DELETE"];
    const ordersUpdatedHook = response["ORDERS_UPDATED"];
    if (!appUninstalledHook.success) {
      console.log(
        `Failed to register APP_UNINSTALLED webhook: ${appUninstalledHook.result}`
      );
    }
    if (!ordersCreateHook.success) {
      console.log(
        `Failed to register ORDERS_CREATE webhook: ${ordersCreateHook.result}`
      );
    }
    if (!ordersFulfilledHook.success) {
      console.log(
        `Failed to register ORDERS_FULFILLED webhook: ${ordersFulfilledHook.result}`
      );
    }
    if (!ordersCancelledHook.success) {
      console.log(
        `Failed to register ORDERS_CANCELLED webhook: ${ordersCancelledHook.result}`
      );
    }
    if (!ordersDeleteHook.success) {
      console.log(
        `Failed to register ORDERS_DELETE webhook: ${ordersDeleteHook.result}`
      );
    }
    if (!ordersUpdatedHook.success) {
      console.log(
        `Failed to register ORDERS_UPDATED webhook: ${ordersUpdatedHook.result}`
      );
    }
  }

Any help would be really appreciated. Thanks

What's the error message displayed for the failed registrations?

What's the error message displayed for the failed registrations?

This the message i receive
2023-04-10T16:37:58.160256+00:00 app[web.1]: [shopify-api/INFO] Registering webhooks | {shop: conzume.myshopify.com}

2023-04-10T16:37:58.161037+00:00 app[web.1]: [shopify-api/DEBUG] Making HTTP request  -  POST https://conzume.myshopify.com/admin/api/2023-01/graphql.json  -  Headers: {"X-Shopify-Access-Token":["correct_access_token"],"User-Agent":["Shopify API Library v6.2.0 | Node v14.21.3"],"Content-Type":["application/graphql"],"Content-Length":["576"]}  -  Body: "{\n  webhookSubscriptions(\n    first: 250,\n    after: null,\n  ) {\n    edges {\n      node {\n        id\n        topic\n        includeFields\n        metafieldNamespaces\n        privateMetafieldNamespaces\n        endpoint {\n          __typename\n          ... on WebhookHttpEndpoint {\n            callbackUrl\n          }\n          ... on WebhookEventBridgeEndpoint {\n            arn\n          }\n          ... on WebhookPubSubEndpoint {\n            pubSubProject\n            pubSubTopic\n          }\n        }\n      }\n    }\n    pageInfo {\n      endCursor\n      hasNextPage\n    }\n  }\n}"

2023-04-10T16:37:58.368867+00:00 app[web.1]: [shopify-api/DEBUG] Completed HTTP request, received 200 OK

2023-04-10T16:37:58.369294+00:00 app[web.1]: [shopify-api/DEBUG] Existing topics: [APP_UNINSTALLED, ORDERS_CANCELLED, ORDERS_DELETE, ORDERS_UPDATED, ORDERS_CREATE, ORDERS_FULFILLED]


Upgrade prestashop_test_lib version to upgrade playwright for E2E tests

Questions
Answers

Description?
Upgrade prestashop_test_lib version to upgrade playwright for E2E tests

Type?
refacto

BC breaks?
no

Deprecations?
no

Fixed ticket?
no

How to test?
GA should be green

Thank you @boubkerbribri


Codelab as completed

Branch reflecting codelab in final completed state

Hello, closing this PR - the codelab is meant to be in a starting state with the final changes commented out.


Comment out scoped validation until VM issue is sorted

Overview
Comment out scoped validation until VM issue is sorted

/azp run


separate conditional dependencies

move cln-rpc to regular dependencies
add whitespace to separate conditional dependencies

fixes build on MSVC and OpenBSD

Merged, thanks!


bpf: sock_ops event PASSIVE_ESTABLISHED_CB missed

In some TCP sessions (notably with 'wrk' stress tests) we are not receiving a PASSIVE_ESTABLISHED_CB event yet the state of the socket is ESTABLISHED. We need to add event hooks in all paths to ESTABLISHED TCP state to properly track socket state.

Its not that we miss a state transition its http using the Linux option 'TCP_DEFER_ACCEPT' which breaks the kproxy because kproxy is using the accept trigger as a signal to add the port into the table of managed sockets. So effectively we only manage 1/2 of the session until after the data is received on the http side.
Work-around is to disable the option in httpd. A better fix will be to signal adding the socket to the managed socket list before accept.

Will need to pull in these connections from earlier state transition. Leave this issue open to prototype BPF datapath code.


could not create new container while Docker > v1.10

error says:
Codetainer 19:41:28 [FATAL] Unable to create codetainer: API error (400): {"message":"starting container with HostConfig was deprecated since v1.10 and removed in v1.12"}

@tjomk @qxhy123 merged


BUG: Weird behavior at some width range.

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
The side-nav bar is looking ugly in the range 768px and 989px
768px:

989px:

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@RitiChandak please check the attached pr.


how to connect to ES(7.15) using X Pack Security  with ssl

I try to use application.conf like this:
play.ws.ssl {    keyManager = {    stores = [     {         type = "PKCS12",         path = "/data/cerebro-0.9.4/elastic-certificates.p12",         password = ""       }     ]  }  trustManager = {    stores = [      { type = "PEM", path = "/data/cerebro-0.9.4/elastic-ca.pem" }    ]  } }
but it fails because error: java.security.cert.CertificateException: No subject alternative names present
it can use like kibana, using  ssl mode: certificate?

Did you try using also the following key?
play.ws.ssl.loose.disableHostnameVerification=true