When I try to debug a query

fromAll().
when({
$init : function(s,e) {return {count : 0}},
$any : function(s,e) {throw "foo"; s.count+=1}
})

I get dropped in the same place as in old ui but when I try to step in on the handler() I end up in the following code instead of the query code

    function defaultEventHandler(state, eventEnvelope) {
        return eventEnvelope.isJson ? eventEnvelope.body : { $e: eventEnvelope.bodyRaw };
    }

If you return to a stale client session, where ES has restarted, and thus the temporary projection(s) no longer exist the page just sticks at "Loading definitions..", and the console shows the below. Perhaps it would be better to display a message or reset the page?

The button style on the "enable" button here is wrong - I suspect it's missing a class?

We should rethink either the style (perhaps a toggling button?) or the location of the "Include Queries" option.

I created a projection that would link all events of certain types into one stream (similar to below).

fromAll()
.when({
"TYPE2": function(s, e) {
linkTo("proj-events",e)
},
"TYPE1": function(s, e) {
linkTo("proj-events",e)
},
})

When I go to the stream page for this:
http://es/web/index.html#/streams/proj-events
and click on one of the events it takes me to the stream of the original event, but at the position of the event in the proj-events stream.

1 6@stream-1 -> Links to http://es/web/index.html#/streams/stream-1/1, should be http://es/web/index.html#/streams/stream-1/6
0 0@stream-0 -> Links to http://es/web/index.html#/streams/stream-0/0

Looks much better overall.

One small detail. The state keeps trying to update after the query completes.

• Run Query
• Open developer tools
• Enter a valid query

fromCategory("Something").when({
    $init : function(s,e) { return { Count : 0 } },
    $any : function(s,e) { s.Count++; return s; }});

• Hit DEBUG
• Delete the query
• Hit UPDATE
• Paste the query back in

fromCategory("Something").when({
    $init : function(s,e) { return { Count : 0 } },
    $any : function(s,e) { s.Count++; return s; }});

• Hit UPDATE
• Wait until refreshes with the query in the window
• Hit RUN STEP

Console shows...

[11524,27,16:48:10.658] Read Request Body Failed.
Value cannot be null.
Parameter name: token

Browser shows...

at least two files cannot be load:

• theme-monokai.js
• mode-javascript.js

It is very hard to select text from inside the EventStore UI, because after 1-2 seconds either the selection vanishes or selects nearly everything. It seems like the UI auto-refreshes every second or so including replacing high amounts of DOM elements and thus invalidates selections during this time, thus only allowing a time window of 1 second to select something.

Tested in Chrome and Internet Explorer.

It's so easy to forget to hit UPDATE after editing your query and then hitting RUN STEP, I wonder if disabling the RUN STEP button if the query has been edited is an idea to consider? Or displaying a message asking if to continue with RUN STEP if the query has been edited?

Sometimes I get double queries run see below:

Name Status Mode Done Read / Write in Progress Write Queues Partitions Cached Rate (events/s) Events
Processed Buffered
$by_category Running Continuous 100.0% 0 / 0 0 / 0 1 0.0 234035 0
$by_event_type Running Continuous 100.0% 0 / 0 0 / 0 1 0.0 390035 0
$stream_by_category Running Continuous 100.0% 0 / 0 0 / 0 1 0.0 2035 0
$streams Running Continuous 100.0% 0 / 0 0 / 0 1 0.0 2035 0
$users Running Continuous 100.0% 0 / 0 0 / 0 1 0.0 0 0
8a51d32a-c37f-4593-9084-b6cd1565893c Running Transient 18.8% 0 / 0 0 / 0 0 23.2 960 46
8a51d32a-c37f-4593-9084-b6cd1565893c-slave-0 Running Transient 19.9% 0 / 0 0 / 0 1 4827.7 335514 3360
8a51d32a-c37f-4593-9084-b6cd1565893c-slave-1 Running Transient 19.9% 0 / 0 0 / 0 1 4554.4 342248 2466
8a51d32a-c37f-4593-9084-b6cd1565893c-slave-2 Running Transient 19.9% 0 / 0 0 / 0 0 3400.7 357888 0
902fa7b6-5e8b-4eb3-ba74-b59c4edfbcc6 Running Transient 18.8% 0 / 1 0 / 0 0 13.9 547 459
902fa7b6-5e8b-4eb3-ba74-b59c4edfbcc6-slave-0 Running/Paused Transient 19.9% 0 / 0 0 / 0 1 4299.6 199095 3043
902fa7b6-5e8b-4eb3-ba74-b59c4edfbcc6-slave-1 Running Transient 19.9% 0 / 0 0 / 0 1 4554.9 203003 2823
902fa7b6-5e8b-4eb3-ba74-b59c4edfbcc6-slave-2 Running Transient 19.9% 0 / 0 0 / 0 1 6427.5 217517 3756

From trying to reproduce it seems that it happens when I have an existing query in the UI (eg let query run to end) when you then click "run query" it will tell you an error but the query is actually running. You can see this by keeping a tab open on projections with queries selected.

Some of the buttons in the stream browser are unstyled (or styled as lists):

as title

We get a blank display screen upon clicking next when that would result in hitting a feed head. To reproduce:

• Start fresh event store, navigate using UI to http://localhost:2113/web/index.html#/streams/$stats-127.0.0.1:2113/metadata
• Click the next link
• See the empty container page as below.

From EventStore/EventStore#542

It would be useful here to make the left hand column only as wide as is necessary and give the projections editor more space

With EventStore 2.0.1 it was possible to browse the $et- and $ce- stream via webui and navigate to the original streams of the events. That was quiet helpful.

With the new webui of eventstore 3 its not possible anymore. I only see name and links of the actual stream and cannot navigate to the original stream. Please take a look at the following screenshots that shows the difference:

EventStore 2.0.1:

EventStore 3.0.5:

Event Details:

EventStore 2.0.1:

EventStore 3.0.5:

(Here i can only navigate back to the $ce- stream)

Is it possible to add that functionality back? Thanks!

nothing more than an annoyance of having to type it.

As a small aside, if you hit "Update" more than once in debug mode, it pushes an empty query because it hasn't had time to reload the JS query back into the browser window.

npm WARN unmet dependency ...\EventStore.UI\node_modules\gulp-bower requires gulp-util@'latest' but will load
npm WARN unmet dependency ...\EventStore.UI\node_modules\gulp-util,
npm WARN unmet dependency which is version 3.0.1

basically, change latest to proper version.

Buttons on the top right of the projections details screen are different sizes. This is also true on the editor screen (although only for the back button there).

Work out a method for minifying the UI and bundling all the resources together - it's currently very large and is making the Event Store distribution too big.

Tiny thing, it reports ES as 0.0.0.0 probably better to write "run locally" on footer.

C:\EventStore.UI>gulp connect

module.js:340
throw err;
^
Error: Cannot find module 'gulp-concat'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:280:25)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (C:\EventStore.UI\gulpfile.js:7:14)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)

Source : https://groups.google.com/forum/#!topic/event-store/SvIASvPkkFA

Remove the "You can also post a standard projection" link unless there's a good reason to keep it around.

when on /streams/$$$... we should not display metadata link, to /streams/$$$.../metadata as there is nothing up there for it.

url: ttp://127.0.0.1:2113/streams/%24%24%24users/metadata?embed=tryharder

Status Code: 400 Stream must be non-empty string and should not be metastream

what we can do is, query for metadata and if status 400, do not display a link, or this link should not be returned from ES in links array.

We need to remove the popups and implement a decent notification system.

Really I am not that concerned about your last edit points and would prefer you to not override mine.

Greg

(Note: this is something that's todo and will likely require server change, just putting it here so it's not forgotten)

Like the new UI, but the font actually hurts my eyes (at least on Chrome in Windows). Particularly the bold on the Gossip page. No doubt it looks lovely on the Mac.

I am setting up a evenstore cluster with SSL termination and load balancer on AWS.
My domain is pointing to the loadbalancer which is on 2113 on HTTPS, and LB is redirecting to the instances of ES wich are on HTTP 2113.

Problem is when we try to run any projection in the UI we get this error in console log:

Mixed Content: The page at 'https://my_domain:2113/web/index.html#/projections/http%253A%252F%252Fmy_domain%253A2113%252Fprojection%252F%2524by_event_type' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://my_domain:2113/projection/$by_event_type/result'. This request has been blocked; the content must be served over HTTPS.

For whatever reason UI is trying to access HTTP. Only during starting/stopping the projections. I did not notice anything else behaving badly.
My current reasearch showed that URL is based on the value we use during login. I have checked and the authdata cookie is stored correctly (meaning: with HTTPS).

My guess is if you test it any fromCategory() etc one will but not a basic fromall()

Saw same thing in esquery (looks like how projections return from queries changed) if its a single result use resultUri if its multiple results use resultStreamUri which is an atom feed

see logic here https://github.com/EventStore/EventStore/tree/esquery

Running a query a second time does not seem to work (query not updated)

Selected text in the UI is unselected during screen refresh making it difficult to copy and paste data from the UI.

When attempting to navigate to the URL of a particular stream without being authenticated, the authentication screen comes up however after authentication, it does not redirect back to the originally specified URL.

One more, which I can happily move to a new Issue if you wish?

• Log into http://localhost:2114
• Run query with JS that has an error:

fromCategory("SomeThing").when({
    $init : function(s,e) { return { Count : 0 } },
    $ny : function(s,e) { s.Count++; return s; }});

• The UI doesn't return or update the state - which is understandable - but there is NO feedback in the UI that this failed. Neither does the console show anything
• Hit "DEBUG" (as you would when something doesn't work)
• Hit "Stop"
• Hit "Run Step"

Console says;

[32368,16,16:36:21.131] Error while processing message EventStore.Projections.Core.Messages.EventReader
intSuggested in queued handler 'Projection Core #0'.
Specified method is not supported.

UI says;

Log viewer:
(nothing)

I'd expect here at least the error in the console to come back to the UI, perhaps in the Log Viewer window or something!? What am I missing?

I have a use case where I need to include a rather large blob of escaped json inside my metadata.
Since this is not being wrapped in the Stream Browser, the table is widened to extreme widths (17000 for example), which makes it very hard to use the UI as one has to scroll all the way to the right to close an opened event and other columns like the Type and the Timestamp are also very hard to read/find.

Here is a screenshot to show the problem: https://dl.dropboxusercontent.com/u/19676954/EventStoreUI-Wrap.png

Would be awesome if either one were able to force a text wrap inside the json output field or if this would be scrollable for itself, so one would not move the other controls and outputs so far away when expanded.

When you try deleting a projection there is no immediate feedback on whether it has been successful, although if you check the projection screen it will be gone. After 10-15s it will pop up a message saying "Projection not removed". At no point does the delete projection screen get navigated away from automatically.

Buttons on the projection editor and on the top of the stream browser appear unstyled and have bullet points

Appears same in Safari and Chrome

If the server name has been defaulted to the place the page was served from, the username entry field should have focus by default.

Remove bower_components from repro and fix bower.json so it will not use latest as version - this is already causing issues when trying to update all bower components.

Leaving the UI open for an extended period of time can lead to increased CPU and memory usage across Firefox and Chrome.

We should drop some uris of the form

on streams page etc so that tools like chrome can grab the atom feed :)

I am a bit confused what this screen is for.

@jen20 any idea?

Steps to reproduce:

• Open up fresh event store
• Sign into the UI. Note the version number display:
  
• Refresh the page (I'm using Cmd+R in Safari). Note the lack of version number display:
  

This is related to a discussion on the Event Store Google Group.
https://groups.google.com/forum/#!topic/event-store/DVH4_DnYRZg

We could possibly investigate exposing configuration in the Event Store UI that would allow the user to set the expiration of the auth cookies.