Thanks for reviewing this diff, and apologies for my late reply and not closing it, I didn't find out how to close it when I first saw your message.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Apr 22 2019
Apr 21 2019
Apr 20 2019
Apr 19 2019
There are a million different file formats out there, why are we rendering Markdown and Jupyter notebooks and not something else?
I think we need to have a conversation about how we decide to add support for rendering specific file formats in the webapp.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/402/ for more details.
Update: Check that hljs supports the notebook language prior calling the highlight function
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/401/ for more details.
Update: last CSS polishing
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/209/ for more details.
no need to keep the cli plugins in a dict
So, from what I understand, the subcommand name is set by the name of the function in the plugin, when the swh.command() decorator is called.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/400/ for more details.
Update: Fix url in notebook.css comment
Build has FAILED
Build is green
See https://jenkins.softwareheritage.org/job/DDEP/job/tox/130/ for more details.
rebased
Add requests to requirements.txt since it does come with swh.core any more
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/399/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/208/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/398/ for more details.
- address comments
kill the PostresHandler instead of "shuffling it around" (© olasd)
Update: address latest olasd comment ('..' => '../')
In D1427#31359, @olasd wrote:The PostgresHandler has been dead code for two years, I think we can just remove it rather than shuffling it around.
Build has FAILED
The PostgresHandler has been dead code for two years, I think we can just remove it rather than shuffling it around.
Are there any blockers left? It would be really nice to roll this out in the very near future.
Build is green
See https://jenkins.softwareheritage.org/job/DDEP/job/tox/127/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/207/ for more details.
Fix commit messages
If we remove it from the main website, we should also remove it everywhere for consistency.
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/205/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DCORE/job/tox/203/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/397/ for more details.
Build is green
See https://jenkins.softwareheritage.org/job/DWAPPS/job/tox/396/ for more details.
Rebase
- address comments
@anlambert: are you proposing to remove it from everywhere or only from www.s.o ?
Resolved with last deployment on HAL
Thank you both for dealing with this bug quickly!
How about dropping the top navbar ? It is not consistent across all of our websites (it is missing on our forge for instance) and all links it contain can be easily found from our main website.
This also requires we can install only a very light base version of swh.core (typically without db or aiohttp/flask dependencies).
A possible way of doing such a thing is to have a master swh command declared in this package as the main entry point: the swh command group (using click) which defines a few very command command line options (like --log-level), and a mechanism to load installed SWH cli plugins via setuptools' pkg_resources
The fix has been deployed to moma.