Masks prevent interactions regardless of layers/groups.

I'm using the layers branch and I've got this very basic setup:
const stage = new PIXI.display.Stage();
stage.group.enableSort = true;

const overlay = new PIXI.display.Group(10, false);
stage.addChild(new PIXI.display.Layer(overlay));

If I set the parentGroup of a display object to overlay it works just fine visually, the object is rendered on top of anything else in the stage, but if the parent of that object has a mask, while still displayed correctly, the interactions don't work unless the object is within the bounds of the mask.
Seems like a pretty nasty problem since the decision is made before even getting to the object that has a parentGroup set
https://github.com/pixijs/pixi-display/blob/25a2a0e06269c6fde4241308a54727bffb9405d2/src/InteractionManagerMixin.ts#L45
so I'm hoping that I just overlooked some easy way around this.

You are right, that's a bug. Its not easy to make interaction work with this, of course we'll need some adjustments ^_^ Working on it.

Wow, you mean there is hope? Yaaay
Thanks!

Ok, lets try new version, i made fast fix but its not complete, it doesnt handle masks of parent layer.

Just tried it, seems to be working well for my use case, thanks for the quick fix!

Ok, i found one more issue with that, and just fixed it. Lets close this issue.


feat: useSignAuthorization experimental hook

Working on the next major version of Wagmi and going to make it easier to add actions and framework-specific function with much less code. Going to close for now and will add your work into there so you still get credit.


Optimize yAxisTitleRotate

New Pull Request
We used to perform multiple identical checks, and query DOM elements that would not be used when a title doesn't exist.
With this patch, we found a slight performance improvements on our project.
Type of change
Performance optimisation.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Hey @yacinehmito
Thanks for your contribution and sorry for the delay in reviewing this PR.
Can you please remove the dist file as it should only be generated for a new build/release?
Thanks!


Fix broken links in Readme

I would also be happy to add any insight from #14 if it's worth it.

Thanks for the patch!


Fix missing error if initial connection cannot be established.

Use case: If you try to create a connection to a DCOM server (OPCDA Server in my example), but misspelled the IP address. Currently the socket setup just runs forever, but we already have a timeout setting and also an error event which we only have to use.
Proposed solution: Add a timer that lets the ComTransport object emit an error event if the timeout times out before the socket has connected, otherwise clear the timeout again immediately.

Greetings
The idea here is to be able to close the socket in case of connecting to the wrong address? If so, the chain of function calls that end on calling the close function from the ComTransport class doesn't serve this purpose?
If I'm not mistaken if the socket is unable to connect it will emit an error event which is transformed and emitted as a 'disconnected' one.

Well, the error is the following: When I set up a connection to an OPC-DA server according to your instructions https://github.com/st-one-io/node-dcom, my example code looks as follows:
`
const domain = 'WORKGROUP'
const username = 'myuser'
const password = 'mypassword'
const ipAddress = '<IP_ADDRESS>'
const classIdString = 'F8582CF2-88FB-11D0-B850-00C0F0104305' // Matrikon.OPC.Simulation
const sessionSingleton = new Session()
const comSession = sessionSingleton.createSession(domain, username, password)
const clsid = new Clsid(classIdString)
let comServer = new ComServer(clsid, ipAddress, comSession)
// start the COM Server
await comServer.init() // this promise hangs (=does not resolve or reject) upon wrong ipAddress
console.log('Successfully connected')
`
In this code, the line comServer.init() will hang forever if the IP Address is an unreachable address, for example someone has mistyped the address.
I am asking for getting a useful error message if the address is unreachable. My proposed patch here is one solution I could come up with: Upon unreachable IP address, the ComTransport just doesn't return (=resolve), but the usual behaviour is to have a timeout running in parallel. So I added this timeout in ComTransport to let it emit an 'error' signal, upon which the Rpc Stub also throws an error.
There might be other solutions possible, of course. My point is that the current code still doesn't handle the unreachable IP address situation and this should be improved. If you already have a different possibility to catch this situation, my request probably asks for documenting this possibility and I'll happily use that. Thanks!

Greetings
You can add a listener to comServer
mycomserver.on("disconnected", function() {

});

However I made a mistake by not including the error message so you can listen to an event but it will say nothing about what happened. Also the time we'll wait for the socket cannot be changed so your suggestion seems like a good solution . I will play with it a bit and if everything is alright this can be merged.
Ty

Any news on including this PR here? You mentioned the 'disconnected' event; however, even though this event exists, it does not get emitted when the initial connection cannot be established (such as wrong IP address). See the provided example file in PR #8: If that one is started with any IP address which doesn't point to an OPC-DA server, currently the call comServer.init() just hangs forever, regardless of whether the event is subscribed to or not.
What else should I provide to you? I submitted a bug description including steps on how to reproduce; I added an example file that directly shows the erroneous behaviour (in PR #8); I submitted a PR here that fixes this. What else do you want to receive?

Any news on including this PR here?

Any news on including this PR here?


Simplify register testutils

Simplify register testutils. Maybe, if possible.
The number of testutil register functions has grown. In these ways they are awkward:

A contract ID is always a parameter, even though the 'register over an existing contract ID' use case is the rarest.
Over time most contracts will have a constructor, but the constructor variants have names that are sooo long they frequently cause line wrapping, which makes examples less enjoyable to read.
The easiest to find fn is register_contract, and it takes no constructor params, but can throw an error saying the wrong number of inputs are passed, which is confusing because there are no variable length inputs obviously visible to the developer.
The stellar asset contract fns are mostly fine.

There now exists six different register functions.

 pub fn register_contract<'a, T: ContractFunctionSet + 'static>(
     &self,
     contract_id: impl Into<Option<&'a Address>>,
     contract: T,
 ) -> Address

 pub fn register_contract_with_constructor<'a, T: ContractFunctionSet + 'static, A: ConstructorArgs>(
     &self,
     contract_id: impl Into<Option<&'a Address>>,
     contract: T,
     constructor_args: A,
 ) -> Address

 pub fn register_contract_wasm<'a>(
     &self,
     contract_id: impl Into<Option<&'a Address>>,
     contract_wasm: impl IntoVal<Env, Bytes>,
 ) -> Address

 pub fn register_contract_wasm_with_constructor<'a>(
     &self,
     contract_id: impl Into<Option<&'a Address>>,
     contract_wasm: impl IntoVal<Env, Bytes>,
     constructor_args: Vec<Val>,
  ) -> Address

 pub fn register_stellar_asset_contract_v2(
     &self,
     admin: Address,
 ) -> StellarAssetContract

 pub fn register_stellar_asset_contract(
     &self,
     admin: Address,
 ) -> Address

Any deprecation and rename should occur in a way that is not breaking to existing contracts.

Maybe worth exploring if we can do something like this:
pub enum Contract<'a, CFS: ContractFunctionSet> {
    Native(CFS),
    Wasm(&'a [u8]),
}

impl<'a, CFS: ContractFunctionSet> From<CFS> for Contract<'a, CFS> { ... }
impl<'a> From<&'a [u8]> for Contract<'a, NoContractFunctionSet> { ... }

pub fn register<'a, C: Into<Contract> + 'static, A: ConstructorArgs>(
      &self,
       contract: C,
       constructor_args: A,
)

pub fn register_at<'a, C: ContractFunctionSet + 'static, A: ConstructorArgs>(
      &self,
       contract_id: impl Into<Option<&'a Address>>,
       contract: C,
       constructor_args: A,
)

To support calls like this:
env.register(MyContract, ());
env.register(imported::WASM, ());

And:
env.register_at(address, MyContract, ());


ART-1011 improve rhsa creation

Provide more correct boilerplate text for different kinds of advisories.
See https://github.com/openshift/ocp-build-data/pull/183 for example.
Raise an error if any bug is not viable:

For RHBA, assert bugs are in one of MODIFIED, ON_QA, or VERIFIED state and not attached to any other advisories.
For RHSA, perform the same checks as RHBA then validate they are tracker bugs.

When running without --yes (preview mode), also print the full list of bugs that would be attached.
CLI: Add help text and alias --bug for option --bugs

NOTE

This PR doesn't prevent users from attaching a security bug to an RHBA/RHEA. Not sure if we should do that.
Boilerplate text updates:

4.2 https://github.com/openshift/ocp-build-data/pull/183

4.1 https://github.com/openshift/ocp-build-data/pull/184

4.3 https://github.com/openshift/ocp-build-data/pull/185

3.11 https://github.com/openshift/ocp-build-data/pull/186

For reviewers

Example commands:

elliott --group=openshift-4.1 --debug create --type=RHSA --date=2019-Oct-12<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>--kind=image --bug=1762123
# should fail with `Bug 1762123 is already attached to advisories: 47489`

elliott --group=openshift-4.1 --debug create --type=RHSA --date=2019-Oct-12<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>--kind=image --bug=1743872
# should fail with `Bug 1743872 is not a CVE tracker: Keywords are [].`

Advisories created using this PR on Errata Tool stage:
RHBA: https://errata.stage.engineering.redhat.com/errata/details/51305
RHSA https://errata.stage.engineering.redhat.com/errata/details/51304

This PR includes https://github.com/openshift/elliott/pull/70. Please focus on the latest commit and don't merge it until https://github.com/openshift/elliott/pull/70 is merged.

This looks very good to me @vfreex ! Lots of refactoring included to clean things up a bit, nice! Merge after the ocp build data PRs are merged, right?
/lgtm

@tbielawa It also uses the existing boilerplate text as fallback so those ocp build data PRs are not blockers.

Rebased

Rebased.

@sosiouxme PTAL.


Reduce size by including only lib directory

Currently all files in this project are included in the npm package, which needlessly bloats the package size.
This PR reduces the size by specifying lib in files field in package.json.
Before
package size:  64.4 kB
unpacked size: 876.1 kB

After
package size:  13.7 kB
unpacked size: 213.1 kB

It was not clear to me whether the release directory should be included.
I would add it if necessary.

@teppeis Thank you!!!


Update Korean error-handling.md

Fix some wrong translation
Follow the latest English content (last line only right now)

Thanks!


Utility Menu Read Only Item

Feature Request
Description
We have a use case where we show a correlation id in the Utility Member. This ID is used to help correlate IDs to requests for better investigation. This would typically be something that a user would highlight and copy paste. However, there does not seem to be an option to have a read-only utility item, so any attempt to highlight/copy-paste this item will count as a button click and closes the menu. A read only option would greatly assist this workflow.
Additional Context / Screenshots

@ Mentions
Consulted with @bjankord and he recommended logging a Read Only option terra bug. He also recommended opening a modal to allow users to copy, which I will follow-up on to see if it is a viable option on our side.

Looks like here is where we would want to start adding changes: https://github.com/cerner/terra-framework/blob/master/packages/terra-application-utility/src/utility/_UtilityMenuItem.jsx

Potential Non Modal Solution

Add a new prop, isReadOnly, to the itemShape.
Add corresponding prop isReadOnly to _UtilityMenuItem.jsx.
Inside _UtilityMenu.jsx's menu item generation, conditionally check isReadOnly to not attach the onChange function to that menu item. Do this here.
Add an onChange existence check here.
Use readOnly prop to create read-only styles for the menu item.

We'll have to handle edge cases. One example - if someone defines a menu item containing both isReadOnly and isSelectable -  I'd vote isReadOnly takes precedence.


Quiet builds and disable unity build

High Level Overview of Change
Verbosity makes gitlab CI choke.
Unity makes gitlab CI explode.

Context of Change

Type of Change

[x] Bug fix (non-breaking change which fixes an issue)

Included with https://github.com/ripple/rippled/commit/d02f0e11c51304d1c5f83e6d40388f474e1215d1


increase build-#, use fontconfig on windows too

increase build-number
remove bogus ignore_run_export
add abs.yaml
use fontconfig on Windows too

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:60: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:62: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:132: missing_description: The recipe is missing a description
WARNING: /tmp/abs_399_wj071n/clone/recipe/meta.yaml:132: documentation_overspecified: Using doc_url and doc_source_url is overspecified
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:60: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:62: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:73: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:134: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_042y3u26to/clone/recipe/meta.yaml:134: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:60: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:62: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:72: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:73: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:133: missing_description: The recipe is missing a description
WARNING: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:133: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:134: missing_description: The recipe is missing a description
WARNING: /tmp/abs_9ckn37yqyk/clone/recipe/meta.yaml:134: documentation_overspecified: Using doc_url and doc_source_url is overspecified
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:60: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:62: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:72: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:73: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:133: missing_description: The recipe is missing a description
WARNING: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:133: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:134: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_83jaytjgu2/clone/recipe/meta.yaml:134: missing_description: The recipe is missing a description
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:63: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:72: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:73: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:74: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:75: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
WARNING: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:136: missing_description: The recipe is missing a description
WARNING: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:136: documentation_overspecified: Using doc_url and doc_source_url is overspecified
WARNING: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:137: missing_description: The recipe is missing a description
WARNING: /tmp/abs_287bzdlsx6/clone/recipe/meta.yaml:137: documentation_overspecified: Using doc_url and doc_source_url is overspecified
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_49uzg3mjmv/clone/recipe/meta.yaml:63: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_49uzg3mjmv/clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_49uzg3mjmv/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_49uzg3mjmv/clone/recipe/meta.yaml:72: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_c4wwyby713/clone/recipe/meta.yaml:63: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c4wwyby713/clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c4wwyby713/clone/recipe/meta.yaml:71: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_c4wwyby713/clone/recipe/meta.yaml:72: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_dav0t2f1r9/clone/recipe/meta.yaml:65: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dav0t2f1r9/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dav0t2f1r9/clone/recipe/meta.yaml:73: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_dav0t2f1r9/clone/recipe/meta.yaml:74: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_292raseuj6/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_f119lzxcl9/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_91h7noru_f/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:75: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_42_dx6tf25/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:75: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:145: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_b1gn_3_htq/clone/recipe/meta.yaml:146: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:66: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:75: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:145: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_155efptd6d/clone/recipe/meta.yaml:146: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:67: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:70: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:146: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_7dfy3q63cv/clone/recipe/meta.yaml:147: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:31: patch_unnecessary: patch should not be in build when source/patches is not set
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:147: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_d441q5i548/clone/recipe/meta.yaml:148: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:68: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:75: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:146: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_9axl9n9ry_/clone/recipe/meta.yaml:147: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:147: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_55s36elov5/clone/recipe/meta.yaml:148: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:44: should_use_compilers: The recipe requires a compiler directly
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:69: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:76: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:77: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:147: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
ERROR: /tmp/abs_598cq9cb4f/clone/recipe/meta.yaml:148: invalid_url: https://gnome.pages.gitlab.gnome.org/librsvg/doc/librsvg/index.html : Not reachable: 404
Errors were found


New version: Sysexits v0.2.2

Registering package: Sysexits
Repository: https://github.com/sorairolake/Sysexits.jl
Created by: @sorairolake
Version: v0.2.2
Commit: b4165b5d2b850465e03c2931b9943d0f6f4c21da
Reviewed by: @sorairolake
Reference: https://github.com/sorairolake/Sysexits.jl/commit/b4165b5d2b850465e03c2931b9943d0f6f4c21da#r123271102
Description: The system exit codes as defined by <sysexits.h> for Julia

please close


Add support for local/remote binary

Based on #47
Add the capability to use local and remote Binary

Test are updated
A local xcframework (for local) and a zipped (for remote) one is available in the resource folder or the test module.

The folder localBinarySample contains the Xcode project and a script to generate the testing framework.

@IlyaGulya Done, the history is dirty, squash if you can :D

Hmm, I'm not sure I want binaries in the repo.
I think we could compile these frameworks during the test execution and put them where required

Also, I think it would be nice to use Xcodegen to avoid putting xcode project files into repo. They are not git-friendly =)

Hmm, I'm not sure I want binaries in the repo. I think we could compile these frameworks during the test execution and put them where required

There are required for testing, especially the .zip one, it needs to be available and have a valid checksum. It can't be done during the tests.
Both case are necessary and take a LOT of time to build.

Also, I think it would be nice to use Xcodegen to avoid putting xcode project files into repo. They are not git-friendly =)

Using an external tools to manage the Xcode project will make thing more complicate to manage.
But yes, not git friendly, like every Apple project. Once it's inside the git, it won't move until we add more cases.
Just stay on the simplest way, I can also put the sample project in a zip to clean the history of the git, If you want.

Regarding the xcodeproj - i don't really see any specific reason to keep whole xcode project in the repo, when it can be easily generated by xcodegen.
It's clean and maintainable
name: DummyFramework
options:
  deploymentTarget:
    iOS: 12.0
    macOS: 11.0
    tvOS: 15.0
    watchOS: 8.0
  xcodeVersion: "16.1"
  preferredProjectObjectVersion: "77"

targets:
  DummyFramework:
    type: framework
    platform: [iOS, macOS, tvOS, watchOS]
    sources:
      - DummyFramework
    settings:
      base:
        PRODUCT_BUNDLE_IDENTIFIER: com.dummy.DummyFramework
        BUILD_LIBRARY_FOR_DISTRIBUTION: YES
        SWIFT_INSTALL_OBJC_HEADER: NO
        DEFINES_MODULE: YES
        SWIFT_VERSION: 5.0
        CURRENT_PROJECT_VERSION: 1
        MARKETING_VERSION: 1.0
        SUPPORTS_MACCATALYST: YES
        SUPPORTS_MAC_DESIGNED_FOR_IPHONE_IPAD: YES
        SUPPORTS_XR_DESIGNED_FOR_IPHONE_IPAD: NO
        DRIVERKIT_DEPLOYMENT_TARGET: 20.0
        SKIP_INSTALL: YES

May be relevant: https://github.com/PaGr0m/kotlin-spm-plugin/pull/7


Support for ?

This doesn't seem to be supported in js-yaml:
? - Detroit Tigers
  - Chicago cubs
:
  - 2001-07-23

? [ New York Yankees,
    Atlanta Braves ]
: [ 2001-07-02, 2001-08-12,
    2001-08-14 ]

The problem is not with ?: notation. But with arrays as keys. I'm 100% sure that it was working before, because some JS limitations forced us to explain behavior of arrays as keys in README. In visual example it can be explained as:
var arr = [];
var key = [1,2,3];
arr[key] = 123;
console.log(arr[key]); // -> 123
console.log(arr['1,2,3']); // -> 123

In other words, when you use arrays as key, it become joined with , (commas) before...
Anyway I'm 100% sure it was working before, so it's a kinda regression.

Good that I discovered the regression :)
Your library is not yet fully test covered?

We are in the progress of porting original tests, so in fact it's a home-brew testing suite, but we are going to switch to vows in future.

Have a look at http://visionmedia.github.com/mocha/ as well. It also works on the browser.

Hm. Probably we will use mocha for this project, yes. The day I was choosing testing framework, vows was the only one that was really good.

Yeah Mocha is quite new compared to Vows. It's by TJ so the quality is really high.

Looks, like we'll need to drop support of arrays or objects as keys due to JavaScript limitations:
> var obj = {};
undefined
> var arr = [1,2,3];
undefined
> var alt = {foo:'bar'};
undefined
> obj[arr] = true;
true
> obj[alt] = true;
true
> obj
{ '1,2,3': true,
  '[object Object]': true }

As you can see using non-scalars as keys in JS is absolutely unpredictable.

I have asked @clarkevans for clarifications, so until his thoughts - suspending issue...

As using arrays/objects as keys of objects in JS is really unpredictable, we will not support it. This will be described in README.


Configure record/detail app link in listings on a per table basis

Currently, the search app navigation to record app or view app is in a chaise config. We need to change this to accommodate the navigation at the table level, or schema level.
The configuration hierarchy should be as follows (lower items override more general items above):

Default behavior of codebase is record app
Chaise config can override in a particular web server
Schema-level annotation can override in one schema of one catalog
Table-level annotation can override in one table of one catalog
Foreign-key level annotation can override for one kind of outbound link on a single table?

The annotation will just specify an app name.  The app interpreting this annotation needs to have built-in knowledge of how to form a link to that app.  If we need to fully customize how a an app link is formed, we should use the more general URL annotations to form links from templates, etc.

BTW we need this to be consistent for search and recordset apps.  Should we file two issues?

@hongsudt I would suggest dropping sub-item 5 from the list.
@karlcz yes, i think we will need 2 issues. i mainly think so because the code bases are so different in this case and need to be assigned to 2 different developers. My opinion...
@svoinea My opinion is that the right way to do this is to define the annotation that you think can address this need. Review it with @karlcz  and @robes. Then implement a reusable function. Then fix it in the search app and let @shinyichen reuse the function to fix recordset.

OK, I drafted an annotation (linked above) and also created #381 for the recordset app version of this task.

Fixed in the commit 0efddae728cc942208bcee41848b78944d9dc255.
The 'recordResource' parameter from chaiseConfig was removed.
The 'tag:isrd.isi.edu,2016:recordlink' annotation is used now at the schema or table level.
The default is "record/". The schema annotation overwrites the default, while the table annotation overwrites the default and/or the schema one.
Available for review on rbk-dev.

@chiragsanghvi please review this fix. THanks.


Use 'kni-installer upi bootstrap-complete' instead of handmade script

Installer already has a subcommand to wait for bootstrap to complete

We'll use this automatically once we move to the installer for deploying the masters.  That work is really close to being done, but it's becoming very difficult to rebase on dev-scripts with the cadence of the changes to the 06 and 07 shell scripts.

Oh, okay, lets focus on kni-installer then and avoid introducing more changes

Build SUCCESS, see build http://<IP_ADDRESS>:8080/job/dev-tools/469/


fix support for 4.14 cluster install

Added missing images to bootstrap step.
Added registry certificates to /etc/containers/certs.d folder.

NAME	  VERSION	AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.14.0-ec.3   True        False         2m      Cluster versio
n is 4.14.0-ec.3

/cc @nmagnezi


How to stub Deno namespace

How would one go about stubbing methods called in the Deno namespace?
e.g. running a cli task:
const run = stub(Deno, "run");

Looking at the documentation for Deno.run, it looks like it is expected to return a Process. Depending on what you are testing, you could either add an array containing a fake process object you would like to be returned for each call to the run function in that test or you could add a function argument that would return a fake process object for each call made to Deno.run.
For the fake process object, you would just need to implement the parts that are used by the code you are testing. Documentation for that object can be found here.
If all you needed to access on the process object was the pid and you were calling the function once, you could do the following.
const run = stub(Deno, "run", [{pid:5}])
try {
  // code you need to test
} finally {
  run.restore();
}

If you were calling it multiple times and you needed each fake process to have a different pid, you could instead do the following. In the below example, the first fake process object would have a pid of 5, then the next would have a pid of 6.
let i = 5;
const run = stub(Deno, "run", () => ({pid:i++}))
try {
  // code you need to test
} finally {
  run.restore();
}

Any property you access or method you call on the process object in the code you are testing would need to be implemented.

thanks!

@KyleJune i did same intuitively at first, but it resulted in error
SpyError: cannot redefine property
    at spy (https://deno.land/x/mock@v0.10.0/spy.ts:134:13)
    at stub (https://deno.land/x/mock@v0.10.0/stub.ts:32:25)
    ...

i don't know what have changed over a year, but definitely there was something
excerpt from my code:
import { stub } from<EMAIL_ADDRESS>// ...
    const s = stub(Deno, "run", [{}]) // <-- this line fails

unfortunately this approach is the only i was able to google.
deno 1.11.5 (release, x86_64-apple-darwin)
v8 9.1.269.35
typescript 4.3.2

@abetaev I think I was wrong at the time I made my comment. My comment was about stubbing in general. The SpyError is caused by the fact that the Deno namespace was frozen. In the most recent release, 1.12.0, they have decided to unfreeze it. If you upgrade deno you should be able to stub Deno.run now.
https://deno.com/blog/v1.12#deno-namespace-is-now-unfrozen-and-configurable
If they didn't make that change there are a few ways to work around it.
In time.ts I had to mock the real setTimeout/clearTimeout functions which my module overwrites. To do that, I copied those functions onto an object called NativeTime and have my module call the functions on that object instead of the global ones. That makes it possible for my tests to stub the real functions.
In another module of mine, I needed to stub Deno.test for my TestSuite class that uses it. To do that, I made a static class method called registerTest that just calls through to Deno.test and have the class use that instead of calling Deno.test directly. In the tests where I need to stub Deno.test, I would instead stub TestSuite.registerTest.

@KyleJune thank you for these news :) i'll try it out
i was thinking about modifying code to make it testable, but code in its current form appears to be much simpler than it would be in testable form, so for now i just paused with this activity


Fix search results i18n.

Needs new string in French before merge.
See #548

Looking good. Steph checked my translation.


Organizational Pages

Feature Request
Desired behaviour
We currently can have a direct link to a search like https://dockstore.org/search-containers?query=pcawg. However, it would be nice to have a permanent link to a new kind of search for an organization (an organization on the Docker side).

This task will include

The creation of a new web resource akin to https://dockstore.org:8443/static/swagger-ui/index.html#!/containers/search that allows for search across organizations (called "namespace" in our object returns)
The creation of a new matching search page akin to https://dockstore.org/search-containers?query=test , perhaps https://dockstore.org/search-containers?namespace=pcawg that searches across organizations

@k-cao
Specific pages seem to filter incorrectly
For example https://staging.dockstore.org/search-containers?namespace=dockstore
displays tools like https://staging.dockstore.org/containers/quay.io/mr_c/khmer which are neither in the GitHub organization for Dockstore or the quay.io organization for Dockstore

This is working correctly now, thanks @k-cao


Add ability to keep state for gelf formatters.

Sometimes, it's make sense to have internal state for formatter.
For example in my formatter I want to collect some properties of
my system once on the start and send them with each messages.
Also, in my formatter I decide to cache host once it will be resolved,
because looks like cash was removed from
https://github.com/erlang/otp/blob/master/lib/kernel/src/inet.erl#L466
So, in my case I prefer to use potentialy outdated hostname instead of
getting potential performance issues.
There is possible to implement such state cache with another approaches
(like external memoisation libs) but I believe that with simply introducing
internal state we will cover most of the cases.
Unfortunately, this changes will be breaking for formatters interface,
but I guess, that there is not so many custom formatters in the wild for today.
P.S. (Some additional PR in the queue F.E chuncking support in udp backend :))

Hi @IgorKarymov, thanks so much for the PR!
I have one request, could you add a note about what functions should be exposed by the formatter to the README? Apart from that, the PR looks great 😄
And obviously, I'm looking forward to the other one 😉

updated

Thanks @IgorKarymov !


Create custom element, i.e.

cc @robdodson

Would you want this to be a Polymer element or vanilla custom element?

Here's a first stab at it: https://github.com/robdodson/offthread-image/commit/9e517a0fe6ae68d3bc857c7cc5165d57011ef446
I used Polymer because if, down the line, you want to handle things like changing a property and having that rerender the whole thing it may be easier using Polymer's sugaring. But if you want a vanilla custom element that would probably be easy enough to do.
To run the test you'll need to use Polymer's polyserve server. https://github.com/PolymerLabs/polyserve
The reason you need polyserve is because the element assume it's being installed with a package manager like bower and therefore uses the "canonical path" to import Polymer https://github.com/robdodson/offthread-image/commit/9e517a0fe6ae68d3bc857c7cc5165d57011ef446#diff-a7f2e0645e94e533a445b974825d4922R1
I didn't attempt to get the element to build using the gulp process so I just manually copied the source into dist. If you run gulp it'll be deleted so yeah.. don't do that :)


Session sharing

The main additions are:

utilities for session sharing when parallelizing with standard Python multiprocessing,
a notebook explaining the session interface and session sharing procedure.

There are also a few minor other improvements.

Codecov Report

Merging #280 (550afeb) into develop (1aa8b2e) will increase coverage by 0.05%.
The diff coverage is 95.16%.

@@             Coverage Diff             @@
##           develop     #280      +/-   ##
===========================================
+ Coverage    88.40%   88.46%   +0.05%
===========================================
  Files           49       49
  Lines         4383     4438      +55
===========================================
+ Hits          3875     3926      +51
- Misses         508      512       +4

Impacted Files
Coverage Δ

sentinelhub/download/session.py
96.36% <94.54%> (-1.89%)
:arrow_down:

sentinelhub/_version.py
100.00% <100.00%> (ø)

sentinelhub/download/__init__.py
100.00% <100.00%> (ø)

sentinelhub/download/sentinelhub_client.py
93.61% <100.00%> (+0.13%)
:arrow_up:

sentinelhub/data_collections.py
93.03% <0.00%> (-0.41%)
:arrow_down:

Continue to review full report at Codecov.

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


ilab serve doesn't warn that model name doesn't have expected model family name

Describe the bug

When ilab serve is used with custom model file, it should warn that model family name cannot be extracted and correct template cannot be selected.
To Reproduce
Steps to reproduce the behavior:
cp models/merlinite-7b-lab-Q4_K_M.gguf models/my-little-model.gguf
ilab serve --model-path models/my-little-model.gguf
ilab chat --model models/my-little-model.gguf -qq "hello" -gm

Expected behavior
Warning that no template would be applied as model family name cannot be extracted
Screenshots
Output:
<|system|>_type = {
    '1': '单人',
    '2': '双人',
    '3': '三人',
    '4': '

Device Info (please complete the following information):

Hardware Specs: Lenovo T14s
OS Version: Fedora Linux 40
Python Version: Python 3.12.3
InstructLab Version: ilab, version 0.16.0

Additional context

Fixed by https://github.com/instructlab/instructlab/pull/1297


Fix xeus-cling CPP kernel and Bumpup version

test:

Thanks for that, can you rebase it on the current master? Maybe that will fix the tests.

@guaraqe Please check out, make sure if you would like to enable the option of unsupportSystem to build on Darwin

@guaraqe Please check out, make sure if you would like to enable the option of unsupportSystem to build on Darwin

Can you send me a reference for this flag? It's the first time I see it.


automatic segmentation error

It is a very nice code! I successfully run the points and box prompt code. However, there is some problem with the automatic segmentation. When I press "a" to run automatic segmentation in VS Studio2019, it returns an error window:

Can you help me with it?
btw, this is the program window to show some information for reference:

Thank you!

Have you used CrashDumps files to investigate where the error occurred, such as identifying the line of code?


Plugin doesnt work with gradle > 4.8 (using packages with java-source throws ClassNotFoundException's)

It seems to throw ClassNotFoundExceptions for used packages with classes included in the java-source stanza.
Reported by @politrons in https://github.com/typelead/eta/issues/904

The workaround is to use gradle 4.7 or 4.8, locally installed or using the gradle wrapper used in examples


Bazel test --batch mode is deprecated

Issue
When running bazel test with the --batch flag, bazel outputs deprecation warning messages. These warning messages can be seen here, in a travis build of master
Following what is stated on the Bazel User Manual, shutdown should be used to explicitly shut down the Bazel server.

Thank you very much!


Update MusicBrainz deletion mechanism

We've changed the way we do this since this was added in 2014, but hopefully it should still be perfectly easy. I don't speak Turkish though, so I can't update the Turkish version.

Removed the Turkish line.
The direct link to removal is username-dependent. account/edit is probably still one of the best ways to get access to a page that links to the delete tab without the user needing to type in their username, which is why I left it :)

Thanks for your contribution!


Scatterplot - Size with timeline

When I use size for scatterplot with time defined two things happen:

If i change the time on the timeline the scatterplot disapears. Only showing when everything is selected.

The axis don't chnage its inicial value. It sums the values of all years. If i change the timeline, for instance, the axis that started with 50 to 100 and I get a value with 20, it gets out of range.

Just found out that i could do this with time fixed and scale linear for x and y. Sorry


cobradocs preview

Based on #60 to merge afterwards.
This adds functionality to preview cobradoc changes
This occurs on PRs opened against either the main branch or release-
branches. The strategy here is to always have the PR consist of two
commits; the first commit is the docs generated against the base ref of
the PR, and the second commit is the docs generated against the head ref
of the PR. It's possible, but unlikely, that the first commit will be
empty, but the second commit will always contain a diff. These preview PRs
should never be merged, anyway.
See https://github.com/ajm188/website/pull/14 and https://github.com/ajm188/website/pull/15 for some demonstrations

I have rebased on origin/main for cleaner files diff preview.


[Debug] Launch In Terminal (Git Bash) does not reuse previous terminal

Issue Type: Bug

set Git Bash as the default terminal
open a python script and set a breakpoint
Debug it and use the restart action(Ctrl+Shift+F5)
I will get many Python Debug Console if I always use the restart action
set PowerShell as the default terminal, the restart action will use the previous terminal

https://user-images.githubusercontent.com/59110636/171585326-47f6b572-e01a-49d1-9e9b-85e76f8a2a54.mp4
Expected: The Git Bash behavior is consistent with Powershell.
VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:15:52.058Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (2 x 2592)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: disabled_offoop_rasterization: unavailable_offopengl: enabled_onrasterization: unavailable_offraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
2.00GB (0.70GB free)

Process Argv
--crash-reporter-id 7d2f941a-b3b6-47a7-b44c-4108b937d761

Screen Reader
no

VM
100%

Extensions (4)

Extension
Author (truncated)
Version

vscode-language-pack-zh-hans
MS-
1.67.3

python
ms-
2022.6.3

vscode-pylance
ms-
2022.2.4

jupyter
ms-
2022.4.1021342353

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
vsclangdc:30486549

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Refactoring: introduce IntrospectionStrategy in the recursive comparison

Summary
The recursive comparison would benefit from a clear introspection strategy when gathering the field to compare and getting their values.
The recursive comparison is a bit inconsistent, it introspects fields to get the list of fields to compare but uses a different strategy to read their values by looking first to a getter then reading the field directly or looking for a map value (key being the field name).
The IntrospectionStrategy would define what to compare and how to read the values to compare.
This is needed for https://github.com/assertj/assertj-core/issues/2108 and https://github.com/assertj/assertj-core/issues/2149

@nach-o-man could you please comment here so I can assign the issue to you?

Comment


Drop hide-readme-header feature

GitHub is shipping new features like crazy! The latest feature is table of contents for README.
Well, not quite polished yet...

While hide-readme-header doesn't interfere with this feature, I see some reasons to drop it:

Doesn't look nice (We avoid orphans)

Currect
  	Default

Doesn't save any space

This is just to raise concern though, I don't think any action should be taken right now. Some other thoughts:

If it only works on repo home and for README only, can we extend it to support all Markdown files as well?

That feature is great! Makes me wonder if we should drop collapse-markdown-sections instead.

I thought about it as well, but collapse-markdown-sections serves more purposes than a regular table of contents. For example you can take a screenshot with some sections folded to put the content you want in a single screen.

Maybe pull the button out to the left of the readme?

Rough CSS:
#readme > :first-child {
  height: 0;
  padding: 0 !important;
  border: none !important;
}
#readme > :first-child details {
  position: absolute;
  left: -4em;
  top: 1em;
}

Alternatively, the space could be used to display the current header (or header breadcrumbs)

For example you can take a screenshot with some sections folded to fit the content you want into a single screen.

Sounds niche and I’m not convinced 🤔

Maybe pull the button out to the left of the readme

Doesn't seem worth the hassle and now the header is better than when the feature was introduced:

2 buttons
white background
fixed header

Maybe we could just reduce the padding to make it smaller, from .p-3 to .p-1 + some extra padding on the right side.

Just noticed the header title now points to #readme (I don't remember whether it's there before the table of contents), serving as a quick way to go to the top of the README.

Semi-related: I wonder why this issue still exists 🤔

Likely due to sticky-sidebar

The feature is expanded to all markup files. Sweet!


Set config.eager_load = true when on CI

Motivation and Context

When reviewing dependabot PRs, I noted a suggestion that setting config.eager_load = true sped up tests on CI. I've opened this PR to try that out.
Your Changes

Description: Updated config/test.rb to set this option when on CI.
Type of change (select all that apply):

[x] Other (please specify):

Testing

Opened this PR and reviewed test run timing.
Questions and Comments (if applicable)

Checklist

[ ] I have performed a self-review of my own code.
[ ] I have verified that the pre-commit.ci checks have passed.
[ ] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported on Coveralls.
[ ] I have added tests for my changes.
[ ] I have updated the Changelog.md file.
[ ] I have made changes to the documentation and linked to that pull request below.

Pull request to make documentation changes (if applicable)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 91.632%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
38834

Relevant Lines:
41759

💛  - Coveralls

Update: didn't seem to speed up tests much. Closing.


AwsCommunity::S3::BucketNotification

AwsCommunity::S3::BucketNotification
Tracking Issue
One of the top requests in the CloudFormation coverage roadmap repo is AWS::S3::BucketNotification, a resource that would solve the well-documented circular dependency issue that prevents a notification configuration from being created at the same time as the bucket and the queue, topic, or function that is receiving the notification.
This resource is an attempt to solve that problem externally with a public registry extension. While ideally the resource would be created as an integral part of the AWS::S3::Bucket resource, solving it here can serve as an example of what is possible with third party resource types. We also need a resource to use as a pilot for our build and release process.
Schema design

Id
Events
Filters
BucketArn
TargetArn
TargetType

This resource differs from the original in that you only configure one notification at a time. The resource handles the SDK calls to configure all notifications for the bucket, making sure not to change or delete any of the pre-existing notifications. It also creates the necessary role for S3 to access the target.
Sample template
Resources:
  Queue:
    Type: AWS::SQS::Queue
  Bucket:
    Type: AWS::S3::Bucket
  Notification:
    Type: AwsCommunity::S3::BucketNotification
    Properties:
      Id: MyNotification
      Events:
        - s3:ObjectCreated:*
      Filters:
        - Name: suffix
          Value: gif
      BucketArn: !GetAtt Bucket.Arn
      TargetType: Queue
      TargetArn: !GetAtt Queue.Arn
    DependsOn:
      - Bucket
      - Queue

Downsides
This resource intentionally introduces drift by altering the notification configuration on the bucket.

We can't actually publish this resource currently. The cfn-test command does not allow any IAM resources other than PassRole to be created. We are working on removing that restriction by requiring the CAPABILITY_IAM flag on stack creation.


Update config.yml

What I Did
Make tests that integrate with g.replicated.com opt-in
How I Did it
Check if the required token is set, else skip
How to verify it
Build from a fork that does not have the variable set
Description for the Changelog
Ship integration testing in CI no longer requires a token to access g.replicated.com. These tests will still be run if the token is set in the build environment.

I think I'd rather split the integration task into two - one for init_app or anything else that ends up requiring an env var, one for all the rest
That way we can keep integration a required test, and just ignore the failing integration-secrets test
That sort of thing

I think we'd rather have this fail silently, then fail explicitly but not block merging. The latter encourages merging in the face of ❌


#90: Fixed implementation of ParseGraph#containsValue().

Fixed implementation of ByOffset#getLowestOffsetValue(ParseGraph). Fixed failing tests.

Current coverage is 99.15% (diff: 100%)

Merging #91 into master will increase coverage by <.01%

@@             master        #91   diff @@
==========================================
  Files            81         81
  Lines          1049       1059    +10
  Methods           0          0
  Messages          0          0
  Branches        186        191     +5
==========================================
+ Hits           1040       1050    +10
  Misses            1          1
  Partials          8          8

Powered by Codecov. Last update 505f1fc...4f227b5


Sync zds 1.10 fixes to master branch

Is there a related issue for this PR?
Issue number:
Developer's Certificate of Origin (DCO)

Signed-off-by: nannanli<EMAIL_ADDRESS>

This looks great - thank you @nannanli  and @PlutoZhang.  Apologies I didn't get to review it ealier but we had a long 4 day vacation weekend here in the UK around Easter Sunday where we get Friday and Monday of work.


Added duplicateQueryParameters method from docs to URI.js.

urijs/URIjs.d.ts
to authors(@RodneyJT @xt0rted). could you review this PR?
:+1: or :-1:?
check list

[ ] pass the Travic-CI test?

Aside from the merge commit this looks good.

thanks mate!


Move to boost::stacktrace

backward-cpp is currently our only dependency which is not managed by vcpkg. Replacing it with boost means we can be be 100% reliant on vcpkg. In addition it should be an easy migration to <stacktrace> in c++23

Moving to Deep-Freeze as boost stack trace does not support collecting back traces from signal handlers (eg from SIGSEGV)


Close #360 : Revert to IPv4 debug port binding if IPv6 fails

Checklist

[X] I have viewed, signed, and submitted the Contributor License Agreement.
[X] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[X] I have added an integration test, if necessary.
[X] I have reviewed the styleguide for guidance on my code quality.
[X] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

we decided to rather rely on the "/sys/module/ipv6/parameters/disable" value to not risk startup slow downs, see #366


Can't print special characters.

So I've tried printing the example from the latin1 codec (since this plugin is already using it), which is: 'blåbærgrød'.
So: printer.println('blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.pc865));
Setting the code table doesn't seem to help, no matter which code table is chosen.
It fails printing æ ø å, which is wierd since it's literally that example they show inside the latin1 codec.

Hi,
You have to use westEur code table along with latin1 codec:
printer.println('blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.westEur));
For the pc865 a new codec should be written.
Could you please test it?
Hope it helps!

Sorry I should have mentioned that westEur was the first thing I tested with. It outputs the exact same string. I've tried setting the code table to various values, just to see if the characters change, which they do not. I know the printer (Epson) supports lots of code tables, as I've previously written my own thermal printer library in javascript for it.

That's weird...
Here is my test:
printer.println('westEur: blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.westEur));
printer.println('pc865: blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.pc865));
printer.println('greek: blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.greek));

And the result is:

Your output is different?
PS: I'm using an Xprinter XP-N160I.

Here's my complete code:
Printer.connect('<IP_ADDRESS>', port: 9100).then((printer) {
   printer.println('blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.westEur));
   printer.cut();
   printer.disconnect();
});

It always outputs your second line of printing, for whatever reason.
My printer is an Epson TM-T20, model M249A.

Could you please post here the output of the following code (consider using the latest library version, a bug in printCodeTable method has just been fixed):
printer.println('westEur:');
printer.printCodeTable(codeTable: PosCodeTable.westEur);
printer.println('\n\npc865:');
printer.printCodeTable(codeTable: PosCodeTable.pc865);

Here's the commands, and the output as an image:
printer.println('westEur:');
printer.printCodeTable(codeTable: PosCodeTable.westEur);
printer.println('\n\npc865:');
printer.printCodeTable(codeTable: PosCodeTable.pc865);
printer.println('\n\n');
printer.println('blåbærgrød', styles: PosStyles(codeTable: PosCodeTable.westEur));

Managed to get an € printed using:
printer.sendRaw([0x1b, 0x74, 0x10, 0x80]);
I set the code page to 1252, and 0x80 is € in this code page.

Thanks for listening. I think I'll just write a layer that sends raw data to the printer. 👍

Hi @larssn ,
Does the issue persist?
Are you using the latest version of the library?
Btw, I've created a list of printers tested with this library.
May I ask you to add your printer model into the table with any comments (what works and what doesn't)?
It will help me to maintain the library and others to choose the right printer!
Thank you!


Can I get an invite to slack?

<EMAIL_ADDRESS>is my email address
I'd like to get some guidance on areas of improvement as we are making pretty heavy use of the library and have identified a handful of things that were confusing but would like some guidance on where to put our effort.

You should have mail.

Thank you @martinwag!


Reformat to make it look more graceful

Signed-off-by: Wen Cheng Ma<EMAIL_ADDRESS>

LGTM. Thanks @wenchma!
ping @moxiegirl

Thanks @wenchma! Since you're reformatting, can you also use markdown for manager0 and consul0?

@nishanttotla  I already markdown manger0 and consul0, PTAL :smile:

@wenchma Thanks for discovering the problems and providing a fix. I found a few more and combined your change with my fixes.

@moxiegirl yes, yours looks better to fix more, :+1:


Python/PubSub: update_subscription and update_snapshot examples are wrong

The example subscription object doesn't have a 'name' field.  Same with update_snapshot. Where can we find these code samples? I've looked through this repo and wasn't able to find them.
Cross-posted bug in Python/PubSub.

Looks like the template code for method samples is in this file: https://github.com/googleapis/gapic-generator/blob/77fe13498b62ee75be88cdfbcd17b8a6dbd821c6/src/main/resources/com/google/api/codegen/py/method_sample.snip#L4-L10

This generator is no longer used for Python, please use gapic-generator-python instead.

TIL parts of the monolith are still used for Python, reopening.


Scrapli is no able to use windows to ssh to device

I am able to ssh from powershell but when i run scrapli i get the following error.
Please advise
from datetime import datetime
from scrapli.driver.core import IOSXEDriver
my_time = datetime.now().strftime("%H:%M:%S")
command_to_send = input("Please Entet the command you would like to send:")
my_device = {
"host": "<IP_ADDRESS>",
"auth_username": "marley",
"auth_password": "dude",
"auth_strict_key": False,
"port": 22,
}
with IOSXEDriver(**my_device) as csr_devnet:
result = csr_devnet.send_command(command_to_send)
print(result)
PS C:\Users\marle\Documents\Python> & C:/Users/marle/AppData/Local/Programs/Python/Python312/python.exe c:/Users/marle/Documents/Python/scraplii.py
Please Entet the command you would like to send:sho run
Traceback (most recent call last):
File "c:\Users\marle\Documents\Python\scraplii.py", line 20, in
with IOSXEDriver(**my_device) as csr_devnet:
^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\driver\core\cisco_iosxe\sync_driver.py", line 130, in init
super().init(
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\driver\network\sync_driver.py", line 51, in init
super().init(
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\driver\generic\sync_driver.py", line 50, in init
super().init(
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\driver\base\sync_driver.py", line 15, in init
super().init(**kwargs)
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\driver\base\base_driver.py", line 199, in init
self.transport = transport_class(
^^^^^^^^^^^^^^^^
File "C:\Users\marle\AppData\Local\Programs\Python\Python312\Lib\site-packages\scrapli\transport\plugins\system\transport.py", line 60, in init
raise ScrapliUnsupportedPlatform("system transport is not supported on windows devices")
scrapli.exceptions.ScrapliUnsupportedPlatform: system transport is not supported on windows devices
PS C:\Users\marle\Documents\Python>

raise ScrapliUnsupportedPlatform("system transport is not supported on windows devices")
scrapli.exceptions.ScrapliUnsupportedPlatform: system transport is not supported on windows devices

also from the readme: Although many parts of scrapli do run on Windows, Windows is not officially supported


[BUG] Null Pointer Exception on performTrigger

Summary - Calling SocialBotManagerService.performTrigger will lead to a NullPointer exception on SocialBotManagerService.java:1034 line
Bug Details

What? - NullPointerException
Where? - This happens on the develop branch of the Social Bot Framework. The bot is connected via Slack
When?/How often? - It occurs every time  a user messages the bot
How?/Current state -
I cloned the Mensa Service and created my own branch called  chatbotCCA.  I created a bot using the Social Bot Framework on the modeling space called mensabot.  I configured a bot action which should trigger a function called getDefaultMenu on the path http://<IP_ADDRESS>:8080/mensa/default. I deployed the bot to my local instance of the Social Bot Manager Service. The bot is connected to Slack. I wrote a message to the bot, asking it for menu. The intent menuDefault is correctly recognized which should in theory trigger the mensa service funtion. However this results in a NullPointerException and the mensa service is never called.

Bot MensaBot triggered:
[]
null
default
MensaBot    pass actingAgent
botagent is b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e
mensanull ; {"msg":"menu","botName":"b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e","channel":"D01920S699A","intent":"menuDefault","email":null,"contextOn":true} null null My string iss:{"msg":"menu","botName":"b4a9aded5f657ae757c823c78ccad693d34f913d16330cb6dc1ae98a39c26a9133b54e5cafcfaedc9fb1d170a008f69861e60eedcf08d490060ff7ab3720843e","channel":"D01920S699A","intent":"menuDefault","email":null,"contextOn":true}
java.lang.NullPointerException
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService.performTrigger(SocialBotManagerService.java:1034)
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService.performIntentTrigger(SocialBotManagerService.java:770)
        at i5.las2peer.services.socialBotManagerService.SocialBotManagerService$BotResource$2.run(SocialBotManagerService.java:644)
        at java.lang.Thread.run(Thread.java:748)
Intent processing finished.

Tried the service myself and @Produces(Type) was missing in the getMenuDefault. After adding (and checking with @lakhoune) worked fine. Closing.


hypercli: don't setup workdir for container by default

otherwise hyperd will ignore the workdir value got from
docker inspect image.
Signed-off-by: Gao feng<EMAIL_ADDRESS>

LGTM!


Add support for IPv6 bare address aliases.

Coverage decreased (-0.3%) to 77.959% when pulling c960bd8b1630e58c58cdd1e678fced214967b98c on kgoodier:ipv6-aliases into 4ab542e9e6f38cdf8ab29d666eecd545fb046d71 on twitter:develop.

+2


Install fails on Windows. Is it not supported?

Complete output from command python setup.py egg_info:
cl : Command line error D8021 : invalid numeric argument '/Wfatal-errors'
Compiling vendor static library ...
Traceback (most recent call last):
  File "c:\users\eugene.niemand\appdata\local\programs\python\python35-32\lib\distutils\_msvccompiler.py", line 395, in compile
    self.spawn(args)
  File "c:\users\eugene.niemand\appdata\local\programs\python\python35-32\lib\distutils\_msvccompiler.py", line 514, in spawn
    return super().spawn(cmd)
  File "c:\users\eugene.niemand\appdata\local\programs\python\python35-32\lib\distutils\ccompiler.py", line 909, in spawn
    spawn(cmd, dry_run=self.dry_run)
  File "c:\users\eugene.niemand\appdata\local\programs\python\python35-32\lib\distutils\spawn.py", line 38, in spawn
    _spawn_nt(cmd, search_path, dry_run=dry_run)
  File "c:\users\eugene.niemand\appdata\local\programs\python\python35-32\lib\distutils\spawn.py", line 81, in _spawn_nt
    "command %r failed with exit status %d" % (cmd, rc))
distutils.errors.DistutilsExecError: command 'C:\\Program Files (x86)\\Microsoft Visual Studio 14.0\\VC\\BIN\\cl.exe' failed with exit status 2

There are a few small tweaks that has to be made to build on windows, like removing some C99 features that are currently used and not supported by the required versions of MSVC, and handling compiler specific flags for different platforms (like the one it is failing on in your traceback fatal-errors which is a gcc flag).
The thought also was taking advantage of the platform specific Wheels builds for Windows so that compilation would not be necessary.  I will be looking into those and commenting back as I move forward with add Windows platform-specific support.

Thanks. Maybe add supported platforms or limitations to the home page.
Would have saved me a few hours.
On Sun, 3 Jul 2016 at 19:09, Chris<EMAIL_ADDRESS>wrote:

There are a few small tweaks that has to be made to build on windows, like
removing some C99 features that are currently used and not supported by the
required versions of MSVC, and handling compiler specific flags for
different platforms (like the one it is failing on in your traceback
fatal-errors which is a gcc flag).
The thought also was taking advantage of the platform specific Wheels
builds for Windows so that compilation would not be necessary. I will be
looking into those and commenting back as I move forward with add Windows
platform-specific support.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ChrisRx/quickavro/issues/1#issuecomment-230166848,
or mute the thread
https://github.com/notifications/unsubscribe/AGf2fdSyP4SC5HSh_Rpf-LiUJpkPuMrNks5qR_rLgaJpZM4JC_ho
.

I am truly sorry to hear about your lost time, however, I stated this is alpha quality and I'm still currently in the process of adding some platform independence features (I only added single source Python 2/3 like a week ago).  As support for other platforms is added, implicitly or otherwise, those are going to be added to any documentation.
I'm keeping this issue open to report back the progress on Windows platform builds, and close it upon initial Windows platform support.  Hopefully it won't be any issue to have a Windows binary Wheel be built and upload to PyPi so that this will not be difficult for Windows installation in the future.

There are some things I'm trying to do that will make quickavro more cross-platform friendly, but at this time, the Windows compiler just isn't up to the task of compiling these C/C++ dependencies with c-avro.  This will unfortunately mean writing my own avro implementation in C, but at the point that happens, I will hopefully be able to comment back in this issue and indicate that better Windows support can be provided.


Commit to Dev Branch

Code cleanup
Small UI tweaks
Introduction of file uploader

Let me know your thoughts on the file uploader.  It was easy to implement on the front end, but I'm not sure how difficult it will be on the back

Whenever I've done something with file uploading I kinda wished I didn't have to do it because it's a pain. ;) But I'll take care of it. It makes sense, especially for uploading custom icons for HASS.
Another thought: How about moving the Icons for creating new elements below the fbheader? Like a filebrowser toolbar. Could look cluttered in the end, bzt maybe worth a test, and would make more sense to have the buttons there. Maybe though an extra save-button that pops up a modal like for the folders and just asks for the name. The current save-button makes use of the long filename-input, which I find useful to spontaneously creating a new file. But creating a new file from the file-browser could behave differently and actually just create the file, refresh the folder content, but not open anything in the editor. What you think about that? :)

It's funny that you say that, because that's exactly what I've been working
on.  I have them in there on my local copy, it's just not pretty yet.
On Tuesday, February 14, 2017, Daniel Perna<EMAIL_ADDRESS>wrote:

Whenever I've done something with file uploading I kinda wished I didn't
have to do it because it's a pain. ;) But I'll take care of it. It makes
sense, especially for uploading custom icons for HASS.
Another thought: How about moving the Icons for creating new elements
below the fbheader? Like a filebrowser toolbar. Could look cluttered in
the end, bzt maybe worth a test, and would make more sense to have the
buttons there. Maybe though an extra save-button that pops up a modal like
for the folders and just asks for the name. The current save-button makes
use of the long filename-input, which I find useful to spontaneously
creating a new file. But creating a new file from the file-browser could
behave differently and actually just create the file, refresh the folder
content, but not open anything in the editor. What you think about that? :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielperna84/hass-poc-configurator/pull/18#issuecomment-279722381,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcJCNIWH8Z16Frl0KvxFGreLsrdj9tOks5rcbrkgaJpZM4MAg4M
.

Ok, then I'll wait and see what you come up with. :)

I took the time to finish the new toolbar in the filebrowser. Creating a new file now uses a modal and works because of an update to configurator.py. File uploading is still to do.
Besides that I have set a consistent color for the elements in the filebrowser. Now they all are the same grey. Except the folder-name, which looks brighter. Might have forgotten that one.

Looks good!   It's generally working, although it's always ending up in the base directory. Gonna fix that tomorrow though.

I've changed the green validation underline to blue for consistency.  CSS has been rearranged some to help keep everything "grouped" now that it's getting quite large.
Upload is working awesome, but like you said, they land in the root.  I also noticed that we aren't getting a success or failure dialog, though you probably already know this :)

Uhm, there should be a toast saying it was successful or not. For me it was working.

Hmm, strange
Does this error help at all?

I have tried with your latest commit included and it still works for me. Tried both on Windows and Linux. Could you try it without SSL? Even though I don't know why it should matter.

Tried without SSL, no dice.  Not sure what could be causing this strange issue, maybe something with my HASS install?

Just to clarify: the upload works and it's just the popup that's missing?

That's correct, the file uploads, but it appears to "crash" after that.  I don't get the popup nor the filebrowser list refresh

Ok. I'll be at home in about an hour and see if I somehow manage to reproduce that.
What you  could try until then: do other popups still work? Like "File saved successfully" etc?

Sounds good, I'm going to backup my current setup and run the AIO HASS installer again
Yup everything else is working great

HASS reinstall went south on me, had to restore a backup.  I'll give it another go when I get home

I think I may have found the bug. I didn't send the required headers along with the response. Although I wonder why I don't get the same error. Anyhow, headers are now added. Take your time to get your system working again, then test. :)

Works perfect now!
I'm think a clearing of the file name from the upload input after success would be a good idea too

Yes, makes sense to do that. I'm also almost done with uploading to different locations.

Done. Feel free to test. For me it works on my Windows machine and on a PI.
Next thought: Download-button next to delete, which allows do download the raw file instead of trying to open it in the editor.

Great idea!
On Wednesday, February 15, 2017, Daniel Perna<EMAIL_ADDRESS>wrote:

Done. Feel free to test. For me it works on my Windows machine and on a PI.
Next thought: Download-button next to delete, which allows do download the
raw file instead of trying to open it in the editor.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/danielperna84/hass-poc-configurator/pull/18#issuecomment-280148730,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcJCN0r8xBV5fGJa28qUpdhCyVCuCy2ks5rc3E3gaJpZM4MAg4M
.

Downloading implemented.

Added basic git functionality. If we're inside a repository, the active branch is displayed under the directory path. Additionally, modified files are red or green, depending on if they are staged for commit or not.
The git integration requires GitPython to be installed. If it's not installed, everything should look as usual. Can you verify it's running without GitPython installed (assuming you haven't got it installed)?

You are correct, I don't have it installed.  All appears well, tested:

Creating file
Saving changes to a file
New folder
Deleting files
Deleting folders
Clearing current file

Great. Is there anything you have on your agenda, or can I just proceed further with git-integration and we'll make a new release when I'm done?
By the way: if you don't mind, you could install the git module so you can also see what's happening there. Installation is really easy: pip3 install gitpython, then (re)start the configurator.
Then, for testing clone some repo (like this one: git clone https://github.com/jmart518/hass-poc-configurator.git) somewhere onto the machine and navigate to it using the filebrowser.

Excellent, proceed with the git integration.  In the mean time, I'll install gitpython today and do some testing

I guess I'm done for the next version. Files are now colored depending on git status, they can be added to the index, and a commit of all staged changes can be performed as well.
Future features could be:

Create a repository in the current directory
Switch branches
Create new branches
Show diff compared to last commit (don't know if that's possible though)

One "bug" I leave to you to fix: the dropdown-button for git commit (yes, they're lower caps on purpose, like the shell commands) isn't properly aligned. Should be displayed like the menu-buttons for the files.

Awesome stuff!
  I'll fix that up in the next hour, gotta finish some work real fast

No need to rush. Bedtime for me now. ;-)

Before you go, what are your thoughts on changing the BG color of the FBToolbar?  I feel like it gives a little separation between it and everything below.
Also, even though I like the new icon for the file browser (lines) I keep thinking we need to change it.  Mainly since HASS already has the similar icon and it just looks kind of odd to me

You can change the color and I'll have a look at it. If it' looking good we'll go with it.
You can change the icon as well. I just found the lines to represent more of what's going to be displayed when it's clicked. But to me it doesn't matter much. So feel free to change that.

Looking good. The only thing that's probably a leftover: $('.dropdown-button2'). There are no elements that have that class.
Is there anything else you want to get into the next version, or are we ready to publish this? :)

That is the last change I wanted to sneak in, merge away good sir


CIP-0010 Discussions

Moving discussions from https://github.com/cardano-foundation/CIPs/pull/906 over here.
from @perturbing and @rphair

That said, I do wonder how this will pan out in the future, as there is no clear guideline.
Furthermore, currently labels are forever, are all registered labels still actively used?
think that CIP-0010 might benefit from an update with whatever clarification might be necessary as project tag requests start coming in again.
I think one addition to CIP-010 could be the addition of the test that there is a reasonable chance that others (people/tooling etc) observing this metadata might want clarity. For example, any project that has an app where users connect their wallet, the wallets might want to leverage the knowledge of this CIP. But applications that are isolated (for whatever reason), do not (liquidation on a lending protocol for example).
We could hash (even with a VRF if needed for proper randomness), their PR, and modulo reduce it to fit in the range and have that as their number

@Ryun1 personally I don't have any dispute with the way things are done today since we have a lightweight system that relies upon a minimum of work.  But I don't consider the current informal system to be future-proof either.
I do think the great majority of the current labels will never be used.  Beyond that, the easy process to obtain official labels with company name & web site represent a potential for misuse to convey a false legitimacy.
Because of the uncertainty I think it would be best to put this & your list of questions out to the wallet dev community... since they produce most of the tooling that would interpret this metadata.  What definition of legitimacy and longevity would they prefer & what would they look for in the validation process and registry format?

p.s. asked on Discord to the Wallets Working Group here.


Remove allocs and use of parent in HS tendency

By removing parent, reshape and the field allocation, this PR improves

Readability
Generalization and
Allocations
threaded performance

Requires CC#959. This will also allow us to start fusing this function with other additional_tendency! functions, further improving our thread scaling

bors r+


Predict from string

Hello!
Is there a function that takes a string as input and outputs the list of the most relevant functions based on the models ?
Thank you !

Maybe the function here is what you're looking for?


[Pulsar Functions] Allowed to subscribe from an arbitrary point in time

Is your feature request related to a problem? Please describe.
In some times, user wants a specific subscription-position for input-topic consumer in Pulsar Functions.
Describe the solution you'd like

Add SubscriptionInitialPosition param in create consumer for input topics.
Add seek logic, allowed to subscribe from an arbitrary point.

@wolfstudy will add feature and docs requested from @candlerb .


AWS KMS - support credentials from service-accounts (EKS)

Is your feature request related to a problem? Please describe.
This issue separates out one of the two enhancement requests described by #1282.
Currently the proxy requires a long-lived AWS access key/secret key combination to authenticate to AWS.   Whilst this
authentication is supported, as it not seen as the most secure option.
For use cases when the proxy binary is running in Amazon EKS, the preferred approach is for the IAM roles to be attached to a service account.  The service account OIDC token can then by retrieved by the application and exchanged for temporary credentials from AWS Security Token Service.  These temporary credentials can then be used to interact with the AWS API.
Describe the solution you'd like
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

EKS

if the proxy binary is running in Amazon EKS, IAM roles can be attached to service accounts but I don't see in the AWS docs a reference to how those credentials can be retrieved outside of using the AWS SDK.

I understand that  the IAM role gets attached to the Kubernetes service account.  The pod using the service account is then able to operate with permission granted by the IAM role against the AWS API.  The AWS docs talk about how the AWS SDK works:

To use the credentials from IAM roles for service accounts, your code can use any AWS SDK to create a client for an AWS service with an SDK, and by default the SDK searches in a chain of locations for AWS Identity and Access Management credentials to use. The IAM roles for service accounts credentials will be used if you don't specify a credential provider when you create the client or otherwise initialized the SDK.
This works because IAM roles for service accounts have been added as a step in the default credential chain. If your workloads currently use credentials that are earlier in the chain of credentials, those credentials will continue to be used even if you configure an IAM roles for service accounts for the same workload.
The SDK automatically exchanges the service account OIDC token for temporary credentials from AWS Security Token Service by using the AssumeRoleWithWebIdentity action. Amazon EKS and this SDK action continue to rotate the temporary credentials by renewing them before they expire.

It sounds possible for the KMS integration to follow the same approach, but this needs to be validated.
We also want to understand how similar/different things are for ROSA.

https://docs.openshift.com/rosa/authentication/assuming-an-aws-iam-role-for-a-service-account.html

For OpenShift on AWS (OSD) I found only this.

https://www.redhat.com/en/blog/running-pods-in-openshift-with-aws-iam-roles-for-service-accounts-aka-irsa