Personal Learning Dashboard (Beta)

GeekGawd

GeekGawd

Contributor

Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute
Graduate attribute

Graduate Attributes

Learn More

Individual Skills

Graduate attribute

Creative thinking

Graduate attribute

Problem Solving

Graduate attribute

Practical/Professional Skills

Team Skills

Graduate attribute

Communication Skills

Graduate attribute

Collaboration

Graduate attribute

Community Engagement

Graduate attribute

Leadership

Graduate attribute

Learn How to Learn

Graduate attribute

Skills to apply digital & technology solutions

Graduate attribute

Critical Thinking

Advanced Skills

Graduate attribute

Autonomy And Responsibility

Graduate attribute

Empathy

Graduate attribute

Value inculcation

Graduate attribute

Multicultural Competence

Cultural Skills

Short Bio

Still waiting for this

Learning Activity

MonWedFriJulAugSepOctNovDecJanFebMarAprMayJun
4 contributions in the last year
LessMore

Highlights

Pull Request
0
Reviews
0
Feed
0

Contributions

  • Shared a comment on an issue in coronasafe/care on June 11, 2023 at 11:47:02 AM

    @vigneshhari Aaahhhhhh... makes sense, Thank You! Yep will do, could you please assign the issue to me.

    https://github.com/coronasafe/care/issues/1339#issuecomment-1586132297

  • Shared a comment on an issue in coronasafe/care on June 9, 2023 at 11:04:30 PM

    @sainak @nikhilagastya This is what I have gotten from my reasearch... First query comes from ConsultationBedSerializer -> BedSerializer (bed_object) -> AssetLocationSerializer (location_object) Second query comes from ConsultationBedSerializer -> ExternalIdSerializerField(consultation) -> queryset (attr) -> PatientConsultation.objects.all() Third query is always called because of the property in Bed Model in ./facility/models/bed.py @property def is_occupied(self) -> bool: return ConsultationBed.objects.filter(bed=self, end_date__isnull=True).exists() I evaluated it by making a custom middleware and wrapping the request/response in that ``` class SQLLoggingMiddleware: def __init__(self, get_response): self.get_response = get_response def __call__(self, request): response = self.get_response(request) sql_queries = connection.queries for query in sql_queries: logger.info(f"SQL Query: {query['sql']} - Time: {query['time']}") reset_queries() return response ``` Did some backtracking and logging got where they came from. I don't really see any optimisation can be done here, as they are coming from Serializer fields. Should we try passing the queryset from the view to Serializer?

    https://github.com/coronasafe/care/issues/1339#issuecomment-1585224689

  • Shared a comment on an issue in coronasafe/care on June 7, 2023 at 2:33:11 PM

    It needs to be wrapped in try catch to properly handle the error... But I would it would not be as easy to just wrap the code with try catch... the validation would go in another file, right?

    https://github.com/coronasafe/care/issues/1348#issuecomment-1580953366

  • Shared a comment on an issue in coronasafe/care_fe on May 29, 2023 at 7:38:43 PM

    @rithviknishad Hi! Sir, I have successfully set up the working environment. To better analyse the joins I was looking forward to use the django_debug_toolbar, it seems to be already present in the settings. Could you guide me as how I would be able to get it running?

    https://github.com/coronasafe/care_fe/issues/5492#issuecomment-1567457492

More to come in the coming days...!