[Bug Report] number validate  bug

Element UI version
2.4.6
OS/Browsers version
win10/chrome
Vue version
2.5.17
Reproduction Link
https://jsfiddle.net/api/post/library/pure/
Steps to reproduce
When we enter a number first and then enter a Chinese character or an English letter, it doesn't report an error but runs through it. But in my opinion, age can't type out characters other than numbers,
What is Expected?
I hope you'll be more careful when you write a demo and solve it
What is actually happening?
i don’t know

@RabbDream 请提供一个正确的链接。


Update ide-overview.md

probably more clarification will be useful

@bergano65 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bergano65 We're going to close this now, as we cannot accept the PR as is. We did however make the change that you suggested. Please see https://docs.microsoft.com/visualstudio/get-started/visual-studio-ide to view the change. And, thanks for helping us improve the documentation!


Check to make sure all STLTs that use REST Transport is still working properly

Check to make sure all STLTs that use REST Transport are still working properly
COVID-19: NY-PHD, WA-PHD, OK-PHD.  ETOR-TI: ETOR, EPIC
1.) Login Prod Admin UI
2.) Set organization
3.) Goto "Daily Data" and download the latest HL7 message
4.) Extract the MSH-10
5.) Goto "Admin" -> "Message Id Search"
6.) Paste the MSH-10 in the "Message ID" box and click Search button
7.) Examine the result to see Success

Get HL7 message daily-data
NY-PHD.ELR
MSH-10: af2f7e68-6abb-42c0-9ae5-ff151f5f0818

WA-PHD.REST
MSH-10: d8e26971-f973-4312-a403-015828ca7044

OK-PHD.ELR
MSH-10: 11f11fc8-9cae-4906-81d8-f919828171a5

Done.


Decide on a testing strategy

One starting point: https://medium.freecodecamp.org/the-right-way-to-test-react-components-548a4736ab22

Snapshot Testing
From https://facebook.github.io/jest/docs/en/snapshot-testing.html
Snapshot tests are a very useful tool whenever you want to make sure your UI does not change unexpectedly.
A typical snapshot test case for a mobile app renders a UI component, takes a screenshot, then compares it to a reference image stored alongside the test. The test will fail if the two images do not match: either the change is unexpected, or the screenshot needs to be updated to the new version of the UI component.
A similar approach can be taken when it comes to testing your React components. Instead of rendering the graphical UI, which would require building the entire app, you can use a test renderer to quickly generate a serializable value for your React tree.

Discussed and decided on a way forward, individual issues created #135, #136, #137, #138, #139, #140


Install error and join jie'dian

2021/12/02 06:39:14 [netclient] node created on remote server...updating configs
2021/12/02 06:39:14 [netclient] retrieving peers
2021/12/02 06:39:14 [netclient] starting wireguard
2021/12/02 06:39:14 error running command: /usr/bin/ip link add dev nm-SA0 type wireguard
2021/12/02 06:39:14 RTNETLINK answers: Not supported
2021/12/02 06:39:14 error running command: /usr/bin/ip address add dev nm-SA0 <IP_ADDRESS>/24
2021/12/02 06:39:14 Cannot find device "nm-SA0"
Device does not exist:
file does not exist
Device does not exist:
file does not exist
2021/12/02 06:39:14 [netclient] attempted to remove interface before editing
2021/12/02 06:39:14 [netclient] error installing: exit status 1
2021/12/02 06:39:15 [netclient] removed machine from SA0 network on remote server
2021/12/02 06:39:15 [netclient] removed SA0 network locally
2021/12/02 06:39:15 [netclient] removed systemd remnants if any existed
2021/12/02 06:39:15 [netclient] removed systemd remnants if any existed

I found out that this module was not loaded
➜  ~ modprobe -a wireguard
failed to find a module named wireguard


Issue involving LuaSignals & ThreadScheduler

There is a major issue involving the LuaSignals and ThreadScheduler preventing further development of PigBot, the Bleu Pigs Discord Server Mascot. Currently, I have narrowed it down to an stuck task within the ThreadScheduler's queue. However, I've checked all the logic involving the ThreadScheduler + tested the ThreadScheduler myself. I am still attempting to review the code, however I feel I may over-complicating the issue and simply cannot see it myself. If anyone can go over with the code with me, that would be fantastic.

And where exactly are you resuming the schedulerThread from Scheduler.lua? Seems like it only gets resumed whenever startService() gets called. Luckily, too, because it seems like the function in it would infinite loop, unless one of the the tasks calls pauseService()


remove r&d organization type

What does this pull request aim to achieve? 💯
Resolves #1044
Removing R&D as organization type as discussed with
To avoid confusion with R&D post type - which we still have:

We also have "Research" as industry if we want to track/use that for other purposes:

[x] I have checked that no one else is working on similar changes.
[x] I have read the latest README and understand the development workflow.
[x] The name of this branch is: feature/<branch_name> (need to have cloned the repo not forked).
[x] This branch is rebased/merged with the latest master.
[x] There are no merge conflicts.
[x] There are no console warnings and errors.
[x] On the right hand side of this PR, I have linked the appropriate issue(s) under "Issues" and added a project progress under "Projects".

Let's get this merged and if there are other comments, let's add them here.


Update kubeconfig docs

This is a...

[x ] Feature Request
[ ] Bug Report

Kubeconfig
Steve Perry (steveperry-53)
PR 4439
Study this topic: Authenticate Across  Clusters with kubeconfig. Is this really a Task page? Does the title reflect the content, or is the content more general than the title? Could some of this content be put in a Concept topic? Could we create one or more Task topics that takes the reader through exercises. If so, Before you begin would probably have to require two clusters. For example, you could create an exercise that has the reader switch from one cluster to another cluster: kubectl config use-context. Either edit this topic, or factor it into new topics. In either case, put the topics into the new Concept and/or Task template. Edit the topic(s) to comply with our style guide. Make it clear that Kubernetes has a file named config in a hidden directory named .kube. There is no file named kubeconfig. Related topic: Share Cluster Access.

PR 4439


TypeScript definitions improvements

This PR follows https://github.com/reactjs/redux/pull/1413. I will open up some wounds here, so please excuse me if I missed any of the points in the previous conversation.
Signature of dispatch
The problem that I still have is with the signature of dispatch. any just isn't type-safe at all. It will propagate silently in the app without the developer even realizing. w.r.t what @pajn and @joshuacc said, there is a difference between consciously making a choice to type-cast and getting any by default. With this in mind, it's even better to use {} instead of any (which btw is what type parameters default to anyway).
Given the nature of dispatch and it being wrapped by middlewares, it isn't possible to properly type it to account for every possibility. (goes with what @xogeny said in previous PR) The default behavior should be to receive Action and return Action. When middlewares are involved, the middleware decides what the action is and what is returned. Unless someone finds of a way to augment the dispatch signature to work auto-magically with specific middlewares, I think it's better to let the user cast explicitly, because it is something known only by him, given the combination of middlewares that he applied.
I understand that explicit cast is more verbose and some may even be tempted to say it's even annoying, but think of it this way: it isn't any different than using Promise or Map or Set. Only the user know what exactly he's dispatching and what he expects to be returned.
Signature of StoreCreator and StoreEnhancer
I'm not sure I fully understand how these work, but the signature looks different to me than what results from the source code: https://github.com/reactjs/redux/blob/master/src/createStore.js#L49
Should be something like:
    interface StoreEnhancer<TState> {
         (createStore: StoreCreator<TState>): (reducer: Reducer<TState>, initialState?: TState) => Store<TState>;
    }

In this case StoreEnhancer should be generic. This leads to another problem. If it's typed as a generic interface, then StoreCreator should be generic as well, in which case we can no longer type the createStore variable. The only way I see to fix this would be to create to interfaces that are basically copy-pastes of each other:
export interface StoreCreatorInferrable {
  <S>(reducer: Reducer<S>, enhancer?: StoreEnhancer): Store<S>;
  <S>(reducer: Reducer<S>, initialState: S,
      enhancer?: StoreEnhancer): Store<S>;
}
export interface StoreCreator<S> {
  (reducer: Reducer<S>, enhancer?: StoreEnhancer<S>): Store<S>;
  (reducer: Reducer<S>, initialState: S,
      enhancer?: StoreEnhancer<S>): Store<S>;
}

cc @aikoven , @igorbt

@Igorbek , I don't think it's possible to infer the types here unless you know exactly what middlewares you added. That's runtime behavior.
Just like my comparison with Promise, you don't know beforehand what that Promise is supposed to resolve to, until someone actually returns something. The middleware case is more or less the same since it might return something or even nothing at all.

You know what you can expect from dispatch if you know what configuration to use.
Ideally, if I had only standard configuration without thunk, dispatch would only expect an action and return it:
export interface Dispatch {
    (action: Action): Action;
}

So then you have no choice but using this signature.
But if you include thunk, you can augment this interface with new supported signatures:
module "redux" { // module augmentation
  export interface Dispatch { // interface augmentation
    (actionCreator: (dispatch: Dispatch) => void): Promise<any>; // whatever it returns
  }
}

So then you can you any of signatures were defined. I believe, TS definition for thunk should be in its package.

I forgot, it takes getState also:
module "redux" { // module augmentation
  export interface Dispatch { // interface augmentation
    (actionCreator: (dispatch: Dispatch, getState: () => any) => void): Promise<any>; // whatever it returns
  }
}

If we define Dispatch to be typed by state< it'd be more useful:
module "redux" { // module augmentation
  export interface Dispatch<TState> { // interface augmentation
    (actionCreator: (dispatch: Dispatch, getState: () => TState) => void): Promise<any>; // whatever it returns
  }
}

And then store must refer to its's state type in dispatch method.

Ok, I've found what it returns. So the thunks's signature would be:
module "redux" {
  export interface Dispatch<TState> {
    <TResult>(asyncAction: (dispatch: Dispatch, getState: () => TState) => TResult): TResult;
  }
}

I've added PR with my thoughts to your PR use-strict/redux#1 :)

@Igorbek , any ideas about the StoreEnhancer in my first post? That's the only thing remaining that I haven't quite figured out.

@use-strict for me, StoreEnhancer looks good as it is now. However, according to its using it doesn't need to support this complex signature of StoreCreator. The function produced by an enhancer can strictly expect initialState were passed and other enhancer weren't passed:
export type StoreEnhancerStoreCreator<S> = (reducer: Reducer<S>, initialState: S) => Store<S>;
export type StoreEnhancer<S> = (next: StoreCreator) => StoreEnhancerStoreCreator<S>;

As you suggested, a typed version of StoreCreator could be added, but not replaced since createStore must be generic. I'll create other PR to express it.

@Igorbek how's its going with PR? Should we wait for it before making a release?

@aikoven Please, if possible, make a release of #1413 that's already merged asap, and then we discuss about the this and #1537 for the next release.

My PR is ready to merge. However the reviewers have asked a few questions which I answered, but didn't hear back from them that is enough or if they have some other concerns.
My PR introduces changes to Dispatch that is more desirable to have earlier rather than after a version without it. I'd say it's worth to wait it merged. I hope it wound't take to much to wait.

@Igorbek I meant another PR that you mentioned above, with changes to StoreEnhancer/StoreCreator. I can't find it in the PR list.

Oh. I've completely forgot about it and misunderstood you meant it. It wouldn't take too much to do this, but I can do it in evening only (it's morning now). So, optimistically, with one day review from you guys, it takes 2 days in total. I know you want to release new features and it might delay, does it work for you?

Out in 3.4.0.


Plans to release 0.4.7?

Currently receiving this error on Android Studio 2.4 Preview 7:
> Annotation processors must be explicitly declared now.  The following dependencies on the compile classpath are found to contain annotation processor.  Please add them to the annotationProcessor configuration.
  - auto-service-1.0-rc2.jar
Alternatively, set android.defaultConfig.javaCompileOptions.annotationProcessorOptions.includeCompileClasspath = true to continue with previous behavior.  Note that this option is deprecated and will be removed in the future.
See https://developer.android.com/r/tools/annotation-processor-error-message.html for more details.

I believe the https://github.com/rharter/auto-value-gson/commit/a94fd1b3e7ced736013c395715d393606e26de68 commit should fix this. Please correct me if I'm wrong (JavaPoet might need to be compileOnly as well, but not sure.
Similarly for https://github.com/rharter/auto-value-parcel

Think we can close this as 0.5.0 has been released.

Hi @autovalue , I'm having this problem with auto-value-gson 0.5.0 and Android Studio 3.0 Beta 4.
Any idea how to fix it?
My dependencies:
autoValueVersion = '1.4.1'
    autoValueGsonVersion = '0.5.0'
    autoValueCursorVersion = '1.1.0'
    autoValueParcelVersion = '0.2.5'
    autoValueWithVersion = '1.0.0'
    autoValueMoshi = '0.4.3'
    auto = [
            value           : 'com.google.auto.value:auto-value:' + autoValueVersion,
            valueCompiler   : 'com.google.auto.value:auto-value:' + autoValueVersion,
            gsonCompiler    : 'com.ryanharter.auto.value:auto-value-gson:' + autoValueGsonVersion,
            gson            : 'com.ryanharter.auto.value:auto-value-gson:' + autoValueGsonVersion,
            parcel          : 'com.ryanharter.auto.value:auto-value-parcel:' + autoValueParcelVersion,
            with            : 'com.gabrielittner.auto.value:auto-value-with:' + autoValueWithVersion,
            cursorCompiler  : 'com.gabrielittner.auto.value:auto-value-cursor:' + autoValueCursorVersion,
            cursorAnnotation: 'com.gabrielittner.auto.value:auto-value-cursor-annotations:' + autoValueCursorVersion,
            moshiCompiler   : 'com.ryanharter.auto.value:auto-value-moshi:' + autoValueMoshi,
            moshiAnnotation : 'com.ryanharter.auto.value:auto-value-moshi-annotations:' + autoValueMoshi,
    ]


Remove tokens definitions from ICP integration

📝 Description
Remove USDC token definition from ICP Integration as it is not a token supported on the network
❓ Context

Impacted projects: crypoassets
Linked resource(s): ``

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

Hi @emmanuelm41 please just provide a changeset using pnpm changeset and we're good to go 👍 thanks!

Done! Thanks!

Oops I forgot about this, but there are a couple snapshots to update when you change the list of supported currencies/tokens:

pnpm desktop test:jest --runTestsByPath src/generate-cryptoassets-md.test.ts -u
pnpm common jest --runTestsByPath src/currencies/sortByMarketcap.test.ts -u

Done!

@emmanuelm41 we have an ongoing issue with the Desktop tests, that's currently blocking many of our PRs too. Sorry about this 🙏 I'll let you know as soon as it's solved on our side, then you'll just have to rebase.

Let me know then!! Thanks for the quick response!

@emmanuelm41 Could you please rebase on develop? Let's give this another go.

@emmanuelm41 Could you please rebase on develop? Let's give this another go.

Done!


tendermint-rs: Add AbciQuery to Method enum

Currently calling abci_query calls the abci_info rpc

D'oh. It'd be good to have an integration test for this (it's the only RPC endpoint that doesn't have one, afaik, because I didn't know how to write one).
That said, I'm going to merge this as-is. And FYI, this whole crate is moving soon to:
https://github.com/interchainio/tendermint-rs

How are you currently running all other integration tests?
Do I need a certain tendermint node running in the background?

The integration tests presently have the #[ignore] attribute, so you need to run them with:
$ cargo test --all-features -- --ignored

I'm presently testing them against gaiad hitting cosmoshub-2, although they're presently written in such a way they should work against any active Tendermint node which has synced to an outside network


Flashing Samsung Galaxy Tab Pro 10.1 Wifi (SM-T520) fails with "Protocol initialisation failed!"

Device: Samsung Galaxy Tab Pro 10.1 Wifi aka. SM-T520 aka. picassowifi
Recovery: clockworkmodrecovery.6051.picassowifi.img
Heimdall host OS: Ubuntu 14.04.1 LTS (trusty)
Heimdall version: git d0526a3
When I try to flash a recovery to my T520, I get the following error:
bin • sudo ./heimdall flash --RECOVERY /home/jason/Desktop/Cyanogen/SM-T520/clockworkmodrecovery.6051.picassowifi.img --no-reboot
Heimdall v1.4.1

Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is
encouraged.

If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/

Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...

Initialising protocol...
ERROR: Protocol initialisation failed!

Releasing device interface...

The device doesn't indicate that any downloading has taken place, and when I reboot into recovery it's just the stock recovery.
I've successfully flashed a different device before successfully using the same USB port and cable (although an older version of Heimdall, 1.4.0).
Please let me know if there is any debugging info I can provide that might help.

Same result on Windows 7 using 1.4.0.

finally i flashed my SM-T530 Galaxy Tab 4 with linux heimdall, iam so happy - no more need for a virtualbox with windows on it just for using odin if download mode is needed.
linux distribution is http://linuxbbq.org -  NOX: Lacipecsenye (amd64)
this is what i did:
sudo apt-get install libudev1 libudev-dev                   \
                     libusb-1.0-0 libusb-1.0-0-dev          \
                     build-essential pkg-config zlib1g-dev  \
                     libusb-dev libqt4-dev qt4-qmake        \
                     autoconf libtool libusb-1.0-0-dev      \
                     qt5-default

git clone git://github.com/Benjamin-Dobell/Heimdall.git

cd Heimdall
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

sub77@grill:~/Heimdall$     mkdir build
sub77@grill:~/Heimdall$     cd build
sub77@grill:~/Heimdall/build$     cmake -DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is GNU 5.2.1
-- The CXX compiler identification is GNU 5.2.1
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found libusb: /usr/lib/x86_64-linux-gnu/libusb-1.0.so
-- Checking if large (64-bit) file support is available...
-- Checking if large (64-bit) file support is available - yes
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8")
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sub77/Heimdall/build
sub77@grill:~/Heimdall/build/bin$ ./heimdall flash --RECOVERY ~/recovery.img
Heimdall v1.4.1
Copyright (c) 2010-2014 Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...

I had the same issue. After reading [http://forum.xda-developers.com/galaxy-tab-pro-12-10-8/help/flash-to-sm-t520-tab-pro-10-1-wifi-t3188168](a forum thread on this problem) I tried with a different USB port on the same machine. Two out of three ports did not work.

I tried 1.4.0 on different USB ports to no avail. Compiled current 1.4.1 and it worked at once.

Closing as reported as fixed on master.

This happened for me on v1.4.1. There's a few ways to fix it:

Ensure you have the latest & greatest version of Heimdall
Install all this:
sudo apt-get install build-essential cmake zlib1g-dev qt5-default libusb-1.0-0-dev libgl1-mesa-glx libgl1-mesa-dev
Reboot your computer
Try connecting on a different USB port - 3 of my USB ports didn't work, and one did!

Trying a different USB port worked for me, after installing from source on Arch from here:
https://aur.archlinux.org/packages/heimdall-git/


added logging for install_id, trace_id

Small addition to print out to the console if Scout is disabled, and to log (printing to the console also if --verbose) the install_id and trace_id for debugging.

Closed PR due to changes in 2505 that override.  in 2505 printing the notification that Scout (phone-home) is disabled, and the install_id and trace_id, are reformatted and colorized.


Repeated terms in output with --find-limits

Running this on Trilangle commit 57b7b8b gives redundant output:
$ cd wasm
$ npx engine-check --find-limits
^14.18.0 || ^16.13.0 || ^16.13.0 || >=18.0.0 || >=18.0.0

The culprit seems to be getIntersection('>=12 || >=16', new semver.Range('>=14.0.0 <15.0.0-0||>=16.0.0 <17.0.0-0||>=18.0.0')) for that particular case. For whatever reason that returns a semver.Range whose string representation is >=14.0.0 <15.0.0-0||>=16.0.0 <17.0.0-0||>=18.0.0||>=16.0.0 <17.0.0-0||>=18.0.0.

https://github.com/bbrk24/engine-check/blob/e2eb23075fc166873ceab995cc4c9b206733a9b5/getIntersection.js#L48-L52
This is probably it. I was hoping the Range c'tor was smarter than this...

filed npm/node-semver#676

Okay I guess I have to do this manually


[ENH]: replace get_* methods on Arrow blocks with get_range()

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2934  👈
#2921
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @codetheweb and the rest of your teammates on  Graphite

Looks good to me

Merge activity

Nov 4, 1:28 PM EST: A user started a stack merge that includes this pull request via Graphite.


Fix SnowparkTableDataSet docstrings

Description
See errors at https://github.com/kedro-org/kedro/pull/2485.
Development notes
I tried a docs build locally:
diff --git a/docs/kedro-datasets-docs.sh b/docs/kedro-datasets-docs.sh
index 10054034..aa4bc8f7 100755
--- a/docs/kedro-datasets-docs.sh
+++ b/docs/kedro-datasets-docs.sh
@@ -7,7 +7,7 @@ set -o nounset
 # Exit script if a statement returns a non-true return value.
 set -o errexit

-pip install kedro-datasets
-pip install --no-deps -t kedro/to_delete kedro-datasets
+pip install ../kedro-plugins/kedro-datasets
+pip install --no-deps -t kedro/to_delete ../kedro-plugins/kedro-datasets
 mv kedro/to_delete/kedro_datasets kedro/datasets
 rm -r kedro/to_delete

And then make build-docs.
Without the change, it fails:
/home/docs/checkouts/readthedocs.org/user_builds/kedro/checkouts/2485/kedro/datasets/snowflake/snowpark_dataset.py:docstring of kedro.datasets.snowflake.snowpark_dataset.SnowparkTableDataSet:3:Error in "code-block" directive:
maximum 1 argument(s) allowed, 19 supplied.

.. code-block:: yaml
    weather:
      type: kedro_datasets.snowflake.SnowparkTableDataSet
      table_name: "weather_data"
      database: "meteorology"
      schema: "observations"
      credentials: db_credentials
      save_args:
        mode: overwrite
        column_order: name
        table_type: ''

Checklist

[ ] Opened this PR as a 'Draft Pull Request' if it is work-in-progress
[ ] Updated the documentation to reflect the code changes
[ ] Added a description of this change in the relevant RELEASE.md file
[ ] Added tests to cover my changes

Right?? I'm going to add "whitespace" to my list of LinkedIn skills


Reverb effect - Error in `python': corrupted double-linked list

🐛 Bug
Getting "Error in `python': corrupted double-linked list" error.

Error in `python': corrupted double-linked list: 0x000055d6aeea0e10 ***

I can't find example usages of the reverb effect elsewhere but this I believe this is the right usage (otherwise SoX should throw an error).
To Reproduce
Steps to reproduce the behavior:
E = torchaudio.sox_effects.SoxEffectsChain()
E.set_input_file(filename)
E.append_effect_to_chain("reverb", [50.0])
x, sr = E.sox_build_flow_effects()

Backtrace: https://gist.github.com/brianc118/05519d0242286fdddfbebe28c722bd06
Environment
PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: CentOS Linux release 7.7.1908 (Core)
GCC version: (GCC) 4.8.5 20150623 (Red Hat 4.8.5-36)
CMake version: version 3.15.3

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 10.1.168
GPU models and configuration: GPU 0: Tesla K40m
Nvidia driver version: 418.67
cuDNN version: Probably one of the following:
/opt/local/stow/cudnn-10.0-v<IP_ADDRESS>/lib64/libcudnn.so.7.5.1
/opt/local/stow/cudnn-7.0-linux-x64-v3.0-prod/lib64/libcudnn.so.7.0.64
/opt/local/stow/cudnn-7.0-linux-x64-v4.0-prod/lib64/libcudnn.so.4.0.7
/opt/local/stow/cudnn-8.0-linux-x64-v5.1/lib64/libcudnn.so.5.1.10
/opt/local/stow/cudnn-8.0-linux-x64-v6.0/lib64/libcudnn.so.6.0.21
/opt/local/stow/cudnn-9.0-linux-x64-v7/lib64/libcudnn.so.7.1.4
/usr/lib64/libcudnn.so.7.5.1

Versions of relevant libraries:
[pip3] numpy==1.10.4
[conda] torch                     1.4.0                    pypi_0    pypi
[conda] torchaudio                0.4.0                    pypi_0    pypi

I can't reproduce the same error, but I do get a segmentation fault and/or an error.
In [1]: filename = "sinewave.wav"
In [2]: import torchaudio
In [3]: E = torchaudio.sox_effects.SoxEffectsChain()
In [4]: E.set_input_file(filename)
In [5]: E.append_effect_to_chain("reverb", [50.0])
In [6]: x, sr = E.sox_build_flow_effects()

zsh: segmentation fault (core dumped)

In [1]: filename = "sinewave.wav"
In [2]: import torchaudio
In [3]: E = torchaudio.sox_effects.SoxEffectsChain()
In [4]: E.append_effect_to_chain("reverb", 50.0)
In [5]: x, sr = E.sox_build_flow_effects()

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-5-437cda69b739> in <module>
----> 1 x, sr = E.sox_build_flow_effects()

~/anaconda3/envs/audio-built/lib/python3.7/site-packages/torchaudio-0.5.0a0+542fbdf-py3.7-linux-x86_64.egg/torchaudio/_backend.py in wrapper(*args, **kwargs)
     50             if get_audio_backend() not in backends:
     51                 raise RuntimeError("Function {} requires backend to be one of {}.".format(func.__name__, backends))
---> 52             return func(*args, **kwargs)
     53         return wrapper
     54

~/anaconda3/envs/audio-built/lib/python3.7/site-packages/torchaudio-0.5.0a0+542fbdf-py3.7-linux-x86_64.egg/torchaudio/sox_effects.py in sox_build_flow_effects(self, out)
    150                                            self.filetype,
    151                                            self.chain,
--> 152                                            self.MAX_EFFECT_OPTS)
    153
    154         torchaudio._audio_normalization(out, self.normalization)

TypeError: build_flow_effects(): incompatible function arguments. The following argument types are supported:
    1. (arg0: str, arg1: at::Tensor, arg2: bool, arg3: _torch_sox.sox_signalinfo_t, arg4: _torch_sox.sox_encodinginfo_t, arg5: str, arg6: List[_torch_sox.SoxEffect], arg7: int) -> int

Invoked with: None, tensor([]), True, None, None, 'raw', [SoxEffect (reverb ,["50.0"])
], 20

Do you have the corresponding command in sox that works?

I just tried running your code @vincentqb and it did not occur any error to me.
Using:
macos: Mojave 10.14.6
sox: 14.4.2_3
torchaudio:  0.4.0

Trying to replicate the error running the snipped from @vincentqb, it produced the effect correctly.
Using:
macos: Mojave 10.14.6
torchaudio: 0.4.0
sox: 14.4.2_3

@vincentqb I'm not sure what your second snippet is trying to do since you don't call set_input_file().
I can reproduce the same segfault with sinewave.wav. However it seems to be dependent on wav file. For example, if the file is steam-train-whistle-daniel_simon.wav then there is no segfault.
import faulthandler

faulthandler.enable()

filename = "steam-train-whistle-daniel_simon.wav"

import torchaudio
E = torchaudio.sox_effects.SoxEffectsChain()
E.set_input_file(filename)
E.append_effect_to_chain("reverb", [50.0])
x, sr = E.sox_build_flow_effects()
torchaudio.save('out.wav', x, sr)

Runs fine. However if we set it to sinewave.wav we get the following segfault
Fatal Python error: Segmentation fault

Current thread 0x00007fe7d8d1a740 (most recent call first):
  File "/home/Student/s4396976/miniconda2/envs/pytorch/lib/python3.7/site-packages/torchaudio/sox_effects.py", line 152 in sox_build_flow_effects
  File "/home/Student/s4396976/miniconda2/envs/pytorch/lib/python3.7/site-packages/torchaudio/_backend.py", line 51 in wrapper
  File "test.py", line 11 in <module>
[1]    42171 segmentation fault  python test.py

Do you have the corresponding command in sox that works?

sox sinewave.wav out.wav reverb 50

Thanks for pointing out the typo, I corrected the example above :)

Do you know if there's a previous version of torchaudio for which it ever worked?

It works with macos, I tried in the other day with the snipped that you provided @vincentqb

Do you know if there's a previous version of torchaudio for which it ever worked?

I'm not aware of any version that worked. I've only started using torchaudio recently.

@brianc118 - I was able to reproduce this with an earlier install of torchaudio on Mac, but your snippet succeeded after I updated to our most recent version. Here is the exact code I executed
import torch
import torchaudio
filename = "./test/assets/sinewave.wav"
E = torchaudio.sox_effects.SoxEffectsChain()
E.set_input_file(filename)
E.append_effect_to_chain("reverb", [50.0])
x, sr = E.sox_build_flow_effects()

Please let me know if this is still an issue after the update.

@cpuhrsch I'm still getting this on linux (CentOS) after updating to version 0.5.0, running the exact code you listed.

closing the issue as SoxEffectsChain has been removed from torchaudio in #977.


same config.yml work on vmware_exporter script but not on dockerized vmware_exporter

hi,
here are my setup:
Operating System: Ubuntu 20.04.3 LTS
Docker version 20.10.12, build 20.10.12-0ubuntu2~20.04.1
vmware_expoerter 0.18.3 ( pip )
i have installed a vmware_exporter using pip and started with this config file :
default:
vsphere_host: "XXXXXXX"
vsphere_user: "XXXXXXX"
vsphere_password: "XXXXXXXX"
ignore_ssl: True
specs_size: 5000
fetch_custom_attributes: True
fetch_tags: True
fetch_alarms: True
collect_only:
vms: False
vmguests: False
datastores: False
hosts: True
snapshots: False
AAAA-vc001v:
vsphere_host: "XXXX"
vsphere_user: 'XXXXXXX'
vsphere_password: 'XXXXX'
ignore_ssl: True
specs_size: 5000
fetch_custom_attributes: True
fetch_tags: True
fetch_alarms: True
collect_only:
vms: False
vmguests: False
datastores: False
hosts: True
snapshots: False
BBBB-vc001v:
vsphere_host: XXXXX
vsphere_user: 'XXXXX'
vsphere_password: 'XXXXXX'
ignore_ssl: True
specs_size: 5000
fetch_custom_attributes: True
fetch_tags: True
fetch_alarms: False
collect_only:
vms: True
vmguests: True
datastores: True
hosts: True
snapshots: True
CCCC-vc001v:
vsphere_host: XXXXXXXX
vsphere_user: 'XXXXXX'
vsphere_password: 'XXXXXXXX'
ignore_ssl: True
specs_size: 5000
fetch_custom_attributes: True
fetch_tags: True
fetch_alarms: False
collect_only:
vms: False
vmguests: False
datastores: False
hosts: True
snapshots: False
i start the exporter with this command :
vmware_exporter -c ./config.yml
it runs fine . i'm able to get each section from browser : http://XXXX:9272/metrics?section=AAAA-vc001v or from prometheus.
Using the same config  using dockerized vmware_exporter , it's not able to find my section:
starting with this command :
docker run -it --rm -p 9272:9272 --name vmware_exporter --network=host -v /home/igc5616/workspace/vmware_exporter/config.yml:/opt/vmware_exporter/config.yml pryorda/vmware_exporter
it got this error message when i try to reach the section:
WARNING: Published ports are discarded when using host network mode
2022-07-25 09:52:59,111 INFO:Starting web server on port :9272
2022-07-25 09:54:31,983 INFO:AAAA-vc001v is not a valid section, using default
2022-07-25 09:54:31,983 INFO:No vsphere_host or target defined
when i validate the config.yml on docker's container shell:
(vmware_exporter_env) igc5616@gtnbs-mn501v:~/workspace/vmware_exporter$ sudo docker ps
CONTAINER ID   IMAGE                              COMMAND                  CREATED         STATUS         PORTS     NAMES
683ee702473d   pryorda/vmware_exporter            "/usr/local/bin/vmwa…"   3 minutes ago   Up 3 minutes             vmware_exporter
a3c7fb886b6f   grafana/grafana-enterprise:8.5.0   "/run.sh"                3 days ago      Up 3 days                pensive_lovelace
df64dd88de28   prom/prometheus                    "/bin/prometheus --c…"   6 days ago      Up 4 days                affectionate_bouman
(vmware_exporter_env) igc5616@gtnbs-mn501v:~/workspace/vmware_exporter$ sudo docker exec -it 683ee702473d sh
/opt/vmware_exporter # ls
CHANGELOG.md README.md                 config.yml                openshift                 setup.py                  vmware_exporter
Dockerfile                alerts                    dashboards                requirements-tests.txt    systemd                   vmware_exporter.egg-info
LICENSE                   build                     docker-compose.yml        requirements.txt          tests
MANIFEST.in               catalog-info.yaml         kubernetes                setup.cfg                 validate-signature.rb
/opt/vmware_exporter # cat config.yml
default:
vsphere_host: "XXXXXX"
vsphere_user: "XXXXXXX"
vsphere_password: "XXXXXXX"
ignore_ssl: True
specs_size: 5000
fetch_custom_attributes: True
fetch_tags: True
fetch_alarms: True
collect_only:
vms: False
vmguests: False
datastores: False
hosts: True
snapshots: False
AAAAA-vc001v:
vsphere_host: "gtnbs-vc001v"
vsphere_user: "XXXXXX"
vsphere_password: "XXXXXXX"
ignore_ssl: True
specs_size: 5000
--- CUT---
it shows config file is the same but SECTION is not reckonized with dockerized vmware_exporter.
any help or clue will be welcome !
regards,
georges

it's run command with config_file=None and all config is loaded from environments, you can read configure function and AAAA-vc001v is not a valid section, using default. Message No vsphere_host or target defined appeared because no environment VSPHERE_HOST.
So:

you can use docker compose as example
or start container with command docker run ... /usr/local/bin/vmware_exporter -c /opt/vmware_exporter/config.yml

hi,
thanks. it works . it's because of my inexperience with docker  :)


Allow passing arbitrary NODE_OPTIONS to Node when starting TS Server

Right now we have typescript.tsserver.maxTsServerMemory which lets users configure the --max-old-space-size flag value provided to whatever Node is at typescript.tsserver.nodePath, but there are other possible cases where one might want additional flags, e.g. --require=pprof-it for profiling tsserver or --min-semi-space-size/--max-semi-space-size for large monorepos similar to --max-old-space-size.  Rather than just adding these as options one by one as needed, it would be more future-proof to just provide a single way of providing these flags.
Just some examples of how this might be surfaced:

Allow specifying these flags as part of typescript.tsserver.nodePath,
e.g. "typescript.tsserver.nodePath": "/usr/local/bin/node --max-old-space-size=4096"
or "typescript.tsserver.nodePath": "NODE_OPTIONS='--max-old-space-size=4096' /usr/local/bin/node"
Add a separate setting, e.g. "typescript.tsserver.nodeArguments": ['--max-old-space-size=4096'],

For now we're using this workaround (https://github.com/microsoft/TypeScript/issues/30981#issuecomment-489202213) that folks used to do before typescript.tsserver.maxTsServerMemory existed.

Sounds too specialized to add to core VS Code but as a workaround try pointing nodePath a proxy script that spawns node with the arguments you need. Something like:
#!/bin/sh

MAX_HEAP_SIZE= 12000

node --max-old-space-size=$MAX_HEAP_SIZE "$@"

Sounds too specialized to add to core VS Code but as a workaround try pointing nodePath a proxy script that spawns node with the arguments you need. Something like:
#!/bin/sh

MAX_HEAP_SIZE= 12000

node --max-old-space-size=$MAX_HEAP_SIZE "$@"


Package Portable Server for Mac OS

As a user, I would like to be able to install Portable Server from a Homebrew package.
Considerations:

The installer may add items to the Filer Explorer context menu for <.glb> and <.glm> files to be served by a user instance of Portable Server.

AC:

Add a build script that produces a Homebrew package for Portable Server for the architecture you are building on. (64-bit x86 should be supported.)
The installer may add a service that could be added to a run-level.
The service should be configurable from files under .
A user without root privileges should be able to start the server from the command line.
The package should work on recent versions of Mac OS (to be clarified).

We should probably split this ticket up. The original portable installer didn't support configuring as a service, so I think that should be split into its own ticket.

It could be split into a separate ticket.
I was hoping requires no more than symlinking configuration files from , and running Python from a standard service wrapper, but practice always tends to be more complex.


add automl specific paths in codeowners

Description
Updated automl job specific paths in code owners
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

@jsquire Do bot rules need to be changed to include all the listed paths for the ML-AutoML tag?

@jsquire Do bot rules need to be changed to include all the listed paths for the ML-AutoML tag?

Can you please help to understand implications with these many paths? I have included those that are specific to automl jobs here.

Can you please help to understand implications with these many paths? I have included those that are specific to automl jobs here.

GitHub does not apply labels to the PR; those are done by other automation.  If we want to ensure that the associated label is added to pull requests based on the paths, the bot rules must be updated to reflect these changes.


rdopkg reqcheck is not using stdout

rdopkg-0.29.1-1.fc21.noarch
$ rdopkg reqcheck > 00reqs
python-oslo-concurrency >=2.3.0  (>=2.3.0 in .spec)
... (snip rest of stderr output which should be going to stdout) ...
$ cat 00reqs
## get_package_env
## reqcheck

MET:

VERSION NOT ENFORCED:

VERSION MISMATCH:

MISSING:

Fixed in bbd6b7e9627c63ba29189ded7b135a647695ffe5.


Add SSE switch to HMM_CLAMP for branchless comparison.

This change adds a compile-time switch, if compiling with SSE, to use the _mm_(min|max)_ps intrinsics in conjunction for a branchless clamp.
Performance has not been tested. However I think it's almost as clear as the scalar code (maybe that's Intel Intrinsic stockholm syndrome). I'll leave that up to you.

Thanks for the PR. I started looking at the disassembly and some benchmarks, and it seems we can actually make HMM_Clamp branchless (in optimized code) just by turning the if / else if into two if statements:
float HMM_ClampBranchless(float Min, float Value, float Max)
{
    float Result = Value;

    if(Result < Min)
    {
        Result = Min;
    }

    if(Result > Max)
    {
        Result = Max;
    }

    return (Result);
}

I ran some benchmarks, and going branchless definitely gives us better results, but the SSE and "normal" branchless versions perform basically the same in optimized builds. The benchmarks probably exaggerate the gains because the data is totally random and uniformly weighted across the possible branches, so it's basically the worst case for the branchy version.
I also looked at performance in unoptimized builds, and the SSE version actually fared the worst there, although all approaches had similar runtime. I think it's because despite being branchless, the SSE code generates a lot of instructions. The new "branchless" version actually did the best.
Godbolt: https://godbolt.org/z/n93q9E
Quick Bench: https://quick-bench.com/q/JvCK6K9Jk9omAFZ2d9WNuj9YXZw
Here are my benchmark results (current version, branchless without SSE, SSE from this PR):
-O2

-O0

Because the non-SSE branchless version seems to perform just as well or better in all the situations I tested, I would rather do that instead of maintaining a separate SSE version. I'll go ahead and make that PR right away because it's so easy.
Thanks for calling my attention to this!

Part of me is disappointed (but not surprised...) that the compiler misses such a basic transform. The other part is glad we managed to weed out an essentially free change by putting on some compiler-tinted glasses, I guess. Good stuff!
I'll close this PR now.


return 404 on /api/messages and /api/inlets/default endpoints

Return 404 instead of 405 on /api/messages and /api/inlets/default endpoints
since "not found" is treated as "error" by curl and maybe other programs
( PR related to https://github.com/muety/telepush/issues/52 → #52 )

Thanks for this! I found an even more elegant way to accomplish this and pushed the fix.

( Danke @muety  , und grüße nach KA ..  ich wünschte andere würden auch so reagieren :+1:  )


Can't get d410 to work with vision board

I have purchased a d410
and a   vision board. I can't seem to get the latest fw updater to see it or my realsense app from seeing it... The errors i am getting respectively are:
connected devices:
 17/08 15:52:20,486 ERROR [3069240080] (types.h:313) set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No buffer space available
RealSense error calling rs2_create_device(info_list:0xcfc570, index:0):
    set_xu(...). xioctl(UVCIOC_CTRL_QUERY) failed Last Error: No buffer space available

Waiting for RealSense device connection.
terminate called after throwing an instance of 'rs2::invalid_value_error'
  what():  hwmon command 0x10( 0 0 0 0 ) failed (response -844431340= unknown)
Aborted

Any ideas ?
Thanks

Hi @GrubbyHalo   May I first ask the questions below, please:

Have you connected the Vision Processor D4 board and and the D410 Depth Module Kit board together with a rigid interposer board or with a flexible interposer cable?

If you have successfully joined the two boards together with an interposer mechanism, have you calibrated the camera afterwards?

What computer / computing device is the camera attached to (PC, Raspberry Pi, Nvidia Jetson, etc)

If you are using the librealsense SDK on Linux, did you build the SDK from source code or build it from Debian packages?

Hi @MartyG-RealSense
The Rigid interposer is being used
W.r.t. the calibrating, I can't run any software to calibrate the camera's as they don't get recognised by the realsense-viewer etc..
I have only connected this to a Raspberry pi. However I have other vision boards and camera modules thad DO contain the IR projector that do work... It just seems like the module without the IR projector does'nt work.
The realsense SDK was built from source.. again, I have other camera's that do work on this rig but not the one i recently purchased that does not contain the IR projector...
Regards

The interposer part number confirms that you have the correct part.
Can you confirm please that the two boards are fully seated in their 50 pin connectors on the rigid interposer board, and that the Vision Processor D4 board is on the lower white connector and the D420 module on the upper connector?
The lack of an IR projector should not make a difference to whether the camera works successfully as the projector is a separate component from the IR imaging sensors on the depth module board.

Hi @MartyG-RealSense
Yes the modules are correctly seated
I managed to update the firmware on the vision boards buy plugging a camera module (450) into the vision board (That was the only way i could update it)
After I did this, the camera was recognised by my own custom software but bombed out after a minute as it had not yet recieved any frames from the module. I updated the realsense SDK to the latest version and all the tools and examples also don't receive any frames..

Is the D420 now at least able to be detected correctly by the RealSense Viewer in its options side-panel, even if the depth streaming does not work when enabled?

I get no frames received in the realsense viewer

Can you open the Viewer's debug log by left-clicking on the small upward triangle in the bottom corner and provide an image of the log when you have No Frames Received on the depth stream, please.

Here we go

It seems like the issue might have been a faulty transposer. After swapping it out it seems to work.

Excellent news that you found a likely cause, @GrubbyHalo - thanks for the update!


HBASE-23245 : MutableHistogram constructor changes and provide Histog…

…ramImpl maxExpected as long

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 19s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:yellow_heart:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

:blue_heart:
mvndep
0m 33s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 47s
master passed

:green_heart:
compile
0m 32s
master passed

:green_heart:
checkstyle
0m 27s
master passed

:green_heart:
shadedjars
5m  7s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 29s
master passed

:blue_heart:
spotbugs
0m 34s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
0m 58s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 13s
Maven dependency ordering for patch

:green_heart:
mvninstall
6m  0s
the patch passed

:green_heart:
compile
0m 33s
the patch passed

:green_heart:
javac
0m 33s
the patch passed

:green_heart:
checkstyle
0m 22s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
5m 13s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m 38s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 29s
the patch passed

:green_heart:
findbugs
1m 12s
the patch passed

_ Other Tests _

:broken_heart:
unit
0m 25s
hbase-metrics in the patch failed.

:green_heart:
unit
0m 40s
hbase-hadoop2-compat in the patch passed.

:green_heart:
asflicense
0m 21s
The patch does not generate ASF License warnings.

55m 51s

Reason
Tests

Failed junit tests
hadoop.hbase.metrics.impl.TestHistogramImpl

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/787

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux aef1ab85b255 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-787/out/precommit/personality/provided.sh

git revision
master / c58e80fbe6

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/1/artifact/out/patch-unit-hbase-metrics.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/1/testReport/

Max. process+thread count
215 (vs. ulimit of 10000)

modules
C: hbase-metrics hbase-hadoop2-compat U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 34s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 34s
Maven dependency ordering for branch

:green_heart:
mvninstall
6m 11s
master passed

:green_heart:
compile
0m 38s
master passed

:green_heart:
checkstyle
0m 29s
master passed

:green_heart:
shadedjars
5m 17s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 30s
master passed

:blue_heart:
spotbugs
0m 33s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
0m 56s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 14s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 29s
the patch passed

:green_heart:
compile
0m 31s
the patch passed

:green_heart:
javac
0m 31s
the patch passed

:green_heart:
checkstyle
0m 23s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
5m  1s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m 36s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 28s
the patch passed

:green_heart:
findbugs
1m  9s
the patch passed

_ Other Tests _

:green_heart:
unit
0m 24s
hbase-metrics in the patch passed.

:green_heart:
unit
0m 36s
hbase-hadoop2-compat in the patch passed.

:green_heart:
asflicense
0m 21s
The patch does not generate ASF License warnings.

55m 32s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/787

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 7779bd2287ba 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-787/out/precommit/personality/provided.sh

git revision
master / c58e80fbe6

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/2/testReport/

Max. process+thread count
258 (vs. ulimit of 10000)

modules
C: hbase-metrics hbase-hadoop2-compat U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

:blue_heart:
reexec
1m 19s
Docker mode activated.

_ Prechecks _

:green_heart:
dupname
0m  0s
No case conflicting files found.

:green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

:green_heart:
@author
0m  0s
The patch does not contain any @author tags.

:green_heart:
test4tests
0m  0s
The patch appears to include 1 new or modified test files.

_ master Compile Tests _

:blue_heart:
mvndep
0m 33s
Maven dependency ordering for branch

:green_heart:
mvninstall
5m 45s
master passed

:green_heart:
compile
0m 31s
master passed

:green_heart:
checkstyle
0m 24s
master passed

:green_heart:
shadedjars
5m  4s
branch has no errors when building our shaded downstream artifacts.

:green_heart:
javadoc
0m 29s
master passed

:blue_heart:
spotbugs
0m 33s
Used deprecated FindBugs config; considering switching to SpotBugs.

:green_heart:
findbugs
0m 56s
master passed

_ Patch Compile Tests _

:blue_heart:
mvndep
0m 13s
Maven dependency ordering for patch

:green_heart:
mvninstall
5m 34s
the patch passed

:green_heart:
compile
0m 32s
the patch passed

:green_heart:
javac
0m 32s
the patch passed

:green_heart:
checkstyle
0m 22s
the patch passed

:green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

:green_heart:
shadedjars
5m  0s
patch has no errors when building our shaded downstream artifacts.

:green_heart:
hadoopcheck
17m 18s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 or 3.1.2.

:green_heart:
javadoc
0m 28s
the patch passed

:green_heart:
findbugs
1m  9s
the patch passed

_ Other Tests _

:green_heart:
unit
0m 25s
hbase-metrics in the patch passed.

:green_heart:
unit
0m 36s
hbase-hadoop2-compat in the patch passed.

:green_heart:
asflicense
0m 21s
The patch does not generate ASF License warnings.

54m  2s

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/787

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 3f45b244c335 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:24:09 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-787/out/precommit/personality/provided.sh

git revision
master / c58e80fbe6

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/3/testReport/

Max. process+thread count
248 (vs. ulimit of 10000)

modules
C: hbase-metrics hbase-hadoop2-compat U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-787/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

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

This message was automatically generated.

Please review @enis @elliottneilclark

Please review @enis @elliottneilclark

Please review @saintstack

If no further concerns we can merge and backport this.


Content Suggestion: NAME OF CONTENT TO BE ADDED

Link to Content: https://noderunners.network/
Briefly Describe Content: Dutch Noderunners Community (Bitcoin Only)
Suggested Section: idk... is there a community section? (think meshtadels) Or maybe under Learning?

Addendum:
I think it would be nice to add a communities section.. For when Twitter and such finally kick us off.

Is this site really Bitcoin Only? I see Pomp shilling NFTs lol

Eugh, that is no good. Sorry about that. Let me send this feedback to them and see what the response is. Will report back. Sorry about this.

They just host allot of podcasts and are def. anti shitcoin and bitcoin only.
It's about 66 peeps now in that community. So its hard to get stuff organized.
If there is anything they should declare on the site to make the above clear, let me know and I'll start poking them :)
Sent with ProtonMail Secure Email.
------- Original Message -------
On Monday, January 31st, 2022 at 2:40 PM, wiz @.***> wrote:

Is this site really Bitcoin Only? I see Pomp shilling NFTs lol
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

I'll pass it on to them.
Thanks Wiz.
I don't condone shitcoining.
Sent with ProtonMail Secure Email.
------- Original Message -------
On Saturday, February 12th, 2022 at 11:58 AM, wiz @.***> wrote:

Not sure what you mean. If they have videos that promote altcoins and NFTs then it's not Bitcoin Only.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


New option to specify default selected pane.

Focus option related to #84
Here is idea. -f is came from "focus".
-f  <expression>
    Specify pane selected by default.
        FP -- first pane
        LP -- Last pane
        BP -- Biggest pane
        SP -- Smallest pane

For example
# Select biggest pane
$ xpanes -f BP A B C D

# Select first pane
$ xpanes -f 0 A B C D

# Select 1 before last index pane.
$ xpanes -f 'NP - 1' A B C D

If anyone is interested in this feature, please add any reactions to this comment 👍
If it earns many reactions ( or I could earn donation), I may work on it.
I am not confident that this feature is worth implementing or not.


offline migration tool

etcd has a live rolling upgrade policy that generally supports X.(N).* to X.(N-1).* upgrades. But, in cases where a user might have an old version of etcd (say 2.0.0), doesn't want to roll through a large number of releases (say to 2.5.0), and can withstand an outage we should provide an offline migration tool that can be ran on every machine and then the cluster can be brought back up.
This would require a few things:

[ ] A test set of older versions of etcd WAL/snap directories. Perhaps stored in git or a tool that can generate old versions.
[ ] A new tool, perhaps etcd offline-migrate, that could migrate from 2.0 WAL/snap directories to the current version.
[ ] Documentation on how to use this tool and how it differs from the live upgrade tool.

Without this tool users are rather stuck in having to do N*machines number of upgrades to use the latest and best version of etcd. With this tool they will have an easier experience getting onto the latest release.

cc @crawford

+1

It seems that no one is really interested enough to implement it. On the other side, for etcd3 the snapshot is already decoupled with WAL and has version attached. We now should support snapshot recover across version in etcd3. So I am wondering if we should just close this issue.
/cc @philips @heyitsanthony @gyuho

Closing. Will reopen if anyone is still interested in working on this for etcd2.


[BUG] Apparently not compatible with Aether Reborn

Description:
Trying to start Industrial Revolution with Aether Reborn but get a Error message. When Aether Reborn is removed everything works fine.
crash-2022-02-15_17.03.26-client.txt
Steps to Reproduce:

Put both in a modpack.

Technical Information:

Minecraft: 1.18.1
Fabric API: 0.12.12
Industrial Revolution: 1.13.6-BETA
Modpack: Custom

Logs:

(https://pastebin.com/TS7AQM3H)

Now compatible with the new version of Aether Reborn


Fix _print_signature() for verbose=True

Fix the following error:
[/usr/local/lib/python3.10/dist-packages/dspy/teleprompt/signature_opt.py](https://localhost:8080/#) in _print_signature(self, predictor)
     96                 signature = predictor.extended_signature1
     97             # print(f"i: {signature.instructions}")
---> 98             # print(f"p: {list(signature.fields().values())[-1].json_schema_extra['prefix']}")
     99             print()
    100

TypeError: 'dict' object is not callable

for Signature Optimizer example. Also, compiled_prompt_opt = teleprompter.compile(cot, devset=devset, eval_kwargs=kwargs) should be changed to compiled_prompt_opt = teleprompter.compile(cot_baseline, devset=devset, eval_kwargs=kwargs)

Thanks @Winston-503 ! Looks like this matches the same fix as #547 which is now merged :). Feel free to close if that's correct!

Yes, looks like it, thanks.


Plus-Minus HackerRank

Description
Code added for Plus-Minus problem in C++
Fixes #2043
Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@ravikr126 please review the PR under label LGM-SOC


[QUESTION] Any alternatives to this tool?

https://github.com/knqyf263/pet
...
ctrl + r
...

I've just made a fully portable alternative written in Rust, no dependencies required.
https://github.com/lasantosr/intelli-shell


[EXEMPLE] sendMediaGroup exemple

Hello,
Everything is working very well except sendMediaGroup I can't find a good way.
I would like to send a bunch of 2-3 images but never working, always a conflict between with the media type
So if someone can give me an example. I am under symfony 5.x

Hello,
I apologize for the late reply
Has your problem been resolved?

Hi,
Do not apologize, i feel lucky someone reply. Even late.
I didn't solve so I put on side for the moment.
I think I will have new try this week

Can you please share your controller or codes


Show conditions of sale

This is one of two required pull requests for conditions of sale. The other is here: https://github.com/artsy/eigen/pull/2599 This is a WIP because we still need to scope the /conditions-of-sale route to only condition of sale links from Emission components (we'll add a query string to avoid other links to /conditions-of-sale being presenting modally).
Work tracked against PURCHASE-60.

Fails

:no_entry_sign:

No CHANGELOG added.

  Generated by :no_entry_sign: dangerJS

Looks great!


Add SC-per-Location Axiom

This commit adds the Sequential Consistency Per Location axiom(https://docs.nvidia.com/cuda/parallel-thread-execution/index.html#sc-per-loc-axiom) which is missing in the model. We add a litmus test from issue(https://github.com/NVlabs/mixedproxy/issues/4). If the Program Order (PO) relation removed from cause_base relation which makes the model roll back to ptx-v6.0 (proxy-less version), this test shows the SC-per-Location axiom is missing.

I agree that if po is taken back out of cause_base, we need SC-per-location.  But given that po is now included in cause_base, isn't SC-per-location redundant?

I don't fully see if this axiom is redundant or not.
I understand that now po-loc pairs in the generic proxy are also part of roxy-preserved-cause-base. This together with irreflexive ((rf | fr); cause) as axiom-Causality might allow to derive some more information, but I don't see how to infer they cannot form a cycle when making the union to morally strong communication (rf+fr+co) pairs.
Even if this is redundant, I think it is a matter of taste between being simple and being explicit. The documentation still explicity mentions this axiom, so I don't see why the formal model should opt for being simple. Personally, I dislike the fact that one could simply modify the definition of cause-base and this would have "hidden" implications.
The formal model has other situations like this. E.g., it uses
pred causality {
  irreflexive[optional[com].cause]
}

which includes co. The documentation and the proxy-less model only refer to rf and fr. I have the feeling that adding co might not have semantic implications (due to the coherence axiom), but I was still planning to open a PR about that one (I wanted first to see if I could find a test showing a problem or some "proof" that there are indeed no semantic differences).

I would be very interested in any concrete litmus tests you might be able to find that would help us distinguish cases like these.  We try to do some sanity checking and model checking as we refactor, but the model has become complex enough that it's entirely possible that cases have slipped through.
Alternatively, if you convince yourselves the changes are indeed sound/redundant, then that would be interesting too.  And yes, I agree it turns into a matter of taste at that point, but if we prove everything is equivalent then there is no contradiction in everyone having their own preferences :)


Show Window resolution size when creating layouts in Fancy Zones

📝 Provide a description of the new feature
Small request to display the zone sizes when creating or modify new layouts in the Fancy Zone editor. It will help when creating new zones to ensure they meet a certain size.
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
The expected behavior would be to have the option to display the resolution of the zone in the upper left-hand corner of each zone and have the resolution change when the zone is being resized. There can be an option in the FancyZone settings to enable this feature.
If you'd like to see this feature implemented, add a 👍 reaction to this post.

@tejones-intel
it will be available in 0.33 (see https://github.com/microsoft/PowerToys/pull/9449)
Closing as duplicate of https://github.com/microsoft/PowerToys/issues/9366


Document improve: use .cargo/config.toml to set env

This way has serval benefits, for example.

IDE syncing support
support relative path than can be work everywhere
repository embeded configuration

config.toml look like below.
[env]
FFMPEG_PKG_CONFIG_PATH = { value = "target/vcpkg/installed/x64-linux/lib/pkgconfig", relative = true }

useful links:
.cargo/config.toml
section detail
thread on stackoverflow

Thanks for your information. I'll enhance the doc later.

If the configuration of environment variables is done in this way during compilation, how can different platforms and architectures be supported?

Currently, [env] in config.toml does not support specifying os and arch.
https://github.com/rust-lang/cargo/issues/10273
https://github.com/rust-lang/cargo/issues/10789

You can use feature link_system_ffmpeg which will use pkg-config to find the ffmpeg https://github.com/CCExtractor/rusty_ffmpeg/blob/1c6a1f58355cdd22248f534f32b6bc143f8ffde4/build.rs#L409-L411 and set
[env]
PKG_CONFIG_PATH_x86_64-unknown-linux-gnu = { value = "target/vcpkg/installed/x64-linux-release/lib/pkgconfig", relative = true }

PKG_CONFIG_PATH_x86_64-apple-darwin = { value = "target/vcpkg/installed/x64-osx-release/lib/pkgconfig", relative = true }
PKG_CONFIG_PATH_aarch64-apple-darwin = { value = "target/vcpkg/installed/arm64-osx-release/lib/pkgconfig", relative = true }

On Windows, set
[env]
# Only Windows uses vcpkg linking.
VCPKG_ROOT = { value = "target/vcpkg", relative = true }
VCPKGRS_TRIPLET = { value = "x64-windows-static-release" }


/etc/resolv.conf points to private name servers

While running up a cluster-lab imaged pi to be a dhcp server, I noticed that the resolv.conf points to private nameservers in Germany.
I know that the expected usecase is for the cluster-lab hosts to have dhcp provide them with their IP/name resolution data, but on the off chance that someone is either exploring (or a serious edge case like a travelling cloud-in-a-box), would it make sense to have it point by default to the google public nameservers (<IP_ADDRESS> and <IP_ADDRESS>)?

@aetherical The Cluster Lab does not change nameservers. Is it maybe the IP of your own router?

On 2016-01-06 11:10, Mathias Renner wrote:

@aetherical [1] The Cluster Lab does not change nameservers. Is it
maybe the IP of your own router?
--
Reply to this email directly or view it on GitHub [2].

Links:
[1] https://github.com/aetherical
[2]
https://github.com/hypriot/cluster-lab/issues/15#issuecomment-169372364

When I mount the freshly flash'd image, /etc/resolv.conf has the
following contents:
Hetzner Online AG installimage
nameserver config
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
Then nslookup returns:
$ nslookup <IP_ADDRESS>
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53
Non-authoritative answer:
<IP_ADDRESS>.in-addr.arpa	name = ns1-coloc.hetzner.de.
Authoritative answers can be found from:
I had written earlier BC (Before Coffee) and wasn't precisely clear.
Here's another test (admittedly from a conference, I can vpn into the
house and paranoia check if people think there is value):
$ nslookup

server <IP_ADDRESS>
Default server: <IP_ADDRESS>
Address: <IP_ADDRESS>#53
prep.ai.mit.edu
;; connection timed out; no servers could be reached
^C
$ nslookup
server <IP_ADDRESS>
Default server: <IP_ADDRESS>
Address: <IP_ADDRESS>#53
prep.ai.mit.edu
Server:		<IP_ADDRESS>
Address:	<IP_ADDRESS>#53

Non-authoritative answer:
prep.ai.mit.edu	canonical name = ftp.gnu.org.
Name:	ftp.gnu.org
Address: <IP_ADDRESS>
Note above that the nameserver in the images /etc/resolv.conf is not
reachable...
Matt

Thanks
I found the part in our SD image creation script.
It is a corner case. Normally the /etc/resolv.conf will be rewritten by connecting to a LAN with a DHCP server configured to deliver DNS servers.
But we will pay attention to this issue in the next releases of our images.
I close this issue but you can reopen it if needed.

@firecyberice Do we need a test for this? :smile:


offline adapters to sync offline data with remote ?

How to write the offline sync logic using getit and not riverpod?

What have you tried?

i have tried the offline initialisation in the docs. But it is in riverpods. How to use the offline retry provider in getit and not riverpods or provider?
This is the sample of code i found in the docs.
final initializerProvider = FutureProvider((ref) async {
// initialize FD
await ref.container.refresh(repositoryInitializerProvider.future);
// initialize other services
// retry offline events
final sub = ref.listen(offlineRetryProvider, (, __) {});
// close offline retry subscription
ref.onDispose(() {
_sub.close();
});
});


Support rust-bindgen in Cargo.tml?

I think it would be nice if a project that uses rust-bindgen can include it in their Cargo.tml, for example:
[build-dependencies.bindgen]
git = "https://github.com/servo/rust-bindgen"
features = ["llvm_stable"]
But one problem is that then Cargo does not build ./bindgen binary, but only lib.rs.  I'm not sure what's would be a proper way of solving this problem yet though.

I think the idea for this is to use the library and invoke it from build.rs. Could you elaborate what kind of use case could require the binary?
I'm not sure cargo support binaries in build-dependencies out of the box :/

Yes right, but actually, I guess we don't need the binary and just can call the library directly from build.rs...


Update running_a_poc.md

suggest analyze only experiment

🚀 Deployed on https://65b01e6ca528132e15d0bfb7--cozy-fox-0defec.netlify.app


Add a retry decorator

Here's the original use case from @liiight on Gitter:

I'm implementing retries in my code, which is done using a package called retry. basically its a super simple decorator, just catch exception, and call the decoratored func until conditions apply, nothing fancy
when using with uplink, I'm implementing it in the layer above uplink, i.e, the usage of it. i was wondering if it's possible to do it via uplink itself
i.e, catch an error and retry the called method

This is similar to #71

Here's my original reply. It would be nice if Uplink supported usage of existing decorators for retry, rate-limiting, etc. At the moment, this is not possible (because of how consumer methods are implemented). It might be worth it to consider if and how we should support this usage.

An additional use case for this sort of functionality is when auth tokens have a short expiry, on some (admittedly not great) API's I catch an expired token as an exception, refresh it and then try the original request again. Being able to simplify that interaction would be awesome.

@bendews You should look into https://github.com/oauthlib/oauthlib and https://requests-oauthlib.readthedocs.io/en/latest/
@prkumar It's kind of a deviation of this issue, but passing custom sessions (like how requests oauthlib implements oauth) would be very cool

@liiight - the client constructor argument of a Consumer subclass supports requests.Session subclasses (like the OAuth2Session class from requests-oauthlib library). So, although I haven't tried it out, the following should work already:
from requests_oauthlib from OAuth2Session

github_session = OAuth2Session(client_id)
github = GitHub(base_url=BASE_URL, client=github_session)

Is this what you're talking about?

Exactly, thanks for pointing that out.
@bednews you should check out the links I gave because requests oauthlib can be refresh token internally (when using oauth obviously)

@liiight I would have had far less sleepless nights if they were OAuth compliant, trust me on that! 😁

The retry decorator should be available in v0.8.0. After I merge #132, I'll create a new alpha release v0.8.0a1 in case you wan't to try it out before the official release. To install this alpha release with pip, do:
$ pip install --pre uplink

Here's some documentation for the decorator. (I'll also be soon adding a section to the quickstart about this feature). Notably, this decorator can be used like the other decorators, such as @timeout or @headers:
class GitHub(uplink.Consumer):
    @uplink.retry(max_attempts=2)
    @uplink.get("/users/{user}")
    def get_user(self, user):
        pass

If you get the chance to try it out, let me know if you also have any feedback!
CC: @bendews @liiight

I haven't had a chance to play with this but the interface look great.
One suggestion though,  you could use native ptrhon status code enum for the retry conditions: https://docs.python.org/3/library/http.html#http.HTTPStatus

@liiight - Thanks for the suggestion! I'll add a way to retry after certain status codes.


can i has update for latest spelunky 2 version?

please

There hasn't been an Overlunky update for 1.20.0j because it already works in the latest version, just like the badge in the readme says. We're not going to make a new release just to bump the version number.


Compatibility issue with aws-java-sdk:1.10.77 and httpclient:4.5.3

Calls to com.amazonaws.http.AmazonHttpClient.execute() may fail with the following exception:
java.lang.IllegalStateException: Socket not created by this factory
	at org.apache.http.util.Asserts.check(Asserts.java:34) ~[httpcore-4.4.6.jar:4.4.6]
	at org.apache.http.conn.ssl.SSLSocketFactory.isSecure(SSLSocketFactory.java:435) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:186) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:326) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[httpclient-4.5.3.jar:4.5.3]
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[httpclient-4.5.3.jar:4.5.3]
	at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:837) ~[aws-java-sdk-core-1.10.77.jar:?]
	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:607) ~[aws-java-sdk-core-1.10.77.jar:?]
	at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:376) ~[aws-java-sdk-core-1.10.77.jar:?]
	at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:338) ~[aws-java-sdk-core-1.10.77.jar:?]
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:287) ~[aws-java-sdk-core-1.10.77.jar:?]

I'm seeing issues with the aws-java-sdk in one of our extensions and believe that it might affect the S3 extension as well. I haven't yet seen any issues in S3, but it uses similar method calls so the version bump might have introduced lurking issues. The aws-java-sdk extends SSLSocketFactory as SdkTLSSocketFactory, and when the factory is asked to create a socket and calls into the incompatible httpclient, it returns a standard Socket instead of an SSLSocket which causes the assertion in isSecure to fail.
Similar issues between aws-java-sdk and httpclient have been reported by others:

https://groups.google.com/forum/#!topic/dropwizard-user/5-zjo5N32Tg
https://github.com/aws/aws-sdk-java/issues/1032

I'd like to revert to httpclient:4.5.1 and httpcore:4.4.3 unless there's a particular reason these need to be upgraded.

WORKS LIKE A CHARM!!!!!!!!! :* :* :* :*


Pre-expanded cell & Prevent user to collapse cell.

In short, I want to disable collapse of cell.

Hello @Rashesh-Bosamiya ,
Do you mean that user open the cell and cell is not collapsable?


Sign in with multiple organisations

Exploring options to enable users to belong to multiple organisations, and choose which one they want to sign in with when they sign in.

First quick idea is something like this:

Have added the addresses as hint text as we know that some organisations (well, pharmacies) will have the same name (Boots, Superdrug) so we might need to differentiate them. Could also show ODS code but not sure how familiar users would be with those...
Thoughts @Deepatee @johnrimmer2?


Allow policies for actions on all controllers

Right now there's either a '*' globally for every action and controller, a controller: { '*' } for all actions in one controller and controller: { 'action' }. Why is there no way to specify policies for any controller but a specific action?
module.exports.policies = {
    // Default policy for all controllers and actions
    '*':                ['authenticated'],
    // example global action
    'create':           ['authenticated', 'createdByUser'],
    'update':           ['authenticated', 'updatedByUser'],
    'destroy':          ['authenticated', 'isCreator'],

    // alternative global action declaration
    '*': {
        '*':           ['authenticated'],
        'create':      ['authenticated', 'createdByUser'],
        'update':      ['authenticated', 'updatedByUser'],
        'destroy':     ['authenticated', 'isCreator']
    }
};

Interesting.  It honestly hasn't come up before, but feel free to make a PR to our roadmap, or even better, a PR implementing this feature, and we'll be happy to take a look at it!


Updating max version of Rancher charts

Updating Helm charts in Rancher page.

unassigned meself and add team Helm Yes!  for reviewing the PR


LUCENE-4056: Japanese Tokenizer (Kuromoji) cannot build UniDic dictionary

TL;DR
The current PR attempts to remediate https://issues.apache.org/jira/browse/LUCENE-4056 (Japanese Tokenizer (Kuromoji) cannot build UniDic dictionary)
Description

The current PR builds up upon @johtani's past PR: https://github.com/apache/lucene-solr/pull/935 and attempts to bring the code into a mergeable state, or at least to re-ignite the conversation about building a UniDic dictionary.
Before exporting the current PR, I verified the @johtani's added behavior in the aforementioned PR (plus some changes of my own) by successfully building a number of dictionaries outlined below and posted my findings in the comment: https://github.com/apache/lucene-solr/pull/935#issuecomment-1685887305
Philosophy of changes
I tried to pick up @johtani's added behavior as-is, while minimizing the amount of changes that I added additionally.
To be honest, I do not really like how DictionaryBuilder.DictionaryFormat format is being passed everywhere, as it creates these small decision trees if IPADIC do this else do that. If this PR gets merged, I would be happy to refactor in order to make the code more modular (where possible) and perhaps with a better separation of concerns. But, I defer to the maintainers of the Lucene library on this one. 🙇🏼♀
The commits are fairly atomic and I hope this can make the reviewing experience more easier
Built Dictionaries

unidic-cwj-202302_full (NINJAL)
unidic-cwj-3.1.1-full (NINJAL) (See Caveat below 👇🏼 )
unidic-mecab-2.1.2_src (NINJAL)
mecab-ipadic-2.7.0-20070801

Caveat
RE: Building the unidic-cwj-3.1.1-full:

I had to increase the the length check of the baseForm from 16 to 35
I had to stop throwing an exception for multiple entries of LeftID, which, to be honest I do not understand the full ramifications of. I did print some of the values for the same left IDs instead of throwing when debugging and that's how they look like:Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,連用形-融合], new fullPOSData=[動詞-一般,五段-ガ行,仮定形-融合]
Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,仮定形-融合], new fullPOSData=[動詞-一般,五段-ガ行,連用形-融合]
Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,連用形-融合], new fullPOSData=[動詞-一般,五段-ガ行,仮定形-融合]
Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,仮定形-融合], new fullPOSData=[動詞-一般,五段-ガ行,連用形-融合]
Multiple entries found for leftID=14172: existing=[動詞-一般,五段-バ行,仮定形-融合], new fullPOSData=[動詞-一般,五段-バ行,連用形-融合]
Multiple entries found for leftID=1121: existing=[動詞-一般,五段-ガ行,連用形-融合], new fullPOSData=[動詞-一般,五段-ガ行,仮定形-融合]
Multiple entries found for leftID=1121: existing=[動詞-一般,五段-ガ行,仮定形-融合], new fullPOSData=[動詞-一般,五段-ガ行,連用形-融合]
Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,連用形-融合], new fullPOSData=[動詞-一般,五段-ガ行,仮定形-融合]
Multiple entries found for leftID=4644: existing=[動詞-一般,五段-ガ行,仮定形-融合], new fullPOSData=[動詞-一般,五段-ガ行,連用形-融合]

Some Inflection form values are different for the same leftID, also, why do we have duplicated IDs? ^. Thus, I would value the input of the Subject matter experts here 🙇🏼♀
Building a dictionary
Gradle command
My build command leverages the new Gradle setup and the DictionaryBuilder JavaDoc comment about how to do it:
I added in lucene/analysis/kuromoji/build.gradle a default run task from the Gradle's application plugin, which allows to build a dictionary are as follows. The command should be executed under the root directory lucene, where the gradlew file is.
For example, the following is my command when building unidic-cwj-3.1.1-full dictionary without the NFKD normalization:
./gradlew -p lucene/analysis/kuromoji run --args='unidic "/Users/azagniotov/Downloads/unidic-cwj-3.1.1-full" "/Users/azagniotov/Downloads/unidic-cwj-3.1.1-full/build" "UTF-8" false'

Unit testing
Unfortunately, the current PR does not include unit tests because the built dictionaries files are very big, e.g.: built unidic-cwj-202302_full  connection costs .DAT file is around ~700MB, while the unidic-cwj-3.1.1-full connection costs .DAT file is around ~450 MB . Thus, the following unit tests were added and ran locally on my machine to verify that the built dictionaries can be used at runtime.
I did see there there is a main/gradle/generation/kuromoji.gradle that downloads dictionaries and compiles them, but for now, I resorted not to add changes there (https://github.com/apache/lucene/pull/12517/commits/bc9d2e3bb38d096ad193ce41e46c644b4c5673f9).
I also think a dictionary should be decoupled (this is related to the existing discussion in:

https://github.com/apache/lucene/issues/9860.

The built dictionaries were tested using the following Japanese strings (no particular reason, I just picked these four strings):

"にじさんじ"
"ちいかわ"
"桃太郎電鉄"
"聖川真斗"

The dictionaries metadata  were placed (dictionary after dictionary) under the lucene/analysis/kuromoji/src/resources/org/apache/lucene/analysis/ja/dict and a few unit test cases were added:
Existing default dictionary already included in Lucene
assertAnalyzesTo(analyzerNoPunct, "にじさんじ", new String[] {"に", "じさ", "ん", "じ"}, new int[] {1, 1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "ちいかわ", new String[] {"ちい", "か", "わ"}, new int[] {1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "桃太郎電鉄", new String[] {"桃太郎", "電鉄"}, new int[] {1, 1});
assertAnalyzesTo(analyzerNoPunct, "聖川真斗", new String[] {"聖川", "真", "斗"}, new int[] {1, 1, 1});

Built unidic-cwj-202302_full
I needed to increase memory before running the tests, as the ConnectionCosts.dat is ~700MB: in main/gradle/testing/defaults-tests.gradle#L50
-           value: { -> propertyOrEnvOrDefault("tests.jvmargs", "TEST_JVM_ARGS", isCIBuild ? "" : "-XX:TieredStopAtLevel=1 -XX:+UseParallelGC -XX:ActiveProcessorCount=1") },
+           value: { -> propertyOrEnvOrDefault("tests.jvmargs", "TEST_JVM_ARGS", isCIBuild ? "" : "-XX:MaxDirectMemorySize=2g -XX:TieredStopAtLevel=1 -XX:+UseParallelGC -XX:ActiveProcessorCount=1") },

assertAnalyzesTo(analyzerNoPunct, "にじさんじ", new String[] {"にじ", "さん", "じ"}, new int[] {1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "ちいかわ", new String[] {"ちい", "かわ"}, new int[] {1, 1});
assertAnalyzesTo(analyzerNoPunct, "桃太郎電鉄", new String[] {"桃", "桃太郎", "太郎", "電鉄"}, new int[] {1, 0, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "聖川真斗", new String[] {"聖", "川", "真", "斗"}, new int[] {1, 1, 1, 1});

Built unidic-cwj-3.1.1-full
assertAnalyzesTo(analyzerNoPunct, "にじさんじ", new String[] {"にじ", "さ", "ん", "じ"}, new int[] {1, 1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "ちいかわ", new String[] {"ちい", "かわ"}, new int[] {1, 1});
assertAnalyzesTo(analyzerNoPunct, "桃太郎電鉄", new String[] {"桃太郎", "電鉄"}, new int[] {1, 1});
assertAnalyzesTo(analyzerNoPunct, "聖川真斗", new String[] {"聖", "川", "真斗"}, new int[] {1, 1, 1});

Built unidic-mecab-2.1.2_src
assertAnalyzesTo(analyzerNoPunct, "にじさんじ", new String[] {"にじ", "さん", "じ"}, new int[] {1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "ちいかわ", new String[] {"ちい", "か", "わ"}, new int[] {1, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "桃太郎電鉄", new String[] {"桃", "桃太郎", "太郎", "電鉄"}, new int[] {1, 0, 1, 1});
assertAnalyzesTo(analyzerNoPunct, "聖川真斗", new String[] {"聖", "川", "真", "斗"}, new int[] {1, 1, 1, 1});

Built mecab-ipadic-2.7.0-20070801
 assertAnalyzesTo(analyzerNoPunct, "にじさんじ", new String[] {"に", "じさ", "ん", "じ"}, new int[] {1, 1, 1, 1});
 assertAnalyzesTo(analyzerNoPunct, "ちいかわ", new String[] {"ちい", "か", "わ"}, new int[] {1, 1, 1});
 assertAnalyzesTo(analyzerNoPunct, "桃太郎電鉄", new String[] {"桃太郎", "電鉄"}, new int[] {1, 1});
 assertAnalyzesTo(analyzerNoPunct, "聖川真斗", new String[] {"聖川", "真", "斗"}, new int[] {1, 1, 1});

Hi,
Please give me some time to review.
Please don't add the application plugin. Instead just add a plain java runner task. The result of the project is a library jar, so please don't change this as it could have effects on the resulting maven pom.

@uschindler thank you for also taking a look, in addition to others. Understood. Please allow me a few days to export a commit that would add a plain java runner task instead of the application plugin. Thank you

Please don't add the application plugin. Instead just add a plain java runner task. The result of the project is a library jar, so please don't change this as it could have effects on the resulting maven pom.

Hi @uschindler, I ended up simply reverting the 8d52f66 commit. The current gradle/generation/kuromoji.gradle already contains def recompileDictionary(...) which is used by all the task compileXXXX(..), thus, the task and the application plugin that I added were not necessary, after all.

I can't tell you anything about the internals touched here, so I can't review it from the language specific point of view.
The Gradle changes look fine.

One thing! Have you checked that a simple recompile of the original mecab (gradlew regenerate) produced same files (working copy clean afterwards)?

@uschindler yes: I have rebased from the latest main branch and ran the ./gradlew clean regenerate. The following is the (partial) output:
...
...
> Task :lucene:analysis:nori:compileMecabKo
Download https://bitbucket.org/eunjeon/mecab-ko-dic/downloads/mecab-ko-dic-2.1.1-20180720.tar.gz

> Task :lucene:analysis:kuromoji:compileMecab
Download https://jaist.dl.sourceforge.net/project/mecab/mecab-ipadic/2.7.0-20070801/mecab-ipadic-2.7.0-20070801.tar.gz
Automaton regenerated from dictionary: mecab-ipadic-2.7.0-20070801

> Task :lucene:analysis:nori:compileMecabKo
Automaton regenerated from dictionary: mecab-ko-dic-2.1.1-20180720

BUILD SUCCESSFUL in 39s
127 actionable tasks: 121 executed, 6 up-to-date

I also confirmed that the dictionary files *.dat were regenerated under the lucene/analysis/kuromoji/src/resources/org/apache/lucene/analysis/ja based on the modified date of the files.
@mocobeta What do you think with regards to next steps with this PR? Is there anything I can add?

@uschindler yes: I have rebased from the latest main branch and ran the ./gradlew clean regenerate. The following is the (partial) output:
...
...
> Task :lucene:analysis:nori:compileMecabKo
Download https://bitbucket.org/eunjeon/mecab-ko-dic/downloads/mecab-ko-dic-2.1.1-20180720.tar.gz

> Task :lucene:analysis:kuromoji:compileMecab
Download https://jaist.dl.sourceforge.net/project/mecab/mecab-ipadic/2.7.0-20070801/mecab-ipadic-2.7.0-20070801.tar.gz
Automaton regenerated from dictionary: mecab-ipadic-2.7.0-20070801

> Task :lucene:analysis:nori:compileMecabKo
Automaton regenerated from dictionary: mecab-ko-dic-2.1.1-20180720

BUILD SUCCESSFUL in 39s
127 actionable tasks: 121 executed, 6 up-to-date

I also confirmed that the dictionary files *.dat were regenerated under the lucene/analysis/kuromoji/src/resources/org/apache/lucene/analysis/ja based on the modified date of the files.
@mocobeta What do you think with regards to next steps with this PR? Is there anything I can add?

@azagniotov Sorry, I've not been available for a while. Let me take a look; I will try to find time next week...

Thank you, @mocobeta 🙇🏼

Hi, sorry for my late reply.
I quickly checked the built dictionary size. The latest Unidic is fairly (to me, insanely) large - its total size is 1.6G.
https://clrd.ninjal.ac.jp/unidic/back_number.html#unidic_cwj
The built kuromoji jar with unidic-cwj-3.1.1-full eventually becomes 442M. Besides the size, I think we should consider performance. I'm worried that there can be a significant impact on analysis/indexing speed. Do you have any benchmark result on that?

The built kuromoji jar with unidic-cwj-3.1.1-full eventually becomes 442M. Besides the size, I think we should consider performance. I'm worried that there can be a significant impact on analysis/indexing speed. Do you have any benchmark result on that?

luceneutil has a runAnalyzerPerf.py benchmark, and the nightly script runs it and posts the results here, including Kuromoji.  We could maybe test tokens/sec throughput using that benchy for this PR running on UniDic?  I'm not sure how we would conclude whether it's fast enough since current Kuromoji (main) can't build UniDic.  Maybe we could defer performance testing / optimizing on UniDic to a later issue...

@mocobeta thank you. I have not done any benchmarks, thus, I cannot comment on potential performance implications. One thing that probably be certain that a larger dictionary will require more memory allocated. Btw, have you had a chance to evaluate the correctness of tokenization?
@mikemccand this sounds interesting. It seems like this is a treaded path. How easy/hard will it be to point runAnalyzerPerf.py to the current PR branch?

@mocobeta @johtani  Hello!
I wanted to touch base within the context of the current PR, I am observing an interesting issue creating tokenizer using:

Setting discardCompoundToken as false
Mode.SEARCH
*.dat files generated from unidic-cwj-202302_full:

I no longer see compound token being emitted, but only the short units. For example, when using the the following *.dat files and running a unit test, the tokenization results are as follows:

Default MeCab: 関西国際空港 => "関西", "関西国際空港", "国際", "空港"
unidic-cwj-202302_full: 関西国際空港 => "関西", "国際", "空港"

Is compound token emitting behavior specific to MeCab dictionary in the implementation of Kuromoji / Viterbi?


Ansible support

Hi,
Have you thought of adding support for using Ansible?
Thx

In what manner do you mean?
Currently cmtools.sh is there to install the agents necessary to install CM (configuration management) tools to provision the box.  The boxes themselves are intended to be JEOS (Just Enough OS) to install a configuration management tool.  It is left as an exercise to the reader to wire up packer to provision these JEOS boxes from the OS on up, as we don't want to maintain a bunch of provisioning scripts for all the various configuration management tools.
Since the agent for ansible is openssh-server, I'm not sure what else cmtools.sh needs to do for you to use ansible to provision these boxes.  What else are you thinking that you need?

The scenario I am considering is the ability to run Ansible script inside a freshly installed machine, for provisioning, w/o being connected to a central server.
I guess this is similar to Chef Solo. If you think this is not appropriate for the intended use of BoxCutter, that is ok.
Thanks

Actually there is an option for the chefdk, which is a similar scenario.  Feel free to modify cmtools.sh to install ansible, and test to make sure it works in an image, then submit a pull request and we'll consider moving it to master.

Thx! My bash skills are not that great but I can give it a try.
The recommended approach for Ubuntu is as follows for the latest version)
sudo apt-get install -y software-properties-common
sudo apt-add-repository -y ppa:ansible/ansible
sudo apt-get install -y ansible

Alternatively, it can be done via pip install
sudo install -y python python-pip
sudo pip install ansible

Can you please let me know which approach would be a better fit for boxcutter?
Thx


Create SQL XmlRepository

From @janpieterz on Saturday, October 7, 2017 8:02:51 AM
Would make sense as it's one of the most common shared pieces of infrastructure between multiple servers.
It's mentioned in https://github.com/aspnet/DataProtection/issues/145 but doesn't seem to have been built.
Copied from original issue: aspnet/DataProtection#280

From @blowdart on Friday, October 13, 2017 11:58:42 AM
@muratg It's worth doing, but I think trying to make it generic, or indeed EF model based might be more bother than its worth. A straightforward SQL, with parameterised queries would do it.

From @urbanhusky on Monday, November 27, 2017 12:46:54 AM
I'm trying to implement such a repository and I use EF. I struggle with figuring out how to properly resolve the corresponding DbContext. The context would be registered as scoped in the DI container, but I don't know how the repository is being registered - or if I would have to register it myself.
I do the following:
// Register db context
services.AddDbContext<DataProtectionDbContext>(
    opts =>
    {
        var dpapiMigrationsAssembly = typeof(DataProtectionDbContext).GetTypeInfo().Assembly.GetName().Name;
        opts.UseSqlServer(dpapiConnectionString, b => b.MigrationsAssembly(dpapiMigrationsAssembly));
    });

// configure dpapi
services.AddDataProtection()
    .ProtectKeysWithCertificate(GetCertificate()) // no support for rollover or revocation when using certificate?
    .AddKeyManagementOptions(options => options.XmlRepository = new SqlDatabaseXmlRepository(/* TODO: how to resolve? Repository needs to be an instance and any DI would be for *right now* */))

I have an EntityFrameworkCore implementation of this along with tests and a sample ready for review. Please let me know if it is ok to submit a pull request.

@dansward thanks for your PR to kick off the conversation on this subject.
We would be interested in taking a well-written PR to create this feature. At minimum, we would hope to see an implementation that satisfies the following:

There is a way for users to create the expected database schema.
There is a way for users to configure the repository by providing a connection string
There is a way for users to change between database providers, such as SQL Server or Postgres.

These requirements are pretty high-level, so let's have a conversation about the options for implementing these. One option includes using Entity Framework Core, but that is not the only alternative.

Done in https://github.com/aspnet/DataProtection/pull/303 and https://github.com/aspnet/DataProtection/pull/323. Thanks @dansward!


address suggested change.

Address minor suggested change.

@TahaTesser please review and merge this whenever you've a chance.


Update _touch.py

Add keyword 'click a point' to click on a specific point using given opt(x,y)
Raise exception error if appium can't perform click on that point.

Thanks!