Why does box_w only divide by strides [-1]

Hello, I would like to ask you a question:
In the multi_gt_creator function of the tools.py file, why does box_w only divide by strides [-1] before calculating iou, does this not always cause iou to be calculated on the minimum or maximum downsampling multiple? Instead of calculating at all downsampling multiples.
box_ws = box_w / strides[-1]
box_hs = box_h / strides[-1]

It is because that my all anchor boxes have been divided by 32(the largest stride). Therefore, before computing IoU, I have to divide the groundtruth box by 32. Even though some anchor boxes correspond to stride =8 or 16, see the formulations:
                tw = np.log(box_ws / p_w)
                th = np.log(box_hs / p_h)
It eliminates the effects of factor stride meaning that we actually needn't to divide the anchor boxes and groundtruth bxoes by stride and just omit strides. If I didn't divide my all anchor boxes by 32, I didn't need to divide the box_w and box_h by 32, either.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年3月21日(星期六) 晚上10:45
收件人<EMAIL_ADDRESS>抄送<EMAIL_ADDRESS>主题: [yjh0410/pytorch-yolo-v2-v3] Why does box_w only divide by strides [-1]  (#25)
Hello, I would like to ask you a question:
In the multi_gt_creator function of the tools.py file, why does box_w only divide by strides [-1] before calculating iou, does this not always cause iou to be calculated on the minimum or maximum downsampling multiple? Instead of calculating at all downsampling multiples.
box_ws = box_w / strides[-1]
box_hs = box_h / strides[-1]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Let ground truth find the anchor box that suits it, and then use the anchor box to decide which downsampling multiple it belongs to. Do you mean that?

Yes. In my configuration, there are 9 anchor boxes where the first three anchor boxes correspond to stride=8, the middle three ones correspond to stride=16, and the last three ones correspond to stride=32. If the one of first three anchor boxes is chosen，then the groundtruth is allocated to stride=8 feature map.
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年3月21日(星期六) 晚上11:11
收件人<EMAIL_ADDRESS>抄送: "ら ．Secret"<1394571815<EMAIL_ADDRESS>主题: Re: [yjh0410/pytorch-yolo-v2-v3] Why does box_w only divide by strides [-1]  (#25)
Let ground truth find the anchor box that suits it, and then use the anchor box to decide which downsampling multiple it belongs to. Do you mean that?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I see, thank you for the explanation.^v^

You are welcome ！！
------------------ 原始邮件 ------------------
发件人<EMAIL_ADDRESS>发送时间: 2020年3月21日(星期六) 晚上11:23
收件人<EMAIL_ADDRESS>抄送: "ら ．Secret"<1394571815<EMAIL_ADDRESS>主题: Re: [yjh0410/pytorch-yolo-v2-v3] Why does box_w only divide by strides [-1]  (#25)
I see, thank you for the explanation.^v^
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

您好，请问我在运行demo的时候出现这个问题怎么解决呢


Error in Building Process

An error (ERROR: Config value 'cpu' is not defined in any .rc file) appeared when I entered "bash apollo.sh build".
root@in-dev-docker:/apollo# bash apollo.sh build
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[INFO] Apollo Environment Settings:
[INFO]     APOLLO_ROOT_DIR: /apollo
[INFO]     APOLLO_CACHE_DIR: /apollo/.cache
[INFO]     APOLLO_IN_DOCKER: true
[INFO]     APOLLO_VERSION: @non-git
[INFO]     DOCKER_IMG: dev-x86_64-18.04-20201210_1400
[INFO]     APOLLO_ENV:  STAGE=dev USE_ESD_CAN=false
[INFO]     USE_GPU: USE_GPU_HOST=0 USE_GPU_TARGET=0
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[ OK ] Running CPU build on x86_64 platform.
[WARNING] ESD CAN library supplied by ESD Electronics doesn't exist.
[WARNING] If you need ESD CAN, please refer to:
[WARNING]   third_party/can_card_library/esd_can/README.md
[INFO] Build Overview:
[INFO]     USE_GPU: 0  [ 0 for CPU, 1 for GPU ]
[INFO]     Bazel Options: --config=cpu
[INFO]     Build Targets: //modules/... union //cyber/...
[INFO]     Disabled:      except //modules/drivers/canbus/can_client/esd/... except //modules/perception/... except //modules/planning/open_space/trajectory_smoother:planning_block except //modules/map/pnc_map:cuda_pnc_util except //modules/map/pnc_map:cuda_util_test
WARNING: The following rc files are no longer being read, please transfer their contents or import their path into one of the standard rc files:
/apollo/tools/bazel.rc
ERROR: Config value 'cpu' is not defined in any .rc file

OS: Ubuntu 16.04
Version: Apollo 6.0
Could you please tell me what should I do?

Try running ./apollo.sh config -n first and then try again.

Try running ./apollo.sh config -n first and then try again.

This problem has been solved. Thank you! @storypku

i still got the same error after following the suggestion, is there anything i missed ? the log is inserted below:
root@in-dev-docker:/apollo# ./apollo.sh config -n
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[INFO] Apollo Environment Settings:
[INFO]     APOLLO_ROOT_DIR: /apollo
[INFO]     APOLLO_CACHE_DIR: /apollo/.cache
[INFO]     APOLLO_IN_DOCKER: true
[INFO]     APOLLO_VERSION: @non-git
[INFO]     DOCKER_IMG: dev-x86_64-18.04-20210108_1105
[INFO]     APOLLO_ENV:  STAGE=dev USE_ESD_CAN=false
[INFO]     USE_GPU: USE_GPU_HOST=0 USE_GPU_TARGET=0
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[INFO] Configure .apollo.bazelrc in non-interactive mode
You have bazel 3.7.1 installed.
Found possible Python library paths:
/usr/lib/python3/dist-packages
/usr/local/lib/python3.6/dist-packages
Found CUDA 10.2 in:
/usr/local/cuda-10.2/targets/x86_64-linux/lib
/usr/local/cuda-10.2/targets/x86_64-linux/include
Found cuDNN 7 in:
/usr/lib/x86_64-linux-gnu
/usr/include
Found TensorRT 7 in:
/usr/lib/x86_64-linux-gnu
/usr/include/x86_64-linux-gnu
[ OK ] Successfully configured .apollo.bazelrc in non-interactive mode.
root@in-dev-docker:/apollo# ./apollo.sh build_opt
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[INFO] Apollo Environment Settings:
[INFO]     APOLLO_ROOT_DIR: /apollo
[INFO]     APOLLO_CACHE_DIR: /apollo/.cache
[INFO]     APOLLO_IN_DOCKER: true
[INFO]     APOLLO_VERSION: @non-git
[INFO]     DOCKER_IMG: dev-x86_64-18.04-20210108_1105
[INFO]     APOLLO_ENV:  STAGE=dev USE_ESD_CAN=false
[INFO]     USE_GPU: USE_GPU_HOST=0 USE_GPU_TARGET=0
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[WARNING] nvidia-smi not found. CPU will be used.
[ OK ] Running CPU build on x86_64 platform.
[WARNING] ESD CAN library supplied by ESD Electronics doesn't exist.
[WARNING] If you need ESD CAN, please refer to:
[WARNING]   third_party/can_card_library/esd_can/README.md
[INFO] Build Overview:
[INFO]     USE_GPU: 0  [ 0 for CPU, 1 for GPU ]
[INFO]     Bazel Options: --config=cpu --config=opt
[INFO]     Build Targets: //modules/... union //cyber/...


CB-8936 Gather 15 minutes of logs on Windows

https://issues.apache.org/jira/browse/CB-8936
Currently we gather default 10 minutes of logs which is enough in general, but when build is timing out it takes about 12-13 minutes so we don't get the logs from starting minutes of the test run.

LGTM


Assets paths added to pubscpec.yaml have wrong backslash '' character on Windows

Description:
After running the command "asset_manager add" in cmd on a Windows machine the resulting paths added to my pubscpec.yaml file have an incorrect basckslash '' character instead of the correct '/', resulting in flutter not being able to successfully run the project.
Issues:

Incorrect backslash '' character instead of correct '/'.

Content in pubspec.yaml after running the package:
flutter:

  assets:
    - assets\audio
    - assets\images
    - assets\images\1_Interiors
    - assets\images\1_Interiors\32x32
    - assets\images\1_Interiors\32x32\Old_Stuff
    - assets\images\1_Interiors\32x32\Room_Bulder_subfiles_32x32
    - assets\images\1_Interiors\32x32\Theme_Sorter_32x32
    - assets\images\1_Interiors\32x32\Theme_Sorter_Black_Shadow_32x32

Resulting error when running the project:
Launching lib/main_development.dart on Windows in debug mode...
main_development.dart:1
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(241,5): error MSB8066: Custom build for 'C:\Users\my_project\build\windows\CMakeFiles\8d5ed7d16c2d77a07f2ed3d3c219134c\flutter_windows.dll.rule;C:\Users\my_project\build\windows\CMakeFiles\8126e6043f2fdff3a26fd3c5142bbc6d\flutter_assemble.rule' exited with code 1. [C:\Users\my_project\build\windows\flutter\flutter_assemble.vcxproj]
Exception: Build process failed.
Exited (sigterm)

Manually replacing the '' and adding '/' at the end of each path fixed it:
flutter:

  assets:
    - assets/audio/
    - assets/images/
    - assets/images/1_Interiors/
    - assets/images/1_Interiors/32x32/
    - assets/images/1_Interiors/32x32/Old_Stuff/
    - assets/images/1_Interiors/32x32/Room_Bulder_subfiles_32x32/
    - assets/images/1_Interiors/32x32/Theme_Sorter_32x32/
    - assets/images/1_Interiors/32x32/Theme_Sorter_Black_Shadow_32x32/

This is my flutter doctor:
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.10.0, on Microsoft Windows [Version 10.0.19045.3324], locale en-US)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Build Tools 2019 16.11.19)
[√] Android Studio (version 2022.2)
[√] VS Code (version 1.81.1)
[√] Connected device (3 available)
[√] Network resources

• No issues found!

The latest stable release 1.0.0 fixes this issues. The paths now are appended with an backslash "/" at the end and for window platforms, we've moved to using "/" as the path separator.
@Ricardo-MT Let me know if the latest release fixes the issues for you.

Hi there @rutvik110 , thanks for the quick reply.
I can confirm this issue is solved. This is a great tool, thanks!

Awesome!
Closing this issue as it's resolved🙌


Document ‘nocanon’ for httpd

Currently, the requirement is shown as an error message when it’s not set: https://github.com/girlbossceo/conduwuit/blob/f3427afc7fc7a0e67a8c78be24cba898a6bdba2e/src/api/ruma_wrapper/axum.rs#L245-L246
So perhaps we should mention it somewhere in the docs? There’s also small performance gains to be made by tweaking the example config for Apache httpd over at Conduit.

I would rather just add a small note somewhere making it generic instead of making it Apache-specific.

"Please make sure your reverse proxy gives conduwuit the raw, original request URI."

This way I'm not adding extra reverse proxy "examples" which was something we intentionally removed for many reasons.

I don't see how or why these would impact performance.

I think your config should just be left as default + nocanon. Is there an issue or something you're facing that you're finding yourself modify these reverse proxy config options?

I was just puzzled by these additional settings I saw in Conduit's example.

This is most certainly one of the many reasons why conduwuit deleted all these reverse proxy examples and urges the user to find documentation online on setting up a reverse proxy, with us providing generic instructions, and generally leave things at their defaults.
They become very opinionated, confusing (as you just mentioned), are annoying to maintain, etc.


Fixed missing migration to dedicated deprecator

This is a follow-up to the PR below:

https://github.com/heartcombo/devise/pull/5583
https://github.com/heartcombo/devise/pull/5598

rails has deprecated the use of ActiveSupport::Deprecation in singleton in this PR, so devise has defined its own Deprecator in response to this, but there was an omission in the correction. So I fixed it.
Please note that a PR has been created that will discontinue support for EOL rails versions, and the files modified this time may also be deleted.
https://github.com/heartcombo/devise/pull/5600

I think the failing tests will be fixed in https://github.com/heartcombo/devise/pull/5622

Thanks!


Manage clusters on batre metal using CAPI

User Stories

As a giant swarm customer I want giant swarm to provide a Cluster API Based solution for bare metal, so that I can use my on prem datacenters.
As an existing giant swarm KVM user I want to use cluster api and have a migration path from the current KVM based solution towards a CAPI based solution.

Background

duplicate


As an EVCM, I want to be able to zoom into my location on the map so I can quickly see my community.

Description
We want users to be able to zoom into their location easily so that they can see their community on the map.
Proposed Solution
We're thinking something along the lines of this UX, whereby a user clicks the icon in the upper right corner and it takes them to their location (if they allow location services): https://docs.mapbox.com/mapbox-gl-js/example/locate-user/
Tasks

[ ] Get icon from USWDS to use
[ ] Implement
[ ] Test!

Definition of Done

[ ] User can click an icon that then zooms the map into their location

Description
Solution
Describe alternatives you've considered
Links to user research or other resources
Tasks
DoD

Moving out of Product Backlog, not prioritized for July 27th

Icon: https://fontawesome.com/v5.15/icons/location

USWDS icons: https://designsystem.digital.gov/components/icon/

You can use this url to test the current behind-a-flag geolocation feature: https://d2zjid6n5ja2pt.cloudfront.net/justice40-tool/14e6a9/en/cejst/?flags=gl .
What is needed now : a "geolocation in progress" indicator of some sort for the time between when you hit the button and it zooms into your location

from the dev side, we’re using the out of the box GeolocateControl from react-map-gl ; it sets a geolocationInProgress bool which triggers the addition of a
Geolocation in progress...

we would still need to :

[ ]  style the geolocation in progress banner according to to-be-provided spec
[ ] account for corner cases (geolocation may have already finished when you hit the button again, etc)
[ ] write tests


docs(storage): add documentation for blob and bucket name property

Fixes [82]

@IlyaFaer  @mf2199 Any suggestion for this?

Replace by https://github.com/q-logic/python-storage/pull/8


[Error] if there are too many VODs in the list, the recording does not work

if about 170 VODs in the list, recording no longer works properly.

what is "not properly"? does it just cut out or not at all? any logs when it happens?

He wants to start recording, but then stops and doesn't say what's wrong. It just doesn't work anymore

and since yesterday I have this problem that the stream just stops for no reason. I have not changed anything on the system

can you check the capture logs in the data/logs/software directory?

i've updated streamlink, it could be the issue along with #486

Thanks, had already seen it and directly pulled it from docker but unfortunately no success

i feel like it must either be a streamlink error or your network connection, but i guess it could also be some kind of system stall. does it use up 100% cpu?

The CPU chills its life with 10% maximum load
I have check it and i have no network problems

i mistakenly set the new queue threshold to disable itself at 0, you could try raising it to a higher number as well as the stream timeout, if it's at all related to #486

okay, i try it with the new build :)

okay, doesn't stop more but is come this error and he record only in 360p but i have choose best and 360p is not the best xD

you're gonna have to check the logs for all of these things, seems to be an unique error for your setup unless someone else reports in too

I have been using the tool for almost 2 years now and the problems started after an update. I just can't remember exactly which one. I can reinstall the recorder, but this didn't help last time
LiveStreamDVR-2024-01-15.log
capture_pnation_42217575609_stdout.log

In what way do you mean ratelimit? From Twitch?

preventing abuse by too many requests from twitch yes, i tried running the same command and it seems to capture just fine

Okay, it worked fine for me for about 10 minutes, then it stopped (error). I only record one streamer and the server also has an IP for itself.

it's going on for 23 minutes for me so far, no problems. i feel like it must be on your end somehow. could your country be rate limiting too?

I am Germany and so is the server. I don't know that we have a limit on Twitch. It's been running for almost the last 2 years and we've accumulated 16 TB of VOD material

In that case I'm out of ideas for now, I'm guessing it's more of a streamlink problem, and that can happen if twitch changes something, being a coincidence.

Okay, I'll now set up a second instance of the recorder and test it with a different IP

I am getting the [stream.hls][warning] Encountered a stream discontinuity. This is unsupported and will result in incoherent output data. error on this test capture intermittently but that's probably just the ads. Try it with a vpn to another country if you can.

VPN is on Linux server not so easy :(

VPN is on Linux server not so easy :(

since you are using docker you can use something like gluetun and connect this docker through gluetun and let it use the vpn connection from it.

But that can't be THE solution. There must be another way. I don't want to spend money on a VPN service now.

if the proxy is having issues then so will you

it could be an isp issue that's blocking things or just functioning incorrectly, using a public dns could help with that. it being the video-weaver.waw02.hls.ttvnw.net address which probably is just a common cdn url it shouldn't have a problem

it could be an isp issue that's blocking things or just functioning incorrectly, using a public dns could help with that. it being the video-weaver.waw02.hls.ttvnw.net address which probably is just a common cdn url it shouldn't have a problem

hmmm true.
@devpanda0 where is your server hosted?

@Serph91P ActiveServers - Interwerk https://active-servers.com/

video-weaver.waw02.hls.ttvnw.net

I always use the dns from Cloudflare

@Serph91P ActiveServers - Interwerk https://active-servers.com/

never heard of them but does not mean they are bad. Cannot find anything out of the ordinary from them.
What server hardware did you rent?

I have a BareMetal server there (i9-7920X, 128 GB memory, 250 Gb nvme systemplate, 2x 2TB nvme for VM space, 4x 16 TB HDD for VOD space and OS Proxmox) I've been with them for over 4 years now, no problems. I don't think it has anything to do with the IP or the server

I have a BareMetal server there (i9-7920X, 128 GB memory, 250 Gb nvme systemplate, 2x 2TB nvme for VM space, 4x 16 TB HDD for VOD space and OS Proxmox) I've been with them for over 4 years now, no problems. I don't think it has anything to do with the IP or the server

how many streamer do you have subscribed to?

one

one

yeah then @MrBrax got it right something is definetly blocking or throttling. What reverse proxy are you using because this is the only thing I can think of what could come from your end and block or throttle.

I use nginx as a reverse proxy

reverse proxy wouldn't block anything as that's on the inverse, but is the ttv lol plugin active, or any other kind of proxy?

reverse proxy wouldn't block anything as that's on the inverse, but is the ttv lol plugin active, or any other kind of proxy?

Some reverse proxy can have some kind of firewall etc so they can def block stuff.

reverse proxy wouldn't block anything as that's on the inverse, but is the ttv lol plugin active, or any other kind of proxy?

Some reverse proxy can have some kind of firewall etc so they can def block stuff.

the reverse proxy only handles incoming traffic, the software inside your nat can use any socket and port to communicate outwards

I still use an opnSense firewall but I allow port 80 and 443 to the server for the Nginx webserver.
I can try it again without the firewall but it didn't cause any problems either
I tried my Twitch bot on the server and it has no problem communicating with Twitch using the IP

a regular bot probably wouldn't be affected as it doesn't fetch video content, but if you have a firewall that might affect things i suppose?

It worked for 2 years with the firewall. Nothing was changed in the firewall. So I think no, it doesn't affect it

twitch might have changed things. when you use external services, anything can change at any time. with an issue as odd as this, you gotta expect anything.

So do I really have to get a VPN or a new IP address for this?

ci is currently building a new version with streamlink updated, they released something two days ago, might be worth trying out later. but anything that changes the network would be closer, like external firewall changes, internal firewall, dns, ip address, geolocation, abuse blacklist checks

It has now recorded for 2:30 minutes but then stopped again. But the resolution is right again.

Is it possible for you to activate the debug log from the stream link? That's enough in the develop branch

if you enable debug mode in settings it should use the default debug mode in streamlink too

okay, thx.
Could this also have something to do with it? When I call up the URL myself, I get the following answer: "No data supplied"

no, that's fine. internal communication should work fine

What can we do now?

if neither a dns, ip, or vpn location change works, and the same streamlink capture launched either in the docker container or on the same machine and getting the same error, you'd have to contact streamlink authors/making an issue there

problem solved. IP change was the solution

very cursed and unfortunate problem, might be worth contacting the isp or host about

thanks for your help and perseverance with the problem

Why come this always?

i made it as a warning for me if a capture fails and a huge ts capture file gets left behind, you can see it and move it out of there since it doesn't appear in the ui. mine would take up hundreds of gigs and i'd wonder what was using space.

are those vods being captured right now? otherwise it's just a file that will do nothing in there

Yes, he is currently recording

then i'll make it so it doesn't show when recording, the feature itself wouldn't be intrusive

Thanks, that would be nice if it's not there during the recording


Fix/codeblock background

Changes the codeblock's background to be lighter in light mode, and darker in dark mode, improving contrast and readability.

Accidentally included branch add-md-support-to-index


Localhost now is a required argument

I've just upgraded to Node Inspector v0.9.2
My command line is:
node-debug --no-preload server.js
This used to work. I now get this message:
Malformed URL http:/debug?port=5858
I now have to use
node-debug --web-host localhost --no-preload server.js

I am not able to reproduce the problem using the latest Node Inspector version 0.10.0 running on Node 0.10.38.
 node-debug --no-preload simple-server/
Node Inspector is now available from http://<IP_ADDRESS>:8080/debug?ws=<IP_ADDRESS>:8080&port=5858
Debugging `simple-server/`

debugger listening on port 5858

Is there anything special about your environment? What is your operating system?

OK I have an answer for this.
The regression is in the handling of the .nodeinspectorrc
My old version:
{
  "web-port": 8088,
  "web-host": null,
  "debug-port": 5858,
  "save-live-edit": true,
  "preload": false,
  "hidden": [],
  "stack-trace-limit": 50
}

It used to work, but does not with 0.10
However, if I remove this line
  "web-host": null //REMOVE

Or if I change it to:
  "web-host": "localhost"

Then it works.
My env
$ node-debug -v
Node Inspector v0.10.0

$ node -v
v0.12.2

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 13.10
Release:        13.10
Codename:       saucy

Cool, thanks for investigating the issue. Could you submit a patch to fix the issue please? The configuration is loaded by lib/config.js.

I would be happy to do this but am on a trip and will not have access for a
month.
On Mon, May 4, 2015, 9:14 AM Miroslav Bajtoš<EMAIL_ADDRESS>wrote:

Cool, thanks for investigating the issue. Could you submit a patch to fix
the issue please? The configuration is loaded by lib/config.js
https://github.com/node-inspector/node-inspector/blob/master/lib/config.js
.
—
Reply to this email directly or view it on GitHub
https://github.com/node-inspector/node-inspector/issues/604#issuecomment-98701737
.

Even if I run node-debug --webhost localhost [myapp], I still have to access my app served at <IP_ADDRESS>:[port] rather than localhost:[port]. Is that what this is getting at or should I open a new issue?
Meanwhile, running my app with node normally allows it to be accessed with localhost or <IP_ADDRESS> interchangeably.

I think the problem may be caused by using IPv4-only <IP_ADDRESS> as a default hostname(source code. localhost is resolved as an IPv6 address, where we don't listen on. That does not explain why --webhost localhost does not work though.

Will be fixed in 0.11.0

Maybe this needs a new issue, maybe the same.  It is IPV6 confusion, 'localhost' can resolve to either IPV4 or IPV6  ... so I get
$ node --version
v6.4.0
$ node  --debug-brk  foo.js
Debugger listening on [::]:5858

Where the [::] looks like the v6 equivalent of <IP_ADDRESS>  .  So in this case, node inspector never connects to it.    Node itself doesn't allow --web-host as an option it seems, only node-inspector.
node-inspector --version v0.7.4


Test with PHP 7.1 but allow build failures

Coverage remained the same at 88.403% when pulling 86b8276c4784e0e2b21011d349a2039476eb8230 on tflight:master into 9347a93f45820ffee65dbd9099c1f90f84ded4ea on slimphp:master.


⚠ AGEG website (prod) has degraded performance

In d57cdff, AGEG website (prod) (https://www.ageg.ca/) experienced degraded performance:

HTTP code: 200
Response time: 3951 ms

Resolved: AGEG website (prod) performance has improved in 9b4fe58.


pull request for e2e test at 12/05/2016 08:15:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Relax upper bounds to allow OCaml 4.14 and dune 3

We've yet to adapt our Gobview project to all the other changes in jsoo-react in the meanwhile, but jsoo-react seems to build fine on OCaml 4.14 and dune 3.

The CI failure seems unrelated, it already failed on main with the scheduled job. Probably related to https://github.com/ocaml-ppx/ppxlib/releases/tag/0.26.0.

Thanks!

The CI failure seems unrelated, it already failed on main with the scheduled job. Probably related to https://github.com/ocaml-ppx/ppxlib/releases/tag/0.26.0.

Should be fixed after https://github.com/ml-in-barcelona/jsoo-react/pull/163.

We've yet to adapt our Gobview project to all the other changes in jsoo-react in the meanwhile

We discussed the creation of a compatibility library that should make this migration a bit easier, but unfortunately I have not found the time to work on it yet.


🚧 macOS 13 Ventura Support

Warning
macOS Ventura is still in Beta! I do not recommend this for productive use!

Current state

[x] It boots!
[x] ACPI Compatibility
[x] Kext Compatibility
[x] OpenCore Compatibility
[ ] Stable Kexts files
[x] Stable macOS Version

OpenCore / Kext Versions:

OpenCore: Modified version of e05a69d
AppleALC: 1.7.3 (bce915e)
CPUFriend: 1.2.6 (44efb5f)
Lilu: 1.6.1 (250b65c)
WhateverGreen: 1.5.9

Screenshot

Known Issues

SMBIOS incompatible: A new SMBIOS model will be required.

Current SMBIOS: MacBookPro11,4
Testing SMBIOS: MacBookPro14,1 (minimum)

Issues: Low CPU / GPU Performance

Hello! Do you have worked DisplayPort With SMBios MBP14,1? I used OpenCore Legacy Patcher for my T440p and iGPU good worked

Where can I get the recovery image file from? I could get the installer's DMG and converted it to img but it didn't boot.

Where can I get the recovery image file from? I could get the installer's DMG and converted it to img but it didn't boot.

No recovery image is currently available until the release. You will need to manually upgrade to Ventura, but I don't recommend it as it is very unstable at the moment.

Hello! Do you have worked DisplayPort With SMBios MBP14,1? I used OpenCore Legacy Patcher for my T440p and iGPU good worked. BUT! I can't get work DisplayPort signal with MPB14.1

I have not tried it yet, but I will look into it later.

Where can I get the recovery image file from? I could get the installer's DMG and converted it to img but it didn't boot.

No recovery image is currently available until the release. You will need to manually upgrade to Ventura, but I don't recommend it as it is very unstable at the moment.

The upgrade failed miserably. I could make a bootable hard-disk and for some reason OC is not recognizing it...

I tried that yea. I tried both using a .img and a real hard-drive with USB-passthrough. Still nothing :(

I'm really excited to see the final result with macOS Ventura support! 😁

I'm currently using a slightly tweaked version of your Monterey EFI on my ThinkPad T440s and it works amazingly well.

Ventura is now released. Is any new code update ?

Hello! Do you have worked DisplayPort With SMBios MBP14,1? I used OpenCore Legacy Patcher for my T440p and iGPU good worked. BUT! I can't get work DisplayPort signal with MPB14.1

I have not tried it yet, but I will look into it later.

is it possible to spoof the smbios to macos kind of like oclp does?

Hello, I've managed to install 13.2.1 on X240. It boots, but after patching graphics with OCLP it freeze at boot logo after restart.
Also tried to patch with SMBIOS for MBP11,1 and revert to MBP14,1... but gave me the same result.
With my current EFI from Monterey 12.6 (OC 0.9.2) I'm able to boot into Ventura, I have audio and Wifi but no Graphics Acceleration. I hope to be able to upgrade with the help of the Community! :)

Hello, I've managed to install 13.2.1 on X240. It boots, but after patching graphics with OCLP it freeze at boot logo after restart. Also tried to patch with SMBIOS for MBP11,1 and revert to MBP14,1... but gave me the same result.
With my current EFI from Monterey 12.6 (OC 0.9.2) I'm able to boot into Ventura, I have audio and Wifi but no Graphics Acceleration. I hope to be able to upgrade with the help of the Community! :)

Please, can you share with us your EFI?

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 only 7mb, very slow. Now I find a fix method from
https://github.com/valnoxy/t440p-oc/tree/macos-13-ventura :
"Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to oc
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/valnoxy/t440p-oc/tree/macos-13-ventura : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to EFI
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Thanks for sharing now its working perfect on t440p

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/OakSaytr527/t440p-ventura-oc : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to EFI
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Before following this guide do we just need to change the SMBIOS to MacBookPro14,1 and add the CPU Friend kext or are there any more steps？

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/OakSaytr527/t440p-ventura-oc : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to EFI
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Before following this guide do we just need to change the SMBIOS to MacBookPro14,1 and add the CPU Friend kext or are there any more steps？

I just changed to MBPro 14,1

I just changed to MBPro 14,1

Ok, thank you!

Are you going to make macOS Ventura support stable for the T440p?

has anybody managed to get the mini display port to work with a patched igpu?

has anybody managed to get the mini display port to work with a patched igpu?

Mine works fine on Ventura with valnoxy's EFI

has anybody managed to get the mini display port to work with a patched igpu?

Mine works fine on Ventura with valnoxy's EFI

odd, which version of ventura?

odd, which version of ventura?

13.6, however I forgot to mention that I am using a mini display port to HDMI adapter, maybe that is why yours is not working.

odd, which version of ventura?

13.6, however I forgot to mention that I am using a mini display port to HDMI adapter, maybe that is why yours is not working.

I tried a mini dp to hdmi aswsell it does work but it's really slow (1920x1080@30hz), also does your bluetooth work by any chance?

I tried a mini dp to hdmi aswsell it does work but it's really slow (1920x1080@30hz), also does your bluetooth work by any chance?
I have a native card so my bluetooth works fine (I enabled it with OCLP). Try to see if the device properties of your GPU looks like this:

HDMI works fine for me on Sonoma 14.1, however sometimes I need to disconnect the adapter and re-connect it in order to be recognized by the system.

I tried a mini dp to hdmi aswsell it does work but it's really slow (1920x1080@30hz), also does your bluetooth work by any chance?

I have a native card so my bluetooth works fine (I enabled it with OCLP). Try to see if the device properties of your GPU looks like this:

HDMI works fine for me on Sonoma 14.1, however sometimes I need to disconnect the adapter and re-connect it in order for it to be recognized by the system.

Congratulation to manage to install Sonoma but How could you upgrade because MBPro14,1 isn't upgradable for me

@MuhamadSelim MacBookPro14,1 natively supports Sonoma, so if you are not able to download it directly from the App Store you are doing something wrong.
Wifi depends on the type of card you have, if you have intel you will have to use the 2.3.0 alpha version of this: https://github.com/OpenIntelWireless/itlwm/releases
Otherwise follow this guide for other unsupported cards: https://github.com/5T33Z0/OC-Little-Translated/blob/main/14_OCLP_Wintel/Enable_Features/WiFi_Sonoma.md

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/valnoxy/t440p-oc/tree/macos-13-ventura : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to EFI
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Thanks for sharing now its working perfect on t440p

I have successfully installed ventura on my t540p laptop everything working perfect but my GPU is showing 4mb
i already followed the above steps but when i do the last to step to patch my ventura mac os and then restarts ,
after restarts the system not booting it shows me a mac os error dialog that mac os encounter some issue that is why it not booting,
so any please me that to figure out this problem

hey guys,
i installed the ventura with the patch but my touchpad is acting kinda weird for ex. when i'm moving windows it's slow and scrolling is working on the beginning but then it's stopping to work it's an t450p touchpad so maybe that the fault can anyone help with it?

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/valnoxy/t440p-oc/tree/macos-13-ventura : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."
steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install
add and enable AMFIExemption.kext to EFI
download OpenCore Configurator V<IP_ADDRESS>
open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000
config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc
open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Thanks for sharing now its working perfect on t440p

I have successfully installed ventura on my t540p laptop everything working perfect but my GPU is showing 4mb
i already followed the above steps but when i do the last to step to patch my ventura mac os and then restarts ,
after restarts the system not booting it shows me a mac os error dialog that mac os encounter some issue that is why it not booting,
so any please me that to figure out this problem

just reinstall macos and it should be gone

Hello, i am using ventura by macos-13-ventura branch , but hd 4600 gpu is only 7mb, very slow. Now I find a fix method from https://github.com/valnoxy/t440p-oc/tree/macos-13-ventura : "Use OpenCore Legacy Patcher to patch your Ventura install. This is because Apple dropped support for HD 4600 graphics with Mac OS Ventura, and unless you want a painfully slow experience on Mac OS, then this step is required."

steps detail from http://imacos.top/2022/09/26/2310/ :

download  OpenCore-Patcher and install

add and enable AMFIExemption.kext to EFI

download OpenCore Configurator V<IP_ADDRESS>

open and modify config.plist by OpenCore Configurator V<IP_ADDRESS>:

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->boot-args->add amfi_get_out_of_my_way=1

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Add->csr-active-config->modify to FF0F0000

config.plist -› nvram -› 7C436110-AB2A-4BBB-A880-FE41995C9F82 -› Delete->add csr-active-config

restart pc

open opencore-patcher.app, click 'Post-install Root Patch'->'Start Root Patching'....reboot pc....finish

finally, Intel HD Graphics 4600 7 MB to Intel HD Graphics 4600 1536 MB, gpu is normal.

Thanks for sharing now its working perfect on t440p

I have successfully installed ventura on my t540p laptop everything working perfect but my GPU is showing 4mb

i already followed the above steps but when i do the last to step to patch my ventura mac os and then restarts ,

after restarts the system not booting it shows me a mac os error dialog that mac os encounter some issue that is why it not booting,

so any please me that to figure out this problem

just reinstall macos and it should be gone

I have not seen evidence or anyone responding to proper questions on ventura or sonoma, i tried both and got working acceleration and ok performance, but firefox and brave would not work, i suspect more issues, just finished downgrade to monterey and its working with no patch, last i remember early monterey had issues so i stuck with big sur, it seems monterey is the farthest T440P/Haswell Graphics

WIFI Not Working still reviewing all

how to gpu fix on macOS Sonoma in intel 4600


Add separate CI job for slow tests

What does this PR do?
Just 1 parametrization for the moment, we can always add more later if necessary.
If I forgot to mark a specific test as slow=True, feel free to commit or comment.
Fixes #9086
Does your PR introduce any breaking changes? If yes, please list them.
None
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[n/a] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[n/a] Did you verify new and existing tests pass locally with your changes?
[x] Did you list all the breaking changes introduced by this pull request?
[n/a] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

cc @carmocca @akihironitta @borda

Not sure if it was discussed, but was it intentional to skip slow tests by default? This means locally all tests marked as slow don't run.  May I suggest to invert the current behavior?

Skipping them by default is the point of adding Slow CI, otherwise, they get to run on all jobs and we get no speedup.

You would make the default to run the slow tests and set
PL_RUN_SLOW_TESTS=0 in the regular CI and
PL_RUN_SLOW_TESTS=1 in the dedicated one.
Currently only the slow ci configuration sets the env variable.

We would need 3 values:

Run only slow tests (current PL_RUN_SLOW_TESTS=1)
Run only non-slow tests (current PL_RUN_SLOW_TESTS=0)
Run all tests. How do you propose we set it?


How to update configuration when stream is running?

Hi,
I'm currently facing an issue with the RTCMultiConnection library.
I'd like to update a connection configuration (for example, changing video stream resolution).
For example, I start a new video & audio stream:
@stream = new RTCMultiConnection(@stream_id)

@stream.isInitiator = true

@stream.open
	session:
		audio: true
		video: true

Then, I want to allow user to change his video stream resolution.
So, after a user interaction I change the resolution:
@stream.media.min someVal, someVal
@stream.media.max someVal, someVal

Unfortunately, the modifications are not applied: they must be made before opening the connection in order to be effective.
I've found a refresh function, but it looks like to behave more like a reset one.
When I try do make a @stream.refresh(), it just stops the stream and I need to reopen a new connection.
So, my question is: is it possible to make changes on the connection configuration (like muting sound or video, changing resolution, changing camera device, ...) without having to reopen a new one with the new configuration?

It isn't yet possible to switch between resolutions without renegotiating peers. However Firefox team shown interest to bring this feature soon.
Chrome requires a separate MediaStream instance to be captured with NEW configurations, and then both peers need to be "renegotiated" to make sure new RTP ports are applied.
RTCMultiConnection is having following methods that auto-performs renegotiation:

addStream
removeStream
switchStream
renegotiate
drop
hold
etc.

var videoConstraints = {
    mandatory: {
        maxWidth: 1920,
        maxHeight: 1080
    },
    optional: []
};

connection.mediaConstraints = {
    video: videoConstraints,
    audio: true
};

// It'll capture a NEW stream with modified resolutions
// it'll also quickly renegotiate peers among all connected users
connection.addStream({
    video: true,
    audio: true
});

You can even remove/stop existing stream:
connection.streams.selectFirst({ local: true }).stop();

// or
connection.removeStream({ local: true });

// or
connection.streams.stop('local');

// or
connection.removeStream('stream-id');
connection.addStream({ audio: true, video: true });

attachExternalStream is useful only when doing initial handshake.
connection.refresh isn't meant to renegotiate peers. It merely sets defaults for local-peer-only. E.g. it can stop all streams, remove all connected peers, close all sockets etc.

@muaz-khan Thank you for your answer!


Fixes for a few potential crashes and support for specifying protocols

Current coverage is 71.56% (diff: 57.89%)

Merging #29 into master will decrease coverage by 1.65%

@@             master        #29   diff @@
==========================================
  Files             6          6
  Lines           295        306    +11
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            216        219     +3
- Misses           79         87     +8
  Partials          0          0

Powered by Codecov. Last update df899dd...7be59d5

@andreasley why was this closed?

@tannernelson Found a serious bug. Fixed it, and opened a new PR: #30


Emoji Sliders don't move flush-right

Chrome 81 / Mac OS
Peeping https://jnkkkk.github.io/MoreToggles.css/allToggles.html, your "emoji" sliders will all move their icons flush to the left side, but when activated, the icons will only move about 2/3rds of the way to the right.

Reproducible for Safari 12.0.3 too

Reproducible for Safari 12.0.3 too

Reproducible for Safari 12.0.3 too

Reproducible for Safari 12.0.3 too

Reproducible for Firefox 81.0.1 too


LLJR

any ICAO code starting with "LL" is = Israel
LLJR is not an exception.
See more at : https://en.wikipedia.org/wiki/Atarot_Airport

I assume this is about LLJR and LLBS in the badStations.csv file. Let me explain why that exists.
I started with a comprehensive list of METAR reporting stations provided by NOAA ADDS at http://aviationweather.gov/docs/metar/stations.txt
This served as the master station list and has been updated over time as I cross-referenced a number of other databases to create stationList.csv with all of its additional information. However, when I started testing, I noticed that roughly 30% of those stations didn't return any data when queried. Any station that is listed in badStations.csv hasn't produced any data (according to the source, aviationweather.gov) since I started testing the pre-alpha version back in March 2015.
badStations.csv is more of a purgatory. Every couple of weeks, one of those stations will produce a report, which causes me to remove it from that list and update the server-side station database.


Heap out of bounds read - WASM_OP_I32_LOAD16_S: wasm_interp_call_func_bytecode (wasm_interp.c:1152)

Environment

Questions
Answers

Related Binary
./iwasm (linux build)

Commit
commit 9a02c49d7c2bb2012fe8d2bd2b9cb2bdaf88ba79

Vulnerability/issue
Heap out of bounds read in wasm_interp_call_func_bytecode (wasm_interp.c:1152)
case: WASM_OP_I32_LOAD16_S
Steps to reproduce the behavior

Download:
PoC.zip

Run:
./iwasm PoC.wasm

Fixed with c47baf221fa8139ee45cd31e7dbf1a8310669d8e


Prefix Cache Aware Scheduling [1/n]

TL;DR

prototype in https://github.com/vllm-project/vllm/pull/9862
addresses https://github.com/vllm-project/vllm/issues/7883
This PR makes scheduling prefix aware in V0. KV Cache utilization will remain high with high prefix cache hit.
Yielding up to 50% throughput improvement on high prefix cache hit for batch inferencing, and 25% request throughput when online serving.
It doesn't introduce e2e overheads when the workload doesn share prefix.

Background
With current impl in main, there are at least 2 places where scheduling is not optimal:

When deciding how many new tokens should be used for scheduling budget, it doesn't take into account already computed tokens.
When deciding if a sequence could be allocated for prefill, it doesn't take into account the already computed blocks.

This would result in under-utilization of KV cache, and un optimal scheduling decision for a batch.
For more details, see the https://github.com/vllm-project/vllm/issues/7883
High Level Approach
This PR addresses the issue by solving 1 only:

Make scheduling prefix cache aware: When deciding how many tokens to schedule, the already cached tokens are now also taken into account, and the scheduling budget now includes cached tokens.
The ComputedBlocksTracker will track the block hashes for a sequence and tell scheduler/block manager how many tokens have been cached given a sequence.

On a high level, there are below major changes.

Scheduler when deciding how many tokens to batch, it also takes into account new tokens that are already cached. So the scheduling budget only includes new and uncached tokens.
The scheduler gets the cached token info by asking the blockmanager which has the computed blocks tracker tracks the information for each sequence.
For each sequence, a block hash is computed twice in the current PR (once at the computed block tracker, once in the allocator). A future PR could improve this.

Throughput Benchmark
Example command
    python ~/vllm-3/benchmarks/benchmark_prefix_caching.py \
        --model meta-llama/Meta-Llama-3-8B-Instruct \
        --enable-prefix-caching \
        --use-v2-block-manager \
        --num-prompts 300 \
        --input-length-range 1000:1000 \
        --output-len 10 \
        --prefix-len $prefix_len \
        --max-num-batched-tokens 2048 \
        --enable-chunked-prefill

More details in this doc
Serving Benchmark
# Server
vllm serve meta-llama/Meta-Llama-3-8B-Instruct --disable-log-requests --enable-prefix-caching --enable-chunked-prefill

Serving Results on QPS=10

The improvement on TTFT is significant.
There's slight improvement on request throughput
There's slight degrade on ITL (likely due to more tokens from prefill in a batch)

python3 benchmarks/benchmark_serving.py --backend vllm --model meta-llama/Meta-Llama-3-8B-Instruct --dataset-name random \
--random-input-len 200 --random-output-len 30 --random-prefix-len 600 --seed 0 \
--request-rate 10 --num-prompts 500

============ Serving Benchmark Result ============
                                          PR           Main
Successful requests:                     500           500
Benchmark duration (s):                  52.01         55.42
Total input tokens:                      400000        400000
Total generated tokens:                  14831         14809
Request throughput (req/s):              9.61          9.02
Output token throughput (tok/s):         285.16        267.23
Total Token throughput (tok/s):          7976.00       7485.27
---------------Time to First Token----------------
Mean TTFT (ms):                          238.19        2193.42
Median TTFT (ms):                        209.70        2510.56
P99 TTFT (ms):                           632.90        3922.97
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          81.33         60.74
Median TPOT (ms):                        75.03         61.54
P99 TPOT (ms):                           135.80        64.79
---------------Inter-token Latency----------------
Mean ITL (ms):                           82.12         61.21
Median ITL (ms):                         62.17         62.90
P99 ITL (ms):                           285.48        116.98
==================================================

Serving Results on QPS=15
With a higher request rate (QPS=15), the improvement on TTFT and request rate will be more significant (25%)
python3 benchmarks/benchmark_serving.py --backend vllm --model meta-llama/Meta-Llama-3-8B-Instruct --dataset-name random --random-input-len 200 --random-output-len 50 --random-prefix-len 600 --seed 0 \
--request-rate 15 \
--num-prompts 500

============ Serving Benchmark Result ============
                                          PR           Main
Successful requests:                     500           500
Benchmark duration (s):                  46.94         58.66
Total input tokens:                      400000        400000
Total generated tokens:                  24685         24668
Request throughput (req/s):              10.65         8.52
Output token throughput (tok/s):         525.92        420.52
Total Token throughput (tok/s):          9048.08       7239.31
---------------Time to First Token----------------
Mean TTFT (ms):                          4797.81       11201.85
Median TTFT (ms):                        4566.95       11076.55
P99 TTFT (ms):                           10789.80      22585.37
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          160.69        64.68
Median TPOT (ms):                        170.73        65.03
P99 TPOT (ms):                           191.34        68.68
---------------Inter-token Latency----------------
Mean ITL (ms):                           161.50        65.20
Median ITL (ms):                         154.61        66.75
P99 ITL (ms):                           847.72        124.48
==================================================

Serving Results on No Prefix Shared
python3 benchmarks/benchmark_serving.py --backend vllm --model meta-llama/Meta-Llama-3-8B-Instruct --dataset-name random --random-input-len 800 --random-output-len 50 --random-prefix-len 0 --seed 0 --request-rate 10 --num-prompts 500

There's no overhead when workload has no shared prefil.

============ Serving Benchmark Result ============
                                          PR           Main
Successful requests:                     500           500
Benchmark duration (s):                  127.43        127.65
Total input tokens:                      400000        400000
Total generated tokens:                  24350         24350
Request throughput (req/s):              3.92          3.92
Output token throughput (tok/s):         191.08        190.76
Total Token throughput (tok/s):          3330.05       3324.43
---------------Time to First Token----------------
Mean TTFT (ms):                          36577.91      36610.46
Median TTFT (ms):                        36444.46      36417.98
P99 TTFT (ms):                           73755.41      73895.10
-----Time per Output Token (excl. 1st token)------
Mean TPOT (ms):                          144.37        144.74
Median TPOT (ms):                        143.66        143.89
P99 TPOT (ms):                           302.23        302.97
---------------Inter-token Latency----------------
Mean ITL (ms):                           142.62        142.98
Median ITL (ms):                         143.56        143.77
P99 ITL (ms):                           286.82        287.27
==================================================

Updates

Added integration test for prefix caching with fully (and partially) cached prompts.

lol - fml, i hate DCO.

Updates

Added test to make sure each scheduled sequence contributes at least one token in the budget (a fully cached prompt should not be scheduled with 0 uncached token).


Add new Event for Codeunit: Calendar Management, Function CheckDateStatus

Hi,
Can the following event please be added to:
Codeunit 7600 "Calendar Management"
Function: CheckDateStatus
New Event:
OnCheckDateStatusAfterCombineChanges(var TargetCustomizedCalendarChange: Record "Customized Calendar Change"; TempCustChange: Record "Customized Calendar Change")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Improvements

Related issues #20 #33
Changes:

Removed "Add Alamofire" option
Removed "Use Storyboards" option
Fixed echo message in install.sh
Update SwiftLint and SwiftGen versions
Update .swiftlint.yml file
Update Makefile
Add SwiftGen usage
Add Assets.swift, Fonts.swift, Strings.swift
Changed name of Screens folder to UserStories
Update README.md

@gregoryvit Hello 🤺


Delegate measurement information to TCG standards

Hi y'all, I'm not particularly familiar with this format but did learn from Jon Lange on the SVSM call that this is carrying measurement-specific data. I'd like to see what we can do about delegating those measurement specifics to the reference integrity manifest (RIM) information model that you can feed through the SP800155 unmeasured event type. The IETF is working on standardizing a CBOR-based actualization of the information model to deprecate the signed XML format the TCG previously specified, which they call CoRIM.
If IGVM can be expanded to specify QemuFwCfg file contents, then we can pass along signed IGVM measurement information to the user through a standard channel via the tcgSp800155PlatformIdEvent3 unmeasured event added in the TCG PC Client Platform Firmware Profile Version 1.06 Revision 52. Say we pass in the events via etc/sp800155evts, vis a vis https://github.com/tianocore/edk2/pull/5738.
I don't know how "generic" IGVM needs to be, since QemuFwCfg is something we use in our non-Qemu VMM at Google. Is this something y'all think is within IGVM's scope?

I'm not too familiar with QemuFwCfg files, how do those get exposed from the host to the guest? Are those via some shared guest physical address, or exposed through something else? I could see us describing some payload data that the host could report via QemuFwConfig via some new header type, as long as we define it as optionally ignored for platforms that do not need/support it.
I'm not against adding standard measurement information to the file. The intention of IGVM is that it's host virtstack and guest OS generic, so if there's some TCG measurement log that's based on the initial contents of guest memory and cpu state, then I think we could include it.
What does CBOR mean?

QemuFwCfg is not entirely necessary to be part of the specification of IGVM so long as the intended meaning of the data blob is in-tact. We need some unmeasured channel for providing the SP800-155 information to the TCG or CC event log. The format of that data I've kept as a mix between the UEFI Platform Initialization definition of an EFI_HOB_GUID_TYPE and the TCG PC Client Platform Firmware Profile definition of a TCG_Sp800_155_PlatformId_Event2 or TCG_Sp800_155_PlatformId_Event3 just for the read into a created hob to avoid having to allocate temporary memory before populating the hob data. It is a bit redundant as a representation since it will always have HobType = 4 and Guid = gTcg800155PlatformIdEventHobGuid.
If the goal is not to even reference UEFI, then the TPM firmware profile for UEFI is irrelevant. Still it would be nice to at least have some notion of reference values that can be passed along however the host virt stack determines. I don't see the virt stack independence respected given the all the Vbs specifics in the implementation. I would more expect to see a Content Media type and a binary blob in something tagged "reference measurements" for the virt stack to interpret.

I think i've misunderstood - you're proposing we embed QemuFwCfg (it's like a defined filesystem format/volume) for the host to be associated with a given IGVM file? And in that, a file builder could put whatever it wants (like measurements, TCG logs, etc)? And this isn't related to the launch context of the guest?

The QemuFwCfg is an implementation detail for the VMM to provide some configuration values post-launch through a relatively simple interface https://github.com/tianocore/edk2/blob/master/OvmfPkg/Library/QemuFwCfgLib/QemuFwCfgLib.c
So for a firmware to express that it should be presented with this SP800155 data through a specific protocol that Qemu (and other VMMs) implements, I'm not sure how we express that with IGVM. The implementation itself is expecting this data, but the implementation may be implemented to expect any number of protocols depending on the host VMM it's able to determine through a protocol.
At the most basic level, I'd like for signed measurements to be expressible in some earmarked blob with a given content type so the hypervisor can extract whatever meaning it needs from it to pass along that information about the firmware it's launching.

I think there's two orthogonal questions/decisions here:

Report an industry standard measurement (CoRIM?) via a new header type for any given platform.
Add the ability to embed a QemuFwCfg (or some sort of filesystem?) for arbitrary data the host can use, and also potentially expose to the guest, via a new header type.

I think that (1) is completely reasonable and great to include. I'm not yet sold on (2). For this specific usecase, couldn't the VMM decide what it wants to expose if it had access to (1)?

Yes, I think I'm only really asking for something like (1), but not even require a format. The header would indicate the section is meant for measurements, and it has an optional string for the format as an IANA Media Type, and the payload as a byte string.

I think for MeasurementType I'd have MediaType(String) instead of CoRIM, SomeOtherFormat in order for the payload to be more open-ended without needing to change the IGVM representation at all. Note CoRIM is planned to have IANA assign the media type application/corim-signed+cbor

At that point, should we just say "This header describes a null terminated string in the file_data section to be parsed as JSON/something/whatever, intended to be used for measurement"?

I don’t expect the payload to be a null-terminated string, no. But the header is meant for signed reference measurements.

While we provide a rust interface to the standard via igvm ultimately the structures are binary defined by igvm_defs. I guess the string need not be null terminated, we could encode both the starting file_offset and length.
I think I've misunderstood though, you want both the identifier to be a string, and then the payload to be variable length, and it for to be just for measurements? So the string would define the measurement type (id of some sorts), then the payload would be up to the loader to figure out how to parse that, and I assume we'd link to some common types for given names with their corresponding specification?

Correct

Sorry back from vacation now - do you want to propose a draft PR to igvm_defs or would you like me to? I should be able to find some time for this later this week.


[BUG]error read ECONNRESET :bug:

window X64系统下报bug
重现bug步骤:

npm install -g yarn
yarn

此时出现bug
error read ECONNRESET
    at exports._errnoException (util.js:1018:11)
    at TLSWrap.onread (net.js:568:26)
info Visit http://yarnpkg.com/en/docs/cli/install for documentation about this comma
nd.

You might have guessed it already: it's a connection error.
"ECONNRESET" means the other side of the TCP conversation abruptly closed its end of the connection. This is most probably due to one or more application protocol errors. You could look at the API server logs to see if it complains about something.
参考：https://stackoverflow.com/questions/17245881/node-js-econnreset


Add stubs for RMSE and RMSLE in sklearn.metrics

Updates sklearn.metrics stubs with changes introduced in v1.4 in https://github.com/scikit-learn/scikit-learn/pull/26734
Originally wanted to mark old function parameters are deprecated, but i guess that isn't possible until PEP702
Related issue from pylance: https://github.com/microsoft/pylance-release/issues/6410

@microsoft-github-policy-service agree

Originally wanted to mark old function parameters are deprecated, but i guess that isn't possible until PEP702

That sounds good to me! deprecated() is available to Python 3.12 and below via the typing_extensions module. See https://peps.python.org/pep-0702/#backwards-compatibility.
I took the liberty of making this change in your branch.

Thanks for your contribution @einarwar!


Docs fix linting

The linter is reporting that we have bold **foo** where we should have headings ### foo
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[x] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Multiple instances, no Shared Models

Sorry I'm light on detail but I've spent quite a lot of time searching.
Also I'm not sure this isn't a sequelize problem.
Versions

sequelize: 5.21.7
sequelize-typescript: 1.1.1
typescript 3.8.3

I'm submitting a ...

[ x] bug report
[ ] feature request
Actual behavior:
We're attempting to use sequelize-typescript with multiple databases.
We are using 2 instances (instance 1 and instance 2) of  sequelize-typescript with different configurations and everything appears to be correct.
We have many models for instance 1 and only one model (modelA) for instance 2 . No models are in both instances.
We've been logging the sequelize object attached to modelA and it appears to be using the correct sequelize instance.
However we are consistently(but not always) running into and error where the table linked to modelA is not found and the sequelize error shows that it's looking at db1 instead of db2.
Expected behavior:
No missing table error when using a second database/instance.
Any information is much appreciated.

The issue was we had the model nested inside a transaction. Ooooops!


Split Presentation Files

Thought we could use issues to share ideas?
Should we split the presentations up? I can see the single file getting huge and unwieldy. If you think it's a good idea, I'll do it and close this. Or, just close this if you think it's lame.

We'll keep it one big file - with comment section separators. Will make it easy for people to download and view without running a web server.


Continue #652 (CI)

This continues

#652

after fixing a problem with src/plfa/part2/fixpoint-old/*.lagda.md:

#656

A new race condition surfaced that is not connected to .agdai files ,see run https://github.com/andreasabel/plfa.github.io/runs/6691178569?check_suite_focus=true#step:17:710
  updated src/plfa/part3/Soundness.lagda.md
site: _site/LambdaFixpoint/index.html: openFile: resource busy (file is locked)
make: *** [Makefile:58: build] Error 1
Error: Process completed with exit code 2.

@wadler @wenkokke Please push the button to run the workflow.

The workflow failed due to an expired hackage-server certificate:

https://github.com/haskell/hackage-server/issues/834

Should be resolved now, so you can try running it again...


官网图表示例报错

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link
https://g6.antv.vision/zh/examples/case/graphDemos#christmasBubbles
Steps to reproduce
g6官网 =》 图表示例 =》 任意图表

Environment
Info

g2
4.1.31

System
-

Browser
-

已经修复了，请清空缓存刷新试试


Possibility of integrating otel-profiling-agent as a library

Thank you for developing such an amazing profiling agent!
I am interested in integrating this project into other eBPF projects to support unwinding for multiple languages, replacing the bpf_get_stackid() helper function. Due to the complex architecture of this project, I would prefer not to fork the code and create my own version. However, it seems that this project does not account for being called by other eBPF programs.
Considering that the eBPF part of this project requires significant assistance from the userspace agent (such as extracting eh_frame information), I envision two possible integration methods:

The userspace component of otel-profiling-agent runs as an independent daemon process, providing the necessary support for the eBPF part. Other projects could obtain a file descriptor pointing to native_tracer_entry from the daemon process and use eBPF extensions or tail calls to invoke it on the eBPF side, similar to calling bpf_get_stackid(). The daemon process would then provide an API for reading the required call stack information.

Other Golang projects integrate otel-profiling-agent as a package, with this package creating separate threads to maintain the information needed for the eBPF program at runtime. This approach might be easier in terms of interaction but less friendly for projects written in languages other than Go.

What do you think about this? I am curious if you are interested in making the unwinder part of this project a general-purpose component. If some work is needed to achieve this, I am more than willing to help.

Hi @i-Pear
Thank you for your interest in this project. At the moment we are focusing and working on donating this project to OTel. In general it should be already possible to use this project as dependency. One can take this projects main.go as an example and start and load the components.
Overall I think there is one limitation: As this project is using BPF_PROG_TYPE_PERF_EVENT eBPF programs and so custom triggers also need to be able to call this eBPF program type.

Hi,
I am one of the Inspektor Gadget maintainers (a CNCF project that would benefit from opentelemetry-ebpf-profiler's stack unwinding abilities). I am new to opentelemetry-ebpf-profiler.
We discussed this topic in the OTel Profiling SIG Meeting today. I talked about the integration method number 1 from above (also described in https://github.com/inspektor-gadget/inspektor-gadget/pull/3457). The feedback I gathered was:

It should be technically feasible.
It would make sense for Open Source to enable component reuse.
But we should consider maintainability. The OpenTelemetry project has a specific scope: mainly profiling and distributed traces. Being consumed by a third-party project that does not fit this scope should not distract OpenTelemetry from its focus. However, other projects under the OpenTelemetry umbrella would benefit from reusability of opentelemetry-ebpf-profiler's ebpf programs to unwind stacks in uprobes, for example ebpf programs that look up distributed traces.
It should be discussed in a github issue for people who are not in the meeting. So here it is :)

Hey,
I just wanted to introduce myself as Alban did. I am one of the maintainers of Kubescape, a Kubernetes security project under the CNCF/LF umbrella. I/we are also contributing to Inspektor Gadget and in general using eBPF for security observability.
I agree with @alban on the points he recorded in the previous comment. The only thing I'd open is the way of integration with the profiling agent.
Correct me if I am wrong, but as I see, options no. 1 and no. 2 are not mutually exclusive.
Projects, that use Go should be able to enjoy the benefits of the ecosystem if it doesn't create extra burden.
cc: @florianl @i-Pear

options no. 1 and no. 2 are not mutually exclusive.
Projects, that use Go should be able to enjoy the benefits of the ecosystem if it doesn't create extra burden.

@slashben I also think both options are viable, each with its own advantages.
Option 1 may focus more on "isolation," as the profiler requires some userspace agent threads to assist the eBPF program. If the profiler and other applications are compiled into the same process, I'm not sure if this would impose limitations on syscalls like fork. Additionally, if there are many containers in a k8s cluster that rely on the profiler, the "profiler as a service" design of Option 1 could save resources.
The clear advantage of Option 2 is the elimination of communication overhead, as there would be no need to design a complex protocol. It also allows for easier and deeper customization. Moreover, the tailcall in Option 1 doesn’t seem to have been proven feasible for all types of eBPF programs, so Option 2 might offer better compatibility.
For the Inspektor Gadget project, another reason to favor Option 1 is that IG has disabled CGO, while the profiler heavily relies on this feature.

Hey @florianl @alban @i-Pear @slashben see our proposal in the attached PR https://github.com/open-telemetry/opentelemetry-ebpf-profiler/pull/192 we would be happy to get your feedback.


chore(main): release 0.7.1

:robot: I have created a release beep boop
0.7.1 (2023-10-23)
Bug Fixes

add missing ROS2 support for the Relay NetApp (#214) (96f74ba)
use PAT for release-please workflow (45a327a)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/5G-ERA/middleware/releases/tag/v0.7.1 :sunflower:


HADOOP-18364. All method metrics related to the RPC protocol should be …

…initialized.

Description of PR
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[x] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[x] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 36s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 1 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m 30s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 28s

trunk passed

+1 :green_heart:
compile
23m 14s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 46s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 23s

trunk passed

+1 :green_heart:
mvnsite
4m 29s

trunk passed

+1 :green_heart:
javadoc
3m 33s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 43s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 10s

trunk passed

+1 :green_heart:
shadedclient
24m 27s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 34s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 31s

the patch passed

+1 :green_heart:
compile
22m 22s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
22m 22s

the patch passed

+1 :green_heart:
compile
20m 44s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
20m 44s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 15s

the patch passed

+1 :green_heart:
mvnsite
4m 29s

the patch passed

+1 :green_heart:
javadoc
3m 27s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 42s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 24s

the patch passed

+1 :green_heart:
shadedclient
24m 35s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 46s

hadoop-common in the patch passed.

-1 :x:
unit
237m 41s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
2m  0s

The patch does not generate ASF License warnings.

486m 46s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.TestDataNodeMetrics

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4624

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 842aa1926d81 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 90286d6b3db325d87c966d61c2bcad97dfeec231

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/1/testReport/

Max. process+thread count
3455 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
11m 33s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  5s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 45s

trunk passed

+1 :green_heart:
compile
26m 51s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
23m 30s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 29s

trunk passed

+1 :green_heart:
mvnsite
4m 28s

trunk passed

+1 :green_heart:
javadoc
3m 29s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 35s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 18s

trunk passed

+1 :green_heart:
shadedclient
24m 29s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 35s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 40s

the patch passed

+1 :green_heart:
compile
26m  9s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
26m  9s

the patch passed

+1 :green_heart:
compile
23m 33s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
23m 33s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  8s

the patch passed

+1 :green_heart:
mvnsite
4m 22s

the patch passed

+1 :green_heart:
javadoc
3m 17s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 30s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 32s

the patch passed

+1 :green_heart:
shadedclient
24m 20s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m 13s

hadoop-common in the patch passed.

+1 :green_heart:
unit
251m 31s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 44s

The patch does not generate ASF License warnings.

524m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4624

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux a5c28852edfb 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b79ea582bb34751ed8073ec77f2bcb1e9d82038e

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/3/testReport/

Max. process+thread count
2958 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/3/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
14m  5s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  4s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
26m 45s

trunk passed

+1 :green_heart:
compile
26m 59s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
23m 22s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 27s

trunk passed

+1 :green_heart:
mvnsite
4m 30s

trunk passed

+1 :green_heart:
javadoc
3m 31s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 36s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 21s

trunk passed

+1 :green_heart:
shadedclient
24m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 34s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 39s

the patch passed

+1 :green_heart:
compile
26m  6s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
26m  6s

the patch passed

+1 :green_heart:
compile
23m 27s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
23m 27s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m  9s

the patch passed

+1 :green_heart:
mvnsite
4m 23s

the patch passed

+1 :green_heart:
javadoc
3m 22s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 35s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 34s

the patch passed

+1 :green_heart:
shadedclient
24m 47s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
19m 10s

hadoop-common in the patch passed.

+1 :green_heart:
unit
252m 21s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
1m 45s

The patch does not generate ASF License warnings.

528m 18s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4624

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux fa11e2d1abb2 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / b79ea582bb34751ed8073ec77f2bcb1e9d82038e

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/2/testReport/

Max. process+thread count
2988 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 37s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 2 new or modified test files.

_ trunk Compile Tests _

+0 :ok:
mvndep
15m  4s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
25m 31s

trunk passed

+1 :green_heart:
compile
23m 10s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
20m 47s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
4m 23s

trunk passed

+1 :green_heart:
mvnsite
4m 29s

trunk passed

+1 :green_heart:
javadoc
3m 34s

trunk passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 39s

trunk passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m  8s

trunk passed

+1 :green_heart:
shadedclient
24m 33s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 33s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
2m 29s

the patch passed

+1 :green_heart:
compile
22m 58s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
22m 58s

the patch passed

+1 :green_heart:
compile
22m 41s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
22m 41s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
4m 39s

the patch passed

+1 :green_heart:
mvnsite
4m 26s

the patch passed

+1 :green_heart:
javadoc
3m 27s

the patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
3m 44s

the patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
7m 24s

the patch passed

+1 :green_heart:
shadedclient
24m 41s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
18m 46s

hadoop-common in the patch passed.

+1 :green_heart:
unit
241m 46s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
2m  2s

The patch does not generate ASF License warnings.

493m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/4/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4624

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d905ff185b25 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 448f038518c29c90988310ba5b70961e8ec17184

Default Java
Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/4/testReport/

Max. process+thread count
3341 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-common hadoop-hdfs-project/hadoop-hdfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4624/4/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@xkrogen Would you mind to take another review? I will to check in this PR after you confirm. Thanks.

Committed to trunk. Thanks @zhangshuyan0 for your works. Thanks @sunchao, @xkrogen for your nice reviews!


golang 1.7 upgrade to importpath.name=value, do we need support 1.7

141:~/gocode/src/github.com/hyperhq/hyperd: make
make[1]: 进入目录“/home/vagrant/gocode/src/github.com/hyperhq/hyperd”
go build -tags "static_build   libdm_no_deferred_remove exclude_graphdriver_btrfs" -ldflags "-X github.com/hyperhq/hyperd/utils.VERSION 0.6.2" hyperd.go
# command-line-arguments
/usr/local/go/pkg/tool/linux_amd64/link: -X flag requires argument of the form importpath.name=value
make[1]: *** [build-hyperd] 错误 2
make[1]: 离开目录“/home/vagrant/gocode/src/github.com/hyperhq/hyperd”
make: *** [all-recursive] 错误 1

i am not sure upstream want to upgrade compiler to go 1.7.
go build -tags "static_build   libdm_no_deferred_remove exclude_graphdriver_btrfs" -ldflags "-X github.com/hyperhq/hyperd/utils.VERSION 0.6.2"

the -X key/value should be update to key=value. it can fix the conflict


Server Side Render - Inconsistent IndexLink

Using the current example for SSR.
The server is adding an extra route into the activeRoutes array. This is making the isActive call incorrectly check against which route holds an indexRoute.
Server:
activeRoutes =
   [ { history: undefined, childRoutes: [Object] },
     { path: '/',
       component: [Function: App],
       indexRoute: [Object],
       childRoutes: [Object] },
     { component: [Function: Home] } ]

Client:
activeRoutes: Array[2]
  0: Object
    childRoutes: Array[1]
    component: App()
    indexRoute: Object
    path: "/"
  1: Object
    component: Home()
  length: 2

It was working for me just fine before this line of code changed:
https://github.com/rackt/react-router/pull/2113/files#diff-3b9d7063d56e0abf361937d8f540ff52L51
This is my current setup:
"react": "^0.14.0",
"react-dom": "^0.14.0",
"react-router": "^1.0.0-rc3",
"history": "^1.9.1",

  <Router history={history}>
    <Route path='/' component={App}>
      <IndexRoute component={Home}/>

    const { url } = this.request;
    match({ routes, location: url }, (error, redirect, renderProps) => {
      <RoutingContext {...renderProps}/>

class HeadNavigation extends React.Component {
  render() {
    return (

        <IndexLink to='/' activeClassName={styles.active}>
          Home
        </IndexLink>

Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) 3k.0.0.0"><a class="" href="/" data-reac

NB: Other Links work fine for the active class on the servr! It's just the IndexLink

This is probably fixed by #2237.

I'm closing this as fixed by #2237.

Has this been pushed to npm? As I can't install from github and the current NPM react-router-rc3 still has the exact same problem.

Not yet. It'll be in RC4 whenever that comes out.


Add accuracy to histograms

Add accuracy to the class DPHistogramSpec

location: opendp_apps.analysis.tools.dp_histogram_spec

from @ecowan: We don't yet have a geometric_scale_to_accuracy function like we have for laplacian noise, I'll check in with the rest of the team about this

closing, part of #423


Remove bp3-intent styling overrides for buttons

Fix to unwind changes that caused button group input styling to break.
Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[x] Caught up with develop branch as of last change.
[x] Added CHANGELOG entry, or determined not required.
[x] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[x] Updated doc comments / prop-types, or determined not required.
[N/R] Reviewed and tested on Mobile, or determined not required.
[x] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

FYI we will see if we can land a fuller resolution via #2016 - reviewing that now - but thank you Petra for teeing this up in case we end up needing more time on the bigger improvement/fix.
Will keep this open for now as well and merge one or the other ASAP to get to a good release candidate.