DEV Community: vedant-jain03

GSoC 2022 CircuitVerse | Week 11 and 12 Report

vedant-jain03 — Mon, 05 Sep 2022 12:52:38 +0000

Description

In previous two weeks, I have been working on completing the field around notifications for CircuitVerse.

We have deployed the new Notification version/UI. There are still data migration task pending that will migrate all the older notifications for respective users.

Webpush Implementation

I have been working on adding Webpush feature, that will enable user to get notified while not been in our site. Just like you see in mobile notifications in the navbar!

Basically, we need to register service-worker.js in the user's browser.

if (navigator.serviceWorker) {
    navigator.serviceWorker.register('/serviceworker.js.erb', { scope: '/' });
}

So there is a gem webpush for adding webpush functionality into your Rails App. We had implementation for webpush already with the model named as Push_subscription. Basically for each webpush notification there will be a record in the database which on subscribing triggered the user browser and he can see the notification in the web.

Noticed gem had really cool feature to have customized delivery method for notifications, so I created a custom delivery method Webpush.

class DeliveryMethods::Webpush < Noticed::DeliveryMethods::Base
  def deliver
    # Logic for sending the notification
    user = User.find(params[:user_id])
    project = Project.find(params[:project_id])
    url = "/users/#{recipient.id}/notifications"
    recipient.push_subscriptions.each do |sub|
      if params[:webpush_type] == "star"
        sub.send_push_notification("#{user.name} starred your project #{project.name}!", url)
      else
        sub.send_push_notification("#{user.name} forked your project #{project.name}!", url)
      end
    end
  end
end

and respectively add the delivery method in our notifications:

# app/notifications/fork_notification.rb
class ForkNotification < Noticed::Base
  deliver_by :webpush, class: "DeliveryMethods::Webpush"
end

Bug : `Couldn't find Project with 'id'`

Initially, for every notifications we were saving the ids of the project and the user(the one who triggered the notificaitons). Due to which while destroying the projects dependent notification were not getting deleted and hence was leading to an error.

Aboobacker assisted me to find the bug, and I finally made an approach to save objects in params, so that destroying the projects should destroy the dependent notifications objects as well. But here was an issue, the new notification version was released 1.5 weeks before, and in the meantime many notifications with old parameters version that means with project_id and user_id in params have been saved. That is why, we decided to create data_migration file that will update the params in the correct way. Have a look at it:

class PopulateNoticedNotificationWithValidParams < ActiveRecord::DataMigration
  def up
    NoticedNotification.find_each do |notification|
      if Project.where(id: notification.params[:project_id]).exists?
        project = Project.find(notification.params[:project_id])
        notification.params[:user] = User.find(notification.params[:user_id])
        notification.params[:project] = project
        notification.save
      else
        notification.destroy!
      end
    end
  end
end

PR

Under Review: Webpush notification
Merged: fix: dependent notifications on project while destroy

Next Task:

Complete notifications API.
Suggested tags for projects.

Conclusion

I was not able to work for 3-4 days due to SIH and health issue. But I learned a lot as always!

GSoC 2022 CircuitVerse | Week 9 and 10 Report

vedant-jain03 — Sun, 21 Aug 2022 12:49:11 +0000

Description

These two weeks were awesome in the context of learning and coding. I learned a lot about migrations, rails console, rails specs, rails ActiveRecord, and rails API.

These 2 weeks were majorly focused on data migration, completing the PR and notification API.

So the migration I coded for the data was ok but need modifications. Aboobacker guided me to write quality and scalable migration. Also, as this was the data migration, Aboobacker suggested to use rails-data-migrations gem that make a separate data_migrations directory in db/, that help us to track the data migrations files.

To Generate data migration file:

rails generate data_migration migration_name

To run the data migration:

rake data:migrate

We have made some cleanups as well.
I also learned a lot about the spec and these weeks I worked on that part as well.

In this week(week 10), I worked on notification API for mobile-app along with the specs.

PR:

The progress we have made in these 2 weeks:

Implement noticed gem.
PR for notification API for Mobile-App.
Activity Notification data Migration.
Removed activity Notification gem.

What Next?

Reimplement Web push for notification.
Design for weekly contest.

Conclusion

By far these two weeks were full of debugging and learning. I took much time as expected for this PR but will work more hard and try to deliver the features as expected.

GSoC 2022 CircuitVerse | Week 7 and 8 Report

vedant-jain03 — Sun, 07 Aug 2022 13:16:00 +0000

Description

This week I worked on completing the Noticed Integration into CircuitVerse, this was one of the challenging and most productive weeks ever as I have learned:

Rails console effective usage.
ActiveRecords
Migration.
Controllers.
Views rails.

So in the last meeting, I showed the demo of the notification functionality to the mentors and they stated that there are some minor changes in the UI and to migrate the old data of Activity Notification.

I completed the task for helper methods, UI, and some cleanups. But the most challenging task for me was to migrate data from one table to another table with different configurations. Aboobacker shared a migration file that contains SQL the query for the migration but that was comparatively simpler than what I needed to do in this task!

So I have comeup with many solutions to render old notifications:

I thought we can just add a before_action filter with method load_old_notifications for user.So I create a new column in old_notification table called migrated with default false, so whenever the user signin, the load_old_notifications will run and will check in the old_notification if the migrated field is false, it will create a new data for notification table and mark migrated as true in old_notification table.
But I find this as very complex as we are thinking of removing ActivityNotification gem and while migrating there is model method needed to get the path of the notification, so I drop this solution and jump into next and next, I failed and finally come up with the solution to use ActiveRecords in migration (it worked but not preferable) so here is my migration file look like:

class PopulateNotificationData < ActiveRecord::Migration[7.0]
  include ActivityNotification
  def change
    Notification.find_each do |data|
      newnotification = NoticedNotification.first_or_initialize(
        :recipient_type => data.target_type,
        :recipient_id => data.target_id,
        :type => "PreviousNotification",
        :params => {
          user_id: data.notifier_id,
          path: data.notifiable_path,
          message: data.notifiable.printable_notifiable_name(data.target),
          type: data.notifiable_type
        },
        :read_at => data.opened_at
      )
      newnotification.save!
    end
  end
end

I need to change it in SQL query.

So that took me around 4 days but it was worth it, I learned a lot from failures.

This 2 weeks I also :

Passed Mid-term Evaluation
Post my first blog on CircuitVerse/Blog regarding first phase of GSoC.
Attended my first offline hackathon and meet awesome peoples.

Next week plan:

Complete spec testcases
Complete migration
Start working on push notification in mobile app.

GSoC 2022 CircuitVerse | Week 5 and 6 Report

vedant-jain03 — Sun, 24 Jul 2022 05:17:57 +0000

During these two weeks, I have worked on:

Assignment Restriction PR.
POC for Weekly Contest.
Some minor bugs & documenation.
Improve Notification Page(Noticed gem Integration).

Assignment Restriction.

We already have element restrictions for the assignment i.e., to restrict the group members with the use of elements for the Project.
But we have got quite a few complaints from professors that CircuitVerse allows cheating easily. For example, users can easily copy/paste any public circuit. They can give collaborators access to their own circuit and copy-paste etc. So it has been requested by professors to disable this feature.

Implementation

Similar to the implementation of elements restriction, I have made a column of type jsonb named feature_restrictions which is gonna store all the selected feature restrictions.
In the assignment form, I have made a select-options dropdown section similar to element restrictions.

So there are 2 feature restrictions in Project Page and 2 in Simulator. So, in the projects page, first I give id's to the respective feature button so that to access them in JS using DOM manipulation and I simply did this then:

<% if @project&.assignment_id.present? && @project.assignment.feature_restrictions %> {
      let restricted_feature = '<%= @project.assignment.feature_restrictions %>';
      if(restricted_feature.includes('Allow Collaborators')) 
    {
        $('#collaboration_button').attr("style", "display:none")
      }
      if(restricted_feature.includes('Copy / Paste')) {
        $('#copy_paste').attr("style", "display:none")
      }
    }
<% end %>

and for the simulator, I similarly did this:

<% if @project&.assignment_id.present? && 
   @project.assignment.feature_restrictions %>
   let restricted_feature = '<%= @project.assignment.feature_restrictions %>'
   if(restricted_feature.includes('Combinational Analysis Tool')) {
     $('#createCombinationalAnalysisPrompt').attr("style", "display:none")
     }
   if(restricted_feature.includes('Verilog tools')) {
     $('#generateVerilog').attr("style", "display:none")
     }
<% end %>

This was the whole implementation summary.

and how can I forget the best part:

POC for Weekly Contest

Weekly contest feature in the CircuitVerse focus to have great circuits creation to be featured and user engagement. So I worked on that part meanwhile nitin was working on the UI part. But this issue or any issue should not be started without plan, so we decided to work on the weekly contest in the beginning of the next phase.

Some minor bugs & documenation.

Here are some work I did:

Notification Page Improvement(Noticed Integration)

Currently, CircuitVerse uses activity_notification gem for the Notifications but the gem is not maintained any more and the notification page is very lagging. So we decided to replace the gem and we found noticed gem by chris oliver of Gorails.

UI

Navbar Notifications
Notification Page

Progress

Done with the initial integration and configuration.
Notification Event covered:
- Star
- Fork
UI
Tab functionality
Navbar quick notification access.

Pending

Data migration.
Cleanup
figma design UI is still under progress.

Next week plan

Completing the Notification pending task.

Conclusion

These two weeks were awesome, I learned a lot on rails and grab knowledge of integration of new gem noticed. Got to know about Rails Console Usage. Grab the knowledge of Rails API.

GSoC 2022 CircuitVerse | Week 4 Report

vedant-jain03 — Sun, 10 Jul 2022 06:38:53 +0000

This week I was focused on:

Getting my ongoing PR to merge i.e. "Improve Embed Feature" and "Support Multiple Mentors".
Finalizing the idea for Weekly Contest.

Completing `Improve Embed Feature`

So in a meeting with Aboobacker(mentor), we concluded that in Embed we should not implement a feature of landing subcircuits for now because of the migration of the simulator from CircuitVerse repo to its own new repo cv-simulator-frontend.
So I clean-up the PR and it finally got merged.

As always my best part:

In this PR I learned:

Rails View Component.
Query-Parameter Parsing.

Completing `Support Multiple Mentors`

This PR was awaiting approval of Mobile Feasibility as it contains the code for API as well which is mainly used in CircuitVerse Mobile App to interact with Database. Ruturaj(PR author) had coded the API very neatly. After some cleanups, the PR got finally merged. These functionalities are still unreleased in Production but will be released soon.

What Else

I also worked on one bug issue and made a PR for it, here.

It was basically the broken pagination in the project comment section.

What Next

In the weekly project meeting, we concluded that the weekly contest feature should be planned very properly as it can bring new creative users to CircuitVerse. So this week I will be working on PoC (Proof of Concept) for the Contest.
In the coding part, I will be working on my PR Assignment Restriction that is now under the scope of my GSoC project.

Conclusion

By far, this week was also great. Comparatively, I coded less this week and researched more.

GSoC 2022 CircuitVerse | Week 3 Report

vedant-jain03 — Sat, 02 Jul 2022 12:15:00 +0000

It's been a month in the GSoC environment with CircuitVerse and it's great so far.
This week I did the following:

Fixes the conflicts of Support Multiple Mentors PR.
Worked on Improve Embed Feature PR.
Reviewed and discussed the UI of all the features. The previous week, I have done with the requested functionality of the PR Support Multiple Mentors but after one commit merged into master, there was a lot of RoboCup conflicting with the files of this PR. Hence, I solved them and was able to fix all the conflicting files. The PR is almost ready and now we are checking its feasibility with CircuitVerse Mobile-App. This week, I worked on the PR by Kartikay(contributor) for Improve Embed Feature. Check out the description of the feature here. I have worked on:
Improving the existing UI.
Some typos.
Implement popup in form of Rails Component view.
Added translation.
added and transfer the code to project_controller(stimulus).
Added Advance feature to enable/disable: - Zoom-in-out feature - Fullscreen button - Clock/Time button - Display Title
Added feature to choose different built-in themes for embed circuit. It looks like this: > Advance Option So, how it is working? CircuitVerse awesome contributors have made embed.js and embedListener.js files for tackling with the embed feature. So I have made some input fields with default values in component views which are connected to data-controller=projects and in projects_controller I have to write code to get the value from those input fields and after the user hits that Publish button, the function in controller takes the values from each input and save it to the variable and finally made a URL variable along with query parameters passed to fetch the values in embed.js. The URL looks like this:

const url = `${document.querySelector('#url').value}?theme=${theme}&display_title=${displayTitle}&clock_time=${clockTimeEnable}&fullscreen=${fullscreen}&zoom_in_out=${zoomInOut}`;

and in embed.js I accessed those parameters using this:

const params = new URLSearchParams(window.location.search);

and to retrieve certain values I use something like this:
const fullscreen = params.get('fullscreen');
So that was all about this week's work. I learned a lot and concluded that anything can done be using javascript. Javascript OP!!!

Next Week Plan

Complete Improve embed PR.
Start working on Weekly Contest.

GSoC 2022 CircuitVerse | Week 2 Report

vedant-jain03 — Sat, 25 Jun 2022 15:10:16 +0000

This week was great. I learned a lot. I was able to complete my deliverables.

So last week the gitlab integration PR got merged and according to my proposal this week goes to SSO but we finalize to add some more important features in the CircuitVerse. In the mentor meeting, we added 3 more features for which PRs were already raised, and out of which one was mine. There are some works to do in all the PRs before the final merge. We update the Project Kanban Board as well and this week I need to work on the feature Support multiple mentors for groups.

This week my PR for SSO integration got merged but we concluded that there is much manual work to do now and there is 3 priority features, so it will be out of the scope of this year. So there was an error with IDP integration that may be taken out next year GSoC. I learned a lot about SSO, SAML, and okta IDP. And finally most awaited thing in the PR(message and status):

Checkout the PR.

SO there was a new feature assigned to me for this week.

Support multiple mentors for groups feature

The feature enables the functionality to have multiple mentors in the group. There will be the primary mentor(owner) of the group who can add mentors to the group. Mentors can:

Create and delete assignments
Grade assignments
Reopen closed assignments

The PR was created by Ruturaj(GSoC'22 Mentor, former GSoC Contributor) and most of the work was done by him, the main functionality. The PR was a long time ago and there are many new features in CircuitVerse from that time that were causing conflicts. The PR need:

To be updated with the master
Should contain i18n translation
Powered with stimulus.js
Fix Circle CI because of LMS integration that was not implemented at that time.
UI fix.

I added all the things one by one commit for clean PR but there was always an error from CodeClimate(bot) for clean code. I was able to change some of them. But the important fail was of CI and it was caused because of the lti_spec because at the time this PR was created lti feature was not there in the CircuitVerse and in this PR the mentor field is replaced with the primary_mentor field in the DB so there was error because of that. I was able to fix it.

Testing locally using bundle exec rspec was not working. I tried but was giving an unknown error and as always Aboobacker come in and guide me through the way, just like that and it was an error because of the permission in the SQL database.

Next week's plan

Will start working on this PR.
UI meets for Weekly Contest Feature.

Conclusion

Overall this week was really great. I learned a lot and was able to complete my deliverables. I am also working as technical writer in Google Season of Docs with the palisadoes foundation. I am getting good at time management. I learned TSDoc this week and started working on the documentation of the Talawa-Admin repository. This week I also updated my Portfolio website. All checks completed.

Checkout My Last week Blog here.
All Blogs here.

GSoC 2022 CircuitVerse | Week 1 Report

vedant-jain03 — Sat, 18 Jun 2022 12:08:37 +0000

Google Summer of Code 2022 Coding period start on 13 June. The previous week, I started working on gitlab and SSO integration in the CircuitVerse main platform.

Check out my previous blog: here.

Week 1 (13 June — 18 June)

I was facing some issues in gitlab integration, after the mentor meet we concluded that it was the version of omniauth-gitlab gem that was causing an error. It was v2.0.0 and should be v4.0.0 but the gem is dependent on the omniauth gem that was also not updated due to which gitlab-omniauth gem was not getting updated. So we concluded to update the omniauth gem first along with smoothing the initial 3rd-Party Authentication.

I updated the omniauth and got it merged. PR

After updating my gitlab branch with master, I was able to update the gitlab gem without any error and commit the changes according to the new version of the omniauth gem. After the review of the PR and changing some bot suggestions. The PR got finally merged.

After getting it merged, I started working on SSO PR. I update it with the master branch and mark the PR from WIP as ready for review.

Next Week Plan

I will be completing the SSO + Keycloack integration in the next week.
I will start with the new feature in CircuitVerse: Weekly Contest.

Conclusion

This week was one of my best productive weeks ever. I learned a lot and was able to fulfill my first week's deliverable as mentioned in the Proposal.

Community Bonding Period at CircuitVerse — Google Summer of Code 2022

vedant-jain03 — Sun, 12 Jun 2022 04:24:10 +0000

What is the Community Bonding Period?

Every successful project has been planned before. Similarly, in this phase contributors connect with respective mentors and discuss the project deliverables, plan the project and finalize the scope of the Project.

My experience

I was so happy after getting selected for GSoC, especially with CircuitVerse. After getting selected, our private channel was created and all the contributors, mentors, and OA were there. We had our first meeting on 26th May, and we were welcomed by our mentors, I meet my mentors Aboobacker, Pavan, Samiran, Ayan, Ruturaj, and contributors Pulkit, Devjit, and Aman. It was a pleasure meeting them all. We had a great meeting and our mentors told us about the flow of the GSoC at CircuitVerse.

After that, for each project separate private channels were created and I had my meeting with my project’s mentors. We set up the project board on GitHub for tracking the project's progress and discussing the project scope, and deliverables. I asked them to let me start the coding on 1st June, as I was aware of the codebase.

My progress and learning (1st June — 10th June)

I start with the feature of integrating Gitlab Authentication for CircuitVerse. I used omniauth-gitlab gem for that. I made an application in gitlab for testing and configured the .env file. I configured and implemented all the required things correctly referencing other OAuth implementations but there was an unknown error. I had a meeting with my mentor and the problem was the omniauth gem version. I will be working on updating that in the upcoming week and hopefully will complete my first task of the Project.

I also started with implementing SSO(Single Sign-On) in CircuitVerse. I used devise_saml_authenticatable gem for it. I created WIP(Work in Progress) PR for that. I was facing an issue on the IDP side. I will be completing this PR after gitlab-implementation. I am researching it meanwhile…

Work done so far

Conclusion

I feel the best experience of my engineering life as it is my first work experience. The whole vibe of the community is so supportive. I learned a lot. I don’t know after getting selected for GSoC I feel responsible and am working accordingly. I am researching more, reading more, and learning more. It is the vibe of GSoC. Overall, I had a great week.

How I crack GSoC 2022

vedant-jain03 — Thu, 26 May 2022 16:46:09 +0000

How I crack GSoC 2022

What is Google Summer of Code?

It is not an internship at Google, or anything working with Google. Make sure your relative does not post it on the WhatsApp group, so…..

In simple words, google summer of code is a program that promotes or provides an opportunity for Open Source Contributions in Open source Organizations.

First Google announces the program officially and starts the application for an Open source organization to participate, then the open-source organization is announced along with its projects for GSoC, then contributors contact and submit the proposal for a project at the respective organization. Then after evaluating the proposal, the organization Admin sent the list of students from their end, then google provides the slots and announces the accepted contributors and Projects for each organization.

Learn more about GSoC, here.

Eligibility Criteria, here.

When should I start?

Right now is the best time, the time when you get to know about it is the best time to start.
But mind that "Selection is not confirmed".

Workflow for getting started

Search for Organization(Most Important and difficult task)
Start contribution

How to choose the right Organization?

Everyone had their perspective to choose the number of organizations! But I will prefer to choose only 1. I mean you can explore many organizations but start contributing to 1 only.

You should first choose the organization on the basis of your interest. In my case, I was searching for organizations based on:

web Development
Javascript technology
Past GSoC project
Supportive community

If it is taking you 1–2 weeks, trust me it is okay and well worth it. Do not aim for a goal in hurry.

How to start contribution?

Go to the community channel to interact with members and mentors.
If you are a beginner, checkout for issue with good first issue as a label.
If it is taking time to get your first PR pulled and merge, don't worry, my first PR is not even merged yet, the rule is never stopped.
Go for the comparatively higher issue next time. Higher issue does not mean with the number of codes, I mean complexity.

Important points regarding contributions?

Quantity never matters, Quality matters. One of the contributors with more PRs than me did not get selected.
Your learning curve in the community should be exponential.
Try to review PRs as well, which can improve your understanding. I always try to read the PRs of other contributors and past GSoC fellows, it clears my thoughts and knowledge by getting to know other's approaches.
Try to participate or attend community meetings and threads!
Don't raise an issue for anything you see in the deployment, sometime it is expected, so always try to raise a thread in the community, after getting approval there, raise an issue in Github.

My journey

I got to know about CircuitVerse organization through an open-source event in July 2021, I participated in that and won 100$ gift vouchers as well. My first contribution, PR, it was just SCSS code. I want to thank Nitin and Shreya Prashad for guiding me.

And then the Fun Began!!!

I decided to continue my contributions to CircuitVerse and then I got to know about the CircuitVerse GSoC experience. I reach out to the CircuitVerse fellow GSoCers and trust me they were really supportive and encourage me to contribute. I want to thank Pavan Joshi, Ruturaj Mohite, Manjot, and Ayan Biswas for that, they are my mentors now.

I was not aware of Ruby on Rails at all at that time. It was my first time contributing to a large codebase, so it took me around 15 days to set up CircuitVerse Main Platform.
I got my first good first issue in CircuitVerse, PR.

Then I started learning Ruby on Rails. Learning while implementing it into a large codebase is the best way to understand, trust me. Then I contributed my first Rails code-based PR and got merged. I got inspired by Aboobacker(Org Admin & my mentor) and Satvik Ramaprasad(Founder). It gave me more confidence. I always try to challenge myself 1 step ahead of issues.

On November 28th, 2021, the organization admin invited me to join the GitHub community as a member for my consistent contributions.

Honestly, I was not aiming CircuitVerse for GSoC only but for the experience and for the open-source. I am always enthusiastic to solve the issues, participate in community meetings, and review others' PR. I got very comfortable with the CircuitVerse environment.

I try to contribute to other repo as well as CircuitVerse.
Checkout My All contributions here.
The organization announces its expected Projects on the wiki before the official GSoC site to get the maximum time to draft the proposal.

My project selection!

I selected Project 2: CircuitVerse Platform Improvements, I selected the project because:

I had major contributions on the main platform only, so I was very comfortable with the whole platform codebase.
Tech stack required.
Scope and need.

Proposal Drafting

A proposal plays a very vital role in selection especially when there is more than 1 approaching active contributor.
on 7th Feb 2022, CircuitVerse announce the Projects on the wiki and 19th April was the deadline. I had enough time to make a good proposal, I never hurried, I planned to review my first draft by 20th March and I did on 23rd March.
So, there were mainly 6 features that need to be implemented so I first start with the feature under my understanding.
I discussed my approach towards each point with mentors which helped me to understand the expectation of the mentors as well. This point is very important as I was taking some of the features differently but they were meant to do something different, this small misconception can result in a bad choice. I never think ashamed while talking to mentors. I always pinged them whenever I need, not necessarily for small issues.

Finally, I drafted my proposal using the template given by the Organization.

Timeline is one of the most important judging criteria, so choose or draft the timeline wisely.

Key Points

Take time to research the scope and needs of the Project.
Ask mentors for any doubts without hesitation.
Choose the approach wisely, if you are not able to add the final code, you can add pseudo code.
Draft the timeline section wisely.
Review your proposal 2, 3 times. I reviewed it 2 times. Do not stop your contributions after proposal submission, be active in the community.

I had my interaction interview as well for the GSoC.
And finally…….

I was so happy, I remember that I shouted out loud for almost 5 minutes saying yes, f***, I did it, ab bol.

But I had many rejection stories and I never celebrated this thing.

GSoC is my first ever life achievement that satisfied me.

There are many fellows who got accepted in their 1st, 2nd, or even 3rd attempt as well. You should never give up. It will make sense after getting it.

I tried GSoC'21 but now I realize that I was not prepared at that time and got Selected for GSoC'22 because I don't give up and try my best.

If I can so do you….

Best of luck.

If you have any doubts, connect with me in:

Twitter.

Linkedin.

I will post more blogs on this platform, so follow me.

Interview Experience Digital Specialist Engineer - Infosys

vedant-jain03 — Mon, 16 May 2022 16:39:34 +0000

What is HackWithInfy?

HackWithInfy is a competitive coding competition for second-year to pre-final year students across India. In this competition, participants have to solve coding questions in a given time and top performers get a chance to interview Infosys.
The level of the competition was medium-hard. I solved 1 question and got AC and other 2 partially accepted. I did not remember the exact questions but they were mainly based on Arrays, Greedy and DP.

All questions can be solved partially with brute force, so will recommend you to solve every question.

If you solved 1 questions fully and some testcases for other 2, you will definitely going to get the interview for DSE role.
So there were two roles Infosys was offering:

SE : 9 LPA
DSE : 6.25 LPA

If you are able to solve all 3, you will get upgraded to advanced rounds and will surely get the interview for SE.

Interview Experience

I got the mail on 3 May 2022 to schedule my interview and I scheduled nearest date possible 7th May. My interviewer forgot about the interview and hence he slept and get back to me after 2 hours. That was funny, XD. Never mind.
The interviewer was really chilled and cool.

He asked me for the introduction.
Then asked me about my current semester subjects.
He then started with question to check weather a number is prime or not. I shared my screen and he asked me that, what if in place of #include <bits/stdc++> can we write #include "bits/stdc++.h", I was not sure about it and said no it will not compiled but it compiled successfully and then I realised about importing modules in react with "". I got pretty nervous.
He then asked me that main() function will return 0 to whom? In my mind I was right OS, but as my overconfident killed my before I not tell him the answer.
Then I write the code, he gave me sample TC and it ran fine.
He then asked me the topic which I can not expect, What is DFA, I asked him to repeat I heard DFS, but it was Deterministic Finite Automata. Luckily I learned the topic in my online classes(YES, I attended first class) and told him everything I knew.
He then asked me about my projects.
He then started with some sense of humour question
- What is color of the wall behind you?
- What is the color of your Shirt?
- How many buttons in your T-Shirt?
He then asked me
- What do you know about Infosys?
- Where do you see yourself after 5 years?

We wrapped up and ask me for any doubts.

I asked him about his experience.
I asked him about my feedback. He told me that I have good communication skills and open source experience.

Conclusion

It is going to be very chill and easy, just be confident(not over).

Add key event listener in React.

vedant-jain03 — Tue, 29 Mar 2022 17:04:03 +0000

It is very simple in react, you can add any key event listener. I have used example of "Enter".

I have defined a sample function for the explaination.

    const handleInputEnter = (e) => {
        // You can 
        if(e.code === 'Enter') {
            console.log("Hello");
        }
    }

Add onKeyUp attribute in the element.
Example:

<input type="text" onKeyUp={handleInputEnter}  />

This will work completely fine.
Follow me on twitter: https://twitter.com/vedantj_03

DEV Community: vedant-jain03

GSoC 2022 CircuitVerse | Week 11 and 12 Report

Description

Webpush Implementation

Bug : Couldn't find Project with 'id'

PR

Next Task:

Conclusion

GSoC 2022 CircuitVerse | Week 9 and 10 Report

Description

PR:

What Next?

Conclusion

GSoC 2022 CircuitVerse | Week 7 and 8 Report

Description

Next week plan:

GSoC 2022 CircuitVerse | Week 5 and 6 Report

During these two weeks, I have worked on:

Assignment Restriction.

Implementation

POC for Weekly Contest

Some minor bugs & documenation.

Notification Page Improvement(Noticed Integration)

UI

Progress

Pending

Next week plan

Conclusion

GSoC 2022 CircuitVerse | Week 4 Report

Completing Improve Embed Feature

Completing Support Multiple Mentors

What Else

What Next

Conclusion

GSoC 2022 CircuitVerse | Week 3 Report

Next Week Plan

GSoC 2022 CircuitVerse | Week 2 Report

Support multiple mentors for groups feature

Next week's plan

Conclusion

GSoC 2022 CircuitVerse | Week 1 Report

Week 1 (13 June — 18 June)

Next Week Plan

Conclusion

Community Bonding Period at CircuitVerse — Google Summer of Code 2022

What is the Community Bonding Period?

My experience

My progress and learning (1st June — 10th June)

Work done so far

Conclusion

How I crack GSoC 2022

What is Google Summer of Code?

When should I start?

Workflow for getting started

How to choose the right Organization?

How to start contribution?

Important points regarding contributions?

My journey

My project selection!

Proposal Drafting

Key Points

Interview Experience Digital Specialist Engineer - Infosys

What is HackWithInfy?

Interview Experience

Conclusion

Add key event listener in React.

Bug : `Couldn't find Project with 'id'`

Completing `Improve Embed Feature`

Completing `Support Multiple Mentors`