Sporadic "contents on disk are newer" issues when saving

VSCode Version: 1.1.1
OS Version: Fedora 23

The message appears randomly while writing code. It even makes saving the work cucumber-some at times.

@pythondetective are you working against a network share? anything special about your setup?

There is nothing special about my setup. I am writing to local disk.

@pythondetective when you do the "Compare" command can you grasp what the modifications are? Are you running another process in the background that modifies files?

I am not running another process in the background that modifies files. Sometimes, there are no modifications at all, just the same file. The problem arises whenever VSC takes long time to react to Ctrl+S.

@pythondetective and then when you click on the "Compare" action, can you see what changes did occur meanwhile that VS Code blames?

Sometimes, "Compare" action takes way too long time to get to compare mode and shows the same file on both side with no changes. Sometimes, "Compare" action is quick and show changes in both file.

@pythondetective how do you notice that the save takes long?

By dot in front of file name in the title bar.

Same issue here. But my situation is different.
I turn on auto save when lost focus. I make some changes and then go to terminal reformat the same file. When I go back to vscode, it won't reload the disk changes sometimes, in which case if I make changes to it again, it will promote the messages. And click compare doesn't help, it will keep promoting the messages and the two way comparison won't show up.

Is this with files in a workspace (folder) or outside / when you do not open a folder?

Yes, it's the a file in my workspace.

I'm having a similar issue. I'm just editing markdown files that are shared through dropbox. However, I'm the only one with access to that dropbox directory. I did some digging and figured out that autosave was not happening, which meant that if I left VSCode open on my home desktop by mistake and then later attempted to edit the same files on my laptop, when I returned and closed VSCode on the desktop, that I would get this message. For my case, if the autosave works properly and the changes are merged in, I think it will probably work for me.
Is it possible that your autosave actually is working, but for some reason VSCode is not recognizing that it is the one that saved last?

If you do not see the dirty indication in the editor it means the file is saved by VS Code if it was dirty before. However we use the modification timestamp of the file to find out if the contents on disk are newer. It looks like we might have to change this strategy and use a content hash instead (https://github.com/Microsoft/vscode/issues/919). Maybe the mtimes are not working properly in some cases.

I'm still testing around on it this morning. I've not gotten autosave working.  Nothing special. I'm doing the same on the laptop sitting right next to me. I can see when changes get pushed from the one computer to the other if a save actually happens. So my issue may be some sort of weird crossover issue from a config problem or something.
Any suggestions on stuff I can try to get more useful data for you? I'm stuck at home with a stomach bug, so....

@williamwgant how does your Code settings look like?

I see a dirty indicator on the file itself. The settings.json for the workspace and the settings.json in my user directory both are as follows:
{
"editor.wrappingColumn": 0,
"editor.selectionHighlight": false,
"files.autosave": "afterDelay",
"files.autoSaveDelay": 1000
}
Umm. Something I just thought of. Is the specified delay in milliseconds? Or seconds? Cause the latter would explain some things.

@williamwgant there is a typo in your setting, it should be files.autoSave and not files.autosave

Aww man. That's embarrassing.
So I've tried since and can't replicate the issue. I don't seem to be able to move fast enough to cause it. I even tried disconnecting the laptop from wireless and doing the changes. I'm not getting burnt now at all.
My podcast partner (on complete developer podcast) is going to give me a hard time for screwing up casing like that. We've also been burned on show notes because I didn't have the config setting named properly, so his stuff autosaves and mine doesn't. That's a huge pain point you just fixed for me, sir.
I presume the issue still exists, but probably needs a larger change set to actually manifest itself. I'm not sure of a good way to prove it though.

No worries, I filed https://github.com/Microsoft/vscode/issues/7252 to warn when this happens in the editor.

@forethoughtde do you run with any extensions installed?

@BusyJay mind opening a new issue for your case? we have a 2 second window where we ignore changes made to a file outside VS Code. maybe you are fast enough to switch to the terminal and run your format command in under 2 seconds?

There is no problem with newer version. @bpasero

@forethoughtde so you say this issue is fixed for you?

Yes, it is got fixed for me.

Hi @bpasero, I'm still getting this error, however, I'm running it on a network share.

I'm getting this error running locally - it is happening sporadically.   I'm using vscode 1.8.1. Not sure if this will help shed light on the subject, but here's my workspace settings.json:
{
    "typescript.check.workspaceVersion": false,
    "editor.fontFamily": "Fira Code",
    "editor.fontSize": 14,
    "editor.fontLigatures": true,
    "editor.lineNumbers": "on",
    "editor.tabSize": 3,
    "editor.renderIndentGuides": true,
    "editor.rulers": [],
    "editor.formatOnSave": true,
    "files.autoSave": "off",
    "editor.mouseWheelZoom": true,
    "typescript.check.tscVersion": false,
    "php.validate.executablePath": "C:\\Program Files (x86)\\PHP\\v5.6\\php.exe",
    "auto-close-tag.activationOnLanguage": [
        "html",
        "xml",
        "php"
    ],
    "macros": {
        "collapseFoldersAndCloseFiles": [
            "workbench.action.closeAllEditors",
            "workbench.files.action.collapseExplorerFolders"
        ]
    },
   "files.exclude": {
      "node_modules/": false,
      ".vscode/": false,
      "config/": false,
      "dist/": false,
      "external/": false,
      "typings/": false,
      ".deployment": false,
      ".gitignore": false,
      "README.md": false,
      "tsconfig.json": false,
      "typings.json": false,
      "**/.git": false,
      "package.json": false,
      "gulpfile.js": false,
      "build/": false,
      "*debug.log": false,
      "**/.htaccess": false,
      "**/favicon.*": false,
      "sys": false,
      "src/main.ts*": false,
      ".htmlhintrc": false
   },
    "search.exclude": {
        "dist": true,
        "build": true,
        "public/js/": true
    },
    "toggleexcludedfiles.statusBar.enabled": true
}

This is occurring for me as well. I have a remote directory mounted via SSH. It happens about every other time I save a file.
Version 1.9.0

I'm still getting this error
Version 1.9

Still getting this as well

I moved from vscode to sublime3 only because of this issue..very sad

@rashnk Something that's working for me as a temporary fix is the ftp-simple extension for Code.

Im working with local project folder only, I suspect this behavior is by an installed extension, im going to disable all of them and clean installation

@rashnk any luck?

Who wants to help: see here https://github.com/Microsoft/vscode/issues/13665#issuecomment-283320421

@forethoughtde @ryekerjh @rashnk @BrianJHodge @johnhamm  does it still reproduce with our latest insider builds? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders

@bpasero new insider build fixed this annoying thing for me, thank you!

That is really good news, I hope it stays like that.

Still hosed using OS X with QNAP NAS (running insiders)
Still getting bad descriptors content on disk newer. Seems to be purely a timing deal near as I can tell. Haven't had time but would like to help work on this. Any suggestions of where to start?
thanks in advanced @bpasero

@origin1tech where do you see the bad descriptors error?

@bpasero  on any save, like every one which is why it's a deal breaker.

@bpasero can you point to me in the vscode source where file saves occur? Thinking about firing up from source and tinkering with it.

@origin1tech that would be nice, the saving code is here: https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/files/node/fileService.ts#L313
Since I suspect this to be a node.js issue, maybe we could also try to distill this into a node script? After all we call fs.writeFile() somewhere in the end.

@bpasero O.k. I will look at this today and monkey with it. Give me a few hours.

@bpasero ...alright I'm working on it now going to focus on non-bom method then go from there.

@origin1tech the error about the contents on disk being newer is actually already thrown here: https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/services/files/node/fileService.ts#L623
The idea is that if the file we have opened in the editor has a smaller Stats.mtime than the version on disk (e.g. someone modified it since), we throw this error.
What would be interesting to find out is who and why the file is edited.

@bpasero I see, well I have a couple hours here I'll see what I can do. strong node background but haven't ever looked at code src may take a few go's at it to get acclimated, but I'll give it appropriate attention, can't be the only one experiencing this. Let u know how far I get in a bit...

@bpasero once I touch a file the descriptor errors go away. In fact
If I see this right changes are watched for and the focus file for lack of better term is stored in users (in case of OS X) ~/library/application support/.... then that's written to the actual absolute path.
O.K. better breakdown on what's happening here. The descriptor errors are only occurring after a move. once the IDE touches them once the error goes away.
If I open a terminal while the IDE is OPEN and I just run like:
 $ touch some-file.ts

The editor will detect the change and I won't get an error. However moving a file into that same dir using the finder and dropping it in that folder via the finder will cause an error but only the first time it is opened from within the IDE.

@bpasero
If you suppress the backup file from being cached at  /Users/Bob/library/application support/code-oss-dev/Backups/fac5c5aa68..../file/fac5c5aa68.... (on Mac in w/ Dev VSCode running).
Then save directly the error goes away. Again it only occurs when files are moved via finder and then opened in IDE. After first open and "compare" it's fine.
Seems to be something with the backup/cached file conflicting when you then go to realize the file and actual write it out on that first save.
Have to look more at it later this week. Oh and writing a little script to touch all the files seemed to solve it as well but that's hacky and I didn't test it fully but it did circumvent the EBADF nag.
Again I'll look more into it in a day or so.

tested after i disabled all extensions - no issue,
updated vscode to the latest. enabled extensions for my ionic2 workspace, now its working fine without any issue @rvanzon @BrianJHodge @bpasero

interesting. any idea which extension? probably not huh. I'm going to
continue with this, this weekend. I have some pretty good ideas now but ran
out of time earlier in the week.
On Fri, Mar 17, 2017 at 8:10 PM, Rashid<EMAIL_ADDRESS>wrote:

tested after i disabled all extensions - no issue,
updated vscode to the latest. enabled extensions for my ionic2 workspace,
now its working fine without any issue @rvanzon
https://github.com/rvanzon @BrianJHodge https://github.com/BrianJHodge
@bpasero https://github.com/bpasero
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/7025#issuecomment-287512289,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABswC7TnC5esUoWSD0fH_LMIqu0tABOfks5rm0scgaJpZM4IppzZ
.

@rashnk awesome to hear that, thanks for testing

@rashnk https://github.com/rashnk tried your suggestion disabled
everything. Still the same behavior I'm rather certain at least in the case
of OS X to a NAS the issue lies with the cached backup and then when it
gets realized basically written out. It's a timing deal.
I need to get some spare time again this week to nail it down but near as I
can tell it seems the temporary cache of the file when written out already
things the destination is newer than it is.
When I logged it out it seems like Code somehow sees that it's at a newer
date than the actual file is.
Yes that's a bit captain obvious I get that but it became very apparent
when I logged out all the times from the file stats. Adding some custom
scripting touching files and so on did clear it up but again that's super
hacky at this point as to push that to the core without know why it fixes
it a bit risky. Anyway this is really something I want fixed so I'll keep
bangning on it just hard to find the time. If someone else gets to it first
I thank you in advance :)
On Fri, Mar 17, 2017 at 11:43 PM, Benjamin Pasero<EMAIL_ADDRESS>wrote:

@rashnk https://github.com/rashnk awesome to hear that, thanks for
testing
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/7025#issuecomment-287520941,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABswC1ffkfSBV5RFKV2QcWsDdg_6KA6Uks5rm30dgaJpZM4IppzZ
.

@origin1tech  did you update the vscode to latest, try that too

Thanks for all the hard work on this issue!

Today I started getting this exact same error when I edit a .css file and save it. I noticed that when I save the format of my CSS code gets changed:
.container {
  display: flex;
  border: 10px solid mistyrose;
}

changed to
.container {
  display: flex;
  border: 10px solid mistyrose; }

@cr101 is this file locally or on a remote network? is there a chance that the file is being changed by another process maybe outside?

@cr101 are you using node-dev maybe? I had a similar problem with it. Switching to nodemon fixed it.

@bpasero The .scss file is on my local machine
@rvanzon I am using create-react-app and the error appears after I run npm start which runs the watch commands below and when I save changes made to the .scss file. The interesting thing is that the error is random and it doesn't always occur on every .scss file save.
"scripts": {
"watch-css": "npm run build-css && node-sass src/ -o src/ --watch --recursive",
"start-js": "react-scripts start",
 "start": "npm-run-all -p watch-css start-js"
}

Here is the link to the Create-React-App Adding a CSS Preprocessor

@cr101 I had the same with node-dev, also random (but a lot), I have the idea the files are maybe changed twice (maybe eslint?). The first time vscode reloads the changes, in that time it's changed again by the watcher. I am not sure.
Maybe you can fiddle around with create-react-app's timing or turn of eslint, just to test.

If someone can give me exact steps how to reproduce this in a workspace I could have a look 👍

@bpasero Ben read my comments again I outline it a little but basically it is really obvious when you debug the ctime, mtime etc. Just haven't had time to finish tracking it down but when it actual goes to realize the write a watcher or something has already touched the temp/cached file.
I got close with it but ran out of time and of course don't know enough about the source. When I did some manual things updating times I was able to circumvent the problem but that obviously isn't a fix but a hack.
Feel pretty confident it has to do with the cached file getting touched by Code itself then the issue presents itself when the file is actually realized  and written out. Times don't line up.
May seem a bit captain obvious there but that's what it appeared to be. I should have some more time this weekend to take this further...
As far as recreating I'm not sure that's possible unless you have a Mac and a NAS. In my case a QNAP. I say that because on a friends Win box and FreeNAS I didn't see the issue.

@origin1tech I see, so you are working against a network share? I was hoping for a repro that actually happens when working locally, that is why I was asking for some steps for me to reproduce that does not involve setting up a network share.

Oh my bad Ben missed that....
On Thu, Apr 6, 2017 at 9:47 AM, Benjamin Pasero<EMAIL_ADDRESS>wrote:

@origin1tech https://github.com/origin1tech I see, so you are working
against a network share? I was hoping for a repro that actually happens
when working locally, that is why I was asking for some steps for me to
reproduce that does not involve setting up a network share.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/7025#issuecomment-292234710,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABswC3Z089Mr3P2RTCjwjTRZAN3eJn88ks5rtRc5gaJpZM4IppzZ
.

There is still https://github.com/Microsoft/vscode/issues/13665 specifically for network share issues.

Yeah I've seen it. I'll try and put some more time into this soon. It is
truly something I need fixed but paying bills gets in the way :)
On Thu, Apr 6, 2017 at 9:54 AM, Benjamin Pasero<EMAIL_ADDRESS>wrote:

There is still #13665 https://github.com/Microsoft/vscode/issues/13665
specifically for network share issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/7025#issuecomment-292236568,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABswC7wwNWbjiyD4SgtKovHAYOej3A7xks5rtRjGgaJpZM4IppzZ
.

Getting this a lot lately, on 1.14

After update to 1.15.1 I'm getting this error constantly. Before that the same solution had no problem.

1.16.1 has the same issue.


Remove Extra Split Cell Action in Notebook Cell Taskbar

Fixes #18019, which i assume is just a result of a merge conflict issue from the merge.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 48.19%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
14520

Relevant Lines:
28627

💛  - Coveralls


feat: Datepicker & Date-time picker

Summary
Datepicker component with two variants : Datepicker and date with time picker
ADO Story
https://dev.azure.com/Kyndryl/Shidoka - Bridge Design System/_workitems/edit/1238186
Checklist

[x] Used Conventional Commit messages as outlined in the contributing guide.

[x] Noted breaking changes (if any).

[x] Documented/updated all props, events, slots, parts, etc with JSDoc.

[x] Ran the analyze command to update Storybook docs.

[x] Added/updated Stories with controls to cover all variants.
[x] Added/updated a basic unit test, at least, for each component.
[x] Added/updated the Figma link for the Story's Design tab.
[x] Added any new component exports to the src/index.ts file

focus stays when type by keyboard or arrow up / down

Only after there's already an entry. The first time I try to type when it's empty, it loses focus.

focus stays when type by keyboard or arrow up / down

Only after there's already an entry. The first time I try to type when it's empty, it loses focus.

yeah its weird don't know whats happen there. Can you help me out here. Think updating component on-input cause this issue might be.

yeah its weird don't know whats happen there. Can you help me out here. Think updating component on-input cause this issue might be.

I don't have time to dig into it, but it might be related to setting inputEl.value on updated. Try taking that out.

sure I am looking into it.

yeah its weird don't know whats happen there. Can you help me out here. Think updating component on-input cause this issue might be.

I don't have time to dig into it, but it might be related to setting inputEl.value on updated. Try taking that out.

sure I am looking into it. why we need inputEl.value here. Can we remove for type="date"

yeah its weird don't know whats happen there. Can you help me out here. Think updating component on-input cause this issue might be.

I don't have time to dig into it, but it might be related to setting inputEl.value on updated. Try taking that out.

sure I am looking into it. but removing inputEl.value not worked.

I tried looking all possibilities but not sure why its losing focus. Need to deep digger may be something happened about LIT component update lifecycle but its not blocking anything.

:tada: This PR is included in version 1.0.0-beta.51 :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 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Mathematical mean functions

Reported by kdavies on 17 Jan 2014 00:39 UTC
This ticket is to add a package of mathematical mean functions to Modelica.Math.  They were necessary for a model library I created and maybe they are useful to others.

Migrated-From: https://trac.modelica.org/Modelica/ticket/1400

Comment by hansolsson on 17 Jan 2014 09:20 UTC
I think we need to consider these in more detail: first and foremost exactly what we need in MSL (do we need mean-functions at all? other similar functions? the median? as blocks as well?), and then where to place these functions.
Looking at the proposed implementation I see two issues:

No guard against unnecessary overflow. The product of all elements is likely to overflow for longer vectors (just think of a geometric mean of a vector of 100 values each between 50 and 100)- there are ways of handling that, but it makes the algorithm longer - especially if you want to avoid any unnecessary rounding errors as well.
Too many ifs. Having a special case for size=2 is not needed, and I found it more confusing for the harmonic mean.

Comment by Kevin Davies on 17 Jan 2014 15:56 UTC
I understand.  I was hesitant myself (re: if and where they should be included in MSL), but I thought I may as well share them.  You can close this if you want.  If you decide to take it, then I'll improve the implementation.

Point to @kdavies4.

@kdavies4 @HansOlsson Can this issue be closed now that there is Mean, RectifiedMean, ContinuousMean, RootMeanSquare, Variance and StandardDeviation in Modelica.Blocks.Math of MSL v3.2.2?

I don't think we can close this just because there are blocks for Mean etc; since these functions could be used to perform analysis inside algorithms.


What about default config to config.jsonc?

Then I think I can edit it with lsp

It's be a breaking change :/

Sorry to bump this old and closed thread, but if anyone stumbles here, like me, wanting to have config as .jsonc for editor reasons, you can simply create a symbolic link like this:
ln -s config.jsonc config
This way you can edit config.jsonc, but waybar will read config, which is just a reference to config.jsonc with a different name.


Frank eitt fix

~format

Reason for changing the mechanism to check if table element is empty: Take the group object table for example. In extreme cases, one might want to add a table entry with no group addresses (i.e. ga_len will be 0). In this case, the old mechanism will think that the entry is empty (which is wrong). I don't think an entry with no group addresses makes sense, but that's how EITT is adding entries to the tables so...

Is it worth changing all occasions of OC_DISCOVERABLE to something like OC_DATAPOINTS?


Update the doccomment for the return value

From internal feedback -- the return values for Promise are sometimes complicated, and the current explanations might be hard to understand immediately. Let's update it.

@lukesneeringer Do you know if we're still working on this?

Won't fix since we'll move to TypeScript generator with a different documentation syntax.


Splitting Course 1 into Course 0 and Course 1

Proposed changes
Divided Course 1 into Course 0 and Course 1
Fixes # (issue)
Type of change

[ ] Bug fix (change which fixes one or more issues)
[ ] New feature (change which adds functionality or features to the course)
[ ] Translations (change which adds or modifies translations of the course)
[x] Documentation (change which modifies documentation related to the course)
[ ] This change requires an update to the course's z/OS environment

Checklist:

[x] I have read the Contributing Guideline
[x] I have included a title and description for this PR
[ ] I have DCO-signed all of my commits that are included in this PR
[x] I have tested it manually and there are no regressions found
[x] I have commented my code, particularly in hard-to-understand areas (if appropriate)
[x] I have made corresponding changes to the documentation (if appropriate)

Signed commits in other pull request.


Improve PagerDuty plugins

Hey, I just made a Pull Request!
This PR improves the pager duty plugin in a couple of ways:

Allow trigger button to be rendered without pagerduty key and remove its optional link design;
Adds tests to the TriggerButton and fixes tests for other components;
Refactor card and button not to rely on shared state;
Allows the IconLinkVertical (used in HeaderIconLinkRow) to receive onClick and do no spread props.

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

@Rugvip wanna have a look and merge?

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131

Tugboat has finished building the preview for this pull request!
Link:

https://pr4681-1a14ybw8fa3xa7ufviganprwjw6tqlev.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/60365db6fcb22df7175ee131


infer shapes for ConvTranspose with output_shape

added lit tests for both pad and output_shape attributes
Signed-off-by: Soren Lassen<EMAIL_ADDRESS>

I'm abandoning this PR in favor of PR #1771


Remote kernel + token

When configuring the jupyter kernel gateway to accept only requests with token in headers and configuring hydrogen like this:
[{"name": "Remote Spark notebook", "options": {"baseUrl": "http://myIp:8888",  "ajaxSettings": {"requestHeaders": {"Authorization": "token tokenValue"}}}}]
I'm able to connect to this Remote spark notebook, choose to launch a new session, then choose Python2 kernel for instance, but then:

kernel tries to reconnect then fails
an 401 error is sent by the gateway

It looks like if the token authentication is used for the first steps but not for the next ones.
For instance, if the token is wrong in the hydrogen settings, I'm not able to connect & pass the first steps.
So, currently I can connect to the gateway, but not open a kernel.

@fsausset I can reproduce this, but I'm at a loss as to why this is happening. As you can see in the reference above, I've posted on the jupyter-js-services tracker to see if they have any suggestions.

Thansk!
Indeed, it's not clear if it comes from client or server side...

@nikitakit Any news from where it could come from: hydrogen or jupyter-js-services?
I can do some more testing if needed, following your instructions.

As I see it, the issue is somewhere between the jupyter-js-services, jupyter notebook, and jupyter kernel gateway projects. Based on the replies in the issue linked above, there currently isn't any solution other than a change of approach (e.g. using http basic auth via nginx to add security, or maybe using ssh tunneling).
I personally would prefer it if secured connections were transparently handled by an upstream library, instead of requiring hydrogen to package a workaround for this issue.
Connecting to secured servers is definitely a real issue, but I currently lack the bandwidth to code up a solution for it. I'm leaving the github tickets open for now.
(Also, adding a link to https://github.com/nteract/rx-jupyter/issues/15 because it may be relevant)

Thanks for the information and links.
I think that I'll use the http basic auth and wait for a better solution from the jupyter side.
I'm indeed interested in using hydrogen + jupyterHub + authentication when it will be available.

The issue is alsothere with a basic http auth through a nginx proxy!
I can connect/launch a kernel, but then it's not usable as it's always in "reconnecting" state.

Did you specify the correct values for both baseUrl and wsUrl? See https://github.com/jupyter/kernel_gateway_demos/blob/master/node_client_example/docker-compose.yml#L35

I forgot wsUrl... Basic http auth is now working. Thanks!

To recap the discussion so far: The notebook's password-based auth is not designed to run anywhere other than the browser. Alternative approaches to secure connections include HTTP basic auth, as well as ssh tunneling.
However, I think this situation is quite unsatisfactory. It should really be possible to connect to a notebook server without having to reconfigure the server hosting. I was hoping that the Jupyter folks would eventually enable to a token-based auth system that works for this purpose, but there is no indication that this will happen soon (if at all).
In the meantime I wrote a hydrogen-auth plugin that should enable logging in to notebook servers. Would anyone here be willing to try it out and test if it works? Unfortunately jupyter-js-services doesn't seem to be targeting our usecase, so the code involves some heavy monkey-patching to get things to work.
/cc @lgeiger @rgbkrk
The usage for the plugin is:

Activate hydrogen first
Then select the "Hydrogen Auth: Login to Gateway" option
Pick a gateway
Double-check that the login URL is correct
Enter the password
Then use "Hydrogen: Connect to Remote Kernel" and check that it has started working. (Note that there is currently no error handling for incorrect passwords)

Token authentication in jupyter notebook is in progress: https://github.com/jupyter/notebook/pull/1831
/cc @minrk

As for the jupyter-js-services monkey patching, feel free to raise an issue with them to see if they have a way to provide what you need (or a reasonable way to workaround).

Now that #542 is merged, users of notebook server v4.3 (or later) will be able to establish secure connections by specifying a token parameter inside options, e.g. [{"name":"local notebook", "options":{"baseUrl": "https://localhost:8888", "token":"secret"}}]. A big thanks to the upstream teams for addressing this use-case!
Other methods such as hydrogen-auth, http basic auth via proxy, and ssh port forwarding continue to be available. Self-signed certificates remain unsupported for all methods, until https://github.com/nodejs/node/pull/9139 (or https://github.com/nodejs/node/pull/8334) make their way into an Atom release.
I would like to close this issue as resolved. Please let me know if you still have problems using hydrogen with secure servers.

@nikitakit can you please update your comment to have http://localhost:8888 instead of https://localhost:8888? I've just spent half an hour trying to debug why it stopped working after I've copied your line that seemingly differed only in "token": "secret". http seem to be the default for jupyter-notebook

@alesguzik Want to make a pull request to change this?

@lgeiger it is correct in the docs, it's just that while debugging I google-landed at this issue thread, and used code from the comment above. I've asked author to update his comment, so people like me won't spend time trying to figure out what's wrong

:+1: I'll update it


Fix flaky test in datacollector attachments manager.

Taking the fix in https://github.com/Microsoft/vstest/pull/752.


alpha_s Classification with GAN

You can use GANs for image classification, but typically GANs are used for generating images rather than directly for classification. However, you can use GANs to augment your dataset by generating more training images, which can then be used to train a classifier.


Replace anypb.New with MessageToAny

Please provide a description of this PR:
Use the MessageToAny function defined by Istio to convert other proto type messages into Any types, thereby simplifying the code and unifying the interface

@Chen-Xintong: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
03cf3add8eb55e1659604ce3b4c23bf1c722284a
link
true
/test lint

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Scroll or smooth attribute error

Hello,
Thanks for this package!
When adding a scroll function like
<Link
  to="/#start"
  scroll={el => el.scrollIntoView({ behavior: 'smooth', block: 'end' })}>
  start
</Link>

I get this error and the function will not fire
Warning: Invalid value for prop `scroll` on <a> tag. Either remove it from the element, or pass a string or number value to keep it in the DOM  (...)
adding the "smooth" attribute like your example will produce this error and no animation is triggered
Warning: Received `true` for a non-boolean attribute `smooth`. If you want to write it to the DOM, pass a string instead: smooth="true" or smooth={value.toString()}. (...)
from my package.json:
"react": "^16.2.0",
"react-router-dom": "^4.2.2",
"react-router": "^4.2.0",

Am I missing something? Ideas?
Thanks

It sounds like your using an old version of react-router-hash-link. You need to use version 1.2.0 for scrolling features.

oh great, that's it! Thanks a lot!


Angular Demo?

Nice work! Very interested in making this work with angular-medium-editor. Do you have a demo/sample available?

Nope. Feel free to make one.

+1


fix: plugin-menu in bulk mode

Fix #297

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

GitHub release
v2.2.0

Your semantic-release bot :package::rocket:


Add gutter to mark lines and fields with errors

to display help
to mark lines and fields with errors


add VSCode and CMake instructions

Adding a settings.json file to the .vscode directory. This integrates with the CMake extension by Microsoft and will help users debug and run samples and tests.

The file is ignored in the .gitignore so if they paste SAS keys or other things in there, it won't get pushed in a branch.

/azp run c - client - ci

The file is ignored in the .gitignore so if they paste SAS keys or other things in there, it won't get pushed in a branch.

I don't think the file is being ignored. I made changes to my .vscode/settings file and they are showing up in git diff:

Maybe we need to add the following to the .gitignore file, or find some other way to make sure folks aren't accidentally checking in anything within their local .vscode folder.

.vscode/.

https://github.com/Azure/azure-sdk-for-c/blob/e33b40000cc8593d3eb8570d3f3970bcfd129dc9/.gitignore#L307-L308
That was precisely the reason why we added it to the .gitignore to begin with and why checking in such files (build, task, settings json, etc.) was considered problematic.
@danewalton, can you please verify that changes to such files are actually ignored by git, and otherwise make any of the necessary .gitignore changes to make that happen?

@ahsonkhan yea we have an issue here that I think Cris opened an issue for. We might have to create some vscode-config folder and put the files in there where people can then copy over the settings.json file to their .vscode


Option service-node-port-range gets ignored

Environmental Info:
K3s Version:
k3s version v1.29.3+k3s1 (8aecc26b)
go version go1.21.8

Node(s) CPU architecture, OS, and Version:
Linux potato 5.10.0-28-amd64 #1 SMP Debian 5.10.209-2 (2024-01-31) x86_64 GNU/Linux

Cluster Configuration:
Single Node
Describe the bug:
According to https://docs.k3s.io/cli/server the cli option service-node-port-range can be passed as CLI option or can be configured in /etc/rancher/k3s/config.yaml, for me it's configured in file as follows
…
service-node-port-range: 1000-32767

but in newer version (can't triangulate right now) it fails to apply this configuration, as seen when creating a NodePort:
# kubectl create svc nodeport example --node-port=1010 --tcp=1010:1010
error: failed to create NodePort service: Service "example" is invalid: spec.ports[0].nodePort: Invalid value: 1010: provided port is not in the valid range. The range of valid ports is 30000-40000

In newer version? Yes, service with that NodePort did already run and was used by other services that now started to complain because the service is not reachable anymore.
Steps To Reproduce:

Installed K3s: v1.29.3+k3s1 as Systemd Service
Append ServiceNodePortRange to /etc/rancher/k3s/config.yaml: echo service-node-port-range: 1000-32767 > /etc/rancher/k3s/config.yaml
Restart K3s: systemctl restart k3s
Create NodePort: kubectl create svc nodeport example --node-port=1010 --tcp=1010:1010

Expected behavior:
NodePort Service should be valid and created
Actual behavior:
Port Range validation fails.

Works fine for me, did you figure out what your problem was?
brandond@dev01:~/$ kubectl get node -o yaml | grep service-node-port-range
      k3s.io/node-args: '["server","--service-node-port-range","1000-32767"]'

brandond@dev01:~$ kubectl create svc nodeport example --node-port=1010 --tcp=1010:1010
service/example created

yes, was a very big Layer-8 error. Something a long the lines of check who you're talking with. That's why I just closed the issue ;)


Add .clang-format to keep coding style consistent.

Add new coding style for librealsense project. The coding style will keep the code base clean.
Contributors will run clang-format before submitting PR.

clang-format-3.8 -i <file.h> <file.cpp>

clang-format automatically corrects files to meet coding style.

@ddiakopoulos Hi, clang-format is the only practical solution to keep the code base clean.
I customized .clang-format to match the existing code base as far as possible.
If you want to change some rules, please let me know.

Not every contributor is willing to use clang-format (nor have even have it installed). I have seen clever things like pre-commit hooks and bundled format exes for windows users, but it's a bit hacky. The style you provide is closer to the actual style we use in practice (but still some major exceptions where what it does is simply wrong/bad looking), but again, I am not personally willing to merge this because it imposes more restrictions on contributing. For 6000 lines of C++ I am not convinced a formatting tool helps in a meaningful way.

You (owner) can define policy. It's up to you whether to impose restriction or not.
If I'm you, I'll merge PR with broken style, and then sometimes run clang-format to prettify code base.
Current code base uses 2 space indent or 4 space indent or even 5 space indent.
It's not black and white decision. You can get both flexible contribution rule and pretty code base.
On the line which you think some major exceptions, please comment what you want. I'll fix it.

@ddiakopoulos, I fixed all you concerned except for struct singleline issue.
could you review again?

We will investigate the use of this .clang-format file at a later date.


No d3 format available for 'bubble size' option in bubble chart.

Screenshot

Description
No d3 format available for 'bubble size' option in bubble chart. When I hover over the bubble chart, I want to see 'Matter Days' Metric (simply a count) in the ",d" format. However, there is no option for this in the explore chart page, just options to format the x-axis and y-axis.
I have also tried creating a metric and setting the format as ",d" but it still doesn't change the format that shows on the hover.
Design input
Does anyone know how to get around this? Or is it a bug?
Thanks in advance!

I don't think we should consider this a bug, but more of a (perfectly reasonable) feature request. I'll convert this to an "Ideas" discussion, and I hope we can get anyone from the community to take a crack at opening a PR for it. If anyone can do so, please link it here, and I/we will be happy to review it!


chore: Bumps all the uds core versions to 0.25.0 and updates deployment docs

Like this! https://github.com/defenseunicorns/uds-common/blob/main/config/renovate.json5
Sounds like a tech debt week sort of thing, and helps close an issue in this: https://github.com/defenseunicorns/leapfrogai/issues/727

LGTM.
Something I would like to do in the future is use Renovate to handled keeping us honest and up to date with dependencies likes this.
Ex) # renovate: datasource=github-tags depName=defenseunicorns/uds-cli versioning=semver example source


Unit test a directive: add an isolated scope test

I think that using an isolated scope is more common scenario than ng-model. I would add it to the scenario + not sure that ng-model should be mandatory. (I am willing to add a PR here!)

I totally agree, looking forward to reviewing your PR

Hey,
A small question regarding this feature - do you think I should leave the current directive with a mandatory ngModel, and add a new directive that uses isolated scope? If so, should I leave it in the save directive test-file? Another option is to add the isolated scope to the current directive and remove ngModel...

@yanivefraim hmmm, it may be useful to have both examples. With the addition of .isolateScope() in version v1.2.3 perhaps a new file would be the cleanest way to present the differences in testing (isolatedDirective.md ?). What pattern are you going to suggest developers use for testing isolate scope? One pattern I've seen is moving logic such as adding a $watch scope into the directive controller so it can be more easily unit tested.

@daniellmb ok, a new file (isolateDirective.md) sounds cool. One thing we have to take into consideration is how those files (such as 'controllerAs.md') will look on the main readme.md page.
Regarding a test pattern - I uses isolated scope test like this:
var isolated = element.isolateScope();
expect(isolated.item).toBeDefined();
Not sure what did you mean when said: "adding a $watch scope into the directive controller" (??)

A bit of an OCD edge-case but for times when you want to unit test that a directive is adding a $watch as expected: http://stackoverflow.com/questions/17371836/how-to-unit-test-isolated-scope-directive-in-angularjs


Changed root size in growvols defaults

Since we're creating a swapfile when a swap partition isn't present due to https://github.com/openstack-k8s-operators/edpm-ansible/pull/156, let's extend the root partition size to reserve some space for the swapfile itself.

recheck


Update Polish translation

closing older translation related PRs, feel free to open an issue if something needs to be pulled from POeditor. thanks!


Pytorch 1.7 and conda env name.

funny that the conda env is called pytorch-1.6 but when it runs conda, since now they released the 1.7 version, it will install that one. I would suggest to call the environment ocnn honestly.

FYI: it passed the test also with Pytorch 1.7

Thanks for point out this issue.


(comcam-ocsbr01.cp) add br1600 interface

This is still waiting on a network change to be useful but this can be merged now.


stake-pool-cli: don't send UpdateValidatorListBalance transactions for subslices of validator list that have already been updated

Problem
The update command on the stake-pool-cli always sends update transactions for the entire validator list. This is redundant and increases the odds of failure if a previous update command failed in the middle since you don't have to run the UpdateValidatorListBalance instruction again on the parts of the validator list that were successfully updated. This is especially true for large stake pools - e.g. solblaze has all 2950 validators on their list.
Solution
In the update command, filter out UpdateValidatorListBalance instructions for subslices of the ValidatorList that have already been updated. Keep the current behaviour for the --force flag.
This builds on PR #6058

Anyone has an idea why SetTransferFee instruction is not being implemented? Weird 🤔🤔

Once https://github.com/solana-labs/solana-program-library/pull/6058 moves along we can circle back to this, or we can do this one first and just cherry pick the last commit and move it up, up to you!

yeah i think lets finish #6058 first


update to latest glm

The currentl used revision produces lots of warnings when doing release builds (regarding -Wstrict-aliasing)
Edit: Ah, this warning seems to be gcc optimizer specific.
Which is your favourite warning, btw? :)
http://fuckingclangwarnings.com/
https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html
More seriously: any preferences which warnings we should turn on by default?

Ah, I don't often compile with GCC or release so it makes sense that I haven't noticed these. GLM upgrade sounds good.
-Wvexing-parse is a fun one haha. I didn't know about -Wmicrosoft-exists but I like how it implies that microsoft existing is a mistake. I tend to appreciate most flags except -Wpedantic, which I find to be, well, pedantic.

For gcc '-Wextra -Wno-unused-parameter' seems sensible. It currently shows a few -Wmissing-field-initializers

http://www.cmake.org/cmake/help/v3.0/module/CheckCXXCompilerFlag.html seems to be handy
I'll take my clang with -Weverything


Problem about Commonsense Conversation Dataset

Thanks for your great job!
In your repo i found the dataset sample CommonsenseConversation, but when i try downloading it i found i can't get it down in the link: http://coai.cs.tsinghua.edu.cn/hml/dataset/#commonsense
I'm curious how you can access this dataset, I would be very honored if you could answer my question!

It seems that their link has been moved somewhere else. You can use the google drive link we prepared.


Better input system

The input in Devzat is quite poor. The fact that it is not possible to comfortably edit multi-lines messages is a bit sad. We should probably refactor that system. Maybe there are some external library to handle that kind of tasks.

huh, that doesn't happen for me. what terminal are you using?

I have this problem on Konsole, Alacritty, and st.

What I get when I try to add some text at the beginning of a multi-line message.

here's an asciinema of what I see: https://asciinema.org/a/1dhK4SCMVSAnm8l6FFBdvxtcZ
(unrelated but this shows the line counting algo is broken)

Wow um yeah input is really jank lol

I looked at potential solutions and Bubbles' textinput looks like a pretty decent solution for us. Do you think I should look into integrating it?

After looking at Bubble Tea, it seems that the inputs are very abstracted. Thus, getting the inputs from the user might be tricky. Bubble Tea might not be the solution to our problem.

I see


Conditions

Conditions are sets of expressions (JSON patterns) that whenever included must evaluate to true against the Authorization JSON, so the scope where the expressions are defined is enforced; otherwise Authorino will skip that scope in the pipeline.
The scope for a set of conditions can be the entire AuthConfig (top level) or a particular evaluator of any phase of the auth pipeline.
Each expression is a tuple composed of a selector, an operator and a fixed comparable value, just like the pattern matching expressions used in the existing conditions field of JSON pattern-matching authz and K8s SubjectAccessReview-based authz – both now superseded by this new implemention.
Conditions can list, mix and combine literal expressions and references to expression sets ("named patterns") defined at the upper level of the AuthConfig spec.
Conditions can be used:
i. to skip an entire AuthConfig based on the context:
spec:
  conditions:
  - selector: context.request.http.path
    operator: neq
    value: /status

ii. to skip parts of an AuthConfig (i.e. a specific evaluator):
spec:
  metadata:
  - name: metadata-source
    http:
      endpoint: https://my-metadata-source.io
    conditions:
    - selector: context.request.http.method
      operator: neq
      value: OPTIONS

iii. to enforce a particular evaluator only in certain contexts (really the same as the above, though to a different use case):
spec:
  identity:
  - name: authn-meth-1
    apiKey: {...} # this authn method only valid for POST requests to /foo[/*]
    conditions:
    - selector: context.request.http.path
      operator: matches
      value: ^/foo(/.*)?$
    - selector: context.request.http.method
      operator: eq
      value: POST

  - name: authn-meth-2
    oidc: {...}

iv. to avoid repetition while defining patterns for conditions:
spec:
  patterns:
    pets:
    - selector: context.request.http.path
      operator: matches
      value: ^/pets/\d+(/.*)$

  metadata:
  - name: pets-info
    conditions:
    - patternRef: pets
    http:
      endpoint: https://pets-info.io?petId={context.request.http.path.@extract:{"sep":"/","pos":2}}

  authorization:
  - name: pets-owners-only
    conditions:
    - patternRef: pets
    opa:
      inlineRego: |
        allow { input.metadata["pets-info"].ownerid == input.auth.identity.userid }

v. to avoid repetition while defining JSON pattern-matching authorizaton rules:
spec:
  patterns:
    admin:
    - selector: auth.identity.roles
      operator: incl
      value: admin

  authorization:
  - name: secured-endpoints
    conditions:
    - selector: context.request.http.path
      operator: matches
      value: ^/secure(/.*)?$
    json:
      rules:
      - patternRef: admin

  - name: only-admins-can-delete
    conditions:
    - selector: context.request.http.method
      operator: eq
      value: DELETE
    json:
     rules:
      - patternRef: admin

vi. mixing and combining literal expressions and refs:
spec:
  patterns:
    foo:
    - selector: context.request.http.path
      operator: eq
      value: /foo

  conditions: # unauthenticated access to /foo always granted
  - patternRef: foo
  - selector: context.request.http.headers.authorization
    operator: eq
    value: ""

  authorization:
  - name: my-policy-1
    conditions: # authenticated access to /foo controlled by policy
    - patternRef: foo
    json: {...}

vii. to avoid evaluating unnecessary identity checks when the user can indicate the preferred authentication method (again the pattern of skipping based upon the context):
spec:
  identity:
  - name: jwt
    conditions:
    - selector: selector: context.request.http.headers.authorization
      operator: matches
      value: JWT .+
    oidc: {...}

  - name: api-key
    conditions:
    - selector: context.request.http.headers.authorization
      operator: matches
      value: APIKEY .+
    apiKey: {...}

Example of AuthConfig with multiple usages of Conditions combined:
apiVersion: authorino.kuadrant.io/v1beta1
kind: AuthConfig
metadata:
  name: talker-api-protection
spec:
  hosts:
  - talker-api-authorino.<IP_ADDRESS>.nip.io

  patterns: # these are named sets of expressions that can be reused
    pets:
    - selector: context.request.http.path
      operator: matches
      value: ^/pets/\d+(/.*)?$

  conditions: # conditions at top level scope
  - selector: context.request.http.path
    operator: neq
    value: /status

  identity:
  - name: idp-users
    oidc:
      endpoint: http://keycloak:8080/auth/realms/kuadrant
    conditions:
    - selector: context.request.http.headers.authorization
      operator: matches
      value: JWT .+
    credentials:
      in: authorization_header
      keySelector: JWT
    extendedProperties:
    - name: username
      valueFrom:
        authJSON: auth.identity.preferred_username
    - name: roles
      valueFrom:
        authJSON: auth.identity.realm_access.roles

  - name: admins
    apiKey:
      labelSelectors:
        authorino.kuadrant.io/managed-by: authorino
    conditions:
    - selector: context.request.http.headers.authorization
      operator: matches
      value: APIKEY .+
    credentials:
      in: authorization_header
      keySelector: APIKEY
    extendedProperties:
    - name: username
      valueFrom:
        authJSON: auth.identity.metadata.annotations.username
    - name: roles
      value: ["admin"]

  metadata:
  - name: resource-metadata
    http:
      endpoint: http://talker-api:3000/pets/{context.request.http.path.@extract:{"sep":"/","pos":2}}/meta
      method: GET
    conditions: # skip unnecessay out-of-context metadata fetching
    - patternRef: pets

  authorization:
  - name: owner-policy
    opa:
      inlineRego: |
        allow { input.auth.identity.username == input.metadata["resource-metadata"].owner }
    conditions:
    - patternRef: pets
    - selector: auth.identity.roles
      operator: excl
      value: admin

  - name: admin-role-required
    json:
      rules:
      - selector: auth.identity.roles
        operator: incl
        value: admin
    conditions:
    - selector: context.request.http.path
      operator: matches
      value: ^/admin(/.*)?$

Closes #205
Closes #24

[x] Conditions
[x] Tests
[x] Docs

First thing in my mind after reading the descr of the PR: s/conditions/when/
Minor thing, but wdyt?

patterns should not be condition-patterns or something similar? To be more meaning ful at top level

First thing in my mind after reading the descr of the PR: s/conditions/when/
Minor thing, but wdyt?

Totally valid suggestion, @eguzki.
I thought about when myself. Ended up going with conditions for 2 reasons:

because it's the same semantics and syntax of the already existing spec.authorization.json.conditions and spec.authorization.kubernetes.conditions
So very "creative" users don't end up thinking there's some cron thing involved here – "when" means "if" in this case

if would also make sense.

I cannot find it. What is the semantic meaning as a boolean operation of a list of conditions? AND, OR?

I cannot find it. What is the semantic meaning as a boolean operation of a list of conditions? AND, OR?

It's AND.

patterns should not be condition-patterns or something similar? To be more meaningful at top level

The patterns can also be used in spec.authorization.json.rules, not only in conditions fields.

implementation looks good to me

Influenced by OAS design (sorry I cannot avoid it), I miss some expression in the form of
(cond11 AND cond12 AND ... AND cond1N) OR (cond21 AND cond22 AND ... AND cond2N) OR ... OR (condM1 AND condM2 AND ... AND condMN)

I wonder if this is even a need. But I can  think two  example:
GET /path1 -> AUTH type: apikey OR http basic  (OAS allows this flexibility)

This use case is already covered having two different identity evaluators that are evaluated with OR semantics. So maybe does not apply but I think it is worth mentioning.
GET /path1 -> AUTH type: apikey
GET /path2 -> AUTH type: apikey

This use case requires defining two different identity evaluators which are exactly the same (except for the conditions)

Influenced by OAS design (sorry I cannot avoid it), I miss some expression in the form of
(cond11 AND cond12 AND ... AND cond1N) OR (cond21 AND cond22 AND ... AND cond2N) OR ... OR (condM1 AND condM2 AND ... AND condMN)

I wonder if this is even a need. But I can think two example:
GET /path1 -> AUTH type: apikey OR http basic  (OAS allows this flexibility)

This use case is already covered having two different identity evaluators that are evaluated with OR semantics. So maybe does not apply but I think it is worth mentioning.
GET /path1 -> AUTH type: apikey
GET /path2 -> AUTH type: apikey

This use case requires defining two different identity evaluators which are exactly the same (except for the conditions)

No problem, @eguzki.
OR logics can be achieved by repeating the evaluator spec as many times as needed, varying only the conditions block.
For authorization based on JSON pattern-matching, because of https://github.com/Kuadrant/authorino/pull/206#issuecomment-1011033183, repeating the rules can get slightly cleaner.
E.g.:
spec:
  patterns:
    my-authz-rules:
    - selector: some.json.path
      operator: eq
      value: some-expected-value
    - selector: some.other.json.path
      operation: incl
      value: some-value-that-must-be-present-in-the-selected-array
  authorization:
  - name: use-case-1
    conditions:
    - selector: context.request.http.path
      operator: eq
      value: /path1
    json:
      rules:
      - patternRef: my-authz-rules
  - name: use-case-2
    conditions:
    - selector: context.request.http.path
      operator: eq
      value: /path2
    json:
      rules:
      - patternRef: my-authz-rules

As for the examples you shared...
First one is simpler:
spec:
  patterns:
    get-path1:
    - selector: context.request.http.method
      operation: eq
      value: GET
    - selector: context.request.http.path
      operator: eq
      value: /path1
  identity:
  - name: api-key
    conditions:
    - patternRef: get-path1
    apikey: {...}
    credentials:
      in: custom_header
      keySelector: API-KEY
  - name: http-basic-auth
    conditions:
    - patternRef: get-path1
    apikey: {...} # RFC 7235 happens to be mimicked in Authorino using API key authn as well, though the label selectors here would probably differ from the ones in the `apiKey` above
    credentials:
      in: authorization_header
      keySelector: Basic

Second one is a bit more annoying because it involves really duplicating the apiKey authn spec:
spec:
  patterns:
    get:
    - selector: context.request.http.method
      operation: eq
      value: GET
  identity:
  - name: path1-authn
    conditions:
    - patternRef: get
    - selector: context.request.http.path
      operator: eq
      value: /path1
    apikey: {...}
  - name: path2-authn
    conditions:
    - patternRef: get
    - selector: context.request.http.path
      operator: eq
      value: /path2
    apikey: {...} # identical to the `apiKey` above

Other than the suggestion to change conditions to when and a broad conversation about whether to focus config in the CR and Policy in rego. This looks good to me 👍


Error when join a managedCluster

I'm using the clusteradm v0.1.0-alpha.5v.1
After run clusteradm join ... command, I got this error message:
E0812 06:32:36.654581  454000 memcache.go:196] couldn't get resource list for operator.open-cluster-management.io/v1: the server could not find the requested resource
Error: no matches for kind "Klusterlet" in version "operator.open-cluster-management.io/v1"

@xuezhaojun
I tried with kind 0.11.0 with 1.21.1 kube version and it worked well.
You may need to provider more context about your issue.

It's weird that this issue doesn't appear every time. I realize my poor network environment could have an effect on this.
At the time when the command "clusteradm join ..." was running, most pods are still in ContainerCreating phase because images are not pulled yet.
After I changed to a good network environment, I found everything is going fine.
I  will close this issue, thanks for your time!


failed to install on macos

I have installed libxml2 from brew,
but pip install bblfsh fails with this error:
In file included from bblfsh/libuast/uast.cc:4:
bblfsh/libuast/uast_private.h:4:10: fatal error: 'libxml/tree.h' file not found
#include <libxml/tree.h>
         ^~~~~~~~~~~~~~~
1 error generated.
error: command 'g++' failed with exit status 1

I just ran into this same issue, and the command that fixed the problem for me was:
env CFLAGS="-I$(brew --prefix)/opt/libxml2/include/libxml2" pip3 install bblfsh
From @creachadair
It would be helpful if this were added to the README.

I just ran into this same issue, and the command that fixed the problem for me was:
env CFLAGS="-I$(brew --prefix)/opt/libxml2/include/libxml2" pip3 install bblfsh
From @creachadair
It would be helpful if this were added to the README. I do not think #128 fixed this issue.

I believe #128 removes the dependency, but that the current release doesn't include it yet. We are planning to cut a release including these changes soon, and at that point this workaround should no longer be required. Sorry for the confusion about timing.

And v3.0.0 release is out now on pypi.


[Bug]: Copy to clipboard in Native takes time and add confirmation popup in settings

This issue respects the following points:

[X] This is a bug, not a question or a configuration issue; Please visit our forum first to troubleshoot with volunteers, before creating a report. The links can be found here.
[X] This issue is not already reported on GitHub (I've searched it).
[X] I'm using an up to date version of OpenBullet2. We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
[X] I agree to follow OpenBullet's Code of Conduct.
[X] This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug
when on Native click copy userdata from hit or ToCHeck tab its takes while before getting into clipboard , dont know reason behind it.
And when add change settings in RL Settings clicking save button must inform that settings are saved with poup
Reproduction steps
Its already explained in bug
What is the current bug behavior?
Its already explained in bug
What is the expected correct behavior?
Its already explained in bug
Version of the client
<IP_ADDRESS>86
Type of client
Native client
Environment
- OS:Windows 10
- Virtualization: NO
- Browser: All

OpenBullet2 logs
No response
Client / Browser logs
No response
Relevant screenshots or videos
No response
Relevant LoliCode if needed
No response
Additional information
No response

This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.
You ticked it but still reported two issues in one 😛 please make another issue for the other thing, thanks!


godoc for scan

Document Scan. Should i remove the example? Should i add more details? WDYT

LGTM! cool!


Added FUSEE 3D to resources

FUSEE is a 3D library / engine written in C# and running on different platforms including client-side browser web assembly.
OpenTK leverages FUSEE to run on various platforms including desktop and Android.

This is a good reminder to take a look at this table and clean up some old abandoned projects from it and to update it with some more recent projects.


State in native activity lost when navigating away and back to app.

As long as current page is a Flutter page, the home button returns to the desktop, you can return from the launcher icon to the original page; but in the native Activity, then the state is lost, the return page is MainActivity

Steps to Reproduce

In android native SecondActivity , press home key back to desktop
click launcher icon enter app , and the MainActivity shows
But in Flutter pages , i don't have this problem

Logs

Duplicate of #6827


feat:scarb scripts

Use scarb scripts instead of Makefile
This is not mergeable as CI fails until scarb is updated with alpha.7 (soon)
Pull Request type

Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

Thanks for this contribution. Can you put it as draft PR until Scarb is ready ?

Thanks for this contribution. Can you put it as draft PR until Scarb is ready ?

Do we know the ETA on Scarb readiness?

Thanks for this contribution. Can you put it as draft PR until Scarb is ready ?

Do we know the ETA on Scarb readiness?

I think they're waiting for alpha.7 and idk when SW will release it

will finish this after next pr

Closing as it doesn't offer any benefit yet.


What exactly is BoundaryConditionDirichlet?

The document and its name seem to suggest it's used for setting Dirichlet boundary condition, but is it true? If I set tspan = (0, 0.7) in https://github.com/trixi-framework/Trixi.jl/issues/962, the following solution is obtained:

Seems that something like open boundary condition (or transparent boundary condition, or boundary condition at infinity, or whatever you want to call it) has been set. (I haven't compared it to the analytic solution, so I may be wrong. )
What's the actual boundary condition here?

As stated in our README.md (and common in CFD; finite volume, discontinuous Galerkin, flux reconstruction, ... methods), we use

weakly-enforced boundary conditions

in Trixi.jl. Such a shock tube problem is usually run to a small final time so that the numerical solution does not interact with the boundary. In that case, such a boundary condition is fine.

@ranocha Er… could you explain the b.c. with traditional math notation, or add a reference readable for a CFD noob? I think it would be good to include such stuff in the tutorial.

… so that the numerical solution does not interact with the boundary.

Perhaps we can extend the discussion a bit: It may be my illusion, but I have a feeling that introductions of Euler equations in various materials tend to avoid discussing solutions interacting with the boundary of Euler equations, they're almost always about solutions localized in a small domain, or periodic. Is it because solutions interacting with the boundary is too complicated to discuss? (BTW b.c. of PDE is something that confused me for years, I asked a question here: https://math.stackexchange.com/q/450367/58219)

Boundary conditions for hyperbolic problems, especially for hyperbolic systems are tricky and quite different to e.g. elliptic PDEs. If you want to read up on this, I would read up on for instance "characteristic boundary conditions" and do a search on it. BCs for hyperbolic problems are often difficult, as they are in some sense artificial for many applications (except, when you have solid wall BCs).
If you follow the key word characteristic boundary condition, you will most likely get to the theoretical background and the difficulties. Also, look up for non-reflecting boundary conditions. I recommend for instance the CFD book by BLAZEK, but there are many others that discuss the implementation (and the difficulty) of boundary conditions.
In Trixi.jl, DirichletBoundaryConditions refers to prescribing an outer state at the boundary, but use the numerical flux at the surface to handle the situation (num flux uses value outside and insede and computes a boundary flux). Note that technically, there is no such thing as Dirichlet BC for compressible Euler (only in a very particular case, e.g. supersonic inflow). By using a numerical flux function, the BC state is applied weakly to the scheme. In particular, if you use a very accurate numerical flux function such as e.g. Roe's approximate Riemann solver, the Trixi.jl Dirichlet BC approaches a characteristic BC...if you use for instance Lax_Friedrichs numerical flux, it is more akin to a penalty type BC.

@gregorgassner I strongly recommend including these in the document, ideally a section named Boundary Conditions or so, but even a few lines a single line BCs for hyperbolic problems are often difficult would be a salvation.

We also added a reference to a good introductory paper in the docs.


Migrate from LABEL= to /dev/disk/by-label/*

Hey folks—this is my first patch against HassOS. First, let me just say that this project is wonderful, and while I'm a relative newcomer to it and to Home Assistant in general, working with Hass/Hassio/HassOS so far has been so much fun.
I wanted to see if y'all would be willing to accept a patch like this one. I'm admittedly running HassOS in a slightly unsupported configuration (basically, with a hassos-data volume on an external storage device, not on my RPi's SD card). Unsurprisingly, this works quite well, except that maybe 50% of the time, my external volume isn't available until a few seconds after the hassos-expand.service unit wants to start. This, in turn, causes that unit to fail, and then any dependent units fail, like mnt-data.mount, leaving the system unable to start.
Digging into the systemd source, my belief is that use of the LABEL= syntax causes systemd not to associate any block device dependencies with the mount, meaning that if a hotplug device isn't available, systemd won't wait for it. If we use /dev/device/by-label/hassos-data, say, all the dependencies should be wired up and everything should work.
Because the hassos-expand.service depends on the filesystem not being mounted, I added an explicit dependency to this unit.
I still need to do some (any?) extensive testing on this, but I'd love some feedback on the approach, and—despite the fact that I'm personally using it to run HassOS in a slightly off-label fashion—whether you'd accept it upstream, as it likely would improve the resiliency of the software in the face of wonky hardware even outside of my use-case.
Anyway, thank you so much for even reading this PR, and thanks for all the work that you do on HA!

@TonyApuzzo It's only half-done, so might be a little premature, but—what specific questions did you have? (I'd like to learn how others might use this functionality to inform how I'll build the migration piece.)

I would like to use my ODroid HC1 with a SATA device as the data to improve performance and stability.  So my basic question is "how to most easily move to using hassos-data on an external device?"
I have had a bit of difficulty getting HassOS to work reliably with an external device, although it is working sorta-ok right now.
I was not sure the right approach to migrating the data partition, so that was my first question.  Initially, I tried to do a migration of an existing HassOS install as follows:
For all "semi-live" copies, I shut down as many docker images as I could to keep dynamic changes on /mnt/data to a minimum.  I couldn't shutdown the supervisor -- now that I have a serial console maybe I could do it??
First Attempt

Install SATA Drive in HC1,
use fdisk to format (MBR)
create an ext4 fs
mount at /tmp/dst
mount /mnt/data to /tmp/src and rsync from /tmp/src to /tmp/dst (using a static compile copy of rsync I found on the internet) the data -- NOTE I couldn't rsync from the 'live' mount because the overlays caused rsync to fail, but using a bind mount let me copy everything underneath docker so it seems like it mostly? worked.
e2label /dev/mmcblk1p4 to hassos-data-orig
e2label /dev/sdb1 to hassos-data
reboot
failed to mount and wouldn't boot

Second Attempt

Same as first attempt except I used dd to make an image of the data partition
This actually corrupted the ssd -- I assume because I had created an MBR disk with fdisk instead of a GPT.. see 4th attempt
Salvaged disk on Windows machine with diskpart and clean

Third Attempt

Build the latest dev branch from git that included your PR (build with vagrant ubuntu on hyper-v, slow but worked first try maybe an 1-1.5 hours to do the build??)
Etcher install on sdcard ODroid HC1
Same as First Attempt
This sort of worked.  The first time I booted it with renamed fs labels, it mounted the new partition and everything looked good.  Unfortunately when I re-booted it failed and then it would never boot again, I tried about 15 times.

Fourth Attempt

I finally recieved the 1.8v USB/UART so I can have a serial console and see more of what was happening
This time I decided to do the copy before first boot of HassOS -- I used a spare Raspberry Pi to do the work since I don't have Armbian for my ODroid.
Write image on microsd
Mount microsd in usb card reader on RPi3
mount data partition
remove ssd from hc1 and mount in usb external enclosure attach to RPi3
re-label with gpt (effectivly reset ssd)
create ext4 fs on ssd
rsync -avxHWAX --sparse --numeric-ids --del --info=progress2 /tmp/src/ /tmp/dst/
e2label as before hassos-data-orig on microsd and hassos-data on SSD
unmount everything from RPi3
reinstall everything in HC1
first boot it worked perfectly, expanded the hassos-data on SSD, downloaded and installs HassIO 0.86.4
next reboot -- BRICK! -- rats!

[   14.924715] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[   14.950265] usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.01
[   14.957016] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   14.964109] usb 4-1: Product: USB to SATA bridge
[   14.968761] usb 4-1: Manufacturer: JMicron
[   14.973833] usb 4-1: SerialNumber: DB00000000013B
[   15.001710] scsi host0: uas
[   15.003894] scsi 0:0:0:0: Direct-Access     JMicron                   3101 PQ: 0 ANSI: 6
[   15.012338] sd 0:0:0:0: Attached scsi generic sg0 type 0
[   15.013508] sd 0:0:0:0: [sda]<PHONE_NUMBER> 512-byte logical blocks: (512 GB/477 GiB)
[   15.017127] usbcore: registered new interface driver uas
[   15.023989] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   15.034647] sd 0:0:0:0: [sda] Write Protect is off
[   15.039572] sd 0:0:0:0: [sda] Disabling FUA
[   15.043377] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   15.057957]  sda: sda1
[   15.061753] sd 0:0:0:0: [sda] Attached SCSI disk
[  OK  ] Found device M4-CT512M4SSD2 hassos-data.
         Starting HassOS data resizing...
[   15.368012]  sda: sda1
[  OK  ] Started HassOS data resizing.
[DEPEND] Dependency failed for HassOS data partition.
[DEPEND] Dependency failed for Docker persistent data.
[DEPEND] Dependency failed for Docker Application Container Engine.
[DEPEND] Dependency failed for Getty on tty1.
[DEPEND] Dependency failed for HassOS supervisor.
[DEPEND] Dependency failed for Dropbear SSH daemon.
[DEPEND] Dependency failed for Serial Getty on ttySAC2.
[DEPEND] Dependency failed for HassOS AppArmor.
[DEPEND] Dependency failed for NetworkManager persistent data.
         Starting Create Volatile Files and Directories...
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Create Volatile Files and Directories.
         Mounting HassOS data partition...
         Mounting NetworkManager persistent system connections...
         Mounting Timesyncd persistent configuration...
         Mounting Hostname persistent configuration...
         Mounting Hosts persistent configuration...[   15.736092] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Mounted HassOS data partition.
[  OK  ] Mounted NetworkManager persistent system connections.
[  OK  ] Mounted Timesyncd persistent configuration.
[  OK  ] Mounted Hostname persistent configuration.
[  OK  ] Mounted Hosts persistent configuration.
         Starting Network Time Synchronization...
[  OK  ] Reached target HassOS overlay targets.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.

It is hung here, the network stack is up, I can ping it and the kernel is running, I can unplug the network and get a notice but don't have login prompt and it never seems to recover

next reboot -- working again -- yay!
risk it and reboot yet again -- BRICK (same error as above, never get console logon prompt.)
next reboot -- still broken :-(
next reboot -- still broken :-(

Not sure if there is something getting corrupted or what to do to diagnose at this point other than re-installing from scratch but I don't know what to do differently leading up to this point.
I get tired of dealing with serial console on windows computer because it keeps loosing connection to the device and I have to unplug/replug everything, so I plug the USB/UART into the RPi3 and now I have remote serial console to HC1 haha.  I plugged the HC1 into a zwave outlet so I can now do reboots remote too.  I can't re-flash remote tho.

Update -- rebooted again and it worked this time....
Success log
[    5.596718] usb 4-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd
[    5.607050] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
[    5.612280] dma-pl330 3880000.adma:  DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
[    5.622817] usb 4-1: New USB device found, idVendor=152d, idProduct=0578, bcdDevice=31.01
[    5.626292] odroid-audio sound: i2s-hifi <-> samsung-i2s mapping ok
[    5.629611] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    5.640671] dma-pl330 3880000.adma: PM domain MAU will not be powered off
[    5.642947] usb 4-1: Product: USB to SATA bridge
[    5.654275] usb 4-1: Manufacturer: JMicron
[    5.658347] usb 4-1: SerialNumber: DB00000000013B
[  OK  ] Found device /dev/zram1.
[    5.689393] scsi host0: uasm2.
[    5.691859] scsi 0:0:0:0: Direct-Access     JMicron                   3101 PQ: 0 ANSI: 6
[    5.700243] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    5.701792] sd 0:0:0:0: [sda]<PHONE_NUMBER> 512-byte logical blocks: (512 GB/477 GiB)
[    5.705587] usbcore: registered new interface driver uas
[    5.711963] sd 0:0:0:0: [sda] 4096-byte physical blocks
[    5.722586] sd 0:0:0:0: [sda] Write Protect is off
[    5.727523] sd 0:0:0:0: [sda] Disabling FUA
[    5.731330] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

[    5.747134]  sda: sda1
[    5.750361] sd 0:0:0:0: [sda] Attached SCSI disk
[  OK  ] Found device /dev/disk/by-label/hassos-overlay.
[  OK  ] Found device /dev/disk/by-label/hassos-boot.
[  OK  ] Started HassOS ZRAM var.
[  OK  ] Started HassOS ZRAM tmp.
[  OK  ] Found device M4-CT512M4SSD2 hassos-data.
         Starting HassOS data resizing...
[  OK  ] Reached target Sound Card.
         Mounting HassOS overlay partition...
         Mounting HassOS ZRAM var...
[    8.944072] EXT4-fs (zram1): mounted filesystem without journal. Opts: nobarrier
         Activating swap HassOS ZRAM swap...
[  OK  ] Mounted HassOS ZRAM var.
[    9.083450] Adding 408064k swap on /dev/zram0.  Priority:-2 extents:1 across:408064k SS
[    9.091125] EXT4-fs (mmcblk1p3): recovery complete
[  OK  ] Activated swap HassOS ZRAM swap.
[    9.100805] EXT4-fs (mmcblk1p3): mounted filesystem with ordered data mode. Opts: (null)
[  OK  ] Mounted HassOS overlay partition.
         Mounting Udev [    9.142495] random: crng init done
[    9.145493] random: 7 urandom warning(s) missed due to ratelimiting
[    9.152624]  sda: sda1
persistent rules.d...
         Mounting Dropbear persistent user...
         Mounting Docker persistent user...
         Mounting Bluetooth persistent state...
         Mounting Docker persistent configuration...
         Mounting Systemd persistent state...
         Mounting Dropbear persistent keys...
         Mounting Systemd persistent logging...
         Mounting Kernel persistent modules-load.d...
[  OK  ] Reached target Swap.
         Mounting Temporary Directory (/tmp)...
[    9.342026] EXT4-fs (zram2): mounted filesystem without journal. Opts: nobarrier
[  OK  ] Started HassOS data resizing.
[  OK  ] Mounted Udev persistent rules.d.
[  OK  ] Mounted Dropbear persistent user.
[  OK  ] Mounted Docker persistent user.
[  OK  ] Mounted Bluetooth persistent state.
[  OK  ] Mounted Docker persistent configuration.
[  OK  ] Mounted Systemd persistent state.
[  OK  ] Mounted Dropbear persistent keys.
[  OK  ] Mounted Systemd persistent logging.
[  OK  ] Mounted Kernel persistent modules-load.d.
[  OK  ] Mounted Temporary Directory (/tmp).
[  OK  ] Reached target Local File Systems.
         Starting Rebuild Journal Catalog...
         Mounting HassOS boot partition...
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
         Starting Flush[    9.711877] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
 Journal to Persistent Storage...
         Starting Load/Save Random Seed...
         Starting Retrigger udev rules after user rules mounted...
         Mounting HassOS data partition...
[  OK  ] Started Rebuild Journal Catalog.
[  OK      9.838836] EXT4-fs (sda1): recovery complete
[    9.842217] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
0m] Mounted HassOS boot partition.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Mounted HassOS data partition.
         Mounting NetworkManager persistent data...
         Mounting Docker persistent data...
         Starting Update is Completed...
[  OK  ] Mounted NetworkManager persistent data.
[  OK  ] Mounted Docker persistent data.
[  OK  ] Started Update is Completed.
[   10.110960] systemd-journald[146]: Received request to flush runtime journal from PID 1
[  OK  ] Started Flush Journal to Persistent Storage.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Create Volatile Files and Directories.
         Mounting Timesyncd persistent configuration...
         Mounting NetworkManager persistent system connections...
         Mounting Hosts persistent configuration...
         Starting Update UTMP about System Boot/Shutdown...
         Mounting Hostname persistent configuration...
[  OK  ] Mounted Timesyncd persistent configuration.
[  OK  ] Mounted NetworkManager persistent system connections.
[  OK  ] Mounted Hosts persistent configuration.
[  OK  ] Mounted Hostname persistent configuration.
         Starting Network Time Synchronization...
[   10.569416] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   10.576787] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[   10.577868] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   10.595862] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[  OK  ] Started Retrigger udev rules after user rules mounted.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Reached target HassOS overlay targets.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
         Starting Docker Socket for the API.
[  OK  ] Started HassOS mark boot partition as good.
[  OK  ] Reached target Timers.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Listening on Docker Socket for the API.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting HassOS AppArmor...
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi DNS Configuration Daemon.
         Starting Rauc Update Service...
         Starting HassOS persists journald...
         Starting Network Manager...
[   11.454679] audit: type=1400 audit(1549177424.592:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor" pid=343 comm="apparmor_parser"
[   11.468781] audit: type=1400 audit(1549177424.592:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/gdbus" pid=343 comm="apparmor_parser"
[   11.485528] audit: type=1400 audit(1549177424.592:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/git" pid=343 comm="apparmor_parser"
[   11.502209] audit: type=1400 audit(1549177424.592:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="hassio-supervisor///usr/bin/socat" pid=343 comm="apparmor_parser"
[   11.518976] audit: type=1300 audit(1549177424.592:2): arch=40000028 syscall=4 per=800000 success=yes exit=69244 a0=6 a1=b6dbc008 a2=10e7c a3=0 items=0 ppid=332 pid=343 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apparmor_parser" exe="/usr/sbin/apparmor_parser" subj==unconfined key=(null)
[   11.549576] audit: type=1327 audit(1549177424.592:2): proctitle=61707061726D6F725F706172736572002D72002D57002D4C002F6D6E742F646174612F73757065727669736F722F61707061726D6F722F6361636865002F6D6E742F646174612F73757065727669736F722F61707061726D6F722F68617373696F2D73757065727669736F72
[  OK  ] Started HassOS persists journald.
[  OK  ] Started HassOS AppArmor.
[  OK  ] Started Rauc Update Service.
         Starting Hostname Service...
[  OK  ] Started Hostname Service.
[  OK  ] Started Network Manager.
         Starting Network Manager Script Dispatcher Service...
         Starting Network Manager Wait Online...
[  OK  ] Reached target Network.
         Starting HassOS Configuration Manager...
[  OK  ] Started Network Manager Script Dispatcher Service.
[   12.336623] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.348148] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  OK     12.377279] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   12.383112] r8152 6-1:1.0 eth0: carrier on
0m] Started HassOS Configuration Manager.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting Docker Application Container Engine...
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[   14.675376] audit: type=1400 audit(1549177427.812:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="docker-default" pid=407 comm="apparmor_parser"
[   14.689262] audit: type=1300 audit(1549177427.812:3): arch=40000028 syscall=4 per=800000 success=yes exit=7945 a0=4 a1=165558 a2=1f09 a3=0 items=0 ppid=406 pid=407 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="apparmor_parser" exe="/usr/sbin/apparmor_parser" subj==unconfined key=(null)
[   14.719425] audit: type=1327 audit(1549177427.812:3): proctitle=61707061726D6F725F706172736572002D4B72002F6D6E742F646174612F646F636B65722F746D702F646F636B65722D64656661756C74323133343130303537
[   15.255525] audit: type=1325 audit(1549177428.392:4): table=nat family=2 entries=5
[   15.340738] Initializing XFRM netlink socket
[   15.531879] IPv6: ADDRCONF(NETDEV_UP): hassio: link is not ready
[   15.708142] IPv6: ADDRCONF(NETDEV_UP): docker0: link is not ready
[   16.488172] kauditd_printk_skb: 137 callbacks suppressed
[   16.488177] audit: type=1325 audit(1549177429.624:50): table=filter family=2 entries=25
[   16.500040] audit: type=1300 audit(1549177429.624:50): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=84438 items=0 ppid=373 pid=579 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj==unconfined key=(null)
[   16.529316] audit: type=1327 audit(1549177429.624:50): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D740066696C746572002D4E00444F434B45522D55534552
[   16.544037] audit: type=1325 audit(1549177429.672:51): table=filter family=2 entries=27
[   16.551955] audit: type=1300 audit(1549177429.672:51): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=849e0 items=0 ppid=373 pid=581 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj==unconfined key=(null)
[   16.581159] audit: type=1327 audit(1549177429.672:51): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D4100444F434B45522D55534552002D6A0052455455524E
[   16.595882] audit: type=1325 audit(1549177429.716:52): table=filter family=2 entries=28
[   16.603844] audit: type=1300 audit(1549177429.716:52): arch=40000028 syscall=294 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=84b40 items=0 ppid=373 pid=583 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj==unconfined key=(null)
[   16.633104] audit: type=1327 audit(1549177429.716:52): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D4900464F5257415244002D6A00444F434B45522D55534552
[  OK  ] Started Docker Application Container Engine.
         Starting HassOS supervisor...
[  OK  ] Started Dropbear SSH daemon.
[  OK  ] Started HassOS supervisor.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttySAC2.
[  OK  ] Reached target Login Prompts.
[  OK  ] Reached target Multi-User System.
         Starting Update UTMP about System Runlevel Changes...

Welcome to HassOS
hassio login: [   18.298239] docker0: port 1(vethe969281) entered blocking state
[   18.302739] docker0: port 1(vethe969281) entered disabled state
[   18.309177] device vethe969281 entered promiscuous mode
[   18.313887] audit: type=1700 audit(1549177431.436:53): dev=vethe969281 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[   18.315849] IPv6: ADDRCONF(NETDEV_UP): vethe969281: link is not ready
[   18.397563] hassio: port 1(vethb8383e9) entered blocking state
[   18.401982] hassio: port 1(vethb8383e9) entered disabled state
[   18.407961] device vethb8383e9 entered promiscuous mode
[   18.415249] IPv6: ADDRCONF(NETDEV_UP): vethb8383e9: link is not ready
[   18.420282] hassio: port 1(vethb8383e9) entered blocking state
[   18.426062] hassio: port 1(vethb8383e9) entered forwarding state
[   18.432377] hassio: port 1(vethb8383e9) entered disabled state
[   18.546259] docker0: port 1(vethe969281) entered disabled state
[   18.551547] device vethe969281 left promiscuous mode
[   18.555729] docker0: port 1(vethe969281) entered disabled state
[   18.650980] hassio: port 1(vethb8383e9) entered disabled state
[   18.656201] device vethb8383e9 left promiscuous mode
[   18.660366] hassio: port 1(vethb8383e9) entered disabled state
[   19.166725] docker0: port 1(vethbfb411a) entered blocking state
[   19.171285] docker0: port 1(vethbfb411a) entered disabled state
[   19.177482] device vethbfb411a entered promiscuous mode
[   19.183138] IPv6: ADDRCONF(NETDEV_UP): vethbfb411a: link is not ready
[   19.188741] docker0: port 1(vethbfb411a) entered blocking state
[   19.194612] docker0: port 1(vethbfb411a) entered forwarding state
[   19.200958] docker0: port 1(vethbfb411a) entered disabled state
[   19.949567] eth0: renamed from vethc4a2125
[   19.981546] IPv6: ADDRCONF(NETDEV_CHANGE): vethbfb411a: link becomes ready
[   19.987141] docker0: port 1(vethbfb411a) entered blocking state
[   19.992876] docker0: port 1(vethbfb411a) entered forwarding state
[   19.999149] IPv6: ADDRCONF(NETDEV_CHANGE): docker0: link becomes ready
[   22.521447] hassio: port 1(vethb558362) entered blocking state
[   22.525846] hassio: port 1(vethb558362) entered disabled state
[   22.532010] device vethb558362 entered promiscuous mode
[   22.536898] kauditd_printk_skb: 14 callbacks suppressed
[   22.536902] audit: type=1700 audit(1549177435.660:58): dev=vethb558362 prom=256 old_prom=0 auid=4294967295 uid=0 gid=0 ses=4294967295
[   22.541838] IPv6: ADDRCONF(NETDEV_UP): vethb558362: link is not ready
[   22.542176] audit: type=1300 audit(1549177435.660:58): arch=40000028 syscall=290 per=800000 success=yes exit=40 a0=c a1=39be600 a2=28 a3=0 items=0 ppid=1 pid=373 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="dockerd" exe="/usr/bin/dockerd" subj==unconfined key=(null)
[   22.589053] audit: type=1327 audit(1549177435.660:58): proctitle=2F7573722F62696E2F646F636B657264002D480066643A2F2F002D2D73746F726167652D6472697665723D6F7665726C617932002D2D6C6F672D6472697665723D6A6F75726E616C64002D2D646174612D726F6F74002F6D6E742F646174612F646F636B6572
[   22.774620] audit: type=1325 audit(1549177435.912:59): table=filter family=2 entries=0
[   22.781137] audit: type=1300 audit(1549177435.912:59): arch=40000028 syscall=295 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=bed9da94 items=0 ppid=783 pid=799 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj==unconfined key=(null)
[   22.810645] audit: type=1327 audit(1549177435.912:59): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D4C002D6E
[   22.822043] audit: type=1325 audit(1549177435.956:60): table=nat family=2 entries=0
[   22.829652] audit: type=1300 audit(1549177435.956:60): arch=40000028 syscall=295 per=800000 success=yes exit=0 a0=4 a1=0 a2=40 a3=bebd9a54 items=0 ppid=783 pid=801 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="iptables" exe="/usr/sbin/xtables-multi" subj==unconfined key=(null)
[   22.859124] audit: type=1327 audit(1549177435.956:60): proctitle=2F7573722F7362696E2F69707461626C6573002D2D77616974002D74006E6174002D43004F5554505554002D64003132372E302E302E3131002D6A00444F434B45525F4F5554505554
[   22.877857] audit: type=1325 audit(1549177435.980:61): table=nat family=2 entries=5
[   22.961518] eth1: renamed from veth18377c8
[   22.993559] IPv6: ADDRCONF(NETDEV_CHANGE): vethb558362: link becomes ready
[   22.999137] hassio: port 1(vethb558362) entered blocking state
[   23.004803] hassio: port 1(vethb558362) entered forwarding state
[   23.010940] IPv6: ADDRCONF(NETDEV_CHANGE): hassio: link becomes ready
[   32.773121] udevd[7]: starting version 3.2.5
[   32.793090] udevd[8]: starting eudev-3.2.5
[   32.934414] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   32.947711] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[   32.974484] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   32.983637] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[   32.999373] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   33.006980] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel
[   33.025891] s5p-mfc 11000000.codec: Direct firmware load for s5p-mfc-v8.fw failed with error -2
[   33.046876] s5p_mfc_load_firmware:73: Firmware is not present in the /lib/firmware directory nor compiled in kernel

Welcome to HassOS
hassio login:

Please don't start discussing on a merged PR. Open an Issue


Added support for windows containers

Implements #8

  It("should attach init container", func() {

can we add a test for Windows? It would make a difference if we (by mistake) change one of the fieldnames etc.

Refers to: pkg/operator/controllers/utilities_test.go:137 in 4040156. [](commit_id = 40401567af8bca4b1e80dfb38579cded2a57878c, deletion_comment = False)