Change event warning and EBUSY error when saving file

Open file from OneDrive folder
Edit file
Save file with Ctrl+S
Wait few seconds, get warning (Unable to read file after file change event), and then get error (EBUSY)

Note: Repeatable, has happened several times.
Atom Version: 1.0.19
System: Microsoft Windows 7 Enterprise
Thrown From: Atom Core
Stack Trace
Uncaught Error: EBUSY: resource busy or locked, open 'C:\Users\bellmg\OneDrive - xxx\Task Management\Action Items\xxx.txt'
At C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:128

Error: EBUSY: resource busy or locked, open 'C:\Users\bellmg\OneDrive - xxx\Task Management\Action Items\xxx.txt'
  at Error (native)
  at Object.fs.openSync (fs.js:549:18)
  at Object.module.(anonymous function) [as openSync] (ATOM_SHELL_ASAR.js:137:20)
  at Object.fs.readFileSync (fs.js:397:15)
  at Object.fs.readFileSync (ATOM_SHELL_ASAR.js:384:29)
  at File.module.exports.File.readSync (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\text-buffer\node_modules\pathwatcher\lib\file.js:261:36)
  at TextBuffer.module.exports.TextBuffer.updateCachedDiskContentsSync (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:1072:85)
  at C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\text-buffer\lib\text-buffer.js:1213:17
  at Emitter.module.exports.Emitter.emit (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\event-kit\lib\emitter.js:82:11)
  at C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\text-buffer\node_modules\pathwatcher\lib\file.js:447:40
  at _fulfilled (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:794:54)
  at self.promiseDispatch.done (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:823:30)
  at Promise.promise.promiseDispatch (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:756:13)
  at C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:564:44
  at flush (C:\Users\bellmg\AppData\Local\atom\app-1.0.19\resources\app.asar\node_modules\q\q.js:110:17)
  at doNTCallback0 (node.js:416:9)
  at process._tickCallback (node.js:345:13)

Commands

Config
{
  "core": {
    "themes": [
      "one-dark-ui",
      "atom-dark-syntax"
    ]
  },
  "editor": {
    "invisibles": {},
    "tabType": "soft"
  }
}

Installed Packages
# User
atom-yeoman, v0.3.15
json-schema, v0.1.15
linter, v1.7.2
omnisharp-atom, v0.24.14

# Dev
No dev packages

Hi @bellmg, can you please try to reproduce this in safe mode (atom --safe)?  Thanks.

Starting atom from command line with 'atom --safe' did not stop the error from happening.
I did notice that when I tried to save a new file for first time, when the 'Save File' dialog opens I get an open file warning "You can't open this location using this program. Please try a different location."
After clicking ok, I can still save the file. A few seconds after that I get the 'Unable to read file after file change event' warning, and the EBUSY error. I also noticed that after saving a file quite a few times the error stopped happening?
I can open and save the files in Notepad++ and windows text pad without issue.

@AskYous reported in #9163 that this also happens with Visual Studio.

I also experienced this issue. The trigger in my case is when I have a file open in Atom that is changed during my build process (the build process is triggered outside of Atom). When I edit the file manually in another editor there are no problems.

I get the same issue here, under Windows 7 Enterprise.  The error only occurs after saving a file opened from anywhere in my OneDrive folder structure, but it only seems to happen once.  For example, if I open a file, make a change, save it (error appears), and then make another change and save there is no error.  If I close that file, and then re-open it, edit, then save the error occurs again, but won't occur again until I close/reopen the file again.
Error doesn't occur when opening/saving files from outside my OneDrive folder.  (Google drive folder works fine).

Windows 7 x86
Atom 1.4.0 from the box, just installed, no additional packages
Steps to reproduce:

Open AssemblyInfo.cs (no matter, what is the filename) in Atom
Copy and replace file using explorer on the disk
Get this error
Cry :sob:

Seems like Atom don't want to be a file monitor for me. Sad...

Would be solved by https://github.com/atom/atom/issues/7659 so tracking it there.


medfilt2d throwing error on valid input

The docs for medfilt2d claim the filter accepts a "A 2-dimensional input array", but this is not the case:
>>> from scipy.signal import medfilt2d
>>> from numpy import array, int32
>>> a = array([[1,40,1],[2,80,2]], np.int32)
>>> medfilt2d(a)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/project/.env/local/lib/python2.7/site-packages/scipy/signal/signaltools.py", line 842, in medfilt2d
    return sigtools._medfilt2d(image, kernel_size)
ValueError: 2D median filter only supports Int8, Float32, and Float64.

Why is this error thrown? My array is 2 dimensional, and the type is one of those listed as acceptable.

... the type is one of those listed as acceptable.

Your array has type int32.  The types listed as acceptable as int8, float32 and float64.  (I don't know why the error message capitalizes those type names.)

However, if you change the data type of your array to int8, you get the same error message, so something is definitely wrong:
In [9]: a = array([[1,40,1],[2,80,2]], np.int8)

In [10]: medfilt2d(a)
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
<ipython-input-10-38125d9c044b> in <module>()
----> 1 medfilt2d(a)

/Users/warren/miniconda3scipy/lib/python3.5/site-packages/scipy-0.19.0.dev0+1cd4ab9-py3.5-macosx-10.6-x86_64.egg/scipy/signal/signaltools.py in medfilt2d(input, kernel_size)
   1173             raise ValueError("Each element of kernel_size should be odd.")
   1174
-> 1175     return sigtools._medfilt2d(image, kernel_size)
   1176
   1177

ValueError: 2D median filter only supports Int8, Float32, and Float64.

It accepts an array of unsigned 8 bit integers:
In [34]: a = array([[1,40,1],[2,80,2]], np.uint8)

In [35]: medfilt2d(a)
Out[35]:
array([[0, 1, 0],
       [0, 1, 0]], dtype=uint8)

So it looks like, at a minimum, the error message should be fixed, and the acceptable types should be noted in the docstring.

Yep, oversight on my part. Sorry.

Yep, oversight on my part.

Despite the oversight, there is in fact a problem.  Type int8 is  not accepted, but uint8 is.  See my previous comment.

I can fix the documentation to make it say 2D median filter only supports uint8, float32, and float64. and also . I might also be able to fix it to accept int8, but I'm not familiar with how some of the logistics work out. I should perhaps write a unit test to begin with. Can I build only a portion of the library instead of the whole thing, to save time?

The "easy fix" is to fix the documentation.  That would be fine.  Modifying the code to accept another data type might be easy, or it could turn out to be much more involved than you initially expect.  If you are interested, you could first create a pull request to fix the documentation to reflect the current behavior.  Then look into enhancing the function to accept int8 (or even other data types).

Can I build only a portion of the library instead of the whole thing, to save time?

I'm not sure.  It would be nice, but I haven't tried it.  Does anyone else out there know if this is possible?

Typically running the submodule-level setup.py files works fine, though maybe there's a better way to do it.

Note that when rebuilding, it only rebuilds changed parts --- so
compiling whole Scipy takes a long time only the first time.

Thank you all for the help. I was editing a C file and this required a rebuild. (When modifying Python files, I already used the in-place build as explained in HACKING.rst.txt. So any changes are directly reflected without the need to rebuild). Indeed, only the changed parts are rebuilt.
I'm submitting a PR at the moment for the documentation fix. If I am able to make the function accept other data arguments, I will send another PR.

The documentation is fixed in gh-6598. Closing since extending to more dtypes seems like a different issue.


loss text in terminal

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

setup node js
type node in terminal
create file 1.js,type in file like
let searchSelector = "div.MmsUiMaterialModal___tab___1dQI92-24-0 > div.MmsUiMaterialModal___search___1pW_I2-24-0 > div > div > div > div > div.IPT_inputBlockCell_5-66-0 > input"
select text above,then terminal -> run selected text
if  not error .type the code:
searchSelector = "div.MmsUiMaterialModal___tab___1dQI92-24-0 > div.MmsUiMaterialModal___search___1pW_I2-24-0 > div > div > div > div > div.IPT_inputBlockCell_5-66-0 > input"
selected the code and then run multi times(terminal -> run selected text)
you can get error :Uncaught SyntaxError: Invalid or unexpected token
if you press“Upward Arrow”，you will find the executed code loss text.my execute text is :> searchSelector = "div.MmsUiMaterialModal___tab___1dQI92-24-0 > div.MmsUiMaterialModal___search___1pW_I2-24-0 > div > div > div > div > div.IPT_inputB

### Tasks

Thanks for your reply
I copy a puppeteer demo from url: https://developer.chrome.com/docs/puppeteer/get-started/
This is my code:
test.zip
I run it two ways:

node .\test.js
This way is ok.
open test.js in notebook ,copy the whole code;type "node" in vscode terminal and paste code. you will find the error.

demo.zip

the demo:
https://github.com/microsoft/vscode/assets/29464607/665f7b88-16d1-4fa5-9c01-916e555fa38f

if not node.exe,eg:powershell,python etc.
This method is ok.
The picture below is the same function.
The function of the menu should be the function you planned.

The purpose of this function is to be able to view the results of a certain piece of code at any time. There is no need to go through it from start to finish.
At the same time, I can also modify the code at any time, select and press F1 to run after the modification.

This suggests that node doesn't support bracketed paste mode, which we cannot do anything about.

@meganrogge
Can you support "Run Selected Text" ?
The same as "bracketed paste "


Populate consul with default values

We are using spring-cloud-consul-config to load properties from consul. We are loading properties using @Value.
If we run our application for the first time, we would like to run with default values.
That is, if consul does not contain the properties, we would like start the application with default values and populate the consul with default values as well.
Currently the application itself didn't start if a property is not present in consul.
Could you please enhance spring-cloud-consul support,

Start the application with default values if property not present in consul
Upload default values to consul, if the property not exist in consul.

A few things, I'd recommend using @ConfigurationProperties rather than @Value. You can put defaults they. If you use @Value, do something like ${my.key:defaultValue} for a default.
I'm inclined to not change the consul key value store by uploading defaults.


Update check-spelling

Summary of the Pull Request
What is this about:
This improves the patterns used by the spell checker.
What is include in the PR:
Updates to the spell checking engine (it's faster, and it makes more suggestions about things to exclude).
Updates to exclusions (the files were suggested by the updated engine, although I've generalized the .filters instance -- you'll want to think about that).
How does someone test / validate:

Use this commit in your own fork and create PRs into it (especially one that adds a typo).
or use https://github.com/check-spelling/PowerToys and create a PR into issue-14854.
Use nektos/act and add a typo locally (just run act from the root of your clone).

Note: currently it will include this extra segment in each comment:
Available dictionaries could cover words not in the dictionary
cspell:cpp/cpp.txt (104293) covers 208 of them
cspell:filetypes/filetypes.txt (337) covers 39 of them
cspell:html/html.txt (542) covers 28 of them
cspell:css/css.txt (993) covers 27 of them
cspell:django/django.txt (2342) covers 21 of them
cspell:aws/aws.txt (1485) covers 19 of them
cspell:golang/go.txt (7745) covers 18 of them
cspell:java/java.txt (33524) covers 12 of them
cspell:csharp/csharp.txt (123) covers 11 of them
cspell:lua/lua.txt (391) covers 9 of them
cspell:fullstack/fullstack.txt (181) covers 8 of them
cspell:scala/scala.txt (2752) covers 7 of them
cspell:rust/rust.txt (112) covers 7 of them
cspell:python/python.txt (364) covers 7 of them
cspell:npm/npm.txt (671) covers 7 of them
cspell:ruby/ruby.txt (354) covers 4 of them
cspell:php/php.txt (9785) covers 4 of them
cspell:dotnet/dotnet.txt (9824) covers 3 of them
cspell:node/node.txt (9611) covers 1 of them
cspell:bash/bash-words.txt (22) covers 1 of them
cspell:ada/ada.txt (72) covers 1 of them
Consider adding them using:
      with:
        extra_dictionaries:
          cspell:cpp/cpp.txt
          cspell:filetypes/filetypes.txt
          cspell:html/html.txt
          cspell:css/css.txt
          cspell:django/django.txt
          cspell:aws/aws.txt
          cspell:golang/go.txt
          cspell:java/java.txt
          cspell:csharp/csharp.txt
          cspell:lua/lua.txt
          cspell:fullstack/fullstack.txt
          cspell:scala/scala.txt
          cspell:rust/rust.txt
          cspell:python/python.txt
          cspell:npm/npm.txt
          cspell:ruby/ruby.txt
          cspell:php/php.txt
          cspell:dotnet/dotnet.txt
          cspell:node/node.txt
          cspell:bash/bash-words.txt
          cspell:ada/ada.txt

To stop checking additional dictionaries, add:
      with:
        check_extra_dictionaries: ''

It might make sense to add the following to the spelling workflow:
        with:
          extra_dictionaries:
            cspell:cpp/cpp.txt
            cspell:filetypes/filetypes.txt
            cspell:html/html.txt
            cspell:css/css.txt

or
        with:
          extra_dictionaries:
            cspell:filetypes/filetypes.txt
            cspell:html/html.txt
            cspell:css/css.txt

The inclusion of cpp.txt is questionable as unfortunately it has quite a few typos included (I haven't had the energy to edit the file to remove them), so this would unfortunately mean the spell checker would skip flagging some actual typos. I think that filetypes.txt, html.txt, and css.txt would be fairly reasonable.
Alternatively, it might be best to just go with:
        with:
          check_extra_dictionaries: ''

which turns off the intelligence entirely.
Quality Checklist

[x] Linked issue: #14854
[x] Communication: I've discussed this with core contributors in the issue.
[x] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[x] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Ah, yes, We'd, this upgrade will no longer trip on that... (it sees We as a two letter word, and two letter words aren't worth checking, ...) I'll undo the drop in the branch for this PR, and then once it lands that can be dropped when someone else gets advice from the upgraded engine.

The above comments give a sense of the items that can be removed once this upgrade is done...

@jsoref you sir are my hero, had you pointed us at a quick link, i would have done it

I was going to, but then I checked and realized there was already a pattern trying to handle it...

Agreed on permission q, why

The pull_request_target (and push for that matter) defaults to having a lot of write permissions (pull_request doesn't have them & originally couldn't get them). So these workflow changes are actually reducing the permissions carried around (instead of having everything, it just has things it needs).
For the push event It needs the contents: write permission in order to make a comment on a commit (I really wish there was a distinct permission for adding / updating a comment, but there isn't).
This is GitHub's basic permissions explanation:
https://docs.github.com/en/actions/security-guides/automatic-token-authentication
(I find it incredibly confusing, and I think it took me months to work out a set of permissions that worked for this action/workflow.)
I should write a page that explains each piece (since this is definitely a FAQ). I'm pretty sure I've written it up in a few places (although I can't think of how to find the where for that right now).
I know that I needed pull-requests: read when running on: push w/ a private repository and checking to see if there's an open PR (this makes sense intuitively).
Here's a run where the workflow (running from https://github.com/jsoref/examples-testing/commit/016d1c5b7c1d71681874012a988cad2d283b2265) is trying to comment on a pull_request (w/ pull-requests: read):
https://github.com/jsoref/examples-testing/runs/4447430085?check_suite_focus=true#step:5:1917
  + curl -L -s -S -H 'Authorization: token ***' -H 'Content-Type: application/json' -H 'Accept: application/vnd.github.comfort-fade-preview+json' --data @/tmp/tmp.n2JvPlGPOK https://api.github.com/repos/jsoref/examples-testing/issues/9/comments
  + '[' 0 -gt 0 ']'
  + '[' -n 1 ']'
  + cat /tmp/tmp.Q0qWz2rEmg.json
  {
    "message": "Resource not accessible by integration",
    "documentation_url": "https://docs.github.com/rest/reference/issues#create-an-issue-comment"
  }

Effectively, what matters is that when this workflow runs for on: push, it needs:
contents: write to access:
https://docs.github.com/en/rest/reference/permissions-required-for-github-apps#permission-on-contents
POST /repos/:owner/:repo/commits/:sha/comments (~:read~ sic)
And when it runs for on: pull_request_target, it needs:
pull-requests: write -- with only pull-requests: read, it fails:
https://github.com/jsoref/examples-testing/runs/4450983220?check_suite_focus=true#step:5:1564
  + curl -L -s -S -H 'Authorization: token ***' -H 'Content-Type: application/json' -H 'Accept: application/vnd.github.comfort-fade-preview+json' --data @/tmp/tmp.7SWv7A8UtC https://api.github.com/repos/jsoref/examples-testing/commits/4fa22a1d590c1c878d13c925be716bf31f1ed350/comments
  + '[' 0 -gt 0 ']'
  + '[' -n 1 ']'
  + cat /tmp/tmp.oXNHd50OoJ.json
  {
    "message": "Resource not accessible by integration",
    "documentation_url": "https://docs.github.com/rest/reference/repos#create-a-commit-comment"
  ++ jq -r '.url // empty' /tmp/tmp.oXNHd50OoJ.json
  }

https://docs.github.com/en/rest/reference/permissions-required-for-github-apps#permission-on-pull-requests
POST /repos/:owner/:repo/issues/:issue_number/comments (:write)

@jsoref , Thanks a lot for the explanation. And thanks again for the contribution.
I've added a commit to fix the conflicts that appeared since then.
@crutkas , Any issue with this going it?

/azp run

@DHowett you good with this?


Unify deprecation message

There're several duplicates of deprecation message, e.g https://github.com/gradle/gradle/blob/614bd5896a5bbc8205519c8d37dfc69b0ad00b9c/subprojects/core/src/main/java/org/gradle/initialization/StartParameterBuildOptions.java#L93
and https://github.com/gradle/gradle/blob/614bd5896a5bbc8205519c8d37dfc69b0ad00b9c/subprojects/core/src/main/java/org/gradle/initialization/StartParameterBuildOptions.java#L171
Since they're similar wording, we should collect and unify them to make it more easy to maintain.

I'd recommend splitting out the logic that constructs messages from the deprecation logger into its own class. It seems like having a DeprecationWarning class would be a good move. Right now we have a bunch of hardcoded "Gradle 5.0" messages, when really the version number should be automatically inferred from the current major release.

Can we first define how this change would surface to the user? It's not fully clear to me based on the description.
For example I am not necessarily a fan of making gradle -? harder to read by adding information on when the option will be removed. What I'd like to see here is: When I as user do x then I see the following.

@bmuschko Sure, added above. Actually there's no big change.

Thanks for clarifying. Instead of adding a deprecation message that indicates the version we want to remove the feature I'd rather want to know why it has been deprecated or what the replacement for it should be. For that reason I am advocating for not adding it to the output of gradle -?.
I also think this reads a bit weird:
deprecated - has been deprecated and is scheduled to be removed in Gradle 5.0
This should be good enough:
deprecated - scheduled to be removed in Gradle 5.0


Failing run-after test for namespaces

Description
There are more and more situations where this test is failing. Cypress is clicking on the Delete tooltip or button in the backdrop and the namespace can't be deleted.

Expected result
Tests are passing without /retest

Actual result
https://status.build.kyma-project.io/view/gs/kyma-prow-logs/pr-logs/pull/kyma-project_busola/1740/pre-busola-integration-test-k3s-namespace/1557620794555633664

Steps to reproduce

Open PR
Run tests

Troubleshooting

The detached element is re-rendered by React. We could either check why it happens and fix the rerendering or use cypress click({force: true})


Video Gallery View

This PR is part of a bigger PR that is being split up into chunks.
Checklist for this PR:

[ ] - path-builder setup,
[ ] - modularization of Django templates (html),
[ ] - dynamic URL's
[ ] added MEDIA_URL and MEDIA_ROOT to settings.py that will be where we link the users DropBox, Google Drive, or other Externall Storage for ease of access.

Overall PR is to enable user to view all videos in a "Gallery" and this Gallery will be pulling these videos from a potentially dynamic upload path of user's choice. no issues are fully resolved so not resolving any here..

Hmm ya after I pushed the changes you asked for (at least on my side) the
pages that i updated said outdated was just trying to make it easier on you
next time around. Do you not see any commits from yesterday ?
On Sun, Apr 24, 2022 at 6:03 PM Meher Lippmann @.***>
wrote:

@.**** commented on this pull request.
In osCam/pathbuilder/views.py
https://github.com/ChicoState/open-source-security-camera/pull/71#discussion_r857202072
:

full_path=""

for data in _full_path:

full_path+=data.path

full_path += "/"+request.POST.get("$PATH")
cur_path_builder: Path = None

if no Path objects exist yet for this user

- we create one and peek at its children

if Path.objects.filter(user=this_user).exists():

# turn on Storate update permissions.

cur_path_builder = Path(

	user=this_user,

	path= "/" + request.POST.get("$PATH"),

)

next_path_list=getNextPathList(this_user, this_path.path)

This file is not listed as "outdated" for me, and I don't see the changes
reflected.
I thought that if you commit a change while the PR is still open that the
change should then be reflected in the files for review?
—
Reply to this email directly, view it on GitHub
https://github.com/ChicoState/open-source-security-camera/pull/71#discussion_r857202072,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALF4UAJTQYHLWAWD37G555TVGXVNVANCNFSM5UEHHVTA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>

--
Kevin Douglass
Software Engineer Intern, eBay
Vice President, ACM - CSU Chico
(916)/581-9298


Faster tests by more relaxed gas estimation

About half of pytest execution time is spent on gas estimation .  The gas estimation tries many gas limits and performs a binary search.
This issue keeps track of running tests faster by either

increasing the binary-search tolerance, or
turn off the gas limitation and just give a lot of gas.

When I change the tolerance from 21000 to 2100000,
time pytest -s raiden_contracts/tests/test_channel_open.py --profile

finishes in 13 seconds instead of 20 seconds.

#805 did it better.


You need to install "jmespath" prior to running json_query filter

error:
TASK [caddy-ansible : Set variable with list of available releases] ************
fatal: [default]: FAILED! => {"msg": "You need to install \"jmespath\" prior to running json_query filter"}

Error showed today (18.12.2023r). Previous build was performed 3 days ago (15.12.2023r) without issues
build on image hashicorp/packer:1.9.1
packer (machine.pkr.hcl):
build {
  ......

  provisioner "ansible" {
    user          = "app"
    galaxy_file   = "./ansible/requirements.yml"
    playbook_file = "./ansible/playbook-step-2.yml"
    ansible_env_vars = [
      "ANSIBLE_SSH_ARGS='-oHostKeyAlgorithms=+ssh-rsa -oPubkeyAcceptedKeyTypes=ssh-rsa'"
    ]
    extra_arguments = [
      "--extra-vars",
      "app=${var.app} env=${var.env}"
    ]
  }

galaxy file (requirements.yml)
roles:
- { src: "git+https://github.com/caddy-ansible/caddy-ansible.git" }

playbook file (playbook-step-2.yml)
- name: Provision Image - Step 2
  hosts: all
  become: true
  tasks:
    - name: ensure exists caddy http server
      include_role: role=caddy-ansible
      vars:
        caddy_setcap: true
        caddy_systemd_capabilities_enabled: true
        caddy_systemd_capabilities: "CAP_NET_BIND_SERVICE"
        caddy_config: "{{ lookup('template', 'templates/Caddyfile.j2') }}"

    - name: enabled caddy
      systemd: name=caddy state=started

adding version to role in requirements.yml like so
roles:
- { src: "git+https://github.com/caddy-ansible/caddy-ansible.git", version: "v3.2.0" }

seems to solve this issue


Rename to "pansharpen"

The cli command and python module are named pansharpen. Maybe the repo should be too?

Repo renamed to rio-pansharpen.


chore(clerk-js,types,shared): Deprecate __unstable methods for organizations

Description
This PR continues with the deprecation of the underlying mechanism for organizations.
For context those values were passed around in order to trigger automatic revalidations when devs where reading invitationList or membershipList from useOrganization. Those have been deprecated in favour of invitations and memberships and  we are introducing mutations for those here.
Automatic revalidations of lists after calling clerk-js methods may return in the future as an "opt-in" mechanism

Checklist

[ ] npm test runs as expected.
[ ] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[x] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


CaptivePortal Fails to Upload/Accept Template

Describe the bug
uploading modified captiveportal template fails. does not show up in the template list. however uploading unmodified template file is accepted.  even just adding a image file in the archive, makes it fail to upload. also tried upload previous template file and those are not accepted also.
what I have done so far

modified as little as possible, even adding 1 image file fails to upload
Reset to default the system, set minimum settings and upload template fails
changed to development version

To Reproduce
Steps to reproduce the behavior:

Go to 'services'
Click on 'captive portal'
Click on 'administrator'
Click on 'templates'
Click on 'add'
Enter name and upload template file

Expected behavior
it should accept the new modified template file. im just using simple html.
Relevant log files
most not acepted template show no logs... some that would show this on log
2020-12-29T15:25:37   configd.py[21139]   [a922a169-75f8-4825-b177-b9f86287c90c] Script action failed with Command '/usr/local/opnsense/scripts/OPNsense/CaptivePortal/strip_template.py 'cp_2cfdbd8d-c875-430b-af03-3897a1af90ff.tmp'' returned non-zero exit status 1. at Traceback (most recent call last): File "/usr/local/opnsense/service/modules/processhandler.py", line 479, in execute stdout=output_stream, stderr=error_stream) File "/usr/local/lib/python3.7/subprocess.py", line 363, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '/usr/local/opnsense/scripts/OPNsense/CaptivePortal/strip_template.py 'cp_2cfdbd8d-c875-430b-af03-3897a1af90ff.tmp'' returned non-zero exit status 1.
upload the default unmodifed template shows
2020-12-29T15:34:49   configd.py[21139]   [9a61b866-280c-4471-a8c1-58002e77b404] strip user captiveportal web template package and return new base64 encoded content
Additional context
I would believe that 20.7.5 should be working since at that time, I uploaded a christmas template, which was accepted.
OPNsense 20.7.7_1-amd64
Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 cores)
OPNsense 20.7.7_1-amd64
Intel(R) Celeron(R) CPU 1037U @ 1.80GHz (2 cores)
OPNsense 20.7.7_1-amd64
Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz (4 cores)
OPNsense 21.1.a_272-amd64
Intel(R) Celeron(R) CPU 1037U @ 1.80GHz (2 cores)

Probably #4533

Yes, was #4533

Yes, was #4533


DeformNetwork.timenet is unused

It is never applied in DeformNetwork.forward. Is this intentional? https://github.com/search?q=repo%3Ahustvl%2F4DGaussians self.timenet&type=code

Indeed, we have tried using timenet for ablation study but it seems not work very well. So we didnt use it.
Thank you for your comment, we will delete it in the next version.


Replace spec indices search with regex

This allows you to search for indices regardless of the order of [], * and ?
Causes panic if the expression does not match the regex. For example, if it contains no or more than one token. This can be avoided if the function returns an option.

Could you add several examples of supported expressions inside spec_ind docs?

Lets replace match panic with PatchResult.
It's better to compile regexpr once: see https://github.com/rust-embedded/svdtools/blob/9ab01ef424ead7fdb1706e6efcf8609f01d47e79/src/html/html_cli.rs#L30
Fix example. See CI error

You can just ignore it: https://doc.rust-lang.org/rustdoc/write-documentation/documentation-tests.html#attributes


Support for appdef extends

This adds support for the extends keyword for application definitions.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.008%) to 78.47%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/dataconverter/validation.py
1
68.2%

pynxtools/dataconverter/helpers.py
1
79.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
2821

Relevant Lines:
3595

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.008%) to 78.47%

Files with Coverage Reduction
New Missed Lines
%

pynxtools/dataconverter/validation.py
1
68.2%

pynxtools/dataconverter/helpers.py
1
79.21%

Totals

Change from base Build<PHONE_NUMBER>:
0.008%

Covered Lines:
2821

Relevant Lines:
3595

💛  - Coveralls

@rettigl The phoibos example now runs through without a warning when using NXmpes_arpes.
I needed to make the following changes to the config file:
diff --git a/specsscan/config/NXmpes_arpes_config.json b/specsscan/config/NXmpes_arpes_config.json
index edf8162..0ae5b3c 100755
--- a/specsscan/config/NXmpes_arpes_config.json
+++ b/specsscan/config/NXmpes_arpes_config.json
@@ -1,7 +1,7 @@
 {
   "/@default": "entry",
   "/ENTRY[entry]/@default": "data",
-  "/ENTRY[entry]/definition": "NXmpes",
+  "/ENTRY[entry]/definition": "NXmpes_arpes",
   "/ENTRY[entry]/definition/@version": "None",
   "/ENTRY[entry]/title": "@attrs:metadata/entry_title",
   "/ENTRY[entry]/start_time": "@attrs:metadata/timing/acquisition_start",
@@ -135,7 +135,7 @@
     "diameter": 300.0,
     "diameter/@units": "mm",
     "entrance_slit": {
-      "shape": "curved",
+      "shape": "curved slit",
       "size": 1.0,
       "size/@units": "mm"
     },
@@ -337,13 +337,13 @@
   },
   "/ENTRY[entry]/data": {
     "@axes": "@data:dims",
-    "AXISNAME_indices[@*_indices]": "@data:*.index",
+    "@*_indices": "@data:*.index",
     "@signal": "data",
     "data": "@data:data",
     "data/@units": "counts",
-    "AXISNAME[*]": "@data:*.data",
-    "AXISNAME[*]/@units": "@data:*.unit",
-    "AXISNAME_depends[@*_depends]": "@attrs:metadata/scan_info/coordinate_depends/*",
+    "*": "@data:*.data",
+    "*/@units": "@data:*.unit",
+    "@*_depends": "@attrs:metadata/scan_info/coordinate_depends/*",
     "energy/@type": "kinetic"
   }
 }

I think it all makes sense except the change of AXISNAME might not be that obvious. While using the upper case notation for nexus groups I think it does not make much sense to apply this concept to field namefitting. For a group we would actually write an NX_class attribute to the file but for fields we have no such concept and we have to completely rely on the namefitting concept for reading the file. Therefore, I think it makes sense to avoid giving information which will be lost while writing and validating the file. We could however think to add an additional check which checks that all the fields written in AXISNAME are actually in the @axes array (which actually associates them to AXISNAME), but this will be something very special to NXdata and might be confusing in other places. Anyways, without using AXISNAME this works fine.

I also created a PR here https://github.com/OpenCOMPES/specsanalyzer/pull/44 to bring the changes to specsanalyzer

LGTM, though I don't fully understand what the code is doing. I checked with NXmpes_arpes as outlined above and it works. Should we maybe add a test case for an extending app def?

Yes, I think it makes sense to make an extends case for NXtest. I'll add it. Also there are still some problems in NXellipsometry. It's probably due to the validation itself and not the extends but I would bring the fixes here, too.

@lukaspie, this is what I get when I run the xps examples with NXxps
I worked on this branch https://github.com/FAIRmat-NFDI/nexus_definitions/pull/170, and pynx-xps main (added NXxps to the supported readers there, though).
For the sle example
Using xps reader to convert the given files:
• EX439_S718_Au.sle
• eln_data_sle.yaml
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/geometries, hasn't been supplied.
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/SAMPLE[sample]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/geometries, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/SAMPLE[sample]/transformations, hasn't been supplied.
Field /ENTRY[Au_in_25mBar_O2__Au4f]/data/energy/@long_name written without documentation.
Field /ENTRY[Au_in_vacuum__Au4f]/data/energy/@long_name written without documentation.
The output file generated: Au_25_mbar_O2_no_align.nxs.

For the phi example (with --ignore-undocumented)
dataconverter --nxdl NXxps --reader xps --ignore-undocumented SnO2_10nm.spe eln_data_phi.yaml
Using xps reader to convert the given files:
• SnO2_10nm.spe
• eln_data_phi.yaml
The required group, /ENTRY[Su1s]/geometries, hasn't been supplied.
The required group, /ENTRY[Su1s]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Su1s]/SAMPLE[sample]/transformations, hasn't been supplied.
The output file generated: output.nxs.

@lukaspie, this is what I get when I run the xps examples with NXxps
I worked on this branch FAIRmat-NFDI/nexus_definitions#170, and pynx-xps main (added NXxps to the supported readers there, though).
For the sle example
Using xps reader to convert the given files:
• EX439_S718_Au.sle
• eln_data_sle.yaml
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/geometries, hasn't been supplied.
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_25mBar_O2__Au4f]/SAMPLE[sample]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/geometries, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Au_in_vacuum__Au4f]/SAMPLE[sample]/transformations, hasn't been supplied.
Field /ENTRY[Au_in_25mBar_O2__Au4f]/data/energy/@long_name written without documentation.
Field /ENTRY[Au_in_vacuum__Au4f]/data/energy/@long_name written without documentation.
The output file generated: Au_25_mbar_O2_no_align.nxs.

For the phi example (with --ignore-undocumented)
dataconverter --nxdl NXxps --reader xps --ignore-undocumented SnO2_10nm.spe eln_data_phi.yaml
Using xps reader to convert the given files:
• SnO2_10nm.spe
• eln_data_phi.yaml
The required group, /ENTRY[Su1s]/geometries, hasn't been supplied.
The required group, /ENTRY[Su1s]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/transformations, hasn't been supplied.
The required group, /ENTRY[Su1s]/SAMPLE[sample]/transformations, hasn't been supplied.
The output file generated: output.nxs.

Does it make sense since the example is not ready or does it seem to you that there is something up with the validation itself?

This is all fine, these examples currently don't populate the transformations. Good that the validation picks that up though, so should be fine. Actually, maybe NXxps is not yet a good test for this, I was probably thinking about validating this feature in a different way. I think it's okay to just test it on NXmpes_arpes and NXellips, NXxps does not add anything that is not also covered by these two.


In Mobile view, Dropdown button is not working.

Bug Report
Dropdown menu is not working
Description
In mobile view , the dropdown menu is not working properly .It must be open the contents of menu while clicking on it .Otherwise the user will face problem in order to perform the menu's functionality.
Steps to Reproduce
[Outline the steps to reproduce the behavior:]

Go to 'Hero page '
Click on 'mobile view'
Click on 'menu button'
4.The button isn't working.
See error

Expected Behavior
As u clicked on the dropdown menu button in the mobile view, it should open with a dropdown.
Actual Behavior
Currently ,while clicking on the menu dropdown button , it is not working .
Screenshots
https://github.com/TailoredUI/TailoredUI/assets/130597958/93d6de6c-f894-42fb-8525-55dce5f81965
Environment

Operating System:  Windows, macOS, Linux
Browser: Brave, Chrome , Safari , Microsoft Edge

can you assign me this issue under gssoc 24.


Code folding improvements + bugs

Multi-line collections cannot be folded at all
Individual cases in a switch cannot be folded at all
This range folds entirely into a single line when only the comment should be folded; instead, the first line of the decl right below it is also collapsed.

Here, the folding marker is incorrectly on the line above the return statement. It is in the correct spot if the comment is removed. It behaves just like the above, where the following line is consumed by folding the comment. I'm guessing this implies all comments should be foldable, but that if a foldable statement exists below a comment, it mistakenly interferes with the ability to fold that statement.

Trailing )'s are not folded up the way trailing }'s are

Unless they're preceded by a }:

Tracked in Apple’s issue tracker as rdar://116877123

I think the folding issues with comment should be fixed by https://github.com/apple/sourcekit-lsp/pull/804 but the other issues are definitely also ones we should fix.

If anyone is interesting in fixing these: The folding ranges are computed in https://github.com/apple/sourcekit-lsp/blob/d043dc068d6955a30f063e4f5550e63516a24d96/Sources/SourceKitLSP/Swift/SwiftLanguageServer.swift#L659, which is a fairly isolated SwiftSyntax visitor that doesn’t require too much outside knowledge apart from swift-syntax trees.
Tests live in https://github.com/apple/sourcekit-lsp/blob/main/Tests/SourceKitLSPTests/FoldingRangeTests.swift


Turn on build library for distribution

Context
I am turning on Xcode's 'Build library for distribution' flag in the vain hope that this will stop the compilation errors every time we move to a new version of XCode (and hence the swift language)
Hopefully, we will have no more 'Failed to build module 'Introspect'; this SDK is not supported by the compiler (the SDK is built with 'Apple Swift version 5.7', while this compiler is 'Apple Swift version 5.7.1 )'.  errors
Checklist

[x] Change meets or does not compromise the Baseline Security Requirements

This is just a test to see if I can get the new Xcode version to build


[building-rollup] missing hash in file name of js module in index.html

The index.html doesn't contain file names with hash of js modules after rollup build.
I tried createDefaultConfig and createCompatibilityConfig.
index.html
<script type="module" src="./src/index.js" crossorigin></script>
<script type="module" src="./src/components/app-shell.js" crossorigin></script>

index.html after the build
<link rel="preload" href="index.js" as="script" crossorigin="anonymous">
<link rel="preload" href="app-shell.js" as="script" crossorigin="anonymous">

HTMLScriptElement.prototype?["./index.js","./app-shell.js"]
window.importShim(e)})):["./legacy/index.js","./legacy/app-shell.js"]

@LarsDenBakker We need the hash in file names for revalidate http cache on the client. Could you fix this issue?

@LarsDenBakker Do you know any solution?

Rollup has an option for this, we need to add it. PRs welcome for this one.

This issue has been solved in #838.

thx 🤗

thx :+1:


Include a lower bound in the dependency version to ensure consistent restore results.

Hi,
i must be need some glasses or something, cant get around this error:
Restore completed in 68.13 ms for D:\prod\structures\DirectManipulation\Tekla.BIM.Utilities\Tekla.BIM.Utilities.csproj.
WARNING: NU1604: Project dependency Tekla.Common.Geometry does not contain an inclusive lower bound. Include a lower bound in the dependency version to ensure consistent restore results.
Committing restore...
Assets file has not changed. Skipping assets file writing. Path: D:\prod\structures\ObjDrop\NugetGenStuff\Tekla.BIM.Geometry\project.assets.json
I can see the package version we specified in the central store exists in one of the feeds, and i can install it... the first version in the feed is 4.5.1 and thats the one that gets intalled
".NETFramework,Version=v4.5.1": {
  "Tekla.Common.Geometry/4.5.1": {
    "type": "package",
    "compile": {

    },
    "runtime": {

    }
  },

can the reason for this be  that the packages dont include lib/net451

If i add the Version="4.5.9" into the project that everything restores fine and works...
Can someone give a help with this one.
thanks

ok i think i found after going through the targs and props file. My project contain packages.config (empty ones) after removing the files it start working

I ran into this same issue. You saved the day @jmecosta


Man pages doesn't work

When I try to execute the command man man, man says that there is no manual entry for man.
I tried to add this line in my config:
pkgs.manpages
But this didn't work.
Is this a bug ?

The default configuration.nix imports the minimal profile, which disables documentation. I just removed the import from my config, but you could also just set documentation.enable = true.


remove invert log ;B

Bug
Description
invert_log method should have been removed.
Checklist

[x] My code follows the style guidelines of this project
[x] I have rebased the branch with the latest code from master
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas, and at the top of new interactors
[x] I have added tests that prove my fix is effective or that my feature works
[x] The build is passing

Waiting on tests.


Kotlin Documentation leaks some weird public APIs

http://square.github.io/okhttp/4.x/okhttp/okhttp/okhttp3/-dns/index.html

Seems like we removed them? We might still have weird public APIs though.
PR: https://github.com/square/okhttp/pull/5158


Configure rolling update

ECS support rolling deployments policies. As compose up updates an existing application using CloudFormation changeset, those will be applied. Service must be created with rolling policy and parameters set according to deploy section in compose file (optionaly relying on custom extensions when relevant)

Compose file format (based on Docker Swarm model) do support deploy.updateConfig.parallelism, as "The number of containers to update at a time".
AWS ECS uses a distinct model based on percent of healthy services during update: MaximumPercent/MinimumHealthyPercent
If deploy.replicas is set, we can compute those percents:

MaximumPercent = (deploy.replicas + parallelism) / deploy.replicas
MinimumHealthyPercent = (deploy.replicas - parallelism) / deploy.replicas

otherwise, we can warn user if deploy.update_config.parallelism has been set and let ECS apply defaults (200%/100%)
Note: this approach will probably be a problem once we introduce auto-scaling support; as replicas won't be relevant anymore.
We also can introduce support for x-aws-maximun_percent and x-aws-minimun_percent to give end-user full control on ECS rolling update policy.

Hmm, I think that deploy.updateConfig.parallelism is not very generic, we should open a spec issue but I would be inclined to have x-aws specific controls as well, and then either change the spec to add a generic "rate" that can be used, or treat parallelism as being able to be an equivalent of rate and use that formula for aws but state in the spec that it isnt a precise mapping to paralllelism.


Add icon for Airbnb

Description

Fixes #(issue)

Type of change

:x: Bug fix (non-breaking change which fixes an issue)
:x: Icon addition (non-breaking change that adds/modifies Lawnicons's icons)
:x: General change (non-breaking change that doesn't fit the above categories like copyediting)

Icons addition information

Icons added

App Name (package.name) - added from icon request form
App Name (package.name)
App Name (package.name)

Icons updated

App Name (package.name)
App Name (package.name)

Icons linked

App Name (linked package.name to @drawable/package)
App Name (linked package.name to @drawable/package)

Please resolve the conflicts, and you should open each PR in a new branch to avoid necessary changes.


Module Not Recognized

Issue Type: Bug
I am trying to import opencv to use cv2, it says requirement already satisfied but when I write any program using it it says cv2 not recognized. I am quite bugged with this issue, kindly fix it.

/needsMoreInfo

If your code doesn't run at all then it is most likely not a problem with VS Code as we don't execute your code in any special way. Is it just not offering completions?

Closing due to lack of update

I am sorry for not replying to the mail, apparently I missed ur msg
somehow…however, the problem’s now has been resolved. VS code is working
properly now :) thank you so much for the assistance, really appreciate it!
On Mon, 13 Sep 2021 at 8:27 PM Logan Ramos @.***> wrote:

Closing due to lack of update
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/132252#issuecomment-918278667,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASUWDC43IS6RXDLSQFG7FMTUBYGNJANCNFSM5DLSSBAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Suggestion: release a month tag (version) of this project and of the viya4-deployment project with tag name like SAS Stable version

Suggestion:  have this project + viya4-deployment project in sync with SAS cadence version (such as 2024.02, 2024.03 etc.) I suggest to release a monthly version/tag of these two projects so that the monthly version of these projects will be in sync with the SAS requirements for that version. So for example, version 2024.03 of the projects will be inline with the SAS requirements for Stable 2024.03. This will make life easier to users consuming these projects.

As an example for this suggestion see the SAS Content Assessment Tool which has versions corresponding to the SAS cadence versions https://support.sas.com/downloads/package.htm?pid=2465


[Question] How can I change the secrets encryption provider for RKE2 in Harvester?

I wasn't sure if I should post this as a bug or question but I'm mostly just interested in replacing the secrets encryption provider from the default aes-cbc to kms.
According to this comment https://github.com/harvester/harvester/issues/2600#issuecomment-1210754985 made in a different issue i should be able to add my own configurations to /etc/rancher/rke2/config.yaml.d/. This way in theory i can pass flags to the apiserver to point it to a different EncryptionConfiguration file and change the encryption provider that way. However if I point to a different config file and restart the rke2-server.service, it doesn't come back up. Below should be the relevant logs, where the last part keeps repeating.
/etc/rancher/rke2/config.yaml.d/10-apiserver.yaml:
kube-apiserver-arg:
  - encryption-provider-config=/<path-to>/encryption-config.yaml
  - kube-apiserver-extra-mount=/var/run/kmsplugin/:/var/run/kmsplugin/

encryption-config.yaml:
apiVersion: apiserver.config.k8s.io/v1
kind: EncryptionConfiguration
resources:
  - resources:
    - secrets
    providers:
    - aescbc:
      keys:
      - name: aescbckey-2023-04-10T13:22:57Z
        secret: <secret>
    - kms:
        name: aws-encryption-provider
        endpoint: unix:///var/run/kmsplugin/socket.sock
        cachesize: 1000
        timeout: 3s
    - identity: {}

Apr 11 15:30:14 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:14Z" level=info msg="etcd data store connection OK"
Apr 11 15:30:14 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:14Z" level=info msg="Waiting for API server to become available"
Apr 11 15:30:15 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:15Z" level=warning msg="bootstrap key already exists"
Apr 11 15:30:15 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:15Z" level=info msg="Reconciling etcd snapshot data in rke2-etcd-snapshots ConfigMap"
Apr 11 15:30:15 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:15Z" level=info msg="Waiting for containerd startup: rpc error: code = Unknown desc = server is not initialized yet"
Apr 11 15:30:16 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:16Z" level=info msg="Containerd is now running"
Apr 11 15:30:16 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:16Z" level=info msg="Pulling images from /var/lib/rancher/rke2/agent/images/cloud-controller-manager-image.txt"
Apr 11 15:30:16 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:16Z" level=info msg="Imported images from /var/lib/rancher/rke2/agent/images/cloud-controller-manager-image.txt in 2.>
Apr 11 15:30:16 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:16Z" level=info msg="Pulling images from /var/lib/rancher/rke2/agent/images/etcd-image.txt"
Apr 11 15:30:16 harvester-test-node-1 rke2[3347]: time="2023-04-11T15:30:16Z" level=info msg="Imported images from /var/lib/rancher/rke2/agent/images/etcd-image.txt in 1.029554ms"
Apr 11 15:28:25 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:25Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:30 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:30Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:35 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:35Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:38 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:38Z" level=info msg="Container for etcd is running"
Apr 11 15:28:38 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:38Z" level=info msg="Container for kube-apiserver not found (no matching container found), retrying"
Apr 11 15:28:40 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:40Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:45 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:45Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:50 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:50Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:55 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:55Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:28:58 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:58Z" level=info msg="Container for etcd is running"
Apr 11 15:28:58 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:28:58Z" level=info msg="Container for kube-apiserver not found (no matching container found), retrying"
Apr 11 15:29:00 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:29:00Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:29:05 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:29:05Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:29:10 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:29:10Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:29:15 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:29:15Z" level=info msg="Waiting to retrieve kube-proxy configuration; server is not ready: https://<IP_ADDRESS>:9345/v1-rke>
Apr 11 15:29:18 harvester-test-node-1 rke2[1087]: time="2023-04-11T15:29:18Z" level=info msg="Container for etcd is running"
...

Bad syntax, should be:
kube-apiserver-arg:
  - encryption-provider-config=/<path-to>/encryption-config.yaml
kube-apiserver-extra-mount:
  - /var/run/kmsplugin/:/var/run/kmsplugin/


Feat: revamp the Sign-in and Sign-up page

Closes #929
Fixes Issue
This PR revamp the Sign-in and Sign-up page of the Android app
Changes proposed

revamp sign-in and sign-up age
fix app theme
update Android version 33 -> 34
fix the dark theme for the Sign-in and Sign-up page

Screenshot

Thank you for your contribution :)

Hi @codervivek5, I didn't receive any points for this merge


Is it possible to calculate dense of state by using cp2k+sirius

cp2k can calculate PDOS with quickstep, and is it possible to work with SIRIUS to get the DOS? To calculate the DOS, does SIRIUS support k-points or just gamma point?

Hi @LM99v ! Sirius supports both k-points and Gamma-point only. There is an API to fech Fermi level and KS eigen-energies from Sirius, then the computation of DOS becomes a trivial task on cp2k side (which, to be honest, somebody has still to do).