Use first-party Hypothesis strategies from the st namespace

As discussed in #18, this PR simply removes all instances of from hypothesis.strategies import ... in favour of from hypothesis import strategies as st, so that first-party strategies are used like st.<strategy>.
If you like, I could go over the suite to aias _array_module as xp and only call array module objects/methods with xp.<attribute>. Even if _array_module is really just a wrapper, it may add more clarity overall. Likewise I can try namespacing hypothesis_helpers and array_helpers if you'd like.

Sorry I didn't notice this PR for some reason. It has a few merge conflicts.
Is the idea with this to make it easier to distinguish between built-in hypothesis strategies and custom ones from hypothesis_helpers?

Is the idea with this to make it easier to distinguish between built-in hypothesis strategies and custom ones from hypothesis_helpers?

Yep. Meant it as a proof-of-concept to see how you feel. It's not a biggie!

I'm really ambivalent either way. If this is something you feel would have helped you coming into the codebase then I am OK with it.


Release 4.0.0

First 4.0.0 release

@ashie Could you check centos-7-aarch64 build works or not?  centos-8-aarch64 is succeeded but 7 is not.

In addition, rdkafka build is broken on CentOS 8. CentOS 7 and other deb packages has no rdkafka build problem.

Working on deb package release...

Finally some CI used ;D

Ubuntu focal / bionic and amazon linux 2 are published.
https://toolbelt.treasuredata.com/sh/install-ubuntu-bionic-td-agent4.sh
https://toolbelt.treasuredata.com/sh/install-ubuntu-focal-td-agent4.sh
https://toolbelt.treasuredata.com/sh/install-amazon2-td-agent4.sh
Ubuntu xenial and Debian buster will be published soon.

In addition, rdkafka build is broken on CentOS 8. CentOS 7 and other deb packages has no rdkafka build problem.

It's reproduced on my env, td-agent-4.0.0-1.el8.x86_64.rpm contains opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext/librdkafka.so but the file size is 0.

It's reproduced on my env, td-agent-4.0.0-1.el8.x86_64.rpm contains opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext/librdkafka.so but the file size is 0.

4.0.0rc1 uses rdkafka-0.7.0, it has valid ELF binary:
$ file opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.7.0/ext/librdkafka.so
opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.7.0/ext/librdkafka.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=487fdfa7f54efb5e87c060b36a17d6ba234e478e, stripped

@ashie Could you check centos-7-aarch64 build works or not? centos-8-aarch64 is succeeded but 7 is not.

I've got the following error on building Docker container.
 CentOS 7 and other deb packages has no rdkafka build problem.

It's reproduced on my env, td-agent-4.0.0-1.el8.x86_64.rpm contains opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext/librdkafka.so but the file size is 0.

td-agent-gem in td-agent-4.0.0-1.el8 can build valid ELF binary for rdkafka-0.8.0.

It's reproduced on my env, td-agent-4.0.0-1.el8.x86_64.rpm contains opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext/librdkafka.so but the file size is 0.

Hmm, it's weird.
It's already 0 bytes just after succeeded to install:
/opt/td-agent/bin/gem install --no-document --bindir /root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/bin /root/rpmbuild/BUILD/td-agent-4.0.0/td-agent/downloads/plugin_gems/16-rdkafka-0.8.0.gem
Fetching mini_portile2-2.5.0.gem
Fetching ffi-1.13.1.gem
Successfully installed mini_portile2-2.5.0
Building native extensions. This could take a while...
Successfully installed ffi-1.13.1
Building native extensions. This could take a while...
Successfully installed rdkafka-0.8.0
3 gems installed
ls -l /root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext/
total 8
-rw-r--r-- 1 root root  386 Jul  3 05:55 README.md
-rw-r--r-- 1 root root 2934 Jul  3 05:55 Rakefile
-rwxr-xr-x 1 root root    0 Jul  3 05:56 librdkafka.so
cat /root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/rdkafka-0.8.0/gem_make.out
current directory: /root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/lib/ruby/gems/2.7.0/gems/rdkafka-0.8.0/ext
/opt/td-agent/bin/ruby -I/opt/td-agent/lib/ruby/2.7.0/rubygems -rrubygems /opt/td-agent/lib/ruby/gems/2.7.0/gems/rake-13.0.1/exe/rake RUBYARCHDIR\=/root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/rdkafka-0.8.0 RUBYLIBDIR\=/root/rpmbuild/BUILDROOT/td-agent-4.0.0-1.el8.x86_64/opt/td-agent/lib/ruby/gems/2.7.0/extensions/x86_64-linux/2.7.0/rdkafka-0.8.0

Extracting v1.4.0 into tmp/x86_64-redhat-linux/ports/librdkafka/1.4.0... OK
Running 'configure' for librdkafka 1.4.0... OK
Running 'compile' for librdkafka 1.4.0... OK
Running 'install' for librdkafka 1.4.0... OK

Hmm, it's weird.
It's already 0 bytes just after succeeded to install:

It seems parallel build issue.
I can build a valid so file when I remove MAKEFLAGFS:
diff --git a/td-agent/Rakefile b/td-agent/Rakefile
index 0c98cbd..5dfb11b 100755
--- a/td-agent/Rakefile
+++ b/td-agent/Rakefile
@@ -651,7 +651,7 @@ class BuildTask

     makeflags = ENV["MAKEFLAGS"]
     gem_home  = ENV["GEM_HOME"]
-    ENV["MAKEFLAGS"] = "-j#{Etc.nprocessors}"
+    #ENV["MAKEFLAGS"] = "-j#{Etc.nprocessors}"
     ENV["GEM_HOME"]  = gem_staging_dir

     sh(gem_command, "install",
@@ -660,7 +660,7 @@ class BuildTask
        gem_path)

     ENV["GEM_HOME"]  = gem_home
-    ENV["MAKEFLAGS"] = makeflags
+    #ENV["MAKEFLAGS"] = makeflags
   end

   def install_gems(files)

Hmm... it's weird behaviour.
Can we disable parallel build on only rdkafka gem?

Hmm... it's weird behaviour.
Can we disable parallel build on only rdkafka gem?

I've committed it just now.

Thanks, I confirmed. Try to release centos 8 rpm.

@ashie Could you check centos-7-aarch64 build works or not? centos-8-aarch64 is succeeded but 7 is not.

I've got the following error on building Docker container.
Probably the yum repository seems broken temporarily.
--> Finished Dependency Resolution
Error: Package: rh-ruby24-rubygems-<IP_ADDRESS>-92.el7.noarch (centos-sclo-rh)
           Requires: /opt/rh/rh-ruby24/root/usr/bin/ruby
...

There is no reason to use older ruby for running the build system, it doesn't affect to the target Ruby.
I'm now confirming that we can use rh-ruby26 for it.

@ashie Could you check centos-7-aarch64 build works or not? centos-8-aarch64 is succeeded but 7 is not.

@repeatedly  I've fixed it. Please retry.


no border for imageview

I see no option to set the border width and color for image. Can you add the functions as well?

This only handles setting the initials avatar in the event that an image is not available. If you have an image, you can just manipulate UIImageView directly by setting properties like layer.borderColor.


Router Issues

[ ] Match header has grey background

[ ] Method dropdown is larger then all other fields

[ ] Exact drop-down for Header & Cookie rule is twice size it should be

[ ] Header & Cookie rule Remove has grey background and should be blue

[ ] Rewrite Request Headers section has gray background

Closing in favor of new QA testing pass.  Hopefully these are component issues that have already been resolved at a higher level.


Add an api to get all events

I already did this in a separate issue, but I'll do it again anyways in case that one doesn't pass code review.


Add support for column type 241 (XML)

fixes error when reading XML column type:
dbbind failed: no such column or no such conversion possible, or target buffer too small.

Fixes issue #39.
My quick test for this passed and I am now able to read XML columns with no problem. But I didn't have time to write tests for this, because I don't have SQL Server available on which I could run the tests.

Looks reasonable. All tests are passing. So I'm merging this.
Thanks, NoICE.


Unittest execution - call stack has incorrect additional entry with Python version

Stack trace of a failed test in Test Detail Summary window shows at 3.6 which is the Python version number. I tried setting active env to 3.7 and that changes it to at 3.7. That shouldn't be there.

I think that was added because PTVS needed the Python language version to use when parsing the code.

We'll reactivate if users notice.


Add Github Actions config

This is a basic config which currently runs the unit tests, rustfmt, and
clippy on both stable and beta rustc.

It may be nice to migrate the test scripts in the test folder to Rust too, or at least run those scripts on the Actions workflow. What do you think? I can try doing that when I have a bit of free time :smile:

I agree, I just didn't have time to get to it in this patch. Mostly because the test script requires the C zopfli binary for comparison. I'm sure installing it on Ubuntu isn't overly complicated, but I wanted to at least get something to start with.

./zopfli isn't the C binary, it's the rust one. Only sample outputs generated with the C zopfli for fixed inputs are used. The C zopfli executable isn't used at all in the test suite.


Filling and stroking empty paths in SVG backend

Fixes #8939
The PDF in the issue invokes the operator f even though no path has been created. Because there is no path, SVGGraphics.current.element remains undefined. Then f tries to access its functions.

/botio-linux preview

Thank you for fixing this!


Add Pointer Authentication module

I'm participating in a project called "Proof-of-concept integration of pointer authentication support in Ibex" in GSoC 2020.

Instantiate Pointer Authentication module
Add basic Pointer Authentication test

Hi @vogelpi,
Thank you for your polite review. I have fixed the location pointed out.
In addition, I added some modifications so that it works correctly when WritebackStage is enabled. Please check my code.
Regards,
Yuichi

Alright, I am merging this.


Stereoscope lit

These changes make it possible to run Stereoscope with the new API. It will require some improvements before merging. So far, Adam and I have flagged:

documentation (overall)
math in documentation can be formated
using register buffer instead of parameter with no grad
add reference in documentation
save / load in unit test?

Please let me know if you find some other things.

Ah! and we might want to look into this trainer behavior for no validation set and see if we can do something nicer. I don't like having to give the train_set twice to the pytorch lightning task

Alright! I think this is good to go, and should have the minimal functionalities we discussed! Let me know if you have any other comments, and generally, if you see some obvious doc changes you'd like to see implemented please go ahead!

checked pytest, flake8, black. not sure what codacy wants from me :)

added those!

Actually, one more thing is how we should incorportate the registration of the ind_x into the anndata at load time with mininal changes. Any suggestions?


Can upload by multi-thread

Please add this, it can make network speed more.Thx

I think it already uses multi-thread. If you open processes list while uploading you will see 5-6 instances of gdrive app.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 2012 ms

Resolved: Bofrost.at performance has improved in eb5cbe2 after 16 minutes.


TagHelpers authoring - SetContent() => SetHtmlContent()

to prevent unwanted encoding of HTML elements

Hi @hakenr, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, DNFBOT;

Thanks! 5a4e5e9bb9efd50cec5effb409bbf5cb8dba6486


Queued jobs failed with restarting elasticsearch service .

Package version
Im using v2.8.7 of the package
Describe the bug
Im using this package to insert the http request info of every request that hits the application to elasticsearch and for that im using packae in a queued job .
in normal situations everything is working fine . but when elasticsearch container goes down for a moment while users are using the application and again comes up to work we still has connection failed to elasticsearch from queued job .
for a temporary solution we have to run queue:restart to fix this .
I wonder if its a bug in this package or in my application code .
To Reproduce
1- create a queued job and within that job try to insert some data to elasticsearch .
2- stop the elasticsearch container .
3- try dispathing the job and you will get error in queue , inserting to elasticsearch .
4- start the container again .
5- you are still getting failed despite that the elasticsearch container works fine .
Expected behavior
We expect that application continue to inserting request logs to elasticsearch after elasticsearch container continue to work correctly .

This smells like a queue config issue. If ES is down all that will happen is that it will throw an exception (No alive nodes) & queues should catch these.
Are you using Horizon and Redis? Do you have supervisor in place to start up again if it goes down?
If you can point to a specific touch point that is causing this as a side effect because of the package then happy to continue here, else will close this in a few days time under the assumption that it falls out of the scope of this package.
I suggest asking the StackOverflow community for a hand using the queue issue as a starting point.
Also, consider upgrading to the 3.8.x version of the package - probably won't help you with this issue, but it's now the maintained version and far more advanced. Good luck!

Yes we are using horizon and redis . and we have a supervisor to bring back the ES service to work .
When ES is down we are getting (No alive nodes) exception and this the expected behavior . but when we bring back up the ES service we are still getting (No alive nodes) exception .
I was searching about this issue and i facet a topic about guzzlehttp and CURLOPT_FORBID_REUSE  and I think its probably responsible for this issue that elasticsearch package is reusing the connection that we have using when ES service is down .
Also Im trying to examine this issue on 3.8.x ....

I have tested v3.8.x and get same result and the issue is still valid .
example-laravel-elasticsearch(laravel 11.x and laravel-elasticsearch 3.11.x)
I have been create an example to show the problem .
please run this project using docker compose file . (elasticsearch and kibana services included in docker-compose)
After running migrations of the app you can hit the / route to test inserting to elasticsearch .
We have simple job that takes a name and insert it to and index in the elasticsearch .
Then try to stop the elasticsearch service , hit the / route to create the job in the queue (that the job will fail ), and then start the elasticsearch again and you still getting (no alive node available) exception .

Can you try simulate this by using the ES PHP client directly?
https://github.com/elastic/elasticsearch-php
Just make job that runs a connection and query manually, then fail the container etc.
Let me know what you find

I have been tested elasticsearch-php package and it was working fine after ES service goes up again .
sample

Last thing I'd like you to try before I commit time to this. Please try simulating the same as native MySQL. And if possible using mongoDB and https://github.com/mongodb/laravel-mongodb
Horizon caches most laravel settings and doesn't clear it until you restart Horizon. Could that point to something?

Also i have tried laravel-mongodb package and its working perfectly in queued job .

I have updated sample-project
implemented these three samples in InsertToElastic job :

laravel-elasticsearch
elasticsearch-php
laravel-mongodb

Hey @alirezaImani-f4L3e - tried and cannot recreate the issue you're facing. Retrying failed jobs works for me:

Different to your sample I used predis though:
composer require predis/predis
and
REDIS_CLIENT=predis

CACHE_DRIVER=redis
QUEUE_CONNECTION=redis
SESSION_DRIVER=redis

Try that, maybe it's something but either way since we're both getting different results with the same code then this must be an environment issue. Can't be sure until I can see it. Sorry man

Just a side note, if you're deferring these to a job queue because these writes are slow, keep in mind that you can save/create without refreshing if you will not be working with that record immediately after. Speed is near instant.
See: https://elasticsearch.pdphilip.com/saving-models#fast-saves
But seeing your ES containers are going down perhaps queuing is safer

Its not working even with predis .
Which command have you used ? (queue:listen or queue:work)
queue:listen is working fine because its not caching the job code . we have problem with queue:work .

php artisan horizon in local and prod
In prod I keep it running via supervisor settings

If you don't mind , try starting workers with queue:work .

So that seems to cache the connection and lock that in when it fails. I have no idea why it would do that.
If I rebuild the connection on every request then that solves this [very] specific issue. However, in doing so it slowed down my tests run time by between 5-15%, which is significant. Given that, it's not viable to incur the performance cost to cover this edge case.
I'll leave this open anyway and look at building in a circuit breaker for failed calls. That should fix this issue without compromising performance, but will need a significant upgrade with how the bridge handles errors.
In the meantime, I suggest running Horizon directly and config a supervisor: https://laravel.com/docs/11.x/horizon#supervisor-configuration - assuming it's in scope of your project of course

@alirezaImani-f4L3e - Am bundling this in with the next release. Can you update dev branch and try again?
It should work now. Let me know so that I know to close this on release notes. Thanks.

Will you fix this issue in 3.8.x in next release ?

Indeed 👍

Hi @alirezaImani-f4L3e - 3.8.1 has been released with a fix for this


Select All feature doesn't work for R-group attachment points

Environment details  (please complete the following information):

Ketcher Version 2.18.0-rc.4 Build at 2024-02-06; 13:45:28
Indigo Toolkit Version 1.18.0-rc.6.0-g98bf384e0-x86_64-linux-gnu-11.2.1
Chrome Version 121.0.6167.140 (Official Build) (64-bit)
Win10
Issue found while testing https://github.com/epam/ketcher/issues/3934

Steps to Reproduce

Open from file: AttachmentPoints.zip
Press Ctrl+A (Select All)

Actual behavior
Attachment points are not selected

Expected behavior
Attachment points are selected

Test automated.

Moved to Refined Backlog since no fix over 3 versions


Group Education - Health Education Topics

Issue
As for Health education, we have a list of health education topics that will be given.
The list of all the Education topics:

Tuberculosis
STDs & Prevention of HIV
Mental Health Diseases & Epilepsy
Malarial diseases and the use of mosquito nets
Childhood illnesses( Prevention, danger signs & emergency case management)
Malnutrition (The prevention and fight against diseases caused by malnutrition)
Antenatal Care, Postnatal Care & Danger Signs in Pregnancy
Family Planning & Sexual and reproductive health
Gender equality, Gender-Based Violence (GBV) & Behavior change
Non-Communicable Diseases(Diabetes , Hypertension & Asthma)

Task

Create the screen as per design
Create the logic for the selection of the topics

@adamhstewart Deployed to Nutrition env

@anvmn

https://nutrition-ihangane.pantheonsite.io/
Android tablet/Chrome

Question:
I think this space should be removed:

Checked and Approved:

The list has been created:

Education topics are selected in Education Session CT node


allow any 6.x.x version

Raven 6.x.x was released in February, allow it to be used.

@alexmuller @erikh360 @KaitCrawford ready for review


Add (unofficial) Go bindings to README

Hello,
Impressed by lol_html months ago, I wrote a Go binding for it here: https://github.com/coolspring8/go-lolhtml.
The Go binding now has a documentation, several ported examples and is 80~% covered with tests. On the other hand, however, the binding has not been tested in the wild, and is a personal "unofficial" work.
Would you like to add it to the "Bindings for other programming languages" part in README?

@CoolSpring8 hi, this is awesome! PR for adding this to the README is welcome


Update go.mod and go.sum manually

Issue #, if available:
Description of changes:
The nightly periodic to pull in the updated go.mod and go.sum did not update to the correctly file versions for the current version (0.6.3). This PR updates them manually until we get that fixed.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Add rate to order ticket

https://www.figma.com/file/6y4nvjfeVZwzwKcoXB0neq/Simplified-UI?node-id=319%3A4398

@bconfortin   rate should always be present. It's only showing up after I start typing

@bconfortin   rate should always be present. It's only showing up after I start typing


Force reversal issue with touch_grid plugin during collision between capsule-geom and plane-geom

Hi MuJoCo team,
I'm working on a project and currently trying to use MuJoCo for simulation. I'm looking for some help with the touch_grid plug-in.
Here is the core-part of my xml model:
<mujoco model="hopper">

  <extension>
    <plugin plugin="mujoco.sensor.touch_grid"/>
  </extension>

  <asset>
    <texture name="skybox" type="skybox" builtin="gradient" rgb1=".2 .3 .4" rgb2="0 0 0" width="800" height="800" mark="random" markrgb="1 1 1"/>
    <texture name="grid" type="2d" builtin="checker" rgb1=".1 .2 .3" rgb2=".2 .3 .4" width="300" height="300" mark="edge" markrgb=".2 .3 .4"/>
    <material name="grid" texture="grid" texrepeat="1 1" texuniform="true" reflectance=".2"/>
    <material name="self" rgba=".7 .5 .3 1"/>
  </asset>
  <visual>
    <headlight ambient=".4 .4 .4" diffuse=".8 .8 .8" specular="0.1 0.1 0.1"/>
    <map znear=".001"/>
    <quality shadowsize="16384"/>
  </visual>
  <compiler angle="degree" coordinate="local" inertiafromgeom="true"/>
  <default>
    <joint armature="1" damping="1" limited="true"/>
    <geom conaffinity="0" condim="1" margin="0.001" solimp=".8 .8 .01" solref=".02 1" rgba=".7 .5 .3 0.1"/>
    <motor ctrllimited="true" ctrlrange="-.4 .4"/>
  </default>
  <option integrator="RK4" timestep="0.002"/>
  <worldbody>
    <light cutoff="100" diffuse="1 1 1" dir="0 -0.7 -1.3" directional="true" exponent="1" pos="0 70 130" specular=".1 .1 .1"/>
    <geom conaffinity="1" condim="3" name="floor" pos="0 0 0" rgba="1 1 1 1" size="200 200 .125" type="plane" material="grid"/>
    <body name="0" pos="0 0 1.25">
      <camera name="track" mode="trackcom" pos="0 -3 1" xyaxes="1 0 0 0 0 1"/>
      <joint armature="0" axis="1 0 0" damping="0" limited="false" name="rootx" pos="0 0 -1.25" stiffness="0" type="slide"/>
      <joint armature="0" axis="0 0 1" damping="0" limited="false" name="rootz" pos="0 0 -1.25" ref="1.25" stiffness="0" type="slide"/>
      <joint armature="0" axis="0 1 0" damping="0" limited="false" name="0_joint" pos="0 0 0" stiffness="0" type="hinge"/>
      <geom friction="0.9" fromto="-0 0 0.2 0 0 -0.2" size="0.05" type="capsule"/>
      <body name="1" pos="0 0 -0.2">
        <joint axis="0 -1 0" name="1_joint" pos="0 0 0" range="-360 360" type="hinge"/>
        <geom friction="2.0" fromto="0 0 0 0 0 -0.45" size="0.05" type="capsule"/>
        <site name="1_touchgrid" pos="0 0 -0.45" zaxis="0 0 0.45" />
      </body>
    </body>
  </worldbody>
  <actuator>
    <motor ctrllimited="true" ctrlrange="-1.0 1.0" gear="200" joint="1_joint" name="1_joint"/>
  </actuator>
  <sensor>
    <plugin name="1_touchgrid" plugin="mujoco.sensor.touch_grid" objtype="site" objname="1_touchgrid">
      <config key="size" value="5 5"/>
      <config key="fov" value="180 90"/>
      <config key="gamma" value="0"/>
      <config key="nchannel" value="1"/>
    </plugin>
  </sensor>
</mujoco>

As shown in the picture below, I am running a rigid-robot for reinforcement learning in MuJoCo. I found that when a high-speed capsule-geom moving towards the plane-geom (e.g. a dog's leg pushing against the ground), the penetration issue is heavy.  Previously, this wasn’t a significant concern, but now I wish to equip the end of the capsule with a touch_grid sensor to simulate tactile feedback.

However, as the image illustrates, the overlap causes incorrect force direction perception (the force direction is reversed, the small white block).

While using contact-force visualization, I get accurate and wanted results!

I’m curious about how to achieve these results with the touch_grid plug-in. Alternatively, if not using touch_grid, what other viable solutions exist? I look forward to your suggestions.
It’s worth noting that I don’t think placing the site at the center or starting point of the geom (in order to make it "high enough") is a good idea, as this would result in an abnormal touch grid distribution.

The direction of the touch grid visualization is not related to the direction of the force, only to the orientation of the touch-grid viewport.
I think this is pretty clear if you look at the associated video: https://www.youtube.com/watch?v=0LOJ3WMnqeA

The direction of the touch grid visualization is not related to the direction of the force, only to the orientation of the touch-grid viewport.
I think this is pretty clear if you look at the associated video: https://www.youtube.com/watch?v=0LOJ3WMnqeA

Thank you very much for your prompt answer. However, the current activated grid unit the upper one. I want to leverage the position of the activate grid unit to simulate the touch point, are there any methods?


Bug fix for duplicate logs with docker

What does this PR do?
Fix a bug where the docker tailer would send the last line of log several time when a container wasn't writing much logs (less than 1 log / 30 sec)
Motivation
What inspired you to submit this pull request?

Codecov Report

Merging #2811 into master will increase coverage by 0.68%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #2811      +/-   ##
==========================================
+ Coverage   57.15%   57.83%   +0.68%
==========================================
  Files         385      356      -29
  Lines       24766    20048    -4718
==========================================
- Hits        14154    11594    -2560
+ Misses       9674     7615    -2059
+ Partials      938      839      -99

Impacted Files
Coverage Δ

pkg/logs/input/docker/since.go
100% <ø> (ø)
:arrow_up:

pkg/logs/input/docker/tailer.go
15.38% <50%> (+3.79%)
:arrow_up:

pkg/collector/runner/runner.go
53.15% <0%> (-15.27%)
:arrow_down:

pkg/metadata/resources/resources.go
75% <0%> (-8.34%)
:arrow_down:

pkg/quantile/key.go
46.15% <0%> (-7.18%)
:arrow_down:

pkg/metadata/host/host_tags.go
74% <0%> (-6%)
:arrow_down:

pkg/util/kubernetes/clustername/clustername.go
57.89% <0%> (-5.75%)
:arrow_down:

pkg/procmatch/signature.go
66.66% <0%> (-4.77%)
:arrow_down:

pkg/metrics/event.go
67.1% <0%> (-4.64%)
:arrow_down:

pkg/metrics/service_check.go
56.71% <0%> (-4.33%)
:arrow_down:

... and 239 more

Hi I am sorry to report this, but I have come across this exact issues after migrating our infrastructure to Fedora Core OS.
The screenshot below shows this exact behaviour.

If I can help with more information or assist in any way, please let me know.

@redRolf this issue shouldn't occur anymore with recent versions of the Agent.
Could you open a support case with our support team, send them a flare, and include the logs from the container where you're seeing this? (please make sure the logs don't contain any sensitive information)


Get nodes that match patterns

The onnx rewriter matches node patterns and replaces them. It would be a useful functionality if the node pattern matcher could be used to get the list of node groups that match patterns.
This could be used to check for existence of patterns, or the user can do things outside of the rewrite rules on the matched nodes.

So instead of doing the full replacement, an api to just find matches may be helpful. I was hoping to have something like that the other day too. @gramalingam

This is optional, but if having a generator as output might be nice too so we can do a fast check for existence of a pattern (return True if pattern exists at least once) without having to go iterator without having to go through the whole model.


Rework ReceiveAndPlot

Improve ReceiveAndPlot somewhat:

use a preallocated buffer for pull_chunk (so even an ancient laptop can show 2 channels @100KHz)
decouple scrolling and pulling for a smoother experience
allow multiple data and marker streams
display all suitable (i.e. data or marker streams) streams found at start time instead of one data and one marker stream

This is just an example of how to use pylsl. Defining a new class called Inlet is confusing. In general, I think we should keep OOP out of these examples because it'll scare away beginners.
If you want a good tool for pulling and plotting data then that's great, I think it's sorely lacking. I'd love to get rid of the Matlab visualizer as the default demo app. App-SigVisualizer is a good start but it needs some work. I think Clemens has a different solution we should also look at.

This is just an example of how to use pylsl.

And the extended version is below 100 LOC.

Defining a new class called Inlet is confusing.

Regarding the name I agree, so I renamed it.
Handling different inlet types differently with inheritance isn't that complicated, especially when compared to several for-loops.

In general, I think we should keep OOP out of these examples because it'll scare away beginners.

For the basic examples I agree, but plotting signals in realtime is something for advanced users.
I added some more comments and docstrings so it's easier to understand.

If you want a good tool for pulling and plotting data then that's great, I think it's sorely lacking.

I want that, but in a pinch I'd also take a quick and dirty python -m pylsl.examples.ReceiveAndPlot that

I'd love to get rid of the Matlab visualizer as the default demo app. App-SigVisualizer is a good start but it needs some work. I think Clemens has a different solution we should also look at.

We're using lsl in the clinic, so we can neither justify buying academic licenses for Matlab nor spending $3000+ for a regular license. For a fully featured visualization tool the SigVisualizer would be my first chioce, but right now it's too complicated to use.
This example shouldn't be the de facto visualizer, but I think it hits a sweet spot between a usable visualizer and API example.


[RedditPost] Handle errors in [p]redditpost add

is core included or does it need to be added to reqs in json?


fix(component): Fix undefined theme issue

:tada: This PR is included in version 0.13.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


MNT: Re-rendered with conda-smithy 1.5.1 [ci skip]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Remove deprecated .where in math_grad.py

This PR substitutes array_ops.where with array_ops.whare_v2 in math_grad.py, removing the deprecated message.

@vcarpani Could you please address the build failures? Thanks!

@vcarpani Could you please resolve the conflicts? Thanks!

@vcarpani Could you please resolve the conflicts? Thanks!

Yes, I will, had no spare time in the last weeks, as soon as i can I will get back on this ;)

bazel test //tensorflow/python(which was failing before) is now passing

@vcarpani can you please check build failures ?

Can one of the admins verify this patch?


[Query] Public Key of Curve25519 is compatible with Ed25519

Hi,
I'm wondering if Curve25519 keys are compatible with Ed25519(Signing & Authenticating)?
Thanks

Not without conversion.
Curve25519 public keys are 255-bit values on the x axis while Ed25519 public keys are 255-bit values on the y axis with an additional sign bit.
You can convert by performing y = ((x - 1) / ( x + 1)) % (2 ** 255) - 19

Aha, nice ...
So, the complete solution for that is like this:
y[0 .. 255] = ((x[0 .. 255] - 1) / (x[0 .. 255] + 1)) % ((2 ** 255) - 19)
Right?


Init part of LoopControlExpression should not be a statement

currently #init of a LoopControlExpression is an AssignmentStatement
It should be an AssignementExpression
Tjis implies:

creating FASTFortranAssignementExpression class as a copy of AssignementStatement
changing AssignementStatement to contain an AssignementExpression ?

merged pull#59

Created an entity FastFortranAssignmentExpression that has leftPart and rightPart of FastFortranVariable.
Change type of init in loopControlExpression to FastFortranAssignmentExpression


label_keep seems to be victoriametrics specifically

https://docs.victoriametrics.com/metricsql/#label_keep
https://github.com/blesswinsamuel/grafana-dashboards/blob/f72e55aa53242d4470ac65777dbfed318dd3188e/dashboards/smartctl.ts#L61-L71
I'm not sure if you want to make it more portable with something else
I removed them from my queries with no ill effect, so not sure if its something about Victoria

Hi @halkeye, thanks for opening this issue :). The reason for using label_keep was to see less noise in the transform tab of this panel in the grafana dashboard. Without label_keep, it looks like this:

And with label_keep:

So I changed it to sum aggregation, which should work with prometheus as well.

Awesome. I kinda figured you'd say no because you wanted it for your own stuff, so i'm happy you are fixing it!


galaxy-rnacommender container not downloading

Expected behavior
Download galaxy-rnacommender container.
Actual behavior
When trying to download this container, it shows: HTTP code is 500 which indicates error: server error - {"message":"Get https://registry-1.docker.io/v2/gianlucacorrado/galaxy-rnacommender/manifests/latest: read tcp <IP_ADDRESS>:56990-\u003e<IP_ADDRESS>:443: read: connection reset by peer"}
Steps to reproduce the behavior

Open Kinematic
Search for galaxy-rnacommender
Click Create and this error will appear

Make sure that you're on a solid connection with a good DNS (something like google's DNS works well)


The v4 releases source commit is not on any branch in the repository

It looks like the commit v4 is based on, fd37e265ec6a48981d62fa415f1fafd03bfd261c isn't pushed to master. This is triggering a warning in the GH UI when looking at the release's commit.
The parent commit f19cd589bfe54c9886202b25321dc302bbbb8e18 is on master. I'm guessing this is just a minor error where the default branch didn't get updated on release.

Thank you

Ha, indeed. I wonder how it happened. The git diff shows no difference between fd37e265ec6a48981d62fa415f1fafd03bfd261c and f19cd589bfe54c9886202b25321dc302bbbb8e18. :thinking: It looks like the only difference is that the commit behind v4 tag (fd37e265ec6a48981d62fa415f1fafd03bfd261c) is actually signed with my SSH key, while the commit in master is not.
Thanks for the reporting this, @dekimsey. I can either force push v4 tag that points to the commit in master, or make some v5 tag that is from master. What option do you think is preferable in your opinion?

I'd recommend simply publishing a new tag/release from master. v4 has been out since Jan 3rd of 2022, so I wouldn't recommend overwriting it. Packaging mistakes happen, I wouldn't worry about it. Just emit a new version with no other changes, after all numbers are free right? 😀

That is very true! However many such projects maintain a major version tag that is rewritten in addition to vX.Y.Z tags that do not.
If you want to rewrite tags, go for it. But I'd ask that you consider making permanent tags too so users may pin to a version they  know works for them.

Hey @dekimsey,
I'm sorry for the delay. I just pushed the v5 version that is tagged from master.
https://github.com/ikalnytskyi/action-setup-postgres/releases/tag/v5


Investigate issue with kafka roundtrip pipeline

It looks like that we have a issue with the kafka roundtrip pipeline.
Example config file: https://github.com/trivago/gollum/blob/master/config/kafka_roundtrip.conf
For some reasons we get no data back from the kafka consumer. This can be an issue in the kafka producer or consumer.

The issue come from a misconfiguration in the used docker-compose file. gollum config and kafka producer/consumer work fine and have no known issues.


Release v3: fix workflow

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

Project coverage is 81.48%. Comparing base (05cf661) to head (fc1f257).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #125   +/-   ##
=======================================
  Coverage   81.48%   81.48%
=======================================
  Files          50       50
  Lines        1842     1842
  Branches      344      344
=======================================
  Hits         1501     1501
  Misses        341      341

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add submodule llava for android sample

[x] I have read the contributing guidelines
Self-reported review complexity:

[ ] Low
[ ] Medium
[ ] High

@zhiyuan8  please review this PR

@liute110 You might want to remove phi2 or other irrrelevant models and replace by phi3-3B / gemma2-2B / llama3-1B
feel free to submit in future PRs


🌱 don't ignore #nosec in golangci-lint config

I understood this config wrong way around. With the additional config it ignored the #nosec lines, which means it failed linting where they were ignored. Default is working well for us.

/test-centos-e2e-integration-main
/test-ubuntu-integration-main

I understood this config wrong way around. With the additional config it ignored the #nosec lines, which means it failed linting where they were ignored. Default is working well for us.

I understood the same as you
/approve

Oh :slightly_frowning_face:
could not start the process: exec: "make test": executable file not found in $PATH

Oh 🙁
could not start the process: exec: "make test": executable file not found in $PATH

Yeah OK, need to wrap it with sh probably.

/retest

/retest


fix: use unpack-stream replace tar-pack

closes issue #10958
Fix create-react-app fails on Node 14+ with local template file

@ianschmitz Hello, Please have a look at this pr.

I also have this problem

@facebook-github-bot Thanks for your work.


Feature/copyright text by country

address this story: https://www.pivotaltracker.com/story/show/145650705/comments/172754371

change copyright text in footer based on country of origin
detect the country of origin first by using user's locale_code (i.e. locale_code is a combination of language code and country/regional code, e.g. en_AU) first. If that is not available, then use the free service -https://freegeoip.net/
css fixes

Hello @achen2401! Thanks for submitting the PR.

In the file portal/views/patients.py, following are the PEP8 issues :

Line 174:27: W291 trailing whitespace


fix: character type

What type of PR is this?

What this PR does / why we need it:
Using  ASCII character.
Which issue(s) this PR fixes:
Special notes for your reviewer:

@caohe PTAL.


Removing unnecessary circular dependencies

References

Fixes #1560

Description
This PR removes as many circular dependencies as possible. There are still some circular dependencies in model classes due to bidirectional relationships.
These circular dependencies in model classes are difficult to remove without seriously complicating the current code base. We suggest to leave those unsolved until one proves to be an actual problem at which point we can come back and see what we can do about it.
This PR also adds an automated check for new circular dependencies to the Github checks. It filters out the problematic model classes.
Instructions for Reviewers
Run npx madge --circular --extensions ts ./ and make sure the only circular dependencies shown are the ones in model classes.
Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[x] My PR passes TSLint validation using yarn run lint
[x] My PR doesn't introduce circular dependencies
[x] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[x] My PR passes all specs/tests

@tdonohue I merged the latest main branch into this branch, merging this PR shouldn't cause any conflicts anymore!

@LotteHofstede : Thanks!  I'll give it one last test on my end to verify all looks good and then get this merged sometime today.

Argh, my apologies @LotteHofstede .  This has minor merge conflicts again after I hit the merge button on a tiny PR #1600   I didn't realize that small PR would again affect this one.   I'll hold off merging anything else at this point, as I want to get this PR merged.  Could you find time to do one last merge conflict resolution?


fbrp -> mrp

Description
FAIR is getting renamed to MetaAI. This PR changes fbrp to mrp.
Type of change
Please check the options that are relevant.

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[x] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[x] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[ ] I want a thorough review of the implementation.
[x] I want a high level review.
[ ] I want a deep design review.

Before and After
Testing
Ran the examples.
Checklist:

[x] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[x] New and existing unit tests pass locally with my changes.
[x] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

Codecov Report

Merging #1054 (f46ebdc) into main (10b05cf) will increase coverage by 0.08%.
The diff coverage is n/a.

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

@@            Coverage Diff             @@
##             main    #1054      +/-   ##
==========================================
+ Coverage   33.07%   33.15%   +0.08%
==========================================
  Files         346      347       +1
  Lines       34116    34361     +245
==========================================
+ Hits        11284    11393     +109
- Misses      22832    22968     +136

Impacted Files
Coverage Δ

agents/droidlet_agent.py
44.08% <0.00%> (-7.69%)
:arrow_down:

agents/_agent.py
51.76% <0.00%> (ø)

lowlevel/minecraft/pyworld/fake_mobs.py
88.98% <0.00%> (+0.84%)
:arrow_up:

grep -ril fbrp *
Shows remaining hits in README.md, mrp/Dockefile, and several examples_and_tutorials notebooks.  Did you want to update these as well?

grep -ril fbrp *
Shows remaining hits in README.md, mrp/Dockefile, and several examples_and_tutorials notebooks. Did you want to update these as well?

Thanks for catching those! I'm surprised I missed mrp/Dockefile. Less surprised I missed README.md. Both updated.
The examples_and_tutorials aren't related. Grep finds part of a base64 encoded image.
$ grep -riEo '.{0,10}fbrp.{0,10}'
examples_and_tutorials/notebooks/active_vision/DataViewer.ipynb:ze2lTIj2rJFbrP/RkzfLMK4X
examples_and_tutorials/notebooks/active_vision/DataViewer.ipynb:YGvco7FyqqFbRPDSPesuI/cQ
examples_and_tutorials/notebooks/active_vision/DataViewer.ipynb:Kv4M2OSQT7FbrpIEaOeDB4gA
examples_and_tutorials/notebooks/detectron2_dataset.ipynb:xyJKqvp1//fbRPQ3AfwqgG8R
examples_and_tutorials/notebooks/detectron2_dataset.ipynb:GShBqng+1MfBRpC8sZs5racM
examples_and_tutorials/notebooks/detectron2_dataset.ipynb:PRP6k9PzAUfBrPnQ0dGngNkS
examples_and_tutorials/notebooks/detectron2_dataset.ipynb:taYwpkakgDFbrpJRRIXUCwuc
examples_and_tutorials/notebooks/pycoco_locobot.ipynb:XDuWalVjAVfbRpLyPrjMQsCJ
examples_and_tutorials/notebooks/train_detector.ipynb:SzzxMQmuAtFbrp8h9eFw63lC
examples_and_tutorials/notebooks/turk_annotations/1_visualize_masks.ipynb:j7I42cnMK1FBRPV8+391kIT7
examples_and_tutorials/notebooks/turk_annotations/1_visualize_masks.ipynb:xRvpar8+OwfBRpfCc9GHSH+n
examples_and_tutorials/notebooks/turk_annotations/1_visualize_masks.ipynb:qNIilmPZy4fBrP6F5Siwn6vc
examples_and_tutorials/notebooks/turk_annotations/1_visualize_masks.ipynb:H/Y4EbTmRIFBrpcm5y1dhp20
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:AKtNRlbojSFbRpigJwswStSV
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:LXj891LpxxFBrPQcMEIS3Ykj
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:ZQx7MJUXS2fBrPUIUl6aVsiu
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:ZQx7MJUXS2fBrPUIUl6aVsiu
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:i9lrZt+dRXfBrP3r7L//O2H+
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:DjP/1f8aWvfBrPHyc8//zzuH
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:x6/Hr8evx5fBrPELF7se8ySf
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:7PWNysAInPFBrPzNE2tDqI+X
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:ym7RZnu08+fbrpHvDFgquxCy
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:eS/O9YSCXDfbrpxLCJX99Skd
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:aJP5y/02j7FbRP2UfvnHQWWf
examples_and_tutorials/notebooks/turk_annotations/2_create_properties_turk_job.ipynb:ETJZpacdktfBrpOvUdjow1N8
examples_and_tutorials/notebooks/turk_annotations/experimental_visualize_tuck_tool.ipynb:otEVuhgBHjFbRpJS0TxnoNx3
examples_and_tutorials/notebooks/turk_annotations/experimental_visualize_tuck_tool.ipynb:myTEyq6heLFbrp86K5YEjCLN
examples_and_tutorials/tutorials/droidlet_for_physical_robots.ipynb:cOScbdSznxFbrp9RcOQd4fbH


Pre pr cleanup

Fixes no specific issues but improves types, fixes somes tests and upgrades packages

[x] npm run test succeeds.
[x] npm run lint succeeds.
[ ] Appropriate changes to README are included in PR.

@grant Here is a smaller PR with only the "small bits" not directly related with the config files. I will submit the proposed config files implementation in another PR (hoping I won't mess up)

@grant I'll let you set the resolved status if appropriate

@grant sorry that I introduced a circular dependency. Let me know how and when you want it to be fully addressed.

Thank you for the contribution.
Please have smaller PR in general.


Update op-erigon and superchain-registry

Update op-erigon to v1.1.2 https://github.com/bobanetwork/op-erigon/commit/bc416811c1de59b750d10cdbd0d1b926ad9eaea1
Update superchain-registry to https://github.com/bobanetwork/superchain-registry/commit/c3fc109db57cdd2029e815e47917c5c39e680521

I can't directly update superchain-registry to https://github.com/bobanetwork/superchain-registry/tree/0964797. It will break op-geth and op-program. The superchain-registry can update to the newer version after merging upstream to the develop branch.


Error management with monorepo and sveltekit 2

Describe the bug
I'm developing an application using sveltekit.
Up until now, I've been using version 1.30 and everything has worked without a hitch (except for the hiccups integrated by my own code ;) ).
Recently, I wanted to upgrade to version 2 of sveltekit, and then I noticed a problem with error handling (in +error.svelte, I didn't get the right status).
To try and give a framework, I've tried to reproduce my problem on this lab: https://www.sveltelab.dev/kvdbsalqt43c5v5
In this lab, I have a service (SlugService in $lib) that simulates a fetch and throws an error if it's not the right slug. Everything's fine here.
In my case, in my package.json, I use another repo from my monorepo a bit like this:
{
	"name": "front",
	"version": "0.0.1",
	"private": true,
	"scripts": {
		"dev": "vite dev --port 5178",
		"build": "vite build",
		"preview": "vite preview",
		"check": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json",
		"check:watch": "svelte-kit sync && svelte-check --tsconfig ./tsconfig.json --watch",
		"lint": "prettier --plugin-search-dir . --check . && eslint .",
		"format": "prettier --plugin-search-dir --write ./src '!**/*.{json,html}'"
	},
	"prettier": "tools/prettier.config.js",
	"devDependencies": {
		"@sveltejs/adapter-auto": "^3.1.1",
		"@sveltejs/adapter-vercel": "^4.0.5",
		"@sveltejs/kit": "^2.5.1",
		"@sveltejs/vite-plugin-svelte": "^3.0.2",
		"svelte": "^4.2.12",
		...
		"tools": "workspace:*",
		"tslib": "^2.6.2",
		"typescript": "^5.3.3",
		"vite": "^5.1.4",
		"vitest": "^1.3.1",
		"zod": "^3.22.4"
	},
	"dependencies": {
		...
		"services": "workspace:*",
		...
	},
	"type": "module"
}

And, of course, in my services repo, the svelte and sveltekit dependencies are with the same versions.
If I move my service to this monorepo (without any modification other than importing it into /[...slug]/+page.server.ts), I see an server-side log: apps/front dev HttpError { status: 404, body: { message: 'Place not found' } } and the error displayed in +error.svelte is 500.
And this same code works perfectly with version 1.30. Do you have any ideas on how to fix this problem?
Reproduction
Move my SlugService into a monorepo.
I created a repo : https://github.com/piolet/error-repo, everything is explained in the readme to reproduce
Expected behavior
catch a 404 error in +error.svelte in both cases
Logs
No response
System Info
System:
    OS: macOS 13.4.1
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
    Memory: 220.00 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.14.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.3.1 - /usr/local/bin/npm
    pnpm: 8.15.4 - /usr/local/bin/pnpm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 122.0.6261.69
    Edge: 122.0.2365.52
    Safari: 16.5.2

Severity
annoyance
Additional Information
No response

closed as in favour of https://github.com/sveltejs/kit/issues/11749


Fix bloom filter creation on BYTES

This is a quick fix for the BYTES support. There are other issues related to bloom filter, and I will create an issue around it and use a separate PR for more fixes and testing.

Codecov Report

Merging #9898 (b86a498) into master (716797f) will decrease coverage by 9.14%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master    #9898      +/-   ##
============================================
- Coverage     24.94%   15.80%   -9.15%
- Complexity       44      175     +131
============================================
  Files          1966     1925      -41
  Lines        105835   103768    -2067
  Branches      16056    15809     -247
============================================
- Hits          26404    16402   -10002
- Misses        76743    86164    +9421
+ Partials       2688     1202    -1486

Flag
Coverage Δ

integration1
?

unittests2
15.80% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

 Learn more


You were added to awesome-humane-tech

This is just a FYI issue to notify that you were added to the curated awesome-humane-tech in the 'Health' category, and - if you like that - are now entitled to wear our badge:

By adding this to the README:
[![Awesome Humane Tech](https://raw.githubusercontent.com/humanetech-community/awesome-humane-tech/main/humane-tech-badge.svg?sanitize=true)](https://github.com/humanetech-community/awesome-humane-tech)

https://github.com/humanetech-community/awesome-humane-tech

Thanks, I had that already :)

👍  Sorry, overlooked. I was processing projects where many entries were added before the badge program.


Signed integer overflow

I added undefined behavior sanitization to snore in a small patch: https://github.com/jpdoyle/snore/tree/ubsan-overflow
With that patch, I can trigger signed integer overflow by doing:
$ ./snore<PHONE_NUMBER>.5
snore.c:100:20: runtime error: signed integer overflow: 49710 * 86400 cannot be represented in type 'int'

Thanks for your feedback.
I would rather prevent the overflow by changing line 122 to INT_MAX. Do you agree? If so please send a PR so that I can merge your fix.

Would you prefer to not have ubsan enabled? It seems like a good thing to include, especially since print_time will have undefined behavior for large numbers on any platform where int is 64-bit.
I can make a PR with both ubsan and the UINT_MAX -> INT_MAX change

Checking against INT_MAX should prevent undefined behaviours but I will give a deeper look and make some test.
I will merge #18 for now.


Hidding resize button at right bottom

How can i hide the default grey resize button at the left bottom of my ImGui ?

I found out by reading

But if you also have trouble finding how to heres the solution:
ImGui::Begin("", NULL, ImGuiWindowFlags_NoResize); {     // Your code } ImGui::End();
You just have to add the flag ImGuiWindowFlags_NoResize in you Begin function call arguments


fix: change the term Docker to upper-case and adjust the term ddev to the DDEV word mark

The Issue
How This PR Solves The Issue
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

I will include the changes from this PR to one for all go files.


Refactor the MaxByte functions to accomodate the DataAvailabilityHeader

As an intermediate step to completing #184, the data availability header was added to the BlockID in #312. Introducing the data availability header dramatically changes the number of bytes in Commits, Votes, and the Block structs, and this fact effects the functions that count the max number of bytes, along with the tests for those functions. Most notably, three tests have been commented out until the BlockID is replaced with the header hash. These tests are TestMaxCommitBytes, TestBlockMaxDataBytes,  and TestBlockMaxDataBytesNoEvidence. Not only do these tests have to be uncommented, but the functions that they test need to refactored in order to accomodate for the data availability header when necessary. There should also be an equivalent max byte function/test for the DataAvailabilityHeader.

This DAH is no longer included in the blockID


Fixing vtgate python cursor to not pass 2 sets of args.

@erzel @dumbunny this was already approved internally.

LGTM


Sporadic GraphQL Error

I'd like to implement this plugin into my site, but most of the times when I run gatsby develop, I get a GraphQL Error.
success delete html files from previous builds — 0.006 s
success open and validate gatsby-config.js — 0.004 s
success copy gatsby files — 0.022 s
success onPreBootstrap — 0.007 s
success source and transform nodes — 0.044 s
success building schema — 0.144 s
success createLayouts — 0.007 s
success createPages — 0.005 s
success createPagesStatefully — 0.014 s
success onPreExtractQueries — 0.001 s
success update schema — 0.092 s
GraphQL Error There was an error while compiling your site's GraphQL queries.
  Invariant Violation: GraphQLParser: Unknown field `siteSearchIndex` on type `RootQueryType`. Source: document `SearchIndexExampleQuery` file: `GraphQL request`.

success extract queries from components — 0.118 s
success run graphql queries — 0.013 s
success write out page data — 0.003 s
success write out redirect data — 0.001 s
success onPostBootstrap — 0.001 s

info bootstrap finished - 1.908 s

Here is my gatsby configuration:
module.exports = {
  plugins: [
    `gatsby-plugin-react-helmet`,
    `gatsby-plugin-catch-links`,
    `gatsby-plugin-styled-components`,
    `gatsby-plugin-sass`,
    {
      resolve: `gatsby-plugin-typography`,
      options: {
        pathToConfigModule: `src/utils/typography.js`,
      },
    },
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        name: `posts`,
        path: `${__dirname}/src/pages/posts`,
      },
    },
    {
      resolve: `gatsby-transformer-remark`,
      options: {
        plugins: [
          {
            resolve: `gatsby-remark-prismjs`,
            options: {
              classPrefix: "language-",
            },
          },
        ],
      },
    },
    {
      resolve: `@andrew-codes/gatsby-plugin-elasticlunr-search`,
      options: {
        fields: [
          'title',
          'tags',
        ],
        resolvers: {
          MarkdownRemark: {
            title: node => node.frontmatter.title,
            tags: node => node.frontmatter.tags,
          },
        },
      },
    },
  ],
};

It seems it doesn't matter in which order the plugins are listed. 90% of the time, I get the error, sometimes it works.
Could this be a timing problem?
Thanks!

Is this related to https://github.com/gatsbyjs/gatsby/issues/3139 and subsequently fixed with https://github.com/gatsbyjs/gatsby/pull/3218 ?

Hmm, not sure, but I will try the latest gatsby, with the fix, and see if it resolves it. I'll do this later today.

Checking in to say I'm also getting this error

I've found out that the node get deleted in the gatsby staleNodes functions when rebuilded from cache. I still dont know why.
https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby/src/utils/source-nodes.js

Seeing this issue as well, on latest versions of everything.
I've added a cache clearing script that runs before develop for the time being.

@shwanton what is your data source?

hey Andrew, I have just faced into that problem.  I am using
"@gatsby-contrib/gatsby-plugin-elasticlunr-search": "^2.3.0",
 "gatsby": "^2.13.25",

My gatsby config:
...
{
      resolve: `@gatsby-contrib/gatsby-plugin-elasticlunr-search`,
      options: {
        // Fields to index
        fields: [`title`, `tags`],
        // How to resolve each field`s value for a supported node type
        resolvers: {
          // For any node of type MarkdownRemark, list how to resolve the fields` values
          MarkdownRemark: {
            title: node => node.frontmatter.title,
            tags: node => node.frontmatter.tags,
            path: node => node.frontmatter.path,
          },
        },
        // Optional filter to limit indexed nodes
        filter: (node, getNode) =>
          node.frontmatter.tags !== 'exempt',
      },
    }
...

The output message is:
success update schema - 0.077 s

 ERROR #85907  GRAPHQL

There was an error in your GraphQL query:

- Unknown field 'siteSearchIndex' on type 'Query'.

File: src/templates/blog-post/index.js

success extract queries from components - 0.372 s

I also cleared .cache, but it doesn't help!


python310Packages.chiavdf: 1.0.4 -> 1.0.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.chiavdf is: "Chia verifiable delay function utilities"
meta.homepage for python310Packages.chiavdf is: "https://www.chia.net/"
meta.changelog for python310Packages.chiavdf is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.0.5 with grep in /nix/store/8n5227hxci2xx9zbn5ar8pm6zgivf3n2-python3.10-chiavdf-1.0.5

found 1.0.5 in filename of file in /nix/store/8n5227hxci2xx9zbn5ar8pm6zgivf3n2-python3.10-chiavdf-1.0.5

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
chia
python310Packages.chiavdf
python39Packages.chiavdf

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/8n5227hxci2xx9zbn5ar8pm6zgivf3n2-python3.10-chiavdf-1.0.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.chiavdf https://github.com/r-ryantm/nixpkgs/archive/4ef067667e76c04f2b75f669edc6e7d1d6373764.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/8n5227hxci2xx9zbn5ar8pm6zgivf3n2-python3.10-chiavdf-1.0.5
ls -la /nix/store/8n5227hxci2xx9zbn5ar8pm6zgivf3n2-python3.10-chiavdf-1.0.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages built:

chia
python310Packages.chiavdf
python39Packages.chiavdf

Maintainer pings
cc @Atemu @lourkeur for testing.

@ofborg build chia

Result of nixpkgs-review pr 157123 run on x86_64-linux 1

3 packages built:

chia
python310Packages.chiavdf
python39Packages.chiavdf


[connectivity_plus_web] Disable network information api

Description
This PR disables the use of the NetworkInformationAPI implementation, as it is still experimental.
I don't see this change as a breaking change, as the extra information that is exposed by NetworkInformation from dart:html is not exposed to end users.
Context: https://github.com/fluttercommunity/plus_plugins/issues/639#issuecomment-1153099644
See also NetworkInformation API docs
Related Issues
https://github.com/fluttercommunity/plus_plugins/issues/639
https://github.com/fluttercommunity/plus_plugins/issues/856
https://github.com/fluttercommunity/plus_plugins/issues/641
https://github.com/fluttercommunity/plus_plugins/issues/436
Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
[x] All existing and new tests are passing.
[x] I updated the version in pubspec.yaml and CHANGELOG.md.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the [Flutter Style Guide].
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Sounds reasonable! Thanks for the contribution @navaronbracke !
Is there any issue that we should close once this is merged?


Fixing Execution Details page UX

Fixing colors, shadows and backgrounds.

Will raise a follow up PR for fixing review comments.


luci-app-squeezelite: add new luci-app-squeezelite package to applications/

LuCI application to configure squeezelite
Squeezelite (https://code.google.com/p/squeezelite/)
is a small headless squeezebox emulator for linux using alsa audio output.
It is aimed at supporting high quality audio including usb dac based output
at multiple sample rates including 44.1/48/88.2/96/176.4/192k/352.8/384kHz
Signed-off-by: Andrew Kazakov<EMAIL_ADDRESS>

I think you need to re-work this to fit into the LuCI build structure - see some other media UI examples like luci-app-minidlna or luci-app-mjpg-streamer.


fixed image name used in docker run

Hi @luisparravicini, thank you for the contribution

Hi @luisparravicini, thank you for the contribution


Domains to consider adding to blacklist

There are a few URL shortener and page builder services that seem to be the source (or a bounce point) for a fair amount of spam. I am keeping an eye on the following domains, considering whether to add them to the blacklist or not.
dinkypage.com
ddrss.at
Your suggestions are welcome.

Here are some additional sources of shorteners to review.
http://dig.do/about/url-shortener
http://bit.do/list-of-url-shorteners.php
https://archive.today/VCaCh
https://code.google.com/archive/p/shortenurl/wikis/URLShorteningServices.wiki

I’ve added the ddrss.* domain to the blacklist, since the service is no longer in operation as of early 2016. Again, this will catch residual links making the rounds from this service and its sister sites, which are either dead or serving up redirection spam.

Disposable Email Domains
https://github.com/ivolo/disposable-email-domains


npm having issues on powershell

Tried all the available tricks like updating npm/nodejs version & other patches suggested on stackoverflow
Steps to reproduce

On windows 10, install nodejs LTS version
Update ComSpec environment variable from "C:\Windows\System32\cmd.exe"  to "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" (I want make powershell as my default terminal )
In powershell try "npm-v" or any npm install

Expected behavior
Should allow to use npm
Actual behavior
Getting below error
**C:\Users\Ravishankar> npm -v
C:\Program : The term 'C:\Program' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

C:\Program Files\nodejs\npm.cmd -v

  + CategoryInfo          : ObjectNotFound: (C:\Program:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException**

Environment data

Operating system : Windows 10 Home
Nodejs version : 6.9.2 LTS as well tried with current version 7.2.1
C:\Users\Ravishankar> $PSVersionTable
**Name                           Value

PSVersion             :         5.1.14393.479
PSEdition              :        Desktop
PSCompatibleVersions  :          {1.0, 2.0, 3.0, 4.0...}
BuildVersion       :            10.0.14393.479
CLRVersion           :          4.0.30319.42000
WSManStackVersion  :            3.0
PSRemotingProtocolVersion  :    2.3
SerializationVersion     :      <IP_ADDRESS>**

Not repro'ing for me:
Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\slee> npm

Usage: npm <command>

where <command> is one of:
    access, adduser, bin, bugs, c, cache, completion, config,
    ddp, dedupe, deprecate, dist-tag, docs, edit, explore, get,
    help, help-search, i, init, install, install-test, it, link,
    list, ln, login, logout, ls, outdated, owner, pack, ping,
    prefix, prune, publish, rb, rebuild, repo, restart, root,
    run, run-script, s, se, search, set, shrinkwrap, star,
    stars, start, stop, t, tag, team, test, tst, un, uninstall,
    unpublish, unstar, up, update, v, version, view, whoami

npm <cmd> -h     quick help on <cmd>
npm -l           display full usage info
npm help <term>  search for help on <term>
npm help npm     involved overview

Specify configs in the ini-formatted file:
    C:\Users\slee\.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

<EMAIL_ADDRESS>C:\Program Files\nodejs\node_modules\npm
PS C:\Users\slee> npm -v
3.10.9

No repro for me either. I tried with Windows PowerShell and Alpha.13. Same result:
PS F:\Notes\> npm -v
3.10.8
PS F:\Notes\> where.exe npm
C:\Program Files\nodejs\npm
C:\Program Files\nodejs\npm.cmd

Need better repro steps to be able to investigate this

@SteveL-MSFT : apologize for  incomplete steps, Updated steps in original issue
I have updated my ComSpec environment variable from "C:\Windows\System32\cmd.exe"  to "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
however with "cmd" as a default terminal, It works without any issues.

I don't think it's recommended to change %comspec% to point to PowerShell.exe as existing apps will break if they use something like:
%comspec% /k foo.bat

From what I read, latest flight of Win10 has made powershell the default, but %comspec% still points to cmd.exe for compatibility reasons.

I am, too, expiriencing the problem.
WIN10, VS Code/ newest.
Can't install anything with NPM
`npm : The term 'npm' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was
included, verify that the path is correct and try again.
At line:1 char:1

npm install

  + CategoryInfo          : ObjectNotFound: (npm:String) [], CommandNotFoundException
  + FullyQualifiedErrorId : CommandNotFoundException`

First of all guys!!  Remember this is not a Window PowerShell forum section.  This is only for PowerShell Core issues.
If you got issues with NPM please go to their respective forums for support.
Thanks!


bug: list index out of range coming while hitting query

Describe the bug
Error coming from clickhouse connect while running the query :
select CAST(json_str AS JSON) AS json_obj from test.json_str_table1;

Steps to reproduce

Run the query in clickhouse

CREATE TABLE test.json_str_table1
(
    `json_str` String
)
ENGINE = MergeTree
ORDER BY tuple()
SETTINGS index_granularity = 8192;

Insert some data in same

insert into test.json_str_table1 (json_str) values ('{"a":"b"}');

Run the query below:

select CAST(json_str AS JSON) AS json_obj from test.json_str_table1;

Expected behaviour
As result is coming is clickhouse playground

Code example
import clickhouse_connect

clickhouse-connect and/or ClickHouse server logs
Stack trace:
-16 16:22:11,370:ERROR:root:on the exception : list index out of range
Traceback (most recent call last):
  File "/Users/apple/Desktop/Datazip/bi/superset/db_engine_specs/base.py", line 1562, in execute
    cursor.execute(query)
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/dbapi/cursor.py", line 51, in execute
    self.data = query_result.result_set
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/query.py", line 254, in result_set
    return self.result_rows
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/query.py", line 272, in result_rows
    for block in stream:
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/common.py", line 195, in __next__
    return next(self.gen)
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/query.py", line 292, in _row_block_stream
    for block in self._column_block_stream():
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/transform.py", line 75, in gen
    next_block = get_block()
  File "/Users/apple/Desktop/Datazip/bi/venvdbt/lib/python3.9/site-packages/clickhouse_connect/driver/transform.py", line 45, in get_block
    col_type = col_types[col_num]
IndexError: list index out of range

Configuration
Environment

clickhouse-connect version: tries 0.6.22 and 0.7.3
Python version: Python 3.9.13
Operating system: MacOs

ClickHouse server

ClickHouse Server version:
ClickHouse Server non-default settings, if any:
CREATE TABLE statements for tables involved:
Sample data for these tables, use clickhouse-obfuscator if necessary

Duplicate of https://github.com/ClickHouse/clickhouse-connect/issues/298.  We no longer actively support the experimental JSON type, and I have no idea what Superset would do with it anyway.


Refactor PushTx network code to use Moya

Using SamouraiAPI and the existing Samourai MoyaProvider streamlines the code and eliminates duplicate code (most importantly the endpoint definition). Will make using a different endpoint (🧅) for all API calls easier.
Note: Having the possibility to use testnet for DEBUG builds would be great. It would make testing easier and less expensive. A comprehensive test suite would be awesome as well, but I'll have to give that some thought. Some things might be challenging to test properly in an automatic fashion.

Merged upstream with https://github.com/Samourai-Wallet/Sentinel-iOS/pull/11


Blind Payload Not Working in POST

    I just realized this issue still persists when using "file --rawdata" with a post request.

I think you fixed it for GET, but not POST.
I see the Referrer header is working with the blind payload, but not the parameters in the data of the POST request
Originally posted by @tekcap in https://github.com/hahwul/dalfox/issues/409#issuecomment-1279844573

yup still does not work with POST v2.9.3


docs: document SessionConfig

Which issue does this PR close?
Closes #8770.
Rationale for this change
It took me a surprisingly long time to figure out how to set these configuration options.
What changes are included in this PR?

Link back to SessionConfig from various *Options structs so users can figure out where they are supposed to set them.
Added examples of how to set options in SessionConfig.
Brought up options() and options_mut() methods to beginning of the impl so that they are near the top of the documentation page. This makes them more visible. Also added simple examples for each.

Are these changes tested?
The documentation changes include doc-tested examples.
Are there any user-facing changes?
These are just documentation changes.

Thanks again @wjones127


Prepare for Laravel 9

This prepares the package to be installed together with Laravel 9.
Added:

Dependencies for Laravel 9
Tests for Laravel 9 on PHP 8.0 and PHP 8.1
Tests for Laravel 8 on PHP 8.1

Hi @JustSteveKing Is it possible to review this PR and get it merged?

@canvural If you want to test these changes you can edit your composer file as follows:
{
    "repositories": [
        {
            "type": "git",
            "url": "https://github.com/jubeki/parental"
        }
    ],
    "require": {
        "calebporzio/parental": "dev-prepare-for-laravel-9"
    }
}


Think about having tool/topic headers in the Discussion instead of days

Participants were asking Snakemake questions later in the week and were not sure where to put them

(switching from HackMD to Discussion section on Canvas)


ERROR: Could not build wheels for pycocotools, which is required to install pyproject.toml-based projects

uilding wheels for collected packages: groundingdino, pycocotools
Building wheel for groundingdino (setup.py): started
Building wheel for groundingdino (setup.py): finished with status 'done'
Created wheel for groundingdino: filename=groundingdino-0.1.0-py3-none-any.whl size=85137 sha256=768c4f4f8cd61e52b67a58c5428f0fd3ff9b3c04a9506ea9e5a285cdb5fc4636
Stored in directory: C:\Users\SZCM02\AppData\Local\Temp\pip-ephem-wheel-cache-9vq8mywu\wheels\85\2b\15\c5a09de5cf3f52e0609c97c8335f8f40f01d4855e46dfd0e26
Building wheel for pycocotools (pyproject.toml): started
Building wheel for pycocotools (pyproject.toml): finished with status 'error'
Successfully built groundingdino
Failed to build pycocotools
stderr: WARNING: Ignoring invalid distribution -rotobuf (d:\baidunetdiskdownload\sd-webui-aki\sd-webui-aki-v4\py310\lib\site-packages)
WARNING: Ignoring invalid distribution -rotobuf (d:\baidunetdiskdownload\sd-webui-aki\sd-webui-aki-v4\py310\lib\site-packages)
Running command git clone --filter=blob:none --quiet https://github.com/IDEA-Research/GroundingDINO 'C:\Users\SZCM02\AppData\Local\Temp\pip-req-build-2p8n9n9p'
error: subprocess-exited-with-error
× Building wheel for pycocotools (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [23 lines of output]
  running bdist_wheel

  running build

  running build_py

  creating build

  creating build\lib.win-amd64-cpython-310

  creating build\lib.win-amd64-cpython-310\pycocotools

None
copying pycocotools\coco.py -> build\lib.win-amd64-cpython-310\pycocotools
GroundingDINO install failed. Please submit an issue to https://github.com/IDEA-Research/Grounded-Segment-Anything/issues.
  copying pycocotools\cocoeval.py -> build\lib.win-amd64-cpython-310\pycocotools

  copying pycocotools\mask.py -> build\lib.win-amd64-cpython-310\pycocotools

  copying pycocotools\__init__.py -> build\lib.win-amd64-cpython-310\pycocotools

  running build_ext

  building 'pycocotools._mask' extension

  creating build\temp.win-amd64-cpython-310

  creating build\temp.win-amd64-cpython-310\Release

  creating build\temp.win-amd64-cpython-310\Release\common

  Bcreating build\temp.win-amd64-cpython-310\Release\pycocotools

  "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\lib\site-packages\numpy\core\include -I./common -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\include -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\ATLMFC\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /Tc./common/maskApi.c /Fobuild\temp.win-amd64-cpython-310\Release\./common/maskApi.obj

  maskApi.c

  ./common/maskApi.c(151): warning C4101: \xa1\xb0xp\xa1\xb1: δ\xd2\xfd\xd3õľֲ\xbf\xb1\xe4\xc1\xbf

  "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\bin\HostX86\x64\cl.exe" /c /nologo /O2 /W3 /GL /DNDEBUG /MD -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\lib\site-packages\numpy\core\include -I./common -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\include -ID:\BaiduNetdiskDownload\sd-webui-aki\sd-webui-aki-v4\py310\Include "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\ATLMFC\include" "-IC:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.29.30133\include" "-IC:\Program Files (x86)\Windows Kits\NETFXSDK\4.8\include\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\ucrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\shared" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\um" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\winrt" "-IC:\Program Files (x86)\Windows Kits\10\include\10.0.19041.0\cppwinrt" /Tcpycocotools/_mask.c /Fobuild\temp.win-amd64-cpython-310\Release\pycocotools/_mask.obj

  _mask.c

  c1: fatal error C1083: \xce޷\xa8\xb4\xf2\xbf\xaaԴ\xceļ\xfe: \xa1\xb0pycocotools/_mask.c\xa1\xb1: No such file or directory

  error: command 'C:\\Program Files (x86)\\Microsoft Visual Studio\\2019\\Community\\VC\\Tools\\MSVC\\14.29.30133\\bin\\HostX86\\x64\\cl.exe' failed with exit code 2

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for pycocotools
ERROR: Could not build wheels for pycocotools, which is required to install pyproject.toml-based projects

I think it's better to check some tutorials on how to install pycocotools on windows, we did not test the windows case before due to the environments reasons, there're some windows pycocotools installation tutorial online~


1.16 pre3 things

mapped every new class except 5395 because i dont understand codecs lol
also other misc stuff

Mind change branch to rc1?


We should add tests for the new config class

I saw that a new class called Config appeared on the project! Should we write tests for it? I am more than happy to do it!

Definitely, it was part of this PR
https://github.com/scopeta/focusedme/pull/9
On Wed, Oct 7, 2020 at 2:29 PM Guilherme Lucas<EMAIL_ADDRESS>wrote:

I saw that a new class called Config appeared on the project! Should we
write tests for it? I am more than happy to do it!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scopeta/focusedme/issues/13, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC2C3SHE3C2QTCUI2X2RLJTSJTMS7ANCNFSM4SH5WODQ
.

Awesome! ill take care of it!


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
63b6da902f3f6ea8a70da37dc3e81ed0925d2dd8
link
/test istio-presubmit

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


update docs - wrong word

directly → directory
Just at typo.

This change is

@bors-servo r+
Thanks!

:pushpin: Commit ada4d15 has been approved by nox

:hourglass: Testing commit ada4d15 with merge 05e30f0...

:sunny: Test successful - status-travis
Approved by: nox
Pushing 05e30f0bceda8939de07c41368e82e2977d22959 to master...


Added disallow hook to start to deprecate disable hook.

https://github.com/feathersjs/feathers-hooks-common/issues/28 we agreed to create a new hook rather than change disable.

disable hook has a predicate & we are deprecating predicates.
the disable predicate is implemented in perhaps the wrong sense.
In https://github.com/feathersjs/feathers-hooks-common/issues/28 we agreed to create a new hook rather than change disable.

Both are much better names. I'd go with disallow to stay within the "dis"
family.
On Wed, Jan 18, 2017 at 1:57 PM, David Luecke<EMAIL_ADDRESS>wrote:

@daffl commented on this pull request.
In README.md
https://github.com/feathersjs/feathers-hooks-common/pull/108#pullrequestreview-17298468
:

@@ -24,8 +24,7 @@ will be removed next version. Use the new populate hook.

Use deleteByDot rather than setByDot(obj, path, value, true).
The delete hook should be used instead of remove.
You will need to wrap delete it in an conditional if you want it to work like remove does.
-- The stop hook may be used instead of disable.
-The disable hook when false instead of the documented true.
+- The disableMethod hook may be used instead of disable.

Should we maybe call it disallow or refuse?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/feathersjs/feathers-hooks-common/pull/108#pullrequestreview-17298468,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeznw_MUTee2ijsss05S-14jPbtP1A_ks5rTmCygaJpZM4LnQEb
.

I prefer names that are clear about what they do, even if they get long. I would prefer a name like disallowProvider. What do you think?

I always think short names combined with the right parameters work. Something like disallow('external') or disallow('rest') is fairly explanatory to me. The provider postfix only makes sense if you know what a provider is (and I think @ekryski and @marshallswain wanted to change to calling it Transport).

Since we are already having to do a major version and have breaking changes, we may as well just call it disable and perform the functionality we want to. Rip that bandaid off instead of having even more legacy code to maintain. That's my 2 cents anyway.

Otherwise I agree with @daffl. Just go with disallow.

Waiting for a ship it then.

:shipit:

:shipit:


pattern for modal close button is complex

The modal demos which include a close button seems overfly complex.
The button could be placed in the header and floated right to achieve the same result.

          <button class="pf-c-button pf-m-action fa-pull-right">

          </button>

            Overwrite existing file?

vs

                Overwrite existing file?

              <button class="pf-c-button pf-m-action">

              </button>

We don't have a fa-pull-right class or any utility class in PF4.
We chose to use the split layout because since users heavily modify patternfly depending on their usecases, by position items within layouts across the system, we are giving them more flexibility at the cost of having more markup.
Ideally it'd be a spaced-between flex displayed header and the title and close btn would accommodate themselves. Since the modal should always have a close btn, have it as a default scoped to the component is not a bad idea.
What do you think?

Sorry the class name fa-pull-right was used in my testing and didn't change it. But as an example it's still valid.
If consistency is the goal, then I think treating the close button as a first class element is better. pf-c-modal-bos__close could be used instead of a utility class.
Since the button needs to appear inside the content area of the modal, absolute positioning of the button could cause layout issues. The layout needs to flow. This is why I suggested floating it.
It's also possible that one might use a modal without a header? If so, what's the markup for this use case with a close button? Using a flex layout here would create a vertical dead space beneath the close button as an entire column of space is reserved.

You are absolutely right, if the header is not present the close btn should be there, therefor is part of the component.
@LHinson Should I create a issue to make this change or can this issue became the task?

We can use this issue, just update the description as necessary @andresgalante

After talking with the CSSers we've decided to create defaults for the modal box. This means:

It should have a close btn.
It should have a title.
the footer should position the action btns.

While making this change lets make sure that this can easily be modifiy with the layout if the user wishes to.

The demos also share a common title styling, I think that too should be a first class element. @andresgalante @christianvogt What do you think?

    <button class="pf-c-modal-box__close" aria-label="Close Dialog">

    </button>

      Modal Header

@mattnolting yes agreed

@christianvogt @mattnolting  Why is the modal close button different from other action (icon) buttons?

@dmiller9911 from a button perspective it's no different. My original concern was with regards to layout.

would it be possible to just do <button class="pf-c-button pf-m-action pf-c-modal-box__close">X</button> the modal close taking care of the positioning? Or would that stray too far from principles?
The alert component has something similar where the element inside the component is just a container with the positioning, and then a button is placed inside of that. For modal it might be something like
...

   ...

    <button class="pf-c-button pf-m-modifier">X</button>

...

@dmiller9911's suggestion aligns with what I originally proposed.


Mechanism for "suggested visualizations"

Each visualization should have a way of deciding if it might be appropriate for the current view of data.
We can then offer a "suggested visualizations" prompt which shows previews.

This is now a dupe of https://github.com/simonw/datasette-vega/issues/4


[hiccup-css] Use of unsigned shift operator prevents negative values

import { px } from<EMAIL_ADDRESS>
console.log(px(-10.666));

// Result   "4294967286px"
// Expected "-10px"

It could also be argued that decimal places should be allowed for px, as browsers support them and the rendered results are different between (e.g.) margin-left: 10px and margin-left: 10.5px

Hi @acarabott - sorry just saw this now (after merging your PR) - you're right & I even think we should amend all spatial units to using .toFixed() with 1-3 fractional digits... ?!
export const px = (x: number) => `${x.toFixed(1)}px`;

export const percent = (x: number) => `${x.toFixed(3)}%`;

Hmm, it doesn't seem like there's anything in the spec about limits. I'd be particularly wary about reducing the precision of % as with very large elements the results could be off by a number of pixels...
I use these helpers to prevent typos and as sugar to avoid `${value + otherValue}px`, so I think I would avoid any adjustments and let that be up to the caller:
export const px = (x: number) => `${x}px`;

Hey @acarabott - agreed & was thinking about that too, but then again if I really would want pixel precision, I wouldn't use percentages... 😉 In any way, I agree it's best to leave the rounding of these values to the user. Milliseconds are the only unit for which this is done now. New release is already out since last Friday...


KAFKA-13370: add unit test for offset-commit metrics

Follow up for https://github.com/apache/kafka/pull/11413#issuecomment-970395759, to add tests for offset-commit metrics.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@rhauch , per our discussion, here's the tests to be added. Thank you.

Failed tests are unrelated. Thank you.
    Build / JDK 17 and Scala 2.13 / kafka.admin.LeaderElectionCommandTest.[1] Type=Raft, Name=testTopicPartition, Security=PLAINTEXT
    Build / JDK 17 and Scala 2.13 / kafka.admin.LeaderElectionCommandTest.[1] Type=Raft, Name=testTopicPartition, Security=PLAINTEXT
    Build / JDK 8 and Scala 2.12 / kafka.admin.LeaderElectionCommandTest.[1] Type=Raft, Name=testAllTopicPartition, Security=PLAINTEXT
    Build / JDK 8 and Scala 2.12 / kafka.admin.LeaderElectionCommandTest.[1] Type=Raft, Name=testAllTopicPartition, Security=PLAINTEXT

Thanks @showuon for the PR. It looks good, can you rebase it?


Wish Curation List: Change calendar icon to indicate today's the day

Proposal to add Change calendar icon to indicate today's the day to to the site.
Feature Name
Change calendar icon to indicate today's the day
Functionality
Date default displays with a blue border
When today's the day, show attention-grabbing border
Notes

@aclaire-thd There are a few other simple design changed need here ( convert text blue to black, logos and need to create a black calendar icon). Shall I create a new issue or add it here? LMK!

@hellonoosh if the design changes are related to today being the day, then I think they belong in this issue - thanks!

I have grabbed this one

Is this issue closed ? Thanks.

Hi @aclaire-thd, is the issue open ? I'd like to work on it.

Hello @aclaire-thd , Is the issue still open? I would like to work on it. Thank you


Template tokens path in jmx and add to doc

Purpose

$subject

Codecov Report
Patch coverage has no change and project coverage change: +54.61% :tada:

Comparison is base (b7d6134) 25.49% compared to head (cebcbb5) 80.10%.
Report is 10 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1683       +/-   ##
===========================================
+ Coverage   25.49%   80.10%   +54.61%
===========================================
  Files         262        9      -253
  Lines       30205      548    -29657
  Branches     5088      246     -4842
===========================================
- Hits         7700      439     -7261
+ Misses      22243      109    -22134
+ Partials      262        0      -262

Flag
Coverage Δ

adapter
?

common-controller
?

config-deployer-service
?

idp-domain-service
80.10% <ø> (ø)

router
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 253 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.