![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
ninetydegreesHi! I would love to patch the style I've submitted but I don't know if it needs @media $medium_media_query and @media $large_media_query and if so, where to put them exactly. Could someone explain our breakpoint system to me?
ninetydegrees
Errors when updating
Jul. 10th, 2015 07:45 pmninetydegreeserror htdocs/scss/components/pickadate/datetime.scss (Line 11 of htdocs/scss/components/pickadate/_base.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/components/pickadate/time.scss (Line 6: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/celerity.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-horizontal.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-vertical.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
Is is just me?
error htdocs/scss/components/pickadate/time.scss (Line 6: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/celerity.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-horizontal.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
error htdocs/scss/skins/gradation/gradation-vertical.scss (Line 107 of htdocs/scss/skins/_nav.scss: Invalid US-ASCII character "\xE2")
Is is just me?
pauammaThis is as mentioned in http://dw-dev-training.dreamwidth.org/58411.html. The question thread for this month is at http://dw-dev.dreamwidth.org/161662.html.
Question thread #21
Jul. 5th, 2014 01:28 pmpauammaIt'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.
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.
Dear Changelog Admins,
Jul. 4th, 2014 02:58 pmninetydegreesCan one of you move the search module of Changelog towards the top of the sidebar, please?
Edit: actually could you do this for dw_dev and dw_dev_training as well? Maybe other comms too.
Edit: actually could you do this for dw_dev and dw_dev_training as well? Maybe other comms too.
Question thread #20
Jun. 6th, 2014 01:04 pmpauammaIt'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.
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.
Question thread #19
May. 2nd, 2014 04:38 pmpauammaIt'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.
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.
Question thread #18
Apr. 3rd, 2014 06:32 pmpauammaIt'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.
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.
Question thread #17
Mar. 2nd, 2014 01:09 pmpauammaIt'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.
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.
Question thread #16
Feb. 1st, 2014 11:51 ampauammaIt'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.
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.
Question thread #15
Jan. 1st, 2014 03:13 pmpauammaIt'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.
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.
Question thread #14
Nov. 25th, 2013 03:01 pmpauammaIt'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.
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.
Question thread #13
Oct. 26th, 2013 04:37 pmpauammaIt'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.
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.
Question thread #12
Sep. 25th, 2013 11:28 ampauammaIt'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.
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.
Question thread #11
Aug. 25th, 2013 09:55 ampauammaIt'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.
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.
Question thread #10
Jul. 20th, 2013 01:12 pmpauammaAgain, it's been way too long since the last question thread (why didn't anyone poke me?) so let's have another one!
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 since no one poked me this time either: do these still serve a useful purpose? And how often would you like to see them, if at all?
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 since no one poked me this time either: do these still serve a useful purpose? And how often would you like to see them, if at all?
Bug 4176 - bizarre broken behaviour
Jun. 13th, 2013 02:00 pmkaberettHere is my pull request.
Here is the Bugzilla entry, plus the diff of the draft patch I am building on.
The idea is that we want to add a "User:" line to every support notification e-mail, indicating who was responsible for the activity prompting the notification.
fu pointed out that I need to:
My code as currently in pull request 427 behaves as expected, and as desired except for the issue outlined in point 2.
Removing the quotation marks from line 1068 produces the behaviour that the name of the user who submitted the request is quoted in all subsequent notification e-mails.
Ideas, please? I am WAY out of my depth here.
Here is the Bugzilla entry, plus the diff of the draft patch I am building on.
The idea is that we want to add a "User:" line to every support notification e-mail, indicating who was responsible for the activity prompting the notification.
fu pointed out that I need to:- remove the quotation marks around
$show_nameat line 1068 - account for the possibility of
$posterid==0at line 1095
My code as currently in pull request 427 behaves as expected, and as desired except for the issue outlined in point 2.
Removing the quotation marks from line 1068 produces the behaviour that the name of the user who submitted the request is quoted in all subsequent notification e-mails.
- this persists if quotation marks are added back in.
- this persists if everything after
username =>is deleted and rewritten. - this behaviour does not persist if line 1095 is replaced with mapping to a static text string, e.g.
username => "badgerbadger",and the change is then committed, but does persist if it is instead mapped to e.g.$posterid. - this behaviour does not persist if the entirety of any line which has ever contained
$show_name(without quotation marks) is deleted or commented out. - supportlog in the database is recording the correct information; it's just not making it to e-mail, somehow.
Ideas, please? I am WAY out of my depth here.
Question thread #9
Mar. 9th, 2013 12:19 pmpauammaIt's been way too long since the last question thread (why didn't anyone poke me?) so let's have another one!
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.
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.
Git and Release Branch
Jan. 9th, 2013 05:34 pmninetydegreesCould someone please explain this entry in simpler terms, preferably with detailed steps? I just don't get it because I have no release branch not stemming from develop so I'm not sure how I should go about creating it (the command given in the entry doesn't work for me obviously as branches on hack are only develop and master).
More git newbie questions
Sep. 2nd, 2012 07:29 pmyviSo I managed to submit my first pull request \o/
However, i have the following problem, bets described in console output:
What's going on there?
However, i have the following problem, bets described in console output:
dh-yvi@newhack:~/dw$ git checkout develop
Switched to branch 'develop'
Your branch is ahead of 'dreamwidth/develop' by 68 commits.
dh-yvi@newhack:~/dw$ git checkout master
Switched to branch 'master'
Your branch is ahead of 'dreamwidth/master' by 200 commits.
dh-yvi@newhack:~/dw$ git pull dreamwidth develop:develop
Already up-to-date.
dh-yvi@newhack:~/dw$ git pull dreamwidth master:master
From https://github.com/dreamwidth/dw-free
! [rejected] master -> master (non-fast-forward)
dh-yvi@newhack:~/dw$ git push origin develop
Everything up-to-date
dh-yvi@newhack:~/dw$ git push origin master
Everything up-to-date
What's going on there?
