maybe I'm doing something wrong...but the output of running the default code snippet on the dlang.org homepage is:

"unable to fork: Cannot allocate memory"

not a good look

On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
> maybe I'm doing something wrong...but the output of running the default code snippet on the dlang.org homepage is:
>
> "unable to fork: Cannot allocate memory"
>
> not a good look

Thank you for letting us know,

This issue will be fixed very soon.

Best regards,
Damian Ziemba

On Wednesday, 16 September 2015 at 06:44:30 UTC, nazriel wrote:
> On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
>> maybe I'm doing something wrong...but the output of running the default code snippet on the dlang.org homepage is:
>>
>> "unable to fork: Cannot allocate memory"
>>
>> not a good look
>
> Thank you for letting us know,
>
> This issue will be fixed very soon.
>
> Best regards,
> Damian Ziemba

Would it be possible to set things up so ones that fail are retired until they can be fixed? Non-working examples look awful for the language.

On 16-Sep-2015 09:44, nazriel wrote:
> On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
>> maybe I'm doing something wrong...but the output of running the
>> default code snippet on the dlang.org homepage is:
>>
>> "unable to fork: Cannot allocate memory"
>>
>> not a good look
>
> Thank you for letting us know,
>
> This issue will be fixed very soon.
>
> Best regards,
> Damian Ziemba

May I suggest you to record such conditions with automatic notification e.g. by e-mail.

Only 1 in 10 of visitors will consider reporting an issue, of these only 1 in 10 will get to dlang forum to post a message.

-- 
Dmitry Olshansky

On Wednesday, 16 September 2015 at 10:17:21 UTC, Dmitry Olshansky wrote:
> On 16-Sep-2015 09:44, nazriel wrote:
>> On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
>>> maybe I'm doing something wrong...but the output of running the
>>> default code snippet on the dlang.org homepage is:
>>>
>>> "unable to fork: Cannot allocate memory"
>>>
>>> not a good look
>>
>> Thank you for letting us know,
>>
>> This issue will be fixed very soon.
>>
>> Best regards,
>> Damian Ziemba
>
> May I suggest you to record such conditions with automatic notification e.g. by e-mail.
>
> Only 1 in 10 of visitors will consider reporting an issue, of these only 1 in 10 will get to dlang forum to post a message.

well now I feel special :)

On Wednesday, 16 September 2015 at 10:17:21 UTC, Dmitry Olshansky wrote:
> On 16-Sep-2015 09:44, nazriel wrote:
>> On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
>>> maybe I'm doing something wrong...but the output of running the
>>> default code snippet on the dlang.org homepage is:
>>>
>>> "unable to fork: Cannot allocate memory"
>>>
>>> not a good look
>>
>> Thank you for letting us know,
>>
>> This issue will be fixed very soon.
>>
>> Best regards,
>> Damian Ziemba
>
> May I suggest you to record such conditions with automatic notification e.g. by e-mail.
>
> Only 1 in 10 of visitors will consider reporting an issue, of these only 1 in 10 will get to dlang forum to post a message.

It is know for me issue.

At the time I was working on runable examples, samples on the main page were way simpler.
Not we are hitting some limitations of Container Dpaste's backend is running in.

I am working on new version of backend (and new container) as we speak so it will be solved once and for all.

1-2 days more and we will be done with it so IMHO no need take any additionals steps for it right now.

On 09/16/2015 09:49 AM, nazriel wrote:
> 1-2 days more and we will be done with it so IMHO no need take any
> additionals steps for it right now.

That's great, thanks for doing this. What is the current status with regard to making the online compilation infrastructure publicly accessible and improvable? Ideally everything would be in the open, and we (= the fledgling D Language Foundation) would pay for the server infrastructure. Please advise, thanks. -- Andrei

On Wednesday, 16 September 2015 at 09:52:23 UTC, ixid wrote:
> On Wednesday, 16 September 2015 at 06:44:30 UTC, nazriel wrote:
>> On Wednesday, 16 September 2015 at 05:54:03 UTC, Andrei Amatuni wrote:
>>> maybe I'm doing something wrong...but the output of running the default code snippet on the dlang.org homepage is:
>>>
>>> "unable to fork: Cannot allocate memory"
>>>
>>> not a good look
>>
>> Thank you for letting us know,
>>
>> This issue will be fixed very soon.
>>
>> Best regards,
>> Damian Ziemba
>
> Would it be possible to set things up so ones that fail are retired until they can be fixed? Non-working examples look awful for the language.

https://github.com/D-Programming-Language/dlang.org/pull/1098

This removes unfixable examples. I think Damian is working on getting the one fixable-but-broken example (rounding floating-point numbers) to work.

On Wednesday, 16 September 2015 at 20:52:08 UTC, Andrei Alexandrescu wrote:
> On 09/16/2015 09:49 AM, nazriel wrote:
>> 1-2 days more and we will be done with it so IMHO no need take any
>> additionals steps for it right now.
>
> That's great, thanks for doing this. What is the current status with regard to making the online compilation infrastructure publicly accessible and improvable? Ideally everything would be

That's the plan.
Currently I am working on upgrading both frontend and backend to be up-to-date with current requirements. I am also trying to integrate the look of dpaste.dzfl.pl to match the one on dlang.org so we could make dpaste part of the *.dlang.org fleet.

Once I am done with those things (should take up to 2 weeks) - the whole product - frontend and backend will be fully open-sourced and available on github for forking.

Currently my main focus is on making Backend less restrictive so we can spawn threads, run all examples from dlang.org without restrictions etc.

The backend will be the first thing that will be open-sourced and it should happen before end of the current week (19.09.2015).


> in the open, and we (= the fledgling D Language Foundation) would pay for the server infrastructure. Please advise, thanks.

I still need to catch up with Vladimir via @ if he is OK with moving dpaste backend into dedicated unprivileged LinuX Container. If yes - then probably we can stick with his server - if not we should discuss other options.

For the first 2 weeks it will run it on my server - but I would prefer to not place it on my server - in case I disappear for a while again ;)

> -- Andrei

Best regards,
Damian Ziemba

On Thursday, 17 September 2015 at 14:48:07 UTC, nazriel wrote:
> On Wednesday, 16 September 2015 at 20:52:08 UTC, Andrei Alexandrescu wrote:
>> On 09/16/2015 09:49 AM, nazriel wrote:
>>> 1-2 days more and we will be done with it so IMHO no need take any
>>> additionals steps for it right now.
>>
>> That's great, thanks for doing this. What is the current status with regard to making the online compilation infrastructure publicly accessible and improvable? Ideally everything would be
>
> That's the plan.
> Currently I am working on upgrading both frontend and backend to be up-to-date with current requirements. I am also trying to integrate the look of dpaste.dzfl.pl to match the one on dlang.org so we could make dpaste part of the *.dlang.org fleet.


Hi Damian,

dpaste doesn't seem to produce any console output at the moment, I just get 'Result: Success  / Return code: 0' and nothing from writeln.