README: Credit teozkr

@teozkr Would you like to have a different URL here?

That's fine with me. What's the plan here going forward here (if any), is this intended to be a general purpose replacement for sbtix, or "just" keeping it alive for internal use?

That's fine with me. What's the plan here going forward here (if any), is this intended to be a general purpose replacement for sbtix, or "just" keeping it alive for internal use?

As a company, Natural Transformation is doing minimal work to keep it working for us. Since we have skin in the game, we are happy to become the "official" maintainer of this project. We hope other companies can try it in production.


Closed Source Devices are broken on main website

Prerequisites
Please check the following before posting an issue / bug report.

[x] I am running the latest version of the firmware found HERE
[x] I have checked the documentation HERE and found no answer
[x] I checked to make sure that this issue has not already been filed HERE
[x] I am reporting the issue to the correct repository

Context
Please provide all relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

Firmware Version: 0.7.4
Name of device:
Link to where you purchased the device:
Is this a custom build?:
Operating System:
Browser:

Expected Behavior
Closed source devices on our download page should redirect to the correct page.
Current Behavior
Closed source devices on our download page redirect to the wrong webpage.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.

Go to https://gp2040-ce.info/#/download
Click website for the BentoBox or the Mavercade controllers
URLs are incorrect

Screenshots & Files
Please include any relevant screenshots or files here.  If you are having issues with a board please include images of the front and back of the board.

Fixed, thank you!


Foundation Watch / Npm Start / Gulp Fail

How can we reproduce this bug?
I'm not entirely sure how you may be able to reproduce this bug, that's part of the problem. I'm hoping someone may have already come across it and fixed it.
I am running Windows 10.
I have successfully installed foundation-cli via npm (globally),
and have also tried cloning the zurb-foundation-template repo and running npm install + bower install
Whenever I run foundation watch (foundation-cli) or npm start I get the following output:
c:\foundationTest\testProject>npm start

><EMAIL_ADDRESS>start c:\foundationTest\testProject
> gulp

[17:04:58] Requiring external module babel-core/register
[17:05:01] Using gulpfile c:\foundationTest\testProject\gulpfile.babel.js
[17:05:01] Starting 'default'...
[17:05:01] Starting 'build'...
[17:05:01] Starting 'clean'...
[17:05:01] Finished 'clean' after 43 ms
[17:05:01] Starting '<parallel>'...
[17:05:01] Starting 'pages'...
[17:05:01] Starting 'sass'...
[17:05:01] Starting 'javascript'...
[17:05:01] Starting 'images'...
[17:05:01] Starting 'copy'...
[17:05:03] Finished 'images' after 2.24 s
[17:05:06] Finished 'pages' after 5.56 s
[17:05:06] Finished 'sass' after 5.67 s
[17:05:07] Finished 'copy' after 5.76 s
[17:05:10] Finished 'javascript' after 8.7 s
[17:05:10] Finished '<parallel>' after 8.71 s
[17:05:10] Starting 'styleGuide'...
[17:05:10] Finished 'styleGuide' after 60 ms
[17:05:10] Finished 'build' after 8.82 s
[17:05:10] Starting 'server'...
[17:05:10] Finished 'server' after 75 ms
[17:05:10] Starting 'watch'...
true
[17:05:10] The following tasks did not complete: default, watch
[17:05:10] Did you forget to signal async completion?

npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Will\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "start"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundation-zurb-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs foundation-zurb-template
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls foundation-zurb-template
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\foundationTest\testProject\npm-debug.log

I have completely uninstalled and reinstalled node, npm & git several times. I have tried a variety of different directories.
Every time I do a fresh install I get the same error.
What did you expect to happen?
I expected the gulp watch to run, and for browser-sync to load a copy of the default foundation page in my browser.
What happened instead?
I got the above output. Browser-Sync fails to load, and watch fails to run when files are updated.
The dist folder is successfully created fresh each time, however.
I appreciate that this a problem not so much about foundation, but with the development tools. I have very little experience with gulp, so I am at a bit of a loss on how to correct this error.
I have posted the verbose error log on pastebin
I have also asked this question on the foundation forum
I'd appreciate any advice!

I'm having pretty close the same result. Note that when I do npm start with the default file structure as created by the foundation new install (using the zurb template), it runs without error. However, when I rename the "src" folder and paste in my "src" folder from previous attempts to work with the zurb template, that's when I start generating errors. Trace below:
PS C:\Users\mhair.ICS\documents\websites\foundation6temp.dev> npm start

<EMAIL_ADDRESS>start C:\Users\mhair.ICS\documents\websites\foundation6temp.dev
gulp

[15:18:34] Failed to load external module babel-register
[15:18:34] Requiring external module babel-core/register
[15:18:35] Using gulpfile ~\documents\websites\foundation6temp.dev\gulpfile.babel.js
[15:18:35] Starting 'default'...
[15:18:35] Starting 'build'...
[15:18:35] Starting 'clean'...
[15:18:35] Finished 'clean' after 14 ms
[15:18:35] Starting 'pages'...
[15:18:35] Starting 'sass'...
[15:18:35] Starting 'javascript'...
[15:18:35] Starting 'images'...
[15:18:35] Starting 'copy'...
[15:18:37] Finished 'sass' after 2.64 s
[15:18:38] Finished 'pages' after 3.15 s
[15:18:39] Finished 'copy' after 4.1 s
[15:18:39] 'javascript' errored after 4.47 s
[15:18:39] SyntaxError in plugin 'gulp-babel'
Message:
C:\Users\mhair.ICS\documents\websites\foundation6temp.dev\src.babelrc: Error while parsing JSON - Unexpected ''
[15:18:39] 'build' errored after 4.49 s
[15:18:39] 'default' errored after 4.49 s
[15:18:39] The following tasks did not complete: images
[15:18:39] Did you forget to signal async completion?
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\mhair.ICS\AppData\Roaming\npm\node_modules\npm\bin
\npm-cli.js" "start"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>start: gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script 'gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundation-zurb-template package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs foundation-zurb-template
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls foundation-zurb-template
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\mhair.ICS\documents\websites\foundation6temp.dev\npm-debug.log
PS C:\Users\mhair.ICS\documents\websites\foundation6temp.dev>
It starts off with failure to load an external module, but doesn't identify which. I read elsewhere that this is likely the babel module, so I tried the following install to get rid of that error message.
npm install gulp-babel babel-preset-es2015 --save-dev
It didn't resolve it.
Then further down when it comes to the javascript task, you see "SyntaxError in plugin 'gulp-babel'. My dist folder is built, but there is no app.js in the js folder.
Later it complains about signalling async completion, which I've not seen any instruction for in the installation docs.
So this is pretty much par for the course in my experience on Windows 7. Again I have to ask if this was tested on Windows 7, or Windows in general. I would certainly assume/hope, but....? It could just be my and a number of others Windows configurations, but from what I've seen in many many forums, node/npm on Windows is a rats nest without much hope for consistency. This makes Zurb's dependence on it to be extremely problematic. Even going to "prepros" I found that it choked due to the babel dependency. I will try prepros again since 6.2.1 is supposed to have precompiled ES5 javascript.
Zurb, please chime in here if you have any bones for the poor Windows have nots. It's not a happy scene, and hasn't been all the way along as you know.

@mhair: What are the specific differences between the two src  directories that you swap out? I am not sure about Windows tests, @kball & @rafibomb would be the ones to speak on that.
@mhair, @face0b1101: Can you run gulp -v for me please and paste the results?

@colin-marshall sorry for not replying sooner. Work has me away from my machine, when I can get a moment I'll get back to you.
Off the top of my head I think the version is 1.2.1 for the cli, and 4 beta 2 for the other version. Don't know if that helps.

@colin-marshall, you asked this question on the foundation forum:

@Will what happens when you change the default task to run server and watch in parallel?
// Build the site, run the server, and watch for file changes
gulp.task('default',
gulp.series('build', gulp.parallel(server, watch)));

The answer is, I get the following (very similar) output:
><EMAIL_ADDRESS>start C:\Users\Will\Websites\foundationSites\testProject
> gulp

[16:13:26] Failed to load external module babel-register
[16:13:26] Requiring external module babel-core/register
[16:13:40] Using gulpfile ~\Websites\foundationSites\testProject\gulpfile.babel.js
[16:13:40] Starting 'default'...
[16:13:40] Starting 'build'...
[16:13:40] Starting 'clean'...
[16:13:41] Finished 'clean' after 31 ms
[16:13:41] Starting 'pages'...
[16:13:41] Starting 'sass'...
[16:13:41] Starting 'javascript'...
[16:13:41] Starting 'images'...
[16:13:41] Starting 'copy'...
[16:13:48] Finished 'images' after 7.34 s
[16:13:51] Finished 'pages' after 10 s
[16:13:51] Finished 'sass' after 10 s
[16:13:51] Finished 'copy' after 10 s
[16:13:53] Finished 'javascript' after 13 s
[16:13:53] Starting 'styleGuide'...
[16:13:53] Finished 'styleGuide' after 72 ms
[16:13:53] Finished 'build' after 13 s
[16:13:53] Starting 'server'...
[16:13:53] Starting 'watch'...
[16:13:53] Finished 'server' after 100 ms
true
[16:13:53] The following tasks did not complete: default, <parallel>, watch
[16:13:53] Did you forget to signal async completion?
Error<EMAIL_ADDRESS>start: `gulp`
Exit status 1
    at EventEmitter.<anonymous> (C:\Users\Will\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\util
s\lifecycle.js:217:16)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)
    at ChildProcess.<anonymous> (C:\Users\Will\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\util
s\spawn.js:24:14)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)

notice the additional failure -

Normally i'd say you have to join the threads, but i think this is all js
stuff so, idk promises? I don't really know JavaScript sorry.
On Thursday, April 14, 2016, face0b1101<EMAIL_ADDRESS>wrote:

@colin-marshall https://github.com/colin-marshall, you asked this
question on the foundation forum:
@Will https://github.com/Will what happens when you change the default
task to run server and watch in parallel?
// Build the site, run the server, and watch for file changes
gulp.task('default',
gulp.series('build', gulp.parallel(server, watch)));
The answer is, I get the following (very similar) output:

<EMAIL_ADDRESS>start C:\Users\Will\Websites\foundationSites\testProject
gulp

[16:13:26] Failed to load external module babel-register
[16:13:26] Requiring external module babel-core/register
[16:13:40] Using gulpfile ~\Websites\foundationSites\testProject\gulpfile.babel.js
[16:13:40] Starting 'default'...
[16:13:40] Starting 'build'...
[16:13:40] Starting 'clean'...
[16:13:41] Finished 'clean' after 31 ms
[16:13:41] Starting 'pages'...
[16:13:41] Starting 'sass'...
[16:13:41] Starting 'javascript'...
[16:13:41] Starting 'images'...
[16:13:41] Starting 'copy'...
[16:13:48] Finished 'images' after 7.34 s
[16:13:51] Finished 'pages' after 10 s
[16:13:51] Finished 'sass' after 10 s
[16:13:51] Finished 'copy' after 10 s
[16:13:53] Finished 'javascript' after 13 s
[16:13:53] Starting 'styleGuide'...
[16:13:53] Finished 'styleGuide' after 72 ms
[16:13:53] Finished 'build' after 13 s
[16:13:53] Starting 'server'...
[16:13:53] Starting 'watch'...
[16:13:53] Finished 'server' after 100 ms
true
[16:13:53] The following tasks did not complete: default, , watch
[16:13:53] Did you forget to signal async completion?
Error<EMAIL_ADDRESS>start: gulp
Exit status 1
at EventEmitter. (C:\Users\Will\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\util
s\lifecycle.js:217:16)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
at ChildProcess. (C:\Users\Will\AppData\Roaming\npm\node_modules\foundation-cli\node_modules\npm\lib\util
s\spawn.js:24:14)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:850:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
notice the additional failure -
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/zurb/foundation-sites/issues/8573#issuecomment-209996426

@colin-marshall
Here is the output from gulp -v
[11:49:03] CLI version 1.2.1
[11:49:03] Local version 3.9.1
PS C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundationpress>
I followed instructions elsewhere to install the gulp cli at the global level, and gulp locally. I've tried both this version of gulp, and the 4.0 alpha 2.
Regarding your question above about what was different about my src folder, it basically just contains multiple layout/partial/pages the way the template is intended to be used. But there is a twist here that I'm not sure I have an explanation for.
I'm currently testing 6.2.1 code in two different ways. 1, the output from above where I was getting the error reported, is a zurb template based prototyping set up. Since I reported the above, the project is now compiling properly and not complaining about anything. What changed?, I changed the config.yml statements to point to the precompiled js, such as this:

"bower_components/foundation-sites/dist/plugins/foundation.abide.js"
However, none of the javascript is working per dropdown menus that aren't firing. I have yet to determine why.

Meanwhile, I had already returned to my foundationpress 2.5 (based on foundation 6) project to do a bower update in hopes that it would run with 6.2.1 foundation. npm run watch did not compile and I get the following output.
PS C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundationpress> npm run
watch

<EMAIL_ADDRESS>watch C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\them
es\foundationpress
gulp

[11:45:15] Using gulpfile ~\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundationpress\gu
lpfile.js
[11:45:15] Starting 'clean'...
[11:45:15] Starting 'clean:javascript'...
[11:45:15] 'clean:javascript' errored after 139 µs
[11:45:15] ReferenceError: del is not defined
at Gulp. (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\fo
undationpress\gulpfile.js:235:10)
at module.exports (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foun
dationpress\node_modules\orchestrator\lib\runTask.js:34:7)
at Gulp.Orchestrator._runTask (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content
\themes\foundationpress\node_modules\orchestrator\index.js:273:3)
at Gulp.Orchestrator._runStep (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content
\themes\foundationpress\node_modules\orchestrator\index.js:214:10)
at Gulp.Orchestrator.start (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\th
emes\foundationpress\node_modules\orchestrator\index.js:134:8)
at runNextSet (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundati
onpress\node_modules\run-sequence\index.js:88:16)
at runSequence (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundat
ionpress\node_modules\run-sequence\index.js:99:2)
at Gulp. (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\fo
undationpress\gulpfile.js:229:3)
at module.exports (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foun
dationpress\node_modules\orchestrator\lib\runTask.js:34:7)
at Gulp.Orchestrator._runTask (C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content
\themes\foundationpress\node_modules\orchestrator\index.js:273:3)
[11:45:15] 'clean' errored after 3.61 ms
[11:45:15] Error in plugin 'run-sequence'
Message:
An error occured in task 'clean:javascript'.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\mhair.ICS\AppData\Roaming\npm\node_modules\npm\bin
\npm-cli.js" "run" "watch"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>watch: gulp
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>watch script 'gulp'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foundationpress package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs foundationpress
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls foundationpress
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundationpres
s\npm-debug.log
PS C:\Users\mhair.ICS\documents\websites\foundationpress6.boardofed.idaho.dev\wp-content\themes\foundationpress>
I have not been able to figure this one out, even using node-debug and a similar node debugging feature of phpstorm. This is the foundationpress version of the gulpfile, not the new yaml based one in Foundation 6.2.1 (and 6.2). So this may be the reason for this. I also tried using this setup with the precompiled js but got the same error.
[13:18:11] Error in plugin 'run-sequence'
Message:
An error occured in task 'clean:javascript'.
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\mhair.ICS\AppData\Roaming\npm\node_modules\npm\bin
\npm-cli.js" "run" "watch"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.6
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>watch: gulp
The only bright spot here is that I then dove deep into translating the gulpfile instructions to something that prepros could work with and I now, for the first time since starting with foundation 6.x, have a fully functioning codebase. But it required taking the gulp/node workflow completely out of the picture. Again, your FoundationPress Grunt-based workflow also worked.
Long story but I felt I needed to put it out there considering how much grief I've been spilling in the forums.
@colin-marshall , if there is anything in these errors that triggers any ideas, please let me know as I'm still curious if I can get the gulp workflow going, but my pace dedicated to it will slow to outside work hours.

@mhair: ReferenceError: del is not defined would either mean that you don't have var del = require('del') in your gulpfile.js, you did not run npm install, or the del package is missing from package.json.

Desperate times, desperate measures.
I could not find a way to rectify this problem. It seems to be an error specific to my particular Windows installation. I seemed to be having a few odd errors in other applications also.
Therefore, unable to fix the problem, I decided to refresh Windows 10...
...** Everything now works as expected.**
So to anyone else who stumbles accross this thread with this error, I recommend you just start again with a fresh copy of Windows. There is probably a way to solve it, but it was much easier to just go for a fresh install.
Thanks to everyone who chipped in with suggestions.

@colin-marshall : I checked all of those things prior, and again just verified, including that the specific file mentioned in the clean:javascript task was there...it is. Plus I did an npm install del --save-dev just for good measure. Any other ideas?

@mhair I'm running out of ideas. Have you tried installing a Node version manager? There's a few for Windows. It allows you to have multiple installs of different versions of Node and switch between them. I would suggest trying this and see if having isolated Node installations with a version manager makes something "work" that wasn't before.
Here's what looks like the most popular one:
https://github.com/coreybutler/nvm-windows
Have you tried any other Win7 computers to see if it's only an issue on your install?


Wrap all/1 returns with an ok-tuple

SwissSchema's all/1 should be returning lists wrapped in ok-tuples:
# Today, all/1 returns a raw list:
User.all() # => [%User{}, %User{}, %User{}, ...]

# It should, instead:
User.all() # => {:ok, [%User{}, %User{}, %User{}, ...]}

The reason is simple: it's an IO op, which might fail due to reasons (network failure, db perms, schema mismatch, etc.). I know it differs from Ecto's default behavior, but I think we might improve the DX by standardizing the returned structure of this function.
Also, if Ecto's all/2 throws errors when things go wrong, we should be rescuing them to returning error-tupled values:
# Something is wrong – eg.: network is unavailable
User.all() # => {:error, %SomeError{}}

And now I'm wondering: should we have an equivalent bang function all!/1? 🤔


Support for SIGTERM handling not possible if spacy-nlp package is included in project

Background:
SIGTERM handling is required for graceful shutdown of node based micro service while running on Kubernetes. An example for SIGTERM graceful handling by node project would the following code (can be tested by sending "kill -15 pid" to the node process id).
process.on('SIGTERM', () => {
console.log('Just Received SIGTERM.');
});
Issue:
When a node project is dependant upon spacy-nlp packge then even if the above code is included in the node project, sending "kill -15 pid" to node process id results in error "INFO Exit: killed ioClient.js children" and node process exits without graceful shutdown.

After commenting the following lines, the SIGTERM is getting handled by the project file correctly.
node_modules/poly-socketio/src/start-io.js
node_modules/spacy-nlp/src/start-io.js
The reason is that these two files have SIGTERM handlers process.exit() is being called by them.
Is there is possibility of getting process.exit() called with some configuration/settings?


Fix pull-request template to pass lint checks

Pull request intention

[X] Code improvement (improve test coverage or code readability)

Description
Lint fix in template; make PR template appropriate for a public repo
Self identified pull request size

[X] XS (Extra Small) SLO - 4 hours
[ ] S (Small) SLO - 1 day
[ ] M (Medium) SLO - 2 days
[ ] L (Large) SLO - 3 days
[ ] XL (Extra Large) SLO - N/A

Pull request checklist

[X] I have performed a self-review of my own code
[X] I have tested my code to prove my fix is effective or that my feature works
[X] I have updated documentation (if applicable)

@joewelsh when you get a sec, can you merge this in?


⚠ SolarOscp has degraded performance

In 65314c1, SolarOscp ($SOLAROSCP_URL) experienced degraded performance:

HTTP code: 200
Response time: 270 ms

Resolved: SolarOscp performance has improved in af02777.


[06262021] - Chapter04 Session06 - Building a free and open cloud one deployment at a time with Unfurl by Adam Souzis

What's The Future Of UNFURL?? Like Where Do You See It In Near Future?

Is opensource somehow restricted in regular cloud IAAS ?

How is the connection between unfurl and open cloud?

How to contribute to Open Cloud?

Regarding to the poll asking how much of cloud expenses we can contribute to open source. My question is how unfurl can save the cloud expenses, as i understood we still using cloud, and unfurl is just a better interface. Please correct me if I understood wrongly.

Also just a feedback - it would be great to make a multiple choose polls. But the questions was great.

What some good resources a beginner can get started with?


conda update

Issue Report Checklist

[ ] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[ ] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[ ] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
What steps reproduce the problem?

What is the expected output? What do you see instead?
Paste Traceback/Error Below (if applicable)

PASTE TRACEBACK HERE

Versions

Spyder version:
Python version:
Qt version:
PyQt version:
Operating System name/version:  Windows 11

Dependencies

PASTE DEPENDENCIES HERE

i have an spyder-cf env in anaconda. I want to install spyder 5.3.3 version  and it is not working

Closing because this is empty.

(base) C:\Users\Roshini>conda install -c anaconda mysql-connector-python
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |


Increment version for apicenter releases

Increment package version after release of Azure.ResourceManager.ApiCenter

API change check
API changes are not detected in this pull request.


screenshot?

Would it be possible to add a screenshot to the README so we can see just what this bot is doing / intended to do?

There's a link at the top of the repository going to http://hornwitser.no/discord/ which shows what this thing does.

Thanks!


az container exec - unwanted characters inserted at shell prompt

Describe the bug
After executing a command on an azure container image, I cannot navigate the shell as normal. At the prompt, hitting the up arrow will cycle through history, but as soon as I press the left arrow to move the cursor to modify a command, I cycle to the previous command in history.
Additionally, when attempting to use a text editor within the container, navigating through the file with the arrow keys results in random inserts of the characters "A", "B", "C", or "D". This behavior happens regardless of editor used - I've tried vi, vim, and nano.
Command Name
az container exec
Errors:
No error codes printed, just unexpected behavior.
To Reproduce:

az container exec -g {} --name {} --container-name {} --exec-command "/bin/bash"

Expected Behavior
I expect bash to behave as it would normally - either in a container on my local machine, or as run on a bare metal or virtualized OS.
Environment Summary
macOS-10.14.1-x86_64-i386-64bit
Python 3.8.1
Shell: bash

azure-cli 2.0.81 *

Additional Context

@dmoore44 Apologies for the late reply. I wasn't able to reproduce this issue from the shell prompt. The arrow key and the editor did work fine. This issue is open for quite sometime. Could you please let me know if you need any further assistance on this ? Awaiting your reply.


[red-knot] Extract red_knot_python_semantic crate

Summary
Extract the red knot code from ruff_python_semantic and move it into its own crate because we don't expect to share any logic between the two semantic models.
Test Plan
cargo build

Oh, I missed some doctests. I'll fix the test failures before merging.


MVVM: List of repositories is lost when the screen is rotated

I'm focused on the app that implements MVVM, using it as an example to help in building my own app, and I see that the list of repositories is not persisted when the activity is killed and recreated when the device is rotated.
How would you accomplish persisting the list of repositories when the device is rotated?

I figured out a way to do it in another repo I was looking at. I don't know if doing it the same way here will work or not but I'm wiped out and dont feel like trying any more. Maybe someone who finds this later will find it helpful...


Hyperfine states with Cell

I'm running into issues with using hyperfine states with Cell. I'm specifying the states using the notation [n, l, j, F, mF] as the documentation suggests, but I'm getting TypeErrors.
It looks like the list for each state is getting passed to the ARC function getRabiFrequency(), but the number of arguments being passed is incompatible. It also seems like the getRabiFrequency function expects arguments in the fine basis [n, l, j, mj]. It's not clear to me how or if Rydiqule handles conversion from the coupled hyperfine basis [n, l, j, F, mF] to the fine basis [n, l, j, mj], especially since the coupled hyperfine basis states are generally superpositions of the uncoupled basis states [n, l, j, mj, i, mi].
An error is not raised if I manually compute the hyperfine transition Rabi frequencies to input in the Cell couplings.
Example code:
import rydiqule as rq
import numpy as np

states = [[6, 0, 0.5, 4, 0], [6, 1, 1.5, 5, 0]]

probe = {'states': (0,1), 'beam_power': 1e-3, 'beam_waist': 1e-3, 'detuning': 0}

cell = rq.Cell('Cs', states[0], states[1], beam_area = np.pi*probe['beam_waist']**2)
cell.add_couplings(probe)

Error message:
  File ~\python scripts\testing\untitled2.py:16
    cell.add_couplings(probe)

  File ~\AppData\Local\miniconda3\envs\rydRelease11\lib\site-packages\rydiqule\sensor.py:366 in add_couplings
    self.add_coupling(states=states, **c_copy, **extra_kwargs)

  File ~\AppData\Local\miniconda3\envs\rydRelease11\lib\site-packages\rydiqule\cell.py:732 in add_coupling
    passed_rabi = np.array([[1e-6*self.atom.getRabiFrequency(*state1, *state2[:-1],

  File ~\AppData\Local\miniconda3\envs\rydRelease11\lib\site-packages\rydiqule\cell.py:732 in <listcomp>
    passed_rabi = np.array([[1e-6*self.atom.getRabiFrequency(*state1, *state2[:-1],

  File ~\AppData\Local\miniconda3\envs\rydRelease11\lib\site-packages\rydiqule\cell.py:732 in <listcomp>
    passed_rabi = np.array([[1e-6*self.atom.getRabiFrequency(*state1, *state2[:-1],

TypeError: getRabiFrequency() takes from 11 to 12 positional arguments but 13 were given

Thanks for the report John! As you've found out, hyperfine support in Cell is very much still in alpha. Even moving beyond this particular issue, I would be very suspicious of dephasing rate calculations. For now I recommend caution using hyperfine states in Cell.
While we are working towards full hyperfine support, but we are first hammering out some structural changes in Sensor before fully tackling Cell hyperfine support.


Use atom list instead of binary with dots as a metric names

This is IMHO much more "natural" way as not all backends uses dots.
Notable dot users:

StatsD (and DataDog)
Graphite
Riemman
Splunk
Wavefront (allows other separators, but use dots as default)

Notable non dot users:

Prometheus (underscore)
InfluxDB (underscore)
Carbon2 (not specified, do not use "metric names" at all)
Dropwizard (if I understand correctly the specs, they do not use any separator, or leave it up to the storage tool)
OpenCensus (slash, by convention)

Not sure:

collectd

Not defined/mixed:

OpenTelemetry do not (yet?) defines metrics separator. Currently only few tags and spans have defined names and in that case both dots and underscores are used.

So while dot seems like popular format, it is not used everywhere, and in my personal opinion it needlessly diverges from the Telemetry approach of defining metrics as a list of atoms. Current naming approach feel very StatsD centric for me.
I feel that the more "natural" way of defining metrics (at least in my opinion) would be:
Telemetry.Metrics.metric_type(metric_group, metric_name, options)

For example
Telemetry.Metrics.distribution([:http, :requests, :stop], :duration, buckets: [100, 200, 300])

Instead of
Telemetry.Metrics.distribution("http.request.stop.duration", buckets: [100, 200, 300])

cc @bryannaegele as he is maintainer of Prometheus integration which uses different separator than dot.

The dot is just sugar, internally it is a list of atoms. I will be glad
with supporting both but I don’t think we should remove the string format
because it can get very verbose. A PR to support both is welcome!
José Valim
www.plataformatec.com.br
Skype: jv.ptec
Founder and Director of R&D

@josevalim I know it is a sugar and that internally it is list of atoms. My point is that we should not have sugar in library basic as this one. TBH sometimes I have feeling that Elixir community fallback to sugar too early and without good reason.

I am not really interested in having this discussion right now. I think it is justified and doesn’t pose any confusion, feel free to disagree. So you are welcome to send a PR or I will be glad to keep things as is too.


tests: revisit/fix test_cli_vital

It was not working after fadce51 at all, but did not report the failure
correctly.
It fails currently ("Undefined variable: s:next" etc),
https://github.com/Kuniwak/vint/issues/274 - but gets skipped without
the submodule being checked out.

Codecov Report

Merging #320 into master will decrease coverage by 0.14%.
The diff coverage is 41.66%.

@@            Coverage Diff             @@
##           master     #320      +/-   ##
==========================================
- Coverage   70.81%   70.66%   -0.15%
==========================================
  Files         134      134
  Lines        7709     7704       -5
  Branches     1253     1252       -1
==========================================
- Hits         5459     5444      -15
- Misses       1922     1933      +11
+ Partials      328      327       -1


15 periodic auth proof

Please move vpuf and auth-proof into a folder called src so it is easy to identify the code


Wrong ordering of "path" statement

Validating the Core IM 1.4.1 with pyang --lint core-model.yang
results in
core-model-1-4.yang:1694: error: keyword "path" not in canonical order (see RFC 6020, Section 12)
(Might already be fixed with updating the UML2YANG for translating the tech.spec. extension.)

In UML2YANG tool , by default the "require-instance" will be generated after the "path" statement. This behavior of the tool fixes the canonical order issue.
We also generated a ReleaseCandidate#1 for the core-model and able to see the correct canonical order.
But , as per the proposal in core/issues/17 , the require-statement of the leafref shall be "false" and not "true".

leaf-list physical-port-reference {
      type leafref {
        path "/core-model:control-construct/core-model:equipment/core-model:uuid";
        require-instance false;
      }
      description
        "One or more text labels for the unmodeled physical port associated with the LTP.
         In many cases there is no associated physical port.";
    }

This will be available if we generate and publish a new release of the core-model-1-4.

Related issue https://github.com/openBackhaul/core/issues/10

As per the decision made in the issue https://github.com/openBackhaul/core/issues/10 ,

Decision : The "pruning and refactoring" step should prune the "LogicalTerminationPoint:physicalPortRefernce[*]". As the result the "physical-port-reference" will be removed from the core-model-1-4.yang.

This issue is obsolete.

Ad-hoc decision in 5G-xHaul call 2023-05-31:
This issue is now obsolete due to the decision made in #10 .
-> closed


distro-base: add minimal iptables variant

I have built these image into a kind image and ran the conformance tests in a kind cluster. They all passed.
I put all the minimal images into the same docker file to allow us to actually build them all in presubmit since we can't base off previously built images with buildkit unless its the same dockerfile.
Todo:

[ ] prow job updates - https://github.com/aws/eks-distro-prow-jobs/pull/201
[x] cdk changes to introduce new image repos (eks-distro-minimal-base-nonroot, eks-distro-minimal-base-iptables)
[ ] add new tag files to eks-distro - https://github.com/aws/eks-distro/pull/486

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/retest


docs(esl-image): fix SVG rendering mode name

:tada: This PR is included in version 4.0.0-beta.7 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Passing an element into one screen's title and then navigating to a screen with a string as title causes crash

On one screen, I have the navigationOptions set as:
  static navigationOptions = {
    title: NavItems.logo(),
    gesturesEnabled: false,
    headerLeft: NavItems.menuButton()
  }

NavItems.logo() returns an Image contained within a View. In the next screen, the navigationOptions are set as:
  static navigationOptions = ({ navigation, screenProps }) => ({
    title: navigation.state.params.name
  })

Upon navigation, I receive the error,
JSON value '{
    "_owner" = "<null>";
    "_store" =     {
    };
    key = "<null>";
    props =     {
        children =         {
            "_owner" = "<null>";
            "_store" =             {
            };
            key = "<null>";
            props =             {
                resizeMode = contain;
                source = 2;
                style =                 (
                                        {
                        height = "25.6";
                    }
                );
            };
            ref = "<null>";
        };
        style =         (
                        {
                alignItems = center;
                height = 50;
                justifyContent = center;
                width = 100;
            }
        );
    };
    ref = "<null>";
}' of type NSDictionary cannot be converted to NSString

could you put together a demo that reproduces the issue?

I get the same error too..

dup: https://github.com/react-navigation/react-navigation/issues/3043

see https://github.com/react-navigation/react-navigation/issues/4058


Update Tenant Kubernetes Addons

Follow up to https://github.com/aenix-io/cozystack/pull/183

Allows to specify hosts, not just a single host
fix typo in cert-manager addon
Addons disabled by default
Add FluxCD addon

fixes https://github.com/aenix-io/cozystack/issues/159
fixes https://github.com/aenix-io/cozystack/issues/157
fixes https://github.com/aenix-io/cozystack/issues/185

I just read this PR over, haven't tested it yet. That is really neat! That is about how I imagined that it would look, and that is about how easy I imagined it would be. I will give it a try and see how it works.
I would not have foreseen that adding flux-operator in the core/cozy-system would so quickly lead us to this point.

When I enabled all the addons, I landed in a failed state:
% kg hr -w|grep -v 'succeeded'
NAMESPACE                        NAME                                 AGE     READY   STATUS
tenant-root                      kubernetes-harvey-cert-manager       9m9s    False   dependency 'tenant-root/kubernetes-harvey-cilium' is not ready
tenant-root                      kubernetes-harvey-cilium             9m9s    False   Helm install failed for release cozy-cilium/cilium with chart<EMAIL_ADDRESS>client rate limiter Wait returned an error: context deadline exceeded
tenant-root                      kubernetes-harvey-fluxcd             9m9s    False   dependency 'tenant-root/kubernetes-harvey-cilium' is not ready
tenant-root                      kubernetes-harvey-fluxcd-operator    9m9s    False   dependency 'tenant-root/kubernetes-harvey-cilium' is not ready
tenant-root                      kubernetes-harvey-ingress-nginx      9m9s    False   dependency 'tenant-root/kubernetes-harvey-cilium' is not ready
tenant-test                      kubernetes-cluster-cilium            7m10s   False   Helm install failed for release cozy-cilium/cilium with chart<EMAIL_ADDRESS>client rate limiter Wait returned an error: context deadline exceeded
tenant-test                      kubernetes-cluster-fluxcd            7m10s   False   dependency 'tenant-test/kubernetes-cluster-cilium' is not ready
tenant-test                      kubernetes-cluster-fluxcd-operator   7m10s   False   dependency 'tenant-test/kubernetes-cluster-cilium' is not ready

The cilium installs just took a bit longer than timeout to become ready, they didn't have any problem, but these addon charts requested by users have to cope with the HelmRelease state machine, that sometimes requires a flux reconcile hr --force
I think you have defined retries and remediation in the HelmRelease resources elsewhere in the system, perhaps we can add some more of that here. Meanwhile I've done a flux reconcile hr --force on each cilium here, and that's enough to get it progressing nicely. I've just tested all the addons together on one cluster + only the flux addon on the other cluster, this is looking like it's going to be really handy! 👏

I am seeing some issues today on a fresh deployment that I haven't seen before.
kubectl get hr -n cozy-fluxcd fluxcd-operator -o jsonpath='{.spec.values}' | helm upgrade -i --post-renderer ../../../scripts/fluxcd-kustomize.sh -n cozy-fluxcd fluxcd-operator . -f -
Error: UPGRADE FAILED: error while running post render on files: error while running command /cozystack/scripts/fluxcd-kustomize.sh. error output:
Variable $NAME is not set!
: exit status 1
make: *** [../../../scripts/package-system.mk:11: apply] Error 1
make: Leaving directory '/cozystack/packages/system/fluxcd-operator'
time="2024-06-27T19:38:04Z" level=fatal msg="failed to run" err="exit status 2"

These errors show up just about as long as it takes for cilium to come online. The Flux controller pods will not be scheduled before CNI is ready, that's normal and good, I think they should communicate over CNI and not hostNetwork 👍 that configuration is fine.
I'm sure that one thing has something to do with the other but I'm not sure how. Why does postrender kustomization fail when it gets run but just the first few times. Is there somewhere in installer.sh that package-system.mk gets invoked without a NAME or NAMESPACE? I can't see it right now.
Perhaps we should start the cilium install a bit earlier? I noticed that flux-operator installs, becomes ready, etc. before Cilium install even begins. That should be reversed if possible, even if flux-operator is running with hostNetwork it might have nothing to do with this bug, it should be fixed before releasing 0.8 🤞

Whatever failure I saw also resulted in the flux-operator landing in state with HelmReleases suspended:

I see some scripts in here that suspend and resume stuff, not sure what they're trying to do, but it looks like they're trying to avoid cross-talking with the Flux controllers themselves when helm template|apply type operation is in progress.

I see it now, when flux_is_ok the part of the invocation where targets="apply resume" is never reached
It should also check that the HelmRelease fluxcd is ready, then I think it will work. Making a change to test it out locally.

I think that this line does not pass NAME and NAMESPACE to the post render script, that's causing make apply to fail whenever it gets called for fluxcd-operator here:
  kubectl get hr -n $(NAMESPACE) $(NAME) -o jsonpath='{.spec.values}' | helm upgrade -i --post-renderer ../../../scripts/fluxcd-kustomize.sh -n $(NAMESPACE) $(NAME) . -f -

in scripts/package-system.mk

Somehow I still landed in this situation. Going to try another from-scratch e2e.

I think this is likely to land in this state because it might take longer than 60s to have the fluxinstance CRD ready, and that there is no recovery path if it happens like that...
make -C packages/system/fluxcd-operator $targets
wait_for_crds fluxinstances.fluxcd.controlplane.io
make -C packages/system/fluxcd $targets
wait_for_crds helmreleases.helm.toolkit.fluxcd.io helmrepositories.source.toolkit.fluxcd.io

wait_for_crds() {
  timeout 60 sh -c "until kubectl get crd $*; do sleep 1; done"
}

When I go back and run
make -C packages/system/fluxcd apply resume

it looks like all is fine.
FWIW, this issue doesn't block the rest of the HelmReleases from progressing

I've had a think about what it means to land in this state, and I've realized that it means users can overwrite any part of the FluxInstance.spec (including any of spec. kustomize.patches, components, cluster, or distribution) without worrying about being overwritten by the cozystack reconciler.
So, I'm not sure that it's a bug to land in that state? I think this can merge, if you have a look at #191

There was some drift in my local build/deploy branch, where I've been test-tagging releases. I don't see the issues described in the screenshots anymore when I rebased my deploy branch on the PR merged, it must have been an error in my fork.
The install proceeds smoothly and the fluxcd helmrelease gets resumed and reconciled A-OK.
I'd like to test the addon stuff a bit more, but I don't think I have any hangups about releasing 0.8.0 now. 🚀


Uninstall not properly working

Observed on Windows 10.
If you install the software, unintall it, and reinstall. The program does not launch. It is probably because the uninstall is not properly working.
However, it worked after manually deleting the models/pipelines after install. Therefore, by simply deleting these during uninstall directly, this should work.

There has been added a full description in the README on how to delete the remaining stuff which the uninstaller fails to delete. Hence, it is possible to properly delete the software across all operating systems.
We could probably make a new issue if we wish to add proper uninstall, requiring no manual step after, but I don't see it as cruicial.


Switching Alt(right) and Caps Lock doesn't work and makes the Alt(right) to be only usable by pressing shift simultaneously. Is it even possible to change Caps lock and Alt(right)?

Microsoft PowerToys version
0.49.1
Running as admin

[ ] Yes

Area(s) with issue?
Keyboard Manager
Steps to reproduce
Trying to switch Alt(right) and Capslock
✔ Expected Behavior
The change to happen without problems.
❌ Actual Behavior
The switch automatically made the Alt(right) to be usable only by pressing shift simultaneously. In the end it doesn't work at all.
Other Software
No response

Failed to reproduce this. Is the following screenshot matching your settings?

Yes the screenshot is right and it works until you try to map caps lock to alt (right). Here are my settings and the alt (right) functionality doesn't work on my caps lock and I cant use any special symbols.

On some keyboard mappings Alt right is actually Alt(Right)+Ctrl(Left) (= Alt Gr), and is not actually a single key.
You might be expecting behavior from pressing these 2 keys at once.(Alt(Right)+Ctrl(Left)).

This is actually an issue, I believe. We might be considering that Ctrl(Left)+Alt(Right) is an incomplete shortcut and so are not allowing the user to set it.

Yes I think you are completely right since I tried including the Ctrl(left) but it still wouldn't change the Alt key.

Please try this: open "Remap a shortcut" and then press your right Alt key. If it shows as (L)Ctrl+(R)Alt then it functions as AltGr.
AltGr and Ctrl+Alt gives (more) issues. There's something fishy about it and I think we should investigate, and make people more aware. Most people just don't know that AltGr = (L)Ctrl + (R)Alt and many remap their (left) Ctrl keys...
Quote from Wikipedia:

On a typical, Windows-compatible PC keyboard, the AltGr key, when present, takes the place of the right-hand Alt key: if not engraved as such, that key may still be remapped to behave as though it is, (or emulated using a chord such as Ctrl+Alt).

I tried that but it still gives me this kind of error:

The keys I have on my keyboard for alt are Alt(left) and AltGr(right) so no Alt key on the rightside.

does this issue still happen with v0.73.0? /needinfo

Haven't tried. I think powertoys just doesn't handle nordic keyboards
On Sat, Sep 16, 2023 at 9:54 PM Joseph Finney @.***>
wrote:

does this issue still happen with v0.73.0? /needinfo
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/14316#issuecomment-1722293335,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV75XBWRAUG22YPKBDHWGHTX2XYW7ANCNFSM5HQV4A2A
.
You are receiving this because you authored the thread.Message ID:
@.***>

/dup https://github.com/microsoft/PowerToys/issues/22863


Adding warning for matching versions

Adding a note to make sure users install matching versions of babylonjs and babylonjs-loaders

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/13544/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13544/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/13544/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/13544/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/13544/merge
https://gui.babylonjs.com/?snapshot=refs/pull/13544/merge
https://nme.babylonjs.com/?snapshot=refs/pull/13544/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/13544/merge#BCU1XR#0

Closing for now, please reopen if needed


code

I'm very much looking forward to open source your work here is my email<EMAIL_ADDRESS>

Thanks for your interest. We will release the code after the corresponding paper is accepted.

I'm very much looking forward to open source your work here is my email<EMAIL_ADDRESS>
Thanks for your interest. We will release the code after the corresponding paper is accepted.


Adjust resources(memory, cpu etc) allocated to each cassandra node after cassandra-mesos gets deployed.

It seems right now there is no way to adjust resources(memory, cpu etc) allocated to each cassandra node after cassandra-mesos gets deployed. Currently I have to tear down the whole cassandra-mesos framework and redeploy it in order to increase memory for each cassandra node. In this case, all the cassandra data will be gone.
A good example to follow will be the kafka-mesos framework. https://github.com/mesos/kafka#updating-broker-configurations.
Its rest api allow us to stop a node, update configuration (including memory/cpu etc.) and restart it.

This repository is deprecated.  Please use the latest supported framework here:  https://github.com/mesosphere/dcos-cassandra-service.


Header View Deque Issue and View not set

Collectionview header not showing on iOS 12 ,Please help

Hi! Can you post the code creating the header and maybe the header code itself too?

func collectionView(_ collectionView: UICollectionView,
viewForSupplementaryElementOfKind kind: String, at indexPath: IndexPath) ->
UICollectionReusableView {
    *if* collectionView == *self*.homeCollectionView {

        *guard* *let* supplementaryView = collectionView.

dequeueReusableSupplementaryView(
            ofKind: HomeViewController.sectionHeaderElementKind,

            withReuseIdentifier:  HomeHeaderView.cellIdentifier(),

            for: indexPath) *as*? HomeHeaderView *else* {

fatalError("Cannot
create header view") }
        supplementaryView.titleLabel.text = *self*.viewModel.homedata

[indexPath.section].name?.uppercased()
        *return* supplementaryView

    }

    *return* UICollectionReusableView()

}

Please check the above code which sometimes showing header in iOS 12 , some
times its doesn't show
On Tue, Jun 23, 2020 at 1:34 PM Joel Ekström<EMAIL_ADDRESS>wrote:

Hi! Can you post the code creating the header and maybe the header code
itself too?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joelekstrom/JEKScrollableSectionCollectionViewLayout/issues/20#issuecomment-647980490,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWELA6PUHT2UQZKFV5NYP3RYBOYLANCNFSM4OEQQXDA
.

--
Thank you for your time and consideration.Sincerely,
Kiran Dhokale
iOS Developer
Mob.<PHONE_NUMBER>

And it works fine on iOS13? What do you have in sizeForSupplementaryElementOfKind:? Note that this layout doesn’t support automatic sizing

I am not used automatic sizing of cells , all cells of same size
On Tue, Jun 23, 2020 at 3:47 PM Joel Ekström<EMAIL_ADDRESS>wrote:

And it works fine on iOS13? What do you have in
sizeForSupplementaryElementOfKind:? Note that this layout doesn’t support
automatic sizing
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joelekstrom/JEKScrollableSectionCollectionViewLayout/issues/20#issuecomment-648048785,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHWELA36K3UDGHH7VISMEDLRYB6KLANCNFSM4OEQQXDA
.

--
Thank you for your time and consideration.Sincerely,
Kiran Dhokale
iOS Developer
Mob.<PHONE_NUMBER>


[AzureMonitorExporter] api feedback (part1)

Responding to feedback on our public api.
Changes

merge Extensions classes.
no change to public api. no user impact with this change.

Run export-api script to update the APIs.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Monitor.OpenTelemetry.Exporter

Superseded by https://github.com/Azure/azure-sdk-for-net/pull/37996


Accessibility Updates - Queue

Title of ticket: Accessibility Updates - Queue
Description
Resolve all accessability "errors" as identified by WAVE extension for the Queue - https://wave.webaim.org/extension/
Critical Changes to Queue that were identified through Running Accessibility Tests on Queue Page
Dependencies
No dependencies.

DOD

[ ] All critical issues resolved or captured in new tasks
[ ] Aria labels added to buttons
[ ] Empty link resolved
[ ] Empty button
[ ] Contrast errors fixed
[ ] Alerts reviewed and fixed if possible

Updated description and DOD.

All critical changes have been fixed. Great Work @divyav-aot & @richard-aot


[ASR][V2A-RCM] Add properties and provider specific models failback provider for V2A RCM.

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[X] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[X] SDK of .NET (need service team to ensure code readiness)
[X] SDK of Python
[X] SDK of Java
[X] SDK of Js
[X] SDK of Go
[X] PowerShell
[X] CLI
[X] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of “no breaking changes
[X] I have reviewed the documentation for the workflow.
[X] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[X] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

This PR adds V2A-RCM specific request-response models and properties for failback direction. Two new PUT APIs and there corresponding examples are added to support "Cancel Failover" operation.

/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationProtectedItems/{replicatedProtectedItemName}/failoverCancel
/Subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationRecoveryPlans/{recoveryPlanName}/failoverCancel

Adding @DevBaburaj, @anmolbhatia289

@ChenTanyi, Please review the PR.

Hi, @imshashwataggarwal your PR are labelled with WaitForARMFeedback. A notification email will be sent out shortly afterwards to notify ARM review board(armapireview@microsoft.com). cc @

@imshashwataggarwal Adding new API need ARM review first, please wait or ask ARM to review it.
@jianyexi Is adding a new path and new properties in current API not considered as breaking change? I saw the breaking change CI has passed.

@Azure/arm-api-review-board : Please review this.


Text Logo Misaligned on Disclaimer on Mobile

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in QA
Followed all applicable steps in the TROUBLESHOOTING guide: TODO
Checked for relevant discussions on Discord: https://discord.gg/pPERUuv
Checked that your issue isn't already filed: https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues

Description
When viewing the disclaimer on mobile, the text logo is off center and requires scrolling to view the entire disclaimer.

Steps to Reproduce

Inspect on mobile view
Log in

Expected behavior:
The text logo should be centered and fully visible within the disclaimer.
Actual behavior:
The text logo is off-center and too large for the screen.
Reproduces how often:
100%

I noticed this and already fixed it and will be pushed with PR in #276

Sounds good! Just referenced this in your PR so it'll close when that's ready to merge


Force close OutOfMemmory

It happens while zooming maps. It fails in native memmory not heap.
Might be related to caches dissaperaing and reapearing. (#5)
java.lang.OutOfMemoryError: bitmap size exceeds VM budget
at android.graphics.Bitmap.nativeCreate(Native Method)
at android.graphics.Bitmap.createBitmap(Bitmap.java:468)
at com.google.android.maps.ZoomHelper.createSnapshot(ZoomHelper.java:444)
at com.google.android.maps.ZoomHelper.doZoom(ZoomHelper.java:151)
at com.google.android.maps.ZoomHelper.doZoom(ZoomHelper.java:140)
at com.google.android.maps.MapView.doZoom(MapView.java:1478)
at com.google.android.maps.MapView.doZoom(MapView.java:1487)
at com.google.android.maps.MapView$6.onZoom(MapView.java:1442)
at android.widget.ZoomButtonsController$3.onClick(ZoomButtonsController.java:268)
at android.view.View.performClick(View.java:2408)
at android.view.View$PerformClick.run(View.java:8816)
at android.os.Handler.handleCallback(Handler.java:587)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4669)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:876)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:634)
at dalvik.system.NativeStart.main(Native Method)

Any progress or a reason to keep this open? If yes, please reopen.

Has this problem been solved or is there another issue, where it is tracked?

It has been somehow addressed but not completely 'solved' as it is neither exactly describable nor reproducible. There are situations, especially when using maps (be it google or mapsforge) where an OutOfMemory, especially with the native bitmap VM budget, con not really be prevented or handled. This is more or less a problem 'built-in' top Android.
We have tried to do our 'homework' and sorted out some places where bitmaps were kept longer then necessary, strings not shortened or multiplied even. So even if this is not solved I too see no benefit of keeping this open as a separate issue.
There are some situations we could try to target specifically (like opening offline-map -> cache -> offline-map which fails on most phones) but nothing as general as described in this issue.

Opening offline-map -> cache -> offline-map is a very common use-case.
Do you mean, you could make it work well? IMO that would be important.

This OOM problem appears to be never on my 2.3.x device but always on my 3.x device....and its still there...

Which OOM problem do you talk about? The one mentioned in this issue or the one I was talking about in the end? If its the latter it may relate to the screen size (The 3.x device is your tablet, right?)


npm run build should create a zip folder

The Chrome Web Store expects a zip folder to be uploaded. At present the build command just emits the files to the build directory. They should be zipped up.

Related issues on upstream (?) project: https://github.com/samuelsimoes/chrome-extension-webpack-boilerplate/pull/72

I ended up using:
// Do this as the first thing so that any code reading it knows the right env.
process.env.BABEL_ENV = 'production';
process.env.NODE_ENV = 'production';
process.env.ASSET_PATH = '/';

var webpack = require('webpack'),
  config = require('../webpack.config'),
  fs = require('fs'),
  ZipPlugin = require('zip-webpack-plugin');

delete config.chromeExtensionBoilerplate;

config.mode = 'production';

var json = JSON.parse(fs.readFileSync('package.json', 'utf-8'));

config.plugins = (config.plugins || []).concat(
  new ZipPlugin({
    path: '../package', // don't save the zip file inside the build directory
    filename: json.name + '-' + json.version + '.zip',
    extension: 'zip',
  })
);

webpack(config, function (err) {
  if (err) throw err;
});

Thanks for the suggestion!

Still not working for me. I changed most of my files to plain .js though, would that maybe cause some issues?

I assume if you comment out the:
config.plugins = (config.plugins || []).concat(
  new ZipPlugin({
    filename: `${packageInfo.name}-${packageInfo.version}.zip`,
    path: path.join(__dirname, '../', 'zip'),
  })
);

in build.js then the build works (albeit without creating a zip file)?

Hey @cancan101, thanks for the fast reply!
I did that, but still no luck, the build folder is not there.
I printed the config from this part
webpack(config, function (err) {
  if (config) {
    console.log('print config', config)
  }
  if (err) throw err;
});

and this is what I get
{
  mode: 'production',
  entry: {
    newtab: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Newtab/index.jsx',
    options: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Options/index.jsx',
    popup: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Popup/index.js',
    background: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Background/index.js',
    contentScript: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Content/index.js',
    devtools: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Devtools/index.js',
    panel: '/Users/uros/Documents/Template/Code/template-chrome-extension/src/pages/Panel/index.jsx'
  },
  output: {
    filename: '[name].bundle.js',
    path: '/Users/uros/Documents/Template/Code/template-chrome-extension/build',
    clean: true,
    publicPath: '/'
  },
  module: {
    rules: [ [Object], [Object], [Object], [Object], [Object], [Object] ]
  },
  resolve: {
    alias: { process: 'process/browser' },
    extensions: [
      '.jpg',   '.jpeg', '.png',
      '.gif',   '.eot',  '.otf',
      '.svg',   '.ttf',  '.woff',
      '.woff2', '.js',   '.jsx',
      '.ts',    '.tsx',  '.css'
    ],
    fallback: {
      crypto: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/crypto-browserify/index.js',
      stream: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/stream-browserify/index.js',
      buffer: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/buffer/index.js',
      https: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/https-browserify/index.js',
      url: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/url/url.js',
      fs: false,
      util: '/Users/uros/Documents/Template/Code/template-chrome-extension/node_modules/util/util.js'
    }
  },
  plugins: [
    CleanWebpackPlugin {
      dangerouslyAllowCleanPatternsOutsideProject: false,
      dry: false,
      verbose: false,
      cleanStaleWebpackAssets: true,
      protectWebpackAssets: true,
      cleanAfterEveryBuildPatterns: [],
      cleanOnceBeforeBuildPatterns: [Array],
      currentAssets: [],
      initialClean: false,
      outputPath: '/Users/uros/Documents/Template/Code/template-chrome-extension/build',
      apply: [Function: bound apply],
      handleInitial: [Function: bound handleInitial],
      handleDone: [Function: bound handleDone],
      removeFiles: [Function: bound removeFiles]
    },
    ProgressPlugin {
      profile: false,
      handler: undefined,
      modulesCount: 5000,
      dependenciesCount: 10000,
      showEntries: true,
      showModules: true,
      showDependencies: true,
      showActiveModules: false,
      percentBy: undefined
    },
    EnvironmentPlugin { keys: [Array], defaultValues: {} },
    CopyPlugin { patterns: [Array], options: {} },
    CopyPlugin { patterns: [Array], options: {} },
    CopyPlugin { patterns: [Array], options: {} },
    CopyPlugin { patterns: [Array], options: {} },
    CopyPlugin { patterns: [Array], options: {} },
    HtmlWebpackPlugin {
      userOptions: [Object],
      version: 5,
      options: [Object]
    },
    HtmlWebpackPlugin {
      userOptions: [Object],
      version: 5,
      options: [Object]
    },
    HtmlWebpackPlugin {
      userOptions: [Object],
      version: 5,
      options: [Object]
    },
    HtmlWebpackPlugin {
      userOptions: [Object],
      version: 5,
      options: [Object]
    },
    HtmlWebpackPlugin {
      userOptions: [Object],
      version: 5,
      options: [Object]
    },
    ProvidePlugin { definitions: [Object] }
  ],
  infrastructureLogging: { level: 'info' },
  optimization: { minimize: true, minimizer: [ [TerserPlugin] ] }
}

Do you have any idea what can I try else. I plan to go one by one through webpack.config.js with the additions I made, but I don't know if my project is then going to be able to work without them.
The additions I made are:
var alias = {
  process: "process/browser"
};

module: {
    rules: [

       ...
      {
        test: /\.m?js/,
        resolve: {
          fullySpecified: false
        }
      }
    ],
  },
  resolve: {
    alias: alias,
    extensions: fileExtensions
      .map((extension) => '.' + extension)
      .concat(['.js', '.jsx', '.ts', '.tsx', '.css']),
    fallback: {
      "crypto": require.resolve("crypto-browserify"),
      "stream": require.resolve("stream-browserify"),
      "buffer": require.resolve("buffer/"),
      "https": require.resolve("https-browserify"),
      "url": require.resolve("url/"),
      "fs": false,
      util: require.resolve('util/'),
    }
  },
  plugins: [
    isDevelopment && new ReactRefreshWebpackPlugin(),
    new CleanWebpackPlugin({ verbose: false }),
    new webpack.ProgressPlugin(),
    // expose and write the allowed env vars on the compiled bundle
    new webpack.EnvironmentPlugin(['NODE_ENV']),
   ...
   new CopyWebpackPlugin({
      patterns: [
        { from: "src/_locales", to: "_locales" }
      ]
    }),
    new webpack.ProvidePlugin({
      process: 'process/browser',
    }),
  ].filter(Boolean),
  infrastructureLogging: {
    level: 'info',
  },
};

@durdevic, if you are not seeing any build folder, then your issue isn't really related to the zip file change, but likely due do with a config issue with Webpack. You can try posting a new issue to this repo, but given you have made local changes, I would suggest you narrow down which changes is causing the issue.

@cancan101 @durdevic I got exactly the same issue. I switched everything to TS. It fails silently too

So I had an issue in the index.jsx file with await. Once I turned that into .then().catch() form, I ended up building it with all my changes to the webpack, also with the .zip file.
Make sure that entry in webpack.config.js is properly set to the name of the file.
entry: {
    newtab: path.join(__dirname, 'src', 'pages', 'Newtab', 'index.jsx'),
    options: path.join(__dirname, 'src', 'pages', 'Options', 'index.jsx'),
    popup: path.join(__dirname, 'src', 'pages', 'Popup', 'index.jsx'),  <---- when I changed to .js I forgot to change it here back to .jsx

It's a bit of looking into code, but I think there might be something that you're overseeing @gilles-yvetot. For me it was additional use of process.env.NODE_ENV !== 'production' that didn't show the error when I was building for prod but passed on the DEV. Make sure not to make this mistake.
Thanks @cancan101 for the support!

Yeah, my issue got auto-solved at some point, I think I must have fixed the typing issues I had. But more importantly, it is still failing silently though

The npm run build command fails silently with no error and does not generate the zip, anything.

had the same thing. it turned out that it was failing because of my TS errors, so I had to switcht o transpile only mode
updated the webpack.config.js
to transpileOnly: true instead of transpileOnly: isDevelopment

This one worked for me.


Preprocess code chunk arguments

We need to choose an API for code chunks options.
Currently implemented
```{kernel_name, chunk_name, echo=False, ...}
def f(x): ...
```

Pandoc style fenced_code_attributes.
```{.kernel_name .chunk_name echo=False, ...}
def f(x): ...
```

RMarkdown style
```{kernel_name chunk_name, echo=False, ...}

notice the lack of a comma between kernel_name and chunk_name
def f(x): ...
```

In all three, the chunk_name argument is optional.
I prefer the first option because it matches Python's syntax and it seems more consistent to always separate with a comma.
It's also easier to parse than RMarkdown's  syntax, where the kernel and chunk name are not separated by commas, but the rest are.

Going with option 1, at least for 1.0. Willing to revisit.


PrimeNG Schedule

Hi, I am trying to integrate the primeNG schedule component into the Angular 4 template but am struggling to work out what to put where so that it works successfully.  I understand that it relies on FullCalendar and moment so I have included these into the package.json file but I am struggling with what to import where so that it all works together.
Are you able to provide an example
Many thanks
Alan

Sorry, in general this issue tracker isn't the best place for support with third-party components. Could you please direct your question to the primeNG community? Thanks!


Image data extraction

Database structure + Upload page display
Update picture Database from single quiz structure to Image + lookups + quiz structure
Convert pictures to .jpeg when storing (making it convenient to display on webpage)
Convert .heic with heicConvert and others with sharp
Using path to get the extension of file and determine which converter to use
Add app.get in Server.js to access pictures from database
Add displaying uploaded picture feature in ImageUpload.js, to confirm the pics are successfully uploaded

postImage + getImage

Separate the function of getting image to display from server.js (app.get()) to getImage() in controller.js and image.js router

Separate the function of posting single image to databse from createGame() to a function named postImage in controller.js. Based on property of this function, it can only be used when creating a game.

Checked that everything runs.


Vulnerability roundup 85: ant-1.9.6: 1 advisory [6.3]

search, files

[ ] CVE-2020-1945 CVSSv3=6.3 (nixos-20.03, nixos-unstable)

Scanned versions: nixos-20.03: a84b797b28e; nixos-unstable: 22c98819ccd. May contain false positives.

Bumping to 1.9.15, same as master & 20.09.

merged - closeme


Youtube

[ IMPORTANT: Please remove or replace everything between two square brackets ( [ ] ) before posting your issue. ]
Describe the bug
[ Whenever I exit a video in youtube or go back to youtube home, the channel name duplicates and shows another copy at the bottom. When I play another video, it goes back to normal. ]
Screenshots
When exiting a video or going to youtube home
 ]
When Playing a youtube video

System information

Rainmeter Version: [Latest Final Version]

Duplicate of #330, please follow the steps there for further help.


Adding the Metabase helm charts with custom concurrent user max limit variables

This will be EQ-CDC owned helm chart repo, and can install the metabase from here.

@sralla-eq Overall looks good. Please do the needed updates. Also, I would like to have all the KUBECTL commands that are used starting from installation to POD troubleshooting.

@rseshadri99 Would you like them to be in document in the git like a README.md file?

@sralla-eq Overall looks good. Please do the needed updates. Also, I would like to have all the KUBECTL commands that are used starting from installation to POD troubleshooting.

@rseshadri99 Would you like them to be in document in the git like a README.md file?

@sralla-eq Yes

@sralla-eq looks good.


Kyverno policies for OpenEBS

Description
On a Kubernetes clusters with kyverno policies(baseline or restricted) enabled, openebs deployment is failing
Restricted policy
Kyverno installation
helm install kyverno kyverno/kyverno --namespace kyverno --create-namespace --set podSecurityStandard=restricted --set validationFailureAction=enforce

NAME: kyverno
LAST DEPLOYED: Wed Sep 22 18:59:19 2021
NAMESPACE: kyverno
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing kyverno v2.0.3 😀

Your release is named kyverno, app version v1.4.3

We have installed the "restricted" profile of Pod Security Standards and set them in enforce mode.

Visit https://kyverno.io/policies/ to find more sample policies.

OpenEBS deployment
helm install openebs openebs/openebs --namespace openebs --create-namespace --set legacy.enabled=false --set cstor.enabled=true --set openebs-ndm.enabled=true --set rbac.kyvernoEnabled=true

Error: admission webhook "validate.kyverno.svc" denied the request:

resource DaemonSet/openebs/openebs-ndm was blocked due to the following policies

disallow-host-namespaces:
  autogen-host-namespaces: 'validation error: Sharing the host namespaces is disallowed.
    The fields spec.hostNetwork, spec.hostIPC, and spec.hostPID must not be set to
    true. Rule autogen-host-namespaces failed at path /spec/template/spec/hostNetwork/'
disallow-host-path:
  autogen-host-path: 'validation error: HostPath volumes are forbidden. The fields
    spec.volumes[*].hostPath must not be set. Rule autogen-host-path failed at path
    /spec/template/spec/volumes/1/hostPath/'
disallow-privileged-containers:
  autogen-priviledged-containers: 'validation error: Privileged mode is disallowed.
    The fields spec.containers[*].securityContext.privileged and spec.initContainers[*].securityContext.privileged
    must not be set to true. Rule autogen-priviledged-containers failed at path /spec/template/spec/containers/0/securityContext/privileged/'
require-run-as-non-root:
  autogen-check-containers: 'validation error: Running as root is not allowed. The
    fields spec.securityContext.runAsNonRoot, spec.containers[*].securityContext.runAsNonRoot,
    and spec.initContainers[*].securityContext.runAsNonRoot must be `true`. Rule autogen-check-containers[0]
    failed at path /spec/template/spec/securityContext/runAsNonRoot/. Rule autogen-check-containers[1]
    failed at path /spec/template/spec/containers/0/securityContext/runAsNonRoot/.'

Baseline policy
kyverno deployment
helm install kyverno kyverno/kyverno --namespace kyverno --create-namespace --set podSecurityStandard=baseline --set validationFailureAction=enforce

NAME: kyverno
LAST DEPLOYED: Wed Sep 22 19:28:05 2021
NAMESPACE: kyverno
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing kyverno v2.0.3 😀

Your release is named kyverno, app version v1.4.3

We have installed the "baseline" profile of Pod Security Standards and set them in enforce mode.

Visit https://kyverno.io/policies/ to find more sample policies.

OpenEBS deployment
 helm install openebs openebs/openebs --namespace openebs --create-namespace --set legacy.enabled=false --set cstor.enabled=true --set openebs-ndm.enabled=true

Error: admission webhook "validate.kyverno.svc" denied the request:

resource DaemonSet/openebs/openebs-ndm was blocked due to the following policies

disallow-host-namespaces:
  autogen-host-namespaces: 'validation error: Sharing the host namespaces is disallowed.
    The fields spec.hostNetwork, spec.hostIPC, and spec.hostPID must not be set to
    true. Rule autogen-host-namespaces failed at path /spec/template/spec/hostNetwork/'
disallow-host-path:
  autogen-host-path: 'validation error: HostPath volumes are forbidden. The fields
    spec.volumes[*].hostPath must not be set. Rule autogen-host-path failed at path
    /spec/template/spec/volumes/1/hostPath/'
disallow-privileged-containers:
  autogen-priviledged-containers: 'validation error: Privileged mode is disallowed.
    The fields spec.containers[*].securityContext.privileged and spec.initContainers[*].securityContext.privileged
    must not be set to true. Rule autogen-priviledged-containers failed at path /spec/template/spec/containers/0/securityContext/privileged/'

Expected Behavior
OpenEBS deployment with the rbac.kyverno enabled, it should have set the policies, which would have deployed openebs successfully.
Your Environment

Others:
GKE cluster with v1.20.9

@Nivedita-coder can you please check on this one?

Hey @nareshdesh,
You had installed the kyverno with a restricted and baseline flag, that's why it has blocked the deployment of OpenEBS. Baseline and Restricted come under  Pod Security Standards. For more details, regarding this, you can check this blog.
Here are the steps:

Install the kyverno in the Kubernetes cluster using YAMLs
kubectl create -f https://raw.githubusercontent.com/kyverno/kyverno/main/definitions/release/install.yaml
or via helm
After that install OpenEBS.
helm install openebs openebs/openebs --namespace openebs --create-namespace --set legacy.enabled=false --set cstor.enabled=true --set openebs-ndm.enabled=true --set rbac.kyvernoEnabled=true

Now, it'll work.
Thanks!

@Nivedita-coder,  what if an administrator has set these policies i.e Baseline or Restricted at a cluster scope. What additional policies does OpenEBS needs to set, in order for the openebs deployment to work.
As per the steps mentioned above, the OpenEBS deployment works even if we do not set  rbac.kyvernoEnabled=true
i.e

Install the kyverno in the Kubernetes cluster using YAMLs
kubectl create -f https://raw.githubusercontent.com/kyverno/kyverno/main/definitions/release/install.yaml or via helm.
After that install OpenEBS.
helm install openebs openebs/openebs --namespace openebs --create-namespace --set legacy.enabled=false --set cstor.enabled=true --set openebs-ndm.enabled=true

With the above behavior, it is not sure whether the openebs policy created, were making any difference at all

Closing this issue, Please reopen it if you are still facing the issue.


Error : x86_64/corenrn/mod2c/cal.mod is not thread safe and incompatible with CoreNEURON

Describe the issue
The model files can not be handled by nrnivmodl -coreneuron
Expected behavior
Successfully finish.
[...]
Mod files: "./cal.mod" "./kcRT03.mod" "./kdr.mod" "./matrix.mod" "./nafPR.mod" "./passiv.mod" "./rcadecay.mod" "./rkq.mod" "./vecst.mod"

Creating x86_64 directory for .o files.

COBJS=''
[INFO] Running: make -j4 -f /p/project/cjzam11/kitayama1/opt/nrn-master/share/coreneuron/nrnivmodl_core_makefile ROOT=/p/project/cjzam11/kitayama1/opt/nrn-master MODS_PATH=x86_64/corenrn/mod2c BUILD_TYPE=SHARED
NEURON { SUFFIX cal }
NEURON { SUFFIX cal }
NEURON { USEION ca WRITE ica }
NEURON { SUFFIX cal }
NEURON { USEION ca WRITE ica }
NEURON { SUFFIX cal }
NEURON { USEION ca WRITE ica }
Default NMODL flags:
Translating x86_64/corenrn/mod2c/cal.mod into x86_64/corenrn/mod2c//cal.cpp
INCLUDEing x86_64/corenrn/mod2c/geneval_cvode.inc
Translating x86_64/corenrn/mod2c/exp2syn.mod into x86_64/corenrn/mod2c//exp2syn.cpp
Notice: Assignment to the GLOBAL variable, "Inf", is not thread safe
Notice: Assignment to the GLOBAL variable, "Tau", is not thread safe
cvode_emit=0 cvode_not_allowed=0
Error : x86_64/corenrn/mod2c/cal.mod is not thread safe and incompatible with CoreNEURON
See details at https://neuron.yale.edu/neuron/docs/multithread-parallelizationTranslating x86_64/corenrn/mod2c/expsyn.mod into x86_64/corenrn/mod2c//expsyn.cpp
cvode_emit=0 cvode_not_allowed=0
cvode_emit=0 cvode_not_allowed=0
Thread Safe
Thread Safe
make: *** [/p/project/cjzam11/kitayama1/opt/nrn-master/share/coreneuron/nrnivmodl_core_makefile:225: x86_64/corenrn/mod2c/cal.cpp] Aborted (core dumped)
make: *** Deleting file 'x86_64/corenrn/mod2c/cal.cpp'
make: *** Waiting for unfinished jobs....
diff: x86_64/corenrn/mod2c/_mod_func.cpp: No such file or directory
Translating x86_64/corenrn/mod2c/hh.mod into x86_64/corenrn/mod2c//hh.cpp
cvode_emit=0 cvode_not_allowed=0
Translating x86_64/corenrn/mod2c/kcRT03.mod into x86_64/corenrn/mod2c//kcRT03.cpp
Notice: Assignment to the GLOBAL variable, "alpha", is not thread safe
Notice: Assignment to the GLOBAL variable, "beta", is not thread safe
cvode_emit=0 cvode_not_allowed=0
Error : x86_64/corenrn/mod2c/kcRT03.mod is not thread safe and incompatible with CoreNEURON
See details at https://neuron.yale.edu/neuron/docs/multithread-parallelizationThread Safe
make: *** [/p/project/cjzam11/kitayama1/opt/nrn-master/share/coreneuron/nrnivmodl_core_makefile:225: x86_64/corenrn/mod2c/kcRT03.cpp] Aborted (core dumped)
make: *** Deleting file 'x86_64/corenrn/mod2c/kcRT03.cpp'

The model files are checked out via:
git clone https://github.com/ModelDBRepository/35358

Is it still the user's job to appropriately change .mod files? It seems that even built-in mechanisms are affected too.

It is often the case with old mod files that ran on a a single thread, that GLOBAL variables were used to store temporary instance values to be used later. E.g In a DERIVATIVE block a rates function would be called to set several inf and tau gating rates and then those gating rates would be used in the following ode statements. This is an obvious race condition for multiple threads and thus not threadsafe. If suffices to declare the GLOBAL variables, used in that way, RANGE variables so there are separate  memory locations for every instance of them.  For other thread issues, the script mkthreadsafe`` can help. However, its solution to the above issue is to add the THREADSAFE``` keyword to the beginning of the NEURON block in the mod file which promotes the offending GLOBAL variables to thread instance variables. This is not sufficient for CoreNEURON GPU use. It is necessary for them to be RANGE variables.

@nrnhines what's the negative effect of changing automatically all those GLOBAL variables to RANGE ones? I've taken a quick look at the translated and created C code, cal.c, but I am not sure if I understand the difference immediately from the code.
I suppose threading support in NEURON has been around for some time, so I don't understand why there are so many thread-unsafe mod files.

@nrnhines what's the negative effect of changing automatically all those GLOBAL variables to RANGE ones?

GLOBAL variable has only one copy whereas RANGE variable is allocated one copy per instance (and hence more memory usage).
But, you are right that some of this can be automatically done. This is what we are precisely doing in new NMODL translator  but this is not yet ready to be used by end users.
So for now, I would suggest to change GLOBAL variables manually. If you need any help / need clarification in the mod file, let us know.