[Question] Exposing services in single-machine cluster

Describe scenario
Running a single-machine AKS Edge k3s cluster on a Intel i7-based machine running Windows 10, connected to Azure Arc.
Question
Is an external load balancer required for exposing services to the network? Currently, when setting up services as load balancer, the external IPs allocated are on subnet 192.168.0.x, which I assume are for the internal (cluster) network, while the network interface of the machine is connected to subnet 192.168.150.x.

Hi @dnarh,
Thanks for reaching out.  Your current understanding is correct, and when you use the default networking options (using an Internal virtual switch),  services will be exposed to the internal network and not accessible by external devices.
There are two alternatives to access services from external devices:

Keep the Internal Switch configuration and static IP deployments/services and then use port forwarding to that static IP. For example, imagine your services has the <IP_ADDRESS> address, and you want to forward the port 8080, then on the Windows host OS you should run the following command: netsh interface portproxy add v4tov4 listenport=8080 listenaddress=<IP_ADDRESS> connectport=8080 connectaddress=<IP_ADDRESS>. For more information, check https://learn.microsoft.com/en-us/windows-server/networking/technologies/netsh/netsh-interface-portproxy.

Deployment using an External virtual switch. When deploying the AKS EE single-node cluster, use an external virtual switch. When doing this, your node will connect to your external network and services will be exposed to external devices.

Hope this helps.
Thanks,
Francisco

Thanks for the reply @fcabrera23.
Alternative 1 works. However, doing this means that all external IPs in the cluster will have to be forwarded to the IP of the host.
Therefore, alternative 2 seems like the better option, but when trying to deploy a single-node cluster with an external virtual switch, I end up with the same error as #25.

Hi @dnarh,
Sorry, I had to update my response as I forgot to mention that for the external switch you need to create a scalableCluster and keep it to one single node, instead of singleNode cluster.
Thanks,
Francisco


add a dsc file

you could publish the dsc file of  ungoogled
for   make  it  useful  at online compile services

Not a bad idea.


Drivetrain file has over 10 major problems

When using the 2024 libraries, WPI vscode warn about multiple problems in the Drive train file in the master branch
the one error is related to path planner on line 137:
the method configureRamsete(Supplier, Consumer, Supplier, Consumer, ReplanningConfig, BooleanSupplier, Subsystem) in the type AutoBuilder is not applicable for the arguments (Supplier, Consumer, Supplier, Consumer, ReplanningConfig, Drivetrain)
All of the warnings are in relation to the recent deprecation of the motor controller group type in WPIlib's current version (2024)

We will have to look into these!
When we were working on things, we were on a beta release of wpilib, as the official 2024 releases hasn't been, well, released yet, so warnings and such were likely ignored, knowing things may still work when using the official 2024 releases.

Freshly cloned. I'm having a similar issue. Looks like it's not able to pull the path planner dependency on my machine
Could not determine the dependencies of task ':jar'.
> Could not resolve all files for configuration ':runtimeClasspath'.
   > Could not find com.pathplanner.lib:PathplannerLib-java:2024.0.0-beta-6.2.
     Searched in the following locations:
       - file:/C:/Users/Public/wpilib/2024/maven/com/pathplanner/lib/PathplannerLib-java/2024.0.0-beta-6.2/PathplannerLib-java-2024.0.0-beta-6.2.pom
       - https://frcmaven.wpi.edu/artifactory/vendor-mvn-release/com/pathplanner/lib/PathplannerLib-java/2024.0.0-beta-6.2/PathplannerLib-java-2024.0.0-beta-6.2.pom
       - https://3015rangerrobotics.github.io/pathplannerlib/repo/com/pathplanner/lib/PathplannerLib-java/2024.0.0-beta-6.2/PathplannerLib-java-2024.0.0-beta-6.2.pom
       - https://repo.maven.apache.org/maven2/com/pathplanner/lib/PathplannerLib-java/2024.0.0-beta-6.2/PathplannerLib-java-2024.0.0-beta-6.2.pom
     Required by:
         project :


BUG FIX: provide nil check in Transaction#block_number

BUG: calling #block_number on a transaction that has just been
committed to the blockchain causes Utility#from_hex to raise an
argument error exception
CAUSE: because the transaction is new, its blockNumber value is
nil, thus when I try to call from_hex #to_i is called on
nil, which fails
FIX: provide a nil check in Transaction#block_number to avoid
calling Utility#from_hex if blockNumber is nil

NOTE:

I have confirmed that this works locally, but have not provided a
test for the patch, as the test harness for the project appears to
be skeletal at the moment. Happy to provide one with guidance from
upstream folks if the lack of testing is a blocker to merging.

ping @izetex -- hope this helps! please let me know if there are any contributor guidelines you'd like me to follow that i have not. :)

hi @izetex -- have you had a chance to look at this yet?


351 fix velocity in solo mod

New feature

Create new system ApplyInputDelay to update velocity

Fixed feature

Use ApplyInputDelay to fix velocity update in solo mod

Codecov Report

Merging #352 (ea4108e) into master (4cfe46e) will decrease coverage by 0.04%.
The diff coverage is 0.00%.

:exclamation: Current head ea4108e differs from pull request most recent head 3c3f3bc.  Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


S3 | Create a Base Image Queue API

Story

As a developer
I need a bootstrapped Image Queue API
So that I can start writing the next API for our application

Acceptance Criteria

An image-api folder
A basic npm package.json with express, mongodb, mocha, should, and body-parser installed
A basic app.js file like the other APIs
A db/index.js like the other APIs
an alive route like the other APIs

@mclark1996

S3 #48


Core 2 Quad Q6600 reports HTT bit to 1.

While CPUID.01h.EDX[28], the HTT bit, denotes the HyperThreading Technology bit, the Q6600 returns to support it, while both the Intel's Ark website and Speccy repports otherwise.
So it's making me think if I'm missing something here.

Debugging information:
|   Leaf   | Sub-leaf | EAX      | EBX      | ECX      | EDX      |
|----------|----------|----------|----------|----------|----------|
|        0 |        0 |        A | 756E6547 | 6C65746E | 49656E69 |
|        1 |        0 |      6FB |  2040800 | 80006381 | BFCBFBFF |
|        2 |        0 |  5B0B101 |   5657F0 |        0 | 2CB43049 |
|        3 |        0 |        0 |        0 |        0 |        0 |
|        4 |        0 |  C000000 |        0 |        0 |        0 |
|        5 |        0 |        0 |        0 |        0 |        0 |
|        6 |        0 |        1 |        2 |        1 |        0 |
|        7 |        0 |        0 |        0 |        0 |        0 |
|        8 |        0 |        0 |        0 |        0 |        0 |
|        9 |        0 |        0 |        0 |        0 |        0 |
|        A |        0 |        0 |        0 |        0 |        0 |
| 80000000 |        0 | 80000008 |        0 |        0 |        0 |
| 80000001 |        0 |        0 |        0 |        1 | 20100800 |
| 80000002 |        0 | 65746E49 | 2952286C | 726F4320 | 4D542865 |
| 80000003 |        0 | 51203229 | 20646175 | 20555043 | 51202020 |
| 80000004 |        0 | 30303636 | 20402020 | 30342E32 |   7A4847 |
| 80000005 |        0 |        0 |        0 |        0 |        0 |
| 80000006 |        0 |        0 |        0 | 10008040 |        0 |
| 80000007 |        0 |        0 |        0 |        0 |        0 |
| 80000008 |        0 |     3024 |        0 |        0 |        0 |
EBP=18FDE8   ESP=18FD84   EDI=18FE80   ESI=0

Update: I tried with core.cpuid.hyperThreading() with it reports false, so there is some detail I'm missing at this moment.

HTT bit can design multi-core design


add progress bar to generate union command in datasets-fs

progress bar has been added to generate distinct but not generate union

done


WebHook Start project does not run on directly from GitHub

Could not get the webhook project to run from github
Created a fork and made the fixes
https://github.com/plaid/tutorial-resources/pull/27

Missing package
Incorrect require command
I think this is for older node versions but the ? caused an error and had to change to a 2-step compare.

closing this out as per discussion on the linked PR the cause was incompatible version of Node (12) being used that has a different interface for the fs promises API:
https://github.com/nodejs/node/issues/35740


[SPARK-6216] [PySpark] check python version of worker with driver

This PR revert #5404, change to pass the version of python in driver into JVM, check it in worker before deserializing closure, then it can works with different major version of Python.

cc @JoshRosen

Merged build triggered.

Merged build started.

Test build #32859 has started for   PR 6203 at commit 47c6278.

LGTM aside from minor suggestion.

Test build #32859 has finished for   PR 6203 at commit 47c6278.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32859/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #32870 has started for   PR 6203 at commit 6ce5096.

Test build #32870 has finished for   PR 6203 at commit 6ce5096.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32870/
Test FAILed.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #32883 has started for   PR 6203 at commit b8fb76e.

Test build #32883 has finished for   PR 6203 at commit b8fb76e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/32883/
Test PASSed.

Merged build finished. Test PASSed.

LGTM as well; this seems like a straightforward fix and will be useful once more people start playing around with Python 3.

I'm going to merge this into master and branch-1.4 (1.4.0).  Thanks!


Map button to a key combo

Is it possible to assign multiple keys to a mouse button? For example Button 5 = LeftCtrl + C to copy

I forgot to answer you question, sorry ^^'
Technically, it seems possible on some devices but this is never used by the SteelSeries Engine (when you setup a combo, it does it by software), so I will probably not support this in Rivalcfg, sorry.


Python gRPC asynchronous bidirectional client doesn't wait for server

I'm making a birectional call to a gRPC server. Python gRPC client doesn't wait for the server response and exits prematurely. Java gRPC client works as expected and I receive the response. I reproduced the issue using official example code: Client code, Server code and rest of the files
Here is the output for  await guide_route_chat(stub):
-------------- RouteChat --------------
Sending First message at
Sending Second message at longitude: 1

Sending Third message at latitude: 1

Sending Fourth message at
Sending Fifth message at latitude: 1

Received message First message at
Received message Third message at latitude: 1

Process finished with exit code 0

As you can see I only receive response for 1st and 3rd message.
Requirements:
grpcio==1.46.0
grpcio-tools==1.46.0

I found a similar but older issue here.

The output is correct for the official example. Sorry for the confusion. Closing the issue.


No explicit tests for PRGAViaPhaseGradient

The documentation and testing is very light for this bloq.  Can this be expanded? it would seem it only has system testing via state-prep via rotations.
Reference:
https://github.com/quantumlib/Qualtran/blob/main/qualtran/bloqs/state_preparation/state_preparation_via_rotation_test.py
contains no tests for the mentioned bloq.

@Vicara12

@ncrubin I added a test on PR #846, which contains both an example of usage and also the formula for converting the desired angle into the value to be loaded in the QROM (which is what the bloq receives). Let me know if you have further feedback!


Upgrades Kafka version and Spring-kafka-test version to latest suggested by whitesource

Signed-off-by: Darshit Chanpura<EMAIL_ADDRESS>Description
Upgrades Kafka and spring-kafka-test jar versions

Enhancement
Failing Whitesource check

Issues Resolved
https://github.com/opensearch-project/security/issues/1564
Is this a backport? If so, please add backport PR # and/or commits #
Testing
[Please provide details of testing done: unit testing, integration testing and manual testing]
Check List

[ ] New functionality includes testing
[ ] New functionality has been documented
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1598 (f38c200) into main (7592846) will decrease coverage by 0.18%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1598      +/-   ##
============================================
- Coverage     64.57%   64.39%   -0.19%
- Complexity     3215     3217       +2
============================================
  Files           247      247
  Lines         17351    17342       -9
  Branches       3082     3068      -14
============================================
- Hits          11205    11167      -38
- Misses         4597     4624      +27
- Partials       1549     1551       +2

Impacted Files
Coverage Δ

...ava/com/amazon/dlic/auth/ldap2/MakeJava9Happy.java
8.69% <0.00%> (-34.79%)
:arrow_down:

...org/opensearch/security/rest/TenantInfoAction.java
77.94% <0.00%> (-10.30%)
:arrow_down:

...com/amazon/dlic/auth/ldap2/PrivilegedProvider.java
44.26% <0.00%> (-6.56%)
:arrow_down:

...ic/auth/ldap/backend/LDAPAuthorizationBackend.java
53.59% <0.00%> (-4.36%)
:arrow_down:

.../org/opensearch/security/support/ConfigHelper.java
80.39% <0.00%> (-1.97%)
:arrow_down:

...zon/dlic/auth/ldap2/LDAPAuthorizationBackend2.java
28.35% <0.00%> (-0.38%)
:arrow_down:

...dlic/auth/http/saml/AuthTokenProcessorHandler.java
46.99% <0.00%> (-0.29%)
:arrow_down:

...ch/security/securityconf/DynamicConfigFactory.java
60.92% <0.00%> (-0.26%)
:arrow_down:

...earch/security/resolver/IndexResolverReplacer.java
63.52% <0.00%> (-0.11%)
:arrow_down:

.../org/opensearch/security/auth/BackendRegistry.java
59.26% <0.00%> (-0.11%)
:arrow_down:

... and 8 more

Continue to review full report at Codecov.

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


Fix Daisy Clock

The new daisy clock was missing a line in metadata.json to make is actually usable as a clock, as it stands you can only open it as an app from the launcher but not set it as a clock in the settings.

Thanks!


Smart Select and OCR text Extraction

Is your feature request related to a problem? Please describe.
This is a genuine problem , many times while storing some important info that comes on screen user either manually note it out ,take a screenshot for manual noting down later , but with smart select feature user can extract text present in screen by selecting portion.
Describe the solution you'd like
user has to follow 3 steps

Take a screenshot of the portion you want
Give screenshot as input
OCR operations take place over screenshot and text is extracted

Describe alternatives you've considered
Alternate solution for future use , i am planning user will come use smart select , select portion he want , and text would be extracted there would no need to take ss , and give input follow this process (future solution)
Approach to be followed (optional)

user will take screenshot
give path of screenshot , OCR operation takes place over image and text etracted will be stored
OCR software  used will be Tesseract

Additional context
Add any other context or screenshots about the feature request here.

Want to work on this for GSSOC'24.

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

Hey its not related to frontal face operation.


Update Initial Funds Page

Updated with information about contributors, tasks, etc... https://thenewboston.com/guide/initial-funds

I'd like to take a crack at this, but see where overall documentation needs refactoring at some point. There are sections that are repetitive, e.g. "Blocks" is mentioned in Guides, Bank API, Validator API. Validator has multiple sections, etc.
@buckyroberts or @angle943 is there anything else I need to know before adding information about "Contributors and Tasks"? What else would you like to see here?


Dockerized installer for korifi

Ship a docker image that creates a kind cluster and runs deploy on kind
Alternatively ship a job definition so that users can create a kind, apply the job and it would install korifi
Other ideas are welcome

[ ] Get push access to cloudfoundry/korifi-installer
[ ] Modify the release job to find the latest release tag (so that it always installs latest release)
[ ] Create a pipeline job that builds and pushes the korifi-installer image (to be triggered by korifi)
[ ] Modify the release job to include the installer job yaml as an asset. It is important that we pin the image version to a particular sha to make it immutable. This means we will have to rebuild the image in the release job
[ ] Update the INSTALL.kind.md to point to release asset so that users don't have to clone the repo in order to run the installer. See article for linking to an asset from latest release
[ ] Release v0.9.1


fix(node): stripe bom

fix #18911
Description
Fix package.json BOM handling in loadPackageData

Thank you for the PR! Would you also add a test case in playground/resolve/package.json?

of course.


New org user (need api info)

New User Page

Input for new user's email address
Radio button to select role (user or admin).
Text explaining how the user will be added. In the mockup I have an example, but I don't know if that's how it will actually work. TBD.
Cancel and add user return you to the list of users.

Update for the last page of that mockup:
If you input the email of a user that is not signed up, then click "Add user to organization" show an error message below the input saying that the user does not exist.
If the user DOES exist, show a toast notification saying that they were successfully added, and clear the input.
You can use the dismissable MUI alert component https://mui.com/material-ui/react-alert/#actions
I've also added a "back to users" link which will take you back to the list of users and updated the page title and button text.


breaking: remove slot

Resolves #567

Forking its-fine and making the APIs ref compatible
removing the marker element and passing the parent/container ref instead

Status

[ ] Code changes have been tested against prettier, or there are no code changes
[ ] I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

[ ] This PR changes the codebase

[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[ ] This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

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

Ahh, it's getting messy because of the v3 rebase!

Ahh, it's getting messy because of the v3 rebase!

Is it cool, now? Can I help?

Is it cool, now? Can I help?

Not yet, but for now let's focus on the implementation, I'll let you know for sure. Thank you so much.

Is it cool, now? Can I help?

Not yet, but for now let's focus on the implementation, I'll let you know for sure. Thank you so much.

My pleasure!


Initial checkin of the setup ops guide. (#2078)

(cherry picked from commit 3b529341a1c48577ac163d5a57c345373d7ea4f3)

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: geeknoid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [geeknoid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


CNN files migration from cats-vs-dogs to cats-dogs_demo issue

Hello
I try to play with a "cat-dogs" example. I managed to train, quantize, evaluate and generate C code. The code works perfectly with sample data (test is passed on board).
On the other hand, I compile the cat dogs demo that uses the same network but also uses the onboard camera, which makes it more fun. I had tested the demo with images of cats and dogs on my computer screen and it works just amazing.
The problem arrives when I try to combine the two projects. It's to say I copy cnn.h, cnn.c, weights.h, and logs to the cats-dogs_demo folder from the generated previously cats-vs-dogs folder. The board reacts to button press and probably takes a picture, but CNN always gives the same output.
My question is: what is the difference between cats-vs-dogs and cats-dogs_demo examples on the CNN level (is it used differently)?
Thank you in advance for your answer!

The issue was solved by adding the --fifo key during C code generation


deepstream.io + nodejs + azure = uws error

Error: Compilation of µWebSockets has failed and there is no pre-compiled binary available for your system. Please install a supported C++11 compiler and reinstall the module 'uws'.
at e (D:\home\site\wwwroot\node_modules\deepstream.io\node_modules\uws\uws.js:31:19)
at Object. (D:\home\site\wwwroot\node_modules\deepstream.io\node_modules\uws\uws.js:35:3)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (D:\home\site\wwwroot\node_modules\deepstream.io\src\message\uws-socket-wrapper.js:5:13)

Hey,
Do you have node-gyp installed correctly on your computer? That tends to be in the initial issue usually!
Cheers,
Yasser

@yasserf, this works fine on my local system. getting this error when i deployed to azure app service. i don't have access to the VM, but from the app settings i got to know it supports node js 6.9.1 out of the box so i guess node-gyp must have been there too?

Afraid not - node gyp (and Python 2.x which it requires) need to be
installed explicitly on windows. Would it not be possible for you to use
the executable?
2017-07-31 19:17 GMT+05:30 dsaiju<EMAIL_ADDRESS>
@yasserf https://github.com/yasserf, this works fine on my local
system. getting this error when i deployed to azure app service. i don't
have access to the VM, but from the app settings i got to know it supports
node js 6.9.1 out of the box so i guess node-gyp must have been there too?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/deepstreamIO/deepstream.io/issues/768#issuecomment-319071799,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABbx5WNUb2zwKcuAk2Skm9v40U0bnn0Zks5sTdrogaJpZM4On8GN
.

@WolframHempel, i used kudu console to fetch the list of processes running on the VM and i could see an entry 'Python27' but nothing for gyp. does python27 mean node-gyp is installed already?
this link also says node-gyp is supported: https://feedback.azure.com/forums/169385-web-apps/suggestions/6573329-support-for-node-gyp-in-nodejs-applications

in the meantime i tried it on azure service fabric and facing a different problem. basically everything works fine on local system since my host is 'localhost' in both server.js side <<new DeepstreamServer(host, port)>> as well as in client.html side <<deepstream('localhost:6020').login({}, ...)>>. but once i move to cloud, getting below error:
WebSocket connection to 'ws://######.cloudapp.azure.com:6020/deepstream' failed: Error in connection establishment: net::ERR_CONNECTION_TIMED_OUT
i've played with 'localhost' and '######.cloudapp.azure.com' in server and client files in all combinations but can't seem to make it work. really want to add deepstream to our tech stack either as an azure app service or an azure service fabric, but stuck so far :(

might be worth trying to use <IP_ADDRESS> as your host in the server rather than localhost?

@yasserf , wow... it worked! i love how fast the connection is made and records fly here and there. thanks guys 👍. this issue can be closed now as i let someone else bug u for azure app service and uws error ;)

Awesome! Happy to hear it worked


[VITE] Missing dependencies after running setup vite command

What is the location of your example repository?
No response
Which package or tool is having this issue?
Hydrogen
What version of that package or tool are you using?
"@shopify/hydrogen": "~2024.1.3"
What version of Remix are you using?
"@remix-run/node": "^2.8.0"
Steps to Reproduce

Create a new Hydrogen project using npm create @shopify/hydrogen@latest
Run vite setup command npx shopify hydrogen setup vite
Launch dev server npm run dev

Expected Behavior
Hydrogen app should launch correctly.
Actual Behavior
Missing dependencies:
Failed to resolve dependency: set-cookie-parser, present in 'ssr.optimizeDeps.include'
Failed to resolve dependency: cookie, present in 'ssr.optimizeDeps.include'
Failed to resolve dependency: content-security-policy-builder, present in 'ssr.optimizeDeps.include'

ReferenceError: exports is not defined

@wizardlyhel I forgot to mention that I'm using pnpm

I created a clean new project following the steps in my first comment and still have the same dependency issue.
Here are the version I use:
❯ pnpm -v
8.15.5
❯ node -v
v21.7.1

I am getting the same error: ReferenceError: exports is not defined
Mine is caused by the typographic-base package, is there any fix for this yet?

I am getting the same error: ReferenceError: exports is not defined
Mine is caused by the typographic-base package, is there any fix for this yet?

That's probably unrelated to this specific issue. For the typographic-base dependency, check how we updated our demo-store to Vite: https://github.com/Shopify/hydrogen-demo-store/pull/12

Thanks @frandiox
I added the .npmrc file and I can confirm this removes the Failed to resolve dependency errors.
Although I still have the ReferenceError: exports is not defined error unless I install the cookie dependency.
ReferenceError: exports is not defined
    at /node_modules/.pnpm/cookie@0.6.0/node_modules/cookie/index.js?v=20f76387:15:1

Yeah sorry I didn't try to remove node_modules. It works perfectly now, thanks!

@frandiox This is still an issue for us unfortunately.
For context, we're using a PNPM monorepo. There's another (non-Hydrogen) Remix Vite app in the same monorepo that works without any issue (and uses many of the same deps), so I suspect these errors are being introduced by the hydrogen and oxygen Vite plugins.
It's like a game of whack-a-mole. We were able to get rid of the errors for cookie, set-cookie-parser and content-security-policy-builder by installing them in the app (prefer to avoid playing around with hoisting), but then started getting errors for typographic-base. We removed that dep from the app entirely, and then got errors for remix-routes (a package we also use in the other Remix Vite app in the monorepo without any issue). After removing remix-routes from the app we started getting errors for use-sync-external-store (see below), and I expect that if we fix that we'll just get another error.
ReferenceError: module is not defined
    at /code/node_modules/.pnpm/use-sync-external-store@1.2.0_react@18.3.1/node_modules/use-sync-external-store/shim/with-selector.js:6:3
    at Object.runViteModule (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:1181:17)
    at ViteRuntime.directRequest (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:1026:78)
    at ViteRuntime.cachedRequest (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:949:28)
    at request (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:976:128)
    at /@fs/code/node_modules/.pnpm/zustand@4.5.2_@types+react@18.3.1_immer@10.1.1_react@18.3.1/node_modules/zustand/esm/index.mjs?v=2603acb1:3:31
    at Object.runViteModule (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:1181:11)
    at ViteRuntime.directRequest (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:1026:60)
    at ViteRuntime.cachedRequest (code/node_modules/.pnpm/@shopify+mini-oxygen@3.0.2_vite@5.2.11/node_modules/@shopify/mini-oxygen/dist/vite/worker-entry.js:950:79)
    at /app/lib/app-state.tsx:3:31

I agree it's frustrating but this is really an issue with the dependencies. They are in CJS, which means they are only compatible with Node.js. Oxygen is a different runtime so you need to tell Vite to do its magic before loading the code in Oxygen.
That said, I'm trying to add here a tool to do all this job automatically: https://github.com/Shopify/hydrogen/pull/2106
Hope to release it soon if it passes the reviews.

Got it, thanks for clarifying. Will keep an eye on your PR as this is the only blocker for us switching to Vite


Markdown not working on production

Might want to note this one too- https://b-wise.mobi/english/your-peeps/bullying/abuse-when-somebody-hurts-another-person/ it’s displaying the markup i.e abuse can be physical, probably related to the cms bug.

This is first & foremost a content issue. Lists items were being used instead of normal paragraphs. Markdown doesn't apply for list items, only for paragraph blocks that are added to the page.
Secondly, there's a CSS styling issue here.  and related tags are stripped of their styling.

@saeedmb8 can you check the styling issue here?

Marking as resolved until we get clear feedback on what's not working. This ticket came from people who didn't understand well enough how the CMS works.


Cargo init should create an examples directory by default for lib crates

Code examples are a great documentation tool for libraries. They're a starting point for learning how to use a new crate. Cargo already supports docs out of the box for building documentation from your code.
Adding the examples directory by default would:

Increase visibility of the feature
Encourage crate authors to add examples

As a result:

Crate quality will improve
Documentation will improve
Barrier of entry for learning new crates will be lower

Sounds plausible to me!

Awesome! I've opened up a PR to implement this, but I'm having some trouble getting cargo to build on my Windows machine. It seems to be a libsshv2 issue.

Given the resolution in https://github.com/rust-lang/cargo/pull/5117#issuecomment-372705756 should this issue be closed?


Rails 3-compatible alternative to action_mailer_cache_delivery?

Though it's not mentioned in this or the action_mailer_cache_delivery README, it appears from local testing that action_mailer_cache_delivery is not Rails 3-compatible.
Is there any Rails 3-friendly way to share emails between separate server and test-running processes (as needed with Selenium and similar tools) short of introducing DelayedJob or ar_mailer?

I haven't looked into this closely, but AFAIK there isn't an easy way to do this.  By easy, I mean a one line change to your config file.  I have some co-workers who ran into this the otherday and I know they came up with a solution... @timcharper or @ewollesen, care to gist the solution you came up with?

Our solution was to setup ActionMailer for local file delivery, then our tests read in those files with the mail gem, and tested their contents. We were using selenium, and some cheeky helpers like this one:
def wait_for_delivery(email, num=1, timeout=20)
  Timeout::timeout(timeout) do
    sleep 0.1 while num_emails_to(email) < num
  end
end

def num_emails_to(email)
  data = File.read(MAILBOX + email)
  data.lines.grep(/^Date:/).size
rescue Errno::ENOENT
  0
end

If you're interested, I forked and gemified the square/action_mailer_cache_delivery repo -- which in turn forks the nicolasochem/action_mailer_cache_delivery repo and has Rails 3 support.
You can find it at http://github.com/ragaskar/action_mailer_cache_delivery and should be able to just shove it in your Gemfile with
gem "action_mailer_cache_delivery", git: "git://github.com/ragaskar/action_mailer_cache_delivery.git"
It ain't pretty (class instance vars), but it appears to work.

Thanks @ragaskar! I've updated the README to point to your version.


Close some tags.

Thanks @huonw :sob:

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit a42dfb0 has been approved by huonw

:hourglass: Testing commit a42dfb0 with merge 6192ef5...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-gnu-32, cargo-win-gnu-64, cargo-win-msvc-32, cargo-win-msvc-64


[Validation on User Model]

We need to add validation on user model attributes:

first_name
last_name

to only include the alphabetic characters like from a-z.
Approach:
We can use the regex for validation
Linked Issues:
#46

Hello ! I'm Hermann, can you assign me this issue please ?

Hey @HermannH34 ,
Assigned


Simpler COM function signatures

Along the way to #81, I needed to harmonize COM and WinRT signatures so I finally implemented logical return values for COM methods and functions. This dramatically simplifies using COM APIs in Rust. This is best illustrated with an example. Previously the com_uri example required the following lines of code:
let mut uri = None;
let uri = CreateUri("http://kennykerr.ca", Default::default(), 0, &mut uri).and_some(uri)?;

let mut domain = BSTR::default();
uri.GetDomain(&mut domain).ok()?;

let mut port = 0;
uri.GetPort(&mut port).ok()?;

With this update, you can now write it far more simply:
let uri = CreateUri("http://kennykerr.ca", Default::default(), 0)?;

let domain = uri.GetDomain()?;
let port = uri.GetPort()?;

Fixes #509
Fixes #880
Fixes #910

Does this mean that WinRT and now COM function signatures will have a smooth appearance but (the massive set of) Win32 signatures have an unsafe rougher look?

This seems to be causing problem for us. The original hresult is now lost if not an error (.ok()), but for some functions (i.e. DoDragDrop we actually need to know the hresult to see if drag succeeded (https://github.com/microsoft/windows-rs/issues/922).


A shorter nodejs image?

Looks like there could be a shorter version of nodejs image compared to what we have in the samples:
FROM windowsservercore

ENV NPM_CONFIG_LOGLEVEL info
ENV IOJS_VERSION 3.2.0

RUN powershell -Command "wget -Uri https://iojs.org/dist/v%IOJS_VERSION%/iojs-v%IOJS_VERSION%-x64.msi -OutFile iojs.msi -UseBasicParsing"

RUN msiexec.exe /q /i iojs.msi

CMD [ "iojs" ]

https://stefanscherer.github.io/create-an-io-js-container-image-for-windows/ @stefanscherer

Thanks @ahmetalpbalkan for connecting the dots. This is great to see more and more open source projects so it becomes easier to give feedback.
The example above is for io.js. A more suitable example for Node.js 0.12.7 can be found in this Dockerfile
FROM windowsservercore

ENV NPM_CONFIG_LOGLEVEL info
ENV NODE_VERSION 0.12.7

RUN powershell -Command "wget -Uri https://nodejs.org/dist/v%NODE_VERSION%/x64/node-v%NODE_VERSION%-x64.msi -OutFile node.msi -UseBasicParsing"

RUN msiexec.exe /q /i node.msi

CMD [ "node" ]

And is derived from the official node Docker image and its 0.12/Dockerfile.
But there are still some differences. What I haven't tried in a Windows Container is:

Verify the download with the SHA256 checksum
Combine multiple shell commands into one RUN command to make it atomic. So you can download file, extract them, install them and remove the downloads and temp files without adding those files into the layer. (Perhaps a Dockerfile should have a feature to make multiple RUN commands atomic...)

I also have assumed that the RUN msiexec ... command waits until msiexec is really done. I've seen the extra wait section in the Powershell script.

Correct - run will wait until the process exits. You can probably use RUN powershell..... && msiexec... to make it atomic. To avoid long lines, use  \ as the continuation character at the end of a line. You should also be able to shorten the ENV using the alternate syntax ENV A=1 B=2

I've played with the SHA256 checksum and atomic commands and came up to this Dockerfile using only one RUN and multiple commands in one powershell script:
FROM windowsservercore

ENV NPM_CONFIG_LOGLEVEL info
ENV IOJS_VERSION 3.3.0
ENV IOJS_SHA256 68289641c2780e8c34fc9d4c1c92290d5adb7612b4979722523d6212c79bb0d0

RUN powershell -Command " \
    wget -Uri https://iojs.org/dist/v%IOJS_VERSION%/iojs-v%IOJS_VERSION%-x64.msi -OutFile iojs.msi -UseBasicParsing; \
    if ((Get-FileHash iojs.msi -Algorithm sha256).Hash -ne $env:IOJS_SHA256) {exit 1}; \
    msiexec /q /i iojs.msi | Out-Null; \
    Remove-Item -Path iojs.msi; \
    "

CMD [ "iojs" ]

I'm assuming that this is no longer an issue, if so, please advise and we can re-open.


HAWQ-1142 - add ambari procedures to master mirroring docs section

edited the existing content and added info and links for ambari procedures related to the master standby.

the topic is resynchronizing standby with the master.  if you look at the
ambari "removing the standby" section, one of the "when to perform" bullet
items is "

Execute this procedure and then add the HAWQ Standby Master once
again, if the HAWQ Standby Master is unable to synchronize with the HAWQ
Master and you need to reinitialize the service.

i took this to mean resynchronize.  if not, i am not sure what ambari
procedure to invoke?  maybe need to remove and add?
On Fri, Nov 4, 2016 at 9:30 AM, David Yozie<EMAIL_ADDRESS>wrote:

@dyozie commented on this pull request.
In admin/MasterMirroring.html.md.erb
https://github.com/apache/incubator-hawq-docs/pull/50#pullrequestreview-7236460
:

-shell -$ hawq init standby -n -
+1. If you use Ambari to manage your cluster, follow the instructions in Removing the HAWQ Standby Master.
Shouldn't this Ambari xref point to a standby init procedure, rather than
a "removing the standby" procedure?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-hawq-docs/pull/50#pullrequestreview-7236460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AS3oddhaSCWewj0HddydHXR76DP0Wd6Hks5q612xgaJpZM4Knymn
.

@lisakowen - I see what you mean.  I think maybe the target Ambari section needs to be renamed, and the final step updated to account for the resynch use case.  That can be handled separately from this PR.


[Docs][PrebidServer] Add /version admin endpoint documentation

Hello there,
Seems that the /version admin endpoint documentation is missing.
Even if the function of this endpoint is clear, it would be great to know more details about it and especially how this version is computed.
Thanks !

Thanks for working on this @benjaminch - does your PR https://github.com/prebid/prebid.github.io/pull/1198 address this issue? If so, may we close this?

Hey !
Indeed it does ! We can close it.
Thanks ;)
On Mon 18 Mar 2019 at 22:35, bretg<EMAIL_ADDRESS>wrote:

Thanks for working on this @benjaminch https://github.com/benjaminch -
does your PR #1198 https://github.com/prebid/prebid.github.io/pull/1198
address this issue? If so, may we close this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/prebid/prebid.github.io/issues/1197#issuecomment-474110826,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABVEg7IMCXg5O89wxRXwQZZfJdiVq5X6ks5vYAaYgaJpZM4bmi5B
.


Confuse about the reslut

Great work !  Thanks for sharing.
however in your terminal session the Result shows the tf from /ar_marker_0 to /ee_link:, how ever in the eye-in-hand usage we really care about the tf from /ee_link to /camera_link,  any suggestion?

Hey, Did u solve this problem? I need transformation from /ee_link to /camera_link too.

Hey, Did you get the answer for this ??

Hi @SarfarazHabib. I did some modification so the results show transformation from /ee_link to /camera_link too. please follow https://github.com/lixiny/Handeye-Calibration-ROS/blob/master/src/handeye_calib_chessboard/launch/handeye_online.launch in my repo.
Thanks for  the jhu-lcsr' s original release.

Hey @lixiny Thanks for your help. It works for me now :)

Hey@lixiny can you explain a little how you solve the problem with your handeye_online,launch, Thanks

Hi, @PeakDing ,  I think I only modify the handeye_calibration.cpp
from:
https://github.com/jhu-lcsr/handeye_calib_camodocal/blob/master/src/handeye_calibration.cpp
to
https://github.com/lixiny/Handeye-Calibration-ROS/blob/master/src/handeye_calib_chessboard/src/handeye_calibration.cpp

Hi, @lixiny , your solution really works for me now. Thanks a lot!
However, I still can't figure out why this simple modification can make the whole thing work.
Could you briefly explain the reason behind?
I will appreciate it.

Hi, @FrankLin9981 , I suggest you to visualize the transformations by drawing it down or using RVIZ.   I drew the transformations of the: AX=XB  and found that the original implementation (may) has tiny little bug on the problem of eye-in-hand.
hope this can help you.


Mural & tiny side quests

Primarily added Mural documentation, but also updated the main README and added some stuff to .gitignore
Signed-off-by: TheBoatyMcBoatFace<EMAIL_ADDRESS>

📚 Documentation preview 📚: https://civicactions-handbook--1389.org.readthedocs.build/en/1389/

@dmundra it has been a while since I updated things from the main repo.

@dmundra it has been a while since I updated things from the main repo.

Ya and I am still seeing a lot of conflicts. It might be easier to start fresh from the master branch or try rebasing again.

Yea. Good idea @dmundra


Mint nft

How can i a mint my nft in getgems??

Hello there,
Visit our dedicated support page to initiate a chat with an agent for further information and enquires on how to get this done Ton-center live chat.
Regards


[Bug] [connector-v2] Dependency Conflict

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
The jar packages in the lib directory have dependency conflicts. For example, when running the s3 plugin, there are multiple Hadoop dependent jar files (hive jar files) that cause errors. When uploading other JDBC drivers, running the es plugin results in HTTP dependency jar conflicts. How to resolve such dependency conflicts
SeaTunnel Version
dev,2.3.8
SeaTunnel Config
{
  "env": {
    "execution.parallelism": "1",
    "job.mode": "BATCH"
  },
  "source": [
     {
      "plugin_name":"jdbc",
      "url":"jdbc:postgresql://******:5432/oceandatum?currentSchema=dw_label",
      "password":"******",
      "user":"******",
      "driver":"org.postgresql.Driver",
      "query": "SELECT \"id\",\"name\",\"label_column_fact\" FROM \"label_group_a\"",
      "result_table_name": "fake"
    }
  ],
  "transform": [
    {"plugin_name": "sql",
      "source_table_name": "fake",
      "result_table_name": "fake2",
      "query": "SELECT  concat(id,'$test') AS id,name AS label,concat('{','\"id\":\"',id,'\",','\"name\":\"',name,'\",','\"label_column_fact\":\"',label_column_fact,'\"','}') AS property FROM fake "
}
  ],
  "sink": [
    {
      "plugin_name": "elasticsearch",
      "hosts":["******:9200"],
      "index":"relation",
      "primary_keys":["id"]
    }
  ]
}

Running Command
bin/seatunnel.sh -c demo.json

Error Exception
Caused by: java.io.IOException: org.apache.hadoop.fs.s3a.SimpleAWSCredentialsProvider instantiation exception: java.lang.NoSuchMethodError: com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)V

Zeta or Flink or Spark Version
No response
Java or Scala Version
1.8
Screenshots

Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Reason for S3 plugin error: The guava version in the Hive driver is lower, while the guava version in the S3 plugin is higher, but now the driver dependencies are all in lib. How to eliminate this dependency conflict problem

该行与hadoop-aws包也有冲突。

I fix the problem.


Feature/csl880 hd discovery

Implemented HD address discovery

@Martoon-00 Is this good to go?

@rockbmb Yep, everything seems fine to me here


AWS?

Have you been able to get this to work with AWS successfully?

Scratch that. I was able to solve it.
in webpack config:
module.exports = {
  entry: './handler.ts',
  externals: [
    'aws-sdk'
  ],
  module: {
    loaders: [
      { test: /\.ts(x?)$/, loader: 'ts-loader' }
    ]
  },
};

Then something like:
import * as AWS from "aws-sdk";

AWS.config.update({
  region: "us-east-1"
});

var table = "Movies";
var year = 2015;
var title = "The Big New Movie";

var params = {
  TableName: table,
  Item: {
    "year": year,
    "title": title,
    "info": {
      "plot": "Nothing happens at all.",
      "rating": 0
    }
  }
};

export const hello = (event, context, cb) => {

  var docClient = new AWS.DynamoDB.DocumentClient();

  console.log("Adding a new item...");
  docClient.put(params, (err, data) => {
    if (err) {
      console.error("Unable to add item. Error JSON:", err);
      cb("unable to add item");
    } else {
      console.log("Added item:", data);
      cb(null, { message: 'Added item', data });
    }
  });
}


Missing API surface after move from bytemuck::Pod

I aim to edit object files directly in memory using this library, however I've encountered the problem that the object Pod implementation is missing much of the bytemuck::Pod functionality - including the operations on mutable references which would be required for this.
I also notice that the object::pod API is also slightly different:

object::pod::bytes_of() = bytemuck::bytes_of()
object::pod::bytes_of_slice() = bytemuck::cast_slice<_, u8>()
object::from_bytes and object::slice_from_bytes both include a tail output alongside the transmuted output

A Move to bytemuck::Pod would break this API, however the functions that include a tail seem to only be used to implement the Bytes struct (a wrapper around a slice), and this same implementation could also be easily modified to work with bytemuck::Pod and its tail-less functions simply by subslicing the input slice before passing it into the function.
The tail-inclusive functionality could also be added into bytemuck for added ecosystem impact.
I was also able to locate this PR from a year ago https://github.com/gimli-rs/object/pull/184 which doesn't seem to really justify the switch to a vendored Pod trait...

The switch to our own Pod implementation was because:

it allows us to avoid a dependency
the required implementation was trivial (especially compared to the complexity of bytemuck)
it allows us to provide a more convenient API (specifically the tail functionality)

I'm fine with adding mutable variants of the API if you need it. I'm unsure how this is intended to interact with the rest of the object file parsing though, which expects to hold multiple references to parts of the file (something that is harder to manage with mutable references).

* the required implementation was trivial (especially compared to the complexity of bytemuck)

May I ask you to elaborate on this? Bytemuck seems pretty easy to implement to me.

If I implemented bytemuck for this crate in a PR would you consider merging it in? (possibly behind a feature gate to avoid a required dependency?)

May I ask you to elaborate on this? Bytemuck seems pretty easy to implement to me.

The implementation in 2d48743bbf00036a9c485cb5e4b85b8cffea72f2 wasn't much larger than the wrappers it replaced. bytemuck handles a more general case (converting between any types, not just byte slices), which adds complexity that we don't need.

If I implemented bytemuck for this crate in a PR would you consider merging it in? (possibly behind a feature gate to avoid a required dependency?)

You'll have to convince me that it isn't enough to add from_bytes_mut and slice_from_bytes_mut to this crate.

from_bytes_mut and slice_from_bytes_mut would probably satisfy requirements, and I'll happily close this issue.

Oops, may also request bytes_of_mut as well?

Sure, curious what you need that for though? I expected mutation via the fields to be enough.

It's for screwing around with elf files mostly, there will likely be corruption of the fields / overlapping etc, so being able to work with raw bytes some of the time helps.

Recently I have implemented a POD struct, but i've been struck with a dilemma of using object::Pod or bytemuck::Pod. First i would like to use derive(Pod) for a struct and don't think about safety conditions or specifying safety comments, it just checks everything for you. Second i would have liked to reuse object's endian-agnostic types like endian::U32Bytes<Endian>. This would be trivially easy if object have depended on bytemuck::Pod, but it isn't. After some thought i don't see any problem with object depending on bytemuck, so let me refute the points made for moving from bytemuck:

it allows us to avoid a dependency

bytemuck has zero dependencies if all except a derive feature, otherwise it pulls a standard collections of crates for derive-macros (proc-macro2, quote, syn). I don't see much of a reason to avoid having +1 dependency to this crate.

the required implementation was trivial (especially compared to the complexity of bytemuck)

You can ignore bytemuck's complexity except for implementing Zeroable trait for the Pod trait. Necessary complexity seems very much trivial to me.

it allows us to provide a more convenient API (specifically the tail functionality)

POD is POD anywhere you go. Nothing stops you from implementing current object::pod functionality, including tail functionality.
Also i think there's some benefit of bringing back bytemuck such as:

bytemuck is more complete as a common API for different crates;
has more std Pod types (i. e. f32 and Optional) than object::Pod has;
delegating responsibility of proving PODness of these types to the bytemuck crate;
concurrent builds (bytemuck -> object + some_pod_types) instead of (object -> some_pod_types)

I would also like to see endian module being extracted into a different crate for similar reasons.

All that said i would like to do the PR for any of these changes, if any of them are approved.


chore: Remove yarn errors from git

Removes all yarn-error.log files from git

Legend – I was going to eventually get around to this :P


added custom error class so activation/error detail is not swallowed

Added a custom error class so that details about the activation are not hidden at the API level.  This takes the "error" object that is caught in base_operation.js and attaches it to the custom error object so we can access logs and the activationId:

Good idea. I'll have a play with this next week.
Can you add unit tests to verify this functionality?

I would like to get this merged but it should have a few unit tests to verify it's working correctly.
Are you able to update this PR?

@triceam gentle nudge about this 😀


TextInput Component does not announce Checked/Unchecked State

Description
Does not announce "checked"/"not checked" on focus of TextInput Component.
This issue is covered in-depth by parent issue #30843, please check there for more details.
React Native version:
0.63

I had a look at this issue and found out accessible & accessibilityState props are properly being passed down to the component (TouchableWithoutFeedback inside TextInput.js) however there seems to be some conflict with TextAncestor.Provider in the same file because when I removed it the screen reader was able to read all props including checked.
This problem was not present on Button #30950  (which I can confirm was solved by PR #31001 ) as that component doesn't deal with an ancestor.
I'm not entirely sure how TextAncestor works so I can't debug any further unfortunately but I hope that bit helps

https://github.com/facebook/react-native/blob/051082117059e461f340f0fb7b0bde3db835e5dd/Libraries/Components/TextInput/AndroidTextInputNativeComponent.js#L549-L550
https://github.com/facebook/react-native/blob/051082117059e461f340f0fb7b0bde3db835e5dd/ReactCommon/react/renderer/components/textinput/androidtextinput/react/renderer/components/androidtextinput/AndroidTextInputShadowNode.cpp#L25
https://github.com/facebook/react-native/blob/051082117059e461f340f0fb7b0bde3db835e5dd/ReactCommon/react/renderer/components/textinput/androidtextinput/react/renderer/components/androidtextinput/AndroidTextInputProps.cpp#L133-L137
seems to me that we need to add accessibilityState in c plusplus component AndroidTextInputProps

While technically this would be possible, I can't imagine a UI where this would be useful or necessary. Closing out.


Log says device or resource busy, although aircrafts are tracked

I have this issue since around 2 weeks. The log output shows the following lines repeatedly:
2020-03-26 07:28:54 | [reader][i]Connected to the receiver, configuring
2020-03-26 07:28:54 | [reader][i]Configured, processing messages
Thu Mar 26 07:28:54 2020 UTC  dump1090-fa v3.8.0 starting up.
rtlsdr: using device #0: Generic RTL2832U (Generic, RTL2832U, SN<PHONE_NUMBER>3705700)
usb_claim_interface error -6

However, connecting to the web frontend shows up some aircraft, although with type "Other" and not "ADS-B", whatever "Other" means. As a result of all this, my account on fr24 was degraded to Basic, since apparently my feeder is connected but i do not send any data. I have already double-checked whether some "real" DVB-T modules in my kernel are disabled, they are all blocked.
How is the feeder currently tracking the aircrafts? Why isn't it able to connect to the stick all of a sudden?

Are you using the latest version  of the image ? We had the same problem but it's now fixed.
See #14.

Have you set your parameters via the Docker Export variables OR the /etc/fr24feed.ini file correctly ?
If you use the ini File instead the variables, your ini File should probably look like this:
receiver="beast-tcp"
host="<IP_ADDRESS>:30005"
fr24key="YOURFEEDERID"
bs="yes"
raw="yes"
logmode="1"
procargs="--net --write-json /usr/lib/fr24/public_html/data"
If receiver "beast-tcp" is not working try "avr-tcp". You probably have "dvbt" in there which is not possible since your RTL SDR Stick is already in use (that is what the error message "usb_claim_interface error -6" is telling you.
So instead of trying to access the USB stick via the USB hardware, try to poll the data via the TCP connection.
Port 30005 is for Outbound Data in BEAST Mode to feed to fr24 and flightaware


Compilation "note" on GCC 6 ARM

When compiling this code:
#include <iostream>
#include <nlohmann/json.hpp>

using json = nlohmann::json;

int main(int argc, char *argv[]) {
  json o=json::parse("{\"foo\":\"bar\",\"list\":{\"100\":{\"l100\":100},\"200\":{\"l200\":200}}}") ;

  json& l=o["list"];

  for (json::iterator it = l.begin(); it != l.end(); ++it) {
    std::cout << it.key() << " : " << it.value() << "\n";
  }

}

compiler report "note":
In file included from /usr/include/c++/6/map:60:0,
                 from /usr/local/include/nlohmann/json.hpp:50,
                 from test.cpp:2:
/usr/include/c++/6/bits/stl_tree.h: In member function ‘std::pair<std::_Rb_tree_node_base*, std::_Rb_tree_node_base*> std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_get_insert_hint_unique_pos(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::const_iterator, const key_type&) [with _Key = std::__cxx11::basic_string<char>; _Val = std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> >; _KeyOfValue = std::_Select1st<std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> > >; _Compare = std::less<std::__cxx11::basic_string<char> >; _Alloc = std::allocator<std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> > >]’:
/usr/include/c++/6/bits/stl_tree.h:1928:5: note: parameter passing for argument of type ‘std::_Rb_tree<std::__cxx11::basic_string<char>, std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> >, std::_Select1st<std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> > >, std::less<std::__cxx11::basic_string<char> >, std::allocator<std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> > > >::const_iterator {aka std::_Rb_tree_const_iterator<std::pair<const std::__cxx11::basic_string<char>, nlohmann::basic_json<> > >}’ will change in GCC 7.1
     _Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Thanks for reporting. I'm not sure whether this is an issue: we already use GCC 7.1 on Travis, and locally I compile and test with GCC 8.

This "note" happens only on arm-linux-gnueabihf arch (Raspberry Pi) . On the same version of GCC 6 (6.3.0) on x86-64 arch the test code compiles well without any notes. However, compiled code works well on ARM.
This note can be turned off by passing argument '-Wno-psabi' to compiler.

still broken

same thing on 8.1

The "note: parameter passing for argument of type ... will change in GCC 7.1" is an internal note about internal data types to the STL and doesn't seem to have anything to do with nlohmann json.
Maybe you are mixing versions of libstdc++ and GCC that are not meant to be used together? I would check how your compiler is finding your STL. If you are making your own GCC, maybe you forgot to also build a compatible version of libstdc++ and you're getting a system one or seomthing?

no, actually i tell you what it is, when not having enough memory, compiler
front end chocks on, for example parsing a map with universal initialization
it's all ok, once i figured it out
On Sun, Feb 17, 2019 at 10:40 AM Jared Grubb<EMAIL_ADDRESS>wrote:

The "note: parameter passing for argument of type ... will change in GCC
7.1" is an internal note about internal data types to the STL and doesn't
seem to have anything to do with nlohmann json.
Maybe you are mixing versions of libstdc++ and GCC that are not meant to
be used together? I would check how your compiler is finding your STL. If
you are making your own GCC, maybe you forgot to also build a compatible
version of libstdc++ and you're getting a system one or seomthing?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/nlohmann/json/issues/658#issuecomment-464478981, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Alm61e2jmSD1w8YwC_dhfLn1VnDPBAsQks5vOYX_gaJpZM4OZcp6
.


Fully implement NAPI C++ over JSI

NAPI issues

[ ] Implement missing IsXXX functions
[ ] ToBoolean and ToNumber need to coerce if the type is not compatible
[x] Implement UTF-16 string support (fixed in #333)
[ ] Implement Symbol class
[ ] Investigate if vf_fallback can be optimized
[ ] Implement Object::HasOwnProperty
[ ] Implement Object::Delete functions (probably need to use eval unless we can get JSI to implement)
[ ] Implement Object::Has(index)
[ ] Handle exceptions in FunctionReference class
[ ] Investigate what should happen if Object::Get(index)/Object::Set(index) is called on non-array type and implement
[ ] Implement Object::DefineProperty/Object::DefineProperties functions
[ ] Implement ArrayBuffer::New overload with finalize callback
[ ] Implement DataView class
[ ] Implement commented out type check in TypedArrayOf
[ ] Implement Error class and related classes
[ ] Determine exactly what should happen with Reference class (use JSI weak objects?)
[ ] Finish/Cleanup/Optimize ObjectWrap class implementation

JSI issues

[ ] jsi::ArrayBuffer cannot take external data. This will cause extra unnecessary copying.
[ ] jsi::Object::instanceOf is not const for some reason. Requires unnecessary const_cast.

JSCRuntime issues

[X] JSCRuntime::createValue is slow and can be easily fixed by using JSValueGetType (fixed in recent versions)
[X] JSCRuntime::JSStringToSTLString is slow and can be optimized (fixed in recent versions)
[ ] JSCRuntime::createStringFromUtf8 doesn't work property with strings that have 0s in them. The usage of JSStringCreateWithUTF8CString is incorrect since this function only read up to the null-termination which is not the expected result from this function which takes a length parameter. Similar problems may be lurking for getting the length of strings.

Handling exceptions is painful right now. Should do that first.

Addressing the error handling part with #444.

Reopen if we need full support


Add Contributor Guidelines doc

This patch adds general contributing guidelines for cloud-provider-openstack.

What this PR does / why we need it:
This PR adds document for general contributing guidelines to cloud-provider-openstack
Which issue this PR fixes :
fixes #230

/approve
/lgtm


D405 cannot set exposure parameters

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{RealSense D405 }

Firmware Version
<IP_ADDRESS>

Operating System & Version
{Win 10

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
{ legacy / 2.. }

Language
python

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
I want to adjust the exposure parameters of Realsense D405
My code is as following:
pipe=rs.pipeline()
cfg=rs.config()
cfg.enable_stream(rs.stream.depth, 1280, 720, rs.format.z16, 30)
cfg.enable_stream(rs.stream.color, 1280, 720, rs.format.rgb8, 30)
profile=pipe.start(cfg)
color_sensor = profile.get_device().query_sensors()[1]
color_sensor =color_sensor.set_option(rs.option.enable_auto_exposure, False)
color_sensor =color_sensor.set_option(rs.option.exposure,10000)
When running the code , erro happens:
color_sensor = profile.get_device().query_sensors()[1]
IndexError: list index out of range
How to solve??

Hi @137ck  Because the D405 does not have a separate RGB sensor and obtains RGB from the depth sensor, a program will fail if the query_sensors() index is set to '1' (RGB sensor).  It should instead be set to '0' (the depth sensor).  Setting a manual exposure value for the depth sensor also configures exposure for RGB.
Please bear in mind that setting a high exposure value can cause FPS to lag, like in the case at https://github.com/IntelRealSense/librealsense/issues/12185 where setting exposure to 100000 causes FPS to drop from 30 to 6.

Hi @137ck  Do you require further assistance with this case, please?  Thanks!

Case closed due to no further comments received.


[BP-3.1][FLINK-35415][base] Fix compatibility with Flink 1.19

Cherry-picked from #3348.

Fixed E2e package failure & rebased to release-3.1 branch, could @leonardBang please trigger the CI? Thanks!


Assertion failed: SortCompare must be an abstract closure taking 2 arguments

When using this shim, an assertion seems to be thrown in SortIndexedProperties.

Assertion failed: SortCompare must be an abstract closure taking 2 arguments

It seems to do this in Chrome 90 and Safari 15.
I've only imported this shim and imported the /auto variant. If I can provide any additional information, please let me know.

Thanks, that's helpful - I'll try to reproduce it.

I can't seem to produce it - both of those sets of tests pass.
What version of es-abstract do you have installed, as well as this package? What package manager are you using? (yarn often installs incorrect dependency versions, eg)

It's very odd, after some experimentation it only seems to happen on production builds.
I'm using npm and Nuxt3 (which uses Vite under the hood), this leads me to think that their build step transforms the code in such a way that it fails.
My full list of packages is such:
"array.prototype.toreversed": "^1.1.2",
"array.prototype.tosorted": "^1.1.4",
"sass": "1.75.0",
"sass-loader": "14.2.1",
"vue-scrollto": "^2.20.0"
"nuxt": "^3.11.2",
"nuxt-gtag": "^1.1.2"

Feel free to close if it's outside of your scope, of course.

what about npm ls es-abstract?

├─┬<EMAIL_ADDRESS>│ └─┬<EMAIL_ADDRESS>│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>deduped
│   ├─┬<EMAIL_ADDRESS>│   │ └──<EMAIL_ADDRESS>deduped
│   └─┬<EMAIL_ADDRESS>│     └──<EMAIL_ADDRESS>deduped
└─┬<EMAIL_ADDRESS>  └──<EMAIL_ADDRESS>deduped

hmm, that should be right.
What bundler are you using? Can you confirm the literal function source that's being passed to SortCompare using the debugger?

I'm using vite (esbuild), which turns this:
npx esbuild --minify node_modules/array.prototype.tosorted/implementation.js

https://github.com/es-shims/Array.prototype.toSorted/blob/850c48e17f4eeffd1eaeff5898b083916224dfef/implementation.js#L24-L26
into this:
      o = function (n, u) {
        return CompareArrayElements(n, u, e);
      },

causing it to fail the IsAbstractClosure fn.name check.
I don't think many minifiers respect (0,x) semantics. terser happens to work here despite not respecting (0,x) because it inlines the SortCompare definition into the SortIndexedProperties call site so the function coincidentally stays anonymous.

Eliding function names isn't universally safe behavior, especially when minifying, because it's introspectable, so that seems like a bug worth filing on esbuild.


Have amplify build containers support ECR containers & custom container sizes

Is your feature request related to a problem? Please describe.
Not all things can be accomplished in 7GB of ram.
Describe the solution you'd like
Have a range of options for build containers on amplify that mirrors those that are available in CodeBuild.

Hi @nagey, Amplify Console does currently support custom public ECR instances as outlined here: https://docs.aws.amazon.com/amplify/latest/userguide/custom-build-image.html however the environment size is not adjustable, we have added this as a feature request.


Object URL has changed to /objects/ from /object/ - suggest that a redirect is created

The object URL (many of which will be bookmarked or coded by external API calls), has changed from /object/ to /objects/.
E.g.
https://lasair-ztf.lsst.ac.uk/objects/ZTF19aaqslxs/
was previously
https://lasair-ztf.lsst.ac.uk/object/ZTF19aaqslxs/
Can we add a redirect in urls.py?

fixed


Docker does not start with redis "authentication required"

📝 Description of issue:
I used docker-compose and want to use my own postgres. I changed the .env file accordingly. While booting up the backend container shows.
File "/usr/local/lib/python3.11/dist-packages/rq/queue.py", line 1033, in _enqueue_job
job.redis_server_version = self.get_redis_server_version()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/rq/queue.py", line 203, in get_redis_server_version
self.redis_server_version = get_version(self.connection)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/rq/utils.py", line 289, in get_version
tuple(int(i) for i in connection.info("server")["redis_version"].split('.')[:3]),
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/commands/core.py", line 993, in info
return self.execute_command("INFO", section, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/client.py", line 1266, in execute_command
conn = self.connection or pool.get_connection(command_name, **options)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 1457, in get_connection
connection.connect()
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 711, in connect
self.on_connect()
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 776, in on_connect
if str_if_bytes(self.read_response()) != "OK":
^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 874, in read_response
response = self._parser.read_response(disable_decoding=disable_decoding)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 347, in read_response
result = self._read_response(disable_decoding=disable_decoding)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/dist-packages/redis/connection.py", line 370, in _read_response
raise error
redis.exceptions.AuthenticationError: Authentication required.
use SECRET_KEY from file
Any idea on this?

Oh boy. Network trouble. It was talking to a different redis container with authentication required turned on.


Feature Suggestion - Complete All (For each category)

Since lots of new users are coming in with many categories already done, and maybe even whole camo categories done, we should offer them the ability to batch complete a category.
Obviously we could double check with the user if they already have made progress in the category (Are you sure you want to complete all challenges in the category?!), to stop it from accidentally ruining their tracking, but this would be incredibly useful for new user onboarding and making it super satisfying to check off everything you've done without having to double click everything or single click all the camos.
Also this would coincidentally help with development and speed up debugging, but that's just a side effect.
(Bad mockup of one potential implementation):

Could also be less invasive and part of double clicking category name? But this doesn't feel as good to me without being accessible and visible to users.

Double-clicking the category name to complete the category was a feature but it suddenly got removed during a commit a while back (regression?).
But I do agree that it should be more visible to the user. Maybe an onboarding experience showing the basics on how to use the site? (Very rough mockup):

Whilst the idea of onboarding seems nice, that to me is just a wall of text that no call of duty player would ever want to read 😄
Big chunks of text are really off putting for new users to a site so I think that should be avoided. Normally in good UX a feature should be able to describe itself with a minimum of explanation.

The function was there earlier, and probably still is available in the store if I recall correctly. I removed it due to not being sure how we would present the camouflages. Before we didn't show the Platinum and Polyatomic until they were unlocked. I can add it back! Needs some modifications though but shouldn't take too long once I begin! 😄
An onboarding feature is a nice suggestion! But I agree with @sol3uk that most people would find it annoying. Perhaps we could do something where we check the available variable for when they first started tracking (beganGrind) in the store, and if the date is null or less than like 7 days (as an example) we would show a notice at the top of the site sort of like:

Welcome to the tracker! To familiar yourself a bit more with the UI, check out our tutorial page!

With a link to a separate page that can be filled with tutorials on how to maneuver the site, save as bookmark to home-screen on mobile, export/import, etc. I've been thinking of adding a Guide page, but haven't had the time yet as it was far down on the priority list 😅 But I'll definitely look into it in the near future! Great suggestion, @CrazyIsEasy!


[ENHANCEMENT] - Pricing Section Components

Is your feature request related to a problem? Please describe.
no
Describe the solution you'd like
a section for showing pricing plans.
Describe alternatives you've considered
none
Additional context

Nice suggestion @usman-faisal I'll take a look, thanks!

okay great! can I be assigned to this task?


"app.dgrm.net has pro features"

Hi - very nice library.
Obviously its no problem to have pro features etc, but at the moment its a little unclear what is pro / what is in the github.
I found the github repo is missing the rectangles, and also has a different right-click behaviour.
What is in / out of scope for the github version?

Hi @calumk
Thanks for reaching out. I'm sorry for the delay.
It is a good question. For now I have to postpone documentation.
Right now I am focus on "live collaboration" feature. Users will be able to work simultaneously on the same diagram, like in Google Docs.

This is a wonderful open source project，everyone is waiting for thes features：multiple selection, copy, paste,redo,undo.
Please,thks


sapmnt not found

I started
./ansible-wrapper ./stacks/NetWeaver-Distributed/playbook.yml --extra-vars<EMAIL_ADDRESS>and got the error message
TASK [nfs-client : trigger automounts] ************************************************************************ failed: [<IP_ADDRESS>] (item={'source': '<IP_ADDRESS>:/sapmnt', 'mountpoint': '/sapmnt'}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["ls", "/sapmnt"], "delta": "0:00:10.015689", "end": "2022-03-22 10:47:38.144072", "item": {"mountpoint": "/sapmnt", "source": "<IP_ADDRESS>:/sapmnt"}, "msg": "non-zero return code", "rc": 2, "start": "2022-03-22 10:47:28.128383", "stderr": "ls: cannot open directory '/sapmnt': No such file or directory", "stderr_lines": ["ls: cannot open directory '/sapmnt': No such file or directory"], "stdout": "", "stdout_lines": []} failed: [<IP_ADDRESS>] (item={'source': '<IP_ADDRESS>:/usr/sap/trans', 'mountpoint': '/usr/sap/trans'}) => {"ansible_loop_var": "item", "changed": true, "cmd": ["ls", "/usr/sap/trans"], "delta": "0:00:10.014608", "end": "2022-03-22 10:47:50.822982", "item": {"mountpoint": "/usr/sap/trans", "source": "<IP_ADDRESS>:/usr/sap/trans"}, "msg": "non-zero return code", "rc": 2, "start": "2022-03-22 10:47:40.808374", "stderr": "ls: cannot open directory '/usr/sap/trans': No such file or directory", "stderr_lines": ["ls: cannot open directory '/usr/sap/trans': No such file or directory"], "stdout": "", "stdout_lines": []}
Seems someone forgot an mkdir /sapmnt?

I know that Terraform is a software that does not focus on how you do things, but what to deliver. In this specific case, this goal makes it hard to debug. Is there a way to find out what Terraform does in what order to debug why it has not happened?

I was able to resolve this issue. The issue was that the firewall was forbidding NFS mounts. Once I opened port 111 and 2049 for (in my case) <IP_ADDRESS>/24, it worked.
Hope this will help other people coming after me.
However, I would still be grateful for any idea how I could have found this information by a systematic approach rather than trying out all kinds of stuff. Thanks.

Closing this, because my remaining question pertains to Terraform, not to this git repository.


Fetching metadata fails silently inside of content_iterator

When fetching metadata fails it should send warnings to Sentry. Currently an error is silently ignored, the page fails to generate a "next" request and harvesting stops abruptly. This in turn can disrupt harvesting other entities.

Failing requests are already visible in the breadcrumbs area of Sentry.


Starlight is incompatible with the Astro build.format preserve option

What version of starlight are you using?
0.21.5
What version of astro are you using?
4.6.3
What package manager are you using?
pnpm
What operating system are you using?
Mac
What browser are you using?
Chrome
Describe the Bug
when I add the options
    trailingSlash: 'always',
    build: {
      format: 'preserve',
    },

to an existing otherwise working starlight project, it stops working with the error
13:16:42 [ERROR] Cannot read properties of undefined (reading 'addBase')
  Stack trace:
    at formatPath (/home/projects/withastro-starlight-7ibewh/node_modules/@astrojs/starlight/utils/createPathFormatter.ts:25:25)
    [...] See full stack trace in the browser, or rerun with --verbose.

Link to Minimal Reproducible Example
https://stackblitz.com/edit/withastro-starlight-7ibewh?file=astro.config.mjs
Participation

[ ] I am willing to submit a pull request for this issue.

Thank you for the bug report @lschierer! I think this is probably related to the 'preserve' setting — that was added to Astro after our logic for paths was added, so we’re likely not accounting for it in the createPathFormatter utility where that error is being logged.
Our formatting strategies account for the 'file' and 'directory' configurations, but not the newer 'preserve':
https://github.com/withastro/starlight/blob/be258c64d398173d061d5411ea4c9294860a74e7/packages/starlight/utils/createPathFormatter.ts#L15-L24


Black triangles after updating driver/llvm

Hi I updated from llvm 6.0.1 to 7.0.1 which fixed some graphic glitches in RE2 remake for me (https://github.com/doitsujin/dxvk/issues/895) but now I've a lot of black triangles in games which were working fine before like Overwatch and it's launcher:

Ok seems you are right, a kernel update from 4.14 to 4.19 fixed the problem again, so probably the newer llvm/mesa driver was incompatible to the older kernel or something like that. :see_no_evil:


fix(lint): disable ESlint notice plugin for JSON

Addresses #123.
Purpose
Fix linting and formatting of JSON files in open source TypeScript projects.
Approach and changes
Disables the ESLint notice plugin in JSON files via an override. The plugin
insisting the need for a copyright header in a JSON file and also causing issues
with the @typescript-eslint/parser configuration.
I'm not adding any tests for this as this is purely declarative and there are no
existing tests for ESLint rules.
Definition of done

[x] Development completed
[ ] Reviewers assigned
[ ] Unit and integration tests

Oupsies. Will have to fix that test. 😆

The tests are still failing, probably because you're on a different Node version. Make sure you're using the one that's defined in .nvmrc which is currently lts/dubnium.

Meeeeh, yeah they were passing locally.


What is the exact network size for Kernel Estimation Module?

I was curious about the number of paramters for the 1d kernel estimation network. In the paper, it states that this sub module has 5.51M of paramters. However, when I look at the kernel estimation network structure in the supplemental material, I believe it is much larger than 5.51M. In the decoder, one layer with 4x4x512x512 already has around 4.19M parameters.

You are so careful, so am I.
I found the problem too.
The method of calculating the net parameters is right, maybe the author was forgotten to modify the text in the paper.
We check  DAIN/networks/DAIN.py/, the Kernel Esti model is created by function: get_MonoNet5
You need to calculate the parameter use this net.
That is why the author share his code.

Oh.. OK, that makes sense. I am very sensitive to the model sizes, that's the reason of being careful.

Oh.. OK, that makes sense. I am very sensitive to the model sizes, that's the reason of being careful.

I can't find the supplemental material. Can you tell me where I can find it.


Handle errors in SSOCallback

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

https://github.com/clerkinc/javascript/assets/19269911/e13d073b-a3db-4e31-a390-659355a633f4

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Path mapping doesn't work for relative modules

Hello!
I'm trying to use path mapping feature (i.e. a "paths" config option) to redirect compiler from one local modules to another one. However, the compiler completely ignores paths when trying to import file starting with ./.
This limits my control over the paths resolution algorithm in TypeScript. Is this intentional? I doesn't see any mentions about this in the documentation.
Example
import readme from './README.md';

{
  "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "*.md": ["./empty-string.ts"]
    }
  }
}

In this example I'm trying to replace all imported markdown files with an empty string, because tsc doesn't know how to import such files. This is handled by Webpack instead.
Actual behavior
Having ./ in the import statement makes tsc to ignore paths option completely.
Expected behavior
Path mapping should work for any module names, be it relative ones or module ids from node_modules.

TypeScript Version: Version 3.9.0-dev.20200421

Path mapping is only applied to nonrelative module names like foo or bar/baz. There is currently no mechanism that allows relative names to be resolved in any way except for in a normal relative manner.


vmapping __init__ of stateful modules

Hi,
Thanks so much for this library! I am a huge huge fan of it
What is the recommended way to vmap over the init functions of stateful models?
As an example of what I mean, here is the way I usually initialize the modules in my models:
class Layer(eqx.Module):
    linear: eqx.nn.Linear
    @classmethod
    def init(cls, key):
        linear = eqx.nn.Linear(in_features=2, out_features=1, key=key)
        return cls(linear)

key = jax.random.PRNGKey(0)
three_layer_model = eqx.filter_vmap(Layer.init)(jax.random.split(key, 3))

This results in a model:
Layer(
  linear=Linear(
    weight=f32[3,1,2],
    bias=f32[3,1],
    in_features=2,
    out_features=1,
    use_bias=True
  )
)

This sort of initialization is especially useful when I have modules that run in parallel like multihead attention and seems to be used a lot in libraries like haliax and levanter.
Now if I make a stateful version of this layer:
class StatefulLayer(eqx.Module):
    linear: eqx.nn.Linear
    state_index: eqx.nn.StateIndex[Array] = eqx.field(init=False)

    def __post_init__(self):
        make_buffers = lambda **_: jnp.zeros((10, 10))
        self.state_index = eqx.nn.StateIndex(make_buffers)

    @classmethod
    def init(cls, key):
        linear = eqx.nn.Linear(in_features=2, out_features=1, key=key)
        return cls(linear)

stateful_layer = StatefulLayer.init(jax.random.PRNGKey(0))
eqx.nn.State(stateful_layer)

I end up with a state
State(0x7f7f92cb6080=f32[10,10])

Now if I do the same vmapped initialization with the stateful layer:
stateful_model = eqx.filter_vmap(StatefulLayer.init)(jax.random.split(key, 3))
eqx.nn.State(stateful_model)

I get out:
State(0x7f7f92cb6170=f32[10,10])

What I would expect to happen is something like
State(0x7f7f92cb6170=f32[3,10,10])

or
State(
  0x7f7f92cb6170=f32[10,10],
  0x7f7f92cb6171=f32[10,10],
  0x7f7f92cb6172=f32[10,10],
)

Then each layer would have its own state.
Is there a recommended way to do vmapped initialization with states?

I've found that initializing the state as part of my model and partitioning out the state after initialization has solved my use case so I will close this issue.

Actually, I'm going to reopen this one! I'm not sufficiently happy with how things are here, and you're right that this could be more ergonomic. I'm going to have a think if there's more that can be done here.

Hi Patrick, great to hear that! I'm really interested to see what kind of solution you suggest for this. I actually spent a day or so thinking about how to refactor the State and StateIndex modules to fit this use case. I'll post my solution below incase you find it useful.
So the solution I came up with involves tracking all the vmap transformations that happens to a StateIndex object through a dummy variable that I called like:
class StateIndex(Module, Generic[_Value]):
    ...
    like: Array = field(init=False)

    def __init__(self, init: Callable[..., _Value]):
        ...
        self.like = jnp.empty(())

If I use the same example as I did above,
stateful_model = eqx.filter_vmap(StatefulLayer.init)(jax.random.split(key, 3))

will result in a model with StateIndex
StatefulLayer(
  ...
  state_index=StateIndex(
    marker=<object object at 0x7fbd30ed40e0>,
    init=<function <lambda>>,
    like=f32[3]
  )
)

like should track how the state's init function should be vmapped. State's init function should then change to vmap over all of like's axes:
class State:
    ...
    def __init__(self, model: PyTree, **kwargs):
        ...
        for leaf in leaves:
            if _is_index(leaf):
                init = partial(leaf.init, **kwargs)
                for _ in range(len(leaf.like.shape)):
                    init = jax.vmap(init)
                value = init(like=leaf.like)

Making these changes I was able to get a simple example to work:
class StatefulLayer(eqx.Module):
    linear: eqx.nn.Linear
    state_index: StateIndex[Array] = eqx.field(init=False)

    def __post_init__(self):
        make_buffers = lambda **_: jnp.ones((2,))
        self.state_index = StateIndex(make_buffers)

    def __call__(self, x, state):
        buffers = state.get(self.state_index)
        return x + buffers

    @classmethod
    def init(cls, key):
        linear = eqx.nn.Linear(in_features=2, out_features=2, key=key)
        return cls(linear)

key = jax.random.PRNGKey(0)
stateful_model = eqx.filter_vmap(StatefulLayer.init)(jax.random.split(key, 3))
state = State(stateful_model)

dynamic_model, static_model = eqx.partition(stateful_model, eqx.is_array)

def apply_layer(x, input):
    _dynamic_layer, st = input
    layer = eqx.combine(_dynamic_layer, static_model)
    return layer(x, st), None

out, _ = jax.lax.scan(apply_layer, init=jnp.ones(2), xs=(dynamic_model, state))

with out having value
Array([4., 4.], dtype=float32)

as expected.
If you like this solution I'm open to working more on it to contribute to the library (although I haven't really contributed to open source projects before so you'll have to bear with me). Anyways, thanks a ton for spending some time on this.

Okay, I think I've got this working now! Take a look at #466 and let me know what you think.
I started by considering a vmap_like approach as you suggest. (Incidentally, you can make it a bit more efficient by initialising as a size-zero array, so that you don't take up any extra memory: jnp.empty((0,)).) In the end I decided against this because:

this only actually handles vmap'ing, but not any other transformation. Admittedly, right now I don't know of use-cases for transforming initialisation other than through vmap, but I wanted to be robust to anything that might arise in the future.
with the current approach, I realised it's easy to have a subtle memory leak by doing something likedef __init__(...):
    some_array = jnp.array(...)
    self.index = eqx.nn.StateIndex(lambda **_: some_array)

for which the initial some_array will never actually be deleted! It's forever stored in self.index.init.__closure__. And in fact, the built-in Equinox spectral normalisation layer did exactly this.

As such I decided that the initial state should probably be initialised at the same time as all the parameters of the model. This means changing from StateIndex(lambda **_: initial_foo) to just StateIndex(initial_foo), and then reorganising things around that. Details in #466.

Hi Patrick, this look fantastic! I agree with you that this is a cleaner solution than the vmap_like one. The only slight bit of awkwardness for my use case was that I had a model where you would want to instantiate a new state (or few states) every so often without having to instantiate an entire new model in memory. But I think one could simply do something like this to get around that
@jax.jit
def make_state(key):
    model, state = eqx.nn.make_with_state(Model)(key)
    return state

I believe this would only ever instantiate the state in memory, is that correct?
Anyways thanks again for the work you've done on this, I really appreciate it!

Yup, I think that should work!
If you get the chance to give #466 a try (before I merge it) let me know -- we can check that there's no other corner case affecting you, that I've might not have thought about.

Will do! I'll try it out and let you know later this week

Hi @patrick-kidger! Sorry for the late reply, last week got a bit busy for me. I tried out the new version of stateful and it works great. The only thing that didn't quite workout of my use case was the make_state function from my previous message. That is, when I tried running this piece of code:
`
class Counter(eqx.Module):
  index: eqx.nn.StateIndex

  def __init__(self):
      init_state = jnp.array(0)
      self.index = eqx.nn.StateIndex(init_state)

  def __call__(self, x: Array, state: eqx.nn.State) -> tuple[Array, eqx.nn.State]:
      value = state.get(self.index)
      new_x = x + value
      new_state = state.set(self.index, value + 1)
      return new_x, new_state

class Model(eqx.Module):
  linear: eqx.nn.Linear
  counter: Counter
  v_counter: Counter

  def __init__(self, key):
      # Not-stateful layer
      self.linear = eqx.nn.Linear(2, 2, key=key)
      # Stateful layer.
      self.counter = Counter()
      # Vmap'd stateful layer. (Whose initial state will include a batch dimension.)
      self.v_counter = eqx.filter_vmap(Counter, axis_size=2)()

  def __call__(self, x: Array, state: eqx.nn.State) -> tuple[Array, eqx.nn.State]:
      # This bit happens as normal.
      assert x.shape == (2,)
      x = self.linear(x)
      x, state = self.counter(x, state)

      # For the vmap, we have to restrict our state to just those states we want to
      # vmap, and then update the overall state again afterwards.
      #
      # After all, the state for `self.counter` isn't expecting to be batched, so we
      # have to remove that.
      substate = state.substate(self.v_counter)
      x, substate = eqx.filter_vmap(self.v_counter)(x, substate)
      state = state.update(substate)

      return x, state

key = jr.PRNGKey(0)
model, state = eqx.nn.make_with_state(Model)(key)
x = jnp.array([5.0, -1.0])
model(x, state)

@jax.jit
def make_state(key):
    _, state = eqx.nn.make_with_state(Model)(key)
    return state

new_state = make_state(jr.PRNGKey(1))
model(x, new_state)

`
It threw a key error at the last line. I think this was due to the fact that the line state.substate(self.v_counter) is looking for the instance of self.v_counter it was initialized with. Since the new state was initialized with a different instance of the model, it doesn't have the right key.
I'm not sure if there is a better way to make a new state without running into this problem, but I'll keep thinking about it for the next few days. Let me know if you have a clever solution. Thanks!

Hmm. The following way of remapping the keys works (and does only use public API), but it's very ugly:
...
_, state = model(x, state)  # Keep old state around

def is_index(x):
    return isinstance(x, eqx.nn.StateIndex)

@eqx.filter_jit
def make_state(old_model, old_state, key):
    mapping = []

    def get_index_mapping(leaf, old_leaf):
        if type(leaf) != type(old_leaf):
            raise ValueError("New and old have different types")
        if is_index(leaf):
            mapping.append((leaf, old_leaf))

    model, state = eqx.nn.make_with_state(Model)(key)
    jax.tree_util.tree_map(get_index_mapping, model, old_model, is_leaf=is_index)
    for marker, old_marker in mapping:
        old_state = old_state.set(old_marker, state.get(marker))
    return old_state

new_state = make_state(model, state, jr.PRNGKey(1))
model(x, new_state)

I think the above is suffiicently hard to divine that we should find a nicer way to do this.

Okay, think I figured this one out! make_with_state just goes through and replaces the keys with integers. As each invocation of make_with_state iterates over its StateIndexs in the same order, then we get the same keys at each spot in the pytree, and things are compatible. See the latest commit on #466.

Wow, great solution @patrick-kidger! I think this works perfectly and it's also quite elegant. I'm good with closing this issue now if you are. Really appreciate you working on this, helps me out a ton!

Great! I've just merged #466. Thank you for helping out with this, and this will appear in the upcoming v0.11.0 release of Equinox. :)


Twig-Extension Deprecations since Twig 2.7

Hey there, your Twig-Extension uses deprecated functions since the release of Twig 2.7. (see https://twig.symfony.com/doc/2.x/deprecated.html) for more.
Should be a very quick fix.

Done in d1678974bda7f095d956d09299694e1e26eb78d0.


test version for arctic

Description

Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[ ] Fix bugs
[ ] Add new feature
[ ] Update documentation

@luocy16 Please follow the instructions to format your code.
Ping me when you are ready.
Thanks