You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*[#1220](https://github.com/mozilla/glean.js/pull/1220): Refactor virtual environment behavior to support virtual environments that aren't in the project root.
10
+
* This means it's possible to run Glean with a virtual environment created by `virtualenv` or `pyenv-virtualenv` without causing a Glean-specific `.venv` directory to be created in a project that is using Glean.
* Timestamps were observed to be negative in a few occurrences, for platforms that do not provide the `performance.now` API, namely QML, and in which we fallback to the `Date.now` API.
14
+
* If event timestamps are negative pings are rejected by the pipeline.
15
+
*[#1132](https://github.com/mozilla/glean.js/pull/1132): Retry ping request on network error with `keepalive: false`. This is sometimes an issue on Chrome browsers below v81.
16
+
*[#1170](https://github.com/mozilla/glean.js/pull/1170): Update glean_parser to version 5.0.0.
17
+
*[#1178](https://github.com/mozilla/glean.js/pull/1178): Enable running the `glean` command offline.
18
+
* When offline Glean will not attempt to install glean_parser.
19
+
*[#1178](https://github.com/mozilla/glean.js/pull/1178): Enable running the `glean` command with as many or as little arguments as wanted.
20
+
* Previously the command could only be run with 3 commands, even though all glean_parser commands would have been valid commands for the `glean` CLI.
21
+
*[#1210](https://github.com/mozilla/glean.js/pull/1210): Show comprehensive error message when missing `storage` permissions for Glean on web extensions.
22
+
*[#1223](https://github.com/mozilla/glean.js/pull/1223): Add `--glean-parser-version` command to CLI to allow users to retrieve the glean_parser version without installing glean_parser.
23
+
*[#1228](https://github.com/mozilla/glean.js/pull/1228): BUGFIX: Apply debug features before sending pings at initialize.
*[#1065](https://github.com/mozilla/glean.js/pull/1065): Delete minimal amount of data when invalid data is found while collecting ping.
10
-
* Previous behaviour was to delete the whole ping when invalid data was found on the database,
11
-
new behaviour only deletes the actually invalid data and leave the rest of the ping intact.
30
+
* Previous behavior was to delete the whole ping when invalid data was found on the database,
31
+
new behavior only deletes the actually invalid data and leave the rest of the ping intact.
12
32
*[#1065](https://github.com/mozilla/glean.js/pull/1065): Only import metric types into the library when they are used either by the user or Glean itself.
13
33
* Previously the code required to deserialize metric data from the database was always imported by the library even if the metric type was never used by the client. This effort will decrease the size of the Glean.js bundles that don't import all the metric types.
14
34
*[#1046](https://github.com/mozilla/glean.js/pull/1046): Remove legacy X-Client-Type X-Client-Version from Glean pings.
15
-
*[#1071](https://github.com/mozilla/glean.js/pull/1071): **BREAKING CHANGE**: Move the `testResetGlean` API from the Glean singletion and into it's own entry point `@mozilla/glean/testing`.
35
+
*[#1071](https://github.com/mozilla/glean.js/pull/1071): **BREAKING CHANGE**: Move the `testResetGlean` API from the Glean singleton and into it's own entry point `@mozilla/glean/testing`.
16
36
* In order to use this API one must import it through `import { testResetGlean } from "@mozilla/glean/testing"` instead of using it from the Glean singleton directly.
17
37
* This lower the size of the Glean library, because testing functionality is not imported unless in a testing environment.
18
38
* This change does not apply to QML. In this environment the API remains the same.
@@ -62,7 +82,7 @@
62
82
* Users may provide a folder name through the `VIRTUAL_ENV` environment variable.
63
83
* If the user is inside an active virtualenv the `VIRTUAL_ENV` environment variable is already set by Python. See: https://docs.python.org/3/library/venv.html.
64
84
*[#968](https://github.com/mozilla/glean.js/pull/968): Add runtime arguments type checking to `Glean.setUploadEnabled` API.
65
-
*[#970](https://github.com/mozilla/glean.js/pull/970): BUGFIX: Guarantee uploading is immediatelly resumed if the uploader has been stopped due to any of the uploading limits being hit.
85
+
*[#970](https://github.com/mozilla/glean.js/pull/970): BUGFIX: Guarantee uploading is immediately resumed if the uploader has been stopped due to any of the uploading limits being hit.
66
86
67
87
# v0.25.0 (2021-11-15)
68
88
@@ -79,10 +99,10 @@
79
99
80
100
*[#856](https://github.com/mozilla/glean.js/pull/856): Expose the `@mozilla/glean/web` entry point for using Glean.js in websites.
81
101
*[#856](https://github.com/mozilla/glean.js/pull/860): Implement the `PlatformInfo` module for the web platform.
82
-
* Out of `os`, `os_version`, `architecture` and `locale`, on the web platform, we can only retrive`os` and `locale` information. The other information will default to the known value `Unknown` for all pings coming from this platform.
102
+
* Out of `os`, `os_version`, `architecture` and `locale`, on the web platform, we can only retrieve`os` and `locale` information. The other information will default to the known value `Unknown` for all pings coming from this platform.
83
103
*[#856](https://github.com/mozilla/glean.js/pull/856): Expose the `@mozilla/glean/web` entry point for using Glean.js in websites.
84
104
*[#908](https://github.com/mozilla/glean.js/pull/908): BUGFIX: Guarantee internal `uploadEnabled` state always has a value.
85
-
* When `uploadEnabled` was set to `false` and then Glean was restarted with it still `false`, the internal `uploadEnabled` state was not being set. That should not cause particularly harmful behaviour, since `undefined` is still a "falsy" value. However, this would create a stream of loud and annoying log messages.
105
+
* When `uploadEnabled` was set to `false` and then Glean was restarted with it still `false`, the internal `uploadEnabled` state was not being set. That should not cause particularly harmful behavior, since `undefined` is still a "falsy" value. However, this would create a stream of loud and annoying log messages.
86
106
*[#898](https://github.com/mozilla/glean.js/pull/898): Implement the `Storage` module for the web platform.
*[#342](https://github.com/mozilla/glean.js/pull/342): BUGFIX: Fix timespan payload representatin to match exactly the payload expected according to the Glean schema.
225
+
*[#342](https://github.com/mozilla/glean.js/pull/342): BUGFIX: Fix timespan payload representation to match exactly the payload expected according to the Glean schema.
206
226
*[#343](https://github.com/mozilla/glean.js/pull/343): BUGFIX: Report the correct failure exit code when the Glean command line tool fails.
207
227
208
228
# v0.14.0 (2021-05-19)
@@ -314,7 +334,7 @@ logic, which allows for reliable sorting of events throughout restarts.
314
334
315
335
*[#123](https://github.com/mozilla/glean.js/pull/123): BUGFIX: Fix support for ES6 environments.
316
336
* Include `.js` extensions in all local import statements.
317
-
* ES6' module resolution algorithm does not currently support automatic resolution of file extensions and does not have the hability to import directories that have an index file. The extension and the name of the file being import need to _always_ be specified. See: https://nodejs.org/api/esm.html#esm_customizing_esm_specifier_resolution_algorithm
337
+
* ES6' module resolution algorithm does not currently support automatic resolution of file extensions and does not have the ability to import directories that have an index file. The extension and the name of the file being import need to _always_ be specified. See: https://nodejs.org/api/esm.html#esm_customizing_esm_specifier_resolution_algorithm
318
338
* Add a `type: module` declaration to the main `package.json`.
319
339
* Without this statement, ES6 support is disabled. See: https://nodejs.org/docs/latest-v13.x/api/esm.html#esm_enabling.:
320
340
* To keep support for CommonJS, in our CommonJS build we include a `package.json` that overrides the `type: module` of the main `package.json` with a `type: commonjs`.
@@ -327,7 +347,7 @@ logic, which allows for reliable sorting of events throughout restarts.
327
347
* This plugin listens to the `afterPingCollection` event. It receives the collected payload of a ping and returns an encrypted version of it using a JWK provided upon instantiation.
328
348
*[#95](https://github.com/mozilla/glean.js/pull/95): Add a `plugins` property to the configuration options and create an event abstraction for triggering internal Glean events.
329
349
* The only internal event triggered at this point is the `afterPingCollection` event, which is triggered after ping collection and logging, and before ping storing.
330
-
* Plugins are built to listen to a specific Glean event. Each plugin must define an `action`, which is executed everytime the event they are listening to is triggered.
350
+
* Plugins are built to listen to a specific Glean event. Each plugin must define an `action`, which is executed every time the event they are listening to is triggered.
331
351
*[#101](https://github.com/mozilla/glean.js/pull/101): BUGFIX: Only validate Debug View Tag and Source Tags when they are present.
332
352
*[#102](https://github.com/mozilla/glean.js/pull/102): BUGFIX: Include a Glean User-Agent header in all pings.
333
353
*[#97](https://github.com/mozilla/glean.js/pull/97): Add support for labeled metric types (string, boolean and counter).
@@ -345,8 +365,8 @@ logic, which allows for reliable sorting of events throughout restarts.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,8 +28,8 @@ As mentioned, Glean.js bugs are filed in Bugzilla. Anything on the Glean.js comp
28
28
with the tag [`[good first bug]`](https://bugzilla.mozilla.org/buglist.cgi?f1=status_whiteboard&v1=%5Bgood%20first%20bug%5D&o1=substring&resolution=---&query_format=advanced&f2=component&v2=Glean.js&list_id=15653400&o2=equals&classification=Client%20Software&classification=Developer%20Infrastructure&classification=Components&classification=Server%20Software&classification=Other)
29
29
is a good place to start.
30
30
31
-
These bugs will usually have a comment explaning the steps to get started working on them.
32
-
(If you find a `[good first bug]` that doesn't have an explainer comment, please ask for one).
31
+
These bugs will usually have a comment explaining the steps to get started working on them.
32
+
(If you find a `[good first bug]` that doesn't have an explanation comment, please ask for one).
33
33
34
34
If you are picking a good first bug or not, make sure you are assigned to the bug before sending a Pull Request for it.
0 commit comments