Fix flaky test testSendCorruptBytesToReplica

Description
This test is failing with WindowsFS.
This change moves SegRep corruption tests to a separate IT class and skips running on WindowsFS.
Related Issues
Resolves https://github.com/opensearch-project/OpenSearch/issues/10542
Resolves https://github.com/opensearch-project/OpenSearch/issues/10709
Check List

[x] New functionality includes testing.

[x] All tests pass

[ ] ~New functionality has been documented.~

[ ] ~New functionality has javadoc added~

[ ] ~Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)~
[x] Commits are signed per the DCO using --signoff
[ ] ~Commit changes are listed out in CHANGELOG.md file (See: Changelog)~
[ ] ~Public documentation issue/PR created~

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28933/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/10899

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28935/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/10899 again

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28938/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/10885

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28939/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/10902

#10902

https://github.com/opensearch-project/OpenSearch/issues/10902

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28946/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

https://github.com/opensearch-project/OpenSearch/issues/10903

Gradle Check (Jenkins) Run Completed with:

RESULT: FAILURE ❌
URL: https://build.ci.opensearch.org/job/gradle-check/28951/
CommitID: 91bd1e9
Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
Is the failure a flaky test unrelated to your change?

....another one https://github.com/opensearch-project/OpenSearch/issues/10899


How can I use Microsoft.AspNetCore.Mvc.Internal.ActionSelector in ASP.NET Core 3.0/.NET Core 3.0 or alternative solution in Core 3.0?

From @Microshaoft on Friday, September 27, 2019 7:04:36 AM
reference MSDN:
https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.mvc.internal.actionselector?view=aspnetcore-2.2
c# code in .NET Core 2.2, for your reference:
https://github.com/Microshaoft/Microshaoft.Common.Utilities.Net.4x/blob/aace0a952433f09d24d5977ad7fae7adf40a18d4/CommonUtilities.Shared/WebApi.Common.Controllers/SyncAsyncActionSelector.cs#L8
Copied from original issue: dotnet/corefx#41381

@Microshaoft the type was made internal as was announced in https://github.com/aspnet/Announcements/issues/326. If you'd like direct parity, I would recommend copying the code in your application - https://github.com/aspnet/AspNetCore/blob/release/3.0/src/Mvc/Mvc.Core/src/Infrastructure/ActionSelector.cs.
I'm having a hard time following your customization in the code that you pointed out, but  I suspect you could use an ActionConstraint to influence action selection. Have a look at https://github.com/aspnet/AspNetCore/blob/release/2.2/src/Mvc/Mvc.WebApiCompatShim/src/OverloadActionConstraint.cs#L21, it's fairly likely something like this would be enough rather than plugging in a custom selector.

@pranavkm both ActionConstraint  and ActionSelector are NOT Supported in ASP.NET Core 3.0.
I want control the request be routed one WebApi Controller action method, when I set same one [Route("XXXX")] to multiple method, such as one method is Sync , another method is Async, and then I want use Custom ActionSelector to control select Sync or Async version method, these two method are almost same, except Async/Sync.
Sync method ProcessActionRequest:
https://github.com/Microshaoft/Microshaoft.Common.Utilities.Net.4x/blob/cc425887db5a8bbfad9e07ae4d2ea6948a31bf03/CommonUtilities.Shared/WebApi.Common.Controllers/StoreProcedureExecutorController/AbstractStoreProcedureExecutorControllerBase.3.NET.Core.Standard.cs#L225
Async method ProcessActionRequestAsync:
https://github.com/Microshaoft/Microshaoft.Common.Utilities.Net.4x/blob/cc425887db5a8bbfad9e07ae4d2ea6948a31bf03/CommonUtilities.Shared/WebApi.Common.Controllers/StoreProcedureExecutorController/AbstractStoreProcedureExecutorControllerBase.3.NET.Core.Standard.cs#L323
the above two methods use same route attribute:
#if !NETCOREAPP3_X
        [HttpDelete]
        [HttpGet]
        [HttpHead]
        [HttpOptions]
        [HttpPatch]
        [HttpPost]
        [HttpPut]
        [
            Route
                (
                    "{routeName}/"
                    + "{resultJsonPathPart1?}/"
                    + "{resultJsonPathPart2?}/"
                    + "{resultJsonPathPart3?}/"
                    + "{resultJsonPathPart4?}/"
                    + "{resultJsonPathPart5?}/"
                    + "{resultJsonPathPart6?}"
                )
        ]
        [
            Route
                (
                    "export/{routeName}/"
                    + "{resultJsonPathPart1?}/"
                    + "{resultJsonPathPart2?}/"
                    + "{resultJsonPathPart3?}/"
                    + "{resultJsonPathPart4?}/"
                    + "{resultJsonPathPart5?}/"
                    + "{resultJsonPathPart6?}"
                )
        ]
#endif

would you give more help? @pranavkm

@pranavkm  @mkArtakMSFT thanks for your feedback. Will you plan to migrate it to . Net Core 3.x recently?

No plans to do this in 3.1 timeframe.

how about postponed plan or not at all ? @mkArtakMSFT

@pranavkm @mkArtakMSFT after .NET Core 3.1 released, when will the feature be back?

with @pranavkm help and tips
I have implemented the feature of Sync or Async action selection by using custom ActionConstraint, custom ApplicationModelProvider, custom RouteAttribute.
https://github.com/Microshaoft/Microshaoft.Common.Utilities.Net.4x/tree/master/CommonUtilities.Shared/WebApi.Common.Controllers/Constraint
https://github.com/Microshaoft/Microshaoft.Common.Utilities.Net.4x/blob/86f7822e359e25e85bbf79df5af53d51aa85690b/Samples/MsSqlCodeDiffVersioning/MsSqlCodeDiffVersioning.Shared/Startup.cs#L83
thanks @pranavkm


python310Packages.pyunifiprotect: 4.2.0 -> 4.3.3

Description of changes
https://github.com/AngellusMortis/pyunifiprotect/releases/

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 192898 run on x86_64-linux 1

6 packages failed to build:

python310Packages.spacy
python310Packages.spacy-transformers
python310Packages.textacy
python39Packages.spacy
python39Packages.spacy-transformers
python39Packages.textacy

21 packages built:

home-assistant-component-tests.unifiprotect
markdown-anki-decks
napari (python310Packages.napari)
python310Packages.authcaptureproxy
python310Packages.coinmetrics-api-client
python310Packages.napari-npe2
python310Packages.pathy
python310Packages.pyunifiprotect
rstcheck (python310Packages.rstcheck)
python310Packages.teslajsonpy
python310Packages.typer
python39Packages.authcaptureproxy
python39Packages.coinmetrics-api-client
python39Packages.napari
python39Packages.napari-npe2
python39Packages.pathy
python39Packages.pyunifiprotect
python39Packages.rstcheck
python39Packages.teslajsonpy
python39Packages.typer
unifi-protect-backup


Need @ignore/@exclude tag provision for spec files

Is your feature request related to a problem? Please describe.
@ignore/@exclude tags should be provided to ignore the set of scenarios in Specmatic.
Describe the solution you'd like
@ignore/@exclude tags should be supported to ignore the scenarios in the spec file.

Hi @nidhi-tomar93, can you let us know why you would like this feature? How will this be useful to you?

We have since moved away from the Gherkin based syntax to industry standard API specifications like OpenAPI, AsyncAPI, etc. which we now treat as API contracts. Please do watch our latest conference videos for more details. Closing this issue for now, please feel free to reopen if required.


Fix Rubocop lint issue, bump gem version for new release

With https://github.com/esigler/lita-dig/pull/2 & https://github.com/esigler/lita-dig/pull/3 in, it's time for a new release!

Coverage remained the same at 100.0% when pulling 5c366aff991ad35f914986ddcecdded5f008bd54 on fix_and_release into d8d812e3b8cd4a60f836fb7ac4b2073e6fa082b5 on master.


Remove duplicate lock-file

One should only use either npm or yarn, and not both. As such I remove the package-lock.json file thats only used by npm.

Hey @TheKnarf! Thanks for your interest in Bluefish and for contributing these PRs. Our development on Bluefish has moved to https://github.com/bluefishjs/bluefish, and I'm archiving this repo.
We'd absolutely welcome new issues and PRs to that repo! Thanks


Spot Margin Research

Start research on spot margin trade
┆Issue is synchronized with this Clickup task by Unito

@rapcmia From my understanding, this is not an Issue


Registering a new _domain

Hello,
I have read the whole documentation, smart contracts code and interaction code. I am very impressed by the solution that is being built. Circle is going to significantly improve stablecoin access on blockchains and increase the strengh of USDC.
From my understanding, if a Blockchain wants to start integrating the devnet mint/burn bridge of Circle, it needs a few actions from Circle:

for integrating the Ethereum -> Blockchain devnet bridge, the Blockchain needs to be associated a _domain in the remoteTokenMessengers storage of TokenMessenger.sol,

for integrating the Blockchain -> Ethereum devnet bridge, the Blockchain needs either that Circle attesters work with the Blockchain or that Circle whitelists the attesters made by the Blockchain, in the enabledAttesters storage of MessageTransmitter.sol.

How to register a new _domain in the remoteTokenMessengers storage of TokenMessenger.sol? This way, the Blockchain could already start the integration of the Ethereum -> Blockchain devnet bridge.

Hi @lcswillems,
Your assessment is correct. For the time being, we aren't registering new domains in Circle-deployed CCTP contracts, or attesting to new domains in Circle's attester. But, more domains will be added over time. You can certainly deploy the contracts yourself, and run your own attester. We hope to eventually make this process easier. Thanks!


Dict() inconsistent with dict() initialization

I noticed this when trying to use with xmldict (https://github.com/martinblech/xmltodict). Sometimes a plain value becomes a list, with the first element an empty dict and the value in the second element:
>>> xml = "<root><x>1</x></root>"
>>> xmltodict.parse(xml, dict_constructor=dict)
{'root': {'x': '1'}}
>>> xmltodict.parse(xml, dict_constructor=addict.Dict)
{'root': [{}, {'x': [{}, '1']}]}

I don't know how xmltodict calls the constructor, but there is obviously something that is not processed in the same way.

After some digging, it looks like it is caused by the __missing__ method returning Dict() when key is not found.
I see, this is to enable stuff like
body = Dict()
body.query.filtered.query.match.description = 'addictive'

but there should be a caveat in the documentation. Or maybe opt-in functionality (Dict and DefaultDict classes for example).

Yeah, that doesn't look right!
One thing you could do is is Dict(xmltodict.parse(xml, dict_constructor=dict)), however feel free to PR some lines into the README.

See also https://github.com/martinblech/xmltodict/pull/256, to fix the other end

Thanks!


ERROR: Your adapter can not be a station (i.e. be connected) and an AP at the same time

This error states that my Wireless Card doesnt support creating hotspot while being connected .Right?
But in Windows I am able to do the same without any issue .
even app in windows like Maryfi works which supposedly creates a wifi station (Hotspot)  while being Connected.
my wireless card supports following Mode-
Supported interface modes:
* IBSS
* managed
* AP
* AP/VLAN
* monitor
* mesh point
* P2P-client
* P2P-GO
So can someone enlight me , where i am wrong or what i am missing?
Thanks in Advance.

What wireless device and Linux driver are you using?
Run iw phy | grep -iC3 combinations. If it doesn't show an interface combination that can do "managed" and "AP" simultaneously, then — from the perspective of your driver — your adapter cannot do both simultaneously.
$ iw phy | grep -iC3 combinations
        software interface modes (can always be added):
                 * AP/VLAN
                 * monitor
        valid interface combinations:
                 * #{ managed } <= 2, #{ AP, mesh point, P2P-client, P2P-GO } <= 2, #{ P2P-device } <= 1,
                   total <= 4, #channels <= 1
                 * #{ managed } <= 2, #{ P2P-client } <= 2, #{ AP, mesh point, P2P-GO } <= 1, #{ P2P-device } <= 1,


Definition - Stress the IFTA with mocked VIM

Stress the IFTA deploying simultaneous NS, try to identify the maximum of simultaneous deployments that the IFTA can perform.

The use of Mock VIMs to test the API performance of the IA is definitely feasible.
We just need an estimation of the actual call time of real deployment, so to embed some kind of wait into the relevant calls of the mock VIM wrappers. A fast measurement of these data can be easily done.
Once we have this, we need the SP to be deployed and configured with a topology composed just by mock VIMs and WIM. Some questions arise:

Is this a separate deployment of the SP?
Are we changing the SP configuration in every test, or are we relying on the same SP instance to run all the tests?


Extend Get-NavContainers with additional information

Additional information returned from Get-NavContainers.ps1 would be nice.
Suggestion:
Return a set of object with additional information about the containers.

ContainerName
ContainerVersion
ContainerState (Running/Stopped/...)
Nav/BC Version numbers
Other relevant infomations

Added a parameter: -includelabels, which includes labels

Fixed in <IP_ADDRESS>


increase current work in progress version to 5.9

Starting the client with verbose mode will make CodeChecker version output a tainted git tag v5.8.0-123-g1234567 showing that the current build was created with changes above 5.8.0.
Doesn't introducing this change create a confusion, as in this state, 5.9.0 is used for all version strings, including the verbose "taint" string too?

With this release we will change when the version is updated.
In the current case we released v5.8 and we are working on v5.9 the version info will reflect that. Until v5.9 is not released we assume this is not a stable release.
If the users build a package from the master branch it will indicate that this version is ahead of the latest released version.
I do not think it will be too much confusing. The taint tag will show what is the latest commit and v5.9 will show that this is the version we are working now.

Actually, upon further thinking into it, the taint tag will still show v5.8.0-NUMBER-gSHA, because the latest git tag available in the repository is still v5.8. 🙂

Ok, than this needs to be changed later. So not the latest git tag is used as the version.

It only shows in --verbose debug mode. In "normal" modes, the API-given version is used.

I've created a separate issue to change the printed version so it will be consistent everywhere.


Adding a swap button for quickplay and sprint builder

the button was surprisingly annoying to add, but it is here

on mobile:

Awesome, this will make my life a lot easier when adding prompts! I think the only thing is the mobile UI. Maybe have it be vertically in-between instead of smushing the end article. Or just not show it at all for mobile if it's too complicated.

Removed swap button for mobile.

oops added commits to the wrong branch. Reverted

LGTM


updated routes/api and new field in table schema

Closing this and deleting the branch - this was covered by #39


LSP error when file path begins with //

When I open Doom it starts from the path // (filesystem root, with double slashes for some reason)

if then I open some file, it causes an error in LSP mode

If I restart the editor using SPC q r, it will restart in the user home folder

and in this case, there is no error.
That seems to be a bug.

I'm experiencing something similar. I'm also on macos.

Can you post your doom info report?

When I open Doom it starts from the path // (filesystem root, with double slashes for some reason)

Sounds like an issue with the method you're using to launch emacs. Please include your M-x doom/info and some steps to reproduce. In the future please do not ignore our issue template.

@hlissner I reinstalled doom and now can't reproduce the issue (steps are simple, just open doom). But I'm not the only one who experienced this issue.
Here is my doom/info:

```
SYSTEM  type       darwin
        config     x86_64-apple-darwin19.6.0
        shell      /bin/zsh
        uname      Darwin 20.1.0 Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64 x86_64
        path       (/var/folders/1t/d2tthcgx6pqd831qg5nbc5vm0000gn/T/fnm_multishell_40948_1605426778958/bin ~/.cargo/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin /Library/Apple/usr/bin<EMAIL_ADDRESS>~/.gem/ruby/2.6.0/bin ~/Library/Android/sdk/emulator ~/.cargo/bin /usr/local/sbin ~/.config/doom.d/bin ~/.fzf/bin<EMAIL_ADDRESS>EMACS   dir        ~/Dropbox/appdata/.config/doom.d/
        version    27.1.50
        build      Nov 10, 2020
        buildopts  --disable-dependency-tracking --disable-silent-rules --enable-locallisppath=/usr/local/share/emacs/site-lisp --infodir=/usr/local/Cellar/emacs-plus@27/HEAD-109eb1e/share/info/emacs --prefix=/usr/local/Cellar/emacs-plus@27/HEAD-109eb1e --with-xml2 --with-gnutls --without-dbus --with-imagemagick --with-modules --with-rsvg --with-ns --disable-ns-self-contained
        features   RSVG IMAGEMAGICK GLIB NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS JSON PDUMPER LCMS2 GMP
        traits     (gui server-running chemacs envvar-file)
DOOM    dir        ~/Dropbox/appdata/.config/doom/
        version    2.0.9
        font       #
        theme      doom-one
        build      HEAD -> develop aa02dc14a 2020-11-14 18:42:31 -0500
        elc-files  0
        modules    (:completion company ivy :ui doom doom-dashboard doom-quit hl-todo ligatures minimap modeline ophints (popup +defaults) treemacs vc-gutter vi-tilde-fringe workspaces :editor (evil +everywhere) file-templates fold (format +onsave) snippets :emacs dired electric undo vc :term vterm :checkers syntax :tools (eval +overlay) lookup lsp magit :os macos :lang emacs-lisp (json +lsp) (javascript +lsp) markdown org rest sh (web +lsp) yaml :config (default +bindings +smartparens))
        packages   (n/a)
        unpin      (n/a)
        elpa       (n/a)
```

I am still experiencing weird issues with the path being // on boot. Here's my doom info:
SYSTEM  type       darwin
	config     x86_64-apple-darwin18.7.0
	shell      /bin/zsh
	uname      Darwin 19.6.0 Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6<IP_ADDRESS>~1/RELEASE_X86_64 x86_64
	path       (~/.local/venv/bin ~/.cabal/bin ~/.ghcup/bin /usr/local/opt/llvm@6/bin /usr/local/opt/sqlite/bin /usr/local/bin /usr/bin /bin /usr/sbin /sbin /opt/X11/bin ~/.local/bin ~/.cargo/bin ~/.fzf/bin /Applications/Emacs.app/Contents/MacOS/bin-x86_64-10_14 /Applications/Emacs.app/Contents/MacOS/libexec-x86_64-10_14 /Applications/Emacs.app/Contents/MacOS/libexec /Applications/Emacs.app/Contents/MacOS/bin)
EMACS   dir        ~/.emacs.d/
	version    27.1
	build      Aug 12, 2020
	buildopts  --with-ns '--enable-locallisppath=/Library/Application Support/Emacs/${version}/site-lisp:/Library/Application Support/Emacs/site-lisp' --with-modules
	features   NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS NS MODULES THREADS JSON PDUMPER
	traits     (batch envvar-file)
DOOM    dir        ~/.doom.d/
	version    2.0.9
	build      HEAD -> develop 92c9127b8 2020-11-07 00:20:07 -0500
	elc-files  0
	modules    (:completion company (ivy +fuzzy +prescient) :ui doom doom-dashboard hl-todo modeline ophints (popup +defaults) treemacs vc-gutter vi-tilde-fringe :editor (evil +everywhere) file-templates snippets :emacs dired electric ibuffer undo vc :term eshell vterm :checkers syntax :tools ansible (eval +overlay) lookup (lsp +peek) (magit +forge) terraform :os macos :lang cc data emacs-lisp (haskell +lsp) json (javascript +lsp) markdown (org +gnuplot +pandoc) python sh web yaml :config (default +bindings))
	packages   ((rg) (ix) (dash-at-point) (vagrant-tramp) (logstash-conf) (exec-path-from-shell) (haskell-snippets) (ormolu) (dhall-mode) (bazel-mode))
	unpin      (n/a)
	elpa       (n/a)

Btw, I noticed that if I start doom on the commandline (GUI or -nw), it seems fine. If I start GUI doom (as a client connecting to a server or just standalone GUI), then Doom starts in //.

@wraithm

Btw, I noticed that if I start doom on the commandline (GUI or -nw), it seems fine. If I start GUI doom (as a client connecting to a server or just standalone GUI), then Doom starts in //.

Hmm, I know that if you start Emacs from the Emacs.app in the application menu (haven't used MacOS in a while so sorry if something is wrong here) it's isolated somewhat. Maybe this is a byproduct of that?

It seems like a change from emacs26 -> emacs27, and not related at all to doom.
I found this https://github.com/d12frosted/homebrew-emacs-plus/issues/220 which led me to this: https://lists.gnu.org/archive/html/help-gnu-emacs/2020-04/msg00232.html.
I'm not sure what proper solution is, but
(setq default-directory "~/")

in config seems to do the trick.

@tam5 Thanks! That fixed my issue.
@hlissner Maybe Doom should do (setq default-directory "~/") in Emacs if the version is 27 and on macOS?

This issue stems from the fact that some builds of Emacs (on macOS) will launch Emacs in an isolated environment, where the "current working directory" is / or //. Emacs (and Doom) are working as intended here, by setting default-directory to the directory Emacs was started from. That it wasn't started from the directory you are expecting I consider a bug with the method being used to launch it.
Setting default-directory in your private config is an acceptable workaround, but not an acceptable solution upstream, because it interferes with folks with sane launchers, that want to open Emacs "from" a directory. This especially harms terminal users.
Since this isn't a Doom issue I will close this issue.

Awesome! Thanks. Keep up the great work! I absolutely love Doom.


change black to #333333

is this a global change?

yeah the soft black will be easier on the eyes


Colors to css variables codemod does not transform types

Relevant code
When running the colors-to-css-vars codemod it is not transforming the usages of Colors as a type.
Before
import { Colors } from '@freenow/wave'

interface LabelVariant {
    color?: Colors
    background?: Colors
    border?: Colors
}

After
interface LabelVariant {
    color?: Colors
    background?: Colors
    border?: Colors
}

What was expected to happen?
The codemod should transform the Colors type to string.
After should look like
interface LabelVariant {
    color?: string
    background?: string
    border?: string
}

I think we should enforce tokens there, after the migration:
interface LabelVariant {
    color?: ReadCssColorVariable
    background?: string
    border?: string
}


Don't call opflow methods on non-OperatorBase objects

This PR checks in some places that elements of opflow expressions are of type OperatorBase before calling the method eval or substituting parameters. This allows, for example, numbers to be passed through. This is useful since some opflow expressions are reduced to numbers.
Closes #5992

I pushed another commit to this PR that checks that the elements of the ListOp are of valid types at construction time.
The main reason for this change is that now when an error is raised, the second call in the stack shows where the ListOp was constructed. Without this change it does not appear in the stack trace. In discussions (out of band) of bugs related to this PR, that information would have been useful.
However, it has the side effect of restricting the semantics of ListOp. This is something we may want to do anyway. Rather than allow anything-goes, widen the allowed types if the need arises.

I'm closing this in favor of #6023, which is less disruptive.


Update docs and implementation

I have some trouble getting started with node-worker-pool. I found that the README deviates from the implementation and that the implementation expects a non-standard promise implementation.
While I seems to be able to communicate with the worker now, after a while I'm getting this error, but I haven't found out why yet:
/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:23
  child.stderr.setEncoding('utf8');
              ^
TypeError: Cannot read property 'setEncoding' of undefined
    at new Worker (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:23:15)
    at WorkerPool._bootNewWorker (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:29:16)
    at WorkerPool._eagerBootAllWorkers (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:4
0:10)
    at new WorkerPool (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:23:10)
    at Object.<anonymous> (/Users/fkling/Dropbox/projects/jsnetworkx/node/_internals/delegate.js:26:18)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:84
    throw new Error(
          ^
Error: Worker process exited before it could be initialized! exit code: 1, exit signal: null
stderr:
  /Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:23
  child.stderr.setEncoding('utf8');
              ^
TypeError: Cannot read property 'setEncoding' of undefined
    at new Worker (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:23:15)
    at WorkerPool._bootNewWorker (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:29:16)
    at WorkerPool._eagerBootAllWorkers (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:4
0:10)
    at new WorkerPool (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/WorkerPool.js:23:10)
    at Object.<anonymous> (/Users/fkling/Dropbox/projects/jsnetworkx/node/_internals/delegate.js:26:18)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)

    at Worker._onChildExit (/Users/fkling/Dropbox/projects/jsnetworkx/node_modules/node-worker-pool/Worker.js:84:11)
    at ChildProcess.emit (events.js:110:17)

I will update the PR if needed, if I can resolve this issue.

Another change I would suggest in the example is that shutDown() is no longer a function


Add debug info to get vm requests

When getting VM info, include some debug info. At least which host it is on, perhaps more?

fixed in https://github.com/kthcloud/go-deploy/pull/307


Added APIM_WORKFLOW.siddhi

Added APIM_WORKFLOW.siddhi to apim-analytics-feature

@shilmyhasan In future commits, please limit the commit message to 50 character. We follow this guideline https://chris.beams.io/posts/git-commit/


failed export for Ethiopia

Tried to export country level - both for Uganda and Ethiopia degradation from 1990 to 2019 to a GEE asset. The export completed but the asset has no data inside - just NAs

Update - tried for shorter time frame - between 2014 - 2015 and it worked for both. I guess it's the date range that made it fail? What years is the degradation data available for?

degradation starts in 1982 so there something else that goes wrong here. The app was previously out of my reach but I'm going to refactor it a bit to make it work (it's currently not displaying anything). I hope it will solve this issue along the way


fix dashboard-uri

Fix #2165 , the config migration tool was assigning wrong dashboard port, fix it.

Coverage decreased (-0.01%) to 52.606% when pulling 30b23fe91b30f0e338691c5af47e662841c71f5d on hao/fix_dashboard_uri into 8afa0eb76a449eb98ea1623f9199964a6291a4ae on master.


Create /xy command

We'd like to add a command to address the "XY Problem". Make the associated message friendly and/or funny, and link to the xyproblem.info. We want something similar to our /question command.
Completion Criteria:

[ ] a new command triggered by /xy with a "fun" message that links to the the XY Problem website
[ ] unit tests and snapshot tests for the new command (please use the /question tests in help.test.js as a reference)
[ ] all tests pass

I direct people to that link every so often, I'd be happy to knock this out.

Thanks!

Closed by #129


Multiple Service processes

Hi all,
Having an issue whereby multiple processes are spawned from the service definitions created by the cookbook. It seems to be new behaviour although, confusingly your version hasn't changed since we started using Telegraf. Some more info:
service definition:
[Unit]
Description=The plugin-driven server agent for reporting metrics into InfluxDB
Documentation=https://github.com/influxdata/telegraf
After=network.target

[Service]
EnvironmentFile=-/etc/default/telegraf
User=micro
ExecStart=/usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d ${TELEGRAF_OPTS}
ExecReload=/bin/kill -HUP $MAINPID
Restart=on-failure
KillMode=process

[Install]
WantedBy=multi-user.target
Alias=telegraf.service

systemctl output:
telegraf.service - The plugin-driven server agent for reporting metrics into InfluxDB
   Loaded: loaded (/usr/lib/systemd/system/telegraf.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2016-06-30 14:41:02 UTC; 1 weeks 3 days ago
     Docs: https://github.com/influxdata/telegraf
 Main PID: 16983 (telegraf)
   CGroup: /system.slice/telegraf.service
           ├─15459 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d
           └─16983 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d

ps output:
dkitchen  2268  0.0  0.0 112648   968 pts/0    S+   13:05   0:00 grep --color=auto telegraf
telegraf 15459  0.1  0.3<PHONE_NUMBER>8 ?        Sl   Jun30  27:37 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d
micro    16983  1.9  0.3<PHONE_NUMBER>6 ?        Ssl  Jun30 300:00 /usr/bin/telegraf -config /etc/telegraf/telegraf.conf -config-directory /etc/telegraf/telegraf.d

In some cases this is harmless but in some cases it seems to first spawn a 'zombie' process. When the second one comes up it cannot bind the port and we get no metrics. You guys have any ideas what could cause this?

Upon further investigation it seems like an error in how we are using the cookbook. It seems we are accidentally spawning a second process by messing around with the service def. Will find out for sure and will close if unneeded.

Thanks @Dan-Kitchen - let us know!

Hi guys,
Apologies it seems it is not an issue with you guys, but the latest Telegraf version 0.13.1. It seems this version was released with a bug which causes multiple zombie processes when telegraf spins up. There was a fix a day after 0.13.1 but there is yet to be another release, see: https://github.com/influxdata/telegraf/pull/1252
We were not pinning our Telegraf version. This has been changed now and pinned to 0.13.0 until a new release. However one issue is that the cookbook will not downgrade or install a version if a later version is installed. Is this functionality you wish to add or would mind me adding in a PR? Specifically the ability to flag an install to downgrade if needed or just install the required version regardless of if a later version is previously installed?

Thanks for the update @Dan-Kitchen!  I would review a PR for installing a downgraded version as long as it could be done cleanly.  I don't think there should be any special flag though, the version should take care of it.
Ultimately, pinning is the right answer, I think.  We did have a default version for a while but that caused folks some other issues.  It might make sense to include that in our README.

Closing this issue.  Thanks!


test/e2e: Decrease config map data limit

This should help debugging flakes seen among others in https://github.com/coreos/prometheus-operator/pull/1586.

@brancz Annotations of  Prometheus rule CRDs are empty both on my local machine as well as Travis.

@brancz Could you give this a review?

lgtm, thanks for taking care of this!


[ERC Registry] Phase 2: Utilize eth_call for enhanced accuracy and to retrieve token details.

Problem
The ERC indexing tool can now detect ERC contracts and categorize them into ERC-20 and ERC-721. However, the categorized contracts only include the contract ID and EVM address, lacking other essential information such as name, symbol, and decimals.
Solution
Implement a new mechanism to make calls to the mirror node to retrieve the necessary information.

As an alternative we could use https://github.com/cdump/evmole (similar to sevm) to extract function selectors. The good thing about evmole is that it seems it allows us to detect the slot values read by a method statically. See for example https://evmole.xyz/#0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2/eth

This way instead of making one eth_call for each value we want to retrieve, we can get all desired slots in one go using https://testnet.mirrornode.hedera.com/api/v1/docs/#/contracts/getContractState.

Another alternative could be to deploy a wrapper contract to get the ERC20 metadata in one go, for example
contract ERC20Metadata {
    struct Metadata {
        string name;
        string symbol;
        uint8 decimals;
        uint256 totalSupply;
    }

    function getTokenMetadata(address erc20Address) external view returns (Metadata memory metadata) {
        metadata.name = IERC20(erc20Address).name();
        metadata.symbol = IERC20(erc20Address).symbol();
        metadata.decimals = IERC20(erc20Address).decimals();
        metadata.totalSupply = IERC20(erc20Address).totalSupply();
    }
}

this way, we get the real information from the network with only making one request per address.


Little fixes

Prerequisites
Before writing the CI I decided to check project state using linter. I ran my eyes through the errors given to me by eslint and fixed all the critical ones, now there's only warnings. Also changed some little things like:

unneded package-lock file (there's already a lock file created by yarn which can lead to errors)
added script to quietly check linter errors and fix fixable ones
deleted boilerplate descriptions from package.json
formatted code using prettier

Now all is pretty ready for developing a CI, will open another PR in a nearest future.

Great fixes!

2 space indentation is standard in react community?
Do we need the semicolons?

Great fixes!

2 space indentation is standard in react community?

It's not the standard, choice of indentation is the question of everyone's preferences(and of course project configurations), rule of thumb is to just use the same indentation everywhere in your js code.

Do we need the semicolons?

After developing a great CI it woulnd't be even a question, all required semicolons, indentations will be automatically added by github actions and a formatiing job.

Seem's like It's all done for this PR, will create another one with CI update soon.

Great fixes!

2 space indentation is standard in react community?

It's not the standard, choice of indentation is the question of everyone's preferences(and of course project configurations), rule of thumb is to just use the same indentation everywhere in your js code.

Do we need the semicolons?

After developing a great CI it woulnd't be even a question, all required semicolons, indentations will be automatically added by github actions and a formatiing job.

Ok sounds good!


Context menu actions not working

Prerequisites

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

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
I've just noticed that, in the latest nightly build, context menu actions are not working throughout the app. The context menu appears and allows me to choose an option, but nothing happens.
Steps to Reproduce

Open Atom with a project
Right-click on a folder in the tree view
Choose "New file..."

Expected behavior:
The file creation dialog panel should appear.
Actual behavior:
The context menu closes and no dialog is shown.
Reproduces how often:
100% of the time. It also reproduces with any other menu option on any other context menu (within a TextEditor, or on unstaged files in the git tab, etc).
Versions
github ➤ atom --version
Atom    : 1.57.0-nightly0
Electron: 9.4.4
Chrome  : 83.0.4103.122
Node    : 12.14.1
github ➤ apm --version
apm  2.5.2
npm  6.14.8
node 12.4.0 x64
atom 1.57.0-nightly0
python 2.7.16
git <IP_ADDRESS>50.gc219791418

Additional Information
No errors appear in the dev console, either.
Keyboard shortcuts (like "A" for the "New file" action in my repro steps) and running commands from the command palette both work as expected.
I'm guessing that this is related to an Electron upgrade?

Reproduced on nightly. I believe it is related to the electron upgrade

Could you delay the schedule for the next nightly release? There is also an issue with the CLI:
https://github.com/atom/atom/issues/22024
, and this PR is not merged yet:
https://github.com/atom/atom/pull/21927

@aminya we can't delay the nightly releases because of the bugs mentioned. Nightly builds are a reflection of what is on the master. The best we can do is expedite the fixes of the bugs mentioned.

@sadick254 Can we at least get those fixes backported to v1.56.0 before it is released?

We should definitely delay the stable version release. It doesn't make sense to release a stable version with a lot of bugs that are already fixed.
The Electron update should have all the fixes included otherwise people will open a lot of issues here.

people will open a lot of issues here.

Ruined UX and usability is the issue to worry about, not the github issues. Because it reduces productivity, and thus speeding up users drain to a competition products.

So i came here because i m exeperiencing all kind of issues. this is the biggest one to be honest.
I'll see if i find any of the root causes

I'm having the same problem
Atom Beta 1.56.0-beta0 x64
Manjaro Linux 20.2.1
When running atom from terminal I get this error message each time a click a item in the menu
Failed to serialize arguments Error: Failed to serialize arguments     at WebContents._.send (electron/js2c/browser_init.js:173:2149)     at AtomWindow.sendCommandToBrowserWindow (/usr/lib/atom/resources/app.asar/src/main-process/atom-window.js:377:36)     at AtomWindow.sendCommand (/usr/lib/atom/resources/app.asar/src/main-process/atom-window.js:364:12)     at AtomApplication.sendCommandToWindow (/usr/lib/atom/resources/app.asar/src/main-process/atom-application.js:1107:27)     at item.click (/usr/lib/atom/resources/app.asar/src/main-process/context-menu.js:21:34)     at MenuItem.click (electron/js2c/browser_init.js:65:1624)     at Function.executeCommand (electron/js2c/browser_init.js:73:1102)
Havbe tried fresh install and safe mode but the problem persist

So i have a solution that works for me, i m just not sure is the correct one. Thanks @aceventura82 because your stack here reduce the time for me to try to fix it to 5 minutes, rather thank looking everything from scratch.
I'll open the pr with the intent of spinning up a discussion to fix it, not sure my fix is acceptable

I opened an alternative PR i did not notice there was another one already open. The fix is indeed different, while the first PR seems a safer approach, i wonder what are we doing with that command detail at all.
Maintainers should know probably, i m interested to understand.

Fixed by https://github.com/atom/atom/pull/22046

@darangi can you make sure this gets fixed in v1.56.0 before it goes to stable as well. It would also be nice to get a v1.56.0-beta1 release with this fix.


add clickable buttons

same as assistant-simple, please add clickable buttons instead of standard list. if people wants lists they can use html formatting

This is being closed as this repo has been deprecated. If you had a question that arose through this issue that has not been answered, we recommend that you ask on Stack Overflow with the IBM Watson tag, or on IBM DeveloperWorks Answers with the tag WATSON


Ghost npm package for 0.10.0 release not available

Issue Summary
It doesn't seem like the [release] NPM package for 0.10.0 is available yet.
The latest release in the registry is 0.10.0-rc1 as of now.
Steps to Reproduce

Try to use 0.10.0 as the npm version:

{
...

  "devDependencies": {
    "ghost": "~0.10.0",

...

results in:
$ npm install
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node4-lts/4.4.7/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v4.4.7
npm ERR! npm  v2.15.8
npm ERR! code ETARGET

npm ERR! notarget No compatible version found<EMAIL_ADDRESS><0.11.0'
npm ERR! notarget Valid install targets:
npm ERR! notarget ["0.6.0","0.6.1","0.6.2","0.6.3","0.6.4","0.7.0","0.7.1","0.7.2","0.7.3","0.7.4","0.7.5","0.7.6","0.7.7","0.7.8","0.7.9","0.8.0","0.9.0-beta.1","0.9.0-beta.2","0.9.0","0.10.0-rc1"]
npm ERR! notarget
npm ERR! notarget This is most likely not a problem with npm itself.
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
...

Technical details:

Ghost Version: 0.10.0
Node Version: -
Browser/OS: OSX 10.11.6
Database: -

This is a known issue. Unfortunately, when publishing the 0.10.0 package, there was some issue with npm which meant some files were missing. We have asked npm to republish the proper version with all the necessary files. In the meantime, 0.10.0-rc1 is the exact same package.

We got an answer from NPM, there is no way to force a republish of the version 0.10.0.
As @ErisDS said, 0.10.0-rc1 is the same version. Closing this issue now, we will release 0.10.1 in a couple of days.


Help with pathmodify.mod.dir?

Hi,
I'm at the end of my rope here in trying to make this work, so thought I'd drop a line and ask the creator.
I have this:
var bundler = browserify(local_config);
var mods = config.app_paths_aliases.map(function(app_paths_alias) {
  return pathmodify.mod.dir(app_paths_alias[0], app_paths_alias[1]);
})

bundler.plugin(pathmodify, {
  mods: mods,
});

console.log(mods);

and it gives me the following console-output for mods:
[   { from: 'event/templates',
    to: '/home/flemming/workspace/dev/arch/event/templates/event',
    expose: undefined,
    type: 'dir' },
  { from: 'event',
    to: '/home/flemming/workspace/dev/arch/event/static/js/modules',
    expose: undefined,
    type: 'dir' } ]

-Does this look like a proper list of mods?
Now, in som browserify module I try
require('event/models/hs-event');

to get at the file
/home/flemming/workspace/dev/arch/event/static/js/modules/models/hs-event.js

But browserify tells me
Cannot find module 'event/models/hs-event' from '/home/flemming/workspace/dev/arch/arch/static/js/modules'

Any ideas? I think I've tried most alternatives, but there is always the option of me not groking browserify completly...
Cheers!

@gnimmelf Thanks for your interest in pathmodify!
That does look like a proper array of mods.  I'll probably change that in the next release.

That, sir, was the problem; not calling pathmodify. Cheers!
As you say, would be a good idea to change it, as other browserify plugins exports the actual plugin object, not a constructor-type function.
Thank you very much!

@gnimmelf You're welcome! Thanks for your feedback.

On second thought on the export; I see now that many plugins also export a constructor-type function, so you really don't need to change anything. And keeping it the way it is won't require us that use your package to update anything either...
Cheers.

On second thought on the export; I see now that many plugins also export a constructor-type function, so you really don't need to change anything. And keeping it the way it is won't require us that use your package to update anything either...

It's perhaps not totally cut and dry. The main thing is that a plugin should export the signature (b, opts), or do some special handling, if it's going to support the CLI. There's definitely an argument for not trying to use something like this (or doing anything that gnarly) via the CLI though. There's also something to be said for providing an interface consistent with other plugins. For the ones you're talking about, is the main export a constructor function? Or you mean they export something like a configure() function?
Thanks again for your feedback.

By constructor-type I just meant that they export a callable.
I'm using browserify for the first time now (with gulp, not the CLI), and rushing through it, so I haven't had the time to actually look into the code of plugins I'm using, so the comment was just from glancing over my code.
Cheers.


Fix BSI minification error

Wierd that polylint didn't catch this...

Before:

After:

@Surekh @omsmith?

@dlockhart Do you know of any more pitfalls of minification?

Yeah I've run into this a couple times myself as well, it's really confusing and annoying that Polylint doesn't catch it.
The only other thing I'm aware of that can be caused by minification is the removal of extra whitespace <between>    <your> <elements>, which I actually prefer to be removed but is a thing nonetheless.


OCPBUGS-9994: Verbosity levels for operator and operand

New deployment hook for adding --v argument on the basis of operatorSpec.logLevel
Added a func in default_cert_manager_controller to set klog verbosity level at runtime via operatorSpec.operatorLogLevel

Signed-off-by: Swarup Ghosh<EMAIL_ADDRESS>

/hold
I'll check out another operator like openshift-apiserver-operator to check if the values for --v is identical for Trace and TraceAll levels.

The bug also mentions operatorLogLevel, are you planning on addressing that in this PR itself?

/retest-required

/test all

/assign

Since the operator already has
https://github.com/openshift/cert-manager-operator/blob/70e39c50c56a5819e05b46b6d34be53d7fef0951/main.go#L23
, Is this functional? If yes we should be able to control log level via env variables which can be updated via the subscription.
Assuming the above flow works, I think we can choose not to support the operator logLevel via the cluster scoped resource.

As discussed previously, to support updating the operator log level from the deployment spec (possibly via the Subscription object on the cluster under the most likely use case of operator being installed through console) and given the predicate that we indeed want to do away with the default controller in the near future, I've updated the PR accordingly with ensuring that operatorLogLevel field of our custom resource is not used for setting the verbosity.
Despite the pflag.CommandLine.AddGoFlagSet(goflag.CommandLine) I found out that our binary still lacked the --v flag, and I was able to add it with cli.Run(command) referring to how cluster-kube-api-server-operator adds those klog verbosity flags.

Changed cli flags summary:
$ ./cert-manager-operator --help
OpenShift cluster cert-manager operator

Usage:
  cert-manager-operator [flags]
  cert-manager-operator [command]

Available Commands:
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  start       Start the cert-manager Operator

Flags:
   -h, --help                           help for cert-manager-operator
       --kubeconfig string              Paths to a kubeconfig. Only required if out-of-cluster.
+      --log-flush-frequency duration   Maximum number of seconds between log flushes (default 5s)
+  -v, --v Level                        number for the log level verbosity
+      --vmodule moduleSpec             comma-separated list of pattern=N settings for file-filtered logging (only works for the default text log format)

Use "cert-manager-operator [command] --help" for more information about a command.

/retest-required

Circling back to our discussion on allowing users to choose to change the operator log level by modifying the subscription object, I've added the OPERATOR_LOG_LEVEL env variable and set it value in the --v arg for klog to setup the log level correctly.
(JFYI @thejasn I found out that node-observability-operator uses a similar setting but since it is based on controller runtime it leverages zap logger which has a different log levels compared to klog, to my understanding debug in zaplog is probably the highest level available even using which we don't get the higher level klog logs that Trace (--v=6) and TraceAll (--v=8) gives us from most of library-go code, so added it this way).
I'll add a md doc about updating operator log level on production cluster (via subscription object) as well as while testing either through --v or changing the deployment's env var.
ref: https://github.com/operator-framework/operator-lifecycle-manager/blob/master/doc/design/subscription-config.md

/remove jira/invalid-bug

/remove-jira invalid-bug

/jira

/label jira/valid-bug

/remove-jira/invalid-bug

/retest-required

/jira refresh

/jira refresh

/jira refresh

/jira refresh

This hasn't yet Dev /lgtm label before labeling qe-approved. But anyway, labeling it; would like to do post-merge test since other work (including OCP Auth) items need me :)
/label qe-approved

/cc @xenolinux
for docs-approved label
/cc @davemulford
for px-approved label

/label docs-approved

/lgtm

/label px-approved


Error running simple mechanism reduction case

Hello,
I have started using cantera and pymars for a couple of days so it is still a code i am unfamiliar with. For a project, i need to reduce some complex mechanism for biomass pyrolysis using CRECK database. While i ran the chemical mechanism reduction command for the simple tutorial case available on the website : pymars --input reduction_input.yaml using the same procedure as the website I see the following error:
Traceback (most recent call last):
File "/home/adil/anaconda3/bin/pymars", line 8, in
from pymars.main import main
File "/home/adil/anaconda3/lib/python3.12/site-packages/pymars/main.py", line 4, in
from .pymars import pymars
File "/home/adil/anaconda3/lib/python3.12/site-packages/pymars/pymars.py", line 19, in
from .tools import convert
File "/home/adil/anaconda3/lib/python3.12/site-packages/pymars/tools.py", line 9, in
from cantera import ck2cti
ImportError: dynamic module does not define module export function (PyInit_ck2cti).
The mistake probably might be silly and come from me. I thought that it might come from installation or python version but didn't work out. I am too unfamiliar with the code to look into it in detail either. (tried unsucessfully).
Please kindly help.

Hello, I have encountered the same problem as you. Have you solved it? How did you solve it? Thank you very much.

Hello, yes I managed to solve it somehow.
I created two different environments, one running python 9.6 to use pymars
module options and one using python 9.12 to use pure cantera problems.
Using that I managed to make the cases work.
Best regards,
Adil
On Mon, Dec 30, 2024 at 10:48 AM kreto7 @.***> wrote:

Hello, I have encountered the same problem as you. Have you solved it? How
did you solve it? Thank you very much.
—
Reply to this email directly, view it on GitHub
https://github.com/Niemeyer-Research-Group/pyMARS/issues/88#issuecomment-2565253748,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVF47FVLUYEPZC2Y352ZTST2IEJIXAVCNFSM6AAAAABRS7YNTOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGI2TGNZUHA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Get mapnik-vector-tile FFI to produce tile for all features

Currently it seems that the FFI to mapnik-vector-tile only produces a tile for one feature, not all of the features in the GeoJSON.

Turns out the marshalling was stopping at the first null terminator. Now we explicitly pass the length of the tile back and all is well!


The blankRow of BS-RSCD dataset

Hi,
I'm tring to do an experiment on your dataset but I didn't find readout ratio in dataset dir. Is there a readot or blankRow? Any suggestions would be appreciated! (the box below is the blankRow)

Thank you in advance! :smile:

Hi, the videos were shot at 15fps.
So, the "blankRow" is around 50ms.

Appreciate it !


[operator] Cannot create report because name too long

What steps did you take and what happened:
We widely use various public helm charts and sometimes helpers in charts can generate very long resource names :)
Unfortunately, it leads to the following problem:
2020-12-21T09:47:39.168Z        DEBUG   controller.pod  Resolving workload properties   {"pod": "core/core-competency-matrix-production-prometheus-redis-exportejdkgp", "owner": {"Kind":"ReplicaSet","Name":"core-competency-matrix-production-prometheus-redis-exporter-5f9d846544","Namespace":"core"}, "hash": "5c4f744665", "containerImages": {"prometheus-redis-exporter":"oliver006/redis_exporter:v1.3.4"}}
2020-12-21T09:47:39.169Z        INFO    controller.pod  Checking scan jobs limit        {"pod": "core/core-competency-matrix-production-prometheus-redis-exportejdkgp", "count": 2, "limit": 3}
2020-12-21T09:47:39.172Z        ERROR   controller      Reconciler error        {"reconcilerGroup": "", "reconcilerKind": "Pod", "controller": "pod", "name": "core-competency-matrix-production-prometheus-redis-exportejdkgp", "namespace": "core", "error": "creating job: Job.batch \"cceaa8f9-8f8b-42e9-a5b3-673c7c62f2e4\" is invalid: [metadata.labels: Invalid value: \"core-competency-matrix-production-prometheus-redis-exporter-5f9d846544\": must be no more than 63 characters, spec.template.labels: Invalid value: \"core-competency-matrix-production-prometheus-redis-exporter-5f9d846544\": must be no more than 63 characters]"}

github.com/go-logr/zapr.(*zapLogger).Error /go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
  /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:246
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
  /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:218
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
  /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.6.3/pkg/internal/controller/controller.go:197
k8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1
  k8s.io/apimachinery/pkg/util/wait.BackoffUntil
/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:156
  k8s.io/apimachinery/pkg/util/wait.JitterUntil
/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:133
  k8s.io/apimachinery/pkg/util/wait.Until
/go/pkg/mod/k8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:90

Environment:

Starboard operator version: 0.7.1
Kubernetes version: 1.18.9

👋 @pcheliniy We're aware of this limitation and actually we plan to change the way we name and store VulnerabilityReports.
TL;DR; We're thinking about naming VulnerabilityReports by image digest. By doing that we'll eliminate the problem that you encountered. What's more, we'll store reports in more efficient way in case multiple workloads use the same image digest:

That's a really good idea.
I've checked our installation and if you realize your proposal we would halve the number of our reports.

Related to #280

Related to #280


Issue 22 nav dropdown

Fix #22
Adding loading of subsection data to be displayed in the site navigation and toggled via mouseover in desktop mode or clicking (with limited display) in mobile mode.
Test URLs:

Before: https://main--vonage--hlxsites.hlx.page/unified-communications/
After: https://issue-22-nav-dropdown--vonage--hlxsites.hlx.page/unified-communications/

Known issues:

Haven't gone through and hooked up most of the urls yet
Haven't implemented any tool menu functionality (search, language selector)
Need to switch the highlighting in the index section while in desktop nav from a mouseover only event to be 'sticky' so it remains highlighted while the associated section list is displayed.
There's an annoying layout shift in the body after the header loads (was there before I just haven't managed to fix it yet)
For some reason the underline on the drop down enabled buttons in the section nav is not extending to the padding added for the decoration chevron (was working previously)
Back to main menu button animation in mobile mode only runs on the first sub menu opening
Closing the mobile nav menu while a sub section is open results in the logo transitioning in from the left of the page (need to disable the animation so it just pops back in)
Scaling the size down and then up while menu is open will lead to oddities (need to close the menu if the screen size changes)
Z-order issue where some blocks in the page are floating over the nav (gradiant cards for example)

I think this is fine - I don't want to spin our wheels over-optimizing/overthinking things. We can do that later.