Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2019 - E1991. Improvements to anonymized view

2019-11-12T02:30:49Z

Sdpampat: /* Impersonating Student Using Anonymized Names */

== ''' Introduction ''' ==
The [http://expertiza.ncsu.edu/ Expertiza] project takes advantage of peer-review among students to allow them to learn from each other. Tracking the time that a student spends on each submitted resources is meaningful to instructors to study and improve the teaching experience. Unfortunately, most peer assessment systems do not manage the content of students’ submission within the systems. They usually allow the authors to submit external links to the submission (e.g. GitHub code / deployed application), which makes it difficult for the system to track the time that the reviewers spend on the submissions.

== ''' Problem Statement ''' ==
The main idea of this project is to improve anonymized view in Expertiza. The feature is already implemented. However, there are issues / limitations with the current implementation which we will try to improve.

==== Anonymized View For Students ====
Currently, anonymized view is not implemented for students. Although, not directly required by students, instructors may want to use anonymized view when impersonating a student.

==== Issue with Impersonating Anonymized Student ====
In an anonymized view, instructors cannot impersonate a student because the username field has the anonymized name instead of their real name in the database. In order to be able to impersonate a student, we need to know their real names from database.

==== Wrong Anonymized Names ====
In some places, anonymized names are not shown. For example, heatgrid view. We need to fix occurrences in different parts of the application where anonymized names are not shown.

==== Anonymizing Team Names ====
Currently, team names are not anonymized. We need to extend the same logic of anonymization to teams.

==== Optional Objective ====
Use randomized American names for anonymized users.

== ''' Proposed Solution ''' ==

In this section, we propose solutions to the problems / issues discussed above.

==== Anonymized View For Students ====
Instructors often use 'impersonate' functionality to use Expertiza as a different user. Sometimes they also need to use anonymized view while they are impersonating a student. Therefore, anonymized view needs to be extended to students as well.

In order to extend Anonymized view for students, the first thing we need to do is extend the following function :

<code>
def set_anonymized_view
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
session[:ip] = request.remote_ip
if anonymized_view_starter_ips.include? session[:ip]
anonymized_view_starter_ips.delete!(" #{session[:ip]}")
else
anonymized_view_starter_ips += " #{session[:ip]}"
end
$redis.set('anonymized_view_starter_ips', anonymized_view_starter_ips)
redirect_to :back
end
</code>

This function is responsible to switch back and forth between normal view and an anonymized view. We could figure out that the session of current user is being manipulated to change views. The main driving logic works by storing user's IP address in a value field of <code>anonymized_view_starter_ips</code> which is in Redis database.

Refer the following flow chart for design details:

[[File:D1.png|center]]

==== Impersonating Student Using Anonymized Names ====

When an instructor is already in Anonymized view and wants to impersonate a student, they have to quit the anonymized view and get the real username of that student. However, we want the instructor to be able to impersonate a student by using their anonymized names. The following function in <code>impersonate_controller.rb</code> is responsible to impersonate students.

<code>
def impersonate
...
begin
original_user = session[:super_user] || session[:user]
# Impersonate using form on /impersonate/start
if params[:impersonate].nil?
...
user = User.find_by(name: params[:user][:name])
...
else
# Impersonate a new account
if !params[:impersonate][:name].empty?
...
user = User.find_by(name: params[:impersonate][:name])
...
else
...
end
end
...
rescue Exception => e
flash[:error] = e.message
redirect_to :back
end
end
</code>

In the above snippet, we have omitted the irrelevant parts of code. The only change we need to do is the logic for <code>User.find_by()</code> function. We will add a condition to check whether the current view is anonymized or not. If anonymized mode is set, we will convert the anonymous name back to the original name of the student. We will then make 'find' query using the real name of the student instead of using their anonymized name.

The procedure to do this would be opposite of what we do to get anonymized names in first place. See following code snippet :

<code>
def name(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ' ' + self.id.to_s : self[:name]
end
</code>

The above snippet is an example of how anonymized names are generated.

Please refer the following flowchart for design details;

[[File:D2 (1).png|center]]

=== Anonymizing Team Names ===

Right now, team names are not anonymized. We need to add accessor methods for team names in <code>team.rb</code> model file.

Additionally, we need a <code>before</code> function to check whether Anonymized view is set or not. In this function, we will generate anonymized name whenever Anonymized view is set. This is very similar to existing implementation of anonymizing user names as shown below :

<code>
def self.anonymized_view?(ip_address = nil)
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
return true if ip_address and anonymized_view_starter_ips.include? ip_address
false
end
...
def fullname(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ', ' + self.id.to_s : self[:fullname]
end
</code>

=== Wrong Anonymized Names ===

In some parts of the application, anonymized names are not working properly right now. It is highly difficult to find all such occurrences in the application at this early stage of the project. We are working to find all such occurrences.

However, we figured out that we need a common helper function to determine the name of a student based on whether Anonymized view is set or not. We will use the same function whenever we need to display name of a student. The function will internally take care of checking whether to return anonymized name or the real name.

=== ''' User Flowchart/Design ''' ===

== ''' Test Plan ''' ==

In this section, we discuss what the expected output of all the features will be in terms of well defined test steps.

==== Anonymized View For Students ====

# Login as an instructor
# Impersonate a student
# Switch to Anonymized view as a student

Right now, (3) is not supported.

==== Impersonating Student Using Anonymized Names ====

# Login as an instructor
# Switch to Anonymized view
# Find a student from list of users
# Assert that the student name is anonymized
# Use the anonymized name to impersonate the real user behind anonymous entity

Currently, (5) is not supported

==== Anonymizing Team Names ====

# Login as an instructor
# Switch to Anonymized view
# All team names should now be anonymized

In current implementation, (3) is not supported

==== Wrong Anonymized Names ====

We are yet to triage the scope of this functionality.

==== American English Names for Anonymized Students ====

# Login as an instructor
# Switch to Anonymized view
# Anonymized student names should be normal human names in American English, instead of cryptic names like <code>student12312</code>

== ''' Team Information ''' ==
#Shubham Dilip Pampattiwar (sdpampat)
#Pranav Maruti Gaikwad (pmgaikwa)
#Omkar Sunil Kulkarni (oskulkar)
#Deepayan Bardhan (dbardha)

'''Mentor''': Sharique Khan (mkhan8)
 '''Professor''': Dr. Edward F. Gehringer (efg)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]

CSC/ECE 517 Fall 2019 - E1991. Improvements to anonymized view

2019-11-12T02:28:38Z

Sdpampat: /* Impersonating Student Using Anonymized Names */

== ''' Introduction ''' ==
The [http://expertiza.ncsu.edu/ Expertiza] project takes advantage of peer-review among students to allow them to learn from each other. Tracking the time that a student spends on each submitted resources is meaningful to instructors to study and improve the teaching experience. Unfortunately, most peer assessment systems do not manage the content of students’ submission within the systems. They usually allow the authors to submit external links to the submission (e.g. GitHub code / deployed application), which makes it difficult for the system to track the time that the reviewers spend on the submissions.

== ''' Problem Statement ''' ==
The main idea of this project is to improve anonymized view in Expertiza. The feature is already implemented. However, there are issues / limitations with the current implementation which we will try to improve as a part of this project.

==== Anonymized View For Students ====
Currently, anonymized view is not implemented for students. Although, not directly required by students, instructors may want to use anonymized view when impersonating a student.

==== Issue with Impersonating Anonymized Student ====
In an anonymized view, instructors cannot impersonate a student because the username field has the anonymized name instead of their real name in the database. In order to be able to impersonate a student, we need to know their real names from database.

==== Wrong Anonymized Names ====
In some places, anonymized names are not shown. For example, heatgrid view.

==== Anonymizing Team Names ====
Currently, team names are not anonymized.

==== Optional Objective ====
Use randomized American names for anonymized users.

== ''' Proposed Solution ''' ==

In this section, we propose solutions to the problems / issues discussed above.

==== Anonymized View For Students ====
Instructors often use 'impersonate' functionality to use Expertiza as a different user. Sometimes they also need to use anonymized view while they are impersonating a student. Therefore, anonymized view needs to be extended to students as well.

In order to extend Anonymized view for students, the first thing we need to do is extend the following function :

<code>
def set_anonymized_view
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
session[:ip] = request.remote_ip
if anonymized_view_starter_ips.include? session[:ip]
anonymized_view_starter_ips.delete!(" #{session[:ip]}")
else
anonymized_view_starter_ips += " #{session[:ip]}"
end
$redis.set('anonymized_view_starter_ips', anonymized_view_starter_ips)
redirect_to :back
end
</code>

This function is responsible to switch back and forth between normal view and an anonymized view. We could figure out that the session of current user is being manipulated to change views. The main driving logic works by storing user's IP address in a value field of <code>anonymized_view_starter_ips</code> which is in Redis database.

Refer the following flow chart for design details:

[[File:D1.png|center]]

==== Impersonating Student Using Anonymized Names ====

When an instructor is already in Anonymized view and wants to impersonate a student, they have to quit the anonymized view and get the real username of that student. However, we want the instructor to be able to impersonate a student by using their anonymized names. The following function in <code>impersonate_controller.rb</code> is responsible to impersonate students.

<code>
def impersonate
...
begin
original_user = session[:super_user] || session[:user]
# Impersonate using form on /impersonate/start
if params[:impersonate].nil?
...
user = User.find_by(name: params[:user][:name])
...
else
# Impersonate a new account
if !params[:impersonate][:name].empty?
...
user = User.find_by(name: params[:impersonate][:name])
...
else
...
end
end
...
rescue Exception => e
flash[:error] = e.message
redirect_to :back
end
end
</code>

In the above snippet, we have omitted the irrelevant parts of code. The only change we need to do is the logic for <code>User.find_by()</code> function. We will add a condition to check whether the current view is anonymized or not. If anonymized mode is set, we will convert the anonymous name back to the original name of the student. We will then make 'find' query using the real name of the student instead of using their anonymized name.

The procedure to do this would be opposite of what we do to get anonymized names in first place. See following code snippet :

<code>
def name(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ' ' + self.id.to_s : self[:name]
end
</code>

The above snippet is an example of how anonymized names are generated.

Please refer the following flowchart for design detials;

[[File:D1(2).png]]

=== Anonymizing Team Names ===

Right now, team names are not anonymized. We need to add accessor methods for team names in <code>team.rb</code> model file.

Additionally, we need a <code>before</code> function to check whether Anonymized view is set or not. In this function, we will generate anonymized name whenever Anonymized view is set. This is very similar to existing implementation of anonymizing user names as shown below :

<code>
def self.anonymized_view?(ip_address = nil)
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
return true if ip_address and anonymized_view_starter_ips.include? ip_address
false
end
...
def fullname(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ', ' + self.id.to_s : self[:fullname]
end
</code>

=== Wrong Anonymized Names ===

In some parts of the application, anonymized names are not working properly right now. It is highly difficult to find all such occurrences in the application at this early stage of the project. We are working to find all such occurrences.

However, we figured out that we need a common helper function to determine the name of a student based on whether Anonymized view is set or not. We will use the same function whenever we need to display name of a student. The function will internally take care of checking whether to return anonymized name or the real name.

=== ''' User Flowchart/Design ''' ===

== ''' Test Plan ''' ==

In this section, we discuss what the expected output of all the features will be in terms of well defined test steps.

==== Anonymized View For Students ====

# Login as an instructor
# Impersonate a student
# Switch to Anonymized view as a student

Right now, (3) is not supported.

==== Impersonating Student Using Anonymized Names ====

# Login as an instructor
# Switch to Anonymized view
# Find a student from list of users
# Assert that the student name is anonymized
# Use the anonymized name to impersonate the real user behind anonymous entity

Currently, (5) is not supported

==== Anonymizing Team Names ====

# Login as an instructor
# Switch to Anonymized view
# All team names should now be anonymized

In current implementation, (3) is not supported

==== Wrong Anonymized Names ====

We are yet to triage the scope of this functionality.

==== American English Names for Anonymized Students ====

# Login as an instructor
# Switch to Anonymized view
# Anonymized student names should be normal human names in American English, instead of cryptic names like <code>student12312</code>

== ''' Team Information ''' ==
#Shubham Dilip Pampattiwar (sdpampat)
#Pranav Maruti Gaikwad (pmgaikwa)
#Omkar Sunil Kulkarni (oskulkar)
#Deepayan Bardhan (dbardha)

'''Mentor''': Sharique Khan (mkhan8)
 '''Professor''': Dr. Edward F. Gehringer (efg)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]

CSC/ECE 517 Fall 2019 - E1991. Improvements to anonymized view

2019-11-12T02:24:59Z

Sdpampat: /* Anonymized View For Students */

== ''' Introduction ''' ==
The [http://expertiza.ncsu.edu/ Expertiza] project takes advantage of peer-review among students to allow them to learn from each other. Tracking the time that a student spends on each submitted resources is meaningful to instructors to study and improve the teaching experience. Unfortunately, most peer assessment systems do not manage the content of students’ submission within the systems. They usually allow the authors to submit external links to the submission (e.g. GitHub code / deployed application), which makes it difficult for the system to track the time that the reviewers spend on the submissions.

== ''' Problem Statement ''' ==
The main idea of this exercise is to improve anonymized view in Expertiza. The feature is already implemented. However, there are issues / limitations with the current implementation which we will try to improve as a part of this project.

==== Anonymized View For Students ====
Currently, anonymized view is not implemented for students. Although, not directly required by students, instructors may want to use anonymized view when impersonating a student.

==== Issue with Impersonating Anonymized Student ====
In an anonymized view, instructors cannot impersonate a student because the username field has the anonymized name instead of their real name in the database. In order to be able to impersonate a student, we need to know their real names from database.

==== Wrong Anonymized Names ====
In some places, anonymized names are not shown. For example, heatgrid view.

==== Anonymizing Team Names ====
Currently, team names are not anonymized.

==== Optional Objective ====
Use randomized American names for anonymized users.

== ''' Proposed Solution ''' ==

In this section, we propose solutions to the problems / issues discussed above.

==== Anonymized View For Students ====
Instructors often use 'impersonate' functionality to use Expertiza as a different user. Sometimes they also need to use anonymized view while they are impersonating a student. Therefore, anonymized view needs to be extended to students as well.

In order to extend Anonymized view for students, the first thing we need to do is extend the following function :

<code>
def set_anonymized_view
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
session[:ip] = request.remote_ip
if anonymized_view_starter_ips.include? session[:ip]
anonymized_view_starter_ips.delete!(" #{session[:ip]}")
else
anonymized_view_starter_ips += " #{session[:ip]}"
end
$redis.set('anonymized_view_starter_ips', anonymized_view_starter_ips)
redirect_to :back
end
</code>

This function is responsible to switch back and forth between normal view and an anonymized view. We could figure out that the session of current user is being manipulated to change views. The main driving logic works by storing user's IP address in a value field of <code>anonymized_view_starter_ips</code> which is in Redis database.

Refer the following flow chart for design details:

[[File:D1.png|center]]

==== Impersonating Student Using Anonymized Names ====

When an instructor is already in Anonymized view and wants to impersonate a student, they have to quit the anonymized view and get the real username of that student. However, we want the instructor to be able to impersonate a student by using their anonymized names. The following function in <code>impersonate_controller.rb</code> is responsible to impersonate students.

<code>
def impersonate
...
begin
original_user = session[:super_user] || session[:user]
# Impersonate using form on /impersonate/start
if params[:impersonate].nil?
...
user = User.find_by(name: params[:user][:name])
...
else
# Impersonate a new account
if !params[:impersonate][:name].empty?
...
user = User.find_by(name: params[:impersonate][:name])
...
else
...
end
end
...
rescue Exception => e
flash[:error] = e.message
redirect_to :back
end
end
</code>

In the above snippet, we have omitted the irrelevant parts of code. The only change we need to do is the logic for <code>User.find_by()</code> function. We will add a condition to check whether the current view is anonymized or not. If anonymized mode is set, we will convert the anonymous name back to the original name of the student. We will then make 'find' query using the real name of the student instead of using their anonymized name.

The procedure to do this would be opposite of what we do to get anonymized names in first place. See following code snippet :

<code>
def name(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ' ' + self.id.to_s : self[:name]
end
</code>

The above snippet is an example of how anonymized names are generated.

=== Anonymizing Team Names ===

Right now, team names are not anonymized. We need to add accessor methods for team names in <code>team.rb</code> model file.

Additionally, we need a <code>before</code> function to check whether Anonymized view is set or not. In this function, we will generate anonymized name whenever Anonymized view is set. This is very similar to existing implementation of anonymizing user names as shown below :

<code>
def self.anonymized_view?(ip_address = nil)
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
return true if ip_address and anonymized_view_starter_ips.include? ip_address
false
end
...
def fullname(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ', ' + self.id.to_s : self[:fullname]
end
</code>

=== Wrong Anonymized Names ===

In some parts of the application, anonymized names are not working properly right now. It is highly difficult to find all such occurrences in the application at this early stage of the project. We are working to find all such occurrences.

However, we figured out that we need a common helper function to determine the name of a student based on whether Anonymized view is set or not. We will use the same function whenever we need to display name of a student. The function will internally take care of checking whether to return anonymized name or the real name.

=== ''' User Flowchart/Design ''' ===

== ''' Test Plan ''' ==

In this section, we discuss what the expected output of all the features will be in terms of well defined test steps.

==== Anonymized View For Students ====

# Login as an instructor
# Impersonate a student
# Switch to Anonymized view as a student

Right now, (3) is not supported.

==== Impersonating Student Using Anonymized Names ====

# Login as an instructor
# Switch to Anonymized view
# Find a student from list of users
# Assert that the student name is anonymized
# Use the anonymized name to impersonate the real user behind anonymous entity

Currently, (5) is not supported

==== Anonymizing Team Names ====

# Login as an instructor
# Switch to Anonymized view
# All team names should now be anonymized

In current implementation, (3) is not supported

==== Wrong Anonymized Names ====

We are yet to triage the scope of this functionality.

==== American English Names for Anonymized Students ====

# Login as an instructor
# Switch to Anonymized view
# Anonymized student names should be normal human names in American English, instead of cryptic names like <code>student12312</code>

== ''' Team Information ''' ==
#Shubham Dilip Pampattiwar (sdpampat)
#Pranav Maruti Gaikwad (pmgaikwa)
#Omkar Sunil Kulkarni (oskulkar)
#Deepayan Bardhan (dbardha)

'''Mentor''': Sharique Khan (mkhan8)
 '''Professor''': Dr. Edward F. Gehringer (efg)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]

CSC/ECE 517 Fall 2019 - E1991. Improvements to anonymized view

2019-11-12T02:24:24Z

Sdpampat: /* Anonymized View For Students */

== ''' Introduction ''' ==
The [http://expertiza.ncsu.edu/ Expertiza] project takes advantage of peer-review among students to allow them to learn from each other. Tracking the time that a student spends on each submitted resources is meaningful to instructors to study and improve the teaching experience. Unfortunately, most peer assessment systems do not manage the content of students’ submission within the systems. They usually allow the authors to submit external links to the submission (e.g. GitHub code / deployed application), which makes it difficult for the system to track the time that the reviewers spend on the submissions.

== ''' Problem Statement ''' ==
The main idea of this exercise is to improve anonymized view in Expertiza. The feature is already implemented. However, there are issues / limitations with the current implementation which we will try to improve as a part of this project.

==== Anonymized View For Students ====
Currently, anonymized view is not implemented for students. Although, not directly required by students, instructors may want to use anonymized view when impersonating a student.

==== Issue with Impersonating Anonymized Student ====
In an anonymized view, instructors cannot impersonate a student because the username field has the anonymized name instead of their real name in the database. In order to be able to impersonate a student, we need to know their real names from database.

==== Wrong Anonymized Names ====
In some places, anonymized names are not shown. For example, heatgrid view.

==== Anonymizing Team Names ====
Currently, team names are not anonymized.

==== Optional Objective ====
Use randomized American names for anonymized users.

== ''' Proposed Solution ''' ==

In this section, we propose solutions to the problems / issues discussed above.

==== Anonymized View For Students ====
Instructors often use 'impersonate' functionality to use Expertiza as a different user. Sometimes they also need to use anonymized view while they are impersonating a student. Therefore, anonymized view needs to be extended to students as well.

In order to extend Anonymized view for students, the first thing we need to do is extend the following function :

<code>
def set_anonymized_view
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
session[:ip] = request.remote_ip
if anonymized_view_starter_ips.include? session[:ip]
anonymized_view_starter_ips.delete!(" #{session[:ip]}")
else
anonymized_view_starter_ips += " #{session[:ip]}"
end
$redis.set('anonymized_view_starter_ips', anonymized_view_starter_ips)
redirect_to :back
end
</code>

This function is responsible to switch back and forth between normal view and an anonymized view. We could figure out that the session of current user is being manipulated to change views. The main driving logic works by storing user's IP address in a value field of <code>anonymized_view_starter_ips</code> which is in Redis database.

Refer the following flow chart for design details:

[[File:D1.png]]

==== Impersonating Student Using Anonymized Names ====

When an instructor is already in Anonymized view and wants to impersonate a student, they have to quit the anonymized view and get the real username of that student. However, we want the instructor to be able to impersonate a student by using their anonymized names. The following function in <code>impersonate_controller.rb</code> is responsible to impersonate students.

<code>
def impersonate
...
begin
original_user = session[:super_user] || session[:user]
# Impersonate using form on /impersonate/start
if params[:impersonate].nil?
...
user = User.find_by(name: params[:user][:name])
...
else
# Impersonate a new account
if !params[:impersonate][:name].empty?
...
user = User.find_by(name: params[:impersonate][:name])
...
else
...
end
end
...
rescue Exception => e
flash[:error] = e.message
redirect_to :back
end
end
</code>

In the above snippet, we have omitted the irrelevant parts of code. The only change we need to do is the logic for <code>User.find_by()</code> function. We will add a condition to check whether the current view is anonymized or not. If anonymized mode is set, we will convert the anonymous name back to the original name of the student. We will then make 'find' query using the real name of the student instead of using their anonymized name.

The procedure to do this would be opposite of what we do to get anonymized names in first place. See following code snippet :

<code>
def name(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ' ' + self.id.to_s : self[:name]
end
</code>

The above snippet is an example of how anonymized names are generated.

=== Anonymizing Team Names ===

Right now, team names are not anonymized. We need to add accessor methods for team names in <code>team.rb</code> model file.

Additionally, we need a <code>before</code> function to check whether Anonymized view is set or not. In this function, we will generate anonymized name whenever Anonymized view is set. This is very similar to existing implementation of anonymizing user names as shown below :

<code>
def self.anonymized_view?(ip_address = nil)
anonymized_view_starter_ips = $redis.get('anonymized_view_starter_ips') || ''
return true if ip_address and anonymized_view_starter_ips.include? ip_address
false
end
...
def fullname(ip_address = nil)
User.anonymized_view?(ip_address) ? self.role.name + ', ' + self.id.to_s : self[:fullname]
end
</code>

=== Wrong Anonymized Names ===

In some parts of the application, anonymized names are not working properly right now. It is highly difficult to find all such occurrences in the application at this early stage of the project. We are working to find all such occurrences.

However, we figured out that we need a common helper function to determine the name of a student based on whether Anonymized view is set or not. We will use the same function whenever we need to display name of a student. The function will internally take care of checking whether to return anonymized name or the real name.

=== ''' User Flowchart/Design ''' ===

== ''' Test Plan ''' ==

In this section, we discuss what the expected output of all the features will be in terms of well defined test steps.

==== Anonymized View For Students ====

# Login as an instructor
# Impersonate a student
# Switch to Anonymized view as a student

Right now, (3) is not supported.

==== Impersonating Student Using Anonymized Names ====

# Login as an instructor
# Switch to Anonymized view
# Find a student from list of users
# Assert that the student name is anonymized
# Use the anonymized name to impersonate the real user behind anonymous entity

Currently, (5) is not supported

==== Anonymizing Team Names ====

# Login as an instructor
# Switch to Anonymized view
# All team names should now be anonymized

In current implementation, (3) is not supported

==== Wrong Anonymized Names ====

We are yet to triage the scope of this functionality.

==== American English Names for Anonymized Students ====

# Login as an instructor
# Switch to Anonymized view
# Anonymized student names should be normal human names in American English, instead of cryptic names like <code>student12312</code>

== ''' Team Information ''' ==
#Shubham Dilip Pampattiwar (sdpampat)
#Pranav Maruti Gaikwad (pmgaikwa)
#Omkar Sunil Kulkarni (oskulkar)
#Deepayan Bardhan (dbardha)

'''Mentor''': Sharique Khan (mkhan8)
 '''Professor''': Dr. Edward F. Gehringer (efg)

==References==

#[https://github.com/expertiza/expertiza Expertiza on GitHub]

File:D2 (1).png

2019-11-12T02:16:29Z

Sdpampat:

2019-10-28T19:25:23Z

Sdpampat: /* Testing */

Servo is a prototype web browser engine written in the [https://en.wikipedia.org/wiki/Rust_(programming_language) Rust] language. Servo is a new, experimental browser that supports synchronously compiling and executing WebAssembly code, but does not yet support asynchronous compilation. This means that the entire WebAssembly program must be fetched before compilation can begin, which leads to longer time loading pages that run WebAssembly programs than in other web browsers. The goal of the project is to support compiling WebAssembly programs asynchronously so compilation can begin while the program is still being fetched from the network.

=='''Introduction'''==

===Servo===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo]Servo is an open source prototype web browser layout engine being developed by Mozilla, and it is written in [https://www.rust-lang.org/ Rust] language. The main idea is to create a highly parallel environment, in which different components can be handled by fine grained, isolated tasks. The different components can be rendering, HTML parsing, etc.

===Rust===
[https://doc.rust-lang.org/book/index.html Rust] is an open source systems programming language developed by Mozilla. Servo is written in Rust. The main purpose behind it's design is to be thread safe and concurrent. The emphasis is also on speed, safety and control of memory layout.

=='''Scope'''==

The scope of the project was to complete the initial steps mentioned [https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project here].

The steps are as follows:

* The project requirement initially stated that we build and Compile servo. Following are the steps for this:
Servo is built with [https://mail.mozilla.org/pipermail/rust-dev/2014-March/009090.html Cargo], the Rust package manager. Mozilla's Mach tools are used to orchestrate the build and other tasks.

git clone https://github.com/servo/servo
cd servo
./mach build --dev
./mach run tests/html/about-mozilla.html

* Create a rust JS::StreamConsumer wrapper that stores a pointer to the object and has methods for consumeChunk, streamEnd, streamError, and noteResponseURLs.
* Implement an extern "C" function in script_runtime.rs that matches ConsumeStreamCallback that initiates the streaming webassembly compilation then creates a wrapper for the stream consumer and stores it in the Response object
* Implement an extern "C" function in script_runtime.rs that matches ReportStreamErrorCallback and reports an error with the error! macro
* Lastly, call InitStreamConsumerCallback in new_rt_and_cx with the two new functions as arguments, described in the specifications

The subsequent steps mentioned [https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project here] are to be done for the final project.

=='''Design Pattern'''==

=='''Testing'''==

Unfortunately, the code added in the initial steps(scope) is not expected to have any change in behaviour on its own. The best we can do is to load https://wasm.bootcss.com/demo/Tanks/ and verify that there is no change in behaviour due to our changes.

Following are the steps to run all the tests for XMLHttpRequest:

# Install the pre-requisites required for servo as mentioned [https://github.com/servo/servo/blob/master/README.md here]
# Run the following commands

<code>
cd
</code>

<code>
git clone https://github.com/Akash-Pateria/servo
</code>

<code>
cd servo
</code>

<code>
git checkout -b origin/async-wasm-compilation-initial
</code>

<code>
./mach fmt
</code>

<code>
./mach test-tidy
</code>

<code>
./mach build -d
</code>

=='''Pull Request'''==

Here is our [https://github.com/servo/servo/pull/24563 pull request]. In the PR, you can see all the code snippets added to implement the above-mentioned steps.

=='''Conclusion'''==

=='''References'''==
1. https://doc.rust-lang.org/book 
2. https://en.wikipedia.org/wiki/Rust_(programming_language) 
3. https://en.wikipedia.org/wiki/Servo_(layout_engine) 
4. https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project 
6. http://rustbyexample.com/

CSC/ECE 517 Fall 2019 - M1950. Support Asynchronous Web Assembly Compilation

2019-10-28T19:25:09Z

Sdpampat: /* Testing */

Servo is a prototype web browser engine written in the [https://en.wikipedia.org/wiki/Rust_(programming_language) Rust] language. Servo is a new, experimental browser that supports synchronously compiling and executing WebAssembly code, but does not yet support asynchronous compilation. This means that the entire WebAssembly program must be fetched before compilation can begin, which leads to longer time loading pages that run WebAssembly programs than in other web browsers. The goal of the project is to support compiling WebAssembly programs asynchronously so compilation can begin while the program is still being fetched from the network.

=='''Introduction'''==

===Servo===
[https://en.wikipedia.org/wiki/Servo_(layout_engine) Servo]Servo is an open source prototype web browser layout engine being developed by Mozilla, and it is written in [https://www.rust-lang.org/ Rust] language. The main idea is to create a highly parallel environment, in which different components can be handled by fine grained, isolated tasks. The different components can be rendering, HTML parsing, etc.

===Rust===
[https://doc.rust-lang.org/book/index.html Rust] is an open source systems programming language developed by Mozilla. Servo is written in Rust. The main purpose behind it's design is to be thread safe and concurrent. The emphasis is also on speed, safety and control of memory layout.

=='''Scope'''==

The scope of the project was to complete the initial steps mentioned [https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project here].

The steps are as follows:

* The project requirement initially stated that we build and Compile servo. Following are the steps for this:
Servo is built with [https://mail.mozilla.org/pipermail/rust-dev/2014-March/009090.html Cargo], the Rust package manager. Mozilla's Mach tools are used to orchestrate the build and other tasks.

git clone https://github.com/servo/servo
cd servo
./mach build --dev
./mach run tests/html/about-mozilla.html

* Create a rust JS::StreamConsumer wrapper that stores a pointer to the object and has methods for consumeChunk, streamEnd, streamError, and noteResponseURLs.
* Implement an extern "C" function in script_runtime.rs that matches ConsumeStreamCallback that initiates the streaming webassembly compilation then creates a wrapper for the stream consumer and stores it in the Response object
* Implement an extern "C" function in script_runtime.rs that matches ReportStreamErrorCallback and reports an error with the error! macro
* Lastly, call InitStreamConsumerCallback in new_rt_and_cx with the two new functions as arguments, described in the specifications

The subsequent steps mentioned [https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project here] are to be done for the final project.

=='''Design Pattern'''==

=='''Testing'''==

Unfortunately, the code added in the initial steps(scope) is not expected to have any change in behaviour on its own. The best we can do is to load https://wasm.bootcss.com/demo/Tanks/ and verify that there is no change in behaviour due to our changes.

Following are the steps to run all the tests for XMLHttpRequest:

# Install the pre-requisites required for servo as mentioned [https://github.com/servo/servo/blob/master/README.md here]
# Run the following commands

<code>
cd
</code>

<code>
git clone https://github.com/Akash-Pateria/servo
</code>

<code>
cd servo
</code>

<code>
git checkout -b origin/async-wasm-compilation-initial
</code>

<code>
./mach fmt
</code>

<code>
./mach test-tidy
</code>

<code>

./mach build -d
</code>

=='''Pull Request'''==

Here is our [https://github.com/servo/servo/pull/24563 pull request]. In the PR, you can see all the code snippets added to implement the above-mentioned steps.

=='''Conclusion'''==

=='''References'''==
1. https://doc.rust-lang.org/book 
2. https://en.wikipedia.org/wiki/Rust_(programming_language) 
3. https://en.wikipedia.org/wiki/Servo_(layout_engine) 
4. https://github.com/servo/servo/wiki/Asynchronous-WebAssembly-compilation-project 
6. http://rustbyexample.com/

CSC/ECE 517 Fall 2019 - M1950. Support Asynchronous Web Assembly Compilation

2019-10-28T19:17:01Z

Sdpampat: /* Testing */

CSC/ECE 517 Fall 2019 - M1950. Support Asynchronous Web Assembly Compilation

2019-10-28T19:16:37Z

Sdpampat: /* Testing */