There should also be something in the cleanup task for removing entries in membership where the user no longer exists. In the production we.riseup.net we have some scripts that remove users via SQL directly, but were missing that part (now fixed) and it would have been good if cleanup had seen them too.
Also remove_dead_memberships
seems to have a desc that was cut and pasted from remove_dead_federatings
but not changed.
Riseup we's onionsite, at address http://zkdppoahhqu5ihjqd4qqvyfd2bm4wejrhjosim67t6yopl77jitg2nad.onion/, is not working. The accused error follows:
Details: 0xF0 — The requested onion service descriptor can't be found on the hashring and therefore the service is not reachable by the client.
I understand that this is not the repository for We, but for Crabgrass, but I didn't know anywhere else to report this. If there is a more appropriate place, I'll go there and delete this.
Thanks!
In the same page I noticed two other errors:
href
. My guess is that it is because of an extra space after the bracket:+ * jump to [crows -> do/static/greencloth #murder]
- * jump to [ crows -> do/static/greencloth #murder]
a) Useful Help can be found at https://textile-lang.com/doc/tables (of course I did not test that all, but for example the Textile Link input (editable) I saw there also works in Crabgrass for "tel:+49...." hyperlinks
b) May be that Syntax help should become a quite normal Wiki page?
On the page to view memberships (e.g. /groups/mygroup/memberships), there are two types of memberships: people (default) and groups (shown when passing view=groups
param) When pagination appears for group memberships, the pagination links do not include the view=groups
param, thus effectively linking to a people page.
Current behavior: When clicking a pagination link on a list of member groups, it goes to the corresponding page of member people
Desired behavior: When clicking a pagination link on a list of member groups, it should go the corresponding page of member groups
I had created a council with only me as a member. Then I deleted the council. Then I tried to create a new council. The council create page did not display. Instead it says pending request to create council. I can only delete my request for creating the council.
My group is strongly considering using the "council ownership" tactic to protect pages for archival, but now we can no longer create a council because my original test council was deleted. No other member seems to be able to create a council and their page renders Council:None.
Can you fix tthis for us? Or are we going to have to create an entirely new group and copy everything over just so we can make a council again?
azul (334c8b25) at 05 May 17:15
fix: duplicate loading of net-protocol.
azul (f7443f72) at 05 May 16:41
fix: pundit deprecation notice
azul (50357c99) at 08 Apr 16:48
fix(test): Minitest now handles kwargs differently from hash
... and 5 more commits
I was testing some privilege related things, and I destroyed a group after removing a user from a group. The removed user's notices had not been dismissed, and when (after the group had been destroyed) I tried to hide the notice - following message was displayed:
Changes could not be saved
There are problems with the following fields
Redirect object can't be blank"
Now the notice just hangs out at the top of https://we.riseup.net/me and can't be removed. This also prevents the "Dismiss All" button from being used to clear other notices.
micah (dcb897e1) at 21 Jan 19:02
Make sure we have the newer bundler installed.
... and 1 more commit
azul (cf56de46) at 21 Jan 13:52
Ensure the linux version of libv8-node gets installed
mini_racer depends on libv8-node, this uses a compiled binary. Bundler should automatically install the linux version but instead uses the linux-musl one.
There are a few issues documenting this behavior
https://github.com/rubyjs/mini_racer/issues/218 https://github.com/rubyjs/libv8-node/issues/5
Setting up the platform will make this usable under linux (ugly, but a non resolved issue will break deployment with ruby 2.5
Thanks guido!
azul (9226d21f) at 21 Jan 13:38
fix: CGI escape page urls
azul (7c02f151) at 31 Dec 12:37
update: use rails 6.1
azul (4afc6e17) at 31 Dec 12:22
update: use rails 6.1