Opened 5 months ago

Last modified 10 days ago

#33113 new enhancement

Meta-ticket: Gitpod usability improvements

Reported by: mkoeppe Owned by:
Priority: major Milestone: sage-9.7
Component: user interface Keywords:
Cc: gh-tobiasdiez, dimpase Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by mkoeppe)

  • Added gitpod badge to trac tickets: Image https://img.shields.io/badge/-Gitpod-908a85?logo=gitpod Link https://gitpod.io/#https://github.com/sagemath/sagetrac-mirror/tree/<branch>
  • #33450 Improve vs code config
  • #33589 Gitpod: track remote trac branch
  • #33739 Migrate gitpod to conda
  • #33613 Gitpod: Install git-trac-command
  • Prebuild of develop branch is not available (probably because the prebuild of the develop branch still uses the old docker image)
  • #32753 Prefer Linux package manager over linuxbrew (or remove linuxbrew from the Docker image)
  • in the terminal, viewing graphics silently does nothing
    sage: polytopes.cube().show()
    Launched html viewer for Graphics3d Object
    sage: polytopes.regular_polygon(5).show()
    Launched png viewer for Graphics object consisting of 7 graphics primitives
    
  • Remove popup notifications:
    • "Snooty language server is not installed or out of date."
  • Extensions for:
    • Cython
    • autoconf

Change History (33)

comment:1 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:2 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:3 Changed 5 months ago by mkoeppe

  • Dependencies changed from #33103 to #30677, #33103

comment:4 Changed 5 months ago by gh-tobiasdiez

  • Description modified (diff)

comment:5 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:6 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:7 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:8 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:9 Changed 5 months ago by mkoeppe

  • Description modified (diff)
  • Milestone changed from sage-9.5 to sage-9.6

comment:10 Changed 5 months ago by mkoeppe

  • Description modified (diff)

comment:11 Changed 4 months ago by mkoeppe

  • Description modified (diff)

comment:12 Changed 4 months ago by mkoeppe

  • Cc dimpase added

comment:13 Changed 4 months ago by mkoeppe

  • Description modified (diff)

comment:14 Changed 3 months ago by mkoeppe

  • Summary changed from gitpod usability improvements to Meta-ticket: Gitpod usability improvements

comment:15 Changed 3 months ago by mkoeppe

  • Dependencies #30677, #33103 deleted

comment:16 Changed 3 months ago by mkoeppe

  • Description modified (diff)

comment:17 Changed 3 months ago by mkoeppe

  • Description modified (diff)

comment:18 Changed 3 months ago by mkoeppe

Ticket branches are often based on an older beta version. Given that we build on top of the Docker image for the current beta version (dev), shouldn't we attempt to merge the branch into the base of the Docker image and build that?

comment:19 follow-up: Changed 3 months ago by gh-tobiasdiez

Isn't this what the prebuild at gitpod is essentially doing?

comment:20 Changed 3 months ago by mkoeppe

  • Description modified (diff)

comment:21 in reply to: ↑ 19 Changed 3 months ago by mkoeppe

Replying to gh-tobiasdiez:

Isn't this what the prebuild at gitpod is essentially doing?

No, it's not merging. It's building the top of the branch.

comment:22 Changed 3 months ago by gh-tobiasdiez

Then I don't understand what you mean. The docker image used by gitpod is the same for all branches.

comment:23 Changed 3 months ago by mkoeppe

Yes, it is, and it is based on the latest beta.

The branch that is being tested, however, may be based on a much older beta. When building this branch, it will downgrade packages to the versions recorded in that older beta.

comment:24 Changed 3 months ago by gh-tobiasdiez

Yes, that's the current behavior, right? So what are you proposing to improve there?

comment:25 follow-up: Changed 8 weeks ago by mkoeppe

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

comment:26 Changed 8 weeks ago by gh-tobiasdiez

  • Description modified (diff)

comment:27 in reply to: ↑ 25 ; follow-ups: Changed 8 weeks ago by gh-tobiasdiez

Replying to mkoeppe:

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

So you want to merge the develop branch into the branch that is open in gitpod?

Note also that gitpod prebuild the branch when a new commit arrives. Thus the docker image used is the one that had been published when the branch had its last commit.

comment:28 Changed 8 weeks ago by gh-tobiasdiez

  • Description modified (diff)

comment:29 in reply to: ↑ 27 Changed 8 weeks ago by mkoeppe

Replying to gh-tobiasdiez:

Replying to mkoeppe:

As I said in comment:18, to merge the current branch into the branch from which the Docker image has been built.

So you want to merge the develop branch into the branch that is open in gitpod?

Technically not the develop branch but the ref from which the Docker image has been built. Most of the times, that's the same.

comment:30 in reply to: ↑ 27 Changed 8 weeks ago by mkoeppe

Replying to gh-tobiasdiez:

Note also that gitpod prebuild the branch when a new commit arrives. Thus the docker image used is the one that had been published when the branch had its last commit.

Yes, that's fine.

comment:31 Changed 8 weeks ago by mkoeppe

  • Description modified (diff)

comment:32 Changed 3 weeks ago by mkoeppe

  • Milestone changed from sage-9.6 to sage-9.7

comment:33 Changed 10 days ago by mkoeppe

  • Description modified (diff)
Note: See TracTickets for help on using tickets.