status-im
/
sourcecred
mirror of https://github.com/status-im/sourcecred.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
sourcecred/sharness/__snapshots__/example-github-scores.json

325 lines
7.7 KiB
JSON
Raw Normal View History

add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
[
{
"type": "sourcecred/cli/scores",
scores command no longer assumes GitHub plugin (#1372) Previously, the `sourcecred scores` command assumed that all users are GitHub users, and assigned users an id based on their GitHub login. Now, the command returns information on all users, regardless of which plugin provided them. As such, we need to identify users differently. Instead of a string id, they now have an array of address parts. That array contains all of the parts of their corresponding node address. For example, the GitHub user `@Beanow` would correspond to the address array `["sourcecred", "github", "USERLIKE", "USER", "Beanow"]` As a general convention, the first two components of any node's address contain information about the plugin that owns that node. The first component is the owner of the plugin, and the second is the name of the plugin. Afterwards, the plugin may represent nodes in whatever manner it sees fit. Thanks to @Beanow and @vsoch for some feedback and discussion on this design. Test plan: Snapshots have been updated. `yarn test` passes.
2019-09-10 21:49:45 +00:00
"version": "0.2.0"
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
},
{
"intervals": [
{
"endTimeMs": 1520121600000,
"startTimeMs": 1519516800000
},
{
"endTimeMs": 1520726400000,
"startTimeMs": 1520121600000
},
{
"endTimeMs": 1521331200000,
"startTimeMs": 1520726400000
},
{
"endTimeMs": 1521936000000,
"startTimeMs": 1521331200000
},
{
"endTimeMs": 1522540800000,
"startTimeMs": 1521936000000
},
{
"endTimeMs": 1523145600000,
"startTimeMs": 1522540800000
},
{
"endTimeMs": 1523750400000,
"startTimeMs": 1523145600000
},
{
"endTimeMs": 1524355200000,
"startTimeMs": 1523750400000
},
{
"endTimeMs": 1524960000000,
"startTimeMs": 1524355200000
},
{
"endTimeMs": 1525564800000,
"startTimeMs": 1524960000000
},
{
"endTimeMs": 1526169600000,
"startTimeMs": 1525564800000
},
{
"endTimeMs": 1526774400000,
"startTimeMs": 1526169600000
},
{
"endTimeMs": 1527379200000,
"startTimeMs": 1526774400000
},
{
"endTimeMs": 1527984000000,
"startTimeMs": 1527379200000
},
{
"endTimeMs": 1528588800000,
"startTimeMs": 1527984000000
},
{
"endTimeMs": 1529193600000,
"startTimeMs": 1528588800000
},
{
"endTimeMs": 1529798400000,
"startTimeMs": 1529193600000
},
{
"endTimeMs": 1530403200000,
"startTimeMs": 1529798400000
},
{
"endTimeMs": 1531008000000,
"startTimeMs": 1530403200000
},
{
"endTimeMs": 1531612800000,
"startTimeMs": 1531008000000
},
{
"endTimeMs": 1532217600000,
"startTimeMs": 1531612800000
},
{
"endTimeMs": 1532822400000,
"startTimeMs": 1532217600000
},
{
"endTimeMs": 1533427200000,
"startTimeMs": 1532822400000
},
{
"endTimeMs": 1534032000000,
"startTimeMs": 1533427200000
},
{
"endTimeMs": 1534636800000,
"startTimeMs": 1534032000000
},
{
"endTimeMs": 1535241600000,
"startTimeMs": 1534636800000
},
{
"endTimeMs": 1535846400000,
"startTimeMs": 1535241600000
},
{
"endTimeMs": 1536451200000,
"startTimeMs": 1535846400000
},
{
"endTimeMs": 1537056000000,
"startTimeMs": 1536451200000
},
{
"endTimeMs": 1537660800000,
"startTimeMs": 1537056000000
},
{
"endTimeMs": 1538265600000,
"startTimeMs": 1537660800000
},
{
"endTimeMs": 1538870400000,
"startTimeMs": 1538265600000
},
{
"endTimeMs": 1539475200000,
"startTimeMs": 1538870400000
},
{
"endTimeMs": 1540080000000,
"startTimeMs": 1539475200000
},
{
"endTimeMs": 1540684800000,
"startTimeMs": 1540080000000
},
{
"endTimeMs": 1541289600000,
"startTimeMs": 1540684800000
},
{
"endTimeMs": 1541894400000,
"startTimeMs": 1541289600000
},
{
"endTimeMs": 1542499200000,
"startTimeMs": 1541894400000
},
{
"endTimeMs": 1543104000000,
"startTimeMs": 1542499200000
},
{
"endTimeMs": 1543708800000,
"startTimeMs": 1543104000000
},
{
"endTimeMs": 1544313600000,
"startTimeMs": 1543708800000
},
{
"endTimeMs": 1544918400000,
"startTimeMs": 1544313600000
},
{
"endTimeMs": 1545523200000,
"startTimeMs": 1544918400000
},
{
"endTimeMs": 1546128000000,
"startTimeMs": 1545523200000
},
{
"endTimeMs": 1546732800000,
"startTimeMs": 1546128000000
},
{
"endTimeMs": 1547337600000,
"startTimeMs": 1546732800000
},
{
"endTimeMs": 1547942400000,
"startTimeMs": 1547337600000
},
{
"endTimeMs": 1548547200000,
"startTimeMs": 1547942400000
}
],
"users": [
{
scores command no longer assumes GitHub plugin (#1372) Previously, the `sourcecred scores` command assumed that all users are GitHub users, and assigned users an id based on their GitHub login. Now, the command returns information on all users, regardless of which plugin provided them. As such, we need to identify users differently. Instead of a string id, they now have an array of address parts. That array contains all of the parts of their corresponding node address. For example, the GitHub user `@Beanow` would correspond to the address array `["sourcecred", "github", "USERLIKE", "USER", "Beanow"]` As a general convention, the first two components of any node's address contain information about the plugin that owns that node. The first component is the owner of the plugin, and the second is the name of the plugin. Afterwards, the plugin may represent nodes in whatever manner it sees fit. Thanks to @Beanow and @vsoch for some feedback and discussion on this design. Test plan: Snapshots have been updated. `yarn test` passes.
2019-09-10 21:49:45 +00:00
"address": [
"sourcecred",
"github",
"USERLIKE",
"USER",
"decentralion"
],
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
"intervalCred": [
Fix full build after #1391 (#1393) In #1391, I updated the default alpha, but forgot to regenerate the load snapshots. This caused a [nightly build failure][1]. This commit fixes it. Test plan: `yarn test --full` passes. [1]: https://circleci.com/gh/sourcecred/sourcecred/2300
2019-09-30 23:37:04 +00:00
9.734371505131229,
4.866769476502015,
5.45967678251199,
4.7373704438615425,
2.3682738955453986,
1.183726718845694,
0.5914613180048877,
0.2953441802319966,
0.1473144899165441,
3.4978536212952984,
1.7559491655988428,
0.8839962777883124,
0.44653137513507696,
0.22600614078858708,
0.11412708331142937,
0.04241671830125515,
0.02095600332095804,
0.5492132258029613,
0.27337032661021154,
0.13551003711598433,
0.06682765923330519,
0.03282560139637494,
0.01614582900556915,
0.008011848698948467,
0.0040263763117773495,
0.002045146244647576,
0.234125107916456,
0.11935025856951863,
2.066716441640751,
1.225987646747624,
0.6136508223713587,
0.3070637150934105,
0.15361287410473679,
0.07683553891284155,
0.03842818491166919,
0.019214582306587714,
0.009601140978431138,
0.004791390002030775,
0.002387368453447827,
0.0011885801142664197,
0.0005920728445612202,
0.00029490583043628775,
0.00014677639527190518,
0.000073579877320932,
0.00003767874911054204,
0.000019748431956321648,
0.000010429797539164292,
0.0000021162129948814497
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
],
Fix full build after #1391 (#1393) In #1391, I updated the default alpha, but forgot to regenerate the load snapshots. This caused a [nightly build failure][1]. This commit fixes it. Test plan: `yarn test --full` passes. [1]: https://circleci.com/gh/sourcecred/sourcecred/2300
2019-09-30 23:37:04 +00:00
"totalCred": 42.33425220677316
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
},
{
scores command no longer assumes GitHub plugin (#1372) Previously, the `sourcecred scores` command assumed that all users are GitHub users, and assigned users an id based on their GitHub login. Now, the command returns information on all users, regardless of which plugin provided them. As such, we need to identify users differently. Instead of a string id, they now have an array of address parts. That array contains all of the parts of their corresponding node address. For example, the GitHub user `@Beanow` would correspond to the address array `["sourcecred", "github", "USERLIKE", "USER", "Beanow"]` As a general convention, the first two components of any node's address contain information about the plugin that owns that node. The first component is the owner of the plugin, and the second is the name of the plugin. Afterwards, the plugin may represent nodes in whatever manner it sees fit. Thanks to @Beanow and @vsoch for some feedback and discussion on this design. Test plan: Snapshots have been updated. `yarn test` passes.
2019-09-10 21:49:45 +00:00
"address": [
"sourcecred",
"github",
"USERLIKE",
"USER",
"wchargin"
],
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
"intervalCred": [
Fix full build after #1391 (#1393) In #1391, I updated the default alpha, but forgot to regenerate the load snapshots. This caused a [nightly build failure][1]. This commit fixes it. Test plan: `yarn test --full` passes. [1]: https://circleci.com/gh/sourcecred/sourcecred/2300
2019-09-30 23:37:04 +00:00
3.2656284948687713,
1.6332305234979851,
0.7903232174880094,
0.387629556138458,
0.19422610445460123,
0.0975232811543062,
0.049163681995112264,
0.024968319768003445,
0.012841760083455873,
2.0822245037047016,
1.034089896901157,
0.5110232534616876,
0.2509783904899231,
0.12274874202391291,
0.06025035809482062,
0.5447720024018698,
0.27263835703060446,
0.59758395437282,
0.3000282634776791,
0.15118925792796095,
0.07652198828866748,
0.03884922236461138,
0.01969158287492401,
0.009906857241298115,
0.004932976658345941,
0.002434530240414069,
0.2681147303260748,
0.13176966055174677,
4.058843517919881,
1.8367923330326925,
0.9177391675187996,
0.4586312798516685,
0.22923462336780273,
0.11458820982342821,
0.05728368945646571,
0.02864135487747973,
0.014326827613602582,
0.007172594293986085,
0.003594623694560603,
0.0018024159597377954,
0.0009034251924408875,
0.00045284318806476605,
0.00022709811397862172,
0.00011335737730433143,
0.00005578987820208967,
0.000026985881699994214,
0.00001293735928899364,
0.000009567365419197517
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
],
Fix full build after #1391 (#1393) In #1391, I updated the default alpha, but forgot to regenerate the load snapshots. This caused a [nightly build failure][1]. This commit fixes it. Test plan: `yarn test --full` passes. [1]: https://circleci.com/gh/sourcecred/sourcecred/2300
2019-09-30 23:37:04 +00:00
"totalCred": 20.665736109648424
add `sourcecred/scores` (#1223) The scores are lightly processed from their internal representation. Example usage: ``` $ yarn backend; $ node bin/sourcecred.js load sourcecred/sourcecred $ node bin/sourcecred.js scores sourcecred/sourcecred > scores.json ``` The data structure is as follows: ```js export type NodeOutput = {| +id: string, +totalCred: number, +intervalCred: $ReadOnlyArray<number>, |}; export type ScoreOutput = Compatible<{| +users: $ReadOnlyArray<NodeOutput>, +intervals: $ReadOnlyArray<Interval>, |}>; ``` Test plan: I added sharness tests at `sharness/test_cli_scores.t`. In the past, we've used javascript tests for CLI commands. However, those are pretty time-consuming to write, and are less robust than simply running the command from bash. Check the snapshot for a sense of what the new data format looks like. Also, the snapshot updater now updates this snapshot too. Relevant for #1047. Thanks to @Beanow for feedback on the output format and design. Thanks to @wchargin for help in code review.
2019-07-14 16:05:13 +00:00
}
]
}
]