pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
[github.com profile] wohali has been working on issue 664 to add a RTE to the new beta update page, and is ready for more eyeballs to poke at it and try to hit weird/unusual use cases or things that could be improved!

If you have a few, please poke at the new RTE on [github.com profile] wohali's dreamhack. To test it:

* Go to http://www.wohali.hack.dreamwidth.net/ and create an account.
* Go to http://www.wohali.hack.dreamwidth.net/beta to turn on the beta update page and http://www.wohali.hack.dreamwidth.net/update to make a post with it.

The update page should default to RTE on the beta update page. To disable it, go to Settings and check "Completely disable the Rich Text Editor (use plain textarea only)". (Historically speaking, a lot of RTE glitches happened when switching from HTML mode to RTE mode, so it's probably worth testing that a bunch.) Accessibility help is available by pressing Alt+0 (zero) while the editor is focused.

If you run into a problem or want to give feedback, you can comment on this entry. If reporting a problem, please include a link to the entry you made so [github.com profile] wohali can see the markup!
kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila
Every few months, I run through [site community profile] changelog compiling a list of who has been contributing patches to our code repository, with the understanding that this is not a competition, or any sort of "high score" list. It's intended as a guide for casual developers, to discern not only our most prolific contributors, but also those who have contributed to the project most recently and therefore would be more likely to provide a timely, informed response to development questions. That is why the list is sorted by "Latest" instead of "Changes".

In general, one commit on Github equals one point in the "Changes" column, but fractional points are awarded for collaborative efforts — the most common example being a new S2 theme, where usually half credit is awarded to the theme author and the other half to the person who converts the theme into a code patch. Due to the nature of development, some changes are massive contributions of new code, and others are tiny tweaks; there is no correlation with the amount of effort involved. We are grateful to everyone who helps to improve Dreamwidth, in ways large or small.

I last compiled this list at the beginning of April. Since that time, we have welcomed five new contributors: [github.com profile] dfabulich, [personal profile] phidari, [personal profile] wohali, [personal profile] pinterface, and [personal profile] onlyembers. Congratulations and thank you again!

  #  User                      Changes     Latest
  1. kareila                      1030     Fri Sep 30 19:09:51 2016 UTC
  2. woggy                          17     Thu Sep 29 22:26:43 2016 UTC
  3. momijizukamori             224.16     Thu Sep 29 19:58:05 2016 UTC
  4. onlyembers                    0.5     Thu Sep 29 19:58:05 2016 UTC
  5. pinterface                   15.5     Sat Sep 24 00:19:48 2016 UTC
  6. wohali                          1     Wed Aug 31 14:12:26 2016 UTC
  7. hotlevel4                      52     Fri Jul 15 22:39:55 2016 UTC
  8. kaberett                       44     Thu Jul 14 14:59:58 2016 UTC
  9. mark                        552.5     Mon Jun 27 04:24:47 2016 UTC
 10. phidari                         2     Sat Jun 18 21:14:12 2016 UTC

 11. cesy                        29.83     Sat Jun 18 15:28:34 2016 UTC
 12. chrisboyle                     15     Sun May 15 12:08:22 2016 UTC
 13. me_and                         36     Sun May 15 11:33:08 2016 UTC
 14. dfabulich                       1     Mon Apr 25 19:53:40 2016 UTC
 15. alierak                      19.5     Sun Apr 10 22:41:50 2016 UTC
 16. azurelunatic                    8     Mon Mar 28 05:54:30 2016 UTC
 17. srukle                          7     Wed Mar 23 16:44:54 2016 UTC
 18. sgsabbage                      17     Wed Feb 24 20:45:39 2016 UTC
 19. sophie                         58     Sun Feb 14 18:19:32 2016 UTC
 20. ljacob                          1     Sat Nov 07 12:13:45 2015 UTC
The rest of the list... (159 total) )
kareila: "Mom, I'm hungry." "Hush, I'm coding. You ate yesterday." (coding)
[personal profile] kareila
I've just merged [personal profile] woggy's code for the new Selective Screening feature! I'm planning on making it live on the site in the next couple of days, but in the meantime, I encourage you to test it in your development environment and let me know if you have any feedback. Here is how it works:

There are three console commands that govern who is subject to selective screening in your journal or community. They are screen_set, screen_unset, and screen_list and they are very similar to the related console commands for banning users. The maximum number of users you are allowed to apply selective screening to is 500 per journal/community.

When a user is subject to selective screening, all of that user's comments in the affected journal/community will be automatically screened, regardless of what the entry's screening settings are. The affected user is informed that their comments are being screened when viewing the reply form. The user's screened comments are like any other screened comments and can be manually unscreened, receive screened replies, etc.

This feature was requested back in 2012 and I am excited that it has been implemented!
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
momijizukamori: Green icon with white text - 'I do believe in phosphorylation! I do!' with a string of DNA basepairs on the bottom (Default)
[personal profile] momijizukamori
I'm in the process of updating /customize/ to move it away from BML and a million widgets, and I've got most of the HTML-y stuff done, but I'm having trouble with the Javascript. The biggest part of this is redoing the AJAX queries, which were previously done in widget-specific ways and passed through a bunch of the Widget class handlers. Working off jQuery, I've gotten as far as getting it to submit a POST request which reaches the controller - but the param formatting is all wrong and missing a bunch of the parameters sent with a TT form POST request. Do we have methods for creating proper POST requests from AJAX?
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
[personal profile] sophie
The Dreamhack machine currently seems to be suffering from a performance issue where if you try to start your Apache, it might tell you that Apache failed to start. In reality, the Apache server *has* started, but the 'start-apache' script is timing out before Apache can report that fact.

If the last line of your Apache log file is:

NOTE: Google::Checkout::* Perl modules were not found.

then Apache has most likely started successfully. (This is a normal warning on Dreamhack machines; we haven't used the Google Checkout code for some time and thus the modules are not installed on the Dreamhack machine.) You can verify this by navigating to your Dreamhack's Web address.

We're investigating this at the moment. This might require a reboot of the Dreamhack machine in the near future; we'll post about it here if that's the case.

[edit: We're going to reboot the Dreamhack machine. I'll edit this post again when it's up.]

[edit 2: The Dreamhack machine is back up, and I've rolled out a new version of start-apache that can wait a bit longer if Apache doesn't start up immediately. It prints out a "Waiting for Apache to start" message, and then checks every second (for up to 6 seconds) whether Apache started, so it shouldn't slow things down for anybody.]
kaberett: A sleeping koalasheep (Avatar: the Last Airbender), with the dreamwidth logo above. (dreamkoalasheep)
[personal profile] kaberett
Only one this time, but the fix is already live because oh my.

Issue 1851: add alert for email output dropping too far
Category:
Patch by: [github.com profile] alierak
Description: Yeah. Yeah. You know that bit where the entire site just... stopped sending e-mails for several days? And this meant nobody got any notifications about comments or support requests about the lack of notifications? And I, for one, saw a few people mention it but was up to my eyeballs in lab and therefore assumed Google had just greylisted Dreamwidth again so didn't actually sound any klaxons? YEAH. It turns out that it's possible, with how notifications get sent, that the connection can... drop... and... no... alerts... went off? So it's now the case that an alarm will start Very Noticeably Blaring if the site doesn't actually succeed in sending any e-mail for longer than 15 minutes. This might get refined, but at least the site won't faceplant into this particular failure mode for quite this long again.

1 total issue resolved
Contributors: [github.com profile] alierak
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
bcholmes: (eclipse)
[personal profile] bcholmes
Are the answers to this thread reflective of the current state of accessing entry comments via an API? Or has anything changed? (In particular, [staff profile] denise mentions a possible new API designed in the 21st century.
kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett
Code tour code tour CODE TOUR aaaaaah. A buch of new themes, plus a lot of tidying!

Edit: and a belated welcome to [github.com profile] rshatch, who I am pretty sure has their first fix featured in this code tour!

Read more... )

11 total issues resolved
Contributors: [github.com profile] cesy, [github.com profile] hotlevel4, [github.com profile] kaberett, [github.com profile] kareila, [github.com profile] pinterface, [github.com profile] rshatch, [github.com profile] zorkian
kareila: Taking refuge from falling debris under a computer desk. (computercrash)
[personal profile] kareila
The server that hosts the Dreamhacks seems to be having hardware issues and is currently not responding. We have a ticket open with the hosting service and will update this post when the server is back online. Sorry for the inconvenience!

Update: It is back up now. Let us know if it stops responding again!
sophie: A cartoon-like representation of a girl standing on a hill, with brown hair, blue eyes, a flowery top, and blue skirt. ☀ (Default)
[personal profile] sophie
Hi,

Soon - probably within the next month - I'm planning to add code on the Dreamhack server which will automatically shut down Apache instances when the owner logs out (or at some point thereafter). I'm doing this because running Apache instances do take up resources on the Dreamhack server and a lot of people don't stop their Apache instances when they're not working on them, and it does make things a bit harder.

Currently I'm thinking of either shutting down the Apache instance either 7 days after the owner last logged out (unless they're currently logged in, of course) or shutting it down immediately on logout. If anybody has any issues with either of these options, please let me know in the comments - I'm very willing to listen to people on this.

If you have any other comments or questions, please do also comment. I'd be happy to answer any questions on this.
kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett
All of these will be going live in tonight's code push!

Read more... )

8 total issues resolved
Contributors: [github.com profile] cesy, [github.com profile] kaberett, [github.com profile] kareila, [github.com profile] pinterface
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
It's time for another question thread!

The rules:

- You may ask any dev-related question you have in a comment. (It doesn't even need to be about Dreamwidth, although if it involves a language/library/framework/database Dreamwidth doesn't use, you will probably get answers pointing that out and suggesting a better place to ask.)
- You may also answer any question, using the guidelines given in To Answer, Or Not To Answer and in this comment thread.
kareila: (Default)
[personal profile] kareila
As mentioned previously, we're about to reboot the Dreamhack server. Hopefully it won't be down too long; I'll update this post when it seems to be back up.

Update: seems to be back now.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
The company that hosts the Dreamhack machine has let us know that they're prepping to migrate the machine to their new platform. We've been warned that due to the large number of files on the machine, the migration is likely to take a long time or fail to complete successfully.

In order to minimize migration-related downtime and maximize the chance of not having failures, we're temporarily zipping up the home directories of anyone who hasn't touched any files in their account since 2014. Nothing will be permanently deleted -- just temporarily turned from many files into one file. (The problem isn't with the amount of data, but the number of files.)

We'll let you know when the migration is happening. EDIT: We're going to aim for Thursday night, probably sometime in the evening, but depends on when [personal profile] alierak has the chance to babysit it.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I'm really sorry for the length of time it's taken me to make a final call on this -- I've been hoping that I would have the brainpower to deal with it, but my physical and mental health have both just been absolute shit lately, and I just have not had the cope. (And it's the kind of thing I can't delegate, not without also handing over the DW card, yadda.)

So, we will not be doing any kind of official DW trip to OSB this year -- I seriously considered a "yes, we will bring people, but you'll have to book your own travel and get reimbursed", but even that level of coordination is just beyond me at the moment. I'll be attending and speaking myself, and I need to reserve my (very few) spare cycles for talk prep and doing my own travel.

If you are attending on your own, I'm happy to meet up with people and hang out during, as long as I don't have to arrange anything! (Jen and I are staying at the Paramount.)

I'm sorry, folks; I'll do my best to make the call earlier next year!
karzilla: a green fist above the word SMASH! (Default)
[staff profile] karzilla
One of the things I want to start doing on a semi-regular basis is encouraging people to come to me with any questions they have about Dreamwidth development, large or small. I want to do this in two ways: for people who prefer real time chat, I have started holding IRC office hours, and for people who prefer threaded comment discussions, use this post as a springboard!

You can ask me absolutely anything related to Dreamwidth and I will answer to the best of my ability. Don't be shy! This is slightly different from the existing monthly question threads in that I will take responsibility for giving at least an initial answer, which others can then expound upon or contradict as they see fit.

If you would like to take advantage of my office hours, http://karzilla.dreamwidth.org/tag/devchat is where to find information about my schedule and how to sign up.

Profile

dw_dev: The word "develop" using the Swirly D logo.  (Default)
Dreamwidth Open Source Development

November 2016

S M T W T F S
  12345
6789101112
13141516171819
20212223242526
272829 30   

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Dec. 8th, 2016 11:54 pm
Powered by Dreamwidth Studios