Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Misleading message in starting log #7296

Closed
jgbarah opened this issue May 26, 2016 · 4 comments
Closed

Misleading message in starting log #7296

jgbarah opened this issue May 26, 2016 · 4 comments
Labels
chore dev Team:Operations Team label for Operations Team

Comments

@jgbarah
Copy link
Contributor

jgbarah commented May 26, 2016

When launching Kibana (current master HEAD) as

npm start

I see the following mesages:

[...]
managr    log   [09:58:44.558] [info][listening] basePath Proxy running at https://localhost:5601/xed
[...]
server    log   [09:58:51.555] [info][listening] Server running at https://localhost:5603
[...]

The first problem is that the second message above is the only one you see when launching in a 20-line console. Reading it, it seems that Kibana will be available at https://localhost:5603 But that's not the case. It is at https://localhost:5601 as the first message seems to tell.

The second problem is that both messages are difficult to interpret, and given that they are the first think you see from Kibana when trying to run it, maybe having messages simpler to interpret would be a good thing.

So, in short, I would change both messages, and make it clear, probably in an additional message, that Kibana is ready to load in the browser at https://localhost:5601 so when you see it bootstrapping for the first time, it is clear how to access it in the browser.

In addition to this, I would a note to the CONTRIBUTING.md file explaining the url to load in the browser.

All these may seem minor issues, but I spent a good deal of time, and some questions, thinking that I had trouble with my Kibana installation, until I realized everything was fine, but I was just pointing my browser at the wrong url.

If you want, I can prepare a simple pull request for the CONTRIBUTING.md file.
@epixa
Copy link
Contributor

epixa commented May 26, 2016

This is definitely confusing, and I'd love to see it fixed up. This is a dev-only issue though since the basePath proxy is not used in release builds, but it's still worth making this all more clear.

And an update to the CONTRIBUTING.md file would be a great first step, thanks!

@bevacqua
Copy link
Contributor

Agreed about the P3 -- I was going to reply something like that 💯

@jgbarah jgbarah mentioned this issue May 26, 2016
Closed
@epixa epixa removed the P3 label Apr 25, 2017
@timroes timroes added the Team:Operations Team label for Operations Team label Aug 13, 2018
@timroes
Copy link
Contributor

timroes commented Aug 13, 2018

cc @elastic/kibana-operations Is this still something we want to look into, or can we close this?

@tylersmalley
Copy link
Contributor

Closing as we no longer output the base path proxy information in the info logs.

cee-chen added a commit that referenced this issue Nov 3, 2023
@cee-chen
Upgrade EUI to v90.0.0 (#170179)
d079e95 
`v89.1.0`⏩`v90.0.0`

The majority of changes in this PR come from:

- **EuiContextMenu** being converted to Emotion
(elastic/eui#7312). If your usage of
`EuiContextMenu` was significantly affected, we recommend pulling down
this PR and QAing it locally.

- `defaultProps` being removed from some very widespread components,
particularly **EuiButton**, in anticipation of React's upcoming
deprecation.
(elastic/eui@b7dc9b4)
**NOTE**: This only affected Enzyme snapshots, and did not affect
production behavior.

[Commits](https://github.com/elastic/kibana/pull/170179/commits) have
been broken up by component changes as well as types of changes.

---

## [`90.0.0`](https://github.com/elastic/eui/tree/v90.0.0)

- Updated the `eventColor` prop on `EuiCommentEvent` to apply the color
to the entire comment header.
([#7288](elastic/eui#7288))
- Updated `EuiBasicTable` and `EuiInMemoryTable` to support a new
controlled selection API: `selection.selected`
([#7321](elastic/eui#7321))

**Bug fixes**

- Fixed controlled `EuiFieldNumbers` not correctly updating native
validity state ([#7291](elastic/eui#7291))
- Fixed `EuiListGroupItem` to pass `style` props to the wrapping `<li>`
element alongside `className` and `css`. All other props will be passed
to the underlying content.
([#7298](elastic/eui#7298))
- Fixed `EuiListGroupItem`'s non-transitioned transform on hover/focus
([#7298](elastic/eui#7298))
- Fixed `EuiDataGrid`s with `gridStyle.stripes` sometimes showing buggy
row striping after being sorted
([#7301](elastic/eui#7301))
- Fixed `EuiDataGrid`'s `gridStyle.rowClasses` API to not conflict with
`gridStyle.stripes` if dynamically updated
([#7301](elastic/eui#7301))
- Fixed `EuiDataGrid`'s `gridStyle.rowClasses` API to support multiple
space-separated classes
([#7301](elastic/eui#7301))
- Fixed `EuiInputPopover` not calling `onPanelResize` callback prop
([#7305](elastic/eui#7305))
- Fixed `EuiDualRange` incorrectly positioning highlights when rendered
with `showInput="inputWithPopover"`
([#7305](elastic/eui#7305))
- Fixed `EuiTabs` incorrectly wrapping text when it should instead
either scroll or truncate
([#7309](elastic/eui#7309))
- `EuiContextMenu` now renders text colors correctly when used within an
`EuiBottomBar` ([#7312](elastic/eui#7312))
- Fixed the width of `EuiSuperDatePicker`'s Absolute date picker
([#7313](elastic/eui#7313))
- Fixed `EuiDataGrid` cells visually cutting off overflowing content a
little too quickly ([#7320](elastic/eui#7320))

**Deprecations**

- Deprecated `EuiBasicTable` and `EuiInMemoryTable`'s ref `setSelection`
API. Use the new `selection.selected` API instead.
([#7321](elastic/eui#7321))

**Breaking changes**

- Removed `EuiPageTemplate_Deprecated`, `EuiPageSideBar_Deprecated`, and
`EuiPageContent*_Deprecated`
([#7265](elastic/eui#7265))
- Removed the `ghost` color option from `EuiButton`, `EuiButtonEmpty`,
and `EuiButtonIcon`. Use an `<EuiThemeProvider colorMode="dark">`
wrapper and `color="text"` instead.
([#7296](elastic/eui#7296))

**Dependency updates**

- Updated `refractor` to v3.6.0
([#7127](elastic/eui#7127))
- Updated `rehype-raw` to v5.1.0
([#7127](elastic/eui#7127))
- Updated `vfile` to v4.2.1
([#7127](elastic/eui#7127))

**Accessibility**

- `EuiContextMenu` now correctly respects reduced motion preferences
([#7312](elastic/eui#7312))
- `EuiAccordion`s no longer attempt to focus child content when the
accordion is externally opened via `forceState`, but will continue to
focus expanded content when users click the toggle button.
([#7314](elastic/eui#7314))

**CSS-in-JS conversions**

- Converted `EuiContextMenu`, `EuiContextMenuPanel`, and
`EuiContextMenuItem` to Emotion; Removed `$euiContextMenuWidth`
([#7312](elastic/eui#7312))
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore dev Team:Operations Team label for Operations Team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@tylersmalley @epixa @timroes @bevacqua @jgbarah