Fixed BindingManager to make sure it doesn't use invalid context

Problem
BindingManager uses application context passed to
NotifyBoundClusterChanged and doesn't care about its life time.
Applications delete the context after calling the method, so if
the context will be used asynchronously (like for HandleDeviceConnect)
it may have invalid value.
Change overview

Added for BindingManager method that allows to register handler
called when context is not used anymore and can be released.
Added releasing context in applications using context release
handler.

Testing
Tested manually with nrfconnect light switch app and chiptool.

/rebase

@bzbarsky-apple thank you for hints and very helpful review.


[new-product] meilisearch

MR for issue: https://github.com/endoflife-date/endoflife.date/issues/3803

Overall LGTM, thanks a lot @andre-m-dev.
There is a few things to fix (some dates are wrong, EOL dates are not set...), but I cannot modify the PR. So will merge and fix in a follow-up PR.

@marcwrobel thank you for your patience and cooperation


Fail fast Kafka Schema Registry on unsupported format

Fail fast Kafka Schema Registry on unsupported format

Depends on: https://github.com/prestosql/presto/pull/6411

@Praveen2112 @skrzypo987 Please take a look.


Rate limiting on paid plans is unacceptable

Type: Bug
I'm not hitting it very hard, just doing some iterative tailwind styling changes, and got this message
Sorry, your request was rate-limited. Please wait 4 minutes before trying again.
What are we paying for? Paid-for Cursor doesn't have this issue.
Extension version: 0.22.2
VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.26100
Modes:

I should not be limited if paying.


adi

call witness for statement
Recommendation-3.pdf

fdf
df

[ ] then do this

tah #15
@jora

Seems like spam. Closing.


\global \newcommand that persist across render / renderToString calls

On KaTeX 0.10.2 the commented line below would fail:
#!/usr/bin/env nodejs
var katex = require('katex')
macros = {}
console.log(katex.renderToString("\\gdef\\foo{myfoo}", {macros: macros, throwOnError: true}));
console.log(katex.renderToString("\\foo", {macros: macros, throwOnError: true}));
console.log(katex.renderToString("\\newcommand{\\baz}[0]{mybaz}", {macros: macros, throwOnError: true}));
//console.log(katex.renderToString("\\baz", {macros: macros, throwOnError: true}));
console.log(katex.renderToString("\\newcommand{\\baz}[0]{mybaz}\n\\baz", {macros: macros, throwOnError: true}));
console.log(macros)

with error:
/home/ciro/test/node_modules/katex/dist/katex.js:16668
    throw error;
    ^

ParseError: KaTeX parse error: Undefined control sequence: \baz at position 1: \̲b̲a̲z̲
    at new ParseError (/home/ciro/test/node_modules/katex/dist/katex.js:261:14)
    at Parser.parseGroup (/home/ciro/test/node_modules/katex/dist/katex.js:16326:17)
    at Parser.parseAtom (/home/ciro/test/node_modules/katex/dist/katex.js:15789:21)
    at Parser.parseExpression (/home/ciro/test/node_modules/katex/dist/katex.js:15650:23)
    at Parser.parse (/home/ciro/test/node_modules/katex/dist/katex.js:15618:22)
    at parseTree (/home/ciro/test/node_modules/katex/dist/katex.js:16579:21)
    at renderToDomTree (/home/ciro/test/node_modules/katex/dist/katex.js:16686:16)
    at Object.renderToString (/home/ciro/test/node_modules/katex/dist/katex.js:16647:16)
    at Object.<anonymous> (/home/ciro/test/main.js:7:19)
    at Module._compile (internal/modules/cjs/loader.js:689:30)

I know about \global\def and \gdef, but \newcommand is much more common.
I've seen the discussion at: https://github.com/KaTeX/KaTeX/pull/1382#issuecomment-396804705 but decided to create a new issue to better focus on the problem.
There is some LaTeX talk about this at: https://groups.google.com/forum/#!topic/comp.text.tex/rm__irFVbuw but I don't mind if we follow LaTeX or not here, e.g. why not either:

make every definition persist across blocks by default and get rid of \global. Why isn't that the default behavior?
invent a new \gnewcomand

My motivation for this is that I'm integrating Asciidoctor with KaTeX to achieve HTML Math Nirvana: https://github.com/asciidoctor/asciidoctor/pull/3338
But so far this feature alone makes me want to fall back on MathJax I think :-(

Our general goal in KaTeX is compatibility with LaTeX.  Sadly, LaTeX doesn't have a global form of \newcommand, and creates a group for every math mode, which is why we're in the current state.
I could a few possible ways to improve the situation:

We could add a render option called something like globalGroup which runs the expression in the global group, instead of creating a math group like LaTeX does.  This could be used specifically for blocks that define macros, or could be set on all blocks to simulate MathJax behavior.
Perhaps we could define something like a \begin{macros}...\end{macros} environment via #2042 that would automatically happen in the global group.  I'm not sure how that would be done in LaTeX though, as \begin always creates a group...
As you suggest, we could make something like \gnewcommand or \global\newcommand, and perhaps add it to the hypothetical katex.sty (#793).  It would be great if there were any precedent for the name of such a command...

Thoughts on which one(s) would be best?

Erik,
Option 1 sound great to me! As you say, I would just enable it on every block to replicate MathJax.
About the macro definition on API, I was aware of that and I'm already using it to propagate \def macros across asciidoctor math blocks.
But it would be awesome if you could explain at macros section in https://katex.org/docs/options.html how to implement macros with arguments (there is a link to source, but it takes some time for my brain to parse that :-)) I would give an example:

Each macro is a property with a name like \name (written "\name" in JavaScript) which maps to a string that describes the expansion of the macro, or a function that accepts an instance of MacroExpander as first argument and returns the expansion as a string.

For example, to define a macro that takes two arguments you can use:

"\\foo": "my #1 favorite #2 foo"

where the number of parameters is deduced from the #1, #2, etc. in the expansion itself.

This would have saved 30 minutes of my life :-)

How do you develop this package? yarn build && nodejs mytest.js with var katex = require('.') in mytest.js works but takes a while in the yarn build, any way to speed that up?

@cirosantilli require('katex') might work without building.

require('katex') gives:
internal/modules/cjs/loader.js:583
    throw err;
    ^

Error: Cannot find module 'katex'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
    at Function.Module._load (internal/modules/cjs/loader.js:507:25)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)
    at Object.<anonymous> (/home/ciro/git/KaTeX/main.js:3:13)
    at Module._compile (internal/modules/cjs/loader.js:689:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)

and var katex = require('./katex.js') gives:
/home/ciro/git/KaTeX/katex.js:11
import ParseError from "./src/ParseError";
       ^^^^^^^^^^

SyntaxError: Unexpected identifier
    at new Script (vm.js:79:7)
    at createScript (vm.js:251:10)
    at Object.runInThisContext (vm.js:303:10)
    at Module._compile (internal/modules/cjs/loader.js:657:28)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:700:10)
    at Module.load (internal/modules/cjs/loader.js:599:32)
    at tryModuleLoad (internal/modules/cjs/loader.js:538:12)
    at Function.Module._load (internal/modules/cjs/loader.js:530:3)
    at Module.require (internal/modules/cjs/loader.js:637:17)
    at require (internal/modules/cjs/helpers.js:22:18)

You would need to enable Node's support for import (a command-line option in Node 12). Obviously untested...
If you're looking to write tests, it'd be better to add them directly to the Jest tests. These run (via yarn test:jest) withour buiilding. Also there's a tool for interactive experimentation via yarn start; that's how I usually develop. It autobuilds as you change source files.


Fix  dep vulnerability check action

closes #39

:tada: This PR is included in version 1.0.0-dev.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Removing all tags throws error

❯ t 11 mod size: -phys
Modifying task 11 'Reparatur VICE'.
Traceback (most recent call last):
  File "/home/janek/.local/share/task/hooks/on-modify-pirate", line 48, in <module>
    print(task.export_data())
  File "/usr/local/lib/python3.8/dist-packages/tasklib/task.py", line 125, in export_data
    data = dict(data_tuples)
  File "/usr/local/lib/python3.8/dist-packages/tasklib/task.py", line 119, in <genexpr>
    data_tuples = ((key, self._serialize(key, value))
  File "/usr/local/lib/python3.8/dist-packages/tasklib/serializing.py", line 52, in _serialize
    return dehydrate_func(value)
  File "/usr/local/lib/python3.8/dist-packages/tasklib/serializing.py", line 176, in serialize_tags
    return list(tags)
TypeError: 'NoneType' object is not iterable
Hook Error: Expected feedback from a failing hook script.

oops, that was an error in my fork. Fixed anyways.


ParticlesMaterial in Particles2D can't have different parameters

Godot version
v4.0.stable.official [92bee43ad]
System information
Windows 10, Geforce GTX 1660, NForward+
Issue description
I've made a simple class that instantiates a scene with a GPUParticle2D inside, to make a simple firework.
The idea is to have multiple fireworks, updating the process_material.color before adding to the scene to have each one with a different color.
The issue is that the material color seems shared between the three instances, having the last one to prevail.
I also apply a different scale to the GPUParticle2D, and in this case it works correctly. The material seem to be the problem.
Steps to reproduce
This is the function to add a new firework:
func add(container:Node, type:String, pos:Vector2, scale:float, color:Color):
	var new_one = load("res://" + type + ".tscn").instantiate()
	new_one.get_node("fx").scale = Vector2(scale, scale)
	new_one.get_node("fx").process_material.color = color
	new_one.position = pos
	container.add_child(new_one)

Then adding multiple fireworks with different color:
	Sparks.add(self, "fx3", Vector2(200,400), 1, Color.RED)
	Sparks.add(self, "fx3", Vector2(500,400), 2, Color.GREEN)
	Sparks.add(self, "fx3", Vector2(800,400), 3, Color.BLUE)`

Will show all three fireworks with the same color of the latest added (blue in this case)
Minimal reproduction project
Here is the Godot 4.0 test project:
ParticlesTest.zip
Thank you.

Resources are shared by default. Enable local_to_scene in your particles material to make it unique for each scene instance.


VCU-35: Configurable SHA Signing Algorithm - V2

Solo: @dbes-gds
Update the MSA to sign with SHA256 by default.
Configuration option provided to revert to SHA1 if required.

We've made the changes requested by Paula, and now everything was either done as a pair or has been reviewed by me, so I'm going to merge.


Optimize all the images

Mostly used results from image lint and try to optimize.

There are still some images unoptimized. I would love to add a small lint for Image that makes sure we use both widths and sizes


Experiment RigidBody Implementation of vehicle

Experiment RigidBody Implementation of vehicle as in following
https://kidscancode.org/godot_recipes/3d/3d_sphere_car/
to enable more "arcade" (i.e. sliding etc) behavior

Latest change is in with initial implementation.
However, it is quite unstable now (there are bumbing behavior when testing, and sometime will fly into mid air).
Even though kinematic vehicle also has unexpected bump time to time, but this is much more unstable.
So use an experimental checkbox under settings to enable it if interested

With the change in main, the spatial vheicle implementation is now the default.
The solution to bumpy behavior is slightly improved by switching from Default physics engine (Bullet) to Godot Physics

Workaround the godot bumpy behavior with moving on trimesh by:

Switching to Godot physics - improve the situation, but not fully resolved as mentioned in here:
https://github.com/godotengine/godot/issues/21341
https://github.com/godotengine/godot/issues/50463

Instead of a trimesh ground, use a box collision shape (the CollisionShape -> Box Shape) with staticbody instead of the generated trimesh from the actual ground -> THIS SEEM TO SOLVE ALL BUMPY BEHAVIOR
The wall will need to be separated mesh and use trimesh for accuracy. But the vehicle no longer bumpy during move.


Fork, Commit, Merge - Easy Issue (HTML)

Fork, Commit, Merge - Easy Issue (HTML)
Add Simple H1-tag
Note: You don't have ask permission to start solving the issue or get assigned, since these issues are supposed to be always open for new contributors. The actions-user bot will reset the file back to previous state for the next contributor after your commit is merged. So you can just simply start working with the issue right away!
Open the tasks/html/easy directory from the root of your project.
Your task is to insert an h1 tag with the name John Doe above the h2 tag in the index.html file.
Note: Only the index.html file needs modification for this task.

Check out README.md for more instructions and how to make a pull request.
Feel free to ask any questions here if you have some problems!
Also, kindly give this project a star to enhance its visibility for new developers!

please assign it to me sir.


Minor cleanup of windows build script and venv configuration

This is helpful. Add the usage of the configure_venv.bat to README.rst.

Add a windows batch file file and this is good to go.


ImportError with create_app.py

Description of problem
Hello,
I installed spyder 3.0.0 on macOS Sierra 10.12 with pip. Spyder start's from terminal fine.
I want to add Spyder to launchpad. So I tried to create app file for adding them to Applications.
I run create_app.py and got an error
Air-Oleg:spyder-3.0.0 xxblx$ python3 create_app.py py2app
Traceback (most recent call last):
  File "create_app.py", line 30, in <module>
    from spyder.config.main import EDIT_EXT
ImportError: cannot import name 'EDIT_EXT'

Steps to reproduce

Download spyder-3.0.0 sources
python3 setup.py build
python3 create_app.py py2app

Versions and main components

spyder 3.0.0

macOS Sierra 10.12

Python 3.5.2 from Anaconda bundle

py2app 0.10

Dependencies
jedi >=0.8.1     :  0.9.0 (OK)
matplotlib >=1.0 :  1.5.3 (OK)
nbconvert >=4.0  :  4.2.0 (OK)
numpy >=1.7      :  1.11.1 (OK)
pandas >=0.13.1  :  0.18.1 (OK)
pep8 >=0.6       :  1.7.0 (OK)
psutil >=0.3     :  4.3.0 (OK)
pyflakes >=0.6.0 :  1.2.3 (OK)
pygments >=2.0   :  2.1.3 (OK)
pylint >=0.25    :  1.6.4 (OK)
qtconsole >=4.2.0:  4.2.1 (OK)
rope >=0.9.4     :  0.9.4-1 (OK)
sphinx >=0.6.6   :  1.4.1 (OK)
sympy >=0.7.3    :  1.0 (OK)

I have the same issue on mac os 10.11, other configurations are the same.

I haven't had time to update create_app.py, that's why it's broken.
However, the process to create our apps is a lot more than just running python create_app.py py2app. If you really want to do this yourselves, please follow the instructions present in:
https://github.com/spyder-ide/mac-application


New Ubuntu icon is small

Tested with Ubuntu 15.04:
MediaConch 15.11:

MediaConch 15.12:

The expected behavior is the one from 15.11 (same size as other icons)
Note: reboot after each install, else the icon is the one cached by the operating system.

Done for next snapshots/releases...
https://github.com/MediaArea/MediaConch_SourceCode/pull/130


Disabling Keycloak Causes NPE

Disabling Keycloak functionality using the KEYCLOAK_ENABLED environment variable has no effect other than a NullPointerException on endpoints that require principal information.
This requires a decision on an architectural level since user information is mandatory. In the past, disabling Keycloak has been reserved for development purposes anyway. Thus, dropping this switch altogether seems to be reasonable.

not relevant anymore as keycloak cannot be disabled anymore


Bursts of interlinking notes should present as one combined feed item

These will be noisy and they tell a more interesting story if presented together. Could use a horizontally scrollable list of transcludes so you can scrub through.
I often create a burst of notes by branching off entities or mentions in an initial thought.

This is probably an out-of-date idea but there is still merit to detecting notes created within a few minutes of one another.


Write chapter to analyze what a quantum safe / emergency quantum break fork might look like

i think it'd be interesting to analyze all the various flavors (surprise vs. heads up) of a QC event as well as different tactics for handling it and transitioning, including the philosophical question of what to do with vulnerable coins, and what to do about mining if 1 entity can dominate.

I don't know if there are any individuals or ASIC manufacturing companies that are interested in or have already experimented with this yet. And where can we check or verify this information from reliable sources?
Or are there any points/sections in the Bitcoin Core code that have already been prepared or implemented to support and address this potential quantum computing problem?

My intention here is more about analysis of how a consensus change could play out vs. specific technical solutions.


docker-elk_logstash_1 exited with code 1

I'm trying to pass syslogs to elasticsearch through logstash.I'm using the dckerized version of ELK stack.The default image runs with no error.However when i use logstash-input-file to give path of /var/log/*log and syslog i get the error mentioned.I did mount the /var/log dir to logstash container in docker-compose.yml.Please note that behind a firewall so do let me know if i have to make any proxy changes. The logatash container doesnt provide any error.I have tried all the previously mentioned solutions also.
Primarily i used this site for reference
https://logz.io/blog/elk-stack-on-docker/
root@debian:/home/arup123/docker-elk# docker-compose down
Removing docker-elk_logstash_1      ... done
Removing docker-elk_kibana_1        ... done
Removing docker-elk_elasticsearch_1 ... done
Removing network docker-elk_elk
root@debian:/home/arup123/docker-elk# docker-compose up --build
Creating network "docker-elk_elk" with driver "bridge"
Building elasticsearch
Step 1/1 : FROM docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.0
---> 345a3630eed8
Successfully built 345a3630eed8
Successfully tagged docker-elk_elasticsearch:latest
Building logstash
Step 1/7 : FROM docker.elastic.co/logstash/logstash-oss:6.3.0
---> 77bdbc2dc566
Step 2/7 : ENV HTTP_PROXY http://<IP_ADDRESS>:9400
---> Using cache
---> 216e4e0a4550
Step 3/7 : ENV HTTPS_PROXY http://<IP_ADDRESS>:9400
---> Using cache
---> 85145b489156
Step 4/7 : RUN export http_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 76d517e946df
Step 5/7 : RUN export https_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 15badd9d5a39
Step 6/7 : RUN export ftp_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 63cd43f41889
Step 7/7 : RUN export no_proxy="localhost,<IP_ADDRESS>"
---> Using cache
---> caa5a13cab97
Successfully built caa5a13cab97
Successfully tagged docker-elk_logstash:latest
Building kibana
Step 1/1 : FROM docker.elastic.co/kibana/kibana-oss:6.3.0
---> 135bf752e257
Successfully built 135bf752e257
Successfully tagged docker-elk_kibana:latest
Creating docker-elk_elasticsearch_1 ... done
Creating docker-elk_kibana_1        ... done
Creating docker-elk_logstash_1      ... done
Attaching to docker-elk_elasticsearch_1, docker-elk_kibana_1, docker-elk_logstash_1
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.
logstash_1       | OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:16Z","tags":["status","plugin:kibana@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:16Z","tags":["status","plugin:elasticsearch@6.3.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["status","plugin:timelion@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["status","plugin:console@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["status","plugin:metrics@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0:5601"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["error","elasticsearch","admin"],"pid":1,"message":"Request error, retrying\nHEAD http://elasticsearch:9200/ => connect ECONNREFUSED <IP_ADDRESS>:9200"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:17Z","tags":["status","plugin:elasticsearch@6.3.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - Unable to connect to Elasticsearch at http://elasticsearch:9200.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
elasticsearch_1  | [2018-07-10T08:33:19,607][INFO ][o.e.n.Node               ] [] initializing ...
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:19Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:19Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:33:20,101][INFO ][o.e.e.NodeEnvironment    ] [4k93D1D] using [1] data paths, mounts [[/ (overlay)]], net usable_space [8.1gb], net total_space [18.2gb], types [overlay]
elasticsearch_1  | [2018-07-10T08:33:20,104][INFO ][o.e.e.NodeEnvironment    ] [4k93D1D] heap size [1015.6mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2018-07-10T08:33:20,110][INFO ][o.e.n.Node               ] [4k93D1D] node name derived from node ID [4k93D1D_Q-uHM2Lt9oUxKg]; set [node.name] to override
elasticsearch_1  | [2018-07-10T08:33:20,113][INFO ][o.e.n.Node               ] [4k93D1D] version[6.3.0], pid[1], build[oss/tar/424e937/2018-06-11T23:38:03.357887Z], OS[Linux/4.9.0-6-amd64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/10.0.1/10.0.1+10]
elasticsearch_1  | [2018-07-10T08:33:20,125][INFO ][o.e.n.Node               ] [4k93D1D] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.q9ZeaQof, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.locale.providers=COMPAT, -Des.cgroups.hierarchy.override=/, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.flavor=oss, -Des.distribution.type=tar]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:22Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:22Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:24Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:24Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:33:25,405][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2018-07-10T08:33:25,412][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [analysis-common]
elasticsearch_1  | [2018-07-10T08:33:25,412][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [ingest-common]
elasticsearch_1  | [2018-07-10T08:33:25,413][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [lang-expression]
elasticsearch_1  | [2018-07-10T08:33:25,413][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [lang-mustache]
elasticsearch_1  | [2018-07-10T08:33:25,413][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [lang-painless]
elasticsearch_1  | [2018-07-10T08:33:25,414][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [mapper-extras]
elasticsearch_1  | [2018-07-10T08:33:25,414][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [parent-join]
elasticsearch_1  | [2018-07-10T08:33:25,414][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [percolator]
elasticsearch_1  | [2018-07-10T08:33:25,414][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [rank-eval]
elasticsearch_1  | [2018-07-10T08:33:25,415][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [reindex]
elasticsearch_1  | [2018-07-10T08:33:25,419][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [repository-url]
elasticsearch_1  | [2018-07-10T08:33:25,420][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [transport-netty4]
elasticsearch_1  | [2018-07-10T08:33:25,421][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded module [tribe]
elasticsearch_1  | [2018-07-10T08:33:25,422][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded plugin [ingest-geoip]
elasticsearch_1  | [2018-07-10T08:33:25,422][INFO ][o.e.p.PluginsService     ] [4k93D1D] loaded plugin [ingest-user-agent]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:27Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:27Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:29Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:29Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:32Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:32Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:34Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:34Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:37Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:37Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:33:39,194][INFO ][o.e.d.DiscoveryModule    ] [4k93D1D] using discovery type [single-node]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:39Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:39Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:33:41,744][INFO ][o.e.n.Node               ] [4k93D1D] initialized
elasticsearch_1  | [2018-07-10T08:33:41,762][INFO ][o.e.n.Node               ] [4k93D1D] starting ...
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:42Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:42Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:33:42,573][INFO ][o.e.t.TransportService   ] [4k93D1D] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
elasticsearch_1  | [2018-07-10T08:33:42,813][INFO ][o.e.h.n.Netty4HttpServerTransport] [4k93D1D] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
elasticsearch_1  | [2018-07-10T08:33:42,814][INFO ][o.e.n.Node               ] [4k93D1D] started
elasticsearch_1  | [2018-07-10T08:33:43,006][INFO ][o.e.g.GatewayService     ] [4k93D1D] recovered [0] indices into cluster_state
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:33:46Z","tags":["status","plugin:elasticsearch@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Unable to connect to Elasticsearch at http://elasticsearch:9200."}
docker-elk_logstash_1 exited with code 1
^CGracefully stopping... (press Ctrl+C again to force)
Stopping docker-elk_kibana_1        ... done
Stopping docker-elk_elasticsearch_1 ... done
root@debian:/home/arup123/docker-elk# /usr/share/logstash/bin/logstash-plugin install logstash-output-mongodb
Validating logstash-output-mongodb
Installing logstash-output-mongodb
Installation successful
root@debian:/home/arup123/docker-elk# gedit docker-compose.yml
(gedit:23956): GLib-GIO-CRITICAL **: g_dbus_proxy_new_sync: assertion 'G_IS_DBUS_CONNECTION (connection)' failed
(gedit:23956): GLib-GIO-CRITICAL **: g_dbus_proxy_get_name_owner: assertion 'G_IS_DBUS_PROXY (proxy)' failed
(gedit:23956): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
(gedit:23956): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
Error creating proxy: The connection is closed (g-io-error-quark, 18)
(gedit:23956): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
(gedit:23956): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
(gedit:23956): dconf-WARNING **: failed to commit changes to dconf: The connection is closed
** (gedit:23956): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-language not supported
** (gedit:23956): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported
** (gedit:23956): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported
(gedit:23956): dconf-WARNING *: failed to commit changes to dconf: The connection is closed
root@debian:/home/arup123/docker-elk# docker-compose down
Removing docker-elk_logstash_1      ... done
Removing docker-elk_kibana_1        ... done
Removing docker-elk_elasticsearch_1 ... done
Removing network docker-elk_elk
root@debian:/home/arup123/docker-elk# docker-compose up --buildCreating network "docker-elk_elk" with driver "bridge"
Building elasticsearch
Step 1/1 : FROM docker.elastic.co/elasticsearch/elasticsearch-oss:6.3.0
---> 345a3630eed8
Successfully built 345a3630eed8
Successfully tagged docker-elk_elasticsearch:latest
Building logstash
Step 1/7 : FROM docker.elastic.co/logstash/logstash-oss:6.3.0
---> 77bdbc2dc566
Step 2/7 : ENV HTTP_PROXY http://<IP_ADDRESS>:9400
---> Using cache
---> 216e4e0a4550
Step 3/7 : ENV HTTPS_PROXY http://<IP_ADDRESS>:9400
---> Using cache
---> 85145b489156
Step 4/7 : RUN export http_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 76d517e946df
Step 5/7 : RUN export https_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 15badd9d5a39
Step 6/7 : RUN export ftp_proxy=http://<IP_ADDRESS>:9400
---> Using cache
---> 63cd43f41889
Step 7/7 : RUN export no_proxy="localhost,<IP_ADDRESS>"
---> Using cache
---> caa5a13cab97
Successfully built caa5a13cab97
Successfully tagged docker-elk_logstash:latest
Building kibana
Step 1/1 : FROM docker.elastic.co/kibana/kibana-oss:6.3.0
---> 135bf752e257
Successfully built 135bf752e257
Successfully tagged docker-elk_kibana:latest
Creating docker-elk_elasticsearch_1 ... done
Creating docker-elk_kibana_1        ... done
Creating docker-elk_logstash_1      ... done
Attaching to docker-elk_elasticsearch_1, docker-elk_kibana_1, docker-elk_logstash_1
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.
logstash_1       | OpenJDK 64-Bit Server VM warning: If the number of processors is expected to increase from one, then you should configure the number of parallel GC threads appropriately using -XX:ParallelGCThreads=N
elasticsearch_1  | [2018-07-10T08:40:24,728][INFO ][o.e.n.Node               ] [] initializing ...
elasticsearch_1  | [2018-07-10T08:40:25,390][INFO ][o.e.e.NodeEnvironment    ] [ghCf0VW] using [1] data paths, mounts [[/ (overlay)]], net usable_space [8.1gb], net total_space [18.2gb], types [overlay]
elasticsearch_1  | [2018-07-10T08:40:25,392][INFO ][o.e.e.NodeEnvironment    ] [ghCf0VW] heap size [247.6mb], compressed ordinary object pointers [true]
elasticsearch_1  | [2018-07-10T08:40:25,406][INFO ][o.e.n.Node               ] [ghCf0VW] node name derived from node ID [ghCf0VWrTF672_q5Kwx2_w]; set [node.name] to override
elasticsearch_1  | [2018-07-10T08:40:25,418][INFO ][o.e.n.Node               ] [ghCf0VW] version[6.3.0], pid[1], build[oss/tar/424e937/2018-06-11T23:38:03.357887Z], OS[Linux/4.9.0-6-amd64/amd64], JVM[Oracle Corporation/OpenJDK 64-Bit Server VM/10.0.1/10.0.1+10]
elasticsearch_1  | [2018-07-10T08:40:25,418][INFO ][o.e.n.Node               ] [ghCf0VW] JVM arguments [-Xms1g, -Xmx1g, -XX:+UseConcMarkSweepGC, -XX:CMSInitiatingOccupancyFraction=75, -XX:+UseCMSInitiatingOccupancyOnly, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.io.tmpdir=/tmp/elasticsearch.z0Rf2x2Y, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=data, -XX:ErrorFile=logs/hs_err_pid%p.log, -Xlog:gc,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.locale.providers=COMPAT, -Des.cgroups.hierarchy.override=/, -Xmx256m, -Xms256m, -Des.path.home=/usr/share/elasticsearch, -Des.path.conf=/usr/share/elasticsearch/config, -Des.distribution.flavor=oss, -Des.distribution.type=tar]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:26Z","tags":["status","plugin:kibana@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:26Z","tags":["status","plugin:elasticsearch@6.3.0","info"],"pid":1,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["status","plugin:timelion@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["status","plugin:console@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["status","plugin:metrics@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["listening","info"],"pid":1,"message":"Server running at http://0:5601"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["error","elasticsearch","admin"],"pid":1,"message":"Request error, retrying\nHEAD http://elasticsearch:9200/ => connect ECONNREFUSED <IP_ADDRESS>:9200"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:27Z","tags":["status","plugin:elasticsearch@6.3.0","error"],"pid":1,"state":"red","message":"Status changed from yellow to red - Unable to connect to Elasticsearch at http://elasticsearch:9200.","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:29Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:29Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:40:30,747][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [aggs-matrix-stats]
elasticsearch_1  | [2018-07-10T08:40:30,757][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [analysis-common]
elasticsearch_1  | [2018-07-10T08:40:30,758][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [ingest-common]
elasticsearch_1  | [2018-07-10T08:40:30,759][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [lang-expression]
elasticsearch_1  | [2018-07-10T08:40:30,759][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [lang-mustache]
elasticsearch_1  | [2018-07-10T08:40:30,759][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [lang-painless]
elasticsearch_1  | [2018-07-10T08:40:30,761][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [mapper-extras]
elasticsearch_1  | [2018-07-10T08:40:30,761][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [parent-join]
elasticsearch_1  | [2018-07-10T08:40:30,762][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [percolator]
elasticsearch_1  | [2018-07-10T08:40:30,762][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [rank-eval]
elasticsearch_1  | [2018-07-10T08:40:30,762][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [reindex]
elasticsearch_1  | [2018-07-10T08:40:30,763][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [repository-url]
elasticsearch_1  | [2018-07-10T08:40:30,763][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [transport-netty4]
elasticsearch_1  | [2018-07-10T08:40:30,763][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded module [tribe]
elasticsearch_1  | [2018-07-10T08:40:30,765][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded plugin [ingest-geoip]
elasticsearch_1  | [2018-07-10T08:40:30,768][INFO ][o.e.p.PluginsService     ] [ghCf0VW] loaded plugin [ingest-user-agent]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:32Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:32Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:34Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:34Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:37Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:37Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:39Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:39Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:42Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:42Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:44Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:44Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:40:47,191][INFO ][o.e.d.DiscoveryModule    ] [ghCf0VW] using discovery type [single-node]
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:47Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:47Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:49Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"Unable to revive connection: http://elasticsearch:9200/"}
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:49Z","tags":["warning","elasticsearch","admin"],"pid":1,"message":"No living connections"}
elasticsearch_1  | [2018-07-10T08:40:50,835][INFO ][o.e.n.Node               ] [ghCf0VW] initialized
elasticsearch_1  | [2018-07-10T08:40:50,840][INFO ][o.e.n.Node               ] [ghCf0VW] starting ...
elasticsearch_1  | [2018-07-10T08:40:51,643][INFO ][o.e.t.TransportService   ] [ghCf0VW] publish_address {<IP_ADDRESS>:9300}, bound_addresses {<IP_ADDRESS>:9300}
elasticsearch_1  | [2018-07-10T08:40:51,956][INFO ][o.e.h.n.Netty4HttpServerTransport] [ghCf0VW] publish_address {<IP_ADDRESS>:9200}, bound_addresses {<IP_ADDRESS>:9200}
elasticsearch_1  | [2018-07-10T08:40:51,957][INFO ][o.e.n.Node               ] [ghCf0VW] started
elasticsearch_1  | [2018-07-10T08:40:52,166][INFO ][o.e.g.GatewayService     ] [ghCf0VW] recovered [0] indices into cluster_state
kibana_1         | {"type":"log","@timestamp":"2018-07-10T08:40:53Z","tags":["status","plugin:elasticsearch@6.3.0","info"],"pid":1,"state":"green","message":"Status changed from red to green - Ready","prevState":"red","prevMsg":"Unable to connect to Elasticsearch at http://elasticsearch:9200."}
docker-elk_logstash_1 exited with code 1
Problem description

Extra information

Stack configuration

Docker setup
<!-- Replace this comment with the full output of the `docker version` command. -->

<!-- Replace this comment with the full output of the `docker-compose version` command. -->

Docker logs
<!-- Replace this comment with the full output of the `docker-compose logs` command. -->

@atheeth96 please fill-in the issue template and re-open this issue. It's really important for us to have clear information in order to be able to help you.
Thanks for your understanding.


when user code throws, the exception is not displayed in the output pane

An exception thrown by successfully-compiling user code is not displayed in the output pane.
The exception is returned in the json response from the server. It appears to affect both try.dot.net/ide and docs.microsoft.com.

I have a PR out for a fix. The Exception message is appended to the output using the same formatting as is done for console. Specifically:
any
stdout
content

Unhandled Exception: exception
    at details

Fixed.

Sweet!!! @piotrpMSFT Do we need to make any updates in the docs front-end code?


Use golang.org/x/sys instead of syscall?

While installing transocks on i686 system, I got the following error:
go/src/github.com/cybozu-go/transocks/original_dst_linux.go:14:3: undefined: syscall.SYS_GETSOCKOPT

The official document says:

Deprecated: this package is locked down. Callers should use the corresponding package in the golang.org/x/sys repository instead. That is also where updates required by new systems or versions should be applied. See https://golang.org/s/go1.4-syscall for more information.

I manually replaced syscall with golang.org/x/sys/unix. It worked well.
For better OS support, use golang.org/x/sys instead?

Thank you for the report!
We should replace it as you described.
Are you willing to make a pull request for it?

Thank you for the quick reply.
I submitted #14. Please take a look.


Ability to get a course grade for a single student regardless of whether course grades are released

From @payten on October 16, 2015 0:38
Required for #247.
In dynamically updating a student's course grade when a score changes, the current endpoint returns 'null' if the course grades are configured to be not released to students.  It'd be great to have the ability to pull back the latest course grade for a single student, also formatted accordingly to the Gradebook settings.
Copied from original issue: steveswinsburg/gradebookNG#266

From @payten on October 19, 2015 11:38
Yep that sounds right - the course grade column is visible to both instructors and TAs so that makes sense.

Checked out the service code for this. There is a hard check in there to not do anything if its not released. However we can probably bypass that with a role check. We'll need this bypassed for both instructor and TA correct?

Created https://jira.sakaiproject.org/browse/SAK-30119 to track the GB service mods.

This will be fixed with the #1464 PR.


[WebUI] Sort quick phrases by last usage timestamp

Sorting is by tier:

By descending order of last used timestamp
In case of tie, sort by creation timestamp
In case of tie, sort lexicographically

Fixes https://github.com/TeamGleason/SpeakFaster/issues/241

@antonkast-google Please review this PR. Thanks.


have automatic separate functions for finger and stylus

I have not found a way for excalidraw to automatically only assign pen functions to the stylus (so the pen will never be used to move around the canvas and is only there to write/highlight) and "touch" functions to the finger (the finger is only used to zoom and move around the canvas and never writes). Please let me know if this can be set up or if it can be implemented. RIght now I have to click on the hand symbol everytime I want to adjust the canvas and back to the pen symbol when I want to write again, which is pretty annoying. Thanks in advance!
Edit: basically have a way for single finger pan when in pen mode

Excellent suggestion. This would greatly improve the drawing experience, and put it on par with onenote's implementation.


Sluggish UI on images with a lot of files

With this image: https://hub.docker.com/r/butomo1989/docker-android-x86-9.0/ moving up and down on a layer can take a few seconds and spin the CPU up to 100%.
If you push up and down a few times the wait time piles up.
It seems the UI code that does some CPU intensive task for rendering the layer. I think there is a lot of room for optimizations.
I am not sure how this relates with #94

There are definitely opportunities for optimizations. The easy route first was taken by building the view tree on the fly. pprof showed a lot of inefficiencies with view writes, which was fixed by drawing only the visible portion of the tree. I'll profile it again soon against this image to see if the sluggishness is due to this or something else.

I look at the UI code (but not in depth) and profiled it.
In main.go I added:
import (
	"log"
	"net/http"
	_ "net/http/pprof"
...

func main() {
	...

	go func() {
		log.Println(http.ListenAndServe("localhost:6060", nil))
	}()

	...

	return tree
}

And then go tool pprof http://localhost:6060/debug/pprof/profile and I just start going up and down on the layers.
Then I created this graph with the png command:

My takes:
It looks the code is coping over and over the filetree. That creates a lot of work for the CPU for creating and deleting (during garbage collection). The filterRegex also seems taking a lot of CPU.
Do you have to keep copying the filetree?
I would probably had used different data structures:

The files on the layers of images will never change. Once you have the tar headers and the hash of the files you have everything you need. You can index stuff in maps by path, by hash, and whatever else you need so you can retrive things in O(1). This is by the way what I was talking about in #90 (2). As a side note, you could also cache the data about a layer or image hash on disk (on a ~/.dive/cache forder maybe?) so next time somebody open dive, instead of opening the image you can just read from the cache without having to calculate hashes or even read the content of the layers... I would also consider using a sqlite db for that purpose.
It can make sense to decoupled the data structure that stores the files on the layers and the UI state (forder expanded, etc).
It is not necessary to redraw everything from scratch. Only the variations needs to change.

I can go more in details if you want me.
It looks like you are already working on some refactoring so it is up to you.

@ccinelli I appreciate the pprof output and comments. I additionally ran a memory profile this go around to see what is taking up space and found a few optimizations.
Up front I decided to take the easy way first with implementation, only optimizing when it became necessary --it has now become necessary for large images. It looks like, in general, we are now looking at a classic time-v-space tradeoff game: do we want to store more or have the user wait for it to be computed?

based on the pprof output I focused on data copying first. The largest culprit of this was with tree "stacking" and comparisons. "Stacking" refers to taking multiple file trees and combining them (which requires copying entire trees), and comparisons were implemented by copying the original tree to ensure the comparison was being done against the un-mutated data.
Removing any viper.Get* calls in places where it is called in a loop was apparently very helpful in saving memory (surprisingly)
Reducing the hash chunk size made layer processing faster
Consolidating the tar header info down to only the fields needed helped on image size
For the meantime I've moved most data copies to the data preprocessing section of the application (before the TUI starts). I'm about to work on a concept where this preprocessing is pushed to the background an allows the user to navigate to layers that have been loaded.

This is been a pretty big step in the right direction. For instance, the current amir20/clashleaders:latest image needs 38 trees built to show all comparisons (^L layer-only comparisons + ^A cumulative comparisons), and has a total of ~820,000 file nodes across all trees. Assuming a FileNode (after optimizations) is about ~400 bytes-ish on average, this means that at least 328 MB of data needs to get generated, not including intermediate data. Pushing all of the tree building (caching) preprocessing up front, this image took 19 seconds to load on my laptop... with the latest optimizations it's down to ~3 seconds! The current work is here: https://github.com/wagoodman/dive/compare/refactor-image-preprocessing...cache-tree-building?expand=1 . I'll make a PR once I fix tests.
After optimizations pprof shows (for CPU time):
File: dive
Type: cpu
Time: Dec 4, 2018 at 8:04pm (EST)
Duration: 12.94s, Total samples = 3.70s (28.59%)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top
Showing nodes accounting for 1890ms, 51.08% of 3700ms total
Dropped 76 nodes (cum <= 18.50ms)
Showing top 10 nodes out of 137
      flat  flat%   sum%        cum   cum%
     410ms 11.08% 11.08%      780ms 21.08%  runtime.scanobject
     250ms  6.76% 17.84%      250ms  6.76%  cmpbody
     230ms  6.22% 24.05%      350ms  9.46%  runtime.mapaccess1_faststr
     190ms  5.14% 29.19%      210ms  5.68%  runtime.findObject
     180ms  4.86% 34.05%     1750ms 47.30%  github.com/wagoodman/dive/filetree.(*FileNode).VisitDepthChildFirst
     140ms  3.78% 37.84%      170ms  4.59%  runtime.heapBitsSetType
     130ms  3.51% 41.35%      130ms  3.51%  runtime.aeshashbody
     130ms  3.51% 44.86%      470ms 12.70%  sort.(*StringSlice).Less
     120ms  3.24% 48.11%      550ms 14.86%  runtime.mallocgc
     110ms  2.97% 51.08%      130ms  3.51%  runtime.mapiternext

and (for memory usage):
File: dive
Type: inuse_space
Time: Dec 4, 2018 at 8:02pm (EST)
Entering interactive mode (type "help" for commands, "o" for options)
(pprof) top
Showing nodes accounting for 2MB, 100% of 2MB total
Dropped 1 node (cum <= 0.01MB)
Showing top 10 nodes out of 37
      flat  flat%   sum%        cum   cum%
    1.04MB 52.28% 52.28%     1.04MB 52.28%  github.com/wagoodman/dive/filetree.NewNode
    0.62MB 30.82% 83.10%     1.39MB 69.38%  github.com/wagoodman/dive/filetree.(*FileNode).AddChild
    0.21MB 10.66% 93.76%     0.23MB 11.45%  github.com/wagoodman/dive/filetree.(*FileNode).Path
    0.10MB  4.85% 98.62%     0.37MB 18.57%  github.com/wagoodman/dive/filetree.(*FileNode).Copy
    0.02MB  0.79% 99.41%     0.02MB  0.79%  strings.Replace
    0.01MB  0.59%   100%     0.01MB  0.59%  archive/tar.(*parser).parseString
         0     0%   100%     0.01MB  0.59%  archive/tar.(*Reader).Next
         0     0%   100%     0.01MB  0.59%  archive/tar.(*Reader).next
         0     0%   100%     0.01MB  0.59%  archive/tar.(*Reader).readHeader
         0     0%   100%        2MB   100%  github.com/spf13/cobra.(*Command).Execute

To respond to your comments:

"Use O(1) datastructures": Initial prototyping showed that prepopulating a hash lookup was taking just as much time as it was to group the tree combinations into one spot... so I instead continued down still using a tree structure. There are some opportunities to store some data structures in a hash (such as the view info as noted in 3, which could be decoupled further). However, I feel that there is more value keeping the tree data structure (instead of replacing it with a hash). One example is comparisons (an important use case highlighted from profiling): when removing a node, what is the best way to remove all child nodes? In a hash data structure it would be a O(n) operation still, since the parent-child relations aren't known. I could imaging a hybrid hash/tree implementation, where pointers to nodes are accessible from a hash (keyed on path), and each node structure has a relation of children... I'm still pondering where it makes sense to implement this.

"cache on the visualization layer": I thought about always storing what was drawn to the screen, such that if the user takes that action again, we wouldn't need to create the string again. When I tried it out, dive started using a lot of memory (unsurprisingly). For now I've decided to focus efforts elsewhere, as I feel that this would become more complicated than the benefits implementing it may have. When I originally profiled it appeared that optimizing the filetree string render function was "good enough" (...for now).

"decouple UI related structures": Yes! I think that this is a good idea to help performance and would make the code more readable.

"don't redraw everything from scratch, only diffs": though this may be tempting, it will introduce a lot of complexity where profiling doesn't indicate a direct problem.

"cache to disk": I think this is a good idea, limiting how much is cached by purging old cache would need to be quick and automatic.

There is a time vs space tradeoff but here I think that the right data structure and algorithm can save a lot of time and memory.
Switching layer is still pretty slow for me and it takes 2Gb.
Same test with the new branch:

Regarding your comments:

I did not mean replacing the tree with a map. I was talking about adding maps where it makes sense.
It depends on what you are caching.
Only if it is convenient.
It depends how it is implemented.
Yes, you can have a LRU mechanism to decide what to deleted when the DB becomes too big.

I realize that I should be more concrete on describing the  changes that I am thinking about. I will post a little bit more in a little bit.
You may also want to look at the implementation of https://github.com/cheton/infinite-tree for inspiration.
In general you do not have to visit the whole tree every time there is an update. Anyway, I will write more shortly.

There are a few wastes of CPU and memory at the moment:

Visiting an entire large tree is expensive so I would try to limit to when is strictly necessary.

I would definitely avoid sorting the Children's keys  every time in VisitDepthChildFirst like here, this and in renderStringTreeBetween - That is probably why the actual visits are slower than expected. With the current features, the tree can easily order once so it is not necessary doing it every time.

I would keep using a tree (similar to what you already have) but I think it could be more effective if the leaf node was a slice of pointers to FileInfo (nil if the file was not present on that layer). You can also try a  a map where the key is the the int is the layer index. The first layer would be in Data.FileInfo[0], the second in Data.FileInfo[1] etc. In this way it would be easy to check the files added and removed by looking at Data.FileInfo[currentLayer - 1] and Data.FileInfo[currentLayer + 1]etc.   It also may make easier to reason about wasted space. You still may have to parse the whole slice to implement #107.

 I would try not to create or destroy trees unless it is REALLY necessary. I do not think you will have to recreate trees or modifying data on it (except the ViewInfo). For the folders I would add more data including the n_tot_files as  [] uint (again one for each layer). I would also capture  in Data the n_tot_visible_files, the TotalWastedBytes, TotalWastedBytes and the other "global" metrics. The only time when you may want to modify the tree is if you want to order the nodes in different order. In #110 I suggested letting people order by descending wasted bytes. Alphabetical order and normal file size order also make sense. When you do that you may have to sort the FileNode.Children. For that reason I wonder if a []*FileNode instead of a map[string]*FileNode for Children  may be more effective  And BTW, if you really need it, you can have both and use the map for the GetNode and use the slice for order. As far a as I know, it is just easier to re-order a slice in place.

Every node of the tree takes a row on the screen.  When you have to render the file tree window you just have to start rendering the row in view. Not only render the string but also you do not have to visit all the nodes and subtree above and below. You can simply scan the tree to find the start_row and end_row without a full visit when you account of n_tot_visible_files in the folders. And, of course you do not have to recalculate the start_row every time and you can just keep a pointer to the start FileNode.

Path in FileInfo seems redundant and could be found just following the chain of Parents - It looks like you already have Node.Path()

Agreed
Agreed, I'll update to sort on insert in a follow up PR.
I like this idea, and though it may save on space a bit I probably will not incorporate this as it would be a fairly major overhaul without a clear performance advantage.
Somewhat agree. The analysis isn't taking up that much time, so including these extra fields and globals I don't think would help all that much --I'm not opposed to it though. Swapping from map[string]*FileNode to []*FileNode makes sense given that there are multiple issues asking for ordering by different metrics.
Somewhat agree. This is actually fairly fast already, though I think it would be a great idea to keep a pointer to the current top FileNode in the filetree pane.
Somewhat agree. I think it makes sense to reduce redundancies but I don't think this is the cause of performance degradation and probably isn't taking up an alarming amount of space --I'm not opposed to removing FileInfo.Path once memoization is implemented on FileNode.Path().

I'll close this issue as there have been several major performance enhancements (with great results!). Thanks for putting in time to address much of this tech debt.
I welcome PRs for performance enhancements at anytime!

I think 0.5.0 is a lot faster than before. So it is a great improvement. At the same time, I still have the UI lagging on large images if I scroll down or up on the layer panel.
I agree on starting on #89. I think that (2) can be kept in mind while implementing it and (4) is actually providing a way to implement different ordering and (2).  You could, in fact, have a map[string][]*FileNode. The key is the order type (maybe 'filesize', 'wastesize', 'name', etc) and the value is the slice with the ordered files. Instead of calculating all keys upfront it can be calculated as the user switch ordering mode. You can keep them in the map that act as a cache so you do not have to reorder again later so switching between different ordering modes and back is snappy. One extra feature in (4) is being able to order by "byte wasted" that, in my opinion, is the best order mode to prioritize the work of shrinking the image that is probably the main use case of dive (see #110).
I know (3) could be a huge refactoring. It is also true that, the more code is written, the more expensive would be to change that in the future. But I do not blame you if you do not want to jump on it ;-)
The main advantage of this format is that the information about the same file across layers is co-located. This makes code more readable, improve the access speed and save you from having to copy things between trees. The speed up is not just the analysis (that you do only once), but it is more in avoiding to visit the whole tree in FileTreeView.Update() to copy ViewInfo.  If you want to further optimize the memory, you can have 2 structures. One for when the file is only on one layer and the one that I described in (3) for when the file changes.
Regarding (5), at the moment the visitDeaphChildFirst is the slowest part. (5) prunes down the part of the tree that needs to be traversed to show the files.
Finally regarding your comment to (6), are not FileInfo.Path (specifically Data.FileInfo.Path) and FileNode.Path() the same? If you want to save memory you just use Data.FileInfo.Path. If you want to save CPU you can use FileNode.Path() that is what I was suggesting. I am assuming there is a fast way to access the file on the other layers like in (3) but after it is ordered I do not think you need it anymore. So I do not understandwhy FileNode.Path() should use memoization. If you are willing to pay the memory toll, why not just use Data.FileInfo.Path and get rid of FileNode.Path()?


AreaAttribute - Doesn't work as expected

The basic behavioural flow of using the RouteAttribute on a Controller implementation results in all actions within the controller that don't start with a forward slash to inherit the controller's route template.  This is true even when you don't include your own RouteAttribute on the Controller.
This convention doesn't work with the AreaAttribute however.  The only way I have been able to get the various RouteAttributes (i.e. HttpGet) to include the area is to add the keyword "[area]" within the action's route template.  This results in the loss of conventional and expected behaviour.  I can no longer apply a global route change to a controller through the top template.
Am I doing something incorrect?  Or is this just a 'feature'?

Ummm... Not sure what's going on but after a few builds this behaviour started working correctly.  I haven't changed anything that I can see that would have caused this though...  I'll close this for now unless I see it occurring again.

If you can post a link to some code I can take a look.

Am I doing something incorrect? Or is this just a 'feature'?

It's intended that attributes work like you typed them. There's no magic here besides substitution of tokens like [area]


Cycle: "Firing, Resolved"

What did you do?
Hello, I have problem with alertmanager cluster. I build cluster with 4 prometheus + (4 sidecar, 4 query), 4 alertmanager. I have two region (region1, region2). In every region there are two prometheus node - replica(A, B). All prometheus have as alerting targets all alertmanager nodes. All alertmanager nodes have have as parameters cluster.peer all alertmanager nodes. Alertmanager send alerts to pagerduty. In alertmanager and pagerduty is grouping disabled.
What did you see instead? Under which circumstances?
If I have up all alertmanager nodes so the alerting send every 3minutes resolve. After 1minute it send firing. Cycling again. If I have up only one alertmanager node per region so OK.
What did you expect to see?
I need running all nodes. If some prometheus send alert to alertmanager cluster so firing status, if prometheus not send alert so resolve status.
Environment

System information:
Linux 4.9.0-7-amd64 x86_64
All running in docker container

Alertmanager version:
alertmanager, version 0.15.3

Prometheus version:
prometheus, version 2.4.2

Alertmanager configuration file:

global:

templates:
- '/etc/alertmanager/templates/*.tmpl'

route:
  receiver: 'pagerduty'
  group_by: ['alertname', 'instance', 'job']
  group_wait: 30s
  group_interval: 5m
  repeat_interval: 4h

inhibit_rules:
- source_match:
    severity: 'critical'
  target_match:
    severity: 'warning'
  equal: ['alertname', 'instance', 'job']

- name: 'pagerduty'
  pagerduty_configs:
  - send_resolved: true
    service_key: ....
    url: https://events.pagerduty.com/v2/enqueue
    client: '{{ template "pagerduty.default.client" . }}'
    client_url: '{{ template "pagerduty.default.clientURL" . }}'
    description: '{{ template "pagerduty.default.description" .}}'
    details:
      firing: '{{ template "pagerduty.default.instances" .Alerts.Firing }}'
      num_firing: '{{ .Alerts.Firing | len }}'
      num_resolved: '{{ .Alerts.Resolved | len }}'
      resolved: '{{ template "pagerduty.default.instances" .Alerts.Resolved }}'
    severity: '{{ if .CommonLabels.severity }}{{ .CommonLabels.severity | toLower
      }}{{ else }}critical{{ end }}'
    class: '{{ .CommonLabels.class }}'
    component: '{{ .CommonLabels.component }}'
    group: '{{ if .CommonLabels.environment }}.{{ .CommonLabels.environment }}{{
      end }}{{ if .CommonLabels.region }}.{{ .CommonLabels.region }}{{ end }}{{ if
      .CommonLabels.service }}.{{ .CommonLabels.service }}{{ end }}'

Prometheus configuration file:
Region: region1
Replica: A

# my global config
global:
  scrape_interval:     40s
  evaluation_interval: 1m
  external_labels:
    region: region1
    replica: A

# Alertmanager configuration
alerting:
  alert_relabel_configs:
    - source_labels: [region]
      replacement: ''
      target_label: region
    - source_labels: [replica]
      replacement: ''
      target_label: replica
  alertmanagers:
  - scheme: https
    static_configs:
    - targets:
      - bafana1.region1:9093
      - bafana2.region1:9093
      - bafana1.region2:9093
      - bafana2.region2:9093

Region: region1
Replica: B
# my global config
global:
  scrape_interval:     40s
  evaluation_interval: 1m
  external_labels:
    region: region1
    replica: B

# Alertmanager configuration
alerting:
  alert_relabel_configs:
    - source_labels: [region]
      replacement: ''
      target_label: region
    - source_labels: [replica]
      replacement: ''
      target_label: replica
  alertmanagers:
  - scheme: https
    static_configs:
    - targets:
      - bafana1.region1:9093
      - bafana2.region1:9093
      - bafana1.region2:9093
      - bafana2.region2:9093

Region: region2
Replica: A
# my global config
global:
  scrape_interval:     40s
  evaluation_interval: 1m
  external_labels:
    region: region2
    replica: A

# Alertmanager configuration
alerting:
  alert_relabel_configs:
    - source_labels: [region]
      replacement: ''
      target_label: region
    - source_labels: [replica]
      replacement: ''
      target_label: replica
  alertmanagers:
  - scheme: https
    static_configs:
    - targets:
      - bafana1.region1:9093
      - bafana2.region1:9093
      - bafana1.region2:9093
      - bafana2.region2:9093

Region: region2
Replica: B
# my global config
global:
  scrape_interval:     40s
  evaluation_interval: 1m
  external_labels:
    region: region2
    replica: B

# Alertmanager configuration
alerting:
  alert_relabel_configs:
    - source_labels: [region]
      replacement: ''
      target_label: region
    - source_labels: [replica]
      replacement: ''
      target_label: replica
  alertmanagers:
  - scheme: https
    static_configs:
    - targets:
      - bafana1.region1:9093
      - bafana2.region1:9093
      - bafana1.region2:9093
      - bafana2.region2:9093

Logs:

@400000005be95c82236f098c level=debug ts=2018-11-12T10:56:56.594019841Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95c8316b98b04 level=debug ts=2018-11-12T10:56:57.38076309Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:56:57 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:9094\n"
@400000005be95ca01b020a24 level=debug ts=2018-11-12T10:57:26.452585627Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95cba12c2ba0c level=debug ts=2018-11-12T10:57:52.31414958Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:57:52 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:54258\n"
@400000005be95cbe2139a35c level=debug ts=2018-11-12T10:57:56.556144368Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[9e4ef6e][active]
@400000005be95cbf17266a1c level=debug ts=2018-11-12T10:57:57.387736935Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:57:57 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:9094\n"
@400000005be95cdc1cf44cd4 level=debug ts=2018-11-12T10:58:26.485316502Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[9e4ef6e][active]
@400000005be95cdc1e06552c level=debug ts=2018-11-12T10:58:26.503348891Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95cf12e704864 level=debug ts=2018-11-12T10:58:47.778565149Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:58:47 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:52528\n"
@400000005be95cf612f7fadc level=debug ts=2018-11-12T10:58:52.317722525Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:58:52 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:54626\n"
@400000005be95cfa1e55a9c4 level=debug ts=2018-11-12T10:58:56.508498654Z caller=impl.go:578 msg="Notifying PagerDuty" incident="{}:{alertname=\"LowDiskSpace\", instance=\"dock011.region1:9100\", job=\"node\"}" eventType=resolve
@400000005be95cfa1fb800b4 level=debug ts=2018-11-12T10:58:56.531041711Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95cfa20be4554 level=debug ts=2018-11-12T10:58:56.548965886Z caller=impl.go:578 msg="Notifying PagerDuty" incident="{}:{alertname=\"LowDiskSpace\", instance=\"dock008.region1:9100\", job=\"node\"}" eventType=resolve
@400000005be95cfb175e1804 level=debug ts=2018-11-12T10:58:57.391571385Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:58:57 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:9094\n"
@400000005be95d1822601a2c level=debug ts=2018-11-12T10:59:26.576195564Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[9e4ef6e][active]
@400000005be95d2d2ea88ea4 level=debug ts=2018-11-12T10:59:47.782276972Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:59:47 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:52882\n"
@400000005be95d3616f1776c level=debug ts=2018-11-12T10:59:56.384307782Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95d362212dcbc level=debug ts=2018-11-12T10:59:56.571066523Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[9e4ef6e][active]
@400000005be95d3717a90f6c level=debug ts=2018-11-12T10:59:57.396393706Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 10:59:57 [DEBUG] memberlist: Initiating push/pull sync with: <IP_ADDRESS>:9094\n"
@400000005be95d5420bb72ac level=debug ts=2018-11-12T11:00:26.547945959Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[456303a][active]
@400000005be95d692ee7d5dc level=debug ts=2018-11-12T11:00:47.786296172Z caller=cluster.go:287 component=cluster memberlist="2018/11/12 11:00:47 [DEBUG] memberlist: Stream connection from=<IP_ADDRESS>:53236\n"
@400000005be95d721b247e74 level=debug ts=2018-11-12T11:00:56.454735658Z caller=dispatch.go:201 component=dispatcher msg="Received alert" alert=LowDiskSpace[9e4ef6e][active]
@400000005be95d721ed925ec level=debug ts=2018-11-12T11:00:56.50966566Z caller=dispatch.go:445 component=dispatcher aggrGroup="{}:{alertname=\"LowDiskSpace\", instance=\"dock011.region1:9100\", job=\"node\"}" msg=Flushing alerts=[LowDiskSpace[9e4ef6e][active]]
@400000005be95d7220d08d04 level=debug ts=2018-11-12T11:00:56.550082378Z caller=dispatch.go:445 component=dispatcher aggrGroup="{}:{alertname=\"LowDiskSpace\", instance=\"dock008.region1:9100\", job=\"node\"}" msg=Flushing alerts=[LowDiskSpace[456303a][active]]
@400000005be95d7316db304c level=debug ts=2018-11-12T11:00:57.382766837Z caller=nflog.go:534 component=nflog msg="gossiping new entry" entry="entry:<group_key:\"{}:{alertname=\\\"LowDiskSpace\\\", instance=\\\"dock008.region1:9100\\\", job=\\\"node\\\"}\" receiver:<group_name:\"pagerduty\" integration:\"pagerduty\" > timestamp:<seconds:1542020457 nanos:375915602 > firing_alerts:14498338330822246194 > expires_at:<seconds:1542452457 nanos:375915602 > "

Alert configuration:

  - alert: LowDiskSpace
    expr: instance:filesystem_free:percent <= 20
    for: 5m
    labels:
      severity: warning
    annotations:
      title: LowDiskSpace
      description: '{{ $labels.instance }} filesystem {{ $labels.device }} has less than 20% disk space remaining.'
      summary: Instance {{ $labels.instance }} filesystem usage warning

I'm not to understand exactly the issue: do you mean that you receive a PagerDuty notification then 3m later you receive the resolved notification and after 1m, it goes back to the first step?
I see you're using version 0.15.3. Does it work as you expect with v0.15.2? Asking because 0.15.3 manages alert end times differently due to a change in Prometheus v2.4.

Sorry, but my english is not very good.
Yes.

Prometheus send alert to alertmanager
Alertmanager send firing to pagerduty
Pagerduty send msg to mattermost
After 3m alertmanager send resolve to pagerduty
Come resolve status to mattermost
After 1m start start second step

I try with v0.15.2 and v0.15.3... the same problem.
I thought so it is problem with evaluation. But from prometheus json will come to alertmanager every 1m. I don't know where I do misstakes.

Please check that clocks are in sync across all the machines. Can you share AlertManager logs spanning a larger interval (including firing/resolved/firing notifications)?

Something to note: Alertmanager's gossip is configured for a LAN, and has not been tested for cross-region performance. This could easily be causing issues.
Is the notification you receive in 6 for the same instance as in 2? You are grouping on instance, so notifications will be for different instances.
Also, your alertmanager config says the group_interval is 5min. For a single notification group, after the initial notification (2), you should get another notification after 5min if the group status changed.

Thanks. Problem is with cross-region.
I create separate alertmanager cluster for each region. Now alerting is ok.
I wanted create big cluster for all (cross-region) for maximal redundation but this solution is ok.


Better explanation of y-axis on graphs

Added percentages to tooltips, this should help at least a little


New call function and improved number validation

Added

Phone number validation function.
Separate command to use selected text or clipboard content as phone number.

Changed

Can now initiate phone call from main view.
Upgraded dependencies.

Fixed

TypeError: Cannot read properties of undefined (reading 'replace')## Description

Checklist

[X] I read the extension guidelines
[X] I read the documentation about publishing
[X] I ran npm run build and tested this distribution build in Raycast
[X] I checked that files in the assets folder are used by the extension itself
[X] I checked that assets used by the README are placed outside of the metadata folder

Hi @chrismessina 👋
Thanks for the update 🔥 Can you move the update for google-maps-search out of this PR so our bot is happy 😂

When I attempt to discard those changes, I get an error. Can you help or provide me with some steps to remedy this issue?

I'll ask my colleague to remove it properly 🙂

Did you know that the current command in Quick Call already supports selection and clipboard? Don't you think it should be enough with just one multi-purpose command?

Did you know that the current command in Quick Call already supports selection and clipboard? Don't you think it should be enough with just one multi-purpose command?

I originally tried that approach, but couldn't figure out how to grab the selected text or clipboard, clean or validate it as a phone number, and then execute it with a no-view command.
I would prefer a single multi-purpose command so if you can point me to a no-view example that processes input from the selected text or clipboard, I can make the changes.

Wrote you on slack 🙂

Can you try the fork method we spoke about? Seems like you keep adding the old google-search files over and over again 🙂


Add secondary target bonus when heist is replayed within 72h cooldown…

… (Criminal Enterprises DLC)

@a-blondel i have only one question. Why you named setting "72h cooldown"? In my opinion it is more a bonus. I know that high value primary targets are less likely to get, but cooldown = break time.

@MichalD96
Glad to help :)
Good question. In my mind, it was a way to shorten "Inside the 72h cooldown in which the rarest primary target chance rates are lowered and secondary targets payout are increased", as it could be used again if you display the chance rates of primary targets by e.g.
As not everyone knows about theses changes, I though of a more neutral label like "Replaying heist within 72h ?".
Choose what you like the most, on that project you are the Kapitan !


MarginSide Top Crash

Was just starting to look over the extension to see if it is something I'd like to use. It was great thus far but I was trying to maybe pull it out of the text editor into its own window type. In doing so I was messing with the settings and set the MarginSide (don't remember actual display name but in source code it is Settings.Default.MarginSide) to Top. By doing this it crashed. Now, every time I open a solution or project I get a Microsoft Visual Studio error with the following message:
An exception has been encountered. This may be caused by an extension.

You can get more information by examining the file 'LOCATION\ActivityLog.xml'

Here's the error from the ActivityLog.xml:
  <entry>
    <record>773</record>
    <time>2019/10/11 20:47:08.963</time>
    <type>Error</type>
    <source>Editor or Editor Extension</source>
    <description>System.NullReferenceException: Object reference not set to an instance of an object.
   at CodeNav.CodeNavMargin.CreateGridTop(IWpfTextViewHost textViewHost) in d:\a\1\s\CodeNav\CodeNavMargin.cs:line 208
   at CodeNav.CodeNavMargin..ctor(IWpfTextViewHost textViewHost, DTE dte, IOutliningManagerService outliningManagerService, VisualStudioWorkspace workspace, MarginSideEnum side) in d:\a\1\s\CodeNav\CodeNavMargin.cs:line 60
   at CodeNav.CodeNavFactory.CreateMargin(IWpfTextViewHost wpfTextViewHost, VisualStudioWorkspace visualStudioWorkspace, IServiceProvider serviceProvider, MarginSideEnum side) in d:\a\1\s\CodeNav\CodeNavMarginFactory.cs:line 108
   at CodeNav.CodeNavTopFactory.CreateMargin(IWpfTextViewHost wpfTextViewHost, IWpfTextViewMargin marginContainer) in d:\a\1\s\CodeNav\CodeNavMarginFactory.cs:line 87
   at Microsoft.VisualStudio.Text.Utilities.ContainerMargin.<AddMargins>b__25_1(IWpfTextViewMarginProvider mp)
   at Microsoft.VisualStudio.Text.Utilities.GuardedOperations.InstantiateExtension[TExtension,TMetadata,TExtensionInstance](Object errorSource, Lazy`2 provider, Func`2 getter)
--- End of stack trace from previous location where exception was thrown ---
   at Microsoft.VisualStudio.Telemetry.WindowsErrorReporting.WatsonReport.GetClrWatsonExceptionInfo(Exception exceptionObject)</description>
  </entry>

I don't really want it to be on the top side but I couldn't find where the settings were being stored to change it. I attempted to uninstall the extension and re-install but it looks like on the uninstall it doesn't also remove settings so it kept that setting. I'd just like to reset to default if possible.

Assuming it takes some time for updates to appear through marketplace?

Had a small hickup in the release to the marketplace, but it is available now: https://marketplace.visualstudio.com/items?itemName=SamirBoulema.CodeNav :D

Perfect! Fixed my issue so I can bring it up again and I was able to use separate window as well! Win-Win! This is also the exact extension I was needing/looking for.
You can close this one out.
Thank you!


Question about vkitti dataset?

Hi, thanks for your good work!
There are two camera views in each sequences (Camera_0 and Camera_1), but i found the data file you used does not distinguish between Camera_0 and Camera_1, for example,
rgb/0006/clone/00046.png depth/0006/clone/00046.png
rgb/0006/clone/00073.png depth/0006/clone/00073.png
rgb/0006/clone/00176.png depth/0006/clone/00176.png
I want to know which camera view you use in the experiment? And why don't use both of Camera_0 and Camera_1  data? It will provide more train data, right?
Another problem is how to divide the train, val and test datasets?
Thank you in advance！

Hi，vkitti dataset does not contain the two camera views.
"Virtual KITTI contains 50 high-resolution monocular videos (21,260 frames) generated from five different virtual worlds in urban settings under different imaging and weather conditions".  For the details of the dataset, you can refer to the link below. https://europe.naverlabs.com/research/computer-vision/proxy-virtual-worlds-vkitti-1

Thanks for your reply!
This may be because I downloaded vkitti 2 dataset and you are using vkitti 1.3.1.


Update .cargo/config Shader Compilation Setup

Hey there! I was just trying this out and found out that there is an extra rustc flag that needed to be added to get it to compile and also to get it to match the settings passed in by the spirv-builder build process.

No problem, thanks!


Emulator no longer working

The Emulator V4 is no longer working, it kept asking for config the ngork service. After serval attempts, it stays not working.

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

ID: fa3a3039-9b21-fcb9-3fd7-4ae8c69bce93
Version Independent ID: 36ceb86e-828a-03d7-3245-44ab6ea4c09a
Content: Test and debug bots using the Bot Framework Emulator - Bot Service
Content Source: articles/bot-service-debug-emulator.md
Service: bot-service
GitHub Login: @DeniseMak
Microsoft Alias: v-demak

You can log an issue in the emulator repo with steps to repro.


[FEAT] :sparkles: Create admin user from command line

Description
We can't create a rest api endpoint for creating admin user because if we do than anyone can use that endpoint to create
admin user for them
We should implement a command that will run in terminal which will create a new user in database with role admin
example command:-
admin -e <email> -p <password>

Anything else?
I have already implemented this in another project you can get reference of code from here:-
https://github.com/shriproperty/server/blob/dev/bin/index.ts
https://github.com/shriproperty/server/blob/dev/package.json#L12-L14

Completed


MouseCoordinateY: arrowWidth broken

I'm submitting a...

[X] bug
[ ] feature
[ ] chore

What is the current behavior
arrowWidth is ignored - arrow never gets rendered.
What is the expected behavior
arrow should be rendered according to arrowWidth.
Please tell us about your environment

Version: 0.2.3
Browser: [all]

Other information
arrowWidth works properly in react-stockcharts (latest ver, 0.7.8)

https://github.com/reactivemarkets/react-financial-charts/blob/6d060c66916d7dd9377d3ffa3808039ceb86ee15/packages/charts/src/coordinates/EdgeCoordinateV3.tsx#L248
Re-add support for arrows on edge co-ordinates.
I should be able to fix this, this afternoon.
Thanks, Mark


Trim whitespace when generating CSVs

Description
Problem 1: "strange CSV"
Step to reproduce: Open https://www.ensembl.org/Homo_sapiens/Gene/Matches?db=core;g=ENSG00000139618;r=13:32315086-32400268 and click on the "Download all tables as CSV" button (if is is visible on the page)
Symptom: the downloaded CSV wasn't displaying properly in Excel

Likely cause: sometimes values in a column would start with a line break, making Excel unable to display the whole value properly.

Solution: always trim white space for values added to CSV columns
View after the fix:

Problem 2: "button disappears after click"
Steps to reproduce: click on the "Download all tables as CSV" button (if is is visible on the page) and refresh the page; the button will no longer be visible.
Cause:

the button appears only when a certain counter that keeps track of the number of tables in a panel shows that there are more than one table (see relevant code)
however, component's output can get cached, in which case the table-rendering code will not get run, and the counter will not get incremented (see relevant code)

Solution: no idea, but a naive approach would be to avoid caching a component.
Notice: this example shows that any panel with multiple tables will have exactly the same problem. I do not know how best to fix it properly.
Views affected
http://wp-np2-1e.ebi.ac.uk:8410/Homo_sapiens/Gene/Matches?db=core;g=ENSG00000139618;r=13:32315086-32400268
Related JIRA Issues (EBI developers only)
https://www.ebi.ac.uk/panda/jira/browse/ENSWEB-6396

I can have a look if you like.

@ens-ap5 That would be great!

Problem 2 is non-fixable - the button is created as a result of calls to the new_table method in E::W::Component, but cached panels doesn't re-render the content. A decision was made to remove this code as there's no easy fix and the current behaviour is just confusing.


[dvsim:uvm_verbosity] add the option to pass a list of verbosities

running a test on any IP with a different verbosity gives a ton of output - most of which is irrelevant to the IP.
much of it comes from the comportable IP etc. so debugging gets cluttered.
a way to work around this is to use +uvm_set_verbosity= when running a test to set a verbosity for a specific component and its sub hierarchy
in my local make flow this has been fully automated by simply defining a verbosity.mk that the tool flow looks for and apply if found.
and example is shown here.
#######################################
# MAKEFILE that set verbosity
# for individual modules or parts
# of the hierarchy
#######################################
COMPONENT_A = uvm_test_top.bch_mag_e.cpu_e.ahb_m_agt.ahb_m_drv
ID_A        = _ALL_
VERBOSITY_A = UVM_DEBUG
PHASE_A     = run
PARAM_A     = +uvm_set_verbosity=${COMPONENT_A},${ID_A},${VERBOSITY_A},${PHASE_A}

COMPONENT_B = uvm_test_top.bch_mag_e.cpu_e.*
ID_B        = _ALL_
VERBOSITY_B = UVM_DEBUG
PHASE_B     = run
PARAM_B     = +uvm_set_verbosity=${COMPONENT_B},${ID_B},${VERBOSITY_B},${PHASE_B}

COMPONENT_C = uvm_test_top.bch_mag_e.*.axi_mon.*
ID_C        = _ALL_
VERBOSITY_C = UVM_LOW
PHASE_C     = run
PARAM_C     = +uvm_set_verbosity=${COMPONENT_C},${ID_C},${VERBOSITY_C},${PHASE_C}
######################################################################################
SIM_PARAMS += ${PARAM_A}
#SIM_PARAMS += ${PARAM_B}
SIM_PARAMS += ${PARAM_C}

This way only the output of exactly the components of interest is produced. which gives a much cleaner and easy to debug log file.
@sriyerg  I am not sure how much effort it takes to get something similar into our flow?
but I would definitely use it.
maybe others would also find this useful?

You can already do this in our flow. See example below:
Also see hw/top_earlgrey/dv/chip_sim_cfg.hjson and look for run_modes.
  // Add the following to your sim_cfg.hjson
  component_a: "uvm_test_top.bch_mag_e.cpu_e.ahb_m_agt.ahb_m_drv"
  id_a: _ALL_
  verbosity_a: UVM_DEBUG
  phase_a: run

  component_b: ...
  ...

  run_modes: [
    {
      name: set_verbosity_comp_a_uvm_debug
      run_opts: ["+uvm_set_verbosity={component_a},{id_a},{verbosity_a},{phase_a}"]
    }
    {
      name: set_verbosity_comp_a_uvm_low
      run_opts: ["+uvm_set_verbosity={component_b},{id_b},{verbosity_b},{phase_b}"]
    }
    {
      name: set_verbosity_comp_a_uvm_high
      run_opts: ["+uvm_set_verbosity={component_c},{id_c},{verbosity_c},{phase_c}"]
    }
  ]

  tests: [
    {
      // For foo test, only turn on UVM_DEBUG verbosity for comp_a and c
      name: foo_test
      ...
      en_run_modes: ["set_verbosity_comp_a_uvm_debug",
                     "set_verbosity_comp_c_uvm_high"]
    }
  ]

Great thanks @sriyerg
I was looking for something similar just didn't find it


CDPS-945: Enabling merge handling in production

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

Project coverage is 85.86%. Comparing base (e700a61) to head (cb86c26).

Additional details and impacted files
@@            Coverage Diff            @@
##               main      #85   +/-   ##
=========================================
  Coverage     85.86%   85.86%
  Complexity      486      486
=========================================
  Files            77       77
  Lines          1415     1415
  Branches        123      123
=========================================
  Hits           1215     1215
  Misses          127      127
  Partials         73       73

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


NTR 3-BrB-PP1 3-[(3-bromophenyl)methyl]-1-tert-butylpyrazolo[3,4-d]pyrimidin-4-amine

hi
I am looking for chebi
https://www.chemsrc.com/en/cas/956025-99-3_794891.html
I could not locate with searches
3-BrB-PP1
3-[(3-bromophenyl)methyl]-1-tert-butylpyrazolo[3,4-d]pyrimidin-4-amine

A new ChEBI entry has now been created for 3-BrB-PP1 (CHEBI:194136).
It should be searchable on the ChEBI website by tomorrow.
https://www.ebi.ac.uk/chebi/searchId.do?chebiId=CHEBI:194136

Thanks!


Transform update_chatbot.html into a Stunning, Interactive User Experience

Expected Updates:

Apply a gradient background for enhanced visual aesthetics.
Update form input fields with animated labels and modern styling.
Add hover effects and smooth transitions to buttons and form elements.
Include a back button with visual spark animations for interaction.
Ensure the design is fully responsive and user-friendly.

Share design which you want to implement

I have designed something

ok to pull request?

Ok assigning then

@kom-senapati
I created the entire update_chatbot.html page from scratch, including forms, animations, and responsive design. Given the scope of the work, I believe it fits the Level 2 category rather than Level 1. Please update the label accordingly.


gha: disable the requires-dep-audit-review action

We're not currently using this action as a way to enforce dep audits so
lets disable it for now in order to reduce noise on PRs.

/land p=low

/land p=low

/cancel

/cancel

/land

/land

:broken_heart: Test Failed - commit-workflow

:broken_heart: Test Failed - commit-workflow

/land

/land