2.5.0 -> 2.5.1 faild load mdx.mjs

Do you still have an issue? I wondering because nobody else reported it 🧐

reproduction
https://github.com/shiyiya/oplayer/pull/70

Vercel deployed logs
[00:14:44.877] Running build in Cleveland, USA (East) – cle1
[00:14:44.939] Cloning github.com/shiyiya/oplayer (Branch: renovate/patch-all-minor-patch, Commit: 336b952)
[00:14:46.674] Cloning completed: 1.734s
[00:14:52.988] Restored build cache
[00:14:53.019] Running "vercel build"
[00:14:53.455] Vercel CLI 29.1.1
[00:14:54.410] Warning: Detected "engines": { "node": ">=16" } in your `package.json` that will automatically upgrade when a new major Node.js Version is released. Learn More: http://vercel.link/node-version
[00:14:54.438] Detected `pnpm-lock.yaml` version 6 generated by pnpm 8...
[00:14:54.438] Running "install" command: `pnpm i`...
[00:14:54.951] Scope: all 11 workspace projects
[00:14:55.094] Lockfile is up to date, resolution step is skipped
[00:14:55.193] Progress: resolved 1, reused 0, downloaded 0, added 0
[00:14:55.302] Packages: +14 -12
[00:14:55.302] ++++++++++++++------------
[00:14:56.194] Progress: resolved 14, reused 0, downloaded 9, added 9
[00:14:57.205] Progress: resolved 14, reused 0, downloaded 14, added 14, done
[00:14:57.347]<EMAIL_ADDRESS>postinstall$ node ./bin/compute-project-graph
[00:14:58.684]<EMAIL_ADDRESS>postinstall: Done
[00:14:59.278]
[00:14:59.279] devDependencies:
[00:14:59.279] - @types/node 18.16.6
[00:14:59.279] + @types/node 18.16.7
[00:14:59.279] - nx 16.1.3
[00:14:59.279] + nx 16.1.4
[00:14:59.279] - terser 5.17.2
[00:14:59.279] + terser 5.17.3
[00:14:59.279]
[00:14:59.281] Done in 4.7s
[00:14:59.800]
[00:14:59.800] ><EMAIL_ADDRESS>build:packs /vercel/path0
[00:14:59.800] > pnpm --filter=@oplayer/* run build
[00:14:59.800]
[00:15:00.322] Scope: 10 of 11 workspace projects
[00:15:00.326] packages/core build$ vite build && tsc --emitDeclarationOnly && vite build --config vite.umd.config.ts
[00:15:00.761] packages/core build: vite v4.3.5 building for production...
[00:15:00.782] packages/core build: transforming...
[00:15:00.943] packages/core build: ✓ 12 modules transformed.
[00:15:01.387] packages/core build: rendering chunks...
[00:15:01.391] packages/core build: computing gzip size...
[00:15:01.407] packages/core build: dist/index.es.js  27.67 kB │ gzip: 7.80 kB
[00:15:01.408] packages/core build: ✓ built in 646ms
[00:15:03.753] packages/core build: vite v4.3.5 building for production...
[00:15:03.775] packages/core build: transforming...
[00:15:03.935] packages/core build: ✓ 11 modules transformed.
[00:15:04.751] packages/core build: rendering chunks...
[00:15:04.756] packages/core build: computing gzip size...
[00:15:04.773] packages/core build: dist/index.min.js  16.07 kB │ gzip: 6.03 kB
[00:15:04.773] packages/core build: ✓ built in 1.02s
[00:15:04.787] packages/core build: Done
[00:15:04.789] packages/danmaku build$ vite build && tsc --emitDeclarationOnly
[00:15:04.789] packages/dash build$ vite build && tsc --emitDeclarationOnly
[00:15:04.789] packages/hls build$ vite build && tsc --emitDeclarationOnly && pnpm run build:extra
[00:15:04.789] packages/mpegts build$ vite build && tsc --emitDeclarationOnly
[00:15:05.487] packages/danmaku build: vite v4.3.5 building for production...
[00:15:05.525] packages/hls build: vite v4.3.5 building for production...
[00:15:05.540] packages/danmaku build: transforming...
[00:15:05.544] packages/dash build: vite v4.3.5 building for production...
[00:15:05.571] packages/hls build: transforming...
[00:15:05.598] packages/dash build: transforming...
[00:15:05.669] packages/mpegts build: vite v4.3.5 building for production...
[00:15:05.689] packages/hls build: ✓ 1 modules transformed.
[00:15:05.693] packages/dash build: ✓ 1 modules transformed.
[00:15:05.708] packages/mpegts build: transforming...
[00:15:05.760] packages/mpegts build: ✓ 1 modules transformed.
[00:15:05.882] packages/danmaku build: ✓ 7 modules transformed.
[00:15:06.057] packages/mpegts build: rendering chunks...
[00:15:06.061] packages/mpegts build: computing gzip size...
[00:15:06.136] packages/mpegts build: dist/index.es.js  2.34 kB │ gzip: 0.92 kB
[00:15:06.137] packages/dash build: rendering chunks...
[00:15:06.152] packages/dash build: computing gzip size...
[00:15:06.244] packages/hls build: rendering chunks...
[00:15:06.256] packages/hls build: computing gzip size...
[00:15:06.262] packages/dash build: dist/index.es.js  7.64 kB │ gzip: 2.08 kB
[00:15:06.303] packages/hls build: dist/index.es.js  7.52 kB │ gzip: 2.14 kB
[00:15:06.704] packages/mpegts build: dist/index.min.js  1.43 kB │ gzip: 0.75 kB
[00:15:06.705] packages/mpegts build: ✓ built in 1.03s
[00:15:06.923] packages/dash build: dist/index.min.js  4.14 kB │ gzip: 1.67 kB
[00:15:06.923] packages/dash build: ✓ built in 1.37s
[00:15:07.051] packages/danmaku build: rendering chunks...
[00:15:07.084] packages/hls build: dist/index.min.js  3.89 kB │ gzip: 1.70 kB
[00:15:07.085] packages/hls build: ✓ built in 1.56s
[00:15:07.094] packages/danmaku build: computing gzip size...
[00:15:07.133] packages/danmaku build: dist/index.es.js  40.03 kB │ gzip: 10.72 kB
[00:15:08.896] packages/danmaku build: dist/index.min.js  24.42 kB │ gzip: 8.61 kB
[00:15:08.896] packages/danmaku build: ✓ built in 3.39s
[00:15:09.821] packages/mpegts build: Done
[00:15:09.822] packages/react build$ vite build && tsc --emitDeclarationOnly
[00:15:10.598] packages/dash build: Done
[00:15:10.602] packages/torrent build$ vite build && tsc --emitDeclarationOnly
[00:15:10.919] packages/react build: vite v4.3.5 building for production...
[00:15:10.960] packages/react build: transforming...
[00:15:11.026] packages/react build: ✓ 1 modules transformed.
[00:15:11.327] packages/hls build: ><EMAIL_ADDRESS>build:extra /vercel/path0/packages/hls
[00:15:11.327] packages/hls build: > vite build --config vite.all.config.ts
[00:15:11.376] packages/react build: rendering chunks...
[00:15:11.382] packages/react build: computing gzip size...
[00:15:11.413] packages/react build: dist/index.es.js  4.00 kB │ gzip: 1.29 kB
[00:15:11.415] packages/react build: Entry module "src/index.tsx" is using named and default exports together. Consumers of your bundle will have to use `oplayer_react.default` to access the default export, which may not be what you want. Use `output.exports: "named"` to disable this warning.
[00:15:11.419] packages/react build: No name was provided for external module "react/jsx-runtime" in "output.globals" – guessing "jsxRuntime".
[00:15:11.505] packages/torrent build: vite v4.3.5 building for production...
[00:15:11.564] packages/torrent build: transforming...
[00:15:11.648] packages/torrent build: ✓ 1 modules transformed.
[00:15:11.873] packages/react build: dist/index.min.js  2.38 kB │ gzip: 1.12 kB
[00:15:11.874] packages/react build: ✓ built in 963ms
[00:15:11.943] packages/torrent build: rendering chunks...
[00:15:11.947] packages/torrent build: computing gzip size...
[00:15:11.973] packages/torrent build: dist/index.es.js  1.71 kB │ gzip: 0.68 kB
[00:15:12.379] packages/hls build: vite v4.3.5 building for production...
[00:15:12.466] packages/hls build: transforming...
[00:15:12.548] packages/torrent build: dist/index.min.js  1.21 kB │ gzip: 0.64 kB
[00:15:12.549] packages/torrent build: ✓ built in 1.04s
[00:15:13.443] packages/danmaku build: Done
[00:15:13.446] packages/ui build$ vite build && tsc --emitDeclarationOnly && pnpm run build:extra
[00:15:14.598] packages/ui build: vite v4.3.5 building for production...
[00:15:14.661] packages/ui build: transforming...
[00:15:15.595] packages/ui build: ✓ 51 modules transformed.
[00:15:15.663] packages/react build: Done
[00:15:15.762] packages/torrent build: Done
[00:15:15.900] packages/hls build: ✓ 4 modules transformed.
[00:15:16.661] packages/ui build: rendering chunks...
[00:15:16.665] packages/ui build: computing gzip size...
[00:15:16.685] packages/ui build: dist/index.es.js  91.73 kB │ gzip: 23.03 kB
[00:15:18.127] packages/ui build: dist/index.min.js  58.92 kB │ gzip: 18.21 kB
[00:15:18.127] packages/ui build: ✓ built in 3.52s
[00:15:19.551] packages/hls build: [BABEL] Note: The code generator has deoptimised the styling of undefined as it exceeds the max of 500KB.
[00:15:21.679] packages/ui build: ><EMAIL_ADDRESS>build:extra /vercel/path0/packages/ui
[00:15:21.679] packages/ui build: > vite build --config vite.core.config.ts
[00:15:22.310] packages/ui build: vite v4.3.5 building for production...
[00:15:22.348] packages/ui build: transforming...
[00:15:22.939] packages/ui build: ✓ 53 modules transformed.
[00:15:25.556] packages/ui build: rendering chunks...
[00:15:25.560] packages/ui build: computing gzip size...
[00:15:25.586] packages/ui build: ../core/dist/index.ui.js  74.08 kB │ gzip: 23.56 kB
[00:15:25.587] packages/ui build: ✓ built in 3.27s
[00:15:25.624] packages/ui build: Done
[00:15:25.705] packages/hls build: rendering chunks...
[00:15:25.712] packages/hls build: computing gzip size...
[00:15:25.741] packages/hls build: dist/index.hls.js  376.86 kB │ gzip: 111.77 kB
[00:15:25.742] packages/hls build: ✓ built in 13.36s
[00:15:25.784] packages/hls build: Done
[00:15:25.785] packages/plugins build$ node build-plugins.js && tsc --emitDeclarationOnly
[00:15:26.072] packages/plugins build: 👾 Start built index ···
[00:15:26.073] packages/plugins build: 👾 Start built index ···
[00:15:26.084] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.085] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.118] packages/plugins build: transforming...
[00:15:26.130] packages/plugins build: transforming...
[00:15:26.269] packages/plugins build: ✓ 7 modules transformed.
[00:15:26.303] packages/plugins build: ✓ 7 modules transformed.
[00:15:26.308] packages/plugins build: rendering chunks...
[00:15:26.313] packages/plugins build: rendering chunks...
[00:15:26.334] packages/plugins build: computing gzip size...
[00:15:26.335] packages/plugins build: computing gzip size...
[00:15:26.353] packages/plugins build: dist/index.es.js  17.35 kB │ gzip: 6.12 kB
[00:15:26.353] packages/plugins build: ✓ built in 266ms
[00:15:26.353] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 283ms!
[00:15:26.354] packages/plugins build: dist/index.es.js  17.35 kB │ gzip: 6.12 kB
[00:15:26.378] packages/plugins build: dist/index.min.js  14.20 kB │ gzip: 5.71 kB
[00:15:26.379] packages/plugins build: ✓ built in 292ms
[00:15:26.379] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 305ms!
[00:15:26.379] packages/plugins build: 👾 Start built vttThumbnails ···
[00:15:26.381] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.388] packages/plugins build: transforming...
[00:15:26.405] packages/plugins build: ✓ 1 modules transformed.
[00:15:26.410] packages/plugins build: rendering chunks...
[00:15:26.417] packages/plugins build: computing gzip size...
[00:15:26.419] packages/plugins build: dist/vttThumbnails.es.js  5.85 kB │ gzip: 2.32 kB
[00:15:26.436] packages/plugins build: dist/vttThumbnails.min.js  4.95 kB │ gzip: 2.21 kB
[00:15:26.436] packages/plugins build: ✓ built in 55ms
[00:15:26.437] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 58ms!
[00:15:26.437] packages/plugins build: 👾 Start built playlist ···
[00:15:26.438] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.444] packages/plugins build: transforming...
[00:15:26.444] packages/plugins build: ✓ 1 modules transformed.
[00:15:26.449] packages/plugins build: rendering chunks...
[00:15:26.457] packages/plugins build: computing gzip size...
[00:15:26.458] packages/plugins build: dist/playlist.es.js  2.06 kB │ gzip: 0.87 kB
[00:15:26.468] packages/plugins build: dist/playlist.min.js  2.25 kB │ gzip: 0.95 kB
[00:15:26.470] packages/plugins build: ✓ built in 29ms
[00:15:26.470] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 32ms!
[00:15:26.470] packages/plugins build: 👾 Start built hello ···
[00:15:26.471] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.475] packages/plugins build: transforming...
[00:15:26.478] packages/plugins build: ✓ 1 modules transformed.
[00:15:26.480] packages/plugins build: rendering chunks...
[00:15:26.488] packages/plugins build: computing gzip size...
[00:15:26.489] packages/plugins build: dist/hello.es.js  2.37 kB │ gzip: 1.01 kB
[00:15:26.502] packages/plugins build: dist/hello.min.js  2.49 kB │ gzip: 1.08 kB
[00:15:26.502] packages/plugins build: ✓ built in 30ms
[00:15:26.503] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 34ms!
[00:15:26.503] packages/plugins build: 👾 Start built chromecast ···
[00:15:26.504] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.508] packages/plugins build: transforming...
[00:15:26.515] packages/plugins build: ✓ 1 modules transformed.
[00:15:26.518] packages/plugins build: rendering chunks...
[00:15:26.548] packages/plugins build: computing gzip size...
[00:15:26.549] packages/plugins build: dist/chromecast.es.js  4.67 kB │ gzip: 1.96 kB
[00:15:26.572] packages/plugins build: dist/chromecast.min.js  4.07 kB │ gzip: 1.91 kB
[00:15:26.573] packages/plugins build: ✓ built in 67ms
[00:15:26.577] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 70ms!
[00:15:26.577] packages/plugins build: 👾 Start built ad ···
[00:15:26.578] packages/plugins build: vite v4.3.5 building for production...
[00:15:26.582] packages/plugins build: transforming...
[00:15:26.590] packages/plugins build: ✓ 1 modules transformed.
[00:15:26.601] packages/plugins build: rendering chunks...
[00:15:26.603] packages/plugins build: computing gzip size...
[00:15:26.604] packages/plugins build: dist/ad.es.js  5.75 kB │ gzip: 2.33 kB
[00:15:26.616] packages/plugins build: dist/ad.min.js  5.20 kB │ gzip: 2.28 kB
[00:15:26.616] packages/plugins build: ✓ built in 37ms
[00:15:26.617] packages/plugins build: ✨ Built<EMAIL_ADDRESS>- 43ms!
[00:15:26.617] packages/plugins build: ✨ Finished building all plugins!
[00:15:28.320] packages/plugins build: Done
[00:15:28.321] packages/docs build$ next build
[00:15:28.802] packages/docs build: Attention: Next.js now collects completely anonymous telemetry regarding usage.
[00:15:28.802] packages/docs build: This information is used to shape Next.js' roadmap and prioritize features.
[00:15:28.802] packages/docs build: You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL:
[00:15:28.802] packages/docs build: https://nextjs.org/telemetry
[00:15:28.897] packages/docs build: - info Linting and checking validity of types...
[00:15:31.028] packages/docs build: - info Creating an optimized production build...
[00:15:32.983] packages/docs build: [nextra] Found "_app.tsx" file, refactor it to "_app.mdx" for better performance.
[00:15:33.235] packages/docs build: [nextra] The repository is shallow cloned, so the latest modified time will not be presented. Set the VERCEL_DEEP_CLONE=true environment variable to enable deep cloning.
[00:15:43.564] packages/docs build: Failed to compile.
[00:15:43.564] packages/docs build: ../danmaku/README.md
[00:15:43.564] packages/docs build: Module not found: Can't resolve '/vercel/path0/node_modules/.pnpm/nextra@2.5.1_next@13.4.1_react-dom<EMAIL_ADDRESS>[00:15:43.565] packages/docs build: https://nextjs.org/docs/messages/module-not-found
[00:15:43.565] packages/docs build: Import trace for requested module:
[00:15:43.565] packages/docs build: ./src/pages/danmaku.mdx
[00:15:43.565] packages/docs build: ../dash/README.md
[00:15:43.567] packages/docs build: Module not found: Can't resolve '/vercel/path0/node_modules/.pnpm/nextra@2.5.1_next@13.4.1_react-dom<EMAIL_ADDRESS>[00:15:43.567] packages/docs build: https://nextjs.org/docs/messages/module-not-found
[00:15:43.567] packages/docs build: Import trace for requested module:
[00:15:43.567] packages/docs build: ./src/pages/dash.mdx
[00:15:43.567] packages/docs build: ../hls/README.md
[00:15:43.568] packages/docs build: Module not found: Can't resolve '/vercel/path0/node_modules/.pnpm/nextra@2.5.1_next@13.4.1_react-dom<EMAIL_ADDRESS>[00:15:43.568] packages/docs build: https://nextjs.org/docs/messages/module-not-found
[00:15:43.568] packages/docs build: Import trace for requested module:
[00:15:43.568] packages/docs build: ./src/pages/hls.mdx
[00:15:43.568] packages/docs build: ../mpegts/README.md
[00:15:43.568] packages/docs build: Module not found: Can't resolve '/vercel/path0/node_modules/.pnpm/nextra@2.5.1_next@13.4.1_react-dom<EMAIL_ADDRESS>[00:15:43.568] packages/docs build: https://nextjs.org/docs/messages/module-not-found
[00:15:43.569] packages/docs build: Import trace for requested module:
[00:15:43.569] packages/docs build: ./src/pages/mpegts.mdx
[00:15:43.569] packages/docs build: ../react/README.md
[00:15:43.569] packages/docs build: Module not found: Can't resolve '/vercel/path0/node_modules/.pnpm/nextra@2.5.1_next@13.4.1_react-dom<EMAIL_ADDRESS>[00:15:43.569] packages/docs build: https://nextjs.org/docs/messages/module-not-found
[00:15:43.569] packages/docs build: Import trace for requested module:
[00:15:43.569] packages/docs build: ./src/pages/react.mdx
[00:15:43.570] packages/docs build: > Build failed because of webpack errors
[00:15:43.599] packages/docs build: Failed
[00:15:43.601] undefined
[00:15:43.601] /vercel/path0/packages/docs:
[00:15:43.601]  ERR_PNPM_RECURSIVE_RUN_FIRST_FAIL  @oplayer/docs@ build: `next build`
[00:15:43.601] Exit status 1
[00:15:43.616]  ELIFECYCLE  Command failed with exit code 1.
[00:15:43.645] Error: Command "pnpm run build:packs" exited with 1
[00:15:44.390] Deployment completed
[00:15:44.013] BUILD_UTILS_SPAWN_1: Command "pnpm run build:packs" exited with 1


make isCheckout a public property for knowing checkout state

right now its ._checkout but it would be useful as a public api. I propose .isCheckout

fixed in 2.3.0


Can't log in

Subject: Can't log in
Description:
The login button does not work
Results:
Backend version: develop-7c33e18d
Frontend version:
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/102.0.5005.99 Safari/537.36
Page: https://couchers.org/login
User:

not enough info or can't reproduce


Verification and utility scripts for new case geo dataset

Added new scripts to check the case geo dataset, lots of housekeeping, updated to use renv, created more utility functions to describe utilty, added a census county subset.

Its ready for Merge Brian


auto captcha not working

using 2CAPTCHA but not working.
wants to enter captcha.

probably fixed 2captcha/rucaptcha... wait for commits and build.
for now making a final touch...


Merge version 0.10.0 of the showcase

Given we're using your fork I'll assign this to you! :D

Is this now done by accepting James' PR?

James is working on making showcase compatible with our project.


fix retry policy

Motivation
Fixes #211
Improve overall default retry policy. It only worked for responses from MAPI, but it did not take into account that an exception can be thrown.
Checklist

[ ] Code follows coding conventions held in this repo
[ ] Automated tests have been added
[ ] Tests are passing
[ ] Docs have been updated (if applicable)
[ ] Temporary settings (e.g. variables used during development and testing) have been reverted to defaults

How to test
Unit tests added.

Codecov Report

Merging #213 (6daea80) into master (76b66e4) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #213      +/-   ##
==========================================
- Coverage   81.06%   80.99%   -0.07%
==========================================
  Files         231      231
  Lines        2640     2631       -9
  Branches      297      296       -1
==========================================
- Hits         2140     2131       -9
  Misses        386      386
  Partials      114      114

Impacted Files
Coverage Δ

...nt.Ai.Management/Exceptions/ManagementException.cs
100.00% <100.00%> (ø)

...agement/Modules/HttpClient/ManagementHttpClient.cs
77.55% <100.00%> (-0.45%)
:arrow_down:

...esiliencePolicy/DefaultResiliencePolicyProvider.cs
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

OK let's try to retry 4XX and 5XX Status codes, but

our Kontent Errors containing specific info would don't retry: https://kontent.ai/learn/reference/openapi/delivery-api/#section/Resolving-errors
If 429 use retry after the header

Once ready add
=> add to https://kontent-ai.github.io/Guidelines-for-SDK-developers information
=> submit issue to core-js-sdk


fix graphql

Refactor graphql usage

This PR given a good idea for using manual GraphQL schema. I will test this. Thx!


Regex::split() crashes

AFL found the following crash in regex-0.1.71 using rustc-1.11.0-dev 2016-06-13
regex::Regex::new("a$").unwrap().split("a").last();

...panicked at 'begin <= end (1 <= 0) when slicing `a`...

I think this is caused by the same underlying issue in #255.


Migrate tasks from Tasks/Comon/utility-common and get rid of it

Task name: NuGetToolInstallerV0, NuGetToolInstallerV1, NuGetV0, TwineAuthenticateV0
Description: The PR replace Tasks/Common/utility-common package with azure-pipelines-tasks-utility-common for tasks
NuGetToolInstallerV0, NuGetToolInstallerV1, NuGetV0, TwineAuthenticateV0 and delete the folder since it is not used anymore.
All tasks were e2e tests by me.
Documentation changes required: N
Added unit tests: N
Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

will be removed in the PR from task owners: https://github.com/microsoft/azure-pipelines-tasks/pull/17729#pullrequestreview-1292639291


[ISSUE #1948] set file modified time

What is the purpose of the change
Invoke File.setLastModified when do flush
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

#1948

Coverage increased (+0.01%) to 50.929% when pulling 8fe98fcff1cb53baadb468655f9e66d07a9cbcb2 on rushsky518:setLastModified into 1706cecff0993efdb00a079068f972d2e9a3699f on apache:develop.

Codecov Report

Merging #1949 into develop will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@              Coverage Diff              @@
##             develop    #1949      +/-   ##
=============================================
- Coverage      45.12%   45.07%   -0.05%
  Complexity      4193     4193
=============================================
  Files            544      544
  Lines          35728    35730       +2
  Branches        4744     4745       +1
=============================================
- Hits           16121    16105      -16
- Misses         17562    17581      +19
+ Partials        2045     2044       -1

Impacted Files
Coverage Δ
Complexity Δ

...ava/org/apache/rocketmq/store/MappedFileQueue.java
62.61% <100.00%> (+0.24%)
76.00 <0.00> (+1.00)

...ain/java/org/apache/rocketmq/test/util/MQWait.java
43.24% <0.00%> (-10.82%)
3.00% <0.00%> (-1.00%)

...tmq/logappender/log4j2/RocketmqLog4j2Appender.java
36.66% <0.00%> (-8.34%)
4.00% <0.00%> (ø%)

...pache/rocketmq/test/listener/AbstractListener.java
66.66% <0.00%> (-7.41%)
9.00% <0.00%> (-1.00%)

...ketmq/client/impl/consumer/PullMessageService.java
71.11% <0.00%> (-4.45%)
8.00% <0.00%> (-1.00%)

...in/java/org/apache/rocketmq/test/util/MQAdmin.java
40.00% <0.00%> (-4.45%)
7.00% <0.00%> (-1.00%)

...nt/impl/consumer/ConsumeMessageOrderlyService.java
38.98% <0.00%> (-3.62%)
16.00% <0.00%> (ø%)

...org/apache/rocketmq/common/stats/StatsItemSet.java
47.52% <0.00%> (-1.99%)
12.00% <0.00%> (-1.00%)

...ava/org/apache/rocketmq/filter/util/BitsArray.java
58.11% <0.00%> (-1.71%)
29.00% <0.00%> (-1.00%)

...pl/consumer/ConsumeMessageConcurrentlyService.java
42.71% <0.00%> (-0.98%)
10.00% <0.00%> (ø%)

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1706cec...8fe98fc. Read the comment docs.

Is it necessary to modify this value, in addition, frequent changes to this value will affect performance?

@RongtongJin
It is not so necessary, mostly rocketmq is deployed on linux, but it's not elegant on windows(And i am not sure if it is my computer's problem).
last_modified_time value is changed when invoke flush, it may take less effects on performance


The type 'materialDesign:Chip' was not found   in v<IP_ADDRESS>3  installed from nuget

I have been working  with  MaterialDesignThemes with no problems until I tried to use  'Chip' and got the next issue:
The type 'materialDesign:Chip' was not found. Verify that you are not missing an assembly reference and that all referenced assemblies have been built.
Then,  I  check in Object  browser and  the Chip type  does not exists! :(

I have installed  version <IP_ADDRESS>3 from  nuget package manager.
By the way,  I tried to reference the dll  compiled from de source in  github but i can't, I got similiar messages of  missing references. Could you  give instructions to install from source?

Hi, this is coming in version 2.0, so you'll need to use the -pre version of the nuget.

thanks, i will installed. By the way, MaterialDesign is  great  a lot!


Add multi OCI runtime support for ctr

Add ctr command line args --runtime and --runtime-args for multiple
OCI runtime support.
Signed-off-by: Zhang Wei<EMAIL_ADDRESS>

Related: https://github.com/docker/containerd/pull/247
This will be good for trying this new feature and debuging containerd.
@mlaventure @crosbymichael What do you think of this?

Thanks, was planning on doing it later! :)

LGTM.

ping @crosbymichael

LGTM


HLS Manifest fails to load with embedded text tracks

Hi, hope all is well! I've noticed an issue today with my HLS Manifests that have embedded text tracks in them. Before I get into the full issue itself, it's totally possible that this is an issue on Vimeo's end, but when I contacted them they refused any actual issue being present.
I'm currently building a custom Vue Component wrapper around Shaka. I have access to a library of ~13k unique videos, all uploaded at varying qualities and bitrates over the years. The only ones I've had an issue with up to this point are the ones with embedded text tracks.
I haven't jumped into the source yet, I thought I'd submit an issue first at least. It appears as though the code is just hitting a point where it's referencing an undefined property on an object. I'll post the errors in the details below.
Have you read the FAQ and checked for duplicate open issues?
Yes. I see a few different issues for Manifests and VTT, but I didn't see my exact error anywhere.
What version of Shaka Player are you using?
2.5.3
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Did not try yet.
Are you using the demo app or your own custom app?
Both
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Ubuntu 18.04 - Chrome, Firefox
MacOS 10.14.5 - Chrome, Firefox (Safari seems to parse them fine with src="")
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
N/A
What are the manifest and license server URIs?
Heres 3 from the same course, all should have embedded text tracks
https://player.vimeo.com/external/217849817.m3u8?s=6e22ea5dc4f9aa27833f8c34db178545a64a8d17
https://player.vimeo.com/external/217857009.m3u8?s=88eb26853baaac585f0173df677eb2385157073b
https://player.vimeo.com/external/217872983.m3u8?s=0e52091b98b126df7afeb3107567f98444ceea5f
What did you do?
I just loaded the Manifest using the .load() method the same way I have with any other.
What did you expect to happen?
The video to load, and be playable.
What actually happened?
It seems like an error is being thrown and caught at the .load() method. I'll post the details for each browser below:
Chrome
TypeError: Cannot read property 'length' of undefined
    at Pg (text_parser.js:44)
    at oo (vtt_text_parser.js:429)
    at no.push../node_modules/shaka-player/dist/shaka-player.compiled.js.no.parseMedia (vtt_text_parser.js:198)
    at Xd.push../node_modules/shaka-player/dist/shaka-player.compiled.js.Xd.Lc (text_engine.js:173)
    at Gh (hls_parser.js:1894)
    at Ja.b (hls_parser.js:1672)
    at Ma (generator_engine]:795)
    at Na.next (generator_engine]:699)
    at c (execute_async_generator]:48)

Firefox
TypeError: "b.b is undefined"
    Pg text_parser.js:44
    oo vtt_text_parser.js:429
    parseMedia vtt_text_parser.js:198
    Lc text_engine.js:173
    Gh hls_parser.js:1894
    k hls_parser.js:1672
    Ma generator_engine]:795
    next generator_engine]:699
    c execute_async_generator]:48
    run polyfill.js:4399
    notify polyfill.js:4416
    flush polyfill.js:1501

Issue reproduced. I'll look into it. Thanks for the report!

I think I see the problem. The HLS parser is fetching the first 2048 bytes of the text, so that we can find the first cue and figure out the start time of the text content. But we try to parse all of the cues in that data, even though we don't really need to. This means that, if the file is larger than 2048 bytes, the text parser will try to parse half of a cue and hit an exception.
We didn't notice this before because it looks like none of our test content has captions files big enough. Whoops!
I'll make a CL to fix this. Again, thanks for the report.

@theodab - Thanks so much for the extremely swift response! I'm glad the issue looks to be fairly trivial. Feel free to continue using those HLS Manifests for your own internal testing if you need (I don't believe those particular URLs should expire).

@theodab - I noticed today an option in the streaming config called "ignoreTextStreamFailures". Is the intended behavior of this option to bypass/ignore the error in my issue or is it related to something else? I've noticed that if I set it to true I still can't get any playback from those sources.

ignoreTextStreamFailures is a config value for the streaming engine; the failure you are experiencing happens in the HLS parser, before the streaming engine is even made.
I suppose we could make an equivalent configuration for the HLS parser, that would make it pretend the manifest had no captions at all if they failed to load initially? I don't know if that has a lot of demand, though; like, I don't know if there are a lot of content providers who expect for their caption tracks to sometimes be missing. Maybe in an ad insertion context, where you don't trust the content provider as much?

@theodab - Thanks for the clarification! In my particular case I hoping to find a workaround. I also have access to all of the text tracks as VTT files, in theory, if the cues are all set at the correct times I can just attach the text track to the shaka player manually and trigger selection/deselection of the subtitles that way, and they will all be in sync with the currentTime of the MediaElement.
It's a bit of a hack though seeing as Shaka as well as the manifest have all of that functionality caked in by default. I'm just going to sit tight until the underlying issue is addressed. I took a bit of time last night to look into it myself but I fear it might be a bit over my head.
I really appreciate all your help, thanks so much!

I have a CL out for review right now that, based on my manual testing, fixes your problem. It just needs to go through code review before it can be added to the project. So it hopefully won't be too long.

Awesome. Thank you so much for your help!

No problem. If you have any further questions, feel free to ask. We're happy to help.

@theodab - Thanks for addressing this, I've had some time to revisit this project now. I would assume your commit made it into the 2.5.4 release as the error described above no longer appears. However, I'm still getting player crashes on some of my videos with embedded text tracks.
I've done some more digging and I have a bit more info that might be helpful before I contact Vimeo about this I'd like to get your opinion first:
If you load the following manifest into the demo player you'll notice it plays fine and the captions work as expected. Awesome!
https://player.vimeo.com/external/217879744.m3u8?s=95d405d9b1bfdb66c2a3f760f4efcf0def01110b
If you load this manifest into the demo player we get an error:
"UNABLE_TO_EXTRACT_CUE_START_TIME"
https://player.vimeo.com/external/217888285.m3u8?s=31641cf0bf55d7ddd3b94611105c143382a703dd
If we actually download the manifest file we can see that the working video is pointing to a nice clean direct URL:
https://skyfire.vimeocdn.com/1565382203-0x43aaee639e8955649c19c907fb49f64a0fcb7a41/217879744/subtitles/4987498/playlist.m3u8?d=963.879563
If we download the manifest for the video that's not working, we notice the text track playlist has some sort of signed URL with an expiry and a secret:
https://86skyfiregce-vimeo.akamaized.net/exp=1565382187~acl=%2F217888285%2F*~hmac=58054ca5433562c6e12b256529ab6a15b57a5016a8e1a6dd6c19f2888043663c/217888285/subtitles/4987499/playlist.m3u8?d=650.107771
While monitoring the network tab as the requests are going through, there's nothing to make me believe the requests are being blocked, I can still see the direct request to the VTT file for both videos, they both return a 200 response, it's just the ones with the weird signed URLs that fail.
It's also worth noting that the VTT files themselves are very similar in size and identical in formatting.
My question is: Do I need to pass some sort of DRM config in this case to handle these text tracks? Or is this something I should just get in contact with Vimeo about?

I've never seen encrypted text tracks, and text doesn't get processed through the browser's CDM (Content Decryption Module), so it's not a DRM issue.
It looks like a known issue in our HLS implementation, which happens to have a fix in progress.  In short, we are trying to extract start timestamps from segments, and this doesn't work well on text.  We should be able to avoid this, though, with an upcoming optimization.
You can follow #1563 and #1558 for the fix.

That commit did NOT make it into the v2.5.4 release; it was too complicated and risky to make it into a bugfix release.  You'll have to wait until v2.6 for this fix to appear.  The failed asset you listed  above works fine for me on the nightly site (off master).

Wow, I love how fast you guys are to respond. Thank you!
I've gone ahead and followed the two issues you posted above. I'll make sure to contribute where I can. Thanks again, guys!


Update style.css

In general, I need a thorough description of changes especially from new contributors. Right now is a bad time for style changes as we're in the middle of some merges of manually written html.


Foundation laid for global Cripts

This is a beginning, there's more work to do here, looking for contributions:

The Bundles callbacks is untested and may need work.
We should add other non-HTTP txn hooks, such as the SNI hooks
Possibly, we should add the other HTTP-txn hooks as well (such as DNS etc.)
More testing / real code and uses cases.

[approve ci autest]

[approve ci autest]


.NET Core 1.1 tooling on hosted agent

Windows hosted agent 2.109.1 on VisualStudio.com.
Is there a timeline for the latest .NET Core 1.1.0 preview to be installed on the hosted agent in VSTS? Currently only 1.0.0 and 1.0.1 are installed and this forces us to manually install 1.1.0 on every build.

@henkmollema it's on our radar, probably next week? @thechrisjohnson

@TingluoHuang thanks for the update!

This repro is about the agent (which does not carry the tools).  The hosted image does.

@bryanmacfarlane is there a repo for the hosted image?

I think this issue should be reopened, The 1.1 version of dotnet core went RTM a couple of weeks ago. Building and deploying from vsts hosted agent to Azure app services results in no error during the CI  process.
However the application on the app service never start and you get a 502.5 enable to start application error when trying ot access it. (see attachment)
Thanks @MaximRouiller for helping me troubleshooting this.
ErrorPage000030.zip

It is important to note that, publishing through Visual Studio works but publishing through VSTS doesn't.

Where should this issue be reported?

developercommunity.visualstudio.com
However, it's being worked on today and it's known work so not sure it will buy you anything.  Good to know going forward.

It is important to note that, publishing through Visual Studio works but publishing through VSTS doesn't.

It works if you provision your own VM (always the way to control the toolsets).  There's just latency in the convenient hosted pool image getting updated.


Add Kinoplan as adopter

Codecov Report

Merging #1686 (c743d47) into master (ad68e71) will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1686      +/-   ##
==========================================
- Coverage   86.99%   86.91%   -0.09%
==========================================
  Files          59       59
  Lines        2392     2392
  Branches      136      136
==========================================
- Hits         2081     2079       -2
- Misses        311      313       +2

Impacted Files
Coverage Δ

...rc/main/scala/io/circe/numbers/BiggerDecimal.scala
87.13% <0.00%> (-1.17%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ad68e71...c743d47. Read the comment docs.


Reskin | Implement search safe redesign

Wait until https://github.com/decentdao/fractal-interface/pull/1823 is merged before reviewing/merging this one
Addresses #1800. Also removed the search bar from top nav. Other top nav updates will happen in a follow PR on #1802

I really like this implementation. Thanks @DarksightKellar


Electron and serialport on raspberry pi 3, Module version missmatch error

Python: 2.7.9
Serialport: 3.8.6
electron prebuilt: 3.8.6
raspberry 3 linux 4.4.16-v7+
Node: 5.12.0
npm: 3.8.6
I cannot get the app to run without the Module version missmatch error. I followed a bunch of tutorials here, suggesting rebuilding the module, changing node & npm & electron versions, and so far i have managed to change the error from:
"Expected 49, got 46" to  "Expected 49, got 47" to "Expected 49, got 48".
Do you please have any more ideas, or point me in the right direction as i am clueless by now.
I tried clearing the npm cache, rebuilding all modules, rebuilding just serialport, deleting node modules and reinstalling them. Using node-gyp to rebuild the binaries... I think i tried every solution out there.
So far, by logging the line before the line that breaks in the node_modules/bindings/bindings.js have managed to isolate the problem ( i think ) to serialport/dist/Release/serialport.node
Here is the log:

<EMAIL_ADDRESS>start /home/pi/eres-one/app
electron main.js

#MY LOG
/home/pi/eres-one/app/node_modules/serialport/build/serialport.node
/home/pi/eres-one/app/node_modules/serialport/build/Debug/serialport.node
/home/pi/eres-one/app/node_modules/serialport/build/Release/serialport.node
#END MY LOG
App threw an error during load
Error: Module version mismatch. Expected 49, got 47.
at Error (native)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20)
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:167:20)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at bindings (/home/pi/eres-one/app/node_modules/bindings/bindings.js:77:44)
A JavaScript error occurred in the main process
Uncaught Exception:
Error: Module version mismatch. Expected 49, got 47.
at Error (native)
at process.module.(anonymous function) [as dlopen] (ELECTRON_ASAR.js:167:20)
at Object.Module._extensions..node (module.js:568:18)
at Object.module.(anonymous function) [as .node] (ELECTRON_ASAR.js:167:20)
at Module.load (module.js:458:32)
at tryModuleLoad (module.js:417:12)
at Function.Module._load (module.js:409:3)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at bindings (/home/pi/eres-one/app/node_modules/bindings/bindings.js:77:44)
Please help me solve this,
Thanks in advance

And the 46, 47, 48 versions i managed to get correlate to the node versions i installed.
46 for node < 4, 47 for node 5.* and 48 for node 6.*
The problem is that it is still 48 for the latest node arm build, and as far as i can see. te official page states
Version	LTS	Date	V8	npm	NODE_MODULE_VERSION[1]
Node.js v6.3.1		2016-07-21	<IP_ADDRESS>	3.10.3	48
https://nodejs.org/en/download/releases/
P

But i tried many versions of electron-rebuild and electron... none of them worked. Are you telling me it cannot be solved?

Thank you, i will. Is there nothing else i can do? and can you pls, if you have the time :) explain why can't i modify the serialport module somehow to use the same version of node as my electron app? As no other modules i am using are having this problem...
I don't mean to be a drag, i'm just trying to understand this problem... i read this https://nodejs.org/api/addons.html and i understand Electron comes with it's own version of node bundled up, and serialport uses a different node version when it is creating the bindings? Could this be changed?

https://github.com/electron/electron-rebuild/issues/97
I tried everything you see here, still nothing. Is there something i am doing wrong?
What determines the version of the package? can i change something in the c++ code to trick electron into thinking that the serialport package is version 49?

https://github.com/juliangruber/require-rebuild/issues/12
even with require-rebuild it doesnt work,
Please help

Allright! i managed to get it working by running sudo npm rebuild --runtime=electron --target=1.2.5 --disturl=https://atom.io/download/atom-shell --build-from-source
and by bumping my electron version to 1.2.6 :)
https://www.youtube.com/watch?v=U5TqIdff_DQ
Thank you for your help

@styoe thanks so much :)

Hi, is there any chance any of you would be able to take a look at a similar issue but for NodeJS on Ubuntu x64? I would really appreciate it!
The issue is here: #964


Update BUILD.md

modify help message and build example.

please review if you satisfy this modification.


[Projections] throw better errors for parameter values that are incorrect

For example, when one of the union of version options are incorrect, or when passing something that we can't extract versions from. Right now it's hard to attach the error in a useful way for users. An API for decorators to use to report errors would help.

related to: https://github.com/microsoft/cadl/issues/200


Unable to publish NodeJS bot

Customer is trying to publish the NodeJS bot in Composer, however it is not getting deployed but waiting endlessly
We have created a Node Bot in Bot framework composer and unable to deploy /publish to azure, It keeps on deploying continuously.
---
'Accepted for publishing...'
---

---
'Abs settings incomplete, skip linking bot with webapp ...'
---

---
'appPasswordHint incomplete, return ...'
---

---
'Building the bot app...'
---

---
'Build succeeded!'
---

---
'Creating build artifact...'
---

---
'Build artifact ready!'
---

---
'Publishing to Azure ...'
---

---
'Uploading zip file... to NodeBotResource'
---

---
'Waiting for zip upload processing.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Building and Deploying 'bf9904fa-300d-46e9-af15-d41ecad467a8'.'
---

---
'Waiting for zip upload processing. Receiving changes.'
---

---
'Waiting for zip upload processing. '
---

---
'Waiting for zip upload processing. '
---

---
'Waiting for zip upload processing. '
---

---
'Waiting for zip upload processing. '
---

---
'Waiting for zip upload processing. '
---

I'm able to reproduce this issue.
I created a Composer NodeJS bot and tried to publish to Azure with Linux OS for the Azure App Service.
Sharing the steps to reproduce:

Run composer in Debug mode using the following Instructions
Create a NodeJS bot in Composer
Publish the bot to Azure in Linux OS App Service
See the following continuous message in the logs

2023-05-08T16:00:14.647Z composer:bot-project Schemas directory found.
2023-05-08T16:00:14.648Z composer:bot-project Customized SDK schema found
2023-05-08T16:00:14.651Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 43.749 ms - -
2023-05-08T16:00:14.759Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:21.096Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:24.672Z composer:bot-project Schemas directory found.
2023-05-08T16:00:24.678Z composer:bot-project Customized SDK schema found
2023-05-08T16:00:24.680Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 75.579 ms - -
2023-05-08T16:00:25.079Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:29.858Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:34.649Z composer:bot-project Schemas directory found.
2023-05-08T16:00:34.651Z composer:bot-project Customized SDK schema found
2023-05-08T16:00:34.652Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 45.535 ms - -
2023-05-08T16:00:34.833Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:39.869Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:44.645Z composer:bot-project Schemas directory found.
2023-05-08T16:00:44.646Z composer:bot-project Customized SDK schema found
2023-05-08T16:00:44.649Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 44.338 ms - -
2023-05-08T16:00:44.849Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:49.922Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:00:54.636Z composer:bot-project Schemas directory found.
2023-05-08T16:00:54.637Z composer:bot-project Customized SDK schema found
2023-05-08T16:00:54.639Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 35.602 ms - -
2023-05-08T16:00:55.607Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:01:00.512Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:01:04.660Z composer:bot-project Schemas directory found.
2023-05-08T16:01:04.662Z composer:bot-project Customized SDK schema found
2023-05-08T16:01:04.665Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 62.121 ms - -
2023-05-08T16:01:04.911Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:01:09.881Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '
}
2023-05-08T16:01:14.641Z composer:bot-project Schemas directory found.
2023-05-08T16:01:14.643Z composer:bot-project Customized SDK schema found
2023-05-08T16:01:14.646Z composer:bot-project UI Schema found.
GET /api/publish/77926.35034022473/status/Azure/2975a4f8-54a7-4d4a-83d6-228eaeda9414 202 40.734 ms - -
2023-05-08T16:01:16.300Z composer:extensions:azurePublish {
  status: 'DEPLOY_INFO',
  message: 'Waiting for zip upload processing. '

The above reproducible issue steps occur when using Linux OS for the app service.
I tried to switch to Windows OS, and after publishing the bot in Composer, it seems the bot does not respond in Azure WebChat and got Error 500 when I visit the app service default domain.
After publishing to Windows OS App Service:

Hey @ceciliaavila.
We are able to reproduce this issue. Assigning to you for now.
Please let me know if you have any questions.
Thanks!

Hi @ramfattah, we were able to reproduce your error. It happened when we attempted to deploy the bot right after creating the resources in Azure. In the second attempt, the deployment was successful.
As the error is a Gateway Timeout during the zip deploy, we believe the reason is that the web app isn't fully ready and needs more time to 'warm up'.
Please, let us know if you still can't deploy your bot.


0.2.0 release

I was just about to change it, following our weekly meeting this morning. This is now updated. I let you review it


Translation Service Issue

We have generated translation file from AL environment. And we are trying to request caption by using Translation service, But when we upload the file and complete the process, it is showing the status with "Completed with error".  There is no proper information about the error and what it is.
Can any one give suggestion on this.

Translation Service is a separate product not support through this forum and not maintained by the NAV/Business Central team. Please try to reach out to the relevant support channel.


Copy blockchain over LAN failing. Possible due to lack of permissions

I want to copy the blockchain from one working node to a new one. Both are under the same network.
I'm getting this error:

# Starting copy over LAN (around 4-6 hours) ...
sending incremental file list
copy_begin.time
rsync: mkstemp "/mnt/hdd/.bitcoin.rLpXFy" failed: Permission denied (13)

sent 126 bytes  received 112 bytes  158.67 bytes/sec
total size is 11  speedup is 0.05
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1207) [sender=3.1.3]
rm: cannot remove './transferred.rsync': Permission denied
sending incremental file list
rsync: mkdir "/mnt/hdd/bitcoin" failed: Permission denied (13)
rsync error: error in file IO (code 11) at main.c(682) [Receiver=3.1.3]

Seems that this is being caused by permission issues. Can you help fixing this?
Note: The working node (source node) has an HDD 1tb and the new node (target node) has an SSD 1tb, not sure if this can also cause conflicts.
Thank you

ls -l /mnt/hdd/bitcoin
ls -la /mnt/hdd/.bitcoin

The problem is most likely that the remote folder /mnt/hdd/bitcoin does not exist yet and the bitcoin user doesn't have permission to create new folders in /mnt/hdd. This is likely fixed by sudo mkdir /mnt/hdd/bitcoin && sudo chown bitcoin:bitcoin /mnt/hdd/bitcoin on the remote machine.
Alternative:
https://github.com/rootzoll/raspiblitz/blob/fc1d44104bc22d85ebebd7b0d6ee2240722a9edf/home.admin/98repairMenu.sh#L114
Use the root user to log in instead, or use admin with parameter --rsync-path 'sudo rsync'.

I wiped out my sd card and SSD and now I'm not able to reproduce it anymore. I will reopen this issue if it happens again, closing for now...
Thank you all.


Refactor pipelines and config files

Description

Refactor kubecf and reconciler pipeline template to accept explicit configs kubecf.yaml & kubecf-pool-reconciler.yaml files.
Thanks to this, remove unneeded templating options, remove old EKCP documentation, and add
a trigger_publish: true to the config.
Motivation and Context

This way there's no way to mistakenly operate against a pipeline you don't intend to. One always needs to specify the name of the pipeline they are operating, and by copying the config kubecf.yaml to their own my-kubecf.yaml they don't operate against the production pipeline.
How Has This Been Tested?

Tested by:

Deploying my own test copy of the pipeline
Running the script against production kubecf & kubecf-pool-reconciler pipelines, seeing no relevant changes.

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.

It is missing the upgrade task, which is in .concourse/tasks/*. This needs to be templated too with the config kubecf.yaml as a datasource.

trigger_publish will still not work but we can fix it in a separate PR
With the pool resource now removed, do we need the reconciler pipeline around? If yes can we make it clear what it should be used for?

1. `trigger_publish` will still not work but we can fix it in a separate PR

trigger_publish option should work, but it's just minimal. My thought process was that it is needed for pipeline copies coming from SUSE contributors and running on concourse.suse.dev, as those would have the creds to succeed in publishing.

2. With the pool resource now removed, do we need the reconciler pipeline around? If yes can we make it clear what it should be used for?

We don't need it around, but I felt it doesn't hurt to have it for a bit. It's undocumented and out of the way.

True "trigger_publish" will work. I though it was the flag that disables all push actions (e.g. update GitHub statuses). That's the one that needs fixing (maybe in a different PR).
Having a non-documented pipeline around is what worries me. It will only confuse people. Especially when it's the same script that deploys that one and the kubecf one. Anyway, we can wait a bit until we decide if we stick to gke or not.


[Improvement] set_aside multiple items

I wanted to recreate the crafting process from this video with kalandralang but it seems impossible without setting aside multiple items because it wants to recombine 4 items into 2 and then into 1 one
TL;DR
Using recombinators to combine items A, B, C and D into items AB and CD first, then into ABCD is impossible with only one set_aside slot
Proposal
Implement set_aside as a stack. set_aside pushes the current item on top of the stack. Actions like recombine consume the item on top of the stack.
This still has limitations when creating more complex recipes but allows the use case described above
Alternative
Implement set_aside as a map/dictionary with string keys, so you can name items (set_aside item_name) and consume arbitrary items by referencing their name (recombine item_name, swap item_name_to_receive item_name_to_set_aside)
I reckon this is far more complex to implement but may be considered if recombinators will stay as a core mechanic
Examples (pseudo code)
Stack
Currently set_aside in line 11 would overwrite the item previously set aside in line 7
 1: .base_ab:
 2:   buy "Imbued Wand" with prefix A
 3:   set_aside
 4:   buy "Prophecy Wand" with prefix B
 5:   recombine
 6:   if not prefix A+B goto .base_ab
 7:   set_aside
 8:
 9: .base_ac:
10:   buy "Imbued Wand" with prefix A
11:   set_aside # pushes on set_aside stack
12:   buy "Tornado Wand" with prefix C
13:   recombine # consumes item from line 11
                # item from line 7 is now on top of set_aside stack
14:   if not prefix A+C goto .base_ac
15:
16: if base type "Imbued Wand" goto .bc
17: swap # sets item from line 7 as current item
          # pushes current item from line 13 on top of set_aside stack
18: if base type "Imbued Wand" goto .bc
19: goto .base_ab # none of both bases is an "Imbued Wand"; restart
20:
21: .bc:
22:   recombine # consumes item from line 13 (swapped in line 17)
23:   if not (base type "Imbued Wand" and prefix A+B+C) goto .base_ab
24:
25: show # "Imbued Wand" with prefixes A, B and C

Map
 1: .base_ab:
 2:   buy "Imbued Wand" with prefix A
 3:   set_aside item_a
 4:   buy "Prophecy Wand" with prefix B
 5:   recombine item_a # consumes item_a from line 3
 6:   if not prefix A+B goto .base_ab
 7:   set_aside item_ab
 8:
 9: .base_ac:
10:   buy "Imbued Wand" with prefix A
11:   set_aside item_a
12:   buy "Tornado Wand" with prefix C
13:   recombine item_a # consumes item_a from line 11
14:   if not prefix A+C goto .base_ac
15:
16: if base type "Imbued Wand" goto .bc
17: swap item_ab item_ac # sets aside the current item as item_ac
                         # retrieves item_ab from line 7 as the current item
18: if base type "Imbued Wand" goto .bc
19: goto .base_ab
20:
21: .bc:
22:   recombine item_ac # consumes item_ac from line 17
23:   if not (base type "Imbued Wand" and prefix A+B+C) goto .base_ab
24:
25: show # "Imbued Wand" with prefixes A, Band C

See my answer in https://github.com/doomeer/kalandralang/pull/29 — short version: yes! It's now in master.
I agree that we may eventually want to name set-aside items. We'll see once we have an example use case where it would really help.

See my answer in #29 — short version: yes! It's now in master.
I agree that we may eventually want to name set-aside items. We'll see once we have an example use case where it would really help.

I think i came up with a use case for named set-aside items:
When recombining items but you don't get your desired outcome it can often be used as one of the two bases for another try. With named set-aside items I could imagine a predicate whether a set-aside item name exists (e.g. is_set_aside <name>) and an instruction to receive a named set-aside item as the current item (e.g. get_aside <name>) for the following crafting process:
.start:
if is_set_aside "base a" then goto .finished_a
# craft base a
set_aside "base a"
.finished_a:

if is_set_aside "base b" then goto .finished_b
# craft base b
set_aside "base b"
.finished_b:

get_aside "base a"
recombine "base b"
if <desired outcome> then goto .success
if <good enough for base a> then {
  set_aside "base a"
} else {
  if <good enough for base b> then {
    set_aside "base b"
  }
}
goto .start

.success:
# continue crafting

That's a very good point.
In fact I had an idea a few weeks ago of having "pools" of items. This is basically the same except that there can be more than one item in a pool. The idea is that when recombining, you can often end up with multiples of the same item. For instance let's say you want to make a ring with T1 int and T1 dex. You may spam alterations trying to get each of the T1 attribute mods. But while doing that you will probably see e.g. T1 dex thrice before seeing T1 int. You could toss the additional T1 dex rings away, but that would be suboptimal because if recombination fails you may very well have a use for them later.
If we also had functions, this could look like this:
function categorize {
  if tier "Dexterity" <= 1 then {
    if tier "Intelligence" <= 1 then push "both" else push "dex"
  }
  if tier "Intelligence" <= 1 then push "int" else
    push "base" # note: if item is rare we actually would have to scour and transmute here
}

function get_attribute $pool {
  until not is_empty $pool do {
    if is_empty "base" then buy magic "some ring base" else pop "base"
    alt
    categorize
  }
  pop $pool
}

until not is_empty "both" do {
  get_attribute "int"
  set_aside
  get_attribute "dex"
  recombine
  categorize
}

pop "both"

It's a lot of boilerplate but it can be interesting. Also one could maybe tell Kalandralang to keep pools when repeating recipes to more accurately reflect average cost.


defaultServiceOfferingConfig feature does not work

It should describe default offering for specified zone. And if it is a custom SO, also default values. See the config guide.
Check the case when offering O1 set as default in zone Z1 and offering availability is on and for the zone Z1 offering O1 not included in the list. Check that system works correctly. The offering should not be listed.
Connected feature ID: config_so_default

Please add validation and type for this parameter.

@chewlite 2.1 - it was fixed (check in a pull request, if you want)

@chewlite @ershovaelena
Check it.
Config information about this property will be:
The user is able to predefine custom/fixed service offering which will be selected as default for each zone in VM creation. For custom service offerings there can be predefined offering parameters: number of CPUs, a speed of CPU and/or memory. For example,

@HeyRoach Okay, please add it to Config guide (I changed it a little bit, copy this text).

@HeyRoach - default service offering is set in a vm-creation.effect on 205.
change it

We decided to split this setting.

Now we should have defaultComputeOffering that only will be describe preselected offering in VM creation from for specific zones.
For example:

"defaultComputeOffering": [
    {
      "zoneId": "415db026-1135-496e-9383-0c820a75694e",
      "offeringId": "f216bd08-947a-4022-8271-c29e9acfffb9"
    }
  ]

Rename customComputeOfferingRestrictions into customComputeOfferingParameters and add default property to parameters.
For example:

"customComputeOfferingParameters": [
    {
      "offeringId": "73cdef05-d01f-49ad-8ecb-4f2ffd7d8e26",
      "cpunumber": {
        "min": 2,
        "max": 8,
        "default": 4
      },
      "cpuspeed": {
        "min": 1000,
        "max": 3000,
        "default": 1500
      },
      "memory": {
        "min": 512,
        "max": 8192,
        "default": 512
      }
    }
  ]

Regression:
config_so_default
config_custom_compute_offerings_parameters

Tested on 1278 in a simulator


[Accessibility] Cherry-pick documentation to v0

added the documentation for accessibility.

documentation for end users done.

technical documentation started.

technical and testing documentation draft is done.

First run of edits.

Mainly changed some sentences, the format and merge end user documentation in one page.

A few more edits.

Missing words, spelling.

Moved the accessibility pictures to another folder.

@veler,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

This needs to go to master to be publicly visible. @veler


fix: GameWidget will not listen to keyboard events without the KeyboardEvents mixin

Description
Currently, the GameWidget uses a Focus widget always, even if the game is unable to receive keyboard events.
This PR makes it so that the Focus node is only used when the game has KeyboardEvents mixin that is used for listening to keyboard events. This is similar to how we use gesture detectors and mouse detectors.
Another advantage here is that now Focus is in parallel with the overlay widgets, which means that it won't interfere with the overlay's text input attempts.
Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[x] I have updated/added tests for ALL new/updated/fixed functionality.
[-] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[-] I have updated/added relevant examples in examples.

Breaking Change

[-] Yes, this is a breaking change.
[x] No, this is not a breaking change (shouldn't be?).

Related Issues
Closes #1710

@renancaraujo
This PR specifically address those Games which do not implement the KeyboardEvents interface/mixin, and do not wish to interact with the keyboard.
I understand the scenario that you're describing, where unhandled key presses cause annoying beeping sounds. But if the user faces this problem, they have an easy solution: add the KeyboardEvents mixin to the game (whose default behavior is to mark all keys as "handled").
If, on the other hand, the user doesn't want to interfere with the key events, then they have no easy solution right now. They could, again, add the KeyboardEvents mixin and mark all keys as "ignored", but this is feels wrong and is very non-intuitive: if you don't want to handle the key events, why would you even think about adding a mixin dedicated to handling key events?


Infinite loop

Hi
when I try to run the SigProfileextractor, it goes into an infinite loop. Below is the screenshot of my error

Basically it goes into an infinite loop.. I am not sure why this is happening. Can someone please help?

Hi @SukanyaPanja,
It appears that you have run into an issue when running SigProfilerExtractor. Please take a look at #88 to see if it helps resolve your issue.
Thanks!


SourceKitLSP crash often

Hi, after setting up the package, my SourceKitLSP crash very often with error (from LspLog):
/AppleInternal/Library/BuildRoots/860631e9-c1c5-11ee-98ee-b6ef2fd8d87b/Library/Caches/com.apple.xbs/Sources/SourceKitLSP/dependencies/swift-syntax/Sources/SwiftParser/Lexer/Cursor.swift:620: Fatal error\n

Then, I need quit and restart nvim. Here is my lspconfig:
lspconfig.sourcekit.setup({
  cmd = {
    "xcrun",
    "--toolchain",
    "swift",
    "sourcekit-lsp",
  },
  filetypes = { "swift" },
  root_dir = function(filename, _)
    local util = require("lspconfig.util")
    return util.root_pattern("buildServer.json")(filename)
        or util.root_pattern("*.xcodeproj", "*.xcworkspace")(filename)
        or util.find_git_ancestor(filename)
        or util.root_pattern("Package.swift")(filename)
  end,
  capabilities = capabilities,
  settings = {
    sourcekit = {
      enableSyntaxMap = true,
      enableSemanticHighlighting = true,
      completion = {
        enableSnippets = true,
      },
      diagnostic = {
        enableExperimental = true,
      },
    },
  },
})

Any idea how to fix? Thank you!

Have you tried this config:
https://github.com/wojciech-kulik/ios-dev-starter-nvim/blob/main/lua/starter/plugins/nvim-lspconfig.lua
?

OK, let me try. I don't have a reliable way to reproduce the error. I will use this config for a while and report :)

@haoyuan80s did you have this issue again?

Not again. I was not writing swift intensively in these two days. It often appears during many build/rebuild debugs. Feel free to close the issue. I don't think is the xcodebuild's problem. Thank you!

Sure, if it happens again, feel free to reopen it :)

Hey! It started happening to me too, 99% of the time is when I accept CMP's suggestion, doesn't seem to matter that the source of suggestion is. What info can I provide to make it clear why that happens?

Hi! This issue is unrelated with this plugin, so it would be best to open a ticket in sourcekit-lsp repo.
Also, we are having a similar discussion here: https://github.com/SolaWing/xcode-build-server/issues/43

Got it, thanks!


[release-v1.2] Dispatcher verticles are now worker verticles

Cherry-pick of https://github.com/knative-sandbox/eventing-kafka-broker/pull/2300/files

Cloning "https://github.com/openshift-knative/eventing-kafka-broker.git" ...
error: fatal: unable to access 'https://github.com/openshift-knative/eventing-kafka-broker.git/': The requested URL returned error: 429

/retest-required

/retest-required

/retest-required

It worked!
100 channels and subscriptions created and deleted
...
namespace "foo99" deleted
namespace/foo100 created
kafkachannel.messaging.knative.dev/channel created
subscription.messaging.knative.dev/event-display created
service/event-display created
deployment.apps/event-display created
sinkbinding.sources.knative.dev/bind-heartbeat created
deployment.apps/hearbeat created
kafkachannel.messaging.knative.dev/channel condition met
subscription.messaging.knative.dev/event-display condition met
Waiting for first events for foo100 for 2s
Waiting for first events for foo100 for 3s
Waiting for first events for foo100 for 4s
Waiting for first events for foo100 for 5s
Waiting for first events for foo100 for 6s
Waiting for first events for foo100 for 7s
namespace "foo100" deleted

retesting to be sure:
/test 410-reconciler-aws-ocp-410

/test 410-e2e-aws-ocp-410

/retest-required

/retest-required

/cherry-pick release-v1.3

/retest

it's green but it's stuck, so merging manually


Messaging around possible differences in state expectations

Why
The possible build states are not the states that will be returned by state in the API.
Eg, a blocked build could return state as passed, but would return blocked as true.

Ah! I should ready your PR descriptions before launching into a diatribe!
You mean blocked 🤦 which is kinda what I suspected. I'll amend your PR

Hi again @mcncl ,
In order to improve the discoverability of this information, I've added this info to the existing callout in the reused descriptions throughout other relevant areas of the docs (i.e. the Notifications and Defining steps pages within the Configuring pipelines section of the Pipelines docs), since there are links to these sections where surfacing this idiosyncratic behaviour would be useful.
Anyway, I shall approve and merge this PR now, but if you have any concerns about these additional changes, please do let me know!


CUSTOMIZE CALLKIT NOTIFICATION AND CALL SCREEN UI

How to customize incoming call screen ui and notification ui of android and ios in flutter?... Please help me to resolve the issue..

Hi @Navaneet00 , did you find any solution about it?

No.. Did u get any solution?

Hlo @rishabhbajpai2000,
No I didn't get any solution.. Did u get any solution?

Guys.....any solutions?
@rishabhbajpai2000
@Navaneet00


Add the ability to draw basic shapes

An early design decision was made that Indigo would be limited to rendering images on top of images. However many times during development, it would have been useful to be able to draw at least basic but possibly arbitrary shapes and lines.
Would be good to add support at minimum for:

Pixels
Lines (Straight and curved)
Rectangles
Circles / Ovals

This is a big subject area and we don't need to solve all the possible permutations of drawing vector graphics in the first instance.
Doing this is reliant on this issue:
https://github.com/PurpleKingdomGames/indigo/issues/6 (more than one shader per layer)

Closing - Will be in the next release.

Did this get released? Is there a relevant doc or PR?

Hi @kag0, yes it did, it's in 0.7.0.
I haven't gotten round to the docs yet I'm afraid, nor is there an official example ...but there's some sample code here if it helps:
https://github.com/PurpleKingdomGames/indigo/blob/master/indigo/sandbox/src/main/scala/com/example/sandbox/scenes/ShapesScene.scala
There's a very brief mention of it in the release notes too:
https://github.com/PurpleKingdomGames/indigo/releases/tag/v0.7.0

Awesome!
I haven't been able to get that working yet 😬 but I'm using Indigo for LD48 and being able to draw rectangles for hitboxes will be very useful for debugging.

Cool! If you hop onto the Discord server I'll be happy to help you if you get stuck? Or there is a gitter channel that literally no-one uses - but you could be the first! 😁
Links to both on the Indigo repo homepage.


Increase JTHarness console output stdout limit?

From the 2021 January Release Retrospective it was noted we were missing Test log console output for some failed tests due to insufficient JTHarness log output: https://github.com/AdoptOpenJDK/TSC/issues/195#issuecomment-764535852
Current value is 100,000

It would be useful to know which test target produced that output.
I was about to propose that we start running the test targets in PARALLEL=dynamic mode, across 2-3 machines, which would split in half or thirds the amount of console output... which would likely render the need for changing the system property javatest.maxOutputSize to a higher value unnecessary.

It would be useful to know which test target produced that output.

@karianna can you remember which testcase this was?

I have encountered lots of cases where console output is too large to render in the browser. Also, Jenkins will have to use more RAM to respond to user queries (including TRSS) for large console output. I agree with Shelley, parallel is a preferred way.

It would be useful to know which test target produced that output.

@karianna can you remember which testcase this was?

Sorry, my mind is drawing a blank today :-(.


replaceExtensions not working with php

I've added php to the replaceExtensions, but when I do a production build, the filenames aren't being replaced with the checksums.
module.exports = function(defaults) {
  var env = EmberApp.env();
  var isProduction = env === 'production';

  var app = new EmberApp(defaults, {
    fingerprint : {
        replaceExtensions : [ 'html', 'php', 'css', 'js' ]
    },
    outputPaths: {
      app: {
        html: isProduction ? 'default.php' : 'index.html',
        css: {
          'app': '/media/application-name.css'
        },
        js: '/media/application-name.js'
      },
      vendor: {
        css: '/media/com_stonewall/vendor.css',
        js: '/media/com_stonewall/vendor.js'
      }
    },

Am I missing something?
EDIT: This actually looks like a problem with using different outputPaths, as when I remove them it works properly. Is there a way to include fingerprinting with different paths?

Are the php files included in the tree sent to the ember application? If you could contribute a failing test, it would be easier for me to figure this out for you.

Closing for now as the extensions are a complete abstraction and I don't see why one extension would work over another. Please provide any additional information and I will re-open.


[Runtime] Make ADTObject POD container type

https://discuss.tvm.ai/t/discuss-runtime-array-containers-array-adt-string/4582
TODO

[x] Fix allocator.
[x] Destructor
[x] ADTObj container interface improve.
[x] Object lifecycle correctness.

NOTE: You will likely need to change memory.h::Allocator interface to allow
Allocator::make_with_extra_space(size * sizeof(ObjectRef), alignof(ObjectRef))

NOTE: You will likely need to change memory.h::Allocator interface to allow
Allocator::make_with_extra_space<ADTObj>(alignof(ObjectRef), size * sizeof(ObjectRef))

Thanks for coming up with the name. :-)

cc @tqchen @zhiics @icemelon9 @junrushao1994

We care about alignment(otherwise it will leads to mysterious segfaults).
Please use std::aligned_storage, allocate an array of if. Make sure you at least get alignof(T), and the requested alignment is dividable by alignof(T)
As an alternative design, we can do
Allocator.make_with_extra_elems<ADTObject, ObjectRef>(num_elem, args);

Which also allows you to get std::align_of the second argument, and use https://en.cppreference.com/w/cpp/types/aligned_storage

The inplace array is indeed somewhat tricky :) Here is one idea to make the effort easier for more similar cases: apology for typing in a window. Have fun!
// Curiously recurring template pattern
template<typename ArrayType, typename ElemType>
class InplaceArray {
   public:
      // caclculate start location
      static_assert(sizeof(ArrayType) % align_of(ElemType));
      ~InplaceArray() {
         ArrayType* self = static_cast<ArrayType*>(this);
         if (!std::is_pod<ElemType>::value) {
           // destruct elements
            for (size_t i = 0; i < self->size(); ++i) {
               void* ptr = AddressOf(i);
               reinterpret_cast<ElemType*>(ptr)->ElemType::~ElemType();
            }
         }
      }
      ElemType& operator[](size_t i) {
         ArrayType* self = static_cast<ArrayType*>(this);
         if (i >= self->size()) {
            CHECK(i < self->capacity());
            void* ptr = AddressOf(i);
            new (ptr) ElemType();
            return *reinterpret_cast<ElemType*>(ptr);
         }
         return *reinterpret_cast<ElemType*>(ptr);
      }
   private:
     static constexpr const int kDataStart = sizeof(ArrayType);
     void* AddressOf(int i) {
        ArrayType* self = static_cast<ArrayType*>(this);
        return reinterpret_cast<char*>(self) + kDataStart;
     }
};

class ADTObj : public Object, public InlineArray<ADTObj> {
}

By aligned storage, I mean we use aligned storage to specify the unit size, and allocate an array of aligned storage, whose number of elements can be passed in runtime

By aligned storage, I mean we use aligned storage to specify the unit size, and allocate an array of aligned storage, whose number of elements can be passed in runtime

Thanks @tqchen. I missed the array part. That makes sense. I'm going to create a new handler in memory.h probably named ArrayHandler(suggestions welcome) which handles types like this(a header type followed by an array of element types). I'll also improve the user facing interface of ADTObject. (standard container like APIs and handle lifecycle correctly).

Comments addressed. Please take another look.  @tqchen @zhiics @icemelon9 @junrushao1994

Will do tomorrow :-)

@tqchen The c++ compiler in CI does not support defining static constexpr from sizeof of ADTObj, since its definition is not complete. I saw the error last time so I changed it to runtime constant. Do you want to upgrade the compiler version or I'll change it back to runtime constant?
/workspace/include/tvm/runtime/container.h:138:40:
error: invalid application of 'sizeof' to an incomplete type 'tvm::runtime::ADTObj'

  static constexpr size_t kDataStart = sizeof(ArrayType);

/workspace/include/tvm/runtime/container.h:163:7: note:
definition of 'tvm::runtime::ADTObj' is not complete until the closing '}'

class ADTObj : public Object, public InplaceArrayBase<ADTObj, ObjectRef> {

Interesting, sorry I didn't realize that due to injection the child class was not complete. It is fine to turn into runtime constant then, but we still need the static assert. An alternative way to do that is to introduce an auxiliary traits class that defines these constants and derived types, and then make use of these constants inside the functions(which will then know the complete type)

Comments about Init function design, we want something that is minimum(can be reused by Vector style sub-class and Tuple-style sub-classes), while not interfering too much with low-level content.
One possible such interface could looks like http://www.cplusplus.com/reference/vector/vector/emplace_back/
protected:
  template <typename... Args>
  void EmplaceInit(size_t idx, Args&&... args);

Which EmplaceInit initializes elements at location idx(given the that idx has not been initialized before. This function can then be used by various other initializer/push_back functions(which we can debate whether they should be in the sub-class or base).

@tqchen I changed the interface a little bit. Now the set of interfaces are:

assign(initializer_list/iterator). This is the interface to initialize an array.
push_back(value). This is the interface to insert elements to the array with a value
emplace_back(args). This is the interface to insert elements to the array in place with arguments. It uses EmplaceInit under the hood.
The reason to have 1 is that it's common to have a source array we want to copy from(ADT, Tuple, for example), we can not easily do inplace initialization. 2 and 3 achieves the same thing just how to do it.

@wweic Some further comments. I think we don't have to implement push_back and emplace_back at the base level as ADT are immutable, we just need to have easy tools to initialize an element(EmplaceInit) and can build the rest of the features in the sub-class on top of the base class.
Thanks for the changes so far. Base data structure is a fundamental piece for the system, so we have to be extra picky in reviewing the code, but it is also rewarding and fun to build.

@tqchen thanks a lot for the comments. Leant something new about our object system, please let me know if you have further comments.

overall looks good, please add some final test cases to tests/cpp/, in particular, it would be great if we can test the exception safe feature(by having an constructor that throws).

@tqchen Tests added. It's a bit contrived since I need to ensure deterministic exception during unit testing. Please take a look.

Thanks @wweic @junrushao1994 , this pr is now merged

@wweic seems that the change breaks MSVC compilation https://dev.azure.com/tvmai/tvm/_build/results?buildId=3440
please followup and send a fix

@tqchen Can we make PR check in blocked on Azure Build test pass as well?


awsmobile publish stops if a cloud-api is imported; does not deploy frontend

I set up a MobileHub project a few days ago with an imported Cloud API, TokenGenerator. As expected, there is no code for this API pulled down by awsmobile pull. As not expected, awsmobile push does not work. I had been using<EMAIL_ADDRESS>but just upgraded to 1.0.11:
removed 12 packages and updated 4 packages in 4.274s
I get the same error:
$ awsmobile push
checking for local backend changes
      Warning: no codebase found for lambda function: TokenGenerator/{proxy+}: undefined

This is keeping me from publishing, which is a pain.

It was a bug and it's been fixed. please get the latest version 1.0.12

Do you think it'll work if there are a mix of MH-created and imported APIs?

For some reason (perhaps due to using old version of the CLI) it now thinks a backend update is required and still fails. Same error as above.
My most recent comment suggested that the push would still fail if a MH-created (and locally edited) API needed to push, but an imported (and not locally edited) API also existed.

I tried a pull before trying publish (to try to sync up state) but did not sync backend with #current-backend-info. Should I have?

$ diff -b -r awsmobilejs/{#current-backend-info,backend}
Only in awsmobilejs/#current-backend-info: aws-exports.js
Only in awsmobilejs/#current-backend-info: backend-details.json
Only in awsmobilejs/backend: cloud-api
diff -b -r awsmobilejs/#current-backend-info/mobile-hub-project.yml awsmobilejs/backend/mobile-hub-project.yml
9c9
<           api-arn: "arn:aws:execute-api:us-east-1:305905853980:w50y4cvwed"
---
>           api-arn: 'arn:aws:execute-api:us-east-1:305905853980:w50y4cvwed'
14c14
<           "/{proxy+}": !com.amazonaws.mobilehub.v0.Function {}
---
>           '/{proxy+}': !com.amazonaws.mobilehub.v0.Function {}

Yes, please execute awsmobile pull and sync backend with #current-backend-info

Makes no difference. Same diffs as above, and publish still wants to push.

Looking at backend-update.js, I understand why it wants to push (last push failed).
The problem is the push failing, not the decision that a push is needed. Go back to the original error: the tool does not seem to support an imported API.

We will notify our server side team on this issue

Update: I just realized the message above is not a fail but a warning (indeed push returns status 0), but nevertheless something about the imported API causes publish to not proceed to deploy the front end.

Hi @ceich I did reproduced the issue. We are working on a fix and planning to publish it ASAP.
Thanks

This is a bug, and it has been fixed. The fix will be released in the next version. Thanks for providing the information.

The latest update (v 1.0.13) should have resolved this issue.

Thanks, it seems to work for me. Warning is still in place for an expected situation, but the push/publish both run to completion.
I haven't tried with a backend that mixes imported and MH-created APIs.


feat: allow loading custom device configs from store/config

Ref: https://github.com/zwave-js/node-zwave-js/pull/2406, needs new zwave-js release

Pull Request Test Coverage Report for Build 774848324

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 17.901%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

lib/ZwaveClient.js
0
2
0.0%

Totals

Change from base Build 773285060:
-0.002%

Covered Lines:
2030

Relevant Lines:
11631

💛  - Coveralls


⚠ Spryr has degraded performance

In ca1e46f, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3505 ms

Resolved: Spryr performance has improved in 13172ea after 13 minutes.


fix ISO8601.DATETIME_COMPLETE format

time parts were using uppercase rather than lowercase

Looks good. Can you add a test verifying it as a sample to others and to prevent future regressions?


[VS Code] Cannot read property 'registerWorkspaceProvider' of undefined

Error:
Cannot read property 'registerWorkspaceProvider' of undefined
Steps to Reproduce:

Click on a Live Sharing Link sent to you by a collaborator after signed in
See error modal in corner of screen after editor opens up and click on "Try Again" and live sharing session will close
Same thing happens if you click on your signed in icon at the bottom of the editor, then copy and paste the live sharing link into the extension instead

Version Data

extensionName
VSLS

extensionVersion
0.3.504

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.22.2

platformName
MacOS

platformVersion
16.7.0

@existenzial Thanks for reporting this issue. We are tracking this with #751 and we'll get this fixed in the next update.


Could \begin{align} and \begin{split} be added?

These are useful for long equations that aren't simple matrices, multiple long equations in sequence, among other things, and are a lot nicer than what I'm currently using (basically \begin{aligned} with set alignment points, which is super brittle and it doesn't look very pretty).

The {split} environment would certainly be useful. Without {split}, one can usually hack something together with {aligned}, \phantom, and \mathllap, but the same thing is easier and cleaner with {split}. We should definitely have that on our list of things to do.
You titled this issue by requesting {split} and {align}. I'm confused by the {align} part because the only difference between {align} and {aligned} is that {aligned} can be used only when LaTeX is already in math mode.  KaTeX starts out already in math mode, so one would nest one {aligned} inside another {aligned}. The outer environment doesn't have to be {align}.
Or maybe you meant something else. {equation} perhaps?

I'm unfamiliar with split, but my reading of amsmath docs so far suggests that it's equivalent to matrix but with arraycolsep set to zero.  Is this correct?  If so, it should be relatively easy to add.
And agreed, we already effectively support align via aligned, though I'd still like to add it as an alternative to \[ at the top level.

Yes, this is rarely essential on web pages but split is really useful in things like IEEE journals where the columns are narrow - obviously this is not quite the primary use-case of KaTeX as such, but for having the same equations across both.
Apropos @edemaine's idea, the AMS implementation seems to be distinct from matrix but I suspect that recycling matrix to this end would be adequate for most KaTeX use-cases.

This would also be useful on mobile devices where the screen is narrow.

There are more subtle differences between \begin{align} and \begin{aligned}, though, ones which make \begin{aligned} (and thus KaTeX as a whole) untenable for my workflow. In particular, you're not supposed to be able to use use \tag() in a \begin{aligned} environment. It gives errors in MathJax (and actual LaTeX I believe), where the correct solution is to instead use \begin{align} (unsupported in MathJax). This means I can't keep the same source code compatible with different engines.
For example, the following snippet renders incorrectly using KaTeX - it puts the tag centered in the middle of the whole block, instead of at the bottom line where it belongs. I think it is also incorrect I guess to allow \tag inside of the aligned environment in the first place, as MathJax (and I assume proper LaTeX) doesn't accept it.
\begin{aligned}
\Delta K = K_2 - K_1 = +W_{12} \\
\Delta U = U_2 - U_1 = -W_{12} \\
\Delta K + \Delta U \\
K_2 + U_2 = K_1 + U_1 \\
E = K + U \tag{mechanical energy is conserved}
\end{aligned}

Closed via PR#2369.


Babel-eslint doesn't throw an error while parsing

Guys from eslint instructed me to create a ticket here, the original report is in this issue: https://github.com/eslint/eslint/issues/8648
Version of babel-eslint: 7.2.3
Please let me know, if I can provide any additional info.

Based on the code sample you gave:
var bar = function (foo) {
    const foo = 123;
    return foo;
};

That actually is a syntax error. If I run this code in an environment that supports const (most environments these days) then I get:

So the solution is to change your code so you're not redeclaring the parameter foo.
Unless I'm missing something. Please re-open this if there's more to it.

Yes, I know that I should change my code, thank you.
But the question is why babel-lint doesn't throw an exception while parsing, while espree does?
I would expect parser to fail when encountering error and be consistent with espree, since it makes sense that linting fails in this case (what currently simply doesn't happen).

Ah, gotcha. My guess is this is actually a babylon parser issue. But that's outside of my level of experience. I'll re-open this and hopefully someone with more experience can chime in. Thanks for clarifying.

There is an issue in babylon https://github.com/babel/babylon/issues/78

Looks like this is just an issue in babel's parser ^ https://github.com/babel/babel/issues/6722


Update Azure SDK tools Consumption Story

Update method of consuming SDK tools to use resources and templates.

/azp run license/cla

/azp run license

/azp run js - cosmos - ci

Cosmos Failure tracked with #5049


grpc client completion queue not shutting down

What version of gRPC and what language are you using?
1.16.1
What operating system (Linux, Windows,...) and version?
LINUX
What runtime / compiler are you using (e.g. python version or version of gcc)
gcc
My code performs the following:
1)Create grpc channel
2)start monitoring completion queue in a different thread
3)Issue shutdown on completion queue
After executing step 3, I expect "(cq.Next(&tag, &ok)" to return false as there are no pending events with above 3 steps. But it is observed that "(cq.Next(&tag, &ok)" never returns false. Please let me know if I am missing something.
Thanks,
ikshu

In order to get channel state notification, a tag was being added to the queue and that use to always post some events. so the cq->next() never returned false. I fixed this issue by achieving same functionality by already existing APIs. So closing the bug.


Removed deprecated scale_factor and x_min/x_max/y_min/y_max parameters.

Depreciation purpose.
In VS Code, I searched for  "until 0.11" and deleted all references.

@hydrobeam : Do you mind having a look why readthedocs fails?
Feel free to push the fix directly on this branch


Separate Training Files vs Single Training File

Hello,
Does it make any difference to have the training text file as a single file or separate files ?
Is the internal state rest it self between different text files ?
I tried to train a model with separate files vs single file, and so far I can see the perplexity is much lower when I have separate files.

It shouldn't make a difference with one vs many files, assuming they are prepared in the same manner (e.g. were generated with something like cat separate_files* > single_file.txt), you specify all of the separate files for training, and you are careful to separate the heldout validation/test files from the training files.


chore: Included githubactions in the dependabot config

This should help with keeping the GitHub actions updated on new releases. This will also help with keeping it secure.
Dependabot helps in keeping the supply chain secure https://docs.github.com/en/code-security/dependabot
GitHub actions up to date https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot
https://github.com/ossf/scorecard/blob/main/docs/checks.md#dependency-update-tool
Signed-off-by: naveen<EMAIL_ADDRESS>

Looking at it ...

LGTM.
@oscerd any thoughts about this? It seems to apply only to the Github actions, which, IMHO, seems fine.

Checkstyle failure is irrelevant in this context. Merging.

Thanks for  your contribution @naveensrinivasan!


Deadlands Classic Redesign

The original sheet was designed by Kevin Justus (Rats). The sheet was upgraded to include rolling, skill modifiers, multi damge die per weapon, and an improved layout.
Prequest https://github.com/Roll20/roll20-character-sheets/pull/3574 submitting changes as a ungrade to the existing sheet. Orginal sheet design credited.

The Fields that will not migrate cleanly are Fate Chips, Ammo, and Weapons.
Fate Chips
Were changed to be by the rules of the system. The originally sheet had it so you could only get 5 of each type. This is wrong the system allows for up to 10 whites, 5 red, 4 blue, and 2 Legend. As a result I lowered the max on Red, Blue, and Legend chips and increased the max on white. The impact on the game should be extremely minimal. Most players will have spent their chips for EXP at the end of the session.
Ammo
Ammo on the sheet, was not very friendly and extremely limited and restive. The sheet only allowed you to track 3 ammo's. With 2 fields being a restive 0-6, and 1 field 0-15.  The Ammo fields on the official printed character sheets could be used a couple different ways.
While this method is fine for pen and paper, it's restive in a digital system. Which forces you to track those sorts of things in different places. So the ammo section was converted to repeating field with custom names, unrestricted capacity and notes. This allows the players to track their ammo in any way they wish. You wouldn't be able to track a belt feed Gatling gun with the current sheet.
This should have a minimal affect on existing games.
Weapons
Originally the fields were just weapon#name, weapon#shots, weapon#rof, weapon#range, weapon#damage. weapon#def, and weapon#speed. Where # was 1-8 (1-4 being ranged, and 5-8 being melee). Though not all of those fields were available for each weapon. So creating macro's to roll things becomes confusing. As well the damage for most weapons were variable. So the damage field was mostly just a description.
So to make macro's easier to create and allow for the weapons to be expanded. As 4 for each category and 1 forced slot (giving you 7 total weapons) were not enough. So i broke the fields down into their seprate groups. Range and Melee, and converted the damage field into a repeat field.
rngweaponname#, rngweaponshots#, rngweaponrof#, rngweaponrange#, rngweapondamage# (repeating field),  where # is 1-6.
meleeweaponname#, meleeweapondefense#, meleeweaponspeed#, meleeweapondamage# (repeating field),  where # is 1-6.
This will be the largest impact on a game. As the players will have to reenter their weapons. Though their macro's should still work. As i did not reuse the old field names. I could possibly put a read only reference to the old weapon values under the misc column.

From your description, it sounds like it may be possible to use a sheet worker to import the old weapons into the new repeating sections. If you aren't familiar with sheet workers, I may be able to find an example to point you toward.
However, if it is simply not possible to convert the old data this way, I would definitely recommend putting all of the data that won't carry over in a new column as you suggest, so players will at least have it to refer to when converting to the new system.
Preferably, there would be a warning dialog at the top of the sheet that will inform users of the change and instruct them how to convert their data to the new system. You can make this dialog only show up the first time the sheet is opened by having them click a checkbox to dismiss it. You can also plan to completely remove the old data from the sheet after everyone has had plenty of time to convert (at least a month is a good rule of thumb), but be sure to inform users when it will be removed in that warning dialog.

If you have a sheet work explain I can take a look. I've not worked with the sheet workers before beyond minor tinkering.
Meanwhile i'll just add a new tab and warning.

I did just add in a new tab, and notices for the older fields.


(TWILL-112) Improve performance of ApplicationBundler

Not to scan a directory again if the directory was added to the bundle jar that is building in progress already

+1 with minor nit on naming.

+1