Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1187)

Side by Side Diff: packages/stack_trace/CHANGELOG.md

Issue 1400473008: Roll Observatory packages and add a roll script (Closed) Base URL: git@github.com:dart-lang/observatory_pub_packages.git@master
Patch Set: Created 5 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
« no previous file with comments | « packages/stack_trace/.test_config ('k') | packages/stack_trace/LICENSE » ('j') | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
(Empty)
1 ## 1.4.2
2
3 * Improve the display of `data:` URIs in stack traces.
4
5 ## 1.4.1
6
7 * Fix a crashing bug in `UnparsedFrame.toString()`.
8
9 ## 1.4.0
10
11 * `new Trace.parse()` and related constructors will no longer throw an exception
12 if they encounter an unparseable stack frame. Instead, they will generate an
13 `UnparsedFrame`, which exposes no metadata but preserves the frame's original
14 text.
15
16 * Properly parse native-code V8 frames.
17
18 ## 1.3.5
19
20 * Properly shorten library names for pathnames of folded frames on Windows.
21
22 ## 1.3.4
23
24 * No longer say that stack chains aren't supported on dart2js now that
25 [sdk#15171][] is fixed. Note that this fix only applies to Dart 1.12.
26
27 [sdk#15171]: https://github.com/dart-lang/sdk/issues/15171
28
29 ## 1.3.3
30
31 * When a `null` stack trace is passed to a completer or stream controller in
32 nested `Chain.capture()` blocks, substitute the inner block's chain rather
33 than the outer block's.
34
35 * Add support for empty chains and chains of empty traces to `Chain.parse()`.
36
37 * Don't crash when parsing stack traces from Dart VM stack overflows.
38
39 ## 1.3.2
40
41 * Don't crash when running `Trace.terse` on empty stack traces.
42
43 ## 1.3.1
44
45 * Support more types of JavaScriptCore stack frames.
46
47 ## 1.3.0
48
49 * Support stack traces generated by JavaScriptCore. They can be explicitly
50 parsed via `new Trace.parseJSCore` and `new Frame.parseJSCore`.
51
52 ## 1.2.4
53
54 * Fix a type annotation in `LazyTrace`.
55
56 ## 1.2.3
57
58 * Fix a crash in `Chain.parse`.
59
60 ## 1.2.2
61
62 * Don't print the first folded frame of terse stack traces. This frame
63 is always just an internal isolate message handler anyway. This
64 improves the readability of stack traces, especially in stack chains.
65
66 * Remove the line numbers and specific files in all terse folded frames, not
67 just those from core libraries.
68
69 * Make padding consistent across all stack traces for `Chain.toString()`.
70
71 ## 1.2.1
72
73 * Add `terse` to `LazyTrace.foldFrames()`.
74
75 * Further improve stack chains when using the VM's async/await implementation.
76
77 ## 1.2.0
78
79 * Add a `terse` argument to `Trace.foldFrames()` and `Chain.foldFrames()`. This
80 allows them to inherit the behavior of `Trace.terse` and `Chain.terse` without
81 having to duplicate the logic.
82
83 ## 1.1.3
84
85 * Produce nicer-looking stack chains when using the VM's async/await
86 implementation.
87
88 ## 1.1.2
89
90 * Support VM frames without line *or* column numbers, which async/await programs
91 occasionally generate.
92
93 * Replace `<<anonymous closure>_async_body>` in VM frames' members with the
94 terser `<async>`.
95
96 ## 1.1.1
97
98 * Widen the SDK constraint to include 1.7.0-dev.4.0.
99
100 ## 1.1.0
101
102 * Unify the parsing of Safari and Firefox stack traces. This fixes an error in
103 Firefox trace parsing.
104
105 * Deprecate `Trace.parseSafari6_0`, `Trace.parseSafari6_1`,
106 `Frame.parseSafari6_0`, and `Frame.parseSafari6_1`.
107
108 * Add `Frame.parseSafari`.
109
110 ## 1.0.3
111
112 * Use `Zone.errorCallback` to attach stack chains to all errors without the need
113 for `Chain.track`, which is now deprecated.
114
115 ## 1.0.2
116
117 * Remove a workaround for [issue 17083][].
118
119 [issue 17083]: http://code.google.com/p/dart/issues/detail?id=17083
120
121 ## 1.0.1
122
123 * Synchronous errors in the [Chain.capture] callback are now handled correctly.
124
125 ## 1.0.0
126
127 * No API changes, just declared stable.
128
129 ## 0.9.3+2
130
131 * Update the dependency on path.
132
133 * Improve the formatting of library URIs in stack traces.
134
135 ## 0.9.3+1
136
137 * If an error is thrown in `Chain.capture`'s `onError` handler, that error is
138 handled by the parent zone. This matches the behavior of `runZoned` in
139 `dart:async`.
140
141 ## 0.9.3
142
143 * Add a `Chain.foldFrames` method that parallels `Trace.foldFrames`.
144
145 * Record anonymous method frames in IE10 as "<fn>".
OLDNEW
« no previous file with comments | « packages/stack_trace/.test_config ('k') | packages/stack_trace/LICENSE » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698