Use hostname es website title

Because I have now two boxes (lottibox and marcobox) I need to see on which box I am. So best is to use hostname of the PI as title.

Why it showes me the old commits? I thought only c2b623d will be commited. What I'm doing wrong? @MiczFlor

Another thing, you suggested somewhere sometime to change the systemd servies to the phoniebox namespace. I did. Please have a look here and tell me if this is what you had in mind:
https://github.com/MiczFlor/RPi-Jukebox-RFID/commit/55bc7492b030702d440ed99c423ceb24c032fca7

btw. @MiczFlor maybe you can explain me how I can contribute without generating any mess? I bought an extra Pi for myself and making development on my box so I have not to grab the box of my daughter every evening. ;-)

Hi @marcohorstmann
sorry for the silence, I was away over the weekend. Best thing to do would be to install the develop branch version, switch to the develop branch and keep changing and contributing there. If you have a dedicated dev hardware: awesome :)
How would you do that?
If you already have the system installed, try this:
cd /home/pi/RPi-Jukebox-RFID
git checkout develop
git fetch origin
git reset --hard origin/develop
git pull

If you have an empty SD card with only stretch on it, best to install from scratch with the one line install script from the develop branch
without spotify:
cd; rm stretch-install-*; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/develop/scripts/installscripts/stretch-install-default.sh; chmod +x stretch-install-default.sh; ./stretch-install-default.sh

with spotify:
cd; rm stretch-install-*; wget https://raw.githubusercontent.com/MiczFlor/RPi-Jukebox-RFID/develop/scripts/installscripts/stretch-install-spotify.sh

And then go to the dev branch :
cd /home/pi/RPi-Jukebox-RFID
git checkout develop
git fetch origin
git reset --hard origin/develop
git pull

You can check the branch you are on with
git branch

Hope this helps :)

@marcohorstmann
ich mach das hier jetzt mal zu, denn ich merge den ganzen Spotify Code aus develop auf master. Dein eÄnderungen müsstest du dann auf develop noch mal einbauen. Danke


[Proposal] FutureBuilder: better distinguish between UI logic and business logic

Hi there,
this proposal is a consequence of the discussion on another thread, a FutureBuilder rework proposal, #87399, in which we discussed how FutureBuilder should be reworked (with some breaking changes).
TLDR: FutureBuilder actual implementation forces the user to mix business logic and UI logic. Introducing a new business logic callback property listen, along with onError and onPending builder methods bring better clarity to FutureBuilder usage, allowing us to distinguish between Business Logic and UI Logic. This also solves #16218.
Use case
As of when I'm writing this, FutureBuilder<T> has only one builder method, that accepts an AsyncSnapshot<T> and allows to react to different state of the snapshot. Unluckily, this means to have mixed business logic and UI logic in the same method.
Proposal
FutureBuilder should have a listen callback, that reacts to the snapshot 's events. Furthermore, this class should have three different builder properties, each for one of the future's state, i.e. builder (when the snapshot is on a "done" state), onError (when something went wrong) and onPending (when the snapshot is not yet done).
Here's the use-case proposal described by @iapicca:
return FutureBuilder<String>(
      future: myFuture,
      child :  const Center(child: CircularProgressIndicator()); /// like in "ValueListenableBuilder"
      listen: (context, snapshot) {
        /// this is a VoidCallback
        /// maybe show a snackbar on error or stuff...
      },
      onPending: (context) {
          return child!;
      },
      builder: (context, snapshot) {
          return Center(child: Text(snapshot.data!));
      },
      onError: (context, error) {
          return const Center(child: Icon(Icons.error));
      },
    );

Note how this proposal is not breaking the current implementation, as the builder method still accepts a snapshot.
@pstromberg98 already offered an implementation on #87672.
We should address the possibility to deprecate the builder property and introduce a onComplete builder method for more clarity.

I made this package when starting flutter (this is unmaintained)

final future = Future.delayed(Duration(seconds: 2)).map((event) => true);
// ...

@override
Widget build(BuildContext context) {
  return FutureGuard<bool>(
    future: future,
    onData: (data) => HomePage('Future data received'),
    onLoad: () => LoadingPage(),
    onError: (e) => ErrorPage(),
  );
}


pass through jest command line config

Just now, running yarn test gave me this:
 › 1 obsolete snapshot found, run with `yarn test -- -u` to remove them.

Then, yarn test -- -u gave me this:
grommet check -u

  Invalid option: 'u'. Showing Help:

  Usage: check [options]

  Runs Javascript/SASS linters and execute tests for your project

  Options:

    --help          output usage information
    -j, --jslint    Whether to run only js lint.
    -s, --scsslint  Whether to run only scss lint.
    -t, --test      Whether to run only tests.

It would be great if jest's advice held true :)

Yeah you can now run grommet check and all options will be kept
grommet check -t -- --updateSnapshot‘ grommet check -t -- --watch‘
Hope it helps
Kr
Alan

On Jul 30, 2017, at 6:04 AM, rasenplanscher<EMAIL_ADDRESS>wrote:
Just now, running yarn test gave me this:
› 1 obsolete snapshot found, run with yarn test -- -u to remove them.
Then, yarn test -- -u gave me this:
grommet check -u
Invalid option: 'u'. Showing Help:
Usage: check [options]
Runs Javascript/SASS linters and execute tests for your project
Options:
--help          output usage information
-j, --jslint    Whether to run only js lint.
-s, --scsslint  Whether to run only scss lint.
-t, --test      Whether to run only tests.

It would be great if jest's advice held true :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thanks for the quick reply!
grommet check -t -- --updateSnapshot does do that, yes. So, I have several options to update the snapshots:

with grommet-cli installed globally, run grommet check -t -- --updateSnapshot
setup an npm script for that
change the test script to grommet check -- so that parameters to yarn test are used as extras for grommet

Unfortunately, grommet-cli seems to ignore -u as an extra parameter. Therefore, I'd need to use the long form. Consequently, the console output will still point me in the wrong direction, for each setup. That divide can be handled through documentation and such, but I really don't believe that's the most user-friendly way to go since each developer has cognitive overload from actively ignoring part of the console output.
Also, your mention of the watch parameter had me thinking, why not add -u and --watch? Possibly as first-order parameters 🤔  A lint watcher would be nice... What do you think?

Then again, we couldn't use Jest's watch mode while simultaneously running something else... Therefore, the watch mode would need to trigger jest as well per change...

we used to have -u only. But I guess it would be too much of an overhead to replicate and maintain all the other CLI parameters in our CLI. That's why I removed the -u in the 5.0 release.
In the past jest used to support both -u and -w as a shortcut to run things. It does not seem to be present in version 20 though. This just enforces the fact that it is cumbersome to replicate the attributes.
That said, I like your idea of having a few first-order parameters like watch and update. They can actually be reused in both eslint and jest.
grommet check -t -w => runs test in watch mode
grommet check -j -w => runs eslint in watch mode
grommet check -t -u => runs test and updates snapshots
grommet check -j -u => runs eslint with fix option so, if possible, lint issues will be automatically fixed
I will try to add support for that soon. Thanks for bringing this up.

@alansouzati did this get added to Jest?


My Language is not detected

My programming language is not displayed on Repo bar...
https://github.com/TheRealBastiaan/ShortMe

Problem is fixed


Straight forward implementation of TodoMVC using Aurelia?

Hi, I am an experienced javascript developer but very new and eager to learn javascript's new and modern frameworks like aurelia, angular, reactjs, etc....
The presence of the ObserverLocator thing in the sample implementation of the Todo app, apart from it being an 'internal' class according to the vague documentation, makes me wonder if this is the most simple possible implementation, or is there another, truelly straightforward way possible, just like Angular2?

Valid point actually. The main reason why I introduced this was #11 due to lack of Observable support in IE. I am not sure if the latest version of Aurelia or any polyfill might help nowadays to get rid of this workaround.
I'll see if I can update the sources and check an alternative approach again. Any PR is welcome as well.

Thank you, @mhoyer for your initial work, which helped send the message about Aurelia to many devs around the world. While it's been great as an example of an Aurelia application, the example itself needs some upgrade to properly reflect Aurelia application in real world, post beta period. I hope you don't mind if I ask the team at todomvc to use newer implementation at https://github.com/bigopon/todomvc/tree/master/examples/aurelia to demonstrate it. I made sure to properly credit you here
https://github.com/bigopon/todomvc/blob/f17016dd65f8627bca49d5bce95473a4a8466560/examples/aurelia/index.html#L64-L66 and the readme.
@ibrahimbensalah Please have a look at how it would look like if you use Aurelia today
https://github.com/bigopon/todomvc/blob/f17016dd65f8627bca49d5bce95473a4a8466560/examples/aurelia/index.html#L11-L85

@bigopon, oh please go ahead. I know that there were a lot of development in Aurelia since this example was created. Thus, an updated version of TodoMVC seems obvious.
Thank you for bringing this project further.


memory leak when using parser since 0.8.0

Hi,
Since version 0.8.0 we observe an increasing of heap memory usage when using yaml parser which is never released (so lead to a OutOfMemory quickly); do not happen in version 0.7.0 but still happen in version 0.11.0-M1
By analyzing quickly a heap dump when memory in high, it seems to be caused mainly by org.yaml.snakeyaml.nodes.{Mark,ScalarNode} instances
Regards,

Sorry it was since version 0.7.0; the 0.6.0 (and previous) is ok

I can confirm this issue.

Seems that the memory leak is in snakeyaml internals. I've just downgraded snakeyaml to 1.18 and circe-yaml seems to work like a charm - no sign of leakage.
@jblanckelkoo said that there was no leak in circe-yaml 0.6.0 - it was the last version with snakeyaml 1.18.

Seems that the memory leak is in snakeyaml internals. I've just downgraded snakeyaml to 1.17 and circe-yaml seems to work like a charm - no sign of leakage. I've also tried 1.18 but with no success.

this appears to have been fixed in circe-yaml 0.13.1, likely this change: #114. (We experienced the same memory leak and upgrading fixed it.)


Error when uploading via activeadmin

We are using activeadmin gem for the admin and have a regular file input. We are trying to upload a file of up to 10mb.
 I think it's not waiting for the file to be uploaded and it gives this error. Is there a reason why this would happen?
EDIT

This only happens on heroku when i try to do this on local it works perfectly.
I also tried to run the production env on local but it works there with passenger and activeadmin and the same code.

This is the activeadmin code:
form do |f|
    f.semantic_errors

    f.inputs do
      f.input :title
      f.input :download_file, as: :file, label: 'Download file'
    end

    f.actions
  end

Ok, so this isn't related to ActiveAdmin, the file command that Shrine uses to determine the MIME type of the file errors for some reason (Shrine uses the Open3 standard library to execute the file command).
Does this consistently happen on Heroku, for any type of file? This comment seems to lay out some cirtumstances where Errno::EPIPE might happen.

It seems that your Errno::PIPE happened when attempting to write the file content to stdin of the file command. From this and this it seems that this might happen if the file command finishes for some reason and isn't accepting any more input.
And it might not be that the file command didn't want to receive any input to begin with, but that it terminated at some point and didn't want to receive more input. I honestly have no clue what might have caused it. Maybe the file command in some cases determines the MIME type early from the content that it has got so far, and then decides not to take any more input. Maybe it's Heroku-related.

@Chocksy Could see what's the file --version on your local computer and Heroku? Maybe the version difference plays a role.
It would be great if you can share the file which causes the error on Heroku, and write a self-contained script which reproduces the bug, something in the lines of
require "open3"
require "open-uri"

file = open("http://example.com/path/to/file.zip")
Open3.capture3(*%W[file --mime-type --brief -], stdin_data: file.read(256*1024), binmode: true) # raises the Errno::EPIPE error

If I have that, I could try running it on Heroku myself and seeing what are the differences in environments. Without a file that reproduces the bug I'm afraid I won't be able to debug this.

@janko-m here is the file i'm trying to upload.
http://take.ms/wBtBa
I was not expecting this but it seems the error does raise on heroku when i run this:
require "open3"
require "open-uri"

file = open("https://www.dropbox.com/s/ojyt304txx9g3ls/cf9728c6bf5317e582fc5672c3c4ac8b.zip?dl=0")
Open3.capture3(*%W[file --mime-type --brief -], stdin_data: file.read(256*1024), binmode: true) # raises the Errno::EPIPE error

And i get this exception:
➜  app ✗ heroku run bundle exec rails runner ./test.rb -a app
Running bundle exec rails runner ./test.rb on ⬢ app... up, run.9799 (Free)
** [Raven] Raven 1.2.2 configured not to capture errors.
/app/vendor/ruby-2.1.5/lib/ruby/2.1.0/open3.rb:260:in `write': Broken pipe (Errno::EPIPE)
	from /app/vendor/ruby-2.1.5/lib/ruby/2.1.0/open3.rb:260:in `block in capture3'
	from /app/vendor/ruby-2.1.5/lib/ruby/2.1.0/open3.rb:199:in `popen_run'
	from /app/vendor/ruby-2.1.5/lib/ruby/2.1.0/open3.rb:93:in `popen3'
	from /app/vendor/ruby-2.1.5/lib/ruby/2.1.0/open3.rb:252:in `capture3'
	from /app/test.rb:5:in `<top (required)>'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/runner.rb:60:in `load'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/runner.rb:60:in `<top (required)>'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:123:in `require'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:123:in `require_command!'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:90:in `runner'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands/commands_tasks.rb:39:in `run_command!'
	from /app/vendor/bundle/ruby/2.1.0/gems/railties-4.2.0/lib/rails/commands.rb:17:in `<top (required)>'
	from bin/rails:8:in `require'
	from bin/rails:8:in `<main>'

I ran this by adding a test.rb file in the rails app that i'm getting the error in.
I can give more details if needed. If i run this on local it does not happen.

I also ran this and it seems like i get something like this:
➜  pxls git:(feat-create_market) ✗ heroku run bundle exec rails runner file --version -a epicpxls-staging-pr-20
Running bundle exec rails runner file --version on ⬢ epicpxls-staging-pr-20... up, run.1447 (Free)
rails: version unknown
➜  pxls git:(feat-create_market) ✗ file --version
file-5.25
magic file from /usr/share/file/magic

The one below is on local obviously. Could heroku not have file installed?
At first i thought that file was not on heroku because of my buildpacks but i ran this on a default ruby buildpack on another heroku app and i get the same thing.

@Chocksy Ok, I also managed to reproduce it on a newly created Heroku dyno. So, these are my findings:

Locally my version of file command is 5.25, but on Heroku it's 5.14, so a bit older.
When I run the above Ruby script on a Heroku dyno which uses Ruby 2.0.0, I get this error consistently.
When I run the above Ruby script on a Heroku dyno which uses Ruby 2.3.0, I don't get this error.
When I run the above Ruby script locally on Ruby 2.0.0, I don't get this error.
When I run the above Ruby script on a Heroku dyno which uses Ruby 2.0.0, but instead of giving 256KB (256*1024) I give 160KB of the file to stdin of the shell command, I mostly don't get this error. I say mostly because I sometimes to get it if I run it many times in a row 😞

In conclusion, I don't know what's the root cause. maybe Ruby improved Open3 implementation in later Ruby versions, or file command was improved in newer versions, or maybe the infrastructure of Heroku dynos is making something not work. What Ruby version are you running on Heroku?
You have the following options:

Upgrade to newer Ruby version on Heroku
plugin :determine_mime_type, magic_header: 160*1024, though even then the Errno::PIPE error can apparently still occasionally occur 😕
Switch to another MIME type analyzer (e.g. plugin :datermine_mime_type, analyzer: :mimemagic)

When using the option (2), you could additionally automatically retry any occasional Errno::EPIPE errors:
plugin :determine_mime_type, magic_header: 160*1024, analyzer: -> (io, analyzers) do
  begin
    analyzers[:file].call(io)
  rescue Errno::EPIPE
    retry
  end
end

@janko-m wow i tried to test with different file sizes and i noticed the same thing it happens with multiple runs but i did not try a different ruby version.
I'm running ruby-2.1.5 I think i can upgrade to 2.3.0 and see if i still get the issue as this project is fairly new. The retry thing is also a good idea.

I just upgraded to ruby 2.3.0 and it seems like all is working fine.
Thanks @janko-m

I had this problem with file analyzer on CentOS with both obsolete file command and obsolete Ruby installed, mimemagic does the job well (option 3). Thanks.


Create a simple A2L Viewer mainly with the purpose to do manual module tests as well as serve as a simple GUI. Use C++ GUI (wxWidgets

Basic viewer is created


Version upgrade: Scala 2.13.0-RC3

details:

Scala:    2.13.0-RC2 -->> 2.13.0-RC3
mockito-scala: 1.4.6 -->> 1.5.0 https://github.com/mockito/mockito-scala/blob/v1.5.0/docs/release-notes.md
scalatest: 3.0.8-RC4 -->> 3.0.8-RC5

Hi @dejan2609,
Thank you for your contribution! We really value the time you've taken to put this together.
Before we proceed with reviewing this pull request, please sign the Lightbend Contributors License Agreement:
http://www.lightbend.com/contribute/cla

Ok, I guess I will try to sign, scan and send individual CLA.

@dejan2609 you are certainly welcome to print and sign the CLA if you prefer to do it that way, but for our purposes, all that's needed is to authenticate by clicking the "Confirm with your GitHub account" if you and your employer agree to the terms.

@TimMoore done, thanx for the tip  !

Publishing scala-logging_2.13.0-RC3-3.9.2


add python runtime dependency

Necessary for the conda package to handle python version dependencies correctly.
@conda-forge-admin, please rerender.

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


Update Motion to Continue

Why are the certificates of service different for the motion and answer?
If they have to be different, we should at least make sure the one in motion to continue is on 1 page and probably move "[date served]" to after the fill in line. The signature line for the defendant is off and it should be made clear they need to select one of the lines.
I think most of all, on the download and in the instructions we should be clear in instructing that this form is not complete or ready to file until service is made and this portion is filled out.

made this change


fix: consider same timestamp as parent block invalid

cons child.timestamp == parent.timestamp as consensus error
ref
https://github.com/ethereum/go-ethereum/blob/8f373227ac481685148019b21ef9e1478d3ba609/consensus/beacon/consensus.go#L239-L242

Codecov Report

Merging #2454 (e7e05c1) into main (eb37bc7) will decrease coverage by 57.29%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #2454       +/-   ##
===========================================
- Coverage   71.46%   14.18%   -57.29%
===========================================
  Files         486      486
  Lines       60030    60030
===========================================
- Hits        42903     8513    -34390
- Misses      17127    51517    +34390

Flag
Coverage Δ

integration-tests
14.18% <0.00%> (-4.10%)
:arrow_down:

unit-tests
?

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

Impacted Files
Coverage Δ

crates/consensus/common/src/validation.rs
0.00% <0.00%> (-80.89%)
:arrow_down:

crates/interfaces/src/consensus.rs
0.00% <ø> (-100.00%)
:arrow_down:

... and 366 files with indirect coverage changes


Script might be confused about buster and bookworm for upgrading?

Hi there,
I was doing some due diligence code review before trying this script out and got confused about how the --to-latest-debian worked, to me it reads like it's going to upgrade buster -> bullseye (which is right, Debian 10 to 11) then try and downgrade bullseye -> buster rather than going to bookworm (Debian 12):
elif [ "--to-latest-debian" = "${ACTION:-$1}" ] ; then
  print_info
  dist_upgrade_lenny_to_squeeze
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_squeeze_to_wheezy
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_wheezy_to_jessie
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_jessie_to_stretch
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_stretch_to_buster
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_buster_to_bullseye
  [ $? -ne 0 ] && ret=$(($ret+1))
  dist_upgrade_bullseye_to_buster
  [ $? -ne 0 ] && ret=$(($ret+1))

In fact looking at this I'm wondering if it's mixing up buster and bookworm here?
function dist_upgrade_bullseye_to_buster() {
export old_distro=bullseye
export old_ver="inux 11"
export new_distro=buster
export new_ver="inux 12"
dist_upgrade_x_to_y
ret=$?
return $ret
}

Should that be this?
function dist_upgrade_bullseye_to_bookworm() {
export old_distro=bullseye
export old_ver="inux 11"
export new_distro=bookworm
export new_ver="inux 12"
dist_upgrade_x_to_y
ret=$?
return $ret
}

Am I interpreting that right?
All the best,
Chris

Thanks for the heads up.  Code updated.


Adjust output audio speed

Is there a way to adjust output audio speed when performing zero-shot TTS?

Hi,
Currently, the model cannot control the speed. However, different random seeds or hyperparameters could generate speech with different speed. You could adjust sub_amount, top_p, seed or cfg_coef in inference.py to get various results.


Refactoring tests definition

During the investigation,
I found that debug version of the test was failing to run due to missing vulkan-1.dll
The program at load time is looking for that .dll  based on env. path but it seems the container we run on fail to provide it.
Since we build and produce vulkan-1.dll at compile time, we updated the env path with the output lib path.

Finally !! 🚀


InfluxDB 2.0.3 release notes

Update release notes for InfluxDB 2.0.3 release.
https://github.com/influxdata/influxdb/blob/master/CHANGELOG.md

Review OSS 2.0.3 milestone issues to make sure all release notes requiring feature doc updates have an associated issue.


typeahead: Fix bug where typeahead showed momentarily on shift + tab.

Break on keyup for case of shift key, instead of letting it trigger the typeahead.
Fixes: #23627.

Screenshots and screen captures:
Before:
https://user-images.githubusercontent.com/68962290/214800322-966f7d08-ade9-4a21-8281-81780913a708.mp4
After:
https://user-images.githubusercontent.com/68962290/214802293-0ea146f9-290a-46ac-b9ee-f62d1271a323.mp4

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@N-Shar-ma I think the PR description and commit message should link to #24152?

Works for me in manual testing! @amanagr could you please review?

@N-Shar-ma I think the PR description and commit message should link to #24152?

Oops! Sorry for the oversight -- fixed!

This works well in my testing and looks reasonable, merged, thanks @N-Shar-ma!

This was reverted because of issues with the > keyboard shortcut for completing a topic that it caused. One can't reopen a merged PR, so plan to submit a new one with that fixed when you've got the chance.


HttpBuildCacheService doesn't cope well with stale connections

We're seeing these exceptions occasionally that seems to indicate the HttpBuildCacheService is reusing a stale connection:
Caused by: org.apache.http.NoHttpResponseException: gradle.netflix.net:443 failed to respond
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:141)
	at org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
	at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
	at org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
	at org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:157)
	at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.gradle.internal.resource.transport.http.HttpClientHelper.performHttpRequest(HttpClientHelper.java:141)
	at org.gradle.internal.resource.transport.http.HttpClientHelper.performHttpRequest(HttpClientHelper.java:117)
	at org.gradle.caching.http.internal.HttpBuildCacheService.store(HttpBuildCacheService.java:159)
	at org.gradle.caching.internal.controller.service.BaseBuildCacheServiceHandle.storeInner(BaseBuildCacheServiceHandle.java:93)

Expected Behavior
Stale connections should be tolerated.
Current Behavior
The pool can return stale connections and attempt to use them.
Context
Build caching is disabled for a build.
Steps to Reproduce
Unclear. We're running a default Varnish configuration for timeouts, which has a generous 60 second connection idle timeout - https://info.varnish-software.com/blog/understanding-timeouts-varnish-cache.
Your Environment
Gradle 6.4.1

We see the same on fetches, which impacts the effectiveness of the cache as it turns off for the remainder of the build:
I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://gradle.netflix.net:443: The target server failed to respond
Retrying request to {s}->https://gradle.netflix.net:443
I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://gradle.netflix.net:443: The target server failed to respond
Retrying request to {s}->https://gradle.netflix.net:443
I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {s}->https://gradle.netflix.net:443: The target server failed to respond
Retrying request to {s}->https://gradle.netflix.net:443
Could not load entry 7f255528692e6b8306a02828ffd93128 from remote build cache: gradle.netflix.net:443 failed to respond

@DanielThomas this indicates that how your proxy is closing connections is not visible to the client. Do you have any details on exactly what your proxy is doing when it closes a connection?

It would appear that timeout_idle is the prevailing timeout, it's 5s by default (https://info.varnish-software.com/blog/understanding-timeouts-varnish-cache), but Varnish received the whole request here.
Here's that session, two requests:
{
  "tag": "Begin",
  "value": "sess 0 PROXY"
},
{
  "tag": "SessOpen",
  "value": "<IP_ADDRESS> 0 a2 <IP_ADDRESS> 0<PHONE_NUMBER>.669103 755"
},
{
  "tag": "Proxy",
  "value": "2 <IP_ADDRESS> 61006 <IP_ADDRESS> 443"
},
{
  "tag": "Link",
  "value": "req 188125996 rxreq"
},
{
  "tag": "Link",
  "value": "req 186631459 rxreq"
},
{
  "tag": "SessClose",
  "value": "RX_TIMEOUT 10.060"
},
{
  "tag": "End",
  "value": ""
}

First request:
{
  "tag": "Begin",
  "value": "req 188125995 rxreq"
},
{
  "tag": "Timestamp",
  "value": "Start:<PHONE_NUMBER>.669175 0.000000 0.000000"
},

Second request, literally 5.007522 between them:
{
  "tag": "Begin",
  "value": "req 188125995 rxreq"
},
{
  "tag": "Timestamp",
  "value": "Start:<PHONE_NUMBER>.676697 0.000000 0.000000"
},

Those errors do seem to indicate that the retries are trying to reuse a stale connections. Maybe we got really unlucky and the pool returned three similarly stale connections in a row. I only see one request, but may be those second and third attempts didn't get that far (but the error seems to indicate the request was sent)?
This is also the same infrastructure that serves all our artifact traffic and we don't see outright failures like this at all, but maybe we're seeing some retries - I'll go look at our metrics. I'll open a case with Varnish to understand the behaviour better too before we increase the setting.
Is 30s still the default idle timeout for Gradle HTTP client connections?

Some background on the stale connections with httpclient. The repeated failures make me thing it's is those connections with RX_TIMEOUT are not reset, as I'd think the connection check would catch those (unless it was a race between the check and the request being made, but doesn't feel like it):
http://hc.apache.org/httpcomponents-client-ga/tutorial/html/connmgmt.html#d5e418
Sounds like we can also control this behaviour with the response, which is good to know:

Some HTTP servers use a non-standard Keep-Alive header to communicate to the client the period of time in seconds they intend to keep the connection alive on the server side. HttpClient makes use of this information if available.

In fact I bet we're seeing this with artifact requests too, but connection reuse is rapid enough that timeouts are rarer and retries are enough to stop the issue bubbling up.

It is a regular close on this timeout, so HttpClient should be seeing those connection closures. Let me run some tests with debug logging for HttpClient and see if I can get some more clarity on what's going on before I make any changes to the timeouts:

Good catch. It looks like the blog post is a bit unclear on that particular point. It says timeout_idle is from accept() until we receive the start of a request and then at the very end it mentions that timeout_idle also applies in between requests for keepalive.
On RX_TIMEOUT we do a regular close() which will trigger the FIN/FIN-ACK.
Worth mentioning is that there is a potential for a race condition here, if the client sends a request just close enough to the timeout. Varnish could even have  the FIN in flight as the client sends the next request.
To summarize, the timeout_idle is the prevailing timeout. It applies both to the initial request and also to the in between requests before we have received any data.
RX_TIMEOUT does a close(), which should result in a regular FIN shutdown (i.e. the other end should see this).

The debug logs indicate we are hitting three seperate stale connections when this bubbles up, they're being correctly closed on error. There's quite a bit of outdated information about the staleness checks. The staleness check on every connection lease was removed some time ago:
https://github.com/apache/httpcomponents-client/commit/c5c0bc680180c3ccac90430a6380901dc1e968df
That's been replaced with getValidateAfterInactivity and as of 4.4 that appears to be 2s by default, which means I'd expect those should catch the 5s timeouts:
https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/conn/PoolingHttpClientConnectionManager.java#L183
I can reproduce the retries easily enough, though all three retries for a single request hitting stale connections is rarer. Here's a complete session with a single retry:
2020-11-16T08:57:26.679+1100 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Load entry d6ceb730b5a490bea6c9b135a93d7fbd from remote build cache' started
2020-11-16T08:57:26.679+1100 [DEBUG] [org.gradle.internal.resource.transport.http.HttpClientHelper] Performing HTTP GET: https://gradle.netflix.net/cache/d6ceb730b5a490bea6c9b135a93d7fbd
2020-11-16T08:57:27.245+1100 [DEBUG] [org.apache.http.impl.conn.DefaultHttpClientConnectionOperator] Connection established <IP_ADDRESS>:53505<-><IP_ADDRESS>:443
2020-11-16T08:57:27.246+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: set socket timeout to 30000
2020-11-16T08:57:27.246+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Executing request GET /cache/d6ceb730b5a490bea6c9b135a93d7fbd HTTP/1.1
2020-11-16T08:57:27.246+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Target auth state: UNCHALLENGED
2020-11-16T08:57:27.246+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Proxy auth state: UNCHALLENGED
2020-11-16T08:57:27.415+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection can be kept alive indefinitely
2020-11-16T08:57:27.419+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection can be kept alive indefinitely
2020-11-16T08:57:27.442+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection can be kept alive indefinitely
2020-11-16T08:57:27.443+1100 [DEBUG] [org.gradle.caching.http.internal.HttpBuildCacheService] Response for GET https://gradle.netflix.net/cache/d6ceb730b5a490bea6c9b135a93d7fbd: HTTP/1.1 200 OK
2020-11-16T08:57:33.541+1100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection [id: 32][route: {s}->https://gradle.netflix.net:443] can be kept alive indefinitely
2020-11-16T08:57:33.542+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: set socket timeout to 0
2020-11-16T08:57:33.543+1100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection released: [id: 32][route: {s}->https://gradle.netflix.net:443][total kept alive: 7; route allocated: 8 of 20; total allocated: 8 of 20]
2020-11-16T08:57:33.548+1100 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Completing Build operation 'Load entry d6ceb730b5a490bea6c9b135a93d7fbd from remote build cache'
2020-11-16T08:57:33.549+1100 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Load entry d6ceb730b5a490bea6c9b135a93d7fbd from remote build cache' completed

There's less than two seconds between the connection being returned and leased again, so it's not checked for staleness, but it also shouldn't have timed out yet. HttpBuildCacheService isn't doing anything unusual with the connection, it's streaming the response entity directly so the connection should have been returned to the pool immediately after the response was finished being read:
2020-11-16T08:57:35.243+1100 [DEBUG] [org.gradle.caching.internal.controller.service.OpFiringBuildCacheServiceHandle] Load entry 7f255528692e6b8306a02828ffd93128 from remote build cache
2020-11-16T08:57:35.243+1100 [DEBUG] [org.gradle.internal.operations.DefaultBuildOperationRunner] Build operation 'Load entry 7f255528692e6b8306a02828ffd93128 from remote build cache' started
2020-11-16T08:57:35.244+1100 [DEBUG] [org.gradle.internal.resource.transport.http.HttpClientHelper] Performing HTTP GET: https://gradle.netflix.net/cache/7f255528692e6b8306a02828ffd93128
2020-11-16T08:57:35.244+1100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection request: [route: {s}->https://gradle.netflix.net:443][total kept alive: 7; route allocated: 8 of 20; total allocated: 8 of 20]
2020-11-16T08:57:35.244+1100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection leased: [id: 32][route: {s}->https://gradle.netflix.net:443][total kept alive: 6; route allocated: 8 of 20; total allocated: 8 of 20]
2020-11-16T08:57:35.244+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: set socket timeout to 30000
2020-11-16T08:57:35.245+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: set socket timeout to 30000
2020-11-16T08:57:35.245+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Executing request GET /cache/7f255528692e6b8306a02828ffd93128 HTTP/1.1
2020-11-16T08:57:35.245+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Target auth state: UNCHALLENGED
2020-11-16T08:57:35.245+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Proxy auth state: UNCHALLENGED
2020-11-16T08:57:35.246+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: Close connection
2020-11-16T08:57:35.247+1100 [DEBUG] [org.apache.http.impl.conn.DefaultManagedHttpClientConnection] http-outgoing-32: Shutdown connection
2020-11-16T08:57:35.247+1100 [DEBUG] [org.apache.http.impl.execchain.MainClientExec] Connection discarded
2020-11-16T08:57:35.247+1100 [DEBUG] [org.apache.http.impl.conn.PoolingHttpClientConnectionManager] Connection released: [id: 32][route: {s}->https://gradle.netflix.net:443][total kept alive: 6; route allocated: 7 of 20; total allocated: 7 of 20]
2020-11-16T08:57:35.247+1100 [DEBUG] [org.apache.http.impl.execchain.RetryExec] The target server failed to respond

Which is caused by the same timeout as before:
{
  "tag": "Begin",
  "value": "sess 0 PROXY"
},
{
  "tag": "SessOpen",
  "value": "<IP_ADDRESS> 0 a2 <IP_ADDRESS> 0<PHONE_NUMBER>.419865 532"
},
{
  "tag": "Proxy",
  "value": "2 <IP_ADDRESS> 53505 <IP_ADDRESS> 443"
},
{
  "tag": "Link",
  "value": "req 332558867 rxreq"
},
{
  "tag": "SessClose",
  "value": "RX_TIMEOUT 5.249"
},
{
  "tag": "End",
  "value": ""
}

Which lead me back to the Varnish blog post:

In the other cases timeout_idle starts ticking after the request handling is done, and that implements the keepalive timeout in Varnish Cache.

That seems to indicate that the timeout starts when request handling is finished, not when the response has been read. If I rate limit keep alive requests, that's what I see:
curl -o /tmp/test --http1.1 --limit-rate 250K -v https://gradle.netflix.net/cache/d6ceb730b5a490bea6c9b135a93d7fbd https://gradle.netflix.net/cache/7f255528692e6b8306a02828ffd93128

...

* Connection #0 to host gradle.netflix.net left intact
* Connection 0 seems to be dead!
* Closing connection 0

I'll follow up with Varnish on that. I think HttpClient could do a better job of checking for closed connections, curl appears to do this really cheaply and effectively, but this makes keep alive ineffective for requests with large responses.

Looks like that also makes the {{Keep-Alive}} header support ineffective too - it (correctly) starts that duration ticking when the connection is released back to the pool:
https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/MainClientExec.java#L275-L289
https://github.com/apache/httpcomponents-client/blob/4.5.x/httpclient/src/main/java/org/apache/http/impl/execchain/ConnectionHolder.java#L99-L100

The default 2s idle check threshold seems incredibly conservative, I can't imagine that it's worst case performance for this method could be more than a ms or two:
https://github.com/apache/httpcomponents-core/blob/4.4.x/httpcore/src/main/java-deprecated/org/apache/http/impl/AbstractHttpClientConnection.java#L314-L330
In fact I ran a quick test setting the threshold to 1ms with a 1ms sleep to ensure the check ran for every lease and the overhead for open connections (which I guess is the worst case, I bet closed connections wouldn't need for wait for the 1ms timeout) and the overhead is tiny:

So you might consider decreasing this threshold so you can keep retries for failures unrelated to the pooled connection state.

@DanielThomas thank you very much for the investigation and wealth of information.

To mitigate this with Varnish we increase timeout_idle from the default 5s to 30s for a session following a delivered requests to allow connection reuse for that period and put us well inside the test on lease threshold for HttpClient:
sub vcl_deliver {
    // increase timeout_idle for subsequent requests
    set sess.timeout_idle = 30s;
}

@DanielThomas is that a satisfactory result for you? Or do you still see a need for a more aggressive aliveness check?

@ldaley I would have said this is fine for us, but we're also seeing this during publishing. Still unclear if it's stale connections however, but does seem like non-retryable requests like this are more likely to see failures that cause this to fail outright:
https://github.com/Netflix/mantis-gradle-plugin/runs/2079912807?check_suite_focus=true
FWIW I also looked at what OkHttp does for comparison, and it's far more aggressive doing an extensive check for every connection except if it's a GET request, using similar method to Apache HttpClient if the Socket is still believed to be open:
https://github.com/square/okhttp/blob/master/okhttp/src/main/kotlin/okhttp3/internal/connection/ExchangeFinder.kt#L80
https://github.com/square/okhttp/blob/master/okhttp/src/main/kotlin/okhttp3/internal/connection/RealConnection.kt#L646-L671
https://github.com/square/okhttp/blob/master/okhttp/src/main/kotlin/okhttp3/internal/Util.kt#L377-L400

@DanielThomas I'll work this into our plans.
We are also going to make the writes retryable in an upcoming round of work.

This may be improved by https://github.com/gradle/gradle/pull/19196


Add Focused.app

71Squared took over the development of Typed, from Realmac Software.
They changed the app name to Focused.

Merged as 7d38a3c505b0043974ac3336ca706eef16e7ef2b.


refactor: use Grid.js to render statusboard

Rework the board using Grid.js library (adding pagination, search, sort)


css bug bottom bar css doesn't move up and handles resize poorly

fix, removed footer, moved content to header


Use

Fleek build fail with this error:

I got the same error in local when i do use serve script

I would recommend update others dependencies to latest version, it may help Vue has a next version 3.1.4 (now we are using 3.1.2)

@bonustrack how does it work for you now?

Awesome


[warning] failed package validation and/or copy for commit 5a076ef454f8dd8d2e3d335d3a7f53bcc67185eb

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py38h526f742_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py36he996604_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py39h424b07e_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py36h4000f80_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py37ha98acdc_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/linux-64/vim-8.2.2488-py37h6ec0b86_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py39hb7b48de_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py37h5f0546e_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py36h1388bb7_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py36hd09ed37_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py37h459389a_0.tar.bz2

Hi @conda-forge/vim! This is the friendly automated conda-forge-webservice!
It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(
This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.
Rerendering the feedstock will usually fix these problems.
If you have any issues or questions, you can find us on gitter in the
community chat room or you can bump us right here.
error messages:

invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/vim-8.2.2488-py38hf0f9b9d_0.tar.bz2


Add jdbc Instant encoder/decoder

Problem
A jdbc Instant encoder/decoder is missing. It is available in classic quill.
Solution
Ported the code from quill classic.
@getquill/maintainers

@deusaquilus Is there something that is blocking this?

Already impl. in other PR.


Facing error: Attempt 1: Verification page detected. Trying to bypass... Error clicking verification button: 'NoneType' object is not callable

Attempt 1: Verification page detected. Trying to bypass...
Error clicking verification button: 'NoneType' object is not callable
Attempt 2: Verification page detected. Trying to bypass...
Verification button found. Attempting to click.
Attempt 3: Verification page detected. Trying to bypass...
Facing that error non stop. Running with logs on my test file.
And then when i run it on test.py
i get this error:
<IP_ADDRESS>:9222浏览器无法链接。
请确认：
1、该端口为浏览器
2、已添加'--remote-debugging-port=9222'启动项
3、用户文件夹没有和已打开的浏览器冲突
4、如为无界面系统，请添加'--headless=new'参数
5、如果是Linux系统，可能还要添加'--no-sandbox'启动参数
可使用ChromiumOptions设置端口和用户文件夹路径。```

Error clicking verification button: 'NoneType' object is not callable
Attempt 2: Verification page detected. Trying to bypass...
Verification button found. Attempting to click.
Attempt 3: Verification page detected. Trying to bypass...
Basic search failed. Searching for button recursively.
Error clicking verification button: 页面被刷新，请操作前尝试等待页面刷新或加载完成。
Attempt 4: Verification page detected. Trying to bypass...
Verification button found. Attempting to click.
Attempt 5: Verification page detected. Trying to bypass...
Basic search failed. Searching for button recursively.
Error clicking verification button: 页面被刷新，请操作前尝试等待页面刷新或加载完成。
Attempt 6: Verification page detected. Trying to bypass...
Verification button found. Attempting to click.
Attempt 7: Verification page detected. Trying to bypass...
^C2024-11-28 01:45:28,038 - INFO - Closing browser...```    tried again wont work :(

@UselessParadox sup apu
co.set_user_agent(
    "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.5615.49 Safari/537.36"
)

请问现在解决问题了嘛？
现在我完全无法通过验证码

@UselessParadox sup apu
co.set_user_agent(
    "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/112.0.5615.49 Safari/537.36"
)

using that ?

Oh, no, I found a problem after reading the source code. The original code judged whether it passed the verification code by the website title, but now I am the verification code of that widget. I modified the logic of ispass, and now the ip can pass the verification under normal conditions, and I didn't modify ua.


Fix javadoc sources Jar publication

#609

Codecov Report

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


Buildx Error

Description
In my Azure TRE deployment I am trying to run the make all command and Get an error I have not seen before, This environment was working before, I ran the destroy command to tear it down, rebuilding isnt working.
Code
Make all

Please try rebuilding your dev container without cache using:

Or this could actually be an issue with the docker configuration on your host machine, rather than the dev container.

Thanks Marcus, I appear to be getting the same error

Ok, that suggests it 's an issue with your Docker configuration rather than Azure TRE.
You could try reinstalling buildx: https://docs.docker.com/build/install-buildx/
If that does not work, suggest creating an issue on the Docker buildx repo: https://github.com/docker/buildx

Closing this as isn't an issue with Azure TRE, but with docker configuration.


Rspec tests

Hey Ryan, I'll be taking this over this weekend, should have a good base so more people can start working on it for the beginning of next week :) Thank you!

@javimbk +1 thank you sir!


Please enable issues on this repository

Hi, this is a dummy PR. Is there a reason why issues are not enabled on this repo? If not, could you enable them please? Thanks!

I'll look into it

Done, thanks. Probably something to do with GitHub members explicitly removing fork status on repository and things breaking.


Fun test stub cleanup using function composition

Not sure if you prefer the explicitness of the mock names. If so we could still simplify the implementations, e.g.:
func mockFetchAuthToken(
  result: Either<Prelude.Unit, GitHubAccessToken>
  )
  -> (String)
  -> EitherIO<Prelude.Unit, GitHubAccessToken> {
    return result |> pure >>> const
}

They'd both have the same implementation, though!

I just pushed a fix for tests on this branch.

Oh weird I swear I ran tests.


[Discussion] Pagination setup

So this is the first time I have done pagination in Timber, I feel it could be abstracted more, a Timber::setup_pagination that sets all this up based off $context['posts'] would be nice, or something of that ilk. If it could take a collection of posts, generate the query needed and then run query_posts that would be awesome, means the code goes from this:
global $paged;

if (!isset($paged) || !$paged){
    $paged = 1;
}

$args = array(
        'post_type' => 'event',
        'posts_per_page' => 5,
        'paged' => $paged
);
/* THIS LINE IS CRUCIAL */
/* in order for WordPress to know what to paginate */
/* your args have to be the defualt query */
    query_posts($args);
/* make sure you've got query_posts in your .php file */
$context['posts'] = Timber::get_posts();
$context['pagination'] = Timber::get_pagination();
Timber::render('page-events.twig', $context);

to
global $paged;
$paged = (!isset($paged) || !$paged) ? 1 : $paged;
$context['posts'] = Timber::get_posts(array('post_type' => 'jobs', 'posts_per_page' => 5, 'paged' => $paged));

Timber::setup_pagination();

Timber::render('page-events.twig', $context);

I'm not sure how feasible generating the query after the query has been made is, even if that part isn't, abstracting the pagination setup away into Timber is nicer and can take a few of the headaches away from the user.

I'm going to close this as there are many other issues open regarding this issue.


Definition mismatch and wrong conversion of InlineValueContext

Hi,
wanted to implement 'textDocument/inlineValue'  from version 3.17 of LSP Documentation in Python and use Version 8.0.0 of vscode-languageclient in my VSCode extension.
But struggeling with the different definition of InlineValueContext in LSP Documentation and the implementation in vscode-languageserver-types  and the implementation of what I get in textDocument/inlineValue request:
{
  "jsonrpc": "2.0",
  "id": 21,
  "method": "textDocument/inlineValue",
  "params": {
    "textDocument": { "uri": "file:///c%3A/tmp/rt1/tests/w.robot" },
    "range": {
      "start": { "line": 0, "character": 0 },
      "end": { "line": 17, "character": 0 }
    },
    "context": {
      "frameId":<PHONE_NUMBER>560,
      "stoppedLocation": [
        { "line": 6, "character": 1 },
        { "line": 6, "character": 1 }
      ]
    }
  }
}

stoppedLocation is not a Range structure, I think it is not converted correctly from vscode.Range to lsp.Range. The frameID is interessting, but I think in LSP implementation not relevant, maybe only together with a DAP implementation.
ok, so what is the correct defintion/implementation of InlineValueContext?
thanks
Daniel

I added the frameId to the spec. I think it could be useful in cases where a server knows about DAP which is OSS as well.

Done and ships with 8.0.1


Board

How can i add third page to scoreboard?

Implement it yourself? Or keep asking random people


Fix rate limiting for test harness's use of Github

#1095 fixed the server's use of Github, but the test harness uses it too.
Have tested locally to make sure this still works when GITHUB_TOKEN is unset.
Fix #979

Thanks Daniel!


create a element that turn a matrix into reduced Echelon form

echelon form/ reduced echelon form can solve a linear system, while also looks very stylish, also it’s unique(reduced echelon form, not normal echelon form)

I'm assuming maths-digraph?


284 aurora UI upgrade

Enlarge all content text for better reading experience
Refactor scroll to comment and content function
Change category style in article detail page
Changed all tags styles for clarity
Changed background wave to a gradient flow to enhance the smooth flow of the background

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kafka topic ingestion fails if topic contains zero messages

Affected module
Ingestion Framework
Describe the bug
A Kafka ingestion pipeline that has "Ingest Sample Data" enabled appears to fail with exit 1 if it tries to sample one or more topics that contains 0 messages.
Topics that do not contain messages will be listed in the failures[] array of the MessageSourceStatus() object. For example:

To Reproduce

Create an Avro topic in Kafka with a corresponding Avro schema, but do not insert any messages in the topic
Create an ingestion pipeline and select the "Ingest Sample Data" option
Run the ingestion pipeline
Check the logs of the pipeline and inspect the failures[] array of the MessageSourceStatus() object outputted to the log

Expected behavior
Topics that contain zero messages should be categorized as "warnings" instead of "failures"--An empty topic should not cause the pipeline to fail.
Version:

OS: Kubernetes
Python version:
OpenMetadata version: 0.12.0
OpenMetadata Ingestion package version:

@ehausig did you enable the sample data to be ingested?

@ehausig are you seeing the pipeline failure or its reporting failures on no.of topics it was able to extract

@harshach I am seeing a pipeline failure:

I now think it has nothing to do with the number of messages in a topic....maybe I should update the report?

Issue misdiagnosed. This looks to be more of an issue with the ingestion pipeline not being able call SchemaRegistryClient.get_by_id().

Thanks for the report @ehausig . Trying to reproduce. Can you please share the ingestion framework version
metadata --version

@harshach sure, where I can I find the ingestion framework version? I know that the container image that is being spun-up for the pipeline is:
openmetadata/airflow:0.12.0


Setting up the visualizer

I am pretty new to electronics and arduino projects in particular.
Right now what I have is a LED strip with 45 LEDs. Right now I am trying to power these of a 5V USB wall plug that should provide about enough to make this work.
I have connected the +5V of the strip to the USBs 5V and the GND of the Strip to the GND of the USB plug.
Now I set up the code in python and Arduino and want to start the visualizaion. But I have a few questions:

how do I flash the ESP8266 correctly, mine has a "Flash"-labeled button - do I need to press it all the time while uploading the code?
Hoe do I connect the ESP8266 to the LED? I dont think that I could just hook up the ESPs RX to the DIN of the LED and powering it off another power source than the strip itself, that would be no common ground. However, I dont know how to connect them properly together.

Thanks for any help!
EDIT 1: My module is the NodeMCU Lua Amica Module V2 ESP8266 ESP-12E.

After some fiddling around I can say what worked for me:

Holding the Flash button the whole time while it flashes works for me.
They dont exactly need the same GND connection, as I was able to simply add the wire from the RX pin to the DIN of the strip, however I now have the problem that there is always flashign of the leds. I don't know if that has somethign to do with that.

Using the Vin and GND pin of my Node MCU I could also resolve this problem, I will maybe make a guide on how to build something like this so others don't run into the same problem as me. Thinking about it afterwards, all questions were pretty silly but for people not knowing a thing about how electronics work it could be a nice touch to make a video / even more detailed written guide with images showing the steps in detail.

I imagine a step by step setup guide would be appreciated by a lot of
people 👍
On Feb 18, 2018 13:48, "Vincent"<EMAIL_ADDRESS>wrote:

Using the Vin and GND pin of my Node MCU I could also resolve this
problem, I will maybe make a guide on how to build something like this so
others don't run into the same problem as me. Thinking about it afterwards,
all questions were pretty silly but for people not knowing a thing about
how electronics work it could be a nice touch to make a video / even more
detailed written guide with images showing the steps in detail.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/scottlawsonbc/audio-reactive-led-strip/issues/125#issuecomment-366517376,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ae5azD4wyes6LSiCoHkgMkFRgeVNgC8bks5tWCocgaJpZM4SJY0V
.


(recreation of) Move this as per TOC #52013

Please provide a description of this PR:
Old PR (#52013) was stuck on an outdated release-builder SHA for some reason. Recreating to see if it bumps.

@bleggett: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
2c26c2f6bdfdf6c060307bb7c133eeaf9b2c0e9c
link
true
/test release-notes

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-sigs/prow repository. I understand the commands that are listed here.


Add .contribute command

Acceptance criteria

Create new function for faq_contribute in faq.py
Function response should link to https://docs.ergoplatform.com/contribute/
Add .contribute command to sigmabot.py file

https://github.com/Eeysirhc/sigmabot/commit/1fac84021e2b67b43d7fb2e56de4bc4bdfeff962


fix flakehell version passed to flake8 application

Currently flakehell is using 2 versions:

flakehell.__version__ which is pypi package version
flakehell._constants.VERSION which is passed to Flake8Application as version kwarg

Maybe it's some leftover after refactor or something, but it's quite confusing and imho only one version number should be used for both cases.
Please correct me if I am wrong, because maybe I misunderstood something.
Thanks for maintaining this really useful project!

There is some issue with CI, both PR I have created (2nd is https://github.com/life4/flakehell/pull/45) are really simple and all tests for them pass locally. If you know exactly what's weong let me know I can try to fix it

CI fixed in https://github.com/life4/flakehell/pull/47

Thank you, good catch :+1:


Add Raspberry Pi and OS X suport

Fixes https://github.com/Rantanen/node-opus/issues/2
Sorry that github thinks 360 files were changed. In reality, it was only 4 files. But I merged your deps change instead of rebasing... so git is going nuts.

If you really want the clean history, I can create a new branch and do some cherry-picking

Could you do that? :)
Or just rebase -i this one to the master and skip my commits.
I don't really care about the history, but I'd like to have a glance at the changes which is painful with the 29672 changed lines. :)
(I think there was something in the README.md for example that was still referencing git submodule, which is what I got rid of to make this work. So that could be removed as well)

Nice... I feel like a freaking git ninja right now.

Oh! That was all of it! I was still waiting for the other commits, didn't realize you squashed them to just two. Nice! :)

Yea, I just went a little nuts when I realized exactly how powerful git rebase -i is :D

Thanks! Removed the git submodule commands from the README.md and pushed to npm!
(And yes, it is! <3)

Whoot! Thanks for staying up late(ish) and hammering this out with me!

No problem! Always happy with incoming PRs.
.. Although I did miss the chance to delay that last commit of mine by 30 seconds to make it count for today's Streak: Wed May 6 23:59:35 2015 +0300.  :)


Service version

Hi, I was wondering if you could include the option to get the version of the services running, I dont know if it would be much trouble, but this is what the library needs, would be really awesome to include that since im working in a big project where we are using it.
Or if it is already there and im not seeing it, please guide me, thanks.

There isn't a way in the current version to get the version of NMAP.
To add this as a feature, I would need to add a new function that runs nmap -v and uses regex to grab the version and return it as a string.  Would that work for you?

no no, i mean, when yo do an nmap scan, you get somethng like
PORT     STATE    SERVICE  VERSION
25/tcp   filtered smtp
80/tcp   open     http     nginx 1.6.2
110/tcp  open     pop3     Dovecot pop3d
143/tcp  open     imap     Dovecot imapd
443/tcp  open     ssl/http nginx
465/tcp  open     ssl/smtp Postfix smtpd
587/tcp  open     smtp     Postfix smtpd
993/tcp  open     ssl/imap Dovecot imapd
995/tcp  open     ssl/pop3 Dovecot pop3d
but the library only shows 'http', 'pop3'... would we cool if we could get also the "dovecot", "nginx" ... part :)
Thanks for the quick reply!

Just to give you an update, I'm working on this.  However, I'm doing a full Typescript to ES6 conversion first since my old code for this module isn't very maintainable.

@Johnhhorton any news?

@cojack Finished converting to ES6 from TypeScript on a separate branch tonight.
@bheru27  Checking out the JSON I'm getting from NMAP with OsAndPortScan, I get this kind of data:
        "protocol": "tcp",
        "portid": "10001"
    },
    "state": [
        {
            "$": {
                "state": "open",
                "reason": "syn-ack",
                "reason_ttl": "64"
            }
        }
    ],
    "service": [
        {
            "$": {
                "name": "scp-config",
                "method": "table",
                "conf": "3"
            }
        }
    ]
}```

What NMAP flags are you using for your scans in NMAP to get the additional output? I need to be able to reproduce your scan to get the desired keys to make available in the final output. If I can reproduce the data, I can have the new version out that night.

There will be breaking changes in this at the require level. I was using pretty poor practices before, so you'll just need to change how you're requiring it (I'll include the changes in the documentation). The code base still isn't great, but it's much more manageable for adding new features.

Thanks for being patient guys, work and home live have been busy this past month.

Got it:  -sV I'll have the new version up soon.

Since -sV will probe for ports and attempt to gather additional information. use
const nmap = require('./index');

let scan = new nmap.NmapScan("google.com", "-sV");

node-nmap will attempt to gather additional options returned from the port/service if they exist.
                "port": 443,
                "protocol": "tcp",
                "service": "http",
                "tunnel": "ssl",
                "method": "probed",
                "product": "ssl"
            }```

the key `product` will contain the information you're looking for. Note: if a value isn't returned, the key will not be set.

New version has been published. @cojack @bheru27

@Johnhhorton thanks :)


Fixed broken link

Wanted to do the same PR, but as it's available, I can only give a 👍  on that :)


OpenClUtils.h not found

Bug Description
cmake .. -DFL_ARRAYFIRE_USE_OPENCL=ON -DFL_USE_OPENCL=ON
make
flashlight/fl/autograd/tensor/backend/onednn/DnnlUtils.cpp:22:12: fatal error: flashlight/fl/common/OpenClUtils.h: No such file or directory
Reproduction Steps
cmake .. -DFL_ARRAYFIRE_USE_OPENCL=ON -DFL_USE_OPENCL=ON
make
flashlight/fl/autograd/tensor/backend/onednn/DnnlUtils.cpp:22:12: fatal error: flashlight/fl/common/OpenClUtils.h: No such file or directory
Platform and Hardware
[Ubuntu 20.04 focal (x86-64)]
Additional Context
[Add any additional information here]

@felixt56 — the OpenCL backend isn't supported at the moment. We're working on adding it back in the next several weeks. It should build in theory in v0.3.2 — can you try checking that version out and building?

Thanks
Maybe I'll try it next month.

Sorry, I hadn't time to check for now


Suggestion for default behavior of swap files

Hi! I've been using this configuration for quite some time and it has saved me tons of configuration work. Now I have some suggestions and hope it might help others.
By default, the swap file is disabled. This is quite unexpected and I learned it the hard way. I think this is a dangerous default behavior because the user might be unaware of this setting and lose some important work when there is terminal crash or system crash. Version control systems are for human errors while swap machanism are more relevant to unexpected failures. Maybe it would be better to change this default behavior or at least mention it in the README page.

Personally the swap file makes me annoying, but I do agree that the change is dangerous and may cause unexpected data lost (#342). It might better be an optional setting rather than a default behavior.

Agree. Disabling swap file by default is dangerous and can cause data loss.

Note that you can include your configs in the my_configs.vim Ref. I find the swap files quite annoying.


#265: Warn and error out when source and include are both used in coverage run

This addresses issue #265, and generates a warning message and errors out. Added a test to ensure that it would return a message and error.

ah, sorry the commit from issue #231 was also included in this. disregard as part of the diff.

[Current coverage][cc-pull] is 90.69%

Merging [#9][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

File ...ests/test_cmdline.py was modified. more

Misses 0
Partials 0
Hits +2

File coverage/python.py was modified. more

Misses 0
Partials 0
Hits +1

@@             master         #9   diff @@
==========================================
  Files            82         82
  Lines          9328       9335     +7
  Methods           0          0
  Messages          0          0
  Branches        991        992     +1
==========================================
+ Hits           8459       8466     +7
  Misses          693        693
  Partials        176        176

Powered by Codecov. Last updated by [8bce453...b18fc73][cc-compare]
[cc-base-branch]: https://codecov.io/gh/nedbat/coveragepy/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/nedbat/coveragepy/compare/8bce4538ba831aed7a891f8282b8faabdd78bfa2...b18fc73744b89e514527be149eb92e66547977a2
[cc-pull]: https://codecov.io/gh/nedbat/coveragepy/pull/9?src=pr

Thanks for the pull request.  PyCon sprints are amazing! :)
I think we need to also account for other styles of conflicts, like if the .coveragerc file has the include, and the command line has the source, or vice-versa.

@nland I understand if you don't want to work on it beyond the sprints. Just let me know.

This was finished differently in https://bitbucket.org/ned/coveragepy/pull-requests/105/source-and-include-are-mutually-exclusive


[Feature] Support invokeAI runtime

Describe the solution you'd like
Support invokeAI as SD runtime

Close as not planned now.


Fix issues on Esp32

Hi bros, I found some issues when I'm using esp32. It has two problems with analogWrite function and OPERATING_VOLTAGE . And now, I fixed it. Tested on Heltec LoRa Esp32.

Ok. Thank you.


add deprecation warning to koa v1 about the new v2 middleware signature

This issue is being addressed with PR #565

closed by #565


Separate C++ interface library for parameter validation.

By putting the C++ code for validators in a header and only copying the user-defined validation functions in it would make the reuse of the parameter validation methods easier and more standard.

Closed via #32


chore: Update root dev requirements

Description of changes
Updating root dev requirements. The main reason was that the version of pip-tools made it impossible to run pip-compile on any of the module requirements. Since I was upgrading that requirements, I updated the rest of them.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: d185c40c2589a3d55d50f51b6afabda3dde04d24
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: e40fd6d3dccf408d8eaf9698a435bb9ac41b6436
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 7d7ed9dd6953a93190bb62dc4191f5f9c47507ec
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 613999f1379a8add892a767e99faf0930f0bc1b4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 0858b93d8edb446f0bd9bcd997662b50d6585396
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Add passthrough option maxHeaderSize to node http.createServer()

To mitigate CVE-2018-12121 node maintainers made a breaking change in https://github.com/nodejs/node/commit/186035243fad247e3955fa0c202987cae99e82db that reduces header size from 80kb to 8kb.
To remedy the fallout from this, a feature was added in node v13.3.0 that allows the maxHeaderSize option to be passed to http.createServer().
http.createServer({
 maxHeaderSize: 8196*2
})

Koa does not currently support this.
I have created a pull request to add the maxHeaderSize option to Koa.
See also:
Limit on HTTP request headers size: #479
https://github.com/nodejs/node/issues/24731

see https://github.com/koajs/koa/pull/1428#pullrequestreview-336703571


[DOC] Correct bounds for v in RectSphereBivariateSpline

This is a fix for #6556 . I changed the SciPy documentation to reflect the actual functionality of fftpack.

@sriki18 I wonder if you're planning to continue to working on this? No pressure, just don't want it to slip into the mists of time.

Hi, Sorry I didn't catch your earlier comment. I am going to have a busy week and will have a go at it if I find the time. I should definitely find time by Friday. If you would prefer to work on it in the mean time, please let me know. Thanks!

Sounds great. No rush, just wanted to make sure you were still interested.

Working on this at the moment.

superceded by #6665


ConnectionSpec.isCompatible() and ConnectionSpec.supportedSpec()'s question

I think the goal of ConnectionSpec is let a client can manipulate a SSL socket's cipher suites and TLS versions.
But it is not like what I think when I checked the code.
What I think is:

By comparing  sslSocket.getSupportedProtocols().

if supported then enable protocols like sslSocket.setEnabledProtocols(...).

Merge the cipher suites and get intersection.

then sslSocket.setEnabledCipherSuites(...).

Right now, it is comparing sslSocket.getEnabledProtocols() in ConnectionSpec.isCompatible()
So I can not manipulate the socket as I want.
Perhaps my thought is wrong.
Can you check this?

I think you'll be better off asking questions like this on StackOverflow.


Api endpoints

Hi there! We are sending this pull request for you to review our code. Thanks in advance for your feedback!
Milestones 🎯:
📌 Work on Pair Programming
📌 Create an API endpoint to list all posts for a user.
📌 Create an API endpoint to list all comments for a user's post.
📌 Create an API endpoint to add a comment to a post.
📌 Ensure API posts JSON & GETS JSON as well
📌 Please, find below our API references

Verb
URI
body
response

GET
/users/:user_id/posts
N/A
[ { post1 } , { post2 } ]

GET
/users/:user_id/posts/:post_id/comments
N/A
[ { comment1 }, { comment2 } ]

POST
/users/:user_id/posts/:post_id/comments
{ "comment": { "text": "your comment" } }
{ comment }

🎖 General requirements:
Gitflow
No linter errors
Ensure the use of best practices and Ruby style

Hi @HFG43, @HFG43
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
I hope you're doing well. After reviewing your project, I faced an issue when trying to create the database. I consulted with a Senior Code Reviewer, and they faced the same error on their end as well.
This suggests that there might be a configuration issue or something missing in your project setup. One of the common reasons for such issues could be related to the bin folder or some specific setup configurations.
Remember, challenges like these are a part of the learning process. Keep pushing forward! 💪
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag @topeogunleye in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.

@topeogunleye Thanks for your reply, is it possible for you to share a screenshot or detail of the error?

Please, find here what was taken as error previously.

Here you will find a print screen on our side when we run the commands:

@topeogunleye Thanks for your reply, is it possible for you to share a screenshot or detail of the error? As it is the same database we have been using before

Replied on slack. ✔


port most simple headers to cats parse

well that blew up more than intended 🙈
hope this is still reviewable, let me know if I should split this up into smaller chunks

Well done! You beat me to it =)

Well done! You beat me to it =)

Great job!

Great job!


cannot hide in swift project

cannot hide

Hi! Can you please explain the issue in more details? What is your setup and what is (and isn't happening)?
If you can, a example project would be very useful too.

sorry, it's my problem in my project. I just make a new project, it work.
https://github.com/longxianlin/Demos/tree/master/AFMInfoBannerInSwift

it work in new project.
but not working in my project. I am searching the bug.

On 24 Sep, 2015, at 3:18 pm, Romans Karpelcevs<EMAIL_ADDRESS>wrote:
Hi! Can you please explain the issue in more details? What is your setup and what is (and isn't happening)?
If you can, a example project would be very useful too.
—
Reply to this email directly or view it on GitHub https://github.com/ask-fm/AFMInfoBanner/issues/6#issuecomment-142837047.


problem if system has old SXML package

Hi, in my system i dont have the most recent version of package SXML, i have synthax errors in method deserialize_id, do you know some replacement for classes sxml ?

Sorry, my bad. I didn't read the description carrefully. Close issue.


feat(reports): add anonymous reports for Wasm filter usage

Tests are based on spec/02-integration/10-go_plugins/01-reports_spec.lua.

I will merge tomorrow if you don't have perms

I don't, so please go ahead! (and send me a Kong contributor T-shirt)


Remove babel

I can't see any reason to keep using babel if you target modern Node.js versions and should simplify things a lot. Also, jest should work out of the box IIRC with import/exports.
Feel free to ping me if anyone makes a WIP branch :)

That's correct. Babel is in use because the ES2015 support was not that good in Node.js still a few years ago.
I'm fine with removing it, if it does not cause any compatibility issues that can not easily be solved.

I'm not sure how to proceed with the imports/exports. I have a WIP (broken) branch here but things will need to change.
So maybe it's time for a 4.0.0 release where we do this and the other breaking changes? BTW let me know if you have any suggestions how to solve the exports issue.

I think only the utils are left in my branch. Let me know if I should continue with this. IMO it's definitely a good move since it makes things cleaner.

Hmm... there are some things ready to review and publish, so maybe it's better to get this repository to a bit cleaner state before releasing 4.0.0. During the Christmas time could be a good moment to do it.
Removing Babel does not bring much benefit for the end user, so it should not be a high priority for now.

Yeah, sure. I just want us to get it done, especially since I've done most of the changes :)
That being said, I'd say let's get the other PRs merged and you release a new version for now.

On a side note, this isn't a development only thing. The final dist size will decrease (not a lot, but still) and there might be a slight improvement in the module load time.

Alright, I fixed all issues in my branch above minus one which I cannot figure out. Not sure how to import postcss-media-query-parser.

Fixed in the v4 branch.


Package biblatex Warning: No driver for entry type 'movie'.

Hi
This is similar to a similar issue 10 years ago:
https://sourceforge.net/p/biblatex-biber/bugs/18/
Zotero exports films as @movie and not as @film or @video and it seems biber does not have a driver for the 'movie' entry type.
I am on Overleaf so I presume the latest version of TeXLive2020. It elicits the following error after compiling:
Package biblatex Warning: No driver for entry type 'movie'. Using fallback driver on input line 53.

@movie like @video or @image is a non-standard type of biblatex, i.e. it is defined, but not implemented for the standard styles. If you want a specific output, you'll have to define your own driver.

Both @movie and @video are listed in the biblatex documentation as "non-standard types" (see §2.1.3 Non-standard Types, pp. 14-15). That means that the standard biblatex styles do not have a dedicated driver for those entry types (the idea here is that standard biblatex cannot implement all possible entry types, but the documentation lists a few possible extensions so that custom styles have a common base to work from). If an entry of that type is encountered, biblatex falls back to the fallback driver, which in the standard styles is @misc (set up with \DeclareBibliographyAlias{*}{misc}) and throws this warning. The warning, which you are free to ignore, tells you that your style does not have dedicated support for this entry type, so that you may have to expect some rough edges in the output. If you are happy with the output and just want to get rid of the warning you can try setting and explicit soft alias with \DeclareBibliographyAlias{movie}{misc}. The output will be unchanged, but the warning will be gone.
\documentclass[british]{article}
\usepackage[T1]{fontenc}
\usepackage{babel}
\usepackage{csquotes}

\usepackage[backend=biber, style=authoryear]{biblatex}

\DeclareBibliographyAlias{movie}{misc}

\begin{filecontents}{\jobname.bib}
@movie{elk,
  author    = {Anne Elk},
  title     = {A Theory on Brontosauruses},
  year      = {1972},
  publisher = {Monthy \& Co.},
  location  = {London},
}
\end{filecontents}
\addbibresource{\jobname.bib}
\addbibresource{biblatex-examples.bib}

\begin{document}
Lorem \autocite{sigfridsson,elk}

\printbibliography
\end{document}

Some custom styles like biblatex-apa or biblatex-chiago support some of the non-standard types with dedicated drivers (both of the styles support @video, but not @movie). So there you may not get a warning like this. But you should check the style documentation (and accompanying resources) for best documentation and best practices on those types. If you are using one of those styles you may want to use the entry type your style supports.
\documentclass[american]{article}
\usepackage[T1]{fontenc}
\usepackage{babel}
\usepackage{csquotes}

\usepackage[backend=biber, style=apa]{biblatex}

\DeclareSourcemap{
  \maps[datatype=bibtex]{
    \map{
      \step[typesource=movie, typetarget=video]
    }
  }
}

% the following entry is just a placeholder
% I have not checked back with the biblatex-apa docs
% for best practices for @movie or @video entries
\begin{filecontents}{\jobname.bib}
@movie{elk,
  author    = {Anne Elk},
  title     = {A Theory on Brontosauruses},
  year      = {1972},
  publisher = {Monthy \& Co.},
  location  = {London},
}
\end{filecontents}
\addbibresource{\jobname.bib}
\addbibresource{biblatex-examples.bib}

\begin{document}
Lorem \autocite{sigfridsson,elk}

\printbibliography
\end{document}

To recap: This is a style-dependent issue, since it is up to your style which entry types it wants to support. If you are using a style that supports one of the relevant entry types here, it would be best to make sure that your .bib file adheres to the documented behaviour and best practices of your style w.r.t. to the relevant types (which may mean that you have to adjust Zotero's export configurations a bit). If you insist on not meddling with your .bib file (or the export setting of your bibliography manager), the next best solution is to attempt to fix the .bib file on the fly with a Biber sourcemap (some things are easy, but not everything can be done with a Biber sourcemap).
Just for future reference, at the moment Overleaf's TeX Live 2020 uses biblatex v3.14. The current release version of biblatex is v3.16. In general Overleaf is not fully up-to-date with CTAN. A few years ago, the fact that Overleaf came with a fairly old default TeX Live was a major headache in online support forums, but recently Overleaf started updating their TeX Live more often (~once a year, so they have each TeX Live release). Still they are rarely at the cutting edge of development. Which is understandable, since they feel an obligation to give their users a stable environment. So constant updates could be tricky.


python311Packages.reolink-aio: 0.7.7 -> 0.7.8

Diff: https://github.com/starkillerOG/reolink_aio/compare/refs/tags/0.7.7...0.7.8
Changelog: https://github.com/starkillerOG/reolink_aio/releases/tag/0.7.8
Description of changes

Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.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 251147 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.reolink
python310Packages.reolink-aio
python310Packages.reolink-aio.dist
python311Packages.reolink-aio
python311Packages.reolink-aio.dist


Resizing problems!

This  shows wtf-like behaviour of terminus window on windows. It's not matter which window type I use.

Can you provide some more information like the Windows version?

I upgraded windows one day ago. Current version is 1909 (Build 18363.900)

It's strange, I just tried it on my Windows VM and I didn't experienced the same problem. Can you please open the debugger and see if there is something that is throwing strange exception while resizing?
Are you using the Terminus version downloaded from here or did you recompiled it? Maybe something related to the screen resolution?

No exceptions are raised.
I think issue #2687 is about that too.
I'll try to debug app later. Maybe I'll find the fix!

I experience similar issues after setting the background type to "fluent".  With the background set to "Blur" this behavior does not exist for me.

Agreed - setting to "blur" resolves the issue for me as well.

Duplicate of #2469, #949


Bulk Upload

Add in queuing of multiple samples, more than five

Closed and moved to https://github.com/refgenomics/mainline/issues/189.


Create Question Model

Question would be the model where queries from users would be stored . Design it using django's native orm using the models module

claim

claim

Great ! @akshatsgh , i have assigned you

This issue is open to be claimed

claim


Custom aggregators

Codecov Report
Base: 63.71% // Head: 63.72% // Increases project coverage by +0.00% :tada:

Coverage data is based on head (1a4f69a) compared to base (b94491d).
Patch coverage: 90.12% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##             latest      #27   +/-   ##
=========================================
  Coverage     63.71%   63.72%
+ Complexity     2213     2210    -3
=========================================
  Files           253      254    +1
  Lines         15689    15712   +23
  Branches       2485     2494    +9
=========================================
+ Hits           9997    10013   +16
- Misses         4892     4896    +4
- Partials        800      803    +3

Impacted Files
Coverage Δ

.../strategy/aggregators/ConcatAggregateFunction.java
84.21% <0.00%> (ø)

.../strategy/aggregators/SampleAggregateFunction.java
85.71% <ø> (ø)

...n/halyard/strategy/HalyardTupleExprEvaluation.java
75.55% <87.93%> (+0.33%)
:arrow_up:

...alyard/strategy/aggregators/AggregateFunction.java
69.23% <100.00%> (ø)

...ard/strategy/aggregators/AvgAggregateFunction.java
84.61% <100.00%> (ø)

...d/strategy/aggregators/CountAggregateFunction.java
100.00% <100.00%> (ø)

...ard/strategy/aggregators/MaxAggregateFunction.java
100.00% <100.00%> (ø)

...ard/strategy/aggregators/MinAggregateFunction.java
100.00% <100.00%> (ø)

...ard/strategy/aggregators/SumAggregateFunction.java
95.00% <100.00%> (ø)

...gy/aggregators/WildcardCountAggregateFunction.java
100.00% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Inconsistency in this approach

I think there's an oversight in this approach, which prevents the syncing from being consistent, as it currently is.
To reproduce in https://yfs.vercel.app:

Start with the document "a".
Wait for it to sync to the local file.
Insert a "b" after the a in the local file.

The resulting document is "cba", not "cab", as intended.

This is because the Y.js delta is "insert a 'b' at position 2". When that's applied to the document, the document is already "ca", and the syncing can't determine that the "b" should actually go after the "a".
Can you reproduce this issue? I wonder what a good way of fixing that behaviour would be. Somehow tying deeper into the CRDT algorithm, to remember where in time the the delta should be applied - on top of which CRDT state?

Hi @blinry thanks for this. Indeed, this is a known issue, due to the fact that at some point, we need to compute a diff, which brings us "out of CRDT land". I think the proper way to do this is to store the CRDT in the file system, and commit locally to it, and then sync the browser and file system CRDTs regularly.