failed to install bcbio???

....
Successfully built bcbio-nextgen
Installing collected packages: bcbio-nextgen
Successfully installed bcbio-nextgen-1.0.8
Installing data and third party dependencies
Traceback (most recent call last):
File ".../bcbio/anaconda/bin/bcbio_nextgen.py", line 36, in
from bcbio import install, utils, workflow
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 25, in
from bcbio import broad, utils
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/broad/init.py", line 17, in
from bcbio.broad import picardrun
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/broad/picardrun.py", line 9, in
from bcbio.distributed.transaction import file_transaction, tx_tmpdir
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/distributed/transaction.py", line 16, in
from bcbio.log import logger
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/log/init.py", line 9, in
import logbook
ImportError: No module named logbook
Traceback (most recent call last):
File "bcbio_nextgen_install.py", line 255, in
main(parser.parse_args(), sys.argv[1:])
File "bcbio_nextgen_install.py", line 41, in main
subprocess.check_call([bcbio["bcbio_nextgen.py"], "upgrade"] + _clean_args(sys_argv, args, bcbio))
File ".../python/2.7.9-2/anaconda/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['.../bcbio/anaconda/bin/bcbio_nextgen.py', 'upgrade', '--tooldir=.../', '--genomes', 'hg19', '--aligners', 'star']' returned non-zero exit status 1

Thanks for the report and apologies about the issue. I'm not positive how it got in a state without the logbook dependency, but you should be able to fix with:
bcbio_conda update -c conda-forge -c bioconda logbook

and then re-run. Please let us know if you run into any other problems.

Where should I run/add this command? It cannot be found. Thanks for your reply.

bcbio_conda should be created as a symlink to the conda installation within bcbio within the bin directory of whatever you specified as --tooldir. If things didn't cleanly install/update, you can use the conda inside of bcbio directly:
bcbio/anaconda/bin/conda install -c conda-forge -c bioconda logbook

Hope this helps.

anaconda/bin/conda install -c conda-forge -c bioconda logbook
Solving environment: done
Package Plan
environment location: /scratch/cas/wchen/programs/bcbio/anaconda
added / updated specs:
- logbook
The following packages will be downloaded:
package                    |            build
---------------------------|-----------------
openssl-1.0.2n             |                0         3.5 MB  conda-forge
logbook-1.0.0              |           py27_0         223 KB  bioconda
conda-4.3.34               |           py27_0         507 KB  conda-forge
certifi-2018.1.18          |           py27_0         143 KB  conda-forge
ca-certificates-2018.1.18  |                0         140 KB  conda-forge
------------------------------------------------------------
                                       Total:         4.5 MB

The following NEW packages will be INSTALLED:
ca-certificates: 2018.1.18-0      conda-forge
logbook:         1.0.0-py27_0     bioconda

The following packages will be UPDATED:
certifi:         2018.1.18-py27_0             --> 2018.1.18-py27_0 conda-forge
openssl:         1.0.2l-0                     --> 1.0.2n-0         conda-forge

The following packages will be DOWNGRADED:
conda:           4.4.11-py27_0                --> 4.3.34-py27_0    conda-forge

Proceed ([y]/n)? vi note
Invalid choice: vi note
Proceed ([y]/n)? y
Downloading and Extracting Packages
openssl 1.0.2n: #################################################################################################################################################################################################################################################################################################### | 100%
logbook 1.0.0: ##################################################################################################################################################################################################################################################################################################### | 100%
conda 4.3.34: ###################################################################################################################################################################################################################################################################################################### | 100%
certifi 2018.1.18: ################################################################################################################################################################################################################################################################################################# | 100%
ca-certificates 2018.1.18: ######################################################################################################################################################################################################################################################################################### | 100%
Preparing transaction: done
Verifying transaction: done
Executing transaction: done
Segmentation fault (core dumped)
Thank you for your help!

Segmentation fault (core dumped)

I tried again, this time it finished.

Now it complains lack of dependencies of  gffutils, pybedtools, cyvcf2. After installed these similar to logbook. There is still problem:
All requested packages already installed.
Requirement already satisfied: fabric in ..../bcbio/anaconda/lib/python2.7/site-packages
Requirement already satisfied: paramiko<3.0,>=1.10 in ..../bcbio/anaconda/lib/python2.7/site-packages (from fabric)
Requirement already satisfied: cryptography>=1.5 in ..../bcbio/anaconda/lib/python2.7/site-packages (from paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: pynacl>=1.0.1 in ..../bcbio/anaconda/lib/python2.7/site-packages (from paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: pyasn1>=0.1.7 in ..../bcbio/anaconda/lib/python2.7/site-packages (from paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: bcrypt>=3.1.3 in ..../bcbio/anaconda/lib/python2.7/site-packages (from paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: idna>=2.1 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: asn1crypto>=0.21.0 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: packaging in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: six>=1.4.1 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: setuptools>=11.3 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: enum34 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: ipaddress in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: cffi>=1.4.1 in ..../bcbio/anaconda/lib/python2.7/site-packages (from cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: pycparser in ..../bcbio/anaconda/lib/python2.7/site-packages (from cffi>=1.4.1->cryptography>=1.5->paramiko<3.0,>=1.10->fabric)
Requirement already satisfied: bcbio-nextgen==1.0.8 in ..../bcbio/anaconda/lib/python2.7/site-packages (from -r https://raw.github.com/chapmanb/bcbio-nextgen/master/requirements.txt (line 1))
Installing data and third party dependencies
Traceback (most recent call last):
File "..../bcbio/anaconda/bin/bcbio_nextgen.py", line 36, in
from bcbio import install, utils, workflow
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 26, in
from bcbio.pipeline import genome, version
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/genome.py", line 17, in
from bcbio.pipeline import alignment
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/alignment.py", line 12, in
from bcbio.ngsalign import (bowtie, bwa, tophat, bowtie2, minimap2,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 14, in
from bcbio.variation import sentieon
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/sentieon.py", line 20, in
from bcbio.variation import bamprep, bedutils, joint, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/joint.py", line 24, in
from bcbio.variation import bamprep, gatkjoint, genotype, multi, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/genotype.py", line 16, in
from bcbio.variation import (gatk, gatkfilter, germline, multi,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/germline.py", line 8, in
import cyvcf2
File "..../bcbio/anaconda/lib/python2.7/site-packages/cyvcf2/init.py", line 1, in
from .cyvcf2 import (VCF, Variant, Writer, r_ as r_unphased, par_relatedness,
File "init.pxd", line 163, in init cyvcf2.cyvcf2
ValueError: numpy.dtype has the wrong size, try recompiling. Expected 88, got 96
Traceback (most recent call last):
File "..../bcbio/anaconda/bin/bcbio_nextgen.py", line 36, in
from bcbio import install, utils, workflow
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 26, in
from bcbio.pipeline import genome, version
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/genome.py", line 17, in
from bcbio.pipeline import alignment
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/alignment.py", line 12, in
from bcbio.ngsalign import (bowtie, bwa, tophat, bowtie2, minimap2,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 14, in
from bcbio.variation import sentieon
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/sentieon.py", line 20, in
from bcbio.variation import bamprep, bedutils, joint, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/joint.py", line 24, in
from bcbio.variation import bamprep, gatkjoint, genotype, multi, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/genotype.py", line 16, in
from bcbio.variation import (gatk, gatkfilter, germline, multi,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/germline.py", line 8, in
import cyvcf2
File "..../bcbio/anaconda/lib/python2.7/site-packages/cyvcf2/init.py", line 1, in
from .cyvcf2 import (VCF, Variant, Writer, r_ as r_unphased, par_relatedness,
File "init.pxd", line 163, in init cyvcf2.cyvcf2
ValueError: numpy.dtype has the wrong size, try recompiling. Expected 88, got 96
Traceback (most recent call last):
File "bcbio_nextgen_install.py", line 255, in
main(parser.parse_args(), sys.argv[1:])
File "bcbio_nextgen_install.py", line 41, in main
subprocess.check_call([bcbio["bcbio_nextgen.py"], "upgrade"] + _clean_args(sys_argv, args, bcbio))
File "...../python/2.7.9-2/anaconda/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['..../bcbio/anaconda/bin/bcbio_nextgen.py', 'upgrade', '--tooldir=..../bcbio', '--genomes', 'hg19', '--aligners', 'star']' returned non-zero exit status 1

Tried this:
bin/bcbio_nextgen.py upgrade -u development
Traceback (most recent call last):
File "bin/bcbio_nextgen.py", line 36, in
from bcbio import install, utils, workflow
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 26, in
from bcbio.pipeline import genome, version
File ".../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/genome.py", line 17, in
from bcbio.pipeline import alignment
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/pipeline/alignment.py", line 12, in
from bcbio.ngsalign import (bowtie, bwa, tophat, bowtie2, minimap2,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/ngsalign/bwa.py", line 14, in
from bcbio.variation import sentieon
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/sentieon.py", line 20, in
from bcbio.variation import bamprep, bedutils, joint, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/joint.py", line 24, in
from bcbio.variation import bamprep, gatkjoint, genotype, multi, vcfutils
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/genotype.py", line 16, in
from bcbio.variation import (gatk, gatkfilter, germline, multi,
File "..../bcbio/anaconda/lib/python2.7/site-packages/bcbio/variation/germline.py", line 8, in
import cyvcf2
File "..../bcbio/anaconda/lib/python2.7/site-packages/cyvcf2/init.py", line 1, in
from .cyvcf2 import (VCF, Variant, Writer, r_ as r_unphased, par_relatedness,
File "init.pxd", line 163, in init cyvcf2.cyvcf2
ValueError: numpy.dtype has the wrong size, try recompiling. Expected 88, got 96

Sorry about the continued problems. The error you're encountering is that the version of numpy installed with your bcbio system is incorrect. Running:
/path/to/bcbio/anacondai/bin/conda install -c conda-forge 'numpy=1.12*'

should resolve it.
More generally, this is a lot of manual updates and installs which shouldn't be necessary on a clean install/upgrade so I feel like something more general is going wrong. Could you provide a bit more detail on your install? Is it a new install or upgrade? What processes have you run so far for the installation? This might help us understand more about the general problems contributing to all these issues. Thanks for the help debugging.

anaconda/bin/conda install -c conda-forge 'numpy=1.12*'
Solving environment: failed
UnsatisfiableError: The following specifications were found to be in conflict:

cpat -> bx-python -> numpy=1.9 -> mkl==11.3.3
numpy=1.12
Use "conda info " to see the dependencies for each package.

How can I clean up everything and reinstall? Thanks!

Saw this:
We don't have an automated remove method but the full installation is isolated to the install directory, so just doing a rm -rf /path/to/bcbio will remove bcbio, the tools, and associated data. Hope this works for your needs.
Tried reinstallation similar to this:
wget https://raw.github.com/chapmanb/bcbio-nextgen/master/scripts/bcbio_nextgen_install.py
python bcbio_nextgen_install.py path/bcbio --tooldir=path/bcbio
--genomes hg19--aligners bwa --aligners star
STILL ERRORS:
Installing data and third party dependencies
Traceback (most recent call last):
File "path/bcbio/anaconda/bin/bcbio_nextgen.py", line 36, in
from bcbio import install, utils, workflow
File "path/bcbio/anaconda/lib/python2.7/site-packages/bcbio/install.py", line 25, in
from bcbio import broad, utils
File "path/bcbio/anaconda/lib/python2.7/site-packages/bcbio/broad/init.py", line 17, in
from bcbio.broad import picardrun
File "path/bcbio/anaconda/lib/python2.7/site-packages/bcbio/broad/picardrun.py", line 6, in
import pysam
File "path/bcbio/anaconda/lib/python2.7/site-packages/pysam/init.py", line 5, in
from pysam.libchtslib import *
ImportError: /lib64/libk5crypto.so.3: symbol krb5int_buf_len, version krb5support_0_MIT not defined in file libkrb5support.so.0 with link time reference
Traceback (most recent call last):
File "bcbio_nextgen_install.py", line 260, in
main(parser.parse_args(), sys.argv[1:])
File "bcbio_nextgen_install.py", line 44, in main
subprocess.check_call([bcbio, "upgrade"] + _clean_args(sys_argv, args))
File "path/python/2.7.9-2/anaconda/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['path/bcbio/anaconda/bin/bcbio_nextgen.py', 'upgrade', '--tooldir=path/bcbio', '--genomes', 'hg19', '--aligners', 'bwa', '--aligners', 'star', '--data']' returned non-zero exit status 1

Thanks for helping debug and sorry for the continued issues. When re-installing does path/bcbio contain a pre-existing anaconda installation from another bcbio installation? If so, removing path/bcbio/anaconda would let you do a clean install using the same data files but creating a new anaconda environment with the issues in your previous one. Hope this helps.

I removed the whole bcbio folder that contained everything from previous bcbio installation, before the automated reinstallation.

Thanks for following up and confirming that we're dealing with a clean install. From the errors I'm seeing it looks like something is problematic about your system crypto libraries, specifically /lib64/libk5crypto.so.3. This is a long thread I found which tries to debug some of this and might be helpful:
http://kerberos.996246.n3.nabble.com/version-krb5support-0-MIT-not-defined-td22574.html
What type of system are you running this on? Is it possible to avoid including the problematic libraries in your shared library path so anaconda can use it's own internal libraries rather than picking these up?
Sorry to not know exactly what is going on but hope this helps some.


Add SharedImages by @crspybits

[x] Project URL: https://github.com/crspybits/SharedImages
[x] Update contents.json instead of README
[x] One project per pull request
[x] Avoid iOS or open-source in description as it is assumed
[x] Use this commit title format if applicable: Add app-name by @github-username
[x] Use approved format for your entry

edited

Thank you!

And you! :).


Silverpeak Module

Silverpeak Module Outputs Missing
Silverpeak modules outputs were missing and caused errors when trying to run code for Solarity. We were getting errors for each route that referenced the Silverpeak nic's.
Example

Error: Module 'route_10_0_0_0': "lan_nic_id" is not a valid output for module "aws_prod_silverpeak"

Solution
This has been temporarily solved by creating a new branch. Branched named dev_silverpeak_outputs_19.3 in this repo will have the output code below which will fix the issue.
output "lan_nic_id" {     value = ["${aws_network_interface.lan0_nic.*.id}"] }
This is only a temporary fix because the branch could easily be deleted and cause the problem again. We have a couple of options to fix this more long term.

Delete and recreate tag for v0.19.3 with the dev_silverpeak_outputs_19.3 branch code. not ideal because it will be a random version that has the necessary code that will not exist before or after the point in time.

Look into creating a fork that we could reference that would remain in place until we updated the Solarity code to Terraform v0.12.

Next Steps

[ ] Update outputs code for Terraform v0.12 in terraform-modules to include the outputs code above.

[ ] Create fork or recreate tag as a temporary fix until Solarity is running Terraform v0.12 code.

This has been temporarily fixed by creating a new branch to reference. We will leave this fix in place until we upgrade the solarity code to TF 12, at which point we can update the TF 12 code on the latest version with the necessary output.


fix: 🐛 DA-290 Replace signing identity with account identity while fetching account permissions

Description
Currently the signing Identity was used to get the permissions that an Account had as a Permissioned Account. This change replaces the use of signingIdentity with the corresponding identity associated with the Account and then uses that to fetch the permissions. Also, throws an error if the Account is not associated with any Identity
Breaking Changes
🧨 account.getPermissions can throw if there is no Identity associated with the Account
JIRA Link
DA-290
Checklist
❌  Updated the Readme.md (if required) ?

Code looks OK to me, but I don't understand why we need to make this change.

Not always does one have a signingIdentity (like it would get called in REST API or even in case when SDK is initialized without a signingManager). getPermissions should be able to provide permissions irrespective whether there is signing Identity or not.

:tada: This PR is included in version 14.0.0-alpha.13 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 14.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 14.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add version info for the plugin

Since it's likely the plugin will iterate faster than the Godot releases, we should include versioning information to allow users to differentiate between successive releases.

@timoschwarzer The current version can be 1.0.0 since that's its first(!) release as a standalone plugin.
In addition, we can use gradle's setProperty for the archivesBaseName property to update the generated .aar filename automatically.

Should the version be dependent of Godot's version? Or on Godot's Android plugin version (v1)?
If different Godot versions might require different plugin versions, I think this should be featured somehow in the version string.

I'd opt for <godot version>-<plugin revision for that godot version>, e.g. 3.2.2-stable-1, 3.2.2-stable-2 and so on. That makes it clear which version to use for the users and guarantees API compatibility between the plugin and Godot for a specific version.
You might have seen that I created releases named after the Godot version. E.g. plugin version 3.2.2-stable was built against the 3.2.2-stable godot-lib AAR.

I'd suggest maybe leaving out the -stable suffix, even on the main Godot repo we don't tag pre-release versions which are not formal releases.
The main issue with a numbering like 3.2.2-stable-1 or 3.2.2-1 (aside from not being very readable), is that it would force us to make new releases for every Godot release, even if the current state of the plugin might be compatible with Godot 3.2.3, 3.2.4 or possibly even 4.0.

Another way I could imagine is having a separate versioning scheme (e.g. semver) and documenting the compatible Godot versions in the release description. What do you think about that?

Another way I could imagine is having a separate versioning scheme (e.g. semver) and documenting the compatible Godot versions in the release description. What do you think about that?

I prefer that approach! Since this plugin is also dependent on the latest stable version of the Google Android Billing library, trying to include all that information in the version name will make it unreadable.
Adopting a separate semver versioning scheme will remove that issue.

Then I'll do that tomorrow :)


 Please use
:hand:   go install golang.org/x/tools/cmd/goimports
:hand: to enable import cleanup.

Fixed by https://github.com/knative-sandbox/kn-plugin-admin/pull/42.
@zhi-gang-sun would you please help to close it! Thanks!


Publish to pypi

Please consider publishing to pypi so users don't have to build from source

Thank you for your suggestion. This is something that I've had planned since the start of this project. I can't say when this will happen but the goal is to have this published on pypi.


make: ensure make fmt is run with -s flag

Another attempt at https://github.com/lightningnetwork/lnd/pull/2092. The previous one would fail travis because of the removal of XARGS and GOLIST (used by testing_flags.mk).
Linting will fail if code is not formatted with the -s flag, so make
sure we always use it when formatting.

I mean it touches the .pb.go files, but makes no changes because they are apparently already go fmt'ed

Ah, I see. Probably okay as long as they are not actually changed.


Plain list selection item callback not work

Library Version:
core:2.2.0
Describe the Bug:
After setting negative button, select listener not called ..
Code:
MaterialDialog(activity).show {
    listItems(items = arrayListOf("Test1", "Test2")) { dialog, index, text ->
        Log.v("MaterialDialog", "$index  ::  $text")
    }
    title(R.string.change_language)
    negativeButton(R.string.cancel) {
        it.dismiss()
    }
}

@aelahmar this is working as intended. The positive button is responsible for calling the listener.

If there is no negative button, the listener called on selection ..
In my case user either select or cancel dialog? why the extra step to confirm his selection?

MaterialDialog(activity).show {
    listItems(items = arrayListOf("Test1", "Test2"),waitForPositiveButton = false) { dialog, index, text ->
        Log.v("MaterialDialog", "$index  ::  $text")
    }
    title(R.string.change_language)
    negativeButton(R.string.cancel) {
        it.dismiss()
    }
}

I did it by setting waitForPositiveButton = false ..


Simple example to toggle content

A simple example for swapping content with animations would be helpful for me. The example for VelocityComponent works for toggle fading a single component in and out:
<VelocityComponent animation={{ opacity: this.state.showSubComponent ? 1 : 0 }} duration={500}>
  <MySubComponent/>
</VelocityComponent>

But I'm not sure how to proceed if I want to swap one component for another with a fadeout/fadein?

I have a crude toggle working. The problem is that the incoming html takes space while the outgoing html fades out. I can set display:'none' for the "leave" animation, or I suppose I could use absolute positioning. Is there any way to delay and not mount the incoming html/component until the outgoing html/component fades out?
Anyway, here's the code:
var MyComponent = React.createClass({

	getInitialState: function() {
		return {showNewComponent:false}
	},

	handleClick: function() {
		this.setState({showNewComponent: !this.state.showNewComponent});
	},

	render: function () {
		var enterAnimation = {
			animation: 'fadeIn',//{opacity: 1},
			duration: 800,
			//delay: 500
		};

		var leaveAnimation = {
			animation: 'fadeOut',//{opacity: 0},
			duration: 800,
			style: {display: 'none'}
		};

		return (

				<button onClick={this.handleClick}>Toggle</button>

				<VelocityTransitionGroup enter={enterAnimation} leave={leaveAnimation}>
					{this.state.showNewComponent ? undefined :
INITIAL COMPONENT
 }
				</VelocityTransitionGroup>

				<VelocityTransitionGroup enter={enterAnimation} leave={leaveAnimation}>
					{this.state.showNewComponent ?
NEW COMPONENT
 : undefined }
				</VelocityTransitionGroup>

		);
	},
});

Take a look at LoadingCrossfadeComponent in the demo code for how to switch an element to absolute as it leaves so that it doesn't take up space.
Putting a delay on the enter animation may work, but the danger there is additional stuttering of the height. (I suspect it would only be feasible if you can let the container collapse down to 0 height.)

You can put them all in the same transition group, if you like:
                <VelocityTransitionGroup enter={enterAnimation} leave={leaveAnimation}>
                    {this.state.showNewComponent ? undefined :
INITIAL COMPONENT
 }
                    {this.state.showNewComponent ?
NEW COMPONENT
 : undefined }
                </VelocityTransitionGroup>


Make kubectl-validate compatible with WASM

Currently it's not possible to use kubectl-validate and build a wasm module because of dependencies that bring a reference to etcd (that has non supported syscalls).
GOOS=js GOARCH=wasm go build -o ./main.wasm ./main.go

package command-line-arguments
        imports sigs.k8s.io/kubectl-validate/pkg/cmd
        imports k8s.io/apiextensions-apiserver/pkg/apiserver
        imports k8s.io/apiextensions-apiserver/pkg/registry/customresource
        imports k8s.io/apiserver/pkg/registry/generic
        imports k8s.io/apiserver/pkg/storage/storagebackend/factory
        imports go.etcd.io/etcd/client/pkg/v3/transport
        imports golang.org/x/sys/unix: build constraints exclude all Go files in /Users/charled/Documents/dev/eddycharly/kubectl-validate/vendor/golang.org/x/sys/unix

I think there's no reason why it should not be possible, probably requires to change packages organisation a little bit though to avoid the package level reference to etcd ?

Yeah this is mainly due to our reliance on apiextensions-apiserver to validate CRDs. THey ahve recursive schemas which the k8s validators choke on.
If we remove the ability to validate CRDs by schema and just skip/error on CRDs then this requirement can be removed.

@alexzielenski you suggest to remove the CRD support ?

IIRC code like this was part of the problem return rest.BeforeCreate(strat, request.WithNamespace(context.TODO(), ""), obj)

@alexzielenski do you suggest removing CRD support ?

I am waffling about it. It is the only resource we cheat for validation on and it would be a lot of work to support its recursive schema. I wonder if users would miss it

ike this was part of the problem return rest.BeforeCreate(strat, request.WithNamespace(context.TODO(), ""), obj)

Ah, if that is the case that can also be quite easily removed & replicated within our own codebase

/remove-lifecycle stale
/lifecycle frozen

Took another look at this. We rely on a lot more code than just ValidateCustomResourceDefinition inside apiextensions-apiserver. Unfortunately itd be quite a large refactor to move them out of that package upstream, and I would rather keep the dependency to ensure the code says the same.


Fixed text colour in mobile view

#436
Description
fixed text of navbar items colour
before

After

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[X] I have updated the documentation accordingly.

@dinxsh please check and merge PR under GSSOC'24

okay sure

@dinxsh check now


mov2mov error...

After updating, ControlNet and adetailer are running, but only mov2mov is not running..
Is this error only happening to me?

me too...

僕もです。


[CARBONDATA-1316] drop partition

Drop partition function

please describe your modification

Refer to below guidance for illustration of drop partition function:
https://github.com/apache/carbondata/blob/master/docs/partition-guide.md#drop-a-partition

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/13/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/121/

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/19/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/755/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/139/

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/13/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/201/

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/78/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/833/

Build Failed with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/79/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/202/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/80/

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/203/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/834/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/835/

Build Success with Spark 1.6, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/83/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/206/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/838/

LGTM


kmc-solid: Mark abort, exit, and _Exit as diverging

This PR marks these functions as diverging (fn (...) -> !) for the *-kmc-solid_* target, so that they are in line with the other targets (e.g., unix).

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

@bors r+

:pushpin: Commit c5c8f5934e92987d56a62793bdd3cc0a0e09172b has been approved by Amanieu

:hourglass: Testing commit c5c8f5934e92987d56a62793bdd3cc0a0e09172b with merge 70e49b693617ebc5f47b6d9b9c22d726e91200c4...

:sunny: Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13
Approved by: Amanieu
Pushing 70e49b693617ebc5f47b6d9b9c22d726e91200c4 to master...


Error after update to V4.5.21

Since the Sailfish update from 4.5.19 to 4.5.21, the button cannot be activated. It no longer asks for the password. The following error message is displayed in the journal:
Error starting org.nephros.sailfish.x10iiicamera
I deleted the app via chum and reinstalled it. Unfortunately, this did not help.
Ronny

Unfortunately yes.

Here is the output:
[root@Xperia10III defaultuser]# systemctl restart org.nephros.sailfish.x10iiicamera.service [root@Xperia10III defaultuser]# systemctl status -l --no-pager org.nephros.sailfish.x10iiicamera.service ● org.nephros.sailfish.x10iiicamera.service - Xperia 10III Triple Camera Toggle    Loaded: loaded (/usr/lib/systemd/system/org.nephros.sailfish.x10iiicamera.service; static; vendor preset: enabled)    Active: active (exited) since Mon 2023-07-24 17:43:11 CEST; 10s ago      Docs: https://docs.sailfishos.org/Support/Help_Articles/Camera/#multiple-cameras-of-xperia-10-iii   Process: 19285 ExecStart=/bin/bash -c /usr/bin/sed -i 's/multiCameraEnable=.*$/multiCameraEnable=TRUE/' $CAMXFILE && /usr/bin/pkill -f $CAMPROVIDER (code=exited, status=0/SUCCESS)  Main PID: 19285 (code=exited, status=0/SUCCESS)
Jul 24 17:43:11 Xperia10III systemd[1]: Starting Xperia 10III Triple Camera Toggle... Jul 24 17:43:11 Xperia10III systemd[1]: Started Xperia 10III Triple Camera Toggle.
Strangely enough, the restart activates the button. But it cannot be deactivated by clicking on it.


Community links blocked on mobile

On mobile, I cannot click the community links because they are covered with an invisible div:

(Visible on desktop on a narrow screen.)

Just a note for the above PR.
The problem was not an invisible div. The overlapping element was the container of the help/upcoming/contribute links, which has a top padding. Converting that to margin and zeroing the padding pushed the container down enough to allow the links to be interactive and maintained the initial look.

Wow! Thank you for fixing this, what an awesome contribution!

Going to keep this open until we deploy the fix.


Description is either outdated or the program sources are as sources have not been updated in a while

Describe the bug

The Description is either outdated or the program is as some sources you say are in the program aren't. Many anime sites like darkanime and itsaturday don't even exist anymore. The description says that choices like a2zanime exists while only 4anime, anitube, anime8, animebinge, gurminder, animedaisuki, animeflix, animeflv, animefreak, animefree, animefrenzy, animekisa, animetake, animeonline360, animeout, animerush, animesimple, animesuge, animevibe, animixplay, darkanime, dbanimes, erai-raws, egyanime, fastani, itsaturday, justdubs, kickass, kissanimex, kisscartoon, 9anime, nyaa, putlockers, ryuanime, subsplease, twist.moe, tenshi.moe, vidstream, voiranime and vostfree exists.
To reproduce

anime dl "Fullmetal Alchemist" -q 1080p -p a2zanime

LOG

Updated. We did have a2zanime, but it was removed in #327 and it somehow escaped us all to update the README to reflect that. Thanks for the catch.

Updated. We did have a2zanime, but it was removed in #327 and it somehow escaped us all to update the README to reflect that. Thanks for the catch.


Update event-hubs-kafka-connect-tutorial.md

Learn Build status updates of commit 9cb9c61:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/event-hubs/event-hubs-kafka-connect-tutorial.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off

In review.
The PR Review team is reviewing your PR. As part of this process, we might make minor changes.
Don't make any commits during this review. When we finish, we’ll tag the PR creator in a comment if we find issues we can't address.
#label:"review-in-progress"
#assign: @jborsecnik


Create user personas for the map dashboard

User personas are an abstraction of the groups of people who we would expect to use a tool like this. I think it would be helpful to make concrete a list of these personas as a first design step to prioritize our features. Groups like admin (us), law students, student groups, community groups, informed citizens, etc — and their expected needs and goals in using a tool like this. Thoughts?

I came up with a few interview questions that I'm planning on asking some of my friends who might use a tool like this:

How do you like to stay civically active at the local level?
What local issues do you care about? Which issues do you follow closely?
How do you stay up to date about local issues?
How do you communicate with others about local issues?
When have you felt "heard" by your local government? When have you felt "unheard"?
How knowledgeable would you say you are about how local government works?
Have you ever attended/watched town meeting/city council/board of selectmen/etc meetings?
How well do you know your local politicians? Have you ever met, written, called, DMed, commented, liked, followed?
How knowledgeable would you say you are about how the state legislature works?
How knowledgeable would you say you are about bills currently being considered by the state?
Have you ever attended/watched the state legislature in session?
What parts of the government do you care about learning more about?

Please feel free to offer feedback or suggest additional questions.

I came up with a few interview questions that I'm planning on asking some of my friends who might use a tool like this:

How do you like to stay civically active at the local level?
What local issues do you care about? Which issues do you follow closely?
How do you stay up to date about local issues?
How do you communicate with others about local issues?
When have you felt "heard" by your local government? When have you felt "unheard"?
How knowledgeable would you say you are about how local government works?
Have you ever attended/watched town meeting/city council/board of selectmen/etc meetings?
How well do you know your local politicians? Have you ever met, written, called, DMed, commented, liked, followed?
How knowledgeable would you say you are about how the state legislature works?
How knowledgeable would you say you are about bills currently being considered by the state?
Have you ever attended/watched the state legislature in session?
What parts of the government do you care about learning more about?

Please feel free to offer feedback or suggest additional questions.


Why is taxonID currently not required in observations.csv?

It seems like taxonID is not required according to the documentation (https://tdwg.github.io/camtrap-dp/data/#observations), but it seems like that would be a required field, no? Maybe I'm missing something?
https://github.com/inbo/camtraptor/pull/145#discussion_r952965544

@Rafnuss I just remember why that is. 😄  Observations can contain blank, unclassified, vehicle "observations" that would not have any taxonomic information associated with it, which is why we can't make it a required term. When it does concern an observation of an animal, it is expected (but not validated) that taxonID is provided.


Feature Set - CTA does not obey open in new window checkbox

This is actually working by design it seems. If the link style is "external" it opens in a new window. Anything else it does not.
While awkward that it doesn't obey the modal dialog, it may be correct as far as usability and accessibility goes. Worth discussion.


Unable to connect to Turtlebot4

Hello,
Following the basic setup tutorials, I configured TB4.
However, while connecting the Raspberry Pi to my school WiFi network (which typically consists of SSID, username and password), since there is no provision for username in the command sudo wifi.sh -s '<WIFI_SSID>' -p '<WIFI_PASSWORD>' -r <REGULATORY_DOMAIN> && sudo reboot, i skipped username.
Further, I connected create3 in the same process as the Raspberry Pi.
After successful completion of installation steps, I observed the IP address on Turtlebot4 is still <IP_ADDRESS>.
I see the solid green light if I lift the robot. Also, I could see Cyan. I attached the images.
I am not sure if turtlebot4 is not properly configured to my school network.
Now, could you please help to reconfigure and connect Turtlebot4 to different network.

This issue is being closed due to inactivity. If you are still experiencing the issue, feel free to reopen this ticket when you are ready to continue the troubleshooting process.

I have the same problem, but when I follow (https://turtlebot.github.io/turtlebot4-user-manual/setup/basic.html#recovering-the-raspberry-pi), the terminal outputs "No route to host"

@HiWiQiao how did you manage to solve the problem? i have the same issue and it is blocking my work


Develop

:tada: This PR is included in version 1.5.1 :tada:
The release is available on:

Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


adding earning history table

Integration test logs

Logs
Add passing integration test logs here

Example query results

Results
Add example SQL query results here (please include the input queries as well)

Thanks @macleanpinto for working on this!
I have a few suggestions for this table that we'd like to see implemented before merging please.
Not found / zero rows
The table should return zero rows when the symbol is not found like the other tables do:
> select * from finance_earning_history where symbol = 'CRAP'
Error: rpc error: code = Internal desc = list call getEarningHistory failed with panic runtime error: index out of range [0] with length 0
>
>
> select * from finance_quote where symbol = 'CRAP'
+--------+------------+----------------------+---------------------+-----+----------+-----------------------------+------------------------------+-----+----------+-------------+--------
| symbol | short_name | regular_market_price | regular_market_time | ask | ask_size | average_daily_volume_10_day | average_daily_volume_3_month | bid | bid_size | currency_id | exchang
+--------+------------+----------------------+---------------------+-----+----------+-----------------------------+------------------------------+-----+----------+-------------+--------
+--------+------------+----------------------+---------------------+-----+----------+-----------------------------+------------------------------+-----+----------+-------------+--------
>

**Symbol exists, but has no earnings should return zero rows**

select * from finance_earning_history where symbol = 'WBK'
Error: interfaceToColumnValue failed for column 'quarter': cannot convert 0 to a time.Time

**Add documentation**

All tables must be documented in `docs/tables/table_name.md`. Please see existing tables for good examples. These will then automatically show up on the hub site.

**Use column types to match the data**

Please use `timestamp` and `double` columns instead of text for the data. It will work better in Postgres queries and will allow more definition in documentation etc to match the data type. Please see code below for an example implementation.

**Use private function names**

Use `getEarningHistory` instead of `GetEarningHistory`. Please see code below for an example implementation.

**Use eps in table name instead of column names?**

Would `finance_eps_history` be a better name than `finance_earning_history`? I'm not sure, but looking at the data perhaps it would be? With that change, you could remove the `eps_` prefix from the column names?

To help with the above, here is a suggested update to the `table_finance_earning_history.go` file to use as a starting point:

package finance
import (
"context"
"github.com/macleanpinto/yahoo-finance/earning"
"github.com/turbot/steampipe-plugin-sdk/grpc/proto"
"github.com/turbot/steampipe-plugin-sdk/plugin"
"github.com/turbot/steampipe-plugin-sdk/plugin/transform"

)
func tableFinanceEarningHistory(ctx context.Context) *plugin.Table {
return &plugin.Table{
Name:        "finance_earning_history",
Description: "Earning history for the most recent four quarters.",
List: &plugin.ListConfig{
Hydrate:    getEarningHistory,
KeyColumns: plugin.SingleColumn("symbol"),
},
Columns: []*plugin.Column{
{Name: "symbol", Type: proto.ColumnType_STRING, Hydrate: symbolString, Transform: transform.FromValue(), Description: "Symbol for the earnings."},
{Name: "quarter", Type: proto.ColumnType_TIMESTAMP, Transform: transform.FromField("Quarter.Fmt"), Description: "Quaterly earnings announcement date."},
{Name: "eps_estimate", Type: proto.ColumnType_DOUBLE, Transform: transform.FromField("EpsEstimate.Raw"), Description: "Estimated earnings per share."},
{Name: "eps_actual", Type: proto.ColumnType_DOUBLE, Transform: transform.FromField("EpsActual.Raw"), Description: "Actual earnings per share."},
{Name: "eps_difference", Type: proto.ColumnType_DOUBLE, Transform: transform.FromField("EpsDifference.Raw"), Description: "Difference between actual and estimated earning per share."},
{Name: "eps_suprise_percent", Type: proto.ColumnType_DOUBLE, Transform: transform.FromField("SurprisePercent.Raw").Transform(convertFloat64ToPercent), Description: "Earning per share suprise as a percentage."},
},
}
}
func convertFloat64ToPercent(_ context.Context, input *transform.TransformData) (interface{}, error) {
f := input.Value.(float64)
return 100 * f, nil
}
func getEarningHistory(ctx context.Context, d *plugin.QueryData, _ *plugin.HydrateData) (interface{}, error) {
quals := d.KeyColumnQuals
symbol := quals["symbol"].GetStringValue()
q, err := earning.GetEarningHistory(symbol)
if err != nil {
plugin.Logger(ctx).Error("finance_earning_history.getEarningHistory", "query_error", err)
return nil, err
}
for _, v := range q {
d.StreamListItem(ctx, v)
}
return nil, nil
}

Hope that helps. Happy to discuss on the Steampipe Slack or answer questions here.


New package: Cocobolo.BatchPatch version 2<IP_ADDRESS>.17

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #171678

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@wingetbot run

Manually validate again.
11:11:16 D:\...\winget-pkgs  [issues/171678 ≡] 4ms pwsh> winget.exe download -m .\manifests\c\Cocobolo\BatchPatch\2<IP_ADDRESS>.17\ --skip-dependencies
已找到 BatchPatch [Cocobolo.BatchPatch] 版本 2<IP_ADDRESS>.17
此应用程序由其所有者授权给你。
Microsoft 对第三方程序包概不负责，也不向第三方程序包授予任何许可证。
已跳过依赖项。
正在下载 https://batchpatch.com/downloads/batchpatch/?tmstv=1725538662
  ██████████████████████████████  1.99 MB / 1.99 MB
已成功验证安装程序哈希
已下载安装程序: D:\Dragon1573\Downloads\Cocobolo.BatchPatch_2<IP_ADDRESS>.17\BatchPatch_2<IP_ADDRESS>.17_X86_portable_en-US.zip

@wingetbot run

@wingetbot run

[!NOTE]
Close with unknown reason: https://github.com/microsoft/winget-pkgs/labels/Validation-Hash-Verification-Failed
There might be some weird behavior of the server. Everything goes normal as expected in manual validation.

Automatic Validation ended with:

Installation failed with exit code -1978335215
2024-09-07 04:14:38.836 [CLI ] Package hash verification failed. SHA256 in manifest [5f9e6496ee2bc661ab3463b26c74c2301661873ba5582719890561484d13a3b2] does not match download [77cb42c354116eb9eb2baaef5687baaebffc676394111ba83727a1a152b9e558]

Automated error analysis suggests -1978335215 may mean The installer files hash does not match the manifest
(Automated response - build 895.)


Please remove the beta note from the v1.0 Documentation page

Please refer the error in the documentation

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

ID: 31ace01e-5ee0-f37f-4fc5-2bb6a96ba41c
Version Independent ID: 988d3a03-bc1b-ab5f-7f5d-6be1846bfae7
Content: taskFileAttachment: createUploadSession - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/taskfileattachment-createuploadsession.md
Product: outlook
Technology: microsoft-graph
GitHub Login: @avijityadav
Microsoft Alias: MSGraphDocsVteam

Closing as this has been fixed. Thanks.


[Review] Update list assets in Oraichain Network

Summary by Oraichain

Chores :

Updated list assests for Oraichain Network ( tokens , images )

@JeremyParish69 Hello. I come from Oraichain. Please review for me :3


Proof of Laplace Polars Expr

Current dependencies on/for this PR:

main

PR #763

PR #765

PR #767

PR #769

PR #771

PR #862

PR #863

PR #865

[!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

#888  👈
#829 : 2 other dependent PRs (#854 , #890 )
#819
#868 : 1 other dependent PR (#864 )
#797 : 1 other dependent PR (#824 )
#847
#1454
#795
#1167
#769 : 1 other dependent PR (#771 )
#767
#765
#763
#917 : 1 other dependent PR (#921 )
#916
#907
#874
#705
#754
#704
#703
#753
#702
main

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

Join @PaulineMauryL and the rest of your teammates on  Graphite

Closing this as the implementation has significantly diverged.


Support cert-manager based deployments

What would you like to be added:
Enable cert-manager enabled clusters to use this webhook
This request is to support webhook certificates via a https://github.com/jetstack/cert-manager ca injector. This will benefit the webhook in a few ways, the certificate will no longer need to be generated by the application itself, removing a dependency on the CSR based upstream k8s certificate manager (where issues do arise like the metrics changes in https://github.com/aws/amazon-eks-pod-identity-webhook/pull/92). Additionally, it will remove the need for secret and CSR RBAC, as cert-manager will inject the CA to the webhook at deploy time. The certificate will get rotated in place when it expires
Why is this needed:
The "standard" set by kubebuilder/controller-runtime is cert manager based certificates as it simplifies certificate management
https://book.kubebuilder.io/cronjob-tutorial/cert-manager.html#deploying-the-cert-manager
Both cert-manager based webhooks and CSR webhooks can both be supported at the same time with feature flags and updated RBAC. We run this today internally by updating RBAC, creating a cert-manager.io Certificate, setting the cert-manager.io/inject-ca-from annotation on the webhook, disabling the in cluster flag, and manually setting tls-cert and tls-key to be a mounted secret volume. But I think the server needs to reload the certificate, like in https://github.com/kubernetes-sigs/controller-runtime/pull/421/files or else when the cert expires, the server will still use the certificate it loaded at startup, not the live certificate on the filesystem
EDIT: The certwatcher may get exported in https://github.com/kubernetes-sigs/controller-runtime/issues/1292

@mcristina422 Can you please share steps how did it?

Thanks @mcristina422 for hints. Below yaml for how you can deploy amazon-eks-pod-identity-webhook with cert-manager
kind: Deployment
metadata:
  name: pod-identity-webhook
  namespace: kube-system
spec:
  replicas: 1
  selector:
    matchLabels:
      app: pod-identity-webhook
  template:
    metadata:
      labels:
        app: pod-identity-webhook
    spec:
      serviceAccountName: pod-identity-webhook
      containers:
        - name: pod-identity-webhook
          image: amazon/amazon-eks-pod-identity-webhook:2c44edc
          imagePullPolicy: Always
          command:
            - /webhook
            - --in-cluster=false
            - --namespace=kube-system
            - --service-name=pod-identity-webhook
            - --annotation-prefix=eks.amazonaws.com
            - --token-audience=sts.amazonaws.com
            - --logtostderr
          volumeMounts:
            - name: cert
              mountPath: "/etc/webhook/certs"
              readOnly: true
      volumes:
        - name: cert
          secret:
            secretName: pod-identity-webhook-cert
---
apiVersion: cert-manager.io/v1alpha3
kind: Certificate
metadata:
  name: pod-identity-webhook
  namespace: kube-system
spec:
  secretName: pod-identity-webhook-cert
  commonName: "pod-identity-webhook.kube-system.svc"
  dnsNames:
  - "pod-identity-webhook"
  - "pod-identity-webhook.kube-system"
  - "pod-identity-webhook.kube-system.svc"
  - "pod-identity-webhook.kube-system.svc.local"
  isCA: true
  duration: 43800h
  renewBefore: 8760h
  issuerRef:
    name: selfsigned
    kind: ClusterIssuer
---
apiVersion: admissionregistration.k8s.io/v1beta1
kind: MutatingWebhookConfiguration
metadata:
  name: pod-identity-webhook
  namespace: kube-system
  annotations:
    cert-manager.io/inject-ca-from: kube-system/pod-identity-webhook
webhooks:
  - name: pod-identity-webhook.amazonaws.com
    failurePolicy: Ignore
    clientConfig:
      service:
        name: pod-identity-webhook
        namespace: kube-system
        path: "/mutate"
    rules:
      - operations: [ "CREATE" ]
        apiGroups: [""]
        apiVersions: ["v1"]
        resources: ["pods"]

In case you are interested in reviewing the implementation - https://github.com/kubernetes-sigs/controller-runtime/pull/1441 hopefully this fulfils your needs as well.

Wanted to bump this issue as well thank @mcristina422 and @avdhoot for the cert-manager integration above! I wanted to ask in mean the time how people are getting around the issue of the cert being loaded on start-up? Deleting the webhook pod with a job periodically? I see the above configuration is setting a long duration for the cert.

On our clusters we use a shorter duration cert and we automatically terminate our EKS nodes weekly, so pods will get rolled out frequently enough to get new certificates. A job to rollout the deployment makes sense to me!
Long term the plan should be to refactor this webhook to use this package to automatically reload the certificate

Long duration for the cert is short term fix for cert rotation issue If the
app does not reload when cert change.
On Thu, May 13, 2021 at 12:28 AM Michael Cristina @.***>
wrote:

On our clusters we use a shorter duration cert and we automatically
terminate our EKS nodes weekly, so pods will get rolled out frequently
enough to get new certificates. A job to rollout the deployment makes sense
to me!
Long term the plan should be to refactor this webhook to use this
https://github.com/kubernetes-sigs/controller-runtime/pull/1441 package
to automatically reload the certificate
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws/amazon-eks-pod-identity-webhook/issues/94#issuecomment-840022942,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKA6Q4JBUHGDAUYWW6EASLTNLFVLANCNFSM4T34I6LQ
.

This unrelated PR might help with the renewal story? https://github.com/aws/amazon-eks-pod-identity-webhook/pull/87

This change adds support for the --external-tls-renewal flag which will make the k8s Secret "readonly", i.e only read but never update it. Instead of having the k8s go-client certificate_manager.Manager renew it via CSR API, it will just try to re-read it from the secret when it is is nearing expiration time.


Possible mistake in JaxRs Whiteboard Specification

https://docs.osgi.org/specification/osgi.cmpn/8.0.0/service.jaxrs.html#d0e134849
The properties section mentions a property service.exported.interfaces as required with description Set appropriately to export the Endpoint service using OSGi Remote Services..
ThIs seems to be an copy and waste mistake.

I think we should probably delete the row in the table.

Table caption is also wrong.

This seems to be an copy and waste mistake.

The intent of this is to require that the JaxrsEndpoint services registered by the implementation are "exportable". Specifically if you have a remote services implementation running then the other frameworks in your system should be able to discover the endpoints provided.

But then we should remove the require tag from the line

But then we should remove the require tag from the line

Why? I'm not sure what the disadvantage or overhead is in saying that the implementation must register the service with service.exported.interfaces=org.osgi.service.jaxrs.runtime.JaxrsEndpoint

Just to get it right. Every successful registered resource and application must register this service?
If yes, is that covered by the TCK? I believe not. Because we didnt implemented this in the Jersey Whiteboard 😔. In the end we need to parse the resources and applications for jaxrs annotations as well to get these information as long as jersey does not provide the necessary information.

It seems this also could have been realized using the conditions? So, I would go for the proposed removal.

I am ok with removing the reference to remote services.


Added Whisper support

Hi there, I've added whisper support for a little project of mine. I'm not sure if this clashes with your plans for 2.0 😉
Also maybe adding some lint file would be great for contributes ;)

After changing the test i am not 100% sure how the channel name should be named, i added a prefix just to be sure to not overlap with the actually users channel and to not have a accidental overlaps with something like #happy_grumpy which could be a separate channel.

Hello there!
Thank you very much for this PR, it's a feature that's been requested several times before and I'm glad you've tackled it. I'm going to take a look at this branch and check it out, and then it will be merged in 😄
I haven't had much time over the last year to focus on this project, but I plan to become more involved again, starting with the new v2 branch. You're also right about the linting - When this project was started several years ago (then kritzbot and node-twitchbot) I was still new to Node and tools such as eslint. The new v2 branch has full linting support and is also implemented in Typescript.
The plan from here is to lock this branch after this PR, and then focus efforts on a 2.0 release. The goal is to keep the API fully backwards compatible (where possible). If you have experience with Typescript and want to help more on this project, I would welcome you raise any issues/improvements about that branch.
Thanks again 👍

I see what you mean by deciding on what format the channel name should be in a whisper chatter. I like the idea of using the WHISPER prefix, but I think we could change the current format. Currently a channel via a whisper message looks like this:
{ channel<EMAIL_ADDRESS>},

Maybe it would be cleaner to remove everything after the !
{ channel: "WHISPER_bot_sender" }, // Remove the "!sender... etc."

Maybe we should use<EMAIL_ADDRESS>as a channel name instead since it is what twitch is giving us as a group-channel.
It is also possible to do do wispers by<EMAIL_ADDRESS>PRIVMSG #channelname: /w targetuser message but i'm using the PRIVMSG #jtv :/w syntax instead since this is what the twitch staff used in most awnsers they've given on discuss.dev.twitch.tv

How is this feature coming along? I was about to implement this feature myself, but checked to see if someone else was working on it. And found this pull request.
Nothing since 24 Oct 2018?

My guess is that this is still stuck between v 1.x and 2.x, you can use my branch but i have not tested this since the day i created the PR.


⚠ Thumbnails API Endpoint has degraded performance

In 3761163, Thumbnails API Endpoint (https://thumbnails.roblox.com/v1/assets?assetIds=82738847&format=Png&isCircular=false&size=30x30) experienced degraded performance:

HTTP code: 200
Response time: 1515 ms

Resolved: Thumbnails API Endpoint performance has improved in 0ad43de.


Time for a new release ?

Hi,
I wish to parse the ledger balance date in production, however this info is extracted from OFX files only since 8331cc7274250880861829c887e859c7ab84e00a (which was committed only 2 months after 0.14 release, such bad luck).
Do you plan a new release anytime soon ?
And thanks for your work on ofxparse, it's very useful.

New release made.  Sorry about the long wait!


send image and data

how to send image and data after drop file?

You write the code necessary to do so.  Usually this involves knowing how
to program and reviewing the examples/documentation about this library so
you know what it does and doesn’t do.
On Sat, Sep 24, 2022 at 12:41 AM 1hilari @.***> wrote:

how to send image and data after drop file?
—
Reply to this email directly, view it on GitHub
https://github.com/cornerstonejs/dicomParser/issues/213, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJVXWQF3RVWV2CFTZFRF2DV72H7PANCNFSM6AAAAAAQUP3WHU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


fix(merge): regExp should not be treated as a objects when merging.

While merging two objects RegExp should not be treated same as the object.
Closes : #12409

i'll fix it myself, lgtm

Thanks!

Thanks @caitp.


Support read-only rights

I would like to use Piperider to profile datasets with user that has read-only rights to those tables. So far CLI nor dbt-config did not allow me to do so - it only allows me to profile the particular schema used in the config. This is an example:

My user has a dedicated workspace with write access and has a read-only access to schemas/tables I would like to run profiling.
when I forced it through CLI --table command it ended up with this error:
Error: Profiler Exception: ProgrammingError('(snowflake.connector.errors.ProgrammingError) 001059 (22023) : SQL compilation error: Must specify the full search path starting from database for SAPI_9609
[SOL: SHOW /* sqlalchemy:_get_schema_primary_keys */PRIMARY KEYS IN SCHEMA sapi_96091
(Background on this error at: https://sqlalche.me/e/14/f405)')

For internal tracking sc-31341

@Vfisa PipeRider does support accessing the read-only snowflake tables.
However, the CLI run option --table with schema and table name didn't work here could be caused by the following issue: https://github.com/InfuseAI/piperider/issues/666
We already fix this issue at the PipeRider latest version v0.24.1
https://github.com/InfuseAI/piperider/releases/tag/v0.24.1
Could you please upgrade the PipeRider to the latest version and try to reproduce this issue again?
Thanks.


Scaling Query

Hi
This is excellent code - many thanks as it aligns with some research I am doing and also helps with my Python.
I have a query regarding the scaling. Am I correct that this code is including the test data in the scaling fit? Should the test set be excluded from that process? That is, should the data not be sploit into train/test prior to fit_transform on train and transform only on test?

Hi Andrew,
Glad the code is helping you! As this is my first shot at RNN (thus take everything cautiously), I also profited massively from other projects and blog posts and thus had to share this...
Regarding the scaling on test data:
Thanks for raising this point. You are very correct, one should not base the standardization on the whole sample but only on the training data and then use the estimated parameters also on the test data, otherwise the model gets an "illegal" glimpse at the test data.
I noticed this flaw only after running the generated models (which took many hours...) and as the hand-in date for the paper was fast approaching, I didn't have time to correct and rerun the models. In the paper I argued that as the series seems to be stationary (if you take out the seasonality) and the distribution of both the train- and test data is similar, the results should not really get affected...

Hi Dafrie
Was more a sanity check than anything critical as I agree the scaling would have been very similar either way.
thanks again


Problem: omn_txn.retry max_attempts is not always practical

Specifically, it doesn't tell us how long we should be trying to commit the transaction for.
Proposed solution: introduce a timeout parameter
A timeout parameter would tell when we should no longer attempt to transact the given transaction.

Bounty size: $250
Read more about bounties

working on this issue please assign me

@yrashk i would like to give it a shot, would you provide more details about the same.


[Isthmus] What's the difference between tpch_smoke.sh and TpchQueryNoValidation

I noticed that both of them share almost same code path. tpch_smoke.sh can not pass some queries(q7,q8...) while TpchQueryNoValidation can pass all. And tpch_smoke.sh is in CI workflow, the other one is not.

They are both in the CI workflow. TpchQueryNoValidation is run as a unit test. tpch_smoke is run against the native compiled binary. The former checks functional behavior, the later that the graal compiled code works (it isn't guaranteed given how graal is a partial jvm).

Thanks for your explanations @jacques-n !
So current status is:

Graal compiled code can not pass all tpch queries(like q7). if so, is there any plan to fix it?
If I want to use Isthmus as a binary for functionality, I would better compile/run it in a legacy JVM way.

Thanks for your explanations @jacques-n ! So current status is:

Graal compiled code can not pass all tpch queries(like q7). if so, is there any plan to fix it?

At one point, not all tpch queries were supported. If something is now passing in the no validation test but is failing in graal, please open a ticket.

If I want to use Isthmus as a binary for functionality, I would better compile/run it in a legacy JVM way.

I don't understand your statement. If you want to use Isthmus as a library in a java project, you can use jars (and ignore graal). If you want to use as a binary executable, you must use graal.

Got it, thanks again! will submit another issue for failed queries.


Sudospawner with jupyterhub 0.8.0

Has anyone had any issues with using sudospawner with version 0.8.0 of jupyterhub?
I can't see any specific errors in the log, other than it mentions that it took too long for the session to spawn. It was all working fine with 0.7.2.

@csghuser I also have problems with jupyterhub 0.8.0 and sudospawner 0.5.0 / 0.6.0.dev0. The error I get is:
[E 2017-10-06 09:17:16.164 JupyterHub gen:914] Exception in Future <tornado.concurrent.Future object at 0x7fb3b1a9b7f0> after timeout
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/tornado/gen.py", line 910, in error_callback
future.result()
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/handlers/base.py", line 444, in finish_user_spawn
yield spawn_future
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 476, in spawn
raise e
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 450, in spawn
resp = yield server.wait_up(http=True, timeout=spawner.http_timeout)
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 180, in wait_for_http_server
timeout=timeout
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 135, in exponential_backoff
raise TimeoutError(fail_message)
TimeoutError: Server at http://servername:40759/user/lbiemans/ didn't respond in 30 seconds
[E 2017-10-06 09:17:16.166 JupyterHub gen:914] Exception in Future <tornado.concurrent.Future object at 0x7fb3b1a9b7f0> after timeout
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/tornado/gen.py", line 910, in error_callback
future.result()
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/handlers/base.py", line 444, in finish_user_spawn
yield spawn_future
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 476, in spawn
raise e
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 450, in spawn
resp = yield server.wait_up(http=True, timeout=spawner.http_timeout)
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 180, in wait_for_http_server
timeout=timeout
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 135, in exponential_backofmyserver
raise TimeoutError(fail_message)
TimeoutError: Server at http://servername:40759/user/lbiemans/ didn't respond in 30 seconds
[E 2017-10-06 09:17:16.454 JupyterHub base:709] Preventing implicit spawn for lbiemans because last spawn failed: Server at http://myserver:40759/user/lbiemans/ didn't respond in 30 seconds
[E 2017-10-06 09:17:16.454 JupyterHub web:1590] Uncaught exception GET /hub/user/lbiemans/ (::ffff:<IP_ADDRESS>)
HTTPServerRequest(protocol='http', host='myserver..local', method='GET', uri='/hub/user/lbiemans/', version='HTTP/1.1', remote_ip='::ffff:<IP_ADDRESS>', headers={'X-Forwarded-Proto': 'http', 'Dnt': '1', 'If-None-Match': '"ffb1b54e48e4c193a5ea828676c52da54457a535-gzip"', 'Accept-Encoding': 'gzip, deflate, br', 'User-Agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:55.0) Gecko/20100101 Firefox/55.0', 'Cookie': 'jupyter-hub-token="2|1:0|10:1507273335|17:jupyter-hub-token|44:NjJhMTRjYWEwN2JlNGU5NDllNDQzYzRiYjk0OWU2MGU=|9d6ae560fa2a95afe99eff94909f984aa18f3d18e310202e8849c79c3e8be8cc"; MOD_AUTH_CAS_S=4a787fbce3b829d703ff26109379597b', 'X-Forwarded-For': '<IP_ADDRESS>,::ffff:<IP_ADDRESS>', 'Host': 'myserver..local', 'Accept': 'text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8', 'Accept-Language': 'en-US,en;q=0.5', 'Cas-User': 'lbiemans', 'Connection': 'close', 'Upgrade-Insecure-Requests': '1', 'X-Forwarded-Server': 'myserver..local', 'X-Forwarded-Port': '80', 'Referer': 'https://myserver..local/hub/home', 'Cache-Control': 'max-age=0', 'X-Forwarded-Host': 'myserver..local'})
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/tornado/web.py", line 1511, in _execute
result = yield result
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/handlers/base.py", line 710, in get
raise spawner._spawn_future.exception()
File "/usr/local/lib/python3.5/dist-packages/tornado/gen.py", line 910, in error_callback
future.result()
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/handlers/base.py", line 444, in finish_user_spawn
yield spawn_future
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 476, in spawn
raise e
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/user.py", line 450, in spawn
resp = yield server.wait_up(http=True, timeout=spawner.http_timeout)
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 180, in wait_for_http_server
timeout=timeout
File "/usr/local/lib/python3.5/dist-packages/jupyterhub/utils.py", line 135, in exponential_backoff
raise TimeoutError(fail_message)
TimeoutError: Server at http://servername:40759/user/lbiemans/ didn't respond in 30 seconds

@lbiemans Yep those are the same errors I'm seeing.
Have you managed to get it working?

@csghuser, tried some things but unfortunately none of theme work.

Same issue here, downgrading JupyterHub to 0.7.2 seems to work.

I think I've figured this out. If you set c.Spawner.ip = '<IP_ADDRESS>' in your config, does it work?
I'll have a PR to sudospawner fixing the defaults shortly.

#45 should fix this. We will release 0.5.1 soon after that is merged.

0.5.1 is out with the fix

@minrk didn't have any time to test it until today, but my test server seems to be running like a charm again. Thanks for the great work!


File icon needed for NetCDF file

@gantian127 Can you put some description of netcdf file here to help @mauriel133 to create this icon? I am wondering if we can use the NetCDF resource icon also for NetCDF file.

This has been implemented. Closing.


The alert rule does not fire for File capacity

I use azure monitor to create an alert rule for azure file share capacity.
For resource type, I select "Storage services", then select resource of my auzre file(like storage_name/file).
And in the condition, I select a file share, set Threshold value to 7M(7340032 bytes).  So the condition is "File capacity is greater than 7340032 bytes"
Then I fill in my email address.
I also select Yes for "Enable rule upon creation".
After the rule is created and enabled, I upload a larger file(more than 7M) to the file share, and wait for about 2 hours, but there is no alert fired, I cannot receive the alert email.
Can you please let me know what's wrong with the alert rule? or it's a bug?
The screenshot below show the configuration of my alert rule:

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

ID: 9aeeedc1-d567-f4b1-9913-14f401df8884
Version Independent ID: 324a8bd9-cec9-3be0-b1fb-01e9a0f95710
Content: Create, view and manage Metric Alerts Using Azure Monitor
Content Source: articles/azure-monitor/platform/alerts-metric.md
Service: azure-monitor
Sub-service: alerts
GitHub Login: @snehithm
Microsoft Alias: snmuvva

@imeya Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update.

Looks like the feedback is valid one and alert with FileCapacity platform metric is not getting fired on crossing the set threshold . Assigning to @snehithm for better analysis / insights.

@KrishnaG-MSFT , @snehithm , any update on this?

Hi @imeya, thanks for reporting it. Might be a bug. Could you please file a support ticket so we can investigate this properly? Docs are not a convenient place to track such issue. Closing this issue.
#please-close.


Possibility to provide (or propagate) proxy settings and bootstrap timeout

In previous versions of juju (prior to 2.0?) it was possible to change timeout and other settings like this: http://askubuntu.com/questions/458535/how-to-change-juju-bootstrap-time-from-the-10min-it-gives-you
In latest version of juju (2.0-beta9-xenial-amd64) and conjure-up (<IP_ADDRESS>-0~459~ubuntu16.04.1) I don't see any way to provide proxy settings and juju bootstrap timeout. There is a thread on stackoverflow which already mentions that: http://askubuntu.com/questions/770624/how-to-set-bootstrap-timeout-when-deploying-landscape-dense-maas-from-conjure-up
Currently I am workarounding this by adding in /usr/share/conjure-up/conjure/juju.py (L:120) additional hardcoded command line params: --config bootstrap-timeout=3600 --config http-proxy=[proxy] --config https-proxy=[proxy] --config apt-http-proxy=[proxy] --config apt-https-proxy=[proxy] --config --config apt-ftp-proxy=[proxy] --config ftp-proxy=[proxy] no-proxy=[IPs]
It would be good to have these parameters configurable or provide a possibility to propagate them from env variables/MAAS 2.0 settings (if MAAS is used).

Thanks I'll make sure this gets in the next prerelease

Thanks! :)

@ptylenda np, this will be in the PPA by next Tuesday July 5th.

I'm using this PPA, but I'm not seeing any global way to set the proxy before a model is created. It seems the only workaround is to use --config everywhere.
See my AskUbuntu post: http://askubuntu.com/q/852154/573381


Getting error when packaging Electron Builder Project

Hi, I am getting the following error when I am trying to package a project that I created with Electron

When I try to run the project, it works fine. But upon running the npm run build command, we get this error.
Minimal Reproduction steps

Clone https://github.com/electron-react-boilerplate/electron-react-boilerplate repository
install the @miniben-90/x-win package
Use activeWindow anywhere in the main.ts file
Run the npm run build command to start building the project

System Information
Operating System: Windows 11 Pro 21H2
Node Version: 16

Adding the dependency to the release package.json resolved the issue. Thanks a bunch @miniben-90


Add note regarding memory requirement.

On a quad core system with 8G memory and 2g swap file the build crashed the computer repeatedly during Clang compilation. Altering thread count had no effect. Increasing swap file size to 8G allowed the build to succeed with all threads.

On a quad core system with 8G memory and 2G swap file the build crashed the computer repeatedly during Clang compilation. Altering thread count had no effect. Increasing swap file size to 8G allowed the build to succeed with all threads.
I added a note to the readme in the hope it will help others. Thanks for Yoe-Distro!


implement -v and/or --version for wcag's version number

I want a quick way to display which version I'm using.
$ wcag -v

or
$ wcag --version

output
$ 0.1.4

If there's no good reason not to implement this I can take care of it.

:+1: Definitely.

Fixed by https://github.com/cfpb/node-wcag/pull/6.


How to set zsh as default shell on startup?

You need to make it your login shell: chsh -s $(which zsh). Also, you might need to log out from your account after that.


Allow for non-"on" methods when using resources

When trying to use a resource and a non-'on' method (once, before, after), Router would error during initialization because in insertEx it was evaluating immediately because it was trying to call apply() on the route which was a string.
I didn't quite figure out why it was trying to do that before init() was being called so the error may be a result of a larger issue, but the fix included in here caused everything to work nicely for my test cases.
Please let me know if you have any questions

¯_(ツ)_/¯


API for shared arguments is a bit weird

So diesel_cli has a use case where basically all of our commands take the same argument. You can see our exact code here: https://github.com/sgrif/diesel/blob/331f81c353ec0c7f0b6897cb80cb405b2d9120bb/diesel_cli/src/main.rs#L13-L42
All of our commands except one take --database-url (and really it's not a big deal if it gets passed to that command as well). Right now, if I put that argument on the Clap::App instance, it requires that the command is run as diesel --database-url=url migration run, but I'd much rather it be diesel migration run --database-url=url, or really just allow it basically anywhere. (As an aside, we're having to wrap the argument in a closure because Arg doesn't derive Clone, but it probably could)
Does this seem like a reasonable/common enough use case to warrant support within clap itself?

If you add that Arg to your top level App instance but set the Arg::global(true) it should be exactly what you're looking for...i.e. it'll just propagate that particular Arg down through all child subcommands....if not it's a bug ;)

@sgrif Also I haven't forgotten about #372 I'm really hoping to have it out really soon with the 2.x base :wink:

@sgrif Also I forgot to mention that in v2 it supports passing borrowed Arg structs, so you could create an Arg instance and just pass a borrow of that same instance to all your subcommands which doesn't require Cloneing like global(true) does in 1.x (global also exists in v2 and removes the Cloneing as well, just FYI it's essentially shorthand for passing a borrow to down through each subcommand).

Yup, I just missed this. Thanks.


Invalid option format for cURL library download

Make sure you have done the following

[X] I have updated to the latest version of blink.cmp
[X] I have read the README

Bug Description
Upon updating to the latest version of blink, I received the following error when launching neovim.
Error executing vim.schedule lua callback: .../.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/init.lua:10: Error while downloading blink.cmp pre-built binary: Failed to download pre-build binaries: curl: option --output=/home/bniwa/.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/fuzzy/../../../../target/release/libblink_cmp_fuzzy.so: is unknown
curl: try 'curl --help' or 'curl --manual' for more information

stack traceback:
	[C]: in function 'error'
	.../.local/share/nvim/lazy/blink.cmp/lua/blink/cmp/init.lua:10: in function ''
	vim/_editor.lua: in function <vim/_editor.lua:0>

Relevant configuration
No response
neovim version
v0.11.0-dev-1270+gc7ec010ade
blink.cmp version: branch, tag, or commit
v0.7.0

It seems like curl doesn't support long options in the format of --option=x and instead prefers --option x. I'll submit a PR in a sec with the fix

nvm, this was already reported in #425 :upside_down_face:


Configuration after ungracefully cluster shutdown/restart

Hello all,
We have EMQX running on an on-prem cluster with 3 core 3 replicant pods. On-Prem cluster has 3 masters and 3 worker nodes. Whenever the on-prem cluster has been shut down ungracefully (power outage), EMQX pods are not running properly again. And I need to scale down/up after the ungracefully shutdown. This causes client disconnections and data loss until fixed manually.
I would like to hear suggestions about the EMQX v5.0.16 configuration that I can use for rolling out core/replicants after the ungracefully on-prem cluster shutdown
I wonder if is there any configuration I can apply on EMQX or best practice I need to follow on the K8S cluster?
I am adding the EMQX configuration below.
apiVersion: apps.emqx.io/v2alpha1
kind: EMQX
metadata:
  name: emqx
  namespace: namespace
spec:
  image: "image"
  imagePullSecrets:
    - name: secret
  bootstrapConfig: |
    authorization {
      no_match = "deny"
      deny_action = "disconnect"
      sources = [{type: "file", enable: true, path: "/etc/emqx/acl.conf"}]
    }
    dashboard {
      listeners.http {
          bind: 18083
      }
    }
    listeners.tcp.default {
      bind = "<IP_ADDRESS>:1883"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.internal {
      bind = "<IP_ADDRESS>:1884"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.quic {
      bind = "<IP_ADDRESS>:1885"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.external {
      bind = "<IP_ADDRESS>:1886"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.api {
      bind = "<IP_ADDRESS>:8083"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.ssl.mqttssl {
      bind = "<IP_ADDRESS>:8883"
      max_connections = 1024000
      acceptors = 256
    }
    mqtt {
    max_inflight = "10000"
    max_mqueue_len = "7200000"
    max_packet_size = "25MB"
    }

  coreTemplate:
    metadata:
      name: emqx-core
      labels:
        apps.emqx.io/instance: emqx
        apps.emqx.io/db-role: core
    spec:
      replicas: 3
      volumeClaimTemplates:
        storageClassName: {{ .Values.storageClassName }}
        resources:
          requests:
            storage: 4Gi
        accessModes:
          - ReadWriteOnce
      extraVolumes:
        - name: acl
          configMap:
            name: emqx-acl
      extraVolumeMounts:
        - name: acl
          mountPath: "/etc/emqx/acl.conf"
          subPath: acl.conf
      resources:
        requests:
          memory: "2Gi"
          cpu: "500m"
        limits:
          memory: "2Gi"
      podSecurityContext:
        runAsUser: 0
        runAsGroup: 0
        fsGroup: 0
        fsGroupChangePolicy: Always
      containerSecurityContext:
        runAsUser: 0
        runAsGroup: 0
      livenessProbe:
        httpGet:
          path: /status
          port: 18083
        initialDelaySeconds: 60
        periodSeconds: 30
        failureThreshold: 3
      readinessProbe:
        httpGet:
          path: /status
          port: 18083
        initialDelaySeconds: 10
        periodSeconds: 5
        failureThreshold: 12
  replicantTemplate:
    metadata:
      name: emqx-replicant
      labels:
        apps.emqx.io/instance: emqx
        apps.emqx.io/db-role: replicant
    spec:
      ports:
        - name: "tcp-replicant"
          protocol: TCP
          containerPort: 18083
      replicas: 3
      command:
        - "/usr/bin/docker-entrypoint.sh"
      args:
        - "/opt/emqx/bin/emqx"
        - "foreground"
      resources:
        requests:
          memory: "2Gi"
          cpu: "500m"
        limits:
          memory: "2Gi"
      extraVolumes:
        - name: acl
          configMap:
            name: emqx-acl
      extraVolumeMounts:
        - name: acl
          mountPath: "/etc/emqx"
      podSecurityContext:
        runAsUser: 1000
        runAsGroup: 1000
        fsGroup: 1000
        fsGroupChangePolicy: Always
        supplementalGroups:
          - 1000
      containerSecurityContext:
        runAsNonRoot: true
        runAsUser: 1000
        runAsGroup: 1000
  listenersServiceTemplate:
    metadata:
      name: emqx-listeners
    spec:
      ports:
        - name: "tcp-default"
          protocol: TCP
          port: 1883
          targetPort: 1883

Hello all,
We have EMQX running on an on-prem cluster with 3 core 3 replicant pods. On-Prem cluster has 3 masters and 3 worker nodes. Whenever the on-prem cluster has been shut down ungracefully (power outage), EMQX pods are not running properly again. And I need to scale down/up after the ungracefully shutdown. This causes client disconnections and data loss until fixed manually.
I would like to hear suggestions about the EMQX v5.0.16 configuration that I can use for rolling out core/replicants after the ungracefully on-prem cluster shutdown
I wonder if is there any configuration I can apply on EMQX or best practice I need to follow on the K8S cluster?
I am adding the EMQX configuration below.
apiVersion: apps.emqx.io/v2alpha1
kind: EMQX
metadata:
  name: emqx
  namespace: namespace
spec:
  image: "image"
  imagePullSecrets:
    - name: secret
  bootstrapConfig: |
    authorization {
      no_match = "deny"
      deny_action = "disconnect"
      sources = [{type: "file", enable: true, path: "/etc/emqx/acl.conf"}]
    }
    dashboard {
      listeners.http {
          bind: 18083
      }
    }
    listeners.tcp.default {
      bind = "<IP_ADDRESS>:1883"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.internal {
      bind = "<IP_ADDRESS>:1884"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.quic {
      bind = "<IP_ADDRESS>:1885"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.external {
      bind = "<IP_ADDRESS>:1886"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.tcp.api {
      bind = "<IP_ADDRESS>:8083"
      max_connections = 1024000
      acceptors = 256
    }
    listeners.ssl.mqttssl {
      bind = "<IP_ADDRESS>:8883"
      max_connections = 1024000
      acceptors = 256
    }
    mqtt {
    max_inflight = "10000"
    max_mqueue_len = "7200000"
    max_packet_size = "25MB"
    }

  coreTemplate:
    metadata:
      name: emqx-core
      labels:
        apps.emqx.io/instance: emqx
        apps.emqx.io/db-role: core
    spec:
      replicas: 3
      volumeClaimTemplates:
        storageClassName: {{ .Values.storageClassName }}
        resources:
          requests:
            storage: 4Gi
        accessModes:
          - ReadWriteOnce
      extraVolumes:
        - name: acl
          configMap:
            name: emqx-acl
      extraVolumeMounts:
        - name: acl
          mountPath: "/etc/emqx/acl.conf"
          subPath: acl.conf
      resources:
        requests:
          memory: "2Gi"
          cpu: "500m"
        limits:
          memory: "2Gi"
      podSecurityContext:
        runAsUser: 0
        runAsGroup: 0
        fsGroup: 0
        fsGroupChangePolicy: Always
      containerSecurityContext:
        runAsUser: 0
        runAsGroup: 0
      livenessProbe:
        httpGet:
          path: /status
          port: 18083
        initialDelaySeconds: 60
        periodSeconds: 30
        failureThreshold: 3
      readinessProbe:
        httpGet:
          path: /status
          port: 18083
        initialDelaySeconds: 10
        periodSeconds: 5
        failureThreshold: 12
  replicantTemplate:
    metadata:
      name: emqx-replicant
      labels:
        apps.emqx.io/instance: emqx
        apps.emqx.io/db-role: replicant
    spec:
      ports:
        - name: "tcp-replicant"
          protocol: TCP
          containerPort: 18083
      replicas: 3
      command:
        - "/usr/bin/docker-entrypoint.sh"
      args:
        - "/opt/emqx/bin/emqx"
        - "foreground"
      resources:
        requests:
          memory: "2Gi"
          cpu: "500m"
        limits:
          memory: "2Gi"
      extraVolumes:
        - name: acl
          configMap:
            name: emqx-acl
      extraVolumeMounts:
        - name: acl
          mountPath: "/etc/emqx"
      podSecurityContext:
        runAsUser: 1000
        runAsGroup: 1000
        fsGroup: 1000
        fsGroupChangePolicy: Always
        supplementalGroups:
          - 1000
      containerSecurityContext:
        runAsNonRoot: true
        runAsUser: 1000
        runAsGroup: 1000
  listenersServiceTemplate:
    metadata:
      name: emqx-listeners
    spec:
      ports:
        - name: "tcp-default"
          protocol: TCP
          port: 1883
          targetPort: 1883

My emqx cluster is deployed using helm. I set log configuration as per documentation but still logs are not getting stored in file. it gets stored in console. why is that, can anyone please help?

@memoliyasti Could you please change EMQX to 5.1.3 and retry it.

@memoliyasti Could you please change EMQX to 5.1.3 and retry it.

Is it not possible in version 4.3.5

@memoliyasti Could you please change EMQX to 5.1.3 and retry it.

Is it not possible in version 4.3.5

I think your question is not related to the topic of this issue, so it is not suitable to discuss it here. You should create a new issue.
The code of EMQX Helm Chart is in the emqx/emqx repository, which is just the repository for EMQX Operator.

@memoliyasti Could you please change EMQX to 5.1.3 and retry it.

Hi @memoliyasti Is your issue still there?

Hi @Rory-Z
When I wanted to use 5.1.3, replicants did not come up. Issue has not been solved since replicant replicants did not come up. But I think this is related with issue what is mentioned here . It was seeming that creating PVC was blocking for replicants to be deployed. I will try it again after this merge

Hi @memoliyasti the EMQX Operator 2.2.1-rc.1 is released,  maybe you can try it

Hi @Rory-Z ,
I had a chance to try the new emqx-operator release (2.2.1-rc.1 ) and when I do that with Helm, replicants did not come up but when I try to deploy it as manifest, replicants came up and pvc has been created successfully.
It seems it is about using Helm.
Let me share the manifest briefly I used below

---
# Source: emqx/templates/configMap.yaml
apiVersion: apps.emqx.io/v2beta1
kind: EMQX
metadata:
  name: emqx
  namespace: <namespace>
spec:
  image: emqx:5.1.4
  coreTemplate:
    spec:
      replicas: 3
      volumeClaimTemplates:
        storageClassName: "default"
        volumeMode: Filesystem
        resources:
          requests:
            storage: 1Gi
        accessModes:
          - ReadWriteOnce
  replicantTemplate:
    spec:
      replicas: 3
  listenersServiceTemplate:
    metadata:
      name: emqx-listeners
    spec:
      ports:
        - name: "tcp-default"
          protocol: TCP
          port: 1883
          targetPort: 1883
  dashboardServiceTemplate:
    metadata:
      name: emqx-dashboard
    spec:
      ports:
        - name: "tcp-http"
          protocol: TCP
          port: 18083
          targetPort: 18083

Hi @memoliyasti, Maybe you can diff Helm template and manifest file ? like this:
$ helm install emqx-operator emqx/emqx-operator --namespace emqx-operator-system --create-namespace --version 2.2.1-rc.3 --debug --dry-run > template.yaml
$ vimdiff template.yaml manifest.yaml


Swagger integration

Required Functionality
I would appreciate for the functionality of new import - import from Swagger spec (and Async / CloudEvents if this is possible). That would help a lot with data generation for mocks/stubs and performance testing
Proposed Solution
Use case
Generating mocks/stubs for performance testing of APIs and fast data for POC validations

This could be possible, but it would require a bit of work. If you could open a PR that would be great.


KeyErrors that may be caused or triggered by smartir

Hi
Yesterday I started to notice keyerrors in the systemlog reported from the quirk I'm using for my Tuya Zigbee IR device. Maybe it's been like this for a while, I don't know.
2024-07-31 08:25:49.111 ERROR (MainThread) [bellows.ezsp] Exception running handler
Traceback (most recent call last):
File "/usr/local/lib/python3.12/site-packages/bellows/ezsp/init.py", line 494, in handle_callback
handler(*args)
File "/usr/local/lib/python3.12/site-packages/bellows/zigbee/application.py", line 617, in ezsp_callback_handler
self._handle_frame(*args)
File "/usr/local/lib/python3.12/site-packages/bellows/zigbee/application.py", line 662, in _handle_frame
self.packet_received(
File "/usr/local/lib/python3.12/site-packages/zigpy/application.py", line 1032, in packet_received
return device.packet_received(packet)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/zigpy/device.py", line 497, in packet_received
endpoint.handle_message(
File "/usr/local/lib/python3.12/site-packages/zigpy/endpoint.py", line 247, in handle_message
handler(hdr, args, dst_addressing=dst_addressing)
File "/usr/local/lib/python3.12/site-packages/zigpy/zcl/init.py", line 430, in handle_message
self.handle_cluster_request(hdr, args, dst_addressing=dst_addressing)
File "/config/custom_zha_quirks/ts1201.py", line 304, in handle_cluster_request
irmsg = self.endpoint.device.ir_msg_to_send[seq]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^
KeyError: 195
To rule out the problem wasn't caused by the quirk, I made an automation that uses zha issue_zigbee_cluster_command to issues all the IR-commands, one by on, from the device codes file I'm using (1266.json). I found that I had to delay each service call by about 1 second to eliminate the errors.
Then I created a script to issue all possible combinations of hvac, preset, fan and temperature with the SmartIR climate component. I set the same delay between each operation, but the same errors started to show up pretty soon. Maybe the quirk or some other component should have handled this, but I've found a couple of things in the SmartIR component that probably should be corrected:

I may be wrong, but it seems to me that the delay setting in the configuration is not honored correctly. For testing purposes I've altered climate.py:
Added await asyncio.sleep(self._delay) after the last await self._controller.send(commands["on"]) in the async def _send_command operation.

Traling comma in ZHAController send  service_data:
service_data["params"] = {
"code": command,
}
For testing purposes I've altered controller.py by removing the trailing comma.

I've got no keyerrors in the system log after these small "fixes".
Sorry for my lack of competence on Github :-(

Hello, thank you for report. The trailing edge comma shall have zero impact on the data structure, it is just byproduct of the python Black formatter. The code with and without comma is equal. I think that this is just coincidence and root cause of the error lays somewhere else.
As you can see Python exception points to the key error - key seq is not defined in the self.endpoint.device.ir_msg_to_send dictionary.

Yes, I agree. The root cause is probably somewhere else, and to me it seems like it's triggered by simultanous/multiple zha calls.
Anyway, when I added "await asyncio.sleep(self._delay)" the issues have disappeared.

Great finding, where did you put the line? In the SmartIR code?

Yes, in climate.py after the last await self._controller.send(commands["on"]) in the async def _send_command operation. In the version I'm using at line number 616

About here in the latest version: https://github.com/litinoveweedle/SmartIR/blob/master/custom_components/smartir/climate.py#L790

Right now almost all the proposed changes for this release are merged with master (and current beta is based on that).
In the master there is already sleep after sending 'on' command.
                        else:
                            # if on code is not present, the on bit can be still set later in the all operation/fan codes"""
                            _LOGGER.debug("Found 'on' operation mode command.")
                            await self._controller.send(commands["on"])
                            await asyncio.sleep(self._delay)

So I am bit confused about you modification as the code is already there....

 I've placed it here instead: https://github.com/litinoveweedle/SmartIR/blob/master/custom_components/smartir/climate.py#L790

It seems like the existing code handle sleep after on operation, but not delays between ir calls. According to the docs delay "Adjusts the delay in seconds between multiple commands. The default is 0.5". With my suggested placement it should be handled.

Great, thank you for reporting, I will fix this and schedule to release it in incoming release.

Thx!
Fyi. I've just finished a couple of days intensive testing of the component and checked that all the IR-codes (in the device codes file I'm using) is picked up and sent correctly by the component. I'm glad to report that I've not able to find any hickups. Well done, @litinoveweedle!

Hello, fix was provided in #96 and was merged into master. I will release new beta soon. Please be warned there are additional breaking changes in the controllers configuration in the latest beta.

The fix was relesed in the latest beta


Transition Directions

Left and Right are swapped in the Transition event lol.
fade right goes left
fly left goes right
etc etc....
No biggie just funny.

 I see the fly right means the into visibility not the exit visibility.