new setup not working

Hi, I've been trying to setup the tailwindcss coc.nvim extension for a couple of days now but cannot get it to work. Could someone point me in the right direction? tailwind completion in vim would be awesome. I'm new to coc.nvim
I installed by :CocInstall coc-tailwindcss
I am using the example coc vimrc config
When trying to modify the html file in the tailwind playground repo and would expect to see some suggestions for tailwind's utility classes by nothing shows up. Project includes the tailwind.config.js
There are no obvious error messages anywhere and I don't know how to confirm if coc.nvim is working. Could I have missed some config somewhere?
CocInfo:
## versions

vim version: NVIM v0.4.3
node version: v12.15.0
coc.nvim version: 0.0.78-95e7ca8324
coc.nivm directory: ~\.vim\bundle\coc.nvim
term: undefined
platform: win32

## Output channel: tailwindcss-language-server

Can not reproduce, have you run yarn install or npm install in that repo?

Yep, already run those in my project.
I tried :checkhealth and it returned this:
health#coc#check
========================================================================
  - OK: Environment check passed
  - WARNING: pyx command not work, some extensions may fail to work, checkout ":help |pythonx|"
  - OK: Javascript bundle build/index.js found
  - OK: Service started

so am looking into the pythonx route

setting "tailwindCSS.trace.server": "verbose" and checkout tailwindcss-language-server output channel.

I had a similar encounter and got something like this when I reload coc-tailwindcss with CocList extensions:
[coc.nvim] error: UnhandledRejection: Connection got disposed.
When I ran npm install, and reloaded, it didn't work. But after setting this "tailwindCSS.trace.server": "verbose" and coming back to a html file, it worked. 😄 . It hasn't failed even after removing that from coc config.

@iamcco
set thte verbose setting and viewing language server output channel as described here
The server log seems to be blank?? (bottom window in screenshot) Let me know if I'm looking in the wrong place, I've not used Coc loads. Thanks!

The LSP is not active, it seems can not found your tailwindcss config

folder structure is below. the html file is ./public/index.html and tailwind.config.js is in the root folder
tree -L 2
.
|-- README.md
|-- css
|   `-- tailwind.css
|-- node_modules
|   `-- ....
|-- package.json
|-- postcss.config.js
|-- public
|   |-- build
|   `-- index.html
|-- tailwind.config.js
`-- yarn.lock

274 directories, 8 files

@iamcco any ideas on what to try next?
I've installed coc-tailwindcss and coc-html with otherwise clean nvim config and am still getting the same issue with coc-tailwindcss (coc-html seems to work fine)

I have no idea since there is nothing log you can offer.

Will upgrade to the new LSP when have time https://github.com/iamcco/coc-tailwindcss/issues/33

I'm having a similar issue. Installed coc-tailwindcss and no suggestions at all. I'm testing in a new index.html with the following content:
<html>
    <body class="bg-gray-">
    </body>
</html>

My cursor is on bg-gray- but no suggestions.
Here's the log after setting to verbose:
## versions

vim version: NVIM v0.4.3
node version: v14.1.0
coc.nvim version: 0.0.74-e04013a8bd
term: iTerm.app
platform: darwin

## Messages

## Output channel: tailwindcss-language-server

[Trace - 12:11:55 p.m.] Sending request 'initialize - (0)'.
Params: {
    "processId": 62805,
    "rootPath": "/Users/chin/Desktop/Projects/coach",
    "rootUri": "file:///Users/chin/Desktop/Projects/coach",
    "capabilities": {
        "workspace": {
            "applyEdit": true,
            "workspaceEdit": {
                "documentChanges": true,
                "resourceOperations": [
                    "create",
                    "rename",
                    "delete"
                ],
                "failureHandling": "textOnlyTransactional"
            },
            "didChangeConfiguration": {
                "dynamicRegistration": true
            },
            "didChangeWatchedFiles": {
                "dynamicRegistration": true
            },
            "symbol": {
                "dynamicRegistration": true,
                "symbolKind": {
                    "valueSet": [
                        1,
                        2,
                        3,
                        4,
                        5,
                        6,
                        7,
                        8,
                        9,
                        10,
                        11,
                        12,
                        13,
                        14,
                        15,
                        16,
                        17,
                        18,
                        19,
                        20,
                        21,
                        22,
                        23,
                        24,
                        25,
                        26
                    ]
                }
            },
            "executeCommand": {
                "dynamicRegistration": true
            },
            "configuration": true,
            "workspaceFolders": true
        },
        "textDocument": {
            "publishDiagnostics": {
                "relatedInformation": true
            },
            "synchronization": {
                "dynamicRegistration": true,
                "willSave": true,
                "willSaveWaitUntil": true,
                "didSave": true
            },
            "completion": {
                "dynamicRegistration": true,
                "contextSupport": true,
                "completionItem": {
                    "snippetSupport": true,
                    "commitCharactersSupport": true,
                    "documentationFormat": [
                        "markdown",
                        "plaintext"
                    ],
                    "deprecatedSupport": true,
                    "preselectSupport": true
                },
                "completionItemKind": {
                    "valueSet": [
                        1,
                        2,
                        3,
                        4,
                        5,
                        6,
                        7,
                        8,
                        9,
                        10,
                        11,
                        12,
                        13,
                        14,
                        15,
                        16,
                        17,
                        18,
                        19,
                        20,
                        21,
                        22,
                        23,
                        24,
                        25
                    ]
                }
            },
            "hover": {
                "dynamicRegistration": true,
                "contentFormat": [
                    "markdown",
                    "plaintext"
                ]
            },
            "signatureHelp": {
                "dynamicRegistration": true,
                "signatureInformation": {
                    "documentationFormat": [
                        "markdown",
                        "plaintext"
                    ],
                    "parameterInformation": {
                        "labelOffsetSupport": true
                    }
                }
            },
            "definition": {
                "dynamicRegistration": true
            },
            "references": {
                "dynamicRegistration": true
            },
            "documentHighlight": {
                "dynamicRegistration": true
            },
            "documentSymbol": {
                "dynamicRegistration": true,
                "symbolKind": {
                    "valueSet": [
                        1,
                        2,
                        3,
                        4,
                        5,
                        6,
                        7,
                        8,
                        9,
                        10,
                        11,
                        12,
                        13,
                        14,
                        15,
                        16,
                        17,
                        18,
                        19,
                        20,
                        21,
                        22,
                        23,
                        24,
                        25,
                        26
                    ]
                }
            },
            "codeAction": {
                "dynamicRegistration": true,
                "codeActionLiteralSupport": {
                    "codeActionKind": {
                        "valueSet": [
                            "",
                            "quickfix",
                            "refactor",
                            "refactor.extract",
                            "refactor.inline",
                            "refactor.rewrite",
                            "source",
                            "source.organizeImports"
                        ]
                    }
                }
            },
            "codeLens": {
                "dynamicRegistration": true
            },
            "formatting": {
                "dynamicRegistration": true
            },
            "rangeFormatting": {
                "dynamicRegistration": true
            },
            "onTypeFormatting": {
                "dynamicRegistration": true
            },
            "rename": {
                "dynamicRegistration": true,
                "prepareSupport": true
            },
            "documentLink": {
                "dynamicRegistration": true
            },
            "typeDefinition": {
                "dynamicRegistration": true
            },
            "implementation": {
                "dynamicRegistration": true
            },
            "declaration": {
                "dynamicRegistration": true
            },
            "colorProvider": {
                "dynamicRegistration": true
            },
            "foldingRange": {
                "dynamicRegistration": true,
                "rangeLimit": 5000,
                "lineFoldingOnly": true
            }
        }
    },
    "trace": "verbose",
    "workspaceFolders": [
        {
            "uri": "file:///Users/chin/Desktop/Projects/coach",
            "name": "coach"
        }
    ]
}

I encounter the same problem.
After I enter git init at the project root, the problem is resolved
I guess the tailwind.config.js should be placed in the directory that same with the workspace folder.
Before I enter git init at the project root, I open the index.html then I check the workspace folder. The workspace folder is the same as where I open the index.html.
I guess the LS will not startup when the tailwind.config.js not placed in  the workspace folder

I had the same issue... seemed everything was working OK but changing from Node 10.x to Node 14.x fixed it all up.  Hope this helps someone else.

I had the same issue... seemed everything was working OK but changing from Node 10.x to Node 14.x fixed it all up.  Hope this helps someone else.


Fix Webots-Ros package

Some dependencies were missing.

test me

Build Passed :ok_hand:
You can safely merge 'fix-webots-ros-package' into 'revision'.

:+1:


fix dvr tests regex in whitebox_neutron_tempest_jobs.yaml

Whitebox neutron tempest plugin test_dvr_ovn file contains not only OvnDvrTest class with tests but also OvnDvrAdvancedTest that has a requirement to run without other tests in the background. This patch widens the regex for dvr tests to ensure all dvr tests run in a single thread workflow.

/lgtm

/ok-to-test

/approve

/lgtm


[1413] Add ordering attribute to models for display sorting

closes #1413

migrate to add ordering attribute and populate existing models
update equipment_model creation to add ordering automatically
add cell to /views/equipment_model/_table to show ordering
add buttons to above table to adjust ordering
add 'up' and 'down' routes to equipment_models_controller to adjust ordering
create rspec testing

Looks great! The only issues I came across were when I was testing with deactivation and reactivation of equipment models.
Steps to reproduce
I had 4 equipment items ordered from 1 to 4. I deactivated # 1 and # 3. The items orders correctly scaled to 1 and 2. I then clicked down on #1 twice. This resulted in two equipment models having the same ordering of 2.

I am no longer able to create new models using the form. Tests aren't catching this, and I think the problem is on master as well. I'll submit an issue.

oof, that's a big issue, hope it's an easy fix.
@zeffman ping me when this is ready for rereview!

Ready for review


Update examples_test.go

Please don't use relative paths. I want to use the package but this is causing problems. I plan on using the package during my GolangUK talk on Friday but I need this fixed.

Wrong version number


feat: tenant details for multi-tenant agent on webhook

[x] Get tenant details on multi-tenant agent webhook.
[x] Filter and store the connection details from webhook based on tenant Id(Org).
[x] Filter and store the credential details from webhook based on tenant Id(Org).
[x] Filter and store the verification details from webhook based on tenant Id(Org).
[x] Research on supabase real-time for web-notification

Completed


Image load optimization V2

Second stab at image load optimization, sticking with useAssets but making it async. There seems to be some hydration error now, have to check if that is just a local dev issue.

Seems like a good improvement. Let's get this live and save 6+ MB on the home page. YOLO.


sdk.deployer.addDeployListener

Hello, i am doing some stuff that listening deploy events using thirdweb library.
Currently, i can listen with status === 'completed' but not status === 'submitted'.
and my version is below.
"@thirdweb-dev/react": "^3.10.3",
"@thirdweb-dev/sdk": "^3.10.3",
"@typechain/ethers-v5": "^10.2.0",

My code is below

const bytecode = "";

export default function Home() {
  const sdk = useSDK();
  const handleDeploy = () => {
    sdk?.deployer.deployContractWithAbi([], bytecode, []);
  };

  const handleListen = (e: DeployEvent) => {
    console.info("[Listening event] : ", e);
  };

  useEffect(() => {
    if (sdk) {
      console.info("[Listen started]");
      sdk.deployer.addDeployListener(handleListen);
    }

    return () => sdk?.deployer.removeDeployListener(handleListen);
  }, [sdk]);

  return (
    <>
      <button onClick={handleDeploy}>Deploy</button>
    </>
  );
}

is there any my fault?
Thank you,

@styleai-luke we actually introduced a new API to get low level control on any transaction done with the SDK, including deploys. On any transaction, you can call .prepare which will return a transaction builder that you can configure, estimate gas, simulate, submit to the blockchain and wait for transactions. See documentation here: https://portal.thirdweb.com/typescript/sdk.smartcontract.prepare
for your use case it would look like this:
const tx = sdk?.deployer.deployContractWithAbi.prepare([], bytecode, []);
// submit the transaction and get the tx hash back
const sentTx = await tx.send();
// wait for confirmations
await sentTx.wait();

let me know if that helps!

Oh it is perfectly working, thank you:)


Transitions: Adjust widths, fix bug with duplicate schools

Fix to https://github.com/studentinsights/studentinsights/pull/2491/files, duplicate schools in the select.

selfie


Moved some capabilities to plugins folder

Based on #280 and my recent work on making a method registry in #328, this is a first step in that direction, trying to isolate code per auth method. That's not the end of the road, but this commit should at least pass the tests.
We are breaking compatibility because we moved the PhoneDevice models to plugins/phonenumber sub-app, but I think that's a price to pay for added modularity.

Looks good! Just a couple of questions:

Is Django going to happy about migrations for PhoneDevice being in a different app?
How much more work would be needed to make django-phonenumber-field optional? From what I can see, this is mostly done with the exception of migrations.

The fact that tests are running fine makes me think the application of migrations is OK (thanks to the Meta.app_label I guess). When doing a makemigrations, the migration file is created in two_factor/migrations, so they will need to be moved by hand (no impact on users IMHO).

Yes, this is a good step in that direction. Would you like this in this same PR?

I just pushed one more commit to go towards phonenumbers independence. Still not there yet.

Making django-phonenumber-field optional is not required for this PR to be merged. I was just getting an idea of how much future work would be required if we wanted to go fully modular with this package.

The failure is a connection timeout while fetching Python 3.5

Are there still reservations about going forward with this patch?

I still need to do a code review, but I thought you were still making changes. As that's not the case I'll try and get on with that this weekend.
To be clear: I like this PR and I think it's the right way froward. The code review will just be me nit-picking :cat:

Feel free to nit-pick as much as you want!

I have yet to test this out on a real Django app and while I could probably get a Twilio working on my app (Twilio has a free trial) I don't own a Yubikey. @claudep how much testing of your own have you done?

For me, this is a step preparing the addition of a U2F plugin. I have tested that (still local) plugin with my Yubikey an it's working without breaking the "normal" TOTP functionality. Frankly, I don't know how I can use my Yubikey to make the current yubikey backend working.
After this and the U2F plugin are in, you might release a pre-version so more people are able to test it in real projects. A new major version number can also signify users that major stuff have been "touched".

Great approach!
Maybe, if we change the structure of this package, we should separate everything related to yubikey and phonenumbers into the plugin folder (probably even regarding TOTP too). If we add a documented interface for the plugins, it becomes a lot easier to include additional devices and reduce special logic for some devices in the core package. Instead we might include some abstract classes and templates to reduce boilerplate in the plugins.
I could see that this paves the way for multiple open issues (and support of WebAuthn @compsult ). Moreover, by decoupling the code testing might become easier.

Great approach!
Maybe, if we change the structure of this package, we should separate everything related to yubikey and phonenumbers into the plugin folder (probably even regarding TOTP too). If we add a documented interface for the plugins, it becomes a lot easier to include additional devices and reduce special logic for some devices in the core package. Instead we might include some abstract classes and templates to reduce boilerplate in the plugins.
I could see that this paves the way for multiple open issues (and support of WebAuthn @compsult ). Moreover, by decoupling the code testing might become easier.

I just rebased on latest master. @moggers87, I think it would be great to finish review and do the merge as soon as possible (no rush, of course), so the upcoming email/webauthn/u2f methods could use the new plugin structure. We may also think about starting a 2.x release series to convey the importance of the structural change.

Thanks a lot for merging! Just a quick note for the future: In general, when I keep separated commits in a pull request, that's because it makes sense to cleanly separate them in consistent chunks, so it should be nice to keep the different commits when merging (no squashing). I also could have specified that earlier... so I'm also to blame :-)


[KMS] Creating the doc.

Thanks!
I would still like to get Harsh's opinion on the structure before merging, since he has had interesting thoughts on docs.


Adding VPC description support and orchestration

WIP: Added VPC description support and orchestration.
Also added some unit tests with Tox.

Need to make DhcpOptions only include the ID for the VPC orchestration.
Also, only pull in the VPC Peering IDs vs. all the details for the orchestration.


RSPM (or rig) does not support this distro: debian 11

Having successfully used rim in the past I tried using rig 0.4.0 on a brand new installation of Debian 11.3 and got the following message
[INFO] Adding /usr/local/bin/R-4.2.0 -> /opt/R/4.2.0/bin/R
[INFO] Setting default CRAN mirror
[INFO] RSPM (or rig) does not support this distro: debian 11
[INFO] No system requirements support for this distro: debian 11 :(
[INFO] Installing pak for R 4.2.0 (if not installed yet)

Can you tell what the messages in lines 3 and 4 mean? The installation appears to work i.e. I can start R and it works.
Thanks

The first means that https://packagemanager.rstudio.com/client/#/ does not support Debian, so rig does not set that up for you.
The second means that rig does not support automatic system (Debian) package installation when installing R packages.

I can see how this can be confusing. Do you think we can have a better message? Or we should remove it completely?


CASSANDRA-19278 Avoid over-skipping of key iterators from static column indexes during mixed intersections

patch by Caleb Rackliffe; reviewed by Piotr Kołaczkowski and Alex Petrov for CASSANDRA-19278

Committed as https://github.com/apache/cassandra/commit/d6c7c87f553a66b8fc270b273886e5fdf3a34f41


Feat/allow html in accordeon

Description
Please include

a summary of the changes
relevant motivation and context
a list of any dependencies that are required for this change

Issue reference
Fixes # (issue)
Type of change
Is it a new feature, bug fix, code improvement, etc.
If it is a breaking change what needs to be done to fix that
Documentation
Is the documentation updated, maybe a link
Tests
(How) has the change been tested
Branch
If the branch to merge to is not development

https://github.com/openstad/openstad-frontend/pull/417 Vervangt deze PR


SSE3 optimization of float32 reduce_add(), reduce_max(), and others not working

given that SSE3 enabled implies SSE2 is also enabled, the sequence of #elif sections in the code:
#elif SIMDPP_USE_SSE2
float32x4 sum2 = _mm_movehl_ps(a, a);
float32x4 sum = add(a, sum2);
sum = add(sum, permute2<1,0>(sum));
return _mm_cvtss_f32(sum);
#elif SIMDPP_USE_SSE3
float32x4 b = a;
b = _mm_hadd_ps(b, b);
b = _mm_hadd_ps(b, b);
return _mm_cvtss_f32(b);
causes SSE2 code to be used even when SSE3 is available.

Fixed in 731f670eecef8732e763df3193dcee7ef08670fa. Thanks!


Opensearch Compatibility PR

Hi,
I've ported the client to use the OpenSearch high-level rest client. I've only made the necessary changes to get it working with the OpenSearch client and have not added tests etc. I've made the changes such that it should still be compatible with elasticsearch client along with the opensearch client.
I've also updated the code gen plugin to generate code for the opensearch classes.
Code changes:

https://github.com/cliffton/es-kotlin-client/pull/2/files
https://github.com/cliffton/es-kotlin-codegen-plugin/commits/master

I was wondering if these changes could be a good candidate to merge with your repository and if I should spend some more time to make a clean PR with tests etc.

Thanks for this. I'm actually working on a v2 of the client where I move away from depending on the now deprecated Java highlevel client (there is a new Java client for Elasticsearch). Basically, I want a client that can deal with opensearch, es7, and es8 and also move away from code generation.

In the meantime, wouldn't it be nice to have this?

Not really, I want to stay compatible with Elasticsearch for now. It's what we use and there's v8.0 coming up soon.  Opensearch is not that big of a priority for me. When I have time, I will rearchitect a few things to allow opensearch, eleasticsearch 7 & 8 by basically getting rid of the dependency on the RestHighLevel client.
But feel free to create a fork for this of course if you need this.

I think the patch above does both, compatibility with Opensearch and with Elasticsearch.

Mainly by copying all the code in a elastic and opensearch variant. That's not really something I want to maintain right now. Having both clients on the classpath is not really great either.
A fork would be the more appropriate solution.


FR: Allow Performance Monitoring to be used in iOS App Extensions

[READ] Guidelines
When filing a feature request please make sure the issue title starts with "FR:".
A good feature request ideally

is either immediately obvious (i.e. "Add Sign in with Apple support"), or
starts with a use case that is not achievable with the existing Firebase API and
includes an API proposal that would make the use case possible. The proposed API
change does not need to be very specific.

Once you've read this section, please delete it and fill out the rest of the template.
Feature proposal

Firebase Component: Performance Monitoring

Describe your use case and/or feature request here.
I have an iOS app with an Action Extension that could benefit from Performance Monitoring. It might look a little different than it does for regular apps, but I believe that this would be beneficial to many iOS developers.

Hi @inPhilly - thanks for the request.
Quick question: Have you tried to include Performance Monitoring in the extension and failed? If so, please let us know what went wrong and what steps you used to get set up. That way we have a good idea of where to look if something is currently broken.

Hi @ryanwilson , I'm having the same issue here. I wanted to see how long my WidgetExtension takes to reload the timeline, and log some custom values depending on the kind of content is fetched depending on some App environment values.
Adding it to the Podfile works fine but then there's an error when I try to use Performance:

cc @visumickey - any idea what could be causing that error to appear?

+1 lots of my code/frameworks is shared across extensions, so right now it's difficult to use the performance SDK. Specifically, I am using new iOS 16 Screen Time API's which make heavy use of extensions, so much of my code runs through extensions.
one big pain-point is that AFAIK you can't do this (this is psuedocode):
#if NOT_EXTENSION
 // track performance
#end

ALL code referencing non-extension safe API  (@available(iOSApplicationExtension, unavailable)) must be called from non-extensions. So this problem "bubbles up" to all code.

Thanks for resurfacing the need for the support for extensions. This can definitely help up prioritize this in the upcoming quarter.
@kgaidis I have not tried this. But can you use the disable performance APIs to see if you can make performance not initialize and process in the extension world? Here are the reference to the firebase performance disable APIs.
In the meanwhile, rest assured, we will work on enabling this feature at the earliest. Thank you!

@visumickey

can you use the disable performance APIs to see if you can make performance not initialize and process in the extension world?

Is this is a question on whether I can still use performance API's outside of the extensions (in my app)? If it is, then yes, I can. The only blocker is having references to the performance SDK inside the extensions. I can still use the performance SDK from my app's target.
If that is not what you meant, then my apologies. LMK if there is something I can still help/answer if-needed.


Update Common Data Service to Dataverse https://docs.microsoft.com/en-us/powerapps/maker/data-platform/use-powerbi-dataverse

Please update references to 'Common Data Service' to 'Dataverse'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 0b0624a6-1375-2fa0-8a41-2b049234d9a9
Version Independent ID: dd507c9c-0273-4b93-5ad6-b68a9ad0b5d4
Content: Use Power BI using Microsoft Dataverse data - Power Apps
Content Source: powerapps-docs/maker/data-platform/use-powerbi-dataverse.md
Service: powerapps
Sub-service: dataverse-maker
GitHub Login: @Mattp123
Microsoft Alias: matp

@aliyoussefi - The references are to the Common Data Services (legacy) connector for Power BI. The article has been updated to reflect that.
Closing issue.


Import Iterable from collections.abc for Python 3.10+ support

Import Iterable from collections.abc for Python 3.10+ support

Hey, thanks for the PR, I'll merge it and release it as drf-serpy 0.4.5


Advanced Composition

First, rename "batch" in proto::Component to "submission", because one submission may contain multiple batches.
When compute_epsilon is called:

Derive batch ids from dependency structure on graph.
Subpartition derived batch IDs by component's submission index.
Compute privacy usage of all subpartitions (reference is_DP function from PSI)
Reduce over subpartition privacy usages.

This algorithm above to batch graphs has been implemented, and the privacy composition is exposed in a function. At this point the function just returns linear composition. Essentially, library integration has been completed but the algorithm itself is missing.


Add IP and IPNET support

Hi!
I`ve add support for IP and IPNET in govaluate.
Expressions like "(MYIP >= <IP_ADDRESS>) || (InNetwork(MYIP, <IP_ADDRESS>/20))" really useful for difficult IP matching.

@antonmedv that pr 1 month older than first comment at master branch expr repo , soooo nope )
But today expr looks great, thank you for info!


[Logging] Update style of the logging tab (updates #46)

This PR updates the design to be inline with what we are getting down for the design. Note this is an initial cut, features like sorting and filtering are not being done at this time. Additionally, the category column hasn't yet been completed and the timing data is missing (pending other discussions). All that said, for what we are doing for logging atm, this PR is complete (obviously unless there are any issues).

Other than some minor comments, LGTM.


Sphinx problem with building dbs server

Applied the PR 649 , I assumed doc generation was disabled.  I was able to build dbs3-pycurl-clientpy3 without generating doc, however I got below errors while building dbs server dbs3py3.
The action "build-cms+dbs3py3+3.16.1000" was not completed successfully because Failed to build dbs3py3. Log file in /build/yuyi/w/BUILD/slc7_amd64_gcc630/cms/dbs3py3/3.16.1000/log. Final lines of the log file:
File "/build/yuyi/w/slc7_amd64_gcc630/external/py3-setuptools/39.2.0/lib/python3.8/site-packages/pkg_resources/__init__.py", line 3108, in _initialize_master_working_set
working_set = WorkingSet._build_master()
File "/build/yuyi/w/slc7_amd64_gcc630/external/py3-setuptools/39.2.0/lib/python3.8/site-packages/pkg_resources/__init__.py", line 570, in _build_master
ws.require(__requires__)
File "/build/yuyi/w/slc7_amd64_gcc630/external/py3-setuptools/39.2.0/lib/python3.8/site-packages/pkg_resources/__init__.py", line 888, in require
needed = self.resolve(parse_requirements(requirements))
File "/build/yuyi/w/slc7_amd64_gcc630/external/py3-setuptools/39.2.0/lib/python3.8/site-packages/pkg_resources/__init__.py", line 774, in resolve
raise DistributionNotFound(req, requirers)
pkg_resources.DistributionNotFound: The 'Sphinx==1.6.3' distribution was not found and is required by the application
make: *** [html] Error 1
make: Leaving directory `/build/yuyi/w/BUILD/slc7_amd64_gcc630/cms/dbs3py3/3.16.1000/WMCore/doc'
setup.py:7: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses
import imp
error: command 'make' failed with exit status 2
error: Bad exit status from /build/yuyi/w/tmp/rpm-tmp.5nZlcQ (%build)
RPM build errors:
Macro %rpmbuild_libdir defined but not used within scope
Bad exit status from /build/yuyi/w/tmp/rpm-tmp.5nZlcQ (%build)

Any ideas? @amaltaro @todor-ivanov @mapellidario

Isn't that PR only to make the client build?  I don't think there's been any attempt at dealing with the server.  Remember, this is just needed to provide a Py3 environment in which WMCore can run so that we can complete the Py3 migration of WMCore.

You are absolutely correct @klannon. The doc generation needs to be disabled at any place where it is initiated in the the server setup code too. The PR mentioned by @yuyiguo is only related to the client setup script.

@todor-ivanov @klannon
The setup file that the PR 649 touched  controls entire DBS code building? So I thought that would disable all doc generation. I may miss something here.
@amaltaro @mapellidario, how you guys handle wmcore doc generation in py3?

It was wmcore trying to generated docs.
python3 setup.py build_system -s wmc-web --skip-docs  stopped the doc generating.

Thanks @yuyiguo for providing that useful command above. It is good to know we have such an alternative.


502: bad gateway on <put> when removing cluster / fleet agent overrides from an existing rke2 cluster

Setup

Rancher version: v2.7-head(95edd02)
Rancher UI Extensions: n/a
Browser type & version:chrome

Describe the bug

when updating an rke2 cluster with existing cluster and fleet agent overrides -> removing all the settings, resulted in a 502 gateway error.
To Reproduce

deploy an rke2 cluster

enter cluster agent overrides for resources, add a toleration, and add a custom affinity
enter fleet agent overrides for resources, add a toleration, and add a custom affinity

allow the cluster to successfully get to an active state
upgrade the cluster

remove all overrides that were entered in the first step

Result
An error is shown in the UI and the user is kept on the cluster edit screen, however the update was actually still applied and the overrides were removed
a padding to disable MSIE and chrome friendly error page

cluster did not appear to go into an updating state
Expected Result

if there's an error, I wouldn't expect the new spec to have applied to the cluster
Screenshots

Additional context

did not happen for an rke1 cluster

Transferred from rancher/dashboard based on @snasovich's comment since it doesn't look like UI. CC: @a-blender

Here's the info I have right now, please lmk if you need more:
safari error:
{"data":"\r\n<title>502 Bad Gateway</title>\r\n\r\n
502 Bad Gateway
\r\n
nginx\r\n\r\n\r\n"}

chrome error:

chrome console logs:

outside of these screenshots, I don't have the network data at this time. If the above info isn't including what you're looking for, please lmk and I can get it for you. @snasovich

@slickwarren
From this description,
An error is shown in the UI and the user is kept on the cluster edit screen, however the update was actually still applied and the overrides were removed
a padding to disable MSIE and chrome friendly error page

cluster did not appear to go into an updating state.
If the update to remove to the agent customization went through, then that tells me that the cluster agent is still connected to rancher and rancher's network connection failed due to other reasons, local network or ingress issues. If the connection to the cluster agent failed, you'd see more like disconnected from cluster agent error not a 502.
Also, it's fine if sometimes you don't see the cluster go into an updating state because the update can be fast. To verify the agent was redeployed with the update, check the rancher logs for 'agent redeployed' and verify the timer on the cluster-agent pod reset indicating a redeploy.

Did you try with Firefox?
Did you see the overrides get removed from the downstream cluster agent or just the rke2 cluster obj?
Has the specific 502 error you are seeing been reproduced/intermittently reproduced in any other setting? Are there other open GH issues for it?

If you were having local network issues, I'd recommend trying to repro again today on a fresh install of Rancher. Rancher logs from the time of API call may also help.

This was not local network issues, and was regularly reproducible on chrome (regular and incognito), and safari, on multiple versions of v2.7-head throughout the last 2 weeks.
The request does seem to go through in every case I've reproduced this, despite the message displayed
There is no other issue filed at this time, but there was some offline (due to security concerns) conversation around this as well in internal channels

This was not local network issues, and was regularly reproducible on chrome (regular and incognito), and safari, on multiple versions of v2.7-head throughout the last 2 weeks.
The request does seem to go through in every case I've reproduced this, despite the message displayed
There is no other issue filed at this time, but there was some offline (due to security concerns) conversation around this as well in internal channels

@slickwarren When you see the request go through, do you see the overrides removed from the cluster agent? Or can you not access the cluster anymore?

The request does appear to update the spec / cluster / fleet agent appropriately, however the user doesn't know that until they leave the 502 error page, and go to edit the cluster again (or go and view the cluster / fleet agent deployments)

exact values used in last repro:

deploy an rke2 cluster

1 node per role
add cluster agent customization:

resource limits: 1000, 1000
resource requests: 100, 100
toleration: tolerate/me , exists , noSchedule
affinity: on the last (required) node affinity, add: label/me , notIn , true

add fleet agent customization:

resource limits: 1001 , 1001
resource requests: 101 , 101
toleration: tolerate/me , equals , noSchedule
affinity: add a (required) node affinity, add: label/me , notIn , true

wait for the cluster to get to an active state
I typically am doing other things for maybe an hour, not sure if the time in between matters
upgrade the cluster

remove all agent customization

set resources to empty in the UI
remove all the tolerations in the UI
for cluster agent, set affinity to default UI option
for fleet agent, remove the required node affinity

@slickwarren Could you please post the rancher server logs from before/during the point of the 502? Without logs, it's hard to tell what call Rancher made that returned a bad gateway and crashed the page.

2023-05-26T16:54:16.655335423Z 2023/05/26 16:54:16 [INFO] clusterDeploy: redeployAgent: redeploy Rancher agents due to agent customization mismatch for [c-m-z4gh8gsq], was [&{[{tolerate/worker Exists  NoSchedule <nil>}] &Affinity{NodeAffinity:&NodeAffinity{RequiredDuringSchedulingIgnoredDuringExecution:&NodeSelector{NodeSelectorTerms:[]NodeSelectorTerm{NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:beta.kubernetes.io/os,Operator:NotIn,Values:[windows],},NodeSelectorRequirement{Key:not.this/nodepool,Operator:NotIn,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},},PreferredDuringSchedulingIgnoredDuringExecution:[]PreferredSchedulingTerm{PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/controlplane,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/control-plane,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/master,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:1,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:cattle.io/cluster-agent,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},},},PodAffinity:nil,PodAntiAffinity:&PodAntiAffinity{RequiredDuringSchedulingIgnoredDuringExecution:[]PodAffinityTerm{},PreferredDuringSchedulingIgnoredDuringExecution:[]WeightedPodAffinityTerm{WeightedPodAffinityTerm{Weight:100,PodAffinityTerm:PodAffinityTerm{LabelSelector:&v1.LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequiremen
t{LabelSelectorRequirement{Key:app,Operator:In,Values:[cattle-cluster-agent],},},},Namespaces:[],TopologyKey:kubernetes.io/hostname,NamespaceSelector:nil,},},},},} &ResourceRequirements{Limits:ResourceList{cpu: {{1 0} {<nil>} 1 DecimalSI},memory: {{1048576000 0} {<nil>}  BinarySI},},Requests:ResourceList{cpu: {{100 -3} {<nil>} 100m DecimalSI},memory: {{104857600 0} {<nil>} 100Mi BinarySI},},}}] and will be [&{[] &Affinity{NodeAffinity:&NodeAffinity{RequiredDuringSchedulingIgnoredDuringExecution:&NodeSelector{NodeSelectorTerms:[]NodeSelectorTerm{NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:beta.kubernetes.io/os,Operator:NotIn,Values:[windows],},},MatchFields:[]NodeSelectorRequirement{},},},},PreferredDuringSchedulingIgnoredDuringExecution:[]PreferredSchedulingTerm{PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/controlplane,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/control-plane,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:100,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:node-role.kubernetes.io/master,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},PreferredSchedulingTerm{Weight:1,Preference:NodeSelectorTerm{MatchExpressions:[]NodeSelectorRequirement{NodeSelectorRequirement{Key:cattle.io/cluster-agent,Operator:In,Values:[true],},},MatchFields:[]NodeSelectorRequirement{},},},},},PodAffinity:nil,PodAntiAffinity:&PodAntiAffinity{RequiredDuringSchedulingIgnoredDuringExecution:[]PodAffinityTerm{},PreferredDuringSchedulingIgnoredDuringExecution:[]WeightedPodAffinityTerm{WeightedPodAffinityTerm{Weight:100,PodAffinityTerm:PodAffinityTerm{LabelSelec
tor:&v1.LabelSelector{MatchLabels:map[string]string{},MatchExpressions:[]LabelSelectorRequirement{LabelSelectorRequirement{Key:app,Operator:In,Values:[cattle-cluster-agent],},},},Namespaces:[],TopologyKey:kubernetes.io/hostname,NamespaceSelector:nil,},},},},} nil}]
2023-05-26T16:54:16.655440084Z 2023/05/26 16:54:16 [INFO] Creating system token for u-k334lys2fw, token: agent-u-k334lys2fw
2023-05-26T16:54:18.010110700Z 2023/05/26 16:54:18 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:18.255007872Z 2023/05/26 16:54:18 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:19.330011076Z 2023/05/26 16:54:19 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:19.471408694Z 2023/05/26 16:54:19 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:19.675914327Z 2023/05/26 16:54:19 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:23.448709224Z 2023/05/26 16:54:23 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:24.953105426Z 2023/05/26 16:54:24 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:25.106595219Z 2023/05/26 16:54:25 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:25.250101
2023/05/26 16:54:25 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:25.781611458Z 2023/05/26 16:54:25 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:25.903995462Z 2023/05/26 16:54:25 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:26.367963212Z 2023/05/26 16:54:26 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:26.729435024Z 2023/05/26 16:54:26 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl: waiting for plan to be applied
2023-05-26T16:54:26.966907694Z 2023/05/26 16:54:26 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl: waiting for plan to be applied
2023-05-26T16:54:27.578708659Z 2023/05/26 16:54:27 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: configuring control plane node(s) ctw-test3-c-6cb59985b7-z98rl: waiting for plan to be applied
2023-05-26T16:54:27.845763983Z 2023/05/26 16:54:27 [INFO] [planner] rkecluster fleet-default/ctw-test3: waiting: ctw-test3-c-6cb59985b7-z98rl,ctw-test3-c2-8cc85b66-n4kjl
2023-05-26T16:54:36.888161268Z 2023/05/26 16:54:36 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023-05-26T16:54:38.087525969Z 2023/05/26 16:54:38 [INFO] Handling backend connection request [c-m-z4gh8gsq]
2023-05-26T16:54:38.183970406Z 2023/05/26 16:54:38 [INFO] Handling backend connection request [stv-cluster-c-m-z4gh8gsq]
2023-05-26T16:54:38.212142365Z 2023/05/26 16:54:38 [INFO] error in remotedialer ser
ver [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023-05-26T16:54:38.237836946Z 2023/05/26 16:54:38 [INFO] Handling backend connection request [stv-cluster-c-m-z4gh8gsq]
2023-05-26T16:54:41.710393388Z 2023/05/26 16:54:41 [INFO] Handling backend connection request [stv-cluster-c-m-z4gh8gsq]
2023/05/26 16:55:00 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023/05/26 16:55:00 [INFO] Handling backend connection request [c-m-z4gh8gsq]
W0526 16:55:00.145524      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Node ended with: an error on the server ("unable to decode an event from the watch stream: stream error: stream ID 94799; INTERNAL_ERROR; received from peer") has prevented the request from succeeding
2023-05-26T16:55:00.146248591Z W0526 16:55:00.145688      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ClusterRoleBinding ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:00.146258071Z W0526 16:55:00.145840      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Role ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:00.146266001Z W0526 16:55:00.145840      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Namespace ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
W0526 16:55:00.145864      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:00.146279581Z W0526 16:55:00.145899      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ClusterRole ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:00.146305281Z W0526 16:55:00.146052      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ServiceAccount ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
W0526 16:55:00.146054      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.RoleBinding ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023/05/26 16:55:00 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
2023/05/26 16:55:00 [INFO] Handling backend connection request [stv-cluster-c-m-z4gh8gsq]
2023/05/26 16:55:06 [INFO] error in remotedialer server [400]: websocket: close 1006 (abnormal closure): unexpected EOF
W0526 16:55:06.819198      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Namespace ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:06.819566165Z W0526 16:55:06.819356      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Role ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:06.819777957Z W0526 16:55:06.819591      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.Secret ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:06.819795497Z W0526 16:55:06.819628      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ClusterRoleBinding ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
W0526 16:55:06.819658      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ServiceAccount ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
W0526 16:55:06.819663      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.RoleBinding ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding
2023-05-26T16:55:06.819829168Z W0526 16:55:06.819700      34 reflector.go:348] pkg/mod/github.com/rancher/client-go@v1.25.4-rancher1/tools/cache/reflector.go:170: watch of *v1.ClusterRole ended with: an error on the server ("unable to decode an event from the watch stream: tunnel disconnect") has prevented the request from succeeding

Following the in-depth investigation this issue is happening due to a confluence of a few things:

Rancher's Steve API now passes Warning headers (see https://github.com/rancher/rancher/issues/39413)
The issue is reproducible on certain setups when there are multiple Affinity customizations only
In the case above, the number of Warning headers generated is quite a lot pushing the response header to over 4 Kb which is the default proxy_buffer_size in NGINX configuration. Bumping proxy_buffer_size makes the issue non-reproducible.

~At this point, the investigations are focused on understanding why Warning headers are returned on some setups but not others. Ideally, we don't want to see these "unknown field" Warning headers.~
Update: It seems to be due to ServerSideFieldValidation k8s feature that is enabled by default since k8s 1.25+ per https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/ - and the setups where the issue reproduced where k8s 1.25 and where not reproducible where 1.24 or earlier.

So, now the focus is to review our CRD(s) to determine why the schema seems incorrect and we use invalid fields.

I verified that the provisioning cluster struct used in our code matches the schema in ETCd that can be retrieved with kubectl get crds clusters.provisioning.cattle.io -o yaml Which also matches the Steve schema defined via https://<server_url>/v1/schemas/provisioning.cattle.io.v1.cluster
Request issues
It appears that the UI is sending a malformed cluster object to the backend, which is causing these errors.
I found three separate problems with the request.

Some of the fields are just in the wrong place, such as.

https://<server_url>/v1/schemas/provisioning.cattle.io.v1.cluster.spec.clusterAgentDeploymentCustomization.overrideAffinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution

Some fields added by Steve should be stripped because they don't exist in ETCd

metadata.fields
metadata.relationships
metadata.state

Other fields are added by the UI and do not exist for example

status.conditions[12].error
status.conditions[12].transitioning

Example
I will use the status conditions error seen below as an example from the UI's PUT request to the backend.
Request Payload from UI for a single condition
{
  "error": false,
  "lastUpdateTime": "2023-05-30T13:06:40Z",
  "reason": "Reconciling",
  "status": "True",
  "transitioning": true,
  "type": "Reconciling"
}

Response Warning Header from K8s
299 - unknown field "status.conditions[12].error"
299 - unknown field "status.conditions[12].transitioning"

v1 schema definition
URL: https://<server_url>/v1/schemas/provisioning.cattle.io.v1.cluster.status.conditions
{
    "id": "provisioning.cattle.io.v1.cluster.status.conditions",
    "type": "schema",
    "links": {
        "self": "https://1908-74-215-28-221.ngrok-free.app/v1/schemas/provisioning.cattle.io.v1.cluster.status.conditions"
    },
    "pluralName": "provisioning.cattle.io.v1.cluster.status.conditionses",
    "resourceFields": {
        "_type": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        },
        "lastTransitionTime": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        },
        "lastUpdateTime": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        },
        "message": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        },
        "reason": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        },
        "status": {
            "type": "string",
            "nullable": true,
            "create": true,
            "update": true
        }
    }
}

struct definition.

Struct: https://github.com/rancher/wrangler/blob/master/pkg/genericcondition/condition.go

@KevinJoiner Kind of on the outskirts of this issue now, but this makes sense that k8s server side field validation has been added in 1.25 but @snasovich could not reproduce on our dev rainbow cluster because it's running k8s 1.24 so those warnings did not show up.

Could you clarify how the fields are in the wrong place here?

https://<server_url>/v1/schemas/provisioning.cattle.io.v1.cluster.spec.clusterAgentDeploymentCustomization.overrideAffinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution

If the UI is sending a malformed cluster obj for affinity values, then that would also make sense how this issue is only consistently reproducible for affinity values being added and then getting removed.

Steve API issue
UI

I would like to point out that based on the Kubernetes docs,
The query parameter fieldValidation may be used to indicate the level of field validation the server should perform. If the parameter is not passed, server side field validation is in Warn mode by default. // hence the 299 errors?
* Strict: Strict field validation, errors on validation failure
* Warn: Field validation is performed, but errors are exposed as warnings rather than failing the request
* Ignore: No server side field validation is performed

we could surprise the 299 warnings about the CRD on the server side by passing fieldValidation=Ignore as a query param. But I do agree with @kinarashah that it'd be better to fix these schema errors rather than just remove the warnings.


Fix and refactor distributed cmd metrics

What changes are proposed in this pull request?
Correct complete metrics counter to only update when all tasks are completed.
Refactor setJobAsFailed to update failure count when setting failure status, change failure counter to update when PlanDefinitionRegistry fails to load job definition.

Potentially fix the stressbench with distributedLoad failure in overmind @yuzhu

alluxio-bot, merge this please


Bump to Pydantic v2

+1

Fixed in https://github.com/shazamio/ShazamIO/pull/124 and 0.7.0 release


Cannot find installation of real FFmpeg (which comes with ffprobe)

@MrinalJain17 I am following your  Jupyter Notebook and when I execute
import numpy as np
import matplotlib.pyplot as plt
from utils import Videos

# The path of a sample video in the training data
sample_files = train_files[:1]

# An object of the class 'Videos'
reader = Videos(target_size=None,
                to_gray=False)

# Loading the sample videos, in their original format
sample = reader.read_videos(sample_files)
print('\nShape of the sample data:', sample.shape)

# Displaying a frame from the sample video
plt.imshow(sample[0][300])

I get AssertionError that says
 0%|          | 0/1 [00:00<?, ?it/s]Traceback (most recent call last):

  File "<ipython-input-11-8fe6b4165331>", line 14, in <module>
    sample = reader.read_videos(sample_files)

  File "C:\Users\sohib\.spyder-py3\utils.py", line 70, in read_videos
    self._read_video(path) for path in tqdm(paths)

  File "C:\Users\sohib\.spyder-py3\utils.py", line 70, in <listcomp>
    self._read_video(path) for path in tqdm(paths)

  File "C:\Users\sohib\.spyder-py3\utils.py", line 126, in _read_video
    cap = FFmpegReader(filename=path)

  File "C:\Users\sohib\Anaconda3\envs\HAR\lib\site-packages\skvideo\io\ffmpeg.py", line 72, in __init__
    assert _HAS_FFMPEG, "Cannot find installation of real FFmpeg (which comes with ffprobe)."

AssertionError: Cannot find installation of real FFmpeg (which comes with ffprobe).

I created a new env in anaconda with python 3.5 and other required packages like sk-video, keras, tensorflow, tqdm, matplotlib, ffmpeg, ffprobe. But still error remains unfixed, what would you suggest doing?

Hi @git-sohib
I believe that you are getting this error because either the FFmpeg codec is not installed on your system, or the location of the binaries has not been added to your PATH.
May I know:

What OS are you using?
How did you installed FFmpeg?

@MrinalJain17  Thanks for your reply, I am on Win10.
I have an env in my Anaconda distribution, after activating an env, I just typed conda install -c menpo ffmpeg .

If you are using Windows, and assuming that you have downloaded ffmpeg, then on extracting the contents of the zip file, the binaries would be available inside a directory called bin/. You need to add the contents of that directory to your path.

@MrinalJain17 I can assure that I downloaded ffmpeg from the link you provided, that's here and it doesn't contain any bin folder. All it has after unzipping are

You need to download the Windows build, not the compressed tar package. Use this link to download it, or configure it according to your needs from here.

@MrinalJain17 Yeap I got it working, thank you for your appreciation

@git-sohib :+1:  Good to know that.


Easy Anvils Incompatibility

I'm having an issue with the reforging tabs not being displayed. Before the assets were moved to a library mod this issue did not occur. After removing Easy Anvils, the issue is resolved.

The tabs are not visible but they are clickable.

After clicking on the right tab both tabs appear.

After exiting the anvil and accessing it again, the tabs disappear.

same issue but i cant click the tab

Added partly compat with https://github.com/Globox1997/tiered/commit/565e64d7bc1851863dcc9e76a765a8fff668d35c
Imo easy anvils should use the old screen and not create a new one - reason for only partly compat


chore: de-glob imports

avoid using glob imports for tests. Only one exception: prelude.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#476  👈
#475
#473
#472
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @pepyakin and the rest of your teammates on  Graphite

I don't see the benefit of this.
My personal policy has always been to avoid glob imports in non-test code (preludes excepted), but to allow super::* in the test file.
The concrete downside of glob imports is that searching for the definition of a type is harder. But in the case of tests, the type is either defined or imported in the main module file anyway.
The concrete benefit of use super::* is to avoid boilerplate code.

I merged this, but don't want to necessarily hold to this rule strongly. I'll give rust-analyzer a try and see if it stays out of my way


Mauro Implementation Planning

Revisit the plan to update to include the changes and have updated version with dependences.
Definition of Done:
1 - Review existing plan and associated tickets on the board
2 - Update with new tasks
3 - Update dependencies
4 - Create new tasks as per updated plan
5 - Update Risks/Issues/Benefits/Dependencies
6 - Share updated plan with stakeholders and management

This was completed last year and a new ticket will be required for 2023


Added support for nest current weather conditions

This adds support for the Nest API current weather conditions. I had a hard time finding a legitimate source that stated where Nest gets this information from. Some people said it is from Weather Underground. Anyway, this change adds support for current temperature, humidity, wind speed, wind direction, and "condition" (i.e., cloudy ).

Looks good :dolphin: One minor comment.

@balloob, I didn't add the error message per sensor part. If you think it
should be removed, what would you suggest instead?
On Feb 18, 2016 11:32 PM, "Paulus Schoutsen"<EMAIL_ADDRESS>wrote:

Looks good [image: :dolphin:] One minor comment.
—
Reply to this email directly or view it on GitHub
https://github.com/balloob/home-assistant/pull/1322#issuecomment-186045787
.

I am trying to get the documentation updated for this. Since the Nest sensor will now be a sensor and a weather component how should it be handled? A new markdown for just the weather portion and don't update the current nest sensor markdown?

Yeah I think that is the right thing to do.


Fails to parse NetworkManager.spec

What happened? What is the problem?
Trying to create an instance of Specfile of NetworkManager.spec fails with the following
    with spec_file.sources() as sources:
         ^^^^^^^^^^^^^^^^^^^
  File "/some-path/.venv/lib/python3.12/site-packages/specfile/context_management.py", line 133, in __call__
    self.values[key] = next(self.generators[key])
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/some-path/.venv/lib/python3.12/site-packages/specfile/specfile.py", line 365, in sources
    with self.sections() as sections, self.tags() as tags:
                                      ^^^^^^^^^^^
  File /some-path//.venv/lib/python3.12/site-packages/specfile/context_management.py", line 133, in __call__
    self.values[key] = next(self.generators[key])
                       ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/some-path/.venv/lib/python3.12/site-packages/specfile/specfile.py", line 292, in tags
    tags = Tags.parse(section, context=self)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/some-path/.venv/lib/python3.12/site-packages/specfile/tags.py", line 497, in parse
    lines = process_conditions(list(section), macro_definitions, context)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/some-path/.venv/lib/python3.12/site-packages/specfile/conditions.py", line 133, in process_conditions
    result.append((line, branches[-2]))
                         ~~~~~~~~^^^^

What did you expect to happen?
The parsing to pass
Example URL(s)
No response
Steps to reproduce
1.
2.
3.

Workaround

[ ] There is an existing workaround that can be used until this issue is fixed.

Participation

[x] I am willing to submit a pull request for this issue. (Packit team is happy to help!)

Hi @bilelmoussaoui !
Just to be sure, we are speaking about this specfile, right?
https://src.fedoraproject.org/rpms/NetworkManager/blob/rawhide/f/NetworkManager.spec
I guess you use a fresh version of specfile.
@nforro do you have any quick ideas what could go wrong here?

I am using the spec file from NetworkManager-1.48.2-2.el9 as I am trying to make use it for some internal experiment.

@nforro do you have any quick ideas what could go wrong here?

Yes, I've already fixed it but discovered another bug during that, so it will take a bit more time :slightly_smiling_face:

Thanks a lot @nforro


Add CloudWatch metrics for authorization/throttling

Adds metrics for places where we return an error (ie, do not allow access) in either the HTTP or websocket authorizers.
A couple things I don't love about what I have here:

Duplicated logging code between HTTP and websocket authorizers. The validation of the token in the websocket authorizer should be refactored to look more like the validation that happens in the HTTP authorizer, which uses a helper TokenValidator to do the validation. The code that takes the event and context objects and deconstructs it into function names, the AWS region, etc. is kind of all over the place. I can't decide whether I should do some prefactoring before adding these metrics. I did a bit of a refactor to share logging code between the two authorizers. Still would be nice to move the DynamoDB client in websocket_authorizer somewhere else, but can do that another time.
The metrics produced here are all caps, snake cased (eg, NOT_VETTED). Metrics being produced from our Java project are upper camel cased (eg, ColdBootTime). We could update the strings of the token states we use to be something more descriptive/camel cased (eg, TokenNotVetted), but would also need to update on javalab side. Added a little mapping between statuses (SNAKE_CASE) and metric names (UpperCamelCase)

@sanchitmalhotra126 @molly-moen updated this a bit to have less duplicate code, LMK what you think!


Typescript

Added new item to programming language (Typescript)

See here
Added TypeScript to the list
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.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

// @dzharii

// @dzharii

Sir @sb16072007  I appreciate your noble attempt to add this list, but we had a conversation about this with Sir @sindresorhus, whom I respect and admire for his open source efforts and with awesome moderators, where I had decided not to comply to the common guidelines for the awesome lists, so that awesome-typescript was removed from awesome-list.
Awesome-typescript will remain in the free lands of the Wild West. This issue can be closed.

Sir @sb16072007  I appreciate your noble attempt to add this list, but we had a conversation about this with Sir @sindresorhus, whom I respect and admire for his open source efforts and with awesome moderators, where I had decided not to comply to the common guidelines for the awesome lists, so that awesome-typescript was removed from awesome-list.
Awesome-typescript will remain in the free lands of the Wild West. This issue can be closed.

@sb16072007 Hi, I think according to pull request guideline you should choose a suitable title for your pull request like -> Add Typescript

@sb16072007 Hi, I think according to pull request guideline you should choose a suitable title for your pull request like -> Add Typescript

Great list, definitely love seeing some TS love in awesome land.
@sindresorhus already commented but a few pointers when I reviewed the list

You are missing the "awesome badge" in the title
In the PR description the link to the repo is linking to your fork not your awesome list
Its a pretty long list and you don't have a Table of Contents
Add the awesome-lint as a CI check https://github.com/sindresorhus/awesome-lint#continuous-integration

I didn't do an exhaustive review but those should be quick wins


BUG - [backend-proxy-middleware] Error retrieving from secure store.

Related Bug
maybe Bug #742
Description
For me this is not an error that breaks anything, but only appears in the log. This may be different for others.
I run wdi5 Tests in GitHub Actions workflows.
Since I updated UI5 Tools from 2.14.17 to 3.0.1, a error/warning appears about secure store, but the app it self still works. This only happens in Github Actions or in a Linux environment.
First example is this job under start app ordersv4fe ui5 108:
https://github.com/marianfoo/ui5-cc-excelUpload/actions/runs/4202734452/jobs/7291263259.

Next example is under the local environment with macOS M1 with Ubuntu Dev Container:

Steps to Reproduce
Steps to reproduce the behavior:
Run a UI5 App with fiori run and a fiori-tools-proxy.
Project and yaml used for this examples above is this (generated by SAP App Generator):
https://github.com/marianfoo/ui5-cc-excelUpload/blob/main/examples/packages/ordersv4fe/ui5.yaml
Expected results
No Error/Warning in Console
Actual results
Warning/Error in console
Version/Components/Environment
Add any other context about the problem here
OS: Linux

Root Cause Analysis
Problem
{describe the problem}
Fix
{describe the fix}
Why was it missed
{Some explanation why this issue might have been missed during normal development/testing cycle}
How can we avoid this
{if we don’t want to see this type of issues anymore what we should do to prevent}

These look actually like two different things.
@zdravko-georgiev could you please have a look at the first one? It what situation are we logging an error? At maximum, I would expect a warning.
@ullasholla the 2nd one is something to discuss. Should we reduce this to a single warning that the secure storage is not available and log the rest only when debugging?

Forgot to add, i fixed the first error with
https://github.com/marianfoo/ui5-cc-excelUpload/blob/2ea3c4d839a4c7afd0ce04667778a7fd4a88d458/.github/workflows/wdi5-test.yml#L31
Don't know if it helps you as I don't understand the underlying issue.
I think I can undo this in the workflow anyway because it doesn't break anything.

@marianfoo is this error still occurring to you?

no, error is not there anymore

Sorry, have to reopen because looked at Github Actions where i used the workaround.
With this workaround the error is gone

Forgot to add, i fixed the first error with https://github.com/marianfoo/ui5-cc-excelUpload/blob/2ea3c4d839a4c7afd0ce04667778a7fd4a88d458/.github/workflows/wdi5-test.yml#L31

Currently using a ubuntu docker container and the error is coming up again.
Still no effect on the app, working fine.

with this:
  "devDependencies": {
    "@sap-ux/ui5-middleware-fe-mockserver": "^2.1.117",
    "@sap/ux-specification": "^1.108.12",
    "@sap/ux-ui5-tooling": "1.10.5",
    "@ui5/cli": "3.5.0"
  },

you need anymore infos?

Hey ! I have the sam error like marianfoo (only the 2nd error )
Can someone pls help me :)


Feature: Unauthorized Access Page

The eligibility of a user to access PDA, would be better not rely only on the authentication result. Instead an early check that the user has at least one active role on PDA seems to be a common practice.
This PR implements a feature that redirects authenticated users with no active role on PDA (ie users that do not have any domain or account linked with their username) to a new template page, where they are informed they are not authorized to access this service. Additional information may be included there by the site admin.

Like the get_user_domain method of User model.
Not sure about the text of the error page, tho

Ok we changed the text, thanks for the feedback @steschuser

Minor update regarding the latest commit:
An objective of ours was to address an issue where users authenticated by some external providers were not redirected to the login page upon clicking the return link, when encountering the Template.
Furthermore, we factored in the "Allow users to create Domain/view History" features, by disabling the Template when these settings are toggled on, as we believe that they are not in line with the general philosophy of the Unauthorized Access Template.


Updated lagoon/docs/developing_lagoon/index.md docker version requirement

Docker version 17.05 was made obsolete and removed from the official Cent Os repository: https://download.docker.com/linux/centos/7/x86_64/stable/Packages/
Version 17.06.0 has a few builder bugs that are fixed in 17.06.1, and that should be the minimal recommended release:
https://docs.docker.com/v17.12/release-notes/docker-ce/#17061-ce-2017-08-15

@ion-as
awesome <3 thank you!


Replace Troy's Axe Nuget Reference with Deque

Change nutget reference of Troy's repo to dequelabs.
The NuGet package will be deprecated and a new repo will be set as the alternate package
The new Deque project will support both Selenium and Playwright
A new project (https://github.com/microsoft/html-reporter-for-axe-core-dotnet) will be used for creating HTML reports. This should provide a much better user experience than the admittedly primitive reporting currently included in Selenium.Axe

@jonreding2010 - Checking with the the reporting team to see if we can get an eta
https://github.com/microsoft/html-reporter-for-axe-core-dotnet/issues/46

@jonreding2010 - The MS HTML report is taking too long
I created this as a stopgap - https://www.nuget.org/packages/TWP.Selenium.Axe.Html/

@jonreding2010 - The MS HTML report is taking too long I created this as a stopgap - https://www.nuget.org/packages/TWP.Selenium.Axe.Html/
Sounds good! I made this issue as a reminder/placeholder for the update to the Microsoft axe reporter.

You stopgap sounds good to me

Done in last release


Javascript assets included in CSS modules are executed during build

If CSS contains Javascript assets, these are executed during build and can interfere with the build and build output.
See this repo for more information: https://github.com/darrenscerri/webpack-extract-text-plugin-empty-require-error.
Related issues:
https://github.com/webpack/webpack/issues/4541
https://github.com/webpack-contrib/css-loader/issues/462

url('') will be rewritten by to url(require('./')) by css-loader, it's an issue in css-loader tracking this an discussion moved to  #462 i'm still wondering about the 'usecase' 🙃


Error: listen EACCES <IP_ADDRESS>:80

I have encountered an error, given with the following stack trace:
$ sudo node start.js
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES <IP_ADDRESS>:80
    at Object._errnoException (util.js:1021:11)
    at _exceptionWithHostPort (util.js:1043:20)
    at Server.setupListenHandle [as _listen2] (net.js:1327:19)
    at listenInCluster (net.js:1385:12)
    at doListen (net.js:1494:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:667:11)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

I am not entirely sure what to make of it. I'm in the process of installing PegaSwitch from scratch after updating to Ubuntu Xenial on WSL.

You running Skype? If so, go to Options > Connection and turn off "Use port 80 and 443 for additional incoming connections"

I'm not even sure if I'm running Skype. But, just to make sure, I have opened Skype, went to Tools > Connection Options, unchecked "Use port 80 and 443 for additional incoming connections," quit Skype, then restart Skype, went back to Tools > Connection Options, and then verified the option has been unchecked, before quitting Skype for a second time.
The Skype Settings have been changed since the Anniversary Update to the Creator's Update. I don't know if there will be any drastic changes for the upcoming Fall Creator's Update.
Upon launching WSL, it was stuck in a state where the title would say, "Select Bash for Windows". Closing the window, as well as attempting to kill the Bash process from the Task Manager wouldn't work. I ended up pressing CTRL+C to force quit it, which worked somehow. WSL then quit normally thereafter.
I then restart WSL, and did sudo node start.js, and it still throws the following stack trace:
$ sudo node start.js
events.js:182
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES <IP_ADDRESS>:80
    at Object._errnoException (util.js:1021:11)
    at _exceptionWithHostPort (util.js:1043:20)
    at Server.setupListenHandle [as _listen2] (net.js:1327:19)
    at listenInCluster (net.js:1385:12)
    at doListen (net.js:1494:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
    at Function.Module.runMain (module.js:667:11)
    at startup (bootstrap_node.js:187:16)
    at bootstrap_node.js:608:3

Any other steps that I can try?

If you run netstat -a -b -n under a command prompt (not bash) with admin privileges I think it should show you what has port 80 bound. I can't test since I'm not running Windows right now.

Thanks, I did the following command, and I found out that AlienwareAlienFXController.exe is listening to port 80. Nothing is listening to port 443 though, so that's good.
It's a shame, but I'm not familiar with what Alienware AlienFX Controller is all about, nor have I been able to kill the process. I'll look it up, but if you have any information, please let me know.

Ok, further investigation reveals that the AlienwareAlienFXController.exe is not the only culprit. Apparently, another culprit is listening to port 80 when I killed the AlienwareAlienFXController.exe process. On Windows 10, if the user has or had enabled or used Internet Information Services in the past (IIS), there is a service called World Wide Web Publishing Service that is running locally on the machine, where it will listen to port 80.
Disabling this service will stop the service from listening to port 80. But this service must be re-enabled for IIS to work properly, if the user intends to host a website or do some web management stuffs.
Disabling this service will also make PegaSwitch work correctly, and no longer throws an exception on not being able to listen to port 80. That's all.
This resolves my issue, and therefore I will be closing this. Thanks.


Suggestion: put libXSLT under optionalDependencies

With https://github.com/enketo/enketo-transformer/pull/178, we added Python and Cpp toolchain to the listed requirements because in an environment without them, the npm install will fail on libxslt.
I realized this is counterintuitive though -- if someone only wants to use client-side transformation, they shouldn't need the native libraries.
As an optional dependency, Node would try to install libxslt, but if that failed it would still continue installing the rest of the packages. https://docs.npmjs.com/cli/v9/configuring-npm/package-json#optionaldependencies

This would especially help anyone using Apple SoCs (who I'm assuming are still affected by https://github.com/enketo/enketo-transformer/issues/176). This would at least let them set up client-side transformation


Added Ukrainian language and fixed custom list highlight bug

Added Ukrainian language;
Fixed custom list rendering problem when row was not highlighted if its index was above the number that can be displayed on the display at the same time

Don't worry, I'll manually apply the changes as best I can in the next day or so.
Thanks for the PR.

manually merged to master branch today.

Thank you! I'm sorry for not getting back to you sooner.
Thank you for such a great library!


Substitution not working or sending custom data

Issue Summary
I'm trying to use the substitution option with a transactional email template, the email is getting sent but the custom data for the substitution is not.
Here is my code
var helper = require('sendgrid').mail;
    var from_email = new helper.Email(from);
    var to_email = new helper.Email(to);
    var subject = 'New Mentorloop notification';
    var content = new helper.Content('text/html', text);
    var mail = new helper.Mail(from_email, subject, to_email, content);
    mail.setTemplateId("ea4f8a70-f487-49a3-b0ee-60b5848921e8");

    var personalization = new helper.Personalization();
    personalization.addTo( new helper.Email( from ) );
    var substitution = new helper.Substitution("%text%", "Example User");
    personalization.addSubstitution(substitution);
    mail.addPersonalization(personalization);

    var request = sendgrid.emptyRequest({
      method: 'POST',
      path: '/v3/mail/send',
      body: mail.toJSON()
    });

    sendgrid.API(request, function(error, response) {
      console.log(response.statusCode);
      console.log(response.body);
      console.log(response.headers);
    });

Technical details:

sendgrid-nodejs Version: lastest version
Node.js Version: v4.7.0

Got it working, keep this up for anyone else that might run into. I had two issues

personalization.addTo( new helper.Email( from ) ); should have been  personalization.addTo( new helper.Email(to));

Assigning incorrect email

var substitution = new helper.Substitution("%text%", "Example User");

It seems text is already being used

Thanks for circling back @AlmogRnD!
Glad you got things working. Please let us know if there is anything else we can help with.


Back WeakDictionary with NSMapTable

I was toying with the idea of backing the WeakDictionary with NSMapTable, and it seems to be working. Unfortunately, I'm running into this problem with NSMapTable, and at this point, I'm starting to wonder if maybe NSMapTable is just broken 🤔
Any ideas? 😄

Okay, so this was actually expected behavior, and the values are released as soon as the current autorelease pool is. I reworked and polished my approach, and I think it works quite well now!
It still seems like there is a quirk with how valuesRetainedByKey works together with NSMapTable, need to throw an extra pair of 👀 on that. I thought that just doing valueOptions: valuesRetainedByKey ? .strongMemory : .weakMemory would work, but maybe not 🤔
Most of the tests are currently failing because it expects a) it expects .count to reflect unreaped nil references, and b) it expects values to be released immediately.
I have some local changes that make almost all tests pass, by sprinkling autoreleasepool and changing counts in the tests 😄 It could potentially be worth just rewriting the tests since they mostly seems to focus on the reaping, which isn't there anymore...
I'll push a commit with the semi-passing tests soon.
@nicholascross In general, how do you feel about this approach?

@LinusU Thanks Linus, I will take a look at this PR tonight.

I remember having similar thoughts at some point but TBH it has been a long time since I thought about it.  This article from back in the day highlights some of the pitfalls with NSMapTable not sure if it still holds true.
In some respects you could draw similarities between intermittent reaping and draining of the autorelease pool.
Whilst I appreciate you are making an easier to use API by removing the need to reap orphaned references adding the NSMapTable backing storage goes against the unstated goals I had with this library.

It should be 100% swift
It should ideally not rely on Objective-C foundation

Maybe it is worth considering though, what your goal is.
You want auto reaped references that NSMapTable provides plus potentially some of the difference mentioned here?

Use of equality operator for key comparison
Supports suscripts and Collection protocol inherited behavior
Keys can optionally retain values as long as the key itself is retained the associated value can be retained
Manual nil reference clean up required. Weak references are reclaimed as normal but container objects are left holding nil references until reaping is triggered

Would it be possible to extend or wrap NSMapTable with only the feature you are after?


Removed Versioneye badge

Updated dependencies
Removed abandoned Versioneye badge from README
Added additional documentation to HttpMessageBuilder

Coverage remained the same at 96.491% when pulling fec8819970b02cf6b1f4e85bbf1b7256008c31b6 on feature/composer-update into 95fa8b3b50d62b3e451a17686b9f5f81a09c3e08 on master.

Coverage remained the same at 96.491% when pulling fec8819970b02cf6b1f4e85bbf1b7256008c31b6 on feature/composer-update into 95fa8b3b50d62b3e451a17686b9f5f81a09c3e08 on master.


CCE Turbo Clusters and CCE Clusters

Issue on page: "CCE Turbo Clusters and CCE Clusters"

Source: https://github.com/opentelekomcloud-docs/cloud-container-engine/blob/main/umn/source/clusters/cluster_overview/cce_turbo_clusters_and_cce_clusters.rst

Rendered: https://docs.otc.t-systems.com/cloud-container-engine/umn/clusters/cluster_overview/cce_turbo_clusters_and_cce_clusters.html

There is a link or statement missing the pricing difference. If there are none, please add an according statement.

The CCE Turbo has not been released as General Available version yet. The official GA version will be announced soon together with billing details. Pricing information is not part of the UMN, but Price Calculator (where CCE Turbo info may be added). At the moment, the price of the CCE Turbo clusters equals to CCE clusters.
Thank you for your remark based on which we will improve this pricing information.

[OTCPR-14805]

As mentioned already, no pricing info has place in the UMN, but the Price calculator - already updated with the turbo.
Thanks for notice.


hal: nrf-regtool: Use sysbuild to merge UICRs

Use sysbuild functionalities to merge UICRs with local domain firmware.
Ref: NCSDK-NONE

After some thought - it'd be better if the ncs_merge_file was capable of handling HEX files merged using runners_yaml_props_target override instead.


Dependency vs Dependencies

Hi, @kmantel, with conditions on graph-scheduler, I noticed a difference in function arguments. There is the use of dependencies vs dependency, both of them work, which argument should be used uniformly across the board?
I've also been trying to run Threshold conditions locally, I started with the simple example you had in a Recent PR. However, this error is getting thrown whenever I create a termination condition with a threshold condition.
ValueError: No param_A evaluable object for Node(metadata=None, id='A', input_ports=[InputPort(metadata=None, id='input_port1', shape=None, type=None)],
functions=[], parameters=[Parameter(metadata=None, id='param_A', value='param_A + 1', default_initial_value=0, time_derivative=None, function=None, args=None, conditions=[])],
output_ports=[OutputPort(metadata=None, id='output_1', value='param_A', shape=None, type=None)]), options: ['input_port1', 'param_A', 'output_1']```

For conditions outside of mdf.Condition, dependencies is used when there are multiple accepted arguments as in Any, while dependency is used when there is only one argument as in Threshold. But for mdf.Conditions, there was a preference to use dependencies everywhere. In order not to break the interface in graph-scheduler, I added a parser to change  dependencies to dependency internally where necessary: https://github.com/ModECI/MDF/blob/8a89c2f8356c5c982e9c287f9a5b521eaaf06b8d/src/modeci_mdf/execution_engine.py#L1183-L1195
The error should be fixed now on main as of #280, that failure was hidden during merge due to CI issues

For conditions outside of mdf.Condition, dependencies is used when there are multiple accepted arguments as in Any, while dependency is used when there is only one argument as in Threshold. But for mdf.Conditions, there was a preference to use dependencies everywhere. In order not to break the interface in graph-scheduler, I added a parser to change dependencies to dependency internally where necessary:
https://github.com/ModECI/MDF/blob/8a89c2f8356c5c982e9c287f9a5b521eaaf06b8d/src/modeci_mdf/execution_engine.py#L1183-L1195
The ValueError with Threshold should be fixed now on main as of #280, that failure was hidden during merge due to CI issues

This clears up the confusion on my part. @pgleeson


[Task - Server]: Pause CRON API

Hey team! Please add your planning poker estimate with Zenhub @nsarupr @srix


fixing typo in gitops-with-meshery page

Notes for Reviewers

This PR fixes #12983

Signed commits

[x] Yes, I signed my commits.

🚀 Preview for commit d856dc7efa063ef1297af5396f1753004a92b490 at: https://676a9a1f872b50b6f7b91a8c--meshery-docs-preview.netlify.app

This PR has been combined into #13000


feat: SetWebhookUtil component

It would be awesome to have a tiny utility component which can be included in all the hosting guides which require a webhook to be set. While it is not hard for many users to correctly set the webhook URL using curl or other tools, some beginners struggle with understanding which URL to fetch.
It would be nice to have a small interactive component on the website which lets users paste their token and URL and then it will set the webhook for them. It could also get some neat information to validate the info:

Call getMe with the token to confirm the bot name
Pass the URL to the URL constructor to validate the URL
Display information from getWebhookInfo so that there is an easy way to confirm that things are working correctly
Provide a tooltip that explains that the bot token will never be used for anything else than setting for this component to function, and tell users to never give away their token to anyone, no matter how polite a website asks.
Have a link that opens the chat with the new bot in a new tab so that users can easily head over to Telegram when the webhook was set and the bot is working.
Perhaps have a second button to delete the webhook again? This might not be necessary, but it could be that it feels more natural to have it. Sometimes people feel the urge to clean up after themselves.
Perhaps store the token locally in the browser so that it persists across page loads? We must not do this if it feels shady, I don't want anyone to believe we store the token server-side (even though we will never do this)

I’ve had this idea before, it would be really useful
This website inspired me: resetbot.com
One more idea: ability to pass placeholders via query params. For example, example.com/?url=<project_name>.deno.dev would open a page with deno.dev part filled in
Templates with custom arguments would be great too, but it is not trivial to implement