[devtools] Add new announcements in WNDT86, rename media url

What's changed, or what was fixed?

Add additional announcements in WNDT86
rename media url - Microsoft suggests to rename to avoid name clashing with their assets folder
run images through ImageOptim

Target Live Date: 2020-08-28

[x] This has been reviewed and approved by (@chybie)
[x] I have run npm test locally and all tests pass.
[x] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

Whoops!
There were 75 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/media-panel/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L34 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L50 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L55 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media/images/01-empty.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/01-empty.png'
src/content/en/tools/chrome-devtools/media/images/02-view.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/02-view.png'
src/content/en/tools/chrome-devtools/media/images/03-events.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/03-events.png'
src/content/en/tools/chrome-devtools/media/images/04-messages.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/04-messages.png'
src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png'
src/content/en/tools/chrome-devtools/media/images/07-hide-show.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/07-hide-show.png'
src/content/en/tools/chrome-devtools/media/images/08-save.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/08-save.png'
src/content/en/updates/2020/08/devtools.md#L291 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/08/devtools.md#L107 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/2020/08/devtools.md#L3 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L35 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L37 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L142 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/08/devtools.md#L28 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L39 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L53 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L66 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L68 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L70 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L74 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L94 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L98 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L112 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L113 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L122 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L128 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L129 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L130 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L132 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L136 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L146 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L148 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L153 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L159 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L173 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L177 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L183 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L194 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L225 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L237 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L239 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L250 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L252 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L262 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L282 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L298 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L13 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L144 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L169 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L170 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L177 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L178 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L182 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L15 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L152 - Line must be at most 100 characters
src/content/en/updates/images/2020/08/properties-pane.png - Try to keep files below 500K, was 509K

Whoops!
There were 75 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/media-panel/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L34 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L50 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L55 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media/images/01-empty.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/01-empty.png'
src/content/en/tools/chrome-devtools/media/images/02-view.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/02-view.png'
src/content/en/tools/chrome-devtools/media/images/03-events.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/03-events.png'
src/content/en/tools/chrome-devtools/media/images/04-messages.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/04-messages.png'
src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png'
src/content/en/tools/chrome-devtools/media/images/07-hide-show.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/07-hide-show.png'
src/content/en/tools/chrome-devtools/media/images/08-save.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/08-save.png'
src/content/en/updates/2020/08/devtools.md#L291 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/08/devtools.md#L107 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/2020/08/devtools.md#L3 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L35 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L37 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L142 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/08/devtools.md#L28 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L39 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L53 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L66 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L68 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L70 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L74 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L94 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L98 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L112 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L113 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L122 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L128 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L129 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L130 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L132 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L136 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L146 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L148 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L153 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L159 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L173 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L177 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L183 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L194 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L225 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L237 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L239 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L250 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L252 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L262 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L282 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L298 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L13 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L144 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L169 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L170 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L177 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L178 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L182 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L15 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L152 - Line must be at most 100 characters
src/content/en/updates/images/2020/08/properties-pane.png - Try to keep files below 500K, was 509K

Whoops!
There were 75 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/chrome-devtools/media-panel/index.md#L14 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L22 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L34 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L42 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L50 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media-panel/index.md#L55 - Line must be at most 100 characters
src/content/en/tools/chrome-devtools/media/images/01-empty.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/01-empty.png'
src/content/en/tools/chrome-devtools/media/images/02-view.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/02-view.png'
src/content/en/tools/chrome-devtools/media/images/03-events.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/03-events.png'
src/content/en/tools/chrome-devtools/media/images/04-messages.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/04-messages.png'
src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/06-remote-debug.png'
src/content/en/tools/chrome-devtools/media/images/07-hide-show.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/07-hide-show.png'
src/content/en/tools/chrome-devtools/media/images/08-save.png - Unable to read file stats: ENOENT: no such file or directory, stat 'src/content/en/tools/chrome-devtools/media/images/08-save.png'
src/content/en/updates/2020/08/devtools.md#L291 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/2020/08/devtools.md#L107 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/2020/08/devtools.md#L3 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L33 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L35 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L37 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L39 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/2020/08/devtools.md#L142 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/2020/08/devtools.md#L28 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L39 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L43 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L53 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L66 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L68 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L70 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L74 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L81 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L85 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L94 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L98 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L112 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L113 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L122 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L128 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L129 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L130 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L131 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L132 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L136 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L146 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L148 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L153 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L159 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L173 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L177 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L183 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L194 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L225 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L237 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L239 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L250 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L252 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L262 - Line must be at most 100 characters
src/content/en/updates/2020/08/devtools.md#L282 - Line must be at most 100 characters
src/content/en/updates/_shared/discover.md#L298 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/updates/_shared/discover.md#L13 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L30 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L8 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L144 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L169 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L170 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L177 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L178 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L182 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L188 - Common typo found: 'node' Should it be 'Node'?
src/content/en/updates/_shared/discover.md#L15 - Common typo found: 'Service Worker' Should it be 'service worker'? Capitalize Service if it's the first word in the sentence.
src/content/en/updates/_shared/discover.md#L152 - Line must be at most 100 characters
src/content/en/updates/images/2020/08/properties-pane.png - Try to keep files below 500K, was 509K


Allow usage of mini.clue of specified kind of non listed buffers

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.clue
Description
As i understand it mini.clue currently only acts on listed buffers as no mapings are created in non-listed buffers.
I would love to use the submode feature especially for the window management functionality (e.g. resize, navigate).
For example i would like to be able to use those from within neotree- or diffview-buffers.
Would this be possible to achieve?

I would love to use the submode feature especially for the window management functionality (e.g. resize, navigate). For example i would like to be able to use those from within neotree- or diffview-buffers.
Would this be possible to achieve?

Yes, this is possible by manually calling enable_buf_triggers for target buffers.
Here is an example of automatically doing this for help buffers:
local clue_group = vim.api.nvim_create_augroup('my-miniclue', { clear = true })
vim.api.nvim_create_autocmd('FileType', {
  pattern = 'help',
  group = clue_group,
  callback = function(data) MiniClue.enable_buf_triggers(data.buf) end,
})

Oh, of course! Thanks for the quick hint!


Re-release to contain recent changes

There have been a few changes to the openfga protocol since the last release. I.e.:
https://github.com/openfga/api/commit/a45dbd0cdbe5b0a219a9353998bbbd4939c50545
It would be great to re-release.
I would also prefer to have those .proto files explicitly in the crate (basically un-gitignore the proto folder or keep the generated rs) so that the state against which was build is visible. Currently there would be zero diff even if some important things changed.

I think this would also enable to remove the allow_dirty and publish_allow_dirty release plz flags


Subtitles of movies are not optional

Marvel's Ten Rings movie dies not give option in English.
I have no idea what language is spoken in now

This is not in the scope of this application.
FrostWire is just a Bittorrent client, it does not control what people share to one another.
Also, please respect your local copyright laws. FrostWire condemns copyright infringement.


[BUG] ClassCastException for Create Connector, Deploy Model, Model Group

What is the bug?
This issue is similar to the 3rd issue of https://github.com/opensearch-project/opensearch-ai-flow-framework/issues/108 but for Create Connector and Register Model Group.
[2023-10-31T19:10:01,406][INFO ][o.r.Reflections          ] [ip-172-31-56-214] Reflections took 1 ms to scan 1 urls, producing 5 keys and 15 values
[2023-10-31T19:10:01,412][INFO ][o.r.Reflections          ] [ip-172-31-56-214] Reflections took 4 ms to scan 1 urls, producing 11 keys and 49 values
[2023-10-31T19:10:01,416][INFO ][o.r.Reflections          ] [ip-172-31-56-214] Reflections took 2 ms to scan 1 urls, producing 8 keys and 11 values
[2023-10-31T19:10:01,449][INFO ][o.o.m.a.c.TransportCreateConnectorAction] [ip-172-31-56-214] connector created, indexing into the connector system index
[2023-10-31T19:10:01,452][INFO ][o.o.p.PluginsService     ] [ip-172-31-56-214] PluginService:onIndexModule index:[.plugins-ml-connector/Iib6OaZJQ4G1-MRjc0YYZw]
[2023-10-31T19:10:01,457][INFO ][o.o.c.m.MetadataCreateIndexService] [ip-172-31-56-214] [.plugins-ml-connector] creating index, cause [api], templates [], shards [1]/[1]
[2023-10-31T19:10:01,458][INFO ][o.o.c.r.a.AllocationService] [ip-172-31-56-214] updating number_of_replicas to [0] for indices [.plugins-ml-connector]
[2023-10-31T19:10:01,471][INFO ][o.o.p.PluginsService     ] [ip-172-31-56-214] PluginService:onIndexModule index:[.plugins-ml-connector/Iib6OaZJQ4G1-MRjc0YYZw]
[2023-10-31T19:10:01,499][INFO ][o.o.c.r.a.AllocationService] [ip-172-31-56-214] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-connector][0]]]).
[2023-10-31T19:10:01,511][INFO ][o.o.m.i.MLIndicesHandler ] [ip-172-31-56-214] create index:.plugins-ml-connector
[2023-10-31T19:10:01,530][INFO ][o.o.m.a.c.TransportCreateConnectorAction] [ip-172-31-56-214] Connector saved into index, result:CREATED, connector id: 0OAkh4sBoiuECYuvjQUp
[2023-10-31T19:10:01,531][ERROR][o.o.f.w.CreateConnectorStep] [ip-172-31-56-214] Failed to create connector
[2023-10-31T19:10:01,532][ERROR][o.o.f.t.ProvisionWorkflowTransportAction] [ip-172-31-56-214] Provisioning failed for workflow z-Akh4sBoiuECYuvOQX8 : org.opensearch.flowframework.exception.FlowFrameworkException: java.util.concurrent.ExecutionException: org.opensearch.flowframework.exception.FlowFrameworkException: class org.opensearch.ml.common.transport.connector.MLCreateConnectorResponse cannot be cast to class org.opensearch.ml.common.transport.connector.MLCreateConnectorResponse (org.opensearch.ml.common.transport.connector.MLCreateConnectorResponse is in unnamed module of loader java.net.FactoryURLClassLoader @5580d62f; org.opensearch.ml.common.transport.connector.MLCreateConnectorResponse is in unnamed module of loader java.net.FactoryURLClassLoader @10823d72)

The solution would be similar to make the changes on ml-commons side like: https://github.com/opensearch-project/ml-commons/pull/1560 for Create Connector and Model Group.
How can one reproduce the bug?

Install ml-commons and flow-framework plugin to OS Cluster.
Hit the API

 curl -XPOST --insecure -u 'admin:admin' -H "Content-Type: application/json" 'http://localhost:9200/_plugins/_flow_framework/workflow' -d '{"name":"deploy-register-model","description":"test case","use_case":"SEMANTIC_SEARCH","version":{"template":"1.0.0","compatibility":["2.12.0","3.0.0"]},"workflows":{"provision":{"nodes":[{"id":"workflow_step_1","type":"create_connector","inputs":{"name":"OpenAI Chat Connector","description":"The connector to public OpenAI model service for GPT 3.5","version":"1","protocol":"http","parameters":{"endpoint":"api.openai.com","model":"gpt-3.5-turbo"},"credential":{"openAI_key":"..."},"actions":[{"action_type":"predict","method":"POST","url":"https://${parameters.endpoint}/v1/chat/completions"}]}},{"id":"workflow_step_2","type":"deploy_model","inputs":{"model_id":{}}}],"edges":[{"source":"workflow_step_1","dest":"workflow_step_2"}]}}}'
{"workflow_id":"z-Akh4sBoiuECYuvOQX8"}

Start provisioning

 curl -XPOST --insecure -u 'admin:admin' -H "Content-Type: application/json" 'http://localhost:9200/_plugins/_flow_framework/workflow/z-Akh4sBoiuECYuvOQX8/_provision'

What is the expected behavior?
A connector should be created and a model group should be registered.
What is your host/environment?
Ubuntu
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.

Additionally, there is a bug for the deploy model API of the MachineLearningNodeClient :
Provisioning failed for workflow LCifjIsBHB5sOr-SRvP8 : org.opensearch.flowframework.exception.FlowFrameworkException: java.util.concurrent.ExecutionException: org.opensearch.flowframework.exception.FlowFrameworkException: class org.opensearch.ml.common.transport.deploy.MLDeployModelResponse cannot be cast to class org.opensearch.ml.common.transport.deploy.MLDeployModelResponse (org.opensearch.ml.common.transport.deploy.MLDeployModelResponse is in unnamed module of loader java.net.FactoryURLClassLoader @17b6d426; org.opensearch.ml.common.transport.deploy.MLDeployModelResponse is in unnamed module of loader java.net.FactoryURLClassLoader @14b0e127)

I'll action this as well

PR https://github.com/opensearch-project/ml-commons/pull/1580 has been raised to resolve this issue :
Testing full provision workflow locally with create connector, register model, deploy model steps :
Creating the workflow :
curl -i -XPOST "localhost:9200/_plugins/_flow_framework/workflow" -H "Content-Type:application/json" --data '{"name":"create-connector-register-deploy-model","description":"test case","use_case":"TEST_CASE","version":{"template":"1.0.0","compatibility":["2.12.0","3.0.0"]},"workflows":{"provision":{"nodes":[{"id":"workflow_step_1","type":"create_connector","user_inputs":{"name":"OpenAI Chat Connector","description":"The connector to public OpenAI model service for GPT 3.5","version":"1","protocol":"http","parameters":{"endpoint":"api.openai.com","model":"gpt-3.5-turbo"},"credential":{"openAI_key":"..."},"actions":[{"action_type":"predict","method":"POST","url":"https://${parameters.endpoint}/v1/chat/completions"}]}},{"id":"workflow_step_2","type":"register_model","previous_node_inputs":{"workflow_step_1":"connector_id"},"user_inputs":{"name":"openAI-gpt-3.5-turbo","function_name":"remote","description":"test model"}},{"id":"workflow_step_3","type":"deploy_model","previous_node_inputs":{"workflow_step_2":"model_id"}}],"edges":[{"source":"workflow_step_1","dest":"workflow_step_2"},{"source":"workflow_step_2","dest":"workflow_step_3"}]}}}'
HTTP/1.1 201 Created
X-OpenSearch-Version: OpenSearch/3.0.0-SNAPSHOT (opensearch)
content-type: application/json; charset=UTF-8
content-length: 38

{"workflow_id":"EdaujIsBaJDYTfB0hQJD"}

Provisioning workflow :
curl -i -XPOST "localhost:9200/_plugins/_flow_framework/workflow/EdaujIsBaJDYTfB0hQJD/_provision"
HTTP/1.1 200 OK
X-OpenSearch-Version: OpenSearch/3.0.0-SNAPSHOT (opensearch)
content-type: application/json; charset=UTF-8
content-length: 38

{"workflow_id":"EdaujIsBaJDYTfB0hQJD"}

OpenSearch logs successful completion of all workflow steps : Provisioning completed successuflly for workflow EdaujIsBaJDYTfB0hQJD
[2023-11-01T20:58:49,537][INFO ][o.o.f.i.FlowFrameworkIndicesHandler] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-ai-global-context
[2023-11-01T20:58:49,583][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-workflow-state/5Y85uH9nRsm2fOIILM98Jw]
[2023-11-01T20:58:49,596][INFO ][o.o.c.m.MetadataCreateIndexService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-workflow-state] creating index, cause [api], templates [], shards [1]/[1]
[2023-11-01T20:58:49,598][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updating number_of_replicas to [0] for indices [.plugins-workflow-state]
[2023-11-01T20:58:49,620][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-workflow-state/5Y85uH9nRsm2fOIILM98Jw]
[2023-11-01T20:58:49,662][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-workflow-state][0]]]).
[2023-11-01T20:58:49,680][INFO ][o.o.f.i.FlowFrameworkIndicesHandler] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-workflow-state
[2023-11-01T20:58:49,693][INFO ][o.o.f.t.CreateWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create state workflow doc
[2023-11-01T20:59:07,901][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Queueing process [workflow_step_1]. Can start immediately!
[2023-11-01T20:59:07,903][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Queueing process [workflow_step_2]. Must wait for [workflow_step_1] to complete first.
[2023-11-01T20:59:07,903][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Starting workflow_step_1.
[2023-11-01T20:59:07,903][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Queueing process [workflow_step_3]. Must wait for [workflow_step_2] to complete first.
[2023-11-01T20:59:07,921][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 8 ms to scan 1 urls, producing 6 keys and 34 values
[2023-11-01T20:59:07,931][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 7 ms to scan 1 urls, producing 8 keys and 38 values
[2023-11-01T20:59:07,934][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updated workflow EdaujIsBaJDYTfB0hQJD state to PROVISIONING
[2023-11-01T20:59:07,936][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 2 ms to scan 1 urls, producing 5 keys and 14 values
[2023-11-01T20:59:07,941][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 2 ms to scan 1 urls, producing 3 keys and 8 values
[2023-11-01T20:59:07,946][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 3 ms to scan 1 urls, producing 5 keys and 15 values
[2023-11-01T20:59:07,957][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 8 ms to scan 1 urls, producing 11 keys and 49 values
[2023-11-01T20:59:07,963][INFO ][o.r.Reflections          ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Reflections took 3 ms to scan 1 urls, producing 8 keys and 11 values
[2023-11-01T20:59:08,004][INFO ][o.o.m.a.c.TransportCreateConnectorAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] connector created, indexing into the connector system index
[2023-11-01T20:59:08,008][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-connector/mkvQpiBkRHicZA9y0Lj8YQ]
[2023-11-01T20:59:08,019][INFO ][o.o.c.m.MetadataCreateIndexService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-ml-connector] creating index, cause [api], templates [], shards [1]/[1]
[2023-11-01T20:59:08,020][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updating number_of_replicas to [0] for indices [.plugins-ml-connector]
[2023-11-01T20:59:08,041][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-connector/mkvQpiBkRHicZA9y0Lj8YQ]
[2023-11-01T20:59:08,089][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-connector][0]]]).
[2023-11-01T20:59:08,107][INFO ][o.o.m.i.MLIndicesHandler ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-ml-connector
[2023-11-01T20:59:08,130][INFO ][o.o.m.a.c.TransportCreateConnectorAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Connector saved into index, result:CREATED, connector id: EtaujIsBaJDYTfB0zQLN
[2023-11-01T20:59:08,131][INFO ][o.o.f.w.CreateConnectorStep] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Created connector successfully
[2023-11-01T20:59:08,131][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Finished workflow_step_1.
[2023-11-01T20:59:08,131][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Starting workflow_step_2.
[2023-11-01T20:59:08,151][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-model-group/mVNad_2QSLqHZpVRbVXw-w]
[2023-11-01T20:59:08,156][INFO ][o.o.c.m.MetadataCreateIndexService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-ml-model-group] creating index, cause [api], templates [], shards [1]/[1]
[2023-11-01T20:59:08,157][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updating number_of_replicas to [0] for indices [.plugins-ml-model-group]
[2023-11-01T20:59:08,175][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-model-group/mVNad_2QSLqHZpVRbVXw-w]
[2023-11-01T20:59:08,221][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-model-group][0]]]).
[2023-11-01T20:59:08,238][INFO ][o.o.m.i.MLIndicesHandler ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-ml-model-group
[2023-11-01T20:59:08,255][INFO ][stdout                   ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] registering the model
[2023-11-01T20:59:08,259][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-task/vUP_B5jWR8yZAPlX2kNELA]
[2023-11-01T20:59:08,265][INFO ][o.o.c.m.MetadataCreateIndexService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-ml-task] creating index, cause [api], templates [], shards [1]/[1]
[2023-11-01T20:59:08,266][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updating number_of_replicas to [0] for indices [.plugins-ml-task]
[2023-11-01T20:59:08,283][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-task/vUP_B5jWR8yZAPlX2kNELA]
[2023-11-01T20:59:08,329][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-task][0]]]).
[2023-11-01T20:59:08,346][INFO ][o.o.m.i.MLIndicesHandler ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-ml-task
[2023-11-01T20:59:08,384][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-model/AxPVDVOfT12WB8srj-eePQ]
[2023-11-01T20:59:08,394][INFO ][o.o.c.m.MetadataCreateIndexService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-ml-model] creating index, cause [api], templates [], shards [1]/[1]
[2023-11-01T20:59:08,395][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] updating number_of_replicas to [0] for indices [.plugins-ml-model]
[2023-11-01T20:59:08,412][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-model/AxPVDVOfT12WB8srj-eePQ]
[2023-11-01T20:59:08,452][INFO ][o.o.c.r.a.AllocationService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Cluster health status changed from [YELLOW] to [GREEN] (reason: [shards started [[.plugins-ml-model][0]]]).
[2023-11-01T20:59:08,468][INFO ][o.o.m.i.MLIndicesHandler ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create index:.plugins-ml-model
[2023-11-01T20:59:08,480][INFO ][o.o.p.PluginsService     ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] PluginService:onIndexModule index:[.plugins-ml-model/AxPVDVOfT12WB8srj-eePQ]
[2023-11-01T20:59:08,488][INFO ][o.o.c.m.MetadataMappingService] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] [.plugins-ml-model/AxPVDVOfT12WB8srj-eePQ] update_mapping [_doc]
[2023-11-01T20:59:08,527][INFO ][o.o.m.m.MLModelManager   ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] create new model meta doc FdaujIsBaJDYTfB0zwI2 for upload task FNaujIsBaJDYTfB0zgK8
[2023-11-01T20:59:08,530][INFO ][o.o.f.w.RegisterModelStep] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Model registration successful
[2023-11-01T20:59:08,531][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Finished workflow_step_2.
[2023-11-01T20:59:08,531][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Starting workflow_step_3.
[2023-11-01T20:59:08,541][INFO ][o.o.m.a.d.TransportDeployModelAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Will deploy model on these nodes: KjtqJSkTSISCXGLthC9oAQ
[2023-11-01T20:59:08,581][INFO ][o.o.m.m.MLModelManager   ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Set connector EtaujIsBaJDYTfB0zQLN for the model: FdaujIsBaJDYTfB0zwI2
[2023-11-01T20:59:08,582][INFO ][o.o.f.w.DeployModelStep  ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Model deployment state COMPLETED
[2023-11-01T20:59:08,583][INFO ][o.o.f.w.ProcessNode      ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Finished workflow_step_3.
[2023-11-01T20:59:08,583][INFO ][o.o.f.t.ProvisionWorkflowTransportAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Provisioning completed successuflly for workflow EdaujIsBaJDYTfB0hQJD
[2023-11-01T20:59:08,619][INFO ][o.o.m.a.f.TransportForwardAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] deploy model done with state: DEPLOYED, model id: FdaujIsBaJDYTfB0zwI2
[2023-11-01T20:59:08,620][INFO ][o.o.m.a.d.TransportDeployModelOnNodeAction] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] deploy model task done FtaujIsBaJDYTfB0zwKB
[2023-11-01T20:59:08,621][INFO ][o.o.m.m.MLModelManager   ] [dev-dsk-jpalis-2c-27c8aa11.us-west-2.amazon.com] Completed setting connector EtaujIsBaJDYTfB0zQLN in the model FdaujIsBaJDYTfB0zwI2


itkSLICImageFilterTest1 fails on macOS ARM

With current ITK Git master, itkSLICImageFilterTest fails on macOS ARM.
2803:   AverageResidual: 1.79769e+308
2803: Name of Class = SLICImageFilter
2803: Iterations #: 0 Average Residual: 0.296951
2803: Iterations #: 1 Average Residual: 0.123393
2803: Iterations #: 2 Average Residual: 0.0615196
2803: Iterations #: 3 Average Residual: 0.0413902
2803: Iterations #: 4 Average Residual: 0.0348925
2803: Iterations #: 5 Average Residual: 0.0359442
2803: Iterations #: 6 Average Residual: 0.030454
2803: Iterations #: 7 Average Residual: 0.026951
2803: Iterations #: 8 Average Residual: 0.0222663
2803: Iterations #: 9 Average Residual: 0.0223891
2803: Test finished.
2803: <DartMeasurement name="ImageError itkSLICImageFilterTest1.1.png" type="numeric/double">187</DartMeasurement>
2803: <DartMeasurement name="ImageError itkSLICImageFilterTest1.png" type="numeric/double">67</DartMeasurement>
2803: <DartMeasurement name="ImageError" type="numeric/double">67</DartMeasurement>
2803: <DartMeasurement name="ImageError Minimum" type="numeric/double">10</DartMeasurement>
2803: <DartMeasurement name="ImageError Maximum" type="numeric/double">22</DartMeasurement>
2803: <DartMeasurement name="ImageError Mean" type="numeric/double">11.9552</DartMeasurement>
2803: <DartMeasurementFile name="DifferenceImage" type="image/png">/Users/matt.mccormick/bin/ITK-GCC-Release/Testing/Temporary/ITKSuperPixel/itkSLICImageFilterTestOutput1.png.diff.png</DartMeasurementFile>
2803: <DartMeasurementFile name="BaselineImage" type="image/png">/Users/matt.mccormick/bin/ITK-GCC-Release/Testing/Temporary/ITKSuperPixel/itkSLICImageFilterTestOutput1.png.base.png</DartMeasurementFile>
2803: <DartMeasurementFile name="TestImage" type="image/png">/Users/matt.mccormick/bin/ITK-GCC-Release/Testing/Temporary/ITKSuperPixel/itkSLICImageFilterTestOutput1.png.test.png</DartMeasurementFile>
2803: <DartMeasurement name="BaselineImageName" type="text/string">itkSLICImageFilterTest1.png</DartMeasurement>
1/1 Test #2803: itkSLICImageFilterTest1 ..........***Failed    0.04 sec

❯ c++ --version
Apple clang version 15.0.0 (clang-15<IP_ADDRESS>)
Target: arm64-apple-darwin23.3.0
Thread model: posix
InstalledDir: /Library/Developer/CommandLineTools/usr/bin

Diff image:

@blowekamp any ideas?

The compared image is of the resulting labels, so that magnitude of the difference is not significant. The number of pixel differences is set to 25. The difference looks like mostly minor boundary differences and not significant. Perhaps due to accumulation error, in an iterative algorithm?

I can't seem to reproduce the issue with clang 14.0.0 and I am unable to upgrade at this time. Perhaps this issue is just with clang 15.0
There is already a second base committed of intel 32-bit instructions (957f35d2ecf93c0e58b86011fcea784b009ff104). Perhaps the appropriate solution is to add another baseline?

Thanks for the feedback. Yes, agreed, @blowekamp . New baseline added in #4515.


No Map Received

Hallo, I am trying cartographer now, and I am quite new to this, but when I tried it there is no map received, here is I attach the file of my urdf, lua, launch, tf_tree, rqt_graph and the view of my rviz
https://drive.google.com/drive/folders/1Ml__KQQvpBj8CJzIfnc7z8kbsa7jeLrI
and I also run all of the tf using comman line, because when I put it on the launch file it doesn't work, so I run
rosrun tf static_transform_publisher 0 0 0 0 0 0 base_link velodyne 10
rosrun tf static_transform_publisher 0 0 0 0 0 0 map base_link 100
those two tf, I run them via the command line
I think the problem is because the scan/velodyne_points topic don't connect to the cartographer node, but I don't know how to fix it, anyone can help me? Thank you

Could be also a remapping that is required, as written here: https://github.com/cartographer-project/cartographer_ros/issues/1414#issuecomment-710109412
Closing for inactivity.


updated install.sh and added instructions

Coverage remained the same at 78.241% when pulling d0f6d619f03b1a787722d9447f3ed5bdd3f3bdcc on update-man-jclc into 7f80b0bd5428b945067343ea1edb67eade95d333 on master.

Coverage remained the same at 78.241% when pulling d0f6d619f03b1a787722d9447f3ed5bdd3f3bdcc on update-man-jclc into 7f80b0bd5428b945067343ea1edb67eade95d333 on master.

The URL in INSTALL.sh is fixed to 0.6.3.
Would something like this work: http://stackoverflow.com/questions/24987542/is-there-a-link-to-github-for-downloading-a-file-in-the-latest-release-of-a-repo#comment49193423_26738019

@juvester No, because it's nearly impossible to parse json in bash without additional dependencies. The fixed version number isn't really problem, because user is immediately asked if they want to update  to the newer version if it's available.

@Salmela Would the command in Edit2 also return pre-releases?

Yeah. I didn't take the pre-releases into account. But it's easy to fix because the latest release is never pre-release so the below line would work.
curl -s https://api.github.com/repos/tmc-cli/tmc-cli/releases/latest | grep -e '"browser_download_url".*/tmc"' | head -n 1 | cut -d '"' -f 4

BTW @jclc could you merge my #376 pull request and create release.
I am not available for about a week.

Coverage remained the same at 81.145% when pulling 21bba37963786b88456d3590a69c96d45a834442 on update-man-jclc into fce02a037f64b99e24ca7eaa483f7d2427a1f208 on master.

Install script should work fine now.

Coverage remained the same at 81.145% when pulling 1262a150aa7f39da590dc73efa3425b92058fbba on update-man-jclc into fce02a037f64b99e24ca7eaa483f7d2427a1f208 on master.

Coverage remained the same at 81.145% when pulling 294b062e08731266cdb7a34522521d6c4d570ca5 on update-man-jclc into fce02a037f64b99e24ca7eaa483f7d2427a1f208 on master.

Coverage remained the same at 81.145% when pulling c4c5a0df1a057a61fc48221dabffc2d44de2d065 on update-man-jclc into fce02a037f64b99e24ca7eaa483f7d2427a1f208 on master.

LGTM.


Race on temporary file in .cache/buildstream/cas/

See original issue on GitLab
In GitLab by [Gitlab user @aevri] on Mar 13, 2019, 13:36
Summary
When building a large project, where the cache volume gets near full, there is a crash when trying to get the file size of a since-removed temporary file in the cascache directory.
Steps to reproduce
Contrive it such that a CacheSizeJob is running at the same time as there is a temporary file in the cascache directory.
Such a file is created whenever BuildQueue has a finished job - the BuildQueue will update the cache size by adding the finished artifact size. Sometimes the CacheSizeJob will notice the temporary file that CASQuota._write_cache_size() uses to atomically update the size file, and try to read it after it is deleted.
What is the current bug behavior?
As reported by [Gitlab user @BenjaminSchubert]:
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/_scheduler/jobs/job.py", line 425, in _child_action
result = self.child_process()  # pylint: disable=assignment-from-no-return
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/_scheduler/jobs/cachesizejob.py", line 31, in child_process
return self._casquota.compute_cache_size()
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/_cas/cascache.py", line 1065, in compute_cache_size
new_cache_size = self.calculate_cache_size()
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/_cas/cascache.py", line 1080, in calculate_cache_size
return utils._get_dir_size(self.casdir)
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/utils.py", line 631, in _get_dir_size
return get_size(path)
File "/home/bschubert/.local/lib/python3.6/site-packages/buildstream/utils.py", line 624, in get_size
total += f.stat(follow_symlinks=False).st_size
FileNotFoundError: [Errno 2] No such file or directory: '/home/bschubert/.cache/buildstream-cache/buildstream/cas/tmpfa6k35pq'

What is the expected correct behavior?
No crashing :)
Relevant logs and/or screenshots
Possible fixes

Using the sibling tmp directory for the temporary file, instead of the cas directory.

We also need to make sure that this isn't a symptom of a larger problem of data races.
Other relevant information

BuildStream version affected: /milestone %BuildStream_v1.x

In GitLab by [Gitlab user @aevri] on Mar 13, 2019, 13:36
mentioned in merge request !1226

In GitLab by [Gitlab user @aevri] on Mar 13, 2019, 18:06
mentioned in merge request !1227

In GitLab by [Gitlab user @aevri] on Mar 14, 2019, 09:42
mentioned in merge request !1229

In GitLab by [Gitlab user @aevri] on Mar 15, 2019, 09:15
Given that my "merge-request assertion" !1229 passes tests, I think my understanding of the scheduling is correct, so I'm confident that there aren't more races on the cas/cache_size file.
I haven't seen evidence of a larger problem of data races, so I think that point is now addressed.

In GitLab by [Gitlab user @aevri] on Mar 21, 2019, 16:39
Everything has landed now, case closed.

In GitLab by [Gitlab user @aevri] on Mar 21, 2019, 16:39
closed


Add support for multiple payment trigger URLs

Allowing at least 2 would be nice. Perhaps we can do this with tabs in the UI?

Would these have their own post data as well?

Yeah so the idea is to switch that part of the UI to use tabs where they could have a tab for each post data + url combo.


Error waiting for EKS Node Group to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred

Description
I have made all the changes; however, despite my best efforts, I am still getting the same error.  Sometimes, there is no error it is just in a never-ending loop.
error waiting for EKS Node Group (eks-bayview-dev:bayview-20220903203234016200000001) to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred

My main class is the following:
provider "aws" {
  region = local.region
}

locals {
  name            = "${var.cluster_name}-${terraform.workspace}"
  cluster_version = var.cluster_version
  region          = var.region
  environment     = terraform.workspace

  tags = {
    cluster_name  = local.name
    environment   = local.environment
    BitBucket     = "bayview-asset-management"
    BitBucketRepo = "infra"
  }
}

module "eks" {
  source  = "terraform-aws-modules/eks/aws"
  version = "~> 18.0"

  cluster_name                    = local.name
  cluster_version                 = local.cluster_version
  cluster_endpoint_private_access = true
  cluster_endpoint_public_access  = true
  enable_irsa                     = true

  create_cni_ipv6_iam_policy = true

  cluster_addons = {
    # Note: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html#fargate-gs-coredns
    coredns = {
      resolve_conflicts = "OVERWRITE"
    }
    kube-proxy = {}
    vpc-cni = {
      resolve_conflicts = "OVERWRITE"
      service_account_role_arn = module.vpc_cni_irsa.iam_role_arn
    }
  }

  cluster_encryption_config = [{
    provider_key_arn = aws_kms_key.eks.arn
    resources        = ["secrets"]
  }]

  vpc_id     = var.vpc_id
  subnet_ids = var.private_subnets

  # You require a node group to schedule coredns which is critical for running correctly internal DNS.
  # If you want to use only fargate you must follow docs `(Optional) Update CoreDNS`
  # available under https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html

  eks_managed_node_group_defaults = {
    disk_size                  = 20
    instance_types             = ["m5.large"]
    ami_type                   = "AL2_x86_64"

    # We are using the IRSA created below for permissions
    # This is a better practice as well so that the nodes do not have the permission,
    # only the VPC CNI addon will have the permission
    iam_role_attach_cni_policy = true
  }

  eks_managed_node_groups = {
    bayview = {
      subnet_ids     = var.private_subnets
      min_size       = 2
      max_size       = 5
      desired_size   = 2
      instance_types = [var.instance_type]

      labels = {
        Example     = "managed_node_groups"
        GithubRepo  = "terraform-aws-eks"
        GithubOrg   = "terraform-aws-modules"
        Environment = terraform.workspace
      }
      tags = local.tags
    }
  }

  # Fargate profiles
  # https://docs.aws.amazon.com/eks/latest/userguide/fargate-profile.html
  fargate_profiles = {
    default = {
      name = "default"
      selectors = [
        {
          namespace = "bftg-backend"
          labels = {
            Application = "bftg-backend"
          }
        },
        {
          namespace = "default"
          labels = {
            WorkerType = "fargate"
          }
        }
      ]

      tags = merge(
        local.tags,
        {
          Profile = "default"
        }
      )

      timeouts = {
        create = "20m"
        delete = "20m"
      }
    }

    secondary = {
      name = "secondary"
      selectors = [
        {
          namespace = "default"
          labels = {
            Environment = terraform.workspace
            GithubRepo  = "infra"
            GithubOrg   = "bayview-asset-management"
          }
        }
      ]

      # Using specific subnets instead of the subnets supplied for the cluster itself
      subnet_ids = var.private_subnets

      tags = merge(
        local.tags,
        {
          Profile = "secondary"
        }
      )
    }
  }

  tags = local.tags
}

resource "aws_kms_key" "eks" {
  description             = "EKS Secret Encryption Key"
  deletion_window_in_days = 7
  enable_key_rotation     = true

  tags = local.tags
}

module "vpc_cni_irsa" {
  source  = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks"

  role_name             = "${local.name}-vpc_cni"
  attach_vpc_cni_policy = true
  vpc_cni_enable_ipv4   = true

  oidc_providers = {
    main = {
      provider_arn               = module.eks.oidc_provider_arn
      namespace_service_accounts = ["kube-system:aws-node"]
    }
  }

  tags = local.tags
}

Versions

Module version [Required]: ~> 18.0

Terraform version: 1.1.9

Provider version(s):

Reproduction Code [Required]

Steps to reproduce the behavior:

Yes, I am using workspaces

Yes, I have cleared the cached and the error still the same

terraform init
terraform plan
terraform apply
Expected behavior

Generate a successful EKS with a eks managed nodegroup and fargate
Actual behavior
The following error:
to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred

Terminal Output Screenshot(s)

The application either generates the error or is constanlty
Additional context

@mfolivas check the vpc_cni role that was created policy - i found it was missing permissions, thus causing nodes to not be added.

hmm, checking the @oc-tdoron , I have the following configuration:
{
    "Statement": [
        {
            "Action": [
                "ec2:UnassignPrivateIpAddresses",
                "ec2:ModifyNetworkInterfaceAttribute",
                "ec2:DetachNetworkInterface",
                "ec2:DescribeTags",
                "ec2:DescribeNetworkInterfaces",
                "ec2:DescribeInstances",
                "ec2:DescribeInstanceTypes",
                "ec2:DeleteNetworkInterface",
                "ec2:CreateNetworkInterface",
                "ec2:AttachNetworkInterface",
                "ec2:AssignPrivateIpAddresses"
            ],
            "Effect": "Allow",
            "Resource": "*",
            "Sid": "IPV4"
        },
        {
            "Action": "ec2:CreateTags",
            "Effect": "Allow",
            "Resource": "arn:aws:ec2:*:*:network-interface/*",
            "Sid": "CreateTags"
        }
    ],
    "Version": "2012-10-17"
}

I will be checking with my client and make sure that I have all access.

I think this is related to issue 1977.
Do you happen to run an "older" version of terraform-aws-eks? The reason I'm asking, and the reason I thing it's related to 1977, is that I got a very similar error message (Except I got a bit more info in the message that pointed me at the Autoscaling group created to house the EKS Node Group). Looking at the ASG, I noticed that under activity, it failed the creation of the EC2 instances because the instances have the instance tags in IMDS enabled. Having tags in the instance metadata service poses further restrictions on the allowed characters in the tags, compared to just having them as regular instance tags. Node groups deployed by EKS has some of these invalid tags applied.
historically, AWS has handled it gracefully by simply not adding those tags to the instances (see 1977), but I guess something must have changed recently on the backend to make it fail instead of... not failing...
The reason I'm asking if you use an old version of terraform-aws-eks is that I believe it used to come with instance_metadata_tags = "enabled" by default - I do not remember which version this was changed in. Your config does not mention instance_metadata_tags, so I believe it's using a default value. You can check this by looking at the ASG created in AWS after it fails, it should show if instance metadata in tags is enabled.
You can explicitly disable it by setting this in your node group config or default node group config
metadata_options = {
   instance_metadata_tags      = "disabled"
 }

I had it set to enabled, which is why it failed for me. Setting it to "disabled" for me fixed my problem ;)

I was able to deploy the cluster with managed nodes (version 18.29.0), 7 days after the deployment, the nodes become NotReady.
I dug a bit and found that pods aws-node were in CrashLoopBackOff with the log "Waiting IPAM-D". The logs within the pod are showing 403 when requesting an IP for ENI.
{"level":"error","ts":"2022-09-28T14:06:07.902Z","caller":"aws-k8s-agent/main.go:27","msg":"Initialization failure: failed to allocate one IP addresses on ENI eni-xxxxxxxxxxxx, err: UnauthorizedOperation: You are not authorized to perform this operation.  Encoded authorization failure message: REDACTED \n\tstatus code: 403, request id: xxxxxxxxx"}

I added the permissions given by @mfolivas above to the VPC-CNI role which solved my issue.

I added the permissions given by @mfolivas above to the VPC-CNI role which solved my issue.

There are two ways that VPC-CNI permissions can be provided and caveats for new clusters or IPv6 clusters:

Permissions can be provided either via the node IAM role or via the VPC-CNI addon configuration
You cannot create a new cluster with permissions passed only via the VPC-CNI because pods will never be assigned due to VPC-CNI dameonset unable to deploy due to lack of permissions on the node (chicken vs. the egg problem). If you want to avoid having these broad permissions available on the node and available for other pods to utilize, you must first provision the cluster with the permissions on the node IAM role and the VPC-CNI addon and after the VPC-CNI daemonsets deploy successfully, you can remove the permissions from the node IAM role
For IPv4 clusters, AWS provides a managed IAM policy AmazonEKS_CNI_Policy, but for IPv6 they provide the required permissions and users have to create the policy. In this module, for IPv4 we use the AWS managed policy and provide an equivalent for IPv6 using the permissions provided by AWS

Hopefully that helps clarify permissions. By default, if you are creating an IPv4 based cluster, the module will attach the AmazonEKS_CNI_Policy AWS managed policy to the node IAM role created by the module, otherwise the cluster will not provision successfully. If you provide a custom IAM role, you will need to ensure the role has these permissions

Thanks for the clarification !
When you mention:

Permissions can be provided either via the node IAM role or via the VPC-CNI addon configuration

Are you referring to this addon ? https://github.com/terraform-aws-modules/terraform-aws-eks/blob/ad6b2e2ab77d35d86028d69fea886f7148db7bb8/docs/irsa_integration.md#irsa-integration
Thanks

Somewhat, yes. You can create an IAM role for service accounts via https://github.com/terraform-aws-modules/terraform-aws-iam/tree/master/modules/iam-role-for-service-accounts-eks for the VPC-CNI which will have the necessary permissions. You can then pass that ARN into the addon config like this to have the addon use that IRSA role for permissions
So to clarify - we are not providing the AWS VPC-CNI addon since this is provided in EKS clusters by default, we are just providing IAM permissions through either the node IAM role(s) and/or the addon itself.

OK thanks.
I noticed that the variable vpc_cni_enable_ipv4 was set to false. Wouldn't be enough though ? Would it be enough?

You can refer to that same example https://github.com/terraform-aws-modules/terraform-aws-eks/blob/ad6b2e2ab77d35d86028d69fea886f7148db7bb8/examples/eks_managed_node_group/main.tf#L407-L423
The iam-role-for-service-accounts sub-module provides policies for a number of popular K8s addons. Users need to toggle on which addon they are creating the IRSA role for in order for the correct permissions to be attached (one role definition can stamp out multiple different IRSA roles for each use case via a boolean flag)

Run into the same issue with the ipv4 IP family
`
module "eks" {
source  = "terraform-aws-modules/eks/aws"
version = "18.30.2"
cluster_name    = local.cluster_name
cluster_version = "1.23"
vpc_id     = var.vpc_id
subnet_ids = var.vpc_private_subnets_ids
cluster_ip_family = "ipv4"
cluster_addons = {
# Note: https://docs.aws.amazon.com/eks/latest/userguide/fargate-getting-started.html#fargate-gs-coredns
coredns = {
resolve_conflicts = "OVERWRITE"
}
kube-proxy = {}
vpc-cni = {
resolve_conflicts        = "OVERWRITE"
service_account_role_arn = module.vpc_cni_irsa.iam_role_arn
}
aws-ebs-csi-driver = {
resolve_conflicts = "OVERWRITE"
}
}
cluster_encryption_config = [{
provider_key_arn = aws_kms_key.eks.arn
resources        = ["secrets"]
}]
cluster_security_group_additional_rules = {
egress_nodes_ephemeral_ports_tcp = {
description                = "To node 1025-65535"
protocol                   = "tcp"
from_port                  = 1025
to_port                    = 65535
type                       = "egress"
source_node_security_group = true
}
}
node_security_group_additional_rules = {
ingress_allow_access_from_control_plane = {
type                          = "ingress"
protocol                      = "tcp"
from_port                     = 9443
to_port                       = 9443
source_cluster_security_group = true
description                   = "Allow access from control plane to webhook port of AWS load balancer controller"
}
egress_mysql = {
description = "Aurora connection"
protocol    = "tcp"
from_port   = 3306
to_port     = 3306
type        = "egress"
cidr_blocks = var.database_subnets_cidr_blocks
}
}
eks_managed_node_group_defaults = {
ami_type       = "AL2_x86_64"
disk_size      = 20
instance_types = [var.core_instance_type]
iam_role_attach_cni_policy = true

}
eks_managed_node_groups = {
default = {
name         = "eks-${var.project_prefix}-${var.environment}"
desired_size = var.core_instance_desired_size
min_size     = var.core_instance_min_size
max_size     = var.core_instance_max_size
  instance_types = [var.core_instance_type]
  capacity_type  = "ON_DEMAND"

  labels = {
    Environment = var.environment
  }

  tags = {
    Environment = var.environment
    Terraform   = "True"
  }

  update_config = {
    max_unavailable_percentage = 50
  }

  metadata_options = {
    http_endpoint               = "enabled"
    http_tokens                 = "required"
    http_put_response_hop_limit = 2
    instance_metadata_tags      = "disabled"
  }

  iam_role_additional_policies = [
    "arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy",
    "arn:aws:iam::aws:policy/service-role/AmazonEBSCSIDriverPolicy"
  ]
}

}
fargate_profiles = {
default = {
name            = "default"
create_iam_role = true
selectors = [
{
namespace = "services"
}
]
tags = {
Environment = var.environment
Terraform   = "True"
Fargate     = "True"
}
timeouts = {
create = "10m"
delete = "10m"
}
  iam_role_additional_policies = [
    "arn:aws:iam::aws:policy/CloudWatchAgentServerPolicy",
    "arn:aws:iam::aws:policy/AmazonEKSServicePolicy",
    "arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryReadOnly"
  ]
}

}
cluster_endpoint_private_access      = true
cluster_endpoint_public_access_cidrs = ["<IP_ADDRESS>/0"]
cluster_endpoint_public_access       = true
manage_aws_auth_configmap = true
aws_auth_roles            = local.admin_role_map
enable_irsa = true
}
module "vpc_cni_irsa" {
source  = "terraform-aws-modules/iam/aws//modules/iam-role-for-service-accounts-eks"
version = "5.4.0"
role_name_prefix      = "VPC-CNI-IRSA"
attach_vpc_cni_policy = true
vpc_cni_enable_ipv4   = true
oidc_providers = {
main = {
provider_arn               = module.eks.oidc_provider_arn
namespace_service_accounts = ["kube-system:aws-node"]
}
}
}
`

same issue appears with me also with EKS managed nodes: NotReady

same issue appears with me also with EKS managed nodes: NotReady i don't use metadata block and VPC CNI policy is attached to nodes i have opened AWS support ticket
in the conditions i see:
container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized
╷
│ Error: error waiting for EKS Node Group (nginx333:blue-2022102307072746890000001f) to create: unexpected state 'CREATE_FAILED', wanted target 'ACTIVE'. last error: 1 error occurred:
│ 	* i-0a52645ed41c3b232: NodeCreationFailure: Unhealthy nodes in the kubernetes cluster
│
│
│
│   with module.eks.module.eks_managed_node_group["blue"].aws_eks_node_group.this[0],
│   on .terraform/modules/eks/modules/eks-managed-node-group/main.tf line 269, in resource "aws_eks_node_group" "this":
│  269: resource "aws_eks_node_group" "this" {

after some tests its a DNS problem but i could not understand the problem from AWS side, the kubelet logs say that it can not resolve HOST. I switched AWS account and it works.

@gfrid could you provide some more context and detail about what you changed to fix the issue by "switching accounts"? I'm encountering the same error:

NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni config uninitialized

Using eks blueprints, but everything was working until I switched to using it to create a launch_template..


updated prgenv-pgi; deleted workaround in gpu_direct_acc.py

there is no issue related to this pull request

Please tag accordingly and put this PR in the right project and milestone.

@jenkins-cscs retry kesch

@teojgo @ajocksch I think CI on Kesch is expected to fail for the default PrgEnv-pgi.

@teojgo Can you fix the conflicts? This is ready to be merged otherwise.

Codecov Report

Merging #348 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #348   +/-   ##
=======================================
  Coverage   91.12%   91.12%
=======================================
  Files          68       68
  Lines        8244     8244
=======================================
  Hits         7512     7512
  Misses        732      732

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 2018a71...2a2e7f5. Read the comment docs.


Health async interfaces poc

Draft for adding a new IAsyncHealthContributor with CheckHealthAsync() method. Steeltoe already supports adding IHealthContributor implementations in addition to Microsoft HealthCheckRegistrations. In order to be flexible to Steeltoe consumers, who want to continue using IHealthContributor, we want to support IAsyncHealthContributor in addition to the other options.

Closing this as discussed,


[ENH] cython a subset of _range_join_indices and equi join

with cython 3.0 we can use python typing within cython and still get some perf gains. This would be beneficial to us within the _range_indices section, where we have to compare within groups. instead of broadcasting (which could be costly for large datasets) we can iterate within each group, get the earliest position and just slice to get the matches. we wouldnt need to broadcast, we can break out early, and we can get the perf of C within the for loop.

Just wondering, @samukweku, given that you've already used numba here, is this doable using numba instead of cython?

Already have a numba implementation. Going this route with cython/rust for the specific points where there is a for loop and no cover with numpy. I have also had issues with debugging numba in some cases and also Mac/Linux environments. Also because cython/rust is precompiled I/user won't need to worry about warmup.still tentative on it considering the team's reluctance to cython/rust because of complexity.


Accuracy_Tester

PR Description 📜
This is an Accuracy tester game that tests the players accuracy.
Fixes #3041

Mark the task you have completed ✅

[ *] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ *] I have performed a self-review of my own code or work.
[ *] I have commented my code, particularly in hard-to-understand areas.
[ *] My changes generates no new warnings.
[ *] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ *] I have added screenshot for website preview in assets/images
[ *] I have added entries for my game in main README.md
[ *] I have added README.md in my folder
[ *] I have specified the respective issue number for which I have requested the new game.

Thank you soo much for contributing to our repository 💗

Thank you @frymanst ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

Thank you  @frymanst , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


Column ordering not saved alongside custom filters

As already commented here (https://github.com/dbeaver/dbeaver/issues/1569#issuecomment-513507363) column ordering is not saved alongside custom filters.
saved-data-filter.xml doesn't change whatsoever upon changing column ordering from ASC to DESC, so this is maybe less a bug report than a feature request :)

hi @t-o-o-m ,
cannot reproduce it with PostgreSQL. What is your database?

Hi,
doesn't work for me with PostgreSQL and MSSQL. How would a DESC-ordering be reflected in saved-data-filter.xml or is it saved somewhere else? I'm using 7.0.2 on Windows; installed via Chocolatey.

I just ran into this same issue with DBeaver 7.0.4 using PostgreSQL 10. Steps to reproduce:

Use the "Customize filters..." button to set a column to be sorted in descending order (arrow pointed down).
Use the "Save filter settings" button to save the filter settings.
Close and reopen DBeaver.
Observe that the column is sorted in ascending order (arrow pointed up).

It's frustrating to not be able to save the sort order of a column along with the filter settings. Thank you very much in advance for taking a look at this!

thanks for the bug report
@austin-beer , thanks for clear steps

Fixed

verified


Zigbee2MQTT Ingress not working

The problem
When I try to open the Z2MQTT ingress it just shows me blank page and this error message in the DevTools console:
Uncaught SyntaxError: Invalid or unexpected token (at index-856ac473.js:1:11982)
I don't know if this is an issue on the side of Z2MQTT or the Cloudflared-Addon because it just stopped working after an update and the ingress is working locally, but not through the cloudflare tunnel.
What version of Cloudflared has the issue?
5.1.9
What was the last working version of Cloudflared?
No response
What type of installation are you running?
Home Assistant OS
Add-on YAML Configuration
external_hostname: ha.XXX.XX
additional_hosts: []

Anything in the logs that might be useful for us?
No response
Steps to reproduce the issue

Install Zigbee2MQTT
Install Cloudflared-Addon
Set up Cloudflared-Addon
Try to open the Z2MQTT ingress through the tunnel

Additional information
No response

Thanks for raising this. Just to clarify: Did this work previously and if so, what did you change / update and from which versions?

I don't know if this is an issue on the side of Z2MQTT or the Cloudflared-Addon because it just stopped working after an update and the ingress is working locally, but not through the cloudflare tunnel.

FYI, I am currently using the latest Cloudflare edge version and zigbee add-on version 1.37.1-1 without any problems.

I've tried it on multiple devices, so caching shouldn't be the issue. The other ingresses like VS Code work via Cloudflared, only Z2MQTT doesn't. I've changed nothing manually and only applied the latest updates of the Cloudflared- and the Z2MQTT-Addons.
My Z2MQTT-Addon is also on version 1.37.1-1 and the Front-End there is set to the default settings.
I updated Z2MQTT from 1.37.0 to 1.37.1 around 4 days ago and last week from 1.36.1 to 1.37.1. The last time I updated cloudflared was on the 26th of April from 5.1.7 to 5.1.9.

The issue seems to have been fixed with the newest version of the add-on :)


PDF version support question

What version of PDF does pdf.js support (1.7 / 2.0) ? Is there any documentation and plans regarding version support ?

As far as I know we provide support until and including PDF 1.7; see https://github.com/mozilla/pdf.js/wiki/Enumeration-Assignments-for-the-Telemetry-Histograms. However, since PDF 2.0 is backwards compatible, most if not all functionality should just work, perhaps only the newly added functionality is not yet available.


not parse body if already parsed

This is fix for hang-bug, when raw-body is used twice in one request. see: https://github.com/stream-utils/raw-body/issues/57
For body-parser (https://expressjs.com/en/resources/middleware/body-parser.html) that one of de facto standards in Express.

Thanks. The only thing we have to consider is that req.body can be another type. However, in almost all cases it is the body parsed by body-parser. At this time let's choose to follow the standard.


Layout with multiple MaterialButtons: Animation framerate drops considerably on Nexus 6P

Issue description
I am observing a considerable animation lag on the Nexus 6P on the ripples of the MaterialButton if there are a couple of them on the scene.
I do not know if other devices are affected, but I am not observing this in the emulator: no matter how much buttons I add to the scene, the emulator appears to keeps animating all the ripples smoothly without any noticeable performance difference.
I initially thought this was due to the complexity of the layout (nested rows/columns with buttons) but, in an attempt to narrow down the issue, after extracting the relevant code into a separate project and simplifying the layout, I noticed that it is still not animating as smooth as it ought to.
Steps to reproduce
I have added code below that demonstrates the matter. It initially shows a single button: holding your finger will animate the ripple smoothly, as expected.
After tapping, there will be 18 buttons on the scene (I added more so the issue is significantly observable).
Touch and holding any button will show a ripple that seems to skip a few frames and the animation feels choppy.
Code
import 'package:flutter/material.dart';

void main() {
  runApp(new FramerateDroppingApp());
}

class FramerateDroppingApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return new MaterialApp(
      title: 'Testing',
      theme: new ThemeData(
        primarySwatch: Colors.green,
      ),
      home: new FramerateDropping(),
    );
  }
}

class _FramerateDroppingState extends State<FramerateDropping> {
  bool _showMore = false;

  @override
  Widget build(BuildContext context) {
    return new Scaffold(
      appBar: new AppBar(
        title: new Text("TEST"),
      ),
      body: _showMore ? _createNineChildren() : _createOneChild(),
    );
  }

  void _flickAll() {
    setState( () {
      _showMore = !_showMore;
    } );
  }

  Widget _createChild() {
    return new MaterialButton(
        color: Colors.green,
        elevation: 4.0,
        minWidth: 32.0,
        height: 32.0,
        onPressed: _flickAll,
        child: new Text( 'Foo' ),
    );
  }

  List<Widget> _createMore() {
    return [
      _createChild(),
      _createChild(),
      _createChild(),

      _createChild(),
      _createChild(),
      _createChild(),

      _createChild(),
      _createChild(),
      _createChild(),

      _createChild(),
      _createChild(),
      _createChild(),

      _createChild(),
      _createChild(),
      _createChild(),

      _createChild(),
      _createChild(),
      _createChild(),
    ];
  }

  Widget _createOneChild() {
    return _createChild();
  }

  Widget _createNineChildren() {
    return new Column( children: _createMore() );
  }
}

class FramerateDropping extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => new _FramerateDroppingState();
}

Can you confirm if you are using debug mode or release mode?

I can confirm this happens in both modes.

If someone is interested in debugging, the first step is probably to turn on showPerformanceOverlay to get a sense as to if this is time spent on the Dart thread or the Rasterizer/GPU thread. I strongly suspect it's the latter.  MaterialApp has several first-line-of-defense perf debugging flags:
https://docs.flutter.io/flutter/material/MaterialApp-class.html
After that we'll escalate to taking a trace from observatory or using flutter trace which can tell us how the time is being spent on those threads.

I tested this today on the master branch, and it animates much smoother on the Nexus 6P now.


Add pattern requirement for mariadb db/user name.

The issue resolved by this Pull Request:
Resolves #207
Description of your changes:
CRD validation now takes into account the regexes used to validate identifiers for mariadb user/db names
Testing instructions

deploy dspo
deploy dspa with invalid user/db names for mariadb spec, example:

spec:
  database:
    mariaDB:
      pipelineDBName: test-fail
      username: test-fail

you should see an error reported from api server
deploy with valid pipeline db and user names, it should now work

spec:
  database:
    mariaDB:
      pipelineDBName: test_pass
      username: test_pass

Try different combinations

NOTE:  that if a user had deployed a DSPA with invalid db identifier names (e.g: "test-fail"), then updated DSPO, DSPO will report errors for this DSPA until the offending DSPA invalid field is updated or removed, example:
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:326
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/opt/app-root/src/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.13.0/pkg/internal/controller/controller.go:234
2023-09-08T18:03:58Z DEBUG DataSciencePipelinesApplication Reconciler called. {"namespace": "dspa1", "dspa_name": "sample"}
2023-09-08T18:03:58Z ERROR Reconciler error {"controller": "datasciencepipelinesapplication", "controllerGroup": "datasciencepipelinesapplications.opendatahub.io", "controllerKind": "DataSciencePipelinesApplication", "DataSciencePipelinesApplication": {"name":"sample","namespace":"dspa1"}, "namespace": "dspa1", "name": "sample", "reconcileID": "2b0a4ca3-96b7-4a50-86a2-9cece3448e56", "error": "DataSciencePipelinesApplication.datasciencepipelinesapplications.opendatahub.io \"sample\" is invalid: spec.database.mariaDB.pipelineDBName: Invalid value: \"`te-st`\": spec.database.mariaDB.pipelineDBName in body should match '^[a-zA-Z0-9_]+$'"}

Checklist

[x] The commits are squashed in a cohesive manner and have meaningful messages.
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has manually tested the changes and verified that the changes work

A new image has been built to help with testing out this PR: quay.io/opendatahub/data-science-pipelines-operator:pr-325
An OCP cluster where you are logged in as cluster admin is required.
To use this image run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines-operator.git
cd data-science-pipelines-operator/
git fetch origin pull/325/head
git checkout -b pullrequest 3ae43186278a7b84a3c4fd0ada8cfdda0c71fc32
make deploy IMG="quay.io/opendatahub/data-science-pipelines-operator:pr-325"

More instructions here on how to deploy and test a Data Science Pipelines Application.


Search functionality is not working after refreshing the page

Steps to reproduce:

open Dashboard page
observe search results
refresh the page with F5

Expected results:

search is working, results are displayed

Actual results:

search is not working, results are not displayed
call to Search service is failing with the error (see below)
user id is not included to Search call (see below)

Verified


FileNotFoundError: No such file or directory: 'results/pretrained_models/niqe_model.mat'

Hi Lorna,
It seems like the niqe_model can not be initialized for the first time without a default niqe_model.mat.
Traceback (most recent call last):
  File "/home/khoa/dev/Real-ESRGAN/train_realesrnet.py", line 475, in validate
    niqe = niqe_model(sr)
  ...
FileNotFoundError: [Errno 2] No such file or directory: 'results/pretrained_models/niqe_model.mat'

I have tried to add a default niqe_model.mat myself before training, then the issue seems to have been solved.
Best regards,
Dante

Which command does this appear when executing?

Hi Lorna,
It's line 94 in train_realesrnet.py, for example.
When initializing the NIQE model, it needs to be passed niqe_model_path.
# Create an IQA evaluation model
    niqe_model = NIQE(config.upscale_factor, config.niqe_model_path)

In the config file, the niqe_mode_path has been set as "results/pretrained_models/niqe_model.mat".
In the original repo, this niqe_model.mat file does not exist, and then, throw the exception.
Traceback (most recent call last):
  File "/home/khoa/dev/ASRGAN/train_asrnet.py", line 508, in <module>
    main()
  File "/home/khoa/dev/ASRGAN/train_asrnet.py", line 109, in main
    _ = validate(
  File "/home/khoa/dev/ASRGAN/train_asrnet.py", line 475, in validate
    niqe = niqe_model(sr)
  File "/home/khoa/anaconda3/envs/asrgan/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
    return forward_call(*input, **kwargs)
  File "/home/khoa/dev/ASRGAN/utils/image_metrics.py", line 1569, in forward
    niqe_metrics = _niqe_torch(
  File "/home/khoa/dev/ASRGAN/utils/image_metrics.py", line 1516, in _niqe_torch
    niqe_model = scipy.io.loadmat(niqe_model_path)
  File "/home/khoa/anaconda3/envs/asrgan/lib/python3.10/site-packages/scipy/io/matlab/_mio.py", line 224, in loadmat
    with _open_file_context(file_name, appendmat) as f:
  File "/home/khoa/anaconda3/envs/asrgan/lib/python3.10/contextlib.py", line 135, in __enter__
    return next(self.gen)
  File "/home/khoa/anaconda3/envs/asrgan/lib/python3.10/site-packages/scipy/io/matlab/_mio.py", line 17, in _open_file_context
    f, opened = _open_file(file_like, appendmat, mode)
  File "/home/khoa/anaconda3/envs/asrgan/lib/python3.10/site-packages/scipy/io/matlab/_mio.py", line 45, in _open_file
    return open(file_like, mode), True
FileNotFoundError: [Errno 2] No such file or directory: 'results/pretrained_models/niqe_model.mat'

I don't seem to have encountered this error before, can you submit a pull request


Show summary of params before starting

It would be very handy if appcenter_upload would show a summary of all the params submitted before starting to work. This would make debugging problems and failures much easier.
Example:
Ran a android lane. Selected Android as OS. Upload failed with "Platform does not match. Expected value: Android. Actual value: iOS". Turns out I had copied over the lane from ios and forgot to change ipa to apk and was also upload an .ipa file. Seeing this output on the command line would have sped up finding this quite a lot.

Thanks for the suggestion we don't consider to do this at the moment.


on iphoneX It represent weird.

When use the modal original It shows normal,but when use this package it seems the modal can not cover the full screen in iPhone X.

you can try to add margin style like this:

Thanks @waterFallFlow


[Feature Request] Docker: root user

Is your feature request related to a problem? Please describe.
The current docker image requires operating as the root user. This is a potential security risk if there's a container escape, as it will then have root access on the host machine. This also gives indiscriminate access to all mounted subdirectories, which may not be 100% desirable.
Describe the solution you'd like
Support Docker's user parameter, hardcode a non-root user in the Dockerfile, or provide env vars for configuring the which user the container runs as.

This would be a great addition, as it would also prevent downloads from the plugins being created as the root user.
Similar discussion about this feature on another project: https://github.com/ipsingh06/seedsync/issues/10

Can confirm that adding user: "1000:1000" (or whatever your specific UID/GID is) to the compose file doesn't work.
Mango ends up unable to start and looping this over and over:
`Mango - Manga Server and Web Reader. Version 0.25.0
The config file /.config/mango/config.yml does not exist. Dumping the default config there.
Unhandled exception: Unable to create directory: '/.config': Permission denied (File::AccessDeniedError)
from usr/share/crystal/src/crystal/system/unix/dir.cr:65:13 in 'mkdir_p'
from usr/share/crystal/src/gc/boehm.cr:110:5 in 'load'
from Mango/src/config.cr:36:5 in '->'
from usr/share/crystal/src/primitives.cr:255:3 in 'start_parse'
from Mango/src/mango.cr:137:1 in '__crystal_main'
from usr/share/crystal/src/crystal/main.cr:110:5 in 'main'
from src/env/__libc_start_main.c:94:2 in 'libc_start_main_stage2'`

This is a potential security risk if there's a container escape, as it will then have root access on the host machine. This also gives indiscriminate access to all mounted subdirectories, which may not be 100% desirable.

Except... That's not how it works...
A container is a self-contained environment.
That's like saying if you have root access on your computer & someone shares a folder with you you'll have root access because you are a root user... Now if you both had the same root username & password that might be true, but most likely you will still have to enter the username & password of root on the other machine to have root access
Imagine the docker like a separate computer that you want to use for a task. It is blank. The DockerFile essentially formats that computer & installs an operating system with the bare minimum for it to do what it's intended to. Once that computer is up it runs what you need, but as soon as it turns off it's back to being as it was formatted in the begining. If you create a Bind Mount you are essentially sharing those locations over the network & the Docker-Compose or Run commands mounts them as local drives in the system. If you create a VOL that's like a USB drive you connect to the computer for it to use.
The docker environment is a completely isolated "Computer" that is connected inside docker on your computer.
As far as the mount directories they have the same access for every user within the container. If you mount it as RO in the compose it's read only, if you mount it as RW in the compose it's read/write, The user logged in has no effect on that.

The docker environment is a completely isolated "Computer" that is connected inside docker on your computer. As far as the mount directories they have the same access for every user within the container. If you mount it as RO in the compose it's read only, if you mount it as RW in the compose it's read/write, The user logged in has no effect on that.

I think you're confusing virtual machines and containers here. Containers do not contain. The fundamental design has not changed significantly since that was published. An OCI container, generally, is in effect a fancy chroot jail on the host system. By sharing the same kernel, container escapes can/have/will expose internal processes without isolation. The use of a container should generally not be treated as a security boundary in the same way that VMs do. There are application kernels with improved isolation capabilities, but that cannot be assumed to always be used.
Container escapes aside, the files written to and read from the volume bind mounts use the same user/group as the user inside the container, and having universal read/write perms, even on a scoped volume bind mount, is not ideal.

Can you provide an example of a container being able to access files not inside a mounted directory? I know there can be issues if you mount the wrong point, but I've never heard of a container being able to access /mnt/f/images/ if it has /mnt/f/docker/container/ as a mount point or it being able to access anything that isn't within the mounted directories. If that were such a big problem I cannot believe they would be used so often in so many places.
From my understanding a container only has access to the points that are mounted to it. No different from a computer not being able to access a USB drive if it's not plugged in or a NAS if it isn't on the same network.


How can I fine-tune the model on some subreddit?

Thank you for this model, amazing results.
I would like to take the pretrained model and fine-tune it on r/advice. Such that it generates responses more similar to conversations in that subreddit.
How should I go about it?

Here is my suggestion -- You might want to extract the subreddit data on your own, and follow our pipeline to create a dataset. Then, loading our model as initialization to fine-tune on the small dataset that you created by you own. However, you can be more creative than this :)


Increase the 5MB limit to 10MB for building apps

Hi @jisqyv, I found the place to change the limit. Can I take this issue? Is there any hidden concern that I might have missed?

It's more complex that just changing the limit in the code.
We put in the limit explicitly.   There is a time limit on connections from
the AppEngine data store.  When that is exceeded, the connection is
closed.    Before we put in that limit there were many more mysterious (to
the users) failures.
It's possible we could expand that to 10 MB, but we should not do this
without a lot of testing.  Part of the timing depends on the speed of the
school's network connection, so testing will be tricky.
== Hal Abelson
<EMAIL_ADDRESS>Prof. of Comp. Sci. and Eng.
MIT Dept. of Elec. Eng. and Comp. Sci.
On Wed, May 4, 2016 at 3:58 AM, E-Hon<EMAIL_ADDRESS>wrote:

Hi @jisqyv https://github.com/jisqyv, I found the place to change the
limit. Can I take this issue? Is there any hidden concern that I might have
missed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/mit-cml/appinventor-sources/issues/700#issuecomment-216771041

Thanks for pointing it out. Anyway, I will be ready to help

As far as I am aware, we are no longer enforcing a 5 MB limit on projects. There is still a hard 10 MB limit imposed by Google App Engine. Closing this issue.


Bower installation doesn't work properly

After the install on $ bower list you can see:
bower ENOTFOUND     Package Google Maps AMD Loader Plugin=googlemaps-amd not found

so the issue is that your username has changed from hamweather to aerisweather and the url is broken in bower.json