limitTo filter should have a left and right bound.

using like this:
{{'abcdefg' | limitTo:2:5}}
output:
cde
useful when paging sth..

+1 for new slice filter, but here coms few questions.
Should it follow:
a)  javascript array slice arr.slice([begin[, end]])
b) php array_slice(int $offset [, int $length = NULL]) and  string substr ( int $start [, int $length])
c) python has great slice(start, stop, [,step])  https://docs.python.org/2/library/functions.html#slice

So, we should land some form of this simple but very often used filter. Reading through various issues / PRs opened for this topic I think that we've got few simple decisions to take:

[ ] - should we extend the existing limitTo filter or introduce a new one?
[ ] - if we introduce a new filter what should be it's name and API?
[ ] - if we introduce a new filter should we depreciate / remove the limitTo one?

My take would be to introduce a new slice filter with the API matching the JavaScript one as it:

does the job and is familiar to JS developers
works for both arrays and strings

Does anyone objects to the above plan? How do people feel about depreciating / removing the limitTo filter? I'm going to raise this during the team meeting tomorrow so it would be great to have feedback from the community.

@pkozlowski-opensource Introduction of a new slice filter and leaving limitTo alone seems right to me

@jlmagee the slight problem with leaving both limitTo and slice is that the impl of the 2 would be almost identical so we would be duplicating bytes for nothing. But maybe we can make one filter calling the other, to be seen.

Would love a new slice filter matching the JS API. I don't really like the idea of having redundant filters, so limitTo should ideally be deprectated. But there is so many examples out there using it that it might be best to leave it as it is, just maybe flag it as an alias in the docs.

Thnx for the input @mgcrea. Yup, there might be slight perf impact (one more function call), but not sure if it would matter in practice. The other idea of making it easier on people:

depreciate limitTo in 1.4 and only remove in 1.5
remove in 1.4 and publish a compatibility module

:+1: for

remove in 1.4 and publish a compatibility module

removing limitTo is terrible idea! it's breaking change just because somebody likes how new word (slice) sounds - I can't believe you can be so irresponsible! Thousands of projects will be forced to spend thousands of man-hours just because mmm... you know... slice sounds more suitable for this case. You already can do filter with limit and offset and just for syntax sugar you want to add breaking change? I can't understand your motivation and not sure you understand consequences.

@jamm the current limitTo filter doesn't do what slice does. So it is not about finding a different name for the same thing. And hey, naming things is important
BTW: it would be really great if we could focus on the technical merits pros & cons and tune down the language a bit - calling people irresponsible in the very moment  when we are reaching out to the community for feedback sounds odd...

@pkozlowski-opensource so add argument and it will. If you want to add breaking change just because of naming - it's irresponsible. If you want to hear only positive feedback, without criticism - it's naive expectation. I'd glad to be less mean, but if we all will keep silence just to be "polite", breaking changes like this will ruin trust to Angular API at all.

@jamm not sure why are saying that this change is only about a name... The crux of the "problem" is that:

limitTo filter only accepts one argument (limit)
proposed slice should accept 2 arguments (start and end index, as in JS)

So the 2 are functionally related but not the same. Could you please elaborate what you mean by:

You already can do filter with limit and offset and just for syntax

Are you referring to collection | limitTo:start | limitTo:-offset or something else?

@pkozlowski-opensource but if you will add second argument to limitTo filter, it will not break anything and will work. It's even proposed by author of this thread :)

Are you referring to collection | limitTo:start | limitTo:-offset

yes, but it's not so important. I agree limitTo:2:3 looks shorter and more handy, I only arguing about breaking change, nothing more.

@jamm ok, cool, I think I got all your answers to my previous questions. Thnx for the feedback!

So basically, if I use limitTo:2:3, then it behvaes like a normal slice filter? Sounds good to me. We could also alias slice to limitTo, althought that has no precedent.

Guys, we are leaning towards merging https://github.com/angular/angular.js/pull/10899 - if anyone is interested in this feature it is time to speak up now

Woooohaaa! One of the most voted (and easiest to fix!) issues just got solved :-)

:+1:

nice! it was my first contribution:)

nice

:+1:


Start using PGP keys to verify commits are coming from you:

^^
Instructions:
https://help.github.com/articles/signing-commits-using-gpg/
https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work
When done: Add your PUBLIC key to https://github.com/zencashofficial/keys via a pull request, make sure the commit is signed ^^
The reason being is that pgp signed commits verify that you indeed wrote the code otherwise this would happen https://github.com/jayphelps/git-blame-someone-else/commit/e5cfe4bb2190a2ae406d5f0b8f49c32ac0f01cd7

Thank you, we will do that asap :)

I have set my PGP key verification.
I am waiting for @neduchal and @jiri-novotny - after that, we can close this.

Awesome :+1:
On Sep 28, 2017 9:03 AM, "Lukáš Bureš"<EMAIL_ADDRESS>wrote:

I have set my PGP key verification.
I am waiting for @neduchal https://github.com/neduchal and @jiri-novotny
https://github.com/jiri-novotny - after that, we can close this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ZencashOfficial/arizen/issues/53#issuecomment-332829664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJmmkYKE7Yrc5iGl-7y9Llg5SMcAlzeIks5sm5kzgaJpZM4Pme-l
.

Now we are waiting for @neduchal  ... go go Petr 🥇

@neduchal has started to use PGP key - so we are waiting for he update  https://github.com/zencashofficial/keys and we are done 👍

All PGPs keys were added ...


Forgot to sign script

Title says it all really. Forgot to sign the script with my key.

Resolved in 1.1


Include integration test binaries in test mode

Fixed

Add top-level tests directory to localPatterns in overlay/mkcrate.nix.

As described in #40, cargo2nix currently does not output integration tests by default when building the crate in test mode. This is because localPatterns does not include the top-level tests directory in the default path regex. This directory is standard for any Cargo project, and the current behavior of not including integration tests when compileMode = "test" is quite surprising, especially for a new user. I believe it should be fine to include this directory by default, if it exists.
Fixes #40.

Please advise whether this change warrants a new release.

I believe we should release 0.6.0 after this PR gets merged since both the default package overrides and alternate registry support features are not included in 0.5.0.

No worries, @trha! Changelogs are nice to have in any project, especially in open source projects. I feel they serve a crucial part of the semver stability contract between developer and user, describing succinctly what changes went into the version bump before they upgrade. I happen to be partial to the Keep a Changelog standard, so I tried to base them on that.
Though, before I merge this PR, I've just realized that I have a minor grammatical mistake in my commit message. Might need to ask you to reapprove in a minute or two, haha.

@trha Okay, just fixed the commit message. Would you mind reapproving the PR, please?


can't upload file

Hi,
Trying to upload a file to a shared private folder. It lets me select from my computer, then even flashes "Encrypting and Uploading" at the bottom in the blue bar. Never appears. I've tried multiple files, even in other places in the folder structure, no luck. I rebooted the computer, then uninstalled/reinstalled keybase as well. Help?
NTC

I'm seeing a similar issue. In the Keybase app for macOS, I get this:

Error: ERROR CODE 218 - Error checking merkle tree: can't operate on old merkle sequence number in method keybase.1.SimpleFS.simpleFSWait

And if I try via the CLI, I get this:

$ keybase fs cp index.html /keybase/public/a2
▶ ERROR Error checking merkle tree: can't operate on old merkle sequence number

@a2 we're looking at your case already today.
@ntcastro please do a keybase log send and post the log ID here.

Apologies, I don't know how to do that. It says to open a terminal window
for that, but can you just hold my hand on how to do that? Thanks!
On Thu, Jul 26, 2018 at 10:03 AM Jeremy Stribling<EMAIL_ADDRESS>wrote:

@a2 https://github.com/a2 we're looking at your case already today.
@ntcastro https://github.com/ntcastro please do a keybase log send and
post the log ID here.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/12987#issuecomment-408108484,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Anx4OlNJYFLMrp53MiL8Ih16Zm3RIPClks5uKcxLgaJpZM4VhCHv
.

@ntcastro what operating system is your computer running?

Windows 10 Home. I thought I was looking for a terminal window within
keybase, that was silly.
Log ID is: 0c4314c703b649a304109c1c
Thanks!
Nicole
On Thu, Jul 26, 2018 at 3:50 PM Jeremy Stribling<EMAIL_ADDRESS>wrote:

@ntcastro https://github.com/ntcastro what operating system is your
computer running?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/keybase/client/issues/12987#issuecomment-408214790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Anx4OqYBuvH-SpH2smtvPQeFNCXWlws-ks5uKh1ygaJpZM4VhCHv
.

I followed up with @ntcastro privately, and the issue is that uploading files through the GUI in Windows doesn't work right now.  We're working on fixing that bug, but for now, accessing the files through Windows explorer worked around the problem.

@strib Thanks so much. Let me know if I can provide more information about my set-up/situation here. Happy to help in any way I can.

@a2 yes sorry, still on the todo list.  Will get to it soon.  (Though you're running a slightly old version, it's still not fixed in the newest version.)

@strib Thanks for the update in either case :)

@a2 thanks for the reminder about this.  Our next release isn't scheduled for a while, but I made a special build for you including a possible fix, if you're interested in trying it.  You can download it here: https://s3.amazonaws.com/prerelease.keybase.io/darwin-test/Keybase-2.6.0-20180808172014%2B2caa6bc657.dmg
(It's the same as our current release, but with the KBFS commits linked above.)
Let me know if it improves things for you!

@strib It works now!! Thank you so much for your help.

Great!


Failed to load project that references LanguageExt.CodeGen from solution folder in WSL

Environment data:
WSL distro: Arch
VS Code version: 1.38.0
C# Extension version: 1.21.1
dotnet --info output in Windows:
.NET Core SDK (reflecting any global.json):
 Version:   2.2.401
 Commit:    729b316c13

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.18362
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.2.401\

Host (useful for support):
  Version: 2.2.6
  Commit:  7dac9b1b51

.NET Core SDKs installed:
  2.1.801 [C:\Program Files\dotnet\sdk]
  2.2.401 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

dotnet --info output in WSL:
.NET Core SDK (reflecting any global.json):
 Version:   2.2.401
 Commit:    729b316c13

Runtime Environment:
 OS Name:     arch
 OS Version:
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/wawa/.dotnet/sdk/2.2.401/

Host (useful for support):
  Version: 2.2.6
  Commit:  7dac9b1b51

.NET Core SDKs installed:
  2.1.701 [/home/wawa/.dotnet/sdk]
  2.2.301 [/home/wawa/.dotnet/sdk]
  2.2.401 [/home/wawa/.dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.12 [/home/wawa/.dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.6 [/home/wawa/.dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.12 [/home/wawa/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.6 [/home/wawa/.dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.12 [/home/wawa/.dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.6 [/home/wawa/.dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Steps to reproduce

git clone https://github.com/wawaforya/loading-failure.git in WSL
Open folder loading-failure in VS Code in WSL
VS Code shows that Some projects have trouble loading... with output in this pastiebin.

Expected  behavior
VS Code should load the project successfully as in Windows (Yes, the project successfully loaded in Windows.)
Actual behavior
Failed to load the project which references to dotnet-codegen.
What I've found
It seems that the issue is related to the command dotnet codegen --version.
This command returns the same result in both Windows and WSL:

In the folder loading-failure it shows No executable found matching command "dotnet-codegen"
In the folder loading-failure/APIService it shows 0.6.1+2b937a442a

Closing this as external; there's some odd ways that targets are getting loaded here that might need to get worked out here: https://github.com/AArnott/CodeGeneration.Roslyn
It could also be that an explicit call to dotnet restore is required.
Separately, the DotNetCliToolReference is considered out of date now, and local tools are the preferred way to use .NET tools that are local to a project. This also requires a dotnet tool restore command to allow use of them.


Race condition error, provider accepts calls before first block has been added

Looks like provider accepts calls (and passes them to web3-provider-engine) before the first block has been added. This causes a race condition.
https://gist.github.com/aakilfernandes/e63a6354c82983f0db663d77539b7cb7
https://github.com/MetaMask/provider-engine/blob/master/subproviders/vm.js#L163

@aakilfernandes this should be fixed in the latest release. If you still have troubles, please let me know.


Error when trying to sample with NUTS

I'm trying to work with the very simple model in the getting started tutorial:
import torch
from sbi import utils as utils
from sbi import analysis as analysis
from sbi.analysis import pairplot
from sbi.inference import SNLE, prepare_for_sbi, simulate_for_sbi, MCMCPosterior

num_dim = 3
prior = utils.BoxUniform(low=-2*torch.ones(num_dim), high=2*torch.ones(num_dim))

def simulator(parameter_set):
    return 1.0 + parameter_set + torch.randn(parameter_set.shape) * 0.1

simulator, prior = prepare_for_sbi(simulator, prior)
inference = SNLE(prior)

theta, x = simulate_for_sbi(simulator, proposal=prior, num_simulations=10000)
density_estimator = inference.append_simulations(theta, x).train()

So far so good. Now sampling from the posterior using slice sampling works:
posterior = inference.build_posterior(mcmc_method="slice_np_vectorized",
                                        mcmc_parameters=dict(init_strategy="sir",
                                                         num_chains=10,
                                                         warmup_steps=100))
posterior.sample((1000,), x=torch.tensor([1.,2.,3.]))

But replacing the method with NUTS results in an error:
posterior2 = inference.build_posterior(mcmc_method="nuts",
                                        mcmc_parameters=dict(num_chains=4,
                                                         warmup_steps=1000))
posterior2.sample((1000,), x=torch.tensor([1.,2.,3.]))

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/opt/conda/lib/python3.9/multiprocessing/spawn.py", line 116, in spawn_main
    exitcode = _main(fd, parent_sentinel)
  File "/opt/conda/lib/python3.9/multiprocessing/spawn.py", line 126, in _main
    self = reduction.pickle.load(from_parent)
  File "/opt/conda/lib/python3.9/site-packages/sbi/utils/__init__.py", line 2, in <module>
    from sbi.utils.conditional_density_utils import extract_and_transform_mog
  File "/opt/conda/lib/python3.9/site-packages/sbi/utils/conditional_density_utils.py", line 14, in <module>
    from sbi.utils.torchutils import ensure_theta_batched
  File "/opt/conda/lib/python3.9/site-packages/sbi/utils/torchutils.py", line 15, in <module>
    from sbi.types import Array, OneOrMore, ScalarFloat
  File "/opt/conda/lib/python3.9/site-packages/sbi/types.py", line 14, in <module>
    from torch.utils.tensorboard.writer import SummaryWriter
  File "/opt/conda/lib/python3.9/site-packages/torch/utils/tensorboard/__init__.py", line 4, in <module>
    LooseVersion = distutils.version.LooseVersion
AttributeError: module 'distutils' has no attribute 'version'

Any ideas about how to solve this? Thanks!

It's a bug upstream in setuptools. Should be solved with
pip install setuptools==59.5.0

See here

Thanks! that solved it


Add more resources in web development

More resources should be added inside web development,
the directory structure is as follow,
./pages/web-development-resources

Hey @hasnainmakada-99 , I would love to work on this issue.

Here you go @Arbtrage


Excel file upload failing UTF-8 validation

A user Excel file unexpectedly failed on upload, with "File is not UTF-8 encoded." error

DatasetCreate() is mistakenly trying to read .xlsx and .ods binary files as UTF-8

fixed in DatasetCreate()


obsolete typescript link

all linked page in typescript website have this message "This page has been deprecated"
Article URL
https://github.com/OfficeDev/office-scripts-docs/blob/master/docs/includes/coding-basics-references.md
Issue
all typescript  page has been deprecated. need to update the link

Thanks for reporting this @yaron-sam. I'll fix the links.


firefox rendering issues with lines

Actual Result
Flickering as you zoom in.

deck: deck.gl 6.3.1 - set deck.log.priority=1 (or higher) to trace attribute updates init.js:39:2
luma: luma.gl 6.3.1 - set luma.log.priority=1 (or higher) to trace rendering init.js:23:4
luma.gl: WebGL debug support imported debug.js:9
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. index.js:152:12
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. supported.js:22:15
deck: t.componentName not specified create-props.js:213:4
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. create-browser-context.js:20:15
luma: WebGL2 context (ATI Technologies Inc.,AMD Radeon Pro 560 OpenGL Engine) context.js:191:2
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. index.js:152:12
react-map-gl: 4.0.4 using mapbox-gl v0.51.0 mapbox.js:181:6
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. map.js:1501:19
luma: Found instanced attributes on non-instanced model transform-model model.js:335:6
Error: WebGL warning: texImage2D: Alpha-premult and y-flip are deprecated for non-DOM-Element uploads.
texture.js:71:16
Error: WebGL warning: checkFramebufferStatus: This operation requires zeroing texture data. This is slow. framebuffer.js:232:19
Error: WebGL warning: clear: This operation requires zeroing texture data. This is slow. draw-layers.js:59:4
Error: WebGL warning: texImage2D: Alpha-premult and y-flip are deprecated for non-DOM-Element uploads.

Expected Result
No flickering.
Reproduce Steps

Open http://deck.gl/#/examples/core-layers/geojson-layer-paths in Firefox latest (64.0)

To Do List

[ ] Add label and assign to milestone
[ ] Coding
[ ] Test

Can also reproduce this using the hex layer w/ a small radius.

Tested on my machine , works fine with Firefox 61.0.2 (64-bit) + AMD Radeon Pro 560X, upgraded my Firefox to 64.0 still works fine.
Is this a regression , was this working for you with previous versions of Firefox, how about Chrome, does it work fine.

@1chandu Chrome works fine.
For reference:

I just did a side by side and it is slightly better (but not really) if tested on a retina screen.

The visual artifact is due to antialiasing being disabled. In your log:
getContext: Disallowing antialiased backbuffers due to blacklisting

Not sure if this is caused by the latest release of FF or your machine.

@Pessimistress Is anti-aliasing requested? That message is always printed, if asked for or not (reference: https://bugzilla.mozilla.org/show_bug.cgi?id=1285937)

It is not required, but if it's disabled you get the above visual quality.


feat: add tracing support.

Thought I'd take a shot at this one. Closes #8.
I've added spans to every operation I can find, but I haven't added any additional log messages yet.
Looks like it would be good to implement this in the rustify crate as well. In Client::execute for example.

Thanks for this PR :) If you're up for it, I had planned on adding tracing output to the tests as well, using something like tracing-test but also open to other suggestions. Otherwise, I'm fine to accept this as-is.

Sounds good, will add that today.

How's this? I've instrumented each test and added a couple log messages to get it started.
Using tracing-test at the moment to configure the subscriber, but it couple be easily replaced with an alternative in the future if necessary.

Awesome, thanks for doing that! Looks like you just need to run cargo fmt and I can merge :)

Done, that should do it.


arrow-cpp: 3.0.0 -> 4.0.0

Motivation for this change
The Arrow project decided to make f959141 the new release: [1]
[1] https://lists.apache.org/thread.html/r4e590a68ff151b29b96780e249614a36f9a805911d82edf15c0a52f6%40<dev.arrow.apache.org>
Things done

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

[x] NixOS
[x] 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 nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 120854 at 45e32377 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.google-cloud-bigquery

3 packages skipped due to time constraints:

python39Packages.datasets
python39Packages.intake
python39Packages.pyarrow

6 packages built successfully:

arrow-cpp
python38Packages.datasets
python38Packages.google-cloud-bigquery
python38Packages.intake
python38Packages.pyarrow
xsimd

1 suggestion:

warning: unused-argument
Unused argument: fetchpatch.
Near pkgs/development/libraries/arrow-cpp/default.nix:1:43:
  |
1 | { stdenv, lib, fetchurl, fetchFromGitHub, fetchpatch, fixDarwinDylibNames
  |                                           ^

@GrahamcOfBorg build python3Packages.pyarrow

Fails on darwin:
/tmp/nix-build-xsimd-7.5.0.drv-0/source/include/xsimd/types/xsimd_scalar.hpp:412:9: error: use of undeclared identifier '__sincosf'; did you mea
n 'sincos'?
        __sincosf(val, &s, &c);
        ^~~~~~~~~
        sincos
/tmp/nix-build-xsimd-7.5.0.drv-0/source/include/xsimd/types/xsimd_scalar.hpp:409:17: note: 'sincos' declared here
    inline void sincos(float val, float&s, float& c)
                ^
/tmp/nix-build-xsimd-7.5.0.drv-0/source/include/xsimd/types/xsimd_scalar.hpp:412:24: error: non-const lvalue reference to type 'float' cannot bi
nd to a temporary of type 'float *'
        __sincosf(val, &s, &c);
                       ^~
/tmp/nix-build-xsimd-7.5.0.drv-0/source/include/xsimd/types/xsimd_scalar.hpp:409:41: note: passing argument to parameter 's' here
    inline void sincos(float val, float&s, float& c)
                                        ^

@veprbl would you like to take another look?

Result of nixpkgs-review pr 120854 run on x86_64-darwin 1

1 package marked as broken and skipped:

python39Packages.google-cloud-bigquery

9 packages built:

arrow-cpp
python38Packages.datasets
python38Packages.google-cloud-bigquery
python38Packages.intake
python38Packages.pyarrow
python39Packages.datasets
python39Packages.intake
python39Packages.pyarrow
xsimd

I've submitted the issue upstream https://github.com/xtensor-stack/xsimd/pull/463

@tobim Thank you!


(#50) Use ora for logging

This PR refactors most of implicit logger and explicit console.log logging via the use of the ora-spinner.
The key is to use the spinner exported from lib/utils/spinner.js, which can be used as a global instance.
This PR is structured into several smaller commits, I recommend squash-merging this PR, as in it's whole it's pretty straight-forward. But for testing it was vital to incrementally commit each commands output. Also the last commit fixes the tests, which were broken in ae3ca01 by (unnecessarily) moving the process.exit() call from the final-clause into the then-clause.
P.S.: Closes #50 :slightly_smiling_face:

Thanks a lot @fleischie :)


Macbook pro touchpad: Mute key disabled and inactive

If/When Karabiner-Elements is running, the mute key on the TouchBar seems to be deactivated no matter what configuration is used (even vanilla/blank).

This seems to happen for me with all touchbar 'control strip' functions that are single buttons. That is, the app-specific touchbar features work as expected, and the slider functions on the control strip (like brightness and volume) work fine, but buttons like mute, Siri, mission control, play, keyboard backlight adjusters, etc. all do nothing when pressed.

I think this is a duplicate of #595
Just deactivate the touchbar in Karabiner prefs to make it work (note, you then won't be able to remap the esc button, etc.) .


Code Cleanup

Description

Minor code quality improvements

Overview of Changes

Added a null safety check for @Grid label creation of a non complex entity.
Code clean up related to Java 8 lambda

(SeepvComparator) This was causing a compile error on my machine. Not sure if updating my JDK would have fixed the issue, but it the change is appropriate.

Type of Change

[ ] Bug fix
[ ] Refactor/Technical Debt

Test Details

Existing test cases

Additional Notes

N/A

You did it @lopezton-anthem!
Thank you for signing the Anthem Opensource Software CLA.


Time for v0.9.5 ?

Since there's been a few contributions merged since v0.9.4, I'd really like if there was a new release containing them! (keeping a git clone of the repo in my node_modules is impractical).
On a related note, does anyone know why telling npm to install a specific version of redux-saga doesn't work? When I have this in my package.json:
dependencies: {
  "redux-saga": "git://github.com/yelouafi/redux-saga.git#master"
}

...then the installed node_modules/redux-saga doesn't contain a lib/ directory, it only has dist/
(that's with npm 3.6)

I think yes. I'll be making a release tonight

Thanks a lot! Sorry for opening an issue on a sunday :star2:

forgot to mention 0.9.5 is out https://github.com/yelouafi/redux-saga/releases/tag/v0.9.5

Awesome, thanks!


AudioKit.swiftmodule is either malformed or generated by a different Swift version

Describe the bug
import AudioKit line shows the warning:

'/Users/me/Library/Developer/Xcode/DerivedData/my-app/Build/Products/Debug-iphonesimulator/XCFrameworkIntermediates/AudioKit/Core/AudioKit.framework/Modules/AudioKit.swiftmodule/Project/x86_64-apple-ios-simulator.swiftsourceinfo' is either malformed or generated by a different Swift version. Note that it uses an unstable format and may leak internal project details, it should not be distributed alongside modules

Details (please complete the following information):

Xcode 13.1
Swift 5
Building for an iOS simulator 15.0
M1 mac
AudioKit Version 5.1.0
Added using cocoapods

Steps like clearing DerivedData, re-opening Xcode, etc don't help.

Sounds likes its telling you what it is wrong. AudioKit "is either malformed or generated by a different Swift version." you don't mention which version of AudioKit you're using. Hav you updated to the latest? Closing for now.

That's because you're using the CocoaPods version with Xcode 13. You need to switch to using SPM for AudioKit. The compiled binaries we used are no longer compatible.

I can see now the latest is v5.2.2, while the latest version published on CocoaPods is 5.1.0. That's a bummer AudioKit no longer supports CocoaPods.


Add support for building a query string from a list of parameters

This is currently supported in the latest version, but as the "commons-httpclient" lib was updated, the existing code was removed due to compatibility issues. It's is a crucial fix, since without it, you're not able to make requests with URL parameters.

Yes, URL parameter building is currently broken. When I finish working on branch v2 I'll take care of the master (/v1 branch) and get it working again. I still need some time though, sorry for that and thanks for this PR!

Thanks for the addition!

No problem, glad to be of help ;)


KAFKA-12267; Implement DescribeTransactions API

This patch implements the DescribeTransactions API as documented in KIP-664: https://cwiki.apache.org/confluence/display/KAFKA/KIP-664%3A+Provide+tooling+to+detect+and+abort+hanging+transactions.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@dengziming Good call. I've added a few test cases. I think we were missing authorization of the topics included in the response.

Can the KIP be updated to change TransactionState from an int8 to a string (as implemented in this PR)?

Also is there a reason not to include the LastUpdateTimestamp? It seems pretty valuable to know how long ago the transaction state was modified.
I'm not sure how valuable LastProducerId or LastProducerEpoch would be, but I know those are available too, although (I think) those are in-memory only values used only for allowing retries of transactional calls.


Accent Color

is there a way to change the accent color now that the individual files have been removed?

@itzTheMeow not right now, and i don't think anytime soon - maintaining more than 50 themes at once with all those changes discord loves to add is too hard.
but it's planned, and i would love to continue working on it, but i just know that i won't be able to maintain them all at once

is there a way to make a build script to generate theme files with each accent added? i think some other catp themes do that. i'm not sure how you're doing the accent colors though since it seems a lot of elements are different colors


Refactor/90 di for usercontroller

Pull Request Information
Relates to Github Issue: #90
What is the PR Type:  refactoring
Describe the added/fixed behaviour:

DI database objects
Tests have their own database to use
Tests don't rely on database file anymore
Remove database file from git

Checklist

[x] Pull request has suitable title, adequately described and associated with a github issue
[x] Branch name follows correct convention (e.g. feature/[id]-some-feature)
[x] Branch builds and executes with no errors
[x] Test cases has been generated for the feature and test cases pass
[x] Updated relevant wiki/documentation

Additional Information

Final Reminders
Please remember to squash the commits

Please wait for cloud tests to run as this change may impact them.


Implemented .tar and tar.gz writing

Merged all Constantine-Fry fork fixes
Refactored things a little bit for consistency (always add a space before pointer *, etc.)
Refactored NVHFile progress handling (added NVHProgress class) to support progress tracking when writing (target file size is unknown in this case)
Improved error handling a little bit (do not crash when passing nil paths, use enum for error checking, etc.)
Implemented .tar and .tar.gz writing (some code borrowed from tarkit) with real time progress tracking
Added examples for all possible use cases

Everything tested and working on iOS 8.

Sorry, I made the pull request from the wrong branch. I just opened a new one. It's exactly the same commits, but on a different branch.


Ever increasing Xfrm error count when ipsec is enabled

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
We recently deployed Cilium with IPsec enabled in a cluster comprising approximately 250 pods. Based on the service-level testing we conducted, everything appears to be functioning as expected. Additionally, when we inspected the cilium_vxlan interface using tcpdump, we could observe the proper flow of esp packets.
However, during our assessment of the encryption status using cilium encrypt status, we encountered a somewhat concerning number of Xfrm errors, particularly XfrmOutPolBlock. In one of the nodes with a higher number of pods, we observed this specific error to be at 709,924. Notably, this number increases every time we execute the cat /proc/net/xfrm_stat command on the Cilium agent daemonset.
For the installation of Cilium on our AKS cluster, we utilized the following Helm command in conjunction with the bring your own CNI mode:
helm upgrade --install cilium cilium/cilium --version 1.13.4 \
  --namespace kube-system \
  --set aksbyocni.enabled=true \
  --set nodeinit.enabled=true \
  --set encryption.enabled=true \
  --set encryption.type=ipsec \
  --set hubble.enabled=true \
  --set hubble.relay.enabled=true \
  --set hubble.ui.enabled=true

The error counter stop as soon as we set the encryption.enabled false. So any insight on this issue would be appreciated.
Cilium Version
1.13.2 and 1.13.4
Kernel Version
5.4.0-1106-azure
Kubernetes Version
1.24.9
Sysdump
No response
Relevant log output
No response
Anything else?
cilium encrypt status
Encryption: IPsec
Keys in use: 1
Max Seq. Number: 0x8b194/0xffffffff
Errors: 710577
	XfrmInNoStates: 646
	XfrmOutPolBlock: 709930
	XfrmInError: 1

/proc/net/xfrm_stat
XfrmInError             	1
XfrmInBufferError       	0
XfrmInHdrError          	0
XfrmInNoStates          	646
XfrmInStateProtoError   	0
XfrmInStateModeError    	0
XfrmInStateSeqError     	0
XfrmInStateExpired      	0
XfrmInStateMismatch     	0
XfrmInStateInvalid      	0
XfrmInTmplMismatch      	0
XfrmInNoPols            	0
XfrmInPolBlock          	0
XfrmInPolError          	0
XfrmOutError            	0
XfrmOutBundleGenError   	0
XfrmOutBundleCheckError 	0
XfrmOutNoStates         	0
XfrmOutStateProtoError  	0
XfrmOutStateModeError   	0
XfrmOutStateSeqError    	0
XfrmOutStateExpired     	0
XfrmOutPolBlock         	709930
XfrmOutPolDead          	0
XfrmOutPolError         	0
XfrmFwdHdrError         	0
XfrmOutStateInvalid     	0
XfrmAcquireError        	0

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hi, Can you check if this PR resolves your issue - https://github.com/cilium/cilium/pull/25735?

Hi @aditighag, we actually did a fresh install of version 1.13.4, and we even tried refreshing all the nodes. However, the XfrmOutPolBlock error counter never stops, even days after the installation. We scaled up the node pool and tested as well. Interestingly, we noticed that the newer nodes also immediately start to collect XfrmOutPolBlock errors as soon as some pods are scheduled on the node, and this issue never seems to stop.

We don't recommend using this release for IPsec. See the big warning in release notes: https://github.com/cilium/cilium/releases/tag/v1.13.4.
If you want to enable IPsec, I would suggest to use v1.13.0 or v1.12.7. We are actively working on fixes and will update here once we have them ready.

Hi @pchaigno,
We were originally using version v1.13.2, and we completely purged it to install version v1.13.4. The main reason for upgrading to v1.13.4 was because it included numerous fixes related to ipsec. Additionally, in the release notes, we were unsure if there was a warning about upgrading from a lower version, so we decided to avoid that release if ipsec was being used. Meanwhile would test out v1.13.0 and get back to you as well.

Hi @pchaigno,
We removed the existing Helm release and deployed version 1.13.0 today. As soon as it was deployed, the error counters stopped increasing. So, we performed a node refresh to check if all the newer nodes would have an error count of 0. However, I noticed that during the refreshing period, the error count seemed to be increasing again. But as soon as all the nodes were up and running, and all the pods were scheduled, the error count stopped increasing.
Thank you for assisting with this. I hope the issue we saw on versions 1.13.2 and above will be fixed in a future release.

I hope the issue we saw on versions 1.13.2 and above will be fixed in a future release.

We're working on it. Those XfrmOutPolBlock errors have proved trickier to fix than other bugs we hit (cf. https://github.com/cilium/cilium/pull/26725).

Ah right good to know, let me know if there is anything I can do help!

@MrSupiri We expect #27029 fixed this issue with XfrmOutPolBlock errors. If you can confirm with that PR's image builds, that would be great!

Hi @pchaigno sorry about the delay, I tried using the ci images and running cilium but this lead to a CrashLoopBackOff of cilium agent pods.
Command I used to install cilium
helm install cilium cilium/cilium --version 1.13.5   --namespace kube-system   --set aksbyocni.enabled=true   --set nodeinit.enabled=true   --set encryption.enabled=true   --set encryption.type=ipsec   --set hubble.enabled=true   --set hubble.relay.enabled=true   --set hubble.ui.enabled=true --set image.repository="quay.io/cilium/cilium-ci" --set image.tag="ffb1591ffca925599e253a1ddf84b280a44c2c4a" --set image.useDigest=false

Log:
$ kubectl -n kube-system get pods | grep cilium
cilium-49b4x                                       0/1     CrashLoopBackOff    4 (24s ago)      22m
cilium-4wrlg                                       0/1     CrashLoopBackOff    13 (2m12s ago)   22m
cilium-node-init-5kjkx                             1/1     Running             0                22m
cilium-node-init-bhtwb                             1/1     Running             1 (5m16s ago)    22m
cilium-operator-7f8b898b56-czc8k                   1/1     Running             0                22m
$
$ kubectl -n kube-system logs cilium-49b4x --previous
Defaulted container "cilium-agent" out of: cilium-agent, config (init), mount-cgroup (init), apply-sysctl-overwrites (init), mount-bpf-fs (init), wait-for-node-init (init), clean-cilium-state (init), install-cni-binaries (init)
$
$ kubectl -n kube-system logs cilium-49b4x -c config
Running
level=info msg=Invoked duration="387.656µs" function="cmd.glob..func36 (build-config.go:32)" subsys=hive
level=info msg=Starting subsys=hive
level=info msg="Establishing connection to apiserver" host="https://<IP_ADDRESS>:443" subsys=k8s-client
level=info msg="Connected to apiserver" subsys=k8s-client
level=info msg="Start hook executed" duration=31.269037ms function="client.(*compositeClientset).onStart" subsys=hive
level=info msg="Reading configuration from config-map:kube-system/cilium-config" configSource="config-map:kube-system/cilium-config" subsys=option-resolver
level=info msg="Got 85 config pairs from source" configSource="config-map:kube-system/cilium-config" subsys=option-resolver
level=info msg="Reading configuration from cilium-node-config:kube-system/" configSource="cilium-node-config:kube-system/" subsys=option-resolver
level=info msg="Got 0 config pairs from source" configSource="cilium-node-config:kube-system/" subsys=option-resolver
level=info msg="Start hook executed" duration=14.13608ms function="cmd.(*buildConfig).onStart" subsys=hive
level=info msg=Stopping subsys=hive
level=info msg="Stop hook executed" duration="22.013µs" function="client.(*compositeClientset).onStop" subsys=hive
$
$ kubectl -n kube-system logs cilium-49b4x -c mount-cgroup
level=info msg="Mounted cgroupv2 filesystem at /run/cilium/cgroupv2" subsys=cgroups
$
$ kubectl -n kube-system logs cilium-49b4x -c apply-sysctl-overwrites
sysctl config created/updated
systemd unit 'systemd-sysctl.service' restarted
$
$ kubectl -n kube-system logs cilium-49b4x -c mount-bpf-fs
$
$ kubectl -n kube-system logs cilium-49b4x -c wait-for-node-init
$
$ kubectl -n kube-system logs cilium-49b4x -c clean-cilium-state
$
$ kubectl -n kube-system logs cilium-49b4x -c install-cni-binaries
Installing cilium-cni to /host/opt/cni/bin/ ...
wrote /host/opt/cni/bin/cilium-cni
$

Did I do something wrong here while installing?

1.13.6 has been released and it includes the fix that Paul mentioned above. You could try upgrading to that release and verify if you still see the increasing errors or not. Please note that even with 1.13.6 there are still some problems with the IPSec stack, in particular there's a chance that during key rotations packets get dropped and ongoing connections get interrupted.

@MrSupiri The error you hit is likely because you are trying to use the images from the PR (built for unreleased main) with a v1.13 release. Testing v1.13.6 as suggested by Marga above is likely the easiest way to test the fix now.

Hi @margamanterola and @pchaigno,
I just tested this issue in the same cluster with v1.13.6 and it seems to have resolved the issue.
Still there are some Xfrm errors as soon as cilium was deployed but upon rechecking it after about 40 minutes, I noticed the error counts stayed the same. I assume this is the expected behaviour.
example encryption status of a pod:
Encryption: IPsec
Keys in use: 1
Max Seq. Number: 0xbb488c6/0xffffffff
Errors: 101
	XfrmOutNoStates: 78
	XfrmFwdHdrError: 6
	XfrmInError: 1
	XfrmInNoStates: 16

Thanks for checking!

Still there are some Xfrm errors as soon as cilium was deployed but upon rechecking it after about 40 minutes, I noticed the error counts stayed the same. I assume this is the expected behaviour.

Depending on what you upgraded from, what the state of IPsec (enabled/disabled) was before, and what XFRM errors were already present, it may be expected, yes.


update autest version

[approve ci autest]

[approve ci autest]

Are the last 4 commits of AuTest diff from 1.10.1?  ( I can't find the 1.10.1 tag )
https://bitbucket.org/autestsuite/reusable-gold-testing-system/commits/tag/1.10.2

Replying to myself, the release note is below.

Release 1.10.2

[Fix][PR #29] Improve StreamWriter performance
[Fix] Exists test for file enities did not work correctly when setting False value in constructor
Clean up testing logic to include 3.11
[Fix] Change to using inspect.getfullargspec() api as older API has been removed from python core

https://bitbucket.org/autestsuite/reusable-gold-testing-system/src/master/docsrc/source/changelog.rst

In case it's helpful, one of the things going into this AuTest release is a performance improvement with stream output processing for processes that produce a lot of output. Our ASF CI handles the new http2_flow_control test well, but we noticed in our internal Yahoo CI that we were getting test failures in http2_flow_control because the test was timing out processing the output. This new AuTest release addresses that issue.

Cherry-picked to v9.2.x


TRTIS should support variable-sized input and output tensor dimensions

Currently TRTIS only allows the first dimension of an input/output tensor to be variable sized and only when that dimension represents batching. TRTIS should allow variable-sized dimensions in other cases since these are supported by some of the FWs (e.g. TensorFlow) and not having it limits which models can easily run on TRTIS.

The described limitation is stalling our team's migration from tf-serving to tensorrt-inference-server.  Glad to hear the need is understood and we will be following the progress eagerly!

Thanks for taking this into consideration! This blocks me from switching to tensorrt inference server for quite a while, also makes deploying detection models such a pain. Hope it get supported soon!

hi, can TRTIS support the model with mutilple outputs??

Hi @tilaba. Yes it does support multiple outputs. For example in case of tensorflow object detection api, for your outputs in the config file you set as follows:
output [
{
name: "detection_boxes"
data_type: TYPE_FP32
dims: [ 100, 4  ]
},
{
name: "detection_scores"
data_type: TYPE_FP32
dims: [ 100 ]
},
{
name: "detection_classes"
data_type: TYPE_FP32
dims: [ 100 ]
}
]
It is an array of outputs. Later, when sending request you can use:
results = ctx.run(     {input_name: input_name},     {output: InferContext.ResultFormat.RAW for output in output_names},     batch_size)
Where output_names = ["detection_boxes", "detection_scores", "detection_classes"]

The inference server now supports variable-size input and output tensor dimensions for backends that support them. As of now that is Tensorflow, Caffe2, and custom (assuming your custom backend handles them correctly). You specify such a dimension by using -1 in the model configuration for the appropriate dimension.
This support is on the master branch and will be in the 19.02 release. Please give it a try and report any issues.

@deadeyegoodwin With this feature, our team is excited to explore a migration from tf-serving to TRTIS. Thank you for responding to the community feedback. It is much appreciated.

@deadeyegoodwin When TRTIS container for 19.02 release will be available?

The monthly container releases are typically available around the 25th. So, following typical practice, 19.02 would be available around Monday 2/25. But this month I think it may be delayed till the end of that week.

The inference server now supports variable-size input and output tensor dimensions for backends that support them. As of now that is Tensorflow, Caffe2, and custom (assuming your custom backend handles them correctly). You specify such a dimension by using -1 in the model configuration for the appropriate dimension.
This support is on the master branch and will be in the 19.02 release. Please give it a try and report any issues.

How come TRTIS supports dynamic input size while TensorRT itself doesn't?

@ziyuang TRTIS does not support TensorRT models alone. It also supports other frameworks as well (tensorrt_plan, tensorflow_graphdef, tensorflow_savedmodel, caffe2_netdef, or custom). These platforms do support dynamic input size. To sum up, TRTIS allows you to specify dynamic input size for your models that are able to handle such inputs.

@ziyuang TRTIS does not support TensorRT models alone. It also supports other frameworks as well (tensorrt_plan, tensorflow_graphdef, tensorflow_savedmodel, caffe2_netdef, or custom). These platforms do support dynamic input size. To sum up, TRTIS allows you to specify dynamic input size for your models that are able to handle such inputs.

Good; would I have the computation graph optimized if I use models other than TensorRT PLAN?

Each backend/framework (tensorrt, tensorflow, caffe2) has its own optimization techniques that it applies to the model before execution. Typically, the optimizations performed by tensorrt provide significant speedups relative to other frameworks. But tensorflow does have some optimization as well. There is also the TensorRT-Tensorflow integration that allows you to get many of the benefits of tensorrt while still using tensorflow. TRTIS fully supports tensorflow models that have been optimized with tensorrt. https://github.com/tensorflow/tensorrt


[BUG] - Input Clear Button No Longer Working

NextUI Version
2.3.5
Describe the bug
When you try to clear the input using the clear button, the value is emptied, but the input still displays the uncleared text.
You can try it directly on the docs page: https://nextui.org/docs/components/input#clear-button
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
You can try it directly on the docs page: https://nextui.org/docs/components/input#clear-button and try to clear the input.
Expected behavior
I still see the text I tried to clear and I cannot get rid of it.
Screenshots or Videos
No response
Operating System Version
macOS Sonoma 14.3.1 (23D60)
Browser
Chrome

Hello, In the documentation example, onClear calls console.log so it has no working when the Clear button is clicked. You can switch to other state-changing operations like setState()
import {Input} from "@nextui-org/react";

export default function App() {
  return (
    <Input
      isClearable
      type="email"
      label="Email"
      variant="bordered"
      placeholder="Enter your email"
<EMAIL_ADDRESS>      onClear={() => console.log("input cleared")}
      className="max-w-xs"
    />
  );
}

@ShrinidhiUpadhyaya I'll take over this.


Definitions of crimes are self-referential

These crimes are self-referential in their definitions:

Terrorism is intentionally committing an act of terrorism [...]
Hijacking is intentionally hijacking [...]
Forgery is forging [...]
Damage to property is causing damage to the property [...]
[Assault:] Infliction of bodily harm is inflicting bodily harm [...]
Polluting environment is causing pollution [...]
Assisting in committing a criminal offence is assisting another person in committing another criminal offence [...]

They will need to be sufficiently defined in order to be understandable and enforceable.

these offences will be defined precisely in the future, this is just a provisional code for the purposes of going to Liberland now :)

I understand what you're saying, and the need to have a basic code in place. It's a good start, however, in any court of law, these should be void for vagueness:
https://en.wikipedia.org/wiki/Void_for_vagueness
Someone accused of any of these crimes has no definition of the actus reus that they must defend themselves as not guilty of having commited.
The crime becomes whatever the prosecution deems it to be at the time (as there's also no case law yet established). Thus, we may resonably doubt that the defendant had mens rea because it was not possible for them to know the particular act was unlawful.
It can establish a precedent, and for those eager to assist with being the first settlers, being subject to a drumhead court-martial isn't a compelling thought.
That said, to the degree which I feel comfortable with legal definitions, I'll make a pull request, though it would be great to receive more input from legal scholars.

no need to convince me, I will make it more precise in some time, leave it for now please :)

Where are the crimes even listed?

Drafting a new Criminal Law (will open an issue about it ASAP). Closing the issue, the new law will NOT contain self-referencing clauses.


ensure scala-3 branch ends up with all the changes on main branch

scala-3 branch is basically a fork of main branch but with support for Scala3.
it has been updated with most of the recent commits to main (cherry-picked or an equivalent commit if the cherry pick did not work)
one major commit that needs to be duplicated in scala-3 branch is https://github.com/apache/incubator-pekko-http/commit/56158e46960d601437fda04a726ed81162bd3b2b -- this one did not cherry pick well, huge conflicts

I don't know of any other missing Pekko era commits that are not brought across

there might be other commits that were missed from Akka times (ie from before Pekko work started)

@mdedetrich since you made the https://github.com/apache/incubator-pekko-http/commit/56158e46960d601437fda04a726ed81162bd3b2b changes, would you be a position to do an equivalent change for the 'scala-3' branch so that that branch does not become stale?

@mdedetrich since you made the https://github.com/apache/incubator-pekko-http/commit/56158e46960d601437fda04a726ed81162bd3b2b changes, would you be a position to do an equivalent change for the 'scala-3' branch so that that branch does not become stale?

Will do, I actually wanted to do one additional PR to change the package to org.apache.pekko, since we are starting to have PRs against pekko http I want to reduce merge conflicts

Is there a good reason to use cherry picking for that branch? I think we should use merge the main branch back to the scala-3 branch from time to time. Otherwise, the final merge will be a big problem.

I was imaging a merge as well. I haven't looked into this because of https://github.com/apache/incubator-pekko/issues/107

I started on bringing a branch up to date by merging main (in chunks), WIP is at https://github.com/apache/incubator-pekko-http/compare/main...raboof:incubator-pekko-http:scala-3-merged .
I got stuck at merging 26846a02a116993138365405354efc45cb49b563 - perhaps @luksow can spot what goes wrong there (when you build with sbt ++3.2.1 compile).

@raboof Not sure if entirely relevant but Is there a reason why you are using Scala 3.2.1? I was under the impression that for now we are compiling against Scala 3.1.1 since thats what Pekko is built against (see https://github.com/apache/incubator-pekko/blob/main/project/Dependencies.scala#L57). Note that there is a PR that will update Pekko to use Scala 3.2.0 (see https://github.com/apache/incubator-pekko/pull/273) but it hasn't been merged yet.
Will also update assignees

Not sure if entirely relevant but Is there a reason why you are using Scala 3.2.1?

parboiled2 is on 3.2.1 so we have to be, too.

Note that there is a PR that will update Pekko to use Scala 3.2.2 (see apache/incubator-pekko#273) but it hasn't been merged yet.

This does not really matter right now as Scala 3 is backward compatible but not forward. You can use pekko core with a lower Scala 3 version than pekko-http.

This does not really matter right now as Scala 3 is backward compatible but not forward. You can use pekko core with a lower Scala 3 version than pekko-http.

Okay then its unrelated. There is a version of Parboiled that was released for Scala 3.1.1 (version 2.4.0 specifically) but in any case Pekko will very likely get updated to use Scala 3.2.1 as mentioned before.

Here's a diff to fix the immediate problem:
diff --git a/http-core/src/main/scala/org/apache/pekko/http/impl/model/parser/CommonRules.scala b/http-core/src/main/scala/org/apache/pekko/http/impl/model/parser/CommonRules.scala
index 49b4e05311..12223e5a12 100644
--- a/http-core/src/main/scala/org/apache/pekko/http/impl/model/parser/CommonRules.scala
+++ b/http-core/src/main/scala/org/apache/pekko/http/impl/model/parser/CommonRules.scala
@@ -22,7 +22,9 @@ import pekko.http.scaladsl.model.headers._
 import org.parboiled2._
 import org.parboiled2.support.hlist._

-private[parser] trait CommonRules { this: HeaderParser with Parser with StringBuilding =>
+private[parser] trait CommonRules extends StringBuilding { this: Parser =>
+  protected def maxCommentParsingDepth: Int
+
   import CharacterClasses._

   // ******************************************************************************************

Though, there's another minor problem in the tests.

I think we can just remove the test failing to compile in HttpHeaderSpec regarding If-Match dispatching, it's not relevant any more anyway.

https://github.com/apache/incubator-pekko-http/pull/130 is merged to main branch


fix: Wrong long line break

Signed-off-by: Klaus Smolin<EMAIL_ADDRESS>

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


⚠ Processors has degraded performance

In 6fe25cb, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 125 ms

Resolved: Processors performance has improved in 0c70c2d.


JWT module

I wrote the jwt module source for tinyhttp, example can be found here /examples/auth,
this package takes inspiration from the express-jwt package

@all-contributors please add BRA1L0R for 🔌

@all-contributors please add BRA1L0R for plugin


[WIP] 3 qubit decomposition

Will eventually fix #451.
This is a "master PR" that will be broken up into smaller pieces (TBD around the strategy for that).
Most importantly, this work is blocked on SciPy's 1.5.0 release as it depends on
https://github.com/scipy/scipy/pull/11524. Currently estimated to be out by June 2020.
As the SciPy team is having an issue now with their weekly builds -  I compiled manually wheels for all the Windows, Mac and Linux builds for Travis CI, you can use those wheels locally as well (pip install <wheel>): temporarily in this build I have the wheels in the repo root and added the extra pip installs to .travis.yaml.
For an overview of the high level design decisions: https://drive.google.com/open?id=1SDEtttIAaTwfV9AUs7XAxeW3AUd0qLoY

Update from scipyDev mailing list: https://mail.python.org/pipermail/scipy-dev/2020-May/024154.html
Following schedule for 1.5.0 is accepted:

May 26/2020: branch 1.5.x
May 29/2020: rc1
June 11/2020: rc2 (if needed)
June 20/2020: final release

@viathor - the last one in the Three Qubit Decomposition Series :D Thank you for all the reviews so far!

@viathor - ready for a final review - I hope you are okay with my reasoning around the two outstanding items.

Automerge cancelled: A status check is failing.


MAHOUT-2127 Fix broken DistanceMetrics.scala hyperlink

Purpose of PR:
Please give a short description of what this PR is for.
Important ToDos
Please mark each with an "x"

[x] A JIRA ticket exists (if not, please create this first)[https://issues.apache.org/jira/browse/mahout/]
[x] Title of PR is "MAHOUT-XXXX Brief Description of Changes" where XXXX is the JIRA number.
[ ] Created unit tests where appropriate
[ ] Added licenses correct on newly added files
[ ] Assigned JIRA to self (unable to do)
[x] Added documentation in scala docs/java docs, and to website
[ ] Successfully built and ran all unit tests, verified that all tests pass locally.

If all of these things aren't complete, but you still feel it is
appropriate to open a PR, please add [WIP] after MAHOUT-XXXX before the
descriptions- e.g. "MAHOUT-XXXX [WIP] Description of Change"
Does this change break earlier versions?
No
Is this the beginning of a larger project for which a feature branch should be made?
No

Thanks for the contribu @lewismc !


how to enable GPU mining.

I would like to inquire about how to enable GPU mining with Qitmeer or if there are specific configurations or a separate miner required to leverage GPU resources.
Could you please provide guidance on how to activate GPU mining, and, if possible, the correct command or configuration to start GPU mining? Any assistance with this would be highly appreciated.
@dindinw

I am using the following command
./qitmeer-miner -C config.conf

The GPU mining is not support officially on Qitmeer mainnet && testnet,  The legacy code for GPU mining in the current project is a historical issue. Please don't use the GPU mining.

Is there any specific reason that Qitmeer does not support GPU mining?

So @dindinw can i run gpu mining on privnet or not ? and why gpu mining  is not supported ?

@Ayushoo07
you can run gpu mining for testing purposes on your own privnet,  but it's not guaranteed to be supported or maintained.
Historically, GPU mode has been used in the pre-public testnet to encourage participation . This mode is now obsolete and will not be supported in the official network and test network.

@dindinw ok got it so can you guide me how can i test gpu mining on privnet .

Hello @dindinw as reading the above conversations and knowing that gpu mining is not supported , how can i mine using asic ?

@dindinw how can I mine using asic ?


Update example prometheus.yml

This PR improve the usability of prometheus.yml:

update the examples to include two servers with relevant ports
consistently use ' rather than a mix of " and '

@amnonh please review


fix: Fetch merged settings on reload

Description
Fetches the mergedSettings from settings state on reload. This would avoid the LUIS key error.
Fixes #5285

Coverage decreased (-0.004%) to 55.316% when pulling f937779a62eb4b1521bbfe4124bb2b472d686e4d on srravich/5285-luis-key into 77c35277504c7e152e2761451b3b2dcb3b3f8179 on main.


Graylog-plugin-CEF loading Error

I have stop the graylog service and place the plugin into the plugin directory and restarted the service. But unfortunately I got following error code and the graylog server is not getting up. My Graylog server version is 2.2.2
Need to fix this bug or any method where I can apply CEF plugin into Graylog server input.
[root@graylog ~]# Exception in thread "main" java.lang.NoClassDefFoundError: org/graylog/plugins/pipelineprocessor/a                              st/functions/AbstractFunction
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(Unknown Source)
        at java.security.SecureClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$100(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.net.FactoryURLClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at org.graylog.plugins.cef.CEFInputModule.configure(CEFInputModule.java:28)
        at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
        at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
        at org.graylog2.shared.bindings.PluginBindings.configure(PluginBindings.java:51)
        at com.google.inject.AbstractModule.configure(AbstractModule.java:62)
        at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:340)
        at com.google.inject.spi.Elements.getElements(Elements.java:110)
        at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:138)
        at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104)
        at com.google.inject.Guice.createInjector(Guice.java:99)
        at org.graylog2.shared.bindings.GuiceInjectorHolder.createInjector(GuiceInjectorHolder.java:34)
        at org.graylog2.bootstrap.CmdLineTool.setupInjector(CmdLineTool.java:379)
        at org.graylog2.bootstrap.CmdLineTool.run(CmdLineTool.java:193)
        at org.graylog2.bootstrap.Main.main(Main.java:44)
Caused by: java.lang.ClassNotFoundException: org.graylog.plugins.pipelineprocessor.ast.functions.AbstractFunction
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at java.net.FactoryURLClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        ... 26 more

@minipop4747 Either the version of the plugin you've downloaded isn't compatible with the version of Graylog you're using (try https://github.com/Graylog2/graylog-plugin-cef/releases/tag/2.2.0-beta.3) or you're missing the Pipeline Processing plugin in your Graylog setup.
Either way, we are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our discussion forum or join the #graylog channel on freenode IRC.
Thank you!

@joschi ,
I found this issue on when I place this plugin and restart the service. Also I removed this plugin from the plugin directory and restart the service and tested, No issue observed and the graylog perfectly worked. Apart from that I have tested all 2.x.x plugin listed in https://github.com/Graylog2/graylog-plugin-cef/releases, page none of them worked for me and gave same error. So it should be some error in the plugin, not in the graylog.

@minipop4747 Please continue this issue to our discussion forum or join the #graylog channel on freenode IRC.
If you want help, please include the necessary information, such as the version of Graylog you're using, the version of the plugin you're using, and the complete contents of the logs of your Graylog nodes.


Add Code of Conduct

Fixes #10

I propose to update the code of conduct to the v2.1 version (https://github.com/boa-dev/boa/pull/2365)

This is no longer blocked :) It just needs to be updated.


Phone login is not supported

This article is about "Microsoft Entra ID for customers tenant".
This sentence below is incorrect:
"For example, you can configure a user flow that requires users to sign-in or sign-up with a phone number or email address."
You cannot sign-in or sign-up with a phone number in a customer tenant.

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

ID: 6e84fb9a-837d-46fb-cb96-6231c9bb7552
Version Independent ID: 04010d26-967a-f3c0-011f-21c7dd3d6254
Content: Tutorial: Prepare your customer tenant to authenticate users in a .NET browserless app - Microsoft Entra External ID
Content Source: docs/external-id/customers/tutorial-browserless-app-dotnet-sign-in-prepare-tenant.md
Service: entra-external-id
Sub-service: customers
GitHub Login: @SHERMANOUKO
Microsoft Alias: shermanouko

@rbrayb
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


Add tutorial on migrating from JavaScript

@bowdenk7 @mhegazy @sandersn @RyanCavanaugh any feedback you have would be valuable here.

Updated

:clock1:


Getting 404 with attribute routing in ASPNetCore 2.1.4

I'm trying to setup Web APIs using aspnetcore 2.1.4.
I have a console app which does the following:-
IWebHost managementHost = ManagementHostBuilder.Build();
managementHost.Start();
I have another dll where I have

WebHostBuilder
Startup
Controller

Code snippets are provided below
WebHostBuilder
Has mostly configuring kestrel and sets up the startup class (ManagementStartup)
Startup Class
public IServiceProvider ConfigureServices(IServiceCollection services)
{
   services.AddMvc().SetCompatibilityVersion(CompatibilityVersion.Version_2_1);
   // other stuff
}

public void Configure(IApplicationBuilder app)
{
   // other stuff
  app.UseMvc();
}

Controller class
[Produces("application/json")]
[Route("api/[controller]")]
[ApiController]
public class ProductsController : ControllerBase
{
      [HttpPost]
       public Task<ActionResult> CreateProductAsync(ProductInfo productInfo)
        {
            return Task.FromResult<ActionResult>(new OkResult());
        }
        [HttpGet("{id}")]
        public Task<ActionResult> GetProductAsync(int id)
        {
            return Task.FromResult<ActionResult>(new OkResult());
        }

        [HttpGet]
        public Task<ActionResult> GetProducts(int id)
        {
            return Task.FromResult<ActionResult>(new OkResult());
        }
 }

After I build and hit F5 I do a curl as follows:-
curl --header "Content-Type: application/json; charset=utf-8" http://<IP_ADDRESS>:5889/api/products
My controller is not being hit. What am I missing. The port number is what I have configured kestrel to run under.

Hi @vkukke.
It looks like your APIs require and id parameter. Try to remove the id parameter from the GetProducts API.

yikes. its a typo.  Apologies. Removed it and same result. FYI

Closing this issue as it's resolved now.


Getting started

I tried to follow the direction in the README.md, however, I get the following error when trying that.

I then loaded up the project in visual studio, set the BlazorShop.Web.Client to the startup project and booted up IIS and again got an error.

Which then outputted the following error.

I have .NET 5 SDK

@thalaeg I think that you need to install .NET Core 3.1 SDK

Okay. So I probably just need to specify .NET Core 3.1 sdk (cause it is probably defaulting to .NET 5).

@thalaeg Install .NET Core 3.1 sdk and let me know if thе problem persists 🙂

@thalaeg  I updated the README.md file. You can now run the project from the command prompt 🙂


lottie: embedded (png) images are not drawn properly

Hi,
Having an issue rendering the below animation with thorvg. Looks like it is only rendering the background of the animation.
Animation: Animation -<PHONE_NUMBER>023.json
Result from Thorvg;
https://github.com/thorvg/thorvg/assets/128362946/b54795c3-9d39-4797-a346-14cbe358335a
Expected Result:
https://github.com/thorvg/thorvg/assets/128362946/94c701aa-7c09-4f33-a3ae-29aefa7307d6

@afsalz the fix will be in v0.14.1


fix: do not burn usage for discord bot

When we share a snippet on discord, discord does a free GET request to
generate a pretty embedded link. The thing is, it burns one usage every
time. We don't want discord burns an usage but we want to keep the
pretty embedded link.
We know look for the request User-Agent header, if discord is detected
we don't retrieve the snippet from the database and send a blank page
where only the <head> tag is filled. If a user is faking the
user-agent then he will only download a blank page.
Co-authored-by: Antoine James Tournepiche<EMAIL_ADDRESS>Closes #91
Closes #92

@AntoineJT better not to review as you wrote the code with me, we need the others to agree with our work ;)


Content/contact page

Changes proposed in this pull request:

Added contact page
Replaced links to email address with links to contact page
Minor typo fixes

The credentials to view the Netlify deploy is the following:

username: crabigator
password: googlebegone

Deploy preview for wanikani-knowledgebase processing.
Building with commit c133ae1c1caad7721ac1c8c98d5be00284cc49f3
https://app.netlify.com/sites/wanikani-knowledgebase/deploys/5c5c7a25478d33000874256e


Add Stats Panel (See Tenants) to Tags

As ...
Ozzie - Operator
I want ...
To be able to see the stats of objects that are assigned a tag.
So that ...
So that I can leverage tags to organize environments, such as a multi-tenant based device. Then I can dive into specific details of my tags.
I know this is done when...
I go to tags and I am then able to see the stats with each of the items.
Optional - Feature groups this request pertains to.

[ ] Automation
[ ] Circuits
[ ] DCIM
[ ] IPAM
[ ] Misc (including Data Sources)
[ ] Organization
[x] Plugins (and other Extensibility)
[ ] Security (Secrets, etc)
[ ] Image Management
[ ] UI/UX
[ ] Documentation
[ ] Other (not directly a platform feature)

Database Changes
None
External Dependencies
None

We should expand this UI pattern to any place where there are 3 or more related object types.


currentPage number doesn't work under a template

Hi, thanks a lot for your help. I'm still learning Angular and understanding scope and 2-way data binding. This is my problem:
I have a main controller where I get the items to list from. And the paginated list is inside a template. Now, when I try to change the page from the controller, there is no problem until I use the built-in pagination controls. After that, the controller is unable to change the page anymore. I would like to keep the chance to change the page from both places.
Please, try what I am saying in this example, using the bottom links for change the page:
http://plnkr.co/edit/qs7bf4y6FO00MrjU2SWf?p=preview
I suspect this is a problem related to scope hierarchy. Check this out:
https://github.com/angular/angular.js/wiki/Understanding-Scopes
Thank you vey much

This problem is solved using:
current-page="$parent.currentPage"

Thank you!


v4: objection v1 and plugin ownership

[x] Upgrade to objection v1 (#53)
[x] Refactor plugin ownership of knex and models
[x] Tests
[ ] Docs

@devinivy yo! took a crack at clearing things up re: how knex instances are bound to models. no idea how I did 🎺 thanks for the help today 🙏

really can't wait for 4.0.0 release! things are broken after upgrading to Objection 1.0.0

@crespowang feel free to use this branch in the short term.  The code is stable and well-tested—we're just working on the docs at this point.  Expect a release in the next day or two!