text:
Disable SSG Transform on Non-SSG Pages

As a performance optimization, this transform should not re-crawl scope or traverse the program unless the page was detected to be a SSG page.

Stats from current PR

Default Server Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
11.6s
11.7s
⚠ +108ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Rendered Page Sizes

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

index.html
4.06 kB
4.06 kB
✓

index.html gzip
1.03 kB
1.03 kB
✓

link.html
4.58 kB
4.58 kB
✓

link.html gzip
1.11 kB
1.11 kB
✓

withRouter.html
4.59 kB
4.59 kB
✓

withRouter.html gzip
1.1 kB
1.1 kB
✓

Overall change
13.2 kB
13.2 kB
✓

Serverless Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
11.7s
12s
⚠ +379ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Serverless bundles

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_error.js
256 kB
256 kB
✓

_error.js gzip
67.9 kB
67.9 kB
✓

hooks.html
4.19 kB
4.19 kB
✓

hooks.html gzip
1.07 kB
1.07 kB
✓

index.js
256 kB
256 kB
✓

index.js gzip
68 kB
68 kB
✓

link.js
289 kB
289 kB
✓

link.js gzip
77.2 kB
77.2 kB
✓

routerDirect.js
282 kB
282 kB
✓

routerDirect.js gzip
75.2 kB
75.2 kB
✓

withRouter.js
282 kB
282 kB
✓

withRouter.js gzip
75.3 kB
75.3 kB
✓

Overall change
1.37 MB
1.37 MB
✓

Commit: db9943045be8c6bb637d2a58489e1dc089c9519b

Stats from current PR

Default Server Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
13.4s
14s
⚠ +615ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Rendered Page Sizes

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

index.html
4.06 kB
4.06 kB
✓

index.html gzip
1.03 kB
1.03 kB
✓

link.html
4.58 kB
4.58 kB
✓

link.html gzip
1.11 kB
1.11 kB
✓

withRouter.html
4.59 kB
4.59 kB
✓

withRouter.html gzip
1.1 kB
1.1 kB
✓

Overall change
13.2 kB
13.2 kB
✓

Serverless Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
14.2s
13.9s
-283ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Serverless bundles

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_error.js
256 kB
256 kB
✓

_error.js gzip
67.9 kB
67.9 kB
✓

hooks.html
4.19 kB
4.19 kB
✓

hooks.html gzip
1.07 kB
1.07 kB
✓

index.js
256 kB
256 kB
✓

index.js gzip
68 kB
68 kB
✓

link.js
289 kB
289 kB
✓

link.js gzip
77.2 kB
77.2 kB
✓

routerDirect.js
282 kB
282 kB
✓

routerDirect.js gzip
75.2 kB
75.2 kB
✓

withRouter.js
282 kB
282 kB
✓

withRouter.js gzip
75.3 kB
75.3 kB
✓

Overall change
1.37 MB
1.37 MB
✓

Commit: d9e984ed777b543af8086164d955e285cb17d49d

Stats from current PR

Default Server Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
12.7s
12.6s
-112ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Rendered Page Sizes

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

index.html
4.06 kB
4.06 kB
✓

index.html gzip
1.03 kB
1.03 kB
✓

link.html
4.58 kB
4.58 kB
✓

link.html gzip
1.11 kB
1.11 kB
✓

withRouter.html
4.59 kB
4.59 kB
✓

withRouter.html gzip
1.1 kB
1.1 kB
✓

Overall change
13.2 kB
13.2 kB
✓

Serverless Mode (Increase detected ⚠)

General Overall increase ⚠

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

buildDuration
13.1s
12.9s
-178ms

nodeModulesSize
46.8 MB
46.8 MB
⚠ +27 B

Client Bundles (main, webpack, commons)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.js
18.3 kB
18.3 kB
✓

main-HASH.js gzip
6.44 kB
6.44 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

16b1a7225520..10012f496.js
20 kB
20 kB
✓

16b1a7225520..f496.js gzip
7.42 kB
7.42 kB
✓

4952ddcd88e7..49d7903c2.js
9.61 kB
9.61 kB
✓

4952ddcd88e7..03c2.js gzip
3.77 kB
3.77 kB
✓

commons.HASH.js
10.4 kB
10.4 kB
✓

commons.HASH.js gzip
3.91 kB
3.91 kB
✓

de003c3a9d30..a5a0ede39.js
21.2 kB
21.2 kB
✓

de003c3a9d30..de39.js gzip
8.19 kB
8.19 kB
✓

framework.HASH.js
126 kB
126 kB
✓

framework.HASH.js gzip
39.5 kB
39.5 kB
✓

Overall change
207 kB
207 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

main-HASH.module.js
14.2 kB
14.2 kB
✓

main-HASH.module.js gzip
5.36 kB
5.36 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

16b1a7225520..e5.module.js
21.2 kB
21.2 kB
✓

16b1a7225520..dule.js gzip
8.18 kB
8.18 kB
✓

4952ddcd88e7..cc.module.js
11.9 kB
11.9 kB
✓

4952ddcd88e7..dule.js gzip
4.42 kB
4.42 kB
✓

de003c3a9d30..80.module.js
15 kB
15 kB
✓

de003c3a9d30..dule.js gzip
6.15 kB
6.15 kB
✓

framework.HASH.module.js
126 kB
126 kB
✓

framework.HA..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
189 kB
189 kB
✓

Legacy Client Bundles (polyfills)

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

polyfills-HASH.js
15.3 kB
15.3 kB
✓

polyfills-HASH.js gzip
4.76 kB
4.76 kB
✓

Overall change
15.3 kB
15.3 kB
✓

Client Pages

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.js
2.93 kB
2.93 kB
✓

_app.js gzip
1.33 kB
1.33 kB
✓

_error.js
13.2 kB
13.2 kB
✓

_error.js gzip
5.11 kB
5.11 kB
✓

hooks.js
1.92 kB
1.92 kB
✓

hooks.js gzip
943 B
943 B
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
6.78 kB
6.78 kB
✓

link.js gzip
2.89 kB
2.89 kB
✓

routerDirect.js
413 B
413 B
✓

routerDirect.js gzip
285 B
285 B
✓

withRouter.js
423 B
423 B
✓

withRouter.js gzip
284 B
284 B
✓

Overall change
26 kB
26 kB
✓

Client Pages Modern

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_app.module.js
1.53 kB
1.53 kB
✓

_app.module.js gzip
745 B
745 B
✓

_error.module.js
10.3 kB
10.3 kB
✓

_error.module.js gzip
4.24 kB
4.24 kB
✓

hooks.module.js
651 B
651 B
✓

hooks.module.js gzip
371 B
371 B
✓

index.module.js
276 B
276 B
✓

index.module.js gzip
212 B
212 B
✓

link.module.js
5.45 kB
5.45 kB
✓

link.module.js gzip
2.46 kB
2.46 kB
✓

routerDirect.module.js
386 B
386 B
✓

routerDirect..dule.js gzip
275 B
275 B
✓

withRouter.module.js
396 B
396 B
✓

withRouter.m..dule.js gzip
274 B
274 B
✓

Overall change
19 kB
19 kB
✓

Client Build Manifests

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_buildManifest.js
244 B
244 B
✓

_buildManifest.js gzip
200 B
200 B
✓

_buildManifest.module.js
251 B
251 B
✓

_buildManife..dule.js gzip
209 B
209 B
✓

Overall change
495 B
495 B
✓

Serverless bundles

zeit/next.js canary
Timer/next.js safe/disable-on-non-ssg
Change

_error.js
256 kB
256 kB
✓

_error.js gzip
67.9 kB
67.9 kB
✓

hooks.html
4.19 kB
4.19 kB
✓

hooks.html gzip
1.07 kB
1.07 kB
✓

index.js
256 kB
256 kB
✓

index.js gzip
68 kB
68 kB
✓

link.js
289 kB
289 kB
✓

link.js gzip
77.2 kB
77.2 kB
✓

routerDirect.js
282 kB
282 kB
✓

routerDirect.js gzip
75.2 kB
75.2 kB
✓

withRouter.js
282 kB
282 kB
✓

withRouter.js gzip
75.3 kB
75.3 kB
✓

Overall change
1.37 MB
1.37 MB
✓

Commit: 47344a793568369228c8eaa40104a6ddf9179e20

authors: Timer ijjk


text:
Unable to deploy site to custom domain

I am unable to deploy open--this.site. I feel it has to do something with the domain having the 2 dashes. It throws  Error! The supplied domain is invalid (400), I have added nameservers to godaddy

I recently touched the custom domain of Punycode (IDN). This is the domain starting with "xn--".
But I have not encountered any problems.
For example: https://github.com/fu-sen/xn--ck8hk4b.tk to https://🎈😍.tk/
It is possible that a problem different from the domain is occurring.
Have you tried with a simple file structure?

Closing since this doesn't seem to be a problem any more.

source: gharchive/issue

authors: ayushxx7 fu-sen juliangruber

repo: zeit/now-cli

license_type: permissive

license_source: github-api


text:
Secret being set incorrectly

setting a secret with:
now secrets add email_pass "u5wV@#om$cLwAZC&mmlB3*2ly&Mm8bkv@54JOZ4N"
is getting the secret passed to my app as:
u5wV@#om&mmlB3*2ly&Mm8bkv@54JOZ4N
I'll put them one on top of each other to inspect them easier, first the original and then the output.
u5wV@#om$cLwAZC&mmlB3*2ly&Mm8bkv@54JOZ4N
u5wV@#om&mmlB3*2ly&Mm8bkv@54JOZ4N

I fixed this by changing the value to only numbers and letters, but I imagine this is unexpected behavior.

This issue was moved to zeit/now-cli#765

authors: captDaylight leo

repo: zeit/now


text:
Styled jsx with post css plugin breaks component testing in jest tests with nesting error

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When running jest tests with rendered react components I get the below error:
    Nesting detected at 5:5. Unfortunately nesting is not supported by styled-jsx.

      at Function.disableNestingPlugin (node_modules/styled-jsx/dist/lib/style-transform.js:24:13)
      at proxy (node_modules/styled-jsx/node_modules/stylis/stylis.js:1478:30)
      at compile (node_modules/styled-jsx/node_modules/stylis/stylis.js:890:14)
      at compile (node_modules/styled-jsx/node_modules/stylis/stylis.js:453:17)
      at compile (node_modules/styled-jsx/node_modules/stylis/stylis.js:453:17)
      at stylis (node_modules/styled-jsx/node_modules/stylis/stylis.js:1686:16)
      at transform (node_modules/styled-jsx/dist/lib/style-transform.js:122:3)
      at processCss (node_modules/styled-jsx/dist/_utils.js:494:51)
      at processTaggedTemplateExpression (node_modules/styled-jsx/dist/babel-external.js:58:38)
      at node_modules/styled-jsx/dist/babel-external.js:183:11

[styled-jsx] Loading plugin from path: styled-jsx-plugin-postcss
Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        2.374s

We are using post css with styled jsx. This works fine when building locally and has been running successfully in production for months. For some reason we are getting dinged for nested jsx.
If the current behavior is a bug, please provide the steps to reproduce and possibly a minimal demo or testcase in the form of a Next.js app, CodeSandbox URL or similar
test-example.js
import React from 'react';
import css from 'styled-jsx/css';
import renderer from 'react-test-renderer';

const styles = css`
  .title {
    &.nested-title-class {
      background: pink;
    }
  }
`;

const TestComponent = () => (

I am a test

);

describe('TestComponent', () => {
  it('should be able to render', () => {
    const wrapper = renderer.create(<TestComponent />);
    console.log('wrapper', wrapper);
  });
});

.babelrc
{
  "presets": ["next/babel"],
  "plugins": [
    ["styled-jsx/babel", { "plugins": ["styled-jsx-plugin-postcss"] }]
  ],
  "env": {
    "jest": {
      "presets": [
        ["next/babel", { "preset-env": { "modules": "commonjs" } }],
        ["env"]
      ],
      "plugins": [
        ["styled-jsx/babel-test"],
        ["transform-class-properties"],
        ["styled-jsx/babel", { "plugins": ["styled-jsx-plugin-postcss"] }]
      ]
    }
  }
}

package.json (condensed)
{
  "dependencies": {
    "@babel/polyfill": "^7.0.0-rc.2",
    "@babel/preset-env": "^7.0.0-rc.2",
    "babel-core": "7.0.0-bridge.0",
    "babel-jest": "^23.4.2",
    "babel-plugin-transform-class-properties": "^6.24.1",
    "babel-preset-env": "@2.0.0-alpha.20",
    "enzyme": "^3.4.4",
    "enzyme-adapter-react-16": "^1.2.0",
    "jest": "^23.5.0",
    "next": "^6.0.3",
    "postcss-calc": "^6.0.1",
    "postcss-color-function": "^4.0.1",
    "postcss-css-variables": "^0.11.0",
    "postcss-custom-media": "^6.0.0",
    "postcss-import": "^11.1.0",
    "postcss-nested": "^3.0.0",
    "prop-types": "^15.6.1",
    "react": "^16.3.2",
    "react-redux": "^5.0.7",
    "react-test-renderer": "^16.5.2",
    "redux": "^4.0.0",
    "styled-jsx": "^3.1.0",
    "styled-jsx-plugin-postcss": "^0.1.3",
  },
  "scripts": {
    "test": "NODE_ENV=jest jest",
    "test:watch": "NODE_ENV=jest jest --watch"
  }
}

jest.config.js
module.exports = {
  setupFiles: ['<rootDir>/jest.setup.js'],
  testPathIgnorePatterns: ['<rootDir>/.next/', '<rootDir>/node_modules/'],
  testRegex: '.*\\.test\\.js',
  moduleFileExtensions: ['js', 'jsx'],
  collectCoverageFrom: [
    '!jest.config.js',
    '!jest.setup.js',
    '!next.config.js',
    '**/*.{js,jsx}',
    '!coverage/**',
    '!server/**',
  ],
};

jest.setup.js
import polyfill from '@babel/polyfill'; /* eslint-disable-line */
import { configure } from 'enzyme';
import Adapter from 'enzyme-adapter-react-16';

configure({ adapter: new Adapter() });

postcss.config.js
const postcssImport = require('postcss-import');
const postcssCustomMedia = require('postcss-custom-media');

const postcssNested = require('postcss-nested');
const cssvariables = require('postcss-css-variables');
const colorFunction = require('postcss-color-function');
const postcssCalc = require('postcss-calc');

module.exports = {
  plugins: [
    postcssImport,
    postcssCustomMedia,

    postcssNested,
    cssvariables({
      preserve: false,
    }),
    colorFunction,
    postcssCalc,
  ],
};

What is the expected behavior?
That the test can render components with styled jsx with nested css sucessfully.
Environment (include versions)

OS: OSX 10.14
Browser: jest
styled-jsx (version): 3.1.0

Did this work in previous versions?
No

Sorry I don't have free time in this period to debug this issue, you might want to dig a bit. Better, you might want to disable styled-jsx when testing https://github.com/zeit/styled-jsx#rendering-in-tests
it is kinda useless to transpile styles for unit tests purposes.

repo: zeit/styled-jsx

license: mit

license_source: bigquery


text:
Remove item and add the same removed item

If you display selectbox with selected items:
For example:
<select multiple="multiple" class="multiselectbox" name="categories">
	<option value="3" selected="selected">cat1</option>
    <option value="6" selected="selected">cat5</option>
	<option value="5" selected="selected">cat2</option>
</select>

Then you do the following actions:

delete item (for example item "cat2")
you come back the same item that was removed ("cat2")

In the form, click on submit button and get this output:
'categories' =>
  array (size=2)
    0 => string '3'
    1 => string '6'

Yes, in output is not item "cat2".
SOLUTION:
Change line 516
from:
$('option[value="' + value + '"]', this.select).attr('selected', true);

to:
$('option[value="' + value + '"]', this.select).prop('selected', true);

Corrected with issue #54, please try with the last master version

I trying new version 2.5 in a firefox browser. Displays only the first item.
Look at the screenshot:

Your select element MUST have multiple attribute before tokenize initialization
https://github.com/zellerda/Tokenize/issues/20

So, I have in select element add multiple attribute. Init js script is below select element.
I get this error in console:
TypeError: this.tokensContainer.sortable is not a function

I will check that !

I have not option sortable.
This is my init script:
$('.multiselectbox').tokenize({ displayDropdownOnFocus: true });

Sorry I was to fast in my answer, that's corrected with the last version

Thank you for the quick action. It works perfectly.

authors: kevas zellerda

repo: zellerda/Tokenize


text:
Handle string URL specs handed over to establish_connection override for ActiveRecord 4.2

When trying to use this gem for setting up leader-follower DBs in a Rails 4.2 app on Heroku, I noticed that ENV["DATABASE_URL"] was getting coerced into a symbol and causing issues with ActiveRecord::ConnectionAdapters::ConnectionSpecification::Resolver.  I was getting this error in particular:
ActiveRecord::AdapterNotSpecified: 'adaptertype://blah@server:port/database' database is not configured. Available: ["development", "test", "production", "production_slave"]

This error was getting raised here: https://github.com/rails/rails/blob/v4.2.11/activerecord/lib/active_record/connection_adapters/connection_specification.rb#L248.
All versions of ActiveRecord 4.2 handle parsing string type spec inputs into either URLs or specific DB configs, so it makes sense to let it deal with the spec as is for the 4.2 patching.

Sorry for not looking into this PR before.
The patch non longer applies cleanly to master branch (after removing Rails 4.2 support there), but if you could rebase onto the 3-x-stable branch I can have another look.

source: gharchive/pull-request


text:
Support SASL OAuthBearer Authentication

Note: This is the same as this PR: (https://github.com/zendesk/ruby-kafka/pull/709). This one is just forked from Shopify as opposed to my personal fork. All the changes here are the last PR + any PR feedback that was left before @sam-obeid said "LGTM"!
This PR adds support for OAuthBearer as a method of SASL Authentication as described in KIP-255 and https://github.com/zendesk/ruby-kafka/issues/705.
When initializing the client, the user must pass in an instance of a class that implements a token method (the interface is described in lib/kafka/sasl/oauth.rb) which returns an ID Token.
Example:
require 'ruby-kafka'

class TokenProvider
    def token
        "some_id_token"
    end
end
# ...
client = Kafka.new(
    ["127.0.0.1:9094"],
    client_id: "phong-ruby-kafka",
    # ...
    sasl_over_ssl: false,
    sasl_oauth_token_provider: TokenProvider.new
)

Tested with a local Kafka cluster and ID Token, and successfully authenticated with the example client initialization above. I am open to suggestions for more cases to write unit tests for.

What other steps are there before getting this PR merged?
I ran tests with a test client that I wrote using my own TokenProvider against brokers in our staging environment and it was able to successfully authenticate and hold a connection!

Sorry, usually, after we approve, you can merge by yourself, but perhaps something changes. I already merge the PR for you 🙆♂

Sorry, usually, after we approve, you can merge by yourself, but perhaps something changes. I already merge the PR for you 🙆♂

repo: zendesk/ruby-kafka


text:
Unexpected behaviour when hydrating objects from Form inputs and from Database

If we use strategies attached to hydrator to do hydration, a method is called AbstractHydrator::hydrateValue($name, $value, $data = null). If we attach a strategy to hydrator using addStrategy() method, for hydration to take place, a $name must 100% match a key in the $data array. Here is the problem. Usually in the forms, people give names to <input>s with first letter lower-case, like someName. In databases, the column names are usually with the first letter capital, like SomeName. Then the name of the strategy you attach via addStrategy() starts to depend on where you get the $data array from: if from database, you must name strategy as SomeName (first letter capital), if from form, you must name the strategy someName (first letter lower-case) for object hydration to succeed. The two together cannot live.
This's quite annoying. Perhaps someone could fix it.

@ddodz

Usually in the forms, people give names to s with first letter lower-case, like someName. In databases, the column names are usually with the first letter capital, like SomeName.

Usually – maybe in your use case.

The two together cannot live.

The CompositeNamingStrategy could help.

Usually – maybe in your use case.

There is subjectivity in naming, I agree. The "best practices", if you can call them like these, are from a DB designer and webdeveloper as I wrote.

The CompositeNamingStrategy could help.

Not sure this will help. Depending on where the call for hydration comes from, either from form (to save in DB) or from a db mapper (to show data on the webpage), you'll have to use either first-letter-lower-case strategy or first-letter-capitalized strategy respectively. So you need a mechanism of distinguishing where the hydration call comes from and attach the CompositeNamingStrategy based on that. I don't see an easy way of implementing this.

@ddodz

So you need a mechanism of distinguishing where the hydration call comes from…

Add or remove a naming strategy. Example:
$hydrator = new \Zend\Hydrator\ClassMethods(false);

$hydrator->hydrate(
    [
        'SomeName' => 'Foo',
    ],
    $foo
);
var_dump($hydrator->extract($foo));
// array (size=1) 'someName' => string 'Foo' (length=3)

$hydrator->setNamingStrategy(
    new Zend\Hydrator\NamingStrategy\MapNamingStrategy(
        [
            'SomeName' => 'someName',
        ]
    )
);

$hydrator->hydrate(
    [
        'someName' => 'Bar',
    ],
    $foo
);
var_dump($hydrator->extract($foo));
// array (size=1) 'SomeName' => string 'Bar'

Is this behaviour correct?

@froschdesign thanks, my friend. What you write is correct, but the problem is elsewhere. Let's assume hydration is done using a strategy. You attach the strategy to the hydrator via addStrategy().
Look at the code of AbstractHydrator::hydrateValue($name, $value, $data = null). You'll see that for hydration to succeed, strategy name ($name) must == a key in array $data. The $data array is either array of html input names or array of DB column names. Now, if you hydrate in form, you have to ensure that the html input name == strategy name. If you hydrate in mapper, DB column name must == strategy name. For hydration to work well for both form and mapper, html input name should == column name. But if DB column name != strategy name (strategy name is someName and column name is SomeName) and html input name == strategy name, the errors appear when you hydrate using mapper. You could compensate for difference between column name and strategy name, as you suggested, using MapNamingStrategy(). But in this case, you must know upfront where the hydration takes place (in form or in mapper) so that you can prepare the hydrator accordingly. This means that you have to have either two separate hydrators and inject either of them based on where you hydrate, or use a hydrator factory that modifies the behaviour based on where hydration takes place (form or mapper). I don't think things should work like this, I believe this needs to be corrected in the source code of ZF3.
This whole explanation is a little cryptic, but I hope you understand what I mean.

I think the source code of ZF3 should be corrected.

Unfortunately, there is a misunderstanding. The source code is correct! Nothing is wrong. zend-hydrator works like documented. See also the blog post from today: "framework.zend.com - Convert objects to arrays and back with zend-hydrator"
You want a different behavior, which is not covered by the current implementation.

I understand, Frank. I wasn't saying the source code was wrong. The current implementation has a drawback though. It makes the strategy name dependent on both DB column names and html input names (I mean lower-case first letter and upper-case first letter thing). If there is a mismatch between those, you're running into problems. In the end, I spent 3 hours on trying to figure out what the problem was, and I may not be the only one who spent time on this :-)

I've reviewed this exchange, and I agree with @froschdesign
You need to hydrate for the context in which you will be consuming the end product. If that means the end produce needs the key names to be StudlyCaps, you will need to ensure your hydrator is configured accordingly. If you then need a different set of rules for extracting data for purposes of generating a JSON payload, you will need to create a different hydrator for that purpose.
While the general use case is for hydrators to be bi-directional, complicated use cases such as those you outlined require either asymmetric extraction/hydration strategies, or you need to create something custom. The latter can be done by implementing ExtractionInterface, HydrationInterface, or HydratorInterface (which is a union of the previous two). These can be created as anonymous classes, by extending or composing the shipped versions, or as dedicated classes you write yourself. Typically, however, I would not rely on strategies and naming strategies unless you are using the shipped hydrators without changes; those features exist to customize those specific approaches to allow them to act as general purpose hydrators. If you need something specific... the general-purpose hydrators are not the solution.

authors: ddodz froschdesign weierophinney

repo: zendframework/zend-hydrator


text:
Bad prototype

Running zend-test test suite against php 7.2
PHP Fatal error:  Declaration of Zend\Session\AbstractContainer::offsetGet($key) must be compatible with & Zend\Stdlib\ArrayObject::offsetGet($key) in ...
Indeed in Zend/Stdlib/ArrayObject.php
    public function &offsetGet($key)
and in Zend/Session/AbstractContainer.php
    public function offsetGet($key)
yes, really early report ;)

@remicollet isn't this technically a BC break in PHP 7.2? Did the signature change recently, or is the engine just being more strict about it?

Did the signature change recently, or is the engine just being more strict about it?

Yes the engine is more strict in 7.2
Technically, you could consider this as a small BC break, BTW, prototype are "really" different, so IMHO, better to report.

CC-ing in also @saramg: this is a subtle BC break.
While it is worth fixing it here, and it will be fixed, this can be extremely annoying to deal with, and should probably be put into discussion for 7.2...

CC-ing in also @saragolemon: this is a subtle BC break.
While it is worth fixing it here, and it will be fixed, this can be extremely annoying to deal with, and should probably be put into discussion for 7.2...

You're always welcome to reopen the discussion (I say reopen, because this kind of BC break was discussed and accepted as reasonable).  However IMO ZF is broken here and should reflect upon its life choices.

https://github.com/zendframework/zend-session/pull/78

This is fixed with the 2.8.0 release.

I put "&" at offsetGet function and found for me:
//Zend/Session/AbstractContainer.php line 425
public function &offsetGet($key)

Perfect!

authors: Ocramius Slamdunk marcosrdesouza remicollet sgolemon sumtsow weierophinney

repo: zendframework/zend-session


text:
AbstractOptions no longer camel casing methods names.

When checking if methods exists from array in AbstractOptions.php, ucwords is no longer applied resulting in BadMethodCallException which does actually use ucwords.
e.g. https://github.com/zendframework/zf2/blob/b1e9f3bb3ce9cdc925139d98672af40f6b0f33d7/library/Zend/Stdlib/AbstractOptions.php#L101
This is what it used to be - $setter = 'set' . str_replace(' ', '', ucwords(str_replace('_', ' ', $key)));

might be related to the changes in #7006.
But since the build for master is still passing on this point and methods are case insensitive it is probably an other issue.
Could you provide some more info? Like your OS and PHP version. And if possible your options class and the way you are calling it.

This is invalid: you most probably have a bug somewhere else: http://3v4l.org/94eT9
<?php

class Foo { function BAR() {}}

var_dump(method_exists(new Foo, 'bar'));
var_dump(method_exists(new Foo, 'BAR'));

Please open a different issue once you figured out the exact problem.

I am passing an array of options to setFromArray -
e.g
[
"name" => "Price Range",
"range" => "0.00-10.00"
];
Because __set no longer uses ucwords, it is looking for "getname" rather than "getName". As method_exists is case sensitive this now throws an exception.

Apologies for this.
Turns out the array I was passing through had a space in one of the array keys.
It would have been helpful if the exception uses the $setter variable defined previously instead of displaying a differently formatted setter. Because the exception indicated that it was looking for "getName" I went down a different route of debugging.
Ideally it should be
throw new Exception\BadMethodCallException(sprintf(
'The option "%s" does not have a matching "%s" setter method which must be defined',
$key,
$setter
));

It is indeed strange the exception uses a completely different setter which is not even used in the check in Zend\Stdlib\AbstractOptions line 103.
$setter = 'set' . str_replace('_', '', $key);

versus
'set' . str_replace(' ', '', ucwords(str_replace('_', ' ', $key)))

@iamtommetcalfe I created PR #7157 for a more accurate exception message.

authors: Martin-P Ocramius iamtommetcalfe jaapio


text:
Bug with SmartTomcat 4.3.1 - Cannot create temporary files

Hi @zengkid from the version 4.3.1 of SmartTomcat when my Spring application starts I see this warning in console:
22-Aug-2022 14:29:02.444 AVVERTENZA [main] org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.createMimeConfig Cannot create temporary files. Multipart attachments will be limited to "4.096" bytes.
	java.io.IOException: File o directory non esistente
		at java.base/java.io.UnixFileSystem.createFileExclusively(Native Method)
		at java.base/java.io.File.createTempFile(File.java:2129)
		at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.createMimeConfig(MultiPartReaderClientSide.java:119)
		at org.glassfish.jersey.media.multipart.internal.MultiPartReaderClientSide.<init>(MultiPartReaderClientSide.java:101)
		at org.glassfish.jersey.media.multipart.internal.MultiPartReaderServerSide.<init>(MultiPartReaderServerSide.java:57)
		at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
		at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
		at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
		at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490)
		at org.glassfish.hk2.utilities.reflection.ReflectionHelper.makeMe(ReflectionHelper.java:1356)
		at org.jvnet.hk2.internal.ClazzCreator.createMe(ClazzCreator.java:248)
		at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:342)
		at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:463)
		at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:59)
		at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:47)
		at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:74)
		at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
		at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:131)
		at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:176)
		at org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:98)
		at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2102)
		at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:93)
		at org.jvnet.hk2.internal.ServiceHandleImpl.getService(ServiceHandleImpl.java:67)
		at org.glassfish.jersey.inject.hk2.AbstractHk2InjectionManager.lambda$getAllServiceHolders$0(AbstractHk2InjectionManager.java:136)
		at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:195)
		at java.base/java.util.LinkedList$LLSpliterator.forEachRemaining(LinkedList.java:1239)
		at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
		at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
		at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
		at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
		at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
		at org.glassfish.jersey.inject.hk2.AbstractHk2InjectionManager.getAllServiceHolders(AbstractHk2InjectionManager.java:140)
		at org.glassfish.jersey.inject.hk2.ImmediateHk2InjectionManager.getAllServiceHolders(ImmediateHk2InjectionManager.java:30)
		at org.glassfish.jersey.internal.inject.Providers.getServiceHolders(Providers.java:307)
		at org.glassfish.jersey.internal.inject.Providers.getCustomProviders(Providers.java:151)
		at org.glassfish.jersey.message.internal.MessageBodyFactory.initialize(MessageBodyFactory.java:219)
		at org.glassfish.jersey.message.internal.MessageBodyFactory$MessageBodyWorkersConfigurator.postInit(MessageBodyFactory.java:114)
		at org.glassfish.jersey.server.ApplicationHandler.lambda$initialize$2(ApplicationHandler.java:353)
		at java.base/java.util.Arrays$ArrayList.forEach(Arrays.java:4390)
		at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:353)
		at org.glassfish.jersey.server.ApplicationHandler.lambda$initialize$1(ApplicationHandler.java:297)
		at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
		at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
		at org.glassfish.jersey.internal.Errors.processWithException(Errors.java:232)
		at org.glassfish.jersey.server.ApplicationHandler.initialize(ApplicationHandler.java:296)
		at org.glassfish.jersey.server.ApplicationHandler.<init>(ApplicationHandler.java:261)
		at org.glassfish.jersey.servlet.WebComponent.<init>(WebComponent.java:311)
		at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:154)
		at org.glassfish.jersey.servlet.ServletContainer.init(ServletContainer.java:347)
		at javax.servlet.GenericServlet.init(GenericServlet.java:158)
		at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1164)
		at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1117)
		at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1010)
		at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4957)
		at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5264)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:726)
		at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:698)
		at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:696)
		at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:690)
		at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1889)
		at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
		at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
		at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
		at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
		at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:583)
		at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:473)
		at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1618)
		at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:319)
		at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:123)
		at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:423)
		at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:366)
		at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:946)
		at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:835)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1396)
		at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1386)
		at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
		at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75)
		at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)
		at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:919)
		at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:265)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.StandardService.startInternal(StandardService.java:432)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:930)
		at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183)
		at org.apache.catalina.startup.Catalina.start(Catalina.java:772)
		at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
		at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
		at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
		at java.base/java.lang.reflect.Method.invoke(Method.java:566)
		at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)
		at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)

My versions:

Spring 5.3.22
Spring Security 5.7.3
org.glassfish.jersey.media -> jersey-media-multipart 2.36
org.glassfish.jersey.media -> jersey-media-json-jackson 2.36

With previuos version of SmartTomcat I had not this warning.
Intellij & SmartTomcat Version
IntelliJ IDEA 2022.2.1 (Community Edition)
Build #IC-222.3739.54, built on August 16, 2022
Runtime version: 17.0.3+7-b469.37 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Linux 5.15.0-46-generic
GC: G1 Young Generation, G1 Old Generation
Memory: 1940M
Cores: 8
Non-Bundled Plugins:
    idea.plugin.protoeditor (222.3739.24)
    com.vermouthx.idea (1.13.3)
    com.samdark.intellij-visual-studio-code-dark-plus (2.6)
    com.poratu.idea.plugins.tomcat (4.3.1)
    com.mallowigi (70.0.0)
    GenerateSerialVersionUID (3.0.3)
    Docker (222.3739.64)
    Dart (222.3739.24)
    io.flutter (69.0.5)

Kotlin: 222-1.7.10-release-334-IJ3739.54
Current Desktop: ubuntu:GNOME

I found the root cause and will fix it soon.

Fixed in 4.3.2, waiting for the approval, will be available tomorrow.

Fixed in 4.3.2, waiting for the approval, will be available tomorrow.

I saw your commit e4407557177f7944fe2938e40d17e4d933627abe and I'm waiting for the plugin update on IntelliJ.
Thanks a lot @yuezk

Yes. The workaround is to create the temp folder manually under the ~/.SmartTomcat/<project_name>/<module_name>/ folder.

authors: polilluminato yuezk

repo: zengkid/SmartTomcat


text:
support new version 15.11.7-ce

Adds unicode locale support.
Without it, the package install breaks with an error.

Dear @zeetabit ,
Thank you very much for your pull request. I appreciate your effort in adding unicode locale support. However, I would like to gather more information about the error you mentioned. As I mainly maintain the official repository for arm64 packaging, my goal is to keep it as close to the upstream image as possible. If the changes you propose are not specific to arm64 or involve modifications beyond that scope, it might be more appropriate to submit your changes directly to the upstream GitLab repository.
Could you please provide me with additional details regarding the error?
Thank you!

Hm, now the issue is not reproduced, sorry for that, closing.
p.s. so this PR just adds Unicode support to a container without real requirements

Hi, @zeetabit
Although the issue may not be present at this time, I still appreciate your efforts to improve the project.
No worries about the non-reproducible issue. It can happen as the environment varies from one to another. It's always good to double-check such things.
Thank you for your contribution and for bringing this to my attention. Don't hesitate to open a new pull request if you find any other issues or improvements in the future.
Thank you again for your time and effort!

authors: zeetabit zengxs


text:
Choose a visual identity

We are searching for someone motivated in providing a visual model for the website.
Inspiration: https://octoverse.github.com/projects

There has been talks of creating a design system for Zenika, should we stick to it or would the platform be independent in its design?

This project needs to be white labelled so other organizations could use it but we could customize Zenika's instance so it follows this "design system" 👍
Who can tell us more about this @christopherkade ?

We'll have a new art director at AYA in May and it seems like she'll be the one managing the design system project.
It may be too far off to rely on it, especially since we want the design to be white labelled. So the safest call would probably be to create a visual identity from scratch.

For the future template we need to be netlify compliant and include one of these badges : https://www.netlify.com/press/#badges

Closed by #41

authors: christopherkade frinyvonnick tbetous

repo: zenika-open-source/insights-website


text:
Changed to debug log

Describe changes
I wanted to clean up log output
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

@schustmi I understand but this should only be given once and it shouldnt be in the constructor.. Otherwise its spammy as hell. I think we can raise it when people are registering a component

Registering seems like a good compromise to me!

Maybe we can add a parameter like warn_about_plain_text_secrets to StackComponentConfig.__init__ which defaults to False, and then in Client.create_stack_component(...) we explicitly set it to True? This would only show the warning when registering a component, but the warning will not be shown in the dashboard (which should probably handle it differently anyway, e.g. using a dynamic warning message or automatically creating a secret)

repo: zenml-io/zenml


text:
html data-content becomes undefined

Hi, I have a custom Inline comment component (using Semantic UI) which creates this html:
    Official statistics say we are winning the War on Cancer. Cancer incidence rates, mortality rates, and five-year-survival
      rates have generally been moving in the right direction over the past few decades.

I save the html as a string. On load, I pass the string as value into React-Quill and data-content becomes "undefined":
    Official statistics say we are winning the War on Cancer. Cancer incidence rates, mortality rates, and five-year-survival
      rates have generally been moving in the right direction over the past few decades.

Any ideas as to why this happens/what I could change to prevent this from happening?
React-Quill version

[x ] master

You probably need a custom formatter registered with Quill:

https://quilljs.com/docs/modules/
https://github.com/zenoamaro/react-quill#custom-formats
https://github.com/quilljs/quill

authors: Strafos alexkrolick

repo: zenoamaro/react-quill


text:
Global loading-overlay

[x] Add global loading-overlay that can be toggled
[ ] Show loading-overlay while files are being processed

@nadar Please implement hide / show for fileupload.
Show while files are being processed uploading && serverProcessing.

repo: zephir/luya


text:
tests/kernel/interrupt fails on qemu_cortex_m0

Describe the bug
starting test - test_nested_isr
isr0 running !!
isr0 execution completed !!

    Assertion failed at ZEPHYR_BASE/tests/kernel/interrupt/src/nested_irq.c:91: isr0: (new_val not equal to old_val)
Nested interrupt is not working

FAIL - test_nested_isr

I am baffled as to why CI is not failing due to this.
To Reproduce
I'm running
sanitycheck -T tests/kernel/interrupt/

Expected behavior
Test passes.
Impact
I don't know if this is a problem with the test or the Cortex-M0 implementation.

Interesting, ran locally and it passes just fine for me.  What's your build.log look like?

I did do: sanitycheck -T tests/kernel/interrupt/ -p qemu_cortex_m0

@galak double-checking my environment and trying the build on some other machines, will follow up shortly.

This appears to be some kind of timing-sensitive race. On further testing, whether it passes or fails seems to be intermittent and depends on how loaded the host machine is.
It also looks like there is already some kind of issue with k_busy_wait() on this platform. The test has some ifdefs:
void isr0(void *param)
{
	ARG_UNUSED(param);
	printk("%s running !!\n", __func__);
#if defined(CONFIG_BOARD_QEMU_CORTEX_M0)
	/* QEMU Cortex-M0 timer emulation appears to not capturing the
	 * current time accurately, resulting in erroneous busy wait
	 * implementation.
	 *
	 * Work-around:
	 * Increase busy-loop duration to ensure the timer interrupt will fire
	 * during the busy loop waiting.
	 */
	k_busy_wait(MS_TO_US(1000));
#else
	k_busy_wait(MS_TO_US(10));
#endif
	printk("%s execution completed !!\n", __func__);
	zassert_equal(new_val, old_val, "Nested interrupt is not working\n");
}

@galak if I run this test outside of sanitycheck, it fails often for me. I think this needs deeper investigation, especially since I cannot find an open bug on k_busy_wait() on qemu_cortex_m0

authors: andrewboie galak

repo: zephyrproject-rtos/zephyr


text:
Can not flash test images into up_squared board.

To Reproduce
Steps to reproduce the behavior:

west build -b up_squared -p auto samples/hello_world/
west flash
See error

Screenshots or console output
[ztest@zserver12 zephyr]$ west flash ~/up_squared.sh
-- west flash: rebuilding
ninja: no work to do.
-- west flash: using runner misc-flasher
flash
FATAL ERROR: required program flash not found; install it or add its location to PATH
Environment (please complete the following information):

OS: fedora28
Toolchain: zephyr-sdk-0.11.1
Commit ID: 5372e78827a

Looks more like a development environment issue?

The flash script is probably only available on your CI system, and is specific to the DUT. Try finding the script in your CI and see if it works on your dev machine. Note that west flash is not supported on master. The official way is to provision a USB stick with GRUB and the Zephyr binary.
Closing this as this is expected and not a bug.

my script is ok to download test image into up_squared via pxe, and it worked well with commit "f8cb3d4d53" in master branch.
for up_squared, misc-flasher was added into master to support sanitycheck running on up_sqaured.

@mbolivar  it seems that this issue is related to commit "dc0948424e" in master.
my added command option "up_sqaured.sh" script in args was replaced by the "flash" command in user_args.

I have verified that west flash is broken with dc0948424ef3711e65e7f351dcaa74682ec3eb18.

I have verified that west flash is broken with dc09484.

@mbolivar FYI

I have verified that west flash is broken with dc09484.

@mbolivar FYI

This issue is specific to misc-flasher, so I've posted a fix to just that file in https://github.com/zephyrproject-rtos/zephyr/pull/23260.

authors: chen-png dcpleung jhedberg mbolivar


text:
RTT Tracing is not working using NXP mimxrt1064_evk

Describe the bug
I would like to use RTT tracing with Segger SystemView and it does not work as specified with NXP MIMXRT1064_EVK. My Segger J-Link is not able to find the RTT control block for this board. Using the same setup with another board (Atmel sam_e70b_xplained) does work without any problems.
To Reproduce
Steps to reproduce the behavior:

Add CONFIG_SEGGER_SYSTEMVIEW=y and CONFIG_TRACING=y to the prj.conf file of any application (for example for the synchonization sample)
Build and flash the application
Try to capture RTT data with Segger SystemView or open the Segger web control panel and switch to the tab "RTT"
SystemView shows the Error: "Could not find RTT Control Block"
The segger web control panel displays that there is no RTT communication at all

Expected behavior
RTT logging should work to analyze the applications behaviour. The same setup works out of the box with Atmel sam_e70b_xplained.
Environment (please complete the following information):

OS: Windows
Toolchain: gnu-arm-embedded
Commit: Release v2.3.0

@MaureenHelm thank you! I tested it and now SystemView does find the RTT control block but unfortunately it is not showing any received events or tasks. Furthermore the uart-terminal stops transmitting data as soon as I start recording in SystemView so possibly the CPU is halted.


text:
Zephyr generic multi-image meta

This is a meta issue trying to collect use-cases related to Zephyr multi-image builds.
Building of multiple images through a single build invocation together with flashing capabilities is a recurring feature request.
This meta issue tries to collect all the different scenarios which have been requested, including those which have a custom solution.
What is desired is an overall solution that is well designed and flexible enough to be extendable, both within Zephyr itself, but to the extend possible also providing hooks for downstream users.
Some examples:

Building and flashing of MCUBoot together with a Zephyr sample
Building and flashing of a custom bootloader together with a Zephyr sample
Building and flashing of a custom sample together with a Zephyr sample, for example Trusted-firmware-M
Building and flashing of a multi-core SoC where both images are Zephyr based, for example: ipc/openamp
Building and flashing of a multi-core SoC where one image is non-Zephyr based.
Building and flashing of a multi-core SoC, where the cores have different architectures.

Considerations:

Sharing of configuration data: Configuration data may need to be shared between projects.
One example is signing key when building a sample with MCUBoot. In such case the keys used for signing and verification must both be know to the build system. In this particular case the high level build system should be the configuration entry point and setting shared to the images.
This implies that settings that might be received from higher level should not be per-image configurable when handled by multi image build system.
Sharing of build information: A given image may need to have knowledge of output data / libraries from another image, for example:
Sample may need to have access to library and headers created by TF-M project.
Sample may need to have have to location and size information of an image.

Tasks covered with this meta issue:

[x] High level architectural design of an extendable solution
See: https://docs.google.com/presentation/d/1d4Jr7DPiAJdTqQGLzY3Zn6hbytdA0NlMl4ug91idHA8
[ ] Implementation of a framework, fixed by #40555
[ ] Support for MCUBoot use-case, see #40309, fixed by #40555
[ ] Support for custom bootloader
[ ] Multicore SoC image support

[ ] Convert samples under sample/subsys/ipc to multi image framework
[ ] Convert following use-cases to multi image framework
- Board: mps2_an521 multi image

#41697 tracks the use case required for #41579, namely the requirement to share information about a secondary image with a primary image in order to enable the primary core image to copy the secondary image from flash to ram

I would like to clarify a little the use-cases described as

Building and flashing of a multi-core SoC where both images are Zephyr based, for example: ipc/openamp

There are some samples in the Zephyr tree which by design can run only on multi-core SoC (like linked openamp samples). However, most of the available samples can run on single-core or multi-core SoCs. When these samples run on multi-core SoC, some require one image, other more.
For example net/sockets/echo_client requires two images if it is configured to use 802.15.4 radio on nRF53 SoC. If you build this sample, you must manually prepare, build, and flash matching configuration of boards/nrf/ieee802154/802154_rpmsg. Similarly, if you build any Bluetooth sample for nRF53, you must manually prepare, build, and flash matching configuration of bluetooth/hci_rpmsg to run on the Net core.
I would like multi-image builds to be able to catch such multi-core dependencies and automatically configure and build appropriate child images like:

if CONFIG_BT on CONFIG_SOC_NRF5340_CPUAPP then build hci_rpmsg
if CONFIG_IEEE802154 on CONFIG_SOC_NRF5340_CPUAPP then build 802154_rpmsg
if CONFIG_IEEE802154_2015 on CONFIG_SOC_NRF5340_CPUAPP then enable CONFIG_NRF_802154_ENCRYPTION for 802154_rpmsg build
if CONFIG_BT and CONFIG_IEEE802154 on CONFIG_SOC_NRF5340_CPUAPP then trigger build error - cannot generate matching child image

Would such child-image configuration/build helper fit in scope of multi-image building initiative?

authors: danieldegrasse hubertmis tejlmand


text:
Suggestion on the framework of Flash driver

As a Flash manufacturer, we hope to integrate various types of Flash drivers in Zephyr, such as SPI NOR Flash ,QSPI NOR Flash, Octal NOR Flash, SPI NAND Flash and ONFI NAND Flash.
We found that the framework of the existing Flash driver is shown in the following figure.

In the Flash folder there are various drivers, even for the same type of Flash, such as flash_stm32_qspi.c, nrf_qspi_nor.c. Each MCU manufacturer maintains a separate driver, which we think is inconvenient to maintain.
Therefore, we propose to modify the framework structure of the Flash driver. We divide the drivers of QSPI NOR Flash and OSPI NOR Flash into two layers, just like the drivers of SPI NOR Flash. The upper layer is a pure Flash driver. Each type of Flash has only one driver file. This layer has nothing to do with which MCU is used.
The lower layer is about the drivers of the Flash controllers of various MCU manufacturers. For example, the QSPI controller of ST corresponds to qspi_ll_stm32.c, the OSPI controller of ST corresponds to ospi_ll_stm32.c, and other manufacturers implement the corresponding ospi_xx. c. Each program in this layer needs to provide several APIs for the upper layer to call, such as ospi_read() and ospi_write() and so on.
We provide the following two solutions, as shown in the figure below:

We consider SPI NAND Flash and ONFI NAND Flash, and the expansion of the above picture is as follows:

We consider that there are already definitions for QSPI and OSPI modes in spi.h, and some drivers use these definitions, we provide solution 2:

At present, we have implemented the modification of the OSPI related program of solution 2, and passed the test on the STM32L562E-DK development board. A PR will be submitted later.

I'm looking forward for this rework. Probably the key factor for success will be proper API interface between vendors low layer driver part and higher generic flash driver part.

@rogeryou since the flash subsystem maintainer, @nvlsianpu, seems to have no objections to the proposal as it stands, will you send a Pull Request to start work on this?

Hi，@carlescufi
I have submitted the source code，please review.

Sorry for going off-topic. What application do you use to create the diagram?
@rogeryou  they look great!

Sorry for going off-topic. What application do you use to create the diagram? @rogeryou they look great!

draw.io

@rogeryou do you plan to return to this?

Any updates on this? Am interesting also in using NAND flash with Zephyr

+1

+1

@MaureenHelm @carlescufi @nvlsianpu
Hi,
Because some developers are also interested in using NAND flash with Zephyr, we will submit a PR for NFTL. The PR is based on the SPI NAND driver #50690. Can we reopen that PR  and discuss how to merge it?"

Because some developers are also interested in using NAND flash with Zephyr, we will submit a PR for NFTL. The PR is based on the SPI NAND driver #50690. Can we reopen that PR and discuss how to merge it?"

I see the PR is opened now, so let's continue the discussion in the PR.


text:
qemu_leon3: tests/posix/common/portability.posix.common fails

Describe the bug
The tests/posix/common/portability.posix.common test fails on the qemu_leon3 target:
ASSERTION FAIL [0] @ WEST_TOPDIR/zephyr/kernel/sched.c:1764
	aborted _current back from dead

This assertion failure occurs after the test successfully completes and the test thread is aborted (fails to swap):
https://github.com/zephyrproject-rtos/zephyr/blob/6cfb18686e1c494d0011aec87bbf24ab530d3a34/kernel/sched.c#L1761-L1765
To Reproduce
Build tests/posix/common/portability.posix.common for qemu_leon3 and run inside QEMU.
Expected behavior
Test passes.
Impact
CI reports a failure.
Logs and console output
Running TESTSUITE posix_apis
===================================================================
START - test_nanosleep_0_1
 PASS - test_nanosleep_0_1 in 0.020 seconds
===================================================================
START - test_nanosleep_0_1000000000
 PASS - test_nanosleep_0_1000000000 in 0.001 seconds
===================================================================
START - test_nanosleep_0_1001
 PASS - test_nanosleep_0_1001 in 0.019 seconds
===================================================================
START - test_nanosleep_0_500000000
 PASS - test_nanosleep_0_500000000 in 0.510 seconds
===================================================================
START - test_nanosleep_0_n1
 PASS - test_nanosleep_0_n1 in 0.001 seconds
===================================================================
START - test_nanosleep_1_0
 PASS - test_nanosleep_1_0 in 1.010 seconds
===================================================================
START - test_nanosleep_1_1
 PASS - test_nanosleep_1_1 in 1.020 seconds
===================================================================
START - test_nanosleep_1_1001
 PASS - test_nanosleep_1_1001 in 1.020 seconds
===================================================================
START - test_nanosleep_NULL_NULL
 PASS - test_nanosleep_NULL_NULL in 0.001 seconds
===================================================================
START - test_nanosleep_NULL_notNULL
 PASS - test_nanosleep_NULL_notNULL in 0.001 seconds
===================================================================
START - test_nanosleep_n1_0
 PASS - test_nanosleep_n1_0 in 0.001 seconds
===================================================================
START - test_nanosleep_n1_n1
 PASS - test_nanosleep_n1_n1 in 0.001 seconds
===================================================================
START - test_nanosleep_notNULL_NULL
 PASS - test_nanosleep_notNULL_NULL in 0.001 seconds
===================================================================
START - test_nanosleep_notNULL_notNULL
 PASS - test_nanosleep_notNULL_notNULL in 0.001 seconds
===================================================================
START - test_nanosleep_req_is_rem
 PASS - test_nanosleep_req_is_rem in 0.016 seconds
===================================================================
START - test_posix_clock
POSIX clock APIs
POSIX clock APIs test done
 PASS - test_posix_clock in 2.021 seconds
===================================================================
START - test_posix_mqueue
 PASS - test_posix_mqueue in 0.020 seconds
===================================================================
START - test_posix_multiple_threads_single_key

Different threads set different values to same key:
thread 0: set value = 1073897936 and retrieved value = 1073897936
thread 1: set value = 1073898160 and retrieved value = 1073898160

 PASS - test_posix_multiple_threads_single_key in 0.003 seconds
===================================================================
START - test_posix_normal_mutex
mutex lock is taken
 PASS - test_posix_normal_mutex in 0.217 seconds
===================================================================
START - test_posix_pthread_create_negative
 PASS - test_posix_pthread_create_negative in 0.001 seconds
===================================================================
START - test_posix_pthread_error_condition
 PASS - test_posix_pthread_error_condition in 0.001 seconds
===================================================================
START - test_posix_pthread_execution
Thread 0 starting with scheduling policy 0 & priority 15
Thread 1 starting with scheduling policy 0 & priority 15
Thread 2 starting with scheduling policy 0 & priority 15
Bounce test OK
Barrier test OK
 PASS - test_posix_pthread_execution in 2.795 seconds
===================================================================
START - test_posix_pthread_termination
Thread 0 starting with a priority of 4
Cancelling thread 0
Thread 1 starting with a priority of 3
Cancelling thread 1
Thread 1 could not be cancelled
Thread 2 starting with a priority of 2
Cancelling thread 2
Thread 3 starting with a priority of 1
Cancelling thread 3
Thread 3 could not be cancelled
 PASS - test_posix_pthread_termination in 1.006 seconds
===================================================================
START - test_posix_realtime
 PASS - test_posix_realtime in 2.000 seconds
===================================================================
START - test_posix_recursive_mutex
recursive mutex lock is taken
 PASS - test_posix_recursive_mutex in 0.001 seconds
===================================================================
START - test_posix_rw_lock

main acquire WR lock and 3 threads acquire RD lock
Thread 2 scheduling policy = 1 & priority 3 started
Not able to get RD lock on trying, try again
Thread 1 scheduling policy = 1 & priority 2 started
Not able to get RD lock on trying, try again
Thread 0 scheduling policy = 1 & priority 1 started
Not able to get RD lock on trying, try again
Parent thread releasing WR lock
Thread 2 got RD lock
Thread 1 got RD lock
Thread 0 got RD lock
Parent thread acquiring WR lock again
Thread 2 releasing RD lock
Thread 2 acquiring WR lock
Thread 1 releasing RD lock
Thread 1 acquiring WR lock
Thread 0 releasing RD lock
Parent thread acquired WR lock again
Thread 0 acquiring WR lock
Parent thread releasing WR lock again

3 threads acquire WR lock
Main thread acquiring RD lock
Thread 2 acquired WR lock
Thread 2 releasing WR lock
Main thread acquired RD lock
Main thread releasing RD lock
Thread 1 acquired WR lock
Thread 1 releasing WR lock
Thread 0 acquired WR lock
Thread 0 releasing WR lock
 PASS - test_posix_rw_lock in 0.139 seconds
===================================================================
START - test_posix_semaphore
 PASS - test_posix_semaphore in 5.012 seconds
===================================================================
START - test_posix_single_thread_multiple_keys

Single thread associates its value with different keys:
key 0: set value = 1073898360 and retrieved value = 1073898360
key 1: set value = 1073898360 and retrieved value = 1073898360

 PASS - test_posix_single_thread_multiple_keys in 0.002 seconds
===================================================================
START - test_posix_thread_attr_stacksize
 PASS - test_posix_thread_attr_stacksize in 0.001 seconds
===================================================================
START - test_posix_timer
POSIX timer test
Timer fires every 0 secs and  100000000 nsecs
Time remaining to fire 0 secs and  890000000 nsecs
Handler Signal value :20 for 1 times
Handler Signal value :20 for 2 times
Handler Signal value :20 for 3 times
Handler Signal value :20 for 4 times
Handler Signal value :20 for 5 times
Handler Signal value :20 for 6 times
Handler Signal value :20 for 7 times
Handler Signal value :20 for 8 times
Handler Signal value :20 for 9 times
Handler Signal value :20 for 10 times
Handler Signal value :20 for 11 times
Handler Signal value :20 for 12 times
 PASS - test_posix_timer in 2.117 seconds
===================================================================
START - test_pthread_descriptor_leak
 PASS - test_pthread_descriptor_leak in 0.011 seconds
===================================================================
TESTSUITE posix_apis succeeded

------ TESTSUITE SUMMARY START ------

SUITE PASS - 100.00% [posix_apis]: pass = 31, fail = 0, skip = 0, total = 31 duration = 18.970 seconds
 - PASS - [posix_apis.test_nanosleep_0_1] duration = 0.020 seconds
 - PASS - [posix_apis.test_nanosleep_0_1000000000] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_0_1001] duration = 0.019 seconds
 - PASS - [posix_apis.test_nanosleep_0_500000000] duration = 0.510 seconds
 - PASS - [posix_apis.test_nanosleep_0_n1] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_1_0] duration = 1.010 seconds
 - PASS - [posix_apis.test_nanosleep_1_1] duration = 1.020 seconds
 - PASS - [posix_apis.test_nanosleep_1_1001] duration = 1.020 seconds
 - PASS - [posix_apis.test_nanosleep_NULL_NULL] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_NULL_notNULL] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_n1_0] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_n1_n1] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_notNULL_NULL] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_notNULL_notNULL] duration = 0.001 seconds
 - PASS - [posix_apis.test_nanosleep_req_is_rem] duration = 0.016 seconds
 - PASS - [posix_apis.test_posix_clock] duration = 2.021 seconds
 - PASS - [posix_apis.test_posix_mqueue] duration = 0.020 seconds
 - PASS - [posix_apis.test_posix_multiple_threads_single_key] duration = 0.003 seconds
 - PASS - [posix_apis.test_posix_normal_mutex] duration = 0.217 seconds
 - PASS - [posix_apis.test_posix_pthread_create_negative] duration = 0.001 seconds
 - PASS - [posix_apis.test_posix_pthread_error_condition] duration = 0.001 seconds
 - PASS - [posix_apis.test_posix_pthread_execution] duration = 2.795 seconds
 - PASS - [posix_apis.test_posix_pthread_termination] duration = 1.006 seconds
 - PASS - [posix_apis.test_posix_realtime] duration = 2.000 seconds
 - PASS - [posix_apis.test_posix_recursive_mutex] duration = 0.001 seconds
 - PASS - [posix_apis.test_posix_rw_lock] duration = 0.139 seconds
 - PASS - [posix_apis.test_posix_semaphore] duration = 5.012 seconds
 - PASS - [posix_apis.test_posix_single_thread_multiple_keys] duration = 0.002 seconds
 - PASS - [posix_apis.test_posix_thread_attr_stacksize] duration = 0.001 seconds
 - PASS - [posix_apis.test_posix_timer] duration = 2.117 seconds
 - PASS - [posix_apis.test_pthread_descriptor_leak] duration = 0.011 seconds

------ TESTSUITE SUMMARY END ------

===================================================================
RunID: 9e2ff8b97f3a7da845c3d3a0c6ccdb19
PROJECT EXECUTION SUCCESSFUL
ASSERTION FAIL [0] @ WEST_TOPDIR/zephyr/kernel/sched.c:1764
	aborted _current back from dead
E:
E: tt = 0x8F, trap_instruction
E:
E:       INS        LOCALS     OUTS       GLOBALS
E:   0:  400166a0   f3000fc2   40015fa0   00000000
E:   1:  00000000   4000ebf0   000006e4   00000004
E:   2:  40016724   4000ebf4   40015fa0   00000006
E:   3:  40018000   00000004   000006e4   00000020
E:   4:  40016724   40008400   40018114   00000000
E:   5:  40015c00   f30000c0   40018000   00000100
E:   6:  400204d8   40000050   40020470   00000000
E:   7:  40006618   00000008   4000fb44   00000000
E:
E: psr: f39000c5   wim: 00000080   tbr: 400008f0   y: 00000000
E:  pc: 40007ef4   npc: 40007ef8
E:
E:       pc         sp
E:  #0   40007ef4   40020470
E:  #1   40006618   400204d8
E:  #2   400083d8   40020538
E:  #3   4000fcb0   00000000
E:
E: >>> ZEPHYR FATAL ERROR 4: Kernel panic on CPU 0
E: Current thread: 0x400166a0 (unknown)
E: Halting system

Environment (please complete the following information):

OS: Ubuntu 20.04
Toolchain: Zephyr SDK 0.14.2
Commit SHA: 0226e53e239f8562b0636a2a4e42e99b0894f784

Additional context
Bisected to 9a4b5e1d908575a552f15204a51c92c9732f3d84; however this commit, in itself, does not seem to be doing anything wrong and the failure is likely due to a more serious underlying issue.
This failure is likely due to an alignment-related issue:
https://github.com/zephyrproject-rtos/zephyr/blob/9a4b5e1d908575a552f15204a51c92c9732f3d84/subsys/testsuite/include/zephyr/tc_util.h#L56-L59
Changing the number of =s by -7 or +7 makes the assertion failure go away.
Related discussion on Discord: https://discord.com/channels/720317445772017664/733037890514321419/1007518292732289034
p.s. That this test also fails when compiled using the Zephyr SDK 0.15.0, so the issue is not toolchain or QEMU version specific.

For now, the quickest workaround is to specify -mfaster-structs, which forces all structs to have 8-byte alignment.
The root cause still needs to be investigated and fixed.

Took a quick look.  Agree that the alignment guess seems close.  After checking to be sure this wasn't a stack overflow (seriously: always check the stacks on weird stuff like this) I got it localized to a particular test case that isn't doing anything but creating a thread and joining it synchronously.  See notes in this patch: https://gist.github.com/andyross/d2edbd77463000e57b4c7a39cac31ed7
I thought it was a race at first, so I added a delay between the steps and that "fixed" it, as did a yield.  But so did a busywait, which is more suspicious (that shouldn't generally cause a context switch), and so did a busy wait of 1us, which was weird.  And so did a hand-written delay.  And so did the same hand written delay with a loop count of 1 that adds only four instructions and a stack word!  (And indeed, AFAICT the spawned thread never runs before the join in that final "working" case, it's not a race between them at all).
But hand-adding four NOPs did not fix the problem, nor did my attempts to expand the stack frame by a word via other means.  So no root cause yet.
But this definitely looks like a glitch in the platform context switch code.  That pthread_join() is just going to call arch_switch() synchronously.  My guess is that there's an edge case in there that gets something wrong based on some oddity about the stack frame + instruction pointer state.
But it could totally be a bug in the pthread code too that just happens to fail here, or in the kernel for that matter.  But my intuition points at the arch code.

authors: andyross stephanosio


text:
tests: net: lib: lwm2m: content_plain_text: net.lwm2m.content_plain_text fails

Describe the bug
The test net.lwm2m.content_plain_text fails.
Observed for nrf52840dk_nrf52840.
To Reproduce
Steps to reproduce the behavior:

have nrf52840dk_nrf52840 connected
go to your zephyr dir
call ./scripts/twister -T tests/net/lib/lwm2m/content_plain_text -p nrf52840dk_nrf52840 --device-testing --device-serial /dev/ttyACM0 -v --inline-logs
See console output with error

Expected behavior
Valid console output
Impact
Not clear
Logs and console output
*** Booting Zephyr OS build zephyr-v3.4.0-3264-g5ba4288fea6d ***
Running TESTSUITE net_content_plain_text
===================================================================
START - test_get_bool
PASS - test_get_bool in 0.001 seconds
===================================================================
START - test_get_float
PASS - test_get_float in 0.001 seconds
===================================================================
START - test_get_objlnk
PASS - test_get_objlnk in 0.001 seconds
===================================================================
START - test_get_opaque
PASS - test_get_opaque in 0.001 seconds
===================================================================
START - test_get_s32
PASS - test_get_s32 in 0.001 seconds
===================================================================
START - test_get_s64
PASS - test_get_s64 in 0.001 seconds
===================================================================
START - test_get_string
PASS - test_get_string in 0.001 seconds
===================================================================
START - test_put_bool
PASS - test_put_bool in 0.001 seconds
===================================================================
START - test_put_float
Assertion failed at ../../../../../../../../../../zephyr/zephyr/tests/net/lib/lwm2m/content_plain_text/src/main.c:231: net_content_plain_text_test_put_float: (ret not equal to strlen(expected_payload[i]))
Invalid length returned
FAIL - test_put_float in 0.021 seconds
===================================================================
START - test_put_objlnk
PASS - test_put_objlnk in 0.001 seconds
===================================================================
START - test_put_s16
PASS - test_put_s16 in 0.001 seconds
===================================================================
START - test_put_s32
PASS - test_put_s32 in 0.001 seconds
===================================================================
START - test_put_s64
Assertion failed at ../../../../../../../../../../zephyr/zephyr/tests/net/lib/lwm2m/content_plain_text/src/main.c:171: net_content_plain_text_test_put_s64: (ret not equal to strlen(expected_payload[i]))
Invalid length returned
FAIL - test_put_s64 in 0.021 seconds
===================================================================
START - test_put_s8
PASS - test_put_s8 in 0.001 seconds
===================================================================
START - test_put_string
PASS - test_put_string in 0.001 seconds
===================================================================
TESTSUITE net_content_plain_text failed.
Running TESTSUITE net_content_plain_text_nodata
===================================================================
START - test_get_bool_nodata
PASS - test_get_bool_nodata in 0.001 seconds
===================================================================
START - test_get_float_nodata
PASS - test_get_float_nodata in 0.001 seconds
===================================================================
START - test_get_objlnk_nodata
PASS - test_get_objlnk_nodata in 0.001 seconds
===================================================================
START - test_get_opaque_nodata
PASS - test_get_opaque_nodata in 0.001 seconds
===================================================================
START - test_get_s32_nodata
PASS - test_get_s32_nodata in 0.001 seconds
===================================================================
START - test_get_s64_nodata
PASS - test_get_s64_nodata in 0.001 seconds
===================================================================
START - test_get_string_nodata
E: Buffer too small to accommodate string, truncating
PASS - test_get_string_nodata in 0.005 seconds
===================================================================
TESTSUITE net_content_plain_text_nodata succeeded
Running TESTSUITE net_content_plain_text_nomem
===================================================================
START - test_put_bool_nomem
PASS - test_put_bool_nomem in 0.001 seconds
===================================================================
START - test_put_float_nomem
PASS - test_put_float_nomem in 0.001 seconds
===================================================================
START - test_put_objlnk_nomem
PASS - test_put_objlnk_nomem in 0.001 seconds
===================================================================
START - test_put_s16_nomem
PASS - test_put_s16_nomem in 0.001 seconds
===================================================================
START - test_put_s32_nomem
PASS - test_put_s32_nomem in 0.001 seconds
===================================================================
START - test_put_s64_nomem
PASS - test_put_s64_nomem in 0.001 seconds
===================================================================
START - test_put_s8_nomem
PASS - test_put_s8_nomem in 0.001 seconds
===================================================================
START - test_put_string_nomem
PASS - test_put_string_nomem in 0.001 seconds
===================================================================
TESTSUITE net_content_plain_text_nomem succeeded
------ TESTSUITE SUMMARY START ------
SUITE FAIL -  86.67% [net_content_plain_text]: pass = 13, fail = 2, skip = 0, total = 15 duration = 0.055 seconds
- PASS - [net_content_plain_text.test_get_bool] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_float] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_objlnk] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_opaque] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_s32] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_s64] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_get_string] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_put_bool] duration = 0.001 seconds
- FAIL - [net_content_plain_text.test_put_float] duration = 0.021 seconds
- PASS - [net_content_plain_text.test_put_objlnk] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_put_s16] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_put_s32] duration = 0.001 seconds
- FAIL - [net_content_plain_text.test_put_s64] duration = 0.021 seconds
- PASS - [net_content_plain_text.test_put_s8] duration = 0.001 seconds
- PASS - [net_content_plain_text.test_put_string] duration = 0.001 seconds
SUITE PASS - 100.00% [net_content_plain_text_nodata]: pass = 7, fail = 0, skip = 0, total = 7 duration = 0.011 seconds
- PASS - [net_content_plain_text_nodata.test_get_bool_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_float_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_objlnk_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_opaque_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_s32_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_s64_nodata] duration = 0.001 seconds
- PASS - [net_content_plain_text_nodata.test_get_string_nodata] duration = 0.005 seconds
SUITE PASS - 100.00% [net_content_plain_text_nomem]: pass = 8, fail = 0, skip = 0, total = 8 duration = 0.008 seconds
- PASS - [net_content_plain_text_nomem.test_put_bool_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_float_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_objlnk_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_s16_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_s32_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_s64_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_s8_nomem] duration = 0.001 seconds
- PASS - [net_content_plain_text_nomem.test_put_string_nomem] duration = 0.001 seconds
------ TESTSUITE SUMMARY END ------
===================================================================
RunID: d89b0029cff77d77925f7a085676cba5
PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: Ubuntu 20.04.1 LTS
Toolchain Zephyr SDK 0.16.0
Commit SHA or Version used: zephyr-v3.4.0-3264-g5ba4288fea6d

The same errors occurred for nrf5340dk_nrf5340_cpunet.

Fixed in https://github.com/zephyrproject-rtos/zephyr/pull/62431
I know the title says that it fixes floating points, but it also fixes 64bit numbers as well.

It is fixed. Thanks

authors: SeppoTakalo katgiadla