'go ' conflicts with generic_editor 'go left/right/up/down'

This is really only a problem if the edit actions are overridden, but one might want to do so for vim...

What behavior do you think you would like? I see three options:

Remove the generic_editor go left/right/up/down commands and only have go <arrow keys>. If you want custom commands for the edit actions, you can add them yourself.

Have go <arrow keys> use edit.left()/edit.right() etc instead of pressing the corresponding keys. Since the default implementations of these are to press the arrow keys, this should be mostly ok? However, it means there's no command to just press those arrow keys if edit.left() etc are overridden. Hm.

Have separate commands for pressing the arrow keys and issuing the edit actions. I'm not sure what these would be called, though.

Have separate commands for pressing the arrow keys and issuing the edit actions. I'm not sure what these would be called, though.

I've seen people (myself included) use the cardinal directions. Not sure if they should belong in knausj_talon, but something to consider.
In that scenario I think it would make sense to keep go <arrow keys> as is, to keep things simple.

Yeah, I'm inclined to leave go <arrow keys> as is and remove or comment out the go left/right/up/down commands in generic_editor.

I would definitely keep go <arrow keys>
Could always use a synonym like walk/march/trek if there's value in keeping the generic_editor commands, but I'd be tempted to make that application-specific.

I would definitely keep go <arrow keys>
Could always use a synonym like walk/march/trek if there's value in keeping the generic_editor commands, but I'd be tempted to make that application-specific.

The approach we landed on during the grooming session today was to

have go <user.arrow_keys> map to edit.direction in generic editor (pressing the arrow keys as many times as was chained),
but then have a separate command press <user.unmodified_key> which can be used to directly press the specific key such as up or down

wdyt @rntz ?

That seems ok, although it means press has three quite different meanings:

press <user.keys> to press a sequence of keys in dictation mode.
press <user.modifiers> to press a modifier key in command mode, eg. press super.
press <user.unmodified_key> to press an unmodified key in command mode, eg press left.

We already had (1) & (2), so this issue already existed, this just makes it more obvious. Maybe this merits a separate issue.
Anyway, if there are folks who want this, and knausj has signed off, I have no objection.

I made a PR to fix this and also my complaint about press being inconsistent: #742.


[2.7.0] Remove Rancher v1 Pipelines UI components

Is your feature request related to a problem? Please describe.

Rancher pipelines were deprecated in rancher v2.5.0. So we need to remove all the associated components in v2.7.0
Additional context

Linked issue: https://github.com/rancher/rancher/issues/37324

per comments in github, this work item has been tested by QA. moving to QA complete.


Enable optional per-method Context callback.

Adds an optional callback to Service that allows manipulation of the
Context that is passed to the method handler based on the
service/method, as well as preliminary request rejection.
Also adds accessor methods to pull the ServiceInfo and MethodInfo from
the handler's context.
This avoids the need to place boilerplate code at the beginning of each
method handler and enables unified Service-wide security and setup
operations.

Implemented by #126


request: Capture shutdown DockableWindow events

How to capture shutdown DockableWindow events. Thank you

Hi,
I'm not sure I understood your need.
However if you need to know whether a window is opened or not, you can

Query its pointer:
C++

        auto window = HelloImGui::GetRunnerParams()->dockingParams.dockableWindowOfName("My Window");

Python:
window =     hello_imgui.get_runner_params().docking_params.dockable_window_of_name("My Window")

Query whether it is visible: window->isVisible

Thank you!
DockableWindow  have a close button.  Some windows I don't want to close., so I want to intercept this button closure event.

Well, at the moment there is no OnClose callback. The best you can do is check whether it was closed on the next frame.
For this you might use the callback runnerParams.callbacks.PreNewFrame (this callback is called before ImGui::NewFrame, so that the window is not yet hidden. You cannot display any Gui in this callback!)
Inside this callback, you can check your window open/close status. If you want to cancel the closing, you can do flip the isVisibleflag. Also, you may also set a boolean flag that  later cause a DialogBox to be shown.

thank you！

How to add such a callback function？

How to add such a callback function？

Your question is not clear enough


chore(deps): upgrade configuration

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-configuration-1.x" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2846

Questions ?
Please refer to the Backport tool documentation


The "Add new item" windows jumped out again after add new item in Django project.

Environment
Build of Visual Studio: 17.1.0 Preview 3.0 [32020.144.main]
Build of Python Package: 17.0.21344.1
OS version: Windows-10-Enterprise-21H1
Python install of Microsoft
Steps to Reproduce

Create a new Django Web Project
Select the project ->Right click ->Add ->New item
Choose a new item and click Add
Observes

Expected behavior
The new item is added successfully without any other error.
Additional context and screenshots
The "Add new item" windows jumped out again

In today's build 17.1.0 Preview 3.0 [32021.100.main], I can repro it in web-based Projects. (Python Application cannot repro.)

On today's build,

This issue also can reproduced on Flask Web Project and Bottle Web Project.

@StellaHuang95 , i can't repro this on today's latest build:  Version 17.4.0 Preview 1.0 [32705.268.main]


Js import is dropped on cell recalculation

Plot something (e. g. an example from tutorial)
Recalculate the same cell
Refresh the page

Expected:
The plot is still shown
Actual:
No plot is shown, an exception window.letsPlotCall is not a function in js console

Unfortunately, IPython API doesn't seem to provide a way to handle a page refreshment in python.
I recommend to use load_lets_plot_js() function somewhere near imports.
It will reload the library every time the notebook cell is evaluated.
For example: distributions.ipynb

That Notebook shows an error "Error loading Lets-Plot JS" and no graphs are displayed. I'm getting the same thing on my local installation I created 2 days ago.

Unfortunately, IPython API doesn't seem to provide a way to handle a page refreshment in python.
I recommend to use load_lets_plot_js() function somewhere near imports.
It will reload the library every time the notebook cell is evaluated.
For example: distributions.ipynb

Just tried this notebook and it looked fine. Probably there was an interruption of the cdn service. Is it still not working for you?

It seems that there is a problem with rendering on Firefox. I tried with Firefox and a Firefox incognito window and get the same error result. On Chrome it appears as I would expect.  My local Jupyter installation also works as expected on Chrome.

I can see no problem in Firefox 74.0 (64-bit) on Mac. Can you see any errors in FF browser console?

@gsteckman could you run Firefox in Safe Mode and check this notebook again (to make sure that the issue is not caused by extensions and/or settings). Also it would be great to see a browser console output.

In Safe Mode, in a private window, everything looks good. Reloading in my regular non safe mode Firefox, I get the following in the console:

So this issue is caused by an extension or settings. I would recommend to disable Ad blockers first, then other extensions. Please leave a comment if this will solve your issue (and name of extension) or take a screenshot of Network tab from developers tools (you can see it in your screenshot. First you need to open this tab, then reload the notebook to capture the data and select GET request for lets-plot like in example image).

This was solved by disabling the extension PrivacyBadger (https://www.eff.org/privacybadger). With PrivacyBadger enabled, the GET request for lets-plot-1.2.0rc2.min.js doesn't occur. Thanks for your help.

@uppi  The issue was fixed in 1.3.0


offline only cufflinks with no dependency on chart_studio

This is related to #196
cufflinks 0.17.0 depends on chart_studio, in particular I found two import of chart_studio in the code
https://github.com/santosjorge/cufflinks/search?q=chart_studio&unscoped_q=chart_studio
Since plotly is pure offline now, and cufflinks can go_offline, we don't want the dependency on chart_studio. Actually in our environment we can't install chart_studio. I think this is the reason why it is split out of plotly at the first place.
So this is kind of a feature request: please make the chart_studio dependency conditional. By default it goes into offline mode, and chart_studio code is needed at all.
I tried to patch 0.17.0 myself, replacing cufflinks/init.py line 23 from
from chart_studio.plotly import plot
to
from plotly.offline import plot
and replacing cufflinks/plotlytools.py line 2 from
import chart_studio.plotly as py
to
import plotly.offline as py
it doesn't really work. For example I get
In [1]: import cufflinks as cf
In [2]: cf.go_offline()
In [3]: fig=cf.datagen.histogram(3).figure(kind='histogram ')
In [4]: cf.iplot(fig,online=True)
TypeError Traceback (most recent call last)
 in
----> 1 cf.iplot(fig,online=True)
cufflinks/0.17.0/lib/cufflinks/plotlytools.py in iplot(figure, validate, sharing, filename, online, asImage, asUrl, asPlot, dimensions, display_image, **kwargs)
1464 else:
1465 return py.iplot(figure,validate=validate,sharing=sharing,
-> 1466 filename=filename)
1467
1468
TypeError: iplot() got an unexpected keyword argument 'sharing'
I assume this is due to API difference between plotly.offline and chart_studio.plotly. So this request is about to make it all depends on plotly.offline API.

In principle I support this. I think we should do this in v0.18 so that v0.17 is minimally different from v0.16.

This is partly addressed in #211, which makes the chart_studio dependency optional.


Dart rules in flutter/engine should use package_config.json instead of .packages

The .packages file doesn't contain language version information, which can block rolls of null safe packages through the engine. It should be straightforward to switch to .dart_tool/package_config.json, and this is already done for the flutter_frontend_server and the const_finder libraries.
The remaining dart rules should be audited and updated.

fyi @zanderso

@jonahwilliams Looks like you're on this already, but could you link to an example location that needs an update? Thanks!

Here is an example commit that fixed const_finder:
https://github.com/flutter/engine/commit/35b5aa5af24925eec3f3bf17543a8662831f57b3
Notable differences: dot_packages in the gn template updated to point at .dart_tool/package_config and the generate package_config script updated to generate this on gclient sync (so that the language versions are up to date for rolls). Keeping a checked in .packages isn't sufficient anymore

Blocked by https://github.com/dart-lang/sdk/issues/42614 for the kernel_compiler target

Status: currently waiting on a dart roll


Some difficult questions (SCSS import as string)...

How to use scss as compiled, but inline string when import from JS?
import styles from './index.scss?scss';
Tried, but there is weird effect with additional loader (in result empty string, or error when no css-loader).
// use require when mjs
import { createRequire } from 'module'
const require = createRequire(import.meta.url)

//
export default {
    resourceQuery: /scss/,
    type: 'asset/source',
    use: [{
        loader: 'postcss-loader',
        options: {
            postcssOptions: require("../config/postcss.config.cjs")
        }
    }, 'sass-loader']
};

Earlier here was an error problem concerning misrepresentation.
Error: Cannot 'resolveSync' because the fileSystem is not sync. Use 'resolve'!
However, this is regarding pug-loader.

(Added some tree info)

Wait some time before I reopen issue.

Hello @unit-404,
You can't use the type: 'asset/source' for imported SCSS in JS to inline CSS. That will be not works.
You can inline CSS imported in JS using the css.inline option.
See the test use case js-import-css-inline-css.

I just needs to make support of some web-components in runtime, such as <template> files in .pug format, with embedded compiled SCSS.

@unit-404
can you please create small repo with your use case.

template.launcher.immersive
    .wrap
        .grid(part='inner')
            slot

    // webpackIgnore: true
    style(scoped='').
        @import url("./modules/uno.css");

    // webpackIgnore: true
    style(scoped='').
        @import url("./modules/styles.css");

    // exact moment, but in practice harder
-    style(scoped='')
-        include ./x-grid.scss
     //- you can inline a style using `?inline` query (no webpack configuration required)
          in generated HTML will be <style>... compiled CSS ...</style>
+    link(href='./x-grid.scss?inline' rel='stylesheet')

I sometimes thought that  is still for the  tag, and is more intended for global styles, while

I sometimes thought that <link> is still for the <head> tag, and is more intended for global styles, while <style> still implies scoped ie within the web component.

you can use link tag in Pug anywhere, not only in head, this is just a syntax that allow you to include CSS anywhere in your template:
template
  divcomponent
       link(href='./x-grid.scss?inline' rel='stylesheet' scope='some')

will be compiled to:
<tremplate>
  <div class="component">
    <style scope="some">
      ... CSS ...
    </style>
  </div>
</tremplate>

@unit-404
I have added experimental support to include a compiled CSS directly to style tag using the require() and the ?include query:
style(scoped='some')=require('./x-grid.scss?include')

The generated HTML:
<style scope="some">
    ... CSS ...
</style>

Please, update the plugin to the version 5.2.0.


nomad-pack: 2022-05-12 -> 0.0.1-techpreview.3

Description of changes
https://github.com/hashicorp/nomad-pack/releases/tag/v0.0.1-techpreview.3
https://github.com/hashicorp/nomad-pack/compare/bee6e8e078ff31fee916b864fbf3648294dbcdf5...v0.0.1-techpreview.3

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

I don't have a good feel for whether this software is still too volatile to track closely in nixpkgs, but feedback about that or anything else is always welcome!

@shanesveller yeah, I wasn't sure either, that's why I was targeting specific commits as the "techpreview" tag hadn't been updated in a while and instead just sending an update every month/ or two, but this is probably for the best to use a proper tag.


Pin ml_dtypes

Will newer versions of ml-dtypes be supported by tensorflow ?

Main branch does not have the upper bound, so yes.

Ok ! Thanks for the explanation on the PR :)


New package: Aislx.FlameLauncher version <IP_ADDRESS>

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

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

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

Microsoft Reviewers: Open in CodeFlow

Manual Validation ended with:

2024-02-22 18:51:24.428 [FAIL] Installer failed security check. Url: https://github.com/aislxflames/flame-launcher/releases/download/v1.0.0/fmcl.setup.latest.exe Result: 0x80004005

(Automated response - build 807.)

Hi @aislxflames,
The package didn't pass a Defender or similar security scan. This might be a false positive and we can rescan tomorrow.


Add support for Plug'n'Play

Is your feature request related to a problem? Please describe.
After the release 0.72.0 promptfoo stopped supporting Plugnplay. It fails to start with the error message:
Error: promptfoo tried to access @inquirer/editor, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

Describe the solution you'd like
Install promptfoo via yarn using pnp - which is the direction the ecosystem is going.
Describe alternatives you've considered
The problem can be circumvented by using the traditional node_modules approach, but that breaks other pieces of my project and could introduce potential errors in the future with ghost dependencies.

Thank you, @pedrooa, for your quick solution on Discord! For anyone else facing the issue, here’s the solution:
To resolve the problem with Plug'n'Play (PnP) and promptfoo:

Update your yarn configuration to use nodeLinker:
yarn config set nodeLinker node-modules
yarn

This will switch from using Plug'n'Play to the traditional node_modules approach, which resolves the issue with missing dependencies for @inquirer/editor.
I’m closing this issue since we have a path forward. Thanks again for the solution! Thanks again @pedrooa


Empty table

Describe the bug
While the table is empty the translation is not shown properly. You see: SafeValue must use [property]=binding: No data to display (see http://g.co/ng/security#xss)
To Reproduce
Steps to reproduce the behavior:
Create an empty table
Expected behavior
You should only see: No data to display

Done

Done


[FEATURE REQUEST] ... Income by Source

Similiar to the "Spending by Payee" report, I'd like to see my income differentiated by source. Thanks for reading my feature request ╰(°▽°)╯

@tobykoby Does the Income Breakdown satisfy this for you?

Not entirely, I'd like to see it as a pie chart. BTW, I am amazed by the pure fact you responded to my request.

hah, trying to get better about it. I'll add this as a feature request then to offer a pie chart as anther income breakdown view. hopefully it's something can get excited about building :D

+feature

We use Trello to track Feature Requests so that users can vote on what they'd like to see next. This is crucial for us since there are so many requests and so little time amongst those of us who work on the Toolkit.
Your feature request has been added here and will need to be manually sorted.
This issue can now be closed.


Expose RDFLoader class to global context + Pass file format information from Loader to Parser + fix typo

This is a rollup of three changes I have made to rdfstore-js sources while working on my current project.
I needed to override a prototype function on the RDFLoader Class from within another JS library, to add additional functionality. In order to do that I needed to expose RDFLoader to the global context. Several other classes such as RDFModel and QueryEngine are exposed globally so I think RDFLoader should also be accessible.
The second change is to pass a format parameter in the options struct from the RDFLoader to the selected parser via the tryToParse method. The N3 parser needs this option passed in to determine whether the file is Turtle or N3 in order to set some internal parsing options.
The final change is a small but nasty typo I found, which affects the use of the store.load helper.

I backup @ashleysommer's PR, it is a necessary fix. Please merge!


chore: testing bridge interactions

Optimism.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 97.72%. Comparing base (357539f) to head (1c515d3).

Additional details and impacted files
@@                     Coverage Diff                     @@
##           addressing_issues_56_27     #169      +/-   ##
===========================================================
+ Coverage                    97.14%   97.72%   +0.57%
===========================================================
  Files                           22       22
  Lines                         1718     1716       -2
  Branches                       386      385       -1
===========================================================
+ Hits                          1669     1677       +8
+ Misses                          49       39      -10

Flag
Coverage Δ

unittests
97.72% <100.00%> (+0.57%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[DOC] Improve documentation of decoders

Closes #436.

Changes proposed in this pull request:

Improve the discrete decoders section (methods/decoding.rst).
Add the continuous decoders section. Add a non-running example.

Open questions:

Do we also want to add the encoders section as part of this pull request?

@JulioAPeraza Is this ready for review?

Yes, it is ready. Thanks!
In addition to the text and formulae from your NiMARE manuscript, I also incorporated text and a non-running example of the CorrelationDecoder with the feature_group argument, so the wording there may be a little confusing.

The math doesn't seem to be rendering properly. Are we missing the necessary plugin or is it maybe formatted for a different language (e.g., markdown)?

I don't know what is causing this. I built the documentation locally with the same version (v4.2.0) of Sphinx that CircleCI used, and the math looked fine.
To generate the latex images, I used the extension "sphinx.ext.imgmath", which is already in the conf.py file.

Hm, okay. It could be that the CI build job is just not configured correctly. This is one good reason for us to switch to using the RTD CI tool instead of CircleCI for the docs build, though I had trouble setting it up the last time I tried.
Anyway, I'm leaning toward merging and then fixing if there are problems.

Do we need to install latex in the Docker image?

I'm thinking we should just merge and see how it goes. If there's a problem then we can fix later. Any concerns with me merging as-is?

Please, feel free to merge it. Thanks!


Randomly resize images at run time in Image datagenerator

Can the image data generator handle the random resizing of the input dynamically, meaning, resize the input to one of the given scales like [256,384, 512, 680..]
Most of the codes i checked does  the resizing externally before passing to the image datagenerator.
The closest one i came across is the 'preprocessing_function' argument in the ImageDataGenerator requires the output tensor to be of same shape of input tensor. Is there a simple implementation to circumvent the problem.

Request you to resubmit a question by filling all the information asked in this template.. Feel free to close if it no longer exists.


Fix update_stream in publisher

Redo of https://github.com/lbryio/lbry/pull/576, I misunderstood what this code was doing.
In Publisher class,
publish_stream() was used to create a lbry file and make a claim, triggered when file_path was specified in jsonrpc_publish().
update_stream() was used to only make a claim, without creating a lbry file, triggered when no file_path was specified and the source was specified indicating already created lbry file in jsonrpc_publish().  It also incorrectly assumed that it was an update and would try to fetch a previous claim, and reuse the fields in the previous claim (same issue as https://github.com/lbryio/lbry/pull/569)
Rename publish_stream() to create_and_publish_stream()
Rename update_stream() to publish_stream() , remove the code that fetched the previous claim and reused its field.

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.

          1 Message

:book:
See http://keepachangelog.com/en/0.3.0/ for details on good changelog guidelines

  Generated by :no_entry_sign: Danger

merged with https://github.com/lbryio/lbry/pull/586


Product dashboard displays NaN for Security Issues

@tabladrum Product dashboard displays NaN for security issues, if 'blocker' issues contain empty string, though 'critical' or 'major' issues types have non Zero values. The graph for security issues also displays nothing in such cases, if 'blocker' issues have a zero value.
Possible cause might be usage of parseInt in /Hygieia/UI/src/components/widgets/product/js/security-analysis-data.js, which returns NaN for empty string.
Line 68 : blocker: parseInt(getCaMetric(metrics, 'blocker'))

@sanjeevnewt  - can you paste a screenshot for this issue.

@sanjeevnewt  update to latest codebase and reopen with screenshot and error log if still an issue.


Wilke/command line tool

closes #103

It would be nice to have some basic tests, but that can always be added in another PR.


feat: bump hdwallet packages

Description

Bumps hdwallet following https://github.com/shapeshift/hdwallet/pull/681. Should be a no-op for the time being (Ledger structured signing coming in soon in https://github.com/shapeshift/hdwallet/pull/674, which this PR prepares for) , but...
Issue (if applicable)

closes N/A
Risk

High Risk PRs Require 2 approvals

What protocols, transaction types, wallets or contract interactions might be affected by this PR?

Technically a no-op but high because of the build changes (now using ESNext in tsconfig.json in hdwallet-land) - already paranoia tested in https://github.com/shapeshift/hdwallet/pull/681 and didn't notice any regression, but worth retesting
Testing

Test all wallet things:

creating/loading a native wallet
connecting wallets
sending Txs on all-chains, for all wallets
signing messages (i.e CoW swaps) for all wallets
accounts correctly derived for all chains and wallets

Engineering

^

Operations

[ ] :checkered_flag: My feature is behind a flag and doesn't require operations testing (yet)

^

Screenshots (if applicable)
https://github.com/shapeshift/hdwallet/pull/681#discussion_r1759530723

Rage quitting fixing build things with vitest, will reopen once fixed


Racism and sexism within this project (trigger warning)

It has come to my attention that you have just closed multiple issues and pull requests, and this appears to have been done without checking your privilege, or for any people of colour, or women. It is very possible that these actions were a result of racism, sexism, or both. I recommend you find a long and detailed CoC and shove it right up inside this repository, to prevent any future discrimination that may be caused by your CIS white male privilege.

Some excellent points raised by installgen2. I hope they can be rectified ASAP.

P.S., project maintainers may find some useful reading attached.
1984.txt


User Pills Are Now Displayed in the Dropdown After Being Selected

When users are searched, the suggest pill will continue to be displayed in the dropdown, even after being selected.
Fixes: #23365

Self-review checklist

[X] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ X] Explains differences from previous plans (e.g., issue description).
[X] Highlights technical choices and bugs encountered.
[X] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[X] Each commit is a coherent idea.
[X] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[X] Visual appearance of the changes.
[X] Responsiveness and internationalization.
[X] Strings and tooltips.
[X] End-to-end functionality of buttons, interactions and flows.
[X] Corner cases, error conditions, and easily imagined bugs.

Thanks @Mina-byte !
Please clean up your commit history and commit message, and post again to request a review. See https://zulip.readthedocs.io/en/latest/contributing/version-control.html.

Closing, as this does not seem to address the issue and is stale.


Feature/historical fires by commodity category widget

Overview
Start of the multiple category ranking list - commodity production areas widget.
The widget contains:

An initial sentence for all the admin levels with no indicator option(just shows the ranked commodities within an admin area by density of alerts in alerts/ha and a title

Parsing of the values to the bar chart.

Things that need attention/fixing:

bar-chart config disappears when changing '%' value to 'alerts/Ha' in the index.js file.
need to add timeline configuration to the barchart (keep it uncomment at the moment)

Demo
If applicable: screenshots, gifs, etc.
Notes
If applicable: ancilary topics, caveats, alternative strategies that didn't work out, etc.
Testing

Include any steps to verify the features this PR introduces.
If this fixes a bug, include bug reproduction steps.

closing this PR as it is now out of date with where fires has gone. I will keep the branch as the sql and maths are valid and can be reused for the next iteration of this widget.


5 ➡ 6

➡ Forward port
Port ign-physics5 to gz-physics6
Branch comparison: https://github.com/gazebosim/gz-physics/compare/gz-physics6...ign-physics5
Note to maintainers: Remember to Merge with commit (not squash-merge or rebase)

this commit is a little weird. It doesn't look like a merge commit and I don't see a commit message about the actual changes

Not sure what happened. I think it's fixed now.


Unable to run the container in Azure Web App Service

I tried to run the Splash container in Azure Web App service by pulling from Docker Hub. Unfortunately, the app was not starting.
InnerException: Docker.DotNet.DockerContainerNotFoundException, Docker API responded with status code=NotFound, response={"message":"No such image: scrapinghub/splash:latest"}

Any help is appreciated.

@sadiq-mc Did you ever manage to solve your issue?

@Gallaecio Sorry for the delayed response. I didn't able to resolve this issue yet.

I get the same error. Is there any other way to host it in azure?

This looks like an issue with the Splash docker image, rather than with scrapy-splash. Could you please report this on https://github.com/scrapinghub/splash?
Please, mention https://circleci.com/docs/2.0/high-uid-error/ which seems to explain the root of the error and how to solve it (as in how Splash developers can fix the issue).


Elasticsearch connection refused (dial tcp <IP_ADDRESS>:9200 ) - Articulate v0.21.2 Release

Issues
I am trying to install Articulate v0.21.2
I pulled the latest from github by following the steps from
Articulate Website
Installed Docker Toolbox on Windows 7.
On running docker-compose up , I am getting a
Elasticsearch connection refused (dial tcp <IP_ADDRESS>:9200
Any help. complete trail below:
C:\Users\ss00346355\Desktop\articulate-v0.21.2>docker-compose up
Starting articulate-v0212_redis_1         ... done
Starting articulate-v0212_duckling_1      ... done
Starting articulate-v0212_rasa_1          ... done
Starting articulate-v0212_elasticsearch_1 ... done
Starting articulate-v0212_api_1           ... done
Starting articulate-v0212_ui_1            ... done
Attaching to articulate-v0212_ui_1, articulate-v0212_duckling_1, articulate-v0212_api_1, articulate-v0212_redis_1, articulate-v0212_rasa_1, articulate-v0212_el
sticsearch_1
api_1            | 2019/04/27 09:56:56 Waiting for: http://elasticsearch:9200
redis_1          | 1:C 27 Apr 09:56:56.444 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis_1          | 1:C 27 Apr 09:56:56.446 # Redis version=4.0.6, bits=64, commit=00000000, modified=0, pid=1, just started
redis_1          | 1:C 27 Apr 09:56:56.447 # Configuration loaded
redis_1          | 1:M 27 Apr 09:56:56.463 * Running mode=standalone, port=6379.
redis_1          | 1:M 27 Apr 09:56:56.467 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lowe
value of 128.
redis_1          | 1:M 27 Apr 09:56:56.470 # Server initialized
redis_1          | 1:M 27 Apr 09:56:56.472 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add
vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
api_1            | 2019/04/27 09:56:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:56:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:56:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
duckling_1       | no port specified, defaulting to port 8000
ui_1             | yarn run v1.13.0
api_1            | 2019/04/27 09:56:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
ui_1             | $ cross-env NODE_ENV=production env-cmd .env node server
ui_1             | Server started ! √
api_1            | 2019/04/27 09:57:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
rasa_1           | 2019-04-27 09:57:07+0000 [-] Log opened.
rasa_1           | 2019-04-27 09:57:07+0000 [-] Site starting on 5000
api_1            | 2019/04/27 09:57:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
api_1            | 2019/04/27 09:57:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-27T09:57:09,599][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:
elasticsearch_1  |   /usr/share/elasticsearch/config/log4j2.properties
elasticsearch_1  | [2019-04-27T09:57:12,544][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/c/Users
]], net usable_space [27.6gb], net total_space [162.3gb], types [vboxsf]
elasticsearch_1  | [2019-04-27T09:57:12,546][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] heap size [503.6mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2019-04-27T09:57:12,575][INFO ][o.e.n.Node               ] [Fy-UkXS] node name derived from node ID [Fy-UkXS_QPuGSsULTNsO-A]; set [node.nam
] to override
elasticsearch_1  | [2019-04-27T09:57:12,578][INFO ][o.e.n.Node               ] [Fy-UkXS] version[6.5.1], pid[1], build[default/tar/8c58350/2018-11-16T02:22:42.
82257Z], OS[Linux/4.14.111-boot2docker/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13]
api_1            | 2019/04/27 09:57:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-27T09:57:12,579][INFO ][o.e.n.Node               ] [Fy-UkXS] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiat
ngOccupancyFraction=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.shutdownHookEna
led=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.qaJv6FG3, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/
s_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, -D
s.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.
lavor=default, -Des.distribution.type=tar]
elasticsearch_1  | [2019-04-27T09:57:18,424][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2019-04-27T09:57:18,433][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [analysis-common]
elasticsearch_1  | [2019-04-27T09:57:18,434][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [ingest-common]
elasticsearch_1  | [2019-04-27T09:57:18,435][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-expression]
elasticsearch_1  | [2019-04-27T09:57:18,439][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-mustache]
elasticsearch_1  | [2019-04-27T09:57:18,440][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-painless]
elasticsearch_1  | [2019-04-27T09:57:18,441][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [mapper-extras]
elasticsearch_1  | [2019-04-27T09:57:18,441][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [parent-join]
elasticsearch_1  | [2019-04-27T09:57:18,443][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [percolator]
elasticsearch_1  | [2019-04-27T09:57:18,444][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [rank-eval]
elasticsearch_1  | [2019-04-27T09:57:18,448][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [reindex]
elasticsearch_1  | [2019-04-27T09:57:18,449][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [repository-url]
elasticsearch_1  | [2019-04-27T09:57:18,450][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [transport-netty4]
elasticsearch_1  | [2019-04-27T09:57:18,451][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [tribe]
elasticsearch_1  | [2019-04-27T09:57:18,453][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ccr]
elasticsearch_1  | [2019-04-27T09:57:18,454][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-core]
elasticsearch_1  | [2019-04-27T09:57:18,455][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-deprecation]
elasticsearch_1  | [2019-04-27T09:57:18,460][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-graph]
elasticsearch_1  | [2019-04-27T09:57:18,460][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-logstash]
elasticsearch_1  | [2019-04-27T09:57:18,462][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ml]
elasticsearch_1  | [2019-04-27T09:57:18,462][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-monitoring]
elasticsearch_1  | [2019-04-27T09:57:18,463][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-rollup]
elasticsearch_1  | [2019-04-27T09:57:18,463][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-security]
elasticsearch_1  | [2019-04-27T09:57:18,464][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-sql]
elasticsearch_1  | [2019-04-27T09:57:18,465][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-upgrade]
elasticsearch_1  | [2019-04-27T09:57:18,465][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-watcher]
elasticsearch_1  | [2019-04-27T09:57:18,467][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded plugin [ingest-geoip]
api_1            | 2019/04/27 09:57:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:31 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:33 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/27 09:57:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
Gracefully stopping... (press Ctrl+C again to force)
Stopping articulate-v0212_api_1           ... done
Stopping articulate-v0212_ui_1            ... done
Stopping articulate-v0212_rasa_1          ... done
Stopping articulate-v0212_elasticsearch_1 ... done
Stopping articulate-v0212_duckling_1      ... done
Stopping articulate-v0212_redis_1         ... done

I am trying to install Articulate v0.21.2
I pulled the latest from github by following the steps from
Articulate Website
Installed Docker Toolbox on Windows 7.
On running docker-compose up , I am getting a
Elasticsearch connection refused (dial tcp <IP_ADDRESS>:9200
Any help. complete trail below:
C:\Users\ss00346355\Desktop\articulate-v0.21.2>docker-compose up Starting articulate-v0212_redis_1         ... done Starting articulate-v0212_duckling_1      ... done Starting articulate-v0212_rasa_1          ... done Starting articulate-v0212_elasticsearch_1 ... done Starting articulate-v0212_api_1           ... done Starting articulate-v0212_ui_1            ... done Attaching to articulate-v0212_ui_1, articulate-v0212_duckling_1, articulate-v0212_api_1, articulate-v0212_redis_1, articulate-v0212_rasa_1, articulate-v0212_el sticsearch_1 api_1            | 2019/04/27 09:56:56 Waiting for: http://elasticsearch:9200 redis_1          | 1:C 27 Apr 09:56:56.444 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo redis_1          | 1:C 27 Apr 09:56:56.446 # Redis version=4.0.6, bits=64, commit=00000000, modified=0, pid=1, just started redis_1          | 1:C 27 Apr 09:56:56.447 # Configuration loaded redis_1          | 1:M 27 Apr 09:56:56.463 * Running mode=standalone, port=6379. redis_1          | 1:M 27 Apr 09:56:56.467 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lowe  value of 128. redis_1          | 1:M 27 Apr 09:56:56.470 # Server initialized redis_1          | 1:M 27 Apr 09:56:56.472 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. api_1            | 2019/04/27 09:56:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:56:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:56:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s duckling_1       | no port specified, defaulting to port 8000 ui_1             | yarn run v1.13.0 api_1            | 2019/04/27 09:56:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s ui_1             | $ cross-env NODE_ENV=production env-cmd .env node server ui_1             | Server started ! √ api_1            | 2019/04/27 09:57:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s rasa_1           | 2019-04-27 09:57:07+0000 [-] Log opened. rasa_1           | 2019-04-27 09:57:07+0000 [-] Site starting on 5000 api_1            | 2019/04/27 09:57:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s elasticsearch_1  | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release. api_1            | 2019/04/27 09:57:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s elasticsearch_1  | [2019-04-27T09:57:09,599][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_namewith[%node_name]%marker  in these locations: elasticsearch_1  |   /usr/share/elasticsearch/config/log4j2.properties elasticsearch_1  | [2019-04-27T09:57:12,544][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/c/Users ]], net usable_space [27.6gb], net total_space [162.3gb], types [vboxsf] elasticsearch_1  | [2019-04-27T09:57:12,546][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] heap size [503.6mb], compressed ordinary object pointers [true] elasticsearch_1  | [2019-04-27T09:57:12,575][INFO ][o.e.n.Node               ] [Fy-UkXS] node name derived from node ID [Fy-UkXS_QPuGSsULTNsO-A]; set [node.nam ] to override elasticsearch_1  | [2019-04-27T09:57:12,578][INFO ][o.e.n.Node               ] [Fy-UkXS] version[6.5.1], pid[1], build[default/tar/8c58350/2018-11-16T02:22:42. 82257Z], OS[Linux/4.14.111-boot2docker/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13] api_1            | 2019/04/27 09:57:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s elasticsearch_1  | [2019-04-27T09:57:12,579][INFO ][o.e.n.Node               ] [Fy-UkXS] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiat ngOccupancyFraction=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.shutdownHookEna led=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.qaJv6FG3, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/ s_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, -D s.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution. lavor=default, -Des.distribution.type=tar] elasticsearch_1  | [2019-04-27T09:57:18,424][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [aggs-matrix-stats] elasticsearch_1  | [2019-04-27T09:57:18,433][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [analysis-common] elasticsearch_1  | [2019-04-27T09:57:18,434][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [ingest-common] elasticsearch_1  | [2019-04-27T09:57:18,435][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-expression] elasticsearch_1  | [2019-04-27T09:57:18,439][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-mustache] elasticsearch_1  | [2019-04-27T09:57:18,440][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-painless] elasticsearch_1  | [2019-04-27T09:57:18,441][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [mapper-extras] elasticsearch_1  | [2019-04-27T09:57:18,441][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [parent-join] elasticsearch_1  | [2019-04-27T09:57:18,443][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [percolator] elasticsearch_1  | [2019-04-27T09:57:18,444][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [rank-eval] elasticsearch_1  | [2019-04-27T09:57:18,448][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [reindex] elasticsearch_1  | [2019-04-27T09:57:18,449][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [repository-url] elasticsearch_1  | [2019-04-27T09:57:18,450][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [transport-netty4] elasticsearch_1  | [2019-04-27T09:57:18,451][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [tribe] elasticsearch_1  | [2019-04-27T09:57:18,453][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ccr] elasticsearch_1  | [2019-04-27T09:57:18,454][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-core] elasticsearch_1  | [2019-04-27T09:57:18,455][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-deprecation] elasticsearch_1  | [2019-04-27T09:57:18,460][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-graph] elasticsearch_1  | [2019-04-27T09:57:18,460][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-logstash] elasticsearch_1  | [2019-04-27T09:57:18,462][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ml] elasticsearch_1  | [2019-04-27T09:57:18,462][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-monitoring] elasticsearch_1  | [2019-04-27T09:57:18,463][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-rollup] elasticsearch_1  | [2019-04-27T09:57:18,463][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-security] elasticsearch_1  | [2019-04-27T09:57:18,464][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-sql] elasticsearch_1  | [2019-04-27T09:57:18,465][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-upgrade] elasticsearch_1  | [2019-04-27T09:57:18,465][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-watcher] elasticsearch_1  | [2019-04-27T09:57:18,467][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded plugin [ingest-geoip] api_1            | 2019/04/27 09:57:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:31 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:33 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s api_1            | 2019/04/27 09:57:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused.  Elasticsearch can take several minutes to start-up.

I tried running it for 5 minutes before the articulate exited after 5 minutes.
Shared below the complete verbose log .
PS: I havent installed elasticsearch seperately on the machine. Am I supposed to do something like that ?
I can paste the yml files but I havent made any change in this.
api_1            | 2019/04/29 10:54:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:33 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
api_1            | 2019/04/29 10:54:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:36 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:38 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:39 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:40 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:41 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
duckling_1       | no port specified, defaulting to port 8000
api_1            | 2019/04/29 10:54:42 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:43 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:44 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:45 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:46 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:47 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:54:35,979][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:
elasticsearch_1  |   /usr/share/elasticsearch/config/log4j2.properties
elasticsearch_1  | [2019-04-29T10:54:51,513][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/c/Users)
]], net usable_space [27.3gb], net total_space [162.3gb], types [vboxsf]
elasticsearch_1  | [2019-04-29T10:54:51,514][INFO ][o.e.e.NodeEnvironment    ] [Fy-UkXS] heap size [503.6mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2019-04-29T10:54:51,546][INFO ][o.e.n.Node               ] [Fy-UkXS] node name derived from node ID [Fy-UkXS_QPuGSsULTNsO-A]; set [node.name
] to override
elasticsearch_1  | [2019-04-29T10:54:51,547][INFO ][o.e.n.Node               ] [Fy-UkXS] version[6.5.1], pid[1], build[default/tar/8c58350/2018-11-16T02:22:42.1
82257Z], OS[Linux/4.14.111-boot2docker/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/11.0.1/11.0.1+13]
api_1            | 2019/04/29 10:54:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:54 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:55 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
rasa_1           | 2019-04-29 10:54:56+0000 [-] Log opened.
rasa_1           | 2019-04-29 10:54:56+0000 [-] Site starting on 5000
api_1            | 2019/04/29 10:54:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:54:59 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:54:51,548][INFO ][o.e.n.Node               ] [Fy-UkXS] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiati
ngOccupancyFraction=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.shutdownHookEnab
led=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.pjnKWUi6, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/h
s_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, -De
s.cgroups.hierarchy.override=/, -Xms512m, -Xmx512m, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.f
lavor=default, -Des.distribution.type=tar]
elasticsearch_1  | [2019-04-29T10:55:05,810][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2019-04-29T10:55:05,814][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [analysis-common]
elasticsearch_1  | [2019-04-29T10:55:05,819][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [ingest-common]
elasticsearch_1  | [2019-04-29T10:55:05,820][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-expression]
elasticsearch_1  | [2019-04-29T10:55:05,822][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-mustache]
elasticsearch_1  | [2019-04-29T10:55:05,825][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [lang-painless]
elasticsearch_1  | [2019-04-29T10:55:05,831][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [mapper-extras]
elasticsearch_1  | [2019-04-29T10:55:05,834][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [parent-join]
elasticsearch_1  | [2019-04-29T10:55:05,839][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [percolator]
elasticsearch_1  | [2019-04-29T10:55:05,852][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [rank-eval]
elasticsearch_1  | [2019-04-29T10:55:05,862][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [reindex]
elasticsearch_1  | [2019-04-29T10:55:05,868][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [repository-url]
elasticsearch_1  | [2019-04-29T10:55:05,872][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [transport-netty4]
elasticsearch_1  | [2019-04-29T10:55:05,877][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [tribe]
elasticsearch_1  | [2019-04-29T10:55:05,879][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ccr]
elasticsearch_1  | [2019-04-29T10:55:05,881][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-core]
elasticsearch_1  | [2019-04-29T10:55:05,883][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-deprecation]
elasticsearch_1  | [2019-04-29T10:55:05,884][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-graph]
elasticsearch_1  | [2019-04-29T10:55:05,889][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-logstash]
elasticsearch_1  | [2019-04-29T10:55:05,890][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-ml]
elasticsearch_1  | [2019-04-29T10:55:05,891][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-monitoring]
elasticsearch_1  | [2019-04-29T10:55:05,891][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-rollup]
elasticsearch_1  | [2019-04-29T10:55:05,892][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-security]
elasticsearch_1  | [2019-04-29T10:55:05,893][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-sql]
elasticsearch_1  | [2019-04-29T10:55:05,894][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-upgrade]
elasticsearch_1  | [2019-04-29T10:55:05,895][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded module [x-pack-watcher]
elasticsearch_1  | [2019-04-29T10:55:05,896][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded plugin [ingest-geoip]
api_1            | 2019/04/29 10:55:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:08 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:17 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:21 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:55:05,899][INFO ][o.e.p.PluginsService     ] [Fy-UkXS] loaded plugin [ingest-user-agent]
api_1            | 2019/04/29 10:55:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:31 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:36 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:55:30,131][INFO ][o.e.d.DiscoveryModule    ] [Fy-UkXS] using discovery type [single-node] and host providers [settings]
elasticsearch_1  | [2019-04-29T10:55:37,622][INFO ][o.e.n.Node               ] [Fy-UkXS] initialized
api_1            | 2019/04/29 10:55:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:38 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:55:37,628][INFO ][o.e.n.Node               ] [Fy-UkXS] starting ...
elasticsearch_1  | [2019-04-29T10:55:39,881][INFO ][o.e.t.TransportService   ] [Fy-UkXS] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
api_1            | 2019/04/29 10:55:39 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:55:40,325][WARN ][o.e.b.BootstrapChecks    ] [Fy-UkXS] max virtual memory areas vm.max_map_count [65530] is too low, increase
to at least [262144]
api_1            | 2019/04/29 10:55:40 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:42 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
elasticsearch_1  | [2019-04-29T10:55:41,659][INFO ][o.e.h.n.Netty4HttpServerTransport] [Fy-UkXS] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9
00}
elasticsearch_1  | [2019-04-29T10:55:41,669][INFO ][o.e.n.Node               ] [Fy-UkXS] started
elasticsearch_1  | [2019-04-29T10:55:43,640][INFO ][o.e.l.LicenseService     ] [Fy-UkXS] license [fc8bce5b-3406-4b94-9c27-6d5893e56a4d] mode [basic] - valid
api_1            | 2019/04/29 10:55:43 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:44 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:45 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:46 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:54 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:55 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:56 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:57 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:55:58 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:00 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:01 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:02 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:03 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:04 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:05 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:06 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:07 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:09 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:10 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:11 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:12 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:13 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:14 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:15 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:16 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:18 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:19 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:20 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:21 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:22 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:23 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:24 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:25 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:26 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:27 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:28 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:29 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:30 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:32 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:56:33 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:34 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:35 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:36 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:37 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:39 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:40 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:41 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:42 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:43 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:44 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:45 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:46 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:48 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:49 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:50 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:51 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:52 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:53 Problem with request: Get http://elasticsearch:9200: dial tcp <IP_ADDRESS>:9200: connect: connection refused. Sleeping 1s
api_1            | 2019/04/29 10:58:54 Timeout after 5m0s waiting on dependencies to become available: [http://elasticsearch:9200]
articulate-v0212_api_1 exited with code 1

hmm, okay. I've got to try an figure out a way to test. This is likely a Docker Toolbox issue. I will try to work on it today.
No, you shouldn't have to install Elasticsearch. The compose file should bring it all up at once.

What is the output of docker-compose ps?

Please see below the outpout from docker-compose ps.
Is there some thing to do with less memory .
I am on a 8GB 64 Bit Windows 7 professional
C:\Users\ss00346355\Desktop\articulate-v0.21.2>docker-compose ps
The system cannot find the path specified.
Name                            Command               State                Ports
articulate-v0212_api_1             /bin/sh -c dockerize -wait ...   Up      <IP_ADDRESS>:7500->7500/tcp
articulate-v0212_duckling_1        /bin/sh -c stack exec duck ...   Up      <IP_ADDRESS>:8000->8000/tcp
articulate-v0212_elasticsearch_1   /usr/local/bin/docker-entr ...   Up      <IP_ADDRESS>:9200->9200/tcp, 9300/tcp
articulate-v0212_rasa_1            ./entrypoint.sh start --pa ...   Up      <IP_ADDRESS>:5000->5000/tcp
articulate-v0212_redis_1           docker-entrypoint.sh redis ...   Up      <IP_ADDRESS>:6379->6379/tcp
articulate-v0212_ui_1              yarn start:prod                  Up      <IP_ADDRESS>:3000->3000/tcp

What do you get if you go to localhost:3000 or {your docker IP}:3000
It's very wierd that it says everything is up, but the code from above says the API had exited.

Hi
I just looked at it and found this.
localhost:3000 says : The site cannot be reached
On doing the docker IP based (IP that shows at the start of docker) : http://<IP_ADDRESS>:3000 the articulate opens with missing api
On using the IP of the container: docker inspect  | grep "IPAddress", it says the site cannot be reached.

Can you try with the 0.22 release? We've changed how the network is configured I am curious if it works any better. Make sure to docker-compose down in your current directory first.

Hi .. I tried running 0.22 . It is no better
The same elasticsearch error kept coming till 5 minutes and then the below error started popping.
Also, whatever missing-api web page was coming with 0.21.2 also stopped coming with 0.22 showing The page isn't working ..weird :-(
elasticsearch_1  | [2019-04-30T05:35:18,857][INFO ][o.e.c.r.a.DiskThresholdMonitor] [g6WXLGL] low disk watermark [85%] exceeded on [g6WXLGLbSN64U0Exe_mfiw][g6WX
LGL][/usr/share/elasticsearch/data/nodes/0] free: 22.8gb[14%], replicas will not be assigned to this node
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }

@earthonclouds sorry I lost track of this one, ever get it?

I am experiencing the same/similar error "WS] Error http://api:7500" . oddly enough, i did NOT experience this issue yesterday when i used v0.22 for the first time. today, i downloaded a fresh copy of the latest version and this error popped up. i did do a docker-compose down and it did not resolve the issue
elasticsearch_1  | [2019-06-11T18:07:30,986][INFO ][o.e.c.r.a.DiskThresholdMonitor] [eJ7JSmm] low disk watermark [85%] exceeded on [eJ7JSmm7S2GEsq6GExQ-HQ][eJ7JSmm][/usr/share/elasticsearch/data/nodes/0] free: 15.7gb[13.9%], replicas will not be assigned to this node
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Disconnect from http://api:7500
ui_1             | { code: undefined,
ui_1             |   explanation: 'Unknown',
ui_1             |   reason: undefined,
ui_1             |   wasClean: undefined,
ui_1             |   willReconnect: true,
ui_1             |   wasRequested: false }
ui_1             | [WS] Will Reconnect = true
ui_1             | [WS] Error http://api:7500
ui_1             | Error: Connection terminated while waiting to connect
ui_1             | [WS] Error http://api:7500
localhost:3000 shows nothing, localhost:7500/documentation shows nothing.

Running the following commands to clean up docker containers and images seems to fix the issue !


Make vkFrameBoundaryANDROID trigger screenshots

This commit is part of what is requested in #1494

CI gfxreconstruct build queued with queue ID 168788.

CI gfxreconstruct build # 4013 running.

CI gfxreconstruct build queued with queue ID 168811.

CI gfxreconstruct build # 4014 running.

CI gfxreconstruct build # 4014 passed.

CI gfxreconstruct build queued with queue ID 169478.

CI gfxreconstruct build # 4023 running.

@panos-lunarg @locke-lunarg could you take a look at this PR, please?  It would be helpful to merge for other sponsors so we should prioritize it.  Thank you!

These code is duplicated with VulkanReplayConsumerBase::WriteScreenshots. It will be better if it has a function for these two cases.

Some thoughts on vkFrameBoundaryANDROID and virtual swapchains:
VulkanReplayConsumerBase::WriteScreenshots takes the image information from the SwapchainKHRInfo which should take care of virtual swapchains.
On the other hand vkFrameBoundaryANDROID takes as a direct argument a handle to the VkImage that's going to be presented/swapped. I assume that the image handles are acquired through vkGetSwapchainImagesKHR which takes care of virtual swapchains. So it should be fine.
@locke-lunarg : does this sound correct to you?

I'm not sure if the image on vkFrameBoundaryANDROID is from vkGetSwapchainImagesKHR. My option is quit simple that it could have a function, like  VulkanReplayConsumerBase::WriteScreenshots(ImageInfo* image_info).
And then
VulkanReplayConsumerBase::WriteScreenshots(const Decoded_VkPresentInfoKHR* meta_info)
{
   ...
          WriteScreenshots(image_info);
   ...
}

VulkanReplayConsumerBase::OverrideFrameBoundaryANDROID(....)
{
   ...
          WriteScreenshots(image_info);
   ...
}

I'm not sure if the image on vkFrameBoundaryANDROID is from vkGetSwapchainImagesKHR. My option is quit simple that it could have a function, like VulkanReplayConsumerBase::WriteScreenshots(ImageInfo* image_info).

Yes, I agree with this suggestion.
Basically my question was about whether this change is compatible with virtual swapchain. As far as I can tell I think it is.

Yes, I agree with this suggestion. Basically my question was about whether this change is compatible with virtual swapchain. As far as I can tell I think it is.

Good point. For virtual swapchain, GetSwapchainImagesKHR return virtual swapchain images, not real swapchain images, so vkFrameBoundaryANDROID would use virtual swapchain images to output image, instead of real swapchain images. But virtual swapchain images and real swapchain images are the same, so it's not a problem.

I'm not sure if the image on vkFrameBoundaryANDROID is from vkGetSwapchainImagesKHR. My option is quit simple that it could have a function, like VulkanReplayConsumerBase::WriteScreenshots(ImageInfo* image_info).
And then
VulkanReplayConsumerBase::WriteScreenshots(const Decoded_VkPresentInfoKHR* meta_info)
{
   ...
          WriteScreenshots(image_info);
   ...
}

VulkanReplayConsumerBase::OverrideFrameBoundaryANDROID(....)
{
   ...
          WriteScreenshots(image_info);
   ...
}

to avoid the duplicated code.

Sure the duplication is ugly, but the only code "really" duplicated here is the computation of the screenshot size. I cannot create the proposed function simply because there is no image_info accessible from the swapchain, only a vector of VkImage.
All the code that could be factorized was factorized in WriteImage

Sorry. That's a wrong click.

CI gfxreconstruct build # 4230 running.

CI gfxreconstruct build # 4230 passed.

@marius-pelegrin-arm  Please solve the conflict, and then it's good to merge.

CI gfxreconstruct build queued with queue ID 198014.

Hi, @locke-lunarg ! I resolved a conflict but that wasn't sufficient; there are compile errors. Will you check out Marius' branch and see if the fix is obvious?

Never mind, I think I see the issue.

CI gfxreconstruct build queued with queue ID 198040.

CI gfxreconstruct build # 4257 running.

CI gfxreconstruct build # 4257 passed.


[Sticky] Sticky Container not Re-flowing on Resize

How can we reproduce this bug?

Step one - Visit this page: http://foundation.zurb.com/sites/docs/sticky.html
Step two - Resize the browser (1300 seems to be consistent)
Step three - Scroll down to "Advanced"
Step four - Scroll up and down repeatedly

What did you expect to happen?
I expected the sticky elements to reflow without overlapping.
What happened instead?
The Orbit photo overlaps the text above it.
NOTE - This happens intermittently.
Give us a link to a CodePen or JSFiddle that recreates the issue.
N/A this issue is recreated on the doc page here: http://foundation.zurb.com/sites/docs/sticky.html

CodePen with Foundation 6 and MotionUI
CodePen with Foundation 6, Flexbox grid and MotionUI

Hi there,  Just checking if this ticket is now stable. Looks like it was closed then reopened. :(

@merlihan Did #8715 take care of this?

@andycochran Yes, it did!  Thank you!


Consider a twitter ID to mastodon handle map

This would replace @mentions on Twitter with correct Mastodon handle references on the toot.
Another idea: re-process old toots to see if the text changes (i.e., if a new mapping has applied) and edit them if so.

Username rewriting done in e525e96351089199a0139c4777c6d7dff482a29d

Edits may be performed if toot mapping changes in f0e0d146547b1f2733c7a6543e6e7f846e80317e

67f6b5b566ee56d9f429be6a6cfe06618a1c754b