fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu
A critical security vulnerability has been announced for Git which affects Windows/Mac. Make sure you update your clients!

The Github announcement has a bunch of useful links to clients. If you're on a Mac and use Homebrew, that one has also been updated. I believe macports has as well, but double-check to be sure.
momijizukamori: (dreamsheep | styles)
[personal profile] momijizukamori
Not dead! Just busy with life. But Fu is in the process of converting the widgets on /customize to something less ridiculous, which gives me time to prod some of the problems that have been stumping me.

1) Preserving search results
The order of actions to generate a page of results from the advanced search, as I have it right now, goes like this:
User checks boxes to indicate choices -> user presses 'search' button -> button triggers POST actions -> a query is generated as one of these actions -> query goes to worker -> worker performs search -> worker sends back a list of theme ids

The problem is that POST data is lost on reload/page change, so when you click to see the second page of results (if there are more than one page), all of the query and the results vanish. Most of our other ways of grabbing a set of layouts (by base style, by designer, etc) append the query string to the URL, which is then hidden from the user via routing, but even just the list of search elements has the potential to get unwieldy fast (and the return list is worse)

2) The auto-categorizer
I don't have this working yet because it's not necessary for the new search, just... nice, given we have almost fifteen hundred themes (!!!). The script needs to pull hexcodes out of the style layers (which is all text to the perspective of anything not the S2 compiler). That seems to say 'regex' to me but I don't know if that's safe/the best way to do it.
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.
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
If you were having issues with reinstalls or database updates on the Dreamhack machine, you should be good to go now if you retry what was failing before. The code needed a new version of the Locale::Codes distribution, meaning that update-db.pl wouldn't work. It should work now!

(Yes, reinstalls work again; I've been meaning to announce it here for ages, but I've kept forgetting. They work now by reinstalling from your personal Git repositories; there's currently no means to automatically nuke those repositories and re-fork, so if you need to do that, let me know.)
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
I have just installed Template Toolkit 2.26 on the Dreamhack machine. We were previously using 2.20, which is still installed but in such a way that the later version should take precedence.

As this is a core module for Dreamwidth, it's recommended that you restart Apache when possible. Things won't break just yet if you don't (since the old files aren't gone just yet), but according to my sources, the Dreamwidth codebase will require this new version of Template Toolkit soon, so things may break in the future.

As always, if anything breaks on the Dreamhack machine because of this change, please comment to let me know, or open a GitHub issue.

[edit 2014-12-07: Fix a typo.]
skud: (Default)
[personal profile] skud
If I recall correctly, there's a bot that assigns github issues to people if they say "claimed" or similar in the issue comments.

Can someone point me to the code/setup/whatever for that bot?
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
For a test, I need to have an expunged user on my dreamhack. I don't intend to wait 2 months for that test, so I'm planning to tweak the existing process. From my reading of the source code of the 3 programs listed in http://wiki.dreamwidth.net/wiki/index.php/Purging_deleted_users, I think what I want is something like:
bin/moveucluster.pl --delete --expungedel <username> 0
with a version of bin/moveucluster.pl modified to remove the built-in delay. Before I start trying and maybe break my database in subtle ways, can someone confirm I'm on the right track?
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.
fu: Close-up of Fu, bringing a scoop of water to her mouth (Default)
[staff profile] fu

With [staff profile] denise's help (the bulk of this was from her really!), we've made major changes to the dev-facing wiki documentation for clarity.

Among other things:

  • merged multiple/redundant pages and sections

  • improved linking

  • (hopefully) reduced the complexity of paths through the wiki for someone just getting started

The biggest change is to Dev Getting Started, which is now greatly expanded, with a much clearer flow, and more focus on someone totally new to DW/development. The resources for someone more experienced have been moved to Dev Quick Start .

The contents of Version Control have been merged with Newbie Guide: How To in Git and the latter is the canonical page for git info -- though now I'm tempted to go rename it to Version Control because it's shorter. Git How To? ;)

Git instructions in some pages have been updated to be much simpler with a pointer to the appropriate section in the git commands in case that's needed.

And the Directory Structure has been expanded to cover more subdirectories.

Beginner Dev Checklist needs some more effort to pull it apart: plan is to integrate it into other pages as appropriate and then get rid of it (since it's not sufficiently different from Dev Getting Started to warrant its own page)

Would appreciate if you poked around through the various pages and let me know if there's anything still left unclear, or if you're aware of similar pages that can be merged into these existing ones!

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.
swaldman: A cute fluffy sheep curled up dreaming of Dreamwidth. Labelled "Simon: Bodger". (dw-dev)
[personal profile] swaldman
So my pull request re posting notifications of new Dreamwidth entries to Twitter got reviewed, and has comments that need to be addressed. However, I don't have time or headspace to devote to DW dev work at the moment, so if this is going to make it in before it bitrots completely, it would probably be best if somebody else took it on. This leads to two questions,
  1. Anybody want to take this on? I think it's mostly there, but needs tweaking as per comments. And probably some fairly thorough re-testing, since things may have changed with Twitter and Net::Twitter since I wrote it 18 months ago.
  2. More generally, what should I do in this scenario? Is there some way in which I can unassign myself from the PR? (I'm not sure that there even is an Issue to unassign myself from; I did this work while we were in bugzilla)
Thanks.
pauamma: Cartooney crab holding drink (Default)
[personal profile] pauamma
The workflow given in http://wiki.dreamwidth.net/wiki/index.php/Routing_and_Template_Cookbook:_BML_Conversion_Workflow doesn't indicate what to do when you find yourself in the presence of a widget, like for htdocs/support/submit.bml. Some questions an addition could cover:
- Can/Should I use the widget itself directly in a controller?
- Which parts of the widget need to go where?
- When is it safe to get rid of the widget itself? (eg, how do I know it's not used anywhere else)

I probably forgot some questions/issues. Discuss here and I'll try to summarize to the wiki?
kareila: (Default)
[personal profile] kareila
A few months ago, I started scheduling regular dev chat meetings in an effort to increase awareness of our development efforts and discuss how to deal with common issues we all face in the course of development.

I think a lot of good has come from these chats. However, over the last six weeks or so, participation has fallen way off, and I'm no longer convinced they can continue to serve a useful purpose in their current form.

If it's a scheduling issue, I'm happy to move it around to get more attendance. I've asked before for alternative times and gotten no responses. I had hoped that by scheduling it to occur at the same time every couple of weeks, that would allow people to plan ahead to arrange their availability to attend. If it would work better to poll everyone for a preferred time for each meeting, I can try that for a while.

If it's not a scheduling issue, I'd like to know why more people aren't showing up to participate. It was made clear to me in the discussion here that there was definitely a perceived need for something like this three months ago. Has that need disappeared? Should we be trying to meet it in a different way?

Basically I want to do whatever I can to help facilitate communication in the development community, but I want to make sure my efforts are having the desired effect. Please comment if you have any thoughts on the matter. Thanks.
swaldman: A cute fluffy sheep curled up dreaming of Dreamwidth. Labelled "Simon: Bodger". (dw-dev)
[personal profile] swaldman
Nice flowchart here.

It's not new, but I haven't seen it here before :-)
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.

Also, I'm curious: if you have a coding blog, would you like links to recent entries rounded up on dw_dev? If so (no obligation), feel free to comment with links and someone will compile them and post a new entry here.
denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
I've had my talk, "When Your Codebase Is Nearly Old Enough To Vote", accepted at Linux Conf Australia in January. Every time I swear I'm going to start developing my talk earlier than "the week before the conference", and this year is no different ...

Description of the talk:
Read more... )

With that in mind, are there any particular horror stories people think I should tell? I mean, I have a general outline in my head already, and I'm definitely going to be talking about things like "what happens when you invent something because you need it, then somebody else invents the same thing two years later and that's the version that takes off instead" (*cough* BML *cough*) and the like, but I'd like to tell some funny stories like "that time we wanted to make it possible for people with a default icon to select 'no icon' at the time they post, only to discover that the reason no icon displays when people haven't chosen a default icon was, in fact, due to a twelve-year-old bug" and stuff like that.
kareila: (embarrassed)
[personal profile] kareila
There will not be a dev chat meeting today unless someone else shows up for me to talk to, because Mark and Fu are on vacation.

However, I will be around trying to hack on DW stuff for the next few hours, so come find me if you want to pick my brain about anything.

The next scheduled meeting time is on Saturday, September 13, at 12 pm EDT.
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
I just updated LWPx::ParanoidAgent and Net::SSL on the Dreamhacks server - something that I've needed to do for some time. In the process about seventy bajillion other modules that they relied on needed to be updated, too (mainly to do with HTTP/SSL stuff) so the following modules (and any submodules included in their distribution) are now at their most recent (and the links given lead to the exact versions installed from CPAN):

23 different distributions in total )

As this is rather a lot of modules, some of which can be core to various things that the codebase does, you should restart your Apache if it's currently running; there may be errors otherwise. Also, it's possible that the update of these modules might somehow cause brokenness in some areas on the Dreamhacks server; please do comment here if that's the case (or open a GitHub issue).

(Please note: This only applies to brokenness on the Dreamhacks server. Nothing has changed on dreamwidth.org, so any issues there should be raised in a Support request as usual.)
azurelunatic: Azz and best friend grabbing each other's noses.  (Default)
[personal profile] azurelunatic
This tour is a group effort. Thanks to [personal profile] kareila for rounding up and coding all the issue links! I provided the descriptions.

Here we have a lot of fixes for styles issues, and a lot of stuff from [staff profile] fu! This is a more prompt release than some, because everybody was really anxious to get some of the mobile wonkiness introduced with the last update fixed in this one. We also have stuff from [staff profile] denise, [staff profile] mark, [personal profile] hotlevel4, and [personal profile] exor674.

This code tour is live: the code push entry is over in [site community profile] dw_maintenance as usual.

Read more... )
kareila: Rosie the Riveter "We Can Do It!" with a DW swirl (dw)
[personal profile] kareila
If you weren't able to make today's meeting in #dreamwidth-dev, the next meeting will be on Saturday, August 23, at 12 pm EDT. Also there will be another hack date on Sunday, August 17, also at 12 pm EDT.

Here's a list of topics we discussed today, and most of them will probably be revisited next time:

  • code push tomorrow, should fix issues with new mobile styles
  • Github Issues revamped, updated docs on wiki
  • possible alternative project trackers and chat platforms
  • scheduled another social hack time for 8/17
  • encourage "what are we working on" discussion/issues outside of IRC
  • reconsidering how we name/advertise release branches


In attendance were myself, Afuna, zorkian, exor674, and V_PauAmma_V.

Raw chat log under the cut. )

Profile

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

December 2014

S M T W T F S
 123456
789 1011 1213
141516171819 20
21222324252627
28293031   

Syndicate

RSS Atom

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Dec. 21st, 2014 12:01 pm
Powered by Dreamwidth Studios