Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Community Check-in #13 Summer Of Code Week 14 #3225

Closed
SidharthBansal opened this issue Aug 12, 2018 · 24 comments
Closed

Community Check-in #13 Summer Of Code Week 14 #3225

SidharthBansal opened this issue Aug 12, 2018 · 24 comments

Comments

@SidharthBansal
Copy link
Member

Hi everybody 😃 !

If you're new here, welcome, and please try some of our first-timers-only issues. This is a checklist for @publiclab/soc.

@stefannibrasil @milaaraujo @MargaretAN9 @Gauravano @ViditChitkara @tech4GT @mridulnagpal @namangupta01 @sagarpreet-chadha @Souravirus @jywarren @MayankKashyap @siaw23 @ryzokuken @ccpandhare @icarito @abTest-123 @steviepubliclab @ebarry @publiclab/soc @publiclab/reviewers

What is the plan for this week?

If you have not planned yet, just leave a Hi! so that we could know that you are in sync with us 🔃


Google Summer of Code timeline

As end to this awesome journey is near, let's review important dates so that we don't miss anything -

📆 https://summerofcode.withgoogle.com/how-it-works/#timeline

⌨️ Coding May 14, 2018 - August 6, 2018

📥 Students Submit Code and Final Evaluations August 6 - 14, 2018 - Students submit their code, project summaries, and final evaluations of their mentors.
(Here are Work Submission Instructions - https://developers.google.com/open-source/gsoc/help/work-product )

📝 Mentors Submit Final Evaluations August 14 - 21, 2018 - Mentors review student code samples and determine if the students have successfully completed their Google Summer of Code 2018 project.

🎉 Results Announced August 22, 2018 - Students are notified of the pass/fail status of their Google Summer of Code 2018 projects.

As @jywarren mentioned in last check-in that he's going on vacation so @publiclab/soc, we all are required to pitch in:


This journey was absolutely full of Code 💻 , tasks 🗒️, fun 🎉 and excitement 😃. And, now it's time to have a new experience with Google Code-In, so if you are excited to be a mentor. Acknowledge here #3168.

As always, if you're waiting for a review, or if you're stuck, please request help
here OR leave a comment with @publiclab/soc and @publiclab/reviewers for
some input.

I will be writing the remaining tests this week. And looking at which issues needs to be addressed in Google Code In(GCI)

Have a nice week 🎉 !
Thank you !

(closing #3222)

@grvsachdeva
Copy link
Member

Hi @publiclab/soc,
I am done with my work product submission and here's note - https://publiclab.org/notes/gauravano/08-12-2018/gsoc-2018-final-work-product-of-draft-feature-and-email-integration-project . Please provide your valuable feedback.

Weekly Update:
I am working on the last setting of the Email Subscribtion settings project which is Unsubscribe from
Q & A
Issue #1610
PR raised at #3220 .
I would also be resolving issues in Email notification milestone, after completing above PR.
Thanks!

@stefannibrasil
Copy link
Contributor

Hi, everyone! This week @milaaraujo and I are going to wrap our work with our two big PR's #3134 and #3217. We plan to call them on the feed RSS methods, so we decrease the amount of duplicated code around the codebase.

After that, we are going to move on to write unit tests for the search API.

@jywarren
Copy link
Member

jywarren commented Aug 14, 2018 via email

@Souravirus
Copy link
Member

Hi everyone! I have submitted my final evaluation. So, currently I am working with the yarn transition and it is still not complete. There were some errors while pushing it to unstable. Any help is appreciated at #2659. Also, I think I will be starting with the work with graph possibly by today.
So, thanks for such a wonderful summer everyone.

@ebarry
Copy link
Member

ebarry commented Aug 14, 2018 via email

@stefannibrasil
Copy link
Contributor

stefannibrasil commented Aug 15, 2018

@siaw23 can we add the API endpoints here as well? https://oss.skylight.io/app/applications/GZDPChmcfm1Q/recent/5m/endpoints

@siaw23-retired
Copy link
Collaborator

you mean those Grape endpoints right? @stefannibrasil well they should be showing once those endpoints are hit. i see those are the only endpoints not registering, i've just sent an email to Skylight for support.

@jywarren
Copy link
Member

Hi, all! Since we have a priority fix on the answer formatting now merged in #3232, i'd like to push this to production. I've just pushed to https://stable.publiclab.org and since we've had some API changes and I'm not as available, I'd like to ask folks to try the site out (especially focusing on new code you've had merged) before we push it to production. Thanks! @publiclab/soc

@jywarren
Copy link
Member

(should take a few minutes to build!)

@jywarren
Copy link
Member

Hmm, looks like it failed! I'm seeing: An HTTP request took too long to complete. Retry with --verbose to obtain debug information.

https://jenkins.laboratoriopublico.org/job/Plots-Stable/lastFailedBuild/console

I wasn't able to figure out where it got this response, but it had gotten past building containers and was in the + make deploy-container segment. @icarito any ideas? I've started it again.

@jywarren
Copy link
Member

Hmm, failed again...


ERROR: for containers_redis_1  Cannot start service redis: transport is closing
�[1A�[2K
Creating containers_db_1 ... �[31merror�[0m
�[1B
ERROR: for containers_db_1  Cannot start service db: grpc: the connection is unavailable

ERROR: for db  Cannot start service db: grpc: the connection is unavailable

ERROR: for redis  Cannot start service redis: transport is closing
Encountered errors while bringing up the project.
Makefile:24: recipe for target 'deploy-container' failed

I wonder if something is up with the network connections between the containers?

@jywarren
Copy link
Member

jywarren commented Aug 16, 2018

Also, heads up everyone! Tomorrow is Rails Girls Summer of Code Burnout Awareness Day! Even if you're not in RGSoC perhaps it's a thing to think about. I wasn't able to find this year's announcement, but here's a great one from a few years ago, with a list of 10 things to to do instead of code:

https://railsgirlssummerofcode.org/blog/rgsoc-day-off

Please always take good care of yourselves, it's far more important than the projects we do together even if we're passionate about them.

@jywarren
Copy link
Member

@publiclab/soc just being sure the notification got sent for the above note!

@Souravirus
Copy link
Member

Yeah that's a nice note about chilling a day out 😄 😄

@stefannibrasil
Copy link
Contributor

@siaw23 yes, I meant the Grape endpoints, you're right. That is great, thank you!

@publiclab/soc about the RGSoC day off, tomorrow @milaaraujo and I will work and we will take the Saturday off instead! :)

@namangupta01
Copy link
Member

Hey all, Sorry for not being active this week...i was busy in my college placements. I will test reply-by-tweet feature in this and coming week on unstable so that we can merge this and make it live soon. 🎉 🎉

@sagarpreet-chadha
Copy link
Contributor

Hi all !!!
I was too busy with college placements...hopefully i will be more active next week . Thanks !

@SidharthBansal
Copy link
Member Author

Hi, who is going to open the next week's Community Check - in?
@publiclab/soc

@milaaraujo
Copy link
Collaborator

I can do it, @SidharthBansal!

@SidharthBansal
Copy link
Member Author

Go for it

@milaaraujo
Copy link
Collaborator

Moved to #3241

@icarito
Copy link
Member

icarito commented Aug 23, 2018

Hi @jywarren (hope you are having a pleasant vacation!) and everyone, the issue with Jenkins was that unstable and stable (and now testing) were sharing the container namespace so they interfered with each other. Once I separated them in Jenkins by tagging the containers with the DOCKER_COMPOSE_PROJECT environment variable, I had to fix a couple of issues but it is working now (#3253 - please merge).

In any case Jenkins should work now.

Also, it looks like #2824 should be fixed once #3253 is merged!

@SidharthBansal
Copy link
Member Author

This is great news sebastian

@stefannibrasil
Copy link
Contributor

good work, @icarito !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests