Support shared subscription

In azure service-bus, subscription support load-leveling / competing consumer:

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-queues-topics-subscriptions#topics-and-subscriptions

Currently, the azure-spring-boot-starter-servicebus-jms's default subscription is not shared.
Code to reproduce:

https://github.com/chenrujun/azure-spring-boot-starter-servicebus-jms-sample/tree/one-subscription-can-not-have-multiple-receivers

Our target is to support shared subscription.

Close this issue for it has been supported in https://github.com/Azure/azure-sdk-for-java/issues/23392


WIP: Run simnet quick test after every commit

Run simnet quick test after every commit
Intention of changes in this PR are to add proper rules and values for variables to build docker image after every commit on any
PR and then run simnet  "quick" test. Quick test is a smoke test that assures a network spawned with the  substrate docker image
has a minimum amount of nodes connected and that  they can produce blocks
Latest pipeline:  https://gitlab.parity.io/parity/substrate/-/pipelines/153419
There is still a FIXME: in there to skip test-linux-stable

Closing this PR because it was implemented in a recent one


AVRO-3932: [C] fix variable reference in CMakeLists.txt

AVRO-3932
@ZLIB_PKG@ can't be replaced as expected since we upgrade cmake from 2.4 to 3.1 in this commit: 664c2fc7fba19709c1f974055f9cf4c8a799e108.
You can find more details here: https://cmake.org/cmake/help/latest/policy/CMP0053.html.
So we should change @ZLIB_PKG@ to ${ZLIB_PKG} or add cmake_policy(SET CMP0053 OLD)

What is the purpose of the change
(For example: This pull request improves file read performance by buffering data, fixing AVRO-XXXX.)
Verifying this change
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Extended interop tests to verify consistent valid schema names between SDKs
Added test that validates that Java throws an AvroRuntimeException on invalid binary data
Manually verified the change by building the website and checking the new redirect

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

The change looks good to me! But I wonder why the CI build and the releases didn't fail until now ? Can we improve something to catch such regressions ?

I think maybe we can check the output of pkg-config --cflags --libs avro-c.

Thank you, @kensou97 !


Epic: Scaling decoupled CMS usage (GraphQL performance)

Hypothesis
By making SilverStripe's GraphQL faster, early adopters are more likely to repeatedly use it for high profile projects.
Goals

Make GraphQL reasonably fast without relying on specialised infrastructure (100ms to 500ms response times)
Make GraphQL a solid foundation for exposing all data via a CMS Content Mangement API, even with 100+ models on larger installations.
Make GraphQL very fast through caching on specialised infrastructuer such as Apollo Engine (10ms to 100ms response times)
Minimise impact on developers and existing deployment workflows
Increase the chances of GraphQL case studies in the wider SilverStripe ecosystem which will reassure decision makers

Notes

Internal reference: https://silverstripe.monday.com/boards/170016794/pulses/170016816

Superseded by: https://github.com/silverstripeltd/product-issues/issues/200

Private :(

Sorry, everyone. Didn't realise this was public. The reason it got moved is because the team that is doing this work operates in more of a business context than an OSS one, and a lot of the goals/outcomes we're after are more company focused and include references to internal personnel and plans.
That said, we're very mindful of how this will affect OSS as well, and I'm happy to include a redacted version of the epic here:
Hypothesis
We believe that improving the performance and overall developer experience of the graphql module will remove a key hinderance to more widespread adoption of GraphQL in the CMS and also in high-profile projects. This will allow developers to deliver more competitive, high performing solutions to clients and give content authors a user experience that is more competitive with the peers of Silverstripe CMS.
Idea and approach
The GraphQL module has a sordid history that makes it an outlier from many of its predecessors. It was originally spun up in October 2016 to serve the emergent needs of a newly decoupled paradigm in asset-admin. As features were tacked on, most of its evolution was unplanned and sporadic, until it was finally, somewhat inappropriately, tagged stable ahead of the core 4.0.0 release. This error in judgment applied a permanence to the nascent GraphQL API that made future, necessary adaptations rigid and slow.
This epic therefore begins with a thorough review of what we have built and maintained over the last four years, what's good about it, and where the limitations are. Many of the performance bottlenecks are a direct result of an overly opinionated API that is tightly coupled to the Silverstripe ORM. As previous experiments have shown, a key ingredient to a high performing graphql server is a cachable, deterministically produced schema. Achieving this will require a challenge of our assumptions in many corners of the API.
The inevitable outcome of this epic should be a set of API changes that contribute largely to a new major release of the module (4.0.0).
Validation
Most of the evidence that GraphQL performance is a problem can be gathered objectively through benchmarking. Previous research shows that this module is in no position to scale in its current form, with some outlandishly slow response times (up to 30s) well within the realm of possibility for a large project.
More anecdotally, we've heard from agencies and members of the community that adopting graphql proved costly in the log run as the surprisingly poor performance wasn't apparent until the project had been scaled up leading up to a launch date. This hasn't been a good look for Silverstripe CMS.
We also know through our community research that making the CMS faster is at the top of the wishlist for CMS users and developers alike. While most of the admin still does not rely on GraphQL, we chose it as a solution because it was best suited to mitigating the performance problems in the CMS and leading us to a more API-driven approach. As of now, that investment is dead on arrival, because expanding the GraphQL API is synonymous with slowing its performance.
Recent experiments with static generation (Gatsby) have shown that the module cannot expose all CMS data to a static generator without major performance limitations. While this hasn't been benchmarked, we know from direct conversations with Gatsby that a maximum five second load time is required to implement previews (a non-negotiable feature of static generated sites), and we're nowhere near delivering that kind of performance reliably.
Out of Scope

A new stable release of the module
Tutorials / upgrade paths
Blockers to GraphQL adoption that are not related to performance/DX (e.g. security pitfalls)


Not building with AGP8

Hello. can you update your lib to agp 8?
Launching lib\main.dart on sdk gphone64 x86 64 in debug mode...
Running Gradle task 'assembleDebug'...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':headset_connection_event'.
> Could not create an instance of type com.android.build.api.variant.impl.LibraryVariantBuilderImpl.
   > Namespace not specified. Specify a namespace in the module's build file. See https://d.android.com/r/tools/upgrade-assistant/set-namespace for information about setting the namespace.

     If you've specified the package attribute in the source AndroidManifest.xml, you can use the AGP Upgrade Assistant to migrate to the namespace value in the build file. Refer to https://d.android.com/r/tools/upgrade-assistant/agp-upgrade-assistant for general information about using the AGP Upgrade Assistant.

You should add namespace to gradle.build like this
android {
  // Conditional for compatibility with AGP <4.2.
  if (project.android.hasProperty("namespace")) {
    namespace 'com.example.app'
  }
...
}

and remove manifest.package from AndroidManifest.xml

Try changing the following in pubspec.yaml:
Before:
dependencies:
  headset_connection_event: ^3.1.0

After:
dependencies:
  headset_connection_event:
    git:
      url: https://github.com/Rupakpoddar/headset_connection_event


Leverage font-display: swap mode of Google fonts

For performance reasons it is best to use font-display: swap and Google Fonts supports this via a URL param. See: https://web.dev/font-display/?utm_source=lighthouse&utm_medium=lr#google-fonts for more info.
I think it would be wise to add this to the template as the lack of it gets a page a significant ding in web performance measurement.

Good work!
Are you able to make a PR for each repo on https://github.com/pages-themes ?
If not you are not, is it okey if I do it?

I'm not familiar enough with the other themes to make that suggestion, but if you are and think they need it please go ahead.


Schnet inference code

Description
Provide a brief description of the PR's purpose here.
Partial #227
Adds inference for the schnet models.
Status

[X] Ready to go

Codecov Report

Merging #250 (df8b033) into main (d1df594) will increase coverage by 0.52%.
The diff coverage is 42.42%.

@kaminow probably ready for another look. :)


[authorization] update doc about roleRef

This update is made according to this commit in code:
https://github.com/kubernetes/kubernetes/commit/8c788233e778f3b0ebef560762c1433c12ea1d43
It has already be released  with k8s v1.5, so it's reasonable to
update the doc now.

This change is

@devin-donnelly this actually needs to be against the 1.5 branch too, right?

lgtm, needs to squash down.

@deads2k no, 1.5 has launched, so that branch has merged and is effectively defunct. Master is fine.


Dialog action button are half hidden on mobile devices

Bug
What is the expected behavior?
The action buttons should be visible
What is the current behavior?
They are not fully visible
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-dialog-button
And scroll the lower console part up:

What is the use-case or motivation for changing an existing behavior?
User can't use the action button on small devices
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
This is not the first issue I'm opening on the dialog, my last issue wasn't even answered. I hope this will be different...

This is one of the things that should be resolved by https://github.com/angular/material2/pull/9236.

Any estimation on when this will be merged?

I can't commit to anything, because it depends on when the caretaker gets around to merging it.

Can you suggest a workaround until this issue is merged? some css magic maybe?

You should be able to work around it by setting a smaller max-height on .mat-dialog-content.

Issue still exists...

Issue still exists


Impossible to launch the React Native Debuguer

Actual Behavior
When I want to run the debuger I got "Le processus de l'adaptateur de débogage s'est terminé de manière inattendue" "Ouvrir launch.json"
Expected Behavior
I want the debuger to be launched!
Software versions
React-Native VS Code extension version: React Native Tools 0.2.0
VSCode version: Version 1.5.3 (1.5.3)
OS platform and version: macOS 10.11.6
React Native version: RN 0.33
Outputs (Include if relevant)
Output of the Debug Console (View -> Toggle Debug Console):
Output of the React-Native output channel (View -> Toggle Output -> Select React-Native in ListBox):
Output of the Developer Tools console (Help -> Toggle Developer Tools -> Select Console tab):
messageService.ts:119Le processus de l'adaptateur de débogage s'est terminé de manière inattendue : Error: Le processus de l'adaptateur de débogage s'est terminé de manière inattendue
at Object._ [as create](file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:34:29245)
at file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:119:8772
at Object.m [as _notify](file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:13448)
at Object.B.enter (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:16953)
at n.Class.define._run (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:18274)
at n.Class.define._chainedError (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:17633)
at n (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:15456)
at n.Class.define.then (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:19083)
at Object.R.enter (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:15525)
at n.Class.define._run (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:18274)
at n.Class.define._setCompleteValue (file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:30:17968)e.doShow @ messageService.ts:119
messageService.ts:119Le processus de l'adaptateur de débogage s'est terminé de manière inattenduee.doShow @ messageService.ts:119
Original report : https://github.com/Microsoft/vscode-react-native/issues/309

This seems to be similar to https://github.com/Microsoft/vscode/issues/10148 since removing another extension (although not flow in this case) solved the issue.

@isidorn Check Microsoft/vscode-react-native#309

@Crash-- if I properly translated the french messages this seems to be unrelated to #10148 since the react debug adapter simply crashes on startup. So the adapter gets properly launched but crashes for some reason
@MSLaguana what exactly makes you think this is due to a bug on the vscode side and not in the react extension?
@MSLaguana can you also reproduce this?

The reason I thought that this might be a vscode issue is that when @Crash-- removed an unrelated extension (jsx beautification) then our debugger worked again.

If our extension was never activated that would cause our debugger to crash since we do some first-run initialization in our extension's activation handler which the debugger component requires. Should the presence of one extension be able to stop another from activating?

@MSLaguana on what exact event is your extension getting reactivated?
@Crash-- could you upload some small repo to github for which you can reproduce this problem. And flow is the only extension you have installled besides react?
Presence of one extension should not stop another from activating

Our extension activates on the presence of a package.json file in the workspace root, although in our activate function we additionally check that executing react-native -v returns a sensible value before we do a lot of our activation.

Is this still an issue?


Remove storybook

Storybook has a very weird conflict with gatsby setup (reported here)

Since I'm not using storybook for all components, the time I spend fix those conflicts doesn't worth at all.

Also delete Netifily repository


Missing some SmS?

good day sir!
your python script was greatful, but I just notice with my 58k SMS, I noticed that messages are only restored dated 10-25-2015 but when I view the xml file, on SMS Backup & Restore View, I have SMS dated 2011 below
but during restoring using SMS Backup & Restore, the oldest is SMS dated 10-25-2015.
can you assist me again with this?
thanks in advance!

Can you explain better? Is the xml file correct, just that the viewer doesn't display them? After you've imported them, do you see them all in your Android messaging app?

ok the converted wp_xml file from the out of your python script from .msg wp sms is good, when I tried to restore it using SMS Backup & Restore android apps, there's a button view there, which it will view the content SMS from the XML files.
but during restoring process, after it restored with some 10 errors, the SMS messages only restored was dated 10-23-2015 only. there's a nearly 4yrs SMS is not successful restored.

Are you sure it's not because of conversations, so that the date makes you think it's the oldest one? Anyway, I suggest that you contact the app developer, since I don't know how that feature works exactly.

ah ok, is there any similar apps can be use for your xml files converted from WP SMS? :D

Not sure about that. There could be other apps but I don't which format they accept.


msal-browser does not get cached login when the page refreshes

Please follow the issue template below. Failure to do so will result in a delay in answering your question.

Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[x]<EMAIL_ADDRESS>and above
[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Important: Please fill in your exact version number above, e.g<EMAIL_ADDRESS>Framework
React
Description
I'm using msal-browser in React. When using redirect flow, the user login is cached in the browser (localStorage or sessionStorage does not matter) however when the page is refreshed the msal-browser component does not read this cached credential and redirects user to the azure login page (and automatically redirected back).
This error is seen in versions 2.4.1 and above. No error in 2.4.0. Probably something changed in the BrowserStorage mechanism when upgrading from 2.4.0
Error Message
Security

[ ] Is this issue security related?

Regression

[x] Did this behavior work before?
Version: 2.4.0 and below

MSAL Configuration
// Provide configuration values here.
// For Azure B2C issues, please include your policies.

Reproduction steps
// Provide relevant code snippets here.
// For Azure B2C issues, please include your policies.

Expected behavior
Browsers/Environment

[x] Chrome
[ ] Firefox
[ ] Edge
[ ] Safari
[ ] IE
[ ] Other (Please add browser name here)

@SihirliDev This appears similar to #2524, which is fixed by #2516.

Thank you @jasonnutter I'll check it.

This is fixed in v2.6.0. Thank you.


_posts/0000-01-02-dominguezdaniel.md

Merge pull request #2 from dominguezdaniel/dependabot/bundler/nokogir…

Closing


Creating a crud

I am newbie to Laravel. I have two mysql tables named galleries and gallery_images. No problem with the  galleries crud.But i want to show the gallery_images related to galleries, when a gallery name clicked in crud.
Do I have to create seperate files out of laravelpanel or is there an easy way to solve this problem in laravelpanel?
Thanks to everyone.

@MehmetOzkose  read this question Q: How can I display/edit data which is fetched from more than one table in CRUD ?
in fag http://laravelpanel.com/docs/master/faq

$grid = DataGrid::source(Product::with('category','material');
class Product extends \Eloquent
{
protected $table = 'products';
public function category() {
    return $this->belongsTo('Category', 'category_id');
}

public function material() {
    return $this->belongsTo('Material', 'material_id');
}

}
In example category,material and products are the cruds listing the all records  created by panel. So I need a model file like above to establish a relation with these three cruds. Is it right?Maybe I need more laravel experience.
Thank you.

@MehmetOzkose Ok as I've understood you want to create a relation between two cruds, it's not straightforward but to do that you should :

add a link in your 'galleries' crud :

	$imagesUrl = url('/panel/galleryImages/all?id={{ $id }}');
	$this->grid->add('View Gallery Images', '');

Then create the galleryImages crud and remove this crud from the 'links' table.

Then in your galleryImages crud you have to add a condition to list just the images of that specific gallery :

        $imagesFilter = \App\galleryImages::with('galleries');
        $this->filter = \DataFilter::source($imagesFilter);

        $images = \App\galleryImages::whereHas('galleries', function($q) {
            $q->where('id', '=', \Input::get('id')); // id of gallery
        })->with('galleries');

	$this->filter = \DataFilter::source($images);
        .
        .

You also should edit the 'Add' button in 'galleryImages' crud to include the 'gallery_id' parameter and then in edit section of galleryImages crud, you should pass the gallery_id as a hidden parameter to get that parameter and save it :

	$this->edit->add('gallery_id', '', 'hidden')->insertValue(\Input::get('id'));
`````

Thanks for the reply. I updated my files as you told but i got "Exception in CrudController.php line 70:
This url is not set yet!" error. I googled but couldn't find something that is working. Is it a route error?

i deleted these lines in vendor/serverfireteam/panel/controllers/CrudController.php
else if (!in_array($this->entity, $configs)) {
throw new \Exception('This url is not set yet!');
}
and then
modified galleryImages model  so the problem was solved;
public function galleries()
{
return $this->belongsTo('App\galleries','gallery_id');
}

@MehmetOzkose  are you sure you need to remove
else if (!in_array($this->entity, $configs)) {
throw new \Exception('This url is not set yet!');
}
You just need to put in link table

But i don't wan't gallery_imagesController link to be seen on left side menu.

@MehmetOzkose Okay

i can't send the input get value to edit view file by this way:
$this->edit->add('gallery_id', '', 'hidden')->insertValue(\Input::get('id'));
How can I do that?

Try this
$this->edit->add('gallery_id', \Input::get('id'), 'hidden');

It didn't work. In modify action and in show action the get value passes, but in 'Add' button it doesn't.

@MehmetOzkose The 'Add' button does not get a parameter by default. So you should override the datagrid view of rapyd in order to add the parameter. You can add a folder inside the 'resources/views/vendor/' folder named 'rapyd' and make a copy of 'datagrid.blade.php' file and edit it as required.

@alenoosh thanks for the reply.
You mean to add a parameter as get value into datagrid.blade.php. Can you please give me an example?
{!! url('panel/'.$current_entity.'/edit') !!}

@MehmetOzkose Yes exactly I mean to add a parameter to 'edit' url in the datagrid.blade.php file inside the resources/views/vendor/rapyd directory :
{!! url('panel/'.$current_entity.'/edit?id=' . $id) !!}
````
You should set the value of $id previously.

Thanks. It works

@MehmetOzkose how did you solve the problem that the ID didn't get passed on to the hidden field when "adding" a new image?
$this->edit->add('gallery_id', \Input::get('id'), 'hidden');


Re-add Dart Analyzer

I think this should be ran on pr too (or pr only) if we shift to a pr centric dev cycle

It does run on pull requests too

I mean I guess pr only makes sense too, we already set main to be a protected branch but I think leaving it for push on main can't hurt


Index.html update breaks acl link header

Since #806 the acl link for a container is now going to point to /index.html.acl instead of /.acl (discovered by integration test when adding a default index.html for the root container).

It's just the link, right? The applicable ACL is ok?

It's just the link, right? The applicable ACL is ok?

Yes, those two are completely separate.


Fixed test fixture's abbreviation for "Universal Declaration of Human Rights"

Important stuff! 😄

@regexident 😂 I managed to find a few more cases of this throughout the project. But hey — partial credit for consistency, amiright?


SR-IOV interfaces are not reported correctly when the guest has no guest-agent.

Is this a BUG REPORT or FEATURE REQUEST?:
/kind bug
What happened:
When looking at a VMI status with SR-IOV interfaces and no guest-agent running, the reported interfaces are wrong.

In cases where only SR-IOV interfaces are defined, it will wrongly show the interfaces with just their network name and without validating that the data is in sync with the domain (e.g. the device may be detached after a migration, but will still be reported in the status).
In cases where "regular" interfaces exists in addition to the SR-IOV one, the SR-IOV interfaces will not appear in the report. This occurs even though the device can be seen in the domain configuration (as a hostdevice).

What you expected to happen:
The SR-IOV interfaces should be reported correctly, based on the domain configuration, even when the guest-agent is not running in the guest.
How to reproduce it (as minimally and precisely as possible):
Unit tests should be enough to show this behavior. See https://github.com/kubevirt/kubevirt/pull/6951
Raise a guest with no guest-agent and at least one SR-IOV interface attached should show the problem.

/sig network

Worth to update this ticket with what you expect still to be done
after https://github.com/kubevirt/kubevirt/pull/7051 is merged please

/reopen

/assign @EdDev


New schema format

This is a PR adding a new schema MVP that intends to encode Rust types a little better than JSON schema does.
The biggest differences are:

Full support for all kinds of enums Rust supports (tuple, named, unit) and enums without cases (so non-constructable types such as core::convert::Infallible)
Full support for all kinds of structs Rust supports (named, tuple, unit)
Full support for tuples
Dedicated HexBinary, Timestamp, Optional, Checksum, Binary, and Address types
Slightly more compact representation through using numeric indices vs. path names
Support for arbitrary-size integers by encoding their precision and whether they are signed
Support for arbitrary-size decimals by encoding their precision and wehther they are signed

God those warnings I added.. they're really "we have compiler warnings at home" material


Range Input throttle

Problem
This component gives users the ability to drag the slider and update the value, which can cause too many request on every change and fills up out tracking data as well.
Fix
Added throttling to only update after half second after user stops dragging slider.

I have a couple of thoughts that you can take or leave, depending on the problems you want to solve in this PR. Feel free to move forward if you don't want to address any of it.

I feel like a debounce function should be self-contained, and that the timer id should not be assigned to a reactive data property. Although it seems to work, it seems like it could lead to unexpected behaviour to assign the timer id to something that's reactive.
~The input event is being fired when clicking on the bar, even though the handle does not move along the bar. This may need to be handled separately to the debounce~ Gaurav corrected me, this is because the step is too small to see, but it is moving
I think that we should move the debounce into the computted setter, or a watcher and handling debouncing there. We should allow the barMinValue and barMaxValue to update as they please. The setting of the global state should be a side-effect, and be debounced. This is my feeling, however, feel free to correct me if this is wrong.
Can we use lodash? I'm not opposed to doing it yourself, but the lodash function is available to us and is re-usable.

There is a good example of a debounce function being applied in this piece of Vue documentation: https://v2.vuejs.org/v2/guide/computed.html#Watchers

I have a couple of thoughts that you can take or leave, depending on the problems you want to solve in this PR. Feel free to move forward if you don't want to address any of it.

I feel like a debounce function should be self-contained, and that the timer id should not be assigned to a reactive data property. Although it seems to work, it seems like it could lead to unexpected behaviour to assign the timer id to something that's reactive.
~The input event is being fired when clicking on the bar, even though the handle does not move along the bar. This may need to be handled separately to the debounce~ Gaurav corrected me, this is because the step is too small to see, but it is moving
I think that we should move the debounce into the computted setter, or a watcher and handling debouncing there. We should allow the barMinValue and barMaxValue to update as they please. The setting of the global state should be a side-effect, and be debounced. This is my feeling, however, feel free to correct me if this is wrong.
Can we use lodash? I'm not opposed to doing it yourself, but the lodash function is available to us and is re-usable.

There is a good example of a debounce function being applied in this piece of Vue documentation: https://v2.vuejs.org/v2/guide/computed.html#Watchers

A self contained timer might not work IMO, it will overwrite the state of throttle id each time update is triggered, let timer = setTimout will erase it, also because we have to check last state of timer, the assignment can only happen after the check before we clearTimeout.
Yes step is prop controller, can be handleded in page file directly.
You can still change the values the global state will only change once you stop dragging the pointers.
I wish we could use it, but we will have to global import it, which is probably not a good idea, sadly our components do not support import yet.

FWIW I think that we are globally importing lodash: https://github.com/snyk/topcoat-core/blob/f7d8174ed199322c74566d0167903bea0da79cbd/frontend/src/core.js#L154

FWIW I think that we are globally importing lodash: https://github.com/snyk/topcoat-core/blob/f7d8174ed199322c74566d0167903bea0da79cbd/frontend/src/core.js#L154
But feel free to move forward.

Oh, 😮.
No you are right, if that is already imported, I can use that.


Added @driver733 to the fan list

Added @driver733 to the fan list

@driver733 thanks!

The job is not in WBS, won't close the order


Fix missing ability to support 3d party devise-modules.

Fix missing ability to support 3d party devise-modules.
https://github.com/spree-contrib/spree_social/issues/143

Thank you @vladimir-shidlovsky, this has been applied to master branch.


[Android] should i call Fresco.shutDown() in reactActivity.onDestroy()

I tried the following steps:

start my RN app
exit by pressing back button
repeat 1,2 for several times

I found the memory keep increasing , and finally it lead to an OOM Exception.
With the help of AndroidStudio Monitor View, i found too many bitmaps were cached.
I tried to call Fresco.shutdown() manually in onDestroy, it seems better.
`@Override
protected void onDestroy() {
super.onDestroy();
Fresco.shutDown();   // call shutdown manually
if (mReactInstanceManager != null) {
mReactInstanceManager.destroy();
}
}`
Here are my questions:

When will the images cached by Fresco be recycled?
Do I need to release images manually?

Thanks guys....

This could be related to #8677. In theory, you should not need to do anything manually.

Have to clear Fresco stuff as well in onDestroy() of ReactActivity. Without it the memory of app process gets higher and higher wenn starting and closing the app frequently. Without it the problem is gone. Should be investigated in more detail because that is critical I guess. I did:
@Override
protected void onDestroy() {
    super.onDestroy();

    ImagePipeline imagePipeline = Fresco.getImagePipeline();
    imagePipeline.clearMemoryCaches();
    Fresco.shutDown();
}

This should have been fixed with recent React Native versions. RN was re-initializing Fresco which lead to these issues.

Thanks @oprisnik  & @norman-kapschefsky , I will do more tests with latest version.

Hi @JuanbingTeam I'll be closing this issue since there has been several updated versions of RN.

thank you, yes ,this has been fixed~


Maximum Response size reached while delete-route endpoint hit

Describe the bug
When the size of Routes increases in the Local-config.yml. And after this if we delete the route. We are not able to get the response as Response size is reached.
To Reproduce
Steps to reproduce the behaviour:

Populate the local-config.yml with more routes
Hit the delete-route endpoint
See error

Expected behaviour
As for now Delete Route returns all the Route as an Json Payload. But It should only return message : "The route is deleted" or an error : ("Route not deleted due to " + error message)
Screenshots

@aquibbaig @muskankhedia @Harkishen-Singh I want to work on this
Approach:

I will change the response Payload :
a.Data = "deleted successfully " in case of success and a.Data = "error message " in case of any error occurs.
I will change the status code to 200 (status OK ) if deleted and 404 if error occurs.


Remove version: Uncrustify.Uncrustify version 0.78.1

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

Close with reason: URL works;


Add GitHub action to comment on PRs with breaking changes

Description
This PR adds a new GitHub Action that runs on PRs targeting main, next, or releases branches. It will detect when a change is made to the "broken" section of a package.json file and alert the author of the PR to ensure they understand they are making a breaking change. Additionally, it will link the author to our wiki articles for guidance regarding making breaking changes.
See this example PR for a demonstration!
Reviewer Guidance
I'd like feedback on:

The wording of the PR comment, and if any additional information/links should be included.
Implementation details
If we think this is a valuable addition to our PR checks

Just for some context - as the things stand today, if user did make a breaking change, they will have to update broken section of package.json for typetests to pass and therefore PR can me merged? Therefore breaking change itself + json updates + breaking note will always be contained within a single PR?
Just FYI - we do have a bug around typetests, where we unintentionally pick up wrong package versions on the release, so we need to adjust typetests (to likely state incorrect information) to pass. We have work item around that (node upgrade).


ScoutCoinFabrik: Milestone 2

Project Abstract
This is the second milestone of the project ScoutCoinFabrik. The pull request associated to the the first milestone is the following:
https://github.com/w3f/Grants-Program/pull/1490
Scout is an extensible open-source tool (or set of tools) to assist Rust Polkadot / Kusama smart contract developers to detect common security issues and deviations from best practices. The objective of this second milestone is the delivery of a prototype tool after the realization of a proof of concept in milestone 1. The repository associated to this project can be found in the following link:
https://github.com/CoinFabrik/web3-grant
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

Thanks for the follow-up application @valeriacaracciolo, happy to see it. A couple of initial comments:

Since this is a new grant, it would technically be a single milestone, so you can go ahead and change the label to "Milestone 1" instead of "2" to avoid confusion when it comes time to submit it.
Are you able to expand a bit on what the prototype would look like? Would this just be a tool written in Rust? The more technical details you can provide, the better.
What kind of functionality will the CLI have?
Can you elaborate on what functionalities the VSCode extension would provide as well? (e.g. code completion, diagnostic errors, hover content, etc.) Would it be compatible with other ink! extensions such as this one for semantic analysis?

Hello Keegan, we will be updating our application tomorrow, but I just wanted to send over our replies to your inquiries, in case you have more comments:

Since this is a new grant, it would technically be a single milestone, so you can go ahead and change the label to "Milestone 1" instead of "2" to avoid confusion when it comes time to submit it.
Ok. We will modify this in the application file. We will add a note or reference to connect this application to the previous milestone.
Are you able to expand a bit on what the prototype would look like? Would this just be a tool written in Rust? The more technical details you can provide, the better.
We are to build a prototype that can analyze Rust code to detect vulnerabilities in ink! smart contracts and possibly in pallets and other pieces of code. This builds over the proof-of-concept tool [mention] (we've built and delivered as part of a previous Web3 Foundation grant) by:
a) Moving from a proof-of-concept (PoC) tool to a robust tool that integrates with a popular IDE (VSCode), includes a CLI, etc,
b) We will improve the precision of the detectors we included in the PoC reducing the rate of false positives, and
c) We will add more detectors to have reasonable coverage of the relevant security vulnerabilities that happen in smart contracts.
What kind of functionality will the CLI have?
For this prototype, we want to develop a simple command line interface like the one used in other static analyzers from other blockchains (eg: Slither https://github.com/crytic/slither, Rustle https://github.com/blocksecteam/rustle).
In particular, we will develop the possibility to run the prototype on smart contract files or directories.
The base command will be:
cargo scout file_name.rs
We will also include options for running subsets of detectors and triggering errors for CI/CD workflows.
Can you elaborate on what functionalities the VSCode extension would provide as well? (e.g. code completion, diagnostic errors, hover content, etc.) Would it be compatible with other ink! extensions such as this one https://w3f.github.io/Grants-Program/applications/ink-analyzer#future-plans for semantic analysis?
Our VSCode development will list security issues, highlight issues with squiggles and hover-over descriptions.
We will seek compatibility of this development with other relevant ink! extensions such as Ink! Analyzer https://w3f.github.io/Grants-Program/applications/ink-analyzer#future-plans.

Thank you so much for all your help Keegan
Best,

On 13 Apr 2023, at 21:31, Keegan | W3F @.***> wrote:
Thanks for the follow-up application @valeriacaracciolo https://github.com/valeriacaracciolo, happy to see it. A couple of initial comments:
Since this is a new grant, it would technically be a single milestone, so you can go ahead and change the label to "Milestone 1" instead of "2" to avoid confusion when it comes time to submit it.
Are you able to expand a bit on what the prototype would look like? Would this just be a tool written in Rust? The more technical details you can provide, the better.
What kind of functionality will the CLI have?
Can you elaborate on what functionalities the VSCode extension would provide as well? (e.g. code completion, diagnostic errors, hover content, etc.) Would it be compatible with other ink! extensions such as this one https://w3f.github.io/Grants-Program/applications/ink-analyzer#future-plans for semantic analysis?
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1666#issuecomment-1507507273, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBOA7SUASDPYBUSVYVUE2DXBBIBBANCNFSM6AAAAAAWZLEN3Q.
You are receiving this because you were mentioned.

Thanks for the answers @valeriacaracciolo I will go ahead and mark the application as ready for review so other committee members can comment. Feel free to ping me once the application has been updated.

I will also share the application again with the rest of the team.

Awesome, thank you so much David
Best,

On 8 May 2023, at 15:48, David Hawig @.***> wrote:
I will also share the application again with the rest of the team.
—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1666#issuecomment-1538390323, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBOA7SD4JCEN5WPBI5T5X3XFD2RLANCNFSM6AAAAAAWZLEN3Q.
You are receiving this because you were mentioned.

Hello Sebastian! Thanks for your inquiries. We have just replied to both of them. Please let us know if you have further comments.
Best,

On 8 May 2023, at 17:55, Sebastian Müller @.***> wrote:
@semuelle requested changes on this pull request.
Sorry for the late reply here, @valeriacaracciolo https://github.com/valeriacaracciolo. You did some useful work in your first grant and generally I think it makes sense to continue.
In applications/ScoutCoinFabrik_2.md https://github.com/w3f/Grants-Program/pull/1666#discussion_r1187609351:

+- Estimated duration: 5 weeks
+- FTE:  5
+- Costs: 30,000 USD

+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| 0a. | License | MIT |
+| 0b. | Documentation | Documentation hosted on a separate webpage. |
+| 0c. | Testing | Integration testing. Specific tests for every linting detector based on code examples and snippets of smart contracts. |
+| 0d. | Docker | Does not apply at this stage. |
+| 0e. | Article | We will upload a report summary to our blog. |

1.a | Research and Development | Vulnerability examples. In addition to the examples developed in Milestone 1 of ScoutCoinFabrik PoC, we will develop more code examples and snippets of vulnerabilities, best practices, and enhancements related to smart contracts written in ink!. |
1.b | Research and Development | Further example versions of vulnerabilities developed in Milestone 1 of ScoutCoinFabrik PoC. This step is geared to provide a wider set of examples, therefore improving our ability to measure the precision of our prototype and any other ink! vulnerability detection tool. |
2.a | Development | Building a prototype that improves over the development of Milestone 1 of ScoutCoinFabrik PoC, detecting more classes of vulnerabilities and improving in precision on existing detectors. We are to build a prototype that can analyze Rust code to detect vulnerabilities in ink! smart contracts and possibly in pallets and other pieces of code. This builds over this proof-of-concept tool we've built and delivered as part of a grant for the web3 foundation by:  a) Moving from a proof-of-concept (PoC) tool to a robust tool that integrates with a popular IDE (VSCode), includes a CLI, etc,  b) We will improve on the precision of the detectors we included in the PoC reducing the rate of false positives, and   c) We will add more detectors in order to have a reasonable coverage of the relevant security vulnerabilities that happen in smart contracts. |
2.b | Development | Command line interface for the prototype. For this prototype, we want to develop a simple command line interface like the one used in other static analyzers from other blockchains (eg: Slither, Rustle).  In particular, we will develop the possibility to run the prototype on smart contract files or directories.  The base command will be: cargo scout file_name.rs  We will also include options for running subsets of detectors and triggering errors for CI/CD workflows. |
2.c | Development | VSCode integration for the prototype. Our VSCode development will list security issues, highlight issues with squiggles and hover-over descriptions. We will seek compatibility of this development with other relevant ink! extensions such as Ink! Analyzer. |
What do you mean by compatibility with other extensions?

In applications/ScoutCoinFabrik_2.md https://github.com/w3f/Grants-Program/pull/1666#discussion_r1187610314:

+### Milestone 1: Prototype

+- Estimated duration: 5 weeks
+- FTE:  5
+- Costs: 30,000 USD
+
+| Number | Deliverable | Specification |
+| -----: | ----------- | ------------- |
+| 0a. | License | MIT |
+| 0b. | Documentation | Documentation hosted on a separate webpage. |
+| 0c. | Testing | Integration testing. Specific tests for every linting detector based on code examples and snippets of smart contracts. |
+| 0d. | Docker | Does not apply at this stage. |
+| 0e. | Article | We will upload a report summary to our blog. |

1.a | Research and Development | Vulnerability examples. In addition to the examples developed in Milestone 1 of ScoutCoinFabrik PoC, we will develop more code examples and snippets of vulnerabilities, best practices, and enhancements related to smart contracts written in ink!. |
1.b | Research and Development | Further example versions of vulnerabilities developed in Milestone 1 of ScoutCoinFabrik PoC. This step is geared to provide a wider set of examples, therefore improving our ability to measure the precision of our prototype and any other ink! vulnerability detection tool. |
2.a | Development | Building a prototype that improves over the development of Milestone 1 of ScoutCoinFabrik PoC, detecting more classes of vulnerabilities and improving in precision on existing detectors. We are to build a prototype that can analyze Rust code to detect vulnerabilities in ink! smart contracts and possibly in pallets and other pieces of code. This builds over this proof-of-concept tool we've built and delivered as part of a grant for the web3 foundation by:  a) Moving from a proof-of-concept (PoC) tool to a robust tool that integrates with a popular IDE (VSCode), includes a CLI, etc,  b) We will improve on the precision of the detectors we included in the PoC reducing the rate of false positives, and   c) We will add more detectors in order to have a reasonable coverage of the relevant security vulnerabilities that happen in smart contracts. |
What do you mean by prototype? I just see a list of detectors https://github.com/CoinFabrik/web3-grant/blob/main/detectors/README.md in the linked repo.

—
Reply to this email directly, view it on GitHub https://github.com/w3f/Grants-Program/pull/1666#pullrequestreview-1417064886, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARBOA7QG3PX6DVGKHTDKBALXFEJQ7ANCNFSM6AAAAAAWZLEN3Q.
You are receiving this because you were mentioned.


Implement Issue Reminder Workflow🚀

Description: Create a GitHub Actions workflow that sends reminders on open issues without updates. The workflow should post a comment prompting assignees to take action.
Expected Benefits:
Improved responsiveness and prioritization of tasks.
Increased overall productivity.
please assign me with level3 label @vansh-codes

it should share reminder in 10 days
its a level1 task


Can we get a JSFiddle for vue-multiselect 3.0 branch with Vue 3?

Is there a jsfiddle that shows the 3.0.x branch working with Vue 3?
I'm trying to add vue-multiselect to my Vue 3 app.  I'm not using a build manager or npm.
I'm using the following CDN links:
<EMAIL_ADDRESS><EMAIL_ADDRESS>I'm seeing two errors in the browser console:
Uncaught ReferenceError: vue is not defined
Uncaught TypeError: window.VueMultiselect is undefined

Sorry i'm budging in but i couldn't find any info on the matter and i don't wanna create a new topic for such a small question.. Will the 3.0 version be compatible with the composition api?
I'm using webpack to completely remove the option api in my project and many other packages that claim they are Vue 3 compatible, are in fact compatible with the option api only

Hi @wkrick looks like our builds aren't quite working as you would expect them. I believe I have implemented a fix for this, and hopefully will be released soon.
@lebadapetru we are wanting 3.0 to be compatible with the composition api when we launch stable, however this is still a WIP and may take some time to actually get there.

Hi @wkrick looks like our builds aren't quite working as you would expect them. I believe I have implemented a fix for this, and hopefully will be released soon.

@mattelen -  Awesome!  Thank you for looking at this.  I posted some test code over on StackOverflow because I thought I was doing something wrong as the V2 fiddle code didn't work anymore and vue-multiselect 3 was supposed to be "mostly backward compatible" with vue-multiselect 2...
https://stackoverflow.com/questions/67745654/how-do-i-get-vue-multiselect-3-working-with-vue-3-v2-v2-works-fine-in-this-ex
As soon as your fix gets released, I'll update my StackOverflow question.

Is it fixed yet? You see I have this project that needs to work yesterday...

@shentao @mattelen - Will there ever be a new release that includes this change?  If not, is there a page somewhere that explains in detail how to make my own release build?

Hiya, was there ever a resolution for this?

@jaulin No resolution.  I don't think this project is active anymore, sadly.  I recently started working with PrimeVue and it meets all my needs.

@jaulin No resolution. I don't think this project is active anymore, sadly. I recently started working with PrimeVue and it meets all my needs.

Cheers mate 👍 was struggling to find an alternative that supports VueJS 3 and without using NPM.

@jaulin - I understand you not wanting to use NPM.  I was against using npm for a long time too but I finally tried it a few months ago. The new "Vite" build system for Vue3 makes everything so easy.  Here's what it looks like to set up a basic Vue3 project using the vue template and then add PrimeVue...
npm create vite@latest my-vue-app -- --template vue
cd my-vue-app
npm install
npm install<EMAIL_ADDRESS>--save
npm install primeicons --save
npm run dev

Which alternative?

Why is this issue closed?


Document the usage of multiple arguments for a function on a template string

i.e. the function "number" accepts many arguments, but what's the syntax? I don't know.

I gave an example in your previous issue. Ill be adding more examples to a few different places to help clarify. If anything else is not clear enough to understand please let me know and ill try to add as much as i can to make it more clear.


Bug 11712101: Hoist CheckObjType out of loops only when the operand's containing object type is also invariant

Check object type of argument to CheckObjType before hoisting it out of a loop, to avoid hoisting it over a DeleteFld that invalidates the type.

@ricobbe,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:shipit:


Update build-deploy with security-compliance branch changes

Update build-deploy with security-compliance branch changes.
Secure Coding Practices Checklist Link

https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Checklist

[ ] Input Validation
[ ] Output Encoding
[ ] Authentication and Password Management
[ ] Session Management
[ ] Access Control
[ ] Cryptographic Practices
[ ] Error Handling and Logging
[ ] Data Protection
[ ] Communication Security
[ ] System Configuration
[ ] Database Security
[ ] File Management
[ ] Memory Management
[ ] General Coding Practices

Codecov Report
Patch coverage: 67.93% and project coverage change: +22.64 :tada:

Comparison is base (209c0c9) 50.14% compared to head (f1cbe33) 72.78%.

Additional details and impacted files
@@             Coverage Diff             @@
##           master     #316       +/-   ##
===========================================
+ Coverage   50.14%   72.78%   +22.64%
===========================================
  Files          13       25       +12
  Lines         357      746      +389
===========================================
+ Hits          179      543      +364
- Misses        178      203       +25

Impacted Files
Coverage Δ

clean_expired_records.py
0.00% <0.00%> (ø)

historical_system_profiles/mgmt_views/v0.py
100.00% <ø> (ø)

kafka_listener.py
0.00% <0.00%> (ø)

standalone_flask_server.py
0.00% <ø> (ø)

wsgi.py
0.00% <ø> (ø)

..._system_profiles/notification_service_interface.py
35.00% <35.00%> (ø)

...ical_system_profiles/baseline_service_interface.py
39.13% <39.13%> (ø)

historical_system_profiles/archiver.py
54.44% <54.41%> (+54.44%)
:arrow_up:

historical_system_profiles/config.py
67.03% <60.52%> (-26.91%)
:arrow_down:

...torical_system_profiles/drift_service_interface.py
66.66% <66.66%> (ø)

... and 14 more

... and 3 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

/retest

/retest


-TypeGraph Visitor for incremental builds

I'm not expecting this to be merged yet, but it's a good time to circulate for feedback. I'm not sure we need this included in J2CL, but it might be nice to have a hook so a custom use provided visitor can be run.
I was unable to use the LibraryInfo as its information is not complete and anything visible to JS is not exported as it's more aimed at pruning - but it works in a similar way. I also created my on simple, CVS style, format to read/write the information - because it's compact and fast - much smaller than the json. For incremental refreshes, we want to cut every bit of time we can.
For this approach to work it expects the IDE to ensure all compilation errors have been resolved, before being passed to j2cl. Although it gracefully handles when that is not the case. While a subset of .java files are passed for transpiration, it uses .class output from the other classes to ensure everything resolves correctly. We have found this to work fine, with our j2cl Quake port.
The code works in two phases. The first phase takes the incoming changeset (as defined by timestamp changes since last iteration) and uses the graph information, if any, to build the expanded list of files that need to be retranspiled. This first phase is done before calling j2cl, such we do in our maven plugin already.
The second phase is after the j2cl produces it's compilation units, and it outputs the new graph information. Note, as it has all the graph information from the previous call, so even if a subset of java files are passed, it is able to ensure a full graph write out on each iteration.
The visitor builds up a list of all the members, and builds a callee/caller graph. "Impact" tracking is added for a member that calls another member who has as different JS name specified in the annotation - as it's possible to change the js name, and the IDE will not trigger refactor in the caller and thus no timestamp change. This way it is ensured the caller is still added to the transpiration changeset. As other issue are identified, they can be added to impact tracking too.
I have added a unit test, to check the main types of issues. We have used this with the j2cl quake port in our maven toolchain and iterations went from 7s to 1.5s for each iteration.


Check explicit indexes when comparing two xarray objects

Is your feature request related to a problem? Please describe.
With the explicit index refactor, two Dataset or DataArray objects a and b may have the same variables / coordinates and attributes but different indexes.
Describe the solution you'd like
I'd suggest that a.identical(b) by default also checks for equality betweena.xindexes and b.xindexes.
One drawback is when we want to check either the attributes or the indexes but not both. Should we add options like suggested in #5733 then?

I also think identical should check xindexes for equality.
I think those options could be provided for assert_equal where you can turn on/off the checking of indexes and attrs.
So identical is a really strict check; while equal is a little looser, and allows some configuration

See the unfinished PR #4760 (which I likely won't finish) for inspiration on adding an argument to assert_* (which I found non trivial).


LSTM example does not work with synchronous all_reduce interface

The LSTM example fails to finish training with the all_reduce interface. It was made for the asynchronous param_sync interface with workers sending messages asking what to do next and writing to shared memory when told.
With all_reduce, the workers train, and one of them converges and stops, but the other get stuck in its training loop when it tries to calculate f_grad_shared. It might be trying to perform an all_reduce but cannot communicate with workers who have finished.
A suggestion it to rewrite the example from scratch for the synchronous interface. This would involve having workers train together, then wait to validate together, and stop together. Ideally, the validation set would be split between workers.

I also get stuck with this example. My log info is that:
Mapped name None to device cuda0: Tesla K40m
PCI Bus ID: 0000:0D:00.0
Using cuDNN version 5103 on context None
WARNING! Failed to register in a local GPU comm world.
Reason: Error loading library
WARNING! Platoon all_reduce interface will not be functional.
Traceback (most recent call last):
File "lstm_worker.py", line 662, in
numpy.random.seed(SEED + worker.global_rank)
File "~/tools/platoon-master/platoon/channel/worker.py", line 215, in global_rank
return self._global_rank
AttributeError: 'Worker' object has no attribute '_global_rank'
Is there anyone who can figure it out? Thanks.

@dvector89 , this sounds like libgpuarray has not been linked to NCCL. You must install NCCL from nvidia's website, then build libgpuarray, cmake should say it found NCCL.

Thanks @slefrancois I'll try it.

@slefrancois I'm failed to install NCCL. I installed it according to https://github.com/NVIDIA/nccl . The error information is below:
[@nk nccl-master]$ make CUDA_HOME=/usr/local/cuda test
Compiling src/libwrap.cu                      > /search/odin/shiliangliang/tools/nccl-master/build/obj/libwrap.o
nvcc fatal   : Value 'gnu++0x' is not defined for option 'std'
make: *** [/search/odin/shiliangliang/tools/nccl-master/build/obj/libwrap.o] Error 1
Could you give me some advice? Thanks.

That looks like an issue with your local environment, either the compiler configuration or CUDA installation.
I think this is beyond the scope of this issue, if you need further help I recommend you use support channels for NCCL or maybe the theano-users mailing list.

This is for the NCCL channel. But this error remind me that maybe you don't
use a good g++ compiler version.
On Tue, Dec 20, 2016 at 10:02 AM, Simon Lefrancois<EMAIL_ADDRESS>
wrote:

That looks like an issue with your local environment, either the compiler
configuration or CUDA installation.
I think this is beyond the scope of this issue, if you need further help I
recommend you use support channels for NCCL or maybe the theano-users
mailing list.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mila-udem/platoon/issues/78#issuecomment-268265055,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AALC-5kEPsm5wRpu6AbevBoVz0TZDXtZks5rJ-3sgaJpZM4Ks_WL
.

Closed by #83.


Browser support header needs to be parsed as HTML

Hmm, this message is quite annoying; because it's a flash message it keeps reappearing after you close it. It also overwrites any other flash messages such as "you have been logged out".
I reckon we'd be better putting this as a separate message on the home (root) page only. What do you think @grdw?

I reckon we'd be better putting this as a separate message on the home (root) page only. What do you think @grdw?

Yes. That would make the most sense. Although I would like to argue that it would also be practical to have it on a scenario's page. I can see people going directly to a single scenario and not entering from the front-page. However, I can't say that for sure because #2653 hasn't been implemented yet 😅

Moved to 'Deploy June 2018' milestone.


  When I searched it shows that we can upload 10k images

@drakshayanidesai Did you receive an error when you uploaded the images?


check terraform scripts for windows VM provisioning accept input vars

we need to check if terraform apply -var xyz=zxy .. works with terraform on @sofusalbertsen and maybe @Sharor machines.
It possibly need single quotes .. terraform apply -var 'xyz=zxy' ..
The scripts in question are : https://github.com/Praqma/provision-win-docker

We made it spin up now, @sami-alajrami  - I just need to go verify they work as they should. Sofus solved this :)

We need to check the commands provided. I changed in the configfile!=best solution.

If the single quotes don't work, I have tried the following docker image and it works  :
$ cd terraform
$ docker run -i -t -v $(pwd):/tmp  hashicorp/terraform:light init /tmp; terraform plan  -var admin_password=MyWindowsServer2016ValidPassword! -var instance_count=1

Note that the command above is plan which plans but does not create resources.

@sami-alajrami  the VM's are painfully slow at extracting files. I think it's the harddisk type used. Can you change so that it's their high performance SSD drives that are used?
Link: https://aws.amazon.com/ebs/details/

@sofusalbertsen the VMs take by default the general purpose ssd ebs volumes.

Backed by Solid-State Drives (SSDs), General Purpose (SSD) volumes provide the ability to burst to 3,000 IOPS per volume, independent of volume size, to meet the performance needs of most applications and also deliver a consistent baseline of 3 IOPS/GB.

the next level is the provisioned IOPS ssd. Here is a comparison.

Would like to change the volumes to be provisioned IOPS?

@sami-alajrami  we just had a problem with the machines beeing really slow at downloading+unpacking images for the training.
But a better thing to do is making a script that pulls down the following images on the machines:
microsoft/nanoserver
microsoft/windowsservercore
microsoft/mssql-server-windows-developer
microsoft/dotnet-framework-samples
microsoft/dotnet-framework-build
microsoft/iis
Is that doable in the terraform script?

@sofusalbertsen yes this is doable.
I would suggest to do it in the Packer AMI VM image instead because doing it in terraform means that each VM would be pulling the images separately and the provisioning time of VMs would take much longer. With Packer, only the VM image will pull the docker images.

And just checked the script for accpetance of variables, and it works with:
./terraform apply -var instance_count=10 -var admin_password=Praqm@2017
I think the reason why it did not work last time was because i did:
./terraform plan -var instance_count=10 -var admin_password=Praqm@2017
and
./terraform apply without any variables.
But now everything works according to documentation :)

@sami-alajrami could be an idea to do it in packer.
Only thing there is if we plan to reuse the image after some time, then the original pulls will be outdated.
But I do not know if the strategy is to make a new AMI for every time we run this training.
If it is best practice, then yes by all means do it once instead of on each VM :)

@sofusalbertsen good point, it is not necessarily a strategy. But I guess that could work.
It is about what is more practical for you. If you are OK with waiting for VMs provisioning using terraform to pull each image, then we can do it in terraform and have VMs up to date. If you don't  have the patience, then we can do it in packer :)
It is your call. :-D

When spinning up servers before a training i have all the time in the world, as long as i know it will take time ;)

@sofusalbertsen it is done in terraform now. You can test it whenever you have the time and ping me if anything else is needed.

@sami-alajrami thanks a lot, you have really been helpful, much appreciated!

@sami-alajrami  this works now, sorry for keeping you waiting so long!


docs(configuration): document snapshot

closes https://github.com/webpack/webpack.js.org/issues/3936

There are some grammar and lexical things pointed for applying or discussion. I have noticed missing spaces on the types. Besides, it feels like both hash and timestamp explanation is very repetitive and could be given once before explaining for each wdyt?

Regarding the repetitive blocks, I would prefer to keep them since people might access those options from url directly, and they have to check other option to find the explanations of hash and timestamp.

Hmm true, ok agree its a valid point to keep them, thanks

Thanks! I think it got much better with all the effort 👍


Updates Godeps to a compiling/stable state

Includes newer docker/libtrust and crowdmob/goamz

We are still getting up and running with Godeps. Thanks for taking the time update this.


Update fldigi to 4.0.2

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Travis CI is reporting:

appcast checkpoint mismatch
Expected: 893060e24002b65d1e34da33fba64724cb6648e29f83d7e25f7cb1465265fd7c
Actual: bed8ba38f33a34e1d0c83dd196babcb31cc68126fe5a14a082664a8601d1303e


how set animation for updating data component

This issue about updating data example
So, how add animation Seies and XAxis when data updating like this
https://codepen.io/atticweb/pen/GZKvgv
for see animations series scroll up down up down up down

right now there are no animations anywhere in the lib, it would be a nice addition though. Although I would like to think about animation on the whole,
for e.g. in zoom, and pan to load more data also appearing slowly in an animation, hover tooltip box moving, or even when a new LineSeries is added/removed it could animate in/out
This one is close to my heart to see these animations in place. When ever I think about this, it comes to mind that this will be too big of an undertaking with many edge cases and I pass. I like to hear your thoughts, it would be good if we could work together and bounce ideas on this

I would gladly help you, but while your project is complicated for the level of my knowledge, the more I do not know canvas at all, maybe later, when i figure out more in the code, I can make my own

No plans for now


chore: adjust eslint rules

Coverage remained the same at 100.0% when pulling 3d5d6240bd980870bd089242b4b85ad82e4442f9 on adjust-eslint into 9378c60cf865a151cafdd3cb5cd5c66830b9ed52 on main.

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Inherit seems misleading

The comment for Inherit states:
// Inherit takes values from the style in the argument applies them to this
// style, overwriting existing definitions. Only values explicitly set on the
// style in argument will be applied.

But the code seems to behave in the opposite way: https://github.com/charmbracelet/lipgloss/blob/master/style.go#L146
The code skips existing definitions, it does not overwrite.  Is this intentional?

You're absolutely right, this is poorly worded. The implementation is as-intended though. The idea is that, say, if you had a background color at the top level you could cascade it to children unless one of the children has a background color set.
Congrats on making Golang Weekly this week, btw!

Got it!  I managed to get the desired behavior for exactly that kind of use case (base -> column -> row -> cell precedence of style application), I just had to reverse the order of the calls.  I can offer a quick PR to reword the comment for clarity.
And thanks!  Been a lot of fun working in this ecosystem, looking forward to more!

Wonderful. By all means, please do submit a PR — !


WOM: Add a warning if the group being synced isn't the same as the current group

If you play on two accounts and are in a different clan in each account, you can accidentally override the group if you sync the group on the account that is not in your main clan. Adding a warning on sync if the clan being synced isn't the same group that is already synced on WOM.
This could possibly be done by checking the clan name (This won't work if the WOM group name isn't the same as the in-game clan name) or maybe checking that the clan owner is the same (This won't work if the clan ownership is transferred).
A good option would be to check the amount of players being removed. If it's a completely different clan being synced, a lot of players would be removed by syncing.

If it's a completely different clan being synced, a lot of players would be removed by syncing.

if X percent of players differ, we can conclude it's a different clan and show a confirmation dialog, I'm not sure what an appropriate threshold would be, 50%?


Error page

Hi Christoffer, once again, thanks you for this app, I wish you sell it.. I was wondering if its possible to get a log of errors, something out of no were, Langly becomes a blank white screen, and I don't know what's causing this, it would be great to have a error window
Hope you consider this

Hi. It's a white screen every time you load the app?
If you clone the code and run the app with npm start you can open the devtools and see what is causing the problems. If you find an issue I would welcome a pull request as I don't have the capacity to work on this at the moment.
Thanks for your understanding


Board service, model and mapper is added

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[x] What does this PR do?
This PR has board service, model and mapper

[ ] What issue/task does this PR references?

[ ] Are the tests Included?

Optional

[ ] Is the documentation Included?

[ ] Are the Release Notes included?

[ ] @mention(s) to expected reviewer(s) included

[test]

@sanbornsen Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2707 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2707 and visit http://localhost:5000 to access it.

@sanbornsen Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2707 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2707 and visit http://localhost:5000 to access it.


QUIC network implementation

Add a QUIC network implementation to Handel.

The QUIC network is around 4 times slower than the UDP network.
The performance hit comes from the handshake phase and QUIC-go doesn't support 0-RTT handshake yet:
https://github.com/lucas-clemente/quic-go/issues/438
After playing with the AcceptCookie callback I managed to decrease the performance hit to 3.5x of UDP network for 500 nodes.


Use aws_s3_bucket's website_endpoint for cloudfront origin domain name

This works as of AWS provider 1.37.
This seems to indicate that https://github.com/terraform-providers/terraform-provider-aws/issues/1117 has been fixed.

I just tried this out, new bucket and everything. I used the same config I'd been using but with a different domain, cleared .terraform, and used my patched version of this module:
module "main" {
  source = "git::https://github.com/colindean/terraform-aws-s3-cloudfront-website.git?ref=patch-1"#"github.com/riboseinc/terraform-aws-s3-cloudfront-website"
…
}

Well, the S3 bucket website works, the CloudFront domain name works, and I'm just waiting for DNS propagation to verify the public FQDN for the intended subdomain.

Thank you @colindean ! I've confirmed the "dot" syntax works, and let's merge this.


Set dynamic column group

Current column group cannot be updated, is there anyway to achieve this?

@lvyandev
There is no function to change the column group yet.
I'll consider this.
Thank you for your comments.


Delete unused param about get_construct_message_f

Delete unused param about get_construct_message_f

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged, thanks for the contribution.


please add a teal accent

Details
cyan/turquoise accent #1D817F

Do you have links/screenshots of themes using that color to be used as a reference?

Do you have links/screenshots of themes using that color to be used as a reference?

I've seen a version very similar to solarized dark in a yt video but the color was more like turquoise than dark, and it looked great!

It was something like that what I saw

Something like this?

Actually I was referring to something a little more light blue and less green, I don't know if that's possible this is the hex color code:
#008080

Sorry for the delay. It's not exactly the color you mentioned, but it's very close. I hope you like it.

Sorry for the delay. It's not exactly the color you mentioned, but it's very close. I hope you like it.

Is there an ETA for this new color?

Sorry for the delay. It's not exactly the color you mentioned, but it's very close. I hope you like it.

Is there an ETA for this new color?

It will be released alongside Node-RED v4.1.


Add support for LaunchAgents on macOSX

Summary
I'd like to add support for LaunchAgents (user daemons in macOSX). Use case is I'd like to use this package to manage user daemons. Here's kind of the overview of the differences:

Details
Currently this package supports only LaunchDaemons :
https://github.com/takama/daemon/blob/aa76b0035d1239b7bb3ae1bd84cd88ef2e0a1f1e/daemon.go#L9-L10
I'm wondering if you would consider adding support for LaunchAgents? Seems where we create the .plist file is the biggest difference (well, that and I guess permissions since it would run as the logged in user):
https://github.com/takama/daemon/blob/aa76b0035d1239b7bb3ae1bd84cd88ef2e0a1f1e/daemon_darwin.go#L28-L31
I'd like to take a stab at adding support for this. So consider this a scoping exercise of sorts to:

Gauge your interest - is this something you'd like me to contribute to your library?
Get feedback on approach - before I write any code, wanna know: are you're ok with the approach below?

On approach, I'm thinking of updating darwinRecord  to have an userAgent bool field ...
https://github.com/takama/daemon/blob/aa76b0035d1239b7bb3ae1bd84cd88ef2e0a1f1e/daemon_darwin.go#L17-L21
Actual implementation might be slightly different but the idea is provide a way to know what type of deamon we want and then internally change the flow based on use case e.g. use /Library/LaunchAgents/ instead of /Library/LaunchDaemons/ when it's a user daemon, etc.
Lemme know what you think.
References

https://developer.apple.com/library/archive/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/CreatingLaunchdJobs.html
https://apple.stackexchange.com/questions/290945/what-are-the-differences-between-launchagents-and-launchdaemons
https://ieftimov.com/post/create-manage-macos-launchd-agents-golang/
https://launchd.info/

A very good proposal.

Alright, thanks. Will take create a PR and we can take it from there.

See PR https://github.com/takama/daemon/pull/90.

Resolved in #90


New feature note find

note find finds notes using one or more keyword(s).

It searches for matches in a Note object's title and noteText fields.

Updated some test codes and created new tests for the new command.

Resolves #204

Coverage increased (+3.8%) to 64.947% when pulling 9c4bf479dcd9e39607bb6b095cad96133ea4854b on jomcruz93:new-feature-note-find into cc9c0379ab4eec05253b358401052bac3f3dcc2a on CS2113-AY1819S1-T16-1:master.


Adding inspect and big refactor to support shared run_id - WIP

Fixes #9

Coverage decreased (-1.9%) to 97.847% when pulling 8119646acb19763eaecf4c996906e1470f7e5264 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-0.3%) to 99.421% when pulling 6f26d86c0fe879061bac2cee6c48efd12567ea60 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-0.3%) to 99.423% when pulling 7ad23ee3391a6ec11be9731e7ffe70ced789d03a on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-0.3%) to 99.423% when pulling<PHONE_NUMBER>4a7bb434a19d330daa2157b3d4cbd8 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-2.3%) to 97.463% when pulling<PHONE_NUMBER>4a7bb434a19d330daa2157b3d4cbd8 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-0.3%) to 99.423% when pulling e10157b912161a9fc996af93a5dadbc8e51b3232 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-0.3%) to 99.431% when pulling 4b4afb34ceeb7ca1caf81b3f9ffd01ca6edfd4ab on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage increased (+0.03%) to 99.775% when pulling 027a413858c81f1750bcb6e7ccca41a471d39b86 on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage decreased (-74.7%) to 25.0% when pulling 404d4b49debc602cd22d227b158df1fe1c45e1eb on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.

Coverage increased (+0.3%) to 100.0% when pulling a53cd6db0b79296c296e00f1bbbfa75a47336bfb on 009_inspect_command into 993a4f5d32a6312424277e7c58b4bf58d1688308 on master.


README.md tweaks

All pedantic:

“IPUAC” -> “IUPAC” typo
added four missing ambiguous nucleotides to parenthetical list to
match claim of ‘all’ being counted
changed apostrophe after 5 and 3 to prime
“Plot” -> “Plots” to match tense of other lines
removed shell from code fence to remove inappropriate highlighting
of shell builtins (‘read’, ‘for’, ‘in’, ‘help’, ‘exit’, ‘do’)

Thanks!


feat(extra): add colorscheme windows terminal

The themes in extras/windows_terminal are Tokyo Night and its variations, so I copied the colors from the alacritty theme.
Here's how it looks:

Great!


Create GPT-Neo on CPU and set the correct device when running on gpus

No longer relevant/needed so closing this PR.


ItemStack abstraction wraps nulls and throws an error as a result

Simulate minecraft:air as a way to fix this

Note, older versions don't allow for an air item, they can just suffer with null exceptions, as the alternative is an exception of my own, or things silently failing


Plugin refactor

Code that imports a foo plugin should never need to import from ./foo/plugin, the IFoo interface and Token should be defined at ./foo.

Nice cleanup, thanks!


Add option to disable to-top rocket ship

This adds an option to remove the to-top rocket ship link from the bottom right of the page. I also fixed a typo in the config file since I was already there.

I have committed the changes manually, thanks for your contribution.


Allow spaces between header name and colon (fixes #88)

Maybe we can put the whitespace skipping in its own #[cold] #[inline(never)] function to keep it off the happy path.

I have restored 1.10 compat.


Merge changes from v1.1.0

@JonRoma this is a fresh migration based on pull request #4. Please review and merge it first. This should be merged into master, and be tagged v3.1.0. For review I recommend diffing against v1.1.0 not master.


Lazy initialization of "static" fields should be "synchronized"

This pull request is focused on resolving occurrences of Sonar rule squid:S2444 - Lazy initialization of "static" fields should be "synchronized"
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid:S2444
Please let me know if you have any questions.
Kirill Vlasov

@blackdrag Thanks for really great remarks!
Could you please kindly review the commit again ?

+1

Merged: https://github.com/apache/groovy/commit/c5f17abbe663577f7f05aa83aa7c79efc38784f0 (minus the change to JavadocFixTool.java, because this file was removed some months ago.)
Thanks!


Added support for Swift 4.2 and Xcode 10

Contents of this pull request:

Added support for Swift 4.2 without dropping support for Xcode 9.3 (and Xcode 9.4) and Swift 4.1 (in Xcode 9.3 and 9.4 warnings will remain due to the fact that the behaviour of IUO is not the same as Xcode 10 beta and as a result compilation fails in tests)
Also fixed support for Xcode 9.2 and swift 4.0.

i have an error in Xcode 10...
in EnumOperatior.swift : '<-' previously declared here

Well, after creating this PR I realized the meaning of the conversation discussed in #976 about Swift 3 (and obviously Swift 4.1) in Xcode 10. So, this is not a perfect solution, unless we somehow specify the compiler to always use the latest version that supports.

After taking a closer look to the Compiler Version Directive, I realized that there is a solution to this issue that doesn't need to change the swift_version in .podspec file.
This includes to change the compiler directives to:
#if !(swift(>=4.1.50) || (swift(>=3.4) && !swift(>=4.0)))
// Code targeting the Swift 4.1 compiler and below.
#endif

Of course this will add to the complexity of the directive check.

@gcharita Do you have any plans to merge this pull request?

@andre991 I am not the maintainor of this repository. The only thing I can do is to apply the latest suggestion that I mentioned in the previous comment. (I believe it is the best solution so far)

Ok, thanks @gcharita.  @tristanhimmelman Do you have any plans to merge this pull request?

For those who are building their apps using Xcode 10, can add the following statement into their Podfile:
```swift pod 'ObjectMapper', :git => 'https://github.com/alecdoconnor/ObjectMapper.git', :branch => 'Swift-4.2'`

@gcharita what do u think about fix warnings about deprecated flatMap in this pr?

@MortMerr I already done this in https://github.com/Hearst-DD/ObjectMapper/pull/980/commits/bed2ff971f64f3aa1aa31a3448155f96a31afecd with backward compatibility.
There was 1 case in Mapper.swift file and 2 in TransformOperators.swift file.
The rest of this was already fixed in https://github.com/Hearst-DD/ObjectMapper/commit/9fd123c5981027bfd73dcdddd7c465b4a67390fe by @tristanhimmelman. (I just added backward compatibility)

Thanks for fix @gcharita ! 👍

@gcharita  I tried it but still getting the error.

@aaparth I am testing it in:

Xcode 10 beta (swift 4.2, 4 and 3)
Xcode 9.4.1 (swift 3.3 and 4.1)
Xcode 9.2 (swift 3.2 and 4.0)

And everything looks ok.
Can you describe what exactly did you did and got the error?

@gcharita Thanks for your contribution
I got the 4.2 release from https://github.com/Hearst-DD/ObjectMapper/releases and everything works perfectly fine now.

@gcharita I'm using swift 3 for Xcode 10 beta. Still got the same error message when I tried to use your commit bed2ff9. Here is what inside my pod file:
pod 'ObjectMapper', :git => 'https://github.com/Hearst-DD/ObjectMapper', :commit => 'bed2ff9'
Do you know what could be the reason? Thanks.

@zhouhao27 this is not the right commit.
Just install the latest version (which currently is 3.3.0) or change the commit, in your Podfile, to
5985794


Fix generated code for MSP430 atomics

The current generated code for MSP430 atomics is not compatible with the rest of the generated code. This PR fixes this.

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

could you add ci tests to prevent this issue in future?
also update changelog

@YuhanLiin I've rebased. See https://github.com/rust-embedded/svd2rust/compare/fix-msp430-atomic


Multi-GPU for LSTM

I am experimenting with multi-gpu feedforwarding for LSTM models, by feeding two batches of sequences through a LSTM model. Here are two cases I am testing:
Single-GPU: simply pass the two batches sequentially on 1 GPU
Two-GPU: 2 parallel GPUs where each GPU takes care of one batch. My code is in the attached file (.txt --> .py).
However, instead of being 2X faster, the two-GPU case runs even slightly slower than the single-GPU case. It seems that even if I am initiating 2 GPU threads, the 2 batches are processed still sequentially, rather than in a parallel manner.
Does anyone see anything wrong with my code, or give any insight on how to do debugging? Your help would be highly appreciated.
lstm_multi_gpu.txt

Several issues I see:

log_device_placement=False,allow_soft_placement=True are passed to your Session ctor.  You should flip both, so as to verify that indeed two GPUs are used, but not just one.

For benchmark purposes, you should not just report one iter.  Best practices are to warm up for a few iters, then start timing (the trial runs), and report avg with std.

Automatically closing due to lack of recent activity. Please reopen when further information becomes available.


Metadata 2.1 PEP 566 is incomplete

https://www.python.org/dev/peps/pep-0566/#summary-of-differences-from-pep-345 and its link to https://packaging.python.org/specifications/core-metadata/ don't mention what happened to fields deprecated in 1.2 spec and how to handle them.
    Requires (in favor of Requires-Dist)
    Provides (in favor of Provides-Dist)
    Obsoletes (in favor of Obsoletes-Dist)

If they are removed, then the proper solution in #1396 is to fail with an error if they are used together with fieds only present in 2.1.

duplicate of https://github.com/pypa/setuptools/issues/1569?


Misleading error about choices sheet when extension omitted in select_one_from_file

Software and hardware versions
pyxform v1.12.2
Problem description
If select_one_from_file is given an argument without an extension, we get There should be a choices sheet in this xlsform. Please ensure that the choices sheet has the mandatory columns 'list_name', 'name', and 'label'.
Steps to reproduce the problem
Convert a form with a select_one_from_file with an argument without an extension like Bad select one from file.xlsx
Expected behavior
The error should be about specifying the filename extension (e.g. Filename for select_one_from_file "things" should include .csv, .xml or .geojson extension). I think it's reasonable to assume that if an extension isn't specified, the form designer made a mistake (it's rare to save files without extensions).

There doesn't seem to be an existing validation check for a missing file extension for select_one_from_file, or select_multiple_from_file. There are mostly implicit checks for invalid extensions. So perhaps this issue is more about adding a new error specifically for missing or invalid extensions.
A minor issue I spotted that could be fixed at the same time is that the existing choices sheet name validation should check for select_multiple_from_file as well as select_one_from_file, on L1124.


Get shell scripts for the examples running on CI

The examples each have a simple shell script for building on the AVR target. Get these shell scripts building the examples for target AVR running on CI.

Some builds are running, but need to check on return value of shell or result of ls commands in order to ascertani success/fail of build. For example example chapter09_08fails but is reportd as success.
Correct this before including the builds of the rest of the examples.

Some builds are running, but need to check on return value of shell or result of ls commands in order to ascertani success/fail of build. For example example chapter09_08fails but is reportd as success.
Correct this before including the builds of the rest of the examples.

Pass/fail on simple ls command is sufficient to ascertain build success on CI

Pass/fail on simple ls command is sufficient to ascertain build success on CI

Also fixes #94

Also fixes #94


Uncaught Error: The specified module could not be found./?\C:\ProgramData*\atom\app-...

[Enter steps to reproduce:]

...
...

Atom: 1.41.0 x64
Electron: 4.2.7
OS: Microsoft Windows 10 Enterprise
Thrown From: Atom Core
Stack Trace
Uncaught Error: The specified module could not be found.
\?\C:\ProgramData*\atom\app-1.41.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
At ELECTRON_ASAR.js:160

Error: The specified module could not be found.
\\?\C:\ProgramData\bruce.liu1\atom\app-1.41.0\resources\app.asar.unpacked\node_modules\keyboard-layout\build\Release\keyboard-layout-manager.node
    at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:160:31)
    at Object.Module._extensions..node (internal/modules/cjs/loader.js:722:18)
    at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:169:18)
    at Module.load (internal/modules/cjs/loader.js:602:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:541:12)
    at Function.Module._load (internal/modules/cjs/loader.js:533:3)
    at Module.require (/app.asar/static/index.js:72:46)
    at require (internal/modules/cjs/helpers.js:20:18)
    at customRequire (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:1:727373)
    at get_KeyboardLayoutManager (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:14:2746273)
    at get_manager (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:14:2746375)
    at Object.getCurrentKeyboardLayout (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:14:2746501)
    at e.keystrokeForKeyboardEvent (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:14:1087039)
    at KeymapManager.keystrokeForKeyboardEvent (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:11:1249633)
    at KeymapManager.handleKeyboardEvent (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:11:1247618)
    at WindowEventHandler.handleDocumentKeyEvent (C:/ProgramData/bruce.liu1/atom/app-1.41.0/resources/app/static/<embedded>:11:284598)

Commands
     -0:12.3.0 find-and-replace:show (input.hidden-input)

Non-Core Packages
compare-files 0.8.1
language-batch 0.4.0
language-powershell 5.0.0
pretty-json 2.0.3
xml-formatter 0.13.0

Thanks for taking the time to contribute!
We noticed that this is a duplicate of https://github.com/atom/atom/issues/21285. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


refactor(sidenav): export component

fixing export for Sidenav component

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.37.0 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


Fixture twins

@rodionovsasha this is the last part of the future - should update version in pom.xml?


feat: new timeout writer implementation

#1529 introduced timeout middleware, but it appears from working in the wild it has some race conditions that are not particularly helpful.
This PR rewrites the implementation to get rid of race conditions, at the expense of slightly higher RAM usage. It follows the implementation of http.TimeoutHandler closely.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

56 of 70 (80.0%)  changed or added relevant lines in 3 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.06%) to 65.689%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

internal/api/verify.go
10
11
90.91%

internal/api/middleware.go
45
58
77.59%

Files with Coverage Reduction
New Missed Lines
%

internal/api/verify.go
1
72.55%

internal/api/middleware.go
3
79.55%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
8397

Relevant Lines:
12783

💛  - Coveralls

@hf i've updated the branch with the following changes:

Verify email change shouldn't be calling http.Redirect twice
timeoutMiddleware doesn't have to be a struct method of API since we don't use any of the properties in it
Calling WriteHeader now takes a snapshot of the existing header map. When finallyWrite is called, we'll write the header from the snapshot rather than the header map.


Package not working with ssl api

I'm working well with localhost applications, but when i connect to https url i gave error like this.
Here is log.
I/flutter (13925): Starting HubConnection.
I/flutter (13925): Starting connection with transfer format 'TransferFormat.text'.
I/flutter (13925): Sending negotiation request: https://url:2600/notify/negotiate.
I/flutter (13925): Selecting transport 'HttpTransportType.serverSentEvents'.
I/flutter (13925): (SSE transport) Connecting.
I/flutter (13925): SSE connected to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw&access_token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJodHRwOi8vc2NoZW1hcy54bWxzb2FwLm9yZy93cy8yMDA1LzA1L2lkZW50aXR5L2NsYWltcy9zeXN0ZW0iOiIxZDMyZGUwYi02MzQ5LTQzNGYtZmMxZi0wOGRhMTNlZjc0NjUiLCJuYW1laWQiOiIzNmYwYjcyOC01NjA4LTQ3MGItYjQ1ZS0zMWI1YjY4YTA0MTUiLCJuYmYiOjE2NTI0NDgzMjgsImV4cCI6MTY1NTA0MDMyOCwiaWF0IjoxNjUyNDQ4MzI4fQ.1nsEoT33fdsV00Mrukq963YGwGsgM4xUtH6CHS1oPKw
I/flutter (13925): The HttpConnection connected successfully.
I/flutter (13925): Sending handshake request.
I/flutter (13925): (SSE transport) sending data. String data of length '32'.
I/flutter (13925): (SSE transport) request complete. Response status: 200.
I/flutter (13925): Using HubProtocol 'json'.
I/flutter (13925): HttpConnection.stopConnection(Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw) called while in state ConnectionState.connected.
I/flutter (13925): Connection disconnected with error 'Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw'.
I/flutter (13925): HubConnection.connectionClosed(Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw) called while in state HubConnectionState.connecting.
I/flutter (13925): Hub handshake failed with error 'Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw' during start(). Stopping HubConnection.
I/flutter (13925): Call to HttpConnection.stop(Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw) ignored because the connection is already in the disconnected state.
I/flutter (13925): HubConnection failed to start successfully because of error '{Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw.toString()}'.
E/flutter (13925): [ERROR:flutter/lib/ui/ui_dart_state.cc(209)] Unhandled Exception: Exception: Failed to connect to https://url:2600/notify?id=UvR4grgdVXNVH0cd4-Wqzw
E/flutter (13925):

Hi @hasanozkaynak26
Thanks for you report, I belive that this issue has been fixed in 1.3.2, please have a check.
So I am ging to clsose this issue, let me know if the issue is still available.
Regards


[WIP] Add dask-sql queries

This adds dask-sql versions of all of the gpu-bdb queries

Nope, no changes to cluster_startup.py or environmental configuration. However, if you're using dask>=2021.7.2 you need to change ucx_config = dask.config.get("ucx") to ucx_config = dask.config.get("distributed.comm.ucx") on line 176 of cluster_startup.py

@ChrisJar is this ready for another round of reviews?

@ChrisJar is this ready for another round of reviews?

Yep! This is ready for another round of reviews

@ChrisJar , Ready for another set of reviews ?

@randerzander , I think we also remove the blazing sql queries  and just keep the dask-sql ones to avoid confusion.

PR LGTM to me.


not creating new batch because there are already 4 in flight out of 4 allowed

Indy decided to limit the number to 4, see https://jira.hyperledger.org/browse/INDY-1863
Main reason to limit it was because of performance: A high number can lead for nodes to get out of order and falling out of consensus.
Reason:
All in all its a consensus problem because of the design decisions.
Position of the error:
https://github.com/hyperledger/indy-plenum/blob/f812a72197bc0740d4c6b75b796beff8f88c73f9/plenum/server/consensus/ordering_service.py
https://github.com/hyperledger/indy-plenum/blob/f812a72197bc0740d4c6b75b796beff8f88c73f9/plenum/test/replica/test_max_3pc_batches_in_flight.py
Todo:
Fixing consensus seems to be a heavy tasks. Changing the number in https://github.com/hyperledger/indy-plenum/blob/f812a72197bc0740d4c6b75b796beff8f88c73f9/plenum/config.py for test purpose should require a rebuild.
To specify if it is a critical bug, the nodes that are throwing the message have to validate how often it is thrown to evaluate if it can be categorized as a warning or a critical error.

@trustcerts Thanks for the issue! That is certainly a relevant issue, but not really related to building container images for indy node, is it? Did you accidentally open this issue in the wrong repo? ;) Given that you already found the right file to (quick) fix this, the issue might be better off in https://github.com/hyperledger/indy-plenum ? You could also ask at e.g. https://chat.hyperledger.org/channel/indy-node / https://chat.hyperledger.org/channel/indy-contributors for the best place

@Echsecutor we had this issue in one of the meetings so I thought placing it here helps everyone to track it. Since only some of our nodes are throwing this error we should collect more information about them to find a pattern before we can submit an issue in the official repos.

@trustcerts maybe we should open an Issue tracker /seperate github repo for AP6/the test network? For now I would recommend moving it to https://nextcloud.idunion.org/apps/deck/#/board/19 + reporting upstream