The first and third answers for Android Q54 seem to be the same, need correction.

https://github.com/Ebazhanov/linkedin-skill-assessments-quizzes/tree/master/android

Description: Modify the Security Review process to:

• initiate a draft/WIP PR of the self-assessment and/or joint-review prior to the presentation to closeout the review
• clearly set the joint-readme and joint-review and/or self-assessment as required for the PR finalization in the process doc.
• Modify co-chair requirements to verify the above items are complete and presentation

Is your feature request related to a problem?

The complain functionality for students will only be available if Begin of Student Review and End of Student Review is set. An instructor who is not familiar with Artemis could assume that the complaint buttons will be available and not decide on the end of the complaint time (maybe a potential time frame was announced via another communicat

Now that we've moved PrairieLib back into the monorepo, we should use direct requires. That is, everywhere that we do this: https://github.com/PrairieLearn/PrairieLearn/blob/89d265461da214d773b722b5e0465e00396f52b1/lib/question.js#L20 we should change it to:

const sqldb = require('../prairielib/sql-db');

and similarly for any require with @prairielib.

These would be useful for insisting that a coefficient is worth including.

The annotations that change $n's behaviour are defined in runtime/scripts/jme-rules.js, in number_conditions. To implement this, add entries for nonzero and nonone which check that tok.value != 0 (or 1)

A student should be able to get an anonymised link of their submission so that they could share it (e.g. on social network). The view would be a readonly view with the feedback of the submission still visible. The link should only contain the submission id.
There should be an option in the task conf to allow or not this feature on a par-task basis.
If an admin follow such a link, he should be r

🚀 Feature Proposal

We should add CloudWatch alarms for all EC2 instances that alerts us (the devs) for things such as:

• CPU pegged for too long
• Gratuitous memory consumption
• Volumes >=90% full

Motivation

We need to know when our EC2 instances are in trouble!

In the "marking algorithm" tab of the part editor, you can enter an answer and see the feedback produced. Each feedback item should have a tick or cross next to it as appropriate, like in the real exam interface.