Links de-duplicating

I used this script to create a pair of IPFS objects, a head and a tail, with 2 links pointing from the head to the tail. The links have different names. ipfs object get $HEAD shows both of the links in place. But looking at the same object in the DAG view of the webui shows only the first link. The twin-pointer-head can be found at /ipfs/QmfYhWKZBouVU7GDzVxEG6gLetESNStsdD63KT8jUe23eV or by running that script locally.

Hi @apiarian! Seems that it has been a while since you asked this question, apologies for that.
The reason why you aren't able to get a linked list is that data structs in IPFS are DAGs.
If you still have questions related to how this works, consider opening an issue at our discussion forum https://discuss.ipfs.io/
Thanks!


Why do you use BCE loss in this formula in your paper?

Thanks.

Since the traditional form of triplet loss cannot support soft-label training. With such BCE loss, we can change the label "1" to soft labels within [0,1] to support soft-label training.

Since the traditional form of triplet loss cannot support soft-label training. With such BCE loss, we can change the label "1" to soft labels within [0,1] to support soft-label training.


Update Bitcoin codebase to support Atomic Swaps/decentralized OTC exchange

In the time when centralized exchanges are on the fall, in fear of strict regulation - It is time to enable support for decentralized and trustless on-chain and off-chain OTC (over-the-counter) exchanges between cryptocurrencies. By updating the codebase of LBRY to the newest codebase of Bitcoin, we will be able to support Atomic Swaps.
https://github.com/decred/atomicswap
Decred (https://Decred.org) made a repository here. We can fork it.
Here is a picture made by Particl, illustrating how it works: https://image.ibb.co/jcomwm/atomic_swap.png
I will also write about these issues at https://LBRY.Community

this will happen when upstream issues are merged

tracking upstream merge progress in #174


Things Needed For Docker

This container is going to be run as a reverse proxy basically.
It should:

SSL CERT: generate its own self-signed SSL cert to accept TLS traffic. User can replace with their own SSL cert after it is up and running if they want
HIGHER VERSION: we should build Apache from source so we get 2.4.38 which has quite a bit more than 2.4.29, the latest version in Ubuntu:18.04 LTS
DEFAULT SITE FILE: we should add in a default site file that sets up the correct ProxyPass directives. The IP address to pass the requests too will be a variable the user will provide on the command-line during docker run.
DOCKERFILE SECURITY: we can probably put some limits on the container by dropping certain kernel privileges, restricting resource consumption, etc. There are some easy/quick commands to do this
RANDOM: random other things I'm forgetting :)

Future Cool Stuff:

We can make a helm chart for ModSecurity!
This helm chart could be used to install ModSecurity firewall layer on any K8s cluster...going to be cool stuff

For SSL CERT, should we add https://github.com/icing/mod_md so we can generate also valid certificates using LetsEncrypt?

We should also add automated builds. The current images are 4 and 6 months old.
That's not  very trustworthy.

For SSL CERT, should we add https://github.com/icing/mod_md so we can generate also valid certificates using LetsEncrypt?

Yes very good point.

hmmm, you think its not a drag on the letsencrypt echosystem?>

The only thing is if this is a public facing IP or not. Otherwise, it won't work.
Also httpd:2.4 doesn't come with mod_md by default, so we may delay this plan a little bit.

@danehrlich1 This one is > 2 years old, lots of things have changed by now. Do you think you can create a new issue with the remaining stuff you'll like to see? I'm closing this one.


Combined deps upgrade.

👍 even though this is more than just deps upgrade!

Sure, depending what you mean. The only changes here are dep upgrades and related other changes (linting, changes to accommodate new dep versions).

Yeah, I saw the JSONField changes as that, but I was thinking of the VS Code config, CoC, useMemo, and webpack config changes; it's all 👍 though!

Yep, all those other changes directly relate to dep upgrades, except I guess adding Pylance.


Native aot stj8

Still has issues with double in netcoreapp3.1.  Not sure what to do there.
Also supposedly we can stop targeting net8 directly and just use netstandard 2.  I'll try that.

I think I'm going to keep the multitarget in the project files.  There are still a few things (like Enum.GetValues<T>()) that require it.  Also, we get the compiler warnings only when devving in .net 8.

Multi-targeting also enables us to run tests reflection enabled and disabled, so that's also handy.

Having done this a bunch these last few days, I prefer the in-source suppressions are better for reviewing/maintaining the code.

Refers to: JsonSchema.Generation/GlobalSuppressions.cs:18 in fb79d00. [](commit_id = fb79d00831e5432ae280f520cbd6ee5dba7f473d, deletion_comment = False)

I prefer the in-source suppressions are better for reviewing/maintaining the code.

I think this'll go in another PR.


Implement user confirmation for each wallet account when connecting to a dApp

Context:

Currently when a user connects a Bearby wallet to a dApp he is asked to confirm the connection once. This confirmation seems to apply not to the selected but to all available user accounts, which is not an expected behavior.
Following the benchmark practices, browser wallets like Metamask ask the user to verify the connection request for each account, once switched. There's a period of time that Metamask allows switching between already connected wallets without additional user confirmation (try to switch between 2/3 wallets of Metamask on Massa Bridge).

Feature suggestion:
Improve handling connection of accounts by asking user to validate connecting each wallet account to a specific dApp.
Dependencies:
If this feature is going to be implemented, please keep us aware in advance before going to prod, to make necessary adjustments in our code. Thanks!

@hicaru might've posted in a wrong repo, feel free to move the issue in a correct one

yes, need remake this system!

@longgamma-massa yes, acutally it more about beabry-extension))


Fixed #1028 by removing typos in Roadmap section of readme

Fixes #1029.

Codecov Report

Merging #1029 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1029   +/-   ##
=========================================
  Coverage     85.14%   85.14%
  Complexity     1038     1038
=========================================
  Files           175      175
  Lines          2834     2834
  Branches        474      474
=========================================
  Hits           2413     2413
  Misses          175      175
  Partials        246      246

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 1b0a751...d966d62. Read the comment docs.

:+1:

:+1:


Editing plotly plots and callback

When editing is enabled for plotly plots, it is, for example, possible to edit the title of the plot. I'd like to use this feature, but how can I receive the new title through a callback to allow me to save the user input? As far as I can see, plotly has a callback onUpdate, but I do not know how to use it when the plotly plot is created through a PivotTableUI.

Good question! At the moment all you can do once you've edited the plot is to save it to PNG or export it to Plotly Cloud using the buttons in the modebar. If you want to submit a PR that hooks up a callback so that you could receive update events, I'd likely accept it :)


internal_build_write should accept jc and z

Perhaps those are terrible names. Existing internal_build_write should get **kwargs until they get upgraded. jc and z will be passed with kwargs.

a bit too much


Add cortex-A55-based QEMU virtual board

This commit introduces a new board based on QEMU's virtual board. The board uses cortex-A55 as CPU and has 2 versions: SMP and non-SMP.
TODOs:

Add missing doc.
Do additional tests (currently tested non-smp/smp + sync example and hello world example)

Signed-off-by: Laurentiu Mihalcea<EMAIL_ADDRESS>

Thanks for the feedback @iuliana-prodan ! Kept only the NXP copyright header for most of the files (exception: mmu_regions.c). I decided to keep the initial copyright header as it also seemed the case for qemu_virt_arm64 (please see: 1)

Thanks for the feedback @iuliana-prodan ! Kept only the NXP copyright header for most of the files (exception: mmu_regions.c). I decided to keep the initial copyright header as it also seemed the case for qemu_virt_arm64 (please see: 1)
EDIT: it seems like in the case of soc/arm64/nxp_layerscape/ls1046a/mmu_regions.c the copyright header from baylibre was replaced by NXP's although the content of the file is the same so I'm still not 100% sure what I should do about this file.

IMO if Broadcom was the first to add this kind of file, I would keep their copyright.
Anyway, put it as you want, most probably someone in upstream (when review on zephyr) will comment and we'll see then :)

Update: Sent PR to zephyr. Will close this now.


Fix tests for using new get_node_options API

Needs: https://github.com/ros-controls/ros2_control/pull/1169
This PR adds fixes to the tests to support using the new get_node_options API that is present inside the controller interface

LGTM, but please extend also the tutorial on writing new controllers to announce the new possibility.

@christophfroehlich Done

@bmagyar I'm fixing it now. I will push them in few min

@bmagyar the semi-binary builds are passing now!


Automated cherry pick of #2823: fix: 修复安全组关联数量校验不正确问题

Cherry pick of #2823 on release/2.11.
#2823: fix: 修复安全组关联数量校验不正确问题

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.11@bd8ea72). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.11   #2825   +/-   ##
==============================================
  Coverage                ?   7.17%
==============================================
  Files                   ?     472
  Lines                   ?   74934
  Branches                ?       0
==============================================
  Hits                    ?    5376
  Misses                  ?   69105
  Partials                ?     453

Flag
Coverage Δ

#aFlag
7.17% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/guest_actions.go
0% <0%> (ø)

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 bd8ea72...a728981. Read the comment docs.

/lgtm

/approve

/lgtm

/approve


[E2E_baseline] Torchbench functorch_dp_cifar10 training accuracy crashed with RuntimeError: slow_conv2d: grad_weight must be contiguous

🐛 Describe the bug
functorch_dp_cifar10 fp32/bf16/fp16 training accuracy crashed with RuntimeError: slow_conv2d: grad_weight must be contiguous
Versions
Pytorch: git clone -b e2e-baseline https://github.com/etaf/pytorch-inductor-xpu pytorch
Test script: inductor_xpu_test.sh

Close it as we have refreshed baseline


feat: [PL-58630]: Use image version for helm-init-container

 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.


Wrong peerDependencies in react-dnd-test-utils-cjs

Describe the bug
when running npm i with the latest version of react-dnd-test-utils-cjs (9.3.9):
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

Reproduction
Steps to reproduce the behavior:

Install<EMAIL_ADDRESS>and<EMAIL_ADDRESS>Install<EMAIL_ADDRESS>Check the npm log stating the missing peer dependencies

Expected behavior
npm shouldn't warn

It this project no longer maintained?


add k2 docs and erp

Had to add category of ERP to docs, there will be more ERP systems coming soon.

Zendesk https://keboola.zendesk.com/agent/tickets/23941


chore(deps): upgrade dev dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-dev-dependencies-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2924

Questions ?
Please refer to the Backport tool documentation


genhtml step fails

Using this sample workflow step:
    - name: Report LCOV report
      uses<EMAIL_ADDRESS>      with:
        coverage-files: coverage/*.info
        artifact-name: code-coverage-report

I get the following error:
/usr/bin/genhtml --rc lcov_branch_coverage=1 --output-directory /tmp/__zgosalvez_github-actions-report-lcov/html
genhtml: No filename specified

This usually happens when the coverage files cannot be found. Please see #9 and let me know if that helps!

Thanks for responding. I still get the same error though.
Here's more from my workflow:
...
      - name: Run unit tests
        run: flutter test test --coverage --coverage-path=coverage/lcov.unit_test.info

      - name: Run integration tests
        run: flutter test integration_test --device-id windows --coverage --coverage-path=coverage/lcov.integration_test.info

      - name: Upload test coverage report
        uses<EMAIL_ADDRESS>        with:
          name: flutter_demo_test_coverage
          path: coverage

report_test_results:
      runs-on: ubuntu-latest
      needs: build_and_test
      steps:
        - uses: actions/download-artifact@v2
          with:
            name: flutter_demo_test_coverage

        - name: Report unit test coverage report
          uses<EMAIL_ADDRESS>          with:
            artifact-name: unit-test-code-coverage-report
            coverage-files: coverage/lcov.unit_test.info

        - name: Report integration test coverage report
          uses<EMAIL_ADDRESS>          with:
            artifact-name: unit-integration-code-coverage-report
            coverage-files: coverage/lcov.integration_test.info

Thanks for your feedback. I didn't correctly declare the location of the input files under  coverage-files input


How to remove unwanted style automatically applied by browser on :focus

Hi,
Not the great CSS champion here, but is there a utility class in tailwind that I can apply to avoid the browser automatically applying styling to focused elements?

As far as I know (i searched the css for it but did not find anything) there is no utility for that.
You can just add your own utility, or (to be consistent on your whole page) maybe just boring old CSS.

THat's what I thought.
The thing is - I tried so many things already, and seem to be unable to fix :-)
You happen to know of the boring yet magic css style that I need to apply?

We're going to add this soon but you can make a class like this to get you by in the mean time:
.outline-0 {
  outline: 0;
}

Or if you want it on a more global level and not as a utility you could use something like that.
nav a,
input,
select {
   outline: 0;
}

But be careful. You should add an alternate style (like border, or darker color) so a user sees what he focused. This is espacially useful when you tab through the webiste without using a mouse.

Yes, I have alternative styling.
I don’t know what my issue is, but I actually tried in many ways with outline:0 before posting here, and for some reason chrome kept on putting the ugly yellow background and blue borders...
Will have to dug into it again...
Thanks for your feedback, guys.

Op 30 nov. 2017 om 20:04 heeft Patrick<EMAIL_ADDRESS>het volgende geschreven:
Or if you want it on a more global level and not as a utility you could use something like that.
nav a,
input,
select {
outline: 0;
}
But be careful. You should add an alternate style (like border, or darker color) so a user sees what he focused. This is espacially useful when you tab through the webiste without using a mouse.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Maybe better to set :focus styles and not remove them? Because accessibility.


Missing the remove step, the script should be:
workspace=$1
SCRIPT_PATH="dirname \"$0\""
xla_path=$workspace/xla
cd $workspace
git clone -b guizili/build https://github.com/Intel-tensorflow/xla xla
bash $SCRIPT_PATH/install_bazel.sh $workspace
bash $xla_path/build_tools/sycl/install_oneapi.sh $workspace install
#bash $SCRIPT_PATH/install_l0.sh $workspace
cd $workspace
bash $xla_path/build_tools/sycl/build_xla.sh $workspace
bash $xla_path/build_tools/sycl/clean.sh $workspace

@guizili0 should we make these cmd as a new script for ci test like https://github.com/Intel-tensorflow/xla/tree/main/tools/ci_build/gpu_build?

Updated @Zantares
the new BKM to build is:
workspace=$1
SCRIPT_PATH="dirname \"$0\""
xla_path=$workspace/xla
cd $workspace
git clone -b guizili/build https://github.com/Intel-tensorflow/xla xla
bash $xla_path/tools/ci_build/sycl_build/build_sycl.sh $workspace

LGTM, I think we can submit this PR to stock OpenXLA now.

LGTM, I think we can submit this PR to stock OpenXLA now.

@ShengYang1 can you help on this? thanks.

https://github.com/openxla/xla/pull/11767

Public PR is submitted: https://github.com/openxla/xla/pull/11767, close this one.


Prevent hidden changes to user model from Confirmable

Confirmable includes a before_update method which changes email to email_was without this being made obvious, https://github.com/plataformatec/devise/blob/master/lib/devise/models/confirmable.rb#L238 . In my case, I had a list of users to import changes for, where I wanted to simply update the user email and persist the change. Devise wouldn't allow the email attribute modification to persist. The value was always persisted in unconfirmed_email. No warns or object errors were displayed. This behavior was unexpected.
After spending time looking at the confirmable module, it's obvious the intent of Confirmable is to first set the user email in the unconfirmed_email attribute, then move the value to the email attribute after confirmation.
I suggest a better pattern might be to only allow unconfirmed_email=, and add an error for the email attribute if the object attempts to call email=. Being explicit has benefits:

It prevents the end user (like me) from trying to make a change which is incompatible with Devise/Confirmable.
It notifies the end user when at attempt to set the email field takes place (record invalid).
It saves the postpone_email_change_until_confirmation_and_regenerate_confirmation_token method from having to do

self.unconfirmed_email = self.email
self.email = self.email_was

If a change in the API isn't desired for email/confirmation_email use, maybe a warn can be displayed when email is being overridden by Confirmable#postpone_email_change_until_confirmation_and_regenerate_confirmation_token ?
Thoughts?

Unfortunately there are no plans to change the API. The best you can do is to call skip_reconfirmation! that will allow you to proceed without triggering Devise's logic.

For the sake of having examples.
Current behavior
> user = User.create email<EMAIL_ADDRESS>=> #<User email<EMAIL_ADDRESS>...
> user.email =<EMAIL_ADDRESS>> user.save
=> true
> user
=> #<User email<EMAIL_ADDRESS>unconfirmed_email<EMAIL_ADDRESS>>
# zoinks! It saved but the email attribute isn't the email attribute I set!

Behavior with less side effects (I like) [API change]
> user = User.create email<EMAIL_ADDRESS>=> #<User email<EMAIL_ADDRESS>...
> user.email =<EMAIL_ADDRESS>> user.save
=> false
> user.errors.full_messages
=> ["Email must be set as unconfirmed_email"]

Behavior that might be a nice consolation [No API change]
> user = User.create email<EMAIL_ADDRESS>=> #<User email<EMAIL_ADDRESS>...
> user.email =<EMAIL_ADDRESS>> user.save
# The following is warn output
[Devise::Confirmable] Attribute email<EMAIL_ADDRESS>persisted to :unconfirmed_email
=> true
> user
=> #<User email<EMAIL_ADDRESS>unconfirmed_email<EMAIL_ADDRESS>>
# zoinks! It persisted the email attribute to email_confirmation but at least it told me.

Given API changes aren't desired, do you think the No API change behavior would be acceptable, or something similar? It'd be nice to have some type of signifier.

The issue is that this warning would then be triggered for everyone
updating an email through a view, which doesn't really make sense and also
cause confusion.
--
José Valimwww.plataformatec.com.br
http://www.plataformatec.com.br/Founder and Lead Developer

Ok. Thanks for your time.


changing code to work with passive buzzer

Line 387. Its pin
board.D13
rather than A0 for us here. Maybe its best coming from the constants (X80 or other one)

Somethings gone really weird with this now. So if I set the pin to D13 in code.py and boot.py - and uncomment the saving lines. It then by default goes to advertise and in the SW_HID mode. I connect and it connects. But then reboots. Then I see MORSE_HID advertised. I pair and connect - but it reboots. And then It doesn't connect again.. I have to remove, restart it all. And back at the beginning. I wonder if my database.txt is causing the issue.

There is file for defining x80 pins, you can change them here if needed.: https://github.com/AceCentre/morAce/blob/main/morAce/x80PinMap.py
So buzzer got working buzzer pin was set to A0 or D13?

I can copy x80_constants.py(https://github.com/AceCentre/X80/blob/main/firmware/python-single-switcher-bluetooth/x80_constants.py) to morAce but there pin variables named differently and A0 not defined in that file.
I just need to confirm pinout.
Should it look like this?
morse_button_1 = board.A4         # no pullup
morse_button_2 = board.A3         # pullup
morse_button_3 = board.A2         # pullup
connection_swap_switch = board.A1 # pullup
mode_swap_switch = board.A0       # pullup
buzzer = board.D13

Yeah - we run out. We have a bizarre way of accessing that mode_swap_switch. Give me a monent to figure it out..

Ok - short answer - its messy.
if you do any refactoring to take into account that x80_constants.py can you drop using a switch for mode_swap_switch - we will just use the morse combination. I personally feel thats better anyway
By all means keep the "if x80" lines so someone (like you and me!) can still build and test this on your own setup.

OK - I've figured this out.
So look at https://github.com/AceCentre/X80/blob/main/firmware/python-single-switcher-bluetooth/x80_constants.py
I could do with copying this file to make my head not spin. Notice https://github.com/AceCentre/X80/blob/02b79f511b82466cdd60af3de2eb2a4ffc3134ca/firmware/python-single-switcher-bluetooth/x80_constants.py#L15
I think we just need a way of defining each pin and whether they are pull-up or not. Sorry to mess up this PR as buzzer thing working well :)

So what I was referring to was the PINUP on switch1. But we are already dealing with that here:
https://github.com/AceCentre/morAce/blob/4b72c2a6f47343598267df30dd604ff2bf7c6313/morAce/boot.py#L24
So maybe thats not the problem I was seeing.

Ok - short answer - its messy. if you do any refactoring to take into account that x80_constants.py can you drop using a switch for mode_swap_switch - we will just use the morse combination. I personally feel thats better anyway

I can do this but we don't have defined morse code for mode swapping.
Currently there is morse code only for swapping connections: https://github.com/AceCentre/morAce/blob/4b72c2a6f47343598267df30dd604ff2bf7c6313/morAce/userConfig.py#L84
Alternatively I can make switching mode by using button and swapping connections only by using morse code.
Let me know which way is more preferred.

OK So we have

keyMouseSwitchMorseCode = ".-.--"
swapBleConnectionMorseCode  = "-.-.--"
user_switch = Swaping BLE connection
user_switch2 = Switching Morse & Switch control

So to clarify - Lets drop user_switch for swapping BLE Connection and make user_switch = Switching Morse & switch control. (because doing a morse combination on this wouldn't really work anyway?)

So to clarify - Lets drop user_switch for swapping BLE Connection and make user_switch = Switching Morse & switch control. (because doing a morse combination on this wouldn't really work anyway?)
ok, I will do it this way

I removed button that was on A0 pin. Now it should work without constant reboots
.

Amazing! Hero @f1andrew  ⭐


Update "Create Jupyter Notebook" command in Python extension

Now we introduced new workflow for creating jupyter notebook, we should update this page too.

The Python extension is deprecating their custom start page in favor of using the Getting Started APIs https://github.com/microsoft/vscode-python/issues/16678
After we implement the New File... contribution for Jupyter notebooks we can ensure that their new start page picks up the new flow.


plugins/lsp: Auto generate the list of lsp servers

This PR allows to auto-generate the list of all lsp servers from the plugin.
The approach taken mirrors the way upstream generates their documentation.
Closes https://github.com/nix-community/nixvim/issues/2163
Closes https://github.com/nix-community/nixvim/issues/2335

This solves: #2335

@mergify queue


ドメイン移行

into, from は間違えないでください()

Check out this link for help with updating HubPress through pull requests.
https://github.com/HubPress/hubpress.io/blob/master/Administration.adoc#update-hubpress


chore(deps): update common-dev-assets digest to c26ebe5

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
36f1bcd -> c26ebe5

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Adds global registry overrides along with invididual check registry o…

…verrides.

Thanks Zach!  This should fix #734.  Feel free to merge after builds pass.


Add missing flow for partner users to reset password

Description
I noticed that we weren't offering the ability for partner users to reset their passwords in humanesssentials.app. This PR addresses that by adding in the flow.
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Tested locally
Screenshots

Decided to merge in and let it sit in staging to test. I thought it was small enough and less risky. I wanted to get these in before stakeholder circle meeting coming up :).

This one looks good too!

Thanks @albertchae !


No Auth Provider found for name "oidc"

Hi,
I'm having problem to run locally if I use oidc authentication.
Kube config:
- name<EMAIL_ADDRESS>  user:
    auth-provider:
      name: oidc
      config:
          # .... configs ....

Hi @ernoaapa ,
I have successfully been able to run  the operator-sdk up command with a Kube Config that uses oidc as the auth-provider.
Is the kube config being used valid? i.e can you perform other cluster operations using the same kube config. Also have you tried to run the operator as a pod inside a Kubernetes cluster using the same kube config?

Hi @ernoaapa ,
If this is no longer an issue I would like to close it out. Please do let us know.

Closing this for now. Please reopen if you have any concerns.


Blog post of my GSoC week-1 progress

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind user-interface

/kind content

/kind translation

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area blog

/area documentation

/area videos

What this PR does / why we need it:
This PR contains my weekly progress of my GSoC Program. GSoC students are to submit their weekly progress in the form of blogs.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

Welcome @Rohith-Raju! It looks like this is your first PR to falcosecurity/falco-website 🎉

CC: (Mentor) @jasondellaluce

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Rohith-Raju
Once this PR has been reviewed and has the lgtm label, please ask for approval from issif. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

content/OWNERS

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, Rohith-Raju
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:

content/OWNERS [Issif]

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

LGTM label has been added.  Git tree hash: 10ccc03888cdc7fee998e8e96c7ae439a3713b59


bug(python): What are the standards for SQL

LanceDB version
0.13.0
What happened?
What are the standards for SQL, MySQL, Oracle, or something else? I want to look up some related operations
Are there known steps to reproduce?
No response

The functions available are mostly from DataFusion: https://datafusion.apache.org/user-guide/sql/scalar_functions.html
We don't support full SQL queries yet and haven't committed to a particular standard. We have a few particular customizations which are documented here: https://lancedb.github.io/lancedb/sql/#sql-filters


The New Linter Problems Database

[ ] Disable linting on whitespace between characters. I don't care.
[ ] Disable linting about long lines. It's not 1990 anymore, all developers here have access to 1080p or better monitors.

I'd also complain about whitespace style, but that ship might have sailed :P


Update Composer dependencies (2020-07-10-00-08)

Visual regression test passed!
View the visual regression test report


bug: extras/vscode not working

Did you check docs and existing issues?

[x] I have read all the LazyVim docs
[x] I have updated the plugin to the latest version before submitting this issue
[x] I have searched the existing issues of LazyVim
[x] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
0.10.2
Operating system/version
MacOS 15.1
Describe the bug
Since the latest update that added Snack.nvim, the VSCode extra stopped working as the latest changes around Snack.nvim do not consider VSCode, leading to nil references that break the config.
Here's a very quick and hacky workaround I've got "working" by editing the lazyvim source.
I just followed the errors in my vscode terminal and added conditionals to stop them from running in vscode env, so I'm sure there more places that need adjusting.
diff --git a/lua/lazyvim/config/keymaps.lua b/lua/lazyvim/config/keymaps.lua
index c4160be..26c361a 100644
--- a/lua/lazyvim/config/keymaps.lua
+++ b/lua/lazyvim/config/keymaps.lua
@@ -117,6 +117,7 @@ map("n", "[w", diagnostic_goto(false, "WARN"), { desc = "Prev Warning" })
 -- stylua: ignore start

 -- toggle options
+if not vim.g.vscode then
 LazyVim.format.snacks_toggle():map("<leader>uf")
 LazyVim.format.snacks_toggle(true):map("<leader>uF")
 Snacks.toggle.option("spell", { name = "Spelling"}):map("<leader>us")
@@ -130,6 +131,7 @@ Snacks.toggle.option("background", { off = "light", on = "dark" , name = "Dark B
 if vim.lsp.inlay_hint then
   Snacks.toggle.inlay_hints():map("<leader>uh")
 end
+end

 -- lazygit
 if vim.fn.executable("lazygit") == 1 then
@@ -153,10 +155,14 @@ map("n", "<leader>uI", "<cmd>InspectTree<cr>", { desc = "Inspect Tree" })
 map("n", "<leader>L", function() LazyVim.news.changelog() end, { desc = "LazyVim Changelog" })

 -- floating terminal
+if not vim.g.vscode then
 map("n", "<leader>fT", function() Snacks.terminal() end, { desc = "Terminal (cwd)" })
 map("n", "<leader>ft", function() Snacks.terminal(nil, { cwd = LazyVim.root() }) end, { desc = "Terminal (Root Dir)" })
 map("n", "<c-/>",      function() Snacks.terminal(nil, { cwd = LazyVim.root() }) end, { desc = "Terminal (Root Dir)" })
 map("n", "<c-_>",      function() Snacks.terminal(nil, { cwd = LazyVim.root() }) end, { desc = "which_key_ignore" })
+else
+  map("n", "<c-/>", function () require("vscode-neovim").action("workbench.action.terminal.toggleTerminal") end)
+end

 -- Terminal Mappings
 map("t", "<C-/>", "<cmd>close<cr>", { desc = "Hide Terminal" })
diff --git a/lua/lazyvim/util/mini.lua b/lua/lazyvim/util/mini.lua
index 28d38f5..feac7e7 100644
--- a/lua/lazyvim/util/mini.lua
+++ b/lua/lazyvim/util/mini.lua
@@ -121,15 +121,17 @@ end

 ---@param opts {skip_next: string, skip_ts: string[], skip_unbalanced: boolean, markdown: boolean}
 function M.pairs(opts)
+  if not vim.g.vscode then
   Snacks.toggle({
     name = "Mini Pairs",
     get = function()
       return not vim.g.minipairs_disable
     end,
     set = function(state)
       vim.g.minipairs_disable = not state
     end,
   }):map("<leader>up")
+  end

   local pairs = require("mini.pairs")
   pairs.setup(opts)
diff --git a/lua/lazyvim/util/ui.lua b/lua/lazyvim/util/ui.lua
index 14d0850..b6acc65 100644
--- a/lua/lazyvim/util/ui.lua
+++ b/lua/lazyvim/util/ui.lua
@@ -86,6 +86,10 @@ function M.foldexpr()
 end

 function M.maximize()
+  if vim.g.vscode then
+    return { map = function() end }
+  end
+
   ---@type {k:string, v:any}[]?
   local maximized = nil
   return Snacks.toggle({

I would create a PR but my lua skills are very basic and I'm sure I would cause more damage than good, but hopefully the diff can help a bit.
Steps To Reproduce

Enable vscode under extras in LazyExtras with LazyVim 13
Open VSCode

Expected Behavior
Snack.nvim and any other incompatible plugins that would break VSCode should be disabled / remapped
Repro

I'm still encountering this problem. Is it possible to reopen this issue?
I have done a clean reinstall and I can confirm 06071dd has been applied.
Failed loading lazyvim.config.keymaps

...are/nvim.d/lazy/lazy/LazyVim/lua/lazyvim/util/format.lua:182: attempt to index global 'Snacks' (a nil value)

# stacktrace:

  - /LazyVim/lua/lazyvim/util/format.lua:182 _in_ **snacks_toggle**

  - /LazyVim/lua/lazyvim/config/keymaps.lua:120

  - /LazyVim/lua/lazyvim/config/init.lua:251

  - /LazyVim/lua/lazyvim/config/init.lua:250 _in_ **_load**

  - /LazyVim/lua/lazyvim/config/init.lua:258 _in_ **load**

  - /LazyVim/lua/lazyvim/config/init.lua:184

How do you trigger this?

Thank you for your quick response!

Clean install the starter template (and run sync in lazy.nvim)
Open with VSCode Neovim

I'm still encountering this problem. Is it possible to reopen this issue? I have done a clean reinstall and I can confirm 06071dd has been applied.
Failed loading lazyvim.config.keymaps

...are/nvim.d/lazy/lazy/LazyVim/lua/lazyvim/util/format.lua:182: attempt to index global 'Snacks' (a nil value)

# stacktrace:

  - /LazyVim/lua/lazyvim/util/format.lua:182 _in_ **snacks_toggle**

  - /LazyVim/lua/lazyvim/config/keymaps.lua:120

  - /LazyVim/lua/lazyvim/config/init.lua:251

  - /LazyVim/lua/lazyvim/config/init.lua:250 _in_ **_load**

  - /LazyVim/lua/lazyvim/config/init.lua:258 _in_ **load**

  - /LazyVim/lua/lazyvim/config/init.lua:184

hi, I am new to LazyVim and got stuck at get stacktrace of loading error. May I know where/how do you get the complete stacktrace logs? (I tried :mess, Noice all not getting what I saw). Thanks a lot for your help!!

I just copy and pasted it from the VSCode window shown in the screenshot above. You can get there by opening the bottom panel with Ctrl+` to open the terminal, and clicking over to the Output tab.

I just copy and pasted it from the VSCode window shown in the screenshot above. You can get there by opening the bottom panel with Ctrl+` to open the terminal, and clicking over to the Output tab.

Ohh, it's from vscode. Got it, thanks a lot, really appreciate your help!

I just copy and pasted it from the VSCode window shown in the screenshot above. You can get there by opening the bottom panel with Ctrl+` to open the terminal, and clicking over to the Output tab.

Ohh, it's from vscode. Got it, thanks a lot, really appreciate your help!

I really can't reproduce this.
It all works as expected for me after my fix.
Can you make sure all your plugins are fully updated in regular Neovim before starting vscode?
If the problem persists, can you open your init.lua, add vim.g.vscode = 1 at the top, and then open NEovim as normal and get me the errors you see?

After making a new VSCode profile and combing through configs, I discovered the problem was a misconfiguration on my part. Sorry to have wasted your time, I'll try that first next time.

If anybody is still encountering this: open Neovim and run update in Lazy.

In my case, I moved the config folder and forgot to change $NVIM_APPNAME

@folke
I added vim.g.vscode at the top of my init.lua and here is the error I have
E5108: Error executing lua [string "v:lua"]:1: module 'snacks.statuscolumn' not found:
        no field package.preload['snacks.statuscolumn']
cache_loader: module snacks.statuscolumn not found
cache_loader_lib: module snacks.statuscolumn not found
        no file './snacks/statuscolumn.lua'
        no file '/opt/homebrew/share/luajit-2.1/snacks/statuscolumn.lua'
        no file '/usr/local/share/lua/5.1/snacks/statuscolumn.lua'
        no file '/usr/local/share/lua/5.1/snacks/statuscolumn/init.lua'
        no file '/opt/homebrew/share/lua/5.1/snacks/statuscolumn.lua'
        no file '/opt/homebrew/share/lua/5.1/snacks/statuscolumn/init.lua'
        no file './snacks/statuscolumn.so'
        no file '/usr/local/lib/lua/5.1/snacks/statuscolumn.so'
        no file '/opt/homebrew/lib/lua/5.1/snacks/statuscolumn.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
        no file './snacks.so'
        no file '/usr/local/lib/lua/5.1/snacks.so'
        no file '/opt/homebrew/lib/lua/5.1/snacks.so'
        no file '/usr/local/lib/lua/5.1/loadall.so'
stack traceback:
        [C]: in function 'require'
        [string "v:lua"]:1: in main chunk

may be happening because of snacks, found an issue that seems more related.
https://github.com/LazyVim/LazyVim/issues/4756

That's just not possible if you're using the proper way of loading LazyVim.
That error can only happen if you manually load your options.lua or don't properly import lazyvim plugins, or in the wrong order.

Or even simpler, did you disable snacks?

@dgokcin you are not even using the vscode extra!!
You have a copy of an old version of the extra https://github.com/dgokcin/dotfiles/blob/main/nvim/lua/plugins/vscode.lua
That of course won't work...
Would've helped a lot if you could have told me that. Sigh

I am having this issue after doing a clean install @mnowotnik update did not work for me. any idea what may be happening?

That is NOT a clean install...

@dgokcin you are not even using the vscode extra!!
You have a copy of an old version of the extra https://github.com/dgokcin/dotfiles/blob/main/nvim/lua/plugins/vscode.lua
That of course won't work...
Would've helped a lot if you could have told me that. Sigh

I created that file from a previous version of vscode.lua to have more control over the custom keymappings that work only on VsCode. Naturally, the fix you did 3 weeks ago did not get reflected to my local config. Sorry for your frustration, was just trying to add more functionality.
Where do you think I should put the VsCode specific keybindings that does not exist in vscode extra to avoid further issues and follow lazyvim best practices?

You can just add them to your regular keymaps.lua:
if vim.g.vscode then
-- add your mappings here
end
You also no longer need to enable the vscode extra, nor do you need to include what you have. That is all done automatically.
Feel free to create a PR to add some of those keymaps to the vscode extra, since I guess they are relevant for all users.

will do later this week, thanks!


Update readme with new failure policy details

Part of #655

/retest

/approve

/assign @kannon92 @ahg-g


Disambiguate icon for daily builds on Windows

Change icon of pwsh.exe for daily builds on Windows to this icon.
Some code had to be borrowed from build.psm1 because this script has to be self contained in case it gets executed by only downloading this file via the published download link here.
Tested on Windows 10.0.16299 (Fall Creators Update) with WMF 5.1

@SteveL-MSFT Can you please take a look?


Workshop example errors

Hey man,
Just running through the Orca workshop documentation and noticed a few of the values in the code examples don't match their description.

Thanks :) Nice catch for the 2B7.


Wrong mAP from validate.py

Hello, I'm very interested in your novel work and try to run your validate.py file, but get totally wrong mAP:
Actually, I run
python validate.py
--model_name=tresnet_l
--model_path=./models_local/MS_COCO_TRresNet_L_448_86.6.pth
but finally it printed out mAP score: 3.7.
Is something wrong with what I did?

make sure you run on the correct dataset, MS-COCO 2014 split, multi label
when you run on the correct dataset, you will get the score mentioned, I validated it myself

make sure you run on the correct dataset, MS-COCO 2014 split, multi label
when you run on the correct dataset, you will get the score mentioned, I validated it myself

OK, thank you very much, I will try!

make sure you run on the correct dataset, MS-COCO 2014 split, multi label
when you run on the correct dataset, you will get the score mentioned, I validated it myself

Sorry to trouble you again, I did get the score mentioned with MS_COCO_TRresNet_L_448_86.6.pth as you mentioned above. However, the mAP was lower than 88.4 when I tried MS_COCO_TResNet_xl_640_88.4.pth with input_size 640. I think there might be some configs in your code that I have to change when test "ResNet_xl_640_88.4.pth"?  Thanks in advance.

were you able to reproduce scores with "MS_COCO_TRresNet_L_448_86.6" (score should be 86.6) ? if you did, I think you are on the clear and can move on.
anyway, to reproduce the score with the larger model, make sure you input the correct resolution.
also, a strong tip for the future:  when you want to open a bug\problem, include full and complete details, including command line, logs, full output and so on.

were you able to reproduce scores with "MS_COCO_TRresNet_L_448_86.6" (score should be 86.6) ? if you did, I think you are on the clear and can move on.
anyway, to reproduce the score with the larger model, make sure you input the correct resolution.
also, a strong tip for the future: when you want to open a bug\problem, include full and complete details, including command line, logs, full output and so on.

Thank you for your sincere advice on how to ask a question, I did produce the score 86.6 and I will try again to reproduce the score with larger model (maybe there is some bug in my code). Anyway, I really appreciate your work.
Best wishes.


doc: releases: release-notes-3.5: update CAN ISO-TP

Add sections for CAN ISO-TP changes in this release.

Shouldn't these go into the migration guide instead? The ISO-TP API changes require code changes for anybody using ISO-TP, right?

Ah, right. I was looking for the "API Changes" section of previous release notes and couldn't find it anymore, so I assumed API change should go directly under the relevant driver/subsystem section. Found the migration guide now and will fix it.

Thanks, @martinjaeger.


feat: toggleable community sharing

Pull Request Checklist
Before submitting, make sure you've checked the following:

[x] Target branch: Please verify that the pull request targets the dev branch.
[x] Description: Provide a concise description of the changes made in this pull request.
[x] Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
[ ] Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
[ ] Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
[x] Testing: Have you written and run sufficient tests for validating the changes?
[x] Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
[x] Label: To cleary categorize this pull request, assign a relevant label to the pull request title, using one of the following:

BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry
Description
Adds a ENABLE_COMMUNITY_SHARING env var that controls whether or not the share to community button is visible. This is configurable via the admin panel as well.
Added

Configure Community Sharing - Admins can now choose to enable or disable sharing of chats to the Open WebUI Community.

LGTM, Thanks!


Feature: brew bump --installed

Verification

[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

Provide a detailed description of the proposed feature
brew bump --installed, similarly to brew livecheck --installed:
% brew help livecheck | grep installed
...
      --installed                  Check formulae and casks that are currently
                                   installed.

What is the motivation for the feature?
I'd like to be able to brew bump all of my installed formulae/casks, just in case livecheck was a false negative (example: repo-location-update) and double check with Repology. Or if I want to quickly see if there's already an open PR.
How will the feature be relevant to at least 90% of Homebrew users?
Somewhat. It adds to automating outdated checks.
What alternatives to the feature have been considered?
$ brew bump $(brew list)
Warning: Treating cmake as a formula. For the cask, use homebrew/cask/cmake
Warning: Treating docker as a formula. For the cask, use homebrew/cask/docker
...

(I do have the cmake formula but I'm actually using the docker cask)

Good idea, will review a PR to add this.

$ brew bump $(brew list)
Warning: Treating cmake as a formula. For the cask, use homebrew/cask/cmake
Warning: Treating docker as a formula. For the cask, use homebrew/cask/docker

Bit off-topic for this particular issue, but I wonder if brew list should return homebrew/cask/<name> if it detects that there's a formula with the same name.

Good idea, will review a PR to add this.

I'm looking into it. I opened livecheck.rb and bump.rb side by side hoping it might be an easy borrow. For livecheck, it looks like the filtering is done via Formula.installed. I can't find a similar construct in def bump. Is it to fetching the list via an api_response? If so, how feasible would it be to manually filter the response afterwards vs modify the api call itself?

Bit off-topic for this particular issue, but I wonder if brew list should return homebrew/cask/ if it detects that there's a formula with the same name, maybe even homebrew/core/ for the vice versa to silence the warnings.

Maybe. It depends on how brew list is used. Is brew [command] $(brew list) a common construct? Many commands already have a --installed flag. I can also maybe see users running brew list | grep <...>.But if I had to guess, it's mostly for visual checking so I'd agree with homebrew/cask/<name but not sure about homebrew/core/<name>).

Not sure off-hand, sorry. Try to hack something together in a draft PR and we can help more there.

Is brew [command] $(brew list) a common construct?

yes

I wonder if brew list should return homebrew/cask/ if it detects that there's a formula with the same name

Or have brew list --full-name return the full name for all installed formulae/casks, instead of only those not from core, which has always struck me as odd.

I think the approach in livecheck should work for bump as well.

I wonder if brew list should return homebrew/cask/ if it detects that there's a formula with the same name

Or have brew list --full-name return the full name for all installed formulae/casks, instead of only those not from core, which has always struck me as odd.

I like this idea, then bump $(brew list --full-name) would be a de facto bump --installed.

I think the approach in livecheck should work for bump as well.

I'm not sure how. The way livecheck fetches formulae is through Formula.all or Formula.installed.
https://github.com/Homebrew/brew/blob/22afefce8ea12552de0a8599297a8a8a6f5a78ef/Library/Homebrew/dev-cmd/livecheck.rb#L77-L90
I couldn't find a Formula. in bump.rb so I'm not sure how it fetches the formulae/casks. But if I had to guess, it happens in handle_api_response if no args are given (formulae_and_casks is an empty array).
https://github.com/Homebrew/brew/blob/22afefce8ea12552de0a8599297a8a8a6f5a78ef/Library/Homebrew/dev-cmd/bump.rb#L82-L89


Fixed #29517 -- Added support for SQLite column check constraints on positive integer fields.

https://code.djangoproject.com/ticket/29517

Is the release note what you had in mind?


Admin Endpoints Categories Swagger

All endpoints should have swagger
Swagger should be generated as github pages, example https://escolalms.github.io/Core/
Copy action definitions from here https://github.com/EscolaLMS/Core/blob/main/.github/workflows/swagger.yml

https://github.com/EscolaLMS/Categories/actions some files are missing
you can copy them from here https://github.com/EscolaLMS/GH-Actions-Template/tree/main/php/env


datastore: DeleteNamespace => DeleteNamespaces

This cleans up some of the tracing in the DeleteNamespace path, too.
Fixes #935

We should also issue the deletes in a single SQL statement, where possible


Ankit numbers

Pls check to add the leet code question array Numbers replacement.

Thank you for contributing.


tdesktop.tg_owt: additional fix for GCC 12 + musl

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

@ofborg build pkgsMusl.tdesktop.tg_owt

beware, tg_owt depends on webkitgtk

Looks like there is a dependency failure? I'm unable to pinpoint which one it is from ofborg logs.

Together with #217073 cherry-picked on staging-next it builds
3e6ba8d316e (HEAD) tdesktop.tg_owt: additional fix for GCC 12 + musl
f919894b06c ell: disable tests on musl
c9849777e3f (nixos/staging-next) Merge #217024: ruby_3_0: fix build on darwin

$ nix build -f . pkgsMusl.tdesktop.tg_owt

$

rebased with the ell PR, now it builds (reliably):
$ nix build github:yu-re-ka/nixpkgs/musl-tg-owt#tdesktop.tg_owt

$

@ofborg build tdesktop.tg_owt


Installation difficulties - Not all systems have /usr/bin/mkdir

OS: Ubuntu 20.04
Nokogiri Version:  1.10.10
While trying to install nokogiri, it looks for /usr/bin/mkdir if it's not found it fails. I was able to circumvent it using the following trick
$ sudo ln -s /bin/mkdir /usr/bin/mkdir

It would be great if nokogiri looks for mkdir rather than /usr/bib/mkdir to prevent this issue. The full output is attached here:
nokogiri installation issue.txt

Hi @mindaslab, thanks for opening this issue, and I'm sorry you're having trouble.
This is very curious, as I develop and maintain Nokogiri on Ubuntu 20.04 and have never seen this issue on my system. Can you help me reproduce it?
Let's start with the bits you skipped when you reported this -- the template for an installation issue asks a few questions:

Have you read and followed the installation tutorial at http://www.nokogiri.org/tutorials/installing_nokogiri.html?
What are the complete contents of the mkmf.log file generated during the failed installation?
Please include the output of uname -a and the contents of /etc/lsb-release.

If you could reply with answers to those questions then I may be able to direct our attention a bit better.

I googled a bit and found a similar issue from the mysql2 gem: https://github.com/brianmario/mysql2/issues/724
Can you also please reply with the value of RbConfig::MAKEFILE_CONFIG['MAKEDIRS']? And can you tell us where your Ruby came from (rvm, rbenv, chruby, apt, ...)?

@flavorjones thanks for looking into this. I'm running into the same issue and the result of RbConfig::MAKEFILE_CONFIG['MAKEDIRS'] is similar to the output in the mysql2 gem issue:
 :001 > RbConfig::MAKEFILE_CONFIG['MAKEDIRS']
 => "/usr/bin/mkdir -p"

My Ruby came from rvm (version 1.29.10) and my Ruby version is version 2.7.1 [ x86_64 ] on Ubuntu 20.04 as well.
The mkdir command for me is located at /bin/mkdir.

@dko26 Did RVM compile this ruby locally during installation, or did it install a precompiled binary from somewhere? I'm assuming it's the latter (precompiled binary) but it might be helpful to confirm that.

@flavorjones yes you're right, it's installing a precompiled binary:
$ rvm reinstall ruby-2.7.1
ruby-2.7.1 - #removing rubies/ruby-2.7.1 - please wait
Searching for binary rubies, this might take some time.
Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/20.04/x86_64/ruby-2.7.1.tar.bz2
Checking requirements for ubuntu.
Requirements installation successful.
ruby-2.7.1 - #configure
ruby-2.7.1 - #download
ruby-2.7.1 - #validate archive
ruby-2.7.1 - #extract
ruby-2.7.1 - #validate binary
ruby-2.7.1 - #setup

Hi everyone,
I am not a very fluent Linux / Ubuntu 20.04 user and seems to experience the same problem as @mindaslab
I get a very long stack trace which ends by
cc1: warning: unrecognized command line option ‘-Wno-self-assign’
cc1: warning: unrecognized command line option ‘-Wno-parentheses-equality’
cc1: warning: unrecognized command line option ‘-Wno-constant-logical-operand’
linking shared-object nokogiri/nokogiri.so
Cleaning files only used during build.
rm -rf /home/maxence/.rvm/gems/ruby-2.7.1/gems/nokogiri-1.10.10/ext/nokogiri/tmp/x86_64-pc-linux-gnu/ports
rm -rf /home/maxence/.rvm/gems/ruby-2.7.1/gems/nokogiri-1.10.10/ports

current directory: /home/maxence/.rvm/gems/ruby-2.7.1/gems/nokogiri-1.10.10/ext/nokogiri
make "DESTDIR=" install
make: /usr/bin/mkdir: Command not found
make: *** [Makefile:202: .sitearchdir.-.nokogiri.time] Error 127

make install failed, exit code 2

Gem files will remain installed in /home/maxence/.rvm/gems/ruby-2.7.1/gems/nokogiri-1.10.10 for inspection.
Results logged to /home/maxence/.rvm/gems/ruby-2.7.1/extensions/x86_64-linux/2.7.0/nokogiri-1.10.10/gem_make.out

Can I use @mindaslab fix as a permanent fix (provided my error is indeed same)?

@maxence33 I'm not really sure how permanent it is but it's been working fine for me since I applied the fix at least.

Hi all,
I spent a few minutes looking into this today to determine whether an upstream issue should be opened at https://github.com/rvm/rvm/issues.
Maybe the most interesting thing I discovered is that the Ubuntu-published docker image for 20.04 (focal) contains /usr/bin/mkdir:
$ docker run -it ubuntu:focal ls -lt /usr/bin/mkdir /bin/mkdir
-rwxr-xr-x 1 root root 88408 Sep  5  2019 /bin/mkdir
-rwxr-xr-x 1 root root 88408 Sep  5  2019 /usr/bin/mkdir

Big if true -- this might explain why Ruby is compiled assuming /usr/bin/mkdir will always be present. I'll open an issue upstream and link to it.

Hey all, I've been trying for the last few hours to get Ubuntu Focal running in a VM to reproduce what you're seeing, but it's turned into a huge yak shave and so I need to ask for your help.
Can someone directly affected by this issue please file an issue upstream at https://github.com/rvm/rvm/issues ? You may want to reference https://github.com/rvm/rvm/pull/4922 as well as @raelgc who is the kind person who's volunteered to build the RVM binaries for Ubuntu.
Sorry I can't be of more direct help here.

I just got here with the same issue. Did anyone file the issue upstream yet? I don't see anything referenced. :(

I think it's not Nokogiri related but rather on how RVM is bundling Ruby 2.7.1

I got the same issues as well when updating from ruby 2.7.0 to 2.7.1 and running bundle install. Patch on top worked fine.

Hi! If you're directly affected by this issue, please don't comment here. Instead, please report it upstream as requested above:

Can someone directly affected by this issue please file an issue upstream at https://github.com/rvm/rvm/issues ? You may want to reference rvm/rvm#4922 as well as @raelgc who is the kind person who's volunteered to build the RVM binaries for Ubuntu.

As a workaround, you can run sudo ln -s /bin/mkdir /usr/bin/mkdir but the root cause is that the precompiled Ruby that's being distributed by RVM assumes the toolchain you're using includes /usr/bin/mkdir which doesn't exist in the base distro (but notably and inexplicably does exist in the official Docker image).
Thanks for being a good open-source community member and reporting this upstream.


use a variable everywhere

I was just looking at the script and seen $destination could be used
in another place instead of duplicating '/usr/lib/ignition'

LGTM, other than the noted nit.

Thanks for the review, sorry for the vague title, I did not want to each 80 character limit, so the title would have been bigger than this insignificant patch itself. :)

Right, but we try to maintain high standards around commit messages. See for example https://github.com/coreos/ignition-dracut/commit/76246ca24510cbb0ae4356262c6c876442e3ae3f

Right, but we try to maintain high standards around commit messages. See for example 76246ca

dully noted, thanks


Declare dependencies in metadata

I'm attempting once again to allow Setuptools to declare dependencies. Due to known bootstrapping issues, it's not possible to declare simply the dependencies (especially any dependencies that require setuptools to install) without considering the bootstrapping issue.
This change offers a fallback to add a directory of dependencies to be added to sys.path when Setuptools/pkg_resources is imported/invoked.

I'm still unsure why the test failures are occurring. They don't occur for me locally, even on Python 3.6. The failures are all in the test_pip_upgrade_from_source tests. I have Python 3.6.6 while the Github actions has 3.6.14.

The failures have at least two modes. On pip 9.0.1, it fails early checking for setuptools being installed. On 18.3, the tests fail when attempting to install the dependencies:
Processing ./setuptools-58.0.0.post20211020-py3-none-any.whl
Collecting pyparsing==2.2.1 (from setuptools==58.0.0.post20211020)
  Using cached https://files.pythonhosted.org/packages/42/47/e6d51aef3d0393f7d343592d63a73beee2a8d3d69c22b053e252c6cfacd5/pyparsing-2.2.1-py2.py3-none-any.whl
Collecting ordered-set==3.1.1 (from setuptools==58.0.0.post20211020)
  Using cached https://files.pythonhosted.org/packages/a3/b7/d4d69641cbe707a45c23b190f2d717466ba5accc4c70b5f7a8a450387895/ordered-set-3.1.1.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
    ModuleNotFoundError: No module named 'setuptools'

I believe the issue is that prior to pip 20, there wasn't adequate support for building source packages without setuptools being implicitly installed.
I think I'm prepared to declare non-support for installation from source with these older pips.

I believe the reason why the tests don't fail for me locally is because I have a local pip cache with things like 'ordered-set' already built into a wheel.

I think I'd prefer the vendored blobs not to be checked into Git but rather gitignored. There could be a script that would populate them separately. Thinking along the lines of what I attempted in python/cpython#12791.

I'd consider something along these lines. I think we can consider that change separately, no?

FFS. Now tests are failing with some error in flake8.
________________________________ FLAKE8-check _________________________________
[gw0] linux -- Python 3.6.15 /home/runner/work/setuptools/setuptools/.tox/python/bin/python
.tox/python/lib/python3.6/site-packages/pluggy/_hooks.py:265: in __call__
    return self._hookexec(self.name, self.get_hookimpls(), kwargs, firstresult)
.tox/python/lib/python3.6/site-packages/pluggy/_manager.py:80: in _hookexec
    return self._inner_hookexec(hook_name, methods, kwargs, firstresult)
.tox/python/lib/python3.6/site-packages/_pytest/runner.py:170: in pytest_runtest_call
    raise e
.tox/python/lib/python3.6/site-packages/_pytest/runner.py:162: in pytest_runtest_call
    item.runtest()
.tox/python/lib/python3.6/site-packages/pytest_flake8.py:127: in runtest
    self.statistics)
.tox/python/lib/python3.6/site-packages/py/_io/capture.py:150: in call
    res = func(*args, **kwargs)
.tox/python/lib/python3.6/site-packages/pytest_flake8.py:222: in check_file
    app.report_errors()
.tox/python/lib/python3.6/site-packages/flake8/main/application.py:309: in report_errors
    results = self.file_checker_manager.report()
.tox/python/lib/python3.6/site-packages/flake8/checker.py:249: in report
    results_reported += self._handle_results(filename, results)
.tox/python/lib/python3.6/site-packages/flake8/checker.py:161: in _handle_results
    physical_line=physical_line,
.tox/python/lib/python3.6/site-packages/flake8/style_guide.py:430: in handle_error
    code, filename, line_number, column_number, text, physical_line
.tox/python/lib/python3.6/site-packages/flake8/style_guide.py:581: in handle_error
    self.formatter.handle(error)
.tox/python/lib/python3.6/site-packages/flake8/formatting/base.py:100: in handle
    self.write(line, source)
.tox/python/lib/python3.6/site-packages/flake8/formatting/base.py:203: in write
    self._write(line)
.tox/python/lib/python3.6/site-packages/flake8/formatting/base.py:187: in _write
    sys.stdout.buffer.write(output.encode() + self.newline.encode())
E   AttributeError: '_io.StringIO' object has no attribute 'buffer'
------------------------------ Captured log call -------------------------------
WARNING  flake8.options.manager:manager.py:221 option --max-complexity: please update from optparse string `type=` to argparse callable `type=` -- this will be an error in the future

Aaah. It's because there was a lint error (unused import) and the error handling between pytest and flake8 is broken.

Strangely, when I create a virtualenv locally, I don't end up with pyparsing in it. Is it pytest-virtualenv that's adding it?

Okay, I see it now. pyparsing is present in c:\hostedtoolcache\windows\python\3.9.7\x64\lib\site-packages. But virtualenv isn't supposed to give access to system-site-packages by default.
~ $ virtualenv --help | grep 'site-packages dir'
  --system-site-packages        give the virtual environment access to the system site-packages dir (default: False)

So why is a package from the system site packages leaking into a (bare) virtualenv?

Ugh. The problem is that bare_virtualenv.run doesn't honor the virtualenv on Windows:
> c:\code\public\pypa\setuptools\setuptools\tests\test_virtualenv.py(48)test_clean_env_install()
-> bare_virtualenv.run(['python', 'setup.py', 'install'], cd=tmp_src)
(Pdb) bv = bare_virtualenv
(Pdb) bv.run(['python', '-c', 'import sys; print(sys.executable)'])
C:\Python39\python.exe

Okay, so in pytest-virtualenv, it's crucial to pass .python for the executable or use the full string syntax. Otherwise, the subprocess may find "python" on the path and not in the virtualenv.

Point taken, but what happens if the technique for bundling dependencies has negative downstream
effects? Then the only option is to back out the whole change and not just the bundling behavior.

That's an interesting question. Note that downstream distro packages absolutely love unbundling the vendored deps and depend on packages that are already packaged for their ecosystem. So I'd say they already have to deal with stuff like this.
Of course, it may somehow be problematic as those packages may have an undesired version.
There's a solution for this — ansible/ansible has a special location with a .gitignore in its tree — a _vendor/ folder. The assumption is that if the packagers have problems with getting the desired deps packaged separately, they could just drop them into that folder and those deps would become available on the import path.
Essentially, the point is that downstreams usually have their own ways to populate this sort of stuff (or vice versa — purge the vendored content).

I agree that it's undesirable to have this bulk content in the repo, so I would like to avoid that.
I'd also like to be able to support pip install from Github, e.g.:
$ pip-run git+https://github.com/pypa/setuptools@feature/unvendor -- -c "import setuptools, appdirs; print(appdirs.__file__)"
...
Successfully installed appdirs-1.4.3 more-itertools-8.8.0 ordered-set-3.1.1 packaging-20.4 pyparsing-2.2.1 setuptools-58.2.0.post20211022 six-1.16.0
/var/folders/c6/v7hnmq453xb6p2dbz1gqc6rr0000gn/T/pip-run-bcrng0_h/appdirs.py

It's not obvious to me how that could work if the content isn't already bundled in the repo.

May I suggest implementing the download logic + caching in the PEP 517 in-tree build backend? If the dirs are already populated, it'd skip the download (after checking the checksums, I guess).
P.S. Apparently pip's vendoring script is now available on PyPI: https://github.com/pypa/pip/tree/main/src/pip/_vendor#automatic-vendoring / https://pypi.org/project/vendoring/. Maybe it's worth checking it out.

Plus, I observe that the content is currently already bundled in both pkg_resources/_vendor and setuptools/_vendor, so this change limits that effect.
I can rewrite the history to remove .whl files for now, as they're unusable.

Yeah, I'm mostly unhappy with things like whl/exe at this point. It'd be great to catch these with linters. Maybe there's some pre-commit hook repo disallowing blobs?

I'm abandoning this effort for now.


Cannot add columns

I am trying out Dolt, and have a basic repository. I want to add a column named "word_class", but was not successful so far. What I have tried is:

use dolt sql --query 'ALTER TABLE vocabulary ADD word_class VARCHAR (20) NOT NULL'
use the dolt sql command line with the same command
use schema add-column --not-null --tag=3 vocabulary word_class VARCHAR (20) NOT NULL

For the third one, I am getting an error saying varchar is not a valid type for this new column
For the first two Error parsing SQL: syntax error at position 37 near 'word_class is the error I am getting.
I am relatively new to databases, and maybe I am doing something wrong, so if someone could guide me, that would be great. Please close the issue if it's not a bug.

Hi bitigchi,
Thanks for the report!
Your example 1) is valid SQL and should work. This is a bug with the SQL parser library we're using, which we plan to fix but haven't yet. You need to put the column definition in parenthesis like this:
dolt sql --query 'ALTER TABLE vocabulary ADD (word_class VARCHAR (20) NOT NULL)'
We'll leave this open until we've fixed the parser.

Thank you!

The parser supports this statemht now :-)


Game speed

Is it only me but I see that games speed is super fast and the sound bad? https://jsnes.org/

"a little fast"? It is totally unplayable and useless.

I play it all the time, it's playable. In the matter of face the speed is not even really noticeable. I'm having little to no problem on my end. I can even show you a video, if you want.

I do, please. If it is different I will show video also. Maybe problem is on my side

Version 67.0.

I can confirm it's not just you. Tetris seems super responsive compared to other emulators, but the speed just kills the game.

This is a known problem! Unfortunately we assume that your monitor's refresh rate is 60 fps, the same as the NES's. Your refresh rate is probably faster than that.
I made an attempt at detecting refresh rates and falling back to setInterval, but it didn't work properly so I disabled it: https://github.com/bfirsh/jsnes-web/blob/master/src/FrameTimer.js
More details here: https://github.com/bfirsh/jsnes-web/issues/15

I don't know about that man, I'm running requestAnimationFrame at 58-60 frames.
Here's a comparison with other emulators. As you can see the difference is quite drastic.

@bfirsh Sound also runs faster, in sync with video I'd say.

I have the same problem, if I play a ROM in PAL region originally designed for 50Hz, game will running too fast.

Probably fixed by https://github.com/bfirsh/jsnes-web/pull/195 and https://github.com/bfirsh/jsnes-web/pull/196. Can all here confirm?

@bfirsh The latest master branch fixed my game speed problem in android chrome. Thanks!


[Docs] Add chatTTS backend

Explanation
Add chatTTS install documentation.
Related issue
#3547
What type of PR is this
/kind documentation

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!


Block schema validation

as #275 but for blocks. Although, blocks can only be written by other nodes, they should be rejected without a vote if the structure is incorrect

related to #311
If a block is written with an invalid schema it should still be voted invalid, right?

BigchainDB Server never validated the schema of a built block. It did that for votes, go figure. But none of that matters anymore, because BigchainDB Server no longer builds blocks or votes. That job is handled by the consensus engine used by BigchainDB 2.0; it is no longer the concern of BigchainDB Server. This is no longer an issue so I'm closing it.


Enable pip caching

@nathanielmanistaatgoogle I threw in a little clean-up refactoring in build_python.sh in prep for whatever comes of future efforts to split external dependency build steps from gRPC build steps.
Somewhat fixes #3623 (but there'll be more on that front for everyone's general build-flakiness-due-to-network-snafus). The basic requirement, as with any caching solution, is that at least one of the previous builds with the same version requirements succeeded.
Tagged DNM to watch what happens on Jenkins.

LGTM but @nicolasnoble will lead review.

(confirming the existence of the populated pip caches on the testing servers outside of the images)


fix: not allowing to alter schema on non-extension

This bug was introduced by fcb20b39de2c56f066ac68066ffa4ea870d92d1a (https://github.com/supabase/supautils/pull/94)
Looks like it escaped review because of https://github.com/supabase/supautils/issues/79.

@soedirgo This CI job is failing: https://github.com/supabase/supautils/actions/runs/12319279442/job/34386154273, is it important?

Something about AWS credentials https://github.com/supabase/supautils/actions/runs/12319279442/job/34386241082

The error is something about AWS credentials

That job is cancelled because of the first error you linked; probably something up with the upload-release-asset action


Share events to Python without copying via arrow crate

Implements the proposal in #224 on top of #213.
TODO:

[ ] Testing
[ ] Add examples that use data_arrow and/or send_output_arrow
[x] Don't assume that events are dropped before next recv call in EventStream

Instead, send the drop tokens via a channel on Drop

Future work:

Avoid copying outputs by adding a method to prepare a zero-initialized ArrowArray backed by shared memory
On sender side: When no drop token is received in reasonable time, remove the shared memory region

This will prevent the creation of new mappings to that region
Already mapped data is kept and only removed when all processes have unmapped it again -> no undefined behavior
Removing the shared memory region makes sense because we probably can't reuse it safely.

Support additional Arrow data types (not just arrays)
Use Arrow data types in Rust/C/C++ APIs too?

Hi Philipp, thanks for making this possible!
I don´t really want to maintain both PyBytes and Arrow. PyBytes has its fair share of edges as well in Python. I would prefer to only keep one if that's possible. Did you keep the PyBytes because you feel like Arrow is still quite unsafe?
Or it's too not break backward compatibility only, which I can manage for dora-drives. PyArrow and np.array are quite interchangeable so in the case of dora-drives. The replacement should be quite easy.

I think we can postpone this: Avoid copying outputs by adding a method to prepare a zero-initialized ArrowArray backed by shared memory.
If we have zero-copy on read the performance will already be really good.

Support additional Arrow data types (not just arrays)

So, I think that we don't have to support all data-types. But one that can be interesting is a HashMap data-types. This way we can encapsulate our metadata type as Arrow. We can even use something like serde_arrow and derive our struct without having to do all the ser/de implementation at the API level. ( e.g. : metadata_to_pydict )
One thing that I personally think is really important is to be able to forward the data-shape, the number of column and row.
We can postpone all other data-types for now.

Use Arrow data types in Rust/C/C++ APIs too?

I think that we can postpone this until we have more clarity on the feature set we want to use out of Arrow. This would avoid having to maintain the 3 API while proving the concept.

I'm having issue running the our python example. It seems that the data is not been received by the receiving node, even though it's sent by the sent node. I have tried to use data_arrow and send_output_arrow but it did not work.

Thanks for testing! I'm not sure what's going wrong yet, by I see these issues too. To make debugging easier, I started to split off unrelated changes into separate PRs, starting with #246.

I pushed some new commits that should solve the issues. The main issue was that the code still assumed that an event is deterministically dropped before the next event is requested. This is no longer the case since the user code and the Python garbage collection can hold on to the event for longer. To fix this, we now collect the drop tokens asynchronously. We also release the GIL while waiting for events to allow the Python garbage collection to run. I also fixed some other potential bugs and implemented some improvements (e.g. for InputClosed reporting).
The webcam tests work fine for me know. Maybe you could do another round of testing too?

So, I was able to run the example without issues and even make a quick benchmark and it seem very fast! The fastest I have on record for large data!
This branch:

Version
platform
Message size (bytes)
Latency in (ns)

dora-rs arrow Python
<EMAIL_ADDRESS>8
19,183

dora-rs arrow Python
<EMAIL_ADDRESS>64
1,003

dora-rs arrow Python
<EMAIL_ADDRESS>512
967

dora-rs arrow Python
<EMAIL_ADDRESS>2048
1,049

dora-rs arrow Python
<EMAIL_ADDRESS>4096
1,100

dora-rs arrow Python
<EMAIL_ADDRESS>16384
1,139

dora-rs arrow Python
<EMAIL_ADDRESS>40960
891

dora-rs arrow Python
<EMAIL_ADDRESS>409600
980

dora-rs arrow Python
<EMAIL_ADDRESS>4096000
1,561

dora-rs arrow Python
<EMAIL_ADDRESS>40960000
4,613

Fastest on record:

Version
platform
Message size (bytes)
Latency in (ns)

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>8
538

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>64
523

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>512
282

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>2,048
546

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>4,096
530

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>16,384
579

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>40,960
416

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>409,600
698

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>4,096,000
2,184

dora-rs iox arrow2 Python
<EMAIL_ADDRESS>40,960,000
8,946

dora-rs iox Rust
<EMAIL_ADDRESS>64
239

dora-rs iox Rust
<EMAIL_ADDRESS>512
279

dora-rs iox Rust
<EMAIL_ADDRESS>2,048
270

dora-rs iox Rust
<EMAIL_ADDRESS>4,096
276

dora-rs iox Rust
<EMAIL_ADDRESS>16,384
293

dora-rs iox Rust
<EMAIL_ADDRESS>40,960
298

dora-rs iox Rust
<EMAIL_ADDRESS>409,600
420

dora-rs iox Rust
<EMAIL_ADDRESS>4,096,000
890

dora-rs iox Rust
<EMAIL_ADDRESS>40,960,000
7,020

Notes that I only runned this once and shall only taken into account as a big O.

When I try the latest branch, calling the very first send_output with an arrow array type (independent of the size) takes ~200ms regardless of the size.
It seem that when using PyBytes the second message is slightly delayed:
message_count=0
latency_receiver_sender=30357.60999955528
message_count=1
latency_receiver_sender=173435.58199900144
message_count=2
latency_receiver_sender=73164.8419987323

@haixuanTao Thanks for testing! There were some remaining bugs related to stopping as well, so I pushed a set of new commits to refactor, simplify, and fix these issues. Some of these bugs might also be related to the latency issues you experienced. Maybe you could try again with the latest commit?

When using value on a PyBytes sent item, the second message read is slightly delayed:

The format used for sending and the format used for receiving should be fully independent. The API translates both PyBytes and arrow arrays to a Rust Vec stored in shared memory, On the receiver side, we convert it back to the requested Python type.

Ok, the error I have reported is actually linked to pyarrow and not dora itself. I have opened a issue: https://github.com/apache/arrow/issues/34994
I'm going to keep on testing and keep you updated.

Ok, so I don't see any other issue. It would be great to be able to send arrow with operators, so that I can make a first POC with dora-drives.

Thanks for testing! I just added support for sending arrow arrays from operators in 235f6da.

So, there is a weird error that prevent user from calling two times dora_event["data"], in the sense that:
    def on_event(
        self,
        dora_event: dict,
        send_output: Callable[[str, bytes], None],
    ) -> DoraStatus:
        if dora_event["type"] == "INPUT":
            length = dora_event["value"]

            length = dora_event["value"] # <--- this will fail

        return DoraStatus.CONTINUE

The error is going to be the following:
https://github.com/dora-rs/dora/blob/235f6da79db917e7492a868f42aa1f7fed8de25f/apis/python/operator/src/lib.rs#L31
We can either fix it or give a heads up.

Thanks for testing! I pushed c1544f8 to fix this issue.

I have tested it again but i'm seeing slightly longer latency with the same code replacing node with operator. I will investigate more later on.
dora Node,8,514.0151
dora Node,64,518.3472199999999
dora Node,512,539.93719
dora Node,2048,507.9925899999999
dora Node,4096,610.57567
dora Node,16384,760.21873
dora Node,40960,2484.4595199999994
dora Node,409600,2773.14837
dora Node,4096000,1728.2458500000002
dora Node,40960000,6397.578890000001
dora Operator,8,7823.535460006497
dora Operator,64,1139.437851472196
dora Operator,512,1319.1025445623814
dora Operator,2048,1319.3751484989364
dora Operator,4096,1377.7049504851404
dora Operator,16384,1210.5615544644727
dora Operator,40960,549.8982871241685
dora Operator,409600,841.9508415788033
dora Operator,4096000,4740.129366341941
dora Operator,40960000,29820.334663385765

So, I think that's its linked to the current implementation of the SendOuputCallback https://github.com/dora-rs/dora/blob/3a35c222ea3da168049be5abe8023907da38d832/binaries/runtime/src/operator/python.rs#L272-L273 that requires an additional ownership to share the data with the runtime through a channel. https://github.com/dora-rs/dora/blob/3a35c222ea3da168049be5abe8023907da38d832/binaries/runtime/src/operator/python.rs#L280
I wonder if we can remove the runtime channel copy

Thanks for investigating!

Just FYI, I have tested it again but i'm seeing slightly longer latency with the same code replacing node with operator.

It's a bit strange that the operator latency is much smaller than the node latency for message sizes 40960 and 409600. For all other data sizes, it's the other way around. Do you have any idea why this is the case?

So, I think that's its linked to the current implementation of the SendOuputCallback that requires an additional ownership to share the data with the runtime through a channel.

Yeah, this definitely has some additional costs for larger messages. I'll look into it.

Thanks for investigating!

Just FYI, I have tested it again but i'm seeing slightly longer latency with the same code replacing node with operator.

It's a bit strange that the operator latency is much smaller than the node latency for message sizes 40960 and 409600. For all other data sizes, it's the other way around. Do you have any idea why this is the case?

will check absolutely as well as for small message!

So, I think that's its linked to the current implementation of the SendOuputCallback that requires an additional ownership to share the data with the runtime through a channel.

Yeah, this definitely has some additional costs for larger messages. I'll look into it.

Should be fixed by 1948a45.

I know get the close latency value for both node and operator:
dora Node,8,545.4713700000001
dora Node,64,533.91939
dora Node,512,548.10928
dora Node,2048,851.3406300000001
dora Node,4096,1078.9238400000002
dora Node,16384,1121.3838500000002
dora Node,40960,1113.2833500000002
dora Node,409600,1230.84563
dora Node,4096000,1636.1486600000003
dora Node,40960000,4848.450280000001
dora Node,8,908.44376
dora Operator,8,817.0425798016367
dora Operator,64,688.4469109383357
dora Operator,512,1090.3208020692437
dora Operator,2048,1117.994148606356
dora Operator,4096,1177.8792475452785
dora Operator,16384,1150.2645544835716
dora Operator,40960,1158.827108732715
dora Operator,409600,1305.7527920152845
dora Operator,4096000,1759.6348711101587
dora Operator,40960000,4455.981317012557

Thanks for the quick fixe.

Great, thanks for testing! Is there anything else blocking this PR or do you think it's ready to be merged?

Great, thanks for testing! Is there anything else blocking this PR or do you think it's ready to be merged?

I'm working on the dora-drives export to arrow. There is couple of things I'm still working on. I should be able to approve this PR by today.

Ok, so I finally find out my issue within dora-drives which is unrelated to our implementation.
I had an issue with numpy that was badly converting types to uint8 using .view(np.uint8) when the array was non-contiguous.
This has been fix in numpy>=1.24 but is a silent error for previous version.


Update URL in the browser address bar when a particular project or tag in the left panel is selected

/project/<project_name>/<project_id>
/tag/<tag_name>


math/big: ModSqrt returns wrong value when aliasing parameters

What version of Go are you using (go version)?
go 1.9
What operating system and processor architecture are you using (go env)?

darwin_amd64
Playground

What did you do?
Aliased z and x in ModSqrt, as allowed by the package docs and not disallowed by the function docs.
y.ModSqrt(y, p.P)

https://play.golang.org/p/MsOief8jlg
What did you expect to see?
The same result as new(big.Int).ModSqrt(y, p.P).
What did you see instead?
An incorrect value is computed.

The optimized path modSqrt3Mod4Prime introduced by ea0491b70a82a207a951f869c7c1e5a52dbf410f starts with z.Set(p), which when aliasing will improperly set x = p, too.


crypto/tls: apply NSS SSLv3 fix

https://golang.org/cl/161700043/

SSLv3 is deprecated: https://tools.ietf.org/html/rfc7568
I don't think we should be doing anything here to help SSLv3.

Agreed.


[FEATURE] Access to plugin configurations (pwa-bundles.json)

Description
Now the pwa-bundles.json gets generated when running shopware-pwa plugins. In the pwa-bundles.json some values i have to use in my code are defined. Think of apiKeys and some configuration values for my plugins. Is it a good idea to make this available also to the client in someway that we can blacklist sensitive keys or whitelist only the one we need?
Example
The Array below exists in pwa-bundles.json:
"shippingMethods": [
          "a4139c276ad24bf1ab51cebce3864345"
 ]`

This array consist of the id of the shippingMethod named pickup.
On the homepage i have a few dynamic buttons which will display a button to select the shippingMethod pickup. Now i need to hardcode the name of the shippingMethod to filter it out of the shippingMethods object of useCheckout.
If i could use the array from pwa-bundles.json, it would be dynamic on buildtime .
Acceptance criteria

[blacklist sensitive values or whitelist non-sensitive values]
[Make pwa-bundles.json available to use in code]

Hey @meeshoogendoorn
I've been experimenting with this and I believe recent changes in defaultConfig are coming with help.
I would prefer to avoid exposing the whole pwa-bundle.json file to the frontend, as you pointed out - it might cause problems with important data leaks.
What would you say for the solution below? In shopware-pwa.config.js
const defaultsConfigBuilder =
  require("@shopware-pwa/nuxt-module/api-defaults").default
const pluginConfig = require("./.shopware-pwa/pwa-bundles.json")

// your custom things in config
defaultsConfigBuilder().replace("useCms.limit", 15)
defaultsConfigBuilder().add("useCms.includes.product", "extensions")

// here you can add your own key, for example for your composable/plugin
defaultsConfigBuilder().add("myPluginDefaults", pluginConfig['my-plugin-name'].configuration.yourKey)

module.exports = {
 ...
}

This way you have control over what's exposed to the frontend on build time.


Save errors/warnings in IRegistration & visualize errors in the registration table

If an error is present on a registration, show it in the registration table, rather than a dedicated error table

Potentially something like this:


[Animated] Interpolation between hex-encoded colors is unsupported

Ex: setting the output range to ['#fff', '#2966fb'].

Yeah it looks like just rgba is supported right now, this would be nice to have though

d3-interpolate combined with d3-color accomplishes this nicely, perhaps we should just pull d3-color in as a dependency?

License is a bit weird though...

cc: @vjeux

The way string interpolation is implemented right now is by looking for consecutive numbers and interpolating those. Super dumb but works okay. Would be nice to have a proper color parser :) Wanna send a pull request?

@vjeux - are you OK with depending on d3-color? Should be easy if so

i'd rather not. We already have color extraction in obj-c, java and this would add another way to interpret colors in js.
What would be nice is to move color normalization in js this way we can share the logic.
In the meantime, can you just add special support for #xxx and #xxxxxx?

Maybe we could add a Color proptype instead of using strings for colors in js? then we could move all string->color conversion to the front-end, and send colors over the bridge as an array of numbers.

To be clear, I'm not suggesting we'd stop using hex strings in the JS apps - just pre-convert them to an array before sending over bridge.

:+1: How important is this to you guys?

Support will be added probably when someone contributes a PR.

Do you guys not use React Native for animations? Or just using RGBA values?

I think all the Facebook examples have used RGBA values.

Color processing is now in JS so this should be easier to add (or maybe just works? haven't checked).

This one is fixed now? ^^ #3177


Investigate the frontend debuggers

The story is to investigate the frontend debuggers. The goal is to find the nice frontend debugger to use instead of writing a custom one.  Checkout Debug Adapter Protocol (GitHub - microsoft/debug-adapter-protocol: Defines a common protocol for debug adapters. )

@bezirg can we consider this done?

@bezirg can we consider this done?

Yes


Add code of conduct

We need something before we start having events or even online interactions

Resolved in #44


chore: remove unused SKU selection labels

Description
Remove SKU selection labels that are unused
How was this change tested?

make presubmit

Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[ ] No

Release Note

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.716%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
35591

Relevant Lines:
36423

💛  - Coveralls


swift-tools-version behavior differs from SE-0209

Is it reproducible with SwiftPM command-line tools: swift build, swift test, swift package etc?

[X] Confirmed reproduction steps with SwiftPM CLI. The description text must include reproduction steps with either of command-line SwiftPM commands, swift build, swift test, swift package etc.

Description
When building the release/6.0 branch of swift-syntax using Xcode 16 beta 5, the build process includes the -swift-version 6 flag. However, according to SE-0209, this should not be the case.
Referring to Example 4 in SE-0209:

Example 4:
// swift-tools-version:4.2

import PackageDescription

let package = Package(
    name: "HTTPClient",
    ...
    swiftLanguageVersions: [.v4, .version("5")]
)

The sources will be compiled with -swift-version 4.

In alignment with this example, the release/6.0 branch of swift-syntax, which has // swift-tools-version:5.7 in its Package.swift, should be built with the -swift-version 5 flag. However, this is not the case, and the build process uses -swift-version 6 instead.
While I personally believe the current behavior might be more correct, it still represents a deviation from the behavior specified in SE-0209, which could be problematic.
Expected behavior
No response
Actual behavior
swift-build --verbose outputs logs using "-swift-version 6"
Steps to reproduce

git clone https://github.com/swiftlang/swift-syntax.git -b release/6.0
cd swift-syntax
swift build --verbose | grep -e "-swift-version 6"

Swift Package Manager version/commit hash
Swift Package Manager - Swift 6.0.0-dev
Swift & OS version (output of swift --version ; uname -a)
swift-driver version: 1.113 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.6 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Darwin norio-nomura-MacBook-Pro.local 24.0.0 Darwin Kernel Version 24.0.0: Wed Jul 31 21:50:55 PDT 2024; root:xnu-11<IP_ADDRESS>1.2~1/RELEASE_ARM64_T6020 arm64

There's three concepts here:

Toolchain (or compiler) version
Tools version specified by the manifest
Supported language modes specified by swiftLanguageModes (which was swiftLanguageVersions)

The language mode used is the one closest to the current compiler version that's in the list of supported language modes. Note that the tools version specified by the manifest is mostly orthogonal in this case, other than being used to decide on a default if no language modes are specified.
In the given example, swift-syntax specifies both 5 and 6. Xcode 16 beta 5 contains a 6.0 compiler, thus language mode 6 is used. If instead a pre 6.0 compiler was used for the compilation, language mode 5 would be selected instead.
The final example in the SE is a little confusing, as the compiler and tools version isn't split and instead assumed to be the same. The actual design states:

The package manager will use standard version numbering rules to determine precedence of language versions. For e.g. 5 > 4.2.1 > 4.2 > 4.
...
When building a package, we will always select the Swift language version that is most close to (but not exceeding) a valid language version of the Swift compiler in use.
If a package does not specify a Swift language version, the tools version of the manifest will be used to derive the value.

Thank you for the clarification. 🙏🏻


Added ability to use av-dropdown without ng-option, using inline option tags instead

nice, clean :shower: and simple :cyclone:


GDP Prediction Model

Dataset:

Dataset

Hello, I would like to work on this issue!

can I work on this issue?

Hello, I would like to work on this issue!

@Ad-hue any updates regarding your model. Do you need more time?

Hello @Rutikab12 , I am currently working on this issue. I am an intermediate at this so I want to make sure everything in my project is correct and for that I do need more time since I am making it from scratch. I however would like to know your deadlines for this project.

Hello @Rutikab12 , I am currently working on this issue. I am an intermediate at this so I want to make sure everything in my project is correct and for that I do need more time since I am making it from scratch. I however would like to know your deadlines for this project.

okay. How much more time do you need?.

@Ad-hue The deadline for every issue is 6 days. If you are facing any issues and can't submit on time, you should come forward to let us know about that yourself instead of us asking specifically.
Also, if only you comment on an issue then unless someone else comments, the issue is yours for some time even after the deadline. but when someone else comments too, they too have an interest and we can't just prioritize you for that long.
So, please let us know the exact situation!

I understand. Since it would take me around 2 weeks to complete this, kindly reassign the issue. Thanks!

Hello, I am a GSSoC22 participant. Please asssign me this

Hello ! I am a GSSOC'24 participant. I am well versed with the ML algorithms from scratch. Please assign me this issue.

Hello! I'm a machine learning and data science enthusiast with hands-on experience in predictive modeling. I'm also a contributor for GSSOC'24. After reviewing the issue, I believe it aligns well with my skills and interests. I kindly request to be assigned to this task.