fix: Data-Analytics-Workspace - Several smaller adjustments to enable testing

Description

Disabled purge protection
Renamed resources
Added dynamic element to deployment names
Upgraded used module versions & applied required updates
Replaced Lock UDT with import

Pipeline Reference

Pipeline

Type of Change

[ ] Update to CI Environment or utilities (Non-module affecting changes)
[ ] Azure Verified Module updates:

[x] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in version.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in version.json.
[ ] Breaking changes and I have bumped the MAJOR version in version.json.
[ ] Update to documentation

Lgtm
@jbinko please have a look when you get some time 🙂


[localstack] Add testcontainer marker labels to additional localstack flags

This PR steps in the footsteps of #8595 and #8844, and sets the testcontainer labels for spawned containers for ECS, EC2 and batch services as well.
There may be another option in the future to set docker flags for all services in one config variable, but for backwards compatibility, and since it is unclear when this work will be, it makes sense to still set the flags right now.
This should avoid leftover containers for other LocalStack compute services in addition to Lambda.

Thanks for your contribution, @dfangl !


[Docs] moco v3 No print loss

📚 The doc issue
No loss was printed while training with moco v3 today
Suggest a potential alternative/fix
Because of too little data set can't print, can be in mmselfsup/configs/selfsup/base/default runtime. Py modify logger = dict (type = 'LoggerHook', the interval = 5)

Hi, the default log interval in default_runtime.py is 50, you can customize it by yourself if your dataset is too small.


Remove configuration reference from variant feature flag

Why this PR?
#489
Visible changes
configuration_reference is not longer supported.

@mrm9084 @zhiyuanliang-ms, just to confirm, we don't have this in the FM of other languages either, right?

Python had it: https://github.com/microsoft/FeatureManagement-Python/pull/37


nix-index - not work

Issue description
Error running nix-index
nix-index --show-trace
+ querying available packages
error: querying available packages failed
caused by: nix-env failed with error: nix-env failed with exit code 1:
error: while querying the derivation named 'gnome-keyring-0.3.1':
while evaluating the attribute 'buildInputs' of the derivation 'gnome-keyring-0.3.1' at /nix/store/haik8pamsqnpxzkphxqf98njm2jwx625-nixos-18.09pre149049.9968d0f053c/nixos/pkgs/stdenv/generic/make-derivation.nix:175:11:
while evaluating 'getOutput' at /nix/store/haik8pamsqnpxzkphxqf98njm2jwx625-nixos-18.09pre149049.9968d0f053c/nixos/lib/attrsets.nix:451:23, called from undefined position:
while evaluating anonymous function at /nix/store/haik8pamsqnpxzkphxqf98njm2jwx625-nixos-18.09pre149049.9968d0f053c/nixos/pkgs/stdenv/generic/make-derivation.nix:113:17, called from undefined position:
attribute 'gnome-keyring' missing, at /nix/store/haik8pamsqnpxzkphxqf98njm2jwx625-nixos-18.09pre149049.9968d0f053c/nixos/pkgs/development/haskell-modules/hackage-packages.nix:85145:10

Technical details

system: "x86_64-linux"
host os: Linux 4.14.62, NixOS, 18.09pre149049.9968d0f053c (Jellyfish)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1pre6338_45bcf541
channels(root): "nixos-18.09pre149049.9968d0f053c"
channels(user): "nixos-18.09pre149002.cfa49751c7f"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Looks like this is not an issue with nix-index. It seems to be caused by a reference to non-existing gnome2.gnome-keyring from haskellPackages.gnome-keyring in pkgs/development/haskell-modules/hackage-packages.nix.
@peti @basvandijk

The broken reference is fixed in the haskell-updates branch, so this issue will be resolved once we merge that update. Meanwhile, I've committed a quick fix to master.


Add export feature implementation details in DG

Add export feature implementation details in DG under section 3 Implementation

Codecov Report

Merging #88 into master will increase coverage by 2.44%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master      #88      +/-   ##
============================================
+ Coverage     69.85%   72.29%   +2.44%
- Complexity      441      454      +13
============================================
  Files            79       79
  Lines          1463     1462       -1
  Branches        151      151
============================================
+ Hits           1022     1057      +35
+ Misses          397      359      -38
- Partials         44       46       +2

Impacted Files
Coverage Δ
Complexity Δ

...va/seedu/address/logic/commands/ExportCommand.java
84.21% <0.00%> (+84.21%)
11.00% <0.00%> (+11.00%)

...eedu/address/logic/parser/ExportCommandParser.java
100.00% <0.00%> (+100.00%)
2.00% <0.00%> (+2.00%)

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 01f52af...2fe2492. Read the comment docs.


key_update test fail after integrate #166

@vinmaciel, would you please take a look and let us know if it is expected or not?
REF: https://github.com/DMTF/libspdm/pull/166
[  ERROR   ] --- 0x8000000000000007 != 0x8000000000000010
[   LINE   ] --- C:\home\DMTF\libspdm\unit_test\test_spdm_requester\key_update.c:4143: error: Failure!
[  ERROR   ] --- 0x8000000000000007 != 0x0
[   LINE   ] --- C:\home\DMTF\libspdm\unit_test\test_spdm_requester\key_update.c:4216: error: Failure!
[  ERROR   ] --- 0x3 != 0x0
[   LINE   ] --- C:\home\DMTF\libspdm\unit_test\test_spdm_requester\key_update.c:4279: error: Failure!
[  ERROR   ] --- 0x8000000000000007 != 0x0
[   LINE   ] --- C:\home\DMTF\libspdm\unit_test\test_spdm_requester\key_update.c:4405: error: Failure!
[  PASSED  ] 30 test(s).
[  FAILED  ] spdm_requester_key_update_tests: 4 test(s), listed below:
[  FAILED  ] test_spdm_requester_key_update_case29
[  FAILED  ] test_spdm_requester_key_update_case30
[  FAILED  ] test_spdm_requester_key_update_case31
[  FAILED  ] test_spdm_requester_key_update_case33

Yes, these errors were expected (please, see comment in #166), and should be successful after fixing issue #165.


Fix semantic releases

Semantic release fails with the following message (https://github.com/es-ude/elastic-ai.creator/actions/runs/4721506857/jobs/8374924401):
Notice:  A new release of pip is available: 23.0.1 -> 23.1
Notice:  To update, run: pip install --upgrade pip
The currently activated Python version 3.10.11 is not supported by the project (~3.11).
Trying to find and use a compatible version.

[Errno 2] No such file or directory: 'python3.11'
error: Encountered a bad command exit code!
error:
error: Command: 'python3 -m pip install poetry && poetry build'
error:
error: Exit code: 1
error:
error: Stdout: already printed
error:
error: Stderr: already printed
error:

@glencoe It seems that this error is still there: https://github.com/es-ude/elastic-ai.creator/actions/runs/4808214230/jobs/8557965124

Still broken... (https://github.com/es-ude/elastic-ai.creator/actions/runs/4891279032/jobs/8731641900)

It works again


shotcut: 17.09 -> 17.11

Motivation for this change
update shotcut.
also it would be great have 1a681a6e, 40ed226 and maybe this one cherry-picked into 17.09. :-)
Things done

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

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

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

@GrahamcOfBorg shotcut

Released in 9396fdb3fa8d90b7d453b8b5ba95f6482f9980cf.


fix: mobile drawers and popups hideClose

Summary

Please summarize your changes, describing what they are and why they were made.

This PR does 2 things:

slidable drawers with hideClose=true were closable by sliding them
poups with hideClose=true were closable with the native android button

Additionally, I refactored a bit the function names of BackButtonHeap
Changelog
- Please write a list of changes

Relevant Issues

Please list any related issues using development keywords.

Close #4143
Testing
Platforms

Please select any platforms where your changes have been tested.

Desktop

[ ] MacOS
[ ] Linux
[ ] Windows

Mobile

[ ] iOS
[x] Android

Instructions

Please describe the specific instructions, configurations, and/or test cases necessary to test and verify that your changes work as intended.

...
Checklist

Please tick all of the following boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or modified tests that prove my changes work as intended
[ ] I have verified that new and existing unit tests pass locally with my changes
[ ] I have verified that my latest changes pass CI workflows for testing and linting
[ ] I have made corresponding changes to the documentation

There is an issue at closing the profile menu, maybe the change on the action?

Pushed a fix for this issue https://github.com/iotaledger/firefly/pull/4144/commits/9ca2fa5dcd7888d35fd2b6603b5346ec65c8d03d though I am not sure why use:slidable was disabled for fromLeft drawers.


Jenkins Pipeline improvements: matrix, diff, etc.

[ ] Move the "updatecli" and all the "non helmfile" stages to a preliminary stage (like we do in jenkins-infra/packer-images)
[ ] Use a pipeline matrix to specify the "helmfile" steps (to avoid duplication of code between clusters)
[ ] prints the "diff" generated by helmfile diff ito the pipeline output (so it's available on both github check output and Jenkins's UIs)

Done in #1864


[bug]: console is broken

Do I have the most recent version of AxonOps Workbench installed?

[X] I am using the most recent beta release

AxonOps Workbench Version
v0.1.1-internal-20240913-01
Is there an existing issue for this?

[X] I have searched the existing issues

Operating System
MacOS
Operating System Version
14.6.1 (23G93)
Apache Cassandra Version(s)
4.1.6
Bug Description
Console is broken - getting corrupt results returned

Steps to Reproduce
run a select
Expected Behavior
results get returned
Actual Behavior
corrupt results get returned
Severity
High
Further Information
No response

Fixed, tested on Linux Ubuntu v22

Tested on Windows 10

Tested and fixed on 0.1.1-internal-20240916-01


Up for the bull (sayg) is promoted too early

When score is 2-1 the prompt is shown
Best of 5
Not able to reproduce via the Practice tool
Not able to reproduce via tournament Sayg tool

Unable to reproduce


Standardize mixer and proxy protobuf definitions in istio/api

Currently, mixer uses "Required", while proxy used "REQUIRED". Should be "Required" in both.

Following @ZackButcher's proposal.

similar to target/destination issue? we should get all the renames in before 0.2 ?

please move to istio/api

rshriram@ - if you are using zenhub there is an option to move issues between repos on the right pane (last option). It would be easier to not close and reopen issues.

I was actually looking for such a feature! will look out for that next time. Thanks


Enhance the storage session mechanism

[ ] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[x] Update the CHANGES log.

Re-implement storage session mechanism, cached metrics are removed only according to their last access timestamp,
rather than the first time. This makes sure hot data never gets removed unexpectedly.
Support session expired threshold configurable. And set default to 2.5 min(min level), rather than 70s.

@Ax1an I have changed the default value to 70s.


Edge detection

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[x] ✨ Feature
[x] 🌟 stared the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[x] 🚩 Other

Description
The horizontal and vertical lines could be identified by using the Sobel Operator (Further details mentioned in code). Examples are displayed in below.

Add Link of GitHub Prof
Dulyaaa

Hi @Nitin-Diwakar, can you please check this one?


[bug] JIT, webpack 4 lazyloaded module: Unhandled Promise rejection: Can't resolve all parameters for

Augury version (required): 1.16.2
Angular version (required): 5-6
Date: 17.5.18
OS: arch gnome
Description of issue:
error described here
angular issues

Also seeing this issue

Thanks for reporting. This issue is top priority.

Same problem here when injecting a service into a lazy load module.
ERROR Error: Uncaught (in promise): Error: Can't resolve all parameters for TranslateService: (?, ?, ?, ?, ?, [object Object], [object Object]).

Thanks for the clue, @LuisPalomo.
Can you tell me more about the service you're injecting?

How are you injecting the service? (as a constructor param, with the @Inject() decorator, with this.injector, etc)
What module is providing the service? Is it provided by the lazy loaded module itself?
What are the service's own dependencies? What modules do they come from? Are they also lazy-loaded?

I'm using:
Angular CLI: 1.6.6
Node: 8.4.0
OS: win32 x64
Angular: 5.2.2

The service is the TranslateService from @ngx-translate/core": "^9.1.1
It's injected in the constructor of the root component of the lazy loaded module:
@NgModule({
    imports: [
        ...
        TranslateModule.forChild({
            loader: {
                provide: TranslateLoader,
                useFactory: HttpLoaderFactory,
                deps: [
                  HttpClient,
                ],
            },
        }),
    ],
    providers: [
        ...
    ],
    declarations: [
        PhysicalPersonModificationComponent,
        ...
    ],
})
export class PhysicalPersonModificationModule {}

@Component({...})
export class PhysicalPersonModificationComponent {
    constructor(private translateService: TranslateService) {...}
}

The module that is providing the service is the TranslateModule that is imported in the core module of the app:
@NgModule({
    imports: [
        ...
        TranslateModule.forRoot({
            loader: {
                provide: TranslateLoader,
                useFactory: HttpLoaderFactory,
                deps: [
                  HttpClient,
                ],
            },
        }),
    ],
    providers: [
        ...
    ],
    declarations: [
         ...
    ],
})
export class CoreModule {}

Hope it helps! 👍

Thanks, @LuisPalomo.
Issue replicated with the following conditions:
Lazy loaded module provides a service that has not been previously provided by a parent module, and that requires dependency resolutions.

The issue appears on e.g. Webpack’s hot module reload - maybe especially if you’ve loaded your whole angular app and reflect-metadata polyfill lazily. And as I said - somehow Augury’s internal version of reflect-metadata (backend.js) takes precedence. Thus two different versions of Reflect.metadata APIs are used at consumption time and definition time

We've published a rolled back version (1.16.3) to address this issue, since it seems to affect multiple people. Unfortunately we were not able to reproduce this issue (in a variety of applications). That said, it is likely related to reflect-metadata as pointed out and we have a working solution to avoid this issue moving forward (likely a Canary build tomorrow).

I have had this problem after I have updated the Chrome to 66 version

A new version of the Canary Build (1.17.0) is released, with what we believe might be a fix for this issue.
reflect-metadata has been removed from the bundle. Angular uses reflect-metadata for its JIT compilations, and a versioning conflict was occurring for some users. We now piggyback off of Angular's global reflect-metadata polyfill.
Can you confirm / disconfirm that version 1.17.0 of the Canary Build fixes the issue?

A new version of the Canary Build (1.17.0) is released, with what we believe might be a fix for this issue.
reflect-metadata has been removed from the bundle. Angular uses reflect-metadata for its JIT compilations, and a versioning conflict was occurring for some users. We now piggyback off of Angular's global reflect-metadata polyfill.
@elboukhari , @williamchristophercooley , @s001dxp , @jaj1014 , @mxchange , can you confirm / disconfirm that version 1.17.0 of the Canary Build fixes the issue?

@santiago-elustondo, The 1.17.0 build works. I have found, however, that the state is only showing for some components and not others...but that a separate bug and I'll post in a new issue if there is not already one created for it.
Thanks!

Canary merged with master as official 1.18 release.


add_class overrides rather than appending in DateTime fields

add_class is working fine with DateField but it is overriding the class when using it on a DateTimeField and after that, the calendar widgets do not appear. My guess is because DateTimeField is formed by two different inputs and when it executes the append_attr function it doesn't detect their class so its lost during the next function calls.

See also: https://bitbucket.org/kmike/django-widget-tweaks/issue/2/doesnt-work-for-selectdatewidget

Oh, thanks, didn't know the repo was also in bitbucket ;).

Yeah, there is a bitbucket repo, but I'm thinking of shutting it down because of issues with hg-git (https://bitbucket.org/durin42/hg-git/issue/133/repositories-can-diverge).


Document development process guidelines

Capture a list of guidelines for development, including expected process for contributions, PRs, reviews, and merge activities.

Completed by https://github.com/eclipse-pass/main/pull/227


Granular control options

Adds doPanning, doPinchZoom and doWheelZoom to control plugin behaviour.
Moves default options into an extended object to allow for boolean defaults.
Adds option breakdown and example to readme.

there is something wrong with the diff. Which branch did you fork?

No not at all. We just might need to merge #13 first and you need to rebase then :)

ah I see, fair enough!

@cfreear can you please resolve the merge conflict? We changed quite a lot :)

Done, let me know if you want any changes making

any update on this?

I totally forgot about this and coming back after like 3 years. Sorry to everyone. I will merge it myself asap


Cleanup : removed duplicated logic in ConstantPool

Motivation :
ConstantPool and AbstractConstant had duplicated logic for id generation. Made code harder to understand.
Modifications :
Id generation removed from ConstantPool.
Uniquifier variable of AbstractConstant for compareTo method removed and replaced with id variable.
Result :
Code cleaner and simpler. AbstractConstant has -1 field.

@normanmaurer a bit confused with 2 last messages :). I made a change, hope I understood it right.

@doom369 yep looks good... Let the ci finish and then I can merge.

@Scottmitch PTAL as well

@Scottmitch fixed. Sorry not used yet to back compatibility.

@doom369 seems like not all is fixed... Please ping us once you did

@normanmaurer returned public nextId as @Scottmitch mentioned. Did I miss something?

see https://github.com/netty/netty/pull/5628#discussion_r73620315 above

@doom369 ^^

@normanmaurer fixed. this is only way I see to avoid breaking current API. However to be honest I don't understand why you should care regarding protected API (yes, I know, inheritance, package, but anyway protected supposed to be protected :) ).

@normanmaurer ah, ok. Removed.

LGTM now... @Scottmitch PTAL as well.

Closing. I'll think how to improve without affecting existing code.


Expected time of release of code and models

Hey team,
Thank you so much for the exciting work that you have done. My question is that what is the expected date of the launch of code and models.
Thanks

Thank you for your attention. Our algorithm is still in the process of being refined. We hope to further improve its performance and organize it into a complete paper before releasing the code.

Thank you for your attention. Our algorithm is still in the process of being refined. We hope to further improve its performance and organize it into a complete paper before releasing the code.

I noticed that you didn't give the values for each hyperparameter, which should be adjustable for different images, but I'm curious if there are any criteria for selecting the values for the different images.


swiftinterface compilation does not re-serialise static library builds

Description
It seems that I recently started getting link errors related to swiftCxx.lib and swiftCxxStdlib.lib such as:
Windows (x64/arm64):
lld-link: error: could not open 'swiftCxx.lib': no such file or directory
lld-link: error: could not open 'swiftCxxStdlib.lib': no such file or directory

LINK : fatal error LNK1104: cannot open file 'swiftCxx.lib'

where I presume it should probably need to load instead libswiftCxx.lib and libswiftCxxStdlib.lib  which actually exist in the toolchain directory, as opposed to swiftCxx.lib and swiftCxxStdlib.lib which don't exist there.
Locally reverting https://github.com/swiftlang/swift/pull/77559 (and https://github.com/swiftlang/swift-installer-scripts/pull/344) seems to make this error go away.
Reproduction
On a recent toolchain build in the main branch:
Windows
C:\Users\hiroshi\Test>cat Test.swift
import CXXModule

C:\Users\hiroshi\Test>cat Inputs\header.h
#ifndef HEADER_H
#define HEADER_H

#endif // HEADER_H

C:\Users\hiroshi\Test>cat Inputs\module.modulemap
module CXXModule {
  header "header.h"
  requires cplusplus
}

C:\Users\hiroshi\Test>swiftc Test.swift -cxx-interoperability-mode=default -o Test.exe -I C:\Users\hiroshi\SwiftCxxTest\Inputs
error: link command failed with exit code 1104 (use -v to see invocation)
LINK : fatal error LNK1104: cannot open file 'swiftCxx.lib'
clang: error: linker command failed with exit code 1104 (use -v to see invocation)

Expected behavior
Successful linking, no link errors.
Environment
With a recent main-branch toolchain build on windows.
Additional information
No response

Hmm, looks like this code might need to change: https://github.com/swiftlang/swift/blob/8a78496368d579c97df381469402ee3352065091/lib/AST/ModuleDependencies.cpp#L502-L508
However, the Windows CI seems to be passing now, so I wonder if there is a difference between the CI and the local build config.

I didn't encounter this during a toolchain build, but in an internal app build. So, the Windows CI build may not trigger this particular issue. I hope that anyone other than me can reproduce with the reduced test example.

The code doesn't need to change, it is correct. The problem is that we are building the libraries as static libraries rather than dynamic libraries, which is why they are failing to link.

The issue here is that we are generating a static resilient module and distributing the swiftinterface now. When the swiftinterface was being re-serialised, we would drop the static indicator resulting in the module trying to be dynamically linked when it was static.


Add Getting Started section to Readme

Readme Update
Please add a getting started section to the Readme so folks know how to start with this project

Added Getting Started section in readme file.


Comments say "// TODO: set large fields to null." - why?

If there's a good reason for it, please document it, otherwise please remove the comments from this document and from any auto-generated code. It's clearly confusing people as you can see if you search online for an answer to it.

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

ID: 572ef6c6-5066-4a14-76a0-c3fb4b62e604
Version Independent ID: 9c754da1-c234-fb12-580b-0fcf9ffe2c20
Content: Implement a Dispose method
Content Source: docs/standard/garbage-collection/implementing-dispose.md
Product: dotnet
Technology: dotnet-standard
GitHub Login: @gewarren
Microsoft Alias: gewarren

It's already documented:

Managed objects that consume large amounts of memory or consume scarce resources. Assign large managed object references to null to make them more likely to be unreachable. This releases them faster than if they were reclaimed non-deterministically.

But there is a conflict that this sentence is below

This block executes if the value of disposing is true. The managed resources that it frees can include

while the

// TODO: set large fields to null.

is not inside if (disposing).

OK, fair enough, I'd missed that. The conflict you mentioned aside though, I'd say that "to make them more likely to be unreachable" is somewhat vague, and it's not mentioned in the generated code comments where people will likely encounter it and wonder why.
I assume you'll investigate the highlighted conflict?


ROSA provider: support getting versions

What
This PR adds a new method named Versions that can be called to return back a list of available versions to deploy clusters with based on the provided options (channel group and hosted control plane support).
Jira

SDCICD-1043

/lgtm


[PluggableDevice] Enable tensor list kernels on Windows

Could someone also review this small change? This is all that's needed to enable tensor list kernels on Windows.

@rohan100jain @gbaned Is it something that could get merged soon-ish? We're targeting this change for 2.9 to enable pluggable devices on Windows.


Proposal: @sig for ::

Hey @soutaro,
First, thanks for your work. I’ve been following this repo from the very first day and very excited of where it goes.
I have a suggestion regarding the primitive syntax—use # @sig instead of #:::

The current syntax is shorter (guess, that’s the reason) but looks like something new and even foreign compared to @x annotations already used by existing tools (notably, YARD)

It would make the syntax consistent (all annotations start with “@“)

It’s more descriptive (readable/understandable), especially to those not yet familiar with RBS syntax.

The @sig notation is also inspired by one of the prominent Ruby projects—Zeitwerk (example). It’s used there for information purpose only but looks very coherent with the rest of the documentation.
We can probably reuse @rbs instead of introducing a new annotation, too:

# @rbs () -> String
def to_s
end

# @rbs (?Regexp?) -> Enumerator[String, void]
# @rbs (?Regexp?) { (String) -> void } -> void
def each_person(pattern = nil, &block)
end

Since a signature must start with a ( (right?), I think, we can distinguish it from other annotations.
P.S. Now, looking at the example, I think that @sig would look better: it’s clear to even non-Ruby engineers that it’s a method signature (reminds of Erlang’s -spec), while @rbs is too Ruby-specific.

Thank you for your feedback!
The #:: syntax is introduced for people who loves more compact syntax, even though a little bit cryptic. I'm open to add something equivalent to it for method types. @rbs method: () -> String was in my mind, but @rbs () -> String looks good too.
Do you think having @sig replacing all of @rbs?
# @sig generic A < BasicObject
class Foo < Bar
  # @sig @name: String

  # @sig name: String
  # @sig yields (Foo) -> void
  def initialize(name) #:: void
  end

  # @sig (String) -> EmailResult?
  def send_email(content)
  end
end

Hmm, not too bad.

Do you think having @sig replacing all of @rbs?

Yeah. The example you provided above looks more readable to me (especially the #send_mail method). Though I understand that’s it’s subjective (so, with discussing with broader audience; maybe, at/after Kaigi?).

@soutaro @palkan Honestly that syntax with @sig looks quite nice to me. Feels immediately understandable.

[Moved from Discord]

I was against the #: (single colon) syntax, but now it looks good enough to me. Maybe it will be changed to #: from #::.

So what was your reason against #: originally?
Could it be a conflict with Steep? I rather look forward to Steep depending on rbs-inline so it doesn’t have to maintain its own set.

I’m split with changing to @sig, but a background on the sig/ folder for RBS would help me decide. Using the sig name (for either this annotation and that folder) is taking RBS beïng Ruby’s “official” (gradual) static type system for granted. The rbs name (for either) is much more explicit (esp. vs. Sorbet).

No conclusion yet for @sig, while I'm okay for either of the two.
#: syntax conflicts with Steep annotation. attr_reader :name #: String in Steep is a type assertion on the result of the method call. So, my plan for this is:

attr_reader-ish are special for Steep that the #: is not type assertion
May add another type assertion syntax to Steep for the case we need it, # @as or something else. Like TS has <T> and as T.

attr_reader-ish are special for Steep that the #: is not type assertion

Resolved by soutaro/steep#1176

I decided to go with @rbs, not @sig.
@rbs is safer and clear enough for people working around this area. @sig would make sense too, but not now. We can add the syntax in future.


Serverless?

@IEvangelist,
Thank you for putting together this great demo. After reviewing the code briefly, it seems the server project's only two roles are to:

provide a REST endpoint for Twilio rooms & room details
provide a SignalR hub for broadcasting room changes

If I wanted to modify to a more "serverless" approach, presumably 1) and 2) could easily be handled by Azure functions and Azure SignalR service, respectively. Or, if publishing updates wasn't a requirement, remove 2) altogether.
Does that sound right? Any issues you can foresee with this approach?
David

Hi @dcuccia - I have thought about making this serverless already. It is absolutely doable, and both of your suggestions are a step in the right direction. I'd love to see how you go about implementing this, if you fork my repo and add it perhaps we could merge that back here when you're done?


Using external tifffile code

We use Tifffile for read_stack with the code for this class in workflow/lib/shared/external/tifffile.py.
This code from Christoph Gohlke does exist as an actively maintained python package so we should probably use this package instead.
@mat10d has informed me that we don't know exactly why a separate file was implemented, so we should make sure that using this package has no unintended consequences.

Fixed in #20!


[syn top_earlgrey] issue: *** [./hw/syn/tools/dvsim/syn.mk:28: do_build] Terminated

syn top_earlgrey_gtech_syn_cfg.hjson command:
./util/dvsim/dvsim.py -t dc hw/top_earlgrey/syn/top_earlgrey_gtech_syn_cfg.hjson --purge –local
issue:
make: *** [/home/riscv/project/opentitan/hw/syn/tools/dvsim/syn.mk:28: do_build] Terminated
build.log:
build.log.txt

I've just looked at the attached log. Thanks for including it. I think the failure is probably in the compile command, and any failure message will appear in compile.rpt. Can you add a comment with the last lines of that report? (They will presumably show what is failing)

Thanks for your help. Please check the attached compile.rpt file with the last lines.
compile(last lines).rpt.txt

"syn.mk:28:do_build terminated" fixed by configuring termination_stage to "reports" from "compile" in common_gtech_syn_cfg.hjson.
link: hw/syn/tools/dvsim/common_gtech_syn_cfg.hjson.
Issue closed. Thanks for your help, have a good day.


GitHubReleaseV1: No files found matching 'path'. Nothing to upload.

Required Information
Type: Question
Task Name: GitHubReleaseV1
Environment

Server - Azure Pipelines

Account name: BrunoBlanes
Team project name: CRM

Agent - Private:

Build number: #20200313.31

Name
Value

Agent.OS
Windows_NT

Agent.OSArchitecture
X64

Agent.OSVersion
10.0.19555

Agent.Version
2.165.1

Issue Description
Why is it that, even though I checked the path and there is a .msixuppload file and another folder full of contents, this task still returns with No files found matching 'C:\agent\_work\4\a\AppxPackages\/*'. Nothing to upload.? Am I doing something wrong here?
Pipeline
- task: GitHubRelease@1
  displayName: 'Create GitHub Release'
  inputs:
    gitHubConnection: '$(gitConnection)'
    repositoryName: '$(Build.Repository.Name)'
    action: 'create'
    target: '$(Build.SourceVersion)'
    tagSource: gitTag
    changeLogCompareToRelease: 'lastFullRelease'
    changeLogType: 'issueBased'
    assets: $(Build.ArtifactStagingDirectory)\AppxPackages\/*

Task Result
Starting: Create GitHub Release
==============================================================================
Task         : GitHub Release
Description  : Create, edit, or delete a GitHub release
Version      : 1.160.2
Author       : Microsoft Corporation
Help         : https://aka.ms/AA5vv5o
==============================================================================
0db16545-6557-4177-9873-73325ad47670 exists true
Searching for tags associated with target commit: d0b0b5dfc57304499d5cf7c82878dffa0849aa0e
Found a tag for target commit: d0b0b5dfc57304499d5cf7c82878dffa0849aa0e
Computing changes made in this release...
Fetching the latest published release...
Found the latest published release: https://github.com/BrunoBlanes/CRM/releases/tag/v0.1.5-alpha
Fetching the list of commits since the last published release...
Found the list of changes.
No issues are linked to commits in the specified commit Diff.
Release notes file: C:\agent\_work\4\s is a directory and not a file.
Creating a release for tag: v0.1.7-alpha
Uploading assets...
Searching for file(s) matching 'C:\agent\_work\4\a\AppxPackages\/*'.
No files found matching 'C:\agent\_work\4\a\AppxPackages\/*'. Nothing to upload.
All assets uploaded successfully.
Release created successfully at https://github.com/BrunoBlanes/CRM/releases/tag/v0.1.7-alpha
Finishing: Create GitHub Release

Never mind, it works now. I guess my build process wasn't generating any packages.


⚠ ETF has degraded performance

In 946abdd, ETF (https://markets.hankyung.com/equity-product/etf) experienced degraded performance:

HTTP code: 200
Response time: 8521 ms

Resolved: 상승종목 performance has improved in 4c78976.


how to use onTrClick

I'd like to use onTrClick to achieve two things:

Set an 'active' class to the row
Retrieve that row's info and send it to another component.

Sorry for the noob question. I'm just started picking up React.

There is no onTrClick anymore.
Please use getTrProps like so:
getTrProps={(state, rowInfo, column, instance) => {
  return {
    onClick: e => {
      // Do something when a tr element is clicked!
    }
  }
}}

As you can see, it's very easy to add other props as well :)


CORTX-32367:Remove hardcoded data node type value from const.py

Problem:

In rgw mini-provisioner phase, we are fetching data pod endpoint (hostname) value using one hardcoded string "node>machine-id>type" as "data_node"
This hardcoded needs to be removed and data pod identification can be done with another keys.

Solution

Use Conf.search() api to identify data pods available in cluster.conf file.
From above list, get the hostnames of data pods.

Signed-off-by: Sachitanand Shelake<EMAIL_ADDRESS>Problem Statement

Problem statement

Design

For Bug, Describe the fix here.
For Feature, Post the link for design

Coding
Checklist for Author

[ ] Coding conventions are followed and code is consistent

Testing
Checklist for Author

[ ] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[ ] Testing was performed with RPM

Impact Analysis
Checklist for Author/Reviewer/GateKeeper

[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)

Review Checklist
Checklist for Author

[ ] JIRA number/GitHub Issue added to PR
[ ] PR is self reviewed
[ ] Jira and state/status is updated and JIRA is updated with PR link
[ ] Check if the description is clear and explained

Documentation
Checklist for Author

[ ] Changes done to WIKI / Confluence page / Quick Start Guide

Tested the latest changes with below images,
Image job :
https://eos-jenkins.colo.seagate.com/job/GitHub-custom-ci-builds/job/generic/job/custom-ci/6898/ (Success)
cortx-docker.colo.seagate.com/seagate/cortx-data:2.0.0-6898-custom-ci
cortx-docker.colo.seagate.com/seagate/cortx-server:2.0.0-6898-custom-ci
cortx-docker.colo.seagate.com/seagate/cortx-control:2.0.0-6898-custom-ci
Deployment job :
https://eos-jenkins.colo.seagate.com/job/Cortx-Automation/job/RGW/job/setup-cortx-rgw-cluster/7715/ (Success)

I have tested this changes with modified value of data type (data_node -> data_node_prime1) on my local k8 setup. changes are working and deployment is successful.
changes made in k8 script for testing : modified_data_type_changes.PNG
rgw setup log after deployment : rgw_setup_with_modified_data_type.PNG


Removed .vscode

I noticed the .vscode was in the .gitignore, yet still in the repository.  I just removed it as an initial hello to the class.

@jak103 I think it somehow got committed to the repo before it was in the gitignore -- so this PR is removing it so what you're saying doesn't happen I believe. Also @Septimis you'll need to rebase to get the fixed test.

@jak103 Your own personal .vscode will stay on your machine and will still customize your vscode experience, however, with the .vscode remaining on the repository, everyone who pulls this down will have their vs code experience pre-set to whoever initially put it up there.  If your goal is to have everyone have their own customized vs code experience, we would want it off the repo
@Skylude Not to come off as a n00b here, but how would I rebase to fix the test?

My bad on this, I read the initial comment as you were removing the .vscode from the .gitignore. Silly me, I just looked that the files changed. Approved.


Added a list of languages supported by MyMemory

Added a list of languages supported by MyMemory in constants.py
Added a new dictionary with the language and its corresponding code, where previously MyMemoryTranslator was defaulting to the languages available on the Google translator
Modified test_mymemory.py according to recent changes in language code.

closes #213


runtime error bad_action_from_state_function

Hello, I have this error, which occurs when the cron job is executed. It seems to happen when I prepare a production release with destilery.
11:08:15.022 [error] GenStateMachine #PID<0.2405.0> terminating
** (ErlangError) Erlang error: {:bad_action_from_state_function, {:reply, :undefined, {:error, :timeout}}}
    (stdlib) gen_statem.erl:1290: :gen_statem.parse_actions_reply/7
    (stdlib) gen_statem.erl:1206: :gen_statem.loop_event_actions_list/10
    (ssl) tls_connection.erl:133: :tls_connection.init/1
    (stdlib) proc_lib.erl:249: :proc_lib.init_p_do_apply/3

I have the same issue running locally, did you ever find a fix?

Unfortunately, no. Currently, the system logs are filled with those errors. Everything seems to be working fine tho. Only that actual errors are hard to find between this one

Replaced by #411


Hostname cycle bugfix

This should fix issue #76

Awesome! Which setting are you changing? I compared your avahi-daemon.conf with my local avahi-daemon.conf but couldn't pick the difference my eye haha.
Also do you think a diff patch would be better suited to apply the changes?

Im making avahi bind to the main interfaces as I have a feeling it tries to bind to others that docker creates

I think placing a file there should tell it not to create something. its basically the default with some changes.
I've done this with tor before

This is now working..

Turns out it is a known bug with Avahi [See: Hostname changes with appending incrementing numbers]. We just need to patch avahi-daemon.conf to disable IPV6 and that's it.

My patch also fixes it too

But how? I see IPv6 as enabled:
https://github.com/getumbrel/umbrel-os/blob/1b26d770bddaf02a43d7677e4d5690f9c9ff24de/stage2/00-sys-tweaks/files/avahi-daemon.conf#L26

Well it's working right now.

working with IPV6 too (I have an ipv6 network)

The only problem with that change is if if that line now longer exists anymore it would fail

Yes, that's still better than installing a avahi-daemon.conf which could be incompatible with a future release of Avahi, as we'd at least know at the build time that the sed failed.

We won't actually

https://stackoverflow.com/questions/15965073/return-code-of-sed-for-no-match


Removal Request: /labs/TheLAb

https://sphere.diybio.org/labs/thelab/
https://github.com/DIYbiosphere/sphere/tree/master/_labs/TheLAb
This business is no longer a DIY lab.
Per Melissa Draeger, VP Operations, TheLab Inc.:

We stopped teaching classes and hosting public events in 2018. We have transitioned to being a start up incubator. Please visit our website for details about the current services and lab rentals that we offer.

When asked about alternative resources, she replied:

Unfortunately I do not know of any resources in the LA area for adults outside of university programs.

It's unfortunate but I think it's important to remove the listing because it highlights that Los Angeles zero DIY community biology labs and little other resources / classes available to the general public.

Hi this is a good point and we discussed the need for a system to verify the activity of entries on the site in #286. Until we decide a specific solution I don't want to manually edit the entry myself. Thanks for your input!


Next/less creating common chunk and page specific chunks

#/static/pageA.less
@import './common.less';
@import './pageA/stylename.less';

#/static/pageB.less
@import './common.less';
@import './pageB/stylename.less';

#/pages/A.js
import 'static/pageA.less';
...

#/pages/B.js
import 'static/pageB.less';
...

#/next.config.js
const withCSS = require('@zeit/next-css')
const withLess = require('@zeit/next-less')
module.exports = withCSS(withLess({
  lessLoaderOptions: {
    javascriptEnabled: true
  }
}))

Next Version: next.canary
Next Plugins: next.canary
How do I force the two page entry files to be separate chunks with a common chunk? I got the impression this was possible in next without too much hacking of the webpack config...

We have an issue template, please follow it 🙏
Besides that you have to override the styles commonschunk, but that's going to be guaranteed to break in the near future.


Download Stops

Im trying to downlaod this

Please provide more details!

I have the same problem, the download stops at a certain point but doesn't show any message. For resuming the download I have to create a second terminal and re-run de command, but now I've done that several times and doesn't resume the download.  Any idea on how to fix this or make all the downloads go in one go?


Reinitialize modal.js object

Imagine, that I have a form in a modal popup. I submit this form in ajax-way, get some json, and try to fill this modal with new content from server.
I did not find a way to update the existing modal with new data, so I tried
modal.modal('toggle') # hide the previous modal
modal = $(json.html).modal(true) # fill with new data
modal.modal('toggle') # show the modal

This way I get the data, that should be in the modal popup just appended to the end of the body tag. It's the wrong behavior, I guess. Is this a bug, or is there a correct and twitterish way to do this?

All you need to do is insert the content as you normally would. You shouldn't need to toggle the modal. If you ask in the mailing list, me or one of the other awesome community people can give you a hand :)


use guice as apollo-client ioc mechanism

Coverage increased (+0.3%) to 50.097% when pulling f048baffef6312723db7e2a162fcf535a841c7a1 on nobodyiam:use-guice-as-client-ioc into c219ee890369f0e859a3a3ee86cc175be3969172 on ctripcorp:master.

Codecov Report

Merging #599 into master will increase coverage by 0.24%.
The diff coverage is 70.73%.

@@             Coverage Diff              @@
##             master     #599      +/-   ##
============================================
+ Coverage      46.3%   46.54%   +0.24%
- Complexity     1446     1450       +4
============================================
  Files           338      338
  Lines          9243     9238       -5
  Branches        911      911
============================================
+ Hits           4280     4300      +20
+ Misses         4639     4611      -28
- Partials        324      327       +3

Impacted Files
Coverage Δ
Complexity Δ

...ork/apollo/internals/AbstractConfigRepository.java
75% <ø> (ø)
6 <0> (ø)
:arrow_down:

...ork/apollo/spring/config/ConfigPropertySource.java
50% <ø> (ø)
3 <0> (ø)
:arrow_down:

...trip/framework/apollo/util/function/Functions.java
100% <ø> (ø)
1 <0> (ø)
:arrow_down:

...apollo/spring/config/PropertySourcesProcessor.java
100% <ø> (ø)
11 <0> (ø)
:arrow_down:

...va/com/ctrip/framework/apollo/util/ConfigUtil.java
45.94% <ø> (ø)
22 <0> (ø)
:arrow_down:

...ework/apollo/spring/util/BeanRegistrationUtil.java
72.72% <ø> (ø)
3 <0> (ø)
:arrow_down:

...pollo/spring/annotation/ApolloConfigRegistrar.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

.../spring/config/ConfigPropertySourcesProcessor.java
100% <ø> (ø)
2 <0> (ø)
:arrow_down:

...trip/framework/apollo/internals/DefaultConfig.java
74.39% <ø> (ø)
22 <0> (ø)
:arrow_down:

...framework/apollo/internals/AbstractConfigFile.java
91.3% <ø> (ø)
5 <0> (ø)
:arrow_down:

... and 22 more

Continue to review full report at Codecov.

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


DBZ-2541 Make log4j root loggers configurable in connect-base image

https://issues.redhat.com/browse/DBZ-2541

Hi, thanks for the PR. Fo start it looks good! Please just update the commit message to refer to JIRA id.
IMHO it is fine to use CONNECT_ prefix. But as these env vars are passed to the Kafka Connect I belive it makes sense to unset all CONNECT_LOG4J_ env vars after they are used.

Hi, thanks for the PR. Fo start it looks good! Please just update the commit message to refer to JIRA id.
IMHO it is fine to use CONNECT_ prefix. But as these env vars are passed to the Kafka Connect I belive it makes sense to unset all CONNECT_LOG4J_ env vars after they are used.

@jpechane I'm not sure I understand regarding unsetting those env vars.  This script does not appear to unset the other CONNECT_ vars after use (https://github.com/debezium/docker-images/blob/a71620eb9cefcdfa5c6f3101464c9e6bd394897f/connect-base/1.3/docker-entrypoint.sh#L195-L216)?

@jfinzel The start script takes all CONNECT_ named properties and converts them into Kafka Connect configuration options (adding to the config file). If CONNECT_LOGJ_ env vars will stary set then the Kafka COnnect configuration will be full of config options named log4j.* which I consider to be confusing

@jfinzel The start script takes all CONNECT_ named properties and converts them into Kafka Connect configuration options (adding to the config file). If CONNECT_LOGJ_ env vars will stary set then the Kafka COnnect configuration will be full of config options named log4j.* which I consider to be confusing

@jpechane I follow.  I have pushed the fix for this.  Let me know if there is anything else.

@jfinzel I've added few changes to make it work. Could you please add this change to the docs? - see https://debezium.io/documentation/reference/1.3/operations/logging.html#configuring-log-level-docker

@jfinzel I've added few changes to make it work. Could you please add this change to the docs? - see https://debezium.io/documentation/reference/1.3/operations/logging.html#configuring-log-level-docker

https://github.com/debezium/debezium/pull/1850


promptfoo doesn't detect false or 0 outputs, I get '[FAIL] No output'

Describe the bug
I use an http provider, my endpoint returns a json like:
{
    "blocked": true
}

When the value is true it works as expected, but when it is false, promptfoo doesn't detect the value, and I get [FAIL] No output message. The behaviour is similar if I use 0 and 1 values (promptfoo doesn't detect 0).
To Reproduce

Save this python code to test_api.py:

from fastapi import FastAPI
from pydantic import BaseModel

app = FastAPI()

class RequestModel(BaseModel):
    message: str

class ResponseModel(BaseModel):
    blocked: bool

@app.post("/status", response_model=ResponseModel)
def post_status(request: RequestModel):
    if request.message == 'this is true':
        return_value = True
    else:
        return_value = False

    return ResponseModel(blocked=return_value)

Run the API with uvicorn:

uvicorn test_api:app

Save this configuration to a promptfooconfig.yml file:

description: "bug test"

prompts:
  - "{{question}}"

providers:
  - id: 'http://<IP_ADDRESS>:8000/status'
    config:
      method: 'POST'
      headers:
        'Content-Type': 'application/json'
      body:
        message: '{{prompt}}'
      responseParser: 'json.blocked'
      responseType:

defaultTest:
  assert:
    - type: equals
      value: "{{is_blocked}}"
tests:
  - vars:
      question: "this is true"
      is_blocked: true
  - vars:
      question: "this is not true"
      is_blocked: false

Run promptfoo with:

promptfoo eval

Expected behavior
Both test pass, as the API return true for the first call and false for the second call.
System information (please complete the following information):

Promptfoo version: 0.74.0

Thanks for the report! #1356 should fix

This should be good in the latest release


No blur on hyprland

Hi,
I have problems getting the blur on hyprland to work. Short summary of my setup:
Arch
hyprland-git: commit be03a6186c22f915d3d92df71d2e74c64e816245dirty (2022-11-20)
 hybrid-bar-git: 0.3.8-1

decoration part of hyprland.config
decoration {
    rounding=10
    blur=1
    blur_size=5
    blur_passes=2
    blur_new_optimizations=1
    blur_ignore_opacity=1
}

HybridBars config.json (important part)
    "hybrid": {
        "r": 10,
        "g": 10,
        "b": 10,
        "a": 0.8
    },

style.css
* {
   font-family: Roboto, "Fork Awesome";
}

label {
   color:         white;
   padding-left: 5px;
   padding-right: 5px;
}

#root {
}

#left {
   border-right: 1px solid;
   border-left: 1px solid;
}

#right {
   border-left: 1px solid;
   border-right: 1px solid;
}

#separator, #separator_ending, #separator_vol {
   background-color: white;
}

/* Button Configuration */
button {
   border-radius: 50%;
   font-weight:    normal;
   border: 1px solid;
   box-shadow: none;
   margin-bottom: 2px;
   margin-top: 2px;
   margin-right: 3px;
   margin-left: 3px;
   padding-left: 0px;
   padding-right: 0px;
   padding-top: 0px;
   padding-bottom: 0px;
   min-width: 25px;
   min-height: 25px;
   background-image: none;
   background-color: rgba(50,97,112,0.75);
}

While I get a nice blur on alacritty with nearly identical settings (opacity=0.8), there is no blur with HybridBar. Did I miss something? I tried different values, restarted everything, but no success. Here are two examples, the second dark bar uses the posted config, the other bars are using a different colour and opacity:

I hope this is the right place to ask this.

Hybrid isn't a window unlike alacritty, it's a layer-surface so you'll have to explicitly enable blur for it: https://wiki.hyprland.org/Configuring/Keywords/#blurring-layersurfaces


Support multiple UDP source ports (multiport)

The goal of this work is to send packets between two hosts using more than one 5-tuple. When running on networks like AWS where the underlying network driver and overlay fabric makes routing, load balancing, and failover decisions based on the flow hash, this enables more than one flow between pairs of hosts.
Multiport spreads outgoing UDP packets across multiple UDP send ports, which allows nebula to work around any issues on the underlay network. Some example issues this could work around:

UDP rate limits on a per flow basis.
Partial underlay network failure in which some flows work and some don't

Agreement is done during the handshake to decide if multiport mode will be used for a given tunnel (one side must have tx_enabled set, the other side must have rx_enabled set)
NOTE: you cannot use multiport on a host if you are relying on UDP hole punching to get through a NAT or firewall.
NOTE: Linux only (uses raw sockets to send). Also currently only works with IPv4 underlay network remotes.
This is implemented by opening a raw socket and sending packets with a source port that is based on a hash of the overlay source/destiation port. For ICMP and Nebula metadata packets, we use a random source port.
Example configuration:
multiport:
  # This host support sending via multiple UDP ports.
  tx_enabled: false

  # This host supports receiving packets sent from multiple UDP ports.
  rx_enabled: false

  # How many UDP ports to use when sending. The lowest source port will be
  # listen.port and go up to (but not including) listen.port + tx_ports.
  tx_ports: 100

  # NOTE: All of your hosts must be running a version of Nebula that supports
  # multiport if you want to enable this feature. Older versions of Nebula
  # will be confused by these multiport handshakes.
  #
  # If handshakes are not getting a response, attempt to transmit handshakes
  # using random UDP source ports (to get around partial underlay network
  # failures).
  tx_handshake: false

  # How many unresponded handshakes we should send before we attempt to
  # send multiport handshakes.
  tx_handshake_delay: 2

Branch now has conflicts, needs updating

Status on this?


An API for release manifests (htsget)

Added activation schema
Wrote manifest producer and test cases

Introduced the concept of a complex JSON manifest
{
      "id": "XYZ",
      "reads": {
        "976611A295F611EDADFF6FE041F91274": {
          "url": "s3://umccr-10g-data-dev/HG03433/HG03433.bam"
        },
        "976625D495F611EDADFF1B4DAF18B332": {
          "url": "s3://umccr-10g-data-dev/HG00173/HG00173.bam"
        },
        "9766298A95F611EDADFF8375566385AD": {
          "url": "s3://umccr-10g-data-dev/HG00171/HG00171.bam"
        },
        "976637CC95F611EDADFF3BBCB6763F0C": {
          "url": "s3://umccr-10g-data-dev/HG00096/HG00096.bam"
        },
        "9778170895F611EDADFF57E065BECAB0": {
          "url": "s3://umccr-10f-data-dev/CHINESE/GGHG002-HG003-HG004.joint.filter.vcf.gz"
        },
        "9778248295F611EDADFFF729ECA472C8": {
          "url": "s3://umccr-10f-data-dev/ASHKENAZIM/HG003.bam"
        },
        "977826F895F611EDADFF9B8B57D53158": {
          "url": "s3://umccr-10f-data-dev/ASHKENAZIM/HG002.bam"
        }
      },
      "variants": {
        "976611A295F611EDADFF6FE041F91274": {
          "url": "s3://umccr-10g-data-dev/HG03433/HG03433.hard-filtered.vcf.gz",
          "variantSampleId": "HG03433"
        },
        "976625D495F611EDADFF1B4DAF18B332": {
          "url": "s3://umccr-10g-data-dev/HG00173/HG00173.hard-filtered.vcf.gz",
          "variantSampleId": "HG00173"
        },
        "9766298A95F611EDADFF8375566385AD": {
          "url": "s3://umccr-10g-data-dev/HG00171/HG00171.hard-filtered.vcf.gz",
          "variantSampleId": "HG00171"
        },
        "976637CC95F611EDADFF3BBCB6763F0C": {
          "url": "s3://umccr-10g-data-dev/HG00096/HG00096.hard-filtered.vcf.gz",
          "variantSampleId": "HG00096"
        },
        "9778170895F611EDADFF57E065BECAB0": {
          "url": "s3://umccr-10f-data-dev/CHINESE/EEHG002-HG003-HG004.joint.filter.vcf.gz",
          "variantSampleId": "HG002"
        },
        "9778248295F611EDADFFF729ECA472C8": {
          "url": "homers3://umccr-10f-data-dev/ASHKENAZIM/HG002-HG003-HG004.joint.filter.vcf.gz",
          "variantSampleId": "HG003"
        },
        "977826F895F611EDADFF9B8B57D53158": {
          "url": "s3://umccr-10f-data-dev/ASHKENAZIM/HG002-HG003-HG004.joint.filter.vcf.gz",
          "variantSampleId": "HG004"
        }
      },
      "restrictions": {},
      "cases": [
        {
          "ids": {
            "": "SIMPSONS",
            "coriellfamily": "3140",
            "giabfamily": "ASHKENAZIM"
          },
          "patients": [
            {
              "ids": {
                "": "BART",
                "1KGP": "HG002",
                "https://my.pgp-hms.org/": "huAA53E0"
              },
              "specimens": [
                {
                  "htsgetId": "977826F895F611EDADFF9B8B57D53158",
                  "ids": {
                    "corielldna": "NA24385",
                    "coriellcell": "GM24385"
                  }
                }
              ]
            },
            {
              "ids": {
                "": "HOMER",
                "1KGP": "HG003",
                "https://my.pgp-hms.org/": "hu6E4515"
              },
              "specimens": [
                {
                  "htsgetId": "9778248295F611EDADFFF729ECA472C8",
                  "ids": {
                    "corielldna": "NA24149",
                    "coriellcell": "GM24149"
                  }
                }
              ]
            }
          ]
        },
        {
          "ids": {
            "": "JETSONS",
            "coriellfamily": "3150",
            "giabfamily": "HAN"
          },
          "patients": [
            {
              "ids": {
                "https://my.pgp-hms.org/": "hu38168C"
              },
              "specimens": [
                {
                  "htsgetId": "9778170895F611EDADFF57E065BECAB0",
                  "ids": {
                    "corielldna": "NA24695",
                    "coriellcell": "GM24694"
                  }
                }
              ]
            }
          ]
        },
        {
          "ids": {
            "": "SINGLETONCHARLES"
          },
          "patients": [
            {
              "ids": {
                "": "CHARLES"
              },
              "specimens": [
                {
                  "htsgetId": "976637CC95F611EDADFF3BBCB6763F0C",
                  "ids": {
                    "": "HG00096"
                  }
                }
              ]
            }
          ]
        },
        {
          "ids": {
            "": "SINGLETONKAARINA"
          },
          "patients": [
            {
              "ids": {
                "": "KAARINA"
              },
              "specimens": [
                {
                  "htsgetId": "9766298A95F611EDADFF8375566385AD",
                  "ids": {
                    "": "HG00171"
                  }
                }
              ]
            }
          ]
        },
        {
          "ids": {
            "": "SINGLETONANNELI"
          },
          "patients": [
            {
              "ids": {
                "": "ANNELI"
              },
              "specimens": [
                {
                  "htsgetId": "976625D495F611EDADFF1B4DAF18B332",
                  "ids": {
                    "": "HG00173"
                  }
                }
              ]
            }
          ]
        },
        {
          "ids": {
            "": "SINGLETONPAKUTEH"
          },
          "patients": [
            {
              "ids": {
                "": "PAKUTEH"
              },
              "specimens": [
                {
                  "htsgetId": "976611A295F611EDADFF6FE041F91274",
                  "ids": {
                    "": "HG03433"
                  }
                }
              ]
            }
          ]
        }
      ]
    }

Also started to introduce a concept that we need - but have been putting off - which is the concept that the release needs to become 'locked'/'activated'/'enabled' at some point.
That is, we need to differentiate between the release when initially created by the Data owner - and the release once they have done all the work they need to say the release is activated for data sharing.
So the basic activation schema is present, and it is in this which the manifest is rendered (once).
There will need to be other tickets where we take into account the meaning of a release being activated (i.e. disable editing, change the UI)

Apologies - this one got away from me a bit in the construction - had to rejig the routing mechanisms whilst I was doing this to split session/cookie auth from other auth (TBD).
Whilst there is a fair bit of code - and it still needs work to integrate though the UI - most of it is orthogonal to the rest of the working code base


Update sessions.py-fixed none problem with saved_session expiry

Had an error in sessions.py where if the session expiry date was None, then the application threw an exception. Fixed the error.

Hi @armurox thanks for the PR, this issue should now be fixed with slightly different logic in the 0.6.0rc1 if you would like to test.


ng2-cropper is not working for select the same image

when i select the same image form file upload than it's not working.
and if i put the click event ested of change than its give me a erroe for file Reader
TypeError: Failed to execute 'readAsDataURL' on 'FileReader': parameter 1 is not of type 'Blob'.
    at _global.(anonymous function).(anonymous function) [as readAsDataURL] (https://npmcdn.com/zone.js@0.6.12?main=browser:952:61)
    at AppComponent.fileChangeListener (https://run.plnkr.co/preview/cj9ql6do400083b5snaoxys2l/app/app.component.ts!transpiled:69:18)
    at _View_AppComponent0._handle_click_24_0 (AppComponent.ngfactory.js:276:28)
    at eval (https://npmcdn.com/@angular/core@2.0.0-rc.5/bundles/core.umd.js:12718:28)
    at eval (https://npmcdn.com/@angular/platform-browser@2.0.0-rc.5/bundles/platform-browser.umd.js:1836:40)
    at eval (https://npmcdn.com/@angular/platform-browser@2.0.0-rc.5/bundles/platform-browser.umd.js:1913:115)
    at ZoneDelegate.invoke (https://npmcdn.com/zone.js@0.6.12?main=browser:323:29)
    at Object.onInvoke (https://npmcdn.com/@angular/core@2.0.0-rc.5/bundles/core.umd.js:9245:45)
    at ZoneDelegate.invoke (https://npmcdn.com/zone.js@0.6.12?main=browser:322:35)
    at Zone.runGuarded (https://npmcdn.com/zone.js@0.6.12?main=browser:230:48)

can you please suggest me?

i got the solutions for this. it's working well for me.
<button class="btn"  (click)="clear()">Cancle</button>

clear( ) {
       let defaultValue: any = '';
       const controlPic = <FormArray>this.myForm.controls['profile_picture'];
       controlPic.setValue( defaultValue );
   }

thanks.


Upgrade solidity version to 0.6.6

I am still working on this, creating PR to see how pipelines work here.

Comparison of gas prices for tests/DelFiPriceTest.js
Solidity 0.5.12 vs 0.6.6

should sort even number of sources correctly
Gas used =  242000 vs Gas used =  239942

should sort even number of sources correctly with two assets
Gas used =  540768 vs Gas used =  536398

posting single source should not record a median
Gas used =  147420 vs Gas used =  145446

posting 0 anchor price should guard price and not revert
Gas used =  224811 vs Gas used =  222627

posting some sources should yield correct median
Gas used =  248853 vs Gas used =  246500
Gas used =  174491 vs Gas used =  172126

should not update median if anchor is much higher
Gas used =  304424 vs Gas used =  301958

should not update median if anchor is much lower
Gas used =  303598 vs Gas used =  301168

posting all sources for two assets should sort correctly and yield correct median
Gas used =  633920 vs Gas used =  628762

view should use most recent post with two sources
Gas used =  633920 vs  Gas used =  628762
Gas used =  424233 vs Gas used =  419063


Upgrade to Compose 1.5 and Kotlin 1.9

Description
Updated Compose to 1.5.3 & Kotlin to 1.9.10.
...
Check list

[x] I have updated CHANGELOG.md if required.
[X] I have updated documentation if required.

For the record, these 2 screenshot tests fail, as you can see only the color is different.
This looks like a change coming from Compose itself: https://developer.android.com/jetpack/androidx/releases/compose-runtime#1.5.0

Removed allocations in recomposition, color animations, and AndroidComposeView.

Relevant change: https://android-review.googlesource.com/c/platform/frameworks/support/+/2577826/7/compose/animation/animation/src/commonMain/kotlin/androidx/compose/animation/ColorVectorConverter.kt


voting parallel run bad result

voting parallel's hyper is top_k?
when setting voting parallel, the result is worse than data parallel
but in fact the result should be feature parallel > voting parallel > data parallel?
speed  data parallel > voting parallel > feature parallel?

@weidong8405347 it depends.
if you #data is small, using data/voting isn't help.
if you #feature is small, using data parallel is enough, and it is a accurate algorithm, so the accuracy so almost the same as feature parallel.
if you #feature is large, you can use voting parallel to speed up. The accuracy depends how many data on each machines.

@guolinke  my question is that why voting result worse than data, i know the algorithm

for speed, voting is faster when #feature is large.
for accuracy, voting is also the same as data when #instances(rows) is large.

@guolinke  voting should better than data,cause it use the voting to choose the top k candidate,the nips
ok i read the paper, maybe in fact the result do not as well as the paper said

As I said before, it depends. we never said the voting is better, our word is the “tradeoff between speed and accuracy”. It may need to tune “top_k” for different datasets.