CMYK images converted to RGB

Steps to reproduce
Tell us about your environment:

Puppeteer version: 5.3.1
Platform / OS version: macOS 10.15.7
URLs (if applicable):
Node.js version: 12.16.1

What steps will reproduce the problem?
Please include code that reproduces the issue.
// give puppeteer access to file
const express = require('express')
const app = express()
app.use(express.static(__dirname))
app.listen(3000)

// generate pdf
const puppeteer = require('puppeteer')
const html = `
<html>
    <body>
        <img src="http://localhost:3000/Channel_digital_image_CMYK_color.jpg">
    </body>
</html>`
;(async () => {
    const browser = await puppeteer.launch()
    const page = await browser.newPage()
    await page.setContent(html)
    await page.pdf({ path: 'output.pdf' });
    console.log('done')
})()

Here is the CMYK image I used: https://upload.wikimedia.org/wikipedia/en/2/25/Channel_digital_image_CMYK_color.jpg
What is the expected result?
If I extract the image from the resulting pdf, it will remain in CMYK format.
What happens instead?
The image is converted to RGB, causing the PDF colors to be wrong when printed.

I am also facing this problem

I am also facing this problem

Me too, we also need PDFs with CMYK colors for printing

Me too, we also need PDFs with CMYK colors for printing

now I'm using Ghostscript to convert pdf RGB to CMYK for printing

Me too, we also need PDFs with CMYK colors for printing

now I'm using Ghostscript to convert pdf RGB to CMYK for printing

Are you generating a pdf with puppeteer and and then running it through Ghostscript afterwards? The image will technically be CMYK, but they will not match the colors of the CMYK image in the initial HTML file.

At the moment we are pre-calculating the RGB values using the same ICC color profile as our print-service and only use this RGB colors in our application.

Are you generating a pdf with puppeteer and and then running it through Ghostscript afterwards? The image will technically be CMYK, but they will not match the colors of the CMYK image in the initial HTML file.

We also tried Ghostscript but as you say it will not be the same as the original picture and it is very slow.

Have you tried specifying -webkit-print-color-adjust:exact ?

Due to the color systems lab and lch are becoming more GA in web standards, the support for exporting alternative color systems as cmyk and lab shall be able to get exported in Chrome and Puppeteer rather than close on inactivity.

Would like to see this issue re-opened.  I'm also experiencing this, and have confirmed that the image linked in the initial ticket has been converted to RGB when inserted into a pdf via puppeteer as in the example code.
Or has this functionality been added and there's a flag one needs to specify to preserve CMYK format?

Due to the color systems lab and lch are becoming more GA in web standards, the support for exporting alternative color systems as cmyk and lab shall be able to get exported in Chrome and Puppeteer rather than close on inactivity.

I am also in need for this. What is a good alternative solution to this? Need to generate PDF to CMYK spec

Cmyk space is limited comparing to rgb. Isnt this good approach to convert all rgb images and rgb colors to safe rgb that will easily convert to cmyk versions?

If the image is originally created as cmyk then converting it to rgb to convert it to cmyk again while printing will affect color appearance of the print. But if you are capable of defining colors cmyk or even better lab* or lch, the right color tone will be used.


Overlaps without CollisionBody

Problem:
The current implementation of testOverlap and testCollision require a CollisionBody* argument. This means that currently, in order to get all collision objects in some area we're required to make a new collision body and get callbacks through this.
Example (current):
Here's an example of one of our utilities.
static void entitiesInShape(base::PhysicsWorld* world, vec3 pos, rp3d::CollisionShape* shape, std::function<void(entt::entity)> func) {
		rp3d::Transform shapePose(convert(pos), rp3d::Quaternion::identity());

		rp3d::CollisionBody* body = world->getWorld()->createCollisionBody(shapePose);
		body->addCollider(shape, rp3d::Transform::identity());

		MyOverlapCallbackAll callback;
		callback.callback = std::move(func);

		world->getWorld()->testOverlap(body, callback);

		// Cleanup
		world->getWorld()->destroyCollisionBody(body);
	}

Overlaps are a very commonly used mechanic in games and performance is quite important on them.
I've dug through the code a bit to see if it'd be easy to provide some functions that only take a shape or specialized functions like testOverlapSphere(position, callback) or testOverlapSphere(position, List&), but it seems most of the internal structure is really geared towards batch processing and CollisionBodies.
Suggestion usage
world->getWorld()->testOverlap(position, shape, callback);

// OR
world->getWorld()->testOverlapSphere(position, callback);

// OR (preferred)
rp3d::List<rp3d::Entity> overlapping(world->getMemoryManager().getSingleFrameAllocator(), 32);
world->getWorld()->testOverlapSphere(position, overlapping);

// Process overlapping here...

The benefit of using a reference to a list in which overlaps are written is that there are some easy C++ optimizations we can make use of. Instead of having to pass around a std::function (which can allocate), we can just inline the function at the call site through templates.
template <typename Func>
static void entitiesInSphere(rp3d::PhysicsWorld* world, const Vector3& pos, float radius, Func func) {
    rp3d::List<rp3d::Entity> overlapping(world->getMemoryManager().getSingleFrameAllocator(), 32);
    world->getWorld()->testOverlapSphere(pos, radius, overlapping);

    for(rp3d::Entity e : overlapping) {
        func(e); // Gets inlined
    }
}

Thoughts? I may have the time to implement this in the near future; some suggestions would be appreciated.

Thanks a lot for your feedback. Yes, it would be a good idea to have a testOverlap() method where you can simply pass a collision shape and not a whole body.
I will need to check if I can add the following method:
PhysicsWorld::testOverlap(collisionShape, transform, callback)
Note that we need to use a transform here (position and rotation).
I don't really know if I will have the time to add this in the next release (v0.9.0). I will let you know here when this is implemented.

@DanielChappuis any updates yet? Maybe somewhere in preview version?

Hello. Sorry but this is not implemented yet.


fix(tar): fix readme and package.json

fix https://github.com/asgardeo/asgardeo-react-native-oidc-sdk/issues/12
fix https://github.com/asgardeo/asgardeo-react-native-oidc-sdk/issues/13

@daniloab Thanks for the contribution!


Update README.md

Added BiometricAuth Framework to Security
Project URL
https://github.com/vasilenkoigor/BiometricAuth
Description
Framework for biometric authentication (via TouchID) in your application
Framework features:

[x] Force failure authentication if was added the new fingerprint to the device. This feature for security considerations.
[x] Saving features list that needs authentication via TouchID

Why it should be included to awesome-ios (optional)
Checklist

[x] Addition in chronological order (bottom of category)
[x] Supports iOS 9 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

:no_entry_sign:
Found 1 link issue

          1 Warning

:warning:
Please update the Pull Request title to contain the library name

Link issue by awesome_bot

Line
Status
Link

2257
301
http://www.ioscreator.com/ redirects tohttps://www.ioscreator.com/

  Generated by :no_entry_sign: danger

Fixed CI issues

@victorgama Fixed :)

Thank you! 🙌


line 58

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

look at line 58 there is some mistakes

LGTM

Congrats @gourabk121 on your first pull request (PR)! 🎉
Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Simplify the code in the RegisterSubnet method of ipallocator.

Thank you for cleaning up this.
LGTM

@junxu the CircleCI tests failed, but not reporting the error (It is NOT due to your fix). We had resolved the failure recently. Can you please rebase your changes and push it again so that we can let the circle-ci succeed ?

@mavenugo I have done the rebase, please check again, thanks!

Thanks @junxu LGTM.


Sort manufacturers from elasticsearch

Thanks to this pull request display of the manufacturers facet with ES backend should be consistent with the DBAL one.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-14770.
Please use this issue to track the state of your pull request.

Good catch. I've scheduled your PR to be included in one of the next sprints.

Thank you @xrogers, this was merged with commit https://github.com/shopware/shopware/commit/778b8f00211.


Frozen experiment execution

Hi, I am using Kubernetes Glue to run my experiments regularly. However I am facing an issue where experiment never gets completed. For successful execution it shows "Process completed successfully" but when it's frozen, this line never get displayed. I guess it's freezing somewhere internally although it is saying "Updated a few seconds ago". This happens once a week and I have to manually abort my experiment. Please let me know how to fix it.

Hi @KuldipN, I assume you're talking about the task log? If the pod is still running, you should be able to exec into it and find the agent's internal log file in the /tmp folder - perhaps it will reveal something...


chore: add [Conditional] tag in fields comments

Explicit indication that field is optional is better then implicit

func optionalField(s structDef, f fieldDef) bool {
	switch {
	case f.Conditional:
		return true
	case f.Type == "string" && f.Name == "ThumbSize":
		return s.RawName == "inputDocumentFileLocation"
	}

	return false
}

This change is not equivalent. I prefer to leave it as is until there is a significant reason to change this.


terraform-docs indent arg usage

Hi,
First and foremost, this is working absolutely great for us. So thank you for creating the TF hooks.
Really need some help here with terraform_docs hook. I would like to use the indent flag when generating the docs. I tried using
...
- id: terraform_docs
   args: ['--indent=3']
...

However it seems not correct as I get an error that the option is not recognized. I am sure there is a way, I am just not so good with bash. Some help here would be greatly appreciated.

Hi @siddmoitra !
You should write it like this, for example:
    - id: terraform_docs
      args: ['--args=--indent 3 --no-requirements']

Thank you. 👍


Geckodriver firefox issues

Issues getting gekodriver to work to allow selenium webdriver to control firefox-ESR
Webdriver Exception: Connection Refused

As I was testing on Debian, I don't know whether using Raspbian will fix the problem

Trying to move over to chrome, which would eliminate this issue


nvim-compe feels slower than coc.nvim

Checkhealth
health#compe#check
========================================================================
## compe:snippet
  - INFO: snippet engine is not detected.

## compe:mapping
  - INFO: `compe#complete` is not mapped
  - INFO: `compe#confirm` is not mapped
  - INFO: `compe#close` is not mapped
  - INFO: `compe#scroll` is not mapped

Describe the bug
There seems to be a delay when filtering results. Maybe it waits for the lsp servers to return completions? I think coc.nvim filters the cached completions.
I tried lowering both the throttle time and debounce text changes, but that does not seem to help.
To Reproduce
Type one letter after a triggerCharacter, you will see a delay in completion filtering.
Actual behavior
A slight delay (50ms?).
Expected behavior
No delay, like in coc.nvim
Screenshots (optional)
coc.nvim

compe

Additional context (optional)
Thanks a lot for all the hard work that went into this plugin!

OK. Thank you. I will check it.

have you tried setting incomplete_delay and throttle_time to 0? works fine for me
https://user-images.githubusercontent.com/51877647/127785581-bc4445ba-db79-4ad9-b645-329e6738933a.mp4

Hi @elianiva, yes I tried that. Sadly, the delay stays. It's more pronounced after a trigger-character (like '.'). Maybe the lsp I use is slower (jedi-language-server)? However, compe could circumvent asking the lsp for competitions when filtering down (i.e., if you have all completions of 'test.' you don't need to request them for 'test.r'), however maybe compe already does this?

I had some capability overwrites or pyright (to disable signature/completion), I removed those, and the delay only happens sometimes now. So it seems like there is a roundtrip to the lsp when filtering down existing completions.

right, my comparison isn't that fair, I should try with the same lang server


Is it possible to detect specific info of the device like mac address ?

I was wondering if it's possible to add attribute like mac address or anything so I can identify if the user already connected with this device or is it a new one ?

this probably wont come through (check for example: https://stackoverflow.com/questions/5074139/how-to-get-mac-address-of-client-using-php )


Improving address DB

Hi, is there anyway we can add more address data?

import address to addresses-us-all.min.json


[Changelog] Update for Ivanchuk Beta2

[skip ci]

@miq-bot add_label documentation

@miq-bot add_label ivanchuk/yes

@carbonin as time permits can you review/merge.

Ivanchuk backport details:
$ git log -1
commit 729701600f5c3abf0490ad18a70188771de83f6c
Author: Nick Carboni<EMAIL_ADDRESS>Date:   Thu Aug 8 09:36:43 2019 -0400

    Merge pull request #19115 from JPrause/ivanb2_cl

    [Changelog] Update for Ivanchuk Beta2

    (cherry picked from commit 49e7db670d43dd06a6eabd6b7374851a20b4aece)


ExpressJS using very out-of-date version of path-to-regexp

In expressjs package.json the version of "path-to-regexp" listed in dependencies is "0.1.7".
This is considerably out-of-date with the the version of "path-to-regexp" in "pillarjs" which is "1.7.0".
Pulling the current "pillarjs" version of "path-to-regexp" into expressjs by upping the version number to
"1.7.0" in expressjs's package.json causes at least one of the expressjs tests to fail (no surprise I guess).
node_modules/path-to-regexp/index.js:394
  return attachKeys(new RegExp('^' + route, flags(options)), keys)
                    ^

SyntaxError: Invalid regular expression: /^\/files\/((?:*))(?:\/(?=$))?$/: Nothing to repeat
    at RegExp (native)

Is there any reason why expressjs is still using the "0.1.7" version of "path-to-regexp" and/or can this
out-of-date version issue be remedied?
Thanks for comments/help, Justin Johansson

Hi @indiescripter the upgrade is not backwards-compatible, so it cannot be upgraded until Express 5.0. We are tacking this in numerous issues like #2237 #2057 #2173
I hope this helps!

Ok, understand. Thanks for quick response @dougwilson.

No problem! The 0.1.x still receives fixes if necessary, so if you're experiencing a bug in that version, let us know and we can get a fix included :)


Support amp level in validation

Thank you for your contribution to the MindCV repo.
Before submitting this PR, please make sure:

[x] You have read the Contributing Guidelines on pull requests
[x] Your code builds clean without any errors or warnings
[x] You are using approved terminology
[ ] You have added unit tests

Motivation
目前 validate.py 跑 Transformer类网络超慢（910, >半小时），比训练一轮的时间都要长，原因在于transformer训练是混合精度，边训边验也是，但validate却只能是O0。
现改为validate也根据yaml脚本的amp_level来配置混合精度，也方便与边训边验的结果的同步。
Test Plan
测试visformer，改成O2 评估后，约在10分钟内完成，未改前超半小时。validate出来的精度跟readme中一致。
Related Issues and PRs
(Is this PR part of a group of changes? Link the other relevant PRs and Issues here. Use https://help.github.com/en/articles/closing-issues-using-keywords for help on GitHub syntax)

duplicate of #676


install script breaks

npx create-react-native-web-app myApp

@Damoness Hi,
A few details about your system would help, for example, is it windows, linux?
It might be a permission problem and you might want to run it with sudo like this:
sudo npx create-react-native-web-app myApp
if that doesn't work please try to install the package globally and then to run the command
like this:
npm i -g create-react-native-web-app
create-react-native-web-app myApp
Hope it helps :)

@Damoness Hi,
A few details about your system would help, for example, is it windows, linux?
It might be a permission problem and you might want to run it with sudo like this:
sudo npx create-react-native-web-app myApp
if that doesn't work please try to install the package globally and then to run the command
like this:
npm i -g create-react-native-web-app
create-react-native-web-app myApp
Hope it helps :)

My system is macOS 10.13.6
The same error

Hi @haruelrovix & @Damoness ,
please check if you still have issues with the new version 0.1.8 :)
thanks for notifying me about the bug

@orYoffe seems I still got the error 🤔

Install 0.1.8

➜  Projects npm i -g create-react-native-web-app@latest
/Users/haruelrovix/.nvm/versions/node/v10.13.0/bin/create-react-native-web-app -> /Users/haruelrovix/.nvm/versions/node/v10.13.0/lib/node_modules/create-react-native-web-app/cli.js
+<EMAIL_ADDRESS>updated 1 package in 5.073s

bootstrap a project

➜  Projects create-react-native-web-app g1tphone
      ⏳ Creating React Native Web App by the name of g1tphone ...

      ✅ Created project folder.

      ✅ Added project files.

      ⏳ Installing project dependencies...

yarn install v1.12.3
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error https://registry.yarnpkg.com/har-validator/-/har-validator-5.1.2.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "Unexpected end of data"
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
child_process.js:651
    throw err;
    ^

Error: Command failed: cd g1tphone && yarn
    at checkExecSyncError (child_process.js:611:11)
    at execSync (child_process.js:648:13)
    at Object.<anonymous> (/Users/haruelrovix/.nvm/versions/node/v10.13.0/lib/node_modules/create-react-native-web-app/cli.js:79:3)
    at Module._compile (internal/modules/cjs/loader.js:688:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
    at Module.load (internal/modules/cjs/loader.js:598:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
    at Function.Module._load (internal/modules/cjs/loader.js:529:3)
    at Function.Module.runMain (internal/modules/cjs/loader.js:741:12)
    at startup (internal/bootstrap/node.js:285:19)

@orYoffe it's not an issue with CRNWA but yarn (?)
What I did:

Go to the project$ cd g1tphone

Remove yarn.lock$ rm yarn.lock

Run yarn again$ yarn

Result:
➜  g1tphone yarn
yarn install v1.12.3
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning eslint > file-entry-cache > flat-cache ><EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
warning jest > jest-cli > prompts ><EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 73.71s.

🎉
References:

Error on install 404 on har-validator-5.1.2.tgz, source
Extracting the tar content of undefined failed, here

@haruelrovix please try the new release v0.1.9
https://github.com/VISI-ONE/create-react-native-web-app/releases/tag/0.1.9

@orYoffe YOU. ARE. AWESOME!
➜  Projects npm i -g create-react-native-web-app@latest
/Users/haruelrovix/.nvm/versions/node/v10.13.0/bin/create-react-native-web-app -> /Users/haruelrovix/.nvm/versions/node/v10.13.0/lib/node_modules/create-react-native-web-app/cli.js
+<EMAIL_ADDRESS>updated 1 package in 6.742s

➜  Projects create-react-native-web-app g1thub
      ⏳ Creating React Native Web App by the name of g1thub ...

      ✅ Created project folder.

      ✅ Added project files.

      ⏳ Installing project dependencies...

yarn install v1.12.3
info No lockfile found.
[1/4] 🔍  Resolving packages...
warning eslint > file-entry-cache > flat-cache ><EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
warning jest > jest-cli > prompts ><EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit <https://github.com/lukeed/kleur/releases/tag/v3.0.0\> for migration path(s).
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 📃  Building fresh packages...
success Saved lockfile.
✨  Done in 122.75s.
      ✅ Installed project dependencies.

      ✅ Done! 😁👍 Your project is ready for development.

        * change directory to your new project
        $ cd g1thub

        $ Then run the these commands to get started:

        * To run development Web server
        $ yarn web

        * To run Android on connected device (after installing Android Debug Bridge "adb" - https://developer.android.com/studio/releases/platform-tools)
        $ yarn android

        * To run ios simulator (after installing Xcode - only on Apple devices)
        $ yarn ios

        * To run tests for Native and Web
        $ yarn test

        * To run build for Web
        $ yarn build

👏


access log: support filter state objects

Description:
Adds serialization method to filter state and use from logger if specified.
Risk Level: Low
Testing: CI
Docs Changes: Added
Release Notes: Will add
Fixes #8790
Signed-off-by: Lizan Zhou<EMAIL_ADDRESS>

@envoyproxy/api-shepherds ping

@htuch gentle ping, I'm blocked on this one to make WasmState serializable.

/azp run envoy-linux

@htuch can you approve again? resolved conflicts on version_history.rst because we're in new version.

/azp run envoy-linux

/azp run envoy-macos


Top Legend of the charts always placed on right

Bug description
Legend of the charts always placed on Top right, It would be great to keep, Top middle or left
How to reproduce the bug
Create a chart (line, bar.....)
Select values for x-axis and y-axis
Select Legend option on customise tab
Try to bring the legend to centre
Keep only the values, remove or keep
Screenshots/recordings
https://github.com/apache/superset/assets/55632570/6a09fc34-d447-47c0-bc77-8a297ea46b5d
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Have you checked ECharts to see if they support this? I assume so. It would just be adding an extra "dynamic control" for Left/Center/Right when the Top or Bottom choices are selected. As long as the defaults for the new control match the current situation, it doesn't seem like anyone ought to mind.

This is more of a feature request than a bug though, so I'll convert it to a Discussion.


[Accessibility]Need a way to set the arial label of task module

As task module is a dialog. It need accessible name.
Or it will cause a11y issue:

@qjkobe -Could you please elaborate more on this?


Add support to MD051 for Gitiles section anchors and named anchors

Would it be possible to add a configuration option for MD051 to support section anchors as defined by Gitiles markdown?  I believe they pretty much follow the same convention as GitHub but they keep the case of each character rather than forcing them to lowercase.
It would also be nice if their named anchors could be supported, e.g.:
## Some Section {#name}

...

## Other Section

See [some section](#name)

As I understand the specification you link to, there are a few differences:

Translation of header text is different, notably for accented characters.
Nested headings generate unique identifiers based on structure
Curly bracket syntax can appear anywhere in the file

None of this is unreasonable, but overall it represents more than a trivial tweak to the logic of the existing rule.

+1 for adding support to custom header ids. They are supported in a number of static site generators (for example, Hugo and docusaurus), and in these contexts this markdownlint rule throws a  false positive.

I'm very interested in just the second part of this request, so that MD051 will not flag this as an invalid link:
## Some Section {#name}

See [some section](#name)

Currently, I need to disable MD051 (and use a separate linkchecker) because this use-case is important to me.
Should this be filed as a separate enhancement request?

Done: https://github.com/DavidAnson/markdownlint/issues/830

+1 for adding support for gitiles flavored anchors.
My company uses gerrit with gitiles for all development, and uses markdownlint in all CI pipelines. And broken links slips through from time to time because MD051 needs to be disabled.


update rack to squash a cve

I rule and have completed some work on Case Manager that's ready for review!
Rack has an open CVE, so fix er up.
This pull request makes the following changes:

bundle update rack

no view changes
no issues
For reviewer:

Adjust the title to explain what it does for the notification email to the listserv.
Tag this PR:

feature if it contains a feature, fix, or similar. This is anything that contains a user-facing fix in some way, such as frontend changes, alterations to backend behavior, or bug fixes.
dependencies if it contains library upgrades or similar. This is anything that upgrades any dependency, such as a Gemfile update or npm package upgrade.

If it contains neither, no need to tag this PR.

godmode since cve


why box_xy in a normalization model should minus the offset between the recovery image shape and compress origin image?

This is a issue when I read the definition of yolo_head and yolo_correct_boxes in the model.py. In previous, the function of the box_xy:
box_xy = (K.sigmoid(feats[..., :2]) + grid) / K.cast(grid_shape[::-1], K.dtype(feats))
the devide by grid_shape make the value to be normalization in the feature map. But after it in the yolo_correct_boxes, box_yx = (box_yx - offset) * scale (new_shape = K.round(image_shape * K.min(input_shape/image_shape)); offset = (input_shape-new_shape)/2./input_shape; scale = input_shape/new_shape). My question is why box_yx need the offset and scale multiply.

i have the same question ? dou you slove it?

@QuntuamLoop Hi, have you figured it out?

check this
hope you two can understand chinese
@xuannianz @QuntuamLoop


Value cannot be null. (Parameter 'responseStream') in DefaultResponseFactory.CreateCoreAsync

Elastic.Clients.Elasticsearch version: 8.16.0
Elasticsearch version: 8.15.3
.NET runtime version: 9.x
Operating system version: Linux (docker)

We migrated from elastic 6.8 to 8 recently and now we are getting some weird errors randomly.

Value cannot be null. (Parameter 'responseStream')

Stack trace :
Elastic.Transport.UnexpectedTransportException: Value cannot be null. (Parameter 'responseStream')
 ---> System.ArgumentNullException: Value cannot be null. (Parameter 'responseStream')
   at Elastic.Transport.DefaultResponseFactory.CreateCoreAsync[TResponse](Boolean isAsync, Endpoint endpoint, RequestData requestData, PostData postData, Exception ex, Nullable`1 statusCode, Dictionary`2 headers, Stream responseStream, String contentType, Int64 contentLength, IReadOnlyDictionary`2 threadPoolStats, IReadOnlyDictionary`2 tcpStats, CancellationToken cancellationToken)
   at Elastic.Transport.HttpRequestInvoker.RequestCoreAsync[TResponse](Boolean isAsync, Endpoint endpoint, RequestData requestData, PostData postData, CancellationToken cancellationToken)
   at Elastic.Transport.RequestPipeline.CallProductEndpointCoreAsync[TResponse](Boolean isAsync, Endpoint endpoint, RequestData requestData, PostData postData, Auditor auditor, CancellationToken cancellationToken)
   at Elastic.Transport.DistributedTransport`1.RequestCoreAsync[TResponse](Boolean isAsync, EndpointPath path, PostData data, OpenTelemetryData openTelemetryData, IRequestConfiguration localConfiguration, CancellationToken cancellationToken)
   --- End of inner exception stack trace ---
   at Elastic.Transport.DistributedTransport`1.RequestCoreAsync[TResponse](Boolean isAsync, EndpointPath path, PostData data, OpenTelemetryData openTelemetryData, IRequestConfiguration localConfiguration, CancellationToken cancellationToken)

Most of the time it seem to happen on ClearScrollAsync. But some time it happen also on SearchAsync.
We recently created a custom IRequestInvoker that wrap the default one to add some polly retry to fix connection reset by peer. But we are not sure if it's a good idea to include the ArgumentNullException in the retry policy. Any advice would be welcomed.
I don't really know what else to add in the ticket as we are not able to reproduce it on demand.

Just found that Elastic.Clients.Elasticsearch 8.16.3 include the ElasticTransport fix. I'll try that.

@latop2604 Let us know if the 8.16.3 version solves your issue 🙂


Protocol layer - pTokens for Reviewers

Job to be Done
As a Sponsor, when launching a Challenge I want the ability to define a pToken payout amount for reviewers, so that I can flexibly incentivize peer review for my Challenge, and optimize my budgets and incentives in a way that best suits me
Requirements
Sponsors must set a reviewer pToken and amount and fund them when launching a Challenge

Resolved in pending commit -- Will return with documentation and links.


Remove duplicated version.archetype.plugin property

The same file kogito-build-parent/pom.xml contained the same property twice.

The Linux check has failed. Please check the logs.

Jenkins please retest this

The Linux check has failed. Please check the logs.

11:14:11,714 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project process-optaplanner-springboot: There are test failures.

11:14:11,714 [ERROR]

11:14:11,714 [ERROR] Please refer to /home/jenkins/workspace/KIE/kogito/pullrequest/kogito-runtimes/kogito-examples/process-optaplanner-springboot/target/surefire-reports for the individual test results.

Jenkins please retest this

The Linux check has failed. Please check the logs.

Jenkins please retest this

The Linux check is successful.

@danielezonca could we please merge?


add support for ColumnConfig skipValueRangeIndexScale and skipValueRangeIndexScale to traditional string columns

Description
Adds the enhancements from #13977 to traditional string columns to improve performance of filter processing by allowing obviously expensive bitmap operations to be skipped. While I haven't run the benchmarks, I assume a similar improvement for string columns that are not created with the 'auto' indexer as were seen in #13977. Previously this performance enhancement was only available for 'auto' and 'json' columns.
This is related to #15550 to help replace the 'auto' search strategy.
I've not documented the configs behind this yet in this PR because I'm still thinking on how to frame what these configs do in an understandable manner without requiring deep knowledge of how query processing actually works. For the most part these settings should probably not be tweaked by users, but will try to think of something and add docs in a follow-up PR.
Release note
String columns created with the 'string' column indexer now have an enhancement for filter match processing that was previously only available to columns created by the 'auto' indexer, and will automatically skip obviously expensive index computation for filters which would require a very large number of bitmap operations. This should improve performance, particularly when filter clauses contain a mix of simple and complex filters since it allows the complex filters. Previously Druid would always utilize indexes if they were available, and this behavior can be returned by setting druid.processing.skipValuePredicateIndexScale and druid.processing.skipValueRangeIndexScale to 1.0.

This PR has:

[x] been self-reviewed.
[ ] added documentation for new or modified features or behaviors.
[x] a release note entry in the PR description.
[x] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[x] been tested in a test Druid cluster.

replaced by #15838


Repeated word in Docs

Link to the Page
https://www.skeleton.dev/utilities/modals
Describe the Issue (screenshots encouraged!)
Your is repeated twice in the same sentence! ctrl + f  = "your your"

This one was already resolved before the ticket was created, so I'm going to close this. The change should already be live!


EOFError: Ran out of input

Hi Philipp,
First of all, thanks for the excellent work!
I have encountered an "EOFError: Ran out of input" when running the command "run_multi_cam_clustering.py  --config configs/clustering_configs/mta_es_abd_non_clean.py". This error was raised when calculating the pickled person_id_tracks. Below is the error message:
`Did not find pickled person_id_tracks. Calculating them now.
36%|███▋      | 423/1165 [00:29<02:17,  5.40it/s]Ran out of input
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/home/lxfhfut/anaconda3/envs/wda/lib/python3.7/multiprocessing/pool.py", line 121, in worker
result = (True, func(*args, **kwds))
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 1413, in cluster_from_weights_task
, dataset_type=dataset_type
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 1113, in cluster_from_weights
,dataset_type=dataset_type)
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 818, in cluster_tracks_via_hierarchical
self.get_all_tracks_with_feature_mean(track_results_folder,dataset_type)
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 239, in get_all_tracks_with_feature_mean
, dataset_type=dataset_type)
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 280, in calculate_track_feature_mean
feature_dict = pickle.load(handle)
EOFError: Ran out of input
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/run_multi_cam_clustering.py", line 108, in
run_clustering.run()
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/run_multi_cam_clustering.py", line 84, in run
, n_split_parts=self.cfg.cluster_from_weights.split_count
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 1377, in splitted_clustering_from_weights
eval_results = get_async_tracking_results(eval_results)
File "/home/lxfhfut/Dropbox/PyCharm/wda_tracker/clustering/multi_cam_clustering.py", line 1277, in get_async_tracking_results
result = result.get()
File "/home/lxfhfut/anaconda3/envs/wda/lib/python3.7/multiprocessing/pool.py", line 657, in get
raise self._value
EOFError: Ran out of input
`
I checked the '*/work_dirs/clustering/config_runs/mta_es_abd_non_clean/person_id_tracks' folder, nothing was generated.
Would you kindly help with this issue? Please let me know if you need further information to resolve the error. Thank you!

Hi,
did you set up mmdetection?

Hi,
did you set up mmdetection?

I think mmdetection has been set up properly because I successfully run the single camera tracker, which calls the person doctor in mmdetection.

And did you also change all necessary paths in mta_es_abd_non_clean.py? I could provide you my config_runs/mta_es_abd_non_clean if required.

And did you also change all necessary paths in mta_es_abd_non_clean.py? I could provide you my config_runs/mta_es_abd_non_clean if required.

Thanks for your reply! I only worked on the 'MTA_ext_short' set coz running on the full-length videos is time-consuming.  I did change the config_runs/mta_es_abd_non_clean. Above is the screenshot, where

work_dirs: I set it to the path to the 'work_dirs' folder I downloaded from the provided link of google drive.
train_track_results_folder: I set it to the path of the single-camera tracking results on the training set of 'MTA_ext_short'.
test_track_results_folder: I set it to the path of the single-camera tracking results on the test set of 'MTA_ext_short'.
train_dataset_folder: I set it to the path of the training set of 'MTA_ext_short'.
test_dataset_folder: I set it to the path of the test set of 'MTA_ext_short'.

The single-camera tracking works well (see above the screenshot of the generated single-camera tracking results) and I am able to run the evaluation on the results of single-camera tracking. I can also confirm that the 'reid_strong_baseline_config' and 'checkpoint_file' exist.
It would be most helpful if you could advise if the settings in config_runs/mta_es_abd_non_clean are correct or not. Thank you.

It seems correct. Maybe some files in config_runs/mta_es_abd_non_clean are empty and you have to remove them and then you have to run the clustering again. I also tried to run it again and it seemed to work. Here is my folder:
https://studentkit-my.sharepoint.com/:u:/g/personal/utcyi_student_kit_edu/EdpWWQ93c-RFnlrmWFWQ2csBRF6iaswKMVmbGc0aq0BlBg?e=ZcqhLM

It seems correct. Maybe some files in config_runs/mta_es_abd_non_clean are empty and you have to remove them and then you have to run the clustering again. I also tried to run it again and it seemed to work. Here is my folder:
https://studentkit-my.sharepoint.com/:u:/g/personal/utcyi_student_kit_edu/EdpWWQ93c-RFnlrmWFWQ2csBRF6iaswKMVmbGc0aq0BlBg?e=ZcqhLM

Hi Phillip,
The issue has been resolved by removing the config_runs/mta_es_abd_non_clean folder and running the clustering again. Thank you so much for your help!

Your're welcome!


Add Gitter for composer/transporter

This is a simple suggestion to add a gitter room for transporter. I would like to collaborate with others that are developing more complex pipelines and realize Github issues are not the place to do it.
https://gitter.im

:+1: been meaning to set this up for a while now

fixed via https://github.com/compose/transporter/commit/7806cecf6aa46040f43963adbc7554386769a8ad


size mismatch with MCS on chiral molecules

An error is given when using MCS to these two chiral molecules. This is with the latest master.
from rdkit import Chem
from rdkit.Chem import rdFMCS

node_mol = Chem.MolFromSmiles("CCN(CC)C(=O)[C@@]1(c2ccccc2)C[C@H]1CN")
lig_mol = Chem.MolFromSmiles("CCN(CC)C(=O)[C@]1(c2ccccc2)C[C@H]1CN")
mcs = rdFMCS.FindMCS([node_mol, lig_mol],
                     matchChiralTag=False)
print mcs.smartsString
# [#6]-[#6]-[#7](-[#6]-[#6])-[#6](=[#8])-[#6]1(-[#6]2:[#6]:[#6]:[#6]:[#6]:[#6]:2)-[#6]-[#6]-1-[#6]-[#7]
mcs = rdFMCS.FindMCS([node_mol, lig_mol],
                     matchChiralTag=True)

# ****
# Pre-condition Violation
# size mismatch
# Violation occurred on line 51 in file /scr/kaus/src/bin/rdkit/Code/RDGeneral/utils.h
# Failed Expression: ref.size()==probe.size()
# ****

# Traceback (most recent call last):
#   File "chiral.py", line 12, in <module>
#     matchChiralTag=True)
# RuntimeError: Pre-condition Violation

This no longer traces back (2024.09pre):


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1341 ms

Resolved: Bofrost.at performance has improved in 5d400ff after 39 minutes.


What is I wish to generate the mesh with multiple images ? - I have front view, left view, right view and back view of a chair - how can I create a mesh utilising all these images ?

Cam this model be modified to support Multiple ground truth consistent input from the user?

do you know which coordinate system they are using?
as a test: i tried inputting screenshots from 6 images from a 3D model in the 360%6 azimuth and also 20 and -10 deg elevations, but the results are kinda crap.

Curious - can you share your generated results from that?

yes but the generated result do not look good! i tried your input and got this!

okay tried it in the order above - slightly better but still not great

hmm still kind of a mess

Hi, is there any update about this problem?


[WIP] Pytorch Test and Proxy

Potential solution for #34

By installing pytorch-cuda=12.1, there's a CTK confusion when building Numbast:
      /opt/conda/envs/test/bin/x86_64-conda-linux-gnu-c++ -DVERSION_INFO=0.0.1 -Dcurand_host_EXPORTS -isystem /opt/conda/envs/test/include/python3.10 -isystem /opt/conda/envs/test/lib/python3.10/site-packages/pybind11/include -fvisibility-inlines-hidden -fmessage-length=0 -march=nocona -mtune=haswell -ftree-vectorize -fPIC -fstack-protector-strong -fno-plt -O2 -ffunction-sections -pipe -isystem /opt/conda/envs/test/include -O3 -DNDEBUG -fPIC -MD -MT CMakeFiles/curand_host.dir/curand_host_api.cpp.o -MF CMakeFiles/curand_host.dir/curand_host_api.cpp.o.d -o CMakeFiles/curand_host.dir/curand_host_api.cpp.o -c /__w/numbast/numbast/numba_extensions/curand_host/curand_host_api.cpp
      /__w/numbast/numbast/numba_extensions/curand_host/curand_host_api.cpp:9:10: fatal error: curand.h: No such file or directory
          9 | #include <curand.h>
            |          ^~~~~~~~~~
      compilation terminated.
      ninja: build stopped: subcommand failed.

      *** CMake build failed
      [end of output]

A bigger problem is that we might need to support CTK 12.1 in general if we want to deliver this feature today.

a94e415 and 37a6f78 are two commits I pushed to leverage the CI to run tests for bfloat16 and the pytorch integration. Skipping fp16 and curand tests.

The conda package probably is going to force CUDA 12.1.  If we install from pip we might be ok mixing everything into a CUDA 12.4 env.

In V100 test the bfloat16 tests are skipped. While A100 tests are not passing due to:
 >               raise AssertionError("Torch not compiled with CUDA enabled")
E               AssertionError: Torch not compiled with CUDA enabled

Do you think we should setup a new instance with CTK 12.1 and only test bfloat16 + pytorch integration?

@isVoid this is now passing and ready for review


CI for Node

Contains the compiled JavaScript (5 ms)
Initializes with two players (3 ms)
Starts the game with a random player (1 ms)
Sets the current player to be whoever it is not


Shapely buffer returns empty polygon

Expected behavior and actual behavior.
I'm using a buffer to reduce precision error before applying contains operation on my geometries. Geometry that is expected to contain another one gets small buffer applied to catch a cases when there is some rounding issue eg. -85.1234 and -85.123400000000055.
However some polygons after having this operation applied returns empty geometry:
example polygon:
POLYGON ((-8486160.859752608 4407005.311912118, -8486322.012133999 4419552.266313265, -8498821.965759974 4419382.682467878, -8498646.158633558 4406836.479565462, -8486160.859752608 4407005.311912118))
buffer(1e-9) - ok
buffer(1e-10) - ok
buffer(1e-11) - POLYGON EMPTY
Steps to reproduce the problem.
wkt = "POLYGON ((-8486160.859752608 4407005.311912118, -8486322.012133999 4419552.266313265, -8498821.965759974 4419382.682467878, -8498646.158633558 4406836.479565462, -8486160.859752608 4407005.311912118))"
poly = shapely.wkt.loads(wkt)
print(poly.buffer(1e-11))

Operating system
Alpine (docker image - ghcr.io/osgeo/gdal:alpine-small-3.8.2)
Shapely version and provenance
shapely - 2.0.3 installed through poetry

In some rare cases this indeed happens when a negative buffer is applied :-(.
Shapely is actually mainly a python wrapper around a C++ library, GEOS, where the actual algorithms are implemented. So I added this example to an existing issue about this problem in the GEOS project: https://github.com/libgeos/geos/issues/984


Can tensorflow be updated?

I see this in the package.json: "@tensorflow/tfjs": "^3.2.0", but the latest version is 4.2.1. Also I notice that there is a reference to "@tensorflow/tfjs-node": "^3.2.0", and that project has been archived.
Is it safe to update those dependencies or will that need lots of other changes?

@dohertyguirand @rabitt
Probably safe to upgrade. I believe tfjs-node is only used for testing. Where have you seen that tfjs-node was archived? I see at least one new release a month ago on npm.

https://github.com/tensorflow/tfjs-node?tab=readme-ov-file

Ah. I guess Google setup tfjs-node to point to tfjs


Issue using big response object in Entry with async client

Hey,
firstly: big thanks for the library and the effort you put into it. It really helps us while testing.
While testing some things in our code base, I discovered that mocked async calls never finish if the response object passed to the  Entry is above some size.
I wrote some code to be able to reproduce the behaviour:
import asyncio
import datetime
import json

import httpx
from mocket import mocketize
from mocket.mockhttp import Entry

@mocketize(strict_mode=True)
def test_sync_case():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(30_000)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    with httpx.Client() as client:
        response = client.post(test_uri)
        print("high number sync: ", len(response.json()))

@mocketize(strict_mode=True)
def test_async_case_low_number():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(100)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    async def main():
        async with httpx.AsyncClient() as client:
            response = await client.post(test_uri)

        print("low number async: ", len(response.json()))

    loop = asyncio.new_event_loop()
    loop.run_until_complete(main())

@mocketize(strict_mode=True)
def test_async_case_high_number():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(30_000)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    async def main():
        async with httpx.AsyncClient() as client:
            # Awaiting the response never finishes
            response = await client.post(test_uri)

        print("high number async: ", len(response.json()))

    loop = asyncio.new_event_loop()
    loop.run_until_complete(main())

test_sync_case()
test_async_case_low_number()
test_async_case_high_number()

While the functions test_sync_case() and test_async_case_low_number() run through, test_async_case_high_number() never finishes.
The number until the code works for test_async_case_low_number() is   response = [{"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(1_525)]. At 1526 it stops working.
Am I doing something wrong? Or could a bug be hiding here?
We're running Python 3.11 with httpx==0.24.1 and mocket==3.12.3

Hi there, the tests pass if set up properly:
$ pytest examply.py
================================================================== test session starts ==================================================================
platform linux -- Python 3.11.6, pytest-7.4.2, pluggy-1.3.0 -- /home/employee/repos/python-mocket/.venv/bin/python3
cachedir: .pytest_cache
rootdir: /home/employee/repos/python-mocket
configfile: pytest.ini
plugins: cov-4.1.0, asyncio-0.21.1, anyio-3.7.1
asyncio: mode=Mode.STRICT
collected 3 items

prova.py::test_sync_case PASSED                                                                                [ 33%]
prova.py::test_async_case_low_number PASSED                                                                                [ 66%]
prova.py::test_async_case_high_number PASSED                                                                                [100%]

---------- coverage: platform linux, python 3.11.6-final-0 -----------
Name                                   Stmts   Miss  Cover   Missing
--------------------------------------------------------------------
mocket/__init__.py                         4      0   100%
mocket/async_mocket.py                     7      0   100%
mocket/compat.py                          18      2    89%   25-26
mocket/exceptions.py                       4      0   100%
mocket/mocket.py                         452    136    70%   56-57, 103, 113-115, 138-140, 143-144, 157-159, 163, 201, 204, 213, 228, 231, 234, 237, 240, 243-248, 263, 266, 270-273, 280-282, 291, 298-300, 313, 317-323, 327, 332-335, 338-427, 448-451, 484-485, 487-488, 494-495, 503-504, 508, 517-518, 602, 606, 611-612, 619, 634, 637, 642-644, 649, 658, 663, 687, 695, 709-711, 718
mocket/mockhttp.py                       151     24    84%   32-35, 55, 59, 63, 67-70, 74, 92, 126-127, 168, 183-185, 205-206, 238, 243, 250
mocket/mockredis.py                       52     52     0%   1-90
mocket/plugins/__init__.py                 0      0   100%
mocket/plugins/httpretty/__init__.py      66     66     0%   1-119
mocket/plugins/httpretty/core.py           2      2     0%   1-3
mocket/plugins/pook_mock_engine.py        45     45     0%   1-80
mocket/utils.py                           26      5    81%   18, 26-27, 35-36
--------------------------------------------------------------------
TOTAL                                    827    332    60%

=================================================================== 3 passed in 0.34s ===================================================================

Here is the version I run:
import datetime
import json

import httpx
import pytest
from mocket import mocketize, async_mocketize
from mocket.mockhttp import Entry

@mocketize(strict_mode=True)
def test_sync_case():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(30_000)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    with httpx.Client() as client:
        response = client.post(test_uri)
        print("high number sync: ", len(response.json()))

@pytest.mark.asyncio
@async_mocketize(strict_mode=True)
async def test_async_case_low_number():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(100)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    async def main():
        async with httpx.AsyncClient() as client:
            response = await client.post(test_uri)

        print("low number async: ", len(response.json()))

@pytest.mark.asyncio
@async_mocketize(strict_mode=True)
async def test_async_case_high_number():

    test_uri = "https://abc.de/testdata/"
    base_timestamp = int(datetime.datetime.now().timestamp())
    response = [
        {"timestamp": base_timestamp + i, "value": 1337 + 42 * i} for i in range(30_000)
    ]
    Entry.single_register(
        method=Entry.POST,
        uri=test_uri,
        body=json.dumps(
            response,
        ),
        headers={"content-type": "application/json"},
    )

    async def main():
        async with httpx.AsyncClient() as client:
            # Awaiting the response never finishes
            response = await client.post(test_uri)

        print("high number async: ", len(response.json()))

Sorry, I made a mistake. Let me have a deeper look at it.

@mindflayer thank you for the fast reply. Much appreciated. Let me know if you need any help troubleshooting or getting to the root of the issue :)

Hi @Veritogen, I spent some time on it but still had no luck. Feel free to investigate further.

I found the problem and I am trying to fix a test that breaks as a drawback. I am positive, btw. :)

Still having issues with aiohttp, a few tests are now broken.
I wonder if @ento could have a look at https://github.com/mindflayer/python-mocket/pull/226.

a test that breaks

A few tests that break :/

Left a comment with my findings in #226 - hope that's useful.

I've just released a new version which should work for your test-case: https://pypi.org/project/mocket/3.12.7/

I'm closing this issue, feel free to comment in case you still experience problems.

I can confirm that it works. Sorry for taking so long to respond and many, many thanks for fixing the issue. Much appreciated!


Problems importing flags from config file

From https://my.guild.ai/t/inferring-flags-from-a-config-file/327/5

This is a project issue - see issue resolution doc


Add use cases to DG add cmd & add parent

Resolves #5

Codecov Report

Merging #17 (da2a4ee) into master (d9f6796) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #17   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


address a few issues in the chrome lighthouse audit

a few issues got flagged in the lighthouse audit, and are addressed in this commit:

lack of "lang" attribute in the html element
lack of "alt" attribute on images

We've added a default alt='' attribute for the images that don't explicitly have alt tags, since for some screen readers, the default behavior is to read the src attribute of the element, and we don't want that.

lack of "meta description"
insecure external links

Most modern browsers support "noopener", though for completeness it's still common to combine it with "noreferrer" for support in older browsers. This addition is to prevent clickjacking vulnerabilities.

Thanks @lpmi-13 👍

See comment posted by @lpmi-13 in https://github.com/HackYourFutureBelgium/hackyourfuture.be/pull/3#issuecomment-701420082


ELECTRON-357 (Fix time-out issue in Unit tests and Spectron tests.)

Description
Fixes time-out issue in Unit tests and Spectron tests.
Changed the unit tests time-out to 60000s.
Before:
150s to 200s to run the Unit tests
300s to 400s to run the Spectron tests
After:
30s to 35s to run the Unit tests
80s to 90s to run the Spectron tests
Approach
How does this change address the problem?

Problem with the code: Running rebuild script every time. causing time-out

Fix: Now running the rebuildscript once before starting the tests.

Learning
N/A
Blog Posts
N/A
Related PRs
N/A
Open Questions if any and Todos

[x] Unit-Tests
Build number: #30

Spectron

[x] Documentation
[x] Automation-Tests

@VikasShashidhar @VishwasShashidhar @KiranNiranjan  Please review. Thanks 😃

@keerthi16 Please address the changes I've requested as part of the comments.
Also, squash the commits and add title to the commits along with the ticket number.
Thanks!

lgtm 👍


Workaround for missing window in web worker

Adds a simple workaround to make this extension compatible with web workers.
See also https://github.com/webpack/webpack/issues/6642

See also: Requires windows since 2.3.1 #62

@N8th8n8el, thanks for the PR.  @physikerwelt and @harryadel will investigate re. #62 before this is merged in.


bump console version

Why -1 ?

@pleeko and I assume it's when you want to release a console patch only without another core release. Like we debated for this one, since there is not core patches.


[nrf fromtree] bluetooth: host: smp: unauth bond overwrite on differe…

…nt identity
Added a new Kconfig option for the Bluetooth Host to allow unauthenticated pairing attempts made by the peer where an unauthenticated bond already exists on other local identity.
Signed-off-by: Kamil Piszczek<EMAIL_ADDRESS>(cherry picked from commit 916e02563cf5742a0948c0ee9987083c32ce4d34)

Linked with: https://github.com/nrfconnect/sdk-nrf/pull/9557


fix(any.do): Any.do integration

＃1799
But only task list.
Not showed in Task card.

I created new pull request


CI: K8sAgentHubbleTest Hubble Observe Test L3/L4 Flow

Test Name
K8sAgentHubbleTest Hubble Observe Test L3/L4 Flow

Failure Output
FAIL: hubble-relay was not able to get into ready state

Stack Trace
/home/jenkins/workspace/Cilium-PR-K8s-1.16-kernel-4.9/src/github.com/cilium/cilium/test/ginkgo-ext/scopes.go:453
hubble-relay was not able to get into ready state
Expected
    <*errors.errorString | 0xc0022117f0>: {
        s: "timed out waiting for pods with filter -l k8s-app=hubble-relay to be ready: 10m0s timeout expired",
    }
to be nil
/home/jenkins/workspace/Cilium-PR-K8s-1.16-kernel-4.9/src/github.com/cilium/cilium/test/k8s/hubble.go:139

Standard Output
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Number of "context deadline exceeded" in logs: 0
Number of "level=error" in logs: 0
Number of "level=warning" in logs: 0
Number of "Cilium API handler panicked" in logs: 0
Number of "Goroutine took lock for more than" in logs: 0
No errors/warnings found in logs
Cilium pods: [cilium-qlsmq cilium-r89zn]
Netpols loaded:
CiliumNetworkPolicies loaded:
Endpoint Policy Enforcement:
Pod                             Ingress   Egress
coredns-8cfc78c54-p9md5         false     false
hubble-relay-579fc44f8d-px86b   false     false
Cilium agent 'cilium-qlsmq': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 20 Failed 0
Cilium agent 'cilium-r89zn': Status: Ok  Health: Ok Nodes "" ContainerRuntime:  Kubernetes: Ok KVstore: Ok Controllers: Total 28 Failed 0

Standard Error
20:04:57 STEP: Running BeforeAll block for EntireTestsuite K8sAgentHubbleTest Hubble Observe
20:04:57 STEP: Ensuring the namespace kube-system exists
20:04:57 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs")
20:04:57 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=cilium-test-logs") => <nil>
20:04:57 STEP: Installing Cilium
20:04:58 STEP: Waiting for Cilium to become ready
20:05:22 STEP: Validating if Kubernetes DNS is deployed
20:05:22 STEP: Checking if deployment is ready
20:05:22 STEP: Checking if kube-dns service is plumbed correctly
20:05:22 STEP: Checking if pods have identity
20:05:22 STEP: Checking if DNS can resolve
20:05:26 STEP: Kubernetes DNS is up and operational
20:05:26 STEP: Validating Cilium Installation
20:05:26 STEP: Performing Cilium controllers preflight check
20:05:26 STEP: Performing Cilium status preflight check
20:05:26 STEP: Performing Cilium health check
20:05:26 STEP: Checking whether host EP regenerated
20:05:34 STEP: Performing Cilium service preflight check
20:05:34 STEP: Performing K8s service preflight check
20:05:40 STEP: Waiting for cilium-operator to be ready
20:05:40 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator")
20:05:40 STEP: WaitforPods(namespace="kube-system", filter="-l name=cilium-operator") => <nil>
20:05:40 STEP: Waiting for hubble-relay to be ready
20:05:40 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=hubble-relay")
20:15:40 STEP: WaitforPods(namespace="kube-system", filter="-l k8s-app=hubble-relay") => timed out waiting for pods with filter -l k8s-app=hubble-relay to be ready: 10m0s timeout expired
20:15:40 STEP: cmd: kubectl describe pods -n kube-system -l k8s-app=hubble-relay
Exitcode: 0
Stdout:
 	 Name:         hubble-relay-579fc44f8d-px86b
	 Namespace:    kube-system
	 Priority:     0
	 Node:         k8s2/<IP_ADDRESS>
	 Start Time:   Wed, 25 Jan 2023 20:04:58 +0000
	 Labels:       app.kubernetes.io/name=hubble-relay
	               app.kubernetes.io/part-of=cilium
	               k8s-app=hubble-relay
	               pod-template-hash=579fc44f8d
	 Annotations:  <none>
	 Status:       Running
	 IP:           <IP_ADDRESS>
	 IPs:
	   IP:           <IP_ADDRESS>
	 Controlled By:  ReplicaSet/hubble-relay-579fc44f8d
	 Containers:
	   hubble-relay:
	     Container ID:  docker://1ec2483b8a81611c182e634e5041c62b844bf7598fb48c0ca956c78cc91bbda6
	     Image:         quay.io/cilium/hubble-relay-ci:b4e7e150352a837e3a3e0b782f2899b5d514a099
	     Image ID:      docker-pullable://quay.io/cilium/hubble-relay-ci@sha256:96cb078f40bb5e1364b47126731b3925d172313436bce63692708b299e5f7542
	     Port:          4245/TCP
	     Host Port:     0/TCP
	     Command:
	       hubble-relay
	     Args:
	       serve
	       --debug
	     State:       Waiting
	       Reason:    CrashLoopBackOff
	     Last State:  Terminated
	       Reason:    Error
	       Message:   Error: failed to start gops agent: open /1: permission denied

	       Exit Code:    1
	       Started:      Wed, 25 Jan 2023 20:11:15 +0000
	       Finished:     Wed, 25 Jan 2023 20:11:15 +0000
	     Ready:          False
	     Restart Count:  6
	     Liveness:       tcp-socket :grpc delay=0s timeout=1s period=10s #success=1 #failure=3
	     Readiness:      tcp-socket :grpc delay=0s timeout=1s period=10s #success=1 #failure=3
	     Environment:    <none>
	     Mounts:
	       /etc/hubble-relay from config (ro)
	       /var/lib/hubble-relay/tls from tls (ro)
	 Conditions:
	   Type              Status
	   Initialized       True
	   Ready             False
	   ContainersReady   False
	   PodScheduled      True
	 Volumes:
	   config:
	     Type:      ConfigMap (a volume populated by a ConfigMap)
	     Name:      hubble-relay-config
	     Optional:  false
	   tls:
	     Type:                Projected (a volume that contains injected data from multiple sources)
	     SecretName:          hubble-relay-client-certs
	     SecretOptionalName:  <nil>
	 QoS Class:               BestEffort
	 Node-Selectors:          kubernetes.io/os=linux
	 Tolerations:             node.kubernetes.io/not-ready:NoExecute for 300s
	                          node.kubernetes.io/unreachable:NoExecute for 300s
	 Events:
	   Type     Reason                  Age                  From               Message
	   ----     ------                  ----                 ----               -------
	   Normal   Scheduled               <unknown>            default-scheduler  Successfully assigned kube-system/hubble-relay-579fc44f8d-px86b to k8s2
	   Warning  FailedCreatePodSandBox  10m                  kubelet, k8s2      Failed create pod sandbox: rpc error: code = Unknown desc = [failed to set up sandbox container "f2795a84b08d360ec1374f5a37ff0000b506c9f72100e52ff59c469ab95f3dec" network for pod "hubble-relay-579fc44f8d-px86b": networkPlugin cni failed to set up pod "hubble-relay-579fc44f8d-px86b_kube-system" network: failed to find plugin "cilium-cni" in path [/opt/cni/bin], failed to clean up sandbox container "f2795a84b08d360ec1374f5a37ff0000b506c9f72100e52ff59c469ab95f3dec" network for pod "hubble-relay-579fc44f8d-px86b": networkPlugin cni failed to teardown pod "hubble-relay-579fc44f8d-px86b_kube-system" network: failed to find plugin "cilium-cni" in path [/opt/cni/bin]]
	   Normal   SandboxChanged          10m (x2 over 10m)    kubelet, k8s2      Pod sandbox changed, it will be killed and re-created.
	   Normal   Pulling                 9m30s (x4 over 10m)  kubelet, k8s2      Pulling image "quay.io/cilium/hubble-relay-ci:b4e7e150352a837e3a3e0b782f2899b5d514a099"
	   Normal   Pulled                  9m30s (x4 over 10m)  kubelet, k8s2      Successfully pulled image "quay.io/cilium/hubble-relay-ci:b4e7e150352a837e3a3e0b782f2899b5d514a099"
	   Normal   Created                 9m30s (x4 over 10m)  kubelet, k8s2      Created container hubble-relay
	   Normal   Started                 9m29s (x4 over 10m)  kubelet, k8s2      Started container hubble-relay
	   Warning  BackOff                 35s (x52 over 10m)   kubelet, k8s2      Back-off restarting failed container

Stderr:

FAIL: hubble-relay was not able to get into ready state
Expected
    <*errors.errorString | 0xc0022117f0>: {
        s: "timed out waiting for pods with filter -l k8s-app=hubble-relay to be ready: 10m0s timeout expired",
    }
to be nil
20:15:40 STEP: Running JustAfterEach block for EntireTestsuite K8sAgentHubbleTest Hubble Observe
===================== TEST FAILED =====================
20:15:40 STEP: Running AfterFailed block for EntireTestsuite K8sAgentHubbleTest Hubble Observe
cmd: kubectl get pods -o wide --all-namespaces
Exitcode: 0
Stdout:
 	 NAMESPACE           NAME                               READY   STATUS             RESTARTS   AGE   IP              NODE   NOMINATED NODE   READINESS GATES
	 cilium-monitoring   grafana-7fd557d749-vpj7h           0/1     Running            0          82m   <IP_ADDRESS>       k8s1   <none>           <none>
	 cilium-monitoring   prometheus-d87f8f984-c6mvs         1/1     Running            0          82m   <IP_ADDRESS>       k8s1   <none>           <none>
	 kube-system         cilium-operator-6cb6d98d7f-4b7hh   1/1     Running            0          10m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         cilium-operator-6cb6d98d7f-n2d66   1/1     Running            0          10m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-qlsmq                       1/1     Running            0          10m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         cilium-r89zn                       1/1     Running            0          10m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         coredns-8cfc78c54-p9md5            1/1     Running            0          10m   <IP_ADDRESS>      k8s2   <none>           <none>
	 kube-system         etcd-k8s1                          1/1     Running            0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         hubble-relay-579fc44f8d-px86b      0/1     CrashLoopBackOff   6          10m   <IP_ADDRESS>        k8s2   <none>           <none>
	 kube-system         kube-apiserver-k8s1                1/1     Running            0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-controller-manager-k8s1       1/1     Running            3          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-hdzsk                   1/1     Running            0          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         kube-proxy-xglsb                   1/1     Running            0          82m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         kube-scheduler-k8s1                1/1     Running            4          85m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         log-gatherer-lckcj                 1/1     Running            0          82m   <IP_ADDRESS>   k8s2   <none>           <none>
	 kube-system         log-gatherer-zdmjs                 1/1     Running            0          82m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-4xdsh               1/1     Running            0          82m   <IP_ADDRESS>   k8s1   <none>           <none>
	 kube-system         registry-adder-xl5gj               1/1     Running            0          82m   <IP_ADDRESS>   k8s2   <none>           <none>

Stderr:

Fetching command output from pods [cilium-qlsmq cilium-r89zn]
cmd: kubectl exec -n kube-system cilium-qlsmq -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])          IPv6       IPv4        STATUS
	            ENFORCEMENT        ENFORCEMENT
	 408        Disabled           Disabled          4          reserved:health                      fd02::8d   <IP_ADDRESS>   ready
	 1764       Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s1                                  ready
	                                                            k8s:node-role.kubernetes.io/master
	                                                            k8s:status=lockdown
	                                                            reserved:host

Stderr:

cmd: kubectl exec -n kube-system cilium-r89zn -c cilium-agent -- cilium endpoint list
Exitcode: 0
Stdout:
 	 ENDPOINT   POLICY (ingress)   POLICY (egress)   IDENTITY   LABELS (source:key[=value])                            IPv6        IPv4         STATUS
	            ENFORCEMENT        ENFORCEMENT
	 121        Disabled           Disabled          4          reserved:health                                        fd02::1fd   <IP_ADDRESS>    ready
	 128        Disabled           Disabled          9807       k8s:io.cilium.k8s.policy.cluster=default               fd02::169   <IP_ADDRESS>   ready
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=coredns
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=kube-dns
	 600        Disabled           Disabled          1          k8s:cilium.io/ci-node=k8s2                                                      ready
	                                                            reserved:host
	 1155       Disabled           Disabled          20461      k8s:app.kubernetes.io/name=hubble-relay                fd02::182   <IP_ADDRESS>     ready
	                                                            k8s:app.kubernetes.io/part-of=cilium
	                                                            k8s:io.cilium.k8s.policy.cluster=default
	                                                            k8s:io.cilium.k8s.policy.serviceaccount=hubble-relay
	                                                            k8s:io.kubernetes.pod.namespace=kube-system
	                                                            k8s:k8s-app=hubble-relay

Stderr:

===================== Exiting AfterFailed =====================
20:15:52 STEP: Running AfterEach for block EntireTestsuite

Resources

Jenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.9/3847
ZIP file(s): 5d011c09_K8sAgentHubbleTest_Hubble_Observe_Test_L3-L4_Flow.zip

Anything else?
Seen on #23333

hubbley-relay is crash-looping:
	 kube-system         hubble-relay-579fc44f8d-px86b      0/1     CrashLoopBackOff   6          10m   <IP_ADDRESS>        k8s2   <none>           <none>

In the crashing pod's logs (pod-kube-system-hubble-relay-579fc44f8d-px86b-hubble-relay.log and pod-kube-system-hubble-relay-579fc44f8d-px86b-hubble-relay-previous.log) we see:
2023-01-25T20:11:15.081665606Z Error: failed to start gops agent: open /1: permission denied

Very likely related to #23259. I'll investigate.

https://github.com/cilium/cilium/pull/23405 is not a proper fix, will open a new PR shortly.


Migrate to better narration rather than tooltips

Instead of confusing icons and tooltips, provide users with better narration for how to initiate mediation and peer connections.

using @AlexAndrei98 mocks

completed as part of https://github.com/roots-id/rootswallet/issues/129


Request = format document Shift+alt + A

maybe they could put "format document Shift+alt + A "

would fix tab problems, line breaks, etc.

interesting! nice idea @ericcobblepot I'll do it on 1.2.0


How to utilize in reactphp?

It is splendid. However, I would like to utilize ReactPHP through the library available at https://github.com/reactphp/datagram. Are there any exemplary instances accessible for consultation?

You can use https://github.com/revoltphp/event-loop-adapter-react to combine ReactPHP libraries with Revolt.


[CCXDEV-9345] Add metrics

Adding prometheus metrics to the fastapi.

ok
(btw do we really trust fastapi + prometheus_fastapi libraries? I heard from Python gurus these are pretty unstable)

I think we should be fine. In the end it's just a layer on top of Starlette. Just for making sure about stability, we are using fixed versions for both libraries.


Fixed README.md

Changed README to README.md, added a screenshot, and fixed a few typos.

Thanks! Was wondering why it was messed up.


refactor: use diamond operator

Co-authored-by: Moderne<EMAIL_ADDRESS>

Ok, I went through the changes end reverted the ones where no type-info was left.


issue with ethernet interface

after installing pynq networking i am unable to access pynq via browser.
is this due to changes made by pynq networking to the eth0 file in interfaces.d??
and i also don't have old backup up file.

https://github.com/Xilinx/PYNQ-Networking/blob/master/setup.py#L62
The setup.py should have made a copy in your system. You can recover using that.
For you issue, there are several things to do first:
1.upgrade your PYNQ image to v2.2:
sudo pip3.6 install --upgrade git+https://github.com/Xilinx/PYNQ.git

then pip install the latest networking overlay.

i checked now PYNQ networking was not completely installed.
after changing eth0 file contents as following i was able to access pynq thorough browser.
auto eth0
iface eth0 inet dhcp
auto eth0:1
iface eth0:1 inet static
address <IP_ADDRESS>
netmask <IP_ADDRESS>

while updating pynq i am getting this error.
fatal: unable to access 'https://github.com/Xilinx/PYNQ.git/': Could not resolve host: github.com
Command "git clone -q https://github.com/Xilinx/PYNQ.git /tmp/pip-dw4yjj8f-build" failed with error code 128 in None

i i upgraded the pynq and installed the latest networkking overlay from pynq which changed my eth0 file contests as following but still i am not able to access jupyter-notebook via browser.

how to resolve this issue because without it i am not able to use this overlay.

I need more information. Can you introduce a little more about your setup? Wireless, wired? Dynamic IP or static IP?

i am using static ip and using wired setup following is the snapshot of the system.

no it is after installing the networking overlay actually i removed br0 line from eth0 file because with that i was unable to access my board from browser.

@yunqu br0 is showing there but now i am unable to access jupyter notebook .

after trying i am able to solve connectivity issue with the following eth0  configuration.

But now when i run following code in jupyter notebook i got an Error shown on serial terminal.

Error shown on Serial port

Kernel seems crashed. Maybe the br0 was assumed to be bridging on top of eth0 instead of the static eth0:1. Instead of trying to resolve this issue by yourself, is it possible to plug in an Ethernet cable to your board, and start over again? Just want to make sure this is actually working before you want to play around the static IP.

as per your instructions i tried it again by reinstalling but same issue that jupyter notebook is not accessible.

it am stuck in this issue since a month.

Let me confirm this: you used DHCP for your Ethernet connection on the board (say you have an assigned IP address a.b.c.d). Then are you able to directly type in that IP in your web browser to access it (assuming your PC is also connected to the same network)?

no i am not using dhcp i have connected board directly to my PC.

@stephenneuendorffer  what to configure in in FPGA.? i just installed the PYNQ overlay from git repository into my board.
no we are working together and having the same issue.

If you really want to use the static IP to connect your board with PC, another hacky thing to try, is to get rid of the original eth0 DHCP and make eth0 IP static assigned (not eth0:1), something like:
auto eth0
iface eth0 inet static
address <IP_ADDRESS>
netmask <IP_ADDRESS>

auto br0
iface br0 inet dhcp
bridge_ports eth0

Thanks @yunqu  i try this and then let you know.

@yunqu  i changed configuration as you mentioned but still not working.

when i ping from both sides it says destination host  unreachable.

After booting the board, you should be able to connect to the jupyter web server. Can you do this?  Can you run through the first three notebooks successfully (which don't use any FPGA acceleration)?
It looks like (based on @jeffiy's comment) that you're getting stuck on the fourth notebook.  You have to run the first two cells in the notebook (which download the overlay) before the third.  It looks like the kernel driver for the bridge IP is crashing, which shouldn't happen if the overlay has been downloaded.  It doesn't surprise me that you run into problems after that point.  We need to determine why the kernel driver is crashing.

@jeffiy I think the configuration for eth0:1 needs to be updated too.
Please try this from the serial port:
sudo ifconfig eth0:1 down
sudo ifconfig br0:1 <IP_ADDRESS>
And then see if you can ping back and forth.

@stephenneuendorffer  Yes now i can open jupyter-notebook via browser.

@stephenneuendorffer  what was the problem and what should i do now?

The problem is that when the bridge is enabled, the eth0 interface is no longer logically accessible independently of the bridge.  As a side effect this means that the eth0:1 interface is not legal.  To make the fix permanent, you can change the /etc/network/interfaces.d/eth0 file to replace 'eth0:1' with 'br0:1'.  This file is processed by ifup to determine the correct ifconfig commands.  @yunqu if this works we should patch things this way.

Let me know if this is the fix: https://github.com/Xilinx/PYNQ-Networking/pull/9

I have made changes as yoou mentioned but now i getting other errors.

hi  @yunqu  and @stephenneuendorffer
what should i do now?

Try assigning your PC static IP address.
https://pynq.readthedocs.io/en/v2.0/appendix.html#assign-your-computer-a-static-ip

Follow this link. Worked for me.

I was able to fix the issue with the ethernet connection, I am using the latex image on the PYNQ-Z2 that is 3.0.1 on Windows 11 22H2.
I did not make changes to anything in the interfaces.d file.
I followed these steps:

Open properties of ethernet adapter
Click QoS Packet Scheduler, then click Configure button.
Go to Advanced tab, and select the Speed & Duplex property
Change its value to 10Mbps Full Duplex.
Apply the settings and ping <IP_ADDRESS>

You should now be able to access jupyter-notebook on <IP_ADDRESS>.
Screenshot for reference


Ux General Issues

I was pressing return/ enter when I was highlighting the "X" too.
Windows x64
Intel i5 9th
16GB RAM

There are some general problems with the UX and I'm planning to work on them as soon as possible. I'll be working on this specific issue first, but in the meantime it should work by clicking on the left vertical blue bar once you finish editing the pin and then clicking anywhere else to close the menu.
Let me know if you stumble across other similar issues.

Ni catch, tbh I never noticed. Keeping up with tests might be nice too

@VitoBarra
Would you like me to create new issues or just bundle them in here?

bundled here will be great. maybe you should also rename the issue "UX general problem"  or something like that. but I don't know which is the best practice in these cases. I think @AOx0  could respond to you better

Getting grouped values to appear can take some poking and prodding. See above image where I have managed to get one to display and one to not.  If there are rules to dictate this it would be nice if they were clear.

The best practice is to keep an issue for each specific problem, it's better for granularity.
We can keep this thread as an issue tracker by making mention of it on each new issue related to UX, tho.


globotv changed to globoplay.globo.com

Apparently, brazilian channel globo reformulated his streaming video content website, now the address is globoplay.globo.com.
Here is the output
ERROR: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 661, in extract_info
ie_result = ie.extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 290, in extract
return self._real_extract(url)
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/globo.py", line 357, in _real_extract
video_id = self._search_regex(self._VIDEOID_REGEXES, webpage, 'video id')
File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 584, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
RegexNotFoundError: Unable to extract video id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Post the full output of youtube-dl when run with --verbose option.

Just updated it.

This issue is already fixed and will be available in the next version of youtube-dl.


Form Validation

Question
Answer

Issue or Enhancement
Enhancement

Laravel Version
8.0

Project Version
3.4

Current Behavior
I have the auth from this package. But Form validation on the signup does not seems to be responsive to text. Example: I have a failed validation for "required" First Name. When I enter any value to it, the form still shows the validation error.
Expected Behavior
If the validation criteria is met and form is not submitted, the error message should not be displayed. As reference from AdminLTE version 3 Validation. Here is the link to reference - https://adminlte.io/themes/v3/pages/forms/validation.html
Steps to Reproduce

Install the package in Laravel 8
Click to Register
Enter No values to the Register and click Submit.
Validation fails error will be displayed.
Put the value to any required text box.

BINGO: You will see the error messaging still displayed.
Possible Solutions
Calling Adminlte AJAX for form validation.
Screenshot

The Form Validation is correct that's simply the expected behavior, it only checks the fields on submit there are no AJAX functions included.

As reference from AdminLTE version 3 Validation.

Thats not a reference its only a way to do it, also the demo is intended to test without any backend framework like Laravel or other that's why there is a simple JS Validation script built in the demo.


fix: Ensure Makefile recipes always re-run

I noticed that sometimes we can't re-run certain recipes, e.g. iOS compilation:
➜  10101 git:(main) ✗ make ios
make: `ios' is up to date.

Fix it by introducing a FORCE target, as suggested here:
https://stackoverflow.com/questions/26226106/how-can-i-force-make-to-execute-a-recipe-all-the-time

bors r+


Include pictures for missing verb icons

get them from flat icon

We need 10/12 more premium icons:

Verb
Link

flee (huir)
https://www.flaticon.com/premium-icon/evacuation_3045277

lay
https://www.flaticon.com/premium-icon/chicken_3061655

put
https://www.flaticon.com/premium-icon/put-on-deodorant_1686012

say
https://www.flaticon.com/premium-icon/talk_1989975

sit
https://www.flaticon.com/premium-icon/sitting_3284707

smell
https://www.flaticon.com/premium-icon/smell_3269952

sow (sembrar)
https://www.flaticon.com/premium-icon/sow_3397582

spit
https://www.flaticon.com/premium-icon/spitting_3736124

spoil (estropearse)
https://www.flaticon.com/premium-icon/burger_4117204

steal
https://www.flaticon.com/premium-icon/thief_2267675

stink
https://www.flaticon.com/premium-icon/foot_3300888

swear
https://www.flaticon.com/premium-icon/oath_4078623

sweep
https://www.flaticon.com/premium-icon/sweeping_2955705

tread
https://www.flaticon.com/premium-icon/step_1184701

understand
https://www.flaticon.com/premium-icon/idea_2436837

upset
https://www.flaticon.com/premium-icon/upset_1533764

wear
https://www.flaticon.com/premium-icon/casual_2853377

weave
https://www.flaticon.com/premium-icon/weave_2769681

wring
https://www.flaticon.com/premium-icon/wring_2042372

Just added them, thanks !!!


Feature request: support renaming

I tried to rename a file in a fuse-mounted hyperdrive, and got the error "Function not implemented".
I'd volunteer to implement the function, but my knowledge on fuse-native and hyperdrive are limited.
If you believe this feature request to be relevant I'd gladly appreciate some pointers to implement it myself.

Hey @8000ff, supporting renames in general is pretty challenging at the moment, and we won't be able to do it properly until we land a major update to hypertrie that's still in the works. Unfortunately this isn't a FUSE issue, and requires a change to the data structure.
I'll leave this issue open to track the progress on this.

#9

#9 Not sure how to implement "not supporting directories".

https://github.com/hypercore-protocol/hyperdrive/issues/144


docs(1.x): update directive names to ngLink and ngViewPort

The JS doc was still using the previous directive names.

Landed as f4ad831fb583112ec736a140299feaafa6de31d1. Thanks!


Loading Tasks ...

Issue tracker is ONLY used for reporting bugs. New feature ideas should be discussed in the ideas section. Please use the Q&A section for supporting issues. Please use the search function.
If you encountered the issue after you installed, updated, or reloaded the tasks plugin, please try restarting obsidian before reporting the bug.
If you want to report a bug, please follow the guide lines below to help me resolve it.
Expected Behavior
Show Tasks
Current Behavior
Loading Tasks ...
Steps to Reproduce
input:

and switch to view mode
Context (Environment)

Obsidian version:v0.13.19
Tasks version:1.4.1
[x] I have tried it with all other plugins disabled and the error still occurs

Possible Solution

Hey @troilus, thank you for reaching out. Could you please open the developer console of obisidian, restart obsidian, and tell me if there are any errors or reports from Tasks? Make sure you don't share anything sensitive, just in case.
You can open the developer console with Control+Shift+i (or Command+Shift+i on a mac).

Thank you! It appears that Obsidian's file cache includes a header section with a line-number that is outside of the range of lines of the file where it is in :monocle_face: It could be that I handle line numbers off by one (0-indexed vs. 1-indexed)? Or possibly a bug in Obsidian?
I need to dig into this further. Do you have a file with some unusual headers going on? Or would you be able to run the Tasks plugin from source where you could add some debugging statements? Or, in the worst case, any chance I can get access to your vault? I cannot reproduce this locally (and apparently not many users can :thinking:).
Any help would be much appreciated. A "quickhack" would be guarding the match in line 332 of the Cache, but it appears that's only the symptom of an underlying issue.

Thanks! My vault is in Onedrive, I copy the hole vault to my desktop and open it with Obsidian, tasks plugin worked.
I noticed that Obsidian rebuild index when I open the vault on my desktop.
So I rename the valut folder in Onedrive to a temporary name, open Obsidian, close it, and rename the folder to previous name and open Obsidian to rebuild index, finally the tasks plugin worked.

Good to hear :smile: Tasks relies on Obsidian's cache and indexing.


app.bundle.js:25100 Uncaught TypeError: Failed to execute 'removeEventListener' on 'EventTarget': 2 arguments required, but only 1 present.

After updating to 3.0.1 for the "destory" fix I get another error when trying to use destroy().
"Uncaught TypeError: Failed to execute 'removeEventListener' on 'EventTarget': 2 arguments required, but only 1 present."
Im using barba.js and im initalizing infinite scroll on enter and destroying on leave:
let infScroll = null

const Blogpage = Barba.BaseView.extend({
  namespace: 'blog',
  onEnterCompleted: function() {
    infScroll = new InfiniteScroll( '.js-articles-list', {
      path: '.js-load-more',
      append: '.js-article',
      button: '.js-load-more',
      scrollThreshold: false,
      status: '.page-load-status',
    })
  },
  onLeave: function() {
    infScroll.destroy()
  }
})

Thank you for reporting this issue. I'm sorry to see you're having trouble with Infinite Scroll. Could you provide a live URL, or even better a reduced test case? See Submitting Issues in the contributing guidelines.

Looks like this was a destroy with button bug. A fix will go out in the next release. See #719


ProcessPool output queue size control and zero copy pyarrow serialization

Effective control over the amount of rowgroups that are processed by process pool. The size of rowgroups allowed to be somewhere in loading/decoding is defined now by the amount of workers.
Improved the way we use pyarrow serialization and pyzmq to reduce amount of memory copies.
Improved pyarrow serialization to support decimal.Decimal type.
Improved diagnostics reported by Reader.
These are too many changes for a single PR, but they are split into small commits.

I noticed this in my bundling PR but tests now seem to always hang on the process pool in python 3.6. Not really sure whats going on but I was not able to reproduce locally on my machine.

Codecov Report

Merging #197 into master will increase coverage by 4.23%.
The diff coverage is 85.55%.

@@            Coverage Diff             @@
##           master     #197      +/-   ##
==========================================
+ Coverage   81.85%   86.09%   +4.23%
==========================================
  Files          65       70       +5
  Lines        3467     3582     +115
  Branches      528      472      -56
==========================================
+ Hits         2838     3084     +246
+ Misses        534      399     -135
- Partials       95       99       +4

Impacted Files
Coverage Δ

petastorm/tf_utils.py
79.13% <0%> (-2.45%)
:arrow_down:

petastorm/benchmark/cli.py
0% <0%> (ø)
:arrow_up:

petastorm/reader_impl/shuffling_buffer.py
85.29% <0%> (ø)
:arrow_up:

petastorm/reader_impl/pickle_serializer.py
100% <100%> (ø)

petastorm/workers_pool/thread_pool.py
89.25% <100%> (+0.18%)
:arrow_up:

petastorm/benchmark/throughput.py
86.36% <100%> (+1.51%)
:arrow_up:

petastorm/reader_impl/same_thread_executor.py
100% <100%> (ø)
:arrow_up:

petastorm/reader.py
88.66% <60%> (+1.16%)
:arrow_up:

petastorm/workers_pool/dummy_pool.py
97.22% <66.66%> (-2.78%)
:arrow_down:

petastorm/reader_impl/pyarrow_serializer.py
89.47% <89.47%> (ø)

... and 17 more

Continue to review full report at Codecov.

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


Scrollbar present after re-sizing visualization

A visible scrollbar is present after resizing the window.

This may also be related to this issue for another plugin.

Setting width to 100% works for now..
public/vis/index.js
d3.select(this)
.attr('width', '100%')


Cleanup p2p configuration structures

Motivation
The existing configuration structures are a bit messy. Some fields are doubled - they exist both in the "main" config struct for p2p as well as in the submodule's config structures (for example, fields for the book check logic).
Changes

cleaned up this duplication by using the submodule's config structures as subfields of the "main" p2p config struct.
removed fields that are not part of the configuration (they cannot be configured by user) out from Config structs. Now Config structs contain only settings configurable either by a config file (config.toml) or flags.
removed config.toml fields that don't exist and moved the ones that changed their place in config structures.

Test Plan
unittests
DevOps Notes

[x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
[x] This PR does not affect public APIs
[x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
[x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)

@dshulyak

i don't think that operator should be aware that we have p2p.bootstrap component or p2p.pubsub, it can get removed or updated and it will require changes in the config structure

I absolutely understand your point and I actually agree :) I think there is a middle point where we can meet with this. My intent was to remove duplication and have a single source of truth for the settings that are configurable by an operator. In order to hide the implementation details from the config, I can embed these structures in the main p2p Config instead of having separate fields.

In order to hide the implementation details from the config, I can embed these structures in the main p2p Config instead of having separate fields.

i don't know if parsing will work without subgroups (there was some special code in cmd/base.go), but in general sounds good

It should work with a squash mapstructure tag. But I will need to rename the structs (they are named just Config now) to avoid name collision when embedded in a single struct.

@dshulyak, I embedded pubsub, discovery and bootstrap to hide them from an operator.


Limit WAL backup segments for a single upload

Describe your changes
Don't upload more than 10 WAL segments in one batch. This helps when backup is interrupted by inconsistent election or anything else.
Issue ticket number and link
Should help with https://github.com/neondatabase/neon/issues/3957, but will not fix it completely.
Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] If it is a core feature, I have added thorough tests.
[ ] Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
[ ] If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

[ ] Do not forget to reformat commit message to not include the above checklist

It will stuck on the next iteration waiting for changed commit_lsn. We need to either fix that or just do it more properly updating backup_lsn after each segment upload.

I also did the same, will push in a minute.

(feel free to take my commit message =))


tested with gatsby-theme-codebushi 1.1.0

Updated README with instructions to run this in the gatsby-theme-codebushi yarn workspace.
Upgraded to work with Gatsby 4.0
Fixes a few github issues
Note that text-primary is not a valid Tailwind v2 class; I've disabled it, without a replacement.

Would love to see this merged in.

@Sylk The problem might be that I do not have the permissions to assign

@ChangoMan
@thinkybeast
@rmatambo8
as Reviewers nor Assignees.


Research Hikari database pool settings

There are a large number of configuration knobs:
https://github.com/brettwooldridge/HikariCP#configuration-knobs-baby
It would be good to read through this documentation and ensure that we have reasonable settings giving our environment:

Number of connections in each pool
connectionTimeout
validationTimeout

(There are just a few that stand out.)

Some more good content to evaluate: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing

Going off of the configuration set here, it appears that the only parameter for which we don't use the default is connectionTimeout. After reading the docs, I see a few other knobs that may require adjustment:

maximumPoolSize: Dynamically set to number of CPUs * 2. This is modified from the formula outlined here because there are no spinning disks on our container instances.

maxLifetime of a connection in the pool: the documentation recommends that this value be set lower than a database-level connection timeout.

validationTimeout: I think a good value for validationTimeout is half of maxLifetime, as we'd likely want to remove a connection that spends half of its life not "alive".

leakDetectionThreshold: It will be useful for future performance troubleshooting if we have information about connection leaks. The lowest accepted threshold is 2 seconds. We can start with the threshold there and increase if that's not enough time to determine if a connection is leaking.

I think it makes sense to set leakDetectionThreshold. validationTimeout should be OK now that connectionTimeout was increased.
maximumPoolSize is probably OK for now too, or until we have more info that the default is not good. Same with maxLifetime.