🎉 New Source: Twilio Taskrouter API [low-code cdk] #18685

aazam-gh · 2022-10-31T13:07:18Z

What

It's useful for twilio users to keep track of their workspaces. This connector adds workspace data from a user's twilio account using the workspace ID

How

This connector adds the following stream

workspaces

🚨 User Impact 🚨

No changes to existing code

Pre-merge Checklist

New Connector

Community member or Airbyter

Community member? Grant edit access to maintainers (instructions)
Secrets in the connector's spec are annotated with airbyte_secret
Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run ./gradlew :airbyte-integrations:connectors:<name>:integrationTest.
Code reviews completed
Documentation updated
- Connector's README.md
- Connector's bootstrap.md. See description and examples
- docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
- docs/integrations/README.md
- airbyte-integrations/builds.md
PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

Create a non-forked branch based on this PR and test the below items on it
Build is successful
If new credentials are required for use in CI, add them to GSM. Instructions.
/test connector=connectors/<name> command is passing
New Connector version released on Dockerhub by running the /publish command described here
After the connector is published, connector added to connector index as described here
Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Tests

Unit

None

Integration

Acceptance

CLAassistant · 2022-10-31T13:07:24Z

All committers have signed the CLA.

YiyangLi · 2022-10-31T18:33:15Z

@Alcadeus0 Thanks for your contribution. I will help to review it, will get back to you EOD.

aazam-gh · 2022-11-01T04:10:33Z

Sure!

YiyangLi

I think it's a good start. The source connector only returns one single workspace. I would encourage you to implement more streams under Taskrouter. Thanks.

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

airbyte-integrations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/spec.yaml

YiyangLi · 2022-11-01T04:25:41Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ record_selector:
+ $ref: "*ref(definitions.selector)"
+ paginator:
+ type: NoPagination


I understand that only one workspace is fetched, so there's no need to paginate. But if sid is offered, you can fetch other resources under the workspace. Can you implement one that requires a paginator?

And the Twilio's paginator is applied across all APIs, including taskrouter. Can you leverage codes in the existing source-twilio?

Do you want me to create another workspace stream and have the user enter the resource name? Because certain resources have indicated to avoid use of Page query in the taskrouter api

A paginator would be needed when the response is too long, or the resource set is huge. Consequently, the requester has to include the page number or another form of cursor to get the remaining parts.

For workspaces, the API "will return the first 50 Workspaces. Supply a PageSize parameter to fetch more than 50 Workspaces." Maybe you can't create multiple workspaces, but I guess the resource set is huge on other streams, for example, activities

Sure that works, so for the workspaces stream I'll have to add another optional parameter for the Page Size. Can you point me to a cdk doc on how to implement it? It would be great

"will return the first 50 Workspaces. Supply a PageSize parameter to fetch more than 50 Workspaces."

It comes from Twilio's API doc, you may supply the parameter to get more than 50. And you may pick or implement a paginator in order to get other pages. For example, the PageSize is 100, and there are 500 entities, there will be 5 pages in total. Airbyte needs to send 5 requests to complete a full import.

My suggestion is to have a workspaces stream that fetches all workspaces, and add another stream that depends on the required field workspaceId.

This is the doc for the paginator

I'm having some trouble implementing the paginator, so I've set it up so that the user can enter a page_size input and page_size reads it as page_size: "{{config['number']}}" but how do i convert it into an integer from a string

number is not part of spec.yaml. When you add it to the spec, you could set the type of an attribute to integer.

My understanding of page_size is it defines the number of entities in a page. You could set a constant number, for example, 50. Even a customer is allowed to use a large number, say 65535, the server-side on twilio may cap it to another number, say 200. And if there are thousands of entities, you need to turn the next page by including the page number.

https://github.com/airbytehq/airbyte/blob/master/airbyte-integrations/connectors/source-greenhouse/source_greenhouse/greenhouse.yaml

source-greenhouse is a good example, the greenhouse includes the page number in the headers of a response. It's an industry standard called RFC 8288. Twilio envelopes the entities, and set page_size, page_number and even the link to next page, called next_page_uri in the response body. Something like the following:

{ "page": 0, "page_size": 50, "uri": "\/2010-04-01\/Accounts\/ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\/Calls.json", "first_page_uri": "\/2010-04-01\/Accounts\/ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\/Calls.json?Page=0&PageSize=50", "previous_page_uri": null, "next_page_uri": "\/2010-04-01\/Accounts\/ACXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX\/Calls.json?Page=1&PageSize=50&AfterSid=CA228399228abecca920de212121", "calls": [

To test your pagination strategy, you don't need to create excessive resources. You could simply set page_size to a small number. For example, you have 6 workers, and the page size is 2, you need to paginate 3 times. After you run the read command, airbyte will tell you how many workers are read.

source-greenhouse is a good example, the greenhouse includes the page number in the headers of a response. It's an industry standard called RFC 8288. Twilio envelopes the entities, and set page_size, page_number and even the link to next page, called next_page_uri in the response body. Something like the following:

Yes, I was confused at first when the response header did not indicate the page_size and number but as you explained it enveloping it makes sense. I'll add the paginator source to the workers stream with the example values you provided and see how it goes.

@YiyangLi could you take a look at the changes and see if I need anything else?

airbyte-integrations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/spec.yaml

YiyangLi

It's good to see the progression. Can you share how to create

YiyangLi · 2022-11-04T20:15:20Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+
+check:
+ stream_names:
+ - "allworkspaces"


I think you only need one stream to verify the check

sure I'll remove the other two streams

it still requires fetching all 3 streams to verify the connectivity. Can you simplify it? Thanks.

Yeah i seemed to have made the new changes in only my topic branch. I'll push the changes to this branch

YiyangLi · 2022-11-04T20:18:33Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ path: "/v1/Workspaces"
+ primary_key: "sid"
+ retriever:
+ $ref: "*ref(definitions.base_stream.retriever)"


do you need the paginator for allworkspaces? I understand that in your test account, there's only one workspace, but for others, there might be more than 50, and a paginator is required. And to avoid a duplicated codes, you can have an incremental_stream that extends base_stream, and you can move the paginator from workers to the incremental stream. workers and allworkspaces extends the incremental_stream, and incremental_stream extends base_stream.

Is the incremental stream implemented using stream slicers? If so, the date-updated property of a workspace can be used

airbyte-integrations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/spec.yaml

YiyangLi · 2022-11-04T20:32:14Z

docs/integrations/sources/twiliotaskrouter.md

+
+1. Navigate to the Airbyte Open Source dashboard.
+2. Set the name for your source.
+3. Enter your `account_sid`.


can you provide more twilio links to tell users where to find the account_sid, auth_token and sid? Users don't see sid in the UI, the label text is the description, which is workspace Id.

YiyangLi · 2022-11-04T20:40:46Z

I just realized that you create the PR based on the master branch in the forked repository, can you use a topic branch?

YiyangLi · 2022-11-04T21:19:06Z

I run the command to fetch data, including workers, the read never stops. I guess it's the problem on the pagination, you need to tell airbyte to stop when it reaches to the last page. It happens when the next_page_url is null.

Take the following payload, it means the page size is 2, and the next page is page 1 (0-index based):

{ "workers": [ ...some workers here, skip it. ], "meta": { "page": 0, "page_size": 2, "first_page_url": "https://taskrouter.twilio.com/v1/Workspaces/WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Workers?PageSize=2&Page=0", "previous_page_url": null, "url": "https://taskrouter.twilio.com/v1/Workspaces/WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Workers?PageSize=2&Page=0", "next_page_url": "https://taskrouter.twilio.com/v1/Workspaces/WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Workers?PageSize=2&Page=1&PageToken=PAWK1WSXXXXXXXXXXXXXXXX", "key": "workers" } }

while for the next response, the next_page_url is null, meaning it reaches to the end.

{ "workers": [ ...some workers here, skip it. ], "meta": { "page": 0, "page_size": 2, "first_page_url": "https://taskrouter.twilio.com/v1/Workspaces/WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Workers?PageSize=2&Page=0", "previous_page_url": null, "url": "https://taskrouter.twilio.com/v1/Workspaces/WSXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/Workers?PageSize=2&Page=0", "next_page_url": null, "key": "workers" } }

You could reproduce the problem by setting a small page_size.

aazam-gh · 2022-11-05T08:30:31Z

I just realized that you create the PR based on the master branch in the forked repository, can you use a topic branch?

I created a new branch twilio-taskrouter but is there a way to edit the pull request to point to it instead of master branch? or should i create a new pr for it?

aazam-gh · 2022-11-05T13:01:21Z

I fixed the endless read error when paginating by implementing CursorPagination as it has a stop condition parameter and giving it a value of null ends when no more records are to be read

YiyangLi · 2022-11-06T16:45:13Z

I just realized that you create the PR based on the master branch in the forked repository, can you use a topic branch?

I created a new branch twilio-taskrouter but is there a way to edit the pull request to point to it instead of master branch? or should i create a new pr for it?

It's okay, just leave it as is. In order to be qualified for the Octoberfest bounty, you need to create the PR before Nov 4th.

Please make sure you share the edit permissions with us. https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork Me or the CI will push commits in order to get your codes published.

YiyangLi · 2022-11-06T16:50:37Z

I fixed the endless read error when paginating by implementing CursorPagination as it has a stop condition parameter and giving it a value of null ends when no more records are to be read

Not sure if you pushed your local commits correctly, the read in my local environment never ends. The version I am running is 2c6a104.

You could try it by the following commands.

Build

docker build . -t airbyte/source-twilio-taskrouter:dev

Run

docker run --rm -v $(pwd)/secrets:/secrets -v $(pwd)/integration_tests:/integration_tests airbyte/source-twilio-taskrouter:dev read --config /secrets/config.json --catalog /integration_tests/configured_catalog.json

In my Twilio account, I have 34 workers. I didn't set the page_size in the secrets/config.json. My config is similar to the sample_config.json you provide.

YiyangLi · 2022-11-06T16:52:05Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ extractor:
+ field_pointer: ["workers"]
+ paginator:
+ type: "DefaultPaginator"


I don't see the CursorPagination you refer to, did you forget to push your commits?

YiyangLi · 2022-11-06T18:42:13Z

I got the error.

{"type": "LOG", "log": {"level": "FATAL", "message": "\"The requested stream workspaces was not found in the source. Available streams: dict_keys(['allworkspaces'])

YiyangLi · 2022-11-06T18:47:01Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ field_pointer: ["workers"]
+
+streams:
+ - "*ref(definitions.allworkspaces_stream)"


you need to list other streams if they are configured in integration_tests/configured_catalog.json.

Yeah I listed the other streams

YiyangLi · 2022-11-06T18:49:08Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ inject_into: "request_parameter"
+ field_name: "page_size"
+ pagination_strategy:
+ type: "CursorPagination"


the paginator doesn't turn to the next page. In my test account, I have 57 workers, I would expect the connector firstly fetches the first 50 workers as 50 is the default page size, and it increases the page to 1 and use page=1 to get the remaining 7. But only the first 50 are read.

{"type": "LOG", "log": {"level": "INFO", "message": "Read 50 records from workers stream"}} {"type": "LOG", "log": {"level": "INFO", "message": "Finished syncing workers"}} {"type": "LOG", "log": {"level": "INFO", "message": "SourceTwilioTaskrouter runtimes:\nSyncing stream allworkspaces 0:00:00.364470\nSyncing stream workers 0:00:00.780400\nSyncing stream workspaces 0:00:00.384402"}} {"type": "LOG", "log": {"level": "INFO", "message": "Finished syncing SourceTwilioTaskrouter"}}

I've made sure the edit access for maintainers is checked, just need to fix the paginator. What could be the reason for it to be unable to read the remaining records. I'll try testing it out by creating more on my test acc

can you run the test again and see if it works?

What could be the reason for it to be unable to read the remaining records

The reason is that you need to parse response.body.meta, get the page number in the next_page_url, and use it to send the request again, until next_age_url is null.

request_url = "base_url/v1/workers"; do { response = request.get(request_url); request_url = response.body.meta.next_page_url; } while (request_url != null)

The pseudo-code looks like above.

where would i need to enter the code? in which file specifically? Is it by done by defining custom components?

Since a new paginator is introduced, please run unit tests, integration tests, and acceptance test in your local environment and provide the logs again. The one in the PR description is out-dated. Thanks.

https://docs.airbyte.com/connector-development/testing-connectors/source-acceptance-tests-reference

I tried with 5 workers and a page size of 2 and obtain the desired output

Here is the log of the new sets of tests

Thanks for all your help, really appreciate it

You are able to fetch 5 workers because the page_size of 2 is not passed to the request parameters. The property in the config.json plays no effects.

I still don't get 57 workers. When I use a different page_size, the result is the same, meaning only the first page is fetched.

where would i need to enter the code? in which file specifically? Is it by done by defining custom components?

I just offer you a pseudo-code to explain the algorithm behind, you need to set up the paginator correctly so that it works like what the algorithm describes. According to your yaml file, your paginator doesn't parse the response at all. Check greenhouse.yaml for an example.

YiyangLi · 2022-11-07T04:11:17Z

...grations/connectors/source-twilio-taskrouter/source_twilio_taskrouter/twilio_taskrouter.yaml

+ field_name: "page_size"
+ pagination_strategy:
+ type: "CursorPagination"
+ cursor_value: "{{ headers['url']['next'] }}"


you try to tell the paginator to get the cursor value from the headers. Are you sure the headers contain the value you want?

The following is an example response header when I try to GET /Workers

Date: Mon, 07 Nov 2022 04:10:22 GMT Content-Type: application/json Content-Length: 4151 Connection: keep-alive x-rate-limit-remaining: 50 x-rate-limit-limit: 50, 50;window=1 Twilio-Concurrent-Requests: 1 x-rate-limit-config: Worker-List Twilio-Request-Id: RQ5982d0470f1e214bfd748a8eb699f817 Twilio-Request-Duration: 0.021 Access-Control-Allow-Origin: * Access-Control-Allow-Headers: Accept, Authorization, Content-Type, If-Match, If-Modified-Since, If-None-Match, If-Unmodified-Since, Idempotency-Key Access-Control-Allow-Methods: GET, POST, DELETE, OPTIONS Access-Control-Expose-Headers: ETag Access-Control-Allow-Credentials: true X-Powered-By: AT-5000 X-Shenanigans: none X-Home-Region: us1 X-API-Domain: taskrouter.twilio.com Strict-Transport-Security: max-age=31536000

Okay, I'll figure out the appropriate cursor value to solve the response header

the cursor value doesn't come from the header. It's part of the response body, it's body["meta"]["next_page_uri"]

I had tried that but it shows that body is not defined

I'm trying with response['meta']['next_page_url'] but it shows the JSON Decode Error at line 1 col 1 char(0)

there's a case that next_page_url is null, which indicates you have reached the last page. And maybe that's the error reason of JSON deserializer.

When i try checking the API, it does show the next page url. Could it maybe related to the page_token injecting the path?

or maybe it's because I am using a record extractor to filter out the meta json respone?

When i try checking the API, it does show the next page url. Could it maybe related to the page_token injecting the path?

The next_page_url is the URL for the next page, you will get another next_page_url in the meta with this URL, until the value is null. This is the pseudo-code I provided you above. The right pagination strategy or paginator in the YAML works like the pseudo-code if it's configured correctly. You can also manually change the URL in a tool like postman to understand how it works.

request_url = "base_url/v1/workers"; do { response = request.get(request_url); request_url = response.body.meta.next_page_url; } while (request_url != null)

I did some adjustments and now it reads all the records, with the page size being 50

YiyangLi

[ ] pass the page_size to request parameters correctly since you put it under the spec.json
[ ] parse the cursor value correctly from the response, and use it for the next request if not null.

marcosmarxm · 2022-11-18T17:31:16Z

/test connector=connectors/source-twilio-taskrouter

🕑 connectors/source-twilio-taskrouter https://github.com/airbytehq/airbyte/actions/runs/3498970594
✅ connectors/source-twilio-taskrouter https://github.com/airbytehq/airbyte/actions/runs/3498970594
Python tests coverage:

 Name Stmts Miss Cover Missing ---------------------------------------------------------------------------------- source_acceptance_test/base.py 12 4 67% 16-19 source_acceptance_test/config.py 139 5 96% 87, 93, 235, 239-240 source_acceptance_test/conftest.py 196 92 53% 35, 41-43, 48, 54, 60, 66, 72-74, 93, 98-100, 106-108, 114-115, 120-121, 126, 132, 141-150, 156-161, 176, 200, 231, 237, 243-248, 256-261, 269-282, 287-293, 300-311, 318-334 source_acceptance_test/plugin.py 69 25 64% 22-23, 31, 36, 120-140, 144-148 source_acceptance_test/tests/test_core.py 398 111 72% 53, 58, 87-95, 100-107, 111-112, 116-117, 299, 337-354, 363-371, 375-380, 386, 419-424, 462-469, 512-514, 517, 582-590, 602-605, 610, 666-667, 673, 676, 712-722, 735-760 source_acceptance_test/tests/test_incremental.py 158 14 91% 52-59, 64-77, 240 source_acceptance_test/utils/asserts.py 37 2 95% 57-58 source_acceptance_test/utils/common.py 94 10 89% 16-17, 32-38, 72, 75 source_acceptance_test/utils/compare.py 62 23 63% 21-51, 68, 97-99 source_acceptance_test/utils/connector_runner.py 112 50 55% 23-26, 32, 36, 39-68, 71-73, 76-78, 81-83, 86-88, 91-93, 96-114, 148-150 source_acceptance_test/utils/json_schema_helper.py 107 13 88% 30-31, 38, 41, 65-68, 96, 120, 192-194 ---------------------------------------------------------------------------------- TOTAL 1563 349 78%

Build Passed

Test summary info:

=========================== short test summary info ============================ SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/plugin.py:63: Skipping TestIncremental.test_two_sequential_reads: not found in the config. SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:88: The previous connector image could not be retrieved. SKIPPED [1] ../usr/local/lib/python3.9/site-packages/source_acceptance_test/tests/test_core.py:364: The previous connector image could not be retrieved. ================= 26 passed, 3 skipped, 29 warnings in 25.33s ==================

marcosmarxm · 2022-11-18T17:35:10Z

I added a SubStreamSlicer to read all workspaces and read all other endpoints with the stream slicer. Also make pagination to work, now reads the 57 records in worker stream.

marcosmarxm · 2022-11-18T17:56:58Z

/publish connector=connectors/source-twilio-taskrouter

🕑 Publishing the following connectors:
connectors/source-twilio-taskrouter
https://github.com/airbytehq/airbyte/actions/runs/3499125417

Connector	Did it publish?	Were definitions generated?
connectors/source-twilio-taskrouter	✅	✅

if you have connectors that successfully published but failed definition generation, follow step 4 here ▶️

marcosmarxm

Thanks @Alcadeus0 and @YiyangLi for the review.

aazam-gh · 2022-11-18T18:30:08Z

Thanks @marcosmarxm and @YiyangLi for reviewing and helping me with this PR.
Much appreciated :)

RealChrisSean · 2022-11-18T19:15:47Z

@Alcadeus0 can you please update your profile with your email? :)

If you prefer, you can DM me instead with the following:

Email
Full Name
link to this PR

Thanks!

aazam-gh · 2022-11-18T20:24:52Z

@RealChrisSean I've added my email to my profile.

aazam-gh added 6 commits October 31, 2022 12:48

Created Workspaces Stream for Connector

170d03f

Created MD file for docs

7276a9c

Added source_definitions

32cb9e3

Removed Catalog.json

13c454f

Fixed SAT errors

850e1f0

Fixed typos in docs

ca37ddd

github-actions bot added area/connectors Connector related issues area/documentation Improvements or additions to documentation labels Oct 31, 2022

octavia-squidington-iv added bounty community connectors/source/twilio-taskrouter labels Oct 31, 2022

aazam-gh mentioned this pull request Oct 31, 2022

New Source: Twilio TaskRouter airbytehq/connector-contest#187

Closed

marcosmarxm added the hacktober label Oct 31, 2022

sajarin assigned YiyangLi Oct 31, 2022

sajarin added the bounty-XL Maintainer program: claimable extra large bounty PR label Oct 31, 2022

marcosmarxm changed the title ~~New Source: Twilio Taskrouter API~~ 🎉 New Source: Twilio Taskrouter API [low-code cdk] Oct 31, 2022

bleonard added the reward-200 label Oct 31, 2022

YiyangLi reviewed Nov 1, 2022

View reviewed changes

aazam-gh and others added 6 commits November 2, 2022 00:33

Implemented allworkspaces stream

e4d7525

Added Workers stream

ac56d36

Pagination Support

378d0dd

Update twiliotaskrouter.md

121bd74

Adjusted Pagination

6ec0d73

Update twilio_taskrouter.yaml

2c6a104

YiyangLi reviewed Nov 4, 2022

View reviewed changes

Fixed next_page_uri error

48da61e

Adjusted Docs to include Workspace ID

2a1c8f9

YiyangLi suggested changes Nov 6, 2022

View reviewed changes

aazam-gh added 2 commits November 7, 2022 00:02

Merge branch 'master' of github.com:Alcadeus0/airbyte

00bed4b

Added Cursor Paginator

14715d4

YiyangLi reviewed Nov 6, 2022

View reviewed changes

YiyangLi suggested changes Nov 6, 2022

View reviewed changes

Update twilio_taskrouter.yaml

9ffc5ab

YiyangLi reviewed Nov 7, 2022

View reviewed changes

YiyangLi suggested changes Nov 7, 2022

View reviewed changes

aazam-gh and others added 3 commits November 14, 2022 00:49

Update twilio_taskrouter.yaml

89ceced

Update twilio_taskrouter.yaml

2c361e4

fix connector

2ebfbf7

marcosmarxm added 2 commits November 18, 2022 12:33

Merge branch 'master' into master

a2ca148

add twilio version

eff31e2

octavia-squidington-iii and others added 2 commits November 18, 2022 18:14

auto-bump connector version

264e9e1

Merge branch 'master' into master

433d682

marcosmarxm approved these changes Nov 18, 2022

View reviewed changes

marcosmarxm merged commit a81c7af into airbytehq:master Nov 18, 2022

🎉 New Source: Twilio Taskrouter API [low-code cdk] #18685

🎉 New Source: Twilio Taskrouter API [low-code cdk] #18685

Uh oh!

Conversation

aazam-gh commented Oct 31, 2022

What

How

Recommended reading order

🚨 User Impact 🚨

Pre-merge Checklist

Community member or Airbyter

Airbyter

Tests

CLAassistant commented Oct 31, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

YiyangLi commented Oct 31, 2022

aazam-gh commented Nov 1, 2022

YiyangLi left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Uh oh!

YiyangLi left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

YiyangLi commented Nov 4, 2022

YiyangLi commented Nov 4, 2022

aazam-gh commented Nov 5, 2022

aazam-gh commented Nov 5, 2022

YiyangLi commented Nov 6, 2022

YiyangLi commented Nov 6, 2022

Choose a reason for hiding this comment

YiyangLi commented Nov 6, 2022

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

YiyangLi Nov 6, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

aazam-gh Nov 6, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

aazam-gh Nov 15, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

YiyangLi left a comment

CLAassistant commented Oct 31, 2022 •

edited

Loading

YiyangLi Nov 6, 2022 •

edited

Loading

aazam-gh Nov 6, 2022 •

edited

Loading

aazam-gh Nov 15, 2022 •

edited

Loading

marcosmarxm commented Nov 18, 2022 •

edited by github-actions bot

Loading

marcosmarxm commented Nov 18, 2022 •

edited by github-actions bot

Loading