[arrow] Update to 10.0.1

Describe the pull request

What does your PR fix?
None

Which triplets are supported/not supported? Have you updated the CI baseline?
Not changed, No

Does your PR follow the maintainer guide?

Yes

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

Feature plasma,s3,parquet,orc,json,jemalloc,flight,filesystem,example,dataset,csv tested successfully in the x64-linux triplet


Dividers do not participate in the calculation

Adding of divider causes wrong calculations of scrollY

Thank you for your fix!


With Add pytest plugin #57117 and Add renode-test integration #56770 we have the start of a common API

Both of these PRs describe similar solution to a common problem. Can we call different Twister runners?
Add pytest plugin #57117
Add renode-test integration #56770
It is my understanding, they they both use pyTest, in different manors, and would benefit from a common front end that already chooses tests plans, and a common back end that using report formats that can be scrapped to be integrated into regression analysis report. I suspect that those parts might remain the same and the runner in the middle can be extended in multiple ways
I'd like us to start looking at the common parts and lets those be tools so the end parts look the same
They can be interegratre as needed in the new systems. Initially, there may be little overlap, but the integrators and consider the possiblities for a later integration stage.
Alternatives are already in play in both solutions
The goal is NOT to slow down merging those solutions in ASAP, but the establish another phase, where this integration can become universal.

for top-down view, do we have a use case diagram on what we expect the control flow should be? As now we have two approaches, and the acrually all act as an twister plugin way, and use twister as a shell and takeover the control by calling its internal calls.  and to unify the apis, we need:

do we need unify the API calls?
does each plugin in need shall the same data such as the functionality can easily shared/overried by other?
do we expect the same reporting result of each plugin? I think we do.

Just a small clarification. Both solutions have python on it's base. However one is based on robot framework and the other on pytest.
1.) I don't think the exact same api is possible since different frameworks have their own interfaces. However, having a unified integration of multiple framework with twister can be beneficial. Already, both PRs are based on harness functionality in twister.
2.) Indeed, both PRs show how to use these frameworks for shell testing but they use different approaches and test's source code. I don't think one test code can be reused by another framework (but the app under test can).
3.) Those are different frameworks and one test cannot be rerun with other framework, hence having "the same" result might not be desired. Although, the reporting should be unified in a way that in the end all results are seen in the final twister report and maintain common format.
I will be showing some simplified flow charts on how the integration with twister is done during our plugin presentation. Maybe it can serve as a starting point for what you're asking Dennis.

I was not suggesting "identical results", but rather a common
reporting framework. From what I've seen, it's hard for even the current
Twister to get "identical" results on some intermittent tests, but both
results are reported in a common format/API. That is the desire, common
reportability tools, not repeatability, at least not yet. ;)
On Wed, May 10, 2023 at 6:56 AM Piotr Zierhoffer @.***>
wrote:

I second what @PerMac https://github.com/PerMac says - these are
conceptually similar, but different solutions addressing different needs
and based on different technical details.
Regarding result reporting, it's difficult to generate identical results,
because we test different things.
What we can do is to produce test results in the xUnit format.
Of course Twister also gathers these results as usual.
—
Reply to this email directly, view it on GitHub
https://github.com/zephyrproject-rtos/zephyr/issues/57715#issuecomment-1542261554,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMUWPUWVIBQES7BI522TTXFOM7NANCNFSM6AAAAAAX3YPJ5E
.
You are receiving this because you authored the thread.Message ID:
@.***>

common results reported in json format by twister is exactly what we have now.


support http_proxy

it seems that run curl command to get nano-server.md maybe. but i'm on proxy environment.

Does anybody have any familiarity with configuring a proxy on linux?
@glinton @notxarb ?

@mattn can you define your problem/goal a little bit more? What is your environment like and what would you like to see happen?

$ nanobox dev

At the first, AFAIK, vagrant create new docker VM and getting nanobox image. But my network environment can't get the image. So I hope to pass environment variable http_proxy/https_proxy/http_proxy_user/http_proxy_pass into the docker VM.

Ok, I think we can make that happen.  And I assume you are able to fetch the vagrant box from within your network environment (vagrant box add nanobox/boot2docker)?

In my understanding, on windows nanobox run on boot2docker. And it seems the init script is downloading something from AWS.

@glinton, @lyondhill: Can we find out if nanobox v1 works within a proxy network?

From what I've read, I think this issue can be resolved, since we no longer use vagrant, the proxy vars should work. It is on my list of things to test/verify though before I close this.

@mattn if this is still an issue feel free to reopen


Upload AVS workbook

Overview/Summary
Uploading AVS workbook template v1
This PR fixes/adds/changes/removes

New visuals, more comprehensive than the dashboard

Testing Evidence

Replace this with any testing evidence to show that your Pull Request works/fixes as described and planned (include screenshots, if appropriate)

As part of this Pull Request I have

[x ] Checked for duplicate Pull Requests
[x ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[x ] Performed testing and provided evidence.
[ ] Updated relevant and associated documentation.

Changed workbook flie to ARM template


Question

The most useful tool.
Have a option to add my own signature when build ?
I try build some older apps and say the app can't install.

You need to sign after any APKEditor actions. Search apksigner

Yeah, right.
Thanks.
That would be great if you can integrations, to be able to put our signatures, like apk editor studio.


Could not create share link. the gradio problem！

Could not create share link. Please check your internet connection or our status page: https://status.gradio.app.
i have the file:frpc_linux_amd64_v0.2 in my conda envs,
and i had done:chmod +x frpc_linux_amd64_v0.2
but i never observing share link on the commond line. how can i sovle it?

I'm sorry, but the information you provided doesn't seem to be enough to tell where the problem is.


'numpy.ndarray' object has no attribute 'show_result'

I used the docker installation environment. The demo program just ran, and I found that the entire function of show result cannot be used. Is this a bug? I'll look at the source code later

and

i have same problems, do you solve them?

Hi @SubMarineas
The first argument of show_result_pyplot should be model not image.

@xvjiarui Okay, I built it under windows and looked at the source code and it was resolved


OLS-1262: use CVE-free virtualenv

Description
OLS-1262: use CVE-free virtualenv
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[x] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-1262

/test 4.17-e2e-ols-cluster
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"
/approve

/test 4.17-e2e-ols-cluster

/test 4.17-e2e-ols-cluster

/lgtm

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 96.97%. Comparing base (e1ae8a7) to head (36a8bf8).
Report is 57 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1993      +/-   ##
==========================================
+ Coverage   96.95%   96.97%   +0.02%
==========================================
  Files          69       69
  Lines        2886     2909      +23
==========================================
+ Hits         2798     2821      +23
  Misses         88       88

see 4 files with indirect coverage changes


[Pager] Modifier.pagerTabIndicatorOffset doesn't support Material3 TabPositions

Description
Modifier.pagerTabIndicatorOffset(pagerState, tabPositions) only supports Material 2 TabPositions.
I'm in the process of writing the migration guide and deprecating Pager in #1504, however, I've noticed even though we've added Modifier.pagerTabIndicatorOffset(pagerState, tabPositions) to work with androidx.compose.foundation.pager, the tab positions object is Material 2 and there isn't an option for Material 3.
Should we add another variant of this Modifier for Material 3? Or how best would it be to proceed here?
cc @Levi-Moreira

I don't think it is something we should solve as part of migration/deprecation of Pagers because we didn't have material3 support for old pager, and we will not have it for the new pager. We stay on the same level of support here.
This question is complex in solving, we can't just add one more modifier as we shouldn't have a library which depends on both material versions. So we or create a separate material3 specific library in accompanist for such indicator, or just not solve it for now, with the idea that long term such modifier should live in compose.material3 library, not in accompanist

That makes sense, I'll leave it as is then. Thanks @andkulikov!


walredo: add tenant_id to span of NoLeakChild::drop

We see the following log lines occasionally in prod:
kill_and_wait_impl{pid=1983042}: wait successful exit_status=signal: 9 (SIGKILL)

This PR makes it easier to find the tenant for the pid, by including the tenant id as a field in the span.

Cc: #3604


Clear formatting

Is it possible to clear formatting on selected text? I tried defining a command but didn't make it work.

I am having the same issue, also, was not able to create a custom command or action.


add note about retrieving error stack to SSL_get_verify_result(3)

This change augments the SSL_get_verify_result(3) man page with a note about retrieving error stack. This would have helped me when diagnosing a subtle certificate verification error.

This pull request is ready to merge

Merges, thanks for the clarification.

Hi everyone, sorry for commenting on an already merged PR, but I'm trying to understand the SSL_get_verify_result(3) man page notes added with this PR.

Sometimes there can be a sequence of errors leading to the verification failure as reported by SSL_get_verify_result(). To get the errors, it is necessary to setup a verify callback via SSL_CTX_set_verify(3) or SSL_set_verify(3) and retrieve the errors from the error stack there, because once SSL_connect(3) returns, these errors may no longer be available.

The above notes says, the errors may no longer be available once SSL_connect(3) returns. Does that mean I won't be able to retrieve the cert verify error via SSL_get_verify_result(3) outside of the verify callback?
Also, noting that the errors might be gone after SSL_connect(3) returns, is that specific to client side handshake routines or does that apply to the server side as well?
I just want to know if I can safely use X509_verify_cert_error_string(SSL_get_verify_result(ssl)) outside of the verify callback without losing the exact certification error.
Thanks!


Add plz a jshintrc editorconfig jscs

Hi ,
I want to help this framework but i need some code convention style from you to do it right !
examples https://gist.github.com/DrMabuse23/88e6686e59dffaa00936

oh its been included i didnt see


Unable to install mesheryctl v0.6.5, meshery-perf and meshery-cillium are crashing

Current Behavior
Current release v0.6.5 failed to complete installation, both meshery-perf and meshery-cillium are crashing. From the previous release, meshery-perf and meshery-cpx are supposed to be deprecated, however, installing the Helm charts, still pulled in meshery-perf even though it is disabled.
For Cillium, here is an existing issue open #71 at the meshery-cillium error provided still persist in my cluster.
I have a possible fix but I'm currently testing it at this time, I would like to submit a PR and I am open to anyone willing to help with me.
Expected Behavior
Installation is supposed to be successful.
Screenshots/Logs
kubectl get pods -n meshery
NAME                                    READY   STATUS             RESTARTS        AGE
meshery-meshery-cpx-5b49b48fdf-7h4g5    1/1     Running            0               5m45s
meshery-istio-65f67fb978-rtfgr          1/1     Running            0               5m45s
meshery-linkerd-cc65f9d78-fspnl         1/1     Running            0               5m44s
meshery-consul-8484fbcc96-kxkjx         1/1     Running            0               5m45s
meshery-operator-7bb97dfdb-j796z        2/2     Running            0               5m44s
meshery-osm-6fbc9769cd-lcpjs            1/1     Running            0               5m43s
meshery-697fd8446-4zgbz                 1/1     Running            0               5m43s
meshery-app-mesh-67c78f557d-xgww5       1/1     Running            0               5m45s
meshery-kuma-785765997-xfzcc            1/1     Running            0               5m44s
meshery-nsm-7788546ff6-wbzgz            1/1     Running            0               5m44s
meshery-traefik-mesh-c5548d4f6-7wk4t    1/1     Running            0               5m43s
meshery-nginx-sm-5c5569dbf4-dx9kg       1/1     Running            0               5m44s
meshery-broker-0                        2/2     Running            0               5m39s
meshery-meshsync-7b498c5686-dwstd       1/1     Running            2 (5m24s ago)   5m38s
meshery-meshery-perf-5bbd4f86df-89pp8   0/1     CrashLoopBackOff   5 (2m39s ago)   5m43s
meshery-cilium-7757c94c4d-46225         0/1     CrashLoopBackOff   5 (2m11s ago)   5m45s

Environment

Host OS: Linux and Ubuntu 22 WSL2
Platform: Kubernetes k3d
Meshery Server Version: stable-v
Meshery Client Version: stable-v

Contributor Guides and Handbook

🛠 Meshery Build & Release Strategy
📚 Instructions for contributing to documentation

Meshery documentation site and source

🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

Removing the two charts: meshery-perf and meshery-cpx from the values.yaml did not work, I tried removing any instances of them being mentioned via the Charts. However, deleting the two folders, solved the issue of keeping the two Docker images being pulled into the Helm deployment.
Please let me know if this was the intention to remove these two from the charts, and not to be used anymore via deployment.
Cilium still persist with the error as before.

@CyrineG @alphaX86 @AugustasV

Removing the two charts: meshery-perf and meshery-cpx from the values.yaml did not work, I tried removing any instances of them being mentioned via the Charts. However, deleting the two folders, solved the issue of keeping the two Docker images being pulled into the Helm deployment.

@acald-creator that is weird. Setting the condition values should be enough, unless the boolean variable path defined is not the correct one :thinking:

@CyrineG I'm thinking thee same thing as well, I'll see if I can make some changes to test to see if it works out or not, where I may not have to removed the folders completely.

I haven't made any changes but was there something changed? This is occurring from the master branch and v0.6.5 tag. I even clone the project separately, and this error came up.
helm install meshery meshery/ --debug --dry-run
install.go:178: [debug] Original chart version: ""
install.go:199: [debug] CHART PATH: /home/auxyria/go/src/github.com/acald-creator/meshery/install/kubernetes/helm/meshery

install.go:206: [debug] WARNING: This chart or one of its subcharts contains CRDs. Rendering may fail or contain inaccuracies.
Error: INSTALLATION FAILED: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind "Broker" in version "meshery.layer5.io/v1alpha1", unable to recognize "": no matches for kind "MeshSync" in version "meshery.layer5.io/v1alpha1"]
helm.go:88: [debug] [unable to recognize "": no matches for kind "Broker" in version "meshery.layer5.io/v1alpha1", unable to recognize "": no matches for kind "MeshSync" in version "meshery.layer5.io/v1alpha1"]
unable to build kubernetes objects from release manifest
helm.sh/helm/v3/pkg/action.(*Install).RunWithContext
        helm.sh/helm/v3/pkg/action/install.go:277
main.runInstall
        helm.sh/helm/v3/cmd/helm/install.go:265
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:125
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371
INSTALLATION FAILED
main.newInstallCmd.func2
        helm.sh/helm/v3/cmd/helm/install.go:127
github.com/spf13/cobra.(*Command).execute
        github.com/spf13/cobra@v1.2.1/command.go:856
github.com/spf13/cobra.(*Command).ExecuteC
        github.com/spf13/cobra@v1.2.1/command.go:974
github.com/spf13/cobra.(*Command).Execute
        github.com/spf13/cobra@v1.2.1/command.go:902
main.main
        helm.sh/helm/v3/cmd/helm/helm.go:87
runtime.main
        runtime/proc.go:225
runtime.goexit
        runtime/asm_amd64.s:1371

@alphaX86 Hi there, the names being appended with meshery- that's when I did a local installation trying to test the changes.
However, using the curl -L https://meshery.io/install | PLATFORM=kubernetes bash - resulted in this output.
kubectl get pods -n meshery
NAME                                   READY   STATUS             RESTARTS      AGE
meshery-nsm-7788546ff6-hrhvp           1/1     Running            0             13m
meshery-consul-8484fbcc96-wkbxh        1/1     Running            0             13m
meshery-cpx-7c6885bcfc-h92ld           1/1     Running            0             13m
meshery-operator-7bb97dfdb-f9jp5       2/2     Running            0             13m
meshery-cilium-7757c94c4d-xxgtz        1/1     Running            0             13m
meshery-osm-6fbc9769cd-sq78k           1/1     Running            0             13m
meshery-app-mesh-67c78f557d-rm7jq      1/1     Running            0             13m
meshery-nginx-sm-5c5569dbf4-f5xsj      1/1     Running            0             13m
meshery-linkerd-cc65f9d78-thdxx        1/1     Running            0             13m
meshery-istio-65f67fb978-gh4sg         1/1     Running            0             13m
meshery-broker-0                       2/2     Running            0             12m
meshery-traefik-mesh-c5548d4f6-5g7bt   1/1     Running            0             13m
meshery-kuma-785765997-52wrm           1/1     Running            0             13m
meshery-meshsync-689bb4f698-pdhcl      1/1     Running            1 (11m ago)   12m
meshery-5d8d749fb4-x7zrm               1/1     Running            0             13m
meshery-perf-794bb4f4c7-dccz5          0/1     CrashLoopBackOff   7 (28s ago)   13m

But meshery-perf and meshery-cpx are still being pulled in, even though they are deprecated? Are they meant not to be pulled in the Helm deployment?

@acald-creator they shouldn't that's why I declared them as deprecated last week to avoid them getting pulled. This is strange... seems they are dependent on something else, time to check it deep

Oh wait.... the charts are being repeated again... under meshery-operator 👀

// @leecalcote

Yes, that was going to be my next question, because it is repeated in meshery-operator and I also had a question about the versioning too, since it is at 0.5.0 and the latest release is v0.6.5.

My initial thought was that the two deprecated charts were been pulled in because it is still in the meshery-operator but I wasn't sure how dependent meshery is on meshery-operator.

So our issue right now here is that:
1- we can't delete their definition as dependencies in meshery/Chart.yaml while keeping their charts under /charts
=> because Helm expects all dependencies under /charts to be declared in Chart.yaml else the Chart Release tests fail
2- the meshery-perf and meshery-cpx are still deployed despite disabling them in Values.yaml
=> I wonder if using tags (like here) to disable them instead could work?

After the PR was reverted, I'm testing to see if keeping them disabled in either meshery-operator or meshery makes a different. Even declaring them deprecated should do something too, but I'll return with a response.

After some testing, it seems that meshery-perf and meshery-cpx takes precedent in the Helm deployment, when it is enabled true via values.yaml in the meshery-operator.
Checking the meshery helm locked file, there aren't any meshery-perf and meshery-cpx but it is still showing through the meshery-operator helm locked file.
Just updating to let you know that I'm still testing, because I reached a point even when I enabled false, and removed the charts from the values.yasml file, it was still being pulled in.


Where does the tenant URL and the credential come from?

In this tutorial's text and also video, the provenance of the secret token is not explained.

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

ID: 9399f2f6-0ccf-7f04-e5c9-eed9ef5330fd
Version Independent ID: afd04f3c-59a4-dacd-36f4-ddfb6fdd3d2d
Content: Tutorial: Configure Adobe Identity Management for automatic user provisioning with Azure Active Directory - Microsoft Entra
Content Source: articles/active-directory/saas-apps/adobe-identity-management-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @twimmers
Microsoft Alias: thwimmer

Hi @avallen, Step 2 in the tutorial explains the process of attaining secret token and SCIM Endpoint URL. You need to have an Adobe Admin Account and follow steps 1 to 4.

#please-close


BF: Fix epochs.plot_image call

The group_by parameter used here is intended for sth else (and doesn't work like this); I believe  picks is what we want instead!

Can this be merged?


[Task] How to use appsmith with your own authentication system

Hey @Nikhil-Nandagopal  can i work on this?

@sakshi006 Welcome to Appsmith & for volunteering to contribute to the project.
I'm sorry but this is a little more involved. It'll be better if a maintainer picks up this issue. I would suggest that you go through our issue list and pick one more suited for first contributors.

Sure, thanks!

We're now welcoming contribution to this issue


Fixed the omission which was happened when converting user_id from int to long.

TFJ-259 overlooked this.

LGTM. Thanks!


⚠ Bofrost.de has degraded performance

In 78f80bd, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 949 ms

Resolved: Bofrost.de performance has improved in 2274536 after 6 minutes.


Adding an e2e job for the hub-spoke topology. (#385)

This workflow is using a single cluster which is both the hub and also the spoke and test the main flow of applying a ManagedClusterModule to the hub and validating that all the artifacts are created on the spoke cluster.

Fixes https://github.com/rh-ecosystem-edge/kernel-module-management/issues/572

/hold
Didn't test it using the bundle (as we are going to do it CI) yet.

Codecov Report

Merging #593 (8db091e) into main (7bc07f1) will increase coverage by 0.06%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #593      +/-   ##
==========================================
+ Coverage   78.57%   78.64%   +0.06%
==========================================
  Files          38       38
  Lines        3482     3521      +39
==========================================
+ Hits         2736     2769      +33
- Misses        629      635       +6
  Partials      117      117

see 6 files with indirect coverage changes

/pj-rehearse

/lgtm

@ybettan can we unhold?

@ybettan can we unhold?

Nope. It is not working yet.

/lgtm


Add NFData instance for NonEmptyText

I've also added the generated cabal file since stack deprecated pointing at repos without it.

How come I missed this pull request?! This slipped through my email. Thank you for the good work @telser !


Please add support for AC0850/11

My AC0850/11 is basically being detected (and connected) via COAP and some values are being updated in the "device" folder, like
"connectType", "deviceId", "productId", started", "statusType", "uptime", "wifiVersion", and in the "info" folder, like "connection".
The other values are all null. Including support for the AC0850/11 would really be great!

Please see attachment
philips-air.0.log


DOC: add install pre-commit code

Added more verbose processing of installing and building pre-commit to save people clicking through to the pre-commit project to see how to install it.
Removed the instructions of going to the dask-ml root as I assume people are working in there if they are running things like https://ml.dask.org/contributing.html#creating-an-environment
I also looked at the xarray docs for inspiration http://xarray.pydata.org/en/stable/contributing.html#code-formatting

Thanks.


Login form cutting off input

I just tried logging in from one of the user's computers in the clerk's office, and the top / bottom of the login page inputs are being cut off.  It may be that they have their browser zoomed.

What browser & os?  Screenshots would also be helpful here.


Add possibility to specify slave labels for the job

DoD: Provide possibility to set node labels for the jobs, update current jobs to pick linux slave, add labels to the existing slave (linux, docker).

Question: How we will define which label will be assign to which node? Should I get first node and set linux , get second and set docker, etc. , or ... You now have possibility to rename and assign... manually))) If we want to assign labels during start up, what the order will be ?

@alexsedova we will have to specify such info during slave build process. This setup has only one node, and we should set labels in the start.sh. The same have to be done for any other slave that will be created later on, i.e. slave build file (Docker/Packer/whatever) will contain predefined labels


Update benchmarks

Hello @mdw362! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file druzhba_run.py:

Line 37:32: E261 at least two spaces before inline comment
Line 55:25: E261 at least two spaces before inline comment
Line 55:25: E262 inline comment should start with '# '


Path to Godot executable

Just nitpicking but the path is set twice:
https://github.com/GodotNativeTools/cpp_bindings/blob/master/SConstruct#L7
and
https://github.com/GodotNativeTools/cpp_bindings/blob/master/SConstruct#L10
But the real issue, it would be nice if this is somehow configurable, maybe an argument?

ah never mind, bin path vs lib path ;)

Hehe 😄


feat(cloudsql/postgres): update to v2 samples

A peer of https://github.com/GoogleCloudPlatform/golang-samples/pull/2312.

I've verified both public and private IP on Cloud Run, in addition to ensuring the tests pass.


fix(deps): update module gomodules.xyz/jsonpatch/v2 to v3

This PR contains the following updates:

Package
Type
Update
Change

gomodules.xyz/jsonpatch/v2
require
major
v2.4.0 -> v3.0.1

Release Notes

gomodules/jsonpatch (gomodules.xyz/jsonpatch/v2)
v3.0.1
Compare Source
This release uses our forked gomodules/orderedmap library. Our forked version has 2 major changes:

Uses *OrderedMap instead of OrderedMap inside nested orderedmaps.
I ported unstructured helpers from Kubernetes to work with orderedmaps.

v3.0.0
Compare Source
This release uses iancoleman/orderedmap to generate predictable patch. This is very useful if the generated patch is checked into a VCS like git.

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

Release note:
NONE

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: go.sum
Command failed: go get -d -t ./...
go: -d flag is deprecated. -d=true is a no-op
go<EMAIL_ADDRESS>unrecognized import path "gomodules.xyz/jsonpatch/v2/v3": reading https://gomodules.xyz/jsonpatch/v2/v3?go-get=1: 404 Not Found


Blog: Compare RetroPGF results v impact vectors

See here: https://github.com/opensource-observer/insights/tree/main/community/datasets/retropgf3_results

https://cerv1.notion.site/What-builders-can-learn-from-RetroPGF-3-separating-the-signal-from-the-noise-fa7b2fc6df4141388e61050506bb81eb?pvs=4 @ryscheng

https://github.com/opensource-observer/oso/pull/744


Updated 02_Upgrading.md

Added a few notes to the Upgrading instructions following upgrading a site to v2.  Thanks.

Great, thanks!
We could also include a link to the Omnipay 2.0 changelog: https://github.com/silverstripe/silverstripe-omnipay/blob/master/docs/changelogs/2.0.md

Thanks, will do.


Fix for Obsidian 1.3.0 log spam

Description
Fix for https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1951.
A log spam that starts in 1.3.0 due to an API change.

Motivation and Context

Users switching to 1.3.0 will be spammed in their Developer Console with hundreds or thousands of errors.
How has this been tested?

Manual test that the error is gone.
A fix to the tests.

Screenshots (if appropriate)
Types of changes

Changes visible to users:

[x] Bug fix (prefix: fix - non-breaking change which fixes an issue)
[ ] New feature (prefix: feat - non-breaking change which adds functionality)
[ ] Breaking change (prefix: feat!! or fix!! - fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (prefix: docs - improvements to any documentation content for users)
[ ] Sample vault (prefix: vault - improvements to the Tasks-Demo sample vault)
[ ] Contributing Guidelines (prefix: contrib - any improvements to documentation content for contributors - see Contributing to Tasks)

Internal changes:

[ ] Refactor (prefix: refactor - non-breaking change which only improves the design or structure of existing code, and making no changes to its external behaviour)
[x] Tests (prefix: test - additions and improvements to unit tests and the smoke tests)
[ ] Infrastructure (prefix: chore - examples include GitHub Actions, issue templates)

Checklist

[x] My code follows the code style of this project and passes yarn run lint.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] My change has adequate Unit Test coverage.

Terms

[x] My contribution follow this project's contributing guide
[x] I agree to follow this project's Code of Conduct

This fix is currently partial and does not address reading mode, see this comment: https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1951#issuecomment-1546836598
This PR should not be merged until I get some confidence about the right approach for Reading Mode.

This fix is currently partial and does not address reading mode, see this comment: #1951 (comment)
This PR should not be merged until I get some confidence about the right approach for Reading Mode.

I wonder whether a partial fix is better than no (released) fix at all?

Hi @esm7, some trivia for future reference...
I've tweaked the description thus:
- Fix for [#1951](https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1951).
+ Fixes https://github.com/obsidian-tasks-group/obsidian-tasks/issues/1951.

So that when this is merged, the underlying issue will be automatically marked as fixed.
The following would also work:
+ Fixes #1951.

A few days late to the party, I saw now your tag in Licat's answer about the correct approach for Markdown post-processors, and will do that today or tomorrow.

A few days late to the party, I saw now your tag in Licat's answer about the correct approach for Markdown post-processors, and will do that today or tomorrow.

Ah - when I belatedly logged it in GitHub, I accidentally put it in the Issue instead of this PR.

This fix is currently partial and does not address reading mode, see this comment: #1951 (comment) This PR should not be merged until I get some confidence about the right approach for Reading Mode.

This PR now fully solves the issue, after I handled the case of the Markdown post-processor based on what Licat explained over Discord (https://discord.com/channels/686053708261228577/716028884885307432/1110790107272859778).

Thanks very much @esm7 !


fix: Use api to get possible nonce

Try out this version of the Hiro Wallet - download extension builds.

fallback to default nonce calculation if the api is not available.
This should solve most of our nonce issues.
cc/ @aulneau @kyranjamie @fbwoolf

@beguene can you please convert to draft, as this should not be merged until the microblocks API is live in production 🙏

@beguene would you be able to bring this across the finish line tomorrow?

@beguene would you be able to bring this across the finish line tomorrow?

Yes.

See https://discord.com/channels/856920147381190717/856977108184989747/879837194053898361

I'm have the same 'pending' issue all day in my wallet.  Question - how do I determine the 'nonce' my wallet is set to so I can calculate how many transactions I am 'off'?  The first stuck transaction is at nonce 200 and when I send STX into my wallet it is nonce 5672.  Is there a way to tell what nonce the wallet thinks we are at?

See https://discord.com/channels/856920147381190717/856977108184989747/879837194053898361

I'm have the same 'pending' issue all day in my wallet.  Question - how do I determine the 'nonce' my wallet is set to so I can calculate how many transactions I am 'off'?  The first stuck transaction is at nonce 200 and when I send STX into my wallet it is nonce 5672.  Is there a way to tell what nonce the wallet thinks we are at?

Yes we can improve on that. There is 'detected_missing_nonces' in the api. We can use that to improve further our nonce calculation in the wallet. However I think I should do it in another PR/issue because this current PR will solve most of the issues for most users.

The first stuck transaction is at nonce 200 and when I send STX into my wallet it is nonce 5672. Is there a way to tell what nonce the wallet thinks we are at?

I do think in this situation, the difference between 200 and 5672 is likely because the nonces are associated with different accounts.

I think it's better the merge this after https://github.com/blockstack/stacks-wallet-web/pull/1608 to have the new integration with react-query
@andresgalante @markmhx Let me know if it's more urgent.

I think it's better the merge this after #1608 to have the new integration with react-query
@andresgalante @markmhx Let me know if it's more urgent.

As discussed, I will merge it before #1608 with the new QueryClientProvider from react-query

@kyranjamie I made some changes regarding the usage of hook and jotai atom. Can you review that ?

I've done some QA on this and it seems pretty stable to me. I opened up a desktop & web wallet and started sending txs from both. I'm sure I could trick it if I queued up two and fired them off simultaneously, but generally sending one, going to the other, sending a new tx etc its worked well.


PDU session status in signalling Service request is not processed

In the current free5gc, if the AMF receives the service request whose service type is signalling, it does not process the PDU session status in this service request and immediately sends the service accept without the PDU session status.
Is this behavior correct?
https://github.com/free5gc/amf/blob/e839de03774f7c5b06dbaaa368ea6f0813a4d0d9/internal/gmm/handler.go#L1643
	if serviceType == nasMessage.ServiceTypeSignalling {
		err := sendServiceAccept(ue, anType, ctxList, suList, nil, nil, nil, nil)
		return err
	}

Hi, based on the picture captured from spec 23.502 <IP_ADDRESS>, it appears that the behavior is correct. If the Service Request is triggered by the UE for signaling only, the UE does not identify any List Of PDU Sessions To Be Activated.


Moving: evernote.evernote version 10.61.4

Microsoft Reviewers: Open in CodeFlow

Hi @SpecterShell,

This PR's version number 10.61.4 has 3 parameters (sets of numbers between dots - major, minor, etc), which is less than the current manifest's version <IP_ADDRESS>40424105017, which has 4 parameters.

Does this PR's version number exactly match the version reported in the Apps & features Settings page? (Feel free to attach a screenshot.)
(Automated response - build 877)

This package's version numbers might not be semantic anymore - the patch parameter appears to be too large to be a 32-bit integer:
     | Could not compare "10.61.4" to "<IP_ADDRESS>40424105017". Error: "Cannot convert value "<IP_ADDRESS>40424105017" to type
     | "System.Version". Error: "Value was either too large or too small for an Int32.""


How to jump the cursor in latex snipppets?

A very typical example: insert \frac{}{}, I would like to move the cursor from the first bracket to the second. In your gif, I found you pressed a certain key and the cursor is directly moved. But I cannot find that key. I pressed the Tab, and nothing happens. I have to manually move the cursor.

You should be able to either press Tab or Enter and Shift+Enter while the popup is open. This works fine for me. Are you on the newest version?

Hi, I'm using the latest version of the plugin in the latest version of Obsidian, with full default hotkeys, and can't for the life of me use the "jump cursor" feature. Pressing Enter with the fraction autocomplete just places the full snippet and my cursor at the end of it.

I'm sorry, but I stopped supporting the legacy editor since live preview came out. Supporting both in the same codebase gets really messy and is a lot more work.

Ah okay. Could you add that as a disclaimer in the plugin's readme?

De: tth05 @.>
Enviado: Sunday, May 1, 2022 7:30:57 AM
Para: tth05/obsidian-completr @.>
Cc: firinael @.>; Comment @.>
Assunto: Re: [tth05/obsidian-completr] How to jump the cursor in latex snipppets? (Issue #16)
I'm sorry, but I stopped supporting the legacy editor since live preview came out. Supporting both in the same codebase gets really messy and is a lot more work.
—
Reply to this email directly, view it on GitHubhttps://github.com/tth05/obsidian-completr/issues/16#issuecomment-1114196884, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AP7NMUOZR2NFK5AK7A73XJDVHZMODANCNFSM5RISXVKA.
You are receiving this because you commented.Message ID: @.***>

Sure, maybe one the other plugins will work for you.


Bump go-version to v1.21

https://github.com/knative/networking/blob/50368a78c1c37564b9455764b88978519058b89a/.github/workflows/knative-downstream.yaml#L38-L42

/assign


IE11: Unhandled promise rejection

I get the following errors in IE11. In other browsers it just works fine. In version 2.1.266 PDF.JS still worked in IE11.
Errors:
Unhandled promise rejection TypeError: Unable to get property 'then' of undefined or null reference
   "Unhandled promise rejection"
   {
      [functions]: ,
      __proto__: { },
      description: "Unable to get property 'then' of undefined or null reference",
      message: "Unable to get property 'then' of undefined or null reference",
      name: "TypeError",
      number: -2146823281,
      stack: "TypeError: Unable to get property 'then' of undefined or null reference
   at Anonymous function (pdfjs/web/viewer.js:1204:7)
   at run (pdfjs/build/pdf.js:3269:13)
   at Anonymous function (pdfjs/build/pdf.js:3290:7)
   at flush (pdfjs/build/pdf.js:3744:9)"
   }

Unhandled promise rejection TypeError: Object doesn't support property or method 'getPageLayout'
   "Unhandled promise rejection"
   {
      [functions]: ,
      __proto__: { },
      description: "Object doesn't support property or method 'getPageLayout'",
      message: "Object doesn't support property or method 'getPageLayout'",
      name: "TypeError",
      number: -2146827850,
      stack: "TypeError: Object doesn't support property or method 'getPageLayout'
   at load (pdfjs/web/viewer.js:1210:5)
   at Anonymous function (pdfjs/web/viewer.js:1030:17)
   at run (pdfjs/build/pdf.js:3269:13)
   at Anonymous function (pdfjs/build/pdf.js:3290:7)
   at flush (pdfjs/build/pdf.js:3744:9)"
   }

Configuration:

Web browser and its version: IE11
Operating system and its version: Windows 10
PDF.js version: 2.2.228
Is a browser extension: No

Please note https://github.com/mozilla/pdf.js/wiki/Frequently-Asked-Questions#faq-support;

While the library and the default viewer should still work in IE 11/Edge (non-Chromium-based) for the time being, some functionality/features may not be available and the performance will be worse compared to modern browsers. Going forward, only bugs which completely prevent the library and/or the default viewer from running will be accepted.

It also doesn't state if this is about the default viewer or a modified (custom) viewer, so without a runnable example this is unfortunately not actionable.


fix logger in rest

Motivation:
Explain the context, and why you're making that change.
To make others understand what is the problem you're trying to solve.
Modification:
Describe the idea and modifications you've done.
Result:
Fixes https://github.com/sofastack/sofa-rpc/issues/513
If there is no issue then describe the changes introduced by this PR.

Codecov Report

Merging #678 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master    #678      +/-   ##
===========================================
+ Coverage     72.38%   72.4%   +0.01%
- Complexity     1078    1079       +1
===========================================
  Files           364     364
  Lines         15127   15127
  Branches       2424    2424
===========================================
+ Hits          10950   10953       +3
  Misses         2916    2916
+ Partials       1261    1258       -3

Impacted Files
Coverage Δ
Complexity Δ

...y/sofa/rpc/server/rest/SofaRestRequestHandler.java
51.66% <100%> (ø)
0 <0> (ø)
:arrow_down:

...y/sofa/rpc/bootstrap/DefaultProviderBootstrap.java
71.23% <0%> (-2.29%)
0% <0%> (ø)

...ofa/rpc/registry/zk/ZookeeperOverrideObserver.java
39.34% <0%> (-1.64%)
0% <0%> (ø)

...ay/sofa/rpc/client/AllConnectConnectionHolder.java
61.66% <0%> (+0.27%)
0% <0%> (ø)
:arrow_down:

...lipay/sofa/rpc/registry/consul/ConsulRegistry.java
50% <0%> (+0.57%)
19% <0%> (+1%)
:arrow_up:

...alipay/sofa/rpc/registry/zk/ZookeeperRegistry.java
63.25% <0%> (+0.6%)
0% <0%> (ø)
:arrow_down:

...va/com/alipay/sofa/rpc/client/AbstractCluster.java
67.94% <0%> (+0.64%)
0% <0%> (ø)
:arrow_down:

.../sofa/rpc/bootstrap/DefaultClientProxyInvoker.java
91.93% <0%> (+1.61%)
0% <0%> (ø)
:arrow_down:

.../main/java/com/alipay/sofa/rpc/tracer/Tracers.java
43.58% <0%> (+2.56%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Maybe it is a bug of WebView component about show image tag of png and jpg@react-native 0.39.0

there are two images, png and jpg,they can show themself normally in chromuim but not in WebView component
html code could be like this

In WebView component,

But in Chromium

            <WebView
                style={{flex: 1}}
                source={{html: "html code"}}
            />

This is the RN code
            <WebView
                style={{flex: 1}}
                source={{html: "html code"}}
            />

Sorry, I had solved this problem. It is not a bug. Thanks


docs: add overwriting css variables for dark mode

Motivation
When I wanted to change the css variables used in dark mode I struggle a bit to figure out how.
Have you read the Contributing Guidelines on pull requests?
yep
Test Plan
I ran:
yarn test
yarn test:build:v2
Closes #3985

thanks 😄

thanks 😄


⚠ ClamAV has degraded performance

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

HTTP code: 200
Response time: 74 ms

Resolved: ClamAV performance has improved in ea7bf99.


[gmp] Build error

Host Environment

OS: [Windows 10]
Compiler: msvc2019

To Reproduce
Steps to reproduce the behavior:
using vcpkg versioning to build cgal, which has a dependcy on gmp.
this is the vcpkg.json:
{     "name": "3dreconstructiondependencies",     "version-semver": "1.0.0",     "dependencies": [         "cgal"     ],     "builtin-baseline":"3426db05b996481ca31e95fff3734cf23e0f51bc",     "overrides": [     ] }
it works well for the first time and create a vcpkg_installed folder at my build directory. Then I try to add more libs(eigen3..) to vcpkg.json, it will rebuild the gmp, and the error occurs:
CMake Error at E:/test/3dreconstruction/build/vcpkg_installed/x64-windows/share/yasm-tool-helper/yasm-tool-helper.cmake:16 (message): Cross-targetting and x64 ports requiring yasm require the x86-windows yasm-tool to be available.  Please install yasm-tool:x86-windows first.
I fellow the advice and install yasm-tool:x86-windows using power-shell and try again, but the error still exists, so I open the cmake file mentioned above  which reports  the error, and I found this:
 get_filename_component(YASM "${CURRENT_INSTALLED_DIR}/../x86-windows/tools/yasm-tool/yasm.exe" ABSOLUTE) if(NOT EXISTS "${YASM}") message(FATAL_ERROR "Cross-targetting and x64 ports requiring yasm require the x86-windows yasm-tool to be available. Please install yasm-tool:x86-windows first.")
the cmake will find yasm.exe from the CURRENT_INSTALLED_DIR, it will work well when using power-shell, but vcpkg versioning will create a local vcpkg_install at my project/build, so yasm.exe cannot be found.

Thanks for posting this issue. yasm-tool has been changed after commit 3426db05b996481ca31e95fff3734cf23e0f51bc. The attached file is cgal version 5.2. You can use overlay-ports way to install it in your project.

If you use cmake project, you need add "cmakeCommandArgs": "-DCPKG_OVERLAY_PORTS=H:/Lily/cgal" to CMakeSettings.json. The path is your cgal path.
If you use msbuild project, you can add Additional Options as the picture.

Remove "builtin-baseline":"3426db05b996481ca31e95fff3734cf23e0f51bc" in vcpkg.json
build project, it will install cgal version 5.2.

cgal.zip

I tried the overlay-ports ways, and the cgal was installed successfully, thank you!


Automated Latest Dependency Updates

This is an auto-generated PR with latest dependency updates. Please do not delete the latest-dep-update branch because it's needed by the auto-dependency bot.

Going to close. This is a dup of https://github.com/alteryx/evalml/pull/2630, you can see there's no diff in the pr anymore


DataSource should raise ConfigException on config error

This change rescues ArgumentError. It is wrong behavior.
This should be fixed with #258.


x/tools/cmd/godoc: godoc doesn't list packages installed via go get

What version of Go are you using (go version)?

$ go version
go version go1.16.3 linux/amd64

Does this issue reproduce with the latest release?
yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/tnv/.cache/go-build"
GOENV="/home/tnv/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/tnv/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/tnv/go"
GOPRIVATE=""
GOPROXY="direct"
GOROOT="/usr/lib/golang"
GOSUMDB="off"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.3"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build477839898=/tmp/go-build -gno-record-gcc-switches"

What did you do?
I ran godoc and before that i installed it via go get golang.org/x/tools/cmd/godoc
What did you expect to see?
documentation for stdlib and packages that was downloaded during go get
What did you see instead?
docs for only stdlib

Let's just confirm what you did.
You started a server with godoc at port 6060 then when you visit it your package isn't listed.
Can you try the following things:

Try using the flag -index and search a regexp in the query box.
Try manually searching for the package instead of using the query box.
Try using go doc <package>

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Grouping API does not work as expected

Hello
I know this is still in alpha but I couldn't find an issue report on this.  According to the grouping API tutorial:
Grouping can be set programmatically by using the columnDef option grouping: { groupPriority: 0 }, or for aggregations on a column by setting grouping: {aggregation: uiGridGroupingConstants.aggregation.COUNT}.
Then I call notifyDataChange(uiGridConstants.dataChange.ALL) or notifyDataChange(uiGridConstants.dataChange.COLUMN)
However nothing happens when I do that.  I can instead inject uiGridGroupingService to call groupColumn and that works fine.  However like similar to the user interactive grouping when grouping is removed the columns are reordered but this only seems to happen with over 10 columns on the grid.
Code example:
onRegisterApi: function (gridApi){
$scope.gridApi = gridApi;
}
$scope.groupBy = function(columnName){
var columnDef = $scope.gridApi.options.columnDefs.filter(function(columnDef) {return columnDef.name === columnName})[0];
columnDef.groupPriority = 0;
$scope.gridApi.core.notifyDataChange(uiGridConstants.dataChange.ALL);
}
I'm using the unstable js file from Commits on Mar 12, 2015.
Thanks
Sam

The notifyDataChange isn't implemented yet, this is included in the outstanding items listed in the tutorial. But it should work if you set the grouping settings on initial render, as in the tutorial.
Sent from my iPhone

On 13 Mar 2015, at 9:08 am, SSAbraham<EMAIL_ADDRESS>wrote:
Hello
I know this is still in alpha but I couldn't find an issue report on this. According to the grouping API tutorial:
Grouping can be set programmatically by using the columnDef option grouping: { groupPriority: 0 }, or for aggregations on a column by setting grouping: {aggregation: uiGridGroupingConstants.aggregation.COUNT}.
Then I call notifyDataChange(uiGridConstants.dataChange.ALL) or notifyDataChange(uiGridConstants.dataChange.COLUMN)
However nothing happens when I do that. I can instead inject uiGridGroupingService to call groupColumn and that works fine. However like similar to the user interactive grouping when grouping is removed the columns are reordered but this only seems to happen with over 10 columns on the grid.
Code example:
onRegisterApi: function (gridApi){
$scope.gridApi = gridApi;
}
$scope.groupBy = function(columnName){
var columnDef = $scope.gridApi.options.columnDefs.filter(function(columnDef) {return columnDef.name === columnName})[0];
columnDef.groupPriority = 0;
$scope.gridApi.core.notifyDataChange(uiGridConstants.dataChange.ALL);
}
I'm using the unstable js file from Commits on Mar 12, 2015.
Thanks
Sam
—
Reply to this email directly or view it on GitHub.

I may have misunderstood the tutorial.  I thought that it was just saying it needed to be called manually for the time being.  It sounds like the hook isn't there at all yet.  Thanks for clarifying this.
Unfortunately, my goal is to allow the users to group the grid after the initial render via the API so that part won't work.  Thanks for your prompt reply.

OK, the notify data change part probably isn't too far away - I need mostly to do some testing to check how it works, but I had started to wonder whether it would work automatically with no changes at all.  Perhaps I should just expose groupColumn and aggregateColumn on the API instead - perhaps the rest of it will take care of itself.

It worked injected the uiGridGroupingService and called uiGridGroupingService.groupColumn($scope.gridApi.grid, column) and did do grouping.  The problem was after uiGridGroupingService.groupColumn($scope.gridApi.grid, column), the column order seems to get messed up.  Also performance was kind of slow with the ungroup call.  I'm happy test in our scenario either way when you're ready.

Thinking about it, the trick may be that the columnBuilders have to run.  The code uses the grouping settings on the columns themselves, and the settings are copied down from the colDef to the columns when the columnBuilders run (unless the user has made changes to the column settings directly via the UI).
So perhaps if you set the grouping on the column directly (same settings as you put on the colDef) then it would "just work".  You may also need to call grid.refresh(), or at least grid.refreshRows().

Just a quick update.  We tried the ColDef followed by the refresh.  Worked and the column order was preserved.  Thanks!

I misspoke above... it was done on columns[i].grouping not on colDef.  I edited the post to reflect the correct info.
Two things of note while I'm in here:

We had to do a sort before grouping to get the desired results
Most grid groupings I've used in the past the column being grouped on moves to the left so you can see the group headers all in one place.  Doing it this way does not result in that.  Interactive grouping does this properly however.

Hmm.  It should, the move column is in the column processor, so if the column processor runs again (which it does in a refresh()) it should move.
Do you have the latest unstable?  It's something I changed in the last few days.

The problem was with v3.0.0-rc.20-b98fa0f - 2015-03-10.  We just tried it with the latest unstable build.  The column ordering seems to be fixed.  The sorting still needs to be applied first however.

Just a few more suggestions.  It would good if the grouped column appears on the header of the grouping rather than repeated as a column in every row, as it that seems redundant.  Also grouping and pinning don't seem to play nice.  When pinning is enabled the grouping seems to push rows below.

On the repeating of the data in rows, I'm not overly thrilled with teh current look and feel but I'm somewhat constrained by a desire to not modify the row templates (doing so impacts scroll performance), and to not change the underlying data entities (can impact on people's $http requests).
So at the moment the data rows are exactly as they were before they were grouped, only the groupHeader rows are new.  I'm open to ideas as to how to do it differently within those constraints, I haven't really come up with any ideas I like a lot that would resolve it.
On pinning, we're looking at that in a few different places, it's not pinning itself, rather it's having more than 1 column in the left render container I think.

Relating to the repeating of data, the tutorial should be updated later today with an example of a cellTemplate that will avoid the data repeating in each row.
I think the right approach to doing this programmatically is to expose the groupColumn, ungroupColumn and aggregateColumn methods.  I'll do a PR with that today.  I'll include the default sort logic inside that.

Great thanks!
On Fri, Mar 20, 2015 at 8:42 PM Paul<EMAIL_ADDRESS>wrote:

Closed #2996 https://github.com/angular-ui/ng-grid/issues/2996 via #3078
https://github.com/angular-ui/ng-grid/pull/3078.
—
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/ng-grid/issues/2996#event-260938068.


Using custom InfoWindow with DirectionsRenderer

I have a potential bug that I'm trying to work through. I've posted a SO question here but it has yet to receive any answers.
Any help here would be greatly appreciated. Thank you!

I imagine that the package is mostly a wrapper around the Google Maps javascript API.

Yes. Nothing more.
The problem with your code is you're using

defaultOptions={{

with this.state.
The defaultOptions will be called once upon its first mount, and it will not reflect any state changes at all (corresponds to defaultValue for the <input> element).
You should change it to options instead.

I understand this is frustrated, but this is not a support form on how to use Google Maps API. react-google-maps is simply a wrapper around it. Unless there's a specific issue on the react-google-maps itself, please post your questions on StackOverflow instead of creating an issue here.
The maintainers only have limited time on open source projects. Please help us keep the health ecosystem. Thanks!


Cannot connect to web kubectl shell.

Rancher Version:
v1.2
Docker Version:
Server:
Version:      1.12.3
API version:  1.24
Go version:   go1.6.3
Git commit:   6b644ec
Built:
OS/Arch:      linux/amd64
OS and where are the hosts located? (cloud, bare metal, etc):
AWS EC2 (Centos 7)
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single master rancher with external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Kubernetes
Steps to Reproduce:
Create kubernetes environment and add nodes to it
Results:
kubectl web shell interface is not accessible.
Shell: kubernetes-kubectld-1
Closed
Catalog listing is also not working.
Catalog-> list
redirects to stacks page

Can you verify if this is the same issue? https://github.com/rancher/rancher/issues/6861

Looks like same.

Duplicate of #6861, closing in favor of that.


Powershell not accepting Ctrl+R for command history search

Windows Terminal version (or Windows build number)
10.0.22000.258
Other Software
No response
Steps to reproduce
Usually in VSCode integrated terminal or directly in the Powershell I press Ctrl+R to get the fuzzy search over previously typed commands. But this time it writes ^R.
The same issue with https://github.com/microsoft/Terminal/issues/350.
I even create a fresh install of Windows 11.  I double confirmed this.
But after some while, press Ctrl+R it only writes ^R. Things changed as I can remeber:
Git installed.
Powershell 7.1 installed.
kb5005537 Installed and os restarted. -- This is the clear timeline I am sure that it didn't work since.
I tried in vscode Ctrl+R still works( show the history).
PSReadLine:
Get-Module PSReadline
ModuleType Version    Name                                ExportedCommands

Script     2.1.0      PSReadline                          {Get-PSReadLineKeyHandler, Get-PSReadLineOption, Remove-PS..
Get-PSReadLineOption output works:
EditMode                               : Windows
AddToHistoryHandler                    : System.Func`2[System.String,System.Object]
HistoryNoDuplicates                    : True
HistorySavePath                        : C:\Users\UserA\AppData\Roaming\Microsoft\Windows\PowerShell\PSReadLine\Console
Host_history.txt
HistorySaveStyle                       : SaveIncrementally
HistorySearchCaseSensitive             : False
HistorySearchCursorMovesToEnd          : False
MaximumHistoryCount                    : 0
ContinuationPrompt                     : >>
ExtraPromptLineCount                   : 0
PromptText                             :
BellStyle                              : Audible
DingDuration                           : 50
DingTone                               : 1221
CommandsToValidateScriptBlockArguments : {ForEach-Object, %, Invoke-Command, icm...}
CommandValidationHandler               :
CompletionQueryItems                   : 100
MaximumKillRingCount                   : 10
ShowToolTips                           : True
ViModeIndicator                        : None
WordDelimiters                         : ;:,.[]{}()/|^&*-=+'"–—―
AnsiEscapeTimeout                      : 100
PredictionSource                       : None
CommandColor                           :
CommentColor                           :
ContinuationPromptColor                :
DefaultTokenColor                      :
EmphasisColor                          :
ErrorColor                             :
KeywordColor                           :
MemberColor                            :
NumberColor                            :
OperatorColor                          :
ParameterColor                         :
InlinePredictionColor                  :
SelectionColor                         :
StringColor                            :
TypeColor                              :
VariableColor                          :
Expected Behavior
press Ctrl+R to get the fuzzy search over previously typed commands.
Actual Behavior
press Ctrl+R writes ^R.

I found that the env $Env:__PSLockdownPolicy (value 4) was added by group policy. Remove that get it works.
Thanks.

Thanks for following up!


Make an iOS app

It can have the normal usage but also a random keyCode of the day. It can also have a key sticker for all the keys, key codes, and modifiers.

On hold for now.


Fix missed Previewer.plain call due to adjacent @ts-expect-error

I used a // @ts-expect-error until 4.3 protocol update comment in some completions code in #119009, but it unintentionally silenced an error that should have arisen as part of @mjbvz’s refactor in #119358. I’ve fixed that, and also shuffled some of the remaining temporary // @ts-expect-error comments to target less code.
I also wrote a smoke test to add to completions.test.ts, but I’m not sure how to run it (without running all smoke tests), and I have low confidence I wrote it correctly, so I haven’t committed it yet. But the content is
test('Import statement completions should work', async () => {
	await createTestEditor(vscode.Uri.parse('/node_modules/styled-components/index.d.ts'),
		`export declare function styled(): any;`
	);

	const indexUri = vscode.Uri.parse('/index.ts');
	const editor = await createTestEditor(indexUri,
		`import sty`
	);

	await acceptFirstSuggestion(indexUri, _disposables);

	assertEditorContents(editor, `import { styled } from "styled-components";`);
});

I also suppose this won’t work until smoke tests are run against TypeScript 4.3, and I’m not sure how that works either.

Thanks! Will follow up on the test once we pick up TS 4.3


Multiple keybindings

session-wizard.tmux has the comment:
Multiple bindings can be set. Default binding is "T".
How can I set multiple bindings?
I have tried:
set -g @session-wizard 'C-o'
set -g @session-wizard 'C-o o'
But that just causes TPM to fail.
Thanks!

I don't think that would be supported by the current state of the plugin.
If this were to be implemented, one way to do it would be to allow a comma-separated list of key bindings. Happy to accept a pull request if you want to submit one.


Updated supported browsers

As discussed with @t-z-u, we only aim to support newish browser versions to not get bogged down by old or crappy browsers that have bad feature support. To represent that I updated the browserslist to support up to roughly 2 year old browser versions.
Note: Brave is currently not supported by browserslist, but the chrome version mostly covers it.

i only use brave!!!

@t-z-u as explained in discord, brave is supported by us just not by the tool "browserslist", that we use for automatically handling browser feature detection/handling. But since Brave is based on chromium and only differs in few features, we should be fine with having chrome in the list.
https://github.com/browserslist/browserslist/issues/578
https://github.com/Fyrd/caniuse/issues/2749


notifications: "Mobile notifications always" should be independent of "Mobile notifications for PMs".

Currently "Mobile notifications always" has a dependency on a parent setting.
This setting should actually be something like "Send mobile notifications immediately" and should not be in the "Private messages and @-mentions" section at all.

The main task is to split the setting from it's parent, so that e.g. if you don't get PM notifications but you do get stream mobile notifications, this setting still works. We can independently do the follow-up work of renaming and moving the setting to another part of the settings UI.

This can be fixed in https://github.com/zulip/zulip/issues/10331

Thanks for looking into this! The two features are fairly unrelated; let's keep them separate (e.g. with separate PRs).

There is already an option to enable "mobile notifications" under "stream notifications" section. So I imagine task remains to remove that unnecessary dependency, isn't it ?

Correct.  I believe the backend actually already behaves with the two settings independent (though we'll want to test that); it's just the settings UI that needs to change.

@ruchit2801 is there a PR for this?

Not yet. There was a bit confusion while fixing it. I'll make a PR for this soon. Just for confirmation, we just want to migrate that Mobile notifications for PMs option to Other notification settings, and change its name to send push notifications immediately. I sure will test this feature, if it works on backend.

Yes, and don't change the variable name -- just the title in the UI.

Fixed via #12148.


new website

Todo:

update CONTRIBUTING.md to contrib to the website

Rendered version: https://xtuc.github.io/website-test/

shiny ✨

That's ready to merge, what do you think @maurobringolf?

Cool the website is online: https://webassembly.js.org/


Blank page when running this app

Hello
I am getting a blank page when running this app. I cannot get the pyvista component to display. You had said you got it working on the cloud. May I know how you did that? Thank you!

Hi @wassimj, you can clone this repo and launch it on Streamlit cloud. Here is the app running, and you should get the same:
https://napoles-uach-pyvista-streamlit-app-s9bt3a.streamlitapp.com/
If running locally, please ensure that you have installed the packages in the requirements.txt and packages.txt files.
Let me know if this works for you! Btw, this code first creates a html file that is opened with components.html, so first ensure that this file is available in the same folder as your app.py file.

Hi. When I run your app from the link that you provided, it works. However, when I clone your repo and deploy it on Streamlit Cloud, it gives me a blank page and reports:
/home/appuser/venv/lib/python3.9/site-packages/pyvista/plotting/plotting.py:116: UserWarning:

This system does not appear to be running an xserver.

PyVista will likely segfault when rendering.

Try starting a virtual frame buffer with xvfb, or using

  ``pyvista.start_xvfb()``

  warnings.warn(

Here is the link to the cloned app: https://wassimj-pyvista-streamlit-app-2t4sbj.streamlitapp.com/

It is weird as I just launched the app in Streamlit Cloud to answer you in my previous reply. I'm not sure of what is failing. I think this is more related to Pyvista than to Streamlit. I'll try to make it work and let you know if I have success.

Hey @wassimj there is a new component that works with pyvista:
https://github.com/edsaac/streamlit-PyVista-viewer
hope that helps!

Many thanks. Will try it


⚠ Auth Portal has degraded performance

In a8c07b6, Auth Portal (https://auth.zyradyl.moe) experienced degraded performance:

HTTP code: 523
Response time: 19493 ms

Resolved: Auth Portal performance has improved in f1a82c0 after 5 minutes.


[feature request] Set custom http client for OpenAI

I am creating tests that don't make calls to the LLM by mocking the HTTP client.
The underlying openai client supports passing in an HTTP client as an option, but the wrapper around it does not (it hard codes the options passed in openaiclient.New(options.token, options.model, options.baseURL, options.organization) .
The Go Openai client also supports setting the client using WithHTTPClient, but to use this, the client on the LLM struct would need to be accessible.

Proposed Fix
Make the openai client accessible with a getter GetClient

Hello there!
I've created a pr #223 with added public WithHTTPClient method for OpenAI, hope that suits your needs. Let me know if you have any feedback or suggestions

If I have local-ai node which runs at localhost:8000 and have API compatible with open-ai then I can create new langchain openai client which will use localhost:8000 as baseURL?

Closing as this has merged.
@JackBekket yes, you can simply use the openai.WithBaseURL() option to override the base url.


feat(docker,ci): split prebuilt stage into autoware-core and autoware-universe stages

Description
This PR is the first step in this discussion https://github.com/orgs/autowarefoundation/discussions/4661#discussioncomment-9995806.
The Dockerfile's prebuilt stage will be divided into two stages: autoware-core and autoware-universe.
Additionally, the src-imported stage, which was prepared for vcs import, has now been renamed to rosdep-depend because src is no longer imported via vcs import but simply called COPY.
The current Dockerfile

This PR's Dockerfile

Tests performed
https://github.com/youtalk/autoware/actions/runs/9868168693
Effects on system behavior

Not applicable.
Interface changes

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

It seems like some of the workflows in Autoware.Universe uses prebuilt image. If we are removing them, we should update Autoware.Universe CIs to use devel environment instead.
https://github.com/autowarefoundation/autoware.universe/blob/ea0276acd134a75bc0227aeeb96266c26db7100e/.github/workflows/build-and-test-differential.yaml#L36

@mitsudome-r That's good catch! Since latest-auware-universe tag will be replaced with the equivalent latest-prebuilt tag, I plan to submit a correction PR to https://github.com/autowarefoundation/autoware.universe as soon as this PR is merged and the image is pushed.

I made a PR to resolve the autoware.universe's issue https://github.com/autowarefoundation/autoware.universe/pull/7952.
Once this PR is merged and the image is pushed, I will change the PR to Ready for review.
@mitsudome-r Please review again.

I'm sorry but I send the message to the different PR.
https://github.com/autowarefoundation/autoware/pull/4975#issuecomment-2224953255

@xmfcx @oguzkaganozt @mitsudome-r Thank you for the discussion on the multi-containerization yesterday. Here is the PR for the first step. Please review it.

@youtalk thanks for the updates.
Could you add the following to the autoware/docker/README.md file:
## Images

Images diagram (in mermaid format please)

### base

- imports from X
- used for X
- contains X

### rosdep-depend

...

So we can understand what's happening easily.

@xmfcx t seems there is no de facto standard syntax for writing multi-stage build Dockerfile in Mermaid format. Do you want me to convert something equivalent to https://github.com/patrickhoefler/dockerfilegraph to Mermaid format on my own?

@xmfcx Is it okay to separate the README update and the Dockerfile modification into different PRs? I think the discussion about the format of the README and the discussion about the design of the Dockerfile's multi-stage build are separate issues.

@youtalk I see, I didn't know it was generated by dockerfilegraph, which uses graphwiz, same as what colcon uses to visualize the package dependency graph!
https://github.com/patrickhoefler/dockerfilegraph?tab=readme-ov-file#more-options
Here it has -o svg option, which should output a svg to be version control friendly, we can use that.

Is it okay to separate the README update and the Dockerfile modification into different PRs? I think the discussion about the format of the README and the discussion about the design of the Dockerfile's multi-stage build are separate issues.

That's alright, as long as we have the documentation in sync with the dockerfile.
Right now it is a little bit messy, people need to read through the dockerfile to know what stands for what.

By the way, I need something like this:
https://github.com/osrf/docker_images/tree/master?tab=readme-ov-file#repo-info-3

@xmfcx I will make a PR to write the README. Thank you for you understanding.


Ridiculously enough it's not possible to programmatically enable or disable shuffle / repeat

There are buttons but no public functions. I would assume this is easy to build in, not sure why this is missing.

There is a similar issue being discussed in #225 but as always, the limit of getting things done on an open source project is the developer's time.
If it's truly that easy, maybe submit a pull request to help everyone out? 😃

Of course, I do understand, it’s just an interesting oversight.

This is fixed in the dev branch: https://github.com/521dimensions/amplitudejs/tree/dev


TECH-2005: Add local variable filter callback

@ColinDKelley Resolved comments. FYI: I forced pushed to keep the commit history clean.


Minor improvements

Pass ctx to HTTP calls.

I noticed the library isn't passing the context down to internal methods. This is important since we use ctx for handling deadlines and timeout.
For the user, if they want to cancel the operation if it isn't completed in under 1 second, the code would be:
ctx, cancel := context.WithTimeout(context.Background(), 1*time.Second)
defer cancel()
res, err := db.QueryContext(ctx, stmt, args...)

to fix this, we must pass the ctx to the callSqld method and use that in the http calls.

Add timeout to HTTP calls

The library currently uses the default http package from the stdlib. The calls from this package don't have any timeouts set, so if the server isn't responding, libsql client may get stuck indefinitely. Usually, it is better to set some timeout on http client itself (which will apply to all the calls).
Adding a timeout solves this:
// the http call has to finish in under 60 seconds
// a global variable which all of http package code will use
var HTTPClient = &http.Client{Timeout: 60 * time.Second}

Another alternative is to use hashicorp's cleanhttp package which comes with some sane defaults

I am happy to send a PR to fix these!

@avinassh sorry, missed this, please do send a pull request!

I'm actually working on this change so please don't listen to @penberg :)

Oh, Let me find something else to contribute!

Actually, I won't have time to wrap up this work in the next few days so I think it's best I leave it for you @avinassh :)

I have opened a PR #15 which passes the ctx to http calls. This fixes the first part of the issue.
For the second one, suggest me a safe default timeout to set? How does 120s sound?

Thanks @avinassh. Could you do the same fix for websockets please?

I opened a PR #16 to add changes for websockets and also added timeout for http driver.
Go sql driver now uses ctx for most methods and methods which don't take ctx are deprecated. I believe that should be done here too.

Thanks @avinassh. I think we can close this issue now.


Allow to specify the value of the trainer/global_step metric on W&B during validation

🚀 Feature
Allow to specify the value of the trainer/global_step metric on W&B even during validation, as it is possible during training.
Motivation
The default value for the trainer/global_step metric during validation is defined as the "total validation step":
https://github.com/Lightning-AI/lightning/blob/e7ad151c311890c931aa5ff3df3672fd21fd351c/src/pytorch_lightning/loops/epoch/evaluation_epoch_loop.py#L152
whereas during training the default value is trainer.fit_loop.epoch_loop._batches_that_stepped, even if there are some inconsistencies (see #13752).
The fact that the behaviour of trainer/global_step is different when switching from training to validation, generates graphs like this on W&B:

as well as the fact that W&B complains when trying to use trainer/global_step as x axis because it's not monotonically increasing:

For training it's possible to set a custom value for training/global_step by using self.log("step", ...) during the training step. For validation, there's no such possibility.
I understand that if one logs using on_step=True during validation, it's important to keep track of the different validation steps. But if one logs using on_step=False and on_epoch=True, it would be useful to link the val metric to the current training step instead of the total validation step.
Pitch
One can set a custom value for training/global_step even during validation.
Alternatives
Another possibility could be to log a different metric for validation, e.g. trainer/validation_global_step and to use that as default x axis as it is done with trainer/global_step here:
https://github.com/Lightning-AI/lightning/blob/6df6deac8fdf0c44b509d531441b4f7e446de6b4/src/pytorch_lightning/loggers/wandb.py#L396-L397

My bad, the issue persists only when logging with on_step=True and thus is a minor problem.
When logging with on_epoch=True (which is the default during validation), the behaviour is the same as during training, i.e. it uses the current training step:
https://github.com/Lightning-AI/lightning/blob/759e89df21684277da996dd25781dee7f21e1b1c/src/pytorch_lightning/trainer/connectors/logger_connector/logger_connector.py#L136-L142
However, I believe that the alternative solution outlined above could be valid to avoid some confusion.

Hi @andreapesare ! Thanks  for pointing this out. Would it be possible to get some code on how to reproduce the global_step plot that you showed above?

Hi @manangoel99 ! This code should reproduce a similar plot, when using step as x axis:
import os
from typing import Optional

import pytorch_lightning as pl
import torch
import torch.nn.functional as F
from pytorch_lightning.loggers.wandb import WandbLogger
from pytorch_lightning.utilities.types import STEP_OUTPUT
from torch import nn
from torch.utils.data import DataLoader
from torchvision import transforms
from torchvision.datasets import MNIST

class LitModel(pl.LightningModule):
    def __init__(self):
        super().__init__()
        self.l1 = nn.Linear(28 * 28, 10)

    def forward(self, x):
        return torch.relu(self.l1(x.view(x.size(0), -1)))

    def training_step(self, batch, batch_idx):
        x, y = batch
        y_hat = self(x)
        loss = F.cross_entropy(y_hat, y)
        self.log("train/loss", loss)
        return loss

    def validation_step(self, batch, batch_idx) -> Optional[STEP_OUTPUT]:
        x, y = batch
        y_hat = self(x)
        loss = F.cross_entropy(y_hat, y)
        self.log("val/loss", loss, on_step=True, on_epoch=False)
        return loss

    def configure_optimizers(self):
        return torch.optim.Adam(self.parameters(), lr=0.02)

train_loader = DataLoader(
    MNIST(os.getcwd(), download=True, train=True, transform=transforms.ToTensor())
)
val_loader = DataLoader(
    MNIST(os.getcwd(), download=True, train=False, transform=transforms.ToTensor())
)
logger = WandbLogger(project="mnist-example")
trainer = pl.Trainer(
    max_epochs=10,
    limit_train_batches=10,
    limit_val_batches=10,
    log_every_n_steps=1,
    logger=logger,
)
model = LitModel()

trainer.fit(model, train_dataloaders=train_loader, val_dataloaders=val_loader)

Here the plot that I get running the code above:

Thanks @andreapesare ! Looking into it


[BEAM-5605, BEAM-2939] Add support for FnApiDoFnRunner to handle split calls.

The next step is to plumb the split request to the BeamFnDataReadRunner which will forward it to the FnApiDoFnRunner.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @ihji @boyuanzz

CC: @youngoli

Run Java PreCommit

Run RAT PreCommit


Improved logging/debugging

When something crashes in the XSLT rendering, it is not possible to see which line in the XSLT that caused it, or why. Could this info be passed into the logs? That would improve debugging in the RSS app since it relies on pretty complex setups and mappings and needs to be debugged often. Bouvet and others also have problems with this.

Sure @aro - Easiest is to start by cloning the code for app-rss on our Github, with it you have a semi-complex XSLT that is very prone to crashing if the data sent in is wrong compared to the xpath's (to my understanding).
After that, use this Content Type to connect to. I think the problem is that the XSLT expects one line of data for Author, but it gets multiple. But just guessing here since customer didn't see any error messages.
<content-type>
<display-name>Blog - Classic</display-name>
<super-type>base:structured</super-type>
<form>
<input name="image" type="ImageSelector">
Main image
<config>
<allowPath>${site}/*</allowPath>
</config>
</input>
<input name="cinemagraphics" type="ImageSelector">
Cinemagraphics
<config>
<allowPath>${site}/*</allowPath>
</config>
</input>
<input name="authors" type="ContentSelector">
Authors
<occurrences minimum="0" maximum="0"/>
<config>
<relationship-type>system:reference</relationship-type>
<allow-content-type>person</allow-content-type>
<allowPath>${site}/*</allowPath>
</config>
</input>
<input name="heading" type="TextLine">
Heading
<occurrences minimum="1" maximum="1"/>
</input>
<input name="lead" type="TextArea">
Lead text
</input>
<input name="body" type="HtmlArea">
Body text
</input>
<field-set name="meta">
Info fra den gamle bloggen
<items>
<input name="oldLink" type="TextLine">
Gammel Link
<help-text>F.eks https://enonic.com</help-text>
</input>
<input name="oldDate" type="DateTime">
Gammel publiseringsdato/tid YYYY-MM-DD tt:mm
</input>
</items>
</field-set>
</form>
</content-type>

According to readme/docs to RSS App you need to setup some things. A Page Template using the page controller the app ships with, and creating a RSS content with the following config. You can skip exclude and include path config:

So far all errors have been a matter of trial and error to fix.
This feature request comes from ticket #2276 in our support.


This code seems not to work with rescript 11.beta.2 and 3

I get the following error after newly adding this package to a new project:
><EMAIL_ADDRESS>build /home/jasoons/Documents/code/envio/envio-operator
> rescript build

Dependency on @ryyppy/rescript-promise
rescript: [5/5] src/Promise.cmj
rescript: [7/7] install.stamp
Dependency on rescript-nodejs
rescript: [58/118] src/Module-NodeJs.cmj
FAILED: src/Module-NodeJs.cmj

  We've found a bug for you!
  /home/jasoons/Documents/code/envio/envio-operator/node_modules/.pnpm/rescript-nodejs@14.4.0/node_modules/rescript-nodejs/src/Module.res:1:9-19

  1 │ include Node_module
  2 │

  The module or file Node_module can't be found.
  - If it's a third-party dependency:
    - Did you list it in bsconfig.json?
    - Did you run `rescript build` instead of `rescript build -with-deps`
      (latter builds third-parties)?
  - Did you include the file's directory in bsconfig.json?

rescript: [79/118] src/Buffer-NodeJs.cmj
FAILED: src/Buffer-NodeJs.cmj

  We've found a bug for you!
  /home/jasoons/Documents/code/envio/envio-operator/node_modules/.pnpm/rescript-nodejs@14.4.0/node_modules/rescript-nodejs/src/Buffer.res:1:10-20

  1 │ type t = Node.buffer
  2 │ open Js.TypedArray2
  3 │

  The module or file Node can't be found.
  - If it's a third-party dependency:
    - Did you list it in bsconfig.json?
    - Did you run `rescript build` instead of `rescript build -with-deps`
      (latter builds third-parties)?
  - Did you include the file's directory in bsconfig.json?

rescript: [97/118] src/Assert-NodeJs.cmj
FAILED: cannot make progress due to previous errors.
Failure<EMAIL_ADDRESS>Location: /home/jasoons/Documents/code/envio/envio-operator/node_modules/rescript-nodejs/lib/bs
 ELIFECYCLE  Command failed with exit code 1.

I'll clone locally and investigate a bit - seems strange - but I also don't know what Node_module is.

Bingo... https://github.com/rescript-lang/rescript-compiler/pull/6285

Oh good find!
We could perhaps just add types to this project, but that would then make it incompatible with ReScript 10.

Yeah, maybe a major version bump, and it requires rescript 11 or higher?

Bundling my own types is the recommended solution. And yes it will need a new major.

@JasoonS As a temp solution you can use the version from my PR:
    "rescript-nodejs": "github:DZakh/rescript-nodejs#3c29dcd",

Cool, thanks - beat me to it @DZakh 💪


Deprecation in 'createStackNavigator': 'transitionConfig' is removed in favor of the new animation APIs

Version
Tell us which versions you are using:

react-native-router-flux v4.3.1
react v17.0.1
react-native v0.64.0

Expected behaviour
Should not recieve below warning.
Deprecation in 'createStackNavigator': 'transitionConfig' is removed in favor of the new animation APIs
Actual behaviour
Following WARNING shown in console.
Deprecation in 'createStackNavigator': 'transitionConfig' is removed in favor of the new animation APIs

any idea how to fix this ?

Same here, any solution?

I have made these changes in Store.js and I no longer get and warning and mye cardStyle started to work again
This is the patch-file (also include a fix regarding the HeaderBackButton):
diff --git a/node_modules/react-native-router-flux/src/NavBar.js b/node_modules/react-native-router-flux/src/NavBar.js
index bb154e0..b4827b5 100644
--- a/node_modules/react-native-router-flux/src/NavBar.js
+++ b/node_modules/react-native-router-flux/src/NavBar.js
@@ -28,7 +28,7 @@ export function BackButton(state) {
   // returning react-navigation's back button well styled for ios and android if rnrf4-supported customization
   // is not required
   if (!state.backButtonImage) {
-    return <HeaderBackButton onPress={onPress} title={state.backTitle} titleStyle={textButtonStyle} tintColor={tintColor} truncatedTitle={state.truncatedTitle} />;
+    return <HeaderBackButton onPress={onPress} label={state.backTitle} titleStyle={textButtonStyle} tintColor={tintColor} truncatedTitle={state.truncatedTitle} />;
   }

   const text = state.backTitle ? <Text style={textButtonStyle}>{state.backTitle}</Text> : null;
diff --git a/node_modules/react-native-router-flux/src/Store.js b/node_modules/react-native-router-flux/src/Store.js
index 82eed18..3c15e69 100644
--- a/node_modules/react-native-router-flux/src/Store.js
+++ b/node_modules/react-native-router-flux/src/Store.js
@@ -110,8 +110,8 @@ function getProperties(component = {}) {
   return res;
 }
 function createTabBarOptions({
-  tabBarStyle, activeTintColor, inactiveTintColor, activeBackgroundColor, inactiveBackgroundColor, showLabel, labelStyle, tabStyle, ...props
-}) {
+                               tabBarStyle, activeTintColor, inactiveTintColor, activeBackgroundColor, inactiveBackgroundColor, showLabel, labelStyle, tabStyle, ...props
+                             }) {
   return {
     ...props,
     style: tabBarStyle,
@@ -124,7 +124,7 @@ function createTabBarOptions({
     tabStyle,
   };
 }
-function createNavigationOptions(params) {
+function createNavigationOptions(params, transitionConfig) {
   const {
     type,
     cardStyle,
@@ -202,6 +202,7 @@ function createNavigationOptions(params) {
       headerTitle: getValue(navigationParams.renderTitle || renderTitle || params.renderTitle, state),
       headerTitleStyle: headerTitleStyle || titleStyle,
       title: getValue(navigationParams.title || title || getTitle, state),
+      transitionConfig: transitionConfig,
     };

     const NavBarFromParams = navigationParams.renderNavigationBar || navigationParams.navBar;
@@ -864,9 +865,7 @@ export default class NavigationStore {
       mode,
       initialRouteParams,
       initialRouteName,
-      ...commonProps,
-      transitionConfig,
-      navigationOptions: createNavigationOptions(commonProps),
+      navigationOptions: createNavigationOptions(commonProps, transitionConfig),
     });
   };

As mentioned above, react-navigation has removed the transitionConfig prop. However the new version provides a new API to customize the animation navigation.
if you, like me, just want to have the iOS animation on Android, you should use TransitionPresets.SlideFromRightIOS from react-navigation-stack like <Stack key="root"  {...TransitionPresets.SlideFromRightIOS}>. Other transition configs are also available via TransisitionsPresets in the react-navigation docs.
As RNRF is built on react-navigation,  you can use the whole API animation explained in react-navigation docs and pass it as prop to <Stack />.
If you want to build your own animation you can use the cardStyleInterpolator prop but it receives different parameters comparing to the old transitionConfig.

@yberstad How do I use your patch file?

@JMRMEDEV, I have used the patch-package, I think the readme is quite good, https://github.com/ds300/patch-package#readme.
But if you have problems using the patch, please reach out again, and I'll try to help.

Hello,
Did someone solve this problem ?


Change scanner layout

Good morning, it is possible to change the layout of the scanner, to add a logo.

Yes this is certainly possible.You need to create your own camera overlay using css and html inside the scanner-ui div.
https://github.com/capacitor-community/barcode-scanner/blob/main/examples/scan-area-layout/index.html


Commit Analyzer Not Working

@mattfordham think you fellows have always helped us get the commit analyzer back up when we've seen issues.  Who can @jim-phillips work w/ to learn more about it so we can self manage?
Thanks,
Rich

I'd be happy to help. Feel free to have @jim-phillips reach out via email<EMAIL_ADDRESS>

Or here, if that's preferable


How to find the token count of a prompt using meta/llama2-70b model

Is tiktoken supports meta/llama2-70b?
I want to find the token count of the prompt before passing the prompt to a meta/llama2-70b model
So how to do this with  tiktoken
import tiktoken
enc = tiktoken.get_encoding("meta/llama2-70b")

is this possible?

Meta's models are tokenized differently from OpenAI's. tiktoken doesn't support non-OpenAI models.


GetQueueURL should return url containing aws id, not queue keyword - fixes #421

Is writing a test possible? :)

Is writing a test possible? :)

there is one already, but the check wasn't specific enough. is it ok now?

there is one already, but the check wasn't specific enough. is it ok now?

Yes, looks good. One more question though - does this change the default behavior in some way? That is, will the queue urls change if somebody used the default configuration?

Yes, looks good. One more question though - does this change the default behavior in some way? That is, will the queue urls change if somebody used the default configuration?

Yes, they will change, because the default configuration contains some aws id. However, both queue/<queue_name> and <aws_id>/<queue_name> urls work for the existing endpoints, so technically the change doesn't break compatibility.

Yes, they will change, because the default configuration contains some aws id. However, both queue/<queue_name> and <aws_id>/<queue_name> urls work for the existing endpoints, so technically the change doesn't break compatibility.

Ok, we'll release it as version 1.1 then :)

Ok, we'll release it as version 1.1 then :)


PlaceHolder text

Description
The placeholder text reads Enrollment number, but the teachers might not particularly have enrollment number though. They might have employee Number.

change placeholder text from "Enrollment no." to User Name in Auth
change Select box title "Teachers" to " Teachers and Staff"

Screenshots

Additional information
No response

I think it will work...

Sure, Go ahead ✅

I am having net issues...
I have already committed....
What u ask me to do....
Can u plz check the code once...

Can you put the screenshot of the changes you made, here?

Hi @Sohelahmed-molla, Great to see you fixed the first Bug in this project and made your first contribution.
You can create a PR with this screenshot. If you are having trouble completing the PR template, make sure to check out any previously closed PR in this repo which contains the completed format of completing the PR template.
Great Work,
Pritam


AUR package

Hi!
Just packaged guess-that-lang in the AUR.

Thank you! I don't know anything about listing stuff on package providers like that, but won't that need to be updated every version?

Well yeah it is supposed to remain up-to-date with the upstream source with some margin!

That might be hard, because I publish versions fairly frequently and don't want you to have to update it on AUR everytime

Closing this because there's nothing that needs to be fixed


Step 1: Change Word Cloud operator to incrementally compute data

Step 1 of the Word Cloud incrementalization project.
We want to change word cloud operator to be incremental. specifically:
i) change word cloud partial operator to output incremental results after a batch
ii) change word cloud final operator to output current snapshot upon receiving a new batch update from partial opeartor
iii) change the sink operator: make the sink operator discard the previous snapshot and stores the new snapshot for every input

done


New functions for NPC

Added setSchedule, hasSchedule, setState and getState functions.

E2 supports enums right? Don't need to use strings

E2Lib.registerConstant, also don't use C style comments.

I think it's better not to have too many constants just use strings as in npcDisp and npcRelationship functions.

Also added way to give npc other weapons than HL2 weapons.

Can you move your string lookup table creation outside of their respective functions? Recreating the table everytime the function is called is wasteful to cpu.

Moved my "string lookup table creation" out of functions


Removing unnecessary properties from TeradataLinkedService

Remove obsolete properties from TeradataLinkedService for Azure Data Factory

Can one of the admins verify this patch?

Hi @adiedrich, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

retest this please

retest this please

@azuresdkci add to whitelist


feat(topnav): add Discuss, remove Media

This PR aims to address immediate need raised in https://github.com/ipfs/website/issues/236#issuecomment-484010305:

We should have a prominent HOW TO GET HELP item that send people to discuss. While there is extensive documentation on how to contribute and help others, there is no reference to how actually get help from others.

Looks like this:

https://discuss.ipfs.io/ is a good async place to direct people at until we have a proper
"Community" / "Help" /  "Comms" landing page, similar to "Teams"

"Media" should not be in the top nav, it was not updated for a long time
and gives bad impression of stale development.

Supersedes https://github.com/ipfs/website/pull/276 and Closes https://github.com/ipfs/website/issues/236

SGTM but I'd rather have a "Help" or "Community" landing page (not sure how much work that is).

Yup, this is just a temporary fix until proper landing page is added.
@olizilla ok to merge this?

I'd suggest we use Discuss or Forum for the links, but not both. Forum gets my vote because it's descriptive to what it is and not related to the product name.
@Stebalien: I agree this should be a page, happy to add that task to my list.
Otherwise, LGTM :shipit:

Forum or Help

Let's go with Forum for now, and we'll look at adding a help/community page next.