[prev in list] [next in list] [prev in thread] [next in thread] 

List:       macports-dev
Subject:    Re: GSoC 2019 [Collect build statistics]
From:       Arjun Salyan via macports-dev <macports-dev () lists ! macports ! org>
Date:       2019-03-31 10:39:09
Message-ID: CAHToqhhY5CuXv2MtbO5=U5CDifZfWA16TMqzc0BPq_seT=RxQg () mail ! gmail ! com
[Download RAW message or body]

On Sun, Mar 31, 2019 at 2:05 PM Mojca Miklavec <mojca@macports.org> wrote:

> There seem to be some issues with subports. (For example any p5.28-*
> under perl would give an error page.)
>
Yes, it was happening for the ports that contain '.' in their names. I have
solved it using regex now.

Just curious: what's the order of magnitude of the time it took?
>
When the database was on the same machine, it took like 30 seconds. And
with my AWS Free Tier Database it took near 40-45 minutes.


> I now created:
>     https://github.com/macports-gsoc/macports-gsoc-2019-webapp
>
> You have full commit rights there, but the idea would be to first
> populate the repository with a basic README (else you probably cannot
> clone the repository at all), then clone it, and finally create a pull
> request with the relevant changes, and not commit directly before the
> code gets reviewed.
>

Sorry that I messed it up. I have created the pull request now.

Thank you, but I don't see it in our dashboard [yet?].
>
Oh, Sorry! I thought the first step was enough. I will quickly finish the
remaining.

Thank You

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr"><br></div><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Sun, Mar 31, 2019 at 2:05 PM Mojca Miklavec &lt;<a \
href="mailto:mojca@macports.org" target="_blank">mojca@macports.org</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">There \
seem to be some issues with subports. (For example any p5.28-*<br> under perl would \
give an error page.)<br></blockquote><div>Yes, it was happening for the ports that \
contain &#39;.&#39; in their names. I have solved it using regex now.  \
</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
 Just curious: what&#39;s the order of magnitude of the time it \
took?<br></blockquote><div>When the database was on the same machine, it took like 30 \
seconds. And with my AWS Free Tier Database it took near 40-45 minutes.</div><div>  \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I \
now created:<br>  <a \
href="https://github.com/macports-gsoc/macports-gsoc-2019-webapp" rel="noreferrer" \
target="_blank">https://github.com/macports-gsoc/macports-gsoc-2019-webapp</a><br> \
<br> You have full commit rights there, but the idea would be to first<br>
populate the repository with a basic README (else you probably cannot<br>
clone the repository at all), then clone it, and finally create a pull<br>
request with the relevant changes, and not commit directly before the<br>
code gets reviewed.<br></blockquote><div>  </div><div>Sorry that I messed it up. I \
have created the pull request now.</div><div><br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">
 Thank you, but I don&#39;t see it in our dashboard [yet?].<br></blockquote><div>Oh, \
Sorry! I thought the first step was enough. I will quickly finish the remaining.  \
</div><div><br></div><div>Thank You</div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]