You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2017/11/09 18:01:42 UTC
[allura:tickets] #8169 Updating markdown cache should not affect last_updated
---
** [tickets:#8169] Updating markdown cache should not affect last_updated**
**Status:** in-progress
**Milestone:** unreleased
**Created:** Thu Nov 09, 2017 04:32 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 09, 2017 04:32 PM UTC
**Owner:** Dave Brondsema
If markdown rendering (e.g for a ticket, comment, whatever) does not exceed `markdown_cache_threshold` it will not save the result to mongo. Later if someone visits the ticket page, and the markdown rendering takes longer and **is** saved to mongo, it currently updates `last_updated` but it shouldn't.
To reproduce this reliably, comment out `markdown_cache_threshold` in your `.ini` and create some content. Then set `markdown_cache_threshold = 0` and visit the page with the content. The updated date will be changed - as can be seen on your user profile list of projects.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8169 Updating markdown cache should not affect last_updated
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: in-progress --> review
- **Comment**:
Fix on branch db/8169
---
** [tickets:#8169] Updating markdown cache should not affect last_updated**
**Status:** review
**Milestone:** unreleased
**Created:** Thu Nov 09, 2017 04:32 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 09, 2017 04:32 PM UTC
**Owner:** Dave Brondsema
If markdown rendering (e.g for a ticket, comment, whatever) does not exceed `markdown_cache_threshold` it will not save the result to mongo. Later if someone visits the ticket page, and the markdown rendering takes longer and **is** saved to mongo, it currently updates `last_updated` but it shouldn't.
To reproduce this reliably, comment out `markdown_cache_threshold` in your `.ini` and create some content. Then set `markdown_cache_threshold = 0` and visit the page with the content. The updated date will be changed - as can be seen on your user profile list of projects.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #8169 Updating markdown cache should not affect last_updated
Posted by Kenton Taylor <kt...@slashdotmedia.com>.
- **status**: review --> closed
---
** [tickets:#8169] Updating markdown cache should not affect last_updated**
**Status:** closed
**Milestone:** unreleased
**Created:** Thu Nov 09, 2017 04:32 PM UTC by Dave Brondsema
**Last Updated:** Thu Nov 09, 2017 06:03 PM UTC
**Owner:** Dave Brondsema
If markdown rendering (e.g for a ticket, comment, whatever) does not exceed `markdown_cache_threshold` it will not save the result to mongo. Later if someone visits the ticket page, and the markdown rendering takes longer and **is** saved to mongo, it currently updates `last_updated` but it shouldn't.
To reproduce this reliably, comment out `markdown_cache_threshold` in your `.ini` and create some content. Then set `markdown_cache_threshold = 0` and visit the page with the content. The updated date will be changed - as can be seen on your user profile list of projects.
---
Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/
To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.