{23} Trac comments (3729 matches)

Results (3001 - 3100 of 3729)

← 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 →
Ticket Posixtime Author Newvalue
#689 1287392122000000 johnbywater Referencing ticket #572 has changed sprint.
#650 1287391932000000 pudo included since cset:781ef73e61cc
#695 1287391751000000 pudo This is triggered by an issue where having local blinker notifications without asynchronous notifications will break indexing. The issues cause is still unknown, but one possible fix is running CKAN with a queue enabled, synchronous indexing on and no queue consumers attached. Not a real solution, but made possible in cset:a065dbc8041c
#681 1287160548000000 dread Looks like integration with drupal is the problem here. I'm writing tests.
#683 1287142289000000 dread Done apart from ultrastable - not in use at moment.
#694 1287087801000000 wwaites Installed postgres client from lenny backports on eu3. Can now access without problem, web sites still appear to work (e.g. fr.ckan.net). Note that the backup process runs directly on eu5 now as mentioned by rgrp in email
#662 1286993727000000 johnbywater It might be natural for the locator of the rating for a package to be "/package/{id}/rating". I've got not idea what I meant by "An issue for CKAN too." I may have intended to log this againt ckanclient. Anyway, it seems to be just a CKAN thing. :-) I think I would like to do this: $data = c.package_register_post({'name': 'example'}) $data['title'] = 'Example' c.package_entity_put($data['id'], $data) and this: $data = c.package_entity_get('example') $data['title'] = 'Example' c.package_entity_put($data['id'], $data) I don't think either work. We could write a test for each. I think this does work: $data = c.package_entity_get('example') $data = c.package_entity_put($data['id'], $data) $data['title'] = 'Old Example' c.package_entity_put($data['id'], $data) Which is inconsistent. The reason is that the data returned by the update operation ("entity put") isn't given the same treatment as the read and create operations, which adds various read-only values. That's as far as I got. I inferred that one or several of the read-only values, when present in the update request data, cause the update to fail. I'm not sure how it fails. Rather than cutting down the response data, we could make the update call more robust. One fix would pick out from the request package data only the attributes that are permitted. A alternative fix would make what ever is choking on the extra values ignore them. I mean, ids are read-only, but we wouldn't want to reject an update because it has an id in the data. We do need to be careful about loading up the package entity data, but the 'id' is read-only and we aren't going to quible about that being present in the data of an update request (even if it doesn't match the referenced entity). I would rather not support "replace the entire package" with especial functionality and documentation. I think the model create/update/delete, where update is "set attributes" is sufficient, simple, and fairly optimal. To obliterate all registerd values without deleting, I would get the package entity data, loop over the keys and set the values to '', [] or {} depending on the type, and then PUT the entity. We could write a test for that.
#662 1286991079000000 dread I agree we should not have the 'read-only' things like Ratings in the default returned Package Entity. What do you think of having a parameter to be able to get these if you want them though? Do you mean you *can* re-post the *entity* post response? Not sure what you mean by "An issue for CKAN too."? In addition to this ticket, what do you think about changing the behaviour of the Package Entity PUT/POST, so that you replace the entire Package, not just the fields you specify? So you don't keep left-over values, just because you didn't specify them as null?
#546 1286896814000000 anonymous [http://www.salle-de-poker-legal.com Jouer au poker en ligne]
#546 1286896450000000 anonymous [http://www.bonus-pokers.eu Poker en ligne]
#546 1286896167000000 anonymous [http://www.pokers.li Jeux de poker en ligne]
#693 1286831155000000 wwaites Fixed with cset:1e53d160abb6 If expires argument is set, Cache-Control headers get set -- so remove any values, default or otherwise from your configs. ETag gets set to last-modified.
#669 1286789428000000 johnbywater Moved from sprint 1.2.7
#670 1286789428000000 johnbywater Moved from sprint 1.2.7
#671 1286789428000000 johnbywater Moved from sprint 1.2.7
#672 1286789428000000 johnbywater Moved from sprint 1.2.7
#650 1286789277000000 johnbywater Moved from sprint 1.2.7
#569 1286786420000000 johnbywater Moved from sprint 1.2.6
#570 1286786420000000 johnbywater Moved from sprint 1.2.6
#572 1286786420000000 johnbywater Moved from sprint 1.2.6
#610 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#611 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#612 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1286786420000000 johnbywater Referencing ticket #569 has changed sprint.
#615 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1286786420000000 johnbywater Referencing ticket #570 has changed sprint.
#621 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#622 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#645 1286786420000000 johnbywater Referencing ticket #572 has changed sprint.
#673 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#675 1286786420000000 johnbywater Referencing ticket #568 has changed sprint.
#677 1286786420000000 johnbywater Moved from sprint 1.2.6
#678 1286786420000000 johnbywater Moved from sprint 1.2.6
#679 1286786420000000 johnbywater Moved from sprint 1.2.6
#681 1286786420000000 johnbywater Moved from sprint 1.2.6
#682 1286786420000000 johnbywater Moved from sprint 1.2.6
#568 1286786419000000 johnbywater Moved from sprint 1.2.6
#623 1286786419000000 johnbywater Referencing ticket #568 has changed sprint.
#674 1286786419000000 johnbywater Referencing ticket #568 has changed sprint.
#684 1286388346000000 dread Referencing ticket #683 has changed sprint.
#686 1286388346000000 dread Referencing ticket #683 has changed sprint.
#685 1286388345000000 dread Referencing ticket #683 has changed sprint.
#448 1286386256000000 dread Has this all been finished yet?
#373 1286376071000000 dread Done
#454 1286376044000000 dread Done
#536 1286376029000000 dread I did this a few weeks ago.
#568 1285957164000000 johnbywater Moved from sprint 1.2.5
#569 1285957164000000 johnbywater Moved from sprint 1.2.5
#572 1285957164000000 johnbywater Moved from sprint 1.2.5
#611 1285957164000000 johnbywater Referencing ticket #569 has changed sprint.
#612 1285957164000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1285957164000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1285957164000000 johnbywater Referencing ticket #569 has changed sprint.
#621 1285957164000000 johnbywater Referencing ticket #568 has changed sprint.
#645 1285957164000000 johnbywater Referencing ticket #572 has changed sprint.
#667 1285925476000000 dread This was done when caching was switched off for a few hours it seems. Still, it is worth investigating this.
#428 1285757316000000 dread This was achieved a couple of weeks ago
#429 1285757274000000 dread Will Waites fixed this a couple of weeks ago
#462 1285757238000000 dread Available at http://data.gov.uk/data/dumps
#509 1285757116000000 dread Will Waites did this a couple of weeks agoWill Waites did this a couple of weeks ago
#610 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1285629333000000 johnbywater Referencing ticket #570 has changed sprint.
#522 1285595317000000 pudo Still missing some internal authorization work but on the UI side, things are mostly functional. cf. http://bitbucket.org/okfn/ckanextiati/changeset/b2588091fa56 ff
#525 1285595080000000 pudo As of now, PE creation can only be done by sysadmins. When opened to normal users, they will not be able to set the group type and thus moderation will be required of sysadmins.
#524 1285594971000000 pudo fixed as of cset:470d1e1c4460
#460 1285489964000000 rgrp To add to this ticket I note that package 'owners' are entitled to see State not just system sysadmins (this allows owners to delete packages).
#460 1285443859000000 [email protected] I believe the initial report is incorrect. It states that the status was changed from "active" to "deleted". I believe that it was actually changed from "active" to "None". This might indicate a bug in the code: The value of the status field is lost.
#560 1285430085000000 [email protected] I think I'm seeing a variation on this behavior: I'm retrieving the packages in the lodcloud group (http://ckan.net/api/rest/group/lodcloud) and finding bibbase, and then fetching the package details (http://ckan.net/api/rest/package/bibbase) and getting a 403 Access Denied. If access to the package isn't available I would think it wouldn't be listed in the lodcloud group response.
#630 1285348178000000 johnbywater Referencing ticket #572 has changed sprint.
#626 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#628 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#629 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#632 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#635 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#645 1285348177000000 johnbywater Referencing ticket #572 has changed sprint.
#633 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#634 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#635 1285348167000000 johnbywater Referencing ticket #572 has changed sprint.
#621 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#622 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#623 1285348152000000 johnbywater Referencing ticket #568 has changed sprint.
#655 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#656 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#657 1285252726000000 johnbywater Referencing ticket #654 has changed sprint.
#658 1285252726000000 johnbywater Referencing ticket #655 has changed sprint.
#611 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
#612 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
#613 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
#614 1285199361000000 johnbywater Referencing ticket #569 has changed sprint.
#610 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#615 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#616 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#617 1285199168000000 johnbywater Referencing ticket #570 has changed sprint.
#204 1285082169000000 anonymous [http://www.casinotop10.fr Top10 des casinos sur internet]
← 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 →
Note: See TracReports for help on using and creating reports.