Use TLS for secure docker connection

By #177 、 docker cmd in runner container use tcp connection to communicate with dockerd in dind container, and this connection is not encrypted.
This PR adds configuration to encrypt the connection.
ref: https://github.com/docker-library/docker/issues/170#issuecomment-514366149

Oops, I mistakenly closed this PR and I have not noticed.

resolved conflicts

Note that this seem to break ghaction-docker-buildx@v1.
Hopefully this can be fixed by migrating to docker's own buildx action in https://github.com/summerwind/actions-runner-controller/pull/197

crazy-max/ghaction-docker-buildx@v1
  with:
    buildx-version: latest
    qemu-version: latest
✅ Buildx version found: v0.4.2
⬇ Downloading https://github.com/docker/buildx/releases/download/v0.4.2/buildx-v0.4.2.linux-amd64...
🔨 Fixing perms...
📣 Buildx info
/usr/local/bin/docker buildx version
github.com/docker/buildx v0.4.2 fb7b670b764764dc4716df3eba07ffdae4cc47b2
⬇ Downloading qemu-user-static Docker image...
/usr/local/bin/docker pull -q multiarch/qemu-user-static:latest
docker.io/multiarch/qemu-user-static:latest
💎 Installing QEMU static binaries...
/usr/local/bin/docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
Setting /usr/bin/qemu-alpha-static as binfmt interpreter for alpha
Setting /usr/bin/qemu-arm-static as binfmt interpreter for arm
Setting /usr/bin/qemu-armeb-static as binfmt interpreter for armeb
Setting /usr/bin/qemu-sparc-static as binfmt interpreter for sparc
Setting /usr/bin/qemu-sparc32plus-static as binfmt interpreter for sparc32plus
Setting /usr/bin/qemu-sparc64-static as binfmt interpreter for sparc64
Setting /usr/bin/qemu-ppc-static as binfmt interpreter for ppc
Setting /usr/bin/qemu-ppc64-static as binfmt interpreter for ppc64
Setting /usr/bin/qemu-ppc64le-static as binfmt interpreter for ppc64le
Setting /usr/bin/qemu-m68k-static as binfmt interpreter for m68k
Setting /usr/bin/qemu-mips-static as binfmt interpreter for mips
Setting /usr/bin/qemu-mipsel-static as binfmt interpreter for mipsel
Setting /usr/bin/qemu-mipsn32-static as binfmt interpreter for mipsn32
Setting /usr/bin/qemu-mipsn32el-static as binfmt interpreter for mipsn32el
Setting /usr/bin/qemu-mips64-static as binfmt interpreter for mips64
Setting /usr/bin/qemu-mips64el-static as binfmt interpreter for mips64el
Setting /usr/bin/qemu-sh4-static as binfmt interpreter for sh4
Setting /usr/bin/qemu-sh4eb-static as binfmt interpreter for sh4eb
Setting /usr/bin/qemu-s390x-static as binfmt interpreter for s390x
Setting /usr/bin/qemu-aarch64-static as binfmt interpreter for aarch64
Setting /usr/bin/qemu-aarch64_be-static as binfmt interpreter for aarch64_be
Setting /usr/bin/qemu-hppa-static as binfmt interpreter for hppa
Setting /usr/bin/qemu-riscv32-static as binfmt interpreter for riscv32
Setting /usr/bin/qemu-riscv64-static as binfmt interpreter for riscv64
Setting /usr/bin/qemu-xtensa-static as binfmt interpreter for xtensa
Setting /usr/bin/qemu-xtensaeb-static as binfmt interpreter for xtensaeb
Setting /usr/bin/qemu-microblaze-static as binfmt interpreter for microblaze
Setting /usr/bin/qemu-microblazeel-static as binfmt interpreter for microblazeel
Setting /usr/bin/qemu-or1k-static as binfmt interpreter for or1k
🔨 Creating a new builder instance...
/usr/local/bin/docker buildx create --name builder-47a7fa61fce1dab9962566ddb987849389286bb5 --driver docker-container --use
could not create a builder instance with TLS data loaded from environment. Please use `docker context create <context-name>` to create a context for current environment and then create a builder instance with `docker buildx create <context-name>`
Error: The process '/usr/local/bin/docker' failed with exit code 1

Okay even docker's own setup-buildx-action doesn't work 😇

Run docker/setup-buildx-action@v1
👉 Installing Buildx
📣 Buildx version: 0.4.2
🔨 Creating a new builder instance
  /usr/local/bin/docker buildx create --name builder-build-2 --driver docker-container --driver-opt image=moby/buildkit:v0.8-beta --buildkitd-flags --allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host --use
  could not create a builder instance with TLS data loaded from environment. Please use `docker context create <context-name>` to create a context for current environment and then create a builder instance with `docker buildx create <context-name>`
  Error: The process '/usr/local/bin/docker' failed with exit code 1

Seems this is exactly what https://github.com/docker/buildx/issues/413 says

You can reproduce https://github.com/docker/buildx/issues/413 on the runner container by running the below steps:
$ mkdir -p ~/.docker/cli-plugins/
$ curl -L -o ~/.docker/cli-plugins/docker-buildx https://github.com/docker/buildx/releases/download/v0.4.2/buildx-v0.4.2.linux-amd64
$ chmod ~/.docker/cli-plugins/docker-buildx
$ docker --help | grep buildx
  buildx*     Build with BuildKit (Docker Inc., v0.4.2)
$ docker buildx create --name builder-build-2 --driver docker-container --driver-opt image=moby/buildkit:v0.8-beta --buildkitd-flags "--allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host --use"
could not create a builder instance with TLS data loaded from environment. Please use `docker context create <context-name>` to create a context for current environment and then create a builder instance with `docker buildx create <context-name>`

In nutshell, you need to pass the valid docker context that has all the TLS settings inherited from envvars.
In the following example, we add buildx to docker buildx create 's first argument, which corresponds to a docker context created by docker context create buildx:
$ docker buildx create buildx --name builder-build-2 --driver docker-container --driver-opt image=moby/buildkit:v0.8-beta --buildkitd-flags "--allow-insecure-entitlement security.insecure --allow-insecure-entitlement network.host" --use
builder-build-2

$ docker buildx build --load .
WARN[0000] invalid non-bool value for BUILDX_NO_DEFAULT_LOAD:
[+] Building 10.1s (7/7) FINISHED
 => [internal] booting buildkit                                                                      4.9s
 => => pulling image moby/buildkit:v0.8-beta                                                         4.2s
 => => creating container buildx_buildkit_builder-build-60                                           0.7s
 => [internal] load build definition from Dockerfile                                                 0.0s
 => => transferring dockerfile: 56B                                                                  0.0s
 => [internal] load .dockerignore                                                                    0.0s
 => => transferring context: 2B                                                                      0.0s
 => [internal] load metadata for docker.io/library/alpine:latest                                     3.7s
 => [1/1] FROM docker.io/library/alpine:latest@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7df  1.1s
 => => resolve docker.io/library/alpine:latest@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7df  0.0s
 => => sha256:188c0c94c7c576fff0792aca7ec73d67a2f7f4cb3a6e53a84559337260b36964 2.80MB / 2.80MB       1.1s
 => exporting to oci image format                                                                    1.3s
 => => exporting layers                                                                              0.0s
 => => exporting manifest sha256:4567b80f4b7d8f139e9574aaa0850c8c4d89cc36b40f973902eab249492a78c6    0.0s
 => => exporting config sha256:8d19be48f0403c567476dc8607fc05eeb8a33846798029f7b4bd2e94f3ee331f      0.0s
 => => sending tarball                                                                               0.1s
 => importing to docker                                                                              0.0s

The below is the workflow config change you need in order to use setup-buildx-action after this TLS secured docker connection change:
https://github.com/mumoshu/actions-runner-controller-ci/commit/e91c8c0f6ca82aa7618010c6d2f417aa46c4a4bf
I have no confidence if this should bother setup-buildx-action. Please open issues/pull requests to the setup-buildx-action if you think it's better supported there.


feat: send status logs to paloma

Related Github tickets

https://github.com/palomachain/paloma/pull/981

Background
This enables pigeons to send status updates to Paloma, which will be caught by nodes and stored in the default log output (not on chain). It's intended to be used mainly to add further observability into some edge cases that would previously not flare up on any logs.
Testing completed

[x] test coverage exists or has been added/updated
[ ] tested in a private testnet

Breaking changes

[x] I have checked my code for breaking changes

I'm not entirely sure how this would be tested in private test net, but I feel fairly confident with these changes, as there's no additional logic flow for error handling, and the client calls are caught in mock testing.


ReadInt32 with not aligned byte

Hi,
I'm not sure but I think the method bitReader in the class Int32 is wrong.
My fix is on the masks. I think it should be :
		$hiMask = $bitmask->getMask($br->getCurrentBit(), BitMask::MASK_LO) ^ 0xFF;
		$loMask = $bitmask->getMask($br->getCurrentBit(), BitMask::MASK_HI) ^ 0xFF;

Case :
Buffer :
FF 07 00 00 00
Position : 1 (2nd byte)
Current bit : 2
Nest Byte : FF
Try to read int32.
The masks are :
hiMask : 00111111
loMask : 00000011
But should be :
hiMask : 11111100
loMask : 11000000
The result will be<PHONE_NUMBER><PHONE_NUMBER>11000000000000000000) and should be<PHONE_NUMBER><PHONE_NUMBER>0111000000000000000000).

Correction, the low mask is correct and should not be changed.
		$loMask = $bitmask->getMask($br->getCurrentBit(), BitMask::MASK_LO);


[UI/UX] UI design of slide progress bar of storymap

Description
slide progress bar feature was added via https://github.com/UNDP-Data/geohub/pull/3886, UI might need to be improved

UI of slide progress bar (color, size of handle, etc)

progress bar is using svelte-range-slider component, the styling option is available https://simeydotme.github.io/svelte-range-slider-pips/en/styling

UI of slide progress bar setting

Screenshots
current progress bar screenshots

slide progress bar

slide progress bar setting

Mockup URL/file
No response

Storymap Viewer
Storymap Setup


Unhandled exception raised while initializing the Google translate menu

Overview
An unhandled exception is raised while initializing the Google translate menu on what appears to be a small number of requests
Expected Behavior
No unhandled exceptions are raised while initializing the Google translate menu
Actual Behavior
An unhandled exception is raised while initializing the Google translate menu on what appears to be a small number of requests
Steps to Reproduce
We only have Rollbar telemetry
Additional context
Possibly related to #414
View details in Rollbar: https://rollbar.com/OpenApparelRegistry/OpenApparelRegistry/items/36/

TypeError: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'.
  File "https://openapparel.org/", line 1, in googleTranslateElementInit
  File "https://translate.googleapis.com/element/TE_20181015_01/e/js/element/element_main.js", line 476, in e

Opening each of the page URLs for the most recent Rollbar exceptions (which are all embedded maps) shows this error in the console: Failed to execute 'observe' on 'MutationObserver': parameter 1 is not of type 'Node'. at googleTranslateElementInit. This might be because we don't render the header, which is where the Google Translate element is stored, in embed mode, but still are attempting to set an observer on the translate element.


why too much bloat options.

can you simply make three options :
download in best quality audio. (audio only)
download in best video. (video only)
donwload in best audio+video.
less is more.

yt-dl fetches streams that are provided by the supported site, These may be audio-only, video-only, or combined video+audio. Depending on the site and selected page, the "best" audio or video may be a combined stream. So:

download in best quality audio. (audio only)

Use -x/--extract-audio.

download in best video. (video only)

Use -f bestvideo/best and then strip any unwanted audio stream using ffmpeg if you really want.

donwload in best audio+video.

-f bestvideo+bestaudio/best (the default).


Python workspace interpreter doesn't select virtualenv interpreter

VSCode Version: 1.16.0
OS Version: MacOS Sierra
Python version: 3.6
pip: 3
virtualenv: 3
extension: https://github.com/DonJayamanne/pythonVSCode/wiki

The Python workspace interpreter doesn't select the virtualenv interpreter, it can't even locate it. Also there isn't a possibility of doing it manually, as it wouldn't save. I'm stuck with system wide interpreter so I cannot locate local virtualenv dependencies.

Is this an issue with the Python extension? Can you open the issue in that repo if so?

@roblourens can you forward this issue to that extension like you did with Microsoft/vscode#33988 ?

This issue was moved to DonJayamanne/pythonVSCode#1198


Convert DataTable to use table reader

Changes DataTable to accept tabular data. It still supports a list of structs and we ignore any underscored attributes. It no longer recognises Ecto structs, so now all the Ecto stuff is encapsulated in Kino.Ecto.

It still supports a list of structs and we ignore any underscored attributes. It no longer recognises Ecto structs, so now all the Ecto stuff is encapsulated in Kino.Ecto.

Wait, we still handle structs, so we handle Ecto structs. What would be missing?

@josevalim yeah, I just meant that we don't use the schema information, they would still be rendered as any other struct :)

I think it's still useful because of the pagination, sorting and type information. I think it would make sense to move it elsewere, but we can discuss that once we start splitting into multiple packages.

For the record Kino.Ecto uses @behaviour Kino.Table, so unless we have all table things in a single package, we may need to make the behaviour public.


Edge not uninstalling

Describe the bug
Upon using this tool I've ticked Edge, and pressed the uninstall button in the top
To Reproduce
Steps to reproduce the behavior:

Open the tool
Tick Edge and click the uninstall button on the top
Script is executing
Error:

Found Microsoft Edge [Microsoft.Edge]
Starting package uninstall...
Uninstall failed with exit code: 93
Expected behavior
Edge to be uninstalled
Screenshots

Additional context
.

Fixed in commit b2e3def

This is failing for me now on latest Windows 11 pro update, same error, using latest version of your tool

Ahh actually it's only broken in the Install tab. If I choose Edge and click the uninstall button I get the error 93, but when I selected Remove Microsoft Edge in the Tweaks tab, it popped open a new shell window with a blue background, ran some other script and successfully uninstalled it.
So I assume the fix in that commit only changed the Tweaks tab.

Can confirm that uninstalling from the Install tab still yields error 93.
Runnning it from the Tweaks tab gives an OK, but Edge is still there and is able to run. Running it a 2nd time gives:
"WARNING: A runtime exception occurred.
WARNING: This command cannot be run due to the error: The system cannot find the file specified."
The reason I tried this tool is because the other uninstall method (running "setup.exe --uninstall --system-level --verbose-logging --force-uninstall") doesn't seem to work anymore. Might those 2 be related?


Script injection and UA custom metric

Add a new script injection directory and seed it with an observer script that detects navigator.userAgent usage.
Add a new property to the privacy custom metric to output the value of the UA observer.
Tests:

https://webpagetest.httparchive.org/result/220519_0T_D/1/details/#waterfall_view_step1

LGTM modulo the lint issues


FAI-786 account suspended

I've removed one of the auth handlers as the functionality it was reproducing is built in


Enable password hash sync through AAD Connect configuration wizard step, at the end,  is missing.

The article is great, but there is one important last step that is not mentioned to make it work as expected:
enable password hash sync through AAD Connect configuration wizard as described here
https://techcommunity.microsoft.com/t5/core-infrastructure-and-security/configure-selective-password-synchronization-with-aadconnect/ba-p/1459434

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a28b3326-1302-1492-3961-0e1d59e12877
Version Independent ID: 7706e19b-5815-ca09-6095-35e98805f41d
Content: Selective Password Hash Synchronization for Azure AD Connect
Content Source: articles/active-directory/hybrid/how-to-connect-selective-password-hash-synchronization.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

@AlexCesarini
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

Thank for submitting this. I have created a work item for it and will reviewing this in the coming weeks. I am not sure what the timeline will be, so I am going to close this for now. But once I have an update I will drop it in here and let you know.
Thank you!
Bill
#please-close


2.38.1 Install Fails on Kali

Trying to perform a new install of the .deb package on Kali Linux.  I receive an error saying mysql-server is not installed.  MySQL is installed by default on Kali, and I've checked to make sure the service is running as well (tried it both running and not).
Here is the error message I get from dpkg:
sudo dpkg -i seccubus_2.38.1-0_amd64.deb
Selecting previously unselected package seccubus.
(Reading database ... 379197 files and directories currently installed.)
Preparing to unpack seccubus_2.38.1-0_amd64.deb ...
Unpacking seccubus (2.38.1-0) ...
dpkg: dependency problems prevent configuration of seccubus:
 seccubus depends on mysql-server; however:
  Package mysql-server is not installed.

dpkg: error processing package seccubus (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 seccubus

Is there a way I can either reconfigure seccubus to try using a different DB, like PostgreSQL for example, or something I can provide to help you troubleshoot this?
Thanks for your time and all your effort on the project!

You need to install all dependancies.
Type: sudo apt-get install -f

That has already been done.  All the dependencies ARE installed, which I mentioned in the original post.  Seccubus is not recognizing that MySQL Server is already installed.

Ubuntu and debian have configured MariaDB-server as an alias for mysql-server Kali doesn;t have this for some reason.
Don;t know how to fix that, yet.

apt install perl MariaDB-server libalgorithm-diff-perl libdbi-perl libdbd-mysql-perl libjson-perl libxml-simple-perl libwww-perl liblwp-protocol-https-perl libnet-ip-perl libtimedate-perl libhtml-parser-perl libcrypt-pbkdf2-perl libterm-readkey-perl libmojolicious-perl;
then install from source:
git clone ...
cd seccubus
./build_all
cd build
./install.pl --basedir /opt/seccubus
This is how i'm doing it on kali!

Confirmed still an issue with Seccubus version 2.40.0
Added bug on the Kali bug tracker: https://bugs.kali.org/view.php?id=4281

The problem in Kali is inherited from Debian. Debian Testing only provides 'default-mysql-server' and not 'mysql-server'.
Suggestion from Kali bug tracker, is to change the debian.control file of the package to include both options:
"mysql-server | default-mysql-server,"
Can the debian.control file be am

The correct dependency to use is "default-mysql-server | virtual-mysql-server". If you want to keep compatibility for version older than stretch you might want to add a third alternative "default-mysql-server | virtual-mysql-server | mysql-server".
Thank you.

Thanks. I will make sure to adopt this.
I hope to be included in Kali one day.


Update pie rose charts

What are the changes/fixes in this PR?
Added some lines of code to add outlines to each sector in the pie/rose charts.
This prevents different sectors of similar colour from blending together when many topics are being visualised.
TODO:

[ ]  Pass tests

What are the changes/fixes in this PR?
Added some lines of code to add outlines to each sector in the pie/rose charts. This prevents different sectors of similar colour from blending together when many topics are being visualised.
TODO:

[ ]   Pass tests

The Baseline files just need to be updated to pass the tests

What are the changes/fixes in this PR?
Added some lines of code to add outlines to each sector in the pie/rose charts. This prevents different sectors of similar colour from blending together when many topics are being visualised.
TODO:

[ ]    Pass tests

The Baseline files just need to be updated to pass the tests

Thanks for the hint, will work on it later this week.


fix: share STDIN across different commands on pre-push hook

Closes https://github.com/evilmartians/lefthook/issues/511
Closes https://github.com/evilmartians/lefthook/issues/611

:zap: Summary
Right now git lfs pre-push hook does not receive STDIN. We should pass it there but some other hooks may also use it.
For this purpose I've added a cachedReader that reads from STDIN once and cached the read data. Not only for pre-push but for all hooks that specify use_stdin option the cachedReader will be used.
However with parallel: true the read data may be incorrect because of random reads from different commands that run cuncurrently. So, when you use use_stdin for more that one command/script, please consider not using parallel: true.
:ballot_box_with_check: Checklist

[x] Check locally
[x] Add tests
[ ] Add documentation

Hey @tdesveaux, I've implemented a slightly different approach but it should solve the issue.

STDIN is passed to git lfs hooks whether it uses it or not. I think this is better to provide it always and avoid being responsible for managin STDIN.
But the STDIN is wrapped in a struct that caches all read bytes and allows to re-read them again and again. This solves issues when you have your own script/command that utilizes stdin together with Git LFS.

Do you have some time to test this code for your case? I've done some testing locally but I'd like to hear some feedback from you since this fix should solve your issue.

This is a far better approach, thanks for the fix.
I'll test try to test this today.
From a cursory review of the code:

You should consider writing the buffered Stdin to a file if it's size is large (pretty edge case, but a big push would receive lots of Stdin). I think this can be an noted improvement for later.
You removed the error escalation if LFS command fails. I'd like to re-iterate how dangerous this is IMHO.

Thank you for the review. Yes, it seems like Git LFS error is a crucial thing so it should fail the whole hook.
I will consider using file for caching. I think it makes sense when STDIN has about 1+ mb of data. Do you think such cases happen often?

https://git-scm.com/docs/githooks#_pre_push
I might have been far too cautious in thinking file buffering might be needed.
There is one line per ref pushed (branch, tag, etc).
For it to attain >1mb, it would take a very large repository being pushed in it's entirety.
Not sure someone doing this would have lefthook enabled.
You can disregard this IMHO, this would add complexity to the code for no real benefit.

@mrexox  Just tested this branch. This fix the issue I reproduced.
FYI, here is what I did to reproduce.

git init a repository
setup lefthook with a pre-push hook. (tested with a simple run: echo pre-push_hook initially)
add a dummy test.bin file with echo test >> test.bin
git lfs track test.bin
commit lefthook.yml and .gitattributes
commit test.bin
push

I also tested your branch with a cheeky:
pre-push:
  commands:
    cat-stdin
      run: cat
      use_stdin: true

and it works.


How to arrange child nodes under the same node from left to right

Describe the bug / 问题描述
How to arrange child nodes under the same node from left to right instead of having large intervals as shown in the picture

Reproduction link / 重现链接
No response
Steps to Reproduce the Bug or Issue / 重现步骤
No response
G6 Version / G6 版本
🆕 5.x
Operating System / 操作系统
Windows
Browser / 浏览器
Chrome
Additional context / 补充说明
No response

这个布局试下？https://g6.antv.antgroup.com/api/layouts/antv-dagre-layout#nodeorder

I have uploaded an example. Could you please take a look
https://codesandbox.io/p/devbox/vue-antv-g6-lctq25?file=%2Fsrc%2Fcomponents%2FDagre.vue%3A48%2C7

I have uploaded an example. Could you please take a look
https://codesandbox.io/p/devbox/vue-antv-g6-lctq25?file=%2Fsrc%2Fstyle.css%3A67%2C22

I have uploaded an example. Could you please take a look
demo

I have uploaded an example. Could you please take a look demo

404😭

Can you see the image? If you can see the image, you can directly create a node based on the current data to take a look

如果反馈的问题是节点之间的间隔过大，这是由于 dagre 布局在生成布局时优先考虑了树的平衡性，对节点的 x 坐标进行了调整。要解决这个问题，需要自定义布局。

如果说是为了考虑树的平衡性，那为什么删除右侧节点的子节点，前面子节点就可以从左向右布局呢？

可以去看一下 dagre 实现的源码 https://github.com/dagrejs/dagre


path to image

Describe the bug
I have this output in astro config...
output: `../sites/test/public/d2`,

and build generates this img path...
<img alt="Diagram" decoding="async" loading="lazy" src="/sites/test/public/d2/sites/test/src/content/docs/guides/example-0.svg" width="953" height="268">

correct path is /d2/sites/test/src/content/docs/guides/example-0.svg
To Reproduce
info above
Expected behavior
correct img path
How often does this bug happen?
Every time
System Info
No response
Additional Context
No response

Thanks for the feedback.
The issue should now be resolved in the version 0.5.1 that I just released. If you have the Astro publicDir option set to ../sites/test/public and the Astro D2 output option set to d2 (which is the default), everything should work as expected.


8.1 update to 8.2 warning: VERGEN_SYSINFO_USER set to default

system:windows 11
vergen:8.2
rustc:1.70.0
warning: VERGEN_SYSINFO_USER set to default
How to solve it？

I'll take a look at this shortly. I've been away for the past week.
That output is generally caused because cannot successfully determine the user. The current logic looks up the current PID and checks the list of users knows about, then checks that list for the user associated with the process. If this fails for any reason (PID can't be found, user is restricted by OS) then you will get the default output. I've seen this happen commonly on Windows systems because getting the PID of the current process fails, but I've never seen in happen on Linux.sysinfo``sysinfo

I'm sure there's no problem with 8.1,occurred on 8.2.

Can you add fail_on_error to your EmitBuilder config to see if any additional insights can be gleaned.    I am unable to reproduce this on my Windows or Linux boxes.

Closing this as I can't reproduce.   If this is still happening, add your build.rs and vergen config from your Cargo.toml to the ticket and re-open.


Broken links with language other than English

Some src and href links point to wrong (relative) paths while the site language is not English.

#203


FIX: Accept all matplotlib color-specifiers

Description
This PR adds a wrapper for pyqtgraph's mkColor which makes PyQtGraphBrowser accept all available matplotlib color-specifiers (especially float-tuples with values from 0-1 where pyqtgraph would need values from 0-255)
References
Closes mne-tools/mne-python#10059

Thanks!


Specifying Dependencies with tilde requirements

Specify a minimal version for regex and once_cell with some ability to update and enhance compatibility for other projects which depends on these crates.
Fixes #190

Hi, @saschagrunert as talked with @utam0k I push this commit to enhance it. PTAL! thx

FYI @utam0k @saschagrunert PTAL ! thx

@Apokleos Can you tell us what project depends on oci-spec-rs? I'm curious why the project is ok with regex 1.10.3, but not regex 1.10.5.

@Apokleos Can you tell us what project depends on oci-spec-rs? I'm curious why the project is ok with regex 1.10.3, but not regex 1.10.5. The changelog of regex doesn't seem to contain breaking change between 1.10.3..1.10.5.

Yeah, you're right. I'll correct it ASAP. Thx for your.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 26.99%. Comparing base (a3d8805) to head (8e0dc98).
Report is 23 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #191      +/-   ##
==========================================
+ Coverage   25.91%   26.99%   +1.07%
==========================================
  Files          23       23
  Lines        2473     2615     +142
  Branches     1367     1443      +76
==========================================
+ Hits          641      706      +65
- Misses        861      873      +12
- Partials      971     1036      +65


Respect authors:

Hello,  I have a question about the code. where is the file that is named 'progress.bar'?  You mentioned the file name in the 'utils/init.py'.

Hi, 'progress.bar' is actually from the package. Hence, you need to install it via 'pip install progress'. I'll add about this in readme file. Thx!

ok, thanks!


Embedded cowboy: Supervisor specs.

A common use case is when we want to embed cowboy underneath the supervisor tree of another application. In this case, we don't want the listener to be added to the supervisor of cowboy, but rather, we want it to be added underneath a supervisor in the hosting application.
An easy way to do this is to create a s child spec invoking cowboy_listener_sup:start_link/5 with the correct parameters. However, this suggestion is to make the cowboy module contain a function that will produce the right kind of ChildSpec for us. That way, embedding cowboy in your supervisor amounts to calling this function and shoving the returned spec into your supervisor tree structure.

Closing fixed.


parallelize tests script

fixed the parallelization script to work and the build is running all tests and passing. ready for review.


Maximum profit that can be obtained by buying and selling a stock at most k-times. c++ [GSSOC'21]

🚀 Feature
A program using dynamic programming to find the maximum profit that can be obtained based on the stock prices given as an array list of stock prices for each day.
Have you read the Contributing Guidelines on Pull Requests?
Yes, I thoroughly read the guidelines.
Motivation
(I initially came across the question of maximum of two transactions allowed to attain best profit, I could bruteforce it. However the beauty of dynamic programming is that it allows us to solve for all the cases with a systematic and mathematical base, and it allowed me to solve for k transactions allowed.)
Pitch
This feature once implemented will allow the users to understand step by step approach towards the problem statement and hence help in solving further questions posed to them in competitions, interviews and so on.

/assign


New version: TopazLabs.TopazPhotoAI version 1.2.1

Pull request has been created with komac v2.0.0 :rocket:
Microsoft Reviewers: Open in CodeFlow

/AzurePipelines run


Lock loadedConfigs while in use

Since AD could modify the map of loaded configs at any time, it's
important that callers examining that list do so while the lock is held.
This is more efficient than copying the list.
Motivation
AGNTGLD-63
Additional Notes
I omitted a changelog since this has no user-visible impact.
Aside from go test, testing for this change would involve running agent configcheck, which uses the new WithLoadedConfig function.
Checklist

[x] A release note has been added or the changelog/no-changelog label has been applied.

I just spotted two more issues in these files, so I'll mark this as draft for the moment.

gopls had missed some spots in renaming functions so I just pushed another commit to fix that up.


ci as a command name in npm task

[Enter feedback here]

#command: 'install' # Options: install, publish, custom

I could use ci as a command name with no error. Might it be a valid command name?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7a3df0ae-70ac-af4c-1a65-999a3de5c9d4
Version Independent ID: 6e72fbc7-7fc9-09d7-8039-a29636417f75
Content: npm task - Azure Pipelines
Content Source: docs/pipelines/tasks/package/npm.md
Product: devops
Technology: devops-cicd-tasks
GitHub Login: @vijayma
Microsoft Alias: vijayma

@naoak Thank you for letting us know. The recommended approach is to use command: custom, and then pass your command to customCommand.

@ramiMSFT Thank you for the information. I will follow your recommended approach. By the way, does this mean that we can use ci as a command now, but may not be able to use it in the future?

Oh, I see. Thank you for your reply!


Call Commit() in TxWithRetry().

Summary
Closes #688.

Codecov Report

Merging #691 (b445378) into develop (b73f450) will increase coverage by 0.02%.
The diff coverage is 66.66%.

@@             Coverage Diff             @@
##           develop     #691      +/-   ##
===========================================
+ Coverage    53.26%   53.28%   +0.02%
===========================================
  Files           23       23
  Lines         3612     3603       -9
===========================================
- Hits          1924     1920       -4
+ Misses        1429     1426       -3
+ Partials       259      257       -2

Impacted Files
Coverage Δ

idb/postgres/postgres_migrations.go
36.04% <0.00%> (ø)

idb/postgres/postgres.go
46.37% <75.00%> (+0.01%)
:arrow_up:

Continue to review full report at Codecov.

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


[CP] Revert "add a new PopScope.onPopWithResultInvoke widget to replace PopScope.onPopInvoke"

Issue Link
https://github.com/flutter/flutter/issues/148867
Target
stable
PR Link
https://github.com/flutter/flutter/pull/147598
Changelog Description
Revert "add a new PopScope.onPopWithResultInvoke widget to replace PopScope.onPopInvoke"
Impacted Users
iOS users on Flutter stable 3.22.0 and 3.22.1
Impact Description
Unable to focus on TextField or open the keyboard again after side pop from another screen on iOS.
Workaround
Stay on 3.19.6 or use tags 3.22.0-19.0.pre and above
Risk
low
Test Coverage
yes
Validation Steps

Flutter stable 3.22.0, 3.22.1; tag 3.22.0-18.0.pre and below

run an app with a TextField on iOS
tap into TextField
keyboard opens
navigate to a separate screen
swipe back (this is important)
tap into TextField
keyboard does not open

Flutter tag 3.22.0-19.0.pre and above

run an app with a TextField on iOS
tap into TextField
keyboard opens
navigate to a separate screen
swipe back (this is important)
tap into TextField
keyboard opens

@justinmc @chunhtai I'm not sure if this is the right thing to cherry-pick, or instead it should be to fix forward to https://github.com/flutter/flutter/pull/147607.  Could you take a look at the regression and test it out?

It looks like the actual PR that we would cherry pick is https://github.com/flutter/flutter/pull/147607, is that right @chunhtai?  Also, are we sure that that is what fixes https://github.com/flutter/flutter/issues/148573 @techouse?

It looks like the actual PR that we would cherry pick is https://github.com/flutter/flutter/pull/147607

I think in order to cherry pick the reapply, you will need to cherry pick the revert first right?
it seems like the release only contains the problematic popscope commit but not the revert and reland? if so we can either cherry pick the revert or both the revert and reland, I am fine with either one.

actually it may be better to cherry pick both because the breaking change is already out with the problematic popscope commit, we don't want them to do it twice

Also, are we sure that that is what fixes https://github.com/flutter/flutter/issues/148573 (and/or https://github.com/flutter/flutter/issues/148867) @techouse?

As stated above in https://github.com/flutter/flutter/issues/149178#issuecomment-2135340355, I tested with 11 versions, including one before and one after the fix. If you want I can do some additional testing, but it seems more than likely that this is the fix/cause.

I am new to the process, may I know which branch I should create the cherry pick against?

actually this looks weird, the stable doesn't have the popscope change, something else is at play.

This should be the commit that fixes the issue
https://github.com/flutter/flutter/pull/147390
can you verify? if it indeed is, we should change the this issue title and description
cc @gspencergoog

This should be the commit that fixes the issue #147390
can you verify? if it indeed is, we should change the this issue title and description
cc @gspencergoog

@chunhtai You're right! It does look like https://github.com/flutter/flutter/pull/147390 is the real fix. I somehow I compared it in reverse, https://github.com/flutter/flutter/compare/3.22.0-19.0.pre...3.22.0-18.0.pre instead of https://github.com/flutter/flutter/compare/3.22.0-18.0.pre...3.22.0-19.0.pre 🤦 and the sheer quantity of PopScopes got me.
I'll change the CP description now.

Yes, I consider this low risk.  The ListenableBuilder part doesn't change functionality at all, and the withExternalFocusNode part is the bug fix, and has very similar functionality to the original code, but will not overwrite the skipTraversal and other attributes of the node when they are out of sync with the Focus widget. The effect of the change should be local to this widget and its FocusScopeNode.

This issue seems to require a hotfix. It is a big problem that text fields do not work properly in released apps.

This issue should be closed; the hotfix is live in Flutter 3.22.2

https://github.com/flutter/flutter/blob/master/docs/releases/Hotfixes-to-the-Stable-Channel.md#3222-june-06-2024

Thank you @techouse and all others who helped troubleshoot and fix this! 🚀


Reducing CRD sync interval from 15secs to 2 secs

Reducing CRD sync interval to reduce the likelihood of hitting a race condition when using AWS release excess IPs feature.

Closed in favor of https://github.com/DataDog/cilium/pull/20


Add view_component_storybook:remove_stories_json

While working with Storybook, we have noticed that old files are left on running instances of the application, which results in adding items that no longer exist to the sidebar.
Examples of scenarios include:

deleting an existing component
renaming a component

Thanks for the contribution 🎉


Adds locale folder for easier string translation

Changes

removes the raw_texts.py file
adds loc package
substitutes all the strings interacting with the user with strings from the french.yml file

Tests
I didn't test all the functionalities cause I couldn't get around the French menu (Sorry).
I tested if it starts, help, settings, commands error message, desync, buffer
Unrelated Bug
Having all roles + owner seems to give a double admin help section?
P.S.
I couldn't find a development branch, I'm not sure this should be merged into master (yikes)

Thanks, that's a great start! Will be merged into locales branch.


No longer require 'git' on the PATH to get the HEAD commit id

GearVRf-DCO-1.0-Signed-off-by: Mihail Marinov<EMAIL_ADDRESS>

Directly reading files under the .git directory to determine the current head commit. No need to have the git executable in the PATH anymore. Verified it works on Windows and Linux.

Will merge tomorrow morning


Update issue templates

Just a template for creating issues in the repo. Please let me know if you want to change/add anything.

Actually, @Amutha37 , this is the issue submitted to Git: https://github.com/CodeforAustralia/council-emissions-calculator/issues/213#issue-1402555884. Let's continue our discussion there?

Closing for @hqtan to submit a separate PRs for git issue templates.


dynamodb-local: 2.5.1 -> 2.5.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for dynamodb-local is: DynamoDB Local is a small client-side database and server that mimics the DynamoDB service
meta.homepage for dynamodb-local is: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/DynamoDBLocal.html
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.5.2 in filename of file in /nix/store/ffqiv49qx321pjbvncnz8jhz5mw3gc6l-dynamodb-local-2.5.2

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

dynamodb-local

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ffqiv49qx321pjbvncnz8jhz5mw3gc6l-dynamodb-local-2.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/0ecb1cffb3e42475dc66e5067feba871042f9b23#dynamodb-local

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ffqiv49qx321pjbvncnz8jhz5mw3gc6l-dynamodb-local-2.5.2
ls -la /nix/store/ffqiv49qx321pjbvncnz8jhz5mw3gc6l-dynamodb-local-2.5.2/bin

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

1 package built:

dynamodb-local

Maintainer pings
cc @shyim @martinjlowm for testing.

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

1 package built:

dynamodb-local


Zones in home assistant are only on or off

Hi, I recently tried out your Airtouch5 integration but for zone control, if you don't  have a temperature sensor for that zone, there appears to only be the ability to 'turn the fan on or off', however, this just sets the zone to 0% or 100%.  Is there any way this can be changed to a 0-100% scale (even it it was a fan speed in x increments)?
Am I perhaps missing something and you can already do that somehow?

What is in home assistant doesn't support this.
But there is support in the library to do it, and I've done the HA side, they just need a lot of tidy up and PR handling
At this commit
binary_sensor.py and cover.py
(removed in the next commit)
cover allows setting the damper%
https://github.com/danzel/airtouch5py/releases/tag/0.2.8
This old release might do it if it still works.
Otherwise please grab those two files, fix them up and PR them to Home Assistant to add it 🙏

Thanks for replying.  I'm a little confused (and somewhat out of my depth).  So you did add support but then removed it?
I'm not really sure what fixing the files would need.

When you add a new integration to HA you are only allowed to add one entity type, so I had to remove them.
I haven't had time to improve and submit adding the entity types since.

I see, I'd love to help but I'm not sure I quite have the skills for that but if you can give me some pointers I am willing to have a go.

Want a hand with this? I just started using the integration and want damper % control too.

Details are above on what needs to be done @Denifia
https://github.com/danzel/airtouch5py/issues/2#issuecomment-2060087684

@danzel if you have free time, can you cast your eye over my PR linked above.

This has been merged into the dev branch of home assistant and will roll out to users at some point. Not sure on the timing of that.
@danzel consider closing this issue.


Bump gulp-load-plugins version

Just to get rid of deprecation message:
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>So far I haven't noticed any problems with this version.

Hi,
Thank your remind and PR.


[vcpkg docs] Update readme.md

Fixes https://github.com/microsoft/vcpkg/issues/18191
Fixes https://github.com/microsoft/vcpkg/issues/18231

The ' .\vcpkg\vcpkg install package:x64-windows' in readme confuse the users, update it to make things clearer to reader.
The readthedocs.io is broken, since issue https://github.com/vcpkg/vcpkg.github.io/issues/12#issuecomment-846094957 closed, so I think it's ready to update it in readme.

Thanks!


Refactor mergeWithDelegate method in DefaultAccount and cancelEntitlementWithDateInternal in Entitlement for improved modularity and maintainability

This PR refactors the mergeWithDelegate method in DefaultAccount.java to improve modularity, maintainability, and adherence to software design principles. The original method handled multiple responsibilities, including validation, field updates, and object creation, which made the code difficult to read, maintain, and extend.
Key changes include:

Encapsulation of Optional Field Updates: A new private helper method, updateOptionalFields, consolidates the logic for updating optional fields, reducing duplication and improving clarity.
Simplified Bill Cycle Day Logic: The logic for determining the bill cycle day has been streamlined into a concise conditional statement.
Improved Readability: The method is now shorter and more focused, making it easier to understand and maintain.
Separation of Concerns: Responsibilities for validation, optional field updates, and object creation are now distinct and modular.

Reason for the Change
The refactor addresses key design issues in the original implementation:

Single Responsibility Principle (SRP): The method now delegates field update logic and validation to dedicated components, ensuring each part of the code has a clear purpose.
DRY Principle: Repeated logic for setting optional fields has been consolidated, reducing redundancy.
Clean Code Practices: The changes make the code more readable, testable, and maintainable.
Encapsulation: The domain logic for merging accounts is now encapsulated within DefaultAccount, aligning with Domain-Driven Design (DDD) principles.

Impact

No Functional Changes: The functionality of the method remains the same, ensuring backward compatibility.
Improved Maintainability: Future changes to validation or field updates can now be implemented without modifying the core logic of the method.
Modular Design: This change reduces the cognitive load for developers working on this class and makes the code easier to test and debug.

Conclusion
This refactor simplifies and improves the design of the mergeWithDelegate method while preserving its functionality. It adheres to SOLID principles and paves the way for easier extensibility and maintenance in the future.

Description:
This pull request also refactors the cancelEntitlementWithDateInternal method in the Entitlement class to improve readability, reusability, and maintainability.
Key Changes:

Simplified Method Logic: The original method was a large, complex block of code. It has been broken down into smaller, logical steps, each encapsulated in its own helper method.
Added Helper Methods:

validateCancellationDates: Ensures the provided cancellation dates are valid.
createEntitlementPluginContext: Prepares the plugin context required for cancellation.
executeCancellationLogic: Handles the main cancellation logic, including plugin interaction.
handleSubscriptionCancellation: Focuses on subscription base cancellation.
handleBlockingStates: Manages blocking states and future notifications.

Why These Changes Were Made:

Breaking the method into smaller, focused methods improves code readability and makes it easier to understand and maintain.
Enhances the testability of individual components.
Follows clean coding principles and aligns with SOLID principles, particularly the Single Responsibility Principle.

Impact:

This refactor ensures that the cancellation logic is clear and extendable for future enhancements or changes.
No breaking changes are expected, as existing functionality remains intact.


CLI script needs better output

--verbose, --quiet flags
Colored output

Closing in favor of #4


Include Python std libs in environment distributed with GRAPEVNE

Include Python std libs in environment distributed with GRAPEVNE (permits access in Snakefiles run through GUI)

@rowannicholls FYI - This PR fixes the grapevne issue identified in https://github.com/kraemer-lab/vneyard/pull/12.


Coverage

more tests
codecov badge
update Action versions

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:

Had to fix some things in a3ae44e for it to work properly.


Actual minimum ruby version required?

The Gemfile requires ruby 2.6.3, which is - according to packaging systems (especially on a centos )- a very recent version.
I tried this in ruby 2.6.2 on Centos (which is available in Redhat Software Collections), and I  saw no problems.
I can of course use rvm, but rvm is actually for development purposes (includes development files, requires login in order to switch version ..).
Is this recent version actually needed?

Hi @nicolasfranck
That's a good point about the minimum versions.  We just upgraded to 2.6.3 with the update to Rails5.  Previously, we'd been using 2.4.4.
I believe Rails5 actually only has the requirement of Ruby v2.2.2, but when we later upgrade to Rails6, that will go up to 2.5.0.
If you do end up testing with an older ruby-version, We'd appreciate the report back with which Roadmap version and Ruby version were compatible.  I don't foresee many issues, but you may find that gem compatibility changes as you modify the Ruby version.
One option to use an older version, but retain that forward looking compatibility would be to use 2.5.x, which would ensure your Rails6 compatibility down the line.

Proposal: retrace our steps until a ruby version is found that is

higher or equal to 2.5.x
does not change the Gemfile.lock


on-page menu not visible if DOI is given

First off, thanks for this amazing plug-in you created to bring Zotero data into Roam!
My issue is with the on-page menu.
I'd only ever seen it displayed properly for one of my sources, which was an unpublished manuscript.
Now I have found out that, for me,  if a source has a DOI in Zotero, only the DOI will be displayed on its Roam page, none of those buttons for Google Scholar, Connected Papers etc.
before

vs after DOI removed and zoteroRoam reloaded

Hi there! Looks like there some error going on while rendering the on-page menu in the first screenshot, which isn't caught & so the menu rendering doesn't complete.
Since it loads without issue when there's no DOI, I think the issue is in the citations data retrieval.
Are you able to put the DOI back in, reload your Roam page, and send me a screenshot of the browser console output?
There should be errors there that point to the underlying problem. Let me know if you need help with that :)
(the console is part of the Developer Tools of the browser ; usually Ctrl-Shift-I opens up the dev tools, then you can go to the "Console" tab ; you can also find the dev tools through your browser menu, typically under "Advanced" or similar ; or you can right-click in a non-interactive spot on the page, then click "Inspect")

Here is the console and the error it displays:

Thanks so much! I located the bug, starting on a fix - will be up by end of today, or tomorrow at the latest.

This should be fixed in the just-published version (0.6.65). There was an issue where, if any library item had a DOI but in the wrong format, the code would fail when generating the on-page menu.
Feel free to open this back up if you still run into issues!

Awesome, thank you so much!
I can confirm that it works for me now (after figuring out I need to update):


add ExposedSecret Report summary metrics

Trivy-Operator now supports ExposedSecret Report summary metrics.
the metric collector needs to be updated to collect exposed secret summary metrics as well.
CRD ref :Exposed Secrets

I believe this is in scope of #78 isn't it? closing unless it's necessary to track separately


Issue when using composer require classiebit/eventmie

Deprecation Notice: Class Classiebit\Eventmie\Http\Controllers\MybookingsController located in ./vendor/classiebit/eventmie/src/Http/Controllers/MyBookingsController.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0. in phar:///usr/local/bin/composer/src/Composer/Autoload/ClassMapGenerator.php:201
Hi I am looking to get a local version up and running to do some testing, I am thinking we maybe able to use this for a project we are building.

Same here. Can't install via composer.

Same here. Can't install via composer.

Still same issue, even submited ticket on website. Your software is not working.

Still same issue, even submited ticket on website. Your software is not working.

Issue resolved. Please try now.

Issue resolved. Please try now.

Works well with PHP 7.3 only.

Works well with PHP 7.3 only.

Yes, because Laravel 8 requires PHP 7.3. While, if you wanna use older than PHP 7.3, then install it with Laravel 7 or below.


fix(card): Remove overflow hidden

Overflow hidden is not needed on card styles by default, and can lead to
unexpected results.
Fixes #4751
BREAKING CHANGE: Changes the overflow style of cards. Users relying on
overflow:hidden; will have to add it back themselves.

LGTM.
Not too much breaking since v2 is still in pre-alpha though. ;)
Thank you.


[chainerx] add softmax

Add softmax.
Reference: #6423

Thanks for the PR. The implementation basically LGTM but could you resolve the conflicts?

For the record, we probably want to implement softmax using cuDNN's cudnnSoftmaxForward for CUDA but that can be addressed in a later PR.

Thank you for comment. I rebased.

Jenkins, test this please.

Jenkins CI test (for commit df12d8c5c9002f2fe3a733f853035f3a5a7c17de, target branch master) succeeded!

Sorry for the delayed merge. LGTM!

Renamed the PR title for style and release note rendering.

Jenkins CI test (for commit df12d8c5c9002f2fe3a733f853035f3a5a7c17de, target branch master) failed with status FAILURE.


Add image text below images in intro section

I don't know why the second image disappears after my edits..any thoughts?

Also, I still wonder if the image should have a border,

I asked UX and they said that without borders the layout appears more clean.


Feature/hlist pins

Still in draft. Need to expand examples, and check a few things, but the core of the idea is there.
The highlight: compare the traditional way with the hlist-way

[ ] Write keyboard example
[ ] Develop a pattern so that a device can be initialized with the pin-list only.
[ ] Construct USB with just an hlist
[ ] Make pin-generic pin-holders sane to initialize (difficult, probably)
[ ] Ensure the overhead is compile-time-only
[ ] validate the hypothesis of better performance through reduced need for indirection/dyn-dispatch
[ ] doc-comment (much) more thoroughly.

Must

[ ] The code compiles without errors or warnings.
[ ] All examples work.
[ ] cargo fmt was run.
[ ] Your changes were added to the CHANGELOG.md in the proper section.
[ ] You updated existing examples or added examples (if applicable).
[ ] Added examples are checked in CI

Nice to have

[ ] You add a description of your work to this PR.
[ ] You added proper docs for your newly added features and code.

Just had a very brief look - so just my first impressions, might be inaccurate or not thought through

it seems like this is just additional functionality but when using this, I don't see how to create any peripheral driver that takes  pins (unless we would change each and every driver to use this)
using AnyPin is much more convenient in situations where the user doesn't want or can't use generics
this still needs generics in user code and introduces terms like Plucker and HList
if we would consider to change each and every driver to use this approach, we probably lose the ability to pass &mut instead of moving the pin into the driver

t.b.h. I don't think we should have this in the HAL (but I am happy to hear other's voices) - the approach is interesting in user code ... if we can do something to create such lists in user code that's certainly fine
As said - just a first impression and I'd like to hear more opinions

t.b.h. I don't think we should have this in the HAL

Apart from the tie-in to the macro that generates the initial list, everything should be doable in an external utility crate. That initial list seems to be, however, rather annoying to define outside of the HAL currently.

I don't see how to create any peripheral driver that takes pins

It remains possible to pluck a pin and pass it to a peripheral. I believe the example is mostly useful to show an example user-defined wrapper. The HAL drivers could define a "pluck constructor" that take ownership over pins and pass them to the current constructors, but again, I believe this should be doable externally. Also, some peripherals, like SPI have way too many constructors already, doubling the number would be an API nightmare for newcomers to decode.
As I see it, the point is that users don't have to name the pin to move out of the IO struct (i.e. the struct field isn't hardcoded any more). This is a small advantage that is visible when supporting multiple hardware configurations in a single codebase.

Just had a very brief look - so just my first impressions, might be inaccurate or not thought through
* it seems like this is just additional functionality but when using this, I don't see how to create any peripheral driver that takes  pins (unless we would change each and every driver to use this)

As it currently stands, absolutely correct. I had this question in the periphery of my mind, but now that the initial draft is up, it needs to be front-and center. Something like this, I think, is needed:
    // Previously, USB::new would take 3 specific pins where the pin_list argument is.
    // These three pins are restricted with marker traits/structs, so pins can't get mixed up.
    // For example, esp32s3, the pins must be 18, 19 and 20 in arument 2, 3 and 4 respectively.
    let (usb, pin_list) = USB::hl_new(
        peripherals.USB0,
        pin_list,
        &mut system.peripheral_clock_control,
    );

inside hl_new, the io will pluck_pin, and the type system will understand that the only pins that are to be plucked, are the ones that have the right marker trait/struct generics. An impl might look a bit like this:
impl<'d, S, P, M> USB<'d, S, P, M>
where
    S: UsbSel + Send + Sync,
    P: UsbDp + Send + Sync,
    M: UsbDm + Send + Sync,
{
    pub fn hl_new<T, U, ???>(
        usb0: impl Peripheral<P = peripherals::USB0> + 'd,
        io: IO<T>,
        peripheral_clock_control: &mut PeripheralClockControl,
    ) -> (Self, IO<U>)
    where
        T: ???,
        U: ???,

    {
        let (sel_pin, io) = io.pluck_pin();
        let (dp_pin, io) = io.pluck_pin();
        let (dm_pin, io) = io.pluck_pin();
        let res = USB::new(usb0, sel_pin, dp_pin, dm_pin, peripheral_clock_control);
        (res, io)
    }

Currently, the type-system constrains the user such that if they choose the wrong pin-number, there will be a compile failure. The benefit I hope to introduce, is to be able to just pass in the pin-list, and the type-system will automagically select the correct pins, by way of the marker trait/structs, and to raise an error if the pins are unavailable.

* using `AnyPin` is much more convenient in situations where the user doesn't want or can't use generics

From my understanding, a specific pin must always be selected, but it can then be .degrade()ed into an any-pin? There shouldn't be any compatability issues, in that case. instead of selecting a pin based on io.pins.gpioN, you just move the N const into .pluck_pin::<N, _>(). You get access to exactly the same thing, but instead of using N to index by a struct-field, you use it to index into a type-construction.

* this still needs generics in user code [...]

The goal is for generics to only be needed by the user when they want to explicitly state a pin-number, or a pin property.

where the pin number can be inferred by the type-system via the way in which the pin is later used, generices are elided entirely (example below)
For pin-number, I would argue that .pins.gpioN and .pluck_pin::<N,_>() are semantically equivilent. one encapsulates the const-generic N in a field name, the other, by way of the type-system. if the turbofish syntax is problematic, a work-around that handles the majority of cases should be possible: io.select_pin_no(4), io.select_pin_property(MarkerStruct::default), for example.
when pin a pin needs to be selected based on marker trait/struct properties, the hlist approach provides the possibility to bypass the need to specify a pin, as demonstrated in the USB::hl_new example implementation. If you need the one pin that implements the Foo marker trait (which might vary across different chips), you could write let (foo_pin, io) = io.pluck_pin<_, Foo>().

use hal::some_module::UsesPinN

let (pin_n, io) = io.pluck_pin();
let thing = UsesPinN::new(peripheral.SOME_PERIPH, pin_n, &mut system.peripheral_clock_control);

in cross-platform code, where different esp32s use different Ns, this code would just work, bucause the type system would know which GpioPin in the hlist satisfies the type-constraints of the new

and introduces terms like Plucker and HList

I agree that this can be improved. An initial thought is to alias it to Selector and PinListByType for starters. I will try to minimise the more esoteric, and higher-barriar-of-entry concepts that come from functional programming.

* if we would consider to change each and every driver to use this approach, we probably lose the ability to pass `&mut` instead of moving the pin into the driver

the backing crate, frunk, has the ability to obtain mutable references instead of managing ownership through types. When you have a moment, could you please refer me to an example so I can make sure this issue is addressed?

t.b.h. I don't think we should have this in the HAL (but I am happy to hear other's voices) - the approach is interesting in user code ... if we can do something to create such lists in user code that's certainly fine
As said - just a first impression and I'd like to hear more opinions

Thanks for taking the time to respond and critique. I've added some TODO points based on your feedback.

Thank you for the contribution, I really am sorry that this fell off of my radar for so long.
I think at this point we will not move forward with this; the maintainers will soon be meeting to discuss redesigning some of our core APIs, include GPIO, and I think our goals may not necessarily align with these changes.
In the future perhaps this is something that can be revisited, however until we have made some concrete decisions regarding the future of our GPIO driver I do not think this makes sense right now.


localization JS files have content-disposition: attachment; filename=... HTTP headers

Category

[x] Bug

Describe the bug
This is a bit of a mystery that is sometimes making browsers download a JS file rather than execute it.  It happens occasionally at a site that is using ADFS and is not using Office 365 CDN for ClientSideAssets.
While most of the js files in the app's folder under the ClientSideAssets folder in the App Catalog are served with no "content-disposition" http header, the one whose name includes "strings_en-us", created by the SPFx localization code gets served with the http header
content-disposition: attachment; filename="(file name).js"
When the download dialog occurs the file always has that anomalous value of the content-disposition header.  Since it is difficult to reproduce, I am focusing instead on reproducing the anomalous content-disposition header, which is easy.
In normal use, this has no effect, browsers probably override this header based on other context, but according to the standard they should download the file.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition
Steps to reproduce
Create a webpart or extension using the guidance here
There is no need to add languages other than en-us or even enter any strings in the en-US.js file
Use includeClientSideAssets and no CDN so that the assets are deployed in the ClientSideAssets folder of the app catalog
Add and deploy the sppkg in the app catalog
Go to the ClientSideAssets folder and the subfolder corresponding to the app
Use the Chrome F12 network tab or equivalent to monitor http response headers
Click on the file whose name includes "strings_en-us" and note the value of the "content-disposition" header
You will also note that the browser prompts you to download the file.
For comparison, click on a different js file in the same folder.  Those other js files have no content-disposition header and do not prompt to download.
Expected behavior
either no content-disposition header or content-disposition: inline
and does not prompt to download.
Environment details (development & target environment)
Chrome Version 85.0.4183.102 on Windows 10
SharePoint Online
SPFx, several different version from the past year or two.
Additional context
I have not seen this on projects that have several real nn-nn.js localization files, only empty en-us.js ones, but I have not done extensive testing of this.

Additional info:  this seems to affect application customizers, not webparts as I had said previously.

Well, I have solved it but the problem is very odd.  It turns out that the length of the file name affects the content-disposition http header in the ClientSideAssets library.  I'm not sure whether the length limit is in the file name or the path, but in my case a file name with a length in the low 80s had the correct header, while the same file with a name length in the high 80s had the wrong header.
The solution was to shorten the part of the file name that I was responsible for.
The underlying problem is probably with SharePoint or IIS, not SPFx.

Making our way through old bugs.  We think this might have been addressed earlier this year, and are working to see if it still repros.

This looks to be resolved.


ManagerNetwork.StartClient(ip, port) needs 2 callbacks OnTimeout, OnConnect

⚠ IMPORTANT: This issue is for the dev branch

https://github.com/GodotModules/GodotModulesCSharp/blob/7f2e7604bdc17251a7837e5e5b9b3c4b05a488b2/Scripts/Scenes/SceneGameServers.cs#L73-L74
The callbacks will be used to update the _connectingToLobby appropriately.
Thread safety should be considered here.

On second thought callbacks are a bad idea because of thread safety.


Give ability poll a source system more than once per minute.

The rufus scheduler supports a schedule based on seconds, by using the repeat method instead of cron, the method returns an EveryJob or a CronJob based on the schedule used.
schedule => "* * * * *" # CronJob scheduled for every minute

schedule => "10" # EveryJob scheduled for every 10 seconds

I have signed the CLA at a company level, twice! Please can this be checked.

You should add a parameter schedule_type (values: cron or repeat) to avoid regressions.

The rufus scheduler supports a schedule based on seconds,

Rufus supports seonds, and Rufus support cron "like", which means it looks like cron, but it isn't cron. Rufus add the "seconds" support, as per their doc. Notice the extra "*"
"* * * * * *" //should be every seconds
"*/10 * * * * *" //every ten seconds (works in my pipeline logstash 7.6)

Closing as although CLA has been signed, it's just being picked up


fix namespace problem in setUser

Catchable fatal error: Argument 1 passed to Slack\Message\MessageBuilder::setUser() must be an instance of Slack\Message\User, instance of Slack\User given

Haha, derp on my part! Looks like I missed that method in the unit test, too.
Looks good. :thumbsup:


Add a godoc example for HLL usage

Add a example of usage of HLL that get added to the documentation by godoc


Change Default project prefix to 'p-' #2

Re-do of https://github.com/rancher/rancher/pull/14398
Original issue https://github.com/rancher/rancher/issues/14400

LGTM


Add support for collectors and source apis

Support for the entire collectors and source apis needs to be added, documentation for the APIs can be found here:
Collectors: https://help.sumologic.com/APIs/Collector-Management-API/Collector-API-Methods-and-Examples
Sources: https://help.sumologic.com/APIs/Collector-Management-API/Source-API

Full collectors API support will be introduced in v0.3.0 which is due to be released on the 8/04/2021.

Work has been completed


Pod File

Add project to cocoapods? Thanks

Same request here :)

+1

+1

+1

+1

+1

I've created this podspec file:
Pod::Spec.new do |s|

  s.name         = "SwiftOCR"
  s.version      = "1.0"
  s.summary      = "OCR engine written in swift"

  s.homepage     = "https://github.com/garnele007/SwiftOCR"
  s.license      = "Apache-2.0"
  s.author       = { "Nicolas Camenisch" =><EMAIL_ADDRESS>}
  s.source       = { :git => "http://github.com/garnele007/SwiftOCR.git", :tag => "#{s.version}" }

  s.source_files  = "framework/SwiftOCR/*.swift", "framework/SwiftOCR/FFNN/*.swift"
  s.resources     = "framework/SwiftOCR/OCR-Network", "framework/SwiftOCR/Realistic Training Images/*.png"

  s.xcconfig = { "SWIFT_VERSION" => "3.0.1" }
  s.dependency "GPUImage"

end

Could anyone check whether this podspec also works for them?
Podfile:
  pod 'GPUImage', :git => 'https://github.com/BradLarson/GPUImage.git'
  pod 'SwiftOCR', :path => '../SwiftOCR'

Podspec worked fine
Good Job

OK. I've added SwiftOCR to CocoaPods.

It seems that It is not ok.
I have error after pod install:
[!] Unable to find a specification for SwiftOCR``

Hello garnele007 I've Used SwiftOCR with CocoaPods , it's not giving string from image, Pls help me


ListTile.divideTiles only run Iterable once

https://github.com/flutter/flutter/pull/75522 fixed the case where ListTile.divideTiles was receiving an empty Iterable.
The fix was not optimal because it would run the Iterable one extra time to check if the list is empty.
This pull request remove the extra iterable.isEmpty check.
cc @miquelbeltran
List which issues are fixed by this PR. You must list at least one issue.
https://github.com/flutter/flutter/issues/75518
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

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

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

Gold has detected about 27 new digest(s) on patchset 1.
View them at https://flutter-gold.skia.org/cl/github/78879

@xvrh - it looks like this PR needs to be resync'd and then pushed again.

@HansMuller I rebased, it seems good now. Thanks for the review.


Restructure the homepage code

Purpose

The purpose of this PR is to fix #358
Goals

Restructuring the homepage code
Approach

I restructured the homepage code
Screenshots

No screenshots
Preview Link
https://yoshitharathnayake.github.io/sack-site/
Checklist

[x] This PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
[ ] I have read and understood the development best practices guidelines
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Related PRs

Test environment

Learning

@YoshithaRathnayake The aim of the mentioned issue is to create a better code structure. You can refer the material kit starter template for that.
Or you can use a template like this:

...

        // content of section 1

        // content of section 2

    ...other sections...

        // content of contact section

And there are some custom styles that we could directly add using bootstrap classes without using custom CSS.
Example:
Currently we have a custom padding (padding-bottom: 40px, padding-top: 40px) for the contact-section. Without using that custom css, we could directly use py-5 CSS class to add that padding.

I think that one is making from this pr #38

Now @Piumal1999

Is that the way wanted


HDR and bloom issues on mobile platforms

Corresponding Unity issue: https://issuetracker.unity3d.com/issues/bloom-not-working-with-hdr-and-bloom-threshold-at-1
Even though it's marked as fixed in 2017.1, it's actually not.
Workaround: unknown, please share if you find any solution.

I've contacted Unity regarding this issue and they got back to me with a working solution:
By default "Use HDR" (the project wide setting) is disabled for all graphics tiers on iOS and Android. To enable it please go to "Edit > Project Settings > Graphics" and disable "Use DEfaults" on the tiers where you wish to use HDR. Then enable the "Use HDR' checkbox on these tiers.
Seems that you also have to set the shader quality to high, otherwise the SpriteOutline shader fails to compile.

Thank you for finding this out! Looks like it appeared to be a feature rather than a bug :) I’ve added the info about enabling HDR for graphic tiers to the readme.
About the compilation issue: I’ve just tested builds on both low and medium shader quality for Android/iOS and everything seems to work fine. Could it be you’ve worked with an old SpriteGlow version or used some special setup? Please consider creating a new issue for this case (if it’s still relevant).

Yep, the shader compilation error was related to me using an older version, thanks.


resnet18 backbone error

I change the resnet50 to resnet18，i change the code and get the right resnet18 structrue，
but have this error：
2019-03-14 14:03:36,553 maskrcnn_benchmark.utils.checkpoint INFO: Loading checkpoint from /home/chenfei/.torch/models/resnet18-5c106cde.pth
2019-03-14 14:03:36,608 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn1.bias                  loaded from layer1.0.bn1.bias                  of shape (64,)
2019-03-14 14:03:36,608 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn1.running_mean          loaded from layer1.0.bn1.running_mean          of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn1.running_var           loaded from layer1.0.bn1.running_var           of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn1.weight                loaded from layer1.0.bn1.weight                of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn2.bias                  loaded from layer1.0.bn2.bias                  of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn2.running_mean          loaded from layer1.0.bn2.running_mean          of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn2.running_var           loaded from layer1.0.bn2.running_var           of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.bn2.weight                loaded from layer1.0.bn2.weight                of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.conv1.weight              loaded from layer1.0.conv1.weight              of shape (64, 64, 3, 3)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.0.conv2.weight              loaded from layer1.0.conv2.weight              of shape (64, 64, 3, 3)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn1.bias                  loaded from layer1.1.bn1.bias                  of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn1.running_mean          loaded from layer1.1.bn1.running_mean          of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn1.running_var           loaded from layer1.1.bn1.running_var           of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn1.weight                loaded from layer1.1.bn1.weight                of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn2.bias                  loaded from layer1.1.bn2.bias                  of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn2.running_mean          loaded from layer1.1.bn2.running_mean          of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn2.running_var           loaded from layer1.1.bn2.running_var           of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.bn2.weight                loaded from layer1.1.bn2.weight                of shape (64,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.conv1.weight              loaded from layer1.1.conv1.weight              of shape (64, 64, 3, 3)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer1.1.conv2.weight              loaded from layer1.1.conv2.weight              of shape (64, 64, 3, 3)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn1.bias                  loaded from layer2.0.bn1.bias                  of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn1.running_mean          loaded from layer2.0.bn1.running_mean          of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn1.running_var           loaded from layer2.0.bn1.running_var           of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn1.weight                loaded from layer2.0.bn1.weight                of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn2.bias                  loaded from layer2.0.bn2.bias                  of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn2.running_mean          loaded from layer2.0.bn2.running_mean          of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn2.running_var           loaded from layer2.0.bn2.running_var           of shape (128,)
2019-03-14 14:03:36,609 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.bn2.weight                loaded from layer2.0.bn2.weight                of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.conv1.weight              loaded from layer2.0.conv1.weight              of shape (128, 64, 3, 3)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.conv2.weight              loaded from layer2.0.conv2.weight              of shape (128, 128, 3, 3)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.downsample.0.weight       loaded from layer2.0.downsample.0.weight       of shape (128, 64, 1, 1)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.downsample.1.bias         loaded from layer2.0.downsample.1.bias         of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.downsample.1.running_mean loaded from layer2.0.downsample.1.running_mean of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.downsample.1.running_var  loaded from layer2.0.downsample.1.running_var  of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.0.downsample.1.weight       loaded from layer2.0.downsample.1.weight       of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn1.bias                  loaded from layer2.1.bn1.bias                  of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn1.running_mean          loaded from layer2.1.bn1.running_mean          of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn1.running_var           loaded from layer2.1.bn1.running_var           of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn1.weight                loaded from layer2.1.bn1.weight                of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn2.bias                  loaded from layer2.1.bn2.bias                  of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn2.running_mean          loaded from layer2.1.bn2.running_mean          of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn2.running_var           loaded from layer2.1.bn2.running_var           of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.bn2.weight                loaded from layer2.1.bn2.weight                of shape (128,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.conv1.weight              loaded from layer2.1.conv1.weight              of shape (128, 128, 3, 3)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer2.1.conv2.weight              loaded from layer2.1.conv2.weight              of shape (128, 128, 3, 3)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn1.bias                  loaded from layer3.0.bn1.bias                  of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn1.running_mean          loaded from layer3.0.bn1.running_mean          of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn1.running_var           loaded from layer3.0.bn1.running_var           of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn1.weight                loaded from layer3.0.bn1.weight                of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn2.bias                  loaded from layer3.0.bn2.bias                  of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn2.running_mean          loaded from layer3.0.bn2.running_mean          of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn2.running_var           loaded from layer3.0.bn2.running_var           of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.bn2.weight                loaded from layer3.0.bn2.weight                of shape (256,)
2019-03-14 14:03:36,610 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.conv1.weight              loaded from layer3.0.conv1.weight              of shape (256, 128, 3, 3)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.conv2.weight              loaded from layer3.0.conv2.weight              of shape (256, 256, 3, 3)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.downsample.0.weight       loaded from layer3.0.downsample.0.weight       of shape (256, 128, 1, 1)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.downsample.1.bias         loaded from layer3.0.downsample.1.bias         of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.downsample.1.running_mean loaded from layer3.0.downsample.1.running_mean of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.downsample.1.running_var  loaded from layer3.0.downsample.1.running_var  of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.0.downsample.1.weight       loaded from layer3.0.downsample.1.weight       of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn1.bias                  loaded from layer3.1.bn1.bias                  of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn1.running_mean          loaded from layer3.1.bn1.running_mean          of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn1.running_var           loaded from layer3.1.bn1.running_var           of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn1.weight                loaded from layer3.1.bn1.weight                of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn2.bias                  loaded from layer3.1.bn2.bias                  of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn2.running_mean          loaded from layer3.1.bn2.running_mean          of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn2.running_var           loaded from layer3.1.bn2.running_var           of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.bn2.weight                loaded from layer3.1.bn2.weight                of shape (256,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.conv1.weight              loaded from layer3.1.conv1.weight              of shape (256, 256, 3, 3)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer3.1.conv2.weight              loaded from layer3.1.conv2.weight              of shape (256, 256, 3, 3)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn1.bias                  loaded from layer4.0.bn1.bias                  of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn1.running_mean          loaded from layer4.0.bn1.running_mean          of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn1.running_var           loaded from layer4.0.bn1.running_var           of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn1.weight                loaded from layer4.0.bn1.weight                of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn2.bias                  loaded from layer4.0.bn2.bias                  of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn2.running_mean          loaded from layer4.0.bn2.running_mean          of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn2.running_var           loaded from layer4.0.bn2.running_var           of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.bn2.weight                loaded from layer4.0.bn2.weight                of shape (512,)
2019-03-14 14:03:36,611 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.conv1.weight              loaded from layer4.0.conv1.weight              of shape (512, 256, 3, 3)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.conv2.weight              loaded from layer4.0.conv2.weight              of shape (512, 512, 3, 3)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.downsample.0.weight       loaded from layer4.0.downsample.0.weight       of shape (512, 256, 1, 1)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.downsample.1.bias         loaded from layer4.0.downsample.1.bias         of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.downsample.1.running_mean loaded from layer4.0.downsample.1.running_mean of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.downsample.1.running_var  loaded from layer4.0.downsample.1.running_var  of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.0.downsample.1.weight       loaded from layer4.0.downsample.1.weight       of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn1.bias                  loaded from layer4.1.bn1.bias                  of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn1.running_mean          loaded from layer4.1.bn1.running_mean          of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn1.running_var           loaded from layer4.1.bn1.running_var           of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn1.weight                loaded from layer4.1.bn1.weight                of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn2.bias                  loaded from layer4.1.bn2.bias                  of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn2.running_mean          loaded from layer4.1.bn2.running_mean          of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn2.running_var           loaded from layer4.1.bn2.running_var           of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.bn2.weight                loaded from layer4.1.bn2.weight                of shape (512,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.conv1.weight              loaded from layer4.1.conv1.weight              of shape (512, 512, 3, 3)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.layer4.1.conv2.weight              loaded from layer4.1.conv2.weight              of shape (512, 512, 3, 3)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.stem.bn1.bias                      loaded from bn1.bias                           of shape (64,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.stem.bn1.running_mean              loaded from bn1.running_mean                   of shape (64,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.stem.bn1.running_var               loaded from bn1.running_var                    of shape (64,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.stem.bn1.weight                    loaded from bn1.weight                         of shape (64,)
2019-03-14 14:03:36,612 maskrcnn_benchmark.utils.model_serialization INFO: backbone.body.stem.conv1.weight                  loaded from conv1.weight                       of shape (64, 3, 7, 7)
2019-03-14 14:03:36,851 maskrcnn_benchmark.trainer INFO: Start training
Traceback (most recent call last):
File "tools/train_net.py", line 171, in
main()
File "tools/train_net.py", line 164, in main
model = train(cfg, args.local_rank, args.distributed)
File "tools/train_net.py", line 73, in train
arguments,
File "/home/chenfei/github/maskrcnn-benchmark/maskrcnn_benchmark/engine/trainer.py", line 66, in do_train
loss_dict = model(images, targets)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in call
result = self.forward(*input, **kwargs)
File "/home/chenfei/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/detector/generalized_rcnn.py", line 49, in forward
features = self.backbone(images.tensors)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in call
result = self.forward(*input, **kwargs)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/container.py", line 92, in forward
input = module(input)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in call
result = self.forward(*input, **kwargs)
File "/home/chenfei/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/backbone/resnet.py", line 127, in forward
x = getattr(self, stage_name)(x)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in call
result = self.forward(*input, **kwargs)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/container.py", line 92, in forward
input = module(input)
File "/home/chenfei/anaconda3/envs/maskrcnn_benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in call
result = self.forward(*input, **kwargs)
File "/home/chenfei/github/maskrcnn-benchmark/maskrcnn_benchmark/modeling/backbone/resnet.py", line 330, in forward
out += residual
RuntimeError: The size of tensor a (334) must match the size of tensor b (336) at non-singleton dimension 3
layer1
Sequential(
(0): BottleneckWithFixedBatchNorm(
(conv1): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
(1): BottleneckWithFixedBatchNorm(
(conv1): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(64, 64, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
)
layer2
Sequential(
(0): BottleneckWithFixedBatchNorm(
(downsample): Sequential(
(0): Conv2d(64, 128, kernel_size=(1, 1), stride=(2, 2), bias=False)
(1): FrozenBatchNorm2d()
)
(conv1): Conv2d(64, 128, kernel_size=(3, 3), stride=(2, 2), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(128, 128, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
(1): BottleneckWithFixedBatchNorm(
(conv1): Conv2d(128, 128, kernel_size=(3, 3), stride=(1, 1), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(128, 128, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
)
layer3
Sequential(
(0): BottleneckWithFixedBatchNorm(
(downsample): Sequential(
(0): Conv2d(128, 256, kernel_size=(1, 1), stride=(2, 2), bias=False)
(1): FrozenBatchNorm2d()
)
(conv1): Conv2d(128, 256, kernel_size=(3, 3), stride=(2, 2), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(256, 256, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
(1): BottleneckWithFixedBatchNorm(
(conv1): Conv2d(256, 256, kernel_size=(3, 3), stride=(1, 1), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(256, 256, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
)
layer4
Sequential(
(0): BottleneckWithFixedBatchNorm(
(downsample): Sequential(
(0): Conv2d(256, 512, kernel_size=(1, 1), stride=(2, 2), bias=False)
(1): FrozenBatchNorm2d()
)
(conv1): Conv2d(256, 512, kernel_size=(3, 3), stride=(2, 2), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(512, 512, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
(1): BottleneckWithFixedBatchNorm(
(conv1): Conv2d(512, 512, kernel_size=(3, 3), stride=(1, 1), bias=False)
(bn1): FrozenBatchNorm2d()
(conv2): Conv2d(512, 512, kernel_size=(3, 3), stride=(1, 1), padding=(1, 1), bias=False)
(bn2): FrozenBatchNorm2d()
)
)

The resnet18 structure is not right: you are using the Bottleneck block, and not the BasicBlock.
If you change this it should work

Is the BasicBlock already implemented?