Not able to fetch images sending blank pages

Example page
http://ampletrails.com/attendance-machine
Error in apache error.log
[Tue Jul 14 08:56:04.223284 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>11840] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/themes/bizway/images/search.png for 5 sec
[Tue Jul 14 08:56:08.856891 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>41024] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2013/02/CCE-Report-Card1-523x1024.png for 10 sec
[Tue Jul 14 08:56:09.223538 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>11840] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/themes/bizway/images/search.png for 10 sec
[Tue Jul 14 08:56:13.574533 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>77504] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/plugins/digg-digg/image/ajax-loader.gif for 5 sec
[Tue Jul 14 08:56:13.857170 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>41024] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2013/02/CCE-Report-Card1-523x1024.png for 15.001 sec
[Tue Jul 14 08:56:14.223777 2015] [pagespeed:warn] [pid 13327:tid<PHONE_NUMBER>11840] [mod_pagespeed <IP_ADDRESS>-7251 @13327] Waiting for completion of URL http://ampletrails.com/wp-content/themes/bizway/images/search.png for 15 sec
[Tue Jul 14 08:56:51.030840 2015] [pagespeed:warn] [pid 13326:tid<PHONE_NUMBER>44064] [mod_pagespeed <IP_ADDRESS>-7251 @13326] CSS parsing error in https://ampletrails.com/automatic-school-students-attendance-machine/e-learning-blog
[Tue Jul 14 09:01:40.136047 2015] [pagespeed:warn] [pid 13326:tid<PHONE_NUMBER>84800] [mod_pagespeed <IP_ADDRESS>-7251 @13326] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2012/07/ampletrails_brochure_front.gif for 5.001 sec
Files are present
ls -ltrh wp-content/uploads/2012/07/ampletrails_brochure_front.gif
-rw-rw-rw- 1 www-data www-data 1.3M Jan  4  2014 wp-content/uploads/2012/07/ampletrails_brochure_front.gif

Duplicate of #1048

@contactmayankjain are you still having this issue?  We're preparing a release with a mitigation for the bug, but because we haven't been able to reproduce it here it would be really very helpful if you could install https://github.com/pagespeed/mod_pagespeed/releases/tag/<IP_ADDRESS> which has the draft fix, and let us know it the problem recurs.

Can you please let me know how can I install it?
On Tue, Jul 28, 2015 at 8:35 PM, Jeff Kaufman<EMAIL_ADDRESS>wrote:

@contactmayankjain https://github.com/contactmayankjain are you still
having this issue? We're preparing a release with a mitigation for the bug,
but because we haven't been able to reproduce it here it would be really
very helpful if you could install
https://github.com/pagespeed/mod_pagespeed/releases/tag/<IP_ADDRESS> which
has the draft fix, and let us know it the problem recurs.
—
Reply to this email directly or view it on GitHub
https://github.com/pagespeed/mod_pagespeed/issues/1108#issuecomment-125641133
.

--
Please refer us to your friends and family if you are satisfied, otherwise
let us know.
Thank You
Regards,
Mayank Jain :)
ampletrails.com
India +91<PHONE_NUMBER>, +91<PHONE_NUMBER>
We have specialization in Attendance Machine|Bulk SMS| Website
Development|Learning Management System|University Management System|CCTV
Cameras|RFID Cards|Library Management System|Access Control System
Disclaimer: This message contains confidential information and is intended
only for the individual named. If you are not the named addressee(s) you
should not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secured or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission. If verification is required please request a hard-copy
version. AmpleTrails

Are you running CentOS/RedHat or Debian/Ubuntu?  Are you running 32-bit or 64?

Its Ubuntu 64 bit.
On Wed, Jul 29, 2015 at 10:53 PM, Jeff Kaufman<EMAIL_ADDRESS>wrote:

Are you running CentOS/RedHat or Debian/Ubuntu? Are you running 32-bit or
64?
—
Reply to this email directly or view it on GitHub
https://github.com/pagespeed/mod_pagespeed/issues/1108#issuecomment-126025883
.

--
Please refer us to your friends and family if you are satisfied, otherwise
let us know.
Thank You
Regards,
Mayank Jain :)
ampletrails.com
India +91<PHONE_NUMBER>, +91<PHONE_NUMBER>
We have specialization in Attendance Machine|Bulk SMS| Website
Development|Learning Management System|University Management System|CCTV
Cameras|RFID Cards|Library Management System|Access Control System
Disclaimer: This message contains confidential information and is intended
only for the individual named. If you are not the named addressee(s) you
should not disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake
and delete this e-mail from your system. E-mail transmission cannot be
guaranteed to be secured or error-free as information could be intercepted,
corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
The sender therefore does not accept liability for any errors or omissions
in the contents of this message, which arise as a result of e-mail
transmission. If verification is required please request a hard-copy
version. AmpleTrails

Release <IP_ADDRESS> is now out, so you should install that:
sudo apt-get update
sudo apt-get upgrade
sudo /etc/init.d/apache2 restart

I did the update by using the commands provided by you.
Now in error.log I am seeing
[Fri Jul 31 07:19:53.817604 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>74272] [mod_pagespeed <IP_ADDRESS>-7251 @20298] CSS parsing error in http://ampletrails.com/attendance-machine
[Fri Jul 31 07:20:07.036418 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>89152] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2014/12/K21-Essl-Identix-Attendance-Machine.png for 5 sec
[Fri Jul 31 07:20:09.312069 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>81856] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/02/k-13.jpg for 5.001 sec
[Fri Jul 31 07:20:09.339918 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>96448] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/05/KF200-Face-Time-Attendance-System-essl-Identix.jpg for 5 sec
[Fri Jul 31 07:20:12.036715 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>89152] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2014/12/K21-Essl-Identix-Attendance-Machine.png for 10 sec
[Fri Jul 31 07:20:14.312297 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>81856] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/02/k-13.jpg for 10.001 sec
[Fri Jul 31 07:20:14.340205 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>96448] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/05/KF200-Face-Time-Attendance-System-essl-Identix.jpg for 10.001 sec
[Fri Jul 31 07:20:17.036970 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>89152] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2014/12/K21-Essl-Identix-Attendance-Machine.png for 15 sec
[Fri Jul 31 07:20:18.572916 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>03744] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2012/06/Logo_Ample_Trails_v4.png for 5 sec
[Fri Jul 31 07:20:19.312555 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>81856] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/02/k-13.jpg for 15.001 sec
[Fri Jul 31 07:20:19.340450 2015] [pagespeed:warn] [pid 20298:tid<PHONE_NUMBER>96448] [mod_pagespeed <IP_ADDRESS>-7251 @20298] Waiting for completion of URL http://ampletrails.com/wp-content/uploads/2015/05/KF200-Face-Time-Attendance-System-essl-Identix.jpg for 15.001 sec

these logs appear to be from <IP_ADDRESS>.
@contactmayankjain it seems like you might be tracking the stable branch.
See the instructions here for changing channels
https://developers.google.com/speed/pagespeed/module/download?hl=en#how-to-change-channels

Hello!
New message, please read http://empiretoorak.com/book.php?p
Mayank Jain

Hello!
New message, please read http://xerox.web.tr/changed.php?1s4r7
Mayank Jain

Hello!
You have a new message, please read http://erdallarteknik.com/peak.php?w7yl
Mayank Jain

Hi,
Please take a look at all that  stuff  and  tell  me what you think  about it, the info is here http://rossell.delins.name/e7vby/81
Pardon my monkey thumbs, Mayank Jain


update() and insert() returns

These methods currently returns a dictionary contained in a list, a list always 1 in length, which makes it useless.
Small change, but it causes API breakage.
Perhaps deprecate somehow.

Moved to projects


animation-bug: unwanted attributes with from/to

animations are currently not working with css, because unwanted attributes are being added to the stylesheet.
from the solidjs-template (npx degit solidjs/templates/js my-app), the animation of the logo gets compiled to:
@keyframes c-Anonymous-c8d13f94-0-logo-spin{from[s\:c-Anonymous-c8d13f94-0]{transform:rotate(0deg)}to[s\:c-Anonymous-c8d13f94-0]{transform:rotate(360deg)}}

while it should be
@keyframes c-Anonymous-c8d13f94-0-logo-spin{from{transform:rotate(0deg)}to{transform:rotate(360deg)}}

Seems like the body of keyframes are being treated as style rules by the parser.

Should be fixed in 0.7.5

nice, works on my end too.
thanks alexis 👍


Newly released version should be 1.4.0 not 1.3.5

1.3.5 goes beyond fixing bugs and adds new API hence it shouldn't be 1.3.5 but it should be 1.4.0

The 1.4.0 is reserved for our new ota feature, which may bring some breaking changes.
We have 1.3.7 which should be released last week, but unfortunatly got some underlying RTX issue, so had to move it to this week.


Question: How to query by unwise_detid?

(Sorry, I see no other way to submit questions.)
Is there not a method to search by unwise_detid?   I already know for which unWISE sources I wish to have the epoch photometry.

Currently, the catalog can only be searched by coordinates.
(I'm fine with submitting questions here, so no need to apologize for that.)

Should I make a change request?  ;^)

Please note that the unwise_objid from the unWISE catalog (Schlafly+2019) is not the same than the unwise_detid from the unTimely catalog. The unwise_detid from the unTimely catalog refers to a single detection whereas the unwise_objid from the unWISE catalog refers to an object/source. unTimely detections and unWISE objects are not related in any way. Also, unTimely detections are not related in any way across epochs. So, the only way to get epoch photometry for an object is to search the unTimely catalog by coordinates and inspect the result table together with the finder charts (overlay_labels=True) to reliably assign detections to a specific source. The overlay labels match the source labels (source_label column) in the result table.

Dear Frank,
Thanks for the clarification. Very helpful.
Ron
On Tue, Jun 20, 2023, 19:50 Frank Kiwy @.***> wrote:

Please note that the unwise_objid from the unWISE catalog (Schlafly+2019)
is not the same than the unwise_detid from the unTimely catalog. The
unwise_detid from the unTimely catalog refers to a single detection whereas
the unwise_objid from the unWISE catalog refers to an object/source.
unTimely detections and unWISE objects are not related in any way. Also,
unTimely detections are not related in any way across epochs. So, the only
way to get epoch photometry for an object is to search the unTimely catalog
by coordinates and inspect the result table together with the finder charts
(overlay_labels=True) to reliably assign detections to a specific source.
The overlay labels match the source labels (source_label column) in the
result table.
—
Reply to this email directly, view it on GitHub
https://github.com/fkiwy/unTimely_Catalog_explorer/issues/4#issuecomment-1599250625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJQPCUSQ4QFKP3NAKI4K75LXMHPHNANCNFSM6AAAAAAZNHIEXA
.
You are receiving this because you authored the thread.Message ID:
@.***>


MiddlewareFactoryInterface should be configured in web.php

Yiisoft\Middleware\Dispatcher\MiddlewareFactoryInterface belongs to the config web.php, but placed to common.php for overwrite configuration web.php from yiisoft/middleware-dispatcher in application.
Maybe has solution for place configuration to web.php ?

Yes, it should not be in common. Does it break if just moved to web?

Yes, it should not be in common. Does it break if just moved to web?

Yes, it should not be in common. Does it break if just moved to web?

Seems this is will be work, but we can't guarantee what config plugin merge web-configuration in right order.
For the config plugin configurations web.php from yiisoft/middleware-dispatcher and yiisoft/request-model are on the same level.

Yes, it should not be in common. Does it break if just moved to web?

Seems this is will be work, but we can't guarantee what config plugin merge web-configuration in right order.
For the config plugin configurations web.php from yiisoft/middleware-dispatcher and yiisoft/request-model are on the same level.


Fix broken status endpoint

In https://github.com/alphagov/digitalmarketplace-search-api/pull/34 I changed the way the search service functions returned multiple responses. However, I forgot to make the required change in the status view.
I've also added a minimal test of the status endpoint.

This still seems to be broken for the case when ElaticSearch is down:

Good spot, that should be fixed (and with a test) now.


streaming server gets terminated not capable to handle CTRL+C

See: https://github.com/projectceladon/cloud-streaming
To reproduce:

Connecting AIC to encoding and streaming servers defined at https://github.com/projectceladon/cloud-streaming
Do not connect any client
Press CTRL+C in streaming container

Expectation is that streaming container will catch SIGINT sent by CTRL+C and normally terminate. Instead it gets aborted:
[7375]<PHONE_NUMBER>.329581  [INFO] :  irrv-receiver: IRRV_CTRL_STOP
[7375]<PHONE_NUMBER>.270583  [INFO] :  irrv-receiver: all stopped
[7375]<PHONE_NUMBER>.270619  [INFO] :  ics-p2p-client: Deinit: Deleting server instance.
terminate called without an active exception
Aborted

Running via gdb provides this stack:
Thread 1 "ga-server-perio" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=135076149925696) at ./nptl/pthread_kill.c:44
44      ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=135076149925696) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=135076149925696) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=135076149925696, signo=signo@entry=6) at ./nptl/pthread_kill.c:89
#3  0x00007ad9de01f476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26
#4  0x00007ad9de0057f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x00007ad9de2c7bbe in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x00007ad9de2d324c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#7  0x00007ad9de2d32b7 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007ad9dcd58397 in vhal::client::CommandChannelInterface::~CommandChannelInterface() () from /opt/lib/libvhal-client.so.0
#9  0x00007ad9ddec438c in ga::webrtc::ICSP2PClient::~ICSP2PClient() () from /opt/lib/ga/server-webrtc.so
#10 0x00007ad9ddecd0b2 in std::shared_ptr<ga::webrtc::ICSP2PClient>::~shared_ptr() () from /opt/lib/ga/server-webrtc.so
#11 0x00007ad9de022495 in __run_exit_handlers (status=0, listp=0x7ad9de1f6838 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true, run_dtors=run_dtors@entry=true) at ./stdlib/exit.c:113
#12 0x00007ad9de022610 in __GI_exit (status=<optimized out>) at ./stdlib/exit.c:143
#13 0x00007ad9de006d97 in __libc_start_call_main (main=main@entry=0x5a4b16ef1530 <main>, argc=argc@entry=14, argv=argv@entry=0x7ffc12898678) at ../sysdeps/nptl/libc_start_call_main.h:74
#14 0x00007ad9de006e40 in __libc_start_main_impl (main=0x5a4b16ef1530 <main>, argc=14, argv=0x7ffc12898678, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
    stack_end=0x7ffc12898668) at ../csu/libc-start.c:392
#15 0x00005a4b16ef33f5 in _start ()

Issues happens in vhal::client::CommandChannelInterface::~CommandChannelInterface() since one of the working thread is not joined and program gets aborted as soon as not terminated thread runs out of scope. See (ftc_talker_thread_ not joined):
https://github.com/projectceladon/libvhal-client/blob/3980f24a663396541313b27dc687ffd7454e44f1/source/command_channel_interface_impl.h#L306

Fix in #8.


Release 1.0.0

🎉  Thanks to everyone who contributed to v1.0.0!

Update changelog
Update contributors list
Add FAQ to GH issue template
Add example code for accessing Quill instance
Add React 16 compatibility to roadmap

Closes #113, #150, #132, #117, #86, #62

Yesssss.


sokol_gfx.h: Cleanup resource 'unbinding' behaviour...

This implements the following new "clarifications" in the resource binding behaviour:

in the GL backend: creating or updating a resource restores the previous resource binding (this may have behaved wrong before when a resource was created or updated between a call to sg_apply_bindings() / sg_update_...() and sg_draw()

in sg_commit(), make sure to unbind all resources that were bound in the frame (just to prevent any accidental resource leaks)

sg_apply_bindings() will still NOT unbind any "unused" resource slots, this is too much hassle in the GL backend. Instead this happens at the end of the frame in sg_commit().

minor GL backend fix: any attempts to bind a texture to a too high slot number (GL_MAX_COMBINED_IMAGE_UNITS) will be silently dropped (before this would have produced a GL error... however this would only be an issue for very old GLES2 implementations which are only guaranteed to have 8 texture slots).

"Correct code" shouldn't require any changes.

Unfortunately when trying to compile with SOKOL_GLCORE33 it fails by not finding GL_MAX_COMBINED_IMAGE_UNITS, so I couldn't test.

...ah alright, I haven't added that define yet to the "mini GL loader" in sokol_app.h for the Windows platform. On macOS where I'm currently testing, the system GL headers are used.

Should work now on GL on Windows, needs an update on sokol_app.h

Tested on windows with this (slightly) modified dyntex sample code, black texture on GLCORE33 and assertion fail on D3D11.

Ok, kinda expected, since with the modified code sokol_gfx.h has no knowledge that the fragment shader has a texture sampler. I guess the assertion in D3D11 is coming from D3D's validation layer itself.
With the new shader-code-generation stuff, the shader compiler will provide reflection information to the C code, so that such a situation should become a proper validation error in sokol_gfx.h.

...note to self: the Metal backend already conforms to the "behaviour clarification" outlined above.

...and D3D11 also conforms to the "clarification", ready for merge.


Revert making parquet::data_type and parquet::arrow::schema experimental

Which issue does this PR close?
Closes #1032
Rationale for this change
#1134 was a tad overzealous and moved some functionality behind the experimental flags that downstream projects depend on.
What changes are included in this PR?

arrow schema conversion functions are made public, these are used by IOx to get the arrow schema from parquet metadata cached in its catalog
data_type is made public, this is used by sqlite2parquet in order to interface with the ColumnWriter APIs

I debated spending the time to instead mark the various bits of these modules experimental, but since the move to more frequent breaking releases (#1120) there seems to be limited value add from such an undertaking. The concept of experimental made sense when breaking changes were quarterly, now that they're biweekly...
Are there any user-facing changes?
No breaking changes, this can (and perhaps should be) a patch release.

Codecov Report

Merging #1244 (6a4469c) into master (02573e9) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1244   +/-   ##
=======================================
  Coverage   82.95%   82.95%
=======================================
  Files         178      178
  Lines       51522    51522
=======================================
+ Hits        42740    42741    +1
+ Misses       8782     8781    -1

Impacted Files
Coverage Δ

arrow/src/array/transform/mod.rs
84.64% <0.00%> (-0.13%)
:arrow_down:

parquet_derive/src/parquet_field.rs
65.98% <0.00%> (ø)

parquet/src/encodings/encoding.rs
93.71% <0.00%> (+0.19%)
:arrow_up:

arrow/src/datatypes/datatype.rs
66.80% <0.00%> (+0.42%)
:arrow_up:

Continue to review full report at Codecov.

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

DataType is used in odbc2parquet, too. I would welcome to have it back in the public API again, or to at least have an alternative.

Thank you for the report @pacman82  👍

You are welcome @alamb !

Thanks for merging!

This should be available in arrow 9.0.0 (scheduled for release in ~ Feb 7, 2022) -- I'll make an RC next friday and then it takes 3ish days to get approved


UPDATED READ.ME

Description
   Minor change in Read.me

What is changing?
     Changed 'mongodb://localhost:27017' to 'mongodb://<IP_ADDRESS>:27017'

Is there new documentation needed for these changes?
       No

What is the motivation for this change?
     Earlier one was not working.

Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: type(NODE-xxxx)[!]: description

Example: feat(NODE-1234)!: rewriting everything in coffeescript

[x] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

hey @RajBhattacharyya  - I went to make a change to the readme update and messed up your fork.  Sorry about that 🙁
I ended up just making the changes on a separate branch, you're still the author on the commit since I squashed my first commit into yours.
We'll still make sure to give you credit too.  thanks for your submission!
https://github.com/mongodb/node-mongodb-native/pull/3509


Add script for travis CI test, Fixes #69

@frewsxcv @Manishearth I've renamed the directories and the bash script. Please review.

@Manishearth Updated.

You need to add the bin directory to the PATH (~/.cargo/bin I think, but could be wrong)
Current one is causing failures on travis:
test/run.sh: line 4: cargo-fuzz: command not found

sed: can't read fuzz/fuzzers/fuzzer_script_1.rs: No such file or directory

test/run.sh: line 6: cargo-fuzz: command not found

also, this will only work on nightly, you should probably restrict this to that platform

@Manishearth I did add the path to binaries to PATH. Now there is another problem, seems related to this https://github.com/rust-lang/cargo/issues/3192

Add
[workspace]
members = ["."]

to the testcrate

@Manishearth unfortunately that doesn't solve the problem
error: multiple workspace roots found in the same workspace:
  /home/travis/build/rust-fuzz/cargo-fuzz/test/testcrate/fuzz
  /home/travis/build/rust-fuzz/cargo-fuzz/test/testcrate

Add a similar key to cargo-fuzz itself?

@Manishearth no, every Cargo.toml has a workspace member, but the issue remains.

I guess a workaround would be to copy this folder to the parent directory, cd there, and run the tests from there.

Seems that moving the tescrate to root of cargo-fuzz still doesn't solve the issue. Probably we should wait for a solution from Cargo team. :thinking:

Can this get revisited? The issue posted to Cargo has been closed with the consensus that nightly works okay, which is fine for us.

triggered a rebuild, let's see if it works

Moved to  https://github.com/rust-fuzz/cargo-fuzz/pull/92


Added support for custom remote pushurl

Can you test this on a repo using SQ?

I tested this using SQ


B63 - Remove redundant sorting from output filters

It was noticed that when data goes through DropOffPlace, it can be sorted twice, which is redundant. This work aims to remove the possibility of that happening.

https://github.com/NationalSecurityAgency/burrito-grande/issues/63

Just a question about where runOutputFilters is called on DropOffPlace.processData line 365. Is the data pre-sorted at this point?If not we should add a call to preFilterHook before runOutputFilters.
Looks good other than that.

I had to rebase. Not sure if that was a mistake in my local environment though. GitHub seems happy so probably just on my end. Just something to check.


Feature/yard doc

Overall feedback:

Get rid of private method documentation
Extend public methods that are being actively used by consumers


move from readthedocs to alternate

perhaps GitHub Pages?

Any particular reason we want to stop using readthedocs?  It's pretty much the standard for freely posting documentation and not worrying about rebuilding.

Yes, we want to be able to generate plots in the docs using Bokeh, and ReadTheDocs will not allow Sphinx extensions like this.  Basically, I want to make sure that the docs are generated and run their contained examples, and when they fail to generate, it means that the docs are out of date.
We will move to something that is no less automated than ReadTheDocs - Travis building the docs, then pushing to github pages.

Yup, sounds good.  Requires a little bit of trickery in saving credentials/encryption within Travis.


[DS-2913] Fix community parent logging infinite loop

https://jira.duraspace.org/browse/DS-2913

+1.  This fix is very helpful.


merge master into pubsub-hp

This commit merges master into pubsub-hp, in preparation for merging back.
This commit adds back previously deleted hand-written pubsub classes.
There is no new surface or feature, only renamings to reflect name changes in gax.
There are still ListenableFuture in the surface. I plan to move to RpcFuture in another PR since this is already humongous.

Coverage increased (+0.4%) to 83.452% when pulling 00df00b18762a5b8d70677c9e1603bb15bab2753 on pongad:pubsub-hp into 36e609e5fea47870e697f83bd41920822b5ea6f3 on GoogleCloudPlatform:pubsub-hp.

LGTM


install skipper on build docker image

What for?

I think now we don't need it
I'll revert when we're finish with the CI setup


Not found when image shared from camera on mobile

I'm using Bot Builder SDK v4, C#
When I attach an image from the desktop application I can get the attached file using the "downloadUrl" inside "Content". My problem comes when a user takes a photo from the mobile App, "Content" comes empty and if I use "ContentUrl" of the attachment object, I receive 404 Not found. Is there a workaround for downloding files shared from mobile this way?

What value are you getting in ContentUrl? There is an issue with inline image's content URL. We are working on it.

What value are you getting in ContentUrl? There is an issue with inline image's content URL. We are working on it.

Thank you for your answer, that is precisely my issue. Replacing "imgo" for "original" con the ContentURL solved my issue.
The following is an example of the url I'm getting on the ContentUrl:
https://smba.trafficmanager.net/amer/v3/attachments/0-cus-d10-2f3d647752092b4dca809dbb30d96414/views/imgo
Thank you, I was able to make a workaround that works in my scenario, I'm sending the image to
Custom Vision to make some evaluation... it would be nice to have the name of the file as well, I guess I'll have to wait for the fix

This issue has been fixed. Please re-open if you are still facing it.


Log yaw drift and reset all trackers

This logs tracker yaw difference between every full or yaw reset in the format [INFO] [HumanPoseManager] x seconds since last reset. Tracker yaw drifts: tracker mac address, x deg (x deg/min) | etc
Example with 3 BNO085: [INFO] [HumanPoseManager] 1162 seconds since last reset. Tracker yaw drifts: udp://F4:CF:A2:4C:B5:FB/0, 0.5888 deg (0.0304 deg/min) | udp://E8:DB:84:98:84:C2/0, 0.3599 deg (0.0186 deg/min) | udp://98:CD:AC:31:AE:B9/0, 0.5923 deg (0.0306 deg/min) |
Also reset every tracker to prevent the need to use logic where it doesn't belong. This is good anyways for visualizing trackers in GUI and should've been done a while ago.
Needs https://github.com/SlimeVR/SlimeVR-Server/pull/647

Ready for review and merge!


Fix self-assignment in ConvertPixel64RGBX16ToPixel48RGB16.

I'd like to express my support for merging this fix, as I've encountered the problem myself. :)


Aqara door/ window sensor as a contact sensor in Homebridge

Please explain your feature request in a one or two sentences.
Would like to know whether would it be possible to make Aqara door/window sensor as a contact sensor for garage door sensor as an alternative rather than using a sonoff DW2 -WiFi sensor?

Is your feature request related to a problem? Please describe.

Been using the sonoff DW2 WiFi sensor quite some time now and the reliability in terms of battery consumption is very bad which makes the sensor goes offline within a week of usage with new batteries..
Been testing with aqara door sensor now and it’s way much reliable. The only problem is I can’t make it to sync with my garage door state (open or close).

Any particular eWeLink devices that this relates to?

DW2 WiFi

Anything else?

Hi @BaskaraR
Any homebridge plugin cannot read accessory status from other native-HomeKit accessories or accessories from other homebridge plugins.
For this reason it would be impossible for the ewelink plugin to obtain the status of the aquara sensor, so obviously couldn't update the garage door accessory.
The only potential way of doing this would be slightly more complicated... the idea being you would need some form of ewelink device sending an update to the plugin when the contact sensor changes state...
For example if you were to set up a sonoff mini or basic... and use something like ifttt to update the ON/OFF of the switch as the contact sensor changes...

contact detected turns the switch OFF
contact not detected turns the switch ON

Then with a couple of changes to the plugin you could use this sonoff switch instead of the DW2 sensor.


fix: generateCanvasTexture generates textures twice the size

fix: #6083
bug: https://jsfiddle.net/JetLu/Lnzyx135/
fixed: https://jsfiddle.net/JetLu/3ok4n7La/

Thank you @JetLua


Happy birthday Eddie!!

Happy Birthday, Eddie!!! This is my first pull request. So I hope I don't break anything :)

loos good to merge

loos good to merge

Oh, alright then. Thanks :) 👍


Infinite redirect loop using urlMappingStrategy: rewrite

Hey there,
thanks for the library, I'm excited to see where this is heading in the future 🙂
When testing this library I pretty much instantly encountered an infinite redirect loop (Chrome/FF) using urlMappingStrategy: rewrite. I saw #96 but I'm not sure if these are related, the resolveLocaleFromRequest function didn't make a difference, sorry if it's a duplicate.
I forked the codesandbox from the docs page: https://codesandbox.io/p/sandbox/recursing-yonath-973rl3?file=/middleware.ts:6,5-6,29 and changed the strategy option parameter.
The loop happens after clicking a locale button or switching the locale in the URL manually

Unrelated but since I'm here: Do you see hiding the default locale from the URL as a valid feature request for this library? I've seen this as a popular URL strategy also used by other i18n libraries. If yes I can create an issue for it!

Thanks for the kind words. Can you try running the same locally? I believe CodeSandbox has issues with cookies, so that might be why you're getting this infinite redirection.

Oh you beat me to it, but thank you! Yes I can confirm it's also happening locally. I tried out the lib in a new project but didn't get far. After that I also tried the next-app example from this repo with the same result 🙂

I've published https://github.com/QuiiBz/next-international/releases/tag/0.9.5 which includes #146 and should fix the issue (sorry for the bad first impression of this library). Feel free to open another one if that's not the case!


baboossh: fix build

Incorporate PR https://github.com/cybiere/baboossh/pull/12 which updates import paramiko.py3compat import u -> paramiko.utils import u
ZHF: #265948
https://hydra.nixos.org/build/239038521
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

2 packages built:

baboossh
baboossh.dist

thanks!


Currency: support symbol-alt-narrow

Adds support for alternative symbols via 'symbolForm' option
Fixes #479

Thanks for your contribution. I will review your PR this weekend, but I've left a couple of inline notes about indentation.

Documentation needs update: https://github.com/jquery/globalize/blob/master/doc/api/currency/currency-formatter.md

There is a functional test, which is good. A bonus would be adding a unit test too.

I've left a couple of comments now, just let me know if you have any questions and thanks so far.

I've made the review updates myself (at https://github.com/rxaviers/globalize/tree/pr-631-continued). Although, due to Foundation changes and its updated CLA, I have been recommended not merge this PR (link) (cc @kborchers) until this is re-signed.

Thanks @gethinwebster

Superseded by #738


Fix Edit Bookmark and Authentication dialog theming

Task/Issue URL: https://app.asana.com/0/1157893581871903/1172335675952700
Description:
The changes in Android Release 5.52.1 (Beta) have somehow messed up with the theming in the Edit Bookmark dialog. This PR fixes that.
Screenshots:

Before
After SDK 21
After SDK > 23

Steps to test this PR:

Open app
Add a Bookmark
Tap on Edit

Good call @marcosholgado!
Updated

Username
Password

)


Adding koios api key support to spo page

After finding the staking button inoperative here I found the same issues on the mesh fork that I had deployed to Vercel. With @jinglescode support on discord we determined the api key was missing.
In my testing this is still not functional but is also not a regression of the current deployment as it currently not functional.

Update @meshsdk/core
Update @meshsdk/react
Created API key as local env var

the CICD checks in this PR are likely failing due to the dep installations requiring force install with 'npm install -f' in vercel.
Validated in personal Vercel deployment here:
https://staking-next-ts-hodlr-git-adding-koiosa-3005ff-my-team-5c660a1c.vercel.app/


Add redirect

Description & motivation

Adding one more redirect for the Using Sources page --
Old link: /reference/using-sources
New Link: /docs/build/sources

lgtm! looks like the build didn't go through bc of no files changed, so i would just verify the redirect is working once live, but it should from the looks of it!

Thank you!! i have been trying to get Netlify to force a preview with no luck. 😅

lgtm! looks like the build didn't go through bc of no files changed, so i would just verify the redirect is working once live, but it should from the looks of it!

Thank you!! i have been trying to get Netlify to force a preview with no luck. 😅

I've resorted to looking through the code and finding a good place to leave a comment 😂


[release-1.2] Skip syncing root cert if not in self signed CA mode

This is a cherry-pick of #18713
#17059

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
73a9f4737e1f04f5e3b56a2e66ea0c0295d42c2c
link
/test integ-mixer-k8s-presubmit-tests-release-1.2

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.

/test integ-mixer-k8s-presubmit-tests-release-1.2

@JimmyCYJ: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/integ-mixer-k8s-presubmit-tests.sh
73a9f4737e1f04f5e3b56a2e66ea0c0295d42c2c
link
/test integ-mixer-k8s-presubmit-tests-release-1.2

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.

/test integ-mixer-k8s-presubmit-tests-release-1.2


Fix typo document_filters.py

Fix typo in document_filters.py
BBS Patern -> BBS Pattern

Thanks for contribution!


EKS 1.16 Support

Opening this issue to handle all changes needed for EKS 1.16, which was released on April 30th:

https://aws.amazon.com/about-aws/whats-new/2020/04/amazon-eks-now-supports-kubernetes-version-1-16/
https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html#1-16-prequisites

I'm submitting a...

[ ] bug report
[X] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

I just upgraded our clusters to 1.16, and I spent quite some time debugging an issue related to kubelet arguments and annotations that are apparently no longer valid.
We were creating worker launch templates with the following kubelet argument, exactly like described on https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/spot-instances.md
kubelet_extra_args  = "--node-labels=kubernetes.io/lifecycle=spot"

These kubernetes.io annotations are no longer accepted. I updated them in our clusters to node.kubernetes.io/lifecycle=spot but not 100% sure if that is a "correct"/conventional value.

I just upgraded our clusters to 1.16, and I spent quite some time debugging an issue related to kubelet arguments and annotations that are apparently no longer valid, resulting in the nodes no longer joining the cluster.
We were creating worker launch templates with the following kubelet argument, exactly like described on /docs/spot-instances.md@master
kubelet_extra_args  = "--node-labels=kubernetes.io/lifecycle=spot"

These kubernetes.io annotations are no longer accepted. I updated them in our clusters to node.kubernetes.io/lifecycle=spot which works but not 100% sure if that is a "correct"/conventional value.

I ran into the same issue; I ended up using node.kubernetes.io/lifecycle=spot, but not sure if that's the convention either. I was a bit upset because it seems you also cannot use node-role.kubernetes.io since that's also a protected prefix.
I know --node-labels=kubernetes.io/lifecycle=spot is present in many examples, so it should probably be updated also in https://github.com/terraform-aws-modules/terraform-aws-eks/pull/857

@gertjangaillet It seems the node-role label has some changed in 1.16 => https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/2019-07-16-node-role-label-use.md

@gertjangaillet Also good discussion here: https://github.com/kubernetes/kubernetes/issues/75457

I just upgraded our clusters to 1.16, and I spent quite some time debugging an issue related to kubelet arguments and annotations that are apparently no longer valid, resulting in the nodes no longer joining the cluster.
We were creating worker launch templates with the following kubelet argument, exactly like described on https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/spot-instances.md
kubelet_extra_args  = "--node-labels=kubernetes.io/lifecycle=spot"

These kubernetes.io annotations are no longer accepted. I updated them in our clusters to node.kubernetes.io/lifecycle=spot which works but not 100% sure if that is a "correct"/conventional value.

Thanks for sharing your workaroud.  This helped put me on the right track for solving the same problem.  Additional other kubernetes.io node labels are no longer supported in 1.16 and will prevent nodes from joining the cluster. In my case I had to remove the alpha.service-controller.kubernetes.io/exclude-balancer=true label.

Great information @gertjangaillet 😃


Curses windows

Hi,
I was trying the plugin but it seems that there is something wrong with drawille and windows...?
I am using gvim in Windows 10. Apparently, it uses curses and it doesn't exist in windows.

@Aborres thank you for reporting the issue.
Can you check whether my last commit fix the issue?

Yes, it fixes it, thank you.
I have strange characters in the minimap but that might be because of the font.

Yes, you need to install a font that include braille glyphs.

Do you recommend anyone in particular? All I am trying are failing.
How do you set the minimap to start up with vim? I have tried to add it to my vimrc but it doesn't seem to be working.

Most 'recent' fonts should support braille patterns. You can check here whether the glyphs are present in your current font -- note that the font used by your terminal emulator has to have support for vim + minimap to be happy!
To have vim-minimap to start with vim, follow the installation instructions -- if those instructions do not work for you, please report the exact steps you've followed for us to be able to help you.


how to cache video?

No permanent cache, only temp cache.

how to set temp cache true.

android.media.MediaPlayer will do it, there is no api, we should not focuse on it


[WIP] Polly implementation

Have implemented all endpoints on Polly. Tested them but need to expand some more on SynthesizeSpeech as it has some complex parameter validation.
It parses basic PLS lexicon XML but it might choke on some proper real world examples, but until we see those we'll never know.
The SynthesizeSpeech endpoint returns binary data as is what AWS does but its just all \x00's, until someone complains about the format it will do. I was thinking we could just hexlify the first n bytes of a audio clip in mp3, ogg_vorbis and pcm for use with this, which would be really neat but until its needed we might as well hold off.
TODO:

[ ] Expand SynthesizeSpeech tests

Oh and also fixed template typo in the script that generates functions for you. Will probably PR some additions to that later, its awesome :smile:

Coverage decreased (-0.3%) to 92.77% when pulling fcacecbef0214790760a8efaeb7d3c3dad65388f on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Oh and also fixed template typo in the script that generates functions for you. Will probably PR some additions to that later, its awesome 😄

YES! I'm glad it's getting some use. Like so much of what we do it was a fantastic first pass but lacks tests and needs a little love from the community.
@toshitanian ^ Your scaffold script is helping out!

@toshitanian Yeah your script is great man ;-)

Coverage decreased (-0.2%) to 92.833% when pulling e61b9cc682e413da2644211736361774e7dfbe50 on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Coverage decreased (-0.1%) to 92.916% when pulling e61b9cc682e413da2644211736361774e7dfbe50 on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Coverage decreased (-0.1%) to 92.916% when pulling e61b9cc682e413da2644211736361774e7dfbe50 on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Wow flask is really picky about regex in urls :disappointed:
If this passes tests, then its good to go

Coverage decreased (-0.04%) to 93.027% when pulling dfb712848d554c15b2ba2b767b9cf5a13a3d6f4e on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Coverage decreased (-0.04%) to 93.027% when pulling cecbbb70e1287f8e588484cdd5051a1fd570752d on terrycain:polly into b17136e36c3a975aa2cebed15aec766bc6776260 on spulec:master.

Should all be good :smile:

This is so satisfying. Great work, @terrycain !

This is released as Moto version 1.1.15


react-markdown doesn't work in SSR dev

Describe the bug
react-markdown fails with ReferenceError: module is not defined when I try to import it from a module loaded with ssrLoadModule. It seems to be caused by mixing ES modules and CJS modules in the transitive dependencies. Everything works as expected when I add "type": "module" to package.json.
Reproduction

Clone this repo and install dependencies: https://github.com/cyco130/vite-react-markdown-issue
Run node ssr-module.mjs and observe that react-markdown works correctly when run directly.
Run node index.cjs and observe loading with SSR fails.
Add "type": "module" to package.json to fix it.

System Info
System:
    OS: Linux 5.4 Linux Mint 20.2 (Uma)
    CPU: (8) x64 Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz
    Memory: 365.33 MB / 15.53 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 14.18.1 - /usr/local/bin/node
    Yarn: 1.22.11 - ~/.npm-global/bin/yarn
    npm: 7.24.1 - ~/.npm-global/bin/npm
  Browsers:
    Chrome: 96.0.4664.45
    Firefox: 94.0
  npmPackages:
    vite: ^2.7.0-beta.9 => 2.7.0-beta.9

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

The code has:
import ReactMarkdown from "react-markdown";

In ssrImport there's a check:
        if (dep[0] !== '.' && dep[0] !== '/') {
            return nodeImport(dep, mod.file, resolveOptions);
        }

It's encountering:
/node_modules/react-markdown/index.js
/node_modules/react-markdown/lib/react-markdown.js

So this is not being treated as external. I think if we did it would fix this. @brillout has suggested several times that we treat all dependencies as external by default

This seems suspect to me:
https://github.com/vitejs/vite/blob/1f91cdb6c5c573fd9efd147e38cabc0e5f22028f/packages/vite/src/node/ssr/ssrExternal.ts#L144
pkg.type is referring the the package.json of the reproduction, but I think it should refer to the dependency's package.json instead?
This was added in https://github.com/vitejs/vite/pull/5197. CC @natemoo-re

Perhaps we should revisit the suggestion in this comment: https://github.com/vitejs/vite/pull/5544#issuecomment-962429655. I.e. rather than only externalizing packages that meet a certain specification, we should reverse that check, externalize by default, and only transform in certain cases where it's necessary. And I'm not sure it's ever necessary. I had been wondering about things like AMD or SystemJS, but I don't think Rollup works with those anyway? Because I realized that even to handle CommonJS, there's @rollup/plugin-commonjs. But there's no such plugin for AMD or SystemJS that I'm aware of. I've never encountered packages for bundling being distributed in those formats

rather than only externalizing packages that meet a certain specification, we should reverse that check, externalize by default, and only transform in certain cases where it's necessary.

Isn't it actually necessary to transform in this case, at least in production build? If we don't transform, the CJS build will try to require an ESM module which will break the build. It doesn't break the dev for some reason, but build doesn't work.

@cyco130 It's expected and a good thing, see https://github.com/vitejs/vite/issues/4340#issuecomment-889763481
@benmccann

. I.e. rather than only externalizing packages that meet a certain specification, we should reverse that check, externalize by default, and only transform in certain cases where it's necessary.

👍 And it makes reasoning about ssrExternal.ts a lot easier.

I dont think this issue should be added as a 2.7 goal. its not a breaking change and not a regression

Hmm. This particular report was broken before 2.7, but the line that's breaking currently was added in 2.7, so I'm not 100% sure there wouldn't be a regression for other libraries given that there is newly added code that's incorrect. In any case, this shouldn't be hard to get into 2.7 since I've sent a fix for it already: https://github.com/vitejs/vite/pull/5903

I agree with Niputi here, the fix looks a bit involved for this point of the beta. Let's try to fix the other two remaining regressions and do the release (https://github.com/vitejs/vite/milestone/4)

@patak-js I will have a look at these 2 regressions. (But let me finish 2 highest prio vite-plugin-ssr things I need to finish today. Hopefully I'll have some spare time for this later today.)

I still think it's incorrect to say there's no regression here in 2.7. While the reproduction the reporter shared doesn't demonstrate a regression, if you read the code it sure looks like there's one and I'd expect we could create a reproduction.
The newly introduced code says the package should be externalized if pkg.type === 'module' but is reading the wrong package.json. I think this means that if the user's project is of "type": "module" then all packages will be externalized. And per the discussion in https://github.com/vitejs/vite/pull/5903 it sounds like we don't want that. I sent https://github.com/vitejs/vite/pull/5927 as an improved fix. If people are able to take a look, I think it'd be nice to get into 2.7


Updated the default filtering on Compliance check page and Compare page

Description
The default filtering is now excluding the "unmodified" resources.
https://github.com/inmanta/web-console/assets/44098050/3a29f893-fd09-469b-af91-882092319bcd

Processing this pull request


Design: Moving in and out of enemy vision range after encountering enemy allows re-rolling combat initiative

When seeing an enemy on the periphery of vision, the player can move out of sight before the enemy would otherwise start pathing towards the player. This allows the player to essentially re-roll for combat initiative to get the first strike by darting in and out of vision range if engaging in combat would not be optimal.
Opening this issue just to track discussions for any actions to take, if any are to be taken.

I feel like if your suggestion for new monster attack mechanics works out, this might be solved too. https://github.com/ASteinheiser/react-rpg.com/issues/21

@all-contributors please add @Alphanumber and @ASteinheiser for ideas

Closing to consolidate conversation in #21


Revert "tests: no need long busy_wait to waste cycles"

This reverts commit 315cba1c40fcd53881ec5c4bbaed0da79892c554 as it was
causing CI failures for qemu_cortex_m0.
Signed-off-by: Kumar Gala<EMAIL_ADDRESS>

What's failing? The PR that included this passed CI.

What's failing? The PR that included this passed CI.

not sure why, but qemu_cortex_m0 fails.

Looks like the test relies on that busy wait crossing a tick boundary to be sure a timer fired.   If DURATION is very small, it's plausible this might not be long enough on 100 Hz systems.  But someone should get in there and root cause this before reverting, because otherwise the enhancement will be lost (IIRC the root cause of the original ARC bug is getting fixed separately in the timer driver).

I can also confirm this failure:
[0/1] To exit from QEMU enter: 'CTRL+a, x'[QEMU] CPU: cortex-m0
*** Booting Zephyr OS build zephyr-v2.2.0-2055-gaef3cfc332de  ***
Running test suite interrupt_feature
===================================================================
starting test - test_isr_dynamic
installing dynamic ISR for IRQ 1
PASS - test_isr_dynamic
===================================================================
starting test - test_nested_isr
Triggering irq : 25
isr0: Enter
Triggering irq : 24
isr1: Enter
isr1: Leave
isr0: Leave
PASS - test_nested_isr
===================================================================
starting test - test_prevent_interruption
locking interrupts
unlocking interrupts

    Assertion failed at ../src/prevent_irq.c:58: test_prevent_itimer fired
nterruption: (handler_result not equal to HANDLER_TOKEN)
timer should have fired
FAIL - test_prevent_interruption
===================================================================
Test suite interrupt_feature failed.
===================================================================
PROJECT EXECUTION FAILED


[bug 1141056] Fix history in onpopstate

When onpopstate kicks off, we were changing the page, but also tweaking
the history. We don't need to do that last bit since the event only
fires on history changing.
Quick r?

gah! r+ when travis goes :green_heart:

6352e56 [bug 1141056] Fix history in onpopstate
Thank you!


NewValidation: Malformed hpaths leading to FEX's

(use upvote :thumbsup: for attentions)
Validation Type
[ ] - Fault
[ ] - Config
[X ] - Bug
[ ] - Other
What needs to be validated
[CSCwh68103] This bug is caused by malformed hpaths leading to FEX's. For example: uni/infra/hpaths-202_eth122_1_22/rsHPathAtt-[topology/pod-1/paths-202/pathep-[eth122/1/22]] Is malformed and should be in the format of: uni/infra/hpaths-202_eth122_1_22/rsHPathAtt-[topology/pod-1/paths-202/extpaths-122/pathep-[eth1/22]]
Why it needs to be validated
These malformed hpaths are usually asymptomatic until an upgrade of the ACI fabric occurs, at which point the customer becomes locked out of making any changes to the ACI fabric.
Additional context
moquery -c infraRsHPathAtt | grep ^dn       <<<This command will show both clean and malformed hpaths.

Same as issue #88


Can't expand World Border

Describe the bug: I've set the border with /wb world set 10000. I now want it to be /wb world set 20000. The console says it changed, but it didnt change  in the game. Bypass also doesnt work. I've tried to clear it, also nothing. I've tried to make it smaller, nothing. I've deleted it completely, nothing. I really don't know what to do anymore, I'm beat...
Server Version: Paper 1.16.4
Plugin Version: 2.1.0
Plugins: EssentialsX, ChatEx, WorldEdit, WorldGuard, LuckPerms, CoreProtect, Vault, AmkMcAuth, BlockLocker, Harbor, SkinsRestorer, WorldBorder

Fixed it by using the /worldborder command instead of /wb. Possibly something was overriding it, IDK. Support helped on discord. Many thanks!

Fixed it by using the /worldborder command instead of /wb. Possibly something was overriding it, IDK. Support helped on discord. Many thanks!

I'm having the same issue, but using /worldborder:wb or /worldborder:wborder is doing nothing, a specific /worldborder command doesnt even seem to exist. I'm unable to clear the border at all.


added fixed search bar, closes #76

Fixes #76
Description
Wrapped search and filter elements in a container, and made it stick to top while scolling by using sticky property. Additionally, also handled the transparent background issue, and stacking issue.
Other information

Wrapped section-search and section-filter in a single div, since both need to stick to top after scrolling.
Used sticky CSS value for position attribute to get the effect of sticking to top after scrolling.
sticky compatibility for various browsers
Added an extra class of - container-search-filter which has these properties - sticky, top, and z-index.
Also, needed to adjust the background colour, since it is transparent as nothing is mentioned, so had to add background: transparent to each parent from container-search-filter upto body

Screenshots
Initial level -

After scrolling -

Checklist:

[x] My pull request has a descriptive title (not a vague title like Update index.md).
[x] My pull request targets the master branch of the repository.
[x] My commit messages follow best practices.
[ ] I added tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no
visible errors.

Developer Certificate of Origin
Version 1.1
Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129
Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.

@nilshah98 I have created an issue #78 where I have discussed the issue #77 and proposed a different solution.
The problems with fixing the search bar to the top of the viewport are:

It does not look good (especially in light mode) because it's a huge size and the whitespace below the search bar.

The whitespace will increase in the future as we add more filters.

It is distracting and decreases the size of the viewport.

If we want to improve this, we have to design a different search bar with a small size and a transparent feel that would be look good when fixed at the top. Also, have to solve the issue of filters. It would be an overkill.
You can go through that issue and share any feedback. You can also tell if you would like to work on it.

Thanks for the feedback.
I see that there is a PR open for the issue related to filter space, once that is resolved, either accepted or rejected, I would like to propose a new solution where in-

The search bar is stuck at top while scrolling.
Filter spacing is 0, unless filter is activated.

I have doubts about working with transparent search bar, I tried it and it did not look good, but that's an issue for later, I suppose.
Thanks again.


Some styles from editor-widget.ini don't do anything for JavaScript.

Ref : https://github.com/slap-editor/editor-widget/blob/1ceaf95cd044bdf90e28fc3aee0f7aa67a2b6b10/editor-widget.ini#L130-L173
First of all thanks for a wonderful console editor.
I only just discovered it from this page : https://github.com/showcases/text-editors
I copied the style lines from editor-widget.ini to ~/.slap/config.  Then changed some styles.
But styles like operator = "{green-fg}" and variable = "{yellow-fg}" don't seem to have any influence whatsoever (only tested with JavaScript code). Even before changing them. While other styles do,
And adding a foreground colour to function = "", for example {light-green-fg}, changes the text colour of the complete line the function name is on. Including the keyword function, which had a red colour because of the style keyword = "{red-fg}". And the text colour of the function parameters also turns green from white (although it's styled with params = "{bold}").
What am I doing wrong? Or maybe what's going on?
And why can't we use styles from /opt/node/lib/node_modules/slap/node_modules/highlight.js/styles?

@BobbyBabes I'm glad you are enjoying the editor! One of the main reasons I wrote the editor in JS is so you can see exactly how the code works without having to learn a more complicated language or framework. I see you were able to find those styles in the source code. Here is how they are detected with highlight.js: https://github.com/slap-editor/editor-widget/blob/b8f3cf67b84b74bf4b0f5f481f82d27e05031bbe/lib/highlight/server.js#L41
In essence, the styles are language specific, as discovered by highlight.js. Changing operator or variable will change those styles for one language but may not change it for another. Initially, I tested various files and found those styles from highlight.js' output, so I added them to the file, but they may not apply anymore as highlight.js has been updated since then. Does that help?

Thanks for the pointer to how styles are detected by highlight.js.
I assumed that the styles were aware of multiple languages (not necessarily all though). But at least JavaScript. This was wrong of course.
I'll look further into the style detection. I might be able to find a better suited style, or change things to my liking.
Thanks for your explanation. I'm OK.


Added ValidableQuestion

With ValidableQuestion you can do things like:
$question = new ValidableQuestion("Give me something: ", ["required"]);

or
$question = new ValidableQuestion("Give me a number: ", ["numeric"]);

I needed to exctract this out and now I share it here. It's just an idea of a functionality that I had to extend into this amazing package. Hope it helps.
Thanks :)

This is a read only repository.
Pull Request should be send to https://github.com/symfony/symfony.
After the merge in the main repository, a sub-tree of split is done and this repository is updated.

Closing as someone already mentioned, we try to avoid having more than one way to do something.


Question: is there any way to keep every html entities as-is?

Consider the following markdown:
stuff Á stuff

The HtmlRenderer returns:
stuff Á stuff

If I use \Á it returns:
stuff &Aacute; stuff

Is there any config to make it return as below?
stuff Á stuff

In other words, don't change any HTML Entity at all?

@acdcjunior, I added an option to get this effect. Release in a minute.

add  HtmlRenderer.UNESCAPE_HTML_ENTITIES, default true. Set to false to leave HTML entities  as is in the rendered HTML.

@acdcjunior, repo updated. Maven updated, may take the usual maven delay to update indices.

@acdcjunior, maven central updated. Let me know if you need more information to get it working for your project.

Awesome, I got it working and it is beautiful, thanks a lot!
Now, since we're at it and you are such a nice guy, as payback, here goes a suggestion (no need to reply to this, just take it into consideration):
I have an app that used marked (js) as md->html engine. Earlier today I decided I'd better use a java-based one. Googled it a bit, found pegdown.
But their readme said the project was deprecated and recommended flexmark-java; that's how I came to know your tool.
Now to the problem/suggestion: when evaluating a tool, we usually don't read stuff, the first thing we want is a running example.
I googled for a sample of flexmark-java and found https://github.com/vsch/flexmark-java-sample. Nice, but... actually, that project is a bit frustrating. Though I'm an IntelliJ user, I still expected the project to be a maven (or gradle) one, not a "raw" IntelliJ module.
The referenced libs are 0.4.17 (so old, I noticed later...) and the Main class has a ton of "detailed" stuff (aka unecessary/too much for me at that moment). Now, of course, when you wrote that class your goal was probably not for it to be a "hello world" class, but bear with me, I'm trying to show you how it felt for me at that point.
The good news is I eventually managed to get it working. What actually helped me a lot was this HtmlRendererTest unit test class I stumbled upon. It uses the parser/renderer in a very simple manner (without any additional options) and was perfect for my needs at the moment.
As the day went on I even found your great wiki and its Usage page! When I saw it, I thought: that is what I needed in the first place.
So, cutting to the chase, my suggestion is: consider putting a running example as the first thing (or close to the top) of your readme. I reckon the code may take too much space, if you feel that way, place at least a link to the wiki page saying something link "For quick sample and usage examples, click here". I think it would benefit newcomers a lot.
So, that's it. Just a quick report. I hope you don't get it as criticism, because it is not at all, your tool is great and I got it working very quickly!
Anyhow, thanks again!! As said, no need to reply, this is just what I thought as a way of saying thank you for your kind feedback on this issue! :) cheers!!

@acdcjunior, all suggestions are greatly appreciated. Especially ones from first time users.
I am still surprised by how little feedback I get from users about their experience and what would help them get started. I keep adding their suggestions as they come in.
I will add a simple working sample at the top of the read me file with links to the Wiki in bold so  first time users cannot miss it. I don't think that a basic sample will take too much space. I will add instructions on flexmark-all dependency which will add all core and extensions so there is no need to fiddle with individual modules to reduce start up complexity. Setting up a working project should be simple in any environment.


elf2uf2-rs: Init at 91ae98873ed01971ab1543b98266a5ad2ec09210

Motivation for this change
This tool converts ELF files to UF2 files. Some micro-controllers (e.g. RPi 2040 which is on the RPi pico) use this for firmware upgrades.
Upstream has no release yet unfortunately. Hence, setting version to latest commit.
Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

All fixed, many thanks for the review!


New test for CASSANDRA-12909

A new test for CASSANDRA-12909.

+1

I just pushed a new commit that extends the tests a bit. I've added more CQL types to the partition key, they are all text related as far as the copy conversion is concerned. I've also added a new test that uses a non-counter table, where we only test non-prepared statements without counters, given that the execution paths are separate.

Still looks great, +1


MDK Compilation Errors

Hey,
I noticed when compiling an MDK for the latest version of fortnite, using the fortnite branch, there are several compilation errors in the merged_UI_UIKit.h header.
MDK/merged_UI_UIKit.h(1562,38): error : expected class name
MDK/merged_UI_UIKit.h(1662,38): error : expected class name
It appears that the classes are being defined in the wrong order, with dependencies being below dependents.
I can upload the MDK dump in question if needed, it should be easily reproducible with the current Fortnite branch on Fortnite v27.10 though
Thank you! :)

hey there, thanks for the report. Would you be able to upload the MDK/post pictures of it? Are you sure it's the MDK itself and not any code you added?

Absolutely, here is the relevant MDK and SaveState files.
The only change I made to MDK before compilation was to move all classes into a separate namespace for organization.
Fortnite-v27.10.zip
SaveState.zip

ive looked into it and it was an issue on my side. I pushed a fix:
https://github.com/Spuckwaffel/UEDumper/commit/58b25611fd67ccb4f862524ef500be494b06a9a0
apparently my loop never executed twice or more for the struct reordering, because i forgot to set a bool to true 🤡
I tested it and it compiles now without an issue.

im really surprised this issue never happened before/in testing as i really thought multiple iterations of struct reordering are necessary.

Glad to see it was a simple fix :)


Updating supported OS

Updating supported OS.
Signed-off-by: Davis Benny<EMAIL_ADDRESS>

where are we calling out Debian?

Adding support for Debian.


Messaging and search features and some minor fixes

Dear @kirbiyik ,
I create some new feature including messaging mechanism and search for users and events. On the other hand, we have to decide where we put search buttons in the pages.
I am waiting your review as soon as possible.

@atifemreyuksel Next time it could be better if we can create seperate branches for distinct features 👍


[LOCAL ONLY] Add passwordless login

This PR adds the ability to log in without a password on local installations only. It also implements a new global object config which - at the time of this PR - contains only the NODE_ENV (in property environment) and JWT token encoding secret key (in property secret).
This PR resolves #269.

@AlexeySachkov do you have any idea why this PR will only pass testing if the timeout of the first test is increased to more than 5s? It looks like it completed in just under 12s (https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery/701/workflows/fde4f457-e058-48c5-8186-060061d9eca5/jobs/700)
I tried splitting out the test stage from the build stage (see https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery?branch=experimental-CI_update) but even so, the first of the route tests takes about 5 or 6s to complete, while the rest complete in literally milliseconds.
Any thoughts? Is this related to the PR at all, or is this generalized testing weirdness???

@AlexeySachkov do you have any idea why this PR will only pass testing if the timeout of the first test is increased to more than 5s? It looks like it completed in just under 12s (https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery/701/workflows/fde4f457-e058-48c5-8186-060061d9eca5/jobs/700)
I tried splitting out the test stage from the build stage (see https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery?branch=experimental-CI_update) but even so, the first of the route tests takes about 5 or 6s to complete, while the rest complete in literally milliseconds.
Any thoughts? Is this related to the PR at all, or is this generalized testing weirdness???

I think it is generalized testing weirdness which has little to do with your PR, see #1982. It seems like tests takes forever to be initialized/set up and I don't know the exact reason for that. One of the reasons could be that modules loading is slow under jest, but I really doubt that your changes caused 2x slowdown - CI machine is likely a non-physical machine, which means that its performance could be unstable as well.
I think it should be ok to increase the timeout, but I suggest we do that globally through jest config in package.json:
https://github.com/naturalcrit/homebrewery/blob/c9935fa45ccc502ec0e454ee090471a9c88be2aa/package.json#L33-L39

@AlexeySachkov do you have any idea why this PR will only pass testing if the timeout of the first test is increased to more than 5s? It looks like it completed in just under 12s (https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery/701/workflows/fde4f457-e058-48c5-8186-060061d9eca5/jobs/700)
I tried splitting out the test stage from the build stage (see https://app.circleci.com/pipelines/github/G-Ambatte/homebrewery?branch=experimental-CI_update) but even so, the first of the route tests takes about 5 or 6s to complete, while the rest complete in literally milliseconds.
Any thoughts? Is this related to the PR at all, or is this generalized testing weirdness???

I think it is generalized testing weirdness which has little to do with your PR, see #1982. It seems like tests takes forever to be initialized/set up and I don't know the exact reason for that. One of the reasons could be that modules loading is slow under jest, but I really doubt that your changes caused 2x slowdown - CI machine is likely a non-physical machine, which means that its performance could be unstable as well.
I think it should be ok to increase the timeout, but I suggest we do that globally through jest config in package.json:
https://github.com/naturalcrit/homebrewery/blob/c9935fa45ccc502ec0e454ee090471a9c88be2aa/package.json#L33-L39

Cool, I'll put it into a separate PR, probably tomorrow at this stage

I have removed the test timeout changes from this PR and raised #2094 to apply the timeout change globally as suggested. However, as the test still takes >5s to complete, it is now failing again. I am extremely confident that this PR will pass the tests once #2094 is merged.

Nice.... This is looking pretty good. As @jeddai said, we can look later at getting Google drive integration but that can be a separate PR. I think this is ready to merge?

I think we're good!
This one has been a bit of a journey, not least because it's in the top five oldest open issues.


Create a way to test nightly locally, or as part of a PR that fixes nightly

Right now, if we get a PR that fixes an issue for the nightly tests, the only way to test it is to approve the PR and merge it, and see what happens as a result of the merge.
We should figure out a way that we can run the nightly tests on demand, either locally, or by doing something in the PR that signals that the nightly tests should be run as part of the PR.
Maybe @twoertwein has an idea here.

@twoertwein I looked into it and why you were having troubles creating that.
Here is what happened:

The workflows you see in the Actions tabs are the ones that gets triggered when you push to the branch.
When you use a comment, you actually use a different trigger (the on section of the yaml workflow).
So even if you commented and it actually triggered the workflow you were hoping for, it would not display in the Checks tab of the PR.

Here is a workaround that we could use (I actually tried it out, PR on my own repo is below since you need to have the workflow file on main branch to have it applied in a PR):

You create a comment command like @twoertwein you did on your PR.
The Action will get triggered and run.
Once the Action is complete you actually create a check run (https://docs.github.com/en/rest/checks/runs?apiVersion=2022-11-28) where you will list if your test ran without error or not.
From there, this will be displayed a little differently than a typical Actions but you will still get most of the information:

We can decide what we want to add in the messages there.

Of course the content of the message will be a little different than if we were using a more standard Actions that is triggered on push but that is a good workaround not to have to run the nightly checks on merge to main branch (mostly to save CI credits and have the status check appearing in green).
PR I used is there https://github.com/loicdiridollou/pandas-stubs/pull/2, feel free to trigger the workflow with /nightly, I have not implemented the other commands yet but wanted to get a good proof-of-concept to share first and discuss if this is a route that you would like to take.
Please let me know what you think and I can spend a little bit more time working on improvements/changes.

Great, thank you @loicdiridollou for figuring it out!
Feel free to open a PR!


Some entities are not displayed after starting Inverter

Version of the custom_component
0.0.26

Configuration
No entry in configuration.yaml, configuration through UI

Describe the bug
Some entities are not read out after inverter start in the morning. As can be seen in the picture, the data from the MPPT1 is missing. The rest is displayed.

When I restart the integration, it works again immediately.
Debug log

2024-08-26 05:59:38.966 WARNING (MainThread) [custom_components.sunspec] Inverter not active on <IP_ADDRESS>:502
2024-08-26 06:01:02.027 WARNING (MainThread) [custom_components.sunspec] Inverter not active on <IP_ADDRESS>:502
2024-08-26 06:02:24.220 WARNING (MainThread) [custom_components.sunspec] Inverter not active on <IP_ADDRESS>:502
2024-08-26 07:30:55.740 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data coordinator update
2024-08-26 07:30:55.740 DEBUG (MainThread) [custom_components.sunspec] Fetching models
2024-08-26 07:30:55.745 DEBUG (MainThread) [custom_components.sunspec] SunSpec Update data got models {160, 113}
2024-08-26 07:30:55.746 DEBUG (MainThread) [custom_components.sunspec] Get data for model 160

after multiple restarts of both inverter and home assistant I was able to get most of them back but the DC values are still missing compared to version 0.0.25


Styling: inline switch

By default the whole switch is filling my whole table cell and its centered. How would I make it inline and align to the left? The default styling seems kind of strange to me.

Try styling it like so
.x-toggle-component {
    justify-content: flex-start !important;
}

Open to suggestions for better defaults.


Support Transkribus

It should be possible to test Transkribus in this framework.

After spending some time training a Transkribus model and running it, I think now this is going to be difficult to support in Handprint. It would require changing how Handprint interacts with the user, which is probably more work than is worth right now for our purposes.

Deleted milestone 1.4.


MINOR: Bump 2.7 to use 2.7.2

Committer Checklist (excluded from commit message)

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

@mjsax @vvcephei Can you upload kafka-stream-2.7.2-test.jar to the kafka-packages S3 bucket? Thanks

@mimaison I have uploaded kafka-streams-2.7.2-test.jar, kafka_2.12-2.7.2.tgz, and kafka_2.13-2.7.2.tgz to s3://kafka-packages.


minor fix in my_application.h file

In the "packages/flutter_tools/templates/app_shared/linux.tmpl/my_application.h" file, a semicolon was missing on line 6, So it was giving error in the template code, I have fixed that issue. Now it is working fine.
The Semicolon was missing in line 6 in my_application.h file, I have fixed that issue.
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

@cbracken Do you know who might be able to review this?

Going to close for now as working as intended, but if you do find there's a case where this is causing a compile error, please let us know and we can re-open.


Honda: cleanup brake press detection

openpilot considers two extra conditions for brake pressed that panda doesn't.

[ ] determine if brake_switch is necessary, and if it is, do we need two samples?
Going back to the one history, this was done to prevent a mismatch between openpilot and the Honda PCM. Do we need this at all? Is the noise real? What signal does the PCM use?

[ ] remove the exception for the Ridgeline, Pilot, and Passport
#475 has the history for this one.

The PCM seems to use something different than us for brake presses. Perhaps it's using a different brake pressed signal or it simply has a threshold on the brake pedal position.

Responses: Honda PCM seems to disable on brake switch, after up to 50 frames on occasion. However the signal we were using (BRAKE_PRESSED on POWERTRAIN_DATA) also can lag for up to tens of frames after BRAKE_SWITCH. Leading to instances where a cruiseDisabled alert was thrown on brake disengagement as the PCM disengaged before openpilot even saw the brake pressed state.
We need to or/|| the two signals, as BRAKE_SWITCH is never 1 when in park, and in other rare circumstances (like near very end of drive, at standstill). We also need to make sure we see BRAKE_SWITCH twice from the car, as sometimes it rises to 1 for a single frame without any real user brake press.


Generate a single report from multiple JSON files

I see two options here.

Merge the JSON files into one long report
Add some kind of tabbed display to show the different reports on one screen

Option 1 is the simpler choice as it only requires merging of data and minimal (if any) updates to the report itself.
Option 2 requires bigger changes to the report components to support tabs and raises questions.

Would there be a max number of tabs allowed?

How about on smaller screens?
Are the tabs ordered?
What does the design look like?

There is a package now available for this called mochawesome-merge. I was using seperate scripts I had created but now reverted to using this.
Also created a package called mochawesome-slack-reporter to send the test report status and artefacts to slack 🤙

No update. Unfortunately I just don't have time to maintain this project let alone work on new features.


GH-15054: [Python] Finalize S3 on pytest exit to prevent shutdown crashes

For some reason destroying an S3Client at shutdown can cause a crash in our tests.  It appears to be because S3's logging is already shut down.  I wouldn't think this would happen because I would think the linker would tear down S3 shared libraries AFTER it tears down Arrow shared libraries.
However, we can also finalize S3 in conftest.py to prevent this crash.
It would still be good to understand the root cause.  Otherwise we need to advise our users to call finalize_s3.

Closes: #15054

because I would think the linker would tear down S3 shared libraries AFTER it tears down Arrow shared libraries.

In a wheel though, we statically link everything, and then destruction order is undefined as usual?

In a wheel though, we statically link everything, and then destruction order is undefined as usual?

Yes, I think that could explain it.  Still, this fix would require pyarrow users to know about and remember calling the finalize S3 method.  I'm going to pause this idea and make an attempt at an arrow::Shutdown.

Closing in favor of #33858


Switch name order to First name -> Surname

I dislike the transposition of surnames and given names in your transcriptions, and the forcing of surnames to uppercase. I would prefer the names to be transcribed exactly as they are written in the original records.

The results are presented forename/ surname. We have always presented Surnames in Capitals to distinguish then from Forenames. There are many case where only one part of the name is present. Capitalization makes it clear which name part is being displayed


Rider/Driver submissions from form fails if some non-required boxes are not checked.

For Example:
rider row insert failed: null value in column "TwoWayTripNeeded" violates not-null constraint.
What should happen:
The backend node app should check for existence / provide default (false/0) values for the data elements which are being inserted.
Those include:
DrivingOnBehalfOfOrganization (default false)
WheelchairCount (default 0)
NonWheelchairCount (default 0)
TwoWayTripNeeded (default false)
DriverEmailValidated (default 0/false?, until validated by confirming/responding to Email.)
DriverPhoneValidated (default 0/false, until validated by confirming/responding to Text.)
ReadyToMatch (default 0)
PleaseStayInTouch (default 0)

@misteranderson are we sure these defaults are valid? That's part of the reason I don't sanitise data received from the client.
How is it possible for the client not to send these values? I'm concerned about the situation where driver/rider enters details and these are not sent, and the defaults are incorrect.
A failure is inconvenient, but better than a result that reports success but is in reality wrongly stored

Well, the results don't actually get inserted into the staging table (so we're not reporting success and storing incorrect values), but the error message is not helpful to the user - if they don't need a two-way ride, and therefore haven't checked the box,, then the form isn't sending that field.

there were some xhtml syntax errors that caused the form to not submit some fields especially some checkboxes. If this is still happening, it may be because old code was re-introduced with the same bug.
In short, always close the xml tags <input ... />  and the value=xxx should not be present.
The form normally always sends true/false value for all checkboxes, whether checked or not

It doesn't seem to be the xhtml this time.
If it isn't resolved by the front-end team I'll apply defaults in the node app for short term purposes

Just put in a PR to fix this issue.

I think we can close this issue now

agreed


AuthComponent is hardcoded

Reported by euromark | January 25th, 2011 @ 07:46 AM
The AuthComponent is hard-coded
I use AuthExt for example...
I propose either
a) omit Auth and use Session ($this->Session->read('Auth.User.id')
b) use configs to allow other Auths
Additionally, the code below fixes another problem: Nonsense-Error-Message for not logged in users
Right now they would get "You already voted" which they obviously didnt^^
I added
$message = __d('ratings', 'Not logged in', true);

in this case. It will abort right away (no need to do anything more) with the correct feedback.
public function startup(&$controller) {
    $message = '';
    $rating = null;
    $params = $controller->params['named'];
    if (empty($params['rating']) && !empty($controller->data[$controller->modelClass]['rating'])) {
        $params['rating'] = $controller->data[$controller->modelClass]['rating'];
    }
    if (!method_exists($controller, 'rate')) {
        if (isset($params['rate']) && isset($params['rating']) && $this->enabled == true) {
            # mod - 2011-01-24 ms
            $uid = $this->Session->read('Auth.User.id');
            $this->rate($params['rate'], $params['rating'], $uid, !empty($params['redirect']));
        }
    }
}

/* * Adds as user rating for a model record * * @param string $rate the model record id * @param string $rating * @param mixed $redirect boolean to redirect to same url or string or array to use it for Router::url() /

public function rate($rate, $rating, $user, $redirect = false) {
    $controller = $this->controller;
    $controller->{$this->modelName}->id = $rate;
    # mod - 2011-01-24 ms
    if (!$user) {
        $message = __d('ratings', 'Not logged in', true);
        $status = 'error';
    } elseif ($controller->{$this->modelName}->exists(true)) {
        if ($controller->{$this->modelName}->saveRating($rate, $user, $rating)) {
            $rating = round($controller->{$this->modelName}->newRating);
            $message = __d('ratings', 'Your rate was successfull.', true);
            $status = 'success';
        } else {
            $message = __d('ratings', 'You have already rated.', true);
            $status = 'error';
        }
    } else {
        $message = __d('ratings', 'Invalid rate.', true);
        $status = 'error';
    }
    $result = compact('status', 'message', 'rating');
    $this->controller->set($result);
    if (!empty($redirect)) {
        if (is_bool($redirect)) {
            $this->redirect($this->buildUrl());
        } else {
            $this->redirect($redirect);
        }
    } else {
        return $result;
    }
}

The most easy solution that we also use for this is simply $this->Auth = $this->CustomAuth; It's better to do it this way than using a different name because even if we would make it configurable every developer might do this differently. The solution I suggest you here is the most simple one and also follows convention over configuration. Enjoy :)


[FEATURE] Add OpenSearch-Java transport as an option

Is your feature request related to a problem?
Currently the hadoop client uses it’s own custom RestClient to make requests to an OpenSearch cluster. While this works today, we’d like to allow users to choose between that and an optional ApacheHttpClient5Transport that’s present in the OpenSearch-Java client. To do this, we would need to add a new transport option and import the java client into hadoop.
Adding the OpenSearch-Java transport as an option allows us to build on top of the upstream client and allows us to and new features like backpressure awareness and others described in https://github.com/opensearch-project/opensearch-clients/issues/27
What solution would you like?
This diagram illustrates how the java client and hadoop client make requests to OpenSearch today:

The hadoop client just translates incoming queries into a SimpleHTTP request and uses the URL, path, queryparameter, method, and headers to construct the request. OpenSearch-Java on the other hand makes use of a Request/Response builder pattern and exposes those methods to the client.
Approach 1
One approach would be to add a new abstraction layer in OpenSearch-Java that would abstract away the GET/POST/PUT/DELETE methods. The hadoop client can just use the appropriate class, construct the request and let the java client handle everything else. This is also an ask here — https://github.com/opensearch-project/opensearch-java/issues/377

Pros:

Would make it easier in the hadoop client to leverage OpenSearch-Java without having to explicitly parse the Request and Response classes
Would let people use the client as is for exisiting APIs and allow them to hit other OpenSearch endpoints that are not supported in the client today, e.g. calling plugin APIs

Cons:

Providing an easy REST layer can shadow the other client endpoints and cause developers to stop using them the right way adding maintenance overhead and potentially going against good design patterns?

Approach 2
Parse the incoming request at the hadoop layer and use the appropriate OpenSearch-Java request and response class to send the request.
Implementation questions:

what’s a good design pattern for this?

Example design pattern:
public class JavaClientTransport {

    public void executeRequest(Request.Method method, CharSequence uri, CharSequence path, CharSequence params, ByteSequence body, String operationType) throws Exception {
        RestClientBuilder builder = RestClient.builder(new HttpHost("endpoint", 9200, "protocol"));
        RestClient restClient = builder.build();

        // Create Client
        OpenSearchTransport transport = new RestClientTransport(restClient, new JacksonJsonpMapper());
        OpenSearchClient client = new OpenSearchClient(transport);
        switch(operationType) {
            case "bulk":
                // build the request right here, looks like we have all the information needed, it might need to be converted to specific format that fits with the BulkRequest
                BulkRequest bulkRequest = new BulkRequest.Builder().index("index").build();
                BulkResponse bulkResponse = client.bulk(bulkRequest);
            case "search":
                SearchRequest searchRequest = new SearchRequest.Builder().index(Arrays.asList("index")).build();
                SearchResponse searchResponse = client.search(searchRequest, null);
            default:
                throw new Exception("No matching path found");
        }
    }
}

how would we convert the Bytesequence that hadoop uses for the body into either JSON or a body class?

Potential example to convert ByteSequence to String
 ByteArrayOutputStream result = new ByteArrayOutputStream();
 byte[] buffer = new byte[1024];
 for (int length; (length = inputStream.read(buffer)) != -1; ) {
     result.write(buffer, 0, length);
 }
 return result.toString("UTF-8");

Potential example to convert Json string to required JsonData that .document() from the Java Client accepts.
JsonpMapper mapper = client._transport().jsonpMapper();
JsonParser parser = mapper.jsonProvider().createParser(new StringReader(jsonString));
JsonData data = JsonData.from(parser, mapper);

A bigger question is, what have I missed in the implementation of the Java client and the hadoop client that would require a third approach?
Do you have any additional context?
This is also a feature request in https://github.com/opensearch-project/spring-data-opensearch/issues/19 and can help consolidate the approaches.

I'll dig deeper but my initial reaction would be to refactor the java client transport as a core library so we take the dependency on opensearch-core and a new opensearch-transport library instead of a cross plugin dependency.

I think opensearch-java needs the ability and expose doing pure HTTP requests to avoid being a bottlebeck, and all the implementations of actual strongly typed methods should use those. For this client, taking a dependency on opensearch-java seems like the right call.

@harshavamsi what is preventing us to opensearch-java as intended, using typed request and response models?

What were you think about doing in https://github.com/opensearch-project/spring-data-opensearch/issues/19? Were you going to pull in the request/response types from opensearch-java?

Yes, the plan going forward is to recommend opensearch-java as the only official client to communicate with OpenSearch, I think we formalized it here [1]
[1] https://github.com/opensearch-project/OpenSearch/issues/5424


Input is required filed, and the input blur will not show errors until the onsubmit event is triggered.

Versions

vee-validate: 2.0.0-rc.25
vue: 2.5.2

input is required filed, and the input blur will not show errors before the onsubmit event is triggered.

Please use the latest version if possible since a lot of bugs are being actively fixed in new releases. Also if the problem persists in the newest version, it would be helpful if you can create an example for it. Will re-open once you do.


Enable lazy certificates for Elasticsearch

The latest versions of Elasticsearch (8.x) come with security enabled.
The somewhat older versions (which are still in use) can have security enabled.
It is handy for people to be able to enable security in their tests also for version 7.x as one of the required steps. This way they can start using the clients in the way that is going to work with 8.x as well.
The proposed changes basically postpone fetching the certificate until the client is created, instead of doing that as part of the container spin-up procedure.

Hi!
One thing I'm not sure of is what to do with:
protected void containerIsStarted(InspectContainerResponse containerInfo) {}
Shall the removal of it be allow-listed, or shall it be kept (e.g. with a comment), despite being empty?

Thanks for your contribution, @pioorg !