Sorald throws (and catches) exceptions during repair

@slarse I think you are aware of most of these, but here is a list of common types of crashes that we face:
Crash in sorald.processor.IteratorNextExceptionProcessor::process
Crash in sorald.processor.CastArithmeticOperandProcessor::process
Crash in sorald.processor.InterruptedExceptionProcessor::process
Crash in sorald.processor.UnclosedResourcesProcessor::process

I think we only have open issues for sorald.processor.CastArithmeticOperandProcessor::process (#125). I'll have a look at the others this week.

I can't reproduce
Crash in sorald.processor.IteratorNextExceptionProcessor::process
I don't experience that crash, neither if I do targeted repair for that violation nor if I do all repairs for that key. There are also no other violations in that file, so it can't be down to the order of repairs. @khaes-kth can you try to run it and see if you get a crash?

Oh wait, all of these crashes are caused by the same thing (not the processors). It's this:
at sorald.UniqueTypesCollector.checkIfThereIsTheSameClassInTheOriginalPath(UniqueTypesCollector.java:59)

The UniqueTypesCollector is badly broken. I'm very surprised this has even been working. PR coming up.

I got a bit distracted by other things, but I now have a working solution for this. To clarify the problem, it's this method in the UniqueTypesCollector:
https://github.com/SpoonLabs/sorald/blob/da98ae47970b13d1c43fa70603e9e55cc3778c8e/src/main/java/sorald/UniqueTypesCollector.java#L53-L70
This method is supposed to resolve a problem that occurs when multiple processors act on the same file A when running in CHANGED_ONLY output mode. In that case, the first processor will operate on A when it's in the original source directory, which is then printed to the intermediate spoon directory (a temporary workdir). The next processor will then operate on the copied version of A, but when collecting that type, there will be a duplicate entry of A in the original source directory and A in the intermediate directory unless the original entry is removed.
That's what this method is supposed to do, but it's pretty broken. The first problem is that it never actually checks if the input file is in the intermediate directory, in which case the regex built from filePath just becomes garbage. This can also cause an out-of-bounds exception if the original filePath is shorter than the intermediate directory name.
The second larger problem is that the filePath regex is shortened further for each iteration, both making it increasingly incorrect, and in the end resulting in an out-of-bounds exception. I'm very surprised this has worked as well as it has, because it's not at all correct.


More git 1

Hi i have added a few git commands

add a new remote
create a signed commit
create a branch from a specific commit
see difference between working directory and last commit
config username and email

Thank you for your code pieces!

Deployed and available here: https://onelinerhub.com/?q=git/


Combining observables

Currently i am trying to solve the following problem using RxCpp.

Assume we have an observable serving objects of A
For each served object trigger a task that returns an observable serving a single object of B and then completes.
Combine A and B and provide an observable that emits the result.

I am trying to figure out how to solve this the most elegant way. My first thought was to do it like this:

Use observable::create and pass a subscription (x)
Subscribe to observable
For each A trigger the task and subscribe to observable
Combine A and B and call x.onNext((A, B))

It feels like there should be a much simpler solution.
Does someone has a suggestions?

My understanding of your problem is this:
observable<A>()
.concat_map([](A a) {
   return Task<B>()
   .map([a](B b) {
      return std::make_pair(a,b);
   });
});

Is that close?

Hi @marcobusemann,
Thanks for asking!
@BenPope has a great solution.
Another resource is the code on this slide - part of this talk.
The code can be reduced to the following, which is similar to what @BenPope posted.
from("https://aka.ms/rxcppreadme", "https://aka.ms/rxcppreadme") | // A
flat_map([](string a) { // flat_map will do http requests at the same time, concat_map will not
  return httpGet(a) | // B
    map([a](response_t b) {
      return make_tuple(a, b);
    });
}) |
subscribe([](tuple<string, request_t>){
// code using a & b
});

Wow, thanks to both of you. That put me in the right direction and both solutions work like a charm.


cleanup conandata.yml before exporting

currently, barbarian export exports conandata.yml file "as-is", so it often contains information about several versions. This is sub-optimal because it means that a change in the information of any version X invalidates the hash of the exported version Y, even if if X != Y. I believe this is the reason why Conan-Center-Index cleans the conandata.yml files before exporting: it removes the information of all the versions which are not being exported.
On the cons side: this can only work if the layout of conandata.yml is fixed, and identical to what CCI uses.
EDIT: this is documented on https://github.com/conan-io/conan-center-index/blob/31441eddce7794b75949e05e6f64c2863c23aa4a/docs/error_knowledge_base.md#kb-h031-conandatayml-reduce, and is implemetend in a post-export hook: https://github.com/conan-io/hooks/blob/master/hooks/conan-center.py#L729-L749

Yes, there is. I edited my message with the info about the hook

Thanks for the quick turnaround !
Unfortunately I think it created a problem during barbarian export:
Traceback (most recent call last):
  File "/home/runner/.local/bin/barbarian", line 8, in <module>
    sys.exit(main())
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 728, in main
    Barbarian()
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 95, in __init__
    getattr(self, "command_"+self.args.command)(self.args)
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 376, in command_export
    self.recipe_data_dir = args
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 199, in recipe_data_dir
    self.recipe_name_and_version = args
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 171, in recipe_name_and_version
    recipe_props = self.conan_api.inspect(
  File "/home/runner/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 316, in conan_api
    copy(os.path.join(hooks_dir_src, name),
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
    with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: '/home/runner/work/conan-center-index/conan-center-index/.conan/hooks/barbarian_clean_conandata_yml.py'

https://github.com/ericLemanissier/conan-center-index/runs/4165143472?check_suite_focus=true#step:3:115
Should I remove the barbarian branch on my repo ?

I tried locally and it succeeded:
$ barbarian export recipes/qt/6.x.x qt/6.2.1@ericLemanissier/conan-center-index
[INFO] root_dir = /mnt/c/pf/conan-center-index
WARN: Remotes registry file missing, creating default one in /mnt/c/pf/conan-center-index/.conan/remotes.json
[INFO] Exporting to /mnt/c/pf/conan-center-index/.conan/data/qt/6.2.1/ericLemanissier/conan-center-index
Exporting package recipe
qt/6.2.1@ericLemanissier/conan-center-index exports: File 'conandata.yml' found. Exporting it...
qt/6.2.1@ericLemanissier/conan-center-index exports: Copied 1 '.yml' file: conandata.yml
qt/6.2.1@ericLemanissier/conan-center-index: Calling export()
qt/6.2.1@ericLemanissier/conan-center-index export() method: Copied 1 '.conf' file: qtmodules6.2.1.conf
qt/6.2.1@ericLemanissier/conan-center-index: Calling export_sources()
qt/6.2.1@ericLemanissier/conan-center-index export_sources() method: Copied 4 '.diff' files: 32451d5.diff, qt6-pri-helpers-fix.diff, c72097e.diff, 138a720.diff
qt/6.2.1@ericLemanissier/conan-center-index export_sources() method: Copied 3 '.patch' files: 5fe0b82.patch, dece6f5.patch, c76d2f6.patch
qt/6.2.1@ericLemanissier/conan-center-index: A new conanfile.py version was exported
qt/6.2.1@ericLemanissier/conan-center-index: Folder: /mnt/c/pf/conan-center-index/.conan/data/qt/6.2.1/ericLemanissier/conan-center-index/export
qt/6.2.1@ericLemanissier/conan-center-index: Using the exported files summary hash as the recipe revision: afe883e09a6238c88c7b77933c8acafd
qt/6.2.1@ericLemanissier/conan-center-index: Exported revision: afe883e09a6238c88c7b77933c8acafd

That said, I cannot find barbarian_clean_conandata_yml.py

Ignore my last message, I was actually using an older version of barbarian CLI.
I can reproduce the error:
$ barbarian export recipes/qt/6.x.x qt/6.2.1@ericLemanissier/conan-center-index
[INFO] root_dir = /mnt/c/pf/conan-center-index
WARN: Remotes registry file missing, creating default one in /mnt/c/pf/conan-center-index/.conan/remotes.json
Auto detecting your dev setup to initialize the default profile (/mnt/c/pf/conan-center-index/.conan/profiles/default)
Found gcc 9
gcc>=5, using the major as version

************************* WARNING: GCC OLD ABI COMPATIBILITY ***********************

Conan detected a GCC version > 5 but has adjusted the 'compiler.libcxx' setting to
'libstdc++' for backwards compatibility.
Your compiler is likely using the new CXX11 ABI by default (libstdc++11).

If you want Conan to use the new ABI for the default profile, run:

    $ conan profile update settings.compiler.libcxx=libstdc++11 default

Or edit '/mnt/c/pf/conan-center-index/.conan/profiles/default' and set compiler.libcxx=libstdc++11

************************************************************************************

Default settings
        os=Linux
        os_build=Linux
        arch=x86_64
        arch_build=x86_64
        compiler=gcc
        compiler.version=9
        compiler.libcxx=libstdc++
        build_type=Release
*** You can change them in /mnt/c/pf/conan-center-index/.conan/profiles/default ***
*** Or override with -s compiler='other' -s ...s***

Traceback (most recent call last):
  File "/home/eric/.local/bin/barbarian", line 8, in <module>
    sys.exit(main())
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 728, in main
    Barbarian()
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 95, in __init__
    getattr(self, "command_"+self.args.command)(self.args)
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 376, in command_export
    self.recipe_data_dir = args
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 199, in recipe_data_dir
    self.recipe_name_and_version = args
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 171, in recipe_name_and_version
    recipe_props = self.conan_api.inspect(
  File "/home/eric/.local/lib/python3.8/site-packages/barbarians/barbarian.py", line 316, in conan_api
    copy(os.path.join(hooks_dir_src, name),
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
    copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
    with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: '/mnt/c/pf/conan-center-index/.conan/hooks/barbarian_clean_conandata_yml.py'

The problem disappears by calling mkdir .conan/hooks before calling barbarian export. The solution is probably just to create the directory hooks_dir_dst in def conan_api(self)
On a side note, Why didn't you consider making barbarian CLI repo public ? the sources are available anyway once it is installed. It would help contributors help you.

I can confirm that https://github.com/ericLemanissier/barbarian-upload/commit/d4ce7dc52ef128eed1b459e8a9499b96460e1d3e works around the problem on CI too:  https://github.com/ericLemanissier/conan-center-index/runs/4168000584
That said I have an error during barbarian upload:
To https://github.com/ericLemanissier/conan-center-index
 ! [rejected]        barbarian -> barbarian (fetch first)
error: failed to push some refs to 'https://github.com/ericLemanissier/conan-center-index'
hint: Updates were rejected because the remote contains work that you do
hint: not have locally. This is usually caused by another repository pushing
hint: to the same ref. You may want to first integrate the remote changes
hint: (e.g., 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

The workaround:
https://github.com/ericLemanissier/barbarian-upload/blob/main/action.yml#L40
https://github.com/ericLemanissier/barbarian-upload/blob/main/action.yml#L44


Add git to cypress/base:ubuntu16 image

add git client tools, see https://github.com/cypress-io/cypress-test-ci-environments/issues/6

seems to be happy


Add Software Architecture

https://github.com/mehdihadeli/awesome-software-architecture
Some articles and resources to learn and practice about software architecture, patterns, and principles.
PR reviewed
4 pull requests I've reviewed: #1936 , #1931 , #1944, #1947, #2006
#1947(comment)
#1936(comment)
#1931(comment)
#1944 (comment)
#2006(comment)
By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ add Swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.
Must not feature Contributing or Footnotes sections.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=main&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name, text, or a Licence section to the readme. GitHub already shows the license name and link to the full text at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.
It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
The section should not appear in the Table of Contents.

All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Your list does not comply with:

Non-generated Markdown file in a GitHub repo.

Your list does not comply with:

Non-generated Markdown file in a GitHub repo.

Hi,
Thanks for review,
What is your mean about Non-generated Markdown?

in a GitHub repo.

Is the part I'm talking about. Awesome lists are meant to be a GitHub repo, not a website. Websites are allowed, but they should be secondary.

@sindresorhus Yes, you're right. but because I have so many links and their nesting section, managing them in a single root readme file was difficult so I moved them to a GitHub page for better navigation and searching capability. I saw a such thing in a pre existing awesome page github.com/ramitsurana/awesome-kubernetes so I did same thing

Closing for now.  If not, that's totally fine too. Not everything has to be listed here. All Awesome lists are searchable on GitHub.

@sindresorhus Could you open this issue again? I changed README file more like awesome list in one page, beside of this README, this repository has an official website


[Go live][Dec 09]

Push to live

Docs Build status updates of commit 1f02270:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/appsource/prepare/create-partner-center-dev-account.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/what-are-tabs.md
:white_check_mark:Succeeded
View

msteams-platform/toolkit/TeamsFx-collaboration.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


data-include and js-loading / js-calls

Hi,
again I need and would like to get a better understanding about the combination of data-include and javascript-initializings.
Example:
An index.html will load e.g. a jquery.js and a slider.js
After full load the page starts with rendering the first slider.
Below are some lazyloaded content areas, e.g.
div class="lazyload" data-include="content/file05.html" data-lazyqueue="05"  /div
File05.html contains as well a second slider, which is using the same slider.js / libraries + jquery.
As far as I understand the second slider will ONLY start if I put the jquery.js and the slider.js again on the file05.html.
It's like a complete new page, like an iframe.
Questions:
Is this a correct understanding?
Is there a way to avoid loading again (...and again) the same .js files?
Is there a way to create a "call-trough", so the already loaded js-file/function can be called or initialized from the later inview-loaded lazysize files?
My aim is to avoid long loading times during initializing of the page but as well later during the lasysize loadings.
To make it more clear: Let's say the slider.js has a function(forward), how I can call this function on the file05.html (if I don't want to load jqury.js and slider.js again)?
Thanks for clarifying :-)

Is this a correct understanding?

No.

Is there a way to avoid loading again (...and again) the same .js files?

Yes.
To be honest everything is explained in detail on the plugin page. In case this isn't clear it would be great, if you would help to improve the documentation.
I just updated the plunk: http://embed.plnkr.co/9G5Cb7/preview
On slide5 you will now see a magic button, that is initialized.
While there are multiple ways to do this (see documentation for lazyincluded event and documentation for special AMD/system Module features), here is an example using the lazyincludedevent:
(function(){
	'use strict';
	var init = function(context){
		//magic slider
		$('#fullpage', context).slider();

		//magic button
		$('button.alert', context)
			.css('textDecoration', 'underline')
			.on('click', function(){
				alert('yeah, this is dynamic');
			})
		;
	};

	$(function(){
		init(document);
		$(document).on('lazyincluded', function(e){
			init(e.target);
		});
	});
})();

Hi,
sorry for the delayed answer - busy week ;-)
And thanks for the answer - will check it ASAP.
Was reading already, but I am not doing js only...


ReadMe example fixed.

I think package name on require statement and 'new' keyword was missing.

Thank you!


ImportError: cannot import name 'RecoveryServicesBackupClient' from 'azure.mgmt.recoveryservicesbackup'

I have installed ansible in ubuntu so when i am running this task
- name: resource group
azure_rm_resourcegroup:
name: New_acr_demo
location: westus
tags:
environment: production
I end up with this error
The error was: ImportError: cannot import name 'RecoveryServicesBackupClient' from 'azure.mgmt.recoveryservicesbackup' (/usr/local/lib/python3.11/site-packages/azure/mgmt/recoveryservicesbackup/init.py)
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to import the required Python library (ansible[azure] (azure >= 2.0.0)) Python /usr/local/bin/python. Please read the module documentation and install it in the appropriate location. If the required library is installed, but Ansible is using the wrong Python interpreter, please consult the documentation on ansible_python_interpreter"}
I have tried importing these libraries
from azure.mgmt.recoveryservicesbackup.activestamp import RecoveryServicesBackupClient
import os
import azure.mgmt.recoveryservicesbackup.activestamp.models as RecoveryServicesBackupModels
but i am still getting this error.
Expected behavior
The issue should have been resolved.

Hi can anyone help me on this.

Thanks for the feedback, we’ll investigate asap.

I have run the same task on azure cloudshell following the Microsoft azure documentation and after installing the azure modules and python libraries I still end up with the same error.
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: cannot import name 'RecoveryServicesBackupClient' from 'azure.mgmt.recoveryservicesbackup' (/home/shashwat_sharma/.local/lib/python3.9/site-packages/azure/mgmt/recoveryservicesbackup/init.py)
fatal: [localhost]: FAILED! => {"changed": false, "msg": "Failed to import the required Python library (ansible[azure] (azure >= 2.0.0)) on  Python /usr/bin/python3.9. Please read the module documentation and install it in the appropriate location. If the required library is installed, but Ansible is using the wrong Python interpreter, please consult the documentation on ansible_python_interpreter"}

Hi, @Shashwat2712200
from azure.mgmt.recoveryservicesbackup import RecoveryServicesBackupClient should work with the latest release, please try reinstall the sdk: pip install azure.mgmt.recoveryservicesbackup==7.0.0.

I have checked the python interpreter it is working fine I am using these commands and then running the ansible-playbook:
pip3 install azure-mgmt-network azure-storage-blob azure-mgmt-automation azure-mgmt-core
pip3 install azure-identity azure-storage-blob msrestazurepip3 install azure-mgmt-recoveryservicesbackup==7.0.0 azure-mgmt-compute==30.3.0 azure-mgmt-resource==23.1.0b2 azure-mgmt-recoveryservices==2.5.0
git clone https://github.com/Azure-Samples/azure-samples-python-management.git
cd azure-samples-python-management/samples/recoveryservicesbackup
pip install -r requirements.txt
from azure.mgmt.recoveryservicesbackup.activestamp import RecoveryServicesBackupClient
from azure.mgmt.recoveryservicesbackup import RecoveryServicesBackupClient
import azure.mgmt.recoveryservicesbackup.activestamp.models as RecoveryServicesBackupModels
I end up with the same error mentioned above

@Shashwat2712200 That's where we addressed the issue, by installing sdk from the requirements.txt, you have reinstalled the azure-mgmt-recoveryservicesbackup with an older version 5.0.0. So I guess what you need to do is to just skip the step pip install -r requirements.txt or manually update this file to make sure it uses the latest sdk.

/unresolve

I have tried this too pip install azure-mgmt-recoveryservicesbackup==7.0.0 and skipped the pip install -r requirements.txt.
then i end up with this error.
The error was: ModuleNotFoundError: No module named 'azure.mgmt.recoveryservicesbackup.models'
I have taken every approach provided on the Internet by using commands.
Can you look into it

import azure.mgmt.recoveryservicesbackup.models is incorrect, if there's such code in your sample, try update it to import azure.mgmt.recoveryservicesbackup.activestamp.models.

I have tried this but i end up with the same error.

Hi @Shashwat2712200 The code from ansible plugins might be the root of error https://github.com/ansible-collections/azure/blob/dev/plugins/module_utils/azure_rm_common.py#L252, and I noticed that the developer of ansible recommends using azure-mgmt-recoveryservicesbackup==3.0.0, you may need reinstall it with version 3.0.0 to get the fully support. If there're still conflicts, I'm afraid it will be necessary to manually modify the ansible plugin files.


Silent failure when IAM permissions missing

Since the current CloudFormation config has overly broad permissions (#579), I configured my Empire controller to use an IAM user role with no access rights as a test. My plan was to run emp commands that I expected to fail with PermissionDenied errors, open up the role, and iterate until everything works.
However, Empire is failing silently:
$ emp deploy remind101/acme-inc:latest
...
Status: Image is up to date for remind101/acme-inc:latest

$ emp ps -a acme-inc
<blank output>

$ emp scale -a acme-inc web=2
error: ServiceNotFoundException: Service not found.
	status code: 400, request id: []

No service or load balancer is created on AWS, but as far as Empire is concerned, the request completed successfully.
Some endpoints did error successfully. I needed to add ecs:ListServices to get this far. Why is service creation failing silently?

Are you checking the logs of the empire daemon?  If it isn't loud enough, you should also try running the Empire daemon with EMPIRE_AWS_DEBUG set.
If you'd like to see somewhat tighter policies, you could also checkout the stacker blueprint policies:
https://github.com/remind101/stacker/blob/master/stacker/blueprints/empire/policies.py

Yep, just discovered and enabled EMPIRE_AWS_DEBUG. I now have some evidence of the failures:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 403 Forbidden
Content-Length: 386
Content-Type: text/xml
Date: Fri, 31 Jul 2015 02:41:25 GMT
X-Amzn-Requestid: a36131b3-372d-11e5-98b0-5363c1742e73

This is better, but the failed request IDs aren't displayed on CloudTrail - I'm looking into that to see if I need to add some additional config on the AWS side.
However, the fact that Empire is showing success when AWS is clearly returning 40x failures for the API calls seems like a Big Deal. Can you confirm that you're seeing the same behavior on your end by intentionally restricting Empire on a test cluster?

Hmm - I may not be able to get to it tonight, but how are you defining 'showing success'?  The deploy command successfully pulling down the image you mean and not throwing an error?

@phobologic As far as I know, the deploy command should a) download the image, b) create a task definition, c) create a service from that definition, and d) create a load balancer for the service.
When using an underprivileged user, only a) succeeds. The rest of the steps are failing silently - you only see the failed API requests with EMPIRE_AWS_DEBUG enabled.
If any of Empire's AWS API requests fail, the failure should be shown to the user instead of swallowed.

I worked my way forward by inspecting the controller's logs with EMPIRE_AWS_DEBUG enabled. However, after adding a good chunk of permissions, I'm now blocked at:
t=2015-08-02T20:39:20+0000 lvl=info msg=CreateService request_id=... trace.id=... trace.parent= trace.func=github.com/remind101/empire/pkg/ecsutil.(*ecsClient).CreateService trace.file=/go/src/github.com/remind101/empire/pkg/ecsutil/ecs.go trace.line=50 trace.duration=82.980599ms service-name=... desired-count=1 task-definition=...

t=2015-08-02T20:39:20+0000 lvl=eror msg= request_id=... error="\"InvalidParameterException: Unable to assume role and validate the listeners configured on your load balancer.  Please verify the role being passed has the proper permissions.\n\tstatus code: 400, request id: []\"" line=52 file=/go/src/github.com/remind101/empire/pkg/ecsutil/ecs.go

As a sanity check, I opened my permissions back up to:
ec2:*
ecs:*
elasticloadbalancing:*
iam:*
route53*

Even wide open like this, the controller throws the error above. Unfortunately, it doesn't show which role it's trying to assume, so I'm not sure what's broken. My instance and service roles are configured per the ECS docs, but it's not clear why Empire would need to access either of these roles directly.

I'm actually working on (today) having emp get better output when you fail at an emp deploy today due to permissions.
You are running this via DEMOMODE=0 bin/bootstrap right?  If so, in your .env you'll have a line like this: EMPIRE_ECS_SERVICE_ROLE=
Does your controller have the ability to assume the role that is listed there?  Does that role exist?  Does it have the policy defined here?
http://docs.aws.amazon.com/AmazonECS/latest/developerguide/service_IAM_role.html
Here's another example of how that is defined: https://github.com/remind101/stacker/blob/4530c00b472d5deab4ca42e1dd8da89dfdb7d2a5/stacker/blueprints/empire/policies.py#L27

@phobologic I'll try your emp deploy changes as soon as they're pushed!
I'm running Empire via a custom setup on Terraform, but it's heavily influenced by your CF template. My controller is still running as an ECS service behind an ELB. The controller's IAM user policy has iam:* (temporarily), so it should be able to assume the service role, which has the policy you linked to.

Does your ECS service have the following environment variable set?
                "Name": "EMPIRE_ECS_SERVICE_ROLE",
                "Value": { "Ref": "ServiceRole" }

Also - make sure that it is pointing at a Role that has the right assumerole policy and the right policy document with all the permissions it needs:
    "ServiceRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "Path": "/",
        "AssumeRolePolicyDocument": {
          "Version": "2008-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Principal": {
                "Service": [ "ecs.amazonaws.com" ]
              },
              "Action": [ "sts:AssumeRole" ]
            }
          ]
        }
      }
    },

    "ServiceRolePolicies": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyName": "ecsServiceRole",
        "Roles": [ { "Ref": "ServiceRole" } ],
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "ec2:Describe*",
                "elasticloadbalancing:*",
                "ecs:*",
                "iam:ListInstanceProfiles",
                "iam:ListRoles",
                "iam:PassRole",
                "route53:*"
              ],
              "Resource": [
                "*"
              ]
            }
          ]
        }
      }
    },

Finally, you should make sure that the instance itself has an InstanceProfile with a Role & Policy that allows it to do the following:
    "InstanceRole": {
      "Type": "AWS::IAM::Role",
      "Properties": {
        "Path": "/",
        "AssumeRolePolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Principal": {
                "Service": [ "ec2.amazonaws.com" ]
              },
              "Action": [ "sts:AssumeRole" ]
            }
          ]
        }
      }
    },

    "InstancePolicies": {
      "Type": "AWS::IAM::Policy",
      "Properties": {
        "PolicyName": "ecs",
        "Roles": [ { "Ref": "InstanceRole" } ],
        "Users": [ { "Ref": "User" } ],
        "PolicyDocument": {
          "Version": "2012-10-17",
          "Statement": [
            {
              "Effect": "Allow",
              "Action": [
                "ec2:Describe*",
                "elasticloadbalancing:*",
                "ecs:*",
                "iam:ListInstanceProfiles",
                "iam:ListRoles",
                "iam:PassRole",
                "iam:UploadServerCertificate",
                "iam:DeleteServerCertificate",
                "route53:*"
              ],
              "Resource": [
                "*"
              ]
            }
          ]
        }
      }

My guess is that there is an issue with your InstanceRole/Profile/Policy - or that you're pointing at the wrong role when it tries to assume role.

Arg, looks like EMPIRE_ECS_SERVICE_ROLE can only be the role name - both ARN and unique ID will fail with an "Unable to assume role" exception.
Worth documenting somewhere if possible.


temperature extrema for this day as entity

Hi,
i need the temperature extrema for this day as entity for some automations in HA.

Hi, please see https://github.com/FL550/dwd_weather/wiki#how-to-get-daily-maxmin-values

THX <3 @FL550

Does not work:
template:

trigger:

platform: time
at: "00:02:00"
platform: homeassistant
event: start
platform: event
event_type: event_template_reloaded
action:

service: weather.get_forecasts
data:
type: daily
target:
entity_id: [[weather.bornheim_eichenkamp]]
response_variable: weather_data
sensor:
name: "Bornheim Eichenkamp: Max Temp Heute"
unique_id: bornheim_eichenkamp_max_temp_today
state: >-
{{ weather_data['[[weather.bornheim_eichenkamp]]'].forecast[0].temperature }}
unit_of_measurement: "°C"
name: "Bornheim Eichenkamp: Min Temp Heute"
unique_id: bornheim_eichenkamp_min_temp_today
state: >-
{{ weather_data['[[weather.bornheim_eichenkamp]]'].forecast[0].templow }}
unit_of_measurement: "°C"


Extension with  "authentication": "UserPassword"

how to set username and password in VS code for extension with  "authentication": "UserPassword"

You will be prompted when trying to communicate with the server.
Note that it is not the extension itself that specifies the authentication method but rather a specific server connection in launch.json.


Make sure pachctl fork-commit documentation is clear enough

This came up in https://github.com/pachyderm/pachyderm/pull/964
It was unclear at the time what the difference between fork and branch were. I couldn't resolve it in the CL because I don't myself know the difference (I was just regenerating the docs) but we should make sure it's clear to users.

fork-commit is branching.  What's unclear about the current documentation?

Not in the API anymore, correct?  Closing.


Requests running in timeout at really large jobs

We recently discovered a problem with a very large job. It is a job with a runtime of >31h on 24 nodes and 96GPUs.
We broke this down to the point that, when retrieving the metrics from the metricstore, timeouts occur at various points. On the one hand in the http client in the cc-backend (default 10s), on the other hand in the cc-metric-store server (30s). This results in incomplete data records.
The trivial solution would certainly be to increase the default timeouts. Alternatively, data compression could be considered to reduce the transmission time.

Similar errors also occur, when loading multiple job pages in parallel (e.g. opening a list of "concurrent jobs" in new tabs). They all run into 502 errors. When reloading the pages sequentially they work. It seems, the parallel load on the server slows down the individual requests.
Therefore, the effect not only occurs with singular very large jobs, but also with multiple jobs loaded in parallel. The difference being, that the pages for "normal" jobs can be successfully reloaded sequentially, while the page for the large job will always fail.

Du you run cc-metric-store on the same host as cc-backend? Does the job show up correctly if completed and loaded from the job archive?

Yes, metric collector and backend are running on the same machine. I will check the second question when the job has finished. Actually it's still running.

Added to current draft merge request due to included optimizations for data loading (resampling / sqlite index rework)


turn on SQLAlchemy 2.0 deprecation warnings

via env var in both docker-compose files
via env var in test.yml CI config

closes sul-dlss/libsys-airflow#467

per standup discussion, i also added this to the prod docker compose config, see #528.
per the suggestion for the airflow project itself in the airflow ticket linked from this PR's issue, i also added the env var to our CI test config.


Haitao/with retry

implement retry for steps in a job.

Codecov Report

Merging #6 (aba8df0) into main (878c42a) will decrease coverage by 0.01%.
The diff coverage is 75.38%.

@@            Coverage Diff             @@
##             main       #6      +/-   ##
==========================================
- Coverage   78.65%   78.64%   -0.02%
==========================================
  Files           5        7       +2
  Lines         342      398      +56
==========================================
+ Hits          269      313      +44
- Misses         55       66      +11
- Partials       18       19       +1

Impacted Files
Coverage Δ

step.go
93.54% <ø> (-0.90%)
:arrow_down:

step_exec_options.go
50.00% <50.00%> (ø)

job.go
77.62% <76.92%> (+1.60%)
:arrow_up:

graph_node.go
90.47% <100.00%> (ø)

retryer.go
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


From where can I get Google phishlet for evilginx2 plz

You can reach how to the developer on icq @mrgretzky

You can reach how to the developer on icq @mrgretzky

You are a scammer using kgretzky i.d to scamm people for phishlets guys beware of him

yes ,you can contact me  rickyrik at protonmail.com


Add Support for Reading KubeVirt Infra Namespace in Cloud Provider Spec

What this PR does / why we need it:
Adding support for passing the underlying KubeVirt infra namespace where KubeVirt resources are going to be created in the infra cluster.
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?
/kind feature

Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

Add `.cloudProvider.kubevirt.infraNamespace` field to the KubeOneCluster API used to control what namespace will be used by the KubeVirt provider to create and manage resources in the infra cluster, such as VirtualMachines and VirtualMachineInstances

Documentation:

None

/approve
/lgtm

/release-note-edit
Add `.cloudProvider.kubevirt.infraNamespace` field to the KubeOneCluster API used to control what namespace will be used by the KubeVirt provider to create and manage resources in the infra cluster, such as VirtualMachines and VirtualMachineInstances

/cherrypick release/v1.9


Primary contact on travel should be able to delete DocuSign envelopes

May actually want an action for this idk

Also allow envelope sender to delete


DELETE not working

Trying to delete an item from my repo : https://my-json-server.typicode.com/yeasin90/my-json-db-server/users/2
Getting 200, but nothing is getting deleted.

Just got to know remote version does not modify data, it only fetches data. Used dockerized clue/docker-json-server instead, and served my purpose :) . Closing this issue.


Transferring nextSteps.md

Transferring the nextSteps.md from Dan's repo to link at the end of the E2E readme examples.

#sign-off


[BUG]

Before you begin

This is NOT Forlax's mod or any other mod. If you have issues related to those versions DO NOT post them here as they will be closed and disregarded immediately.
Do NOT post any form of illegal content (e.g. screenshots of you cracking a website with stolen credentials) and do NOT ask for Configs for websites. Doing that will result in a report to the GitHub security team and a permanent ban from posting to this repository.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Version

Version [e.g. 1.0.1]

Additional context
Add any other context about the problem here.
idk what category to put this under, but I don't see an option to parse a cookie as a var anymore....
very confusing

SORRY IDIOT ALERT KEK

Please don't make issues for this dumb stuff, use the forum. Thanks...
https://forum.openbullet.dev/topic/4/how-to-parse-cookies-headers


Added docs for supported flags in JFrog

Harness Developer Pull Request
Added docs for supported flags for JFrog Artifactory
What Type of PR is This?

[ ] Issue
[X] Feature
[ ] Maintenance/Chore

House Keeping

[X] Tested Locally
[X] Optional Screenshot.

Refer the below screenshot:-

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d61703887506c5edd42382--harness-developer.netlify.app

@shiv-am0 Is it possible to set these flags as stage variables when using the built-in step. Eg. PLUGIN_BUILD_NUMBER?

Yes. These settings can be passed as variables in the built-in step as PLUGIN_BUILD_NUMBER and PLUGIN_BUILD_NAME.

@shiv-am0 I reorganized the topic a bit but I kept the info you added. I'll merge it after the build passes.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65d79264cf8796264ee21218--harness-developer.netlify.app


Fine granular AWS IAM Policy for Ark

Describe the solution you'd like
The documentation provides an AWS policy where bucket permissions are limited to 1 bucket. However, snapshot and volume actions allow ark to operate on any volume and snapshot in the given AWS account. We should be able to limit the resources that Ark would like to operate on using tags. For example, it should only be able to create/describe/delete snapshots and volumes if an X label exists in the resource tags.
I am creating many kubernetes clusters in the same account from a central cluster. If it was possible to run ark server on that orchestrator cluster, I could give all the access. However, I don't want an AWS IAM user that can operate on others' resources to exist in customer cluster.
Environment:

Velero version (use velero version): 0.1.11
Kubernetes version (use kubectl version): 1.11
Cloud provider or hardware configuration: AWS

@bymafmaf this is a great idea. We do already attach a couple of tags to snapshots, and they get copied to the volume on a restore - would that be sufficient? (I'm not super-familiar with tag-based IAM policies).  The standard tags are velero.io/backup which has the backup name, and velero.io/pv which has the PV name


<EMAIL_ADDRESS>

Bunch of releases have happened in node-pty, should pull in all that good stuff :smile: https://github.com/Tyriar/node-pty/releases

Great! Any idea why tests might be failing though?
https://travis-ci.org/sourcelair/xterm.js/jobs/211531244

It's happening because it was relying on a private API, I'll fix this up when I get a chance.

I'll close this off since I just released a new version. Didn't fix this particular thing though.


Normalize advice provider instructions

Instructions which deal with the advice provider are not very well organized right now. They evolved together with the advice provider which went though several design iterations. It would be great to re-organize them to make sure (1) there is some consistency in naming etc. and (2) we have a way to add many more such instructions (which we will need) without running out of the 256 instruction maximum. Currently, we have 3 broad groups of instructions which interact with the advice provider:

Group 1:  instructions which move data from the advice stack onto the operand stack: adv_push.n, adv_loadw, and adv_pipe (this one also writes data to memory).
Group 2: instructions which push data onto the advice stack: adv.keyval, adv.u64div, adv.ext2inv, adv.ext2intt, adv.smtget, adv.smtinsert.
Group 3: instructions which insert data into the advice map: adv.mem.

The first group will likely remain relatively stable. The second group will likely keep growing as we add more functionality to the VM (e.g., for non-deterministic signature generation). The third group needs to be a bit more robust (i.e., being able to insert values from the stack - not just memory), but once we define the basic set, it'll probably remain stable over time.
There are many options for how we can choose to refactor these instructions. Here are a couple of them:
Option 1
We could make the instructions more explicit in terms of which part of the advice provider they affect and how. For example, we could have adv_stack.<action> and adv_map.<action> format, and then express all of the above instructions as follows:

Group 1: adv_stack.pop.n, adv_stack.popw, adv_stack.pipe.
Group 2: adv_stack.push.keyval, adv_stack.push.u64div, adv_stack.push.ext2inv etc.
Group 3: adv_map.set.mem. This could be extended to include adv_map.append.x. Also, we could replace adv_stack.push.keyval with adv_map.get which could be a more intuitive way to describe "get value from advice map and put it onto advice stack"

Overall, we get 2 high-level instructions adv_stack and adv_map which are parametrized further to define may sub-instructions. This gives us a lot of flexibility to introduce additional sub-instructions.
One thing that I don't entirely love is that for group 1 instructions it is not really clear what that adv_stack.pop.n and adv_stack.popw actually work differently with the operand stack (i.e., adv_stack.pop.n pushes n values from the advice stack onto the operand stack, while adv_stack.popw overwrites top 4 values on the operand stack with the values popped from the advice stack).
Option 2
We could keep group 1 instructions as they are now (this way that'd be more consistent with mem_load, loc_load etc.) and use "verb-based" instructions for the rest (.e.g, `adv_.

Group 1: remains as adv_push.n, adv_loadw, and adv_pipe
Group 2: adv_inject.keyval, adv.inject.u64div etc.
Group 3: adv_set.mem and in the future adv_append.mem

The downsides of this approach are:

We have more distinct top-level instructions (5 or 6 vs. 2 in the previous option).
The choice of verbs for groups 2 and 3 is somewhat arbitrary (i.e., why "inject" vs. "set").
It is not immediately clear which part of the advice provider is affected.

Related issues: #880, https://github.com/0xPolygonMiden/miden-vm/pull/844#issuecomment-1506016096, #835, #800, #674, #673.

One important distinction that I didn't mention above is that group 1 instructions are actually real operation (i.e., they affect the VM state outside of the advice provider) while group 2 and 3 instructions are just decorators (i.e., they affect the state of the advice provider only). Thus, it may make sense to keep group 1 separate from the other two.
So, maybe option 3 could look as follows:

Group 1, same as now: adv_push.n, adv_loadw, and adv_pipe.
Group 2, instructions which put the data onto the advice stack: adv_stack.push_mapval, adv_stack.push_u64div etc.
Group 3, instructions which put the data into the advice map: adv_map.insert_mem.

Closed by #933 and #944.


Hanging on "Waiting for machine-controller to come up"

Installation hangs every time on "Waiting for machine-controller to come up".
KubeOne version: 1.18.1 (installed on a RHEL 8 host)
Image: Rocky Linux 8.10
Provider: Openstack
Control plane VM flavor: 2C-4GB-50GB
Worker VM flavor: 4C-8GB-50GB
If I instead use an older CentOS 7 image then installation will succeed on the second attempt but never the first time (need to abort the first attempt, then run kubeone reset, then try kubeone apply again). When using the Rocky Linux image the installation hangs on "Waiting for machine-controller to come up" every time.
INFO[09:27:13 CEST] Determine hostname...
INFO[09:27:13 CEST] Determine operating system...
INFO[09:27:13 CEST] Running host probes...
INFO[09:27:14 CEST] Installing prerequisites...
INFO[09:27:14 CEST] Creating environment file...                  node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Creating environment file...                  node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Creating environment file...                  node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Configuring proxy...                          node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Installing kubeadm...                         node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Configuring proxy...                          node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Installing kubeadm...                         node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Configuring proxy...                          node=<IP_ADDRESS> os=rockylinux
INFO[09:27:14 CEST] Installing kubeadm...                         node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Creating environment file...                  node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Creating environment file...                  node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Configuring proxy...                          node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Installing kubeadm...                         node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Configuring proxy...                          node=<IP_ADDRESS> os=rockylinux
INFO[09:27:39 CEST] Installing kubeadm...                         node=<IP_ADDRESS> os=rockylinux
INFO[09:28:03 CEST] Generating kubeadm config file...
INFO[09:28:03 CEST] Determining Kubernetes pause image...
INFO[09:28:06 CEST] Uploading config files...                     node=<IP_ADDRESS>
INFO[09:28:06 CEST] Uploading config files...                     node=<IP_ADDRESS>
INFO[09:28:06 CEST] Uploading config files...                     node=<IP_ADDRESS>
INFO[09:28:08 CEST] Uploading config files...                     node=<IP_ADDRESS>
INFO[09:28:08 CEST] Uploading config files...                     node=<IP_ADDRESS>
INFO[09:28:10 CEST] Running kubeadm preflight checks...

INFO[09:28:13 CEST] Ensuring Certificates...                      node=<IP_ADDRESS>
INFO[09:28:16 CEST] Downloading PKI...
INFO[09:28:17 CEST] Creating local backup...                      node=<IP_ADDRESS>
INFO[09:28:17 CEST] Uploading PKI...
INFO[09:28:19 CEST] Configuring certs and etcd on consecutive control plane node...
INFO[09:28:19 CEST] Ensuring Certificates...                      node=<IP_ADDRESS>
INFO[09:28:19 CEST] Ensuring Certificates...                      node=<IP_ADDRESS>
INFO[09:28:21 CEST] Initializing Kubernetes on leader...
INFO[09:28:21 CEST] Running kubeadm...                            node=<IP_ADDRESS>
INFO[09:28:31 CEST] Building Kubernetes clientset...
INFO[09:28:31 CEST] Waiting 20s for CSRs to approve...            node=<IP_ADDRESS>
INFO[09:28:51 CEST] Approve pending CSR "csr-6g8h9" for username "system:node:cnf-test1-cp-0"  node=<IP_ADDRESS>
INFO[09:28:51 CEST] Approve pending CSR "csr-pqpdp" for username "system:node:cnf-test1-cp-0"  node=<IP_ADDRESS>
INFO[09:28:51 CEST] Check if cluster needs any repairs...
INFO[09:28:52 CEST] Joining controlplane node...
INFO[09:28:52 CEST] Waiting 15s to ensure main control plane components are up...  node=<IP_ADDRESS>
INFO[09:29:07 CEST] Joining control plane node                    node=<IP_ADDRESS>
INFO[09:29:14 CEST] Waiting 20s for CSRs to approve...            node=<IP_ADDRESS>
INFO[09:29:34 CEST] Approve pending CSR "csr-gfhwb" for username "system:node:cnf-test1-cp-1"  node=<IP_ADDRESS>
INFO[09:29:34 CEST] Waiting 15s to ensure main control plane components are up...  node=<IP_ADDRESS>
INFO[09:29:49 CEST] Joining control plane node                    node=<IP_ADDRESS>
INFO[09:29:56 CEST] Waiting 20s for CSRs to approve...            node=<IP_ADDRESS>
INFO[09:30:16 CEST] Approve pending CSR "csr-q8cf5" for username "system:node:cnf-test1-cp-2"  node=<IP_ADDRESS>
INFO[09:30:16 CEST] Restarting unhealthy API servers if needed...
INFO[09:30:17 CEST] Determining Kubernetes pause image...
INFO[09:30:17 CEST] Patching static pods...
INFO[09:30:17 CEST] Patching static pods...
INFO[09:30:17 CEST] Patching static pods...
INFO[09:30:18 CEST] Downloading kubeconfig...
INFO[09:30:18 CEST] Downloading PKI...
INFO[09:30:19 CEST] Creating local backup...                      node=<IP_ADDRESS>
INFO[09:30:19 CEST] Activating additional features...
INFO[09:30:19 CEST] Patching CoreDNS...
INFO[09:30:19 CEST] Creating machine-controller credentials secret...
INFO[09:30:19 CEST] Creating CCM credentials secret...
INFO[09:30:19 CEST] Applying addon coredns-pdb...
INFO[09:30:22 CEST] Applying addon metrics-server...
INFO[09:30:24 CEST] Applying addon nodelocaldns...
INFO[09:30:28 CEST] Applying addon machinecontroller...
INFO[09:30:38 CEST] Applying addon operating-system-manager...
INFO[09:30:50 CEST] Applying addon csi-openstack-cinder...
INFO[09:30:53 CEST] Applying addon csi-external-snapshotter...
INFO[09:30:57 CEST] Applying addon ccm-openstack...
INFO[09:31:00 CEST] Applying user provided addons...
INFO[09:31:00 CEST] Applying addons from the root directory...
INFO[09:31:00 CEST] Applying addon ...
INFO[09:31:04 CEST] Waiting for nodes to initialize by CCM...
INFO[09:32:24 CEST] Joining worker node                           node=<IP_ADDRESS>
INFO[09:32:24 CEST] Joining worker node                           node=<IP_ADDRESS>
INFO[09:32:26 CEST] Waiting 20s for CSRs to approve...            node=<IP_ADDRESS>
INFO[09:32:26 CEST] Waiting 20s for CSRs to approve...            node=<IP_ADDRESS>
INFO[09:32:46 CEST] Approve pending CSR "csr-rpvcl" for username "system:node:cnf-test1-sw-0"  node=<IP_ADDRESS>
INFO[09:32:46 CEST] Approve pending CSR "csr-hvm2c" for username "system:node:cnf-test1-sw-1"  node=<IP_ADDRESS>
INFO[09:32:46 CEST] Labeling nodes...
INFO[09:32:46 CEST] Fixing permissions of the kubernetes system files...
INFO[09:32:49 CEST] Waiting for machine-controller to come up...
WARN[09:35:49 CEST] Task failed, error was: kubernetes: waiting for machine-controller webhook to became ready
context deadline exceeded
WARN[09:35:59 CEST] Retrying task...
WARN[09:35:59 CEST] Retrying task...
INFO[09:35:59 CEST] Waiting for machine-controller to come up...
WARN[09:38:59 CEST] Task failed, error was: kubernetes: waiting for machine-controller webhook to became ready
context deadline exceeded
WARN[09:39:13 CEST] Retrying task...
INFO[09:39:13 CEST] Waiting for machine-controller to come up...
WARN[09:42:13 CEST] Task failed, error was: kubernetes: waiting for machine-controller webhook to became ready
context deadline exceeded
WARN[09:42:33 CEST] Retrying task...
INFO[09:42:33 CEST] Waiting for machine-controller to come up...
WARN[09:45:33 CEST] Task failed, error was: kubernetes: waiting for machine-controller webhook to became ready
context deadline exceeded

$ kubeone status -m control-plane.yaml -t cluster1.infra.json -c credentials-cluster1.yaml
INFO[12:28:39 CEST] Determine hostname...
INFO[12:28:39 CEST] Determine operating system...
INFO[12:28:40 CEST] Building Kubernetes clientset...
INFO[12:28:40 CEST] Verifying that nodes in the cluster match nodes defined in the manifest...
INFO[12:28:40 CEST] Verifying that all nodes in the cluster are ready...
INFO[12:28:40 CEST] Verifying that there is no upgrade in progress...
NODE                    VERSION   APISERVER   ETCD
cnf-test1-cp-0   v1.29.4   healthy     healthy
cnf-test1-cp-1   v1.29.4   healthy     healthy
cnf-test1-cp-2   v1.29.4   healthy     healthy

$ kubectl get nodes -o wide
NAME                    STATUS   ROLES           AGE     VERSION   INTERNAL-IP     EXTERNAL-IP   OS-IMAGE                            KERNEL-VERSION             CONTAINER-RUNTIME
cnf-test1-cp-0   Ready    control-plane   9m49s   v1.29.4   <IP_ADDRESS>   <none>        Rocky Linux 8.10 (Green Obsidian)   4.18.0-553.el8_10.x86_64   containerd://1.6.32
cnf-test1-cp-1   Ready    control-plane   9m7s    v1.29.4   <IP_ADDRESS>   <none>        Rocky Linux 8.10 (Green Obsidian)   4.18.0-553.el8_10.x86_64   containerd://1.6.32
cnf-test1-cp-2   Ready    control-plane   8m24s   v1.29.4   <IP_ADDRESS>   <none>        Rocky Linux 8.10 (Green Obsidian)   4.18.0-553.el8_10.x86_64   containerd://1.6.32
cnf-test1-sw-0   Ready    <none>          5m24s   v1.29.4   <IP_ADDRESS>   <none>        Rocky Linux 8.10 (Green Obsidian)   4.18.0-553.el8_10.x86_64   containerd://1.6.32
cnf-test1-sw-1   Ready    <none>          5m24s   v1.29.4   <IP_ADDRESS>   <none>        Rocky Linux 8.10 (Green Obsidian)   4.18.0-553.el8_10.x86_64   containerd://1.6.32

$ kubectl  apply -f workers-cluster1.yaml
Error from server (InternalError): error when creating "workers-cluster1.yaml": Internal error occurred: failed calling webhook "machinedeployments.machine-controller.kubermatic.io": failed to call webhook: Post "https://machine-controller-webhook.kube-system.svc:443/machinedeployments?timeout=10s": dial tcp <IP_ADDRESS>:443: connect: connection refused

I tried with doubling CPU and RAM on my VMs but made no change. Still hanging forever on "Waiting for machine-controller to come up...".

Hi,
I found the problem, it had nothing to do with Kubeone but with Calico.
2024-07-05 11:00:53.692 [WARNING][9] startup/autodetection_methods.go 113: Unable to auto-detect an IPv4 address using interface regexes [eth0]: no valid host interfaces found
2024-07-05 11:00:53.692 [WARNING][9] startup/startup.go 507: Couldn't autodetect an IPv4 address. If auto-detecting, choose a different autodetection method. Otherwise provide an explicit address.
2024-07-05 11:00:53.692 [INFO][9] startup/startup.go 391: Clearing out-of-date IPv4 address from this node IP=""
2024-07-05 11:00:53.698 [WARNING][9] startup/utils.go 48: Terminating
Calico node failed to start

After I corrected the Calico configuration and reset the cluster, apply finished without errors.
Best regards,
Andreas

Thanks for reporting back!
/close


Windows support

gtk handles Windows platform for a while now. Any project to add Windows support of SolidOak ? :)

I finally updated gtk today so I'll try this out once I get access to a Windows machine.

\o/

加油！

Windows supported

I'll help you.

@oakes I'm using Windows. Maybe I can build it for you.

I have finally updated my deps to the latest version of gtk-rs! I also made neovim-rs build on windows. The last remaining issue is that MSYS2 does not seem to have a vte package. I've tried to build it manually but have failed so far. If anyone can help, I'd appreciate it!

cc @antoyo

I don't have Windows, so I cannot help you.

Is there any Kind of Progress? I couldnt help too! But i could try to build it on Windows 10!?


build failed with Vulkan_GLSLANG_VALIDATOR_EXECUTABLE-NOTFOUND

I got the build failed log as bellow:
[ 40%] Compiling vertex shader
/bin/sh: 1: Vulkan_GLSLANG_VALIDATOR_EXECUTABLE-NOTFOUND: not found
gmake[2]: *** [HIP-Basic/vulkan_interop/CMakeFiles/shaders.dir/build.make:78: HIP-Basic/vulkan_interop/sinewave.vert.spv.h] Error 127
gmake[1]: *** [CMakeFiles/Makefile2:2697: HIP-Basic/vulkan_interop/CMakeFiles/shaders.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
(base) amd@AIG-PM:~/Gits/rocm-examples$
How to fix it?

I assume the above fixed it. Please reopen if there's still a problem.


Starttime on cosmos diagnostics not moving with retries

Describe the bug
Start Time on retry remains the same in responseStaticsList
Version - 4.39.0
Screenshots

@aayush3011 please take a look at this, thanks!

@rinatmini pls take a look at this, thanks!

Fixed in #35705


Allow null return in before change handler

I have a need to block certain values from being entered into cells. To achieve this, I've made a small change to use null as the value if it is returned from the onbeforechange function.

you must return an empty string "" not a null or undefined. Otherwise other users that won't use this method will have problems.


[BUG] 1.1.1 - 1.1.2 upgrade (before 1.2.x upgrade)

Describe the bug

We just closed out our Fall semester and went to upgrade to 1.2.x. To do so we need to upgrade
1.1.1 to 1.1.2
1.1.2 to 1.2.x
Unfortunately upon initating the upgrade get an error in the logs stating that elemental isn't availble in registry.opensuse.org
Dec 18 13:35:05 <IP_ADDRESS> 2023-11-04T02: 38:55+00:00#011rke2#011{"level":"E","thread_id":"2581","filename":"pod_workers.go","linenumber":"965","message":""Error syncing pod, skipping" err="failed to \"StartContainer\" for \"runner\" with ImagePullBackOff: \"Back-off pulling image \\\"registry.opensuse.org/isv/rancher/elemental/stable/teal53/15.4/rancher/elemental-teal-channel/5.3:latest\\\"\"" pod="fleet-default/elemental-teal-channel" podUID=bb7fe3c1-1e25-43ef-9248-3744af7c55c4"}
Any recommendations or alternative registries we should use?
To Reproduce
Steps to reproduce the behavior:

Start 1.1.1 -> 1.1.2 upgrade via the gui

Expected behavior

A successful upgrade to 1.1.2
Support bundle

This is on the way
Environment

Harvester ISO version:
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):
15 Baremetal Dell R6000 AMD nodes

Additional context
Add any other context about the problem here.

@Sepiidae Can you share which file contains the log? The image is not used by Harvester.

@Sepiidae Can you share which file contains the log? The image is not used by Harvester.

The log line is received via log shipping to our syslog server. I am not sure which file on the harvester servers contains this line. I am going to run a grep to search.

Ok, we went down the wrong rabbit hole. This error message was not related to the upgrade. It appears we are stuck with prometheus being stuck during its upgrade. I am following a few other threads which walk through the fix. If we get stuck I'll post another issue.
As aways thank you for this community.


L9 Support

Trying to install on L9 and get:
Problem 1
- Root composer.json requires lykegenes/laravel-countries ^2.0 -> satisfiable by lykegenes/laravel-countries[2.0.0].
- lykegenes/laravel-countries 2.0.0 requires illuminate/support ^5.8|^6.0|^7.0|^8.0 -> found illuminate/support[v5.8.0, ..., 5.8.x-dev, v6.0.0, ..., 6.x-dev, v7.0.0, ..., 7.x-dev, v8.0.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
How can I make it working ?

This open PR on the data source dependency mledoze/countries prevents Laravel 9 support.
I could probably remove the direct dependency and modify my compiler script to use the Github URL pointing to the file I need instead.

Fixed in #20 and tagged a new release, should work right out of the box!

Thank you but I am not able to retrieve the 2.0.1 version, even after a composer clear-cache, it's trying to retrieve 2.0 version. Event if I force the version I got " Could not find package lykegenes/laravel-countries in a version matching 2.0.1"


Cursor is missing

When activating the plugin the cursor on the row is not shown. Not even when you start to write, you see only the letters appear.

I have the same issue, I thought it was because I was running it with the vim plugin, would be nice to get this fixed.

I had to unpublish this plugin as there is no way to fix the issue due to the changes that have been made in Atom v1.1.0. It is good that Atom has this feature built in.

It is good that Atom has this feature built in.

I can't see this feature in Atom. @kharlamov Show Invisibles only supports leading and trailing whitespace, not whitespace between characters.


[Question]: Future Plans for Proton and Contributions

Hello there!
I am really liking the overall idea of Proton, and I personally think if could offer a decent Ruby framework to create desktop apps. The only issue right now is that is only setup to only create the main.js starting the main process for Electron. Do you have any plans or ideas to handle the app-side of Proton?
I can see you use Opal for the Electron side, but surely not the best idea for the app itself. Of course since Proton doesn't touch that side of the app, someone could use whatever they want, like CoffeeScript 2 which brings JSX to the Ruby ring. Have you considered creating a development environment to help users write Ruby code for the app/renderer side without having to stop and compile with every change? (e.g. Using Rails to watch and recompile changes after saves). Also what about offering a default vanilla main.rb file, since users have to rely on the example apps? I really think adding things like this would certainly give Ruby devs the same benefits a JS dev would have natively.
I'm setting up a dev webpacker/coffeescript/sass environment for one of my own projects, and if you would like Proton to offer something like this I certainly don't mind sending an example, or even a PR to add some capability.
Anyways, I thought I would ask, and certainly plan to start sending code/doc PRs your way if you are still active, as I really believe this project has potential.

Sorry @ghivert I meant to give you an update on this, the day-job took over my time, and next thing I knew it had been a year! Anyways, when attacking this, there were way too many caveats and cases where setting up webpack with proton wasn't any better than just using a basic js/webpack setup using Coffeescript. Since there is no longer a ruby binary to install with an electron app, it raises a new issue of having the user take an extra step just to add a ruby base to the app itself. I recently ran into more issues with a polyglot electon app I developed last year, and because there were so many issues with language support and the JS-Ruby bridge, switching Ruby to JS was the best answer to remedy the problems that arose.
Overall/TL;DR There are way too many edge-cases/concerns using Ruby/webpack with Electron, that it felt like it was better to use a common js/webpack setup.

Hi @3DEsprit, and thank you very much for the update! I was just closing the issue because no activity on this since a year seems good to me to close it.
Thanks for you for taking time to leave feedbacks. It's fun because I went through exactly the same path. Like going to Webpack and JS instead of Ruby, because of lack of real support and awesome support for JS, TS, or Elm and Purescript. I changed my main languages, and this project is really not a priority for me.
I would really be happy to know more about your experiences about Electron!


DS3231_test:16:8: error: 'DS3231 clock' redeclared as different kind of symbol  DS3231 clock;         ^~~~~

Hi,
I am trying to load this example Arduino on a Nano attached to a DS3231 RTC and it fails with these error messages.  Is there an update available?
Using library DS3231 at version 1.1.0 in folder: S:\MyProject\AVR\Arduinosketchbook\libraries\DS3231
Using library Wire at version 1.0 in folder:
\AppData\Local\Arduino15\packages\arduino\hardware\avr\1.8.5\libraries\Wire
exit status 1
'DS3231 clock' redeclared as different kind of symbol

Changed "clock" to "clock0", it worked OK.
Thx.


pip package size

The current unzipped pip package size is >600MB making it unusable for deployment on systems like e.g. AWS lambda in my case.
It would be good if e.g. the package could be organized like e.g. the aws boto3 library where the services needed are packaged as package "extras" so you can do something like this in requirements.txt:
msgraph-beta-sdk[security,me] == 1.0.0a9

Hi @haavardw , Thanks for trying the Graph Python SDK.
Currently, this SDK is generated using kiota and the guidelines on how to generated the SDK is dependent on the Kiota library. If you are still interested in having this discussion, kindly open an issue/discussion in Kiota for better visibility and we can have this discussion on the repo. Please start by testing and sharing your experience with the latest version of the SDK


Configuration: outdir should be dist by default and not required

Why closed? I still think outdir should be optional

Sorry, I think I closed this in error.


Work with thunk?

Thank you for the great library. My project is using redux thunk. May i ask if the library works with thunk? If so, is there any sample code?
Thanks for your advice

It does work, however I encountered some bugs which I cannot explain yet when using thunks with redux-offline.


fix: support date ranges in download function

Support for Ranges: https://github.com/npm/registry/blob/master/docs/download-counts.md#ranges

@all-contributors please add @privatenumber for code


chore(CPlusPlus): add find words matching pattern dictionary

Given a dictionary of words where each word follows a CamelCase notation, find all words in it that matches a given pattern of all uppercase characters.
CamelCase Notation is the practice of writing compound words or phrases joined without spaces, where each word’s first letter is capitalized. For example, PowerPoint, LibreOffice, CinemaScope, etc., are in CamelCase.
We can use a Trie data structure to solve this problem. The idea is to insert all uppercase characters of each word in the CamelCase dictionary into a Trie. In contrast, the complete word is stored in a container associated with the corresponding leaf node. After the complete dictionary is processed, traverse the Trie and find all words that match the given pattern.
Output:
HiTech
HiTechLab
HiTechCity

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[ ] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

@UG-SEP please review.

@ming-tsai i have edited the readme file. @Arsenic-ATG could you please review and merge this too.

@ming-tsai please assign review to @Arsenic-ATG

@ming-tsai please assign review to @Arsenic-ATG

This also requires an update in readme.md patch-1 branch this time.

Done @Arsenic-ATG


docs(avatar): update docs

What I did

Updated the docs for rh-avatar element based on the specs mentioned in https://github.com/RedHat-UX/red-hat-design-system/issues/909

Testing Instructions

Review the updated docs for rh-avatar(preview) and check if they match the design spec and the content

@diwanshi Looks fantastic! Some tiny edits:
Style tab

Spacer image in table is still 2x
Change Interaction States heading to Interaction states

Guidelines tab

Small breakpoints heading, image still looks 2x
Change Best Practices heading to Best practices

see #1005 and #949 wrt spacer images

@diwanshi Final edits:
Overview page

Add a check in the RHDS column

Guidelines page

Under the Best practices h2 and Thumbnail shape h3, I updated the image and the new version is on Dropbox

@coreyvickery ready for the review.

i'll take a look


.ngfactory not found when upgrading @ngtools/webpack to >1.2.0

OS?

Windows 10

Versions.

node v6.9.4

Repro steps.

I have an app set up with @ngtools/webpack v1.2.0 and webpack v2.1.0-beta.27. When I try to upgrade to any of v1.2.1, v1.2.2, v1.2.3 or v1.2.4 (and also the required webpack version) I get the following error:

    ERROR in ./src/boot-client-aot.ts
    Module not found: Error: Can't resolve './components/main.aot.ngfactory' in 'XXXXX\src'
     @ ./src/boot-client-aot.ts 5:0-70

boot-client-aot.ts:
import "./polyfills";
import "./rxjs-operators";

import { enableProdMode } from '@angular/core';
import { platformBrowser } from "@angular/platform-browser";
import { MainModuleNgFactory } from "./components/main.aot.ngfactory";

enableProdMode();

// Boot the application, either now or when the DOM content is loaded
const platform = platformBrowser();
const bootApplication = () => { platform.bootstrapModuleFactory(MainModuleNgFactory); };
if (document.readyState === "complete") {
    bootApplication();
}
else {
    document.addEventListener("DOMContentLoaded", bootApplication);
}

Webpack config:
var ngToolsWebpack = require("@ngtools/webpack");
// ....
    plugins: [
        new ngToolsWebpack.AotPlugin({
            tsConfigPath: path.resolve(__dirname, "tsconfig.aot.json"),
            entryModule: path.resolve(__dirname, "ClientApp", "components", "main.aot#MainModule"),
        }),

It's worth noting that I tried different paths for the plugin configuration without success, including setting them through my tsconfig.aot.json.
Any help would be appreciated. Thanks!

@hansl any idea what's going wrong?

just tried v1.2.8 and it's still not working.

resolved ?

Sorry I'm not able to provide a repro at the moment. Are you having this same issue? Can you help with a repro?
Thanks!

Sorry i just only used the @ngtool/webpack in my project. It's work in my repo but when i run my other project i got some error

It seems to work if I use a simple main file and let the tools do their magic by convention like here: https://github.com/kunl/Angular-webpack-AOT/blob/master/src/main.ts

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.


pythonPackages.xmljson: init at 0.2.1

pythonPackages.xmljson: init at 0.2.1
Motivation for this change
This is required for adding pythonPackages.imantics. https://github.com/NixOS/nixpkgs/pull/102442
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 102440 run on x86_64-darwin 1

3 packages built:

python27Packages.xmljson
python37Packages.xmljson
python38Packages.xmljson


:bug: Fix: Broken openzepplen version in svelte build

Description
Svelte build had a bad version of open zepplen that didn't run in ci because the package was missing build:dist
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #790   👈

PR #789

This stack of pull requests is managed by Graphite.


[Request] level uncompleter

It uncompletes levels like in mega hack
steps:
So check if you did the level, And then check is it plat or classic. Then see how many stars it gives, and take away the stars and correct difficulty of demon. Maybe there is more but thats all I can think of.

Yeah we really need that, I accidently beat a level with speedhack and for some reason it counted as a completion (I had safe mode on)

This already exists


ci: test on 3.12.0b3

Closing - there seem to be issues compiling greenlet issues on 3.12. Will wait for 3.12 proper before taking any action I think


Add tags

Add tags to allow more granular tasks filtering.
Add generator script for MD formatted tags found.
Add docs for tags how-to.
Partial implements https://github.com/kubernetes-incubator/kargo/issues/699
Signed-off-by: Bogdan Dobrelya<EMAIL_ADDRESS>

This approach sounds nice, but I think we need some more overlap and an idea of which tag combinations should work. I'll get more into this tomorrow.

This unblocks the ofline/intranet footprint. Otherwise, the early preconfigured DNS fails on Red Hat. This may be related to its DNS stack implementation, libc libs etc. If we configure kubedns IP in /etc/resolv.conf  and there is no k8s yet deployed, it fails with timeout for priv escalation error... And w/o tags, I cannot smooth implement separated DNS config stages: one that stands for ealry config, and one for the latest, for which there are already dnsmasq ds/kubedns app serving requests.

@mattymo also note that this only adds some flexibility, like for example commands I provided in the docs, or ... cluster.yml --tags netchecker,download to deploy and enable netchecker manually on live cluster, and much more cases. While takes away nothing. Even though this is not complete implementation yet.

looks good, maybe a little too much granularity. Make sure that running any of this single tag make sense.

@ant31 it's hard to predict deploy paths users will want to execute on their brown-field clusters. For example, rolling upgrades on kube-apiservers (plus hyperkube) but nothing else.


Expense App- how to make data stay ?

Hello sir, how can we make our entries/data stay after refreshing the page ? 😊

Use something like Firebase for that. It's easy to integrate.
Or learn Express plus MongoDB.


Unbound: Add description for [reload] action

Adds description for unbound's configd [reload] action
This causes the reload option to show up as a predefined action in cron and Let's Encrypt UI pages.[1] This is desirable if you want to use your Let's Encrypt certificate to offer DNS-over-TLS via unbound on port 853, so that the LE plugin can reload the unbound config whenever it renews the relevant certificate
[1] https://forum.opnsense.org/index.php?topic=6177.msg25956#msg25956

Restart already has a description on 21.7 and reload has been removed -> closing this PR.


resolves #2521 don't hyphenate autolink when hyphenation is enabled

(see commit log message for details, including caveats)
(sorry about the force push, I won't do any more of those)

I've updated the implementation to use a skipping filter instead of a backreference. I think this is a cleaner and more stable approach.

Once the tests pass, I will accept this change. A few notes about future PRs that will help them get merged faster.
First, every non-docs PR should have an associated issue. Without an issue, PRs mostly get ignored because they provide any context and are difficult to track using our process. Before submitting a PR, always start by creating an issue. You can mention in the issue that you intend on submitting a PR, which will help get the issue scheduled.
Both the CHANGELOG entry and the PR should reference the issue.
Aside from that, I'd actually say the PR was pretty good. Don't worry about force pushing in a PR. That is completely acceptable. The main goal is that you want to end up with only one commit.


Navigating within Arguendo

@budparr Once you get into a specific "Arguendo", there is no easy way to navigate to the other Arguendos. To me, it is important that we capture people who are interested in this idea of multiple takes on a given question.
http://www.international-criminal-justice-today.org/arguendo/question/How-can-the-international-community-best-support-the-need-to-protect-witnesses-in-international-criminal-trials/
Maybe an arrow that people can hit that takes them back to here (http://www.international-criminal-justice-today.org/arguendo/ ) that says something like "Back to Arguendo homepage"

Duplicate #31

actually, leave this one open because it's more descriptive, closing the older one

@budparr Is there anyway to make it more prominent and maybe placed above the column of experts? That is where my eye is drawn, and there is lots of white space there to occupy.

I can make it more prominent (bigger), but I think it has to have that tight relationship to arguendo, so should be in the same place.


CSSnext & preCSS Support

Please add CSSnext & preCSS Support
When using cssnext in combination with precss a lot of warning are given concerning expected braces or semicolons when nesting. This leads to a lot of red stripes and color theme being completely off.
Configuration is:
CSSnext (through PostCSS)

PreCSS for Sass-like nesting

Yeah, we would really like this too...
Obviously it makes no sense to talk about adding syntax support for PostCSS, as that is nothing more than a task runner and could theoretically support any syntax, but it would be really great to have an option to at least enable support for the subset of future css syntax supported by CSSNext (http://cssnext.io/features).
Our design/css/html guys work in Sublime Text and they absolutely insist on using PostCSS with CSSNext - which is fine, except that the mess of red squiggles the rest of us see in VS Code is really getting in the way of collaboration. Is this something you would consider supporting?

@thomas-darling Does it help to disable the built-in CSS validation using "css.validate": false and then use one of the CSS linter extensions, e.g., https://marketplace.visualstudio.com/items?itemName=shinnn.stylelint?

The former will certainly help but the highlighting is off too.

Has there been any progress on this front by chance?

I used https://marketplace.visualstudio.com/items?itemName=ricard.PostCSS.

I need proper cssnext support 👍

Adding a user setting that allows you to enable future CSS spec validation, would be a helpful and logical way to support CSSNext.

Assigning to @aeschli, there are some recent CSS improvements.

Recently I added support for variables, for @apply and custom property to the base CSS support.
In general we only adopt css specs when they become widely adopted and supported by all the major browsers. There are a lot of proposed specs out there. You can imagine that it's takes a lot of time to study, adopt the parser and get it right.
Please file specific requests for features to support. The current issue (add support for CSSNext and  preCSS) is too broad to take action on.
Also, if you don't want to wait: Write an extension that adds the missing features. Or make a pull requests. https://github.com/Microsoft/vscode-css-languageservice is the repository for the css language support.

using the ricard.PostCSS plugin, provides correct syntax highlighting for .pcss, .postcss files.
you can then associate .css files to be treated as .pcss files in your settings, and you'll get the correct syntax highlighting:
    "files.associations": {
        "*.css": "postcss"
    }

Note: this method will completely disable validation, as postcss is not a known target for validation.

As mentioned, please file specific issues if you want the css support to catch up on a new css spec.


split code block in examples/preprocessing/plot_virtual_evoked

right now, because all plots come from a single code block, they are plotted at the top of the example in a group of 4 (and consequently the plots are really small).  By splitting the 4 plotting calls into different code blocks, they will plot larger / be easier to see & compare, without increasing run time of the example.  Code blocks can be split with a line of 79 # marks (adding a bit of explanatory text too is usually a good idea)

I would like to take care of this one

File name (plot_evoked) and title (Remap mag channels) of this example are different. Not sure how important it is to you that they match?
In my opinion, the title seems to be more appropriate than the file name, but changing file names is probably more troublesome than changing a title.


add other symbol

SECURITY_PREFIX It is marked as a static variable.
I think other symbols should be similarly marked for subsequent maintenance

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Tag with close icon gives error: Cannot read property '0' of undefined

Using the following snippet provided on chip demo page:

  Tag
  close

Clicking on the close icon gives the following error:
materialize.js:5769 Uncaught TypeError: Cannot read property '0' of undefined
    at r.fn.init.selectChip (materialize.js:5769)
    at HTMLDivElement.<anonymous> (materialize.js:5546)
    at HTMLDocument.dispatch (jquery-3.2.1.min.js:3)
    at HTMLDocument.q.handle (jquery-3.2.1.min.js:3)

This bug is present on the demo page: http://materializecss.com/chips.html .... simply click the close icon of the tag with Tag text on top of the page, you'll get the error in the console.

How to reproduce
I created a Plunker that demonstrate the error.
Investigation
I found out that the error happens when you have both tag and chips input on the same page.
The initilalization of the chips input seems to interfere with the tag ... which gives an error when closing a tag as he tries to select the previous chip but there is none.
materialize.js:5774 Uncaught TypeError: Cannot read property '0' of undefined
    at r.fn.init.selectChip (VM3645 materialize.js:5774)
    at HTMLDivElement.<anonymous> (VM3645 materialize.js:5551)
    at HTMLDocument.dispatch (VM3539 jquery.min.js:3)
    at HTMLDocument.q.handle (VM3539 jquery.min.js:3)

Following stack traces shows that it breaks in selectChip function which is called from chips-select event.
Possible solution
Validate if there is any chip to apply the selected class and trigger chip.select event before to do it.
this.selectChip = function(chipIndex, $chips) {
  var $chip = $chips.find('.chip').eq(chipIndex);
- if ($chip && false === $chip.hasClass('selected')) {
+ if ($chip && $chip.length > 0 && false === $chip.hasClass('selected')) {
    $chip.addClass('selected');
    $chips.trigger('chip.select', $chips.data('chips')[chipIndex]);
  }
};

Are you up for a fix?
I noticed the master branch has been pushed toward v1.0.0 which brought me to ask if you guys are event going to be willing to do a new release of v0.100.x?
If the answer is yes and that you are ok with the possible solution here, I can provide the PR.
I am waiting for your follow up,
Thanks again!


Rename the default branch from master to main

This change would align with the other repos in webdriverio and webdriverio-community.
For more see https://github.com/github/renaming?tab=readme-ov-file#renaming-the-default-branch-from-master.

Let's wait with this until #126 is merged.

It's pretty easy to change the base branch:
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request

Updated the name. It seems that it didn't had an impact on the PR.


Add socio-economic indices data layers (2016) from AURIN

All layers have the end points under each data description on https://map.aurin.org.au/
Add the following (2016 only) datasets from AURIN to Investor Map, under the Social and Economic - Socio-economic indices:

[ ] ABS Estimating Homelessness by LGA 2016

[ ] ABS Estimating Homelessness by SA2 2016

[ ] ABS SEIFA IEO by SA1 2016

[ ]  ABS SEIFA IEO by SA2 2016

[ ] ABS SEIFA IER by SA1 2016

[ ] ABS SEIFA IER by SA2 2016

[ ] ABS SEIFA IRSAD by SA2 2016

[ ] ABS SEIFA IRSD by SA1 2016

[ ]  ABS SEIFA IRSD by SA2 2016

[ ] NATSEM OECD Indicators: Synthetic Estimates SA2 2016

[ ] NATSEM Social and Economic Indicators: Dependency Rate SA2 2016

[ ] NATSEM Social and Economic Indicators: Employment Rate SA2 2016

[ ] NATSEM Social and Economic Indicators: Indigenous Indicators SA2 2016

[ ] NATSEM Social and Economic Indicators: Migration Rate SA2 2016

[ ] NATSEM Social and Economic Indicators: Synthetic Estimates SA2 2016

[ ] NATSEM Social and Economic Indicators: Unemployment Rate SA2 2016

[ ]  NATSEM Social and Economic Indicators: Volunteering SA2 2016

[ ] NATSEM Health and Wellbeing Indicators: Synthetic Estimates SA2 2016

[ ] NATSEM Trust Indicators: Synthetic Estimates SA2 2016

[ ] VAMPIRE SA1 2016

Under Social and Economic group, create a sub-group Population Density with the following layers from AURIN:

[ ] ABS G01 Population Density by SA1 2016

[ ] ABS Population Density by Mesh Block 2016

AURIN informed about this addition in case they have some suggestions or upcoming additions of data/indices.

NATSEM OECD Indicators: Synthetic Estimates SA2 2016

Only exists as 2011, added that.

NATSEM Health and Wellbeing Indicators: Synthetic Estimates SA2 2016
NATSEM Trust Indicators: Synthetic Estimates SA2 2016
VAMPIRE SA1 2016

These technically exist in a different group in AURIN. Added.

Note that "map.aurin.org.au" has to be added to the CORS proxy whitelist in production. I'm not sure where that is managed?