keepass: bring back and update plugins load patches

Motivation for this change
Plugins loading was broken as those patches were removed
in latest release. I brought patches back and updated them
onto 2.38 release code base.
This closes #35446.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build keepass

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘mono-<IP_ADDRESS>’ in /var/lib/gc-of-borg/nix-test-rs-3/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-3/pkgs/development/compilers/mono/generic.nix:90 is not supported on ‘aarch64-linux’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

Failure on x86_64-darwin (full log)
Partial log (click to expand)
Package ‘xdotool-3.20160805.1’ in /private/var/lib/ofborg/checkout/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/lnl7-mac/pkgs/tools/X11/xdotool/default.nix:23 is not supported on ‘x86_64-darwin’, refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowBroken = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowBroken = true; }
to ~/.config/nixpkgs/config.nix.

I tried:
       (pkgs.keepass.override {
          plugins = with pkgs; [
            keepass-keepassrpc
          ];
        })

and the build failed with the following error:
these derivations will be built:
  /nix/store/ig95qbl30lqdrgci9hqs842idgyyggdq-keepass-2.38.drv
  /nix/store/vnlli1nn61g57giql0z5ilxf7iyx16c0-staging.drv
these paths will be fetched (0.24 MiB download, 0.26 MiB unpacked):
  /nix/store/82fw1wqj109n8qv2fggnhqbqq287a302-keepassrpc-<IP_ADDRESS>
  /nix/store/pbs43gw4fkn4mz8ip1a97kdr7w526ysi-keepassrpc-<IP_ADDRESS>
copying path '/nix/store/82fw1wqj109n8qv2fggnhqbqq287a302-keepassrpc-<IP_ADDRESS>' from 'https://cache.nixos.org'...
copying path '/nix/store/pbs43gw4fkn4mz8ip1a97kdr7w526ysi-keepassrpc-<IP_ADDRESS>' from 'https://cache.nixos.org'...
building '/nix/store/ig95qbl30lqdrgci9hqs842idgyyggdq-keepass-2.38.drv'...
unpacking sources
unpacking source archive /nix/store/5cxnr3yfmi23bl0w6mk7cfrmjawx5dr0-KeePass-2.38-Source.zip
source root is .
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file ./.attr-0
warning: file ./.attr-0 may be generated; SOURCE_DATE_EPOCH may be non-deterministic
patching sources
applying patch /nix/store/b3ri3isia4pgqjiqw919ssdhhrsmiryp-fix-paths.patch
patching file KeePass/Native/NativeMethods.Unix.cs
patching file KeePass/Util/ClipboardUtil.Unix.cs
patching file KeePassLib/Native/ClipboardU.cs
patching file KeePassLib/Utility/MonoWorkarounds.cs
patching file KeePass/Forms/MainForm.cs
patch: **** malformed patch at line 14:                         // of loaded plugins have been updated already)
builder for '/nix/store/ig95qbl30lqdrgci9hqs842idgyyggdq-keepass-2.38.drv' failed with exit code 2
cannot build derivation '/nix/store/vnlli1nn61g57giql0z5ilxf7iyx16c0-staging.drv': 1 dependencies couldn't be built
error: build of '/nix/store/vnlli1nn61g57giql0z5ilxf7iyx16c0-staging.drv' failed

Success on x86_64-linux (full log)
Partial log (click to expand)
/nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38 /tmp/nix-build-keepass-2.38.drv-0
/tmp/nix-build-keepass-2.38.drv-0
Created /nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38/lib/pkgconfig/KeePassLib.pc
rscFileExt=ico
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38
patching script interpreter paths in /nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38
checking for references to /tmp/nix-build-keepass-2.38.drv-0 in /nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38...
/nix/store/ily135iv59svkfyv297r10035icd3mdw-keepass-2.38

@Mic92 thanks for testing! Should be fixed now.

Thanks! Plugin was listed now.


Add an important example to Closures setTimeout

The additional argument to setTimeout wasn't mentioned, and it's a really neat way to achieve this.

Neat! I wouldn't say that 'behaves as a closure' though. It would be better to say 'this passes these arguments through to the callback'

Sure, will change that now

Would it be possible to specify the legacy envs that don't support the
additional args please?
On Wed, Jan 14, 2015 at 11:11 AM, Sam Morrow<EMAIL_ADDRESS>wrote:

Sure, will change that now
—
Reply to this email directly or view it on GitHub
https://github.com/BonsaiDen/JavaScript-Garden/pull/265#issuecomment-69901573
.

MDN specify it as "passing additional parameters to the function in the first syntax does not work in Internet Explorer 9 and below".
If you are happy I will just amend it to IE < 9;

wonderful!
On Wed, Jan 14, 2015 at 11:58 AM, Sam Morrow<EMAIL_ADDRESS>wrote:

MDN specify it as "passing additional parameters to the function in the
first syntax does not work in Internet Explorer 9 and below"
https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers.setTimeout
.
If you are happy I will just amend it to IE < 9;
—
Reply to this email directly or view it on GitHub
https://github.com/BonsaiDen/JavaScript-Garden/pull/265#issuecomment-69906418
.


Unit testing

This sets up Jest (with babel-jest for es6 support) as our unit testing framework. Stick tests in the tests directory, then run npm test to run the tests. So far just tests that a GameState can be constructed ok.

need write access to approve, lgtm


Remove old, unnecessary polymer and vulcanize functionality

Vulcanize and the polymerpatch were used for polymer functionality. Without the combination DartPad can still run appropriately.
This simplifies contribution to DartPad as users no longer need npm or vulcanize, plus the build and serve times are a little bit faster.
Fixes #1776

Thanks, this looks great. I'll deploy this to AppEngine so we can double check everything.

This is now deployed to https://20210224t103411-dot-dart-pad.appspot.com/, but It looks like files in the /packages directory aren't being served correctly:

@devoncarew do you know what might be causing this?

I'm not sure - perhaps we never had to serve content out of that directory before due to the vulcanization? I'd check the app.yaml settings.

It might also be worth doing this in a few more stages (it looks like we're removing the polymer patch script, removing vulcanize, and updating the iframe event listener all in one go).

@parlough I needed to change some lines in web/app.yaml, it looks like vulcanize might have been renaming some directories:
  - url: /packages/codemirror
    static_dir: packages/codemirror

  - url: /packages/dart-pad
    static_dir: packages/dart_pad

  - url: /packages/split
    static_dir: packages/split

  - url: /packages/mdc_web
    static_dir: packages/mdc_web

The polymer patch script and the iframe event handler go together and without the "vulcanization" could potentially cause issues in the order of the event registration behavior.

@johnpryan I've gone ahead and updated the app.yaml. I didn't think to check that, sorry!

LGTM. Testing on the above spot checking link feels good to me. Is there is a way of testing embedding?

The embeds can be tested https://20210224t105113-dot-dart-pad.appspot.com/example/embed.html, and seem to be working the same as https://dartpad.dev/example/embed.html


Building with latest commit to fix ESP32-S3 DAC error results in failed build

Building rust-esp32-std-demo for the ESP32-S3 fails to build.
On commit "b28d5454adc620b57b7021291056eca60315d3ed", the latest at time of writing I get the following error:
error[E0412]: cannot find type `dac_channel_t` in this scope
     --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/esp-idf-hal-0.23.2/src/gpio.rs:75:25
      |
75    |     fn dac_channel() -> dac_channel_t;
      |                         ^^^^^^^^^^^^^ help: a type alias with a similar name exists: `adc_channel_t`
      |
     ::: /home/user/rust-esp32-std-demo/target/xtensa-esp32s3-espidf/release/build/esp-idf-sys-d57948dc3e50df5e/out/bindings.rs:28769:1
      |
28769 | pub type adc_channel_t = c_types::c_uint;
      | ----------------------------------------- similarly named type alias `adc_channel_t` defined here

For more information about this error, try `rustc --explain E0412`.
error: could not compile `esp-idf-hal` due to previous error
warning: build failed, waiting for other jobs to finish...
error: build failed

On the previous commit "090311018dbbb0edc2efc8578c089edf4d59b10d", I get the following error:
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:627:20: warning: section does not match previous declaration [-Wsection]
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:356:20: note: previous attribute is here
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:646:26: warning: section does not match previous declaration [-Wsection]
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:398:26: note: previous attribute is here
  /home/user/.cargo/git/checkouts/esp-idf-sys-d4c2e811b42d99d6/0903110/src/include/esp-idf/bindings.h:65:10: fatal error: 'driver/dac.h' file not found
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:627:20: warning: section does not match previous declaration [-Wsection], err: false
  /home/user/.espressif/esp-idf-master/components/freertos/FreeRTOS-Kernel/portable/xtensa/include/freertos/portmacro.h:646:26: warning: section does not match previous declaration [-Wsection], err: false
  /home/user/.cargo/git/checkouts/esp-idf-sys-d4c2e811b42d99d6/0903110/src/include/esp-idf/bindings.h:65:10: fatal error: 'driver/dac.h' file not found, err: true

I realise the latest commit is supposed to fix it, however I cannot build the latest. As a work around I have edited 'src/include/esp-idf/bindings.h' of commit "090311018dbbb0edc2efc8578c089edf4d59b10d", and modified line 65 to say '#include "driver/dac_common.h"' instead of the following as a hacky workaround.
https://github.com/esp-rs/esp-idf-sys/blob/9b49ade5fa985c5f0aa3a31b2f758117078c7fde/src/include/esp-idf/bindings.h#L65
From then on I am able to build and flash the project to my ESP32-S3 Dev Board successfully.

esp-rs/esp-idf-hal#12 will fix this.

Should work fine now, after cargo update and then a clean build.


 Two new flags are being added:

git-signing-key-path, which should contain the path of a local GPG private key to sign commits,
git-signing-key-passphrase, which is used to decrypt the local GPG private key if it is encrypted.

thanks for your contribution!


Image training error with small dataset

Value cannot be null.
Parameter name: source

@gocool67 Sorry you've run into this problem. Quick question, are you using only one image example per training class? Or training only one class?
We've seen this before due to very small number of images per class.

@gocool67 Any luck with adding additional images?

Sorry to late reply,
May be you right but there is not one image but small scale of images, I mean 20+ images over there
I will try with more images soon

I am try create solutions on lion image tracking
But I not able to find image of lion in large numbers
On Thu, Oct 1, 2020, 11:53 PM Becca McHenry<EMAIL_ADDRESS>wrote:

Any update?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-702315434,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BUZ3JA333ZHQM5VWWQLSITCJHANCNFSM4P4DG3OA
.

Do you only have one class - meaning do you only have one folder of images? Is "Lion" the only class you're trying to identify?

@gocool67 Any update here? Are you using more than one class (more than just Lion)?

I am using lion and lioness, and apart from this my definition is indentify
lion, so there is on folder my be
Like unique lion from several images
You got my point ?
On Thu, Oct 22, 2020, 1:48 AM Becca McHenry<EMAIL_ADDRESS>wrote:

@gocool67 https://github.com/gocool67 Any update here? Are you using
more than one class (more than just Lion)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-713849637,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BUYSAI7OKZX3PHL4J3LSL4627ANCNFSM4P4DG3OA
.

@gocool67 Does your data look like this?

No,
As human have finger print and facial difference to identify person to
person, I want to same on lion to help census of lion with out interfering
them life
Nice to make an interest on it, thanks
I approached to give name to lion like this
http://livingwithlions.org/mara/lions/akiki/
Thanks
Gokul
On Mon, Oct 26, 2020, 10:01 PM Becca McHenry<EMAIL_ADDRESS>wrote:

@gocool67 https://github.com/gocool67 Does your data look like this? [image:
image.png]
https://camo.githubusercontent.com/f841218ac2e5a8cba216bf5df160f3a5cb06a35d/68747470733a2f2f696d616765732e7a656e68756275736572636f6e74656e742e636f6d2f3564353563336436386661633834303030313331346561612f65396235656461632d306432632d343036362d393063392d343966653638313038626334
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-716667776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BU4WSQ743VKSXCEPDQLSMWP6DANCNFSM4P4DG3OA
.

@gocool67 Thanks for the additional info! I understand your scenario now. If you share you data or data source with me I can try it on my side.

Sure,
I am requesting to some data providers but due to clearing it is in waiting
mode.
I ask few provides to give me data but still not positive response,I will
update on same and if they are not give then I am plan to download from my
own but it is not in as much.
Thanks
Gokul
On Tue, Oct 27, 2020, 10:12 PM Becca McHenry<EMAIL_ADDRESS>wrote:

@gocool67 https://github.com/gocool67 Thanks for the additional info! I
understand your scenario now. If you share you data or data source with me
I can try it on my side.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-717373625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BUY4J6GAMJNPOP4ABL3SM3Z7NANCNFSM4P4DG3OA
.

@gocool67 Sounds like a cool project! If you need help let me know.

Sure, thanks
I sure need you in detail how I trained or modify module
Thanks
Gokul
On Wed, Nov 4, 2020, 9:46 PM Becca McHenry<EMAIL_ADDRESS>wrote:

@gocool67 https://github.com/gocool67 Sounds like a cool project! If
you need help let me know.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-721827393,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BU37ZKPTUBMEDZNVYLTSOF44DANCNFSM4P4DG3OA
.

@gocool67 Can you share your data with me?

Sorry for the late reply,
But data providers are not responding
Thanks
GOKUL Hirani
On Sun, Nov 8, 2020, 11:17 PM Becca McHenry<EMAIL_ADDRESS>wrote:

@gocool67 https://github.com/gocool67 Can you share your data with me?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/machinelearning-modelbuilder/issues/945#issuecomment-723643124,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIG3BU6ZTLUZDR3EKFQM2V3SO3KURANCNFSM4P4DG3OA
.

@gocool67 We've made a lot of changes since you filed this last August. A larger dataset should work. It if doesn't (or you need other help with this project) feel free to re-open this issue. Thanks!


Data viz ultimate image update battle royale

Advanced charts / Dashboards images WIP

Hey, it looks like you’ve marked this PR as a work in progress, I’m going to switch it over to a draft PR, please feel free to mark it “ready for review” at the bottom whenever you’d like us to be pinged to come take a look!

Looks great so far 💯
Thanks Jeannie for taking on this MASSIVE piece of work 🙂
One piece I'd change is the Mapbox theme URLs
There are 2 types of URLs we're going to need in that section (2nd one is more important):

URLs that you'll actually use in a Mapbox map to apply the theme
White: mapbox://styles/carbondesignsystem/ck7c8cfpp08h61irrudv7f1xg
G10: mapbox://styles/carbondesignsystem/ck7c8ce1y05h61ipb2fixfe76
G90: mapbox://styles/carbondesignsystem/ck7c8ccac08jj1imhvd2g4qfb
G100: mapbox://styles/carbondesignsystem/ck7c89g8708gy1imlz9g5o6h9

URLs to previews of the styles
White: https://api.mapbox.com/styles/v1/carbondesignsystem/ck7c8cfpp08h61irrudv7f1xg.html?fresh=true&title=view&access_token=pk.eyJ1IjoiY2FyYm9uZGVzaWduc3lzdGVtIiwiYSI6ImNrN2M4MXBwNjAxMHkzbG1vM3FpajJvbGIifQ.uMK_mzxHwI4dWUOG-uBedQ
G10: https://api.mapbox.com/styles/v1/carbondesignsystem/ck7c8ce1y05h61ipb2fixfe76.html?fresh=true&title=view&access_token=pk.eyJ1IjoiY2FyYm9uZGVzaWduc3lzdGVtIiwiYSI6ImNrN2M4MXBwNjAxMHkzbG1vM3FpajJvbGIifQ.uMK_mzxHwI4dWUOG-uBedQ
G90: https://api.mapbox.com/styles/v1/carbondesignsystem/ck7c8ccac08jj1imhvd2g4qfb.html?fresh=true&title=view&access_token=pk.eyJ1IjoiY2FyYm9uZGVzaWduc3lzdGVtIiwiYSI6ImNrN2M4MXBwNjAxMHkzbG1vM3FpajJvbGIifQ.uMK_mzxHwI4dWUOG-uBedQ
G100: https://api.mapbox.com/styles/v1/carbondesignsystem/ck7c89g8708gy1imlz9g5o6h9.html?fresh=true&title=view&access_token=pk.eyJ1IjoiY2FyYm9uZGVzaWduc3lzdGVtIiwiYSI6ImNrN2M4MXBwNjAxMHkzbG1vM3FpajJvbGIifQ.uMK_mzxHwI4dWUOG-uBedQ

Amazing work Jeannie! Thanks for taking this on <3. I haven't gone through all pages yet. Comments below are page by page. @janchild I noticed a few small things about content but will defer to your opinion.
Advanced charts
Alluvial

some links/slinky are in purple 30 and blue 30. These colors are not part of the white theme categorical palette and are not 3:1 accessible against white. I agree they look nice and I made big push to bring in the 30s earlier on but got shot down. If we wanna bring the 30s back, we probably should be consistent across Palette page and offer a justification.

Heat map

Nitpick, but all things here are graphic representation of data. I'd simplify and remove unhelpful words.

This is inaccurate. Lightest value on dark theme represent highest value. In general, it might be better to say higher contrast against background denote higher value.

Heatmap should be using one of the sequential palettes (purple or blue). Also palette page should be updated to show monochromatic palette with a wider range of shades (10-80?) https://carbondesignsystem.com/data-visualization/color-palettes#monochromatic

A few potential small errors. See image below:

I think this caption is unhelpful for users. It seems like a design justification we want to either keep to ourselves, or document as a "Don't do" if having borders is an option.

Should Heatmaps have an outline for the area with data (not individual cells)? Accessibility requirement is "meaningful graphic objects" has to be 3:1 against background. I'd expect geo-heatmaps to definitely have an g50 border so any islands don't get lost.

I just googled "trheat" map and found no match... Doesn't look like an established term. But maybe Jan or someone content could check if it's okay.

@jeanservaas Great work and looking good.
Let’s keep in mind all the accessibility rules on color can be countered with additional interaction/feedback. If you strictly follows rules a few of the charts actually would not communicate what they intend. A heat map can be one of those when having many cells. You can’t add a divider line without destroying the cart and what it communicates. It’s why we need to make sure we cover those interactions, hovers, and tooltips, etc.
We can confirm with accessibility team but I’m certain we had this discussion with them on a call with Cognos team.

@jeanservaas Also, see the bad ass advanced charts page reminds me the “Charts types” page needs a few updated
—  Radar enabled
— remove tags for Stacked area”
— Add tags to Tree map, Heat map and Parallel coordinates
What is Stream chart? Is that same as curved area? Or do we not cover this at all yet?

@mjabbink this is the demos PR, it'll automatically pull down all demos every time we update the version for @carbon/charts in the Carbon website.
However, we still have the issue of showing over 20 demos on 1 page, it's slow even on my Macbook Pro, so slower devices (android phones etc.) might suffer

@theiliad works really well for me so I cannot comment on speed.
A side note on that preview link you sent above. The axis type and labels are not Plex

@theiliad works really well for me so I cannot comment on speed.
A side note on that preview link you sent above. The axis, labels, and legend type are not Plex. https://carbon-website-kasaqbdlj.now.sh/data-visualization/basic-charts/

Yes the condensed font is not imported onto the carbon website. Vince suggested using the variable font to create the same look as condensed

@theiliad The variable font solution can work. I also think Carbon needs to support the use of Condensed. I’ll make this a priority because we must use Plex and cannot mix it with another font.

Condensed fonts should be included in Carbon, they may just not be used on the website. https://github.com/carbon-design-system/carbon/pull/5680


Zombie processes exceeding ulimits

I have a k8s cluster running for about a month. One of the nodes became very unresponsive, on sshing into this node (which worked after a few attempts).
ps -ef | grep defunct | wc -l gives 18622 processes.
Here is a sample of ps -ef | grep defunct
root     63412 16414  0 Mar31 ?        00:00:00 [wc] <defunct>
root     63451 16414  0 Mar31 ?        00:00:00 [wc] <defunct>
root     63588 16414  0 Mar31 ?        00:00:00 [wc] <defunct>
root     63679 16414  0 Mar31 ?        00:00:00 [wc] <defunct>
root     63686 16414  0 Mar31 ?        00:00:00 [wc] <defunct>
where 16414 is the kubelet process. Any idea why they're not getting killed properly?

After restarting the kubelet process on these nodes. Things seem to be fine. It's been around 4 days and not observing any such process on ps -aux.
Something very specific to my setup might have triggered this?

Hi @rushabhnagda11. Take a look at the Kubernetes cluster troubleshooting guide: https://kubernetes.io/docs/tasks/debug-application-cluster/debug-cluster/
I'm closing this issue for now, but feel free to re-open if you gather more information.

not reopening since I cant find a way to reproduce


Error running grind serve locally

What happened?
The contribute guide says:
https://github.com/dart-lang/dart-pad/blob/master/CONTRIBUTING.md#how-to-run-dartpad-locally
pub global activate grinder
grind serve

I get an error running grind serve:
> flutter pub global activate grinder
Resolving dependencies...
+ async 2.4.2 (2.5.0 available)
+ charcode 1.1.3 (1.2.0 available)
+ cli_util 0.2.0 (0.3.0 available)
+ collection 1.14.13 (1.15.0 available)
+ file 5.2.1 (6.0.0 available)
+ glob 1.2.0 (2.0.0 available)
+ grinder 0.8.6
+ intl 0.16.1 (0.17.0 available)
+ js 0.6.2 (0.6.3 available)
+ meta 1.2.4 (1.3.0 available)
+ node_interop 1.2.1
+ node_io 1.2.0
+ path 1.7.0 (1.8.0 available)
+ pedantic 1.9.2 (1.10.0 available)
+ source_span 1.7.0 (1.8.1 available)
+ string_scanner 1.0.5 (1.1.0 available)
+ term_glyph 1.1.0 (1.2.0 available)
Downloading grinder 0.8.6...
Precompiling executables...
Precompiled grinder:init.
Precompiled grinder:grinder.
Precompiled grinder:_boot.
Installed executable grind.
Activated grinder 0.8.6.
~/src/dart-pad master ?1                                                                                4s 12:01:48
> grind serve
Error: Could not resolve the package 'git' in 'package:git/git.dart'.
Error: Could not resolve the package 'grinder' in 'package:grinder/grinder.dart'.
Error: Could not resolve the package 'yaml' in 'package:yaml/yaml.dart'.
tool/grind.dart:12:8: Error: Not found: 'package:git/git.dart'
import 'package:git/git.dart';
       ^
tool/grind.dart:13:8: Error: Not found: 'package:grinder/grinder.dart'
import 'package:grinder/grinder.dart';
       ^
tool/grind.dart:14:8: Error: Not found: 'package:yaml/yaml.dart'
import 'package:yaml/yaml.dart' as yaml;
       ^
tool/grind.dart:16:7: Error: Type 'FilePath' not found.
final FilePath _buildDir = FilePath('build');
      ^^^^^^^^
tool/grind.dart:17:7: Error: Type 'FilePath' not found.
final FilePath _pkgDir = FilePath('third_party/pkg');
      ^^^^^^^^
tool/grind.dart:18:7: Error: Type 'FilePath' not found.
final FilePath _routeDir = FilePath('third_party/pkg/route.dart');
      ^^^^^^^^
tool/grind.dart:300:19: Error: Type 'FilePath' not found.
String _printSize(FilePath file) =>

Steps to reproduce problem
pub global activate grinder
grind serve

Additional info
Browser
Browser:
Version:

flutter --version
Flutter 1.22.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision<PHONE_NUMBER> (9 weeks ago) • 2020-12-10 11:54:40 -0800
Engine • revision ae90085a84
Tools • Dart 2.10.4

DartPad's output
Did DartPad print anything to the console pane? If so, paste it below:
[paste console output here]

If you were running Flutter code, you can also paste an image of the
Flutter output directly into this bug report.

Did you run pub get in the dart-pad directory before trying to serve the site?

i ran flutter pub get successfully

Hmm. Could you try running flutter pub run grinder serve instead and let me know if that works?

Hmm. Could you try running flutter pub run grinder serve instead and let me know if that works?

thanks that works, sorry for the n00b error

I'm reopening to update documentation

Fixed with https://github.com/dart-lang/dart-pad/commit/14be9f0e2fdf9a4be8eb4fe87f018176e7cdbb8d


feat(iOS): optimize for iOS config option

Right now iOS is very slow.  There are possibly some things we can do (http://stackoverflow.com/questions/25915967/how-to-make-appium-tests-run-faster-on-ios).

@sjelin are the tests only slow when combined with appium or also if the "normal" iOS safari driver is used?


Minimal 2.0 manifests to get a 2.0 build going.

Signed-off-by: dblock<EMAIL_ADDRESS>Description
This will enable a 2.0 build of just OpenSearch and OpenSearch Dashboards without rc1 and unblock https://github.com/opensearch-project/opensearch-build/issues/2078
Issues Resolved
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #2090 (3ea8003) into main (69ef45f) will increase coverage by 0.27%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #2090      +/-   ##
============================================
+ Coverage     94.23%   94.50%   +0.27%
============================================
  Files           198      152      -46
  Lines          3902     3732     -170
  Branches         29       19      -10
============================================
- Hits           3677     3527     -150
+ Misses          219      205      -14
+ Partials          6        0       -6

Impacted Files
Coverage Δ

src/system/temporary_directory.py
83.87% <0.00%> (-12.91%)
:arrow_down:

src/system/os.py
93.75% <0.00%> (-6.25%)
:arrow_down:

tests/jenkins/jobs/BuildArchive_Jenkinsfile

...sts/jenkins/jobs/ArchiveAssembleUpload_Jenkinsfile

...ts/jenkins/jobs/uploadMinSnapshotsToS3_Jenkinsfile

...RunBwcTestScript_OpenSearch_Dashboards_Jenkinsfile

...nkins/jobs/RpmDashboardsDistValidation_Jenkinsfile

src/jenkins/InputManifest.groovy

...rtifacts_actions_OpenSearch_Dashboards_Jenkinsfile

...ests/jenkins/jobs/CopyContainer_docker_Jenkinsfile

... and 38 more

Continue to review full report at Codecov.

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

Close in favor of this issue: https://github.com/opensearch-project/opensearch-build/issues/2091


Video Recording on iOS has 1-2 seconds cut off at end of video🐛

What were you trying to do?
Recording a video on an iOS device, with the expectation that the final video file would include the frames from the moment "startRecording" was called until the moment "stopRecording" was called.
Reproduceable Code
<Camera
    ref={ref => {
	this.camera = ref;
    }}
    style={Style.cameraContainer}
    isActive={true}
    device={this.state.cameraDevice}
    audio={true}
    video={true}
    zoom={this.state.zoom}
    videoStabilizationMode={'auto'}
    preset={'hd-1920x1080'}
></Camera>

What happened instead?
The last 1-2 seconds of video are not present in the final recording file. This problem does not apply to Android devices. I recorded a timer and stopped the video when the timer reached 5 seconds. The video file that was saved ended before the timer reached 4 seconds.
Relevant log output
No response
Device
iPad 9th Gen (15.5)
VisionCamera Version
2.13.0
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Closing as this is a stale issue - this might have been fixed with the full rewrite in VisionCamera V3 (🥳) - if not, please create a new issue.
If your issue has been fixed, consider sponsoring me on GitHub to say thanks 💖

I'm unable to upgrade to VisionCamera V3 until the orientation issues are resolved, and this problem still occurs with the latest version of V2. In addition, the audio is out of sync with the video, as it seems like the video recording starts 1-2 seconds before the button is pressed, and ends 1-2 seconds early. The audio is actually correct but since the video is not, it appears out of sync. I can also confirm this happens with iOS 17 on a variety of iOS devices.

In addition, the audio is out of sync with the video

In V3?

In addition, the audio is out of sync with the video

In V3?

This only happens in V2. Apologies if I'm not supposed to open issues for V2 anymore, I know there's only limited support being provided.

Ah - yea no worries mate! But yes you're right I can't really provide support for both codebases. Hope you'll figure this one out or are able to upgrade to V3!


Rmc 177 qid pairs for welsh questionnaires

Motivation and Context
Export Initial Contact Questionnaire for Wales
What has changed
New template added.
Change to how manifest is generated.
How to test?
Deploy in Docker Dev and run acceptance tests
Links
https://trello.com/c/W5MYJG94/654-rmc-177-manage-uac-qid-pairs-for-welsh-initial-contact-questionnaire-print-packs-13

 RMC-177 - Manage UAC/QID pairs for Welsh Initial Contact Questionnaire print packs (13)


Experiment: New DRL Parser : Test failure : Unknown language level

Parent issue: https://github.com/apache/incubator-kie-drools/issues/5678
For example, KnowledgeBuilderTest.testWarnOnFunctionReplacementand some other tests fail with
java.lang.RuntimeException: Unknown language level
	at org.drools.drl.parser.DRLFactory.getDRLParser(DRLFactory.java:109)
	at org.drools.drl.parser.DRLFactory.buildParser(DRLFactory.java:71)
	at org.drools.drl.parser.DrlParser.parse(DrlParser.java:87)
	at org.drools.drl.parser.DrlParser.parse(DrlParser.java:93)
	at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:314)
	at org.drools.compiler.builder.impl.KnowledgeBuilderImpl.addPackageFromDrl(KnowledgeBuilderImpl.java:300)

It means DrlParser and DRLFactory require more (hopefully clean) integration with the new parser.

I'm working in a way that removing DRL10 and introduce a system property drools.antlr4.parser.enabled.
Kind of overlapping https://github.com/apache/incubator-kie-drools/issues/5681

Fixed by https://github.com/apache/incubator-kie-drools/pull/5693


Changing the Email Address of a Invited Expense

Describe the bug
This issue was reported at the slack thread; https://opencollective.slack.com/archives/GFH4N961L/p1702663040491629. Trying to change the email address of an already submitted expense invite seems to error out giving;

To Reproduce
Steps to reproduce the behavior:

Go to a collective and invite an expense (make sure to choose a non existing user on the platform; i.e: set the name and email manually)
Go to the draft expense submitted and click on the actions button and edit the expense
Change the email address and try to save
See error

Expected behavior
A payout method should not be expected from an expense that is invited; since the user is going to set the payout method in the future.

cc @kewitz

While I could reproduce this issue on production for this specific expense, I cannot reproduce this on staging. I'll keep and lookout if this issue occurs again and re-open this issue if necessary.


Create flag for custom output -directory

This is needed especially for Docker.

Fixed docker issue with Dockerfile & WORKDIR. No need for this, at least ATM.


Documentation Request: Clarity for matmul operator

What is your issue?
Currently the matmul documentation states that the operator does "matrix multiplication". It's unclear if this means np.matmul semantics, or xr.dot.
It's probably worth explicitly calling out the distinction inline between np.matmul and np.dot, with a short explanation why this isn't the np.matmul behavior.

Thanks for pointing this out @mthramann ! We would happily accept a PR to clarify this :)


Update our plugin example

Update our plugin example repo to conform with the new changes to the plugin api.
https://github.com/heptio/velero-plugin-example

Closed by https://github.com/heptio/velero-plugin-example/pull/21


New TF binding site

Loz1 response elements
synonym LRE elelments
A conserved sequence   (5ʹ-CGNMGATCNTY-3') transcription repressor binding site  required for gene repression in the presence of  high zinc
parent
core_eukaryotic_promoter_element (SO:0001660)
(I'm not sure if this will be the parent in the future, but it is where some of the other TF binding sites are?

Hi Ruth, do you think this might be a better child under TF_binding_site (SO:0000235) instead of core_eukaryotic_promoter_element?
Thanks,
Dave

Hi @ValWood,
I apologize, I have been emailing another person named Ruth. Do you think this might be a better child under TF_binding_site (SO:0000235) instead of core_eukaryotic_promoter_element?
Thanks,
Dave

Yes, I think TF_binding site works fine.
...in this case some of the existing binding sites we use might need to be migrated under this term if they are not there already:
https://www.pombase.org/browse-curation/dna-binding-sites

Hi Val, we found a term for zinc_repressed_element (SO:0002006). Would this new term be a synonym of this, or a child term to this?

Probably a child. There are almost certainly others.

Hi Val,
A new child term "LOZ1_response_element" has been assigned ID SO:0002225. It has been pushed to the GitHub page and will be updated on the browser when the server refreshes later this week.
Thanks,
Dave

thanks!


Adding context to existing CS/CF instances

ATM we have two APIs for adding context to CompletionStage and CompletableFuture:

ManagedExecutor: you can create contextualised CompletableFuture instances that are completed or incomplete, but you can't wrap existing instances.
ThreadContext: you can only wrap contextualised CompletableFuture and CompletionStage instances, but those can't have an Executor defined, and will throw when calling Async methods.

While working around a bug, I found myself having to call the Async methods of a CS I had wrapped using ThreadContext, and it threw at me.
Then I found myself having to switch to using ManagedExecutor to wrap my CS stuff, but although I could replace some calls to tc.withContextPropagation(CompletableFuture.completedValue(...))  I found I could not wrap existing CS instances with that API. The bext thing I found was to use:
managedExecutor.completedFuture(null).thenCompose(v -> pool.begin())

Which is not great, but also hard to guess to people not familiar with CS and composition. I couldn't use existing ManagedExecutor methods to wrap a CS I did not create myself.
This leads me to believe there's something missing in the spec.
Now, additionally, for SmallRye-CP we had to add a method to our impl of ContextManager.Builder:
        public Builder withDefaultExecutorService(ExecutorService executorService) {
            this.defaultExecutorService = executorService;
            return this;
        }

To be able to specify a default executor service for all built ManagedExecutor (unless overridden by a similar method in our impl of ManagedExecutor.Builder).
Which leads me to think that for deployments where a (single) default executor service can be specified, it shouldn't be an issue to call Async methods of contextualised CS/CF by ThreadContext. But the current API forbids this.
Let me know how it's implemented in OpenLiberty, but if you have the same builder extensions to be able to specify a default executor service, we could add those to the spec to the three builders (ContextManager, ThreadContext and ManagedExecutor) and soften the API for wrapping CS/CF from ThreadContext wrt having a default executor?
I'd also favour add a method to be able to wrap existing CS/CF to ManagedExecutor and adding variants in ThreadContext  to be able to specify an ExecutorService when wrapping CS/CF.
This way, no matter which of the two APIs you're using you should be able to wrap existing CS/CF and even override the ExecutorService if it turns out your platform has no default.
WDYT?
I can work out a PR if you agree with the general direction. Or even do a PR just to help make a decision and discuss.

The possibility of an equivalent on ManagedExecutor for withContextCapture was something that came to mind while working on v1.0, but I had put the thought on hold to finish off the initial release, recognizing that thenCompose does provide a working (albeit ugly) solution as a stopgap measure.
I'd rather not see a ManagedExecutor supplied to a ThreadContext.Builder or new variants of the withContextCapture(stage, executor) methods to accept an executor parameter.  In both cases, that creates confusion with conflicting context propagation settings (the managed executor's vs the thread context's).
Instead, I think the right approach here is to create a parallel interface on ManagedExecutor for the Java 11 CompletableFuture.copy method, which directly matches the behavior one would expect out of a withContextCapture equivalent (copy is what we modeled withContextCapture after).  The spec already employs this approach for other methods on ManagedExecutor:  ManagedExecutor.newIncompleteFuture(), ManagedExecutor.runAsync(action), ManagedExecutor.supplyAsync(action), and so on, so it is very natural to have,
stage2 = ManagedExecutor.copy(stage1);

Here's a draft of what the JavaDoc might look like, copying directly from withContextCapture,
/**
 *
Returns a new CompletableFuture that is completed by the completion of the
 * specified stage.

 *
 *
The new completable future is backed by the ManagedExecutor upon which copy is invoked,
 * which serves as the default asynchronous execution facility
 * for the new stage and all dependent stages created from it, and so forth.

 *
 *
When dependent stages are created from the new completable future, thread context is captured
 * and/or cleared by the ManagedExecutor. This guarantees that the action
 * performed by each stage always runs under the thread context of the code that creates the stage,
 * unless the user explicitly overrides by supplying a pre-contextualized action.

 *
 *
Invocation of this method does not impact thread context propagation for the supplied
 * completable future or any dependent stages created from it, other than the new dependent
 * completable future that is created by this method.

 *
 * @param <T> completable future result type.
 * @param stage a completable future whose completion triggers completion of the new completable
 *        future that is created by this method.
 * @return the new completable future.
 */
<T> CompletableFuture<T> copy(CompletableFuture<T> stage);

The above addresses the first half of the issue, and since the comment is already getting a bit long, I'm going to stop here and post a second comment for the second half discussing configuring/using default executor services.

Regarding the second set of questions, OpenLiberty doesn't implement a ContextManager.Builder (it's optional and we didn't need one), however, we do have the concept of a default executor service.  This default executor service/thread pool isn't something that a user ever directly interfaces with and so they wouldn't be able to supply it to a spec method.  Instead, this default executor service/thread pool is what backs all managed executors and many other async operations as well.  For environments like this (with a built-in default executor/thread pool, or for an executor that is specified with the new ContextManager.Builder.withDefaultExecutorService method), it seems natural to lift the withContextCapture restriction against async stages and be able to utilize that executor for async operations.
Specifically regarding the proposal, that means I'm fine with the addition of:
ContextManager.Builder.withDefaultExecutorService(executor)
With respect to having withDefaultExecutorService on ThreadContext.Builder, it seems out of place.  ThreadContext ought to only concern thread context and only be used for thread context, so I don't think we should add withDefaultExecutorService there, but hopefully my proposal in the previous comment to add managedExecutor.copy will cover all of the scenarios where that would have been needed.
With regard to ManagedExecutor.Builder.withDefaultExecutorService(executor), I'm undecided.  I can see where this might provide additional flexibility in some cases, but I can also foresee ambiguity and potential collisions between the supplied executor's behavior and other builder config like the maxQueued/maxAsync settings.  With that in mind, a different option could be threadContext.createManagedExecutor(executor)?  Or, maybe threadContext.withContextCapture(stage, executor) (mentioned earlier) isn't be so bad if clearly documented that the thread context comes from the invoking threadContext instance, not the supplied executor.  I'm not sure what is best here, and will need to give this some more thought.

I'd rather not see a ManagedExecutor supplied to a ThreadContext.Builder or new variants of the withContextCapture(stage, executor) methods to accept an executor parameter. In both cases, that creates confusion with conflicting context propagation settings (the managed executor's vs the thread context's).

I was suggesting an ExecutorService. It would be clearly indicated that even if you pass a ManagedExecutor, its propagation settings would be ignored in favour of the ThreadContext.
ManagedExecutor.copy works for me, except that it should have a variant for CompletionStage because most of our APIs don't deal with CompletableFuture.

Specifically regarding the proposal, that means I'm fine with the addition of:
ContextManager.Builder.withDefaultExecutorService(executor)

Cool.

With respect to having withDefaultExecutorService on ThreadContext.Builder, it seems out of place. ThreadContext ought to only concern thread context and only be used for thread context, so I don't think we should add withDefaultExecutorService there, but hopefully my proposal in the previous comment to add managedExecutor.copy will cover all of the scenarios where that would have been needed.

They would indeed, but I thought it would make it more regular, and allow people to specify an ExecutorService that is not the default one, which can be handy because the CS/CF API doesn't let you specify one otherwise. I don't have a use-case for this, so I'm not going to fight over it and we can always add it later if a use-case appears. But I don't really see where it would hurt.

With regard to ManagedExecutor.Builder.withDefaultExecutorService(executor), I'm undecided. I can see where this might provide additional flexibility in some cases, but I can also foresee ambiguity and potential collisions between the supplied executor's behavior and other builder config like the maxQueued/maxAsync settings

Well, there's always going to be a bit of a question when it comes to that, especially because we can't query the ExecutorService's maxQueued/maxAsync settings to check if they are coherent.
But if you view the ManagedExecutor as a "view" over another ExecutorService you can easily defend that having a lower maxQueued/maxAsync setting in the view than in the backing ExecutorService restricts the view's window (which is fine), and having a larger setting in the view means we will never reach the max, but that's also acceptable: if you wanted to attain the max you could have given a different backing executor, or none at all and it would create one of the right size.

With that in mind, a different option could be threadContext.createManagedExecutor(executor)?

That would be easy to implement for us. But then I feel we could solve a bunch of issues by adding ManagedExecutor.getThreadContext() as well, to get additional operations :)

maybe threadContext.withContextCapture(stage, executor) (mentioned earlier) isn't so bad if clearly documented that the thread context comes from the invoking threadContext instance, not the supplied executor. I'm not sure what is best here, and will need to give this some more thought.

That is indeed the behaviour I expect. If that seems acceptable, then ThreadContext.Builder.withDefaultExecutorService(ExecutorService) can't be so unacceptable, then, because it provides a default for that parameter.

ManagedExecutor.copy works for me, except that it should have a variant for CompletionStage because most of our APIs don't deal with CompletableFuture.

Agreed.  I would expect to have signatures for both CompletionStage and CompletableFuture, just like withContextCapture has.

With that in mind, a different option could be threadContext.createManagedExecutor(executor)?

That would be easy to implement for us. But then I feel we could solve a bunch of issues by adding ManagedExecutor.getThreadContext() as well, to get additional operations :)

If you want to have a ManagedExecutor.getThreadContext(), I would be fine with it.  This seems consistent because managed executor configuration clearly includes thread context settings and propagates thread context as well, so it makes sense that you would be able to obtain the ThreadContext instance which it uses (I think we basically implemented it this way as well, so there is no cost to us here to do this).
It seems like we have a lot of agreement already on many of the proposed interfaces.
I'm going to try to summarize those here.  Do these cover all of the scenarios you had in mind?
new ContextManager.Builder methods:
Builder withDefaultExecutorService(ExecutorService executorService)
new ThreadContext methods:
ManagedExecutor createManagedExecutor(Executor executor);
new ManagedExecutor methods:
<T> CompletableFuture<T> copy(CompletableFuture<T> stage);
<T> CompletionStage<T> copy(CompletionStage<T> stage);
ThreadContext getThreadContext();
Having just written the above right next to each other, I can see that we need to decide between java.util.concurrent.Executor versus java.util.concurrent.ExecutorService as the parameter type for the first two methods.  It doesn't make any difference to me - just make them consistent.  If you don't have any other way of deciding, we could just go with Executor because it looks like that is what the CompletableFuture API uses here.

Ah, good question. Thing is, ManagedExecutor really forwards calls to an ExecutorService so providing it with an Executor is a lot less useful.
But you're right that CS/CF use Executor, which is easier to implement. However, if both our implementations eventually delegate to an ExecutorService I'd say let's stick with this type at least for ContextManager.Builder.withDefaultExecutorService and ThreadContext.createManagedExecutor.
Given that this is on the builder for ContextManager which serves both for ManagedExecutor and ThreadContext I think it makes sense to make it ExecutorService because this is a platform API and platforms are more likely to delegate to that type than any hand-made Executor.
If we add ThreadContext.withContextCapture(CF, Executor) we can use Executor for CS/CF coherence. I've checked and our implementation only needs an Executor, so it's possible yours too.

Our global thread pool is an ExecutorService, but our implementation of ManagedExecutor is written such that Executor could alternatively be used if one was supplied, so we are compatible with either way.
I thought of one other reason why a user might be interested in supplying Executor rather ExecutorService, which is to prevent anyone with access to completion stages from attempting the shutdown operation. The following would not be possible with just Executor,
((ExecutorService) completableFuture.defaultExecutor()).shutdown();

This was never a concern when the default executor was a ManagedExecutor owned by the application, because the application is then just shutting down its own instance.  However, when backed by our global thread pool as the default executor, we will certainly need to include a layer in between here, because shutting that down would be catastrophic and not something that applications ought to be able to do.

In our case, we pass an ExecutorService which throws on shutdown methods. I think that's enough to avoid the issue.
As for ManagedExecutor being able to work when backed by a simple Executor, that must complexify the implementation, unless there's a simple implementation in the JDK that I'm unaware of…

So, in smallrye/smallrye-context-propagation#183 I've made an implementation of this, with the methods you mentioned, minus one:

new ContextManager.Builder methods:

Builder withDefaultExecutorService(ExecutorService executorService)

updated ThreadContext method JavaDoc (to allow async operations using built-in or configured executor)

 CompletableFuture withContextCapture(CompletableFuture stage)
 CompletionStage withContextCapture(CompletionStage stage)

new ManagedExecutor methods:

 CompletableFuture copy(CompletableFuture stage);
 CompletionStage copy(CompletionStage stage);
ThreadContext getThreadContext();

I did not add this one because I'm not sure it brings value, I think we can wait to see if it's useful:

new ThreadContext methods:

ManagedExecutor createManagedExecutor(Executor executor);

I had to add the notion that ThreadContext has a "default executor" which comes from either the ContextManager (as specified in its builder), or from the ManagedExecutor on which ManagedExecutor.getThreadContextwas called.
So I rephrased the javadoc for ThreadContext.withContextCapture(CompletableFuture) and ThreadContext.withContextCapture(CompletionStage) to mention that this default executor would be used for the Async methods which aren't passed an explicit Executor, and that they will still throw if there is no default executor.
I also mention in ManagedExecutor.getThreadContext that the resulting thread context uses this executor as default executor. Actually in the implementation they use the managed executor's forwarding ExecutorService because our ManagedExecutor is shallow.
In practice, ThreadContext.withContextCapture and ManagedExecutor.copy do the same thing now, when there is a default executor.
I did notice a weird detail wrt the unchanged setting in that only ThreadContext has such a setting, while ManagedExecutor does not. Which means that the ThreadContext returned by ManagedExecutor.getThreadContext is less configurable than those that don't belong to managed executors.
I remember a discussion about this discrepency a long time ago, but I don't remember why they differed.

If we add ThreadContext.withContextCapture(CF, Executor)

Hah, what's funny is that we already have this method as public in SmallRye for a long time.

I don't think there's a PR yet.

I don't think there's a PR yet.

Are you planning to create a PR (or already working on one)? Or would you rather have me create it?  I'm fine either way, just looking to avoid duplication.  It should be easy enough given that we have a bunch of draft method signatures and even some draft JavaDoc for it in the discussion above.

I can make a PR.

It's at #196.

And TCK at https://github.com/eclipse/microprofile-context-propagation/pull/197

@FroMage I can find ManagedExecutor.allOf . May be it is unnecessary or it is a gap. Could you please give some comments?

@FroMage I can't find ManagedExecutor.allOf . May be it is unnecessary or it is a gap. Could you please give some comments?

We didn't add managedExecutor.allOf because it seemed unnecessary, just a shortcut for doing:
stage = managedExecutor.copy(CompletableFuture.allOf(...));

@njr-11 thank you. But actually I use quarkus and it seems it does not provides microprofile-context-propagation-api 1.1 by some reason.

@njr-11 I counted how often allOf is used in my case - 25 times. I think it is not few. What do you think to add allOf to make API more symmetric?

@njr-11 I counted how often allOf is used in my case - 25 times. I think it is not few. What do you think of adding allOf to make API more symmetric?

It would be fine with me to add it if it makes the programming model easier to use for applications.  I expect the ManagedExecutor variant of allOf wouldn't be static like CompletableFuture.allOf is, because the resulting completion stage ought to be backed by a specific ManagedExecutor for the sake of any dependent stages that are added on to it.  Go ahead and open an issue for it (this current issue where we are discussing this is already closed out) and we can discuss it on the next MicroProfile Context Propagation call as a possible enhancement for the next release of the spec.


[performance] Listing repositories is slow

Description
Request to
/repo/search?sort=updated&order=desc&uid=3&team_id=undefined&q=&page=1&limit=100&mode=&archived=false
on dashboard page (http://root_path), right pane, takes almost 5 seconds for 50 repositories exists
Database - sqlite
At the same time same repository list on http://root_path/organization appears instantly
Screenshots
none
Gitea Version
1.20.1
Can you reproduce the bug on the Gitea demo site?
No
Operating System
Windows server 10.0
Browser Version
113

Oh, looks like for every repo 3 git commands are executed. Looks like information from database is not sufficient to display repo list. But in Json returned by rest method seems does not contains any special  data.

It is not clear, why here, in "https://root_path", after "SearchRepositoryByCondition" git commands are executed, but on "https://root_path/Organization" after the same "SearchRepositoryByCondition" - no git commands are executed and pageload is instant.

This issue comes from #24638 in v1.20 and should be resolved by #22743 in v1.21

Yes, I also ran into this after upgrading v1.19 to v1.20.4. Glad a fix is inbound!

I think this has been resolved. Please feel free to reopen if it is still a problem.

Yes, though also simply reorganizing indices in MSSQL also helped!


sqlfilter / json url parameter encoding

JSON does not want to be encoded as stringified URI. A JSON value may contain an ampersand (&) character. The JSON value should be stringified and URLComponent encoded.
The api module script should not be required to decode URI parameter. This should happen by default.
Hence the parameter value is already assumed to be encoded by the time the value is added to [filter] SQLParams array. The skip option for the wildcard is therefore unnecessary.

@dbauszus-glx Just pushed a fix to this i think - but needs testing by others.


Update systicks max sleep value when set CONFIG_BT

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_telink
https://github.com/telink-semi/hal_telink/commit/dbe339c95efc8adef1e6ad19c60af1e90312bb81
https://github.com/telink-semi/hal_telink/pull/16
telink-semi/hal_telink#16/files

Note: This message is automatically posted and updated by the Manifest GitHub Action.


ng new FAIL

When I'm trying to type ng new tutorial I get this message error right here :
OS  ? OS X El Capitan
module.js:327
    throw err;
    ^
Error: Cannot find module 'exists-sync'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object.<anonymous> (/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/lib/models/project.js:11:26)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)

I don't know what or why it shows up, help would be great 👍

npm install should have fix the issue.
make sure your npm version is : 3.10.2

You have to go into the /node_modules/angular-cli and then run npm install, not sure why this is ... but it's the default behavior right now, the only documented fixes are in other GitHub issues.

Could you tell me where I can find this, is it in /usr/bin ?
2016-07-03 22:59 GMT+02:00 Joe<EMAIL_ADDRESS>
You have to go into the /node_modules/angular-cli and then run npm install,
not sure why this is ... but it's the default behavior right now, the only
documented fixes are in other GitHub issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1274#issuecomment-230175038,
or mute the thread
https://github.com/notifications/unsubscribe/AKTOFNUNRfoUuhqwEX8I1T3MyOZYKXYxks5qSCKxgaJpZM4JD5MC
.

Nop, sorry but still nothing
ng new ang_project
/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:54
throw err;
^
Error: EACCES: permission denied, open
'/Users/redsun/.config/configstore/ember-cli.json'
You don't have access to this file.
at Error (native)
at Object.fs.openSync (fs.js:549:18)
at Object.fs.readFileSync (fs.js:397:15)
at Object.create.all.get

(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:35:26)
at Object.Configstore
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:28:44)
at clientId
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/lib/cli/index.js:22:21)
at module.exports
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/lib/cli/index.js:65:19)
at module.exports
(/usr/local/lib/node_modules/angular-cli/lib/cli/index.js:106:10)
at /usr/local/lib/node_modules/angular-cli/bin/ng:31:5
at
/usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:46:14
➜  ~ npm -v
2.15.8
2016-07-03 23:06 GMT+02:00 Djamal Dag<EMAIL_ADDRESS>
Could you tell me where I can find this, is it in /usr/bin ?
2016-07-03 22:59 GMT+02:00 Joe<EMAIL_ADDRESS>
You have to go into the /node_modules/angular-cli and then run npm
install, not sure why this is ... but it's the default behavior right
now, the only documented fixes are in other GitHub issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1274#issuecomment-230175038,
or mute the thread
https://github.com/notifications/unsubscribe/AKTOFNUNRfoUuhqwEX8I1T3MyOZYKXYxks5qSCKxgaJpZM4JD5MC
.

Ok, I just understood the problem, Now It creates the necessary files but
when I do ng serve this Shows up :
ng serve
module.js:327
throw err;
^
Error: Cannot find module 'exists-sync'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.
(/Users/redsun/pro/node_modules/angular-cli/node_modules/ember-cli/lib/models/project.js:11:26)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
2016-07-03 23:09 GMT+02:00 Djamal Dag<EMAIL_ADDRESS>
Nop, sorry but still nothing
ng new ang_project
/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:54
throw err;
^
Error: EACCES: permission denied, open
'/Users/redsun/.config/configstore/ember-cli.json'
You don't have access to this file.
at Error (native)
at Object.fs.openSync (fs.js:549:18)
at Object.fs.readFileSync (fs.js:397:15)
at Object.create.all.get

(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:35:26)
at Object.Configstore
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/node_modules/configstore/index.js:28:44)
at clientId
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/lib/cli/index.js:22:21)
at module.exports
(/usr/local/lib/node_modules/angular-cli/node_modules/ember-cli/lib/cli/index.js:65:19)
at module.exports
(/usr/local/lib/node_modules/angular-cli/lib/cli/index.js:106:10)
at /usr/local/lib/node_modules/angular-cli/bin/ng:31:5
at
/usr/local/lib/node_modules/angular-cli/node_modules/resolve/lib/async.js:46:14
➜  ~ npm -v
2.15.8
2016-07-03 23:06 GMT+02:00 Djamal Dag<EMAIL_ADDRESS>
Could you tell me where I can find this, is it in /usr/bin ?
2016-07-03 22:59 GMT+02:00 Joe<EMAIL_ADDRESS>
You have to go into the /node_modules/angular-cli and then run npm
install, not sure why this is ... but it's the default behavior right
now, the only documented fixes are in other GitHub issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/1274#issuecomment-230175038,
or mute the thread
https://github.com/notifications/unsubscribe/AKTOFNUNRfoUuhqwEX8I1T3MyOZYKXYxks5qSCKxgaJpZM4JD5MC
.

Duplicate of https://github.com/angular/angular-cli/issues/1186, solved in https://github.com/angular/angular-cli/pull/1250. Will be in the next release.


32 bit constant issues

It seems sometimes 32 bit constant pairs are packed into 64 bit constants. This is a big problem for jit, since it cannot track constants properly. Is there a way to detect such const64 byte codes? I suspect that is not possible, that a constant is used as both 64 bit and a pair of 32 bit, so at parsing time we could replace them with two 32 bit constants in the latter case. A flag or a byte code type would be enough.

Can you give a example code?

It is not bug. this is intended operation for copy arguments without reference function arguments type
(f64.const 64)  (f32.const 32)
(copy4B, copy4B) (copy4B)
each copy count of type is computed by function valueFunctionCopyCount
but It could be confusing. may I add a function for original position?

I suspect this is something new. Are these true:

affect calls / callIndirects only
all data type are split into pointer sized fragments, so a 128 bit value is 4 moves on 32 bit, and 2 moves on 64 bit?
32 bit moves are 64 bit moves on 64 bit?

If this is true, I can create an algorithm to detect which "arguments" needs to be ignored by jit.

Yes, three things are true.

It looks like End opcode is also affected.


Use file upload start time to calculate token validity

Hi CAPI team! I believe the higher-level idea for this was recently discussed with my team (the SAP Control Plane team) at your office hours. Please let me know what you think of this implementation. Apologies if there's anything particularly daft in here - I'm an ops person new to application development. In addition to the new unit tests I've run this manually and observed that a package upload started shortly before a token expires will authenticate successfully when the upload finishes after the token has expired (previously this produced an error).
UPDATE: I've updated this so that the upload start time is also used when calculating token expiry for buildpack and droplet uploads, in addition to packages.

A short explanation of the proposed change:

Uses the upload start time instead of the current time when calculating authorization token validity for POST requests to /v3/packages/:guid/upload, /v3/droplets/:guid/upload and /v3/buildpacks/:guid/upload:
{"timestamp":"2021-08-02T16:47:00.219459711Z","message":"Using alternate reference time of 2021-08-02 16:44:30 +0000
 to calculate token expiry instead of current time","log_level":"info","source":"cc.uaa_token_decoder","data":{"requ
est_guid":"12a2481b-e0ca-4774-7803-7e1ef0ca9d0e::3396cc39-04c5-4498-9ef2-7befc6824c2e"},"thread_id":104100,"fiber_id
":104120,"process_id":6,"file":"/var/vcap/data/packages/cloud_controller_ng/39b0abd119926dfc9c8b684272bb69a02365530c
/cloud_controller_ng/lib/cloud_controller/uaa/uaa_token_decoder.rb","lineno":80,"method":"decode_token_with_key"}

An explanation of the use cases your change solves

Currently users whose token is still valid at the time a file upload starts, but whose token expires before that upload finishes, are presented with a CF-InvalidAuthToken error. Although the option to set a grace period already exists, this is only useful to users who are able to easily change platform-wide configuration, and who can accurately predict the time their uploads will need. I believe it is uncommon for users to be in this position.

Links to any other associated PRs

https://github.com/cloudfoundry/capi-release/pull/201

[x] I have reviewed the contributing guide

[x] I have viewed, signed, and submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests using bundle exec rake

[ ] I have run CF Acceptance Tests

Hey @will-gant, do you have a reliable way to repro this? I'm working on validating the change.
I tried uploading a large (~1GB) app via the /v3/packages/:guid/upload endpoint right before the token expired, but didn't have much success (also bothersome because of having to wait for the token to get close to expiring)

Spoke with @stephanme and @tjvman who both gave the thumbs up, given that folks at SAP were able to validate this I am going to merge.
Thanks @will-gant !


Drag'n'dropping channels wrongly positions the channel in flight

Easier to explain with a GIF:

Note that:

This happens on channels only, not networks.
Reproducing this requires some playing on the drag'n'dropping, it looks good at first, then for no reason it breaks, and then it's consistently broken until next refresh.
This happens both on master and 2.0.0-pre.4, not sure about previous pre-releases and stable releases (if someone wants to try with other versions, that'd be helpful).

Its dependent from where you start dragging element. Problem is only if you drag from upper side on the area. Might be fixed with updating jquery.

It seems if you grab bottom side of the grabbing area, there are no problems, but if top side of the area, bug happens.

I belive #702 fixed this completely? Is so, this issue should be closed.


Generating address for steem

I can generate the private key using PrivateKeyFactory::fromHex($hashSha256)->toWif(); for steem blockchan but when i try to generate the public address using $privateKey->getPublicKey()->getAddress()->getAddress() I only bitcoin address and cant generate a steem address with the address prefix STM

You haven't passed in the details for the Steem network yet, and the library uses bitcoin by default.
You'll need to implement a NetworkInterface for Steem. This is pretty easy, look in NetworkFactory for the parts that are required, then check out steems chainparams.cpp to get the correct values (or look in other implementations for the details)
Then, you have two options:
\BitWasp\Bitcoin\Bitcoin::setNetwork($yourNetwork) changes the default, so now your steem network would be used globally.
If you don't like globally configuring the network, pass $yourNetwork as an argument to toWif and getAddress to override the default.


Why is listening only ipv6 port? Ipv4 support?

composer req spiral/roadrunner symfony/psr-http-message-bridge
wget https://github.com/spiral/roadrunner/releases/download/v1.3.5/roadrunner-1.3.5-linux-amd64.tar.gz
tar xvzf roadrunner-1.3.5-linux-amd64.tar.gz
Copy .rr.yml and worker.php from https://github.com/spiral/roadrunner/wiki/Symfony-Framework
http:
  address: <IP_ADDRESS>:8080
  maxRequest: 10
  workers:
    command: "php /var/www/app/current/worker.php"
  pool:
    numWorkers: 4

./roadrunner-1.3.5-linux-amd64/rr serve -v -d

DEBU[0000] [static]: disabled
DEBU[0000] [rpc]: started
DEBU[0000] [http]: started

netstat -tulpn | grep 8080

tcp6       0      0 :::8080                 :::*                    LISTEN      -

If run as root:
netstat -tulpn | grep roadr

tcp        0      0 <IP_ADDRESS>:6001          <IP_ADDRESS>:*               LISTEN      1291/./roadrunner-1
tcp6       0      0 :::8080                 :::*                    LISTEN      1291/./roadrunner-1

uname -a
Linux php 4.9.125-linuxkit #1 SMP Fri Sep 7 08:20:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
wget http://localhost:8080/
--2019-02-25 13:09:32--  http://localhost:8080/
Resolving localhost (localhost)... <IP_ADDRESS>, ::1
Connecting to localhost (localhost)|<IP_ADDRESS>|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 58 [application/json]
Saving to: ‘index.html’

100%[==============================================================================>] 58          --.-K/s   in 0s

2019-02-25 13:09:33 (10.6 MB/s) - ‘index.html’ saved [58/58]

In log:

INFO[0090] <IP_ADDRESS> {843ms} 200 GET http://localhost:8080/

Did you try to run wget http://<IP_ADDRESS>:8080/ ?

It must listen to both ipv4 and ipv6. I can clearly observe server respond by both ipv6 and ipv4 on my local test rig.
FYI,
maxRequest: 10

it is about maximum request body size, in next release, we will rename this option to avoid confusion.

Oh, false alarm, sorry. Indeed, the tcp6 line in netstat includes both ipv4 and ipv6.
But at first glance misleading.

I ended up here, looking for ipv6 support.
The discussion here is no longer relevant since roadrunner 2 which at the moment only supports ipv4.


Build once, run multiple tests

Is it possible to call test_cdylib::build_current_project() once per test file and let all the test functions inside that test file use that build?

You could use once_cell to store the result, e.g.
use once_cell::sync::Lazy;
static LIB_PATH: Lazy<PathBuf> = Lazy::new(|| test_cdylib::build_current_project());

Thanks, that works fine for me. Maybe you could extend your example with it. The usual test case is to have one test suite with many tests inside.


Problems with styles / less on a basic donejs project

How often can you reproduce it?

[x] Always
[ ] Sometimes
[ ] Rarely
[ ] Unable
[ ] I didn’t try

Description:
Creating a basic donejs app will result in a strange behaviour while running it on develop mode (donejs develop).
IMPORTANT NOTE: I managed to make it work by commenting in index.stache this line: <can-import from="~/styles.less" />.
Also if I add a component, say myComponent.component then it will also fail.

Steps to reproduce:

npm install -g<EMAIL_ADDRESS>donejs add app
donejs develop
open http://localhost:8080

Expected results:
Show "Hello World!"

Actual results:
Shows "Hello World!" for a few seconds then there is a blank screen.

Environment:

Software
Version

donejs -V
2.1.0

node -v
v8.11.1

npm -v
6.4.0

Browser
Version 69.0.3497.100 (Official Build) (64-bit)

Operating system
OSX Mojave

Thanks, will check this out soon...

Screen Recording 2018-09-29 at 2.35.46 PM.mov.zip
This is how the issue looks like

if you take a look at the video, it will fail not when styles.less loads but when /node_modules/can-component/package.json loads

I see that too now. Really strange. Investigating....

Something is injecting

Trying to figure out where that is coming from...

Should be fixed by steal-less 1.3.3. I'm confirming now...

Looks good with a new app now. Thanks for reporting!

Working fine now, thanks @matthewp


No create

In the web interface, I entered python in the textbox, unable to create, what caused this?

Are you trying to run the site locally?


⚠ TROJAN 🇮🇩 Indonesia IDJ 1 has degraded performance

In 1e7dd71, TROJAN 🇮🇩 Indonesia IDJ 1 (https://idt-1.opensvr.net/) experienced degraded performance:

HTTP code: 200
Response time: 20492 ms

Resolved: TROJAN 🇮🇩 Indonesia IDJ 1 performance has improved in 1dd9ccc.


Issue with Windows Subsystem for Linux (WSL)

Hi, during my app development I have faced with issue.
Error:
tyaonami@local:~/forum$ go run .
# forum
/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/pkg/tool/linux_amd64/link: running gcc-5 failed: exit status 1
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000010.o: in function `pthreadMutexTry':
/home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:27514: undefined reference to `pthread_mutex_trylock'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000010.o: in function `sqlite3ThreadCreate':
/home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:31287: undefined reference to `pthread_create'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000010.o: in function `pthreadMutexAlloc':
/home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:27369: undefined reference to `pthread_mutexattr_init'
/home/linuxbrew/.linuxbrew/bin/ld: /home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:27370: undefined reference to `pthread_mutexattr_settype'
/home/linuxbrew/.linuxbrew/bin/ld: /home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:27372: undefined reference to `pthread_mutexattr_destroy'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000010.o: in function `sqlite3ThreadJoin':
/home/tyaonami/go/pkg/mod/github.com/mattn/go-sqlite3@v1.14.10/sqlite3-binding.c:31307: undefined reference to `pthread_join'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000016.o: in function `_cgo_try_pthread_create':
/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_libinit.c:100: undefined reference to `pthread_create'
/home/linuxbrew/.linuxbrew/bin/ld: /home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_libinit.c:102: undefined reference to `pthread_detach'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000017.o: in function `x_cgo_init':
/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_linux_amd64.c:46: undefined reference to `pthread_attr_getstacksize'
/home/linuxbrew/.linuxbrew/bin/ld: /tmp/go-link-456674004/000017.o: in function `_cgo_sys_thread_start':
/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_linux_amd64.c:67: undefined reference to `pthread_sigmask'
/home/linuxbrew/.linuxbrew/bin/ld: /home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_linux_amd64.c:70: undefined reference to `pthread_attr_getstacksize'
/home/linuxbrew/.linuxbrew/bin/ld: /home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/src/runtime/cgo/gcc_linux_amd64.c:75: undefined reference to `pthread_sigmask'
collect2: error: ld returned 1 exit status

My code:
package main

import (
	"fmt"

	_ "github.com/mattn/go-sqlite3"
)

func main() {

	fmt.Println("Hello")
}

Go environment:
tyaonami@local:~/forum$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/tyaonami/.cache/go-build"
GOENV="/home/tyaonami/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/tyaonami/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/tyaonami/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/linuxbrew/.linuxbrew/Cellar/go/1.16.5/libexec/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.16.5"
GCCGO="gccgo"
AR="ar"
CC="gcc-5"
CXX="g++-5"
CGO_ENABLED="1"
GOMOD="/home/tyaonami/forum/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3584474454=/tmp/go-build -gno-record-gcc-switches"

gcc version
tyaonami@local:~/forum$ gcc-5 --version
gcc-5 (Homebrew GCC 5.5.0_7) 5.5.0
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

tyaonami@local:~/forum$ gcc --version
gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Can you test with go run -ldflags="-extldflags='-lpthread'" .?


keep an eye on macro_reexport rfc

https://github.com/rust-lang/rust/issues/29638
this enables the removal of the need to have users export cpython macros

This is now fixed with re exports


Problem: tmdata tracked files change in dev env

Solution: Only track config.toml and generate the other files such as
genesis.json and priv_validator.json in the container via tendermint init
Related issue: #1997

Codecov Report

Merging #2042 into tendermint will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           tendermint    #2042   +/-   ##
===========================================
  Coverage       52.41%   52.41%
===========================================
  Files              71       71
  Lines            3566     3566
===========================================
  Hits             1869     1869
  Misses           1697     1697


[Relay] Flexible shape dispatch transformation

This PR adds a new pass to relay.transform that creates a dispatcher around an input module to handle multiple input shapes. For example consider a case where I'd like to optimize my model to handle both batch_size=1 and batch_size=4. I can now do so elegantly as follows:
shape_dict = {'data': [1, 3, 224, 224]}
model_bs1 = tvmc.load('my_model.onnx', shape_dict=shape_dict)
tvmc.tune(model, log_file='batch_1.logs')

shape_dict = {'data': [4, 3, 224, 224]}
model_bs4 = tvmc.load('my_model.onnx', shape_dict=shape_dict)
tvmc.tune(model, log_file='batch_4.logs')

# Create dispatcher for multiple batch sizes.
flex_mod = relay.transform.FlexibleShapeDispatch(buckets=[1, 4])(model_bs1.mod)

with ApplyHistoryBest(['batch_1.logs', 'batch_4.logs']):
    exe = relay.vm.compile(flex_mod, "llvm")

# Now we can run inputs with either batch 1 or batch 4 and get the tuned performance!
batch_1 = np.random.rand(1, 3, 224, 224).astype("float32")
vm.benchmark(tvm.cpu(), batch_2, func_name="main")

batch_4 = np.random.rand(4, 3, 224, 224).astype("float32")
vm.benchmark(tvm.cpu(), batch_4, func_name="main")

As seen above FlexibleShapeDispatch is a simple halfway point between fully static and fully dynamic graphs that allows us to leverage TVM tuning. If an input shape is not provided in buckets, it will either run fully dynamically using relay.Any, or if the auto_pad argument is set for FlexibleShapeDispatch, padding will be applied to match the closest bucket.
There are a few special cases that this pass handles. Multiple dynamic inputs (like those you might see in BERT) can be handled by setting input_indices to indicate which inputs have a dynamic axis. affects_output can be set to False for cases where the output shape is not dependent on input dynamism which could occur in dynamic resolution cases or something.
To make applying tuning logs more convenient, I also added the ability to load and merge multiple files to both autotvm and autoscheduler.
Thanks @jroesch for providing the backbone of this implementation.

cc @mbs-octoml

@jroesch I think the documentation should now be substantially improved based on your input. Let me know what you think.

All feedback has been addressed and tests are green. @jroesch do you want to give this one more pass?


Release v2 milestone.

Gathering fixes that will require non-backward compatible API  changes and labelling them as 'v2' milestones. Comment here if you urgently need some of these changes published, otherwise I will continue to gather requirements for a while to try and batch together a decent sized API bump for v2.

All v2 issues have been closed, so time to put out a new release.


close listening socket in #stop not to accept new connections anymore

This change is revival of #861, to close listening connections in #stop, not to accept connections to tell clients that this node denies incoming data now.
When shared: true, SocketManager in ServerEngine accepts connections. So plugin side cannot control it (this change doesn't affect to SM's behavior).
But it's correct, because other workers may be able to handle connections newly coming.

@repeatedly can you review this?

@repeatedly ping?

With shared: false, how handle tcp connections in multi processing mode?

Ah, wait. Multi processing patch changes its value to true.

One comment. Others are good for me.


Image not being created with latest data

Issue
Both fetch.py and create_image.py run withtout issues.
However a csv inspection shows that the image that is created is not using the most recent earthquake data.
Solution
Check both scripts to make sure that the image is generated using the latest data

This was solved directly on main

Commit 7fd9f96cd98d74998d5c6177367bc6a8c89c9fd6

Issue is closed. Thank you @miguelantoniosantos @pedrolucas7i and @MicaelMCarvalho for the support

FYI, issue is still open @JorgeMiguelGomes  :)

Thanks!
On Fri, 12 Jul 2024, 23:27 Micael Carvalho, @.***>
wrote:

FYI, issue is still open @JorgeMiguelGomes
https://github.com/JorgeMiguelGomes :)
—
Reply to this email directly, view it on GitHub
https://github.com/vostpt/aterratreme_auto/issues/1#issuecomment-2226439128,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIGDRCIWGT6HMLWSFO2ISO3ZMBJ5XAVCNFSM6AAAAABKXQKN6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRWGQZTSMJSHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Confidencialidade: Esta mensagem (e eventuais ficheiros anexos) é destinada
exclusivamente às pessoas nela indicadas e tem natureza confidencial. Se
receber esta mensagem por engano, por favor contacte o remetente e elimine
a mensagem e ficheiros, sem tomar conhecimento do respectivo conteúdo e sem
reproduzi-la ou divulgá-la. Confidentiality Warning: This e-mail message
(and any attached files) is confidential and is intended solely for the use
of the individual or entity to whom it is addressed. lf you are not the
intended recipient of this message please notify the sender and delete and
destroy all copies immediately.


add pfm

closes https://github.com/Stride-Labs/stride/pull/800
Summary
Add PFM
Integration guide: https://github.com/cosmos/ibc-apps/blob/main/middleware/packet-forward-middleware/docs/integration.md
Test plan

hey @asalzmann,
Stride's UX would really profit a lot from having PFM enabled.
We at Secret network would like to bridge in a lot of stride assets directly from osmosis and PFM would ease the UX quite a lot! :)

@sampocs are you signed off on this PR?
Is the main outstanding task to review interaction between autopilot / PFM?

I’m signed off on all the comments, but remaining tasks are:

think about the interaction between autopilot snd pfm
test it in dockernet if you havent already
fix whatever the build error is that’s causing CI to fail

[ ] think about the interaction between autopilot snd pfm
[ ] test it in dockernet if you havent already
[ ] fix whatever the build error is that’s causing CI to fail


Static page translations + footer_links

This PR adds static page translations (including the ability to have a separate layout/locale) and adds back in the footer links option.

Thanks for your contribution.
I've created branch with your changes, rebased it to master(we had some changes) and fixed dependencies and spec for it in #234.
It's already merged into master. I really appreciate your help!

Thanks @bbonislawski!


ci: Measure code coverage via grcov (and not tarpaulin).

Closing, because this has been the case for a while already.


i have uploaded Heap code in c folder

Great work please give this repo a star and follow me for follow back 😊


Add instances_retrievable/bindings_retrievable catalog fields added in v2.14

https://github.com/openservicebrokerapi/servicebroker/blob/v2.14/spec.md\#fetching-a-service-binding
https://github.com/openservicebrokerapi/servicebroker/blob/v2.14/spec.md\#fetching-a-service-instance

The catalog unit tests are failing. They should either expect the new fields, or the new fields should be tagged 'omitempty'.

$ ginkgo -r

...
Summarizing 3 Failures:

[Fail] Service Broker API catalog endpoint [It] returns valid catalog json
/Users/pivotal/workspace/on-demand-service-broker-release/src/github.com/pivotal-cf/brokerapi/api_test.go:278

[Fail] Catalog Service JSON encoding [It] uses the correct keys
/Users/pivotal/workspace/on-demand-service-broker-release/src/github.com/pivotal-cf/brokerapi/catalog_test.go:64

[Fail] Catalog Service [It] encodes the optional 'requires' fields
/Users/pivotal/workspace/on-demand-service-broker-release/src/github.com/pivotal-cf/brokerapi/catalog_test.go:107

Ran 219 of 219 Specs in 0.166 seconds
FAIL! -- 216 Passed | 3 Failed | 0 Pending | 0 Skipped --- FAIL: TestAPI (0.17s)
FAIL

Ginkgo ran 1 suite in 3.143985371s
Test Suite Failed

I'm sorry about. I'm surprised at myself that I submitted the PR with tests failing.

I've rebased, added omitempty, and tests pass.

Excellent. Thank you.


Menu bar is gone

Hi there, after I run this script I got the new user "[benutzer]" and the most annoying thing:  my dock (Anwedungsleiste) is gone. If I connect via VNC I got no graphical possibility to interact with the system.
RaspberryPiOs bullseye, Raspberry Pi 3+

Did you follow the instructions and use only the "Lite" version (without graphical interface) for your device?
This script is meant to convert a freshly installed (!) Raspberry Pi device with Raspberry Pi OS Lite (!) into an audio receiver. It is not meant to modify an existing system with graphical UI and so on.

Okay. Got it. I used it on a system with running Pi-hole, ejabberd Server etc. Everything is working fine by the way.


Support ConvertOaDate parameter in ExcelOpenXmlReader

I have two files with date and time formated cells, both files have the same values.
If  file is binary (XLS) exceldatareader takes values as double, case openxml (XLSX) reader takes values as datetime.
As a result I have for example, 42148 (case XLS), or 5/24/2015  12:00:00 AM (case XLSX) output.
Similar issue reading time formated cells, different output.
Is it possible to get the correct output (datetime) from different type excel files?

Setting ConvertOaDate to true should give the behavior that you're looking for.
Note that AsDataSet() and AsDataSet(bool convertOADateTime) overwrite ConvertOaDate (AsDataSet() just calls AsDataSet(false) internally), so even when you set ConvertOaDate to true, calling AsDataSet() instead of AsDataSet(true) will revert it to false.

The bug is you didn't get doubles from both =) @pwitvoet is likely correct, setting ConvertOaDate to true should do it. Suggest to keep open until either ConvertOaDate is no longer needed or the behavior is consistent across the formats.


Add content_reference event

Adds the content_reference web hook event along with the content reference type.
github/apps.go seemed the best place for ContentReference to live but if there is a better place let me know.
GitHub API docs: https://developer.github.com/webhooks/event-payloads/#content_reference

@googlebot I signed it!

I don't really see any existing tests for this code path. Does that sound right?

Found the ParseWebHook tests, added!

@gmlewis great thanks! Found another issue implementing this content reference flow which is fixed in #1602


Remove tautology

"trivial" and "easy" mean the same thing in this context, so it might as well just be simplified to "easy" to make it easier for everyone to understand.

Thanks for the review @posva. I'm not planning on doing any major docs refactor, just took a few seconds to remove this extra word. I don't think it's worth conflating "reword the section" with "fix minor grammatical error".
Feel free to close the PR otherwise :)

Ok, thanks!


Create Business Configuration for Factory Calendar

Tutorials: https://developers.sap.com/tutorials/abap-environment-service-binding.html
Step 4: Enable log changes
The screenshot shows the changelog to be set for ZCAL_HOLITXT_XXX. The instructions tell you that the settings needs to be done for ZCAL_HOLIDAY_XXX. What is correct?

Hi @gregorwolf ,
the text and screenshot are missleading, we'll update it as soon as possible. You can select database table ZCAL_HOLITXT_XXX as databasetable and technical table setting to enable the log changes.

Best regards,
Merve

Hi @MichaelCzcz,
I created following PR: #7809. Can you merge?
Thank you.
Best regards,
Merve


As of may 8th, 2017, authentication with yahoo does not work. I have fixed it.

Hello. Authentication with yahoo has stopped working. I have fixed it, let me know how can I send you the code to review.
Greetings.

Sorry, forgot NDA

@jpmaciasg. The yahoo authentication fix that you did earlier, Can you help me? the script does not authenticate yahoo email ids anymore.

I will have some time this week to update the script and fix the problems.


Nested functions not working

Alice describes something like:
'<strtolower(<(implode(" ", ["HELLO", "WORLD", \<foo()>]))>)> \<bar()>'

But hautelook:fixtures:load says:

The value "<(implode(" "" contains an unclosed function.

This occurs in a yml like this:
Foo\BarEntity:
  message_{1..29}:
    title: <text(50)>
    level: '<strtolower(<(implode(" ", ["HELLO", "WORLD", \<foo()>]))>)> \<bar()>'
  message_{30..100}:
    title: <text(50)>
    level: '<strtolower(<(implode(" ", ["HELLO", "WORLD", \<foo()>]))>)> \<bar()>'

Example taken from https://github.com/nelmio/alice/blob/master/doc/advanced-guide.md#functions
Also for simpler things like '<pow(0,<numberBetween(0,2)>)>' .

Duplicate of https://github.com/nelmio/alice/issues/663.
Sorry for the inconvenience, the quick fix is to patch the Lexer in alice... the proper fix is to take care of https://github.com/nelmio/alice/issues/601.