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.

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

Preview is not shown in default project for Python Django stack #15053

Open
4 of 23 tasks
Katka92 opened this issue Oct 31, 2019 · 6 comments
Open
4 of 23 tasks

Preview is not shown in default project for Python Django stack #15053

Katka92 opened this issue Oct 31, 2019 · 6 comments
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@Katka92
Copy link
Contributor

Katka92 commented Oct 31, 2019

Describe the bug

When the default project in Python Djnago stack is built, the web page is opened but the page is not here.

Che version

  • latest - 7.3.1
  • nightly
  • other: please specify

Steps to reproduce

  1. Create Python Django stack with default project
  2. Run the application (run commands: install dependencies, migrate, run server)
  3. The page is opened but not loaded correctly

Expected behavior

The page should be loaded correctly.

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Screenshots

Screenshot from 2019-10-31 16-26-25

Installation method

  • chectl
    server:start --platform minikube -i eclipse/che-server:7.3.1 -t ${WORKSPACE}/deploy --k8spodreadytimeout=180000 --listr-renderer=verbose where the ${WORKSPACE} is a path to Che with 7.3.1 tag checkouted.
  • che-operator
  • minishift-addon
  • I don't know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify
@Katka92 Katka92 added the kind/bug Outline of a bug - must adhere to the bug report template. label Oct 31, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 31, 2019
@RomanNikitenko
Copy link
Member

preview_bug

@tsmaeder tsmaeder added team/languages severity/P1 Has a major impact to usage or development of the system. severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 31, 2019
@tolusha
Copy link
Contributor

tolusha commented Nov 4, 2019

It is the case when web page doesn't work in preview and has to be opened in a separate tab.

@schwingkopf
Copy link

I get the exact same error, in preview as well as separate tab in firefox.

@tsmaeder tsmaeder mentioned this issue Dec 18, 2019
28 tasks
@tsmaeder tsmaeder mentioned this issue Jan 8, 2020
35 tasks
@tsmaeder tsmaeder mentioned this issue Jan 23, 2020
36 tasks
@ScrewTSW
Copy link
Member

@tolusha Yes. It works outside of the preview, but because the site returns 404 HTML code, the Theia Preview just shows the usual 404 screen, even though the site also returns web page content.

I can see the proper web site in firefox and chrome, but Theia just has the blank 404 screen

@ScrewTSW
Copy link
Member

I think there is also a same-origin policy set in the example which prevents the page to be loaded inside an iframe

@dmytro-ndp dmytro-ndp removed the severity/P2 Has a minor but important impact to the usage or development of the system. label Apr 2, 2020
@ericwill ericwill added severity/P2 Has a minor but important impact to the usage or development of the system. and removed severity/P1 Has a major impact to usage or development of the system. labels Oct 20, 2020
@che-bot
Copy link
Contributor

che-bot commented Apr 26, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 26, 2021
@ericwill ericwill added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Apr 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

10 participants