Use multisend instead of multiple send message

There is a MsgMultisend message type in Cosmos SDK. Sending to multiple addresses can be achieved by using a single message.
https://github.com/cosmos/cosmos-sdk/blob/e3aec18403bdef14118fbb97636c76ca9c951d74/proto/cosmos/bank/v1beta1/tx.proto#L34

A multi send message can be formatted in this way.
{
                "@type": "/cosmos.bank.v1beta1.MsgMultiSend",
                "inputs": [{
                    "address": "desmos177pzpz63y8x4p6k6day4qhk6qjqm7q7zevlx2z",
                    "coins": [{
                        "denom": "udsm",
                        "amount": "200000000"
                    }]
                }],
                "outputs": [
                    {
                        "address": "desmos1a7kkr92a55259hzacpdee4nhxurmyvwt7jnp5h",
                        "coins": [{
                            "denom": "udsm",
                            "amount": "100000000"
                        }]
                    },
                    {
                        "address": "desmos18tug2x5uwkgnh7qgadezvdntpwgjc88c98zuck",
                        "coins": [{
                            "denom": "udsm",
                            "amount": "100000000"
                        }]
                    }
                ]

            }

The amount of coins in inputs is always the same as the sum of coins in outputs.

Please add your planning poker estimate with ZenHub @calvinkei


Experiment profiles

Some issues/suggestions:

‘Run profile > stop’ will stop the experiment profile wherever its last leaving off (Ex. consider a profile that starts stirring at 400 RPM and stops after 1.5 mins. If stirring is active, and the profile is stopped early, it will keep stirring indefinitely)  — does this make sense for users? Would it be better to stop all jobs associated with the profile?

Starting a new profile with stirring and temp automation, while temp is already running. The profile successfully starts but the temp is skipped, and a yellow notif appears after the green success notification. The profile will successfully finish and not indicate that any actions couldn't be accomplished. Suggestion = to not allow a profile to begin unless all profile activities can succeed, or allow “starting” a profile to restart/reconfigure any active activities.

Experiment profile activities can be stopped via pioreactor > manage > stop on individual activities, but the profile will still appear to be running and will still “successfully execute”. However, when clicking “stop all activities”, the profile will “successfully” exit early and state ‘actions not completed’. These two “stop” actions should have the same result.

Bug = stirring is still running even after experiment profile has completed + success notification. Activities in the pioreactor menu show that stirring is not running. Starting+stopping stirring, and stopping all activities will not stop this stirring...

This is on the roadmap: https://github.com/Pioreactor/pioreactor/issues/440. I don't know if this should be the default or not though. I was thinking of a keyword in the top-level of the profile: stop_on_exit: bool that users can choose.

Bug = stirring is still running even after experiment profile has completed + success notification. Activities in the pioreactor menu show that stirring is not running. Starting+stopping stirring, and stopping all activities will not stop this stirring...

Can you provide detailed replication steps for this one?


Seeding re-stores chunks even if they are already stored

When you seed a file, it doesn't matter if the pieces are already on the store, it will create a ChunkStoreWriteStream and re-store them.
The verifying happens in Torrent._onMetadata, called on Torrent._onSwarnListening
The re-storing happens in Torrent.load, called in WebTorrent.seed
webtorrent:torrent got metadata +5ms
webtorrent:torrent verifying existing torrent data +3ms
webtorrent:torrent piece verified 0 +34ms
webtorrent:torrent piece verified 1 +1ms
webtorrent:torrent piece verified 2 +1ms
webtorrent:torrent done verifying +2ms
webtorrent:torrent on store +1ms
webtorrent:torrent select 0-2 (priority 0) +1ms
webtorrent:torrent file done: PMC-InformelaMuestra.pdf +3ms
webtorrent:torrent torrent done: 307f97a2e9264a5c17d04dd83aae6069d249a287 +1ms
bittorrent-tracker send `complete` +0ms
function onData(chunk) {
    if (self.destroyed) return
    store.put(index, chunk)
    index += 1
  }
put 0 from function (index, buf, cb) {
  console.info(arguments.callee.caller.toString())
  var self = this
  self.mem[index] = buf
  self.store.put(index, buf, function (err) {
    self.mem[index] = null
    if (cb) cb(err)
  })
}
function onData(chunk) {
    if (self.destroyed) return
    store.put(index, chunk)
    index += 1
  }
put 1 from function (index, buf, cb) {
  console.info(arguments.callee.caller.toString())
  var self = this
  self.mem[index] = buf
  self.store.put(index, buf, function (err) {
    self.mem[index] = null
    if (cb) cb(err)
  })
}
function onData(chunk) {
    if (self.destroyed) return
    store.put(index, chunk)
    index += 1
  }
put 2 from function (index, buf, cb) {
  console.info(arguments.callee.caller.toString())
  var self = this
  self.mem[index] = buf
  self.store.put(index, buf, function (err) {
    self.mem[index] = null
    if (cb) cb(err)
  })
}
webtorrent:torrent torrent done: 307f97a2e9264a5c17d04dd83aae6069d249a287 +54ms
bittorrent-tracker send `complete` +1ms

You're right. We can:

Eliminate verifying for all input types to client.seed, since it'll obviously be correct.

Eliminate the torrent.load (streaming into the store) when input is a filesystem path.


add instructions on how to run the notebooks in the IBM quantum lab

Hello @1ucian0, is this issue still open? I can work on this. Just to be sure, what all is required to be covered here? Is it just how to open notebooks in the IBM Quantum lab?

It is still open! Feel free to jump in.
The idea is to add a section on how to open the notebooks in IBM Quantum Lab to reduce the entry level for newcomers.


null initial date on Android

null initial date on android throw error: "Cannot read property 'getMonth' of null" from
https://github.com/facebook/react-native/blob/master/Libraries/Components/DatePickerAndroid/DatePickerAndroid.android.js#L22

Could you paste some code here?

Same error here :( @stereodenis have you find a solution ?

Same issue :/

same issue

same

If it helps, we ran into the same issue (but for endDate) and replacing null with undefined solved it for us.

Still getting this issue. Using undefined as per @rodrigoalmeidaee's suggestion doesn't work for me.


Add function to get hsl values

Hi @KittyGiraudel!
I have updated _functions.scss to add get-hsl-values function.

Some common use cases:
// _variables.scss
$theme: (
  primary: (
    300: hsl(199 100% 65%),
    base: hsl(199 100% 50%),
    500: hsl(199 100% 45%),
  ),
  secondary: (
    300: hsl(32 100% 65%),
    base: hsl(32 100% 50%),
    500: hsl(32 100% 45%),
  ),
  accent: (
    300: hsl(0 0% 35%),
    base: hsl(0 0% 24%),
    500: hsl(0 0% 16%),
  ),
);

// _root.scss
:root {

  // colors
  @each $type, $shades in $theme {
    @each $key, $value in $shades {
      --clr-#{$type}-#{$key}: #{$value};
      --clr-#{$type}-#{$key}-hsl: #{get-hsl-values($value)};
    }
  }

}

May you review and feedback me?

Hello. I’m sorry for being 2 years late on this — looks like it went through the cracks. While I appreciate the contribution, I’m not looking to grow that boilerplate as I no longer use it and can’t speak from authority anymore. I’ll therefore close this MR.


Remove double validation password

https://github.com/nsaladie/MP13-Hospital-BackEnd/blob/18f355a72803b65054011c85d04a765bd391be7a/src/main/java/com/example/Hospital/Hospital/NurseController.java#L39
if nurseRepository.findByNameAndPassword is already searching by name and password, check again password is not required in controller layer

With these changes, the double validation of the password is removed.
It validates that the database password and the user password are case-sensitive, this change is compatible with the Mysql database but may not be compatible with other databases.


Toggle ready for manufacture status based on drawing upload

check that a quantity is also provided

@morops status is now set to ready to manufacture when a drawing is uploaded and quantity is not ""
Unless other behavior is requested, we should close this issue


Expose slotted input feature on field components

Because of Shadow DOM limitations, our components such as vaadin-text-field do not work well with autocomplete and some password managers because the <input> element is not in the light DOM by default.
We have undocumented slotted <input> feature in vaadin-text-field but not in other components.
At the same time we have the following components that aren't well maintained:

vaadin-combo-box-light
vaadin-date-picker-light

Let's discuss if we should implement slotted <input> for all the components (and then get rid of these two components).
Related issues:

https://github.com/vaadin/vaadin-text-field/issues/67
https://github.com/vaadin/vaadin-form-layout/issues/74
https://github.com/vaadin/vaadin-text-field/issues/534

Also related to https://github.com/vaadin/vaadin-login/issues/96 since this effectively prevents you from placing Vaadin components into the Login component as custom content, sinice the username/password autocompletion will be disabled.

Another related issue is https://github.com/vaadin/vaadin-core/issues/238 (field wrapper component).

In our case, slotted input feature is highly useful to integrate with existing GUI form-building backend mini-apps. Advanced and very expensive to reimplement JS-based features like conditional logic, multi-page etc can stay compatible with much less work - if they  have input available for processing in light DOM.

In our case, slotted input feature is highly useful to integrate with existing GUI form-building backend mini-apps. Advanced and very expensive to reimplement JS-based features like conditional logic, multi-page etc can stay compatible with much less work - if they  have input available for processing in light DOM.

Prototype which we can use for inspiration: https://vaadin-form-prototype.glitch.me

@web-padawan Impressive work! Looks really promising!

Thanks! The prototype is actually created by @jouni


Updated redirects.

Updated redirects in .openpublishing.redirection.json.

Docs Build status updates of commit 44c793f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

#sign-off and merged.


yargs-parser are vulnerable to prototype pollution in version 3.4.1

Describe the bug
yargs-parser are vulnerable to prototype pollution in version 3.4.1
Expected behavior
should fix the security issue.
Actual behavior
yargs-parser are vulnerable to prototype pollution in version 3.4.1.

<EMAIL_ADDRESS>doesn't exist.

@ianschmitz I think this issue is referring to version 3.4.1 of react-scripts not yargs-parser.
<EMAIL_ADDRESS>D:\TelAnalytics\BigRed\Microsoft.FUN.BigRed.Website\ClientApp
--<EMAIL_ADDRESS> +--<EMAIL_ADDRESS> | --<EMAIL_ADDRESS>|   --<EMAIL_ADDRESS> |     --<EMAIL_ADDRESS>--<EMAIL_ADDRESS>   --<EMAIL_ADDRESS>`--<EMAIL_ADDRESS>

@ianschmitz I believe this issue is referring to react-scripts version 3.4.1 not yargs-parser.
--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>| --  --<EMAIL_ADDRESS>| --  --  --<EMAIL_ADDRESS>--<EMAIL_ADDRESS>--  --<EMAIL_ADDRESS>--  --  --<EMAIL_ADDRESS>

Why was this issue closed if the issue has not been fixed?  react-scripts 3.4.1 is still vulnerable and will cause an npm audit to return non-zero:
Low Prototype Pollution

Package yargs-parser

Patched in >=13.1.2 <14.0.0 || >=15.0.1 <16.0.0 || >=18.1.2

Dependency of react-scripts [dev]

Path react-scripts > webpack-dev-server > yargs > yargs-parser

More info https://npmjs.com/advisories/1500

this has been resolved on master but not yet released: https://github.com/facebook/create-react-app/pull/8975

Any sense of when that release will be?


ts file configuration in webpack.config.js

Unless there is something I'm missing, in order for the webpack build process to work with .ts files as well as .js files (as is currently the case) then the 'doTypeCheck': false query option is required for the .ts entry.
So, for files with the 'ts' ending to compile with ionic serve the webpack.config.js file config element;
  {
    test: /\.ts$/,
    loader: "awesome-typescript",
    include: [path.join(__dirname, 'www')],
    exclude: /node_modules/
  }

should actually be:
  {
    test: /\.ts$/,
    loader: "awesome-typescript",
    query: {
      'doTypeCheck': false
    },
    include: [path.join(__dirname, 'www')],
    exclude: /node_modules/
  }

Hey this is a good workaround for the moment, but the real issue I believe is that ionic serve should still build even when it encounters type errors.  If you have webpack installed and run webpack it will emit type errors but still build.
I've opened an issue for this: https://github.com/driftyco/ionic2/issues/646, so I'm going to close this and track it there.


Add Auth0 For Authentication

https://github.com/auth0/nextjs-auth0
Heroku provides Auth0 as an addon, and I've always wanted to try out using it for SSO and user management. No users will exist in the database attached to giving-frontend, but rather they will exist in Auth0. Each application sends users to Auth0 for logging in, and each consumer then stores session info in its database with role of the user in that application.
Some unique ID, like email, can be used to fingerprint users...I don't think putting permission logic in Auth0 makes sense, but only that a user exists for the application. It would be great to invite people via email so that the user roles are set in the consumer app's db before the user logs in.
To start, just emails can be used, but GitHub auth would be a good social login provider...and then eventually SAML with CU.

So I found out that adding "enterprise" connections to an app vs. something like Google or Facebook auth ends up costing around $525 per month. Salesforce social auth is an option and combined with IP restrictions, I think it can get really close to what the regular SSO login flows gives you back: whether or not a user works at the university or not.
I'm keeping permissions and roles within the application layer instead of Auth0 globally so that end-user can assign permissions if needed. There is no way to add "internal users" to the Auth0 admin UI via Heroku, but you can add an "external user" to your app and then do what you want with permissions.
I think I will hard-code the emails of the super users, who will bypass permissions and invite initial users to the site, but from then on roles will be managed by "site owners" who invite users based on CU email addresses to certain roles. Once the user logs in for the first time, they are granted the role if Auth0 lets them pass. We used this system on Web Express and it worked well.

I'm not sure what the issue is on the review app, but I need to merge this in so that I can use it for working with users in a database.


Add support for Note-style comments.

J supports multi-line comments with the Note verb. They can look like this:
Note 'a string argument'
some comments followed by a closing right paren by itself:
)

or this:
 Note 'with whitespace before is okay'
)

or this:
myVar =: 42 Note 'this is a single-line comment'

This pull request supports all three varieties. I removed Note in line 29, because if it matches as a keyword then the first case (the one without preceding whitespaces) does not register as a comment.

Thank you for this.
I'm not sure we should treat Note the same as a comment, since it is not a comment defined in the language, just an ordinary stdlib verb.
   digits=: i. 10  NB. 0, 1, 2...
   digits=: i. 10  Note 0, 1, 2...
|ill-formed number

I do think it would make sense to highlight the body of monadic Note like explicit noun definition (noun define and variants).
You can highlight explicit noun definitions like comments by putting highlight link jNounDefine Comment in your vimrc.

I do think it would make sense to highlight the body of monadic Note like explicit noun definition (noun define and variants).

Sounds good to me. The result would look like below:
Note 'a note'
Only the text on this line is highlighted as an explicit noun definition.
)

Yeah, that's what I had in mind.
I can look into it this weekend. In case you want to work on this yourself, please only request pulls to develop. Stuff goes in master only once it's made it into upstream Vim.


Volume exercise

Possible to do ops in mem, then backup?
Context to switch to mem, then record back to file. How make safe?

Done.


Washington DC mini maps rendering isn't pretty

Minimaps on the Washington DC Community Maps page have a rendering issue, see screenshot below:

This is almost certainly due to the simplification we're doing with turf before returning this GeoJSON
https://github.com/PublicMapping/districtbuilder/blob/d3138c49316a1545985125f5d76fd34f94fdec21/src/server/src/projects/services/projects.service.ts#L73
DC is quite small compared to most states - I wonder if we need to vary the tolerance we use based on a per-region configuration (or maybe dynamically chosen based on region size?)


Fix issue when bedrock_autoloader option

This fixes an issue where the bedrock_autoloader option is set but the number of plugins differs. I ran into this issue when moving a plugin from plugin to mu-plugin and deploying to a remote server.
I haven't been able to recreate this in a reliable way but having ran into this issue a couple of times on different servers I figured I'd propose my fix.
Basically $cache will not evaluate to false because it will be set to an array looking like this:
array(
'plugins' => array(),
'count' => 0,
);

This fixed it for me.
I created the issue in the wrong project. And instead of spamming new issue here you can read my original issue on the Trellis-project https://github.com/roots/trellis/issues/1022.
If you want me to open issue here anyway I can do it.

This seems to make sense. We'll have to try it out first.


[ISSUE-510] Fix componentWillReceiveProps deprecation warning

Any plan to use the new getDerivedStateFromProps API instead of prefixing the deprecated lifecycle hook with UNSAFE?

@giamir
Seems this https://github.com/nosir/cleave.js/pull/527 fixed the issue so that we no longer need this fix.  thoughts?

@cht8687 True; #527 is still open at the moment.

thanks @jonathanconway
hey @giamir , we've merged #527 and I think we can close this now. We will release a new version soon.

Awesome @cht8687 . Thanks for your help.


[Bug] MapImage() crashes when using an image buffer

I am encountering a weird ?bug?.
I used xxd to convert my Dll to a C-Style header which I include in the injector.
When trying to manual map the image into the target process, the injector crashes with error 0xC0000005: Access Violation.
I managed to locate where it crashes:
void PEImage::Release( bool temporary /*= false*/ )
{
    if (_pFileBase)
    {
        UnmapViewOfFile( _pFileBase ); // <-- crashes here
        _pFileBase = nullptr;
    }
[...]
}

Call Tree:
> Launcher.exe!blackbone::pe::PEImage::Release(bool temporary) Line 118
> Launcher.exe!blackbone::pe::PEImage::~PEImage() Line 26
> Launcher.exe!blackbone::PatternLoader::DoSearch() Line 144
> Launcher.exe!blackbone::InitOnce::Exec() Line 39
> [Inline Frame] Launcher.exe!blackbone::InitializeOnce() Line 133
> [Inline Frame] Launcher.exe!blackbone::DynImport::get(const std::basic_string<char,std::char_traits<char>,std::allocator<char> > &) Line 33
> Launcher.exe!blackbone::Utils::GetExeDirectory() Line 125
> Launcher.exe!main() Line 89
> [External Code]     Annotated Frame

Now the weird part.
When I inject the same Dll, but instead of using the bin header, I use CreateFile() like in the MMapTest.cpp it doesn't crash.

How do you call it in the Launcher.exe!main ?

I call it like this:
auto image = proc.mmap().MapImage(dll_size, (void*) const_cast<unsigned char*>(dll_data), false, flags, nullptr, nullptr, &cArgs);


Make compatible with tamato-taric-import

The TAMATO TARIC importer script has a dependency on TAMATO's serializers and models to
validate and modify the TAMATO DB.
This change adds a setup.py to allow TAMATO to be added as a pip dependency
It also adds preliminary serializers for Commodity and Measure models, to allow the
importer to deserialize these models.
Finally, the ValiditySerializerMixin is modified to handle TARIC date format strings
(YYYY-MM-DD) as well as ISO 8601 format (the default), for convenience.

Codecov Report

Merging #32 into master will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #32      +/-   ##
==========================================
+ Coverage   77.88%   77.91%   +0.03%
==========================================
  Files          45       45
  Lines        1343     1345       +2
  Branches       50       50
==========================================
+ Hits         1046     1048       +2
  Misses        285      285
  Partials       12       12

Impacted Files
Coverage Δ

common/serializers.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Usage of property initializer syntax throws no-invalid-this eslint error

When I use "property initializer syntax" to define my event handlers per the React docs (https://facebook.github.io/react/docs/handling-events.html) and do a this.setState inside the handle, I get eslint throwing a no-invalid-this error.
I don't think this is a bug in create-react-app, but perhaps something that has not been worked into babel-eslint or eslint-plugin-babel (See: https://github.com/babel/babel-eslint/issues/401#issuecomment-253099182)
Has a workaround to this be found?

The following works for me:
import React, { Component } from 'react';
import logo from './logo.svg';
import './App.css';

class App extends Component {
  click = () => {
    console.log('yas')
  }

  render() {
    return (

Welcome to React

          To get started, edit src/App.js and save to reload.

    );
  }
}

export default App;

Please downgrade to npm@4, remove your node_modules (and package-lock.json), and run npm install.

@Timer Could you give me some color on why the need to downgrade to npm4? We are trying to make use of the lockfile capabilities of npm 5 and I'd hate to have the solution require us to lose that feature of npm

@Timer Also, in your example, I see that you are using the property initializer syntax, but unlike my original post, you are not trying to use this in the lambda assigned to the property

Using this also works for me, and it's because npm 5 is extremely buggy and should not be used in production yet.
Use Yarn if you'd like a stable lock file!

I'll close this as an npm 5 bug installing incorrect dependencies. Please report this bug there. :)


agent/exec: remove use of gomock.

Signed-off-by: Alexander Midlash<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_gomock" git@github.com:Syntaxide/swarmkit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354273672
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

@Syntaxide: There appears to be an extra commit in this PR related to #2054. Perhaps it's a rebase artifact?  You might want to wait for some code review before addressing those nits, but just keep in mind that they will have to be addressed at some point.
ping @stevvooe for review of the test changes

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "remove_gomock" git@github.com:Syntaxide/swarmkit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353192400
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Ok, so going through the cases, I think we are mostly good.
I know I had indicated that call counting was bad, but there still needs to be something ensure that an expected method was called. You can reintroduce call counting or just flip some closed over bool for the cases where it makes sense.
With that fix, we can probably go forward!
Thanks for this contribution! This was a massive pain point!

Thanks. I've re-added the counts, and added the necessary comments to satisfy golint.

LGTM

LGTM
@Syntaxide: Can you please squash the commits before this is merged?

Just squashed.


Community forum?

Even a simple #gauge channel on Freenode would be nice.

We have a "Talk to us" page  :)
tl;dr: reach us at getgauge[at]googlegroups.com (it is quiet at the moment, but we are watching it)


unable to preview variables in stats component

reproduce:

create a new variable
change mantissa to 1

can't reproduce, maybe it's been fixed already


I changed the UDF to import from AbstractUDFClass


added support for bfloat16 datatype to be used for Intel Xeon processors

This PR enables Whisper with bfloat16 inference capabilities on Intel hardware. The Intel AMX instructions are designed to accelerate deep learning operations such as matrix multiplication and convolutions that use bfloat16. AMX is supported by 4th Gen Xeon Scalable Processors codenamed Sapphire Rapids.
More details can be found here
Using bfloat16 inference with PyTorch needs:
Intel® Extension for PyTorch*
Installation instructions
Successfully tested on Intel 4th Gen Xeon

Hi @jongwook
May I get an estimate on the review for this PR?
or if there's a process to be followed? Thank you

Hi, I think it wouldn't hurt, but I don't have access to Xeon hardware to test this. For other platforms, it wouldn't make much sense to compute in BF16 because the model weights are distributed in fp16, and casting to bf16 would just lose some precision, although it's probably okay.
Do you have a performance comparison between fp32 and bf16 inference speeds on Sapphire Rapids?

@devpramod-intel , it looks that PR is missing proper handling of DecodeOptions in transcribe() method:
https://github.com/openai/whisper/blob/main/whisper/transcribe.py#L109-L118


Hotfix - Apply saved search params to query string

@alecritson it appears to remember it now. However, when I unselect the saved search, it doesn't go back to showing all products? This may be a separate issue.
E.g.

@alecritson it appears to remember it now. However, when I unselect the saved search, it doesn't go back to showing all products? This may be a separate issue.
E.g.

Works okay for me 🤔 can't seem to reproduce.


fix functioanlization tests

Fixes #799
The fix is a change in core, but I tested that the tests pass locally with  https://github.com/pytorch/pytorch/pull/77358. I'll wait til that PR lands before merging this one.

LGTM (once the PR lands and nightly updates)! We should see the failure in the nightly build and then can merge
Thanks for the fast fix on this!

Looks like the xfails are failing on lated CI - merging this (https://app.circleci.com/pipelines/github/pytorch/functorch/2817/workflows/63087caa-e0e2-411d-936f-c28b9a53229b/jobs/19067/tests#failed-test-0)


O1 is the default in the help message

fix #463
I am sorry I forgot to change that

I am sorry I forgot to change that

It's ok, things like this happen to everyone all the time :)


Fix dockercross build error "docker: invalid reference format" when user or group contains spaces

References: https://github.com/dockcross/dockcross/pull/265

The Travis build failure will be fixed by #373.

Merged. Thanks


Split examples into scripts & notebooks subfolders

The number of example scripts/notebooks increased quite a lot already and will probably increase further in the future. FI was wondering if it might be a clearer structure if we split the examples folder into a scripts and a notebooks subfolder. Furthermore, it happened to me several times that I clicked on a notebook when I wanted to open a script and vise versa.
The new structure could look like this:
├── ...
├── examples
│   ├── notebooks
│   │   └── *.ipynb files
│   ├── scripts
│   │   └── *.py files
│   └── ruff.toml
└── ...

Or we could leave the scripts in the examples folder and only move the *.ipynb files into a notebooks subfolder:
├── ...
├── examples
│   ├── notebooks
│   │   └── *.ipynb files
│   ├── *.py files
│   └── ruff.toml
└── ...

Any opinions?

+1 to splitting,
I think I would slightly prefer option .

+1 to splitting, I think I would slightly prefer option .

Maybe it's just me, but I don't really understand which option you prefer 😨

Not sure how that happened.😅
Separate notebooks and scripts folder in examples.

Should I do it in https://github.com/PTB-MR/mrpro/pull/537 then?


Come up with Tag Names we need

Let's use this issue as a container for all the label names we think we need, we can also categorize them (later or as we go) like @jessicalins proposed here also including here what @ihucos proposed here
Labels for pull requests can be capitalized as @JanNash suggested here
Product Related Labels

feature
bug

Technical Labels

refactoring
performance

Non Coding Labels

examine/investigation/inspection/planning
discussion

Workflow Labels

Needs Backend Review
Needs Frontend Review
Needs Product Review
Backend 👍
Frontend 👍
Product 👍
Backend 👎
Frontend 👎
Product 👎

This is a list of the current tags we use in the resmio app repo:
** More than 10 uses **

admin
analytics
Backend refactoring
Backend
blocked
bookings
bug
Code reviewed
crm
duplicate
easy pickings
emails
enhancement
feedback
Frontend Refactoring
Frontend
help wanted
in progress
invalid
ipad
large
medium
mockup needed
newsletters
on Test
PO Approved
Project X
proposal
question
ready for QA
ready
requirements needed
search
small
sprint ready
tests needed
ticketing
widget
wontfix
x-large
x-small

** Less than 10 uses **

0 - Backlog
1 - Ready
2 - Working
3 - Done
button
dashboard
hollow-butter
proof of concept
search

Product Related Labels

feature
bug
and
enhancement
proposal
emails

What do you think?

Sorry, can you explain the difference between feature, and proposal?
Don't you think emails is more a 'subject' label?


[SPARK-35328][Core] Use 'SPARK_DRIVER_LOG_URL_' as env prefix for getting driver log urls by default

What changes were proposed in this pull request?
Currently, spark on kubernetes can't show logs url on ui. To check history logs, we usually collect pod logs to third-party logging services, which can be accessed by urls. To show log urls on ui,  we can set env prefixed with 'SPARK_LOG_URL_' for executors. But for driver, there is no way to show log urls by setting env.
This pr use 'SPARK_DRIVER_LOG_URL_' as env prefix for getting driver log urls by default.
Why are the changes needed?
To show driver log urls on ui by setting env prefixed with 'SPARK_DRIVER_LOG_URL_'.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A

Can one of the admins verify this patch?

@sharkdtu do you mind:

Keep the github PR template: https://github.com/apache/spark/blob/master/.github/PULL_REQUEST_TEMPLATE
Fix the test failure: https://github.com/sharkdtu/spark/runs/2518937303?check_suite_focus=true

@HyukjinKwon Thanks, PR description has been updated and the test failure has been fixed.

@HyukjinKwon Could you review this pr, and merge it if it is ok. Thanks a lot.

Does anyone follow up on this pr? It's quite useful for spark on k8s.

I'm working on https://github.com/apache/spark/pull/38357, it covers this functionality.


[Fix] convert the source code of client app to MVVM format

Describe the Issue
rewrite the whole client lib folder by following the MVVM design pattern.
you can refer to the example given in this repository
https://github.com/flutter-devs/flutter_mvvm_demo/blob/master/lib/view models/movie_list_view_model.dart

I am interested to work on this issue. Do assign me , if it is still open .

Yes it's open. Go for it.

Just leave a confirmation, so that I can assign it to you

Yes it's open. Go for it.
Just leave a confirmation, so that I can assign it to you

Yes I am ready to work on it

Can i work on this issue

This project is not actively maintained. @ramanjitsingh-hub


Logstash is not sending data to elasticsearch

Problem description
Logstash is not sending data to elasticsearch, but showing up received logs on console through
docker service logs -f elk_logstash
Extra information
No error message on service logs
Stack configuration

deployed docker stack using docker-stack.yml
Using all default setup, only changed logstash url from 5000 to 5044

Docker setup
Docker version 18.09.0, build 4d60db4

logstash logs
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:12:57,184][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:12:57,194][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:12:57,630][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"6.5.1"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:12:57,663][INFO ][logstash.agent           ] No persistent UUID file found. Generating new UUID {:uuid=>"9b842324-da08-48e1-a6c5-a934bd8e1a95", :path=>"/usr/share/logstash/data/uuid"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:00,583][INFO ][logstash.pipeline        ] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:00,927][INFO ][logstash.inputs.beats    ] Beats inputs: Starting input listener {:address=>"<IP_ADDRESS>:5044"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:00,948][INFO ][logstash.pipeline        ] Pipeline started successfully {:pipeline_id=>"main", :thread=>"#<Thread:0x1d8bdb1c run>"}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:01,008][INFO ][logstash.agent           ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:01,082][INFO ][org.logstash.beats.Server] Starting server on port: 5044
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | [2019-01-05T16:13:01,303][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |           "tags" => [
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         [0] "beats_input_codec_plain_applied"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     ],
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |           "meta" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "cloud" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                  "machine_type" => "t2.large",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                      "provider" => "ec2",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                   "instance_id" => "i-04a68a9e4c7f12eb0",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                        "region" => "eu-central-1",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |             "availability_zone" => "eu-central-1b"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         }
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     },
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |           "beat" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |          "version" => "6.5.4",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |             "name" => "ip-172-31-46-80",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "hostname" => "ip-172-31-46-80"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     },
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |       "@version" => "1",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |          "input" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "type" => "log"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     },
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |        "message" => "Test log4",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "offset" => 30,
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     "@timestamp" => 2019-01-05T16:13:24.234Z,
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |           "host" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                  "name" => "ip-172-31-46-80",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |          "architecture" => "x86_64",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                    "os" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |             "codename" => "bionic",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |              "version" => "18.04.1 LTS (Bionic Beaver)",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |               "family" => "debian",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |             "platform" => "ubuntu"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         },
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "containerized" => false,
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |                    "id" => "c68aecfbda9841da86c7071546fef3e6"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     },
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "source" => "/home/ubuntu/logs/test.log",
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     "prospector" => {
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |         "type" => "log"
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    |     }
elk_logstash.1.ti7wpoz958d0@ip-172-31-35-206    | }

elasticsearch logs
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,409][WARN ][o.e.c.l.LogConfigurator  ] [unknown] Some logging configurations have %marker but don't have %node_name. We will automatically add %node_name to the pattern to ease the migration for users who customize log4j2.properties but will stop this behavior in 7.0. You should manually replace `%node_name` with `[%node_name]%marker ` in these locations:
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    |   /usr/share/elasticsearch/config/log4j2.properties
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,860][INFO ][o.e.e.NodeEnvironment    ] [2YL0Ce4] using [1] data paths, mounts [[/ (overlay)]], net usable_space [669.3mb], net total_space [7.6gb], types [overlay]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,860][INFO ][o.e.e.NodeEnvironment    ] [2YL0Ce4] heap size [990.7mb], compressed ordinary object pointers [true]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,861][INFO ][o.e.n.Node               ] [2YL0Ce4] node name derived from node ID [2YL0Ce4YRgOVw6FDHOOy8A]; set [node.name] to override
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,862][INFO ][o.e.n.Node               ] [2YL0Ce4] version[6.5.1], pid[1], build[oss/tar/8c58350/2018-11-16T02:22:42.182257Z], OS[Linux/4.15.0-1031-aws/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:37,862][INFO ][o.e.n.Node               ] [2YL0Ce4] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.v3KnDFEo, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.locale.providers=COMPAT, -XX:UseAVX=2, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.flavor=oss, -Des.distribution.type=tar]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [aggs-matrix-stats]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [analysis-common]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [ingest-common]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [lang-expression]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [lang-mustache]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [lang-painless]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [mapper-extras]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,902][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [parent-join]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,903][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [percolator]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,903][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [rank-eval]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,903][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [reindex]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,903][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [repository-url]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,903][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [transport-netty4]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,904][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded module [tribe]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,904][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded plugin [ingest-geoip]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:38,904][INFO ][o.e.p.PluginsService     ] [2YL0Ce4] loaded plugin [ingest-user-agent]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:42,387][INFO ][o.e.d.DiscoveryModule    ] [2YL0Ce4] using discovery type [single-node] and host providers [settings]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,114][INFO ][o.e.n.Node               ] [2YL0Ce4] initialized
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,114][INFO ][o.e.n.Node               ] [2YL0Ce4] starting ...
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,435][INFO ][o.e.t.TransportService   ] [2YL0Ce4] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,583][INFO ][o.e.h.n.Netty4HttpServerTransport] [2YL0Ce4] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,583][INFO ][o.e.n.Node               ] [2YL0Ce4] started
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:43,671][INFO ][o.e.g.GatewayService     ] [2YL0Ce4] recovered [0] indices into cluster_state
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:45,886][INFO ][o.e.c.m.MetaDataCreateIndexService] [2YL0Ce4] [.kibana_1] creating index, cause [api], templates [], shards [1]/[1], mappings [doc]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:45,908][INFO ][o.e.c.r.a.AllocationService] [2YL0Ce4] updating number_of_replicas to [0] for indices [.kibana_1]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:12:46,359][INFO ][o.e.c.r.a.AllocationService] [2YL0Ce4] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.kibana_1][0]] ...]).
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:13:13,554][WARN ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] high disk watermark [90%] exceeded on [2YL0Ce4YRgOVw6FDHOOy8A][2YL0Ce4][/usr/share/elasticsearch/data/nodes/0] free: 666.7mb[8.4%], shards will be relocated away from this node
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:13:13,555][INFO ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] rerouting shards: [high disk watermark exceeded on one or more nodes]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:13:43,558][WARN ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] high disk watermark [90%] exceeded on [2YL0Ce4YRgOVw6FDHOOy8A][2YL0Ce4][/usr/share/elasticsearch/data/nodes/0] free: 666.7mb[8.4%], shards will be relocated away from this node
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:14:13,560][WARN ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] high disk watermark [90%] exceeded on [2YL0Ce4YRgOVw6FDHOOy8A][2YL0Ce4][/usr/share/elasticsearch/data/nodes/0] free: 666.6mb[8.4%], shards will be relocated away from this node
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:14:13,560][INFO ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] rerouting shards: [high disk watermark exceeded on one or more nodes]
elk_elasticsearch.1.ekb4hwzhei3p@ip-172-31-35-206    | [2019-01-05T16:14:43,561][WARN ][o.e.c.r.a.DiskThresholdMonitor] [2YL0Ce4] high disk watermark [90%] exceeded on [2YL0Ce4YRgOVw6FDHOOy8A][2YL0Ce4][/usr/share/elasticsearch/data/nodes/0] free: 666.6mb[8.4%], shards will be relocated away from this node
e

The logs of the automated tests show that sending the "docker-elk" string to Logstash created the expected document in Elasticsearch: https://travis-ci.org/deviantony/docker-elk/jobs/471611895#L479
Could you provide more details about your setup and workflow?
Please also note that docker-stack.yaml should only be used with Swarm.

Same problem here:
input {
  beats {
    port => 5044
  }
}

output {
  elasticsearch {
    hosts  => ["https://kibana.fidesol.org:9201"]
    index => "%{[<EMAIL_ADDRESS>    user => "logstash_internal"
    password => "xxx"
    #user => "elastic"
    #password => "changeme"
  }
}

user has manage index_templates and monitor privileges on the cluster...
logstash print the filebeat input in stdout, but no send to elasticsearch. And no erros appears in stout log filebeat. (I also run all in docker)
¿How you fix it?

@Nitrosito that's not enough. You need a user that can create indexes (the logstash-* rolling index) and write to these indexes.

With user "elastic" with al privileges dont work too...
No erros in container logs, elastic, logstash log... same as @subhadippramanik
Logstash log container:
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | WARNING: An illegal reflective access operation has occurred
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | WARNING: Illegal reflective access by com.headius.backport9.modules.Modules (file:/usr/share/logstash/logstash-core/lib/jars/jruby-complete-<IP_ADDRESS>.jar) to field java.io.FileDescriptor.fd
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | WARNING: Please consider reporting this to the maintainers of com.headius.backport9.modules.Modules
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | WARNING: All illegal access operations will be denied in a future release
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | Thread.exclusive is deprecated, use Thread::Mutex
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | Sending Logstash logs to /usr/share/logstash/logs which is now configured via log4j2.properties
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:06:54,895][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.queue", :path=>"/usr/share/logstash/data/queue"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:06:54,961][INFO ][logstash.setting.writabledirectory] Creating directory {:setting=>"path.dead_letter_queue", :path=>"/usr/share/logstash/data/dead_letter_queue"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:06:56,298][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"7.2.0"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:06:56,370][INFO ][logstash.agent           ] No persistent UUID file found. Generating new UUID {:uuid=>"cb670e63-bf0f-4faa-a8f0-46567e404701", :path=>"/usr/share/logstash/data/uuid"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:02,395][WARN ][org.logstash.instrument.metrics.gauge.LazyDelegatingGauge] A gauge metric of an unknown type (org.jruby.RubyArray) has been create for key: cluster_uuids. This may result in invalid serialization.  It is recommended to log an issue to the responsible developer/development team.
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:02,416][INFO ][logstash.javapipeline    ] Starting pipeline {:pipeline_id=>"main", "pipeline.workers"=>8, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>50, "pipeline.max_inflight"=>1000, :thread=>"#<Thread:0xf39d08e run>"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:04,195][INFO ][logstash.inputs.beats    ] Beats inputs: Starting input listener {:address=>"<IP_ADDRESS>:5044"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:04,242][INFO ][logstash.javapipeline    ] Pipeline started {"pipeline.id"=>"main"}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:04,515][INFO ][logstash.agent           ] Pipelines running {:count=>1, :running_pipelines=>[:main], :non_running_pipelines=>[]}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:04,569][INFO ][org.logstash.beats.Server] Starting server on port: 5044
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | [2019-06-26T09:07:05,737][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/awesome_print-1.7.0/lib/awesome_print/formatters/base_formatter.rb:31: warning: constant ::Fixnum is deprecated
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |          "input" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         "type" => "log"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     },
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |          "agent" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |             "hostname" => "SBF20",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         "ephemeral_id" => "276117c4-e382-47d6-994b-33f693009579",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |              "version" => "7.2.0",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |                 "type" => "filebeat",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |                   "id" => "7f3eee11-b7d8-4a63-8690-cdc1b9bddc88"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     },
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     "@timestamp" => 2019-06-26T09:07:12.426Z,
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |           "tags" => [
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         [0] "beats_input_codec_plain_applied"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     ],
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |            "log" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |           "file" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |             "path" => "/home/xxx/example.log"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         },
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         "offset" => 8
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     },
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |        "message" => "meh2446",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |       "@version" => "1",
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |           "host" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         "name" => "xxx"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     },
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |            "ecs" => {
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |         "version" => "1.0.0"
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    |     }
ElasticStack_logstash.1.ismc1mg1dyxn@skynet    | }

if I change the port to another in the log it does not reflect the change, it keeps pointing to the old one after the restart. It is clear that I do not take the file config. I will investigate, thank you

My error is than i put configuration files (.conf) in usr/share/logstash/config/
And the correct place is usr/share/logstash/pipeline
Is ok? Now works in pipeline directory


Can I Fetch data from classic OPC Server?

Dear Sir,
I want to fetch data from classic OPC Server.
Can it possible by ProcessControlStandards.OPC?
Thanks,

Dear Sir,
I am able to show OPC DA simulator but how can i fetch live variable from OPC DA server ?


Cleaned up element tests

Hi
A bit of a cleanup of the element tests:

move globals to class
remove unused function
re-structured fixtures to ensure idempotency

Cheers
Alex
https://github.com/cubewise-code/tm1py/issues/301

Nice one. Thanks


Add real videos

Adds to @pwalczysko #372.
Uses a <video> tag with poster for placeholder.
NB: When we add a video, we now need to add a placeholder image and set the vid_poster1 to point to it in order for the video to show up on the page.
See https://snoopycrimecop.github.io/www.openmicroscopy.org/events/ome-community-meeting-2020/day1/ and day2

Looks good to me on https://snoopycrimecop.github.io/www.openmicroscopy.org/events/ome-community-meeting-2020/day2/ . See what @jrswedlow thinks, thanks @will-moore

One thought - do we want the videos to play in-line when they are so small? Maybe they should just be links to the full-sized video?

One thought - do we want the videos to play in-line when they are so small? Maybe they should just be links to the full-sized video?

But you can maximize your screen once the play starts. See what @jrswedlow thinks.

Ideally people could watch it in a window without going full screen so they can still see their other applications

Practice talks are removed, as verified via snoopy.
@jrswedlow okayed this, merging for release.


Suppress multiple welcome emails on zulipchat.com for same email address

It's kinda annoying that as you sign up for multiple organizations on zulipchat.com, you get multiple copies of the welcome emails and hotspots (Etc.).  I think what we can do here is modify the enqueue_welcome_emails logic to have a conditional for users whose email already has an account.
I don't think we can just send 0 emails, but I think a good model would be this:

If your email address already has an account on the server, we don't do hotspots for you.
We also don't send a day2 follow-up email to these users
We modify the text of the followup day1 email to mostly just congratulate them on their new Zulip organization, and prominently advertise the "organization URL" they should use to login in the apps.

From discussion at https://chat.zulip.org/#narrow/stream/9-issues/subject/multiple.20welcome.20mails/near/569385.

@zulipbot claim

Is this superseded by the "import profile" idea?

"import profile" is ~complete and handles hotspots but I think not this; @hackerkid is that correct?  If so, can you do a PR with a first commit to suppress at least the day2 welcome email for users imported this way?  The second commit (to change the day1 email) would need a bit more thought from @rishig on the email's content... @rishig do you think we can make this work by just having the day1 email have an extra conditional, rather than ~rewriting it?

Yup. I have a PR already for this. Will make some changes and update it tomorrow :)

Can we just suppress day1 email as well? It's not that important for them to get their org_URL from the email.

@rishig for security/ToS model reasons, I think it's important to send a confirmation email when someone signs up for a new account (if they're doing Google auth, there may have been no email transaction), so I think we do want to send an email.  And I think it is valuable to have an email with the organization URL, because if they are on a new computer and forget how their organization URL is spelled, searching one's email is probably a reasonable way to do that.

I am wondering if there are still things to do for this issue?
The first point should be solved by this PR which came out of this discussion.

I am wondering if there are still things to do for this issue?
The first point should be solved by this PR which came out of this discussion.

@mrchntia I think I have created a PR in the past that took care of 2 and 3 as well. Can you verify if this is the case by testing in dev environment?

@mrchntia I think I have created a PR in the past that took care of 2 and 3 as well. Can you verify if this is the case by testing in dev environment?

https://github.com/zulip/zulip/commit/ba640bf89d7f08ed29e894294e8a10c848dea18c is the commit for 2.

https://github.com/zulip/zulip/commit/ba640bf89d7f08ed29e894294e8a10c848dea18c is the commit for 2.

2 is solved, but 3 doesn't seem to be solved. I got the same day1 followup email when I signed up the same user in a second organization.

2 is solved, but 3 doesn't seem to be solved. I got the same day1 followup email when I signed up the same user in a second organization.

Sould we ideally drop the following lines and leave the rest as it is?
(you'll need these to sign in to the mobile and desktop apps)
Learn more about Zulip, become a pro with a few keyboard shortcuts, or dive right in!

Sould we ideally drop the following lines and leave the rest as it is?
(you'll need these to sign in to the mobile and desktop apps)
Learn more about Zulip, become a pro with a few keyboard shortcuts, or dive right in!

@mrchntia Yup. We can start with that and make more changes if required by Tim.

@mrchntia Yup. We can start with that and make more changes if required by Tim.

Great. I started working on it.

Great. I started working on it.

Closing this as resolved, see the comment on #17081 for details.

Closing this as resolved, see the comment on #17081 for details.


Troubleshooting docs: osx scrypt

Just a small addition to the troubleshooting docs.
See also #205

Coverage remained the same at 70.122% when pulling 77e8aabc7a61d25cc7ee643bf669278e5980d18b on docs-troubleshooting into 7adb87df602b063108a02c7650b1ea0584568406 on development.


bower.json contains gulpfile.js as "main"

This causes the wiredep to install gulpfile.js into the page, instead of the real "main" file. Should probably be dist/no-frameworks/n17-password-strength.js

Thanks for the heads up, will get this changed and pushed for you

Resolved in v1.0.5


Filter Regions within Assignment

Having a filter to single region feature similar to Segmentor, especially when working on multiple nuclei within a single assignment

Implemented


Less intrusive handling of riak.conf and advanced.config

Currently, we always set a config file for the cluster, using a default file that isn't favourable for TS. This requires operators to always set a cluster config file for TS clusters.
Let's use the config that comes with Riak by default and simply override the things we MUST control (e.g. http port etc) where necessary. Obviously we still provide the mechanism for an operator to set their own config file.

Let's not forget to

[ ] update the README.md with the new instructions


rez-depends -- 'ProgressBar' object is not an iterator (py-3, rez-2.47.4)

platform: windows
rez: 2.47.4
rez-python: 3.6.5

Hey guys, just updated. I noticed an issue with rez-depends under py3/windows on the latest release.
rez-depends fails with a stacktrace:
C:\Users\willjp\Desktop\tmp\tma\src\core\tmatoolRezPackageBuilder>rez-depends tmacoreAppLauncher
Traceback (most recent call last):
  File "C:\Python-3.6.5\Lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Python-3.6.5\Lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\willjp\Documents\tma\rez\install\Scripts\rez\rez-depends.exe\__main__.py", line 7, in <module>
  File "c:\users\willjp\documents\tma\rez\install\lib\site-packages\rez\cli\_entry_points.py", line 138, in run_rez_depends
    return run("depends")
  File "c:\users\willjp\documents\tma\rez\install\lib\site-packages\rez\cli\_main.py", line 152, in run
    returncode = run_cmd()
  File "c:\users\willjp\documents\tma\rez\install\lib\site-packages\rez\cli\_main.py", line 144, in run_cmd
    return opts.func(opts, opts.parser, extra_arg_groups)
  File "c:\users\willjp\documents\tma\rez\install\lib\site-packages\rez\cli\depends.py", line 63, in command
    private_build_requires=opts.private_build_requires)
  File "c:\users\willjp\documents\tma\rez\install\lib\site-packages\rez\package_search.py", line 88, in get_reverse_dependency_tree
    next(bar)
TypeError: 'ProgressBar' object is not an iterator

When I have some extra time I'll see about making a pull request if it's helpful :).

Got you covered in #766 PR. This is my mistake, in batching updates to py3 centric iterators, whereas this progress library really just expects the oldschool iterator handling in spite of advertising itself as py3 friendly.

oh right on! thanks for letting me know!


[FEATURE] Renaming downloaded YouTube videos

Is your feature request related to a problem? Please describe.
The youtube videos downloaded through Drifty, has the filename like this [video_id] video_title. So, the user has to take great efforts to find the file.
Describe the solution you'd like.
The feature to rename the downloaded file will help to solve the above problem.
Application Version
v1.2.2
Screenshots
No response
Additional information
If anyone wants to work on this issue, please comment below and I shall assign you with the task. Ensure that you will link this issue to your PR.

Hi @SaptarshiSarkar12, I would like to work on this feature. Could you please assign it to me?

Yup, you xan work on this issue. @varad64


cross-build quicklens for Scala.js

I heard about quicklens a few weeks ago and have been wanting to try it out; the first time I've had a real reason is for Scala.js front-end work. I've locally published 1.3 built with this commit, and have used the javascript version and seems to work great (as all macro projects should).
Anyway, ScalaZ & Monocle have already been ported to SJS, and Shapeless is starting to release official builds, but those projects are scary to me (not smart enough yet) - it'd be cool if you published an official SJS artifact!

(and the 1.4-SNAPSHOT seems to be working just as well)

Thanks! I just published the snapshot - can you test that it's ok? I'll do a normal release then.

I switched from my compiled jar to the jars from sonatype snapshots and everything still works great!

Released 1.3.1 - thanks again!


Fix/sync placeholder

I exposed the updateSyncStatus function in the Node.js API for seamless integration and usage in external applications.

@miguelsw
Additionally, merged with the 'feat/synchronization-monitoring' branch to expose the two required functions.


Unable to create "CorrelationFilter" rule in ServiceBus subscription from AZ CLI - 'az servicebus topic subscription rule create'

Hello,
I am able to create ServiceBus subscription rules/filters through the Azure portal, but I am not able to create the same subscription rule/filter through AZ CLI.
while creating through az-cli, I am getting below error.
az servicebus topic subscription rule create --resource-group myresourcegroup --namespace-name mynamespace --topic-name mytopic --subscription-name mysubscription --name myrule --label myvalue --debug

msrest.http_logger :     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
msrest.http_logger :     'X-Content-Type-Options': 'nosniff'
msrest.http_logger :     'Date': 'Wed, 29 Jul 2020 20:12:52 GMT'
msrest.http_logger : Response content:
msrest.http_logger : {"error":{"message":"Value cannot be null.\r\nParameter name: sqlExpression CorrelationId: 449c0b40-baf6-4830-9c4b-2a19c0d01ad3","code":"BadRequest"}}
msrest.exceptions : Operation returned an invalid status code 'Bad Request'
cli.azure.cli.core.util : BadRequest - Value cannot be null.
Parameter name: sqlExpression CorrelationId: 449c0b40-baf6-4830-9c4b-2a19c0d01ad3
BadRequest - Value cannot be null.
Parameter name: sqlExpression CorrelationId: 449c0b40-baf6-4830-9c4b-2a19c0d01ad3
az_command_data_logger : exit code: 1

I don't see any option to pass the filterType=CorrelationFilter parameter in the below command.
az servicebus topic subscription rule create
I see the filterType parameter is available in ServiceBus Template template too.
Please let me if I am using any wrong command for this or do we have any other az-cli command.

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

ID: 6fd5960a-ea47-7542-6837-3e4e49e95d0a
Version Independent ID: c8a9f5b6-2a2f-4820-3be4-c87e3896a6b7
Content: az servicebus topic subscription rule
Content Source: src/azure-cli/azure/cli/command_modules/servicebus/_help.py
Service: service-bus
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Hi @gopi158 , thanks for reporting, we will look at it.

Duplicate of https://github.com/Azure/azure-cli/issues/11389.

Hi Team,
Apologies for the delay here. We have been looking into it and would get back with an update soon.

Our latest release fixes this issue: https://docs.microsoft.com/en-us/cli/azure/release-notes-azure-cli?view=azure-cli-latest#service-bus.
Please retry the operation and let us know in case of any discrepancy. Thanks


Don't warn users about every dirty form

The choice regarding which forms should or should not trigger a warning
is subjective. I tried to be consistent and not warn about forms that:

run an action, rather than edit data: search, send an email.
delete data: a warning about losing data would be confusing

Note that forms on sign-in pages were already ignored (using a selector,
rather than an explicit class on the form element).
Fixes #3698.
Note: I did not yet manage to build gitea (due to some problem with golang), so I have not been able to test this change properly

Codecov Report

Merging #3707 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3707      +/-   ##
==========================================
+ Coverage   35.79%   35.79%   +<.01%
==========================================
  Files         287      287
  Lines       41496    41496
==========================================
+ Hits        14854    14855       +1
  Misses      24454    24454
+ Partials     2188     2187       -1

Impacted Files
Coverage Δ

models/repo_list.go
56.37% <0%> (-1.35%)
:arrow_down:

modules/process/manager.go
81.15% <0%> (+4.34%)
:arrow_up:

Continue to review full report at Codecov.

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

@thehowl your suggestion does not help much ;)

@lafriks someone's pulling a prank on me, it seems (that's thehowi, not thehowl). Whatever twisted mind thought of that...


Greenkeeper/@types/lodash 4.14.76

Coverage remained the same at 96.262% when pulling 2333f1d569f48c9f8c80bc833afbea11c6f295d4 on<EMAIL_ADDRESS>into ae6a9b1c5b649061ecef56c9b70a964d3f48b9ee on master.


Improvements from enterprise app

Description: This PR contains fixes and improvements found working on new edx-enterprise app.
JIRA: ENT-21
Testing instructions:

Run tests and make sure they are passing.
Try generating new app (as described in this repo's README) and check the following:
** pydocstyle does not require all classes to have docstrings (arguable decision, see https://github.com/edx/edx-enterprise/pull/1#discussion_r84101811 for motivation)
generated docs/{{appname}}.rst is gitignored
make docs return zero violations
Django is added to dependency list in setup.py
test_utils package is present (used to workaround "tests folder should not contain init.py file")
make quality report zero violations

Reviewers:

[x] @mtyaka (internal review at Opencraft)
[x] @clintonb
[ ] @edx/platform-team

@jmbowman ping - here are some fixes/improvements to cookiecutter django app template - what are the process for handling OSPR contributions on this repo?

@mtyaka @jmbowman friendly reminder to review and approve this PR.

:+1:

[x] I tested the changes using instructions from the PR description
[x] I read through the code
[x] Includes documentation documentation not required

@edx/platform-team Could someone please review this PR?

@jmbowman Thank you (and no worries for the delay)!


Add validation for orcid field

Why was this change made?
How was this change tested?
Which documentation and/or configurations were updated?

Superceded by #1880


Improve kernel config for fused brute force knn search

Using the example from #277, one can observe that the performance of the fused distance+knn kernels are not ideal when the number of queries is low. The task is:

tune the configuration of the fused distance+knn kernels to maximize performance
re-evaluate the logic to choose between fused and non fused kernels

Cross referencing FAISS issue https://github.com/facebookresearch/faiss/issues/3621


proposal: affected/package: Adding Stack and stacktrace details as cause to the error

Proposal:
I would be interested to provide a proposal and design for finding runtime details for the errors and append them to the wrapped errors hierarchically.
The same error details can be unwrapped, formated and will be applicable and used wherever needed across other existing functions.
Please let me know if a proposal of this kind would be helpful enough and considered for future Roadmaps.

I'm sorry, I don't understand what you mean by "finding runtime details for the errors."  If you mean a stack backtrace, see https://pkg.go.dev/github.com/go-errors/errors.

Yes stack details, frames, file no and line no like that.
can that be implemented as part of errors standard lib as well, without adding any new struct but do that change with string formatting and appending as part of struct errorString struct in errors package.
However we have to have implicit internal calls to collect those stack details as part of https://cs.opensource.google/go/go/+/refs/tags/go1.20:src/errors/errors.go;bpv=1;bpt=1;l=66?gsn=errorString&gs=kythe%3A%2F%2Fgo.googlesource.com%2Fgo%3Flang%3Dgo%3Fpath%3Derrors%23type%2520errorString
But to show or unwrap them can be optional parameters in func or formatting…

Sorry, we are not going to change the standard library errors package to collect additional information by default, whether that additional information is stack traces or file/line information or whatever.


Does not detect misspelt words

Fails to detect obviously misspelt words, such as:
hellosd
applesq
bananasa
respectss
Tested version 1.0.1 on Windows.
Am I missing something?

Thank.  That is an issue.  For some reason the code is assuming that since the first part is a valid word. The rest must also be valid.

Thank you for finding this issue.  It has been fixed.

Works for me; great support! Thanks.

I also found that "alsmot" (for almost) it not detected. I've just confirmed this in version 1.0.2 with the UK dictionary in a C file. Is this a mistake in the dictionary or something else?

It must be in one of the dictionary files someplace.  I am working on a trace function to show which dictionaries contain a file.


Mattermost Electron Steals Focus on new message

I confirm (by marking "x" in the [ ] below: [x]):

[x ] This is not a troubleshooting question. Troubleshooting questions go here: https://docs.mattermost.com/install/troubleshooting.html.
[x ] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
[x ] I have read contributing guidelines.

Summary

Environment

Operating System: Ubuntu 22.04
Mattermost Desktop App version: 5.1.0
Mattermost Server version: 6.7.0

Normal usage.
New messages should provide a notification in taskbar of new message, however the electron app should remain in current state of focus - either behind current active application(s) or in front if active application.
Descriptive:
MM Desktop steals focus and comes to foreground on any new message. If the user is in the process of typing in another application (e.g. creating an email), MM comes to the foreground and steals focus and typing results in MM.

@mtompkins I believe this is the same issue as this one correct? https://github.com/mattermost/desktop/issues/1827

@mtompkins I believe this is the same issue as this one correct? #1827

Apologies, autoraise was an unknown term to me. I would agree this is the same.


[WIP] Convert misc pages to markupsafe (markupsafe-4)

Refs [#OSF-4426]
Purpose
Continues the markupsafe series. This PR focuses on single / miscellaneous pages, including search, meetings, SHARE, login, and dashboard functionality. All testing notes from previous items in the series continue to apply.
Summary of changes / routes affected
Some of these routes are static or otherwise make minimal use of mako variables. Routes particularly expected to be affected by this conversion are marked with a (*).
TODO: Write list once conversion complete

Closing for now until this gets back in to the priority queue.


build: remove ts-node forking bug workaround

In the past, ts-node had a bug that prevented forking processes when used in
combination with --esm.
We contributed a fix upstream to ts-node to fix this, and this commit updates to
the latest version so that we can simplify our ng-dev invocation. TypeStrong/ts-node@32d07e2

Thanks. I will send a patch port


Correct sentinals -> sentinels typo

@cidrblock This renames a module. Do we need changelog fragment or not really?

I think this partially depends on whether we can treat this as public API (technically, we don't use _private notation anywhere so there's no clear "statement" in code). Although, it may be useful for the contributors, in which case maybe think about adding an internal fragment if it's useful but only for the maintainers, use misc.
But a more generic answer to this question would be — think if reading this sort of information would be useful to you (as an external contributor, as a maintainer or as a user). If the answer is "yes", you probably want a fragment. If the answer is "no" — it depends if somebody else can think of a reason to include it.

@ssbarnea I noticed that this changes more things than mentioned in the title or description. Plz reflect those changes there.

RE change log. I have no pref here today.  If we had 1000s of contributors, I might weigh in.
Wouldn't that be cool?

@ssbarnea I've corrected a few very minor typos in the change note and requested gating. I hope that's alright with you.


What's the license for this repository?

The code is under the MIT license though SPDX headers, though I'll add the LICENSE file now.

Could you add the LICENSE file to the 0.1.0 version too?

I'll make a new tagged release v0.1.1. I recently fixed a few major bugs; for example, trying to iterate an empty HierarchicalBitset would throw an exception :P

Oh, even better then.


Fix error when optional merchant ID is not referenced

All Submissions:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you read and signed the automated Contributor's License Agreement?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

[ ] Does your submission pass tests?
[ ] Have you lint your code locally prior to submission?

Changes to Core Features:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your core changes, as applicable?
[ ] Have you successfully ran tests with your changes locally?

When we use the Node sdk, it say that the Merchant ID is optional if the user have only one merchant, but it's not the case, when the merchant ID is not referenced, an error occurs. This PR make the merchant ID really optional.
I'm not familiar yet with the project, so please, let me know if the modification fits the project conventions.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Bob Merlet seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


autovpn -T -r us-east-1 does not shut down the instance

After starting an instance, running openvpn, and terminating it, the command autovpn -T -r us-east-1 does not stop the instance.
I also tried autovpn -T -r us-east-1 -i instance_id. The instance_id can be obtained from the EC2 console or via aws ec2 describe-instances.

-z is to specify instance to terminate
On Sat, Jun 24, 2017, 14:15 Dale Smith<EMAIL_ADDRESS>wrote:

After starting an instance, running openvpn, and terminating it, the
command autovpn -T -r us-east-1 does not shut down the instance.
I also tried autovpn -T -r us-east-1 -i instance_id. The instance_id can
be obtained from the EC2 console or via aws ec2 describe-instances.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ttlequals0/autovpn/issues/40, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIRxhP1_kKN7Akrjtsaj0h83Y4UoNPVJks5sHWA7gaJpZM4OEaeX
.

Thanks, did something dumb.


What is the dimension of the learnable feature grid?

Thanks for your excellent work! Curious about the details of the learnable feature grid (e_coord), what is the dimension of it and do you keep it the same dimension when rendering images of different resolutions?
Looking forward to your reply.

In our paper, the learnable feature grid is designed as a 32-channel 3D volume with a resolution of 963. We keep it the same resolution for different image sizes.

@MrTornado24 Thanks for your explanation. Would the 96^3 grid limit the resolution of synthesized images (e.g. poor results on 256x256)?

@cwchenwang You can try to use a smaller grid size but the feature grid is not the bootle neck of rendering resolution in our case. To render higher resolution images you can use 2D superresolution networks instead of the pure nerf architecture in FENeRF.


trailing comma

Bug Report

TSLint version: 3.10.2
TypeScript version: 1.8.10
Running TSLint via:  Node.js API

TypeScript code being linted
 return {
            error: g.error.yes,
            model: undefined,
            errorBag: validationErrors
        }

Actual behavior
Reports an error of missing trailing comma after validationErrors

Expected behavior
It should not. I can remove this behavior when moving the brace up, but I prefer it where it is.

@Brakkar What settings are you using for the trailing-comma rile?

@Brakkar you can disable this check with trailing-comma: { multiline: "never" } (or omitting multiline altogether).
see http://eslint.org/docs/rules/comma-dangle for reference.

@adidahiya this did fix the issue. Thanks.


seeds order products

comments for changes on the associations:
got rid of "purchase_id" because i think that's going to be confusing for later use (for un-checked-out carts)
got rid of "product_id" because don't actually need it. we get productId "for free"


audio_common: 0.3.11-1 in 'noetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository audio_common to 0.3.11-1:

upstream repository: https://github.com/ros-drivers/audio_common.git
release repository: https://github.com/ros-gbp/audio_common-release.git
distro file: noetic/distribution.yaml
bloom version: 0.10.6
previous version for package: 0.3.10-1

audio_capture

No changes

audio_common

No changes

audio_common_msgs

No changes

audio_play

No changes

sound_play
* Merge pull request #167 <https://github.com/ros-drivers/audio_common/issues/167> from k-okada/fix_155
* Use rospy.myargv() instead of sys.argv to support remapping
* Contributors: Kei Okada, Shingo Kitagawa

@knorth55 please, consider adding a BSD license at the root of https://github.com/ros-drivers/audio_common.git.


VS2015 compile fail

Hi all,
I'm trying to import json.hpp into my project. When compiling, an error came out and pointed to line 8500 "max = static_cast<uint64_t>(std::numeric_limits<number_integer_t>::max()) + 1;"
Error Code: C2589 '(': illegal token on right side of '::'

I'll have a look into this. Just to make sure:

Are you using the most recent version from the develop branch?
Which version of MSVC are you using?

I'm asking because AppVeyor could execute all tests successfully (https://ci.appveyor.com/project/nlohmann/json) with MSVC 19.0.23918.0.

I can confirm that this does happen with the most recent commit in VS2015.  This is due to the fact that Windows defines max() and min() as macros in windows.h.  You can avoid the macro expansion by surrounding numeric_limits::max in extra parentheses, like so:
max = static_cast<uint64_t>((std::numeric_limits<number_integer_t>::max)()) + 1;

You can also add the following to prevent them from being defined, as long as none of your code requires them to be defined, or you can update your code.
#define NOMINMAX

Many thanks to all. I will test right the way

@nlohmann I'm using VS Community 2015 Version 14.0.23107.0 D14REL and it is the  most recent version from the develop branch

@Epidal your suggestion fix the issues. Thx
@gregmarr NOMINMAX seems not work

You need to define that before including any Windows headers.

I committed the fix, but I won't merge it before Travis builds it (there seem to be problems with the LLVM's apt server...)

Finally merged commit b508d1f to develop branch.


fv3fit.emulation: add temperature scaling

The microphysics emulator performs poorly in cold places. Performing ML in a temperature-scaled space should help.
Added public API:

fv3fit.emulation.transforms.ConditionallyScaled configuration class

Some interpolation and groupby-apply-combine functions utilties:

fv3fit.keras.math.piecewise
fv3fit.keras.math.groupby_bins

Running an experiment with this code here: https://wandb.ai/ai2cm/microphysics-emulation/runs/1ctz7e3w/overview?workspace=user-nbrenowitz


Update adoption-score.md

Adoption score not available in GCC.
per issue #https://github.com/MicrosoftDocs/microsoft-365-docs/issues/9814
No other reference document.

@JohanFreelancer9 Please copy review

Learn Build status updates of commit 7684bb0:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/adoption/adoption-score.md
:white_check_mark:Succeeded

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

Learn Build status updates of commit a2685a9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/adoption/adoption-score.md
:white_check_mark:Succeeded

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

@JohanFreelancer9

@efrene

Learn Build status updates of commit b2d12b8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/adoption/adoption-score.md
:white_check_mark:Succeeded

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


⚠ Spryr has degraded performance

In afa7841, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3905 ms

Resolved: Spryr performance has improved in 58fdd87 after 10 minutes.


[FLINK-25899] Add connected components example

This PR adds an example for calculating the connected components using Stateful Functions.
This PR needs to be ported to dev and release-3.2.

Thanks for the review @igalshilman. I've addressed your comments and pushed an update. Merging this PR now into release-3.1, release-3.2 and dev.


extending doc to turn off migrations Closes #178

The commented line requires reference to a previously refactored base.py and an additional import to refer to the database engine.
The Readme documents that alembic migration can be turned off and hence this extension of the documentation and commented code allows to do so going forward.
:dancers: When working together in a repo, do consider to use migrations to avoid database schema conflicts that cannot be rolled back.

Thanks! This was covered in another PR, so I'll pass on this one, but thanks for the effort! :coffee: