'npm install' stucks at reify

Hi,
I just upgraded the package to 1.6.0. Then executed npm install. It stucks at "reify". Then I downgraded to 1.5.1. npm install did work then fine. Then one more time upgraded to 1.6.0. It stucked again (pls see the screenshot). So it seems to be there is something with the new version that blocks npm install.

Bests,
Ilhami

Thanks for letting us know. We will check it out.

OK. Here are some might be usefull information:
My NodeJs version is 16.15.1 LTS. I tried with 18.4.0. It changed nothing, same error.
Then I downgraded to 14.x. This time it did work though. I could install react-to-webcomponent package.
Bests, Ilhami

Hey @bahag-xvisnei. I wasn't able to recreate the problem locally, but I think I did discover the issue. There was a postinstall script that was supposed to be dev-only. I removed that and published a new version (v1.6.1). Could you try installing that version and let me know if the error is fixed or if it persists?

Thanks @christopherjbaker, I just tried it with Node 16. It works.


[Feature][UI] Add manual input for scheduling dates.

Purpose of the pull request
This pull request adds manual input for scheduling dates.
Annexes

Related issue
#10370

Codecov Report

Merging #10396 (631aafb) into dev (9782fe4) will increase coverage by 0.03%.
The diff coverage is 95.45%.

:exclamation: Current head 631aafb differs from pull request most recent head e51f8db. Consider uploading reports for the commit e51f8db to get more accurate results

@@             Coverage Diff              @@
##                dev   #10396      +/-   ##
============================================
+ Coverage     40.53%   40.56%   +0.03%
- Complexity     4760     4766       +6
============================================
  Files           877      877
  Lines         35607    35621      +14
  Branches       3945     3945
============================================
+ Hits          14432    14450      +18
+ Misses        19741    19738       -3
+ Partials       1434     1433       -1

Impacted Files
Coverage Δ

...nscheduler/plugin/task/mlflow/MlflowConstants.java
0.00% <ø> (ø)

...olphinscheduler/plugin/task/mlflow/MlflowTask.java
71.95% <90.90%> (+3.89%)
:arrow_up:

...scheduler/plugin/task/mlflow/MlflowParameters.java
77.08% <100.00%> (+10.77%)
:arrow_up:

...org/apache/dolphinscheduler/remote/utils/Host.java
37.77% <0.00%> (-2.23%)
:arrow_down:

...dolphinscheduler/remote/future/ResponseFuture.java
81.96% <0.00%> (-1.64%)
:arrow_down:

...e/dolphinscheduler/remote/NettyRemotingClient.java
52.11% <0.00%> (-1.41%)
:arrow_down:

...r/plugin/task/sqoop/parameter/SqoopParameters.java
53.33% <0.00%> (-1.34%)
:arrow_down:

Continue to review full report at Codecov.

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


[misc] fix custom allreduce p2p cache file generation

previously, we directly use the output of the test process to unpickle.
however, that process might have some warning messages, e.g. in https://github.com/vllm-project/vllm/issues/7846
we should add markers to mark the start and end of the data.

@youkaichao wdyt about just doing it via a temp file instead, probably would be cleaner?

@njhill thanks for the suggestion, it makes sense to me. please check the new code.


Fix all edge swipe gestures

Fixes https://github.com/motif/company/issues/2225

Tested a bit. LGTM.


fix: Fix extract not working on windows

Maybe I was a little bit too ambitious with the update of the dependencies. I realized earlier that the extract is not picking up keys on my windows machine. The newer versions of glob require that the patterns should always use forward slash.
https://github.com/isaacs/node-glob#readme

We should probably add windows to the CI workflow. Are you interested in attempting that?

We should probably add windows to the CI workflow. Are you interested in attempting that?

We could do that but the main problem is that the extract.task.ts is not tested... We should first add some smoke tests there and since that would probably mean that we will mock the file system maybe adding windows to the workflow won't be necessary.

Ah ok. Well I just added windows anyway - it's a tiny change so worth having there for catching future issues.
I just published v9.0.2 with the latest fixes. Thanks for your work on this!


Readme overhaul

I updated a few things in the readme, definitely let me know if you have any feedback. The style changes are totally up to you if you want to use them, if you're not interested no big deal.
You can view the modified read me here.
Thanks!
Chase

amazing, super lucky to have you involved :)


Text Fields and Select borders do not render on initial load in Safari

Summary of the bug
Text Fields and Select borders do not render on initial load in Safari
🪜 How to reproduce

Open Safari
Navigate to Text Field & Select pages
Notice how the border does not load until you move your mouse/change state

📸 Screenshots or code
If you can, add screenshots to show the problem. If you need to show a code example, you can include a snippet or link to a repository with an example.
🧐 Expected behaviour
The border to appear

Can't replicate in Storybook, only the site


Projections Apply Event is not called for base class, when Apply for child class is not present.

When an aggregation has an Apply event for a base class, but no Apply event for the Event class itself, the base Apply is not called.

We, @jeremydmiller  and I decided the correct method to approach this is to implement an IProjection with a custom aggregation to do this.


Visual Studio 2022 (NOT VS CODE) -- Inline comment-invoked prompt doesn't work

Visual Studio 2022 v. 4.8.09032 and v. 17.8.0 Preview 1 (NOT VS CODE)
OS Version: Windows 11
GH Copilot v. 1.1000.0.0 (@6ffo82509
GH Copilot Chat v. 01.1227.30434
In current version of Visual Studio 2022 (v. 4.8.09032), inline comments do nothing (image 1):

However, in the prerelease version of Visual Studio 2022 (17.8.0 Preview 1), inline comments generate code as expected (image 2):

Note in scenario 1, where inline comments do nothing, no telemetry/logging generated in GitHub Copliot Chat output window.

This repo is just for vscode it looks like https://github.com/orgs/community/discussions is the right place for VS copilot feedback


⚠ Bofrost.at has degraded performance

In 4ac30c0, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 3829 ms

Resolved: Bofrost.at performance has improved in 7b20c77.


Auto create release version branch from .x branch on start of release cycle process

Is your feature request related to a problem? Please describe
We currently wait for individual repo managers to create the release branch before switching the build manifest to point to appropriate release branch for building a release candidate corresponding to specific OpenSearch version.
Acceptance criteria:

Add a workflow to create a new branch if doesn't exist.
Run the workflow from source branch to target branch when required.
Get the repo list from the Input Manifest and create the release branch the repos in the list.

Describe the solution you'd like
Implement an automated workflow to create the release branch from .x branch for corresponding OpenSearch and OpenSearch dashboards release version branch on beginning of release process.
Describe alternatives you've considered
Manually creating the release branch from .x branch.
Additional context
No response

One of the major concern with this is even though we cut major.minor branch from major.x branch, who approves the changes that are going in?
Considering worst case scenario if a feature was pushed to next release or was intended for future minor release (example: 2.13.0 with 2.10.0 going on) how would we cherry-pick or decide what commits go in the 2.10 branch?
Are we okay with this edge case and add a check point in our component release issue to verify the release branch has expected changes aimed for ongoing release?

@gaiksaya We need to get inputs from all teams participating in a release before we finalize this process.  Creating branch automatically from .x has its own advantages and dis-advantages based on the usage of .x branch by corresponding teams. Lets use this issue is to discuss, brainstorm and analyze the feasibility of automating the release branch creation process.

We can have on demand workflow that can be kicked off by a release manager after the code cut off date, the workflow will auto cut the release branch (a logic that can auto detect from <VERSION>.x to actual RELEASE_VERSION 2.x-2.12.0) for all the repos part of the input manifest. Along with creation of branch it should also update the release specific input manifests ref to use that new release branch and raise a PR to get it merged to main branch of the build repo, here is a sample manual PR raised which can be automated with the same workflow.
Thank you

The Jenkins job should have the following flow.

An input as manifests (a comma separated manifests for both OS and OSD), sourceBranch, taretBranch`.
Identify the repos from the release specific input manifest (as a fallback a release manager can use previous release manifest) coming from the above manifests parameter .
Git clone with a repo write access user git clone<EMAIL_ADDRESS>Check if the release branch exists.
Skip the repo if the branch exists.
If no branch, create a branch and push to repo.
Re-run the workflow when the new components (new plugins onboarded) added to the release input manifest.

Closed via https://github.com/opensearch-project/opensearch-build/pull/4520


Add support for image fields and multi-file media

Right now if you want a derivative to live on the Media, you can only use file fields.  With a small change we can add support for image fields, too.

Fixed with https://github.com/Islandora/islandora/pull/860

There was already an Action plugin for this.
Here.

I didn't see it because it's within islandora_image, a submodule that I didn't have enabled. My bad...
Unfortunately, the "Generate an Image Derivative for Media Attachment" option also only lets you select file fields.
It appears this PR hits the parent class, AbstractGenerateDerivativeMediaFile and thus applies to all multi-file media derivatives. I'll work on a fix, if anyone is willing to test?


[Feature Request] Use Enum field type in JSON type

Is your feature request related to a problem? Please describe.
I'd like to be able to do this (or a similar alternative solution):
enum TagType {
    One
    Two
    Three
}

type TestData {
    tag     TagType?
    eventId String?
}

model Test {
    id   String   @id @default(cuid())
    data TestData @json
}

fixed in 2.8.1


Fixes

Fixed a bug in remote inspect code causing panic.
Code now passes validation checks.
Unfortunately tests fail in spectacular way. At least they compile now.

Merged


Quotes in the step code implementation is treating the parameter as dynamic

Expected behavior
The <> should be used for dynamic parameters.
Actual behavior
In code if the annotation text @Step("Add \"product\" to basket") is being allowed and considered as dynamic parameter. However subsequent operations like refactoring are not working.
**Steps to replicate

Create a spec

Test all verifications
======================
* Add "product1" to basket

Test break on failure
---------------------
* Add "product1" to basket

Create an implementation

    @Step("Add \"product\" to basket")
    public void implementation13(Object arg0) {
        System.out.println(arg0);
    }

Refactoring does not complete successfully

Version
Gauge version: 0.6.1.nightly-2016-07-25

Plugins
-------
csharp (0.9.1.nightly-2016-07-25)
html-report (2.1.1.nightly-2016-07-20)
java (0.5.1.nightly-2016-07-25)
ruby (0.3.1.nightly-2016-07-25)

@Step("Add \"product\" to basket")

Not adding refactoring support for this format


master分支代码插入数据好像有点儿问题

groupMember表，以前老数据插入uid在前，gid在后，现在新数据插入gid在前，uid在后，后面执行根据key查询数据，新数据可以查询出来，老数据查询不出来了
写入的时候，如何不改变写入时key的bson的顺序？

Background
This is an expected breaking change that happened in im.turms.server.common.storage.mongo.entity.MongoEntityFactory#parse in 2022-11, which ensures the document field order is in alphabetical order to ensure serializing document fields in a consistent order.
Solution
It's quite easy to migrate data to follow the new schema.
Run the following aggregation:
db.orders.aggregate([
  // Stage 1: Change the order of fields in "_id"
  {
    $set:
    {
      "_id": {
        "gid": "$_id.uid",
        "uid": "$_id.gid"
    }
  },
  // Stage 2: Copy data to a new collection
  {
    $out:
    {
      db: 'turms_dev', // change to your database
      coll: 'groupMember_v2'
    }
  }
])

And then drop your groupMember collection, and rename groupMember_v2 to groupMember.
When you start turms-service, it will create indexes for groupMembers automatically.
btw, Turms is stable currently, and only status codes will have breaking changes (e.g. names change).


[UI] Adopt fundamental styles - view Debugger

Target

[ ] Adopt the fundamental styles in Debugger view

Use https://github.com/dirigiblelabs/ide-next as reference

Issue cloned to https://github.com/eclipse/dirigible/issues/1524


Upgrade legacy learners that paid and are erolled, have exam attempt

What are the relevant tickets?
Fix https://github.com/mitodl/mitxonline/issues/960
What's this PR do?
This is a management command that take in a file and upgrades learners in their current enrollment
How should this be manually tested?
Create a csv file that has data of a learner in your local mitxonline environment, that is auditing a a current course.
In the csv file add a record: <learner_email>, <course_run_key>
Run the command ./manage.py upgrade_eligible_users input_file.csv
The enrollment should get upgrades to 'verified'.

Codecov Report

Merging #1059 (98db08c) into main (b7528b3) will decrease coverage by 1.59%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1059      +/-   ##
==========================================
- Coverage   85.95%   84.36%   -1.60%
==========================================
  Files         284      143     -141
  Lines       10816     6989    -3827
  Branches     1168     1168
==========================================
- Hits         9297     5896    -3401
+ Misses       1314      885     -429
- Partials      205      208       +3

Impacted Files
Coverage Δ

ecommerce/models.py
88.79% <0.00%> (-1.18%)
:arrow_down:

ecommerce/views/v0/__init__.py
89.65% <0.00%> (-0.87%)
:arrow_down:

...src/containers/pages/register/RegisterEmailPage.js

.../public/src/containers/pages/DashboardPage_test.js

...c/containers/pages/register/RegisterDetailsPage.js

...tainers/pages/settings/AccountSettingsPage_test.js

...d/public/src/components/forms/ResetPasswordForm.js

...ainers/pages/login/LoginForgotPasswordPage_test.js

frontend/public/src/contextDefinitions.js

...d/public/src/components/forms/RegisterEmailForm.js

... and 133 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@jkachel I added a check for edx_request_success to log out failed enrollments. Thanks


GTA.Native.?A0xe506951e

3/7/2016 5:44:28 PM:Unable to cast native value to object of type 'GTA.VehicleColor'    at GTA.Native.?A0xe506951e.ObjectFromNative(Type type, UInt64* value)
   at GTA.Native.OutputArgument.GetResult[T]()
   at SinglePlayerApartment.INMNative.SPAVehicle.get_SecondaryColor()
   at SinglePlayerApartment.INMNative.SPAVehicle.set_PrimaryColor(VehicleColor Value)
   at SinglePlayerApartment.Mechanic2.SetModKit(SPAVehicle _Vehicle, String VehicleCfgFile)
   at SinglePlayerApartment.Mechanic2.Franklin_SendVehicle(String SelectedItem_Car, String VehicleModel, String VehicleHash, UIMenuItem selectedItem, UIMenu sender)
   at SinglePlayerApartment.Mechanic.CategoryItemSelectHandler(UIMenu sender, UIMenuItem selectedItem, Int32 index)

I this happened when I try to get secondary color or get primary color of a vehicle

Solved by changing Type VehicleColor to Integer

For future reference Enums are fully supported in the v3 build. so once that releases Native.Function.Call(blah) will work without any errors


Part 1 of a fix for #1712 - ModelBinding and validation should not use

reflection.
This change moves the logic to process BindingBehaviorAttribute into the
model metadata system, and exposes it via that CanBeBound and IsRequired
properties.
This removes the need in the MutableObjectModelBinder to reflect over
properties and look at for this attribute.

/cc @dougbu

Hitting the pause button here. Making validation respect our ModelMetadata.IsRequired property might cause some trouble. Will have a discussion and come up with another PR.


ARROW-4251: [C++][Release] Add option to set ARROW_BOOST_VENDORED environment variable in verify-release-candidate.sh

I'm taking this for a spin on 0.12.1 RC0 on Ubuntu 14.04 (where the system boost does not work -- see ARROW-4868)

This works for me on Ubuntu 14.04, except that I hit ARROW-4250
109: [ RUN      ] TestProjector.TestExtendedMath
109: /tmp/arrow-0.12.1.cZzB4/apache-arrow-0.12.1/cpp/src/gandiva/tests/projector_test.cc:358: Failure
109: Value of: (expected_cbrt)->Equals(outputs.at(0))
109:   Actual: false
109: Expected: true
109: expected array: [
109:   2.51984,
109:   2.15443,
109:   -2.41014,
109:   2.02469
109: ] actual array: [
109:   2.51984,
109:   2.15443,
109:   -2.41014,
109:   2.02469
109: ]

+1


feat(providers): support deepseek api

Add support for Deepseek-Coder-v2-0724 model.

I apologize for not noticing the earlier pull request. This new pull request is unnecessary.


rustic-cargo-new has a little problem

Issue
The funcion rustic-cargo-new in “rustic-cargo.el” has a logical problem.
When I execute the command cargo new --lib mylib in terminal, cargo will automatically create a directory named "mylib" for me, even if the directory does not exist before. But when I execute the rustic-cargo-new function under emacs, emacs will let me choose a directory, and it must be an existing directory, otherwise it will prompt me "match required".

I checked the source code of the function rustic-cargo-new and found that (interactive "DProject path: ") is used in it, and this D parameter is the cause of the problem. I'm using doomemacs, I don't know if the same is true for other emacs.
Expected behaviour
rustic-cargo-new should create a lib even the directory does not exist before.
Notes
I changed (interactive "DProject path: ") to (interactive "sProject path: ") and then manually entered the path of the directory, the function achieved my purpose, and I can create a new library just like in the terminal

When you use rustic-cargo-new, you can interactively select the existing directory and then type in the new name that you are looking for (appending it with the directory which you have chosen). I tested the workflow and can confirm that I'm able to create both library as well as binary package. Although, I'm not using doomemacs.

I am facing the same issue, with Doom Emacs. I think another possible fix is to mimic how functions like find-file are implemented, i.e. with find-file-read-args.


typo: Navie Query Engine in README title

It should be 'naive' 😁.

oh, many thanks for pointing it out! ♥


Bosh dns core dns

We implemented BOSH-compatible hostname aliases

We use a second DNS server
k8s headless services are created based on the alias configuration
The old headless service names are resolved by the second DNS server.

All these features are only enabled if the bosh dns addon is configured inside the manifest.
It can be tested using docs/examples/bosh-deployment/boshdeployment-with-bosh-dns.yaml.
It's also working with the SUSE cloudfoundry v3-release after changing the file scripts/scf/bazel-scf/deploy/helm/scf/assets/operations/addons.yaml

Remove

- type: remove
  path: /addons/name=bosh-dns-aliases

Add*

- type: replace
  path: /addons/name=bosh-dns-aliases/jobs/name=bosh-dns-aliases/properties/aliases/domain=nats?
  value:
    domain: nats.service.cf.internal
    targets:
      - deployment: cf
        domain: bosh
        instance_group: nats
        network: default
        query: '*'
- type: replace
  path: /addons/name=bosh-dns-aliases/jobs/name=bosh-dns-aliases/properties/aliases/domain=eirini?
  value:
    domain: eirini.service.cf.internal
    targets:
      - deployment: cf
        domain: bosh
        instance_group: eirini
        network: default
        query: '*'

Thanks @kramerul  - this is great. 👍
We'll try to get this in as soon as possible.

fyi: I think there are some review comments open and at least one integration test is still missing. Tomorrow is public holiday in Germany, so we will pick this up on Monday.

We added an integration test.


[Snyk] Upgrade pdfkit from 0.11.0 to 0.13.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade pdfkit from 0.11.0 to 0.13.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 5 versions ahead of your current version.
The recommended version was released 2 years ago, on 2021-10-24.

The recommended version fixes:

Severity
Issue
PriorityScore (*)
Exploit Maturity

Use of Weak Hash SNYK-JS-CRYPTOJS-6028119
644/1000  Why? Has a fix available, CVSS 8.6
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Release notes

Package name: pdfkit

0.13.0 - 2021-10-24
Add tiling pattern support

0.12.3 - 2021-08-01v0.12.3

0.12.2 - 2021-08-01

0.12.1 - 2021-04-10
Update crypto-js to v3.3 (fix security issue)
Update fontkit to 1.8.1

0.12.0 - 2021-04-04
Add support for Embedded Files and File Attachment Annotations
Accessibility support
Replace integration tests by visual regression tests
Fix access permissions in PDF version 1.7ext3
Fix Buffer() is deprecation warning
Add forms.md to generate documentation files
Fix "@" in FontName

0.11.0 - 2019-12-10
Fix infinite loop when an individual character is bigger than the width of the text.
Fix infinite loop when text is positioned after page right margin
Allow links in continued text to be stopped by setting link to null
Add support to interlaced PNG files
Do not emit _interopDefault helper in commonjs build
Fix gradient with multiple stops (#1045)
Set link annotation flag to print by default
Add support for AcroForms
Drop support for (uncommon) cid less fonts on standalone build (reduces bundle size)

    from pdfkit GitHub release notes

Commit messages

Package name: pdfkit

3525247 v0.13.0
9098c41 Ignore browserify bundle file
4c5e73a Tiling pattern support (#526) (#1311)
fd72a78 Fix syntax highlighting on pdfkit.org (#1308)
55ed6d5 Add missing dependencies to webpack example
29216b7 Fix and cleanup webpack example
e9c7d9e v0.12.3
cc6331b Add examples folder to .npmignore
62ed253 Remove src folder from .gitignore
5ff4eae fix ignore crypto in standalone build
a41f338 Refactor on equality check function (#1280)
b5b0ac1 Revert "github actions - add node.js 16"
7b96ca6 github actions - add node.js 16
529acf4 fix tests
6567035 Add webpack example
f7947c8 Upgrade crypto-js to 4.0.0
8f70c33 Remove package-lock.json
5fbdfd6 Reorganize and cleanup examples
dd6569e Add interactive browser demo files to publish website script
4898dcb update ignored files in npm
a4c5756 update lock files
aa8c65d add 0.12.1 from npm release
4700537 Fix for PDF accessibility check. (#1265)
131df9e Add option to define AcroForm fontSize. Fixes #1088

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Checkmarx One – Scan Summary & Details – 90d26ca6-2952-426c-a981-f15e0b02add8
Fixed Issues

Severity
Issue
Source File / Package

CVE-2023-46233
Npm-crypto-js-3.3.0


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:16: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:22: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:41: missing_license_family: The recipe is missing the about/license_family key.
WARNING: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
ERROR: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:41: missing_documentation: The recipe is missing a doc_url or doc_source_url
ERROR: /tmp/abs_cdldlo1inr/clone/recipe/meta.yaml:41: missing_dev_url: The recipe is missing a dev_url
Errors were found


Add ability to run and monitor workflow to UI

Task to do
Add ability to run and monitor workflow to UI
Reason
Allows users to start workflows and see how they're progressing
Result
Able to start and monitor workflows

Closing as duplicate


feat(plugins): ai-prompt-guard-plugin

Summary
This commit offers another plugin that extends the functionality of "AI Proxy" in #12207.
It compares the user's llm/v1/chat or llm/v1/completions request against a series of regular expressions, in two config arrays:

Allow
Deny

If the request matches any regex pattern in deny, the caller is 400'd.
If any allow is specified, by the request matches none of them, the caller is also 400'd.
Engineering design document is available for this feature, but it is quite simple. Comprehensive tests supplied.
This reason for its development, is that many of our users would like to block specific prompts, words, phrases, or otherwise more tightly control how an AI / LLM model is used, if being called via Kong, and this applies especially with the AI Proxy plugin that will simplify this process.
Checklist

[x] The Pull Request has tests
[x] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - docs being discussed internally, as part of AI-Proxy plugin in #12207

@locao do we have another gateway reviewer for this PR?

@flrgh this is on me, reviewing it now.


Leverage the Python "future" Module To Support More Use Cases

MacOS	provides Python 3.8. Using the future module we get support back to most of Python 3.7.
Demonstrate "tox" and "pytest" to help validate that multiple versions of Python can run this code and provide a structure for additional tests to be written.

The "future" imports were injected with:
FILES=`grep -r 'list\[.*\]' pyedgeconnect 2> /dev/null | cut -d':' -f1 | uniq`
for f in $FILES; do sed -i '5s/^/from __future__ import annotations\n/' $f; done

I think you've pulled in at least the "future" stuff in your development branch - my apologies for getting this posted so late.

Thanks for the suggestions Tim, as you noted majority of this was incorporated in the 0.15.1 release. Appreciate the conversation we had and your ideas around improvements! Added some of the intial tox testing in the latest 0.15.2 release now as well

@zachcamara-hpe no worries - excited to see the new stuff!


Either convert .rst files to markdown, or add an rst linting script to CI

Silly rst markup errors aren't being caught by the CI (e.g. https://github.com/PyCQA/flake8-pyi/pull/72 fixes a bunch that look like they've been there for a while).
We should probably either convert these files to markdown, or add linting script like CPython's rstlint.py to the CI.

I think we should just use markdown, because we are more familiar with its syntax and won't make silly errors.

I think we should just use markdown, because we are more familiar with its syntax and won't make silly errors.

I agree.

I fixed a bunch more in #117, I'm completely unfamiliar with rst but the support in PyCharm (syntax highlighting and preview window) made it extremely easy to work with.

I fixed a bunch more in #117, I'm completely unfamiliar with rst but the support in PyCharm (syntax highlighting and preview window) made it extremely easy to work with.

Thank you very much!


 VCF objects are meant to be directly in-memory representations of VCF files anyway, so why fight it? I'd estimate that it would take a few thousand lines of code to validate a VCF experiment properly, and that's not worth the effort if we can push responsibility to an existing format.

Closed by #28.


dm-rails should map empty Strings to nil, for Integer properties that allow_nil

I discovered an incompatibility in how dm-rails consumes empty Strings, from select/option form fields. When a select form field is left unselected, the submitted value is always an empty String. ActiveRecord would treat empty Strings as nil values, when populating attributes. dm-rails should not map all empty Strings to nil, but only for Integer properties that allows nil.

@postmodern I'm assuming this is still an issue. If it's not something we want to solve on dm-core, do you think I should add your patch to dm-rails?


Ignore non-left mouse clicks

Right and middle clicks shouldn't be treated as taps (when using a desktop browser)
This should resolve issue #46 (thx to @giulianoriccio)

Thanks!


Fix this in swig.compile()

The value of this might be modified when called in other situations.
All other references to this are guarded with self in all other functions.
In particular, this should fix Travis errors in jstransformers/jstransformer-swig#2: https://travis-ci.org/jstransformers/jstransformer-swig/builds/51301563

:+1:

Ping.

@paularmstrong ?


Creepers explode bigger

Maybe have a long fuse too

It lags out the game a lot more than vanilla amplified explosions

This is only at huge multiplier. Use big ones at your own risk ;)


Share current view as is

Currently user can share filter but not content. It's impossible to see same content on different devices. We need to introduce possibility to share current view for teammates.

#1005


karyon1 healthcheck plugin

karyon1 healthcheck plugin that can be used with  karyon2-admin framework

NetflixOSS » karyon » karyon-pull-requests #37 FAILURE
Looks like there's a problem with this pull request

NetflixOSS » karyon » karyon-pull-requests #38 SUCCESS
This pull request looks good

NetflixOSS » karyon » karyon-pull-requests #39 SUCCESS
This pull request looks good


Cant connect

Hi folks,
I'm having this problem right here...
"SUMMARY
PARAMETERS

/rosdistro: noetic
/rosversion: 1.15.14
/vicon/datastream_hostport: <IP_ADDRESS>:801
/vicon/stream_mode: ClientPull
/vicon/tf_ref_frame_id: /vicon/world

NODES
/
vicon (vicon_bridge/vicon_bridge)
auto-starting new master
process[master]: started with pid [29224]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 7e1806ca-d6b0-11ec-bfbd-9f4f946023f3
process[rosout-1]: started with pid [29241]
started core service [/rosout]
process[vicon-2]: started with pid [29244]
[ INFO] [1652881406.549681766]: Connecting to Vicon DataStream SDK at <IP_ADDRESS>:801 ...
[ INFO] [1652881406.551587664]: .
[ INFO] [1652881407.552179954]: .
[ INFO] [1652881408.553358608]: .
[ INFO] [1652881409.554279805]: .
[ INFO] [1652881410.555420396]: .
[ INFO] [1652881411.556637230]: .
[ INFO] [1652881412.557781509]: .
[ INFO] [1652881413.558694132]: .
[ INFO] [1652881414.559790780]: .
I'm connected with my Ubuntu Laptop to the Windows PC via Ethernet Cable."
Any suggestions?

Hey! I'm assuming you found a fix for this since the time you posted this issue, but what worked for me was using netstat -aon and looking for 192.168.10 local addresses, and trying out each of the foreign addresses that were linked to them as the datastream_hostport. One of those worked for me.


*Id.*s with the same pincite

*Id.*s are using pincites even if the previous citation cited to the same page.
If an Id. has the same pincite as the prior cite, it should not render the pincite.

Fixed in commit 8862133.


where is the settings file?

where is the config.cson referenced in the readme?

The config.cson, like all other Atom configuration files, is stored in the ~/.atom directory. You can also get to it by opening the Command Palette and searching for "Open Your Config".


⚠ Turnos 24x7 has degraded performance

In 7d6d059, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 941 ms

Resolved: Turnos 24x7 performance has improved in 0f29468.


组件[Wheel] 加个滚动条，滚轮有问题，结果上下乱跳

Description
我这滚轮有问题，结果上下乱跳
Suggested solution
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

请提供一下复现以及操作步骤。


Copying Mobject

Description of bug / unexpected behavior

Copying a mobject fails when trying to graph a ParametricFunction.
Expected behavior

The copying is successful and the ParametricFunction is successfully graphed.
How to reproduce the issue

Code for reproducing the problem (inside
Class RandomlyObscureScene(Scene):
     def func(self, t):
        x = 12*t-6
        y = np.sin(x)
        return x*LEFT+y*UP

    def construct(self):
        funk = ParametricFunction(function=self.func,x_min=-3,x_max=3)
        self.play(ShowCreation(funk))
        self.wait()

Additional media files

Images/GIFs

Logs
Terminal output

https://pastebin.com/FVZTMRZT

System specifications
System Details

OS Win 10
RAM: 12 GB
Python version (python/py/python3 --version): Python 3.9
Installed modules (provide output from pip list):

Package           Version
----------------- -------
cairocffi         1.2.0
cffi              1.14.3
colorama          0.4.4
colour            0.1.5
commonmark        0.9.1
grpcio            1.33.2
grpcio-tools      1.33.2
manimce           0.1.0
numpy             1.19.3
pangocairocffi    0.3.2
pangocffi         0.6.0
pathtools         0.1.2
Pillow            8.0.1
pip               20.2.4
progressbar       2.5
protobuf          3.13.0
pycairo           1.20.0
pycparser         2.20
pydub             0.24.1
Pygments          2.7.2
rich              9.2.0
scipy             1.5.4
setuptools        50.3.2
six               1.15.0
tqdm              4.51.0
typing-extensions <IP_ADDRESS>
watchdog          0.10.3

LaTeX details

LaTeX distribution (e.g. TeX Live 2020): TeX Live 2020
Installed LaTeX packages: manim-latex

FFMPEG
Output of ffmpeg -version:
ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers
built with gcc 10.2.1 (GCC) 20200726
configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libsrt --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvmaf --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libgsm --enable-librav1e --disable-w32threads --enable-libmfx --enable-ffnvcodec --enable-cuda-llvm --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
libavutil      56. 51.100 / 56. 51.100
libavcodec     58. 91.100 / 58. 91.100
libavformat    58. 45.100 / 58. 45.100
libavdevice    58. 10.100 / 58. 10.100
libavfilter     7. 85.100 /  7. 85.100
libswscale      5.  7.100 /  5.  7.100
libswresample   3.  7.100 /  3.  7.100
libpostproc    55.  7.100 / 55.  7.100

Additional comments
This is related to Mobject.copy() and possibly the lack of a deepcopy magic method.

Hi, thanks so much for the report.
I don't see where/how you are trying to copy something. Am i Missing something?
On another hand, could you please try to run the same scene with --disable_caching?

No problem! I am not intrinsically trying to copy anything, but I combed through the traceback and found the error to be with the Mobject.copy() method. I tried running the same scene with the flag --disable_caching and the result was not different. Thank you for your help!

Ah I figured something out, changing func to a staticmethod without the self parameter fixes the issue. This is very interesting and I'll look into it more.

@protonlaser91 thanks for reporting this.
Mobject defines the copy() method, which executes the same code as in your stacktrace: copy.deepcopy(self). There are other parts of the codebase that use this method, so it seems like this is not necessarily the culprit.
Since your func does not require access to self I suggest defining it outside of the class (not even as a static method of the class). Please let us know if that solves your problem.

This does! Thank you.


setViewPager error while working with viewPager2

setViewPager accept a viewPager but when you are working with viewPager2 you can't pass the view

setViewPager accepts a viewPager2, it works for me. You should choose CircleIndicator3.

@talatkuyuk i'll check it out


refactor: move cb(handleService/handlePod) as method of ambient index

Please provide a description of this PR:
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[x] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

@hzxuzhonghu: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test release-notes

unit-tests-arm64_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test release-notes

unit-tests-arm64_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test unit-tests-arm64

integ-pilot_istio
dab51fb7f023acf863547164fc32c3f4cd74d029
link
true
/test integ-pilot

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Pre-Compiled Binaries For Hazel

There are no pre-compiled binaries for hazel, and most regular users(not programmers) get frustrated if it's not there.
Solution
Putting pre-compiled binaries of Hazel in hazelengine.com

I don't see a "regular" user using a game engine...

Never seen artist's (like Harry Nesbitt and many others) make a game using a game engine before?

Tbh I agree. There should be pre-compiled binaries.


Is caching necessary?

Hello I’m new to all this so excuse me if I’m no expert. I just switched from 1.9 version to the latest and now whenever I start the screensaver the screen just turns all black. I tried to fix it and I think is because with previous version I wouldn’t cache the videos. So my question is: is it possible to have the screensaver working without downloading or caching videos on the computer? (Obviously having an internet connection working)

Hi @amedeocalcio
Users who had that particular mix of settings seem to be experiencing issues, yes. I would recommend deleting the settings and start fresh. Location of files here at the bottom, you need to reboot after deleting though (plist are cached by macOS) : https://aerialscreensaver.github.io/installation.html
Answering your question, is caching "necessary" ? Nothing per se is really necessary. But streaming is at the root of a lot of issues in Aerial that I want to get rid of. That's the reason why I've hidden it (although apparently you can still bend Aerial to stream, against my best efforts !).
There are a few reasons I made that change, the first one is, Apple servers are not configured correctly for streaming. The Apple TV's screensaver uses the exact logic I implemented in 2.0, which is cache, and rotate the cache periodically. This avoids a lot of failed playback issues, inability to resume etc. There's also a question of being mindful of resources that aren't ours. Apple seems to tolerate Aerial. If everyone streamed all the time, they may take a different eye to it, either by obfuscating their servers or using some other level.
So yes, I highly recommend that you use a rotating cache after resetting your settings and I will not bring back the streaming all the time option.

That makes sense, you know I just considered what was best for my Mac, but with all these things in play I can understand why you’re doing what you’re doing. Thanks for the quick and exhaustive answer man! Keep up the good work.

Thanks for your understanding !

Since you answered, will it be possible to have back the narrow button option, the one for changing video while playing?

Since you answered, will it be possible to have back the narrow button option, the one for changing video while playing?

Hmm ? Which button are you referring to ?

My bad, I typed it wrongly. I'm referring to the right arrow key for skipping the video

Since you answered, will it be possible to have back the narrow button option, the one for changing video while playing?

Hmm ? Which button are you referring to ?

It's still there and enabled by default, but it no longer works on Catalina and Big Sur because of sandboxing restrictions. It still works on 10.14 and below, but I have 0 control over it, it's a restriction imposed by Apple.


Allow shipshape to run on a single file

Right now, the CLI assumes it runs on a directory. Also allow a single file. Amin, do you need to operate on dirty buffers? That will be more difficult to support.

Fixed.


[RFC] Change on the syntax for listening providers

Hello!
This issue is an open discussion for a potential change on how to consume/combine providers.
The goal of these changes are:

offer a uniformized way to listen to providers (no-longer have ref.watch vs useProvider vs watch)
add an equivalent to ProviderListener that works inside providers too
revamp ProviderListener not to involve nesting
support a ConsumerStatefulWidget
support useProvider(myProvider.select((user) => user.name)) in all the places that may want to listen to a provider

The problem
At the moment, there are many similar but slightly different syntax for listening to a provider:

providers wanting to listen to another provider may use ref.watch(myProvider):final provider = Provider((ref) {
  final value = ref.watch(anotherProvider);
});

HookWidget may use useProvider(myProvider):class Example extends HookWidget {
  @override
  Widget build(BuildContext context) {
    final value = useProvider(anotherProvider);

  }
}

ConsumerWidget & Consumer may use watch(myProvider):class Example extends ConsumerWidget {
  @override
  Widget build(BuildContext context, ScopedReader watch) {
    final value = watch(anotherProvider);
  }
}
...
Consumer(
  builder: (context, watch, child) {
    final value = watch(anotherProvider);
  }
)

all widgets can use ProviderListener but not providersclass Example extends StatelessWidget {
@override
Widget build(BuildContext context) {
  return ProviderListener<Something>(
    provider: anotherProvider,
    onChange: (context, value) {}
  );
}
}

This works fine but is slightly confusing. While in practice, there's only one solution on how to listen to a provider depending on where you are, the fact that the syntax isn't the same everywhere confuses newcomers.
On top of that, due to how ConsumerWidget/Consumer works, it is inconvenient to add new ways to listen to providers (such as a simplification of ProviderListener that does not involve nesting) because that would require adding parameters to the build method.
This also means that it is impossible to listen to providers inside StatefulWidget, as it is impossible to add extra parameters to State.build. This requires developers to use Consumer, which decreases readability.
Proposal
This proposal is about fusing all of these methods for listening providers into two static functions:

watch, the equivalent of ref.watch/useProvider/...
listen, the equivalent of ProviderListener

These two functions would work in all providers and inside ConsumerWidget, Consumer, and two new additions:

ConsumerHookWidget
ConsumerStatefulWidget

Long story short, here is how both functions would look like in practice:
final a = Provider<A>(...);

final b = Provider((ref) {
  A value = watch(a);
  listen<A>(a, (value) {
  });
});

Consumer(
  builder: (context) {
    A value = watch(a);
    listen<A>(a, (value) {
    });
  },
);

class StatelessExample extends ConsumerWidget {
  @override
  Widget build(BuildContext context) {
    A value = watch(a);
    listen<A>(a, (value) {
    });

  }
}

class HooksExample extends ConsumerHookWidget {
  @override
  Widget build(BuildContext context) {
    A value = watch(a);
    listen<A>(a, (value) {
    });

  }
}

class StatefulExample extends ConsumerStatefulWidget {
   @override
  _StatefulExampleState createState() => _StatefulExampleState();
}

class _StatefulExampleState extends State<StatefulExample> {
  @override
  Widget build(BuildContext context) {
    A value = watch(a);
    listen<A>(a, (value) {
    });

  }
}

This change would involve:

deprecating useProvider in favor of ConsumerHookWidget + watch
deprecating ProviderListener in favor of listen
deprecating ref.watch in favor of watch
removing the extra parameter of ConsumerWidget.build

This change would have no impact on <ref/context>.read
The downside
The main issue with this change is, we lose some of the "compilation safety".
More specifically, there are two cases that currently purposefully do not compile but would now compile (and throw) after this change:

reading a ScopedProvider inside a non-scoped provider:
final scoped = ScopedProvider(...)

final provider = Provider((ref) {
  watch(scoped);
});

reading an .autoDispose provider inside a provider that is not marked with .autoDispose:
final autoDispose = Provider.autoDispose(...)

final provider = Provider((ref) {
  watch(autoDispose);
});

Since these would now throw exceptions instead of compilation errors, this would make refactoring more difficult.
The bright side is, there is an alternate solution for these: custom lint rules.
Instead of relying on the Dart compiler to have a compilation error, we could extend the Dart analyzer to add support for these scenarios.
This is a separate project on its own but is feasible.
Closing word
That's it~
What do you think of the proposed change, and what do you think about the downsides?
Feel free to comment or vote on this issue to express your opinion:

vote 🚀  if you want this change even without the analyzer plugin (the analyzer plugin would still come but after the release of such change)
vote 🎉 if you want this change, but only if we have the analyzer plugin (this would lock the release of such change until the analyzer plugin is ready)
for 👎  if you don't want this change at all
leave a comment for any other opinion

I overall like the proposal but I have a few concerns.

Would Consumer actually lose their child attribute as indicated here

or is it just a typo?

Although I like the syntax, I feel like in the case of Providers, ref.watch is actually clearer as it clearly indicates that it is the reference that is watching and will thus rebuild the provider whereas watch is a little obscure as to what actually watches a (in the example).

I don't agree with these changes mostly.
listen inside pods is unneeded imo. Because it's usage heavily related with context where navigation or showing snackbar-dialog etc. needed, which is not a normal case inside a pod. And nesting for ProviderListener is very okay because the functionality you get is totally worth.
I'm not sure about watch but I can easily say it makes ProviderReferences irrelevant from developer side, imagine having two different scope(I know it's unlikely but possible), watch function may confuse in that scenario.
Also I'm not fan of occupying generic names at top level namespace.
I can't say much about changes related to hook because I don't use it.
I think you are trying to over-simplify the riverpod. It's already pretty easy and versatile way to manage state, imo it's best so far. Yes, it may be hard to empathize with newcomers but what I like about you packages, you use everything in their proper place without breaking patterns, riverpod shouldn't go in that way.

Would Consumer actually lose their child attribute as indicated here or is it just a typo

Just a typo

listen inside pods is unneeded imo

It has been requested numerous times
The use-case is to perform an action on StateNotifier/ChangeNotifier when another provider updates, without destroying the provider state:
final provider = StateNotifierProvider((ref) {
  final notifier = MyNotifier();

  listen<Something>(anotherProvider, (value) {
    notifier.doSomething();
  });

  return notifier;
});

And nesting for ProviderListener is very okay because the functionality you get is totally worth.

listen inside pods is unneeded imo

It has been requested numerous times
The use-case is to perform an action on StateNotifier/ChangeNotifier when another provider updates, without destroying the provider state:
final provider = StateNotifierProvider((ref) {
  final notifier = MyNotifier();

  listen<Something>(anotherProvider, (value) {
    notifier.doSomething();
  });

  return notifier;
});

And nesting for ProviderListener is very okay because the functionality you get is totally worth.

If we can do the same without nested, why not?

I'm not sure about watch but I can easily say it makes ProviderReferences irrelevant from developer side, imagine having two different scope(I know it's unlikely but possible), watch function may confuse in that scenario.

Do you have an example?

Yes, it may be hard to empathize with newcomers but what I like about you packages, you use everything in their proper place without breaking patterns, riverpod shouldn't go in the other way.

What pattern would this break?

It has been requested numerous times

I agree with @rrousselGit here, I needed that feature a few days ago and still do.

I personally like as is 😊

Another question, would we still be able to do something like this ?
final a = Provider<A>(...);
final b = Provider((ref) {
  return MyClass(ref);
});
class MyClass {
  final ProviderReference ref;
  MyClass(this.ref) {
    final val = ref.watch(a);
    // Logic here
  }
}

Another question, would we still be able to do something like this?

No. That's a bad practice to begin with.
Even without this change, a linter would warn you to not do that
It decreases the readability of providers quite a bit. It's harder to see what can cause the provider to "rebuild"

Alright that's true, I agree. The new watch would then actually be better I do agree. Thought for a moment ref.read would be impacted but no. Sunday mornings 😅
LGTM then 👍🏼

Although I like the syntax, I feel like in the case of Providers, ref.watch is actually clearer as it clearly indicates that it is the reference that is watching and will thus rebuild the provider whereas watch is a little obscure as to what actually watches a (in the example).

I agree with this. I believe it's better than having a top level watch which might be confusing as well.

The use-case is to perform an action on StateNotifier/ChangeNotifier when another provider updates, without destroying the provider state:
final provider = StateNotifierProvider((ref) {
  final notifier = MyNotifier();

  listen<Something>(anotherProvider, (value) {
    notifier.doSomething();
  });

  return notifier;
});

Is it possible right now? If so, how?

Is it possible right now? If so, how?

It's not~
That would be a new feature.
Your best bet, for now, is to use ChangeNotifier.addListener / Stream.listen combined with ref.onDispose, and potentially a create a separate Provider to filter rebuilds

Do you have an example?
After my comment, I thought more about this, it's actually confused me a little. What I was considering, say we have a game/app inside your application but as I thought more about this, actually there is no problem.

What pattern would this break?
Top level functions without context(I mean the general meaning of the context as used in many prog lang, not only BuildContext or ProviderReference), that's an anti-pattern, but clearly there is a benefit here by using just watch and ProviderReference is still relevant in that case, which makes everything optional.

As long as I think about the proposal, it makes sense but meantime I'm confused, okay I'm neutral now 😄

Top level functions without context that's an anti-pattern

It's not really without a context.
You can think of it more as Kotlin's "this" parameter, where instead of:
Class((this) {
  this.doSomething();
});

you just do:
Class(() {
 doSomething();
});

The only difference is that it relies on a workaround to work

Out of curiosity what would that workaround be ?
I feel like even though the code would be more concise it might be less clear to newcomers what the effect of watch would be and why it would (/not) work in different cases. The fact that this method becomes accessible everywhere but actually doesn't work everywhere might be confusing.
A well written doc would be needed but I know for a fact that yours docs are always really well written so I'm not really worried 😊

This would rely on Zone parameters

I wouldn't like to see useProvider deprecated as it would prevent hook composition. I prefer to have consistency of code within a build method.
final tabController = useTabController(...);
final brand = useBrand();

...

BrandData useBrand() => useProvider(brandProvider);

I wouldn't like to see useProvider deprecated as it would prevent hook composition

watch would work inside hooks too

How are you planning to implement this change? Set the provider context before calling the callbacks?
I feel like this might be a dangerous move, but I have not thought about it enough yet 🤔

Also, I would not want the change just for the sake of changing or just because some function names do not look nice. If there is any comprimise connected to it, it does not feel worth it because we lose quality just for having more consistent function naming.

Things I like

With an AsyncValue I may want to build a widget for loading and error states but trigger a navigation event when data comes in. In that case I would have to have a ProviderListener in one place in the build tree and the Consumer or useProvider in another. I like that this syntax will put this code a little closer together instead of spread across the build tree.
I like that this eliminates the nesting of the ProviderListener
This will help with adoption for new people. Consistency of syntax is an improvement.
Thing I don't like
I make the mistake of mixing auto dispose providers with others all the time. It is nice that the compiler helps find those issues. The linter improvement would help, but is not a perfect solution.

I make the mistake of mixing auto dispose providers with others all the time. It is nice that the compiler helps find those issues. The linter improvement would help, but is not a perfect solution.

Why isn't the linter a perfect solution?
It would likely be more helpful than the compiler, because instead of a weird error message like "Cannot assign RootProvider to AutoDisposeProvider" we'd get a proper error message akin to "Cannot listen to a provider marked with autoDispose in a provider not marked with autoDispose"

How are you planning to implement this change? Set the provider context before calling the callbacks? (zone parameters would be one way, e.g. Zone.current[#_providerContext])

Yes this would be using the Zone. We can't just use a static variable because of FutureProvider/StreamProvider that may call "watch" after some delay.
The Zone fixes that

Feels like a hack all in all 🤔

I make the mistake of mixing auto dispose providers with others all the time. It is nice that the compiler helps find those issues. The linter improvement would help, but is not a perfect solution.

Why isn't the linter a perfect solution?
It would likely be more helpful than the compiler, because instead of a weird error message like "Cannot assign RootProvider to AutoDisposeProvider" we'd get a proper error message akin to "Cannot listen to a provider marked with autoDispose in a provider not marked with autoDispose"

Not everyone on my team checks the linter for warnings and errors unfortunately which is why it is not ideal. I know there are things I can do to force compile errors when the linter has an error, but I haven't set that up yet.

I like the Idea of ConsumerHookWidget

Unfortunately, not everyone checks the linter for warnings and errors which is why it is not ideal. I know there are things I can do to force compile errors when the linter has an error, but I haven't set that up yet.

I totally agree. I think the majority of developers, especially new flutter developers don't care that much about warnings.
For me, riverpod is compile safe and it should stay that way.

@smiLLe But people should be aware of warnings nonetheless. They exists for a reason.
In any case warnings can be turned into an error. Like the required parameter lint.

Putting aside ProviderListener the main syntax difference appears to be between the watch and useProvider functions.  Might it be that introducing ConsumerHookWidget and removing useProvider is enough, either with watch being a method of ConsumerWidget/ConsumerHookWidget or an additional param passed to the build method?
Following on, I'm not sure that I appreciate the necessity for passing ref to provider "create" functions, as opposed to just passing the watch function, so that we instead write:
final httpProvider = Provider((_) => HttpClient());

final apiProvider = Provider<ApiService>((watch) {
  final http = watch(httpProvider);
  return ApiService(http);
});

I seem to recall in earlier days using ref.read but believe that guidance became to always use ref.watch.  I think I recall seeing a comment recently that passing ref through to say a StateNotifier is frowned upon, preferring now to watch the provider values in the create function and pass them through to the notifier's constructor.  If that is true, then I'm not sure what need there is for passing in ref over watch.

I think using Lint is a must for any development... If the documentation makes it clear which Lint rules to use I don't see any problem, it would even be an improvement for the error message as Remi says.
Two things:

Would the "ref" param still make sense?

I think that we should also add "read" as static function.

Following on, I'm not sure that I appreciate the necessity for passing ref to provider "create" functions, as opposed to just passing the watch function, so that we instead write:

ref is necessary for things like onDispose,  read, maintainState and more. It's also a placeholder for adding features without requiring a breaking change.
For example there's an issue about having providers receive their previous value. This would likely be done with a ref.previousValue
We could also add a listen through ref:
final provider = Provider((ref) {
  ref.listen<A>(anotherProvider, (value) {

  });
});

read is no less useful after this change. The discussion you found is referring to bad practices that the linter would highlight

An alternate solution to this issue could be to update ConsumerWidget and HookWidget to receive a pseudo ref:
class Example extends ConsumerWidget {
  @override
  Widget build(BuildContext context, WidgetReference ref) {
    final value = ref.watch(provider.state);

    return RaisedButton(
      onPressed: () => ref.read(provider).increment();
    );
  }
}

The downside is:

this is more verbose
this doesn't allow a ConsumerStatefulWidget (unless we can somehow to it with a mixin on State?)

I think that we should also add "read" as static function.

This is sadly not feasible for read.

ref is necessary for things like onDispose, read, maintainState and more. It's also a placeholder for adding features without requiring a breaking change.

👍

An alternate solution to this issue could be to update ConsumerWidget and HookWidget to receive a pseudo ref:

I think I'd probably prefer to just use the watch function as-is, combined with a ConsumerHookWidget.  I could live without useProvider and apply watch everywhere.
Is there a strong need for ConsumerStatefulWidget that isn't addressed by ConsumerHookWidget or by adding a Consumer to the stateful widget's sub-tree?
As an aside, if one were to introduce a static watch method then we could nicely add extension methods to have myProvider.watch() and myProvider.read(context), which does feel a bit more natural and hides the static method implementation detail.

As an aside, if one were to introduce a static watch method then we could nicely add extension methods to have myProvider.watch() and myProvider.read(context), which does feel a bit more natural and hides the static method implementation detail.

That is not possible, because read is based on a different object depending on where we are.
Inside providers we do ref.read, and inside widgets we do context.read.
The objects being different means that we can't have a single provider.read.

Is there a strong need for ConsumerStatefulWidget that isn't addressed by ConsumerHookWidget or by adding a Consumer to the stateful widget's sub-tree?

No. The goal is to not require the dependency on hooks, nor require an unnecessary Consumer inside StatefulWidgets

That is not possible, because read is based on a different object depending on where we are. Inside providers we do ref.read, and inside widgets we do context.read.

Yeah, I was assuming context.read, which for me at least tends to be the primary use of read.

Yet another solution would be to subclass BuildContext to make it implement a common interface with ref
That would allow myProvider.read(context) vs myProvider.read(ref)

My opinion:
It seems like this proposal is actually two things:

A proposed syntax change unifying ref.watch, useProvider from hooks and watch from ConsumerWidget.
A proposal for new features:

add an equivalent to ProviderListener that works inside providers too
revamp ProviderListener not to involve nesting
support a ConsumerStatefulWidget
support useProvider(myProvider.select((user) => user.name)) in all the places that may want to listen to a provider
support ConsumerHookWidget

I think most developers are in support of all the new features
The most conflict is around the syntax change for watching
I agree that a unified syntax for watching is nice, but that it doesn't feel right given that there wouldn't be a uniform way to read a provider, to me it makes sense for the watch to be coming from the ref. A watch parameter in the build of ConsumerHookWidget would make the useProvider mostly obsolete except for composing hooks, which would unify much of the syntax. (Only having watch / ref.watch). And if you did like you mentioned and give something like a ref to the ConsumerWidgets then you would unify it by only having ref.watch.
My questions are:
Can we have the new features without the new syntax, or is it not feasible?
What features would not be feasible without the new syntax?

Can we have the new features without the new syntax, or is it not feasible?
Which features would not be feasible without the new syntax?

We can likely have those features in one way or another
As I mentioned before, it is entirely feasible to add a ref parameter to ConsumerWidget.build  (and somehow use mixins for StatefulWidgets)
We could then have:
Widget build(BuildContext context, WidgetsReference ref) {
  ref.watch(myprovider);
  ref.read(myprovider);
  ref.listen<A>(myprovider, (value) {});
}

This could be a solution. My worry would be:
"Do people care about listen enough so that it is worth to have ref.watch instead of watch?"

Is it strictly necessary to pass watch or ref through to the Consumer*Widget build method?  Could it not be a method of the widget?  That way the developer decides whether to use watch or ref.

Widgets are immutable
A method on a widget cannot do anything

I really like this approach of ref as ConsumerWidget build parameter. Its a very nice solution. But in this approach how we use Hooks? Some useProviderRef?
I dont know if people use a lot of listens but with this we have all functionallity accesible and it's clear from where watch function comes.

This could be a solution. My worry would be:
"Do people care about listen enough so that it is worth to have ref.watch instead of watch?"

I think changing watch to ref.watch is a much preferred change than making watch global. And it still accomplishes unifying the syntax to avoid confusion for beginners.
Personally my vote on order of features would be:

Change the watch parameter to a ref, or subclass BuildContext as ProviderBuildContext and only have the ProviderBuildContext parameter. (i.e. Widget build(BuildContext context, WidgetsReference ref); or Widget build(ProviderBuildContext context);)
Create the ConsumerStatefulWidget and ConsumerHookWidget
Add listen functionality
Update the .select functionality to work in all contexts
Update ProviderListener to not involve nesting
Add linter for enforcing best practices

After the new features, ask the community again if they would like the watch to be global. (I don't necessarily like this idea). If the goal is to unify the syntax then ref.watch seems like the best option to me, especially since it mirrors the ref.read and ref.listen syntax.

But in this approach how we use Hooks? Some useProviderRef?
@ldasilva-net
That is why we would have a ConsumerHookWidget. But I think hook functions for the same purpose could be made accessible like you suggested.

This could be a solution. My worry would be:
"Do people care about listen enough so that it is worth to have ref.watch instead of watch?"

Would using ref in this way still have the two downsides of compilation safety? If so, I don't care enough to have ref.watch instead of watch.

Would using ref in this way still have the two downsides of compilation safety? If so, I don't care enough to have ref.watch instead of watch.

No, as I understand it ref.watch would be essentially the same as watch is currently in a ConsumerWidget. i.e. No downsides of the proposal at the top of this issue, except adding the ref..

Indeed, ref.watch would be compile safe.
The downside is, we wouldn't have a ConsumerStatefulWidget

An alternate solution to this issue could be to update ConsumerWidget and HookWidget to receive a pseudo ref:
The downside is:

this is more verbose
this doesn't allow a ConsumerStatefulWidget (unless we can somehow to it with a mixin on State?)

@rrousselGit
In your previous comment you mentioned that there might be a way to do it with a mixin on State? Or is the ConsumerStatefulWidget not at all possible with this approach? As @scopendo mentioned most developers can workaround not having a ConsumerStatefulWidget by using Consumer in their build method, or separating out that part into a separate widget.

I would type ref. all.... day..... long..... if it means we could get type safety back. As to the loss of ConsumerStatefulWidget I don't personally need it because I use flutter hooks. I realize others need it, so if there was a way to accomplish it with a mixin that would be a win win.

This is interesting
@rrousselGit when will this change be applied to river_pod?

This is interesting
@rrousselGit when will this change be applied to river_pod?

It'll take a bit of time. I need to make another RFC with one of the suggested alternative. It wouldn't be fair to not evaluable all possibilities, especially considering the opinions on this one are mixed.

It'll take a bit of time. I need to make another RFC with one of the suggested alternative. It wouldn't be fair to not evaluable all possibilities, especially considering the opinions on this one are mixed.

Maybe slight of topic, but when watch a provider, the returned value is depended on which type of provider we are watching, and i was wondering if it would make sense to make a more uniform API for getting a value from watch?
E.g. for Provider we get the value (Object) directly, for StateProvider we have to access it through the .state getter, for FutureProvider or StreamProvider we receive an AsyncValue object.
I understand the point of AsyncValue as means to listen for various state changes, i just wonder if this API could become more uniform in some way..
I noticed this when i was trying to combine, a set of providers using a provider and get the result back as values. I had to check for various provider types to get the correct value back.
I'm not really sure how such a solution would look like, and maybe being specific here makes more sense, but making a API more uniform is always nice, and one could perhaps simplify the code in some cases.
The problem now i guess is ChangeNotifier which doesn't have a standard way to get a state, but perhaps Riverpod could consider to drop support for it..?
BTW perhaps, you could add an optional state parameter to the watch method, to only trigger when E.g. data is ready for AsyncData?

Maybe slight of topic, but when watch a provider, the returned value is depended on which type of provider we are watching, and i was wondering if it would make sense to make a more uniform API for getting a value from watch?
E.g. for Provider we get the value (Object) directly, for StateProvider we have to access it through the .state getter, for FutureProvider or StreamProvider we receive an AsyncValue object.
I understand the point of AsyncValue as means to listen for various state changes, i just wonder if this API could become more uniform in some way..
I noticed this when i was trying to combine, a set of providers using a provider and get the result back as values. I had to check for various provider types to get the correct value back.
I'm not really sure how such a solution would look like, and maybe being specific here makes more sense, but making a API more uniform is always nice, and one could perhaps simplify the code in some cases.
The problem now i guess is ChangeNotifier which doesn't have a standard way to get a state, but perhaps Riverpod could consider to drop support for it..?
BTW perhaps, you could add an optional state parameter to the watch method, to only trigger when E.g. data is ready for AsyncData?

I'm just coming to riverpod and really architecture besides built in state. i agree that it's a bit confusing to have so many different ways but it feels like the cons of switching outweight the pros
The hooks example seems so nice and to have it consistent with the rest of hooks seems like an asset.
Plus it feels like we are adding boilerplate/complexity in the hooks example... even if only a very little.

I'm just coming to riverpod and really architecture besides built in state. i agree that it's a bit confusing to have so many different ways but it feels like the cons of switching outweight the pros
The hooks example seems so nice and to have it consistent with the rest of hooks seems like an asset.
Plus it feels like we are adding boilerplate/complexity in the hooks example... even if only a very little.

Regarding the main RFC issue:
Having ref.watch makes sense to me if we can maintain compile safety.
I'm all for keeping it minimal, so i would drop all Widgets except Consumer widget.
You could then summarize the use cases to:
final a = Provider<A>(...);

final b = Provider((ref) {
  A value = ref.watch(a);
  ref.listen<A>(a, (value) {
  });
});

Consumer(
  builder: (context, ref, child) {
    A value = ref.watch(a);
    ref.listen<A>(a, (value) {
    });
  },
);

Regarding the main RFC issue:
Having ref.watch makes sense to me if we can maintain compile safety.
I'm all for keeping it minimal, so i would drop all Widgets except Consumer widget.
You could then summarize the use cases to:
final a = Provider<A>(...);

final b = Provider((ref) {
  A value = ref.watch(a);
  ref.listen<A>(a, (value) {
  });
});

Consumer(
  builder: (context, ref, child) {
    A value = ref.watch(a);
    ref.listen<A>(a, (value) {
    });
  },
);

Closing this as I won't proceed forward with this variant.
The opinions are fairly biased, and a good alternative has been proposed.

I've opened a new RFC with the alternate syntax proposed https://github.com/rrousselGit/river_pod/issues/335


Consider removing queries again into their own plugin

This has come up before from the perspective of simplifying core sonobuoy, but as we are continuing to make building/installing plugins easier we should reconsider it again.
The blocker was always that we wanted the queries to run after the other plugins.
That leads to the question of how to implement that ordering:

as a one off for this plugin? We don't want one offs anymore when possible!
as a basic ordering scheme (optional value on plugins, defaults to 0 but settable so that you can change the query-plugin value to 1 (or 99, etc) and it will run afterward. This is pretty easy to implement and I had a working branch with that before. I'd vote here if we do this.
as a full effort to support plugin ordering via a directed-acyclic-graph (a graph of dependencies that wont loop on itself). This would be like in github actions where you can say step E requires step A,B to be done. And B may require F,G,Z. This is much more complicated but would be very robust especially if we, somehow, allow users to chain resources so that what is produced in one plugin is used by another.
Another option? In a way this is already supported if you're really savvy with the plugins. You just make a single plugin that wraps steps A,B,C then internally handles passing output around and submits final results to the aggregator. The aggregator would only know about the whole "recipe", so it would only report it as a single plugin though.

Two small issues recently make this seem like a good idea:

error flow for this query logic is different than error flow for any plugin. It would be better handled/logged if it was just a separate plugin
if it wasn't baked in, we could make modifications out of band from sonobuoy releases themselves and reduce risk from bugs

#1550 Helped make error handling a bit better. Still not out of band, but I do think its already improved by being extracted a bit from the discovery.Run logic.


Version updates

Update dependencies to latest major versions.  Dependent on https://github.com/nodesecurity/nsp/pull/88

this breaks in node 0.12/0.10


chore: update svg attributes to React-compatible attributes

Before
The build had some warnings due to incorrect React attributes:

After
The attributes were updated to be compatible with React

Still looks good in Sidebar app

Still running into SVGs that don't load in the breakout modal. Wonder if this is related?


⚠ Bofrost.at has degraded performance

In b71f3f8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 952 ms

Resolved: Bofrost.at performance has improved in c548b08 after 9 minutes.


Consider a more contemporary installer

The ordinary Windows Installer I currently use does not seem to be a top-notch tool.
I want to conduct a research and find a better alternative. Probably it will have some features built in, like auto-update, and easy-to-inject code.

WiX is a good option to start with

WIX got implemented with #124


Change object annotation layer orders?

Hi I am wondering if it is possible to change the annotations's layer order?
When I am using the tool for segmentation labeling, on the object panel, the early labeled objects are always on lower layers, and the later labeled objects are always covering the early ones. Is it possible to change the orders of the annotations on the object panel?

@liand23
Hi, Please, read about z order.
You also can enable it for a task after it has been created, by using an admin panel.

Got it! Thank you very much!


Braavos wallet write returns an error for successful executions

in files frontend/src/components/NewProposalForm.tsx & frontend/src/components/Proposal.tsx
Braavos wallet connection only works on HTTPS or localhost
transaction goes through but an error is returned by the SDK

@DaveVodrazka I assume you faced this issue already, not really a blocker since the tx still goes through, but curious to know what's wrong

I don't use starknet-react on the Carmine app, so I don't have much experience with it 🤷♂
But if I have the time I will check what's going on (but probably not anytime soon)

I would love to work on this Issue @tensojka

@Jemiiah were you able to reproduce it?

Yes I was @tensojka and I’ll be able to fix it by today

great, go ahead then

Great!!! @tensojka thank you


Ignore scenario loading errors to enable other testing

@nedbat | @cpennington pls review

Coverage decreased (-23.6%) to 68.499% when pulling bbcb69ee3a0bc21bd28ae1bdf7875b66d8c9c9b1 on dhm/fix_bootstrap into 70162eef4ed0f587cc5f337accdb92fd40c1a81a on master.


Window.bind on_drop_* not working

Software Versions

Python: 3.10.7
OS: Windows 11
Kivy: v2.1.0, v2.2.0.dev0
Kivy installation method: kivy[full], kivy[base], master

on_drop_file, on_drop_end, on_drop_begin and on_drop_text not working for Window.bind
it doesn't even give an error
# import kivy.graphics.cgl

# kivy.graphics.cgl.cgl_init(allowed=["sdl2"], ignored=["glew"])
from kivy.app import App
from kivy.core.window import Window

from kivy.uix.button import Button
from kivy.uix.boxlayout import BoxLayout
from kivy.uix.scrollview import ScrollView
from kivy.uix.gridlayout import GridLayout
import sys

class DropApp(App):
    def build(self):

        box = BoxLayout()
        self.scrV = ScrollView(width = 300, height = 400, size_hint_x=None, size_hint_y=None)
        box.add_widget(self.scrV)

        layout = GridLayout(cols=1, spacing=10, size_hint_y=None)
        layout.bind(minimum_height=layout.setter('height'))
        for i in range(100):
            btn = Button(text=str(i), size_hint_y=None, height=40)

            layout.add_widget(btn)
        self.scrV.add_widget(layout)

        Window.bind(on_drop_file=self.handledrops)

        return box

    def handledrops(self, window, filename, x, y):
        """
        if self.scrV.collide_point(*Window.mouse_pos):
            pass
        """
        print("It's Working!", file=sys.stderr)
        print("It's Working!", file=sys.stdout)
        raise Exception("It's Working!")

if __name__ == '__main__':
    DropApp().run()

[INFO   ] [Logger      ] Record log in C:\Users\hasan\.kivy\logs\kivy_22-10-10_48.txt
[INFO   ] [deps        ] Successfully imported "kivy_deps.gstreamer" 0.3.3
[INFO   ] [deps        ] Successfully imported "kivy_deps.angle" 0.3.2
[INFO   ] [deps        ] Successfully imported "kivy_deps.glew" 0.3.1
[INFO   ] [deps        ] Successfully imported "kivy_deps.sdl2" 0.5.0
[INFO   ] [Kivy        ] v2.2.0.dev0
[INFO   ] [Kivy        ] Installed at "C:\Users\hasan\Desktop\arge\merge-excel\venv\lib\site-packages\kivy\__init__.py"
[INFO   ] [Python      ] v3.10.7 (tags/v3.10.7:6cc6b13, Sep  5 2022, 14:08:36) [MSC v.1933 64 bit (AMD64)]
[INFO   ] [Python      ] Interpreter at "C:\Users\hasan\Desktop\arge\merge-excel\venv\Scripts\python.exe"
[INFO   ] [Logger      ] Purge log fired. Processing...
[INFO   ] [Logger      ] Purge finished!
[INFO   ] [Image       ] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffpyplayer ignored)
[INFO   ] [Factory     ] 189 symbols loaded
[INFO   ] [Window      ] Provider: sdl2
[INFO   ] [GL          ] Using the "OpenGL" graphics system
[INFO   ] [GL          ] GLEW initialization succeeded
[INFO   ] [GL          ] Backend used <glew>
[INFO   ] [GL          ] OpenGL version <b'4.6.0 - Build <IP_ADDRESS>11'>
[INFO   ] [GL          ] OpenGL vendor <b'Intel'>
[INFO   ] [GL          ] OpenGL renderer <b'Intel(R) UHD Graphics 630'>
[INFO   ] [GL          ] OpenGL parsed version: 4, 6
[INFO   ] [GL          ] Shading version <b'4.60 - Build <IP_ADDRESS>11'>
[INFO   ] [GL          ] Texture max size <16384>
[INFO   ] [GL          ] Texture max units <32>
[INFO   ] [Window      ] auto add sdl2 input provider
[INFO   ] [Window      ] virtual keyboard not allowed, single mode, not docked
[INFO   ] [Text        ] Provider: sdl2
[INFO   ] [Base        ] Start application main loop
[INFO   ] [GL          ] NPOT texture support is available

Seems like an issue with Windows 11 as your code works on Windows 10.

@Brankhos Can you install latest version of kivy_deps and re-test?

I'm with the same problem, but my version from windows was 10. I'm with the latest version from Kivy (2.2.1).


Leonardo's race-control-tv working perfect of NVidia Shield set-top box

This is a non issue, but I'd like to thank Leonardo. Now race-control-tv is infinitelly better than official F1TV on an NVidia Shield Android TV set-top box. I can use nvidia remote without issue, in order to access the content.
Thanks to all original race-control-tv authors and Leonardo, especially.
Obrigado!

Valeu mano 👊🏾


Add spec documentation for superfluid

Closes: #XXX
Description

Adds additional documentation for superfluid, reviews on how we want to improve documentation and what additional documentations we need are needed!

For contributor use:

[ ] Targeted PR against correct branch (see CONTRIBUTING.md)
[ ] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[ ] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[ ] Re-reviewed Files changed in the Github PR explorer

Merging this PR!


Global rcParams change on import

In persim/landscapes/visuals.py, line 15 defines mpl.rcParams["text.usetex"] = True. This means that whenever we import persim, the behavior of pyplot changes to that setting in all the pyplot uses. This is undesirable, as the user might prefer the default pyplot options for other uses than calls through persim.
If TeX rendering is necessary for the plots, is it possible to do the change only locally whenever a plot is created? It could be done using with mpl.rc_context({"text.usetex": True}): construction or by passing usetex=True at the individual places where it is desired.

Thanks for the issue @OnDraganov. Absolutely! I agree that this shouldn't be set as a global. I believe we only use TeX for subscripts and superscripts in a mathematician friendly way. I think the context manager mpl.rc_context is a great way to deal with this. Are you interested in submitting a PR to implement the change?

I've just encountered the same problem.
If TeX is only used for subscripts and superscripts, it might not be necessary at all?
Default math rendering by matplotlib does this already. In that case, I would remove the line entirely and let the user choose to turn TeX if they want to.
Unless you use specific characters with which it may not work?

@maximelucas The layers of the landscapes (indexed over depth) are typically denoted with $\lambda$, but I don't think we need latex for that. I think we can just use unicode characters, as shown in the updated answer here. If you agree, then please submit a PR implementing that change.

I tried and r$\lambda_{2}$ actually shows correctly even with matplotlib.rcParams['text.usetex'] being False (matplotlib version 3.8.4). So just erasing the 15 should be enough. Is that worth a pull request?

Yes most of the time it works even without the "r" in front.
I just created a PR.


Refactor tests related to notBefore and nbf (#492)

First PR for #492.
This change extracts all tests in the current files related to notBefore and nbf into a single test file. It also adds several missing related tests.
I believe I removed all references to nbf and notBefore from the current tests.
There are two TODOs in the tests, because I found a few unhandled cases that I expected would cause an error but did not. They are:

Passing an empty string to notBefore. I'm not sure if this should default to 0 or should throw an error. Currently it throws a val is not a non-empty string or a valid number. val="" from ms.
Passing -Infinity, Infinity and NaN to nbf. These all JSON.stringify to null, so I would assume should be considered invalid.

Any suggestions of missing tests are more than welcome, and I will gladly add!

I fixed some of the formatting in https://github.com/MitMaro/node-jsonwebtoken/commit/943dab9 after fixing the issues noted above.


Fixes internal ninja links in announcement push notifications

fixes #134104237

The specs were failing compilation on those two cells. Adding public got a compile.


[documentation] Align contents section in README

Came here from ApacheCon, saw this and thought I'll start my contributions here 😄
This PR adds changes to format the contents section of the README in a way that the 9th and 10th list element are not rendered on to the same line. I've also changed the numbering from 1,2,3,4 to 1,1,1,1 so that Markdown can figure out the numbering (lesser chance of missing a number in the list)
Before:

After:

For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[x] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[x] Have you written or updated unit tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

@nikochiko Thank you for your contribution!
For tracking purposes I created a JIRA ticket for this fix. Please prepend 'GEODE-9619: ' to the title of this PR.
You can view the JIRA ticket at https://issues.apache.org/jira/projects/GEODE/issues/GEODE-9619?filter=allopenissues.
I could not locate your username in the system, so I assigned the ticket to myself for now.

Hey @davebarnes97 Thank you for reviewing the pull request.
I have added an account on Jira as well with the username nikochiko. (I thought it was only for Apache folks so I hadn't created an account earlier)


core-image-minimal: Bootloader fails to perform autoboot from eMMC on Jetson TX1

Hello madisongh,
first of all thank you for this BSP. We have the following problem:
We basically followed issue #12 and were
successful with the core-image-sato, but with core-image-minimal the boot process failed.
The flashing looks good but when U-Boot scans mmc 0:1, it doesn't recognize anything to boot from. Indeed ls mmc 0:1 boot reveals, that /boot is empty.
We tried this with branch morty-l4t-r27.1 as well as with commit 1436d4c2ad8dd1ec3d96f475629a4d7b1c354116 from master.
Do you have any clues for us what to try next?
Thanks in advance,
selbstereg

Yes, I ran into this as well.  I may need to move kernel-image and kernel-device tree from MACHINE_EXTRA_RRECOMMENDS to MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS, since the minimal rootfs only includes the latter, and for booting any of the Tegra systems we pretty much need those files all the time.
In the meantime, you can work around it by adding
IMAGE_INSTALL_append = " ${MACHINE_EXTRA_RRECOMMENDS}"

to your local.conf.

Awesome, that worked. Thank you very much and have a good time maintaining your great layer.


Improve usage

Might be a codegangsta issue but the usage is a bit messed up:
$ kompose k8s ps -h
Usage: kompose ps [OPTIONS]

Get active data in the kubernetes cluster

Options:
   --services, -s	Get active services
   --rc, -r		Get active replication controller

Usage should list kompose k8s ps
That issue is valid for all subcommands.
Interestingly kompose k8s returns the usage for convert alone and not the kompose k8s help

Yes. It also doesn't list subcommands, even show details of the first of them.
`$ kompose k8s -h
Usage: kompose convert [OPTIONS]
Convert docker-compose.yml to Kubernetes object and submit
Options:
--file, -f "docker-compose.yml"	Specify an alternate compose file (default: docker-compose.yml) [$COMPOSE_FILE]
--deployment, -d			Generate a deployment resource file
--chart, -c				Create a chart deployment
--yaml, -y				Generate a deployment resource file in yaml format
`

I have this:
$ kompose k8s ps --rc
Name           Containers     Images                        Replicas  Selectors
redis          redis          redis:3.0                     3         service=redis

$ kompose k8s ps --svc
Name                Cluster IP          Ports               Selectors
redis               <IP_ADDRESS>           TCP(6379)           service=redis

and I'd expect to see all of them or at least error message without specifying options:
$ kompose k8s ps
(returns me nothing)

This issue was solved on kompose2


added cursor moving effect 404 error message

Please read #18 before submitting. This is going to be closed since it's not using tsParticles as requested.


[move-only] fix conformance synthesis & conformances in extensions

resolves rdar://104986597

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test macOS

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge


Sequentially dock two molecules vs multi-ligand docking

Hi,
I want to dock a cofactor-substrate pair into several designed enzyme pocket (no metal). What I found was that the cofactor usually get a good pose while the substrate not. So I'm wondering:

Is it at all possible to do sequential docking in one-line command, i.e. cofactor first then the substrate with the cofactor held in place?
If the above option not supported, can I combine the docked cofactor pose and the enzyme into one .pdb and perform another round of docking? Do I prepare the receptor as usual and is ADFRsuite able to handle it?
Conceptually are sequential docking and docking two molecules at the same time different? Or are they gonna yield the same result?

I'd appreciate your help! Thanks in advance.

Hello,

no
this is the way to do it
yes they are different, no guarantees of getting the same result

Thanks for your reply. Then my question is how to prepare a receptor with small molecule in it? ADFRsuite gives me the message:

'  ' apparently composed of not std residues. Deleting

And the prepared .pdbqt has no small molecule that I want to have there.

Hi @andrew0901
The default behavior of ADFRSuite's prepare receptor is to delete chains that are entirely made up of nonstandard residues or ligands. With that, to keep a small molecule you could change the small molecule's chain ID to the same chain ID as the protein receptor


[BUG]: Issue with Sandbox Account Payment Failure

Is there an existing issue for this?

[x] I have searched the existing issues.

🐞 Describe the Bug
Hi,
I am encountering an error when trying to make a payment using a sandbox account, and the transaction fails.
I have also tried recreating a new sandbox account and retrying, but the same error occurs.
On the other hand, a one-time payment with a production account and a subscription payment with a sandbox account both work successfully.
Below is the code that fails to make the payment:
〜
const paypalScriptOptions = {
    'client-id': 'test',
    currency: 'JPY',
};

<PayPalScriptProvider options={paypalScriptOptions}>
    <PaypalButton />
</PayPalScriptProvider>
〜

Do you have any solutions for this issue?
😕 Current Behavior
No response
🤔 Expected Behavior
No response
🔬 Minimal Reproduction
No response
🌍 Environment
| Software         | Version(s) |
| ---------------- | ---------- |
| react-paypal-js  |  8.3.0     |
| Browser          |  Chrome and Firefox     |
| Operating System |  Mac OS          |

Relevant log output
No response
Code of Conduct

[ ] I agree to follow this project's Code of Conduct

➕ Anything else?
No response

We have moved this repository to our paypal-js monorepo: https://github.com/paypal/paypal-js
We will be archiving this repo at the end of the day which will turn off Issues activity. If this is still an issue for you, please re-open this issue here: https://github.com/paypal/paypal-js/issues


Update cuco git tag

Related to https://github.com/rapidsai/cudf/issues/12108.
This PR fetches the latest cuCo git tag to fix a bug of iterator range overflows.
Description

Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The cmake-format.json is up to date with these changes.
[ ] I have added new files under rapids-cmake/

[ ] I have added include guards (include_guard(GLOBAL))
[ ] I have added the associated docs/ rst file and update the api.rst

I can change the base branch to 22.12 if it's a hot fix.
cc @abellina

Targeting 22.12 based on offline discussion.

@PointKernel @bdice we ready to merge this?

@PointKernel @bdice we ready to merge this?

Yes, please. I don't have write access to this repo.

@gpucibot merge


GH-84 refactor DNSRecord conflict detection

Currently contains only the logic to change behaviour on conflict detection and conflict resolution.
Also moves all the logic for updating the status of the DNS Record to the updateStatus() func.
Finally, allows you to override default validation timeout using a flag (defaults to the 5 sec)

It has as a base Mike's PR #103 I guess it is a merge race! (that is there will be changes on that PR) If that looks good we can have one PR to rule 'em all

Also added an option to override validation timeout for the DNS controller. With the "default" 5 seconds some tests could be flaky and would timeout after 15 secs.  In this repo the integration suite doesn't take ages to run, but I'd rather make tests faster if I can rather than increasing timeouts

This looks basically fine, other than a few small comments


Close connection if requestTLS fails

Correctly close the PostgreSQL connection if requestTLS fails.
Resolves #133
I'm assuming this needs a test?

@gwynne test added. Remove the fix, tests crash. Add fix, tests pass

These changes are now available in 1.4.1


New Package tinygo-org.tinygo 0.27.0

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Resolves #109049
Microsoft Reviewers: Open in CodeFlow

Pull request will be marked as merge because there is a validation error in the pipelines.

Stephengille Pull request will be marked as not merge because there is a validation-executable-error in the pipelines.

I believe this error might be due to the dependency.

Ok.

Another problem is the TinyGoRoot environment on the app which unable to set.

Hmmmm....

Automatic Validation ended with:

Exception during executable launch operation System.AggregateException: One or more errors occurred. (The system cannot find the file specified.)  ---
System.ComponentModel.Win32Exception (2): The system cannot find the file specified.
--- End of stack trace from previous location where exception was thrown ---    --- End of inner exception stack trace ---    at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)